[4.14][10.0][TAMA][AKARI] Broken Treble

[Gouster4]

Platform:Tama
Device:Akari
Kernel version:4.14
Android version:10
Software binaries version:v3

Previously working on
I was never able to boot any GSI on sodp base on Akari

Description
After flashing any GSI (last time tryed Android 11 gsi) i ended up stuck at sony logo.

Symptoms
Stuck at sony logo

How to reproduce
download any gsi
fastboot flash system gsi.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase userdata

Additional context
I tryed also without wiping userdata,
without --disable-verity --disable-verification
and also without flashing vbmeta.
Always ended up stuck at sony logo

[MarijnS95]

I tried to reproduce your situation but the Android 11 GSI boots "fine" on Bahamut. There should not be anything specific preventing Tama/Akari from doing so either.

vbmeta appropriately covers only the system partition, and is fine to be left enabled. You should always wipe userdata.

As for Previously working on: Does a normal flashed SODP work correctly, before a GSI is flashed over it?

Please enable adb in the vendor build and see if a log can be obtained:

PRODUCT_PROPERTY_OVERRIDES += \
    ro.debuggable=1 \
    ro.adb.secure=0

[Gouster4]

I tried to reproduce your situation but the Android 11 GSI boots "fine" on Bahamut. There should not be anything specific preventing Tama/Akari from doing so either.

vbmeta appropriately covers only the system partition, and is fine to be left enabled. You should always wipe userdata.

As for Previously working on: Does a normal flashed SODP work correctly, before a GSI is flashed over it?

Please enable adb in the vendor build and see if a log can be obtained:

PRODUCT_PROPERTY_OVERRIDES += \
    ro.debuggable=1 \
    ro.adb.secure=0

yes, sodp rom booted fine.
will try to catch logs

[Gouster4]

device isnt seen by adb. even after PROPERTY_OVVERIDES.
Sodp rom shows:
adb shell
akari:/ # getprop ro.debuggable
1
akari:/ # getprop ro.adb.secure
0
akari:/ #

[MarijnS95]

That comment clearly shows that you have access to adb?

Nvm, I am confused with a different situation, where having access to adb shell without having access to adb logcat is called "I have no adb" 🤦‍♂️.

[Gouster4]

where having access to adb shell without having access to adb logcat is called "I have no adb" 🤦‍♂.

used adb shell in sodp rom with that PROPERTY_OVVERIDES to check if it really changed props.
Then after flashing GSI and erasing data, i have no adb access.

How else i can catch logs?

[Gouster4]

pstore

[Gouster4]

MartinX3 found from pstore it wants keymaster 4.0.
Needs to be faked on keymaster 3.0 devices like Akari and older.
Good Luck if u guys would do that.

[MartinX3]

I just say it doesn't work because of keymaster 3.0 (it is many times mentioned in the pstore everywhere) and that it works on devices with keymaster 4.0 like the XZ3 :D

[MartinX3]

Could be the same issue like
#547
#527

[MarijnS95]

MartinX3 found from pstore it wants keymaster 4.0.

That is totally incorrect.

Martin reminded me again of the fact that it only seems to work on KM4 devices (Griffin and Bahamut from Kumano, and Akatsuki), which instantly lit a bulb 💡
We had problems with versioning before in KM4, but as it turns out the KM3 implementation does something finicky too. It requires ro.build.version.release to be a version number (like Android 8.1) and doesn't allow it to be a letter like R on the Android 11 preview GSI.
If this service refuses to start the phone will refuse to boot.

The easiest way is to trick it by overriding in the vendor image with:

PRODUCT_PROPERTY_OVERRIDES += \
  ro.build.version.release=11

[MarijnS95]

@MartinX3 Yoshino devices are a different game. All except Maple do Only maple does not have a vendor partition, just like Loire and Tone. All the necessary files reside on /system/vendor which does not persist a GSI flash.

@ix5 Has done work on that and afaik also distributes working builds on XDA. The last solution reuses the unused cache partition, or wraps vendor and odm in a single one, iirc.