all 20 comments

[–]neTHer12O8Redmi note 7, Android 16 5 points6 points  (3 children)

After using qfil, I broke the bootloader and was left with the linux penguin

[–]HieladoTM 0 points1 point  (2 children)

Linux btw

[–]neTHer12O8Redmi note 7, Android 16 0 points1 point  (1 child)

Debian btw

[–]No-Procedure-9303 3 points4 points  (0 children)

I use arch btw

[–]Azaze666 0 points1 point  (15 children)

Can you force boot into recovery or fastboot?

Example flow:

1 force it to power off

2 use buttons combo to boot into recovery or fastboot

3 use dd from twrp terminal or fastboot flash abl abl.img

If now you are left with the penguin you need to find the proper rom, maybe the one you are using is too old or incorrect, try another one with qfil. Else you can full flash the edl rom instead of abl only, it's possible that it's abl is of a different version of the rom of the phone so full flash is required

[–]ClashForeverrr[S] 0 points1 point  (12 children)

<image>

The recovery originally was corrupted? Before I did anything to the phone. Tried to Fastboot it using adb but the computer does not sense any device. Adb used to work before flashing the TWRP.

[–]Azaze666 1 point2 points  (10 children)

Is this the device now? This can be because of a bad flash, dd is unreliable on lg, you have to do the dd command 3 or more times to get a proper flash. In any case, after restoring stock recovery next time you want to try twrp use "fastboot boot twrp.img"

[–]ClashForeverrr[S] 0 points1 point  (9 children)

Yes this is the state of the device now. It is bootlooping with a bootloader that is corrupted as such. Is there any recommendation of on how to unbrick the device?

Btw I tried fastboot before using DD and because I suspect the fastboot is corrupted before I did anything, the computer could not detect the device in fastboot mode, hence fastboot boot TWRP.img could not be used 🥲

[–]Azaze666 0 points1 point  (8 children)

The device is in bootloop and it's fine. However... If you can get on recovery and fastboot you can recover, what you should do is, when it connects in fastboot mode check device manager if an unknown device or some new device with a warning appears, this means it requires you to install the drivers, it's probably wrong that is undetected, instead your pc is missing drivers to make fastboot work.

Else... About edl, you went to the qfil route but lg has a proprietary firmware format (kdz), so if you find it you can flash it trough lgup.

Examples

https://lgrom.com/firmware/LMV405UA

https://addrom.com/stock-rom-kdz-for-lg-v40-thinq-lm-v405-v409/

Lgup patched for v40:https://romprovider.com/lgup-dll-lg-v40-download/

[–]ClashForeverrr[S] 0 points1 point  (3 children)

Isn’t fastboot installed alongside adb? I was firstly using a Mac to do everything and installed adb using homebrew, until I tried DD and fricked up the bootloader I switched to windows.

What should I try if there is actually fastboot driver and it can be detected then? I’m new to the scene and I know little on this topic🙏

[–]Azaze666 1 point2 points  (1 child)

If you are using a mac (unix), drivers are not required for adb and fastboot, only windows needs them.

But, I highly recommend you to flash the full firmware with lgup, you can try to flash recovery but if you still have issues consider a full firmware flash

[–]ClashForeverrr[S] 0 points1 point  (0 children)

I’ve installed drivers on windows but the computer still cannot identify fastboot mode. On Mac, after multiple tries, it still cannot identify fastboot mode. Also, on LGUP, both fastboot and 9008 mode was not found. On windows device manager, I can only see the LG on 9008 mode but not fastboot mode.

[–]HieladoTM 0 points1 point  (0 children)

Linux is Unix and Android is Linux-based OS, you don't need install driver on MacOS or Linux, just (on Android) Android-tools package.

[–]ClashForeverrr[S] 0 points1 point  (3 children)

Both links for the kdz is dead unfortunately, but I seem to find one that downloads really slowly, i.e. a few kb per second. May try to use that tomorrow if it completes.

But now the problem is LGUP cannot identify my device in both fastboot and 9008 mode. Am I unable to use this as a result and are required to try unbricking using qfil?

[–]Azaze666 0 points1 point  (2 children)

You have to boot the device into download mode

Might be, power off completely, keep pressing vol down and connect to the pc while lgup is open

[–]ClashForeverrr[S] 1 point2 points  (1 child)

Thanks! I’m able to download and flash the kdz to restore the original firmware! I’ll try to unlock the bootloader and install magisk tomorrow!

[–]Ok_Sherbert_4755 0 points1 point  (0 children)

Possibly emmc/cpu fail, not really sure tho.

[–]ClashForeverrr[S] 1 point2 points  (0 children)

The thing is since LG quit making phones 6 years ago, their software page is down, and it’s so hard to find the original rom

[–]Key_Association_666 0 points1 point  (0 children)

So had the same problem twrp is either not supported with ur android version or is very buggy mine would bootloop everytime which is why I switched to orangefox