[ROM][10]Android Open Source Illusion Project[Bonito][Official]

[ClefAria]

One other question, maybe silly since I haven't actually gotten down to trying to install this yet: are the "update instructions" a dirty flash? Or will all the ROM settings and such get wiped out each time I update?

 

[Skittles9823]

One other question, maybe silly since I haven't actually gotten down to trying to install this yet: are the "update instructions" a dirty flash? Or will all the ROM settings and such get wiped out each time I update?

You can choose to dirty flash if you wish, but the best and easiest way to update is to use the built in updater that works similar to an OTA on stock

Sent from my Pixel 3a XL using XDA Labs

 

[ClefAria]

You can choose to dirty flash if you wish, but the best and easiest way to update is to use the built in updater that works similar to an OTA on stock

Sent from my Pixel 3a XL using XDA Labs

There's a built-in updater?! The answer I didn't even know I wanted.

Looking forward to trying it out!

 

[41rw4lk]

The built-in updater keeps me on this rom. No hassle, no interruptions, no command lines, just seamless updates. If you have an A/B device and don't have seamless updates working for you then it's a missed opportunity imo.

 

[Redilarus]

Flashed wrong ROM and need help

So... I have a Pixel 3a and accidentally loaded the ROM here for the 3a XL. This has caused some issues, the most pressing of which is that the device doesn't show up to ADB unless it's in Rescue Mode.

I can't even check anything because the touch screen reads all wrong (doubtless because it's the wrong damn phone). I'm trying to get back to stock just to even be able to use it again, but with ADB not recognizing it I'm not sure what to do.

Any advice? Obviously I need to be more careful in the future.

 

[41rw4lk]

So... I have a Pixel 3a and accidentally loaded the ROM here for the 3a XL. This has caused some issues, the most pressing of which is that the device doesn't show up to ADB unless it's in Rescue Mode.

I can't even check anything because the touch screen reads all wrong (doubtless because it's the wrong damn phone). I'm trying to get back to stock just to even be able to use it again, but with ADB not recognizing it I'm not sure what to do.

Any advice? Obviously I need to be more careful in the future.

https://pixelrepair.withgoogle.com/

 

[Redilarus]

I tried that and it wouldn't install. I'm going to try to re-update the drivers again in the morning. :-/

 

[adm1jtg]

Try downloading a full Google image and then run flash-all.bat from a pc connected via usb. Phone should be on bootloader screen.

This should rebuild everything to a full Google image and you can they load aosip again on top of it.

Please understand this will wipe the entire phone including any apps and data you may have on the phone

 

[Redilarus]

Yes! That did the trick. I had managed to find a thread on it and gave it a try and if worked a treat. Thank you for the awesome advice!

 

[ClefAria]

Okay, so I'm trying this out, and after some difficulty (apparently "fastbootd" is different in some way from "fastboot", never saw the former before I upgraded to Android 10 (custom ROM I was using before was on 9)), I'm in!

There are instructions for updating with magisk, but how should I go about installing magisk fresh on this ROM? Do I just sideload the .zip installer in the same way as I did the ROM? I'm not used to working without TWRP...

 

[adm1jtg]

Perhaps a stupid question but.... i downloaded the fastboot images for the rom and for gapps but don't see anywhere the fastboot commands to use for each img file. Can someone provide or link me to the commands to fastboot the rom files and gapps files, like by line

 

[Dopamin3]

Perhaps a stupid question but.... i downloaded the fastboot images for the rom and for gapps but don't see anywhere the fastboot commands to use for each img file. Can someone provide or link me to the commands to fastboot the rom files and gapps files, like by line

I know this isn't helpful, but just download AOSiP-10-Gapps-bonito-20200904.zip and AOSiP-10-Gapps-bonito-20200904-boot.img. Follow the instructions in the second post. You will then boot no issues to the ROM and it's a lot less time consuming than fastboot flashing each partition.

 

[ClefAria]

Does OTA updating mess with root via Magisk?

 

[drew071]

Does OTA updating mess with root via Magisk?

Yes, it removes root as the boot.img isn't patched

 

[Skittles9823]

Does OTA updating mess with root via Magisk?

Not if you follow the magisk instructions to flash to 2nd slot after taking the OTA but before rebooting. I'll update the second post now to detail that.

Sent from my Pixel 3a XL using XDA Labs

 

[thatsupnow]

Not if you follow the magisk instructions to flash to 2nd slot after taking the OTA but before rebooting. I'll update the second post now to detail that.

So download and install, but before reboot flash magisk to inactive slot??

Yea got it figured out. It's exactly as said

 

[chuckcheeze]

Not if you follow the magisk instructions to flash to 2nd slot after taking the OTA but before rebooting. I'll update the second post now to detail that.

Sent from my Pixel 3a XL using XDA Labs

thanks for updating the Magisk install instructions. works great! saves me steps to manually patch boot and fastboot flash.

 

[ITGrouch]

I am having issues installing the ROM. I flashed the last Q stock and went through the steps in post 2. No problems installing the boot image but when I reboot to recovery and go to the adb sideload, when I try to sideload the ROM, I get the error messages on the phone "E:footer is wrong E:Signature verification failed E:error: 21". I also tried flashing the March Q stock and went through the same steps and still get the same error messages. I am at a loss. Any suggestions?

 

[Dopamin3]

I am having issues installing the ROM. I flashed the last Q stock and went through the steps in post 2. No problems installing the boot image but when I reboot to recovery and go to the adb sideload, when I try to sideload the ROM, I get the error messages on the phone "E:footer is wrong E:Signature verification failed E:error: 21. I also tried flashing the March Q stock and went through the same steps and still get the same error messages. I am at a loss. Any suggestions?

Probably a corrupt download... Verify the checksum. I like to use http://onlinemd5.com but there are other methods as well.

 

[ITGrouch]

Probably a corrupt download... Verify the checksum. I like to use http://onlinemd5.com but there are other methods as well.

Thanks for the reply. I performed the checksum on the ROM before trying to install and they matched. From what I read online, the errors I received is because the ROM file isn't signed and will not install. I have put upgrading on hold until I get more info here.

---------- Post added at 12:10 PM ---------- Previous post was at 11:14 AM ----------

Thanks for the reply. I performed the checksum on the ROM before trying to install and they matched. From what I read online, the errors I received is because the ROM file isn't signed and will not install. I have put upgrading on hold until I get more info here.

Found what the problem was. The boot image file was corrupt. I downloaded it three times and finally the third download worked.