Related
Alright, so my Kindle Fire is bricked, and was stuck at the boot screen (the default Kindle Fire loading screen) after attempting to root it with an outdated tutorial (didn't know this at the time, but the program is called SuperOneClick) then I made another foolish attempt to install TWRP (I THINK I did it to restore the Kindle back to the factory software/defaults but I'm not sure exactly what I was thinking as it was probably 2 weeks ago)... After doing a little more research, I made my way back here because the forums have been resourceful in the past concerning my Evo 4G... After that I found a very similar thread and decided to try my luck once again, had extreme problems trying to get my computer to recognize the Kindle (on both Windows 7 and Ubuntu), all of my settings were correct and are now correct to the best of my knowledge (adb/udev files included)... To this day I still have no luck getting my computer to recognize it, after reading through numerous tutorials/threads I've resorted to buying a "factory cable" because the battery died (while plugged in the wall/usb both it just flashed on and off) and I was told by another member here that it is the only way to bypass the dead battery... Yesterday I've received the "factory cable", but the Kindle still flashes on and off while it is plugged in via usb, and still doesn't show up in device manager, or in command prompt/terminal via adb devices/lsusb commands even after multiple restarts and adb kill-server, adb start-server have been applied... Can anybody help guide me through this??? My faith is running extremely dry at this point, and I'm willing to try just about anything to get this thing right, and learn a few things in the process!!!
Thanks in Advance,
CJ
Firekit http://forum.xda-developers.com/showthread.php?t=1430038
I will help you
And you have done sooo much!!! I've spent a total of at least 12 hours trying to figure this thing out, and getting the terminal to recognize it CORRECTLY is the furthest I've seen so far, even if it was for only one command, for a few seconds... My charging attempt has yet again failed miserably, BUT I have however bypassed the boot loop for about 30 seconds, still staying at the default Kindle Fire screen (tried a random tutorial to trick the Kindle into charging, it MIGHT have worked because it was only plugged in via usb for about 1 minute after this trick but instead of the orange light coming on the Kindle just stayed in the power off looking state)... Even with the boot loop bypassed though, fk did not seem to recognize the device so I'm even more lost than I was originally lol...
EDIT: I am positive the Kindle is receiving a charge, the charge light isn't on BUT it is charging!!! Regardless of the power state no command is working to recognize the device, including "adb devices", "lsusb", and "fastboot getvar product"... I guess that it's possible that one of my files have gone corrupt so I'll check them out again but other than that I'm stumped...
After many trial and error's, and with the amazing guidance of "Thepooch", we have finally unbricked the KF!!! Thank you for your time and patience, if it wasn't for you I would've probably given up by now
Great Job Pooch! You da' man. Glad you got it working!
Was an adventure your welcome though
Sent from my Amazon Kindle Fire using Tapatalk 2
An adventure is an understatement, for me at least but in the end you came through once again and it is up and running like a champ!!!
Sent from my GT-P3113 using Tapatalk 2
Bricked Kindle Fire
I was having trouble using KFU. I wanted to install JellyBean 4.1 and after finding a post to perform some command lines the KFU finally found my KF. I installed the permanent root (i thought) and it rebooted the KF into fastboot it stated. Now it loads to a logo and stops. If I hold the power button (5-10 secs) it shuts off and that is the only thing I can do. It does not show up in my device manager so I feel I killed it. I know you guys have the answer and I apologize in advanced for being a newbie but I am desperate. It looked so easy in the YouTube videos but as always that is the famous last words...
gtc954 said:
I was having trouble using KFU. I wanted to install JellyBean 4.1 and after finding a post to perform some command lines the KFU finally found my KF. I installed the permanent root (i thought) and it rebooted the KF into fastboot it stated. Now it loads to a logo and stops. If I hold the power button (5-10 secs) it shuts off and that is the only thing I can do. It does not show up in my device manager so I feel I killed it. I know you guys have the answer and I apologize in advanced for being a newbie but I am desperate. It looked so easy in the YouTube videos but as always that is the famous last words...
Click to expand...
Click to collapse
Likely your stuck in fastboot shift+ right click on the tools folder in kfu select open command window here power your device off completely leave it unplugged type fastboot -i 0x1949 getvar product when it says waiting for device plug in your powered off kindle it should then power on in fastboot mode if you get the response product: kindle then type fastboot -i 0x1949 oem idme bootmode 4000 it will say okay hopefully the type fastboot -i 0x1949 reboot it should then reboot in normal mode
Thepooch said:
Likely your stuck in fastboot shift+ right click on the tools folder in kfu select open command window here power your device off completely leave it unplugged type fastboot -i 0x1949 getvar product when it says waiting for device plug in your powered off kindle it should then power on in fastboot mode if you get the response product: kindle then type fastboot -i 0x1949 oem idme bootmode 4000 it will say okay hopefully the type fastboot -i 0x1949 reboot it should then reboot in normal mode
Click to expand...
Click to collapse
You are amazing!!!!
GameGuru41 said:
You are amazing!!!!
Click to expand...
Click to collapse
Naww lol don't forget to hit the than button lol
Thank you!!
Thepooch said:
Likely your stuck in fastboot shift+ right click on the tools folder in kfu select open command window here power your device off completely leave it unplugged type fastboot -i 0x1949 getvar product when it says waiting for device plug in your powered off kindle it should then power on in fastboot mode if you get the response product: kindle then type fastboot -i 0x1949 oem idme bootmode 4000 it will say okay hopefully the type fastboot -i 0x1949 reboot it should then reboot in normal mode
Click to expand...
Click to collapse
Pooch thank you buddy very much!! I thought I owned a black brick. Now with that newbie mess out of the way could you help with what went wrong using KFU? It would not find my KF and only when I found something about typing in some command lines (similar to your fix) did KFU finally state the KF was online. I then chose option 2 used the permanent root function and viola a brick. I of course followed all the previous directions about loading drivers and making sure the ADB composite was in the device manager. Can you point me in the right direction?
Thanks again...
gtc954 said:
Pooch thank you buddy very much!! I thought I owned a black brick. Now with that newbie mess out of the way could you help with what went wrong using KFU? It would not find my KF and only when I found something about typing in some command lines (similar to your fix) did KFU finally state the KF was online. I then chose option 2 used the permanent root function and viola a brick. I of course followed all the previous directions about loading drivers and making sure the ADB composite was in the device manager. Can you point me in the right direction?
Thanks again...
Click to expand...
Click to collapse
If your main intent is to flash a ROM no need to root simply just allow installation from unknown sources under device in your kindle settings when you plug it it disconnect the USB transfer app. Then select option for twrp it should reboot then swipe open and stop USB app again this time send fff. Then use the boot loader to enter recovery when there select backup make a backup that you will later name noroot631 without spaces after you have created a backup reboot to os then use the USB app to place a ROM zip and a gapp zip on your SD card but do not place it inside of a folder this is considered the root of your sdcard then boot back into recovery . Go to install make sure you can locate the files you intend to flash then use the back button or home button in upper right to return to twrp main screen. At this point you have a safety net and a backup and you are getting familiar with the functions and learning how to navigate in twrp. Now for a flash if you are gonna flash modaco for the stock like adventure its not required to perform any wipes just simply flash and reboot. No gapps required either now you are rooted If you intend to flash a different flavor like cm7 cm9 or jelly bean it gets a bit more technical . After placing ROM and appropriate gapps on your SD card this time your gonna wipe and its very important you do so!!! First go and wipe factory reset then wipe cache then wipe dalvik here's the scary part wipe system do not reboot you have no system!! There is no need to wipe sdcard or external storage as it is called in the new twrp if you did you would have nothing to flash then hit the home button above right taking you back to the twrp main screen this time select install tap on the ROM zip swipe to install then home again install again this time select gapps swipe to install select reboot and system if prompted. It will reboot initial boot takes time I would say 5-8 mins longer and then you need to be a little alarmed If your greeted by an android for account setup your good congrats your rooted. If boot takes longer than 10 mins hold power button return to recovery restore your backup after the wipes I mentioned above try again later with new ROM and new gapps. Good luck as for kfu awhhh so many things broken for so many people near impossble to say why so many fail to root frankly operator error accounts for at least 80% of failures could be more like 90% . Common mistakes thinking you need to root to flash a ROM, bad drivers windows is terrrrrible,wrong cable,using a 3.0 USB port instead of 2.0, and general miscommunication between the device your computer and the utility. Whewwww all that said install twrp install fff if you can 100% verify that you have both and you know how to use both and move files to your SD card and have made a backup every time before you flash. Then flash Awaaaayyy!!! Hope I didnt miss anything oh and the usual disclaimer know what your doing or you shoot your eye out lol and of course I'm not responsible if you brick your kindle!! Good luck
---------- Post added at 10:57 PM ---------- Previous post was at 10:55 PM ----------
Ohh and if you can't read that I'm sorry for the novel punctuation and such costs more
---------- Post added at 11:11 PM ---------- Previous post was at 10:57 PM ----------
PS as well after creating the huge safety net I explained above go ahead after your backup and select permanent root with superuser you have a backup and a bootloder that resets your boot mode have it but IMO that function is broken for too many people these days I don't recommend it because if our gonna flash a ROM all ROMs are rooted so what's the point?
Thepooch said:
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
Thepooch said:
Common mistakes thinking you need to root to flash a ROM, bad drivers windows is terrrrrible,wrong cable,using a 3.0 USB port instead of 2.0, and general miscommunication between the device your computer and the utility.
Click to expand...
Click to collapse
So that's probably why I bricked my kindle was due to using a 3.0 port. I don't see how that would affect it though. Either way, I'm trying to charge up the battery on my kindle some since it drained itself to dead over night when I gave up in frustration and went to sleep. Then I'm going to try to unbrick using your methods mentions above and on the first page. If none work you'll be hearing from me again. lol
Well switching to the USB 2 and those commands through dos worked perfectly. Now if only it would download the twrp file. Just can't get a break with this stupid thing.
http://forum.xda-developers.com/showthread.php?t=1836005 twrp problem
where are the simple, easy to follow directions...
to root my Kindle..
All this stuff is overwhemingly confusing for a non-computer speaking person..
I tried to follow the directions listed here:
http://forum.xda-developers.com/showthread.php?t=1638452
but got really confused.
So I read through this thread: http://forum.xda-developers.com/showthread.php?t=1399889 and got even more confused.
I've rooted my Samsung Galaxy SII, but that used a simple one-click process. Trying to decipher the procedures for rooting a kindle fire is confusing to say the least.
Im begining to think that my stock Kindle is ok...
I'd just assume ship my KF off to someone to root it and install a custom ROM.. i've been reading these threads and forums for 3 days now and I just keep spinning myself in circles...
Thepooch said:
Likely your stuck in fastboot shift+ right click on the tools folder in kfu select open command window here power your device off completely leave it unplugged type fastboot -i 0x1949 getvar product when it says waiting for device plug in your powered off kindle it should then power on in fastboot mode if you get the response product: kindle then type fastboot -i 0x1949 oem idme bootmode 4000 it will say okay hopefully the type fastboot -i 0x1949 reboot it should then reboot in normal mode
Click to expand...
Click to collapse
Don't worked here. The triangles keep spinnig and the cmd keeps on <waiting for device>.
Reinaque said:
Don't worked here. The triangles keep spinnig and the cmd keeps on <waiting for device>.
Click to expand...
Click to collapse
Start a new thread and explain your problem in detail.
My Kindle was rooted but I decided to try my hand at installing a custom ROM. However, the ROM I tried would not work and the screen stayed black. However, thanks to TWRP I could install Kindle from Amazon again. The installation went thru smoothly, or so I thought. Now, when I boot the Kindle, I see the Kindle Fire Logo and it stays there. The Computer can see the Kindle as an Android device, Android Composite Device. But Kindle Fire Utility cannot see it so I could try and re-install it again. Any suggestions?
Lacking information, so I'll just fill the voids with assumptions.
I *assume* you didn't wipe cache, dalvik-cache and most important when switching from a ROM to another, Factory Reset - this is the reason said custom ROM wouldn't work, and the reason flashing back update.zip (as you said you installed it, rather than restoring a backup) caused your KF to get stuck in a semi brick.
The most important question here is, do you have FFF installed?
If you do, fixing this is trivial. Just get into TWRP from FFF, wipe cache, dalvik-cache and factory reset and then install whatever ROM you'd like to try or use.
If you don't have FFF installed, then your solutions are to either get a factory cable (recommended) or to crack open the case and do the USB pin short trick. From there you can use fastboot to install FFF and boot into TWRP.
Alternatively, you can try "fastboot getvar product" or "adb shell idme bootmode 5001" to see if you get lucky.
Dasanko said:
Lacking information, so I'll just fill the voids with assumptions.
I *assume* you didn't wipe cache, dalvik-cache and most important when switching from a ROM to another, Factory Reset - this is the reason said custom ROM wouldn't work, and the reason flashing back update.zip (as you said you installed it, rather than restoring a backup) caused your KF to get stuck in a semi brick.
The most important question here is, do you have FFF installed?
If you do, fixing this is trivial. Just get into TWRP from FFF, wipe cache, dalvik-cache and factory reset and then install whatever ROM you'd like to try or use.
If you don't have FFF installed, then your solutions are to either get a factory cable (recommended) or to crack open the case and do the USB pin short trick. From there you can use fastboot to install FFF and boot into TWRP.
Alternatively, you can try "fastboot getvar product" or "adb shell idme bootmode 5001" to see if you get lucky.
Click to expand...
Click to collapse
I tried the USB pin short trick but now my Kindle won't turn on at all nor will it charge. Thanks anyways!
i have similar problem ......please need help
After successfully rooting kf with kfu and making a backup ... I did factory reset and flashed a custom rom ... now kindle is stuck on " kindle fire" logo and just keeps flashing and rebooting . My computer recognizes it as android phone ( android adb ) and kfu does too but only for a couple of seconds . During those few seconds I try recovery ... fast boot ...normal boot... n none seem to work . Kf just reboots n returns to boot loop . Any advice is appreciated .. thanks
Start a new thread when you're posting your own issues.
What colour is the "kindle fire" logo when you turn on your KF?
Force Kindle into Fastboot
Ok, so I have finally got my Kindle to turn on, using the USB Short Trick. Now my only question is about getting the Kindle to boot into fastboot mode so I can re-format the sdcard partition and finally load a new ROM. I have tried several different commands and they all seem to miss the window of opportunity to start the kindle in fastboot mode. Is there any way, short of a factory cable, that one can make the kindle start in fastboot mode?
Not fastboot get var
ComputerGenuis2.0 said:
Ok, so I have finally got my Kindle to turn on, using the USB Short Trick. Now my only question is about getting the Kindle to boot into fastboot mode so I can re-format the sdcard partition and finally load a new ROM. I have tried several different commands and they all seem to miss the window of opportunity to start the kindle in fastboot mode. Is there any way, short of a factory cable, that one can make the kindle start in fastboot mode?
Click to expand...
Click to collapse
fastboot getvar product doesn't seem to do the trick. The kindle seems to be in fastboot mode but the adb shell cannot access the device.
The problem is that you don't have the fastboot drivers installed (also, ADB will not work while fastboot is active) - Windows is painfully slow at detecting a device and installing its drivers, so by the time it even notices anything, the fastboot window is already over.
To solve this, use firekit: http://forum.xda-developers.com/showthread.php?t=1430038
The script that will probably suit your needs the most is usb_install_fff_twrp.
Used Firekit
Dasanko said:
The problem is that you don't have the fastboot drivers installed (also, ADB will not work while fastboot is active) - Windows is painfully slow at detecting a device and installing its drivers, so by the time it even notices anything, the fastboot window is already over.
To solve this, use firekit: http://forum.xda-developers.com/showthread.php?t=1430038
The script that will probably suit your needs the most is usb_install_fff_twrp.
Click to expand...
Click to collapse
I have TWRP and FFF installed. However, upon booting into TWRP, the sdcard partition cannot be mounted, to the Kindle that is, and as such, I cannot mount the sdcard to the computer. When I researched this some more, I found that I can fix this by using a command via adb shell. The guide instructed using fastboot to achieve this. When would be the best time to use adb shell?
What's the output of partitions.txt? (type the following from TWRP)
adb shell parted /dev/block/mmcblk0 p > partitions.txt
Can't use adb
Dasanko said:
What's the output of partitions.txt? (type the following from TWRP)
adb shell parted /dev/block/mmcblk0 p > partitions.txt
Click to expand...
Click to collapse
The problem at hand is using adb. I can never time it exactly right to open adb. I always get an "error: device not found". Windows even recognizes that Android ADB Interface is plugged in.
Okay, things are getting awfully confusing here.
What exactly is it that you can do and that you cannot do?
For example, are FFF and TWRP functional?
GOT IT!
Thank you! I finally figured out that the wrong driver had reinstalled and that was causing my computer to not be able to use adb shell. I fixed that and voila, I am now running CM9. Thanks again!
Not sure what's going on here.. I unrooted my kindlefire with update.zip but I forgot to wipe to factory reset before i flashed update.zip and when i rebooted my kindle i noticed that A ! symbol popped up with "Sorry" that says "The application Calendar Storage (process com.android.providers.calendar) has stopped unexpectedly. Please try again" That isn't the only problem, i click force close and another prompt comes up saying "The process android.process.acore has stopped unexpectedly. Please try again" It waits a few seconds, then proceeds to do a fast reboot? It comes up with the yellow kindle fire and immediately after it boots up it shows the errors.
Not sure what to do. Tried installing TWRP but the kindle doesn't stay on long enough so right now I'm pretty unconvinced of anything..
Any help would be greatly appreciated.
You just need to fast quickly get to factory reset and reset it try from a powered off position it may give you a few seconds extra to complete the task...
Thepooch said:
You just need to fast quickly get to factory reset and reset it try from a powered off position it may give you a few seconds extra to complete the task...
Click to expand...
Click to collapse
I'm not sure how to get there.. I don't have any form of backup installed. It's on the complete default rom
Edit: Found out how to get to factory reset, only to discover that I need a 40% charge, when mine is less than 5% and won't charge any more because of my problem
Still haven't figured this out. Can't use my kindle at all until this is fixed :/
iKrotos said:
Still haven't figured this out. Can't use my kindle at all until this is fixed :/
Click to expand...
Click to collapse
You're most likely going to have to put the device into fastboot mode to fix this problem. You can quickly send a sequence of adb commands to put the device into fastboot before the system crashes...
http://forum.xda-developers.com/showthread.php?t=1638452
by using the "Getting to fastboot mode" section above. That seems sketchy at best. Otherwise, you can get a factory cable...
http://forum.xda-developers.com/showthread.php?t=1550999
and put it into fastboot mode that way. In either case, you'll want to delete the userdata partition...
Code:
fastboot -i 0x1949 erase userdata
Then the next time you boot the device normally (by changing the bootmode back to 4000 if it isn't already), the system software will remake that partition and it should boot normally.
kinfauns said:
You're most likely going to have to put the device into fastboot mode to fix this problem. You can quickly send a sequence of adb commands to put the device into fastboot before the system crashes...
http://forum.xda-developers.com/showthread.php?t=1638452
by using the "Getting to fastboot mode" section above. That seems sketchy at best. Otherwise, you can get a factory cable...
http://forum.xda-developers.com/showthread.php?t=1550999
and put it into fastboot mode that way. In either case, you'll want to delete the userdata partition...
Code:
fastboot -i 0x1949 erase userdata
Then the next time you boot the device normally (by changing the bootmode back to 4000 if it isn't already), the system software will remake that partition and it should boot normally.
Click to expand...
Click to collapse
Read the beginners guide for KF, Found about about ADB fastboot etc. Going to install ADB tomorrow and try to figure this all out. Thanks.
I can't do this. It's been over a month. My kindle is finished..
iKrotos said:
I can't do this. It's been over a month. My kindle is finished..
Click to expand...
Click to collapse
"I can't do this"
Well that explains everything, doesn't it? It's a good thing you explained your problem in such great detail or I might spend time trying to help you fix your Kindle thinking you "could" do it. Phew. Saved us all a lot of time, thank you.
I made the same mistake of flashing the stock update without wiping and factory resetting.
The device will boot, then immediately give the calendar and android.process.acore errors for about 20 seconds before rebooting. It doesn't give me enough time to do a factory reset through the menu before it restarts.
After reading up on basic guides and downloading the necessary software, I can't find a way to get to fastboot, and I'm afraid even the noob guides are just confusing me more at this point.
From what I can understand, I'll probably have to get a factory cable to force the device into fastboot, because the Kindle reboots before the PC has a chance to recognize it, but what happens then? I've read the ADB for dummies guides, and searched the forum for and I still can't really understand how to execute the commands.
Can anyone link a relevant thread, or maybe give some dumbed-down advice?
LaszloToth said:
I made the same mistake of flashing the stock update without wiping and factory resetting.
The device will boot, then immediately give the calendar and android.process.acore errors for about 20 seconds before rebooting. It doesn't give me enough time to do a factory reset through the menu before it restarts.
After reading up on basic guides and downloading the necessary software, I can't find a way to get to fastboot, and I'm afraid even the noob guides are just confusing me more at this point.
From what I can understand, I'll probably have to get a factory cable to force the device into fastboot, because the Kindle reboots before the PC has a chance to recognize it, but what happens then? I've read the ADB for dummies guides, and searched the forum for and I still can't really understand how to execute the commands.
Can anyone link a relevant thread, or maybe give some dumbed-down advice?
Click to expand...
Click to collapse
Get a factory cable and then we can work on fixing your device.
One thing you have to know about entering commands is that computers have no more intelligence than, say, an ordinary rock. Meaning, they are not able to think on their own. They don't have the capacity to make their own decisions. Everything is laid out for them via sets of instructions. ADB and fastboot are programs with their own sets of instructions embedded into them, so in order to use them, you must direct the computer to those programs. When entering commands from the command line, the computer will search only the present working directory for those commands (plus any directories in it's PATH, but that is a subject for another time). When you open a command prompt in Windows, it will start in a specific directory (folder). Normally in Windows its the "Documents and Settings" folder (if I remember correctly). When you enter a command like "adb devices", the computer will search it's own set of built in commands for the first word (command) in the command line (in this case, adb). If that command isn't in it's set of built in commands, it searches the present working directory. In all likelihood, adb will not be in in the first present working directory when the command prompt opens up so you have to redirect it. There are several ways to do this. You can make sure the directory containing adb is in your PATH, but there's a little bit of learning involved and it's unnecessary unless you intend to enter a LOT of adb commands. You can change directories (cd) to the correct folder, but if you don't know what you're doing it can get very confusing and frustrating. The easiest and most straight forward way of doing this is to locate the directory containing adb and fastboot then "Shift + right-click, on that folder and select "Open command window here". The command window that opens is where you'll enter your adb/fastboot commands. Apart from that, you must really know the commands you're using, how they're used and what they do, or you're just wasting your time.
Does or kindle gets recognized.. if so there is a chance to recover
Sent from my MB526 using Tapatalk 2
soupmagnet said:
Get a factory cable and then we can work on fixing your device.
One thing you have to know about entering commands is that computers have no more intelligence than, say, an ordinary rock. Meaning, they are not able to think on their own. They don't have the capacity to make their own decisions. Everything is laid out for them via sets of instructions. ADB and fastboot are programs with their own sets of instructions embedded into them, so in order to use them, you must direct the computer to those programs. When entering commands from the command line, the computer will search only the present working directory for those commands (plus any directories in it's PATH, but that is a subject for another time). When you open a command prompt in Windows, it will start in a specific directory (folder). Normally in Windows its the "Documents and Settings" folder (if I remember correctly). When you enter a command like "adb devices", the computer will search it's own set of built in commands for the first word (command) in the command line (in this case, adb). If that command isn't in it's set of built in commands, it searches the present working directory. In all likelihood, adb will not be in in the first present working directory when the command prompt opens up so you have to redirect it. There are several ways to do this. You can make sure the directory containing adb is in your PATH, but there's a little bit of learning involved and it's unnecessary unless you intend to enter a LOT of adb commands. You can change directories (cd) to the correct folder, but if you don't know what you're doing it can get very confusing and frustrating. The easiest and most straight forward way of doing this is to locate the directory containing adb and fastboot then "Shift + right-click, on that folder and select "Open command window here". The command window that opens is where you'll enter your adb/fastboot commands. Apart from that, you must really know the commands you're using, how they're used and what they do, or you're just wasting your time.
Click to expand...
Click to collapse
Thanks, I've read up a bit more about the ADB and Fastboot commands, and I think I have a better grasp on them now, and your explanation of where I need be as far as changing directories in the command prompt really clears things up.
From reading your advice earlier in this thread, my best option would probably be to wipe the existing user data on the device that I forgot about before re-flashing the stock Kindle update by changing directories to the folder which contains ADB.exe and Fastboot.exe, then running the "fastboot -i 0x1949 erase userdata" command once I've connected the device with a factory cable. By doing this, would I be essentially restoring the device as if it were brand new again? Aside from erasing user data, are there any other ADB or Fastboot commands that I should run?
Also, assuming the ADB drivers are installed properly, once I've plugged in the device with the factory cable, will KFU immediately recognize the device, or will I need to first run the "fastboot -i 0x1949 erase userdata" command to get it back to stock first before I get 4000 status in KFU? I'm wondering if I could just plug in the factory cable, root and flash TWRP via KFU, then wipe and factory reset the user data from within TWRP, or would that be going about it backwards?
Thanks again fro the help!
---------- Post added at 02:31 PM ---------- Previous post was at 02:24 PM ----------
kishorev said:
Does or kindle gets recognized.. if so there is a chance to recover
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
No, the KFU status is "unknown" and Windows doesn't even really have time to recognize that the device is connected via USB, since the Kindle will reboot every 15-20 seconds.
I've ordered a factory cable, so hopefully it will be a pretty straight-forward fix once I get it.
Had a similar problem of rebooting every 10 sec or so..I left it on charge overnight and it worked..it got charged decent enough for me to help recover it..
Just try charging it overnight it might just work..I always feel using factory cable shd be the last resort
Sent from my Kindle Fire using Tapatalk 2
LaszloToth said:
Thanks, I've read up a bit more about the ADB and Fastboot commands, and I think I have a better grasp on them now, and your explanation of where I need be as far as changing directories in the command prompt really clears things up.
From reading your advice earlier in this thread, my best option would probably be to wipe the existing user data on the device that I forgot about before re-flashing the stock Kindle update by changing directories to the folder which contains ADB.exe and Fastboot.exe, then running the "fastboot -i 0x1949 erase userdata" command once I've connected the device with a factory cable. By doing this, would I be essentially restoring the device as if it were brand new again? Aside from erasing user data, are there any other ADB or Fastboot commands that I should run?
Also, assuming the ADB drivers are installed properly, once I've plugged in the device with the factory cable, will KFU immediately recognize the device, or will I need to first run the "fastboot -i 0x1949 erase userdata" command to get it back to stock first before I get 4000 status in KFU? I'm wondering if I could just plug in the factory cable, root and flash TWRP via KFU, then wipe and factory reset the user data from within TWRP, or would that be going about it backwards?
No, the KFU status is "unknown" and Windows doesn't even really have time to recognize that the device is connected via USB, since the Kindle will reboot every 15-20 seconds.
I've ordered a factory cable, so hopefully it will be a pretty straight-forward fix once I get it.
Click to expand...
Click to collapse
One thing you need to realize, is that once you get custom recovery installed, you will rarely ever need to use fastboot commands. Fastboot commands really only need to be used when everything else fails. Custom recovery and the latest version of the FireFireFire bootloader have probably 90% of the functionality that fastboot has, so unless those options aren't available to you, try to avoid fastboot altogether.
Most Kindle Fire problems are fixed by wiping the system, data & cache (factory reset) partitions and reinstalling the ROM.
Your first course of action should be to get TWRP and FireFireFire installed, if they aren't already. For this you will need fastboot commands. In order to issue fastboot commands, you need to be in fastboot mode. I'm guessing this is most likely not the case. Unfortunately, without a system to boot to, or the FireFireFire bootloader (blue Kindle Fire logo) installed, you have no chance of getting into fastboot without a factory cable.
The factory cable will get you into fastboot so you can reinstall custom recovery and reinstall a new ROM. You can then use the custom recovery to install a new bootloader (never wipe to install a bootloader BTW). Chances are, that is all you need to fix your device. You should keep your device powered off (hold power button for 20 seconds), until the factory cable arrives.
Hope that helps.
soupmagnet said:
One thing you need to realize, is that once you get custom recovery installed, you will rarely ever need to use fastboot commands. Fastboot commands really only need to be used when everything else fails. Custom recovery and the latest version of the FireFireFire bootloader have probably 90% of the functionality that fastboot has, so unless those options aren't available to you, try to avoid fastboot altogether.
Most Kindle Fire problems are fixed by wiping the system, data & cache (factory reset) partitions and reinstalling the ROM.
Your first course of action should be to get TWRP and FireFireFire installed, if they aren't already. For this you will need fastboot commands. In order to issue fastboot commands, you need to be in fastboot mode. I'm guessing this is most likely not the case. Unfortunately, without a system to boot to, or the FireFireFire bootloader (blue Kindle Fire logo) installed, you have no chance of getting into fastboot without a factory cable.
The factory cable will get you into fastboot so you can reinstall custom recovery and reinstall a new ROM. You can then use the custom recovery to install a new bootloader (never wipe to install a bootloader BTW). Chances are, that is all you need to fix your device. You should keep your device powered off (hold power button for 20 seconds), until the factory cable arrives.
Hope that helps.
Click to expand...
Click to collapse
So instead of using fastboot to wipe the user data, I should use it to install TWRP? Can you give me the fastboot command for that? Or can I do that with KFU once I plug in the factory cable?
http://forum.xda-developers.com/showpost.php?p=23747804
Thanks soupmagnet, I got the factory cable today and was able to flash FFF and TWRP with fastboot commands, and it's working like it should again. You help has been much appreciated.
same problem with kindle fire.
LaszloToth said:
Thanks soupmagnet, I got the factory cable today and was able to flash FFF and TWRP with fastboot commands, and it's working like it should again. You help has been much appreciated.
Click to expand...
Click to collapse
hi, i am new here and i got exact the same problem with you, i just ordered the factory cable, can you please give the step by step procedure on solving this problem with the factory cable. your help will be appreciated, thanks.
Thepooch said:
You just need to fast quickly get to factory reset and reset it try from a powered off position it may give you a few seconds extra to complete the task...
Click to expand...
Click to collapse
:good::good::good::good::good::good: works for me thank you
ok, today i had the same problem because i didn't wipe the factory restore!
The solution WASN'T the Factory Cable (I was considering buying one)!
Very easy:
Linux and SOUPKIT! were the solution, when the tablet boots up immediately hit the install recovery, after installing recovery, just set to boot into recovery.
Now is very much you can do (ex. wipe everything and than install update.zip all over)
Very much thank you to the guy who made SOUPKIT! (u've saved my S many many times )
Hell. I've received my KF's (1st gen) replacement today and I've tried to get into fastboot using a factory cable.
My KF would enter FB mode but upon doing so my system (both Linux and Windows) would "lose connection" with my KF.
So I'd reboot instead. When it'd boot into stock ADB worked so I changed bootmodes hoping that this time around Fastboot will work.
Again both my Linux and my Windows systems refuse to make any "contact" with my KF, only this time around my KF is also incapable to get out of fastboot as well (given that I changed the bootmode via ADB).
So what is this? (while in Windows I'm getting "unknown drivers", in Linux nothing happens as if the device is not connected at all)
Also would the USB method work, or should I -merely- again replace my KF since as it seems there's some problem in a Hardware level...
Thanks.
Stevethegreat said:
Hell. I've received my KF's (1st gen) replacement today and I've tried to get into fastboot using a factory cable.
My KF would enter FB mode but upon doing so my system (both Linux and Windows) would "lose connection" with my KF.
So I'd reboot instead. When it'd boot into stock ADB worked so I changed bootmodes hoping that this time around Fastboot will work.
Again both my Linux and my Windows systems refuse to make any "contact" with my KF, only this time around my KF is also incapable to get out of fastboot as well (given that I changed the bootmode via ADB).
So what is this? (while in Windows I'm getting "unknown drivers", in Linux nothing happens as if the device is not connected at all)
Also would the USB method work, or should I -merely- again replace my KF since as it seems there's some problem in a Hardware level...
Thanks.
Click to expand...
Click to collapse
In Linux, can you see the device in fastboot with lsusb?
You know, they may have given you the proverbial shaft and replaced your 1st gen with a 2nd gen.
soupmagnet said:
In Linux, can you see the device in fastboot with lsusb?
You know, they may have given you the proverbial shaft and replaced your 1st gen with a 2nd gen.
Click to expand...
Click to collapse
Yep I can (as "Lab126"), but trying to issue any command and I get the proverbial "waiting for device"... How can I even check it's 2nd gen? IIRC it had bluetooth support for one and I don't, also Windows gave me the Hardware ID of KF 1st gen (unless they somehow share the same Hardware ID).
In other news I managed to change the bootmode back to normal (for a split second FB worked enought to change the bootmode, but not enough to do anything else). So yeah I have adb support (when I boot into the rom), but nothing much else. What can I do with adb (w/t fastboot my hands are tied aren't they?).
What does the following command return? (in Linux)
Code:
lsusb -vd 1949:0006 | grep 'bcdDevice'
soupmagnet said:
What does the following command return?
Code:
lsusb -vd 1949:0006 | grep 'bcdDevice'
Click to expand...
Click to collapse
Hmm for the time being I'm back into Windows restoring my KF apparently adding the flag "-i 0x1949" after fastboot did the trick even though "bare" fastboot commands don't work ("fastboot devices" gives me nil). Anyhow I've managed to install FFF, TWRP and as I mentioned earlier I'm currently restoring from my backups.
However if you wish I can try run the command when all this is finished (it's still a mystery to me why "regular" fastboot doesn't work).
Stevethegreat said:
Hmm for the time being I'm back into Windows restoring my KF apparently adding the flag "-i 0x1949" after fastboot did the trick even though "bare" fastboot commands don't work ("fastboot devices" gives me nil). Anyhow I've managed to install FFF, TWRP and as I mentioned earlier I'm currently restoring from my backups.
However if you wish I can try run the command when all this is finished (it's still a mystery to me why "regular" fastboot doesn't work).
Click to expand...
Click to collapse
It's because of the stock bootloader. The stock bootloader requires the -i switch, FFF does not.
soupmagnet said:
It's because of the stock bootloader. The stock bootloader requires the -i switch, FFF does not.
Click to expand...
Click to collapse
Gotcha! Thanks
A few months ago I tried to root/ gapps a KF2 for a friend, and after a freak OTA update the horrible thing kept getting stuck in a bootloop.
Basically if you powered it on it would get stuck on the Kindle pulsing logo until it restarted itself from scratch and did it all over again. Then on the few times it would get to the standard lock screen it would freeze up there and restart itself anyway.
Every now and then it would boot in and work fine though.
What I eventually did to get it working:
1.) Get a factory cable (they don't cost too much off ebay).
2.) Using fastboot mode clear the data and cache partition:
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
20 seconds later the device worked perfectly and hasn't bootlooped since.
It might also be possible to do this by a.) installing TWRP and erasing the cache/ data from there, or b.) booting into the bootloader from a rooted system. I don't want to test this though because at this point I just want to make this awful thing work properly in stock.
I hope this helps someone else in the same situation. I do remember reading a similar problem on XDA a few months ago when it started giving trouble.
hexd said:
A few months ago I tried to root/ gapps a KF2 for a friend, and after a freak OTA update the horrible thing kept getting stuck in a bootloop.
Basically if you powered it on it would get stuck on the Kindle pulsing logo until it restarted itself from scratch and did it all over again. Then on the few times it would get to the standard lock screen it would freeze up there and restart itself anyway.
Every now and then it would boot in and work fine though.
What I eventually did to get it working:
1.) Get a factory cable (they don't cost too much off ebay).
2.) Using fastboot mode clear the data and cache partition:
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
20 seconds later the device worked perfectly and hasn't bootlooped since.
It might also be possible to do this by a.) installing TWRP and erasing the cache/ data from there, or b.) booting into the bootloader from a rooted system. I don't want to test this though because at this point I just want to make this awful thing work properly in stock.
I hope this helps someone else in the same situation. I do remember reading a similar problem on XDA a few months ago when it started giving trouble.
Click to expand...
Click to collapse
Where do i enter this in when I'm in fastboot?
Karetus said:
Where do i enter this in when I'm in fastboot?
Click to expand...
Click to collapse
You need to use the fastboot application. You can get it either via the Android Development Kit (just google for it) or just use it from any other source (I know the FlashTool for Sony phones has it along with ADB). Once it is on your PC, open a command prompt window to that folder and run it from there.
Just remember you need the Kindle to be in FB Mode (the screen has a picture of a red and green stoplight on it) and you need fastboot drivers installed for the device (this is a bit tricky for Win8, no problem for Windows 7 though).
hexd said:
You need to use the fastboot application. You can get it either via the Android Development Kit (just google for it) or just use it from any other source (I know the FlashTool for Sony phones has it along with ADB). Once it is on your PC, open a command prompt window to that folder and run it from there.
Just remember you need the Kindle to be in FB Mode (the screen has a picture of a red and green stoplight on it) and you need fastboot drivers installed for the device (this is a bit tricky for Win8, no problem for Windows 7 though).
Click to expand...
Click to collapse
I'm at a screen with a blue arrow a and yellow text that says "fastboot mode"
Karetus said:
I'm at a screen with a blue arrow a and yellow text that says "fastboot mode"
Click to expand...
Click to collapse
Please make sure that you have a Kindle Fire 2 (or at least something in the second generation Fire range). It might help if you take a picture of the device in fastboot mode and post it here.
Also did you boot the kindle into fastboot mode using a factory cable, or using a command from Android itself (it would have involved adb shell).
hexd said:
Please make sure that you have a Kindle Fire 2 (or at least something in the second generation Fire range). It might help if you take a picture of the device in fastboot mode and post it here.
Also did you boot the kindle into fastboot mode using a factory cable, or using a command from Android itself (it would have involved adb shell).
Click to expand...
Click to collapse
From the computer. KFF Aide. I'm still stuck I have been looking for hours.
hexd said:
A few months ago I tried to root/ gapps a KF2 for a friend, and after a freak OTA update the horrible thing kept getting stuck in a bootloop.
Basically if you powered it on it would get stuck on the Kindle pulsing logo until it restarted itself from scratch and did it all over again. Then on the few times it would get to the standard lock screen it would freeze up there and restart itself anyway.
Every now and then it would boot in and work fine though.
What I eventually did to get it working:
1.) Get a factory cable (they don't cost too much off ebay).
2.) Using fastboot mode clear the data and cache partition:
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
20 seconds later the device worked perfectly and hasn't bootlooped since.
It might also be possible to do this by a.) installing TWRP and erasing the cache/ data from there, or b.) booting into the bootloader from a rooted system. I don't want to test this though because at this point I just want to make this awful thing work properly in stock.
I hope this helps someone else in the same situation. I do remember reading a similar problem on XDA a few months ago when it started giving trouble.
Click to expand...
Click to collapse
my kindle fire hd 7 7.3.1 just went into a boot loop. it is recognized by my computer the drivers work it says device cant startup. adb wont work. how do i get it into fast-boot without a factory cable
JORDANZ1998 said:
my kindle fire hd 7 7.3.1 just went into a boot loop. it is recognized by my computer the drivers work it says device cant startup. adb wont work. how do i get it into fast-boot without a factory cable
Click to expand...
Click to collapse
Trying to do any work on a Kindle without a cable is a total pain. If you own the device just pay the few dollars to get one and make your life easier.
If you cannot get into ADB with full root, or a 3rd party recovery that was already installed you will need the cable to fix things.