Last night I made a Factory Reset on my kindle fire and now suddenly Its stuck on Recovery Bootmode (5001) and I cant change It with KF utility. When I try to apply the normal boot mode option it says "The system cannot find the drive specified". In the KFU main menu its says adb is online. If someone could tellme how to change my bootmode through cmd that would be great.
btw... Is there any way to completly unroot a kindle fire?
Plug kindle in, open KFU, select change bootmodes in KFU, select normal bootmode option 1, hold power button till device turns off, then power it on. Bootmode changing is not instant ignore device not found and wait longer.
sorry, thats not working. and cmd also wont recognize the adb command.
Soupkit http://forum.xda-developers.com/showthread.php?t=1850038
thanks, man. that totally worked.
Related
Just got a new KF today and tried loading Go Launcher EX. Got to the point where I rebooted the KF and told it to always boot to GO Launcher..... BIG MISTAKE... something had gone wrong in the go launcher install and Not I have a pretty Kindle Fire Logo on my screen that will not go away.
I have downloaded KFU and Installed the drivers. With my KF on and plugged into usb my device manager shows. "Android ADB Device" which if i read correctly is what it should show.
But inside KFU it does not seem to connect to the device.
Is there something i have missed or is it truly a brick ...
I tried that ... Uninstalled device (made sure to remove driver) refresh device manager.. update drivers on kindle device... Then tried KFU
All I keep getting is waiting on device...
On the main screen it says:
ADB Status: Offline
Boot Status: Unknown
When I go into the Bootmode Menu and select 1 it sits on a screen saying waiting on device.
This is pretty much where i have been stuck at all day ...
Power your kindle off by holding the power button for like 30 seconds its very likey that adb will not detect your kindle it cannot while its in fastboot But first try this shift plus right click on the tools folder in kindle fire utility select open command window here power your kindle off and enter the command Fastboot getvar product (hit enter)Plug your kindle in it will power on in fastboot If you get the response product: kindle then we can move on.
if you get the response product: kindle Type fastboot oem idme bootmode 4000 (hit enter)fastboot reboot (hit enter)
Nothing.?then Then next time try fastboot -i 0x1949 getvar product (hit enter) when it says <waiting for device> plug in your powered off device if it says product: kindle type fastboot -i 0x1949 oem idme bootmode 4000 (hit enter)fastboot -i 0x1949 reboot(hit enter)
Fastboot getvar product
fastboot -i 0x1949 getvar product
Click to expand...
Click to collapse
I tried both of these. Each time i unplugged the KF, held power for 30 secs(using a timer),typed command then hit enter, then plugged in KF.
both times it powered on and went to the Kindle Fire logo and the command window just said waiting on device. A side note is that during power on but before windows beeped as if it had recognized the device the KF logo blinked a few times.
Don't unplug it.
I've found with mine, whenever I'm stuck in fastboot I do the following:
1. LEAVE THE KF PLUGGED INTO THE COMPUTER AT ALL TIMES!
2. Uninstall all instances of the Android Device in Device Manager.
3. Power off KF by holding the power button for NO LESS than 30 seconds. Even when it looks off, keep holding it and count to 30. (keep plugged in)
4. Power on the KF by simply clicking the power button once. (still plugged in)
5. Once the KF is back at fastboot, the computer should automatically install the drivers from the KFU folder, if not then manually point it there.
6. Open KFU and start run.bat
7. At the menu, regardless of device status (mine says offline/unknown when in fastboot mode), press 1, enter, 1, enter.
so are you suggesting i do the command line stuff?
EDIT.... any way i cut it im getting the same Kindle Fire screen ...
one I used this -i 0x1949 one I didnt because sometimes it doesnt matter but lelandfried is suggesting to try to use kfu to reset your bootmode which is logical and keep working with your drivers which also makes 100% sense keep trying you could get lucky and something will work its windows darn drivers that are killing you another option is this http://forum.xda-developers.com/showthread.php?t=1670405 then you wont be messing with the drivers anymore add sudo to the front of all your fastboot commands.
If I have ubuntu running on a VM can I do this through there? I have mixed success using usb devices
whoops sorry soupmagnet will know if it will run on a vm ask him he can give you the best advice
No problem. Im going to give it a shot... I have done everything i can think of to get the right drivers on here in windows. As best as I can tell from the chart on this thread http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
I have the ADB driver loaded for Recovery,Stock SW or ROM (USB Debog On)
I think I will try the ubuntu thing for a bit .... Frustrating .. very frustrating
I gave ubuntu VM a shot. I was able to connect to the device via usb in the VMWare console then i tried to run the two commands given earlier in this thread ... but i was never able to get anything but a <waiting for device> message in the terminal window.
Hopefully someone can give me some new guidance. Or show me where im going wrong so far. I feel like its something dumb that im missing ...
did you use sudo before all your commands and plug in your prepowered off kindle in when it says waiting for device?
Deslyxia said:
I gave ubuntu VM a shot. I was able to connect to the device via usb in the VMWare console then i tried to run the two commands given earlier in this thread ... but i was never able to get anything but a <waiting for device> message in the terminal window.
Hopefully someone can give me some new guidance. Or show me where im going wrong so far. I feel like its something dumb that im missing ...
Click to expand...
Click to collapse
Soupmagnet said he had problems getting the KF to work with VMWare in fastboot mode. YMMV. I use Parallels Desktop and have no problems with it.
The most telling thing you said in this thread...
Deslyxia said:
A side note is that during power on but before windows beeped as if it had recognized the device the KF logo blinked a few times.
Click to expand...
Click to collapse
If the logo "blinked" a few times, then it's not in fastboot mode. It is most likely past the bootloader stage, loaded the boot partition and trying to start up the system. At this point, your best hope is to send it some adb commands to get the KF into fastboot or recovery, but it might not be far enough along in the process to accept adb commands either.
Read the following post about fastboot mode...
http://forum.xda-developers.com/showthread.php?t=1668159
Most people in your situation end up buying a factory cable.
Okay. thank you to everyone for the help so far. From within Ubuntu I was able to use this guide http://forum.xda-developers.com/showthread.php?t=1414832 to get into fast boot mode. From there I installed TWRP Recovery then rebooted into recovery mode. Then I installed FFF, Rebooted into recovery mode and reset to factory.
When I rebooted I got the FFF boot screen and let it boot like normal to a factory reset KF.
Again thank you all for your help .
I'm glad you got it going just make sure you do all the right things if you start flashing roms don't be afraid to ask questions its better than getting messed up again always make backups and do proper wipes just don't wipe your SD card or let your battery die good luck
I dunno how to do adb thru Ubuntu, even though I have it on my desktop. I do all my adb stuff through my Windows laptop.
Glad to hear you got it going. I'm bookmarking this thread for the Ubuntu links and info, Thanks!
I had Jandycane installed and wanted to go back to the stock rom and I guess I didn't wipe everything I should have. The Kindle now boots into what appears to be a stock rom and then I get several popup errors and then it reboots. I have tried to quickly get into the factory reset but it reboots while trying to reset. The final says that "billing is not supported on this version of android market" If I ignore the error or if I don't swipe to log in it reboots anyway after about 10-15 seconds.
I have the Kindle fire utility installed but I don't see how I could mount if the unit won't stay on.
I don't see anyway to get into TWRP. The unit goes right into the kindle fire startup, so option for bootloader.
Anything I can try?
From the command prompt, with device turned off, enter:
Code:
adb wait-for-device shell idme bootmode 4002
…then turn the device on. That should put you back in fastboot, assuming the shell still works.
soupmagnet said:
From the command prompt, with device turned off, enter:
Code:
adb wait-for-device shell idme bootmode 4002
…then turn the device on. That should put you back in fastboot, assuming the shell still works.
Click to expand...
Click to collapse
It just boots to the Kindle Fire rom and reboots.
That's all? No messages in the command window? No errors or confirmations of any sort?
soupmagnet said:
That's all? No messages in the command window? No errors or confirmations of any sort?
Click to expand...
Click to collapse
Nothing. I tried the cable in a different port and the command window doesn't change. The Kindle Fire will say a USB cable is connected after I swipe into the Fire OS. It reboots after 10 or so seconds. One of the error in the Fire OS has to do with Calender and the other with android.process.acore.
You can try the Linux approach, but I doubt it would help in your situation.
You'll probably need to get a factory cable to get the device in fastboot before you can fix anything.
All fixed.
soupmagnet said:
You can try the Linux approach, but I doubt it would help in your situation.
You'll probably need to get a factory cable to get the device in fastboot before you can fix anything.
Click to expand...
Click to collapse
Cable bought, cable received, read the forums, got into TWRP again, wiped everything, installed clean ROM, ALL BETTER.
Thanks for your help and thanks to SkOrPn for the cable.
I can get around in both windows and linux. I have rooted, flashed and modded a smartphone before (Samsung Galaxy Express) successfully.
This should be an easy one for some of you to diagnose. A fresh stock Kindle Fire (6.3.2). Trying to install KFU v0.9.6 from a Win7 (also have various flavors of linux, ubuntu, arch, debian, etc available to use if need be). ran install_drivers.bat without any problems, device showed up and was recognized. Ran run.bat. put it in fastboot mode. Kindle Fire rebooted into the "Kindle Fire" White/Orange static logo and is stuck. No animation, no powerbutton response, can't turn it off, unknown device in Win7, adb and fastboot commands return no devices.
From reading the many beginner guides and unbricking posts, I was lead to believe that I needed to put this unit in fastbootmode to do any custom work with the device, and seeing that it's #1 on the menu list of the KFU I thought this was a pre-requisite before installing anything else. Apparently this is not the case. The device comes up as a USB Unknown Device (Code 43) now, and KFU can not find the device and is waiting for the device. Can't do anything. The only clue I was able to read was possibly letting the power drain. It was full charged so I will have to wait for a while. In the meantime, I figured I would hit up the forum to see if anyone has a better suggestion.
How do I get my Kindle Fire out of FastBoot Mode?
I am right there too...
BlushNine said:
I can get around in both windows and linux. I have rooted, flashed and modded a smartphone before (Samsung Galaxy Express) successfully.
This should be an easy one for some of you to diagnose. A fresh stock Kindle Fire (6.3.2). Trying to install KFU v0.9.6 from a Win7 (also have various flavors of linux, ubuntu, arch, debian, etc available to use if need be). ran install_drivers.bat without any problems, device showed up and was recognized. Ran run.bat. put it in fastboot mode. Kindle Fire rebooted into the "Kindle Fire" White/Orange static logo and is stuck. No animation, no powerbutton response, can't turn it off, unknown device in Win7, adb and fastboot commands return no devices.
From reading the many beginner guides and unbricking posts, I was lead to believe that I needed to put this unit in fastbootmode to do any custom work with the device, and seeing that it's #1 on the menu list of the KFU I thought this was a pre-requisite before installing anything else. Apparently this is not the case. The device comes up as a USB Unknown Device (Code 43) now, and KFU can not find the device and is waiting for the device. Can't do anything. The only clue I was able to read was possibly letting the power drain. It was full charged so I will have to wait for a while. In the meantime, I figured I would hit up the forum to see if anyone has a better suggestion.
How do I get my Kindle Fire out of FastBoot Mode?
Click to expand...
Click to collapse
I am right there too...
I ordered a Factory Cable and it should be in any day now. . . .
That is what I am doing and crossing my fingers . . .
serendipityguy said:
I am right there too...
I ordered a Factory Cable and it should be in any day now. . . .
That is what I am doing and crossing my fingers . . .
Click to expand...
Click to collapse
For anyone who has run into the same problem, this is how I fixed my problem
[1] Power off the Kindle Fire and unplug. Hold down the power button for more than 10seconds. There seems to be some variance with how long you have to hold the button down.
[2] Use the Kindle Fire Utility "run.bat" in Windows. Without the Kindle Fire device plugged in, the ADB Status will be Offline and Boot Status unknown, obviously. Go into boot menu [1] and select Normal Boot [1]. It will tell you <waiting for device>.
[3] Plug in Kindle Fire device.
[4] It should reset the Kindle Fire to normal working status.
PS. I tried the power drain, but it as soon as I supplied power back to the unit it resumed its stuck boot loop condition, so nothing changed. The reason it took so long to figure out this problem was (a) I didn't know you had to hold down the power button so long. 3-5 seconds is typical for most devices to perform a hard shutdown. (b) You have to set the Kindle Fire Utility waiting to catch the Kindle Fire device booting, if it's stuck in this condition. You can't just plug it in and run the KFU while its stuck on that screen.
Also, DO NOT SELECT [1] and FastBoot Mode on a fresh stock unmodified Kindle Fire. The other install menu selections in KFU will automatically Fastboot in order to perform what they need to do.
Hope this helps others.
I had a tough time learning how to UN-brick my wife's AND my friends Kindle Fire devices. I'm going to liberally add links to things around the site because I found them extremely useful and educational, but I could not find all of the things I needed in one place. Both of the Kindle Fire devices I had to fix were Kindle Fire first generation devices, so I can only speak to these fixes. However it may help you at least get your head straight to understand what you are doing, what you have and what you need to do. My intent with both of these devices was never to root them or replace the ROM's, although I have done that to my own phones and love the Android OS, it was simply to get both working again so my wife could read and check email and my friends kids could play their games.
What I had and the issue with each device:
Kindle Fire (1) - no more space on the device, stuck at logo.
Kindle Fire (2) - originally USB connector separated from the circuit board, I had a local electronics guy solder a new one back on and upon start up it was stuck at the logo also (it worked before he fixed the board).
Utilities you need:
Kindle Fire factory cable - quality cable get one from here: http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9
Minimal ADB and Fastboot Utility: http://forum.xda-developers.com/showthread.php?p=42407269
Kindle Fire Utility 0.9.9 - get it here: http://forum.xda-developers.com/showthread.php?t=2192818
Fix the Kindle Fire Utility run.bat file - It would not run on my WinXP or Win7 machine and the fix works no matter which version you are running: http://forum.xda-developers.com/showthread.php?t=1737671
Information about TWRP, it comes with the Kindle Fire Utility: http://www.teamw.in/project/twrp2
Information about FireFireFire: http://www.xda-developers.com/android/firefirefire-custom-bootloader-for-the-kindle-fire/ FireFireFire comes with the Kindle Fire Utility and allows you to get into recovery when not connected to the computer, install FireFireFire after TWRP.
Informative video on using Kindle Fire Utility: https://www.youtube.com/watch?v=CQ21pr6_SHI
The Forum recommends reading these first, do yourself a favor and READ THESE FIRST:
Kindle Fire for Beginners (very helpful): http://forum.xda-developers.com/showthread.php?t=1552547
Kindle Fire for Beginners - Supplemental How-To Guide: http://forum.xda-developers.com/showthread.php?t=1638452
The PROCESS of UN-bricking:
1, Install Minimal ADB and Fastboot:
2, Install Kindle Fire Utility - I just put it into the Minimal ADB install directory so its all in one place.
3, In the Kindle Fire Utility directory run "install_drivers.bat" without the device connected (does not matter what version of WinXP or Win7, I have no idea if these will work on Win8 I did not try it). Reboot if you need to.
4, Plug the factory cable into your device, then plug the cable into the USB port on your computer and the Kindle Fire will boot into FASTBOOT all by itself. You can tell by the White/Orange logo and the screen is brighter than normal.
NOTE: This is the part that drove me bat crazy! With a stock Kindle Fire when using the stock bootloader (plain "kindle fire" boot logo), the fastboot command must always specify the custom vendor ID used by the Kindle Fire, ie "fastboot -i 0x1949 devices", where 0x1949 is the stock vendor ID. Also ADB and Fastboot are mutually exclusive, meaning you can only be in and use one at a time, never both. ADB commands will not work in fastboot mode or with the factory cable, you must use a regular USB cable for that and not be in fasboot mode. Even at the logo with a standard USB cable ADB would connect, but it's READ ONLY.
5, Run the Minimal ADB shortcut to the ADB prompt or open a CMD shell, navigate to the directory and run "fastboot -i 0x1949 devices". If it returns something like "0123456789ABCDEF fastboot", the number being your device number then you are in fastboot mode.
6, In the Kindle Fire Utility directory run the "run.bat" file, a CMD window with a menu will open.
NOTE:
You will see something like the below in the CMD window, ignore it, the stock Kindle Fire always shows this. If you want to make sure you are still in fastboot Run the Minimal ADB shortcut to the ADB prompt or open a CMD shell, navigate to the directory and run "fastboot -i 0x1949 devices" again and make sure your device shows up.
ADB Status: Offline
Boot Status: Unknown
7, Once Kindle Fire Utility loads, select option 3 and install TWRP, let it finish and it will reboot the device, hit enter back to the main menu. The logo will not change yet.
8, Once Kindle Fire Utility loads, select option 5 and install FireFireFire, let it finish and it will reboot the device, hit enter back to the main menu. The logo will still be white and blue logo.
9, Once Kindle Fire Utility loads if you want to root select 2 "Install Permanent Root with Superuser", let it finish and it will reboot the device, hit enter back to the main menu. The logo will still be white and blue logo.
10, Hold the power button until the device shuts down, unplug the factory cable from the computer, then the device.
11, Tap the power button and the device should start to boot. At the bottom you will see the boot select prompt, hold power button a couple of seconds and a menu should pop up. Tap the power button to change menu item until recovery is selected "--Recovery--" and leave it until it boots into TWRP.
12, Once you boot into TWRP select WIPE,
13, On the bottom of the next screen swipe "Swipe to factory reset", let it finish and select the back button.
14, Select REBOOT and then SYSTEM (this resets Fastboot mode to 4000 if you changed it to 4002 or screwed with it otherwise).
15, At one point I was asked if I want to root it and install SU. On my wife's I did and on my friends I did not, kids have a habit of pushing the right combination of buttons and bricking them. I don't recall when it actually asked me to do the root, but it probably has to do with me doing step 9 above on one and not the other.
16, After it reboots and it takes a while the first time again, reconfigure your Factory Stock Kindle Fire as you would out of the box. All of your stuff will synch back to it, unless you used a USB cable to transfer data to it, that stuff may be gone, but I did not have any of that to worry about.
17, Since the Kindle was already registered both your Kindle books and Amazon apps should be there but you will have to reinstall the apps and lose saved game data.
Again, this is how I chose to do the repair based on my knowledge level (and frustration level) after a lot of research, reading, testing and rebooting. Like I said, all I wanted was a stock fresh Kindle Fire, so this worked for me. I might at some point wipe it and install a custom ROM and Kernel but for now they are both grateful and happy to have their devices back without buying new ones.
Also, I am grateful to all the people who posted here before me that allowed me to learn more about the Android OS devices and repair them. It was actually a fun and frustrating adventure, but the thrill of beating it into submission was well worth the learning curve on another device!!!
Jocco-
So here's what happened.
About a year ago, I rooted my Kindle and flashed CM 10.1. Everything worked out great.
Fast forward to a few days ago, I thought it'd be cool to give the KF an update. Total mistake. I wanted to flash CM 11, but figured it'd be important to install the latest version of TWRP as well. Before I knew it, my Kindle Fire was bricked. In the process of updating TWRP, I downloaded and flashed the most recent img file (using Flashify), and after the device rebooted automatically, it wouldn't move past the silver/orange "Kindle Fire" screen. I've since tried a number of things, including powering the device on and off, and holding the volume up button to boot into TWRP, but nothing seems to work. I always end up getting stuck at the same screen.
I've also tried using Kindle Fire Unbrick Utility, but I get a "device not found" message. My computer makes a noise, as if to recognize the KF when it powers on, but within seconds, loses communication.
Am I screwed?
arthurk62 said:
So here's what happened.
About a year ago, I rooted my Kindle and flashed CM 10.1. Everything worked out great.
Fast forward to a few days ago, I thought it'd be cool to give the KF an update. Total mistake. I wanted to flash CM 11, but figured it'd be important to install the latest version of TWRP as well. Before I knew it, my Kindle Fire was bricked. In the process of updating TWRP, I downloaded and flashed the most recent img file (using Flashify), and after the device rebooted automatically, it wouldn't move past the silver/orange "Kindle Fire" screen. I've since tried a number of things, including powering the device on and off, and holding the volume up button to boot into TWRP, but nothing seems to work. I always end up getting stuck at the same screen.
I've also tried using Kindle Fire Unbrick Utility, but I get a "device not found" message. My computer makes a noise, as if to recognize the KF when it powers on, but within seconds, loses communication.
Am I screwed?
Click to expand...
Click to collapse
Can you get into fastboot? Did you restore your backup?
Don't worry you must have flashed TWRP for the wrong kindle generation.
Connect your kindle to your pc with the normal cable that is provided with your kindle. Now turn your kindle off and type the following in your cmd
fastboot -i 0x1949 getvar product
now it should show
< waiting for device >
then turn on your device
you should be in fastboot now.
From here follow this thread from step 2
forum.xda-developers.com/showthread.php?t=2128175
skullarc said:
Don't worry you must have flashed TWRP for the wrong kindle generation.
Connect your kindle to your pc with the normal cable that is provided with your kindle. Now turn your kindle off and type the following in your cmd
fastboot -i 0x1949 getvar product
now it should show
< waiting for device >
then turn on your device
you should be in fastboot now.
From here follow this thread from step 2
forum.xda-developers.com/showthread.php?t=2128175
Click to expand...
Click to collapse
I had a feeling that must've been the case.
I followed your directions, but can't get past the "<waiting for device> message in CMD. Turning the kindle on or off doesn't seem to make a difference. Am I doing something wrong? Are there other alternatives?
Did you follow the steps in the right order
Turn of Kindle
connect the wire
type command
when waiting for device is shown then only turn on your kindle
Similar Problem
skullarc said:
Don't worry you must have flashed TWRP for the wrong kindle generation.
Connect your kindle to your pc with the normal cable that is provided with your kindle. Now turn your kindle off and type the following in your cmd
fastboot -i 0x1949 getvar product
now it should show
< waiting for device >
then turn on your device
you should be in fastboot now.
From here follow this thread from step 2
forum.xda-developers.com/showthread.php?t=2128175
Click to expand...
Click to collapse
I have a similar problem. I try to give the "fastboot -i 0x1949 getvar product" in windows cmd but it just gves an error. Do I need to install something to fix this
My guess is you don't have the right drivers installed. You have to install the driver while the device is attempting fastboot. If you have the device manager up you'll see it flash for a second when it boots. Right click when it flashes and install the driver.