[ROM] [12.1] [OFFICIAL] AICP 17.1 [OOS12] [instantnoodle]

Search This thread

graycorgi

Senior Member
Apr 23, 2010
339
95
Dallas
SORRY NO OOS 11
I have the same phone OOS 11 Firmware.

Latest tmoble Firmware
The source page for EU Android 12 firmware says it can be flashed to US and IN devices too, coming from Android 11 firmware. Would be weird if it didn't work on TMobile, especially because I was able to convert it to Global on Android 10 and upgrade all the way to stock OOS 12 with no issues (an upgrade that necessarily installs A12 firmware)

Edit: The directions for the A12 firmware based builds in the telegram chat tell you to update to the latest OOS and flash EU Android 12 firmware (which should work on IN/US devices also) before flashing the Android 12 build. It specifically says not to flash OOS12, so the lack of a t-mobile OOS shouldn't matter (doubly so because I converted it to Global) That is where I encounter issues. For the builds in this thread obviously you need to be on A11 firmware.
 

oneplus8user

Member
Aug 3, 2022
17
6
I just installed this on a brand new device. I'm able to boot and start playing around, then after ~30-300 seconds it goes into "QUALCOM CrashDump Mode" with message "Panic requested on external modem boot failure"

Device/Versions etc:
- Device name: OnePlus8
- HW version: EU
- ACIP version: 17.1-WEEKLY
- Build number: SQ3A.220705.003A1
- Recovery version: 17.1 (20220802_100532)

Replicate:
1. unpack new phone
2. boot to system and update to latest OOS ( IN2013_11.C.16_1160_202204222304) (EDIT: that was a lie, see my next post in response to @greycorgi)
3. become developer and unlock bootloader using fastboot
4. flash lineage recovery (from link provided here) using fastboot
5. boot to recovery and "factory reset/wipe data"
6. in recovery sideload ROM
7. boot to system... play...crash

Attached see logcat from crash (last 1K lines anyway). Also the below link (valid for 1 week) contains the boot log which is too big to attach here (I removed 400K repeating lines in the middle, leaving the first 20K and the last ~2K)

https://sprend.com/download?C=b93dfd45637a43508888dc53c44120e9
 

Attachments

  • aicp_crash.log
    162.8 KB · Views: 7
Last edited:

graycorgi

Senior Member
Apr 23, 2010
339
95
Dallas
I just installed this on a brand new device. I'm able to boot and start playing around, then after ~30-300 seconds it goes into "QUALCOM CrashDump Mode" with message "Panic requested on external modem boot failure"

Device/Versions etc:
- Device name: OnePlus8
- HW version: EU
- ACIP version: 17.1-WEEKLY
- Build number: SQ3A.220705.003A1
- Recovery version: 17.1 (20220802_100532)

Replicate:
1. unpack new phone
2. boot to system and update to latest OOS ( IN2013_11.C.16_1160_202204222304)
3. become developer and unlock bootloader using fastboot
4. flash lineage recovery (from link provided here) using fastboot
5. boot to recovery and "factory reset/wipe data"
6. in recovery sideload ROM
7. boot to system... play...crash

Attached see logcat from crash (last 1K lines anyway). Also the below link (valid for 1 week) contains the boot log which is too big to attach here (I removed 400K repeating lines in the middle, leaving the first 20K and the last ~2K)

https://sprend.com/download?C=b93dfd45637a43508888dc53c44120e9
IN2013_11.C.16_1160_202204222304 is Android 12 OOS. Unless you are using the builds in their Telegram specifically designed for Android 12 OOS firmware, you need to be on the latest Android 11 OOS (not 12).
 
  • Like
Reactions: semdoc

oneplus8user

Member
Aug 3, 2022
17
6
IN2013_11.C.16_1160_202204222304 is Android 12 OOS. Unless you are using the builds in their Telegram specifically designed for Android 12 OOS firmware, you need to be on the latest Android 11 OOS (not 12).
My bad, I don't think "IN2013_11.C.16_1160_202204222304" is what I actually installed, I think it was a Android 11 OOS and I think the reason for my confusion are the A/B slots (I got the above update version number by switching to the inactive slot which still had OOS on it and attempted to update it and it said it was downloading the aformentioned version)...

Anywho, while still on the OOS slot I followed this guide https://forum.xda-developers.com/t/verifying-firmware-versions-on-both-slots.4280239/ which copied *something* to the AICP slot and after that I was able to switch to the AICP slot and boot without issue!
 

phpbb3

Senior Member
Hello folks!

Our team and countless others have been working away both in front of and behind the curtain.

The fruit of their labors - OOS12 based builds are coming.

Starting with the 8/23 (August 23) build, AICP official builds will now REQUIRE an OOS12 firmware base

PLEASE BE ADVISED - YOU MUST UPDATE TO OOS12 FIRMWARE BEFORE INSTALLING THE 8/23 UPDATE.

The current firmware upgrade path is available here as found on the op8 series Telegram support group:

1. Boot up AICP recovery

2. Go to "Advanced" -> "Enable ADB"

3. Check your DDR type using the following command:

adb shell getprop ro.boot.ddr_type

or in case getprop returns an empty value, use:

adb shell cat /proc/devinfo/ddr_type

4. Download firmware (C33 recommended, minimum C20/21 required) from here:

5. Go to "Advanced" -> "Enter fastbootd"

6. Execute following commands after opening a command line in the fw directory:

fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all logo logo.img
fastboot flash --slot=all mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all multiimgoem multiimgoem.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all spunvm spunvm.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img

7. Flash correct XBL files

* For DDR type 0 (DDR4):

fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img

* For DDR type 1 (DDR5):

fastboot flash --slot=all xbl_config xbl_config_lp5.img
fastboot flash --slot=all xbl xbl_lp5.img

8. Boot your recovery from here and install the new update:


IF YOU ARE ON STOCK OOS12

These instructions are for you:

Thanks to @Anierin_Bliss First Time Install / Clean Flash
1. Have an unlocked bootloader & OOS 12 (C20 - C33) flashed to both slots.
2. Download vbmeta, recovery, ROM and GAPPS (optional) for your device from here: https://drive.google.com/drive/folders/1A2SeD6YFKJ2S-iiAKmyfgnrEeJz8zjNm
3. Reboot to bootloader
4. fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
5. While in recovery, navigate to Apply update -> Apply from ADB
6. adb sideload ROM.zip -> reboot recovery -> adb sideload GAPPS.zip
7. Format data, reboot to system & Enjoy !
 
Last edited:

semdoc

Recognized Contributor

16.08.2022 Weeklies were the last builds based on OOS11 base.

Starting with 23.08.2022 Builds, we are switching to OOS12 Base.

BE ADVISED !!!!

DO NOT FLASH NEW WEEKLY OVER 16.08.2022 Builds via OTA.

Please follow the instructions in the 2nd post for FW update first,

then you can flash New Weeklies.

 

Incognit420

Member
Aug 24, 2017
39
9
OnePlus 8
Hello everyone! Is there any possibility of getting the C33 firmware working on Verizon in2019? I installed the global firmware and it worked except no calling or lte network. I also tried the in2011 but would not boot, so after that I didn't even try with in2013, figured it would be the same outcome. I have AICP 17.1 installed and everything works but want the full android 12 firmware. Any help would be much appreciated, thanks.
 

semdoc

Recognized Contributor
Hello everyone! Is there any possibility of getting the C33 firmware working on Verizon in2019? I installed the global firmware and it worked except no calling or lte network. I also tried the in2011 but would not boot, so after that I didn't even try with in2013, figured it would be the same outcome. I have AICP 17.1 installed and everything works but want the full android 12 firmware. Any help would be much appreciated, thanks.

As I don't have your device, all ı can say is only: Wish I could help.
But maybe you can find another users with similar questions and answers in our TG channel. Follow my signature and ask there....
 
  • Like
Reactions: Incognit420

mmoritz

Member
Sep 21, 2021
11
3
Do follow the instructions! Unfortunately, I had done the OTA update yesterday without having visited this forum and my phone got jacked to EDL proportions. Finally back up and running but it's certainly a hassle if you don't follow the instructions. 😀
 
to those unfortunate who updated without reading the tread like me...its not over yet i bricked my phone but know you can still go to fastboot so plug on pc open the terminal and > fastboot --set-active=a
or fastboot --set-active=b
see wich one boots and you can go on from there follow this tread to update.
note:keep in mind now you have one partition who is corrupted can be fixed with msm
 
Last edited:

krakout

Senior Member
Hello!

Trying to flash aicp_instantnoodle_t-18.0-WEEKLY-20221109.zip, coming from Evolution X (A13). Flashed recivery, sideloaded ROM ok, but when trying to install GApps (Mind the gapps from the download folder) I'm getting the following:

Low resource device detected, removing large extras

Not enough space for GApps! Aborting

Cleaning up files

Unmounting partitions

Error: recovery: Error in /sideload/package.zip (status 1)

Any ideas?

[EDIT] is this related to the FW issue? I thought, coming from a A13 ROM, I was all set...

[EDIT2 - FIXED!] So, I made a stupid mistake, it would seem - huge thanks to @dante4715 for pointing it out to me: forgot to reboot after flashing the ROM and before flashing GAPPs.... I feel so stupid, but i'm leaving my post here in case it helps others.
 
Last edited:

shimomiaizo

Member
Apr 23, 2017
16
4
Hi, I have one question regarding flashing AICP onto my OP8: I recently flashed Evolution X to my OP8 (my OP8 was on the latest OOS12, and if I remember it correctly it should be C48 or something like that). Evolution X is based on Android 13, so is it safe/ok to directly flash AICP onto my phone, or should I downgrade to OOS12/other Android 12 ROMs and then flash AICP? I attached a screenshot of my OS info. Appreciated!
 

Attachments

  • photo_2022-11-29_00-35-29.jpg
    photo_2022-11-29_00-35-29.jpg
    42.9 KB · Views: 9

krakout

Senior Member
Hi, I have one question regarding flashing AICP onto my OP8: I recently flashed Evolution X to my OP8 (my OP8 was on the latest OOS12, and if I remember it correctly it should be C48 or something like that). Evolution X is based on Android 13, so is it safe/ok to directly flash AICP onto my phone, or should I downgrade to OOS12/other Android 12 ROMs and then flash AICP? I attached a screenshot of my OS info. Appreciated!
I was the same as you - EvoX, A13, then flashed this one with no problem.

Incidentally, this is a great ROM, it's strange (?) that all the action is taking place on Telegram and nobody posts here :D
 
  • Like
Reactions: shimomiaizo

shimomiaizo

Member
Apr 23, 2017
16
4
I was the same as you - EvoX, A13, then flashed this one with no problem.

Incidentally, this is a great ROM, it's strange (?) that all the action is taking place on Telegram and nobody posts here :D
Thank you so much for sharing the experience! I can't wait to get off work and flash this into my phone. EvoX is by no means bad or anything (actually it brought lots of improvements to my phone, and I'm so happy that my phone feels like a completely new device again), it's just there's a few things I want but EvoX does not provide, and I'm hoping to find those in AICP. (I used to be a long time AOSPExtended user on my 5t... AOSPE was GOAT)
 
  • Like
Reactions: krakout

krakout

Senior Member
You're very welcome. But
Thank you so much for sharing the experience! I can't wait to get off work and flash this into my phone. EvoX is by no means bad or anything (actually it brought lots of improvements to my phone, and I'm so happy that my phone feels like a completely new device again), it's just there's a few things I want but EvoX does not provide, and I'm hoping to find those in AICP. (I used to be a long time AOSPExtended user on my 5t... AOSPE was GOAT)
You're very welcome! But just to make sure, do drop by their telegram channel, not only does it have great guides and links to the newest builds, but also got can ask for more qualified help 🙂
 
  • Like
Reactions: shimomiaizo

shimomiaizo

Member
Apr 23, 2017
16
4
You're very welcome. But

You're very welcome! But just to make sure, do drop by their telegram channel, not only does it have great guides and links to the newest builds, but also got can ask for more qualified help 🙂
Hi, I'm back, I got AICP to work on my OP8 but I do have a few questions. I also joined AICP TG channel but I can't talk there just yet so here we go

1. somehow in System Settings my OS version is said to be Android 13? Is it supposed to be 13? I thought AICP is 12?

2. there seems to be no "safe area" at the bottom of the screen for the gesture navigation bar (i.e. UI elements drawn on the screen will go below the navigation line), and I looked around in the settings, there also does not seem to be anything that fixes this. I don't remember encountering this on OOS12 or Evo X, is it me doing something wrong or is this just supposed to be this way on AICP?

3. Is there a way for me to use my own font for the OS, or is there nothing like that? I wanted Product Sans/Google Sans but that is not one of the built-in options. Additionally, since there's no Product Sans, I wanted to go with Source Sans Pro, but since Noto Serif and Source Sans Pro are a pair, there's also no way for me to only use SSP and not NS......
 

krakout

Senior Member
Yes the latest builds are A13, almost stable (when it gets to stable it'll get OTA updates too).

Not sure about the gap at the bottom, never noticed anything but then again I've always used Action Launcher and Magisk modules...

As for the font, are you rooted? Product Sans is indeed a great font btw!
 

shimomiaizo

Member
Apr 23, 2017
16
4
Yes the latest builds are A13, almost stable (when it gets to stable it'll get OTA updates too).

Not sure about the gap at the bottom, never noticed anything but then again I've always used Action Launcher and Magisk modules...

As for the font, are you rooted? Product Sans is indeed a great font btw!
thanks for the reply!

12 v.s. 13
thanks for the confirmation - I look forward to the OTA :))​
safe area for gesture nav bar at bottom of screen
this is not THAT breaking for me at the moment, I'll keep look into this; if I can't really do anything to change it I'll just leave it be.​
fonts
I'm not rooted because I do use Google Pay/Wallet and I do quite some gaming on my phone too, and all these kind of require me not to root my device, which is why I tend not to. Additionally, rooting and using rooted modules does increase changes of system instability, and since this is my daily drive, any unexpected downtime would be quite annoying.​
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    logo_black.png



    AICP

    Android Ice Cold Project




    AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!

    Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
    With the re-brand of CM to LineageOS (LOS), we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
    We changed again for Android Q-S with a base of AOSP repositories and some additions from LineageOS for device-specific repositories.

    If there are any bugs we will sort them out if it concerns our codebase. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!


    Code:
    #include <std_disclaimer.h>
    
    /*
    * Your warranty is now void.
    *
    * We are not responsible for bricked devices, dead SD cards,
    * thermonuclear war or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications and if
    * you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
    *
    */

    features.png

    Feature list (rough overview)


    credits.png


    In the beginning, we would like to thank:

    LineageOS & CM (R.I.P.) team
    Evolution X Team & @AnierinB
    GZOSP team
    @maxwen and the rest of the OmniRom team
    DU team
    Resurrection Remix team
    AOSiP team
    Whole Android Community

    team.png


    @LorD ClockaN
    @eyosen
    @semdoc
    @SpiritCroc
    @wartomato
    @Miccia
    plus the rest of the crazy bunch that we call "team"



    donations.png


    We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
    Thank you!!



    downloads.png


    Latest Stable Release Version 17.1

    Download link: https://dwnld.aicp-rom.com/

    Please note that official builds will be deleted from our servers every month due to maintenance services.
    Starting with AICP 15 we will be storing a copy of the most recent release here: https://media.aicp-rom.com/vault/.



    changelog.png


    Full Changelog link: https://dwnld.aicp-rom.com/
    (Just click the changelog button next to the download link in the list of builds available for your device)

    Google Apps:
    We recommend MindTheGapps as it has been thoroughly tested and it works well with the ROM, some other minimal (and others) GApps packages could have issues, so try using MindTheGapps if you have any issues with other GApps packages

    MindTheGapps: Download from HERE


    issues.png


    Due to new light sensor, autobrightness is a mess for now. But will be fixed soon I hope.

    FAQ:
    Before using the ROM:
    Q. Can I have an ETA for the next build?
    A. Yes, just look here to see what day your device is built on.

    Q. Does this ROM support custom kernels officially?
    A. No. You can still use them, but the discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!

    Q. Does this ROM include GApps or do I have to flash them separately?
    A. No, we do not include prebuilt GApps, because of possible licensing issues with Google Software and because some users do not want GApps preinstalled as they want to use alternative services like MicroG or just prefer flashing a GApps "flavor" of their liking.

    Q. Does this ROM use the camera or gallery app from stock?
    A. It depends on the device. In most cases, these apps include proprietary libs/code and cannot be included in the device trees on GitHub or we risk having the ROM banned from GitHub. In this case, we might try to make them installable (separate from the ROM zip), or we might provide a version of these apps with the ROM that doesn't include any proprietary libs. It's also sometimes the case that these apps are simply not included because we didn't feel the need to do so for the device in question.

    Q. Does this ROM have Extended/Scrolling screenshot?
    A. No, extended screenshot was implemented using an app extracted and modified from manufacturer firmware/system images and is proprietary as well. It led to the closing of many ROM's sources on GitHub.

    Q. Does this ROM have FaceUnlock?
    A. No, FaceUnlock was also an app extracted and modified from some manufacturers. Even Google removed the Trusted Face (FaceUnlock) feature for security reasons on Android 9.0/10.x. Adding the modified feature did the same to ROM sources as described above.

    Q. Can you add (insert favorite weather provider)?
    A. No, we cannot add more weather providers as the implementations change and we (the ROM) now have to pay for most services, and that is not cheap, so we decided to use the best free service that we could find, the only way to add your own is for users to apply for their own API key to use their preferred service.

    Q. Does this ROM have private official builds with the above proprietary libs included?
    A. No, we believe in open source software, this way users know what's in the build and can replicate it themselves, all official builds are built on our build servers using the public sources from GitHub, and no one can (or would) add their own private sources to the build.

    Flashing the ROM:
    Q. What do I need to know before flashing?
    A. Check the flashing instructions...

    Q. Can the builds be dirty flashed over each other?
    A. Yes, this is how users can/should install updates most of the time, this can be done with the built-in updater service or with a custom recovery.

    Q. How do I 'dirty flash' builds?
    A 1. For "A only" devices: Wipe the System, Cache, and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.

    A 2. For "A/B" devices": Wipe the ART/Dalvik cache. Flash the ROM, reboot to the recovery, flash GApps, your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.

    Q. How do I flash kernel builds?
    A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to lose root and reboot.
    A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to lose root. Now swipe to flash and reboot afterward.

    Using the ROM:

    Q. Do I need to provide a logcat if I'm reporting a bug?
    A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. Do not post the content here. Thanks.)

    Q. How do I get a logcat, what type should I get, and more questions that can conveniently be answered by my pre-determined answer?
    A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
    A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section on the AICP Extras main page.


    instructions.png


    The ROM should contain everything you need to enjoy Android S. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
    If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM zip file.

    It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
    If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.

    How to flash for the first time:
    (Again: Don't do it if you don't know!)

    16.08.2022 Weeklies were the last builds based on OOS11 base.

    Starting with 23.08.2022 Builds, we are switching to OOS12 Base.

    BE ADVISED !!!!

    DO NOT FLASH NEW WEEKLY OVER 16.08.2022 Builds via OTA.

    Please follow the instructions in the 2nd post for FW update first,

    then you can flash New Weeklies.




    If you are flashing using adb sideload, GAPPS needs to be flashed on every dirty flash as it's mentioned above.
    If you are flashing using OTA, no need to flash GAPPS, .


    Currently supported Root Solution:

    Magisk versions >= feel free to report. Didn't tested myself.


    Instructions for OTA ("Over-The-Air" Updates) on "A only" devices (not A/B):
    Using on board recovery will be enough mostly for your operations.

    Instructions for OTA ("Over-The-Air" Updates) on "A/B" devices:
    Open the updater app, download the update, then press install and wait for the process to finish (feel free to let it run in the background), then press reboot when prompted, there isn't any need to flash GApps separately

    sources.png


    If you want to contribute to AICP, or if you want to see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)

    Kernel source:
    Device tree source:
    Follow this guide if you want to extract the vendor blobs

    ROM & Additional links:
    AICP's Homepage
    AICP Gerrit Code Review
    AICP sources on GitHub
    AICP Download page for official builds and media content
    AICP Discord Community
    AICP Telegram channel for server notifications on official builds

    Contributors:

    (mention all the devs who have contributed to your device tree, kernel, vendor, etc,
    only mention the main ones though, probably the top four or so, otherwise this list will be a mile long xD)

    Information:
    ROM OS Version:
    12.1
    Kernel: Linux 4.19.11-perf
    ROM {Firmware|Vendor} required: Latest OOS 12 (At least C20/21 firmware)
    Status:
    STABLE
    Release Date: 23-08-2022

    You want to see a "normal" night at the "DEV office", click here!!​
    2
    IN2013_11.C.16_1160_202204222304 is Android 12 OOS. Unless you are using the builds in their Telegram specifically designed for Android 12 OOS firmware, you need to be on the latest Android 11 OOS (not 12).
    My bad, I don't think "IN2013_11.C.16_1160_202204222304" is what I actually installed, I think it was a Android 11 OOS and I think the reason for my confusion are the A/B slots (I got the above update version number by switching to the inactive slot which still had OOS on it and attempted to update it and it said it was downloading the aformentioned version)...

    Anywho, while still on the OOS slot I followed this guide https://forum.xda-developers.com/t/verifying-firmware-versions-on-both-slots.4280239/ which copied *something* to the AICP slot and after that I was able to switch to the AICP slot and boot without issue!
    1
    Hi thanks all for your tremendous efforts
    If we are on OOS 12 then do we have to revert to OOS11 ?
    1
    What a pleasant surprise, love your work semdoc, can't wait to get home and flash this.
    1
    Ok, so, rooting steps in brief:

    Download https://github.com/ssut/payload-dumper-go/releases . Great to extract boot images (and more). Extract boot.img from the ROM file (well, the dumper will extract all files, but this is the one we're interested in). Copy it to your phone. Download the Magisk apk (ONLY from https://github.com/topjohnwu/Magisk/ ). Use it to patch the image. The flash it through ADB Fastboot once your ROM is set up.

    OR (easier method)

    INSTALL ROM:
    -Get files from https://drive.google.com/drive/folders/1luchnV0R4UN8LQFWc5s4OeFjZIRELN09 .
    -Boot into bootloader.
    -Flash the provided recovery: fastboot flash recovery recovery.img.
    -Boot to recovery. Flash via "sideload". (on your PC, assuming you have connected your phone to it, type: adb sideload ROM.zip)
    -reboot to recovery (VERY important! The first time I forgot to, and Gapps would not install)
    -Sideload the GAPPs by "adb sideload gapps.zip"
    -format data.
    -Reboot to system.
    ROOTING
    -Download Magisk.apk and rename it to magisk.zip.
    -Reboot to Recovery again, and choose Sideload install
    -On your PC, "adb sideload Magisk.zip".

    That's it. Pretty easy. That was the whole process of installing the ROM btw, plus rooting. Interestingly I found that root persisted between updates! If you get a verification error (I think it happens with Gapps), ignore it.

    Huge thanks to @dante4715 for helping me to figure it out :)
    Huge thanks to you and your friend both! I'm about to try the rooting-only part out, since I just flashed AICP 48h ago lol. I bookmarked your post cuz I feel like this process (very clear and well written, step by step easy to follow) will be continuously useful until the day I no longer use any Android devices lolll