yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Skilover:
I used Saferoot, and had my phone working well, SU installed perfectly, except that the only recovery app was the Samsung one. It is worthless, as it won't scroll the card. So, I found an app that would download and install TWRP. Unfortunately, when I went to reboot, I got this error that I had unauthorized System software, and it locked the phone.

So, I used Heimdall, and reflashed MJ9, and my phone is stock, but working. If I use Saferoot, I can get it rooted again. Also, during the install of SU, it asked if I wanted it to try to override Knox, and I said OK. Perhaps that was an error, the instructions on OP don't mention this choice.

Further reading leads me to understand that I need to install a second Safe App, i.e. SafeStrap, in order to install TWRP, and to then install a custom rom. I didn't realize I needed the second step, not just Saferoot.

When did all this begin? I have been using N3bula, and haven't seen any posts about people not being able to flash their phones.

UPDATE: When I rooted the phone the second time, I realized I hadn't quite finished the first time--It installed SuperSU, but didn't install busy box, and didn't disable Knox. However, it seems that my issue was not realizing the phone software won't allow me to install TWRP or CWM as I'm used to. I take it, for now, we are to use Safestrap as a work-around.
[Verizon Samsung Galaxy S 4] decaturbob:
If you don't have a mdk base phone you can not use twrp or CWM. ..

sent by safestrap enabled bajarom
[Verizon Samsung Galaxy S 4] PetrichorXFi:
MD5 Hash for "saferoot.zip"

The MD5 Hash for "saferoot.zip" downloaded via the OP first posting is: 70D371EF52E165F83E6C6D5B09C32489

*Note: this was found by downloading the file multiple times, creating MD5 hash of downloaded files and verifying they all match.

Can the OP please add the hash to the first posting? [MENTION=3940199]k1mu[/MENTION]

thanks...
[Verizon Samsung Galaxy S 4] k1mu:
I concur with the md5sum:

70d371ef52e165f83e6c6d5b09c32489 saferoot.zip

However, it's a small (3 Mb) file. Unlike a 2Gb or greater ROM image, it's not very likely to be corrupted during download.

Also, it's a ZIP file. Any corrupted download will be detected by the ZIP CRC check when unpacking. Checking the md5sum is kind of redundant for such a small file.
[Verizon Samsung Galaxy S 4] k1mu:
You're conflating a number of issues.

First, rooting. Saferoot gets you root access. Root, and that's it. If you want custom recovery, you will need to read a forum specific to your phone to understand if that's possible. The Verizon Samsung Galaxy S4, which is where this is posted, does not allow custom recovery unless you have the original MDK bootloader. On other phones, especially if they're not VZ or AT&T, the bootloader may not be locked, and may allow custom recovery. For the VZ i545, the bootloader is locked and all we have is Safestrap recovery.

This thread isn't about installing custom recovery, and it can't be, because that's so device and build specific that it would be very difficult to follow or keep up to date. That's why there's device specific threads once you're rooted.

If you want custom recovery, the appropriate place to ask is in your device-specific forum.
[Verizon Samsung Galaxy S 4] incubus26jc:
Hey guys, I'm not a regular gs4 forum contributor but my mother in law is having problems with hers.

She brought it to me saying she messed it up trying to upgrade.

She has no idea what shes even flashed to make it have issues.

The issue is she is not able to turn on wifi or hotspot. The toggles just dont turn on at all.

Looking at the phone.. looks like she is using a stock rom that has been rooted with a tether hack (found a few zips on root of her sd card)

(man, i can't believe she actually did this. We could have been hanging out months ago lol)

She said she kept getting an upgrade notification and wanted to upgrade manually to avoid loosing root. That is when she messed up.

I think she flashed a firmware upgrade from here maybe?

Her "about phone is all messed up with NC5 firmware and mk2 base band etc...

Looks like she does have some sort of safestrap recovery.

Thanks anyone. Sorry for not being more prepared

Incubus
[Verizon Samsung Galaxy S 4] decaturbob:
You probably need to get better understanding of odin process for starters.

sent by safestrap enabled bajarom
[Verizon Samsung Galaxy S 4] incubus26jc:
I am familiar with odin. I will see what i can do. She doesnt want to lose data.

Looks like this is the method she should have taken as far as upgrading and keeping root.

http://xdaforums.com/showthread.php?t=2726868
[Verizon Samsung Galaxy S 4] k1mu:
There's way too many questions left unanswered here to be able to help, unfortunately.

First, is this a Verizon GS4? What bootloader and what baseband version is she on now?

It sounds like the WiFi modules in the baseband don't match the kernel, so you'll need to figure out what version you have so you can choose the proper modules to get wifi turned back on.
[Verizon Samsung Galaxy S 4] erwinjmalmsteen:
Dear k1mu,

saferoot running in the s4 i9500 on kitkat (xxufnb7) without knox void?,please your advice
[Verizon Samsung Galaxy S 4] decaturbob:
saferoot will not native root any kitkat base phone

been said since kitkat was released

---------- Post added at 11:27 AM ---------- Previous post was at 11:24 AM ----------

this really isn't a saferoot problem, you may want to post in Q&A forum

remember rooting and custom roms are not for the faint of heart and you have to very careful especially with what is involved with kitkat with all the processes involved
[Verizon Samsung Galaxy S 4] incubus26jc:
She has a Verizon s4 and I think you are right on with your suspicion. I'm waiting for her to bring it back to me. I will try to find out more info. I did flash mk2 modules because that's what "about" said she had before she left with it last night just to see if it was an easy fix. No go

I understand and am blown away that she attempted this without saying anything to me about it. I've been developing ROMs for years just not for this phone. So I'm trying to play catch up in a hurry. Just need to familiarise myself better with safestraps limitations as a recovery I think.

I should not have posted here but the OP did help me in the right direction so I'm glad I did. Also all she kept telling me was that she did this "saferoot" thing lol
[Verizon Samsung Galaxy S 4] incubus26jc:
Thanks everyone. Shes upgraded to kitkat and rooted with working modules. Thanks again
[Verizon Samsung Galaxy S 4] izgil82:
Hello everyone. So I just got the replacement phone today and need to get it to the condition that my previous s4 was in when I was able to install sbreen's hyperdrive. I just rooted the phone. All this mk2 (that my phone has) or mj7 or whatever extensions are too confusing. I tried searching the forums for straight-forward instructions on how to install a custom rom on mk2 but couldnt find any.

I would really appreciate if someone advises me on the right steps to take.

Thank you, guys.
[Verizon Samsung Galaxy S 4] decaturbob:
there is a stickie in the general section....dont know how it can be missed...
[Verizon Samsung Galaxy S 4] KiwiBird97:
KNOX maybe causing the issue. Here are the following messages from each system.

MESSAGE FROM DEVICE

Prevention Information

An application has been forced to stop for an unauthorized attempt to access system in your device. It may be safe to delete an application from an authorized route. Check now?

MESSAGE FROM PC

Starting rooting program.

ro.build.product=hlte

ro.build.id=JSS15J

setsockopt() failed: Bad address.

this device is not supported.

kallsyms_addresses search failed.
[Verizon Samsung Galaxy S 4] dkephart:
Is something unclear about this portion of the output? You cannot use Saferoot on this device. It knows how to shut down Knox on devices where that is possible. Not so on yours.

See OP, or better yet, the thread for your device to see if there is an alternative.

Literally hundreds of posts on this thread say the same thing.
[Verizon Samsung Galaxy S 4] k1mu:
First, please don't use out of date copies of Saferoot. Current versions try to explain the "this device is not supported" message better.

However, the bottom line is that your phone has a kernel that's patched to stop the exploit that Saferoot from working. You must either downgrade somehow to an older kernel (which is probably not possible on a phone with a locked bootloader) or find another rooting technique.
[Verizon Samsung Galaxy S 4] k1mu:
First,start with the sticky in the General forum: http://xdaforums.com/showthread.php?t=2606501

Then, read this: http://xdaforums.com/showthread.php?p=48683964

OK, you've got a MK2 phone. That's Android 4.3. You can root it, install Safestrap 3.71, then install Hyperdrive 15.

Or, you can upgrade to NC5 (Android 4.4, Kit Kat) and install Hyperdrive 16.1.

HD 15 isn't too hard. Going to HD 16 is complicated, and requires a lot of attention to detail if you're not going to brick your phone. Seems to me based on your question that you need to do more research before you decide what to install.
[Verizon Samsung Galaxy S 4] gothicasshole:
Yea safe strap is a boot strap recovery it has to boot rite before the kernel and with the locked boot loaders we can only flash the official kernels it just depends on the boot loader for if you want 4.3 (mk2) or 4.4.2 (nc1 or what ever) so we are basically stuck lol from what I can tell the Verizon is the same way and if you took 4.4.2 you have to basically Odin flash to mk2 then re root then flash a 4.4.2 rooted rom re Odin flash the modules then any updater script or super.su script reboot
[Verizon Samsung Galaxy S 4] EagleTalon1:
Hi, can you make the same for the sgs5?

Grtx

Joey
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Doesn't SGS5 ship with kitkat? If so, read the thread, KitKat is NOT vulnerable to the exploit and will NEVER be rooted by this method.

::drops the mic::
[Verizon Samsung Galaxy S 4] EagleTalon1:
Hi, maybe I wasn't clear about what I mean, I'm looking for a way to root my sgs5 without getting Knox on 0x1
[Verizon Samsung Galaxy S 4] decaturbob:
If your S5 came loaded with kitkat this root method won't work and can't be made work

sent by bajarom v2.2 kitkat
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
No not unclear. The S5 is not saferoot compatible. You will have to wait (possibly months) for a root method to be achieved for that device (or/and older devices running KitKat) and there isn't even a guarantee that one will

EVER

occur.
[Verizon Samsung Galaxy S 4] EagleTalon1:
Ok, thankyou for your reply I'll wait then .
[Verizon Samsung Galaxy S 4] rjmohit:
Anyone try this on Verizon Moto G on 4.3?
[Verizon Samsung Galaxy S 4] bgmg:
Check the first post. Saferoot only works on pre kit kat os's such as 4.3 and if it's been reported to work on moto g, it would be listed with all the other models at the bottom of post one.

Additionally. This is a very safe root-method to try. It's doesn't trip any flags, and will tell you if your os is not supported and whether root failed or succeeded. It's as about as harmless as you get... so give it a try.
[Verizon Samsung Galaxy S 4] rjmohit:
Sure, just waiting for best buy to deliver my toy! :P

Also, I heard it still ships with 4.3 on it, so I have high hopes! :D
[Verizon Samsung Galaxy S 4] bgmg:
... And If your model has not been listed, it doesn't mean it won't work either.

If your device has 4.3, there is a good chance it will work.

And again Saferoot is as harmless a method as you will find.
[Verizon Samsung Galaxy S 4] jayc137:
Works with Samsung Galaxy Grand (I9082) a.k.a "baffin" too :good:
[Verizon Samsung Galaxy S 4] k1mu:
What build was that? If you'll let me know, I'll add it to the OP.
[Verizon Samsung Galaxy S 4] jayc137:
Build I9082XXUBMK3.
[Verizon Samsung Galaxy S 4] PrettyPistol555:
Allow Knox (don't disable), OR allow SuperSU to disable Knox?

Confused....

Thx for the awesome tutorial and root method, lot easier than my Note 3!
[Verizon Samsung Galaxy S 4] k1mu:
If SuperSU asks you for permission to disable Knox, allow SuperSU to disable it.

More clear now? :)
[Verizon Samsung Galaxy S 4] jayc137:
4.2.2 BMK3 build.
[Verizon Samsung Galaxy S 4] -=puma=-:
Cricket Galaxy S4 (r970cvvuemk4) It works!
[Verizon Samsung Galaxy S 4] k1mu:
A hint to people having problems (I'll add this to the OP as well):

If you use XDA to e-mail me a question, SET YOUR XDA ACCOUNT UP TO ACCEPT MAIL.

If you are set up to refuse mail, then your question will be ignored.

Actually, you shouldn't e-mail me. PM or post here.
[Verizon Samsung Galaxy S 4] GrapeBandit:
how long is this supposed to take? been on this screen for like 10 minutes already

its been sending the files for 10 minutes

---------- Post added at 04:44 PM ---------- Previous post was at 03:50 PM ----------

Never mind. issue resolved. i did a full wipe on my laptop the other day and just had to reinstall Samsung drivers. Thanks for the tutorial.
[Verizon Samsung Galaxy S 4] doctorwho2:
XT926 9.30.1 Worked like a charm!!

Thanks so much!! Can root be preserved with Voodoo during update to 4.2.2? Motorola XT926 182.46.10 & newer?
[Verizon Samsung Galaxy S 4] k1mu:
Please consider not quoting the original post when asking a single-line question. :crying:

So far, none of the 4.4.x upgrades have allowed root to be preserved.

It's possible that's being worked on, but unless Voodoo says it's been updated, I wouldn't assume that it's going to work.
[Verizon Samsung Galaxy S 4] mun_tez:
My linux kernel is 3.0.31 dated 7 jan and running 4.3 N7100DDUENA1 firmware and it says it is patched cant root. Whereas in main page its stated that it is compatible upto 3.5.5 dont understand why it failed when my kernel is so old ?? K1MU any solution or advice would be appreciated.
[Verizon Samsung Galaxy S 4] k1mu:
The 3.0.31 kernel is old enough that it may predate the flaw that getroot uses.

That's not important, as you're running a kernel either before the defect was introduced, or one with it patched. Either way, you'll need to find a new technique. Perhaps towelroot will work for you.
[Verizon Samsung Galaxy S 4] jpolcari:
Works for LG VS840. Go to www dot lg dot com and get the USB driver for your phone and install it first.
[Verizon Samsung Galaxy S 4] TH3F4LL3N:
What about 4.4.2?

Will this work for the new kitkat update for the galaxy s3 or any other devices running kitkat?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
no this will not
[Verizon Samsung Galaxy S 4] iua:
Hangs at file saving

Thank you very much, I was able to root HTC Evo Design 4G running ICS using saferoot.

I tried same on Samsung Galaxy SIII running Android 4.3. Kernel verison is 3.0.31. When I run install.sh on ubuntu, hangs at "Saving files to your Device". I saw previous posts in the thread with same issue, but I am not clear why the issue is, and how to overcome.

P.S. usb debuging is enable and my device is listed at adb devices.
[Verizon Samsung Galaxy S 4] Fe4r_[KiNg]*:
Today I tried to do the OTA update on my device, but when installation comes to 26% show an icon of android with red belly and says that there is an error during installation.

My phone was rooted with Saferoot method and I unrooted it with SU.

What can I do to update my phone?

Could it be a problem with frozen app, during the root It froozed KNOX automatically and when I was unrooting my phone I dont know did It unfrooze KNOX?

Forgive me for my bad english.
[Verizon Samsung Galaxy S 4] Sir_Eagle:
You'll need to re-root and unfreeze all apps, as well as reinstall any that were deleted.

or

Flash the NC5 .tar file using odin.
[Verizon Samsung Galaxy S 4] Fe4r_[KiNg]*:
How to unfreeze apps and how I can know which apps are deleted.

If I flash NC5.tar file using odin, will it trigger knox?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
unfreze any applications the you manually froze using the application you froze them with (usually a user would use titanium backup).

you must also undo any changes you made, such as xposed modules, firewalls, ad blockers etc)

if you don't know what you froze, or, especially, if you're unsure what preinstalled by samsung/your carrier applications you uninstalled (or as I once did, didn't backup before uninstall so had no way to restore) you would odin (instructions are readily available on this site) the official NC5 tar.

if you use the full wipe version (which honestly I might suggest you do, from the sound of things) remember to run a full backup with titanium before unrooting.

if odin is done correctly, you will not trip knox.
[Verizon Samsung Galaxy S 4] k1mu:
Before you take an OTA, you've got to return to stock. You don't need to re-enable Knox enforcement, but you do need to remove the xposed framework, restore any applications that you deleted, and so forth.

It's easier to re-flash the MK2 no-wipe ROM image. Then the OTA will work. Now that NC5 is rootable, you can flash NC5 no-wipe factory image and do it in one operation.
[Verizon Samsung Galaxy S 4] camerona:
Can you add code to detect if a user is on 4.4 and use the new exploit used by towelroot
[Verizon Samsung Galaxy S 4] doncaruana:
Why wouldn't you just use towelroot to begin with? It is such a simple and fast method to root with towelroot, I'd go there first anyway. (http://www.towelroot.com/)
[Verizon Samsung Galaxy S 4] bgmg:
Does towelroot trip the Knox flag?

---------- Post added at 07:06 AM ---------- Previous post was at 07:00 AM ----------

1. Why would a developer incorporate someone else's program into his own. Then he would have to support someone else's program as well as his own, and he would be trampling on someone else's territory.

2. More than likely towelroot will trip knox. The point of saferoot it to root without tripping knox.
[Verizon Samsung Galaxy S 4] mielletseed:
Please read tho OP of the towelroot thread.

For me it didn't trip the knox flag ...
[Verizon Samsung Galaxy S 4] bgmg:
I read it once and missed it. Read it twice and found it ;)

Interesting. In regards to trippjng Knox, it says "Most probably not. My phone says KNOX WARRANTY VOID: 0x0, but no promises".

This combined with your confirmation sounds promising and relatively new. Thanks for the info.
[Verizon Samsung Galaxy S 4] camerona:
1. If he just implements the original exploit Linux kernel CVE-2014-3153. I'm not asking him to steal his code just write his own code to exploit this and add it to his app.

2.This is a safe root.
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
This is a saferoot, because of the way it does it and because of the previous root for these builds (to which I am a victim) was not safe.

Regarding knox tripping, the only way to trip knox counter is to mess with the original bootloader
[Verizon Samsung Galaxy S 4] kyij:
Connected As Installer

I got an S3 off a friend and it has 4.3 installed so I found this forum.

Anyhow, the problem I am running into is that the Saferoot (install .bat) will only recognize the phone while it is in installer mode - which is automatically enabled for the first 30 seconds when it is plugged in. Then it switches to MTP mode and I then get an error that "no devices found" in the middle of the image dump or what ever step it gets to.

I am assuming it is a driver issue, but am not sure if there are modes that I can change to fix this on the phone - have it just stay in installer mode..

Thanks.
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
when it switches to MTP switch it back and forth to PTP, this resolved the no device issue for some
[Verizon Samsung Galaxy S 4] kyij:
I have tried this. I switched 5 times on each and waited a while on each one. I have tried to uninstall reinstall drivers, etc.. My next step is to use a different computer or a VM unless someone else has a different idea.
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Have you cleared your device's adb cached machines (revoke usb authorizations.
[Verizon Samsung Galaxy S 4] k1mu:
Yes, I could. That would be really, really rude to Geohot. He's built Towelroot and deserves to collect whatever contributions he can for that work.

Eventually, I might consider updating this to work on Kit Kat. but not for a while, until it's not infringing on a very valuable member of this community.
[Verizon Samsung Galaxy S 4] k1mu:
The S4 starts in installer mode, flips temporarily to MTP, then flips back. So plug in and wait a couple of minutes, then check if it appears in "adb devices".

Or, try the saferoot app from here. Not my work, but based on it.
[Verizon Samsung Galaxy S 4] camerona:
Sorry i really was not thinking about it like that. I was just thinking about how you could possible expand the amount of users your root works for again i'm sorry.
[Verizon Samsung Galaxy S 4] k1mu:
No need to apologize, as you asked a reasonable question. I'm just providing my rationale.
[Verizon Samsung Galaxy S 4] touji:
thanks k1mu for your contributions, i would like to ask, i have N7100 4.3 and i have rooted with cf-autoroot, i did it for repair reasons, i have 049 imei and no network, after i rooted, i repair imei and network using Z3X repair software, but after awhile the signal will be no service and the Super SU is gone, i think that something or maybe KNOX is disabling my software repair/patch, so everytime i need to do root again, write imei and repair network, so my solution is not permanent...

if i use this root method you have provided, will it be good for N7100 4.3 N7100XXUEML3 and after restart the KNOX will not disable the root and make my N7100 no service again?

the Z3X software make patches to my modem firmware so i can get signal and make calls but it would require root access...
[Verizon Samsung Galaxy S 4] thebat1:
64 bit compatible?

Does safe root work on Vista 64 system.. when I click install bat it opens real quick and closes???:confused:
[Verizon Samsung Galaxy S 4] k1mu:
Yes, it'll probably work on anything from Windows XP onward. :)

You probably unzipped it incorrectly, so the batch file is generating an error and closing.

Open a command prompt (start/run, type cmd then enter). Use the "CD" command to change to the directory where you unzipped, then type "install.bat". You should now see the error.

If unzipped properly, you should have an install.bat, unroot.bat, install.sh, unroot.sh, and a folder called "files" with the rest of the stuff.
[Verizon Samsung Galaxy S 4] k1mu:
I would start out by flashing a factory stock ROM to fix the IMEI problem. However, it can't hurt to try this as it'll try to block the Knox runtime.
[Verizon Samsung Galaxy S 4] thebat1:
saferoot error and May-2014 OTA update

I do have all those files your mentioning,,and the folder called "files"

here is what it said..when I ran install.bat

C:\>cd saferoot

C:\saferoot>install.bat

The system cannot find the path specified.

--- Samsung Galaxy S4 Android 4.3 Root ---

--- Based on the CVE-2013-6282 exploit by cubeundcube ---

( was unexpected at this time.

C:\saferoot>

I also just read this some where??

If you have a rooted Note II (SCH-I605) on the Verizon network and you need to preserve root-level access

on your Note II, then you cannot allow this OTA update to install. Furthermore, when the KitKat version

is finally available as an official OTA update, you'll have the same problem and will need to avoid it

until a new method is discovered to root the phone under its new security system. Past techniques, like

Saferoot, no longer work under the May-2014 update of Android 4.3 or the upcoming Android 4.4 update on

the Verizon network.

Can anyone confirm that is true? if so Saferoot will not work?

Sorry dont recall link of the quote..

thanks for the reply
[Verizon Samsung Galaxy S 4] k1mu:
I'll bet you're running as an adminstrator.

Two things to try:

start/run, then type CMD /X and enter. Try it again.

Or, rename install.bat to install.cmd and try running it that way.

Yes, it's true. If you upgrade to a kernel released past april or so, especially an Android 4.4 release, it's patched. Saferoot will no longer work.