yashsingh1/xdaforums huggingface dataset:
[LG V40 Guides, News, & Discussion] SuperMike393:
Hi, me again. Im trying to unlock my LM405UA still. Im using the updated QPST/QFIL install and im still unable to get to the partition manager. Once i hear the EDL connect to my pc im clicking partition manager in around under a second. When you click partition manager is it supposed to load for a while or should it be instantaneous? In the guide it shows him with rawprogram0.xml should I have that from somewhere?

https://i.imgur.com/xjwy1ba.png
[LG V40 Guides, News, & Discussion] Clearlove2407:
I could not get the files rawprogram0.xml . Please
[LG V40 Guides, News, & Discussion] cogpie:
It should be pretty quick, in my experience. Any time it took more than a few seconds it would usually fail with the Sahara error. From the moment Windows Device Manager registers the device, try to have QFIL loaded and ready to go. That said, I still found it wouldn't connect all the time, and had to keep at it, although I put this down to largely trying to do things through a Virtual Machine running Windows 8.1

This is not needed - please ignore this part of the image in the guide. [MENTION=5796697]Xsavi[/MENTION] did a good job of revamping the guide, if they have a bit more energy maybe they could just put a white box over that part of the image to save others confusion too. Thank you
[LG V40 Guides, News, & Discussion] Clearlove2407:
I'm sorry. But I couldn't find any firmware version similar to the firmware version of my current to get the files rawprogram0.xml . If you know about it please help me. My current firmware is V405UA11e
[LG V40 Guides, News, & Discussion] SuperMike393:
Thanks for being patient with me and guiding me through, i appreciate it. I've just tried this on a separate win 10 laptop (with updated everything) and im still getting sahara. What does this error come from (9008 usb driver, the phone itself, QFIL, etc). I am trying to figure out why this is happening when most other people didnt seem to have nearly as difficult time as I am right now. For clarification does it matter that I flashed oreo to my device? The guide said if the device doesnt have OEM then you need to flash v35 engineering bootloader and to have engineering bootloader i need to be on oreo. The version i got is 8.1.0. Again thanks.
[LG V40 Guides, News, & Discussion] Infy_AsiX:
I can't seem to run fastboot commands on my Australian model, except the oem unlock first. Even nuking the laf's for fastboot didn't help. I ended up relying on EDL for putting TWRP into boot to install LOS.
[LG V40 Guides, News, & Discussion] teesby:
will this method sim unlock a LM405UA V40 model
[LG V40 Guides, News, & Discussion] Infy_AsiX:
it's for bootloader unlocking
[LG V40 Guides, News, & Discussion] Arian420:
I want to know . I am on Android 10 . Which abl i should flash .abl stok pie or abl10? I am on varizon verson android 10
[LG V40 Guides, News, & Discussion] AsItLies:
You should **always** back up any partition you flash over, so that you can restore it if something goes wrong or you want to revert back to original.

Partitions are not 'interchangeable' between carriers and os versions. I mean you **might** get lucky and one will work, but odds are they will not.

the reason the guide has and says what it does is that's what xsavi was using at the time he wrote it. It's that simple. If yer not using the exact same carrier and os version, then use yours, not his.

cheers
[LG V40 Guides, News, & Discussion] AsItLies:
@con_ritmo wrote

Hello!

I just purchased a v40 and would like to unlock the bootloader/twrp/magisk it.

My v40 is att v405ua30c on android 10. So i figure it's 10c?

I noticed that you mentioned in the v40 unlock thread that you need a specific bootloader for android 10...and provided a link to download 10e injected with twrp.

Where would I be able to find a 10c bootloader injected with twrp?

Thank you for any help you can provide!

Regards

So, the naming conventions LG uses can be a bit confusing, but android 8 was v405ua10x, and android 9 is v405ua20x and android 10 is v405ua30x. The 'x' signifies updates, which are usually just security patches.

your v40 is att v405ua, the 30c indicates the OS version. That's the boot partition with twrp that you want, the one for att 30c.

this is the link to that one, att 30c.

cheers
[LG V40 Guides, News, & Discussion] PetiaWarzel:
The portable QFIL Tool will not work. Instead, install the QPST Tool, then open the QFIL Tool that was shipped with the QPST Tool.

Latest QPST Tool- https://qpsttool.com/category/download
[LG V40 Guides, News, & Discussion] AsItLies:
You've certainly learned quite a bit from your experiences, that's good, doing is what helps us learn.

I'd clarify a few things though for people thinking about doing this. Your A and B sections are basically Windows and it's related problems. Really, we all have to go through that no matters what.

The C section I'd point out: If you already have a boot partition with twrp injected (which u did, see my post above), then there's no need to use the bootable-twrp, just use qfil to flash the mentioned boot-twrp and go directly to recovery from qfil.

Then, once in twrp, format data, reboot recovery, flash magisk and dm-verity. Then yer done.

I'd also clarify that the v35_eng.abl is the only version of fastboot that's really needed (you don't have to erase laf partitions). And the only thing it's really needed for is to 'fastboot oem unlock' (if you plan on blanking vbmeta then it's needed for that also). But other than that, you're essentially done with it.

You can erase the laf and get a 'watered down' version of fastboot (when u use key combo for DL mode), but it varies from rom to rom what functionality this version has, and none of the versions allows unlocking bootloader (thus the need for v35_eng). But, keep in mind, you'll loose download mode until you flash the original laf partition back, if you do this.

cheers
[LG V40 Guides, News, & Discussion] con_ritmo:
You are absolutely correct Asitlies!

I could not get the fastboot on my phone up when connected to my main computer. As it turns out it's an issue with that specific computer. The nuking laf was to eliminate the "user error getting into fastboot" part of the problem and just get fastboot no matter what. Once I saw that the problem still persisted, I moved on to another computer and all went well.

Unfortunately the injected bootloader twrp didn't work for me...the phone hung on the V40 splash screen. This was done with QFIL...maybe if I had fastboot flashed it would've worked? Maybe if I had waited longer the boot wouldve gone through. At that point I figured since I was going to fastboot anyway I just decided to do the twrp process too.

I appreciate all your help Asitlies...you've been keeping this forum alive with your expertise!!! Couldn't have done it without your posts.
[LG V40 Guides, News, & Discussion] jameasdf02:
My OEM unlock missing pls can somebody help me
[LG V40 Guides, News, & Discussion] zeuskrap:
i just stock on the red triangle !!

cuz no one write that i should take backup abl_a !

i need help guys i have no one around to help me
[LG V40 Guides, News, & Discussion] zeuskrap:
anyone with back up abl_a

please send it and tell me the way to appear again in QFIL

please i just can't hold my self
[LG V40 Guides, News, & Discussion] AsItLies:
That's because your rom is probably Verizon. The directions on the first page says to flash frp in that case. cheers
[LG V40 Guides, News, & Discussion] AsItLies:
You get the red triangle when you have mis-matched partitions. First, in any situation like this, when you are destroying a partition by writing over it, you should **alwyas** back it up first... it's just common sense.

and no one can provide u with abl_a if they don't know the version and variant you're running. Is it AT&T? Verizon? Which version of android? 10c? 20e? 30d?

these partitions are not interchangeable.

cheers
[LG V40 Guides, News, & Discussion] zeuskrap:
Is it At&t Yes
[LG V40 Guides, News, & Discussion] AsItLies:
at&t android 8? at&t android 9? at&t android 10?

and...

which version of 8? or 9? or 10? The versions are incremented by a, b, c etc etc.

go to 'about phone' in settings, look at software version information.
[LG V40 Guides, News, & Discussion] zeuskrap:
i've tried somethin and now the phone blacked out !

any way to shows again in Device manager ?

it's android 9 pie at&t version
[LG V40 Guides, News, & Discussion] AsItLies:
hahah wish I could help more but it's kind of impossible...

u tried something? what did u try? to put it in edl mode? I have no idea, sorry, my crystal ball is broken ;)

any way to show in device manager? yup, but you have to know what 'mode' the phone is in, edl? fastboot? lgup?

android 9 at&t, okay, not sure how may versions of 9 they had, but I know there's one backup around. I'll look for it.
[LG V40 Guides, News, & Discussion] Alibaba0101:
Thanks!

can qfil be used to apply the twrp image to laf_a and laf_b?

How did you boot back to fastboot after reapplying the original abl_a and abl_b? I assume you had to reapply the engineering bootloader, access fastboot, restore abl_a and abl_b and then fastboot boot to twrp.img?

Also, I'm getting just a splash screen when i fastboot boot judypn_TWRP_bootable-metadata.img and it does not boot into twrp. Any help would be appreciated :)
[LG V40 Guides, News, & Discussion] laminarturbulent:
Well, I think I hard bricked my V405UA (originally ATT 30e). I tried doing the guide written by con_ritmo for 30c and it gave me the red triangle with "all slots are unbootable."

After restoring abl, boot, and laf with QFIL, it still gave me the red triangle with unbootable error.

At this point, I can think of a few things that might have caused it:

I turned on "Enable OEM unlock" and went straight to EDL without one full reboot

There's something about 30e that breaks stuff

I used a USB 3.1 type C to type C cable

I was able to go into EDL/9008 mode at this point as well, but then everything went wrong when I tried unlocking again by:

Flashing the V35 bootloader to abl

Not erasing laf

Doing the fastboot oem unlock stuff (it would say unlock failed the first time then an error about it already being unlocked)

Flashing this 30e TWRP boot image to boot

That got me to where I am now. It seems like my V40 can go into fastboot (stuck on V35 fastboot) and EDL/9008 mode but none of the computers I've tried are detecting it over USB (no Windows sound, nothing in Device Manager or USBTreeView). So I don't know what I can do now besides try to replace the USB-C port (which may not even work if it's something else in the hardware that's broken).

EDIT: Forgot to mention that it draws 450 mA over USB so at least the power lines aren't broken.
[LG V40 Guides, News, & Discussion] AsItLies:
First, it's highly unlikely it's hardbricked. Actually, it's almost impossible to do with a v40 (with the tools we have for it).

The red triangle (all slot unbootable) means u have mismatched partitions on both slots. For the device to be recognize by windows, it's absolutely the best to use a usb 2.0 port, if possible. Also, windows has to have drivers installed for it to recognize the device in BOTH adb AND fastboot (you can't just install a driver for one and the other will work, it has to be installed for both).

So if you can use edl (or fastboot) to flash the original laf, abl and boot partitions back, you should be able to boot okay.

If not, try the following (from tele group) (this will essentially get lgup to work, but then you will need to flash a kdz and start fresh again).

Flash V35 BL to both abl_a and abl_b

Unlock BL

Go back to qfil

Flash abl, laf, dtbo from here: lgup_recover to both a and b slots

Reboot to download mode

Flash kdz

Note, not all carriers allow their kdz to public. At&t and Sprint most notably. This becomes an issue especially if u are sim locked to one of them, because u have to use their rom to unlock the sim (no other way)... so in that case you'd have to dig around for a backup someone made from qfil of either of those.

cheers
[LG V40 Guides, News, & Discussion] laminarturbulent:
Unfortunately even using a USB 2.0 port did not work. I don't have much hope for it since I was able to connect over fastboot and EDL previously but it currently won't connect over USB at all.

I even tried putting it in the freezer in case the issue was something similar to what happened with the good old Note 4, but that only made it draw ~140 mA while it was cold instead of ~450 mA, still no indication of connecting on either of my computers.

What I can see/access right now is:

1. "V40 ThinQ Powered by Android" boot screen, then goes immediately to red triangle (specifically this time there is no "all slots are unbootable" message), then to V35 fastboot:

2. EDL mode (I think). I hold power + volume down while in fastboot and then rapidly push the volume up button. If timed right it goes to a blank screen instead of rebooting to option 1 (V40 boot screen etc.).

3. A circle with a lightning bolt (presumably the charging screen) shows up momentarily -> red triangle -> V35 fastboot.

4. Factory reset screen (tried resetting, it didn't change anything)

Maybe there's some magic key combination or something to be discovered in the future involving a microSD card (if it's even a software problem, perhaps some chip or fuse blew and that's why it won't connect over USB) but I think my V40 is now a fancy paperweight/parts phone. At least it was less than $100!
[LG V40 Guides, News, & Discussion] AsItLies:
Obviously the phones not dead, it's just not booting. It's possible the usb port has gone bad, some say using a q-tip and isopropyl alcohol to clean it helps.

Be sure, in device manager, that you don't have anything with a '!' symbol (like android, etc), as that would mean a driver problem. I know you said it was working before, but check that again as windows can be very finicky.

Does the pc see the device using lgup? (device off, hold vol up, plug in usb cable). Yeah the usb problem needs to be figured out first. Seems possible, given the price u paid, it might have been bad to begin with and only worked intermittently?

cheers
[LG V40 Guides, News, & Discussion] xv6700redfred:
I'm wondering if anyone can help me.

This is what I did step by step to screw up my phone.

Using qfil:

1. Used the "read" option to back-up the partitions of abl_a, abl_b, boot_a, boot_b, laf_a laf_b.

I located the partitions and named them accordingly.

I tried to follow the tutorial on page 30 of this form and failed to get past the bootloader unlock.

Used these codes:

astboot getvar all

fastboot oem unlock

fastboot --set-active=a

fastboot flash abl_a c:\original boot file here\abl_a.img

2. Erased the 6 partitions above.

3. Tried to restore the 6 partitions above, rebooted and I get a very dim error screen.
[LG V40 Guides, News, & Discussion] AsItLies:
I understand that sort of thing happens when you bork the partition table, usually by flashing an image to a wrong partition (the image is too big so it overwrites whats near it).

From the tele group the solution is the v40unbrick:

-------------------

v40unbrick:

Download (https://drive.google.com/drive/folders/1WQaaM35SWiF_UbXAM8hiRB95D2CDkIEq) the backup. Unzip it to find 7 luns (0-6).

1. Open QFIL

2. Select Flat Build

3. Click load xml and select the rawprogram(#) XML that is in the lun(0-6) folder.

4. If it asks you for a patch xml, click cancel. It's not needed to flash this backup.

5. Click download

6. Repeat steps for each lun folder.

---------------------

that will at least get the phone working again, but I think the backup is at&t pie (not positive). None the less, you'll then be able to flash a kdz of your choice or find a newer backup of at&t or sprint if that's what u want to use.

cheers
[LG V40 Guides, News, & Discussion] xv6700redfred:
Thank you for your help on this I really appreciate it!

Ok so I didn't tell you the whole story. Lol

I did load the wrong backup file in fastboot with the "fastboot flash abl_a c:\original boot file here\abl_a.img"

there was an error code that said "data overflow" or something like that.

Then I went back into qfil and deleted all 6 of the partitions (noted in the above post) and proceeded to flash back the back-up partitions not knowing that I was loading them to the wrong partitions. 2 out of the 6 said the same error "data overflow" and I proceeded anyways. Once I found that I had labeled the back-up wrong I was able to load the correct back-up .bin files to the correct partition.

That's when I got the dim error screen upon reboot.

Fyi My phone is Lg v40, Sprint, Pie 9.

I will follow you instructions, thank you!
[LG V40 Guides, News, & Discussion] xv6700redfred:
When I load all 7 xml files as you described above will this overwrite everything on the phone?

Like a dumbass I didn't save my imei number. Ugh...
[LG V40 Guides, News, & Discussion] AsItLies:
it shouldn't but always, before overwriting a partition, save it. In this case, the critical partitions (that have imei and serial) are ftm, fsg, modem, modemst1 and modemst2. Save those just in case you have to flash them back after doing the restore.

one thing that happens with doing a restore like this is after ea xml (lun), pretty sure it will need to be put back into edl mode ea time. Kind of a pain. Also, if one of the lun restore doesn't restore anything, not a big issue (I think there are actually 2 of them that do that).

finish them all, none the less, then it should boot.

cheers
[LG V40 Guides, News, & Discussion] xv6700redfred:
Hello again, sorry for all the hand-holding here. I'll figure this out soon I'm sure. I loaded all the luns, Lun 0 failed to load. I then loaded back the Fsg, Ftm, Modem_a, Modem_b Modemst1, Modemst2. Nonetheless things are looking up. I was able to get into fastboot and also retrieve my IMEI number. But the phone will still not boot. I get a red triangle error on the screen and the phone automatically reboots after some time. Any idea on what could be going on?
[LG V40 Guides, News, & Discussion] AsItLies:
You shouldn't need to reload those partitions. Just have them in case your IMEI disappears, but it probably won't. I'd say do the luns again and it will probably be okay.

Cheers
[LG V40 Guides, News, & Discussion] xv6700redfred:
I tried to load them again, the only one that would not load is Lun 0. I reboot after and still have the red triangle error.

Any ideas? If not no worries I will keep messing with it. Cheers!
[LG V40 Guides, News, & Discussion] AsItLies:
Well a red triangle means partition mismatch. So somehow they are still not all of the same version.

I'd suggest this, flash the files from this link (not the boot one with twrp in the name). This should hopefully give you lgup (download) ability.

After flashing them with qfil, exit edl with holding vol - and the pwr button, after windows chime, just hold vol up (and of course leave usb plugged in).

That should then bring you to lgup download mode and you can then flash a kdz. I'd suggest go with the US Open Pie (there is no Q version). When flashing the kdz, first do it with partition D/L mode, select all partitions but ftm. Then, after it reboots and finishes, turn off, enter lgup mode again, and do a 'refurbish' with the exact same kdz you just used for D/L mode.

So, at this point anyway, yer gpt table error is gone, you've got backups of critical files (in case they are needed - **if** imei disappears), and with the above you should get download mode.

yer not that far away from having it being fully functional again. give it a go.
[LG V40 Guides, News, & Discussion] gcwct71513:
Need Help. I did this on a LG V40 ThinQ (android 10, att) and it keep booting in EDL.
[LG V40 Guides, News, & Discussion] silverrose:
Hey everyone!

First, Thanks for posting this guide and all the help you've given others, and me, as I try to figure this out.

Still having trouble with fastboot, but that's not the point of this post.

This post is to say what I think will fix the dreaded Sahara Error once and for all. At least it did for me.

Go into Firehose Configuration (under configuration) and check the box next to "DOWNLOAD PROTOCOL SAHARA" that says "Reset State Machine" in the upper left corner.

Once I did that, I connected no problem. I tried clearing the check box, and immediately had problems again. Checked it, and back in.

Hopefully this works for you, and if it does, let me, and more importantly, others know! Good luck, and happy rooting.

PS. Don't worry, I'll probably be back with questions on why my fastboot keeps crashing... O_O

Edit: Fixed the fastboot issues by using an older PC. Now where do I go from here? Install TWRP and then custom ROMS?
[LG V40 Guides, News, & Discussion] AsItLies:
follow what's in this post.
[LG V40 Guides, News, & Discussion] gcwct71513:
They all say "Download Fail:Sahara Fail:QSaharaServer Fail: Process fail"
[LG V40 Guides, News, & Discussion] AsItLies:
When you get a sahara error, that means the phone is not connecting properly and nothing will work, no matters how many of the luns you try, or if you try to look at the partitions, or anything... it's not connected, basically.

from the tele group on what to do with a sahara error:

__________________________________

When you get a sahara error on Qfil, change your USB port/cable.

Restart both phone and pc before trying again.

Check drivers on PC

Try reducing the COM port speed by going to device manager

Try another PC

Disable driver signature verification on Windows 10

If you run out of ideas, use a Linux installation; will save you a lot of trouble

_______________________________

It's not an uncommon thing, unfortunately. Cheers
[LG V40 Guides, News, & Discussion] gcwct71513:
Thank you. I'm able to boot to fastboot and download mode.
[LG V40 Guides, News, & Discussion] AsItLies:
One thing is certain, you've learned quite a bit from this experience. And I always feel like, if that's all you get out of it, that's not all bad, it's even pretty dang good.

So one thing, with later versions of android, to get twrp, we have to 'ramdisk inject' it into the existing bootloader. As catch-22 would have it, you have to have twrp already installed to do that.

So, while there are numerous ways to accomplish that task, the point is it's been done already for pretty much all variants of the lg v40. Basically, just indicate which variant / version you're using, and someone will have the boot image patched with twrp for you already.

As example, if you had korean open 30f installed, this would be the boot image patched with twrp. After flashing this with qfil, boot directly to twrp, if asked for pw just cancel out of that, format data, reboot recovery, flash magisk and dm-verity, and yer done.

It's not that hard, but as you've seen, there's a bit to be learned. But doing the above, in addition to the unlocking B/L, as you've discovered, then you'll have twrp, magisk, unencrypted... basically, all set!

cheers
[LG V40 Guides, News, & Discussion] pichulo:
Is this guide applicable to LM-V409NUA running android 10 (korean version crossflashed to Sprint unlocked phone)?

My software version is V409NUA30b.

I think that will only work if Im in Oreo, right?

Thanks in advance.
[LG V40 Guides, News, & Discussion] AsItLies:
No, the guide will work for any variant, except t-mobile. And that includes any version of android. The v35 abl is Oreo based, which means it won't BOOT anything but an Oreo rom. But you're not going to use it to boot, you're just going to use it to unlock the bootloader, then flash the abl back that you SAVED OFF before starting the process.

so, you have to have YOUR abl, that's on your system now, back on it, to be able to boot.

cheers
[LG V40 Guides, News, & Discussion] Rasczak AW:
When i finally enter in fastboot mode, for the time when i write the command "fastboot oem unlock", the fastboot mode reload and enters in a loop. I'm trying on a sprint LG V40
[LG V40 Guides, News, & Discussion] AsItLies:
before using that command, you have to go to developer options and enable 'OEM Unlock' in developer settings.

flash the original abl back (with qfil or v35 eng abl), fix developer settings, and try again.

cheers