**UPDATE:** so I have managed after many tries to unbrick my phone. So I have unbricked it using kdz method.
No the weird thing is that the phone works fine while in the charger, but when I take the charger off it shuts itself off and starts getting into a bootloop again.
I really don't care any more about my data, I just wanna get my phone normal again.
Any idea what to do?
So I have installed fulmics rom 2 days ago in my phone. At first it seemed great but after couple of hours it started having some problems (when entering the snapchat it just shutdown). It really annoyed me so I decided install a new kernel . I downlaoded xceed kernel and just flashed it and hoped it will succeed.
After that every thing got ****! The device just showed the LG logo and restarted and than showed it again.
I didn't know what to do than I searched a little bit and I connected my device, and using adb sideload transfered cloudy rom(of course I did wipe before flashing it).
After I flashed the room every thing seemed great, it took time and in the setup there was a step where you "restore" you device. (Google service).
I chose the apps I wanted and while it was proccessing it just shut down and again started showing the lg device and restarting it self.
I am really lost, I dont know what to do, I trying ****ing every thing.
Thank you guys.
Same here and still dont know the answer
I'd advice you to read carefully on the rom you want to flash before flashing so you know exactly what to expect. While your phone is busy stuck in bootloop, try connecting it to the charger and let me know what happens.
Related
Okay, I don't know what the deal is but I've now screwed my second device lol
I have a T-Mobile H811 on 10H, my second to be exact, and after I follow instructions for low level root and flashing a recovery, everything works fine! For as long as I stay on that rooted stock image...
The moment I flash anything other than the rooted stock image my device looses sound, becomes extremely slow and unresponsive, with the SystemUI crashing constantly and restarting. Shows lock screen, doesn't respond to touch, and if it does it's only for a brief moment before it freezes and then shows "Optimizing Android", rinse, repeat.
This persists through returning to stock with a kdz. Once it begins, it doesn't stop, which is why I had to return my first device...... and it looks like I'll be returning this one as well :crying:
I am no stranger to the game, I was not on 10N, I made sure to use the right COM port (the diag one), I make sure to only flash things for the H811, so what in the world is happening to my device when I flash other roms? My first device I flashed BlissPop nightlies and thought that might have been the reason, this time I just flashed a modified stock image. I for the life of me cannot figure out what I'm doing wrong or how to undo the damage once it's been done.
I still have access to download mode and TWRP
I am desperate for help... I cannot seem to find anyone else who's had this issue. Missing those Nexus 5 days D:
Thanks in advanced
EDIT: I flashed back to stock and took the 10N update (it was like pulling teeth) and everything seems to be working again... but I'd really still like some insight as to what I did wrong lest I do it again.
And now I flashed Bliss and everything is working just fine... strange
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?
So my brother gave me his old G3 which never turned on again after 1 year or less of use, I believe the problem it had was the LG famous black screen or whatever, I never had a LG phone of my own, but I heard something about it and that it happens to up to the G4 (G5 maybe). I took it to a repair shop and they got it to turn on and make it functional, but it didn't last much longer than a month, it then started freezing completely to the state it's now, which turns on but then it freezes after 10 seconds or something.
I doubt this has anything to do with the software, but still I don't miss anything by trying. So far I've tried installing a custom ROM but there is a problem, it has no recovery nor fastboot installed, I don't even know how this is possible, and I know this is the case because when I try to access any of both I get the LG logo with some white letters on the top left saying some kind of boot security error.
I tried installing the fastboot img through my pc with sdk tools but idk if either the file was corrupted or what but I couldn't make it work (tested multiple I believe), and without the fastboot I can't install a custom recovery.
So I'm hearing any suggestions you guys might have before throwing this phone already.
Hi guys
I have an Lg g3 device unrooted for almost 30 months. Last night when the phone was sitting on the couch, I saw the LG logo and i thought the phone did one of the random surprise. Anyway it didn't load the OS for almost 15 mins. I hard resetted the phone, i deleted everything and restarted. Then i had Android is starting and Applications are optimizing. I got the Setting section. boom phone restarted again and bootloop again. I took it to download mode, i had a clean installation with the recent official KDZ. and again optimizing, then boom again. The phone only passes the loading phase if i hard reset it or just flash the original KDZ . I select the language. Network option. Restarts. I tried 3 batteries. No luck. All batteries are working on other phones.
Any idea how i can fix it? I dont mind rooting the device. I need the device for 2 weeks. then i would be upgrading to another phone. I am going nutz. Please help!
I picked up my UK V30 H930 yesterday all fine and saw that LG have unlocked the bootloader on my model so I went ahead and tried it along with trying the alpha TWRP build
So I thought id write about what went wrong and how I recovered from it.
I made the mistake of letting the phone auto update to 10v software verion before I did this. As I had 10f on before when I bought the phone.
I went to load in all the software needed to unlock the bootloader and proceeded to do so but in my haste of the user data being wiped taking a longer then I thought it would I unpluged the phone to try "fastboot flash unlock unlock.bin" again . No such luck already unlocked. It booted back in fine so I thought everything was ok but that was the moment I thought could have caused my entire night to be ruined.
I thought with the bootloader saying it was unlock it was now fine to flash TWRP on now so went to do that and discovered it would no longer boot into the rom anymore coming up with the LG V30 Logo and just staying put. Thought it must be my 10v software version messing it up. Ok ill try to flash a 10f stock kdz. After about an hour or so of 'Finding my feet' with the phones boot methods for download mode, Fastboot and recovery I found that twrp was being strange with mounting the phone tried otherways eventually got the phone talking to the pc by using uppercut with LGUP and having the phone in download mode and the port com channel in device mananger set to com 41. After about 4 tries of flashing KDZ's to the phone it would just come with a "erasing" circle and proceed to get stuck on boot logo again so I messed about with .dlls and tried to other methods. Still nothing.
Now I tried LG Bridge's "Update error recovery" and I was actually talking to the phone for the 1st time so i let it do its thing which took well over an hour to download the kdz file. "Fine just work please". it got to the updating stage at 5% and froze and the phone being in download mode hadnt done a thing. I tried again but still nothing. Eventually now at 6am and having been up all night I went to give up but I manged to get it on to fastboot mode and by chance came across "flashing lock_bootloader" tried and it and it locked tthe bootloader back up (this thing of LG saying it cannot be undone must be rubbish?) now before I tried anything I rebooted the phone . IT BOOTED! onto the fresh 10v KDZ i had installed on it but before anything I wanted to see if it would now run with a unlocked bootloader on its own with no TWRP installed. It works! Now i just need a method of rooting but im now ready at least.
Hope this helps anyone with simular troubles.
Also had some trouble yesterday after trying out some Magisk modules.
On reboot it sometimes got stuck in the LG V30 screen, and sometimes even the bootanimation came up, but it didnt finish the boot lol
Only installed and adblock btw, and tried the Xposed module. Uninstalled that again btw. Now only using Adblock.
Phone also seems to need Power + Vol- to force shutdown for me, not only Power like other phones. Also didnt manage to find a way to boot into recovery when the phone is off, only found a way to get into the factory reset screen ?
sadly i dont have a working sdcard currently (my 3 year old 128GB one is read only for some reason, atleast changes dont get applied), so ill wait for a new one to mess around more ^^
Also working on a LOS14.1 build atm (it compiled, but didnt adapt all parts of thr device tree yet, and no idea if i have all vendor files lol)
SGCMarkus said:
Also had some trouble yesterday after trying out some Magisk modules.
On reboot it sometimes got stuck in the LG V30 screen, and sometimes even the bootanimation came up, but it didnt finish the boot lol
Only installed and adblock btw, and tried the Xposed module. Uninstalled that again btw. Now only using Adblock.
Phone also seems to need Power + Vol- to force shutdown for me, not only Power like other phones. Also didnt manage to find a way to boot into recovery when the phone is off, only found a way to get into the factory reset screen
sadly i dont have a working sdcard currently (my 3 year old 128GB one is read only for some reason, atleast changes dont get applied), so ill wait for a new one to mess around more ^^
Also working on a LOS14.1 build atm (it compiled, but didnt adapt all parts of thr device tree yet, and no idea if i have all vendor files lol)
Click to expand...
Click to collapse
Ive just managed to get 10f on so ill retry flashing twrp now.
Are you sure your sdcard doesnt have a little read/write switch on it . Im sure i remember so of them used to have one.
Dreamxtreme said:
Ive just managed to get 10f on so ill retry flashing twrp now.
Are you sure your sdcard doesnt have a little read/write switch on it . Im sure i remember so of them used to have one.
Click to expand...
Click to collapse
nope, doesnt have one. Neither windows nor Linux fail at writing on it, or when deleting files, but as soon as I re-insert the SDCard all changes are reversed. Formatting doesnt work anymore, unknown error. Tried that in Windows, Linux and in the Phone (Androids formatting crashed, TWRPs produced an error after it timed out)