Yes, for me it works without having to tweak anything, though if you plan on rooting that may be a different story.Hi, had a few questions..
Do banking apps work ?
Does safetynet pass and is selinux enforcing?
Yes, for me it works without having to tweak anything, though if you plan on rooting that may be a different story.Hi, had a few questions..
Do banking apps work ?
Does safetynet pass and is selinux enforcing?
I get error when I issue fastboot flash boot_ab magisk_patched-23000_[some CODE] anyone had this issue?Tried it like that and it worked perfectly. Caffeine keeps the screen & phone awake. The update takes about half an hour (rather add a few minutes than take a few) and then you're on the newest version.
For Magisk I'm still using the method described b y @kwanice in this thread.
You need adb and fastboot installed, USB debugging over developer settings needs to be activated and the PC allowed to use it once the phone is connected.
- Extract boot.img from the newest ROM-zip. I'm using the excellent tool Fastboot Enhanced by @xzr467706992 which allows you to add the ROM and then extract the boot.img by:
- Download zip under "Assets" from here and extract it.
- Start the GUI from FastbootEnhance.exe
- Select tab Payload Dumper
- Click Browse button and add the ROM-zip you installed on your phone
- Select tab "Partitions"
- Select boot (should be around 100 MB size), click the Extract Image button on the right and choose the location where to save the boot.img (ideally where your adb.exe is)
- Start a cmd- or Powershell-window and locate your folder where adb and fastboot are installed through
cd C:/ADB/
(change accordingly. For me adb.exe is under C:/ADB/adb.exe)- Connect your phone to your computer and check that you're in the right folder with
adb devices
It should say:
* daemon not running; starting now at tcp:5037
* daemon started succesfully
List of devices attached
[some numbers] device
(if it says "unauthorised" instead of "device" you haven't authorised USB debugging on this PC - there should be a pop-up message on your phone about it)- Copy the boot.img to your phone with the command
adb push boot.img /sdcard/
If you put the boot.img somewhere other than in the same folder as your adb.exe you need to use the following
adb push X:/path-to-your-file/boot.img /sdcard/
If you did it correctly, the screen should read
boot.img: 1 file pushed, 0 skipped. [some numbers about speed]
- Now open the magisk app on your phone, tap the "Install" next to Magisk, tap "Select and Patcha File" and select the boot.img you just copied to your internal memory (a file browser helps with navigating)
- Tap "LET'S GO ->" and let the process work. It should tell you at the end, that the patched image has been saved in your Download folder, leave this screen open
- in the command window on the PC type
adb pull /sdcard/Download/magisk_patched-23000_[some CODE]
The code is random.
Note: The magisk_patched part might change depending on version. Just have a look what it's called in the magisk app.
If you done it correctly the command window should show
/sdcard/Download/magisk_patched-23000_[some CODE].img: 1 file pulled, 0 skipped. [some numbers about speed]
Also, the file magisk_patched-23000_[some CODE].img should turn up in your ADB and fastboot-Folder.- Uninstall Magisk app
- Reboot phone into fastboot mode
- In fastboot check that everything works by typing into the command window
fastboot devices
which should show
[some numbers] fastboot
- Now flash the modified boot.img with the command
fastboot flash boot_ab magisk_patched-23000_[some CODE]
It should show
Sending 'boot_ab' (12345KB) OKAY [ 1.234s]
Writing 'boot_ab' (bootloader) Partition boot_a flashed successfully
(bootloader) Partition boot_b flashed successfully
OKAY [ 1.234s]
- Now restart the phone with
fastboot reboot
- Once the phone is restarted, download the newest Magisk-app again and install it
- Done!
Please enable 'Pause App' feature. (if possible), Thank you <3Update 2022-01-12
Device changelog:
- Update blobs to MIUI V12.5.5.0.RKHMIXM
- rootdir: Allow all filesystems for USB-OTG
- props: Increase audio HAL buffer size to 240
- Misc fixes and upstream changes.
Kernel:
- Merge branch android-4.19-stable of android/kernel/common
- Misc fixes and upstream changes.
ROM changelog: https://arrowos.net/changelog.php
Installation instruction: https://forum.xda-developers.com/t/...othin-arrowos-12-0-beta.4348617/post-85790097
Download: https://arrowos.net/download/alioth
Note:
- Recommend use with fw part MIUI 12.5.5.0 (A11) Global / India / EU.
P.S. My personal Telegram support chat: https://t.me/mipa_lab
This still isn't fixed. Is this a Google problem? It needs to be fixed in the official builds beforehand?
I've been facing the same issue since December update and was hoping the January one would have a fix. My guess it's a Google problem but not sure.I have to say this is an amazing build by devs. Hats of for them, honestly these are amazing work they are doing for us free. We should appreciate them.
Everything in this ROM is great, just one single issue I am facing last 1 week most is, "SCREEN NOT TURNING OFF EVEN AFTER 15 SECONDS OF SCREEN TIME OFF HAS BEEN SET". Any solution for this would be great. Build Number SQ1D.211205.017
![]()
If anyone stumbles across this error, when trying to flash the new firmware "This adb server's $ADB_VENDOR_KEYS is not set":I just did apply update from arrow recovery and on my computer typed "adb sideload <name of the firmware zip>. Then on the phone there was a warning that the package signature verification failed. I just confirmed I did want to apply the update anyway. After the flash was done, I just rebooted the phone.
Using as daily driver since november.I'm considering to update from ArrowOS 11. However, I'm held back by various reports of problems in this topic (such as the one above the post), which make me doubt if this ROM is stable 'enough' yet.
Any thoughts?
it's the stupid reddit app, i had too root my phone and check every process to find the culprit
I think the difference is you're away from miui which is a bloated trash bagNope. But I'm not sure there's any real difference between "turbo mode" à la MIUI and, say, "clearing all inactive apps and putting aggressive background activity policiies on apps"
Nope. But I'm not sure there's any real difference between "turbo mode" à la MIUI and, say, "clearing all inactive apps and putting aggressive background activity policiies on apps".Thanks bro! Is there an option to boost gaming performance? (ie: Miui's game turbo, performance mode)
/*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, We will laugh at you.
* It is your fault because you chose to do all the modifications on your device.
* Remember projects like these and the work done on them is a hobby to the
* contributors and the team members, no one is working for you nor is getting paid for it
* have some respect for the work done by them since it is done purely on interest or a hobby
*/
fastboot flash boot_ab boot_alioth.img
fastboot flash vendor_boot_ab vendor_boot_alioth.img
fastboot reboot recovery
adb sideload name.zip
adb sideload name.zip
adb sideload name.zip