search

phhusson / treble_experimentations

Notes about tinkering with Android Project Treble
3.4k stars 660 forks source link

Android 11 GSIs dont boot on various devices but Android 10 does #1687

Open AtamiiX opened 3 years ago

AtamiiX commented 3 years ago

So i have a collection of MTK Treble enabled devices to play around and use. I tried every 11 GSI and still it goes like this: Fastboot erase system Fastboot flash system .....img Fastboot erase userdata Fastboot reboot BOOTLOOP Rebooting Into fastboot again. Also i am not able to take logs, is there any way to boot A11?

phhusson commented 3 years ago

Erasing userdata is stupid. I'm pretty sure my AOSP 10 GSI doesn't boot if you erase userdata either.

Le mer. 20 janv. 2021 à 15:19, AtamiiX notifications@github.com a écrit :

So i have a collection of MTK Treble enabled devices to play around and use. I tried every 11 GSI and still it goes like this: Fastboot erase system Fastboot flash system .....img Fastboot erase userdata Fastboot reboot BOOTLOOP Rebooting Into fastboot again. Also i am not able to take logs, is there any way to boot A11?

— 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/1687, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OV5LTUWUX4RJMC7ZDDS23Q7PANCNFSM4WKX3VDA .

AtamiiX commented 3 years ago

So tell me what to do. Thanks.

AtamiiX commented 3 years ago

So i tried not erasing userdata and flashing system over stock (as said in many tutorials) still bootloops

phhusson commented 3 years ago

You need to factory reset from stock recovery

AtamiiX commented 3 years ago

You need to factory reset from stock recovery

i did that It makes the phone reboot to fastboot after factory reset

phhusson commented 3 years ago

What device is it? Does it have vbmeta partition, and did you flash it?

AtamiiX commented 3 years ago

Those Android Go Oreo devices and some older Android 8.1 devices. I factory reseted from stock and erase system via fastboot, then flashed system via fastboot, rebooted. Also none of those devices have VBMETA i think (not ones i tested it on)

djvinniev77 commented 3 years ago

@phhusson Hi, sorry I am jumping into this thread but I believe I have a similar situation.device is an Umidigi Bison mt6771 p60 chip, has a only partition and stock recovery can take me to fastbootd to flash system img in the super partition. While in fastbootd, I am unable to flash vbmeta, says it doesn't exist. I can get out to bootloader and with regular fastboot can successfully flash vbmeta.

It does the same thing as OP when flashing and after wiping with stock recovery. It just goes right back to bootloader at reboot. I haven't found anything else online regarding this, was wondering if you have come across anything like this? I have done the following order:

Flash vbmeta Reboot to fastbootd Flash system gsi Fastboot -w to wipe, Reboot Stuck at bootloader at reboot

Even did it reverse order, bootloader to fastbootd, erase system, flash system gsi, reboot bootloader, flash vbmeta, reboot, stuck at bootloader.

For every flashing exercise I see everyone doing, it seems they're just in fastbootd flashing everything. This device is unable to recognize the vbmeta partition in fastbootd, just regular fastboot.
Any thoughts? Thanks in advance.

phhusson commented 3 years ago

There is no a only with fastbootd

1 avr. 2021 03:40:27 djvinniev77 @.***>:

@phhusson[https://github.com/phhusson] Hi, sorry I am jumping into this thread but I believe I have a similar situation.device is an Umidigi Bison mt6771 p60 chip, has a only partition and stock recovery can take me to fastbootd to flash system img in the super partition. While in fastbootd, I am unable to flash vbmeta, says it doesn't exist. I can get out to bootloader and with regular fastboot can successfully flash vbmeta.

It does the same thing as OP when flashing and after wiping with stock recovery. It just goes right back to bootloader at reboot. I haven't found anything else online regarding this, was wondering if you have come across anything like this? I have done the following order:

Flash vbmeta Reboot to fastbootd Flash system gsi Fastboot -w to wipe, Reboot Stuck at bootloader at reboot

Even did it reverse order, bootloader to fastbootd, erase system, flash system gsi, reboot bootloader, flash vbmeta, reboot, stuck at bootloader.

For every flashing exercise I see everyone doing, it seems they're just in fastbootd flashing everything. This device is unable to recognize the vbmeta partition in fastbootd, just regular fastboot. Any thoughts? Thanks in advance.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub[https://github.com/phhusson/treble_experimentations/issues/1687#issuecomment-811576262], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAAA4OR5W34FN43HXEOQ6WDTGPFIVANCNFSM4WKX3VDA]. [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADgAAAA4CAYAAACohjseAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAjSURBVGiB7cEBDQAAAMKg909tDwcUAAAAAAAAAAAAAADApwExOAABR9ZGcwAAAABJRU5ErkJggg==###24x24:true###][Image de pistage][https://github.com/notifications/beacon/AAAA4OX4ZEHL3YH5FH7EHBDTGPFIVA5CNFSM4WKX3VDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGBP2XRQ.gif]

djvinniev77 commented 3 years ago

I hope that's the case. I used the treble check app and that's what it says. Project Treble supported. seamless system updates unsupported , detected to have an a-only partition. I will play around with it and try out ab images and see.
Thanks!

JonnyTech commented 3 years ago

Do not use treble check - use treble info instead: https://play.google.com/store/apps/details?id=tk.hack5.treblecheck

PeterBurner commented 3 years ago

I have the same problem on Qin 2 Pro
Android 9 and 10 are working fine
with Android 11 it always reboots to fastboot
I wiped userdata and cache in TWRP

abdullah5490 commented 3 years ago

I'm not sure about android 10, but facing the same on android11 GSIs on my infinix note7 x690 (mt6768). I tried 4 different GSIs. when I try fastboot.exe flash system system.img, it says "partition table doesn't exist". but fastboot flash super system.img flashes the things, but after rebooting, it always went to fastboot again.

sukkysounds commented 3 years ago

i also have this same issue previous gsi (Q) have always booted on my infinix hot 6x (x623) but android 11 just doesnt boot it just stay on the android logo like forever

wvffle commented 3 years ago

Same with Ulefone Armor 3

ghost commented 2 years ago

And the same with Redmi 9C. Whether trying to flash with fastbootd or PBRP. Always bootloops regardless of whether I flash the Vbmeta_vendor or vbmeta_system before or after the flash. Mediatek does not work well with custom ROMs and GSIs

phhusson commented 2 years ago

All my ab mediatek device boot my aosp 11 and 12 just fine. Stop with your bullshit.

On January 12, 2022 12:31:30 PM GMT+01:00, q-254 @.***> wrote:

And the same with Redmi 9C. Whether trying to flash with fastbootd or PBRP. Always bootloops regardless of whether I flash the Vbmeta_vendor or vbmeta_system before or after the flash. Mediatek does not work well with custom ROMs and GSIs

-- Reply to this email directly or view it on GitHub: https://github.com/phhusson/treble_experimentations/issues/1687#issuecomment-1010946834 You are receiving this because you were mentioned.

Message ID: @.***>

nation888 commented 2 years ago
I used to use ADB/Fastboot method but realized spflash tool is by far the best to install recovery and vbmeta on MTK devices. Once TWRP is installed then proceed to flash the GSI img’s.  Using Oukitel K9Regards, Trevor W. From: q-254Sent: January 12, 2022 5:31 AMTo: phhusson/treble_experimentationsCc: SubscribedSubject: Re: [phhusson/treble_experimentations] Android 11 GSIs dont boot on various devices but Android 10 does (#1687) And the same with Redmi 9C. Whether trying to flash with fastbootd or PBRP. Always bootloops regardless of whether I flash the Vbmeta_vendor or vbmeta_system before or after the flash. Mediatek does not work well with custom ROMs and GSIs—Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***> 
EthanCodes07 commented 2 years ago

Hi I'm also dealing with this issue with Android 11 not booting on my phone either Q and Pie Works and when I try to install a11 the recovery installs it like it's a full custom ROM I'm not sure why but my Device is a Moto e5 Play Go (Pettyl Varient)

In my prediction as the Google Pixel 2 and newer use gsis to update to the latest Android version but I'm pretty sure the pixel 2 never made it to the a11 update I'm not defo saying it is but my friend had a pixel 2 with Q on it but like I say I might be wrong but if I am right this might help explain why 8.1 vendors won't boot a11

phhusson commented 2 years ago

My Pixel 1 is booting my A12 GSI just fine :P

In this context, I think the biggest issue is A-only, not A8 vendor, but idk.

BradleyCodes commented 2 years ago

What about any arm-v7 architecture devices? Do you know if they boot a11 fine?

BradleyCodes commented 2 years ago

What about any arm-v7 architecture devices? Do you know if they boot a11 fine?

Btw it's the same acc as my Ethan codes one it's just on my tablet

sirkev commented 2 years ago

What was the fix for this?

I have umidigi A9 Pro 2021 mt6771 arm64ab, android 11 gsi boot just fine but no android 12 gsi boots for me

RealACJoshua commented 2 years ago

I have tried different A11 version on my A only device and it seems to bootloop but A10 works fine

EthanCodes07 commented 2 years ago

What was the fix for this?

I have umidigi A9 Pro 2021 mt6771 arm64ab, android 11 gsi boot just fine but no android 12 gsi boots for me

It could all depend on the vendor