[TWRP]LG V40 / Judypn

[2566SB]

ok thank you very much for your patience and your advice. whether I succeed or not I will write a howto about lg and todays flashing. (please watch lgv40 guides and lg v40 roms recovery ect ... I have already written a quick little howto to easily go into bootloader mode)

but I think I understood something. if we wanted to flash let's say "android 15" and lg does not make official lgv40 roms for android 15 there can never be custom firmware for android 15 on lgv40?

oh I think TWRP will solve the problem.We know lots of old devices have android Q ROM now.Like Samsung s7，Xiaomi4.Maybe It's not difficult to flash TWRP at that time,just because we can now right?
Just like now we can replace “abl” to flash TWRP ，maybe directly install the NEWest Android ROM is OK.

 

[AsItLies]

ok thank you very much for your patience and your advice. whether I succeed or not I will write a howto about lg and todays flashing. (please watch lgv40 guides and lg v40 roms recovery ect ... I have already written a quick little howto to easily go into bootloader mode)

but I think I understood something. if we wanted to flash let's say "android 15" and lg does not make official lgv40 roms for android 15 there can never be custom firmware for android 15 on lgv40?

Not necessarily. The Lineage OS Rom developer (of let's say android 15) *could* make it work with an earlier base rom of say android 10.

I believe there's already an custom android 11 rom and it of course works with lg base rom of android 10. I can't say for sure how long LOS developers will put in the time to make roms that work with older LG versions. Most times they buy a new phone and move on.

But recently, it seems many are finding that new phones and new OS versions aren't different enough to justify the expense.

cheers

 

[iannisb]

When ever i '' flashboot boot TWRP-judypn-boot.img'' TWRP does not load. Instead it loads the OS (A10,30d)

When i '' flashboot boot judypn_TWRP_bootable-metadata.img'' the TWRP loads but there is no option in Advanced -> Install Recovery Ramdisk

 

[AsItLies]

When ever i '' flashboot boot TWRP-judypn-boot.img'' TWRP does not load. Instead it loads the OS (A10,30d)

When i '' flashboot boot judypn_TWRP_bootable-metadata.img'' the TWRP loads but there is no option in Advanced -> Install Recovery Ramdisk

Which 30d do u have? is that Korean open? Are other variants also 30d? I don't know. Can't help if don't know.

 

[iannisb]

Which 30d do u have? is that Korean open? Are other variants also 30d? I don't know. Can't help if don't know.

I am using the UK 30d for European 405ebw from lg firmwares.
I ve flashed using partition DL from lgup dev
unlocked officially

 

[AsItLies]

I am using the UK 30d for European 405ebw from lg firmwares.
I ve flashed using partition DL from lgup dev
unlocked officially

Well a couple of things, 1) with newer firmware, you can no longer 'fastboot boot twrp'. The way to create a boot loader with twrp in it, you have to do 'ramdisk inject'.

I explain that because, near as I can tell, no one has created your needed boot partition with twrp injected into it. It exists for many other versions, but 30d is very new.

2) The 'overview' of how u do it goes like this; Use qfil to flash to boot_a an older version of yoour type of firmware like this one for 30b, that way u can exit qfil and go directly to twrp. Once in twrp, you'll want to use advanced option and do a dd copy of the boot_b image over to the boot_a image (replacing the twrp u just put there). Then, u use the twrp file in the 'inject' option to ramdisk inject the twrp file into the original boot partition you just copied from b_slot.

it's confusing, maybe wait a bit and someone with more experience will get it done. Or u can send me your boot_a partition and I'll do it.

cheers

 

[iannisb]

Well a couple of things, 1) with newer firmware, you can no longer 'fastboot boot twrp'. The way to create a boot loader with twrp in it, you have to do 'ramdisk inject'.

I explain that because, near as I can tell, no one has created your needed boot partition with twrp injected into it. It exists for many other versions, but 30d is very new.

2) The 'overview' of how u do it goes like this; Use qfil to flash to boot_a an older version of yoour type of firmware like this one for 30b, that way u can exit qfil and go directly to twrp. Once in twrp, you'll want to use advanced option and do a dd copy of the boot_b image over to the boot_a image (replacing the twrp u just put there). Then, u use the twrp file in the 'inject' option to ramdisk inject the twrp file into the original boot partition you just copied from b_slot.

it's confusing, maybe wait a bit and someone with more experience will get it done. Or u can send me your boot_a partition and I'll do it.

cheers

I ve decompressed the dz from 30D and i found two boot partitions :
boot.img_65286 and boot.img_163830
How do i tell which is a and b?

 

[AsItLies]

I ve decompressed the dz from 30D and i found two boot partitions :
boot.img_65286 and boot.img_163830
How do i tell which is a and b?

They are identical. The way you can verify that is look at the file sizes, pretty good indicator, but even better would be to run an md5 checksum, they will be identical.

cheers

 

[iannisb]

Yes they appear to be identical.
Can you do it for me please? I dont have the experience that you obviously have...

 

[AsItLies]

Yes they appear to be identical.
Can you do it for me please? I dont have the experience that you obviously have...

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

 

[iannisb]

i understand. i had the kdz downloaded and extraction wasnt that difficult with windowsLGfirmwareextract tool.
Thanks you!
i am reading about qfil as we speak

 

[iannisb]

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

Do i have to format data and remove the dm-verity?
Ideally i would like to keep the encryption while i have root through magisk

is there a link for the dm-verity?
Thanks again!

 

[AsItLies]

Do i have to format data and remove the dm-verity?
Ideally i would like to keep the encryption while i have root through magisk

is there a link for the dm-verity?
Thanks again!

common question, the thing is that if you go that way, you can't back up data with twrp, obviously it will be encrypted and unable to do that. There could be more that I"m not aware of, problems doing it that way I mean. I've never myself so not sure.

this is link to dm-verity. I'd say use it and not worry about data not being encrypted, basically, if u loose the device, a hacker could delete finger print and screen lock and get into device even if encrypt. So... don't lose the device

 

[iannisb]

common question, the thing is that if you go that way, you can't back up data with twrp, obviously it will be encrypted and unable to do that. There could be more that I"m not aware of, problems doing it that way I mean. I've never myself so not sure.

this is link to dm-verity. I'd say use it and not worry about data not being encrypted, basically, if u loose the device, a hacker could delete finger print and screen lock and get into device even if encrypt. So... don't lose the device

 

[iannisb]

Thank you !
Everything worked fine!
Cheers!

 

[martinmh24]

[QUOTE = "AsItLies, publicación: 84565331, miembro: 2129545"]
dame un poco, lo haré. Pero primero, ¿te das cuenta de que tendrás que usar qfil para cargar esto? No se puede hacer con fastboot. Menciono eso porque te tomaste la molestia de descomponer un kdz a dz en imágenes para obtener el archivo boot_a. pero, ¿con qfil podría haber leído los datos de la partición y guardarlos?

Lo haré de todos modos, pero debe actualizarse con qfil, luego seguir las instrucciones adicionales.

aquí hay un enlace de gdrive a su ebw 30d con twrp ramdisk inyectado. Recuerde, use qfil para hacer una copia de seguridad de boot_a existente (aunque ya está eso), luego actualice este archivo. Una vez que haya parpadeado, salga de qfil y mantenga presionado el botón de encendido y apagado para salir del modo edl en el dispositivo. Mantenga presionado hasta el logotipo de lg, luego suelte rápidamente solo pwr y luego vuelva a aplicarlo. Eso trae a twrp. Seleccione cancelar si solicita pw, deslice para permitir modificaciones, formatee los datos y luego reinicie la recuperación. Una vez de vuelta en twrp flash magisk y dm-verity.

debería estar todo listo entonces. Salud
[/CITA]
amigo, se ve que sabes del tema, pase twrp por fastboot a mi v40 pero no abre twrp, tengo la rom koreana android 10 30f, podrias ayudarme a arrancar twrp para rootear e instalar una custom rom?

 

[iannisb]

common question, the thing is that if you go that way, you can't back up data with twrp, obviously it will be encrypted and unable to do that. There could be more that I"m not aware of, problems doing it that way I mean. I've never myself so not sure.

this is link to dm-verity. I'd say use it and not worry about data not being encrypted, basically, if u loose the device, a hacker could delete finger print and screen lock and get into device even if encrypt. So... don't lose the device

Ever since i rooted my v40 with magisk and your help i ve been wanting to get rid of this annoying message.
I read that i have to modify cust_path_mapping.cfg in root/oem/op but the privileges/rights can not be changed even though i am rooted.
Is there anything you can advise me to do?
Thank you!

 

[AsItLies]

Ever since i rooted my v40 with magisk and your help i ve been wanting to get rid of this annoying message.
I read that i have to modify cust_path_mapping.cfg in root/oem/op but the privileges/rights can not be changed even though i am rooted.
Is there anything you can advise me to do?
Thank you!

Yes, there are 2 things to consider; 1) to be able to edit that file (or any others) you need to disable vbmeta. It's a basic thing you have to do with fastboot, pretty easy really, follow this to download and read the txt file.

I've not had much luck doing it that way though, some have, so worth a try I guess. But the way that has always worked for me, is to (unfortunately you will be starting over to do this), remove all accounts / fingerprints, use LGUP to do part d/l again of the rom u want to use, then boot to start up (which is normal procedure for part d/l), then shut device off and go back to LGUP.

now, with same exact rom you just used, do a refurbish.

It seems what happens is that the s/n and imei and that nt code info gets propagated throughout the system (especially the ftm partition) during these procedures, and for it to work correctly (with cross flashing) it needs to do both part d/l and refurbish.

cheers

 

[iannisb]

Yes, there are 2 things to consider; 1) to be able to edit that file (or any others) you need to disable vbmeta. It's a basic thing you have to do with fastboot, pretty easy really, follow this to download and read the txt file.

I've not had much luck doing it that way though, some have, so worth a try I guess. But the way that has always worked for me, is to (unfortunately you will be starting over to do this), remove all accounts / fingerprints, use LGUP to do part d/l again of the rom u want to use, then boot to start up (which is normal procedure for part d/l), then shut device off and go back to LGUP.

now, with same exact rom you just used, do a refurbish.

It seems what happens is that the s/n and imei and that nt code info gets propagated throughout the system (especially the ftm partition) during these procedures, and for it to work correctly (with cross flashing) it needs to do both part d/l and refurbish.

cheers

I copied both vbmeta_a.img and vbmeta_b.img from dev/block
i run the command but i got this error
fastboot: unrecognised option `--disable-verity'

 

[AsItLies]

I copied both vbmeta_a.img and vbmeta_b.img from dev/block
i run the command but i got this error
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