Related
I'm in need of some help, I'm rooted or so i'm lead to believe, I used wugfresh's method http://forum.xda-developers.com/showthread.php?t=1766475 and everything seemed to work as planed but when i try to use TB or rom toobox it tells me I don't have root. I also tried root check and that comes back telling me I don't have proper root access. Can someone show me some love and help me out.
Thanks.
njswift10141980 said:
I'm in need of some help, I'm rooted or so i'm lead to believe, I used wugfresh's method http://forum.xda-developers.com/showthread.php?t=1766475 and everything seemed to work as planed but when i try to use TB or rom toobox it tells me I don't have root. I also tried root check and that comes back telling me I don't have proper root access. Can someone show me some love and help me out.
Thanks.
Click to expand...
Click to collapse
Install busybox installer from the market and install/update busybox. See if that fixes your issues. Also try installing SuperSu from the market, opening it, and updating su binary when it opens.
Did you run the busybox free app?
Sent from my Nexus 7 using xda premium
Metallice said:
Install busybox installer from the market and install/update busybox. See if that fixes your issues. Also try installing SuperSu from the market, opening it, and updating su binary when it opens.
Click to expand...
Click to collapse
I installed busybox installer and when I try to install/update it says it failed. As for SuperSu, it doesn't give me an option to update the su binary.
ScipioWarrior said:
Did you run the busybox free app?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I ran busybox free and it says it's unable to verify whether or not certain utilities needed for this app to run are present and functional on my device. This problem could be caused by a device that is not properly rooted or by superuser settings that are misconfigured
njswift10141980 said:
I'm in need of some help, I'm rooted or so i'm lead to believe, I used wugfresh's method http://forum.xda-developers.com/showthread.php?t=1766475 and everything seemed to work as planed but when i try to use TB or rom toobox it tells me I don't have root. I also tried root check and that comes back telling me I don't have proper root access. Can someone show me some love and help me out.
Thanks.
Click to expand...
Click to collapse
Likely not but thought i'd ask - Did you update to 4.1.1 after initially rooting?
Sent from my Nexus 7 using Tapatalk 2
Did you have the apps that use root before you rooted? I've noticed with some apps (that work with and without root) sometimes dont register that root is installed on your device so perhaps you should try redownloading them from the play store.
animatechnica said:
Likely not but thought i'd ask - Did you update to 4.1.1 after initially rooting?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I installed the update after rooting.
jonnyg1097 said:
Did you have the apps that use root before you rooted? I've noticed with some apps (that work with and without root) sometimes dont register that root is installed on your device so perhaps you should try redownloading them from the play store.
Click to expand...
Click to collapse
I've had the apps for a while on my droid x but I waited until after I rooted to also install them on the N7. I also tried uninstalling them and reinstalling them but they still don't work.
njswift10141980 said:
Yes, I installed the update after rooting.
I've had the apps for a while on my droid x but I waited until after I rooted to also install them on the N7. I also tried uninstalling them and reinstalling them but they still don't work.
Click to expand...
Click to collapse
When you take an update it unroots your device. Re-root it with the tool and you'll be fine.
neilrl79 said:
When you take an update it unroots your device. Re-root it with the tool and you'll be fine.
Click to expand...
Click to collapse
He should've used voodoo over the air rootkeeper to back up n save his root. So once you update, you can easily restore rot with one click in that app instead of having to use roottoolkit again.
neilrl79 said:
When you take an update it unroots your device. Re-root it with the tool and you'll be fine.
Click to expand...
Click to collapse
I feel like a moron especially since I froze the updater on my droid x, I'll give it a try when I get home from work, is there anything special I should do or will I just have to click the root button?
demandarin said:
He should've used voodoo over the air rootkeeper to back up n save his root. So once you update, you can easily restore rot with one click in that app instead of having to use roottoolkit again.
Click to expand...
Click to collapse
I will have to look at this app.
I will report back later.
Just rerooted and it looks like everything is working, thanks everybody
I have a Galaxy Tab 10.1 (PT-7500R from Rogers), trying to root on the new official ICS.
I have followed the directions at http://forum.xda-developers.com/showthread.php?t=1239185
CWM installed and works fine. After applying "Samsung_Galaxy_Tab_10.1_root.zip" in CWM, I boot into Android, I see SuperUser in my app menu and can bring up its interface.
However, when I try to launch a su-required function (such as Reboot Recovery in ROM Manager), I don't get a prompt for SU permissions.
I have tried this with both OTA and manual (Odin3) installs of the official ICS from Rogers, from unrooted stock Honeycomb, several times.
I don't encounter this problem with stock Honeycomb... rooting that version appears to work fine.
I have experimented with some community builds, perhaps I have installed an incompatible kernel that needs replacing? I don't know, but any advice would be greatly appreciated.
Regards,
diggerB
diggerb said:
I have a Galaxy Tab 10.1 (PT-7500R from Rogers), trying to root on the new official ICS.
I have followed the directions at http://forum.xda-developers.com/showthread.php?t=1239185
CWM installed and works fine. "After applying Samsung_Galaxy_Tab_10.1_root.zip" in CWM, I boot into Android, I see SuperUser in my app menu and can bring up its interface.
However, when I try to launch a su-required function (such as Reboot Recovery in ROM Manager), I don't get a prompt for SU permissions.
I have tried this with both OTA and manual (Odin3) installs of the official ICS from Rogers, from unrooted stock Honeycomb, several times.
I don't encounter this problem with stock Honeycomb... rooting that version appears to work fine.
I have experimented with some community builds, perhaps I have installed an incompatible kernel that needs replacing? I don't know, but any advice would be greatly appreciated.
Regards,
diggerB
Click to expand...
Click to collapse
Have you tried to see if superuser had an update in the market? I recommend to also make sure the binary is up to date in the superuser app.
Sent from my SAMSUNG-SGH-I747 using xda premium
nakedninja42 said:
Have you tried to see if superuser had an update in the market? I recommend to also make sure the binary is up to date in the superuser app.
Click to expand...
Click to collapse
Thank you for your reply.
I updated to the latest version in Play Store, it shows Binary v2.3.1-ef , update check shows latest version 3.1.1 but when I click Update, it fails on the step "Gaining root access..."
Cheers
diggerB
You're not rooted anymore. The superuser app is there but it can't do anything since the su is missing. You have to re-root.
Sent from my GT-I9300 using Tapatalk 2
Tyxerakias said:
You're not rooted anymore. The superuser app is there but it can't do anything since the su is missing. You have to re-root.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the feedback... but I just went back into CWM and applied the root again, still in exactly the same boat.
Thanks to all, I found a solution in another thread: http://forum.xda-developers.com/showthread.php?p=31179418#post31179418
Superuser just didn't want to work. The SuperSU root method referred by the OP in that thread worked great. All is well again. Until next time of course.
Hi, if you go to "www.galaxytabhacks.com" you will find the solution, there is an upgrade to superuser.
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.
I downloaded and flashed a fresh version of stock 4.3, and installed the supersu zip file through CWM. now i have a working device that is supposedly rooted.
my problem is that something is causing root privileges to do some weird things. I enabled root file manager on the rhythm software file manager, and it suddenly cant access my data on the internal SD card, but when i disable root for it, i can see the stuff fine.
As well, when i try to start Hola using Root, it starts, then flashes several times and stops.
Apps ask for root permissions fine, and it grants them fine, but they just aren't working right.
I have tried re-downloading and flashing a couple different versions of supersu through CWM, including the newest, v1.43.
Is this something that can be fixed, or will i need to start from scratch again?
Hey,
Got the same thing for getting to my sdcard content. Get to it thru /mnt/sdcard instead of /sdcard. This works for me with rooted 4.3.
Cheers
Sent from my Nexus 4 using xda app-developers app
Ricx94 said:
I downloaded and flashed a fresh version of stock 4.3, and installed the supersu zip file through CWM. now i have a working device that is supposedly rooted.
my problem is that something is causing root privileges to do some weird things. I enabled root file manager on the rhythm software file manager, and it suddenly cant access my data on the internal SD card, but when i disable root for it, i can see the stuff fine.
As well, when i try to start Hola using Root, it starts, then flashes several times and stops.
Apps ask for root permissions fine, and it grants them fine, but they just aren't working right.
I have tried re-downloading and flashing a couple different versions of supersu through CWM, including the newest, v1.43.
Is this something that can be fixed, or will i need to start from scratch again?
Click to expand...
Click to collapse
have you tried updating to the newest superSU to version 1.44 in the playstore ? should've been the first thing you did after flashing 1.43 as it fixes alot of the root problems
Sgace said:
Hey,
Got the same thing for getting to my sdcard content. Get to it thru /mnt/sdcard instead of /sdcard. This works for me with rooted 4.3.
Cheers
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Nope...doesn't work as it redirects to the same place. There is a single file there that is unreadable named 0 and its 0kb, same as what I currently see
paul_viado said:
have you tried updating to the newest superSU to version 1.44 in the playstore ? should've been the first thing you did after flashing 1.43 as it fixes alot of the root problems
Click to expand...
Click to collapse
That was the first thing i tried as well. i also did a cleanup and reinstalled from the play store several times hoping it would work, but nothing. SuperSU seems to think i am rooted, because it doesn't complain about the binaries or anything, it simply grants permissions, but the permissions don't work right.
https://plus.google.com/113517319477420052449/posts/7o5H214hRSv
Sent from my Nexus 4 using xda premium
stuart0001 said:
https://plus.google.com/113517319477420052449/posts/7o5H214hRSv
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
tried installing newest version, didn't have any effect. i think I'll just flash a new ROM onto the phone...maybe cyanogenmod 10.1.2
Thanks you guys for the help, though.
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