Can't find kdz file for LGH918 (T-Mobile LG V20) - LG V20 Questions & Answers

I'm trying to find the latest kdz file for the H918 (T-Mobile LG V20). After looking at several guides, I still can't track it down.
This guide gives a link where you can supposedly download the firmware, but all I can find by following that guide is the Android source code, not a .kdz file.
This guide gives a url you can visit (on a non-standard port), and you have to put your phone's IMEI number in the URL parameters. This url will return an xml file that contains another url where you can download the kdz for your specific phone. However, when I followed this guide, the xml file returned a successful response but the sw_url field was empty (along with most other fields).
Other guides have said to go to https://lg-firmwares.com/category/lg-series/lg-v20/ but I am getting a 500 server error on that page. Maybe it's just down today, but seems kind of odd that I can't access it. When I try to find LGH918 by visiting the main domain name (lg-firmwares.com) and navigating from there, I can't seem to find anything.
The closest I have come so far is this download page, but it is for the LGH918TN (instead of LGH918). Is that "close enough" or is it going to brick my phone?
UPDATE: I think I did find the correct kdz file since I started writing this post, but I am going to post this information anyway, for anybody else having the same issue. I went to lg-firmwares.com and clicked "Check IMEI" and entered my phone's IMEI number. It directed me to a download page for LGH918TN, so it looks like that is correct for my phone! I will try and remember to report back here on whether the kdz file actually worked or not. Hoping it doesn't brick my phone, yet again.

As an update to my original post, I did manage to successfully flash the kdz file using the "Upgrade" option in LGUP, and did not lose any of my data. However, I'm still getting the unlocked bootloader message when I start my phone ("Your device cannot be checked for corruption..."). Does anybody know if flashing the .kdz file causes TWRP to be replaced with the original recovery mode? I don't want to try to boot into TWRP in case it has been replaced, thus triggering a factory reset and losing all my data.
It ok to try and relock the bootloader now? (if so, how?) Or do I need to replace TWRP too?

fronzee88 said:
As an update to my original post, I did manage to successfully flash the kdz file using the "Upgrade" option in LGUP, and did not lose any of my data. However, I'm still getting the unlocked bootloader message when I start my phone ("Your device cannot be checked for corruption..."). Does anybody know if flashing the .kdz file causes TWRP to be replaced with the original recovery mode? I don't want to try to boot into TWRP in case it has been replaced, thus triggering a factory reset and losing all my data.
It ok to try and relock the bootloader now? (if so, how?) Or do I need to replace TWRP too?
Click to expand...
Click to collapse
You need to use LG Bridge to restore to stock. That will replace TWRP. Then you need to fastboot OEM lock.
If you don't want root and want to relock the bootloader to stop seeing that screen, you will lose data.
Sent from my LG-H918 using XDA Labs

Related

Get rid of shutting down after "device corrupt" message - so possibility to gain root

Get rid of shutting down after "device corrupt" message - so possibility to gain root
Some of you might face the problem that whatever you do anything you change on your device in order to gain root even if your bootloader is unlocked your device is turning off after promting "device corrupt, etc..." message.
Sometimes you can't even unbrick with lg bridge cos' it can't see that your firmware has any problems.
Typical symptom of this problem that very interestingly your phone is not showing any corrupt messages during normal boot up even if your bootloader is unlocked (it should write some warnig message at every boot up).
Also when you "fastboot boot yourstockbootimage.img" it's booting up but writing some network related error then shuts down saying corrupt battery.
In order to root your phone you must be able to change the firmware a bit (tweak the boot image).
First of all you need to unlock your bootloader if you didn't do it yet: http://forum.xda-developers.com/lg-k10/how-to/unlock-bootloader-lg-k10-mtk-devices-t3486302
All you have to do is allow modifications in TWRP step 2.1 here: https://forum.xda-developers.com/lg-k10/how-to/friendly-root-method-lg-k8-k10-t3531223
It means the rest written under is fully unnecessary but i keep it just in case the above mentioned method would not work for someone:
Other requirements:
- lg up working with your device: http://forum.xda-developers.com/lg-k10/how-to/flashing-firmware-using-lg-t3517839
- kdz firmware
- twrp recovery of your device (usually you can find it in your favorite root thread or somewhere on xda)
Extract boot image from your firmware with lg firmware extractor (http://viid.me/qe7ufH). First you have to extract the ".dz" file and then the boot image form that ".dz" file.
Once you have your boot image (eg. boot_157696.bin) rename it to "boot.img"!
Put this "boot.img" on your sd card!
Flash this firmware (that you taken your boot image form!!!) on your phone with LG UP.
Boot up and see if it works also tick all the necessary options (oem unlock in developer options, usb debug,...)
Reboot to fastboot, check if your bootloader is still unlocked ("fastboot getvar all"). If it's locked unlock it!
Boot into your TWRP (fastboot boot twrp.img), you can allow it to read system.
Go to "install" (tick install image) and flash your "boot.img" form your sd card (naturally onto your boot partition).
Now before you reboot make a full wipe (fastory reset) in TWRP (wipe menu) then you can reboot to system.
After the "device corrupt" message it must be booting on and boot up normally and during every boot up there should be that message.
Now you can go and root your phone - always use that boot image you just flashed during the first step of the root process (recompress this boot image to gzip and ... read a rooting guide: http://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807 there this should be "bootlz4_0.img")
There is no explanation why it works... wierd.
Hi.
I have this problem, corrupt device screen and continuous bootloops, I only have access to the download mode, but LG UP does not allow me to flash the .kdz even though I have the boot.img file on the sd card. It shows me the typical error at 9% of the process 'Error code = 0x81000304, CBasicFlash :: _func_LoadGptF - ErrorCode: 8222'. Would someone tell me what it is and how can I fix it?
I have tried to revive the cell phone in myriad ways and it is not possible for me.
I appreciate any suggestions.
Thank you very much.
Llony said:
I appreciate any suggestions.
Thank you very much.
Click to expand...
Click to collapse
This thread is not about bootloops but shutting down. Different subject. You should start a new thread about it.
However i looked at it, check out this comment:
http://forum.xda-developers.com/showpost.php?p=66135219&postcount=74
anyways if i were you i'd do a hard reset (http://www.hardreset.info/devices/lg/lg-k10/) and then i'd use lg bridge's update error recovery function (or you can change the order - first lg bridge, then hard reset).
Also make sure you chose "refurbish" when you use lg up and also make sure you are using the right kdz file (i recommend using lg mobile support tool to download your kdz - there is a possibility under options and upgrade recovery that using your imei it downloads the kdz to a hidden folder: http://forum.xda-developers.com/showthread.php?t=2395323)
I have bootloop with usb connected, without usb powered off
Llony said:
I have bootloop with usb connected, without usb powered off
Click to expand...
Click to collapse
I see... okay. However check out what i wrote above and one more thing: make sure you use usb 2.0 not any 3.0 ports.
I still do not find the solution, LG Up detects that it has installed the version k43010y, this version does not even exist! And I still give the error to 9% of the process. I do not know what to do to recover it
Llony said:
I still do not find the solution, LG Up detects that it has installed the version k43010y, this version does not even exist! And I still give the error to 9% of the process. I do not know what to do to recover it
Click to expand...
Click to collapse
Did you try lg bridge - update error recovery?
LG Bridge It does not give me the option to recover update error. And the LG flash tool before starting the process shows me 'contact the system administrator'. He does not let me get him back in any way.
Would it be possible to enter the fastboot mode through the download mode? So I guess I could try to flash an unmodified boot.
Thanks.
Llony said:
LG Bridge It does not give me the option to recover update error. And the LG flash tool before starting the process shows me 'contact the system administrator'. He does not let me get him back in any way.
Would it be possible to enter the fastboot mode through the download mode? So I guess I could try to flash an unmodified boot.
Thanks.
Click to expand...
Click to collapse
What do you mean it doesn't give you the option? I mean LG bridge, there is no update error recovery on the software update page? As in this video:
https://www.youtube.com/watch?v=b_GqAG02OXU

How to fix very bricked LG V20 from bad rooting?

jeanclaudevandamme said:
Right, I've figured out where things have went wrong but still can't find a fix
1) So after Step 14 after running the BAT files all cmd windows closed. I then clicked step3.bat while in fastboot mode. because he did not explain clearly where you were supposed to get CMD window for commands in Step 16.
I had used CMD / ADB / Fastboot years ago, but I had forgotten how they worked exactly, as the instructions for the previous phones I have rooted were so much better written.
later i discovered how to see what was inside a BAT file (use notepad to open it) so step3.BAT contained instructions to flash "boot1.img" which came with the Dirty Santa v20 files. I don't know what model that boot image was taken from. it also contained instructions to flash a twrp file name that didn't exist (so I guess nothing would have gotten flashed).
2) later I was able to launch into fastboot mode and manually flash the correct twrp file onto the phone. then led me being able to get into twrp recovery to flash kernel + SU.
However phone still didn't boot, presumably of the mistake was previously by clicking Step3.BAT, which flashed a "boot1.img" from dirty santa files
Also when going into download mode, the phone would crash with static 1 second after connection.
3) At the time, I didn't know the difference between aboot and boot files. So I went into fastboot and flashed abootbackup.img
I still don't know fully what aboot does. But the effect it has is it locked the bootloader, so i am no longer able to flash anything with fastboot. writing the old aboot.img has caused my device to go into a corrupt bootloop, cannot launch into recovery.
I think that if I flashed bootbackup.img then things might have worked out ok. i had 2 choices and I picked the wrong one, but that's gone now.
flashing the abootbackup.img also had another effect, download mode no longer crashed with static after 1 second, however a new error code came up when download mode is launched <633A B50>, the phone acts like a firmware is currently trying to be flashed but stuck at 0% even just by launching download mode.
I'm guessing there may be some sort of variant mismatch between the boot1.img and the abootbackup.img as the boot1.img wouldn't have originally come from my phone? As well as the other stuff pushed onto device in Step2.BAT
eithe way, LG Bridge / LGUP do not recognise model even with Uppercut.. LG Flash 2014 has the error messge of "connection to server failed", I tried letting it run in the background without closing error message as suggested in that thread, but I guess because of my 633A B50 error message, flashing did not occur in the background like other people.
----------------
I don't know where to go from here exactly. because
1) boot1.img, that came with dirtysanta files, which model / variant did it come from?
2) what LGUP_common.dll will recognise my device now? I know someone patched their DLL, but how do you patch a DLL using hex editor and how to make the DLL recognise my presumably mismatched device?
3) i don't know what the <633A B50> error message means exactly
------
https://forum.xda-developers.com/v20/help/help-h990ds-t3650303
looks like someone did something similar to what I did. he didn't get answers to his questions and he hasn't been logged in since August..
Click to expand...
Click to collapse
It's more bricked than usual..
Have a go at this?
I like using the LGUP Patched DLL for H91810J. It seems to recognize all variants.
as a last resort use LG Bridge, refurbish. it will repair all sorts of half installs and messed up partitions. the only thing is : IT WILL BRING YOUR BUILD UP TO 10q=================WHICH IS NOT ROOTABLE!!======================
Just in case this issue has not been resolved. I did the same thing 10 minutes ago. I flashed the wrong abootbackup.img (10c) instead of 10d.
All you have to do is open LGUP and if the device won't be recognise, just run the Uppercut tool and the device will show up. Flash your .kdz file and the phone should be running once again.

[UsU] [G4] UsU Removal and Relock TOT Method

UsU Removal and Unbricking Method for ARB 02 Devices
WARNING: THIS METHOD IS FOR DEVICES ON ARB=2 **ONLY**!!!!!
ANY DAMAGE DONE TO YOUR DEVICE FOR FOLLOWING YOUR GUIDE, IS YOUR RESPONSIBILITY! I AM NOT RESPONSIBLE IF YOU'RE DEVICE IS BRICKED DURING THIS GUIDE!
INFO:
While trying to fix my bricked LG G4 VS986, I accidentally figured out a method to fix a stuck on bootscreen firmware, and at the same time, remove UsU. Unfortunately, after messaging back and forth with SteadFasterX, he confirmed that this method will only work on ARB=2 LG G4's, Meaning that models H815, H812, H818, H819, F500 Will not work, and NEVER WILL WORK, at least not with this method.
That being said, your warranty is obviously already void if you have UsU, and if you don't, WHY ARE YOU HERE lol
Also, if you have a frankenstein device (device labeled and shown as a certain model, with a different model motherboard), I have no idea if this guide will work for you, although it did for my frankenstein device, at the loss of cell service. But no guarantees!
So lets get right into it!
REQUIREMENTS:
- UsU Bootloader Unlocked LG G4
- Your device must have a firmware available (doesn't have to be currently installed) with an ARB value of 2 ... Anything else, and your device WILL brick
- Patience and the understanding that if you brick your device, it IS NOT my fault
REQUIRED DOWNLOADS
- TOT file for YOUR device model (not our gpt compatible model, your model under the battery model)
You can find some tot files here (make sure you select the TOT FILE, not the kdz, or else this guide will not work): TOT Files
Or if you have the verizon variant, you can use the file i used, here
And if you can't stand the slow download speeds, look up Fshare premium link generator on google, and I never said that, mods (XD)
- LGUP and UPPERCUT tool (BOTH REQUIRED!!!)
You can download LGUP and the UPPERCUT tool from here
- QFIL and RESTORE FILES (I know, calm down)
You will need to download, as well as install, the qualcomm drivers, and a few unbrick firehose files, both of which can be found here
INSTALLATION:
Step 1:
Download and Extract the RAR file for your ORIGINAL (not GPT compatible) G4 model. For me, it was the VS986. I recommend you make a folder on your desktop, and extract all the files you download right to the root of it.
Step 2:
Download and extract the LGUP and UPPERCUT tool from the above Google Drive link, making sure to install the dll .msi installer, and then the LGUP setup.
Step 3:
Extract the UPPERCUT tool and navigate to the UPPERCUT.exe file extracted. Connect your phone in download mode by powering it down, then holding volume up while plugging the phone into your computer. Open the UPPERCUT.exe file, and wait for LGUP to show up
Step 4:
In the list of options below the list of connected devices, make sure that "PARTITION DL" is selected. Find the line below the list of options that says bin file. Double-click it, and select the TOT file you downloaded earlier. Click "Start", and when a window with a list of partitions appears, just tick "Select All" and click "OK"
Step 5:
The firmware should flash. If it throws an error out at you, double check that you selected "Partition DL", and that you have the LG Mobile USB drivers installed on your computer.
Once it is done flashing, your phone will be in a bricked state. DO NOT WORRY!!! We will fix this next
Step 6:
Your phone should go into Qualcomm HSUSB Dloader 9008 Mode after the flash is complete. This is what is SUPPOSED to happen, and means things are going in the direction they should be going in the process. Read on
Step 7:
Now download the QFIL files from the download link above. Extract them to the folder previously created on the desktop. Install the "INSTALL FIRST - DRIVERS.exe" file, then reboot your computer. Navigate to the "QFIL" folder, in the same directory as the file you just installed. Run "QFIL.exe", NOT AS ADMINISTRATOR, ELSE YOU WILL FAIL, and make sure your port is showing at the top. If it is not, click "select port", and click on the Qualcomm 9008 port, and click "ok". Under "Select Build Type", click "Flat Build".
Step 8:
Under "Select Programmer", click browse, and navigate to the "Unbrick LG G4 QFIL" folder in the same directory as the QFIL folder you extracted, and select the "prog_emmc_firehose_8992_lite.mbn" file. Then, under "Download", click "Load XML", and just click the first file in the window that pops up for each XML file it asks for (should be "rawprogram0.xml" first, and "patch0.xml" second). Once you select those files, click download. Wait for it to finish, it may take up to two minutes.
Step 9:
Once its done, you should see the LG logo on your device's display. Do not do anything, including moving the device, just to be safe, until you see the android setup screen. Once you see the android setup screen, your device may get stuck on "checking connection", just wait two minutes until the skip button appears, and you'll be good. If you want, you can now flash an official KDZ file for your device, as there may be some mods done to some of those TOT files, as I am not the creator of them.
Step 10:
That's it, you're done! Once you get to the setup screen, you are on your device's original firmware, and your bootloader is once again locked. If you found this guide helpful, consider thanking me and donating to me via paypal by clicking here
Don't forget to give this post a thanks if it helped you, and if you want to support me, donate to me via paypal by clicking here
jacoblong09 said:
WARNING: THIS METHOD IS FOR DEVICES ON ARB=2 **ONLY**!!!!!
I will be posting the UsU removal/relocking process in a couple hours, stay tuned!
Click to expand...
Click to collapse
Reservation.
I am not seeing PARTITION DL ? ALLI see in Process are 4 options : Upgrade, PRL Update, PHONESETTING and FOTA Upgrade?
seanwarez said:
I am not seeing PARTITION DL ? ALLI see in Process are 4 options : Upgrade, PRL Update, PHONESETTING and FOTA Upgrade?
Click to expand...
Click to collapse
did you use the UPPERCUT tool to open LGUP, rather than using the regular lgup shortcut? That's the only way to make the PARTITION DL option appear. Make sure you also have installed the lgup dll .msi setup program before running uppercut. let me know how it goes
there are dangerous and non- trustable qfil files on web be carefull your devices my convert to ls991 or f500l!! (because mine was before)and never back to network connection again
floast said:
there are dangerous and non- trustable qfil files on web be carefull your devices my convert to ls991 or f500l!! (because mine was before)and never back to network connection again
Click to expand...
Click to collapse
Hi, my lg g4 811 converted to ls991 too, how did you get out of yours
jacoblong09 said:
did you use the UPPERCUT tool to open LGUP, rather than using the regular lgup shortcut? That's the only way to make the PARTITION DL option appear. Make sure you also have installed the lgup dll .msi setup program before running uppercut. let me know how it goes
Click to expand...
Click to collapse
Actually the files you posted have some KMS threats, according to my AV sw anyway.
https://forum.xda-developers.com/showpost.php?p=73051003&postcount=32 allows me to have a patched dev Lgup. I even do not need to do anything to unbrick! It was not bricked and I was back to the rooted stock LP, unUsUed in 1 step, using the patched LGUP dev and your tot file, flashed using Partition DL, well at least it worked for my VS986.
using uppercut all i have is the 4 normal settings . If i patch the dll i get the rest but lgup.dll .0.3.2 will not finish flashing stops at 16% (boot). reinstall lgup and extract Lg-up.dll .0.0 .4 from vs9862ba.kdz, lg up flashes fine with the 4 settings but when patch is applied it states *unknown .dll version*.
help please
SatGator said:
using uppercut all i have is the 4 normal settings . If i patch the dll i get the rest but lgup.dll .0.3.2 will not finish flashing stops at 16% (boot). reinstall lgup and extract Lg-up.dll .0.0 .4 from vs9862ba.kdz, lg up flashes fine with the 4 settings but when patch is applied it states *unknown .dll version*.
help please
Click to expand...
Click to collapse
It is way deeper than that, what you have to do is download the firmware, extract it into a folder then flash all the key components via adb, that worked for me.
flashed the VS98613B_Fix_Global_by_Lamlazy .tot it did not brick my device .. simply installed and powered on...
If i understand. qfil files for F500 available??
So it means F500 can be un unlocked right?
post #5 says device may converted to ls991 or f500.
I think that F500 is still non fusing device even after USU. So it can flash ARB 0 KDZs. I'm bit confused???
[email protected] said:
If i understand. qfil files for F500 available??
So it means F500 can be un unlocked right?
post #5 says device may converted to ls991 or f500.
I think that F500 is still non fusing device even after USU. So it can flash ARB 0 KDZs. I'm bit confused???
Click to expand...
Click to collapse
Never ever mess with qfil unless you understand fully the technical details about how this tool is working and how ****ing dangerous it is to use it. There are no valid files for your model available so even when they are named for the f500 I can't say it often enough do not use it! Also as already said in the other thread your device arb and non fusing has nothing to do with the model number as it's not that easy.
You can unlock your device by UsU and when you have a fusing device like 90% have than you can't relock afterwards
Sent from my LG-H815 using XDA Labs
after relocking using this method can re-usu-unlock be achieved again ?
Deleted
Deleted.
pls can anyone share the download links? above link is broken thanks.

LGUP Login Info

I must be missing something super basic here, but when I start LGUP it asks for my login info. So I put in my LG Developer login (made when unlocking the bootloader) but it's not accepting it. Registering through the software doesn't work either, it says my ID (email or the nickname) is not registered on "GDMS" or the "LGUP Certification System". Not sure how to proceed?
I'm trying to get back to stock in a desperate attempt to get Google Pay working. I've flashed a stock LG image and the stock recovery, but no luck yet. Hoping that using LGUP I can flash the official kdz file and that would solve the issue.
Edit: found. For any future googlers, I used [this](https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/) link.
* Download LGUP 1.14
* Install it
* Move everything in the Patch folder to the installation directory, overwriting all files
And that's it.

LG VS995 Only boots to LG screen and vibrates -- Help needed please

OS - Windows 10 Enterprise N LTSC 64-bit
How I got here:
Rolled back to 2016 build using LGUP (store, patched).
Used dirtysanta to unlock bootloader and install TWRP.
On first boot, I got static and a constant buzz from the haptic feedback motor.
Not knowing that Verizon users sometimes need to wait over 20 minutes, after 10 or so I assumed I was toast.
Tried to flash NotYetADev's Oreo build with the same result. (https://forum.xda-developers.com/v20/development/vs995-verizon-lg-v20-stock-oreo-rooted-t3845669)
Attempted repairs:
Tried LG Flashtool using dksoni411's method (https://forum.xda-developers.com/v20/how-to/guide-lg-v20-to-life-t3827732) and it failed to work.
Now LGUP is not working. Changes between "not recognized" and "wrong DLL" depending upon LHUP_common.dll version.
Uppercut ran after disabling A/V but didn't work and required a system restore to get Windows back to a normal state.
Flashing several alternate kernels doesn't fix.
Flashing LineageOS, same thing.
What's still working:
Download Mode
Fastboot Mode
TWRP
Notes:
I have the original files from the first LGUP dump.
Looking at the build.prop from the TWRP terminal, each flash appears to be successful but still hangs at the LG "Life's good" screen.
I am kind of at a loss as to how to proceed. I have some reservations pushing aboot or any other files via fastboot as I don't want to risk a hardbrick condition. Any assistance would be greatly appreciated. I can spinup a VM if needed to run Uppercut. I am not going down that road again...
Update:
Installed all software, drivers, etc. in a Windows VM. Same results. Uppercut still fails to work with LGUP...
Out of desperation, I flashed bootbackup.img to the device. No change.
Anyone? Anyone? Bueller?
It appears that TWRP is not flashing the system partition even though it is mounted.
Anyone?
You don't need uppercut. Remove it. You need lgup patched working. Do that first. Trial and error I recall with dll file. Just keep trying. Forget virtual machine. If you don't need Verizon firmware you can use US996 and then dirtysanta. Vibrator issue is with verizon firmware only.
Sent from my LGE LG-US996 using XDA Labs
Posting an updated request in another thread as no help is forthcoming here.
if i remember correctly it has to do with dirty santa step 3 where you install twrp and need to type
"adb reboot recovery"? this step almost screwed me over... you actually dont need to wait for vibrate to stop to boot in twrp, wait 5mins then type the adb command, and it will reboot in recovery...
Thanks for the reply.
I got LGUP (patched) working again on a clean virtual machine. My work PC is very loaded with software and I wanted to avoid driver conflicts. Sadly, the original KDZ dated December 2016 that I first flashed won't work now. It throws a "wrong model" error likely caused by my using the LG flash tool and it failing to complete the flash.
It turns out that my file system was hosed but I managed to fix that in TWRP. Rather than try and use fastboot to flash the files individually from the original LGUP dump, I am making a TWRP flashable zip. Hopefully, that will work.
If I can get it back to stock, I am confident that I can get it going. My main screwup was not waiting long enough on the first rooted boot (static screen, and vibrate). I now have a kernel to flash that is supposed to fix that. I have a bad feeling that I will need to revisit the LG Flashtool and correct those errors before anything will be resolved.
More information in an updated thread here:
https://forum.xda-developers.com/v2...anta-bootloader-t3519410/page400#post81065413

Categories

Resources