tl;dr summary:
- Replaced screen, worked for 1 week
- Randomly switches between hard-brick no response, and soft-brick boot loop
- Boot loops on loading TWRP as well as OS
- Running latest 7.0.0 NBD90W
- Phone is H790 variant
- Flashed Android 7 in the bootloader, not through OTA. This was as soon as Nougat came out, and it worked great for weeks.
- Bootloader unlocked (for temp-booting twrp only, "fastboot boot twrp.img" otherwise kept stock)
- Phone NEVER rooted
- No charging indicator when plugged in
- Battery bent during previous removal, maybe causing issues a week later?
Replaced screen with genuine LG front frame assembly after a running accident cracked my screen/digitizer. Phone worked fine for about a week, then randomly shut off and went into a boot loop.
Now it randomly switches between a boot loop and a hard brick. When it's acting like a hard brick, sometimes it goes back into boot loop temporarily if I disconnect and reconnect the battery. It eventually returns to hard brick.
Hard brick mode:
-- Doesn't respond to any power button presses. Does not indicate charging when plugged in. Entirely unresponsive.
Soft brick mode:
-- Normal boot: normally gets to Google logo and restarts. Rarely makes it to the flashing dot animation. Twice has booted into Android, past the lock screen, and works perfectly for ~10-15 seconds before rebooting.
-- Boot into bootloader: On occasion will reboot itself from bootloader, but rare. Usually works correctly including all adb commands.
-- Boot into stock recovery: Same as bootloader, usually works, sometimes reboots.
-- Boot into TWRP 3.0.2-2 bullhead: boots for a few seconds and then locks up. Has never made it through decryption - will either a) freeze and reboot right after I draw my pattern, throwing an error that it could not mount storage right before restarting or b) freeze and reboot anyway if I take too long before drawing my pattern. It seems to be more time-based than a function of anything I do.
Things I've tried:
Since my bootloader is unlocked, I've re-flashed these partitions with no fix:
bootloader.img
boot.img
recovery.img (stock)
radio.img
vendor.img
I've cleared cache through stock recovery, can't remember if I tried flashing cache.img
I have yet to flash system.img or userdata.img as I have a few files I'm trying to recover... The fact that I can't boot into TWRP, and the sporadic hard-brick behavior, doesn't give me enough confidence that wiping my data will help.
Phone tends to live in hard-brick mode unless I disconnect and reconnect the battery, then it sometimes goes into soft-brick boot loop for a while before once again hard-bricking itself. When hard bricked, no charging indicator appears when plugged in. When soft-bricked and turned off, will sometimes display the battery status after short-tapping the power button. No change when plugged in except only once it displayed the battery with lightning bolt icon for about 2 minutes, before returning to the icon without the lightning bolt.
My best guess is that I damaged the battery during removal.
- The adhesive was really strong, and while I didn't puncture the case, I did bend it somewhere between 30-45 degrees in the process. If I damaged the Li-Po foil, would that make sense for the phone to work, only to go belly-up a week later? I ordered an OEM LG battery for $13 because it's worth a shot at that price point. Arriving next week.
- The reboots sound in-line with it crashing when it tries to draw too much power? Bootloader and stock recovery usually run okay and I assume have a low power draw. The OS and TWRP probably draw more power and that's where it fails? The reboots seem to be more time-dependent than depending on anything in particular that I do, such as rebooting before OR after drawing my pattern on TWRP. And that it sometimes boots into full Android for a few seconds implies to me that the OS is working on at least some level.
Does anyone have any better ideas for when the new battery inevitably doesn't fix it, or things to try in the meantime? Could the common Nexus 5X boot loop under Nougat be causing issues booting into TWRP too? It feels hardware-related to me. I took it all apart and looked for loose/oxidized/bent contacts on all the connections but couldn't spot anything.
My Pixel isn't arriving until Nov 23-25, and to make matters worse I switched to Google Fi 3 days ago and I have no compatible phones to use in the meantime. Oops, lesson learned.
Related
Wanted to seek some clarity on whether my phone is HW bricked. Here're the conditions:
Rooted/Unlocked Bootloader/Custom ROM/Stock Kernel
Randomly found the phone not responding last night, no software updates or heavy usage that day.
Have to long press power to get to turn on. Typical bootloader unlocked warning message then Google screen, then phone turns off. No screen content when charging (battery indicator or booting).
I can get to fastboot with power/vol down and interact with from Nexus Toolkit but attempting to boot to anything including TWRP just produces the same sequence: boot warning, google logo then complete shutdown. Tried booting recovery, wiping, etc from toolkit, nothing.
Occasionally it'll loop once or twice but most of the time it just shuts right off.
Phone is in the freezer now, will try heating solder later. Am I looking at a new phone here? Anything else I can try before heading to the store?
Same issue
Did the freezer trick work?
I have the same issue.
Nexus 5X
Rooted/Unlocked/TWRP/Stock ROM
Randomly turned off, Long press to get back on. Turns off during boot. Managed to access Recovery the first time but havent been able to since, just shuts off.
Google chat thinks it hardware issue.. still under warranty, but would be nice to back up the userdata from it some how...
Surprisingly enough the freezer trick allowed the device to boot into recovery.. unfortunately it wasn't long enough to recover any data and now the phone won't turn on at all :/
Hi,
a few hours ago I dropped my G4 H815. The back fell off and the battery got out. I put the Battery back in and after a few tries I could load the device. However, I just can`t start the phone now. When I press the power Boutton, nothing happens.
When plugging in the microUSB-Cable the screen turns on and I sometimes see the screen with the LG Logo, but no matter how often I try, it does not boot into recovery (the volume down key was always a bit tricky though). It just goes on to the Screen saying your battery is loading and it´s at 100%.
I can reach Download-Mode, but I do not see any way to force a reboot from there.
My Bootloader is unlocked and the device is rooted. Im running TWRP and LineageOS 14.
Norkzlam said:
Hi,
a few hours ago I dropped my G4 H815. The back fell off and the battery got out. I put the Battery back in and after a few tries I could load the device. However, I just can`t start the phone now. When I press the power Boutton, nothing happens.
When plugging in the microUSB-Cable the screen turns on and I sometimes see the screen with the LG Logo, but no matter how often I try, it does not boot into recovery (the volume down key was always a bit tricky though). It just goes on to the Screen saying your battery is loading and it´s at 100%.
I can reach Download-Mode, but I do not see any way to force a reboot from there.
My Bootloader is unlocked and the device is rooted. Im running TWRP and LineageOS 14.
Click to expand...
Click to collapse
Well it sounds like the infamous Bootloop at least the symptoms are the same. The Bootloop issue is not caused by dropping the phone but while booting Android as this is a very CPU intensive process.
Ilapo or not I would take a backup with SALT before anything else.
You can also boot to fastboot and assuming you haven't installed the nougat v29 bootloader stack you can just boot TWRP temporary by using
fastboot boot twrp.img
(where twrp.img should be my latest TWRP version preview 144 or higher)
Sent from my LG-H815 using XDA Labs
No Bootloop. It seems like the power Button is broken. Using SALT I could reboot the phone and it starts and works normal. The knok-on feature makes this situation, at least temporally, bearable.
I will probably try to fix the Button.
Hi, my 5X got itself into a bootloop state I have no knowledge of and I would really appreciate some pointers.
I searched the forum but I'm still not sure what I'm looking at and more importantly what to do about it. My main concern is not losing my data on the device.
Short summary: unlocked bootloader and rooted, bootloops, difficult to power off, factory images flash successfully but still only bootloader boots. The phone is on the latest stock Android 8.1 and was rooted with Magisk. In the meantime I've reflashed all factory images except userdata with no luck.
Bootloops: the phone started bootlooping by itself overnight. It was on the charger for a top-up and running only a sleep monitoring app like any other night. It boots as far as the Google logo, pauses a bit and repeats.
Power off: if I leave the charger cable connected the phone powers off from the bootloader menu only as far as the charging display and then starts bootlooping. If I first disconnect the charger it does power off, but as soon as I reconnect the charger the phone turns on and starts bootlooping.
Reflashing doesn't help: all factory images reflash successfully but the phone still won't boot into anything other than the bootloader. Booting into either the standard recovery or TWRP goes straight into the same bootloop. FWIW I also obtained the latest cache image and erased and flashed that but no luck.
My main concern is not losing my data so I want to be careful with whatever I try next.
I'd be really grateful for some pointers on what I'm dealing with and what the options are, thanks.
In case some other lost soul with the same problem stumbles across this, the explanation and fix are here:
https://forum.xda-developers.com/nexus-5x/general/tool-bootloop-death-blod-workaround-t3819497
So I updated to Android 11 on Tuesday, and all seemed fine. Last night my phone was trying to install an app, and seemed to freeze.
After a few minutes, I forced it to shut-down (power + vol down) and it started to reboot. It got to the G logo with the small bottom bar animation for a number of minutes and eventually kicked back into Recovery mode.
I decided to try rebooting, and it started to reboot, got to the Google logo (the full word, not the "G"), and then kicked back into rebooting.
The phone now constantly reboots and even if I get into fastboot mode, it only stays in fastboot until I hit a key (vol up/down or power) and it then reboots into constant bootloops described above.
If I don't push a button on fastboot mode, it will just start booting anyways after about 3-5 seconds.
Does anybody know of what I could do? Not sure if replacing the battery would help (e.g. a power issue) or if it may be a corruption of the flash memory and that the system and underlying partitions are corrupt leading to nothing I could do to repair the phone.
I have really enjoyed this phone, but I am afraid that this phone is all-but-dead and unusable.
Any assistance is greatly appreciated.
Cheers,
B.D.
You can try flashing the stock rom from recovery or from fastboot.
Had something similar on an og Pixel... Turned out to be a broken power switch.
I had a weird issue last week. Phone would freeze after a couple of minutes and would reboot. It would also boot loop while connected for charging (wireless and corded.). The battery would not charge. I would shut down the phone and when I plugged in the charger, it would boot loop. The battery finally discharged to 0% and shut off. I plugged the charger in and it remained off. I let it charge to 100% and it's been working for the past week without issue. I'm not sure what happened.
I would suggest letting the battery drain to 0% and go from there. HTH
I updated my 3XL to Android 11 two days ago and since then I have caught it rebooting at seemingly random times, though only when it is on the wireless charger. I guess it's back to Android 10 for now. Hopefully reverting a Pixel is as easy as it was on the Nexus. Thanks Google.
BostonDan said:
So I updated to Android 11 on Tuesday, and all seemed fine. Last night my phone was trying to install an app, and seemed to freeze.
After a few minutes, I forced it to shut-down (power + vol down) and it started to reboot. It got to the G logo with the small bottom bar animation for a number of minutes and eventually kicked back into Recovery mode.
I decided to try rebooting, and it started to reboot, got to the Google logo (the full word, not the "G"), and then kicked back into rebooting.
The phone now constantly reboots and even if I get into fastboot mode, it only stays in fastboot until I hit a key (vol up/down or power) and it then reboots into constant bootloops described above.
If I don't push a button on fastboot mode, it will just start booting anyways after about 3-5 seconds.
Does anybody know of what I could do? Not sure if replacing the battery would help (e.g. a power issue) or if it may be a corruption of the flash memory and that the system and underlying partitions are corrupt leading to nothing I could do to repair the phone.
I have really enjoyed this phone, but I am afraid that this phone is all-but-dead and unusable.
Any assistance is greatly appreciated.
Cheers,
B.D.
Click to expand...
Click to collapse
Are you familiar with how to use commands in platform-tools to flash stock images? How did you upgrade? OTA? Are you rooted? Is it unlocked or Verizon variant? If unlocked, do you know how to unlock the bootloader?
jjlane86 said:
Are you familiar with how to use commands in platform-tools to flash stock images? How did you upgrade? OTA? Are you rooted? Is it unlocked or Verizon variant? If unlocked, do you know how to unlock the bootloader?
Click to expand...
Click to collapse
I am proficient in using the bootloader. Phone has been bootloader unlocked since day one.
I upgraded to Android 11 with ota and all was good for a day (rooted with Magisk canary). Then the phone started acting up, first not booting system and then bootlooping.
I can get into the bootloader (fastboot) but only for maximum 3-5 seconds before the phone reboots, or if I hit any button (vol up/down) the phone reboots. Also, if connected to my computer the USB does not recognize fastboot anymore (before it reboots anyways)
I think it's dead, Jim.
Cheers,
B.D.
To begin with, the device was rooted with Magisk 18.1 flashed about 2 years ago, running stock OxygenOS Oreo 8.1. Recovery: TWRP-3.2.1-1-cheeseburger. Kernel: RenderZenith OP5T [OOS-O-EAS-V3.7.0]. This was the setup I was satisfied with and running in about a year (a total of 2 years).
However, after the first year, I've tried to update TWRP to version 3.3.1-20190908-0-codeworkx-signed-forcedecrypt-dumpling in order to flash and update to the newer OxygenOS Pie 9.0. Something went wrong after flashing the newer TWRP and I couldn't get into recovery anymore... all I saw was a black screen when trying to get into it. I haven't bothered about this since the system booted and worked fine, so I gave up on the 9.0 update and stayed on 8.1. I was able to use it like normal another year. Everything was running very smoothly until a couple of days ago...
The battery has discharged to 0% and the device shut off by itself. 30 seconds before the shutdown, the UI was much less responsive and a popup about the device turning off popped up. I've put it in charge the whole night and when I woke up in the morning... couldn't boot into the system anymore. Instead, the phone booted into the 'broken' recovery, with constant lit of light blue LED (started to lit a couple of seconds after booting, only in the 'non-visible' recovery), and a black screen. I've looked up the fastboot/bootloader keys combination and went into it, well from there, I've tried the turn-off, start, recovery, and bootloader option. Turn off = Off. Start = Recovery. Recovery = Recovery. Bootloader = Bootloader.
The next step I've done was to connect it through a PC and run ADB on it in order to flash the old TWRP-3.2.1-1-cheeseburger. Re-booted into recovery straight after successfully flash and the recovery started to work again. The light blue LED stopped to lit any longer and I haven't seen it anymore. The first thing I've done in recovery was to clear the cache, dalvik, and do a nandroid backup, then tried to re-boot into the system. Finally, it booted into the system and I was happy like a kid when I saw the OnePlus boot animation again, however after putting my password and SIM pin code, I can enjoy it without any issue for about 30-40 seconds before the UI suddenly starts to be non-response (touch doesn't work), the screen starts to flash, sometimes (looks more like turning the screen on and off), until I see a "Turning off..." popup 20-30 seconds later (the battery is fully charged and disconnected from the power source) and the device is rebooting itself into the 'working' recovery. This is how it works each time I boot up into the system now. However, the power button is working and I can turn the screen off and on while the screen/touch isn't responding, the power menu can be opened by holding it (before it's too late and the "Turning off..." popup appears), from there I can choose to re-boot or power off. Magically the touch is working here. If the phone has been rebooted/turned off manually, by hitting either reboot or power off in the power menu, it reboots into the system instead and the same **** happens - not to recovery like it does when the "Turning off..." popup appears and it's turning off by the system.
I'd like to get everything back if possible, at least for one or two days, to back up all data, do some screenshots, back up browser bookmarks, history, open tabs, sms and calls, then give a fresh custom 11 to it.
Any help I can get from you guys? Is there a solution that I could try? What about flashing the newest Magisk onto it? Might it help or rather corrupt it more? Anything else? I'm out of knowledge in this situation and I'm relying on you.