So all of sudden, my rooted S3 is not rooted anymore.
I wanted to use Titanium Backup and it says
"Sorry, I could not acquire root privileges. This application will *not* work! Pleasre verify that your ROM is rooted, and try again.
This attempt was made using the "/system/xbin/su" command."
and then I tried my other root applications such as Greenify, App Ops and they are all saying my phone isn't rooted anymore.
I don't understand, I never upgraded my phone after I rooted and I never flashed a different rom and kept the Touchwiz Rom.
I used this guide to root my phone originally:
http://forum.xda-developers.com/showthread.php?t=1771687
My phone is running 4.3 Android (Same Version I used when Rooted in the first place)
Baseband Version: T999UVUEMJC
Please let me know what to do
check if supersu is working properly.
Cronoss said:
check if supersu is working properly.
Click to expand...
Click to collapse
It isn't.
The following message pops up:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
magic132131 said:
It isn't.
The following message pops up:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
Click to expand...
Click to collapse
My suggestion would be to back everything up and re flash root66.
Cronoss said:
My suggestion would be to back everything up and re flash root66.
Click to expand...
Click to collapse
Would I lose all my data?
In terms of re flash root66, that means simply using Odin and re-rooting my phone like I do the first time right? Would it be the same instructions too?
magic132131 said:
Would I lose all my data?
In terms of re flash root66, that means simply using Odin and re-rooting my phone like I do the first time right? Would it be the same instructions too?
Click to expand...
Click to collapse
I'm not sure if you are going to lose your data.. so that's why I said to back everything up, just in case.
And yes.. same method as before from that post.
Befoe you flash again. Try uninstalling then installing supersu again
SoulEater- said:
Befoe you flash again. Try uninstalling then installing supersu again
Click to expand...
Click to collapse
I can't uninstall supersu as it gives me no option to do so. I can only uninstall all updates that were applied but not complete remove and then install it.
I had this happen on my Tmobile Galaxy S3.
I read somewhere else on XDA that you just had to install the latest SuperSU, in zip form, from recovery mode.
I havent posted enough here to be able to post a link, but you can find it on chainfires website.
Then reboot and it should work.
Related
I am new with rooting my phone. I have used Rooted phones before, I followed http://forum.xda-developers.com/showthread.php?t=2258633 Motochopper how to. I ran into a problem. I click the superuser app that was installed onto my phone, and it tells me that "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices." I click install and it tells me there was an error. I would like to root my phone along with potentially installing CWM so that I can easily install Cyanogenmod when they release a stable verison for the S4. Also would love to install titanium backup along with some Adfree apps.
Any help would be very much appreciated.
OK, so it looks like you already have it rooted.
When super SU asks that question, dont install via CWM, tell it to just install normally.
Once you have SuperSU working, Download Rom Manager from the play store and install CWM Recovery right from within the ROM Manager app.
It will give you the option to pick between two types of CWM(ClockWorkMod). The Touch version, like its name gives you the ability to use the touch screen and not only the volume up/down + Power button.
Telling it to install normally causes it to just tell me there was an error, it also tells me it is out of date as well. Titanium Backup tells me that it cant get root access and I was never asked about it.
OK, so your phone is not rooted then.
Your going to have to try rooting it again or flashing an already rooted rom with Odin.
I just tried it again, this time it said failure after the install of the superuser.apk. I just read that one of the later updates by samsung can make it harder to root. I just got my phone and i was fully updated. What Roms, are already rooted for the S4. I am actually enjoying some of the default apps that came with the phone.
Wicked (and most ROMs that don't include the [STOCK] tag) are pre-rooted...but you'll need to ODIN a custom recovery first then flash the ROM.
If you want to stay on rooted stock, follow the steps in the "root May 7 MDL" thread to ODIN a rooted kernel, and you'll be good to go.
(You don't need root access to get a custom recovery flashed)
Basically, any of your options are pretty straightforward, but they're going to involve Odin-ing stuff.
So there isn't really a way to just root my phone without installing a custom rom?
There was before the second update, with the second update rooting got just a little bit more steps
Sent from my SGH-M919 using xda premium
movieaddict said:
There was before the second update, with the second update rooting got just a little bit more steps
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
So is there a way to keep it stock but root it? What are the other steps I would have to take. Why does Samsung not like people rooting their phones, I thought carriers were the ones that hated people rooting their phones
Spud37 said:
So is there a way to keep it stock but root it? What are the other steps I would have to take. Why does Samsung not like people rooting their phones, I thought carriers were the ones that hated people rooting their phones
Click to expand...
Click to collapse
Are you still on the MDB firmware or have you done any over the air updates? Specifically the May 7 update which is MDL. Motochopper is specifically for then older firmware (MDB) and it won't work if you are already on the updated. MDL firmware. In which case you would have to follow these instructions to acquire root.
http://forum.xda-developers.com/showthread.php?p=41162041
I usually use a market app called root checker to quickly check if I do have root.
And yes you can be rooted on stock.
Sent from my SGH-M919
lazaro17 said:
Are you still on the MDB firmware or have you done any over the air updates? Specifically the May 7 update which is MDL. Motochopper is specifically for then older firmware (MDB) and it won't work if you are already on the updated. MDL firmware. In which case you would have to follow these instructions to acquire root.
http://forum.xda-developers.com/showthread.php?p=41162041
I usually use a market app called root checker to quickly check if I do have root.
And yes you can be rooted on stock.
Sent from my SGH-M919
Click to expand...
Click to collapse
Root checker says no root. I believe it does have that over the air update installed. T Mobile updated it when they gave me the phone, because they thought I didn't really know anything about phones. I assume this means I have to follow another method to root my phone?
If you have the MDL update you have to root using the steps listed here:
http://forum.xda-developers.com/showthread.php?t=2268880
Easily done, just a few more steps.
ronin4740 said:
If you have the MDL update you have to root using the steps listed here:
http://forum.xda-developers.com/showthread.php?t=2268880
Easily done, just a few more steps.
Click to expand...
Click to collapse
This is going to sound like a dumb question but from reading all of that I need to use ODIN to install the ROOT_M919?UVUAMDL onto the phone? that should root the phone and allow me to install ROM Manager and install CWM from there right?
Also would doing this delete everything I have on my phone right now?
Spud37 said:
This is going to sound like a dumb question but from reading all of that I need to use ODIN to install the ROOT_M919?UVUAMDL onto the phone? that should root the phone and allow me to install ROM Manager and install CWM from there right?
Also would doing this delete everything I have on my phone right now?
Click to expand...
Click to collapse
No, you use Odin to install one of the recoveries. You use the recovery to install the zip ROOT_M919?UVUAMD. Personally I didn't use that file. I installed the kernel in recovery and SuperSU in recovery. And no, it won't delete things on your phone.
Atmazzz said:
No, you use Odin to install one of the recoveries. You use the recovery to install the zip ROOT_M919?UVUAMD. Personally I didn't use that file. I installed the kernel in recovery and SuperSU in recovery. And no, it won't delete things on your phone.
Click to expand...
Click to collapse
Thank you so much, I am about to go and do this. I will use the kernel you suggested since that looks like a better option, after flashing the kernal should i reboot and just use it normally for a bit and then go to recovery and flash SuperSU?
EDIT: The steps on the thread for ODIN are for installing a rooted ROM, I am assuming its still the same steps for installing a recovery instead of a rooted ROM
Spud37 said:
after flashing the kernal should i reboot and just use it normally for a bit and then go to recovery and flash SuperSU?
Click to expand...
Click to collapse
If I remember right I just flashed them both at the same time. Just make sure you do the kernel first.
---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------
Spud37 said:
EDIT: The steps on the thread for ODIN are for installing a rooted ROM, I am assuming its still the same steps for installing a recovery instead of a rooted ROM
Click to expand...
Click to collapse
The steps for Odin are for the stock rom, but yes, you use it the same way for a recovery.
Atmazzz said:
If I remember right I just flashed them both at the same time. Just make sure you do the kernel first.
---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------
The steps for Odin are for the stock rom, but yes, you use it the same way for a recovery.
Click to expand...
Click to collapse
Okay I didn't get any error using ODIN, however when I try and boot into CWM using Volume Up + Power it just goes to android recovery. Which doesn't have any of the options I need. Am I just booting up the wrong way, or did I do something wrong. I tried both the touch version and the non-touch version
Spud37 said:
Okay I didn't get any error using ODIN, however when I try and boot into CWM using Volume Up + Power it just goes to android recovery. Which doesn't have any of the options I need. Am I just booting up the wrong way, or did I do something wrong. I tried both the touch version and the non-touch version
Click to expand...
Click to collapse
2 options. uncheck auto reboot in Odin. When Odin is done, unplug your phone, pull your battery, then boot into recovery. Or .. when Odin is done and it reboots your phone, keep holding volume up to get to recovery.
Atmazzz said:
2 options. uncheck auto reboot in Odin. When Odin is done, unplug your phone, pull your battery, then boot into recovery. Or .. when Odin is done and it reboots your phone, keep holding volume up to get to recovery.
Click to expand...
Click to collapse
Thank You so much. However it now seems like I have both Super User and SuperSU installed.
How did you root? Did you install the ROOT_M919?UVUAMDL zip and install SuperSU?
sooo i was stock i took the OTA update to 4.3 mk6
i decided i didn't care about the knox counter so i rooted and custom recovery (this is the rom location http://forum.xda-developers.com/showthread.php?t=2589891) and this is the recovery location http://forum.xda-developers.com/showthread.php?t=2159652
now every thing is working (SU, Titanium Back up, and so on)
however when i try certain apps (game killer, game chi) it says i don't have root
i have searched everywhere but i am not seeing any posts about this
any help would be greatly appreciated
You could flash superSU from recovery to system...
That often corrects the issue...
Did you download superSU from the market and update it ??
Try that first....and if no change....flash this....g
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
gregsarg said:
You could flash superSU from recovery to system...
That often corrects the issue...
Did you download superSU from the market and update it ??
Try that first....and if no change....flash this....g
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
Click to expand...
Click to collapse
thanks for the help i will try this now
gregsarg said:
You could flash superSU from recovery to system...
That often corrects the issue...
Did you download superSU from the market and update it ??
Try that first....and if no change....flash this....g
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
Click to expand...
Click to collapse
i uninstalled superSU then went to the market and downloaded and updated that didn't work it was still the same
no i have downloaded and installed from customer recovery and when i open superSU it says i need to manually re-root my phone so i guess i need to re flash my rom from original post?
Try installing the current version of SuperSU via Odin.. you shouldn't have to reinstall the rom...
Once SuperSU is installed, boot phone, check Play Store for updates for SuperSU and install if any. Then run SuperSU, update the binary if prompted, then when asked to disable Knox, answer yes. You should be good to go.
Zen Arcade said:
Try installing the current version of SuperSU via Odin.. you shouldn't have to reinstall the rom...
Once SuperSU is installed, boot phone, check Play Store for updates for SuperSU and install if any. Then run SuperSU, update the binary if prompted, then when asked to disable Knox, answer yes. You should be good to go.
Click to expand...
Click to collapse
okay i found it and did it and now i am back where i started most things work but the 2 app's i use most still say root permission denied (granted permission in superSU)
mrnewspaper said:
okay i found it and did it and now i am back where i started most things work but the 2 app's i use most still say root permission denied (granted permission in superSU)
Click to expand...
Click to collapse
Remove them from SU list. Restart app and approve the SU request again.....
dicksteele said:
Remove them from SU list. Restart app and approve the SU request again.....
Click to expand...
Click to collapse
okay done and no change
mrnewspaper said:
okay i found it and did it and now i am back where i started most things work but the 2 app's i use most still say root permission denied (granted permission in superSU)
Click to expand...
Click to collapse
Which apps?
Zen Arcade said:
Which apps?
Click to expand...
Click to collapse
the apps that wont work are game chi and game killer
the apps that are working looks like all of my apps that require root other then those 2
even root checker says i do have root
mrnewspaper said:
the apps that wont work are game chi and game killer
the apps that are working looks like all of my apps that require root other then those 2
even root checker says i do have root
Click to expand...
Click to collapse
Game Killer - Comments on Play Store show that this is a known issue with 4.3 and SuperSU with this app.
GameCIH - (I assume this is what you meant) Comments on Play Store also show a known issue with 4.3. Some comments from dev about enabling USB debugging, but it appears to be a 4.3 issue.
Looks like you are out of luck for now unless you step back to 4.2 or below.
Zen Arcade said:
Game Killer - Comments on Play Store show that this is a known issue with 4.3 and SuperSU with this app.
GameCIH - (I assume this is what you meant) Comments on Play Store also show a known issue with 4.3. Some comments from dev about enabling USB debugging, but it appears to be a 4.3 issue.
Looks like you are out of luck for now unless you step back to 4.2 or below.
Click to expand...
Click to collapse
i didn't see those notes but thanks to everyone for all the help and i will look in to stepping back again (i bricked the first time)
If you have the MK6 bootloader, avoid the MA4 stock package. You'll need the LJ2 stock package (which does not have a bootloader in it). See this guide... you can follow it up to the point where you have MH3 on your phone and then stop:
http://forum.xda-developers.com/showthread.php?t=2618447
Zen Arcade said:
If you have the MK6 bootloader, avoid the MA4 stock package. You'll need the LJ2 stock package (which does not have a bootloader in it). See this guide... you can follow it up to the point where you have MH3 on your phone and then stop:
http://forum.xda-developers.com/showthread.php?t=2618447
Click to expand...
Click to collapse
awesome thank you
Hello people,
I have a Note 2 (SGH-i317m) running the MVLUCMK5 Official Android 4.3 rom. I flashed the cf-autoroot from chainfire's website using odin and download mode, updated super SU as soon as the device booted, disabled Knox and got the device rooted. Root was working fine. Titanium backup could restore the app backup and everything.
However, when I restarted the phone, the root was gone. Any idea what's going on? I will have to flash CF again and it will work. But the flash counter keeps counting every flash. Is there a permanent root method for 4.3?
PS: Sorry to hijack this thread. I figured there was a relevant discussion going on, why clutter the section with a new thread. Also, since my post count is low, I couldn't post in CF's thread.
pavanchirmade said:
Hello people,
I have a Note 2 (SGH-i317m) running the MVLUCMK5 Official Android 4.3 rom. I flashed the cf-autoroot from chainfire's website using odin and download mode, updated super SU as soon as the device booted, disabled Knox and got the device rooted. Root was working fine. Titanium backup could restore the app backup and everything.
However, when I restarted the phone, the root was gone. Any idea what's going on? I will have to flash CF again and it will work. But the flash counter keeps counting every flash. Is there a permanent root method for 4.3?
PS: Sorry to hijack this thread. I figured there was a relevant discussion going on, why clutter the section with a new thread. Also, since my post count is low, I couldn't post in CF's thread.
Click to expand...
Click to collapse
Sounds like you may be using an older version of cf-auto-root? Try this one via Odin:
main - http://autoroot.chainfire.eu/
i317m - http://download.chainfire.eu/279/CF-Root/CF-Auto-Root/CF-Auto-Root-t0ltecan-t0ltevl-sghi317m.zip
Zen Arcade said:
Sounds like you may be using an older version of cf-auto-root? Try this one via Odin:
main - http://autoroot.chainfire.eu/
i317m - http://download.chainfire.eu/279/CF-Root/CF-Auto-Root/CF-Auto-Root-t0ltecan-t0ltevl-sghi317m.zip
Click to expand...
Click to collapse
I flashed the same one.
Are you running the stock kernel?
After you flash cf-auto-root and boot phone, what do the contents of this file look like?
/system/etc/install-recovery.sh
Does it reference SuperSU and run daemonsu or does it reference recovery-from-boot.p ?
Zen Arcade said:
Are you running the stock kernel?
After you flash cf-auto-root and boot phone, what do the contents of this file look like?
/system/etc/install-recovery.sh
Does it reference SuperSU and run daemonsu or does it reference recovery-from-boot.p ?
Click to expand...
Click to collapse
Here's a screenshot.
That's the correct file...
A deeper dive would involve looking at the permissions and properties of su and daemonsu in /system/xbin as well as a few other SuperSU related files in /system and subdirectories.
If you are running a custom kernel it's possible that it is pushing an older version of SuperSU (or other superuser app).
Do you have only the SuperSU app installed (i.e. no SuperUser or other app in the app drawer)?
Reaching at this point as it's not typical for the current versions of SuperSU to lose root.
One thing you can try is root with current, boot phone, immediately run SuperSU, choose "Full Unroot", reboot boot phone, then shutdown and reflash cf-auto-root and see if it sticks.
As for flash counter, once you get root to stick, you can use Triangle Away to reset that to zero - works for everything but the knox warranty counter.
Hi All!
I'm stuck in the state where I cannot complete root after update. I have no idea why this happened. I used autoroot first time on a stock. Everything worked like a charm. However In order to install update I have installed xposed and few modules to hide reset flag. After that I was able to update stock. Problem is that after this running autoroot and installing stock recover does not help. I not getting root despite the fact that I see instalation successfully completed and other people report success.
So question is - were to get SU binaries for P600 and where to put them? I'm able to reboot in TWRP using ADB if this matter.
I would also glad to reflush latest stock, but I do not know how to do it, because KIES says i'm up to date.
Any help will be greatly appreciated.
CNemo7539 said:
Hi All!
I'm stuck in the state where I cannot complete root after update. I have no idea why this happened. I used autoroot first time on a stock. Everything worked like a charm. However In order to install update I have installed xposed and few modules to hide reset flag. After that I was able to update stock. Problem is that after this running autoroot and installing stock recover does not help. I not getting root despite the fact that I see instalation successfully completed and other people report success.
So question is - were to get SU binaries for P600 and where to put them? I'm able to reboot in TWRP using ADB if this matter.
I would also glad to reflush latest stock, but I do not know how to do it, because KIES says i'm up to date.
Any help will be greatly appreciated.
Click to expand...
Click to collapse
Have you tried updating Supersu from play store
lsherif said:
Have you tried updating Supersu from play store
Click to expand...
Click to collapse
Yes, I did. It says that binaries are not found.
CNemo7539 said:
Yes, I did. It says that binaries are not found.
Click to expand...
Click to collapse
Have you tried flashing SU zip? You should be good to go after flashing :good:
http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
22sl22 said:
Have you tried flashing SU zip? You should be good to go after flashing :good:
http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
Click to expand...
Click to collapse
Thank you! Now I'm rooted again!
I have searched the forums for my device, and other people's posts trying to find a way to root my device. Towelroot did not work for me. I read that i could install Philz touch recovery and root with that, but i cannot find the version of that for my phone. If somebody could point me in the direction of a method to root my phone, i would very much appreciate it
The Cheese Deity said:
I have searched the forums for my device, and other people's posts trying to find a way to root my device. Towelroot did not work for me. I read that i could install Philz touch recovery and root with that, but i cannot find the version of that for my phone. If somebody could point me in the direction of a method to root my phone, i would very much appreciate it
Click to expand...
Click to collapse
You could download GooManager (or Flashify) off the Play Store, install custom recovery (TWRP) and root. It will install the one for your phone automatically.
You need root to use GooManager.
Im curious, what happened with Towelroot? I cant see any reason it wouldnt work. Can you tell me the steps you used?
DocHoliday77 said:
You need root to use GooManager.
Im curious, what happened with Towelroot? I cant see any reason it wouldnt work. Can you tell me the steps you used?
Click to expand...
Click to collapse
I downloaded the towelroot apk, installed it and clicked "make it rain" and the app said i should have root. I downloaded root checker and it says i do not have root access.
After running Towelroot You have to install SuperSU from the Play Store, then open the app and let it update the binary and disable Knox.
If SuperSU hangs, reboot and it'll work on the second try.
DocHoliday77 said:
After running Towelroot You have to install SuperSU from the Play Store, then open the app and let it update the binary and disable Knox.
If SuperSU hangs, reboot and it'll work on the second try.
Click to expand...
Click to collapse
I had tried CF-Auto-Root before towelroot, and it seems to have either partially installed SuperSU, or SuperSU just doesn't like my phone. It shows up in my app list as "eu.chainfire.supersu.MainActi" and force closes when i try to open it. I cannot uninstall it. (i should have mentioned this in my OP maybe)
Oh ok. That makes more sense to me for why Towelroot didn't work then. Probably the easiest fix would be to reflash the firmware with Odin, then try Towelroot first. Since you dont have root now, its going to make fixing the problem any other way near impossible.......actually, now that I said that, you could flash twrp recovery, then use its file manager to manually delete any traces of the failed root.
Still, I think the firmware flash is an easier and safer option. But its up to you how you want to proceed.
DocHoliday77 said:
Oh ok. That makes more sense to me for why Towelroot didn't work then. Probably the easiest fix would be to reflash the firmware with Odin, then try Towelroot first. Since you dont have root now, its going to make fixing the problem any other way near impossible.......actually, now that I said that, you could flash twrp recovery, then use its file manager to manually delete any traces of the failed root.
Still, I think the firmware flash is an easier and safer option. But its up to you how you want to proceed.
Click to expand...
Click to collapse
I successfully flashed TWRP, exactly what files should i delete?
Check the cf autoroot thread to be sure, but probably the su binary, install-recovery.sh, daemonsu, etc.
DocHoliday77 said:
Check the cf autoroot thread to be sure, but probably the su binary, install-recovery.sh, daemonsu, etc.
Click to expand...
Click to collapse
The recovery file manager does not see a lot of the files on my phone. It does see the SuperSU folder, but even if i delete or rename it, it just fixes itself upon reboot. I'm thinking of flashing the 4.4.2 firmware through odin, is a factory reset absolutely necessary to do that?
I flashed the firmware, ran towelroot, installed SuperSU, installed the binary, disabled Knox, and i am now running a rooted device!
Thank you very much DocHoliday77 for all of your help, i greatly appreciate it.
Which firmware did you reflash? Stock 4.4.2??
I cannot find towelroot on the app store. Are there any suggestions on what to do without towelroot
Hi friendly xda android enthusiasts. I have, after many issues, finally rooted my gt-n5110 using odin and cf-auto. Workered without a hitch. Odin passed, tab rebooted, and BAM, "superSU has stopped working". I immediately navigated myself over to the playstore to reinstall SuperSU and for the first time i have ever seen it wouldnt allow me to. It only gave me a choice to open. No update no uninstall. Going into my apps list it was not present on downloads but was available on device list. Clucked it and no option to uninstall, only to force stop or turn off. So it is incorporated as a system with no access to it. This has me stumped. I have only seen old threads with answers to this and they are temp fixes. Need to know what i can do to fix this on a permanent basis and if someone could help me understand how and why this issue occured it would give me a better understanding and possibly prevent further issues. Thanks in advance guys.
Try the flashable version in this post after you install a custom recovery with odin.
ramjet73
ramjet73 said:
Try the flashable version in this post after you install a custom recovery with odin.
ramjet73
Click to expand...
Click to collapse
This may be a very stupid question but i have to be sure. As i stated the odin DID pass the auto root and tab rebooted. But along with the superSU error i ran root checker and was unable to obtain root. Im assuming its because supersu is not embedded. So with that said is it still ok to attempt to flash a recovery to the tab?
mattdiehl83 said:
This may be a very stupid question but i have to be sure. As i stated the odin DID pass the auto root and tab rebooted. But along with the superSU error i ran root checker and was unable to obtain root. Im assuming its because supersu is not embedded. So with that said is it still ok to attempt to flash a recovery to the tab?
Click to expand...
Click to collapse
Yes. Recovery is independent of whether or not you are rooted. You can install it from Android using tools like Flashify once you are properly rooted, but Odin works fine as long as you have a version of recovery in that format.
Flashing SuperSU from a custom recovery once it is installed should fix the superuser problems you are having.
ramjet73
ramjet73 said:
Yes. Recovery is independent of whether or not you are rooted. You can install it from Android using tools like Flashify once you are properly rooted, but Odin works fine as long as you have a version of recovery in that format.
Flashing SuperSU from a custom recovery once it is installed should fix the superuser problems you are having.
ramjet73
Click to expand...
Click to collapse
Doing now. Thankyou. Fingers crossed.
I had the same issue on my 5110. The flashable root only worked for me until I rebooted, then it would lose root. What ultimately worked for me was to unroot with Kingo. Then with USB debugging enabled, re-rooted with Kingo (which took around 10 min).
Sent from my AT&T Galaxy Note 3 using Tapatalk®
andygev35 said:
I had the same issue on my 5110. The flashable root only worked for me until I rebooted, then it would lose root. What ultimately worked for me was to unroot with Kingo. Then with USB debugging enabled, re-rooted with Kingo (which took around 10 min).
Click to expand...
Click to collapse
If flashing SuperSU from recovery doesn't result in a successful rooted system someone should let @Chainfire know. I've never had a problem rooting a stock ROM that way but let's see what @mattdiehl83 reports.
ramjet73
OS X
ramjet73 said:
If flashing SuperSU from recovery doesn't result in a successful rooted system someone should let @Chainfire know. I've never had a problem rooting a stock ROM that way but let's see what @mattdiehl83 reports.
ramjet73
Click to expand...
Click to collapse
Not near pc. Only have OS X available now. Can anybody walk me through using OS X to flash?
mattdiehl83 said:
Not near pc. Only have OS X available now. Can anybody walk me through using OS X to flash?
Click to expand...
Click to collapse
The recovery? I don't know if there is an OS X version of Odin.
ramjet73
ramjet73 said:
The recovery? I don't know if there is an OS X version of Odin.
ramjet73
Click to expand...
Click to collapse
I am wondering what flashing tool to use with OS X. Odin is for windows. I know of heimdall but that requires ALOT to flash anything. Wondering if there is another odin like tool for OS X
You could try this: http://forum.xda-developers.com/showthread.php?t=2598203
Sent from my AT&T Galaxy Note 3 using Tapatalk®
done.
Hi guys sorry for the delay in update. I ended up using VM ware and it allowed to operate as windows on OS X. I installed TWRP, went into the file manager in TWRP and removed the superSU, i then flashed superSU and rebooted. Once back to the tablet i went and restored services to superSU and went into the play store. And finally the playstore gave me the option the update the superSU. And then the rest was all normal installation of superSU. Hope this thread helps anybody dealing with these issues.
Glad you got it working. :good:
This post in the CF-Autoroot thread might be helpful as well.
ramjet73
there is a easy way to fix it!
download supersu 2.02 and install ta da and it works
2.01 does not work with n5110 well if you flash cf auto root
hmmmm.....
Bordo_Bereli51 said:
there is a easy way to fix it!
download supersu 2.02 and install ta da and it works
2.01 does not work with n5110 well if you flash cf auto root
Click to expand...
Click to collapse
Tada..your a genius. Oh wait i believe i stated it didnt have that option it was disabled. Yes i decided scarcasm would be fitting due to the fact it says ALL OVER xda to please read before you post.
mattdiehl83 said:
Tada..your a genius. Oh wait i believe i stated it didnt have that option it was disabled. Yes i decided scarcasm would be fitting due to the fact it says ALL OVER xda to please read before you post.
Click to expand...
Click to collapse
I read all the post and didnt found something
YOU DONT NEED TO DELETE SUPERSU 2.0.1
Install 2.02 apk and go to supersu, then to settings and push to /system
This is the easiest way. the one you found: go to recovery delete that and this. download supersu 2.0.2 apk and install it not the recovery zip i mean the APK! i didnt say the flashable supersu zip.
oh wait, yes you are a intelligent boy, you know everything.
mattdiehl83 said:
I am wondering what flashing tool to use with OS X. Odin is for windows. I know of heimdall but that requires ALOT to flash anything. Wondering if there is another odin like tool for OS X
Click to expand...
Click to collapse
That's a bit of a dilemma.
Unfortunately Samsung does not support using fastboot and bootloader mode (they call it download mode) so that standard SDK tool Google provides for Windows, Linux and MAC OS X isn't applicable. Your best bet would be to find a Windows PC that you can use to flash the recovery with Odin since that is the most common and best documented method.
Edit: NVM, somehow I responded to an old post of yours.
ramjet73