Unfortunately for the Sprint variant I don't think we will ever be able to obtain root. Sprint removed fastboot completely from the phone. Unless there is a way to enable it, no root for Sprint variant.
Windows and mac...
Any way to install on linux? Ive been looking for them and xant find any?
Any way to install on linux? Ive been looking for them and xant find any?
I would expect Linux users to know how to search their software center or make a simple apt-cache query if on a Debian based distro.
Code:
[email protected]:~$ apt-cache search fastboot
fastboot - Android fastboot tool
[email protected]:~$ apt-cache search adb
adb - Android Debug Bridge
[email protected]:~$ ssu
[email protected]:/home/jc# apt-get install fastboot adbIf fastboot is gone entirely, maybe they accidentally removed signature verification as well?
They are, after all, both part of aboot.Could try these steps without the fastboot oem unlock part. Anyone tried yet?
Last edited:
I did try this on sprint v20 first issue was could not chmod 0777 * gave me error messageI would expect Linux users to know how to search their software center or make a simple apt-cache query if on a Debian based distro.
If fastboot is gone entirely, maybe they accidentally removed signature verification as well?
Could try these steps without the fastboot oem unlock part. Anyone tried yet?
Proceeded with the install anyways yolo right lol
Got all the way to the recowvery-applypatch boot and received the fail exiting message with the welcome to recowvery but could not execute run-as su
If anyone has any ideas im open to try @jcadduono
Attachments
Chainfire is da man ,its why I buy his apps to support all he does for the android community
Sent from my VS995 using Tapatalk
Sent from my VS995 using Tapatalk
So I can't seem to fastboot oem unlock. No devices recognized when I boot into fastboot. I have installed drivers and it recognizes from adb but not fastboot. I have no idea what's going on. I've tried the drivers op linked, Google's drivers, and even Marshall LG Drivers. Nada.
TWRP is functioning on H918. Doing some more bug checking before I can make it official.
Everything will be ready when @jcadduono is done making sure it's a stable release. There is no root nor is there a working TWRP as of now, but I'm sure if we are patient it will be VERY soon!
---------- Post added at 02:21 AM ---------- Previous post was at 02:17 AM ----------
I'm in the same boat! I have tried what seems to be everything, but can't get ADB to recognize the V20 in Fastboot, therefore cannot unlock the bootloader... I am going to try on my Mac to see if I have something else going on here?
Let me know how it goes! I'm gonna try a couple other things and see what works. Have no idea why it isn't.Everything will be ready when @jcadduono is done making sure it's a stable release. There is no root nor is there a working TWRP as of now, but I'm sure if we are patient it will be VERY soon!
---------- Post added at 02:21 AM ---------- Previous post was at 02:17 AM ----------
I'm in the same boat! I have tried what seems to be everything, but can't get ADB to recognize the V20 in Fastboot, therefore cannot unlock the bootloader... I am going to try on my Mac to see if I have something else going on here?
Actually, @Chainfire did achieve root using this method. His tweet is linked in the thread. I have started learning to code myself and it's insanely overwhelming so I understand not only needing to debug but also possible make it easier for people to do.Everything will be ready when @jcadduono is done making sure it's a stable release. There is no root nor is there a working TWRP as of now, but I'm sure if we are patient it will be VERY soon!
---------- Post added at 02:21 AM ---------- Previous post was at 02:17 AM ----------
I'm in the same boat! I have tried what seems to be everything, but can't get ADB to recognize the V20 in Fastboot, therefore cannot unlock the bootloader... I am going to try on my Mac to see if I have something else going on here?
I unlocked mine using my mac with no issues. Downloaded the drivers from the link, restarted and unlocked it.
Well we know root has been achieved, but NOT released for the public as of yet. That's all I was saying... And I am glad to know that it worked on your Mac cause that's what I am in the process of doing at this very moment.
You guys have received both a working TWRP and root but its risky and work is being done on the encryption and decryption
Please be patient
Please be patient
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.
Last edited:
so, following your guide (same as TMO G5...) should i finally have a working system ? No bootloop, right ?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
When you have more time, write all complete steps on Top Thread.
Last edited:
Thank you fine sir! Much appreciated!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.
I ran through the exploit process several times last night with no issues. I proceeded to flash SuperSU twice with no surprises either time. TWRP needs some work before it will support full disk encryption, but is otherwise in very good shape.
I've experienced zero bootloops and haven't had a single softbrick scare yet.
Pics incoming...
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone