Hey guys long time lurker here !
I'm experiencing an issue with my G4 h815 currently with AICP (rev from around April) and TWRP (from around January 2017).
Since the last update of AICP I did (so back in April) everything went fine with the phone.
I did nothing weird with the phone (haven't installed an app for months, neither droped the phone or whatsoever)
It suddenly froze while I was browsing Chrome, then bootlooped 2 times, couldn't get past the "swipe to unlock" thingy.
I then decided to get into recovery mode with PWR+Volume down buttons => "do you want to erase blabla ?" => YES => "Are you sure blabla" => YES.
The "TeamWin" logo from TWRP appeared once, phone bootlooped again, and until then it just freezes after the second "YES" when I try to get to recovery mode and then bootloops again.
Obviously this crap happens when I'm far away from home (and for a long time) so I installed drivers / ADB stuff on my laptop but I can't get the phone to be recognized by win 10 in any way. ADB says : error: device '(null)' not found
I'm a bit lost right now, any thoughts / keywords that could help me getting sorted are welcome !
Many thanks in advance,
Fosco
Ok I managed to go a bit further ... discovered about the download mode thingy (Vol UP while plugin it to computer).
I installed LG UP, picked a KDZ file here.
I was then able to "upgrade" the phone with the stock rom : Complete success from the process perspective. It then froze on the basic LG logo. I removed the battery, entered recovery mode, reset worked, phone went back alive => "android is preparing apps, etc" but then it rebooted and froze again on LG logo.
Am I missing something ?
EDIT : Tried LG Bridge method aswell ... can't get it to go further than boot ... still freezing on the boot screen
Went ahead, disassembled the phone and heated the CPU ... looks like it needed it-ish.
I am still stuck on the LG logo, but atleast now I have the green android guy having his belly "moving stuff" and the blue led is glowing :laugh:
Nah seriously this is getting annoying ... IDK what to do next ... Cure it with lawnmower ?
Related
Hello, first I'd like to thank you for your time reading this.
Note: I've searched the forums a lot, even for other LG Devices (G2 for ex) but I couldn't find a solution.
Trying to flash CM12 by _infected (amazing rom, working as a daily driver on my other lg pad btw) and messed up something on TWRP.
-First trying to do a Factory Reset via TWRP gave me "failed to mount /data" and "/system" I rebooted and the device went straight to TWRP Recovery, I rebooted again, this time making sure I selected "Reboot to System" and it went again to TWRP Recovery...
- I did another wipe, this time wiped everything (all checkboxes in TWRP), reboot and... no boot...
Now my LG Pad is at the following State:
- Black Screen (No LG Logo)
- Connecting USB to Windows gives the "connected sound"
- Adb doesnt find device (driver was installed and working).
- Device Manager "refreshes" on USB plug but doesnt show the device (or I can't find it?).
- Holding Power on the tablet while USB plugged to Windows gives the "disconnected sound" -> "connected sound" -> "connected sound".
- Can't boot into Download Mode.
- Can't turn off the Tablet... only Reboots holding Power key.
Please? Any help?
What can I do?
Is warranty void at this point?
Thank you very much for any help you can provide.
I have a G pad in the same situation, and I wasn't able to fix it. I managed to pick up another cheap one, but I'll follow this thread in case you get an answer.
You have to find a way to get it into download mode or you wont be able to fix it with LG Tool
What did you mess up, and how did you install twrp ? Also what twrp version abd base.
mekoneko said:
What did you mess up, and how did you install twrp ? Also what twrp version abd base.
Click to expand...
Click to collapse
For me personally, I assumed it'd be as easy as the twrp page makes it out to be , or my nexus 4 was, so I just went for it. I ran into that secure boot error with twrp, and rebooted back into stock. There was an OTA update, so I did it (stupid I now realise) and that bricked it on reboot. It won't turn on at all. If i plug into USB on a computer it OCCASIONALLY brings something up on the screen, the LG logo I think or something, but I cannot for the life of me get it into download mode. It's at home right now, so ic anot remmeber the exact thing it shows on screen, but almost certainly not download mode, and none of the hardware buttons seem to be responsive for doing factory resets or download or anything.
I managed to send the LG G Pad to warranty and got a new one... Lucky me...
Guess that if we can't get into DL mode they can't either.
However after much investigation I've realized that the problem was a corrupted system partition...
I have an Asus ZenFone 2 4/64 w/ a 128 gig card. In the middle of watching a YouTube Video, the screen stopped responding to touch. However it would respond to Google voice commands. I restarted it a couple of times with no luck. I then tried to boot into recovery mode and it gave me the android guy with the open stomach and an error message. I then tried to use Asus PC link and was able to navigate the phone that way. So I decided to do a factory reset. Now I have the android guy with the open stomach with his guts turning around and it says erasing. It has been like that for at least 20 minutes. I know it doesn't take that long to reset the phone and whenever I reboot it, it goes right to that screen. Also, on the initial screen when you boot into the system, it says that my bootloader version is unknown, the HW variant is not listed, and the "signing" and "secure boot" both have question marks next to them. Someone please help ?
when you see dead android guy hold volume up and press power button see of that works.
Hey everyone,
I did something really stupid while trying to get a certain app to recognize a codec that it needed in order for it to work and seem to have probably bricked my phone.
Phone Details:
LGH812
Lollipop 5.0.1
rooted
I went to /system/ and renamed lib64 to lib64bak because I wanted to put some new files in there. This caused the phone screen to immediately go black and unresponsive. I took out the battery and re-inserted it. The phone boot logo with LG comes up and then it goes to a black screen with the dead android guy with red triangle and the exclamation mark. No other text is present in this screen. Stays at this screen for about a minute and reboots only to go back to the exact same screen.
Things I have tried:
1.) I tried to boot into download mode (power+volume down) still goes to the aforementioned screen.
2.) Got LGUP to recognize the com port once, but it shows up as unknown and won't let me proceed with a fresh wipe/install
3.) Tried the LG Flashing tool, couldn't even see the com port.
4.) Tried the WHQL universal drivers as well as the specific device drivers with no advancement.
What I believe is happening is that it's trying to boot properly initially, but it can't find lib64 folder so it fails to launch the os and then tries to go into recovery due to error, but fails to go to recovery also because of lib64 is missing.
If anyone has any ideas/things I can try to get it into recovery or download mode or if anyone has seen this state before and was able to fix it please let me know.
Thank you all for your time!
I enrolled in the Beta Program, and upgraded to Android O. Everything was great! Until I rebooted, things were acting funny. I have played with enough nightly builds and custom roms to realize, I need to factory Reset.
Bootloop.
I was able to get into the recovery mode: and then did another factory reset from here--
Now my recovery mode is only, "No Command" Vol up + power did not get me a list of options again
So, I followed this guide: https://forum.xda-developers.com/nexus-5x/help/guide-fix-bootloop-locked-bootloader-t3608679
I got here: "click on all buttons and flash all partition files from extracted archive - except recovery ,userdata and cache."
And still was boot looping
So, I went to this guide: https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Installing the "LGUP_8994_DLL_Ver_0_0_3_23" Looks rather uneventful.
But, I booted up with Vol UP+Power
and got to the Firmware Update screen.
It's been sitting at 0% for twenty minutes... "Do not unplug the USB connection until the process is completed"
and "LG USB driver installation is needed before starting LGUP"
and I will need to close my laptop in an hour
Im lost
Edit:
Okay, I got the LGUP to install a new TOT file--
LGH791 - resulted in freezing on "google" after reboot
LGH790 - also frozen on "google" after reboot
However, my recovery mode is no longer "No Command"
So I'm going to try to Sideload an update
I Has an operating system! I'm going to update my firmware to 791 now
hmm.. .no option for "BIN" so I'm going to leave it-- i was supposed to go an hour ago
[Follow-up] My sensors were "malfunctioning" with LGH790. Upgrading to LGH791 fixed all of my sensor issues.
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.