yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] k1mu:
That's a pretty old kernel release.. what kind of device and what build are you running?

I'd assume that it's a Galaxy Note 2, but just because you tried a root technique for a GN2 doesn't mean that it actually is a GN2.

Based on the post you link to, it's not bootloader locked, so rooting should be pretty easy.
[Verizon Samsung Galaxy S 4] skeven:
Might want to add a tidbit to the op about what BusyBox is, since it's the first thing encountered on the install.

Also is there a verbose mode?
[Verizon Samsung Galaxy S 4] k1mu:
If you don't know what BusyBox is, you're in the wrong place. :)

Seriously, I have no idea why anyone would want root without a reasonably complete set of shell utilities, but that's just me. I'll add something to the OP about busybox,

Verbose mode? No. What would you like it to tell you? Most of what the installation does is pretty boring (if it works) and there's appropriate errors when it doesn't.
[Verizon Samsung Galaxy S 4] k1mu:
Further on this - the kernel bug that allows Saferoot to root your phone was introduced in Ice Cream Sandwich (Android 4.0) so anything earlier won't be rootable. Anything past that up to Kit Kat is fairly likely; some of the Jelly Bean releases running kernel 3.4.x have been patched, and all of the Kit Kat releases I've seen have been patched.

As has been stated before, if Saferoot says the kernel is patched, then there's nothing I can do to help you root. Either install a release with a vulnerable kernel, or try some other way to root.
[Verizon Samsung Galaxy S 4] joetrizeo:
Works! Please add this phone to the list of Successes!

•Verizon Galaxy S3 Mini SM-G730V, MI9
[Verizon Samsung Galaxy S 4] shankarana:
Thanks for clarification and advice
[Verizon Samsung Galaxy S 4] soralz:
Park at here first, will be getting my Android 4.3 Note II N7100 tomorrow.
[Verizon Samsung Galaxy S 4] Phatboyj420:
The OP states as verified success

AT&T Galaxy S4 ZOOM

I specifically am trying to root a Galaxy S4 ZOOM SM-C105AUCUAMJ2

Can anyone verify this will work for my above stated device

This is my first go around with a device sporting a F****ing Locked Bootloader so any added support/advice will be greatly appreciated

Thank you in advance
[Verizon Samsung Galaxy S 4] jmjoyas:
There is absolutely no harm in trying this method. It attempts to root using an exploit and it could either succeed or fail. There is really no chance of a brick.
[Verizon Samsung Galaxy S 4] Phatboyj420:
Thanks I'll give her a try
[Verizon Samsung Galaxy S 4] Phatboyj420:
Permission to share request

[MENTION=3940199]k1mu[/MENTION]

First Thank You

I just Successfully rooted my Wife's Stock Galaxy S4 ZOOM SM-C105AUCUAMJ2 Jelly Bean 4.2.2

I would very much like to post a thread about this tool in the dedicated device thread as there is currently Zero/0 development occurring on this device

If allowed I would graciously provide you with all deserved credit.

I would also only provide access to Your tool via a direct link to your OP.

Thank You in advance You have helped me greatly.

Now if only I can find a working custom recovery for said device preferably TWRP I will be satisfied completely!!!!
[Verizon Samsung Galaxy S 4] k1mu:
I'm glad it worked for you. No problem with creating a thread discussing the root and pointing here. My only concern is that people link back here so that any updates get picked up. I already get enough repeat questions about this, so I'd like to keep the number of "clones" down.
[Verizon Samsung Galaxy S 4] azuziel:
Sweet. Thanks for sharing. Now I know i can use it too, i had stayed away from it bc of what i read, now i can use it too! Sorry if i gave you palpitations lol.

Sent from my SGH-I337M
[Verizon Samsung Galaxy S 4] Craleb:
Keep in mind though I do have a a few knox apps frozen and allowed superSU to disable knox. So just be safe. Lol.

I also haven't messed with many settings aside from getting rid of the custom boot getting rid of dock icon lables and the brightness slider which was was a default setting... I'm too scared to try roo many things... i don't want a bootloop!

Oh and hiding battery icon!

I used the latest xposed installer.
[Verizon Samsung Galaxy S 4] TemporalShadows:
Your description implied you were running it on a corporate network, and you didn't contradict k1mu when he explicitly mentioned it. You could have responded to his comment by saying that it was a separate, secure environment, but you didn't.

I had the option of running it on a segregated network, but personally when I tried vroot I ran it on a laptop running Wireshark that I wiped and reimaged after, while connected to the internet a mobile hotspot so that no other devices were possibly connected just to be extra safe. It was more out of curiosity than anything, because I already knew they were sending data back. I never tried kingo because at the time kingo wasn't reported to be working on Verizon MJ7.

k1mu isn't one of my "budz", I just disliked your response because you were harsh and belittled his opinion and skills. You chose to take what he said personally (I wouldn't have, I would have clarified what I did) and then you went ahead with the public shaming instead of a simple "I disagree."

I deal with mostly Hyper-V for virtualization. I've messed with Cisco a little, but I mainly work with HP networking equipment.
[Verizon Samsung Galaxy S 4] azuziel:
If anyone here thinks i was/am promoting the use of Kingo over this script, i am not. My goal was to simply share what i was told from the source, and to share the results of my lab. Given the choice between Kingo and this method, id use this method in this thread every time for reasons already discussed (open source). I really just wanted to share what i found.

Sent from my SGH-I337M

---------- Post added at 11:17 PM ---------- Previous post was at 11:05 PM ----------

Ok, i re-edited my post and added some more detail when i got home. While i was responding initially, i was in a parking lot waiting on a coworker to finish up a window.

I did so say it was secure /segregated, go back and read it and check the time of the edit, long before your latest reply. I did also briecly touchon vlans ( segregation) and dmzs in my response. Its quoted. I didnt like him assuming i was irresponsible. I already clarified that. Splitting a network isnt Ll that tough. I have the luxury of having multiple 5505s laying around, and a sandbox environment i had setup for hyper v testing.

If youre all interested in actually getting to the bottom of this, with an actual concrete answer, more than happy to repeat and record the lab for use. The problem with forum, is they dont pass emotion well, i wasnt angry, in fact i wad laughing with a coworker driving home about it.

I have no reason to lie, or make up info. I was tired of reading "under investigation" everywhere that i read here in regards to it. I knew vroot was unsafe for sure, kingo wasnt sure, and since this investigating has been ongoing for months, thought id get to the bottom of it myself, or as close as i could get on closed source software.

Sent from my SGH-I337M
[Verizon Samsung Galaxy S 4] TemporalShadows:
XDA doesn't notify of replies, so I didn't see your edit. To be precise, you mentioned having knowledge of those things, not that you used them in your analysis.

Anyway, back on topic before the mods come calling.

The point is/was that both are closed source, and this one is open source, so we can easily check the source and see that it's safe (without Wireshark or network monitoring). We don't need to worry about the safety of VRoot or Kingo except that it's been established in other threads that they leave no malicious software on the handset, so no need to ODIN and re-root if you've used them.
[Verizon Samsung Galaxy S 4] Nick3193:
Back on subject ...

This was by far one of the easiest roots I've done. Excellent work. One minor issue, in the install.sh script you appear to be missing the "shell" in the last adb command (where busybox is installed):

echo "installing busybox"
echo "unlock your phone and give permission for the install to run."
adb "su -c /system/xbin/busybox --install -s /system/xbin"
echo ""

I attempted to run the command directly and had the following message show up on my phone (after I granted root access to the adb shell):

"An attempt to access a secure area on your phone without authorization has been blocked."

So I then installed Titanium Backup and froze Knox; this prevented the message. (I'd already disabled the Verizon Security app so no warnings there.)

In either case the busybox install seems to fail due to the file system being mounted read only:

$ adb shell "su -c /system/xbin/busybox --install -s /system/xbin"
busybox: /system/xbin/[: Read-only file system
busybox: /system/xbin/[[: Read-only file system
busybox: /system/xbin/acpid: Read-only file system
busybox: /system/xbin/add-shell: Read-only file system
...

Not really a problem since it can be installed in other ways once you have root, but I thought you might like to know.

Bottom line, I have root and I'm happy again. Thank you!!
[Verizon Samsung Galaxy S 4] azuziel:
Absolutely. I agree 100%. Had this method been available when i needed it, i would have been all over it. So i went with the safest method available to me at the time, and not before labbing. Then i just wanted to share my results with the community. To be clear, i said i flashed a coworkers unit, i didnt say i used my production environment to do it. Not like i jacked in to a dc to do it (funny stuff).

Guys, an olive branch. The tinfoil hat thing was a joke, in fact all my coworkers think im so overly cautious they made me a tinfoil hat (like actually) then labelled it 256 AES, i'll snap a shot of it monday. I wear it proudly on my twitter.

After rereading the first few paragraphs of my post, i will edit and remove those comments. My apologies if i shat on anyone's work, was not ny intention, but i can see now rereading how it sounded.

Apologies to you both.

Sent from my SGH-I337M
[Verizon Samsung Galaxy S 4] Swimboy46163:
How do you install busybox once rooted?
[Verizon Samsung Galaxy S 4] azuziel:
Nice catch. And i second the fantastic work. Easy method, and verifiable.

Sent from my SGH-I337M
[Verizon Samsung Galaxy S 4] Sniper_5:
Still no luck for me, same errors.
[Verizon Samsung Galaxy S 4] azuziel:
Has anyone managed to get busybox installed ? Maybe missing a chmod line. Busybox is essential i believe (only been working with android 6 weeks, bes/bb guy before). What about letting supersu fix perms?

To the gentleman whom wanam'd to remlve custom message.....were you able to successfully backup with kies? Or can you poll for ota updates (as long as youre latest, wouldn't want it to actually update on you).

Just curious.

Sent from my SGH-I337M
[Verizon Samsung Galaxy S 4] Surge1223:
Playstore>>busybox>>install.

Also lets stop with all the bickering here. And pulling out credentials doesnt help anyone. You dont have to be an IT specialist or a programmer to express your opinions infact I dont have any IT degrees, mine are in science but I like to think I know a thing or two ;). Lets just be happy we have an open source solution for root.
[Verizon Samsung Galaxy S 4] Sniper_5:
Edit, ran the program with Kies running in the background. Still no root but a different result (see pic 2)
[Verizon Samsung Galaxy S 4] k1mu:
OK, thanks. Sorry if I set you off, and it was over the top for which I apologize.
[Verizon Samsung Galaxy S 4] k1mu:
I believe you're running an older version of the updater script - the current one uses SuperSU. Please try re-downloading.

However, why are you running Kies? I don't know that will interfere, but I'd shut it down before running the rooting tool.
[Verizon Samsung Galaxy S 4] k1mu:
I thought that the busybox install would take care of remounting. No problem, I've added the commands to the script to remount system as read/write then remount when done as readonly. Thanks for reporting this.
[Verizon Samsung Galaxy S 4] Swimboy46163:
Any idea why Knox doesn't show up in titanium backup?
[Verizon Samsung Galaxy S 4] jwhistler:
How did you get custom boot screen back to official?
[Verizon Samsung Galaxy S 4] Swimboy46163:
Xposed installer-> winam xposed
[Verizon Samsung Galaxy S 4] k1mu:
Here's what's REALLY happening.

Chainfire allows bundling SuperSU (non-PRO, of course). He wants the apk to be called "Superuser.apk" and installed into /system/app/Superuser.apk. That's why, even though it's called Superuser.apk, it's actually SuperSU.apk.

I've put this back the way it originally was to comply with his wishes.
[Verizon Samsung Galaxy S 4] marlar:
Getting a 4.4 update

Hi,

I succesfully rooted my S4 back in January and have been very happy with it.

Today my phone has downloaded a 500 MB 4.4 Kitkat upgrade which puzzles me because ever since rooting my phone it has said something like "OTA upgrade is not possible because the firmware has been altered" when I tried looking for updates. Not exactly those words, but you get the point.

But today it found and downloaded an upgrade by itself and I have two specific questions:

1. If I do upgrade to 4.4, will I loose my root access?

2. Is it possible to make the phone forget about the downloaded software package? I have only the option to postpone the installation up to 3 hours. I would rather make it forget all about it until I actually decide by myself that I wish to upgrade, in which case I can just download it again.

Thanks,

Martin
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Yes

You should freeze/disable the update app using titanium backup or some other capable software.

Sadly, I don't know the answer to question 2
[Verizon Samsung Galaxy S 4] acraigl:
You will almost certainly lose root. You may be able to keep it by setting SuperSU to Survival Mode, but there is no guarantee. I'm not sure if there is yet an exploit for KK, so if you're happy I would try to hold off.

On blocking altogether, here's a link that should help

http://androidforums.com/samsung-galaxy-s4/780592-possible-block-ota-updates.html
[Verizon Samsung Galaxy S 4] k1mu:
SuperSU survival mode hasn't worked so far. I wouldn't count on it. And there's no known exploit for Kit Kat.

You're able to downgrade to a rooted release, then upgrade to a rooted version with Kit Kat, so all is not lost. Each upgrade does restrict you further.
[Verizon Samsung Galaxy S 4] Phatboyj420:
I fully understand all links will point to your original Post Thanks again for your root method and your permission to repost in my device thread you Rock!!!

@k1mu

Here it is http://xdaforums.com/showthread.php?t=2757233

please check it out and voice any concerns you may have

of course i will be adding Info to it as I find time but I wanted to get the word out as the device has a serious lack of development interest also it lacks a dedicated forum as far as being AT&T device specific My hopes are that this will help "I can't thank you enough"

EDIT:

I just contacted a mod about having my thread moved to the original development section so if the above link does not work this is why

I'm not sure if it will be moved or not
[Verizon Samsung Galaxy S 4] lancasterv3:
Hello all, I am writing this for my friend who rooted his Verizon S4 (model number SCH-I545---Android version 4.3). I am not familiar with Samsung handsets but I am familiar with android as a whole (Rooting/ROMS/ADB etc.) He rooted his phone two days ago using the Saferoot method without any problems and he is happy with root (thanks to all involved). He then attempted to take the OTA which is Jelly Bean 4.4, however when the update attempted to install it failed with error 402. From what I have been reading it seems the only way to get him back to stock is via ODIN or possibly a factory reset. I just wanted to check here to see if there is a different method for him to take the OTA. He lives several hours away from me and is not familiar with android so I do not want to direct him to ODIN at this point if it's not necessary. Thanks in advance :laugh:
[Verizon Samsung Galaxy S 4] gadget069:
At this point I would not take any OTA. He may not be able to gain root afterwards.
[Verizon Samsung Galaxy S 4] Craked:
Verizon Galaxy Note 2 4.3

whats up all .. i wanted to know if the galaxy note 2 model number SCH-I605 baseband I605VRUAND3 can be rooted yet. i tried with this program but it said that the kernal is patched.. is there any way i can go around this? any help?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
No your kernal being patched mean exactly what it says, this route will not work for you
[Verizon Samsung Galaxy S 4] lancasterv3:
He actually gained root for the sole purpose of attempting to recover deleted pictures. Root is not necessary for him at this point.
[Verizon Samsung Galaxy S 4] Craked:
damnit so no more free wifi router for me huh .. so i cant root it at all
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Have you attempted to unroot via SuperSU and the instructions at the start of this thread? If no customization was done to the rooted phone (i.e. installing Xposed framework abd modules) the OTA shouldn't have failed, but unroot is the next step I'd suggest.

---------- Post added at 09:22 AM ---------- Previous post was at 09:20 AM ----------

No idea if you can root with another method, you should ask in you device's board, not the VZW S4 board
[Verizon Samsung Galaxy S 4] lancasterv3:
That's what I thought initially, the OTA should have gone through and wiped out root but that is not the case.I had him hold off on the unroot script until I had gathered more information about the exploit. During my digging I have read other users using the unroot method with the same issue. I am still currently trying to figure out what he changed.
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Be sure that those other users unrooted in SuperSU first before running the script
[Verizon Samsung Galaxy S 4] lancasterv3:
Gotcha thank you, I will have him give that a try.
[Verizon Samsung Galaxy S 4] lancasterv3:
Just a update, that did the trick thanks again.
[Verizon Samsung Galaxy S 4] Craked:
Oh OK I didn't even realize I was in the gs 4 thread .. but as I seen in the description ... that the note 2 was compatible with this safe root ..
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
If your specific device/build combination is listed then you probably have security updating turned on. Odin or Otherwise restore your device to the base of the build, then turn off security updates (on the S4 it's settings>more>security) then run root. If your specific device/build combination isn't listed then I may not have the needed kernel for exploitation
[Verizon Samsung Galaxy S 4] ITAdmin:
Verizon STILL sending OTA updates to my Note II after SafeRoot

Hello all!

Thanks for the great info. I was able to install saferoot and get my phone back to some semblence of usefullness after my phone took the I605VRUEMJ9 update, without my permission nonetheless, but now that I have it rooted, I need to stop them from doing any more updates unless someone here says it's safe and that it won't remove my root!

Can anyone advise how I can stop the update that's currently prompting me to install it and prevent them from installing in the future?

Thanks for all the help here!!

ITADMIN
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
If you device is S4 then you need to freeze SDM and Updater (using Titanium Backup or other capable software), one or the other may not appear on your specific device.
[Verizon Samsung Galaxy S 4] ITAdmin:
Thanks for the reply!

I have a Galaxy Note II. Would the proceedure be the same as for the S4?

Please advise as this update popup is driving me nuts!

Thanks

Tom
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
You'll have to ask in the Note 2 board, as I doubt very many here in the S4 board can tell you for sure
[Verizon Samsung Galaxy S 4] k1mu:
Seems like you don't have a real /bin/sh.

Switching to /bin/bash won't work because bash isn't a standard shell, so it's not guaranteed to be there. /bin/sh is, but whatever you have isn't really compatible with the standard /bin/sh. Perhaps you can report this defect to your distribution. :laugh:

It's possible that changing the "[ xxx ]" to "test xxx" would make this work with whatever you have installed as /bin/sh. Having a compatible /bin/sh from your distribution would be better. Shame that Debian can't get this simple thing right.

I'll see if I can spin up a Debian VM to try this when I get a chance.
[Verizon Samsung Galaxy S 4] omegaflare:
It works with S3 T999 (on Quantum.4 mod similar to slim ROM). Version 4.4.2.
[Verizon Samsung Galaxy S 4] jeayci:
I'm quoting this because I had the same problem, and the solution that worked for me wasn't one I saw anyone else mention (apologies if I just missed it). Despite having tried running Install.bat as administrator - with no luck - what finally worked for me was to actually log into my administrator account and run it from there. Easy peasy from that point on, so perhaps worth trying for anyone else who encounters a similar problem.
[Verizon Samsung Galaxy S 4] k1mu:
I built a Debian Jessie install and saw what you did. Apparently Debian ships /bin/dash and calls it "/bin/sh".

The issue is that there's a problem with the install.sh. Lines like

if [ "A" == "A" ]; then

shouldn't have two equal signs. Bash fixes that, as does /bin/sh on a number of other platforms. but if I fix it to single equal signs it works with Debian's dash as well, so it's on me to fix. Thanks for the report!
[Verizon Samsung Galaxy S 4] speed2001:
Fixed waiting for device freezing

Hi all, just rooted my ATT SGH-I337, MK2 and it went easy after I figured out why it was hanging at waiting for device message. I've followed the instructions of the first posting and downloaded Kies and it was able to find my phone ok but running the install bat it always frozen @ waiting for the device... no matter what I tried it always stopped there... then, at the far end, almost giving up, I've downloaded the Samsung drivers for mobile and voilá...all went smooth.

So, do not follow the first post advice of getting your drivers from Kies, use instead the latest version of Samsung mobile drivers if you are stuck at the waiting for device message.

Thank you all that developed and perfected this exploit. Works like a charm and I'm a happy camper now that I won't have to endure the 4.4....

Cheers

Speed:laugh:
[Verizon Samsung Galaxy S 4] XRSTOY1:
Can't get Root reflashed MK2

After flashing back to Mk2 and trying to regain root. The installer will not see the phone no mater what I do. I've redone drivers, tried multiple computers I've enabled and turned on Debugging. All of that. EVERYTHING else see it. But not ADB it sees my Galaxy s3 no problem.

I first rooted the phone without safe root. But I can't find anything anymore I tried to use terminal emulator but the phone blocks it. Anyone have any Ideas? should I reflash MK2 in odin?
[Verizon Samsung Galaxy S 4] k1mu:
speed2001 a couple of posts above suggests trying the Samsung mobile drivers versus Kies.

What I would start with is to kill the ADB server with "adb kill-server". Don't plug in any other phones to that PC. Now, plug in your phone.

Is the USB device recognized? What kind of device do you see?

I know that this can be VERY frustrating. I recently spent three days on and off trying to get my brother-in-law's Galaxy Camera to be recognized on his PC. Maddening. I kept coming back to it because I wouldn't let it beat me. (And I'm OCD.)
[Verizon Samsung Galaxy S 4] marlar:
Thanks for the reply. I coulnd't find the app with Ttianium (didn't know the name of it) so I ended up simply long-pressing the notification and force-closed the app. Then I deleted the downloaded update file at about 500 MB from the cache folder.

That worked, it hasn't bugged me about any update after that.