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
Related
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 just tried getting root access via this guide using Odin, but although I've already updated the firmware first, it just doesn't take. It installs the superSU app, but not the binary it seems. Any idea where I can get it from? I also tried superuser instead, which allows me to get an up to date binary, but when it then tries to install the binary it fails.
Here's the guide I followed:
http://m.ibtimes.co.uk/galaxys4-gti9505-official-android422-xxuadmn-jellybean-firmware-464478.html
Any ideas?
XXUAMDM Root not possible?
Hi,
have done the same, tried to root the I9505 XXUAMDM (European LTE model) - there was no SU installed.
Therefore I installed the SuperSU from the market and checked, but it says that the SU Binaries are missing...
So what went wrong with rooting? Any suggestions
BTW: After the start of Titanium Backup the window asking about root for the app appeared.
Now starting Super SU I can see Titanium in the list, but short after start the mentioned "SU-Binary missing" window appears...
jochenthomas said:
Hi,
have done the same, tried to root the I9505 XXUAMDM (European LTE model) - there was no SU installed.
Therefore I installed the SuperSU from the market and checked, but it says that the SU Binaries are missing...
So what went wrong with rooting? Any suggestions
Click to expand...
Click to collapse
Exactly the same as me, the update went fine, the rooting seemed to go fine too, but the binary is supposedly missing.
Just been pointed to this thread, which works a treat:
http://forum.xda-developers.com/showthread.php?t=2255190&nocache=1
It seems the method we used isn't compatible with the MDM and MDN firmware updates, so need to use a modified version of CF auto root instead. In that thread it also shows you how to reset the flash counter too! Result!
StuartTheFish said:
I just tried getting root access via this guide using Odin, but although I've already updated the firmware first, it just doesn't take. It installs the superSU app, but not the binary it seems. Any idea where I can get it from? I also tried superuser instead, which allows me to get an up to date binary, but when it then tries to install the binary it fails.
Here's the guide I followed:
http://m.ibtimes.co.uk/galaxys4-gti9505-official-android422-xxuadmn-jellybean-firmware-464478.html
Click to expand...
Click to collapse
I know your sorted ow but out of interest before were you using steps outlined here when it didn't work on mdm
http://androidjinn.com/root-xxuamdm-android-4-2-2-on-galaxy-s4-i9505-official-firmware.html/2
Sent from my GT-I9505 using xda app-developers app
topcat07 said:
I know your sorted ow but out of interest before were you using steps outlined here when it didn't work on mdm
http://androidjinn.com/root-xxuamdm-android-4-2-2-on-galaxy-s4-i9505-official-firmware.html/2
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Different guide, but same method. We simply needed a modified file t work on the newer firmware.
StuartTheFish said:
Different guide, but same method. We simply needed a modified file t work on the newer firmware.
Click to expand...
Click to collapse
Strange someone has got it working with normal file
Sent from my GT-I9505 using xda app-developers app
topcat07 said:
Strange someone has got it working with normal file
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Pass, don't know! All I do know is the regular cf auto root didn't work for me on this firmware, but the modified one did.
StuartTheFish said:
Just been pointed to this thread, which works a treat:
http://forum.xda-developers.com/showthread.php?t=2255190&nocache=1
It seems the method we used isn't compatible with the MDM and MDN firmware updates, so need to use a modified version of CF auto root instead. In that thread it also shows you how to reset the flash counter too! Result!
Click to expand...
Click to collapse
OMFG I have googled and torn my hair our for hours and hours as I just could not get root on my MDM S4 using the methods detailed on this site, this modified file rooted it straight away with no problems. It REALLY needs to be shouted a bit louder lol !
Thanks all.
this doesnt work for i9500
this kernel does not root i9500.
anyway i have a different problem and its about bluetooth. is this the proper place or should i search elsewhere?
No, there's a different method to rooting for a gt19500.
Thanks
Hey guys.
I updated to 4.3 (MK2) and kept root with Survival Mode, everything went smooth. Except now when i boot the phone the splash screen shows a litle padlock icon unlocked and says "unnofical" underneath it.. My questions are:
1. What does that mean?
2. What can AT&T find out from that?
3. How can we get rid of this.. it is kind of unnerving when i see it.
Thanks guys
It means you have modified your system. ie: root
That your device has been modified. Again, root. Your warranty is only void. That is all that can happen.
I am not sure of any method to remove it on MK2. Maybe triangle away. I suggest doing a ton of reading.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
It means you have modified your system. ie: root
That your device has been modified. Again, root. Your warranty is only void. That is all that can happen.
I am not sure of any method to remove it on MK2. Maybe triangle away. I suggest doing a ton of reading.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This.
IF you still have root because you used survival mode, you can actually go ahead and uninstall SuperSU, and reinstall it and update the Database, and reboot your device TWICE, this usually does the trick.
I would suggest at least trying it before the triangle away crap.
Also. If SuperSU is installed as a system app, just use a root uninstaller from the play store and reinstall it and then update the DB.
I downloaded the update for my note 3 but now I am having second thoughts on installing. How can I stop this update from happening. I keep delaying it. Thanks
Sent from my unrooted note 3
What update are you referring to
Sent from One Bad Ass Note 3
The software update kitkat
Sent from my SM-N900V using xda app-developers app
simp dogg said:
The software update kitkat
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Verizon hasn't released kit-kat for the note 3 yet...
Sent from my SM-N900V using Tapatalk
What base do you currently have installed?
Sent from my SM-N900V using Tapatalk
The update was MJ7 to MJE. I wasn't sure what update it was when I downloaded it. I am sorry coming off like newb. What does MJE do as far as rooting? Does it make it harder to root or just an enhancement.
Sent from my SM-N900V using xda app-developers app
simp dogg said:
The update was MJ7 to MJE. I wasn't sure what update it was when I downloaded it. I am sorry coming off like newb. What does MJE do as far as rooting? Does it make it harder to root or just an enhancement.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
MJE is still rootable with kingo, then you can go ahead and install safestrap if you want.
Sent from my SM-N900V using Tapatalk
The download (a .zip file) gets dropped into the /cache folder, along with a recovery command file at
/cache/recovery/command
If you are rooted, you could just go in to the /cache folder and delete them. After that, you could look up the thread in the dev forum which details the .apk files in /system/apps which could be frozen (or "chmod 000"'ed) so that the nagging and download behavior stops. (This too requires root.)
This last bit is 100% reversible in case you later decide to apply the update, and/or you can keep the downloaded files (from /cache) in case you manually wanted to perform the update at a later time.
I don't know of a way to do this without rooting.
bftb0 said:
The download (a .zip file) gets dropped into the /cache folder, along with a recovery command file at
/cache/recovery/command
If you are rooted, you could just go in to the /cache folder and delete them. After that, you could look up the thread in the dev forum which details the .apk files in /system/apps which could be frozen (or "chmod 000"'ed) so that the nagging and download behavior stops. (This too requires root.)
This last bit is 100% reversible in case you later decide to apply the update, and/or you can keep the downloaded files (from /cache) in case you manually wanted to perform the update at a later time.
I don't know of a way to do this without rooting.
Click to expand...
Click to collapse
Well one way is to flash the pit file in Odin, or just flash a factory restore odin tar (full-wipe) but for the end user it might be easier to just root and do as you 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
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.