Yeah, so I accidentally reset my kindle, and then it rebooted into TWRP then wiped the files, and now it keeps booting into TWRP. I tried installing the 6.2.1 update and CM7 and neither work. Please help?
You need to change the bootmode. If ADB is working just type:
adb shell
idme bootmode 4000
reboot
Should boot normally after that. Cheers.
I had soemthing similar happen and I had to reinstall the usb driver to get it recognizing the kindle again
Before you get all mad at me, I know there is another thread for this. This is a method that has worked for me when all other methods have failed.
I found out about this after looking around the interwebs for a while when my Kindle was stuck in a recovery loop, or stuck at the boot logo.
Your Kindle is stuck at the boot logo? I think I can help! Follow these steps!
This is WINDOWS ONLY for the time being!
1. Download and extract Kindle Fire Utility. You should be able to easily find it on the xda forums.
2. Reboot your PC.
2.5. If you have FIREFIREFIRE, go into the drivers folder in the Kindle Fire Utility and open up adb_usb.ini. Add the following line:
Code:
0x18d1
Do not delete the other lines.
3. After the reboot, connect your Kindle via USB. Go into where you unzipped Kindle Fire Utility, and run install_drivers.bat
4. Once that's done, open up a command prompt and navigate to the "tools" folder of the Kindle Fire Utility.
You do this by using this command:
Code:
cd (File path to tools folder)
Or in my case:
Code:
cd C:\Users\ZombiePiratez\Desktop\KFire Utility\Kindle Fire Utility\tools
5. After that, run the following commands:
If you DO NOT have FIREFIREFIRE, then use these commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If you DO have FIREFIREFIRE
Code:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
If all else fails, try these commands:
Code:
fastboot oem idme bootmode 4000
fastboot reboot
6. Hopefully by this point, your Kindle will be rebooting. THIS WILL NOT WORK FOR EVERYONE. Only people stuck at the bootlogo, or in a recovery loop.
Now, go have fun with your newly awesome and unbricked Kindle Fire!
What is firefirefire? Have yet to see a formal definition of that
androidcues said:
What is firefirefire? Have yet to see a formal definition of that
Click to expand...
Click to collapse
Its a bootloader
Sent from my Kindle Fire using xda premium
Thanks Man, I was messing around with CM7 and I rebooted into recovery not knowing that it would keep me in a recovery boot loop and KFU wasn't helping trying to help me.
Tierehl said:
Thanks Man, I was messing around with CM7 and I rebooted into recovery not knowing that it would keep me in a recovery boot loop and KFU wasn't helping trying to help me.
Click to expand...
Click to collapse
Happy to help
Zombiepiratez said:
Before you get all mad at me, I know there is another thread for this. This is a method that has worked for me when all other methods have failed.
I found out about this after looking around the interwebs for a while when my Kindle was stuck in a recovery loop, or stuck at the boot logo.
Your Kindle is stuck at the boot logo? I think I can help! Follow these steps!
This is WINDOWS ONLY for the time being!
1. Download and extract Kindle Fire Utility. You should be able to easily find it on the xda forums.
2. Reboot your PC.
2.5. If you have FIREFIREFIRE, go into the drivers folder in the Kindle Fire Utility and open up adb_usb.ini. Add the following line:
Code:
0x18d1
Do not delete the other lines.
3. After the reboot, connect your Kindle via USB. Go into where you unzipped Kindle Fire Utility, and run install_drivers.bat
4. Once that's done, open up a command prompt and navigate to the "tools" folder of the Kindle Fire Utility.
You do this by using this command:
Code:
cd (File path to tools folder)
Or in my case:
Code:
cd C:\Users\ZombiePiratez\Desktop\KFire Utility\Kindle Fire Utility\tools
5. After that, run the following commands:
If you DO NOT have FIREFIREFIRE, then use these commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If you DO have FIREFIREFIRE
Code:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
If all else fails, try these commands:
Code:
fastboot oem idme bootmode 4000
fastboot reboot
6. Hopefully by this point, your Kindle will be rebooting. THIS WILL NOT WORK FOR EVERYONE. Only people stuck at the bootlogo, or in a recovery loop.
Now, go have fun with your newly awesome and unbricked Kindle Fire!
Click to expand...
Click to collapse
Unfortunately this will only work if your windows based computer even recognizes the kindle, which mine doesn't. Thanks tho. I've given mine to my tech geek who has access to linux based system, so hopefully he will be able to recover my brick.
Sent from my MB860 using XDA App
Sorry about that. I wish I could help.
I am a newbie. I recover my kf using the recovery boot with kfu and it works fine now. how could
I know if it is in the recovery boot loop? Many thanks.
Sent from my GT-I9100 using XDA App
Zombiepiratez said:
Sorry about that. I wish I could help.
Click to expand...
Click to collapse
Its ok. I read everywhere its impossible to brick a kindle so im hoping that's true.
Sent from my MB860 using XDA App
My Windows PC wouldn't recognize my KF stuck in recovery mode, either. I think it reported in as an "unknown USB device" or something. I had to shut down the Kindle and then plug the USB in, which for whatever reason got my computer to recognize it. I think it might be similar to the effect of a battery drain?
*Snip*
Double post, fail.
CiggyPipe said:
My Windows PC wouldn't recognize my KF stuck in recovery mode, either. I think it reported in as an "unknown USB device" or something. I had to shut down the Kindle and then plug the USB in, which for whatever reason got my computer to recognize it. I think it might be similar to the effect of a battery drain?
Click to expand...
Click to collapse
Did it just immediately recognize it, or did you have to re-install drivers? And i'm not sure about the battery drain thing...
CiggyPipe said:
My Windows PC wouldn't recognize my KF stuck in recovery mode, either. I think it reported in as an "unknown USB device" or something. I had to shut down the Kindle and then plug the USB in, which for whatever reason got my computer to recognize it. I think it might be similar to the effect of a battery drain?
Click to expand...
Click to collapse
Tried that to no avail as well.
Sent from my MB860 using XDA App
Zombiepiratez said:
Did it just immediately recognize it, or did you have to re-install drivers? And i'm not sure about the battery drain thing...
Click to expand...
Click to collapse
I guess I should make note that by this point I'd uninstalled the driver I used. It was recognized as "kindle" once after I plugged it in while off, so then I went ahead and manually reinstalled the driver (from Jayce Ooi's site), which allowed the fastboot commands to work. Otherwise, the command would hang at <waiting for device>.
Thanks! My kindle fire was stuck at the firefirefire logo. My computer couldn't even recognize my kindle but I uninstalled the Android ADB composite interface and plugged it back in, when the kindle was off. Then I used your commands to get fastboot. I installed TWRP, now I'm stuck in TWRP and can't mount my sd... to flash any rom.
Thanks
Thanks for the info. i thought i'd bricked it and the info worked a treat. that will teach me to keep my mouth shut "of course i can root your kindle"
try fixing permissions under advanced, and then make sure only the sdcard box is marked in mount option.
Sent from my Amazon Kindle Fire using xda premium
Zombiepiratez said:
Before you get all mad at me, I know there is another thread for this. This is a method that has worked for me when all other methods have failed.
I found out about this after looking around the interwebs for a while when my Kindle was stuck in a recovery loop, or stuck at the boot logo.
Your Kindle is stuck at the boot logo? I think I can help! Follow these steps!
This is WINDOWS ONLY for the time being!
1. Download and extract Kindle Fire Utility. You should be able to easily find it on the xda forums.
2. Reboot your PC.
2.5. If you have FIREFIREFIRE, go into the drivers folder in the Kindle Fire Utility and open up adb_usb.ini. Add the following line:
Code:
0x18d1
Do not delete the other lines.
3. After the reboot, connect your Kindle via USB. Go into where you unzipped Kindle Fire Utility, and run install_drivers.bat
4. Once that's done, open up a command prompt and navigate to the "tools" folder of the Kindle Fire Utility.
You do this by using this command:
Code:
cd (File path to tools folder)
Or in my case:
Code:
cd C:\Users\ZombiePiratez\Desktop\KFire Utility\Kindle Fire Utility\tools
5. After that, run the following commands:
If you DO NOT have FIREFIREFIRE, then use these commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If you DO have FIREFIREFIRE
Code:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
If all else fails, try these commands:
Code:
fastboot oem idme bootmode 4000
fastboot reboot
6. Hopefully by this point, your Kindle will be rebooting. THIS WILL NOT WORK FOR EVERYONE. Only people stuck at the bootlogo, or in a recovery loop.
Now, go have fun with your newly awesome and unbricked Kindle Fire!
Click to expand...
Click to collapse
I'm sorry but I tried all the steps above but KF's still stuck at boot logo. I flashed CM9 stock kernel 3.0 with FFF 1.4a and CWR, wiped everything and factory reset, then install...but it just hangs at the blue skating droid logo... any idea?
jamesphan said:
I'm sorry but I tried all the steps above but KF's still stuck at boot logo. I flashed CM9 stock kernel 3.0 with FFF 1.4a and CWR, wiped everything and factory reset, then install...but it just hangs at the blue skating droid logo... any idea?
Click to expand...
Click to collapse
The Unbrick utility won't help in your case. When the device hangs at the boot animation or goes to a blank screen afterwards, the problem is usually one of three things.
* the rom installed is corrupted
* you didn't wipe the necessary data before installing
* you tried flashing a rom that's incompatible with the recovery you are using (I'm betting this is most likely the case)
Try installing a different rom (preferably non-ICS) to see if that fixes the problem. Of so, check to see if you're using the latest version of CWM by Hashcode or install TWRP to run ICS based roms.
Any further questions regarding this matter should be redirected to the Q&A section.
[Edit:] For some reason I thought this was the thread for the Unbrick Utility. Regardless, the solution is still the same.
You are a GENIOUS!!!
Thanks a LOT!!!!!!!!!!
I have previously installed TWRP which has run without any problem, helping me to install the rooted version of KF 6.2.1 firmware posted here in xda a month or so earlier. It has been running fine until yesterday.
For some reason, when I ran Market, it asked for secure login with a "Retry" button which did not work. When I checked it was still registered with my GMail account for Google. Then the wifi started to go on and off for no reason.
I realized something went wrong so I decided to re-install the rooted 6.2.1 using TWRP.
The installation process completed successfully. I pressed "Reboot" button then choose "Power off". However when I restarted the KF by pressing the on/off button, it booted into TWRP by itself (meaning when the yellow triangle came up, I DID NOT press and hold the on/off button to boot into TWRP; the light went orange by itself and booted into TWRP). I switched on and off several times, but it booted into TWRP by itself all the times.
I decided to wipe everything before re-installing the firmware. I got back into TWRP and wiped cache, Dalvik, System, Factory reset and SDcard. When I press "Install" button, the copy of firmware is no longer on the KF because of complete wiping. I press "Mount" -> "Mount USB storage" and hook up the KF to my PC, so that I can transfer the copy of the firmware to the KF.
I repeated the process (firmware installation was again successful), but I still got the automatic booting into TWRP instead of normal boot.
Then I tried using KF Utility 0.9.2 to update TWRP (I originally installed TWRP using the TWRP Installer). However, I could not get it into fastboot mode (the Utility says "fastboot mode: no"). The instruction from the Utility said if installation did not work, try reinstalling the drivers - I ran "install-drivers.bat" and reinstalled the drivers, but did not get into fastboot mode to do anything.
Then I tried to install CM7 instead of the original firmware. I copied CM7 onto KF and used TWRP to install the zip. Again I wiped everything before installation. Unfortunately this time, the installation process did not complete. I rebooted the KF and again it auto-boot into TWRP (probably because there is no OS on the KF now).
I can still boot into TWRP without problem. The nightmare now is that:
When I try to mount USB device so as to connect to the PC to transfer files, my PC does not detect it as a drive.
Before the screw-up, it shows in Windows Explorer as "Kindle" (or "Amazon Kindle device"). Now when I go to device manager and click "Disk Drives", only the HD of the PC shows.
The "Android Phone" ("Android ADB interface") still shows in Device manager when I hook up the KF, therefore I guess I can still use ADB.
So these are my two questions:
(1) How do I get out of the "reboot loop" and stop the automatic reboot into TWRP so that I can boot normally into Android (this is presuming I install the firmware successfully)
(2) What can I do now that "USB Mount" in TWRP does not work? Can I fix it or can I reinstall TWRP?
Thanks.
Desperately yours
ST
If in Device Manager it shows up as "Android Phone" that means you have the ADB drivers installed and it will not mount as a drive. Simply delete the device from Device Manager and replug the kindle to your computer, or just use a different computer.
Sent from my Kindle Fire using Tapatalk
DesDr0id said:
If in Device Manager it shows up as "Android Phone" that means you have the ADB drivers installed and it will not mount as a drive. Simply delete the device from Device Manager and replug the kindle to your computer, or just use a different computer.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
ALL PROBLEMS SOLVED
Thanks. I uninstalled ADB then reconnect KF, and it reinstalled ADB. When I press "Mount USB storage", my PC detects KF as a drive ("Kindle") again.
Actually I also solved the problem of TWRP bootloop:
http://forum.xda-developers.com/showthread.php?t=1390773
I used ADB to issue "idme bootmode 4000". This took my KF out of the TWRP bootloop back to normal boot. I am surprised to see that CM7 installation is successful, despite it seemed that in TWRP this was cut off in the middle, without the usual "installation successful" message that came after original firmware installation.
Can you see it in adb by doing an "adb devices"?
just for the future - the commands to set bootmode to normal depending on the current bootmode and version of fff:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
please mark the subject of the topic (edit first post) to [Solved]
Accidentally erased my stock OS I think. Kindle still rooted and when I turn it on it auto goes to TWRP2.0 after FFF. ADB still working. can I push and flash another ROM or the original stock OS or am I screwed. I did a factory reset instead of going to TWRP like a dork. I can see all the folders and everything from TWRP when I select to flash something.
Mount the sd card from TWRP copy the rom you want then un mount then flash the rom
when you say mount you mean by adb correct --> adb push blah blah rom to kindle unmount then flash using TWRP correct??
You can mount the sd card from within twrp
My kindle won't go into usb mode. when you plug in usb it starts normal with FFF then auto loads TWRP 2.0 how to i load the rom then?
Did you flash a rom already?
I re read your post and you just need to set the boot mode
Use KFU and get your PC to recognize the kindle then set the boot mode to normal
says activating normal (4000) at the top then nothing just the text input blinker???
is there a new KFU am using 9.2
edit after a sec kindle booted on pc to view files --->.> guess u expected that huh. will this work with the stock os software or so i need to put into another folder?
Is KFU recognizing your kindle?
I dont think you erased anything
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
In KFU set the boot mode to normal 4000
it doesn't really do anything and bootmode doesn't change it just sits there saying activating (4000). my pc did recognze my kindle and stock os finally after doing this, but i don't think KFU is.i have stock os which is labled update.zip is in there as well as MIUI. should i try flashing?
you can flash it if you want as long as you have twrp you can pretty much do anything.
sweet thank you for helping bro thought i bricked and screwed up horrible. atl east its just a little funky. next time am going to make sure am not tired or baked next time i try to fix ****. long first day at the college and four hours sleep >.<.
Hello I am having a similar problem as the original poster.
I just got a new kindle and have been playing around with it for a few days. I have had adb working for some time now with updated drivers across the board. Today I decided to apply KFU followed by TWRP. In this process my kindle bricked. This is how it proceeded
1) yellow triangle + TWRP loads but is "empty". KFU fails to recognize kindle.
2) Same as above + PC stopped recognizing kindle only listing it as "Unspecified". (Some hours later after trying various ways to reconnect adb)
3) loss of TWRP --> stuck @ the yellow triangle
Have I totally bricked out? Seems I damaged corrupted the OS or damaged my HD somehow
i asume your in fastboot mode
first fix your drivers by updating the drivers
select manually - the right one for fastboot is "android adb interface" (no composite !)
then
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
I just did a restore setting in the CM7 option after that I cannot boot into the CM7 but only the TWRP...
Can anyone tell me how to reinstall the TWRP...
I tried to use the kindle fire utility to re-install it, however it doesn't connect...
always shows offline..
please help
thanks
Did you restore bootloader, recovery and system from your backup using TWRP? If so you should have TWRP installed.
Please provide detail info what you have done to give further help.
You may need to update your USB diver to get adb working and to be able to install recovery software.
Sent from my Amazon Kindle Fire using Tapatalk
i think you said boot to recovery in cm7 - now you'r in a recovery bootloop - means it boots allways to recovery by itself - right ?
if so (if it is booted to twrp) use kfu option1 - bootmode normal
or issue manually:
adb shell idme bootmode 4000
adb reboot
an other method is to use fastboot commands:
fastboot oem idme bootmode 4000
fastboot reboot
in the case it says <waiting for device> power it off by holding the pwr button for ~20sec till it turns of - pwr on again - the command should resume and finish
a second pwr off/on will bring you back to normal
if commands don't work check your drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Can anyone tell me what the befits are to running cm7 vs a lunched like adw ion the fire?