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
Related
So geohot announced last night that he has rooted 4.4.2, its specifically tailored to the S5's with locked bootloaders, but he states it should work on all devices with a kernel older than June 5th (Our latest update, NE6, is dated May 19th).
He also states it shouldnt trigger knox, but he makes no guarantees.
Its also just an apk which is awesome.
Im feeling bold today, so if nobody else gets around to testing it on the tmobile note 3, ill be testing it in a few hours on my lunch.
http://towelroot.com/
http://forum.xda-developers.com/showthread.php?t=2783157
RESTATING OBVIOUS: this isn't my work, all credit goes to geohot, I'm merely linking to it as our phone meets the criteria and should theoretically work works.
UPDATE
Worked without a hitch... Just make sure to install the latest SuperSU (download the zip from chainfires website, and extract SuperSU.apk from common)... It's newer than the play store version.
SuperSU zip:
http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
The play store version of SuperSU has been updated and should work fine now.
1) run towel root ("make it rain"), it will reboot automatically
2) immediatly after reboot, install latest SuperSU (before you run it)
3) run SuperSU, let it update binaries, it will freeze on disabling knox
4) reboot again, run again, disable knox will be successful.
IT DID NOT TRIP KNOX
Just to clarify, this device is a virgin (never been rooted before) running the latest NE6 update...
Restoring to stock (/w nothing tripped) should be as easy as flashing the stock NE6 tar via odin.
UPDATE 2
I can confirm by reply's here, as well as actually trying it on a friends phone that is is not working for NB4, but works perfectly fine on NE6
{
"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 SM-N900T using Tapatalk
starnostar said:
So geohot announced last night that he has rooted 4.4.2, its specifically tailored to the S5's with locked bootloaders, but he states it should work on all devices with a kernel older than June 5th (Our latest update, NE6, is dated May 19th).
He also states it shouldnt trigger knox, but he makes no guarantees.
Its also just an apk which is awesome.
Im feeling bold today, so if nobody else gets around to testing it on the tmobile note 3, ill be testing it in a few hours on my lunch.
http://towelroot.com/
http://forum.xda-developers.com/showthread.php?t=2783157
RESTATING OBVIOUS: this isn't my work, all credit goes to geohot, I'm merely linking to it as our phone meets the criteria and should theoretically work.
Click to expand...
Click to collapse
Let me know if it works for you I've got the galaxy s5 for T-Mobile but I'm not sure I want to try it until I've got proof on T-Mobile devices
Worst case scenario if I were to try and right now what would happen
Sent from my SM-N900T using xda premium
Pajar0913 said:
Worst case scenario if I were to try and right now what would happen
Click to expand...
Click to collapse
you would trip knox and/or have to flash a stock tar... ill be testing it in about 30 min.
Keep us updated
There might be bugs since it was intended for the S5. It's not tailored for our devices. Geohot says the same thing. And he didn't say it shouldn't trip knox. Just threw it out there that it didn't trip it for him.
Sent from my SM-N900T using XDA Premium 4 mobile app
Moved to OP
I can confirm that it works following starnostar's instructions.
Sent from my SM-P600 using Tapatalk
So I can go install a custom recovery thereafter
Hello and this is kind of newbee-ish I am an ATT customer looking (actually getting delivery tomorrow) for an N900T - i.e. Tmo Note - which needs to be sim ulocked after it is rooted and then a custom recovery - and then to my fav - an CM ROM.
I think if I do flash a custom recovery - it will trip knox - Just asking here to see if that's true or get some more insights into my plans for the device.
Thanks for reading so far.
Not working 4.4.2 / first time root
I tried rooting following starnostar instructions and it didn't work. The binaries that SuperSU need wouldn't download after the towelroot initial reboot. Tried installing SuperSU (entire directory in file provided) from the phone/SD card with the same result. Did an uninstall of everything a few times. Reboot -> install tr -> reboot -> install SuperSU provided from phone/SD card (either) -> run SuperSU or reboot and run SuperSU. Tried with other super user apps (ChainsDD and ClockworkMod). Same result.
The only things I can think to do are disable Lookout, factory restart the phone or start then stop KNOX (I disabled it a little while back). Any ideas?
Awesome news!!! Being new to rooting in general I'll wait until I see a bit more feedback, but very excited there is a new Knox friendly root available. Thanks for posting!
Sent from my SM-N900T using xda app-developers app
gitofgits said:
I tried rooting following starnostar instructions and it didn't work. The binaries that SuperSU need wouldn't download after the towelroot initial reboot. Tried installing SuperSU (entire directory in file provided) from the phone/SD card with the same result. Did an uninstall of everything a few times. Reboot -> install tr -> reboot -> install SuperSU provided from phone/SD card (either) -> run SuperSU or reboot and run SuperSU. Tried with other super user apps (ChainsDD and ClockworkMod). Same result.
The only things I can think to do are disable Lookout, factory restart the phone or start then stop KNOX (I disabled it a little while back). Any ideas?
Click to expand...
Click to collapse
How did you disable knox without root? if you rooted in the past, maybe residual files left over are causing issues. If this is the case (that you had rooted in the past), maybe a fresh "never-rooted" odin flash is in order.
Another possibility is I used root checker to verify root before installing supersu (i never opened the app, just accepted the prompt), maybe a root prompt must be triggered and granted to complete the process.
starnostar said:
How did you disable knox without root? if you rooted in the past, maybe residual files left over are causing issues. If this is the case (that you had rooted in the past), maybe a fresh "never-rooted" odin flash is in order.
Another possibility is I used root checker to verify root before installing supersu (i never opened the app, just accepted the prompt), maybe a root prompt must be triggered and granted to complete the process.
Click to expand...
Click to collapse
Yeah, I was thinking that I needed a prompt too. I've never attempted root with this phone.
As to KNOX, I just turned it off/disabled it after I did a reset as I did with a handful of things. I was one of the unfortunate few who had to reset after the 4.4.2 upgrade. I did reinstall KNOX, but there was no change. reboot -> install tr - make it ra1n -> reboot -> check - no root access -> install SU - no SU binary to install. Or little variations on that. I'll just wait around a few weeks to see if anyone figures out a solution or factory reset and try again.
Bummer too, I was really looking forward to getting Call Master back. :/
On ne6. Rooted fine and knox 0x0.
Worked for me, Almost forgot the step to (download the zip from chainfires website, and extract SuperSU.apk from common) got errors updating the SuperSU files but its working now!
Help!! Getting error on SuperSU
On Note 3 Tmobile NB4, never rooted, installed Towelroot, rebooted, and installed superSU, when tried to load Super User I get this message,
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
Please help!!
zemaj800 said:
Worked for me, Almost forgot the step to (download the zip from chainfires website, and extract SuperSU.apk from common) got errors updating the SuperSU files but its working now!
Click to expand...
Click to collapse
shijocj said:
On Note 3 Tmobile NB4, never rooted, installed Towelroot, rebooted, and installed superSU, when tried to load Super User I get this message,
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
Please help!!
Click to expand...
Click to collapse
I initially tried on NB4 but had the same issue, updated to NE6 with Samsung's Kies app and then tried again and it worked fine.
stpinc said:
I initially tried on NB4 but had the same issue, updated to NE6 with Samsung's Kies app and then tried again and it worked fine.
Click to expand...
Click to collapse
I was on NB4 and getting Kies and updating the firmware fixed it for me. Thanks!
Wow, finally a working root solution for our Note 3!
Kies is installed and as soon as I charge my phone, I will update to NE6 and give this a shot!
So u got it working did it trip Knox for u
Sent from my SM-N900T using XDA Free mobile app
Q&A for Prerooted Stock Images
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Prerooted Stock Images. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Ever since I installed the recovery menu and the latest pre-rooted FW I've had a few issues I can't seem to pin to anything. For one thing, now every time I reboot I get the Amazon boot splash screen followed by the updating software screen, as though it's installing a new update, which it isn't. Is this normal?
If so I can live with that, but installing the custom FW has now broken the google play store and Aptoide, leaving me sideloading everything. I've tried uninstalling and reinstalling all of the associated APKs but it doesn't make a difference at all. Starting either market just momentarily starts the app just to immediately close it and kick me back to the launcher. Any ideas here?
Trying to get late October 2014 Netflix working on FireTV
I updated my fireTV to bueller-51.1.4.0_514006420-rooted and the new Netflix didn't play videos- some DRM issue. I downgraded to bueller-51.1.3.0_513011820-rooted and had to install Netflix. It was the old version and played fine. I took the Netflix app from 51.1.4.0 before I downgraded:
com.netflix.ninja-1.apk MD5: ae2a3cfa57a599e6bd13069d9928b725
It doesn't install on 51.1.3.0:
>adb install com.netflix.ninja-1.apk
1506 KB/s (8039804 bytes in 5.211s)
pkg: /data/local/tmp/com.netflix.ninja-1.apk
Failure [INSTALL_FAILED_OLDER_SDK]
malacoid said:
I updated my fireTV to bueller-51.1.4.0_514006420-rooted and the new Netflix didn't play videos- some DRM issue. I downgraded to bueller-51.1.3.0_513011820-rooted and had to install Netflix. It was the old version and played fine. I took the Netflix app from 51.1.4.0 before I downgraded:
com.netflix.ninja-1.apk MD5: ae2a3cfa57a599e6bd13069d9928b725
It doesn't install on 51.1.3.0:
>adb install com.netflix.ninja-1.apk
1506 KB/s (8039804 bytes in 5.211s)
pkg: /data/local/tmp/com.netflix.ninja-1.apk
Failure [INSTALL_FAILED_OLDER_SDK]
Click to expand...
Click to collapse
Interesting. Amazon must have bumped their SDK version. I'm going to see if I can easily disable the forced upgrade so the old Netflix might still work on the new version. In the end, I need to figure out what's wrong though.
The "Amazon Kernel Not Patched" error is normal. It's telling you that the image contained a stock Amazon kernel therefore it was not patched. Did you install the alternate Amazon AppStore by chance? I do not have the alternate Amazon AppStore installed and I just upgraded three firetv's in the last 30 minutes. One was on the previous "broken" version so the new Netflix was already installed. It connected immediately and I played a video. I proceeded to upgrade my other two. They both prompted me through the download and installation of the new Netflix. I had to re-enter my credentials in each but they worked.
edit
Doh I tried to reply to the pre-rooted dev thread but it got put here. An admin can delete this.
I am on the 51.1.4.0 prerooted fw and want to update to 51.1.4.1, but I have some hiccups in my current verison. (free time not working, su won't launch) Should I try to fix those issues before attempting to update or will updating hopefully fix those issues??
I have version 51.1.1.0_user_511070220 and have installed Boot Menu with custom recovery 6.0.5.1.4. Can I update custom rom 51.1.4.1_514013920 without installing Pre-Rooted ROM version 51.1.4.0 first? Thanks.
vinhdt1 said:
I have version 51.1.1.0_user_511070220 and have installed Boot Menu with custom recovery 6.0.5.1.4. Can I update custom rom 51.1.4.1_514013920 without installing Pre-Rooted ROM version 51.1.4.0 first? Thanks.
Click to expand...
Click to collapse
NO...
Nov 21, 2014 - Added 51.1.4.1_514013920+fixed (md5sum: 4429327daeed0df852731d81fa9b1f54)
Starting with this update, this requires FireTV Boot Menu.
You also must ensure you have already flashed 51.1.4.0.
Click to expand...
Click to collapse
Y314K said:
NO...
Click to expand...
Click to collapse
Thanks. Also, do I need to remove the Boot Menu and lock the bootloader? Or can I leave it and just install Pre-Rooted ROM version 51.1.4.0 first, reinstall the Boot Menu and then install Pre-rooted 51.1.4.1_514013920? Thanks again.
vinhdt1 said:
Thanks. Also, do I need to remove the Boot Menu and lock the bootloader? Or can I leave it and just install Pre-Rooted ROM version 51.1.4.0 first, reinstall the Boot Menu and then install Pre-rooted 51.1.4.1_514013920? Thanks again.
Click to expand...
Click to collapse
I think once you partially unlock the bootloader you leave it like that.
Y314K said:
I think once you partially unlock the bootloader you leave it like that.
Click to expand...
Click to collapse
Thanks Y314K, I have successfully installed 51.1.4.0. How do I know if my partially unlock bootloader is still there and can I proceed to install the Boot Menu or do I need to check to make sure the bootloader is still unlock first? Thanks.
vinhdt1 said:
Thanks Y314K, I have successfully installed 51.1.4.0. How do I know if my partially unlock bootloader is still there and can I proceed to install the Boot Menu or do I need to check to make sure the bootloader is still unlock first? Thanks.
Click to expand...
Click to collapse
I don't think PreRooted FW flashing will get rid of any of that. If you can still go into the CWM custom recovery 6.0.5.1.4 which requires the unlock bootloader then your good.. I thought you mentioned you already had the boot menu installed ??
Hopefully you have CWM 6.0.5.1.4a installed insead of 6.0.5.1.4...
Firmware upgrade.
I have couple questions...
When upgrading to newer pre-rooted firmware, should I clear cache in recovery?
Another one... I'm on 51.1.4.0, rooted, boot menu, recovery... If I want to start over what is the best way? What needs to be cleared (data in recovery?), reset option in FTV launcher? Will recovery and boot menu stay?
how can you delete the prerooted images that are on the SD card? I cant find them in Es File explorer.
I can see them here in CWM though...
{
"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"
}
Dolphin Browser crashes on Prerooted 51.1.4.0_514006420
I have prerooted 51.1.4.0_514006420 version on my FireTV and I want to report that Dolphin Browser will crash if Jetpack is turned on. Is this also happening on the latest prerooted version ?
Dolphin Browser with Jetpack was working fine on prerooted version 51.1.3.0_513011820
lowbee said:
I have prerooted 51.1.4.0_514006420 version on my FireTV and I want to report that Dolphin Browser will crash if Jetpack is turned on. Is this also happening on the latest prerooted version ?
Dolphin Browser with Jetpack was working fine on prerooted version 51.1.3.0_513011820
Click to expand...
Click to collapse
You should probably complain to the Dolphin developers...
mroneeyedboh said:
how can you delete the prerooted images that are on the SD card? I cant find them in Es File explorer.
I can see them here in CWM though...
Click to expand...
Click to collapse
You would need to do it from ADB or the way I do it is I use ES File Explorer or a similar app. If it's a Google Store app you might need a mouse to control it right. Since they are touch based. Holding the button press for a while over a file will give you the option to move/copy/delete it.
Just wondering if prime videos stopped working for anyone else?
I am on the latest pre rooted and tried to watch a video last night and it errored out.
At work now and can't give the exact error message but it was a dialog that I believe said unknown error has occured.
Worked fine a few days ago.
snorkel01 said:
Just wondering if prime videos stopped working for anyone else?
I am on the latest pre rooted and tried to watch a video last night and it errored out.
At work now and can't give the exact error message but it was a dialog that I believe said unknown error has occured.
Worked fine a few days ago.
Click to expand...
Click to collapse
I was watching prime last night just fine.
rbox said:
I was watching prime last night just fine.
Click to expand...
Click to collapse
OK, found out what the issue was. I was unaware but if XBMC/KODI is left suspended in the background, i.e. you hit the home button on the remote without exiting XBMC/KODI the
prime video does not work. I can do it everytime.
Not a big deal I guess.
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
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.
I was using Xiaomi.eu weekly rom in my mi 11x, then i reverted to stock miui 12.0.4 through fastboot, now in play store device is not certified is showing, beacuse of this some apps like netflix can't be downloaded from play store, so how to fix and get the device certified.
Find your device’s GSF Device-ID. There’s a simple app on the Play Store called ‘Device ID‘, but since you obviously can’t access the Play Store I have mirrored the application here.
Open the app and copy the code in the second line called “Google Service Framework (GSF).”
Go to this webpage.
Enter your GSF Device-ID in the “Android ID” box.
After you tap “Register”, your registered ID should appear on the page.
{
"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"
}
Keno_I said:
Find your device’s GSF Device-ID. There’s a simple app on the Play Store called ‘Device ID‘, but since you obviously can’t access the Play Store I have mirrored the application here.
Open the app and copy the code in the second line called “Google Service Framework (GSF).”
Go to this webpage.
Enter your GSF Device-ID in the “Android ID” box.
After you tap “Register”, your registered ID should appear on the page.
Click to expand...
Click to collapse
Ok I'll try this method.
Get back to me if it works!
Are you rooted? Every time this happens I make sure I have the play store enabled in MagiskHide then I clear data for the Play Store and the next time I open the Play Store it says certified.
ajsmsg78 said:
Are you rooted? Every time this happens I make sure I have the play store enabled in MagiskHide then I clear data for the Play Store and the next time I open the Play Store it says certified.
Click to expand...
Click to collapse
Yeah I overlooked root
ajsmsg78 said:
Are you rooted? Every time this happens I make sure I have the play store enabled in MagiskHide then I clear data for the Play Store and the next time I open the Play Store it says certified.
Click to expand...
Click to collapse
But he did say that he reverted the rom from fastboot so...
Keno_I said:
But he did say that he reverted the rom from fastboot so...
Click to expand...
Click to collapse
But he did not say everything he did after reverted from fastboot.
pl1992aw said:
But he did not say what he did after reverted from fastboot !!!
Click to expand...
Click to collapse
True but.....
I'm not rooted and not using any custom recovery, phone is in stock condition, i tried device id registration method but it didn't worked, play store still showing device not certified
Vipul9254 said:
I'm not rooted and not using any custom recovery, phone is in stock condition, i tried device id registration method but it didn't worked, play store still showing device not certified
Click to expand...
Click to collapse
Is your OEM unlock option in Developer Options enabled by any chance?
ajsmsg78 said:
Is your OEM unlock option in Developer Options enabled by any chance?
Click to expand...
Click to collapse
Yes it is enabled and it can't be disabled untill i relock the bootloader
Vipul9254 said:
I'm not rooted and not using any custom recovery, phone is in stock condition, i tried device id registration method but it didn't worked, play store still showing device not certified
Click to expand...
Click to collapse
Try to reflash the ROM...maybe it was an error when u flashed it first time....just saying
See if you can renew certificate as mentioned here:
https://xiaomi.eu/community/threads/info-widevine-l1-support.61064/
Read the reply as well:
https://xiaomi.eu/community/threads/info-widevine-l1-support.61064/post-606155
Root with magisk and install this module.
https://github.com/kdrag0n/safetynet-fix/releases/download/v1.1.1/safetynet-fix-v1.1.1.zip
Same happened to me as well after stock rom with miflash.
It is because of bootloader unlock.
Select Magisk Hide from magisk options.All good after that.
Vipul9254 said:
I was using Xiaomi.eu weekly rom in my mi 11x, then i reverted to stock miui 12.0.4 through fastboot, now in play store device is not certified is showing, beacuse of this some apps like netflix can't be downloaded from play store, so how to fix and get the device certified.
Click to expand...
Click to collapse
If you want to stay on a stock rom try this.
Download the Fastboot Rom here(update after with OTA if necessary)
use this tool
Dont relock the bootloader.
________________________
If the play store is still not certified (Xiaomi fault) use Magisk.
Kenora_I said:
Find your device’s GSF Device-ID. There’s a simple app on the Play Store called ‘Device ID‘, but since you obviously can’t access the Play Store I have mirrored the application here.
Open the app and copy the code in the second line called “Google Service Framework (GSF).”
Go to this webpage.
Enter your GSF Device-ID in the “Android ID” box.
After you tap “Register”, your registered ID should appear on the page.
Click to expand...
Click to collapse
not working device ID box remains red as if the ID is not correct then when I click register it says it is
hexisg said:
Root with magisk and install this module.
https://github.com/kdrag0n/safetynet-fix/releases/download/v1.1.1/safetynet-fix-v1.1.1.zip
Same happened to me as well after stock rom with miflash.
It is because of bootloader unlock.
Select Magisk Hide from magisk options.All good after that.
Click to expand...
Click to collapse
what version of TWRP should I use for this?
hexisg said:
Root with magisk and install this module.
https://github.com/kdrag0n/safetynet-fix/releases/download/v1.1.1/safetynet-fix-v1.1.1.zip
Same happened to me as well after stock rom with miflash.
It is because of bootloader unlock.
Select Magisk Hide from magisk options.All good after that.
Click to expand...
Click to collapse
done that and it passed safety net but still says device uncertified any help would be great really don't want to lock the bootloader
deleted