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

Search This thread

gessler2244

Member
Nov 5, 2016
23
6
I just want to pick up this issue one more time.
I searched the web a little, and there is at least one patch solution (haven't tried that until now).

But as far as I got it, LineageOS implemented the "recording per country" option first time in LOS 15.
I'm pretty sure that I had an official LOS 16.0 on my BQ Aquaris X Pro before its display died (R.I.P. :cry:), and that I found a Magisk module that enabled the call recording button on the dialer - and it worked very well (although it was only stated to work with LOS 14 & 15, as far as I remember)!

Anyway, I wanted to test it, but I'm not able to find it anbymore.
Does anyone know that module as well (and have it still availiable somewhere), and if so, is it working for the ArrowOS on Poco X3?
I tested some modules and other plugins etc. nothing worked, until I tried to follow the steps mentioned in this thread (I use AOSP Dialer, ArrowOS Vanilla nad Nikgapps Core): https://forum.xda-developers.com/t/how-to-enable-native-call-recorder.3996233/
and after some frustrating trial and error finally managed to get it working for my country. I added to the MMC folders Bools.xml: <bool name="call_recording_enabled">true</bool>
,created the MNC Folders for my counttry network providers and added Bools.xml files in every one of the MNC Folders with <bool name="call_recording_enabled">true</bool> in it.
If someone wnats to download my version(Works for Brazil!) download it here:
and decompile, and have a look what I did. Just rename the MMC and MNC folders according to your country, compile it, then put it in the /product/priv-app/Dialer folder and install it. I use total commander to open the file, total commander needs to have root . And you got to try several times, I needed to reboot two times and stop the dialer app, finally the dialer app installed sucessfully and works, my and the other voice is recording, files are in the /storage/emulated/0/music/Call Recordings folder. This is not a step by step guide, but should give a good idea of how it basically works, I don´t remember everything how and what sorry.
 
  • Like
Reactions: just Nob

Makuhita22

New member
Apr 14, 2021
2
0
I have 2 questions for this thread:
1) On the original post there is stated no magisk is need but I would assume your banking apps etc would still recognize your phone as rooted? Which I didn't try because I instantly flashed magisk after first boot. I used the GAPPS version for this.
2) Is there something I can do about a kernel panic seems to be caused by a fatal error on modem. Modem subsystem failure reason seems to be LTE (something about my carrier service)? Maybe a de-sync between wifi and 4G?
Anyway it causes my phone to reboot some time more severe than other times. This is an anoying occurance.
Thanks in advance.
172505649_499316691084203_4736219218237918096_n.png
 

blekr

Senior Member
  • Dec 2, 2013
    121
    41
    Xiaomi Poco X3 NFC
    I have 2 questions for this thread:
    1) On the original post there is stated no magisk is need but I would assume your banking apps etc would still recognize your phone as rooted? Which I didn't try because I instantly flashed magisk after first boot. I used the GAPPS version for this.
    2) Is there something I can do about a kernel panic seems to be caused by a fatal error on modem. Modem subsystem failure reason seems to be LTE (something about my carrier service)? Maybe a de-sync between wifi and 4G?
    Anyway it causes my phone to reboot some time more severe than other times. This is an anoying occurance.
    Thanks in advance.View attachment 5278813
    Before the root there are no problems with banking applications. After the root I only had to hide Magisk from the settings and the banking applications did not detect it. The safetynet test with or without root, it always passes the test.

    What test did you run from the terminal?, to try it in mine and give you my results.
     

    jjcdennis

    Senior Member
  • Jun 20, 2015
    428
    98
    Toronto
    Well I have to do a clean flash after force uninstalling Android Auto (mistake) and want to make sure I do it right. I have these instructions from the first time I flashed Arrow:

    1618610895256.png


    Is this still the right method for a clean flash? Its different because with my last phone I had to do an advanced wipe on the phone and format data before installed the ROM.
    Thanks
     

    Revontheus

    Senior Member
  • Aug 1, 2013
    1,997
    1,087
    cycling/studying or asleep
    Well I have to do a clean flash after force uninstalling Android Auto (mistake) and want to make sure I do it right. I have these instructions from the first time I flashed Arrow:

    View attachment 5281379

    Is this still the right method for a clean flash? Its different because with my last phone I had to do an advanced wipe on the phone and format data before installed the ROM.
    Thanks
    The OrangeFox referred to in that post is outdated. Get the latest version.
     

    Top Liked Posts

    • 1
      Netflix is glitching so much I need to wait like 2minutes before it will be fine again fast forwarding triggers the glitch again please fix it 😭😢😭😢😭
      1
      Flashed the ROM with TWRP, did data wipe, and now the phone only boots into TWRP and doesn't boot into system. Any idea?
      Format. Don't wipe.
      1
      Flashed the ROM with TWRP, did data wipe, and now the phone only boots into TWRP and doesn't boot into system. Any idea?
      Format data, the one in which you have to type 'yes'. It will delete all files on your storage.
    • 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
      4
      Ganesh, since you're here, any information on the TWRP encryption issue after the June 9 build?
      I'm yet in the process of figuring it out. I'm completely caught off-guard by this weird issue all of a sudden as there has been literally no changes been made to the device sources nor the rom source so at this point i'm not sure what's even causing it. I've also decompiled the twrp and went through its contents but everything looks fine and dandy in there.

      For now i would suggest to make use of Arrow recovery to meet the needs of OTA updates etc.
      3
      I was on the latest global MIUI and tried to install Arrow, but got a bootloop to orange recovery.

      I followed all the steps, so I'm at a loss for what happened. Orange fox says something about encryption, but the main page of the rom mentions nothing about that for flashing it from stock MIUI.

      I reflashed it stock, unlocked bootloader again, installed the TWRP mentioned in the first post.
      Then installed latest Arrow GAPPS with it, formated data.
      It installed fine, but the ROM wasn't working. System crashing all the time during config.
      1) Download and install latest fastboot ROM which is based on Android 11 (MIUI V12.0.8.0.RJGEUXM Stable Official Update for
      POCO X3 NFC EEA)


      Fastboot, the one which is 4.9 GB

      2) Unlock bootloader.
      3) Install TWRP (twrp-3.5.2_10-4-surya.img)


      4) Install this ROM (I used GApps version)
      5) Format DATA (it's where you have to type in "yes"). Don't do any other wipes before or after installing this ROM.
      6) Reboot and enjoy
      3
      4PDA link to patch not working (error 404).

      Someone needs to get in touch with @ganesh varma to present that solution and upload the patch to the ArrowOS Gitlab Tracker, so that it can be incorporated into the device tree.
      That is because you do not have the 4pda account. That is why it shows that error.

      Here is the .zip patch.
      3
      Neither morals nor stories, i have installed all OTA updates automatically through recovery, except when the developer decided to migrate to OSS Vendor. The installation problems or errors are not due to recovery. They are the fault of users who do not read the recommendations. The migration process has already been discussed for several pages. I don't understand why there are still users stupid to upgrade from a MIUI provider build to the new OSS provider build, simply wanting to update the recovery .zip, when this would mean data loss without having made a copy of security, and then they come here with their irony to complain or cry that they have lost their information
      Wtf are talking about, who said I was on MIUI vendor, I was very clear in my post that I was on the first OSS version before updating to latest ArrowOS.

      That recovery which was supposed to work with OTA ArrowOS from Open Source Vendor to Open Source Vendor didn't work as expected and instead booted to ArrowOS recovery with failed to boot message with one option only and that was to Factory Reset to use my phone again.

      Go back to school and relearn how to read before you start calling people idiots.
    • 52
      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
      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.