[Q] Attempting to Root, stuck at "Setting Recovery Bootmode. Please Wait..."
Okay, so I decided to root my Kindle Fire, figuring it wouldn't be too complicated. I'm generally great at technical stuff, and if I don't know how to do something then I learn quickly. But I can't figure out what, if anything, I'm doing wrong.
I have downloaded and extracted KFU, installed the drivers, and run the .bat with no problems. However, when I begin the permanent root process, it activates fastboot, installs TWRP, and then nothing. It gets to where it says "Setting Recovery Bootmode. Please wait..." and it doesn't get any further. I've been waiting for maybe an hour now? Surely it's not supposed to take that long, what's going on?
I just realized I put this in the wrong thread, I apologize for that lol.
http://forum.xda-developers.com/showthread.php?p=23747567
http://forum.xda-developers.com/showthread.php?p=23747671
http://forum.xda-developers.com/showthread.php?p=23747804
Will give you some insight to your problem and how to fix it.
Those links all lead to the same page? Thanks though, that helps me understand what SHOULD be happening, but I still don't know why it isn't working..
Well, let's start with...When you turn the device on, what happens?
Uh, what exactly do you mean? It'll turn on just fine if I stop the root and set it back to normal mode. While it's plugged in attempting to do that it just sits at the kindle fire logo.
The links that I gave you point to different posts from the same guide, but I'm learning today that the XDA app has trouble with multiple post links from the same thread.
But, that's not important right now. What is important, is the reason I directed you to that page in the first place. True, it does give you an idea of what's supposed to happen, but it also tells you about the different bootmodes and what it means when you are stuck at the Kindle Fire logo, along with a whole host of other things.
It is very important for you to understand this because it will aid you in understanding that your "problem" is not really a problem at all and that your Kindle is doing exactly what it's supposed to do.
Knowing this, your issue should be relatively easy to fix. I would suggest you go back over that thread and try to get an idea of what's going on.
I understand that it's in fastboot mode. Like it should be. I understand what recovery mode is and does. What I don't understand is why it is taking so long to get past this particular step of the rooting process. My issue isn't that it's stuck on the boot screen and I don't know how to get past that. My issue is that it won't root. After installing TWPR, when it says "Setting Recovery Bootmode" blah blah blah, which I'm guessing means it is setting up TWPR to do what it should do, it doesn't get any further. KFU just stops, telling me to "Please wait..." for hours.
Also, if any of that comes off as rude or anything, I don't intend for it to sound that way lol. I do appreciate your help. I'm just a bit frustrated with this.
1. Which Kindle Fire logo is it booting to, stock or KF w/android
2. Are you familiar with the command line interface?
You need to see if TWRP was ever installed in the first place. Enter the command to set it to recovery:
fastboot -i 0x1949 oem idme bootmode 5001 (for stock bootloader)
or
fastboot oem idme bootmode 5001 (for FFF KF w/android)
...then reboot
If it boots into recovery then all you need to do is install FFF (if it isn't already)
If it doesn't boot into recovery you need to install it manually.
It boots to the logo with the android.
And I am familiar with that, yes. I messed around with some of the commands after reading through the page you linked me to, but it doesn't recognize the commands I enter. I know that you are supposed to change the directory, and I did that, but it still didn't work. I dunno if I'm just not going to the right place, or I have the folder saved somewhere that won't work (which would be my desktop), or if I'm just dumb and doing it completely wrong. I will try those commands now, though.
kodasaur said:
It boots to the logo with the android.
And I am familiar with that, yes. I messed around with some of the commands after reading through the page you linked me to, but it doesn't recognize the commands I enter. I know that you are supposed to change the directory, and I did that, but it still didn't work. I dunno if I'm just not going to the right place, or I have the folder saved somewhere that won't work (which would be my desktop), or if I'm just dumb and doing it completely wrong. I will try those commands now, though.
Click to expand...
Click to collapse
You need to fix your drivers
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
The problem is explained in detail here:
http://forum.xda-developers.com/showthread.php?p=25444709
...also, in that thread, I think gedemis has made a fix for the driver issue, though I'm not sure how well it works.
The drivers are installed properly, it shows up in the device manager as "Android Composite ADB Interface". Still not getting anything.
kodasaur said:
The drivers are installed properly, it shows up in the device manager as "Android Composite ADB Interface". Still not getting anything.
Click to expand...
Click to collapse
Does any device appear when you enter this? With those drivers, the Kindle should be able to be detected, and you can flash the bootloader.
Code:
fastboot devices
I'm sorry, I guess I should have explained it a little better.
When your computer cannot communicate with your device, 99.99999% of the time it's caused by the drivers, regardless of what Windows says. Sometimes you can just reinstall over the old ones, but you usually have to uninstall (and delete if possible) the old ones, reboot the computer and reinstall the drivers manually. The first link I gave you has detailed instructions on how to install your drivers. The second link that I gave you explained the problem in detail and provided information for making sure your drivers are configured properly.
In rare cases, switching out your USB cable or trying different USB ports is enough to fix the problem but chances are, it's more likely to be the drivers.
Go back, read, and make absolutely sure you've done EVERYTHING you can to fix your drivers because based on what you've told us, that's probably what your problem is.
Now, on the chance that you have actually done this but are having trouble communicating it effectively, we are going to need some more detailed information as to what steps you have taken to enter the above posted "fastboot" commands and, if any, what type of error messages you've received.
The more detail you're able to provide, the better, as it will help us pinpoint your exact problem and eliminate any possibility of user error.
But it IS commumicating with the Kindle? At least up until that step. It does everything else that it's supposed to.
I've uninstalled the drivers and manually reinstalled them. I don't know what else to do.
Where exactly am I supposed to enter these commands? I keep getting "fastboot is not a recognized internal or external command, operable program, or batch file"
kodasaur said:
But it IS commumicating with the Kindle? At least up until that step. It does everything else that it's supposed to.
I've uninstalled the drivers and manually reinstalled them. I don't know what else to do.
Where exactly am I supposed to enter these commands? I keep getting "fastboot is not a recognized internal or external command, operable program, or batch file"
Click to expand...
Click to collapse
Shift+right click on the KFU "tools" folder containing fastboot.exe and select "Run in Command..."
The prompt that opens up will be where you enter your fastboot commands. Make sure you understand the command before you enter it, especially if it involves the bootloader.
Okay, thanks. When I use that command, it returns either a series of question marks, or "0123456789ABCDEF". Which I now see means that it's in fastboot mode. Now what?
When it returns 123456789ABCDEF enter the following command
fastboot -i 0x1949 oem idem bootmode 4000
...then reboot
When I do that I get
... FAILED (remote failure)
kodasaur said:
When I do that I get
... FAILED (remote failure)
Click to expand...
Click to collapse
Sorry, typo...
fastboot -i 0x1949 oem idme bootmode 4000
Alright, that worked lol. After rebooting?
Related
Hi XDA Community!
Completely bone-headed n00b here (is there any other kind)?
Firstly, a quick background:
HTC Desire, rooted, S-Off, 16 gig Class 4 SD card with 1 gb ext4 partition
I was flashed with a perfectly working Leedroid 2.2f rom, overkill backed up with Clockwork, AmonRa, Titanium, MyBackup Pro, complete SD card backup (you name it, I did it), then wiped and flashed ownhere's Rom because I was running out of app space. The flash was successful then I proceeded to backup ownhere's rom after re-installing all my apps and I think that's where the problem began. I began my first backup with Clockwork via Rom Manager, but was not getting any response, so I rebooted my phone into Clockwork Recovery and backed up ownhere's rom there. After that, I could not turn on my phone.
I'd appreciate if someone could point me in the right direction. As of right now, my phone goes into a vicious boot loop whenever I try to turn it on. I can still get into hboot by holding down the power button and volume down button and then get into Android system recovery (Amon Ra Recovery, build: RA-desire-v2.0.0) by selecting "recovery", but when I try to do a nandroid restore, the error message I get is:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount SDCARD:/nandroid/
I've googled many times and have attempted to follow the steps outlined by various tutorials with similar sounding problems, but unfortunately to no avail. I've tried formatting my SD card on my computer, re-partitioning the SD card on my phone (not sure if that was successful), wiping it, attempting to restore it, attempting to flash it, but I keep getting that same error message above in the end.
I certainly don't deserve it after what I've done, but any help would be greatly appreciated! Thanks for having the patience to read.
EDITED: Below are the steps I took to resolve the issue.
First and foremost, I'd like to point out that prior to encountering this problem (or any problem for that matter), I did a very thorough job of backing up my entire phone multiple times through various methods, but it turns out I only really needed a single nandroid backup and mariosraptor's help. Still, better safe than sorry, I say, which is ironic considering what I did to my phone. Ah well.
Anyway, after running into my problem as described in my OP (original post), the following steps were needed to restore functionality to the phone:
1) With the phone turned off, I booted it into Fastboot by either a) holding down volume rocker+power on button, then choosing "fastboot" or b) holding back button+power on button, which takes you straight into "fastboot".
2) Once in fastboot, I connected my phone to my computer via USB cable.
3) I'm not sure if I needed it running or not, but I then ran Android SDK (a program I used back when I first got my phone and was tinkering with rooting and forcing apps to install onto the SD card before I learned about SD card partitioning and AP2SD/AP2SD+ supported roms and now DATA2SD/DATA2EXT). This program can be downloaded here and an example of how it's used is here, but I'm assuming (I know I shouldn't assume, but I can only describe things I've done or have already done) anyone who as gotten this far already has this program and used it before, even with limited knowledge.
4) I then went into my Start Menu in Windows and ran command prompt. The simplest way to run command prompt, I find, is to type "cmd" into the run dialog, then enter.
5) Once command prompt popped up, I typed in cd\ to change the directory to C:\ and then entered in cd android-sdk-windows/tools to open the directory to c:\android-sdk-windows\tools (I just noticed that you enter in /backsplashes, but end up with \forwardslashes, weird!).
6) I then typed in the fastboot commands as outlined by mariosraptor, that is, I entered "fastboot oem enableqxdm 0" pressed enter, let it finish, then typed in "fastboot reboot" and enter. Wait for phone to reboot, could take a while.
I'm hoping for most people those are all the steps needed in order to restore the phone, but in my case, after entering "fastboot oem enableqxdm 0", I received an error saying: "The program can't start because AdbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem." I was about to re-install when mariosraptor provided me with the AdbWinApi.dll file here. This is rapidshare link so it will expire. My suggestion is to search for it somewhere (google) if you run into the same missing file as me.
My problem actually didn't stop there either. I found my phone was stuck on the boot animation, although I supposed I could've left it even longer just to make sure it wasn't working, but I actually took my battery out to shut the phone down. I then proceeded to do a nandroid restore to a previous backup I had done before I created this whole problem. I did that by booting the phone into recovery by holding down volume rocker+power button, selecting "recovery", then selecting "nandroid backup/restore" and letting the process go through fully, which took quite some time.
Anyway, it's been a long 20 or so hours for me. I'm going to go rest now. Props again to mariosraptor!
in fastboot mode through adb cmd
fastboot oem enableqxdm 0
fastboot reboot
as long as you are S-off you can use fastboot commands and it is recommended that whatever you do from the moment that youre S-off'd you use fastboot and adb for various works on your Desire.
for more fastboot commands in adb just type fatboot
Hey mario, thanks for the quick reply.
I'm currently reading ADB for Dummies to figure out what you're talking about and will get back to you. I know I've used it before when I rooted my phone, but I was just following step-by-step instructions and had no idea what I was doing.
I recall seeing "unknown device" in device manager while my phone was plugged into my computer via USB during one of my recent attempts at fixing my current issue.
PS. I'm on Windows 7.
So I haven't been able to get far. I've noticed all the ADB commands that need to be entered in command prompt require me to have my phone in "USB debugging mode" by going into in Settings>Applications>Development, but I can't even turn on my phone to get there.
Am I missing something from your instructions? Sorry, my knowledge is quite limited.
When you are in Amonra, you are automaticly in "adb mode" so you can ignore that step. You should however install htc sync for the drivers needed.
turn off your phone by removing battery. press the back button+power on. you are in fastboot mode. the correct cmd's are fastboot commands.
like "fastboot reboot-bootloader" w/o the quotes.
ayato kamina said:
So I haven't been able to get far. I've noticed all the ADB commands that need to be entered in command prompt require me to have my phone in "USB debugging mode" by going into in Settings>Applications>Development, but I can't even turn on my phone to get there.
Am I missing something from your instructions? Sorry, my knowledge is quite limited.
Click to expand...
Click to collapse
Gotcha, I was able to get into "fastboot USB" by following your back button+power on (or down volume+power, then selecting fastboot) and connecting a USB cable to from the phone to my computer. I then went into command prompt (cmd) in the start menu. Typed in:
1) cd\
2) cd android-sdk-windows\tools
3) entered in "fastboot oem enableqxdm 0"
I then received the error message: The program can't start because AdbWinApi.dll is missing from you computer. Try reinstalling the program to fix this problem.
That will be my next step is to re-install Android SDK Windows.
Will report back, thanks!
Lennyz1988 said:
When you are in Amonra, you are automaticly in "adb mode" so you can ignore that step. You should however install htc sync for the drivers needed.
Click to expand...
Click to collapse
Thanks for pointing that out, Lenny. I didn't know that. I'm not sure if I have the HTC Sync drivers, but in fastboot mode (as instructed by mario), I checked device manager in properties of My Computer and the unknown device exclamation icon is gone. I see, ADB interface>HTC Bootloader.
http://rapidshare.com/files/380196682/AdbWinApi.dll
donload it from the link and put in tools foder of SDK
mariosraptor said:
http://rapidshare.com/files/380196682/AdbWinApi.dll
donload it from the link and put in tools foder of SDK
Click to expand...
Click to collapse
Phew! Thanks Mario! I was struggling to re-install Android SDK for some reason. A problem with Java SE JDK. *shrugs*
Will continue now....
i hope it helps. i will see more tomorrow. good luck!!!
ayato kamina said:
Phew! Thanks Mario! I was struggling to re-install Android SDK for some reason. A problem with Java SE JDK. *shrugs*
Will continue now....
Click to expand...
Click to collapse
PROGRESS!!
So I'm finally passed the S-off splash screen and am waiting on the boot animation screen. I expect there to be a problem because I've been formatting and partitioning my SD card so much, the card itself may actually be empty at the moment (not sure). I will wait for while and if nothing changes, I'm going to restore my SD card and try again.
Thanks for getting me this far so far, Mario! Much appreciated!
just let see what happens and hopefully it will work again.
ayato kamina said:
PROGRESS!!
So I'm finally passed the S-off splash screen and am waiting on the boot animation screen. I expect there to be a problem because I've been formatting and partitioning my SD card so much, the card itself may actually be empty at the moment (not sure). I will wait for while and if nothing changes, I'm going to restore my SD card and try again.
Thanks for getting me this far so far, Mario! Much appreciated!
Click to expand...
Click to collapse
mariosraptor said:
in fastboot mode through adb cmd
fastboot oem enableqxdm 0
fastboot reboot
as long as you are S-off you can use fastboot commands and it is recommended that whatever you do from the moment that youre S-off'd you use fastboot and adb for various works on your Desire.
for more fastboot commands in adb just type fatboot
Click to expand...
Click to collapse
my phone is connected,drivers are installed and it is available in fastboot. But when I am typing "fastboot oem enableqxdm 0" it returnes: "... FAILED (status malformed (1 bytes))" and nothing happens.
could u help pleas?
mariosraptor said:
just let see what happens and hopefully it will work again.
Click to expand...
Click to collapse
YES! I can finally turn on my phone again! Thanks so much, Mario! You are a genius and thank you for being so patient with me.
This is what happened:
I waited a while and the phone remained stuck on the boot animation so I took the battery out and completely restored all my files onto my partitioned SD card. I tried booting again with similar results so I tried running a nandroid restore to a previous Leedroid rom from Amon Ra Recovery and no longer received the cannot mount message so the restore was finally able to execute and after a lengthy boot process, I'm up and running again!
Thanks again so much! Once more, I could not have done it without your help. I'm going to see how stable it is, but it looks very good. By tomorrow if I'm still up, I will re-edit my first post with the exact steps I took to remedy my particular problem.
May I have your paypal email address?
persianblue said:
my phone is connected,drivers are installed and it is available in fastboot. But when I am typing "fastboot oem enableqxdm 0" it returnes: "... FAILED (status malformed (1 bytes))" and nothing happens.
could u help pleas?
Click to expand...
Click to collapse
Sorry to hear that, persianblue. In light of your problem, I will write the solution right now, although it sounds like a you're getting a different error message than I did after entering the fastboot command. Regardless, I will post the step-by-step instructions because there's no guarantee you did exactly what I did to recover my phone.
I'll have it up shortly.
SOLUTION
copied and pasted from the first post:
Below are the steps I took to resolve the issue.
First and foremost, I'd like to point out that prior to encountering this problem (or any problem for that matter), I did a very thorough job of backing up my entire phone multiple times through various methods, but it turns out I only really needed a single nandroid backup and mariosraptor's help. Still, better safe than sorry, I say, which is ironic considering what I did to my phone. Ah well.
Anyway, after running into my problem as described in my OP (original post), the following steps were needed to restore functionality to the phone:
1) With the phone turned off, I booted it into Fastboot by either a) holding down volume rocker+power on button, then choosing "fastboot" or b) holding back button+power on button, which takes you straight into "fastboot".
2) Once in fastboot, I connected my phone to my computer via USB cable.
3) I'm not sure if I needed it running or not, but I then ran Android SDK (a program I used back when I first got my phone and was tinkering with rooting and forcing apps to install onto the SD card before I learned about SD card partitioning and AP2SD/AP2SD+ supported roms and now DATA2SD/DATA2EXT). This program can be downloaded here and an example of how it's used is here, but I'm assuming (I know I shouldn't assume, but I can only describe things I've done or have already done) anyone who as gotten this far already has this program and used it before, even with limited knowledge.
4) I then went into my Start Menu in Windows and ran command prompt. The simplest way to run command prompt, I find, is to type "cmd" into the run dialog, then enter.
5) Once command prompt popped up, I typed in cd\ to change the directory to C:\ and then entered in cd android-sdk-windows/tools to open the directory to c:\android-sdk-windows\tools (I just noticed that you enter in /backsplashes, but end up with \forwardslashes, weird!).
6) I then typed in the fastboot commands as outlined by mariosraptor, that is, I entered "fastboot oem enableqxdm 0" pressed enter, let it finish, then typed in "fastboot reboot" and enter. Wait for phone to reboot, could take a while.
I'm hoping for most people those are all the steps needed in order to restore the phone, but in my case, after entering "fastboot oem enableqxdm 0", I received an error saying: "The program can't start because AdbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem." I was about to re-install when mariosraptor provided me with the AdbWinApi.dll file here. This is rapidshare link so it will expire. My suggestion is to search for it somewhere (google) if you run into the same missing file as me.
My problem actually didn't stop there either. I found my phone was stuck on the boot animation, although I supposed I could've left it even longer just to make sure it wasn't working, but I actually took my battery out to shut the phone down. I then proceeded to do a nandroid restore to a previous backup I had done before I created this whole problem. I did that by booting the phone into recovery by holding down volume rocker+power button, selecting "recovery", then selecting "nandroid backup/restore" and letting the process go through fully, which took quite some time.
Anyway, it's been a long 20 or so hours for me. I'm going to go rest now. Props again to mariosraptor!
Click to expand...
Click to collapse
Congrats mate. nice to hear that you are up and running again. this is what the community does. Help each other!!!
mariosraptor said:
Congrats mate. nice to hear that you are up and running again. this is what the community does. Help each other!!!
Click to expand...
Click to collapse
Absolutely! I'm discovering that firsthand thanks to you. Again, I appreciate your help. I had spent soooo much time trying to figure it out on my own and you were able to help me right away.
You sir, are a class act!
So it's been over a full day since my personal debacle and I'm happy to say my phone is still up and running . There has been, however, one abnormality. It's not a huge issue in the long run as I can still use the phone as I normally do, but I've noticed whenever I plug my micro-usb cable into my phone (with the other end either connected to a computer or a power outlet), there is a noticeable delay before it starts charge. Also, when connected to a computer, I'm no longer receiving the prompt for 1) charge only 2) mount sd card 3) sync 4) etc etc.
The icon in the top left that normally pops up doesn't show either when I have it connected to computer. Again, not a big deal in the long run, but obviously it can be a nuisance not being able to transfer files b/t my phone and computer via this method anymore. Not sure if anyone else has encountered this issue. I'm using the same cable, same computer. My next step is to try it on a diff computer, then eventually a different cable and hopefully that might be the issue.
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 )
After succesfully rooting my Kindle, I flashed a JB bulid. About a month later wanting to flash an update I noticed I have no recovery and no more FFF boot logo. I tried usiong KFU, but nothing worked. After searching through pages and pages, I decided to uninstall drivers as many have suggested, and delete, then reinstall kfu. I finally got it working again. I flash another rom, and two weeks later, no recovery or fff.
I repeated my steps to no avail. Trying KFU, or getting into fbmode, leave me nowhere, but with a cmd prompt screen with waiting for device.
On KFU my ADB status is online and Boot status 4000
When trying to install FFF I get: failed to copy 'files\fbmode' to data/local/fbmodeermission denied
Unable to chmod /data/local/fbmode: No such file or directory
/system/bin/sh: /data/local/fbmode:not found
Same when trying to install TWRP. When screen prompt initiates fbmode reboot, it boots into normal os.
adb devices gives me this reading 0123456789ABCDEF.
While trying Pokey 9000's fbmode, I was able to enter fbmode, but trying to install TWRP again left me with Waiting for device..
Any help/suggestions would be appreciated.
I'm not sure if /data/local/ is user writable. I've always used /data/local/tmp/ for this purpose. Here are some manual instructions to get TWRP and FFF installed manually...
http://forum.xda-developers.com/showthread.php?t=1638452
Fastboot mode uses a different interface than adb, so your Windows box may not have the drivers properly installed for it even if adb is working. You might also have to force the KF off by pressing/holding the power for 20 seconds or so and then restart it because both the host and the KF must see the other the moment the device goes into fastboot mode. Check the second post for help on getting the device drivers working properly...
http://forum.xda-developers.com/showthread.php?t=1552547
I tried pokey's fbmode which worked. Now I'm stuck in fbmode and can't get out.
When trying to flash TWRP it would not pass waiting for device
When I connect to my pc, a propmt states device is unrecognizable.
Device manager only shows USB Mass Storage with exclamation.
ADB does not recognize device
Here try this iso*http://db.tt/KDNzyCTP
*Instructions:*
1. Download this http://www.pendrivelinux.com/
2. Download iso
3. Preformat usb in windows
4. Select try unlisted Linux iso from the very bottom of dropdown in universal usb installer
5. Select iso
6. Select usb drive letter
7. Tick format
8. Create
9. Eject safely and remove
10. Shut down computer
11. Insert and power on computer
12. Select boot from usb and use..
All you need is a 2 gig usb flash drive to create this live linux adb and fastboot are preconfigured
different build but thread found here http://forum.xda-developers.com/showthread.php?t=1882565
kinfauns said:
I'm not sure if /data/local/ is user writable. I've always used /data/local/tmp/ for this purpose. Here are some manual instructions to get TWRP and FFF installed manually...
http://forum.xda-developers.com/showthread.php?t=1638452
Fastboot mode uses a different interface than adb, so your Windows box may not have the drivers properly installed for it even if adb is working. You might also have to force the KF off by pressing/holding the power for 20 seconds or so and then restart it because both the host and the KF must see the other the moment the device goes into fastboot mode. Check the second post for help on getting the device drivers working properly...
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
Windows,Windows,Windows...Why must I reboot so much!
After installing/Unstalling drivers, many reboots, and unplugging/plugging in usb, I've finally got it fixed. Big thanks for those guides. Everything I needed was right there, except my pc was being a real d***head about these drivers.
I uninstalled faulty USB mass storage drivers then reinstalled, and it recognized my device immediately
Now that I have it fixed, any insight on why I lost TWRP and FFF. I would hate for this to be a recurring issue. Especially if I have to wait for my pc to play ball..
I really dont know what you did to wipe fff and twrp but I would say that your case is extremely rare in fact Im sure there is great debate about whether it is even truly possible... And if you were able to duplicate it would be quite impressive... It certainly wouldnt hurt to flash a little smirkit when you change roms if you do it frequently http://forum.xda-developers.com/showthread.php?t=1500935 as far as I know the only thing that will wipeout fff and twrp like that is update.zip your case I believe is only the 3rd that I have ever heard this happening to. I can almost say with at least 98 % certainty that one of those occasions was purely user error.......
Thepooch said:
I really dont know what you did to wipe fff and twrp but I would say that your case is extremely rare in fact Im sure there is great debate about whether it is even truly possible... And if you were able to duplicate it would be quite impressive... It certainly wouldnt hurt to flash a little smirkit when you change roms if you do it frequently http://forum.xda-developers.com/showthread.php?t=1500935 as far as I know the only thing that will wipeout fff and twrp like that is update.zip your case I believe is only the 3rd that I have ever heard this happening to. I can almost say with at least 98 % certainty that one of those occasions was purely user error.......
Click to expand...
Click to collapse
I'm not too sure if I lost TWRP, but I know I lost fff. Kfu and fastboot wasn't working. I know when things like this happen, usually a step was missed.
Sent from my HTC Sensation using xda premium
I read the guide and have been browsing the forums for similar situations.
First of all, many months ago I tried to root my KF with something named "doomlord"? I basically googled how to root, picked one, went at it. It ran fine, though I don't recall trying to do anything with the root. Most recently every time I powered it on, I was in the CWMR menu. I tried to install the latest kindle update from amazon (changed it to .zip, placed it in the folder, tried to install from cwmr menu), to get it back to stock. Didn't work, and the only way I was able to use my kindle was wiping everything and rebooting. I became frustrated and started to try anything I hadn't, I clicked fastboot mode. Now it's been stuck at the yellow triangle, does nothing when power is pressed, isn't recognized by my mac.
Many users had my similar situation but I truly am a newbie and went at this with no knowledge, though I do know some terms through the guide. It seems I'm stuck in a bootloop, and my kindle isn't truly broken for good.
What I want to know, in basic terms:
What do I need to download?
To send commands.. do I use terminal? Seems like I need to get 'fastboot' and 'adb'
I've also seen references to getting kindle fire utility- can I use this even though I used some random doomlord program and it's using CWMR?
How to 'flash' something?
Simple, step by step instructions would be SO APPRECIATED! I apologize for having a question everyone else has asked, but I feel so frustrated at this point.
Anybody?
So far, I have downloaded KFU, adb, fastboot, and FFF 1.2.
I've tried many commands to see if my kindle is in fastboot, it does not seem to be. All commands come back with "-bash: fastboot: command not found". I also am going into the directory of "android" where I put adb and fastboot. I think that is correct.
Not sure what to do with KFU, or FFF that I've downloaded.
Should I wait for the battery to drain? Though I don't think that will fix the problem at all.
Kindle still not being recognized by my mac.
At this point I will just pay somebody to help me successfully fix this or send it out. But if it's as easy as the solutions make it seem, I'd love to just do it myself. I think I'm just confused about what exact steps I need to make, whether that is flashing FFF or TWRP?
Whatever you do, don't let the battery drain.
Make sure you have your driver installed and configured correctly:
Code:
cat ~/.android/adb_usb.ini
The only acceptable output is "0x1949".
Next, try to take advantage of the temporary fastboot mode that comes with FireFireFire (yellow triangle).
Hold the power button to shut the device down and enter the following:
Code:
fastboot getvar product
Restart the KF when you see "waiting for device".
Give it a second to boot and you should get an output of "kindle" in the terminal. If you do, repeat the previous step with the following commands:
Code:
fastboot oem idme bootmode 5001
fastboot reboot
That should boot you into recovery again. (but you're not quite finished yet, we'll see if you can get this far first)
If that doesn't work, you should get a Linux LiveUSB (if you have a PC to use) or a VM (only Parallels will work with fastboot) to run Linux, and install and run Firekit. Depending on your Mac, it is possible, albeit very tricky, to get it to boot to a LiveUSB...but I wouldn't count on it. You might need to use the shorting trick to temporarily put the device in USBboot so Firekit can install a new bootloader (see Firekit thread).
soupmagnet said:
Whatever you do, don't let the battery drain.
Make sure you have your driver installed and configured correctly:
Code:
cat ~/.android/adb_usb.ini
The only acceptable output is "0x1949".
Next, try to take advantage of the temporary fastboot mode that comes with FireFireFire (yellow triangle).
Hold the power button to shut the device down and enter the following:
Code:
fastboot getvar product
Restart the KF when you see "waiting for device".
Give it a second to boot and you should get an output of "kindle" in the terminal. If you do, repeat the previous step with the following commands:
Code:
fastboot oem idme bootmode 5001
fastboot reboot
That should boot you into recovery again. (but you're not quite finished yet, we'll see if you can get this far first)
If that doesn't work, you should get a Linux LiveUSB (if you have a PC to use) or a VM (only Parallels will work with fastboot) to run Linux, and install and run Firekit. Depending on your Mac, it is possible, albeit very tricky, to get it to boot to a LiveUSB...but I wouldn't count on it. You might need to use the shorting trick to temporarily put the device in USBboot so Firekit can install a new bootloader (see Firekit thread).
Click to expand...
Click to collapse
Thanks so much for trying to help out. No dice, though. Your directions seem fairly simple and straightforward. I'll tell you what I did step by step-
First I connected KF to my mac, the yellow triangle appears. I go into the directory where adb is. I'm not sure what you meant by which drivers should be installed properly, but I put in the following into terminal:
Code:
cat ~/.android/adb_usb.ini
As a result I got:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
This seems about right. I shut it down, and tried to input "fastboot getvar product". That is when I get the "-bash: fastboot: command not found". I feel really dumb right now. It really seems so simple but I'm just not getting it. I added a screenshot if that would give you any clue as to why even the first step isn't working. Thank you
2hellwu said:
Thanks so much for trying to help out. No dice, though. Your directions seem fairly simple and straightforward. I'll tell you what I did step by step-
First I connected KF to my mac, the yellow triangle appears. I go into the directory where adb is. I'm not sure what you meant by which drivers should be installed properly, but I put in the following into terminal:
Code:
cat ~/.android/adb_usb.ini
As a result I got:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
This seems about right. I shut it down, and tried to input "fastboot getvar product". That is when I get the "-bash: fastboot: command not found". I feel really dumb right now. It really seems so simple but I'm just not getting it. I added a screenshot if that would give you any clue as to why even the first step isn't working. Thank you
Click to expand...
Click to collapse
Put the fastboot binary in your home folder and enter 'cd' (without quotes). Then run the commands.
soupmagnet said:
Put the fastboot binary in your home folder and enter 'cd' (without quotes). Then run the commands.
Click to expand...
Click to collapse
I am probably making this harder than it really is. Alright, both adb and fastboot now exist inside my home folder "/user/Lianna/"
Started with kindle on and plugged in, entered "cd" into terminal. Didn't do anything. Continued with "cat ~/.android/adb_usb.ini" got same response as before. Other commands were unrecognized/"not found".
2hellwu said:
I am probably making this harder than it really is. Alright, both adb and fastboot now exist inside my home folder "/user/Lianna/"
Started with kindle on and plugged in, entered "cd" into terminal. Didn't do anything. Continued with "cat ~/.android/adb_usb.ini" got same response as before. Other commands were unrecognized/"not found".
Click to expand...
Click to collapse
Ok try this:
Instead of typing the word "fastboot" into the terminal, drag fastboot into the terminal window and then type in the rest of the command.
[EDIT:] I almost forgot...you're not using fastboot from KFU are you? You need fastboot for Mac.
soupmagnet said:
Ok try this:
Instead of typing the word "fastboot" into the terminal, drag fastboot into the terminal window and then type in the rest of the command.
[EDIT:] I almost forgot...you're not using fastboot from KFU are you? You need fastboot for Mac.
Click to expand...
Click to collapse
Again, command not found. Does the first step indicate that my fastboot is indeed functional?
2hellwu said:
Again, command not found. Does the first step indicate that my fastboot is indeed functional?
Click to expand...
Click to collapse
Are you using the fastboot.exe from the KFU folder or a Mac specific fastboot binary?
soupmagnet said:
Are you using the fastboot.exe from the KFU folder or a Mac specific fastboot binary?
Click to expand...
Click to collapse
I used the two individual downloads for adb and fastboot from here: http://forum.xda-developers.com/showthread.php?t=1917237
I do have KFU in my downloads but I'm not using the fastboot.exe that comes with it. I am using the ones downloaded from above, which seems to be a "unix executable file". I'll show what happens when I open it.
2hellwu said:
I used the two individual downloads for adb and fastboot from here: http://forum.xda-developers.com/showthread.php?t=1917237
I do have KFU in my downloads but I'm not using the fastboot.exe that comes with it. I am using the ones downloaded from above, which seems to be a "unix executable file". I'll show what happens when I open it.
Click to expand...
Click to collapse
Ok let's simplify this. Put fastboot on your desktop and enter the following:
Code:
~/Desktop/fastboot getvar product
soupmagnet said:
Ok let's simplify this. Put fastboot on your desktop and enter the following:
Code:
~/Desktop/fastboot getvar product
Click to expand...
Click to collapse
That did get me the <waiting for device> product:kindle! I then restarted and tried to input
Code:
fastboot oem idme bootmode 5001
fastboot reboot
which again, got "-bash: fastboot: command not found"
2hellwu said:
That did get me the <waiting for device> product:kindle! I then restarted and tried to input
Code:
fastboot oem idme bootmode 5001
fastboot reboot
which again, got "-bash: fastboot: command not found"
Click to expand...
Click to collapse
LOL, pay attention now...
Code:
~/Desktop/fastboot oem idme bootmode 5001
~/Desktop/fastboot reboot
OR
Code:
cd ~/Desktop
fastboot oem idme bootmode 5001
fastboot reboot
...you follow?
soupmagnet said:
LOL, pay attention now...
Code:
~/Desktop/fastboot oem idme bootmode 5001
~/Desktop/fastboot reboot
OR
Code:
cd ~/Desktop
fastboot oem idme bootmode 5001
fastboot reboot
...you follow?
Click to expand...
Click to collapse
ah yes. so, that worked. now at:
Code:
< waiting for device >
~/Desktop/fastboot reboot
at this point KF is still off. power on or no?
Ok, KF is on and back in recovery mode. "CWM-based recovery v5.0.2.7" I have the menu of reboot, install zip from sdcard, etc
2hellwu said:
Ok, KF is on and back in recovery mode. "CWM-based recovery v5.0.2.7" I have the menu of reboot, install zip from sdcard, etc
Click to expand...
Click to collapse
Okay, first you need to find and download the ROM of your choice. You'll also need to download recovery flashable versions of TWRP and FFF, found HERE and HERE.
With those three things downloaded, boot into recovery and find the "Mount" or "Mount to USB" option. I haven't used CWM in quite a while so I couldn't tell you exactly how to get to it. Look around and you will find it. What that does is mounts your sdcard to USB as if it were a USB flash drive. Do that and transfer the three files you downloaded earlier to your sdcard.
With them on your sdcard, install both FFF and TWRP. CWM is way outdated and will not work anymore...Use TWRP instead. You can update to COTR later if you choose as it has a nearly identical look and feel as CWM. The new version of FFF will give you an option at the boot logo to change bootmodes on the fly (makes entering recovery much easier).
With FFF and TWRP installed reboot the device. As the device is booting you will see the Kindle Fire logo in blue instead of orange. When you see it, hold the power button until the boot options appear at the bottom of the screen. Select Recovery.
When TWRP boots up, select "Wipe" then wipe system and factory reset (this step is very important).
Afterwards, select Install, navigate to your sdcard and select the ROM you downloaded then swipe the arrow at the bottom. Select reboot system and you should be all set.
One more thing to note: If the device keeps booting into recovery after subsequent reboots, select "reset boot mode" in the FFF boot options.
Good luck.
soupmagnet said:
Okay, first you need to find and download the ROM of your choice. You'll also need to download recovery flashable versions of TWRP and FFF, found HERE and HERE.
With those three things downloaded, boot into recovery and find the "Mount" or "Mount to USB" option. I haven't used CWM in quite a while so I couldn't tell you exactly how to get to it. Look around and you will find it. What that does is mounts your sdcard to USB as if it were a USB flash drive. Do that and transfer the three files you downloaded earlier to your sdcard.
With them on your sdcard, install both FFF and TWRP. CWM is way outdated and will not work anymore...Use TWRP instead. You can update to COTR later if you choose as it has a nearly identical look and feel as CWM. The new version of FFF will give you an option at the boot logo to change bootmodes on the fly (makes entering recovery much easier).
With FFF and TWRP installed reboot the device. As the device is booting you will see the Kindle Fire logo in blue instead of orange. When you see it, hold the power button until the boot options appear at the bottom of the screen. Select Recovery.
When TWRP boots up, select "Wipe" then wipe system and factory reset (this step is very important).
Afterwards, select Install, navigate to your sdcard and select the ROM you downloaded then swipe the arrow at the bottom. Select reboot system and you should be all set.
One more thing to note: If the device keeps booting into recovery after subsequent reboots, select "reset boot mode" in the FFF boot options.
Good luck.
Click to expand...
Click to collapse
Before I start this- I should have clarified my main goal is to get my kindle back to stock. I don't have a need for anything extra, I really just use it to read books. From other guides, maybe it seems that my next steps should be to download the kindle update from amazon, and flash that?
In that case, download the update from Amazon, change the ".bin" to ".zip" and use that in place of your ROM. All other instructions will be the same...especially when it comes to wiping
"That's a special kind of stupid. The kind that makes me laugh"
soupmagnet said:
In that case, download the update from Amazon, change the ".bin" to ".zip" and use that in place of your ROM. All other instructions will be the same...especially when it comes to wiping
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
Ok I feel stupid, but how do I find where the sdcard folder is? Is it simply just dragging the update to "Kindle" or should I be putting it into a specific folder
2hellwu said:
Ok I feel stupid, but how do I find where the sdcard folder is? Is it simply just dragging the update to "Kindle" or should I be putting it into a specific folder
Click to expand...
Click to collapse
Yes, the mounted volume "Kindle" is your sdcard. Just drag and drop everything into that folder. Be sure to eject the volume from your computer (right-click on it and select eject) before you unmount it in TWRP.
"That's a special kind of stupid. The kind that makes me laugh."
Hi All,
First up the device is Kindle Fire 3.6.2, and im on Windows 7 64 bit.
I first tried using KFU to start the root, but KFU kept hanging when trying to reboot in FastbootMode. The Kindle WOULD boot to fastbootmode, but then KFU was frozen on the line that said somthing like "rebooting to Fastboot mode". It then explained to turn off and on your kindle if it gets stuck, which i did numerous times, but it KFU didnt resume the batch file.
So, I have been following the Guide here:
http://forum.xda-developers.com/showthread.php?t=1638452
And i was able to succeffully install TWRP and backup my system, but TWRP keeps getting frozen on "updating partition", so im not confident that the Backup was successfull, however I can see the backup when i reboot the device in TWRP.
Now im attempting to use the Next few steps to root the kindle, specifically this step:
adb shell mount system
But adb says:
Error - more than one device.
When i query devices I get (shortened for clarity):
123 device
123 recovery
Im not sure why each of my steps have been sooo difficult to root my kindle! I really just want to experience Jelly Bean for the first time in my life!
Is there any tool at this point I can use to do the steps for me more easily? I tried KFU again but it always freezes after rebooting in fastboot mode,
If no tool is available, should i somehow disconnect one of the devices in adb? (I dont know how too).
BTW - I have no other devices other than a mouse attached to my PC!
Thanks so much in advance.
Regards,
Dale
Please, anybody? Ill be very grateful for any help!
help
still would love any help anyone!
dalecameron said:
still would love any help anyone!
Click to expand...
Click to collapse
First of all, when using adb (especially in Windows), always start every adb session with the command 'adb kill-server'. This will prevent previous adb sessions from staying active and causing problems down the line, like with the "multiple devices" error you are receiving.
Also, "updating partition details" in TWRP recovery takes only about a split second, but for some reason doesn't specifically let you know when it's finished. Your backup is in it's place so there's nothing to worry about. Beyond that, you shouldn't be having any problems whatsoever. Your adb shows connected in both normal and recovery modes, which suggests you have access to both, so your problems are all but non-existent.
And finally, you don't need to waste your time trying to "root" your device. When you flash a custom ROM in recovery, it gives you "root" automatically, so all you need to do at this point is use adb to push a ROM to your sdcard, factory reset in recovery, then flash the ROM (and Gapps, of course).
soupmagnet said:
First of all, when using adb (especially in Windows), always start every adb session with the command 'adb kill-server'. This will prevent previous adb sessions from staying active and causing problems down the line, like with the "multiple devices" error you are receiving.
Also, "updating partition details" in TWRP recovery takes only about a split second, but for some reason doesn't specifically let you know when it's finished. Your backup is in it's place so there's nothing to worry about. Beyond that, you shouldn't be having any problems whatsoever. Your adb shows connected in both normal and recovery modes, which suggests you have access to both, so your problems are all but non-existent.
And finally, you don't need to waste your time trying to "root" your device. When you flash a custom ROM in recovery, it gives you "root" automatically, so all you need to do at this point is use adb to push a ROM to your sdcard, factory reset in recovery, then flash the ROM (and Gapps, of course).
Click to expand...
Click to collapse
Thanks SoupMagnet! Much appreciated, and thanks for the adb tip!
dalecameron said:
Hi All,
First up the device is Kindle Fire 3.6.2, and im on Windows 7 64 bit.
I first tried using KFU to start the root, but KFU kept hanging when trying to reboot in FastbootMode. The Kindle WOULD boot to fastbootmode, but then KFU was frozen on the line that said somthing like "rebooting to Fastboot mode". It then explained to turn off and on your kindle if it gets stuck, which i did numerous times, but it KFU didnt resume the batch file.
So, I have been following the Guide here:
http://forum.xda-developers.com/showthread.php?t=1638452
And i was able to succeffully install TWRP and backup my system, but TWRP keeps getting frozen on "updating partition", so im not confident that the Backup was successfull, however I can see the backup when i reboot the device in TWRP.
Now im attempting to use the Next few steps to root the kindle, specifically this step:
adb shell mount system
But adb says:
Error - more than one device.
When i query devices I get (shortened for clarity):
123 device
123 recovery
Im not sure why each of my steps have been sooo difficult to root my kindle! I really just want to experience Jelly Bean for the first time in my life!
Is there any tool at this point I can use to do the steps for me more easily? I tried KFU again but it always freezes after rebooting in fastboot mode,
If no tool is available, should i somehow disconnect one of the devices in adb? (I dont know how too).
BTW - I have no other devices other than a mouse attached to my PC!
Thanks so much in advance.
Regards,
Dale
Click to expand...
Click to collapse
Uncheck the backup of android secure and I believe it will stop hanging at updating partitions.