Related
My Kindle was rooted but I decided to try my hand at installing a custom ROM. However, the ROM I tried would not work and the screen stayed black. However, thanks to TWRP I could install Kindle from Amazon again. The installation went thru smoothly, or so I thought. Now, when I boot the Kindle, I see the Kindle Fire Logo and it stays there. The Computer can see the Kindle as an Android device, Android Composite Device. But Kindle Fire Utility cannot see it so I could try and re-install it again. Any suggestions?
Lacking information, so I'll just fill the voids with assumptions.
I *assume* you didn't wipe cache, dalvik-cache and most important when switching from a ROM to another, Factory Reset - this is the reason said custom ROM wouldn't work, and the reason flashing back update.zip (as you said you installed it, rather than restoring a backup) caused your KF to get stuck in a semi brick.
The most important question here is, do you have FFF installed?
If you do, fixing this is trivial. Just get into TWRP from FFF, wipe cache, dalvik-cache and factory reset and then install whatever ROM you'd like to try or use.
If you don't have FFF installed, then your solutions are to either get a factory cable (recommended) or to crack open the case and do the USB pin short trick. From there you can use fastboot to install FFF and boot into TWRP.
Alternatively, you can try "fastboot getvar product" or "adb shell idme bootmode 5001" to see if you get lucky.
Dasanko said:
Lacking information, so I'll just fill the voids with assumptions.
I *assume* you didn't wipe cache, dalvik-cache and most important when switching from a ROM to another, Factory Reset - this is the reason said custom ROM wouldn't work, and the reason flashing back update.zip (as you said you installed it, rather than restoring a backup) caused your KF to get stuck in a semi brick.
The most important question here is, do you have FFF installed?
If you do, fixing this is trivial. Just get into TWRP from FFF, wipe cache, dalvik-cache and factory reset and then install whatever ROM you'd like to try or use.
If you don't have FFF installed, then your solutions are to either get a factory cable (recommended) or to crack open the case and do the USB pin short trick. From there you can use fastboot to install FFF and boot into TWRP.
Alternatively, you can try "fastboot getvar product" or "adb shell idme bootmode 5001" to see if you get lucky.
Click to expand...
Click to collapse
I tried the USB pin short trick but now my Kindle won't turn on at all nor will it charge. Thanks anyways!
i have similar problem ......please need help
After successfully rooting kf with kfu and making a backup ... I did factory reset and flashed a custom rom ... now kindle is stuck on " kindle fire" logo and just keeps flashing and rebooting . My computer recognizes it as android phone ( android adb ) and kfu does too but only for a couple of seconds . During those few seconds I try recovery ... fast boot ...normal boot... n none seem to work . Kf just reboots n returns to boot loop . Any advice is appreciated .. thanks
Start a new thread when you're posting your own issues.
What colour is the "kindle fire" logo when you turn on your KF?
Force Kindle into Fastboot
Ok, so I have finally got my Kindle to turn on, using the USB Short Trick. Now my only question is about getting the Kindle to boot into fastboot mode so I can re-format the sdcard partition and finally load a new ROM. I have tried several different commands and they all seem to miss the window of opportunity to start the kindle in fastboot mode. Is there any way, short of a factory cable, that one can make the kindle start in fastboot mode?
Not fastboot get var
ComputerGenuis2.0 said:
Ok, so I have finally got my Kindle to turn on, using the USB Short Trick. Now my only question is about getting the Kindle to boot into fastboot mode so I can re-format the sdcard partition and finally load a new ROM. I have tried several different commands and they all seem to miss the window of opportunity to start the kindle in fastboot mode. Is there any way, short of a factory cable, that one can make the kindle start in fastboot mode?
Click to expand...
Click to collapse
fastboot getvar product doesn't seem to do the trick. The kindle seems to be in fastboot mode but the adb shell cannot access the device.
The problem is that you don't have the fastboot drivers installed (also, ADB will not work while fastboot is active) - Windows is painfully slow at detecting a device and installing its drivers, so by the time it even notices anything, the fastboot window is already over.
To solve this, use firekit: http://forum.xda-developers.com/showthread.php?t=1430038
The script that will probably suit your needs the most is usb_install_fff_twrp.
Used Firekit
Dasanko said:
The problem is that you don't have the fastboot drivers installed (also, ADB will not work while fastboot is active) - Windows is painfully slow at detecting a device and installing its drivers, so by the time it even notices anything, the fastboot window is already over.
To solve this, use firekit: http://forum.xda-developers.com/showthread.php?t=1430038
The script that will probably suit your needs the most is usb_install_fff_twrp.
Click to expand...
Click to collapse
I have TWRP and FFF installed. However, upon booting into TWRP, the sdcard partition cannot be mounted, to the Kindle that is, and as such, I cannot mount the sdcard to the computer. When I researched this some more, I found that I can fix this by using a command via adb shell. The guide instructed using fastboot to achieve this. When would be the best time to use adb shell?
What's the output of partitions.txt? (type the following from TWRP)
adb shell parted /dev/block/mmcblk0 p > partitions.txt
Can't use adb
Dasanko said:
What's the output of partitions.txt? (type the following from TWRP)
adb shell parted /dev/block/mmcblk0 p > partitions.txt
Click to expand...
Click to collapse
The problem at hand is using adb. I can never time it exactly right to open adb. I always get an "error: device not found". Windows even recognizes that Android ADB Interface is plugged in.
Okay, things are getting awfully confusing here.
What exactly is it that you can do and that you cannot do?
For example, are FFF and TWRP functional?
GOT IT!
Thank you! I finally figured out that the wrong driver had reinstalled and that was causing my computer to not be able to use adb shell. I fixed that and voila, I am now running CM9. Thanks again!
Not sure what's going on here.. I unrooted my kindlefire with update.zip but I forgot to wipe to factory reset before i flashed update.zip and when i rebooted my kindle i noticed that A ! symbol popped up with "Sorry" that says "The application Calendar Storage (process com.android.providers.calendar) has stopped unexpectedly. Please try again" That isn't the only problem, i click force close and another prompt comes up saying "The process android.process.acore has stopped unexpectedly. Please try again" It waits a few seconds, then proceeds to do a fast reboot? It comes up with the yellow kindle fire and immediately after it boots up it shows the errors.
Not sure what to do. Tried installing TWRP but the kindle doesn't stay on long enough so right now I'm pretty unconvinced of anything..
Any help would be greatly appreciated.
You just need to fast quickly get to factory reset and reset it try from a powered off position it may give you a few seconds extra to complete the task...
Thepooch said:
You just need to fast quickly get to factory reset and reset it try from a powered off position it may give you a few seconds extra to complete the task...
Click to expand...
Click to collapse
I'm not sure how to get there.. I don't have any form of backup installed. It's on the complete default rom
Edit: Found out how to get to factory reset, only to discover that I need a 40% charge, when mine is less than 5% and won't charge any more because of my problem
Still haven't figured this out. Can't use my kindle at all until this is fixed :/
iKrotos said:
Still haven't figured this out. Can't use my kindle at all until this is fixed :/
Click to expand...
Click to collapse
You're most likely going to have to put the device into fastboot mode to fix this problem. You can quickly send a sequence of adb commands to put the device into fastboot before the system crashes...
http://forum.xda-developers.com/showthread.php?t=1638452
by using the "Getting to fastboot mode" section above. That seems sketchy at best. Otherwise, you can get a factory cable...
http://forum.xda-developers.com/showthread.php?t=1550999
and put it into fastboot mode that way. In either case, you'll want to delete the userdata partition...
Code:
fastboot -i 0x1949 erase userdata
Then the next time you boot the device normally (by changing the bootmode back to 4000 if it isn't already), the system software will remake that partition and it should boot normally.
kinfauns said:
You're most likely going to have to put the device into fastboot mode to fix this problem. You can quickly send a sequence of adb commands to put the device into fastboot before the system crashes...
http://forum.xda-developers.com/showthread.php?t=1638452
by using the "Getting to fastboot mode" section above. That seems sketchy at best. Otherwise, you can get a factory cable...
http://forum.xda-developers.com/showthread.php?t=1550999
and put it into fastboot mode that way. In either case, you'll want to delete the userdata partition...
Code:
fastboot -i 0x1949 erase userdata
Then the next time you boot the device normally (by changing the bootmode back to 4000 if it isn't already), the system software will remake that partition and it should boot normally.
Click to expand...
Click to collapse
Read the beginners guide for KF, Found about about ADB fastboot etc. Going to install ADB tomorrow and try to figure this all out. Thanks.
I can't do this. It's been over a month. My kindle is finished..
iKrotos said:
I can't do this. It's been over a month. My kindle is finished..
Click to expand...
Click to collapse
"I can't do this"
Well that explains everything, doesn't it? It's a good thing you explained your problem in such great detail or I might spend time trying to help you fix your Kindle thinking you "could" do it. Phew. Saved us all a lot of time, thank you.
I made the same mistake of flashing the stock update without wiping and factory resetting.
The device will boot, then immediately give the calendar and android.process.acore errors for about 20 seconds before rebooting. It doesn't give me enough time to do a factory reset through the menu before it restarts.
After reading up on basic guides and downloading the necessary software, I can't find a way to get to fastboot, and I'm afraid even the noob guides are just confusing me more at this point.
From what I can understand, I'll probably have to get a factory cable to force the device into fastboot, because the Kindle reboots before the PC has a chance to recognize it, but what happens then? I've read the ADB for dummies guides, and searched the forum for and I still can't really understand how to execute the commands.
Can anyone link a relevant thread, or maybe give some dumbed-down advice?
LaszloToth said:
I made the same mistake of flashing the stock update without wiping and factory resetting.
The device will boot, then immediately give the calendar and android.process.acore errors for about 20 seconds before rebooting. It doesn't give me enough time to do a factory reset through the menu before it restarts.
After reading up on basic guides and downloading the necessary software, I can't find a way to get to fastboot, and I'm afraid even the noob guides are just confusing me more at this point.
From what I can understand, I'll probably have to get a factory cable to force the device into fastboot, because the Kindle reboots before the PC has a chance to recognize it, but what happens then? I've read the ADB for dummies guides, and searched the forum for and I still can't really understand how to execute the commands.
Can anyone link a relevant thread, or maybe give some dumbed-down advice?
Click to expand...
Click to collapse
Get a factory cable and then we can work on fixing your device.
One thing you have to know about entering commands is that computers have no more intelligence than, say, an ordinary rock. Meaning, they are not able to think on their own. They don't have the capacity to make their own decisions. Everything is laid out for them via sets of instructions. ADB and fastboot are programs with their own sets of instructions embedded into them, so in order to use them, you must direct the computer to those programs. When entering commands from the command line, the computer will search only the present working directory for those commands (plus any directories in it's PATH, but that is a subject for another time). When you open a command prompt in Windows, it will start in a specific directory (folder). Normally in Windows its the "Documents and Settings" folder (if I remember correctly). When you enter a command like "adb devices", the computer will search it's own set of built in commands for the first word (command) in the command line (in this case, adb). If that command isn't in it's set of built in commands, it searches the present working directory. In all likelihood, adb will not be in in the first present working directory when the command prompt opens up so you have to redirect it. There are several ways to do this. You can make sure the directory containing adb is in your PATH, but there's a little bit of learning involved and it's unnecessary unless you intend to enter a LOT of adb commands. You can change directories (cd) to the correct folder, but if you don't know what you're doing it can get very confusing and frustrating. The easiest and most straight forward way of doing this is to locate the directory containing adb and fastboot then "Shift + right-click, on that folder and select "Open command window here". The command window that opens is where you'll enter your adb/fastboot commands. Apart from that, you must really know the commands you're using, how they're used and what they do, or you're just wasting your time.
Does or kindle gets recognized.. if so there is a chance to recover
Sent from my MB526 using Tapatalk 2
soupmagnet said:
Get a factory cable and then we can work on fixing your device.
One thing you have to know about entering commands is that computers have no more intelligence than, say, an ordinary rock. Meaning, they are not able to think on their own. They don't have the capacity to make their own decisions. Everything is laid out for them via sets of instructions. ADB and fastboot are programs with their own sets of instructions embedded into them, so in order to use them, you must direct the computer to those programs. When entering commands from the command line, the computer will search only the present working directory for those commands (plus any directories in it's PATH, but that is a subject for another time). When you open a command prompt in Windows, it will start in a specific directory (folder). Normally in Windows its the "Documents and Settings" folder (if I remember correctly). When you enter a command like "adb devices", the computer will search it's own set of built in commands for the first word (command) in the command line (in this case, adb). If that command isn't in it's set of built in commands, it searches the present working directory. In all likelihood, adb will not be in in the first present working directory when the command prompt opens up so you have to redirect it. There are several ways to do this. You can make sure the directory containing adb is in your PATH, but there's a little bit of learning involved and it's unnecessary unless you intend to enter a LOT of adb commands. You can change directories (cd) to the correct folder, but if you don't know what you're doing it can get very confusing and frustrating. The easiest and most straight forward way of doing this is to locate the directory containing adb and fastboot then "Shift + right-click, on that folder and select "Open command window here". The command window that opens is where you'll enter your adb/fastboot commands. Apart from that, you must really know the commands you're using, how they're used and what they do, or you're just wasting your time.
Click to expand...
Click to collapse
Thanks, I've read up a bit more about the ADB and Fastboot commands, and I think I have a better grasp on them now, and your explanation of where I need be as far as changing directories in the command prompt really clears things up.
From reading your advice earlier in this thread, my best option would probably be to wipe the existing user data on the device that I forgot about before re-flashing the stock Kindle update by changing directories to the folder which contains ADB.exe and Fastboot.exe, then running the "fastboot -i 0x1949 erase userdata" command once I've connected the device with a factory cable. By doing this, would I be essentially restoring the device as if it were brand new again? Aside from erasing user data, are there any other ADB or Fastboot commands that I should run?
Also, assuming the ADB drivers are installed properly, once I've plugged in the device with the factory cable, will KFU immediately recognize the device, or will I need to first run the "fastboot -i 0x1949 erase userdata" command to get it back to stock first before I get 4000 status in KFU? I'm wondering if I could just plug in the factory cable, root and flash TWRP via KFU, then wipe and factory reset the user data from within TWRP, or would that be going about it backwards?
Thanks again fro the help!
---------- Post added at 02:31 PM ---------- Previous post was at 02:24 PM ----------
kishorev said:
Does or kindle gets recognized.. if so there is a chance to recover
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
No, the KFU status is "unknown" and Windows doesn't even really have time to recognize that the device is connected via USB, since the Kindle will reboot every 15-20 seconds.
I've ordered a factory cable, so hopefully it will be a pretty straight-forward fix once I get it.
Had a similar problem of rebooting every 10 sec or so..I left it on charge overnight and it worked..it got charged decent enough for me to help recover it..
Just try charging it overnight it might just work..I always feel using factory cable shd be the last resort
Sent from my Kindle Fire using Tapatalk 2
LaszloToth said:
Thanks, I've read up a bit more about the ADB and Fastboot commands, and I think I have a better grasp on them now, and your explanation of where I need be as far as changing directories in the command prompt really clears things up.
From reading your advice earlier in this thread, my best option would probably be to wipe the existing user data on the device that I forgot about before re-flashing the stock Kindle update by changing directories to the folder which contains ADB.exe and Fastboot.exe, then running the "fastboot -i 0x1949 erase userdata" command once I've connected the device with a factory cable. By doing this, would I be essentially restoring the device as if it were brand new again? Aside from erasing user data, are there any other ADB or Fastboot commands that I should run?
Also, assuming the ADB drivers are installed properly, once I've plugged in the device with the factory cable, will KFU immediately recognize the device, or will I need to first run the "fastboot -i 0x1949 erase userdata" command to get it back to stock first before I get 4000 status in KFU? I'm wondering if I could just plug in the factory cable, root and flash TWRP via KFU, then wipe and factory reset the user data from within TWRP, or would that be going about it backwards?
No, the KFU status is "unknown" and Windows doesn't even really have time to recognize that the device is connected via USB, since the Kindle will reboot every 15-20 seconds.
I've ordered a factory cable, so hopefully it will be a pretty straight-forward fix once I get it.
Click to expand...
Click to collapse
One thing you need to realize, is that once you get custom recovery installed, you will rarely ever need to use fastboot commands. Fastboot commands really only need to be used when everything else fails. Custom recovery and the latest version of the FireFireFire bootloader have probably 90% of the functionality that fastboot has, so unless those options aren't available to you, try to avoid fastboot altogether.
Most Kindle Fire problems are fixed by wiping the system, data & cache (factory reset) partitions and reinstalling the ROM.
Your first course of action should be to get TWRP and FireFireFire installed, if they aren't already. For this you will need fastboot commands. In order to issue fastboot commands, you need to be in fastboot mode. I'm guessing this is most likely not the case. Unfortunately, without a system to boot to, or the FireFireFire bootloader (blue Kindle Fire logo) installed, you have no chance of getting into fastboot without a factory cable.
The factory cable will get you into fastboot so you can reinstall custom recovery and reinstall a new ROM. You can then use the custom recovery to install a new bootloader (never wipe to install a bootloader BTW). Chances are, that is all you need to fix your device. You should keep your device powered off (hold power button for 20 seconds), until the factory cable arrives.
Hope that helps.
soupmagnet said:
One thing you need to realize, is that once you get custom recovery installed, you will rarely ever need to use fastboot commands. Fastboot commands really only need to be used when everything else fails. Custom recovery and the latest version of the FireFireFire bootloader have probably 90% of the functionality that fastboot has, so unless those options aren't available to you, try to avoid fastboot altogether.
Most Kindle Fire problems are fixed by wiping the system, data & cache (factory reset) partitions and reinstalling the ROM.
Your first course of action should be to get TWRP and FireFireFire installed, if they aren't already. For this you will need fastboot commands. In order to issue fastboot commands, you need to be in fastboot mode. I'm guessing this is most likely not the case. Unfortunately, without a system to boot to, or the FireFireFire bootloader (blue Kindle Fire logo) installed, you have no chance of getting into fastboot without a factory cable.
The factory cable will get you into fastboot so you can reinstall custom recovery and reinstall a new ROM. You can then use the custom recovery to install a new bootloader (never wipe to install a bootloader BTW). Chances are, that is all you need to fix your device. You should keep your device powered off (hold power button for 20 seconds), until the factory cable arrives.
Hope that helps.
Click to expand...
Click to collapse
So instead of using fastboot to wipe the user data, I should use it to install TWRP? Can you give me the fastboot command for that? Or can I do that with KFU once I plug in the factory cable?
http://forum.xda-developers.com/showpost.php?p=23747804
Thanks soupmagnet, I got the factory cable today and was able to flash FFF and TWRP with fastboot commands, and it's working like it should again. You help has been much appreciated.
same problem with kindle fire.
LaszloToth said:
Thanks soupmagnet, I got the factory cable today and was able to flash FFF and TWRP with fastboot commands, and it's working like it should again. You help has been much appreciated.
Click to expand...
Click to collapse
hi, i am new here and i got exact the same problem with you, i just ordered the factory cable, can you please give the step by step procedure on solving this problem with the factory cable. your help will be appreciated, thanks.
Thepooch said:
You just need to fast quickly get to factory reset and reset it try from a powered off position it may give you a few seconds extra to complete the task...
Click to expand...
Click to collapse
:good::good::good::good::good::good: works for me thank you
ok, today i had the same problem because i didn't wipe the factory restore!
The solution WASN'T the Factory Cable (I was considering buying one)!
Very easy:
Linux and SOUPKIT! were the solution, when the tablet boots up immediately hit the install recovery, after installing recovery, just set to boot into recovery.
Now is very much you can do (ex. wipe everything and than install update.zip all over)
Very much thank you to the guy who made SOUPKIT! (u've saved my S many many times )
A few months ago I tried to root/ gapps a KF2 for a friend, and after a freak OTA update the horrible thing kept getting stuck in a bootloop.
Basically if you powered it on it would get stuck on the Kindle pulsing logo until it restarted itself from scratch and did it all over again. Then on the few times it would get to the standard lock screen it would freeze up there and restart itself anyway.
Every now and then it would boot in and work fine though.
What I eventually did to get it working:
1.) Get a factory cable (they don't cost too much off ebay).
2.) Using fastboot mode clear the data and cache partition:
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
20 seconds later the device worked perfectly and hasn't bootlooped since.
It might also be possible to do this by a.) installing TWRP and erasing the cache/ data from there, or b.) booting into the bootloader from a rooted system. I don't want to test this though because at this point I just want to make this awful thing work properly in stock.
I hope this helps someone else in the same situation. I do remember reading a similar problem on XDA a few months ago when it started giving trouble.
hexd said:
A few months ago I tried to root/ gapps a KF2 for a friend, and after a freak OTA update the horrible thing kept getting stuck in a bootloop.
Basically if you powered it on it would get stuck on the Kindle pulsing logo until it restarted itself from scratch and did it all over again. Then on the few times it would get to the standard lock screen it would freeze up there and restart itself anyway.
Every now and then it would boot in and work fine though.
What I eventually did to get it working:
1.) Get a factory cable (they don't cost too much off ebay).
2.) Using fastboot mode clear the data and cache partition:
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
20 seconds later the device worked perfectly and hasn't bootlooped since.
It might also be possible to do this by a.) installing TWRP and erasing the cache/ data from there, or b.) booting into the bootloader from a rooted system. I don't want to test this though because at this point I just want to make this awful thing work properly in stock.
I hope this helps someone else in the same situation. I do remember reading a similar problem on XDA a few months ago when it started giving trouble.
Click to expand...
Click to collapse
Where do i enter this in when I'm in fastboot?
Karetus said:
Where do i enter this in when I'm in fastboot?
Click to expand...
Click to collapse
You need to use the fastboot application. You can get it either via the Android Development Kit (just google for it) or just use it from any other source (I know the FlashTool for Sony phones has it along with ADB). Once it is on your PC, open a command prompt window to that folder and run it from there.
Just remember you need the Kindle to be in FB Mode (the screen has a picture of a red and green stoplight on it) and you need fastboot drivers installed for the device (this is a bit tricky for Win8, no problem for Windows 7 though).
hexd said:
You need to use the fastboot application. You can get it either via the Android Development Kit (just google for it) or just use it from any other source (I know the FlashTool for Sony phones has it along with ADB). Once it is on your PC, open a command prompt window to that folder and run it from there.
Just remember you need the Kindle to be in FB Mode (the screen has a picture of a red and green stoplight on it) and you need fastboot drivers installed for the device (this is a bit tricky for Win8, no problem for Windows 7 though).
Click to expand...
Click to collapse
I'm at a screen with a blue arrow a and yellow text that says "fastboot mode"
Karetus said:
I'm at a screen with a blue arrow a and yellow text that says "fastboot mode"
Click to expand...
Click to collapse
Please make sure that you have a Kindle Fire 2 (or at least something in the second generation Fire range). It might help if you take a picture of the device in fastboot mode and post it here.
Also did you boot the kindle into fastboot mode using a factory cable, or using a command from Android itself (it would have involved adb shell).
hexd said:
Please make sure that you have a Kindle Fire 2 (or at least something in the second generation Fire range). It might help if you take a picture of the device in fastboot mode and post it here.
Also did you boot the kindle into fastboot mode using a factory cable, or using a command from Android itself (it would have involved adb shell).
Click to expand...
Click to collapse
From the computer. KFF Aide. I'm still stuck I have been looking for hours.
hexd said:
A few months ago I tried to root/ gapps a KF2 for a friend, and after a freak OTA update the horrible thing kept getting stuck in a bootloop.
Basically if you powered it on it would get stuck on the Kindle pulsing logo until it restarted itself from scratch and did it all over again. Then on the few times it would get to the standard lock screen it would freeze up there and restart itself anyway.
Every now and then it would boot in and work fine though.
What I eventually did to get it working:
1.) Get a factory cable (they don't cost too much off ebay).
2.) Using fastboot mode clear the data and cache partition:
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
20 seconds later the device worked perfectly and hasn't bootlooped since.
It might also be possible to do this by a.) installing TWRP and erasing the cache/ data from there, or b.) booting into the bootloader from a rooted system. I don't want to test this though because at this point I just want to make this awful thing work properly in stock.
I hope this helps someone else in the same situation. I do remember reading a similar problem on XDA a few months ago when it started giving trouble.
Click to expand...
Click to collapse
my kindle fire hd 7 7.3.1 just went into a boot loop. it is recognized by my computer the drivers work it says device cant startup. adb wont work. how do i get it into fast-boot without a factory cable
JORDANZ1998 said:
my kindle fire hd 7 7.3.1 just went into a boot loop. it is recognized by my computer the drivers work it says device cant startup. adb wont work. how do i get it into fast-boot without a factory cable
Click to expand...
Click to collapse
Trying to do any work on a Kindle without a cable is a total pain. If you own the device just pay the few dollars to get one and make your life easier.
If you cannot get into ADB with full root, or a 3rd party recovery that was already installed you will need the cable to fix things.
I have tried several times to get CM 10.1 installed on my Kindle Fire 8.9 and every time I get the red wipe screen trying to install the 2nd boot loader. After searching through the forums I have not found a definitive explanation (not that its not out there, but i didn't find one) of what causes the red screen, just how to recover from it.
I have tried using HashCode's process
http://forum.xda-developers.com/showthread.php?t=2128175
and also Option (41) in KFFirstAide
Can someone please explain what the red wipe screen indicates on the Kindle Fire 8.9, so I can avoid it and get the 2nd boot loader installed?
My Kindle is currently running Version 8.1.4 installed from the latest KFFirstAide (option 7). I have successfully rooted the device and I have been able to recover after the red screen each time.
Device Status before attempting to install 2nd boot loader
- Rooted using B4nary's Tool (v18.5.1)
- Erased Kindle Cache and User Data
- Enabled ADB on Kindle
- Enabled Allow 3rd party software
- Verified ADB Commands can be executed
- Verified Fastboot Commands can be executed
Thank You in Advance!
Derek
drockmd said:
I have tried several times to get CM 10.1 installed on my Kindle Fire 8.9 and every time I get the red wipe screen trying to install the 2nd boot loader. After searching through the forums I have not found a definitive explanation (not that its not out there, but i didn't find one) of what causes the red screen, just how to recover from it.
I have tried using HashCode's process
http://forum.xda-developers.com/showthread.php?t=2128175
and also Option (41) in KFFirstAide
Can someone please explain what the red wipe screen indicates on the Kindle Fire 8.9, so I can avoid it and get the 2nd boot loader installed?
My Kindle is currently running Version 8.1.4 installed from the latest KFFirstAide (option 7). I have successfully rooted the device and I have been able to recover after the red screen each time.
Device Status before attempting to install 2nd boot loader
- Rooted using B4nary's Tool (v18.5.1)
- Erased Kindle Cache and User Data
- Enabled ADB on Kindle
- Enabled Allow 3rd party software
- Verified ADB Commands can be executed
- Verified Fastboot Commands can be executed
Thank You in Advance!
Derek
Click to expand...
Click to collapse
Can anyone help with this? I have been through the process numerous times and i still get the red wipe screen.
drockmd said:
Can anyone help with this? I have been through the process numerous times and i still get the red wipe screen.
Click to expand...
Click to collapse
I used this tool KFHD_SRTv2.1- 8.1.4 To get into fastboot when I had the solid red screen then used option 7 to completely wipe and restore their is probably another way to just do the boot but it did work for me (did it today even)
Turn the kindle off (hold power down)
Load the KFHD_SRTv2.1- 8.1.4 tool using run as administrator
then use option 1
once your kindle says its in fastboot then close that utility and run the First aid
drockmd said:
I have tried several times to get CM 10.1 installed on my Kindle Fire 8.9 and every time I get the red wipe screen trying to install the 2nd boot loader. After searching through the forums I have not found a definitive explanation (not that its not out there, but i didn't find one) of what causes the red screen, just how to recover from it.
I have tried using HashCode's process
http://forum.xda-developers.com/showthread.php?t=2128175
and also Option (41) in KFFirstAide
Can someone please explain what the red wipe screen indicates on the Kindle Fire 8.9, so I can avoid it and get the 2nd boot loader installed?
My Kindle is currently running Version 8.1.4 installed from the latest KFFirstAide (option 7). I have successfully rooted the device and I have been able to recover after the red screen each time.
Device Status before attempting to install 2nd boot loader
- Rooted using B4nary's Tool (v18.5.1)
- Erased Kindle Cache and User Data
- Enabled ADB on Kindle
- Enabled Allow 3rd party software
- Verified ADB Commands can be executed
- Verified Fastboot Commands can be executed
Thank You in Advance!
Derek
Click to expand...
Click to collapse
I know you said you aren't on 8.3, but it sounds like the bootloader issue Hash talks about in step 4.5 of his post. You could try flashing the bootloader he posts in that step to see if that fixes your issue. I had the same problem, until I flashed it.
Just an idea, I am in no way an expert just a tinkerer.
lizzord30 said:
I used this tool KFHD_SRTv2.1- 8.1.4 To get into fastboot when I had the solid red screen then used option 7 to completely wipe and restore their is probably another way to just do the boot but it did work for me (did it today even)
Turn the kindle off (hold power down)
Load the KFHD_SRTv2.1- 8.1.4 tool using run as administrator
then use option 1
once your kindle says its in fastboot then close that utility and run the First aid
Click to expand...
Click to collapse
I too have the red screen, I tried to use the SRtool but was unsuccessful in recovering, can u provide anymore information? i'm really freaking out a little because i'm new to this stuff
I think fattire said Amazon enabled fastboot in this state. On KF2 and KFHD7, this is possible with a factory cable. I guess it's also possible that they have enabled the use of the factory cable for the KFHD8.9, but I'm only speculating.
Before the update, flashing unsigned boot and recovery partitions without the 2nd bootloader properly functioning, the device just wouldn't turn on. Now, not only will the device turn on, but some are even fixable in this state. I'm wondering if Amazon realized that wasn't cost effective to send every broken modified device to a specific secure location to get reflashed.
I don't quite remember what I did, but I was able to fix the "red wipe" screen on my Kindle 8.9.
I think I got this when I first tried installing 8.9StariROM when it was first posted on the forum. I did not know that the red screen could appear if TWRP was not installed already, and I think that's why I got the red screen error.
I didn't really know what it was all about, but somehow I was able to make my kindle go into the fastboot using this command (fastboot -i 0x1949 getvar product) and basically followed the instruction here: http://forum.xda-developers.com/showthread.php?t=2128175
I kept getting device not found error on ADB commands, so I skipped to STEP 4.5 and ran below commands in order: (of course, I downloaded all those files as well)
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.3.0.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.4.4.0-recovery.img
then I think I ran fastboot -i 0x1949 flash system starirom-system.img to load the system image and I was able to have a working kindle 8.9 again.
I hope this helps.
Here is what I did to get myself out of trouble after screwing around with my KFHD 8.9 and getting a red screen (NOTE: I am assuming you have already installed the proper drivers so your PC can recognize the Kindle Fire HD):
1) Downloaded the above-mentioned KFHD SRT tool from here: https://docs.google.com/open?id=0B4lZEJI5lYeMR1YteUt2MGxZTGM) and the boot.img and recovery.img from here: https://drive.google.com/folderview?id=0B4lZEJI5lYeMNGdXMHI3T3pKM2c&usp=sharing
2) Unzipped the SRT tool into a folder on my Windows 7 boot drive (C:\KFHD_SRT_v2.1), and copied over the two .img files to the /images sub-folder.
3) Ran SR Tool.bat in Admin mode (right-click, Run As Administrator, click Yes to accept)
4) Turned off my Kindle by holding the power button 10 seconds until the screen was off
5) Chose option 1. Enable Fastboot, chose "n" when the tool asks if the device is turned on, then pressed the power button once on the Kindle to turn the screen on. Voilà, I was in Fastboot mode.
6) From a command line prompt (started in Admin mode as always), went to the /images sub-folder of the KFHD SRT tool and typed in the following commands, one at a time (just press Enter at the end of each, and wait until done):
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img (note: this may take a few minutes, depending on the speed of your USB port)
7) Still from the same command prompt, rebooted the tablet using the following command (type it in and press Enter):
fastboot -i 0x1949 reboot
I was back in business from there.
Can we get this as a sticky in the Dev Section? it took me 2 weeks to get my system back from a red screen that the below was able to do.
GenghisKhan67 said:
Here is what I did to get myself out of trouble after screwing around with my KFHD 8.9 and getting a red screen (NOTE: I am assuming you have already installed the proper drivers so your PC can recognize the Kindle Fire HD):
1) cant post this but look at above post.
2) Unzipped the SRT tool into a folder on my Windows 7 boot drive (C:\KFHD_SRT_v2.1), and copied over the two .img files to the /images sub-folder.
3) Ran SR Tool.bat in Admin mode (right-click, Run As Administrator, click Yes to accept)
4) Turned off my Kindle by holding the power button 10 seconds until the screen was off
5) Chose option 1. Enable Fastboot, chose "n" when the tool asks if the device is turned on, then pressed the power button once on the Kindle to turn the screen on. Voilà, I was in Fastboot mode.
6) From a command line prompt (started in Admin mode as always), went to the /images sub-folder of the KFHD SRT tool and typed in the following commands, one at a time (just press Enter at the end of each, and wait until done):
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img (note: this may take a few minutes, depending on the speed of your USB port)
7) Still from the same command prompt, rebooted the tablet using the following command (type it in and press Enter):
fastboot -i 0x1949 reboot
I was back in business from there.
Click to expand...
Click to collapse
I have a kindle fire HD 8.9, where a system framework file was edited and turns out to be bad.
When i try to boot it fails and defaults to recovery where i have two options, to reboot, or wipe data (which i have done extensively). I want to flash a full brand new system image to get the kindle like new, (note: It was on system 8.4.6 i believe) so that i can go the road of android. If possible, please leave a way to revert to an old system version.
Also, this cannot be recognized in fastboot because it boots straight to the recovery when given the fastboot command to boot to fastboot.
Much thanks.
@Hashcode (I figure youd be able to help the most)
michaelg117 said:
I have a kindle fire HD 8.9, where a system framework file was edited and turns out to be bad.
When i try to boot it fails and defaults to recovery where i have two options, to reboot, or wipe data (which i have done extensively). I want to flash a full brand new system image to get the kindle like new, (note: It was on system 8.4.6 i believe) so that i can go the road of android. If possible, please leave a way to revert to an old system version.
Also, this cannot be recognized in fastboot because it boots straight to the recovery when given the fastboot command to boot to fastboot.
Much thanks.
@Hashcode (I figure youd be able to help the most)
Click to expand...
Click to collapse
the fastboot 0x1949 getvar product doesnt seem to work now, it just shows the charging sign
michaelg117 said:
the fastboot 0x1949 getvar product doesnt seem to work now, it just shows the charging sign
Click to expand...
Click to collapse
turn off the kindle, type the fastboot command, when it says "waiting", then plugin the kindle
This is always a pain, if you have never installed the fastboot driver you will have to install the driver when it briefly appears before that command will work, that's why this process is so much easier on Ubuntu 13.10. If you boot a live CD there's no drivers to install, you just need to run a few commands, 2 for the package manager then the fastboot command itself.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
This is always a pain, if you have never installed the fastboot driver you will have to install the driver when it briefly appears before that command will work, that's why this process is so much easier on Ubuntu 13.10. If you boot a live CD there's no drivers to install, you just need to run a few commands, 2 for the package manager then the fastboot command itself.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I was able to do this with modded drivers when it popped up in device manager, after removing driver verification(stupid windows 8...) , then use one of the various tools to get into fastboot because for some reason the normal command wouldn't do the job, then i used yet another tool to revert to 8.1.4, and i am now happily running ParanoidAndroid
EDIT: Thanks for the drivers by the way!