LG V30 Unbrick guide (Qualcomm EDL 9008 Mode, Hardbirck, with no download mode) - LG V30 Guides, News, & Discussion

If you try this method, I nor anybody else is responsible for any further damage done to your phone.
Models Confirmed : V300L
We currently have firehose for V30.
Therefore, we can program UFS flash memory in 9008 mode.
It requires rawprogram?.xml(s) and patch?.xml(s) to program it.
It's easy to generate rawprogram?.xml(s) from kdz file, but generate patch?.xml(s) is not easy. (Unfortunately, I couldn't have time to generate patch?.xml(s)).
I have edited kdztools to generate rawprogram?.xml(s) easily (You can generate it by using "-r" argument. Currently, generate patch?.xml(s) is not supported. I'll add it soon).
I used patch?.xml(s) in post. it works well, but boot loop in the LG Logo.
However, it was possible to enter download mode.
------------------- GUIDE -------------------​1. Download rawprogram?.xml patch?.xml with images from link. (It uses V300L30h000906.kdz)
2. Download firehose (prog_ufs_firehose_8998_lgev30.elf) from link.
<< Linux >>
3. Build qdl or download pre-built binary
4. Extract zip or tar.gz files 1, 2, 3 in any folder.
5. Run
Code:
$ ./qdl --storage ufs prog_ufs_firehose_8998_lgev30.elf rawprogram0.xml patch0.xml rawprogram1.xml patch1.xml rawprogram2.xml patch2.xml rawprogram3.xml patch3.xml rawprogram4.xml patch4.xml rawprogram5.xml patch5.xml rawprogram6.xml patch6.xml
in the terminal.
6. If LG logo shows, enter to the download mode.
<< Windows >>
3-6. You can program by QFIL similar as qdl.
7. Connect to any Windows PC with LGUP (must support Android Pie).
8. Flash kdz with ChipErase. (IMPORTANT)
9. If it boots successfully, your device has unbricked.

you can create rawprogramer and patch.xml with this program
I have already tried it on lg v10 kdz with successful.
after extract kdz :
1-open qualcomtool 2.4 and go to EMMC tabe.
2-clic browse and select primarygpt_0.bin
3- select all partitions and click exract partition
4- click extract firmware
you will find every things you need in extracted folder.
you can edid rowprogramer.xml with notepad ++ .
edit : tryed with lg v30 kdz not work
(gpt not present when select file)

Thank you for your work

download problem
quickwshell said:
If you try this method, I nor anybody else is responsible for any further damage done to your phone.
Models Confirmed : V300L
We currently have firehose for V30.
Therefore, we can program UFS flash memory in 9008 mode.
It requires rawprogram?.xml(s) and patch?.xml(s) to program it.
It's easy to generate rawprogram?.xml(s) from kdz file, but generate patch?.xml(s) is not easy. (Unfortunately, I couldn't have time to generate patch?.xml(s)).
I have edited kdztools to generate rawprogram?.xml(s) easily (You can generate it by using "-r" argument. Currently, generate patch?.xml(s) is not supported. I'll add it soon).
I used patch?.xml(s) in post. it works well, but boot loop in the LG Logo.
However, it was possible to enter download mode.
------------------- GUIDE -------------------​1. Download rawprogram?.xml patch?.xml with images from link. (It uses V300L30h000906.kdz)
2. Download firehose (prog_ufs_firehose_8998_lgev30.elf) from link.
<< Linux >>
3. Build qdl or download pre-built binary
4. Extract zip or tar.gz files 1, 2, 3 in any folder.
5. Run
Code:
$ ./qdl --storage ufs prog_ufs_firehose_8998_lgev30.elf rawprogram0.xml patch0.xml rawprogram1.xml patch1.xml rawprogram2.xml patch2.xml rawprogram3.xml patch3.xml rawprogram4.xml patch4.xml rawprogram5.xml patch5.xml rawprogram6.xml patch6.xml
in the terminal.
6. If LG logo shows, enter to the download mode.
<< Windows >>
3-6. You can program by QFIL similar as qdl.
7. Connect to any Windows PC with LGUP (must support Android Pie).
8. Flash kdz with ChipErase. (IMPORTANT)
9. If it boots successfully, your device has unbricked.
Click to expand...
Click to collapse
thank you so much,but can't download zip from this website,if you can offer other download way,such as google,mega,onedrive,i will apreciate it so much,thanks for your work

Johoneycn said:
thank you so much,but can't download zip from this website,if you can offer other download way,such as google,mega,onedrive,i will apreciate it so much,thanks for your work
Click to expand...
Click to collapse
Sorry for the late reply
mega. nz/#!zCZBkC4D!Vxo9wrd1c9vsZgCfQIrLelcp3unTY7sJAqMXjANvzjQ is V30_UNBRICK.zip
and mega. nz/#!PLIBzQ6L!JKtfq_RH2iFgcQckkRi_LtZGt9u2zaO2YF6x8dtHL6A is a firehose.

It is a shame we resort to such lengths for this. Shame on vendors. It is like pure gold or diamonds when we come across a programmer...

Hi, @quickwshell, could you see this: Help! bootloop per 5 sec, cannot enter rec, download or fastboot. Does the problem I'm facing now is what your method targeting to?

@quickwshell
Thank you so much for sharing firehorse for v30 and this solution. I have LS998 bricked bootloop after interrupting upgrade as @zacox123. I tried your files posted but still phone cant get download mode. Now Im trying to create rawprogram.xml and patch.xml from specific firmware model ls998 but I want to know what partitions are necesary just for getting download mode and then try to upgrade for usb mode.
Could you please help me?
thanks in advance

Pulian said:
@quickwshell
Thank you so much for sharing firehorse for v30 and this solution. I have LS998 bricked bootloop after interrupting upgrade as @zacox123. I tried your files posted but still phone cant get download mode. Now Im trying to create rawprogram.xml and patch.xml from specific firmware model ls998 but I want to know what partitions are necesary just for getting download mode and then try to upgrade for usb mode.
Could you please help me?
thanks in advance
Click to expand...
Click to collapse
How did you do with your phone? Have you made your phone into 9008 mode? Did you use the correct tool?
I have not processed my problem yet. But I read some other posts introducing that, use qpst or miracle box or any similar tools with the edl file provided by @quickwshell to flash in twrp directly, instead of getting download mode back. Maybe you can have a trial.

I was converting my lg [email protected] for unlocking. I have tools for flashing and I did it before with others phones. Accidently flashing process was interrupted and phone got that condition, no download mode. Now I'm using testpoint connection and UMT (tool for repair Qualcomm Phones) for trying to recover download mode. I suppose you can use QFIL for programming after we have correct rawprogramer.xml and patch.xml. Let me finish my test and I'll post results.
Pd: bootloader is not unlocked and I don't know if I can write twrp and it'll work.
Could you share links referring this topic and phone? Thanks.

Well, it definitely worked :good:.
Partitions extracted from us998 firmware
. Now I'm flashing again.
Pd: sorry for inverted picture. I make it from cellphone without edition

Do we need any special process before the computer work, @quickwshell and @Pulian? Is any special cable or teardown work needed? I have never used 9008 before but see other brands like xiaomi cannot simply enter 9008 mode directly.
---------- Post added at 04:27 PM ---------- Previous post was at 04:08 PM ----------
Pulian said:
Well, it definitely worked :good:.
Partitions extracted from us998 firmware
. Now I'm flashing again.
Pd: sorry for inverted picture. I make it from cellphone without edition
Click to expand...
Click to collapse
I see octoplus in your pic. Could you please share your tools and detailed steps? I have never tried 9008, so I hope some extra hand-by-hand instructions. Thanks.
The post I read is from an Android community app, and I'm afraid I cannot provide a link to it. And the author of that post said he had not tested yet, just some common sense and rough idea. I'd hear more from you, afterwards you have succeeded.

Thanks again @quickwshell. Firehorse file is the most important think for starting.
1. I extracted files partitions from firmware KDZ using this software https://forum.xda-developers.com/showthread.php?t=2600575
2.. I used testpoint for getting EDL (QUALCOM 9008) connection. https://forum.xda-developers.com/showpost.php?p=78573920&postcount=2
3. I tried firmware posted here without success (Maybe it works on others). So I wrote critical partitions extracted from my specific firmware (US998) using UMT box and I didnt need to create .xml files because this tool can read and detect internal partitions.
4. I got download mode and just write firmware by USB using octoplusbox. Phone Alive!!
I think every step here can be replaced using diferent software. good luck!

nate0 said:
It is a shame we resort to such lengths for this. Shame on vendors. It is like pure gold or diamonds when we come across a programmer...
Click to expand...
Click to collapse
yes,i think so too, lg is too bad on the software

Pulian said:
Thanks again @quickwshell. Firehorse file is the most important think for starting.
1. I extracted files partitions from firmware KDZ using this software https://forum.xda-developers.com/showthread.php?t=2600575
2.. I used testpoint for getting EDL (QUALCOM 9008) connection. https://forum.xda-developers.com/showpost.php?p=78573920&postcount=2
3. I tried firmware posted here without success (Maybe it works on others). So I wrote critical partitions extracted from my specific firmware (US998) using UMT box and I didnt need to create .xml files because this tool can read and detect internal partitions.
4. I got download mode and just write firmware by USB using octoplusbox. Phone Alive!!
I think every step here can be replaced using diferent software. good luck!
Click to expand...
Click to collapse
After getting download mode back, do we need chiperase like @quickwshell mentioned? I don't know if octoplusbox did it before writing firmware and I suppose most people would still use LGUP for firmware writing. Did you lose s/n, imei, etc. after phone booting? If not, I guess partition dl should be OK.

I didnt touch imei and security partitions. My phone worked after flashing without problems.

Pulian said:
Thanks again @quickwshell. Firehorse file is the most important think for starting.
1. I extracted files partitions from firmware KDZ using this software https://forum.xda-developers.com/showthread.php?t=2600575
2.. I used testpoint for getting EDL (QUALCOM 9008) connection. https://forum.xda-developers.com/showpost.php?p=78573920&postcount=2
3. I tried firmware posted here without success (Maybe it works on others). So I wrote critical partitions extracted from my specific firmware (US998) using UMT box and I didnt need to create .xml files because this tool can read and detect internal partitions.
4. I got download mode and just write firmware by USB using octoplusbox. Phone Alive!!
I think every step here can be replaced using diferent software. good luck!
Click to expand...
Click to collapse
I searched a lot for UMT Box and it seems like one has to collect it with the dongle or else it's not gonna work. Getting frustrated here Are there any way other than umt? Can you or anyone suggest?

moyedchowdhury said:
I searched a lot for UMT Box and it seems like one has to collect it with the dongle or else it's not gonna work. Getting frustrated here Are there any way other than umt? Can you or anyone suggest?
Click to expand...
Click to collapse
use cracked miracle box

seloka180 said:
use cracked miracle box
Click to expand...
Click to collapse
THANKS FOR COMING BACK. Mine is a LS998 converted into US998.
I'm So disappointed right now. Past few days have been unbearable. Even my Blood pressure is getting high
I'll describe what happened so that the situation is understood and you could suggest accordingly.
*I unlocked bootloader by wtf method.
*Tried several roms.
*Decided to stay on LOS 17.1 Q [Nearly got f*****g everything]
*Flushed a module via magisk which offered pixel boot animation(actually was searching for smartpixel to turn off 50% pixels)
*Rebooted and the device stuck into bootloop
*Rebooted into fastboot mode and reinstalled twrp and reboot- No luck
*Used a guide to wipe different partitions via fastboot and then reinstall twrp. Success but still boot stuck.
*Tried to go into download mode by pressing volume up while connecting USB, went into the mode but "waiting for any connection..." showed and was not detected by device mgr.
*Thought relocking the bootloader might get me into download mode.(That's when I burnt my luck I guess...)
*Did lock the bootloader.
*Aaaand still not detected in device manager.
*Moreover, now showing that Your device has failed a routine security check and will not boot!
{
"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"
}
*Opened the back and test pointed motherboard, detected in 9008 mode
*Tried QFIL with V30_Unbrick.zip, sahara error.
*Tried a bunch of other tools most of them were so old that they didn't even have the firehose for this model.
Please someone help.

seloka180 said:
use cracked miracle box
Click to expand...
Click to collapse
Can't thank you enough mate! Used it and miracle did happen. I even tried to use it before but after you said it, I tried hard this time. Searched here and there, then took some risk and started to do things like this way -
I had V30_UNBRICK.zip unzipped in a folder with firehose and xml files.
*Disable defender or any other antivirus. (Normally not recommended, but it's the first thing I do when doing these things, also I have an extra laptop where I do all these which doesn't have any private or necessary files, never had any problem though).
*Also, disable driver signature enforcement on Windows(https://windowsreport.com/driver-signature-enforcement-windows-10/)
1. I searched and found Miracle box Thunder v2.93 with loader (No box needed)
2. Select Qualcomm, then flashing and Write Flash.
3. Untick the auto button beside firehose.
4. Under "write flash"
see this image
i. Select firehose, this doesn't recognize the .elf file so renamed it to .mbn (finger was crossed) and it worked!
ii. There are six rawprogram?.xml and patch?.xml (Here, ? = 1, 2, 3....6), I only used rawprogram0.xml and
iii. patch0.xml
5. Got everything ready and then detached the phone from cable.
6. Pressed the start button right after entering into Testpoint EDL Mode. The process starts and failed after a while due to missing files. Then I matched which files were present corresponding to the lines in the xml file, after that deleted all the extra lines(i. e. file was not present in the V30_UNBRICK.zip) from rawprogram0.xml and saved the file (patch0.xml was untouched). I used Notepad++ for editing.
7. Again detached the phone, detached battery, reattached battery, pressed the start button right after I shorted the edl test points, even before the device was detected in the device manager, no delay.
8. The process was completed, files flashed. These files were flashed so that we can now flash proper kdz with download mode. Do not turn on the phone. Or else you'll get into bootloop.
9. Detached the battery, shorted power button for a while(skip if you don't understand), reattached the battery.
10. Pressed volume up and inserted USB cable. Not detected first time. Detached and reattached with pressing volume up button hard this time.
11. witnessed one of the happiest moment seeing it was detected as an LG device in device manager. Wasn't 100% sure yet.
12. Flashed chiperase(important) with patched LGUP in dev mode. And it was done.
13. I will upload the XML file, you can use it with the existing files inside V30_UNBRICK.zip.
the xml file here
Before doing all that I spent five horrific days searching for a solution and almost ordered a motherboard from Aliexpress with a price tag of $100. I tried to be as elaborative as possible so that whoever next encounter the issue don't have to go through what I experienced past few days. If you're reading this and having a problem understanding anything, read again, repeat 10 times, then repeat more 10 times(worked for me), still no solution? knock me here (also: [email protected]). I could help you(with v 30, g6) remotely if I have time, no charges, donate if you will and if you don't I'll still be happy to help. Keep flashing, peace.
---------- Post added at 05:36 AM ---------- Previous post was at 04:57 AM ----------
quickwshell said:
If you try this method, I nor anybody else is responsible for any further damage done to your phone.
Models Confirmed : V300L
We currently have firehose for V30.
Therefore, we can program UFS flash memory in 9008 mode.
It requires rawprogram?.xml(s) and patch?.xml(s) to program it.
It's easy to generate rawprogram?.xml(s) from kdz file, but generate patch?.xml(s) is not easy. (Unfortunately, I couldn't have time to generate patch?.xml(s)).
I have edited kdztools to generate rawprogram?.xml(s) easily (You can generate it by using "-r" argument. Currently, generate patch?.xml(s) is not supported. I'll add it soon).
I used patch?.xml(s) in post. it works well, but boot loop in the LG Logo.
However, it was possible to enter download mode.
------------------- GUIDE -------------------​1. Download rawprogram?.xml patch?.xml with images from link. (It uses V300L30h000906.kdz)
2. Download firehose (prog_ufs_firehose_8998_lgev30.elf) from link.
<< Linux >>
3. Build qdl or download pre-built binary
4. Extract zip or tar.gz files 1, 2, 3 in any folder.
5. Run
Code:
$ ./qdl --storage ufs prog_ufs_firehose_8998_lgev30.elf rawprogram0.xml patch0.xml rawprogram1.xml patch1.xml rawprogram2.xml patch2.xml rawprogram3.xml patch3.xml rawprogram4.xml patch4.xml rawprogram5.xml patch5.xml rawprogram6.xml patch6.xml
in the terminal.
6. If LG logo shows, enter to the download mode.
<< Windows >>
3-6. You can program by QFIL similar as qdl.
7. Connect to any Windows PC with LGUP (must support Android Pie).
8. Flash kdz with ChipErase. (IMPORTANT)
9. If it boots successfully, your device has unbricked.
Click to expand...
Click to collapse
Thank you, Your post helped me to understand a lot of things. Without whome I'd be having an expensive brick which can't even be used to build anything.
This is the way I recovered. So posting it here for people might get help.
seloka180 said:
use cracked miracle box
Click to expand...
Click to collapse
Can't thank you enough mate! Used it and miracle did happen. I even tried to use it before but after you said it, I tried hard this time. Searched here and there, then took some risk and started to do things like this way -
I had V30_UNBRICK.zip unzipped in a folder with firehose and xml files.
*Disable defender or any other antivirus. (Normally not recommended, but it's the first thing I do when doing these things, also I have an extra laptop where I do all these which doesn't have any private or necessary files, but never had any problems).
*Also, disable driver signature enforcement on Windows(https://windowsreport.com/driver-sig...nt-windows-10/)
1. I searched and found Miracle box Thunder v2.93 with loader (No box needed)
2. Select Qualcomm, then flashing and Write Flash.
3. Untick the auto button beside firehose.
4. Under "write flash"
see this image
i. Select firehose, this doesn't recognize the .elf file so renamed it to .mbn (finger was crossed) and it worked!
ii. There are six rawprogram?.xml and patch?.xml (Here, ? = 1, 2, 3....6), I only used rawprogram0.xml and
iii. patch0.xml
5. Got everything ready and then detached the phone from cable.
6. Pressed the start button right after entering into Testpoint EDL Mode. The process starts and failed after a while due to missing files. Then I matched which files were present corresponding to the lines in the xml file, after that deleted all the extra lines(i. e. file was not present in the V30_UNBRICK.zip) from rawprogram0.xml and saved the file (patch0.xml was untouched). I used Notepad++ for editing.
7. Again detached the phone, detached battery, reattached battery, pressed the start button right after I shorted the edl test points, even before the device was detected in the device manager, no delay.
8. The process was completed, files flashed. These files were flashed so that we can now flash proper kdz with download mode.
9. Detached the battery, shorted power button for a while(skip if you don't understand), reattached the battery.
10. Pressed volume up and inserted USB cable. Not detected first time. Detached and reattached with pressing volume button hard this time.
11. witnessed one of the happiest moment seeing it was detected as an LG device in device manager. Wasn't 100% sure yet.
12. Flashed chiperase(important) with patched LGUP in dev mode. And it was done.
13. I will upload the XML file, you can use it with the existing files inside V30_UNBRICK.zip.
the xml file here
Before doing all that I spent five horrific days searching for a solution and almost ordered a motherboard from Aliexpress with a price tag of $100. I tried to be as elaborative as possible so that whoever next encounter the issue don't have to go through what I experienced past few days. If you're reading this and having a problem understanding anything, read again, repeat 10 times, then repeat more 10 times(worked for me). Keep flashing, peace.

Related

[GUIDE] How to UNBRICK your Optimus G - security error, bootloop etc

For whatever reasons (improper rooting/flashing, power outage during updating, freezing/removal of LG bloatwares or simple bad luck etc), if you bricked your Optimus G and is stuck with a Security Error or in a bootloop, fear not, as long as you can put it into Download and Recovery Mode, all is not lost.
I got the korean version of the (almost) Optimus G (Optimus LTE2, f160k) and ran into the same security error problem that happened out of the blue.
The steps that I undertook below resolved the problem for me and has been proven to work on Optimus G by fellow members.
http://forum.xda-developers.com/showpost.php?p=34516791&postcount=29
1) Download the latest KDZ from LG's server for your phone via the app below (kudos to the creator)
http://www.mediafire.com/?cgeb6o5osy2yl9c
2) Make sure you have LG United Drivers already installed, otherwise download from below
http://www.mediafire.com/?82nt1aeh04aqa3m
3) Download LG KDZ Updater
http://www.mediafire.com/?sj5y073xal03ntw
4) Download the manual adb wipe batch file
http://www.mediafire.com/?ru7erfxsz7p7s3p
5) Put your Optimus G into Download Mode by switching it off, attaching the usb cable to the phone, holding both the up and down volume buttons at the same time and lastly inserting the usb cable into the computer; wait for the drivers to finish loading if doing it for the first time.
6) Unzip the downloaded updater zip file and run KDZ_FW_UPD.exe. Use the settings below
Type: 3GQCT
Phone Mode: CS_Emergency
KDZ file: navigate to the folder which you have saved the downloaded KDZ from the step (1)
Click Launch Software Update and wait for the flash process to finish
7) Your phone will restart itself when IParam = 90 is displayed and proceed slower until you see IParam=1 again (which signals the end of flash, you can safely exit the program then and remove the cable from the phone). If phone boots up normally, congrats, skip the steps below and proceed to use the phone as per normal.
However, this most probably will not be the case for newer Optimus-es, as the data partition somehow wasn't wiped even when KDZ-ed, remaining 'dirty', thus causing bootloop or security infringement.
8) If the phone is stuck at the booting up LG/Telco logo, you will need to manually wipe the data partition.
9) Force the phone off by holding the power button for appx 15secs.
10) Put the phone into recovery mode by holding the volume up and home button concurrently, then press the power button. Let go of all the buttons after you see the LG logo on screen for the 2nd time and the screen goes blank thereafter (backlight may still be on). The phone will kind of reboot and then enters recovery mode. Repeat the process if you did not get it the first time.
11) With the phone in Recovery Mode, connect it to the computer, wait for the drivers to load (if doing it for the first time), unzip the wipe batch file downloaded earlier from step (4), double click on wipe.bat to execute the wipe command.
12) Your phone will auto reboot when wiped and (hopefully) boot as per normal.
Hope with this simple guide fellow members will feel safer when rooting or removing non essential LG wares from their Optimus G.
Tried this, however the phone get stuck on a bootloop. It's stuck on bootanimation. I also tried to clear data with the adb wipe files but i end up with a phone stuck on that
{
"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"
}
image.
Bell E973
I have E973 from Bell and it's been bricked since sunday after renaming couple of system apps.
I am trying to follow the instruction above but i can't download KDZ file with LG firmware downloader bc it just would not take my SN.
Error msg is "unsuccessful in connecting to server orphone infomations is wrong!"
Could anyone upload KDZ file for Bell E973 somewhere on the net that i can download?
It would be much appreciated..
razrgalaxy said:
I have E973 from Bell and it's been bricked since sunday after renaming couple of system apps.
I am trying to follow the instruction above but i can't download KDZ file with LG firmware downloader bc it just would not take my SN.
Error msg is "unsuccessful in connecting to server orphone infomations is wrong!"
Could anyone upload KDZ file for Bell E973 somewhere on the net that i can download?
It would be much appreciated..
Click to expand...
Click to collapse
Go here, replacing <yourimei> with your actual imei (just numbers, nothing else), it'll spit out a bunch of text including an address with the kdz.
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=<yourimei>
Thanks thracky for quick response.
but it is just stck at blank window..
---------- Post added at 10:55 AM ---------- Previous post was at 10:17 AM ----------
razrgalaxy said:
Thanks thracky for quick response.
but it is just stck at blank window..
Click to expand...
Click to collapse
Tried it on Chrome but no address with KDZ.
razrgalaxy said:
Thanks thracky for quick response.
but it is just stck at blank window..
---------- Post added at 10:55 AM ---------- Previous post was at 10:17 AM ----------
Tried it on Chrome but no address with KDZ.
Click to expand...
Click to collapse
Don't include the <> characters with your imei, I just put those there to mark where the IMEI goes
Also, your IMEI should be 15 digits, and I've only used this on my computer, so I'm not sure if it works on mobile browser or not, and if that's how you're trying it.
razrgalaxy said:
I have E973 from Bell and it's been bricked since sunday after renaming couple of system apps.
I am trying to follow the instruction above but i can't download KDZ file with LG firmware downloader bc it just would not take my SN.
Error msg is "unsuccessful in connecting to server orphone infomations is wrong!"
Could anyone upload KDZ file for Bell E973 somewhere on the net that i can download?
It would be much appreciated..
Click to expand...
Click to collapse
2nd thracky's view.
would recommend u do it on the PC, use the app, enter your model E973, enter your imei (15 digits, usually means omitting the the last 0 or digit), shd be able to download your KDZ.
chadouming said:
Tried this, however the phone get stuck on a bootloop. It's stuck on bootanimation. I also tried to clear data with the adb wipe files but i end up with a phone stuck on that .
Click to expand...
Click to collapse
did u wipe in recovery mode?
can you put your phone into download mode again?
if yes, try the whole process again?
as long as your phone can still enter download mode, all is not lost, even if this method does not work,
good luck!
potatohead said:
did u wipe in recovery mode?
can you put your phone into download mode again?
if yes, try the whole process again?
as long as your phone can still enter download mode, all is not lost, even if this method does not work,
good luck!
Click to expand...
Click to collapse
He couldn't get into recovery at all, that image he posted was what happened going into recovery.
I think he mangled his partition table, and I feel like KDZ wouldn't necessarily repartition everything based on my experience with tools for other phones like Odin for Samsung phones, where you explicitly have to tell it to repartition and give it a file to dictate the layout.
thracky said:
He couldn't get into recovery at all, that image he posted was what happened going into recovery.
I think he mangled his partition table, and I feel like KDZ wouldn't necessarily repartition everything based on my experience with tools for other phones like Odin for Samsung phones, where you explicitly have to tell it to repartition and give it a file to dictate the layout.
Click to expand...
Click to collapse
learned something new, thanks
KDZ-ing of LG's phones of late seem to be not as 'thorough' as previous, it used to be the be all and end all; or maybe i didnt mangle my phone bad enough
has he tried upgrading via LG's update tool instead?
he may need to KDZ an older version first (if available) so LG tool can sense an upgrade is necessary, and hopefully, it is intelligent enough to repartition if one is necessary.
also, LG's update tool has in-built recovery/repair option, not sure how that works though, worth to explore?
potatohead said:
learned something new, thanks
KDZ-ing of LG's phones of late seem to be not as 'thorough' as previous, it used to be the be all and end all; or maybe i didnt mangle my phone bad enough
has he tried upgrading via LG's update tool instead?
he may need to KDZ an older version first (if available) so LG tool can sense an upgrade is necessary, and hopefully, it is intelligent enough to repartition if one is necessary.
also, LG's update tool has in-built recovery/repair option, not sure how that works though, worth to explore?
Click to expand...
Click to collapse
Yep update tool was tried, recovery wouldn't work either. He wound up exchanging the phone anyways
I could not find the KDZ file
wish to know if there are any other ways to get the kdz?
I've asked some L-01E onwers, they replied that normal ways do not work japan version
look for help THX
ssfirme said:
I could not find the KDZ file
Click to expand...
Click to collapse
Can you give me your IMEI, I'll paste link download for you
keeping getting "upgrade error wparam 100 lparam 72"
Question for Sprint
potatohead said:
6) Unzip the downloaded updater zip file and run KDZ_FW_UPD.exe. Use the settings below
Type: 3GQCT
Phone Mode: CS_Emergency
KDZ file: navigate to the folder which you have saved the downloaded KDZ from the step (1)
Click to expand...
Click to collapse
Question, on the Sprint version of this phone, would the type be CDMA?
Also, do you think anything else would be different?
*edit* Also, when I try to download the KDZ file, it is instead a .CAB file that has an .wdb, .wdh, and a .dll file inside.
Am I supposed to rename it? convert it?
Thanks!
I can not get it to download the KDZ file either. Is there anyway to post a link for a direct download?
trusteelfan said:
I can not get it to download the KDZ file either. Is there anyway to post a link for a direct download?
Click to expand...
Click to collapse
This should not be used for the Sprint or AT&T variants, please see instructions for restoring with LGNPST in the respective forums as we have .tot files for both AT&T and Sprint.
thracky said:
This should not be used for the Sprint or AT&T variants, please see instructions for restoring with LGNPST in the respective forums as we have .tot files for both AT&T and Sprint.
Click to expand...
Click to collapse
Thank you. I have seen that but I do not know how to flash the TOT file. I have downloaded that, but do not know how to flash it.
I wouldn't work for me until I added 1 more step
First of all, thanks again to the poster and xda in general...y'all freakin rule.
I couldn't get this to work for the longest time, though I knew that these valuable instructions were the key to fixing my device.
The difference between total failure and absolute success for me was making sure to run "msxml.msi" in the KDZ updater before running "KDZ_FW_UPD.exe"
If you're stuck, try that!!!
Thanks once again for helping me fix my device!

LG K10 LGM250n rooting

Starting this thread for i've found no viable method for rooting, custom ROMs, etc. for the 2017 european model of K10 ( which actually is supplied carrier unlocked in my country with ROM version LGM250AT-00-V12q-COM-DEC-18-2017+0 at this moment, )
First of all, there is *no way* to get into bootloader mode, by ADB or key combo at startup, tried everything suggested on forums , docs pages, whatnot. To be honest, the Internet is full of crap, there should be some censoring, or whoever isn't really fit to publish information or methods they don't master, simply refrain themselves from doing so.
What i have: actually managed to capture the original ROM file, M250n10n_00_OPEN_EU_OP_1218.kdz from the LG Updater tool , can be downloaded from below link. 7zipped for minimal size and password protected the archive, the password is 12345678, for just in case
h.t.t.p.s:././ drive.google.com/file/d/1_uYKC1ecAOvhqyqSr3h2-XSTWvZfHOWn/view?usp=sharing
Apparently, the .kdz file can be successfully unpacked with WindowsLGFirmwareExtract-1.2.6.1 , the boot image extracted from the .dz file, etc. At this point, my knowledge on this is exhausted , haven't done any phone hacking in the last 10 years, last and only time was an Alcatel OTC 960 (i think), with Android 2, don't remember squat now. Don't exactly have time for research and tinkering too much either, i'd rather pass over to someone with more up to date knowledge and experience.
The phone hardware is quite powerful for it's price class, 8 core CPU of which the high perf cluster (4 cores) runs on 1.5 GHz, the low power cluster on 1 GHz, 2 GB DDR2 RAM @667 MHz, 16 GB flash , a decent GPU , generic connectivity options, sd card support, overall a good phone for day by day use.
Full of bloatware though, dire need of rooting, cleanup and some advanced tweaking possibility ( which obviously requires rooting).
Booting into native recovery mode
.. it does work, to some extent. Method:
- connect to ADB make sure all debug stuff, oem unlock etc. is set
- issue command 'adb reboot recovery' command, phone will reboot into recovery mode, with a burnt out android dummy on screen
- press Power + Volume UP simultaneously for a second, the recovery menu will show up
The recovery menu offers a fair few options: reboot to bootloader, format, install update from fota partition or sdcard, mount /system or normal reboot. The reboot to bootloader option doesn't work, it will force a normal reboot. Interesting the manufacturer left this option at all, while non functional. or better, there must be some hidden option to be set which will actually unlock the bootloader, but it's definitely not the "enable OEM unlock" from the developer menu nor from the r&d diagnostic hidden menu.
The option to install an update in recovery mode, from sd card sounds promising though. I wonder if somebody has any experience with that, if so, please share it here.
Wipe recovery partition first, then go into recovery..its look like freeze coz recovery partition now empty but this is the way for fastboot
ElRongMcBong said:
Wipe recovery partition first, then go into recovery..its look like freeze coz recovery partition now empty but this is the way for fastboot
Click to expand...
Click to collapse
then, how can we wipe recovery partition?
we're going in circles. no root, no wipe. but for root, need unlocked bootloader. and the default bootloader doesn't allow fastboot/rooting, etc. so it's a stall. please guys, if you have any ***working*** method, post only that.
So far, i have a working method to downgrade the firmware:
- install LG UP
- extract the "LGUP_c.dll" file from the firmware using WindowsLGFirmwareExtract-1.2.6.1-Release
- download and run Uppercut, it likely will detect the phone, keep it open then go to the LG UP installation directory c:\Program Files (x86)\LG Electronics\LGUP\model\ , duplicate the "common" folder ( or it'll vanish when Uppercut is closed)
- close Uppercut, it's useless, rename back the duplicate "common" folder, place the extracted "LGUPc.dll", rename it literally to "LGUP_common.dll" ; obviously, will need to delete the one from teh folder, that's garbage by Uppercut. Keep "WPDAPI.exe", it's needed.
- run LG UP , choose the .kdz file, both Upgrade and FOTA Upgrade work ( this last one flashes the /fota partition). Refurbish doesn't work, and no idea what it does, so far
- let LG UP do it's thing, at 100% upload , the phone will restart, then a white background shows with the upgrading message, etc. and a progress bar , the phone will either restart at 97 % of the progress bar, or go directly into normal OS load, then within the OS will see the upgrading continues for a few seconds, etc. It depends on the firmware version.
And here comes my problem. None of the available firmwares have the bootloader unlockable. The oldest, M250n10g_00_OPEN_EU_OP_0420.kdz is still from April, dated 3 months after the original release.
We need some of the very first firmwares, if indeed the claim by pvineeth97 is true that he could root it and install TWRP recovery. To be honest, the guy seems to be a hack, probably copy - pasted the method from the older K10 model, and he actually has no proof for having a working method for the 2017 model. Also, doesn't answer to private messages, so that's that... I saw a lot of "methods" by googling, everybody just adds the M250N model to the list, claims rooting works, etc. IT IS NOT TRUE, these are all false claims, just some idiots looking for cheap popularity, taking credit for some other peoples' work, and so on...
I can put the tools onto my gdrive and share the link, if someone else wants to try, but so far, we're short on a proper firmware image.
Try using the scatter file for MT6750.
adacsaba said:
So far, i have a working method to downgrade the firmware:
- install LG UP
- extract the "LGUP_c.dll" file from the firmware using WindowsLGFirmwareExtract-1.2.6.1-Release
- download and run Uppercut, it likely will detect the phone, keep it open then go to the LG UP installation directory c:\Program Files (x86)\LG Electronics\LGUP\model\ , duplicate the "common" folder ( or it'll vanish when Uppercut is closed)
- close Uppercut, it's useless, rename back the duplicate "common" folder, place the extracted "LGUPc.dll", rename it literally to "LGUP_common.dll" ; obviously, will need to delete the one from teh folder, that's garbage by Uppercut. Keep "WPDAPI.exe", it's needed.
- run LG UP , choose the .kdz file, both Upgrade and FOTA Upgrade work ( this last one flashes the /fota partition). Refurbish doesn't work, and no idea what it does, so far
- let LG UP do it's thing, at 100% upload , the phone will restart, then a white background shows with the upgrading message, etc. and a progress bar , the phone will either restart at 97 % of the progress bar, or go directly into normal OS load, then within the OS will see the upgrading continues for a few seconds, etc. It depends on the firmware version.
And here comes my problem. None of the available firmwares have the bootloader unlockable. The oldest, M250n10g_00_OPEN_EU_OP_0420.kdz is still from April, dated 3 months after the original release.
We need some of the very first firmwares, if indeed the claim by pvineeth97 is true that he could root it and install TWRP recovery. To be honest, the guy seems to be a hack, probably copy - pasted the method from the older K10 model, and he actually has no proof for having a working method for the 2017 model. Also, doesn't answer to private messages, so that's that... I saw a lot of "methods" by googling, everybody just adds the M250N model to the list, claims rooting works, etc. IT IS NOT TRUE, these are all false claims, just some idiots looking for cheap popularity, taking credit for some other peoples' work, and so on...
I can put the tools onto my gdrive and share the link, if someone else wants to try, but so far, we're short on a proper firmware image.
Click to expand...
Click to collapse
You are true, @adacsaba but try the scatter file method unique to MTK. I hope that works.
adacsaba said:
Starting this thread for i've found no viable method for rooting, custom ROMs, etc. for the 2017 european model of K10 ( which actually is supplied carrier unlocked in my country with ROM version LGM250AT-00-V12q-COM-DEC-18-2017+0 at this moment, )
First of all, there is *no way* to get into bootloader mode, by ADB or key combo at startup, tried everything suggested on forums , docs pages, whatnot. To be honest, the Internet is full of crap, there should be some censoring, or whoever isn't really fit to publish information or methods they don't master, simply refrain themselves from doing so.
What i have: actually managed to capture the original ROM file, M250n10n_00_OPEN_EU_OP_1218.kdz from the LG Updater tool , can be downloaded from below link. 7zipped for minimal size and password protected the archive, the password is 12345678, for just in case
h.t.t.p.s:././ drive.google.com/file/d/1_uYKC1ecAOvhqyqSr3h2-XSTWvZfHOWn/view?usp=sharing
Apparently, the .kdz file can be successfully unpacked with WindowsLGFirmwareExtract-1.2.6.1 , the boot image extracted from the .dz file, etc. At this point, my knowledge on this is exhausted , haven't done any phone hacking in the last 10 years, last and only time was an Alcatel OTC 960 (i think), with Android 2, don't remember squat now. Don't exactly have time for research and tinkering too much either, i'd rather pass over to someone with more up to date knowledge and experience.
The phone hardware is quite powerful for it's price class, 8 core CPU of which the high perf cluster (4 cores) runs on 1.5 GHz, the low power cluster on 1 GHz, 2 GB DDR2 RAM @667 MHz, 16 GB flash , a decent GPU , generic connectivity options, sd card support, overall a good phone for day by day use.
Full of bloatware though, dire need of rooting, cleanup and some advanced tweaking possibility ( which obviously requires rooting).
Click to expand...
Click to collapse
Hi,
You have helped me to get rid of bloatware ) thank you so much I was trying to install new firmware all day. Now I have clean phone.
adacsaba said:
we're going in circles. no root, no wipe. but for root, need unlocked bootloader. and the default bootloader doesn't allow fastboot/rooting, etc. so it's a stall. please guys, if you have any ***working*** method, post only that.
Click to expand...
Click to collapse
No friend, By what I read here in the forum, it is not necessary to unlock the bootloader in this template
Someone checked this secret menu * # 546368 # * 250 #? has several options that I did not check for lack of experience anyone any solution to open the fastboot or unlock the bootloader
{
"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"
}
---------- Post added at 06:53 AM ---------- Previous post was at 06:49 AM ----------
*#546368#*250# code
you can test your phone without problems...
Still no solution for root or how to make this phone google free :crying:
whitearmor said:
Hi,
You have helped me to get rid of bloatware ) thank you so much I was trying to install new firmware all day. Now I have clean phone.
Click to expand...
Click to collapse
Hello! How did you do it? could you explain? It would be good since you can not even root this team, because at least remove the bloatware from the system, recovering the space of the applications that still exist in the private folder on the same system.
I have a LG Tribute Empire (LM-X220PM). It is also based on the MTK 6750, my device seems to be on running 32-Bit instead of 64-Bit though.
I cannot enter fastboot mode either. I have all of these problems as mentioned in the OP. I was going to start a thread until I saw this. Does deleting the recovery partition really allow the device to boot into fastboot mode?
Because I was about to start looking into lglaf, the advanced flash functions might be a solid connect on a mediatek system. Because Mediatek Devices are normally unlockable. I just need to find my own device's firmware so I can look at the system and ramdisk. Everything about the phone screams there can be root. Maybe a system root though. I need to find the Dev Patched LG UP though to flash partitions. And read how to give LG Advanced Flash commands.
Delgoth said:
Does deleting the recovery partition really allow the device to boot into fastboot mode?
Click to expand...
Click to collapse
Nope. You can wipe it but then it boots to the system which rebuilds recovery from the boot.
I have though about wiping the boot too, to see how it reacts, but there might be some catch.
Also the lgup hasn't been always so steady recognizing my device, m250n.
Also the LG's Bridge has sometimes recognized it to some totally different device.
Odd, but so far I've used it through virtualbox, which might have something do with it.
Delgoth said:
Because I was about to start looking into lglaf, the advanced flash functions might be a solid connect on a mediatek system. Because Mediatek Devices are normally unlockable. I just need to find my own device's firmware so I can look at the system and ramdisk. Everything about the phone screams there can be root. Maybe a system root though. I need to find the Dev Patched LG UP though to flash partitions. And read how to give LG Advanced Flash commands.
Click to expand...
Click to collapse
LG has done their best to remove MTK stuff from m250n, don't know about your device...
CXZa said:
Nope. You can wipe it but then it boots to the system which rebuilds recovery from the boot.
I have though about wiping the boot too, to see how it reacts, but there might be some catch.
Also the lgup hasn't been always so steady recognizing my device, m250n.
Also the LG's Bridge has sometimes recognized it to some totally different device.
Odd, but so far I've used it through virtualbox, which might have something do with it.
LG has done their best to remove MTK stuff from m250n, don't know about your device...
Click to expand...
Click to collapse
Sounds like I need to figure out how to customize the flasher to my device then is all. LGUP 1.4 didn't recognize my device at all.
Delgoth said:
Sounds like I need to figure out how to customize the flasher to my device then is all. LGUP 1.4 didn't recognize my device at all.
Click to expand...
Click to collapse
You might need to use your devices own dll which is inside the kdz file.
---> [LG TOOL] KDZ dll extractor
CXZa said:
You might need to use your devices own dll which is inside the kdz file.
---> [LG TOOL] KDZ dll extractor
Click to expand...
Click to collapse
Or maybe these help, IDK... you probably have found them too...
https://www.mylgphones.com/lgup-dll-for-sprint-lg-tribute-empire.html
https://www.mylgphones.com/how-to-dump-backup-lg-tribute-empire-lmx220pm-firmware.html
CXZa said:
You might need to use your devices own dll which is inside the kdz file.
---> [LG TOOL] KDZ dll extractor
Click to expand...
Click to collapse
I've seen that a lot of LG information is spread around. I normally have Samsung Devices I work with. So the whole flashing process is different. Different Tools, different build types.
Really I'm still trying to wrap my around the LG process. There seems to be many different ways to do things but are kind of device specific. I've only just recently learned about the patched LGUP but I can't find my firmware anywhere to get started with it and get it patched. So I'll look around to hopefully find a KDZ somewhere for the x220pm.
lol I feel like a newb again just because I switched OEM's.

10+ eXYNOS BOOTLOADER REMOVED

First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing
link is restricted
Bro. Share file pls on your googledrive. We cantdownload it
Flar4eg said:
Bro. Share file pls on your googledrive. We cantdownload it
Click to expand...
Click to collapse
Excuse me, is that I uploaded the files to my google drive cloud and I detect a dll, or part of the flashtool as a virus, now I upload it again and put the link
https://mega.nz/file/eWRkiCwI#XP0yMOiBsfkUKIoxhKaZkLIgdhkwnEtiyVHqixMu8NI
multiuploader error: WinDNWApi.dll file could not be found.
Skyfall191299 said:
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Click to expand...
Click to collapse
can anybody please explain how to make these files I have my Sboot.bin which was in the phone, I don't understand how to use hex editor. can some plz assist me, working on a750g. broke bootloader by flashing wrong firmware a750f after MDM bypass. software ver U1ARL3 for sboot
here is my sboot, can someone please create or show me how to create with hex https://drive.google.com/file/d/1CcEqe4MH__APK7H42aP3H2KGdqkAi-xx/view?usp=sharing
Skyfall191299 said:
https://mega.nz/file/eWRkiCwI#XP0yMOiBsfkUKIoxhKaZkLIgdhkwnEtiyVHqixMu8NI
Click to expand...
Click to collapse
getting error that el3mon_dram not found. can you help me?
Hello someone has the files ? The download link is inactive
The download link is inactive, please active or reupload please.
Skyfall191299 said:
First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing
Click to expand...
Click to collapse
good jod
im follwed to this instruction but all links not woriking
pla give me ur telegram or whtas app
and upload files to the new link plz
eldon301 said:
can anybody please explain how to make these files I have my Sboot.bin which was in the phone, I don't understand how to use hex editor. can some plz assist me, working on a750g. broke bootloader by flashing wrong firmware a750f after MDM bypass. software ver U1ARL3 for sboot
here is my sboot, can someone please create or show me how to create with hex https://drive.google.com/file/d/1CcEqe4MH__APK7H42aP3H2KGdqkAi-xx/view?usp=sharing
Click to expand...
Click to collapse
how to create with hex bro ?
links not woriking
link isn't working please fix
akbarshoxdedamirzayev said:
how to create with hex bro ?
Click to expand...
Click to collapse
Find the exact firmware that’s currently in the device, extract sboot from the firmware. You need to find correct location of bl1 bl2 el3 and others, names correspond to which is cut. You need 5 files from sboot. Am stuck on the forth file failing and I still don’t understand how to find them. What I did was follow others with exactly the same problem to see and understand how they got there’s and then tried it on my sboot. I am failing on part4 don’t even know how to make a cfg but from what I understand e for exynos and the number after so mine is e7885. Still not sure like I said
http://www.mediafire.com/file/sg5m2ti3k6a63z5/USB_Down_Load_32bit.zip/file download link
Skyfall191299 said:
First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing
Click to expand...
Click to collapse
Can you check the addresses and lenghts of the partitions cut out of sboot?
I think you've made a mistake.
Can give me the precise partition details?
Are you 100% positive that this is valid at least for most devices of the same chipset?
I'd like to try to make an automated script or a tool of some sort.
Also when I was dividing my A515F U5 sboot I've spotted some long breaks in data which I assumed were empty blocks at the end of partitions.
What confused me about it is that I didn't find those where you said partitions are ending.
Can you demonstrate graphically your partitions in a linear projection?
It’s been 3 years and still can’t get help with A750G hard brick. I guess XDA is not so friendly and helpful anymore.
The world is slowly dying. Peace to everyone who still cares
eldon301 said:
It’s been 3 years and still can’t get help with A750G hard brick. I guess XDA is not so friendly and helpful anymore.
The world is slowly dying. Peace to everyone who still cares
Click to expand...
Click to collapse
I'd like to help
NonStickAtom785 said:
I'd like to help
Click to expand...
Click to collapse
Hello my friend I am try to get life back into a A750G, it’s completely hard bricked showing exynos usb in device manager. Can i direct message you or should I keep it in the forums. I was falling on part 4 off the files needed to create, I didn’t even know if my cfg file was correct but I tried my best at understanding the creation of the files. Plz help my brothers

How To Guide Backup full firmware(ROM) of any MediaTek device using MTK client| Oppo reno6 5G | MT6877

Hello Guys,
Many times we encounter a situation where we need to do some software update, flash custom ROM, install stock ROM etc, so it is advisable to take full firmware/ROM backup of your device. If required then you can flash this backup to restore your device.
We will use MTK client Github tool for this backup process and using same tool we can flash the backup firmware.
This method has been tested on OPPO Reno6 5G which is powered by MediaTek MT6877 chip. Backup size was approx 12 GB. Using this method you can backup firmware of any other supported MediaTek chip in this tool. In this method I don't backup userdata because this tool backups entire partition size irrespective of actual data stored.
Step1: Pre-requisite -Installing required drivers and doing setup
Install MediaTek driver.
Install python(during installation of python please select "install for all user" from customization and tick add path to system variable).
install usbdk.
download extarct Mtk client tool.
go to folder where you extract mtk client
View attachment 5541629
open cmd here and run below command
cd mtkclient
pip3 install -r requirements.txt
Windows+10_MTK+VCOM+USB+Preloader+Drivers.zip | by karimovic44 for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Download Python
The official home of the Python Programming Language
www.python.org
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
Releases · daynix/UsbDk
Usb Drivers Development Kit for Windows. Contribute to daynix/UsbDk development by creating an account on GitHub.
github.com
Step2: Create a new folder/directory in your computer to store the backup files.
{
"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"
}
Step3: Run full firmware backup
In cmd run command below, please skip userdata partition only because of very huge size.
python mtk rl --skip userdata "<full path to store the backup files>"
Once all the partitions dumped it will show message "All dumped partitions success"
During backup process it will dump the device preloader, this file is very important so, please keep this file safely. this file may require in future.
Step3: Reboot the phone
Once backup is done, you can restart your phone by pressing vol up and power button together for 30 sec.
Step4: How to Restore (if required)
Backup process might have created approximately 58 files but we do not need to flash all those files.
We only need to flash below files, so create a new folder and copy all these 33 files from original backup to your newly created folder.
audio_dsp.bin
boot.bin
cam_vpu1.bin
cam_vpu2.bin
cam_vpu3.bin
cdt_engineering.bin
dpm_1.bin
dpm_2.bin
dtbo.bin
gpt_backup.bin
gpt_main.bin
gz1.bin
gz2.bin
lk.bin
lk2.bin
logo.bin
mcupm_1.bin
mcupm_2.bin
md1img.bin
oplusreserve2.bin
pi_img.bin
recovery.bin
scp1.bin
scp2.bin
spmfw.bin
sspm_1.bin
sspm_2.bin
super.bin
tee1.bin
tee2.bin
vbmeta.bin
vbmeta_system.bin
vbmeta_vendor.bin
open cmd and type below command
python mtk wl "<full path where 33 files are stored>"
Backup should be restored on same device from which it was taken else device may brick.
Thanks and Regards
Nand,
thanks a lot why only 33 files restored ?
Please please, i have a question. can i use that firmware on oppo reno4 z 5G, has a model CPH2065
if not where i can find one for my device?
please i have oppo reno4 z 5G and model number CPH2065
jason__ said:
Please please, i have a question. can i use that firmware on oppo reno4 z 5G, has a model CPH2065
if not where i can find one for my device?
please i have oppo reno4 z 5G and model number CPH2065
Click to expand...
Click to collapse
No. you can NOT use.
Nand kumar said:
No. you can NOT use.
Click to expand...
Click to collapse
please where can i find fireware for my model. i searched everywhere and i can't find it.
jason__ said:
please where can i find fireware for my model. i searched everywhere and i can't find it.
Click to expand...
Click to collapse
Try this. I think You need to buy unlock tool license to flash the firmware. Search unlock tool.net in google.
https://oppostockrom.com/oppo-reno-4-z-5g-cph2065
Nand kumar said:
Try this. I think You need to buy unlock tool license to flash the firmware. Search unlock tool.net in google.
https://oppostockrom.com/oppo-reno-4-z-5g-cph2065
Click to expand...
Click to collapse
is it country neutral? what does that PU stand for?
i appreciate your time so much for trying to help me out.
jason__ said:
is it country neutral? what does that PU stand for?
i appreciate your time so much for trying to help me out.
Click to expand...
Click to collapse
Firmware size is 8 gb so I think it support all countries. You will get drop down list to select country while flashing. Download and extract and see if it has ofp file
okay sir, i'll get back to you when it's downloaded.
Nand kumar said:
Firmware size is 8 gb so I think it support all countries. You will get drop down list to select country while flashing. Download and extract and see if it has ofp file
Click to expand...
Click to collapse
Sorry for being late sir.
Yeah it has that file. but i installed realme flash, and some drivers were available in the package. then when i try to fastboot my phone (down volume key + power key) i find that my phone is not accessible.
i download every possible driver that i could find online and nothing.
also, when i try to fastboot my phone, i enter recovery mode. are they the same?
Please help me.
jason__ said:
Sorry for being late sir.
Yeah it has that file. but i installed realme flash, and some drivers were available in the package. then when i try to fastboot my phone (down volume key + power key) i find that my phone is not accessible.
i download every possible driver that i could find online and nothing.
also, when i try to fastboot my phone, i enter recovery mode. are they the same?
Please help me.
Click to expand...
Click to collapse
i think you need to enter EDL mode aka download mode and not fastboot for that tool...
Nand kumar said:
Hello Guys,
Many times we encounter a situation where we need to do some software update, flash custom ROM, install stock ROM etc, so it is advisable to take full firmware/ROM backup of your device. If required then you can flash this backup to restore your device.
We will use MTK client Github tool for this backup process and using same tool we can flash the backup firmware.
This method has been tested on OPPO Reno6 5G which is powered by MediaTek MT6877 chip. Backup size was approx 12 GB. Using this method you can backup firmware of any other supported MediaTek chip in this tool. In this method I don't backup userdata because this tool backups entire partition size irrespective of actual data stored.
Step1: Pre-requisite -Installing required drivers and doing setup
Install MediaTek driver.
Install python(during installation of python please select "install for all user" from customization and tick add path to system variable).
install usbdk.
download extarct Mtk client tool.
go to folder where you extract mtk client
View attachment 5541629
open cmd here and run below command
cd mtkclient
pip3 install -r requirements.txt
Windows+10_MTK+VCOM+USB+Preloader+Drivers.zip | by karimovic44 for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Download Python
The official home of the Python Programming Language
www.python.org
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
Releases · daynix/UsbDk
Usb Drivers Development Kit for Windows. Contribute to daynix/UsbDk development by creating an account on GitHub.
github.com
Step2: Create a new folder/directory in your computer to store the backup files.
View attachment 5543511
Step3: Run full firmware backup
In cmd run command below, please skip userdata partition only because of very huge size.
python mtk rl --skip userdata "<full path to store the backup files>"
View attachment 5543497
View attachment 5543501
Once all the partitions dumped it will show message "All dumped partitions success"
During backup process it will dump the device preloader, this file is very important so, please keep this file safely. this file may require in future.
Step3: Reboot the phone
Once backup is done, you can restart your phone by pressing vol up and power button together for 30 sec.
Step4: How to Restore (if required)
Backup process might have created approximately 58 files but we do not need to flash all those files.
We only need to flash below files, so create a new folder and copy all these 33 files from original backup to your newly created folder.
audio_dsp.bin
boot.bin
cam_vpu1.bin
cam_vpu2.bin
cam_vpu3.bin
cdt_engineering.bin
dpm_1.bin
dpm_2.bin
dtbo.bin
gpt_backup.bin
gpt_main.bin
gz1.bin
gz2.bin
lk.bin
lk2.bin
logo.bin
mcupm_1.bin
mcupm_2.bin
md1img.bin
oplusreserve2.bin
pi_img.bin
recovery.bin
scp1.bin
scp2.bin
spmfw.bin
sspm_1.bin
sspm_2.bin
super.bin
tee1.bin
tee2.bin
vbmeta.bin
vbmeta_system.bin
vbmeta_vendor.bin
open cmd and type below command
python mtk wl "<full path where 33 files are stored>"
Backup should be restored on same device from which it was taken else device may brick.
Thanks and Regards
Nand,
Click to expand...
Click to collapse
Can I ask how much time will it take to backup without userdata
hi i want this backup
idk why but my hanshake keeps failing.
i installed drivers as mentioned,but no coms showing up on device manager.
i think that when we install all drivers it usually shows like mtk device in devmgr,but it doesnt.
also i cant go to preloader mode easily.when i switch off phone and connect usb,it automatically turns back on.
why does it keep failing please help.are there any other methods for backup.like using sp flashtool.
pls help someone.
mohdsha said:
View attachment 5695877
idk why but my hanshake keeps failing.
i installed drivers as mentioned,but no coms showing up on device manager.
View attachment 5695881
i think that when we install all drivers it usually shows like mtk device in devmgr,but it doesnt.
also i cant go to preloader mode easily.when i switch off phone and connect usb,it automatically turns back on.
why does it keep failing please help.are there any other methods for backup.like using sp flashtool.
pls help someone.
Click to expand...
Click to collapse
ihave the same issue, did you find any solution to going into preloading?
mamomia said:
ihave the same issue, did you find any solution to going into preloading?
Click to expand...
Click to collapse
no bro.. im still trying .. i use a 5a cable..maybe we need og cable to coonect.idk i will try some troubleshooting.if successfull ,i will let you know.
Nand kumar said:
python mtk wl "<full path where 33 files are stored>"
Backup should be restored on same device from which it was taken else device may brick.
Click to expand...
Click to collapse
can a backup of the 33 files be applied to a new device which is exactly the same model without bricking it? (ie. a rom transfer to create a clone onto second device)
Hello and thank you so much for your guide. I was able to get everything setup for the most part, but I am held up by two problems, I'm sure they are simple but I would appreciate any help if anyone knows the answer.
Problem number one, is the correct vcom driver, the preloader one as shown in this
Spoiler: PIC
Or should I be using another?
My other question is, what is the correct terminology for what we are trying to achieve by getting the phone to register in the MTK client? Like, are we trying to get it to "boot into preloader mode"?
Spoiler: PIC
I am unable to get my phone to register or show in device manager or with the mtk client, to get it to post into the "preloader" mode. Since I do not know how to adequately describe what I am trying to do, I am having a hard time even searching on google for more help. If anyone can give me any help in grammer google search or direct knowledge on this simple part i would appreciate it
The answer to the driver question is to install all of them not just one. This discussion on reddit has some comments which go into more discussion of the bootrom protection and other github repos to achieve this. So to answer my main question about the phone not being detected by the MTK client it seems there is one more step for myself and other folks in this condition.
Spoiler: show link
https://www.reddit.com/r/androidroot/comments/wj6zrv
This guide explains how the MTK devices load the preloader. It is only up for 1 second apparently
Spoiler: show link
https://www.reddit.com/r/Smartphoneforensics/comments/xwd562
thanks a lot!!!! i have installed easily mtk client on garuda linux, and works very well (used for restore stook boot and solve a bootloop that seems impossible to solve). this guide is what i'm searching from some week. a way to do a full backup of my phone, userdata included
my suggestion for install mtkclient and other android tool is switch to garuda linux. if you try linux, you will never use windows again. garuda app manager with chaotic-aur have all software that you need. try to believe

LG G710EAW partitions corrupted. Permanently Locked!!

I hard bricked an LG G7 ThinQ G710EAW by flashing the wrong firmware (T-Mobile) onto it via LGUP. It now goes into EDL mode after shorting test points, but I'm unable to revive it by following this unbrick thread. Loading up the partition images via Partition Manager in QFIL "succeeds", but it doesn't revive my phone. Doesn't get me to fastboot. Still nothing on screen.
I also tried the rawprogram*.xml option using the XMLs in that thread, but QFIL keeps erroring out that the partition sizes defined in the XML are different from what it sees on the device.
The OP for the thread seems to not be active any longer.
Can someone here please help me understand how to recover my phone?
Anyone? Happy to donate for help as well.
Bumping up this thread.
If I had another EAW motherboard, would it help unbrick my motherboard? Wondering how I can fix my phone
So, I was able to finally figure this all out, recover my LG G710EAW and bring it back to life! It was a mix of information from many threads. No boxes, and no payment to anyone. All free.
The OP of this thread is active but has completely stopped responding to his thread and to his DMs - he's likely uninterested in a 4-5 year old phone at this point. In his first post he mentioned creating rawprogram* XMLs by hand, and it taking hour+ to do so. However, I'm unsure why it took him that long and in the end the files don't even work for QFIL since the sector size in the XMLs (512B) is different from device sector size (4096B). Nevertheless, I was able to flash these via command line 'edl' which ignored the sector size, but it didn't recover the device.
Generating rawprogram XMLs is easy if you can figure out how to run this Python program mentioned in this thread. However, the files attached there no longer work in 2022, the links are dead, and Python 2.7 is a dinosaur. Someone in that thread mentioned a different, fixed, repo but it didn't work with Python 2.7 for the 'undz' part. After a lot of head banging, I tried Python3 and 'undz' worked.
Here are the steps:
- Download the firmware for your model in KDZ format
- Install QPST
- Install Python3.x
- Run: pip3 install setuptools zstandard
- Download ZIP for kdztools from the repo: https://github.com/ErickG233/kdztools (or the attachment)
- Unzip kdztools and CD into that directory kdztools-master. This version is bug-fixed and also generates rawprogram files for us.
- Copy the firmware KDZ into kdztools-master directory
- Run: python3 unkdz.py -f G710EAW30e_00_0916.kdz -x. This creates a DZ file in a new `kdzextracted` folder
- Move the extracted DZ file from the kdzextracted folder back one level up, into kdztools-master dir
- Run: python3 undz.py -f G71030q_00_user-signed-ARB0_OPEN_ESA_DS_OP_0916.dz -c
- This creates a dzextracted folder here with all the files needed to recover your phone. Now all we need are the rawprogram XMLs.
- Run: python3 undz.py -f G71030q_00_user-signed-ARB0_OPEN_ESA_DS_OP_0916.dz -r. This will create all the rawprogram XMLs you need to flash. No patch files are created, but that is OK.
- In my case, QFIL complained it couldn't find file "PrimaryGPT_0.bin", so I copied file gpt_main0.bin_0 and renamed the copy gpt_main0.bin_0_copy > PrimaryGPT_0.bin
- Load your phone into EDL mode. If you want to use test points, see the image in this thread.
- Load QFIL. Use the ELF programmer file from any of the threads linked thus far. Select flat build. Load all rawprogram XMLs generated previously. Hit cancel when it asks for patch file XMLs.
- Hit Download.
This will recover your phone so it's able to boot and all. However, in my case, the phone had lost serial number and IMEI numbers (dual SIM) as well.
- To restore your IMEI numbers, you will need your QCN file or a backup of your FSG (fsg.img) partition from before bricking. In my case, I had flashed, via LGUP, T-Mobile firmware on my Indian phone. I then dumped all the partitions using command line EDL. I have not used QCN method since it seems to require a lot of steps to put the phone into diagnostics mode. I had a backup of the FSG partition, so I used that instead.
- If you have a backup of your FSG partition, load QFIL > Partition Manager. Erase modemst1 modemst2 and fsg partitions. Then, load the backup FSG.img file onto FSG partition. Restart phone.
- Now, if you have the serial number from your bill or box, see this thread to restore it. Pay extra attention to the Firehose configuration section, or else, it may create some issues. It's best to restore S/N after restoring IMEI in my experience, but this could just be some randomness or bad Firehose config during S/N restore.
This happiness was short-lived. When I was flashing all these KDZ via QFIL and LGUP trying to get my IMEIs back, I once saw "This phone is permanently locked and cannot be unlocked". That seems to have taken out my second SIM slot.
Now, after a fresh QFIL flash (with erase before download), my first SIM slot is also dead.
Neither of the SIM slots work now.
This has been so frustrating!
urover said:
This happiness was short-lived. When I was flashing all these KDZ via QFIL and LGUP trying to get my IMEIs back, I once saw "This phone is permanently locked and cannot be unlocked". That seems to have taken out my second SIM slot.
Now, after a fresh QFIL flash (with erase before download), my first SIM slot is also dead.
Neither of the SIM slots work now.
This has been so frustrating!
Click to expand...
Click to collapse
Any luck in recovering the phone ??

Categories

Resources