Database Info

LG G3 D850 is stuck on boot loop Error 570/8130

vI accidently flashed the TWRP recovery image to my kernel and ever since then my g3 been stuck in this awful boot loop that won't even pass the LG logo.
I've been looking to find different ways to successfully unbrick my g3 and I keep running into the LG Flash Tool. I downloaded it but I cant seem use it because I don't have the .KDZ file appropriate for my phone.
if anyone knows of a different method of unbricking my phone please help, or if you know where I can find the .kdz file appropriate for the D850
{
"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"
}

12345678910111213141516 said:
I accidently flashed the TWRP recovery image to my kernel and ever since then my g3 been stuck in this awful boot loop that won't even pass the LG logo.
I've been looking to find different ways to successfully unbrick my g3 and I keep running into the LG Flash Tool. I downloaded it but I cant seem use it because I don't have the .KDZ file appropriate for my phone.
if anyone knows of a different method of unbricking my phone please help, or if you know where I can find the .kdz file appropriate for the D850
Click to expand...
Click to collapse
I'd suggest you follow the actual guide.. - http://forum.xda-developers.com/showthread.php?t=2785089 ... If you follow it you'll see there is two different methods and that the D850 AT&T version is TOT method only and in which you download the zip, extract it and flash it.

hyelton said:
I'd suggest you follow the actual guide.. - http://forum.xda-developers.com/showthread.php?t=2785089 ... If you follow it you'll see there is two different methods and that the D850 AT&T version is TOT method only and in which you download the zip, extract it and flash it.
Click to expand...
Click to collapse
You're right. I didnt see that first time but have tried that method prior to moving on to the .kdz one. The reason why i did so was because the LG FLASH TOOL would stop working. Im not sure if its because im on windows 10 or what.

12345678910111213141516 said:
You're right. I didnt see that first time but have tried that method prior to moving on to the .kdz one. The reason why i did so was because the LG FLASH TOOL would stop working. Im not sure if its because im on windows 10 or what.
Click to expand...
Click to collapse
Windows 10 can cause issues. But if you have the D850. Tot is the only way.
Sent from my iPhone using Tapatalk

i was able to flash via LG flash tool TOT method fine no more then an hour ago running windows 10. Keep in mind like that OP says "it could take up to 45 mins".. although i flashed successfully it did take near that amount of time.. GL

First things first, can you go into download mode or not? If the answer is yes, then you have to tell where exactly does the Flashtool stop? Because the only method with d850 is tot method. Did you connect it on port 41 or not? If yes, have you provided it with proper tot file and dll? If yes, then Does the flashtool stop at ~ 6% where it says it cannot recognize your phone model, or @ ~ 13%, where it says it cannot go into download mode? You have to be more specific in describing your problem. If the answer is no to the first question, then how does windows recognize your phone? Is it connected as Android Device, or QDLoader 9008, or QHSUSB_BULK?
In my view, if you have just messed with the kernel (boot) partition, you should still be able to go to download mode and flash the correct firmware by following the tot procedure detailed by hyelton.

stops at 6%(cant change to download mode)
unikorn74 said:
First things first, can you go into download mode or not? If the answer is yes, then you have to tell where exactly does the Flashtool stop? Because the only method with d850 is tot method. Did you connect it on port 41 or not? If yes, have you provided it with proper tot file and dll? If yes, then Does the flashtool stop at ~ 6% where it says it cannot recognize your phone model, or @ ~ 13%, where it says it cannot go into download mode? You have to be more specific in describing your problem. If the answer is no to the first question, then how does windows recognize your phone? Is it connected as Android Device, or QDLoader 9008, or QHSUSB_BULK?
In my view, if you have just messed with the kernel (boot) partition, you should still be able to go to download mode and flash the correct firmware by following the tot procedure detailed by hyelton.
Click to expand...
Click to collapse
I followed step 7 and at step 10, I press down power button and it starts and stops immediately at 6%(cant change to download mode).what can I do?

Can't flash "correct model ROM on Frankephone

I bought a LG G2 d802 from ebay.
Everything seemed to work as should until i tried to upgrade software though PC Suite.
Phone updated and acted erratic with the touchscreen and god knows what else.
So i started digging on xda and found out that in the backcover of my phone it says d800 so i flashed a d800 tot (hex edited file) and i hardbricked it.
When i finally restored it i went further down to the mainboard and saw that my phone is actually a d801.
Now when i flash (through tot or kdz) d801 and d800 roms my phone hardbricks (somethimes in fast boot sometimes in "bulk" mode).
But when i flash a d802 rom it installs and boots normally but when it opens up i have the same issue with the touch.
Any ideas would be welcome as i spent 2 fully days flashing and restoring this thing
{
"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"
}

Any insights people?
I've seen more difficult problems being solved in this forum!
Sent from my V919 3G Air DualOS using Tapatalk

leris2 said:
Any insights people?
I've seen more difficult problems being solved in this forum!
Sent from my V919 3G Air DualOS using Tapatalk
Click to expand...
Click to collapse
hi i am on the same cuest as you are. i faced this once and got victorious after 5 long days. back then i had a moto g wich i changed for a lg g2 with touch problems. after flashing multiple 802 roms i opened the phone and find out that the phone was in fact a D800 ATT. i fought a lon fight trying to fix it and after five days and almost killing the phone and giving up.. i did it. that g2 is now my wifes phone. wich she loves.
now ive traded a galaxy s3 for another G2 with the same problem. i was for sure thinking that this was also a d800. both phones have D802 back covers like yours and software too. when i opened this one results that it is a D801 TMOBILE. i had it for a day now. i managed to rooted and to intall a recovery. im not completly sure what to do now. im searching for a d801 to flash on the d802 software. so far no luck. i readed that with the correct kernel the screen problem will be gone. im being more careful this time beacuse i dont want to have to kill this phone too just to recover it after. i want to do it more clean and quick this time.

I'm away right now.
Will post how i solved it when i get home
Sent from my LG-E980

---------- Post added at 01:17 AM ---------- Previous post was at 01:15 AM ----------
leris2 said:
I'm away right now.
Will post how i solved it when i get home
Sent from my LG-E980
Click to expand...
Click to collapse
aaah. well, that is good. ill wait to see how yo did it.

http://androidforums.com/threads/bricking-and-unbricking-fake-lg-g2-d802-bought-on-ebay.952680/
Use this guide.
I entered fastboot and unbricked it using srk tool and the 10v tot files.
Then i updated using flashtool as normal and now it is d801 as normal.
Keep me posted i might be able to help you further.
Sent from my LG-E980
Remove the buttons plate and see under the motherboard the actuall number of your phone like in my picture.
Only then you can be sure of your actuall model.

that is more or less what ive did the first time with my wifes d800 (faked as a D802). that was several months ago and i cant remember everything. i do remember that i just had fastboot in that moment and using repartition table i were able to fix it.
now, this is a D801 like yours, mine boots entirely with its D802 rom just with the screen touch hardly usable. i got it rooted. im able to use adb, download mode and everything. what you suggest me to do?

I had the exact behavior.
What i did and worked was to get to fastboot mode and flash the files that mentioned in my previous post.
Now for me to get to fastboot was the tricky part.
I had to fully brick the device to get to it.
Sent from my LG-E980

ok, i was hoping to find another way. well... i have it on lollipop and have a D801 lollipop kdz. can i use its extracted files instead of the tot files ones? because the TOT is around 2.2 gigs and trying to extract the zip file i found and error. it says that it is a unknown format or is damaged. i ask because i have a poor connection and the wait to download it again is long.
another cuestion, did you format partition before flashing the parts?

ok i screw it. i was flashing recovery and rebooted into fastboot mode. PC was showing QHSUSB bulk... with a lot of external devices. now is showing marshal london HS-USB diagnostics 9006 (COM 5) and the same lot of external devices. i guess this is the moment to use TOT extracted files? or can i use the kdz ones? do i have to repartition?
sorry to bother.

i was flashing partition using fastboot, i got a problem writing 'primaryGPT'... FAILED (remote: partition table doesn´t exist) i see that on the link you gave the guy mentions something about primaryGPT. but i dont know how to get pass from this point..

For me only using the v10 tot extracted partitions and replacing the files in the srk tool worked.
Search for srk tool here on xda.
Try to restore your fastboot mode and then flash the above.
The tool is self explanatory.
Good luck
Sent from my LG-E980

hi, i have the srk tool. im going to try restoring my fastboot but i dont know how. wich file do i have to replace in the srk tool?

Follow the instructions on how to restore via fastboot mode.
You have to extract the tot file first.
Google it on how to.
It is not a very easy procedure but once you get used to it you will figure it out.
Sent from my LG-E980

the thing is that now i lost fastboot. the phone doesnt do more than turning off and on the screen.

When you connect it to the pc it shows too many empty drives that need formating?
Sent from my LG-E980

yes, 12 of them

This is the qbulk mode(or something like that) find the repair option for it in the tool to enable fastboot.
Sent from my LG-E980

leris2 said:
This is the qbulk mode(or something like that) find the repair option for it in the tool to enable fastboot.
Sent from my LG-E980
Click to expand...
Click to collapse
thank you man. i recovered fastboot using srk. now i will try to continue

this fastboot isnt responding to commands...

Flashing Firmware: A Simple Guide

When it comes to flashing firmware for the XZ Premium, I know there is a plethora of information scattered through many threads in this section. Quite frankly, I was a little overwhelmed with the whole flashing process, and, despite everyone's best efforts, was totally lost. I just wanted to flash my USA XZ Premium to the Central Europe FW to enable the fingerprint reader, but I didn't want to alter the radios, etc like in the other thread that describes the process.
So, after a bit of trial and error, I decided to put together a simple guide that I hope is easy for those with a little less "flashing" experience. I'd like to point out that none of this information is my own; I'm simply compiling it in a way in which I believe will be helpful. This post is only possible because of all the people who have contributed in the various flashing threads thus far, so many thanks to all of them. Also, I know it's a touchy subject around these parts, but I wanted to give a shout out to the developer of Newflasher -- without his tool, we all still may not have method to flash our XZPs. Thank you, sir.
Anyway:
1. Find, download and install/extract Newflasher, XperiFirm, Flashtool and the official Xperia Companion application.
2. XperiFirm: download whichever variant of the FW you’d like to load. Be sure you are choosing the correct version of your hardware.
3. Flashtool: go to the application folder, then go to the drivers folder. Run this app, and check the boxes next to Flashmode Drivers and Fastboot drivers. You will need these installed to avoid any possible connection issues with Newflasher.
4. Open the folder which contains Newflasher so you can view all of the contents. Do the same with the firmware folder that you now have which was downloaded from XperiFirm (Ex. G8142_Customized CE1).
5. Copy all of the .sin files, as well as the partition and boot folders, from the firmware folder over to the Newflasher folder. Create a new folder name "partition," and extract the existing partition folders files (that you copied from the firmware folder) in to the new partition folder.
6. Power down your phone and wait 5 seconds. Hold the volume down button with the device powered off, and plug your device into your PC.
7. Run Newflasher.exe. You should now start to see the application working (this process took about 5-10 minutes for me). It will tell you when you can disconnect.
8. Open the Xperia Companion application, and, following the on-screen instructions, do a Software Repair on your device.
9. Start your device like normal, and you should have your new software loaded!
Thanks again to all who have contributed to this process!

thanks just flashed mine from Three over to the UK customised
working great

Thanks for the guide. But someone can make a YouTube video how to flashing xzp with newflasher please! Cant find one there ty.
Sent from my G8141 using Tapatalk

Question
If I flash my phone ( details in screenshot) will it remove demo mode application that installed in it? Retail demo mode.
{
"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"
}
Thanks in advance. Don't be hard on me I am new to this. :fingers-crossed:

For those left still confused by the lack of detail above, here's a more visualized and well explained flashing method I found and mentioned in my XZP flashing thread a while back. Also has links to newflasher - which this one doesnt
https://forum.xda-developers.com/showpost.php?p=73176149&postcount=3

Ok it worked for me, just the step of repairing with pc companion did not work, pc companion restores firmware original telcel MX, so after flashing no longer repair with pc companion and finally worked.
Firmware flashing 45.0.A.7.120 generic Latam
Thanks for this tutorial !!! I hate the telcel personalization !!!

kinkyK said:
thanks just flashed mine from Three over to the UK customised
working great
Click to expand...
Click to collapse
After flashing what system apps were preinstalled? Im just wonderinf because I just got my XZ premium today and there seems to be a fair bit of bloat I wanna get rid of but cant with out root and dont wanna root because of drm, also because there isnt much support.

Just the standard Sony stuff really mate no operator stuff
Seems much better like

kinkyK said:
Just the standard Sony stuff really mate no operator stuff
Seems much better like
Click to expand...
Click to collapse
Did you have spotify pre installed?

RJASSI21 said:
After flashing what system apps were preinstalled? Im just wonderinf because I just got my XZ premium today and there seems to be a fair bit of bloat I wanna get rid of but cant with out root and dont wanna root because of drm, also because there isnt much support.
Click to expand...
Click to collapse
Try this tutorial. I've successfully deinstalled some system apps without root:
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/

RJASSI21 said:
Did you have spotify pre installed?
Click to expand...
Click to collapse
Yes m8

kinkyK said:
Yes m8
Click to expand...
Click to collapse
OK thanks for the info.

If you flash the ce1 firmware to the us xzp do you retain the ability to receive ota updates? Do any problems arise from flashing international Firmware?

IS33D34DP30PL3 said:
If you flash the ce1 firmware to the us xzp do you retain the ability to receive ota updates? Do any problems arise from flashing international Firmware?
Click to expand...
Click to collapse
You'll still be able to receive OTA updates. No problems /should/ occur when flashing the international firmware. My brother has the XZP (US Variant) and I him flash a UK firmware to enable the fingerprint sensor.

IS33D34DP30PL3 said:
If you flash the ce1 firmware to the us xzp do you retain the ability to receive ota updates? Do any problems arise from flashing international Firmware?
Click to expand...
Click to collapse
CE1 seems to get FW updates later rather than sooner, so keep that in mind when flashing.

The_Newtype said:
CE1 seems to get FW updates later rather than sooner, so keep that in mind when flashing.
Click to expand...
Click to collapse
I flashed my US version with 45.0.A.5.1 when i got it. I'm yet to receive an OTA.

Guys I need help to finishing flashing my XZP
Guys maybe im doing something wrong or missing something here, please someone guide me because this is my 1st time flashing a phone.
Im trying to flash my US version XZP dual sim (G8142) to Central Europe(CE1) firmware to enable fingerprint sensor, but when I start newflasher, it wont do anything, and it just says: Optional step! Type 'y' and press enter if you need Gordon flash driver, or type 'n' to skip. This creates GordonGate.7s archive in the same dir with newflasher.exe!
and it just stays there and do nothing, what should i do? type 'y' or 'n'? i dont know what are the next steps...
Because in step #7 you said that you will see the application working (about 5-10 minutes), but in my case I dont know what im missing because when I start the program it just doesn't start doing its thing.
someone please tell what im doing wrong or if I should install that Gordon flash driver because I really wanna enable the fingerprint.

johnpgv said:
Guys maybe im doing something wrong or missing something here, please someone guide me because this is my 1st time flashing a phone.
Im trying to flash my US version XZP dual sim (G8142) to Central Europe(CE1) firmware to enable fingerprint sensor, but when I start newflasher, it wont do anything, and it just says: Optional step! Type 'y' and press enter if you need Gordon flash driver, or type 'n' to skip. This creates GordonGate.7s archive in the same dir with newflasher.exe!
and it just stays there and do nothing, what should i do? type 'y' or 'n'? i dont know what are the next steps...
Because in step #7 you said that you will see the application working (about 5-10 minutes), but in my case I dont know what im missing because when I start the program it just doesn't start doing its thing.
someone please tell what im doing wrong or if I should install that Gordon flash driver because I really wanna enable the fingerprint.
Click to expand...
Click to collapse
You need to extract the Gordon flash driver and install it manually

hi all, good to be here
thanks for tutorial, sounds good
two questions only:
the downloaded firmware (CE1) contains much more files inside as mentioned in the 5th step of the tutorial
are these files really not needed?
and
if something may go wrong and flashing will be unsuccessful, will it harm the phone? if yes, can i restore the last firmware with Xperia Companion?
thank you

help
Is there anyway possible that you could post a video of how to do it. I'm a better visual learner and I have been struggling for quite sometime now to complete the task so that I could flash my US version xz premium to the Central Europe so that I may use my fingerprint scanner.

[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.

General SM-A125U Multitool Kit (Root/TWRP/Unlock/Unbrick)

Here is a toolkit of several tools ive collected and put together for the A12 in a single pack to help see through all the clutter and chaos of this forum, i have an A125U (converterd to a-125w) so thats all i can confirm working 100% but im 99% sure the methods will work for any mediatek version of this phone just make sure to use your correct firmware
the tools included will allow you to :
Enable OEM Unlock +Unlock the Bootloader
Create Scatter Firmware
Unbrick your device if stuck in Brom/Da mode
Root Your Device / Install TWRP
Enter Brom Mode
and more
All instructions are included inside the main folder of tools, seriously... and i mean seriously...please read the 3 or 4 different guides/methods to see which ones you actually need to do. Some are not needed depending on your end goal. I spent a month making every error possible and testing things so you dont have to so save yourself the trouble and read through
Ill do my best to answer any questions or issues you might have but please...please use your eyeballs and google.. i really dont want to have to answer questions like "how flash magisk" etc. Google is there.. it is your friend , use it. XD
A12 Toolkit.zip | by Privyetcyka for Galaxy A12 Nacho
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com

Thank you, I hope I can figure it out with the translator, I went to try ..

fackstrot said:
Thank you, I hope I can figure it out with the translator, I went to try ..
Click to expand...
Click to collapse
No problem. What exactly are you trying to do, just unbrick the phone and flash stock firmware? I can make the instructions more easy to translate for you

PrivyetCyka said:
No problem. What exactly are you trying to do, just unbrick the phone and flash stock firmware? I can make the instructions more easy to translate for you
Click to expand...
Click to collapse
I did something with it when I reset Frp and now it does not start, it is defined simply as the mtk port...does not enter into any of the modes (recovery or loading) does not respond to charging
yes i just want to run it on stock firmware

fackstrot said:
I did something with it when I reset Frp and now it does not start, it is defined simply as the mtk port...does not enter into any of the modes (recovery or loading) does not respond to charging
yes i just want to run it on stock firmware
Click to expand...
Click to collapse
Just follow the Unbrick directions that will get your phone back working stock. If you don't have scatter firmware for your device youll need to make that also, tools are included

PrivyetCyka said:
Just follow the Unbrick directions that will get your phone back working stock. If you don't have scatter firmware for your device youll need to make that also, tools are included
Click to expand...
Click to collapse
I followed the steps, I was inattentive myself) but still ran into a problem

when you enter Samsung Enable Brom by PGPT, nothing happens to the phone...
{
"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"
}

Through such a bypass, I was able to see at least some kind of response from the flash tool, but the error

well, if I put it from SM-A125W, then the rollback error

Will that work for the Samsung Galaxy A13

Apologies for the stupid question, but this part:
**Follow the instructions Provided by A125U Root bit 3 by FixMX file to actually unlock the bootloader and root the device**
don't seem to be included in the zip file, unless I'm a buffoon and didn't notice them.
Is a FixMX a user who already wrote a guide for this? I just need to unlock the bootloader and then I can follow basic directions from there to get what I need.

Ansemseekerofdarkness said:
Apologies for the stupid question, but this part:
**Follow the instructions Provided by A125U Root bit 3 by FixMX file to actually unlock the bootloader and root the device**
don't seem to be included in the zip file, unless I'm a buffoon and didn't notice them.
Is a FixMX a user who already wrote a guide for this? I just need to unlock the bootloader and then I can follow basic directions from there to get what I need.
Click to expand...
Click to collapse
I have no idea which directions your directions your talking about the only ones I wrote are the ones in the main folder , probably with a bunch of exclamations. I can't remember and don't have the file with me right now but as far as unlocking the bootloader you just need to get the phone to accept different firmware. Try flashing Sm-a125w Canadian version XAS

fackstrot said:
when you enter Samsung Enable Brom by PGPT, nothing happens to the phone...
Click to expand...
Click to collapse
Nothing will happen. Once your in brom mode you need to use another tool to unlock the bootloader and disable secureboot everything is included

PrivyetCyka said:
Nothing will happen. Once your in brom mode you need to use another tool to unlock the bootloader and disable secureboot everything is included
Click to expand...
Click to collapse
Nothing happened .. I got upset and put the phone on the shelf, told the owner to pick it up and carry it to the service center, but they didn’t take it to the service center

fackstrot said:
Nothing happened .. I got upset and put the phone on the shelf, told the owner to pick it up and carry it to the service center, but they didn’t take it to the service center
Click to expand...
Click to collapse
Nothing is supposed to happen if nothing happens that is good . Just leave the phone connected how it is and use a mediatek unlocking tool

When i get to the oart in your instructions that says to open the MTKMETATOOL file i just get a message informing me that it has expired and to see the developer. Is there another link to open the tool somewhere else? Ive looked at the other option to get a windows tool from github that you included but i can admit that im not as savvy as i would like to believe and all ive ever used is windows so i have no idea what to do with all of that on github. I hate having to bother you guys but i really would appreciate the help. Thanks in advance and you guys are just awesome!

ronnieshane1 said:
When i get to the oart in your instructions that says to open the MTKMETATOOL file i just get a message informing me that it has expired and to see the developer. Is there another link to open the tool somewhere else? Ive looked at the other option to get a windows tool from github that you included but i can admit that im not as savvy as i would like to believe and all ive ever used is windows so i have no idea what to do with all of that on github. I hate having to bother you guys but i really would appreciate the help. Thanks in advance and you guys are just awesome!
Click to expand...
Click to collapse
Change date to 25 may 2022 to get working

Ok... im trying to repair mi phone and failed i follow exactly as i seen in the readme instructions on the unbrick folder and nothing... i got 2 errors in relation of super.img (im trying to flash the last android 11 firmware on the phone A125MUBS3BVF1) if i uncheck the super the phone flash correctly but doesn't boot so what next...?

fackstrot said:
Through such a bypass, I was able to see at least some kind of response from the flash tool, but the error View attachment 5664401
Click to expand...
Click to collapse
And now i had this error i think using the format all + download relocks the bootloader sp flash tool is asking me to download signed images i can't exit from that so i give up and buy another mainboard

My last reply...
I uploaded some images to get BROM working on A125M this zip includes
Preloader and PGPT files from 4 firmwares
Android 10 Binary 1 (AUC1)
Android 11 Binary 1 (BUF9)
Android 11 Binary 3 (BVF1)
Android 12 Binary 3 (CVH3)
Plus i will modify this post because im uploading CVH3 firmware for SP Flash tool flash (Includes the scatter) pls disable the auth using mtkmeta or the python coded program (used 3.7.9 and worked using the shell)
PGPT and Preloader images