Database Info

Bootloop 2013 Moto G Boost Mobile XT1031 8GB

Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.

blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.

I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.

You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?

blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).

_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.

@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!

[H915] Root Guide + Restore Any Bricked LG V20

Just in Time for The New Year I would like to show Everyone How to root there Canadian variant LG V20!
Current Known issues
- No Service From Carrier
- Seems VERY Laggy (Can be Fixed with using a Kernel)
Other Information
- Yes you can Restore to factory Settings with this Method (So Don't worry if you screw up)
- Sorry far I Only know This works on the H915 however the Restore should work with all LG Models
- This will give you a Bootloader to have access to fastboot Commands
- Working TWRP Recovery
So After Reading the No Service Part many are mostly not going to be interested... I uploaded this Thread anyway to see if anyone could find a fix to this issue. (When one is found I will update this with the fix)
So If you still want to Root your Canadian LG V20 Let's do it!
DOWNLOAD THE ZIP FILE HERE
https://mega.nz/#!ABZV0AZZ!8LBGgpjiGT1ij6scshWTQO4tGhUb9GMUcTHtKLLhfW0
- I DO NOT TAKE ANY RESPONSIBILITY FOR YOU BREAKING YOUR DEVICE
- I HAVE NOT CREATED ANY OF THESE FILES I ONLY PUT EVERYTHING INTO ZIP FOLDER FOR YOU TO DOWNLOAD AND MAKE THINGS CONVENIENT AND SIMPLE
- PLEASE THANK THE ACTUAL DEVELOPERS WHO CREATED THESE FILES (LISTED BELOW)
FILES USED/THANK THESE PEOPLE
@me2151 Dirty Santa Files (Boot2.img, Step 1.bat, Step 2.bat and RUNMEFIRST.bat) -
HTML:
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
@jcadduono recowvery and dirtycow exploit (used with Dirty Santa)
HTML:
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Stock Images for LG V20 H915 you can find those here
HTML:
http://lg-firmwares.com/lg-h915-firmwares/
(You will need to be flashed on H91510d for this to work however you could try 10e if you wanted)
@autoprime UPPERCUT for LGUP (This is what allows the LG V20 to be read and will allow you to downgrade to 10d if needed and will let you restore to stock using Download Mode at any time! This will only be used for you if you mess up with the root and need to flash back to stock or you need to upgrade or downgrade to the 10d firmware)
HTML:
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
@Chainfire SuperSu v2.79 SR1
HTML:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
WHAT DO YOU NEED BEFORE YOU START
- A Copy of LGUP
- An LG V20 H915 Running the 10d Firmware (if you need help flashing this firmware read below before Step 1)
- The Zip File I Listed above to Download
- ADB and LG Drivers
- A Windows Computer
HOW TO UPGRADE/DOWNGRADE TO FIRMWARE VERSION 10d
Step 1 - Boot Your Device into Download Mode (Turn the phone off hold the Vol + Button and plug in your device to the Computer)
Step 2 - On your Computer find the Zip File (extract it) and Open Uppercut.exe (This should launch LGUP and Make sure your Phone is Connected to your Computer)
Step 3 - In LGUP Select the Upgrade button (even if you are downgrading it will still work) then find the Firmware .kdz file for 10d
Step 4 - Flash the KDZ back onto your device
ROOTING THE DEVICE!
Step 1 - Install a Terminal Emulator App to your Device
Step 2 - Verify your device is plugged in and that ADB sees the Device (adb devices)
Step 3 - On your Computer Open the RUNMEFIRST.bat (do not close this window)
Step 4 - After loading up RUNMEFIRST.bat run Step1.bat (if you see permission denied on the files Flatland and Flatland64 this is normal)
Step 5 - Once the shell prompt opens in the step 1.bat window type "run-as con" (without quotations then hit enter) then type "chmod 0777 /storage/emulated/0/*" (yet again not in quotations and then hit enter)
Step 6 - Once that has finished on your phone open the Terminal app you downloaded earlier and type in id (if untrusted_app is displayed continue if not redo the steps)
Step 7 - In the Terminal Emulator type applypatch /system/bin/atd /storage/emulated/0/dirtysanta then watch the RUNMEFIRST.bat to see when it tells u to open Step2.bat (when it tells u to open Step2.bat open it)
Step 8 - You should now Be into a Somewhat usable bootloader on your device... now we Stop using DirySanta and Start to do things manually by ourselves open up a Command Prompt and type "fastboot flash boot boot.img" this will flash the boot2.img used in the Dirty Santa Exploit
Step 9 - After that finishes type "fastboot flash recovery TWRP.img" This will put TWRP (For the H918 Variant) on your device
Step 10 - Boot into TWRP (Remove battery then put it back in hold the Vol - Button and the Power Button Once LG Powered by Android Logo Appears Release the Power Button then Hold it Again, A White screen should come up say yes to both screens then should boot into TWRP)
Step 11 - Now that you are this far I recommend you backup everything so that you can start from this point if you mess up any upcoming steps that way you do not have to reflash the stock image and start from step 1 again....
Step 12 - Select Wipe from the Main menu then go to Format Data then type yes and enter (This will remove the password lock currently enabled on the device)
Step 13 - On the Main Menu select Install browse to your SD Card where you put your SuperSU.zip File onto and flash that to the device
Step 14 - Once that is completed return to the main menu select the Wipe menu again go to Format Data then yes again
Step 15 - Go back to the Wipe Menu and go to Advanced and select Dalvik, Data and Cache then slide to wipe after this finishes reboot to the system
Step 16 - Once in the System complete the Android setup and enable USB Debugging again then type adb reboot recovery (if your device does not boot into Android this is when u go back into TWRP by doing the remove battery method and holding those buttons down as I stated before and you Restore your Backup you made in Step 11 and you try doing those Steps again)
Step 17 - Once Back into TWRP (you may make another backup here if you would like) select Install then Flash SuperSU to your device again... Go back to the Main Menu Select Wipe then Advanced and Select Dalvik and Cache then Slide to Wipe and reboot into the System
Step 18 - Once back into Android you should see SuperSU on your device and you may download a Root Checker app of the Play Store to Make sure your Device is Fully Rooted and Working!
Please inform any Issues in the Replies below and I will add them to the List for People to Know before they Attempt rooting... If anyone finds a Fix for the Modem file to get service working on the LG V20 H915 while rooted please reply and i will Add that to the guide BELOW!
I DID NOT MAKE ANY OF THESE FILES SO PLEASE THANK THE CREATORS (LISTED ABOVE) FOR THEIR HARD WORK AND EFFORTS!
I THINK I BRICKED MY DEVICE/ THE ROOT DID NOT WORK/ I WANT TO GO BACK TO STOCK
Step 1 - As Stated Above to this all we need to do is Enter Download Mode (Remove Battery reinsert battery hold Vol + and plug in the Device) and then run the UPPERCUT.exe File
Step 2 - Select Upgrade browse over to your kdz file and select it then flash it to your device! Your Device Should boot up into Android (I Have Bricked my LG V20 Many Times Removing TWRP and the Bootloader and having nothing but the LG Logo and the Download Mode and I could Still get into the Device after doing this so it should work for you! However any problems should be dealt with the developer on his forum listed here
HTML:
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
)
Anyone willing to Try installing things like Kernels and ROMs I would assume you would be using H918 Supported Files For those as thats what TWRP is running in.....

Will be adding a Zip File will all the Files need in a Couple of Minutes....

There seems to be a hidden settings menu on our Devices in which we can play around with the Modem Settings among other things.... you need to open the Phone App and Type in *#546368#*915# and the menu should come up.... Maybe somebody can figure out how to get Service running.... All Credit for this goes to @KedarWolf in his post listed here https://forum.xda-developers.com/v20/how-to/access-hidden-menu-h915-t3515098

Nice little write up. Did you try this on the wind/freedom 915 or videotron 915? My guess would be that you tried it on the wind 915 and if so i bet it has something to do with their slightly differnet bands they use albeit for a change an unlocked wind device works fine on other networks. But i really have no clue if there's a connection on why there's no signal. This kind of thing is beyond my pay grade. I would be guessing someone like @autoprime would be someone to ask but chances are he has other things to worry about and likely doesn't have the device.
But keep plugging away. You may figure it out yet

markbencze said:
Nice little write up. Did you try this on the wind/freedom 915 or videotron 915? My guess would be that you tried it on the wind 915 and if so i bet it has something to do with their slightly differnet bands they use albeit for a change an unlocked wind device works fine on other networks. But i really have no clue if there's a connection on why there's no signal. This kind of thing is beyond my pay grade. I would be guessing someone like @autoprime would be someone to ask but chances are he has other things to worry about and likely doesn't have the device.
But keep plugging away. You may figure it out yet
Click to expand...
Click to collapse
Yes the Wind H915 still haven't got it figured out yet hopefully someone will soon then we will have an official working root for the Canadian Variant

I would have jumped on the Freedom Mobile (formerly Wind) deal ($30 for 6GB for the first 10 months) if the H915 had been root and has an unlocked bootloader. LG's track record of offering unlocked bootloader is looking very bleak for the H915.

@TheDantee I am sure the service issue will be resolved soon but "Seems VERY Laggy" part is worrying me more. What is the reason for that? I like the possibility to go to the default LG rom like nothing happen.

Emilius said:
@TheDantee I am sure the service issue will be resolved soon but "Seems VERY Laggy" part is worrying me more. What is the reason for that? I like the possibility to go to the default LG rom like nothing happen.
Click to expand...
Click to collapse
Sorry i should mention that a Kernel fixed this issue for me!

TheDantee said:
Sorry i should mention that a Kernel fixed this issue for me!
Click to expand...
Click to collapse
Service issue or laggy part?

Emilius said:
Service issue or laggy part?
Click to expand...
Click to collapse
Laggy Part

Noob question, is the phone fully functional after step 10 (TWRP).
The reason I ask is because I really only need to get to TWRP as I want to enable google assistant.
At this point, the root is not a big concern for me.
Thanks,

SHABBA JOTS said:
Noob question, is the phone fully functional after step 10 (TWRP).
The reason I ask is because I really only need to get to TWRP as I want to enable google assistant.
At this point, the root is not a big concern for me.
Thanks,
Click to expand...
Click to collapse
Shoulbe be but you will need to still do a format on the device or you will get locked out and it will ask for a passcode....

TheDantee said:
Shoulbe be but you will need to still do a format on the device or you will get locked out and it will ask for a passcode....
Click to expand...
Click to collapse
So SuperSU messed the service reception? Not bootloader?

Emilius said:
So SuperSU messed the service reception? Not bootloader?
Click to expand...
Click to collapse
I don't think its SuperSU Causing the problem... In the bootloader (debug) that is provided in the DirtySanta root it states the device as an unlocked US996 LG V20 I feel that this is because it has no idea which provider its with since we are Canadian.. I have tried flashing many many modem files from many different firmwares I either get modem blue screens on boot (Goes away permanently if you remove sim card) or I get no Service in the System it self... so personally I think it is the Bootloader since its a debug bootloader because the Canadian Variant does not seem to have a bootloader.... May I ask what is your reasoning for SuperSU being the issue?

TheDantee said:
I don't think its SuperSU Causing the problem... In the bootloader (debug) that is provided in the DirtySanta root it states the device as an unlocked US996 LG V20 I feel that this is because it has no idea which provider its with since we are Canadian.. I have tried flashing many many modem files from many different firmwares I either get modem blue screens on boot (Goes away permanently if you remove sim card) or I get no Service in the System it self... so personally I think it is the Bootloader since its a debug bootloader because the Canadian Variant does not seem to have a bootloader.... May I ask what is your reasoning for SuperSU being the issue?
Click to expand...
Click to collapse
Based on your answer to SHABBA JOTS I get feeling that maybe is SuperSU creating that problem if until step 10 (TWRP) is all good. So soon we do step 8 (flashing boot image) service is gone. Is that right?

Emilius said:
Based on your answer to SHABBA JOTS I get feeling that maybe is SuperSU creating that problem if until step 10 (TWRP) is all good. So soon we do step 8 (flashing boot image) service is gone. Is that right?
Click to expand...
Click to collapse
Currently I have no access to my V20 so i can not try and tell you but if you are willing to reset and try the steps again up to Step 8 then lemme know the answer... however the system is very very very unstable many crashes tons of lag massive downgrade in battery without that boot.img... what if u flash twrp once in the bootloader but not the boot.img try that.... then get back to me Curious now lol

TheDantee said:
Currently I have no access to my V20 so i can not try and tell you but if you are willing to reset and try the steps again up to Step 8 then lemme know the answer... however the system is very very very unstable many crashes tons of lag massive downgrade in battery without that boot.img... what if u flash twrp once in the bootloader but not the boot.img try that.... then get back to me Curious now lol
Click to expand...
Click to collapse
He he, I am an Nexus person. I am so afraid to mess up my V20. With Nexus it is so easy, in 2 steps you are done. I miss that part I mast say.

Ok so i gave this a quick read and from what i gather you flash the bootloader before you flash twrp and super su. So here's a question that may or may not have been tried. Is there any reason you can't follow this method to root and then flash stock recovery and then flash stock bootloader?
Since it seems bootloader is the issue with having no data or signal. You would at least have root but just not twrp. Does that make sense?

markbencze said:
Ok so i gave this a quick read and from what i gather you flash the bootloader before you flash twrp and super su. So here's a question that may or may not have been tried. Is there any reason you can't follow this method to root and then flash stock recovery and then flash stock bootloader?
Since it seems bootloader is the issue with having no data or signal. You would at least have root but just not twrp. Does that make sense?
Click to expand...
Click to collapse
It's look like H915 dues not have bootloader at all.

Emilius said:
It's look like H915 dues not have bootloader at all.
Click to expand...
Click to collapse
Well it has to have a bootloader. It's just locked right. Like if we pulled apart the stock kdz we should be able to find it and my theory is we could use flashfire to flash stock recovery and also flash thr bootloader since twrp can't to my knowledge flash bootloaders. We would be left with root but no recovery. I could be so far from being right but who knows. This could be the only way to have root and a working phone.

Update on How to Root from Scratch, (Backup TA, Unlock Bootloader, then Recovery)

First off, i'm sorry if the title is misleading and/or belong in the wrong part of this forum.
So, I'm late to the party, just got myself a Z5 E6653 and when I look for guides on how to obtain root they kind of out-of-date. So i'm here to make sure the path I choose to follow will be the correct one as I dont want to lose my TA partition. As far as I know, according to this guide to back up my TA partition I have to downgrade to Lollipop, but I found something interesting about backing up TA partition on Marshmallow using dirtycow method (sorry Nougat users).
So, the steps I'm proposed is, if my device is already on stock MM unrooted, locked bootloader.
1. Go here Sony cross-devices development and download file called backupTA_v2.zip this shouldnt makes us need to downgrade
2. Run the BackupTA.cmd file if you're on windows
3. There will be errors about dirtycow failed but the script automatically retry, me myself got screen-full of retries before the script actually backed up my TA partition and you'll be presented with .imgfile called TA_devicemodel_somenumbers_timestamp.img about 2MB in size (am i correct so far? this is why i want to make sure this will work)
4. Save your file in a very secure place.
That concludes the Backup TA part of rooting process am I on the right path so far?
To get unlocked bootloader according to this :
Given that you have downloaded flashtool and installed the drivers in the \drivers folder in flashtool installation
!!THIS WILL WIPE ALL DATA!!
1. Click the BLU button at top then open Sony developer website
2. Select device and follow instruction until you get a key
3. Paste the key to flashtool
4. THAT'S IT?
Now after this we can use fastboot command to flash kernel and the kernel includes recovery.
Are these steps correct so far?
I might as well add these here.
To get kernel and recovery up and running, I'll be taking androplus kernel for example, I'm assuming it works with stock ROM.
1. Get the kernel .zip here at Androplus homepage
2. And download latest TWRP recovery from androplus download page, at this time of writing it should be TWRP-3.0.2.2-e6653.img
3. Notice that it's in .zip format which we cannot use yet since we don't have custom recovery.
4. Open the zip file you just downloaded and you should see boot.img That's your brand new shining kernel, extract it outside put it in a folder along with your favorite fastboot.exe file
5. Go to fastboot, as far as I know you go to fastboot by turning off the device -> hold volume down then plug USB cable. (see note)
6. First, according to Androplus page, flash the kernel first using the command
Code:
fastboot flash boot boot.img
7. Then the recovery
Code:
fastboot flash recovery TWRP-3.0.2.2-E6653.img
8. Reboot by unplugging the USB cable
Note: some interesting thing I found while trying to enter fastboot or flashmode that it might not work if your USB port is powered How to tell if your port is powered? I'm not sure. You will have to change port and hope for the best ^_^

Yes. Explained many times. Not hard to do.. 4-5 minutes then WHOLA!

sceryavuz said:
Yes. Explained many times. Not hard to do.. 4-5 minutes then WHOLA!
Click to expand...
Click to collapse
Ahaha, sorry. Those guides are "old" in android way of changing things very fast, and I haven't seen a guide which includes backup TA partition on marshmallow so I wasn't sure it'd work correctly. Now that I know it worked, I can proceed to unlock my bootloader.
Any tips or Kernel/Rom I should use for first time flash?

webslasher said:
Ahaha, sorry. Those guides are "old" in android way of changing things very fast, and I haven't seen a guide which includes backup TA partition on marshmallow so I wasn't sure it'd work correctly. Now that I know it worked, I can proceed to unlock my bootloader.
Any tips or Kernel/Rom I should use for first time flash?
Click to expand...
Click to collapse
LineageOS, CarbonROM, eXistenZ, SunKernel..

Dear both,
I was just doing quite the same, so it was nice to read the short summary. Honestly, I'm doing these "Flash ROM stuff" very rarely, so I'm not 100% confident how to bring back those DRM/TA. I recorded it - the device came with Android LP 5.11, so this was easy done by iovyroot.
Anyway, I have the TA-backup - so I'm also going to unlock the Boot Loader now. :good:
Good to know I spend a day on reading so many related stuff, and it could be done in 4-5 min

sceryavuz said:
LineageOS, CarbonROM, eXistenZ, SunKernel..
Click to expand...
Click to collapse
I will try Existenz as I want to keep it stock looking, thanks!
bosquarid said:
Dear both,
I was just doing quite the same, so it was nice to read the short summary. Honestly, I'm doing these "Flash ROM stuff" very rarely, so I'm not 100% confident how to bring back those DRM/TA. I recorded it - the device came with Android LP 5.11, so this was easy done by iovyroot.
Anyway, I have the TA-backup - so I'm also going to unlock the Boot Loader now. :good:
Good to know I spend a day on reading so many related stuff, and it could be done in 4-5 min
Click to expand...
Click to collapse
I'm glad to find someone that is going to go through these procedures too! I will also proceed to unlock my bootloader what rom and kernel do you plan to flash?

Hi, thanks for this. I just got the Z5 today so my first port of call was coming here and finding out how to root it. I previously had the Z2 and Z2 tablet which I rooted last year with the help of the members here, I hope the process for this isn't too different for this one. I think I forget more than I remember so the guide is helpful.

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

***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

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.

I am Definitely missing something here, I cant for the life of me get the h915 firmware to flash using lgup
It just states kdz file is invalid.
H910 -> h915
Confirmed im attempting to use the patched lgup as well

It is definitely not reading the modified model file. You must have had another version installed. You need to uninstall / delete any other model dll files you have installed.

It would appear that i dont have lgup installed correctly (not at all in this case) to begin with
Let me do a little digging to figure out lgup.
Not entirely sure how i did a full dump with it not even installed but alright
---------- Post added at 09:10 PM ---------- Previous post was at 08:51 PM ----------
Just to confirm for 100% sure that we are supposed to be ticking the upgrade option and not the option for partition dl that is mentioned in the patched lgup thread correct?
I simply cannot get passed invalid kdz and have confirmed numerous times now that there is only one dll in the lgup folder
Path to the lgup exe that i have replaced with the above patched executable from the other thread
C:\Program Files (x86)\LG Electronics\LGUP\LGUP.exe
Path to the dll folder that i placed there as well along with a LOG folder directly above it
C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_common.dll
The log folder consists of a folder by this name here LG-H910 (my current device)
There is nothing else in the model folder at all except for the two mentions above
If lgup is somehow reading from another directory outside of where i launched the exe, I have zero clue as i have searched lgup to no availability.

And that is why I wanted to write this up as I did it
You are correct. Choose partition dl, and make sure all partitions are selected.
After that, the rest of the instructions should be correct.

runningnak3d said:
And that is why I wanted to write this up as I did it
You are correct. Choose partition dl, and make sure all partitions are selected.
After that, the rest of the instructions should be correct.
Click to expand...
Click to collapse
I have ran out of time tonight to muck around with it but have definitely rendered it bootlooping currently (stuck at second lg logo is more accurate)
Not entirely sure what i did wrong, was able to get into twrp a couple times as well trying to continue the steps

Since you have TWRP installed, you can fix whatever is wrong.
Unfortunately, whatever you did wrong was within the DirtySanta root procedure, and that would have gone wrong even with H910 firmware with the Dec. 2016 sec patch.
You are going to have to provide some more details.

It booted successfully after the h915 flash and I made it all the way up to step three before it was bricked under the dirty Santa method and have been attempting to recover it since.. I can't get lg up to recognize it any longer as of now
---------- Post added at 01:37 PM ---------- Previous post was at 01:27 PM ----------
Scratch that somehow i got it booted, I was stuffing around it twrp and flashed the natf with a factory reset and it is now static booting which I'll have to fix once I grab that kernel

runningnak3d said:
WARNING: This is ONLY for H910. If you flash H915 firmware on an H918 -- you WILL brick it. I am not sure about other variants, but cross flashing firmware is HIGHLY risky. I only found out this was safe because I got myself in a situation where I had nothing to lose, so I tried it.
Since I have had quite a few people ask me via PM for the procedure, I figured it was time to make a post. I really wanted to wait till I got my H910 back from LG so I could type this up as I do it again (yes this has been tested) to make sure that I don't miss a step. I am 99% sure that I didn't, but even if I did, the worst that is going to happen is that you get an error or have to start again.
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 version that is no longer rootable by DirtySanta (IE: dirtycow has been patched), but it has only been tested on v10m (Sec. patch April 2017).
The H910 and H915 have the same PBL (Primary Boot Loader), so it is safe to flash H915 firmware on H910 hardware.
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.
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.
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 selected.
Once it is complete, your phone should reboot into a nice new (old) Freedom Mobile ROM, and you will have no signal. This is normal.
You are now safe to root your phone following the standard DirtySanta procedure: link. You can ignore the part where it says that you can't go back to stock. As soon as my phone comes back from LG, I will be posting a zip that you can flash that will completely return you to stock v10m.
OK, so now you are rooted, and have TWRP. Now I am guessing you would like to actually be able to use your phone to make calls / send texts / surf porn read XDA, so you need a working modem...
The following you will do from a command prompt:
adb reboot recovery
adb push X:\path\modem_COMYY /sdcard/
Where X:\path is the path that you saved the dump from your phone, and YY is the COM port number. For example, if Windows detected your phone as COM11, then the file will be named: modem_COM11
adb shell
cd /sdcard
dd if=modem_COMYY of=/dev/block/bootdevice/by-name/modem
exit
adb reboot
When your phone reboots you should have a rooted H910 with Freedom Mobile v10e ROM and phone / data functional.
At this point, you are free to flash any ROM that is for the H910. I use NATF, but some prefer WETA. I am not including links since you should really go find a ROM you like yourself.
As I stated at the beginning of this post, my phone is in the shop and I don't have a full dump of v10m. When it gets back, I will make a zip that will flash all the pertinent partitions with our v10m firmware so that we have nice, updated phones. I will also post a zip that will flash ALL the v10m partitions and take you back to exactly where you are now in case you want to return to stock for some reason.
Feel free to ask away if any of this doesn't make sense
-- Brian
Click to expand...
Click to collapse
GOD BLESS YOU! I needed this today! Will try later!

Passing along an update of progress, currently still having trouble with this.
Current status is it is static screen booting currently.
I also have no signal and your steps for flashing the modem work just fine to what it appears to from the commands lines (everything goes through correctly) but upon booting shortly after i am greeted with a blue screen saying subsystem crash : modem
Yes i did use the dumps from the very first step and they appeared to have flashed back correctly.
Lgup will not recognize the phone from everything i have tried to recover it at this time either
Edit: when it comes to the step where you have to type this here below
dd if=modem_COM5 of=/dev/block/bootdevice/by-name/modem
Is the portion from this line where it states "by-name" correct?
Com5 is correct as that is the name of my file when i pulled it from the device

Stuck on step 5 of Dirty Santa on an H910. Went back and redid steps 3-5 and it's still just sitting on LG logo. Any ideas???? I know I followed the instructions verbatim!!

jreed3786 said:
Stuck on step 5 of Dirty Santa on an H910. Went back and redid steps 3-5 and it's still just sitting on LG logo. Any ideas???? I know I followed the instructions verbatim!!
Click to expand...
Click to collapse
Have you tried this
me2151 said:
It has come to my attention that some users have encountered abnormally long first boot time(over 20 minutes before first time setup)
To resolve this issue:
Boot into bootloader by pulling the battery and reinserting it and holding VOL- and phugging in the phone. then typing:
Code:
fastboot flash boot bootbackup.img
fastboot reboot
Click to expand...
Click to collapse
Sent from my LG-H910 using Tapatalk

Is there a method to getting back to full stock 10m on the h910 for now until i can get this sorted out.
Ive tried flashing the backed up modem i have multiple times at this point and cannot get signal back after following this method here to the letter.
I do have access to twrp but cannot get access to lgup at all no matter whether it is in fastboot mode/recovery/usb debugging/etc etc etc

daw41 said:
Have you tried this
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
SURE have. This is for the Verizon variant. I have AT&T. No such path found. I too, just need the modem to work. I tried a few workarounds...
SO, either a fix for the bootloop on the LG logo, or a flashable H910 modem so I can use my phone.

runningnak3d said:
Reserved for FAQ
Click to expand...
Click to collapse
Sir, i accdientally KDZ my H910 to F800K. I managed to make the call, mess function again by flashing US996 modem file but now my phone can't connect to any mobile network when data switch on. I mean i can call and receive call from other people, send and receive mess too. Could you kindly teach me how to fix this???? I can KDZ to US996 rom but it end up in bootloop (i can get into the rom, but after a few second it will reboot itself). In US996 rom, my phone functioning normal, no problem at all, but the bootloop happen so, sir. Help me, please

jreed3786 said:
SURE have. This is for the Verizon variant. I have AT&T. No such path found. I too, just need the modem to work. I tried a few workarounds...
SO, either a fix for the bootloop on the LG logo, or a flashable H910 modem so I can use my phone.
Click to expand...
Click to collapse
So if you're at step 5 you should have TWRP manually reboot into TWRP and Flash a ROM like natf or weta should fix your issue
Sent from my LG-H910 using Tapatalk

daw41 said:
So if you're at step 5 you should have TWRP manually reboot into TWRP and Flash a ROM like natf or weta should fix your issue
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
Yes sir...it should, but I still get error about modem, even when flashing WETA and rebooting. Any easier way to flash the H910 modem?

jreed3786 said:
Yes sir...it should, but I still get error about modem, even when flashing WETA and rebooting. Any easier way to flash the H910 modem?
Click to expand...
Click to collapse
Sir, i can make the phone call and mess work again but the mobile data i nowhere to be found. At least you can make phone call and send text. You can try by flashing US996 modem file, the signal will come back but without 4g,3g or whatsoever.

Jerry SQ said:
Sir, i can make the phone call and mess work again but the mobile data i nowhere to be found. At least you can make phone call and send text. You can try by flashing US996 modem file, the signal will come back but without 4g,3g or whatsoever.
Click to expand...
Click to collapse
There's no way to flash or find an H910 modem file? Why is this? Just wondering.

[CLOSED]LG Stylo 6 root development! ANY HELP APPRECIATED. DISCORD LINK AVAILABLE

Moderator Announcement:
Thread closed and content removed on request of OP.
- Oswald Boelcke

I SERIOUSLY would like to know how you get that bug report so I can get any files for the stylo 6 boost mobile
Where did you find the zip or link to the site hosting the zip in the big report? I can get that far but I really want any help on getting similar files from this specific device model/variant
I am not gonna lie your post is an oasis in a desert and I hope this does find its way into the right hands to push root dev

Me to I have the lg stylo 6 from my cable company

I'm currently browsing through the root directory to see if I can pull the boot.img.. there's a method of rooting it with magisk manager.. the bigger issue is how to reinstall the modified boot.img.. I think we will need the bootloader unlocked
Spoiler
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I just checked on firmware download and the kdz for lgup is available to download.. in theory because I don't have a pc to verify.. a possible root method might be as simple as, extracting the kdz file, modifying the boot.img with magisk manager, rebuild the kdz file with a kdz tool.. then flashing the modified kdz with lgup.. then install magisk manager after 1st boot and hope we have root.. feel free to test or share any other ideas..
Spoiler

It seems like very few working on this project.. I've come across a dual mode lgup made by one of our developers capable of crossflash.. probably the best version of lgup to flash firmware with modified boot.img.. I'm also buying a laptop for experiments on this device.. I now have 2 versions of the stylo 6 to play with.. hopefully I don't go overboard and turn them to paperweight .. the only thing I need is the method or tool to rezip kdz to try achieving root myself.. if anyone find such a tool, please share ..

The boot image wouldn't work. In theory, you would use kdzTools and it will turn the KDZ into a DZ file and then you extract the DZ file. You would have to use Qfil or fastboot to flash a modified boot image, and have an unlocked bootloader. LGUP is an amazing tool to crossflash different firmware from different Stylo variants, but with AVB 2.0, this doesn't work on many of the LG devices that came out of the box with Android 10, and repacking the KDZ with a modified boot image would fail because of the boot image being signed inncorrectly. Your best bet is to see if there is an exploit like what was found on the V50, and to hope that someone makes gets Firehose working for the Stylo.

Yeedatoy said:
The boot image wouldn't work. In theory, you would use kdzTools and it will turn the KDZ into a DZ file and then you extract the DZ file. You would have to use Qfil or fastboot to flash a modified boot image, and have an unlocked bootloader. LGUP is an amazing tool to crossflash different firmware from different Stylo variants, but with AVB 2.0, this doesn't work on many of the LG devices that came out of the box with Android 10, and repacking the KDZ with a modified boot image would fail because of the boot image being signed inncorrectly. Your best bet is to see if there is an exploit like what was found on the V50, and to hope that someone makes gets Firehose working for the Stylo.
Click to expand...
Click to collapse
I just found all the information necessary to root our Stylo.. I'm not experienced enough to do the final step but I'm willing to pay our more experienced developers to do it.. we can simply use an all in one tool I'll share the link to, that will let us extract the kdz, modify the system.img and reconstruct the kdz.. in the extracted system.img we can hopefully find the boot.img and modify it for root using magisk manager.. dual mode lgup should flash the modified kdz.. I plan to try.. then on 1st boot we can manually install magisk manager and enjoy root.. the downside is with a locked bootloader all we get is root.. no custom recovery or custom rom until we unlock the bootloader.. but it's a start.. again.. bounty for dev that can use this handy tool.. Happy New Year
GitHub - ehem/kdztools: Tools for working with KDZ files (LG's Android device upgrade format)
Tools for working with KDZ files (LG's Android device upgrade format) - GitHub - ehem/kdztools: Tools for working with KDZ files (LG's Android device upgrade format)
github.com
Spoiler

lowkeyst4tus said:
I just found all the information necessary to root our Stylo.. I'm not experienced enough to do the final step but I'm willing to pay our more experienced developers to do it.. we can simply use an all in one tool I'll share the link to, that will let us extract the kdz, modify the system.img and reconstruct the kdz.. in the extracted system.img we can hopefully find the boot.img and modify it for root using magisk manager.. dual mode lgup should flash the modified kdz.. I plan to try.. then on 1st boot we can manually install magisk manager and enjoy root.. the downside is with a locked bootloader all we get is root.. no custom recovery or custom rom until we unlock the bootloader.. but it's a start.. again.. bounty for dev that can use this handy tool.. Happy New Year
GitHub - ehem/kdztools: Tools for working with KDZ files (LG's Android device upgrade format)
Tools for working with KDZ files (LG's Android device upgrade format) - GitHub - ehem/kdztools: Tools for working with KDZ files (LG's Android device upgrade format)
github.com
View attachment 5179601
Click to expand...
Click to collapse
Give it a shot, it's not as confusing as it may look at first glance. Just put everything in the same folder on you computer. Open the tool and select your KDZ file. Extract it, and it turns it from a KDZ file into DZ file. Select extract DZ in KDZ tools next, and it will fully extract the file. You'll see a bunch of bin files. You can simply rename bin, to img for boot, and then copy it to your phone and patch it with magisk. Then copy the patched boot image back to your PC and change the img extension back to bin and rezip the KDZ.

Do you have fastboot access on the Stylo 6?

Not sure yet but I don't think I'll need it.. I don't want to start by diving deep and overlook a simpler solution than accessing fastboot.. I just need a developer that can modify a kdz.. if I can simply achieve root via the new magisk method, it's a start.. I'm picking up another stylo 6 today, then a real computer cause my chromebook useless.. I'll update if I get a modified kdz and what happens when I try to flash

lowkeyst4tus said:
Not sure yet but I don't think I'll need it.. I don't want to start by diving deep and overlook a simpler solution than accessing fastboot.. I just need a developer that can modify a kdz.. if I can simply achieve root via the new magisk method, it's a start.. I'm picking up another stylo 6 today, then a real computer cause my chromebook useless.. I'll update if I get a modified kdz and what happens when I try to flash
Click to expand...
Click to collapse
I myself have just finally found this thread and am super more than willing to put in some work!
so i've gotta:
- `adb reboot recovery`
- boot into fastboot from recovery
- unlock the bootloader with `fastboot oem_unlock`
- let the phone factory reset with an unlocked bootloader
_____________________
and:
- download the .kdz firmware file for the unlocked version on pc
- locate and extract the boot.bin with kdzTools and convert it to boot.img
- send extracted file to my personal phone
- patch boot.img in magisk manager app on my phone
- send it back to pc with `adb pull /sdcard/boot.img C:/users/myname/`
_____________________
then:
- load patched boot.img into the stylo 6 through `fastboot flash boot boot.img`
- `fastboot reboot` and let it reboot hopefully with root AND with carrier unlock
- download magisk manager to verify
I guess I'll give this a shot and get back to you guys.

haise.zero said:
I myself have just finally found this thread and am super more than willing to put in some work!
so i've gotta:
- `adb reboot recovery`
- boot into fastboot from recovery
- unlock the bootloader with `fastboot oem_unlock`
- let the phone factory reset with an unlocked bootloader
_____________________
and:
- download the .kdz firmware file for the unlocked version on pc
- locate and extract the boot.bin with kdzTools and convert it to boot.img
- send extracted file to my personal phone
- patch boot.img in magisk manager app on my phone
- send it back to pc with `adb pull /sdcard/boot.img C:/users/myname/`
_____________________
then:
- load patched boot.img into the stylo 6 through `fastboot flash boot boot.img`
- `fastboot reboot` and let it reboot hopefully with root AND with carrier unlock
- download magisk manager to verify
I guess I'll give this a shot and get back to you guys.
Click to expand...
Click to collapse
If you do manage to get into fastboot, there's 2 commands to try.. the new command is " fastboot flashing unlock".. you can also try getting unlock.bin even though there's no mention of availability.. it might be required for fastboot unlock.. the unlocked firmware is what I was going to experiment with also.. if you do manage to successfully extract the boot.img from the kdz, skip fastboot flashing.. just install magisk manager on your phone and follow the instructions on other threads to modify the boot.img.. then rezip the kdz with the modified boot.img.. flash with dual mode lgup for better chance of success.. it should install and boot normal.. on the surface you should not notice any change like errors with boot.. after 1st boot, install magisk manager and it should say root is working .. good luck and I look forward to your results
Spoiler

lowkeyst4tus said:
If you do manage to get into fastboot, there's 2 commands to try.. the new command is " fastboot flashing unlock".. you can also try getting unlock.bin even though there's no mention of availability.. it might be required for fastboot unlock.. the unlocked firmware is what I was going to experiment with also.. if you do manage to successfully extract the boot.img from the kdz, skip fastboot flashing.. just install magisk manager on your phone and follow the instructions on other threads to modify the boot.img.. then rezip the kdz with the modified boot.img.. flash with dual mode lgup for better chance of success.. it should install and boot normal.. on the surface you should not notice any change like errors with boot.. after 1st boot, install magisk manager and it should say root is working .. good luck and I look forward to your results View attachment 5181357
Click to expand...
Click to collapse
Sounds good, thanks for the advice! It's super helpful.
I'll be taking a crack at it here soon, or maybe tomorrow since it's 1:30am and I'm having a drink (depends on my mood ). I'll probably go with fastboot flashing unlock_critical just to be on the safe side of things and have everything unlocked from the get go for development purposes. I did run into an issue when I ran that command already -
C:\Users\myname>fastboot flashing unlock_critical
...
FAILED (remote: Unrecognized command flashing unlock_critical)
finished. total time: 0.006s
I can get into fastbootd on the device, and need to read up on it a bit since nearly every fastboot command I send in is unrecognized (see above) or gets a response like FAILED (remote: Unable to open fastboot HAL)
I'll enable test signing mode on my windows machine and get the right drivers installed, and get fastbootd working and then try again. I'll likely run into a roadblock though, since Boost doesn't exactly want us unlocking the bootloader - nor does LG, apparently...
For now, here's a few resources that might help catch you up on things and possibly give me some more room to wiggle around:
- Android documentation on fastbootd and fastboot being moved to userspace (contains information about the HAL)
- A mildly helpful and more easy-on-the-eyes article that can help explain the above documentation
I'll try and get past this issue. There's gotta be something, somewhere... I first just need to communicate with the phone correctly and get it to do what I need it to do in fastboot mode.
I also have downloaded two different .kdz files and have indeed extracted both of them into .dz files. I didn't get past that last night, so I'll have to get in there soon or maybe tomorrow and see if I can't find the system.img and/or the boot.img contained within. If I can, I'll be sure to get it patched and try to pass it to the phone.
For anyone trying to use the kdztools, it's outdated and you'll get some error about the headers when you try to extract the Stylo 6's .kdz files. Below are links to a couple of repositories that will be helpful:
- An updated fork of the original kdztools from somebody else that I've forked for laziness (fixes the headers issue)
- A fork of KDZZ, an up-to-date-enough tool for zipping .kdz files into TWRP-able zip files (again, personally forked for laziness)
There's only one problem... Boost Mobile.
I bought this phone from a third party and it is still registered to someone else on the Boost network. Since it's gone through a factory reset and my google account has been added to it, the phone isn't activated on their network and they seem to have disabled my ability to use wifi as they constantly send me screens and notifications trying to get me to activate the device, which I don't have the money to do. So, no internet access; I'll have to adb push and pull files and apks in order to get things working. I could factory reset and not ping their networks or put the other person's SIM in, but for the sake of longevity, I'd love if anybody had a solution to carrier unlocking this thing - or even an idea of what to do for that? Could I flash stock firmware? Is there any process to read the code I need from logcat? Any ideas at all? New ideas, hypothetical ideas, or even old ideas I could shine up and make new? Even just a thought? This is a pain.
I will keep everyone posted! I'd ask you all do the same - about this, and about carrier unlocking just as a possible favor.
PS: Bounty, huh? I could really use the reward. I might just have to take you up on that if we can get this working haha, exciting!

haise.zero said:
Sounds good, thanks for the advice! It's super helpful.
I'll be taking a crack at it here soon, or maybe tomorrow since it's 1:30am and I'm having a drink (depends on my mood ). I'll probably go with fastboot flashing unlock_critical just to be on the safe side of things and have everything unlocked from the get go for development purposes. I did run into an issue when I ran that command already -
C:\Users\myname>fastboot flashing unlock_critical
...
FAILED (remote: Unrecognized command flashing unlock_critical)
finished. total time: 0.006s
I can get into fastbootd on the device, and need to read up on it a bit since nearly every fastboot command I send in is unrecognized (see above) or gets a response like FAILED (remote: Unable to open fastboot HAL)
I'll enable test signing mode on my windows machine and get the right drivers installed, and get fastbootd working and then try again. I'll likely run into a roadblock though, since Boost doesn't exactly want us unlocking the bootloader - nor does LG, apparently...
For now, here's a few resources that might help catch you up on things and possibly give me some more room to wiggle around:
- Android documentation on fastbootd and fastboot being moved to userspace (contains information about the HAL)
- A mildly helpful and more easy-on-the-eyes article that can help explain the above documentation
I'll try and get past this issue. There's gotta be something, somewhere... I first just need to communicate with the phone correctly and get it to do what I need it to do in fastboot mode.
I also have downloaded two different .kdz files and have indeed extracted both of them into .dz files. I didn't get past that last night, so I'll have to get in there soon or maybe tomorrow and see if I can't find the system.img and/or the boot.img contained within. If I can, I'll be sure to get it patched and try to pass it to the phone.
For anyone trying to use the kdztools, it's outdated and you'll get some error about the headers when you try to extract the Stylo 6's .kdz files. Below are links to a couple of repositories that will be helpful:
- An updated fork of the original kdztools from somebody else that I've forked for laziness (fixes the headers issue)
- A fork of KDZZ, an up-to-date-enough tool for zipping .kdz files into TWRP-able zip files (again, personally forked for laziness)
There's only one problem... Boost Mobile.
I bought this phone from a third party and it is still registered to someone else on the Boost network. Since it's gone through a factory reset and my google account has been added to it, the phone isn't activated on their network and they seem to have disabled my ability to use wifi as they constantly send me screens and notifications trying to get me to activate the device, which I don't have the money to do. So, no internet access; I'll have to adb push and pull files and apks in order to get things working. I could factory reset and not ping their networks or put the other person's SIM in, but for the sake of longevity, I'd love if anybody had a solution to carrier unlocking this thing - or even an idea of what to do for that? Could I flash stock firmware? Is there any process to read the code I need from logcat? Any ideas at all? New ideas, hypothetical ideas, or even old ideas I could shine up and make new? Even just a thought? This is a pain.
I will keep everyone posted! I'd ask you all do the same - about this, and about carrier unlocking just as a possible favor.
PS: Bounty, huh? I could really use the reward. I might just have to take you up on that if we can get this working haha, exciting!
Click to expand...
Click to collapse
I have the boost mobile version and I got the cricket wireless version yesterday just for gradient blue.. according to Gsmarena, all versions of the Stylo 6 are identical.. I'm going to try flashing the unlock firmware on the boost mobile version.. it should unlock the sim and no longer ask for activation .. then I'm going to sell it before I drop it .. I'll use my blue one for development

lowkeyst4tus said:
I have the boost mobile version and I got the cricket wireless version yesterday just for gradient blue.. according to Gsmarena, all versions of the Stylo 6 are identical.. I'm going to try flashing the unlock firmware on the boost mobile version.. it should unlock the sim and no longer ask for activation .. then I'm going to sell it before I drop it .. I'll use my blue one for development
Click to expand...
Click to collapse
Could you link me to the unlocked firmware? Is it the Q730M10l? Or another one?
I would love to flash the unlock firmware and factory reset this thing to get some internet and functionality back. It would greatly help with my development
Thank you!

haise.zero said:
Could you link me to the unlocked firmware? Is it the Q730M10l? Or another one?
I would love to flash the unlock firmware and factory reset this thing to get some internet and functionality back. It would greatly help with my development
Thank you!
Click to expand...
Click to collapse
The unlocked model according to Best Buy is LMQ730QM.. I can't find a download source yet but I'm still looking

Weird, my Stylo 6 says its software version is Q730TM... Q730TM10P to be specific There shouldn't be any issues if they're all identical though, right? I can safely flash a Q730QM image on a Q730TM device?
And I'm looking as well - I'll edit this post if/when I find a source
Edit:
Found this, and this, but I'm unsure if Q730QM10c or Q730QM10d is the genuinely unlocked version, (the C variant is USA and the D variant is USL) and I'm also unsure what carrier, if any, NAO stands for (Q730QM10c_00_NAO_US_OP_0908.kdz for example)
I suppose I'll download the kdz and flash it to try it out. I can always revert back to stock if something goes wrong. I'll let you know how that goes
Hmm... I'm having some trouble. kdzdownloader downloads 0kb. I tried switching my useragent but it didn't work out, either. You having any better luck? Able to attach the file?
Woohoo! I got it.
Use this to install the XDM download manager, and then paste this link into a new job (just hit the + button). It just worked for me.
We officially have the .kdz for Q730QM10C! Time to flash it as soon as it's done downloading.

haise.zero said:
Weird, my Stylo 6 says its software version is Q730TM... Q730TM10P to be specific There shouldn't be any issues if they're all identical though, right? I can safely flash a Q730QM image on a Q730TM device?
And I'm looking as well - I'll edit this post if/when I find a source
Edit:
Found this, and this, but I'm unsure if Q730QM10c or Q730QM10d is the genuinely unlocked version, (the C variant is USA and the D variant is USL) and I'm also unsure what carrier, if any, NAO stands for (Q730QM10c_00_NAO_US_OP_0908.kdz for example)
I suppose I'll download the kdz and flash it to try it out. I can always revert back to stock if something goes wrong. I'll let you know how that goes
Hmm... I'm having some trouble. kdzdownloader downloads 0kb. I tried switching my useragent but it didn't work out, either. You having any better luck? Able to attach the file?
Woohoo! I got it.
Use this to install the XDM download manager, and then paste this link into a new job (just hit the + button). It just worked for me.
We officially have the .kdz for Q730QM10C! Time to flash it as soon as it's done downloading.
Click to expand...
Click to collapse
Great job bro.. use dual mode lgup from XDA as it's designed for crossflashing and supposed to have more features than regular lgup.. let me know if you sim unlock with Q730QM firmware.. Q730TM is the Boost Mobile model.. I have that and the Q730AM in gradient blue from cricket wireless.. I want to crossflash both to Q730QM

Alrighty, well I've been halted. Before I could get to flash, I installed the LG drivers because LGUP wasn't detecting my device (or maybe I was just being dumb).
After that... the phone stopped being recognized. In device manager it says Unknown USB (Device Descriptor Failed)
I've looked online, no solutions have helped. I've installed the Google USB drivers through Android Studio, I've uninstalled the device and reconnected the phone, tried reinstalling the LG drivers, I've factory reset the phone, tried a different USB port, a different cable, and nothing. After I factory reset, it showed up for a bit, but upon a reconnection it crapped itself again and refuses to show up.
Any ideas? I can't continue development if I can't communicate with the phone.
Never mind, possibly? It works after uninstalling the device and replugging again... for the 20th time. But ADB still won't recognize the phone even as unauthorized; it just doesn't show up. Weird... I guess I'll tinker and get back to the post here in a while.
It's back to the error... so damn weird. I'll look into it. If and when I find a solution I'll let you know.
Development has been paused for the time being.