[Q] Am I Rooted or Not?? - Galaxy S 4 Q&A, Help & Troubleshooting

Got my shiny new Samsung Galaxy S4 on Friday and attempted to root it yesterday (I've previously rooted SGSII). I have used ODIN to flash the CF-Root.tar file (thanks Chainfire) which it seemed to do ok and came up green with "Pass" and said it had succeeded and I got the red android icon before it automatically rebooted itself but when I try to get root rights with Titanium it hangs for ages "asking for root rights" and then eventually (after about 15mins) says it couldn't access root privileges.
So everything looks ok but apparently it's not. Any ideas as to why it's (a) not rooted; or (b) Titanium can't get root access?
Thanks in advance

flipflop104 said:
Got my shiny new Samsung Galaxy S4 on Friday and attempted to root it yesterday (I've previously rooted SGSII). I have used ODIN to flash the CF-Root.tar file (thanks Chainfire) which it seemed to do ok and came up green with "Pass" and said it had succeeded and I got the red android icon before it automatically rebooted itself but when I try to get root rights with Titanium it hangs for ages "asking for root rights" and then eventually (after about 15mins) says it couldn't access root privileges.
So everything looks ok but apparently it's not. Any ideas as to why it's (a) not rooted; or (b) Titanium can't get root access?
Thanks in advance
Click to expand...
Click to collapse
Someone else has posted somewhere about the bootloader (write protection: enable). Could this be why it's not rooted even thought it appears to be?

flipflop104 said:
Got my shiny new Samsung Galaxy S4 on Friday and attempted to root it yesterday (I've previously rooted SGSII). I have used ODIN to flash the CF-Root.tar file (thanks Chainfire) which it seemed to do ok and came up green with "Pass" and said it had succeeded and I got the red android icon before it automatically rebooted itself but when I try to get root rights with Titanium it hangs for ages "asking for root rights" and then eventually (after about 15mins) says it couldn't access root privileges.
So everything looks ok but apparently it's not. Any ideas as to why it's (a) not rooted; or (b) Titanium can't get root access?
Thanks in advance
Click to expand...
Click to collapse
Check your firmware, the new build MDM can't be rooted with CF.
If you have MDM then you can use Odin and flash any of MDE or MDF builds, they can be rooted easily , or use PRE-ROOTED OFFICIAL Rom from Development Section.
flipflop104 said:
Someone else has posted somewhere about the bootloader (write protection: enable). Could this be why it's not rooted even thought it appears to be?
Click to expand...
Click to collapse
Hahahah!!
If you don't know what you're saying then don't say anything!!

djembey said:
Hahahah!!
If you don't know what you're saying then don't say anything!!
Click to expand...
Click to collapse
Hehe I'm desperate!! lol

Did you install SuperSU or SuperUser from the market yet?

djembey said:
Check your firmware, the new build MDM can't be rooted with CF.
If you have MDM then you can use Odin and flash any of MDE or MDF builds, they can be rooted easily , or use PRE-ROOTED OFFICIAL Rom from Development Section.
Click to expand...
Click to collapse
Build is JDQ39i9505XXUAMDF which I thought was ok??? No???

ChronoReverse said:
Did you install SuperSU or SuperUser from the market yet?
Click to expand...
Click to collapse
Just done it

ChronoReverse said:
Did you install SuperSU or SuperUser from the market yet?
Click to expand...
Click to collapse
SU Binary Updater
Downloading manifest... okay! (in green)
Parsing manifest.... okay! (in green)
Latest version = 3.1.1 (in green)
Checking installed version = 1.15:SUPERSU (in red)
Fixing database.... okay! (in green)
Unpacking sutools... okay! (in green)
Checking current install path... /system/xbin/su (in green)
Downloading new binary... okay! (in green)
Gaining root access
Changing su file mode to 06755...
Making sure new su works... fail! (in red)
Is this lot just confirming what I already know - not rooted??

Not rooted. Is this AT&T or Verizon?

ChronoReverse said:
Not rooted. Is this AT&T or Verizon?
Click to expand...
Click to collapse
Neither, it's from EE in the UK and is the i9505

Any further suggestions??? Please.........

ken2802 said:
try supersu, from my point of view superuser seems to have a few problems with the s4 , atleast this was the case with my phone.
Click to expand...
Click to collapse
This seems to have done the trick. Titanium is now gaining root access.

Related

Any Chance To Unlock The Bootloader?

hello,
i got my Samsung Galaxy S4 from EE in England .. I9505 version .. and i found out that the Bootloader is locked .. so dose any one have any idea how to unlock it ..coz i need to root the device and change things up.. thanks in advance
As been stated multiple times, write protection does not mean it is locked. That's all dependent on your carrier
If I helped you out be sure to hit thanks
Swyped from a minimalist S2
MultiLockOn said:
As been stated multiple times, write protection does not mean it is locked. That's all dependent on your carrier
If I helped you out be sure to hit thanks
Swyped from a minimalist S2
Click to expand...
Click to collapse
thanks for your reply .. well how can i make sure? is it ok if i try flashing the root from odin?
MultiLockOn said:
As been stated multiple times, write protection does not mean it is locked. That's all dependent on your carrier
If I helped you out be sure to hit thanks
Swyped from a minimalist S2
Click to expand...
Click to collapse
thank you very much for this information .. well i tried to flash the root from Odin and it WORKS .... thank god the bootloader is not locked :good::good::good:
Mine too is from EE and had the same as yours. However attempted to root it yesterday. I ticked USB debugging and then used ODIN to flash the CF-Root.tar file (thanks Chainfire) which it seemed to do ok and came up green with "Pass" and said it had succeeded and I got the red android icon before it automatically rebooted itself but when I try to get root rights with Titanium it hangs for ages "asking for root rights" and then eventually (after about 15mins) says it couldn't access root privileges.
So everything looks ok but apparently it's not. Any ideas as to why it's (a) not rooted; or (b) Titanium can't get root access?
Did you root yours following this method??
I'm stumped!!
flipflop104 said:
Mine too is from EE and had the same as yours. However attempted to root it yesterday. I ticked USB debugging and then used ODIN to flash the CF-Root.tar file (thanks Chainfire) which it seemed to do ok and came up green with "Pass" and said it had succeeded and I got the red android icon before it automatically rebooted itself but when I try to get root rights with Titanium it hangs for ages "asking for root rights" and then eventually (after about 15mins) says it couldn't access root privileges.
So everything looks ok but apparently it's not. Any ideas as to why it's (a) not rooted; or (b) Titanium can't get root access?
Did you root yours following this method??
I'm stumped!!
Click to expand...
Click to collapse
thats weird .. the root is working just fine with me and the Titanium is working as well .. i changed the font and everything is ok with me ..
Untraceable said:
thats weird .. the root is working just fine with me and the Titanium is working as well .. i changed the font and everything is ok with me ..
Click to expand...
Click to collapse
How strange :crying:

Note 3 DCNO Prod Test Help

Okay, so I have this phone and the info attached to the imei DCNO Prod Test phone. It has the following build listed N900VVREBMJ5 test-keys. I checked for root access with a app and it didn't have root access. I tried to root with odin3 root_de_la etc and it came up with an error and was basically soft bricked. Was able to reload the pit file and eventually get it working again. I clearly don't know what I'm doing and bought this phone online and have learned very little since last night. It loads up with the custom logo etc etc. I'm looking load a regular stock rom onto or just a custom one, but no matter what I do I get an error.. Can anybody help.. thanks
Use kingo root.... Google it. It works on all of the builds for n900v.
Sent from my SM-N900V using Tapatalk
shiftr182 said:
Use kingo root.... Google it. It works on all of the builds for n900v.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
as stated on the general tab, the most important thing is to check if secureboot is enabled first!!! Turn phone off, turn on holding power, home, volume down and check to see if it say secureboot enabled. If it says disabled you might be famous
2swizzle said:
as stated on the general tab, the most important thing is to check if secureboot is enabled first!!! Turn phone off, turn on holding power, home, volume down and check to see if it say secureboot enabled. If it says disabled you might be famous
Click to expand...
Click to collapse
It's enabled. Btw, it says rooted already, but it fails to remove root or reroot. I also can't load anything on it...
topurdue said:
It's enabled. Btw, it says rooted already, but it fails to remove root or reroot. I also can't load anything on it...
Click to expand...
Click to collapse
Anyways, my problem is this. It says I'm rooted. I installed SuperSU it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!" Safestrap reads, "not rooted not active". Kingo states root "yes". I don't know what to do any help whould be great
topurdue said:
Anyways, my problem is this. It says I'm rooted. I installed SuperSU it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!" Safestrap reads, "not rooted not active". Kingo states root "yes". I don't know what to do any help whould be great
Click to expand...
Click to collapse
Anyways, i wiped deleted restarted and now i have root access.. blah blah ill be back im sure.

[Q] Note 3 Manual Re-Root - no SU binary installed

I rooted my device with Kingo Android root. I am currently running android OS 4.3.
Everything was going just fine until just today when opened SuperSU and it told me that there is no SU binary installed. SuperSU cannot install it.
Pretty much I need to manually re-root my device.
I am not aware of any recovery files that I may have. To clarify, I have never backed up my device in any way. I have only had it for a month, and there is hardly anything on it. I figured, why bother? Well now I know.
I have done quite a few google searches about this, and I can not find any help.
What is my best course of action?
Thank you very much.
Try reflash and re-root with cf-auto root through Odin. A a small question: u still have root right to install some app such root explorer and titanium backup?
Sent from my SM-N9005 using XDA Premium 4 mobile app
hhai2pth said:
Try reflash and re-root with cf-auto root through Odin. A a small question: u still have root right to install some app such root explorer and titanium backup?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunatly, I no longer have root. None of my root apps can get root permissions because the SU binary is missing.
I tried flashing my firmware, but now my phone is stuck in an unusable state. The official firmware leaves me unable to boot with a "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I flash a different ROM on top of that one, all my spen stuff is messed up.
This is way different from jailbreaking. There are so many rom files I have a hard time finding the one I need.
SM-900A in case anyone wants my number.
DrShenanigan said:
Unfortunatly, I no longer have root. None of my root apps can get root permissions because the SU binary is missing.
I tried flashing my firmware, but now my phone is stuck in an unusable state. The official firmware leaves me unable to boot with a "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I flash a different ROM on top of that one, all my spen stuff is messed up.
This is way different from jailbreaking. There are so many rom files I have a hard time finding the one I need.
SM-900A in case anyone wants my number.
Click to expand...
Click to collapse
You need to go on sammobile and download your stock firmware (you probably want to stay on 4.3 unless your particular phone and carrier have root capabilities on 4.4.2 which verizon and att do not yet have) then flash it through odin... just search your model # through sammobile and it will show all the available stock firmwares. That will at least get you running again then u will have to root it again from there
Posted from my beast of a VZW Note 3!!
I downloaded the firmware from that site and have tried to flash it.
I get an Error Meassage:
SW REV CHECK FAIL : [sb1]Fused 2 > Binary 1
DrShenanigan said:
I rooted my device with Kingo Android root. I am currently running android OS 4.3.
Everything was going just fine until just today when opened SuperSU and it told me that there is no SU binary installed. SuperSU cannot install it.
Pretty much I need to manually re-root my device.
I am not aware of any recovery files that I may have. To clarify, I have never backed up my device in any way. I have only had it for a month, and there is hardly anything on it. I figured, why bother? Well now I know.
I have done quite a few google searches about this, and I can not find any help.
What is my best course of action?
Thank you very much.
Click to expand...
Click to collapse
1st : I dunno ur device which version of note 3.
2nd : kingo sometimes for some device not working well. Try avoid to use this method. Try cf-autoroot instead. Easy nd simple, but knox will trip.
3rd : have u tried update to latest supersu?
3rd :
Sent from somewhere under the sky, at the vorner of this rounded earth.
antique_sonic said:
1st : I dunno ur device which version of note 3.
2nd : kingo sometimes for some device not working well. Try avoid to use this method. Try cf-autoroot instead. Easy nd simple, but knox will trip.
3rd : have u tried update to latest supersu?
3rd :
Sent from somewhere under the sky, at the vorner of this rounded earth.
Click to expand...
Click to collapse
Updating SuperSU is what cause this mess, I believe. It's too late for that now anyhow, because my phone does not boot.
I have the SM-900A. There is no cf-autoroot for it. Not that I canfind at least.
DrShenanigan said:
Updating SuperSU is what cause this mess, I believe. It's too late for that now anyhow, because my phone does not boot.
I have the SM-900A. There is no cf-autoroot for it. Not that I canfind at least.
Click to expand...
Click to collapse
Try this, mate
http://forum.xda-developers.com/showthread.php?t=2466423

Towelroot work??

I know outside of Att note 3 it hasn't been confirmed to work but wondering if anyone tried it on other note devices? Thanks.
Sent from my iPhone using Tapatalk
Used it installed safestrap and when it reboots get the unlock symbol on the boot screen
Sent from my SM-N900V using XDA Premium 4 mobile app
Works fine on my device. For the unlock symbol, download latest SU and updated binaries. That will go away.
Sent from my SM-N900V using Tapatalk
Definitely works for getting root. Rooted, installed SuperSU, Xposed, SafeStrap all successfully. Now struggling to get a rom to work (tried Eclipse & Hyperdrive). Both say they install successfully via SafeStrap and then hangs on boot up. I've seen one other post on the Eclipse thread for the same problem, so it might be something to keep an eye on.
i can verify that this method works. i just installed superuser and it works flawlessly. the only thing is make sure to download the superuser app from here so you have the updated binaries: http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
re
i have root access verified w/root checker
downloaded v1.99r4.zip and installed it
when i open it it asks for me to update binary and it fails installation
any ideas or workarounds??
lazygregg said:
i have root access verified w/root checker
downloaded v1.99r4.zip and installed it
when i open it it asks for me to update binary and it fails installation
any ideas or workarounds??
Click to expand...
Click to collapse
Rerun towelroot
re
drewcam888 said:
Rerun towelroot
Click to expand...
Click to collapse
i've done that multiple times...
reran towelroot, it reboots phone..open supersu the version that i downloaded earlier from the website and try to download supersu binary and it fails
lazygregg said:
i've done that multiple times...
reran towelroot, it reboots phone..open supersu the version that i downloaded earlier from the website and try to download supersu binary and it fails
Click to expand...
Click to collapse
I seem to be in the same boat as well. Things I have tried and it still does not work:
Installed Play Store Edition
Installed 1.99r4
Installed 1.99r5
All of them are saying I need to update binaries. While I am technically rooted and can grant permissions to apps, I need to get into SuperSU so I can modify some settings.
There are several others have issues on Reddit as well, so its not a couple of people.
exaltedgod said:
I seem to be in the same boat as well. Things I have tried and it still does not work:
Installed Play Store Edition
Installed 1.99r4
Installed 1.99r5
All of them are saying I need to update binaries. While I am technically rooted and can grant permissions to apps, I need to get into SuperSU so I can modify some settings.
There are several others have issues on Reddit as well, so its not a couple of people.
Click to expand...
Click to collapse
Try this. Install safestrap 3.7x. Open it, give su permission, install recovery, hit the home button. Open supersu, update binary thru cwm/twrp. Don't click to reboot phone into recovery from supersu. Hold down home and bring safestrap back up. Reboot to recovery from there and it should update the binary. Hope this helps.
Sent from my SM-N900V using XDA Premium HD app
Dc4479 said:
Try this. Install safestrap 3.7x. Open it, give su permission, install recovery, hit the home button. Open supersu, update binary thru cwm/twrp. Don't click to reboot phone into recovery from supersu. Hold down home and bring safestrap back up. Reboot to recovery from there and it should update the binary. Hope this helps.
Click to expand...
Click to collapse
This is being very peculiar. After I installed Safe Strap, SuperSU went fine, able to get in and do what I needed to get done. I reboot into recovery. Made a backup, and rebooted system. Went right to SuperSU again. And the same issue occurs, constantly asking for updated binaries. I am trying everyone once more to make it all work. If not, then I will just stick with what I have and hopefully it doesn't cause any other issues.
Thank you for the help thus far. :good:
exaltedgod said:
This is being very peculiar. After I installed Safe Strap, SuperSU went fine, able to get in and do what I needed to get done. I reboot into recovery. Made a backup, and rebooted system. Went right to SuperSU again. And the same issue occurs, constantly asking for updated binaries. I am trying everyone once more to make it all work. If not, then I will just stick with what I have and hopefully it doesn't cause any other issues.
Thank you for the help thus far. :good:
Click to expand...
Click to collapse
Yeah I just did all this last night...I installed SafeStrap and installed Recovery, then went into SuperSU and clicked Normal when asking for updating Binaries and it hasnt asked again thankfully. All of this of course was after installing BusyBox from the Play Store.
Note though: Safestrap isnt working for flashing roms just yet, just like someone else said here, and someone else said this in the Jasmine Rom forum. I just tried it myself and everything looks fine when installing, but then when you boot up, screen goes black and unresponsive after the SS splash screen on a reboot. Hopefully we have an update to SS soon. Fair warning - make sure you create a backup of your System/Data, etc in SS before messing around...it makes it so much easier to restore in case something screws up.
pmt223 said:
Yeah I just did all this last night...I installed SafeStrap and installed Recovery, then went into SuperSU and clicked Normal when asking for updating Binaries and it hasnt asked again thankfully. All of this of course was after installing BusyBox from the Play Store.
Note though: Safestrap isnt working for flashing roms just yet, just like someone else said here, and someone else said this in the Jasmine Rom forum. I just tried it myself and everything looks fine when installing, but then when you boot up, screen goes black and unresponsive after the SS splash screen on a reboot. Hopefully we have an update to SS soon. Fair warning - make sure you create a backup of your System/Data, etc in SS before messing around...it makes it so much easier to restore in case something screws up.
Click to expand...
Click to collapse
So, can someone enlighten me on what this "root" does? I've been running SafeStrap 3.72 with HyperROM 8 and just yesterday, successfully installed Towelroot on my Verizon Note 3. I downloaded the new SU to my SDcard before running Towelroot and was able to run it immediately after root and all looks good. But... what did I actually gain? Can I now install Cyanogen or others? I am a bit fuzzy on the difference, if any, on a rooted phone vs. an unlocked bootloader. Those of us on the Verizon retail Note 3 still don't have unlocked bootloaders do we? I miss the ease of playing with my old S3! LOL. Thanks!
emtownsend said:
So, can someone enlighten me on what this "root" does? I've been running SafeStrap 3.72 with HyperROM 8 and just yesterday, successfully installed Towelroot on my Verizon Note 3. I downloaded the new SU to my SDcard before running Towelroot and was able to run it immediately after root and all looks good. But... what did I actually gain? Can I now install Cyanogen or others? I am a bit fuzzy on the difference, if any, on a rooted phone vs. an unlocked bootloader. Those of us on the Verizon retail Note 3 still don't have unlocked bootloaders do we? I miss the ease of playing with my old S3! LOL. Thanks!
Click to expand...
Click to collapse
No, you dont gain an unlocked bootlader. At this point, only the Almighty will make that happen lol. For us with Verizon Notes (and some others), this helps the folks who either a) dont want to use Kingo or the other web methods, and b) folks who were on stock 4.4.2 NC4, like from an OTA (like me). This now gave me root, where when the OTA came out people were fearing there would never be a root for it (thanks to everyone else who put monies towards a bounty). Many people as well as myself cannot use SafeStrap successfully to fully flash a rom yet (you'll see this remarked in a lot of places), so Im sure there is an update forthcoming. In the meantime, I can use TB and freeze/uninstall a lot of the bloatware crap, and use Xposed for whatever else, which is fine by me. But no, we are still a no-go on full rooting and unlocked bootladers like on some other phones, which means no CyanogenMod, etc.
pmt223 said:
No, you dont gain an unlocked bootlader. At this point, only the Almighty will make that happen lol. For us with Verizon Notes (and some others), this helps the folks who either a) dont want to use Kingo or the other web methods, and b) folks who were on stock 4.4.2 NC4, like from an OTA (like me). This now gave me root, where when the OTA came out people were fearing there would never be a root for it (thanks to everyone else who put monies towards a bounty). Many people as well as myself cannot use SafeStrap successfully to fully flash a rom yet (you'll see this remarked in a lot of places), so Im sure there is an update forthcoming. In the meantime, I can use TB and freeze/uninstall a lot of the bloatware crap, and use Xposed for whatever else, which is fine by me. But no, we are still a no-go on full rooting and unlocked bootladers like on some other phones, which means no CyanogenMod, etc.
Click to expand...
Click to collapse
Ah. Got it. Thanks!
* I successfully used SafeStrap to install HyperROM 8 on slot 1 only, so I had to lose my stock ROM, but I'm OK with that.
cnotes2019 said:
I know outside of Att note 3 it hasn't been confirmed to work but wondering if anyone tried it on other note devices? Thanks.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
i rooted today with towelroot. i have a verizon note 3 on 4.4.2

[Q] NC-4 can't get it rooted?....Help please

Ok I did take that darn update and so am on: NC-4
I used the " towelroot " when it was first introduced.
I have the " Unlocked padlock " with the word "custom" under it when I reboot.
I have used " Root checker basic " by Joeykrim. " this device does not have proper root access".
I have been reading loads of thread's but can't find anyone else who is having the same issue.
I then tried towelroot 2 and 3 when they came out, but I still can't get my phone rooted.
I don't know what to try now.
Did You update the su binaries? As per op
Sent from my SM-N900V using XDA Premium 4 mobile app
Have you just tried a different root checker?
I did and have
Sorry for my slow response, RL got crazy for a few days there.
I did update the SU, via the link to chain fire
I have tried multiple root checkers.
I am about to go through the steps again.
j_axxy said:
Sorry for my slow response, RL got crazy for a few days there.
I did update the SU, via the link to chain fire
I have tried multiple root checkers.
I am about to go through the steps again.
Click to expand...
Click to collapse
If it doesn't work again try reflashing the NC4 stock tar via odin and trying the towelroot process again. The SU binaries not being up to date should have no effect on whether you are actually rooted or not.
FIXED
kinstre11 said:
Try reflashing the NC4 stock tar via odin and trying the towelroot process again.
Click to expand...
Click to collapse
That got it done, thank you kindly kinstre11.
My pleasure.

Categories

Resources