I'm rooted using Franco kernel.
When I try and reboot through the Xposed Framework I get the following error message everytime:
sush:<stdin>[5]: /data/user/0/
de.robv.android/xposed.installer/cache/busybox-
xposed:not found
Reboot failed: Please use the device's normal reboot
function.
I have busbox installed. Not sure what else I'm doing wrong?
Same thing since CM initially out. I think this is a Superuser problem - it seems Xposed and some other apps can't get proper su rights on N6P. Other devices with CM don't have the problem.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
I get the same problem, systemless root, everything else is stock (apart from recovery). FYI I'm on Nexus 5x
Related
Can anyone tell me if Magisk works with our device (i have the d802) ?
See: http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
I'am worried about getting bootloader errors again (forgot the bump script before SuperSU :silly, so are there any pitfalls or things to watch out for?
My current ROM is CAF AOSPA,but i doubt that matters.
Thanks!
Have you successfully tried it ?
Works for me on D800 with the bump script
for me does not work. tried from stock from cm13. always secure boot error and have to uninstall magisk with twrp to boot. tried both root options. no way.
update! finally working
http://forum.xda-developers.com/showpost.php?p=68680286&postcount=2082
EDIT: I have verified supersu and busybox are installed and functioning as expected so looks like viper4android is the culprit.
ORIGINAL POST
Could someone who has installed viper4android on resurrection ROM in the past tell me what the steps are?
I have tried installing permissive mode, enforcing mode and using supersu for root instead but all have given error: driver failed to install: busybox not found.... yadadada.. you get the point.
thanks!
Same problem brother. RR 5.8.2
Viper4android 2.5.0.5
drago10029 said:
EDIT: I have verified supersu and busybox are installed and functioning as expected so looks like viper4android is the culprit.
ORIGINAL POST
Could someone who has installed viper4android on resurrection ROM in the past tell me what the steps are?
I have tried installing permissive mode, enforcing mode and using supersu for root instead but all have given error: driver failed to install: busybox not found.... yadadada.. you get the point.
thanks!
Click to expand...
Click to collapse
Why aren't you using A.R.I.S.E sound systems? It is viper4arise and is a lot better sound quality than viper4android.
Hi,
I originally posted this over at android central where I was told it is not possible to root a Moto G4, so I am trying here hoping for a different answer = )
I am attempting to install Cyanogenmod on my handset using the below guide:
Install_CM_for_peregrine (looks like I can't post link but that is the name of the page on he Cyanogenmod site)
I have unlocked the handset, copied the Cyanogenmod zip file to my sdcard, booted in recovery mode and attempted to install the zip package. At this point I get an error "E:failed to verify whole-file signature". I have tried both the stable and nightly build with the same result. Also when I have attempted to install SuperSU using the same process have received the same error so I suspect it is not a corrupted file.
I believe this is being caused by the signature check and to get around this have been following the below guide to disable signature check:
tutorial-how-to-disable-signature-check.html (name of the tutorial as can't post links)
When it comes to the step "Then find a option Called "Patch To Android", I don't see this option, and from what I understand this may be due to not having my phone rooted.
I have installed Kingo ROOT to resolve this but it failed to root the handset (error 0x1C5C33 if that means anything to anybody), checking the list of phones which Kingo ROOT can root, Moto is not one of them. What are the other options?
Any advice greatly appreciated. Thanks in advance.
Get rid of kingo. Look up android doctor on YouTube for unlock, root, twrp instructions. CM has a lot of bugs and isn't ready for daily use on this device. Slim roms has released their rom, it's CM based. I've been using it for a few days, and it's running smooth. There's a thread about it with the link on here. The only problem I've had was a boot loop when I try and flash xposed and supersu. There's a built in super user access in the settings, so supersu isn't necessary.
hooks024 said:
Get rid of kingo. Look up android doctor on YouTube for unlock, root, twrp instructions. CM has a lot of bugs and isn't ready for daily use on this device. Slim roms has released their rom, it's CM based. I've been using it for a few days, and it's running smooth. There's a thread about it with the link on here. The only problem I've had was a boot loop when I try and flash xposed and supersu. There's a built in super user access in the settings, so supersu isn't necessary.
Click to expand...
Click to collapse
Phone rooted, thanks!
Now to install SlimRoms
Strange, after rooting gained the below options in Lucky Patcher:
Signature Verification Status always True
Disable .apk Signature Verification
Disable signature verification in the package manager
Patch applied for all three, but then when I restart in recovery mode and attempt to install the SlimRoms zip still getting error "E:failed to verify whole-file signature".
I didn't patch anything. Just root, installed twrp, and flashed slim rom and gapps
hooks024 said:
I didn't patch anything. Just root, installed twrp, and flashed slim rom and gapps
Click to expand...
Click to collapse
Ah I see, did not realise you install the rom via twrp. It's installed now, awesome, thanks.
Hi guys,
thank you very much for the wonderful job everybody is doing here.
I have been using cyanogenmod 12.1 with parrotmod for a while now, with extreme pleasure.
I now would like to try out the new 12.1 compiled with uber toolkit and I was reading the PARROTMOD thread that advised to have the latest supersu installed first.
REQUIRES LATEST SUPERSU INSTALLED FIRST http://download.chainfire.eu/supersu-stable
EVEN IF YOUR ROM HAS BUILT IN ROOT LIKE CYANOGENMOD, TURN IT OFF IN SETTINGS, THEN FLASH SUPERSU!!
Click to expand...
Click to collapse
How can i do that? Where do I "turn it off"?
Do I have to
* flash cm 12.1 plus gapps
* initialize everything
* "turn off root"
* reboot to recovery
* flash SuperSU (I suppose in systemless mode, but I don't know, the installer should know what to do)
* flash PARROTMOD
Is it correct?
I have had difficulties to undertand the workings of this new "built-in" root access. Do I have to simply flash SuperSU over the freshly flased ROM? And why so? Isn't root "built-in"?
I already tried this on a Droid4, but the installer always spat out "failed" as last message. In any case installing SuperSU via Google Play always yelded a "you have to update the SuperSU binary" message.
Help. thanks
I think that "turn off root" in CM is in developer option (7-8 tap on build number). Procedure ordering is OK.
Sent from my Nexus 7 using Tapatalk
I found out what the author was talking about. Most cyanogen mod Roma have built-in SuperSU. In order to have Parrot Mod working you have to start the ROM, go to apps, settings, DISABLE SuperSU, restart to recovery, flash SuperSU, flash Parrot Mod and you're good to go. I'm going to put SOLVED on the post
I have rooted the device, and currently using Nougat RR ROM. But ViperDD is not working properly on device. Busybox also installed, the driver status shows Abnormal. Any Solution for it.
Uninstall Viper driver, reboot and then go to /system/vendor/etc and rename audio_effects.conf as audio_effects.conf.bak, go back to Viper app and try to install the driver or just check the driver status, should work with that
uday_kruk said:
I have rooted the device, and currently using Nougat RR ROM. But ViperDD is not working properly on device. Busybox also installed, the driver status shows Abnormal. Any Solution for it.
Click to expand...
Click to collapse
I would also check that your kernel is set to permissive, not enforcing. Heard that causes problems as well.
Also, you might like to install SuperSU from XDA rather than using the inbuilt CM root, as it appears to resolve the Abnormal error you're seeing. (credit: https://plus.google.com/communities/104675617308252943432)
The stable SuperSU is herehttps://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703. I've installed the TWRP version of SuperSU on my XT1642 Plus on RR 5.8.0 24/01/2017 build (after making a backup in TWRP) and flashed Viper4Arise (i think it's based on Viper4Android), which works well
uday_kruk said:
<snip> Any Solution for it.
Click to expand...
Click to collapse
The Arise Sound System zip flash works much better:
https://forum.xda-developers.com/and...earch-t3379709
But they leave out the critical step of modifying the arise_customize.prop file and placing it in internal storage
BEFORE you flash (SMH).
http://www.droidviews.com/install-ar...d-mod-android/
-G
If you use Magisk, ViPER4Android works flawlessly on nougat ROMs using the ViPER4Android for Magisk v14 module found within the downloads section of Magisk Manager, just install and reboot, nothing more required.