[ROOT][MAGISK][OREO/PIE] Magisk 18.0+

[rcurious]

At last I learned how to make boot_v20e-magisk.img by myself. It seems nothing special just need to download correct firmware for phone and use Lg firmware extract tool to extract boot.img, then use Magisk, which is installed on the phone to patch extracted boot.img.

 

[Syrop]

#link removed#
boot 20e_eur for g710em from kdz
OP opens
magisk 20.1

 

[stel67]

https://drive.google.com/open?id=12j8GNtUuI7YccYf1SnpZ1JsrYkAL3-gc
boot 20e_eur for g710em from kdz
OP opens
magisk 20.1

Does the sound work after applying this ?

 

[Syrop]

Does the sound work after applying this ?

sure
it works

 

[stel67]

@Syrop
This is strange.
After flashing it, phone boots ok but all sounds are off. Even the dialer does not make any sound.
This is how I flashed it:
adb reboot bootloader
fastboot flash boot_a boot_20e_op_magisk.img
fastboot flash boot_b boot_20e_op_magisk.img
fastboot reboot
How come the size of this boot img is only 25 MB ?
The one coming with kdz is 67 MB.

[edit]
I also patched the boot.img coming with G710EM20e_00_1115.kdz
The size is the patched boot image is identical to yours (25.477.120 bytes ), the files do not match.
Could it be a corruption on the google drive ?

 

[Syrop]

@Syrop
This is strange.
After flashing it, phone boots ok but all sounds are off. Even the dialer does not make any sound.
This is how I flashed it:
adb reboot bootloader
fastboot flash boot_a boot_20e_op_magisk.img
fastboot flash boot_b boot_20e_op_magisk.img
fastboot reboot
How come the size of this boot img is only 25 MB ?
The one coming with kdz is 67 MB.

[edit]
I also patched the boot.img coming with G710EM20e_00_1115.kdz
The size is the patched boot image is identical to yours (25.477.120 bytes ), the files do not match.
Could it be a corruption on the google drive ?

i changed boot.product.lge.op_verity from 1 to 0 also

 

[stel67]

@Syrop , I know you answered that before. What exactly does this change mean?

 

[Syrop]

@Syrop , I know you answered that before. What exactly does this change mean?

you can modify /oem/OP

 

[jonsat]

At last I learned how to make boot_v20e-magisk.img by myself. It seems nothing special just need to download correct firmware for phone and use Lg firmware extract tool to extract boot.img, then use Magisk, which is installed on the phone to patch extracted boot.img.

Me too wish to perform this action without waiting every time for other's good willing work...
One thing confusing me: when I extracted latest kdz (20e), relative dz file contains TWO boot.img files, boot.img_65286 and boot.img_163830. Which file is the right one? Size seems identical, but I prefer not to risk messing around with boot files.
Can you explicitate a little more how to proceed?

 

[rcurious]

Me too wish to perform this action without waiting every time for other's good willing work...
One thing confusing me: when I extracted latest kdz (20e), relative dz file contains TWO boot.img files, boot.img_65286 and boot.img_163830. Which file is the right one? Size seems identical, but I prefer not to risk messing around with boot files.
Can you explicitate a little more how to proceed?

They are identical, just names are different. Take one of these. And so you have a working phone with magisk app? Then copy this file to phone open Magisk app and choose Magisk install - > select and patch a file -> chose that file and patch. Now you have boot file with magisk, copy that file from phone to PC. Than just follow as usual.

 

[jonsat]

They are identical, just names are different. Take one of these. And so you have a working phone with magisk app? Then copy this file to phone open Magisk app and choose Magisk install - > select and patch a file -> chose that file and patch. Now you have boot file with magisk and just follow later procedure written hear in topic.

Thanks for clarifing things. After my post, I realized that the two boot files were identical, just because they belong to boot_a and boot_b partitions. I should have known that!

 

[rcurious]

@Syrop
[edit]
I also patched the boot.img coming with G710EM20e_00_1115.kdz
The size is the patched boot image is identical to yours (25.477.120 bytes ), the files do not match.
Could it be a corruption on the google drive ?

You must be sure you have firmware, which is for you model. For example G710EM20e_00_1114.kdz and G710EM20e_00_1115.kdz boot images content is different, the same size doesn't mean they are identical. You can check that country your phone belongs to with IMEI in the firmware.
site. Magisk makes file smaller. Mine was also 25MB, but everything is good. I don't know how author of the topic retains 60MB. Maybe he plays with partitioning tools, because these images are like Linux ext2/ext4 partitions.

 

[kadyt]

@Syrop
This is strange.
After flashing it, phone boots ok but all sounds are off. Even the dialer does not make any sound.
This is how I flashed it:
adb reboot bootloader
fastboot flash boot_a boot_20e_op_magisk.img
fastboot flash boot_b boot_20e_op_magisk.img
fastboot reboot
How come the size of this boot img is only 25 MB ?
The one coming with kdz is 67 MB.

[edit]
I also patched the boot.img coming with G710EM20e_00_1115.kdz
The size is the patched boot image is identical to yours (25.477.120 bytes ), the files do not match.
Could it be a corruption on the google drive ?

Has this happened to you with @Syrop's patched boot? It has happened to me with my own patched boot

Also for me, the boot extracted from the KDZ was 67 MB and after patching it it was 24 MB

I patched boot.img_65286 of the two boots in the kdz (see below)

Now there are not any sounds: No sounds at boot, Tidal and Spotify do not work, Poweramp says it cannot start the audio engine ...

Have you fixed it? I don't know how to follow now, if flashing the stock v20e boot again or perform a factory reset or what ...

Also after flashing the patched boot it said that the microsd was corrupted (??). But then in Windows it did not have any problems but the phone refused to recognize it (it had been working without problems just till before flashing the patched boot) I had to format it in the phone ...

For the previous OTA I patched and flashed the boot without any problems

Me too wish to perform this action without waiting every time for other's good willing work...
One thing confusing me: when I extracted latest kdz (20e), relative dz file contains TWO boot.img files, boot.img_65286 and boot.img_163830. Which file is the right one? Size seems identical, but I prefer not to risk messing around with boot files.
Can you explicitate a little more how to proceed?

I also realized of that, I would say that in the previous OTA there was only a boot and it was boot.img. Maybe I'm wrong but I don't remember to have found names like and these & two boots

I patched boot.img_65286 and ignored boot.img_163830 and it seems something did not go well this time

Thanks for clarifing things. After my post, I realized that the two boot files were identical, just because they belong to boot_a and boot_b partitions. I should have known that!

I'm wondering, should the two boots be patched and flash boot.img_65286_patched in boot_a and boot.img_163830_patched in boot_b?

Again, just wondering, if doing this would fix things

But this time I prefer to wait for more opinions before doing anything else

 

[stel67]

Has this happened to you with @Syrop's patched boot? It has happened to me with my own patched boot

Also for me, the boot extracted from the KDZ was 67 MB and after patching it it was 24 MB

I patched boot.img_65286 of the two boots in the kdz (see below)

Now there are not any sounds: No sounds at boot, Tidal and Spotify do not work, Poweramp says it cannot start the audio engine ...

Have you fixed it? I don't know how to follow now, if flashing the stock v20e boot again or perform a factory reset or what ...

Also after flashing the patched boot it said that the microsd was corrupted (??). But then in Windows it did not have any problems but the phone refused to recognize it (it had been working without problems just till before flashing the patched boot) I had to format it in the phone ...

For the previous OTA I patched and flashed the boot without any problems



I also realized of that, I would say that in the previous OTA there was only a boot and it was boot.img. Maybe I'm wrong but I don't remember to have found names like and these & two boots

I patched boot.img_65286 and ignored boot.img_163830 and it seems something did not go well this time



I'm wondering, should the two boots be patched and flash boot.img_65286_patched in boot_a and boot.img_163830_patched in boot_b?

Again, just wondering, if doing this would fix things

But this time I prefer to wait for more opinions before doing anything else

Hi, I had exactly the same problems after using Syrop's patched boot.img
(no sound, corrupted SD card).
To solve them, I used LG bridge, the option to restore recovery.
This
A) Fixed the sound problem
B) Let me got the proper kdz for my phone
After getting the kdz, I got the boot.img and patched it.
So first use LG bridge to get back the proper boot img.

 

[Syrop]

ops
sorry guys, but for me everything works correctly
will remove patched boot

 

[jonsat]

ops
sorry guys, but for me everything works correctly
will remove patched boot

@kadyt @stel67
I can only say that I've had no trouble using Syrop's patched v20e boot. Sound ok, no sd corruption.

 

[stel67]

ops
sorry guys, but for me everything works correctly
will remove patched boot

No need for asking sorry. Such things happen.
I had no problem at all with your previous 20d boot.img.
What was the name of the kdz you used this time?

 

[Syrop]

No need for asking sorry. Such things happen.
I had no problem at all with your previous 20d boot.img.
What was the name of the kdz you used this time?

G710EM20e_00_1114.kdz

 

[kadyt]

Hi, I had exactly the same problems after using Syrop's patched boot.img
(no sound, corrupted SD card).
To solve them, I used LG bridge, the option to restore recovery.
This
A) Fixed the sound problem
B) Let me got the proper kdz for my phone
After getting the kdz, I got the boot.img and patched it.
So first use LG bridge to get back the proper boot img.

Thank you very much for the info!!

I understand that now you are in 20e stock without magisk nor root, right?

ops
sorry guys, but for me everything works correctly
will remove patched boot

@kadyt @stel67
I can only say that I've had no trouble using Syrop's patched v20e boot. Sound ok, no sd corruption.

As I said I did not use @Syrop's boot, I patched it myself from the .kdz like I did with the previous OTA - without problems then - and I've had the same problems than @stel67 had using @Syrop's boot

Why it works for some and fails for others ... ?????

I patched the boot extracted from G710EM20e_00_1115.kdz (G71020e00OPENEU1115.dz in it, it has two boots, boot.img_65286 and boot.img_163830, I patched boot.img_65286 and flashed it in boot_a and boot_b, I ignored boot.img_163830)

---------- Post added at 11:18 AM ---------- Previous post was at 10:57 AM ----------

@Syrop
This is strange.
After flashing it, phone boots ok but all sounds are off. Even the dialer does not make any sound.
This is how I flashed it:
adb reboot bootloader
fastboot flash boot_a boot_20e_op_magisk.img
fastboot flash boot_b boot_20e_op_magisk.img
fastboot reboot
How come the size of this boot img is only 25 MB ?
The one coming with kdz is 67 MB.

[edit]
I also patched the boot.img coming with G710EM20e_00_1115.kdz
The size is the patched boot image is identical to yours (25.477.120 bytes ), the files do not match.
Could it be a corruption on the google drive ?

G710EM20e_00_1114.kdz

@stel67 so you patched a boot coming from G710EM20e_00_1115.kdz like me? And then you had the same problems?

I first understood that you had used @Syrop's patched boot but if his boot comes from G710EM20e_00_1114.kdz and gives no problem, maybe the problem is in the .kdz version

 

[stel67]

@kadyt, after using LG bridge to restore recovery I flashed the patched boot img generated by magisk.
Now I am fine (root).