I tried to do this and I bricked my old phone. I don't wanna run the risk of doing it again. If anyone in the south Florida area can help me out. By rooting and installing a recovery so I can flash ROMs I would appreciate it. Please let me know.
Sent from my SM-N900V using XDA Free mobile app
marshall_634 said:
I tried to do this and I bricked my old phone. I don't wanna run the risk of doing it again. If anyone in the south Florida area can help me out. By rooting and installing a recovery so I can flash ROMs I would appreciate it. Please let me know.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
It's very simple, just download TowelRoot, SafeStrap and SuperUser. Install TowerRoot, hit root then wait for the device to reboot. Then install SU, open it and hit update binaries (normal method) and then install SS, grant it SU permisions and hit install recovery.
airmaxx23 said:
It's very simple, just download TowelRoot, SafeStrap and SuperUser. Install TowerRoot, hit root then wait for the device to reboot. Then install SU, open it and hit update binaries (normal method) and then install SS, grant it SU permisions and hit install recovery.
Click to expand...
Click to collapse
I got them. Running SU and it is stuck on the disabling KNOX. Do I just wait.
Sent from my SM-N900V using XDA Free mobile app
I keep getting this.
Sent from my SM-N900V using XDA Free mobile app
marshall_634 said:
I keep getting this.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
Have you rebooted a few times?
airmaxx23 said:
Have you rebooted a few times?
Click to expand...
Click to collapse
Yes.
Sent from my SM-N900V using XDA Free mobile app
marshall_634 said:
Yes.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
Install BusyBox from the Play Store, open it and install BusyBox, then try SU again.
airmaxx23 said:
Install BusyBox from the Play Store, open it and install BusyBox, then try SU again.
Click to expand...
Click to collapse
Busy box asked for SU permission. I granted it. Install was sucussfull. Then went back to SU to install bianary . no luck. What am I doing wrong.
Sent from my SM-N900V using XDA Free mobile app
marshall_634 said:
Busy box asked for SU permission. I granted it. Install was sucussfull. Then went back to SU to install bianary . no luck. What am I doing wrong.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
Try the newest SU, delete the one on your phone. download THIS file, unzip it, go to the common folder and install that SU app.
airmaxx23 said:
Try the newest SU, delete the one on your phone. download THIS file, unzip it, go to the common folder and install that SU app.
Click to expand...
Click to collapse
Nope still no luck. The first time I ran SU it asked to bypass Samsung KNOX. Could that be the issue. I said yes to bypass.
Sent from my SM-N900V using XDA Free mobile app
marshall_634 said:
Nope still no luck. The first time I ran SU it asked to bypass Samsung KNOX. Could that be the issue. I said yes to bypass.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
Did it install the SU binaries before you saw the KNOX notification?
airmaxx23 said:
Did it install the SU binaries before you saw the KNOX notification?
Click to expand...
Click to collapse
It was in the middle of installing the binaries. So am I OK to install saftstrap recovery?
Sent from my SM-N900V using XDA Free mobile app
marshall_634 said:
It was in the middle of installing the binaries. So am I OK to install saftstrap recovery?
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
Try it and see if you can grant SU permissions when you open the app.
airmaxx23 said:
Try it and see if you can grant SU permissions when you open the app.
Click to expand...
Click to collapse
It installed and I made a backup of the stock rom. But I saved it to my internal memory. Will that be affected when I install custom ROM.
marshall_634 said:
It installed and I made a backup of the stock rom. But I saved it to my internal memory. Will that be affected when I install custom ROM.
Click to expand...
Click to collapse
It's best to place the backups on an external SDcard, that way if something happens and you need to flash a tar file in odin the backup is safe.
I'm glad you got it rooted, enjoy.
airmaxx23 said:
It's best to place the backups on an external SDcard, that way if something happens and you need to flash a tar file in odin the backup is safe.
I'm glad you got it rooted, enjoy.
Click to expand...
Click to collapse
My phone is running soooo slow. Programs wont open and keep getting force close popups. How can I revert back to full stock not rooted.
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.
when trying to install apps via titanium backup , the error i get is sorry i could not require root privileges.. please verify your rom is rooted, includes busybox and try again.... this attempt was made using /system/xbin/su
how can i fix this
when i click problems, it only allows me to upgrade SU.. not busybox. Im on the strike 1.0.3 aosp rom 4.0.3
Try clearing your app data for superuser permissions.
I got that error twice, after accidentally selecting "no" when it asked for root and on one of the last updates for titanium backup.
This was the solution in each case, just be sure to re-approve all if your other program's that request root.
Sent from my PC36100 using xda app-developers app
jfortier16 said:
Try clearing your app data for superuser permissions.
I got that error twice, after accidentally selecting "no" when it asked for root and on one of the last updates for titanium backup.
This was the solution in each case, just be sure to re-approve all if your other program's that request root.
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
What ROM are you running?? Did you go into SU and toggle permissions on?
I ran into a similar issue recently while trying to play with a JB ROM. I updated my su binary through Superuser and everything worked fine afterwards
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.
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
hey guys. I need help on this. and I'm also questioning it, I'm running 4.3 pac rom and I'm when I use the superSU app I have to flash it through rom manager. but if I reboot into recovery and then push reboot I get this option to.. fix root (system/xbin/su/ or it no then it says go back. CANT SOMEONE HELP ME ON THIS. PLEASE AND THANK YOU!
Sent from my Nexus 4 using XDA Premium 4 mobile app
gabriel31012 said:
hey guys. I need help on this. and I'm also questioning it, I'm running 4.3 pac rom and I'm when I use the superSU app I have to flash it through rom manager. but if I reboot into recovery and then push reboot I get this option to.. fix root (system/xbin/su/ or it no then it says go back. CANT SOMEONE HELP ME ON THIS. PLEASE AND THANK YOU!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My friend take a moment and look at the zip file you are flashing then notice what your are pushing over. Within the zip file there are multiple files being installed to your system as opposed to you only pushing over one file. Always good practice to check out what you are flashing
Push everything over and fix permissions if needed
but it's not a zip file. I know that this rom cones pre installed with the super user setting in the settings but I'm using the app. but when I click on it the app tells me that I have to update something so when I did normal it says failed try flashing in cwm or custom recovery. so when I do custom recovery. but even time I reboot into recovery says what I said about.
Sent from my Nexus 4 using XDA Premium 4 mobile app