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.
Related
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.
i was successfully rooting my phone, using fastboot flash, i was thinking to use custom recovery but it need to unlock bootloader, i jog myself around google and found my self exhausted since none of their method work on my device, once i found a way to unlock my bootloader by downgrading the fastboot version, so i install the previous fastboot version with stock recovery on my phone, after that my phone start to reboot and stuck at asus logo, now its stuck at USB logo(clover view plus) now i pray to god to found solution to my problem rather i need dnx, ifwi, dnx osr, and fastboot .bin that worked with my device or any other way that make it through fastboot or droidboot again, i really really appreciate any working brain of yours
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.
Hello everyone.
Yesterday I decided to upgrade my G4 from MM to Nougat. I used a guide from xda (https://forum.xda-developers.com/g4/general/guide-upgrade-h815-locked-bootloader-to-t3684945) and it worked flawlessly.
However I want to root my G4 so I can install Xposed and Viper4Android but I have no clue how or if it's even possible to do it without downgrading my android version.
If anyone could link me a good guide or tell me how to do it I'd appreciate it a lot.
Just like in MM you can't root if your bootloader is locked.
Enjoy the N beta for now and just wait steadfasterX to release the unofficial BL unlock method
exermode said:
Hello everyone.
Yesterday I decided to upgrade my G4 from MM to Nougat. I used a guide from xda (https://forum.xda-developers.com/g4/general/guide-upgrade-h815-locked-bootloader-to-t3684945) and it worked flawlessly.
However I want to root my G4 so I can install Xposed and Viper4Android but I have no clue how or if it's even possible to do it without downgrading my android version.
If anyone could link me a good guide or tell me how to do it I'd appreciate it a lot.
Click to expand...
Click to collapse
First unlock Bootloader like in MM. YES its works in Nougat too !
Connect Phone via USB to PC with USB Debuggin in Developer option
In Terminal/ Console:
ADB Devices = Phone was detected
ADB reboot bootloader = Phone boot into Bootloader
FASTBOOT Devices = Phone was detected
FASTBOOT flash recovery twrp3.1.1-1-g4.img
Pull Battery out, put back and bootup Phone, first boot fails but the 2nd boot was okay.
After Phone boots up its in ADB Mode again.
ADB Devices = Phone was detected
ADB reboot recovery = Phone boot into TWRP
In TWRP, install TWRP and SU like you did in MM. Install Root Checker and check the root status, DONE
Finished, rooted Nougat !!
hello, I followed the guide step by step, I flashed the twrp recovery, but when I try to start the recovery mode, "no command" appears with the android symbol. I read online that just press a key combination I have tried many but I have not succeeded, if someone can help me thank him very much
vkoniv said:
hello, I followed the guide step by step, I flashed the twrp recovery, but when I try to start the recovery mode, "no command" appears with the android symbol. I read online that just press a key combination I have tried many but I have not succeeded, if someone can help me thank him very much
Click to expand...
Click to collapse
just do as how g7 goes in to recovery mode.
I have a Mi 10T purchased in Italy, and therefore coming factory loaded with a "branded" firmware RJDEUHG. It should be a Windtre modded ROM, please correct me if I'm wrong.
The latest known working ROM was the miui_APOLLOEEAHGGlobal_V12.5.3.0.RJDEUHG_da9e1c75b5_11.0.
Tired of waiting for the slow updates, compared to the unbranded global rooms, I decided to de-brand the phone and upgrade to a stock RJDEUXM.
But none of the XM firmware would load from recovery, therefore I applied and successfully unlocked the bootloader.
With the bootloader unlocked I managed to successfully flash
apollo_eea_global_images_V13.0.2.0.SJDEUXM_20220329.0000.00_12.0_eea_ad6f7ce846
apollo_eea_global_images_V12.5.12.0.RJDEUXM_20220208.0000.00_11.0_eea_664a15ed19
but both got stuck in a bootloop right after flashing.
During one of the many attempts, I used the MiFlash tool and accidentally left the default Flash & Lock option, the flashing was successful and the bootloader was locked.
At the moment I'm on V13.0.2.0.SJDEUXM, and can load onto bootloader and recovery, while, as mentioned before, the system won't load and get stuck in bootloop.
If I try to unlock the bootloader once again, the MiUnlock does not recognize the phone while in fastboot mode, remaining in the "Not connected to the phone" screen.
Any help would be really appreciated.
maybe, this is the solution, seems the same issue
https://c.mi.com/thread-3265050-1-0.html
fastboot devices
fastboot continue
if you have some lucky, boot normally
otherwise follow all the step
bye