Database Info

[ROM] [12.1] [OFFICIAL] AICP 17.1 [OOS12] [instantnoodle] - OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
*
*/
Feature list (rough overview)
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
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
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!!
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/.
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
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.
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
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:
GitHub - AICP/kernel_oneplus_sm8250
Contribute to AICP/kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
Device tree source:
AICP/device_oneplus_instantnoodle
Device tree for OnePlus 8. Contribute to AICP/device_oneplus_instantnoodle development by creating an account on GitHub.
github.com
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!!​

For further support you can visit our TG Channel:
AICP Support Channel for OnePlus 8 Devices
PLEASE BE ADVISED - YOU MUST UPDATE TO OOS12 FIRMWARE BEFORE INSTALLING THE 8/23 UPDATE.
​
If you are on OOS11 based Stock or Custom ROM:
Best approach is to flash stock OOS11 and update to the latest for your device OOS12 OTA.
While it's done, you can follow the flashing instructions over stock OOS12 given below.​
Click to expand...
Click to collapse
The current firmware upgrade path is available here as found on the Op8 series Telegram support group:​
Spoiler
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:
FirmWares - Google Drive
drive.google.com
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 then install the new update:
Android12L - Google Drive
drive.google.com
9. Now, you can update via OTA safely.
IF YOU ARE ON STOCK OOS12
These instructions are for you:​
Spoiler
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 !

Hi thanks all for your tremendous efforts
If we are on OOS 12 then do we have to revert to OOS11 ?

adsxlnc said:
Hi thanks all for your tremendous efforts
If we are on OOS 12 then do we have to revert to OOS11 ?
Click to expand...
Click to collapse
We are preparing OOS 12 based trees. Till then, yes - please go back to latest OOS 11 then flash AICP. 12.1

What a pleasant surprise, love your work semdoc, can't wait to get home and flash this.

Wow great rom, I was looking for one with the built in adblock and no gapps. Fast, smooth, and very light weight. I also love the custom work you did on the QS <3

Amazing work, I like the easy to follow instructions as well. I was on the Tmobile version that was OOS 11. After a long research I flashed the global version of OOS 10, then OTA to OOS 11. I tried to flash multiple different A12 roms, but all of them crashed. This was the only A12 rom that worked for me. The system runs smoothly, I also like all the added features. I used MindTheGapps and Magisk 25.1, both work correctly. I then used Konabess to overclock the gpu to 925 MHz.

Issilar said:
Amazing work, I like the easy to follow instructions as well. I was on the Tmobile version that was OOS 11. After a long research I flashed the global version of OOS 10, then OTA to OOS 11. I tried to flash multiple different A12 roms, but all of them crashed. This was the only A12 rom that worked for me. The system runs smoothly, I also like all the added features. I used MindTheGapps and Magisk 25.1, both work correctly. I then used Konabess to overclock the gpu to 925 MHz.
Click to expand...
Click to collapse
Have you try Nameless rom ever brother,, i have the same t mobile version of ur phone,, nameless isnt work for me. qualcomn crash damp happened

Hiya! I've turned on the always-on display, and have noticed that i have to turn the screen on to get the fingerprint sensor to work (most of the time. I think it's active a few seconds after screen lock?)! Is there any way around this? OxygenOS seemed to turn the sensor on with a finger press no matter the AOD state
cheers!

Hey I was on T-Mobile Android 11. I tried to unlock the bootloader and flashed this ROM. The phone does not capture the network anymore. Also the GAPPS installation via adb sideload is failing. Any idea?

ditomathew said:
Hey I was on T-Mobile Android 11. I tried to unlock the bootloader and flashed this ROM. The phone does not capture the network anymore. Also the GAPPS installation via adb sideload is failing. Any idea?
Click to expand...
Click to collapse
I've had other roms do this before, run MSM restore tool, then unlock bootloader (and adb debugging) then re do the installation

RogueVisual said:
I've had other roms do this before, run MSM restore tool, then unlock bootloader (and adb debugging) then re do the installation
Click to expand...
Click to collapse
Thanks I did that, and now I reinstalled.

allen-evan said:
Have you try Nameless rom ever brother,, i have the same t mobile version of ur phone,, nameless isnt work for me. qualcomn crash damp happened
Click to expand...
Click to collapse
Nameless works just fine on my device, TMO OP8

Small but IMPORTANT note for anybody experiencing issues coming from OOS and trying this for the first time. I could not get the ROM to boot until I flashed the "copy partitions" zip from Lineage. (https://wiki.lineageos.org/devices/...suring-all-firmware-partitions-are-consistent).
Until I flashed this I would install the ROM and then try to reboot to recovery and it would go straight to the bootloader. If I switched back to the other slot I could get back to recovery but could not proceed further.
So my install instructions looked like this: (because I was doing some trial and error I had installed the ROM a few times hence it being here twice)
adb sideload ROM.zip (I believe you can skip this one but cannot say for certain) -> adb sideload copy-partitions.zip -> adb sideload ROM.zip -> reboot to recovery -> adb sideload GAPPS.zip -> reboot to system
If you get stuck on the bootloader you can use fastboot to check your active slot and then switch back to the previous slot to get back into recovery.
Check current slot:
Code:
fastboot getvar all
Look for the line that says:
Code:
(bootloader) current-slot
The two options are "a" or "b". Then switch to the other slot with:
Code:
fastboot --set-active=a
OR
Code:
fastboot --set-active=b
Another small note, "Apply Update > Install from ADB" (terms are from memory, should be close enough) inside of the Lineage Recovery is what you are looking for to enter adb sideload mode. I had used TWRP previously and didn't know how to get this working at first in Lineage Recovery.

is it possible
to install with official twrp recovery ??

Does this rom works with OnePlus 8 Verizon 5G UW (IN2019)? Does the SIM work?

I tried using the Android 12 based builds but end up in soft-bricked state every time where only MSM can recover. Why is this?
I have T-Mobile OP8, unlocked. I just MSM back to A10, unlock bootloader, convert to global, update to latest A11, install lineage recovery, flash EU A12 firmware, flash ROM, reboot to bootloader -> softbricked at this point with QDLoader in device manager.
Tried asking in telegram but the bot banned me for flooding for sending exactly 1 message.

graycorgi said:
I tried using the Android 12 based builds but end up in soft-bricked state every time where only MSM can recover. Why is this?
I have T-Mobile OP8, unlocked. I just MSM back to A10, unlock bootloader, convert to global, update to latest A11, install lineage recovery, flash EU A12 firmware, flash ROM, reboot to bootloader -> softbricked at this point with QDLoader in device manager.
Tried asking in telegram but the bot banned me for flooding for sending exactly 1 message.
Click to expand...
Click to collapse
ROM {Firmware|Vendor} required: Latest OOS 11

Larkin24 said:
ROM {Firmware|Vendor} required: Latest OOS 11
Click to expand...
Click to collapse
They have ones for Android 12 firmware on their support telegram channel for this device (link in OP). I only posted here because their telegram bot bans you without warning if you type too long of a message.

graycorgi said:
They have ones for Android 12 firmware on their support telegram channel for this device (link in OP). I only posted here because their telegram bot bans you without warning if you type too long of a message.
Click to expand...
Click to collapse
SORRY NO OOS 11
I have the same phone OOS 11 Firmware.
Latest tmoble Firmware
OnePlus Updates Tracker
An automated channel that tracks OnePlus Oxygen and Hydrogen OS ROMs releases. https://github.com/androidtrackers/oneplus-updates-tracker More automated channels that you may like: @yshalsager_projects Developed by: @yshalsager
t.me

Related

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
StatiXOS for OnePlus 7T (hotdogb)
About us
StatiXOS is a custom ROM based on the Android Open Source Project aiming to be minimal while providing quality of life improvements and up to date security patches.
Source code
Spoiler
GitHub
Gerrit
Features
Spoiler
Feature List
Screenshots
Download StatiXOS here
Spoiler
Download StatiXOS
Mirror
GApps are included!
Stay in touch
Our Telegram channel​
ROM OS Version: 11.0
ROM Firmware Required: OOS 10.0.16 (Global Version)

You're free to flash StatiXOS with Lineage Recovery, TWRP or fastbootd
Clean Flash
Spoiler
The last OOS you flashed to your phone (doesn't necessarily need to be the flashed right before StatiX) needs to be the latest stable global variant, you can get it here.
Spoiler: Easiest way: fastbootimages
Download the ROM from here (or our mirror server)
Reboot to bootloader
Flash StatiX by executing
Code:
fastboot update <statix_hotodgb-...-.zip>
(Replace the text between the "<>" with the actual zip name and remove the "<>")
Spoiler: Through LOS Recovery
Download the recovery from here (or our mirror server)
Flash LOS recovery by executing
Code:
fastboot flash recovery <recovery-hotdogb-...-.img>
(Replace the text between the <> with the actual zip name)
Reboot into recovery mode
Format your data to f2fs
Go back to the main menu and tap Apply Update
Tap Apply from ADB
Sideload the ROM by executing
Code:
adb sideload <statix_hotodgb-...-OFFICIAL.zip>
(Replace the text between the <> with the actual zip name)
Reboot
You'll find more info in this section of LineageOS Wiki
Spoiler: NOT ADVISED: Through TWRP
Reboot to bootloader (!= fastbootd)
Connect your device to a computer and execute:
Code:
fastboot -w
Note: This will format your data, which means that a backup is advised
Reboot to recovery
Flash the ROM zipfile
Reboot to bootloader once again and execute
Code:
fastboot -w
Reboot to system
Spoiler: Through fastbootd
Dump the ROM zipfile through payload_dumper
Reboot to bootloader (!= fastbootd)
Connect your device to a computer and execute:
Code:
fastboot -w
Note: This will format your data, which means that a backup is advised
Now reboot to fastbootd executing:
Code:
fastboot reboot fastboot
Flash each partition (be sure to open the terminal window in the folder you extracted the payload):
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
Reboot to system
Spoiler: Magisk
You can install Magisk by patching the boot image (which can be found here, download the one with the same date as the build you've flashed) or flashing its zip (Version 21.0+) once you've booted for the first time.
Update
Spoiler
Spoiler: Easiest way: Builtin OTA Updater
Go into Settings > System > Updater
Check for Update
Once it's finished updating press "REBOOT"
Note: Remember to flash whatever add-on you need (eg. Magisk) before rebooting to the other slot
Spoiler: Through TWRP
Disable thedevice PIN/Passcode
Reboot to recovery
Flash the ROM zipfile
If you want to flash further zips (e.g. Magisk) reboot to recovery to switch slots
Reboot to system
Add back your PIN/Passcode
Spoiler: Through fastboot
Dump the ROM zipfile through payload_dumper
Reboot to bootloader (!= fastbootd)
Now reboot to fastbootd executing:
Code:
fastboot reboot fastboot
Flash each partition (be sure to open the terminal window in the folder you extracted the payload):
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
Reboot to system

F.A.Q. / Various Info
At the moment I'm shipping LOS kernel, for a simple reason: it's the only one that doesn't have issues with MTP, I'll switch to a custom solution as soon as OnePlus releases OOS11 kernel sources. In the meantime you're free to use a custom kernel (I highly suggest neutrino) if you don't care about MTP and rather prefer a better battery life.
SELinux is Enforcing and builds are user.
This ROM has been tested with Verizon and everything works as expected.
If you end up in a bootloop after a clean flash reboot to recovery and format your data partition to either ext4 or f2fs.
If you encounter issues with the fingerprint sensor be sure to flash the latest stable version of OOS (be sure to flash ALL the partitions, if you can use the unbrick tool/msmtool is even better, remember to select the "global" variant from the dropdown menu before starting the process) and then flash StatiX on top of that.
TWRP can't decrypt so you must disable your PIN/Passcode prior to rebooting to TWRP.
Follow these steps to format your filesystem to f2fs using Built-in/LOS recovery
Spoiler: Switch to f2fs
Clean flash the ROM using your preferred method
Boot into the system
Reboot to recovery
Tap on "Factory reset"
Tap on "Format data/factory reset"
Select "f2fs"
Tap on "Format data"
Reboot
[*][*][*][*][*]
You can fully pass SafetyNet by following these steps:
Spoiler: How to pass SafetyNet
Right after the first boot flash Magisk through your favorite method
Boot back into system
Open the Magisk app and enable MagiskHide
Install the MagiskHide Props Config module through the Magisk app
Reboot
Install and open a terminal app (e.g. Termiux) -or use adb shell-
Give it root permissions by entering
Code:
su
Enter
Code:
props
Enter
Code:
1
(aka "Edit device fingerprint")
Enter
Code:
f
(aka "Pick a certified fingerprint")
Enter
Code:
21
(aka "OnePlus")
Enter the number corresponding to your OnePlus 7T model
Confirm by entering
Code:
y
Reboot
Open the Magisk app and check SafetyNet status, you should now pass both basicintegrity and ctsProfile
Clear storage of both Google Play Store and Google Play Services
Enjoy
[*][*][*][*]
GPay fully works! How? Here it is:
Spoiler: How to setup GPay
Be sure to fully pass SafetyNet
Install GPay
Enable MagiskHide for GPay
Clear storage of both Google Play Store and Google Play Services
Install GPay
Enable MagiskHide for GPay
Enjoy
[*][*][*][*]
Known Issues:
Setting the USB preference to "File transfer" to trasfer files between the phone and PC leads to crashdump mode.
Workaround: keep the device connected to your pc and force reboot to bootloader by holding vol up + vol down + power, reboot to system: file transfer should now work fine. FIXED!

Nice

Another rom! Awsome!! Can't wait to try this out

Is there a three-finger screenshot?

Is there face unlock and how reliable is the fingerprint compared to stock?

swt95237 said:
Is there a three-finger screenshot?
Click to expand...
Click to collapse
Not yet, will be implemented very soon.
Nicholas6706 said:
Is there face unlock and how reliable is the fingerprint compared to stock?
Click to expand...
Click to collapse
No face unlock. Fingerprint is just as fast and reliable as on OOS, with no flickers whatsoever.

Any chance for micro G support?

NisseGurra said:
Any chance for micro G support?
Click to expand...
Click to collapse
MicroG hasn't been tested, but keep in mind that we (currently) prebuild our custom gapps package, which means that you'd need to remove any trace of it if you want to install MicroG.

zzkW35 said:
MicroG hasn't been tested, but keep in mind that we (currently) prebuild our custom gapps package, which means that you'd need to remove any trace of it if you want to install MicroG.
Click to expand...
Click to collapse
Yes, but to have microg support the services.jar need to have spoofing support.
As now there is no way to add it afterwards until smali has been updated to support android 11

NisseGurra said:
Yes, but to have microg support the services.jar need to have spoofing support.
As now there is no way to add it afterwards until smali has been updated to support android 11
Click to expand...
Click to collapse
At the moment I don't see a reason to support signature spoofing on the source side of things, since our builds contain gapps. Nonetheless if we added said support, would you really go through the hassle of first removing the built-in gapps and then installing microG?

Everything is working fine and smooth until now. I think this is the best implementation of adaptive brightness I've seen on custom ROMs on the Oneplus 7T. I'm having a little worse signal on wifi and on mobile but I think all custom ROMs are the same, I have a router that changes 2.4ghz and 5ghz wifi depending on the reliability and it doesn't seem to keep 5ghz for long, on OOS it did but I think it's the same on all custom ROMs I've tried until now. A+ for this first build.
Edit: Also a little things I've noticed (not major): Lockscreen colors are somewhat different before you unlock the phone, also when lockscreen (or always on screen) the fingerprint logo is full brightness even if you're not touching it.
Edit 2: Sorry, it was a known issue.

hectorviov said:
Everything is working fine and smooth until now. I think this is the best implementation of adaptive brightness I've seen on custom ROMs on the Oneplus 7T. I'm having a little worse signal on wifi and on mobile but I think all custom ROMs are the same, I have a router that changes 2.4ghz and 5ghz wifi depending on the reliability and it doesn't seem to keep 5ghz for long, on OOS it did but I think it's the same on all custom ROMs I've tried until now. A+ for this first build.
Edit: Also a little things I've noticed (not major): Lockscreen colors are somewhat different before you unlock the phone, also when lockscreen (or always on screen) the fingerprint logo is full brightness even if you're not touching it.
Edit 2: Found a bug, when connecting with USB to computer, if you change to file transfer mode, instead of only charging, system crashes. I once got a qualcomm dump screen and the second time that I tried it soft rebooted.
Click to expand...
Click to collapse
Its stated on the op.

hectorviov said:
Everything is working fine and smooth until now. I think this is the best implementation of adaptive brightness I've seen on custom ROMs on the Oneplus 7T. I'm having a little worse signal on wifi and on mobile but I think all custom ROMs are the same, I have a router that changes 2.4ghz and 5ghz wifi depending on the reliability and it doesn't seem to keep 5ghz for long, on OOS it did but I think it's the same on all custom ROMs I've tried until now. A+ for this first build.
Click to expand...
Click to collapse
I'll look into this asap.
hectorviov said:
Edit: Also a little things I've noticed (not major): Lockscreen colors are somewhat different before you unlock the phone, also when lockscreen (or always on screen) the fingerprint logo is full brightness even if you're not touching it.
Click to expand...
Click to collapse
I'm aware, it's a way to avoid weird screen flickers when FOD is pressed. Will be very likely fixed in the next release.
hectorviov said:
Edit 2: Found a bug, when connecting with USB to computer, if you change to file transfer mode, instead of only charging, system crashes. I once got a qualcomm dump screen and the second time that I tried it soft rebooted.
Click to expand...
Click to collapse
This is a known issue, check the 3rd post of this thread.

Awsome!! thanks

@zzkW35 phil da hero

zzkW35 said:
I'll look into this asap.
I'm aware, it's a way to avoid weird screen flickers when FOD is pressed. Will be very likely fixed in the next release.
This is a known issue, check the 3rd post of this thread.
Click to expand...
Click to collapse
for the icon dim one, we forward ported it on yaap (also there on aosip gerrit under https://review.aosip.dev/q/topic:"eleven-fod-dim"+(status:open OR status:merged) for quick repopicks) configurable by overlay so shouldnt mess with other devices either

Fingerprint entry and fingerprint unlocking are too slow Fingerprint entry is almost unavailable

OmkarTheAndroid said:
for the icon dim one, we forward ported it on yaap (also there on aosip gerrit under https://review.aosip.dev/q/topic:"eleven-fod-dim"+(status:open OR status:merged) for quick repopicks) configurable by overlay so shouldnt mess with other devices either
Click to expand...
Click to collapse
Thanks
谷歌原生 said:
Fingerprint entry and fingerprint unlocking are too slow Fingerprint entry is almost unavailable
Click to expand...
Click to collapse
As I already wrote in a previous reply: with stock kernel and no janky Magisk mods FOD is just as fast as on OOS. Have you changed kernel and/or flashed Magisk mods?

⚠ This project is no longer maintained. See below. ⚠
You are encouraged to migrate to the official nightly builds (huge thanks to @anishpratheepan and to the LOS team for bringing that up). If you update from an unofficial build, it is highly recommended that you opt-in for build signature check after the flash:
Open Settings
Privacy => Trust
Check "Build signature" at the very bottom
Note that you should be able to update from unofficial to official builds seamlessly, without wiping anything.
-----
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Unlock your bootloader
Backup everything, especially the "persist" partition
Make sure you're on a recent version of OxygenOS.
Download the latest build
Run the following commands:
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot fastboot
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot reboot recovery
Wipe all data from recovery.
(Optional) If you need GApps, NikGApps Core are known to work ("Apply update" => "Update from ADB", and then run adb sideload <NikGapps-xxx-arm64-11-yyy.zip>). Note that other variants than Core can crash.
Reboot.
Downloads:
https://drive.google.com/drive/folders/1V17qsn_wMpwPgJHMhCjfYYmZEPGzPvP2
Known issues:
Displays "Charging slowly" when it's actually not
Build signed with public keys for now
Reporting Bugs:
Make sure the bug you want to report isn't already known
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 /proc/last_kmsg. (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. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][UNOFFICIAL][instantnoodle][11] LineageOS 18.1, ROM for the OnePlus 8
Contributors
KennyG9, LuK1337
Source Code:
Since February 2021 (based on the official LineageOS device tree):
Device tree: https://github.com/LineageOS/android_device_oneplus_instantnoodle
Kernel: https://github.com/LineageOS/android_kernel_oneplus_sm8250
Proprietary blobs: https://github.com/TheMuppets/proprietary_vendor_oneplus
Before February 2021 (based on LuK1337's work on instantnoodlep with minor adjustments to the device tree):
Device tree: https://gitlab.com/nlr/android_device_oneplus_instantnoodle
Kernel: https://github.com/luk1337/android_kernel_oneplus_sm8250
Proprietary blobs: https://github.com/luk1337/proprietary_vendor_oneplus
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2021-01-07
Last Updated 2021-02-10

Very cool. Stoked. Can you add link for gapps as I know lineage needs to work properly.

mattie_49 said:
Very cool. Stoked. Can you add link for gapps as I know lineage needs to work properly.
Click to expand...
Click to collapse
I don't have GApps myself and I don't want to flash them on my personal device. I'm fine with adding a link in the original post provided that one or two person can confirm it works and provide instructions. I think NikGApps are the best candidate.

KennyG9 said:
I don't have GApps myself and I don't want to flash them on my personal device. I'm fine with adding a link in the original post provided that one or two person can confirm it works and provide instructions. I think NiksGApps are the best candidate.
Click to expand...
Click to collapse
Fair enough. Thank you for bringing this to the op8 community.

I made an attempt to bundle OpenGApps into the build: https://drive.google.com/file/d/1edechrEwpX5L5SjE6OlsAjRckT-UF69t/view (using https://github.com/opengapps/aosp_build). It bootlooped on my device but I suspect that's because it requires a factory reset which I didn't want to do. Flashing instructions are identical, just make sure you have flashed OOS 11 at some point. If that happens to work for some of you, I'll try to publish both flavors with every release.

KennyG9 said:
I made an attempt to bundle OpenGApps into the build: https://drive.google.com/file/d/1edechrEwpX5L5SjE6OlsAjRckT-UF69t/view (using https://github.com/opengapps/aosp_build). It bootlooped on my device but I suspect that's because it requires a factory reset which I didn't want to do. Flashing instructions are identical, just make sure you have flashed OOS 11 at some point. If that happens to work for some of you, I'll try to publish both flavors with every release.
Click to expand...
Click to collapse
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?

mobile_sensei said:
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?
Click to expand...
Click to collapse
LOS builds only contain a few subset of all the partitions that exist on the OP8 (system, boot, product, dtbo, and some others). The OP8 also contains a lot of other proprietary partitions (ABL, AOP, bluetooth, modem, etc…) that only the manufacturer is able to provide updates for. As far as I understand, those blobs must also be updated to be able to run Android 11 without issues. If you don't update them, it'll likely bootloop or refuse to boot and it's not recommended anyways.
I'm not sure upgrading from 17.1 to 18.1 without wiping is even possible, but if you want to give it a shot, I think your best bet is to extract all the proprietary images from a recent OOS build, then flash them and flash LOS 18.1 over that. You may avoid the annoying MSM step, but my bet is that you'll have to wipe anyways if you want to boot, so I strongly advise that your backup all your data and apps before. In deeper details, you need to :
- get a recent and official OOS 11 build from here : https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300
- extract the payload.bin from the image using a tool like this one : https://github.com/LineageOS/scripts/blob/master/update-payload-extractor/extract.py
- reboot to bootloader (adb reboot bootloader)
- flash the stock recovery you just extracted (fastboot flash recovery recovery.img)
- reboot into stock fastboot (fastboot reboot fastboot)
- flash all the blobs you just extracted (fastboot flash abl abl.img && fastboot flash aop aop.img && fastboot flash bluetooth bluetooth.img && ………)
- follow LOS 18.1 flashing instructions from the first post

mobile_sensei said:
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?
Click to expand...
Click to collapse
Yes I agree here.
I and need step by step exact instructions how to flash any rom here.
I am not even gonna try to flash this rom because I know my device is gonna end up at the Qualcomm dump mode.
I can't get anything booted if I flash anything coming from OOS11, don't ask because I have no idea why.
The only way to get my device booting stock rom at this point is to flash stock rom in EDL mode with the msm tool
[OP8][OOS 21AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
My device is OnePlus 8 5G - 12GB/256GB Interstellar Glow- Firmware : Firmware: OxygenOS - GE / EN / FR / ES
IN2010
Inspected 2020.06.18
As TWRP isn't working completely is there way to do the equivalent full system backup with all partitions without TWRP perhaps via fastboot? Because I know I'm not gonna be able to flash a rom its gonna be the same story over and over again setting up the same stock rom over again ..it gets old.
Because custom software for OnePlus 8 is not at the stage of flash and forget I think a unified toolkit in a zip is needed.
It can be separate or bundled with each rom release and regularly updated that I can extract and cd into, and run the fastboot commands from to help making flashing roms and debug as accurate as we possibly can starting with all of us using the same exact toolkit to begin with.
Driver used
Developer framework ie fastboot, adb executable
Payload dumper
Readme File
Bat/sh file for automation
perhaps payload/img files
bundled with rom Gapps with dev, flavor and release because this seem to be subject to not booting
This would make sure everyone is 100% following the same exact instructions making debugging much easier, in this case it seem like gapps one piece of the puzzle possibly preventing rom from booting, in my case I'm can't even make it to square one getting stuck at Qualcomm dump mode..
Spoiler
KennyG9 said:
LOS builds only contain a few subset of all the partitions that exist on the OP8 (system, boot, product, dtbo, and some others). The OP8 also contains a lot of other proprietary partitions (ABL, AOP, bluetooth, modem, etc…) that only the manufacturer is able to provide updates for. As far as I understand, those blobs must also be updated to be able to run Android 11 without issues. If you don't update them, it'll likely bootloop or refuse to boot and it's not recommended anyways. I'm not sure upgrading from 17.1 to 18.1 without wiping is even possible, but if you want to give it a shot, I think your best bet is to extract all the proprietary images from a recent OOS build, then flash them and flash LOS 18.1 over that. You may avoid the annoying MSM step, but my bet is that you'll have to wipe anyways if you want to boot, so I strongly advise that your backup all your data and apps before. In deeper details, you need to : - get a recent and official OOS 11 build from here : https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300 - extract the payload.bin from the image using a tool like this one : https://github.com/LineageOS/scripts/blob/master/update-payload-extractor/extract.py - reboot to bootloader (adb reboot bootloader) - flash the stock recovery you just extracted (fastboot flash recovery recovery.img) - reboot into stock fastboot (fastboot reboot fastboot) - flash all the blobs you just extracted (fastboot flash abl abl.img && fastboot flash aop aop.img && fastboot flash bluetooth bluetooth.img && ………) - follow LOS 18.1 flashing instructions from the first post
Click to expand...
Click to collapse
Good information, I didn't finish my reply during breakfast and noticed you wrote one more.
The only thing I am not comfortable with is that there are links to tools that I have to download from the internet.
Its one factor subject to being sourced from random google searches.
Like the fastboot binary from xda although old doesn't work on op8, I found out the hard way and I am now downloading this directly from Android developer page.
But a lot of headache could be eliminated trying to figure out where and which binaries should be used, what work and what does not.
Is fastboot/adb bundle too old or driver not installed?
Did all of us follow the exact same installation steps in detail the rom developer did?
I hope you understand.
This device has been the most problematic I've ever dealt with

SUPERUSER said:
Yes I agree here.
I and need step by step exact instructions how to flash any rom here.
I am not even gonna try to flash this rom because I know my device is gonna end up at the Qualcomm dump mode.
I can't get anything booted if I flash anything coming from OOS11, don't ask because I have no idea why.
The only way to get my device booting stock rom at this point is to flash stock rom in EDL mode with the msm tool
[OP8][OOS 21AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
My device is OnePlus 8 5G - 12GB/256GB Interstellar Glow- Firmware : Firmware: OxygenOS - GE / EN / FR / ES
IN2010
Inspected 2020.06.18
As TWRP isn't working completely is there way to do the equivalent full system backup with all partitions without TWRP perhaps via fastboot? Because I know I'm not gonna be able to flash a rom its gonna be the same story over and over again setting up the same stock rom over again ..it gets old.
Because custom software for OnePlus 8 is not at the stage of flash and forget I think a unified toolkit in a zip is needed.
It can be separate or bundled with each rom release and regularly updated that I can extract and cd into, and run the fastboot commands from to help making flashing roms and debug as accurate as we possibly can starting with all of us using the same exact toolkit to begin with.
Driver used
Developer framework ie fastboot, adb executable
Payload dumper
Readme File
Bat/sh file for automation
perhaps payload/img files
bundled with rom Gapps with dev, flavor and release because this seem to be subject to not booting
This would make sure everyone is 100% following the same exact instructions making debugging much easier, in this case it seem like gapps one piece of the puzzle possibly preventing rom from booting, in my case I'm can't even make it to square one getting stuck at Qualcomm dump mode..
Good information, I didn't finish my reply during breakfast and noticed you wrote one more.
The only thing I am not comfortable with is that there are links to tools that I have to download from the internet.
Its one factor subject to being sourced from random google searches.
Like the fastboot binary from xda although old doesn't work on op8, I found out the hard way and I am now downloading this directly from Android developer page.
But a lot of headache could be eliminated trying to figure out where and which binaries should be used, what work and what does not.
Is fastboot/adb bundle too old or driver not installed?
Did all of us follow the exact same installation steps in detail the rom developer did?
I hope you understand.
This device has been the most problematic I've ever dealt with
Click to expand...
Click to collapse
I don't have a definitive answer to everything, but here are some remarks:
- Not sure what exactly your problems were and I'm unaware of any way to backup partitions using fastboot unfortunately. As far as I know, it was not possible to restore nandroid backups using mauronofrio's TWRP on Android 10 either. I think the best you can achieve for now is software and data backup (using "adb pull" and "OAndBackup+" or something else). I can also attest that I had way more weird partitioning issues when using TWRP than LOS' fastboot. Since I stopped using TWRP, I never had to use MSM again.
- What you may attempt to reduce the risk of bricking your device is to take advantage of the A/B partitioning. You can flash everything on the unused slot and switch back to the working slot if anything goes wrong. This can be done by running "fastboot getvar current-slot" to get the current slot, then "fastboot --set-active=a" to switch to slot a (or "fastboot --set-active=b" to switch to slot b, depending on which slot was active).
- I second your reluctance on using tools coming from untrusted sources. Please, don't get fastboot/adb from XDA, use the official Android builds. I can't help you regarding the drivers as I use Linux which ships with drivers, but if you use Windows try to get those drivers from either Microsoft, OnePlus or Qualcomm directly. My instructions to avoid flashing Android 11 with MSM makes you use an official image from OnePlus (which you have to trust anyways) + an open-source tool that's made by LOS developers (which you have to trust anyways). At this point, I think the weakest point of trust if you don't want to build LOS yourself is me.
- Regardless of what you attempt, always make sure you have backups of your valuable data, apps and persist partition. Especially given how capricious this device is .

working great so far. any way to re-enable the 90Hz refresh rate?
edit: found it in display options!

LuK1337 said:
OP8 is no longer supported so RIP.
Click to expand...
Click to collapse
New flash method for both 8p and 8t does not allow to use it on instantnoodle, migrated yesterday from there to this build and it's working perfect with NikGapps-core and Magisk, great job @KennyG9

any way to get the OP camera app working? tried several versions available on APKMirror, but all seem to crash. maybe there are some dependencies?

Does OnePlus 8 tmobile version work with dual sim on this rom?

veridiam said:
any way to get the OP camera app working? tried several versions available on APKMirror, but all seem to crash. maybe there are some dependencies?
Click to expand...
Click to collapse
There's a lot of proprietary software/firmware (apart from the camera apk itself) that its not included in LOS. There have been some ports in the past (e.g. OnePlus6 OOS Camera port or oxy-ify) but all of them seem dead, maybe because google camera port working out of the box.
Creating a magisk module should be doable, but you need to start the app, let it crash and add the missing dep N times until you have all of them

@LuK1337 , please accept pull request: https://github.com/luk1337/android_kernel_oneplus_sm8250/pull/1

Running great. I would mention that only nikgapps core works. The rest for me ended in a crash whilst setting up.

passion8059 said:
Running great. I would mention that only nikgapps core works. The rest for me ended in a crash whilst setting up.
Click to expand...
Click to collapse
Thanks, just updated first post to mention that.

KennyG9 said:
Thanks, just updated first post to mention that.
Click to expand...
Click to collapse
Would you be able to look into face unlock? Handy feature for me especially at work.

passion8059 said:
Would you be able to look into face unlock? Handy feature for me especially at work.
Click to expand...
Click to collapse
Face unlock is an OxygenOS feature and I don't think AOSP or LineageOS supports something like that officially as it's quite terrible security-wise. GApps also dropped support for face unlock in Android 10 because of security concerns. So unless I'm missing something it probably won't happen anytime soon unless through some third-party module, sorry. It's not just about porting some blobs, it's a whole new OS feature.

Is WiFi calling and LTE calling working?

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
NOTICE:
This is the last update before i sold this phone.
[Please make sure you updated to 58.1.X (Which is Android11)]
+ Camera key and Assist Key Fix
+ Update to R based
+ Fix the issue about 5Ghz hotspot
+ March Security Update
About LineageOS:
LineageOS is a free, community built, aftermarket firmware distribution of Android 11.x (R),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website : http://lineageos.org
About LineageOS Legal : http://lineageos.org/legal/
Important Information:
1. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
2. This ROM will never work with any versions of Google Camera (GCam)!
3. You need to flash Stock Android 11 before flashing this ROM.
4. For VoLTE, you need to boot into stock firmware and enable it before flashing this ROM!
5. If you came from SODP ROMs, you need to go back to official Android 11 firmware, and boot into launcher.
6. Please make sure you are using Android 11 Stock ROM [Version > 58.1.X] before flash this.
7. Still in developing. May have some unexpected bugs.
Downloads Links
LineageOS 18.1:
Unofficial-build: Link (MEGA)
Looking For CinemaPro And PhotoPro:
Click Here
Google Applications (optional):
NikGApps: https://nikgapps.com
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
How to flash
Make sure you upgraded to Official Android 11 from Sony
Unlock bootloader is necessary.
Download latest platform-tools from google
1. Install fastbootd drivers, guidance
2. Put your device into fastboot by volume up key.
3. Enter fastbootd:
Code:
fastboot reboot fastboot
4. Flash LineageOS:
Code:
fastboot set_active a
fastboot flash boot boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot erase metadata
fastboot flash system system.img
fastboot flash product product.img
5. If you are first time to flash LineageOS, Wipe the old userdata:
Code:
fastboot erase userdata
GApps:
Download my OrangeFox Recovery then flash it
Root access:
Flash Magisk in recovery.
SD CARD Notice:
Format you sdcard into 'FAT32' if your sdcard can NOT be use in this system
Issues and reports:
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with Logcat for example
Bugs:
LDAC (Not sure)
FP Not working in Third Apps
Also thanks to:
BBN Shion Sjll
nezorflame (This build won`t come out so fast without his server)
The LineageOS Team
The CyanogenMod Team
Source:
Kernel Source
Device vendor
Device Tree
Feel free to donate me:
Paypal
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Oh wow it was quick lol thanks a lot for this build once again. Fortunately, there are developers like you.
I have a few questions though :
1. Which version of Magisk will work for root on this build?
2. Can I install full or stock NikGapps without any issues?
3. Does the issue with the sd card mentioned in the post about LOS 17.1 been fixed?
Have a beautiful day.

Stuck on boot on Lineage logo. Have already upgraded to A11 before this, so it might be connected.
Will try to grab logcat.

flyl0 said:
Oh wow it was quick lol thanks a lot for this build once again. Fortunately, there are developers like you.
I have a few questions though :
1. Which version of Magisk will work for root on this build?
2. Can I install full or stock NikGapps without any issues?
3. Does the issue with the sd card mentioned in the post about LOS 17.1 been fixed?
Have a beautiful day.
Click to expand...
Click to collapse
Both Nik's and OpenGApps latest packages should be fine, but you may have issues regarding the size - I wasn't able to install our stock package due to insufficient space.

Nezorflame said:
Stuck on boot on Lineage logo. Have already upgraded to A11 before this, so it might be connected.
Will try to grab logcat.
Click to expand...
Click to collapse
Nezorflame said:
Both Nik's and OpenGApps latest packages should be fine, but you may have issues regarding the size - I wasn't able to install our stock package due to insufficient space.
Click to expand...
Click to collapse
Damn so we can't install full or stock Gapps/NikGapps on LOS 18.1 ?
Anyway i can stay on A10 and flash this rom right ?

As OP said, yeah.

ken442266 said:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 11.x (R),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website : http://lineageos.org
About LineageOS Legal : http://lineageos.org/legal/
Important Information
1. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
2. This ROM will never work with any versions of Google Camera (GCam)!
3. You need to flash Stock Android 10 before flashing this ROM.
4. For VoLTE, you need to boot into stock firmware and enable it before flashing this ROM!
5. If you came from SODP ROMs, you need to go back to official Android 10 firmware, and boot into launcher.
6. You don`t need to upgrade to R vendor (58.1.X).Just stay at Q vendor 58.0.X will be fine.
7. Still in developing. May have some unexpected bugs.
Downloads Links
LineageOS 18.1:
Unofficial-build: Link (AFH)
Google Applications (optional):
NikGApps: https://nikgapps.com
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
How to flash
Make sure you upgraded to Official Android 10.0 from Sony
Unlock bootloader is necessary.
Download latest platform-tools from google
1. Install fastbootd drivers, guidance
2. Put your device into fastboot by volume up key.
3. Enter fastbootd:
Code:
fastboot reboot fastboot
4. Flash LineageOS:
Code:
fastboot set_active a
fastboot flash boot boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot erase metadata
fastboot flash system system.img
fastboot flash product product.img
5. If you are first time to flash LineageOS, Wipe the old userdata:
Code:
fastboot erase userdata
GApps:
Download Lineage Recovery
Flash and boot into Recovery then choose Apply update - Apply from ADB, then sideload the gapps package on your PC with adb tool:
Code:
adb sideload <PATH OF GAPPS>
Root access:
Flash Magisk in recovery.
Issues and reports:
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with Logcat for example
Bugs:
LDAC (Not sure)
Also thanks to:
BBN Shion Sjll
The LineageOS Team
The CyanogenMod Team
Source:
Kernel Source
Device vendor
Device Tree
Screenshots:
View attachment 5194147View attachment 5194149View attachment 5194151
Click to expand...
Click to collapse
Awesome!, did you manage to get the SD card working?

Nezorflame said:
Stuck on boot on Lineage logo. Have already upgraded to A11 before this, so it might be connected.
Will try to grab logcat.
Click to expand...
Click to collapse
The OP says you should use the stock android 10 firmware as a basis, so I'd imagine thats your issue.

Jayram2000 said:
The OP says you should use the stock android 10 firmware as a basis, so I'd imagine thats your issue.
Click to expand...
Click to collapse
Not really - the first post states that "You don`t need to upgrade to R vendor (58.1.X)", that doesn't imply that with R vendor the phone won't boot. If that's the case, then the initial quote is kinda misleading.
In any case, I'll just try Q vendor as well and see how it goes.

So I've been testing different vendor setups and yes, using R vendor will render the ROM not to boot - it doesn't get past the initial boot animation loop.
So I guess it'd be better to correct the first post stating that users MUST use Q vendor in order to be able to boot.

Apparently the sd card bug is still there too..

flyl0 said:
Apparently the sd card bug is still there too..
Click to expand...
Click to collapse
Yup, it doesn't get detected as properly formatted, OS wants me to reformat it.

Nezorflame said:
So I've been testing different vendor setups and yes, using R vendor will render the ROM not to boot - it doesn't get past the initial boot animation loop.
So I guess it'd be better to correct the first post stating that users MUST use Q vendor in order to be able to boot.
Click to expand...
Click to collapse
Thanks for correct. Yeah, You have to use Q vendor.

It's a shame because I will not use this build if my sd card is not recognized

So about sd card issue. I`m not sure what cause this issue. And when i trying to solve this.
It just works fine on my sd card. So i do not know how to solve it as i can`t get some details on it.
So if anybody can provide logcat for format && access sd card that can be great.
By the way. PixelExperience Eleven is on the way.

ken442266 said:
So about sd card issue. I`m not sure what cause this issue. And when i trying to solve this.
It just works fine on my sd card. So i do not know how to solve it as i can`t get some details on it.
So if anybody can provide logcat for format && access sd card that can be great.
By the way. PixelExperience Eleven is on the way.
View attachment 5194959View attachment 5194961
Click to expand...
Click to collapse
I have a 128gb SDXC card from Samsung, I can try again. How can I capture the logcat for the SD?

TIP 1 : If you have an sd card and want to use it on this build you have to format the sd card to fat32, then it will work just fine.
TIP 2 : If you want Gapps on LOS, make sure to choose the core gapps or basic gapps only.

my apologies if this has been answered somewhere. What prevents GCAM from running on xperia devices with either stock or custom roms?

teostar said:
my apologies if this has been answered somewhere. What prevents GCAM from running on xperia devices with either stock or custom roms?
Click to expand...
Click to collapse
The answer is : "SONY"

Works well so far with the SD card formatted to FAT32. Now I have another device for my OpenGApps build testing
Let's hope exFAT support comes soon <3 great work!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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-R 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.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
Pixel Experience Team
AOSiP team
Community
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
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!!
Latest Stable Release Version 16.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/.
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 GApps packages still have issues, however feel free to try other GApps if you want to, just try MindTheGapps if you have any GApps related issues
MindTheGapps: https://androidfilehost.com/?w=files&flid=322935
Mirror: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
You tell...
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 the usual behavior on flashing a new official build by (or using) the build-in updater service.
Q. How do I 'dirty flash' builds?
A. 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.
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.
The ROM should contain everything you need to enjoy Android R. 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!)​
On Clean Flash: mandatory for first install !!!​At the beginning, if you are on Stock OOS 11 ROM with locked bootloader, please follow the instructions for unlocking bootloader here: https://wiki.lineageos.org/devices/instantnoodle/install
1. Download the ROM and GApps to your PC with proper adb & fastboot setup.
Also download to your PC instantnoodle-recovery.img from HERE
2. Boot to bootloader and run in cmd (windows) / terminal (linux)
fastboot flash recovery instantnoodle-recovery.img
4. Boot to recovery. Tap on Factory Reset (this will erase everything on your device) then return to main menu
3. Connect your device to your PC and tap on Apply Update -> Apply from ADB and
4. Flash the ROM zip file using
adb sideload aicp_instantnoodle_r-16.1-WEEKLY-{date}.zip
5. Once its finished, reboot to recovery to flash the GApps (optional, needed for e.g. Google Playstore to work). This is mandatory becoz will switch automatically current slot and will flash GAPPS.
Once it boots to recovery, tap on Apply Update -> Apply from ADB then run
adb sideload GAPPS.zip
6. Reboot and set up your device.
7. Reboot back into recovery.
8. Flash the root solution of your choice (optional).
9. Reboot your device.
The main workflow for flashing via recovery:
reboot to recovery -> adb sideload ROM.zip -> reboot recovery -> adb sideload GAPPS.zip -> reboot to system
Click to expand...
Click to collapse
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 21.4 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
Go to Aicp Extras -> Update Centre then install new Weekly Build.
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: We are building Neutrino Kernel adopted to our sources with permission by Kernel Dev
GitHub - AICP/kernel_oneplus_sm8250
Contribute to AICP/kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
Device tree source:
AICP/device_oneplus_instantnoodle
Device tree for OnePlus 8. Contribute to AICP/device_oneplus_instantnoodle development by creating an account on GitHub.
github.com
Common device tree source:
GitHub - AICP/device_oneplus_sm8250-common
Contribute to AICP/device_oneplus_sm8250-common development by creating an account on GitHub.
github.com
Vendor source:
AICP/proprietary_vendor_oneplus
Contribute to AICP/proprietary_vendor_oneplus development by creating an account on GitHub.
github.com
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
Join us on our Discord Channel
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:[/U[
ROM OS Version: 11.1
Kernel: Linux 4.19.176
ROM {Firmware|Vendor} OnePlus8Oxygen_15.E.35_OTA_0350.
Status: {STABLE}
Release Date: 04-03-2021
You want to see a "normal" night at the "DEV office", click here!!​

AICP recovery: link HERE
---------------------------------------------------------------------------------------------------------------
New build guys
10.04.2021 UPDATE​
Download aicp_instantnoodle_r-16.1-WEEKLY-20210410.zip from HERE
Changelog: link HERE
No GAPPS in the ROM.zip.
** İf you are comming from older version - no need to flash clean.
-- if you are rooted: Just go to Updater in AicpExtras choose the downloaded zip from your storage and install the update.
-- if you aren't rooted:
**** Download the zip. Connect your phone to your PC. and run adb root in terminal (or cmd windows for Win). Then run adb shell setenforce 0 and install downloaded zip as local upgrade from Updater in AicpExtras. You'll be on enforcing selinux mode after reboot
-- You can flash in recovery via adb sideload. İf you choose this way, don't forget to reboot to recovery and flash your GAPPS.zip via adb sideload again.
-- if you want to clean flash:
**** reboot to recovery. Format data then follow the procedure given below:
flash rom.zip via adb sideload -> reboot recovery -> flash gapps.zip via adb sideload -> reboot to system
What's new:
1. April '21 ASB merged
2. Added ALipay fingerprint payment support
3. Screenbrightness fixes for all 3 devices
4. Many fixes including SafetyNet (fixed again)
Enjoy !!!
---------------------------------------------------------------------------------------------------------------
04.04.2021 Build !!!​
Download aicp_instantnoodle_r-16.1-WEEKLY-20210404.zip from HERE.
Changelog: link HERE.
-- There is no GAPPS in the ROM.zip.​Download GAPPS from:
MindTheGapps or OpenGapps Android 11 Nano​
How to install:
1. Go to recovery. Format data if you want to flash clean.
2. Apply Update from ADB
3. then adb sideload aicp_instantnoodle_r-16.1-WEEKLY-20210404.zip
4. Reboot to recovery
5. Flash Gapps via adb sideload GAPPS.zip
** İmportant: Android Auto fails to connect with OpenGapps. All good with MindTheGapps
** There is no DevicePersonalization app in these - if you want, I can provide a modified GAPPS package
6. If you want to switch in between GAPPS packages, just flash other GAPPS package on the new flash. Clean flash isn't trivial, but recommended....
*** Next flashes can go through Updater or adb sideload.
** If you flash via Updater, backup tool will handle your gapps - no need to reflash them again.
** GAPPS need to be flashed on every update if you flash via adb sideload. Flash them as it is described above.
What's new?
** Stock vibration patterns are back
** App Lock from AOSP-A
** Neutrino Kernel updated to 4.19.183
** and many more....
All feedbacks are appreciated, as always.
Cheerz
---------------------------------------------------------------------------------------------------------------
For those who want to ROOT their devices:
Download Magisk 21.4 zip: link HERE
** boot to recovery
** flash via adb sideload magisk.zip:
** reboot.
** Note that you HAVE to do this on every update.
** SafetyNet is fixed on March 5 build !!!
Enjoy !!

Which Camera we can use:
1. Using this Camera: GCam_7.3.018_Urnyx05-v2.1_Wichaya_V3.1.1_snapcam.apk
2. Also I have thix xml file under GCam/Configs7 : nrG Wichaya 7.3.018_v3.1.1.xml

finally! thanks

Very nice. Quick question. Are Verizon a11 blobs merged ? No custom rom currently gets data for us Verizon op8 users?

mattie_49 said:
Very nice. Quick question. Are Verizon a11 blobs merged ? No custom rom currently gets data for us Verizon op8 users?
Click to expand...
Click to collapse
No unfortunately. Doubt it'll work on Verizon.

semdoc said:
No unfortunately. Doubt it'll work on Verizon.
Click to expand...
Click to collapse
Thanks for quick response. I'm gonna try later anyway. He he. Why is it so hard for us to get data/signal on custom roms. Qti telephony ? Or the 5g modem that gets mm wave?

mattie_49 said:
Thanks for quick response. I'm gonna try later anyway. He he. Why is it so hard for us to get data/signal on custom roms. Qti telephony ? Or the 5g modem that gets mm wave?
Click to expand...
Click to collapse
most likely qti telephony....

Rebuilt and re-uploaded initial build. The issue was broken adb sideload . Now fixed and all should be fine.
Download aicp_instantnoodle_r-16.1-WEEKLY-20210305.zip from HERE
Cheers.

Thanks for the rom, working great, but has same issue as all lineage based roms...video calls have audio distorted (too loud) and bad feedback from mic. Any fixes in the pipeline? Thanks again!

passion8059 said:
Thanks for the rom, working great, but has same issue as all lineage based roms...video calls have audio distorted (too loud) and bad feedback from mic. Any fixes in the pipeline? Thanks again!
Click to expand...
Click to collapse
Will check it out Thanx for feedback

passion8059 said:
Thanks for the rom, working great, but has same issue as all lineage based roms...video calls have audio distorted (too loud) and bad feedback from mic. Any fixes in the pipeline? Thanks again!
Click to expand...
Click to collapse
Can you please test this build:
Download aicp_instantnoodle_r-16.1-WEEKLY-20210307.zip from HERE
** Attempt to fix audio ssues.
If you are rooted: Just download the build to your device. Choose from AicpExtras -> Updater and flash after choosing from right upper corner.
If you aren't rooted:
1. go to recovery and flash via adb sideload and reboot.
All feeedbacks are appreciated.

semdoc said:
Can you please test this build:
Download aicp_instantnoodle_r-16.1-WEEKLY-20210307.zip from HERE
** Attempt to fix audio ssues.
If you are rooted: Just download the build to your device. Choose from AicpExtras -> Updater and flash after choosing from right upper corner.
If you aren't rooted:
1. go to recovery and flash via adb sideload and reboot.
All feeedbacks are appreciated.
Click to expand...
Click to collapse
Will update and report back accordingly. Thanks

passion8059 said:
Will update and report back accordingly. Thanks
Click to expand...
Click to collapse
Have tried video call today, mic seems to be fixed but on max volume (I have 2 young boys who won't be quiet ;-)) it still distorts so have to knock it down a bit and struggle to hear what is being said.

passion8059 said:
Have tried video call today, mic seems to be fixed but on max volume (I have 2 young boys who won't be quiet ;-)) it still distorts so have to knock it down a bit and struggle to hear what is being said.
Click to expand...
Click to collapse
LUK merged fixes for all 3 op8 devices today...
So you'll get test builds later today...

hello what interests me can we record the conversation natively?

doc411 said:
hello what interests me can we record the conversation natively?
Click to expand...
Click to collapse
Yes, we have that option in our Dialer.

semdoc said:
Yes, we have that option in our Dialer.
Click to expand...
Click to collapse
thank you very much for your quick rest

New build guys.
You can download aicp_instantnoodle_r-16.1-WEEKLY-20210309.zip from HERE.
-- Please test audio, calls - including whatsapp & telegram calls in all aspects..
-- OOS Style Clear all notificaitons button added
-- Kernel Update by Neutrino kernel dev.
Changelog: link HERE
Cheerz guys

Thanks for the update. Ringing at max is distorted still and there is a severe memory lag where you watch YouTube videos it'll play but then buffer then play again. I'm on a good broadband connection (500mb) and WiFi 6 coverage. Have cleared caches and used ex kernel manager to clear memory buffers but still the same.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
I built this from source because I love crDroid and our main camera doesn't work at all (and other various small nuisances) on the OnePlus 9 Pro crDroid rom. Proceed with caution, this is my first rom. However, things seem stable enough to call it weekly.
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
Download LOS recovery
Download Tiny ADB & Fastboot
Download arm64 gapps (tested with NikGapps Canary Core Gapps)
First time installation (clean flash):
It is recommended to come clean from latest OOS installation
Backup your data to PC, OTG flash drive
Reboot to bootloader (fastboot)
Run fastboot devices to confirm there is connection to the phone
Install LOS recovery with following command fastboot flash boot lineage-18.1-20211212-recovery-lemonade.img
Reboot to recovery with following command fastboot reboot recovery
Navigate with volume keys to Factory Reset -> Format data/factory reset and confirm format of data
Go back to main menu and choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
When asked to confirm flash, do confirm it
Now adb sideload latest gapps package with adb sideload gapps.zip
(if Gapps fails saying it could not mount system, boot to rom, then back to recovery and try sideloading Gapps again)
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Update installation:
Through recovery:
Download latest crDroid zip and reboot to recovery
Choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Built-in OTA (slower):
Might not work until we are official again.
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8350
Download:
ROM https://crdroid.net/lemonade
Changelog:
Changelogs from OP9Pro crDroid since last build should mostly apply:
Initial crDroid 7.13 code base
Updated to December 2021 security patches
Updated to clang 14.0.0
Updated SQLite
Updated libjpeg-turbo
TWRP is included
Some other small changes
Misc fixes and overall improvements
Updated translations
Known issues:
Flashing via USB C Thunderbolt 4 ports may brick your device to edl only mode requiring multiple msm restores to fix.
USB-OTG not working for me at least.
Looking for additional feedback to see.
Visit official website @ crDroid.net
crDroid Lemonade/Lemonadep Telegram
crDroid Community Telegram
Donate to help the crDroid team pay server costs
Donate to buy the maintainer a beer

Reserved

What is the way to go back to normal root 1.2.7.7 if I dont decide to revert back?
Do I still do ADB Sideload even with TWRP?

Don't use twrp for now, use lineageos recovery. When oneplus9 pro crdroid can flash from twrp I will make that ability available here.
If you have a backup made from twrp, I don't see why restoring from it wouldn't work.

Alright sounds good brother.

Glad to see this here for the 9 stoked. I ran on my Verizon variant op8 unlocked for a long time. Very nice.

audalics said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
I built this from source because I love crDroid and our main camera doesn't work at all (and other various small nuisances) on the OnePlus 9 Pro crDroid rom. Proceed with caution, this is my first rom.
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
Until TWRP is ready, this version of crDroid comes with prebaked core Gapps
Download LOS recovery
Download Tiny ADB & Fastboot
First time installation (clean flash):
It is recommended to come clean from latest OOS installation
Backup your data to PC, OTG flash drive
Reboot to bootloader (fastboot)
Run fastboot devices to confirm there is connection to the phone
Install LOS recovery with following command fastboot flash boot lineage-18.1-20210615-recovery-lemonadep.img
Power off and reboot to recovery by pressing VOL down + Power from shutdown state
Navigate with volume keys to Factory Reset -> Format data/factory reset and confirm format of data
Go back to main menu and choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
When asked to confirm flash, do confirm it
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Update installation:
Through recovery:
Download latest crDroid zip and reboot to recovery
Choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Built-in OTA (slower):
When ready
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8350
Download:
ROM https://www.dropbox.com/s/xkd5augxh37cfdk/crDroidAndroid-11.0-20210625-lemonade-v7.7.zip
Changelog:
Main camera sorta works
Camera cutout size and position corrected
Fingerprint hardware fixed
Fingerprint ui element fixed
Other various fixes for op9 vs op9pro
Known issues:
Camera app crashes when switching modes or to selfie camera.
Video recording not working.
Looking for additional feedback to see.
Visit official website @ crDroid.net
crDroid Lemonade Telegram
crDroid Community Telegram
Donate to help our team pay server costs
Click to expand...
Click to collapse
Hi why i have ' E:error 21
package is for product oneplus9 but expected oneplus9pro
Even when i have oneplus 9?

papad13 said:
Hi why i have ' E:error 21
package is for product oneplus9 but expected oneplus9pro
Even when i have oneplus 9?
Click to expand...
Click to collapse
You sure you sideloading correctly?

mattie_49 said:
You sure you sideloading correctly?
Click to expand...
Click to collapse
Yes but i flashed the oneplus 9 pro version of 'crdroid' in the begining .
And noew i see in the product name lahaina. I thing this is the oneplus 9 pro name ?

papad13 said:
Yes but i flashed the oneplus 9 pro version of 'crdroid' in the begining .
And noew i see in the product name lahaina. I thing this is the oneplus 9 pro name ?
Click to expand...
Click to collapse
Op9p is pro

papad13 said:
Hi why i have ' E:error 21
package is for product oneplus9 but expected oneplus9pro
Even when i have oneplus 9?
Click to expand...
Click to collapse
I have updated op to include instructions for resetting the device name if you've previously flashed a op9pro rom

I also have the same error. I tried it a hundred times.

illusiveairforce said:
I also have the same error. I tried it a hundred times.
Click to expand...
Click to collapse
Have you flashed the boot.img I added to the op? I also received this error in testing since I had flashed the OP9Pro crDroid build.

illusiveairforce said:
I also have the same error. I tried it a hundred times.
Click to expand...
Click to collapse
Your coming from aospa and it's built for op9 pro. So if you didn't msm between there is your issue.

mattie_49 said:
Your coming from aospa and it's built for op9 pro. So if you didn't msm between there is your issue.
Click to expand...
Click to collapse
I did msm already but no fix for the name

audalics said:
Have you flashed the boot.img I added to the op? I also received this error in testing since I had flashed the OP9Pro crDroid build.
Click to expand...
Click to collapse
Yep you are the man, Thanks. That worked

Yeah I guess I didnt msm. Now I kind of got all screwed up. I had to reset and wipe a bunch of times. fastboot the 1.2.7.7DA and then installed Magisk. Now my phone bootloops FOREVER but then finally gets to the homescreen. im talking like 15-20mins. It actually does the boot screen twice. I am lost. Can someone help me get back to square one?
Should I update local storage and do 1.2.7.7 all over again or what

illusiveairforce said:
Yeah I guess I didnt msm. Now I kind of got all screwed up. I had to reset and wipe a bunch of times. fastboot the 1.2.7.7DA and then installed Magisk. Now my phone bootloops FOREVER but then finally gets to the homescreen. im talking like 15-20mins. It actually does the boot screen twice. I am lost. Can someone help me get back to square one?
Should I update local storage and do 1.2.7.7 all over again or what
Click to expand...
Click to collapse
Msm now if one is available for your variant. Or use fastboot stock rom in the threads.

ok please help me out.
So I do adb devices and my device shows up.
i do adb reboot bootloader, works and goes to Fastboot, but then nothing i type works. I do fastboot boot patched_boot_11.2.7.7.LE25DA.img and it just waiting for device.
Now heres another. When I turn my game on, Pubg mobile. It says please enable permissions and I do it. But it still says media only. wont let me do files. i dont get it. Is it cause I accidently mounted system or something.
Please help

illusiveairforce said:
ok please help me out.
So I do adb devices and my device shows up.
i do adb reboot bootloader, works and goes to Fastboot, but then nothing i type works. I do fastboot boot patched_boot_11.2.7.7.LE25DA.img and it just waiting for device.
Now heres another. When I turn my game on, Pubg mobile. It says please enable permissions and I do it. But it still says media only. wont let me do files. i dont get it. Is it cause I accidently mounted system or something.
Please help
Click to expand...
Click to collapse
Make sure your instructions call for fastboot boot <img> instead of fastboot flash boot <img>, mixing up the two would cause issues.
As for the Pubg issue with permissions, I am unsure of what you mean.