Database Users

[Q] Am I Rooted or Not??

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.

[Q] Motochopper / Reboot Message

I am using motochopper to root but when I do, instead of the expected "Allow App to do whatever" to your phone message I am receiving the "Detection Information: To protect your device, it is recommended you reboot. <Reboot Now> < Reboot later>" message.
The solution for this appears to either Freeze or remove the System/Apps/ KNOXAgent.apk, KNOXAgent.odex, KNOXStore.apk, KNOXStore.odex files along with data/data/com.sec.knox.seandroid.
1) I don't seem to have a com.sec.knox.seandroid file.
2) all of the Knox files are read only to me.
I have followed what I am seeing to be the proper steps before hand. droidviews.com/2013/how-to-root-verizon-galaxy-s4-sch-i545-and-install-cwm-recovery-on-it/
Any help would be appreciated. Feel free to call me names if this in a dozen other threads (though I have looked!), just please provide a link

Use chainfire's autoroot http://forum.xda-developers.com/showthread.php?t=2291827 works perfectly.
I believe motochopper was disabled by the latest OTA.

gharlane00 said:
Use chainfire's autoroot http://forum.xda-developers.com/showthread.php?t=2291827 works perfectly.
I believe motochopper was disabled by the latest OTA.
Click to expand...
Click to collapse
I have a Verizon S4 so I believe this thread states not to use CF Auto. Am I wrong?

kewlguy53403 said:
I have a Verizon S4 so I believe this thread states not to use CF Auto. Am I wrong?
Click to expand...
Click to collapse
Not sure. You posted in the Sprint forum so I gave you Sprint advice.

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] MF3 to 4.4.2 with root

Greetings,
My wife's S4 is on 4.2.2 (MF3) and it drives me nuts. I've been looking around the forums, but haven't found anything conclusive as to if there is a way to go from 4.2.2 to 4.4.2 and keep or reroot.
Normally I'd throw caution to the wind, close my eyes, and hit start... but, being that this is the wife's phone and that she is perfectly content with 4.2.2, the last thing I want to do is screw up her phone.
So I guess the question is: Does anyone know of a guide they can point me to that upgrades a rooted 4.2.2 to 4.4.2?
Thank you!
PS
I found this guide (http://forum.xda-developers.com/showthread.php?t=2728462), but it just seems strange that the thread was all but ignored, so there is no feedback from users/testers.

You can upgrade to 4.4.2, but you don't keep root. You'll have to re-root it. And you have to use Odin which means you'll wipe the phone. If it was my wife's phone I wouldn't want to put up with the complaining of having to setup everything again.
Sent from my Nexus 5 using XDA Free mobile app

tarikakleh said:
Greetings,
My wife's S4 is on 4.2.2 (MF3) and it drives me nuts. I've been looking around the forums, but haven't found anything conclusive as to if there is a way to go from 4.2.2 to 4.4.2 and keep or reroot.
Normally I'd throw caution to the wind, close my eyes, and hit start... but, being that this is the wife's phone and that she is perfectly content with 4.2.2, the last thing I want to do is screw up her phone.
So I guess the question is: Does anyone know of a guide they can point me to that upgrades a rooted 4.2.2 to 4.4.2?
Thank you!
PS
I found this guide (http://forum.xda-developers.com/showthread.php?t=2728462), but it just seems strange that the thread was all but ignored, so there is no feedback from users/testers.
Click to expand...
Click to collapse
You can first unroot then go to settings---->more----->about device----> software update and take the OTA to MK2. Once on MK2 take the OTA to NB1, then to NC1, then re-root using towelroot: http://forum.xda-developers.com/showthread.php?t=2783157
The above process will leave your current set-up intact and rooted.

muniz_ri said:
You can first unroot then go to settings---->more----->about device----> software update and take the OTA to MK2. Once on MK2 take the OTA to NB1, then to NC1, then re-root using towelroot: http://forum.xda-developers.com/showthread.php?t=2783157
The above process will leave your current set-up intact and rooted.
Click to expand...
Click to collapse
Would this method be the best way to unroot, starting with step 2 in my case since I still have root...or is there a different route I can take?
Originally Posted by ou812bkewl
So, here is what I did and what you must do:
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.
When you reboot, wait a full minute and check on device status. It should still say "Official" and you will be fully un-rooted.
Why does it stay "Official" with Busybox present ONLY when SuperSU's most recently updated apk and binary are present? I have no clue... But I hope this helps you out.
Click to expand...
Click to collapse

[Q] Annoying software update postponed icon

I hit check for software update today and it downloaded the new Lollipop rom i don't want. The only option i had was hide. now i have an annoying icon in status bar and notification area and i don't know how to get rid of it.... and how can i delete the update (where was it downloaded)
On other subject if i decide to update to this just to see how it is (and losing root and exposed) how is the best way to downgrade? Currently i'm on G900FXXU1ANG2 android 4.4.2 rooted but knox is still 0x0
from what i have read it should be pretty simple
1) download stock rom and odin
2) flash rom ticking f reset and auto reboot
3) restart in samsung recovery
4)wipe data
5) ...
but what is this about the new bootloader (about being locked)? i'm kinda confused... some people say it works some say it doesn't...

gigeaky said:
I hit check for software update today and it downloaded the new Lollipop rom i don't want. The only option i had was hide. now i have an annoying icon in status bar and notification area and i don't know how to get rid of it.... and how can i delete the update (where was it downloaded)
On other subject if i decide to update to this just to see how it is (and losing root and exposed) how is the best way to downgrade? Currently i'm on G900FXXU1ANG2 android 4.4.2 rooted but knox is still 0x0
from what i have read it should be pretty simple
1) download stock rom and odin
2) flash rom ticking f reset and auto reboot
3) restart in samsung recovery
4)wipe data
5) ...
but what is this about the new bootloader (about being locked)? i'm kinda confused... some people say it works some say it doesn't...
Click to expand...
Click to collapse
Hi gigeaky:
You can follow the next guides for root and downgrade. Downgrade, root
Hope it helps.

I have read those two and I thought there is something else...
I'll put a screen shot of my other problem

gigeaky said:
I have read those two and I thought there is something else...
I'll put a screen shot of my other problem
Click to expand...
Click to collapse
in /root/cache/fota there should be "update.zip".
if you delete that (would recommend backing it up just in case) and then tell it to update, it will fail and the notification will go away.
its not permanent, i do this every few weeks or so (however long until it checks again), but its easy enough and gets rid of that annoying icon/notification

gogo0 said:
in /root/cache/fota there should be "update.zip".
if you delete that (would recommend backing it up just in case) and then tell it to update, it will fail and the notification will go away.
its not permanent, i do this every few weeks or so (however long until it checks again), but its easy enough and gets rid of that annoying icon/notification
Click to expand...
Click to collapse
Can't you just uncheck "auto-update" so you don't get future notifications?

EsuS. said:
Can't you just uncheck "auto-update" so you don't get future notifications?
Click to expand...
Click to collapse
doesnt work for me for some reason, it always ends up checking and popping up that notification from time to time anyway.

The folder is empty...
It was in data/fota

gigeaky said:
It was in data/fota
Click to expand...
Click to collapse
Thank you very much all! I was searching this thread for an hour.
I access it with Total Commander, now everything great!

Hello I did very same thing (downloaded Marshmallow update but did not install) I currently have Lollipop. My phone is not rooted, is there a way to delete this reminder without rooting the phone? I'm really not tech savvy at all and would rather not try rooting.