I was going to use the hashcode JB ROM, here are the steps:
Downloaded KFU, installed driver (Shows up as ADB interface)
Installed permanent root
installed TWRP
installed FFF
Copied jb-kfire-hashcode-07-13.zip to the download folder
Boot into recovery, backup, wipe cache, wipe dalvik
installed - .zip file
Rebooted to nothing
Now it's a black screen, the power light is amber when plugged in. My Win7 PC still recognizes it, but that's it.
I've tried the unbricking tool GUI , no matter what I choose it's < waiting for device >
I then tried the Firekit , ran "usb_fix_parts_and_install_fff_twrp" and it's just sitting there "waiting for OMAP44xx device..."
What now?
Well, I was going to do the USB shorting trick, so I started unplugging the battery and I saw the LED go green. I flipped it over and realize it was rebooting so I was able to boot into recovery and then restore the backup I made before all of this started.
Then I started the process all over again, but I got it working with the JB ROM...
Related
Just a moment ago I pushed my own custom framework-res to the phone. I had only edited some picture files inside it. After rebooting it worked correctly so I edited some more images, booted into clockworkmod recovery and tried to push in a new framework. But this time my adb just gave me an error "error: device offline".
After rebooting into revoked recovery I tried using adb again but with the same result. I also noticed that my computer suddenly installed all of the Android related drivers again, there were four different drivers it installed.
I thought it was because of my custom framework so I decided to flash my custom rom again. I didn't do a full wipe and after rebooting I got stuck in a bootloop.
So currently the only way I can access the phone is in fastboot. My computer recognizes the phone when it's in recovery but I can't use any adb commands. When I type adb devices it lists my devices but says it's offline. I tried doing the first step of the rooting process and it worked fine but after booting into recovery I tried doing the step2 but the device was still offline.
Is this because of my Windows drivers or did I screw up the Android system somehow?
You should have made a backup using nandroid. I though think you need to wipe.
Sent from something using the internet.
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?
i was curious to get get android market on my kindle today.. and looked up how. i used the kindle fire utility to root it. then my KF it started to go into a loop of the boot logo. it just flashes on and flashes off over and over again.hard reset doesnt affect it at all, it wont even turn off unless i unplug it. it doesnt show up on my computer either.
i dont know if this helps but when i ran the Kf utility it said 'findstr' not recognized.. blah blah blah. and it didnt give me the 1234567 options on there. i just typed in '2' and pressed enter because thats what the video told me .-. it doesnt have a triangle, or a blue screen logo either just the kindle fire logo flashing off and on. I honestly am lost. please keep this noob friendly
i am running win 7. 64 bit.
josepho1997 said:
It seems like your stuck in fastboot mode. You need to reinstall the drivers manually and then go into KFU. Press 1(bootmode)and 1(normal). If you still want to root it, when it gets to installing fff, and if it says <waiting for device>, you need to do a hard reset and your Kindle, unplug, plug it back in, and manually install the drivers. Then it will finish rooting.
Click to expand...
Click to collapse
How do you reinstall the drivers manually? and also when i go into the kindle fire utility it doesnt give me 1,2,3,4,5,6,7 options... it just says findstr is not a recognized as an internal or external command, operable program or batch file. and another thing i tried another utility on here and it said it said my device was not found when i plugged it in , is it because it turns off every 5 seconds?
First before you mess with your drivers 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
Edit: hit enter after each command
zellerax said:
How do you reinstall the drivers manually? and also when i go into the kindle fire utility it doesnt give me 1,2,3,4,5,6,7 options... it just says findstr is not a recognized as an internal or external command, operable program or batch file. and another thing i tried another utility on here and it said it said my device was not found when i plugged it in , is it because it turns off every 5 seconds?
Click to expand...
Click to collapse
Sounds like there's some sort of PATH problem with your setup, which is why KFU won't work properly. You'll have to manually use ADB/fastboot commands if you want to get things done.
About it turning off constantly, it's probably out of battery. Use the stock wall charger (it provides a greater power output, don't bother with USB or a random clone) so it can refill some. The bootloops may be due to a bad boot mode, but it's a bit hard to pinpont with your description of the issue.
You may want to have a read here, it'll help you to better understand what's going on and how to express yourself about the problems you are experiencing: http://forum.xda-developers.com/showthread.php?t=1552547
zellerax said:
How do you reinstall the drivers manually? and also when i go into the kindle fire utility it doesnt give me 1,2,3,4,5,6,7 options... it just says findstr is not a recognized as an internal or external command, operable program or batch file. and another thing i tried another utility on here and it said it said my device was not found when i plugged it in , is it because it turns off every 5 seconds?
Click to expand...
Click to collapse
You might have corrupt drivers. Here's how to reinstall them:
Try going to your Control Panel >> Device Manager. If you see an entry for "Android Phone," (Android ADB interface) delete it (and any associations with Portable Devices >> KF or Kindle Fire).
Restart computer.
Then go to your KFU utility folder, open "install_drivers.bat" (right-click "Run Administrator"). This shouldn't take long at all.
You might want to restart here too after.
Then open KFU utility, plug in Kindle - if all went well here, you should read something along the lines of "Online" and "4000".
I am a similar situation
Hi Guys,
I rooted my KF with no issues, was able to copy the Jellybean and Gapp zip file to the SD and thought I flashed with no issues. Then rebooted. Now the KF is stuck in a boot loop. If I boot to recovery, that works and allows me the recovery options. if I boot up to normal, it constantly reboots, if I boot to fastboot, it displays the Kindle Fire logo and says "press power button to boot menu" at the bottom and does nothing else. My computer recognizes it as Android ADB interface but will not allow to access the SD ram. Any help would be greatly appreciated.
It's usually better to start your own thread here on Q&A.
Are you able to access the SD Card from TWRP? (Mount USB)
If so and the ROM is still in there, wipe cache, dalvik-cache, factory reset and system, then flash/install the ROM again (don't install gapps yet) and reboot. If it boots all the way to the desktop, reboot to recovery and install gapps.
You may also want to check the ROM's hash.
You haven't mentioned what versions of TWRP and FFF do you have, either. Hopefully 2.1.1 or 2.2 for TWRP and 1.4a (blue "fire" on the kindle fire logo) for FFF.
Dasanko said:
It's usually better to start your own thread here on Q&A.
Are you able to access the SD Card from TWRP? (Mount USB)
If so and the ROM is still in there, wipe cache, dalvik-cache, factory reset and system, then flash/install the ROM again (don't install gapps yet) and reboot. If it boots all the way to the desktop, reboot to recovery and install gapps.
You may also want to check the ROM's hash.
You haven't mentioned what versions of TWRP and FFF do you have, either. Hopefully 2.1.1 or 2.2 for TWRP and 1.4a (blue "fire" on the kindle fire logo) for FFF.
Click to expand...
Click to collapse
Thanks for the info and sorry for the incomplete initial info. I will check this as soon as I get home and can work on it again.
Thanks for your help. It turns out that I didnt even have TWRP installed. Thats fixed. I was able to get roms installed and have different problems. (Will start a new thread in another area) Thank you very much for your help.
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 was looking to do a full wipe from TWRP and wanted to wipe data as well. Knowing that that would erase everything from the internal storage and not having an SD card available to me now I decided to wipe everything and then transfer the new ROM with adb commands.
Before wiping, I wanted to make sure that adb was working first. So I downloaded the Android SDK and booted to TWRP. Went to Advanced--->ADB Sideload and started the command prompt on my PC. From the folder were adb.exe was I typed "adb usb" and got error:device not found.
I don't know why but after 30 minutes trying to fix that I pressed the "Fix permissions" option in TWRP and now my phone is stuck at the boot logo every time I try to turn it on. I also noticed in Device Manager on my PC that every time I connect the phone to the PC that there is a yellow exclamation mark next to the phone which suggests that I don't have the needed drivers. However I tried to install versions 3.10 and the newest 3.12 and the exclamation mark is still there.
So my question is how do I reach the phone with ADB and transfer the flashable ROM zipfile so I can get the phone past the boot logo?
Well I'll answer myself if anybody has the same problem in the future. It was obviously the USB driver's fault and since none of the LG's drivers worked, I used Google's USB drivers and was able to adb sideload the ROM zip and now it's booting into the OS.
So always check your drivers people! In case LG's don't work, then use Google's!