Rooting an LG LMV405EBW with Android 10 installed... endless error experience? - LG V40 Questions & Answers

Hey guys,
maybe I'm just dumb, maybe it's just horror. Let's start the journey of my problems. My Android version is 10, with security update from 1. December 2020. Software version "V30e-EUR-xx", Kernel 4.9.193. Model is LM-V405EBW. First, I tried following this guide:
[GUIDE] Unlock your LG V40 via 9008 mode (Every Variant except T-Mobile)
This Guide will explain how to unlock your LG V40 (Every variant except T-Mobile) Unlock Prerequisites: Make sure you have "Enable OEM Unlock" enabled in developer options, along with adb debugging. Very important. You'll be stuck with the red...
forum.xda-developers.com
After finally getting the drivers to work and the phone being recognized as "Qualcomm HS-USB QDLoader 9008" under "Kedacom USB Device" in the device manager in EDL mode, storage was set to ufs, the prog_ufs_firehose_Sdm845_lge.elf was selected, I loaded the v35eng.img onto the abl_a and every step seemed to work just as intended, until I entered the bootloader menu. When I try to set the command "fastboot oem unlock", it said:
FAILED (remote: unknown command)
finished. total time: 0.002s
Under fastboot devices, my device says:
LMV405EBW80f37c1d
Isn't it supposed to say something like "LMV350..."? According to a YT video, it does (for me, makes sense with v35eng being flashed as well). And then I realized this guide was only supposed to work with Android Oreo. So I first tried to unlock the bootloader the official way, just to realize that LG has completely terminated the dev program and the ":fastboot flash unlock unlock.bin" command won't bring be anywhere, since I'll not be able to get the unlock.bin from LG. So I went on and tried to crossflash it back to Oreo... well...
Since the driver in the device manager said "LGE Mobile USB Serial Port" in download mode (while still saying "Qualcomm HS-USB QDLoader 9008" in EDL mode), I tried to flash an old Oreo .kdz for my exact device, first using LGUP, using this guide:
[GUIDE] LGUP for all (no root needed)
Greetings everyone, i go by the name Ainz Ooal Gown. Here i bring you the Official Guide on LGUP to fix a Brick of your device or to simply Cross flash/Upgrade your device from Windows. First things first if you try this and end up with a brick...
forum.xda-developers.com
... stuck at error message. LGUp says:
Error: 0x6004, CrossDL
judypn_lao_eea>@judypn_la (can't read the rest)
Then I tried LG Flash Tool... again, stuck at error message, it says:
Please install CSMG B2C Client Tool
Select Tool -> B2C Client Setup Menu
Trying to get Flash Tool to work, I downloaded LG Mobile Support Tool, since it's supposed to have that B2C Client Tool (and not a single source of B2C Client Tool was online anymore), but that doesn't install at all, probably because LG terminated that as well.
Am I just THAT lost or is it really THAT hard to unlock a simple bootloader? Never experienced something even remotely as frustrating as that right here. Neither with the LG G3, nor G5, nor V30. Thinking about giving up... I mean, it still boots...
If you have the solution, I'd be very thankful of your help.
Edit: Found out myself. Not only abl_a.bin needs to be flashed via QFIL, but abl_b as well. When in fastboot mode, also just flash both backup .bins to the device and then restart.

Related

Qhsusb_bulk/Qualcomm HS-USB QDLOADER 9008?

I will be explaining eeverything that happened. If you don't want to read it and just skip to the information about my phone, then please do so.
Ok, so to start with, I first bricked my phone by trying to unlock my bootloader and flashing TWRP recovery. Luckily I backed up my recovery and kernel images using Flashify, before my first brick. I then followed this to unbrick it http://forum.xda-developers.com/showpost.php?p=61808443&postcount=9. After, I was able to unlock the bootloader and flash TWRP recvoery, following http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690. I used the D405n v20a version of the aboot.bin file and TWRP_2 (I forgot which version). I was trying to unlock the PIE security, because when I used qpyplus 2.7 (python) and typed "python", I got an error. This is my thread http://forum.xda-developers.com/subscription.php?do=viewsubscription&folderid=all. I tried a few times to follow multiple tutorials, which each time, I had to reflash the stock ROM after bricking it, and following the first tutorial I linked to unbrick my phone. I would get an error, saying the version is wrong, or something like that, every time I rebooted my phone. I rooted my phone again, then tried to follow the unlock bootloader and flash TWRP, following this tutorial http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690. Using the same aboot.bin and TWRP.img I used before. It was no longer working. When I went from the very start refollowing this http://forum.xda-developers.com/showpost.php?p=61808443&postcount=9, stupidly I tried reflashing the recovery.img instead of the loader.img. Now, my phone never acts like it did when I was bricking it before. It never shows up in My Computer, doesn't show up in drive manager, showing no partitions, when I go to device manager, under "Other devices", my phone is "QHSUSB_BULK" http://i.imgur.com/QP4fRVp.png. In properties, this is under "general" http://i.imgur.com/CVgbAFR.png. "driver" http://i.imgur.com/38HRDib.png. "details" http://i.imgur.com/ejch5sW.png. "events" http://i.imgur.com/XP3Y3TP.png. I've plugged it into different ports, I commonly have it in COM-3. Upon looking around for "bricked phone QHSUSB_BULK", I found this forum http://androidforums.com/threads/hard-brick-lg-g2-qhsusb_bulk-but-no-partitions-detected.934856/. I scrolled down and saw to install some drivers, so I intsalled them. The phone then came under "Ports (COM & LPT)" as "Qualcomm HS-USB QDLoader 9008 (COM3)".
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
So that is what happened, here is the information on my phone:
LG D405n L90
Android 5.0.2 (Lollipop)
Kernel 3.4.0+
v20a
Stock recovery
Root
Stock Recovery
*I assume most stuff above is reset or different since it's bricked*
Images:
http://i.imgur.com/zTRWMU6.png
http://i.imgur.com/QP4fRVp.png
http://i.imgur.com/CVgbAFR.png
http://i.imgur.com/38HRDib.png
http://i.imgur.com/ejch5sW.png
http://i.imgur.com/XP3Y3TP.png
Attachments:
http://forum.xda-developers.com/showpost.php?p=61808443&postcount=9
http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690
http://forum.xda-developers.com/subscription.php?do=viewsubscription&folderid=all
http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690
http://forum.xda-developers.com/showpost.php?p=61808443&postcount=9
http://androidforums.com/threads/hard-brick-lg-g2-qhsusb_bulk-but-no-partitions-detected.934856/
If anybody could help with this, I would be very greatful. Thank you.
If anyone has the same problem above, please follow this tutorial: http://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429 It fixed it for me.
I put Samsung Note 3 ( N9005) Qualcomm based mobile on EDL by ADB Command. The command does work & phone reboot to show in device manager Qualcomm usb Driver, BUT Qualcomm USB drivers disappear after few seconds .... What could be the issue....as i wanted to use QPST ( QFil) to flash the phone but its giving error that no port is selected.
How to make " Qualcomm HS-USB QD loader 9008 " drivers to appear permanently in Device manager.
searched a lot on goolge but nothing is working...
Pls any one help.

Lg up tool Device model unknown?

My g4 is in a state of half alive half dead.
I explained in another post my issue.
Seemingly people say lg up tool is now the only method Unlike the old flash tool method to unbrick or kdz stock is this Only cause of 6.0 firmware?
When i plug in phone to pc in download mode Lg up tool shows device model as unknown. And says please select a device model which theres no butons to do that.
Lg flash tool 2014 won't flash 20i kdz it errors out connection upon extracting kdz software at around 80% Even leting it sit don't work like people say to do
Ive tried 10n kdz also that says software upgrade in progress fails at 9% then says unplug phone from pc and retry.
There is no Com in the download mode screen at any point.
All i did by mistake was fastboot oem relock bootloader Whilw rooted and on micromods Rom ONLY cause i wasnt sure if that' was the cause of the failed Flash tool errors. Now i have secure boot error 1003. Now I knew that was a No no with Nexus phones but i suspected Lg kdz over writes all that stuff.
Theres gotta be a way with one of the 2 tools Or a way to adb re unlock the bootloader and maybe salvage my Underlying twrp recovery and O.S
ANY HELP HELPS
Sent from my LGMS631 using XDA Free mobile app

P9 rescue - only fastboot (Help please)

Hi,
I have a P9 here I'm was asked to repair. I think it is kind of bricked and I hope some one can help me to unbrick it.
According to the auto dc-unlocker identification:
Found Phone : EVA-L09
Firmware : EVA-L09C432B386
FB LockState: LOCKED
USER LockState: LOCKED
So, bootloader locked and FRP locked. I don't know if the Firmware version above is right. All I know is that some Update.app files were flashed to the state of the phone now and before there where bootloops while the start animation and stuck boot with black screen.
At the moment I can do:
- turn on to see only the first huawei log with "powered by android", then nothing happens
- I can not enter eRecovery or update for Update.app
- I can only enter fastboot
I have the unlock code for the bootloader. I can not commit any fastboot commands (oem unlock, flash, etc) all is blocked with:
FAILED (remote: Command not allowed)
The locked FRP should be the reason for this.
I think OEM-unlock and usb debug from developer section was not enabled as the phone was usable. adb commands like "adb reboot bootloader" fail with
error: device '(null)' not found
fastboot devices shows the device
I have tried to uncharge the battery and then try to enter other modes than fastboot. No luck with that.
Do I have any chance to unbrick it without paying for the dc-unlocker/phoenix?
Can I do something with SRKTool?
If I have to use unlocker,
- do I have to unlock the bootloader?
- should I flash the same firmware that is now on the phone (B386) and where can I find it? (found only 1000 other versions until now)
Hope for answers
I've gone through that before, but ended up using DC-Phoenix to unbrick it when it's FRP and bootloader locked. Cost me about $15. There is a post on how to do this but I'll have to search for it again.
Here is the post I used:
https://forum.xda-developers.com/showpost.php?p=71767614&postcount=7
I guess you enter fastboot by Vol- and Power?
Not sure if the following method could help you with, but you can analyze before you go for dc-phoenix:
https://forum.xda-developers.com/showpost.php?p=74169408&postcount=7
scammander said:
Hi,
I have a P9 here I'm was asked to repair. I think it is kind of bricked and I hope some one can help me to unbrick it.
According to the auto dc-unlocker identification:
Found Phone : EVA-L09
Firmware : EVA-L09C432B386
FB LockState: LOCKED
USER LockState: LOCKED
So, bootloader locked and FRP locked. I don't know if the Firmware version above is right. All I know is that some Update.app files were flashed to the state of the phone now and before there where bootloops while the start animation and stuck boot with black screen.
At the moment I can do:
- turn on to see only the first huawei log with "powered by android", then nothing happens
- I can not enter eRecovery or update for Update.app
- I can only enter fastboot
I have the unlock code for the bootloader. I can not commit any fastboot commands (oem unlock, flash, etc) all is blocked with:
FAILED (remote: Command not allowed)
The locked FRP should be the reason for this.
I think OEM-unlock and usb debug from developer section was not enabled as the phone was usable. adb commands like "adb reboot bootloader" fail with
error: device '(null)' not found
fastboot devices shows the device
I have tried to uncharge the battery and then try to enter other modes than fastboot. No luck with that.
Do I have any chance to unbrick it without paying for the dc-unlocker/phoenix?
Can I do something with SRKTool?
If I have to use unlocker,
- do I have to unlock the bootloader?
- should I flash the same firmware that is now on the phone (B386) and where can I find it? (found only 1000 other versions until now)
Hope for answers
Click to expand...
Click to collapse
So you can not update via dload method? Did you try booting into recovery (not Recovery)? And you can't update with Update.app, you need to flash update.zip and full_update.zip via TWRP or Recovery. What wanted the owner of this phone to do, that he bricked it ?
Thank you all for your answers. Like I tried to describe: I was not able to access any other mode than fastboot.
"was able": I used DC-Phoenix now and it worked just fine.
Little confusing is that in all tutorials, even the on on the DC site, the UI of the tool is different.
But that's now Problem. The current Version is lot easier. Just "Standard Mode", select Update.app (full), Click Update.
The Phone gets flashed with fastboot, DC will restart it to update mode and will flash again. All automatic.
Really easy.
so you paid 15 USD ?
DallasCZ said:
so you paid 15 USD ?
Click to expand...
Click to collapse
Yes I did, and it worked.

EDL stuck after flashing October Patch with MiFlash

Hello everyone, I wanted to open a topic here because I'm about 6 hours that I'm trying, but without any success ...
practically, after flashing via MiFlash (the latest version available) the update of 8.1.0 with the patches of October, the smartphone has started correctly, and then, suddenly turn off and go into EDL mode.
I tried all the possible combinations with the keys, but the result is that it simply always goes to EDL (the computer, also in Device Manager, detects Qualcomm HS-USB QDLoader 9008) ...
When i try to flash any rom stock, MiFlash detects the smartphone, but by flashing it gives me "hello packet not received" or, after flashing the firehose and abl me files from "You can not authorized to Download !!!" or, start the flash and then disconnect the smartphone by giving "can not read from port COM *number*".
I also tried to replace the files inside "images" by taking the files from Patched Programmer, but the result is always the same.
I really do not know how to continue ...
By chance, does anyone have a solution?
Thanks in advance for any help from you.
oscar-goat said:
Hello everyone, I wanted to open a topic here because I'm about 6 hours that I'm trying, but without any success ...
practically, after flashing via MiFlash (the latest version available) the update of 8.1.0 with the patches of October, the smartphone has started correctly, and then, suddenly turn off and go into EDL mode.
I tried all the possible combinations with the keys, but the result is that it simply always goes to EDL (the computer, also in Device Manager, detects Qualcomm HS-USB QDLoader 9008) ...
When i try to flash any rom stock, MiFlash detects the smartphone, but by flashing it gives me "hello packet not received" or, after flashing the firehose and abl me files from "You can not authorized to Download !!!" or, start the flash and then disconnect the smartphone by giving "can not read from port COM *number*".
I also tried to replace the files inside "images" by taking the files from Patched Programmer, but the result is always the same.
I really do not know how to continue ...
By chance, does anyone have a solution?
Thanks in advance for any help from you.
Click to expand...
Click to collapse
1)your bootloader is unlocked or not when you flash stock rom with MiFlash?(fastboot oem unlock and fastboot flashing unlock critical and this will wipe all your data if you don't already use this command)
2)Hello packet not received is currently with USB 3.0 and USB 3.1 port, try USB 2.0 port and reboot your PC and the phone
3)If this not work try to use your warranty

Ungrey out bootloader

I am having major issues with GFIL working. My bootloader showed locked, though I know it was unlocked. Now it is grey out and says it is unlocked, it there a way to get that back to showing locked so I can manually unlock it again.
I am thinking that is the only reason QFIL is not working
Thank you:good:
Qfil only works if you entered the bulk or 9008 mode only. If you have unlocked your bootloader and reflashed or flashed a stock kdz for your device you will now have to relock and unlock it again, a reason why its greyed out.
KouaV1 said:
Qfil only works if you entered the bulk or 9008 mode only. If you have unlocked your bootloader and reflashed or flashed a stock kdz for your device you will now have to relock and unlock it again, a reason why its greyed out.
Click to expand...
Click to collapse
It is unlocked, but greyed out. QFIL won't work so no way to get into fastboot, to lock and unlock. So I am pretty well SOL.. QFIL won't bring up the option to get into Partiton Manager.
You dont need qfil to get into fastboot as thats a method from Xsavi for bootloader unlocking. Use the files in Xsavis post https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207 . how did you get into fastboot mode in the first place to unlock it? Does Qfil show 9008 mode? if not showing 9008 it mean you didnt do it right.You need to relock the bootloader after you flash back the original kdz, do the steps to unlock again or else you cant flash twrp.
KouaV1 said:
You dont need qfil to get into fastboot as thats a method from Xsavi for bootloader unlocking. Use the files in Xsavis post https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207 . how did you get into fastboot mode in the first place to unlock it? Does Qfil show 9008 mode? if not showing 9008 it mean you didnt do it right.You need to relock the bootloader after you flash back the original kdz, do the steps to unlock again or else you cant flash twrp.
Click to expand...
Click to collapse
I installed US Pie through LGUP from Sprint. I lost fast boot in the process, and now when I try using QFIL the Partition Manager will now pop up for me to flash the Engineering Bootloader (abl_a"). All the drivers are installed and showing up correctly in Windows 10 Device Manager, and in QFIL.
Droidman61 said:
I installed US Pie through LGUP from Sprint. I lost fast boot in the process, and now when I try using QFIL the Partition Manager will now pop up for me to flash the Engineering Bootloader (abl_a"). All the drivers are installed and showing up correctly in Windows 10 Device Manager, and in QFIL.
Click to expand...
Click to collapse
Yeah flash the v35 eng image onto the abl_a partition but back up your abl_a first before doing that incase it messed up. After you have done that you should press and hold the Power and Volume Down buttons until your device reboots out of 9008. When you hear the disconnect sound, immediately hold volume down (only volume down) to enter fastboot right away.
If still no fastboot then after you have sucessfully unlocked bootloader and stuff then youll need qfil to flash twrp onto abl_a.
KouaV1 said:
Yeah flash the v35 eng image onto the abl_a partition but back up your abl_a first before doing that incase it messed up. After you have done that you should press and hold the Power and Volume Down buttons until your device reboots out of 9008. When you hear the disconnect sound, immediately hold volume down (only volume down) to enter fastboot right away.
If still no fastboot then after you have sucessfully unlocked bootloader and stuff then youll need qfil to flash twrp onto abl_a.
Click to expand...
Click to collapse
I lost fast boot in the process, and now when I try using QFIL the Partition Manager will NOT POP UP for me to flash the Engineering Bootloader (abl_a"). All the drivers are installed and showing up correctly in Windows 10 Device Manager, and in QFIL.
So I don't know why the "Partition Manager" in QFIL will not work so I can install abl_a!:
Droidman61 said:
I lost fast boot in the process, and now when I try using QFIL the Partition Manager will NOT POP UP for me to flash the Engineering Bootloader (abl_a"). All the drivers are installed and showing up correctly in Windows 10 Device Manager, and in QFIL.
So I don't know why the "Partition Manager" in QFIL will not work so I can install abl_a!:
Click to expand...
Click to collapse
Does device Manager show your in "Qualcomm HS-USB QDLoader 9008"? Are you setting storage type to "UFS" in Qfil? Are your COM ports correct in device manager and in QFil? I ask these questions just incase you did something wrong but All I know is if your device does not have fastboot then qfil will be the one you need to flash twrp. Also make sure your using a USB 2.0 port as 3.0 has issues with the V40. Other thing is if your phones developer setting has OEM unlock greyed out then you will need to relash original kdz and relock bootloader and unlock again otherwise youll have fastboot fail with twrp flash. You don't need fastboot for qfil to work unless your phone is bricked if its just black screen and no light and if you cant boot into your phone.
KouaV1 said:
Does device Manager show your in "Qualcomm HS-USB QDLoader 9008"? Are you setting storage type to "UFS" in Qfil? Are your COM ports correct in device manager and in QFil? I ask these questions just incase you did something wrong but All I know is if your device does not have fastboot then qfil will be the one you need to flash twrp. Also make sure your using a USB 2.0 port as 3.0 has issues with the V40. Other thing is if your phones developer setting has OEM unlock greyed out then you will need to relash original kdz and relock bootloader and unlock again otherwise youll have fastboot fail with twrp flash. You don't need fastboot for qfil to work unless your phone is bricked if its just black screen and no light and if you cant boot into your phone.
Click to expand...
Click to collapse
Wow thank you for the info, sadly I have Sprint and there is NO kdz for this. to lock and re-lock. I think I am screwed.
Thank you.:good:
Yeah your probably screwed if you locked it with a custom rom or twrp. This a reason why I rather go with US unlvoked variant. AT&T also never releases software or firmwares for their phones and verizon removing fastboot. US carriers want your money thats the reason they do all these
KouaV1 said:
Yeah your probably screwed if you locked it with a custom rom or twrp. This a reason why I rather go with US unlvoked variant. AT&T also never releases software or firmwares for their phones and verizon removing fastboot. US carriers want your money thats the reason they do all these
Click to expand...
Click to collapse
I re-installed Windows 10 and boot, instant QFIL.:fingers-crossed::fingers-crossed:
Droidman61 said:
I re-installed Windows 10 and boot, instant QFIL.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
awesome good for you

Categories

Resources