Related
I believe im having the "5 second bootloop" problem, no idea why since my KF was never rooted, flashed, or modified in any way. I plugged the Micro B in the KF (KF was off) and then plugged the Type-A end into my PC, the KF turned on in like 10 seconds (maybe less) and it isn't doing the bootloop anymore which i guess is a good thing but its been like 10 minutes and it still just says kindle fire (with a green light on the bottom). What should I do from here for my specific situation? Any help would be great! Thanks in advance!
edit: just wanted to add that before when i would plug it in, it would keep rebooting and usually not even get to the slide to unlock screen, but sometimes it would and then instantly reboot again.
First off...what bootloader do you have installed?
How could I find out? I never modified it if that helps? So it should be stock everything.
also i downloaded KFU and installed the drivers, but it does not recognize my device, altho when i first plugged it in after installing the drivers it said kindle in Device Manager, since it didnt go anywhere i unplugged the kindle and turned it off, when i tried again it installed ADB, but still doesnt recognize it (it also prompted me to restart, which i did right before i posted this reply, and still not recognized, also still at the kindle fire screen with green light on)
Untraumatized said:
How could I find out? I never modified it if that helps? So it should be stock everything.
also i downloaded KFU and installed the drivers, but it does not recognize my device, altho when i first plugged it in after installing the drivers it said kindle in Device Manager, since it didnt go anywhere i unplugged the kindle and turned it off, when i tried again it installed ADB, but still doesnt recognize it (it also prompted me to restart, which i did right before i posted this reply, and still not recognized, also still at the kindle fire screen with green light on)
Click to expand...
Click to collapse
ok so i read that sometimes it just wont read that it worked... so i check device manager, it said android phone, went to KFU, still said unknown after 0+enter, then i tried 3, it said it worked and to press any key to reboot, i pressed a key but the kindle didnt reboot, is it supposed to? also i tried 4 then like i read to do and it says the download path is incorrect so whats wrong?
Untraumatized said:
ok so i read that sometimes it just wont read that it worked... so i check device manager, it said android phone, went to KFU, still said unknown after 0+enter, then i tried 3, it said it worked and to press any key to reboot, i pressed a key but the kindle didnt reboot, is it supposed to? also i tried 4 then like i read to do and it says the download path is incorrect so whats wrong?
Click to expand...
Click to collapse
sorry for triple posting i will fix it but i dont want to confuse you on the timing of these events lol... so i figured out that CWM may be broken right now??? anyways since twrp worked i insatlled FFF with worked and now its at a menu that is kindle fire but BLUE fire text and says press power button for boot menu, but when i do that it doesnt do anything, do i need to unplug it?
Untraumatized said:
sorry for triple posting i will fix it but i dont want to confuse you on the timing of these events lol... so i figured out that CWM may be broken right now??? anyways since twrp worked i insatlled FFF with worked and now its at a menu that is kindle fire but BLUE fire text and says press power button for boot menu, but when i do that it doesnt do anything, do i need to unplug it?
Click to expand...
Click to collapse
you still there buddy? lol, i unplugged it and ya that worked, so now im at TWRP, just because it seems like a good idea i am backing up the things that were already checkmarked when i clicked backup
but now im afraid to continue without help, what step am i at exactly now? lol
EDIT: stuck at the end of the backup, been stuck there a while, will probably try to turn it off in a few minutes or so... anybody have some advice?
How about a little more information about what it is you intend to accomplish with your device?
soupmagnet said:
How about a little more information about what it is you intend to accomplish with your device?
Click to expand...
Click to collapse
i just want it to work! my power went out one day while i was sleeping and it was charging, for some reason it was dead (had been at 100% so shouldnt have drained, but the power going out messed with it) and when i tried to charge it, it bootloops
right now i have TWRP installed and FFF installed, what should i do now? i have tried booting it up and it just gets to the slide to unlock screen and then resets back to the blue kindle fire screen
i also just tried to install permanent root with superuser and it seemed to be working then said rebooting and "please wait...." and it never did anything (except the kindle booted back to the blue kind fire screen)
Untraumatized said:
i just want it to work! my power went out one day while i was sleeping and it was charging, for some reason it was dead (had been at 100% so shouldnt have drained, but the power going out messed with it) and when i tried to charge it, it bootloops
right now i have TWRP installed and FFF installed, what should i do now? i have tried booting it up and it just gets to the slide to unlock screen and then resets back to the blue kindle fire screen
i also just tried to install permanent root with superuser and it seemed to be working then said rebooting and "please wait...." and it never did anything (except the kindle booted back to the blue kind fire screen)
Click to expand...
Click to collapse
ANY help would be appreciated... im sitting here screwing with it waiting for a reply....
Untraumatized said:
ANY help would be appreciated... im sitting here screwing with it waiting for a reply....
Click to expand...
Click to collapse
well i managed to fix it by just factory resetting it with no help AT ALL
Very likely the factory reset had nothing to do with it. Just simply having it plugged in via USB may have given it enough time to charge. Questions of this nature are best handled in q & a not in development.
Untraumatized said:
well i managed to fix it by just factory resetting it with no help AT ALL
Click to expand...
Click to collapse
I'm sorry for not sitting at my computer, waiting with baited breath for you to respond, so I can devote all of my attention to your problem. I hope you can forgive me.
I wasnt trying to be offensive lol I was just proud to figure it out with NO HELP AT ALL! But anyways I am pretty sure it wasnt the charge because it was at 56% before and after i did the factory reset, and after the factory reset i backed it up and it finished that time (last time i had to unplug the KF and hard reset it)... Also I tried resetting it a couple times before the factory reset and it always rebooted once it got to the slide to unlock screen. Anyways it works, I am probably going to give it to my mom because of the simplicity (she just needs email, and internet... lol) and I might try to get my hands on a Nexus 7
AND HOW DO I DELETE ALL THOSE REPOSTS? THE DELETE BUTTON ISNT WORKING FOR ME ^__^'
Untraumatized said:
I wasnt trying to be offensive lol I was just proud to figure it out with NO HELP AT ALL! But anyways I am pretty sure it wasnt the charge because it was at 56% before and after i did the factory reset, and after the factory reset i backed it up and it finished that time (last time i had to unplug the KF and hard reset it)... Also I tried resetting it a couple times before the factory reset and it always rebooted once it got to the slide to unlock screen. Anyways it works, I am probably going to give it to my mom because of the simplicity (she just needs email, and internet... lol) and I might try to get my hands on a Nexus 7
AND HOW DO I DELETE ALL THOSE REPOSTS? THE DELETE BUTTON ISNT WORKING FOR ME ^__^'
Click to expand...
Click to collapse
Correct me if im wrong but you can't delete posts....but this thread should not be in Android Dev section, it should be in Q and A... Not to be mean or anything I am going to report this thread so it can be moved to the right section (to help the mods out)
OP, First This Thread Is In The Wrong Place. And It Appears To Me Users Where Trying To Help, On Limited Information. But You Figure It Out On Your Own Great.
Thank You And Thread Closed.
Hello I need a but of help my Nexus 7 is showing my nothing but the google logo and at the store earlier it showed the android with his chest up and a red triangle. it doesnt even show the moving colors after i turn it on it just sits and says google like a paper weight. i can turn it off and on but nothing more. the geek squad at best buy told me to ask for help here at Xda. last thing i was doing with it was opening deer hunter 2013 and next i go to see if it opened and it stuck on the google logo. can anyone help me fix my tablet? its not under store warranty only manufactures.
Well, sucks to be you.....just kidding...but that does suck. Now, on to more serious matters...
Do you have access to your bootloader? (hold the power button + the vol up button at the same time) If you do, you might want to look into rooting the tablet. Based on the content of your post, I am assuming that you haven't. There is plenty information about rooting the Nexus 7.2 tablet (and just about every other Android device). Simply Google "root Nexus 7 2013" and you will quickly find your answer.
Also, how much do you know about rooting and the sort? I want to know before I waste my time giving details about info that you are aware of.
aarsyl said:
Well, sucks to be you.....just kidding...but that does suck. Now, on to more serious matters...
Do you have access to your bootloader? (hold the power button + the vol up button at the same time) If you do, you might want to look into rooting the tablet. Based on the content of your post, I am assuming that you haven't. There is plenty information about rooting the Nexus 7.2 tablet (and just about every other Android device). Simply Google "root Nexus 7 2013" and you will quickly find your answer.
Also, how much do you know about rooting and the sort? I want to know before I waste my time giving details about info that you are aware of.
Click to expand...
Click to collapse
i dont know anything about rooting. i dont have access to the boot loader. i did a few days ago now it wont even show up, the guy and best buy tried to bring it up and its like it was showing a dead android or something chest open with a red triangle above it. he said someting about maybe have to flash a new or or something like that on to it, it wont show me anything just stays off or shows the google logo when its on
Sigh...that is the bootloader. Maybe...he could have booted into the stock recovery, which shows this or something similar for most devices. Please remember, they are reps...they may know about the software, but usually they speak from their experience or their perspective. I'm glad that he sent you here for a second opinion.
Hold the volume down button and power button to get into the bootloader. You should see some options at the top of the screen saying Start, Restart bootloader, Recovery Mode, Power Off. Not sure if those are the exact options, but it's pretty close.
Also, you need to look into rooting your device. You need to download some files first. You'll need adb, fastboot, and drivers for your Nexus.
And one last thing....what Computer OS do you use? The rooting process is slightly different for each one (Windows 7, 8/8.1, Mac OS, & Linux). If you are into computers, and you have Linux installed on a device, good for you. That is my preference when rooting, as Android is built from Linux, and naturally supported without the need for drivers.
I had similar problems when I first bought it. Going into recovery and resetting the tablet cured it. You will lost all your data BTW.
He's facing the loss of his entire tablet, so I'm sure that data loss isn't the biggest thing to worry about.
But yes, just about every solution involves a clean wipe of data.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________
I'm stuck on the google logo too. I had my tablet plugged in over night and when I opened the cover this morning it woke up, but as soon I tried to access anything it rebooted and stuck.
I'm unlocked and have tried various thing. NRT doesn't recognize it as an ADB device so I don't think that will work. Fastboot works, but I keep getting "FAILED (remote: flash write failure)" when I try to use the factory flash all, or the instructions found here: http://forum.xda-developers.com/showthread.php?t=2381582
I can use fastboot to query the device and get it to return "flo" but it seems like the flash storage has failed.
if it's truly horked, can I use "fastboot oem lock" to relock it and attempt a warranty replacement?
sean67854 said:
I'm stuck on the google logo too. I had my tablet plugged in over night and when I opened the cover this morning it woke up, but as soon I tried to access anything it rebooted and stuck.
I'm unlocked and have tried various thing. NRT doesn't recognize it as an ADB device so I don't think that will work. Fastboot works, but I keep getting "FAILED (remote: flash write failure)" when I try to use the factory flash all, or the instructions found here: http://forum.xda-developers.com/showthread.php?t=2381582
I can use fastboot to query the device and get it to return "flo" but it seems like the flash storage has failed.
if it's truly horked, can I use "fastboot oem lock" to relock it and attempt a warranty replacement?
Click to expand...
Click to collapse
You can try Method 2 from this post: http://forum.xda-developers.com/showthread.php?t=2513701
I know it's for the N5, but I used this one for both my Galaxy Nexus, N5 and N7. Since they are all Nexuses (Nexi?), the same general procedures apply. I always prefer to do it all manually, step-by-step, which is why I went with Method 2 in the OP of that thread. Obviously, since this is the N7, just skip the radio flashing command. Everything else is the pretty much exactly the same. If this doesn't work in fastboot, then it's probably a hardware failure.
Hi Everyone
As a new user here, thanks in advance for any help that you can give me.
I've got a KF2, running 10.4.1 (I think, or maybe 10.4.3) - it's rooted, but generally stock apart from that (no TWRP).
It was left with something playing and the battery ran down to nothing yesterday. Initially it would charge, sometimes with the red light on and sometimes not, but then it would start up and as soon as it got to the lock screen it would give a low battery noise and shut down.
After leaving it plugged in overnight it is now charged but it is getting stuck on the animated kindle fire boot logo.
If I plug it into my PC it is detected in windows and I can connect to it with ADB with no obvious errors on logcat. Easy options like clearing the dalvik cache don't fix anything (only AmazonPlatform and atlasframework get recreated in the dalvik cache before it sets into doing nothing).
Searching the forum here, there are lots of different avenues discussed for "stuck at boot logo" problems - I'd appreciate some pointers on the most sensible things to try.
Thanks
Try a system restore with kindle fire first aid.
Sent from my Amazon Kindle Fire HD using Tapatalk
Hello, it seems that you face the same issue as I met last week with KF2 that I got for free. The KF2 got a boot problem after a low bat event and nobody was able to get him back. I seems thats the same issue. While I wasn't able to establish adb i used fastboot with a homebuild factory cable. (Forget KFfirst aid) Take a look on this thread: http://forum.xda-developers.com/showthread.php?t=2698935 - After formating cash and userdata user let him charging for a while on the pc usb port. Next day he returned booting showing a untouched KF2 with factory setup. Rootet him and gave him a CM11. Grate tablet for free. Take care, after formating cash and user he doesn't came back imidiatly Let him for some hours in the fastboot screen blinking his green led on screen. Next day he came back booting. My suspicion is a sw bug regarding low battery events. After cash and userdata format he need to develop valid boot conditions regarding the battery or other stuff. Who knows... But after the procedure he came back without further flaws.
Send via Tapatalk - HW: Kindl HD 8.9 - SW: Android 4.4.2 KitKat < CM 11.0 HC mod.
Thanks for the assistance guys. Sorry for not coming back sooner - I couldn't get my password to work this morning!
I tried restoring to 10.2.3 using KF first aide - after sitting in fastboot for ages downloading the images it flashed ok and then went back to the empty battery screen after it restarted. It stayed like that for so long I thought it was still broken, but eventually it booted back into the kindle launcher.
As I was going from 10.4 back to 10.2.3 I wiped the cache and userdata. Used ADB to get as much data off it as I could first - could I have safely used any of the KF first aide backups on it first?
One weird bit - I've rooted using bin4ry/qemu and used KF First Aide to disable OTA and install google play, maps etc, and now location services don't seem to work any more. Maps, Chrome, Silk, BBC Weather - they all give the location icon in the notification bar but then can't get a location fix.
This is why I don't use Amazon os... Seems like small things like this happen because we either forget to put something on the device that is needed or the os just breaks something like this out of nowhere. In my opinion its easier to avoid these kinda problems altogether by flashing cm but that's just my take, if you want amazon os then keep it. That sounded grouchier than I intended.
Sent from my Amazon Kindle Fire HD using Tapatalk
Stunts513, yes, AOS stucks out of nothing and your gone. On that way a got a kindle for free that entered in a boot loop after a low bat event and even USB recovery doesn't worked worked out by failing and access. Only fastboot and a CM makes that tablet working for real
Send from HTC Sensation - Android 4.4.3 - CM11 - Kitkat
My tablet is the WiFi only version. I had it unlocked and rooted previously.
So I downloaded the new 5.1.1 images, intending to finally switch to Lollipop, and I kept getting the "missing system.img" error when trying use the batch scripts.
So I found this guide:
http://www.talkandroid.com/guides/b...-lollipop-factory-image-on-your-nexus-device/
And tried to follow it to the letter.
Sadly, once I flashed the boot.img, the device wouldn't boot anymore and it won't show up in fastboot and adb.
I also can't seem to boot it into recovery mode. My volume down button is finicky so perhaps I'm not trying hard enough?
Is there anything that can be done?
Edit: Okay, I was being an easily-panicky moron. Stupid key. Must have tried it like 10+ times till it acknowledged my press.
All is fine... I think. Once it finishes optimizing a crap-load of apps.
So, after optimizing everything works fine?
Indeed it does. Marvellously.
Rooted, enjoying the latest of Android and even helped pinpoint the source of a long-standing problem I had with brightness.
It may even help battery life.
Same Problem still exists for me
I have the wifi only version and I seem to be at a loss now.
I cannot get into recovery no matter how many times I try
PC recognises device but as APX
Screen appears to be stuck on an image of Andy stood upright with a sort of hexagonal wire frame rotating in his belly with "erasing" underneath. Stays this way for hours/days and does not change. Have looked through all sorts of forums for help or do you guys think I should just give up??
ANY Help at all would be greatly appreciated
It seems that your device is toast Maybe your NAND storage is faulty and you will need to purchase a new mainboard
tommygraham429 said:
I have the wifi only version and I seem to be at a loss now.
I cannot get into recovery no matter how many times I try
PC recognises device but as APX
Screen appears to be stuck on an image of Andy stood upright with a sort of hexagonal wire frame rotating in his belly with "erasing" underneath. Stays this way for hours/days and does not change. Have looked through all sorts of forums for help or do you guys think I should just give up??
ANY Help at all would be greatly appreciated
Click to expand...
Click to collapse
I had a booting problem as well but i was able to fix it with nexus root toolkit
[Q] So, I flashed the wrong ROM into my 3HT7G 8.9" Kindle fire. Is there any fix?
I have been googling and searching for years with no usable results and fixes to all manner of problems other than what I have here.
Ok... So a few years back, I was using a program (I forget which one) to flash a new ROM and didn't pay adequate attention to what I was flashing into my Kindle 3HT7G 8.9" Fire. I put the rom for the 7 inch model (Oopse!) Anyways this corrupted the boot sector of the device and now the thing is completely non responsive. I have tried googling every variation of the question I am asking and have tried the hold power 30 sec, Hold power while rebooting, various (unbricking utilities) all with absolutely no results other than seemingly dead screen. I have charged overnight, used factory cable on computer, Voodoo magic chants. (ok so I don't know Voodoo) Kind loving words, Harsh threats, pleading... Etc... The closest to an answer was in some thread somewhere, someone said to another person asking similar question was , "Yep it's now a $200 paperweight..." I understand that rewriting the boot sector to something wrong is stupid. (I presume this is where the information that tells the device who and what it is and what all buttons do resides) I did just that. Is there any way to force feed the correct ROM or even remove the memory to mount in another environment to rewrite it? Is this device really completely useless? Or, is there a way but too cost prohibitive? I have been holding on to this device in hopes that one day a cure can be found and I can thaw it out and perform the required surgery on it.
Thanks,
Dan
alarmguydan said:
I have been googling and searching for years with no usable results and fixes to all manner of problems other than what I have here.
Ok... So a few years back, I was using a program (I forget which one) to flash a new ROM and didn't pay adequate attention to what I was flashing into my Kindle 3HT7G 8.9" Fire. I put the rom for the 7 inch model (Oopse!) Anyways this corrupted the boot sector of the device and now the thing is completely non responsive. I have tried googling every variation of the question I am asking and have tried the hold power 30 sec, Hold power while rebooting, various (unbricking utilities) all with absolutely no results other than seemingly dead screen. I have charged overnight, used factory cable on computer, Voodoo magic chants. (ok so I don't know Voodoo) Kind loving words, Harsh threats, pleading... Etc... The closest to an answer was in some thread somewhere, someone said to another person asking similar question was , "Yep it's now a $200 paperweight..." I understand that rewriting the boot sector to something wrong is stupid. (I presume this is where the information that tells the device who and what it is and what all buttons do resides) I did just that. Is there any way to force feed the correct ROM or even remove the memory to mount in another environment to rewrite it? Is this device really completely useless? Or, is there a way but too cost prohibitive? I have been holding on to this device in hopes that one day a cure can be found and I can thaw it out and perform the required surgery on it.
Thanks,
Dan
Click to expand...
Click to collapse
Hello
I have the same problem.
I have a one idea to connect motherboard witch usb card reader and try to repair my kindle. If i will do that I will writing here all. Or maybe U unbrick ur kindle first or allready u do taht.
Thread moved
Can you go into fastboot mode? Or at least use adb commands.
If not, make sure you have Android SDK
Try my tutorial: http://forum.xda-developers.com/kin...help/kindle-fire-hd-8-9-bootloop-fix-t3137732