I am trying to understand why a particular LG G4 is hanging during boot.
Previously, LOS 14.1 (7.1.2) worked fine, with no notable problems. The phone would sometimes get warm during use (primarily when location services were active), but this seemed to be manageable.
Then, the battery was accidentally allowed to discharge to zero. After the battery was recharged, the phone became unable to boot past the Lineageos "bubble on a string" animation (first bubble). The animation of the first bubble simply continues forever.
The phone can boot to TWRP, fasboot, download mode, etc.
I am looking for info on how to retrieve the logs produced during boot so that the problem can be identified.
I tried attaching to computer and launching "adb logcat" during animation, but the device is never found. If I remember correctly, "USB debugging" was off when the device died. (ADB does work in TWRP.)
Further information here: https://forum.xda-developers.com/t/is-this-ilapo-or-something-else-g4.4211343/
Related
Closed now.
To try and give you more information, since I'm trying to help an older friend with her phone, I'll list down everything I've noted and seen so far, and then describe the hours of attempts I've followed online to try and get this working.
Product name: Tuna
Variant: maguro 16GB
HW Version: 9
Bootloader: Prime LC03
Baseband: I9250UGLL1
Lockstate: Unlocked.
TeamWin Recovery Project v. 2.6.0.0.
Onward to the issue. Apparently an associate of hers said she needed to update her phone, and did it for her. Since that point, her phone has gone through two different loops, as far as I can tell.
One: You can access TeamWin Recovery Project.
There are no recovery files, factory reset does not work, there are folders under the command terminal but none of them are the ones from the guides/threads made similar to this issue.
[Wipe/Restore/Reboot/Fix Permissions - None of them work.]
Two: You can access Fastboot Mode, where you can select 'reboot bootloader' or 'recovery mode'. Both take you back to the 'google logo' for a while, where the former just stays there forever, and the latter takes you to TWRP.
I've tried 'Hard Reset' as it's described in several guides, which for the most part seems to be the same as 'Factory Reset', which I've definitely tried. I could be too much was deleted before she even gave me the phone, having clicked around on the phone first beforehand.
Figuring this might be the case, I turned to the Nexus Root Toolkit, v2.0.5, developed by WugFresh.
I unlocked, I have never plugged a phone into this laptop (so no previous drivers to conflict), I clicked the soft-bricked/bootloop option and moved on through that command menu, leaving the phone on the screen with the green 'help android' as instructed.
However, the 'Fastboot device was not found'. The computer can't find anything resembling a phone, samsung, or google, or the model number, under the Device Manager menu, so I can't update the driver, or apply a universal driver, because apparently the computer can't detect the phone in the first place.
So, if the wise people here could kindly help, the list of problems follows in short form:
- I cannot get the device to access any information beyond the TWRP or Fastboot mode; none of those options seem to work.
- I suspect the OS is gone, which would explain the previous problem.
- I cannot get the computer to recognize a phone is connected at all. It tells me I have nothing plugged into any usb port. The phone is charging, however.
She's a very sweet lady and I would really like to get this fixed for her, even if until today I've never even heard of half the problems I've read about.
What other information can I provide that you might be able to help me with? I can provide links of directions I've followed?
Dear Nexus 5X users,
I would like to share my success story to booting up the bootlooped Nexus 5X. My phone was bootloader locked when the bootloop happened. After searching threads for hours, I found out I had to unlocked the bootloader. And the only way to do that is to go to the developer's option and change the OEM bootloader setting. But, it seems impossible to do that when I am having the bootlooping.
From one of the thread, I saw that one person used a hair dryer to heat up his phone, then the phone booted up normally. So, I also tried to heat up my phone. Following is how I did that. It only took ~10 minutes.
I put my phone on top of my electric radiator. The phone has a cover, so it kinda helps not to burn my phone. After 5 min later, I turned on my phone. It rebooted 2-3 times, then magically it booted up normally. So, I quickly activated developer's option and switch on the OEM bootloader unlock option.
Now, I just installed TWRP and one of the 4core kernel. It is booting normally. I hope this is helpful for someone who is in my position.
If this is not an appropriate new thread, or there is a better thread I can post to, let me know.
Man, I am in a somewhat similar situation. Was running PureNexus ROM, when suddenly got BLOD. In my desperation, I wiped data clean as soon as it booted into TWRP after a million tries. Now device won't go beyond Google logo, and the bootloader (fastboot) mode is not being detected in PC
I tried all driver installation methods, but the culprit is incorrect device ID being shown to my PC - USB\VID_0000&PID_0002\5&ECB7860&0&9 (unknown usb device - device descriptor request failed)
What do I do? I can heat up the phone but will have to continue doing it till the first boot after data wipe finishes, which can be like 10-15mins, which sounds risky.
UPDATE:
My situation was peculiar, because I had wiped the /data partition when the device was already bootlooping (managed to boot into TWRP after cooling the phone and wiped /data in my infinite wisdom). After that, I was still stuck in BLOD, except one change - PC was no longer recognizing the device in fastboot (see the hardware ID I mentioned above).
How it fixed it:
Removed the case, and heated up my phone with a hair dryer for 5min
Booted it up, it was stuck on Google logo for a fairly long time before bootlooping, as compared to earlier. My guess - it was trying to load system files, which wasn't happening when the phone wasn't heated up.
Now I booted into bootloader and PC was able to recognize the device in fastboot mode.
Finally I was able to flash the moded boot.img files to disable bigger cores and my 5X is back to being my daily driver.
Hello, I would like to first tell you the story my LG G4 has gone through and then I tell you the error.
So, at first my phone was working absolutely properly. I accidentally deleted some pictures and to do a recovery, I had to root it. And rooting would be useful for later so why not do it?
So I first unlocked the bootloader through the code from the LG site. After unlocking, the phone reset (because it would be just too good to make some memory changes and nothing more.) But allright. Then I was ready to root. I just booted the phone, everything was fine. I unlocked the developer mode and opened ADB. I rebooted to recovery through
Code:
adb reboot recovery
I was expecting to see some menu with buttons (but that would be just too good). However, I saw just android with a red triangle in the middle. Nothing more. No response to buttons, nothing.
So I thought. Allright, let's boot into recovery using hardware buttons (vol down + power) at startup. Unfortunatelly, it seemed like there is no such mode System just normally booted (and that was just after bootloader unlocking. Recovery mode goodbye.).
I tried to send commands to the phone using diagnostic port. Unfortunately, it responded by FAIL to every command.
I reboot to bootloader and booted an image: "boot-em.img" (from here: google: how-to-root-lg-g4-on-android-6-0-marshmallow-20a20b-firmware. I'm a newbie here. thx for understanding.)
After that the console uploaded the image and booted successfully. Then, however, system started to boot up and was endlessly booting (LG boot animation) till the battery was critical.
I was able to access the EMI number through volume-down button and volume-up button pressed simultaneously.
I was also able to access some factory-reset dialog by holding volume-down and pressing power-button several times. I choosed to reset everything and then accepted it with one more 'are you sure dialog'. System rebooted and was stucked in the LG boot animation.
Then I got to download mode, since recovery mode was lost in hell. Through LG-UP I flashed the original KDZ firmware and everything got back to normal, but recovery mode was still inaccessible through the hardware buttons. I got through the process of setting everything up, getting developer, rebooting to bootloader and I booted TWRP.
TWRP loaded and it responded to double-tap on screen to wake it up. I just checked the menus and let the phone sleep.
After several hours I went back to the phone and double-tapped on display. Nothing. Phone was not responding. I pressed the power button and the phone restarted (I think. It either restarted into the system or was not responding to power button.)
So I got to the system and again rebooted to the TWRP (through fast-boot). I tried to back-up one partition to the disk. During the process phone had turned the display off. So I double tapped. Nothing. I removed the SD card and the phone woke, saying that back-up process was not able to complete. Suddenly it stopped responding to double-tap. It woke up through an interrupt. I re-inserted the card, successfully backed-up the partition to the SD-card and I left the phone laying on the bed plugged in the charger. It stayed that way for 4 hours or so, doing nothing. All of a sudden, a yellow screen was there, (and that's a screen of absolute death that was never supposed to come. Little I knew.) saying that an unexpected critical error happened and to do a memory dump, insert a cable, set up some communication (I don't remember what it was, didn't take a picture of it.) and it could send the memory dump to PC or somewhere. I thought to myself. So, the application is not so stable after all. It said that to reboot just press the power button or something.
And now the problem comes:
The first start: Bootloader booted, LG animation went on and finished. The starting up apps dialog came rolling. Then, system restarted.
The restart: Bootloader booted, LG animation went on and freezed. Then, the phone restarted.
Second restart: The same thing as the first one.
Fourth restart up till now: Bootloader tries to boot and restarts before the LG animation.
I got to download mode and it restarted even there. After re-inserting the batterry I can sometimes get to the Firmware Update window and communicate. There I flashed the official firmware again.
No success, as if I didn't even do it. It restarts before the animation.
Can I do anything with the phone? Hopefully I can. No hardware problem occured (except for a situation where the error could fry the wires inside the mighty System On Chip.)
For the software state I cannot even tell but I might say it's cooked just wrong. That's why I came here.
I know I did some pretty stupid steps. But the error was not done by me. It worked fine and after the yellow screen which came by itself, it just (some bad words).
Thanks for replies.
Phone: LG-G4 H815, European market
Solution
So, I was looking around and believe it or not, this problem disconnected the pins on the motherboard's snapdragon 808.
I think this happened: The device, although it was heated many times during its life, it withstood that so far.
However, a longer run of the TWRP had finished it off. Memory got disconnected while running and it threw a yellow-screen.
Pins got disconnected and from then on it was just a standard common LG bootloop issue.
The continuous process of dying (First it partially loaded, then only animation, then nothing) is explained by this fact that the pins were so-so there and a couple of reboots just got it totaled.
Temporary fix:
Pre-heated the memory chip to 250°C using Hot-Air gun. After 18 seconds at this temperature I pressed the memory on top of the snapdragon down to the board while cooling.
Then I added a little metal square on the metal part that is covering the system on chip. This part is over the SOC where before there was just some tape.
This can work for several days in sleep mode or a couple of 'heat-demanding' operations on the phone.
Permanent solution should be to reball the memory chip on the snapdragon. That's my next step.
Just spent hours on a stock AT&T G2 getting root, using Autorec to flash TWRP (twrp-2.8.7.0-d800), and finally using TWRP to wipe and then flash LineageOS 14.1 (lineage-14.1-20180516-nightly-d800-signed) and GApps mini (open_gapps-arm-7.1-mini-20180517). Rebooted afterwards. Saw the usual LG logo, followed by the LineageOS boot animation. All seemed well! Until the boot animation kept going... for over 8 hours.
I can hold the power button to restart. I can access "hardware key control mode." Nothing else. I've spent hours trying every conceivable Vol+/Power/Vol- combination and I can't access anything else. No recovery, no reset mode, nothing.
When I try to access download mode using Vol+ and plugging into PC, it only shows a battery charging screen with a yellow LED.
Although the PC does make a standard "USB device connected" sound if it is connected during the LineageOS animation, it doesn't show up in device manager other than as an additional item under "Human Interface Devices."
I've been poring over every XDA thread and google result i can find but nothing that works for me. The only person I've found in the same situation is here: https://forum.xda-developers.com/lg-g2/help/d802-bricked-lineageos-14-1-installation-t3587653 and they don't seem to have found a solution.
If anyone can help I would appreciate it immensely!
I'm really anxious and nervous about this so I'll simplify this as much as I can; recently my phone was turned on on top of my desk and randomly restarted. I thought little of it, as it quickly went through the OnePlus logo (it began to take longer the second time I restarted it) and Android splash screen, but then stopped on the circles animation and remained looping there. I have very important data on it that I'd like to recover and WILL NOT factory reset (flash) my phone.
The battery icon and percentage still show up when I plug in the device. I still have access to Recovery Mode, Fastboot, and Sideload through their key shortcuts. I previously had USB Debugging enabled but can't authorize ADB since I can't check the confirmation dialogue box (shows up as "unauthorized" in command prompt). I had very little storage (less than 250mB) for the last few days. I don't have root access, custom recovery, or an unlocked bootloader.
I already tried clearing my cache; if I restart after doing so it only takes a few seconds to pass the OnePlus logo as opposed to the ~20 seconds it previously took. This delay raises every few restarts. I've tried waiting many hours to see if anything would happen or if ADB would start functioning. I also tried fully draining my battery overnight and nothing happened. My files are not deleted/fully corrupt since I could still see them when flashing through internal storage from Recovery Mode. OnePlus chat support said I have to flash my phone and Twitter support refused to respond. Local data recovery centers said I could get my phone shipped to them for a free diagnostic, should I do so or is there a way to unbrick or recover my data at home?
Is there anything I can do? Thank you very much!... for now I'll just remain depressed...
TL;DR - My phone's stuck at the circles boot animation and I want to recover my files or fix the soft-brick without resetting. I don't have root access, custom recovery, or an unlocked bootloader.
UPDATE: I boot into Recovery Mode and "Reset System Settings"- my phone rebooted with 112 gigabytes of storage already taken up and all of my Android/data folders empty! I lost very little as I set my save folders to other locations! It looks like the error was not having enough storage! OnePlus chat support said that I had to factory reset my phone, DO NOT listen to them! MY PHONE IS UNBRICKED!
Check out other responses:
https://www.reddit.com/r/Oneplus5T/comments/ahfabg/data_recovery_for_softbricked_oneplus_5t/
https://forums.oneplus.com/threads/data-recovery-for-soft-bricked-oneplus-5t.986096