Random reboot after 2-3 minutes of use - Verizon Samsung Galaxy Note5

Under a variety of circumstances (charging, safe mode, plugged into computer, etc.) I have tried to use my phone but whenever it is turned on to any degree, it consistently restarts itself after a couple minutes.
At this point, I don't even care if I need to buy another phone; if I can fix this? Awesome! If not, I really just want to save my data.
It is not in a boot loop - it functions fully with no error until it restarts.
EDIT: I found some suggestions about wiping the cache partition (I believe that's the wording) but that didn't help at all.
EDIT2: Development; the phone stays on as long as I constantly touch the screen

Related

Fighting a lost cause?

I've got a rooted (Super SU, but the original root manager was Superuser) LG C800 that I was having problems with. To be specific, I installed some apps on to the system. Some of these apps would be Titanium Backup for root, Avast Mobile Security, ROM Tool Box Lite, Super SU, and a quite a few others. From day one they seem to be kicked right back to my S.D. card, but not all at the same time, and some would stay on the system. I read where I should move the apps back to my S.D. card and try to re-install them on the system minus the data. When I did, the phone went nuts. Now it stays in a restart mode but never fully boots up. Can I salvage it, and if so, please tell me how?! I have tried the hard reset/recovery boot where you hold down the power button, volume, and a few other keys, but it did not work. I'm a broke college student and can't really afford to buy a new phone. I used this one for everything including tethering it to get my assignments done at home and turned in on time. Please help! I'm open to suggestions....... My phone will be completely off. When I plug it into my computer, via U.S.B., it automatically turns it on whether I want it to be on or not. Then it starts off in "reboot recovery" mode, will boot all the way to the point to where the home screen would normally turn on, but then it starts in that "boot loop" all over again but never fully boots up before going back to the beginning of that "boot loop" yet again. I can't even get it to register on my laptop as being plugged in. The reason I took the apps I placed on the system off was because sometimes when I'd re-boot the system the apps would be on the system and sometimes back on my S.D. card without my involvement of any kind other than rebooting my phone. Is completing a Nandroid recovery or re-installation of my ROM even possible with my computer no longer recognizing it as even being plugged in? From what I can tell it won't be. Am I fighting a lost cause or is it salvageable?
Rooted myTouch Q 4G, a.k.a. LG C800
I believe it has a 2.3.4 GRJ22-perf, and then something like 2.6.35.7? I can't remember off the top of my head, and I can't pull it up on my phone anymore or else I'd double check.
Have you tried booting into recovery?
(More about my phone from the original post) Honestly.........I'm not what you may consider technologically inclined. I have however done about as much research online concerning this matter as any one person can do. I've looked it up on all major sites, and many smaller ones too, that post remedies for phone, or "human" if you'd rather, malfunctions. They all talk about still being able to reach a home screen or doing the whole holding the power and volume decrease buttons until I "reboot recovery" screen appears (if that's what you're referring to as doing a recovery reboot as). Don't forget the one where you hold hold the power and volume decrease buttons along with the "A" and "F" keys as well. I even tried one from here where you're supposed to push the genius button after the Android figure leaves the screen. My phone won't allow me to do either. Basically if it's online, I myself, or this girl that's been staying with me, have tried it without any results. On the initial boot the Android figure and the box with the arrow coming out of it show up and it boots until just about the point that it use to switch over to the home screen and it will start the whole "boot loop" over again. The thing is though that the Android figure and box aren't there any other time after the first boot, and with every boot loop it makes after that, the time is reduced from the beginning of the loop to the end when it starts all over again. The phone won't shut off unless I remove the battery and even though my laptop no longer recognizes the device, when I plug my phone into it or another power source and it's off, it automatically turns itself on and begins that boot loop all over again. there is one thing I have yet to try. I read on one site where I could download a custom ROM on my S.D. and then try reboot it, but it never makes it to the point in which the files on my S.D. card are ran, much less scanned. I am still 100% open to any and all suggestions in the diagnosis of this issue. I may record and place a video on one of the more popular "tube" sites to better show or further explain what's happening and then come back on here to post the link?! Feel free to reply back if it's possible you can help before I'm able to complete that later this evening. And thanks for any and all help in advance to everyone.

S6 keeps Rebooting

Hello all,
Today my Verizon S6 (on CleanRom 1.5) started to keep rebooting. After it boots, I can use the phone for less than a minute until it reboots again.
Here's how it began to happen today, if it helps.
- I didn't plug my phone to a charger last night, and when I woke up the phone had like 0%~1% battery. The phone died soon after I picked up the phone.
- At the same time I turned on the phone, I connected it to the stock charger.
- I used it for like 1-2 minutes, and the phone seemed to get confused whether it should die again or not (at 0% battery level)
- Then the phone decided to die again, and keeps rebooting itself.
My guess is something related to booting, initializing, or battery might have gone wrong. Also the soft button lights get never turn on.
Now I cannot use the phone really, as it dies like 30 seconds after I swipe the lockscreen.
- I tried to boot into safe mode, it didn't help.
- I wiped cache partition, it didn't help either.
The last thing I would like to try is to odin CleanRom again (or factory reset) but I would like to try other things first because I cannot even backup the data as it keeps rebooting. Odin will wipe all the data in my phone.
Any help or suggestions guys?
mtshure said:
Hello all,
Today my Verizon S6 (on CleanRom 1.5) started to keep rebooting. After it boots, I can use the phone for less than a minute until it reboots again.
Here's how it began to happen today, if it helps.
- I didn't plug my phone to a charger last night, and when I woke up the phone had like 0%~1% battery. The phone died soon after I picked up the phone.
- At the same time I turned on the phone, I connected it to the stock charger.
- I used it for like 1-2 minutes, and the phone seemed to get confused whether it should die again or not (at 0% battery level)
- Then the phone decided to die again, and keeps rebooting itself.
My guess is something related to booting, initializing, or battery might have gone wrong. Also the soft button lights get never turn on.
Now I cannot use the phone really, as it dies like 30 seconds after I swipe the lockscreen.
- I tried to boot into safe mode, it didn't help.
- I wiped cache partition, it didn't help either.
The last thing I would like to try is to odin CleanRom again (or factory reset) but I would like to try other things first because I cannot even backup the data as it keeps rebooting. Odin will wipe all the data in my phone.
Any help or suggestions guys?
Click to expand...
Click to collapse
The OE2 tar file shouldn't wipe your phone as it is not a full wipe tar. I don't know if your phone would do it with it's reboot problem but a dirty flash of clean rom shouldn't wipe your phone either. However, a reboot during the middle of either of those would not be good. Flashfire does seem to be able to keep a phone from rebooting once it gets going or at least it has for me when I have been caught in a bad way before.
Problem Solved!!!
Thank you Tulsadiver for your suggestions. But is it okay to do odin without wiping anything?
I almost gave up after struggling several hours and thought about doing a factory reset, but the problem is solved now.
I found it weird that the soft key lights never turn on, so I thought that there might have been something wrong with the power management. So I turned the ultra power saving mode on (fortunately the phone didn't reboot before I did that), and it didn't reboot itself. I turned it back off then now the problem is gone!
I am happy with it now, and this might be one of the things to try if you experience a random reboot.

Nexus 5: My phone starts to freeze or restart when not charging

I noticed a strange problem with my Nexus 5. It starts to hang or restarts on its own. Sometimes go in to continuous boot loop. I could not differentiate why it would do that. Sometimes it worked flawlessly for hours. Then I realized that when it's charged off my computer USB power it works smooth. It works fine for sometime. But after few minutes of idle time or quick usage session freezes the phone and it re starts and keep going to boot loop, even after wiping cache. After a few attempt to wipe sometimes it starts without external power help. However, when attached to USB power it just starts without any issue.
I have done factory reset a few times. Unlocked my phone and also installed TWRP with Pure Nexus. The behavior hasn't changed much.
I think this is hardware issue. Could be a battery.
Can anyone provide a detail on how I can find issue?
super19 said:
I noticed a strange problem with my Nexus 5. It starts to hang or restarts on its own. Sometimes go in to continuous boot loop. I could not differentiate why it would do that. Sometimes it worked flawlessly for hours. Then I realized that when it's charged off my computer USB power it works smooth. It works fine for sometime. But after few minutes of idle time or quick usage session freezes the phone and it re starts and keep going to boot loop, even after wiping cache. After a few attempt to wipe sometimes it starts without external power help. However, when attached to USB power it just starts without any issue.
I have done factory reset a few times. Unlocked my phone and also installed TWRP with Pure Nexus. The behavior hasn't changed much.
I think this is hardware issue. Could be a battery.
Can anyone provide a detail on how I can find issue?
Click to expand...
Click to collapse
Sounds like the battery is failing.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

HELP! HTC U11+ Just won't turn on!

I've been using HTC U11 Plus as my main phone since the day it came out. I absolutely love this phone. In my opinion it's the best phone I've ever had. I never felt the need to get a new phone. I've been gaming, working, etc. and I never had any issue with it.
Two days ago all of a sudden while using my phone it got stuck. None of the button were working and the screen also had response so I pressed and hold the Power button and Volume Down button to boot into recovery mode. So i could clear cache and reboot again but my phone doesn't seem to reboot. It just turns off when I select reboot now. I even tried "Wipe data/factory reset from the Recovery menu options" and then delete all user data option and then Reboot system now to restart your phone. Still no luck. As soon as I press on reboot system my phone just turns off and doesn't reboot or turn on at all.
Even when I put my phone on charging there is not light to indicate that my phone is charging at all.
PLEASE HELP!!!!
Same problem here... Screen flashed white, phone rebooted to encryption screen to enter pin, then powered off... Hasn't been back on since (thins happened in October 2021).
I'm interested in a possible way to get the data off the phone, even if some parts swapping is involved.
PS. I changed the battery thinking it was that, but the phone still isn't coming on or showing the red battery charging light.
I guess it is time for you both to use ADB. When installed properly you should be able to see your phone in device manager on Windows systems. That in itself would be a good starting point. Or just fire up ADB and check if ADB detects your phone. If you are unfamiliar with ADB, Google it.
In ADB use: *.\adb devices* (without the *) If it works properly you should get a return with a device number. You could then flash a boot image or system image or both and see if your phone start's up again.
Hello,
same Issue here.
Solution is to heat up the Phone above 50°C and hold the temperature while it run and copy Data.
I have spend 40h+ to Backup Data and heat up the Phone.
Seems for me to the same problem like the RROD at Xbox360.
Lead-Free solder at the BGA-Chips.

Unknown bootlooping problem on Redmi Note 10

Hello, so about 2 days ago from now, my device, while waiting for the bus started to bootloop for no known reason. Skipping into this weekend, I have tried almost everything to get it working without the risk of any data loss, unsuccessful I am here.
Right, so the main problem of the device is that it's very unpredictable, that being said, the device doesn't really have a consistent bootloop. First it started off with the usual, constant bootloop, and then when it got enough of that, it shut off, or I just put it into Fastboot mode to shut off, because it wouldn't stop bootlooping. The power button would always restart it. The loop would start at the start of the booting process(MI Logo) and end when the device would turn on the Lock Screen and then about 3 or 5 seconds later it would crash. Meaning that I can change any setting in the top UI, like wifi settings, bluetooth and whatnot(not that it meant anything since I only had about 5 seconds). Then I left it shut off overnight, and the next day I turned it on, and it actually booted... This gave me a lot of time to back up every photo and video in a panic, and I still had a bit of time. First I thought it was bootlooping because the storage was full, so I uninstalled a lot of apps, and moved about 7GB of data onto my PC. Since the problem kept going, I left it overnight once again to retrieve any more data I needed(right now there's still data on it that I need like 2FA tokens and passwords).
By the way the amount of time I was able to spend in the device was about 5 or 8 minutes before it shut off.. Maybe even more, I had time to move the whole gallery onto my PC and still had time. And the second time I had access to it was just recovering more data, that time I also thought of enabling "OEM Unlock" but I decided not to(like an idiot).
This time though I did not wait till the phone restarted on its own, rather the battery fully discharged at 0%. And that put a somewhat permanent "Empty battery logo" on my recovery UI(the one that uses ADB). I can still access ADB, like the menu works it's just that I'm going blind into it, I can click volume down and select options, it's just that I can't see what I'm clicking. I tried booting it the 3rd time, now in even worse condition than before and now it's fully bricked the whole battery system, because meanwhile I was waiting for it to "do it's thing again" so I can access it I decided to charge it. It 100% had enough time to charge to full battery, yet the phone still thinks the battery is empty and wont show me the Recovery UI. And when I manage to get to the Lock Screen the battery shows 2% and there's absolutely no way it's that low. I slept a good hour waiting for it to charge, and that should be at least 70 - 90%.
Right, so I'm thinking it's either a bad battery connector or a faulty temperature sensor that's making the phone crash, because I can only access it once and that's when it fully cools down, since there's nothing going on in it anyway when it's dead. And later when it heats up it crashes.?
But then again, accessing it like 10 or 20 minutes after it naturally shuts off only gives me about 2 or 3 extra seconds when it fully boots even though being cool to to the touch. And leaving it overnight gives me minutes of time.(if)
Right now I have no idea if I will be able to access it ever again, so if I do I'm backing up my tokens and turning "OEM Unlock" on so I can flash it or factory wipe it. And if I don't, my question is.. Is there anything I can do to save this mf phone? Since I don't even know if I have the right idea to why it could be doing this in the first place, and if I can't turn on "OEM Unlock" I can't even factory reset it properly.
I've tried using ADB to pull files, and just use shell, but I can't due to Errors, I also can't boot a custom recovery without OEM. Shutting it off before it shuts off also doesn't do anything.
Tex2083 said:
Hello, so about 2 days ago from now, my device, while waiting for the bus started to bootloop for no known reason. Skipping into this weekend, I have tried almost everything to get it working without the risk of any data loss, unsuccessful I am here.
Right, so the main problem of the device is that it's very unpredictable, that being said, the device doesn't really have a consistent bootloop. First it started off with the usual, constant bootloop, and then when it got enough of that, it shut off, or I just put it into Fastboot mode to shut off, because it wouldn't stop bootlooping. The power button would always restart it. The loop would start at the start of the booting process(MI Logo) and end when the device would turn on the Lock Screen and then about 3 or 5 seconds later it would crash. Meaning that I can change any setting in the top UI, like wifi settings, bluetooth and whatnot(not that it meant anything since I only had about 5 seconds). Then I left it shut off overnight, and the next day I turned it on, and it actually booted... This gave me a lot of time to back up every photo and video in a panic, and I still had a bit of time. First I thought it was bootlooping because the storage was full, so I uninstalled a lot of apps, and moved about 7GB of data onto my PC. Since the problem kept going, I left it overnight once again to retrieve any more data I needed(right now there's still data on it that I need like 2FA tokens and passwords).
By the way the amount of time I was able to spend in the device was about 5 or 8 minutes before it shut off.. Maybe even more, I had time to move the whole gallery onto my PC and still had time. And the second time I had access to it was just recovering more data, that time I also thought of enabling "OEM Unlock" but I decided not to(like an idiot).
This time though I did not wait till the phone restarted on its own, rather the battery fully discharged at 0%. And that put a somewhat permanent "Empty battery logo" on my recovery UI(the one that uses ADB). I can still access ADB, like the menu works it's just that I'm going blind into it, I can click volume down and select options, it's just that I can't see what I'm clicking. I tried booting it the 3rd time, now in even worse condition than before and now it's fully bricked the whole battery system, because meanwhile I was waiting for it to "do it's thing again" so I can access it I decided to charge it. It 100% had enough time to charge to full battery, yet the phone still thinks the battery is empty and wont show me the Recovery UI. And when I manage to get to the Lock Screen the battery shows 2% and there's absolutely no way it's that low. I slept a good hour waiting for it to charge, and that should be at least 70 - 90%.
Right, so I'm thinking it's either a bad battery connector or a faulty temperature sensor that's making the phone crash, because I can only access it once and that's when it fully cools down, since there's nothing going on in it anyway when it's dead. And later when it heats up it crashes.?
But then again, accessing it like 10 or 20 minutes after it naturally shuts off only gives me about 2 or 3 extra seconds when it fully boots even though being cool to to the touch. And leaving it overnight gives me minutes of time.(if)
Right now I have no idea if I will be able to access it ever again, so if I do I'm backing up my tokens and turning "OEM Unlock" on so I can flash it or factory wipe it. And if I don't, my question is.. Is there anything I can do to save this mf phone? Since I don't even know if I have the right idea to why it could be doing this in the first place, and if I can't turn on "OEM Unlock" I can't even factory reset it properly.
I've tried using ADB to pull files, and just use shell, but I can't due to Errors, I also can't boot a custom recovery without OEM. Shutting it off before it shuts off also doesn't do anything.
Click to expand...
Click to collapse
ADB is useless at this stage, through the stock recovery.
By enabling OEM unlock, but not binding your Mi account, to start the unlocking process, it´s also useless, per se.
You can´t flash any partition through fastboot, if the bootloader is locked, by enabling OEM unlock, it´s not enough to.
Try booting to stock recovery, you can wipe your data/factory reset, in case this may help.
But, probably, the issue is with the battery or the battery connector, pay attention to the charger time, and test if the charge level is correct.
Just in case you need to power off your device, you may connect to the PC while you press the volume down button, you´ll get fastboot mode, then disconnect the cable to the PC, device will shut off itself, when the connection time expires, it may takes only seconds.
Tex2083 said:
Hello, so about 2 days ago from now, my device, while waiting for the bus started to bootloop for no known reason. Skipping into this weekend, I have tried almost everything to get it working without the risk of any data loss, unsuccessful I am here.
Right, so the main problem of the device is that it's very unpredictable, that being said, the device doesn't really have a consistent bootloop. First it started off with the usual, constant bootloop, and then when it got enough of that, it shut off, or I just put it into Fastboot mode to shut off, because it wouldn't stop bootlooping. The power button would always restart it. The loop would start at the start of the booting process(MI Logo) and end when the device would turn on the Lock Screen and then about 3 or 5 seconds later it would crash. Meaning that I can change any setting in the top UI, like wifi settings, bluetooth and whatnot(not that it meant anything since I only had about 5 seconds). Then I left it shut off overnight, and the next day I turned it on, and it actually booted... This gave me a lot of time to back up every photo and video in a panic, and I still had a bit of time. First I thought it was bootlooping because the storage was full, so I uninstalled a lot of apps, and moved about 7GB of data onto my PC. Since the problem kept going, I left it overnight once again to retrieve any more data I needed(right now there's still data on it that I need like 2FA tokens and passwords).
By the way the amount of time I was able to spend in the device was about 5 or 8 minutes before it shut off.. Maybe even more, I had time to move the whole gallery onto my PC and still had time. And the second time I had access to it was just recovering more data, that time I also thought of enabling "OEM Unlock" but I decided not to(like an idiot).
This time though I did not wait till the phone restarted on its own, rather the battery fully discharged at 0%. And that put a somewhat permanent "Empty battery logo" on my recovery UI(the one that uses ADB). I can still access ADB, like the menu works it's just that I'm going blind into it, I can click volume down and select options, it's just that I can't see what I'm clicking. I tried booting it the 3rd time, now in even worse condition than before and now it's fully bricked the whole battery system, because meanwhile I was waiting for it to "do it's thing again" so I can access it I decided to charge it. It 100% had enough time to charge to full battery, yet the phone still thinks the battery is empty and wont show me the Recovery UI. And when I manage to get to the Lock Screen the battery shows 2% and there's absolutely no way it's that low. I slept a good hour waiting for it to charge, and that should be at least 70 - 90%.
Right, so I'm thinking it's either a bad battery connector or a faulty temperature sensor that's making the phone crash, because I can only access it once and that's when it fully cools down, since there's nothing going on in it anyway when it's dead. And later when it heats up it crashes.?
But then again, accessing it like 10 or 20 minutes after it naturally shuts off only gives me about 2 or 3 extra seconds when it fully boots even though being cool to to the touch. And leaving it overnight gives me minutes of time.(if)
Right now I have no idea if I will be able to access it ever again, so if I do I'm backing up my tokens and turning "OEM Unlock" on so I can flash it or factory wipe it. And if I don't, my question is.. Is there anything I can do to save this mf phone? Since I don't even know if I have the right idea to why it could be doing this in the first place, and if I can't turn on "OEM Unlock" I can't even factory reset it properly.
I've tried using ADB to pull files, and just use shell, but I can't due to Errors, I also can't boot a custom recovery without OEM. Shutting it off before it shuts off also doesn't do anything.
Click to expand...
Click to collapse
Hey there. Was you issue fixed? I had somewhat of a similar issue. My phone did the same bootloop in two different days. First I thought it was some error after update. I didn't bother. It happened once again and after few times of crashing at lockscreen, it actually booted and I was able to use it for a day. I thought of backing up my stuff but didn't give much attention. Now it have happened once again and this time it is never getting into usable boot. If the battery is sufficient enough, it'll go into lockscreen and crashes repeatedly. Then soon it just crash after the MI Logo and the three loading dots. Safe mode does the same. It boots into lockscreen at times but the safe mode symbol is not seen.
I read you were able to get your data out of it. Did you resolve the issue?

Categories

Resources