This procedure will put temporarily SELinux in PERMISSIVE.
I'M NOT RESPONSIBLE FOR ANYTHING YOU DO ON YOUR PHONE!
You find SELinux switcher here (it's temporary, if you uninstall the app it will return to ENFORCING):
https://forum.xda-developers.com/android/apps-games/app-selinux-switch-t3656502
Because not having Viper is not an option and I had bad experience before with Arise Magnus Opus because it consumed a lot of battery, for the moment I prefer to use Viper in permissive.
PROCEDURE:
Reboot into recovery and install V4A+2.5.0.5.zip
Boot normally install BusyBox and launch Viper4android.
Select install drivers, grant root permission and wait until it is installed.
Don't worry if an IO Error occurs, it'll work anyway.
Reboot and open any file manager.
Delete the Viper4android folder in "/system/priv-app".
Rename "/system/vendor/etc/audio_effects" to "/system/vendor/etc/audio_effects.bak"
Copy audio_effects in the attachment to /system/vendor/etc/
Install ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk (don't execute)
Install The.SELinux.Switch.ver.6.0.8.build.608.apk and set to permissive
Reboot once again and open Viper4android - driver is now working
NOTE: This method is the most stable of the ones I found till now
{
"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"
}
If you uninstall the app. The sound mod will stop working. SELinux Switcher patches the status on every boot. So whenever you reboot you'll get an Enforcing kernel again. (Not entirely sure). And for Viper4Android to work it needs a permissive kernel.
Edit : You have stated it in OP. Didn't notice! Very well ?
I have solution with working enforcing selinux on stock rom.
Disable stock audio effects. Go to recovery and flash latest magisk. Reboot system to load all magisk files and reboot again to recovery. Flash attached f2f loopback fix. Reboot in system and in magisk manager download module called Viper4Android FX Materialized and flash it. I recommend to download deep buffer remover to, to allow v4a processing on streaming music players like spotify.
My current setup is ainur audio with dolby atmos and v4a - all like a modules in magisk.
Do not wipe cache in recovery, because all modules will be gone!
Enjoy.
dado_13 said:
I have solution with working enforcing selinux on stock rom.
Disable stock audio effects. Go to recovery and flash latest magisk. Reboot system to load all magisk files and reboot again to recovery. Flash attached f2f loopback fix. Reboot in system and in magisk manager download module called Viper4Android FX Materialized and flash it. I recommend to download deep buffer remover to, to allow v4a processing on streaming music players like spotify.
My current setup is ainur audio with dolby atmos and v4a - all like a modules in magisk.
Do not wipe cache in recovery, because all modules will be gone!
Enjoy.
Click to expand...
Click to collapse
Are you able to install the modules in Magisk with 7.1.1?
citytrader said:
Are you able to install the modules in Magisk with 7.1.1?
Click to expand...
Click to collapse
With f2fs loopback fix, yeah, see attachments.
dado_13 said:
With f2fs loopback fix, yeah, see attachments.
Click to expand...
Click to collapse
I was able to make one of the modules work, but if I unplug and plug again my headphones, Viper stops to work, it does not process audio again
citytrader said:
I was able to make one of the modules work, but if I unplug and plug again my headphones, Viper stops to work, it does not process audio again
Click to expand...
Click to collapse
With your method you don't experience this problem?
dado_13 said:
With your method you don't experience this problem?
Click to expand...
Click to collapse
With the first method all works flawlessly, if I install the patch for the F2FS Loopback I experienced that something was wrong, for example with Total Commander I had delay opening folders, etc... for the moment I will stick with the method using the permissive kernel that all works perfect.
Newbie here. The only reason I'm considering rooting my phone and trying something like Viper4Android, is because I want to resolve the issue with the ascending ringtone and low speakerphone call volume. I want to override all of the volume limitations that Motorola has forced on me with Moto Z Play. Can someone who knows exactly what I'm talking about, assure me that this problem is gone, once you root the phone and install Viper4Android? To risk bricking my phone, only to have this problem persist, would be infuriating, as I'm sure you can appreciate.
Thanks for your help!
onekingprods said:
Newbie here. The only reason I'm considering rooting my phone and trying something like Viper4Android, is because I want to resolve the issue with the ascending ringtone and low speakerphone call volume. I want to override all of the volume limitations that Motorola has forced on me with Moto Z Play. Can someone who knows exactly what I'm talking about, assure me that this problem is gone, once you root the phone and install Viper4Android? To risk bricking my phone, only to have this problem persist, would be infuriating, as I'm sure you can appreciate.
Thanks for your help!
Click to expand...
Click to collapse
If you root your phone means you can do modifications, that's it, If your goal is to get more volume just edit MIXER_GAINS.XML and thats it, you don't Viper for that.
If you root the phone in the correct way, you don't have to worry about bricking the phone, I have went from 6.0 to 7.1.1 and after that returned to 6.0 a couple of times and never bricked my phone, do all by command line (don't use RDSLite) not flashing modem, fsg and NON-HLOS and that's it and do not use OTA Rom's.
citytrader said:
If you root your phone means you can do modifications, that's it, If your goal is to get more volume just edit MIXER_GAINS.XML and thats it, you don't Viper for that.
If you root the phone in the correct way, you don't have to worry about bricking the phone, I have went from 6.0 to 7.1.1 and after that returned to 6.0 a couple of times and never bricked my phone, do all by command line (don't use RDSLite) not flashing modem, fsg and NON-HLOS and that's it and do not use OTA Rom's.
Click to expand...
Click to collapse
Okay, bear with me, here. In order to edit the .xml file you're talking about, do I still need to root the phone? I assume I do. Secondly, where would I find this file on my phone? I only heard about the concept of "rooting" a week ago. Didn't even know this world existed. So, I'm afraid I need to be "spoon-fed" this stuff, to start with. Thank you for your patience and help.
onekingprods said:
Okay, bear with me, here. In order to edit the .xml file you're talking about, do I still need to root the phone? I assume I do. Secondly, where would I find this file on my phone? I only heard about the concept of "rooting" a week ago. Didn't even know this world existed. So, I'm afraid I need to be "spoon-fed" this stuff, to start with. Thank you for your patience and help.
Click to expand...
Click to collapse
Root allows you to modify stuff in the phone that is normally protected, you can access to the root filesystem that otherwise is not possible, before doing anything I suggest you to read the tutorials here to avoid making mistakes.
Here you have some good tutorials in spanish:
http://www.htcmania.com/showthread.php?t=1243470
The file to modify in Moto is /system/etc/MIXER_PATHS.XML
MIXER_GAINS.XML is for Galaxy A7 for example.
Thanks. Got this working on my G5S
Got it working on my Nexus 6 , stock rom 7.1 with EX kernel. But upon clicking the equalizer in stock Play Music app the Music fx crashes . I was personally hopping to access Viper via that option.. any ideas?
Thanks
hi good day..can this be flash on the new update Oreo?
You actually just need to download the Magisk Module for it to work.
Thanks!! I've been trying to get this to work all day! and this was the only method that worked for me
Related
Hey!
I try to install ViperFX on my Mi 5s with LOS alike roms but it doesn't work at all. I tried on the latest nougat based roms like RR, viperOS and AICP.
I flashed guitardedhero, changed the audio config in etc folder - enabled: no
I used Magisk to install the mod - enabled: no
I installed the 'fix' apk, changed the audio confg - enabled: no.
Of course I have a root and I have busybox installed but it just keep refusing to work with me.
Please help, I love stock-based roms but the sound quality is like so terrible.
Ok, disclaimer now - the sound on viperOS was pretty god, but it has some issues and last update was pretty long time ago.
Thanks in advance!
mychall said:
Hey!
I try to install ViperFX on my Mi 5s with LOS alike roms but it doesn't work at all. I tried on the latest nougat based roms like RR, viperOS and AICP.
I flashed guitardedhero, changed the audio config in etc folder - enabled: no
I used Magisk to install the mod - enabled: no
I installed the 'fix' apk, changed the audio confg - enabled: no.
Of course I have a root and I have busybox installed but it just keep refusing to work with me.
Please help, I love stock-based roms but the sound quality is like so terrible.
Ok, disclaimer now - the sound on viperOS was pretty god, but it has some issues and last update was pretty long time ago.
Thanks in advance!
Click to expand...
Click to collapse
1.Flash guitardedhero
2.Change audio_effects.conf (/vendor/etc/)
3.Install viperfx driver
4.Reboot
5.Enjoy
Well, that doesn't work
mychall said:
Well, that doesn't work
Click to expand...
Click to collapse
Go into viper activate the developer options and disable selinux
Still the same.
I also tried to turned on compatible mode but nothing happened
First flash SuperSU and then flash this file
First flash SuperSU and then flash this file.
xcf258 said:
First flash SuperSU and then flash this file.
Click to expand...
Click to collapse
But will it work with Magisk? I use root hide for some apps
Edit:
Ok, I've tried it on a clean installation. Eh. Still nothing. This time each time viper prompted alert that driver is not installed, each time it installed successfully but after the restart it all started over again
Ok I have the same problem with you and waiting solutions
Try disabling SELinux from viperfx settings (developer mode) and turning on master power (after installing the drivers). Before installing the drivers change audio_effects.conf to audio_effects.conf.bak in vendor/etc.
mychall said:
But will it work with Magisk? I use root hide for some apps
Edit:
Ok, I've tried it on a clean installation. Eh. Still nothing. This time each time viper prompted alert that driver is not installed, each time it installed successfully but after the restart it all started over again
Click to expand...
Click to collapse
Disable SELinux before installing the driver.
You have to disable SELinux to enable ViperFX each reboot.
You can use SELinuxModeChanger to disable SElinux.
I hope that will be helpful.
xcf258 said:
Disable SELinux before installing the driver.
You have to disable SELinux to enable ViperFX each reboot.
You can use SELinuxModeChanger to disable SElinux.
I hope that will be helpful.
Click to expand...
Click to collapse
Ok, I can't check it before the trip but maybe someone else can try it!
Hello dudes and dudiens,
I got a question... I have a OnePlus 5t (Stock Rom / Franco Kernel / 128/8), I tried both systemless and system aplications of Viper4FX and I didnt have any effects on my
Sennheiser Momentum IE. But when I listened to music in my Car (via bluetooth) it had a effect. How could I fix this? :/ any thoughts.?
btw. I yes I have root + magisk (+ optional xposed)
have a nice day ^^
Are you using high res audio output? I had issues with Viper with that.
DerDavid01 said:
Hello dudes and dudiens,
I got a question... I have a OnePlus 5t (Stock Rom / Franco Kernel / 128/8), I tried both systemless and system aplications of Viper4FX and I didnt have any effects on my
Sennheiser Momentum IE. But when I listened to music in my Car (via bluetooth) it had a effect. How could I fix this? :/ any thoughts.?
btw. I yes I have root + magisk (+ optional xposed)
have a nice day ^^
Click to expand...
Click to collapse
Hi, you can try the version 1.7.3 - page 370 from this thread
https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058/page370
I cant install the driver
manojpawarsj12 said:
Change FX compatible mode from normal to compatible
Click to expand...
Click to collapse
Idk why but when I hit "Install Driver" it says: "The driver needs to be reinstalled. Do you want to do this now?"
I hit yes and then it sais: "Installion failed because of an I/O error. Try rebooting your device and try again"
I rebooted it but still not workin idk why .
DerDavid01 said:
Idk why but when I hit "Install Driver" it says: "The driver needs to be reinstalled. Do you want to do this now?"
I hit yes and then it sais: "Installion failed because of an I/O error. Try rebooting your device and try again"
I rebooted it but still not workin idk why .
Click to expand...
Click to collapse
Install busybox and then try to install driver
Hope it works
I was happy and did not know. It was perfect my viper4fx there magisk suggested an update to version 1.7.5 unfortunately I lost the equalizer, it did not work anymore. I installed busybox, drivers, dozens of times, backed up the versions, nothing. Damn update, I think I'll have to format. I'm sad.
Go into the App, then close it with the exit button in the menu. Then restart the App.
That's works for me.
Jajara249 said:
I was happy and did not know. It was perfect my viper4fx there magisk suggested an update to version 1.7.5 unfortunately I lost the equalizer, it did not work anymore. I installed busybox, drivers, dozens of times, backed up the versions, nothing. Damn update, I think I'll have to format. I'm sad.
Click to expand...
Click to collapse
I have the same issue. Now I use V4A from the XDA store and just install viper manually. It always works. It also shows up as a magisk module, and it works just fine with AML.
Also, if you want to use the magisk repo V4A FX by zackptg5, it doesn't seem to work on oreo but it works great on pie.
So, I went to change a few settings in V4A yesterday and the icon was missing. I could open the app by searching for it, sometimes it would show the icon, sometimes it would show the system app name "com.xxx.xxx" or whatever it is called. For the record, I have had no issues in the past with installing or running Magisk or V4a.
I decided I'd uninstall it, and reinstall to see if it would fix it.
I went into Titanium Backup and backed up the app and data.
Went to Magisk, uninstalled
Rebooted
Attempted to reinstall in Magisk, and it the install hangs
What resulted was a vicious loop of me trying to install uninstall, with the result being every time the install hangs in Magisk.
I'm wondering if this is a Magisk problem or a V4A problem, or an issue with Google protect being goofy with this app?
Just want to get my beloved V4A back =]
Thanks for your help.
I'm on latest Stock Pie with Latest Kirisakura Kernel.
The issues that I always had with v4a was that when I went to update it would install the update and then it would keep trying to load the driver after reboot. I ended up just going into magisk and manually uninstalling it before I went to install the update. And then it works great. I never backed up the settings in titanium before. I just saved my settings in the 'profile' page of the v4a and it always stays when I update. I update it and then load the old profile and move on with life.
So I am not sure if it was the titanium backup that messed it up or the lack of uninstall prior to the install of the updated version, I am, again, not sure. But I hope that this may help?
Yeah, I'm confident it wasn't anything to do with TiBu.
Incidentally, I later tried restoring the TiBu backup, but it just hung, as I anticipated. Perhaps I'll have to just do a clean install. Something got mucked up the first time the install hung I'm guessing.
MeetFace said:
Yeah, I'm confident it wasn't anything to do with TiBu.
Incidentally, I later tried restoring the TiBu backup, but it just hung, as I anticipated. Perhaps I'll have to just do a clean install. Something got mucked up the first time the install hung I'm guessing.
Click to expand...
Click to collapse
The more that I think about my experience with viper4android. I once also had that same issue where the icon would disappear. Ultimately I ended up manually uninstalling and reinstalling from the magisk repository and it seemed to work after that.
I understand the concept of titanium backup, however, I have, personally, never had any luck with any of the backups that I've ever made on reinstalling things. So honestly I don't really use Titanium Backup.
brandonpa said:
The more that I think about my experience with viper4android. I once also had that same issue where the icon would disappear. Ultimately I ended up manually uninstalling and reinstalling from the magisk repository and it seemed to work after that.
I understand the concept of titanium backup, however, I have, personally, never had any luck with any of the backups that I've ever made on reinstalling things. So honestly I don't really use Titanium Backup.
Click to expand...
Click to collapse
Thanks Brandon, did you just uninstall and reinstall Magisk in TWRP?
Any more, I typically just use TiBu to back up data on my apps for when I clean install, which isn't often anymore. The beauty of undefiled android is I can typically dirty flash monthlies without issue.
MeetFace said:
Thanks Brandon, did you just uninstall and reinstall Magisk in TWRP?
Any more, I typically just use TiBu to back up data on my apps for when I clean install, which isn't often anymore. The beauty of undefiled android is I can typically dirty flash monthlies without issue.
Click to expand...
Click to collapse
I just did it all through magisk.
MeetFace said:
Just want to get my beloved V4A back =]
.
Click to expand...
Click to collapse
I've been in this cycle before. What's worked for me is deleting the module in magisk, rebooting, downloading the module with magisk (don't install, just download) and then flashing the zip with EXKM app.
My install options are as follows - New Version of Viper --> Material Theme --> Install as System App. For some reason when I install the original themed version I get the "driver failed to install" message and have to start over again.
That is the exact process I go through when I update. I just use magisk to reinstall versus the exkm program.
This is puzzling. I removed the module, rebooted , downloaded, rebooted to TWRP, installed zip.
App icon doesn't show up, but when I search, I get this and I am able to open and it says it's processing:
{
"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"
}
Sent from my Pixel 3 XL using Tapatalk
ffchampmt said:
I've been in this cycle before. What's worked for me is deleting the module in magisk, rebooting, downloading the module with magisk (don't install, just download) and then flashing the zip with EXKM app.
My install options are as follows - New Version of Viper --> Material Theme --> Install as System App. For some reason when I install the original themed version I get the "driver failed to install" message and have to start over again.
Click to expand...
Click to collapse
This method works and on first reboot driver status is normal but on subsequent reboots driver status shows neon enabled=no and driver status=abnormal. If I use Magisk to flash V4a then there's no icon on reboot as mentioned previously. All this didn't begin till I installed Magisk 19.
MeetFace said:
This is puzzling. I removed the module, rebooted , downloaded, rebooted to TWRP, installed zip.
App icon doesn't show up, but when I search, I get this and I am able to open and it says it's processing:
Click to expand...
Click to collapse
Same here
I'm starting to believe this is a Magisk problem since updating?
The YouTube Vanced icon appears and disappears as well.
Sent from my Pixel 3 XL using Tapatalk
Hello,
Only Few days ago, we received the new OTA Update for our OnePlus 8 Pro devices,
notifying us to upgrade to the latest available stable version (11.0.4.4) from the older version 11.0.3.3.
with such great expectations based on update log.
{
"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"
}
As we're testing whether there are enough improvements in the latest update or not..
Let me share with you, how to update to the latest OTA update on a rooted OnePlus device..
Using magisk manager .. for magisk-rooted devices (without custom recovery of course) ..
First we check the new update notification in notification bar, and go to download the new update ..
if you didn't get that notification.. go to settings and check for updates manually
start to Download the update - the device will tell you that because of having a rooted device.. the software version will be downloaded as a full package from the start.. not just the update package ..
that's why it will be around 4.00 Gbs.
while waiting for the update to finish .. make sure your magisk manager is uptodate
and now return to ur update progress bar..
SOFTWARE Update Download finishes. Click on Install NOW to install the newest OTA update...
Make Sure ur device is charged at least 20% - Click Install
After Installation is Complete, DONT REBOOT ur device as it offers in the bottom of the screen
Now Go to magisk manager application once more..
choose install or update (as depicted).
choose the last option (install to inactive slot (after OTA) )
Agree to the warning that appears by clicking OK
Now it finishes flashing the new patched_boot to the inactive slot which will be master one after reboot.
Now click reboot .. and voila you have the new update without losing magisk..
Thanks for reading.
until we meet in another tutorial.. goodbye..
appreciate it
Thanks for your tutorial
Have had this tutorial up for over a year.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
Maybe read next time before putting so much effort in.
Doesn't work for me - in Android 11 OnePlus Updater doesn't offer downloading full update - it just instantly fails on rooted devices.
okgnew said:
Doesn't work for me - in Android 11 OnePlus Updater doesn't offer downloading full update - it just instantly fails on rooted devices.View attachment 5227685
Click to expand...
Click to collapse
You should just use oxygen updater bud
Deleted.
How has this process changed with Magisk 22.0 Since I can choose Install to Inactive Slot (After OTA) but hitting Let's Go does nothing?
update instantly fails for me too....I would use oxygen updater but...it's not available on there.
cali310 said:
update instantly fails for me too....I would use oxygen updater but...it's not available on there.
Click to expand...
Click to collapse
Same problem here, I have the OTA notification for 11.0.5.5 but I can't install it, not on Oxygen Updater either. Wish there was a way to get the file off my phone that failed to install so I could try a local upgrade myself.
I installed the update via local update, but I forgot to uninstall Magisk first, what should I do now? Should I continue with install to inactive slot or I pretty much lose the root and after start from scratch? Thanks!
marvyzoro said:
I installed the update via local update, but I forgot to uninstall Magisk first, what should I do now? Should I continue with install to inactive slot or I pretty much lose the root and after start from scratch? Thanks!
Click to expand...
Click to collapse
You shouldn't have uninstalled magisk, just disabled modules.
Yes install to active slot, provided you didn't reboot after the update.
If you rebooted then you'll need to boot (via fastboot) the patched image then install directly via magisk.
Let me know if you get stuck.
Thank you dladz. I went ahead and select the Install to inactive slot after OTA. It flashed and rebooted and it came back, but even after I locally installed beta 8, it came back as beta 7.
dladz said:
You shouldn't have uninstalled magisk, just disabled modules.
Yes install to active slot, provided you didn't reboot after the update.
If you rebooted then you'll need to boot (via fastboot) the patched image then install directly via magisk.
Let me know if you get stuck.
Click to expand...
Click to collapse
OK, I did the step one more time, installed the update follow with Magisk install to active slot. This time it came back updated to Beta 8 with root. Thanks!
The part that I am confused is that I didn't uninstall or disable the Magisk module before install the oneplus update as some other posts suggested that needs to be done first.
marvyzoro said:
The part that I am confused is that I didn't uninstall or disable the Magisk module before install the oneplus update as some other posts suggested that needs to be done first.
Click to expand...
Click to collapse
You don't have to but if a module requires a specific part of an OS like OPSystemUI.apk in my center clock mod's case, then you'll enter a bootloop.
However depending on the module you may be absolutely fine, so it's more of a fail-safe rather than anything else..
Can someone post the entire update file?
Hi! So today I got a notice of an update for 11.0.5.5.IN11AA on my IN2025 (8 Pro) which is rooted (I did mine by doing the download boot.img, patch with magisk, then flash with adb/fastboot on unlocked phone).
Looks like there's something different about the new update? I tried the process above and here's what happens:
Click "Download and install" button in update screen
Almost immediately you get a "Installation will continue when device isn't being used. To install now, tap Resume" error at the top.
Click "Resume" button in update screen.
Again almost immediately, get "Installation problem" error at top and button is now "Try again"
Try again just repeats the scenario. I have noticed a lot of OnePlus website pages, even my trade in page where I'm supposed to accept my trade in value, are throwing errors too. Maybe it's just a OnePlus server issue?
wesblake said:
Hi! So today I got a notice of an update for 11.0.5.5.IN11AA on my IN2025 (8 Pro) which is rooted (I did mine by doing the download boot.img, patch with magisk, then flash with adb/fastboot on unlocked phone).
Looks like there's something different about the new update? I tried the process above and here's what happens:
Click "Download and install" button in update screen
Almost immediately you get a "Installation will continue when device isn't being used. To install now, tap Resume" error at the top.
Click "Resume" button in update screen.
Again almost immediately, get "Installation problem" error at top and button is now "Try again"
Try again just repeats the scenario. I have noticed a lot of OnePlus website pages, even my trade in page where I'm supposed to accept my trade in value, are throwing errors too. Maybe it's just a OnePlus server issue?
Click to expand...
Click to collapse
If its incremental then it won't work that way..
It needs to be a full update.
If it is a full update, then just take the update locally, then run the OTA install on magisk
Thanks. Was able to follow the guide to update my phone today.
Like the title said after upgrade magisk to v25.2 i receive no sim card icon also seems like i lost my root after this....
someone can help me pls?
roberto_1986 said:
Like the title said after upgrade magisk to v25.2 i receive no sim card icon also seems like i lost my root after this....
someone can help me pls?
Click to expand...
Click to collapse
Magisk shouldn't have affected your SIM card icon in any way.
Open your phone app and type: *#06# and tell us if you get both IMEI numbers. You can also check this in Settings (the location will vary depending on which ROM you're using).
Compass.
Compass Linux said:
Magisk shouldn't have affected your SIM card icon in any way.
Open your phone app and type: *#06# and tell us if you get both IMEI numbers. You can also check this in Settings (the location will vary depending on which ROM you're using).
Compass.
Click to expand...
Click to collapse
Yes i can see both IMEI and ICCID 1 and SERIAL NUMBER!!!
I root my phone with LR TWRP-3.3.1-1104 that come with magisk v20 by default!
then from magisk im update first the app to 25.2 then magisk but when i put my magisk to 25.2
i receive no sim card icon....what i can do>???
its a week im stuck....>.<
roberto_1986 said:
Yes i can see both IMEI and ICCID 1 and SERIAL NUMBER!!!
I root my phone with LR TWRP-3.3.1-1104 that come with magisk v20 by default!
then from magisk im update first the app to 25.2 then magisk but when i put my magisk to 25.2
i receive no sim card icon....what i can do>???
its a week im stuck....>.<
Click to expand...
Click to collapse
Since I don't know what you've done to your phone, I recommend you the following:
Backup all your data;
Flash the latest MIUI fastboot ROM according to what you want (12.0.x for A10; 12.5.x for A11/A12/A13) with data format and don't re(lock) your bootloader;
Install the Custom ROM of your choice.
Some Custom ROMs pass SafetyNet by default, so there's no need to install any SafetyNet module neither Magisk Hide Props Config.
Instead of Magisk you could try Magisk Delta. I've never used it but it exists.
In the TeleGram groups people have been avoiding Magisk 25.2. I'm using 24.3 here.
Compass.
Compass Linux said:
Since I don't know what you've done to your phone, I recommend you the following:
Backup all your data;
Flash the latest MIUI fastboot ROM according to what you want (12.0.x for A10; 12.5.x for A11/A12/A13) with data format and don't re(lock) your bootloader;
Install the Custom ROM of your choice.
Some Custom ROMs pass SafetyNet by default, so there's no need to install any SafetyNet module neither Magisk Hide Props Config.
Instead of Magisk you could try Magisk Delta. I've never used it but it exists.
In the TeleGram groups people have been avoiding Magisk 25.2. I'm using 24.3 here.
Compass.
Click to expand...
Click to collapse
Ty for your answer!!!
Im always used stock ROM with A9 (the last firmware before A10) V11.0.3.0.PGGEUXM with Magisk v25.2
and LR TWRP-3.3.1-1104 without problem...
Only now i get this problem and its weird...also im followed this guide to root my phone:
[GUIDE][BEGONIA]Unlock Bootloader, Flash TWRP and Root[PROPER]
/* * Your warranty is now void. * * I am 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...
forum.xda-developers.com
Why i dont need to relock when use MI Flash??? tbh im always leaved as default without problem...
{
"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"
}
Also everytime i made a fresh install im used "advanced wipe" in recovery and delete everything system too
withouth problem!!!
Witch custom rom u suggest is the best to be installed? usually im prefer stock rom because the custom rom has some bugs so i prefer stay on stock rom but if there is some custom rom that is better then stock why not!!!
roberto_1986 said:
Ty for your answer!!!
Im always used stock ROM with A9 (the last firmware before A10) V11.0.3.0.PGGEUXM with Magisk v25.2
and LR TWRP-3.3.1-1104 without problem...
Only now i get this problem and its weird...also im followed this guide to root my phone:
[GUIDE][BEGONIA]Unlock Bootloader, Flash TWRP and Root[PROPER]
/* * Your warranty is now void. * * I am 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...
forum.xda-developers.com
Why i dont need to relock when use MI Flash??? tbh im always leaved as default without problem...
View attachment 5804157
Also everytime i made a fresh install im used "advanced wipe" in recovery and delete everything system too
withouth problem!!!
Witch custom rom u suggest is the best to be installed? usually im prefer stock rom because the custom rom has some bugs so i prefer stay on stock rom but if there is some custom rom that is better then stock why not!!!
Click to expand...
Click to collapse
I recommend using the "clean all" option. If you use "clean all and lock" you'll relock your bootloader, and won't be able to flash fastboot ROMs anymore (for example). You won't be able to root either.
If you prefer stock ROMs use them. The matter of which custom ROM is better is an never ending discussion.
Compass.
Compass Linux said:
I recommend using the "clean all" option. If you use "clean all and lock" you'll relock your bootloader, and won't be able to flash fastboot ROMs anymore (for example). You won't be able to root either.
If you prefer stock ROMs use them. The matter of which custom ROM is better is an never ending discussion.
Compass.
Click to expand...
Click to collapse
Im use clean and lock because then im unlock with MI UNLOCK!!!
Im updated again magisk to v25. 2 because i wanna test when i get no sim card icon if it show my imei and it show it but with the difference that instead of write IMEI its write HEX IMEI...why???
Also i cant understand yet why if i update to last version i get no sim card icon???
roberto_1986 said:
Im use clean and lock because then im unlock with MI UNLOCK!!!
Im updated again magisk to v25. 2 because i wanna test when i get no sim card icon if it show my imei and it show it but with the difference that instead of write IMEI its write HEX IMEI...why???
Also i cant understand yet why if i update to last version i get no sim card icon???
Click to expand...
Click to collapse
If you relock your bootloader you'll have to wait 168 hours to unlock it again. Your choice.
I've never seen the message "HEX IMEI" and I don't know what that means.
If you flashed the MIUI fastboot ROM you wanted and the SIM card icon is there, you're doing something that's removing it. You have to find out what that is and avoid doing it again.
Compass.
Compass Linux said:
If you relock your bootloader you'll have to wait 168 hours to unlock it again. Your choice.
I've never seen the message "HEX IMEI" and I don't know what that means.
If you flashed the MIUI fastboot ROM you wanted and the SIM card icon is there, you're doing something that's removing it. You have to find out what that is and avoid doing it again.
Compass.
Click to expand...
Click to collapse
Hey!!!
Nope only the first time u have to wait 168 hr!!! then u unlock without wait!!!
Yhea im flash the ROM as fastboot with MI flash
OK seems like we didnt find it why i have this problem...well then later im try to update magisk only to v24.3
and how about magisk app? i can upgrade to last version??
Ty anyway for your support >,<
roberto_1986 said:
Hey!!!
Nope only the first time u have to wait 168 hr!!! then u unlock without wait!!!
Yhea im flash the ROM as fastboot with MI flash
View attachment 5804445
OK seems like we didnt find it why i have this problem...well then later im try to update magisk only to v24.3
and how about magisk app? i can upgrade to last version??
Ty anyway for your support >,<
Click to expand...
Click to collapse
I think you are able to unlock immediately because your device is still linked to your Mi account. If you try unlocking a new device the 168 hours should kick in.
I don't see how Magisk is related to your problem, but try Magisk 24.3 instead of 25.2 and see if that works. This is the first time I've heard of Magisk affecting the Sim card icon.
Compass.
Compass Linux said:
I think you are able to unlock immediately because your device is still linked to your Mi account. If you try unlocking a new device the 168 hours should kick in.
I don't see how Magisk is related to your problem, but try Magisk 24.3 instead of 25.2 and see if that works. This is the first time I've heard of Magisk affecting the Sim card icon.
Compass.
Click to expand...
Click to collapse
Ok im just finished to make fresh install + ROOT with magisk v24.3 and magisk app v25.2 + safity net 2.3.1 (passed)
and seems like everything working just fine appart i cant change name at magisk...when i try it tell me failed....
also when i was updating all app my messages app keep crashing but after update no more.
- Why i cant hide magisk by changing name?
- Im hide google play services with deny list but if i reboot my phone he gone from deny list and i need to put again...
appart google play services witch file i need to put in deny list???
ty so much!!!
roberto_1986 said:
Ok im just finished to make fresh install + ROOT with magisk v24.3 and magisk app v25.2 + safity net 2.3.1 (passed)
and seems like everything working just fine appart i cant change name at magisk...when i try it tell me failed....
also when i was updating all app my messages app keep crashing but after update no more.
- Why i cant hide magisk by changing name?
- Im hide google play services with deny list but if i reboot my phone he gone from deny list and i need to put again...
appart google play services witch file i need to put in deny list???
ty so much!!!
Click to expand...
Click to collapse
Why are you mixing Magisk 24.3 and Magisk 25.2? Use only Magisk 24.3! Then verify SafetyNet is passing using YASNAC (Google Play Store).
The fact that you can't spoof Magisk neither permanently add Google Play Services to the Deny List seems to indicate that your bootloader isn't unlocked or SafetyNet isn't passing.
You'll keep having issues by mixing Magisk versions.
Compass.
Compass Linux said:
Why are you mixing Magisk 24.3 and Magisk 25.2? Use only Magisk 24.3! Then verify SafetyNet is passing using YASNAC (Google Play Store).
The fact that you can't spoof Magisk neither permanently add Google Play Services to the Deny List seems to indicate that your bootloader isn't unlocked or SafetyNet isn't passing.
You'll keep having issues by mixing Magisk versions.
Compass.
Click to expand...
Click to collapse
Idk wtf its going on here...im checked now on Settings > Additional Settings > Developer Options and seems like my device isnt unlocked but if i reboot my phone on the bottom tell me is unlocked...i pretty sure my phone was unlocked...
I never had all this issues....i will try again to root or i will buy new phone...>,>
roberto_1986 said:
Idk wtf its going on here...im checked now on Settings > Additional Settings > Developer Options and seems like my device isnt unlocked but if i reboot my phone on the bottom tell me is unlocked...i pretty sure my phone was unlocked...
I never had all this issues....i will try again to root or i will buy new phone...>,>
Click to expand...
Click to collapse
The easiest way to know if any Xiaomi phone has an unlocked bootloader is by turning it on and looking at the top for a opened padlock () during the initial boot process.
Compass.
Compass Linux said:
The easiest way to know if any Xiaomi phone has an unlocked bootloader is by turning it on and looking at the top for a opened padlock () during the initial boot process.
Compass.
Click to expand...
Click to collapse
Yhea on RN8P its on bottom!
The weird thing is on opening tell me its unlocked but on Developer Options no because when its unlocked i cant add MI account account and its on grey so u cant click it!
instead when its locked i can add mi unlock like in this screenshot below...
k
Later i will try again....ty for your effort on help me.
Spoiler: lll
lll
roberto_1986 said:
Yhea on RN8P its on bottom!
The weird thing is on opening tell me its unlocked but on Developer Options no because when its unlocked i cant add MI account account and its on grey so u cant click it!
instead when its locked i can add mi unlock like in this screenshot below...
kView attachment 5804923
Later i will try again....ty for your effort on help me.
Click to expand...
Click to collapse
You're using an older MIUI so the location of the open padlock is different? OK. I haven't used anything based on MIUI 11.x for a while.
Perhaps because you have an unlocked bootloader it doesn't allow you to select the Unlock Status neither add a MIUI account (probably due to security reasons).
Compass.
Compass Linux said:
Spoiler: lll
lll
You're using an older MIUI so the location of the open padlock is different? OK. I haven't used anything based on MIUI 11.x for a while.
Perhaps because you have an unlocked bootloader it doesn't allow you to select the Unlock Status neither add a MIUI account (probably due to security reasons).
Compass.
Click to expand...
Click to collapse
OK this time i will try to upgrade to A10...maybe its just time to upgrade to new version also A10 its a mature version because now there is A11!!! i will test and let u know!
Ok @Compass Linux
Im finished now to install A10 - V12.0.5.0.QGGEUXM on my phone!!!
Also finaly im installed with no problem both magisk / app 25.2 with no problem!!!
But i noticed 2 problem...
- The first its i renamed magisk to hide but now i have 2 app...1 renamed + magisk...im reboot phone but app still there
so i can uninstall normal magisk???
- The second problem its on modules...I have this module (.core) blank...usually i received this on A9 when i tryed to install last version on magisk that cause me a problem so i can delete this module???
whats its that???
Again i wanna tell u ty so much for all your effort to help me^^
EDIT:
- Fixed the magisk app cloned while im tryed to hide.
- Got another problem...im successfully unloked bootloader but after reboot my phone "Unlock OEM" its not anymore
grey like its happened when i was on A9....what did u think its the problem???
Also when i reboot my phone on up side i can see the lock its unlocked.
roberto_1986 said:
Ok @Compass Linux
Im finished now to install A10 - V12.0.5.0.QGGEUXM on my phone!!!
Also finaly im installed with no problem both magisk / app 25.2 with no problem!!!
But i noticed 2 problem...
- The first its i renamed magisk to hide but now i have 2 app...1 renamed + magisk...im reboot phone but app still there
so i can uninstall normal magisk???
View attachment 5805113
- The second problem its on modules...I have this module (.core) blank...usually i received this on A9 when i tryed to install last version on magisk that cause me a problem so i can delete this module???
whats its that???
View attachment 5805117
Again i wanna tell u ty so much for all your effort to help me^^
Click to expand...
Click to collapse
I don't know what this module is.
Compass.