Basically as the title says whenever I want to restart my phone I get stuck in this inexplicable boot loop that doesn't stop and I can only actually get into the phone in some weird magical way that I haven't figured out how is done yet.
I've tried flashing stock(I was on btu 7.0), wiping cache partition/factory resetting but the issue still remains. Anyone encountered anything similar?
If flashing rom and factory reset doesn't fix it then it might be hardware issue and need mainboard replacement.
Sent from my SM-G935F using Tapatalk
This is where most of the people make problem even worst, please don't mess with the software anymore and take it to service,it must be hardware related.
Related
So recently (like 2 hours ago), my phone started acting like it wasn't on the cricket network anymore. I've rebooted. Taken things out and reinserted them. Nothing works. So I figured I would just hard reset my phone. So I get through the process of getting it to the recovery booting screen only to find out that something WON'T LET ME FACTORY RESET MY PHONE!!! I am frustrated beyond belief and I just want to be able to use my phone. Can anyone please please help me? I am afraid I have a virus or someone is trying to hack my device/already has
littllejimmy said:
So recently (like 2 hours ago), my phone started acting like it wasn't on the cricket network anymore. I've rebooted. Taken things out and reinserted them. Nothing works. So I figured I would just hard reset my phone. So I get through the process of getting it to the recovery booting screen only to find out that something WON'T LET ME FACTORY RESET MY PHONE!!! I am frustrated beyond belief and I just want to be able to use my phone. Can anyone please please help me? I am afraid I have a virus or someone is trying to hack my device/already has
Click to expand...
Click to collapse
What do you mean it wont let you factory reset, what happens when you try it?
Sent from my Galaxy S5 using XDA Labs
Sounds like recovery might be corrupted if it doesn't let you into recovery
Or does it enter recovery? Need a bit more detail about what's actually happening, instead of "Something won't let it reset"
Flash a stock ROM back over the top to repair recovery/system etc and try resetting again
My XT1575 just decided to go into a bootloop a week ago on its own, literally. I was just checking traffic on Google maps when I noticed it started to lock up. Finally, I see the Motorola splash screen, and that was the beginning of it. Went into recovery mode and tried a factory reset, clear cache partition, etc. but no luck. I've tried everything under Android 6.0 here but it continues to bootloop no matter what I do.
It's not rooted and the bootloader is locked, so I don't think I can even install TWRP or any custom recovery. I have never even though of enabling USB debugging so that's out of the question. What's odd is after trying all sorts of things, sometimes, after the phone has been off for a while I would power it on and it would actually boot into the Welcome screen. Shortly after that though, it locks up and starts bootlooping again. I don't know what else I can do about this or if it's recoverable. I hope someone can help. If it's of any significance, when in recovery mode, at the top I see what I think is the firmware it's currently on -- motorola/clark_retus/clark 6.0/MPHS24.49-18-4/5. Please help!
Update - After having my XT1575 powered off overnight, I powered it on this morning and it was able boot all the way into the Welcome screen, setup, etc. Right away I went and turned on USB Debugging and Allow OEM unlock. Tried rebooting and again it fails to boot. What's weird is it randomly seems to boot when it wants, and something must be corrupt but I just don't know what it could be. Does anyone have any ideas?
Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.
jason2678 said:
Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.
Click to expand...
Click to collapse
Yes undo what you just did an follow this guy
jason2678 said:
Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.
Click to expand...
Click to collapse
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?
iflyimpilot said:
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?
Click to expand...
Click to collapse
The random nature of what you're describing does sound like hardware. Consider a full restore where you fastboot flash everything back to stock of you haven't already.
Check logs. See if you're getting anything in last_kmsg. Use an app like syslog if you aren't used to pulling them, though you might have to use adb if you aren't getting through boot all the time.
jason2678 said:
The random nature of what you're describing does sound like hardware. Consider a full restore where you fastboot flash everything back to stock of you haven't already.
Check logs. See if you're getting anything in last_kmsg. Use an app like syslog if you aren't used to pulling them, though you might have to use adb if you aren't getting through boot all the time.
Click to expand...
Click to collapse
Thanks for replying. I've tried fastboot flashing everything and even going into recovery and clearing cache partition as well as doing a factory data reset. I'm afraid it may very well be hardware. I'll try your suggestion about the logs.
Is 'last_kmsg' a line I should be looking for in the log? If so, what would I need to see in order to determine whether or not it's a hardware problem?
iflyimpilot said:
Thanks for replying. I've tried fastboot flashing everything and even going into recovery and clearing cache partition as well as doing a factory data reset. I'm afraid it may very well be hardware. I'll try your suggestion about the logs.
Is 'last_kmsg' a line I should be looking for in the log? If so, what would I need to see in order to determine whether or not it's a hardware problem?
Click to expand...
Click to collapse
/proc/last_kmsg is a log file that should get written to if a kernel panic causes a reboot in theory. In practice I find it is often blank even after a random reboot.
iflyimpilot said:
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?
Click to expand...
Click to collapse
going by that logic the thing that you should have done was get a factory image from moto and flash to stock using moto tools if that failed at fixing it then send into moto it might not be lost yet but the more you progress the more less likely to replace the phone moto is...
it sounds like something is going bad could be ram emmc or the soc
What i would do is get into discussions with lenovo to see if they can get you fixed up. if you unlocked the bl they know be straight with them. if you get nowhere and no rom you load can fix it sell as parts replace at your expense...
Classic "my phone keeps freezing and rebooting". I am quite in the know about flashing roms and such.
It started on the stock firmware 6.1.1 (i think it was). I dd factory resets, cache wipes the lot. It would still randomly reboot.
So i flashed Telstra version of 7.0. Still froze every now and then. Did the same things as above.
Flashed TWRP and wiped everything, flashed Renovate Rom and the bootloader for it, Still did it. Numerus factory resets and wipes of everything. It would freeze at any point from startup, to having setup the phone and making phone calls or on facebook or whatever. It would even freeze in twrp, or loading twrp.
I found that the data partition was corrupt so i re partitioned to ext4. Still nothing. I reformatted every partition so the phone was a complete brick with nothing on it and after flashing clean again it would still do it.
Whats the issue that I'm missing, or is there a way to log so i can find where it keeps getting stuck? It gets hot and blue light flashes and i have to hard reset it or sometimes i have to let the battery drain so i can turn it back on again.
pls help?
Hmm i will give you an advice so you dont have to wait for your battery to drain...just press volume down and power button for like 5 secs and phone will force boot. Anyway back to your problem...did you tried flashing latest stock samsung firmware?
raz_il_dio said:
Hmm i will give you an advice so you dont have to wait for your battery to drain...just press volume down and power button for like 5 secs and phone will force boot. Anyway back to your problem...did you tried flashing latest stock samsung firmware?
Click to expand...
Click to collapse
This advice doesn't work with my phone even with holding the buttons for 30 secs and more. For rebooting I can only wait until the battery is completely drained. With little hope for another way shortening time to the next reboot any help is appreciated.
Same here...experiencing the same prob...
Same problem.
Sent from my Redmi Note 4 using Tapatalk
smallcapsicum said:
Classic "my phone keeps freezing and rebooting". I am quite in the know about flashing roms and such.
It started on the stock firmware 6.1.1 (i think it was). I dd factory resets, cache wipes the lot. It would still randomly reboot.
So i flashed Telstra version of 7.0. Still froze every now and then. Did the same things as above.
Flashed TWRP and wiped everything, flashed Renovate Rom and the bootloader for it, Still did it. Numerus factory resets and wipes of everything. It would freeze at any point from startup, to having setup the phone and making phone calls or on facebook or whatever. It would even freeze in twrp, or loading twrp.
I found that the data partition was corrupt so i re partitioned to ext4. Still nothing. I reformatted every partition so the phone was a complete brick with nothing on it and after flashing clean again it would still do it.
Whats the issue that I'm missing, or is there a way to log so i can find where it keeps getting stuck? It gets hot and blue light flashes and i have to hard reset it or sometimes i have to let the battery drain so i can turn it back on again.
pls help?
Click to expand...
Click to collapse
Sounds like you need your motherboard replaced i had the same issues on marshmallow thought the nougat update would fix it but realized it was a hardware fault not software..left it in store to get fixed and on repair sheet it said faulty motherboard..
Sent from my SM-G935F using XDA-Developers Legacy app
As i know some S7 have motherboard hardware problem, mine has too, what help? warranty and they replaced motherboard. But if you root, you can say good bye to warranty, they look at knox first with this problem.
please help
my nexus is stuck trying to boot up itself but it stuck on the google screen. I have done a factory reset and cleared everything, but it is still stuck. I did some research and it might be an OS issue but how do I fix the os? or is it something else that is causing the problem and if so, how do I fix that?
Meme-Man said:
please help
my nexus is stuck trying to boot up itself but it stuck on the google screen. I have done a factory reset and cleared everything, but it is still stuck. I did some research and it might be an OS issue but how do I fix the os? or is it something else that is causing the problem and if so, how do I fix that?
Click to expand...
Click to collapse
Sounds like the CPU hardware issue. If your bootloader is unlocked you can fix. Search for 6p bootloop fix
Sent from my Nexus 6P using Tapatalk
Meme-Man said:
please help. my nexus is stuck trying to boot up itself but it stuck on the google screen. I have done a factory reset and cleared everything, but it is still stuck. I did some research and it might be an OS issue but how do I fix the os? or is it something else that is causing the problem and if so, how do I fix that?
Click to expand...
Click to collapse
There are SO many other threads on this exact same issue that you could read and learn from. Basically if your bootloader is locked there is nothing you can do, except repeatedly try to get it to boot so you CAN unlock it and apply the bootloop workaround. Please do some reading, and try some of the methods first.
Ever since I updated my phone to stable android 10 it started to restart itself every couple of days and gets stuck on boot animation, tried hard reseting it, tried adb but the only thing that works is disconnecting the battery and connecting it back again and it boots just fine (broke my glass back while trying to open it ).
I assume that the android 10 update causes it and Im waiting for another ota that will maybe fix it (dont want to factory reset the phone cause I dont know if it will help and I dont want to backup stuff cause Im lazy).
Has anyone experienced it or have an idea on how to solve it?
You'll have to try factory reset and manually reinstall your apps.
omerbagi10 said:
Ever since I updated my phone to stable android 10 it started to restart itself every couple of days and gets stuck on boot animation, tried hard reseting it, tried adb but the only thing that works is disconnecting the battery and connecting it back again and it boots just fine (broke my glass back while trying to open it ).
I assume that the android 10 update causes it and Im waiting for another ota that will maybe fix it (dont want to factory reset the phone cause I dont know if it will help and I dont want to backup stuff cause Im lazy).
Has anyone experienced it or have an idea on how to solve it?
Click to expand...
Click to collapse
Removing the battery was a waste of time
Any phone with a non removable battery can easily be reset with a simple button combo. Just hold power + volume up and the phone will restart same as a battery pull.
As for you phone rebooting on its own you'll likely have to do the full wipe and re install to fix it.
Sent from my ONEPLUS A6010 using Tapatalk
omerbagi10 said:
Ever since I updated my phone to stable android 10 it started to restart itself every couple of days and gets stuck on boot animation, tried hard reseting it, tried adb but the only thing that works is disconnecting the battery and connecting it back again and it boots just fine (broke my glass back while trying to open it ).
I assume that the android 10 update causes it and Im waiting for another ota that will maybe fix it (dont want to factory reset the phone cause I dont know if it will help and I dont want to backup stuff cause Im lazy).
Has anyone experienced it or have an idea on how to solve it?
Click to expand...
Click to collapse
This problem is reported by many users. I had it as well (TMobile converted phone). Volume+ and power will reboot the phone. This problem happened to me 2-3 times in 3 days so I went back to pie. And I did a full reset when I upgraded the phone. It is not that. I have 2 Sims (TMobile + Verizon).
Sent from my [device_name] using XDA-Developers Legacy app