• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

PopCaps1996

Senior Member
Last edited:

Tylerlewis395

New member
Jul 14, 2018
4
1
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
 
  • Like
Reactions: Kaybabe4

lowkeyst4tus

Senior Member
May 13, 2010
421
181
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 🔓
Screenshot_20201228-103810.png
 

lowkeyst4tus

Senior Member
May 13, 2010
421
181
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..
Screenshot_20201228-105712.png
Screenshots_2020-12-28-11-16-52.png
 
Last edited:

lowkeyst4tus

Senior Member
May 13, 2010
421
181
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 🍻🥳..
 

Yeedatoy

Senior Member
Jul 18, 2018
160
67
36
Charlotte
Moto G6
LG G7 ThinQ
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.
 
  • Like
Reactions: lowkeyst4tus

lowkeyst4tus

Senior Member
May 13, 2010
421
181
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.
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 😎
Screenshot_20210106-143229.png
 
Last edited:

Yeedatoy

Senior Member
Jul 18, 2018
160
67
36
Charlotte
Moto G6
LG G7 ThinQ
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 😎
View attachment 5179601
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.
 
  • Like
Reactions: lowkeyst4tus

lowkeyst4tus

Senior Member
May 13, 2010
421
181
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🤞
 
  • Like
Reactions: haise.zero

haise.zero

Senior Member
Oct 6, 2017
58
85
Pacific Northwest
LG V60 ThinQ
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🤞
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. :)
 

lowkeyst4tus

Senior Member
May 13, 2010
421
181
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. :)
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 🍻
Screenshots_2021-01-08-11-17-46.png
 
Last edited:
  • Like
Reactions: haise.zero

haise.zero

Senior Member
Oct 6, 2017
58
85
Pacific Northwest
LG V60 ThinQ
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
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 :D). 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. :D

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!
 
Last edited:
  • Like
Reactions: lowkeyst4tus

lowkeyst4tus

Senior Member
May 13, 2010
421
181
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 :D). 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. :D

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!
😂 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 🥳
 

haise.zero

Senior Member
Oct 6, 2017
58
85
Pacific Northwest
LG V60 ThinQ
😂 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 🥳
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!
 

lowkeyst4tus

Senior Member
May 13, 2010
421
181
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!
The unlocked model according to Best Buy is LMQ730QM.. I can't find a download source yet but I'm still looking 🤞
 
  • Like
Reactions: haise.zero

haise.zero

Senior Member
Oct 6, 2017
58
85
Pacific Northwest
LG V60 ThinQ
Weird, my Stylo 6 says its software version is Q730TM... Q730TM10P to be specific :p 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.
 
Last edited:
  • Like
Reactions: lowkeyst4tus

lowkeyst4tus

Senior Member
May 13, 2010
421
181
Weird, my Stylo 6 says its software version is Q730TM... Q730TM10P to be specific :p 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.
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🍻🥳
 
Last edited:
  • Like
Reactions: Bamblixx

haise.zero

Senior Member
Oct 6, 2017
58
85
Pacific Northwest
LG V60 ThinQ
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.
 
Last edited:
  • Like
Reactions: lowkeyst4tus

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    That's my official write up that I posted the other day, it works and that's got all the info, steps for installation, links for the downloads and commands needed to make a proper backup and unlock the bootloader and root it. Works on almost all mediatek devices except the Samsung ones but I'm working on those right now. DM me for my discord if you need help or want to join in on an active group that are working on many devices, over 220 members in a very short time of being active.
  • 7

    The era of LGUP is dead; an update, for those of you who are not in our Discord

    First, some context for the abbreviations used:
    • LGMST = LG Mobile Service Tool, the successor of LGUP. More context within the post.
    • R&D = Research & Development, their department of developers and researches that work on their proprietary and consumer software and solutions
    • LG MC = LG MobileComm., their mobile phone division



    LGUP Background - Goodbye!​



    LGUP was created by their R&D team some time ago for personal use as well as for release to their collaborators, i.e the carriers that sell their devices under their own phone plans with their own software. There were three versions as far as we knew, being Dev, Lab, and CS, and even more configuration based on the UI_Config.lgl file which specified which options were available to which carriers. The LGUP.exe executable does not actually contain all of the instructions, methods, functions etc, but is rather a sort of shell to work with the LGUP_Common.dll library, which is where all of the real instructions are.
    Both of these files were built using C++, which the reverse engineers out there will know is extremely difficult to work with when a program is already compiled, and essentially impossible to decompile back to any sort of original source code, especially when it comes to the actual .exe that utilizes the dll library, since all versions of the exe after 1.14.3 have been packed with Themida. The NSA's Ghidra does an impressive job of working with this, but it is still brain-rotting to read through and work with even in rough C++, hence why there were so few patches ever made to this application and so little support. The good news is, nobody needs to spend four weeks on figuring out the internals of this anymore, and no assembly reverse engineering is required anymore.


    The Good News​



    We now have the latest - and probably the last available, since LG MC is shutting down - tool from LG's R&D department. The original LGMST that we obtained was v1.1.4.3, from April of 2020. The new one that we are now currently working with is v1.1.6.1, from March 24th of 2021, just barely over a week ago as of posting today. This version came with a set of drivers, too, which we're pretty confident are the ones that the development team has been working with. They're an older version, but not too old, and this makes sense because they've likely been using and working on this tool for a while now, and development for an application that interfaces with a device can cause unnecessarily tricky troubleshooting and incompatibility issues for the dev team if they're changing the driver that handles the actual communication all the time. It is much easier and more efficient to work with a consistently working driver version during development - and besides, the LG dev team's motto has always been "if it isn't broken we don't need to change it."

    LGMST is written in .NET, which the reverse engineers and any .NET developers will know is actually quite exciting to work with when doing reverse engineering. This is because .NET applications can be decompiled to C# and/or IL code that is nearly if not completely identical to the original source code. However, version 1.1.6.1 is far more heavily obfuscated than 1.1.4.3 was. We wouldn't be working with the new one and wiping our previous progress if the last version we had wasn't a year old. We wanted to avoid compatibility issues, and decided to move forward with this version instead and essentially start over.

    What this means for you guys is that you will have a higher level of compatibility and functions to work with. Absolutely worst case scenario: we can offer the opportunity to flash your devices and read information from a tool that YOU can easily decompile and work with by hand to tweak and alter as much as you'd like. Providing information about the full capability range of the program is something I want to refrain from doing though, because I don't want to make promises we cannot keep; however, I will state that with everything we've seen, it is all super exciting and should leave LGUP in the dust by comparison.


    The Crappy News​



    It's not really bad news so I refrained from using that term.

    Look, it'll be a while. We're not right around the corner from this, but we're closer than we have ever, ever been. I have full confidence in this program and the team that's working on this with me. There is a lot of functionality offered in this tool, and thus there is a lot more ground to cover than simply flashing firmware onto our devices. I can't go into detail here as to why, because it has been evident in the past that LG is watching us here in XDA, and I don't want to risk unveiling what we do and don't know.



    A Note to the LG R&D Team​



    Hi! I'm Haise, and in this message, I speak for the LG mobile device community.

    I wouldn't be here - none of us would be here - and I wouldn't have learned and obtained everything that I've obtained if it weren't for you. I thank you for this opportunity to learn and expand my skillset, but listen, I shouldn't have had to. None of your community and consumer base should be sitting here excited about the news I'm unveiling to them. My team, your community, and myself from the very beginning should have had the opportunity to unlock our devices from the get-go. And fine - secrets, competition, blah blah blah, I get it. You couldn't back then. But you can now, because it's over. Your Mobile Communications division has met its end, and support for every last one of your mobile device consumers has ended. Your last updates are rolling out, and every single one of your devices will reach its end of life, with no system updates, no security updates, no way to protect ourselves and no way to improve or work on our devices.
    So support us. It's over. You can finally let us unlock our devices now. You have solutions, too. Change your bootloader unlock page online to support all LG mobile devices and keep the portal up, or release your factory/engineering bootloader files for our devices, or make a crappy tool that'd take three days to build with three developers that can download the file and flash it to our device - hell I know a few people already that you could hire under contract - or just figure it out your way. It really isn't too late. You have every given moment right now to make a decision, and you should make the right one, because we aren't here to steal anything. We aren't here to leak your software and firmware information to competitors and it doesn't matter now, anyways, because they don't have you to compete against anymore.
    We purchased your devices. We own them, rightfully, but you've built them in such a strictly specific way that prevents us from taking advantage of our ownership. Your terms and conditions treat a purchase as if it were a lease.
    And if there's some sort of specific reason or restriction that you can't do that, then fine - at least voice it to us. Notice us and acknowledge us, because you built incredibly beautiful and impressive devices, and you had a lot of loyal fans of those devices out here - you still do. Don't let them down, don't leave them empty handed, don't completely screw them by leaving them with locked pieces of crap that they can never, ever improve; swallow your pride, work out a few things, let go of your uptight attitude and just let us do this on our own, because you're letting of of us now.
    Give us our freedom, because we loved you as a company and what you provided to us, and you did a good job with this. Don't ruin everything you've ever built and don't screw over your consumers. Let it go, and give us our freedom. We've earned it. They've earned it.
    5
    Mod edit: @Warlockguitarman I've edited your post and deleted other of your posts throughout different threads, which you posted lately.

    As an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to share references to their social media in their own development threads. These conditions obviously don't apply to your posts, you or this thread. For this reason the reference to your social media has been removed. Please refrain from sharing of social media in future. Thanks for your cooperation!

    Regards
    Oswald Boelcke
    Senior Moderator

    With a little help we found out all that is needed to build a new unlocking tool, I'm working with some developers to make this happen, it won't be a tethered unlock so no need to reflash the phone after each boot like what haise is trying to do, and no worries about glitches or any issues accept secured boot looks like it will take some more time to disable but we also have the source code for the bootloader so it should be in the works too, just taking me longer since I was banned from Haise server by him because I didn't want to stop my research and let him discourage me from continuing my quest for knowledge
    4
    discord invite link


    i have the lg stylo 6 LM-Q730MM by metro usa.

    i have grab the ota.zip through a bug report then downloaded it
    an used payload dumper python

    an these are my results

    untouched Lg Stylo 6 7-25-20 ota.zip https://www.mediafire.com/file/hx7k0fajaw2xl1i/76c9e56e3d40225a77a4dadacd68f89995801e6b.zip/file

    Extracted payload.bin https://www.mediafire.com/file/s2xen6qtgxm4s5t/Lg_Stylo_6_7-25-20_payload_extract.zip/file

    hope this helps root process
    3
    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🤞
    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. :)
    2
    A few updates!

    Got through to the main window tonight. The app has several kind of obfuscations but we're working with it pretty well. LG went reaaally out of their way to break this app in all sorts of ways, presumably so that any R&D guys who get a new update wont be able to mess with it - or because we have it and they don't want us to do exactly what we're doing anyways. Besides, we have backups of earlier versions anyways so it doesn't matter.

    Anyways, I've attached a screenshot - it's a little broken right now so don't mind that, we're definitely in the development phase, not even pre-alpha - so feel free to take a look! It's nice and shiny. :D

    Tonight and tomorrow we'll be doing something really cool, too. This is also one of the last posts that'll be here for a while. Stay tuned and again feel free to join our discord!


    prepreprepreprealpha.png