Reverting to OOS12 and trying to flash should fix both of your issues.
No.
Use msm tool to factory reset phone to initial state.
[OPNORD][OOS AC01AA/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
Afterwards install OOS12 update via OTA.
Thank you for your reply. Now I can flash this rom worry free. I will give review soon.
Did all the steps (MSM, OTA to OOS 12) now the new recovery boots fine, I can install the ROM, but now I have the SIM card missing problem.
Because there is still OOS 12 on the other slot, I switched the slot. After booting OOS both SIM card are working well in OOS 12.
Edit: installed the previous version from 20230122, the SIM card are working with this version.
Last edited:
The exact opposite is happening to me, did all the steps and the recovery image doesn't boot for me now.
I flashed from 00S12, got issue no sim detected + "serial console is enabled, to disable, check bootloader" 
During testing I found the following.
If there is OOS12 (or all Android 12 based ROMs ?) in the current slot, then only the new recovery starts, but the A11 based ones no longer.
But if there is an Android 11 based ROM in the current slot, then "old" recoveries start, but the new A12 based not.
So I think the new recovery can't be used for updating from LOS 19 or 20 (20230122).
Last edited:
I'm always confused with this "slot" stuff. I had OOS12 working, made sure i had no problem, then unlocked the bootloader and flashed the new recovery image. Did I miss a step ?
Newer Android phones have two parallel (boot/recovery/system/etc) partitions A and B. One is always active and the other is the "previous" old system, before the last update.
I don't flash the recoveries before updating, I just start them with "fastboot boot recovery.img".
That was a huge help, I was able to get the rom installed, same problems as before though. I'm going back to the previous version for now.
I did the same, now back on LOS 20 - 20230122.
You can use the "new" recovery to downgrade, it warns you, but you can confirm the downgrade while flashing.
Last edited:
HOTFIX RELEASE
Changelog:
Both versions:
- Radio / SIM problems have been fixed
- Serial console has been deactivated, this fixes/removes the notification
Download links to the new versions have been added to the first post of this thread.
Apart from the changes mentioned above nothing has been added. Therefore this release keeps it's name "2023-02-05".
The "please note" section of the original release post remains valid.
It says this is a stable rom without known issues. I hesitate to install it because it is still unofficial. Can someone tell me why? Is something not working?
I noticed when reusing OOS12 yesterday for the upgrade that the sound when listening to music on my headphones was noticeably better than on LineageOS. Disabling audioFX didn't change anything. Searched for the problem and it seems I'm not the only one who noticed this on LineageOS as a whole, people recommended Viper4Android for example, is that worth it ? If someone here as another idea to improve it that would be greatly appreciated, otherwise I think I'm gonna try another custom OS, as much as I like this one, but that's a dealbreaker for me.
I will switch from prebuilt audio stack to OOS one in the next release. That might improve audio quality.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
3First official build is live:
LineageOS Downloads
download.lineageos.org
I flashed the official LineageOS build over a recent unofficial one - no problems so far.
Thank you @MajorP93 and @KakatkarAkshay for all the time and effort that has gone into this!3Official LineageOS
We just released official LineageOS for the OnePlus Nord / avicii.
This means that this unofficial LineageOS ROM will not receive any more updates.
Feel free to switch to official LineageOS and participate in the new XDA thread: *Link*
Any XDA moderator may close this thread.2LineageOs wiki says there is official device support here https://wiki.lineageos.org/devices/avicii/ (links do not work and it says current version is 17, while last supported version was 20). If this means that progress towards official build has been made then I am super hyped and thank you for your work (anyways).1
As far as I can tell it is not pre-rooted, but this worked for me:
0. Please read everything before trying it on your device.
1. Install the magisk apk
2. Go into System > Developes options and enable USB debugging as well as Rooted debugging
3. Open a terminal on your PC, and typeadb root
4. Get a shell on your device withadb shell
5. Navigate to by-name block devicescd dev/block/by-name/
6. Using dd, copy boot_a and boot_b to your internal storage:
-dd if=boot_a of=/storage/emulated/0/Download/boot_a.img
-dd if=boot_b of=/storage/emulated/0/Download/boot_b.img
7. Exit the shellexit
8. Open the Magisk app, tap "install" (the one beside Magisk) and select "Select and Patch a File"
9. Navigate to your Downloads folder, select boot_a.img and click "LET'S GO"
10. After patching is completed rename the file (file name is something like: magisk_patched-25200_NCLa0.img) to magisk_boot_a.img and copy it to your pc (check if the file size matches your original boot_a.img file. If it is 0kb, disconnect your phone from your PC and try step 8-9 again. If it is still 0kb clear Magisk cache and app data and try again)
11. Repeat steps 8-10 for boot_b and rename everything accordingly (magisk_boot_b.img)
12. On your PC terminal typeadb reboot bootloader
13. Once you are in fastboot mode usefastboot getvar current-slotto determine which slot your device is currently using:
14. Flash your boot_[a/b].img
- For "current-slot: a":fastboot flash boot ./magisk_boot_a.img
- For "current-slot: b":fastboot flash boot ./magisk_boot_b.img
(Make sure your terminal is the folder the magisk_boot_[a/b].img files are located in or use absolute paths)
14. rebootfastboot reboot
Done!
When you open the Magisk app again you should see Magisk "Installed [version number]".
Note: This worked for me and seems to be reliable. However I do not take any responsibility for if something goes wrong, loss of data or anything else. If during all of this you get an error, device bootloop or other kind of brick, you can always try flashing the original boot_a.img / boot_b.img (provided you still have them), boot a custom recovery and flash the lineage-20.0-[...].zip and see if it changes anything (I havent tried either as I have never had issues with this method). Alternatively you can use MSMDownloadTool to completely reset your device (This will wipe everything including any custom recoverys and replace them with the stock one).
Further reading:
- Magisk Github
- Magisk installation instructions
- MSMDownloadTool -
39
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, 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.
What's working :
Boots
RIL
Fingerprint
Wi-Fi
Bluetooth
Camera
Audio
Sensors
Flash
GPS
Alert Slider
NFC
DT2W
Known issues :
-
Versions :
There are 2 versions available:
-LineageOS 20 with microG (includes microG, FDroid and AuroraStore)
-LineageOS 20 vanilla (no Gapps / nothing added)
In order to prevent problems please use the recovery image included in this release!
Instructions :
-Download the ROM and recovery image
-Boot into bootloader: adb reboot bootloader
-Boot the recovery image: fastboot boot recovery.img
-Format data / do a factory reset in recovery
-Go to Apply update and choose Apply from ADB
-Sideload the rom: adb sideload rom.zip
Please note:
in order to enable push notifications open up microG services core,
set up your Google account and enable device registration & cloud messaging.
Downloads :
-Recovery image: *Link*
-LineageOS 20 with microG included: *Link*
-LineageOS 20 vanilla (no Gapps included): *Link*
Android OS version: 13
Build author/ROM Maintainer: @MajorP93, @KakatkarAkshay
Kernel Source: *Link*
Device Tree: *Link*
Based on: LineageOS
Status: Stable
Current Stable Version: 20
Stable Release Date: Updated monthly
Created: 2023-01-22
Last Updated: 2023-02-20
Telegram Group: *Link*
Special Thanks:
- to the LineageOS and microG team
- @KakatkarAkshay for putting in awesome work towards bringing up OOS12 firmware based trees.23
HOW TO GET GAPPS IN THE VANILLA VERSION OF THIS ROM:
Reference: *Link*
Follow these steps:
-Download Gapps from here: *Link* (MindTheGapps-13.0.0-arm64)
-Boot into bootloader: adb reboot bootloader
-Boot the recovery image: fastboot boot recovery.img
-Format data / do a factory reset in recovery
-Go to Apply update and choose Apply from ADB
-Sideload the vanilla version of the rom: adb sideload rom.zip
-Reboot into recovery: click advanced --> reboot to recovery (!important do not start LineageOS yet)
-Go to Apply update again and choose Apply from ADB
-Sideload the Gapps package you just downloaded: adb sideload gapps.zip, when prompted select "install anyway" after the "signature verification" message.
UPDATING THE ROM:
Unless I say the opposite in the update announcement, this ROM can be updated using the dirty flash method.
In order to do so, follow these steps:
-Download the new version of the ROM you are using (microG/vanilla)
-Reboot into recovery: adb reboot recovery
-DO NOT CLICK ON FACTORY RESET / WIPE DATA
-Flash the Zip-File of the new ROM: adb sideload rom.zip
Important: if you are using the vanilla version of the ROM,
you have to re-flash Gapps after updating and before starting LineageOS:
-Reboot into recovery: click advanced --> reboot to recovery
-Go to Apply update again and choose Apply from ADB
-Download Gapps from the link above
-Sideload the Gapps package you just downloaded: adb sideload gapps.zip, when prompted select "install anyway" after the "signature verification" message.
12UPDATE 2021-09-29
Changelog:
Both versions:
- Switched to source built kernel
- General performance and stability improvements
- Fixed NFC in source built kernel
- Fixed DT2W
- Updated FOD behavior
- Fixed FOD unlock from AOD screen
- Added support for NXP secure element
- Updated display profile behavior
- Improved touch gestures
Download links to the new versions have been added to the original post.
For update instructions please refer to the second post of this thread.10We reached our crowdfunding goal of 300€!
I just purchased a used Nord device.
@Keertesh is currently working on finding the best option for purchasing his second Nord device.
Thanks a lot to everyone who donated! We are a great community!
We already started working on the scratch bringup.10UPDATE 2023-01-22
New major release LineageOS 20.0
Changelog:
Both versions:
- Initial release
- Android 13
Download links to the new versions have been added to the original post.
Please note:
While upgrading from our latest LineageOS 19.1 release to this LineageOS 20.0 release using the dirty flash method worked in our tests it is strongly recommended to backup your important data before doing so.
If possible do a clean flash instead as it can prevent issues when upgrading to a new major release / new version of Android.
If you like our work and want to support us you can tip us a beer by donating to one (or both) of our PayPal accounts:
Keertesh19: https://paypal.me/keertesh83
MajorP93: https://paypal.me/MajorP93
