Was running stock ROM rooted and everything was fine until I restarted the phone today. Started to boot loop and hasn't stopped. I've tried restoring backups, installing a ROM fresh and nothing works, just endless boot loops.
What else can I do?
Edit: Did the second option in the link below and it worked like a charm:
http://forum.xda-developers.com/showthread.php?p=46205598
re: boot loop
themichael said:
Was running stock ROM rooted and everything was fine until I restarted the phone today. Started to boot loop and hasn't stopped. I've tried restoring backups, installing a ROM fresh and nothing works, just endless boot loops.
What else can I do?
Click to expand...
Click to collapse
Have you tried to go into recovery and did a "Factory Reset" yet?
That usually works.
Good luck!
Misterjunky said:
Have you tried to go into recovery and did a "Factory Reset" yet?
That usually works.
Good luck!
Click to expand...
Click to collapse
Yeah, reinstalled entire ROMs and no luck.
themichael said:
Was running stock ROM rooted and everything was fine until I restarted the phone today. Started to boot loop and hasn't stopped. I've tried restoring backups, installing a ROM fresh and nothing works, just endless boot loops.
What else can I do?
Click to expand...
Click to collapse
Sounds like she's bricked unfortunately. Might have put an incorrect kernal or flashing something that wasn't supposed to. I bought a bestbuy warranty and it just saved me, because I made an incorrect flash. It was hard bricked. Nothing I did would fix it. Improper kernals can fry CPUs, and if you're odining your stock firmware from sammobile and it still is looping, chances are that's what's happened.
themichael said:
Was running stock ROM rooted and everything was fine until I restarted the phone today. Started to boot loop and hasn't stopped. I've tried restoring backups, installing a ROM fresh and nothing works, just endless boot loops.
What else can I do?
Click to expand...
Click to collapse
My Note 3 suffered a few random boot loops out of the box. Then it ended up in sheer boot loop hell soon after it was rooted. At first, I too thought I had done something wrong until seeing all the posts about unchecking "Always Allow Scanning".
After the phone spent a solid 12 hours rebooting over and over, never getting past the T-Mo splash screen, it finally came back up. I unchecked "Always Allow Scanning" in the WiFi settings, and it's been fine ever since.
It would get quite hot during the boot loops, almost too hot to touch, while draining the battery very quickly. I plugged it in and set it on the fan in the top of my computer tower to keep it from frying itself.
themichael said:
Was running stock ROM rooted and everything was fine until I restarted the phone today. Started to boot loop and hasn't stopped. I've tried restoring backups, installing a ROM fresh and nothing works, just endless boot loops.
What else can I do?
Click to expand...
Click to collapse
Is your Knox flag already tripped? If so, I have a guide somewhere in here...
http://forum.xda-developers.com/showthread.php?t=2545009
I had same issue. Heimdall fixed it. Try it out, let me know. I have a lot of downloads, but no feedback. I need to know what other sorts of issues it can recover...
Recommendation though is to try the Bootloop recovery first just to get into a good recovery position, then wipe pretty much everything, and perform the stock restore.
When the stock restore hits, it runs its own little recovery script automatically fixing bootloop issues. You can root and do whatever else you want after that... Good luck.
try this it work for me
http://forum.xda-developers.com/showthread.php?p=46205598
conganhthuc said:
try this it work for me
http://forum.xda-developers.com/showthread.php?p=46205598
Click to expand...
Click to collapse
This worked! tried the second option since it was easiest and it saved my phone! Thank you so much!
Related
hello sooo i may of really screwed the pooch, I've got a rooted htc eve 4g with warm two point three rom on it. everything was just dandy until last night when i took the battery out. its now stuck in a bootloop, i can get into recovery (I'm using RA-supersonic-v2.3). i have previously done a nandroid backup and i tried wiping everything like 5 times then restoring it and it completes and then just goes back into boot loopI've also tried switching roms it just goes back into boot loop after the rom is installed. someone please help me!!
Shoot me a pm and ill send you a link with everything you need to fix it for good.
Sent from my A500 using xda premium
jrmusante said:
hello sooo i may of really screwed the pooch, I've got a rooted htc eve 4g with warm two point three rom on it. everything was just dandy until last night when i took the battery out. its now stuck in a bootloop, i can get into recovery (I'm using RA-supersonic-v2.3). i have previously done a nandroid backup and i tried wiping everything like 5 times then restoring it and it completes and then just goes back into boot loopI've also tried switching roms it just goes back into boot loop after the rom is installed. someone please help me!!
Click to expand...
Click to collapse
Have you tried flashing a different ROM yet? If you have, the most extreme thing to do left would be to completely unroot and restore to stock Sense...
Hey,
when I had that issue just wiping data cache and Davlik cache and that would allow me to reboot the phone, I ended up running an ruu and installing a custom recovery and that seemed to fix it for me, but I might have just got lucky.
Stevo
i ended up flashing Calkulins_FORMAT_ALL and that did the trick, thanks tho everyone
I'm having a weird issue with the phone not booting up, and wanted to see if anyone could offer some insight.
Got the S3 the beginning of the month, the only thing I did was use this guide to root the phone - http://forum.xda-developers.com/showthread.php?t=1739426 Have not put any custom rom on the phone, just the rooted stock. It was running smoothly till last week. Put my phone in my pocket leaving a building and got in my car pulled it out and I was faced with the dreaded "Glowing Samsung Logo." Nothing I did would get it to boot. I tried restarting (Holding Volume Up and Power,) then taking the battery out and restarting. No luck, get the ATT logo (droplets) and music, then the glowing samsung logo and nothing. I then tried taking the battery out and letting it out for the drive home. Get home, nothing still does the same thing. I then thought maybe it's the battery, so with the phone off I let it charge for an hour, tried to start it up and same deal no go.
I then did all the reading I could. I could get into Download Mode and Recovery, so I first tried wiping cache. That didn't work, glowing logo again. Then I bite the bullet, do a factory wipe and get the phone back up and running.
My first assumption through problem solving was that I did something wrong. Putting it in my pocket maybe the buttons got pressed in a weird manner. Maybe it's an app. But after setting the phone back up, it was running smoothly again - til last night. I set my phone down last night and when I come back to it I see the glowing logo again. Repeated all my steps again, no luck booting up, just a glowing logo. I figured I would take it to an ATT store to see what they can diagnose, but they are closed. So I used Odin again and tried just re-applying the rooted stock back on. No luck, bite the bullet wipe the phone and it's up and running again.
Can anyone give me any insight into what is happening. I have looked at the Sudden Death threads and it would seem that I don't have the issue. Maybe a bad assumption, but the fact that I can always get into Download Mode and Recovery leads me to think I don't have the Sudden Death issue. I'm perplexed and can't think of why this issue is happening or what the cause is. I would like to find the root cause of what is going on.
Anyone have any suggestions or things to investigate that would help me find out why it is happening?
OfficialDoughboy said:
I'm having a weird issue with the phone not booting up, and wanted to see if anyone could offer some insight.
Got the S3 the beginning of the month, the only thing I did was use this guide to root the phone - http://forum.xda-developers.com/showthread.php?t=1739426 Have not put any custom rom on the phone, just the rooted stock. It was running smoothly till last week. Put my phone in my pocket leaving a building and got in my car pulled it out and I was faced with the dreaded "Glowing Samsung Logo." Nothing I did would get it to boot. I tried restarting (Holding Volume Up and Power,) then taking the battery out and restarting. No luck, get the ATT logo (droplets) and music, then the glowing samsung logo and nothing. I then tried taking the battery out and letting it out for the drive home. Get home, nothing still does the same thing. I then thought maybe it's the battery, so with the phone off I let it charge for an hour, tried to start it up and same deal no go.
I then did all the reading I could. I could get into Download Mode and Recovery, so I first tried wiping cache. That didn't work, glowing logo again. Then I bite the bullet, do a factory wipe and get the phone back up and running.
My first assumption through problem solving was that I did something wrong. Putting it in my pocket maybe the buttons got pressed in a weird manner. Maybe it's an app. But after setting the phone back up, it was running smoothly again - til last night. I set my phone down last night and when I come back to it I see the glowing logo again. Repeated all my steps again, no luck booting up, just a glowing logo. I figured I would take it to an ATT store to see what they can diagnose, but they are closed. So I used Odin again and tried just re-applying the rooted stock back on. No luck, bite the bullet wipe the phone and it's up and running again.
Can anyone give me any insight into what is happening. I have looked at the Sudden Death threads and it would seem that I don't have the issue. Maybe a bad assumption, but the fact that I can always get into Download Mode and Recovery leads me to think I don't have the Sudden Death issue. I'm perplexed and can't think of why this issue is happening or what the cause is. I would like to find the root cause of what is going on.
Anyone have any suggestions or things to investigate that would help me find out why it is happening?
Click to expand...
Click to collapse
It's just a simple bootloop, do you have any recoveries installed? If yes then make a nandroid backup, do a factory reset, then restore data.
Ali7000 said:
It's just a simple bootloop, do you have any recoveries installed? If yes then make a nandroid backup, do a factory reset, then restore data.
Click to expand...
Click to collapse
Actually no custom recovery installed, had no intention to install a custom rom so I heeded the warning on the thread - " flashing a custom recovery will trip your counter no matter the method used." My most important data is sitting on the external SD, so I had that precaution in place.
I did start looking at the custom recoveries (CWM/TWRP,) know how they work (had CWM on my HTC Inspire) but in this case something is causing the phone to bootloop. I see the benefit of getting up and running quick, but I want to find the source of the problem.
Thanks for the response and taking time to answer.
OfficialDoughboy said:
Anyone have any suggestions or things to investigate that would help me find out why it is happening?
Click to expand...
Click to collapse
OfficialDoughboy said:
Actually no custom recovery installed, had no intention to install a custom rom so I heeded the warning on the thread - " flashing a custom recovery will trip your counter no matter the method used." My most important data is sitting on the external SD, so I had that precaution in place.
I did start looking at the custom recoveries (CWM/TWRP,) know how they work (had CWM on my HTC Inspire) but in this case something is causing the phone to bootloop. I see the benefit of getting up and running quick, but I want to find the source of the problem.
Click to expand...
Click to collapse
It could be your hardware. Of course this is not my area of expertise. You could try to install a custom recovery, wipe everything (system, data, cache, dalvik) and try reinstalling the rooted rom via ODIN. You can use Triangle Away later if needed. If you do not want to go through all of this, you can try going through warranty (just be sure you counter is not tripped and you have stock unrooted before you do).
aybarrap1 said:
It could be your hardware. Of course this is not my area of expertise. You could try to install a custom recovery, wipe everything (system, data, cache, dalvik) and try reinstalling the rooted rom via ODIN. You can use Triangle Away later if needed. If you do not want to go through all of this, you can try going through warranty (just be sure you counter is not tripped and you have stock unrooted before you do).
Click to expand...
Click to collapse
Thanks for the reply. I have all my apps now backed up with Titanium Backup just in case. I also checked for Sudden Death Syndrome with the eMMC Check app and it says I don't have an affected phone. I'm going to give it another week and see if the same thing happens again. If it does I'm going to go through warranty to get a replacement.
OfficialDoughboy said:
Thanks for the reply. I have all my apps now backed up with Titanium Backup just in case. I also checked for Sudden Death Syndrome with the eMMC Check app and it says I don't have an affected phone. I'm going to give it another week and see if the same thing happens again. If it does I'm going to go through warranty to get a replacement.
Click to expand...
Click to collapse
Honestly I suggest going into stock recovery and doing a factory reset and wiping cache. When you flash back stock with Odin you usually have to do a factory reset anyway because it will bootloop.
About tripping the flash counter is almost a non issue as all you have to do is use triangle away and Odin flash back to stock and its gone.
hednik said:
Honestly I suggest going into stock recovery and doing a factory reset and wiping cache. When you flash back stock with Odin you usually have to do a factory reset anyway because it will bootloop.
About tripping the flash counter is almost a non issue as all you have to do is use triangle away and Odin flash back to stock and its gone.
Click to expand...
Click to collapse
I actually did that, sorry I wasn't clear in my original post. This last time, I wiped the cache and rebooted the phone, that didn't work. Then I tried Odin to see if I could save internal data, re-flashed and again couldn't boot. Last thing I did was do a factory reset through stock recovery and got the phone to boot.
For some reason my phone isn't booting up all the way to the rom/OS. It gets stuck on the boot animation and goes on forever and hasn't been able to boot up since yesterday, when my powered off at 20% battery, which is something normal for my phone. I was rooted and on android 4.3/MK4, but when I put it to charge and tried booting it back up, the phone would boot up, but would get stuck on the boot animation, going on forever. It wouldn't freeze it would just continue to play the animation. I tried removing the battery, factory wiping it, and installing a new rom, which I found out was for a different baseband. When i finished installing it it still wouldn't boot up all the way through.:crying: I then tried installing the previous rom, and still no good. After all that I installed a stock firmware using odin, hoping it would work. I installed the 4.4.2 NE2 firmware, which isn't for my phone but watching zedomax's video, he said to download the latest build date, which is what I did. Well, downloaded it and flashed it through Odin with a PASS and everything going good. Although, when it was rebooting-even after a factory and cache wipe-it still wouldn't boot up. I tried installing other firmwares aswell, but still no luck. I'm just waiting for it to finally boot up, so if anyone can help me out, I WOULD GREATLY APPRECIATE IT, otherwise, anything is going to help at this point. Since I flashed the firmware, I now have a stock recovery and rom(I hope). I've been through these types of situations, but not to this point.. :crying:
It seems odds, but you may want to try a new battery. I recently went through a total disaster with my device and it ultimately was the battery. You may want to try booting with it connected to the a/c wall charger. It may give you an indication.
Have you tried the quick fix posted? My phone did the same thing when i had the stock recovery it showed error mounting efs folder. I noticed after installing clockwork that error didnt show up. It was still the same problem though. Wouldnt hurt to check it out. I got my note two from a friend who described the issue starting the same way you said happend to yours. The phone had never been rooted though. Good luck to you in trying to fix it.
Sent from my SM-T217S using XDA Free mobile app
Hi.
I have a problem with my D855. My phone is rooted and runs the fulmics ROM. Everything was working fine, , on Fulmics 5.3, except than one day, I was using my phone normally and then it crashed. I saw the phone rebooting, but for some reason it got stuck. The phone tried to boot unsuccessfully until the "firmware update" went through, after what it reboots again (unsuccessfully) and so on.
At that time, I was able to access twrp, do some backup, and flash properly with a downgraded version of fulmics (from 5.3 to 4.1).
It was able to boot again and use my phone like before. Yet, after one month of usage, the same problem happened on version 4.1. The phone crashed and now cannot boot.
Any idea of where it is coming from? Should I go back to stock? Should I contact customer service?
What did you do before the phone crashes ?
I think you probably should flash the stock ROM and wait for an other crash... or not.
Jb-kun said:
What did you do before the phone crashes ?
I think you probably should flash the stock ROM and wait for an other crash... or not.
Click to expand...
Click to collapse
I haven't done anything special. I think that the first time I was playing on candy crush. The second time I was just looking at pictures in my gallery.
I was using the ROM without any tweaks or extra modules such as Xposed. Just regular use.
Update on my situation: I switched back to stock ROM and it seems to work OK for now (it has been 4 days). So I will wait and see if new problems happen. By the way, it was extremely difficult for me to get back to Stock directly from fulmics ROM. I tried several methods that I have found on xda based on LGUP or LG Flash tool without success. For some reason I was not able to connect the phone to my PC in download mode.
The only way that I found was to use a nandroid backup that I did just after rooting the phone and that was based on stock ROM.
shewshain said:
I haven't done anything special. I think that the first time I was playing on candy crush. The second time I was just looking at pictures in my gallery.
I was using the ROM without any tweaks or extra modules such as Xposed. Just regular use.
Update on my situation: I switched back to stock ROM and it seems to work OK for now (it has been 4 days). So I will wait and see if new problems happen. By the way, it was extremely difficult for me to get back to Stock directly from fulmics ROM. I tried several methods that I have found on xda based on LGUP or LG Flash tool without success. For some reason I was not able to connect the phone to my PC in download mode.
The only way that I found was to use a nandroid backup that I did just after rooting the phone and that was based on stock ROM.
Click to expand...
Click to collapse
You can also use the Stock rom flashable from twrp. So you can wipe the system partition and get a "better situation" than a nandroid backup that should be with an old version.
Or use this that has also root and other improvements.
shewshain said:
Hi.
I have a problem with my D855. My phone is rooted and runs the fulmics ROM. Everything was working fine, , on Fulmics 5.3, except than one day, I was using my phone normally and then it crashed. I saw the phone rebooting, but for some reason it got stuck. The phone tried to boot unsuccessfully until the "firmware update" went through, after what it reboots again (unsuccessfully) and so on.
At that time, I was able to access twrp, do some backup, and flash properly with a downgraded version of fulmics (from 5.3 to 4.1).
It was able to boot again and use my phone like before. Yet, after one month of usage, the same problem happened on version 4.1. The phone crashed and now cannot boot.
Any idea of where it is coming from? Should I go back to stock? Should I contact customer service?
Click to expand...
Click to collapse
Same problem here. Normal usage suddenly started to reboot and now it's stuck in boot loop
Coming from Fulmics too - stopped working one fine day.
Now, continues to boot-loop at the initial LG screen. Trying to get into the recovery shows me the the 'Factory Reset' screen, but beyond that leads to boot-loops again. Even the Download mode loops!
I'm at my wits end without a solution in sight.
Blysterk said:
You can also use the Stock rom flashable from twrp. So you can wipe the system partition and get a "better situation" than a nandroid backup that should be with an old version.
Or use this that has also root and other improvements.
Click to expand...
Click to collapse
Thank you for this advice. I was able to update my stock ROM after the Nandroid backup through LGUP, but your method would have been faster.
But anyway, I am waiting to see if I am stuck with bootloops again, using non-root stock version, so I can send it to customer service if this happen again.
AhmadAlmousa said:
Same problem here. Normal usage suddenly started to reboot and now it's stuck in boot loop
Click to expand...
Click to collapse
abourdeau said:
I have the exact same problem, I even bought a second battery with no success.
Click to expand...
Click to collapse
Are you using Fulmics ROM as well? Can you have access to TWRP? I was able to connect to a PC in the recovery mode and to transfer files before flashing, in case you need some basic backup...
prakhargr8 said:
Coming from Fulmics too - stopped working one fine day.
Now, continues to boot-loop at the initial LG screen. Trying to get into the recovery shows me the the 'Factory Reset' screen, but beyond that leads to boot-loops again. Even the Download mode loops!
I'm at my wits end without a solution in sight.
Click to expand...
Click to collapse
Silly question, but are you sure that you selected "Yes" when the screen asks you about factory reset? you have to press "volume down" and the "power button", since the default answer is no.
shewshain said:
Silly question, but are you sure that you selected "Yes" when the screen asks you about factory reset? you have to press "volume down" and the "power button", since the default answer is no.
Click to expand...
Click to collapse
Yes, of course I was able to access TWRP successfully earlier.
Curiously enough, the phone boot-loops in regular startup, Download mode and trying to get to recovery. However, it doesn't restart itself and fall into a loop, while on the Factory Reset menu. Am I correct in assuming that the battery could not be the root cause of the overall problem? Because if it was, it would likely loop even on this Factory Reset menu as well as far as I understand.
Unfortunately, the phone restarts as soon as it lands in the Download mode so I cannot even restore to stock.
EDIT: Okay, weirdly enough it just booted and reached the homescreen before restarting again. What I did was let it charge to a 100% and tried booting while plugged in. Could it be the battery after all? Though this exact set of steps hasn't been helpful before.
I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks
So I tried sideloading. I was able to get into the stock recovery. I tried wiping cache and data, then tried installing the newest stock rom.
Everything seemed to work. Then I had to restart. A message popped up after the same "Your device software can't be checked for corruptions. Please lock the bootloader". It had the title in blue stating "Encryption unsuccessful".
Then said, "Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible. To resume using your phone you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account."
Then there is a single button that says, "Reset Phone".
Problem still persists.
Help please...
Why did you bought a bootlooped phone?
Sin Stalker said:
I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks
Click to expand...
Click to collapse
When my Nexus 5x got into bootloop, I sent it to LG and they had to change the whole circuit. So yeah.
When you flash Google Factory Image, it flash the stock kernel.
If you have warranty, then send it to Google/LG. If you haven't got, then you're in problem. New motherboard needed, but it's expensive.
See the following thread for more info.
https://forum.xda-developers.com/nexus-5x/help/5x-bootloop-cause-fix-t3476794/
khalifakk said:
Why did you bought a bootlooped phone?
Click to expand...
Click to collapse
Cause its cheaper.
Sin Stalker said:
Cause its cheaper.
Click to expand...
Click to collapse
Then face the consequences...
khalifakk said:
Then face the consequences...
Click to expand...
Click to collapse
What consequences?
Hardware bootloop can't be fix by software.
Duckscreen said:
Hardware bootloop can't be fix by software.
Click to expand...
Click to collapse
Exactly. Everyone has either been able to get a replacement under warranty or was pretty much screwed if it was out of warranty.
Sent from my Nexus 5X using Tapatalk
Sin Stalker said:
What consequences?
Click to expand...
Click to collapse
A bootlooped phone for ever....
I recommend you will install kernel adiutor app after try rooting
I recommend you will install kernel adiutor app after try rooting
Almost I got no bootloop even no random reboot nexus 5x's state