I have been researching and trying various things for a week now, including soupkit.
Every partition on the Kindle had been wiped, so there is no OS installed.
I am able to boot my kindle into fastboot mode using fastboot -i 0x1949 oem idme bootmode 4002 which lets me flash a bootloader, firefirefire 1.4a and a recovery TWRP 2.6
However nothing I do will get the kindle to register over USB unless its in fastboot mode. I have been in linux and it does not even detect the kindle when it is plugged in. Therefore I can not mount the USB drive and put a factory image on the sdcard to flash through recovery nor can I push a factory image with adb to the sdcard to flash through recovery.
It seems my only option would be to flash a system.img through the fastboot mode which i am still able to enter, but I am unable to find a good copy of stock 6.3.2 or any other system.img that would able my kindle to boot again or possibly re-enable the ability to use adb or mount the usb drive. Hopefully someone could point me in that direction or give some other suggestion.
Maybe I'm missing something, but why can't you boot into recovery (by pressing the power button while booting to get the Recovery option) , connect via a standard USB cable (not a factory cable) from the KF to your computer, and then use 'adb push <pathname> /sdcard/' to copy to the KF whatever ROM you want to install, and then install it using the TWRP commands on the KF?
aarons510 said:
Maybe I'm missing something, but why can't you boot into recovery (by pressing the power button while booting to get the Recovery option) , connect via a standard USB cable (not a factory cable) from the KF to your computer, and then use 'adb push <pathname> /sdcard/' to copy to the KF whatever ROM you want to install, and then install it using the TWRP commands on the KF?
Click to expand...
Click to collapse
I can boot into recovery, but when I plug in a USB cable at that point, the kindle does not register on a computer. Like I said, I even tried in Linux using the command lsusb, it does not show, it will only be on the list if in fastboot mode.
Maverickwolf said:
I can boot into recovery, but when I plug in a USB cable at that point, the kindle does not register on a computer. Like I said, I even tried in Linux using the command lsusb, it does not show, it will only be on the list if in fastboot mode.
Click to expand...
Click to collapse
The answers to the following questions are probably all in the affirmative, but, just to be sure, I'll ask anyway:
Does your computer recognize other devices when they are plugged into the same cable?
Have you tried other cables?
Does the Kindle work as it should when in recovery, aside from not being recognized by your computer?
aarons510 said:
The answers to the following questions are probably all in the affirmative, but, just to be sure, I'll ask anyway:
Does your computer recognize other devices when they are plugged into the same cable?
Have you tried other cables?
Does the Kindle work as it should when in recovery, aside from not being recognized by your computer?
Click to expand...
Click to collapse
My computer does recognize other devices as well as the kindle in fastboot mode.
I have tried different cables as well.
The kindle functions in recovery aside from not being recognized. I have also tried flashing older versions of TWRP and CWM and no detection on those either.
Related
So I've read the similar threads, no clear answer.
I've searched the forums with no real clear answer.
So before I continue, I just want to make sure that this is correct.
Kindle Fire turns on, I have fully charged it overnight, and it still boot loops. The Kindle Fire logo comes on, flashes on and off, logo shows again with the logo glimmering, and then turns off and back on. It starts the process over. Very rarely will it go all the way to the arrow that you slide but you can't ever slide it over to get in, it just restarts.
So from my understanding is that the shell is corrupt and I need a factory cable to force fastboot. Is this correct? Thank you for reading my post.
Not necessarily. If you are talking about the stock "Kindle Fire" logo. Skip to the second half.
If you are talking about the FFF1.3 Kindle Fire logo with the Andy above it, you should be able to get into recovery, so long as you flashed a recovery.
If this is the case, start the kindle and watch the power button. When it dims press it a few times. It should change to an orange/amber color after a few presses and then boot into your recovery. From there you can load a rom and get yourself back on track.
If you have the stock bootloader, I'm not sure this will work for you, but it won't hurt to try. Worst case you are out the time it took you to make the USB.
As I found out yesterday, fastboot occurs so quick that Windows might not have the chance to discover and install drivers. So if you have a USB drive, create a firekit LiveUSB.
Once you have a LiveUSB and have booted off it and started firekit, try running normal_boot and then, when powered off, plug the kindle into the computer. With luck, it will reboot and start up into your rom.
If you are unlucky, try install_fff_twrp. Again have the kindle off, and connect it to the USB.
If that does not work try again with install_fff_twrp_from_stock as a last ditch effort.
If that fails, get your factory cable. You can try the other commands too, but I wouldn't hold your breath. But, if it works great.
ok well first off when I first turn it on, I get the yellow fire warning sign that states at the bottom to push the power button for recovery.
I'm getting things to install just fine but anytime it has anything to do with ADB, it does not work. It doesn't work with a regular cable nor the factory cable. Everytime it states that device is not found.
From what I've read the drivers are working properly if I'm able to use fastboot and it shows up in the device manager as a Android Phone > Android ADB Device.
The only time I can keep it recognized by the computer is with the factory cable.
If I use the regular cable, it recognizes it for a second then boots into TWRP but the computer doesn't see the Kindle anymore.
All I'm needing to do is reinstall STOCK Firmware. When I first got it, it just boot looped.
Use the factory cable to change your bootmode to 4000. Reboot, then turn it off and let it charge. It sounds like you are stuck in fastboot mode (4002) with a dead battery, and if I'm not mistaken the device won't charge in fastboot. The factory cable forces fastboot mode, bypasses the battery and provides power directly to the device which is why you are able to issue fastboot commands with the cable.
Sent from my Amazon Kindle Fire using xda premium
Charged
When I am not working on it, I plug it back up to the charger to charge, so charging isn't the problem. TWRP states that the battery is 98% charged when I unplug it.
in twrp you have to manually mount the system and sd card from mount options!
Mount the sd card, save the kindle update bin file, renaming it to update.zip and install from twrp
[Note to self:] Avoid using XDA while on Ambien.
wiredextreme said:
I'm getting things to install just fine but anytime it has anything to do with ADB, it does not work. It doesn't work with a regular cable nor the factory cable. Everytime it states that device is not found.
From what I've read the drivers are working properly if I'm able to use fastboot and it shows up in the device manager as a Android Phone > Android ADB Device.
Click to expand...
Click to collapse
Not necessarily true when using Windows and KFU. Sometimes you still have to uninstall/delete your drivers and reinstall again.
The only time I can keep it recognized by the computer is with the factory cable.
Click to expand...
Click to collapse
If I use the regular cable, it recognizes it for a second then boots into TWRP but the computer doesn't see the Kindle anymore.
Click to expand...
Click to collapse
If it boots directly into TWRP, then you have your bootmode set to recovery.
All I'm needing to do is reinstall STOCK Firmware. When I first got it, it just boot looped.
Click to expand...
Click to collapse
If all you want to do is reinstall stock this is easy to fix. Go to the Amazon Kindle website and download the latest 6.3 update. It will be in a .bin format.
Change the name of the update.bin to update.zip
Boot your Kindle to TWRP
Go to "Mount" and mount your SDcard
You should see "[X] Unmount Sdcard" before pressing "Mount to USB"
Your device's sdcard will show up on your computer
Place the newly renamed update.zip on your sdcard
Go to "Install" and flash the update.zip
When installed, the update.zip will turn everything back the way it was when you turned it on for the first time.
Sent from my Kindle Fire using xda premium
In TWRP, it will not let me select Mount SD Card, it will only let me select Mount System. :X
The only option I know of besides Linux liveUSB Firekit, would require you to format your sdcard and you would lose all of your data. You might be able to mount your system folder to transfer files and just flash it in TWRP from there but I've never tried it. If that doesn't work and you don't mind erasing your whole sdcard...
Boot into recovery (TWRP)
Get your command prompt ready with adb in your present working directory (if you're not sure type: dir )
adb shell
echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file
That will mount sdcard to your computer like an external drive. You'll probably have to format it. In Windows, select Quick Format > FAT32 > block size 4096.
Just make sure that the volume you are formatting is your sdcard (>5Gb) You should be able to move your update.zip to it then.
soupmagnet said:
You'll probably have to format it
Click to expand...
Click to collapse
May be am missing something here, but why can't he "adb push update.zip sdcard/Download" and Flash it from twrp?
I tried to install [JB 4.3.1] CM10.2/SGT7 [20131022] and now bootlogo CM is looping. Tried reinstall but result is the same. I can enter in FFF, TWRP is installed. What should i do?
Hi, I recently bought a factory cable because my Kindle is bricked. I'm stuck at the kindle fire logo with no adb shell and fastboot says "waiting for device". I got in this situation by doing a wipe from twrp and then flashing the stock recovery (dumb, I know).
Anyway, with a regular cable I can do basic adb commands (adb reboot, etc).
With the factory cable my kindle isn't showing up under adb devices. Windows recognizes it and it shows up in the device manager. I've already re-installed the drivers and everything.
Here's an outline of what happens when I plug in the factory cable. This is starting with the kindle off.
Kindle turns on and goes tot he kindle fire logo and freezes. The power button is green with the factory cable. I noticed that with the normal cable it's orange. I'm not sure if this has any relevance at all.
Anyway, I'm wondering what I can do to get my kindle to show up in adb while using the factory cable.
If you need more info from me let me know and I'll add it.
A factory cable puts the device in fastboot mode, therefore will only accept fastboot commands.
soupmagnet said:
A factory cable puts the device in fastboot mode, therefore will only accept fastboot commands.
Click to expand...
Click to collapse
I'm not sure if I'm missing something, but fastboot commands aren't working either. It's not showing up under fastboot devices and fastboot flash recovery hangs at "waiting for device".
WhatTheFiber said:
I'm not sure if I'm missing something, but fastboot commands aren't working either. It's not showing up under fastboot devices and fastboot flash recovery hangs at "waiting for device".
Click to expand...
Click to collapse
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
The second post is about device drivers and what to look for in the device manager when your device is in fastboot mode.
It's also possible that you aren't including the vendor ID in your fastboot command. That's covered in the third post.
kinfauns said:
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
The second post is about device drivers and what to look for in the device manager when your device is in fastboot mode.
It's also possible that you aren't including the vendor ID in your fastboot command. That's covered in the third post.
Click to expand...
Click to collapse
Thank you so much! I was able to flash twrp by using fastboot -i 0x1949. Now I've just got to choose a new rom to flash .
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!
I know that this has been gone over multiple times, but I can't get any of the other threads to help so I figured I'd post my own.
Basically, I worked for Best Buy for awhile, rooted the demo Kindle Fire we got at work and that was that. So I figured I could get a demo Kindle Fire off Ebay and just get it rooted and Rom'ed. Well, I can't get the damn thing to be recognized by my computer in ADB.
I've literally tried everything, I've changed the android_usb.ini file to include the 0x1949 and the other file to have the kindle fire in it. Then I tried to point the Kindle to the new file that was changed. Everytime I update the driver it stays as the MTP Device and I can't get it to ADB Composite. I've tried the KFF and that doesn't work either. Uninstalled drivers and reinstalled with no success.
Also, it seems that every time I plug the Kindle into the computer it reinstalls the Drivers.
I do have a Factory Cable on the way so I'm hoping that that will work for me if nothing else does.
Thanks in advance all.
As long as the factory cable you speak of is the fastboot cable that is all you will need. Simply get it into fastboot, flash FFF and TWRP, transfer a Rom.zip and Gapps.zip to the sdcard, do a full wipe in recovery minus the sdcard/external storage. Flash Rom, flash Gapps and reboot. if you get it properly into fastboot your driver will read Android ADB interface. If your running windows 8 you need to disable driver signature verification in order to install the driver.
Thepooch said:
As long as the factory cable you speak of is the fastboot cable that is all you will need. Simply get it into fastboot, flash FFF and TWRP, transfer a Rom.zip and Gapps.zip to the sdcard, do a full wipe in recovery minus the sdcard/external storage. Flash Rom, flash Gapps and reboot. if you get it properly into fastboot your driver will read Android ADB interface. If your running windows 8 you need to disable driver signature verification in order to install the driver.
Click to expand...
Click to collapse
Thanks! It should be here today so I'm excited. I read all of what you've posted multiple times now in other threads, I just haven't been able to get it into fastboot so I'm really hoping that fastboot cable works for me.
Thanks for the quick reply Pooch.
Well. It's bricked. Couldn't get it to boot into twrp. After trying for awhile I decided to just flash fff as I knew the recovery was there. I get nothing now. Completely black screen and no led on power button. I've tried the whole firekit short usb with no luck. It gets past the first part but then just sits at waiting for device. So I'm lost. Is it fried?
I've been trying to root my Kindle Fire running 6.3.3. I bought a fastboot cable and got it to boot into fastboot mode to flash TWRP and firefirefire. I ran the commands and TWRP failed but firefirefire installed. Now when the kindle boots I get the firefirefire bootloader but it cant boot into the recovery because the TWRP never installed. Also, I can't get it to fastboot anymore, not even with the cable. Can anyone please help me get TWRP installed? I've read many forums and tried about everything I found.
kas782000 said:
I've been trying to root my Kindle Fire running 6.3.3. I bought a fastboot cable and got it to boot into fastboot mode to flash TWRP and firefirefire. I ran the commands and TWRP failed but firefirefire installed. Now when the kindle boots I get the firefirefire bootloader but it cant boot into the recovery because the TWRP never installed. Also, I can't get it to fastboot anymore, not even with the cable. Can anyone please help me get TWRP installed? I've read many forums and tried about everything I found.
Click to expand...
Click to collapse
FFF bootloader supports fastboot commands, but the flash command is now
fastboot flash recovery file name
ie drop the -i 0x1949
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img
because the fastboot mode window is short
with kindle connected to pc, power off kindle, enter commands, then power on kindle
sd_shadow said:
FFF bootloader supports fastboot commands, but the flash command is now
fastboot flash recovery file name
ie drop the -i 0x1949
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img
because the fastboot mode window is short
with kindle connected to pc, power off kindle, enter commands, then power on kindle
Click to expand...
Click to collapse
I've been trying this for about 30 minutes or so with no luck...I even downloaded a different version of the twrp image. Do I have to wait for the fastboot screen to start the command or do I start the process before powering on the device? I'm not really sure what I'm doing wrong here.
kas782000 said:
I've been trying this for about 30 minutes or so with no luck...I even downloaded a different version of the twrp image. Do I have to wait for the fastboot screen to start the command or do I start the process before powering on the device? I'm not really sure what I'm doing wrong here.
Click to expand...
Click to collapse
Should be able to do it either way but I press enter, before the power button
This will not work if drivers are not correct
could try
Code:
fastboot devices
as a test should get something like
Code:
123456789 bootloader
back in command prompt
I finally got it to work and I can't thank you enough. You were right. I knew my computer recognized the device with adb in normal boot but my computer wouldn't recognize the device in fastboot mode until i reinstalled the android driver while it was in fastboot mode. Now I have a custom ROM running Google Play apps! Again, thank you!
Hey, I don't know if this will help others, but I had a hell of a time trying to get my kindle to recognize while in the bootloader/fastboot mode... It frustrated me so much that I had to write about it.
I recently switched to Windows 10, so it seems like my computer is relearning drivers and stuff...
My kindle was fine when on, and I could issue adb commands from the main screen, but when in fastboot mode, I couldn't get it detected. I knew the drivers were an issue, but I couldn't figure out how to do it. I looked at Amazon's support pages, went through the SDK route, tinkered with the adb.ini and so forth... to no avail.
Post after post said that the easiest way to install the drivers was through the Kindle Fire Utility, but for some reason, the drivers in the .bat file kept failing and would not load. It took a good few hours to figure out the solution.
When I asked the Web why the drivers kept failing, I came across a post that said Windows was actually blocking unknown drivers from loading onto my system. I really wish Windows had told me that instead of just saying "Fail"...
I had to hold down the shift button and click restart on the start menu, and when the computer restarted, I when through: troubleshoot -> advanced options -> startup settings and clicked on Restart. It eventually gave me the option to disable that signature verification [F7]
My explanation is crude, because I want you to look it up properly. Just search for "disable driver signature enforcement" and you should be fine.
Hope this helps others out. I may have to revisit my own post just to see how to do this again.