Hello,
I’ve got a One S (S4 version) that’s driving me crazy. Can you help me please?
I bought this phone second hand – hoping that I could fix it up and give it to my mum for her birthday. It looks immaculate, but it was sold because the previous owner couldn’t get it out of a boot loop.
When I received the phone, the first thing I did was to hook it up to the charger. As soon as the charger was connected, the charging LED came on, but then after about 5 seconds (without pressing the power button), the device turned its self on and begin rebooting at the “Quietly Brilliant” screen. It wasn’t the usual “Quietly Brilliant” screen though… There was a progress bar in the top right hand corner, indicating that it was trying to flash something. The progress bar went from 0-100% twice, then after a pause of about 20 seconds – it rebooted again. This process would repeat endlessly
After a lot of messing around, I managed to get into the bootloader. The status was “Tampered – Relocked”. At this point, I downloaded and flash the latest RUU (2.31). However, even though the RUU flashed successfully, it still boot loops. The only difference is that the “Quietly Brilliant” screen no longer has the progress bar in the top right corner (it’s just the normal boot screen now).
After this, I unlocked the bootloader via HTCDev and flashed CWM recovery. The flash was successful , but trying to access recovery also fails. It just sits on a screen with the “for development purposes only” warning for a few seconds, then reboots and follows the same boot loop sequence as before.
Does anyone know whether I’m wasting my time on the phone? At this point I’m very worried about flashing things, because I never know how much juice is left in the battery. If I hook up the charger, the charging LED does come on, but only for a matter of seconds. After 5-10 seconds, the charge LED goes out and the device automatically fires up into a boot loop. It’s impossible to power down the device when it’s connected to the charger. It will turn its self back on again! The best I can do is to leave the phone sat in the bootloader, but there is no indication that it’s charging (no LED).
:crying:
I've just read over my last message and I think the clue is in the way this thing turns on by its self when connected to power. I bet some water has got into the phone and caused a mess inside. I think it might be time to get the screwdrivers out.
Related
Yesterday, after installing the 2.2 update (maybe related?) I plugged it in to charge and couldn't get it to wake up after charging for some time. When it eventually did come up, it came up to the boot loader screen (small text with a list of options) choosing Continue or Recovery from the list gives me small text that disappears quickly that reads "boot failed" (along with other things I couldn't read).
Fastboot seems to be working, but any command to reflash partitions is met by a notice that it failed because my boot loader is locked, and if I try to fastboot OEM unlock, it prompts me on the tablet, I choose yes, and it promptly fails (fastboot returns unknown error). Perhaps the emmc is toast or is it still recoverable via APX or something like that? I couldn't find anyone who had used APX on the shield tablet.
This morning the battery appears to be dead (I let it discharge overnight, hoping that doing so would clear some state and get things working again) and when I plug it in to charge the display does power on (backlight lit with black screen) but I don't see the charging animation come up.
I spent hours searching into the night last night and couldn't find someone who couldn't even unlock the tablet. I'd really like to fix it myself and not have to RMA because I wanted to use the tablet to play Ingress at an event this weekend. It's the LTE model and I bought it for playing Ingress.
Any ideas for how to bring this tablet back?
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.
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