I attempted to root the LG V10 a few days ago. I managed to get the bootloader unlocked. I was on 20e when I did this. I then flashed 20L to get twrp and I can't boot up after that. It loops back to TWRP. Am I missing another part?. When I connect my phone to LGUP it says I'm still on 20e firmware. I will point out that in TWRP I get the error message that it cant mount /cache. Easy fix. Just wiping cache will do. And when I flash 20j zip, at the end it says that it failed or something but it wasnt in red. I haven't found a thread or youtube video that can help. I'm currently at work when writing this and I would like to be pointed in the right direction to get it solved when I get home. Thanks in advance to anyone who will help. :good:
Scratch that. I managed to get the phone up and running. I just flashed the 20j kdz and reflashed the rooted .tot
Related
All:
I have attempted to flash TWRP via various methods to no avail. I have somehow messed something up so I cannot get the stock recovery to work. I can get into the stock recovery screen, but if I select anything, it says Secure boot error. I am currently on OTA 5.0.1 VS98523C. Any advice on how to proceed? I have looked at KDZ options, but am wondering if I can just get the stock recovery back and let it ride until TWRP is available.
Thanks in advance,
Steven
I'm having trouble with getting TWRP to flash successfully. Using their app and flashify
MrSpohn1 said:
All:
I have attempted to flash TWRP via various methods to no avail. I have somehow messed something up so I cannot get the stock recovery to work. I can get into the stock recovery screen, but if I select anything, it says Secure boot error. I am currently on OTA 5.0.1 VS98523C. Any advice on how to proceed? I have looked at KDZ options, but am wondering if I can just get the stock recovery back and let it ride until TWRP is available.
Thanks in advance,
Steven
Click to expand...
Click to collapse
In theory, you can use the dd comment to put the aboot back, but I would not recommend it as I got my phone hard bricked that way. (so dead that even KDZ does not work)The safest way is KDZ back to 10b, and then stump root. Then:
1. Install TWRP manager from Google Play.
2. From TWRP manager you can choose your phone model and download and install TWRP recovery.
3. Follow the instruction from this link to use TWRP to install the 23c
http://forum.xda-developers.com/verizon-lg-g3/development/rom-rom-base-lp-upgrade-bump-t3051884
Never do OTA if you have rooted your phone. It needs to be completely stock for OTA to work.
/\ What he said.
Twrp doesn't work after lollipop because of the signing requirements in the bootloader.
It needs to be rolled back to 10-12b and then rooted and then you can load twrp. Once you have twrp you can load jasmine or skydragon which are both 5.01.
http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
Thanks! So if I want to use xposed, I should roll back to the other versions of lollipop?
thanks all. I KDZ'd 12b stock rom, rooted, then flashed TWRP through flashify. I then went into recovery and installed the 23c rom. I used skydragon 4.0.0 because I tried to flash Jasmine 7.0 like 8 times. I did not have any of the bottom keys and I could not access my pulldown menu. I could not figure out why this was happening. Skydragon worked for me perfectly. Thanks All.
I have one LG g3 Ls990 model with Android 5.0.1 and ZVA firmware.
I rooted phone with LG script method without any issue. Rooting successful.
After this I installed twrp with Ls990 autorec lolipop apk.
Then I switch off phone and booted in twrp and made backup of my efs and present stock rom.
But when I again booted phone , it show lg logo and screen written with "Security Error" and then switch off.
Still I am able to boot in twrp and download mode but not able to boot in rom.
Kindly guide me to resolve this issue.
Thanks in advance.
arunkarnwal1981 said:
I have one LG g3 Ls990 model with Android 5.0.1 and ZVA firmware.
I rooted phone with LG script method without any issue. Rooting successful.
After this I installed twrp with Ls990 autorec lolipop apk.
Then I switch off phone and booted in twrp and made backup of my efs and present stock rom.
But when I again booted phone , it show lg logo and screen written with "Security Error" and then switch off.
Still I am able to boot in twrp and download mode but not able to boot in rom.
Kindly guide me to resolve this issue.
Thanks in advance.
Click to expand...
Click to collapse
I don't know if this will help, but it SHOULDN'T hurt either.
http://forum.xda-developers.com/showthread.php?p=57144978
Try flashing it. It's skin1980 sharpening mod, and it bumps the kernel.
Maybe it'll work.
engine95 said:
I don't know if this will help, but it SHOULDN'T hurt either.
http://forum.xda-developers.com/showthread.php?p=57144978
Try flashing it. It's skin1980 sharpening mod, and it bumps the kernel.
Maybe it'll work.
Click to expand...
Click to collapse
not work. but finally i flashed zv4 tot and root it with bump twrp.
now i want to install ZVA or any lollipop rom, so kindly guide me further steps as presently i am on ZV4 with root and bump twrp and also gsm unlocked.
arunkarnwal1981 said:
not work. but finally i flashed zv4 tot and root it with bump twrp.
now i want to install ZVA or any lollipop rom, so kindly guide me further steps as presently i am on ZV4 with root and bump twrp and also gsm unlocked.
Click to expand...
Click to collapse
Boot into twrp and flash "BarpapA" by @engine95
1619415 said:
Boot into twrp and flash "BarpapA" by @engine95
Click to expand...
Click to collapse
can I install cloudy 2.5 in same manner?? or required to flash zv8 modem
arunkarnwal1981 said:
I have one LG g3 Ls990 model with Android 5.0.1 and ZVA firmware.
I rooted phone with LG script method without any issue. Rooting successful.
After this I installed twrp with Ls990 autorec lolipop apk.
Then I switch off phone and booted in twrp and made backup of my efs and present stock rom.
But when I again booted phone , it show lg logo and screen written with "Security Error" and then switch off.
Still I am able to boot in twrp and download mode but not able to boot in rom.
Kindly guide me to resolve this issue.
Thanks in advance.
Click to expand...
Click to collapse
I am in the same place (Security Error) and arrived there via the same steps. I think the only difference is that I am on ZVB firmware.
The firmware difference may explain (or maybe not) why I can boot into TWRP but NOT into download mode.
I'm thinking that if I have TWRP access I should be able to dig myself out of this hole, but not sure how to proceed. I'm guessing that doing a factory reset is not going to fix this, but if that were to return me to stock, that would be great. But I don't want to attempt that without getting some experienced feedback.
If a reset is a no-go, what are my flashing options?
Thanks for any suggestions!
Update & Additional Info: When I'm in TWRP, if I select Reboot and then Bootloader, the Firmware Update screen appears.
Any way to return to Stock?
Yes I have tried the LgUp route....no go
Yes I have tried LG FlashTool route.......well something happened
Yes I have tried the ALL IN ONE Toolkit for Verizon......this is nothing more than the LG FlashTool route, just step by step.
History.......I flashed the new FW version 3.1.1 from XDABBEB and now I cannot flash stock again.
Best I could get is the LG FlashTool, because LGUP sees this phone now as "unkown".
When I try to flash through LG FlashTool I get null for pid and imei, yes I have used various versions of DLL that came with the TOT file.
At this point I am clueless......I can see that when I used the LG FlashTool it sees this:
Error: [14:53;5] CrossDL [VS985 4G] to [VS985]
Anybody have any ideas....thanks in advance.
i ran into the same problem also. i tried to flash back to 10b after installing @xdabbeb's 3.1.1 rom and i got the same CrossDL error almost immediately. the good news is that since the error comes up almost immediately, nothing is downloaded or flashed to your phone. you should still be able to boot into it.
i had a nandroid backup of my previous rom, which was jasmine 4.0. i flashed the 12b bootstack and then restored the nandroid. the interesting thing was that after restoring the nandroid, i still wasn't able to downgrade to 10b. i had to boot into the rom and then power back down. after that, i was able to flash 10b.
other people have reported being able to downgrade to 10b from 28a. @xdabbeb's 3.1.1 rom uses systemless root which modifies the system and/or boot image files. my guess is that the systemless root is what is preventing the downgrade to 10b from working. my suggestion is to try unrooting first and then try flashing 10b. if not, i hope you have a nandroid backup that you can restore and downgrade from.
http://forum.xda-developers.com/showthread.php?p=68957928
The above, and flash any KDZ 35B or higher first, then the TOT since TOTs fix things that KDZs can't.
I did a data wipe accidentally in TwRP. Meant to just get cache. Now I lost root/TWRP apparently. Just recently updated to 20c. I have no recovery when I reboot but I still get the unlocked bootloader info when rebooting. Any ideas/help is greatly appreciated.
Jjavitable22 said:
I did a data wipe accidentally in TwRP. Meant to just get cache. Now I lost root/TWRP apparently. Just recently updated to 20c. I have no recovery when I reboot but I still get the unlocked bootloader info when rebooting. Any ideas/help is greatly appreciated.
Click to expand...
Click to collapse
I don't see how wiping data would remove TWRP, but the way I'd reestablish TWRP once it's gone would be to LGUP the Tungkick 10d tot file and then use that TWRP to flash the 20c zip by Autoprime. Flash SuperSU one way or another and then have a blast. I'm sure there are other ways to accomplish all this, but this way is easy and has been reliable for me.
It seems that you can still boot the phone.
If you still have valid bootloader the issue is not that tricky.
Just do a "adb reboot bootloader" and reflash twrp, like how you installed them in the first place.
I'm not sure which exact version of twrp is compatible with v20*, but that should be easy to find anyway.
Then boot into twrp and flash supersu/magisk/any other thing you need.
ReVanTis said:
It seems that you can still boot the phone.
If you still have valid bootloader the issue is not that tricky.
Just do a "adb reboot bootloader" and reflash twrp, like how you installed them in the first place.
I'm not sure which exact version of twrp is compatible with v20*, but that should be easy to find anyway.
Then boot into twrp and flash supersu/magisk/any other thing you need.
Click to expand...
Click to collapse
So I did a factory reset from the settings menu. Now it boots back into TWRP. Weird. But that's it. No OS. Just the recovery. So I guess I'll try and flash a ROM and see if I can get that back. Thanks for trying to help.
Bulkang U. Antibop said:
I don't see how wiping data would remove TWRP, but the way I'd reestablish TWRP once it's gone would be to LGUP the Tungkick 10d tot file and then use that TWRP to flash the 20c zip by Autoprime. Flash SuperSU one way or another and then have a blast. I'm sure there are other ways to accomplish all this, but this way is easy and has been reliable for me.
Click to expand...
Click to collapse
Wasn't sure if I could do any 10s coming from 20C. I got into TWRP recovery but now I have no OS. Thanks for helping out.
Jjavitable22 said:
Wasn't sure if I could do any 10s coming from 20C. I got into TWRP recovery but now I have no OS. Thanks for helping out.
Click to expand...
Click to collapse
Yeah, as long as the ARB is the same (ANTIROLLBACK 01) you can flash 10 after 20. I don't think 10a qualifies, but 10d should be okay from 20a or 20c.
It's a quirk of the G5 that TWRP can only be accessed from boot by factory reset of the phone. If you are already up and rooted, you can use a command or program AFTER boot to access TWRP without factory reset. But, for now, that's our doorway into TWRP from power-off.
Now that you're in TWRP you can sideload a ROM onto your SD and flash it, just remember to also flash the latest superSU zip afterward to ensure root (unless your ROM is pre-rooted.)
Hi,
I have a rooted LG G5 H850 with an unlocked bootloader and TWRP. I was on H850 20A OPEN EU ROM from autoprime and I tried to flash H850 20D OPEN EU ROM. I booted into recovery TWRP and flashed the Zip file together with the newest SuperSU. When I tried to reboot the phone stuck in reboot - always changing between the message "Your device software cannot be checked for corruption" and the LG logo. After a long time (15 minutes or so) I pulled the battery. The same thing. Then I tried to get into recovery using the 2 hands method. I clicked through the factory reset screens (yes, yes...) - and the phone stuck between warning screen and logo again.
Could someone help me to get into TWRP again? If this would be possible I could restore my backup. Otherwise I don't what to to else...
Thanks for any helP!
Ok, after several tries with the 2 hand method, I got into TWRP again. I tried to restore my backup but it failed with an error. After that I did a full wipe (factory reset) but without the internal storage. Then I flashed the 20D zip again, after that SuperSU. Now the phone is rebooting and rebooting and rebooting. It is stuck on the LG logo and nothing else is happening. It's frustrating...
Firmware reset > flash zip file.
If that doesn't work use the LGUP or LG Bridge method to flash firmware. There should be threads in the development section
projectsome said:
Firmware reset > flash zip file.
If that doesn't work use the LGUP or LG Bridge method to flash firmware. There should be threads in the development section
Click to expand...
Click to collapse
Thanks for your help, but I don't use windows. But in the meantime I got it solved. The reason for the failure was a corrupted external sd card. Flashing from a new card did help.
i'm getting the same problem with the OREO OPEN EU ROM, booted into TWRP, flashed SuperSU and after a few loops got stuck on the LG logo. Had to pull the battery, go into download mode & reflash the ROM via LGUP. I somehow doubt it's the SD card as there were no errors on the SuperSU install.