Hi!
Very weird situation. Before that everything was stock and OK (no custom ROM or anything).
- If the phone is unplugged, nothing works at all (key combinations,...)
- The battery is charged, at some point, when totally off, it showed the battery charging, 60% at least. But have not been able to go back into this mode.
- When connected, it starts booting, but keeps rebooting very fast (1-2 s after Samsung splash screen).
- Unable to boot into Recovery mode (UP+HOME+PWR, for wiping cache,...). Just does nothing, howerver long I wait
- Unable to boot "directly" into Maintenance Mode (all buttons), more on that later
- Can boot into Download (ODIN) mode (DOWN+HOME+PWR) very easily. I was able to flash stock ROM, but nothing changed.
- From ODIN mode I can boot into Maintenance mode (all buttons). I can navigate the menu, but any choice, even Factory Reset, gets me directly back to the reboot loop...
As I can not even turn it off, I cannot drain the battery (at least not quick). As soon as I disconnect the cable it goes dark (whatever mode I am in).
Anything I missed that I could try before throwing the phone?
Thanks!
SOLVED
Just to leave a trace on what happened:
- Left the phone alone, un plugged, for 8-10 hours.
- Just to see, tried to reboot it normally,
- It booted on a blue/cyan display, with "installing updates".
- At one point before I had that screen, but after 10 seconds it rebooted into the loop cycle. And after playing with the recovery reboots, I had never managed to get this special boot again.
- This time it stayed on "installing updates" for 1-2 mn, then rebooted, and Voilà!!!
So apart from my magic touch of doing nothing, don't really know what happened... So much for the recovery recipe!
A fairly similar thing happened to my girlfriend's g920v yesterday. We haven't been that lucky that it got fixed.
The situation is slightly different though, it boots for about 3 seconds, makes the low battery sound, battery indicator says 0%, then shuts back down.
Tried flashing stock in odin a few times, a few factory resets, nothing.
It seems like an OTA update failed and now the stupid locked bootloader won't let me or the or OS fix it.
Sorry you were not as lucky... But as you said the problem seems a little bit different, as I never had an empty battery warning. I agree though that it looks as a bad update stuck somewhere.
guimou_qc said:
Sorry you were not as lucky... But as you said the problem seems a little bit different, as I never had an empty battery warning. I agree though that it looks as a bad update stuck somewhere.
Click to expand...
Click to collapse
There's got to be some connection of some sort, yours is the 4th post I've seen here or on Reddit this month about bootloops probably related to updates
Hello, recently I started reading comics and found my old tab lying around so ill give it a go
First thing first it wont boot becaue it had no charge obviously (been there for like some years), then I tried to plug the charger but to no avail
I cleaned the contacts of the charger with a dry brush and start charging which then my tab starts charging!
when I booted, I think it was CM 12 (or 13? the one with andy I believe) and everything is force stopping.
I then tried to go to recovery mode and wipe data, but when i rebooted it it just stuck with the splash screen (the one before bootanimation)
I turned the tab off and tried to boot to download/recovery mode but it would just boot me right to the splash screen again, which mean i cant go to TWRP or ODIN.
And it doesn't always want to turn on, sometimes it just stuck there with black screen (not turned on) even if i press power/combo button, sometimes it pop up to the splash screen. what i notice is that i should wait for the charging indicator to show up before i can try to boot again (i got enough juice now, 56% the last time it turned on)
also one thing i remember is something about F2FS but im not sure what that is, but that might be a clue to my situation so ill just write this down here
Hi
Same here with P5110 and Slim7. I can't start it anymore....
I didn't use it for some time and then i charged it to 100% and it started but everything seemed to lag. Then i turned it off and wanted to look for another rom or a newer build. But i can't start it anymore. when i plug in the charger i can see the charging screen but beside of that i can do nothing. It has no effect when i push the on/off button or anything else...and it has to be at nearly 100%...
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
bigblkyj said:
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
Click to expand...
Click to collapse
If what you've described is correct, all of the solutions involve flashing the stock firmware which will of course wipe the device.
Were your photos not stored in a folder on the SD card?
There is a chance you can recover the device using Samsung Kies with the emergency recover option but if you've encountered the "no command" screen it's not looking good.
Unfortunately I did have an SD card installed, but I normally kept my camera pics on the phone's memory, since I have had an SD card fail as well and lost everything on there.
So this took an unexpected turn yesterday pretty much right after posting this... I've been messing with the phone, unplugging the battery each time, and have managed to get into different menus which kept making me think that something still had to be working if I could do that. Well, after leaving the No Command message on the screen it magically booted into the Recovery menu with (finally) the option to wipe the cache partition, which I did and rebooted normally. Believe it or not, it booted normally and into the OS like nothing ever happened?!
I instantly plugged it into my PC and ran Smart Switch which started taking a backup! About 25% though the device restarted again and was really warm to the touch on the RF covers inside. Bummer...
So I figured heat was now the issue for some reason... I waited for it to cool and then reinstalled the SD card and figured, if I could get it to boot long enough, the SD card is a quicker transfer and I'd just use ES File Explorer to try and do a photo dump to the SD card and see how far it would get. It actually made it all the way through and gave me enough time to grab some other stuff before getting hot and restarting again.
I believe the overheating is being caused by my opening of the device though... Currently I have the antennas removed and the speaker so that I'm able to quickly access the battery connector (which BTW seems to be the trick here to this working) But inadvertently, without the larger wireless charging coil in place, it relieved the pressure on the motherboard and broke the thermal paste connection between the chipset and the copper heatsink (I didn't tear it down further to check, but I can hear the 'sticking and peeling' when you press down on it).
I think what I'm going to do is apply pressure with a chip clip or something similar (non conductive) and see if I can grab a backup again before it restarts. After the cache wipe the phone seems to understand that it's plugged in and charging now which is a new thing as well...
Sorry for the long winded posts, but if this at all helps even one person with the same situation as I have, maybe that'll be worth getting lost in here
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?