How do i change patch date to use in dsu

[Osanosa]

Hi there! Sorry to bother with stupid questions, but I really want to use this rom for dual booting in dsu and testing stuff but it wont boot if i have main system with newer patch date
i have tried editing build prop strings like timestamp and date trying to make it 2099 so there wouldnt be conflicts but it doesnt work out
could you give an advice on can i edit unpacked rom to bump security patch date or else? where are these values being stored and read from?

[ChonDoit]

Hi there! Sorry to bother with stupid questions, but I really want to use this rom for dual booting in dsu and testing stuff but it wont boot if i have main system with newer patch date i have tried editing build prop strings like timestamp and date trying to make it 2099 so there wouldnt be conflicts but it doesnt work out could you give an advice on can i edit unpacked rom to bump security patch date or else? where are these values being stored and read from?

Edit security patch/date on props will do nothing more than a visual change.

• Check your vndk with Treble info
• Which device is it?
• Share logs.

Otherwise can't help

[Osanosa]

Edit security patch/date on props will do nothing more than a visual change.

• Check your vndk with Treble info • Which device is it? • Share logs.

Otherwise can't help

no like i don't have any issues with booting unless main rom is newer
currently i have a recent build of A16 installed, but i want to use A13 in DSU for testing purposes. this latest release here has newer build date i can boot into it via DSU but if I update main rom and this release will have older build date that main system it wont allow to boot
like vbmeta and stuff i'm not too familiar with that

I just want this rom with higher build date so there wont be downgrade protection and i could boot it in DSU

[ChonDoit]

Edit security patch/date on props will do nothing more than a visual change.
• Check your vndk with Treble info • Which device is it? • Share logs.
Otherwise can't help

no like i don't have any issues with booting unless main rom is newer currently i have a recent build of A16 installed, but i want to use A13 in DSU for testing purposes. this latest release here has newer build date i can boot into it via DSU but if I update main rom and this release will have older build date that main system it wont allow to boot like vbmeta and stuff i'm not too familiar with that

I just want this rom with higher build date so there wont be downgrade protection and i could boot it in DSU

Security patch date (what you saw on about system) is a simple visual string, affects nothing. Changes are done internally on system/kernel/vendor. Take logs if you want to figure out why can't boot.

[Osanosa]

Security patch date (what you saw on about system) is a simple visual string, affects nothing. Changes are done internally on your main system/vendor. Take logs if you want to figure out why can't boot.

https://source.android.com/docs/core/ota/dynamic-system-updates#rollback_protection

[Osanosa]

can i just edit hex like this or do i need to use avb

[ChonDoit]

Security patch date (what you saw on about system) is a simple visual string, affects nothing. Changes are done internally on your main system/vendor. Take logs if you want to figure out why can't boot.

https://source.android.com/docs/core/ota/dynamic-system-updates#rollback_protection

You can disable AVB flashing vbmeta with disable flags.