You gotta go back through basically the whole process and run the recowvery commands through ADB. It sucks, but I would start back at page 1 of this thread with where you're at. I had a lot of trouble running recowvery, but basically you want to use only official Google ADB and Fastboot. If you're having issues, try another PC. That's what made the difference for me. The step where it looks like the phone is freezing really tripped me up a few times too. It went to the T-Mobile startup screen, and I kept thinking the process failed. For my phone at least though, that's how it looked when the process was successful. Feel free to reply with any other questions but you basically want to follow everything from page 1 and skip whatever is N/A like your bootloader is already unlocked. Best of luck!
When I get to
dirtycow /system/bin/app_process64 recowvery-app_process64
"<wait for completion your phone will look like it's crashing>"
it goes into a boot loop on the T-Mobile startup screen
dirtycow /system/bin/app_process64 recowvery-app_process64
"<wait for completion your phone will look like it's crashing>"
it goes into a boot loop on the T-Mobile startup screen
Yeah it's supposed to look like that. that step confused me too. It looks like it's booting, but it isn't. While it shows the T-Mobile startup screen you then go ahead and proceed to the next command, exit the shell and run the "adb logcat -s recowvery" to see if it was successful. That step was difficult for me too
That is the most difficult step. If you don't get success with "adb logcat -s recowvery", then I would try either a different PC, or a different version of ADB if you can find one. It didn't seem to work for me on Windows using the recommended ADB that I downloaded, but it did work on Linux Mint with the version available in their app store
I agree this is the most difficult step
. I had to install Linux Mint than complete the rest of the script. If it wasn't for your quick reply I would been stuck here a lot longer. Thank you
Last edited:
I have a carrier-unlocked US996 variant of the LG V20 sold in the United States (where I also am). I upgraded from this phone in 2020 because the screen started to ghost really bad. It has been sitting in a drawer since, and as a result its battery went bad; not an issue in principle because I didn't need it. However, because I now need to use it, I went out and got a new battery for it. The phone is currently on Android 8 with Software version US99620F, in case it matters (yes, I do see some references to rolling back to Android 7 in the thread, but that's not why I'm stating all that).
My issue, and question, is this: LG has shut off the portal where LG phone owners can go to download the file that will unlock the boot loader. Does anyone know of another way for getting the unlock file? I have done my due diligence searching Google in this respect and come up empty.
I have seen is references to a "Dirty Santa/Dirty Elf" procedure and researched this approach. However, unless I'm missing something, I've hit a brick wall with that as well: One method includes the US996 in the title, but then goes on to rather explicitly say it will brick the US996. The other method lists the US996 in the title as well, but then reaches a step that uses Fastboot and hangs. Researching what to do when that hang happens only returns instructions for specific LG models and warns that it will brick any not listed therein.
Any direction here would be greatly appreciated. I suppose that if I need to stick with the stock LG Android 8, I'll have to do so. However, I would really like to try and run a newer Android release. It's not just that: My understanding is that the long-term fix that addresses the aforementioned ghosting cannot be applied under the stock Android 8; they require rooting, which (unless I'm missing something) requires unlocking the boot loader. Consequently, I'm stuck between a rock and a hard place.
ANY guidance would be greatly appreciated.
My issue, and question, is this: LG has shut off the portal where LG phone owners can go to download the file that will unlock the boot loader. Does anyone know of another way for getting the unlock file? I have done my due diligence searching Google in this respect and come up empty.
I have seen is references to a "Dirty Santa/Dirty Elf" procedure and researched this approach. However, unless I'm missing something, I've hit a brick wall with that as well: One method includes the US996 in the title, but then goes on to rather explicitly say it will brick the US996. The other method lists the US996 in the title as well, but then reaches a step that uses Fastboot and hangs. Researching what to do when that hang happens only returns instructions for specific LG models and warns that it will brick any not listed therein.
Any direction here would be greatly appreciated. I suppose that if I need to stick with the stock LG Android 8, I'll have to do so. However, I would really like to try and run a newer Android release. It's not just that: My understanding is that the long-term fix that addresses the aforementioned ghosting cannot be applied under the stock Android 8; they require rooting, which (unless I'm missing something) requires unlocking the boot loader. Consequently, I'm stuck between a rock and a hard place.
ANY guidance would be greatly appreciated.
Last edited:
Just use a vs995 dirtysanta guide, the one from Lazerwolf is pretty good.
Similar threads
- Poll
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
206If you are not an H918, H830, or US996 (Unlocked, NOT US Cellular) user, kindly leave this thread, this will not do anything for your device, exchange it if you're so desperate. Thank you.
Note for US996: It's probably easier for you guys just to flash TWRP the normal way and pull your battery then do the factory reset dance to get in!
Team Win Recovery Project 3.0.2-1
Alright, so you guys have probably heard about me working on this project for a week now. Sorry it's been taking so long, there's been so many variables and hurdles to go through!
I don't own the device myself, so it was all done over TeamViewer thanks to @slayerh4x and @Darriousx who stayed around in the #twrp channel on freenode to assist with their devices.
This will allow you to install TWRP and flash SuperSU!
Step 1: Unlocking your bootloader
You will need to unlock your bootloader first. For this you'll probably need LG's drivers.
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
You will also need adb and fastboot. You can download them in a portable small form factor here:
http://forum.xda-developers.com/android/software/host-tools-t3402497
Start by turning on developer options in Settings -> About device -> Software info -> Build number. (tap 7 times until it's enabled)
Now navigate to Settings -> Developer options -> OEM unlock. (turn it on)
Don't ever turn OEM unlock or Developer options off when using a custom ROM or recovery. This could lose to loss of all your data.
For your computer to see ADB, you will need to put the phone in PTP mode (for transferring images). I don't know why this is, a misconfiguration in LG's kernel gadget drivers maybe?
Extract adb and fastboot to a folder on your PC.
Type adb start-server and make sure to check the notification on your phone to accept debugging authorization.
You can reboot into fastboot mode with adb reboot bootloader once authorized.
If it fails to authorize or show the notification on your phone, you may need to try other USB ports.
H918/H830 users only:
To unlock your bootloader, use fastboot oem unlock once the phone boots into fastboot mode.
Warning: This step will wipe all your data and factory reset your phone!
You can check the status of your bootloader lock with the fastboot getvar all command.
ex. (bootloader) unlocked:yes
You should now boot back into your phone (fastboot reboot).
You will probably need to complete the Android setup wizard at this point to get access to ADB again.
US996 users only:
To unlock your bootloader, follow the unlock instructions on LG's site (I can't really help you there):
https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
Once you're finished with unlocking your bootloader, continue on to step 2.
Step 2: Running recowvery
You can find the recowvery binaries (you need to download all of these) at:
https://build.nethunter.com/android-tools/dirtycow/arm64/
You're now ready to follow the recowvery installation instructions.
See here: https://github.com/jcadduono/android_external_dirtycow#running (running section)
Bonus: There's also a full write up on that page on how recowvery works if you're into that kind of stuff.
Step 3: Flashing TWRP & Rooting
Notice: There is currently no decryption support, just the same as the LG G5, I'm running into the exact same scenario (unable to start rpmb device).
Due to this, I have disabled hardware decryption in this build to keep it stable. If you wish to have your data work in TWRP, you will need to disable decryption.
If you're coming from the Note 7 or S7, this will be a familiar scenario for you.
Once you've got your permissive shell in adb, you will have access to your partitions via dd.
You should transfer TWRP to your internal storage (name in twrp.img) using MTP, you can also just use adb push. (mentioned here)
Download TWRP: (official builds, V20 is waiting for TWRP 3.1.0 for twrp.me download)
H918: https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-h918.img
US996: https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-us996.img
H830: https://twrp.me/devices/lgg5h830.html
This step requires that you've used dirtycow to replace /system/bin/run-as with recowvery-run-as. If you've rebooted since doing that, you will need to go back and do that again.
You should be inside TWRP now. It will ask you if you want to enable system modifications. You should swipe yes, otherwise your OS will replace TWRP on next boot.Code:adb push twrp-3.0.2-x-xxxx.img /sdcard/twrp.img adb shell $ run-as exec dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery "<wait for it to complete>" $ reboot recovery
Flash the latest zip from https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ to turn off forced encryption at boot and allow you to boot a modified system. If you're flashing SuperSU.zip, it will also do this for you so this won't be necessary.
Warning: If you don't flash either no-verity-opt-encrypt or SuperSU, you will probably end up in a horrifying never-ending boot loop of "corruption"!
Latest SuperSU: https://download.chainfire.eu/supersu
To disable encryption after flashing SuperSU or the no-verity-opt-encrypt zip, you must use the [Format Data] button on the Wipe page in TWRP. No other options will work.
Back up all your internal storage and apps data that you can to your PC. You can use Titanium Backup with SuperSU before doing this step if you like.
Warning: Using [Format Data] will wipe all your apps and data (including internal storage) off the phone, giving you the out-of-the-box experience of a new phone!
Once this is done, you should be able to backup/restore/use any function of TWRP without any issues.
Flashed SuperSU? You're done! Boot up (it will reboot a few times) and set up your SuperSU Manager to your liking and give this post a thanks!
Step 4: Have fun!
I know a few people have mentioned donating, there is a button right on this post under my username.
Sorry, I don't keep a list as I prefer to keep people's information confidential, but if you do send any money my way, you can request that I mention you at the bottom of this post with any details.
I ask that people please not attach files in this thread, everything required is mentioned in this post, and should be stable in its present state. Thank you.30The combination of the amount of thanks on Chainfire's post that does nothing more than say he's glad he doesn't have to work on the device compared to my actual OP, and this headline on AndroidHeadlines: "Chainfire Successfully Gains Root Access To LG V20" is pretty frustrating. Why why why!
In the meantime I've made a few bug fixes and cleaned up the code to recowvery, so it should be a little more understandable too. New binaries are already up at the same location.
I'm wondering what other devices out there in the world don't have signature enforcement enabled (unlockable, or unlocked but inaccessible or flash disabled bootloader), whatever there is, recowvery will very likely work on them as well in its current state. I assume people have tried this on all variants of the V20 now... (skipping past the fastboot instructions)
It should work on the H830 as well I think, negating the need to use TOTs and flash their entire device. (does it still do that?)20
Well then, let's release it to the public then.
https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-0-beta4-h918.img
Follow the instructions in the OP, there are instructions in the end of the README to flash the TWRP image.
There is currently no decryption support, just the same as the LG G5, I'm running into the exact same scenario (unable to start rpmb device).
Due to this, I have disabled hardware decryption in this build to keep it stable. If you wish to have your data work in TWRP, you will need to disable decryption.
If you're coming from the Note 7 or S7, this will be a familiar scenario for you.
Flash the latest version from https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ once you're in TWRP to turn off forced encryption at boot and allow you to boot a modified system. If you're flashing SuperSU.zip, it will also do this for you.
Latest SuperSU: https://download.chainfire.eu/supersu
To disable encryption after flashing SuperSU or the no-verity-opt-encrypt zip, you must use the [Format Data] button on the Wipe page in TWRP. No other options will work.
Back up all your internal storage and apps data that you can to your PC. You can use Titanium Backup with SuperSU before doing this step if you like.
Warning: Using [Format Data] will wipe all your apps and data (including internal storage) off the phone, giving you the out-of-the-box experience of a new phone!
Once this is done, you should be able to backup/restore/use any function of TWRP without any issues.
New posts
-
[MOD][DEV] MediaTek / MTK - Auth Bypass (SLA/DAA) - Utility- Latest: TheProvingGround
-
-
