Database Info

[Q] Unbrick LG Optimus Net

Wondering if there is anyone here willing to help me with this issue. I tried flashing the phone with the LG Tool and the .cab firmware file but it keeps giving me a fatal error. I also could not use the tool for converting it to .kdz. Please can someone give me instructions for unbricking this phone and or point me to a firmware that I can try flashing with Odin or a .kdz package? Can it be done from the memory card? I had CWM recovery installed but all I can get it to do his hang on the LG logo or go into emergency mode. Any help appreciated. Thanks.

Use this to download your original kdz.

post-mortem said:
Use this to download your original kdz.
Click to expand...
Click to collapse
Only downloads a 7.88MB file when the firmware is 95.6MB.
After following these instructions:
Step 1: Get drivers here and install them
LGUnitedMobileDriver_S4981MAN37AP22_ML_WHQL_Ver_3. 7.2.exe
Step 2: Reboot
Step 3: Make sure phone has at least 50% battery
Step 4: Get firmware here
Firmware LGL45CT2_01
Step 5: Download this and extract
KDZ_FW_UPD_EN.zip
Step 6: Put phone in emergency mode
To put the LGL45C into download/emergency mode:
1. With the phone powered off you hold Volume Down and Back at the same time.
2. While holding the keys insert a USB cable plugged into a PC or charger, in a couple of seconds the the screen should say emergency mode at the bottom.
Step 7: Follow these steps in order (This is from the extracted "KDZ_FW_UPD_EN.zip" ZIP)
Install msxml.msi
Disable antivirus software
Open UpTestEX_mod2_marwin.exe
Wait for the program to open
Look for "Encrypt cab file to kdz file"
Click the folder icon
Choose the location of the cab you downloaded for L45C firmware
Encrypt cab -> kdz Program will freeze up. DO NOT EXIT until program says Done!!! Otherwise it won't finish converting.
Close program
Open KDZ_FW_UPD.exe
"Type" choose CDMA
Choose in "Phonemode": Emergency
Click the folder icon and choose the kdz file that UpTestEX_mod2_marwin.exe just made.
Click Launch software update and enjoy!
I get:
"
[R&D Test Tools Log File]
13:06:25 : Launching SW update
13:06:25 : Unpacking KDZ
13:06:28 : KDZ file extraced
13:06:35 : Files were extracted.
13:06:35 : LGMobileDL Load.
13:06:35 : Port = -1
13:06:35 : Connecting to phone
13:06:44 : Check Phone mode = 2
13:06:51 : Phone type check.......
13:06:51 : LGMobileDL.DLL Loading....
13:06:51 : _SetAuthMark Ok : wAuthMark(13164)
13:06:51 : LoadLibrary Error(126)
13:06:53 : ===FINISHED===
"

I believe the KDZ flasher will work with the phone in emergency mode. It's a bit more dangerous than LGMDP, because you can brick the phone if you pull the battery, or if your computer happens to freeze during the flash.

post-mortem said:
I believe the KDZ flasher will work with the phone in emergency mode. It's a bit more dangerous than LGMDP, because you can brick the phone if you pull the battery, or if your computer happens to freeze during the flash.
Click to expand...
Click to collapse
Yes, but I can't seem to find a solution to the error.

13:06:51 : LGMobileDL.DLL Loading....
13:06:51 : _SetAuthMark Ok : wAuthMark(13164)
13:06:51 : LoadLibrary Error(126)
Click to expand...
Click to collapse
It's unable to load the .dll file. If that file is included in the files you downloaded, try downloading it again. If it's downloaded on the fly by the program you were running, try running it again, to force it to redownload the dll. Also, make sure there isn't another version re: 32 vs. 64 bit. Lastly, try doing the update on another computer.

post-mortem said:
It's unable to load the .dll file. If that file is included in the files you downloaded, try downloading it again. If it's downloaded on the fly by the program you were running, try running it again, to force it to redownload the dll. Also, make sure there isn't another version re: 32 vs. 64 bit. Lastly, try doing the update on another computer.
Click to expand...
Click to collapse
Still getting the same story on another PC.

Try this. Before you do the flash (the step which throws the error), look for LGMobileDL.dll on your computer, and replace it with this one or this one (they're different).

I'm sorry for bumping a nearly-year-old thread but I'm currently experiencing the same problems.
I successfully rooted my L45C but idiotically didn't do a backup and ran into some problems while playing around with it down the line. I am now stuck in a bootloop with CWM recovery.
I've tried the method that callihn tried (which I found on androidforums) and got the same results. I tried to force a system update with the LG Mobile Support Tool both to no avail. Replacing the LGMobileDL.dll (as suggested above) didn't help (the first link was dead for me as well).
I would love if it someone could help give me some insight on how to fix my problem.

DUDE, STOP!!
daihatsuboy said:
I'm sorry for bumping a nearly-year-old thread but I'm currently experiencing the same problems.
I successfully rooted my L45C but idiotically didn't do a backup and ran into some problems while playing around with it down the line. I am now stuck in a bootloop with CWM recovery.
I've tried the method that callihn tried (which I found on androidforums) and got the same results. I tried to force a system update with the LG Mobile Support Tool both to no avail. Replacing the LGMobileDL.dll (as suggested above) didn't help (the first link was dead for me as well).
I would love if it someone could help give me some insight on how to fix my problem.
Click to expand...
Click to collapse
K. Listen up. YOU ARE NOT BRICKED. DO NOT flash any of these solutions. If you can get into CWM recovery, you are GOLDEN. I wish
I could, as I am truly bricked. To truly brick it, just go to System>privacy>factory reset and then you can be where we are. What you want
is a copy of an LGl45c NANDROID backup. That's it, that's all. I have copies on my Linux partition (I'm in Windows now). You can email
me.
Do not lose ability to get to CWM. If you do, and all you can get to is the EMERGENCY download mode, you will find that the l45c is not
nearly as supported as you thought (just look at how many custom ROMs you could find). Flashing these firmware downloads may very well
brick your phone for real, especially since we are having difficulty finding the correct files that are not corrupt or really for a 'phone that may or
not be close....'.
I'd give you my phone number, but.... oh yeah, I'm bricked!!! lol!!! :cyclops:
Edit: Google for 'stock l45c images' (.img) files. They are hard to find. In fact, I did the same as you and couldn't find an original. I used
an older one. Know the definition of the word 'flash', and what you are flashing. You want to flash an .img, not a firmware update. (Firmware is the lowest. Think programming: machine>assembly>language). You are 'in assembly'. Yay!! Stay away from 'machine' !!)

Nandroid
COULD YOU PLEASE SEND ME THE BACKUPS!? Or any files you have for this phone!? Please and thank you!

what os did you use to flash the firmware my phone is bricked as well and none of these methods work, i always get load library error 126.

post-mortem said:
Try this. Before you do the flash (the step which throws the error), look for LGMobileDL.dll on your computer, and replace it with this one or this one (they're different).
Click to expand...
Click to collapse
Some of these links don't work any more. I've attached a ZIP archive of various versions of the LGMobileDL.dll file. I downloaded these versions from zhaodll.co (very skeptically at first), but ran them through my virus checked, then stripped the junk and identifier files that site added to the package.
Unfortunately, I haven't had success at using any of these modules with the KDZ program. I still either hit the LoadLibrary error ("LoadLibrary Error(126)"), or the KDZ program hangs.

post-mortem said:
It's unable to load the .dll file. If that file is included in the files you downloaded, try downloading it again. If it's downloaded on the fly by the program you were running, try running it again, to force it to redownload the dll. Also, make sure there isn't another version re: 32 vs. 64 bit. Lastly, try doing the update on another computer.
Click to expand...
Click to collapse
We are discussing a few different DLL files. I discovered that LGMobileDL.dll does not cause the problem. The absence of a different DLL file causes the problem (and the LGMobileDL reports the error).
Unfortunately, the download for this specific device (the CAB file) does not contain a DLL which the flasher application expects to use. LG's own "Mobile Support Tool" downloads a file from LG's servers and expects the package to contain this DLL file to process the flashing, but for the LGL45C, the package does not contain this DLL (again, from LG's own servers!).

[official][stock] sm-g360v

DISCLAIMER: Since this is a third-party supplied file, flashing this file places any and all outcomes on YOU, the flasher (get your mind out of the gutter, thanks.) This file, though supplied by Samsung Kies 3, may cause issues or have undesirable effects. What these effects are, I have no clue. If you have a custom recovery, it will be overwritten with the stock recovery. Again, if you use this, you are the one responsible for any negative outcome.
​This the official stock ROM flashable via Odin. This took me a few hours to download several times and locate the temp directory that housed it. It is a 2.12 gig tar.md5 file. Since Samsung does not have an open source copy for us to download, I used Kies 3 to download it.
FLASHING INSTRUCTIONS:
Using the most recent Odin, put the file in the AP section and flash it.
Link

Thank you so much it fixed my bricked device!

Thank you so much - Accidentally upgraded firmware and lost root and could not re-root. Worked like a charm and used kingroot to gain root again. You rock!

It downloads as a .RAR file if converted to .TAR, ODIN can not load it. How can the .rar file be used by ODIN?

bunivers said:
It downloads as a .RAR file if converted to .TAR, ODIN can not load it. How can the .rar file be used by ODIN?
Click to expand...
Click to collapse
The flashable .Tar file that you will use to restore your device via Odin, is located inside the .RAR provided in the download link. Once the .RAR file has been unrared/unzipped using 7zip, you will have your restore .Tar file that you're referring to. If you need to, you can Google 7zip and download it. The program is free and open-source, and it supports .RAR .TAR .ZIP etc. Happy Restore!

@jaywillsoul Please add to the OP that this firmware will wipe the device.
Thanks again for the firmware!
Sent from my XT1528 using XDA Labs

I was able to un-brick my wife's Verizon Core Prime with this. Thank you for your time and effort, @jaywillsoul.
Donation sent.

Fail
I downloaded the firmware, began to flash and Odin wrote "FAIL", and the screen after turning on is "Software update failed. Your device didnt update successfully. Use the Verizon Software Repair Assistant on a computer to repare your device and complete the update." But the Verizon Software Repair Assistant after this can not find the phone.

Thank you for this wonderful gift to the underdeveloped Core Prime! :good: worked for me and I was able to root afterwards!

is that process unlock the sim card lock for Verizon

ty it work's. I can root now

Sorry to bump this thread, but will updating through recovery mode end up wiping all the data of the phone? (like pictures, and files)
I was dumb and didn't enable usb debugging before my phone got soft bricked, now it freezes on the carrier animation
My phone is a model SM-G360T1

Link999123 said:
Sorry to bump this thread, but will updating through recovery mode end up wiping all the data of the phone? (like pictures, and files)
I was dumb and didn't enable usb debugging before my phone got soft bricked, now it freezes on the carrier animation
My phone is a model SM-G360T1
Click to expand...
Click to collapse
You have the wrong model - this guide is for the G360V, not the G360T1. Sorry.

Camera is broken.

Hello,
My device is the Mate 9 (MHA-L29C185B110) and I seem to have a problem with the camera.
When pressing the button to take a photo, the camera app restarts itself. I try again, but didn't work, to no avail.
I also tried to record a video. It seems to work, but the camera freezes but it's still counting, otherwise recording.
I have just recently flashed a custom recovery img (TWRP), the boot img on another thread that prevents the device from being automatically encrypted, and SuperSU root.
Do any of you have a solution to this problem?
Would this be because I haven't flashed Public_data.zip and Full_HW_data.zip?
And will this problem fix if I completely install the MHA-L29C185B172's firmware?

SeanPHTRPW said:
Hello,
My device is the Mate 9 (MHA-L29C185B110) and I seem to have a problem with the camera.
When pressing the button to take a photo, the camera app restarts itself. I try again, but didn't work, to no avail.
I also tried to record a video. It seems to work, but the camera freezes but it's still counting, otherwise recording.
I have just recently flashed a custom recovery img (TWRP), the boot img on another thread that prevents the device from being automatically encrypted, and SuperSU root.
Do any of you have a solution to this problem?
Would this be because I haven't flashed Public_data.zip and Full_HW_data.zip?
And will this problem fix if I completely install the MHA-L29C185B172's firmware?
Click to expand...
Click to collapse
It could be a problem if you flashed a boot image for a different model. You need boot image for C185B110. It should work without hw and Public zips, but a lot of other things break without flashing those. Updating to C185B172 will fix it.
By the way, which supersu did you use?
If the one from the "Decrypt" thread in Guides you don't need to flash a pre-decrypted boot image, the installer does it for you.

ante0 said:
It could be a problem if you flashed a boot image for a different model. You need boot image for C185B110. It should work without hw and Public zips, but a lot of other things break without flashing those. Updating to C185B172 will fix it.
By the way, which supersu did you use?
If the one from the "Decrypt" thread in Guides you don't need to flash a pre-decrypted boot image, the installer does it for you.
Click to expand...
Click to collapse
As for the SuperSU, I think I took it from the full root guide w/o decrypt img, but obviously I had to use a decrypt img because of stock
SUPERSU-2.79-MATE9-init.d_support
For the boot (No force encryption boot)
This is probably where things went wrong. I flashed the wrong build image.
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
I had to use above link because I couldn't flash SuperSU since I don't have an external sd to extract it from (Since you have to format your data before flashing it)
I couldn't find the hw and public zips for C185B110, so if you have it, a link would be generous.
Would flashing stock boot img for MHA-L29C185B110 fix it?
and what would happen if i flash stock boot.img?
and do you have a decrypt boot.img for C185B110?
Thanks!

SeanPHTRPW said:
As for the SuperSU, I think I took it from the full root guide w/o decrypt img, but obviously I had to use a decrypt img because of stock
SUPERSU-2.79-MATE9-init.d_support
For the boot (No force encryption boot)
This is probably where things went wrong. I flashed the wrong build image.
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
I had to use above link because I couldn't flash SuperSU since I don't have an external sd to extract it from (Since you have to format your data before flashing it)
I couldn't find the hw and public zips for C185B110, so if you have it, a link would be generous.
Would flashing stock boot img for MHA-L29C185B110 fix it?
and what would happen if i flash stock boot.img?
and do you have a decrypt boot.img for C185B110?
Thanks!
Click to expand...
Click to collapse
It would probably fix it yes, but no boot image or hw/public exist for B110 so I'm guessing it shipped with that build.
You'd have to update, using https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
I don't think you can use Firmware Finder as you're probably missing the System Update feature.
Either that one I linked or FunkyHuawei, but Funky cost money to use.

Thanks,
I will try using the link you used.
although it is not clear.
On manual update step A, do you need to download all three?
the base, the OS(windows) and the model?
and where do i put these files?
and on b and c on update zip
do i have to download two update.zip?
for example, C185B110 and C185B172
do i also need to download full ota instead of just ota? fullota is incompatible, says firmware finder on mobile

SeanPHTRPW said:
Thanks,
I will try using the link you used.
although it is not clear.
On manual update step A, do you need to download all three?
the base, the OS(windows) and the model?
and where do i put these files?
and on b and c on update zip
do i have to download two update.zip?
for example, C185B110 and C185B172
do i also need to download full ota instead of just ota? fullota is incompatible, says firmware finder on mobile
Click to expand...
Click to collapse
Yes, download base, os and MHA. Extract all to the same folder. You should only have one folder named HWOTA and the files/folders in that. If it extracts to a folder with the same name as the zips, enter the folders and copy hwota folder then go back one folder and paste/merge so you end up with one folder named HWOTA. Easiest way is putting it directly in C:\hwota\, if your windows version allows it. Else place it on desktop. (long file paths or a path containing spaces might make hwota not function correctly).
You need to download all 3 files (fullota update.zip, hw zip and Public zip), easiest way is using firmware finder to download. Either mobile or the pc version. For pc go to the common base tab and search for your model and then download the build you want including public and HW zips.
You only need to download the fullota update, hw and Public zip of the build you're updating to. If you're on b110 and going to update to B172 you only need to download B172.
Rename the files according to the guide (update.zip, update_all_hw.zip and update_data_public.zip), place them in either hwota/update folder or make a HWOTA folder on your sdcard and put the renamed files there.
When running hwota, select script update folder or sdcard update folder depending on where you put the files. Select same model update.

One last question:
Does it have to be FULLOTA, not just OTA?

LG Aristo 3 X220MA Root Search

So I just got the Aristo 3 and wanted to root it. after an extensive search I have come up empty. Does anyone know if there is a method available to use yet or maybe something is in the works? I've unlocked flashing but I cant seem to boot recovery. Any help would be greatly appreciated.

Same ive spent about 6 hours researching this ive never built my own root before however i just dont have the time to do whats needed. From what i researched get the original boot rom from lg bridge and perform a restore to download the factory boot image then use magisk to rebuild the image

Nvitethedark said:
Same ive spent about 6 hours researching this ive never built my own root before however i just dont have the time to do whats needed. From what i researched get the original boot rom from lg bridge and perform a restore to download the factory boot image then use magisk to rebuild the image
Click to expand...
Click to collapse
Hmm I'll give it a try. The phone is still new enough that I don't have much saved to it and if I brick it can take it back

should be able to just get the boot image may be the aristo 2 dev would pick this up since he's familiar with it I see you have a few posts in that forum maybe you can send that dev a message see if they would pick it up.

I eagerly await any progress in this run! My girlfriend cracked her screen on her Aristo 2 and decided that it was time to upgrade. I've never been disappointed in the idea of upgrading my phone...until it meant giving up my Aristoboy Mk.2(which was/is quite formidable)and rooted status along with it. If there is anything I might read about the process online, I would at very least consider the task myself. I am learning, but I have some decent skills and experience behind me. Please let me know if I can assist in any way. If not, I hope to see the first strides towards tackling this latest addition to the Aristo line!
My thanks to all my fellow devs here! You each make up a piece of the whole collection that make this, hands down the best forum/online community available the world over! Keep it up! We are making a difference in so many lives!
Your friend,
~[ProTech]~

So I've been busy as **** lately, but I found that the issue seems to be with the os more than the phone itself. I'm not that proficient with downgrading the os to a earlier version since this phone came stock with Oreo. I will try and talk to some of the devs who did the aristo 2 x210ma. Hopefully they have a solution. I've been using my 2 instead. I never realized how much you can't do with a stock phone and os.

OK here's something you can try...
first get dev-patched LGup {GooGle It}
then use the Dump function of Lgup to dump All partitions from your fone...
look for boot_COM{some#here} and rename it to boot.img
put that file on your fones sdcard and install magisk manager app.
use magisk manager app to patch that boot.img file.
find the new file patched_boot.img whereever magisk put it on your sdcard...
move it to your desktop or a folder etc. on P.C
now try to flash it to your fone...
Code:
adb reboot bootloader
Code:
fastboot oem unlock
if that works your bootloader is now unlocked you'll have to reboot the fone once as it'll erase cache and data...
after that
again do
Code:
adb reboot bootloader
now try
Code:
fastboot flash boot patched_boot.img
if that works....
Code:
fastboot reboot
and you'll have root by magisk.
if fastboot's not working other option is to rename "patched_boot.img" to "boot.img"
and then use Partitions DL option in lgup to flash the "patched"boot.img to the phone...
if that works you'll have root by magisk...
If this helped you feel free to hit thanks and come back to post the results plz.
Thanks

LgPWN'd said:
OK here's something you can try...
first get dev-patched LGup {GooGle It}
then use the Dump function of Lgup to dump All partitions from your fone...
look for boot_COM{some#here} and rename it to boot.img
put that file on your fones sdcard and install magisk manager app.
use magisk manager app to patch that boot.img file.
find the new file patched_boot.img whereever magisk put it on your sdcard...
move it to your desktop or a folder etc. on P.C
now try to flash it to your fone...
Code:
adb reboot bootloader
Code:
fastboot oem unlock
if that works your bootloader is now unlocked you'll have to reboot the fone once as it'll erase cache and data...
after that
again do
Code:
adb reboot bootloader
now try
Code:
fastboot flash boot patched_boot.img
if that works....
Code:
fastboot reboot
and you'll have root by magisk.
if fastboot's not working other option is to rename "patched_boot.img" to "boot.img"
and then use Partitions DL option in lgup to flash the "patched"boot.img to the phone...
if that works you'll have root by magisk...
If this helped you feel free to hit thanks and come back to post the results plz.
Thanks
Click to expand...
Click to collapse
My bootloader is already unlocked I've just not been able to flash anything with fastboot. So I have LGup, is there a difference with the dev patched one? I also have magisk on my phone, but it really doesn't give me any options besides to install a new version. I'm gonna go try your suggestion soon though...it sounds promising...and may open up other options if this doesn't succeed. Thanks I'll keep you posted.

Reckless459 said:
My bootloader is already unlocked I've just not been able to flash anything with fastboot. So I have LGup, is there a difference with the dev patched one? I also have magisk on my phone, but it really doesn't give me any options besides to install a new version. I'm gonna go try your suggestion soon though...it sounds promising...and may open up other options if this doesn't succeed. Thanks I'll keep you posted.
Click to expand...
Click to collapse
PLease let us know how it go's...
I'm trying to port and compile Multi-rom for LG-aristo Lg-m210 at the moment...
So I have LGup, is there a difference with the dev patched one?
.
Click to expand...
Click to collapse
in answer to that YES quite a difference...
devpatched lgup gives you extra options such as Dump and Partitions-DL and Chiperase among others...
you'll NEED that dump and partitions-DL option....

LgPWN'd said:
PLease let us know how it go's...
I'm trying to port and compile Multi-rom for LG-aristo Lg-m210 at the moment...ll
Click to expand...
Click to collapse
So I can't get passed the dump. I keep getting a timed out error. I even tried to format the user data using fastboot and it failed. And I am curious about the boot_COM. I didn't see any file in the partition list matching that. I did see the boot partition and many others that I didn't recognize. So kinda feeling that we are back to

Reckless459 said:
So I can't get passed the dump. I keep getting a timed out error. I even tried to format the user data using fastboot and it failed. And I am curious about the boot_COM. I didn't see any file in the partition list matching that. I did see the boot partition and many others that I didn't recognize. So kinda feeling that we are back to
Click to expand...
Click to collapse
No the file wont say that in lgup, it'll be named that after you create a new folder on desktop call it "Dump" then use the dev-patched lgup and Dump option, select the folder Dump on the desktop and select the little checkbox for all on partitions list and click start...
also you may be haveing issues because of the .dll your useing... will lgup flash a stock .kdz to the device?
if yes, I'd think the dump option would work fine...
for firmware look here : https://www.mylgphones.com/metropcs-lg-aristo-3-lmx220ma-x220ma-firmware.html
for direct download use this link
Code:
http://pkg02.lime.gdms.lge.com/dn/downloader.dev?fileKey=FW88KEQ4C2VSAF0C3D54FH4/X220MA10e_00_MPCS_US_OP_0123.kdz

LgPWN'd said:
No the file wont say that in lgup, it'll be named that after you create a new folder on desktop call it "Dump" then use the dev-patched lgup and Dump option, select the folder Dump on the desktop and select the little checkbox for all on partitions list and click start...
also you may be haveing issues because of the .dll your useing... will lgup flash a stock .kdz to the device?
if yes, I'd think the dump option would work fine...
for firmware look here : https://www.mylgphones.com/metropcs-lg-aristo-3-lmx220ma-x220ma-firmware.html
for direct download use this link
Code:
http://pkg02.lime.gdms.lge.com/dn/downloader.dev?fileKey=FW88KEQ4C2VSAF0C3D54FH4/X220MA10e_00_MPCS_US_OP_0123.kdz
Click to expand...
Click to collapse
So yes it would load a stock formware but no it wouldn't allow me to dump even one partion. And the strange thing was that my list of options would chanhe sometimes. Like it would give me more options i.e. phonesettings. I even tried different cables and ports. It doesnt matter though i somehow hard bricked it so bad that it won't even. Boot to download mode and somehow fried my sim card to the point it wont work in any other phone. Im just waiting for metro to open so i can try again

Reckless459 said:
So yes it would load a stock formware but no it wouldn't allow me to dump even one partion. And the strange thing was that my list of options would chanhe sometimes. Like it would give me more options i.e. phonesettings. I even tried different cables and ports. It doesnt matter though i somehow hard bricked it so bad that it won't even. Boot to download mode and somehow fried my sim card to the point it wont work in any other phone. Im just waiting for metro to open so i can try again
Click to expand...
Click to collapse
OH WOW what a mess...
I would say it's the .dll in the LGUP causing pain here...
something you can try when you're ready to try again....
remove/uninstall devpatched LGUP and install regular store version
use the Common .dll
and add this file{ UI_Config.lgl } to your Common folder in the lgup install location ...
to make it easier I'll just zip up My common folder for you to replace yours
to do this
right click on lgup, select open file location...
navigate to the model subfolder you'll see things like
{ AllinOne } {Common} and {LGUP_LGNPST} folders...
at that point just right click and rename {Common} folder to {Commonbak},
then take my zip file I'm attaching and unzip it and inside will be Common folder...
just Copy / Paste that new Common folder to where the old one is..
set permissions of folder { read-only} and open the folder find file called { UI_Config.lgl }
and set it's permissions to READ ONLY . otherwise it'll be erased once you start LGUP.
and see If that changes anything with being able to Dump...
It's let me dump every LG i've plugged into it...
so I should think it should work for you too...

@Reckless459
is there nothing further?

LgPWN'd said:
@Reckless459
is there nothing further?
Click to expand...
Click to collapse
Dude...
First off let me say MertoPCS has the biggest pile of **** customer care department. I'm still waiting on my new device to comr from the warrenty department. I did however fix the sim issue (again metro sucks leaky bowels). I will definitely post any new developments as soon as the happen.
Oh also i did a dump on another phone (aristo 2) and had no issuses. And i saw what ypu meant with the boot_COM##. Thanks for the help.

LGUP dll
Sorry apparently i haven't reloaded this page in 12 hrs and their has been progressing i have 2 aristos im going to work on this also.
i will step in and help out ill read the updates and post further
---------- Post added at 09:43 PM ---------- Previous post was at 09:35 PM ----------
LgPWN'd said:
@Reckless459
is there nothing further?
Click to expand...
Click to collapse
I had a question i would like to chime in here, can i do an extraction on the KDZ with lg extractor i see a boot image in it and flash that?

Nvitethedark said:
Sorry apparently i haven't reloaded this page in 12 hrs and their has been progressing i have 2 aristos im going to work on this also.
i will step in and help out ill read the updates and post further
---------- Post added at 09:43 PM ---------- Previous post was at 09:35 PM ----------
I had a question i would like to chime in here, can i do an extraction on the KDZ with lg extractor i see a boot image in it and flash that?
Click to expand...
Click to collapse
it may work,
when lgup is being a pain it's worth a try.
I say go for it. but to be certain I'd try flashing the extracted boot.img with partitions DL option in lgup once to make sure it flashes it b4 trying to patch it and flash it again...
Just my 2 cents.

LgPWN'd said:
it may work,
when lgup is being a pain it's worth a try.
I say go for it. but to be certain I'd try flashing the extracted boot.img with partitions DL option in lgup once to make sure it flashes it b4 trying to patch it and flash it again...
Just my 2 cents.
Click to expand...
Click to collapse
Aristo3 FW: X220MA10B "10b" came on the system stock
LGUP V1.14 - patched
DLL v1.0.28.17
The above dll is the only one I have found that will recognize the phone and load LGUP, I have also attempted to use uppercut: Error DLL for X220M10b is invalid install a valid dll
https://imgur.com/1Ptrv3n
however, once i attempt to dump phone reboots into download mode i get: Error: 0x2000, please use latest Dll LAF protocol version is not match dll=0 device 162512928
https://imgur.com/5I7GfOa
I attempted to use the LGUPC DLL from the kdz V 10E firmware and that did not recognize the device i also attempted to use your zipped commons.
any feedback on this?
I feel that i should use LG tool update to 0F then use the 0F kdz to attempt all this?

DOWNGRADE Don't UPGRADE
Nvitethedark said:
Aristo3 FW: X220MA10B "10b" came on the system stock
LGUP V1.14 - patched
DLL v1.0.28.17
The above dll is the only one I have found that will recognize the phone and load LGUP, I have also attempted to use uppercut: Error DLL for X220M10b is invalid install a valid dll
https://imgur.com/1Ptrv3n
however, once i attempt to dump phone reboots into download mode i get: Error: 0x2000, please use latest Dll LAF protocol version is not match dll=0 device 162512928
https://imgur.com/5I7GfOa
I attempted to use the LGUPC DLL from the kdz V 10E firmware and that did not recognize the device i also attempted to use your zipped commons.
any feedback on this?
I feel that i should use LG tool update to 0F then use the 0F kdz to attempt all this?
Click to expand...
Click to collapse
If at all posible find the OLDEST firmware possible in kdz and do a full flash of that .
and try your dll mod with that by extracting the dll from said kdz and renaming to what ever the one in Common folder is and keep the UI_Config.lgl in there to keep the extra options if possible...
It's all trial and error with this stuff, so keep at it.
DO NOT flash a firmware.kdz from a different model of the device as it'll flash aboot sbl etc and you'll end with a brick that can't be fixed.
and I've always liked { in my experiments} to use the partitions DL option even when downgrading etc to be able to NOT CHOOSE the boot-stack partitions...
but give it a shot and tell us how it go's.
we may be able to split a root-bounty if we come up with something working across users

LgPWN'd said:
OH WOW what a mess...
I would say it's the .dll in the LGUP causing pain here...
something you can try when you're ready to try again....
remove/uninstall devpatched LGUP and install regular store version
use the Common .dll
and add this file{ UI_Config.lgl } to your Common folder in the lgup install location ...
to make it easier I'll just zip up My common folder for you to replace yours
to do this
right click on lgup, select open file location...
navigate to the model subfolder you'll see things like
{ AllinOne } {Common} and {LGUP_LGNPST} folders...
at that point just right click and rename {Common} folder to {Commonbak},
then take my zip file I'm attaching and unzip it and inside will be Common folder...
just Copy / Paste that new Common folder to where the old one is..
set permissions of folder { read-only} and open the folder find file called { UI_Config.lgl }
and set it's permissions to READ ONLY . otherwise it'll be erased once you start LGUP.
and see If that changes anything with being able to Dump...
It's let me dump every LG i've plugged into it...
so I should think it should work for you too...
Click to expand...
Click to collapse
reinstalled a non-patched version of lgup and used your common folder and set read-only options attempted a dump got this:
https://imgur.com/FJPMUwv

Can I recover Tab3 7.0 Android 4.4.2 WiFi using Haimdall on FWUL and how is it done?

As Odin in Windows does not do the trick for me, flashing stock ROM onto the Tab3, 7.0 WiFi device, I'll now want to try using Haimdall on FWUL.
But to make that happen, I seem need seperate .img files as Haimdall works with seperate files instead of that big tar.md5 file like Odin in Windows does.
So the first question would be:
What tools do I need to get all these seperate .img files out of the stock ROM Odin uses??
In Haimdall I managed to detect the Tab3 device and download and save the PIT file successfully.
But when I try to write into 'recovery' partition using a renamed file (TWRP 3.0.0-0.img) recovery.img, the process failed.
The log shows successfull writing of the PIT file, but it failed on recovery.img with this error 'failed to confirm end file transfer sequence'.
Also, there's no progressbar showing on the Tab3 device, while writing.
I already tried other USB cables, same results.
So the second question would be:
What did I do wrong, or did I miss something?

xdausernl said:
As Odin in Windows does not do the trick for me, flashing stock ROM onto the Tab3, 7.0 WiFi device, I'll now want to try using Haimdall on FWUL.
But to make that happen, I seem need seperate .img files as Haimdall works with seperate files instead of that big tar.md5 file like Odin in Windows does.
So the first question would be:
What tools do I need to get all these seperate .img files out of the stock ROM Odin uses??
In Haimdall I managed to detect the Tab3 device and download and save the PIT file successfully.
But when I try to write into 'recovery' partition using a renamed file (TWRP 3.0.0-0.img) recovery.img, the process failed.
The log shows successfull writing of the PIT file, but it failed on recovery.img with this error 'failed to confirm end file transfer sequence'.
Also, there's no progressbar showing on the Tab3 device, while writing.
I already tried other USB cables, same results.
So the second question would be:
What did I do wrong, or did I miss something?
Click to expand...
Click to collapse
To extract the firmware down to the individual .img files, try this thread, it leads to another guide on another site.
https://forum.xda-developers.com/showthread.php?t=2138885
Keep in mind, this guide is a bit old, the basic process is still valid but some things may have changed in how Samsung firmware is put together, there may be some extra steps required for firmware from newer devices.
Sent from my LGL84VL using Tapatalk

Droidriven said:
To extract the firmware down to the individual .img files, try this thread, it leads to another guide on another site.
https://forum.xda-developers.com/showthread.php?t=2138885
Keep in mind, this guide is a bit old, the basic process is still valid but some things may have changed in how Samsung firmware is put together, there may be some extra steps required for firmware from newer devices.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply,
Right after I wrote this text, I came up with another approach ... to just rename the stock ROM extension 'tar.md5' to '.tar' and so I did, then I unzipped the file.
But thanks anyway ...
Inside I found several files and about 6 image files and the PBL.bin file.
For 4 partitions I found an image file, system.img, NVM.img, cache.img and hidden.img.
Guess what ... with Haimdall in FWUL the upload went successfully and there's also a statusbar on Tab3 while at download, where as Odin (any version) in Windows failed on me all the time.
All files needed to upload seperately though, all at the same time gave me this error 'failed to confirm end of file transfer sequence'.
For the boot.img file I couldn't find a partition.
Recovery.img and the PBL.bin file failed to upload using Haimdall with errors 'failed to upload' and 'failed to confirm end of file transfer sequence'.
I also tried to rename a TWRP image to recovery.img, but that upload failed as well.
At this point I only proved the hardware being OK, that is the USB cable and the USB port on the Tab3 device.
It seems like Android operating system crashes after the message windows from antivirus program 'program has stopped', it then shut down and reboot.
After login the same thing happens all over again ... like some sort of boot loop.
And there's just not enough time to change any of the system settings, nor to disable any apps due to all those message windows you have to click first.
Overall status being Android operating system is still faulty.
This means that I just may be able to fix this thing, I only need the right tools to get the job done.
And I can't believe there's no one out there that couldn't help me out ...

xdausernl said:
Thanks for your reply,
Right after I wrote this text, I came up with another approach ... to just rename the stock ROM extension 'tar.md5' to '.tar' and so I did, then I unzipped the file.
But thanks anyway ...
Inside I found several files and about 6 image files and the PBL.bin file.
For 4 partitions I found an image file, system.img, NVM.img, cache.img and hidden.img.
Guess what ... with Haimdall in FWUL the upload went successfully and there's also a statusbar on Tab3 while at download, where as Odin (any version) in Windows failed on me all the time.
All files needed to upload seperately though, all at the same time gave me this error 'failed to confirm end of file transfer sequence'.
For the boot.img file I couldn't find a partition.
Recovery.img and the PBL.bin file failed to upload using Haimdall with errors 'failed to upload' and 'failed to confirm end of file transfer sequence'.
I also tried to rename a TWRP image to recovery.img, but that upload failed as well.
At this point I only proved the hardware being OK, that is the USB cable and the USB port on the Tab3 device.
It seems like Android operating system crashes after the message windows from antivirus program 'program has stopped', it then shut down and reboot.
After login the same thing happens all over again ... like some sort of boot loop.
And there's just not enough time to change any of the system settings, nor to disable any apps due to all those message windows you have to click first.
Overall status being Android operating system is still faulty.
This means that I just may be able to fix this thing, I only need the right tools to get the job done.
And I can't believe there's no one out there that couldn't help me out ...
Click to expand...
Click to collapse
I have to edit the last post, because I can change the stock ROM file name as mentioned before and that did not cause any problems with the md5 hash.
At this point, I can also download all files (10) succesfully from Heimdall with the Samsung tablet.
The only problem is caused by replacing the 'system.img' file, as the tablet immediatly reboots after Heimdall released the device after download was successfully.
It could mean that after the succesfull download, the downloaded system.img file is deleted at immediate reboot of the tablet, which would also explain why there's no changes after tablet reboot.
With all the other 9 downloaded files from Heimdall, it took several seconds until reboot of the tablet.

xdausernl said:
I have to edit the last post, because I can change the stock ROM file name as mentioned before and that did not cause any problems with the md5 hash.
At this point, I can also download all files (10) succesfully from Heimdall with the Samsung tablet.
The only problem is caused by replacing the 'system.img' file, as the tablet immediatly reboots after Heimdall released the device after download was successfully.
It could mean that after the succesfull download, the downloaded system.img file is deleted at immediate reboot of the tablet, which would also explain why there's no changes after tablet reboot.
With all the other 9 downloaded files from Heimdall, it took several seconds until reboot of the tablet.
Click to expand...
Click to collapse
Try a windows PC and try flashing via Odin, it tends to work better than Heimdall.
Also, if you are trying to use a system.img that is different than the system.img in your firmware, your bootloader may not be allowing the different system to flash or boot on your device.
Sent from my SM-S767VL using Tapatalk

xdausernl said:
Thanks for your reply,
Right after I wrote this text, I came up with another approach ... to just rename the stock ROM extension 'tar.md5' to '.tar' and so I did, then I unzipped the file.
But thanks anyway ...
Inside I found several files and about 6 image files and the PBL.bin file.
For 4 partitions I found an image file, system.img, NVM.img, cache.img and hidden.img.
Guess what ... with Haimdall in FWUL the upload went successfully and there's also a statusbar on Tab3 while at download, where as Odin (any version) in Windows failed on me all the time.
All files needed to upload seperately though, all at the same time gave me this error 'failed to confirm end of file transfer sequence'.
For the boot.img file I couldn't find a partition.
Recovery.img and the PBL.bin file failed to upload using Haimdall with errors 'failed to upload' and 'failed to confirm end of file transfer sequence'.
I also tried to rename a TWRP image to recovery.img, but that upload failed as well.
At this point I only proved the hardware being OK, that is the USB cable and the USB port on the Tab3 device.
It seems like Android operating system crashes after the message windows from antivirus program 'program has stopped', it then shut down and reboot.
After login the same thing happens all over again ... like some sort of boot loop.
And there's just not enough time to change any of the system settings, nor to disable any apps due to all those message windows you have to click first.
Overall status being Android operating system is still faulty.
This means that I just may be able to fix this thing, I only need the right tools to get the job done.
And I can't believe there's no one out there that couldn't help me out ...
Click to expand...
Click to collapse
Droidriven said:
Try a windows PC and try flashing via Odin, it tends to work better than Heimdall.
Also, if you are trying to use a system.img that is different than the system.img in your firmware, your bootloader may not be allowing the different system to flash or boot on your device.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply.
But I came to Heimdall because Odin3 in Windows and even JOdin3 in Linux failed.
My guess is that the installed system.img on the system partition the culprit was in this case, because the stock ROM was the correct one for my tablet.
If you don't have the correct software, you either cannot install it or you will get your device bricked.
My device seem to be software bricked, for that matter and that is due to either the root software, anti virus software or an combination of both.

xdausernl said:
Thanks for your reply.
But I came to Heimdall because Odin3 in Windows and even JOdin3 in Linux failed.
My guess is that the installed system.img on the system partition the culprit was in this case, because the stock ROM was the correct one for my tablet.
If you don't have the correct software, you either cannot install it or you will get your device bricked.
My device seem to be software bricked, for that matter and that is due to either the root software, anti virus software or an combination of both.
Click to expand...
Click to collapse
Meanwhile I think I found a possible cause for failure using Heimdall-Frontend.
Heimdall-Frontend uses only extracted content of a stock ROM, in my case that's 10 files.
Although the download of the 'system.img' file completed successfully and Heimdall-Frontend releases the connected device, there's still a slightly different behaviour at reboot of Tab3.
Because after the release of the connected device, Tab3 then immediately goes into reboot.
That's not the case with all other downloaded files.
After releasing the connected device, it then takes a few second until the Tab3 goes into reboot.
So my guess is that at immediate reboot the downloaded 'system.img' file will then be deleted from the Tab3.
That would explain why after reboot nothing has really being changed.