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

Search This thread

evolez

Senior Member
May 29, 2013
208
47
Is it possible to install the kernel without losing all the info in the phone? Or I will have to reinstall the rom?
No need to format. Just flash it via recovery and wipe cache, dalvik.

Kernels version has to be 11.24 or older. Newer ones don't work. You gonna stuck at fastboot
 
Last edited:

Master One

Senior Member
Jan 31, 2011
742
254
Europe
That's actually firmware, not vendor, and yes, it should be enough to simply flash the firmware package, BUT:

Is it possible that flashing the full MIUI ROM changes the (super-)partition layout?

I have six POCO X3 NFC here, all setup identically, and one shows a different partition list when Magisk is restored by the backup script after an upgrade of ArrowOS, which must have something to do with the fact, that the other five phones came from the latest MIUI, but the sixth phone I already had with ArrowOS and I only updated the firmware package before.

So to make it a clean flash, just to be sure, I would flash the whole MIUI package, then custom recovery again, then ArrowOS followed by formating the data partition.

My main problem now is, that I still don't know how to make a full backup of everything (including settings) so that I can restore the phone to the exact same state as it is now, because I put a lot of time into setting up those six phones.

I'm not using Titanium Backup, but OAndBackupX instead. Backing up and restoring the data partition in recovery doesn't make sense, because that would just equal a dirty flash.

Is it enough to backup user apps and their data, the data of system apps and a manual backup of /sdcard (= /storage/emulated/0)?

I really need help with this before I start messing up already perfectly configured phones.
 

shootomanUK

Senior Member
Jun 6, 2010
109
39
Just tried ota update (may 10th)...and it gives an error.
I think it says something about needing latest firmware from miui ?

Anyone now which is latest and also is can we just flash it via recovery ?

a link to fw would be nice :)

Thanks
 

ruchimes

Member
Jul 27, 2016
38
4
Just tried ota update (may 10th)...and it gives an error.
I think it says something about needing latest firmware from miui ?

Anyone now which is latest and also is can we just flash it via recovery ?

a link to fw would be nice :)

Thanks

Few messages before yours you have this:
Flash 12.0.7 Eu Vendor
Arrow
Reboot to recovery
DFE
Format data
Reboot system

(Use DFE only if you want to stay decript)

I just installed it like this and the rom looks amazing

What are the changes in this OSS version?
 

camperbh

Senior Member
Feb 22, 2021
64
21
I already have an OSS vendor rom installed. Can I just format data and flash the new version?
Edit: I formatted data and flashed this and flame gapps but its stuck at the arrow logo.
 
Last edited:

Vulnerability

Senior Member
Sep 14, 2017
61
29
Do we have to use EU vendor
forget that.......
Personally I'm going to wait for Official A11 to be released, once done I'll flash the full Official A11 ROM, then upgrade to the new ArrowOS OSS Vendor build.

Currently I'm on the MIUI Vendor Arrow build & it works fine, no urgency to upgrade.
 

Rene040

Member
Jun 30, 2016
9
1
Personally I'm going to wait for Official A11 to be released, once done I'll flash the full Official A11 ROM, then upgrade to the new ArrowOS OSS Vendor build.

Currently I'm on the MIUI Vendor Arrow build & it works fine, no urgency to upgrade.
What advantage does that give? I'm quite new to custom roms so don't know.
 

Zleilndka5

Member
Feb 19, 2021
47
14
Hello !

I feel like installing the new firmware doesn't work for me and messes up the "/ sdcard" file (I don't have an sd card, it's not: "/ scdard1") .

I also have the mention: "E: Error making / sdcard / Fox directory: Required key not available"

Here is what I get. An idea of the problem ?

I installed once, then totally reinstalled MIUI with MIUI Flash Tool, then clean install, but I still have this ...

Thank you in advance !!!

IMG_20210510_130337_3.jpg
 

schillio

Member
May 10, 2021
13
6
Hello !

I feel like installing the new firmware doesn't work for me and messes up the "/ sdcard" file (I don't have an sd card, it's not: "/ scdard1") .

I also have the mention: "E: Error making / sdcard / Fox directory: Required key not available"

Here is what I get. An idea of the problem ?

I installed once, then totally reinstalled MIUI with MIUI Flash Tool, then clean install, but I still have this ...

Thank you in advance !!!

View attachment 5305135That's because current recoveries does not support decryption on oss vendor, only way around it for now is to use DFE or flash it through sd card
 

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
  • 51
    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.