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

Search This thread

orangepowerpokes

Senior Member
Sep 3, 2016
90
25
Last edited:

Nick-Henkey

New member
Feb 23, 2021
3
1
For anyone new, be sure to back up persist.img. After the last update my IMEI got deleted and it does not appear to be recoverable.

The update worked for about 1 week, it's possible my device just wasn't checked by the network for that week. It's also possible that T-Mobile deleted it since they just released a terms update today that says:
"we may remotely change software, systems, applications, features or programming on your device without notice"
Just be aware and be careful! Loved this ROM while it lasted but water under the bridge now. Edit: "Love this ROM!"

Update 3/6/2021 - Phone fixed:

My phone is fixed. I did not update OOS before flashing AOSiP so this issue was very likely my fault. I had to flash back to OOS and then re-flash AOSiP. Full scenario and instructions are below; feel free to disregard the rest if you followed anirudhgupta109's instructions correctly.

Scenario
About 7 days after the February update the device no longer recognized the SIM card. When I attempted to re-flash OOS, the bootloader got half-way locked (showed as unlocked but would not let me do anything).

This was a factory and carrier unlocked phone, which was weird. As stated above, T-Mobile might have some super secret controls over our devices. The phone ran fine for 7 days after the February 13th update, so I did not think that it was caused by my inability to follow instructions. Still not 100% sure.

How it was fixed:
Gather latest images for flashing:
Download necessary files from this and the latest OOS from maronofrio's thread
Get Unlock code from T-Mobile
Gather info from command - `fastboot oem get_unlock_code`
  • Returned a blank IMEI for me, don't freak out
  • Locate your box or type in #06# to return your device IMEI
  • The unlock code should be clearly marked
Go to website and fill in the form - http://www.oneplus.com/unlock_token
Wait a week, and follow the instructions that get emailed to you....

Now you can flash OxygenOS
## Back up your data, this process will delete it ##
You now have to re-lock and re-unlock your bootloader. These were the commands I used in Manjaro (Arch) Linux

  • fastboot oem lock
  • sudo fastboot flash cust-unlock '/home/nick/Downloads/unlock_code.bin'
  • sudo fastboot oem unlock
  • sudo fastboot reboot bootloader
  • cd Downloads/OB1-GLOBAL-OnePlus7TOxygen_13.W.01_OTA_001_all_2003061944_9cb2036f4e514fe9-FASTBOOT
  • fastboot -w
Follow OOS re-flashing instructions here - https://forum.xda-developers.com/t/...t-stock-fastboot-roms-for-oneplus-7t.3979213/

Now run all phone updates, this will take a bit, so grab a beer or 3


Re-Install AOSiP
Follow the instructions anirudhgupta109 posted at the beginning of this thread

Closing
When I saw that there was no IMEI I was worried that my persist.img file was corrupted, this happens sometimes with Samsung and OnePlus devices. To alleviate this concern for the future, I rooted the device (posted by anirudhgupta109) at the beginning of this thread. Once rooted, I was able to install a terminal emulator to back up recovery_a, recovery_b, and persist using the following instructions:

You will need to log into terminal as su

 
Last edited:
  • Like
Reactions: livinglight

livinglight

New member
Feb 16, 2021
4
1
For anyone new, be sure to back up persist.img. After the last update my IMEI got deleted and it does not appear to be recoverable.

The update worked for about 1 week, it's possible my device just wasn't checked by the network for that week. It's also possible that T-Mobile deleted it since they just released a terms update today that says:

Just be aware and be careful! Loved this ROM while it lasted but water under the bridge now.

Wow. Thank you for telling me this. I'm shocked. Do you think your imei was stolen and used to flash on a device with a stolen imei?

Anyway, I decided to avoid the 7T for now. Until official twrp exists, its not worth it. I need the guarantee of LineageOS. 4/5/6s are all great devices. I would love the camera on the 7, though!!
 

Nick-Henkey

New member
Feb 23, 2021
3
1
Wow. Thank you for telling me this. I'm shocked. Do you think your imei was stolen and used to flash on a device with a stolen imei?

Anyway, I decided to avoid the 7T for now. Until official twrp exists, its not worth it. I need the guarantee of LineageOS. 4/5/6s are all great devices. I would love the camera on the 7, though!!
The 6 is supposed to be a great device.

I doubt the IMEI was stolen because there's no way to flash it without using someone else's persist.img file. A foreign persist.img will block some of the phone's functionality and appears to be closed-source.

Apparently custom ROMs overwrite this file sometimes during updates; TWRP is great because it protects against this. XDA board leaders highly recommend backup (I screwed up by not doing research). My phone worked fine for a full week after the February 13th update, so I don't think that's what broke the device. You can back up persist.img on your own with root.

There's one more thing I can try... re-flash OOS. The IMEI shows up in some screens but not others so my initial diagnosis is hopefully wrong. Somehow my boot-loader is locked BUT showing unlocked. I can't lock then unlock the thing because it's demanding a carrier unlock token (4 more days). It was a carrier unlocked phone.
 

Nick-Henkey

New member
Feb 23, 2021
3
1
Where have you heard this? This is the first time for me hearing this.
Not from XDA, but this is a known risk from custom ROMs (Samsung most affected):

This is one of two threads that I found with veteran board members that appeared to be irritated that people did not take backups:

Backup Instructions:

There are several YMMV guides on XDA if persist.img gets corrupted:
 

Sporos

Member
Jan 6, 2020
20
11
Ever since I installed this rom I can't seem to get rid of the super partition. I want to revert to the previous partition layout with system_a and system_b so that I may dual boot. I've tried everything, I just flashed 3 different builds with the MSM tool and my partition layout is still not how it was before. How can I reverse this and get the normal partition layout back?
 

Lossyx

Senior Member
Jan 14, 2014
1,422
574
OnePlus 7T Pro
Ever since I installed this rom I can't seem to get rid of the super partition. I want to revert to the previous partition layout with system_a and system_b so that I may dual boot. I've tried everything, I just flashed 3 different builds with the MSM tool and my partition layout is still not how it was before. How can I reverse this and get the normal partition layout back?
All devices launched with A10 has this partition layout, it's called Dynamic partitions. This includes OOS. And no, it's not really possible to get old partition structure back. Dual booting is not possible either.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Is this rom for the HD1905 or 1907?
    Both
  • 51
    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


    Source code:

    AOSiP Gerrit Review
    AOSiP Github
    Kernel Source
    (A massive thanks to @0ctobot and @RenderBroken for the help with the kernel)


    Latest Downloads:

    Official Server | SourceForge Mirror
    NOTE:

    - Download the Fastboot images zip of the variant you want

    - There are two variants, "Official" does not contain Gapps while "Gapps" does.


    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 OnePlus 7T

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

    ROM OS Version: Android 10
    ROM Kernel: Linux 4.x
    ROM Firmware Required: OxygenOS 10.0.2 or above
    Based On: AOSP

    Version Information
    Status: Stable

    Created 2019-12-14
    Last Updated 2020-05-06
    36
    Reserved

    INSTALLATION PROCEDURE:
    MAKE SURE YOU'RE ON THE LATEST OOS FROM HERE

    DO NOT EVER WIPE SYSTEM OR VENDOR ON THE OP7T!!!!!

    Considering how the 7T doesn't have TWRP and has dynamic partitions, I'll try to explain everything in detail:

    1. If you're coming from another ROM (including OOS) or need to perform a clean flash:
    • Boot into the bootloader (if you don't know how to do this, you should probably not flash)
    • Connect your phone to your PC and in an ADB/Fastboot shell, wipe device using
      Code:
      fastboot -w
    • Connect your phone to your PC and in an ADB/Fastboot shell, type
      Code:
      fastboot reboot fastboot
      NOTE: If command prompt/line complains about fastboot not being a valid target you need to update fastboot from HERE
    • Your phone should now be in fastbootd (the UI is exactly like recovery mode so don't get confused)
      Read about fastbootd HERE
    • Type the following to make sure your phone is in fastbootd while also making sure your phone is in the recovery-like UI
      Code:
      fastboot getvar is-userspace
    • If the above does returns the value true you can now flash the ROMs, if it doesn't try figuring out what went wrong (I don't want to hear about the failed attempts, please don't spam the thread with them)
    • Type this command to flash the ROM:
      Code:
      fastboot update <ROM.zip>
      NOTE: IF COMMAND LINE IS SAYING:
      Code:
      archive does not contain 'xyz.sig'
      This is normal, ignore it.
    • After the above is done, your device will automatically reboot to AOSiP, have fun!
      OPTIONAL:
    • If you want magisk, patch the boot image from the AOSiP site which ends in the name -boot.img, in Magisk manager
    • Boot to bootloader
    • Boot into that image (DO NOT FLASH!!!)
      Code:
      fastboot boot magisk_patched.img
    • Install Magisk manager and from it select Install > Direct install
    • Reboot and enjoy AOSiP with Magisk!
    • Enjoy
      OPTIONAL:
      If you'd like to convert to F2FS:
    • Open settings>system>reset options and select Erase all data (factory reset)
    • This'll wipe all data and convert your device to f2fs automatically!

    2. If you're updating the ROM:
    a. Via the inbuilt Updater
    • When you get a notification of new build available, tap it
    • Tap Download
    • Wait for Download
    • Tap install
    • Wait for install
    • If you use Magisk, open Magisk Manager, select install, select Install to Inactive Slot (After OTA)
    • Tap reboot
    • Enjoy!!
    b. Manually via bootloader
    • Disable all substratum overlays if you have a theme applied
    • Boot into fastbootd
      If you're booted into the system
      Code:
      adb reboot fastboot
      If you're booted into bootloader
      Code:
      fastboot reboot fastboot
    • Flash the ROM using
      Code:
      fastboot update <ROM.zip>
      NOTE: YOU DO NOT NEED TO WIPE DATA WHEN UPDATING
    • Reboot to system and enjoy
    NOTE: If you have issues with Settings or Play Services force-closes you need to clean flash (Method 1).

    KNOWN ISSUES:
    Auto brightness is wonky in dark enviroments Fixed in 20200625
    21
    Reserved

    Reporting Bugs
    • 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.)
    • Include your OOS base versions in reports. (Eg: 10.0.1, 10.0.2, 10.0.6 etc.)
    • Mention any and all Magisk modules you might be using along with the Magisk version
    • 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.
    21
    FREQUENTLY ASKED QUESTIONS:
    Q: Fastboot isn't allowing me to flash system image, what am I doing wrong?
    A: You haven't booted to fastbootd (the UI looks like recovery and fastboot devices command shows the device in fastboot mode)

    Q: What GApps do I flash?
    A: You cannot flash Gapps on the device, use the Gapps variant build instead if you need Gapps.

    Q: When booting to the Magisk patched image, it leads to crashdump mode.
    A: You didn't select the first two options in Magisk Manager before patching the boot image under Advanced settings (i.e. Preserve force encryption and Preserve AVB 2.0/dm-verity).

    Q: Do I have to wipe data if coming from another ROM?
    A: Yes, I will not be providing help/support to users that haven't wiped data when coming from another ROM.

    Q: How often will I be getting updates?
    A: The plan is for weeklies, if unavoidable circumstances come up, please don't spam the thread. I will release a build as soon as one is ready.

    Q: Does VoLTE/VoWiFi work?
    A: VoLTE works, I have tested on Airtel in India and a couple of my US based testers have too.
    VoWiFi (WiFi Calling) works based on my testers in the US and for me on Airtel (India), let me know about other carriers.

    Q: Does Android Auto work?
    A: I don't have accessibility to an Android Auto vehicle nor the hardware but my testers have confirmed that it works! Let me know if it does for you too so that others have concrete proof about it.

    Q: I ended up on CrashDump mode, how do I get back to my system?
    A: Theres a valuable thread HERE which can help restoring your system, you WILL LOSE ALL DATA and I will not be blamed under any circumstances.

    Q: Is the ROM official?
    A: The ROM is Official.

    Q: I use Telegram, where can I find help on that platform?
    A: There is a common AOSiP Group Chat for all devices, the link is HERE

    Q: Does SafteyNet pass and is the SELinux Enforcing?
    A: Yes, SafteyNet does pass out-of-the-box and SELinux is Enforcing.

    Q: What OOS Base firmware do I use?
    A: OOS 10.0.6 is the recommended base firmware right now.

    Q: I'm having high idle drain, please fix.
    A: I'll need more data from you to figure it out, Install BetterBatteryStats and let me know about what it tells you after 3-4 charge cycles. Please do not report issues when having apps like Greenify, Naptime, Wakelock blocker etc.

    Q: My phone is stuck on the "Bootloader is unlocked" warning page, why isn't my system booting?
    A: Since there are a bunch of scripts being executed when the device is sent a power on signal, it might take some time to boot. Don't panic, your system will boot fine after some time. All builds are personally tested by me and a few testers.
    20
    New Alpha build dated 20200117 is out!

    The link to ROM is in the OP.

    The procedure to update from existing AOSiP to the new one is in the 1st page, give it a read!

    There were a ton of crucial updates to the ROM including fingerprint and vibration.
    Shifted back to only FP area brightness boost and improved accuracy for it. If you had issues in the past with FP on older builds or other ROMs, give this a go since it definitely should be an improvement and let me know.
    Brightness flicker shouldn't be present at all when using FP but the colour shift is normal when placing finger on sensor which can't be overcome.
    Vibration has been improved and responds exactly like stock OOS, a massive thanks to @rituj_b

    As usual let me know about any issues with the ROM.

    Changelog:
    Code:
    Switch fingerprint brightness only to fingerprint area
    Remove brightness flicker (colour shift is normal and can't be avoided due to power consumption causing a shift in gamma)
    Upstream kernel to 4.14.165
    Updated Wireguard module to January 5th
    Merge in latest OnePlus changes to kernel
    Disable Dolby Atmos support
    Fixed some sepolicy
    Kill sysinit
    sm8150-common: Use custom vibration configs
    Launcher3: add dark primary support
    Add more default permissions from Google
    Track vendor/overlays
    Clean up class preloading
    Utils: Update notch check logic
    AlarmManagerService: Add null check to QCNsrmAlarmExtension call
    Fix cannot see "see more" button in UI
    Settings: Bump privacy category's initial expanded children count to 10
    Don't change nouns in summaries to lower case for German
    fingerprint: Allow devices to configure sensor location
    DevelopmentSettings: Hide OEM unlock by default
    Fix SystemUI glitches from ambient display
    NtpTrustedTime: Refresh NTP server from resources before requesting time
    SystemUI: Use matching data usage size formatting between QS and Settings
    Update NotificationRecord of snooze even after it is cancelled
    Limit the retry attemps on restarting Bluetooth
    Services exit fg when bg-restricted app leaves top
    Telephony: Direct return false for unsupport sms platform.
    fingerprint: handle PerformanceStats NULL pointers
    sensors: Create bool to select what timestamp to use
    PowerProfile: allow overriding default power profile
    Merge changes for launching wifidisplay from system settings
    Check GL extension is supported before using it in glwallpaper
    Reduce unnecessary NotificationListener binder transaction.
    Don't clear the output array if it failed to open the proc status file
    Fix memory leak in aapt2
    aapt2: disable leak detection
    Fix FD leak in ConnectivityManager.getConnectionOwnerUid
    Apply JNI optimizations to HwParcel
    AudioService: Remove Analog Dock from fixed-volume devices
    Correction in logic of roundend size calculation of SD card
    Fix bug Device that can't support adoptable storage cannot read the sdcard.
    AppOpsService: Watch op mode changes when an AppOp restriction dies
    audio: Don't play sound effects if stream is muted
    Color/tint the wifi/mobile status bar icons correctly
    Remove a user/userdebug difference.
    core/Build: ro.system when comparing fingerprint
    overlay: Introduce AOSiP Primary
    Settings: fix hardcoded black text in storage summary
    OwlsNest: integrate ThemePicker
    vendor: Add a bunch of accents for ThemePicker
    Correct fingerprint position during setup
    CameraService: Support hooks for motorized camera
    Fix Issue Where SignalStrengthGsm is null
    toasts: Increase elevation to 4
    toasts: Follows theme corner radius
    core: Materialize Toast notifications
    Gesture nav Assistant handles: don't show them in lockscreen
    PowerMenu: Tint lockdown with the system accent
    PowerMenu: Fix Advanced button position on low DPI
    PowerMenu: Only tint items once
    Dark theme: Clean up
    Address a memory leak
    Suggestion cards: Align them to searchbar
    In sim1 APN settings interface and hot plug out/in sim2, APN information change to sim2's
    fingerprint: Remove unnecessary spacing in enroll layout
    Remove empty space in tether preference
    SearchBar: Add avatar to search bar
    vendor: Conditionally include our Prebuilts repo
    ueventd: make parallel restorecon functionality optional
    adb: host: Provide better sideload status
    NFCService: Add sysprop to prevent FW download during boot  with NFC off.
    No Calendarwidget 4x4 widget displayed
    Use common style for recents task menu divider
    Use Google's strings for Google now panel
    Let's make the search bar on all apps round
    Launcher3: Add updated Google Feed lib from Pixel 3 launcher
    Launcher3: Allow swipe for google now to be optional
    Launcher3: Animate workspace when animating the Google now page
    Launcher3: Make sure service is connected before trying to unbind
    Launcher3: Support google now tab
    Launcher3: Import reversed google now lib
    Launcher3: Can't search out local app by Chinese
    Use new widget style for Google searchbar
    Launcher: disable uneeded dev settings
    Add back button to Settings
    Stability NullPointer issue
    Elevate to 'core/platform' app'
    Launcher3: correctly apply grid changes from grid control provider
    Launcher3: fix preview rendering after adding qsb switch
    Launcher3: add switch to hide search widget
    prebuilt: backuptool: Implement dynamic system mount for A-only
    Revert "recovery: Blank screen during shutdown and reboot"
    Support PRESIGNED in soong_app_prebuilt.mk
    releasetools: Move system mount handling to backuptool
    releasetools: squash backuptool support
    Improve scrolling cache
    base: set scrolling to 0.006f
    Gboard: Set pixel theme as default
    Allow tuning of heaptargetutilization
    Trigger GC when 90% heap is utilized
    Add dalvik-heap device configs for 8/12/16 GiB devices
    Add dalvik-heap device-configs for 4/6GB devices
    Don't print critical path parallelism ratio if elapsed time is 0.
    Take into account RAM usage for multiproduct_kati
    Revert "soong: Default kati jobs to NumCPU()"
    Add TotalRAM detection
    Fix crash in call stats.
    Dialer: AudioModeProvider: use wired route for usb headsets
    Control dialer's incoming call proximity sensor check via an overlay
    Dialer: disable anti-falsing for call answer screen
    Dialer: adaptive icon
    Dialer: define app category
    Re-add call statistics.
    Allow per-call account selection.
    Add setting to enable Do Not Disturb during calls
    Allow using private framework API.
    Revert "Remove dialer sounds and vibrations settings fragments and redirect to the system sound settings fragment instead."
    libhardware: Add new display types.
    aosip: sounds: Fix default sounds
    aosip: Switch to Pixel sounds
    Statusbar clock date: behave like on stock when showing QS panel
    Add VOLTE icon toggle
    SystemUI: Show 4G instead of LTE switch
    Fix VOLTE icon color on Light statusbar
    VoLTE: Add New Minimal Icon
    base: Fix padding for VoLTE icon
    SystemUI: Enhancement for volte icon
    SystemUI: Query IMS state after CapabilityCallback is regisered
    SystemUI: Fix HD icon missing
    Adapt to IMS registration changes.
    SystemUI: Refactor the feature of volte icon
    SystemUI: Fix volte icon doesn't update in real time
    SystemUI: Add new configuration for displaying Volte icon
    soong_config: Add BOOTLOADER_MESSAGE_OFFSET
    manifest: update to android-10.0.0_r23
    vendor: elgoog: fix new permissions for Q
    releasetools: ota_from_target_files: add FullOTA_PostValidate
    build: ota: Support for install tools in /tmp/install
    Thanks for your feedback and support ;);)!
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone