Hi, I'm stuck in twrp bootloop. When I connect my kindle to PC (Win7) sometimes it shows unkown device and sometime nothing happens. I've searched the web for solutions for 4 weeks and nothing helped me. I tried mount USB storage in twrp, nothing happens. I just want my PC (Win7) to recognize my kindle, then I will follow the instructions from other threads.
*I have a factory cable.
**If you need more information,tell me.
What do you mean by twrp bootloop? Does it keep booting into TWRP over and over?
You're most likely experiencing a driver issue. Try to follow the directions here: http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2 and see if it helps any. Just having the KF show up on the device manager is a good step forward, even if mounting usb storage isn't working.
Are you stuck in FFF or TWRP? What color is the Logo?
Drivers are the #1 cause of pain for KF owners trying to root. What steps have you taken to install the drivers? Are you using KFU?
You should be reading: if you havent
http://forum.xda-developers.com/showthread.php?t=1552547
More spesifically this post regarding how drivers should look, and what to do if they dont.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
I'm stuck in TWRP. Every time I load the device I get to TWRP.
I've read the threads you provided, nothing helped.
I did ''add legacy hardware'' in device manager, now I got Android composite ABD Interface shown but it has the code 10 error.
Y.Always.Me said:
I'm stuck in TWRP. Every time I load the device I get to TWRP.
I've read the threads you provided, nothing helped.
I did ''add legacy hardware'' in device manager, now I got Android composite ABD Interface shown but it has the code 10 error.
Click to expand...
Click to collapse
Have you tried plugging in the KF, uninstalling every single driver relating to Android (even samsung android drivers!), the KF, restarting the computer, and then running install_drivers.bat included in KFU?
The bootloop is very easy to fix - you're most likely stuck in the Recovery bootmode (5001), so having fastboot or ADB set your bootmode to Normal (4000) will solve it, but first you need to sort out ADB/fastboot, which are showing a drivers problem.
As a side note, this probably happened because you are using an outdated FFF/TWRP. When this is fixed, it's in your best interest to update to the latest version of each (1.4a, 2.1.1 respectively).
Dasanko said:
Have you tried plugging in the KF, uninstalling every single driver relating to Android (even samsung android drivers!), the KF, restarting the computer, and then running install_drivers.bat included in KFU?
The bootloop is very easy to fix - you're most likely stuck in the Recovery bootmode (5001), so having fastboot or ADB set your bootmode to Normal (4000) will solve it, but first you need to sort out ADB/fastboot, which are showing a drivers problem.
As a side note, this probably happened because you are using an outdated FFF/TWRP. When this is fixed, it's in your best interest to update to the latest version of each (1.4a, 2.1.1 respectively).
Click to expand...
Click to collapse
I tried, (Have you tried plugging in the KF, uninstalling every single driver relating to Android (even samsung android drivers!), the KF, restarting the computer, and then running install_drivers.bat included in KFU?), but it didnt help.
I have TWRP 2.0.0.
now I dont even get unkown device. What else can I do?? I just want it to show on my PC.
Y.Always.Me said:
I tried, (Have you tried plugging in the KF, uninstalling every single driver relating to Android (even samsung android drivers!), the KF, restarting the computer, and then running install_drivers.bat included in KFU?), but it didnt help.
I have TWRP 2.0.0.
now I dont even get unkown device. What else can I do?? I just want it to show on my PC.
Click to expand...
Click to collapse
TWRP 2.0 included FFF, so you can use fastboot -
Issue "fastboot getvar product" and then plug in the KF, see if the fastboot driver is working. Otherwise, you're stuck on a driver problem again.
If it does list one device, then you can go with "fastboot oem idme bootmode 4000" and then "fastboot reboot". That should get you back on Normal bootmode and out of the TWRP bootloop.
Next would be updating both TWRP and FFF to prevent this from happening again, but there's the pending driver issue. I can't really add much more, other than carefully going through the post linked earlier, step by step.
Dasanko said:
TWRP 2.0 included FFF, so you can use fastboot -
Issue "fastboot getvar product" and then plug in the KF, see if the fastboot driver is working. Otherwise, you're stuck on a driver problem again.
If it does list one device, then you can go with "fastboot oem idme bootmode 4000" and then "fastboot reboot". That should get you back on Normal bootmode and out of the TWRP bootloop.
Next would be updating both TWRP and FFF to prevent this from happening again, but there's the pending driver issue. I can't really add much more, other than carefully going through the post linked earlier, step by step.
Click to expand...
Click to collapse
when I issue "fastboot getvar product" I get('fastboot' is not recognized as an internal or external command, operable program or batch file.)
Y.Always.Me said:
when I issue "fastboot getvar product" I get('fastboot' is not recognized as an internal or external command, operable program or batch file.)
Click to expand...
Click to collapse
Download KFU and then open a command prompt in the "tools" directory.
Idid, it says <waiting for devive>
I pluged KF, nothing happened.
then I restarted it and nothing happened.
I gess I'm stuck for good.
Y.Always.Me said:
Idid, it says <waiting for devive>
I pluged KF, nothing happened.
then I restarted it and nothing happened.
I gess I'm stuck for good.
Click to expand...
Click to collapse
Means you have a driver problem, which takes us back to the starting point. Can't do anything else until you manage to get the drivers installed properly, sorry. Alternatively, you can, on a different computer, download KFU and then run install_drivers.bat BEFORE you plug in the KF for the first time.
Dasanko said:
Means you have a driver problem, which takes us back to the starting point. Can't do anything else until you manage to get the drivers installed properly, sorry. Alternatively, you can, on a different computer, download KFU and then run install_drivers.bat BEFORE you plug in the KF for the first time.
Click to expand...
Click to collapse
I tried nothing happened.
If you are doing flashes and nothing is working go to mount and make sure there are no checks in the boxes for system and data if so remove them then reflash or restore a backup after restore or reflashing a rom go back and check to make sure those boxes still have no check inside them then reboot I have had frequent errors like this when flashing roms that have the gapp package prebaked into the rom I do not have this issue when flashing gapps seperately
I found that from 20% - 80% battery it takes 12 hours
Hey so a few weeks ago i tried to root my kindle fire, version 6.3.1 (to the best of my memory), on windows 7. I tried Kindle Fire Utility but the drivers wouldn't install so i found a different one and ended up bricking it. I was able to use an unbricking tool i found online which worked initially, but a couple of weeks later i restarted the kindle and now it is stuck in FireFireFire (yellow triangle), which i think is fastboot mode (correct me if i'm wrong). I have TWRP installed and have been able to load into it once, but was unable to fix the problem and now have been unable to load into it since. Kindle is mostly unresponsive now, but can turn on and off with the power button and turns on when plugged in. My computer recognizes the kindle as an unknown device and is unable to update the drivers. I have tried reinstalling the drivers from Kindle Fire Utility v0.9.9 dozens of times, yet still nothing. I went to the the "read before you post" thread concerning drivers and attempted to follow that process a few times, however after i have selected the new drivers and clicked next the computer determines that the best drivers are already installed, and prevents me from installing the new ones manually.
Thanks for reading, would be nice if i could fix this issue.
New user so i cant post links, I will put the link to the site i bricked it on in the comments if needed.
Just to get it out of the way: are you rooted?
If you are, try this:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Make sure you have ADB set up before trying this.
gadgetroid said:
Just to get it out of the way: are you rooted?
If you are, try this:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Make sure you have ADB set up before trying this.
Click to expand...
Click to collapse
No midroot it got stuck in fastboot.
Okay so i went and followed the instructions for installing drivers and was able to get my computer to recognize that it is an android phone when plugged in rather than an unknown device. Unbricking tools still wouldn't work, so i followed the instructions to the point where i need to do go to the "have disk" part. After selecting the proper drivers, the computer said that it couldnt update the drivers "since the device cant start (code 10)".
Mudk1p21 said:
Okay so i went and followed the instructions for installing drivers and was able to get my computer to recognize that it is an android phone when plugged in rather than an unknown device. Unbricking tools still wouldn't work, so i followed the instructions to the point where i need to do go to the "have disk" part. After selecting the proper drivers, the computer said that it couldnt update the drivers "since the device cant start (code 10)".
Click to expand...
Click to collapse
Unplug your device and try once.
Hello all.
This is my first post and my first experience with android devices so please go gentle.
I recently purchased for £20 a kindle fire 2nd gen otter.
The reason it was so cheap was that it is stuck in a bootloop.
The friend I bought it from intended to bring it back to life and install CM to the device but never got round to it. So I took it on as my little project.
I have been scrolling through pages and pages of google and this site for research but have hit a brick wall.
I purchased a factory or fastboot cable knowing I may well need it. I also have the original cable.
When trying to boot the device I get the usual kindle and fire logo orange as of it's booting then every 10 seconds or so the screen will go black and back to the kindle fire bootloop.
I have tried to use the normal cable to link to my desktop on windows 7. When doing this the device will not show up in device manager at all.
When I plug it via a fastboot cable it boots into fastboot with a green flashing light on screen and is recognised as an otter prod 04 on device manager.
I have installed the latest sdk. Also fastboot.
I have changed the windows environment variables under path on the PC and can successfully run fastboot in a command window. I can also issue adb commands through also a dos command window so I know both are working correctly on my PC.
I have typed in fastboot devices
I have also typed in adb devices.
When I issue either or these commands my device will not be found through the command window. It just returns a blank.
I know this is due to drivers not working correctly so have opened device manager. Update driver , have tried the android sdk path for drivers have also tried my adb drivers. I have also downloaded the latest Google USB driver and none will install. I have a programme running that allows any unsigned driver to be installed on win 7 so I know it's not that.
All I have returned is cannot install drivers for otter prod. 04
The only thing it will accept is choosing from a list of devices, Then android. And installs as adb device or adb composite device, this is obviously useless as I can't boot device into normal mode to be able to use it as adb or issue commands to it.
I have tried everything. I know this kindle is save able I just don't know how. My end result is make it bootable, root device and install CM
I have trawled through loads of pages of info and tried tried and tried for answers but nothing works. Can anybody shed some light on the issue for me.
Many thanks in advance
Just thought id add, I have also tried all timed variations of holding down the power button
I have also let device run flat and recharge. Have also tried a different PC and USB port.
Hello Vincent,
ADB stands for Android Device Bridge (Just wanted to point that out since you are new to Android).
The ADB Composite Device driver lets your computer and your Kindle Fire device communicate with each other. This includes ADB as well as fastboot.
Install the ADB Composite Device driver in Device Manager and then go to the command line window and type fastboot -i 0x1949 devices and it should now show up in fastboot.
Now flash the stock bootloader, recovery, and system img files to your device. After that, you should see it boot successfully.
Hope this helped, and don't be afraid to ask me more questions about your device!
phiftyopz
Sent from my iPhone using Tapatalk
I need a little help. I tried to unlock and root my phone. I was on build NDE63X. I was able to unlock the device no problem, but then ran into some issue with the root. I'm not sure what happened. Now I am stuck in bootloop.
I am trying to sideload the OTA NDE63X through ADB. However, adb isn't recognizing my device. If I type "fastboot devices" then it pulls up my device. I have tried to uninstall my drivers and reinstall the drivers and every time the driver says "Android Bootloader Interface". I don't know if that is the problem or not. Any help would be appreciated.
Thanks!
charr83 said:
I need a little help. I tried to unlock and root my phone. I was on build NDE63X. I was able to unlock the device no problem, but then ran into some issue with the root. I'm not sure what happened. Now I am stuck in bootloop.
I am trying to sideload the OTA NDE63X through ADB. However, adb isn't recognizing my device. If I type "fastboot devices" then it pulls up my device. I have tried to uninstall my drivers and reinstall the drivers and every time the driver says "Android Bootloader Interface". I don't know if that is the problem or not. Any help would be appreciated.
Thanks!
Click to expand...
Click to collapse
unplug the phone
switch off the phone
press power + volume down
does it go in Fastboot mode ?
Hi.
Got a problem here I can't solve on my own.
QFIL-flashed a stock rom (tried to fix the blue screen on boot-thing) and was thinking it should be a breeze to unlock the bootloader and so on. But nope.
I have:
* Adb and fastboot installed
* The ZUK USB-drivers (yes, have turned off the option for windows to require signed drivers)
* Tried different USB-ports. Even another computer
* Other drivers, such as the "mi flash" drivers, universal ADB-drivers, naked ADB-drivers...
I have enabled USB-debugging, and when I write adb devices (when the phone is in android), the device is shown.
Then I use the "adb reboot bootloader" fo get into fastboot. The phone says fastboot_mode, but when I try to find the device via "fastboot devices", it's not shown.
In windows device manager the driver is OK, and shown as "ShenQI Composite ADB Interface".
Any clue what's wrong?
Well, I used the "tool all in one", and now it works....from that program. But still no devices in fastboot devices when I check manually....