Database Info

[FAQ][Discussion]LineageOS 15.1 by abhishek987 [ask your questions HERE]

Because LineageOS 15.1 by @abhishek987 thread is bloated by questions anwsered before or not dev related - ask and discuss here - to debloat main thread.
How to flash Lineage 15.1:
!NEW AND THE ONLY RECOMMENDED METHOD!​
You must be on Oreo. Before flashing delete all your saved fingerprints and screen locks.
1. Reboot to bootloader (Bootloader must be unlocked)
2. fastboot boot recovery-xx.img (in ADB)
-> Grab official recovery from here: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
3. Wipe System/Data/Cache/Dalvik
4. Flash Lineage & TWRP Installer zip
-> Grab TWRP installer from the link above
5. Reboot to recovery using TWRP Recovery (In TWRP go to Reboot -> recovery)
6. Flash Gapps/MicroG (opengapps.org -> platform ARM64 -> Android 8.1 + Variant [IMO pico is your best pick])
7. Flash Magisk [latest] if you want ROOT (I bet you want!)
-> Grab Magisk from here: http://tiny.cc/latestmagisk
8. Reboot to System
How to update from previous build:
If you don't have permament TWRP, just follow the method above.
If you have permament TWRP:
Delete all your previous fingerprints (just for safety)
Boot to TWRP
Wipe Data/Cache/Dalvik (wiping is optional - but clean flash is always encouraged)
Flash Lineage ROM zip file
Flash Magisk
Flash Gapps/MicroG
Reboot
KNOWN BUGS:​* No bugs right now! Enjoy bug-free rom!
If you have signal stability issues, try this:
Dial *#*#4636#*#*
Go to Phone information
Set Preferred Network Type from Unknown to LTE or WCDMA only
WHAT IS WORKING:​* Everything else
LINEAGE BUILD CHANGELOG:
Code:
[FONT="Arial"]
[B]Most recent build (24.03.2018):[/B]
Fixed portrait mode
Enabled hal3 camera by default
Added doze
Lineage upstream
[B](22.03.2018): [/B]
Fixed double tap to wake (should only work for focaltech panel)
Rebased kernel to latest oreo source drop
Enabled cpusets
Lineage upstreams
[B](13.03.2018): [/B]
Fixed verity issue (builds now can be flashed without magisk)
Fixed Live Display
Fixed Substratum
Fixed ril issues
Lineage Upstream changes
[B](08.03.2018): [/B]
Fixed notification light (should work in call cases now)
Fixed slow charging
Fixed deep sleep issue
Added navbar toggle
Fixed goodix fingerprint issue (should work for all and all 5 fingerprint should be registered now)
Lineage Upstream changes
[B](06.03.2018): [/B]
Fixed led light
Added fingerprint gestures
Fixed Bluetooth name
Fixed battery capacity
Lineage upstream changes[/FONT]
Have fun with LOS!

Q&A
What does NIGHTLY mean?
Nightlies are automatical builds (every few days), so it mean you will have frequent updates, recent Lineage changes will be present in a rom. Also fixes and new stuff will come faster!
How I can go back to stock?
Grab Mi A1 tool from here: https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857.
Install it in your PC, enable USB Debugging on your phone, plug phone to PC
Click Flash Stock ROM button
Click Download ROM and wait
Click FlashAll. Your phone will reboot to fastboot and it will start to flash stock
[You will loose all your data, so backup is encouraged]
Do I need to downgrade to Nougat before flashing?
Not anymore It's advised to flash from Oreo
After update my FP don't work, wat to do?!
Make a clean flash using method from OP. If clean flash won't help, try: https://forum.xda-developers.com/mi-a1/development/xiaomi-mi-a1-tissot-firmware-flashable-t3759886
Is Dolby working on Lineage 15.1? How to install it?
Just download Magisk module and enjoy!
My mobile signal is unstable. Is there a way to fix it?
Yes, see a workaround from OP
Why Selinux is permissive, not enforcing?
In unofficial builds Selinux is permissive. If the build goes official, it will have Selinux set to enforcing. Don't worry, just wait for official version!
Is this rom stable enough to be a daily driver?
Depends what you need. Check buglist - if these bugs don't bother you - it can surely be a daily driver
When new build will be avaible?
Don't ask for ETAs. Developers are working hard (in their free time!) to fix a bugs - we just need to wait patiently.

Some users are experiencing wifi issues (myself included). How can i fetch the log?
Steps to reproduce: Turn off bluetooth. wait a moment... wifi will start dropping connection a lot. To fix, just turn on BT again.

Headphones do not work.

Headphones are working!
By the way. I found a bug. The equalizer don't work correct. Everytime when you skip a song you must tap the bass regulator again in the equalizer app. When you don't do it, it plays without bass.

konradit said:
Headphones do not work.
Click to expand...
Click to collapse
Everything fine here, try to reflash

Installed and used for 24 hrs with no apparent problems. No fingerprint bug.
All the other bugs reported in OP exists.
Returned to Stock since I found it a bit smoother.
I will wait for a more stable official build
Good work so far

still

rasputine said:
still
Click to expand...
Click to collapse
Are you using the deadman twrp? I got that using other TWRP versions.

goofball2k said:
Are you using the deadman twrp? I got that using other TWRP versions.
Click to expand...
Click to collapse
Yes I'm using deadman's twrp

rasputine said:
Yes I'm using deadman's twrp
Click to expand...
Click to collapse
Did you reboot after doing the data wipe?

Can I install LOS 15.1 without flashing magisk? I have tried this and had bootloop before any lineageos bootlogo

radogost said:
Because LineageOS 15.1 by @abhishek987 thread is bloated by questions anwsered before or not dev related - ask and discuss here - to debloat main thread.
How to flash Lineage 15.1: ​There's a few working methods. First, most popular one:
....
Third, last one:
Boot to the recovery (same recovery as method above)
Wipe system and cache ( data is optional if your are on Oreo)
Check which partition you are on (A or on partiton B)
Flash the rom on one of the partitions
Flash the twrp installer zip
link: http://www.mediafire.com/file/338o7cl72z52rzz/twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip
Reboot back to the recovery
Switch to the second partition
Flash GAPPS/MicroG and Magisk
Reboot
Click to expand...
Click to collapse
Sorry to pick this up again but the last method implies that TWRP will be installed permanently as default recovery, right? I was successfull only with the first method however I always end up in LOS recovery when try to enter recovery with Vol-up+Power after everything is installed.
I'm sure we all agree that this whole recovery mess needs to be sorted out quickly. Even experienced users are hitting snags and flood the board with questions .

goofball2k said:
Did you reboot after doing the data wipe?
Click to expand...
Click to collapse
Yes sir

i face the same issue with any methond i am using.
in some cases i am unable to install all the zips and in another case i am unable to install only magisk(error 1)
i followed exactly the steps.
any suggestions?

I'm not sure why the issues. I followed the steps in the OP, except I didn't flash TWRP, I just boot to it temporarily.
I did the following:
Flashed 7.11.18 ROM using MiFlash.
Booted into the ROM, set it up minimally.
Rebooted to fastboot, unlocked bootloader
booted temporarily to deadman TWRP, wiped system/cache/dalvik/data (just to be sure it is completely clean)
rebooted and then booted back into deadman TWRP
flashed LOS.
rebooted and then booted back into deadman TWRP
Flashed gapps and magisk.
rebooted to OS.

hey guys! If you are in STOCK OREO you need to downgrade to NOUGAT FIRMWARE version 7.11.18 because DEADMAN'S TWRP will NOT WORK PROPERLY in STOCK OREO! DEADMAN'S TWRP is made ONLY to WORK ON NOUGAT rom that's why you get those errors!

Flashed from 8.1.10 without any problems...

ZSL mode of gcam doesn't work..
Can somebody tell me how to disable hardware navigation keys?
---------- Post added at 01:47 PM ---------- Previous post was at 01:47 PM ----------
ZSL mode of gcam doesn't work..
Can somebody tell me how to disable hardware navigation keys?

t0per666 said:
hey guys! If you are in STOCK OREO you need to downgrade to NOUGAT FIRMWARE version 7.11.18 because DEADMAN'S TWRP will NOT WORK PROPERLY in STOCK OREO! DEADMAN'S TWRP is made ONLY to WORK ON NOUGAT rom that's why you get those errors!
Click to expand...
Click to collapse
Tornado95 said:
Flashed from 8.1.10 without any problems...
Click to expand...
Click to collapse
Hmm so which one is telling the truth? ??
Sent from my Xiaomi Mi A1 using XDA Labs

[Solved]Problem Booting Android 10 GSI

Hey, I installed every GSI of android Q. Which is available for our device. So The Problem is Whenever I try to boot gsi with "GAPPS" It Does Boot But The Setup Screen keeps crashing. So, I can't go further then that and it gets stuck in the Setup Screen.
Any Solution?

AmanDevil77 said:
Hey, I installed every GSI of android Q. Which is available for our device. So The Problem is Whenever I try to boot gsi with "GAPPS" It Does Boot But The Setup Screen keeps crashing. So, I can't go further then that and it gets stuck in the Setup Screen.
Any Solution?
Click to expand...
Click to collapse
Resize system partition.

kraken77 said:
Resize system partition.
Click to expand...
Click to collapse
It's not working, I already tried it

AmanDevil77 said:
It's not working, I already tried it
Click to expand...
Click to collapse
On boot connect your usb and open command prompt.
Follow this command and restart.
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1

kraken77 said:
On boot connect your usb and open command prompt.
Follow this command and restart.
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
Click to expand...
Click to collapse
Could you please tell step by step process

AmanDevil77 said:
Could you please tell step by step process
Click to expand...
Click to collapse
When your device is booted connect your phone to pc.
Search for command prompt and open it
Make sure you have adb installed.
Type adb devices
Then type
adb shell settings put secure user_setup_complete 1
Press enter
Type again
adb shell settings put global device_provisioned 1
Press enter and reboot your phone. Done

AmanDevil77 said:
Hey, I installed every GSI of android Q. Which is available for our device. So The Problem is Whenever I try to boot gsi with "GAPPS" It Does Boot But The Setup Screen keeps crashing. So, I can't go further then that and it gets stuck in the Setup Screen.
Any Solution?
Click to expand...
Click to collapse
Can you tell me which Android 10 GSI ROMs booted? I am trying to find one.

blazzer12 said:
Can you tell me which Android 10 GSI ROMs booted? I am trying to find one.
Click to expand...
Click to collapse
it's fixed in new builds, I tried latest pixel experience gsi build and it booted. Everything worked fine except camera, so I reverted back to android pie. I hope someone would find a camera fix for our device in android 10 ROM.

AmanDevil77 said:
it's fixed in new builds, I tried latest pixel experience gsi build and it booted. Everything worked fine except camera, so I reverted back to android pie. I hope someone would find a camera fix for our device in android 10 ROM.
Click to expand...
Click to collapse
Thank you for letting me know! :good:

could you please tell what was the gsi ROM that you installed? yesterday I tried with pixel experience and evolution but it only remained in bootloop

For me Havoc Os 2.9 working perfectly..
Wysłane z mojego SM-A750FN przy użyciu Tapatalka

GSI Problem a7 2018 A750FN
Hi all, i have a problema...... i try to install a gsi10 image (RR7, Piexlex; General, and many more) all rom i install stuck on animation boot...
TWRP 3.2
clear all (cache, system, data, dalvick)
Flash image
Flash Gaaps
Reboot but bootloop on animation
i try to flash also (Permissiver_v5)
someone can help me?? PLS!!

Masok77 said:
Hi all, i have a problema...... i try to install a gsi10 image (RR7, Piexlex; General, and many more) all rom i install stuck on animation boot...
TWRP 3.2
clear all (cache, system, data, dalvick)
Flash image
Flash Gaaps
Reboot but bootloop on animation
i try to flash also (Permissiver_v5)
someone can help me?? PLS!!
Click to expand...
Click to collapse
You need GSI Kernal from "Quantom Kernal For GSI" To Boot the GSI ROM, you can find and download it in the rom and Kernal section of the device on XDA
PS : And also Only download A-Only Arm64 version of the ROM, I have seen that latest build of ROMs work, I have only tried pixel experience and AOSP Yet.

AmanDevil77 said:
You need GSI Kernal from "Quantom Kernal For GSI" To Boot the GSI ROM, you can find and download it in the rom and Kernal section of the device on XDA
PS : And also Only download A-Only Arm64 version of the ROM, I have seen that latest build of ROMs work, I have only tried pixel experience and AOSP Yet.
Click to expand...
Click to collapse
Thanks for the reply, i try it, piexel experience needs gaaps?
about how long do I have to wait to see if everything is going well?
---------- Post added at 07:35 PM ---------- Previous post was at 06:57 PM ----------
Wipe Cache, dalvick, data, system
flash with TWRP "PixelExperience_ARM64-A-10.0-20191115-1115-BETA-UNOFFICIAL"
flash with TWRP "Quantum_Kernel-GSI_A7_v3"
reboot....stuck on boot animation..... Where am I doing wrong....
i wait about 20 min....

I try with AOSP and same problem..... :'(
PLS HELP :'(
---------- Post added at 09:16 PM ---------- Previous post was at 08:44 PM ----------
lrico155 said:
could you please tell what was the gsi ROM that you installed? yesterday I tried with pixel experience and evolution but it only remained in bootloop
Click to expand...
Click to collapse
I have some problem....you solving??
i try also Lineage os 17, havoc 3, AOSP, RRemix 7, all time also install Quantum kernel V3, and try with and without GSI Fix boot.......but not solved......

Masok77 said:
I try with AOSP and same problem..... :'(
PLS HELP :'(
---------- Post added at 09:16 PM ---------- Previous post was at 08:44 PM ----------
I have some problem....you solving??
i try also Lineage os 17, havoc 3, AOSP, RRemix 7, all time also install Quantum kernel V3, and try with and without GSI Fix boot.......but not solved......
Click to expand...
Click to collapse
Nope, maybe it's for the kernel

OK, i try GSI 9 and all work..... .probably problem on Quantum kernel for GSI 10 IHMO, do you find it? any suggestions?

That's what I did for getting Android 10 booted
1. Flash official ONE UI rom of android 9 ( you can go for a framework flash with ODIN or try quantum one UI rom and flash with TWRP)
2. Make A Full boot, and make sure it's booted fine
3. Go to official page of gsi roms at git hub and download any android 10 ROM with "a-only arm64" ver. ( i prefer pixel experience or aosp for yet , because I have only tried these )
PS. Don't forget to extract that ROM file to get a .img file
4. Download Quantum kernal for gsi from the " ROMS And Kernal" section of the device
6. Go to TWRP and wipe data ( Reset )
7. Flash the Quantum Kernal for gsi
8. Flash the System image of the rom that you downloaded
Then Reboot to TWRP again
9. Flash The modified Magisk provided in the download.
Credit goes to : phhusson ( i dont know rom will boot with lastest Magisk)
10. Reboot and it should boot into android 10
-You don't need any other zip file to flash

thanks!!! tonight I try, thank you very much

AmanDevil77 said:
That's what I did for getting Android 10 booted
1. Flash official ONE UI rom of android 9 ( you can go for a framework flash with ODIN or try quantum one UI rom and flash with TWRP)
2. Make A Full boot, and make sure it's booted fine
3. Go to official page of gsi roms at git hub and download any android 10 ROM with "a-only arm64" ver. ( i prefer pixel experience or aosp for yet , because I have only tried these )
PS. Don't forget to extract that ROM file to get a .img file
4. Download Quantum kernal for gsi from the " ROMS And Kernal" section of the device
6. Go to TWRP and wipe data ( Reset )
7. Flash the Quantum Kernal for gsi
8. Flash the System image of the rom that you downloaded
Then Reboot to TWRP again
9. Flash The modified Magisk provided in the download.
Credit goes to : phhusson ( i dont know rom will boot with lastest Magisk)
10. Reboot and it should boot into android 10
-You don't need any other zip file to flash
Click to expand...
Click to collapse
thank you very much, it works!
but unfortunately the camera doesn't

CUstom ROM installation problem, please help

Hi to everyone. I have a european version of the op7 pro. The device produces an issue when using android auto, which I use daily (the bottom bar is rarely responsive to my touches whereas the rest of android auto works fine). So I wanted to try a custom ROM and see if the problem persists.
I tried multiple roms like havoc, aosip and lineage following the respective guides of installation, but regardless of the ROM, I always get stuck at the startup animation when I first try to reboot to system after installing twrp, magisk, gapps etc.
The only rom that seems to work is any version of OOS.
Any help would be greatly appreciated!

Exact what steps you do when installing a custom ROM?

U need to explain how you flash those OS; from my experience on OP6 -> flashing a third party rom need to update it' firmware to match the rom u try to flash, or else it cannot go into system definitely!

Steps :
Unlock bootloader
Boot twrp
Flash twrp
Flash rom
Flash twrp
Reboot to recovery
Once again flash rom
Once again flash twrp
Flash magisk
Flash gapps

Use international version instead of European. This mostly solves the issue.
Also steps should be.
Flash oos
Flash twrp
Reboot recovery
Flash oos
Flash twrp
Reboot recovery
Format data
Flash rom
Flash twrp
Flash gapps (if required)
Flash magisk(if needed)
Flash dm verity (if needed)
Reboot system

pranacrockz said:
Use international version instead of European. This mostly solves the issue.
Also steps should be.
Flash oos
Flash twrp
Reboot recovery
Flash oos
Flash twrp
Reboot recovery
Format data
Flash rom
Flash twrp
Flash gapps (if required)
Flash magisk(if needed)
Flash dm verity (if needed)
Reboot system
Click to expand...
Click to collapse
What oos do I flash? Would you mind linking me to it?:good:

Kama45 said:
What oos do I flash? Would you mind linking me to it?:good:
Click to expand...
Click to collapse
Latest android 10 stable rom available for your phone.

pranacrockz said:
Use international version instead of European. This mostly solves the issue.
Also steps should be.
Flash oos
Flash twrp
Reboot recovery
Flash oos
Flash twrp
Reboot recovery
Format data
Flash rom
Flash twrp
Flash gapps (if required)
Flash magisk(if needed)
Flash dm verity (if needed)
Reboot system
Click to expand...
Click to collapse
I think this post is useful. But what is dm verity, where to find?
I flash the roms and manage to open them but sensors not working on any custom rom. I create a topic to help but nobody cared.

c3drik 67 said:
Latest android 10 stable rom available for your phone.
Click to expand...
Click to collapse
Is that the same as going back to stock with the MSM tool?
Like this one: https://androidfilehost.com/?fid=4349826312261732239

poulidis said:
Steps :
Unlock bootloader
Boot twrp
Flash twrp
Flash rom
Flash twrp
Reboot to recovery
Once again flash rom
Once again flash twrp
Flash magisk
Flash gapps
Click to expand...
Click to collapse
You must Format internal storage before booting into Custom ROM.
Also, when you flash a Custom Rom, when it's done flashing, reboot once more to recovery and then flash the rest like Gapps, Magisk, etc... (Keep in mind that some custom ROMs require once time boot before flashing Magisk).

Kama45 said:
What oos do I flash? Would you mind linking me to it?:good:
Click to expand...
Click to collapse
https://otafsg1.h2os.com/patch/amaz...P.26_OTA_026_all_2003222032_6893aca031668.zip
---------- Post added at 09:09 AM ---------- Previous post was at 09:08 AM ----------
GöğüstekiDövme said:
I think this post is useful. But what is dm verity, where to find?
I flash the roms and manage to open them but sensors not working on any custom rom. I create a topic to help but nobody cared.
Click to expand...
Click to collapse
Dm Verity is to keep the phone unencrypted. I don't use dm Verity but I never faced such problems.
Which rom u using?

pranacrockz said:
https://otafsg1.h2os.com/patch/amaz...P.26_OTA_026_all_2003222032_6893aca031668.zip
---------- Post added at 09:09 AM ---------- Previous post was at 09:08 AM ----------
Dm Verity is to keep the phone unencrypted. I don't use dm Verity but I never faced such problems.
Which rom u using?
Click to expand...
Click to collapse
Oos O2 Beta 11 now. Back when I try, it was oos beta 10. None of custom roms sensors were not working. Like Pixel exp, havoc, lineage
Sent from my OnePlus7Pro using XDA Labs

Never use beta. Always use stable

pranacrockz said:
Never use beta. Always use stable
Click to expand...
Click to collapse
I'll try one more time later. Thanks.

Android 11 Red Magic Rom [FLASHGUIDE]

Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool

Perseo99 said:
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Click to expand...
Click to collapse
Thanks for the update.
I have been planning to upgrade my Red Magic 3 to Android 10 (CN rom) for quite a while now. And its good to know A11 beta has arrived too.
Have you tried fps games on this device like pubg mobile, cod etc? Do they work properly ?
Also, I haven't even unlocked bootloader on my device. Can you proivde a better guide, to completely switch from global rom (stock) to A11 (beta) or A10 CN rom (stable).
Need links / guide for following items -
- Unlock bootloader
- Link of working twrp and steps to flash (should I change recovery after installing this beta?)
- Gapps and Magisk link (As I can't run this device without Google services).
It will be a huge help for me to get started.
Take your time with it (no rush).
Thanks in advance!!!

nalin_s3 said:
Thanks for the update.
I have been planning to upgrade my Red Magic 3 to Android 10 (CN rom) for quite a while now. And its good to know A11 beta has arrived too.
Have you tried fps games on this device like pubg mobile, cod etc? Do they work properly ?
Also, I haven't even unlocked bootloader on my device. Can you proivde a better guide, to completely switch from global rom (stock) to A11 (beta) or A10 CN rom (stable).
Need links / guide for following items -
- Unlock bootloader
- Link of working twrp and steps to flash (should I change recovery after installing this beta?)
- Gapps and Magisk link (As I can't run this device without Google services).
It will be a huge help for me to get started.
Take your time with it (no rush).
Thanks in advance!!!
Click to expand...
Click to collapse
Hey!
No problem at all. I let you here two guides to migrate to the cn rom and even a gsi
Be careful and aware about what you are going to do, It's not specially difficult but you have to get ready all the files and tools in case of brick or bootloops.
Enjoy the flashing!

Perseo99 said:
Hey!
No problem at all. I let you here two guides to migrate to the cn rom and even a gsi
Be careful and aware about what you are going to do, It's not specially difficult but you have to get ready all the files and tools in case of brick or bootloops.
Enjoy the flashing!
Click to expand...
Click to collapse
Thanks for the links. I am planning to update to stable A10 version for now.
I have few questions it be a huge help you could clear some of my doubts -
1. After unlocking bootloader I have to install TWRP (for gapps to run). So should I install TWRP after flashing CN rom ? or before ?
I am asking this because I read in some guides that only CN rom is custom recovery capable.
2. If you have run A10 stables before, does OTA updates require to be installed via TWRP only ?
Will I loose Gapps and Root access if I updated the ota directly from settings? And will every rom flash with TWRP clear my installed apps ?
Thanks in advance for helping!!. ??

nalin_s3 said:
Thanks for the links. I am planning to update to stable A10 version for now.
I have few questions it be a huge help you could clear some of my doubts -
1. After unlocking bootloader I have to install TWRP (for gapps to run). So should I install TWRP after flashing CN rom ? or before ?
I am asking this because I read in some guides that only CN rom is custom recovery capable.
2. If you have run A10 stables before, does OTA updates require to be installed via TWRP only ?
Will I loose Gapps and Root access if I updated the ota directly from settings? And will every rom flash with TWRP clear my installed apps ?
Thanks in advance for helping!!. ?
Click to expand...
Click to collapse
Well, I will go in order:
1. You have to flash first in the stock recovery the Android 10 CN rom and then flash the custom recovery. There is no twrp avaible for global rom. Once in the custom recovery, you can flash Gapps and Magisk (in android 10 there is no need of DFE file, the recovery is able to decrypt data properly.
2. You don't need to get worried about OTAs, there is no a constant software update work by nubia for this device, but in case of update, you would flash the rom from the offcial page, with magisk and gapps again and be sure you keep the custom recovery.

Perseo99 said:
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Click to expand...
Click to collapse
Can you check your pm??

There's no problem in flashing but take note there's no going back i mean you cant downgrade it anymore using unbric tool even if you flash rom using cmd it will not work my rm3s now is bricked theres no tool or method that can fix it right now. Unless someone make a new unbrick tool

jepoyxxv said:
There's no problem in flashing but take note there's no going back i mean you cant downgrade it anymore using unbric tool even if you flash rom using cmd it will not work my rm3s now is bricked theres no tool or method that can fix it right now. Unless someone make a new unbrick tool
Click to expand...
Click to collapse
I already went to 11 and flash to 3.11

But how did you flash android 10 3.11 in rm3s no matter what tool i use i cant fix my rm3s from being bricked by flashing android 11 beta can you tell me what did you do did you flash it manually in command prompt please help me

jepoyxxv said:
But how did you flash android 10 3.11 in rm3s no matter what tool i use i cant fix my rm3s from being bricked by flashing android 11 beta can you tell me what did you do did you flash it manually in command prompt please help me
Click to expand...
Click to collapse
If you are in 11 beta and want to downgrade..just simple flash global version and again flash 3.11 done

What did you use to flash global rom lastweek i successfully installed android 11 beta and use unbrick tool to go back to global but i got bricked. And i cant fix it anymore.

jepoyxxv said:
What did you use to flash global rom lastweek i successfully installed android 11 beta and use unbrick tool to go back to global but i got bricked. And i cant fix it anymore.
Click to expand...
Click to collapse
I just flash global from otg and tham again 3.11

walkwitmeinhel said:
I just flash global from otg and tham again 3.11
Click to expand...
Click to collapse
Could you please tell me where to download the 3.11 rom. I am not aware that this rom exists. Is this a CN or global rom? Thanks for your reply.

[email protected] said:
Could you please tell me where to download the 3.11 rom. I am not aware that this rom exists. Is this a CN or global rom? Thanks for your reply.
Click to expand...
Click to collapse
http://ui.nubia.cn/rom/detail/64

Oh! Didn't expect that. I just post this for Red Magic 3 device users. I don't know how RM3S actually works. Have you tried the unbrick tool from chinese version? Or just flashing the global rom from recovery is enough?

Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...

jepoyxxv said:
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
Click to expand...
Click to collapse
Let's see. Here is a link for Red Magic 3S unbrick tool. Download the non-eu ones.
If you have a Red Magic 3 with Red Magic 3s software, I will provide you the link to the other unbrick tool.
Also, you can try flashing the global rom from the stock recovery included in the package of the A11 rom that you have download.

Thanks for replying my bro.. my device is rm3s i already use rm3 and rm3s unbrick tool.. downloading fire hose programmer and image was successfully but.. my phone is still corrupted... And one thingg i dont have twrp install in my rm3s thats why its hard for me to fix it.. can you please guide or teach me how to flash stock recovery using global rom i know how to use cmd and adb

jepoyxxv said:
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
Click to expand...
Click to collapse
So then, It's not a problem of the unbrick tool, that is actually working properly. The thing is that you didn't know how to do a correct process to migrate from cm rom to global...
The first thing you should do is reboot the phone into fastboot mode (power+vol. Down). Then, connect the phone to the PC and type the next commands in the cmd:
Code:
fastboot devices
in order to see if your device is being recognized
Code:
fastboot oem nubia_unlock NUBIA_NX629J
to unlock the bootloader
Code:
fastboot flashing unlock
in order to make your phone able to boot with a modified software. In the moment you will enter this command, you will see a screen advising you about your data (it'll be erased once you accept to unlock flashing).
After that, you can reboot your phone, that will show you an screen advising you that the bootloader is open. Accept and continue without problems.
Tell me if you have been able to make your phone boot.

Perseo99 said:
Well, I will go in order:
1. You have to flash first in the stock recovery the Android 10 CN rom and then flash the custom recovery. There is no twrp avaible for global rom. Once in the custom recovery, you can flash Gapps and Magisk (in android 10 there is no need of DFE file, the recovery is able to decrypt data properly.
2. You don't need to get worried about OTAs, there is no a constant software update work by nubia for this device, but in case of update, you would flash the rom from the offcial page, with magisk and gapps again and be sure you keep the custom recovery.
Click to expand...
Click to collapse
Required in CN A10 + twrp A10, or maybe from CN A9 + twrp A9 to be able to flash

Development OP9-LEMONADE-A13-ROM-WATCHDOGS-JUNE 25, 2023

I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE!!!
YOU HAVE BEEN WARNED!!!
Watch dogs is a ROM I created and it started with the OnePlus 9 Pro back in December. I have decided to bring it to the OnePlus 9, it's based on LineageOS & crDroid source & dependencies and I thank them for its use. SafetyNet and CTS passes whether your rooted or not. Modules not required. Most features are the same as crDroid but I have made some adjustments to bluetooth quality and some fonts that are not available there, plus Gapps are included.
Before you begin, if you don't have the latest platform tools installed on your windows machine. Download it here:
DO NOT FLASH GAPPS!!!! THEY ARE INCLUDED IN BUILD!!!!!
Flashing Instructions
First time installation (clean flash):
This update requires OOS 13.1 - 13.1.0.500(EX01) firmware
Backup your data
Download the ROM, and firmware flasher listed further down on this post and place all in your platform tools folder,
Extract all the contents in platform tools, Firmware flasher in folder.
You must flash firmware in bootloader.
Boot to recovery and factory reset then adb sideload
adb sideload WatchDogs-13.0-20230625-lemonade.zip
Reboot to system
reboot to recovery if you want root
adb sideload magisk.apk or adb sideload magisk.zip
Reboot to system
Update installation:
Updates can be sideloaded with custom recovery. Updates do not appear in system updater.
Sources:
ROM
Kernel
Downloads:
ROM
FIRMWARE FLASHER
Bugs?
Let me know.

Initial builds
WatchDogs-WITHGAPPS-13.0-20230312-lemonade.zip
WatchDogs-NOGAPPS-13.0-20230312-lemonade.zip
If you require Google apps, flash the first one only!
If you do not want Google apps, flash the second one only!
You can't cross dirty flash a update which should be common sense. Example, you can't dirty flash the with gapps build then next update, dirty flash the no gapps one.

I tried CRdroid recovery and the one I was on and both said name mismatch. Got any suggestions for me to try? Thank you for the new development too!

Telegram group please

lorilucille9 said:
I tried CRdroid recovery and the one I was on and both said name mismatch. Got any suggestions for me to try? Thank you for the new development too!
Click to expand...
Click to collapse
That's weird. Did you try sideloading the firmware flasher first before the ROM? If you still have difficulties, I will post the dtbo, boot and vendor_boot files for you to flash to make it compatible. I don't have this phone. I have the OnePlus9 Pro so I can't test it. I'm sure it works or there would be other users saying the same thing.

I flashed the firmware successfully and tried it again but still got the same error. It wouldn't hurt to post the kit files and recovery for others too. If you do then I'll try again before I have to head into work in a couple hours.
UPDATE:
I used the CrDroid boot-20230106 file and then sideloaded fw_Oneplus9_IN_OOS13_F20 on both slots and was able to flash the rom on both slots successfully. Will let you know what I find in time and thanks again for another version rom to pplay with

lorilucille9 said:
I flashed the firmware successfully and tried it again but still got the same error. It wouldn't hurt to post the kit files and recovery for others too. If you do then I'll try again before I have to head into work in a couple hours.
UPDATE:
I used the CrDroid boot-20230106 file and then sideloaded fw_Oneplus9_IN_OOS13_F20 on both slots and was able to flash the rom on both slots successfully. Will let you know what I find in time and thanks again for another version rom to pplay with
Click to expand...
Click to collapse
Good deal, and no problem. Since I use crDroid sources, I figured that should work. I will still post the files necessary to flash recovery when I get a chance. Let me know if there are any bugs or issues with the ROM itself so I can work on it. Thank you!

I installed it on my first try without any problems. but I couldn't understand how it differs from crdroid.

incesu571 said:
I installed it on my first try without any problems. but I couldn't understand how it differs from crdroid.
Click to expand...
Click to collapse
Bootanimation, fonts, bluetooth, sound audio and other tweaks.

TheSayaMan said:
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
Click to expand...
Click to collapse
thx bro

TheSayaMan said:
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
Click to expand...
Click to collapse
Not to mention Gapps included if you choose it so OTAs with no issues... otherwise you'd have to sideload Gapps again after at least for me that's what was happening.

lorilucille9 said:
Not to mention Gapps included if you choose it so OTAs with no issues... otherwise you'd have to sideload Gapps again after at least for me that's what was happening.
Click to expand...
Click to collapse
correct, sorry, forgot to mention that as well. Thank you!! crDroid doesn't offer a with gapps build. You can use the no gapps build to flash your own gapps but I won't support force close issues with the ROM. Example, pixel setup wizard can't be used because it interfers with the default launcher. And yes, on updates, just sideload the with gapps build and your done, unless you want root, then you will have to reboot and sideload magisk because root will be gone on a update.

incesu571 said:
Telegram group please
Click to expand...
Click to collapse
There is one in my 9 pro thread. I will update when I can.

I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?

Sady94 said:
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Click to expand...
Click to collapse
Convert your T-Mobile to EU as listed on another thread, then you can use the EU firmware. I will be posting a update soon with the boot, vendor_boot and dtbo. If you don't want to do that, I will post them later to flash recovery on your phone. Keep in mind that different variants act different, so you may have bugs on T-Mobile, it wasn't tested.

screenshots?

pubmastervnt said:
screenshots?
Click to expand...
Click to collapse
Not by me, maybe someone else who is running it

MARCH UPDATES: 03/24:
WatchDogs-WITHGAPPS-13.0-20230324-lemonade.zip
WatchDogs-NOGAPPS-13.0-20230324-lemonade.zip

Sady94 said:
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Click to expand...
Click to collapse
You can use my custom recovery, files added in OP. You still need latest stock A13.
fastboot flash --slot all boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img

You cant install this (or any rom but base 11) on tmobile 2117 without BL unlock key. Pretty sure its not possible.
You can only convert to base global 11\OOS11 on 2117 for root, then in ui updater doesnt work OTA or manually. You can get to 13 stock only, because you need to be stock to ota, where you need a key to unlock bootloader again (conversion would bring you back to 11).
*The rooting situation with this phone sucks. I think Jaguar is the only one that will work because it is base 11.