• 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

bagus101

Member
Aug 10, 2017
5
2
When I tried to shutdown or reboot the phone after a day long use, the device freeze and I need to hold power button until it restarts. Is there a way to fix this behavior? Currently on latest GAPPS build, TWRP, and 12.5.1 FW. Also no root.
 
  • Like
Reactions: Porcupine1

Porcupine1

Senior Member
Dec 14, 2017
157
44
When I tried to shutdown or reboot the phone after a day long use, the device freeze and I need to hold power button until it restarts. Is there a way to fix this behavior? Currently on latest GAPPS build, TWRP, and 12.5.1 FW. Also no root.
I had the same problem on Crdroid and here on Arrow this bug still exsist in my case too. but maybe soon will be some fix for that.
 
  • Like
Reactions: bagus101

khantastic

Senior Member
Jan 12, 2011
782
341
Xiaomi Poco X3 NFC
Xiaomi Poco F3
yesterday i tried to flash this rom, coming from 12.5.1 global miui. I was not able to boot the gapps variant of the rom, however i was able to boot vanilla variant, here are the steps i followed, can someone help me identify the issue why gapps variant did not boot or was i too quick to assume its stuck?
attempt 1:
1. unlocked BL.
2. fastboot>flash twrp>boot to twrp.
3. wipe cache, dalvik, data
4. flash using add more zip option in twrp: miui firmware (less than 100mb file)+vanilla rom+flame_gapps
5. wipe data>yes>reboot> the first boot successful in a minute.
attempt 2:
1. boot to twrp.
2. wipe cache, dalvik, data
3. flash using add more zip option in twrp: miui firmware (less than 100mb file)+gapps rom
4. wipe data>yes>reboot> first boot 'stuck' at arrowos logo for around 15 mins.
attempt 3:
then i attempted again, to make sure i did not forget to do format data, so flashed again, format data>yes... again for 10 minutes 'stuck' at arrowos boot logo.
attempt 4:
then i went back to recovery and flashed firmware+vanilla+gapps>format data>yes>reboot>boot within a minute.

Does the gapps variant take this much time to first boot as compared to vanilla? or did i miss something?
 

MarkRobert

Member
Nov 22, 2011
45
8
I'm trying to figure out whether I've a hardware issue, software issue, or a poltergeist! On occasion, the phone will start to behave as if I was switching screens and touching things on the screen. Ghost touches I suppose. Once, it managed to send 5 messesger messages to my local pizza place. Thank goodness they were just nonsense pictures. :-D

I've dropped this phone a million times, but no cracks or damage.
 

camperbh

Senior Member
Feb 22, 2021
96
30
I'm trying to figure out whether I've a hardware issue, software issue, or a poltergeist! On occasion, the phone will start to behave as if I was switching screens and touching things on the screen. Ghost touches I suppose. Once, it managed to send 5 messesger messages to my local pizza place. Thank goodness they were just nonsense pictures. :-D

I've dropped this phone a million times, but no cracks or damage.
Well if you've dropped it a million times, the digitizer could have been damaged even though there is no visible damage. I suggest getting it looked at.
 
  • Like
Reactions: MarkRobert

Chevan94

Senior Member
Aug 30, 2011
227
37
Kraków
yesterday i tried to flash this rom, coming from 12.5.1 global miui. I was not able to boot the gapps variant of the rom, however i was able to boot vanilla variant, here are the steps i followed, can someone help me identify the issue why gapps variant did not boot or was i too quick to assume its stuck?
attempt 1:
1. unlocked BL.
2. fastboot>flash twrp>boot to twrp.
3. wipe cache, dalvik, data
4. flash using add more zip option in twrp: miui firmware (less than 100mb file)+vanilla rom+flame_gapps
5. wipe data>yes>reboot> the first boot successful in a minute.
attempt 2:
1. boot to twrp.
2. wipe cache, dalvik, data
3. flash using add more zip option in twrp: miui firmware (less than 100mb file)+gapps rom
4. wipe data>yes>reboot> first boot 'stuck' at arrowos logo for around 15 mins.
attempt 3:
then i attempted again, to make sure i did not forget to do format data, so flashed again, format data>yes... again for 10 minutes 'stuck' at arrowos boot logo.
attempt 4:
then i went back to recovery and flashed firmware+vanilla+gapps>format data>yes>reboot>boot within a minute.

Does the gapps variant take this much time to first boot as compared to vanilla? or did i miss something?
Correct me if I'm wrong, but:

Aren't you supposed to "Format data" (where your type in "yes" to format)? This wipes your internal storage too.
The GApps variant has them already baked in, no need to flash other packages

Also, AFAIK you don't need to flash the firmware package if you were already on 12.5.1 ROM.
 

khantastic

Senior Member
Jan 12, 2011
782
341
Xiaomi Poco X3 NFC
Xiaomi Poco F3
Correct me if I'm wrong, but:

Aren't you supposed to "Format data" (where your type in "yes" to format)? This wipes your internal storage too.
The GApps variant has them already baked in, no need to flash other packages

Also, AFAIK you don't need to flash the firmware package if you were already on 12.5.1 ROM.
for the first time yes i did not have to flash the firmware but did it just in case.

also, i flashed gapps only when i flashed vanilla rom. i have not been able to boot the one with builtin gapps, i did not flash gapps separately with it.

for format data with yes optiom: i read it in one of the guides, but even then, it wipes storage i am ok with storage wipe. why the rom did not boot though? how much time does the gapps variant takes to first boot?
 

Chevan94

Senior Member
Aug 30, 2011
227
37
Kraków
for the first time yes i did not have to flash the firmware but did it just in case.

also, i flashed gapps only when i flashed vanilla rom. i have not been able to boot the one with builtin gapps, i did not flash gapps separately with it.

for format data with yes optiom: i read it in one of the guides, but even then, it wipes storage i am ok with storage wipe. why the rom did not boot though? how much time does the gapps variant takes to first boot?
Try redownloading the ROM and check MD5, the download might've been corrupted.

I've yet to unlock the bootloader and install this ROM but from the looks of it something's wrong with the GApps portion of your download as the vanilla one boots fine
 

khantastic

Senior Member
Jan 12, 2011
782
341
Xiaomi Poco X3 NFC
Xiaomi Poco F3
Try redownloading the ROM and check MD5, the download might've been corrupted.

I've yet to unlock the bootloader and install this ROM but from the looks of it something's wrong with the GApps portion of your download as the vanilla one boots fine
i thought the same, i will redownload just in case, but have already verified the hash of the zip file and it matched the one available online.

and since vanilla booted fine, this is why i am confused if i am missing something or what.
 

gorillaz_gr

Senior Member
I just updated from a 2020 android 10 version to the latest version... I followed instructions in first Post and it all worked out...
Now I have Bluetooth issues and my hd (acc) headset won't play and when using it for calls I cannot hear anything...
Plus, this morning my alarm did not go off as the phone crashed and I had to do a hard reset reboot...
Any idea what I can do now?
about Bluetooth: try to go to developer settings and enable the setting (in English): disable absolute volume

about alarm clock: it seems that after an update from Google, there are a few problems with google clock, many people around the world , never woke up to go for work!!! I don't use it , so I can not be sure, I always use another clock from PlayStore.
 
  • Like
Reactions: wurst_wasser

Top Liked Posts

  • There are no posts matching your filters.
  • 16
    Hello.

    Does anyone have any working TWRP for Surya model ?

    I see that the developer Brigudav seems to have given up on developing TWRP for Surya.

    TWRP by Brigudav Official website

    So is there any replacement ?

    Thank you very much.
    Update -09
    5
    For anyone who had the GApps Updater bug on the 03/10 build & has been following along with the diagnosis process: the newly-released 08/10 build seems to have updated properly, overwriting the dodgy config file for the GApps channel on the update server.

    So hopefully, you'll now find the Updater app can successfully download the 08/10 GApps build.

    If there are no errors flagged up in the next day or so I'll probably go ahead & tag the Gitlab ticket for closure.
    5
    a crappy rom camera is so bad I do not recommend
    i dont think people use the stock cam of custom roms lol. You can disregard this rom if you dont like it. Anyway, there are gcam and anx cam and others to enjoy cam in custom roms. Maybe you did not try to explore, and now you are spreading bad vibes to users. Remember the devs created this rom for us to use FOR FREE and nobody is telling you to use this forcefully lol
    5

    FROM THE MODERATOR: Posts like this only drives more developers away. Instead of whining or griping about what you would like to see ....Try making your own ROM, then maintain it and answer every question someone who does not understand what it takes to make a ROM. In other words, show us your skills other than running your mouth and complaining. Remember, Everyone in XDA is here doing what they do for free.




    Legion 3.8,,, the only rom I've been back to for 4 months, no one can make a rom, I'm watching the developers with amazement fxy.011 kernel is successful, every time you play it starts great. Will corvus and miui swell in 15 days, there is no rom to install, wouldn't it be nice if the developers gathered under the same roof? ? ? ? Ok, when I install it, a light rom comes out, but the phone turns itself off, this problem is not solved. I get very good performance especially without using pubg modules. The groups that make modules are total bullshit, they eat the device's brain, please stop making roms every day, something is done, the other is broken, I loaded 80 roms, I'm fed up, legion developer you really know this but you quit. also poco x3 nfc
    3
    When can we expect android 12? I know it's close, really can't wait
    Usual question so usual answer : when it's ready...

    The source code (at least in AOSP) is available since only a few days (and I'm not sure everything is available).

    I know most people, as you (and me !), wants to get the most recent stuff but please be patient ;)
    Let the devs do their magic and, please, never ask for an ETA : they will publish when i's ready :D
  • 75
    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
    16
    Hello.

    Does anyone have any working TWRP for Surya model ?

    I see that the developer Brigudav seems to have given up on developing TWRP for Surya.

    TWRP by Brigudav Official website

    So is there any replacement ?

    Thank you very much.
    Update -09
    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.