Hi,
I have a 5x not rooted, but unlocked.
It started bootlooping after the N update, but now even after I downgrade to 6.0.1 via fastboot it still bootloops.
when the battery is almost empty it doesn't bootloop for few minutes, but then after connecting to charger it starts again.
I gave it to a technician (before the downgrade) and he gave up.
Any idea?
Thanks!
hardware problem?
I read that downgrading helped some people here, but some say it is a hardware problem.
Is there an official response from LG?
Related
Hi,
I had installed custom ROM developer by @Ziyan 5.1.1. I believe it was AOSP (ROM link) around 5-6 months back. Everything was working correctly.
Last friday night it switched off and since, then it hasn't started up yet. Sometimes the home screen comes but it immediately reboots. It is continuously rebooting and i have to remove the battery from stopping itself from rebooting.
I tried going back to official stock rom 4.3 and used the command fastboot -w flashall and everything happened correctly..atleast that's what it said on the command prompt but it still the phone tries to boot up the 5.1.1 version. It's been a week and i haven't been able to get past this issue. I gave it in the service centre but even they haven't been able to get past the issue.
What issue are you guys suspecting ? Any help would be greatly appreciated !
Thanks,
Adithya
I came back to look here and it is sad to still see phones die this way.. I am sorry dude.. You can try to lock the bootloader and if it is still unlocked upon rebooting the EMMC is fried (internal storage). The only solution is a new motherboard..
I'm stuck and confused:
Had a Nexus 4 and 5 for years. Decided to upgrade this past November to the LG G4 (T-Mobile H811)
Got it to root without touching the boot loader.
In came MM and then I had issues of repeating the process.
I came across a solution, to unlock my bootloader. So I did it and managed to get my G4 rooted while running stock LG MM (H81120i).
Everything was running well for several months, but then I started to see erratic behavior. It would heat-up in my pocket for no reason. It would not save pictures. Connections via WiFi and LTE were breaking up. All in all, I wasn't happy and I missed the stock Google interface.
So I've decided to install CM13. Had many issues of getting it to work for several days, which included persistent closings of Google Play services (and many others) and not being able to make/receive calls (it would automatically reboot) After several different attempts, I managed to get it all working. Cleared/Wiped everything off my internal drive, installed the "LG-H81120i-Flashable.COMPLETE" and "cm-13.0-201605xx-NIGHTLY-h811" and "open_gapps-arm64-6.0-nano-201605xx", all back to back. And then installed manual everything as needed Gmail, Maps, etc.
Everything worked great for about 2-days, until then next morning my screen locked up. Then the phone rebooted. After the reboot, it lasted for about 10-15 seconds in CM13 and rebooted again manually. Continued to reboot over and over, till it then stopped booting with CM13. I thought that maybe I needed to install the latest CM13 zip file, but found I couldn't get into recovery. The first reboot screen, showing "Bootloader State: Bootloader unlocked? and the LG logo would be in a loop. During that time, I could feel the phone getting hotter and hotter.
Sometimes, the phone would boot up into CM fully and last for 5 to 10 minutes. Then reboot again and stay in the first reboot screen.
I managed to get into TWRP recovery and thought that putting back the stock MRA58K image would help. During the install in recovery, the phone rebooted! I never thought it could do that. Eventually I got the stock LG back-up up and running, but it didn’t help, and same rebooting occurred.
I'm stuck and out of options. I would like to get the phone BACK TO STOCK and then perform an RMA. I’m afraid that with the BOOTLOADER UNLOCKED that my RMA will be denied and I’m stuck with what I have.
So can the H811's bootloader be re-locked?
PiCASSiMO said:
I'm stuck and confused:
Had a Nexus 4 and 5 for years. Decided to upgrade this past November to the LG G4 (T-Mobile H811)
Got it to root without touching the boot loader.
In came MM and then I had issues of repeating the process.
I came across a solution, to unlock my bootloader. So I did it and managed to get my G4 rooted while running stock LG MM (H81120i).
Everything was running well for several months, but then I started to see erratic behavior. It would heat-up in my pocket for no reason. It would not save pictures. Connections via WiFi and LTE were breaking up. All in all, I wasn't happy and I missed the stock Google interface.
So I've decided to install CM13. Had many issues of getting it to work for several days, which included persistent closings of Google Play services (and many others) and not being able to make/receive calls (it would automatically reboot) After several different attempts, I managed to get it all working. Cleared/Wiped everything off my internal drive, installed the "LG-H81120i-Flashable.COMPLETE" and "cm-13.0-201605xx-NIGHTLY-h811" and "open_gapps-arm64-6.0-nano-201605xx", all back to back. And then installed manual everything as needed Gmail, Maps, etc.
Everything worked great for about 2-days, until then next morning my screen locked up. Then the phone rebooted. After the reboot, it lasted for about 10-15 seconds in CM13 and rebooted again manually. Continued to reboot over and over, till it then stopped booting with CM13. I thought that maybe I needed to install the latest CM13 zip file, but found I couldn't get into recovery. The first reboot screen, showing "Bootloader State: Bootloader unlocked? and the LG logo would be in a loop. During that time, I could feel the phone getting hotter and hotter.
Sometimes, the phone would boot up into CM fully and last for 5 to 10 minutes. Then reboot again and stay in the first reboot screen.
I managed to get into TWRP recovery and thought that putting back the stock MRA58K image would help. During the install in recovery, the phone rebooted! I never thought it could do that. Eventually I got the stock LG back-up up and running, but it didn’t help, and same rebooting occurred.
I'm stuck and out of options. I would like to get the phone BACK TO STOCK and then perform an RMA. I’m afraid that with the BOOTLOADER UNLOCKED that my RMA will be denied and I’m stuck with what I have.
So can the H811's bootloader be re-locked?
Click to expand...
Click to collapse
Since you live in the US your only option is to apply over voltage to the battery terminal and burn the mobo so that it wont even boot up. The exact method is somewhere around here in xda so you should look it up since you have no other choice
Edit: To answer your question: No
sirsomething said:
Since you live in the US your only option is to apply over voltage to the battery terminal and burn the mobo so that it wont even boot up. The exact method is somewhere around here in xda so you should look it up since you have no other choice
Edit: To answer your question: No
Click to expand...
Click to collapse
If I can't re-lock the bootloader, has anyone had the success of returning their phones under warranty? Through T-Mobile?
I got an H815 on Android 6.0 V20d-EUR-XX. Bought it second hand so I have no idea what has been done prior to me. I'm following the official LG guide on this but when I do "adb reboot bootloader" the phone simply reboots and goes into Android again. Been looking for a solution for the last hour and this is my last resort as I was about to give up. Any help is appreciated. Thank you in advance!
Edit: might have something to do with the phone having previously a bootloop problem that was solved in some devious way?
FIXED! This was a driver issue. After updating the drivers for the phone on the PC everything worked.
Hi, I've met this strange problem:
Yesterday I was browsing Facebook using my Nexus 5X, but it suddenly stuck. A few seconds later, it automatically switched off and failed to switch on any more.
Then, when I switched on the phone, it froze within seconds of the boot process, then automatically switched off or rebooted.
Third-party Recovery not working. Stock Recovery not always working.
Since then I use Nexus Root Toolkit to flash the oldest firmware and the latest firmware. A lot of times. Not working.
Trying to use LG's tot file to recovery, however the LG's firmware update interface also froze within seconds of opening.
During this time only once it managed to boot up, with the earliest firmware (after a fresh firmware flash), when I restart, it went back to bootloop.
Is my Nexus 5X bricked? Any way to bring it back to work?
Thank you guys.
Read a bit. Thousands of threads about Nexus bootlop.
It's a hardware issue, RMA or nothing, it's unrepairable (all methods with heating/ cooling don't solve the problem)
Domin_PL said:
Read a bit. Thousands of threads about Nexus bootlop.
It's a hardware issue, RMA or nothing, it's unrepairable (all methods with heating/ cooling don't solve the problem)
Click to expand...
Click to collapse
I have a hard time believing it just a hardware issue. So many reports of phone working fine until the 7.1 update. Then BAM it bricks a few days later
Sent from my Nexus 5 using Tapatalk
Hi guys. I rarely have to post anything on here as I always find the resolution to my problem. I have a Vodafone UK HTC One M9 and I was rooted with S-off, unlocked bootloader. When the Android 7.0 update was able to be downloaded ota I tried to install it and it didn't work. I assumed it was because I had TWRP recovery installed rather than the stock recovery. I flashed stock recovery back on and then it still didnt work. I can't exactly remember what happened but i ended up spending two weeks trying to recover the phone. I have now S-on and after flashing hundreds of things i've finally got it sort of working again.
The Problem.
It is now running android 7.0 BUT it constantly displays 77% for the battery level and refuses to charge. I have the charging LED but it does not charge. Now the battery has died I can only power the phone whilst it is plugged into the mains. I can get into download mode and android. As soon as I try and load recovery it turns the phone off (allthough I have reflashed recovery).
What have I cocked up? I assume I need to reflash something that controls my battery? The phone worked perfectly prior to this. Any suggestions or advice would be greatly appreciated.
You flashed a stock recovery in a rooted state. That's what you did wrong.
Considering I know nothing about what you've done to it so far I'd say to follow flippy's thread in the general section stickies and return the phone to stock state.
Beamed in by telepathy.