I rooted my fire a couple weeks ago. Used the KFU and everything worked perfectly. I have the android marketplace. I even downloaded the OTA something that allows you to temporally disable so I can still watch prime videos.
But tonight it powered off on its own and got stuck on the yellow triangle screen. I tried using the KFU and change it to normal boot mode. which seemed to work. It got to the Kindle fire screen and booted up. As soon as the carousel popped up it shutdown immediately and got stuck on the yellow triangle screen. It keeps doing this. Any ideas.
I tried reading many of the other threads, but I got majorly confused. So any help is appreciated. Thanks
edit: I noticed i had a few seconds before it would shutdown on me. I was able to open OTA rootkeeper and turn the root back on before it shutdown. As soon as I click restore root, it shutdown again, but it booted up fine. Im thinking the issue was caused by the root temporally being disabled. Is this a known problem. Seems to be working fine, will update tomorrow.
Edit: seems I have to changed it no normal boot everytime. Is there a way to unroot my fire. Hopefully its not too complicated.
Thanks for anything guys.
And I think the root is disabled at the moment, but not a %100 sure. NOt sure if that matters.
Mine's doing the same thing. I think it has something to do with the new OTA update? Mine will start up then reboot into recovery...any thoughts guys?
I'd start here, since it appears many others had similar problems with the OTA push:
http://forum.xda-developers.com/showthread.php?t=1634075&page=2
Supposedly KFU rooting still works. You may need to try this method again. Check this thread and see what others had to say as far as what worked for them. Good luck!
How do I unroot it completely. Its still getting stuck on yellow triangle. I used it for 30 minutes last night. Now unless I make it boot up normally, it gets stuck. getting frustrated.
Now when I use KFU to start it in normal mode, it gets to the Kindle fire screen, and occasionally the screen where I typed in my code to unlock it and it turns off, black screen, It will only turn on when plugged in.
edit: I guess my battery somehow died overnight. Swear it was full when I went to bed
Would updating my fire with the usb get rid of the root? I just want it back to normal. What is easiest way to do that?
Now its stuck on this cycle where it says theres an error and the kindle fire must reset to its original factory settings its does this. Reboots I think and does it again. Its stuck like this.
To break root and restore everything back to original:
http://forum.xda-developers.com/showthread.php?p=25681034
soupmagnet said:
To break root and restore everything back to original:
http://forum.xda-developers.com/showthread.php?p=25681034
Click to expand...
Click to collapse
Thanks but I cant get out of the cycle of what I said in my last post. I think my Fire is broken for good.
Can you boot into recovery? Do you know how?
soupmagnet said:
Can you boot into recovery? Do you know how?
Click to expand...
Click to collapse
I was able to before. My computer doesn't recognize the Kindle anymore
Guess I will be buying a new one.
TURBO1112 said:
I was able to before. My computer doesn't recognize the Kindle anymore
Click to expand...
Click to collapse
Your computer doesn't need to be recognized by the computer to boot into recovery.
soupmagnet said:
Can you boot into recovery? Do you know how?
Click to expand...
Click to collapse
I *think* I'm having the same issue. When the fire is not plugged in, it's a black screen. No method of pressing the power button does anything (length of time, number of times, etc.). When it IS plugged in, the standard kindle fire/android logo just blinks. Again, power button has no effect whatsoever.
KFU shows ADB offline and Boot unknown.
Just some background info, I had a rooted working Fire. Out of the blue (likely the OTA update) it got stuck at the triangle logo screen and was able to get it into recovery mode. The first time I just reset it to factory.
Rooted again using KFU, said successful root, but installing Google apps kept saying failed or error until finally saying "All done!"
Then tried to install TWRP, and KFU got stuck at trying to put the fire into fast boot mode then <waiting for device>. Recovery screen came up again, and (here's where I made a bonehead decision) figuring I would help things along, I selected fast boot mode. It was stuck on the kindle fire screen for hours. I even tried reinstalling the drivers but that failed. I left it plugged in to my PC and when I woke up this morning I found it in the state it is in now that I first described above.
I will continue to search more threads for an answer, but if I don't update this one that I've found one, it means I haven't.
fzdolfan said:
I *think* I'm having the same issue. When the fire is not plugged in, it's a black screen. No method of pressing the power button does anything (length of time, number of times, etc.). When it IS plugged in, the standard kindle fire/android logo just blinks. Again, power button has no effect whatsoever.
KFU shows ADB offline and Boot unknown.
Just some background info, I had a rooted working Fire. Out of the blue (likely the OTA update) it got stuck at the triangle logo screen and was able to get it into recovery mode. The first time I just reset it to factory.
Rooted again using KFU, said successful root, but installing Google apps kept saying failed or error until finally saying "All done!"
Then tried to install TWRP, and KFU got stuck at trying to put the fire into fast boot mode then . Recovery screen came up again, and (here's where I made a bonehead decision) figuring I would help things along, I selected fast boot mode. It was stuck on the kindle fire screen for hours. I even tried reinstalling the drivers but that failed. I left it plugged in to my PC and when I woke up this morning I found it in the state it is in now that I first described above.
I will continue to search more threads for an answer, but if I don't update this one that I've found one, it means I haven't.
Click to expand...
Click to collapse
The "blinking" boot logo is indicative of a dead battery, probably caused by leaving it in fastboot mode for so long.
http://forum.xda-developers.com/showthread.php?p=25400963
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
http://forum.xda-developers.com/showthread.php?p=20317299
Your best bet is to follow the first link and do what you can to install FFF1.4 and that will allow you to charge your battery from such a low power state.
You'll have to use the fastboot flash command for this so be sure that the file you use to flash your bootloader is in a .bin format. Simply renaming a .zip to .bin will not work. You have to extract the u-boot.bin from the FFF1.4.zip, otherwise you will hard-brick your device. If you're unsure of what you're doing, ask for help.
On the chance you can't get FFF1.4 installed, you'll need to acquire a factory cable to keep the device powered on long enough to install your bootloader.
Another user recently had a problem that required a factory cable to fix. Take a look at that thread so you have an idea of what needs to be done and how to fix your problem. His problem was different from yours but the solution is the same. http://forum.xda-developers.com/showthread.php?p=25693109
soupmagnet said:
The "blinking" boot logo is indicative of a dead battery, probably caused by leaving it in fastboot mode for so long.
http://forum.xda-developers.com/showthread.php?p=25400963
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
http://forum.xda-developers.com/showthread.php?p=20317299
Your best bet is to follow the first link and do what you can to install FFF1.4 and that will allow you to charge your battery from such a low power state.
You'll have to use the fastboot flash command for this so be sure that the file you use to flash your bootloader is in a .bin format. Simply renaming a .zip to .bin will not work. You have to extract the u-boot.bin from the FFF1.4.zip, otherwise you will hard-brick your device. If you're unsure of what you're doing, ask for help.
On the chance you can't get FFF1.4 installed, you'll need to acquire a factory cable to keep the device powered on long enough to install your bootloader.
Another user recently had a problem that required a factory cable to fix. Take a look at that thread so you have an idea of what needs to be done and how to fix your problem. His problem was different from yours but the solution is the same. http://forum.xda-developers.com/showthread.php?p=25693109
Click to expand...
Click to collapse
Even after reading the posts regarding the factory cable, I'm still not sure what the difference is. I have been (successfully) using a Motorola Android phone cable that when plugged into the Fire (when it was working) would say that USB is connected and I can now transfer files. I also successfully rooted it once before and installed all the apps and such with the KFU. What would be different that would make this cable only now insufficient?
Btw, I was able to charge it using the stock wall charger. At least I assume it is charged because it is no longer blinking the kindle fire logo, and I am able to shut it down by holding the power button even when plugged into the USB cable.
However, it still won't do anything but show the android/kindle fire logo (static, not flashing/oscillating) whether it's turned on with or without a cable plugged in. Opening the KFU and trying boot modes does nothing. There is no acknowledgment whatsoever that it is connected to the PC either from the fire or the PC. I don't even get the sound effect from the PC that something has been connected via USB.
fzdolfan said:
Even after reading the posts regarding the factory cable, I'm still not sure what the difference is. I have been (successfully) using a Motorola Android phone cable that when plugged into the Fire (when it was working) would say that USB is connected and I can now transfer files. I also successfully rooted it once before and installed all the apps and such with the KFU. What would be different that would make this cable only now insufficient?
Btw, I was able to charge it using the stock wall charger. At least I assume it is charged because it is no longer blinking the kindle fire logo, and I am able to shut it down by holding the power button even when plugged into the USB cable.
However, it still won't do anything but show the android/kindle fire logo (static, not flashing/oscillating) whether it's turned on with or without a cable plugged in. Opening the KFU and trying boot modes does nothing. There is no acknowledgment whatsoever that it is connected to the PC either from the fire or the PC. I don't even get the sound effect from the PC that something has been connected via USB.
Click to expand...
Click to collapse
A "factory cable" is specially made to interact with the device in a way that is different from the OEM Motorola USB cable you are currently using. With a little research and a little more reading you'll be able to find out what the difference is and why it works for fixing dead battery issues.
Using the stock charger was one of the very first things covered in the first link that I gave you. I'm trying to help you fix your problem so please try to pay attention to the information I'm giving you.
So now that your battery issue is resolved, you have to fix the next part of the problem which is resetting your bootmode. By far the easiest way to do this is by flashing the latest 1.4 version of FireFireFire in recovery. Be sure to use recovery to install it or you may find yourself in more trouble than you started.
The thread for the new version along with important information on how to install and use it can be found here: http://forum.xda-developers.com/showthread.php?t=1632375
soupmagnet said:
Using the stock charger was one of the very first things covered in the first link that I gave you.
Click to expand...
Click to collapse
I realize that, and I acknowledged it in my post by stating that it solved the drained battery issue. I also gave thanks on your post.
Accusing me of not paying attention is not necessary.
I only said that I don't see the difference in the factory cable because a) my drained battery was resolved by other means and b) I did read in the factory cable thread that "Seems like you have power and this cable is maininly for when your ... battery is dead and you need to ... fastboot with no battery life left.... So the cable does not matter in your case since your battery has power you can use any usb cable."
soupmagnet said:
So now that your battery issue is resolved, you have to fix the next part of the problem which is resetting your bootmode. By far the easiest way to do this is by flashing the latest 1.4 version of FireFireFire in recovery. Be sure to use recovery to install it or you may find yourself in more trouble than you started.
The thread for the new version along with important information on how to install and use it can be found here: http://forum.xda-developers.com/showthread.php?t=1632375
Click to expand...
Click to collapse
I also looked at this thread, but the initial post seems to imply that I already know how to "Apply this flash.zip from recovery just like any other ROM or kernel .zip file.", which I do not.
As I said, my fire is currently stuck at the kindle fire logo and does not respond to being plugged in to the PC (other than turning on to the kindle fire screen).
Admittedly, I only went about 4 pages deep into the thread, but it seemed to be all posts of thanks (for the most part) to the original post. I will continue reading the thread if you're saying that it indeed contains more helpful information.
I apologize if my post came across as ignorant or lazy, but the fact is that I've been researching this for the better part of the day, and I see plenty of info on what to do if I can get my PC to communicate with my Fire, but the first problem is that I cannot find out how to hurdle that first very important obstacle.
Just to save us both some time (and I do appreciate your patience and willingness to help), are you saying that I need a factory cable regardless of the state of the battery? Because if that's the case, then my first priority is to figure out how to get one, because my knowledge, means, and experience in soldering and inner workings of electronics is zero, so making one myself is not an option.
Forgive my impatience but playing twenty questions with other, less motivated to learn users, gets kind of old after a while (not to say that you fall into that category). Not to mention, I'm a prick and have very little patience to begin with.
With a good charge on your battery there is no longer a need for a factory cable.
Most of the users here are fairly proficient with the use of recovery so its easy to overlook those who aren't. That's why it's important to know up front what your level of experience is, to avoid such assumptions.
Your recovery (TWRP or CWM) has a mount function for mounting certain partitions as external drives onto your computer. Your computer will recognize it in the same way it does a thumb drive. Use it to mount your sdcard and transfer the FFF1.4 so it can be installed while in recovery.
Once installed, reboot and hold the power button as if you were trying to enter recovery again and you will be able to select which mode to boot with. Choose "Normal Boot".
Greetings,
I have a rooted epic running the latest Clean GB
The other night the phone went crazy, it would reboot over and over and the screen would lock out. I went into CWM and restored it back to when I first installed Clean GB about 2 months ago. It had an error the first two times then it went on the third time. Then the phone crashed while rebooting and now will only go to the Samsung black screen. I cannot boot to cwm only to the Download screen (#1 and power). I tried connecting it to my computer to try and odin it back and I can not get it to connect. After reading the forms I re-installed the drivers uninstalled rebooted installed over and over. about 10 times. I found on the forums that the stock cable could be bad so found 3 other cables at home and tried them, still nothing then went to radio shack and bought the 22$ cable and still nothing. I have tried 3 different computers (2 windows 7 and 1 windows xp) every usb port on all the computers it says the device has malfunctioned. Odin does not recognize the device either does Heimdall. I am lost can you guys help me out? or do I need to see if sprint can fix it or use it for target practice? Thanks for your help
It may be a bad motherboard.
Sent from my PantechP4100 using xda premium
draginspect3 said:
Greetings,
I have a rooted epic running the latest Clean GB
The other night the phone went crazy, it would reboot over and over and the screen would lock out. I went into CWM and restored it back to when I first installed Clean GB about 2 months ago. It had an error the first two times then it went on the third time. Then the phone crashed while rebooting and now will only go to the Samsung black screen. I cannot boot to cwm only to the Download screen (#1 and power). I tried connecting it to my computer to try and odin it back and I can not get it to connect. After reading the forms I re-installed the drivers uninstalled rebooted installed over and over. about 10 times. I found on the forums that the stock cable could be bad so found 3 other cables at home and tried them, still nothing then went to radio shack and bought the 22$ cable and still nothing. I have tried 3 different computers (2 windows 7 and 1 windows xp) every usb port on all the computers it says the device has malfunctioned. Odin does not recognize the device either does Heimdall. I am lost can you guys help me out? or do I need to see if sprint can fix it or use it for target practice? Thanks for your help
Click to expand...
Click to collapse
What kind of usb cables? just because it was $22 doesn't means its a good data cable. I find thick blackberry cables are the best, i leave one plugged into my pc.
.
Also make sure your micro usb port on the phone isn't dirty. I find a can of air duster works well.
Are you downloading the correct drivers straight from samsungs website?
If you can get into download mode its either usb port is bad, cable is bad, or computer doesn't play well with your phone.
Sent from My Epic Ice Cream Sandwich With Sprinkles!!!
Thanks
Thanks for the ideas, I just cleaned my usb ports on my computer and on the phone and nothing. The cable is the thickest one I can find. I have read on other forums that they have had great success with that cable. Who knows, I may try and find black berry cable or take it to someone that knows more than I do. If anyone has any other ideas it would be greatly appreciated.
Thanks
Thanks
I forgot to mention that yes I downloaded them from Samsung and also from a thread on xda.
Hey,
I have looked everywhere found many tricks and tips, guides, programs, drivers, yet i'm still have problems. I think that it could be problems with my phone. I recently bricked my phone (installed a rom from a different note 2 version and was stuck in a boot loop). Went to go plug in the phone to restore back to stock and the phone wasn't detected. It was a new laptop so i figured it was a driver issue. Installed the drivers still nothing. Long story short I have installed multiple drivers, Note 2 toolkit (mskip big thanks), Samsung Kies, and Odin (all at separate times) all in an attempt to get this phone connected. I have tried 2 different USB cords, different plug-ins, different computers yet still nothing. Now I have gotten my phone back to stock but went to install a new rom and now it wont load past the boot screen. But that was after my trying for a whole day of plugging in and unplugging before 1 time it was connected. I can not understand the issue besides it being my phone. I don't have anything else to try besides plugging it in and out over and over for the 1 time it decides to work and connect. I am getting very frustrated with this because I currently have no phone. Is their a way to tell if the connector is messed up in any way? I'm really needing help because nothing i'm doing is working.
Steepgnomeking said:
Hey,
I have looked everywhere found many tricks and tips, guides, programs, drivers, yet i'm still have problems. I think that it could be problems with my phone. I recently bricked my phone (installed a rom from a different note 2 version and was stuck in a boot loop). Went to go plug in the phone to restore back to stock and the phone wasn't detected. It was a new laptop so i figured it was a driver issue. Installed the drivers still nothing. Long story short I have installed multiple drivers, Note 2 toolkit (mskip big thanks), Samsung Kies, and Odin (all at separate times) all in an attempt to get this phone connected. I have tried 2 different USB cords, different plug-ins, different computers yet still nothing. Now I have gotten my phone back to stock but went to install a new rom and now it wont load past the boot screen. But that was after my trying for a whole day of plugging in and unplugging before 1 time it was connected. I can not understand the issue besides it being my phone. I don't have anything else to try besides plugging it in and out over and over for the 1 time it decides to work and connect. I am getting very frustrated with this because I currently have no phone. Is their a way to tell if the connector is messed up in any way? I'm really needing help because nothing i'm doing is working.
Click to expand...
Click to collapse
Have the same issue. I am trying fr a work computer, internet restricted, no kies. Now can only recognize note 2 as a camera. When I switch thw usb settings in android, I get the not supported box. Same thing happens at the home computer. I left bb for this??
This is a simple hardware fail and needs to be taken in for warranty repair. The fact that it's bricked, we'll you're just gonna have to cross your fingers and hope they don't charge you for a new one.
Or you can try a jig to get it into download mode and try to push a rom through.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Thats what i'm going to do take it in and see if they can fix it but i want to get it back to stock firmware before but not being able to plug it in to update it is kinda ruining that plan.
Well I turned in 3 notes with custom roms that were rooted and I never got charged, but I always run a stockist rom.
What rom did you flash?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Are u able to boot in recovery?
PM me if u need help
Sent from MOON......
Can you boot into recovery? If so then you can push a file to your SD card using adb. If your having problems with Samsung drivers or what ever good way to test is connecting your phone to a Linux box and setting up udev and adb. Then you can do a adb device command and see if it sees it.
If you have the time to install Linux on a extra hard drive or duel boot you can connect using adb.
Nice thing about Linux is that you can connect directly to the USB device using udev and the device id and with ADB you can push a file onto your phones SD card. Here's a good how to
http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
Sent from my SGH-I317 using xda app-developers app
hey guys. i havent messed with this in a while but i did the usual stuff then flashed hell fire o it a couple years ago and it boot looped on me. so i finally got around to playing with it and using my factory cable it goes right into bootloader but my computer has no clue its even plugged in. cable is fine ive used it in the passed to unbrick a couple motorollas and it goes straight to loader from power off. i have all the drivers including every sdk package but i cant figure this out? if i power off and reboot without cable it just freezes at the helfire loading screen but never goes further. so it isnt really looping actually. either way i cant get it recognized by my laptop (win 7 x64) not even with a standard data cable which i verified with gs6 is working. anyone have any advice on how to get a working fastboot connection with this or am i just sol? thanks
ps. i have stock bootloader 1st gen fire but i believe it has twrp though i cant remember the version and i cant get into it. adb doesnt recognize it, device manager shows nothing the computer does nothing when i plug it in regardless the cable. very strange. any and all help is appreciated. thanks guys!
dannyHD2 said:
hey guys. i havent messed with this in a while but i did the usual stuff then flashed hell fire o it a couple years ago and it boot looped on me. so i finally got around to playing with it and using my factory cable it goes right into bootloader but my computer has no clue its even plugged in. cable is fine ive used it in the passed to unbrick a couple motorollas and it goes straight to loader from power off. i have all the drivers including every sdk package but i cant figure this out? if i power off and reboot without cable it just freezes at the helfire loading screen but never goes further. so it isnt really looping actually. either way i cant get it recognized by my laptop (win 7 x64) not even with a standard data cable which i verified with gs6 is working. anyone have any advice on how to get a working fastboot connection with this or am i just sol? thanks
ps. i have stock bootloader 1st gen fire but i believe it has twrp though i cant remember the version and i cant get into it. adb doesnt recognize it, device manager shows nothing the computer does nothing when i plug it in regardless the cable. very strange. any and all help is appreciated. thanks guys!
Click to expand...
Click to collapse
twrp doesn't work with stock bootloader
custom Roms should not work with stock bootloader
what is on bootloader screen?
So, this morning my son (who has a Nexus 5X) says his phone is bootlooping. I said "gimme that!..you don't know what you're doing." Lol
Thought I could fix it, but an hour later, a dozen google searches and trying a bunch of different things I can't get ADB mode to work on this phone!!
I'm using a Windows 10 PC that works fine with my Nexus 6P and ASUS tablet. I reinstalled USB drivers just in case but that's not it. I've tried different cables with no luck either.
I can get the 5X to boot into recovery mode where I see the dead Android robot with 'no command' under him. I then press the power button + volume up to get to ADB sideload menu. I can hear the "da da" music of the PC seeing something on the other end of the USB cord but no matter what I do, no ADB/Fastboot. I've even tried the LGUP tool, that even says no device attached.
I was hoping someone may have some way to restore the device. It boots up the Google logo then reboots Google logo then just shuts itself off. Every once in a while I can get it to boot to the Android boot animation for about 2 seconds before it freezes and shuts itself off. The device is about 11 months old (one year warranty?) and has never been rooted.
Thanks for any info... **I called Project Fi, going to get a replacement**
Sorry, I totally missed the last part before replying.
It could be a hardware failure. Since you're so close to 12 months, I would contact Google (or LG if not from google) and let them try to troubleshoot. That's the best way to get warranty repair. They will run you through any steps that might work. You just don't have much time to troubleshoot.
Sent from my Nexus 9 using Tapatalk
Mine does not appear at all on Windows or any operating system I'm guessing none if the init files should be zero bytes either I have no idea wth happened I check the root system with root browser and got this and my 5x is bootlocked I reset it dozens of times and still no recognition set mtp manually via devel options and nothing
Don't know about these files but re-installing (updating) all drivers seems to work for me. I've had to do this many times in the past 4 months for rooted N5, & N9, not rooted but bl-unlocked N5X, and virgin N5X. Never had to do this before and could use multiple devices interchangeably with Windows 10 which I've had since its beginning. Wugfresh has a driver install/repair section on his NRToolkit that can be helpful.
Sent from my Nexus 9 using Tapatalk
Sorry this is old thread. but I have same issue with nexus 5x. though it recently experienced BLOD and flashed 4cores. did you find a solution to your problem? mine however only recognized in adb on ubuntu. but no where else. no windows 10. and on ubuntu mtp didn't work
are you guys checking your adb device drivers in windows?