[ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED)

Search This thread

minhtuan990

Member
Dec 21, 2011
21
1
i found here
there is a solution for sale but now I am having a very difficult time, can't afford to buy, please help me any solution to break the password in the video's description file
 

minhtuan990

Member
Dec 21, 2011
21
1

Attachments

  • IMG_20220421_143835.jpg
    IMG_20220421_143835.jpg
    1.2 MB · Views: 14
  • IMG_20220421_143921.jpg
    IMG_20220421_143921.jpg
    1.5 MB · Views: 15

Darnrain1

Senior Member
Jan 2, 2018
470
134
USA
I installed twrp-3.3.1-0-h910.img and flashed rom H910_20g_Oreo_full_rooted.zip, the screen is like this, please help me
That is normal don't worry. First you need to take you time don't panic. I know how to fix this.

Yeah it looks like you didn't flash Auto_Debloat_H910_20g_only_v7.8_flashable.zip

Okay because you only flashed the rom you now do not have twrp installed on your phone. So what you need to do is go into flastboot mode flash twrp again reboot back into twrp. Start at step one from the Installation Instructions read them first please then follow them. Take your time you will get this fixed.

Your phone is rooted but has only stock kernel no twrp installed but you should be able to get into flastboot mode by turning off phone, holding the down vol button down and plugging in usb to computer.

flastboot flash recovery twrp.img
fastboot reboot

take battery out

go into twrp

start at step 1 read all instructions first then follow them.

And if you still can not get signal then You need to call AT&T and have to enable VoLTE and wifi calling on there side. But this version of Oreo VoLTE works on the H910.
 
Last edited:
  • Like
Reactions: minhtuan990

minhtuan990

Member
Dec 21, 2011
21
1
That is normal don't worry.

Yeah it looks like you didn't flash Auto_Debloat_H910_20g_only_v7.8_flashable.zip

Okay because you only flashed the rom you now do not have twrp installed on your phone. So what you need to do is go into flastboot mode flash twrp again reboot back into twrp. Start at step one from the Installation Instructions read them first please then follow them. Take your time you will get this fixed don't worry.
i didn't flash Auto_Debloat_H910_20g_only_v7.8_flashable.zip, what should i do now, please help, but i wait for a while it also goes to the main screen but the waveform still shows the cross mark, no signal
 

Attachments

  • IMG_20220421_145509.jpg
    IMG_20220421_145509.jpg
    1.1 MB · Views: 9

Darnrain1

Senior Member
Jan 2, 2018
470
134
USA
i didn't flash Auto_Debloat_H910_20g_only_v7.8_flashable.zip, what should i do now, please help, but i wait for a while it also goes to the main screen but the waveform still shows the cross mark, no signal
I added more to my notes press F5 look up one level. Okay maybe two levels.

It's getting late I am heading to bed. If you still need help Message me and I will get back to you tomorrow. you got this.
 
Last edited:
  • Like
Reactions: minhtuan990

Darnrain1

Senior Member
Jan 2, 2018
470
134
USA
i didn't flash Auto_Debloat_H910_20g_only_v7.8_flashable.zip, what should i do now, please help, but i wait for a while it also goes to the main screen but the waveform still shows the cross mark, no signal
I just flashed Nougat again on my H910 "h910_root_pkg.zip" rom. After flashing the h910_root_pkg I also flashed these files.

H910_BTTF-mk2000.zip
and
Magisk-v19.0.zip
and
twrp-3.3.1-0-h910.img


My cell signal is strong and working.

You just need to call AT&T.


taken from link

"I've been on LOS for ages, have to move back to Oreo for VoLTE, and I've tried this several times in several different ways and I never get cellular service working. I've flashed rooted 20g, rooted 20i, 910 oreo modem files, my original backup modem files, writing after factory reset, writing after wiping system, just still no cellular. On LOS I was getting cellular connections, just not calls since it doesn't do VoLTE.

I've followed the instructions to the letter, on top of trying other things, does anyone have ideas? Do I have to go all the way back to Nougat or something like that?

Thanks for your time."



"Ya'll were right, it was on AT&Ts end, it just coincided with reflashing the phone in a way that made me think I had done the process wrong. Eerie, but solvable.

I really appreciate it, I'm back on Oreo, debloated, and now need to dial this thing back in; I've been using LOS so long I don't know where to start, but I've got VoLTE and Wifi calling back, so that's what this was for.

I really appreciate your efforts here, thanks so much!"
 
Last edited:

minhtuan990

Member
Dec 21, 2011
21
1
I just flashed Nougat again on my H910 "h910_root_pkg.zip" rom. After flashing the h910_root_pkg I also flashed these files.

H910_BTTF-mk2000.zip
and
Magisk-v19.0.zip
and
twrp-3.3.1-0-h910.img


My cell signal is strong and working.

You just need to call AT&T.


taken from link

"I've been on LOS for ages, have to move back to Oreo for VoLTE, and I've tried this several times in several different ways and I never get cellular service working. I've flashed rooted 20g, rooted 20i, 910 oreo modem files, my original backup modem files, writing after factory reset, writing after wiping system, just still no cellular. On LOS I was getting cellular connections, just not calls since it doesn't do VoLTE.

I've followed the instructions to the letter, on top of trying other things, does anyone have ideas? Do I have to go all the way back to Nougat or something like that?

Thanks for your time."



"Ya'll were right, it was on AT&Ts end, it just coincided with reflashing the phone in a way that made me think I had done the process wrong. Eerie, but solvable.

I really appreciate it, I'm back on Oreo, debloated, and now need to dial this thing back in; I've been using LOS so long I don't know where to start, but I've got VoLTE and Wifi calling back, so that's what this was for.

I really appreciate your efforts here, thanks so much!"
Can you give me the link to download your H910 "h910_root_pkg.zip" rom, I'm in Vietnam, how can I call at&t
 

Darnrain1

Senior Member
Jan 2, 2018
470
134
USA
Can you give me the link to download your H910 "h910_root_pkg.zip" rom, I'm in Vietnam, how can I call at&t
That's what I like to call a typo. I meant h910-10r.zip that's the rom I used. But if your not in the US and your using the H910 outside of the US then I don't have any knowledge of how to get it working sorry. Maybe call the provider that your trying to use the H910 on over there?
 

mp42409

New member
Apr 12, 2012
3
0
SANTO DOMINGO
I have a ATT lg v20 (LG-H910) with Android 7 Security Patch Sep 1, 2016 Build# NRD90M, Software Version H91010c. should i update to a more desirable version of Android OS to install LOS or proceed with this guide?
 

Darnrain1

Senior Member
Jan 2, 2018
470
134
USA
I have a ATT lg v20 (LG-H910) with Android 7 Security Patch Sep 1, 2016 Build# NRD90M, Software Version H91010c. should i update to a more desirable version of Android OS to install LOS or proceed with this guide?
Hello, You can use this guide it works, you have to downgrade your firmware to a compatible version that works with dirtysanta root. Some of the links are broken. Make sure to make a dump backup before you downgrade your firmware it has your EFS.

h910_root_pkg.zip "DirtySanta root package"
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
h910-10r.zip The Nougat rom
 
Last edited:

dornz

Senior Member
Feb 19, 2013
535
93
Yes downgrade and go through steps it does work!! but unfortunately I don't posess that phone anymore
 

commshop

Member
Jan 9, 2011
14
1
Have V 20 H910. All files used and installed are downloaded from this thread for compatibility reasons.
Downgrade using LGUP to H91510e works fine.

2 terminals opened both in dirtysanta folder. Phones Developer & USB Debug on. Terminal app installed on phone.
1) In Terminal1 - adb logcat -s dirtysanta executes (this does not drop to prompt - appears waiting)
2) In Terminal2 - STEP1.BAT ends in a shell of my H910.
3) In Terminal2 - run-as con (changes shell prompt from $ to #) but
chmod 0777 /storage/emulated/0/* fails to make all files in /0 readable, writable and executable. "ls -l" proves this. CHMOD Fails.
4) In Phone Terminal - applypatch executes and drops to a prompt but Terminal 1 never displays to run step 2. (It remains waiting) Also terminal 2 remains in a shell & requires exit command twice to execute STEP2.BAT (No mention of this in instructions)
5) In Terminal 2 (after 2hr wait and no sign from Terminal 1 to proceed) I exit the shell and run STEP2.BAT. Phone goes into Fastboot mode.
6) Once phone in Fastboot mode all ADB connection is lost. All ADB command fail. ADB Devices shows no device available.
7) In Terminal 2 - I run STEP3.BAT but prompt remains in (waiting for device) it never proceeds, Understandable since all ADB devices are not available in Fastboot mode.

I much rather execute ADB commands from the CLI and the BAT files have simple ADB commands but How to execute ADB cmd's while in Fastboot mode is beyond me.

Remove battery and reboot results in scrambled screen and inability to do anything on phone. To fix I revert to Partition DL in LGUP w/ H91510e KDZ file. This puts me back to square 1. Many attempts result in same.

How should I proceed I wonder?
 
Last edited:

dornz

Senior Member
Feb 19, 2013
535
93
Have V 20 H910. All files used and installed are downloaded from this thread for compatibility reasons.
Downgrade using LGUP to H91510e works fine.

2 terminals opened both in dirtysanta folder. Phones Developer & USB Debug on. Terminal app installed on phone.
1) In Terminal1 - adb logcat -s dirtysanta executes (this does not drop to prompt - appears waiting)
2) In Terminal2 - STEP1.BAT ends in a shell of my H910.
3) In Terminal2 - run-as con (changes shell prompt to $) but
chmod 0777 /storage/emulated/0/* fails to make all files in /0 readable, writable and executable. "ls -l" proves this. CHMOD Fails.
4) In Phone Terminal - applypatch executes and drops to a prompt but Terminal 1 never displays to run step 2. (It remains waiting) Also terminal 2 remains in a shell & requires exit command twice to execute STEP2.BAT (No mention of this in instructions)
5) In Terminal 2 (after 2hr wait and no sign from Terminal 1 to proceed) I exit the shell and run STEP2.BAT. Phone goes into Fastboot mode.
6) Once phone in Fastboot mode all ADB connection is lost. All ADB command fail. ADB Devices shows no device available.
7) In Terminal 2 - I run STEP3.BAT but prompt remains in (waiting for device) it never proceeds, Understandable since all ADB devices are not available in Fastboot mode.

I much rather execute ADB commands from the CLI and the BAT files have simple ADB commands but How to execute ADB cmd's while in Fastboot mode is beyond me.

Remove battery and reboot results in scrambled screen and inability to do anything on phone. To fix I revert to Partition DL in LGUP w/ H91510e KDZ file. This puts me back to square 1. Many attempts result in same.

How should I proceed I wonder?
H
Yes downgrade and go through steps it does work!! but unfortunately I don't posess that phone anymore
Hi at step 3 I did not run a command in cmd I double clicked on bat file in explorer as I was on Windows os when rooting hope that helps as I rooted two or three time with that method so try the file explorer way
 

commshop

Member
Jan 9, 2011
14
1
H

Hi at step 3 I did not run a command in cmd I double clicked on bat file in explorer as I was on Windows os when rooting hope that helps as I rooted two or three time with that method so try the file explorer way
Hi dornz, Your reply is much appreciated. I am going to do as you say. I understand STEP3.BAT is run from file explorer and not cmd window per this threads instructions. I hope that's right. After 2 days and uncountable runs at this process with nothing but the same failing result, All insight & comments are appreciated.

Here is what I anticipate dornz: Since STEP2.BAT puts phone in fastboot mode, no matter how STEP3.BAT is executed (from cmd window or file mgr, I anticipate (Waiting for device failure). I say this because STEP3.BAT is full of fastboot commands and since device is not found, fastboot and adb commands all fail. (Just my 2cents worth) I've been surprised in the past and will not ignore your suggestion. I'm on it and will post the results when done. Thanks again dornz. I appreciate you. Cheers, CommShop
 

dornz

Senior Member
Feb 19, 2013
535
93
Hi dornz, Your reply is much appreciated. I am going to do as you say. I understand STEP3.BAT is run from file explorer and not cmd window per this threads instructions. I hope that's right. After 2 days and uncountable runs at this process with nothing but the same failing result, All insight & comments are appreciated.

Here is what I anticipate dornz: Since STEP2.BAT puts phone in fastboot mode, no matter how STEP3.BAT is executed (from cmd window or file mgr, I anticipate (Waiting for device failure). I say this because STEP3.BAT is full of fastboot commands and since device is not found, fastboot and adb commands all fail. (Just my 2cents worth) I've been surprised in the past and will not ignore your suggestion. I'm on it and will post the results when done. Thanks again dornz. I appreciate you. Cheers, CommShop
Sorry about that, It does work though I had three of them devices and rooted them all should be some pics on here somewhere
 

commshop

Member
Jan 9, 2011
14
1
Hi dornz, Your reply is much appreciated. I am going to do as you say. I understand STEP3.BAT is run from file explorer and not cmd window per this threads instructions. I hope that's right. After 2 days and uncountable runs at this process with nothing but the same failing result, All insight & comments are appreciated.

Here is what I anticipate dornz: Since STEP2.BAT puts phone in fastboot mode, no matter how STEP3.BAT is executed (from cmd window or file mgr, I anticipate (Waiting for device failure). I say this because STEP3.BAT is full of fastboot commands and since device is not found, fastboot and adb commands all fail. (Just my 2cents worth) I've been surprised in the past and will not ignore your suggestion. I'm on it and will post the results when done. Thanks again dornz. I appreciate you. Cheers, CommShop
DONE! Executed STEP3.BAT from windows file explorer and got a terminal window "waiting for device" as I expected. Since devices do not respond to ADB and FASTBOOT commands when in Fastboot mode, it failed like the dozens of attempts I have made to run this process per this threads instructions.

I am going to skip STEP2.bat & run STEP3.BAT individual fastboot commands in CLI as a test. Since phone is not in fastboot mode fastboot CLI commands should take. I will report back with results.

--Well that was big failure. Seems fastboot commands are not accepted although adb devices shows device available. I did notice, although Developer options Enable OEM Unlock is enabled, My STEP2.BAT fastboot screen shows: Lock State - Locked.

If bootloader is locked, perhaps this is the issue. I wonder how to unlock?

UPDATE: Nov-2

Yesterday, Using the Win machine above and a Linux laptop. DirtySanta root succeeded w/ the following:
Windows machine would never put my LG V20 into fastboot mode. <waiting for device> was the problem.
I was never able to fix Win Wkstn from passing Step2.bat cmd of (adb reboot bootloader)
Windows Drivers issue? Don't know.

Here's what I did:
All cmds within the .bat files entered manually from Win command prompt from .step 1
These commands are adb push and shell commands. On LG V20 terminal app, the adb shell, run-as con & the chom cmds all entered and good.

Since Win Wkstn fastboot devices commands never showed my device, I moved phones USB cable to my Linux laptop.
I made sure the ADB stack was current ( turns out it was the same version as on my Win Wkstn.)

Fastboot devices command shows the LG attached. Phew! I can now enter the fastboot commands in step3.bat.
Entered the Step3.bat commands manually and Viola! I am so happy to have a rooted H910.

From Linux wkstn I entered the Step2.bat command of adb reboot bootloader.
If I remember correctly this puts LG in Fastboot mode (Tiny red text Fastboot)

I did several steps different since I didn't want a ATT's stock Oreo.

I mixed this post instructions with that of Lemondrop Debloated ROM for H910/

Changes made:
Post #1 in this thread says: Flash the zip. Choose "Install" and browse to your SD card, and select the h910-10r.zip

I assume h910-10r is an Oreo file? Don't know but I wanted to find a VOLTE supported custom ROM and found none.
The next best thing was a debloated Oreo w/ VOLTE support and Lemondrop fit the bill.

Instead of flashing h910-10r.zip from this thread, I flashed: H910_20g_Oreo_full_rooted.zip from the following post:

From this step forward I stayed on the Lemondrop post, followed the instructions and all worked. IMPORTANT: Do the required backup dump within LGUP from this thread. (Lemondrop post instructs to restored the modem files and the backup is your means to secure the files you need. (This is key in restoring VOLTE for the H910)

Thank you to all who helped me in this 2month journey. Cheers to all.
 
Last edited:

tcpipnet

New member
Oct 6, 2022
2
0
Download this modified (by modified, I mean it contains all the extras needed to make this work) DirtySanta root package: link.

file no longer available
 

baugen55

Member
Oct 17, 2022
38
2
Re original method I forgot the DUMP step. Phone still works seemingly fine but no signal.
Should i do it again with dump step? ok it was just backup well too late :)
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 86
    ***WARNING***
    This is ONLY for the H910. If you flash H915 firmware on an H918 -- you WILL brick it.​

    If you are currently on Oreo, you can root your phone, but you CAN NOT keep Oreo - for now. This will downgrade you back to Nougat, which is rootable.

    I know this is a long post, but this is also a complicated root procedure. Please read the ENTIRE post before starting.
    Also, if you run into a problem, please use the search thread box to see if your problem has already been addressed. It will save having to ask the same questions over and over.

    If you want to restore to stock v10q after rooting, you can use this: link.

    Standard disclaimer: There are no guarantees in life. No part of this should brick your phone, but if it does somehow, that is on you.

    This should work on any H910 version, up to v20g, that is no longer rootable by DirtySanta (IE: dirtycow has been patched). It has been tested on 10m to 20g

    • Make sure that you have an SD card that has at least 8 gigs of free space. It CAN NOT be formatted FAT, or FAT32. It needs to be exFat or ext4, otherwise the zip won't fit (2 gig file limit on FAT and FAT32).
    • Make sure you have a working adb environment. I use Linux so hopefully this is a good resource. If not, you will have to Google this yourself: link.
    • Make sure that you have a working WiFi connection. Part of this process involves installing a terminal emulator. Since the phone will have no signal at that time, you use WiFi, or you can side load.
    • Download the H915 v10e KDZ: H91510e_00_VTR_CA_OP_1205.kdz.
      - WARNING: Do not use any newer H915 firmware, as they all have dirtycow patched (v10p, v10q), and I do not know if they increment ARB.
      - If they do increment ARB, then you will be stuck with a phone that can't be rooted, and you can't fix the modem! You have been warned.
    • Download the patched LG UP from this thread: link.
    • Make sure you install it in C:\Program Files (x86)\LG Electronics\LGUP or it will either read the wrong model file (if you had a previous installation of LG UP), or it will not be able to find the model file at all.
    • Put your phone into download mode (power off / hold vol. up / plug in USB cable)
    • Use LG UP to dump your phone. When you run it, there will be additional radio buttons.
      - Pick the one that says DUMP and click Start. You will be asked what partitions to dump, click the "select all" checkbox, and then you can uncheck userdata.
      - This is an OPTIONAL but HIGHLY recommended step. It is a good idea to have a full backup of your phone, but with this new procedure, this is no longer needed.
    • When it is finished, click the PARTITION DL radio button, pick the H915 v10e KDZ that you downloaded above, and click start. Make sure all partitions are checked.
    • Once it is complete, your phone should reboot into a nice new (old) Freedom Mobile ROM (complete the setup), and you may not have signal.
      - If you are on AT&T I understand that you will, but T-Mobile does not. Either way, this is normal.
    • Before continuing, make sure that you enable developer mode, and enable USB debugging. Also, make sure that your PC is authorized (plug the phone in and touch always allow, and then OK).
    • Also go ahead and download a terminal emulator -- NOT Termux. I recommend good old "Terminal Emulator for Andorid" -- the first thing that pops up if you search for "terminal"
    • Download this modified (by modified, I mean it contains all the extras needed to make this work) DirtySanta root package: link.
      - Extract this somewhere that you can run adb and fastboot from.
      - Check the SHA hash: 88a3a0f90c66a486807da3e69e9fb0a08c779efe
    • Download the v10r firmware + boot + system here: link (sorry - no time to dump and package 10v)
      - Check the SHA hash: 5451146030393e490dcfba3558b620badefe75cd
      - This includes v1.0 of the mk2000 kernel
    • Copy the zip, to your SD card, and insert it in the phone.
      - Alternatively, you can use adb to push the zip to your phone while in TWRP. This is NOT supported.
      - I switched to having people flash from SD card because too many people were having problems with adb.
      - If you want, try it, if it doesn't work, don't ask for help -- use the SD card method!
    Open two command windows. In each one change to the directory that you extracted the root package.

    In the first one execute:
    Code:
    adb logcat -s dirtysanta

    Then in the second one execute:
    Code:
    STEP1.BAT

    Wait till you get a prompt back then type (or copy / paste):
    Code:
    run-as con
    chmod 0777 /storage/emulated/0/*

    Now open up your terminal emulator on your phone and type:
    Code:
    applypatch /system/bin/atd /storage/emulated/0/dirtysanta

    Watch the window that has logcat running. When it says to run step 2, execute:
    Code:
    STEP2.BAT

    Once fastboot comes up -- it will be a really small red font that says, FASTBOOT MODE. Once that is up, execute:
    Code:
    STEP3.BAT
    This is flashing TWRP and the WW 2.0 kernel onto your phone. The phone will reboot once they are flashed.
    When it reboots, you will get a very nasty looking warning about the fact that your phone has been compromised and will not boot.
    This is due to running the engineering aboot and is normal -- don't panic your phone will boot. You will see this every time the phone reboots.

    At this point, you have H915v10e and TWRP. You can now boot into TWRP so that we can flash the H910 firmware back onto the phone:
    If you have re-enabled developer mode, and enabled USB debugging, and have your phone connected, you can execute the following in a command window:
    Code:
    adb reboot recovery

    Otherwise just pull the battery, put the battery back in, hold vol down + power till the LG logo appears. Release power, and then immediately press and hold it again until you get to a screen that asks if you want to factory reset your phone. Say yes twice and it will take you into TWRP. If the phone had the stock recovery, it would do a factory reset -- however, since you now have TWRP, that is what you are taken to instead. This is a key combination that is embedded into the bootloader that tells it to execute recovery - in this case TWRP. Hope that clears up some confusion as to why you get a screen asking you to factory reset your phone...

    Now that you are in TWRP you need to do a couple of things:

    • Format data. Wipe -> Format data. It will ask you to type "yes". If you don't do this, you will be prompted to enter a passcode, and will have 30 tries. If that happens, just boot back to TWRP and do this step again.
    • Wipe cache / dalvik cache
    • Flash the zip. Choose "Install" and browse to your SD card, and select the h910-10r.zip file. When complete hit the home button.
    • Now, format data again for good measure....

    Once the second format completes you can reboot your phone, and it will be just like you got it fresh off the factory floor, except it will have TWRP.
    No part of the H915 firmware is left on the phone. The only things that are not 100% stock v10r firmware are ABOOT (it is the US996 engineering aboot that is unlocked. It also gives the nasty warning on boot), BOOT (it is the 10q kernel with a few patches added by @askermk2000 - KCAL, Adreno idler, etc), and of course RECOVERY (TWRP).

    It takes a little while for the first boot -- be patient. It should NOT take longer than 10 minutes. If it does, something went wrong. Boot back to TWRP and try flashing the 10r zip again.

    Now that you have a phone with TWRP, feel free to download whatever root method you would like (SuperSU or Magisk).



    Old, unsupported ROMs will NOT work with the 10p, 10q or 10r firmware.
    If you want to run NATF or WETA (or any old, unsupported ROM that you find floating around these forums) you will need to flash the older 10m firmware: here.
    SHA: 1007dedb6e935b0bea1e25f28e39ccb8e69f9694
    This is JUST the firmware! It has no kernel, or system. You MUST flash a 10m or earlier ROM or your phone will not boot. If you forget, you can always boot back to TWRP and try again.
    The newer kernel should work, but I have not tested it with the older firmware. If it doesn't grab the WW2.0 kernel, it works fine with 10m.


    For the latest kernel, please visit @askermk2000's thread: here

    Do NOT flash firmware for the H918 -- it will brick your phone. Firmware for the other models won't work, but they won't brick your phone.

    Feel free to ask away if any of this doesn't make sense. I really hope that isn't the case now :)

    Most of all -- have fun. That is what this is supposed to be about!


    Again, If you want to restore to stock v10q, you can use this: link.

    Serious credits go out to:
    @me2151 for DirtySanta. Please visit his original thread and hit the thanks button.
    @smitel for Reversing LG UP and figuring out how unlock lab mode. No partition dl, no root on the new firmware. Again, hit the thanks button.
    @Prowler_gr for patching LG UP for the V20 not to mention finding that thread. I never go into the G5 forums, so I would have never seen it. AGAIN -- hit that thanks button.
    @USA-RedDragon for his Werewolf kernel. I know I sure like not having static on boot. Most people get the ability to hit thanks 6 or 7 times a day -- be sure to use up one more.
    @askermk2000 For the new 10q kernel. Dude doesn't even have a V20 and jumped in to help out.

    Seriously, these guys are the real devs, and the ones that have left the V20 scene are missed...

    -- Brian
    8
    FAQ:

    Q1: If I revert to stock will AT&T know that I rooted my phone?
    A1: Nope. Unlike Samsung phones (at least older ones, I don't know about current ones), there is no KNOX style indicator that shows how many times a phone has been flashed.

    Q2: Do we have to flash ALL of the H915 firmware, that seems like a waste?
    A2: You would be correct -- it is a waste, but I am going to need more time to test and make sure that only the XBL and ABOOT need to be flashed AND that doesn't break trusted boot. As I have stated, the H910 and H915 have the same PBL. I ran my phone with the H915 XBL, with the rest of the firmware being H910 and I don't have a brick -- but I did it manually and not though LG UP. When I feel like wiping my phone again, I will test this.

    Q3: Can any other variants be rooted with this method?
    A3: Maybe. I was able to get the patched LG UP to recognize a KDZ that I modified, and it let me flash. My next step is to completely roll my own KDZ. If that works, then ANY LG phone will be rootable simply by flashing a KDZ.
    A3: YES! It turns out that the LS997 is able to use the VS995 KDZ. I have written up a post on the procedure.

    Q4: If that works, and you can roll your own KDZ, can you get around ARB?
    A4: I believe so. Now that we have the ability to take a dump of an unmodified / stock / out of the box phone, we could dump the XBL (this is what updates ARB), and package that up with an older ABOOT. I am mainly talking about H918s here, since all other V20s work with the engineering ABOOT. But it will also apply if AT&T ever increments ARB on the H910.
    Nope, there is no getting around ARB. Once a particular ARB version is blown into your QFPROM, you *MUST* use a boot stack that has that ARB version, and that is basically the entire firmware except for boot, recovery, laf and system.

    Q5: Will the AM&FM Radio still work
    A5: Yes.

    Q6: Why are my boot times longer after rooting?
    A6: In order to unlock the bootloader, an engineering aboot had to be used, and a lot of additional data is generated on boot.

    Q7: Can I return my phone to stock?
    A7: This was addressed in the post above, but I will address it again. Yes. For the link, see the post above.
    5
    Jerry SQ to the rescure, follow these steps to fix signal and data (h910 only):
    1 Dowload US99610f.kdz and F800K10e.kdz firmware, LGUP with patch in the first post
    2 KDZ F800K10e.kdz, partition dl, tick select all, wait for it to boot into rom, install TWRP with dirtysanta steps, boot into TWRP, then select reboot, select bootloader (or using adb, your choice, but the bootloader need to be unlocked)
    3 type these codes in booloader
    fastboot erase modemst1
    fastboot erase modemst2
    4 wait till it done, don't rebooted the phone yet, instead, pull the batterry out, get back to TWRP by hardware button
    5 format your rom, reboot back to TWRP, wipe Cache, System, internall storage, then poweroff the phone
    6 get in dowload mode, KDZ US996 firmware, partition dl, tick select all, boot into rom, if it stuck somewhere, factory reset might do the trick
    7 when it boot up, it will get bootloop after you get in the setup screen (i don't know it'll happen to you, but for me it'll bootloop)
    8 pull battery out, get in dowload mode, KDZ F800K firmware, partition dl, TICK MANUALLY EVERY THING EXEPT BOOT, MODEM, ABOOT, ABOOTBAK
    9 when it done, you will have signal, data mobile again, if you like, you can use F800K firmware or you can follow dirtysanta steps and install any rom you like
    5
    @runningnak3d could you update the link from DirtySanta root package?

    all the root files for this thread are in my AFH (in my signature) the root package is here >> https://androidfilehost.com/?fid=1322778262903990218
    4
    Kernel with some features

    Ok :)

    This one is a bit more experimental. I've looked at some patches from Werewolf and D.O.T.S Kernel, and picked a few compatible ones that looked rather straight forward without risk of complications.

    So we have:
    KCAL - the one that started it all.
    Adreno Idler - Battery savings.
    Disable software CRC checking of SD Card - More performance.
    Remove temperature polling - Battery savings.
    Reduce DSI status check - Battery savings.
    Fixed USB erratic behavior with some chargers.
    Static Screen fixed.
    RCTD removed.

    ^^Let's hope it works :) Would welcome feedback.
    If it works nicely I'll make one for H918 as well.

    --removed-- Look here!