Develop Bugs

few questions before I root the KFHD8932GB

Hello, I've just bought my gf the 8.9 32gb version and she's not keen on the overlay UI and the lack of stuff on amazons market so she's asked me to root it.
1) If I root it, can I get it back to default state without showing that its previously been rooted? (any insuring later)
2) If you install the Play store, what device does the store think you have in order to install apps/games etc?
3) its just updated itself, am I right in thinking it cannot be rooted from this latest software? is downgrading easy?
4) Will we lose the things that are already on it? (Full wipe)
Thanks

Andyokane said:
Hello, I've just bought my gf the 8.9 32gb version and she's not keen on the overlay UI and the lack of stuff on amazons market so she's asked me to root it.
1) If I root it, can I get it back to default state without showing that its previously been rooted? (any insuring later)
2) If you install the Play store, what device does the store think you have in order to install apps/games etc?
3) its just updated itself, am I right in thinking it cannot be rooted from this latest software? is downgrading easy?
4) Will we lose the things that are already on it? (Full wipe)
Thanks
Click to expand...
Click to collapse
There's been no change to update methods, the bin4ry method, option 2 has always worked. If you look @ lizzard30's SteriROM 1.2 thread, you'll end up by-passing the whole rooting process, end up rooted, w/android market & more installed. Just make sure you adb drivers are properly installed: Windows 8 will definitely block installation of unsigned drivers, and Windows 7 a bit too--google search disabling driver signature enforcement for the OS your installing computer uses if it's Windows.
As part of the install process, you'll deregister from amazon. All your programs you've installed will be wiped, so if it ain't part of the of the install package you'd have to reinstall. You can select to wipe your SDCARD, but that isn't necessary. Music and documents should still be there.
If you're going Gi Joe this and root, install busybox, then android market, that's kool. You'll need bin4rys root method to root, get busybox installer from 1mobile market website, enable installation of unknown programs. You want the installer for after rooting--install it, open it, install busybox. Then you'll need kindle fire first aid. Don't use KFFA to root or install busybox. Install busybox, it's required to use KFFA. Use KFFA to install market first, then market apps if you'd like.
Good luck! Oh, if you don't deregister and use SteriROM and go medieval instead, visit application manager and wipe data for kindle reader, amazon vod, and silk. Maybe a few other amazon apps ... otherwise not all your stuff will show up.

I've completed every step and everything went perfect but now i've finished and rebooted im not stuck on the first KindleFire orange logo and it goes no further

Andyokane said:
I've completed every step and everything went perfect but now i've finished and rebooted im not stuck on the first KindleFire orange logo and it goes no further
Click to expand...
Click to collapse
SteriROM? Bin4ry? If you need help, pm me, I can send you my email to google chat or something to figure it out. Lemme know

4iiiidnerd said:
SteriROM?
Click to expand...
Click to collapse
??>>

ive tried the whole process now about 5 times, and it boot loops when I try install Twrp recovery/img any ideas??

Andyokane said:
ive tried the whole process now about 5 times, and it boot loops when I try install Twrp recovery/img any ideas??
Click to expand...
Click to collapse
so, you never get past "Fix the red screen"? and are unable to install TWRP. were there any errors when you installed the ADB drivers? error message do not mean everything is working good
It'd be nice if someone else had input on the TWRP install ... which I haven't done yet.
you might want to post on the steriROM thread (check for sim circumstances)
---
I looked at Hashcode's thread about twrp installation:
http://forum.xda-developers.com/showthread.php?t=2128175
notice step 4.5--your Kindle fire would have 8.3.1 on it, you will likely need to download the file and install in fastboot like Hashcode suggests

4iiiidnerd said:
so, you never get past "Fix the red screen"? and are unable to install TWRP. were there any errors when you installed the ADB drivers? error message do not mean everything is working good
It'd be nice if someone else had input on the TWRP install ... which I haven't done yet.
you might want to post on the steriROM thread (check for sim circumstances)
---
I looked at Hashcode's thread about twrp installation:
http://forum.xda-developers.com/showthread.php?t=2128175
notice step 4.5--your Kindle fire would have 8.3.1 on it, you will likely need to download the file and install in fastboot like Hashcode suggests
Click to expand...
Click to collapse
Didnt seem to get any errors. Going to try the StariRom method today and see how that does thanks.

[Q] "Unfortionately superuser has stopped" Error messege PLZ HELP

Hello to all,
I recently rooted my sgs3 sph-L710 v4.3 and am experiencing some problems. Whenever I try to open superusers it automatically closes, and I receive a notification saying, "security notice an attempt to access a secure area on your phone without authorization has been blocked." After doing some research online I discovered that the 4.3 version is protected by KNOX. Online sources state that in order to defeat the KNOX system you must update supersu, but I am not sure how to do that. Whenever I download supersu from the Google play store there is no option to update it. I would really appreciate any help thanks.

kingart93 said:
Hello to all,
I recently rooted my sgs3 sph-L710 v4.3 and am experiencing some problems. Whenever I try to open superusers it automatically closes, and I receive a notification saying, "security notice an attempt to access a secure area on your phone without authorization has been blocked." After doing some research online I discovered that the 4.3 version is protected by KNOX. Online sources state that in order to defeat the KNOX system you must update supersu, but I am not sure how to do that. Whenever I download supersu from the Google play store there is no option to update it. I would really appreciate any help thanks.
Click to expand...
Click to collapse
Have you checked to make sure you haven't lost root? When you install an app from Google play, you get the latest version.
sent from my GS3

Also, have you actually opened up the SuperSU app? You need to open it up (not just download it) so that it will prompt you about disabling Knox, and it might also prompt you to update the binaries. And which custom recovery are you using? If need be, you can flash the SuperSU zip from recovery, and if you are using Philz Touch (HIGHLY recommended) there is an option to have it check for root before booting back into system.

I did it!!!
Mr. Struck said:
Also, have you actually opened up the SuperSU app? You need to open it up (not just download it) so that it will prompt you about disabling Knox, and it might also prompt you to update the binaries. And which custom recovery are you using? If need be, you can flash the SuperSU zip from recovery, and if you are using Philz Touch (HIGHLY recommended) there is an option to have it check for root before booting back into system.
Click to expand...
Click to collapse
Yes I finally got it to work I just re rooted the device and superuser was gone. However, i downloaded supersu and it prompted me to update, i did and I was able to bypass knox! I think it was a problem with the method I used to get my phone rooted the first time. The video tutorial I watched the first time told me to uncheck the 2 boxes that come prechecked on odin i believe one of them was auto reboot i cant recall the other one. Then I took out the battery of the phone and selected the root file through mod recovery mode and that was it. The second time around I left the boxes checked and my phone auto restarted. I then downloaded supersu updated,rebooted, and Visalia!!!
Thanks guys I appreciate the help.

Found a working root for 4.6.1

Greetings!
I was successfully able to root my US unlocked Fire Phone (on 4.6.1) by installing and running KingRoot 4.0!
KingRoot appears to work on other 4th gen Amazon devices as well!
http://forum.xda-developers.com/kindle-fire-hdx/general/to-root-4th-gen-amazon-device-t3104853
One caveat:
KingRoot installs KingUser as its superuser app, and KingUser appears to prevent the su binary from being overwritten.
Because of this, I have not yet been able to replace KingUser with SuperSU or similar.
Hopefully someone more knowledgeable can resolve this, but until then
I've opted to install the Xposed Framework and LightningWall module in order to block KingUser's network activity.
najoor has found a way to replace KingUser via adb:
najoor said:
Instructions for replacing Kinguser with SuperSU are posted in the general forum:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546
Click to expand...
Click to collapse
Also, hydromän pointed out that HDXPosed is working to enable widgets and block potential updates. Awesome!
hydromän said:
How to Block now Amazon Updates?
Fixed. Using xposed with hdxmodules. Now working all Launchers with Widgets and Updates Are disabled
http://forum.xda-developers.com/showthread.php?t=2618158
Click to expand...
Click to collapse

Granted! Root working!

z64 said:
Greetings!
I was successfully able to root my US unlocked Fire Phone (on 4.6.1) by installing and running KingRoot 4.0!
Everything seems to be working, however, I am not sure how safe KingRoot is actually.
KingRoot installs KingUser as its superuser app, and KingUser appears to prevent the su binary from being overwritten.
Because of this, I have not yet been able to replace KingUser with SuperSU or similar.
Maybe someone more experienced than myself could take a look at it.
Other than that, seems great.
Hope this bit of news helps!
Click to expand...
Click to collapse
Thanks z64 for the information about a working root for 4.6.1 (US Unlocked GSM) Fire Phone.
I would like to know if KingRoot 4.0 is really safe to use, and if will make a FULL or a PARTIAL root to the Amazon Fire Phone?
I also would like to know if after rooting, you will be able to go backward and UnRoot later the Fire Phone, to the default and normal original state?

z64 said:
Greetings!
I was successfully able to root my US unlocked Fire Phone (on 4.6.1) by installing and running KingRoot 4.0!
Everything seems to be working, however, I am not sure how safe KingRoot is actually.
KingRoot installs KingUser as its superuser app, and KingUser appears to prevent the su binary from being overwritten.
Because of this, I have not yet been able to replace KingUser with SuperSU or similar.
Maybe someone more experienced than myself could take a look at it.
Other than that, seems great.
Hope this bit of news helps!
Click to expand...
Click to collapse
Is KingRoot a PC based program or a APK file? I'm Google searching now, just wondering which you used.

http://androidxda.com/download-kingroot-application
Choose 4.0

does this survive a reboot? that would be great news =)

After rebooting root checker report" ROOT" but you are right superSU is not working actualy it got installed but the SU binary upgrade failed

Can I go backward and UnRoot later the FirePhone to Default/Normal Original State??
Please, can someone that has already Rooted their Fire-Phone, if after rooting would be able to go backward and UnRoot later the Fire Phone, to the default and normal original state?

ulises.rodriguez said:
Thanks z64 for the information about a working root for 4.6.1 (US Unlocked GSM) Fire Phone.
I would like to know if KingRoot 4.0 is really safe to use, and if will make a FULL or a PARTIAL root to the Amazon Fire Phone?
I also would like to know if after rooting, you will be able to go backward and UnRoot later the Fire Phone, to the default and normal original state?
Click to expand...
Click to collapse
I'm not sure what qualifies as a full or partial root; the bootloader is still locked, so no custom recovery or custom roms.
It is possible to unroot using the included KingUser app.
You have to uncheck "Backup Root permission" first to completely unroot it.
(Still haven't figured out how to replace KingUser with SuperSU while it's rooted.)
Viperise152 said:
Is KingRoot a PC based program or a APK file? I'm Google searching now, just wondering which you used.
Click to expand...
Click to collapse
I used the latest KingRoot 4 apk from kingroot.net/down
"KingRoot-4.0.0.233-release-201505071219_105001.apk"
drdoomgod said:
does this survive a reboot? that would be great news =)
Click to expand...
Click to collapse
It does survive reboot!
I just installed the Xposed Framework with LightningWall to control net access.

How to Block now Amazon Updates?
Fixed. Using xposed with hdxmodules. Now working all Launchers with Widgets and Updates Are disabled
http://forum.xda-developers.com/showthread.php?t=2618158

works !

Failed for me. Wouldn't install.
EDIT: Got it working!!
Sent from my SD4930UR using XDA Free mobile app

The question is what can we do with it now? Can we get rid of the lock screen and install a new settings apk??

TheDynamo said:
The question is what can we do with it now? Can we get rid of the lock screen and install a new settings apk??
Click to expand...
Click to collapse
Xposed framework is the first thing I did

Hi, i have the xposed framwork installed but not sure what to do with it lol

Instructions for replacing Kinguser with SuperSU are posted in the general forum:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546

Not sure why - but after following instruction (after rooting etc) tried to follow the guide for making phone look like normal android and thats when all hell broke loose on my phone. Unresponsive bottom button, wiget's not loading, super su showing nothing then refreshing a while later showing apps in there etc.
Kinda killed my phone so going to factory reset and start again.

This is great! I got the now launcher to work, although I'm not exactly sure how. I tried the supersu replacement and only made it to steps 6 and 7 mostly because I couldn't understand what exactly I was supposed to do, so step 8 didn't work and I'm still using the kingsu. I then d/l the now launcher and the google (search) apps, tried to run it a couple of times with no luck. Then force stopped the home app, restarted, and I was given the choice to use the now launcher.

Its easy. If u have root, convert Google Now Launcher and Google Search with Titanium Backup to a System App... And you can Choose Google Now Launcher.

This is great. I was able to fix my play store/services issues by changing my build.prop to nexus 5 after rooting. Awesome!

Disabling Knox on Tab S 8.4 4G

I'm brand new to this website, and have only signed up because I cannot find a solution for this problem. I have always used the forum to get answers, but never though to join! My Galaxy Tab S 8.4 4G T705Y was put through the CF-Auto-Root method, and no a glitch at all. Very smooth. By the way I checked the ChainFire website to make sure I was using the latest. When my device started up I noticed, as I have done before with my Nexus phones, that SuperSU has been added. Good Sign!
But when I open SuperSU I was prompted to update the Binary. Then I pressed 'continue', used the 'normal' method, and waited. It then asked me if I would like to Disable Knox. Yes I would! FAILED TO DISABLE KNOX. Shut down SuperSU. Unhappy Face. As you can see at this point, I am not very up to speed with my rooting knowledge.
So then I decided to select the 'never' option to updating SuperSU, and still it failed to update the binary, I'd say due to Knox stopping it from gaining access.
So my pickle is this: I can't update SuperSU because Knox will not allow me to use SuperSU. I cannot simply hit yes to disabling Knox in SuperSU, as that didn't work for me. I also tried finding something called Knox on my tablet and it seems to be very elusive. I tried updating SuperSU on Play Store also, but to no avail!
I am also unable to use any third party app to do so as I need to grant them access in SuperSU before they can begin! And around I go...
There is a guide here http://forum.xda-developers.com/showthread.php?t=2540761 but it's not for my device so I'm a bit hesitant to start trying random things, as my device is working great atm!
Any info or help would be greatly appreciated!

Look in the android development section for my updated builds of cf_autoroot and flash that.
If you still get issues flash supersu v2.49 with twrp.

ashyx said:
Look in the android development section for my updated builds of cf_autoroot and flash that.
If you still get issues flash supersu v2.49 with twrp.
Click to expand...
Click to collapse
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.

clint.fish said:
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
Click to expand...
Click to collapse
UPDATE: So now I have managed to try and install the version of superSU that you have released in the dev thread, using TWRP. seemed to work fine, but i still got the same binary missing error.

clint.fish said:
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
Click to expand...
Click to collapse
Whoah way way way over complicating things. You just install twrp with odin and that's it.
Then you flash this with twrp http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip

ashyx said:
Whoah way way way over complicating things. You just install twrp with odin and that's it.
Then you flash this with twrp
Click to expand...
Click to collapse
So this is what I do.
Power off device.
Restart in Download Mode.
Use Odin to install the cf-autoroot-twrp-t705.tar from the development section.
When device restarts I put supersu version 2.52 (beta) on the devices memory, then turn off device.
Restart in TWRP Recovery mode, hit install, choose the zip file, install, reboot device.
When device reboots, open superuser and get this message: "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device".
I swear i'm not blonde. :good:

Something is blocking supersu from installing. Which firmware build is this device running and is reactivation lock disabled?

ashyx said:
Something is blocking supersu from installing. Which firmware build is this device running and is reactivation lock disabled?
Click to expand...
Click to collapse
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.

clint.fish said:
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
Click to expand...
Click to collapse
UPDATE: So I went into my Samsung account and Performed a factory reset. Only had the device a few days so no biggy. Then as it reset i chose not to put in and Samsung details and skip all the options i could, assuming this would help. Flashed cf autoroot with odin, then updated supersu through twrp... still nothing

clint.fish said:
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
Click to expand...
Click to collapse
UPDATE: SUCCESS! I used the latest version of Kingroot available on this forum. From looking around, you are a very patient person ashyx. Thanks for all your help!

clint.fish said:
UPDATE: SUCCESS! I used the latest version of Kingroot available on this forum. From looking around, you are a very patient person ashyx. Thanks for all your help!
Click to expand...
Click to collapse
This doesn't make sense. Something is amiss if you can't root with cf_autoroot or twrp. You are the only one as far as I'm aware that has experienced this.
Reactivation lock is under 'Find my phone' in security settings.

clint.fish said:
I'm brand new to this website, and have only signed up because I cannot find a solution for this problem. I have always used the forum to get answers, but never though to join! My Galaxy Tab S 8.4 4G T705Y was put through the CF-Auto-Root method, and no a glitch at all. Very smooth. By the way I checked the ChainFire website to make sure I was using the latest. When my device started up I noticed, as I have done before with my Nexus phones, that SuperSU has been added. Good Sign!
But when I open SuperSU I was prompted to update the Binary. Then I pressed 'continue', used the 'normal' method, and waited. It then asked me if I would like to Disable Knox. Yes I would! FAILED TO DISABLE KNOX. Shut down SuperSU. Unhappy Face. As you can see at this point, I am not very up to speed with my rooting knowledge.
So then I decided to select the 'never' option to updating SuperSU, and still it failed to update the binary, I'd say due to Knox stopping it from gaining access.
So my pickle is this: I can't update SuperSU because Knox will not allow me to use SuperSU. I cannot simply hit yes to disabling Knox in SuperSU, as that didn't work for me. I also tried finding something called Knox on my tablet and it seems to be very elusive. I tried updating SuperSU on Play Store also, but to no avail!
I am also unable to use any third party app to do so as I need to grant them access in SuperSU before they can begin! And around I go...
There is a guide here http://forum.xda-developers.com/showthread.php?t=2540761 but it's not for my device so I'm a bit hesitant to start trying random things, as my device is working great atm!
Any info or help would be greatly appreciated!
Click to expand...
Click to collapse
Chimed in with some feedback but noticed your problem solved after I replied. Unable to delete. Glad to see you're good to go though.

Need help getting Viper/ARISE working on stock, rooted setup

I've spent way too long trying to get this working without any success.
If I flash a custom ROM (ie. Pure Nexus), I can flash the ARISE zip (ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip) and it works perfectly. No driver issues, or anything.
When running stock, rooted, after flashing the above zip file, it appears to flash successfully, but when I open the app after rebooting, it always says that the drivers are missing and offers to install them. If I choose the option to install the drivers, it always fails.
I learned that if you're on stock, you have to flash a custom kernel before it'll actually flash (and auto install the apk), so I tried with franco and elemental kernels.
Does anyone know the steps I'm missing? I'm wondering if maybe it's because I need busybox, but I'm not sure where to install busybox (or the best method).
I know there has to be a way to get this working. I'm sure I'm missing something simple.
Thanks in advance!

eleazar123 said:
I've spent way too long trying to get this working without any success.
If I flash a custom ROM (ie. Pure Nexus), I can flash the ARISE zip (ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip) and it works perfectly. No driver issues, or anything.
When running stock, rooted, after flashing the above zip file, it appears to flash successfully, but when I open the app after rebooting, it always says that the drivers are missing and offers to install them. If I choose the option to install the drivers, it always fails.
I learned that if you're on stock, you have to flash a custom kernel before it'll actually flash (and auto install the apk), so I tried with franco and elemental kernels.
Does anyone know the steps I'm missing? I'm wondering if maybe it's because I need busybox, but I'm not sure where to install busybox (or the best method).
I know there has to be a way to get this working. I'm sure I'm missing something simple.
Thanks in advance!
Click to expand...
Click to collapse
I think not only do you need Busybox (you should just be able to download this from the play store now you're rooted) you will also need a way of setting SELinux to permissive. Try The SELinux toggler.

rename/remove /vendor/etc/audio_effects.conf

grifforama said:
I think not only do you need Busybox (you should just be able to download this from the play store now you're rooted) you will also need a way of setting SELinux to permissive. Try The SELinux toggler.
Click to expand...
Click to collapse
Shawn haz root said:
rename/remove /vendor/etc/audio_effects.conf
Click to expand...
Click to collapse
Thank you both! I will try all of those solutions right now.
When I tried to install busybox via the play store installer to /system/xbin/, it says "It looks like the installation of BusyBox was not successful. Try installing to a different location, that may resolve the issue".
My understanding is that I need to put it in /system/xbin. Do you guys have any ideas? The busybox installer was granted root when I first opened it, so I know it has root access. :\

eleazar123 said:
Thank you both! I will try all of those solutions right now.
When I tried to install busybox via the play store installer to /system/xbin/, it says "It looks like the installation of BusyBox was not successful. Try installing to a different location, that may resolve the issue".
My understanding is that I need to put it in /system/xbin. Do you guys have any ideas? The busybox installer was granted root when I first opened it, so I know it has root access. :\
Click to expand...
Click to collapse
I'd be interested to hear how you get on.
I have Viper4Arise installed, Busybox installed, and it appears to be working (sometimes it just doesn't) but when it does, I don't hear any difference when I apply my convolver irs .

grifforama said:
I'd be interested to hear how you get on.
I have Viper4Arise installed, Busybox installed, and it appears to be working (sometimes it just doesn't) but when it does, I don't hear any difference when I apply my convolver irs .
Click to expand...
Click to collapse
When I was running custom roms, it worked perfectly and I could tell a major difference in the music.
How did you get busybox installed? I can't figure out why the play store installer is failing. It's also failing for my friend on his Pixel XL (also rooted)

eleazar123 said:
When I was running custom roms, it worked perfectly and I could tell a major difference in the music.
How did you get busybox installed? I can't figure out why the play store installer is failing. It's also failing for my friend on his Pixel XL (also rooted)
Click to expand...
Click to collapse
If you install an app called "root browser classic", the second you open it, it requests to install an add on which is busy box. Then close and open it again and it asks to update which takes you to the Google play store then installed the busy box app. Not exactly a conventional way but I just tried and it installed. Not sure if that will help you or not.
Root browser
https://play.google.com/store/apps/details?id=com.jrummyapps.rootbrowser.classic
Busy box
https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer
I also installed this with no issues
https://play.google.com/store/apps/details?id=stericson.busybox

Shawn haz root said:
If you install an app called "root browser classic", the second you open it, it requests to install an add on which is busy box. Then close and open it again and it asks to update which takes you to the Google play store then installed the busy box app. Not exactly a conventional way but I just tried and it installed. Not sure if that will help you or not.
Root browser
https://play.google.com/store/apps/details?id=com.jrummyapps.rootbrowser.classic
Busy box
https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer
I also installed this with no issues
https://play.google.com/store/apps/details?id=stericson.busybox
Click to expand...
Click to collapse
Thank you! That jrummy busy box installer worked perfectly the first time. I confirmed in the stericson version that busy box is really installed.
I went ahead and flashed the arise zip file, and it has an option to set SELinux to permissive. Unfortunately upon reboot, it was the same drivers not installed error
I'm now thinking my issue might be the audio_effect.conf file. I've tried Solid Explorer (my go to file explorer) and Root Browser that you linked above. Both explorers have been granted root, but neither can actually rename the file (or delete it). Jrummy's app just says operation denied, while solid explorer shows the file gone, but if you refresh, it's right back where it was. I'm struggling to find a way to mount system r/w in either app. Do you have any ideas? :\
I tried to find a tool to set SELinux to permissive and i found lots of kernel tuning apps, but none that actually allowed setting permissive. Even Franco's own app for his kernel doesn't have that option (he said it's something about trying to keep it more secure). Hopefully the arise zip is really setting it properly, it's just the audio_effects issue causing my problem.
Thanks again for your help, guys!