Kindle Fire HD 8.9. Was able to root and install custom Rom. Working fine, until wife (I know) tried to do a factory reset. Now when it powers up, I get the gold Kindle fire logo... then the blue kindle fire logo, then the strip across the top of the screen indicating it is going to recovery, then the TEAMWIN screen.... then it continues to try to boot into recovery, but just stays on the TEAMWIN screen. Am I hard Booted? Any suggestions how I can recover?
You've TWRP installed, so I assume you have an unlocked bootloader?
Tried to re-install TWRP via adb again?
Which custom ROM did you install, and what kind of factory reset was done? Usually this should have been done from TWRP.
Cl4ncy said:
You've TWRP installed, so I assume you have an unlocked bootloader?
Tried to re-install TWRP via adb again?
Which custom ROM did you install, and what kind of factory reset was done? Usually this should have been done from TWRP.
Click to expand...
Click to collapse
Based on symptoms not sure @bprice46B has native twrp (flashed to recovery partition) as 'factory reset' followed by incomplete boot is characteristic of stock recovery. Thinking Safestrap although in v4 does not display teamwin splash screen. Not sure about v3. Just thinking out loud ...
Davey126 said:
Based on symptoms not sure @bprice46B has native twrp (flashed to recovery partition) as 'factory reset' followed by incomplete boot is characteristic of stock recovery. Thinking Safestrap although in v4 does not display teamwin splash screen. Not sure about v3. Just thinking out loud ...
Click to expand...
Click to collapse
I'm not exactly sure either, but AFAIR Safestrap just shows a Safestrap enabled screen, with a 10 seconds boot count down, and two buttons Recovery and Continue (Boot). The TWRP version it's actually based on is shown later in Safestrap though.
Well, we need some info here, Fire OS version, locked or unlocked bootloader, Safestrap or (real) TWRP?
I think device is hd 8.9 and this post in wrong forum.
ONYXis said:
I think device is hd 8.9 and this post in wrong forum.
Click to expand...
Click to collapse
Good call.
Related
Father wants JB on his TF201, I thought this shouldn't be difficult doing since I had a droid, and a galaxy nexus before and it was simple. He for some reason already had it unlocked, so that took out one step.
I flashed TWRP (http://teamw.in/project/twrp2/93) for ICS since he was still on ICS. Booted into Recovery, then flashed Energy (http://forum.xda-developers.com/showthread.php?t=1982156).
Now it just sits at the splash screen.
Afterwords I did flash or install nvflash so now it says AndroidRoot 9.4.3.20r01 in the top left when booting... but Not sure what that gets me at this point.
I can boot up into TWRP and re flash Energy but it still doesn't work. Wiped Cache / Wiped system. So what do I need to do to get this working now?
bump
dilutedq said:
Father wants JB on his TF201, I thought this shouldn't be difficult doing since I had a droid, and a galaxy nexus before and it was simple. He for some reason already had it unlocked, so that took out one step.
I flashed TWRP (http://teamw.in/project/twrp2/93) for ICS since he was still on ICS. Booted into Recovery, then flashed Energy (http://forum.xda-developers.com/showthread.php?t=1982156).
Now it just sits at the splash screen.
Afterwords I did flash or install nvflash so now it says AndroidRoot 9.4.3.20r01 in the top left when booting... but Not sure what that gets me at this point.
I can boot up into TWRP and re flash Energy but it still doesn't work. Wiped Cache / Wiped system. So what do I need to do to get this working now?
Click to expand...
Click to collapse
since you have ics bootloader (nvidia logo on bottom center of splash screen) you need to install a rom that has the jellybean bootloader. easiest way to do this is follow this post. After that you can install any jellybean rom that requires official bootloader.
http://forum.xda-developers.com/showpost.php?p=34938455&postcount=6212
I am a new Transformer Prime user, but not new to Android. My Prime is stuck on the initial "ASUS" splash screen (with NVIDIA logo).
I got my TFP yesterday and decided to put CM10 on it to see if it would fix the lag I was having (came with JB 4.1.1). Since it came with JB, I knew I couldn't use nvflash so I used the ASUS unlock tool which worked fine. I then downloaded TWRP 2.4.1 and flashed the JB blob file via fastboot.
Upon entering TWRP for the first time, everything seemed fine. I went in, did a backup (which I subsequently deleted by mistake) and wiped cache/dalvik/data/system and installed the official CM10 nightly. After flashing, I wiped cache/dalvik again and rebooted.
EDIT: So I flashed the Unofficial CM 10.1 here on XDA and it is now booting. So is the official CM 10 not for our devices with the JB BL?
Official CM10 nightlies are still made for the ICS bootloader, as you discovered. Until they update, you're better off downloading the unofficial builds here.
thefsfempire said:
I am a new Transformer Prime user, but not new to Android. My Prime is stuck on the initial "ASUS" splash screen (with NVIDIA logo).
I got my TFP yesterday and decided to put CM10 on it to see if it would fix the lag I was having (came with JB 4.1.1). Since it came with JB, I knew I couldn't use nvflash so I used the ASUS unlock tool which worked fine. I then downloaded TWRP 2.4.1 and flashed the JB blob file via fastboot.
Upon entering TWRP for the first time, everything seemed fine. I went in, did a backup (which I subsequently deleted by mistake) and wiped cache/dalvik/data/system and installed the official CM10 nightly. After flashing, I wiped cache/dalvik again and rebooted.
EDIT: So I flashed the Unofficial CM 10.1 here on XDA and it is now booting. So is the official CM 10 not for our devices with the JB BL?
Click to expand...
Click to collapse
I'm at the same screen, got there a lil different then you but along the same lines. I've switched out roms alot with no issues, but after flashing jellybean, i haven't been able to boot into recovery by power + vol down button. So i tried going into goo manager to boot into recovery and since then its just sitting at the first screen with this device is unlocked in the top left corner and nv in bottom left. When i hold the power button to reboot it, it just comes right back. Even when i let the battery die and try'ed it after that its just the same thing. Is there any hope out there for me?
foxhound08 said:
I'm at the same screen, got there a lil different then you but along the same lines. I've switched out roms alot with no issues, but after flashing jellybean, i haven't been able to boot into recovery by power + vol down button. So i tried going into goo manager to boot into recovery and since then its just sitting at the first screen with this device is unlocked in the top left corner and nv in bottom left. When i hold the power button to reboot it, it just comes right back. Even when i let the battery die and try'ed it after that its just the same thing. Is there any hope out there for me?
Click to expand...
Click to collapse
Can you access the stock recovery menu? If you can, you might be able to flash a custom recovery using fastboot.
Voyager2k said:
Can you access the stock recovery menu? If you can, you might be able to flash a custom recovery using fastboot.
Click to expand...
Click to collapse
No i can't access anything.
foxhound08 said:
No i can't access anything.
Click to expand...
Click to collapse
I am also stuck at this screen. I have access to nothing including adb, fastboot, recovery, bootloader, and everything else. All I did was use the asus bootloader unlock apk, fastboot flash recovery clockwork.img, boot back into android normally, and then I reboot into the bootloader wiped data, and now it is stuck.
dunngh said:
I am also stuck at this screen. I have access to nothing including adb, fastboot, recovery, bootloader, and everything else. All I did was use the asus bootloader unlock apk, fastboot flash recovery clockwork.img, boot back into android normally, and then I reboot into the bootloader wiped data, and now it is stuck.
Click to expand...
Click to collapse
Same here. I unlocked it and flashed CWM. For a while I used the tablet without any custom rom nor any problem, however it just stopped booting suddenly. I dont know what to do.
eec_ said:
Same here. I unlocked it and flashed CWM. For a while I used the tablet without any custom rom nor any problem, however it just stopped booting suddenly. I dont know what to do.
Click to expand...
Click to collapse
same here as well so at least you guys arent alone does show up as an apx device but not sure how useful that could be at the moment its just a paper weight just need someone to write an automated recovery from apx mode to flash the appropriate files if thats even possible
Exact same problem. Still no fix?
Just developed the same problem after installing Androwook2.2. Flashed the JB bootloader, then flashed the rom, after completing the initial Android setup the tablet started to download updates, which then froze. The screen stopped responding to any inputs, only the power and volume buttons did anything, but wouldn't restart it.
I hit the reset button with a pin which allowed me to enter recovery, which also didn't respond to screen touches, another reset button hit and there's now no USB connection in bootloader
Another restart and I can't get into bootloader either.
So no recovery or ADB = paperweight unless someone finds a solution
swatsbiz said:
Just developed the same problem after installing Androwook2.2. Flashed the JB bootloader, then flashed the rom, after completing the initial Android setup the tablet started to download updates, which then froze. The screen stopped responding to any inputs, only the power and volume buttons did anything, but wouldn't restart it.
I hit the reset button with a pin which allowed me to enter recovery, which also didn't respond to screen touches, another reset button hit and there's now no USB connection in bootloader
Another restart and I can't get into bootloader either.
So no recovery or ADB = paperweight unless someone finds a solution
Click to expand...
Click to collapse
Your problem was different to theirs and you have been fixed in the Androwook thread. Yours was caused by the pad firmware not installing properly the first time and freezing your screen and buttons.
I have the same problem...
hbhorat said:
Exact same problem. Still no fix?
Click to expand...
Click to collapse
any fixes to this ?
sraghav20 said:
any fixes to this ?
Click to expand...
Click to collapse
Me too.. looking for a fix on this with no luck so far
Q&A for [RECOVERY] TWRP Recovery 2.8.1.0 - Thor
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY] TWRP Recovery 2.8.1.0 - Thor. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Tried it on 13.3.2.4 with know dice. You have to hard reset a couple of times and then safestrap comes back up. Tried a few times with zero luck so I just flashed twrp2.7.1 and all is good again. Also made me post here because I have less than 10 posts.
Kudos!
Firstly - thanks very much to all people involved in this - especially vortox - excellent work!
Secondly, I've just flashed TWRP successfully on 13.3.0.5.
The only thing which seems a bit strange is that when starting TWRP, I have to wait until the HDX's display goes into power-saving mode (i. e. goes deeply black) and switch the display on again before the starting screen of TWRP can be seen & TWRP be used (before that point, the display black for a while, but not in power-saving mode).
Is this normal?
I have made a grave error and have no recovery.
Well watching this special day unfold I mistakenly lost my original backup recovery.img and after dd now have no recovery. What can I do to get a working stock recovery.img back onto /dev/block/mmcblk0p18. When I dd twrp I apparently wasn't ready and now I have no recovery. I am running the rollback 13.3.0.9 and still have root/safestrap.
Nevermind I followed this and fixed my stock recovery.
http://forum.xda-developers.com/showthread.php?t=2782159&page=20
Certainly no expert here, but can't you just flash the TWRP recovery via Rashr or Flashify while the OS is running...? Or do you just want to have the stock recovery image? If I'm misunderstanding your question - sorry.
nocmonkee said:
Well watching this special day unfold I mistakenly lost my original backup recovery.img and after dd now have no recovery. What can I do to get a working stock recovery.img back onto /dev/block/mmcblk0p18. When I dd twrp I apparently wasn't ready and now I have no recovery. I am running the rollback 13.3.0.9 and still have root/safestrap.
Click to expand...
Click to collapse
RiseT said:
Certainly no expert here, but can't you just flash the TWRP recovery via Rashr or Flashify while the OS is running...? Or do you just want to have the stock recovery image? If I'm misunderstanding your question - sorry.
Click to expand...
Click to collapse
Sure but it never would boot into recovery or it was booting into an unexploitable recovery. I hadn't fully downgraded it yet or something went wrong so I had no usable recovery. I couldn't use amazon's tools to fix it and I could properly install twrp, so after "Amazon Recovery" worked again I was able to boot into the rollback image and use amazon's own upgrade bin. "update-kindle-13.3.1.0_user_310079820.bin". Once it went through the Amazon upgrade process. I used the KFHDX Toolkit to root it, then I adb'd into it and then su'd to root and immediately dd'd the TWRP recovery and then did reboot recovery in adb and "TADA" I had working twrp recovery and was able to install the CM 11 and gapps.
I see. Great to hear that it's working now. As you've successfully installed TWRP & CM 11 now - could you confirm the above stated behaviour regarding the black screen? Additionally to TWRP, I've just installed CM as well; interestingly, the display is showing the same behaviour with CM as with TWRP (I can only see something after the display returned from power-saving mode). With Amazon stock recovery & ROM, this isn't the case, so it shouldn't be a hardware problem.
nocmonkee said:
Sure but it never would boot recovery. I hadn't fully downgraded it yet or something went wrong so I had no recovery. After "Amazon Recovery" worked again I was about to boot into the rollback image and use amazon's own upgrade bin. "update-kindle-13.3.1.0_user_310079820.bin". Once it rebooted I used the KFHDX Toolkit to root it, then I adb'd into it and then su'd to root and immediately dd'd the TWRP recovery and then did reboot recovery in adb and "TADA" I had working twrp recovery and was able to install the CM 11 and gapps.
Click to expand...
Click to collapse
RiseT said:
I see. Great to hear that it's working now. As you've successfully installed TWRP & CM 11 now - could you confirm the above stated behaviour regarding the black screen? Additionally to TWRP, I've just installed CM as well; interestingly, the display is showing the same behaviour with CM as with TWRP (I can only see something after the display returned from power-saving mode). With Amazon stock recovery & ROM, this isn't the case, so it shouldn't be a hardware problem.
Click to expand...
Click to collapse
I am not experiencing this black screen issue. I did though start from 3.2.4 and worked my way down to 3.1.0. CM boots quickly and is super responsive. When booting it flashes the all gray "kindle fire" for about 10-20 seconds before it boots into recovery or cm. Possibly you just aren't see that screen and are seeing black instead?
Thanks for the feedback!
I think I don't see the gray "Kindle Fire" for that long - so that's a possibility. Btw, I also don't see the Cyanogenmod boot logo I'm used to on mobile phones. I guess I have to investigate this further. Wondering if the fact that I started with a rather "antique" stock firmware could have something to do with it, but I would guess that this is not possible as all that old stuff is wiped away when installing TWRP & the CM rom.
Edit: The gray "Kindle Fire" logo shows up for circa 4 seconds.
nocmonkee said:
I am not experiencing this black screen issue. I did though start from 3.2.4 and worked my way down to 3.1.0. CM boots quickly and is super responsive. When booting it flashes the all gray "kindle fire" for about 20 seconds before it boots into recovery or cm. Possibly you just aren't see that screen and are seeing black instead?
Click to expand...
Click to collapse
Thanks to everyone for their hard work bringing us TWRP for the Kindle HDX models.
vortox said:
It's not working on 3.2.4, but works atleast at 3.1.0. I didn't test other versions.
Click to expand...
Click to collapse
What's the best way to downgrade a rooted/safestrapped 13.3.2.4 stock-rom to a lower version?
well
Deathcrow said:
Thanks to everyone for their hard work bringing us TWRP for the Kindle HDX models.
What's the best way to downgrade a rooted/safestrapped 13.3.2.4 stock-rom to a lower version?
Click to expand...
Click to collapse
go back to development and start reading. To have somebody here we explain everything would just be ridiculous there is a thread or several threads on rolling back..from different versions to different versions I believe in development there is even a thread started now for exactly your question. And it was started yesterday or the day before.
jimyv said:
go back to development and start reading. To have somebody here we explain everything would just be ridiculous there is a thread or several threads on rolling back..from different versions to different versions I believe in development there is even a thread started now for exactly your question. And it was started yesterday or the day before.
Click to expand...
Click to collapse
Oh yeah, I completely missed that. Thanks for pointing it out.
if i install this twrp, what would happen to my safetrap recovery and can i even access it after and use the backups i saved using safetrap on twrp?
well
latedays101 said:
if i install this twrp, what would happen to my safetrap recovery and can i even access it after and use the backups i saved using safetrap on twrp?
Click to expand...
Click to collapse
yes you will still be able to access your safestrap. And yes your safestrap backups will be compatible with your new recovery. But keep in mind that your backups from safestrap will not contain a kernel and you will have to match one up with it..
jimyv said:
yes you will still be able to access your safestrap. And yes your safestrap backups will be compatible with your new recovery. But keep in mind that your backups from safestrap will not contain a kernel and you will have to match one up with it..
Click to expand...
Click to collapse
thanks, i just installed the twrp recovery successfully, how do i boot into safetrap again if i want to use it?
lol
latedays101 said:
thanks, i just installed the twrp recovery successfully, how do i boot into safetrap again if i want to use it?
Click to expand...
Click to collapse
it probably took you longer to ask me that question then it did for you to figure it out.
if not just simply reboot it and tap recovery on the splash screen as it boots just like always if you want access to it from your system just install the APK..personally I wouldn't mess with itother than to get into the backups from my new recovery to restore data....
jimyv said:
it probably took you longer to ask me that question then it did for you to figure it out.
if not just simply reboot it and tap recovery on the splash screen as it boots just like always if you want access to it from your system just install the APK..personally I wouldn't mess with itother than to get into the backups from my new recovery to restore data....
Click to expand...
Click to collapse
yeah i tried that but seems like its just boots into twrp not safetrap and thought something weird is happening and even if i tried installing the apk and press into recovery, it just boots into the cm rom.
well
latedays101 said:
yeah i tried that but seems like its just boots into twrp not safetrap and thought something weird is happening and even if i tried installing the apk and press into recovery, it just boots into the cm rom.
Click to expand...
Click to collapse
did you open up the app and see if the recovery is installed?. Like I said I would not mess with it personally. safestrap is a version of TRWP.. but is installed in the system and may have compatibility issues with your cm 11 etc other ROM that you may install with your new true recovery.
besides if you flash cm through your new recovery nothing you can install through safestrap at this moment would be compatible with the kernel ..besides a backup of that same rom. you would have left there. Unless you flash a renamed bin file to get compatible kernel for whatever stock backup you were trying to restore from safestrap
jimyv said:
did you open up the app and see if the recovery is installed?. Like I said I would not mess with it personally. safestrap is a version of TRWP.. but is installed in the system and may have compatibility issues with your cm 11 etc other ROM that you may install with your new true recovery.
besides if you flash cm through your new recovery nothing you can install through safestrap at this moment would be compatible with the kernel ..besides a backup of that same rom. you would have left there. Unless you flash a renamed bin file to get compatible kernel for whatever stock backup you were trying to restore from safestrap
Click to expand...
Click to collapse
Hm damn i just wanted to go back into safestrap so i can delete all my rom slots that i created that are wasted space seems like i kind of screwed right now for not backing the previous safetrap recovery i guess, unless someone share a back image of safetrap that i can flash?
well .
latedays101 said:
Hm damn i just wanted to go back into safestrap so i can delete all my rom slots that i created that are wasted space seems like i kind of screwed right now for not backing the previous safetrap recovery i guess, unless someone share a back image of safetrap that i can flash?
Click to expand...
Click to collapse
you were supposed to do that somewhere in the rolling back effort just before you do your new recovery. You were supposed to do it through a stock system and stock recovery to completely wipe the device.
you can still do it in your new recovery after you back your stuff up to your PC just go into wipe options and choose the option on the right wipe complete data.but that location of that folder is someplace I'm trying to find it for you
---------- Post added at 09:31 PM ---------- Previous post was at 09:23 PM ----------
jimyv said:
you were supposed to do that somewhere in the rolling back effort just before you do your new recovery. You were supposed to do it through a stock system and stock recovery to completely wipe the device.
you can still do it in your new recovery after you back your stuff up to your PC just go into wipe options and choose the option on the right wipe complete data.but that location of that folder is someplace I'm trying to find it for you
Click to expand...
Click to collapse
Try \mnt\shell\emulated\ then delete that folder named safestrap. That is where it is on my Apollo anyway
I think I finally bricked my device. I'm guilty. Just want to keep track of everything I did and share how it's bricked.
1. Everything starts because the 4g LTE stopped working. The device starts to give me "Invalid SIM" message no matter how I try. Same message with either T-mobile sim card or the stock AT&T sim card. At this time, the device is on TWRP 2.8.1.0 with Thor Gapps Rom ( 13.3.2.4 ).
2. Thinking it might be a ROM issue, I restored 13.3.2.3.2. Same error message: Invalid SIM.
3. Thinking to restore everything stock before returning it to amazon, I flash stock recovery.img to overwrite TWRP and restored 13.3.2.6 backed-up with safestrap. System starts up but has some issue: it always goes back to selecting language page.
4. Flashed update-kindle-13.4.5.2_user_452004120-twrp.zip to stock slot with safestrap in hope of fixing everything. Now system stalls at the white "Kindle fire" screen.
I know that zip is for twrp, but I thought twrp can take backup made with safestrap, why not the other way around?! Well, I'm unlucky this time. One shall never touch stock slot with safestrap. I think I should have used the official update-kindle-13.4.5.2_user_452004220.bin and update through Device-update menu. Oh well.
Any way I can still play with this device before it set off for amazon?
In
shadowcliffs said:
I think I finally bricked my device. I'm guilty. Just want to keep track of everything I did and share how it's bricked.
1. Everything starts because the 4g LTE stopped working. The device starts to give me "Invalid SIM" message no matter how I try. Same message with either T-mobile sim card or the stock AT&T sim card. At this time, the device is on TWRP 2.8.1.0 with Thor Gapps Rom ( 13.3.2.4 ).
2. Thinking it might be a ROM issue, I restored 13.3.2.3.2. Same error message: Invalid SIM.
3. Thinking to restore everything stock before returning it to amazon, I flash stock recovery.img to overwrite TWRP and restored 13.3.2.6 backed-up with safestrap. System starts up but has some issue: it always goes back to selecting language page.
4. Flashed update-kindle-13.4.5.2_user_452004120-twrp.zip to stock slot with safestrap in hope of fixing everything. Now system stalls at the white "Kindle fire" screen.
I know that zip is for twrp, but I thought twrp can take backup made with safestrap, why not the other way around?! Well, I'm unlucky this time. One shall never touch stock slot with safestrap. I think I should have used the official update-kindle-13.4.5.2_user_452004220.bin and update through Device-update menu. Oh well.
Any way I can still play with this device before it set off for amazon?
Click to expand...
Click to collapse
Did you already try just holding onto the power button for over 20sec , to force a hard reset and get back into RECOVERY
the rest I'm not sure about you say you are on Thor gapps? with our new 2. 8. 1. 0?
did he make that compatible? I didn't realize Thor gapps was compatible
and what are you even doing with the update .5.2 ?that is the KitKat update and is completely incompatible with safestrap or older kernels so I am really confused on what you have stated in above post
or do you have that TRW P recovery flashed and somehow using safestrap also?
looks like to me you have flashed everything but the right thing but then again it's really hard to tell what you have going on here.
Holding the power button for over 20 sec does me nothing. I can enter "Kindle Fire System Recovery" the same way I entry twrp though by holding power and volume up during booting. There are two options there:
Reboot your Kindle
Reset to Facotry Defaults
I tried both and none helped me to boot into system.
I hate it that HDX is not like Samsung Galaxy phones which have a true recovery mode that can flash file, or a download mode that allows access via adb.
I think the reason that my hdx is bricked are:
1. First, I overwrote twrp with stock recovery 13.3.4 (because I want to restore to stock mode for return). Otherwise if I can still enter twrp, I will be saved.
2. Second, the file I flashed to stock slot with safestrap, update-kindle-13.4.5.2_user_452004120-twrp.zip, is made to boot with twrp. I guess it doesn't go well with the stock recovery 13.3.4.
jimyv said:
InDid you already try just holding onto the power button for over 20sec , to force a hard reset and get back into RECOVERY
the rest I'm not sure about you say you are on Thor gapps? with our new 2. 8. 1. 0?
did he make that compatible? I didn't realize Thor gapps was compatible
and what are you even doing with the update .5.2 ?that is the KitKat update and is completely incompatible with safestrap or older kernels so I am really confused on what you have stated in above post
or do you have that TRW P recovery flashed and somehow using safestrap also?
looks like to me you have flashed everything but the right thing but then again it's really hard to tell what you have going on here.
Click to expand...
Click to collapse
So here's what happened: I had TWRP and HDX Nexus ROM successfully installed for a while, but I decided I wanted to go back to Fire OS and update to the newest version. I used TWRP to flash the stock backup I had saved, and then I used the KFHDX Tool to re-enable OTA updates. I got the OTA update to .3.2.5, and when the system rebooted it booted into TWRP automatically to flash the update. That kinda surprised me, since I thought doing an OTA update would wipe out any custom recovery, but I guess not. The Kindle booted and completed the .3.2.5 installation, then downloaded the .4.1.1 file. At this point it tried to reboot but hung on the grey Kindle Fire logo. I held the power button to restart it and it booted normally, but the update was unsuccessful. I tried it a couple more times for good measure, with the same result each time. I tried following the instructions here to downgrade to .3.1.0, but it said it couldn't validate the update file. I tried doing a factory reset, but it hung on the grey Kindle logo and was unsuccessful.
Basically, I think my recovery got messed up. I tried the adb reboot recovery command from my computer and it caused the Kindle to hang on the grey logo, so I'm guessing that's what's causing my issues. Not sure where to go from here.
iNTRCPT4lyfe said:
So here's what happened: I had TWRP and HDX Nexus ROM successfully installed for a while, but I decided I wanted to go back to Fire OS and update to the newest version. I used TWRP to flash the stock backup I had saved, and then I used the KFHDX Tool to re-enable OTA updates. I got the OTA update to .3.2.5, and when the system rebooted it booted into TWRP automatically to flash the update. That kinda surprised me, since I thought doing an OTA update would wipe out any custom recovery, but I guess not. The Kindle booted and completed the .3.2.5 installation, then downloaded the .4.1.1 file. At this point it tried to reboot but hung on the grey Kindle Fire logo. I held the power button to restart it and it booted normally, but the update was unsuccessful. I tried it a couple more times for good measure, with the same result each time. I tried following the instructions here to downgrade to .3.1.0, but it said it couldn't validate the update file. I tried doing a factory reset, but it hung on the grey Kindle logo and was unsuccessful.
Basically, I think my recovery got messed up. I tried the adb reboot recovery command from my computer and it caused the Kindle to hang on the grey logo, so I'm guessing that's what's causing my issues. Not sure where to go from here.
Click to expand...
Click to collapse
If you have a thor (7" HDX) try flashing this recovery. It's from stock 3.2.6 but proven to be compatible with 3.2.5. You can use Flashify to install the recovery image. Note there's always some risk messing with recovery. Also assuming you can boot into 3.2.5 and are not stuck at the grey Kindle logo.
Thanks, that worked great. Now that the bootloader is unlocked, I got cold feet about going down the OTA path anyway. I was able to successfully roll back to .3.1.1 after I flashed the .3.2.6 recovery.
iNTRCPT4lyfe said:
Thanks, that worked great. Now that the bootloader is unlocked, I got cold feet about going down the OTA path anyway. I was able to successfully roll back to .3.1.1 after I flashed the .3.2.6 recovery.
Click to expand...
Click to collapse
Thanks for the update! Glad it worked out.