So heres the background, I flashed a new rom and while in the procedure of it getting passed the boot animation and it was downloading my apps from the play store, it rebooted and did that over again and again, without getting passed the boot animation. So logically, I factory reset the phone and try again for another 3 times, no dice. The same thing happened again, It would boot up, then at the boot animation, it reboots itself. I can get to my CWM Recovery just fine and interact with it just fine. So lastly, I flashed my backup of CM 10.1, but it happened again. I really don't know what to do, so please give me advice and answers to my predicament.
http://forum.xda-developers.com/showthread.php?t=1626895
a manta wrote this.
Just out of curiosity, why would returning to stock help me in this situation? I'm not saying that it won't help, but why would it? Can you explain?
Sent from my Nexus One using xda app-developers app
Stock is usually going to be the most stable software. If stock doesn't work, that probably rules out software problems, so your hardware is the likely problem.
Related
Ok, so I flashed a MIUI port for the AT&T Note 2, and it was disgusting...it crashed everything, and needless to say I ended up stuck at the boot logo for a long time. FINALLY managed to get it to flash via Odin...so I flashed Stock Rom...and now it's stuck on Samsung logo...Ok..so I go flash CWM...do a wipe and everything, and install CM10.1 via that...stuck at CM logo. I've left each ROM plugged in, stuck on boot screen for over 20-30 minutes each. I'm at a loss of what to do. Could I need to flash a kernel? or am I missing something obvious? The good news, I guess, is with a few steps, I can get into DL mode and use Odin, and I can flash CWM and get into that..but I can't inject anything into my phone so CWM can use it, I only have what's there now, which is CM10.1. I'm so mad...I've never had too many issues with ROMs but this one jacked things up badly...guess that's what I get for using a port even though it noted that everything was working now. Anyway...does anyone have any advice?
Edit: I flashed CWM, and tried to clear cache/dalvik then factory reset...the first two worked...as soon as I hit factory reset, that's where the screen goes black and it resets...it's like it just refuses to do it. I'm seriously at a loss here. Is it toast?
Edit again: sorry but I'm trying more to give more info. I went into CWM and went to advanced and started formatting one by one...it's when you hit format /data that it immediately dies and restarts. So..something weird is going on there. Can I use a PIT file for this phone, if it exists, to reformat and just get it going? I'm desperate...
Us this http://forum.xda-developers.com/showthread.php?t=2052779 on a PC.
Follow directions and Odin back to stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
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!
So, at the risk of posting too much info (instead of not enough) I'm going to start at the beginning:
I rooted my wife's S3 and loaded TWRP and Paranoid Android. It ran fine, but there was a camera issue, so she wanted me to restore it to the stock ROM. I did this (to 4.1, I believe, whatever was out in August). Again, it ran fine and I was planning to restore the root access, but did not.
Later, it was dropped in Hibachi sauce (not sure this is relevant, but in case) and we put it immediately in rice. It worked fine, other than the touch screen intermittently ceasing to receive touch commands.
When the updated ROM came from Samsung, my wife installed the update and the phone continued to work fine, other than the screen issue.
She was tired of the issue and decided to sell it to buy an iPhone (shudder) so she did a factory reset. This is where the issues began (I included the previous steps as I'm not sure which may have caused the current issue).
Upon the factory reset, the phone would only boot to the beginning of the AT&T logo loading. I thought it may be something she could fix through Kies and suggested she try that, so she did. The phone would then boot to a screen in Odin mode that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." We did this and there was no help.
I can get it to boot into recovery (the default one now) and have tried to reflash that and the stock ROM that I did previously and only can get two actions: either the freeze at the AT&T logo (if I use Odin to flash the ROM) or the above message in Odin mode (after trying to fix from Kies).
I'm not sure what to do at this point and would appreciate any and all help you guys can provide. I've lurked around and learned quite a bit to flash my ROM and my wife's from you guys, so I'm really hoping I can learn more from this.
Thanks in advance!
Fearborn said:
So, at the risk of posting too much info (instead of not enough) I'm going to start at the beginning:
I rooted my wife's S3 and loaded TWRP and Paranoid Android. It ran fine, but there was a camera issue, so she wanted me to restore it to the stock ROM. I did this (to 4.1, I believe, whatever was out in August). Again, it ran fine and I was planning to restore the root access, but did not.
Later, it was dropped in Hibachi sauce (not sure this is relevant, but in case) and we put it immediately in rice. It worked fine, other than the touch screen intermittently ceasing to receive touch commands.
When the updated ROM came from Samsung, my wife installed the update and the phone continued to work fine, other than the screen issue.
She was tired of the issue and decided to sell it to buy an iPhone (shudder) so she did a factory reset. This is where the issues began (I included the previous steps as I'm not sure which may have caused the current issue).
Upon the factory reset, the phone would only boot to the beginning of the AT&T logo loading. I thought it may be something she could fix through Kies and suggested she try that, so she did. The phone would then boot to a screen in Odin mode that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." We did this and there was no help.
I can get it to boot into recovery (the default one now) and have tried to reflash that and the stock ROM that I did previously and only can get two actions: either the freeze at the AT&T logo (if I use Odin to flash the ROM) or the above message in Odin mode (after trying to fix from Kies).
I'm not sure what to do at this point and would appreciate any and all help you guys can provide. I've lurked around and learned quite a bit to flash my ROM and my wife's from you guys, so I'm really hoping I can learn more from this.
Thanks in advance!
Click to expand...
Click to collapse
So is it stuck on the AT&T Logo? Or Samsung Logo?
UnknownTroll1 said:
So is it stuck on the AT&T Logo? Or Samsung Logo?
Click to expand...
Click to collapse
It was the AT&T logo, it's currently the Odin. If I flash it again with the stock ROM, it'll be the AT&T logo again, but it doesn't completely load the AT&T logo. The Samsung one loads and then the AT&T starts to load, but doesn't finish playing.
Anyone?
Yes, Odin to stock unrooted, then go ahead and factory reset by holding volume up + home button on first boot. Done.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
jblparisi said:
Yes, Odin to stock unrooted, then go ahead and factory reset by holding volume up + home button on first boot. Done.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
If this works (I'll try it when I get home) I will be so grateful! BTW, do you happen to have a decent link to a stock ROM? If not, I'll Google it tonight.
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
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