How to unlock bootloader and root the LG Stylo 6 and K51 K61 and other K model LG devices

[GMSS75]

Ok I was finally able to connect, back up, bootloader unlock and root my stylo 6.
I could never get the phone to connect with SPFT and mtkclient.

What I eventually did was open the phone and short the test points. (Mobo had to be removed, test points are on screen side of board)
After doing that the phone will connect instantly to mtkclient, and in my case I had no need to use SPFT at all.

Also I updated to latest firmware with Feb 2022 security patch and could still connect no problem and flash boot images.

Hopefully this helps anyone like me who can't get a connection to their phone otherwise.

Thanks to @Warlockguitarman for the tutorial, nice job!

 

[Warlockguitarman]

Without using the test points you can get it to connect to mtk client by using sp flash tool to lengthen the time the stylo 6 is in the correct mode for mtk client, you won't connect to sp flash tool unless you use the by bypass utility, but the sp flash tool method is only needed for windows, use Linux for better connection

 

[Mastercodeon]

Without using the test points you can get it to connect to mtk client by using sp flash tool to lengthen the time the stylo 6 is in the correct mode for mtk client, you won't connect to sp flash tool unless you use the by bypass utility, but the sp flash tool method is only needed for windows, use Linux for better connection

This makes huge sense because that's how I was finally able to get my Stylo to connect to mtkclient last week. I built a program to automate forcing the device into brom by running flash_tool.exe -i and give it an xml file. The xml file tells it to only flash the preloader, and once it connect, it won't return anything when run as a silent process, so then the script knows it can continue and connect with mtkclient. I can power off the phone, arm the app, plug it in and it'll connect right up.
I wonder if there's a command line that will bypass the need for that xml file, and just attempt to flash the preloader in the first place, maybe using some specified scatter.

I'm also curious as to how other mtk phones connect, do they need this method or shorting out the test points? Or is this just strictly an LG/Stylo 6 thing?

 

[Warlockguitarman]

The k51 connects easily without sp flash tool, the Samsung A12 connects with test points, alcatels and many other phones connect easily, the only one I've found to need the sp flash tool process is the stylo 6

 

[shinobisoft]

The k51 connects easily without sp flash tool, the Samsung A12 connects with test points, alcatels and many other phones connect easily, the only one I've found to need the sp flash tool process is the stylo 6

Would you mind doing a small write up on doing this with a Linux machine? I use Linux exclusively and all of the tools have issues with detecting devices when run on an OS via a virtual machine. I'd be more willing to try this then. I've not been active in modding/rooting in many years so I'm pretty damn rusty...

 

[Warlockguitarman]

Look at the read me in the mtkclient folder it tells what you need for Linux

 

[luridphantom]

linux is super easy like everyone is saying. just hold both volume buttons while the phone is off and plug in the cable and mtkclient should work 100% of the time. i had maybe a .001% success rate for windows

a little off topic but switching to linux helped me easily unlock and root my lg m250n and tribute dynasty

thanks for the really detailed write up warlock!!

 

[CXZa]

helped me easily unlock and root my lg m250n and tribute dynasty

Could you provide the exact details? The procedure was probably a bit different than the one explained in the OP??? Thanks.

Here is another way to have root on m250n. Have you tested it?
What I think is different for a user that it doesn't show info about the bootloader being unlocked, which would be nice...
Though I haven't tested so I don't for it sure...
https://xdaforums.com/t/exploit-boo...7-m250-bootloader-secure-boot-bypass.4183545/

 

[luridphantom]

Could you provide the exact details? The procedure was probably a bit different than the one explained in the OP??? Thanks.

Here is another way to have root on m250n. Have you tested it?
What I think is different for a user that it doesn't show info about the bootloader being unlocked, which would be nice...
Though I haven't tested so I don't for it sure...
https://xdaforums.com/t/exploit-boo...7-m250-bootloader-secure-boot-bypass.4183545/

oops my output got cut off a bit but there were no issues unlocking the bootloader through mtkclient for the m250n. only issue is i have no confirmation, not a warning screen or a message in the dev options. i already have temp root through mtk-su so i didnt experiment much further

Preloader -     Mem read auth:        False
Preloader -     Mem write auth:        False
Preloader -     Cmd 0xC8 blocked:    False
Preloader - Get Target info
Preloader -     HW subcode:        0x8a00
Preloader -     HW Ver:            0xcb00
Preloader -     SW Ver:            0x1
Preloader - ME_ID:           
Mtk - We're not in bootrom, trying to crash da...
PLTools - Crashing da...
Preloader
Preloader - [LIB]: upload_data failed with error: DA_IMAGE_SIG_VERIFY_FAIL (0x2001)
Preloader
Preloader - [LIB]: Error on uploading da data
Preloader - Jumping to 0x0
usb_class - USBError(5, 'Input/Output Error')
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
Preloader
Preloader - [LIB]: Status: Handshake failed, retrying...
Port - Device detected :)
Preloader -     CPU:            MT6755/MT6750/M/T/S(Helio P10/P15/P18)
Preloader -     HW version:        0x0
Preloader -     WDT:            0x10007000
Preloader -     Uart:            0x11002000
Preloader -     Brom payload addr:    0x100a00
Preloader -     DA payload addr:    0x201000
Preloader -     CQ_DMA addr:        0x10212c00
Preloader -     Var1:            0xa
Preloader - Disabling Watchdog...
Preloader - HW code:            0x326
Preloader - Target config:        0x5
Preloader -     SBC enabled:        True
Preloader -     SLA enabled:        False
Preloader -     DAA enabled:        True
Preloader -     SWJTAG enabled:        True
Preloader -     EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT:    False
Preloader -     Root cert required:    False
Preloader -     Mem read auth:        False
Preloader -     Mem write auth:        False
Preloader -     Cmd 0xC8 blocked:    False
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader -     HW subcode:        0x8a00
Preloader -     HW Ver:            0xcb00
Preloader -     SW Ver:            0x1
Preloader - ME_ID:            69A24F1A1C650D8183AD3DC76CB8BD73
PLTools - Loading payload from mt6755_payload.bin, 0x258 bytes
PLTools - Kamakiri / DA Run
Kamakiri - Trying kamakiri2..
Kamakiri - Done sending payload...
PLTools - Successfully sent payload: /opt/mtkclient/mtkclient/payloads/mt6755_payload.bin
Port - Device detected :)
DA_handler - Device is protected.
DA_handler - Device is in BROM mode. Trying to dump preloader.
DAXFlash - Uploading xflash stage 1 from MTK_AllInOne_DA_5.2136.bin
DAXFlash - Successfully uploaded stage 1, jumping ..
Preloader - Jumping to 0x200000
Preloader - Jumping to 0x200000: ok.
DAXFlash - Successfully received DA sync
DAXFlash - Sending emi data ...
DAXFlash - Sending emi data succeeded.
DAXFlash - Uploading stage 2...
DAXFlash - Successfully uploaded stage 2
DAXFlash - EMMC FWVer:      0x0
DAXFlash - EMMC ID:         QE13MB
DAXFlash - EMMC CID:        150100514531334d420d52ac90781419
DAXFlash - EMMC Boot1 Size: 0x400000
DAXFlash - EMMC Boot2 Size: 0x400000
DAXFlash - EMMC GP1 Size:   0x0
DAXFlash - EMMC GP2 Size:   0x0
DAXFlash - EMMC GP3 Size:   0x0
DAXFlash - EMMC GP4 Size:   0x0
DAXFlash - EMMC RPMB Size:  0x400000
DAXFlash - EMMC USER Size:  0x3a3e00000
DAXFlash - Reconnecting to preloader
DAXFlash - Connected to preloader
DAXFlash - DA-CODE      : 0x50B76
DAXFlash - DA Extensions successfully added
sej - HACC init
sej - HACC run
sej - HACC terminate
sej - HACC init
sej - HACC run
sej - HACC terminate
Done |--------------------------------------------------| 0.0% Write (Sector 0x0Progress: |██████████████████████████████████████████████████| 100.0% Write (Sector 0x1 of 0x1, ) 0.04 MB/s
DA_handler - Successfully wrote seccfg.

 

[CXZa]

unlocking the bootloader through mtkclient for the m250n

Okay, thanks. That probably did the job if it said so.
Maybe.. Should test by trying write something there.
Like a TWRP etc...

How about bank apks etc. did they stop working at this point already? I know that they do when magisk manager is installed. Though with mtk-su one doesn't really need magisk manager ...

 

[luridphantom]

Okay, thanks. That probably did the job if it said so.
Maybe.. Should test by trying write something there.
Like a TWRP etc...

How about bank apks etc. did they stop working at this point already? I know that they do when magisk manager is installed. Though with mtk-su one doesn't really need magisk manager ...

havent fully explored root on it due to work commitments but feel free to go ahead and try

with mtkclient it should be pretty much unbrickable

 

[Blaze Uchiha]

Is there any chance of a video tutorial for this?

 

[guero.lurias]

HI THANK U 4 tutorial warlockguitarman, was able to unlock bootloader and root with magisk, i got a question, i think i read somewhere that you'd teach how to network unlock by flashing other carrier firmware? could you give me any advice on how to make work? I have the Q730TM10 boost mobile but i want to make it ATT.

 

[Mastercodeon]

HI THANK U 4 tutorial warlockguitarman, was able to unlock bootloader and root with magisk, i got a question, i think i read somewhere that you'd teach how to network unlock by flashing other carrier firmware? could you give me any advice on how to make work? I have the Q730TM10 boost mobile but i want to make it ATT.

Unfortunately ATT made their firmware unavailable for download because they locked their servers down(don't know the specifics), so flashing an ATT firmware is gonna be a fun task unless you find someone willing to give you a copy of the att kdz. Otherwise, you're best bet is to carrier unlock the device (DMed you about that already). But yes, cross flashing is easily done. In your case I'm pretty sure a carrier unlock will be more doable.

 

[JUSTPIE]

If anyone wants to get it root the alcetel 7 6062w just follow the instruction that Warlockguitarman has but with a few modifications to the commands
first make sure to back up with python mtk rf flash.bin and save it somewhere else cause its like 30GB

then do
"python mtk rl" out to get the boot.bin


to unlock the boot loader use
"python mtk da seccfg unlock"

then just follow the magisk app part to patch the boot.bin and make sure u save when u get it to the PC side to save it as
boot.img to make it easier and use this command

"python mtk w boot boot.img"

and ur done, super easy but a little time consuming for the most part

make sure to back up, back up back up, dont be lazy with it just in case

been looking for way for a long time since i got the phone around 2018 and this is the only way it worked

 

[PimpinAintEasy]

Verizon LG K51, used TFT MTK Module to unlock bootloader by going to Brom mode. 1st attempt
Used mtkclient to extract boot_a & boot_b
Installed alpha version of magiks, updated to most current & still says alpha in file name
Patched boot_a & boot_b
Renamed both patched boot.img from .img to .bin also renamed blank vbmeta to vbmeta.bin
Put patched boot_a.bin & boot_b.bin & vbmeta.bin
Placed all 3 files in the mtkclient folder where mtk & mtk_gui are.
Ran python mtk_gui
Connected phone in Brom again
Flashed all of these at the same time
boot_a.bin & boot_b.bin
Vbmeta.bin (blank)

Use vbmeta.bin for each of the vbmeta_a & b's
boot_a.bin
vbmeta_a/vbmeta_system_a/vbmeta_vendor_a
boot_b.bin
vbmeta_b/vbmeta_system_b/vbmeta_vendor_b

Hold power until phone reboots
Complete, enjoy

 

[lentm]

It looks like BROM mode has been removed on Tmobile 20h firmware.
Installed 20f kdz with LGUP and re-rooted. Not sure about 20g.

Q: Is there a way to update the firmware via ota with root?
I tried to restore the stock boot with dd command, but I found out I can't write to boot when I can with OnePlus. :\
I need to find a way to restore the stock boot,
so I can try ota update without rebooting, back up the new stock boot with dd command on shell, and patch the inactive boot slot via magisk.

 

[luridphantom]

It looks like BROM mode has been removed on Tmobile 20h firmware.
Installed 20f kdz with LGUP and re-rooted. Not sure about 20g.

Q: Is there a way to update the firmware via ota with root?
I tried to restore the stock boot with dd command, but I found out I can't write to boot when I can with OnePlus. :\
I need to find a way to restore the stock boot,
so I can try ota update without rebooting, back up the new stock boot with dd command on shell, and patch the inactive boot slot via magisk.

use partition dl in lgup like this guide https://www.xda-developers.com/how-to-bootloader-unlock-root-magisk-tmobile-lg-velvet/

 

[kingrise]

use partition dl in lgup like this guide https://www.xda-developers.com/how-to-bootloader-unlock-root-magisk-tmobile-lg-velvet/

Tempting but it relies on Fastboot to reroot and my version of K61 doesn't have fastboot.

 

[luridphantom]

Tempting but it relies on Fastboot to reroot and my version of K61 doesn't have fastboot.

you're supposed to use mtkclient to reroot not fast boot