• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

InContext

Member
Aug 2, 2017
44
11
Total heresay, saw on one of the Xiaomi forums, someone saying that the global update won't happen until October.

I still can't believe the developers deleted the pre-OSS versions before we even have the firmware to be able to upgrade.

Thank god for users like Taranis01 who had the mind to download the last one. Lost everything from the 11th onwards (had to reformat the data partition) but at least I have a working phone again.
 
Last edited:

ganesh varma

Senior Member
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.
 

blekr

Senior Member
Dec 2, 2013
121
41
Xiaomi Poco X3 NFC
@ganesh varma I appreciate the effort they make to keep this great ROM up to date.

Personally I decided to stay for a while on the latest build with MIUI Vendor, because all firmwares (except 12.0.7 android 10 global version and earlier) have problems with the proximity sensor. The build of "20210503" it's rock solid, and it's excellent for use it as a daily driver.

I will wait for android 11 to be officially released for the global version, waiting for the problem with the proximity sensor to be corrected I am sure that many have this problem and have not realized it. But if anyone looking for a solution, just flash global firmware 12.0.7.
 
Last edited:

prorecheto

New member
Apr 30, 2021
4
1
Hi guys, after installing the newest update, it didn't go through. Now my phone is stuck in a boot loop and I don't have USB debugging enabled. When trying to format the data and reinstall the ROM I received the following error: Failed to mount '/product' (invalid argument).

Is my phone bricked?? Please help!

Edit: How can I transfer files if I don't have USB debugging enabled?
 

SkaboXD

Senior Member
Jan 18, 2017
1,068
390
Ganja
Xiaomi Poco X3 NFC
@ganesh varma I appreciate the effort they make to keep this great ROM up to date.

Personally I decided to stay for a while on the latest build with MIUI Vendor, because all firmwares (except 12.0.7 android 10 global version and earlier) have problems with the proximity sensor. The build of "20210503" it's rock solid, and it's excellent for use it as a daily driver.

I will wait for android 11 to be officially released for the global version, waiting for the problem with the proximity sensor to be corrected I am sure that many have this problem and have not realized it. But if anyone looking for a solution, just flash global firmware 12.0.7.
no problem with proximity sensor for me on latest build. Everything works fine.
 

Waki_Miko

Member
Jan 10, 2021
8
1
Where can I find these "device changelogs"? I didn't see anything about the OSS update in the changelogs the OTA updater opens when I upgraded from 2021-04-30 to 2021-05-10.

Since I don't install every nightly, my OTA updates weren't blocked at all. Would it be possible for the installer itself to perform the firmware checks and throw an error? That would certainly prevent some headaches.
 

Master One

Senior Member
Jan 31, 2011
751
262
Europe
... because all firmwares (except 12.0.7 android 10 global version and earlier) have problems with the proximity sensor .. but if anyone looking for a solution, just flash global firmware 12.0.7.
Can you please be more specific?

What are these problems with the proximity sensor?

Is there any difference concerning this issue between
  • V12.0.7.0.QJGMIXM (A10 Global)
  • V12.0.7.0.QJGEUXM (A10 Europe)
  • V12.0.8.0.QJGMIXM (A10 Global)
  • V12.0.8.0.QJGEUXM (A10 Europe)
?

I'm currently on V12.0.8.0.QJGEUXM (A10 Europe) with ArrowOS 11 VANILLA 20210503, but I could not tell anything about problems with the proximity sensor.

Where can I find these "device changelogs"?
 
  • Like
Reactions: Waki_Miko

Master One

Senior Member
Jan 31, 2011
751
262
Europe
@ganesh varma, does ArrowOS now come with its own recovery?

From the Source changelog on 2021-05-13:

android_bootable_recovery: recovery: Allow custom bootloader msg offset in block misc
android_bootable_recovery: recovery: use ensure_volume_unmounted in format_volume
android_bootable_recovery: bootable: Read all asserts in case there are more than one
android_bootable_recovery: recovery_ui: Tell the user they're actually formatting
android_bootable_recovery: recovery: Remove the "Format system partition" menu on A/B devices
android_bootable_recovery: recovery: Map logical partitions before installation
android_bootable_recovery: recovery: Draw header lines with less padding
android_bootable_recovery: recovery: Always use the text menu for rescue party
android_bootable_recovery: recovery: allow A/B updater to downgrade
android_bootable_recovery: minui: Allow skipping EV_REL input devices.
android_bootable_recovery: Return the correct action for PromptAndWait
android_bootable_recovery: recovery: Allow going back in rescue party menu
android_bootable_recovery: recovery: Support writing to Virtual A/B partitions
android_bootable_recovery: recovery: Add ability to unmount system
android_bootable_recovery: Add controller support
android_bootable_recovery: roots: Correct mount flags in /etc/fstab
android_build: Remove unused locale data for recovery
android_vendor_arrow: soong: Export bootloader_message_offset to dependencies
android_build_soong: soong: Add equivalent for LOCAL_EXPORT_CFLAGS
android_bootable_recovery: recovery: Set the INFO color to white
android_bootable_recovery: recovery: Clarify help text
android_bootable_recovery: recovery: Draw the help message below the menu on non-touch devices
android_bootable_recovery: recovery: Display recovery version
android_bootable_recovery: recovery: Print the active slot
 

nurojggwp

Member
May 14, 2021
7
0
I've been using arrow OS for a while, but recently I seemed to have reached a point where I cant get new installs on my phone. Whenever I download the install, it shows install. But after trying to install, it just fails
 

f4lkon

Senior Member
Dec 11, 2010
94
22
Just tested todays 20210514 build. Autoupdate did not work. On first try it hangs at 100% restarting. On second try it reboots into recovery and thats it. I had to flash it manually. To do so I had to format data (lost all data) again because decryption does not work with current recoveries. Currently I would just recommend everyone to stay on 2021.05.03 and wait till we get recoveries which work with decryption.
 

joakovlsc

Member
Mar 14, 2017
10
8
Just tested todays 20210514 build. Autoupdate did not work. On first try it hangs at 100% restarting. On second try it reboots into recovery and thats it. I had to flash it manually. To do so I had to format data (lost all data) again because decryption does not work with current recoveries. Currently I would just recommend everyone to stay on 2021.05.03 and wait till we get recoveries which work with decryption.

For future references, there's no need to format data - Until we get a working recovery you can always enter yours and push the latest arrow os zip through adb and then flash it normally (even if the data is encrypted), no need to lose data on every update.

Here's how: https://www.androidauthority.com/android-customization-transfer-files-adb-push-adb-pull-601015/
 

Immortal68

Senior Member
Feb 5, 2013
172
73
Koblenz
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.
I feel like the problem is that downloading the ROM-breaking update through the official updater only opens https://arrowos.net/changelog.php, which looks like this:

Screenshot_20210514-154347.png



There's nothing in there giving me any kind of warning. The actual warning is found in our device specific changelog (which I'm guessing is the only one you can edit?). See here:

Screenshot_20210514-154608.png


Which is still far too little, too calm, imo. There should be a big fat red warning in the changelog that opens when you download the 12.05. update like:

⚠ !!! WARNING !!! ⚠
UPDATE 12.05. WILL BOOTLOOP YOUR ROM IF YOU DON'T FOLLOW INSTRUCTIONS CAREFULLY! YOU WILL LOSE YOUR DATA!
 
Last edited:
  • Like
Reactions: pnin

Master One

Senior Member
Jan 31, 2011
751
262
Europe
I feel like the problem is that downloading the ROM-breaking update through the official updater only opens https://arrowos.net/changelog.php... There's nothing in there giving me any kind of warning. The actual warning is found in our device specific changelog... Which is still far too little, too calm, imo. There should be a big fat red warning in the changelog that opens when you download the 12.05. update like: ⚠ !!! WARNING !!! ⚠ THIS WILL BOOTLOOP YOUR ROM IF YOU DON'T FOLLOW INSTRUCTIONS CAREFULLY! YOU WILL LOSE YOUR DATA!
I don't understand how someone can actually get into troubles with this, as OTA updates have been blocked after the 20210503 nightly, which means you can not update through the updater and it gives a proper explanation and warning:

updater_1.jpgupdater_2.jpg
 

Master One

Senior Member
Jan 31, 2011
751
262
Europe
@Master One I think you will still need an external sd card to push. This can be done via adb or just mounting it via recovery and move via filesystem without adb.
That's what I thought, no messing around with adb, but simply use an OTG USB device (which is very handy, I have a 256GB USB stick with an USB-A connector at one end and an USB-C connector at the other end) containing the file.
 

Top Liked Posts

  • 1
    There are a lot of notes regarding a safetynet fix. AM I correct that the lates version of the rom passes safetynet and doesn't require a fix?
    Yes, just root your phone, activate MagiskHide and you should be good.
  • 5
    payment by NFC does not work. I'm on 08/29 build
    I got the same message today, even though I'm using 20210601 build.

    SafetyNet also started failing this morning.

    Edit: The fix is rather easy. Flash this Magisk module:


    You need the safetynet-fix-v1.2.0-MOD
    5

    bagus101

    Hello.

    I have a similar problem that I reported yesterday on GitLab.

    https://gitlab.com/arrowos-support/issues/android/-/issues/241

    So can you comment on my GitLab post as well ?

    Maybe the developers will notice it sooner :)

    Thanks.
    4
    Please don't address another ROM in this thread.

    This thread is for the Arrow OS ROM.

    Thank you.
    And we're talking how Arrow compares to other ROMs.

    Please mind your business.

    Thank you.
    3
    Just FYI, SafetyNet is ok again on latest (2021-09-08) build
    3
    My list of modules is rather small:
    - ANX camera
    - Systemless hosts
    - Universal SafetyNet fix (linked above)

    I also use Magisk Hide and have hid Magisk. It's somewhere in the settings. The Magisk APK then gets a different name and different icon
    Alright, I think I got it working. I had Magisk Hide for Google apps and banking already activated. I hadn't hidden the manager yet though.

    Guide for anyone experiencing the same problem. What I did was:

    1. Make sure MagiskHide was active for everything Google and banking app
    2. Hide Magisk Manager App through the option (I renamed it to "Admin")
    3. Clear any storage of Google Pay, Google Play Store and Google Play Services through Settings > Apps & notifications
    4. Install SafetyNet-Fix-Mod.zip from storage in Magisk Manager
    5. Restart the device
    6. Open Play Store
    7. Open Google Pay and set up contactless payment

    Some of the steps might be redundant, but the old error doesn't show up and in theory it should work. Will have to see if actual payments work.

    Anyways, thanks for the guideline in the right direction, @Noter2017 !

    Edit: Payment works!
  • 71
    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.