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.
Related
I recently successfully unlocked bootloader on my H815 EUR version, v20a. I then proceeded to flash TWRP after booting into it from fastboot. I let the phone restart to make sure everything is ok. Then I went back into TWRP to flash SU. After that, I got a bootloop stuck at LG logo. Luckily I was able to use LG Bridge to flash back to stock and get rid of bootloop.
My question is, how come I got a bootloop? Is it worth it to try to root my phone again? I want to be able to use titanium backup to transfer stuff from my old phone. I also want to use xposed.
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.
So long story short, my rom (nitrogenOS, great rom BTW) got corrupt (or so I thought) and I had to wipe all data to re-install it clean.
But now I'm in a position where my phone has no rom, no recovery (neither TWRP nor stock) and both my bootloader and bootloader critical are locked (Last time I had to lock and unlock them to prevent bootloop before flashing stock OS, I don't know why)
Now I can't boot into twrp or absolutely anything, and cannot unlock the bootloader either because it says "Flashing unlock is not allowed".
Is my device 100% unrecoverable?
Going to have to go back to JBHifi (Australia) and have them send it to google
Any thing I can still do to recover the device?!
railpressureflip said:
So long story short, my rom (nitrogenOS, great rom BTW) got corrupt (or so I thought) and I had to wipe all data to re-install it clean.
But now I'm in a position where my phone has no rom, no recovery (neither TWRP nor stock) and both my bootloader and bootloader critical are locked (Last time I had to lock and unlock them to prevent bootloop before flashing stock OS, I don't know why)
Now I can't boot into twrp or absolutely anything, and cannot unlock the bootloader either because it says "Flashing unlock is not allowed".
Is my device 100% unrecoverable?
Going to have to go back to JBHifi (Australia) and have them send it to google
Any thing I can still do to recover the device?!
Click to expand...
Click to collapse
you might be able to fastboot boot path/to/recovey.img like when you were flashing twrp but im not sure if that works on locked devices try it with a factory image with the recovery extracted and if that works you can sideload the full ota in recovery.
and possibly lgs flashtool can rewrite the phone with it locked but idk if there are imgs out there or if it works with pixel 2 xl
for next time never lock your phone on a custom rom really never relock once unlocked there is no need to and it only takes away your recovery options
railpressureflip said:
So long story short, my rom (nitrogenOS, great rom BTW) got corrupt (or so I thought) and I had to wipe all data to re-install it clean.
But now I'm in a position where my phone has no rom, no recovery (neither TWRP nor stock) and both my bootloader and bootloader critical are locked (Last time I had to lock and unlock them to prevent bootloop before flashing stock OS, I don't know why)
Now I can't boot into twrp or absolutely anything, and cannot unlock the bootloader either because it says "Flashing unlock is not allowed".
Is my device 100% unrecoverable?
Going to have to go back to JBHifi (Australia) and have them send it to google
Any thing I can still do to recover the device?!
Click to expand...
Click to collapse
How the heck did your bootloader get locked if you didn't do it yourself?? Do you get your phone ID displayed when you type in "fastboot devices" in bootloader mode???
You probably ended up switching slots when you reflashed. You need to use Deuces flashing script. Say yes to unlocking.
Try downloading and installing skipsoft tools. It might not see your device but try. If it doesn't see it, manually select your device. Have it install USB drivers. Restart skipsoft and see if it sees your device then. I got into a situation once where in fastboot it showed something like a corrupt bootloader and my computer could not see my device. After messing with the phone with skipsoft running, skipsoft could see it when my computer couldn't.
Hello all,
I'm pulling my hair out trying to figure this one out. I have long ago unlocked the bootloader and have crossflashed my G710PM to ULM. At this point my main goal is to flash lineage to this device. I had originally bricked the phone flashing a V30 experimental bootloader, seeing as it was my daily driver, I went an purchased a new phone. Now I'm back to work on this phone as a project, and with a quick QFIL flash, I'm back to square one.
I have only been able to access fastboot when I have the ULM11g firmware flashed to the phone, as far as I'm aware, you can't flash TWRP using this version so I flashed ULM21d in order to get TWRP on it. I wasn't able to get to fastboot from this version so I tried flashing the Euro firmware EM20b. Once again, no fastboot. I've made multiple attemps to find the abl-a image for the ULM version with no success.
I'm determined to get lineage on the phone.. Any help as to where I should start would be hugely appreciated!
Flash Ulm11g again and ab_a then flash ulm20e or 20