• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

ClefAria

Member
Aug 23, 2012
44
7
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

Recognized Contributor
Jan 9, 2015
1,813
2,079
23
Sydney
Google Pixel 3a XL
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
 

41rw4lk

Senior Member
Dec 11, 2010
874
332
Springfield, MO
Google Pixel 3a XL
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

New member
Sep 10, 2020
3
0
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

Senior Member
Dec 11, 2010
874
332
Springfield, MO
Google Pixel 3a XL
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

New member
Sep 10, 2020
3
0
I tried that and it wouldn't install. I'm going to try to re-update the drivers again in the morning. :-/
 

adm1jtg

Senior Member
Jul 26, 2010
2,772
868
Georgia
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

New member
Sep 10, 2020
3
0
Yes! That did the trick. :D 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

Member
Aug 23, 2012
44
7
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...
 
Last edited:

adm1jtg

Senior Member
Jul 26, 2010
2,772
868
Georgia
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

Senior Member
Dec 7, 2010
398
213
Nexus 6
Google Pixel 3a XL
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.
 

ITGrouch

Member
Dec 27, 2012
35
5
Near Music City USA
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?
 
Last edited:

Dopamin3

Senior Member
Dec 7, 2010
398
213
Nexus 6
Google Pixel 3a XL
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

Member
Dec 27, 2012
35
5
Near Music City USA
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.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 13
    url]

    Code:
    [B][CENTER]**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****[/CENTER][/B]
    Android Open Source illusion Project

    About us:
    AOSIP is a quality custom ROM based purely on AOSP. Twisted with the latest features and blended with stability. We strive for perfection and it shows.

    Team Illusion:

    Josh Fox (xlxfoxxlx)
    Akhil Narang
    Harsh Shandilya
    Anirudh Gupta


    Bug reporting:

    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    • Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.


    Source code:


    Latest Downloads:

    Official Server | SourceForge Mirror

    Credit/Thanks:

    Mike Williams (founder and creator of AOSiP)
    Google for Android and AOSP
    LineageOS
    ABC ROM
    AquariOS
    BootleggersROM
    Dirty Unicorns
    PixelExperience
    OmniROM
    CarbonROM
    nathanchance
    ---------
    Other projects whose work helped us to create this
    And last but not the least, all our testers, who have helped us to squash many bugs so that we can try to release builds that as are flawless as possible



    Hosted and built on


    XDA:DevDB Information
    Android Open Source Illusion Project, ROM for the Google Pixel 3a XL

    Contributors
    Skittles9823
    Source Code: [url]https://github.com/AOSiP[/URL]

    ROM OS Version: Android 10
    ROM Kernel: Linux 4.x
    ROM Firmware Required: May 2020 security patch
    Based On: AOSP

    Version Information
    Status: Official

    Created 2020-02-04
    Last Updated 2020-05-25
    5
    Installation procedure:
    Have an unlocked bootloader (Not gonna be explained here, there'll be threads in this forum somewhere)

    Make sure to backup internal storage as wiping data will delete everything.

    Reboot to fastboot and flash the provided boot.img with the following commands:
    Code:
    adb reboot bootloader
    fastboot flash boot /path/to/boot.img
    reboot into recovery and select "Apply update from ADB":
    Code:
    fastboot reboot recovery
    adb sideload /path/to/rom.zip
    In recovery before rebooting, make sure to factory reset/wipe data.
    Reboot into the system, and enjoy the illusion!

    Update procedure:
    Just use the built in updater. Easy peasy.

    Updating with Magisk:
    Update using the built in updater same as you would without magisk, but when it prompts you to reboot, open magisk manager, tap install for the magisk option > then select "install to inactive slot" > then proceed as you normally would and reboot once it's done.

    KNOWN ISSUES:
    Currently none, let me know what you find!
    5
    Im on q android 10 stock april 2020 patch with only bootloader unlocked.. can i do this . just got phone and use it for streaming to my cochlear implant.
    update. rooted now. but boot img page no longer works
    update 2 are we waiting for april update?
    Yea, I'd wait a little bit for the new update. New builds should be up soon, the build system finally works for bonito and coral, I'll be flashing a new build later today to test and see if anything is broken and if all is good then officials should be good to go.

    Just a note to others who are running older builds that they'll be required to clean flash to use the newer ones as they're being signed now.
    5
    Is there an ETA on March security patch/release?
    Not currently. I'm waiting for major changes in rom source to settle down a bit so clean flashes aren't needed each update as often. I'll most likely release the next build with the April patch with a bunch of fixes. Hopefully within the week of its release.

    Sent from my Pixel 3a XL using XDA Labs