I was using device perfectly till today. I've installed nocturnal kit lastly. Don't know if it's related to this or not but it seems i've lost my root access. Now I can't use CM file manager which was working well and can't edit any app's settings in paranoidandroid. Both need root access. It keeps saying "couldn't get privileges" So is it possible to lose root by installing apps, mods or any software issues?
Not likely. Just go to your superuser app and make sure root access is being given.
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
Not likely. Just go to your superuser app and make sure root access is being given.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
checked su app and all root needed apps are seems to have access but they don't work I'm gonna wipe and reflash I think.
Try wiping cache for superuser. And you can try switching to superSU, it's better than the original.
Sent from my Nexus 4 using xda app-developers app
get the supersu app from the market, free. install it, open it, then press yes when it asks you to update your su binaries. supersu works well for jelly bean, superuser is hit and miss.
Ace42 said:
Try wiping cache for superuser. And you can try switching to superSU, it's better than the original.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Tried that too. Also wiped cache & dalvik and didn't work.
Related
Beware of the recent update to 3.04, there are frequent reports of apps requiring root access not working due to superuser fcing. YMMV.
Sent from my PC36100 using XDA App
Yes very true
Sent from my Gruesomes Rom using XDA App
Is there a way to reverse this? All root apps no longer working : |EVO 4G
1range said:
Is there a way to reverse this? All root apps no longer working : |
Click to expand...
Click to collapse
Yes in the market hit uninstall and it will revert back to the previous version
Sent from my Gruesomes Rom using XDA App
Thanks for the quick response, however I've done that -having the same result...Tried apps after that...still no go. Ran root checker "No Root Acess." Unless its the Titanium Backup update. Other than those 2, I haven't done anything else.
1range said:
Thanks for the quick response, however I've done that -having the same result...Tried apps after that...still no go. Ran root checker "No Root Acess." Unless its the Titanium Backup update. Other than those 2, I haven't done anything else.
Click to expand...
Click to collapse
Uninstall su and reflash your rom
Deck's + SZ + SuperCharger script + ViperMod script.
Oops
Deck's + SZ + SuperCharger script + ViperMod script.
So far unsuccessfull at uninstalling su...theres only the update option from the market...at this point lost..
I have had the same issue. So far the only workable solution that I have come up with is to:
- Delete the App data for Superuser (in Manage Apps).
- Run Super User and change the Automatic Response to Allow (in superuser preferences).
Not ideal because any app that requests su will get it. Have to keep an eye on the log until a fix if there are any apps that you do not want to have su.
Thanks...was able to delete su app data and access su...yet still no access to root apps (su 2.3.6.3)
Just reflash rom
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
Appreciate it...I'll keep working on it...for some reason can't get into boot mode...power-volume down button not working
Sent from my PC36100 using XDA App
No need to reflash roms or uninstall anything from from your phone guys.... The fix is to uninstall updates of superuser in market.... Once done this go to your applications on your phone and click on superuser app and hit ok when the popup screen comes up.... And your apps that require root access will work once again....
Sent from my PC36100 using XDA Premium App
towncop1978 said:
No need to reflash roms or uninstall anything from from your phone guys.... The fix is to uninstall updates of superuser in market.... Once done this go to your applications on your phone and click on superuser app and hit ok when the popup screen comes up.... And your apps that require root access will work once again....
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Confirmed. Recent update fixed issues.
my fix was...
Uninstall updates as stated in earlier post ;-) Then a restart or Reboot is all is needed. no need to reinstall the rom thats not the answer.
No issues here, have the latest superuser.
Downgraded, Restarted, rebooted su force closes still...any suggestions?
Sent from my PC36100 using XDA App
The fix seemed to have worked for me. Glad, because this has been killing me all day!
re: updated superuser
evo4gnoob said:
Yes in the market hit uninstall and it will revert back to the previous version
Sent from my Gruesomes Rom using XDA App
Click to expand...
Click to collapse
Thanks evo4gnoob for the keen eye and the catch! I've already uninstalled superuser -- awaiting a more stable release.
Once again, thanks a million! =)
The new SU screwed my phone too, but I just installed, and flashed a older one from recovery, and all is well.
Last night I installed SuperSU on my Nexus.. it's awesome but I'm having issues with some apps. Though 98% of them are still recognized from before I installed SuperSU couple are now not compatible.
Anyone else run into this issue?
Sent from my Nexus 7 using xda app-developers app
What does not compatible mean. SuperSu doesn't recognize some app's or won't grant them 'root'? Are the app's in SuperSu but won't complete root actions?
Iffn it was me I would tell SuperSu to forget all app's. Then wipe data in manage app's in setting. Then uninstall and reinstall SuperSu. Of course you will lose your 'remembered' app's but I can't see that being a very big deal.
Sent from my Nexus 7 using xda premium
I'm not trying to root this app, I had it installed on my tablet prior to SuperSU but now it says "your device is not compatible with this version"
Sent from my Nexus 7 using xda app-developers app
Today when I wanted to update Franco kernel with his application I noticed that somehow my superuser have stopped working completely.
I have root but I don't get prompted with the "give root access" windows when opening apps.
What can I do to fix this?
Sent from my Nexus 4 using Tapatalk 2
pimmen said:
Today when I wanted to update Franco kernel with his application I noticed that somehow my superuser have stopped working completely.
I have root but I don't get prompted with the "give root access" windows when opening apps.
What can I do to fix this?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
You might try installing superSU from Google Play and switch granting root access to this app in the SU settings.
Is Superuser set to "Prompt" in the settings?
WastedJoker said:
Is Superuser set to "Prompt" in the settings?
Click to expand...
Click to collapse
Yes sir.
Sent from my Nexus 4 using Tapatalk 2
Are your rooted apps actually working fully?
Guess you could try going to Settings > Apps and clear data on superuser before rebooting.
WastedJoker said:
Are your rooted apps actually working fully?
Guess you could try going to Settings > Apps and clear data on superuser before rebooting.
Click to expand...
Click to collapse
No that Is exactly, all of a sudden my root apps stopped working, seeder/titanium backup etcetera.
Sent from my Nexus 4 using Tapatalk 2
Sounds like you've become unrooted.
Try re-rooting again?
Are you running stock? If so, did this problem appeared after upgrading to 4.2.2? System Updates usually-if not always- break root. Just download Root Checker from the Play Store to check if you still have root access, if not then you must root it again
This wasn't happening yesterday. Every morning I reboot my phone when j remove from the Wireless charger to prevent the wireless charger wakelock.
This morning however I notice that everytime I reboot I get the Android is upgrading message as if I just performed a OTA.
The phone finishes the upgrade and looks and acts fine bit if I reboot again it does it again.
Anyone else experience this before? Its still happening if I reboot everytime.
Sent from my Nexus 7 using xda app-developers app
Clear cache and maybe load a new kernel maybe?
Sent from my Nexus 4 using xda app-developers app
if you didnt do it yourself, then its either an app, a mod, or the rom/kernel that youre running. whats happening is that your dalvik-cache is getting wiped then rebuilt on boot.
I'm on stock 4.2.2 rooted and running motley kernel. Have been running this setup for a month no and no issues and haven't installed any weird apps that could do this.
Doesn't make sense
Sent from my Nexus 4 using xda app-developers app
I think it happens when you wipe davlik with apps disabled.
if it only pops up for a second or so, don't worry about it.
It was the beats audio root app (paid version) I noticed it would consistently say permission granted even when the phone was idle.
Uninstalled the drivers using the inapp uninstaller and now no more message when rebooting.
Anyone know why this app clears dalvik cache every reboot?
Sent from my Nexus 4 using xda app-developers app
nextelbuddy said:
It was the beats audio root app (paid version) I noticed it would consistently say permission granted even when the phone was idle.
Uninstalled the drivers using the inapp uninstaller and now no more message when rebooting.
Anyone know why this app clears dalvik cache every reboot?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
i use the beats+xlouder flashable mod, and it clears dalvik upon flashing. its nonsense that the app clears dalvik after a reboot, i definitely wouldnt be happy with it.
nextelbuddy said:
I'm on stock 4.2.2 rooted and running motley kernel. Have been running this setup for a month no and no issues and haven't installed any weird apps that could do this.
Doesn't make sense
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This started in 4.0, its just part of system startup to check system integrity I believe
Sent from my Jelly Nexus 4
So how do you find out which application is the one that's wiping the cache?
yahoowizard said:
So how do you find out which application is the one that's wiping the cache?
Click to expand...
Click to collapse
its probably one that needs root. it could be a flashed mod too.
simms22 said:
its probably one that needs root. it could be a flashed mod too.
Click to expand...
Click to collapse
Thanks, I think I found what the problem might be.
yahoowizard said:
Thanks, I think I found what the problem might be.
Click to expand...
Click to collapse
sweet
Thank you for sharing what was the problem.
I have found fix for this error, it is mainly due to odex files which are created by lucky patcher so deleting these files using lucky patcher itself will surely remove this error with 50 percent success rate. Here's the fix; open lucky patcher, there in lower left section you can see Toolbox, click Toolbox button then select 4th last option i.e Remove all odex files. Thats it android will reboot on itself and vola no android is upgrading. .
Check out attachement for help.
:good:Hits Thanks If I helped u:good:
Has anyone tried this method? SuperSU has a full unroot option in its settings. I have read many posts saying it is impossible to unroot at this time.
I did a little searching around and didn't find much. Just suggestions to try it and no one ever reported back if it works or doesn't.
I personally don't have the OTA and have a custom ROM, but i would like to know any confirmation of it working or not working by anyone that has tried it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
I did the ota to mf3 and successfully rooted it I then realized that I had like 6gbs missing so in an effort to restore I went into the SU settings and chose the remove root option and it seemed to work I checked with root checker and I no longer had root access I still was unable to restore it just bumps me into Odin mode and I have to boot power+home+volume- then cancel to reboot my phone into working order
But as far as I can tell I have no root
Since I can't restore and try and clear up my missing storage I wanted to take it in and try and get a new one under warranty but I'm afraid to use triangle away so I'm just gonna wait it out until we get a mf3 restore firmware for Odin since my phone works fine for now
Sent from my SAMSUNG-SGH-I337 using xda premium
So that is 1 confirmation for an unroot. Basically hit unroot, it sends the phone to bootloop. Remove battery, put it back, then boot to download mode with power+volume down, then hit volume down again to cancel and reboot to a fully functional phone with no root. If that doesn't work, use power+home+volume down. Anyone else?
Btw,
Don't use triangle away. It flashes a temporary recovery to reset the binary. It will brick you or just fail.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
Has anyone tried this method? SuperSU has a full unroot option in its settings.
Click to expand...
Click to collapse
I fully un-rooted using the method in my post here - http://forum.xda-developers.com/showthread.php?p=44495559 . For me, it just threw the custom-lock icon boot up screen and showed "Custom" status in the "About Phone" menu when using the SuperSU's un-root method.
The problem was busy box. The MF3 root scripts install Busybox files into the /xbin directory, but SuperSU's "full unroot" doesn't touch Busybox's files. Not even any Busybox apps can remove those files.
So delete the busybox files first, then unroot. That is 2 confirmed unroots.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
ou812bkewl said:
I fully un-rooted using the method in my post here - http://forum.xda-developers.com/showthread.php?p=44495559 . For me, it just threw the custom-lock icon boot up screen and showed "Custom" status in the "About Phone" menu when using the SuperSU's un-root method.
The problem was busy box. The MF3 root scripts install Busybox files into the /xbin directory, but SuperSU's "full unroot" doesn't touch Busybox's files. Not even any Busybox apps can remove those files.
Click to expand...
Click to collapse
graydiggy said:
So delete the busybox files first, then unroot. That is 2 confirmed unroots.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This method also worked for me as well. Had no problems following the steps.
3 confirmed
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
3 confirmed
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Good info to know. Thanks graydiggy
I am going to change this to a how to thread later today. Anyone else try it?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
this may be a stupid question, but if you went through the trouble of rooting after the mf3 update.. why would you want to unroot?
Warranty replacement in case of a hardware issue, testing purposes, also, some people only want a temp root to remove bloat. After that, they don't want root anymore.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
So to summarize the steps from what I've read on rooting & unrooting MF3:
Root:
Use this guide by jortex: http://forum.xda-developers.com/showthread.php?t=2387577&highlight=mf3
Unroot: http://forum.xda-developers.com/showpost.php?p=44495559&postcount=39
1. Re-root again using the same method you did before for MF3, then:
--a) Reboot, update SuperSU app and it's binary
--b) Reboot again, verify device status is back to"Official"
--c) Reboot again, verifying that, this time, the boot screen is back to normal again
2. Download a file manager app in the Play Store called "Total Commander" and enable "Root functions everywhere" in its settings.
3. Navigate to a folder called "/system/xbin"
4. Delete ONLY files in that folder with the word "busybox" within its filename or symlink path. You should end up with three files left. I did. Two of them are SuperSU related. DO NOT DELETE ANY OF THEM!
5.Open SuperSU and, in its settings, select the "Full un-root" option. Once SuperSU closes, reboot.
Click to expand...
Click to collapse
Follow step 1 if not rooted or messed up somewhere during unrooting process.
Just double checking step 2: We can use es file explorer with root explorer option as well correct?
Also I noticed superSU got updated today:
http://forum.xda-developers.com/showthread.php?t=1538053
05.09.2013 - v1.60
- Added SELinux+Enforcing compatibility (for new SGS4 ROMs)
- Fixed (newest) CWM versions asking you question that break root if answered wrongly
- Fixed issue with the TWRP/CWM binary installer
- Fixed 4.3 OTA survival looping
Click to expand...
Click to collapse
Does the new update have something to do with our mf3 baseband like SELinux?
haremmon said:
So to summarize the steps from what I've read on rooting & unrooting MF3:
Root:
Use this guide by jortex: http://forum.xda-developers.com/showthread.php?t=2387577&highlight=mf3
Unroot: http://forum.xda-developers.com/showpost.php?p=44495559&postcount=39
Follow step 1 if not rooted or messed up somewhere during unrooting process.
Just double checking step 2: We can use es file explorer with root explorer option as well correct?
Also I noticed superSU got updated today:
http://forum.xda-developers.com/showthread.php?t=1538053
Does the new update have something to do with our mf3 baseband like SELinux?
Click to expand...
Click to collapse
This worked for me! But I skipped all the steps in the beginning. They sounded useless to me. Rerouting to unroot? Hah
I deleted all busybox files and was left with 3 files then went to SuperSU and did the full unroot and restart.
I check with root checker and installed SuperSU as well. Root checker said I have no root and SuperSU fails. Status is official.
Going to restart a few times to be sure.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
WezzleD said:
This worked for me! But I skipped all the steps in the beginning. They sounded useless to me. Rerouting to unroot? Hah
I deleted all busybox files and was left with 3 files then went to SuperSU and did the full unroot and restart.
I check with root checker and installed SuperSU as well. Root checker said I have no root and SuperSU fails. Status is official.
Going to restart a few times to be sure.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Nice! Thank you. Looks like 4 confirmed. Also, was SuperSU on v1.60?
haremmon said:
Nice! Thank you. Looks like 4 confirmed. Also, was SuperSU on v1.60?
Click to expand...
Click to collapse
I'm actually not sure. Didn't look at version numbers.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
4 confirmed. Let's get 5 and I will post a how to.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
ou812bkewl said:
I fully un-rooted using the method in my post here - http://forum.xda-developers.com/showthread.php?p=44495559 . For me, it just threw the custom-lock icon boot up screen and showed "Custom" status in the "About Phone" menu when using the SuperSU's un-root method.
The problem was busy box. The MF3 root scripts install Busybox files into the /xbin directory, but SuperSU's "full unroot" doesn't touch Busybox's files. Not even any Busybox apps can remove those files.
Click to expand...
Click to collapse
That method worked for me also. I'm so glad it was discovered. Successfully unrooted.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
5!
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
5!
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was able to unlock as well. However my phone stopped showing the custom unlocked symbol at bootup a few days ago (before doing this) and I am at a loss as to why. So I am not sure I can count as a real confirmation.
I did your unroot process, root checker confirms I no longer have root and the unlock symbol has not come back.
Stay tuned guys. Getting everything ready to quickly make a more organized how to.
Being horribly sick is not helping
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app