It's been a long time. About one-two years ago, I flashed Slim.LP on my Amazon Fire 5.1.1 device and everything was great. Then I decided to play with the "Layers" app. I found a layer, applied it, then restarted - but my tablet couldn't start because it was now in a bootloop. I guess the "Layers" app was broken or something. Anyways, back then, I scoured the forums looking for a fix to my doomed device; but the search was in vain. Now, in 2016. I've decided to give it a go again. Does anyone know of a way to help me? The tablet can boot into fastboot (==>FASTBOOT) normally, but as for the recovery, the tablet hangs on the "Amazon" logo. Please reply if you think you can help!
Bump...
iifrost said:
Bump...
Click to expand...
Click to collapse
No (stock) recovery = no solution. Sorry.
(unless you are exceptionally fortunate and own a device with the original 5.01 bootloader which can boot a twrp image)
Related
my kindle fire hd is caught in a bootloop with the only options being to reboot it or reset it to factory defaults. neither fixes it.
please help, it'd be greatly appreciated!
neut401 said:
my kindle fire hd is caught in a bootloop with the only options being to reboot it or reset it to factory defaults. neither fixes it.
please help, it'd be greatly appreciated!
Click to expand...
Click to collapse
I'm not sure really how to help, but if you can describe the last thing you were doing prior that will help people diagnose it. Were you rooted? Or trying to root? Did you try to modify any system files?
I have the same problem. I was rooted. I was trying to copy the vendor apk into system/ app folder. I think I accidently made copy of app folder, it said app copy then froze. I clicked system restore. did nothing.
Are you able to reach the system with adb shell at all? or not? If not, I think you are stuck sending it back to Amazon for repair/replacement. If you can, you should be able to use the same method you used to root to get /system RW again, and try to fix it up.
I don't know how to use ADB. I used the one click root method. My computer isn't recognizing the device when plugged in. Is there a step by step guide on how to fix it or will it be possible in the future?
If its not recognized, then its unlikely that adb will work. If I had a bricked device though...I would start reading and trying to get that working. If you really don't feel confident in messing around and trying to fix it, call Amazon and ask them to send you a new one.
neut401 said:
my kindle fire hd is caught in a bootloop with the only options being to reboot it or reset it to factory defaults. neither fixes it.
please help, it'd be greatly appreciated!
Click to expand...
Click to collapse
what do you do so that KFTT state in bootloop?
can you take screenshot? or take a picture?
I am having the same problem.
any luck fixing it?
Hi, I am in the same situation. Here in Spain we have the KFHD since 4 days ago.
I rooted it correctly via ADB. I installed google play and installed several app's apparently without difficulties. The issue came after putting the Go luncher HD apk on system\app. After that I rebooted the device and appeared the two luncher options. So everything ok. I was moving around my new luncher and everything was ok, but suddenly the device rebooted and I had the same issue here explained. Bootloop and no factory default possible. Of course just rebooting didn't solve it. I have to say that the last thing I was doing before the sudden reboot was modifying permissions from SU. Maybe it's related, so don't touch anything from there. ADB was not working any more so very few things to try...
Amazon accepted a replacement (I just said what happened but not why) and now I'm waiting a new one.
Hope this can help.
Regards,
If you're willing to do a little work, you can try this recovery method: http://forum.xda-developers.com/showthread.php?t=1951254. Personally, I would just send in the device to be replaced, and not tell them the exact circumstances of how the problem happened. Amazon's generally pretty good about returns and replacements while you're still within warranty.
I shouldn't have restored factory defaults
I am in the same issue
The main mistake I made was selecting "Reset to Factory Defaults"
This automatically turns off the debug mode and with it stopped any communication between my PC and the Kindle Fire HD 7". Even the Factory cable I bought for £3.19 didn't help. The driver shows like it is installed correctly and my Kindle shows Fastboot on the screen when connected, but there is no communication.
I only got it for Christmas and I've goosed it. I am now hoping Amazon will be sympathetic and believe that it just started looping itself without me modding it.
When you reach the fastboot screen unplug factory cable and insert the usb that came with it. Then check your drivers to make sure they are Installed properly. Then use system Img restore tool to restore, follow directions exactly
Sent from my KFTT using XDA Premium HD app
Hello All! I was messing around with App Quarantine and ended up bricking my KFHD (not sure what I did because I was still messing around with it.) My KFHD is rooted but I didn't install TWRP or any type of recovery program. Is there any way for me to unbrick this or am I stuck with a fancy paper weight?
Ichigo said:
You guys should check the 1st gen. Kindle Fire Forums for similar problems and solutions.
Android>iOS... Android FTW!
Click to expand...
Click to collapse
Lord NO! Any Kindle with the letters HD after Fire have nothing in common. Anything run to access the system or modify it will guarantee a permanent brick with NO WAY OUT.
[email protected]@dog said:
Lord NO! Any Kindle with the letters HD after Fire have nothing in common. Anything run to access the system or modify it will guarantee a permanent brick with NO WAY OUT.
Click to expand...
Click to collapse
Technically, the factory cable will still work, even if there are ways to know that you shouldn't do some things (like number 4 in the thread in my signature).
Ichigo said:
Way to bump an old thread.
Click to expand...
Click to collapse
It was sort of a failed attempt, so what the heck.
Alright from the get go. I am running 10.3.1. I rooted using a tutorial from this site, it was rather easy. It only took me like 25 minutes and then to add the Play store, another 25. I had it running perfectly fine with GO launcher and it was the way i liked it till I saw NEXT launcher and I wanted that instead. I had GO still running and being a noob I thought if I installed NEXT launcher that it would be able to be set by default when I was asked and that would be it. From what I can tell they were fighting for the kindle's affection and it was at a constant refresh directly after the install. I then soft reset it and I'm stuck at a kindle fire screen. The animation is very fast, with no delay between ending and beginning again. I tried today using the KFU to no avail. I also tried to reinstall the drivers, nada. my computer in device manager does read it, "other devices" Kindle" Uppercase "K". I've uninstalled and reinstalled. I cannot get the SDK to work on my computer. Even with the correct environment setup, nothing. I've viewed plenty of other fixes, none help my situation, not because I don't think they do, but because I've tried. When I KFU I get a Waiting for Device, nothing further happens (40 minute waiting period). I tried to Recovery boot and I tried to push TWRP, nothing. I'm at a loss. To be clear idk what fastboot is and I don't know how to "code" anything so anything help in detail, would be awesome, you guy are a great community and I wouldn't dream going any where else for expertise. Thanks for any help. Btw AMA and I'll try and best accommodate so I can fix this
rekindle said:
Alright from the get go. I am running 10.3.1. I rooted using a tutorial from this site, it was rather easy. It only took me like 25 minutes and then to add the Play store, another 25. I had it running perfectly fine with GO launcher and it was the way i liked it till I saw NEXT launcher and I wanted that instead. I had GO still running and being a noob I thought if I installed NEXT launcher that it would be able to be set by default when I was asked and that would be it. From what I can tell they were fighting for the kindle's affection and it was at a constant refresh directly after the install. I then soft reset it and I'm stuck at a kindle fire screen. The animation is very fast, with no delay between ending and beginning again. I tried today using the KFU to no avail. I also tried to reinstall the drivers, nada. my computer in device manager does read it, "other devices" Kindle" Uppercase "K". I've uninstalled and reinstalled. I cannot get the SDK to work on my computer. Even with the correct environment setup, nothing. I've viewed plenty of other fixes, none help my situation, not because I don't think they do, but because I've tried. When I KFU I get a Waiting for Device, nothing further happens (40 minute waiting period). I tried to Recovery boot and I tried to push TWRP, nothing. I'm at a loss. To be clear idk what fastboot is and I don't know how to "code" anything so anything help in detail, would be awesome, you guy are a great community and I wouldn't dream going any where else for expertise. Thanks for any help. Btw AMA and I'll try and best accommodate so I can fix this
Click to expand...
Click to collapse
Please post in the correct forum.
seokhun said:
Please post in the correct forum.
Click to expand...
Click to collapse
Which would be...Could you link me Sir/Ma'am?
rekindle said:
Which would be...Could you link me Sir/Ma'am?
Click to expand...
Click to collapse
http://forum.xda-developers.com/forumdisplay.php?f=2097. You said your device runs 10.3.1. The 7" KFHD runs 7.3.1 and the 8.9" runs 8.3.1, only the KF2 runs 10.3.1.
Hey everyone I totally screwed up my new KFHD and I would love some help. I tried to root it a couple days ago with the KFSOWI all in one tool and it seemed to work for a few minutes. SuperSU installed correctly and installed its binary but when I tried to use the root explorer in ES File Explorer it said that it failed so I opened up SuperSU again and it told me it needed to install the binary again as if it wasn't rooted. It failed to install it and Root Checker told me it wasn't rooted so I tried to re-root it with the same KFSOWI tool.
This is when it got messed up. The tool said it rooted successfully again but when I tried to boot it up normally (I had been using a factory cable to get into Fastboot) it got stuck on the Kindle Fire logo screen (the white one not the orange one). I thought maybe it was a problem with the root so I tried to unroot it with another tool and ever since then it briefly shows a red screen at boot and then stays on the Fastboot logo. I've tried holding the power button down for 20 seconds, restoring the firmware to stock (got an error about system.img saying that it wasn't a sparse file), and restoring to an older firmware. None of this has made any difference.
I read somewhere that the red screen is a sign of a missing bootloader but if that's true how do I get back to the stock bootloader? I had 11.3.2.2/7.4.8 installed before all this happened if that helps. I'm willing to try anything at this point. I would like to at least be able to use the Play Store but if I have to stick to stock FireOS I'll just endure it. If you have any questions ask away! Thank you all for your help.
pgautraud said:
Hey everyone I totally screwed up my new KFHD and I would love some help. I tried to root it a couple days ago with the KFSOWI all in one tool and it seemed to work for a few minutes. SuperSU installed correctly and installed its binary but when I tried to use the root explorer in ES File Explorer it said that it failed so I opened up SuperSU again and it told me it needed to install the binary again as if it wasn't rooted. It failed to install it and Root Checker told me it wasn't rooted so I tried to re-root it with the same KFSOWI tool.
This is when it got messed up. The tool said it rooted successfully again but when I tried to boot it up normally (I had been using a factory cable to get into Fastboot) it got stuck on the Kindle Fire logo screen (the white one not the orange one). I thought maybe it was a problem with the root so I tried to unroot it with another tool and ever since then it briefly shows a red screen at boot and then stays on the Fastboot logo. I've tried holding the power button down for 20 seconds, restoring the firmware to stock (got an error about system.img saying that it wasn't a sparse file), and restoring to an older firmware. None of this has made any difference.
I read somewhere that the red screen is a sign of a missing bootloader but if that's true how do I get back to the stock bootloader? I had 11.3.2.2/7.4.8 installed before all this happened if that helps. I'm willing to try anything at this point. I would like to at least be able to use the Play Store but if I have to stick to stock FireOS I'll just endure it. If you have any questions ask away! Thank you all for your help.
Click to expand...
Click to collapse
ok first ting i wanna ask is what do you mean 11.3.2/7.4.8, because 11.x.x is for teh 2013 and 7.x.x is for teh 2012 kindle. Also red screen doesnt mean you are missing the bootloader, if you were missing that the device wouldnt even turn on. That error you got when trying to restore the device is probably part of why its not working, probably need to fix that to fix the device, it never reflashed the system partition when it errored and said that the image was not sparse, which is a bit odd in itself considering how the method we use to fix it works.
stunts513 said:
ok first ting i wanna ask is what do you mean 11.3.2/7.4.8, because 11.x.x is for teh 2013 and 7.x.x is for teh 2012 kindle. Also red screen doesnt mean you are missing the bootloader, if you were missing that the device wouldnt even turn on. That error you got when trying to restore the device is probably part of why its not working, probably need to fix that to fix the device, it never reflashed the system partition when it errored and said that the image was not sparse, which is a bit odd in itself considering how the method we use to fix it works.
Click to expand...
Click to collapse
I have the 2013 version, I just bought it from Amazon two weeks ago and it said the firmware version was 11.3.2.2. I had said 7.4.8 because whenever I searched for a way to root 11.3.2.2 the most recent information I could find talked about 7.4.8 so I thought they were the same thing. So is there a way for me to sparse the system image? Or are there system images out there that are sparsed? If you have a tool that you prefer over others I would love to try it.
Try this, I think this was the thread I was looking for and if its the same one you posted a link to then my bad because I'm half asleep.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Try this, I think this was the thread I was looking for and if its the same one you posted a link to then my bad because I'm half asleep.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
What am I supposed to try?
Wow I was half asleep after all I didn't post the link... Lemme get my bearings and retrace my line of though.
Edit: here's the link I was intending on posting: http://forum.xda-developers.com/showthread.php?t=2685090
Weird thing is i remember copying the URL for the thread, Idk why I never pasted it.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Wow I was half asleep after all I didn't post the link... Lemme get my bearings and retrace my line of though.
Edit: here's the link I was intending on posting: http://forum.xda-developers.com/showthread.php?t=2685090
Weird thing is i remember copying the URL for the thread, Idk why I never pasted it.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thanks for the link! I actually tried the newest version of his tool and it works up until it says "waiting for boot..." I assume it means it's waiting for a normal boot but since I can't get it to boot past the Fastboot logo (even with a normal cable or no cable at all) it never gets any further. Any suggestions?
Sounds like the bootimg needs to be reflashed. Sometimes a bad bootimg causes it to kick into fastboot upon boot.
Sent from my Amazon Kindle Fire HD using Tapatalk
I have a kindle fire that used to belong to my brother and he had it rooted. I did a factory reset and upon registering the kindle it throws me into a language selection loop. I can still manage to get into apps, settings, etc.. if I click fast enough before the language selection pops up again. I'm assuming this is happening because it is rooted and I deleted files that were needed with the factory reset. I believe it's a 3rd gen kindle but I don't know how to be sure. Current version is 13.3.2.3.2_user_323001720 Build date Sunday, June 1, 2014. I prefer it to be unrooted for a fresh start but if it's easier to get past that error loop I'll take it. Can anyone help me with this please?
prisonmike1021 said:
I have a kindle fire that used to belong to my brother and he had it rooted. I did a factory reset and upon registering the kindle it throws me into a language selection loop. I can still manage to get into apps, settings, etc.. if I click fast enough before the language selection pops up again. I'm assuming this is happening because it is rooted and I deleted files that were needed with the factory reset. I believe it's a 3rd gen kindle but I don't know how to be sure. Current version is 13.3.2.3.2_user_323001720 Build date Sunday, June 1, 2014. I prefer it to be unrooted for a fresh start but if it's easier to get past that error loop I'll take it. Can anyone help me with this please?
Click to expand...
Click to collapse
Sounds like you may have a 3rd gen HDX. You'll need to identify the exact model as recovery procedures differ among the various fire devices.
Bumping this to see if I can get any help on it. I have decided to try again after finding my tablet. The tablet is a Kindle Fire HDX 7 3rd gen. After researching for a while I found out my brother rooted it using SuperSU as there's an su file under system/xbin (my brother doesn't remember anything) but no SuperSU app installed due to the factory reset. I was able to solve the language selection loop error but now I'm stuck on what to do next. Some apps work some don't. I just want to be able to use newer apps/games. Would you guys recommend trying to unroot or can I update current root to something not stuck in a 2014 update?
prisonmike1021 said:
Bumping this to see if I can get any help on it. I have decided to try again after finding my tablet. The tablet is a Kindle Fire HDX 7 3rd gen. After researching for a while I found out my brother rooted it using SuperSU as there's an su file under system/xbin (my brother doesn't remember anything) but no SuperSU app installed due to the factory reset. I was able to solve the language selection loop error but now I'm stuck on what to do next. Some apps work some don't. I just want to be able to use newer apps/games. Would you guys recommend trying to unroot or can I update current root to something not stuck in a 2014 update?
Click to expand...
Click to collapse
I would suggest go to amazon and download the full update. Also there is a hdx thread that might be more relevant. I do not have one of these devices and this thread is for the fire 7. See the next post...
Thanks @DB126
Here is a link to the amazon files
https://www.amazon.com/gp/help/customer/display.html?nodeId=G2JXLC4L34GX73TE
Here is a link the the HDX thread
https://forum.xda-developers.com/kindle-fire-hdx/orig-development
Michajin said:
I would suggest go to amazon and download the full update. Install the update. Also there is a hdx thread that might be more relevant. I do not have one of these devices and this thread is for the fire 7. ADB sideload should do the trick to get back to stock if you do not know what has been done to it.
Here is a link to the amazon files
https://www.amazon.com/gp/help/customer/display.html?nodeId=G2JXLC4L34GX73TE
Here is a link the the HDX thread
https://forum.xda-developers.com/kindle-fire-hdx/orig-development
Click to expand...
Click to collapse
Reloading FireOS (any build) is not an option on unrooted HDX device. Also rather dangerous without an understanding of compatible versions; a difficult to correct brick can easily result. Re-ask your question in the HDX help thread; someone (most likely me) will respond. You'll need to do a fair bit of work to restore that device including unlocking the bootloader and installing a custom ROM. Not for the faint of heart.
Thank you guys!
Hi there
First post so apologies in advance for any noob questions.
So I bought a Nook HD+ back in 2013 since my techie mates both had one and I bought one for the ride. From memory we used Cyanogenmod and CM11 or CM 12 I think, and installed an Ovation image. Since then I might have attempted an install of an ovation image from 2016, but have not used it at all. I've recently found the Nook HD+ in my storage boxes and wanted to either flash to the latest version or reset to stock to sell the unit off. However it no longer seems to want to boot up. Can anyone advise why it's not working when it was happily working back in the day, given nothing's been touched of late?
I charged it up and switched it on but it doesn't make it past the loader screen. Any ideas on what I should do to get this working again? Kinda don't want to spend time reloading an image or stuffing around with it as I only plan on offloading it assuming it's working.
I've tried to clear all cache and dalvik and various attempts to reboot. No difference to the outcome - always ends back at the loader screen.
I get a "Root Access possibly lost" message from time to time when trying to reboot. Doesn’t make a difference whether I choose yes or no, it ultimately ends up on that loader screen.
I’ve also tried booting into TWRP but don’t see any options to revert back to stock.
Any thoughts?
Cheers
Ben
benobi37 said:
Hi there
First post so apologies in advance for any noob questions.
So I bought a Nook HD+ back in 2013 since my techie mates both had one and I bought one for the ride. From memory we used Cyanogenmod and CM11 or CM 12 I think, and installed an Ovation image. Since then I might have attempted an install of an ovation image from 2016, but have not used it at all. I've recently found the Nook HD+ in my storage boxes and wanted to either flash to the latest version or reset to stock to sell the unit off. However it no longer seems to want to boot up. Can anyone advise why it's not working when it was happily working back in the day, given nothing's been touched of late?
I charged it up and switched it on but it doesn't make it past the loader screen. Any ideas on what I should do to get this working again? Kinda don't want to spend time reloading an image or stuffing around with it as I only plan on offloading it assuming it's working.
I've tried to clear all cache and dalvik and various attempts to reboot. No difference to the outcome - always ends back at the loader screen.
I get a "Root Access possibly lost" message from time to time when trying to reboot. Doesn’t make a difference whether I choose yes or no, it ultimately ends up on that loader screen.
I’ve also tried booting into TWRP but don’t see any options to revert back to stock.
Any thoughts?
Cheers
Ben
Click to expand...
Click to collapse
Bumping my original post - can someone help please? Cheers, Ben
benobi37 said:
Hi there
First post so apologies in advance for any noob questions.
So I bought a Nook HD+ back in 2013 since my techie mates both had one and I bought one for the ride. From memory we used Cyanogenmod and CM11 or CM 12 I think, and installed an Ovation image. Since then I might have attempted an install of an ovation image from 2016, but have not used it at all. I've recently found the Nook HD+ in my storage boxes and wanted to either flash to the latest version or reset to stock to sell the unit off. However it no longer seems to want to boot up. Can anyone advise why it's not working when it was happily working back in the day, given nothing's been touched of late?
I charged it up and switched it on but it doesn't make it past the loader screen. Any ideas on what I should do to get this working again? Kinda don't want to spend time reloading an image or stuffing around with it as I only plan on offloading it assuming it's working.
I've tried to clear all cache and dalvik and various attempts to reboot. No difference to the outcome - always ends back at the loader screen.
I get a "Root Access possibly lost" message from time to time when trying to reboot. Doesn’t make a difference whether I choose yes or no, it ultimately ends up on that loader screen.
I’ve also tried booting into TWRP but don’t see any options to revert back to stock.
Any thoughts?
Cheers
Ben
Click to expand...
Click to collapse
Hey, one question, are you able to boot into TWRP? If so, you can flash any rom. Also, here is the link for installing stock rom again if you want. https://forum.xda-developers.com/nook-hd/development/stock-nook-hd-nook-hd-2-2-1-2018-update-t3840163 I personally haven't tested it though.