[TWRP]LG V40 / Judypn

[iannisb]

okay so the command, I think I made clear in the notes, is all on one line. It's not separated out.

additionally, you can't use the 'nuked laf' version of fastboot (that's a crippled version), you have to use the v35_engineering_abl version to flash that.

without seeing exactly what yer doing, that's all I can think of to help.

cheers

I followed the instructions to the letter and i approached with the easier way to give it a try

C:\Download>fastboot flash --disable-verity --disable-verification vbmeta_a blank_vbmeta.img
fastboot: unrecognised option `--disable-verity'

 

[AsItLies]

I followed the instructions to the letter and i approached with the easier way to give it a try

C:\Download>fastboot flash --disable-verity --disable-verification vbmeta_a blank_vbmeta.img
fastboot: unrecognised option `--disable-verity'

see, I'll have to check my notes in that folder, but that's wrong.

it's fastboot --disable (etc) and THEn it's flash vbmeta_a blank_vbmeta.img

you have the 'flash' part in the wrong position.

Oooops sorry, my bad. I created that a long time ago and got the command wrong, you were doing what it says, but it's corrected now to reflect what I pointed out above.

my goof, Cheers

 

[iannisb]

C:\Download>fastboot flash --disable-verity --disable-verification vbmeta_a blank_vbmeta.img
fastboot: unrecognised option `--disable-verity'

okay so the command, I think I made clear in the notes, is all on one line. It's not separated out.

additionally, you can't use the 'nuked laf' version of fastboot (that's a crippled version), you have to use the v35_engineering_abl version to flash that.

without seeing exactly what yer doing, that's all I can think of to help.

cheers

so its three commands?

fastboot flash disable-verity
fastboot flash disable-verification
flash vbmeta_a blank_vbmeta.img

 

[AsItLies]

C:\Download>fastboot flash --disable-verity --disable-verification vbmeta_a blank_vbmeta.img
fastboot: unrecognised option `--disable-verity'


so its three commands?

fastboot flash disable-verity
fastboot flash disable-verification
flash vbmeta_a blank_vbmeta.img

No! absolutely not, that's a mistake. I was doing that at first and it's not doing what it should do.

It's one command, all on one line. See post above, I corrected the info. Sorry.

 

[iannisb]

No! absolutely not, that's a mistake. I was doing that at first and it's not doing what it should do.

It's one command, all on one line. See post above, I corrected the info. Sorry.

Again i get the same error :
C:\Download>fastboot --disable-verity --disable-verification flash vbmeta_a blank_vbmeta.img
fastboot: unrecognised option `--disable-verity'

IS there a special fastboot that i should install in my windows 10 laptop?
Thank you for your time

 

[AsItLies]

Again i get the same error :
C:\Download>fastboot --disable-verity --disable-verification flash vbmeta_a blank_vbmeta.img
fastboot: unrecognised option `--disable-verity'

IS there a special fastboot that i should install in my windows 10 laptop?
Thank you for your time

not a special one on the pc, but it does need to be the v35 eng abl on the phone. The fastboot we get by nuking the laf image isn't as powerful as the v35 eng abl one is.

 

[nikothebarber]

i need the latest Q boot img for ATT im stuck on Lg V40 screen please

 

[AsItLies]

i need the latest Q boot img for ATT im stuck on Lg V40 screen please

What is the 'latest for ATT'? They don't make their kdz available, the only people that will have the 'latest' are the ones that receive it OTA?

I've no idea (as I don't use ATT) what that version is? Maybe if u had a version number someone could help, but without that it's just a guess, unless you find someone that is unrooted and locked and getting updates from ATT...

 

[Scorcerer]

Again i get the same error :
C:\Download>fastboot --disable-verity --disable-verification flash vbmeta_a blank_vbmeta.img
fastboot: unrecognised option `--disable-verity'

IS there a special fastboot that i should install in my windows 10 laptop?
Thank you for your time

maybe try with --disable-verify

 

[osaka35]

Hi, looked through all the pages here and a few threads, but couldn't find a 30E boot image with TWRP. From what I've read, I'll need that particular one to get TWRP and then MAGISK (or should I update to the latest version, whatever that is, then find boot with TWRP?).

Actually, how relevant is this guide given I'm on Android 10? Should I follow these steps with modifications, or is there someone willing to help get me from point A to point B?

to note: I'm successfully back on ATT unlocked android 10 (obviously), after successfully unlocking the bootloader using V35engineering and getting it back to stock.

 

[AsItLies]

maybe try with --disable-verify

**maybe** just type fastboot -h and look at the output to verify the correct commands, instead of **guessing** what they might be?


options:
-w Wipe userdata.
-s SERIAL Specify a USB device.
-s tcp|udp:HOST[ORT] Specify a network device.
-S SIZE[K|M|G] Break into sparse files no larger than SIZE.
--force Force a flash operation that may be unsafe.
--slot SLOT Use SLOT; 'all' for both slots, 'other' for
non-current slot (default: current active slot).
--set-active[=SLOT] Sets the active slot before rebooting.
--skip-secondary Don't flash secondary slots in flashall/update.
--skip-reboot Don't reboot device after flashing.
--disable-verity Sets disable-verity when flashing vbmeta.
--disable-verification Sets disable-verification when flashing vbmeta.
--wipe-and-use-fbe Enable file-based encryption, wiping userdata.
--unbuffered Don't buffer input or output.
--verbose, -v Verbose output.
--version Display version.
--help, -h Show this message.

 

[AsItLies]

Hi, looked through all the pages here and a few threads, but couldn't find a 30E boot image with TWRP. From what I've read, I'll need that particular one to get TWRP and then MAGISK (or should I update to the latest version, whatever that is, then find boot with TWRP?).

Actually, how relevant is this guide given I'm on Android 10? Should I follow these steps with modifications, or is there someone willing to help get me from point A to point B?

to note: I'm successfully back on ATT unlocked android 10 (obviously), after successfully unlocking the bootloader using V35engineering and getting it back to stock.

Don't think you'll find one until someone copies their att 30e boot partition and posts it so they can patch it with twrp.

Their kdz isn't available, so no one can extract it from that. Use qfil and save your 30e boot_a and I'll patch it with twrp for u and post back here.

But that's the only way it will happen, is if someone posts it, but be sure to specify exactly what it is, like this: att_30e_boot_a.img, it avoids confusion with say korean oepn 30e, or ebw 30e... etc etc

cheers

 

[nikothebarber]

Hi, looked through all the pages here and a few threads, but couldn't find a 30E boot image with TWRP. From what I've read, I'll need that particular one to get TWRP and then MAGISK (or should I update to the latest version, whatever that is, then find boot with TWRP?).

Actually, how relevant is this guide given I'm on Android 10? Should I follow these steps with modifications, or is there someone willing to help get me from point A to point B?

to note: I'm successfully back on ATT unlocked android 10 (obviously), after successfully unlocking the bootloader using V35engineering and getting it back to stock.

Dude I need 30E boot img PLEASE i cant boot with out it

 

[osaka35]

Don't think you'll find one until someone copies their att 30e boot partition and posts it so they can patch it with twrp.

Their kdz isn't available, so no one can extract it from that. Use qfil and save your 30e boot_a and I'll patch it with twrp for u and post back here.

But that's the only way it will happen, is if someone posts it, but be sure to specify exactly what it is, like this: att_30e_boot_a.img, it avoids confusion with say korean oepn 30e, or ebw 30e... etc etc

cheers

Thanks, I really appreciate it. Attached are the stock boot_a+b.bin gotten from QFIL.
ATT - Android 10 - V405UA30E
For those curious, this is the latest update for US ATT V40 as of march 13, 2021

My goal is to flash Magisk after flashing TWRP and run on the modified stock. Which guide should I follow, and with any modifications, considering I'm on android 10?

Much thanks, you've saved me. Let me know if I can ever help you out with anything

 

[AsItLies]

Thanks, I really appreciate it. Attached are the stock boot_a+b.bin gotten from QFIL.
ATT - Android 10 - V405UA30E
For those curious, this is the latest update for US ATT V40 as of march 13, 2021

My goal is to flash Magisk after flashing TWRP and run on the modified stock. Which guide should I follow, and with any modifications, considering I'm on android 10?

Much thanks, you've saved me. Let me know if I can ever help you out with anything

Okay here are your 2 images. Just as an fyi, these 2 images were not identical, I think it's safe to assume whichever one is the inactive slot (b or a) is the older att version, and the active slot will be the 30e.

cheers

also, in case yer not sure, use 'fastboot getvar all' and at the end of the output it will tell you which slot is active.

Additionally, these images should be flashed using qfil, then upon exiting edl, use the key combo to go directly to recovery (now twrp). First, format data (not wipe), then, reboot recovery. Then flash magisk and dm_verity, and u should be all set.

So, just to make sure it's clear, even though I labeled these both as 30e, one of them is not. One of them is the older att version. We can't know which is which until we know which slot is active, that will be the 30e.

 

[osaka35]

Okay here are your 2 images. Just as an fyi, these 2 images were not identical, I think it's safe to assume whichever one is the inactive slot (b or a) is the older att version, and the active slot will be the 30e.

cheers

also, in case yer not sure, use 'fastboot getvar all' and at the end of the output it will tell you which slot is active.

Additionally, these images should be flashed using qfil, then upon exiting edl, use the key combo to go directly to recovery (now twrp). First, format data (not wipe), then, reboot recovery. Then flash magisk and dm_verity, and u should be all set.

Thank you! You're my hero.

For anyone else who's curious. "slot B" was my active slot.

I couldn't get me into recovery using the key combination, but a normal reboot and a simple "ADB reboot recovery" got me in.

 

[AsItLies]

Thank you! You're my hero.

For anyone else who's curious. "slot B" was my active slot.

I couldn't get me into recovery using the key combination, but a normal reboot and a simple "ADB reboot recovery" got me in.

Yer welcome no probs.

I went ahead and deleted the boot_a one as that's not for 30e. Don't need any confusion. In case others don't know, the b and a are interchangeable. so the one above labeled b could be used on a or b. The important thing is that it's the right one for att 30e.

cheers

 

[iannisb]

HEll

give me a bit, I'll get to it. But first, you realize you'll have to use qfil to load this? Can't be done with fastboot. I mention that because you went to all the trouble to decompose a kdz to dz to images to get the boot_a. but wiht qfil you could have just read the partition data and saved it?

I'll do it nonetheless, but it has to be flashed with qfil, then follow the additional instructions.

here's a gdrive link to your ebw 30d with twrp ramdisk injected. Remember, use qfil to first back up existing boot_a (u already that that though), then flash this file. Once flashed, back out of qfil and hold vol minus and power button to exit edl mode on the device. Keep holding until lg logo, then quickly release only pwr and then reapply it. That brings to twrp. Sel cancel if it asks for pw, swipe to allow mods, format data, then reboot recovery. Once back in twrp flash magisk and dm-verity.

should be all set then. Cheers

Hello there how are you ?
Today i came accross this problem.
i was listening to music (had installed viper4android through Magisk.)
I went for a run and used a running app to measure distance. The app froze and reboot the phone.
After the rebootthe phone stuck at LG V40 screen so i went into twrp and chose fix recovery bootloop.
The phone booted normally but i lost root , magisk didnt work..
Whenever i flashed magisk again , the phone gets stuck at LG V40 so i have to run ''fix recovery bootloop'' to boot into android..but then i lose root magisk...again!

 

[AsItLies]

HEll


Hello there how are you ?
Today i came accross this problem.
i was listening to music (had installed viper4android through Magisk.)
I went for a run and used a running app to measure distance. The app froze and reboot the phone.
After the rebootthe phone stuck at LG V40 screen so i went into twrp and chose fix recovery bootloop.
The phone booted normally but i lost root , magisk didnt work..
Whenever i flashed magisk again , the phone gets stuck at LG V40 so i have to run ''fix recovery bootloop'' to boot into android..but then i lose root magisk...again!

sorry haven't much of an idea on that, don't use viper4android nor any app to measure distances.

Can you get back to where u were before installing these apps? Always a good idea to do a twrp backup prior to installing, just in case. If u can get back, or start over, do backup and then just one app at a time, to determine which one is problem, assuming it is one of those.

cheers

 

[iannisb]

sorry haven't much of an idea on that, don't use viper4android nor any app to measure distances.

Can you get back to where u were before installing these apps? Always a good idea to do a twrp backup prior to installing, just in case. If u can get back, or start over, do backup and then just one app at a time, to determine which one is problem, assuming it is one of those.

cheers

Yes i reinstall android the phone works but i dont have root..
i use viper4android for better musik and runtastik app for running.
i believe it has something to do with magisk and viper4android.
I tried to re do everything.
Flash TWRP in slot A and then android but everytime i flasj Magisk the phone bootloops the LGV40 screen and the only way for the phone to work is to fix bootloop recovery through TWRP.
I dont understand how is it possible that the root was lost in the first place???