hi guys, help me how to play the game using the ps3 stick, I already root using Magisk. but the sixasis controller application still doesn't work. is there a solution??
custom roms seem to lack the required libraries
if you're on MIUI, you need to run the apl while in permissive SE Linux mode. It should work
salzzz said:
custom roms seem to lack the required libraries
if you're on MIUI, you need to run the apl while in permissive SE Linux mode. It should work
Click to expand...
Click to collapse
Oh my bro..thanks you.. I don't know why I am very happy..yeah it's work:laugh::laugh:
aribz said:
Oh my bro..thanks you.. I don't know why I am very happy..yeah it's work:laugh::laugh:
Click to expand...
Click to collapse
Hi, I am having the same problem OP had, and apparently he was able to solve this.
I feel like I am praying to understand ancient scrolls here, but what is APL and permissive SE linux mode? My Mi Pad 4 is running MIUI 10.2, I think CN version.
I have rooted the device with magisk on the latest version - 18.1 and 7.0
Nevermind, found it: at the moment I have managed to make it work by setting permissive mode through Terminal:
0. Open terminal emulator (root required).
1. Check status by typing 'getenforce', if it says permissive, you already have it set to permissive. Don't read any further.
2. Type 'su', press enter. Terminal will run in super user.
3. Type 'setenforce 0'. It will set SELinux to permissive mode.
4. Check status by 'getenforce'.
Related
I am currently on the NC5 build, and I have root. I have safestrap working, I can login as su on a terminal, and I have used the SELinux mod app to change the SELinux status to 'permissive"
I verified this with
Code:
#getenforce
Permissive
Still, Debian-Kit cannot find SU. Trying to unpack it returns the ASH error mentioned in thread 2475803
Linux Deploy also fails with the mount point error others have mentioned.
Is this related to Knox? I have been thinking about switching to T-Mobile for the unlocked bootloader so I could install a different kernel, but I should be able to proceed with the permissive status, right?
If this is a problem with Knox, then I suppose that any current Samsung device will not allow chroot Linux or Debian-Kit?
I got a Samsung to use as a full Linux OS on my Desktop - this is a deal breaker for me.
FWIW, I had been on NK1, but I could not get SELinux to change to permissive, so I downgraded to NC5.
zekeb said:
I am currently on the NC5 build, and I have root. I have safestrap working, I can login as su on a terminal, and I have used the SELinux mod app to change the SELinux status to 'permissive"
I verified this with
Code:
#getenforce
Permissive
Still, Debian-Kit cannot find SU. Trying to unpack it returns the ASH error mentioned in thread 2475803
Linux Deploy also fails with the mount point error others have mentioned.
Is this related to Knox? I have been thinking about switching to T-Mobile for the unlocked bootloader so I could install a different kernel, but I should be able to proceed with the permissive status, right?
If this is a problem with Knox, then I suppose that any current Samsung device will not allow chroot Linux or Debian-Kit?
I got a Samsung to use as a full Linux OS on my Desktop - this is a deal breaker for me.
FWIW, I had been on NK1, but I could not get SELinux to change to permissive, so I downgraded to NC5.
Click to expand...
Click to collapse
Your kernel doesn't support loop devices. That's why debian wont boot. No way around it.
Putting your current device on TMO wont unlock the bootloader FYI.
npjohnson said:
Your kernel doesn't support loop devices. That's why debian wont boot. No way around it.
Putting your current device on TMO wont unlock the bootloader FYI.
Click to expand...
Click to collapse
Thank you!!!!! This has been so confusing, because Debian-Kit reports that I do have loop mount ability. But this explains why there is no linux on android solution that works.
I was planning on buying a tmo S4, which has the unlocked bootloader. Will look for a stock kernel for tmo S4 that allows loop mount - do you know if such a thing exists?
CM kernel seems to allow it, as another reported success with it, but I don't want to use it because I want to dock my phone using MHL -> HDMI + USB OTG on my desktop at work. I don't think CM supports the 11-pin function of the S4 which is why I bought this in the first place!
zekeb said:
Thank you!!!!! This has been so confusing, because Debian-Kit reports that I do have loop mount ability. But this explains why there is no linux on android solution that works.
I was planning on buying a tmo S4, which has the unlocked bootloader. Will look for a stock kernel for tmo S4 that allows loop mount - do you know if such a thing exists?
CM kernel seems to allow it, as another reported success with it, but I don't want to use it because I want to dock my phone using MHL -> HDMI + USB OTG on my desktop at work. I don't think CM supports the 11-pin function of the S4 which is why I bought this in the first place!
Click to expand...
Click to collapse
I think CM odes support the S4s dock mode... Check over on that forum. CM does have loop mount. Id bet anything there's a kernel out there to do loop support on stock though.
Hi! Is there any way I could install V4A into Fire Nexus Rom? It says it can't install the drivers necessary for V4A I already installed busybox but to no avail...
Anyone?
myjellyrollsoul said:
Hi! Is there any way I could install V4A into Fire Nexus Rom? It says it can't install the drivers necessary for V4A I already installed busybox but to no avail...
Click to expand...
Click to collapse
myjellyrollsoul said:
Anyone?
Click to expand...
Click to collapse
I am not familiar with the intricacies of V4A. If the ROM needs customization to handle V4A then it's not going to happen as Fire Nexus is, by design, bare-bones AOSP. Many audio enhancers (eg: Dolby) need to be flashed which is risky/impossible with this device unless you have an unlocked bootloader. If it's a straight install but missing the dev may consider it - albeit unlikely given waning support/interest for this discontinued device.
Davey126 said:
I am not familiar with the intricacies of V4A. If the ROM needs customization to handle V4A then it's not going to happen as Fire Nexus is, by design, bare-bones AOSP. Many audio enhancers (eg: Dolby) need to be flashed which is risky/impossible with this device unless you have an unlocked bootloader. If it's a straight install but missing the dev may consider it - albeit unlikely given waning support/interest for this discontinued device.
Click to expand...
Click to collapse
Hi thank you for the prompt reply I just figured how to make it work as I was browsing through the official thread of V4A. You just have to uncheck Mount namespace separation under /settings/security from SuperSU, reboot then the drivers will install successfully.
myjellyrollsoul said:
Hi thank you for the prompt reply I just figured how to make it work as I was browsing through the official thread of V4A. You just have to uncheck Mount namespace separation under /settings/security from SuperSU, reboot then the drivers will install successfully.
Click to expand...
Click to collapse
Cool - good info. Might give it a whirl as I have been less than impressed with 3rd party Dolby options for this device.
Hey guys! It's me again... sorry So, I finally was able to make NoozXoide works with Spotify. It truly improves the sound, even with local files, different from others eq... But no, it's not enough. So, I decided to give up. I need Viper4Android, and only it.
When I was doing some research about sound mods without root, I remember finding an article which described how to install Viper4Android without rooting the device. I remember, though, it was necessairy to change SELinux Policies to permissive. But I can't find this article anywhere... So I figured it out it would be easier to ask you guys here. Also, I need to know if it's working with Android Nougat... I use Moto G4 Plus, just fyi.
Can you please help me?
(Sorry, I was in doubt about where should I post it)
http://stackoverflow.com/questions/...or-permissive-mode-in-android-4-4-4-and-above
I know how to change the SELinux, cause in most places they recomend an Selinux Changer... My doubt is, after changing Selinux, all I have to do is install Viper4Android..? Or do I have to install it before changing...? Do I have to keep it in permissive after installing the driver...?
Thanks!
Install with Permissive, but on every boot you need permissive
Won't work. Viper requires root in order to install its driver.
No root = no driver, regardless of what selinux is set to.
There are ways to flash the driver through a custom recovery, BUT, and I may be wrong, I believe you also need root in order to change selinux mode.
As far as I know, Viper won't work in enforcing mode, so even if you flash the driver, you'd still need root in order to change selinux for Viper to actually work.
How about installing a custom recovery, flashing the v4a driver and then try to set selinux to permissive with ADB?
Or just get magisk, there is a V4A systemless module.
Correct me if I'm wrong but If we just got magisk then we wouldnt need it without root because flash magisk and your rooted. No?
asafroid said:
Correct me if I'm wrong but If we just got magisk then we wouldnt need it without root because flash magisk and your rooted. No?
Click to expand...
Click to collapse
pretty much but you still need a custom recovery to flash Magisk and for most phones you need a unlocked bootloader to flash a custom recovery
Hi guys I am trying to load v4a2.7.2.1 with magisk version 23, on android 7.0 on An lg v530 gpad x2 8.0 plus. I have checked and I have root. I also have busybox installed via magisk and I installed selinux switch and used it to switch to permissive mode. V4a just keeps trying to install the driver and reboot every time I load it up. Can anyone guide me as to how to make v4a work? I've spent days on xda trying to find a way to make this work. Way to confusing with all the old versions of v4a like 2.5.*.* and using it with newer Android versions with and without magisk. So far nothing I've found works obviously or I wouldnt be posting. Any help would be appreciated.
polygaryd said:
Hi guys I am trying to load v4a2.7.2.1 with magisk version 23, on android 7.0 on An lg v530 glad x2 8.0 plus. I have checked and I have root. I also have busybox installed via magisk and I installed selinux switch and used it to switch to permissive mode. V4a just keeps trying to install the driver and reboot every time I load it up. Can anyone guide me as to how to make v4a work? I've spent days on xda trying to find a way to make this work. Way to confusing with all the old versions of v4a like 2.5.*.* and using it with newer Android versions with and without magisk. So far nothing I've found works obviously or I wouldnt be posting. Any help would be appreciated.
Click to expand...
Click to collapse
Oh and there is no twrp version for this device for me to try to install the rootless driver which I did download to try to install manually.
Anyone with knowledge about this out there that can help?
I too have the same issue so can we put our heads together and fix it? Im using mtk 6753t octa core agptek t06s mp4 player I patched my recovery.img with universal mtk twrp patcher but no dice booting to recovery. By the way I'm rooted and tried everything.
I'm reading this... https://www.apkmirror.com/apk/team-dewitt/viper4android-fx/viper4android-fx-2-7-2-1-release/
I couldn't find any simple instructions for rooting so hopefully this helps someone.
I'm assuming you've already unlocked your bootloader. If not, download the deep testing app (there are various apks on xda e.g. from here). Then submit the application (it took me a few minutes to get approved) then use the app to reboot into the bootloader, then run command fastboot flashing unlock. I don't believe the deep testing app works on android 12 yet so you may have to downgrade to android 11 to unlock your bootloader.
If your bootloader is unlocked you can update to android 12 (though it isn't necessary to root). If your gt isn't offering you the latest version you can download a recent version on this thread and then use "local install" in the update menu.
Next, download twrp from:
https://github.com/qiurigao/RMX2202
The latest version is twrp-3.6.0-V2.img
And download magisk from:
https://github.com/topjohnwu/Magisk/releases
The latest version is Magisk-v24.3.apk
Put your gt into fastboot mode by powering off, then hold the power and volume down buttons together until you're in the fastboot screen.
Then run command:
fastboot boot "twrp-3.6.0-V2.img"
Do NOT try installing twrp as I've read it can cause issues.
This should boot twrp (it will be in chinese but it doesn't matter).
Rename the magisk apk to a zip e.g. Magisk-v24.3.zip
Now run:
adb push Magisk-v24.3.zip /data/Magisk-v24.3.zip
Then:
adb shell "twrp install /data/Magisk-v24.3.zip"
Now you can adb reboot and you should be rooted!
Good luck.
Thank you so much this guide. i've successfully rooted my device. but how can i run the banking apps ? because magisk hide not working. thanks in advance.
Fjsdfjasdasd said:
Thank you so much this guide. i've successfully rooted my device. but how can i run the banking apps ? because magisk hide not working. thanks in advance.
Click to expand...
Click to collapse
Having the same issue. Unfortunately no banking apps working for me.
F0Xie said:
Having the same issue. Unfortunately no banking apps working for me.
Fjsdfjasdasd said:
Thank you so much this guide. i've successfully rooted my device. but how can i run the banking apps ? because magisk hide not working. thanks in advance.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Look in Magisk settings, enable Zygisk (beta), enable enforce denylist, add apps to the denylist then install universal safetynet fix module from github and reboot device.
Update: now we can use deep testing app to unlock bootloader while using Realme UI 3
Unlocking bootloader and rooting the device will format data?
Unlocking bootloader - yes
Thanks, this worked!
Also, really DO NOT install Magisk by clicking on "Install" in the TWRP interface, it can brick the device. Just don't touch the phone while installing Magisk, only use the fastboot and adb commands.
F0Xie said:
Update: now we can use deep testing app to unlock bootloader while using Realme UI 3
Click to expand...
Click to collapse
still working on last update?
robertaalves said:
still working on last update?
Click to expand...
Click to collapse
Yes, absolutely. It will work in Android 12 no matter how many updates you'll get. But will not work in Android 13.
Thanks man, it worked like a charm.
F0Xie said:
Yes, absolutely. It will work in Android 12 no matter how many updates you'll get. But will not work in Android 13.
Click to expand...
Click to collapse
This method works with the Android 13 update.
Use the same twrp image (twrp-3.6.0-V2.img) but use the latest Magisk (25.2)
I did this with 2 devices and had no Problems with root. Had to reinstall the Magisk App afterwards though.
(FWIW I did not remove root before updating to Android 13, that doesn't seem to be a problem)
Hiiii, I'm thinking of buying this phone so I got 2 questions; 1) are there any custom roms available? From my little to none research, I've only found gsi, andd after my failed attempts, hearing the word gsi brings a bad taste, lol. Aanndd 2) is there any development/general discussion group about this device on telegram?
Gordin said:
This method works with the Android 13 update.
Use the same twrp image (twrp-3.6.0-V2.img) but use the latest Magisk (25.2)
I did this with 2 devices and had no Problems with root. Had to reinstall the Magisk App afterwards though.
(FWIW I did not remove root before updating to Android 13, that doesn't seem to be a problem)
Click to expand...
Click to collapse
can you open the bootloader in a13? or you need to open it before update?
Hm, to unlock bootloader, you need the right deep testing apk for your system version. I haven't looked into if there exists one for Android 13, but I would just downgrade the phone to a patch that works. I think I unlocked mine by downgrading to stock, and then installing the latest system update that is still Android 11. Sounds like there is a working Android 12 too, but I haven't tested it. Having to downgrade doesn't really matter to me, because unlocking will wipe all user data anyway. (Of course if you find a deep testing apk that is meant for 13, you can also try that, I just don't know if one exists)
alex61194 said:
can you open the bootloader in a13? or you need to open it before update?
Click to expand...
Click to collapse