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?
Related
I was using an app on Sunday, when the app froze completely and the screen of the s3 went black. The only thing I could see was the status bar up top, but even that was unresponsive. So I pulled the battery and turned it back on, and it was acting extremely slow so I got impatient and started trying to get into settings, when it went unresponsive again.
This time I held down the power button to see if I could get it to respond and the lock screen came up, without my wallpaper and instead of Verizon Wireless at the top, it said "No Service". After a couple of seconds my wallpaper showed up and then it said Verizon Wireless. After I get through the lock screen, I would go through the same whole routine - e.g. try and get into settings, freeze, hold power, have it come back up, etc. So I battery pulled again.
Finally, I got it to boot OK, by just letting it be for 10 minutes and completely ignoring it.
However, today my battery drain was pretty fast, it was on for 12 hours and was down to 40% after only 30 minutes of screen time. The culprit was "Android System" at 61%, i've never seen this that high before. Because of the high "Android System" power usage, I thought it might be good to power it down. Upon boot up, I assumed I'd be able to use it immediately, so I started going into Settings, and yet again it went unresponsive.
Are the two issues unrelated? What should I do?
As a warning, I'm extremely new to anything smarter than a Nokia brick, so be patient - Thanks!
As inconvenient as it is, I would recommend a full system wipe and go back to out of the box. That seems to fix everything and unfortunately it is rather difficult to diagnose issues on phones, especially unrooted.
In order to do a wipe you can do one of two things, goto settings then backup and reset, then hit factory data reset.
-OR-
Turn off the phone. When you start it again hold volume-up, power, and home to get into recovery. Then do the factory reset.
Ok, I thought that's what my option was. Thanks dwibbles.
Bought a Nexus 5 about 6 months ago USED. It has been amazing. I got the latest OTA a week ago or so, not sure if that has anything to do with current issues.
About 2 days ago started randomly restarting. Today, it shut down and has been in continuous loop restarting. I see "Google" and maybe even the boot dots loading, then it is off. Three seconds later, starts again and repeats. Never makes it all the way into Android system. I let it sit for a while and when I pick it up, without touching any buttons, it repeats all of this. I suppose it is probably dead in general, but I don't know. Do you guys have any ideas? Again, I bought it used and from a ma/pap store who said they buy 100 in bulk, which made me skeptical, but they also had a 60 day guarantee and it was amazing the first 60 days and even after. It has been error free for 6 months, so I don't know if this is just a random issue or if the previous owner dropped it in a lake and I got lucky, or what. FWIW the damn thing has been in a case and never dropped, so it isn't anything that I have done I don't think. Thanks for any help.
edit: never rooted, never messed with, always been stock
Another user reported some instability since the last OTA update.
Flashing the full factory images did the trick.
a friend of mine gave me his nexus 5 to repair and its doing something similar. He had ir rooted and on latest 5.1.1 (i think). Either way, he said it was randomly locking up and rebooting. When i got it it had the red blinking light when plugged so i got a new battery. That got fixed but then the constant bootloop showed itself. I flashed TWRP (many versions, 2.6.3.1; 2.7.1.1; 2.8.7.1; the one that worked best was 2.7.1.1). So, once in twrp wiped, pushed cm 12 snapshot, flashed it, pushed gapps, falshed, pushe supersu flashed. Started the system. That precise order of things (ie: pushing flashing, then pushing something new and flashing it) was what gave me best results to actually boot up at least once. Once booted up and logging in and everything to cm i had some sort of stability (even rebooting and powering off) but i think that everything went wrong when i plugged the phone to the computer and it was back to bootloops and not even getting to the recovery. Flashed everything again. Didnt work. Had to leave the phone sit for a while (without the back casing) before trying again, in order, before getting any success. Im starting to think of ovrheating but it doesnt even get that hot...
Dunno if you guys have any ideas on this. Or if i can give you mor details to help us out.
Regards!
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
WaxLarry said:
In my opinion your problems seems power button's related.
Click to expand...
Click to collapse
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Paul22000 said:
This morning my Nexus 5 was turned off all of a sudden after not having used it for 20-30 minutes. I held the power button and nothing. I plugged it into power and the "Google" screen appeared. It then went into a reboot loop on and off, on and off, on and off. I held the Volume Buttons and it went into fastboot, but then boot looped out again and again. Searching on Google yielded that this was indeed a common problem. [...]
Click to expand...
Click to collapse
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Ok @jeffsf keep going on this thread. I had the same damn experience, that ended with RMA. LG said that the problem is related to some tension change in the power button. After the RMA I used the phone totally stock and never had a problem. Two months ago I switched to blu_spark kernel and some weeks after i noticed some problem. When I pressed the button to lock the screen, phone locked itself and then screen turned on, sometimes showing the shutdown option. So i understood that something was happening to the power button. I tried to overvolt with a +5mV on general offset and since then i never had problem. If you can enter recovery or bootloader i suggest you to flash some kernel with volt change support and then overvolt the general offset... and keep finger crossed
jeffsf said:
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Click to expand...
Click to collapse
I got a notification for this post since you quoted me. I'm not sure if you're having the same problem but I'll tell you what happened to me, just in case. I called T-Mobile and they referred me to the nearest 3rd party phone repair shop. I went there and after an evaluation, the repairman told me the power button on my phone was indeed broken. They replaced it for $55.
The story doesn't end there though. I took my phone home and a few hours later I tried to use bluetooth and it didn't work. I took it back and found out that unfortunately, when the guy replaced the power button, he inadvertently broke the bluetooth. There's no way to fix bluetooth without replacing the motherboard entirely, which would cost $200. I'd rather buy a new phone at that point since my Nexus 5 was getting old. He refunded me, which was nice. At least the power button worked so I could use my phone. Bluetooth isn't as valuable as being able to you know, turn on the phone, so at least it was a net gain.
After that, I purchased a Nexus 6 and rooted it so I could use double-tap-to-wake (along with the automatic screen on when you pick up the Nexus 6). I also use the following app in order to turn off the screen by swiping up from the home button (I don't care about losing the shortcut to Google Now): Screen Off and Lock
I can now literally go weeks without using the power button on my Nexus 6. (I literally only use it when tap to wake sometimes becomes unresponsive which is rare.)
Bottom line: I will never buy another phone without tap to wake functionality! :good:
A local repair shop here indicated that one sometimes does changing the power switch resolve the issue. They have seen situations where the issue appears to be one of the power-management ICs. Just something to be aware of when examining the potential cost of a repair and who you would have do the work.
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
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
The problem I have is with the galaxy z flip 3, it worked just fine inthe morning but after it ran outta juice and I charged it to a certain percentage, it stopped working properly, and got into an infinite boot loop, I tried forcing it to restart by long pressing volume down+power , but it didn't work, then I tried opening the recovery by long pressing on volume up+power and yet it also didn't work (I think that maybe it's because it was trying to boot at the time), so have you guys any solutions , please do help me cuz this phone really is important and with all honestly, isn't even mine XD, I'll be waiting for an answer
Your failsafe options are contact Samsung or do a factory reset (and then potentially contact Samsung).
If you can't boot it to anything, the only real option you have is to flash firmware, which likely won't help without wiping.
Unfortunately, not booting doesn't have a whole lot of options that don't wipe data without being rooted. Even then, you'd need recovery.
I see, then I may consider giving it to samsung, as long as they won't reset it, cuz the only reason why the phone is so important is because of the data, altough, isn't there any other way to acess recovery? Cuz I had this problem with the s10 before and I fixed it somehow (a certain Bixby key combination), but this time it seems there isn't any hidden combination.
Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left
twistedumbrella said:
Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left
Click to expand...
Click to collapse
Well I just asked the original owner (my mother), and apparently she doesn't remember downloading anything new into it, and it just went crazy by itself, also something else I wanna note, I tried charging it and it booted into recovery all by itself, I taught it was weird but Still went and wiped the cache and then when I tried restarting it it suddenly ran out of juice once again, also, it's second display shows some weird curruption/bug or glitch-like lines. So based off of this, can you really find the origin of this problem and if there is really any hope of saving it's data XD. Thank you btw, and once again, I'll be waiting for an answer
There are hundreds of reasons it could do that, including a faulty board. Thanks to the removal of physical sdcard support, you'd need to get it to boot into something with at least adb support to pull anything off it. Stock recovery doesn't provide any ways to perform a decent backup, but it sounds like the only option that wouldn't wipe the device didn't work.
I see, alright, thanks a lot, I'll consider resetting it
It may be worth trying to flash firmware first. Go into it knowing it may reset the device or leave you needing to reset it, but it doesn't hurt to try if you run out of safer options.
Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )
ariveraiv said:
Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )
Click to expand...
Click to collapse
Hello everyone just a quick update. Once I got home I plugged the device into a Samsung fast charger and Samsung OEM USB type-c cable and realize the device booted all the way to the home screen but register the same battery level as I mentioned above. Device was working as if nothing happened to it. So I updated all the apps on the Galaxy store then updated all the apps left over from the Google Play store, I then proceeded to check for a firmware update because I know the April update just released and installed the update with no issues. Updated the apps that needed to be updated again somehow there's always something and unplug the device from the power cable. Everything was working if no issues about half hour later the device cuts off and does not want to power on. FYI I already had my wife contact T-Mobile and get a warranty replacement we only paid $5.00 so my thoughts and conclusion on what's going on something happened to the battery or it's defective. Btw we only use Samsung OEM cables and equipment at home and in the car while connected through Android auto. it's only working while being plugged in it's not charging all the way even though it's registering it's charge level while the device is on.