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.
Related
As anxious as I am an ass after unlocking the bootloader and install cwm ics wanted to return to the locked bootloader with cwm recovery and now "boot not verified" and I can not change or A200 for fastboot bootloader "operation not permitted" and hoped APX in my androidboot-SerialNo with euu (APX trought flash mode) of the page vache and is worthless and this time the sat not swallow it becomes clear that this manipulated the boot and recovery so do not do any help will be grateful to and for many people with this problem for various reasons
health
peporras said:
As anxious as I am an ass after unlocking the bootloader and install cwm ics wanted to return to the locked bootloader with cwm recovery and now "boot not verified" and I can not change or A200 for fastboot bootloader "operation not permitted" and hoped APX in my androidboot-SerialNo with euu (APX trought flash mode) of the page vache and is worthless and this time the sat not swallow it becomes clear that this manipulated the boot and recovery so do not do any help will be grateful to and for many people with this problem for various reasons
health
Click to expand...
Click to collapse
So wait you can't use fastboot?, because if you can try flashing our bootloader and then try the unlockboot loader technique.
You can not because the bootloader Original ics A100 is blocked in fastboot mode screen says "operation not allowed in locked mode" or maybe not appropriate commands
As far as I understand it, Your only hope is using fastboot to flash the unlocked bootloader again. I'm not sure why did you do this, since using custom recoveries require either an unlocked bootloader or some other way to bypass the security.
peporras said:
As anxious as I am an ass after unlocking the bootloader and install cwm ics wanted to return to the locked bootloader with cwm recovery and now "boot not verified" and I can not change or A200 for fastboot bootloader "operation not permitted" and hoped APX in my androidboot-SerialNo with euu (APX trought flash mode) of the page vache and is worthless and this time the sat not swallow it becomes clear that this manipulated the boot and recovery so do not do any help will be grateful to and for many people with this problem for various reasons
health
Click to expand...
Click to collapse
hello peporras, am i understanding correctly that you are able to access fastboot mode? if this is correct, you should be able to access adb. what exactly did you do to get your tablet where it is now? what exactly is happening when you turn on the tablet? were you rooted and did you have an unlocked bootloader when you got in this situation? let me know and i will do what i can to get you back up and running as soon as possible. good luck
so you flashed the a100 bootloader back to it? Are you able to boot into android? If so, I don't see why you can't install the a200 bootloader like you did before (assuming your rooted). Once you do that, you can unlock it with fastboot.
Sent from my SPH-D710 using Tapatalk
oneovakindoldys2 said:
hello peporras, am i understanding correctly that you are able to access fastboot mode? if this is correct, you should be able to access adb. what exactly did you do to get your tablet where it is now? what exactly is happening when you turn on the tablet? were you rooted and did you have an unlocked bootloader when you got in this situation? let me know and i will do what i can to get you back up and running as soon as possible. good luck
Click to expand...
Click to collapse
Ics because it has the last filtered root vache + + wm, if you boot normally in the upper left "verified boot failed" if I boot in recovery "recovery verified failed" and if you can boot into fastboot "bootloader v0.03.11-ICS: STARTING astboot download usb protocol protocol "and is another option that erases user data, I can not access ADB in any way I have a dmsg.test I drew a serial.no when used to work but not APX EEU-FLASH and a pair backup that I did with cwm when it worked I'm sure some way to restore it to and
regards
Euclid's Brother said:
so you flashed the a100 bootloader back to it? Are you able to boot into android? If so, I don't see why you can't install the a200 bootloader like you did before (assuming your rooted). Once you do that, you can unlock it with fastboot.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Well do not know why I did it maybe because I'm restless and try to leave the factory but now I have a nice paperweight bad mark
that is amazing over 430 visit of this help request without any answer please give me a Proposal
thanks
I used the GAIOv1.50 toolkit (Great tool! I just obviously don't know what I'm doing) to root my LG Optimus G I also used it to unlock the bootloader but I did not use it to install the custom recovery or restore the unlock stock boot. After doing what I just mentioned I restarted my phone. I was able to access the bootloader menus, but after realizing that I didn't install the custom recovery or restore the unlock stock boot, I performed those steps from the backlight screen. Now the bootloader screen loops and I can no longer access the menus and I don't know what to do from here (Or from the beginning obviously). I am definitely a NOOB and need help.
Please help!
iviarchello said:
I used the GAIOv1.50 toolkit (Great tool! I just obviously don't know what I'm doing) to root my LG Optimus G I also used it to unlock the bootloader but I did not use it to install the custom recovery or restore the unlock stock boot. After doing what I just mentioned I restarted my phone. I was able to access the bootloader menus, but after realizing that I didn't install the custom recovery or restore the unlock stock boot, I performed those steps from the backlight screen. Now the bootloader screen loops and I can no longer access the menus and I don't know what to do from here (Or from the beginning obviously). I am definitely a NOOB and need help.
Please help!
Click to expand...
Click to collapse
Did you solve the problem? How? If not, try this http://forum.xda-developers.com/showthread.php?t=2010624
I've got an LG G4 H811 (tmo) that I'm trying to install CyanogenMod on. (They list it as a supported device.) I successfully rooted it (Thanks, Team Codefire!), but "adb reboot bootloader" is just restarting the phone normally, and holding power & vol+ isn't working for me either. I'm running H81110h and I checked "Enable OEM unlock" in dev options. Does tmo have the bootloader locked down completely, or am I missing something?
Did you install TWRP? Whenever I get a new G4 (I'm on my 3rd one due to bootloop issue - this one was made in September, so hopefully I don't have anymore problems) I flash rooted image, and use that to install TWRP via Flashify or similar app. Once I have TWRP, I install whatever ROM I want.
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 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.