I received my replacement Kindle Fire today. I proceeded to follow the same steps as I did with my first to root and install modaco. However, once I installed modaco the Kindle would not start. Luckily I backed up the system after I first rooted and was able to restore and get it going again. I then compared my old unit to the new and found that the software versions were different. I downloaded the update from Amazon and ran the install in TWRP. I am now stuck in this endless reboot cycle where it tells me that it detected a problem and must clear App storage. It prompts me to press the power button to proceed. I do this and it just repeats itself. Is there anything I can do to get out of this mode??
http://forum.xda-developers.com/showthread.php?t=1986798 different software versions? As in what version do you speak of?
Edit: my solution is no good if you can't reach the system to perform it.
Thepooch said:
http://forum.xda-developers.com/showthread.php?t=1986798 different software versions? As in what version do you speak of?
Edit: my solution is no good if you can't reach the system to perform it.
Click to expand...
Click to collapse
Kindle came with 6.3 and tried to upgrade it to 6.3.1.
That souldn`t be a problem since it`s likely you no longer have fff and twrp after doing so very good chance you will need factory cable to force it into fastboot so that you can send fff and twrp back to the device in order to flash a rom you can buy a factory cable here http://forum.xda-developers.com/showthread.php?t=1392693 post 9
Thepooch said:
That souldn`t be a problem since it`s likely you no longer have fff and twrp after doing so very good chance you will need factory cable to force it into fastboot so that you can send fff and twrp back to the device in order to flash a rom you can buy a factory cable here http://forum.xda-developers.com/showthread.php?t=1392693 post 9
Click to expand...
Click to collapse
Thanks for your help. I am ordering one today.
You're welcome the most important thing at this point is to keep it charged.
I assume that once I receive the cable I will be able to load FFF and TWRP using KFU?
Yes when you get your cable pm me and I will assist you in getting that done.
Related
Hello all,
So, I rooted my kindle fire and successfully installed TWRP but after flashing a new ROM (CM9 Reloaded) it just boots to a black screen. I will see the default kindle logo for a few seconds then nothing but a black back lit screen. I can't get into TWRP, adb shell can't find the device and kfu stalls out after waiting for my device to respond. Also, I don't believe FFF ever installed properly as I never saw the logo. I have tried re-installing the drivers but I still can't get my PC to see it. Under Device manager it will appear as Android Phone: Android ADB Interface.
I searched the forums and all I could find was that i need to get into fastboot which seems impossible at the moment. Is the factory cable my only hope?
Thanks Guys!
schachinger40 said:
Hello all,
So, I rooted my kindle fire and successfully installed TWRP but after flashing a new ROM (CM9 Reloaded) it just boots to a black screen. I will see the default kindle logo for a few seconds then nothing but a black back lit screen. I can't get into TWRP, adb shell can't find the device and kfu stalls out after waiting for my device to respond. Also, I don't believe FFF ever installed properly as I never saw the logo. I have tried re-installing the drivers but I still can't get my PC to see it. Under Device manager it will appear as Android Phone: Android ADB Interface.
I searched the forums and all I could find was that i need to get into fastboot which seems impossible at the moment. Is the factory cable my only hope?
Thanks Guys!
Click to expand...
Click to collapse
Just in case someone is reading this and is having the same issue, the factory cable worked like a charm. I was able to get back into TWRP recovery. Although, it did take a few tries to get it to boot.
schachinger40 said:
Just in case someone is reading this and is having the same issue, the factory cable worked like a charm. I was able to get back into TWRP recovery. Although, it did take a few tries to get it to boot.
Click to expand...
Click to collapse
So the only option is to get or make a factory cable?
Factory cable is not your only option but it would definitely be the easiest route.
Otherwise, fix your drivers or do whatever you can to get adb working.
With FFF installed, you can access twrp and reflash the ROM or try a different one.
Comeonesticks said:
So the only option is to get or make a factory cable?
Click to expand...
Click to collapse
It was the only thing that worked for me but it all depends on how much time you are willing to spend on it. For me, it was well worth the $12. I bought mine from here: http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9
The quality of the cable is great and I received it within a week. If it doesn't work at first don't freak out. It took a little while to get back into TWRP.
Good luck!
Am I screwed or can this be fixed with a fast boot?
If you must know this happened by using TWRP terminal command to get to fastboot, then going into Kindle Fire HD Restore Tool and using only option 1. Restore recovery and bootloader ( Only 1. not 2.Restore OS). After that I switched the boot back to normal and restarted.
Stupidity on my part I know, but can It be fixed?
P.S. I already ordered a factory cable.
narms72 said:
Am I screwed or can this be fixed with a fast boot?
If you must know this happened by using TWRP terminal command to get to fastboot, then going into Kindle Fire HD Restore Tool and using only option 1. Restore recovery and bootloader ( Only 1. not 2.Restore OS). After that I switched the boot back to normal and restarted.
Stupidity on my part I know, but can It be fixed?
P.S. I already ordered a factory cable.
Click to expand...
Click to collapse
when factory cable come reflash all, if dont work, request to amazon support to change it
persano said:
when factory cable come reflash all, if dont work, request to amazon support to change it
Click to expand...
Click to collapse
Thanks my factory cable came today in the mail will try the restore at like 6 tell you how it goes when done
Do you know if there is anyway I can flash cm10 to it with the factory cable in the kindle 2s current state?
Thanks again by the way!
narms72 said:
Do you know if there is anyway I can flash cm10 to it with the factory cable in the kindle 2s current state?
Thanks again by the way!
Click to expand...
Click to collapse
you cannot flash a cm10 system image. I could probalby get a startup script to autoboot into second boot..
similar issue
narms72 said:
Thanks my factory cable came today in the mail will try the restore at like 6 tell you how it goes when done
Click to expand...
Click to collapse
I have the same problem too. Just my kindle fire hd 8.9 doen't turn on. So i can not get in fastboot. I did my own factory usb, only put togueter pin 4 and 1 of micro usb. However my kindle fire looks as dead.
Some advice????
This is somewhat unique, I haven't found an exact duplicate of this problem yet, but basically I have 2 original KF's. I rooted them months ago, and installed android 4.2 on them. I got a couple new tablets and decided to bring these back to factory defaults, so I went through the process. One worked great and is currently able to do everything as per usual. The second is in a perpetual boot loop. I can't get FFF or TWRP to install because it won't stay booted long enough. It will boot usually with the Kindle Fire gold and white text, and then go to the unlock screen. Once I swipe to unlock, I get a handful of errors about processes not working properly. I can navigate around for right about 20 seconds before it immediately reboots. There is no shutdown process, just a black screen and then the KF logo again. I have a full charge and I am at a loss, any suggestions?
I would reflash the rom.
Sent from my Nexus 7 using xda app-developers app
Ixthusdan said:
I would reflash the rom.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I would love to, but I can't get it to connect to the PC long enough to do anything, how can I do that?
jonduben said:
I would love to, but I can't get it to connect to the PC long enough to do anything, how can I do that?
Click to expand...
Click to collapse
This is my problem exactly as well! I got rid of the error messages by clearing the data of contacts, contacts storage and calendar applications.
You can do this from settings -> applications -> all applications
Any help for the continuous lock screen -> home screen -> boot logo -> lock screen -loop would be appreciated!
I ran TWRP and had a custom rom on it before, but then reverted back to stock rom and am now running 6.3.2 from Amazon itself without any custom bootloaders.
So I got mine working, and now I feel really super embarassed.
Not sure which trick finally did it, but here's what I did:
I can't paste links yet as I am a newb user on the forum, but google for "kindle fire usb debugging" and open the result saying "Setting Up Your Kindle Fire Tablet for Testing". Note that there are two steps in that guide, first install the Amazon provided USB-driver and then prepare your Kindle.
Then the embarassing part: change the USB-port. I tried with three different cables and four different ports. Apparently the ports on the front of my desktop pc aren't good for this. After switching ports to behind my pc, Kindle Fire Utility all of a sudden was able to push in TRWP and FireFireFire bootloader!
4th: Wipe EVERYTHING using TRWP. Everything might not be necessary, but I figured why not. Even the SDcard had to go.
5th: Push in an older TRWP with instructions from here: teamw.in/project/twrp2/79
The instructions are a bit messy, after "idme bootmode 4002" you should exit the adb shell and run the fastboot command.
Having the older TRWP seems to be the only way to install Amazon's stock rom, newer ones give me errors. The version I used was 2.2.2.1.
I also installed the 6.3.1 version of the stock rom just to be sure, and let Kindle do the update afterwards on its own.
Everything seems to be working now, hope you'll get yours working too!
kesman said:
So I got mine working, and now I feel really super embarassed.
Not sure which trick finally did it, but here's what I did:
I can't paste links yet as I am a newb user on the forum, but google for "kindle fire usb debugging" and open the result saying "Setting Up Your Kindle Fire Tablet for Testing". Note that there are two steps in that guide, first install the Amazon provided USB-driver and then prepare your Kindle.
Then the embarassing part: change the USB-port. I tried with three different cables and four different ports. Apparently the ports on the front of my desktop pc aren't good for this. After switching ports to behind my pc, Kindle Fire Utility all of a sudden was able to push in TRWP and FireFireFire bootloader!
4th: Wipe EVERYTHING using TRWP. Everything might not be necessary, but I figured why not. Even the SDcard had to go.
5th: Push in an older TRWP with instructions from here: teamw.in/project/twrp2/79
The instructions are a bit messy, after "idme bootmode 4002" you should exit the adb shell and run the fastboot command.
Having the older TRWP seems to be the only way to install Amazon's stock rom, newer ones give me errors. The version I used was 2.2.2.1.
I also installed the 6.3.1 version of the stock rom just to be sure, and let Kindle do the update afterwards on its own.
Everything seems to be working now, hope you'll get yours working too!
Click to expand...
Click to collapse
you can also install the flashable zip version of 2.2.2.1 in current TWRP.
jonduben said:
This is somewhat unique, I haven't found an exact duplicate of this problem yet, but basically I have 2 original KF's. I rooted them months ago, and installed android 4.2 on them. I got a couple new tablets and decided to bring these back to factory defaults, so I went through the process. One worked great and is currently able to do everything as per usual. The second is in a perpetual boot loop. I can't get FFF or TWRP to install because it won't stay booted long enough. It will boot usually with the Kindle Fire gold and white text, and then go to the unlock screen. Once I swipe to unlock, I get a handful of errors about processes not working properly. I can navigate around for right about 20 seconds before it immediately reboots. There is no shutdown process, just a black screen and then the KF logo again. I have a full charge and I am at a loss, any suggestions?
Click to expand...
Click to collapse
I'm having the exact same issue. Were you able to fix yours?
fooz said:
I'm having the exact same issue. Were you able to fix yours?
Click to expand...
Click to collapse
kindle had a custom rom, and then you installed stock update.zip and now it's bootlooping?
sd_shadow said:
kindle had a custom rom, and then you installed stock update.zip and now it's bootlooping?
Click to expand...
Click to collapse
Correct. I wiped everything first, then renamed to update.zip and flashed stock.
Which update did you use? Bin name?
sd_shadow said:
Which update did you use? Bin name?
Click to expand...
Click to collapse
This one. https://s3.amazonaws.com/kindle-fire-updates/update-kindle-6.3.3_D01E_4112920.bin
update-kindle-6.3.3_D01E_4112920.bin
fooz said:
This one. https://s3.amazonaws.com/kindle-fire-updates/update-kindle-6.3.3_D01E_4112920.bin
Click to expand...
Click to collapse
file should be 204 MB (214,586,505 bytes) MD5: 89A4DEF015289F2291BF502E09A70554 see https://sites.google.com/site/sdshadowscollection/home/hash-checksums
update-kindle-6.3.3_D01E_4112920.bin[/QUOTE]Probably need a fastboot cable to fix, Amazon has locked that version down pretty good.
see my Using Factory/Fastboot Cable to Flash FFF Bootloader and TWRP Recovery
if the md5 checksum matched
could try the [UTILITY] Kindle Fire Unbrick Utility V1.1
but think it is unlikely that will work, with 6.3.3
.
sd_shadow said:
file should be 204 MB (214,586,505 bytes) MD5: 89A4DEF015289F2291BF502E09A70554 see https://sites.google.com/site/sdshadowscollection/home/hash-checksums
update-kindle-6.3.3_D01E_4112920.bin
Click to expand...
Click to collapse
Probably need a fastboot cable to fix, Amazon has locked that version down pretty good.
see my Using Factory/Fastboot Cable to Flash FFF Bootloader and TWRP Recovery
if the md5 checksum matched
could try the [UTILITY] Kindle Fire Unbrick Utility V1.1
but think it is unlikely t will work, with 6.3.3
.[/QUOTE]
Thanks for your help. Will try this and report back.
I think I'm out of luck with this one, but hopefully someone can guide me a bit more and get me out of this mess. Long story short, I had cyanogen running on my original Kindle Fire. Decided to go back to stock to trade it in. It is currently running 6.3.3. However, I ended up leaving TWRP without doing a factory reset / wiping cache / etc. Now my Fire is stuck in a reboot loop where it boots and seems to work fine, but then it starts giving me errors about the kindle keyboard has stopped, acore has stopped, calendar storage has stopped and then it reboots. I've tried just about everything I've seen on these boards to get it working again, but I run into a wall regardless of which method I try.
I've tried quickly navigating to the settings and trying a factory reset around 100 times without any success.
I've tried using adb to factory reset without success.
I've tried using the kindle fire utility to grant root but it reboots too quickly to finish the script.
I have a fastboot cable and have followed many of the guides on this forum and nothing seems to be working.
I'm sure I'm missing some other stuff I've done, but my brain is just mush at this point with everything.
KFU does not root 6.3.3
KFU can't flash twrp/fff on 6.3.3
How to flash twrp and firefirefire with a Fastboot cable
http://forum.xda-developers.com/showpost.php?p=53652317&postcount=2
Sent from my XT907 using Tapatalk
I'm pretty sure I've followed that guide before and it wouldn't let me perform the flash. I don't know what is wrong now though. The factory cable is not even forcing it into fastboot at this point.
low battery?
Sent from my XT907 using Tapatalk
sd_shadow said:
low battery?
Click to expand...
Click to collapse
Seems to be around 75%. I'll try on another PC in the house to double check.
ZeroCoin said:
Seems to be around 75%. I'll try on another PC in the house to double check.
Click to expand...
Click to collapse
No luck on a different PC. Not sure what could have happened as I'm positive the cable was working before.
ZeroCoin said:
I'm pretty sure I've followed that guide before and it wouldn't let me perform the flash. I don't know what is wrong now though. The factory cable is not even forcing it into fastboot at this point.
Click to expand...
Click to collapse
What worked for me was getting to TWRP and then ADB side loading the correct bootloader, TWRP, ROM & Gapps. Not 100% sure if it would work in your situation, but may be worth a try. Someone smarter than me will have to tell you of this is a bad idea, since I may have just gotten lucky...
I followed the AFTV guide to a T. Flashed 51.1.4.0, had the boot menu, CWM and everything was golden. Pushed 51.1.5.3 to the SD, rebooted to CWM, flashed, now stuck in a loop. I cant even connect to it with the adb connect command. Am I screwed? Is this thing done? I dont understand. It doesnt even show the boot menu anymore. Just straight to the looping firetv logo. Was i supposed to reflash the boot menu after installing prerooted 51.1.4.0? This sucks if it's done for.....
Have a look here:
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/
Calibaan said:
Have a look here:
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/
Click to expand...
Click to collapse
Thanks man. Hopefully one of those methods works. I've been at this for 4 hours carefully working my way through every single step. The highest high of the one last flash to go, turning into the gut wrenching sickness of a boot loop is too much for tonight and I'll try tomorrow.
On a side note: who runs that site? Guy is a God and needs a golden fire TV sent to him.
supremekizzle said:
On a side note: who runs that site? Guy is a God and needs a golden fire TV sent to him.
Click to expand...
Click to collapse
LOL! Glad you're finding the site useful. Sorry you ran into issues, but if you unlocked your bootloader already, then you should be able to recover. Follow the guide Calibaan linked.
Maybe I should write a "Hello, I'm Elias" post to put a face to my work.
AFTVnews.com said:
LOL! Glad you're finding the site useful. Sorry you ran into issues, but if you unlocked your bootloader already, then you should be able to recover. Follow the guide Calibaan linked.
Maybe I should write a "Hello, I'm Elias" post to put a face to my work.
Click to expand...
Click to collapse
Yea bootloader is unlocked. I was literally at the step of flashing the newest prerooted version when it happened. So, if I get past the bootloop, which step should I continue with?
supremekizzle said:
Yea bootloader is unlocked. I was literally at the step of flashing the newest prerooted version when it happened. So, if I get past the bootloop, which step should I continue with?
Click to expand...
Click to collapse
Once you get into recovery, you should follow the "Resetting with Recovery Mode" section found here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3.2
Some of the steps will likely be redundant and unnecessary, but it ensures everything is in a good state to proceed. Most likely something went wrong when you installed the boot menu, so be sure to verify the boot menu is working by using it to enter recovery mode BEFORE flashing the 51.1.5.3 ROM.
AFTVnews.com said:
Once you get into recovery, you should follow the "Resetting with Recovery Mode" section found here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3.2
Some of the steps will likely be redundant and unnecessary, but it ensures everything is in a good state to proceed. Most likely something went wrong when you installed the boot menu, so be sure to verify the boot menu is working by using it to enter recovery mode BEFORE flashing the 51.1.5.3 ROM.
Click to expand...
Click to collapse
Thank you. I'm perfectly fine redoing all the steps no matter how redundant. I just want to make sure it's OK to reflash some of the stuff without first deleting the old. Will it just overwrite?
supremekizzle said:
Thank you. I'm perfectly fine redoing all the steps no matter how redundant. I just want to make sure it's OK to reflash some of the stuff without first deleting the old. Will it just overwrite?
Click to expand...
Click to collapse
Yes, it's alright to re-flash anything. You should manually delete any files you "pushed" to the Fire TV and re-push them to ensure a corrupted file wasn't the cause of the boot loop. (You don't want to use the same corrupted file when you re-do things.)
AFTVnews.com said:
Yes, it's alright to re-flash anything. You should manually delete any files you "pushed" to the Fire TV and re-push them to ensure a corrupted file wasn't the cause of the boot loop. (You don't want to use the same corrupted file when you re-do things.)
Click to expand...
Click to collapse
doesnt matter. just tried to fastboot and it isnt detecting any. I know the bootloader was unlocked. I did the adb shell command and it showed unlocked bootloader. WTF happened? EVERYTHING was followed.
OK tried just fastboot device minus the "s" and it's just waiting on device.
It's dead. Isn't it?
OMG OMG OMG OMG OMG!!!!!!!!!! Keyboard trick worked! It didnt work last night, but hitting the keys in quick succession finally made it boot into recovery!!!! What is the BEST way to proceed now that I'm here. I cannot eff this up!
supremekizzle said:
doesnt matter. just tried to fastboot and it isnt detecting any. I know the bootloader was unlocked. I did the adb shell command and it showed unlocked bootloader. WTF happened? EVERYTHING was followed.
OK tried just fastboot device minus the "s" and it's just waiting on device.
It's dead. Isn't it?
Click to expand...
Click to collapse
The Fire TV will still connect via fastboot even if the bootloader is locked. You just can't flash anything if the bootloader is locked.
While it's powered off, connect it to your PC using the A-to-A USB cable. Then plug in the Fire TV power. When it powers on, see if it's stuck on the white Amazon logo. If it is, then you're in fastboot mode, which means it's just an issue with PC drivers. If it's still doing a boot loop, then it's either too far damaged, or there's something wrong with your USB cable/USB port. As for PC drivers, I don't have an exact driver to tell you to use because, at the time I tried many and am not sure which one ultimately worked. It's something I;ve been meaning to figure out.
When the Fire TV detects power coming in through the USB port while it's booting, it enters fastboot mode (indicated by the stuck white Amazon logo).
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
supremekizzle said:
OMG OMG OMG OMG OMG!!!!!!!!!! Keyboard trick worked! It didnt work last night, but hitting the keys in quick succession finally made it boot into recovery!!!! What is the BEST way to proceed now that I'm here. I cannot eff this up!
Click to expand...
Click to collapse
If you're in recovery, install 51.1.4.0 and then proceed with the guide I linked.
AFTVnews.com said:
The Fire TV will still connect via fastboot even if the bootloader is locked. You just can't flash anything if the bootloader is locked.
While it's powered off, connect it to your PC using the A-to-A USB cable. Then plug in the Fire TV power. When it powers on, see if it's stuck on the white Amazon logo. If it is, then you're in fastboot mode, which means it's just an issue with PC drivers. If it's still doing a boot loop, then it's either too far damaged, or there's something wrong with your USB cable/USB port. As for PC drivers, I don't have an exact driver to tell you to use because, at the time I tried many and am not sure which one ultimately worked. It's something I;ve been meaning to figure out.
When the Fire TV detects power coming in through the USB port while it's booting, it enters fastboot mode (indicated by the stuck white Amazon logo).
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
If you're in recovery, install 51.1.4.0 and then proceed with the guide I linked.
Click to expand...
Click to collapse
THANK YOU! While doing the keyboard trick there were a couple of times it stuck on the static amazon logo so it must have detected that, but 4 or 5 times connecting to my computer trying to fastboot it did not. I have to go to the Zoo right now, but will continue this later. Just one more question: As long as I'm now in recovery, I should be able to recover. Right? I already went out and bought another rootable FTV, but if this one is saved I can just go return that one.
supremekizzle said:
THANK YOU! While doing the keyboard trick there were a couple of times it stuck on the static amazon logo so it must have detected that, but 4 or 5 times connecting to my computer trying to fastboot it did not. I have to go to the Zoo right now, but will continue this later. Just one more question: As long as I'm now in recovery, I should be able to recover. Right? I already went out and bought another rootable FTV, but if this one is saved I can just go return that one.
Click to expand...
Click to collapse
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.
AFTVnews.com said:
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.
Click to expand...
Click to collapse
So, should I be using the ip shown as "current ip address in CWM" for ADB or the one I had written down from when it was working?
Nevermind. Cannot connect to either IP from adb
lol. I'm dumb. Gotta connect the ethernet.
.....flashed 51.1.4.0 annnnnnnddddd boot loop again gaaaahhhhhhhhhh. Help me fix AFTVNews and I will make a nice donation to you
BOOTED!!!!
AND.... On latest rooted version. Thanks for bearing with me through that emotional roller coaster of despair and hope. None of this would be possible without AFTVNews collecting all of the information into one place and all of the others who put so much work into this like rbox. Round of beers going out to those two via donation. Thank you!
AFTVnews.com said:
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.
Click to expand...
Click to collapse
Any suggestions?:
http://forum.xda-developers.com/fire-tv/help/fire-tv-boots-white-amazon-logo-screen-t3139511
supremekizzle,
Glad it worked out for you.:good:
supremekizzle said:
So, should I be using the ip shown as "current ip address in CWM" for ADB or the one I had written down from when it was working?
Nevermind. Cannot connect to either IP from adb
lol. I'm dumb. Gotta connect the ethernet.
.....flashed 51.1.4.0 annnnnnnddddd boot loop again gaaaahhhhhhhhhh. Help me fix AFTVNews and I will make a nice donation to you
BOOTED!!!!
AND.... On latest rooted version. Thanks for bearing with me through that emotional roller coaster of despair and hope. None of this would be possible without AFTVNews collecting all of the information into one place and all of the others who put so much work into this like rbox. Round of beers going out to those two via donation. Thank you!
Click to expand...
Click to collapse
Glad it all worked out and glad I could help!
For future reference, when you edit a post, it doesn;t trigger XDA to send out a notification to the user you're quoting (me). That's why I didn't respond to your last message until now (when I manually checked it). Post a reply and use the '@' symbol (like this: @supremekizzle ) to ensure the user gets notified.