It seems the 'prog_ufs_firehose_Sdm845_lge.elf' is compatible for LG devices whose CPU is Snapdragon (SDM) 845? And thus the firehose file would be safe to use with 'LG G7'?
Edit: It seems so, since I succeeded in extracting the partition files: abl_a (1 MB), boot_a & boot_b (64 MB each), and laf_a & laf_b (48 MB each).
Edit: It seems so, since I succeeded in extracting the partition files: abl_a (1 MB), boot_a & boot_b (64 MB each), and laf_a & laf_b (48 MB each).
Last edited:
issues
do you have the latest drivers i would also try reinstalling the software or try on a different computer. also make sure boot loader unlock enable is set to on and you are in developer settings.
Last edited:
Have done all that though not quite sure if i have the newest drivers. I used the ones on with the files.
Got an error message saying, original abl_a.bin file is too large to download, it's only 1.0 MB
i.imgur.com/oxh5vxk.png
NVM, it was because of the space characters; I had to enclose the directory in quotation marks. Keep in mind MS Word uses 'smart quotes' instead of 'straight quotes'; “ vs ".
When I get back into the phone to re-enable developer mode, I noticed 'Enable OEM Unlock' is always on by default due to 'bootloader is already unlocked'.
i.imgur.com/YsFJ1eM.png
i.imgur.com/oxh5vxk.png
NVM, it was because of the space characters; I had to enclose the directory in quotation marks. Keep in mind MS Word uses 'smart quotes' instead of 'straight quotes'; “ vs ".
When I get back into the phone to re-enable developer mode, I noticed 'Enable OEM Unlock' is always on by default due to 'bootloader is already unlocked'.
i.imgur.com/YsFJ1eM.png
Last edited:
You can get into fastboot mode to determine whether your phone uses abl_a or abl_b, AFTER flashing with v35eng.img, as seen in 3rd second of the following video:
/watch?v=kN7oNBslgck
Last edited:
Hello, What is the difference between classical unlocking (if possible) and unlocking according to this guide?
Are there any differences?
thanks for the reply
Are there any differences?
thanks for the reply
The same thing happened to me. I followed the directions hoping to bootloader unlock my Sprint V405UA. Process:
1) Updated phone to Pie via OTA.
2) Crossflashed 20e to phone.
3) Downloaded all unlock bootloader files.
4) Booted up into 9008 mode.
5) Uploaded the V35 Engineering bootloader.
All went well. No real issues.
Rebooted ... and red triangle with "Your device has failed a routine safety check and will not boot" and reads at the bottom all slots are unbootable.
I can reboot into stock recovery. I can get into fastboot. Everthing seems to be going right.
I can also boot into 9008 access. I tried flashing the ab1piestock that way, but the problem persists. Phone won't go past red triangle.
Any advice?
[NG]Owner
Last edited:
So I spent the better part of three hours trying to get the bootloader unlocked on my Sprint V405UA. Nothing I did worked. Finally threw in the towel and used download mode and the kdz file to go back to crossflashed stock Pie.
I'd like to try again, but I don't see it working. I tried damn near everything. Answers to these questions may help though:
1) Why is the ablpiestock.img in the OP only 216 KB? Why isn't the ablpiestock.img as large as the V35 image? v35eng.img clocks in at 1 MB. I can't help but think this is a problem. Is that file really the right one?
2) I read the data from abl_b via QFIL, then tried to write it to abl_a via Fastboot. The file QFIL saved was a bin (and the file size was the exact same as v35eng.img). Well that didn't work either. I don't know why. Can we even flash .bin files in fastboot? Do I have to convert a bin to an img file? How do I do that?
3) Is there a way to extract just the abl_a image from a kdz and flash it via fastboot? That would seem to be the easiest way. But how do you unpack a kdz file?
In any case, I can't get it to work tonight. Maybe there'll be answers tomorrow!
[NG]Owner
I'd like to try again, but I don't see it working. I tried damn near everything. Answers to these questions may help though:
1) Why is the ablpiestock.img in the OP only 216 KB? Why isn't the ablpiestock.img as large as the V35 image? v35eng.img clocks in at 1 MB. I can't help but think this is a problem. Is that file really the right one?
2) I read the data from abl_b via QFIL, then tried to write it to abl_a via Fastboot. The file QFIL saved was a bin (and the file size was the exact same as v35eng.img). Well that didn't work either. I don't know why. Can we even flash .bin files in fastboot? Do I have to convert a bin to an img file? How do I do that?
3) Is there a way to extract just the abl_a image from a kdz and flash it via fastboot? That would seem to be the easiest way. But how do you unpack a kdz file?
In any case, I can't get it to work tonight. Maybe there'll be answers tomorrow!
[NG]Owner
Last edited:
I figured I'd **** around with it again while waiting for guidance on how to make unlocking the bootloader on my Sprint V405UA work. And I got it to work! Amazing!
Here are some additional pieces of advice on how I got to be successful:
1) I had all of the files I needed to upload/flash in a folder right off of C: drive. No long convoluted paths. Just straight C:/v40root.
2) Load up QFIL first. Have that program up and in the foreground as you try to get into 9008 mode.
3) @argon9898 His advice on how to get into 9008 mode was invaluable: The key to activating EDL mode is to hold all three buttons down: POWER + VOL UP + VOL DOWN while the phone is still on. After 8-10 seconds the screen will turn off. When the screen turns off keep holding POWER + VOL DOWN while REPEATEDLY PRESS VOL UP. That should get you into EDL mode.
4) As you successfully enter into 9008 mode, the top line of the QFIL program will switch from No Port Available to Qualcomm HS-USB QDLoader 9008 (COMX). That is your definitive clue that the phone is ready for the v35 Engineering bootloader.
5) Load the v35 Engineering bootloader as described. DO NOT EXIT out of any of the QFIL screens. Leave them up as is.
6) Perform the exit out of the 9008 mode into v35 Engineering bootloader mode as described. The bootloader will look strange. Different color text by lines, and the volume button will cycle through Restart, Power Off, then some Fastboot gibberish. If that's what you see, you've loaded the v35 Engineering bootloader successfully.
7) Perform the fastboot commands as described.
8) Once done with the fastboot commands as described, unplug the USB-C cable from the phone.
9) Use the volume keys on the phone select Restart (or something along those lines, I can't remember now).
10) The phone will flash a warning about bootloader unlocked, then begin its normal boot process. That boot process will take a bit longer than usual because userdata was wiped unlocking the bootloader.
Good luck!
[NG]Owner
Here are some additional pieces of advice on how I got to be successful:
1) I had all of the files I needed to upload/flash in a folder right off of C: drive. No long convoluted paths. Just straight C:/v40root.
2) Load up QFIL first. Have that program up and in the foreground as you try to get into 9008 mode.
3) @argon9898 His advice on how to get into 9008 mode was invaluable: The key to activating EDL mode is to hold all three buttons down: POWER + VOL UP + VOL DOWN while the phone is still on. After 8-10 seconds the screen will turn off. When the screen turns off keep holding POWER + VOL DOWN while REPEATEDLY PRESS VOL UP. That should get you into EDL mode.
4) As you successfully enter into 9008 mode, the top line of the QFIL program will switch from No Port Available to Qualcomm HS-USB QDLoader 9008 (COMX). That is your definitive clue that the phone is ready for the v35 Engineering bootloader.
5) Load the v35 Engineering bootloader as described. DO NOT EXIT out of any of the QFIL screens. Leave them up as is.
6) Perform the exit out of the 9008 mode into v35 Engineering bootloader mode as described. The bootloader will look strange. Different color text by lines, and the volume button will cycle through Restart, Power Off, then some Fastboot gibberish. If that's what you see, you've loaded the v35 Engineering bootloader successfully.
7) Perform the fastboot commands as described.
8) Once done with the fastboot commands as described, unplug the USB-C cable from the phone.
9) Use the volume keys on the phone select Restart (or something along those lines, I can't remember now).
10) The phone will flash a warning about bootloader unlocked, then begin its normal boot process. That boot process will take a bit longer than usual because userdata was wiped unlocking the bootloader.
Good luck!
[NG]Owner
Do you still get OTA update after this root?
Sent from my LM-V405 using Tapatalk
Sent from my LM-V405 using Tapatalk
Hi. I'm trying to understand the guide. It says "If you don't have the "Enable OEM Unlock" option in developer options, you'll have to flash frp with the v35 engineering bootloader." I do have Enable OEM unlock option and I have it enabled. Does it mean I can skip to the "Unlocking your bootloader" section? thanks
I have LM-V405UA sprint android 9 feb 2020 security patch sim unlocked
I have LM-V405UA sprint android 9 feb 2020 security patch sim unlocked
Last edited:
How Does/Will This Work on 405QA?
I have a brand new model 405QA with Pie (V405QA20a) installed at the factory. It has an OEM unlock switch in developer settings. I used fastboot to get the device's long ID code and tried to get an bootloader unlock code from the LG Developer's site. But it said that my model could not be unlocked!
I have to be able to root this device or back it goes. So I am trolling for a solution and found this thread. If this will work, which steps must I follow? Thanks for any help.
I have a brand new model 405QA with Pie (V405QA20a) installed at the factory. It has an OEM unlock switch in developer settings. I used fastboot to get the device's long ID code and tried to get an bootloader unlock code from the LG Developer's site. But it said that my model could not be unlocked!
I have to be able to root this device or back it goes. So I am trolling for a solution and found this thread. If this will work, which steps must I follow? Thanks for any help.
fastboot oem unlock fails (unknown command)
Hello. I appreciate any help you can give...
I have gone through this process on my new 405QA device. All seems fine. The QFIL console window shows that the v35 bootloader has been sent successfully. So I reboot into fastboot mode and try to issue fastboot oem unlock. All I get is "FAILED (remote: unknown command).
Any idea what this means and how to proceed to get this job done?
Thanks!
<<added>>
To be clear, I sent the v35 file to the abl_a that is within LUN #4 as shown in the screenshots. I say this because I noticed there was also an abl_a in LUN #1. No idea why that is or what the difference is. So I just did as I was told. This also makes me wonder about using the fastboot flash abl_a path/to/ablpiestock.img since it is not clear to me how fastboot will know the difference between the partition with the abl_a label in the 2 LUN. Thanks
Hello. I appreciate any help you can give...
I have gone through this process on my new 405QA device. All seems fine. The QFIL console window shows that the v35 bootloader has been sent successfully. So I reboot into fastboot mode and try to issue fastboot oem unlock. All I get is "FAILED (remote: unknown command).
Any idea what this means and how to proceed to get this job done?
Thanks!
<<added>>
To be clear, I sent the v35 file to the abl_a that is within LUN #4 as shown in the screenshots. I say this because I noticed there was also an abl_a in LUN #1. No idea why that is or what the difference is. So I just did as I was told. This also makes me wonder about using the fastboot flash abl_a path/to/ablpiestock.img since it is not clear to me how fastboot will know the difference between the partition with the abl_a label in the 2 LUN. Thanks
Last edited:
Hi. I am hoping that my problem is same as yours - using only slot A as shown. How can I tell which slot the phone is actually using? Thanks
Ok, progress finally. Seems the active slot in my device was B, not A. After backing up all the B partitions, I was able to install the V35 bootloader, unlock, and flash the original Pie bootloader. When I reboot into normal mode, I now see an unlocked warning and it took a very long time for the phone to get started and prompt me to start all over with my Android install. Before I do that I am trying to restore the backup I made of the userdata partition to see if that spares me the whole setup thing. Thanks to all.
Hi. Has anyone else noticed that once they have done this bootloader unlocking and installed the TWRP on their V40 that they cannot boot into TWRP recovery mode using the power and volume down buttons? I still can:
1. Boot into what seems like factory recovery mode which permits only factory reset or not using power and volume down buttons.
2. Press/hold the down volume key and plug in a usb to get to fastboot.
3. Press/hold both volume keys along with the power button to display the IMEI and serial number.
4. Get into Engineering mode as described in this thread and out of Engineering mode by press/hold power and volume down keys.
But I cannot seem to get into TWRP recovery any longer using just the hardware buttons. I can use a root app for this purpose or issue the root command "/system/bin/reboot recovery", or "adb shell reboot recovery".
This seems a bad thing to loose. Am I alone on this? If so, what am I doing wrong? Thanks
1. Boot into what seems like factory recovery mode which permits only factory reset or not using power and volume down buttons.
2. Press/hold the down volume key and plug in a usb to get to fastboot.
3. Press/hold both volume keys along with the power button to display the IMEI and serial number.
4. Get into Engineering mode as described in this thread and out of Engineering mode by press/hold power and volume down keys.
But I cannot seem to get into TWRP recovery any longer using just the hardware buttons. I can use a root app for this purpose or issue the root command "/system/bin/reboot recovery", or "adb shell reboot recovery".
This seems a bad thing to loose. Am I alone on this? If so, what am I doing wrong? Thanks
Last edited:
Bricked?
Hello everyone I wanted to ask a noobish question. Where would I be able to find the files needed to unbrick with QFil? Thanks in advanced.
Hello everyone I wanted to ask a noobish question. Where would I be able to find the files needed to unbrick with QFil? Thanks in advanced.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone