changing boot.img flag

safin252
Senior Member

192

23-04-2023, 05:16 AM

#1

how can i change flag 0 to 2 in ubuntu using avbtool? python2 and 3 is installed

AutoResponder
Verified Account

609

23-04-2023, 05:16 AM

#2

Thank you for reaching out for support. Due to high demand, our free support services may experience some delays in response time. We apologize for any inconvenience this may cause.
Alternatively, we offer private support where you can receive dedicated attention and prompt support. These sessions are designed to provide personalized solutions to your specific needs.
If you are interested in scheduling a private session, please visit https://www.hovatek.com/remote

maxpayne
Intern

4,033

24-04-2023, 03:00 PM

#3

(23-04-2023, 05:16 AM)safin252 how can i change flag 0 to 2 in ubuntu using avbtool? python2 and 3 is installed

Do you mean in vbmeta.img?

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.

safin252
Senior Member

192

24-04-2023, 08:07 PM

#4

(24-04-2023, 03:00 PM)maxpayne
(23-04-2023, 05:16 AM)safin252 how can i change flag 0 to 2 in ubuntu using avbtool? python2 and 3 is installed

Do you mean in vbmeta.img?

No ..boot img...?? Flag 2 means no verify am i right?

qwerty_in_me
Newbie

1

25-04-2023, 06:11 PM

#5

(24-04-2023, 08:07 PM)safin252
(24-04-2023, 03:00 PM)maxpayne
(23-04-2023, 05:16 AM)safin252 how can i change flag 0 to 2 in ubuntu using avbtool? python2 and 3 is installed

Do you mean in vbmeta.img?

No ..boot img...?? Flag 2 means no verify am i right?

I've dealt with boot images quite a bit, but I'm unaware of numeric flags in/on them. Closest thing I do know would be the mkbootimg args whitch are all in hex/ASCII

if you're trying to disable verified boot, that's a LittleKernel thing so you'd need to make an empty vbmeta image with avbtool (if memory serves me yet), while in LK's fastboot disable verification and verity then flash the empty vbmeta to the vbmeta partition (some phones have the vbmeta in the boot partiton, though I haven't dealt with that and only know because of magisk).

now rereading the thread and my own answer, I THINK you have a phone with vbmeta in the boot image, and since I haven't dealt with that I'd recomend you to read the official avbtool manpage, alternatively, unpack the boot image with unpack_bootimg (saving the mkbootimg args as according to the help page of unpack_bootimg), make an empty vbmeta image, replace the extracted vbmeta with the generated one and then repack & reflash

View a Printable Version

Users browsing this thread:
1 Guest(s)

Find us

Call us

Mail us

Useful Links

Actions