yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] higogo:
I downloaded the patched iso image from https://github.com/amonet-kamakiri/fireiso/releases

Used etcher to copy ISO to USB, but PC will not boot to it, I get invalid boot device or similar error.

What is the best(right) way to create bootable USB?

Or should I create a bootable USB and then copy over the files from

https://github.com/amonet-kamakiri/fireiso/releases zip file?.
[Fire TV Original Android Development] Bertonumber1:
You won't know for sure until you open the device and hook it up to your pc.

Follow the OP carefully and place a piece of rolled up aluminium foil into the position (for the short) if your device doesn't show up on usb with the short in place then you cannot exploit the device.

When booting you have to F2, F12 and select your pc to boot from the USB drive.
[Fire TV Original Android Development] higogo:
All good, I can connect to device and boot to recovery with OTG mouse. Now what?

I am trying to reflash image but don't know how to upload image file to firestick for flashing.

Please advise
[Fire TV Original Android Development] Bertonumber1:
OK pretty simple, you cannot have the OTG cable connect while you send files to the firestick as it won't recognise stick. Use only factory cable and use :

adb push \path\to\yourfirmware\xxxx.zip /sdcard

adb push \path\to\Magisk-vxx.x.zip /sdcard

adb shell

twrp install xxxxx.zip

twrp install Magisk-vxx.x.zip

(optional)

twrp wipe cache

twrp wipe dalvik

Ofc you can place the files onto a USB flash drive (fat32) on otg and install from ext_sd in twrp gui under "select storage" then "install"

Flash your rom first then magisk

Regards
[Fire TV Original Android Development] emkorial:
How to you interact with the Fire Stick after you do the short unlock? Is this all over the TV display?

Are the simple instructions for going from "Open Box - Remove Stick" to "Having a rooted stick that can be downgraded to remove the OTA Update"?
[Fire TV Original Android Development] emkorial:
The picture in the first Post shows 2 options for shorting, but 3 circles. Which circles go to which option?
[Fire TV Original Android Development] Rortiz2:
You can either short DAT0 or CLK
[Fire TV Original Android Development] emkorial:
Thanks. Once shorted how would I go about disabling OTA before I plug it into my TV and activate it?
[Fire TV Original Android Development] Sus_i:
In case the unlock worked and you've got TWRP, your stick is safe...

Install Magisk and then you're able to use this adb shell commands, to block updates:

su

pm disable com.amazon.device.software.ota

pm disable com.amazon.device.software.ota.override

pm disable com.amazon.tv.forcedotaupdater.v2

PS: It's better to short the whole part instead of the circled side.
[Fire TV Original Android Development] higogo:
Thanks,

That is a good idea
[Fire TV Original Android Development] 5h1v4u:
I unlocked and then flashed skel40 debloated rom. After rebooting from it, fire tv updated itself and while flashing open recovery script, I unplugged the power. Now it doesn't seem to have any os and it simply bootloops within 3 seconds. Wouldn't boot to twrp either and bottom exploit can't recognize the device anymore. How do I reset the stick back?
[Fire TV Original Android Development] Sus_i:
Connect an OTG cable with mouse and TWRP will come up...

If not, re-do the unlock in order to boot TWRP.
[Fire TV Original Android Development] emkorial:
How would I A) Install Magisk (what is Magisk) and B) use Magisk to execute ADB commands before the stick is activated (If I activate the stick it will just update OTA and I'm back where I started)
[Fire TV Original Android Development] 5h1v4u:
It did not. It boots and displays fire tv for few seconds and reboot again. Device is not recognized to do the unlock

Edit: Nvm, unlocking now
[Fire TV Original Android Development] Sus_i:
lol. You should first try if your stick is unlockable, if not that questions are obsolete. ;)

You see, you replace the stock recovery with TWRP due unlocking, so the efuse is safe, because the efuse gets blown by the stock recovery, not via TWRP. In other words, if you get TWRP running and the OS does an OTA update, TWRP will boot up instead the stock recovery.
[Fire TV Original Android Development] Sus_i:
Don't forget, your system partition is damaged, you need to fix this with TWRP, i.e. install a stock update file and Magisk.
[Fire TV Original Android Development] Bertonumber1:
Google magisk manager root for an explanation as to its purpose. Though my thought is if you don't know what magisk is you should probably leave it well alone. But hey.. You're going to do it anyway aren't ya.

I recommend you read this post thoroughly

https://xdaforums.com/t/newbie-guid...root-and-install-addons-firestick-4k.4015273/

Follow it to the letter .

NO.. If you have a stick that can be unlocked do NOT plug it in and register it unless you have disabled Ota first.

If you follow that guide above you'll be OK, on first boot when you've unlocked your device, enable adb and then you can enter the commands immediately to disable updates

Which are as follows :

adb shell

su (grant root permission)

pm disable com.amazon.device.software.ota

pm disable com.amazon.device.software.ota.override

pm disable com.amazon.tv.forcedotaupdater.v2

Regards
[Fire TV Original Android Development] emkorial:
So this is what I am trying to do, but I don't see how it is possible since the updates are installed DURING the setup. If I could get to ADB before the OTA update was installed I am entirely comfortable with connecting to the stick via ADB and running those commands.

The problem is I have not found any way to get to the point where I can get to the system preferences and enable ADB debugging so I can connect to the device via ADB and run those commands without the update being applied and blowing the eFuse, which defeats the purpose of blocking the update.

Sus_i says if I unlock the device using the tinfoil trick that will prevent the eFuse from blowing, and I do consider him to be a very knowledgable source but I'm just not comfortable gambling on that because if it does I'm screwed

You say "If you follow that guide above you'll be OK, on first boot when you've unlocked your device, enable adb", I don't see how unlocking the device would prevent the system from updating OTA during first boot. How do you enable ADB on first boot without having the OTA update installed? If I could figure that out I think I would be golden. Disabling OTA seems like the easy part, getting to a point where I can access the Stick via ADB to disable OTA without the OTA being applied during the first boot is the brick wall I can't seem to get past

Edit: So that "newbie" guide (which is still VERY confusing) Says I SHOULD plug the Fire Stick into a TV, but when I do that won't it just update and screw me? And Sus_i said I should unlock the device WITHOUT plugging it into the TV. Which is correct?
[Fire TV Original Android Development] Bertonumber1:
And Sus_i was correct in telling you this. If you unlock your device upon first boot enter >settings >developer options> and enable adb and apps from unknown sources.

Goto managed installed apps and give magisk manager permissions. Then :

Disable ota:

pm disable com.amazon.device.software.ota

pm disable com.amazon.device.software.ota.override

pm disable com.amazon.tv.forcedotaupdater.v2

Reboot to twrp and flash another firmware (preferably 6.2.7.6/7) with latest magisk flashed directly afterwards and reboot.

We could sit all night going through the risks but it's software related so the risks will always remain hence the disclaimers at time of each modification.

You shouldn't have any problems but if you don't want to take the risk it's pretty simple. Don't do it!!

Regards
[Fire TV Original Android Development] emkorial:
If I unlock my device, that itself does not disable updates, correct?

So the process you are saying is

1. Unlock device

2. Setup device, it will update to 6.0.8.x during setup

3. Enable ADB and then Disable OTA via ADB commands

4. Then downgrade to 6.2.7.6?

Wouldn't the 6.0.8 upgrade blow the eFuse and make downgrading impossible?

The software risk I am cool with cause thats rarely non reversible, it's the eFuse hardware risk that is worrisome because that is a one way door.
[Fire TV Original Android Development] Bertonumber1:
No. If you short it and unlock it you should still be able to flash another firmware .... If not worst case is.... you will be stuck on 6.2. 7.8 without the possibility of a downgrade to an earlier firmware but at least you will still be unlocked and rooted.

I don't know what else you need me to tell you

Regards
[Fire TV Original Android Development] emkorial:
The entire point of this exercise is to avoid the 6.2.8.x upgrade.

All I'm looking for a step by step instructions to get a Firestick I can use that will not upgrade. No one seems to be able to put that list of steps together. I don't get it. Even the "Noob friendly guide" doesn't explain 1/2 of the process. I really don't get why it's so hard to just say "Step 1 - Do this, Step 2 - Do this"
[Fire TV Original Android Development] emkorial:
I do not want to flash another firmware. I don't care about being rooted at all. I'm never going to install any silly add-on's or pointless extras. I have one goal and one goal only: Keep the OS version on the stick now and prevent it from ever updating.

Here is the process I have put together from scouring about 20 different threads and a half dozen conversations.

1 - Download the linux iso and the script to unlock the Fire Stick

2 - boot a PC with the linux iso

3 - plug Fire Stick into PC with supplied USB cable only. Do not plug the HDMI into anything

4 - Run the script and do the tinfoil thing

5 - After the script is done type "./fastboot-step.sh" which will reboot the device into TWRP. I will have no idea if this is working because there is no display for me to look at, correct?

6 - I would I guess wait a few minutes for the device to reboot since I would have no display available I would have no idea when it is done rebooting, but at some point I would type "adb devices" and my device would appear in the list? Is this how you tell the Stick has rebooted?

7. Type "adb shell" at that point to get to a shell window where I can send adb commands.

8. Type su to get into superuser mode. Do I need "Magisk" (whatever the hell that is) or will su work?

9 Once I see the hashtag to know I am in su mode, execute the pm disable commands

10 - And then after that, OTA would be disabled, I can unplug the Stick from my PC, plug it into my TV for the first time, and it would let me register and not auto update during the registration process and never bug me for updates again?

Is that right? Or do I NEED to flash a ROM? I don't care about being rooted at all so if all flashing a ROM does is give you root I am happy just skipping it. Or is that how I get this "Magisk" thing, or do I even need that?

Also I have seen many different variants of the actual pm disable commands required to disable OTA, can you provide the actual correct ones?

Just the simple, bare bones steps you need to do to prevent the OTA update from ever happening. I am not going to risk setting up the stick and running the upgrade and hoping I can the "re-downgrade"
[Fire TV Original Android Development] emkorial:
The worst case is the device will be stuck on 6.2.8 ad I cant downgrade it and it get thrown in the trash because that OS version triggers my disability. I am seriously confused why no one can follow what I am after here.
[Fire TV Original Android Development] emkorial:
I want to do is execute the pm commands from an ADB Shell BEFORE the OTA updates are installed during setup. In order to execute those commands, I need to turn on USB debugging. But I cannot get to the screen to turn on USB debugging until I set up the Fire Srtick, which will install OTA updates. So How do I execute the ADB commands without going through the Fire Stick setup?

Will flashing a custom ROM enable USB Debugging by default, so I DON'T have to go to Settings to turn it on? If so, THAT would make sense as I could connect to the device via ADB and run the PM commands BEFORE setup went to check for updates and disable them.
[Fire TV Original Android Development] JohanVincent:
It doesn't seem that hard to short your device & I have been trying since yesterday. Mine either gives me the message mt65xx Preloader after running lsusb, which from what I've read means the short wasn't applied, or Linux doesn't recognize the device. If I unplug and plug my USB cable back into my PC it will sometimes find the device. I am really puzzled at this point!

My serial number is like this VM149, so it should be exploitable and I purchased it Nov 2019. I am wondering if I am out of luck?

I am running Linux off of my PC because I cannot boot it off of the USB key I made through Rufus.

Edit: I think I am, I am on Software Version 6.2.8.0
[Fire TV Original Android Development] emkorial:
I don't know if it matters, but if your device was updated to 6.2.8.0 via amazon OTA, it blows an eFuse to prevent some things from happening. Maybe the foil trick is one of them?

I will soon be trying this on a stick that was bought in Nov 2019 and never opened or used, so I will see if it works on that one.

Are you using a VM? That is what I am going to try first, and if i run into problems I can boot an old laptop I have laying around off the USB stick and try it on a bare metal.
[Fire TV Original Android Development] JohanVincent:
Yep used a VMWare trial option (30 days)
[Fire TV Original Android Development] emkorial:
I have had USB problems before running Linux in a VM. Just a guess,
[Fire TV Original Android Development] JohanVincent:
Yeah I did too, I was presented one option to connect the USB to the Host or the VM. I selected the VM and it seemed to work ok? I just wish I knew what I was doing wrong as to why I could not boot Linux from the USB.
[Fire TV Original Android Development] Bertonumber1:
@emkorial So why all the questions about unlocking and magisk etc???? You gave the impression you wanted to unlock the device, hence why I explained how to do it.

Just do the research instead of challenging everything I post .. If you know everything already why you asking?

You cannot avoid the update nag at boot unless you edit the build.prop in twrp before flashing the zip (you will still need to unlock bl and root to do this)

Add insecure ADB and by putting adb shell monkey -p com.amazon.tv.oobe -v 500 to bypass the update nag screen

That's probably (if still possible) the only way round it. Again... you will have to unlock and root your mantis to do this.

You can use the adb commands without root with regard to disabling updates once you've got to the home screen.

Use the search facility on xda to learn how to do it . Google is also your friend in this respect.

Regards
[Fire TV Original Android Development] emkorial:
My goal is to block OTA updates during setup with as few steps as possible. If I don't need to unlock or flash a new ROM to do that, I'd prefer to go the simpler route because it gives less chances for me to mess something up, and I am really good at messing things up. Is it possible to get to the Home screen of a non unlocked, non rooted Fire Stick without the OTA update occurring? If so that would solve all my issues, but I cannot find a reliable method to do so. I saw some posts talk about blocking Amazon servers in your router config, or downloading the Fire Stick remote control app on your phone that allow you to bypass the update and get to settings, but those are all from like 2014 and don't seem to work on newer Sticks.

Sorry if I am coming across frustrated. No ill will intended.

Can the "nag" be bypassed so the update does not install? I so rarely reboot the Fire Stick that if it is easy to just dismiss the nag, I wouldn't consider that a huge hassle.

I've not heard of "insecure ADB", could you explain what that is? Is that the Remote ADB shell APK?

I managed to put that together, since none of the tutorials on how to run the pm commands said they required root. The issue I have is that I cannot get to the home screen and then settings to enable USB debugging to be able to execute those pm commands without going through the Fire Stick setup, which will update the stick.

If there is a way to bypass the OTA update that occurs during the Fire Stick setup, and get to the Home screen in an non updated state, I know I could then execute the pm commands. But so far I have not found a way to bypass the OTA update that occurs during setup before you get to the Home Screen. Do you know of one?

From what I seeing at this point, the only way to be able to run those PM commands prior to the forced OTA update during setup is to have USB debugging enabled by default, and the only way to have USB debugging enabled by default is to unlock the device, flash TWRP, and flash a rooted ROM with USB debugging enabled by default. Is that a correct statement?

Thanks again for the ongoing help!
[Fire TV Original Android Development] emkorial:
Maybe you have the boot mode wrong? From my memory of working with rufus, you have 2 options to burn the stick, either MBR or UEFI. You need to match whichever method your BIOS supports.

Go into the BIOS of your PC and see if it has a "Boot Mode" option you can check. Most of the ones I have seen will have 2 options, "Legacy" (which is MBR) and "UEFI". Make sure your boot mode matches whichever mode you burned the stick with in Rufus.

In general I always pick Legacy/MBR if possible, it just seems to go smoother for me, but UEFI works too.
[Fire TV Original Android Development] Bertonumber1:
No worries.

Have you tried simply? :

pm disable-user - - user 0 com.amazon.tv.oobe

(I have done this command several times to sticks stuck at update screen)

Another method is to Download the firetv remote app (find out your sticks ip) and use it to get to the settings menu on the stick.

Once you've done that you can then enable adb and use your pc/phone/tablet to issue the commands you want.

The links below explain how to bypass the setup screen on blacklisted sticks, however I understand we have same kinda issue here. Check it out :

Tutorial (READ ME FIRST!)

docs.google.com

Blacklisted FireTVstick Tutorial and Tools - Google Drive

I don't know if this method will still work but it should. If not there's not really a lot more you can do without going down the road of root and build.prop tweaks.

Regards
[Fire TV Original Android Development] emkorial:
At which point would I try that command? Would that be upon inserting the Stick, having it at the Welcome screen and then connecting a USB cable? I do not know if I would have ADB access at that time since USB Debugging will not have been enabled on the default OS

If the stick is sitting on the welcome screen, I do not know if adb devices will see the device and if I can use adb shell to execute that pm command. I will try it and then report back.

If you don't mind explaining what is the difference between that command and the pm commands that disable the OTA updates?

I saw that men tioned in another post but several users reported that method as no longer working. I am worried to try it because in order to connect to the stick, I need to connect the stick to my network, whihc will put it online, and possible allow it to update

I will give those a read, thanks

Edit: That doesn't really seem to apply, in a weird way they describe a situation I would LIKE to have in that the Stick will not update LOL.

Do we know if blocking d1s31zyz7dcc2d.cloudfront.net, amzdigital-a.akamaihd.net, and amzdigitaldownloads.edgesuite.net on the router still works in blocking updates? I see it mentioned in a few guides but they are all from 2014-2015.

I guess theoretically I could start a hotspot session on my phone, disable the phones internet access, connect the fire stick to the phones hotspot, and be able to get to it over a network that way. I'll give it a shot, it's non intrusive so can't hurt anything

Reading https://www.aftvnews.com/how-to-blo...k-by-setting-a-custom-fire-os-version-number/, it looks like I could unlock the device and edit the build prop without having to flash a ROM, I could just edit the build prop on the device. That would be one less step at least, I'll try that as a step before flashing a prerooted ROM
[Fire TV Original Android Development] emkorial:
Well that was a disaster.

I unboxed the Fire Stick. I plugged it into the TV. I powered it on. I paired the Remote. I picked my language. It then DOWNLOADED UPDATES BEFORE I EVER CONNECTED TO A WIFI NETWORK!!! HOW DID IT GET ONLINE????!

So I now have two ruined FireSticks.
[Fire TV Original Android Development] Bertonumber1:
It shouldn't have downloaded the updates without connecting to Internet . Goto settings

As soon as you've enabled adb disconnect Internet and run the commands

pm disable-user - - user 0 com.amazon.device.software.ota

pm disable-user - - user 0 com.amazon.tv.forcedotaupdater.v2

pm disable-user - - user 0 com.amazon.device.software.ota.override

When you've allowed adb permission to pc

You don't have two ruined firesticks

Edit : I thought you didn't wnst to unlock the stick? I already said unlock root and edit the build.prop via twrp (ie insecure adb within prop config / build.prop) ....

Regards
[Fire TV Original Android Development] retyre:
Don't be so sure. It's for purposes like these that Amazon allows users to save their WiFi passwords on its server. No user intervention needed.
[Fire TV Original Android Development] Bertonumber1:
Yeah right enough... If he unlocks the mantis via short process won't he be able to regain control?

Regards
[Fire TV Original Android Development] JohanVincent:
@emkorial I may have missed one of your requirements, but since I have the update and the eFuse has supposedly been triggered I installed Wolf Launcher. I've also disabled some of the software I don't want running on the Fire Stick. Maybe you could explore that route?
[Fire TV Original Android Development] emkorial:
I tried Wolf Launcher myself and it is quite nice, however one thing the update installs is an update to the HDMI driver. That update is what seems to be triggering my issues. Apps that gave me no problem before are now causing migraines , which means the underlying display stack has changed. So it;s not just a matter of UI preference, it seems to be a driver update that is installed.
[Fire TV Original Android Development] Bertonumber1:
Lmao were just going round in circles here I think I said all this in beginning when I thought you wanted to unlock it as you were enquiring about magisk etc.

You're right you cannot do Any of this without unlock and root. Which is my point really. Unless you're willing to root the device etc you're up sh*t creek without a paddle with regard to modifying anything /system.

But you can still disable ota etc by adb BUT only once you've got by the update screen and to home screen, but I guess you already knew that.

The long and short of it you cannot do anything without unlock and root

I wish you all the best

Regards
[Fire TV Original Android Development] Sus_i:
lol, yeah.

Idk why it is so hard, just to do the unlock first.. it will protect the efuse ;)

Then all options are possible, up- or downgrade, just nothing gets blocked.
[Fire TV Original Android Development] BeAtSs:
Can anyone confirm that unlocking by shorting still works with FireOS 6.2.8?
[Fire TV Original Android Development] Sus_i:
No, OP won't work anymore, due to the efuse thing.
[Fire TV Original Android Development] Bertonumber1:
Half a day of my life I'll never get back... I gives up pmsl

Hope you're well my friend :cool: