Database Info

[Completed] Stuck at LG logo on LG L5 II e460

So, yesterday I decided to reboot my phone since it was very sluggish for whatever reason. I think it shut down properly but when it came back on, there was a very interesting problem that had come up - it didn't boot any further than the logo screen, which didn't even play its standard animation; it just stood there with the LED on the home button changing colors (like normal). I left it on overnight hoping the problem would be gone, but to no avail. It still hadn't booted when I woke up. If it matters, the only thing I can boot to is download mode. It doesn't let me get to safe mode or however it's called (the menu you navigate with volume up/down and the power button). Needless to say, I was very puzzled. Then I went on and tried to flash the latest kdz since I thought that would fix the problem. I hoped that would easily fix the problem. But no, it decided to be funny and give me more headache. I tried using this guide: http://forum.xda-developers.com/showthread.php?t=2409308 but after step 20 the LG Mobile Support Tool crashes and I can't continue. Sure thing, I will try the Upgrade Recovery that the tool has built in. It properly detects my phone, the software download and extraction goes smoothly. Then I reach the S/W Upgrade part of the process. The few first seconds everything is fine, but then the bar reaches 5% and just stops. Just like that. Now it's been 8 hours since I began the recovery and no progress has been made.
Can anybody help me? I'm lost here...

rexsis13 said:
So, yesterday I decided to reboot my phone since it was very sluggish for whatever reason. I think it shut down properly but when it came back on, there was a very interesting problem that had come up - it didn't boot any further than the logo screen, which didn't even play its standard animation; it just stood there with the LED on the home button changing colors (like normal). I left it on overnight hoping the problem would be gone, but to no avail. It still hadn't booted when I woke up. If it matters, the only thing I can boot to is download mode. It doesn't let me get to safe mode or however it's called (the menu you navigate with volume up/down and the power button). Needless to say, I was very puzzled. Then I went on and tried to flash the latest kdz since I thought that would fix the problem. I hoped that would easily fix the problem. But no, it decided to be funny and give me more headache. I tried using this guide: http://forum.xda-developers.com/showthread.php?t=2409308 but after step 20 the LG Mobile Support Tool crashes and I can't continue. Sure thing, I will try the Upgrade Recovery that the tool has built in. It properly detects my phone, the software download and extraction goes smoothly. Then I reach the S/W Upgrade part of the process. The few first seconds everything is fine, but then the bar reaches 5% and just stops. Just like that. Now it's been 8 hours since I began the recovery and no progress has been made.
Can anybody help me? I'm lost here...
Click to expand...
Click to collapse
Hi, thanks for using XDA assist!
Please post your question here:
http://forum.xda-developers.com/showthread.php?t=2257421
The experts in that thread will be able to help.
Good luck!

Thread closed.

Can't boot, restarts constantly

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.

Wondefoo HCT-PX5-REV12 periodically won't turn on

Hi,
First of all, please excuse me if I have post on the wrong forum. I really searched a lot for a similar question but haven't found it. My unit's MCU versoin is MTCE_CZ_V3.10_2, so I don't know if it's really a "MTCE" head unit, but I don't see a MTCE specific sub-forum (by the way, what does the MTCD, MTCB and so on nomenclature mean?). I got this unit from AliExpress about a year and a half ago, it's a 4 GB, octa-core [email protected] version, with 64 GB internal memory and DVD, for Vauxhall/Opel Corsa, and this is the current (updated) product page for it:
https://www.aliexpress.com/item/32789005299.html?spm=a2g0s.9042311.0.0.27424c4dbyAN90
It currently displays a PX6 version; mine is the PX5 one.
Well, the problem with the unit happend a few weeks after I installed it on my car. Suddenly, one time, when I started my car's engine, I noticed the unit wouldn't turn on. No matter how times I attempted to reset it, it wouldn't do anything (although when doing so, through the small pin hole, colorful led light would cycle through the cover.
I contacted Wondefoo and they sent-me a an HTC-PX5--REV12(LPDDR-221), 20190515, board replacement, exactly like the original one. After replacing it, the unit started working again.
In january 2020 this happened again. Tried exchanging it again with the original MCU; nothing worked.
Nearly two months later I attempted the same procedura and this time it worked - the unit started working again.
My bet is that something is causing this unit to get stuck, and after enough time passes and the capacitors get emptied and the DRAM erases, it's able to "recover" somehow.
Maybe 6 months ago, this happened again. Out of frustration, in the middle of a drive, once I started pushing all the buttons randomly. Finally, I don't know by which combination, the unit turned on, displaying a recover menu. I don't know how, simple choosed to restart and it became working again.
Some weeks later, after getting unresponsive again and trying the "random button push" procedure, the menu showed up again. This time I attempted a factory reset and got the unit working for severl weeks.
Finally, my unit died for the last time about two months ago and I haven't been able to recover it by the "pushing buttons" method, neither by disconnecting it from the power source and reconnecting days later. I came back to the original radio player, which is a hassle as the CD player is also broken.
I'd like to try echanging the MCU with the spare one; I'm almost sure that it will work again, but before doing so I'd like to assure that I won't find myself in this situation again, as it's a waste of time. Maybe the problem is known and you can recommend me a software version / update that would prevent this from happen again. Maybe there is some sort of hardware mod that can be attempted by replacing some component. Maybe you know how to "hard reset" it from some motherboard pins, maybe where I could mount a switch to do so when the unit becomes dead, or maybe you can tell me the proper key combination for the recovery menu.
I've also found some firmware pages, namely https://yadi.sk/d/umCvHqCDzHccr, with a long list for several models. It looks more or less clear where to get the MCU firmware, but for the Android image it's a bit more complicated. If I enter the RockChip PX5 Android 9 folder, then HTC subfolder, there are several HTC4_XXXXXXXXXXX, HTC5_XXXXXXXXXXX and HTC_XXXXXXXXXXX options, and the same for RockChip PX5 Android 10 (assuming that there were an Android 10 update for my hardware; it came with Android 9 if I'm not wrong), so I don't know which one to attempt.
PS: the "reset" little hole never has really worked for me in this situation. It just will cycle to RGB leds if I push it with a paperclick and, while pushing, press the "on" button, and they will shut off when I release the button, but that's all.

Noone encountered a similar problem?

Problem after updating to ColorOS 11.1

Hi everyone. I'm using an Oppo Find X2 Lite since january and today I finally received the update to the ColorOS 11.1 based on Android 11. I put my phone in charge and started updating, but when the process finished something strange happened. When the phone re-booted it showed nothing but a black screen with the top bar with time, wi-fi and battery icons that goes on and off in a loop. I can't do anything: if I try to boot off the phone by pressing the power key, a white empty rectangle appears on the screen, but touching it does nothing. If I press the power button multiple times I can enter in a "SOS Emergency" mode by which I can use the flash light as an SOS or call my local number for an ambulance.
After buying the phone, I debloated it with adb commands following a list I found on this forum: may this be the reason for this behaviour? After debloating the phone I updated it a couple of times, but they were minor security update of ColorOS 7.
I have no idea of what to try, I'm just waiting for the battery to die and then try to access a recovery mode. Hope someone can help me, cheers

kibalcic said:
Hi everyone. I'm using an Oppo Find X2 Lite since january and today I finally received the update to the ColorOS 11.1 based on Android 11. I put my phone in charge and started updating, but when the process finished something strange happened. When the phone re-booted it showed nothing but a black screen with the top bar with time, wi-fi and battery icons that goes on and off in a loop. I can't do anything: if I try to boot off the phone by pressing the power key, a white empty rectangle appears on the screen, but touching it does nothing. If I press the power button multiple times I can enter in a "SOS Emergency" mode by which I can use the flash light as an SOS or call my local number for an ambulance.
After buying the phone, I debloated it with adb commands following a list I found on this forum: may this be the reason for this behaviour? After debloating the phone I updated it a couple of times, but they were minor security update of ColorOS 7.
I have no idea of what to try, I'm just waiting for the battery to die and then try to access a recovery mode. Hope someone can help me, cheers
Click to expand...
Click to collapse
Try holding volume up + power button for 10-15 seconds phone should power down , when it does hold voume down plus power button should take you to recovery mode.

Hi,
I answer late but I got the same problem with my Oppo Find X2 lite. After dowonloading the Color 0S11.1 update my phone restarted.
But then I couldn't unlock it. The screen was flashing on and off in a bootloop.
I managed to get in recovery mode using the method described above. Unfortunately I couldn't just remove or restart the update and I had to do a full factory reset. Then the Colors OS 11 update went smooth.
I had also debloated my phone but only a few apps and services. I was very careful. So I have another clue : to me it looked like the phone couldn't load the fingerpint id sensor on start screen.
I wonder if it shouldn't be deactivated before any major updates.
@kibalcic : did you manage to solve your problem ?

Question Z flip 3 bootloop

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.