[ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED)
- Thread starter runningnak3d
- Start date
Hello, I'm a newb at this and I'm slowly trying to learn how to root my V20 H910. Kinda embarrassing but I seem to be having trouble with the ADB part. I downloaded ADB and it's in the platform-tools directory. I extracted the root package with the dirta santa and step.bat files into the platform-tools directory. In powershell, when I type ".\adb logcat -s dirtysanta", nothing happens. What do I do exactly? In fact, when I type ".\adb devices", it just lists my phone's model number instead of the serial number. Is that supposed to happen? Any help would be appreciated. My main goal is to just have the 10q stock rom into my device.
there is no ".\" only "adb logcat -s dirtysanta" make sure your in the same directory as the adb.exe file and the setup1.bat setup2.bat setup3.bat
Also if that does not work make sure you open a command prompt as the administrator. I am not sure about powershell.
Hi, sorry for the lack of response. I've been kinda busy the past few days but now I'm ready. Well I typed "adb logcat -s dirtysanta" in CMD instead of Powershell and it still does the same thing. After I type it and press enter, the cursor just goes to the next line and blinks without anything happening and it just sits there. I did run CMD as administrator.
My guess is there might be something wrong with the ADB installation. I know it's the platform-tools download file. I'm pretty sure I have all the Google drivers and LG Mobile drivers updated, although I'm not really sure.
Also, I have a slight change of plan. Instead of installing v10q stock, I decided I want v20g stock instead. By the way, do I need the mk2000 file with it or is that only necessary for the rooted version?
My guess is there might be something wrong with the ADB installation. I know it's the platform-tools download file. I'm pretty sure I have all the Google drivers and LG Mobile drivers updated, although I'm not really sure.
Also, I have a slight change of plan. Instead of installing v10q stock, I decided I want v20g stock instead. By the way, do I need the mk2000 file with it or is that only necessary for the rooted version?
Last edited:
No error message means that the command was successfully executed, I know it's kinda weird but that's how CMD works, It's only when you get an error message back is when you have to worry. Go to the next step open up another CMD window and type STEP1.BAT
You need to have two CMD windows open to root your phone.
Just follow the steps. You got this.
Thanks, it worked! Ok so now I'm trying to do the following steps from another topic.
"
- Flash this zip from TWRP. This is every piece of the v10q firmware: h910_10q_full_stock.zip
SHA1: 720f122605dda361b8d8de1abaa8a56326416056 - Wipe Cache/Dalvik Cache
- Format data
- Reboot"
Not a problem,
Okay I see what happened. You installed the rom then formatted. That's why twrp is telling you there is no OS installed.
I made a guide on how to install Oreo on the H910 you can use your 20g rom if you want.
link
Last edited:
I took a leap of faith and rebooted it, thinking that if it hangs or soft-bricks I could just boot up TWRP again. Luckily, it was fine and now I successfully got stock v20g. While it does seem to be running smoother than my AT&T's OTA version of Oreo, I noticed I seem to be having some minor ghost touch issues where I'm doing something in an app and it randomly goes back to the home screen. It's not frequent by any means but it does occur on rare occasions. I never got that on my previous AT&T's OTA version of Oreo. Just wondering if you guys are noticing the same thing on your V20 after rooting.
Anyways, the reason why I wanted to do a fresh Oreo install was because I was having some issues with the quad dac where I felt it didn't seem to be performing at its full potential. It does seem to sound better now. At first, I thought about downgrading to Nougat but figured hey why not try reinstalling Oreo to see if that fixes it. I've always felt AT&T's version of Oreo was not very good quality, like they released it without fully testing it.
Anyways, the reason why I wanted to do a fresh Oreo install was because I was having some issues with the quad dac where I felt it didn't seem to be performing at its full potential. It does seem to sound better now. At first, I thought about downgrading to Nougat but figured hey why not try reinstalling Oreo to see if that fixes it. I've always felt AT&T's version of Oreo was not very good quality, like they released it without fully testing it.
Last edited:
Can someone please help me? I followed all the instructions, but I got stuck at this:
"Wait till you get a prompt back then type (or copy / paste):
Code:
run-as con
chmod 0777 /storage/emulated/0/*"
I waited until a prompted show up, but nothing unusual happened, at the end of the process it showed up just this line:
elsa:/ #
I pasted the command and it looked like this:
elsa:/ $ run-as con
elsa:/ # chmod 0777 /storage/emulated/0/*run-as con
0/*chmod: /storage/emulated/0/*run-as: No such file or directory
chmod: con: No such file or directory
1|elsa:/ #
So... what I did wrong? I did wrote this command on the android terminal emulator: "applypatch /system/bin/atd /storage/emulated/0/dirtysanta", the logcat window did not changed at all... So, I am lost...
"Wait till you get a prompt back then type (or copy / paste):
Code:
run-as con
chmod 0777 /storage/emulated/0/*"
I waited until a prompted show up, but nothing unusual happened, at the end of the process it showed up just this line:
elsa:/ #
I pasted the command and it looked like this:
elsa:/ $ run-as con
elsa:/ # chmod 0777 /storage/emulated/0/*run-as con
0/*chmod: /storage/emulated/0/*run-as: No such file or directory
chmod: con: No such file or directory
1|elsa:/ #
So... what I did wrong? I did wrote this command on the android terminal emulator: "applypatch /system/bin/atd /storage/emulated/0/dirtysanta", the logcat window did not changed at all... So, I am lost...
Each line is a separate command
run-as con
chmod 0777 /storage/emulated/0/*
Somehow it looks like you accidentally pasted as the second command.
chmod 0777 /storage/emulated/0/*run-as con0/*chmod
Hi @runningnak3d ,
The links you mentioned for packages in the post are broken. Any chance we can get new links?
The links you mentioned for packages in the post are broken. Any chance we can get new links?
hear you go
h910-10r.zip "the v10r firmware + boot + system"
h910_root_pkg.zip "DirtySanta root package"
usb drivers for windows
Terminal Emulator for Android
Yes I was on 10C and the root would not work but when I flashed the kdz file I was able to root. It be a good idea anyway just to make sure your on the correct firmware. Good idea to make a dump backup first also.
Note: when flashing the firmware you may have to uncheck laf or it will hang and error out.
my device is lg v29 h910, I followed the root instructions, no signal network, showing a slash, please tell me how to fix it
Can you give me more info? Like how far did you get with the guide? If you were able to finish the guide then you should have a rooted phone with 10r version. I don't know if that version supports VoLTE or not. But some times you have to call AT&T and have them enable VoLTE and wifi calling.
Last edited:
now i have kdz through h915 10e and unlockedbootloader again, installed twrp like in this video
Similar threads
- Poll
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!
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:
This is flashing TWRP and the WW 2.0 kernel onto your phone. The phone will reboot once they are flashed.Code:STEP3.BAT
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...
-- Brian8FAQ:
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.5Jerry 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 like5
all the root files for this thread are in my AFH (in my signature) the root package is here >> https://androidfilehost.com/?fid=13227782629039902184Kernel 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!
New posts
-
Update Samsung Galaxy Tab 4 (SM-T531) Unofficial Rom - Problem
- Latest: torombolo74
-
-
-
