yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Srambo217:
So my screen kept waking up no matter what I did (even after an Odin back to 4.1), I got a refurb today and rooted it with Safestrap because it came with 4.3 installed. I'm debating wheter or not I should just keep my borked device and continue to live lawlessly flashing ROMs and such, or wait it out with this locked bootloader. If I choose the former will I be able to remove safestrap root from this refurb prior to sending it back?
[Verizon Samsung Galaxy S 4] k1mu:
Yes, as long as you don't remove or modify any of the stock ROM content - which includes debloating, you can take an OTA even if rooted.

I just gave up deferring the MJ7 to MK2 update tonight while rooted. I lost root, but got it back in a few minutes, so no issue.

As has been said, the KitKat update has a newer kernel with no known exploits, so rooting will be a waiting game.

Flashing mods isn't impossible. You can use Safestrap recovery to install mods, but there's no guarantee anything will work right, and flashing into stock is not supported. You can also take apart a flashable mod and figure out what it installs and do that using other means (push to sdcard, install by hand, for example), but that's also risky and a lot of work. That's what Safestrap is for: it removes the risk since you can always choose to boot stock.
[Verizon Samsung Galaxy S 4] k1mu:
Unrooting info is available in the second post in this thread. Also, you can always flash a stock full-wipe ROM prior to returning.
[Verizon Samsung Galaxy S 4] negativzeroe:
Intrigued... Do you have a link with more info on that?
[Verizon Samsung Galaxy S 4] lalec:
No link. Just read the second post on page one of this thread and see if that is what you needed.
[Verizon Samsung Galaxy S 4] negativzeroe:
Would that work if I was to flash philz and roms and such?

Edit: what I mean is to bring it into sprint for service and I want it to be stock.
[Verizon Samsung Galaxy S 4] JerryGNYC:
You'll need to register (there is a free version) -

http://www.sammobile.com/firmwares/3/?download=23532

Install is via Odin, though I don't (yet) know what happens if you have a custom recovery.
[Verizon Samsung Galaxy S 4] dimm0k:
just wanted to confirm... removing bloatware from Samsung would prevent OTA, but what about the crapware that the carrier loads?
[Verizon Samsung Galaxy S 4] aviwdoowks:
[MENTION=3940199]k1mu[/MENTION]

What do you think about the chances of it working on the droid ultra? I do not have one yet. On 4.4 I mean.

http://xdaforums.com/showpost.php?p=50374439&postcount=14
[Verizon Samsung Galaxy S 4] NiMaD83:
ok so i am almost done with this i think and i am on this screen via SuperSU

Knox detected. This might limit blah blah. Disable knox?

yes or no?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Yes

---------- Post added at 02:02 PM ---------- Previous post was at 01:59 PM ----------

NOT REGARDING THE ABOVE QUESTION, but I just saw this sentence

LULZ
[Verizon Samsung Galaxy S 4] NiMaD83:
Holy SHET i rebooted after all of this and now all services are stopping, touch control having issues, things not opening. WTF

---------- Post added at 01:20 PM ---------- Previous post was at 01:15 PM ----------

wtf did this do to my phone?

how can i undo this?????
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
You need to kill and freeze all Knox programs and that should stop
[Verizon Samsung Galaxy S 4] NiMaD83:
with what? and what are all of them? I get "unfortunately XXXXX has stopped." with most things and evne Process system isn't responding

and "Android is upgrading..." on reboot

using LInk2SD i froze everything named Knox and am rebooting

still getting "Android is upgrading..." on reboot

play store opening and running better though

---------- Post added at 01:41 PM ---------- Previous post was at 01:28 PM ----------

so with still getting "Android is upgrading..." on reboot

some apps still "stop" when trying to open them as well as a delay between touch and starting to open

EDIT ... nope most if not all apps still freezing and stopping

with all the root methods ive seen for this phone why wasnt Odin used?

Anybody here?

---------- Post added at 02:21 PM ---------- Previous post was at 01:41 PM ----------

"unrooted" via post 2 and its still showing Android is upgrading on reboot. WHAT THE HELL
[Verizon Samsung Galaxy S 4] katodragon:
I used post 2 and my phone upgraded successfully.
[Verizon Samsung Galaxy S 4] gothicasshole:
It is uppon us ahhhhhhhh dint update no root !!!!!!! http://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB419415&cv=820#fbid=8GuwNEak5-d
[Verizon Samsung Galaxy S 4] k1mu:
After all what? I would be quite surprised if you suddenly have things force closing due just to being rooted.

What else did you do after rooting?

What kind of phone are you using, what version of Android, what build?
[Verizon Samsung Galaxy S 4] k1mu:
The carrier is responsible for what appears on the phone, so removing their stuff will also possibly break an OTA.

For example, "NFL Mobile" that Verizon keeps trying to update on my phone... they've already got a copy in /system eating storage, I don't need an update that will consume even more space. But deleting it (or freezing it) will probably break any OTAs.

It's best to assume that removing anything from the stock ROM may break OTAs. Same with freezing things, but that's less risky since you can always defrost as long as you're still rooted.
[Verizon Samsung Galaxy S 4] k1mu:
"Android is upgrading" is telling you that it's rebuilding the Dalvik cache. I've seen that with the Google Wallet 2.0 hack, specifically caused by flashing deodexed APKs onto an odexed ROM. Something has corrupted one of your files.

As far as the Wallet fix, that doesn't work for me on the stock Verizon MK2 ROM, and permanently breaks WiFi, requiring me to restore a no-wipe using Odin. It's not recommended.

Odin wasn't used to root because it's not possible.

And sorry, but real life intruded today.

.

At this point, your quickest recovery is to re-flash using Odin. I can't point you anywhere given that I have no idea what you're running.
[Verizon Samsung Galaxy S 4] tuffluck:
Okay. So just to be clear, kitkat is available OTA if you defrost all apps related to the OTA. And at the moment, no one can root after the OTA. Do I understand that right, and if so, what are we waiting on to get the OTA? A safestrap version or a saferoot version compatible?

Sorry to be a layman, there really is a lot of info on here that is difficult to sort through properly.
[Verizon Samsung Galaxy S 4] gothicasshole:
As of yet there is no root method to gain root access on kit kat so as far as getting an ota avoid it if you want root THERE IS NO KNOX ROOT METHOD FOR THE GALAXY S4 FOR KIT KAT MOST LIKELY SAFESTRAP WILL NOT WORK UNTIL IT IS UPDATED FOR KIT KAT YOU RUN THE WRISK OF LOSING ROOT AND IF YOU ARE IN A SAFE STRAP ROM A VOID THE OTA AT ALL COST IF YOU DONT KNOW WHAT YOUR DOING YOU WILL BRICK IT YOU HAVE BEEN WARNED
[Verizon Samsung Galaxy S 4] k1mu:
Yes, you can defrost or flash a no-wipe factory ROM. Either will then allow you to update to KitKat.

If you fail to restore/defrost everything, the OTA will fail (i.e. leaving your original ROM intact), so it's fairly safe from that standpoint.

As far as rooting goes, if your phone has a locked bootloader, there's currently no way to root it. If you're one of the lucky ones with, say, a T-Mobile phone, it may come with an unlocked bootloader that will allow you to root.

It's also remotely possible that Safestrap's recovery may survive the OTA. If so, then you could flash a root zip into the stock ROM using Safestrap. While I think that's pretty unlikely, keeping SS installed (no slot, just the recovery) may allow you to re-root.

On the other hand (see, this is complicated), Samsung and AT&T have figured out in their post-MK2 releases how to use Knox to limit root even further, along with making it very difficult to stop Knox from running. With KitKat, Verizon may succeed in making having root be useless. That's their goal, as it helps them in the enterprise market.
[Verizon Samsung Galaxy S 4] sawyerbenjamin:
It hangs at "[*] Waiting for phone to appear"

I have my drivers and USB debugging enabled, although I never get the prompt to allow access from my laptop, which is Win8 btw.

Suggestions?

Sprint S3 - 4.3
[Verizon Samsung Galaxy S 4] k1mu:
Does the device show up in device manager once plugged in? If it's showing up and the drivers are right, you should get the permission prompt. But that will only happen once (if you tap the checkbox to enable it.)

I'd guess a bad cable, or perhaps trying a different USB port.
[Verizon Samsung Galaxy S 4] sawyerbenjamin:
It shows up correctly when in the 3.0 port. Program still hangs and still no prompt.

Is this right?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Have you tried reseting the approved machines for ADB? (On the phone: Developer options>revoke usb permissions)
[Verizon Samsung Galaxy S 4] sawyerbenjamin:
Yep. Doesnt do anything except tell me to confirm.
[Verizon Samsung Galaxy S 4] tailgunner9:
After Root Can I Get Updates

After using this root, can I still get the update of Kit Kat OTA? Or do I have to go back to completely Stock?? I still have Stock recovery, No CWM. Need to know since Kit Kat Update came out today. Thanks.:confused:
[Verizon Samsung Galaxy S 4] k1mu:
You will need a stock device to guarantee OTAs will work. Unrooting is not strictly necessary, but doing that will ensure the the phone doesn't decide to reject the OTA due to being "Custom".

Of course, you should understand that prospects of rooting 4.4 are quite bleak at the moment.
[Verizon Samsung Galaxy S 4] decaturbob:
I can't wait when all those that leap to kit kat ota realize they are most likely lock into stock...With little chance of root....

These threads will be filled with what can we do...
[Verizon Samsung Galaxy S 4] tailgunner9:
Root Kit Kat

No I did not know that!!! May hold off then. Thanks
[Verizon Samsung Galaxy S 4] SCWells72:
My MK2 has been successfully rooted for a few months now using this technique. The 4.4 update just started downloading to my phone. I'd prefer to stay with rooted 4.3 until there's a solid root method for 4.4. Is there a safe way for me to shut down update down and prevent it from installing in the future?

UPDATE: I'm trying the following to prevent the OTA:

http://xdaforums.com/showthread.php?t=2506101
[Verizon Samsung Galaxy S 4] esheesle:
Ok, so I'm confused. Just got a galaxy s4 (on mk2). Got usb debugging enabled with no problems. Plugged in and Kies3 can see the phone just fine. I run the script and get the prompt to plug in my phone and press enter. I press enter and it goes nowhere, even after some time. Tried also not having the phone already plugged in and same result. Device appears to be connected as a media device just fine. thoughts?
[Verizon Samsung Galaxy S 4] tailgunner9:
Root Kit Kat

I think I will stay with 4.3 also after reading we may never be able to Root it to get rid of AT&T apps that most people do not even use. Think I have read after maybe 4 times telling it not to download update it will just Auto do it and install. Thanks...
[Verizon Samsung Galaxy S 4] k1mu:
To confirm resetting, then you don't get another prompt when plugging in?

There's only a few possible causes left. I think I asked if the OS shows anything when you plug in - does it? By that, I mean anything, including a disk drive. Open device manager (Windows/Break, then click "Device Manager" if necessary.) Do you see anything coming and going when you plug in and unplug?

If you're using Linux, dmesg should generate info about the phone after you plug in.

If you're seeing nothing, then you've got a cable problem or a problem with the USB port on your phone.

If you're seeing a device - specifically the storage on the phone - but no permission prompt when you plug in, it's either a driver problem or you don't have USB Debugging enabled.

What does the "adb devices" command give for output when the phone is plugged in? Probably just "List of devices attached" and nothing else, but it's worth asking.
[Verizon Samsung Galaxy S 4] k1mu:
If it's connecting as a media device, then you most likely do not have USB debugging enabled. Or, you missed the prompt to authorize your computer for debugging.

Start/Settings/More/Developer options. Make sure "USB debugging" is checked.

If it is, unplug your phone, tap on "Revoke USB debugging authorization" then OK.

Now, plug your phone back in. On the "Allow USB debugging?" tap on "Always allow from this computer" then tap "OK".
[Verizon Samsung Galaxy S 4] gothicasshole:
Did you make sure the rsa key was set for your computer to use adb? If not it will do that go to settings developer options and press revolk usb debugging authorization it will reset it re plug it into your computer and make sure your not in camera mode while Your connected and bam should ask for permission with a new rsa key and you can then run the root ;)
[Verizon Samsung Galaxy S 4] metalfr33ak:
Does anybody know if this will work on galaxy s4 with the latest update to 4.3 NA4?
[Verizon Samsung Galaxy S 4] cnewsgrp:
NeverMind ...
[Verizon Samsung Galaxy S 4] sawyerbenjamin:
Basically heres what happens:

I revoke all Computer access, then confirm that that is what I want to do.

Then I plug my S3 into my laptop, and I'll get a notification on my phone either saying "Plugged in as Media Device" or Plugged in as camera"

My computer will also open it up automatically (Thats the default action I chose) where I can either go into the phone storage or the SD card.

Thats it. No prompt on my phone for ADB access, and the Saferoot hangs every time.

I'm gonna give this a go on my brother's Win7 laptop.

Thanks for trying to help btw, I appreciate it.
[Verizon Samsung Galaxy S 4] esheesle:
USB debugging was definitely enabled, even got the prompt to authorize access (and said accept from this computer always). Cleared all authorized computers and tried again, prompted but still never got past the same prompt.

I decided to do a test of my own and did and adb reboot on the command line and phone rebooted, so obviously working. I commented out your findstr chunk of code and all worked great. Phone rooted/rebooted/etc.. Thanks.
[Verizon Samsung Galaxy S 4] k1mu:
OK, thanks. I would like to understand what's happening here. What does "adb get-state" output when you phone is plugged in?

That convoluted "findstr" is capturing the output of that command. If it says "device", then you won't get the message

Then it does an "adb wait-for-device" which shouldn't be hanging for you.

Is it possible to send me a copy of the install.bat that worked for you so I can diagnose the problem? Thanks.
[Verizon Samsung Galaxy S 4] esheesle:
I'll check it tonight and let you know.
[Verizon Samsung Galaxy S 4] thornev:
They found a root process for kit Kat on the Tab Pro. Maybe just time before it can be done on S4?
[Verizon Samsung Galaxy S 4] k1mu:
The Tab Pro doesn't have a locked bootloader, so it can be rooted with CF-AutoRoot.

It's pretty common for Samsung WiFi-only tablets to have unlocked bootloaders.

Devices with unlocked bootloaders are easily rooted, but you're not going to get one of those from very many carriers. Definitely not from Verizon or AT&T.
[Verizon Samsung Galaxy S 4] thornev:
And so far the development activity for Tab Pro is nill.
[Verizon Samsung Galaxy S 4] negativzeroe:
So I just got the notification for an ota on my spark s4 and used this method to root. After I unroot and take the ota, you guys think this root will work on it?

Edit. Found on update thread. No.
[Verizon Samsung Galaxy S 4] martikp:
Will Saferoot work on android 4.4.2 i9505 XXUFNB8 ?
[Verizon Samsung Galaxy S 4] decaturbob:
Only for 4.3...
[Verizon Samsung Galaxy S 4] k1mu:
It's not very likely. Any build after MKx probably has the kernel defect patched.

You can always give it a try, but it's not likely to work.
[Verizon Samsung Galaxy S 4] gastric123:
I had some initial troubles keeping my phone connected, but ultimately I was successful in rooting my Sprint Samsung Galaxy S3 SPH-L710 running the OTA Android 4.3

And... finally.... I no longer have to listen to the @#$% shutter, focus, and video start/stop sounds.

The only minor point of confusion was when SuperSU asked if I wanted to disable KNOX, that wasn't specifically covered in the OP.

Honestly, the hardest part of the whole process was Step 1) Finding this thread. There's a ton of rooting articles, but it took me a long time to find one to deal specifically with the OTA 4.3 update.

Thank you kindly. :)
[Verizon Samsung Galaxy S 4] gastric123:
Would someone be so kind to provide me with some concise links and/or directions to setup nandroid or onandroid backups using this specific root? I've spent over an hour reading backup remarks in this thread and have seen reference to nandroid via safestrap but no specific links to the appropriate / specific source to obtain it. I also haven't seen definitive remarks on whether it can do restores as well as backups. Looking for a way to do a snapshot-in-time backup of my entire device.

Many thanks.
[Verizon Samsung Galaxy S 4] LBCaptivate:
Are there any problems running this on AT&T S3 4.3 with the Isis sim card? I do not use Isis any more but have not uninstalled it from my phone.
[Verizon Samsung Galaxy S 4] mag1017:
Work with mf3 perfect

:good::good::good::fingers-crossed:Hi, work with mf3, probed:good::good::good::fingers-crossed: THANKS
[Verizon Samsung Galaxy S 4] k1mu:
Thanks - I've added a comment about the Knox disabling to the OP. That doesn't always happen, so I can't tell people to watch for it.

Also added a comment about using "Normal" mode to update the "su" binary if SuperSU asks.
[Verizon Samsung Galaxy S 4] k1mu:
No problems. The SIM card type doesn't have anything to do with what saferoot does.
[Verizon Samsung Galaxy S 4] k1mu:
That's far too dependent on what device you have and what bootloader is installed.

First you need to root. OK, you've done that. Then you need to install a custom recovery. The custom recovery is what does the backups, and is something you do after rooting.

If you're on a Verizon i545, and if you're on the MDK bootloader, install whatever recovery you want. (I can't help there - I've never had my hands on a MDK phone.) Otherwise, install Safestrap. The recovery in Safestrap allows you to make nandroid backups.

There's nothing that saferoot does that allows you to make nandroid backups. It does enable Titanium backup to perform full app backups, though.

Does that help?
[Verizon Samsung Galaxy S 4] dafonehacker:
So if I understand correctly this won't trip knox, neither when it fails? I have a Galaxy s4 i9505 running this software:

AP: UEMKF

CSC: EMK3

Will this work?

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Verizon Samsung Galaxy S 4] gastric123:
Just to clarify I have: Sprint Galaxy S3 (SPH-L710), MK3

Ahhh, I'm such a noob. I just realized I've ventured into the Verizon threads while seeking Sprint S3 tools. Like I said, I spent a lot of time just finding my way here to locate your excellent root tool, which worked great.

For anyone else looking, here's the Safestrap thread: http://xdaforums.com/showthread.php?t=2605648

Has big red text "CONFIRM THAT YOU ARE USING A VERIZON WIRELESS SAMSUNG GALAXY S3 (d2vzw)" Hence my Sprint-user confusion. :silly:

And the main site which only references S4's not S3's at all: http://blog.hash-of-codes.com/downloads/safestrap/
[Verizon Samsung Galaxy S 4] k1mu:
From the original post:

So no, this will not "trip knox". :)

And for the i9505, MH6, MH8, MJ5, MKE, MKF are reported to work. That information is also available in the original post.
[Verizon Samsung Galaxy S 4] dafonehacker:
Thanks a lot I used it and I still have Knox 0x0! Awsome!

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Verizon Samsung Galaxy S 4] iarapilot:
I bought an I9192 yesterday with MK4. I rooted with saferoot....the updated one on P4 post # 36. I followed the instructions and at the end it said that Knox was disabled. In download mode the counter was still at 0x0. I then flashed TWRP from this forum and my Knox counter is still at 0x0 and the phone works fine....FYI.
[Verizon Samsung Galaxy S 4] dafonehacker:
Is it possible to flash custom recovery without tripping knox? And without safstrap because it isn't available for i9505.

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Verizon Samsung Galaxy S 4] k1mu:
Just to be clear: using the term "Knox" is ambiguous. There is no "Knox flag", there's a "Knox Warranty Void" flag. I always use the full phrase "Knox Warranty Void" to avoid confusion. The "Knox Warranty Void" flag will be set if you try to flash an unauthorized bootloader. Since Saferoot doesn't flash anything, it can't set that flag. That flag is managed by the bootloader, and only the bootloader burns that fuse. Software running on your phone after boot won't touch it. Saferoot only operates post boot, so it can't cause the flag to be set.

There's also the Knox components on the phone itself which enforce security policies. If you leave that running, some attempts to use root permission will be killed. SuperSU and Saferoot both attempt to disable that process so it won't interfere with you. However, that has nothing to do with the Knox Warranty Void flag.
[Verizon Samsung Galaxy S 4] iarapilot:
I must correct my previous statement......looking again, in download mode I have Knox Kernel Lock 0x0, but I do have Knox Warranty Void 0x1. My mistake, and sorry for the bad info!
[Verizon Samsung Galaxy S 4] k1mu:
That was probably set when you flashed TWRP. :(
[Verizon Samsung Galaxy S 4] decaturbob:
more or less I totally lost my wifi testing out various safestrap roms sunday (either purified or echo took it on my phone) so I had to odin the MJ7 wipe tar and reroot using saferoot and resetup everything this morning

low and behold, Selinux was set to permissive after I rebooted a couple times in the stock slot after freezing a bunch on knox stuff via tubu. Just letting you know.

not that it makes much difference overall.
[Verizon Samsung Galaxy S 4] k1mu:
No, you can't flash a custom recovery. The locked bootloader will reject the flash. If you're lucky, the attempt won't trigger the "Knox Warranty Void" flag, but either way, it won't work.

Safestrap may get you recovery for your phone even if there's no Safestrap-compatible ROMs for the i9505. I don't know what you're planning to do, but if you want recovery so you can back up, Safestrap may work. If you want custom recovery so you can flash custom ROMs, that's not possible with a locked bootloader.
[Verizon Samsung Galaxy S 4] k1mu:
The Kernel for the MJ7/MK2 ROMs mostly ignores that flag. It's pretty easy to set it to permissive, but that doesn't change most of the enforcement that SELinux performs. That's pretty frustrating to me.

I actually spent the time to individually disable each of the SELinux hooks by pointing them back to the non-SELinux functions. That kills SELinux, but then userland stuff starts to break when they start probing for SELInux context values. Nice try, but no dice.
[Verizon Samsung Galaxy S 4] decaturbob:
All I can say is your routine ran flawless.
[Verizon Samsung Galaxy S 4] iarapilot:
Yes it did, and I am a knucklehead for miss-reading the Knox warranty counter.
[Verizon Samsung Galaxy S 4] texz71:
Searched but not finding my exact answer. How do I check the knox flag on Verizon Samsung Galaxy S4 i545 MK2 after using this root process (which seemed to work ok). I went into download mode and I get the Warning screen asking if I want to continue to load custom OS (volume up: continue; Volume down: cancel). I didn't want to continue since I was not sure at this point.

Thanks in advance.