Development [DEV][EOL] Vbmeta Patcher, Devinfo Patcher, and Boot Image Tool

[capntrips]

log2

Well that happened earlier in the process than I expected. See if this resolves it for you:

v1.0.0-alpha04-simplified-paths

If not, let me know where you can find the paths to your vbmeta partitions on your device and if you have an fstab file somewhere in your /vendor/etc folder.

Mine is Samsung Device. A52s.

I should note that I know little about Samsung devices. I'm going to assume you have a means of flashing a clean copy of your vbmeta partition if something goes wrong.

 

[theghostkill]

v1.0.0-alpha04-simplified-paths

vbmeta - /dev/block/bootdevice/by-name/
vbmeta_system - /dev/block/bootdevice/by-name/

Also attached vbmeta.img & vbmeta_system.img with fstab files.

I can flash stock vbmeta is something goes wrong, no problem. Btw, I'm trying to remove all those AVB flags.

 

[capntrips]

vbmeta - /dev/block/bootdevice/by-name/
vbmeta_system - /dev/block/bootdevice/by-name/

Also attached vbmeta.img & vbmeta_system.img with fstab files.

I assume you got a new exception? Can you post the stacktrace?

To confirm, neither /dev/block/by-name/vbmeta_a nor /dev/block/by-name/vbmeta_b exist?

Can you give me the output of each of these:

getprop ro.boot.fstab_suffix
getprop ro.boot.hardware
getprop ro.boot.hardware.platform

One of those should be qcom. Was fstab.qcom in /vendor/etc? If not, was it in any of /odm/etc, /, or /first_stage_ramdisk?

Also, what is the output of getprop ro.boot.slot_suffix?

 

[theghostkill]

I assume you got a new exception? Can you post the stacktrace?

LOG3 - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com

Also got an popup error Failed to get magic

To confirm, neither /dev/block/by-name/vbmeta_a nor /dev/block/by-name/vbmeta_b exist?

No, A52s doesn't have slots. So, only vbmeta and not any of _a or _b

Can you give me the output of each of these:

getprop ro.boot.fstab_suffix

default

getprop ro.boot.hardware

qcom

getprop ro.boot.hardware.platform

no output - empty

ro.board.platform := lahaina

One of those should be qcom. Was fstab.qcom in /vendor/etc? If not, was it in any of /odm/etc, /, or /first_stage_ramdisk?

fstab.qcom and two other files in that zip was in vendor/etc
not in odm/etc
there is first_stage_ramdisk folder

Also, what is the output of getprop ro.boot.slot_suffix?

no output - empty

 

[capntrips]

No, A52s doesn't have slots. So, only vbmeta and not any of _a or _b

I'll assume that is the issue for now. See if this one works for you:

v1.0.0-alpha04-allow-non-ab

If not, does /dev/block/by-name/vbmeta exist?

 

[theghostkill]

I'll assume that is the issue for now. See if this one works for you:

v1.0.0-alpha04-allow-non-ab

https://pastebin.com/H6ifq4i1

If not, does /dev/block/by-name/vbmeta exist?

My mistake
vbmeta & vbmeta_system is in

/dev/block/bootdevice/by-name

as well as in

/dev/block/by-name

 

[capntrips]

log4

vbmeta is in /dev/block/bootdevice/by-name as well as in /dev/block/by-name

Are you able to run any of the following in a root shell:

dd if=/dev/block/by-name/vbmeta bs=4 count=1 status=none
busybox dd if=/dev/block/by-name/vbmeta bs=4 count=1 status=none
/data/adb/magisk/busybox dd if=/dev/block/by-name/vbmeta bs=4 count=1 status=none

If so, do any of them output AVB0? Note that dd it doesn't print a newline after output, so it may print before the prompt.

 

[theghostkill]

Are you able to run any of the following in a root shell:

dd if=/dev/block/by-name/vbmeta bs=4 count=1 status=none
busybox dd if=/dev/block/by-name/vbmeta bs=4 count=1 status=none
/data/adb/magisk/busybox dd if=/dev/block/by-name/vbmeta bs=4 count=1 status=none

If so, do any of them output AVB0? Note that dd it doesn't print a newline after output, so it may print before the prompt.

Yes, for first and third command, getting AVB0 at the beginning of the new line

For second getting this -

/system/bin/sh: busybox: inaccessible or not found

 

[capntrips]

Don't know what you mean by this

For example, if I issue the above command for one of the slots on a Pixel 5a, it looks like this:

barbet:/ $ su
barbet:/ # dd if=/dev/block/by-name/vbmeta_a bs=4 count=1 status=none
AVB0barbet:/ #

At first glance, it appears that there was no output, but the last line is AVB0barbet, rather than just barbet.

In any case, I took a closer look at the previous stacktrace, and I think I figured out the problem:

v1.0.0-alpha04-allow-non-ab2

Edit: I'm fading fast, so it may be morning before I make any additional replies.

 

[theghostkill]

For example, if I issue the above command for one of the slots on a Pixel 5a, it looks like this:

barbet:/ $ su
barbet:/ # dd if=/dev/block/by-name/vbmeta_a bs=4 count=1 status=none
AVB0barbet:/ #

At first glance, it appears that there was no output, but the last line is AVB0barbet, rather than just barbet.

In any case, I took a closer look at the previous stacktrace, and I think I figured out the problem:

v1.0.0-alpha04-allow-non-ab2

Edit: I'm fading fast, so it may be morning before I make any additional replies.

Yes, for first and third command, getting AVB0 at the beginning of the new line like yours AVB0barbet:/

For second getting this -
Code:
/system/bin/sh: busybox: inaccessible or not found

 

[theghostkill]

For example, if I issue the above command for one of the slots on a Pixel 5a, it looks like this:

barbet:/ $ su
barbet:/ # dd if=/dev/block/by-name/vbmeta_a bs=4 count=1 status=none
AVB0barbet:/ #

At first glance, it appears that there was no output, but the last line is AVB0barbet, rather than just barbet.

In any case, I took a closer look at the previous stacktrace, and I think I figured out the problem:

v1.0.0-alpha04-allow-non-ab2

Edit: I'm fading fast, so it may be morning before I make any additional replies.

Yes, the app is working now. Thank you for giving your time.

 

[bzz11g]

Hi @capntrips ! Have you tried updating your phone over the air with the new Magisk v25?
I updated my phone before it became available, but on our local forum people write that the root did not appear after the update and that they had to patch the kernel and install it via fastboot on PC

 

[capntrips]

Have you tried updating your phone over the air with the new Magisk v25?

Yes, I installed the June update OTA via System Update after updating to 25001, and it worked without an issue. I have rebooted a few times since, and I never lost root.