search

phhusson / treble_experimentations

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

Cannot flash Android 11 GSI on my Asus Zenfone Go #1796

Open Iuspeppe88 opened 3 years ago

Iuspeppe88 commented 3 years ago

Hi! Until now I've flased Android 9 and 10 on my device and everything was fine during the flashing. But when I try to flash Android 11 GSI release via fastboot I get this error: FAILED (remote Unknown chunk type). System partition type of my device (Asus Zenfone Go) is A only.

Thanks to those who will help me and sorry for my bad english!

phhusson commented 3 years ago

Which gsi variant do you use?

9 avr. 2021 19:04:57 Iuspeppe88 @.***>:

Hi! Until now I've flased Android 9 and 10 on my device and everything was fine during the flashing. But when I try to flash Android 11 GSI release via fastboot I get this error: FAILED (remote Unknown chunk type). System partition type of my device (Asus Zenfone Go) is A only.

Thanks to those who will help me and sorry for my bad english!

— 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/1796], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAAA4OWJTRVRW7K5MBB5QPLTH4XTTANCNFSM42VK5IMA]. [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADgAAAA4CAYAAACohjseAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAjSURBVGiB7cEBDQAAAMKg909tDwcUAAAAAAAAAAAAAADApwExOAABR9ZGcwAAAABJRU5ErkJggg==###24x24:true###][Image de pistage][https://github.com/notifications/beacon/AAAA4OSYWQPSIMSLJ7ITBVDTH4XTTA5CNFSM42VK5IMKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4MXRWDVQ.gif]

Iuspeppe88 commented 3 years ago

Which gsi variant do you use? 9 avr. 2021 19:04:57 Iuspeppe88 @.***>:

I use "system-roar-arm-aonly-vanilla.img"

Iuspeppe88 commented 3 years ago

It's normal that the filename extension is "img-1" instead of "img"? AOSP 10 images was "img" only, but these with Android 11 end with "img-1". I try to change extension to img, but I get the same error "FAILED (remote Unknown chunk type)". I don't know where I'm wrong :(

youcancallmekhen commented 3 years ago

It's normal that the filename extension is "img-1" instead of "img"? AOSP 10 images was "img" only, but these with Android 11 end with "img-1". I try to change extension to img, but I get the same error "FAILED (remote Unknown chunk type)". I don't know where I'm wrong :(

For some reason, it seems the img file you downloaded was split into multiple files, that's why the file extension becomes img-1. You need to download the file again.

Iuspeppe88 commented 3 years ago

For some reason, it seems the img file you downloaded was split into multiple files, that's why the file extension becomes img-1. You need to download the file again.

I downloaded the image several times and the extension is always "img-1". But, as I said before, this only happens when I try to download AOSP 11 GSI, no problem with AOSP 9 or 10.

Iuspeppe88 commented 3 years ago

Newest release are back to "img" extension, but the issue remain :( Immagine

phhusson commented 3 years ago

That's going to sound weird, but you might need to use an older fastboot tool on your computer (the "chunk type" is created by fastboot computer-side when the file being flashed is not sparse)

Iuspeppe88 commented 3 years ago

That's going to sound weird, but you might need to use an older fastboot tool on your computer (the "chunk type" is created by fastboot computer-side when the file being flashed is not sparse)

It's weird 'cause I haven't that issue when I try to flash AOSP 9 or 10 with the same fastboot tool. However, could you suggest me an alternative fastboot tool that I can try? Thank you for your help ^^

phhusson commented 3 years ago

Yes my aosp 9 and aosp 10 releases are sparse, which means it's not sparsed by fastboot

11 juin 2021 12:07:38 Iuspeppe88 @.***>:

That's going to sound weird, but you might need to use an older fastboot tool on your computer (the "chunk type" is created by fastboot computer-side when the file being flashed is not sparse)

It's weird 'cause I haven't that issue when I try to flash AOSP 9 or 10 with the same fastboot tool. However, could you suggest me an alternative fastboot tool that I can try? Thank you for your help ^^

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

Iuspeppe88 commented 3 years ago

Yes my aosp 9 and aosp 10 releases are sparse, which means it's not sparsed by fastboot

Ok, thank you! I'll try with an older version of fastboot tool and I'll let you know ;)

Iuspeppe88 commented 3 years ago

So, I tried different versions of the fastboot tool, but I alway get the same error "FAILED (remote Unknown chunk type)". I found this tool called "SparseConverter" which I've converted your AOSP 11 in a sparse img. When I try to flash the converted img it no more get me the message "Invalid sparse file format at header magic"... but it still ends with "FAILED (remote Unknown chunk type)" lol! I'm desperate XD Immagine

JonnyTech commented 3 years ago

Are you able to try to fastboot flash with Linux rather than Windows? (even from a live usb medium)

Iuspeppe88 commented 3 years ago

Are you able to try to fastboot flash with Linux rather than Windows? (even from a live usb medium)

Uhm yeah, I can. I'll try with a virtual machine and I'll let you know. Thanks ^^

Iuspeppe88 commented 3 years ago

@JonnyTech same error with Linux :( Immagine

JonnyTech commented 3 years ago

Hmm, are you sure that you have unlocked your phone's bootloader? I get that message with some (re)locked bootloaders.

Please try these commands to correctly download and extract the image:

wget https://github.com/phhusson/treble_experimentations/releases/download/v309/system-roar-arm-aonly-vanilla.img.xz
xz -dk system-roar-arm-aonly-vanilla.img.xz

Then the following to verify it:

file system-roar-arm-aonly-vanilla.img
system-roar-arm-aonly-vanilla.img: Linux rev 1.0 ext2 filesystem data, UUID=8a90a354-6fbf-42bb-9f00-d1e1eeecf4b3 (extents) (large files) (huge files)

sha256sum system-roar-arm-aonly-vanilla.img
982f7dcd748f8cdfa319d861e049599112e815ec486e222c609cf921ac9f15bb  system-roar-arm-aonly-vanilla.img

sha1sum system-roar-arm-aonly-vanilla.img
409bb9ff9c848d045766bfd6e6d8a08fb80bd2c1  system-roar-arm-aonly-vanilla.img

If the checksum matches then flash it:

sudo flash system system-roar-arm-aonly-vanilla.img

Otherwise you may need to do a full stock update (all partitions) in order to get a working bootloader.

Iuspeppe88 commented 3 years ago

Hmm, are you sure that you have unlocked your phone's bootloader? I get that message with some (re)locked bootloaders.

Yes, 'cause flashing AOSP 9 and 10 GSI does not give me this error. I get that message only when I try to flash AOSP 11 GSI.

Then the following to verify it: Immagine

If the checksum matches then flash it: Immagine2

Otherwise you may need to do a full stock update (all partitions) in order to get a working bootloader.

Hmm, I don’t think I can... I’m not that experienced ahah XD. Anyway, thank you ^^