I have a Gen1 Kindle Fire that will not power up. I bought it as not working so I don't know any history on it. I can usually fix these stuck in boot loop units with no problem.
On this one, I get the Orange/White Kindle Fire logo for 5 seconds and then it shuts down. I have spent a couple of days reading every post in the "5 second bootloop! aka: Don't let your battery die!" thread and have had the KF plugged into a 2 amp charger over night. Nothing seems to work including a factory cable. No drivers get a chance to load and nothing appears in device manager on a pc which loads drivers fine with a different Kindle.
I finally took the battery out and put it in another KF and it booted up no problem. When I went into Settings > Devices it said that the battery charge was 100%. I haven't been able to find any other threads with this same problem.
Now what? Can I use something like Firekit to reflash the bootloader and/or system? Any other ideas?
Any help would be greatly appreciated.
Any words of wisdom out there?
Related
I was running the cm10 build on my rooted kindle fire. its a kindle fire 1st generation. i was searching google for and android 4.2 rom for kindle fire, downloaded and flashed it. then when i rebooted, its not working anymore. it turns on normally and shows the blue kindle fire logo from FireFireFire. it says press power button to change oot options, like we normally do. i let it boot normally, and the rom gets stuck on the bootscreen. so i thought i needed to reflash and factory reset, so i force shut it down and turned it on again. this time, i held the power button to say Recovery. it says booting and the power button turn orange. but then it just gets stuck there. it wont boot into recovery. it just sits there all day with the orange light and the words booting. i cant boot into anything. Anyone Please Help Me... Happy Holidays...
Well for one I haven't seen a 4.2 available for the kindle fire so I am pretty sure your system is broken. Flashing it may have affected the other partitions in some way the one I would be concerned with is the recovery partition which you need access to in order to fix it. Your best bet now is soupkit, first to get some communication with the device, secondly to reflash recovery or force it to recovery bootmode. Here's where to start http://forum.xda-developers.com/showthread.php?t=1850038.
one thing though
My Kindle Fire Has A Damaged Charger Slot, Where You Have To Put Pressure And Bend It Forward To Make It Charge. And I cant Move it When Its Charging My USB isn't doing well either, I Haven't Been Able To Connect My Kindle Fire To My PC In Forever! However, Thanks. If You Know A Way To Get The USB Port On The KFire Replaced Please Let Me Know please.
siju21 said:
My Kindle Fire Has A Damaged Charger Slot, Where You Have To Put Pressure And Bend It Forward To Make It Charge. And I cant Move it When Its Charging My USB isn't doing well either, I Haven't Been Able To Connect My Kindle Fire To My PC In Forever! However, Thanks. If You Know A Way To Get The USB Port On The KFire Replaced Please Let Me Know please.
Click to expand...
Click to collapse
Use tape to hold it in place then maybe you can at least get it fixed so it runs.
Tried that so many times...
Thepooch said:
Use tape to hold it in place then maybe you can at least get it fixed so it runs.
Click to expand...
Click to collapse
Sorry for the delay, Christmas stuff. I have tried for days trying to make a contact between the port and the serial bus. it hasnt worked. the best i could do is get it to charge, but it wouldn't do the same with the usb. im using an android phone usb, chich is VERY thick. mabye i should use the stock usb and give that a shot. i will let you know. :good:
stock usb failed
i used to stock USB to charge my kfire. after charged, its still in the boot loop as expected. i tried to get connection to the device my using my new usb and wiggling it back and forth. the kf utility still wont recognize my kindle no matter what i do. all i can get it to do is turn on to the bootloader. so to make a long story short, i have a boot loader which cant boot into anything. PLUS, i tried soupkit. wouldnt do a thing. i even tried the kfire unbrick utility. none of them can get a connection with my device.
Rank newbie here. I did l watch the video of forum instructions for newbies and I have looked high and low for an answer I could understand. I am still stuck so reluctantly....Here we go...
I rooted my KF 2 Gen and had no problem doing so. Installed Google aps store, launchers etc. all on the stock OS.
All worked well until I got smart and decided to try a custom rom. It seemed to install fine. Asked all the options as I installed. Did I want Chrome, what launchers, etc. I wiped all the cache options and system. Went through all those screens and when it finally booted, I am stuck at the stock Kindle Fire logo in a boot loop. It will not connect to the computer. It seems to boot before it is recognized Dug on this forum, made myself a "factory cable" and it does work. When I plug it in, I get the Kindle logo a moment then a flashing gif of a stop light blinking red and green with the words. "Fast Boot" at the top of the screen. The problem is, I can not get the computer to "see" the Kindle Fire 2 Gen on this fast boot/ factory cable. I have tried switching ports, all the suggestions. The cable will launch the tablet into fast boot mode just fine however, the tablet does not connect to the computer. ( Windows XP Pro SP 3). I think I can figure out how to flash and restore on my own if I can get the tablet to communicate with the computer. I have no idea where to go now other than having a brand new paperweight. I just bought it two days prior and I suppose I could return it but the issues were caused by me so I don't feel like it's their duty to replace it.
Thanking you in advance for your assistance.
Go into TWRP, factory reset, and try again.
soupmagnet said:
Go into TWRP, factory reset, and try again.
Click to expand...
Click to collapse
Thank you for your reply.
Sadly, the boot sequence terminates and it reboots before it ever gets to the TWRP stage.
AV8R318 said:
Thank you for your reply.
Sadly, the boot sequence terminates and it reboots before it ever gets to the TWRP stage.
Click to expand...
Click to collapse
When your device boots, do you see the blue Kindle Fire logo at any point?
Got it going! Thanks to this forum!
soupmagnet said:
When your device boots, do you see the blue Kindle Fire logo at any point?
Click to expand...
Click to collapse
No, Soup. I would never get to the blue logo but....
I got it flying! After I got to fast boot, I swapped the fast boot cable to a regular cable and all was down hill from there on. I'm looking at a booted tablet.
Beers on me next time I am in Austin!
Hi there guys, Good regards too all
There is major problem i couldn't really solve on bring back my kindle that went from booting on the "Kindle Fire" logo only , and then later on it went in to fastbooth ..slowly later i tried to turn on it wont On.
How do i recover this.?
The earlier scenario to this case was : I did successfully rooted the device to CM10.1 Android 4.2.2 custom ROM. followed zedomax (Max lee) everything was good perfect. After awhile i decided to go back to Kindle original OS. and mange to restore back that perfectly. My device was still rooted with superuser and all. After few months went by the auto update went on the apps in there which was (my suspect to this outcome) I left my device in the drawer for day and when I got to use it it was On and hot, the screen was blankbut on
Well restarted the device the "Kindle fire" logo came on and then it hangs to blank on screen only. I mange to and tried to play around with Adb configuration and all it work till fastbooth then next when I turn it on the device was detected and Off later debunk by windows while i was on . then the last few round i tried again later on the was flat dead! couldn't On. (What i highly suspect it is just the battery got drained out )
Chances are the battery dried to what I d suspected cause when the last i was using the battery was 45% and 1 days pass with this minor testing on trying to debug it .
If it is the battery How do i charge it back? - get it going (will the factory cable work?)
Is there any other alternative in reviving my device.? - since it wont on.
I highly do believe its only the battery that got drain off otherwise i cauld find my way back to the device just figuring out how do i bring it back in to charging it?
*cause now it is totally does not turn on cause it is drain in battery and being bricked I cant charge in between
Any other suggestion or alternative.? or shall i wait for my Factory cable to revive it?
Thanks
Har.
*I do believe it's possible to bring my Kindle back but how. ?
My unlocked phone will only work if it is plugged into the charger.
If I unplug it it will go into an endless loop of the amazon start screen.
Stock rom and I just upgraded to the new firmware.
Please help!
Please help!
Can you access recovery?
updated below
not even the stock recovery?
I can access stock recovery only when the phone is plugged into the charger
Will not work if the phone is plugged into the computer via usb
xjakerobertsx said:
I can access stock recovery only when the phone is plugged into the charger
Will not work if the phone is plugged into the computer via usb
Click to expand...
Click to collapse
then this is out of my league.
xjakerobertsx said:
I can access stock recovery only when the phone is plugged into the charger
Will not work if the phone is plugged into the computer via usb
Click to expand...
Click to collapse
I'm guessing this means you have a faulty battery. The fact that it works on the charger and not unplugged or plugged in via USB is indicative the phone believes the battery is completely drained.
I would try to following before contacting Amazon for a warranty replacement: Try to factory reset from the Amazon Stock Recovery (assuming you're certain you are on FireOS). I would then let it charge turned off for a couple hours and try to turn on. If it works, great. If not, I'm afraid working with Amazon is your only avenue.
Any update on the case? I had the same situation. My fire phone having endless bootloop. Only if I connect to charger it can work.
Manage to go to recovery, wipe all, problem still persist.
Same thing
Went into stock recovery
Wipe the phone clean and it still gives me the endless loop
Anyone got an fixes for this? How can I pull all my pics off if this if it keeps rebooting
bump for help
blazin6969 said:
Anyone got an fixes for this? How can I pull all my pics off if this if it keeps rebooting
Click to expand...
Click to collapse
Try to charge your phone and turn it on. If can, you can use WiFi file explorer from play store to pull your data. Make sure fire phone and pc or laptop connect to the same WiFi.
Mine will goes to bootloop if direct connect to pc or laptop.
I just started having this problem yesterday, same exact symptoms. Wiping cache took an incredibly long time, factory reset went smoothly, but neither fixed the issue. It went in to another boot loop immediately after the reset completed, and only came out if it when I plugged it in to a charger again.
That said, it told me a little later that it had updated its firmware, congrats yada yada... and so far (fingers crossed) it hasn't acted up again.
It's now on Fire OS 4.6.6.1 (466001420), I couldn't say what it was before. Can anyone still experiencing this report what version you are on right now?
Also, it may or may not be relevant that I allowed the phone to charge for over 12 hours before disconnecting it.
Have you tried booting into stock recovery then pushing amazon update file to the phone via adb (adb sideload)?
sirkero said:
I just started having this problem yesterday, same exact symptoms. Wiping cache took an incredibly long time, factory reset went smoothly, but neither fixed the issue. It went in to another boot loop immediately after the reset completed, and only came out if it when I plugged it in to a charger again.
That said, it told me a little later that it had updated its firmware, congrats yada yada... and so far (fingers crossed) it hasn't acted up again.
It's now on Fire OS 4.6.6.1 (466001420), I couldn't say what it was before. Can anyone still experiencing this report what version you are on right now?
Also, it may or may not be relevant that I allowed the phone to charge for over 12 hours before disconnecting it.
Click to expand...
Click to collapse
Is it possible do to update you fix your issue? I had charge my phone for more than 12 hours but no luck...
I will try to update via sideload adb. If anyone can show me the link for the how to appreciate it.
Sent from my MI 4LTE using XDA-Developers mobile app
Update on mine:
The firmware update did not fix the problem. It is still possible that it alleviated the situation for a time, but much more likely it was just coincidental timing.
My Fire Phone behaved itself for most of a day and a half, then suddenly went back to the boot loop. I left it this way overnight to try to deep cycle the battery.
After draining completely, it took several hours on the charger before it began showing a charging screen, which comes and goes in intervals just like the Amazon logo had before. It has not progressed beyond 0% charge since then. I'm assuming a faulty battery at this point, or perhaps a corrupt battery stats file (but that should have cleared with the factory reset correct?)
My sincere apologies for any false hopes I may have given anyone.
sirkero said:
Update on mine:
The firmware update did not fix the problem. It is still possible that it alleviated the situation for a time, but much more likely it was just coincidental timing.
My Fire Phone behaved itself for most of a day and a half, then suddenly went back to the boot loop. I left it this way overnight to try to deep cycle the battery.
After draining completely, it took several hours on the charger before it began showing a charging screen, which comes and goes in intervals just like the Amazon logo had before. It has not progressed beyond 0% charge since then. I'm assuming a faulty battery at this point, or perhaps a corrupt battery stats file (but that should have cleared with the factory reset correct?)
My sincere apologies for any false hopes I may have given anyone.
Click to expand...
Click to collapse
It's OK mate, we all trying to find possible solutions for our problem.
Cheers.
Sent from my MI 4LTE using XDA-Developers mobile app
Solved replacing battery
I had this problem weeks ago, solved by:
1.- Drained battery to 0% (may skip this step? idk)
2.- Replaced battery for a new one (Search for one in amazon)
3.- Fully charged the new battery.
4.- Turned on fire phone.
cramosa said:
I had this problem weeks ago, solved by:
1.- Drained battery to 0% (may skip this step? idk)
2.- Replaced battery for a new one (Search for one in amazon)
3.- Fully charged the new battery.
4.- Turned on fire phone.
Click to expand...
Click to collapse
+1 for this.
I had this problem and just replaced battery. Fire Phone worked great again !
Can't believe a. faulty battery cause many problems.
Btw, if you replace battery by yourself, please notice the attached glue between battery and case. Try to remove them all gently - can search on YouTube how to replace Fire phone battery.
Hello there everyone! Let me explain my problem:
Backstory
I have a Samsung Galaxy Nexus GT-i9250 maguro since 7-6 years or so. I've been flashing some roms into it and everything went well since a week ago.
I had installed from a very long time this version of CM "cm-13.0-20160921-NIGHTLY-maguro" and I have not updated it, so I basically was running that from a very long time.
Three weeks ago the phone started behaving strangely, it was closing automatically, and I thought that it was a temperature problem (being a very hot summer) so I did not worry too much.
Everything was working fine, charging and connecting via USB .
Problem
Last week the phone once again died and I tried to boot it up normally as I would normally do, but nothing happened, not even the Google logo popped up.
So I removed the battery and put it back in, the phone booted up to the Google logo, then after two or three seconds the Google logo flashed like brightness went up to 100% and black screen.
Went into fastboot, booted TWRP to see if that was working, and the recovery was working fine.
Things got worse.
At the moment
I cannot get the phone to do anything if it's not connected to a power source.
If the phone is connected via USB, or charger, I can get it to go ONLY on fastboot, and download mode. If I unplug the phone while on fastboot or download mode, the screen brightness goes up to 100% for half a second then it glitches out and goes into black screen immediatelly. I can not access bootloader nor recovery mode from fastboot, because the phone reboots, shows the Google logo and then it dies.
What I tried
Thinking that maybe the ROM went crazy, I followed this guide to flash the phone with all the original ROM and recovery (I downloaded "yakju-jwr66y-factory-4cadea65" and followed the instructions of the guide).
Nothing changed, if the phone is not connected to a power source, it is basically dead, if I put it to a power source it shows the charging logo for a second, then black screen, and I can only boot up fastboot and download mode.
I don't know if this might help but I've also tested the battery voltage and it seems to be fine.
Last thing, if I connect the phone to the PC (with the battery or without) every 2 seconds it shows up that an unidentified device is being detected.
I currently am using a laptop running windows 8.
On my desktop computer the same thing happens (the device detection) but from device manager I see a OMAP4400 (something like that) popping up but at the moment I cannot use my desktop PC since I'm traveling.
I would really like to know what happened to my phone, any answer will be appreciated.
Thanks in advance!
Update [solved]
After doing some research and trying different methods I gave up. But then I realized that maybe trying the stupidest thing could be the solution, so I went to a phone shop and asked them if they had some sort of test battery that I could plug in my phone temporarily to see if it was booting up.
Turns out, it was the battery.
I bought a new battery and now the phone runs smoothly like it's new.
I feel so dumb and I'm so sorry if I've made some of you people waste your time by reading the poem of the first post.
Hopefully this will someday help someone that will have the same problem of my GT-I9250!
(This thread can be closed now)