Database Users

[GUIDE] Simplest way to root your desire z

First downgrade your firmware version to 1.34.405.5 or below, you can do this by copying 1.34.405.5_PC10IMG.zip which you can download from here and rename it to "PC10IMG.zip".
Then boot into bootloader, you can do this through adb by typing "adb reboot bootloader" or you can just power off your phone, pull out your battery and then restarting it with both power button and volume down button pressed together.
Make sure you have enabled USB debugging in your phone.
It will automatically detect the image and will install it on your phone.
Now fill in your information and let your phone get started for the first time.
Now follow this guide:
Your phone is rooted by now.
Download ROM manager and flash clockworkmod recovery.
Now your are good to go.
Hit the thanks button if you find my post useful.

You can download the android sdk and g2_root from the following links.
Android sdk is needed for adb.
Android SDK:
- http://developer.android.com/sdk/index.html
G2 Root (Pack
- http://www.mediafire.com/?jmdqt1z03msaybl
Remember to turn off your pc antivirus before doing this because it may detect rage as a virus and won't allow you to run it.

This guide is completely unneccessary, and also lacking.
You cannot just do a straight downgrade to 1.34, you need to temp-root and modify your misc partition first.
Also, if you're gonna bother using adb a little, you may as well run everything in cmd/terminal, as you can copy/paste instead of having to type the commands onto the phone.
-Nipqer

Nipqer said:
This guide is completely unneccessary, and also lacking.
You cannot just do a straight downgrade to 1.34, you need to temp-root and modify your misc partition first.
Also, if you're gonna bother using adb a little, you may as well run everything in cmd/terminal, as you can copy/paste instead of having to type the commands onto the phone.
-Nipqer
Click to expand...
Click to collapse
Someone asked for a tutorial for noobs who just want to get their phone rooted without bothering about anything. That's why I posted it.
And the above mentioned tutorial is 100% working as far I have tested it.

ajhavery said:
Someone asked for a tutorial for noobs who just want to get their phone rooted without bothering about anything. That's why I posted it.
Click to expand...
Click to collapse
You took somebody else's YouTube video, and just added a couple lines of text, that are too vague, and would completely confuse a noob. I don't see how this in any way is better than:
http://forum.xda-developers.com/showthread.php?t=1178912
and
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD

Continual Boot to TWRP [T-Mo]

So for the first time in my history of Android's since the G1 I've finally bricked a phone. Apparently there was an OTA for the T-Mo devices and I managed to hamfist my notification and accept it.
Needless to say I'm now stuck permanently booting into TWRP. I've tried some various troubleshooting methods including doing what I thought was a successful sideload of the TMo-Stock-Rooted Rom. It showed a successful push and ran through the install but I got a message kicked back saying "No OS installed". Now I've seen other users receive this same message and after rebooting anyway they got their ROM to boot.
No such luck for me, after it reboots (post sideload install) it shows system as unmounted and then just boots back into recovery ad nauseum...I'm really at a loss here folks.

Have you already tried this?...
http://forum.xda-developers.com/showthread.php?t=2451696

redduc900 said:
Have you already tried this?...
http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
Hadn't tried it previously but I just attempted to run the ADB command and it still boots into TWRP. I'm not sure if those commands worked or not however. I got a big wall of text in terminal after the second command.
FWIW, on every reboot System is unmounted (Data & Cache remain mounted) but I can check it. Seems that it's irrelevant whether its checked or not.
Tried a sideload using the Stock Rooted 110G image and still nothing. Sideload appears to go, and install goes through without error but reboots only into TWRP with System unmounted.

k4ylr said:
Hadn't tried it previously but I just attempted to run the ADB command and it still boots into TWRP. I'm not sure if those commands worked or not however. I got a big wall of text in terminal after the second command.
FWIW, on every reboot System is unmounted (Data & Cache remain mounted) but I can check it. Seems that it's irrelevant whether its checked or not.
Click to expand...
Click to collapse
can you get the phone to shut off and stay off. If you can then simply put it in download mode and use LG flash tool to flash stock rom back on. Please let me know if this is an option if not I will try and figure out something else

joewaz said:
can you get the phone to shut off and stay off. If you can then simply put it in download mode and use LG flash tool to flash stock rom back on. Please let me know if this is an option if not I will try and figure out something else
Click to expand...
Click to collapse
I can get it to shut off and stay off no problem. I'm on OSX at the moment and likely won't be able to get to a PC until the 9th. I'll definitely give the LG Flash tool method a try when I can.

k4ylr said:
I can get it to shut off and stay off no problem. I'm on OSX at the moment and likely won't be able to get to a PC until the 9th. I'll definitely give the LG Flash tool method a try when I can.
Click to expand...
Click to collapse
yes I am afraid you are stuck in till you can get to a real man's computer lol. I'm just kidding though my girlfriend has a stupid Apple and I was stuck with the same problem I had to drive 50 miles to where I used to live to pick up my laptop to fix this. But the LG flash tool works like a charm and you will not have any problems. Just make sure that you read the procedure for the Verizon phone. If you are not surelookup the forum wink Link

joewaz said:
yes I am afraid you are stuck in till you can get to a real man's computer lol. I'm just kidding though my girlfriend has a stupid Apple and I was stuck with the same problem I had to drive 50 miles to where I used to live to pick up my laptop to fix this. But the LG flash tool works like a charm and you will not have any problems. Just make sure that you read the procedure for the Verizon phone. If you are not surelookup the forum wink Link
Click to expand...
Click to collapse
Haha I hear you. I moved recently and the apt I'm in doesn't have ethernet drops so I had to order up a PCI wireless nic card =\ I'll dig around for the LG flash tool guides and see what I can learn.
I was hesitant to even flash a recovery because of how ass backwards LG made it for us in the first place =\

k4ylr said:
Haha I hear you. I moved recently and the apt I'm in doesn't have ethernet drops so I had to order up a PCI wireless nic card =\ I'll dig around for the LG flash tool guides and see what I can learn.
I was hesitant to even flash a recovery because of how ass backwards LG made it for us in the first place =\
Click to expand...
Click to collapse
brother I feel your pain. But when you get everything all situated I will tell you the easiest way to install a backup recovery program. It is an app in the App Market called free GEE... One click and bam you have a backup lol.. You may want to use freegee to make sure twrp is installed right.. It will just over write all the files and correct any wrongs... Freegee.. Remember that!!

k4ylr said:
So for the first time in my history of Android's since the G1 I've finally bricked a phone. Apparently there was an OTA for the T-Mo devices and I managed to hamfist my notification and accept it.
Needless to say I'm now stuck permanently booting into TWRP. I've tried some various troubleshooting methods including doing what I thought was a successful sideload of the TMo-Stock-Rooted Rom. It showed a successful push and ran through the install but I got a message kicked back saying "No OS installed". Now I've seen other users receive this same message and after rebooting anyway they got their ROM to boot.
No such luck for me, after it reboots (post sideload install) it shows system as unmounted and then just boots back into recovery ad nauseum...I'm really at a loss here folks.
Click to expand...
Click to collapse
No worries friend! I almost went crazy last night trying to find a fix!! Here what fixed mine!
You need to be EXTREMELY CAUTIOUS when typing this in:
Go to Advanced in TWRP and run Terminal
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit go
after it pushes through again type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.

coldcrush390 said:
No worries friend! I almost went crazy last night trying to find a fix!! Here what fixed mine!
You need to be EXTREMELY CAUTIOUS when typing this in:
Go to Advanced in TWRP and run Terminal
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit go
after it pushes through again type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
Are those commands pushable through ADB? For whatever reason when I get to the Terminal Command through TWRP it wants me to navigate to a different directory and there's no command line to type things in. I've always been a CWM flash a .zip kinda guy so digging into ADB is all new for me.

coldcrush390 said:
no worries friend! I almost went crazy last night trying to find a fix!! Here what fixed mine!
You need to be extremely cautious when typing this in:
Go to advanced in twrp and run terminal
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit go
after it pushes through again type:
Dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
this worked perfectly!!! Thanks sooooo much!!!!!!!!!!!

k4ylr said:
Are those commands pushable through ADB? For whatever reason when I get to the Terminal Command through TWRP it wants me to navigate to a different directory and there's no command line to type things in. I've always been a CWM flash a .zip kinda guy so digging into ADB is all new for me.
Click to expand...
Click to collapse
Don't navigate anywhere, I thought the same thing just tap on select below and follow the commands. Take your time doing it and don't rush!
---------- Post added at 07:24 PM ---------- Previous post was at 07:23 PM ----------
jwagman1 said:
this worked perfectly!!! Thanks sooooo much!!!!!!!!!!!
Click to expand...
Click to collapse
Your welcome

What about if your in CWR? How can I bring my wife's phone? It tried to update itself and I'm stuck on recovery

coldcrush390 said:
Don't navigate anywhere, I thought the same thing just tap on select below and follow the commands. Take your time doing it and don't rush!
Click to expand...
Click to collapse
Ran the terminal side commands, got to LG Splash and we're sitting there now. We'll see how long it sits or if it's a boot loop.
**EDIT**
10 minutes sitting at the LG splash no go. I managed to snag an interim wifi adapter for my desktop so I'm going to try the Flash tool posted from earlier and see if it works.

Update
I was able to bring the phone back with those commands using adb thank you guys for your help.

djeddieone said:
How can I do this on add? What would be the commands on adb? I'm on CWR so I can't use twrp
Click to expand...
Click to collapse
Can't say for sure, I had seen some to run this way:
adb shell
then the 2 lines of prompt. I'm stuck on a boot loop so I'm trying to get the Flash Tool method to work. I should have not messed with G2 in retrospect lol, way too little support and far too big of a PITA to bother.

coldcrush390 said:
No worries friend! I almost went crazy last night trying to find a fix!! Here what fixed mine!
You need to be EXTREMELY CAUTIOUS when typing this in:
Go to Advanced in TWRP and run Terminal
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit go
after it pushes through again type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
This worked for me. I tried several other methods from other threads but could not complete them for various reasons.
This also is the simplest method as it installed the update without my having to download it again.

djeddieone said:
Update
I was able to bring the phone back with those commands using adb thank you guys for your help.
Click to expand...
Click to collapse
Did you have any driver issues? I'm stuck in the same situation booting just to ClockworkMod Recovery after an attempted OTA update. Can't connect to Win7 because driver can't configure properly even with the latest drivers installed. Connects file with my wife's working LG G2 so I know the drivers are right. Also tried to get into download mode with no luck. I'm stuck. Does anyone know how to get pass this?

Problem fixed!!!!
eat314 said:
Did you have any driver issues? I'm stuck in the same situation booting just to ClockworkMod Recovery after an attempted OTA update. Can't connect to Win7 because driver can't configure properly even with the latest drivers installed. Connects file with my wife's working LG G2 so I know the drivers are right. Also tried to get into download mode with no luck. I'm stuck. Does anyone know how to get pass this?
Click to expand...
Click to collapse
OK. Finally got it working. Wish I had figured it out before I factory reset my phone. My main issue was the driver. Even though I had the right LG drivers installed, it just would not recognize it properly. Here is what I had to do after a failed device configuration.
- Go to Computer Management and find the failed device and Update Driver.
- Choose to manually select device and then select Have Disk.
- Find and select \Program Files (x86)\LG Electronics\LG VZW United Driver\64BitADB\lgandadb.inf (Tried the other xxxadb.inf files but none worked)
- When the list of devices is presented, scroll down and select LGE Mobile Server Single ADB Interface
Your device should now be recognized by adb. Follow the steps provided by others above in this thread and you should be good to go. Worked for me. Good luck.
Thank you all for the great knowledge base. Saved me $500!!! ::good:

[Q] IOroot 20 help needed it wont reroot my d800

Hi I am a long time lurker and not much of a poster so I don't have my 10 posts so I can use the developers section!!
I have a d800, I initially rooted with the first version of IOroot available for the d800. Up until tonight it has stayed rooted for the most part. There have been a few times when I flashed something in TWRP and it would say that it appeared I lost root would I like it to reinstall SuperSU, I would let it, then reboot and all was well.
Tonight it randomly became unrooted. And in an effort to give all information I did flash the phone with SuperBam about six hours before for the first time, before this happened.
When I attempt to rreroot using IOroot 20, the computer and phone see each other fine. It will not run the batch file and I can't quite make out why since the command prompt closes to quickly. I decide to just do it manually. I type in adb shell and it responds with the proper information. I issue the command to push Su onto the phone and it successfully completes. I then reboot the phone and pull the USB cable when the screen pops up. After I plug it back in I type adb shell, but instead of the # it is a $. I exit and try to run the remaining commands anyways and get this error:Mountperation not permitted.
I am running 8.1 on my PC, it is the same one that initially rooted the phone. Using TWRP and running ProBam with PAEK.
I was told to post the results from four commands to et assistance:
1.adb shell "getprop ro.product.model" LG-D800
2.adb shell "getprop ro.build.target_operator"
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
3.adb shell "getprop ro.lge.swversion" No response
4. adb shell "getprop ro.build.fingerprint" lge/g2_att_us/g2:4.2.2/JDQ39B/D80010d.1376460177:user/release-keys
Since I have worked in IT for 20 years, I know most are just going to say get rid of ProBam. I am hoping someone has seen this resolved without doing yet another reflash. If not I will start redoing it in a bit and I like ProBam. and don't really want to get rid of it.

flash the superuser app via recovery, some roms like omnirom have it linked in first post. That should do the trick. After open superuser app, let it update binaries and it should work.
Sent from my LG-D802 using xda app-developers app

Oh yeah. Thanks I should have seen that one. I better get some sleep
Sent from my LG-D800 using Tapatalk

[GUIDE] Recovering from a bootloop without TWRP or KDZ/TOT

Please note: This will not recover you from a bricked device. This applies to bootloops caused by modifications you made, AFTER successfully rooting.
So you changed your build.prop or deleted a system file you shouldn't have? Your phone is now constantly rebooting? Your variant doesn't have a KDZ available? Here's an easy, albeit time consuming method to recover. (without TWRP or KDZ and no data loss)
First off, if you haven't caused a bootloop yet and you are doing a lot of modifications, do the following. Go to SuperSU and allow su requests on boot. This will allow you to fix minor problems during the bootloop, such as restoring your backed up build.prop or other modified system file. Many times, people will forget to set permissions on a file, especially build.prop. This will cause a bootloop.
If you GRANTED su requests during boot in SuperSU:
Say you set the wrong permissions on build.prop:
While your phone is bootlooping, plug it into your PC, then execute the following commands:
Code:
adb shell
$ stop
$ su
# chmod 0644 /system/build.prop
# reboot
Say you screwed the build.prop up and need to restore a backup you made to your sdcard:
Code:
adb shell
$ stop
$ su
# cp /sdcard/build.prop /system/build.prop
# chmod 0644 /system/build.prop
# reboot
If you DID NOT grant su requests during boot in SuperSU (or if you have tried and failed other methods to recover):
While your phone is bootlooping, plug it into your PC, then do the following:
1. Locate the image you used to root your phone.
2. If the image is on your phone still, just re-root. Your phone will be fixed.
3. If you deleted it from your internal SD card continue to step 4.
4. Open command prompt in folder on your PC containing image, then issue the following command:
This will take a VERY long time (20-30 minutes)
Code:
adb push system_image_name.img /sdcard/system_image_name.img
Note: If you don't have adb mapped to your environment variables, move the image into your platform-tools folder, or whichever folder contains adb. Then run the above command.
5. Re-root

Can't wait to try this when i get home. I soft bricked my LG G4 with a bad system.img so i am trying to restore. Is this actually going to allow me to push the img file back to the phone even though i cant boot?

minirx7 said:
Can't wait to try this when i get home. I soft bricked my LG G4 with a bad system.img so i am trying to restore. Is this actually going to allow me to push the img file back to the phone even though i cant boot?
Click to expand...
Click to collapse
In your case I'd say 50/50. It depends if it at least gets to the part of the boot sequence which enables adb.

I KDZ back to stock, then re-rooted to fix mine. No data loss.
Sent from my VS986 using XDA Free mobile app

Meibs81 said:
I KDZ back to stock, then re-rooted to fix mine. No data loss.
Sent from my VS986 using XDA Free mobile app
Click to expand...
Click to collapse
That is a great method to use, but several variants don't have KDZs :crying:

I'm on the Sprint variant and am getting the Security Error loop. I have no system.img yet, however I can't seem to adb push anything (or see the phone with ADB at all)... am I doing something wrong?

pcrhckyman said:
I'm on the Sprint variant and am getting the Security Error loop. I have no system.img yet, however I can't seem to adb push anything (or see the phone with ADB at all)... am I doing something wrong?
Click to expand...
Click to collapse
That would not be considered a bootloop. That's a brick. I'm sorry, but in your case unless you already had a system image on your phone to flash, you are SOL until we get a TOT file.

tabp0le said:
In your case I'd say 50/50. It depends if it at least gets to the part of the boot sequence which enables adb.
Click to expand...
Click to collapse
Well i am able to access factory reset and i am able to get into download mode and see it from the send_command tool.. HOpe that means my odds are 100% instead!

minirx7 said:
Well i am able to access factory reset and i am able to get into download mode and see it from the send_command tool.. HOpe that means my odds are 100% instead!
Click to expand...
Click to collapse
Not necessarily. Download mode and factory reset(recovery) are located on different partitions than boot and system. Do you at least get to the carrier boot animation while attempting to boot? If so, your chances are good. If not, your chances are bad. The initial commands, including adb push have to be run while the phone is attempting to boot. NOT in download mode or recovery.

tabp0le said:
In your case I'd say 50/50. It depends if it at least gets to the part of the boot sequence which enables adb.
Click to expand...
Click to collapse
tabp0le said:
Not necessarily. Download mode and factory reset(recovery) are located on different partitions than boot and system. Do you at least get to the carrier boot animation while attempting to boot? If so, your chances are good. If not, your chances are bad. The initial commands, including adb push have to be run while the phone is attempting to boot. NOT in download mode or recovery.
Click to expand...
Click to collapse
I get stuck on the LG logo where the light flashes on and off. While this happens if the phone is connected to the computer i hear the USB connection sound in windows. I will be trying it in a few hours.. hope it works!

minirx7 said:
I get stuck on the LG logo where the light flashes on and off. While this happens if the phone is connected to the computer i hear the USB connection sound in windows. I will be trying it in a few hours.. hope it works!
Click to expand...
Click to collapse
You may be able to do it then. Let us know how it goes!

Delete

Peeptastic said:
Can I use this method to solve my particular problem (bypassing setup - I cannot move forward in the setup after a hard reset). Thanks (Can give you more info if you need it)
Click to expand...
Click to collapse
You may be able to. Does your phone boot? How far does it get in the booting process? If you get to initial phone setup, and can't get to the settings app to enable developer options and debugging, then you probably can't use this.. I'm not sure it would work, but you could try-During boot, debugging might enabled by default. (I'm not sure) Right when your bootanimation comes on you might be able to run the command:
Code:
adb shell stop
Then run the rest of the commands/follow this guide. It would be worth a shot.

Delete

Peeptastic said:
I will try it. I can get into the phone to the screen right after entering wifi, then it just stalls. It doesn't freeze, but it also doesn't go anywhere. This is with wifi and data (I left the phone on for a bit and data picked up). If it's related, I turned on Voice Assistance and when the phone gets to the first set up screen she says something about Google play services not working and then "Hangouts needs Google Play services". That could be why I can't move on.....
---------- Post added at 05:10 PM ---------- Previous post was at 05:07 PM ----------
I hear windows chime when it starts up, and the computer charges the phone. Running your command tells me: error: device not found.
Click to expand...
Click to collapse
How did you get in this situation to begin with? Are you able to get into settings at all?

Delete

Peeptastic said:
Factory reset because of the Google play error. Only it looks like Factory reset didn't fix it. And nope, can't get into settings because I can't get out of the set up screen (setup like when you first turn on the phone out of the box). I can get to download mode and stock recovery. As far as I know, there is no way to skip the original LG setup (clockwise button press doesn't work).
Can I adb sideload the image and try that way
Click to expand...
Click to collapse
Unfortunately that will not work. adb sideload is only for flashing .zip files.

tabp0le said:
Unfortunately that will not work. adb sideload is only for flashing .zip files.
Click to expand...
Click to collapse
Delete

every time I run the command while in bootloop it says "Device not found"

sarwaria23 said:
every time I run the command while in bootloop it says "Device not found"
Click to expand...
Click to collapse
This is what is happening to me too. I can see that the phone during boot loop is recognized. I check the device drivers and it shows up under windows as LG.
Crap. not good.

Root H830 running 20A and 20C [Nougat] AutoMagically (Custom Easy Recowvery Script)

I posted this as a reply originally. Then thought it probably should be a thread so it can help as many people as possible! Let's get the custom kernels and ROMs going for this beautiful device!
You will need to already have Android 20A (C should be fine as well) stock image installed, and the bootloader unlocked [Plenty of easy help via Google won't cover that here]
You can use the Recowvery Method on 20A (Nougat) (again this should be the same for 20C) with the H830. Below is the script I used with supersu and no-verity script included. Plug-in the device to your Windows machine. Install LG drivers, and remember to unlock screen and authorize the computer via the Device's screen so ADB commands can run (unnecessary tech note: you could open command prompt cd to where this is and use it's ADB to run adb devices (if you don't understand that no worries skip it)). After that just run the script and follow the menus. Answer yes when asked if you're sure you wish to continue, and done. I hope you find my work helpful .
I used this guy's script [Easy Recowvery ALL CREDITS TO THE AUTHOR I'M JUST SUPPLYING AN H830 SPECIFIC PACK WITH NEEDED FILES THAT I VERIFIED FULLY WORK. PLEASE GO RATE HIS THREAD AND CLICK THANKS IF THIS WORKS FOR YOU!]: http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
DON'T FORGET
This should work granted you have the drivers installed, and Windows has finished installing them, you tapped the prompt on your device screen to allow the adb connection, and you run script as administrator, and you restart the computer if you run adb commands yourself and aren't comfortable checking task manager to kill any and all running adb instances (could also issue the stop server command too), but if unsure of any or all of that last statement, restart
Of note answer yes when it says this isn't a V20 are you sure you wish to continue?. Also, as stated in notes I had to actually run it twice for it to stick for me (I'm sure I rushed the first time or something).
I took the time to create an H830 package of the script version with the files that worked for me. Out of respect I changed nothing aside from adding the needed files and throwing quick notes in the readme.md (bottom of file) file. (PLEASE read it, if you have issues read it you missed something). You will also still need to type yes when it states this is not a V20; Do you wish to continue? <Yes>.
. I used this package to root my H830 after the Nougat OTA killed my root access so
SHOULD WORK ON ANY H830 RUNNING STOCK 20A (should work with 20C) [NOUGAT] Read the following paragraph if you skip the rest
Read the readme.md file found in root of archive (see bottom of file).
Start it up hit like 5 for TWRP and supersu (or there's another menu option for just supersu or just TWRP whatever you desire).
Answer yes to the prompt to continue.
Now wait for the magic (again not mine this is the authors work)).
Once done you can download a reboot to recovery app or widget (or root checker) and verify that you're good to go.
If it doesn't take the first time you may need to run it again. DON'T FREAK OUT, RUN SCRIPT AGAIN IT CAN TAKE MULTIPLE RUNS.
Don't forget to install BusyBox (Stericson installer recommended and I use /su/bin personally (/su/xbin should also be fine) Since we're talking stock here generally I like to minimize any changes to /system if it can be helped personally; so I haven't tried running BusyBox from any /system mount) as this is a stock ROM.
Kernel Adiutor works and yes I recommend leaving thermald enabled as your thermal governor unless you flash a custom kernel (not included)
Manual Boot to Recovery:
Start With phone off (pinch battery button and re-insert battery if you can't otherwise shut it down or are lazy like me )
Hold both Power AND Volume Down at same time
1-2 seconds in to seeing LG Logo release and hold power button while continuing to hold volume down the entire time...
Release once you see white screen prompting yes or no to wipe user data (don't freak) ¹
use volume key to highlight yes
Hit Power key (think enter)
¹(If you have factory recovery this WILL format all user data and settings you've been warned. Only way to boot to stock recovery is to use app, widget, or terminal/adb command (reboot recovery). I don't know of any manual physical button methods to access stock recovery directly.).
You should now see TWRP Loading and can release any keys if you're holding any down still (once white wipe screen is seen you should release the keys)
Sweet, the file is small enough to be attached to this post directly, Enjoy! Also it's a 7-zip archive. It's available for every OS. For Android if you use ES File Explorer the first time you try to use a 7z file it'll offer to download plug-in, and you're good to read/write 7z archives (best compression almost always imho).

It doesn't seem to work for me, it reboots and the little android says No Command. Any suggestions?

well I ran the script ,Im afraid what was happening earlier is happening here to,when the script tries to flash Supersu it reboots to Firmware Update screen,Im fairly certain thats not right...am I correct? Gonna try to pull out (lol) before that screen loads like I did with the other method...

Ahhh I miss being able to root without a PC. I don't own one ?

Can anyone confirm this works fine? I won't have time for troubleshooting if it doesn't..

Jonathanpeyton said:
well I ran the script ,Im afraid what was happening earlier is happening here to,when the script tries to flash Supersu it reboots to Firmware Update screen,Im fairly certain thats not right...am I correct? Gonna try to pull out (lol) before that screen loads like I did with the other method...
Click to expand...
Click to collapse
Sounds like your hope would be if someone made a tot with root for 20A

shaneg79 said:
Sounds like your hope would be if someone made a tot with root for 20A
Click to expand...
Click to collapse
unfortunatley, I think that may be the only way Ill ever get my oddball device to accept TWRP....

WiiR0cKz said:
It doesn't seem to work for me, it reboots and the little android says No Command. Any suggestions?
Click to expand...
Click to collapse
same issue i turned off integrety check and ran it again it worked fine

Alpha_wolf said:
same issue i turned off integrety check and ran it again it worked fine
Click to expand...
Click to collapse
Where did you find integrety check
Sent from my LG-H830 using Tapatalk

Hi, thanks you for this post. I tried to use this script and I got an error saying that I am missing files in the "exploit" directory...please see the attached screenshot. Any ideas? Thanks.

famous145 said:
Where did you find integrety check
Sent from my LG-H830 using Tapatalk
Click to expand...
Click to collapse
hit 5 in the main screen it should be there

Can someone please help me unlock my bootloader now that I am running nougat! TIA fellow peeps!

Is this working for everyone / anyone? Most posts so far seem to have issues...

Alpha_wolf said:
hit 5 in the main screen it should be there
Click to expand...
Click to collapse
I did this but am still getting the no command issue

This method worked for me after about 5 failed attempts. The OP guide is not very clear, I might write my own and post it today.

aanonymoushuman said:
This method worked for me after about 5 failed attempts. The OP guide is not very clear, I might write my own and post it today.
Click to expand...
Click to collapse
Please!
When you say failed, did you get the no command issue as well,or something different?

Dumboguy03 said:
Please!
When you say failed, did you get the no command issue as well,or something different?
Click to expand...
Click to collapse
I did get the no command issue in recovery, the first time I did it, disabling integrity verification solved the problem when I did my next time, but I got some other issues before this solution worked.

My problem is, i am on Mac in parallels i can't list my phone in adb devices command. it shows as empty. Installed every possible app scenarios but still looks empty

Check out my guide on rooting Nougat, https://forum.xda-developers.com/lg-g5/how-to/guide-root-stock-n-using-jcadduonos-t3529093

Can confirm this does work. Took me 30 tries but it worked!