Related
I was following directions on rooting 2.2 on my mac and now am stuck in a boot loop and unable to get into recovery.
After applying PC36IMG.zip the phone rebooted as the instructions said it would. Then I ran the command ./adb shell mv /sdcard/PC36IMG.zip /sdcard/root-PC36IMG.zip
Which gave the following error.
error: device not found
My computer is no longer communicating with the phone and when I go into recovery I get a red triangle with an exclamation mark.
Can anyone help?
Hello,
I just received a Kindle Fire and decided to root and install Cyanogenmod. I found a tutorial which I thought looked pretty straightforward on Lilputing. I downloaded the Kindle Fire Utility and followed both the utility and the article told me to do. After installing TWRP 2.0, disaster. I rebooted the device and the Kindle read, "press power button for recovery," and showed a yellow triangle with a fire icon in the middle. I pressed the power button, and nothing happened. At this point, I rebooted. The device would not get passed this screen, and my PC would not recognize the Kindle. I presume I bricked my device, however (as I do not have any experience in this field) I honestly have no idea what I did, nor do I know where to go next. Any suggestions? Please help!
I'm stuck too. And i cannot install the driver because it is an unknown device.
kw1999 said:
Hello,
I just received a Kindle Fire and decided to root and install Cyanogenmod. I found a tutorial which I thought looked pretty straightforward on Lilputing. I downloaded the Kindle Fire Utility and followed both the utility and the article told me to do. After installing TWRP 2.0, disaster. I rebooted the device and the Kindle read, "press power button for recovery," and showed a yellow triangle with a fire icon in the middle. I pressed the power button, and nothing happened. At this point, I rebooted. The device would not get passed this screen, and my PC would not recognize the Kindle. I presume I bricked my device, however (as I do not have any experience in this field) I honestly have no idea what I did, nor do I know where to go next. Any suggestions? Please help!
Click to expand...
Click to collapse
Try this:
1) Download v6 of the Kindle Fire Utility from here. (The forum thread can be found here)
2) Extract the files into a folder anywhere (but remember where, obviously)
3) Go into the folder, then into 'drivers' and open up adb_usb.ini in a text editor and add "0x18D1" (without the quotes) on a line underneath "0x1949"
4) Open up Device Manager and find "kindle". It should have a yellow triangle near it.
5) Download fastboot.exe from here
6) Open up command prompt and navigate to wherever you saved fastboot to.
7) Run the command "fastboot oem idme bootmode 4000"
8) Power off your device by holding down the power button for ~10 seconds and turn it back on, and this time don't hit the power button to go into TWRP. It should move past the yellow triangle after a few seconds and boot into Kindle. Hope this helps!
Thank you!
I did, however, find a solution using the Kindle Fire Utility.
With my device connected to my computer, I selected Change BootMode. Next, I chose Normal. That brought me out of the frozen boot screen, so I decided to wing it and flashed Cyanogenmod, and that worked. Thank you anyway for your time.
bikeracer4487 said:
Try this:
1) Download v6 of the Kindle Fire Utility from here. (The forum thread can be found here)
2) Extract the files into a folder anywhere (but remember where, obviously)
3) Go into the folder, then into 'drivers' and open up adb_usb.ini in a text editor and add "0x18D1" (without the quotes) on a line underneath "0x1949"
4) Open up Device Manager and find "kindle". It should have a yellow triangle near it.
5) Download fastboot.exe from here
6) Open up command prompt and navigate to wherever you saved fastboot to.
7) Run the command "fastboot oem idme bootmode 4000"
8) Power off your device by holding down the power button for ~10 seconds and turn it back on, and this time don't hit the power button to go into TWRP. It should move past the yellow triangle after a few seconds and boot into Kindle. Hope this helps!
Click to expand...
Click to collapse
For me 7 resulted in a device not found, though I fixed this by rebooting the kindle (I guess fastboot mode ends at some point?)
So after I fix this - how do I get into TWRP? Trying to install it from the utility does not work!!
andTab said:
For me 7 resulted in a device not found, though I fixed this by rebooting the kindle (I guess fastboot mode ends at some point?)
So after I fix this - how do I get into TWRP? Trying to install it from the utility does not work!!
Click to expand...
Click to collapse
Unfortunately, I don't know. I've been trying to get in TWRP all night and have been unsuccessful. I knew how to get out of this issue because I've put myself here several times tonight, trying to get TWRP to start up...so far, no luck...
I had same problem. Kept booting to "press power button for recovery" but never went to recovery. I had to download and install FireFireFire manually after i installed twrp. Now works great. Just power off then hold power button in for few seconds (until it turns orange) when powering back on, release, then there's twrp.
Wired0980 said:
I had same problem. Kept booting to "press power button for recovery" but never went to recovery. I had to download and install FireFireFire manually after i installed twrp. Now works great. Just power off then hold power button in for few seconds (until it turns orange) when powering back on, release, then there's twrp.
Click to expand...
Click to collapse
THANK YOU! This fixed the problem, I just had to find the thread that was ONLY FireFireFire, and not combined with TWRP, since that hadn't worked for me. I included instruction below for anyone having similar issues:
I downloaded the u-boot.win from here then ran
Code:
fastboot flash bootloader u-boot.bin
at which point it sait "Waiting for device". So I rebooted the Kindle like had the last several times that's appeared and it flashed it and then I rebooted again and I held down the power button, and it turned amber, like it had earlier, except THIS time it actually booted into TWRP!! Hooray! Hope this helps anyone else having this issue.
bikeracer4487 said:
Try this:
1) Download v6 of the Kindle Fire Utility from here. (The forum thread can be found here)
2) Extract the files into a folder anywhere (but remember where, obviously)
3) Go into the folder, then into 'drivers' and open up adb_usb.ini in a text editor and add "0x18D1" (without the quotes) on a line underneath "0x1949"
4) Open up Device Manager and find "kindle". It should have a yellow triangle near it.
5) Download fastboot.exe from here
6) Open up command prompt and navigate to wherever you saved fastboot to.
7) Run the command "fastboot oem idme bootmode 4000"
8) Power off your device by holding down the power button for ~10 seconds and turn it back on, and this time don't hit the power button to go into TWRP. It should move past the yellow triangle after a few seconds and boot into Kindle. Hope this helps!
Click to expand...
Click to collapse
Thank you so much!!!!!! i thought my device was a gonner... and i just got it today
how can you remove TWRP from kindle fire if it's possible, whatit to boot likeif i just got itout of the box, which i did today when i recieveit.
Thanks.
bikeracer4487 said:
Try this:
1) Download v6 of the Kindle Fire Utility from here. (The forum thread can be found here)
2) Extract the files into a folder anywhere (but remember where, obviously)
3) Go into the folder, then into 'drivers' and open up adb_usb.ini in a text editor and add "0x18D1" (without the quotes) on a line underneath "0x1949"
4) Open up Device Manager and find "kindle". It should have a yellow triangle near it.
5) Download fastboot.exe from here
6) Open up command prompt and navigate to wherever you saved fastboot to.
7) Run the command "fastboot oem idme bootmode 4000"
8) Power off your device by holding down the power button for ~10 seconds and turn it back on, and this time don't hit the power button to go into TWRP. It should move past the yellow triangle after a few seconds and boot into Kindle. Hope this helps!
Click to expand...
Click to collapse
I tried this and it won't work, what am I doing wrong ?
Why is there a step 4? Is it only there so I check if kindle shows up or do I have to update its driver so there is no yellow triangle anymore?
EDIT:
So I managed to get it running. What I did is I added the "0x18D1" as in step 3 but after that I opened my device manager and by clicking on kindle (that has yellow triangle next to it) I updated its driver. I chose the location of adb_usb.ini that I edited. After that I ran Kindle Fire Utility and chose option 1 (Boot mode) and in the following menu I tried all of the options. In the option 3 (Recovery) it did something and now every time I boot kindle it goes to the yellow triangle but by pressing power button once it starts normal boot.
Ok, but still I would like to get it completely back to normal if possible so if anyone can help, thanks
It is supposed to show the recovery triangle EVERY time you reboot.
Just don't touch anything and it will continue to boot on its own to the OS.
The only time you should do something different is if you want to boot into recovery, then you push the power button until it turns orange and let go, it will boot into the TWRP recovery.
You really shouldn't need reboot the machine often. I do it maybe once every couple days at most.
nuttmeg said:
how can you remove TWRP from kindle fire if it's possible, whatit to boot likeif i just got itout of the box, which i did today when i recieveit.
Thanks.
Click to expand...
Click to collapse
To remove TWRP and go back to the stock Amazon ROM, all you have to do is flash the stock Amazon firmware. Use Kindle Fire Utility v.7 to download the stock update.zip, copy the file to the SD card, boot into recovery, and install it.
---------- Post added at 05:30 PM ---------- Previous post was at 05:25 PM ----------
kw1999 said:
Hello,
I just received a Kindle Fire and decided to root and install Cyanogenmod. I found a tutorial which I thought looked pretty straightforward on Lilputing. I downloaded the Kindle Fire Utility and followed both the utility and the article told me to do. After installing TWRP 2.0, disaster. I rebooted the device and the Kindle read, "press power button for recovery," and showed a yellow triangle with a fire icon in the middle. I pressed the power button, and nothing happened. At this point, I rebooted. The device would not get passed this screen, and my PC would not recognize the Kindle. I presume I bricked my device, however (as I do not have any experience in this field) I honestly have no idea what I did, nor do I know where to go next. Any suggestions? Please help!
Click to expand...
Click to collapse
I had this same problem a few days ago. I fixed it by going into Device Manager, finding the device called "kindle" (it had a yellow triangle next to it) and manually installing the ADB drivers. You can't search for drivers automatically, you have to manually specify the "ADB Composite Interface" or something to that effect.
I have also had this issue, thought it was because I was using a 64 bit windows 7 system.
I had previously installed cyanogenmod 7 using destructions from this forum, and I have also done something similar with my Galaxy S2 (I mention this, because this may be why the drivers havent worked?)
Anyway, I added the line above, then rebooted my PC (twice), and then unplugged my kindle fire and rebooted. I then plugged it in to the PC and it came up as "kindle" in device manager, but had the exclamation mark warning. I clicked update driver and found the updated usb.ini file. Windows did its stuff and then it appears as Android bridge device.
The kindle wa still stuck at the yellow triangle, but selection the fastboot menu option 1, then boot normal and it worked a charm.
Persevere and dont give up!
Thanks to the great advice on this forum, everything becomes easy, once you have found the right posts!
bikeracer4487 said:
Try this:
1) Download v6 of the Kindle Fire Utility from here. (The forum thread can be found here)
2) Extract the files into a folder anywhere (but remember where, obviously)
3) Go into the folder, then into 'drivers' and open up adb_usb.ini in a text editor and add "0x18D1" (without the quotes) on a line underneath "0x1949"
4) Open up Device Manager and find "kindle". It should have a yellow triangle near it.
5) Download fastboot.exe from here
6) Open up command prompt and navigate to wherever you saved fastboot to.
7) Run the command "fastboot oem idme bootmode 4000"
8) Power off your device by holding down the power button for ~10 seconds and turn it back on, and this time don't hit the power button to go into TWRP. It should move past the yellow triangle after a few seconds and boot into Kindle. Hope this helps!
Click to expand...
Click to collapse
The page wont load to download that version of KFU. Also everytime I try to download fastboot I get an error saying AdbWinApi.dll is missing from my computer. Where do I find that?
http://forum.xda-developers.com/showthread.php?t=1399889
and the missing file is in kfu
krelvinaz said:
It is supposed to show the recovery triangle EVERY time you reboot.
Click to expand...
Click to collapse
That can't be right, surely?
bikeracer4487 said:
Try this:
1) Download v6 of the Kindle Fire Utility from here. (The forum thread can be found here)
2) Extract the files into a folder anywhere (but remember where, obviously)
3) Go into the folder, then into 'drivers' and open up adb_usb.ini in a text editor and add "0x18D1" (without the quotes) on a line underneath "0x1949"
4) Open up Device Manager and find "kindle". It should have a yellow triangle near it.
5) Download fastboot.exe from here
6) Open up command prompt and navigate to wherever you saved fastboot to.
7) Run the command "fastboot oem idme bootmode 4000"
8) Power off your device by holding down the power button for ~10 seconds and turn it back on, and this time don't hit the power button to go into TWRP. It should move past the yellow triangle after a few seconds and boot into Kindle. Hope this helps!
Click to expand...
Click to collapse
Kindle is not recognized? Please help?
Uninstall/reinstall device drivers and try again.
Sent from my Amazon Kindle Fire using xda premium
Wired0980 said:
I had same problem. Kept booting to "press power button for recovery" but never went to recovery. I had to download and install FireFireFire manually after i installed twrp. Now works great. Just power off then hold power button in for few seconds (until it turns orange) when powering back on, release, then there's twrp.
Click to expand...
Click to collapse
I am having this problem and have gone back to install FireFireFire manually but I still get stuck at "press power button for recovery". If I leave it alone it eventually boots as normal. If I press and hold the power button for a few seconds, it turns orange but never does anything. Any ideas?
I should mention that I'm running Ubuntu Linux - no access to Windows so KFU is not an option. My Fire is at version 6.3 and I've been roughly following the guide here: http://forum.xda-developers.com/showthread.php?t=1568340
i have been following multiple threads about unbricking , rooting and installing CWM on my Su640 but unfortunately, I have failed every time.
I am not new to rooting / unbricking, I have been doing it for over an year with multiple HTC phones but SU640 is becoming a nightmare.
I have followed this guide :
http://forum.xda-developers.com/showthread.php?t=1784709
Which has come closest to giving me GB + Root + CWM. But the steps after that , moving to AT&T stock ROM, always stucks on LG logo.
Guide me please.
salimbaba said:
i have been following multiple threads about unbricking , rooting and installing CWM on my Su640 but unfortunately, I have failed every time.
I am not new to rooting / unbricking, I have been doing it for over an year with multiple HTC phones but SU640 is becoming a nightmare.
I have followed this guide :
http://forum.xda-developers.com/showthread.php?t=1784709
Which has come closest to giving me GB + Root + CWM. But the steps after that , moving to AT&T stock ROM, always stucks on LG logo.
Guide me please.
Click to expand...
Click to collapse
That guide works. Are you performing a factory reset after flashing the AT&T stock ROM?
So I gave it another try...
and here are few ambiguities
there is a step in ROOT.bat that says
"Rebooting device"
"Press any key to continue"
and then without me pressing any key, it continues and gives me
"error: device not found"
followed by
"if the above text is "# exit" then you then you have rooted.
If not, please retry this .bat script."
No matter how many times I try running the bat script, i get the same results.
So assuming I am rooted despite the error msg, i confirmed via adb shell , su .
I carried on with AT&T stock image part.
still stuck on LG logo after hard-reset, for 20 mins.
what am i doing wrong ?
P.S : when the device is stuck at LG logo, I can still see it recognized in Device Manager, but no ADB support
lordcheeto03 said:
That guide works. Are you performing a factory reset after flashing the AT&T stock ROM?
Click to expand...
Click to collapse
after following the guide again,
This time I am stuck in a kind of boot loop after Hard-reset ... LG logo appears, then disappears, appears again , disappears again... and this continues.
salimbaba said:
So I gave it another try...
and here are few ambiguities
there is a step in ROOT.bat that says
"Rebooting device"
"Press any key to continue"
and then without me pressing any key, it continues and gives me
"error: device not found"
followed by
"if the above text is "# exit" then you then you have rooted.
If not, please retry this .bat script."
No matter how many times I try running the bat script, i get the same results.
So assuming I am rooted despite the error msg, i confirmed via adb shell , su .
I carried on with AT&T stock image part.
still stuck on LG logo after hard-reset, for 20 mins.
what am i doing wrong ?
P.S : when the device is stuck at LG logo, I can still see it recognized in Device Manager, but no ADB support
Click to expand...
Click to collapse
Each time it says "Rebooting device: press any key to continue" I believe you need to wait for it to reboot before pressing anything; at least that's the safest. It's using adb to do what it's doing, and there's a window of time upon reboot that adb isn't accessible: namely when the LG boot logo is shown. Once the carrier logo is shown, adb should be accessible, but I personally still wait until the boot completes. It's confusing, I know. It should go through that 3 times; waiting for the device to fully boot before pressing "any key". If you failed to gain root on that step, it's possible that is why you are experiencing the boot loop. That last line, "If the above text is #" or whatever, it should be something like root=0 or something. It tells you what to expect if you are rooted, I just don't remember exactly what it says. Either way, if it doesn't show what it tells you that you will see if you are rooted, then you aren't rooted. Also, if it's doing that through adb shell, then the exit command would show # exit if you are rooted, $ exit if you aren't; as # denotes you are running as root, $ shows a regular user.
lordcheeto03 said:
Each time it says "Rebooting device: press any key to continue" I believe you need to wait for it to reboot before pressing anything; at least that's the safest. It's using adb to do what it's doing, and there's a window of time upon reboot that adb isn't accessible: namely when the LG boot logo is shown. Once the carrier logo is shown, adb should be accessible, but I personally still wait until the boot completes. It's confusing, I know. It should go through that 3 times; waiting for the device to fully boot before pressing "any key". If you failed to gain root on that step, it's possible that is why you are experiencing the boot loop. That last line, "If the above text is #" or whatever, it should be something like root=0 or something. It tells you what to expect if you are rooted, I just don't remember exactly what it says. Either way, if it doesn't show what it tells you that you will see if you are rooted, then you aren't rooted. Also, if it's doing that through adb shell, then the exit command would show # exit if you are rooted, $ exit if you aren't; as # denotes you are running as root, $ shows a regular user.
Click to expand...
Click to collapse
ok, so I have successfully been rooted, what was I doing wrong ?
This :
when it says "sleep 20" , then you have to turn on wifi , make sure its been turned on , then turn it off.
rest of the process remains same.
After that, I say the "# exit" tag means I am properly rooted now. So i flashed the given image files in exact order ... "dd if= ...." commands.
rebooted ... hard factory reset... and now I am stuck on LG logo , which seems like i am rebooting over n over again :I
ok so i gave it another go, followed exactly same procedure, this time i am stuck on "rethink possible" animation screen -_-
Hi!
Is it normal to lose the ability to get into fastboot via software commands after installing CM10.1? I've tried SU and reboot bootloader - just reboots and stops at the blue KindleFire logo of TWRP. I've tried the fastboot command with the Kindle Fire turned off and disconnected and then plugging it in, and I think that still hangs at the TWRP logo (if I remember correctly). I've tried setting bootmode to 4009 using IDME, that doesn't seem to do anything.
I won't be back from military deployment for a few days, so I don't have my new factory cable to try yet. Just wondering if this is normal, and if not what can I do to fix it?
Thank you in advance,
John
NavyLCDR said:
Hi!
Is it normal to lose the ability to get into fastboot via software commands after installing CM10.1? I've tried SU and reboot bootloader - just reboots and stops at the blue KindleFire logo of TWRP. I've tried the fastboot command with the Kindle Fire turned off and disconnected and then plugging it in, and I think that still hangs at the TWRP logo (if I remember correctly). I've tried setting bootmode to 4009 using IDME, that doesn't seem to do anything.
I won't be back from military deployment for a few days, so I don't have my new factory cable to try yet. Just wondering if this is normal, and if not what can I do to fix it?
Thank you in advance,
John
Click to expand...
Click to collapse
Can it boot into TWRP?
If it can
Code:
adb reboot bootloader
This should get you into fastboot
EDIT:
I so misread the question...so you are stuck at the blue KindFire boot screen and not the TWRP boot screen right?
Thank you for your reply! Now that I have my Kindle in front of me this time:
1st: I have CM 10.2-20131015.UNOFFICIAL-otter2 loaded. Kernel is 3.0.72+. Everything works normal, and I love it, except can't get into fastboot.
Using Terminal Emulator I type in su and get the "[email protected]:/ #" prompt, so I know I have root.
I type reboot bootloader and something appears quickly in response in the terminal window that I can't read because the Kindle reboots immediately. I captured the text to a txt file and what appears is:
Reading idme data ...
Setting bootmode to 7
Writing new vars to temp area
It shows the white and orange KindleFire logo for a brief moment and then black screen. The Kindle appears to turn itself off after the brief appearance of the KindleFire white and orange logo.
The same thing happens if I do reboot bootloader using adb shell.
I can get into TWRP the normal way by pressing the power button at boot time.
I won't have access to my factory cable for a few more days, so so don't know if that works or not.
NavyLCDR said:
Thank you for your reply! Now that I have my Kindle in front of me this time:
1st: I have CM 10.2-20131015.UNOFFICIAL-otter2 loaded. Kernel is 3.0.72+. Everything works normal, and I love it, except can't get into fastboot.
Using Terminal Emulator I type in su and get the "[email protected]:/ #" prompt, so I know I have root.
I type reboot bootloader and something appears quickly in response in the terminal window that I can't read because the Kindle reboots immediately. I captured the text to a txt file and what appears is:
Reading idme data ...
Setting bootmode to 7
Writing new vars to temp area
It shows the white and orange KindleFire logo for a brief moment and then black screen. The Kindle appears to turn itself off after the brief appearance of the KindleFire white and orange logo.
The same thing happens if I do reboot bootloader using adb shell.
I can get into TWRP the normal way by pressing the power button at boot time.
I won't have access to my factory cable for a few more days, so so don't know if that works or not.
Click to expand...
Click to collapse
Make sure to turn ADB on and enable developer options by tapping "build" six times. Now plug your kF2 into a USB port and open a command prompt and type "adb reboot bootloader" with no quotes. You should enter fastboot mode. You should be able to just open a command prompt and type "fastboot" (no tablet plugged in) and see some lines of data which lets you know the path is set right.
LinearEquation said:
Make sure to turn ADB on and enable developer options by tapping "build" six times. Now plug your kF2 into a USB port and open a command prompt and type "adb reboot bootloader" with no quotes. You should enter fastboot mode. You should be able to just open a command prompt and type "fastboot" (no tablet plugged in) and see some lines of data which lets you know the path is set right.
Click to expand...
Click to collapse
adb reboot bootloader and adb reboot recovery both do the same thing - the Kindle reboots, I get the white and orange KindleFire logo for a second and it turns itself off. Press the power button and all is normal. I can get into TWRP by pressing the power key when the blue and white Kindle Fire logo is up.
NavyLCDR said:
adb reboot bootloader and adb reboot recovery both do the same thing - the Kindle reboots, I get the white and orange KindleFire logo for a second and it turns itself off. Press the power button and all is normal. I can get into TWRP by pressing the power key when the blue and white Kindle Fire logo is up.
Click to expand...
Click to collapse
No, they are not the same thing. One reboots into the bootloader and the other reboots into recovery. My comment had nothing to do with testing a reboot and everything to see if you can enter fastboot mode.
Since you have now stated you can enter TWRP, use this tutorial to push a ROM onto TWRP and then just flash it from there. http://forum.xda-developers.com/showthread.php?t=2459498
LinearEquation,
I know that adb reboot bootloader and adb reboot recovery are not the same commands and I know that they are not SUPPOSED to do the same thing. HOWEVER, on MY Kindle both commands ARE doing the same thing. And that is why I know something is wrong. Both commands on MY Kindle ARE having the same result: the Kindle reboots, I get the white and orange KindleFire logo for a second and it turns off.
Why would I want to reinstall a ROM from TWRP when I have a ROM installed? Once I press the power button, if I let it go it boots into CM 10.2 just fine or I can boot into TWRP by pressing the power button at the right time. I cannot reboot in TWRP or fastboot using software commands, and I don't even know if it is supposed to be that way, or if it is a problem.
I did not (and still don't) know if it is normal for the only way to get into fastboot is with a cable after CM 10.2 is installed (and I don't know if I can get into fastboot that way for a few more days), or if I need to reflash a bootloader file or which bootloader file I need to reflash.
I hope that clarified what my problem is.
I managed to block the url and prevented the update from happening, but the next screen says "Checking for updates" and simply just won't go any further.
hungrymr2 said:
I managed to block the url and prevented the update from happening, but the next screen says "Checking for updates" and simply just won't go any further.
Click to expand...
Click to collapse
Have you tried killing the internet connection at the right time? See this guide for info: http://www.aftvnews.com/how-to-complete-the-fire-tv-initial-setup-without-updating/
AFTVnews.com said:
Have you tried killing the internet connection at the right time? See this guide for info: http://www.aftvnews.com/how-to-complete-the-fire-tv-initial-setup-without-updating/
Click to expand...
Click to collapse
Thanks, it took a lot of retries to get past that screen. I found out that I'm running on "51.1.1.0" and I got the first root, superuser (shell + beatbox), and beatbox to install. . My next problem is that I'm stuck on the white Amazon logo(loading screen) after "adb reboot recovery".
When I first tried to push the update.zip to /cache, it would say access denied. Then I proceeded to push recovery.img to /sdcard/ instead. After I repeated the entire process, it no longer says access denied when I push update.zip, however, after "adb reboot recovery" it would simply restart and hang at the first logo screen. I'm not sure what I did wrong. If pull the plug and start it back up, it would still say version 51.1.1.0
hungrymr2 said:
Thanks, it took a lot of retries to get past that screen. I found out that I'm running on "51.1.1.0" and I got the first root, superuser (shell + beatbox), and beatbox to install. . My next problem is that I'm stuck on the white Amazon logo(loading screen) after "adb reboot recovery".
When I first tried to push the update.zip to /cache, it would say access denied. Then I proceeded to push recovery.img to /sdcard/ instead. After I repeated the entire process, it no longer says access denied when I push update.zip, however, after "adb reboot recovery" it would simply restart and hang at the first logo screen. I'm not sure what I did wrong. If pull the plug and start it back up, it would still say version 51.1.1.0
Click to expand...
Click to collapse
read this, your box most probably has an updated partition that is blocking downgrades,
http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/
bula1ca said:
read this, your box most probably has an updated partition that is blocking downgrades,
http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/
Click to expand...
Click to collapse
Thanks, that blocking downgrade partition and also downloading the wrong recovery.img didn't help too much. XD
I got it all sorted out. thanks.
Could I plug the stick into my computer and have it update that way - then plug it back into my TV?