[NIGHTLIES][ROM] [11.0.0] ArrowOS POCO X3 [OFFICIAL][SURYA][UNIFIED]

Search This thread

ganesh varma

Senior Member
logo.png

ArrowOS

ABOUT
ArrowOS
is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.

Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net

Checkout more documentation at (maintainership/contributing): Check this out

WHAT WORKS?
  • Almost everything

WHAT DOESN'T WORK?
  • You tell me
Be sure to include a log : check how to

DOWNLOADS
POCO X3 (NFC) (surya/karna)

Note: These are enforcing builds. Safety net checks pass out of the box! No need to flash magisk modules, which might in turn break the integrity!

Builds have been unified now under surya codename for both NFC and non-NFC variants

Tip: Select OEM -> Device,choose Arrow version, choose build type: "GAPPS" or "VANILLA" to download.

Latest Instructions for OSS builds (w.e.f 10/05/2021)
If migrating from pre OSS builds
  • Flash the latest available MIUI 11 firmware. (Flash global or any if you can't find your region)
  • Download and copy arrow build to a OTG prendrive or sd card.
  • Now flash Arrow Vanilla/Gapps build.
  • FORMAT DATA. (You'll loose all your data!)
  • Reboot.
Fresh install coming from MIUI
  • Flash latest available MIUI 11 if you aren't on it already.
  • Install any suitable recovery (mentioned below).
  • Download and copy arrow build to a OTG prendrive or sd card.
  • Flash latest Arrow Vanilla/Gapps build.
  • FORMAT DATA. (You'll loose all your data!)
  • Reboot.
TWRP Recovery by @brigudav :
Note: This build of twrp will support decryption on ArrowOS OSS builds.

ArrowOS Recovery :
Note: This is a very basic aosp recovery only intended for OTA installs. Do NOT expect other functionalities.​
* Do not use with DFE or while unencrypted.​
F.A.Q :

1. My WiFi, bluetooth and network aren't working after updating to OSS build?
A. This happens if you're still on the old Q firmware. Flash the latest available R firmware and then follow the above give steps to properly flash the rom.​

2. Unable to update OTA's using TWRP?
A. The current available recoveries are outdated and are no longer supported for OSS builds. To have a hassle free OTA experience use the above mentioned ArrowOS recovery.
A. Two of the currently supported recoveries are mentioned above.​

Read our blog article/post about:
* GAPPS and VANILLA variants
* Checking build integrity

ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/ArrowOS-Devices/android_kernel_xiaomi_surya

XDA:DevDB Information
ArrowOS, ROM for the Xiaomi Poco X3 NFC

Contributors
ganesh varma, kubersharma, palaych
Source Code: https://github.com/ArrowOS

ROM OS Version: Android 11
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest R firmware
Based On: AOSP, CAF

Version Information
Status:
Stable
Stable Release Date: 2020-11-19

Created 2020-11-19
Last Updated 2021-05-18
 
Last edited:

SkaboXD

Senior Member
Jan 18, 2017
1,045
361
Ganja
Xiaomi Poco X3 NFC

Zen9_o

Member
Nov 1, 2020
13
6
Enforcing/Permissive

can you explain the difference between the two selinux

Enforcing is overall more secure than Permissive. With permissive, you're more vulnerable of having your data stolen. Also banking applications do not work with permissive mode on, although there are some ways to make it work on permissive, such as using magisk hide as well as hiding the magisk manager (by renaming). There are some benefits of permissive, though, using mods such as Viper4Android - whereas on Enforcing it does not work (from my experience). It's totally up to the user to decide which mode is best for them. If it's your main phone and you have banking apps and important information on, then I suggest Enforcing. Whereas if it's your secondary phone without any important information on it, then use permissive and mod it to the fullest extent.
 
  • Like
Reactions: hacker812c

highdude

Senior Member
Aug 10, 2017
58
2
Does it install on updated Android version on Poco x3 nfc?

---------- Post added at 09:39 PM ---------- Previous post was at 09:37 PM ----------

Does fingerprint work after root?
 
  • Like
Reactions: hacker812c

SkaboXD

Senior Member
Jan 18, 2017
1,045
361
Ganja
Xiaomi Poco X3 NFC
Nice to see another rom, but...this:
-WHAT WORKS?
-Almost everything
Soooo, that's clear. 🏻

- WHAT DOESN'T WORK?
- You tell me
;)

---------- Post added at 09:31 PM ---------- Previous post was at 09:28 PM ----------

Just switched over from Lineage. What a blast! Even exFAT support is in! :)

So microSD card should work unlike on NitrogenOS?
 
  • Like
Reactions: hacker812c

Ralx7

New member
Nov 19, 2020
1
1
I have tested the stable ROM (surya) and in the android configuration screen where the language is selected, something that says UI stops, then it continues with the configuration and at the time of activating WiFi it does not search for networks, the configuration can be done with mobile data but it is a great impediment, currently I have installed the unofficial experience pixel ROM for surya with the same installation method and it is perfect
 
  • Like
Reactions: hacker812c

Top Liked Posts

  • 1
    Flashed the ROM with TWRP, did data wipe, and now the phone only boots into TWRP and doesn't boot into system. Any idea?
    Format. Don't wipe.
    1
    Flashed the ROM with TWRP, did data wipe, and now the phone only boots into TWRP and doesn't boot into system. Any idea?
    Format data, the one in which you have to type 'yes'. It will delete all files on your storage.
  • 4
    I'm getting the error:

    assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))
    Updater process ended with ERROR: 1
    Error installing zip file

    Please can someone help! Tried formatting data multiple times
    Fixed in version twrp-3.5.2_10-4-surya
    4
    Ganesh, since you're here, any information on the TWRP encryption issue after the June 9 build?
    I'm yet in the process of figuring it out. I'm completely caught off-guard by this weird issue all of a sudden as there has been literally no changes been made to the device sources nor the rom source so at this point i'm not sure what's even causing it. I've also decompiled the twrp and went through its contents but everything looks fine and dandy in there.

    For now i would suggest to make use of Arrow recovery to meet the needs of OTA updates etc.
    3
    I was on the latest global MIUI and tried to install Arrow, but got a bootloop to orange recovery.

    I followed all the steps, so I'm at a loss for what happened. Orange fox says something about encryption, but the main page of the rom mentions nothing about that for flashing it from stock MIUI.

    I reflashed it stock, unlocked bootloader again, installed the TWRP mentioned in the first post.
    Then installed latest Arrow GAPPS with it, formated data.
    It installed fine, but the ROM wasn't working. System crashing all the time during config.
    1) Download and install latest fastboot ROM which is based on Android 11 (MIUI V12.0.8.0.RJGEUXM Stable Official Update for
    POCO X3 NFC EEA)


    Fastboot, the one which is 4.9 GB

    2) Unlock bootloader.
    3) Install TWRP (twrp-3.5.2_10-4-surya.img)


    4) Install this ROM (I used GApps version)
    5) Format DATA (it's where you have to type in "yes"). Don't do any other wipes before or after installing this ROM.
    6) Reboot and enjoy
    3
    4PDA link to patch not working (error 404).

    Someone needs to get in touch with @ganesh varma to present that solution and upload the patch to the ArrowOS Gitlab Tracker, so that it can be incorporated into the device tree.
    That is because you do not have the 4pda account. That is why it shows that error.

    Here is the .zip patch.
    3
    Neither morals nor stories, i have installed all OTA updates automatically through recovery, except when the developer decided to migrate to OSS Vendor. The installation problems or errors are not due to recovery. They are the fault of users who do not read the recommendations. The migration process has already been discussed for several pages. I don't understand why there are still users stupid to upgrade from a MIUI provider build to the new OSS provider build, simply wanting to update the recovery .zip, when this would mean data loss without having made a copy of security, and then they come here with their irony to complain or cry that they have lost their information
    Wtf are talking about, who said I was on MIUI vendor, I was very clear in my post that I was on the first OSS version before updating to latest ArrowOS.

    That recovery which was supposed to work with OTA ArrowOS from Open Source Vendor to Open Source Vendor didn't work as expected and instead booted to ArrowOS recovery with failed to boot message with one option only and that was to Factory Reset to use my phone again.

    Go back to school and relearn how to read before you start calling people idiots.
  • 52
    logo.png

    ArrowOS

    ABOUT
    ArrowOS
    is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.

    Website: https://arrowos.net
    Telegram: Channel | TG Portal/Links
    Github: https://github.com/ArrowOS
    Code Review: review.arrowos.net
    E-mail: arrowos.contact
    PayPal: Donate to us
    Blog: blog.arrowos.net

    Checkout more documentation at (maintainership/contributing): Check this out

    WHAT WORKS?
    • Almost everything

    WHAT DOESN'T WORK?
    • You tell me
    Be sure to include a log : check how to

    DOWNLOADS
    POCO X3 (NFC) (surya/karna)

    Note: These are enforcing builds. Safety net checks pass out of the box! No need to flash magisk modules, which might in turn break the integrity!

    Builds have been unified now under surya codename for both NFC and non-NFC variants

    Tip: Select OEM -> Device,choose Arrow version, choose build type: "GAPPS" or "VANILLA" to download.

    Latest Instructions for OSS builds (w.e.f 10/05/2021)
    If migrating from pre OSS builds
    • Flash the latest available MIUI 11 firmware. (Flash global or any if you can't find your region)
    • Download and copy arrow build to a OTG prendrive or sd card.
    • Now flash Arrow Vanilla/Gapps build.
    • FORMAT DATA. (You'll loose all your data!)
    • Reboot.
    Fresh install coming from MIUI
    • Flash latest available MIUI 11 if you aren't on it already.
    • Install any suitable recovery (mentioned below).
    • Download and copy arrow build to a OTG prendrive or sd card.
    • Flash latest Arrow Vanilla/Gapps build.
    • FORMAT DATA. (You'll loose all your data!)
    • Reboot.
    TWRP Recovery by @brigudav :
    Note: This build of twrp will support decryption on ArrowOS OSS builds.

    ArrowOS Recovery :
    Note: This is a very basic aosp recovery only intended for OTA installs. Do NOT expect other functionalities.​
    * Do not use with DFE or while unencrypted.​
    F.A.Q :

    1. My WiFi, bluetooth and network aren't working after updating to OSS build?
    A. This happens if you're still on the old Q firmware. Flash the latest available R firmware and then follow the above give steps to properly flash the rom.​

    2. Unable to update OTA's using TWRP?
    A. The current available recoveries are outdated and are no longer supported for OSS builds. To have a hassle free OTA experience use the above mentioned ArrowOS recovery.
    A. Two of the currently supported recoveries are mentioned above.​

    Read our blog article/post about:
    * GAPPS and VANILLA variants
    * Checking build integrity

    ROM Source: https://github.com/ArrowOS
    Kernel Source: https://github.com/ArrowOS-Devices/android_kernel_xiaomi_surya

    XDA:DevDB Information
    ArrowOS, ROM for the Xiaomi Poco X3 NFC

    Contributors
    ganesh varma, kubersharma, palaych
    Source Code: https://github.com/ArrowOS

    ROM OS Version: Android 11
    ROM Kernel: Linux 4.x
    ROM Firmware Required: Latest R firmware
    Based On: AOSP, CAF

    Version Information
    Status:
    Stable
    Stable Release Date: 2020-11-19

    Created 2020-11-19
    Last Updated 2021-05-18
    13
    So i haven't been around here for a while, after looking at the recent posts many seem to be confused, blaming and do not understand on migrating to OSS builds. In the final MIUI vendor builds the OTA functionality was blocked in order to prevent users from directly updating to OSS builds as it will be needing a MIUI 11 firmware followed by a clean flash. The same has been notified in our device changelogs. Every step and preventive measures have been taken, there's only much i can do from my side in clearing things up. We have this forum and community in place to help each other out, so lets not be pointing fingers here!

    Here again i would like to make it clear with a simple guide on how to migrate onto OSS build!

    Note: This update will require a CLEAN FLASH (format data), so please backup everything beforehand.
    • Flash the latest available MIUI 11 firmware. (Region doesn't matter!!)
    • Now flash Arrow Vanilla/Gapps build.
    • FORMAT DATA. (You'll loose all your data!)
    • Reboot.
    Beware that the current available recoveries haven't been updated yet to support decryption for OSS builds at this point.
    11
    Here are the instructions on how you should flash the new OSS Vendor ROM since most people here are confused:

    - Flash latest TWRP by brigudav
    - Flash Android 11 12.0.7 MIUI firmware
    - Reboot recovery
    - Format Data
    - Reboot recovery
    - Flash ArrowOS

    OPTIONAL:
    - Flash Magisk
    - Flash Gapps (If you're on Vanilla build & If you want custom gapps)

    - Reboot system

    Download link:
    - Firmware: https://xiaomifirmwareupdater.com/firmware/surya/stable/V12.0.7.0.RJGEUXM/
    - TWRP: You can find it on 4pda but you need an account. I'm not allowed to share it, so you have to get it yourself.

    This firmware is for NFC model as I'm not sure where is A11 firmware for non-NFC model. It can possibly work for non-NFC model, feel free to try.
    10
    Mission Impossible in all custom ROMs !

    1. Safetynet check the bootloader status and will automatically fail if magisk is not installed (Magisk Hide ON must be applied for this) !

    2. Furthermore, now you have to install the safetynet-fix module to make your banking apps working !

    3. Finally, you must hide Magisk Manager.apk with a random name too (Magisk Settings)
    To everyone, please STOP this misconception about having the need to flash magisk in order to pass safety net. Do read the OP I've clearly mentioned there's no need of a magisk or modules for safety net. Device is certified and passes safety net out of the box without need of any modifications.

    By improper usage of magisk and mods you're further complicating and breaking things when they're completely unnecessary which end up causing unrelated issues which you end up calling them rom source bugs ¯\(◉‿◉)/¯

    P.S : I'm not against magisk, but when you do prefer using modifications do ask yourself on your needs and if you're able to rectify the issues it might generate. Isolate yourself from magisk or any form of modifications to recheck and confirm the issue before making a bug report.
    8
    Even dev says in dec the 3rd changelog that notification led was implemented, it still doesn't work for me :(
    I'm aware of the notification led issue, its interlinked to an sepolicy denial from vendor which is quite tricky to address it while we're using the prebuilt/stock vendor. For now you can assume it as a trade off for enforcing builds. I'm working on a fix, once we start a full transition towards an OSS vendor these issues will be more convenient to be addressed.