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

Search This thread

Immortal68

Senior Member
  • Feb 5, 2013
    157
    66
    Koblenz
    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:

    View attachment 5309011View attachment 5309013

    Like f4lkon said this wasn't the case for me, coming from 30.04.
    There was no difference to any other upgrade from before.

    Edit: glad to see this warning exists though. That is something I would find suitable.
     
    Last edited:

    Taranis01

    Senior Member
    May 22, 2012
    87
    23
    Xiaomi Poco X3 NFC
    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?
    I also had a bootloop before after flashing a rom (sucessfully). I was still able to transfer files via adb (fastboot mode) and you could also try transfering files using the mount feature of your recovery. Alternatively use MiFlash to flash stock MIUI and then restart the whole process again (unlocking, flashing recovery, ect).
     

    blekr

    Senior Member
  • Dec 2, 2013
    121
    41
    Xiaomi Poco X3 NFC
    no problem with proximity sensor for me on latest build. Everything works fine.
    What firmware version are you in? Download any utility to test the sensor, in my case I use the multi-tool sensors app, try several times to remove and put your hand, surely after several attempts (you have to try several times) you will simply see how your sensor gets stuck. This problem is present in a version higher than global 12.0.7 (I do not know the equivalent version in the global ROM global European). So you can solve it by simply flashing global firmware 12.0.7 on any stock or custom ROM as long as it's android 10 (There is no need to flash the full ROM, just the firmware).

    In fact there would be a thread, with the solution.
     
    Last edited:

    blekr

    Senior Member
  • Dec 2, 2013
    121
    41
    Xiaomi Poco X3 NFC
    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:

    View attachment 5309011View attachment 5309013
    I'm sure he had a version prior to the last compilation with MIUI Vendor, that's why the install button still appears, and after trying it gives him an error. (Tested by me).
     

    blekr

    Senior Member
  • Dec 2, 2013
    121
    41
    Xiaomi Poco X3 NFC
    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.


    The version "V12.0.7.0.QJGMIXM (A10 Global)" and earlier do not present this problem (I do not know its equivalence in the Europe version).

    Tried doing the thing from my answer above. Install a utility to test the sensor (in my case I use "multitool sensors.apk"). Perform several attempts, I repeat "several attempts", and you will see how it simply stays stuck your sensor). There is a thread that I opened where I explain the solution to this problem. But in short, basically flashing the global firmware "V12.0.7.0.QJGMIXM Android 10 (no need to flash full ROM, you can flash firmware only). "you solve the problem. (you can flash from any stock ROM or custom, as long as it's Android 10).

    That is why I prefer to wait for that the official version of Android 11 is released for the global version (with the problem corrected), because this problem still remains in the "Android 11 firmware Europe 12.0.7"
     
    Last edited:
    • Like
    Reactions: Master One

    Yoda007

    Senior Member
    Apr 8, 2012
    99
    9
    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/

    I prefer using USB - Buying an usb c male to usb A female and connecting a flash drive with roms, magisks, whatever. Before Poco 3 even used it to make nandroid backups on it directly.
    This I assume still works with the A11 TWRP since the USB drive isn't encrypted?
     

    Master One

    Senior Member
    Jan 31, 2011
    742
    254
    Europe
    The version "V12.0.7.0.QJGMIXM (A10 Global)" and earlier do not present this problem (I do not know its equivalence in the Europe version).

    Tried doing the thing from my answer above. Install a utility to test the sensor (in my case I use "multitool sensors.apk"). Perform several attempts, I repeat "several attempts", and you will see how it simply stays stuck your sensor). There is a thread that I opened where I explain the solution to this problem. But in short, basically flashing the global firmware "V12.0.7.0.QJGMIXM Android 10 (no need to flash full ROM, you can flash firmware only). "you solve the problem. (you can flash from any stock ROM or custom, as long as it's Android 10).

    That is why I prefer to wait for that the official version of Android 11 is released for the global version (with the problem corrected), because this problem still remains in the "Android 11 firmware Europe 12.0.7"
    OK, I have installed Sensors Multitool and the Proximity test indeed seems to get stuck occasionally, but only for a few seconds, which also could be an issue with the Sensors Multitool app?

    I have tested this several times now. I have laid down the phone and it shows Proximity: 5.0 cm.

    Moving my hand over the top part of the phone makes it toggle between Proximity: 5.0 cm and Proximity: 0.0 cm.

    I can do that many times at different speeds without problems, but sometimes it just stays at Proximity: 0.0 cm for several seconds, though it always recovers back to Proximity: 5.0 cm after some time.

    So are you sure that this is an actual problem with the firmware and that this does not occur with V12.0.7.0.QJGMIXM (A10 Global) and earlier?
     

    Yoda007

    Senior Member
    Apr 8, 2012
    99
    9
    I still have the problem with the default Phone app, anyone else ? If someone calls while the phone display is off the display turns on but there is just black screen and the pull down status bar. No caller, nothing, I have to drop down the status bar, click on the call notification, enter my pattern and then answer on the notification from the expanded status bar.

    Though there is a workaround i have been using for months since this is happenin -> Installed a SImple dialer app and set it as default.

    Using vanilla. Reported the bug on the bug tracker but it was closed saying i should clear the phone app data&cache, which i tried before and does not help at all.
     

    SkaboXD

    Senior Member
    Jan 18, 2017
    1,039
    359
    Ganja
    Xiaomi Poco X3 NFC
    OK, I have installed Sensors Multitool and the Proximity test indeed seems to get stuck occasionally, but only for a few seconds, which also could be an issue with the Sensors Multitool app?

    I have tested this several times now. I have laid down the phone and it shows Proximity: 5.0 cm.

    Moving my hand over the top part of the phone makes it toggle between Proximity: 5.0 cm and Proximity: 0.0 cm.

    I can do that many times at different speeds without problems, but sometimes it just stays at Proximity: 0.0 cm for several seconds, though it always recovers back to Proximity: 5.0 cm after some time.

    So are you sure that this is an actual problem with the firmware and that this does not occur with V12.0.7.0.QJGMIXM (A10 Global) and earlier?
    I'm on Android 11 12.0.7 firmware and I tested proximity sensor with Device Info HW app. It works flawlessly. Proximity sensor activates almost instantly. I also did call that lasted around 2 minutes constantly activating and deactivating proximity sensor and it worked as expected.
     

    Master One

    Senior Member
    Jan 31, 2011
    742
    254
    Europe
    I'm on Android 11 12.0.7 firmware and I tested proximity sensor with Device Info HW app. It works flawlessly. Proximity sensor activates almost instantly. I also did call that lasted around 2 minutes constantly activating and deactivating proximity sensor and it worked as expected.
    Yeah, but as mentioned by @blekr it's supposed to be working with V12.0.7.0.QJGMIXM (A10 Global) and earlier anyway, but I'm on V12.0.8.0.QJGEUXM (A10 Europe) with ArrowOS 11 VANILLA 20210503.
     

    blekr

    Senior Member
  • Dec 2, 2013
    121
    41
    Xiaomi Poco X3 NFC
    Sí, pero como lo mencionó [USER = 5584789] @blekr [/ USER], se supone que funciona con V12.0.7.0.QJGMIXM (A10 Global) y antes de todos modos, pero estoy en V12.0.8.0.QJGEUXM (A10 Europa) con ArrowOS 11 VANILLA 20210503.

    De acuerdo, he instalado Sensors Multitool y la prueba de proximidad parece atascarse ocasionalmente, pero solo durante unos segundos, lo que también podría ser un problema con la aplicación Sensors Multitool.

    He probado esto varias veces. He dejado el teléfono y muestra Proximidad: 5,0 cm .

    Mover mi mano sobre la parte superior del teléfono hace que cambie entre Proximidad: 5.0 cm y Proximidad: 0.0 cm .

    Puedo hacer eso muchas veces a diferentes velocidades sin problemas, pero a veces simplemente se mantiene en Proximidad: 0.0 cm durante varios segundos, aunque siempre se recupera a Proximidad: 5.0 cm después de un tiempo.

    Entonces, ¿está seguro de que se trata de un problema real con el firmware y que esto no ocurre con V12.0.7.0.QJGMIXM (A10 Global) y versiones anteriores?
    Es This problem is not from the application. You can replicate it with the calling app. That is why it remained at 12.0.7 globally. Why is it very annoying for me.
     
    • Like
    Reactions: Master One

    blekr

    Senior Member
  • Dec 2, 2013
    121
    41
    Xiaomi Poco X3 NFC
    OK, I have installed Sensors Multitool and the Proximity test indeed seems to get stuck occasionally, but only for a few seconds, which also could be an issue with the Sensors Multitool app?

    I have tested this several times now. I have laid down the phone and it shows Proximity: 5.0 cm.

    Moving my hand over the top part of the phone makes it toggle between Proximity: 5.0 cm and Proximity: 0.0 cm.

    I can do that many times at different speeds without problems, but sometimes it just stays at Proximity: 0.0 cm for several seconds, though it always recovers back to Proximity: 5.0 cm after some time.

    So are you sure that this is an actual problem with the firmware and that this does not occur with V12.0.7.0.QJGMIXM (A10 Global) and earlier?
    Now run the same test on global firmware 12.0.7 and you will notice the difference.

    This problem is present in any application that makes use of the proximity sensor, so the problem is in the firmware. If you like you can replicate it with another app.

    For me it is very annoying in calls for example. That is why I still stay at global firmware 12.0.7
     
    Last edited:
    • Like
    Reactions: Master One

    Master One

    Senior Member
    Jan 31, 2011
    742
    254
    Europe
    This problem is present in any application that makes use of the proximity sensor, so the problem is in the firmware. For me it is very annoying in calls for example. That is why I still stay at global firmware 12.0.7
    So can anyone check and confirm, if this issue is still there with V12.0.7.0.RJGEUXM (A11 Europe)?
     

    Master One

    Senior Member
    Jan 31, 2011
    742
    254
    Europe
    I think blekr is right about proximity sensor issue. There are many complaints about that and xiaomi knows and accept the issue as i know.

    Btw 12.0.9 is out. It might be solved in that release
    Well, anyone dares to test V12.0.9.0.QJGMIXM (A10 Global) concerning the proximity sensor issue?
     

    Top Liked Posts

    • 1
      I am on the most latest update i think and still i get that error
      use european version, i used that.
    • 8
      I have tried Migrate since my phone was rooted but had issues restoring the backup. The phone got into a bootloop, so I have been forced to set everything back up from scratch again
      Not good! I haven't tried Migrate yet, it was just presented to me as an option for the task at hands, so either someone comes up with a success story, or I will have to just try all three backup methods and find out for myself if any of these is going to work.

      Just now, I installed TWRP 3.5.2_10-2 (Brigudav) on my Poco X3 NFC ... then I flashed "Disable_DM-Verity_ForceEncrypt" ... and I have no issues with the TWRP reading files unencrypted.
      Why would TWRP (any version, same as any version of OrangeFox) have any issues if you have an unencypted device???

      This whole story is about decrypting the device from recovery if your device is encrypted.

      And yes, it is a very bad idea and NOT recommended at all to use an unencrypted device, because as said before, if you lose your phone and you have any sensitive or personal data on it, you are done!

      If you have unencrypted your device because someone told you that this is the solution for the current problems with device decryption on A11 + OSS vendor, you have been given extremely bad advice!
      6
      Guys, all what's been written in the recent couple of pages is totally excessive, why not just wait for an update of OrangeFox / TWRP that can deal with the device decryption on A11 + OSS vendor, before upgrading from A11 + MIUI vendor?

      ArrowOS 11 VANILLA 20210503 is working fine here and I have absolutely no interest and time for any hassle, as has been shown in the numerous posts from the last two weeks.
      5
      Hello everyone,

      I saw that brigudav updated his TWRP version to 3.5.2_10-2.
      https://androidfilehost.com/?fid=14943124697586337627
      Did anyone try it yet? Does decryption with OSS builds work? (I don't have the time to experiment with the new OSS builds atm)
      After testing, I can affirm that TWRP 3.5.2_10-2 by brigudav cannot decrypt the data encrypted with Android 11 + OSS vendor.
      4
      Can you tell more about it?

      Can it decrypt the the data partition with A11+OSS vendor?

      Is this what the Changelog entries from 2021-05-13 concerning android_bootable_recovery were all about?
      Like i said the Arrow recovery is only intended for OTA updates with no extra features. You won't be able to access internal data as its posed as a security risk.
      I just installed this ROM, but my wifi does not work. Any suggestions?
      I have answered and added a few FAQ's to the original post. Those who are still having difficulties switching to OSS builds have to check them out.

      As for the NFC issues they have addressed in the latest builds.
      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
    • 50
      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. (Region doesn't matter!!)
      • 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.