search

phhusson / treble_experimentations

Notes about tinkering with Android Project Treble
3.35k stars 658 forks source link

Cant get GSIs to work on Mediatek 6580 generic device (bootloop) #1661

Open AtamiiX opened 3 years ago

AtamiiX commented 3 years ago

So, for the last 2 months i have been trying to get GSIs work on Aligator S4090 a.k.a upgraded Version of Irbis SP402 with more memory. I have done everything to get it working. Flashing via fastboot, TWRP, flashing over system, wiping userdatas, caches and disabling force verifies, rooting. Still every i tried (Android GO, Pixel Experience, AOSP) GSI is stuck at boot animation. Then it fades and shuts off. I know nobody will probably help me but its worth a try. Thanks

phhusson commented 3 years ago

I got my GSIs to boot just fine on MT6580 devices, so your title is wrong. (Not Android 11 GSIs though, all my MT6580 devices are battery dead.).

What's your vendor Android version? Which of my AOSP GSIs did you try? Do you have adb working when stuck on bootanimation? If so, provide logs.

Your last sentence makes me want to not answer you, stop with that passive-aggressive bullshit.

Le ven. 8 janv. 2021 à 10:45, AtamiiX notifications@github.com a écrit :

So, for the last 2 months i have been trying to get GSIs work on Aligator S4090 a.k.a upgraded Version of Irbis SP402 with more memory. I have done everything to get it working. Flashing via fastboot, TWRP, flashing over system, wiping userdatas, caches and disabling force verifies, rooting. Still every i tried (Android GO, Pixel Experience, AOSP) GSI is stuck at boot animation. Then it fades and shuts off. I know nobody will probably help me but its worth a try. Thanks

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/1661, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4ORKJCC32DW4ETLVUALSY3H2XANCNFSM4V2GQOLA .

AtamiiX commented 3 years ago

Sorry for that anyways i was able to boot A10 lineage with some mods done to boot.img and twrp. Also i can confirm 11 does not work. Thanks for your answer.

phhusson commented 3 years ago

Got logs?

Le ven. 8 janv. 2021 à 13:59, AtamiiX notifications@github.com a écrit :

Sorry for that anyways i was able to boot A10 lineage with some mods done to boot.img and twrp. Also i can confirm 11 does not work. Thanks for your answer.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/1661#issuecomment-756743024, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OTRVQMOGKFHSU5JDT3SY36UNANCNFSM4V2GQOLA .

AtamiiX commented 3 years ago

I cant get the logs (the device doesnt respond via the USB). Only think i found were some header magic error at bootup. Then it shutted off. Somehow im having better luck with Lineage 17 than anything other

bahamut657 commented 3 years ago

@AtamiiX can you follow the Cubot Quest wiki page and follow the steps procedure? I got bootloop if not flashing the GSI in that way. Ensure to perform fastboot -wtwice (it seems it doesn't format userdata the first time)

ShahrukhAbrar commented 3 years ago

Did you flash vbmeta? Do you have Magisk in your boot.img?

bahamut657 commented 3 years ago

If you read the Cubot Quest guide you can set that: 1) you have to flash vbmeta 2) you have to flash also stock boot

Please read the wiki Page and let me know. Regards

AtamiiX commented 3 years ago

If you read the Cubot Quest guide you can set that:

1. you have to flash vbmeta

2. you have to flash also stock boot

Please read the wiki Page and let me know. Regards

My devise was Android 8.1 so no VBMETA.