Related
I was trying to install a rom on my Kindle Fire HD 8.9 and I am now stuck on a red screen. The kindle will start up and show the boot logo for about two seconds before a red screen appears on the tablet. My device manage flashes as if it was updating the devices on my computer. My PC does not recognize my Kindle. Any help would be appreciated.
Unless you can manage to get it into fastboot somehow, there's nothing you can do
If you do a search on here for KFFirstAide, you will find loads of information on installing drivers, restoring OS and various other helpful tips.
Hope this helps
praed0r said:
If you do a search on here for KFFirstAide, you will find loads of information on installing drivers, restoring OS and various other helpful tips.
Hope this helps
Click to expand...
Click to collapse
It still requires fastboot
soupmagnet said:
It still requires fastboot
Click to expand...
Click to collapse
Have to get the drivers working correctly, that you should be able to get into fastboot!
lizzord30 said:
Have to get the drivers working correctly, that you should be able to get into fastboot!
Click to expand...
Click to collapse
Yes, I rooted my Kindle before causing this problem. I do have the drivers working. I apparently need to boot into fastboot. I cannot do this with a fastboot cable as they don't work on my device. I can't do this with a PC as my Kindle won't be able to connect to it. I'm at a standstill at the moment. I hope I will be able to fix my device at one point in time. If these are my only options I suppose I will sit on my thumbs until I am able to fix my Kindle.
Blissful_Tea said:
Yes, I rooted my Kindle before causing this problem. I do have the drivers working. I apparently need to boot into fastboot. I cannot do this with a fastboot cable as they don't work on my device. I can't do this with a PC as my Kindle won't be able to connect to it. I'm at a standstill at the moment. I hope I will be able to fix my device at one point in time. If these are my only options I suppose I will sit on my thumbs until I am able to fix my Kindle.
Click to expand...
Click to collapse
Working adb drivers doesnt mean you have working fastboot drivers (I had the same problem before) Had to uninstall the drivers then dissable driver signiture form windows and install the unsinged drivers from the kindle first aid.
After you get fastboot working then you can install my rom if you want! Should fix fastboot and install TWRP, after that you can install any rom you want! Hope you can get it going!
Here is the link
Thank you Lizzord30. After messing around in Kindle first aid I got it working again.
Blissful_Tea said:
Thank you Lizzord30. After messing around in Kindle first aid I got it working again.
Click to expand...
Click to collapse
What exactly did you do to get it working?
SolusCado said:
What exactly did you do to get it working?
Click to expand...
Click to collapse
16) Reboot the kindle fire into fastboot mode (alternative method).
I used kindle fire first aid. Once in fastboot I restored it.
Blissful_Tea said:
16) Reboot the kindle fire into fastboot mode (alternative method).
I used kindle fire first aid. Once in fastboot I restored it.
Click to expand...
Click to collapse
Thanks. I figured it out.
Blissful_Tea said:
I was trying to install a rom on my Kindle Fire HD 8.9 and I am now stuck on a red screen. The kindle will start up and show the boot logo for about two seconds before a red screen appears on the tablet. My device manage flashes as if it was updating the devices on my computer. My PC does not recognize my Kindle. Any help would be appreciated.
Click to expand...
Click to collapse
To get your device into fastboot mode, turn off your device. On your pc go to any directory where you have access to fastboot.exe and press shift+right click anywhere, Click "open command window here"
copy and paste this code
Code:
fastboot -i 0x1949 getvar product
you'll get "Waiting for device"
Just plugin your device using normal cable, Your device wil power up and get into fastboot
Now all you need to do is use a restore tool like Kindle Fire first aide to flash a fresh rooted image to your device.
I am trying to install Cyanogenmod on my kindle fire. However, before I was able to start flashing any images or anything like that, I ran into a problem (although this is probably the best time to have a problem). My Kindle Fire HD 8.9 won't enter fastboot mode.
I'm running Windows 7.
I installed the android SDK.
I installed Amazon's drivers for the Kindle Fire.
When I type in "Adb drivers" into the command line, I get my serial number.
When I type in "fastboot drivers", I don't get anything back.
When I type in "fastboot -i 0x1949 getvar product" , I get "waiting for device", I plug in my Kindle Fire HD 8.9 (Edit: when it is off), but it just says at "waiting for device".
I've tried typing ""adb reboot-bootloader", but that reboots the device normally.
I've read that I don't need a fastboot cable for the Kindle Fire HD 8.9 (unlike the 7).
What am I doing wrong?
Power OFF
Have you tried connecting your Kindle while POWER OFF. (Pressing power button for 20 Sec)
Steps
1. Go to elevated command prompt (admin command window)
2. type "fastboot -i 0x1949 getvar product", "waiting for device" should display on screen
3. Power off Kindle (20 sec press of Power Button)
4. Connect kindle to PC
It should go into Fastboot mode.
This will work. Hit Thanks if I helped you.
Didn't work.
mgaju said:
Have you tried connecting your Kindle while POWER OFF. (Pressing power button for 20 Sec)
Steps
1. Go to elevated command prompt (admin command window)
2. type "fastboot -i 0x1949 getvar product", "waiting for device" should display on screen
3. Power off Kindle (20 sec press of Power Button)
4. Connect kindle to PC
It should go into Fastboot mode.
This will work. Hit Thanks if I helped you.
Click to expand...
Click to collapse
I had already tried that without success. I tried it again, but it just booted into normal mode. I know i must be doing something wrong, but I'm not sure what.
ajshell1 said:
I am trying to install Cyanogenmod on my kindle fire. However, before I was able to start flashing any images or anything like that, I ran into a problem (although this is probably the best time to have a problem). My Kindle Fire HD 8.9 won't enter fastboot mode.
I'm running Windows 7.
I installed the android SDK.
I installed Amazon's drivers for the Kindle Fire.
When I type in "Adb drivers" into the command line, I get my serial number.
When I type in "fastboot drivers", I don't get anything back.
When I type in "fastboot -i 0x1949 getvar product" , I get "waiting for device", I plug in my Kindle Fire HD 8.9 (Edit: when it is off), but it just says at "waiting for device".
I've tried typing ""adb reboot-bootloader", but that reboots the device normally.
I've read that I don't need a fastboot cable for the Kindle Fire HD 8.9 (unlike the 7).
What am I doing wrong?
Click to expand...
Click to collapse
I'm in the slow lane now after trying numerous ways to root this 8.9 8.5.1 fire. Still not showing root but everything goes slow now.
Guess its better than a brick. Wonder if I can load a CM since my root failed.
ant17 said:
I'm in the slow lane now after trying numerous ways to root this 8.9 8.5.1 fire. Still not showing root but everything goes slow now.
Guess its better than a brick. Wonder if I can load a CM since my root failed.
Click to expand...
Click to collapse
Update: restored settings, back to fast but no root.
ajshell1 said:
I had already tried that without success. I tried it again, but it just booted into normal mode. I know i must be doing something wrong, but I'm not sure what.
Click to expand...
Click to collapse
Anyone figure this out? Having the same problem - won't boot into fastboot mode, just boots normally (with cable plugging in and fastboot waiting on the device). Adb also works fine.
Install android studio and get the drivers from that.
Same Problem on Kindle Fire 8.9 HD - Fastboot not work!
Hi,
I have the same problem. Adb works, fastboot doesn't work on my stock Kindle Fire HD 8.9" 2nd Generation. Here is my environment:
Windows 10 Pro x64 with latest MS Patches, Toshiba Patches, Intel Patches
BitDefender Anti Virus
ADB enabled on Kindle
Adb and fastboot Drivers installed via Android SDK
Kindle Driver install downloaded from Amazon
PC is new Toshiba Satellite P50W with USB 3.0
Drivers look okay in Device Manager
- Kindle Fire -> Driver = Android Composite ADB Interface provided by Amazon dated 12/3/2012
- Portable Devices / Kindle -> Driver =provided by Microsoft dated 6/21/2006
Symptoms:
ADB Commands work including adb kill-server, adb start-server, adb devices (returns Serial Number)
- Fastboot -i 0x1949 getvar product shows "waiting for device" in PC's CMD Window and never goes away
- I attach standard USB Cable to the Kindle that is currently Powered Down (not just sleeping) after issuing above command on PC
- Attaching USB Cable simply causes Kindle to power on and boot normally.
What I have unsuccessfully tried to date:.
Tried alternate commands:
- adb reboot bootloader (to start Fastboot)
- fastboot -1 0x1949 reboot (to exit Fastboot)
Tried USB 2.0 Port instead of 3.0 Port.
Tried reloading Kindle Drivers.
Trying Android Platform Tools Ver 23.1 RC1 instead of Ver 23.01
Tried two different "Standard" USB Cables, one Factory Cable by itself
Any Ideas? I've been trying to get FASTBOOT working so I can play with Cyanogenmod for a couple of days without any luck. Thanks.
Ken (Android Noob )
Same
Having the same issues on 5.1.1 5th gen 8.9HD. zero fastboot....
I'm having the same issue. Has anyone found a solution or found another way to root the device with version 8.5.1_user_5159720 installed?
Hate the Kindle version of the OS. I want to install CM or LineageOS (If I can find a build for it!)
Thanks!
---------- Post added at 11:33 AM ---------- Previous post was at 11:08 AM ----------
Sailing_Nut said:
I'm having the same issue. Has anyone found a solution or found another way to root the device with version 8.5.1_user_5159720 installed?
Hate the Kindle version of the OS. I want to install CM or LineageOS (If I can find a build for it!)
Thanks!
Click to expand...
Click to collapse
I did a bit more digging and found a tool that will root the device. You can find it at https://rootmaster.co Just download and install the APK on your device and allow it to root.
emaster101 said:
Having the same issues on 5.1.1 5th gen 8.9HD. zero fastboot....
Click to expand...
Click to collapse
this is a COPY/PASTE of my own post. the files i specify are the exact names, just search this section of X-DA for them. SEE BELOW.
i had the same problem with the "red screen of death" as well. i found that if i installed the "Minimal ADB and Fastboot" and / OR (i did the minimal first.... ) KFHD_SRTv1.3.5 and RUN THE APP FIRST, then when it says "waiting for device" you then plug in the ALREADY OFF tablet it then WORKS!! says "fastboot mode" on the tablet. and it is listed in device manager also.
i got BOTH apps here at this board in this section.
WARNING: i run windows XP with all updates as of 10-31-2017 (pm me for info, 2 lines of text!! ) . NEWER windows versions have "permission issues". fixes are posted in multiple topics here in the Amazon 7" Kindle Fire HD, 8.9" Kindle Fire HD, Kindle Fire 2 section. READ THEM!!
Start by turning off tablet. type in "fastboot -i 0x1949 getvar product". Get (waiting for device) message. Plug USB into tablet.
Hi Guys,
My android smart tv kodak 32hdxsmart pro stuck on boot logo,after i executed the following command.
ADB REBOOT BOOTLOADER
I was working on adb wifi and trying few adb commands on my tv to unistall few apps.
I tried male to male usb to connect fastboot ,but not connecting in fastboot mode or recovery.
Any help?
I found the motherboard inside the tv is cv950xh-c42 ,but am not able to find firmware for this board
I tried usb boot with u-boot.bin recovery image,but its not going to recovery as well ,any suggestion here?
kodak tv
rumsam said:
I found the motherboard inside the tv is cv950xh-c42 ,but am not able to find firmware for this board
Click to expand...
Click to collapse
download the frimware on your pc
format your pen drive in fat32
and then extract the files from downloaded RAR and copy it in the pen drive eject the pen drive and insert it into the tv and then boot the tv.
it might work.
gmail me for link cant post on xda yewaleprithvi2003
Hi I'm getting error on Appstore and most of the apps as "Device not licensed" on Kodak 32smartpro, please suggest.
Sammyoken said:
Hi I'm getting error on Appstore and most of the apps as "Device not licensed" on Kodak 32smartpro, please suggest.
Click to expand...
Click to collapse
does any one have kodak smart tv frimware needed urgently
i flashed a wrong frimware and now remote is not working
Hi, i am using Kodak 32 smart LED . In screen mirroring after 3 to 4 min it will be stuck.. what is the reason .... ia m using vivo v15 mobile. and i thought it was my mobile problem. So i have done flash my mobile last week but still the same problem is there. Any one know the issue? pls give the solution
rumsam said:
Hi Guys,
My android smart tv kodak 32hdxsmart pro stuck on boot logo,after i executed the following command.
ADB REBOOT BOOTLOADER
I was working on adb wifi and trying few adb commands on my tv to unistall few apps.
I tried male to male usb to connect fastboot ,but not connecting in fastboot mode or recovery.
Any help?
Click to expand...
Click to collapse
Hi bro I am also stuck with the same problem can you please help me to get out of it
rumsam said:
Hi Guys,
My android smart tv kodak 32hdxsmart pro stuck on boot logo,after i executed the following command.
ADB REBOOT BOOTLOADER
I was working on adb wifi and trying few adb commands on my tv to unistall few apps.
I tried male to male usb to connect fastboot ,but not connecting in fastboot mode or recovery.
Any help?
Click to expand...
Click to collapse
Hi, I'm stuck with same issue. Did you get it resolved?
What are the TV buttons to enter recovery mode in Kodak?
rumsam said:
Hi Guys,
My android smart tv kodak 32hdxsmart pro stuck on boot logo,after i executed the following command.
ADB REBOOT BOOTLOADER
I was working on adb wifi and trying few adb commands on my tv to unistall few apps.
I tried male to male usb to connect fastboot ,but not connecting in fastboot mode or recovery.
Any help?
Click to expand...
Click to collapse
Were you able to resolve this issue?
Sree9448958 said:
Hi, I'm stuck with same issue. Did you get it resolved?
What are the TV buttons to enter recovery mode in Kodak?
Click to expand...
Click to collapse
You cannot reboot into recovery mode directly.
I tried recovery.img from a different model of 42" FHDTV firmware img.
I copied only the img file into the USB drive and attached it to TV USB slot 1.
Switch on the TV plug while holding the Power button on back panel.
But it did not solved the problem of OP's boot logo issue.
Hello,
I was rying to install FireFireFire in my kindle fire 1 gen by doing this guide: https://forum.xda-developers.com/t/...flashing-fff-twrp-2015.2814955/#post-54124313
Beforehand I rooted kindle with saferoot successfully.
After device entered fbmode, it shows kindle fire logo and can't be recognized on computer.
How do I exit out of fastboot?
Is it possible to exit with short circuiting to boot via USB? how do I do this?
Kindle version is 6.3.4
mrsiri said:
Hello,
I was rying to install FireFireFire in my kindle fire 1 gen by doing this guide: https://forum.xda-developers.com/t/...flashing-fff-twrp-2015.2814955/#post-54124313
Beforehand I rooted kindle with saferoot successfully.
After device entered fbmode, it shows kindle fire logo and can't be recognized on computer.
How do I exit out of fastboot?
Is it possible to exit with short circuiting to boot via USB? how do I do this?
Kindle version is 6.3.4
Click to expand...
Click to collapse
Root doesn't affect flashing Recoveries or bootloaders
Likely a driver issue, Using Windows 10?
The only way to exit out of Fastboot mode that I know is
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Thank you for the reply.
I tried using both linux and windows 10 but none detected my kindle.
Can I try the short pin method? Since I never done anything like this before, do I need to ground myself before shorting to not get shocked? since my version is 6.3.4 and the guide had version 6.2.1 idk if I can
mrsiri said:
Thank you for the reply.
I tried using both linux and windows 10 but none detected my kindle.
Can I try the short pin method? Since I never done anything like this before, do I need to ground myself before shorting to not get shocked? since my version is 6.3.4 and the guide had version 6.2.1 idk if I can
Click to expand...
Click to collapse
You don't need to ground your self, you can try the short pin method, it doesn't matter what firmware version is installed.
sd_shadow said:
You don't need to ground your self, you can try the short pin method, it doesn't matter what firmware version is installed.
Click to expand...
Click to collapse
Okay I'll try that and report after doing it.
Thank you again
mrsiri said:
Okay I'll try that and report after doing it.
Thank you again
Click to expand...
Click to collapse
Shorting the pins before, after and during plug in didn't change anything on screen...
It should at least be detected on computer, but either windows or linux don't show anything.
Since I need to lift the cable slightly up for it to connect to computer, I guess the problem is the port.
mrsiri said:
Shorting the pins before, after and during plug in didn't change anything on screen...
It should at least be detected on computer, but either windows or linux don't show anything.
Since I need to lift the cable slightly up for it to connect to computer, I guess the problem is the port.
Click to expand...
Click to collapse
There were lots of port issue reported over the years, likely the most common thing that let to there retirement.
So instead of spamming the forums, I thought I would just make on consolidated post asking for help
Background: I have suffered from a visual disability for over 20 years. There are many facets to it but the one that is relevant here is that some displays trigger instant eye strain and migraines when I view them. I have been to over 27 specialists in 7 states over 2 decades and no one has been able to find out exactly what us causing it. All we know is the issue isn't really caused by the display, but what is driving the display, and seem to be related to colors somehow.
Anyway, I ordered a 4k Fire Stick on July 15, 2019. SO looking at https://forum.xda-developers.com/t/...is-prerooted-stock-images-6-2-8-0_r1.3983091/, it looks like my Fire Stick came with OS 6.2.6.5_r1. I do not recall it ever asking for updates before this, so I do not know if it ever updated to 6.2.7.7_r1 (which is the last update prior to the UI update). I would like to flash OS 6.2.6.5_r1 which is the closest ROM I can find to what was on the stick when I first bought it and it worked.
I also have an unopened 4k Fire Stick I purchased on Nov 29, 2019. This is still sitting new in the box and have never been opened or plugged into anything.
So here is where my questions start
General Questions
1. Are the sticks I ordered the "mantis" one? So I would look for "mantis" instructions for working with it? Can someone provide a stock Mantis 6.2.6.5 ROM, I really don't care too much about being rooted honestly.
Questions for upgraded stick (that I cannot use right now due to disability)
1. Is there any hope for this device? As I understand it there is an eFuse blown during the 6.8 upgrade preventing downgrades.
2. Is there any work going on that will allow that blown eFuse to be bypassed (like a modified 6.2.6.x ROM that doesn't check the eFuse status)?
Questions for unopened stick
1. Is there any way to block the updates while setting up the device (prevent auto update)?
- 1a: I know there is a "BlockUpdate.apk" that can be sideloaded and run, but to do that I would need to have the device up and running to enable ADB Debugging and connect to the device, so I would have had to go though the initial setup, which will update the device, making it to late to install the APK and block the update
- 1b: I know you can also install Remote ADB Shell on the stick and use the PM disable user commands to block OTA updates, but again, you can't get to the point where you can turn on ADB Debugging and install those apps before going though the initial setup, which will update the device, making it to late to block the updates
2. I saw there were some methods where people were using their routers to block access to certain Amazon and/or akamai servers so you could activate the stick but the update check would fail, but all those guides seem to be for Fire TV's, not Fire Sticks, and are all from 2016-ish. Do these still work?
Questions for Rooting device
1. I saw the aluminum foil trick, but all the guides I see seem to start after a point where the device has been activated, which would have forced the update and would be to late for me. Can you root BEFORE the device is activated?
2. How do you connect a Fire Stick to a PC to allow the Linux scripts to see it and root it? I can't connect to the TV and then to my wifi, cause once it connects to wifi, it auto updates, and we're stuck again.
So can anyone help me out? My end goal is to have my upgraded Fire Stick downgraded to the 6.2.6.5 version and will NEVER install a system update, and/or have my unopened FireStick activated and working and NEVER install an update. I don't really care about any enhanced "debloating" or anything after that.
Many thanks up front.
Yes, you can try the unlock infront of the setup, that is the way to go.
But I would test your ruined stick first, it doesn't harm anything... maybe big A. messed the efuse burning up, who knows. Short the stick and in case you can't see 'phone' mode in lsusb, the efuse is burned as expected.
Sus_i said:
Yes, you can try the unlock infront of the setup, that is the way to go.
But I would test your ruined stick first, it doesn't harm anything... maybe big A. messed the efuse burning up, who knows. Short the stick and in case you can't see 'phone' mode in lsusb, the efuse is burned as expected.
Click to expand...
Click to collapse
Thanks, how would I unlock the device and block the updates without having to go through through Fire Stick setup (which would force the update)
As I understand it, I could
1 - Boot up the modified Linux iso in a VM
2 - Open the Fire Stick and use the aluminum foil to short it
At that point, how do I connect the Fire Stick to my PC? If I plug it into my TV and connect it to my network, it's going to auto update.
Once the above quesiton is answered, I could then run the scripts and get root and get twrp via the scripts in the Linux iso. But at that point, what would I flash in TWRP to block the OTA updates? I would not be anle to get to any point that allows me to enable ADB debugging without going through the Fire Stick setup, which would force the OTA updates
The thing is really easy.
Older 4k sticks are vulnerable to the current kamakiri exploit, and newer sticks are not.
Amaz. fixed with 6.2.8.0 the bootrom feature used in kamakiri, so any kamakiri vulnerable stick gets fixed with that update... Only way to prevent this fix, is to unlock it first, then the OTA updates can't harm anything.
The unlock protects them. In this case the update is fine...
If you want to try the unlock, you need to follow the kamakiri OP.
You don't need a TV or a network connection for your stick.
You need the usb cable and some tinfoil.
No one knows if your stick is vulnerable or not.
You may check this in a terminal with the lsusb command, while shorted (see the unlock OP for details).
If you can keep the stick with the short in 'phone' mode (look in lsusb a few times instead of running the bootrom-step), you're lucky and the unlock may work.
Sus_i said:
The thing is really easy.
Older 4k sticks are vulnerable to the current kamakiri exploit, and newer sticks are not.
Amaz. fixed with 6.2.8.0 the bootrom feature used in kamakiri, so any kamakiri vulnerable stick gets fixed with that update... Only way to prevent this fix, is to unlock it first, then the OTA updates can't harm anything.
The unlock protects them. In this case the update is fine...
If you want to try the unlock, you need to follow the kamakiri OP.
You don't need a TV or a network connection for your stick.
You need the usb cable and some tinfoil.
No one knows if your stick is vulnerable or not.
You may check this in a terminal with the lsusb command, while shorted (see the unlock OP for details).
If you can keep the stick with the short in 'phone' mode (look in lsusb a few times instead of running the bootrom-step), you're lucky and the unlock may work.
Click to expand...
Click to collapse
I thought even if you were unlocked, once you were auto updated, the eFuse is blown and you can't downgrade?
FOr the old Fire Stick (that has never been upgraded so it should be fine) once I unlock the device and flash TWRP, what would I flash to prevent the OTA update from taking place during the setup of the device?
emkorial said:
I thought even if you were unlocked, once you were auto updated, the eFuse is blown and you can't downgrade?
FOr the old Fire Stick (that has never been upgraded so it should be fine) once I unlock the device and flash TWRP, what would I flash to prevent the OTA update from taking place during the setup of the device?
Click to expand...
Click to collapse
No, unlocked = safe.
There isn't a reason to mess with the initial update, as long as you've done the unlock successfully and TWRP is in place. Then you can downgrade anytime later to whatever OS version, if you like.
After you did the unlock, flash magisk, do the initial setup, enable adb, you can use adb shell commands to disable the OTA updates.
You don't need a TV or a network connection for your stick.
Click to expand...
Click to collapse
How do I interact with TWRP if it isn't plugged into the TV?? What do you see the TWRP screen on to navigate it??
See post two and three in the unlock thread...
Most people use always TWRP commandline via ADB.
Sus_i said:
See post two and three in the unlock thread...
Most people use always TWRP commandline via ADB.
Click to expand...
Click to collapse
So I am still very confused. If I have the Fire Stick only connected to my computer via USB cabl, there will be no Fire Stick display anywhere. So I will be unable to interact with TWRP. But step 1 of post 2 says I can use an OTG mouse to interact with TWRP. How can you use a mouse when the Stick isn't plugged in to a TV?? How do you even boot into TWRP when the stick isn't plugged in?
The second point says use a command line and use ADB, but I thought you need to have ADB permissions set on the device to allow that to work, and you can't get to those ADB permissions without activating the device, which will update it, which defeats the whole purpose
I really appreciate the help but I am totally confused. This is so very frustrating.
You can plug the hdmi into your TV, but that wont help you to interact, because you use TWRP commands via adb. Ofc you see the commands and the TWRP txt output in the terminal window...
If the unlock is done, you can unplug the usb and use OTG + mouse, if you like. Should work too, but you need an usb hub and a storage stick too, if you like to install a ROM or Magisk or whatever. TWRP commandline is easier, you can push files via adb and then just run a adb shell twrp install command...
If TWRP is up, adb is always enabled...
Only the fireOS wants a permission, if you want to use adb.
Sus_i said:
You can plug the hdmi into your TV, but that wont help you to interact, because you use TWRP commands via adb. Ofc you see the commands and the TWRP txt output in the terminal window...
If TWRP is up, adb is always enabled...
Only the fireOS wants a permission, if you want to use adb.
Click to expand...
Click to collapse
OK, that is helpful, so you are saying if I unlock the device, flash TWRP, and reboot into recovery, ADB will be enabled, there is no need to allow ADB Debugging and I can run those pm uninstall commands?
SO are you saying this is the process?
1 - Download linux iso and script to unlock
2 - boot 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?
If that is all correct, then I know I can type "adb shell" at that point to get to a shell window where I can send adb commands. Could I then execute the pm disable commands? Or do I NEED to flash a new rooted ROM before I do that? I honestly don't care at all about being rooted, I just want to disable OTA
7 - 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?
Also I have seen many different variants of the actual pm disable commands required to disable OTA, can you provide the actual correct ones?
Thanks again
emkorial said:
OK, that is helpful, so you are saying if I unlock the device, flash TWRP, and reboot into recovery, ADB will be enabled, there is no need to allow ADB Debugging and I can run those pm uninstall commands?
Click to expand...
Click to collapse
No, never said something like that
You cannot run pm uninstall commands in TWRP adb...
but you can run adb push/pull, adb shell, twrp install and all the other TWRP commands, in order to 'interact' with TWRP.
Maybe do some research, read a bit more about it. There are also some youtube guides out there.
emkorial said:
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
Click to expand...
Click to collapse
It doesn't matter if hdmi is in or out.
But you need to follow the unlocks OP.
You need to short the stick infront any usb connection...
i.e. run the script, keep the short, then connect usb and so on.
Take your time, follow the OP
Maybe @Bertonumber1 answers some of your other questions, I've got no time to continue for now... sry.
Sus_i said:
No, never said something like that
Click to expand...
Click to collapse
Thats exactly what you said. You said "If TWRP is up, adb is always enabled..." So which is it, will I be able to run adb shell and then run the pm commands once it boots into twrp or not?
Sus_i said:
You cannot run pm uninstall commands in TWRP adb...
but you can run adb push/pull, adb shell, twrp install and all the other TWRP commands, in order to 'interact' with TWRP.
Click to expand...
Click to collapse
So you are saying I cannot run adb commands from TWRP, but you say I can run adb shell from twrp, which I can then run adb commands from. Which is it?
Sus_i said:
Maybe do some research, read a bit more about it. There are also some youtube guides out there.
Click to expand...
Click to collapse
I've read everything there is on the topic and it's very poorly documented from a step by step perspective. Can you answer the questions where you gave two opposite answers?
And the other questions no one has answers:
1 - Do I need to flash a rooted ROM before running the pm uninstall commands?
2 - Do I need Magisk installed? If so how do I install it?
I've been a remember of xda dev for years and years over many devices and I will never, ever understand how no one on this site ever seems capable of just giving simple step by step instructions and answering simple direct questions with simple direct answers.
At this point I am more confused than when I started so I feel it is still to risky to try this
Sus_i said:
It doesn't matter if hdmi is in or out.
But you need to follow the unlocks OP.
You need to short the stick infront any usb connection...
i.e. run the script, keep the short, then connect usb and so on.
Click to expand...
Click to collapse
I get that the HDMI does not need to be hooked up. Can you answer my quesiotn about how to know when the device is rebooted if I have no display? So I just keep checking adb devices until it shows up?
Sus_i said:
Take your time, follow the OP
Maybe @Bertonumber1 answers some of your other questions, I've got no time to continue for now... sry.
Click to expand...
Click to collapse
Can you just answer this, once I unlock, and reboot, if I wait and then my device shows up in adb devices, can I then run adb shell and run the pm uninstall commands?
emkorial said:
Thats exactly what you said. You said "If TWRP is up, adb is always enabled..." So which is it, will I be able to run adb shell and then run the pm commands once it boots into twrp or not?
So you are saying I cannot run adb commands from TWRP, but you say I can run adb shell from twrp, which I can then run adb commands from. Which is it?
Click to expand...
Click to collapse
lol. Its just like I said yesterday:
You can run adb push/pull, adb shell, twrp install and all the other commands, in order to 'interact' with TWRP.
Click to expand...
Click to collapse
You see, it isn't TWRP that searchs for updates
It is the fireOS that wants to keep the stick up-to-date.
If you want to disable this OTA update process inside the fireOS, you need to run the pm disable commands while fireOS is up and running.
Then I said yesterday:
It doesn't matter if hdmi is in or out.
But you need to short the stick infront any usb connection...
i.e. run the script, keep the short, then connect usb and so on.
Take your time, follow the OP
Click to expand...
Click to collapse
About four hours later, you ask the same question, in the same wrong order!??:
emkorial said:
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
Click to expand...
Click to collapse
At this point It doesn't make sense, just to write it again and again, if you can't get the point.
emkorial said:
I've been a remember of xda dev for years and years over many devices and I will never, ever understand how no one on this site ever seems capable of just giving simple step by step instructions and answering simple direct questions with simple direct answers.
At this point I am more confused than when I started so I feel it is still to risky to try this
Click to expand...
Click to collapse
I'm sorry to hear that.
I've just realized that I can't help you at all, so I'm going to stop answering.
Wish you good luck. Have fun.
Sus_i said:
If you want to disable this OTA update process inside the fireOS, you need to run the pm disable commands while fireOS is up and running.
Click to expand...
Click to collapse
OK, that makes sense. But since Fire OS is up and running and sitting at the setup screen, USB Debugging has never been turned on. So how do you connect to the Fire Stick via ADB since you cant get to developer options?
UNLESS, does the pre rooted image you flash after unlocking have USB Debugging enabled by DEFAULT, so you DON'T have to turn it on via Settings? THAT would make this ALL make sense. Is that the case?
If so, then it would be
1 - Download iso and script
2 - boot iso and do foil trick and run script
3 - flash a rooted ROM (that will have USB Debugging enabled by default)
4 - boot Fire Stick and just sit at initial screen, don't go though setup
5 - Connect via ADB (which will work since USB Debugging is turned on by default)
6 - Run pm commands
7 - Continue with setup and OTA will be blocked
Is that correct?
Edit: I suppose I can just keep trying at each step until it works. Like this
Step 1 - Take the stick out of the box, plug it into the TV, get to the welcome screen, do not connect to wifi or set up the device (so no OTA updates will occur), connect the USB cable to my PC, and see if I can run the ADB Commands. If that doesn't work...
Step 2 - Unlock the device via the foil trick, plug the stick into the TV, get to the welcome screen, do not connect to wifi or set up the device (so no OTA updates will occur), connect the USB cable to my PC, and see if I can run the ADB Commands. If that doesn't work...
Step 3 - Flash a custom ROM, plug the stick into the TV, get to the welcome screen, do not connect to wifi or set up the device (so no OTA updates will occur), connect the USB cable to my PC, and see if I can run the ADB Commands. That should work as that mirrors the process in the guide.