So I was trying to downgrade my busybox to use the v6 Supercharger script. I had 1.19.3 installed. Was trying to go down to 1.18.3 I believe.
I used BusyBoxInstaller from the market to install the older one, and when it tried to download and install it said it didn't have the permissions and failed even though Superuser was allowing the app.
I figured it might of installed regardless so I went to ScriptManager and that wouldn't open, just FC. So I went back to BustBoxInstaller, and it started stating that my phone wasn't rooted and wouldn't open. I went to RootExplorer and that just hangs and then FC's. Restarted the phone, same issues. Tried a different busy box installer (BusyBox from the market) and it states some files are missing and it won't install either.
I used EsFile Explorer and I go into System/Xbin and it shows a busyBox file there, but I can't even mess with that. It can't be moved, renamed or anything. Not sure if it should even be messed with.
I tried searching this issue up around XDA, couldn't find anything similar.
Anyhow, did I just mess up pretty good and do I need to reflash my ROM? or is there a quick fix without all the mess?
I think I would reflash the ROM, then use the busybox installer on a fresh flash, before you restore anything, to install the version of busybox that you want
There are two busybox installers that I'm aware of, have you tried both? I prefer the newer one on the market - I think it's by jrummy. Also make sure the install location is correct.
If you've somehow reverted to s-on then the file won't install either. I doubt this is the case but I remember one case of someone having issues with something to do with a file in system and after trying everything they finally realized they were somehow s-on.
Supersonic Evo 4G | MIUI | Tapatalk
plainjane said:
There are two busybox installers that I'm aware of, have you tried both? I prefer the newer one on the market - I think it's by jrummy. Also make sure the install location is correct.
If you've somehow reverted to s-on then the file won't install either. I doubt this is the case but I remember one case of someone having issues with something to do with a file in system and after trying everything they finally realized they were somehow s-on.
Supersonic Evo 4G | MIUI | Tapatalk
Click to expand...
Click to collapse
This is true quoted for truth!
I checked and I'm s-off. I used both busybox apps. The one from rummy won't even open. It states I'm not rooted and then closes. The other app (just called busybox) opens but when I hit install it basically states the same thing. I can't choose the install location on that one either. I saw something about pushing it with ABD tool. Just not at home to try that out. Thanks for the help guys. Probably gonna have to wipe and start over.
Sent from my PC36100 using XDA App
I have this same issue. Ever since the busybody updated I cannot do anything. I can't go into root explorer, install any apks will not connect to wifi or wimax
Want to point out a few things, if your running scripts use Busybox 1.18.2. Secondly, the app in the market, Busynox Installer works wonder, however, sometimes when you change the version number it doesn't stick. Today, I had to cycle through installing 1.18.2 four times until it stuck. After installing another version, use root check to verify the version of busybox installed before proceeding to using any scripts. Also, check with the rom your using and make sure theres no issues. Each rom behaves differently.
JollyGrnReefer said:
Want to point out a few things, if your running scripts use Busybox 1.18.2. Secondly, the app in the market, Busynox Installer works wonder, however, sometimes when you change the version number it doesn't stick. Today, I had to cycle through installing 1.18.2 four times until it stuck. After installing another version, use root check to verify the version of busybox installed before proceeding to using any scripts. Also, check with the rom your using and make sure theres no issues. Each rom behaves differently.
Click to expand...
Click to collapse
Thanks for the help. Again though I can't get into BusyBox Installer or BusyBox app (both from the market) So I really don't have a choice to get it to stick or to pick where it installs. I wound up having to just go back and recover off an old ROM backup I had.
I did try go back to 1.18.2 but BusyBox Installer (the one by Rummy) for some reason it wouldn't install. It kept saying that I didn't have permission and then another pop-up would come saying "superuser access permitted" or something like that. I hit install a few times, and kept getting the same error. I figured it was just a bug in the app. I tried going into the Script manager but it would FC without opening. I then tried going back into BusyBox installer which then claimed that I wasn't rooted (even though I show S-Off) and then would close. I then tried going into RootExplorer to delete the script thinking that might be the issue. Root Explorer would just hang. It'd stay on a black screen..say "this is taking longer then normal. Force close or wait" I hit wait 3 times, and no luck. Tried restarting multiple times, same issues.
Earlier today it stared effecting my connectivity or so I assume because all of a sudden I'd be roaming, the not, then I would be again..on and off all day. I never had that issue on that ROM before this whole busybox issue.
Anyhow. Again, I just reverted back to the old ROM I had and am going to sit on it for a bit.
Thanks to everyone for the help, ideas, tips, etc. It's greatly appreciated.
Related
So I used Visionary to root my HTC Desire Z, checked that it was rooted with Android Terminal Emulator using su returning #
I then proceeded to delete all the .apk's of the bloatware in /system/app folder
Upon restart they reappeared. I've tried 3 different file managers and I also tried deleting their data folders in /data/data and now matter what I do they reappear on a restart.
Does this mean it is hard coded into the ROM? DO I have to wait for a permanent root and flash a new stock ROM minus the bloatware?
Anyone found a solution or maybe i'm doing it wrong...
This is another example of where we're miles behind the G2 forums. Check out the G2 ROM Dev forum, there is an app there to show how you can delete built-in apps and then they won't reappear.
But BE CAREFUL ! It will probably be the case that if you go down this road, you may have a problem with future OTA updates.
The reason it's not working with your current method is that you're not really deleting anything. Write access to the internal storage is not possible right now (it is being worked on intensively for the G2), so the phone is caching the file system and making it appear they've been deleted, but the internal storage hasn't been updated. So when you reboot, the app just comes back again. This is how come there's been a myth that the phone automatically "un-does" any changes and resets itself when you reboot - it's not really doing that, because you didn't make any permanent changes in the first place.
steviewevie said:
This is another example of where we're miles behind the G2 forums. Check out the G2 ROM Dev forum, there is an app there to show how you can delete built-in apps and then they won't reappear.
But BE CAREFUL ! It will probably be the case that if you go down this road, you may have a problem with future OTA updates.
The reason it's not working with your current method is that you're not really deleting anything. Write access to the internal storage is not possible right now (it is being worked on intensively for the G2), so the phone is caching the file system and making it appear they've been deleted, but the internal storage hasn't been updated. So when you reboot, the app just comes back again. This is how come there's been a myth that the phone automatically "un-does" any changes and resets itself when you reboot - it's not really doing that, because you didn't make any permanent changes in the first place.
Click to expand...
Click to collapse
Thanks for the explanation! Hmm yeah, I don't know if I want to start flashing roms or leave it stock because it's pretty decent stock. And I did hear that updating/upgrading to new OS's have problems is you delete the bloatware programs...
Thanks again
st1n6r4y said:
So I used Visionary to root my HTC Desire Z, checked that it was rooted with Android Terminal Emulator using su returning #
I then proceeded to delete all the .apk's of the bloatware in /system/app folder
Upon restart they reappeared. I've tried 3 different file managers and I also tried deleting their data folders in /data/data and now matter what I do they reappear on a restart.
Does this mean it is hard coded into the ROM? DO I have to wait for a permanent root and flash a new stock ROM minus the bloatware?
Anyone found a solution or maybe i'm doing it wrong...
Click to expand...
Click to collapse
try this method:
1. install VISIONary
2. install busybox
3. install titanium backup
4. run VISIONary
5. Run BusyBox
6. install busybox through the installer
7. run Titanium Back-up
8. find the app you don't want
9. press and hold and an a contextual menu will pop up and select the last option
or check our this link: http://android.modaco.com/content/h...move-applications-using-the-recovery-exploit/
i did it this way and have master reset many times and all the Bell Bloatware is gone, BUT... i had to repeat the steps 4 - 9 after each time, but the crapware is gone!
seattleboi1982 said:
try this method:
1. install VISIONary
2. install busybox
3. install titanium backup
4. run VISIONary
5. Run BusyBox
6. install busybox through the installer
7. run Titanium Back-up
8. find the app you don't want
9. press and hold and an a contextual menu will pop up and select the last option
or check our this link: http://android.modaco.com/content/h...move-applications-using-the-recovery-exploit/
i did it this way and have master reset many times and all the Bell Bloatware is gone, BUT... i had to repeat the steps 4 - 9 after each time, but the crapware is gone!
Click to expand...
Click to collapse
Cool thanks!
seattleboi1982 said:
try this method:
1. install VISIONary
2. install busybox
3. install titanium backup
4. run VISIONary
5. Run BusyBox
6. install busybox through the installer
7. run Titanium Back-up
8. find the app you don't want
9. press and hold and an a contextual menu will pop up and select the last option
or check our this link: http://android.modaco.com/content/h...move-applications-using-the-recovery-exploit/
i did it this way and have master reset many times and all the Bell Bloatware is gone, BUT... i had to repeat the steps 4 - 9 after each time, but the crapware is gone!
Click to expand...
Click to collapse
Tried this method. Everything works fine (rooted, Busybox installed), but when I try to pick the option to "Force remove app (by recovery exploit)" I get the error message "Cannot remove system app, Failed to locate apk file".
What am I doing wrong?
redpoint73 said:
Tried this method. Everything works fine (rooted, Busybox installed), but when I try to pick the option to "Force remove app (by recovery exploit)" I get the error message "Cannot remove system app, Failed to locate apk file".
What am I doing wrong?
Click to expand...
Click to collapse
Never mind, I figured it out. You need to have either S-OFF or CID unlock in order for this method to work. I was only rooted, and intentionally not S-OFF and SuperCID. I used the gfree method to S-OFF and SuperCID, and the above method of removing the bloatware seems to be working perfectly now.
redpoint73 said:
Never mind, I figured it out. You need to have either S-OFF or CID unlock in order for this method to work. I was only rooted, and intentionally not S-OFF and SuperCID. I used the gfree method to S-OFF and SuperCID, and the above method of removing the bloatware seems to be working perfectly now.
Click to expand...
Click to collapse
It was the S-OFF. Unless you have S-OFF, you still have write protection on the system and recovery partitions. So apps will appear to get deleted as the information is written to cache. But they'll come back on a reboot because the information was never written to (deleted from) permanent storage.
So if I'm rooted using Visionary and have S off using the gfree method but I never installed busybox.. What would be the best method? Can I just install busybox and install or would I need to do another method?
Sent from my HTC Vision using XDA App
Rickroller said:
So if I'm rooted using Visionary and have S off using the gfree method but I never installed busybox.. What would be the best method? Can I just install busybox and install or would I need to do another method?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Just install Busybox.
The above method worked great EXCEPT for one app: Kobo (e-reader). I've tried to force remove in Titanium Backup three times now, and also tried using the "regular" un-install option in Titanium Backup. Every time the phone reboots, Kobo is still there.
Any ideas?
I used an app called system app remover i think thats the name...not 100% suree...but i got it to get rid of wifi calling cuz im on roger and tmobile wifi calling wouldnt work so i tried the titanium back up method and it didnt work so i looked around and android underground had a download for the app and it removed the app and it went into an fc loop so i pulled the battery and it is gone and rom runs perfectly fine
Sent from my HTC DesireZed
SN4K3B1T3 said:
I used an app called system app remover i think thats the name...not 100% suree...but i got it to get rid of wifi calling cuz im on roger and tmobile wifi calling wouldnt work so i tried the titanium back up method and it didnt work so i looked around and android underground had a download for the app and it removed the app and it went into an fc loop so i pulled the battery and it is gone and rom runs perfectly fine
Sent from my HTC DesireZed
Click to expand...
Click to collapse
Using an app called Absolute System Root Tool has the feature to uninstall system apps, and this worked for me to remove Kobo.
I've searched high and low for a solution to this that works for me, both here and everywhere else Google would point me, but I have yet to find one that works, so I hope someone can help me.
I've an original Desire running a rooted Froyo ROM, which was rooted using unrevoked ages ago (probably a year or so no). When I originally rooted it, everything worked perfectly. A few months ago I ran the newest version of unrevoked over it again to update the recovery to the latest clockwork and it appeared to work fine, but ever since I did this the superuser app will continually pop up asking for permissions every time any app that needs root is run (sometimes MANY times, as when Titanium backup is run).
I've tried different things to see if I could fix it - clearing the data for the Superuser app, clearing the Dalvik cache, even reflashing the older clockwork recovery back onto my phone with the older version of unrevoked which originally worked, but with no luck. The phone is still S-ON, but I don't see why that would matter when I had no problems with the original rooting of the phone.
I'm stuck and am not sure where to go from here, so any advice would be very appreciated.
Ommadawn said:
I've searched high and low for a solution to this that works for me, both here and everywhere else Google would point me, but I have yet to find one that works, so I hope someone can help me.
I've an original Desire running a rooted Froyo ROM, which was rooted using unrevoked ages ago (probably a year or so no). When I originally rooted it, everything worked perfectly. A few months ago I ran the newest version of unrevoked over it again to update the recovery to the latest clockwork and it appeared to work fine, but ever since I did this the superuser app will continually pop up asking for permissions every time any app that needs root is run (sometimes MANY times, as when Titanium backup is run).
I've tried different things to see if I could fix it - clearing the data for the Superuser app, clearing the Dalvik cache, even reflashing the older clockwork recovery back onto my phone with the older version of unrevoked which originally worked, but with no luck. The phone is still S-ON, but I don't see why that would matter when I had no problems with the original rooting of the phone.
I'm stuck and am not sure where to go from here, so any advice would be very appreciated.
Click to expand...
Click to collapse
When you're on Superuser app, do you see your apps with green button on the rigth ?
Witch version of Superuser app do you use ? Mine is v2.3.6.3 with cmd su v2.3.1-ef
Also, when being asked for permission, is "Remember" checked?
why not just re-root?
punky.mtp said:
When you're on Superuser app, do you see your apps with green button on the rigth ?
Witch version of Superuser app do you use ? Mine is v2.3.6.3 with cmd su v2.3.1-ef
Click to expand...
Click to collapse
Yes you should have a list of allowed apps on opening the su app itself - click apps on top left. The allowed apps shouldn't keep requesting permission each time.
You coukkd uninstall su app then reinstall from market?
Nandroid backup first!
Thanks for the all the replies, much appreciated!
@punky.mtp & @stringer7: Yes, I can see the apps I've granted permissions to in the Superuser app, each has a green button against it. I'm not sure of the current version of SU I'm running, but I know it's not the latest version. I've tried to update it from the Market but it won't over-write the existing installed SU. I'm doing a nandroid as I type and will try uninstalling and reinstalling to see if that helps.
@HiVoltage85: Yes, I've set the remember checkbox as well for each app when granting permission.
@BigMrB: I've already re-rooted with different versions of unrevoked, several times, which hasn't fixed the problem.
I'll let you know how I go.
Sorry, I'm giving away my ignorance, but how do I uninstall my current Superuser app? The uninstall button is disabled in the manage applications part of the phone's setup.
Edit - Never mind, I found how to do it.
Looks like I have it fixed. I was able to remove the old Superuser app and install a new one from recovery (v2.3.6.3) which works properly and doesn't keep asking for permissions repeatedly. Thanks for the suggestions and help!
Hey guys, im fairly new to the whole rooting and customizing of android scene, but i rooted my epic 4g using the oneclickmethod found here. Everything has gone fine and ive been able to flash multiple roms and try different things out, but today i downloaded the font changer app which then lead me to downloading the busy box app, however i got hung up on the installation of busy box because its saying im not nand unlocked. i assumed that took place with the whole rooting method, is there anything i can do to fix that at all?
ianduh said:
Hey guys, im fairly new to the whole rooting and customizing of android scene, but i rooted my epic 4g using the oneclickmethod found here. Everything has gone fine and ive been able to flash multiple roms and try different things out, but today i downloaded the font changer app which then lead me to downloading the busy box app, however i got hung up on the installation of busy box because its saying im not nand unlocked. i assumed that took place with the whole rooting method, is there anything i can do to fix that at all?
Click to expand...
Click to collapse
I believe No nand unlock is needed, unless it goes through that when rooting. Make sure superuser is up to date. Even try to uninstall superuser and re install. I had the same problem before and am trying to remember what I did. I know I uninstalled superuser & re installed and uninstalled the APP i was trying to get to work and also re installed. So try that and see if it works
Samsung doesn't NAND lock their phones.
Even try to uninstall superuser and re install. I had the same problem before and am trying to remember what I did. I know I uninstalled superuser & re installed and uninstalled the APP i was trying to get to work and also re installed. So try that and see if it works
Click to expand...
Click to collapse
i dont mean to sound completely stupid, but how do i go about uninstalling/reinstalling superuser, do i just re-root the phone? Just asking before i try anything so i minimize my chance of bricking, thanks guys.
why dont you link us to the app not working?
If you have a ROM installed chances are that you already have busybox, there that most dev's include it on there ROMs.
I think that your trying to install Busybox in an area of your phone were its currently mounted as Read Only and not R/W. Double check the destination of the busybox installer (it will give you several options) and choose from there.
Hey Guys,
I looked for a specific post relating to my issue, but I couldn't find one. I just installed MIUI 111250 on my Verizon Droid Incredible. I've been rooted since day one, and up until now I have been on skyraider with NO problems. I used rom manager to move over, and I cleared all the data. The ROM installed with no issues, but I cannot access root with any of my apps. They are requesting permission, and I have granted them permission, but no luck. I've checked the SU app, and everything is enabled (including manage permissions). Has anyone else had this problem. Thanks in advance for any help / suggestions.
- BL00513
Do you have Busy Box installed? I have had this similar issue before and installing busy box off the market cleared it up for me.
RE:
I've tried installing busybox, but it will not let me. I actually tried both installers with no success. Any other ideas?
You can RUU to stock and re-root using unrevoked. Just make sure you use the Froyo RUU. After that try installing MIUI again...
RE: RUU
A little more info..... I downloaded "Root Checker", and it is telling me that I have root. This seems really weird to me! I am going to try flashing CM7 to see if I have root with that ROM. I will keep let you guys know how it goes.
RE: RUU
Is there a specific way you recommend to RUU? I tried using ADB shell, but I get permission denied when I do CHMOD. Do you have a better idea? Isn't there an exe out there that will do this for me? Thanks!
Check out pvillecomp.com I think the froyo ruu is there. I'm not by a pc right now otherwise id be able to point you in the right direction. Make sure you use the froyo ruu so that you can root with unrevoked.
Sent from my Droid Incredible
I doubt an RUU is necessary in this situation, it sounds like an issue with superuser. Try downloading "superuser update fixer" from the market and see if that fixes your problem. This isn't a rom issue, it's a SU issue. Did you update SU through the market?
Fixed it....
I am not sure what the problem was, but I am leaning towards it being a SU issue. Whatever the case, I reflashed the rom (this time from clockwork directly instead of ROM manager). This did the trick! Thank you guys for all of your help.
Figured I would start here in my device thread before trying the SuperSU thread.
Anybody have issues with SuperSU since the last few updates ago?
SuperSU does not even open. Root-dependent apps do not open. Titanium sits there at the initial screen "asking for root rights" until I kill the app. AdAway does not open... just goes right to a black screen until I kill the app. AdAway seems to work though, as my web surfing does not have ads.
I've also tried manually going in and applying the latest update via (philz) recovery.
Would I be safe to roll back to an older version of SuperSU?
Mods... if you're going to gun the thread, please at least point me in the right direction as I did search, but did not find anything related to recent issues on the Note 2 for SuperSU.
TIA for help and suggestions.
Oh yeah its still sitting in the play store. I lost root the last couple updates ago. I had to re flash my rom and start over.
ceabbott2 said:
Oh yeah its still sitting in the play store. I lost root the last couple updates ago. I had to re flash my rom and start over.
Click to expand...
Click to collapse
As part of my search, I did see Chainfire mention in his "fix" thread that some apps like wanam can cause issues. Of course, I have xsposed installed, so that could be the issue.
Do you (or did you) also have xsposed installed as well?
I have tried older versions of SU, uninstalling via philz then redownloading from Play - which now tells me the binaries are out of date and can't be done by SU, and I need to re-root.
Think I might try one of the other SuperUser apps "just to see how it works", or if it does.
lennykravitz2004 said:
As part of my search, I did see Chainfire mention in his "fix" thread that some apps like wanam can cause issues. Of course, I have xsposed installed, so that could be the issue.
Do you (or did you) also have xsposed installed as well?
I have tried older versions of SU, uninstalling via philz then redownloading from Play - which now tells me the binaries are out of date and can't be done by SU, and I need to re-root.
Think I might try one of the other SuperUser apps "just to see how it works", or if it does.
Click to expand...
Click to collapse
For me, I just reflashed the ROM I was running at the time and that resolved it. Of course seeing that the update was " fixed" I attempted it and lost root again. I then did the same as before, wiped and relashed. I didn't do clean installs either time. Just wiped caches and reflashed. That sucks if you have to re-root. I mean, it's easy and all but it shouldn't have to be done.
D
Before attempting any drastic measures (i.e., full wipe and reinstallation of the ROM), try this. This trick usually works for me.
Open your Application Manager, and locate your SuperSU application. Turn it off (i.e., click the "Turn Off" button). It may prompt you that updates are about to be uninstalled; that's ok. Download "BETA-SuperSU-v2.25.zip" and verify the MD5. Reboot into recovery and flash this file. Reboot and re-enable the SuperSU application from the Application Manager (it will be easy to find this time - scroll all the way over to the right, under "Turned Off"). Open SuperSU and it should let you reinstall the binaries.
Recently I've inexplicably lost root a number of times, and the above method has fixed it for me every time.
DJ_Barcode said:
Before attempting any drastic measures (i.e., full wipe and reinstallation of the ROM), try this. This trick usually works for me.
Open your Application Manager, and locate your SuperSU application. Turn it off (i.e., click the "Turn Off" button). It may prompt you that updates are about to be uninstalled; that's ok. Download "BETA-SuperSU-v2.25.zip" and verify the MD5. Reboot into recovery and flash this file. Reboot and re-enable the SuperSU application from the Application Manager (it will be easy to find this time - scroll all the way over to the right, under "Turned Off"). Open SuperSU and it should let you reinstall the binaries.
Recently I've inexplicably lost root a number of times, and the above method has fixed it for me every time.
Click to expand...
Click to collapse
Thanks for the try. Did not work though.
Looks like I just need to re-flash the ROM.
My problem was odd. Before I discovered the aforementioned trick, I'd re-root with Chainfire or Kingo. I'd reboot, and my device would be rooted. But those two methods have an additional payload - they flash the stock recovery. So I'd ODIN the Philz Touch recovery back to the device, reboot, and root would be gone. Never figured out what was going on.
Yup. Issues with new version. Only last 2 or three updates.
They seemed to be perfectly fine with cm12 though.
Sent from my SPH-L900 using XDA Free mobile app
Thanks for all of the input.
After doing a full wipe, and then re-loading Classic Stock 4.4.2, life is good again! Back to running awesome for a few weeks now.
Having said that, I did want to follow-up and ask others what current version of SuperSU you are on. As of right now, I am still on v2.01 (which is what was packaged with the ROM) and have not updated yet. Only other versions of SuperSU I have zips downloaded for are: 2.25 from post above, 2.36, and 2.37.
Any suggestions or confirmations on which newer/more recent versions will not bork my root status? Or which versions to definitely stay away from trying to use?
Thanks, and I appreciate any help and suggestions!
lennykravitz2004 said:
Thanks for all of the input.
After doing a full wipe, and then re-loading Classic Stock 4.4.2, life is good again! Back to running awesome for a few weeks now.
Having said that, I did want to follow-up and ask others what current version of SuperSU you are on. As of right now, I am still on v2.01 (which is what was packaged with the ROM) and have not updated yet. Only other versions of SuperSU I have zips downloaded for are: 2.25 from post above, 2.36, and 2.37.
Any suggestions or confirmations on which newer/more recent versions will not bork my root status? Or which versions to definitely stay away from trying to use?
Thanks, and I appreciate any help and suggestions!
Click to expand...
Click to collapse
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
jlmancuso said:
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
As always, thanks for your response. Your recommendation is what I've been doing, just wanted to follow-up on this and see if there was anything else I needed to consider or change as well.
My main concern was to make sure I was not going to run into any "big" issues (especially security) by staying on current version. Thanks for explaining where the issue really lies on this too. I'm obviously not a dev, however I do want to understand what is exactly going on and responses like yours always provide that type of info. :good: Thank you.
And, FWIW, using "fool proof" to describe a process only makes me more curious (and no, not in that way) about your suggestion. :laugh:
Now I HAVE to find out more about that option... (only after some of the best BBQ in all of the land - Sugarfire BBQ in STL )
jlmancuso said:
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
How do you disable auto update of binary on SuperSU? I keep seeing it in the notification bar, very annoying.