Develop Bugs

Just rooted my G2, got a few questions

I've got my G2 rooted with S-off and now I am just curious as to how I get the latest Cyanogen rom on it as well as whether or not i need to factory reset my phone or not.
thanks for any of the help

I just did it. Go to that thread where the rom is and there is a wiki link that tells u how to do it.
I'm by far not experienced with this stuff and have done it once before and it was very easy. I mostly used the wiki link.
From my permarooted overclocked HTC G2 with cyanogen 7 nightly via XDA app

I recommend you read and understand all the information regarding rooting, rom manager, flashing roms, how to restore nandroid in case things don't go correctly..
Always so a nandroid before flashing a new rom
Sent from my HTC Glacier using XDA App

I've rooted before on my G1 so i know about recovery, rom manager, and nandroid backups just was wondering if anything has changed since the G1, but I just figured it out, i'm currently running cyanogenmod 6.1.1
I am curious as to what cyanogen mod nightly is
Also I heard the best overclocking app for root users was setcpu, how is it? and does it work on the G2?

This iz not Evan said:
I've rooted before on my G1 so i know about recovery, rom manager, and nandroid backups just was wondering if anything has changed since the G1, but I just figured it out, i'm currently running cyanogenmod 6.1.1
I am curious as to what cyanogen mod nightly is
Also I heard the best overclocking app for root users was setcpu, how is it? and does it work on the G2?
Click to expand...
Click to collapse
The CyanogenMod Nightlies are daily (nightly) updates to the ROM, that include the latest changes to it, most of which are experiments or small corrections. I'd only recommend flashing these if you have an interest in being on the bleeding edge of the ROM. For most people, the RC1 and then later on the stable CM7 mod will be best for them.
As far as installing CM7 (probably the RC1) goes, be sure to do a FULL data, cache, dalvik wipe before flashing. It just makes things much easier and lets you start off fresh while lowering the possibility of issues. It is very easy to simply flash through ROM manager and check the box for "wipe data+cache". I also recommend checking the "google addon" box as well, so you can get your Google Apps at the same time. If you don't you'll have to flash them separately later.
And as always, do a nandroid backup before you flash!
SetCPU is definitely the most widely used to regulate overclocks/underclocks and have profiles set, but CM7 also has a native overclocking system built into CMSettings that does basically the same thing.

Re-installing su on Jelly Bean after removing it with Smelkus

Hi guys, I made a mistake while playing with Smelkus (Ra-supersonic-v4.3-smelkusMOD).
While in recovery, I went into the Developer Menu and entered on the "Install eng (unguarded) su" option, which after rebooting, disabled root access from my EVO. Now, every time I try to get root access I get a segmentation fault error.
I'm using MazWoz 4.2.1 Jelly Bean B4.
Short of re-flashing the ROM, Is there anything I can do to regain root access? I really got it working the way I want it, so I don't want to wipe everything if I can avoid it.
Thanks! Oh, by the way, I made no back up ...(I know, my mistake).

Have done the same thing trying to get SU to work properly with a rom. Easiest way is just to restore a nandroid backup.

Edit: Sorry, earlier it was in the dev section.

connman said:
Have done the same thing trying to get SU to work properly with a rom. Easiest way is just to restore a nandroid backup.
Click to expand...
Click to collapse
Unfortunately, I did not make a nandroid backup for this ROM (been using it for only 2 days!).
Anyway, here's what I did so far:
1)I "Pushed" the Superuser.apk found on the MozWoz Rom to my EVO using "adb."
And it did not work. The superuser application installed properly on my device because I can launch it fine from the app drawer, but it does not give me root privileges.
Any other suggestions?
There's gotta be a way to solving this. Exactly, what does the "Install eng (unguarded) su" option on Smelkus do anyway? Does anybody know?

Krazy4evo said:
Unfortunately, I did not make a nandroid backup for this ROM (been using it for only 2 days!).
Anyway, here's what I did so far:
1)I "Pushed" the Superuser.apk found on the MozWoz Rom to my EVO using "adb."
And it did not work. The superuser application installed properly on my device because I can launch it fine from the app drawer, but it does not give me root privileges.
Any other suggestions?
There's gotta be a way to solving this. Exactly, what does the "Install eng (unguarded) su" option on Smelkus do anyway? Does anybody know?
Click to expand...
Click to collapse
http://androidsu.com/superuser/
Download the ARM zip, flash in recovery. You also need the binary and not just the apk. That's why it still didn't work. If it still fails after this then clean wipe and flash ROM again.
Sent from my Galaxy Nexus using xda premium

the.emilio said:
http://androidsu.com/superuser/
Download the ARM zip, flash in recovery. You also need the binary and not just the apk. That's why it still didn't work. If it still fails after this then clean wipe and flash ROM again.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I flashed the ARM zip files with varying results, but none gave me root access.
Anyway, the only way I gained access was to reflash the ROM....
I hope this saves time for any one who's ran into this issue. Nothing but flashing the ROM seemed to work.

Krazy4evo said:
I flashed the ARM zip files with varying results, but none gave me root access.
Anyway, the only way I gained access was to reflash the ROM....
I hope this saves time for any one who's ran into this issue. Nothing but flashing the ROM seemed to work.
Click to expand...
Click to collapse
Glad that you got it figured out.
Like the.emilio said, there are two parts to the SU. You had just downloaded the apk (the app) but that needs the binary (instructions) to work.
I would have thought that the ARM files would have done this.
At any rate, you're back and working, so that's good news. My advice would be to now go make a nandroid backup. That way as you discover and play with this new rom, if you break something, you can easily return to a known "good" state without too much hassle.
Saved my bacon more than once over the years.

connman said:
Glad that you got it figured out.
Like the.emilio said, there are two parts to the SU. You had just downloaded the apk (the app) but that needs the binary (instructions) to work.
I would have thought that the ARM files would have done this.
At any rate, you're back and working, so that's good news. My advice would be to now go make a nandroid backup. That way as you discover and play with this new rom, if you break something, you can easily return to a known "good" state without too much hassle.
Saved my bacon more than once over the years.
Click to expand...
Click to collapse
I barely ran the ROM for 2 days before realizing I had not made a backup -lol!
My guess is that Smelkus was intended to be used with GB, so it created ROM root privileges that were different from later version of su? Maybe Smelkus needs to do a kernel check before enabling certain options?
Anyway, it's great to be back. And yes, I made a backup shortly after getting everything to work.

Krazy4evo said:
I barely ran the ROM for 2 days before realizing I had not made a backup -lol!
My guess is that Smelkus was intended to be used with GB, so it created ROM root privileges that were different from later version of su? Maybe Smelkus needs to do a kernel check before enabling certain options?
Anyway, it's great to be back. And yes, I made a backup shortly after getting everything to work.
Click to expand...
Click to collapse
Hmm. I'm running Smelkus in Provision/Jellyvision, which is a JB rom (great rom, by the way and very stable on our Evo). In fact, smelkusmod was recommended by the developer of Provision/Jellyvision as the recovery. It's based on AmonRA, so should be pretty compatible regardless.

Install unguarded su installs some old superuser hack as the su binary. Not sure what it was for, but it had a purpose at some point. The regular "Install or fix su & superuser" choice installs a normal (but quite old) version of the superuser.apk and binary and sets their permissions. Both should be avoided at this late stage of Evo use. I think Diablo updated to SuperSU on his version, but if you need to install Superuser (koush), SuperSU, or SuperUser it would be better to use the latest version of their respective flashable zips.
Recovery is entirely separate from the ROM and kernel you are running, so it doesn't matter if you have Jelly Bean, ICS, GB or even Android at all for that matter. All recoveries - stock, CWM, TWRP, RA, etc - are basically a mini-OS with their own kernel and init. It boots and runs the program, recovery. Recovery then executes built in commands and scripts included with it. When a ROM developer recommends a recovery, they are just promoting what they like. Any recovery can do the job in their own manner.
In your case, after installing that unguarded su, you could have done any of the following steps to recover:
Flashed a current Superuser zip if it was already on your phone
adb pushed one and flashed
Booted up the ROM, downloaded one, go back to recovery and flash
Flashed the ROM and gapps again, wiped cache and dalvik and rebooted
Restored backup if available

[Q] Help Me Choose a ROM?

Probably not the first, won't be the last. I rooted my N7 with WugFresh root toolkit. But I can't choose a ROM. I would prefer close to vanilla with the advanced power menu that includes reboot and bootloader if possible. I have TWRP for recovery.
I've looked at Kangakat, CleanROM and Sinless. If one of them is better over the other that would be fine. Or another ROM. I want the latest build (KOT49H) and OTA potential.

scottad said:
Probably not the first, won't be the last. I rooted my N7 with WugFresh root toolkit. But I can't choose a ROM. I would prefer close to vanilla with the advanced power menu that includes reboot and bootloader if possible. I have TWRP for recovery.
I've looked at Kangakat, CleanROM and Sinless. If one of them is better over the other that would be fine. Or another ROM. I want the latest build (KOT49H) and OTA potential.
Click to expand...
Click to collapse
Everyone's taste is different. You should flash them all to find out which one suits you best.

Sounds like all you need is xposed and 1 module.

I did install Xposed and a few modules. Also added a different kernel. Elemental-X
Sent from my Nexus 7 using Tapatalk

i'd recommend OmniROM, close to stock, stable, nice features, OTA support, latest build (KVT49L) not (KOT49H) check out this thread: http://forum.xda-developers.com/showthread.php?t=2626831

Or if you want a clean build which your only requirement is the advanced shutdown menu, CleanRom has it with no add-ons. Its clean, fast and stable.
Sent from my LG-P880 using xda app-developers app

The author of cleanrom said its abandoned now :/
But its still my favorite rom . Fast and stable
Sent from my Nexus 7 using xda premium

scottad said:
Probably not the first, won't be the last. I rooted my N7 with WugFresh root toolkit. But I can't choose a ROM. I would prefer close to vanilla with the advanced power menu that includes reboot and bootloader if possible. I have TWRP for recovery.
I've looked at Kangakat, CleanROM and Sinless. If one of them is better over the other that would be fine. Or another ROM. I want the latest build (KOT49H) and OTA potential.
Click to expand...
Click to collapse
You don't need another rom for that, just Xposed and the GrafityBox plugin
.

Ed V said:
You don't need another rom for that, just Xposed and the GrafityBox plugin
.
Click to expand...
Click to collapse
That's pretty much what I did XPosed and then a plugin. Didn't use Gravity but am considering it!

Personally I've Installed Cyanogenmod Nightlies, with ElementalX Kernel. CM ROMs are close to stock, but with some cool stuff. you can activate advanced power menu in CM in Developers section. The latest Nightlies are stable and smooth, and the battery life is correct.
Don't forget, unlocking your device will do a full wipe :laugh:
Sincerely

Speaking of CM11, what isn't stable? Like what problems have you came across? If any that is cx
Sent from my Nexus 7 using Tapatalk

vparres said:
Personally I've Installed Cyanogenmod Nightlies, with ElementalX Kernel. CM ROMs are close to stock, but with some cool stuff. you can activate advanced power menu in CM in Developers section. The latest Nightlies are stable and smooth, and the battery life is correct.
Don't forget, unlocking your device will do a full wipe :laugh:
Sincerely
Click to expand...
Click to collapse
CM is about as far from stock as one can get.

BioDesigner48 said:
Speaking of CM11, what isn't stable? Like what problems have you came across? If any that is cx
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I experienced some bootloops, lags, even some fonctions broken (Wifi, proxymity sens, etc) in some nightlies. I experienced it on my friend's Galaxy S2, but i never experienced something like that with my N7 on "stock" CM11. In fact, i bought my N7 recently

look into omnirom...
I am not going to say any ROM is better than others because all ROMs have their pros and cons. To find out which ROM you like best you will have to try and experiment for yourself.
Nexus devices have a wonderful recovery manager which is TWRP which stands for Team Win Recovery Project. Nexus devices also have a great tool which works with TWRP recovery manager, this tool is call MultiROM manager. What multirom manager does is it allows you to install multiple ROM's on your Nexus device without harming or altering your stock ROM.
In order to use multirom you need to first patch your stock ROM with the kexec-hardboot patch. That can be done very easily. First thing you need to do is root your device. If you are going to root your device i would also recommend unlocking the tablets bootloader. This can all be done with WuGFresh's NRT (nexus root toolkit). Here is a link for NRT -> http://www.wugfresh.com/nrt/
After you have your tablet rooted and bootloader unlocked then install TWRP recovery, again all of this can be done with the Nexus Root Toolkit.
After that you can go to the google play store and download the app MultiROM Manager. This is the easiest way to install multirom. Here is the link for multirom manager -> https://play.google.com/store/apps/details?id=com.tassadar.multirommgr
Again, if you don't have your stock kernel patched with the kexec-harboot patch you won't be able to boot multiple roms. You can patch your stock kernel with the kexec-harboot patch from multirom manager.
So once you have unlocked bootloader + root + twrp recovery manager + kexec harboot patch for stock kernel (from stock rom) + multirom manager you have the freedom to do whatever you want to your tablet without harming or modifying your stock rom.
As for a custom ROM i would recommend that you look into OmniROM. It has gotten good reviews and i personally love it. I find it very stable and it also has a really nice feature with multi-windows and split screens.
Another thing you might be interested in is look into "xposed framework" that allows you to customize your stock or custom rom by adding things like multi-windows or advanced reboot menu for example.
I hope this has been helpful...
If you get stuck on anything there is great documentation on rooting + twrp recovery manager here on xda or you can find great videos on youtube.com.
-droidshadow

droidshadow said:
I am not going to say any ROM is better than others because all ROMs have their pros and cons. To find out which ROM you like best you will have to try and experiment for yourself.
Nexus devices have a wonderful recovery manager which is TWRP which stands for Team Win Recovery Project. Nexus devices also have a great tool which works with TWRP recovery manager, this tool is call MultiROM manager. What multirom manager does is it allows you to install multiple ROM's on your Nexus device without harming or altering your stock ROM.
In order to use multirom you need to first patch your stock ROM with the kexec-hardboot patch. That can be done very easily. First thing you need to do is root your device. If you are going to root your device i would also recommend unlocking the tablets bootloader. This can all be done with WuGFresh's NRT (nexus root toolkit). Here is a link for NRT -> http://www.wugfresh.com/nrt/
After you have your tablet rooted and bootloader unlocked then install TWRP recovery, again all of this can be done with the Nexus Root Toolkit.
After that you can go to the google play store and download the app MultiROM Manager. This is the easiest way to install multirom. Here is the link for multirom manager -> https://play.google.com/store/apps/details?id=com.tassadar.multirommgr
Again, if you don't have your stock kernel patched with the kexec-harboot patch you won't be able to boot multiple roms. You can patch your stock kernel with the kexec-harboot patch from multirom manager.
So once you have unlocked bootloader + root + twrp recovery manager + kexec harboot patch for stock kernel (from stock rom) + multirom manager you have the freedom to do whatever you want to your tablet without harming or modifying your stock rom.
As for a custom ROM i would recommend that you look into OmniROM. It has gotten good reviews and i personally love it. I find it very stable and it also has a really nice feature with multi-windows and split screens.
Another thing you might be interested in is look into "xposed framework" that allows you to customize your stock or custom rom by adding things like multi-windows or advanced reboot menu for example.
I hope this has been helpful...
If you get stuck on anything there is great documentation on rooting + twrp recovery manager here on xda or you can find great videos on youtube.com.
-droidshadow
Click to expand...
Click to collapse
Thanks I was thinking bout omni ROM lol
sent from my LG Optimus L9 P769 v20h
I'm on YouTube (aSuperSaiyanG0D)

Rooted stock 28.0.A.8.251 ROM - looking for testers

I have successfully created a stock rooted ROM based on 28.0.A.8.251 Generic HK firmware
The ROM has the following features
Stock ROM with MyXperia app removed
Rooted with SuperSU on the /system partition
Custom kernel from latest 28.0.A.7 kernel- copyleft sources with SELinux in permissive mode and Sony RIC disabled
Deodexed and zip-aligned
Writeable external sdcard
Busybox
This ROM can be flashed using @ChrisJ951's command line TWRP.
I'm not yet ready to release it publicly but I am looking for a couple of beta testers. If you're a sophisticated user and you're willing to give it a go then send me a PM and I'll let you have a link to the download and some instructions for installation. The installation doesn't touch the userdata partition, so it's a non-wipe install, although I strongly recommend you update to the base firmware before installing the custom rom.

dl12345 said:
I have successfully created a stock rooted ROM based on 28.0.A.8.251 Generic HK firmware
The ROM has the following features
Stock ROM with MyXperia app removed
Rooted with SuperSU on the /system partition
Custom kernel from latest 28.0.A.7 kernel- copyleft sources with SELinux in permissive mode and Sony RIC disabled
Deodexed and zip-aligned
Writeable external sdcard
Busybox
This ROM can be flashed using @ChrisJ951's command line TWRP.
I'm not yet ready to release it publicly but I am looking for a couple of beta testers. If you're a sophisticated user and you're willing to give it a go then send me a PM and I'll let you have a link to the download and some instructions for installation. The installation doesn't touch the userdata partition, so it's a non-wipe install, although I strongly recommend you update to the base firmware before installing the custom rom.
Click to expand...
Click to collapse
Will this need me to unlock the bootloader?
Sent from my E6533 using XDA Free mobile app

angvil said:
Will this need me to unlock the bootloader?
Sent from my E6533 using XDA Free mobile app
Click to expand...
Click to collapse
Yes

Does it add anything over flashing the rom and then the rooted boot.img posted in the general forum?

ChrisJ951 said:
Does it add anything over flashing the rom and then the rooted boot.img posted in the general forum?
Click to expand...
Click to collapse
Yes, it's deodexed, zipaligned, SELinux in permissive mode, RIC disabled, busybox installed, write-enabled external SD card, adb insecure. I'll probably add some other things soon - Xposed is top of the list.

Does you think this can fix the over heating problem with some Z3+ devices? I hope so

dl12345 said:
I have successfully created a stock rooted ROM based on 28.0.A.8.251 Generic HK firmware
The ROM has the following features
Stock ROM with MyXperia app removed
Rooted with SuperSU on the /system partition
Custom kernel from latest 28.0.A.7 kernel- copyleft sources with SELinux in permissive mode and Sony RIC disabled
Deodexed and zip-aligned
Writeable external sdcard
Busybox
This ROM can be flashed using @ChrisJ951's command line TWRP.
I'm not yet ready to release it publicly but I am looking for a couple of beta testers. If you're a sophisticated user and you're willing to give it a go then send me a PM and I'll let you have a link to the download and some instructions for installation. The installation doesn't touch the userdata partition, so it's a non-wipe install, although I strongly recommend you update to the base firmware before installing the custom rom.
Click to expand...
Click to collapse
Got my Z3+ last night and about to unlock the bootloader so happy to give it a test and report back. I've seen the command line twrp link but might need some additional guidance on flashing your ROM, if you wouldn't mind.

lilloscar said:
Does you think this can fix the over heating problem with some Z3+ devices? I hope so
Click to expand...
Click to collapse
I doubt it. I've made no bug fixes. If there's a problem in the base ROM, the problem will exist in this ROM.

dl12345 said:
I have successfully created a stock rooted ROM based on 28.0.A.8.251 Generic HK firmware
The ROM has the following features
Stock ROM with MyXperia app removed
Rooted with SuperSU on the /system partition
Custom kernel from latest 28.0.A.7 kernel- copyleft sources with SELinux in permissive mode and Sony RIC disabled
Deodexed and zip-aligned
Writeable external sdcard
Busybox
This ROM can be flashed using @ChrisJ951's command line TWRP.
I'm not yet ready to release it publicly but I am looking for a couple of beta testers. If you're a sophisticated user and you're willing to give it a go then send me a PM and I'll let you have a link to the download and some instructions for installation. The installation doesn't touch the userdata partition, so it's a non-wipe install, although I strongly recommend you update to the base firmware before installing the custom rom.
Click to expand...
Click to collapse
OK, so far, everything seems to be working fine including LTE, WiFi, Bluetooth and NFC transferring of files between devices, Location, Sync, Google Play, System RW (ES File Explorer and AdAway worked), ExternalSD RW (Titanium Backup and SMS Backup & Restore worked), Camera and all other Sony apps seem to be working fine. I haven't made any phone calls yet though. TWRP also worked great - backup, wiping and installing all worked great.
Only slight niggles I've found so far are: Google Drive keeps popping up a blank grey/white screen for a split second - when trying to sync or access Play Store - and disappears and when setting up a Google account, a message pops up saying Google Play Services has stopped - even thought it works just fine. Oh and Google Maps didn't connect the first time but forcing a continue worked. Other than those 3 items, everything else seems to be working fine. However, once all apps are updated, they all work fine.
Currently testing 4K recording and it's just gone past 11 minutes .
Xposed also working as well as Greenify Experimental Features and it seems the 20MP Superior Auto is working. Xperia Xposed didn't work - I believe this is a general incompatibility matter and not restricted to this ROM - haven't tried anything else though
Thank you very much @dl12345 for your hard work. If you need any more testing, let me know.

My first initial thoughts are perfect. I haven't had any issue whatsoever. No problem with root, works with every app. Appreciate the work.
Skickat från min E6553 via Tapatalk

rjhellel said:
OK, so far, everything seems to be working fine including LTE, WiFi, Bluetooth and NFC transferring of files between devices, Location, Sync, Google Play, System RW (ES File Explorer and AdAway worked), ExternalSD RW (Titanium Backup and SMS Backup & Restore worked), Camera and all other Sony apps seem to be working fine. I haven't made any phone calls yet though. TWRP also worked great - backup, wiping and installing all worked great.
Only slight niggles I've found so far are: Google Drive keeps popping up a blank grey/white screen for a split second - when trying to sync or access Play Store - and disappears and when setting up a Google account, a message pops up saying Google Play Services has stopped - even thought it works just fine. Oh and Google Maps didn't connect the first time but forcing a continue worked. Other than those 3 items, everything else seems to be working fine. However, once all apps are updated, they all work fine.
Currently testing 4K recording and it's just gone past 11 minutes .
Xposed also working as well as Greenify Experimental Features and it seems the 20MP Superior Auto is working. Xperia Xposed didn't work - I believe this is a general incompatibility matter and not restricted to this ROM - haven't tried anything else though
Thank you very much @dl12345 for your hard work. If you need any more testing, let me know.
Click to expand...
Click to collapse
Which version of Xposed did you use? All the ones I tried only resulted in bootloops.

I used official xposed v73 sdk21 arm64.

Little note: You have to wipe dalvik cache before or after installing Xposed to prevent bootloop.
Latest Xposed has auto-wipe feature, but to make sure...

Could I test, just unlocked my bl last night

hello all this rom have lte band 38/2600 ? Or can be added? thx

Having a e6533 Dual. 266 firmware with unlocked bootloader. Would like to downgrade and test this rooted 251 ROM. Thank you.

I used to use xposed-v74-sdk21-arm64-dl12345-UNOFFICIAL-20150929.zip as from some post. Facing random reboot from time to time.
Last week, I need to reflash, I tried official xposed-v79-sdk21-arm64.zip. It works ... and the phone stay "no reboot" for one day. Then it starts again. I wipe cache and seems back to be more stable. My own feeling is thsi v79-sdk21 has less reboot issue, but still does.
---------- Post added at 16:35 ---------- Previous post was at 16:29 ----------
BTW, Sony has new update in Asia ...
28.0.A.8.272 Release: 1/9/2016 Still 5.0.2
I could not find anywhere to download full rom. Also not sure existing root/xposed will work or not.

Viper4Android Help

I've been trying to get Viper4Android driver installed but it keeps failing.
I've tested CM11 and Stock but no go when I hit install driver. I'm guessing it may have something to do with SE Linux as I have to set it to permissive but haven't had any luck with trying to change it as apps do not detect it.
Just looking to see if anyone else had any luck with the app on their Fire Phone?

I had it working without problems on CM-11. SELinux is disabled on that ROM, so no drawback here, no need to change anything...
Before I annoy you with more stories, tell us which file you used exactly to install V4A on your device.
I had to use SELinuxModeChanger on other devices (they used "enforcing") because they didn't offer a setting to change the SELinux mode.

Bingo Bronson said:
I had it working without problems on CM-11. SELinux is disabled on that ROM, so no drawback here...
Before I annoy you with more stories, tell us which file you used exactly to install V4A on your device.
Click to expand...
Click to collapse
I've reviewed the following thread
http://forum.xda-developers.com/showthread.php?t=2191223
I've tested 2.4.0.1 & 2.3.4.0 but can't install the driver. I have BusyBox Pro installed and running and reviewed the logs in SuperSU but i have no idea whats going on when I try the driver install.
Screenshot of Super SU Log: http://postimg.org/image/wdhvthr73/
I am currently back on CM-11 if you have any steps for me to try...

Kerrona said:
I have BusyBox Pro installed and running [...] I am currently back on CM-11 if you have any steps for me to try...
Click to expand...
Click to collapse
Hm, well that's interesting... I also used Stericson's busybox (non pro) and it worked right away... (I also used "ViPER4Android_FX_v2401_A4.x-A6.x.apk")
Maybe reinstall busybox... why isn't it able to find the "toolbox" / why is it calling the path with failsafe?
I see you have some security / privacy / permission tools running... can't really vouch for a hassle free install in such an environment.
You could try to flash this zip from safestrap recovery, this worked for me on other devices and the driver is already integrated, no need for a separate install from within the app.

This has something to do with superSU Binaries updated from normal method, if you have updated super su from playstore then you have to wipe the system partition reflash the rom and latest superSU zip. Otherwise you can flash the pre-build V4a zip as suggested above.

Thanks guys.
I got the driver installed and enabled now with the flash version.
Will probably wipe and start fresh and try the apk again.