Develop Bugs

V4A Driver Won't Stick

I Flashed V4A_2.3.4.0_Enforcing_Lollipop.zip with TWRP on stock, rooted 6.0.1 nexus 5x, with Busybox installed, SuperSU mount namespace unchecked and selinux both permissive and enforcing and can't get driver to stick! I'm Prompted to install after every reboot. App storage perms are on. Any help most appreciated. Thx
I've posted my question in two other threads but none has answered

You need to delete the file "audio_effects.conf" in /root/vendor/etc/ Use a file explorer or something else you can get access to edit root files

Stop with the old stuff, so many things to do to get it working. Just flash latest version by guitardedhero or flash the new ARISE sound mod. Guitardedhero has worked so hard to make these mods super compatible.

Thanks to both of you. Pollie, I am unfamiliar with Guitardedhero. Can you please provide a link?
Hypemanisus, I did as you suggested, and while I am no longer prompted to update the driver upon opening V4A, and in fact the option in settings says ,"Uninstall Driver," driver status is still No, Unsupported an Abnormal across the board. Indeed I am not hearing any enhancement either as I certainly did hear with my Nexus 6 and Galaxy S4.

http://forum.xda-developers.com/android/software/viperaudio-viperatmos-3-8-sq-driver-t3289075 , isntall the universal version , should work .

Thanks Apyah. I will get around to this this weekend and advise

Flashed Dolby Atmos as directed. It is stopping upon opening. Perhaps there is conflict with previous version of V4A, which I removed using a root uninstaller. Advice?

Is there a flashable uninstall zip for the above V4A system app? Concerned some files might have been left behind which are conflicting with guitardedhero. Tried dr ketan fix too with v4a didn't allow driver install either

But then again I really have no idea. Quite frustrated. NEED MY VIPER compulsively!

what did you flash ? don't flash dolby atmos , just flash universal version , it has dolby and viper , just turn off dolby and use viper , don't delete anything .

Perhaps i'm crazy but there's no more link for the Viper|Audio. Only Viper|Atmos and DD.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Cannot find Guitarded Hero Universal Audio system app so I installed the latest V4A user app (V2.4.0.1). Removed "audio_effects.conf" from /root/vendor/etc/. Set SelLInux to permissive. Installed Driver. SOFT reboot and it now works. Still upset though because It's a pain to have to setenforce 0 then soft reboot and run phone in permissive every time. Coulda sworn i read somewhere a script to get this to run in enforcing...

no need permissive , i just flash the universal version on my 5X and G2 (5X hard brick now) viper work on both phone in enforcing SElinux .
Try reinstall your rom , clean wipe .

Thx Apayah. Where can I find this universal version you speak of please?

the one i gave to you , or to be simple http://forum.xda-developers.com/attachment.php?attachmentid=3701983&d=1459364213

[UNOFFICIAL][RMX1901] Lineage Os 16 For Realme X

Sup!
Hope u guys are having a great day, today we are proud to release Lineage Os 16 For Realme X
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to Install?
•BOOT INTO TWRP
•WIPE SYSTEM, DATA, DALVIK CACHE
•FLASH THE LINEAGE OS ZIP
•FLASH GAPPS
•THEN REBOOT
BUGS :
•Volte Doesn't Work
•Fingerprint Sensor Doesn't work
New Build bug fixes :
•Fixed Front Camera
DOWNLOAD :
LINEGAE OS 16 LATEST BUILD
Credits :
@SamarV121
|| If you are facing any issues or want to keep up with development of this device then join us on telegram at RealmeXOfficial ||
Regards @APHACKER007
Kernel Source : https://github.com/realme-kernel-opensource/realmeX-kernel-source
Device tree : (Shared in the download Link)

Not For Chinese version?

Great work . Will try it

Will it be possible to fix fp and camera when source codes are released?

nice work dev

Can i use this rom in my CN realme X?

Hello friends,
How can we install TWRP?
Thanks

Nice work

For now the kernel source has been realeased, will fix Fingerprint and Front camera please? (and volte)

Kernel Sources Released
The kernel Sources for the Realme X has been released. I really hope the Devs fix all the issues soon so I could use this as my daily driver!~?

Waiting for an update after integrating new kernel released in it.

Can't flash lineageos
Hemelorten11 said:
Can i use this rom in my CN realme X?
Click to expand...
Click to collapse
I have twrp on RMX1901CN but I can't flash this lineageos. Error 1001 and "can't mount /system"

LovemyRealme said:
I have twrp on RMX1901CN but I can't flash this lineageos. Error 1001 and "can't mount /system"
Click to expand...
Click to collapse
Have you got root on this phone? Magisk or SuperSu?
Thx.

nickyip123 said:
Have you got root on this phone? Magisk or SuperSu?
Thx.
Click to expand...
Click to collapse
From TWRP, I successfully flash Magisk (19.2, and 19.3) but still can't flash lineage os.

Share some screenshots guys...

It says the device is not play protect certified when i flash gapps. and when i flash magisk, it deletes the rom and boots back into bootloader. please help.

Can anyone here help me. I got the error "The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service" after flashing something in TWRP is there any way to get out of this?

Any update?

kakagi said:
Any update?
Click to expand...
Click to collapse
In latest update, front camera is fixed, but fingerprint sensor is still not working.

nickyip123 said:
In latest update, front camera is fixed, but fingerprint sensor is still not working.
Click to expand...
Click to collapse
Is it something that can't be fixed or just something that will take time to fix?
Sent from my RMX1901 using Tapatalk

[NEWS/GUIDE] Pass SafetyNet with stock, bootloader unlocked, rooted RUI with Magisk and custom kernel. Now virus scan of apks is removed too!

Source: https://forum.xda-developers.com/t/...net-test-on-coloros-6-1.4094995/post-82499427
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Alright guys. I found a solution! Actually, yes, I just found it but someone else came up with it. As of now I'm running latest RUI on my Realme Q. It's a bit newer (RMX1971_11.C.11, released: 2020/12/27) than the Indian or EU update (RMX1971EX_11.C.08, released: 2020/11/28) but that shouldn't make a difference in our case. I'm now running the above mentioned, stock, official ROM with a few modifications. I migrated from Pixel Experience Android 11 by Bablus by clean flash.
Saved all my data to external SD card.
Cleaned everything in TWRP.
Formatted all partitions to ext4 (since sadly RUI doesn’t support f2fs)
Flashed the official .ozip update file through wzsx’s TWRP that is capable of direct flashing .ozip files (I’m unsure about the TWRP you RM5P guys use though… But you can find this TWRP online or in the group)
Without exiting TWRP, I flashed the TWRP.img as recovery since stock rom overwrites that.
Flashed modified vbmeta.img too for the same reason.
Flashed SilonT Kernel v5 Hana, then Magisk Stable release 21.4
Then formatted data just to make sure.
After first startup when tried to launch Magisk Manager it said it was incorrectly or partially updated, probably because of RUI. It fixed itself by downloading the latest Manager.
As of now SafetyNet fails, both CTS and basicIntegrity, don’t fret.
Download and install from Magisk module repo: MagiskHide Props Config, AR Core/Playground Patcher and lastly Busybox (I’m unsure of this had anything to do with successfully passing the test, probably not but I use it frequently)
Turned on MagiskHide from Magisk settings.
Rebooted the device. After reboot SafetyNet Passes.
Debloating is done though I'm still polishing here and there.
As of now:
Roughly debloated ROM : ✓ Shown in video:
Magisk : ✓ (21.4 stable release)
Busybox : ✓ (Magisk module)
SafetyNet : ✓ (CTS profile & BasicIntegrity)
Custom kernel : ✓ (SilonT Hana v5 release)
Kernel manager : ✓ (SmartPack kernel manager)
Free apk installing without restriction : ✓ (ADB debug: "adb shell pm disable-user --user 0 com.coloros.phonemanager")
Permissive SeLinux : ✓ (turn off MagiskHide, Change Selinux State with The SeLinux switch app, turn MagiskHide back on, check SafetyNet, it'll probably pass. Only works until reboot or till you change selinux state yourself)
Remove recovery rootcheck: ✓ (delete recovery rootcheck and ck.fs files from root/vendor/oppo folder. These files detect if the System is rooted and makes battery consumption higher, also makes the device overheat faster thus subtly prompting the user to revert to unrooted device. Clever Oppo. Very clever.)

Question Rooted and debloated with C.47 update (some apps, mainly google, would open and crash)

I don't know if it's just me, but I updated to C.47 by:
Magisk uninstall, restoring stock images.
installing the update
Magisk install to inactive after OTA completes
Reboot.
I have 4 modules. USNF, osm0sis busybox binary, debloater and systemless hosts.
The only way I was able to get them to work was by disabling all modules, rebooting, finding the google play store APK download from APKMirror and installing it.
Now, I have randomly cloned APKs, but they were only ones I debloated. I debloated again and they vanished.
I admit this thread might be a huge waste of your time to read, but if someone is having this trouble, it might bail them out

I am in same situation like u with Google play store and Google services play crash .I try everything but no luck .finally idowngrade to os 11. But I'm very intested to know why Google applications crash .The only magisk module installed is : Octavia dialer A12.

Wow, good to know this is happening and that you found a workaround. I guess I'll probably wait a few days to install this and see if other people are having issues.

In c47 version, the 5G option returned in network settings?

DavidKalil10 said:
In c47 version, the 5G option returned in network settings?
Click to expand...
Click to collapse
Not for me

Skenderbeggar said:
Not for me
Click to expand...
Click to collapse
I've just discovered a workaround isign the app force LTE/5G. With this app is possible to open the Network settings and force the 5G as it was possible in Android 11 using *#*#4636#*#*
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

It fails when reaching the middle

Moka UA said:
It fails when reaching the middle
View attachment 5566125
Click to expand...
Click to collapse
are you rooted?

Yes

Moka UA said:
Yes
Click to expand...
Click to collapse
go to magisk, uninstall magisk. pick restore images. DO NOT REBOOT. install the update. go back to magisk. install magisk to inactive slot. reboot
i'd disable whatever modules you have enabled.

aNGERY said:
go to magisk, uninstall magisk. pick restore images. DO NOT REBOOT. install the update. go back to magisk. install magisk to inactive slot. reboot
i'd disable whatever modules you have enabled.
Click to expand...
Click to collapse
Ok..i have root zygisk ..Is there a problem with that?

Moka UA said:
Ok..i have root zygisk ..Is there a problem with that?
Click to expand...
Click to collapse
Zygisk is fine, only installed modules should be disabled when you update to avoid possible issues. Most modules won't have any issues, though.

Question Cannot activate Magisk after MUI Update

Hello,
I had a working Setup with TWRP + Magisk.
Then I had the stupid idea to accept the OTA update to MIUI 14.0.6.0 (eu).
As I lost my root permissions, I decided to install Magisk again. I used the boot.img from the rom and installed it via fastboot from magisk_patched-XXXX.img.
When I look into the Magisk App (v26.1), it still states: "Installed N/A".
I also tried to flash the patched boot image via TWRP, but there is no way to gain root access anymore :/
Current Version: MIUI V14.0.6.0.TKHCNXM | stable
Can somebody give me a hint, what i'm doing wrong? I also tried to flash the _a and _b slot...
Thanks,
Stefan

stefan_at_localhost said:
Hello,
I had a working Setup with TWRP + Magisk.
Then I had the stupid idea to accept the OTA update to MIUI 14.0.6.0 (eu).
As I lost my root permissions, I decided to install Magisk again. I used the boot.img from the rom and installed it via fastboot from magisk_patched-XXXX.img.
When I look into the Magisk App (v26.1), it still states: "Installed N/A".
I also tried to flash the patched boot image via TWRP, but there is no way to gain root access anymore :/
Current Version: MIUI V14.0.6.0.TKHCNXM | stable
Can somebody give me a hint, what i'm doing wrong? I also tried to flash the _a and _b slot...
Thanks,
Stefan
Click to expand...
Click to collapse
You'll want to use fastboot to boot recovery (not flash)
And install the recovery via the on device gui
Also, I would use orangefox recovery, it was built from twrp, but has more features.
Use "method 2" in this guide:
https://theandroidrush.com/how-to-flash-orangefox-recovery-on-xiaomi-phone/

Hi,
I flashed the patched magisk boot via orangefox, but no success. Magisk still N/A
Step1: Patch boot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step2: Flash via TWRP or Orangefox
no screenshot available
Step3: Result, no Magisk (N/A)
I don't understand this. Is there a greater change in MUI14?
I also installed the Magisk APK via TWRP and Orangefox, but no other result.
Thanks,
Stefan

After serveral hours of debugging I found out, that there was a post on the net, which recommended to install the debug version of Magisk. This was a first step into the right direction. But the GUI crashed and removed the Magisk App.
The strange thing was, that all other whitelisted root apps worked. But no access to change the Whitelist.
So I tried to get the GUI back. But there was no way.
When I installed the APK, it was automatically killed and removed :/
After reinstalling via the xiaomi.eu repair (update) script I decided to to try an older Magisk Version (26.0). This crashed also, but I was able to re-run the app again.
Finally it seems that Magisk implemented a change, that crashes with my MIUI version. I will observe this and try to file a bug report.