boot issue with a mt6580 tablet on android 12 gsi

[Leaft-prog]

I have a boot issue with my mediacom iyo 8 tablet (mt6580 soc) with android 12, the tablet has pie vendor requiring arm32-binder64 A/B system image, with android 11 boots without problem, but with android 12 doesn't boot. Of course i wiped data and cache using stock recovery but its stuck in the boot screen (not the android logo boot screen).

[phhusson]

Can you grab logs? What kind of "doesn't boot" is it?

[Leaft-prog]

Its stuck on the mediacom logo (before android boot), i don't know if i can grab logs because it cannot boot on the system partition.

[Leaft-prog]

[phhusson]

(I thought your "mediacom" was a typo of "mediatek". nope, fun. And fun logo too) Well if you do adb devices, does it show your device?

Le mer. 23 févr. 2022 à 15:07, Leaft-prog @.***> a écrit :

[image: IMG20220223150638] https://user-images.githubusercontent.com/83707338/155335188-3b3c707d-cd60-4611-88fe-e3b985b4096a.jpg

— Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/2208#issuecomment-1048816654, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OST6E7Q4IJL22QS2JDU4TSYRANCNFSM5PCGL7PA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID: @.***>

[Leaft-prog]

Saddly it doesn't work

[theh0riz0n]

did you removed dm-verity (Android Verified Boot) by flashing vbmeta? i had that problem on my motorola but only just was an vbmeta problem.

[Leaft-prog]

Yes i also did that i forgot to mention

[Leaft-prog]

Maybe later i will try again with the new release maybe its fixed

[theh0riz0n]

You could try to go through installing pre release versions of A12 when on 400.h fingerprint sensor on Galaxy A50 was working flawlessly now it little bit off. also on 400.h fixed boot issues on most devices when i was testing on mine.

[Leaft-prog]

All versions of android 12 has the same issue on that device (android 11 works everything except audio codecs, android 10 boots but it has screen orientation issues)

[theh0riz0n]

All versions of android 12 has the same issue on that device (android 11 works everything except audio codecs, android 10 boots but it has screen orientation issues)

thats kinda bad. if you have stock firmware extract it and you could add libraries to own built gsi. althrough its time consuming. since my daily driver is a cheap motorola it has its own issues. nfc not working ota glitching but i think it's a global issue.

[Leaft-prog]

Yes i have stock the stock firmware (not sources because its a cheap chinese tablet)

[theh0riz0n]

Yes i have stock the stock firmware (not sources because its a cheap chinese tablet)

i think you would need just extract vendor and add it when building and it should fix issues that you're facing right now.

[Leaft-prog]

Ok i will try that solution if android 12.1 dosen't work

[Leaft-prog]

Sadly android 12.1 dosen't boot either, the only difference now its that it reboots maybe i will try the building solution or wait for android 13 release date

[byf3332]

The problem is, mt6580 is purely a 32bit processor and will never boot up 64 bit system:( binder64 is for devices with 64bit processor but on 32bit mode.

[phhusson]

@byf3332 that's plain wrong. binder64 is a protocol, not an execution format or assembly. It could work just as well on a 8 bit CPU.

[Leaft-prog]

With binder64 using android 11 works (also treble info says that the device needs a binder64 image) I also i was wrong, it's not an mt6580 but its an mt8321 (in the sp flash tool says mt6580, but in the mediacom site and the build prop says mt8321)

[Leaft-prog]

Issue fixed in Android 13