• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

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

Search This thread

ganesh varma

Senior Member
is the safetynet keystore patch already included ???
They have been merged recently, but regardless of that i had the changes incorporated into the device tree since beginning to make sure of passing safety net, so there's never a time it failed since release.
 

ganesh varma

Senior Member
Please, can you explain how use NFC to pay?
I've tried the ROM (with and without install Magisk). In both cases GPay installs fine, then no issues to add bank cards but when I try to pay in a store, the dataphone refuses to operate. No issues with MIUI.
Thanks
I have the non-nfc variant so its impossible for me to test this. Capture and provide with logs while doing the payment or where it refuses via NFC.
 

laserpc01

New member
Dec 6, 2015
4
0
Google Pay It works on Arrow, as it does on any custon rom
Screenshot_20210122-162848.pngScreenshot_20210122-162825.pngScreenshot_20210122-162819.png
 

iakoboss7

Senior Member
Last edited:

jeryll

Senior Member
Dec 23, 2010
859
684
Xiaomi Poco X3 NFC
Redmi Note 10 Pro
  • Like
Reactions: iakoboss7

ralfhein

Member
May 14, 2019
14
11
I would need to increase the volume_steps set in /system/default.prop file (at least this is how it worked for me on other phones) so I can use the phone with a decent headset for music. The 15 default steps of android are just not enough imho.

Is there a way to mount /system as r/w in OrangeFox or TWRP or whatever to be able to edit this file via adb?
I could obviously also do a build myself to fix this, but that really does seem overkill.

Or does anyone have another suggestion how to fix the volume steps? Thanks!
 

jeryll

Senior Member
Dec 23, 2010
859
684
Xiaomi Poco X3 NFC
Redmi Note 10 Pro
I would need to increase the volume_steps set in /system/default.prop file (at least this is how it worked for me on other phones) so I can use the phone with a decent headset for music. The 15 default steps of android are just not enough imho.

Is there a way to mount /system as r/w in OrangeFox or TWRP or whatever to be able to edit this file via adb?
I could obviously also do a build myself to fix this, but that really does seem overkill.

Or does anyone have another suggestion how to fix the volume steps? Thanks!
not a clue about the rest, but you can mount /system in OrangeFox...
 
  • Like
Reactions: ralfhein

ralfhein

Member
May 14, 2019
14
11

bartito

Inactive Recognized Developer
Dec 1, 2005
3,931
1,783
I have the non-nfc variant so its impossible for me to test this. Capture and provide with logs while doing the payment or where it refuses via NFC.

Thanks for the quick reply.
I have changed my device and I need to wait until February to unlock the new one due to the Xiaomi stupid policy to allow only one unlock per month, but I will post the logs when I have it done.
 

miuirred

Member
Jan 7, 2017
24
8
I would need to increase the volume_steps set in /system/default.prop file (at least this is how it worked for me on other phones) so I can use the phone with a decent headset for music. The 15 default steps of android are just not enough imho.

Is there a way to mount /system as r/w in OrangeFox or TWRP or whatever to be able to edit this file via adb?
I could obviously also do a build myself to fix this, but that really does seem overkill.

Or does anyone have another suggestion how to fix the volume steps? Thanks!
I added "ro.config.media_vol_steps=20" in build.prop via https://forum.xda-developers.com/t/...released-fully-featured-file-manager.1523691/ - works fine in my rooted X3. Has to be repeated after update of course.
 
  • Like
Reactions: ralfhein

Top Liked Posts

  • 1
    i just flashed arrow os on miui 12.5 and the phone is stuck on the arrow os logo, help plz
    does the bootloader unlocked?

    wouldn't sure 12.5 worked since I'm from 12.0.1. If bootloader unlocked try reflash firmware via Mi Flash tool (need to download fastboot firmware).

    Then if same problem try downgrade, 12.0.1 proven to work since I successfully flash on it. (Edit : 12.5.0.1 a guy successfully flashed it.)

    This are only way I could think of to suggest. May god help you.

    make sure TWRP 3.5.2_10-5 and format data after flashing ArrowOS.
    1
    i just flashed arrow os on miui 12.5 and the phone is stuck on the arrow os logo, help plz
    You probably made a mistake flashing the ROM.

    Enter recovery, flash ArrowOS, format DATA (it's where you have to type "yes"), restart.

    Only format DATA after flashing the ROM. No other wipes are necessary before or after flashing the ROM.
    1
    does the bootloader unlocked?

    wouldn't sure 12.5 worked since I'm from 12.0.1. If bootloader unlocked try reflash firmware via Mi Flash tool (need to download fastboot firmware).

    Then if same problem try downgrade, 12.0.1 proven to work since I successfully flash on it. (Edit : 12.5.0.1 a guy successfully flashed it.)

    This are only way I could think of to suggest. May god help you.

    make sure TWRP 3.5.2_10-5 and format data after flashing ArrowOS.
    yeah it did i just didnt properly format data, thanks for the help
  • 8
    FYI

    ArrowOS for Poco X3 it's not dead!

    3
    Yes, the update is up and downloadable on arrowos site but not yet available through OTA.
    edit: OTA is now available
    edit 2: Update flashed through ota without any issue. Arrow is back in the game. Kudos to the devs!
    3
    Hello so I recently flashed Arrowos only to realize that my previous MIUI 12.0.7 ROM was not in fact on the latest Android 11 firmware. Now I am stuck without Wifi and honestly am a bit lost. Asking for a friend here, what should my next steps be? Thanks in advance :')
    Flash latest 12.5.1.0 firmware, reboot to recovery, flash latest ArrowOS, format data, wipe cache & dalvik cache, reboot to system.

    Firmware: https://chuangtzu.ftp.acc.umu.se/mi...AGlobal_V12.5.1.0.RJGMIXM_e3b8205e7f_11.0.zip
  • 65
    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
    14
    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.
    13
    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.