Database Users

Stock Recovery, No Root, Model Number Prevents Flash To Stock

Over the years I've always been good at solving these things, but this is the first time I've every had to request help/guidance.
LG
1. Came from from 4.4.2, ioroot rooted, installed twrp via freegee, but not the kernel patch. This prevented me from booting back into Android.
2. Factory reset everything, wiped everything from twrp.
3. Ran adb commands here:http://forum.xda-developers.com/showthread.php?t=2451696 Got me into fastboot.
4. Flashed all .img files for LG D800 from prime's D800 img stash. Fastboot rebooted.
5. Installed Mahndi ROM via adb. Reboot
6. Stuck. Phone hangs on LG logo, loading modem and com drivers in windows. Recovery is now stock, so no flashing. Download mode works but always get a "Device Model is different" error at 0% when flashing from LG Flash Tools. Correct .tot and correct .dll for D800.
Any help or ideas to get my G2 up and running again would be amazing. I'm still trying to figure out if I can modify the .tot to match my device's current model or just ignore it and overwrite (best hope). Even if i can get ubuntu to detect the phone that would lit my spirits.
Thanks.

Progress
So I have actually figured out the problem completely, yet I do not yet have a solution.
-I after flashing the correct .img over to my device, I was all set to go, but read somewhere about flashing over mahdi ROM.
-I successfully flashed Mahdi, but DID NOT FLASH THE DEVICE VERSION PATCH (literally hit my head on the desk when I realized).
-I panicked after it did not work and reflashed all the .img so I was stuck with stock recovery, no adb, no sideload, no fastboot.
Is there ANY WAY to flash back to stock with the LG Flash Tool for the ATT D800 that ignores the model number inconsistency. This type of phone only supports the .TOT method of flashing. There is no other way (KDZ = NO). Currently my device's build.prop says that the model is "g2" (this is what the patch was supposed to fix) and my flashing file/.dll is for "D800".
My device can not be seen in Ubuntu.
Any suggestions?

datdude_tc said:
So I have actually figured out the problem completely, yet I do not yet have a solution.
-I after flashing the correct .img over to my device, I was all set to go, but read somewhere about flashing over mahdi ROM.
-I successfully flashed Mahdi, but DID NOT FLASH THE DEVICE VERSION PATCH (literally hit my head on the desk when I realized).
-I panicked after it did not work and reflashed all the .img so I was stuck with stock recovery, no adb, no sideload, no fastboot.
Is there ANY WAY to flash back to stock with the LG Flash Tool for the ATT D800 that ignores the model number inconsistency. This type of phone only supports the .TOT method of flashing. There is no other way (KDZ = NO). Currently my device's build.prop says that the model is "g2" (this is what the patch was supposed to fix) and my flashing file/.dll is for "D800".
My device can not be seen in Ubuntu.
Any suggestions?
Click to expand...
Click to collapse
over here http://androtransfer.com/AndroidUser00110001/ROM/G2/KK/D80220a/ there is a dll named lgup_8974.dll which is for d800 and is supposed to skip the model check

datdude_tc said:
Over the years I've always been good at solving these things, but this is the first time I've every had to request help/guidance.
LG
1. Came from from 4.4.2, ioroot rooted, installed twrp via freegee, but not the kernel patch. This prevented me from booting back into Android.
2. Factory reset everything, wiped everything from twrp.
3. Ran adb commands here:http://forum.xda-developers.com/showthread.php?t=2451696 Got me into fastboot.
4. Flashed all .img files for LG D800 from prime's D800 img stash. Fastboot rebooted.
5. Installed Mahndi ROM via adb. Reboot
6. Stuck. Phone hangs on LG logo, loading modem and com drivers in windows. Recovery is now stock, so no flashing. Download mode works but always get a "Device Model is different" error at 0% when flashing from LG Flash Tools. Correct .tot and correct .dll for D800.
Any help or ideas to get my G2 up and running again would be amazing. I'm still trying to figure out if I can modify the .tot to match my device's current model or just ignore it and overwrite (best hope). Even if i can get ubuntu to detect the phone that would lit my spirits.
Thanks.
Click to expand...
Click to collapse
I have almost the exact same problem will keep an eye on thread, hope we git it sorted soon!

I'll Take a look
XxZombiePikachu said:
over here http://androtransfer.com/AndroidUser00110001/ROM/G2/KK/D80220a/ there is a dll named lgup_8974.dll which is for d800 and is supposed to skip the model check
Click to expand...
Click to collapse
Thanks!
I have seen and downloaded that one before, and if I recall correctly, I didn't get a model error, but rather something else. I believe it was a bin file error??, but I do not recall. I actually just sent my G2 in on a warranty claim (*please oh please don't notice I replaced the screen") and hopefully that will take care of it. I was just posting so that maybe someone doesn't have to dig through 350 pages of replies to find out what happened. I'll keep the post going when I find anything out though.

Working together!
MRobbo80 said:
I have almost the exact same problem will keep an eye on thread, hope we git it sorted soon!
Click to expand...
Click to collapse
I won't have my phone available for a few days. Any chance you could go ahead and give that lgup_8974.dll a test run and report back? I'd be more than willing to help do any research if it gives a different error besides the model.

Sorry to dig up this thread, but I have the exact same problem, except I flashed mahdi on my D802 and somehow the version patch didnt flash correctly. Is there anything like a lgup_8974.dll for D802s?
I'm really desperate here.

i have the exact same problem!!
Any solution found yet??

HELP!!! My LG V20 Says Firmware Update And Won't Load

I just purchased a LG V20 for $150, but it has one problem. It says Firmware Update now waiting for any connection. It has an error code or something below it with 633A B50. I can only go into a few of the boot menues. I can't turn on ADB, and i can't access recovery or download mode. WHAT CAN I DO, PLEASE HELP.

tms1003 said:
I just purchased a LG V20 for $150, but it has one problem. It says Firmware Update now waiting for any connection. It has an error code or something below it with 633A B50. I can only go into a few of the boot menues. I can't turn on ADB, and i can't access recovery or download mode. WHAT CAN I DO, PLEASE HELP.
Click to expand...
Click to collapse
If it says Firmware Update, then you are in download mode. If you have pretty much anything other than an AT&T, or Sprint model, you should be able to get a KDZ or use LG Bridge. If there is no KDZ for your phone, then it is a brick.
-- Brian

runningnak3d said:
If it says Firmware Update, then you are in download mode. If you have pretty much anything other than an AT&T, or Sprint model, you should be able to get a KDZ or use LG Bridge. If there is no KDZ for your phone, then it is a brick.
-- Brian
Click to expand...
Click to collapse
It is the sprint ls997 variant so no .kdz file as of currently. ADB is not connecting, but i can get LGUP with uppercut to recognize the device in download mode. I don't believe the boot loader is unlocked, but is there anyway i could use LGUP to push a .kdz file for a different variant (I tried the Verizon variant and it failed because it recognized i was trying the wrong variant) which would allow me to boot into a OS and turn on debugging and from there use Dirty Santa? Basically is there anyway to let LGUP push the wrong .kdz variant?

Have you tried the LG Flash tool? I know there are some patches that will allow it to flash without checking the model. Since you have a brick already, you have nothing to lose. If it were me, I would try every V20 KDZ that is out there in the hopes that one of them would boot. If you can get it to boot, then you can use dirty santa, and you will have a working phone again. On the plus side -- you got a great deal for $150.00. You can always hop on Ebay and find a system board to swap in.

runningnak3d said:
Have you tried the LG Flash tool? I know there are some patches that will allow it to flash without checking the model. Since you have a brick already, you have nothing to lose. If it were me, I would try every V20 KDZ that is out there in the hopes that one of them would boot. If you can get it to boot, then you can use dirty santa, and you will have a working phone again. On the plus side -- you got a great deal for $150.00. You can always hop on Ebay and find a system board to swap in.
Click to expand...
Click to collapse
what patches of LGUP will allow to flash without checking model?
I am having this trouble too. but i bricked mine trying to root it

there was a post on lg viet forums where they converted a ls997 to a Korean model, it had no service but after flashing the sprint modem,it worked perfectly. just look for patched lgup first.

jass65 said:
there was a post on lg viet forums where they converted a ls997 to a Korean model, it had no service but after flashing the sprint modem,it worked perfectly. just look for patched lgup first.
Click to expand...
Click to collapse
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
Do you mean this? My LGUP never worked even before brick, so I already had to use this patched exe and dll file to even roll back to older firmware for dirty santa root in the first place.
Now after running step3.bat and flashing saved aboot img, the phone is locked out if recovery and download mode shows 633A B50 and patched LGUP / DLL no longer recognise device. Uppercut also doesn't recognise device. LG Flash 2014 also failed so did LG Bridge

jeanclaudevandamme said:
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
Do you mean this? My LGUP never worked even before brick, so I already had to use this patched exe and dll file to even roll back to older firmware for dirty santa root in the first place.
Now after running step3.bat and flashing saved aboot img, the phone is locked out if recovery and download mode shows 633A B50 and patched LGUP / DLL no longer recognise device. Uppercut also doesn't recognise device. LG Flash 2014 also failed so did LG Bridge
Click to expand...
Click to collapse
no not that, this http://lgviet.com/forum/threads/huóng-dãn-up-rom-bản-hàn-cho-các-máy-mỹ-lg997-us996.66261/
but i guess you cant even get into download mode or have root.

jass65 said:
no not that, this http://lgviet.com/forum/threads/huóng-dãn-up-rom-bản-hàn-cho-các-máy-mỹ-lg997-us996.66261/
but i guess you cant even get into download mode or have root.
Click to expand...
Click to collapse
well i can get into download mode, but there is error 633A B50 which stop it from doing much useful
i can also launch into fastboot, though it's locked and fastboot flash commands no longer work

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.

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

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

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