I think I now understand my mistakes, but I'd love to hear it if there's a way around this. I have the International version H815. My plan was to end up with a rooted version of Marshmallow. At the beginning of the day, I was not so clear about the difference between unlocking and rooting. I followed directions to install a rooted version of Lollipop. That went well. I flashed TWRP but couldn't figure out why that didn't work until I figured out that the bootloader should have been unlocked first. I then went through most of the steps to officially unlock the phone, but my phone just hangs at a fastboot intro screen using the abd reboot bootloader command, so I can't use the fastboot utility to recover the device ID I would need to get an unlock code. And I can't get into the original recovery menu using the power-volume down keys. I think I overwrote the stock Recovery utility when I flashed TWRP from within a rooted system. Switching back to a stock kdz didn't help. The phone still works fine otherwise, but now I see no path to unlocking it and then installing TWRP to load a rooted 6.0 image. Should I just give up now, or are there any other options?
Thanks,
Jim
Got it working
I reinstalled the rooted image and flashed a stock recovery.img. That didn't work. Then I went back to stock with a different kdz image. I still couldn't access the recovery tools with the power and volume down buttons, but I was a able to get fastboot functioning and got the unlock code from LG and entered it - now to see if I can go back to an unlocked system and install TWRP to upgrade to Marshmallow.
So I followed all the right steps to getting the bootloader unlocked, installing TWRP as the custom recovery and installing SuperSU root. Now I'm stuck in a bootloop with no way to access the bootloader from ADB... Hardware access to the bootloader doesn't work. I get the bootloader unlocked notification but then it goes straight into boot. Windows recognises that there's a device there but I can't access the files and see it in adb... Feeling very lost with this
I had a similar issue. TWRP installed correctly, flashed SuperSU. Unable to boot - phone stuck on the initial splash screen.
In the end I had to us LGUP to flash a suitable KDZ file and resurrect the handset. Read more about it here: http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Curiously, I have greater success using adb and fastboot on a Mac than I do on Windows 10 from which Fastboot resolutely refuses to communicate with the phone.
Has anyone successfully put a custom ROM on this device? I used to have an old Samsung S3 where I was able to put on CM and it was a piece of cake, but with this tablet I'm having issues with the bootloader being locked.
So far I've tried to install TWRP, CWM, and Philz custom recoveries. The problem seems to be with the versioning. Everything is customized for the v500. I was able to install Philz_Touch_recovery_V490.img which allowed me to boot into some sort of 'fastboot' recovery mode when before I would just get the message: "error boot certification verify" on start up. This fastboot mode isn't the Philz interface and it doesn't give me the option to back anything up or boot a ROM. It doesn't really give me any options except to restart, restart bootloader, or power off.
Were you on Lollipop or Marshmallow before you bricked it? (Which one?)
Lollipop.
The device is not bricked as I am still able to access the stock ROM. I just never was able to access my boot loader. I keep getting the error message "Error: boot certification verify" My carrier is US Cellular and they tend to lock a lot of features on their device. Is it possible they blocked boot loader access to be assholes?
BTW, my device is successfully rooted. (I checked with a root verify app.)
I'm looking into implementing the loki-master hack to unlock my boot loader and hopefully then Philz recovery will work as intended. (It is the only custom recover option that didn't give me an out-right failure message). This does seem to be an advanced developer tool requiring some code skills. Anybody have any tips for this Loki procedure?
BossRoyce said:
Lollipop.
The device is not bricked as I am still able to access the stock ROM. I just never was able to access my boot loader. I keep getting the error message "Error: boot certification verify" My carrier is US Cellular and they tend to lock a lot of features on their device. Is it possible they blocked boot loader access to be assholes?
BTW, my device is successfully rooted. (I checked with a root verify app.)
I'm looking into implementing the loki-master hack to unlock my boot loader and hopefully then Philz recovery will work as intended. (It is the only custom recover option that didn't give me an out-right failure message). This does seem to be an advanced developer tool requiring some code skills. Anybody have any tips for this Loki procedure?
Click to expand...
Click to collapse
I would doubt if you could still use the Loki method on a stock LG Lollipop ROM. For example, LG patched the Loki exploit on the VK810 LG G Pad 8.3 as of KitKat, and Lollipop on this device can't even boot the ROM using the old bootloader - it requires the Lollipop bootloader. In our case, the exploited bootloader can be temporarily reflashed to get into TWRP, but then we have to reflash the Lollipop bootloader to boot the ROM again.
sorry bring up old stuff
so i was able to root. have su i bcked up stock recovery and basicly any recover i flash i get the boot error but also gets fastboot.
ofcoarse ive tried most common commands and she wont reconize any of them.
im a long time lg user and thinking that this old of a sytem needs to be bumped like g3
att has always had a strictly locked bootloader state
Help oem unlock m8
I am currently trying to unlock bootloader on Lg gpad f 8.0 v495. At&t I follow all steps until enable oem unlock in developer options.. this option is missing in my developer options.. anyone know why or how to fix this or can I proceed without it. Help please.
BossRoyce said:
Has anyone successfully put a custom ROM on this device? I used to have an old Samsung S3 where I was able to put on CM and it was a piece of cake, but with this tablet I'm having issues with the bootloader being locked.
So far I've tried to install TWRP, CWM, and Philz custom recoveries. The problem seems to be with the versioning. Everything is customized for the v500. I was able to install Philz_Touch_recovery_V490.img which allowed me to boot into some sort of 'fastboot' recovery mode when before I would just get the message: "error boot certification verify" on start up. This fastboot mode isn't the Philz interface and it doesn't give me the option to back anything up or boot a ROM. It doesn't really give me any options except to restart, restart bootloader, or power off.
Click to expand...
Click to collapse
can you point me to the files you used to root the device.
THank you
Lg g pad f 8.0 v495
I rooted with kingroot apk but make sure you use kingroot version no higher than 4.5 . Because you are going to want to use SuperSume to replace kingroot as superuser it runs alot smoother. And for some reason any version higher than 4.5 of kingroot the supersume always freezez u. Hope this helps. If u get time pm have a question totally unrelated to the g pad but could use some help.
have vibe shot z90a40. android 5.1.1
1.i tried to root with kingroot, kingoroot, iroot etc, didnt work.
2. cannot unlock bootloader. when tried minimal adb and fastboot cannot reach bootloader or start in fastboot. when i use 'adb fastboot-bootloader' it hangs on the logo on restarting.
Although 'adb fastboot recovery' command works.
3, Tried vol down +power. it takes phone to service menu something (0 to 14 0. Board test 1. Current Test 2. RF test etc)
i have enabled developer options OEM UNLOCK AND USB DEBUGGING (maybe oem unlock feature isnt working, i read somewhere)
Actually i am trying to flash with another rom S363 marshmallow (internatinal rom for this phone only).
i want to backup my present rom so i want root and twrp.
i read steps of flashing on the forum WITHOUT UNLOCK i suppose with QFIL.
Dont want to take risk of bricking without unlock.
plz tell me how to unlock bootloader, custom recovery install and root as nothing else works.
please help me.
Hello guys I have H815 and I can't proceed with unlocking bootloader cause my phone cannot boot into bootloader/fastboot mode. I'm not newbie, but with this phone everything goes ****ing different than in instruction.
I the instruction there is adb reboot bootloader. Of course my phone is seen in adb mode but after this command it just reboot to system. I tried also key combinations with no luck...
What to do?
My system is android 6
remialfa said:
Hello guys I have H815 and I can't proceed with unlocking bootloader cause my phone cannot boot into bootloader/fastboot mode. I'm not newbie, but with this phone everything goes ****ing different than in instruction.
I the instruction there is adb reboot bootloader. Of course my phone is seen in adb mode but after this command it just reboot to system. I tried also key combinations with no luck...
What to do?
My system is android 6
Click to expand...
Click to collapse
Hi,
I'm the same...
looking for solution I found this on Youtube:
Pratically, you have to press vol up while connect USB on PC....
I haven't the G4 with my today and so I cannot test if this is a valid mode...
If you do this, let me know if you can enter in fastboot mode
auceto63 said:
Hi,
I'm the same...
looking for solution I found this on Youtube:
Pratically, you have to press vol up while connect USB on PC....
I haven't the G4 with my today and so I cannot test if this is a valid mode...
If you do this, let me know if you can enter in fastboot mode
Click to expand...
Click to collapse
I did that and yeah it entered this mode but it's not valid bootloader/fastboot mode. It's some service mode to update firmware. Anyway it's not visible in pc as a normal fastboot and I cannot proceed further with unlocking bootloader...
Edit: it's download mode... So as I said it's not fastboot mode.
Anyone can help?
Seriously nobody? I thought this phone has good community and support...
I'm facing the exact same problem with my H810 on 6.0. Sick of not being able to root atleast.
Seriously hasn't anyone on earth found a way to boot this **** in fastboot? I mean there are a number of tutorials but everything goes different as F*** with this thing. Hope someone will update with good news. :fingers-crossed::fingers-crossed:
charith262 said:
I'm facing the exact same problem with my H810 on 6.0. Sick of not being able to root atleast.
Seriously hasn't anyone on earth found a way to boot this **** in fastboot? I mean there are a number of tutorials but everything goes different as F*** with this thing. Hope someone will update with good news. :fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
You can check out UsU. That is an unofficial bootloader unlock
ThePiGuy said:
You can check out UsU. That is an unofficial bootloader unlock
Click to expand...
Click to collapse
Thanks yeah I checked but that's for ARB<=2 devices. I forgot to mention earlier this godforsaken thing is ARB3.
I have an H811 (T-Mo) running firmware H81120p, ARB3. Doesn't seem to be much that can be done with it as far as rooting. It also has no stock recovery, only boots to system.
you did follow this official guide right? it unlocked mine after a few angry moments
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
use minimal ADB https://forum.xda-developers.com/showthread.php?t=2317790
Only way to boot twrp later is to use fastboot with ADB, recovery with buttons doesn't work.
if the device wont boot a rom use adb to get back in recovery.
if you use bank apps, install magisk before installing rom, do not get SU
samadee3 said:
you did follow this official guide right? it unlocked mine after a few angry moments
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
use minimal ADB https://forum.xda-developers.com/showthread.php?t=2317790
Only way to boot twrp later is to use fastboot with ADB, recovery with buttons doesn't work.
if the device wont boot a rom use adb to get back in recovery.
Click to expand...
Click to collapse
Only problem is that the info linked to above applies to ONE G4 variant only - the H815 international model. The rest of us are SOL. The bootloader on US carrier G4 - AT&T, T-Mo, VzW, etc (most later firmware revisions for G3 as well) models has been nailed down. The only exception is a G4 with ARB <= 2 can be hacked with UsU in order to root it and install a custom recovery.
SofaSpud said:
Only problem is that the info linked to above applies to ONE G4 variant only - the H815 international model. The rest of us are SOL. The bootloader on US carrier G4 - AT&T, T-Mo, VzW, etc (most later firmware revisions for G3 as well) models has been nailed down. The only exception is a G4 with ARB <= 2 can be hacked with UsU in order to root it and install a custom recovery.
Click to expand...
Click to collapse
Tmo is very easy
Go to dev options and enable adb
Then run "adb reboot bootloader"
Once there, run "fastboot oem unlock" and voila, you have an officially unlocked bootloader with no restrictions related to UsU
Please be aware the above will factory reset your device
ThePiGuy said:
Tmo is very easy
Go to dev options and enable adb
Then run "adb reboot bootloader"
Once there, run "fastboot oem unlock" and voila, you have an officially unlocked bootloader with no restrictions related to UsU
Please be aware the above will factory reset your device
Click to expand...
Click to collapse
Do you know anyone who has done it with H81120o or later? I've seen posts for two yrs about doing it that way, but I don't remember reading about it being done on 20o or later.
Sent from my SAMSUNG-SM-G935A using Tapatalk
SofaSpud said:
Do you know anyone who has done it with H81120o or later? I've seen posts for two yrs about doing it that way, but I don't remember reading about it being done on 20o or later.
Click to expand...
Click to collapse
Why v20o
Remember, this has nothing to do with UsU and therefore ARB etc doesn't matter
Edit: ps there are loads of H811 users in my Lineage thread and the other ROMs too
ThePiGuy said:
Why v20o
Remember, this has nothing to do with UsU and therefore ARB etc doesn't matter
Edit: ps there are loads of H811 users in my Lineage thread and the other ROMs too
Click to expand...
Click to collapse
Got it. Guess that it makes sense. ARB prevents rolling back to earlier release than 20o, I'm ok. Will try the BL unlock today then.
Sent from my SAMSUNG-SM-G935A using Tapatalk
I actually managed to get my LG V20 F800L into same situation after messing up my rooting process.
First i was stuck at logo and factory reset did nothing. Bootloader was working then.
Then i downloaded new firmware through "Download Mode", and after that i lost access to bootloader.
I know the phone model is different, but process seems to be very similar for all LG devices.
Trying to troubleshoot that atm, if i'll have results i'll post them here.
P.S. I know original poster long left (probably after throwing phone into a grinder), but maybe for someone with same problem as us in the future the info will be useful.
Florimer said:
I actually managed to get my LG V20 F800L into same situation after messing up my rooting process.
First i was stuck at logo and factory reset did nothing. Bootloader was working then.
Then i downloaded new firmware through "Download Mode", and after that i lost access to bootloader.
I know the phone model is different, but process seems to be very similar for all LG devices.
Trying to troubleshoot that atm, if i'll have results i'll post them here.
P.S. I know original poster long left (probably after throwing phone into a grinder), but maybe for someone with same problem as us in the future the info will be useful.
Click to expand...
Click to collapse
Ok, now i have to reply to my own post, since i believe i understand now something important:
LG phones usually dont have bootloader open to access. Until you use some exploits to do so.
I did not know that at the time of writing that reply.
Florimer said:
Ok, now i have to reply to my own post, since i believe i understand now something important:
LG phones usually dont have bootloader open to access. Until you use some exploits to do so.
I did not know that at the time of writing that reply.
Click to expand...
Click to collapse
Do you have more details about this? I seem to be in a similar situation than you and I'm struggling to make it work.