yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Original Android Developme] dahrat:
hmm i skimmed through the thread, seeing alot of failures but not sure on the solution.

ATT version here. just got my phone yesterday. didnt update. its on 4.2.2. installed drivers via windows update. and then installed kies too. yes i have developer options enabled and Debugging on. ran run.bat as administrator.

Press any key to continue . . .

[*]

[*] Waiting for device...

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

[*] Device found.

[*] Pushing exploit...

2976 KB/s (1283460 bytes in 0.421s)

[*] Pushing root tools...

3513 KB/s (366952 bytes in 0.102s)

3233 KB/s (1867568 bytes in 0.564s)

2828 KB/s (1578585 bytes in 0.545s)

pkg: /data/local/tmp/Superuser.apk

Success

[*] Rooting phone...

[+] This may take a few minutes.

[-] Failure.

[*] Cleaning up...

[*] Exploit complete. Press enter to reboot and exit.

Press any key to continue . . .

I had the same issue with Casual. on both my debian and windows

EDIT: Just Noticed my Firmware Version. MF3. im assuming this is why i cant root it with these methods.
[AT&T Samsung Galaxy S 4 Original Android Developme] mannybeekause:
Hello, I ran into the same issue, I realized i had the Superuser.apk installed using the superuser I found on Play store. I uninstalled all superuser tools and apps and I ran motochopper again and it all worked.

Hope that helps!!!!
[AT&T Samsung Galaxy S 4 Original Android Developme] RockRatt:
Yep MF3 probably updated by itself. Other users had that happen as well. Now you will have to use safestrap.

UNLESS you were rooted already and had installed a MF3 ROM in the past and have a cwm or twrp recovery?

Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
[AT&T Samsung Galaxy S 4 Original Android Developme] dahrat:
I WISH!!. MF3 stock out of the box, lucky me. thanks for the reply and helpful information. im going to look into safestrap. anything get get off stock.:p
[AT&T Samsung Galaxy S 4 Original Android Developme] MotoDefier:
If you would like to use the root tool I made you can pm me, I am removing the link for now so i can work on further device support. I will start a new thread shortly for the tool itself. Right now it HAS BEEN TESTED ON the qualcomm variants of the s3 and the s4 on AOSP4.3+TWRP if you would like to test it on your devices setup PM me so we can test and add additional device setups and devices to the support list. It should work on every device that motochopper works on since it is based on motochopper with new techniques to override the changes made in 4.3 mainly SE-linux builds but may still exist in other builds of 4.3 as well. Because of the script I use it is as safe to try as motochopper, I.e. if it doesn't work for you it will only leave you in the same boat as motochopper currently does which is you will have the superuser.apk installed but no root access. If motochopper did not brick your device this tool will not brick it either.
[AT&T Samsung Galaxy S 4 Original Android Developme] shauna_cc:
THANK YOU!!

You're the best!! Thanks, couldnt figure it out god dammit haha
[AT&T Samsung Galaxy S 4 Original Android Developme] redhonker:
Once it's rooted, is there a step to stop OTA update?

And how would I apply official ROM upgrade later?

Thanks
[AT&T Samsung Galaxy S 4 Original Android Developme] MotoDefier:
If you have TWRP or CWM recovery installed, it should block OTA updates because of the custom binary counter, at least this was the case on my T999L. To install the official upgrade, flash the stock recovery back to the phone with ODIN. purchase triangle away reset the binary counter then use the system modified work around to disable superuser at boot to check for your ota, you will also want to purchase SuperSU and check the ota survival mode before installing the update, once you have it updated you can flash TWRP OR CWM back to the device if you want.
[AT&T Samsung Galaxy S 4 Original Android Developme] redhonker:
I don't intend to use custom ROM. Only want to root it for things such as launcher and firewall.

In that case, do I need to disable OTA? If yes, how could I do it?

Thanks
[AT&T Samsung Galaxy S 4 Original Android Developme] MotoDefier:
TWRP AND CWM are not ROMs, they are recoveries and they will trip the flash counter and disable OTA'S you can run the stock ROM rooted with one or the other and you don't have to worry about a forced OTA you can then reflash the stock recovery and reset the binary counter to update the stock ROM as previously stated. You don't need root to run a different launcher.
[AT&T Samsung Galaxy S 4 Original Android Developme] redhonker:
OK. The only use case I left is firewall which can treat WiFi, Data and Roaming differently. All I found so far says it requires root.

My biggest concern is: if I root and OTA update comes, will it break the device? If not, I think it's OK.

Thanks
[AT&T Samsung Galaxy S 4 Original Android Developme] MotoDefier:
On most devices now you get a notification there is one available and you have to chose to download and install, but flashing the custom recovery will guarantee it to be blocked, some older devices bricked when applying ota's but most now just remove root or fail to install. It might leave you in a boot loop but you can flash the stock firmware back with Odin if that is the case, also if you are using a custom recovery you can make a full backup of the device and would be able to flash your backup if you run into any problems. There are a million different ways to do it, its your choice, if you don't want to go this route I'm sure someone else could give you another method.
[AT&T Samsung Galaxy S 4 Original Android Developme] ga8r13llitt05:
how to unroot?
[AT&T Samsung Galaxy S 4 Original Android Developme] surge27:
[MENTION=4229979]djrbliss[/MENTION], will we ever see Motochopper revisited for the MF3 build? I'm sure many here will bring lots of Xma$ presents....
[AT&T Samsung Galaxy S 4 Original Android Developme] MotoDefier:
Try this, you need twrp but it should work

https://www.cubby.com/pl/AOSP-RT.zip/_8993b27f32b9447996c3611b3af19cd8
[AT&T Samsung Galaxy S 4 Original Android Developme] surge27:
What is this?
[AT&T Samsung Galaxy S 4 Original Android Developme] MotoDefier:
Its a root exploit I modified that takes care of the issues the current version of motochopper cannot handle due to changes in 4.3 I will have a specific post for it soon, I just haven't had time to post it. For now I have tested it on the s3/s4 not MF3 YET but it should still work, it will either work or fail but it will not harm your device unless it is used on a non Qualcomm device. You MUST HAVE TWRP installed.
[AT&T Samsung Galaxy S 4 Original Android Developme] surge27:
You consider safestrap TWRP? For the MF3 folks...that's all we got. At least that I've seen.
[AT&T Samsung Galaxy S 4 Original Android Developme] MotoDefier:
This is not safestrap. I call it AOSP-RT (Android Open Source Project -Root Tool) and it requires TWRP to work because of file permissions in production builds.
[AT&T Samsung Galaxy S 4 Original Android Developme] surge27:
I dont think MF3 owners have twrp
[AT&T Samsung Galaxy S 4 Original Android Developme] MotoDefier:
MF3 is a firmware version instead of a device, double check with twrp but if you have twrp for the S4 there shouldn't be any reason I can think of any reason that would disallow you to flash it in Odin just because you have MF3 firmware.
[AT&T Samsung Galaxy S 4 Original Android Developme] WordsworthESP:
I think what they're asking is how can you have TWRP without some kind of previous exploit. I could be wrong, but that's how I read it, as my thought process is similar.

On my last device (HTC Inspire) you had to root and unlock the bootloader before you could flash a custom recovery, so if their experiences are similar, I imagine that's where the confusion arises.

Sent from my MF(3)ing S4
[AT&T Samsung Galaxy S 4 Original Android Developme] MotoDefier:
Unless its different for other samsung devices, I used Odin to flash twrp to my device before using an exploit. With all of the samsung devices i have owned or worked with. Unlocked bootloaders and s-off is not an issue that is mainly and HTC thing.
[AT&T Samsung Galaxy S 4 Original Android Developme] davemccorkle:
AT&T S4

Updated my AT&T S4 last night to 4.3 from AT&T. Totally stock! Have the latest drivers, turned on debugging mode and started run.bat. A security message came up and said an unwanted program was blocked. I rebooted and tried again and now I get this.

[*] device found

[*] pushing exploit...

3612 kb/s.....

[*] pushing root tools...

2816kb/s...

pkg:/data/local/tmp/Superuser.apk

Failure [INSTALLED_FAILED_ALREADY_EXISTS]

[*] rooting phone....

[+] this may take a few minutes

[-] failure

[*] cleaning up....

[*] exploit complete. press enter to reboot

I reboot and not rooted.

I am running Windows 8.1 64bit

Thanks
[AT&T Samsung Galaxy S 4 Original Android Developme] MotoDefier:
http://xdaforums.com/showthread.php?t=2554493
[AT&T Samsung Galaxy S 4 Original Android Developme] nomoiphone:
HELP...I'm going nuts trying to figure this out.

I'm stuck on "daemon started successfully" and I've tried to get through all the posts to find my problem but keep coming up empty or overwhelmed. I've ticked USB Debugging and have the latest version of Kies3.

Here is a screen shot of my device...Is the 4.3 the issue? Thanks!
[AT&T Samsung Galaxy S 4 Original Android Developme] Braxton355:
Will someone help me I'm getting this same error and the phone is on 4.2.2 it's really pissing me off sorry to say that. But it installed SU and whenever I try to update the bianys or whatever it gives me an error on the app telling me to contact a developer so please help. I'm not trying to me a douche I'm sorry about that but it's aggrivating me. I tried the option of installing a recovery it also doesn't work. It reboots me to recovery and then it goes to stock recovery. Not a custom. So Idk what else to do. I tried installing a recovery via adb but Idk the commands.
[AT&T Samsung Galaxy S 4 Original Android Developme] RockRatt:
Yes it is because your on 4.3. This ONLY works with the MDB and MDL bootloaders to bypass the locked bootloader. It does NOT work for MF3 4.2.2 or any of the 4.3 firmwares.

Right now the ONLY thing you can do with the MK2 4.3 is read up about using other methods for root. But you will not have any custom recovery for flashing anything.

Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337

---------- Post added at 11:06 AM ---------- Previous post was at 11:01 AM ----------

Are you on MF3 4.2.2 ? If so see the other post I referred to

Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
[AT&T Samsung Galaxy S 4 Original Android Developme] nomoiphone:
Thanks for the reply...I'll just see how things play out.
[AT&T Samsung Galaxy S 4 Original Android Developme] Braxton355:
So is there no way to get custom toms right now?
[AT&T Samsung Galaxy S 4 Original Android Developme] RockRatt:
Not on the newest 4.3 firmware.

If you have MF3 then YES, just use safestrap and check out the Roms that are known to work.

(I am NOT on mf3 or the newer bootloaders as I have kept my MDB bootloaders and was able to use motochopper when I first bought the phone. So just keep an eye in the general and q&a threads to see if/when a custom recovery is available.

Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
[AT&T Samsung Galaxy S 4 Original Android Developme] ryanperez:
Why do i get error on installing su binary. The error is: There was an error installing Superuser. Please send a log of the error to the developer. My phone is:

Samsung Galaxy Fame

Android Version: 4.1.2

Latest firmware.

stock rom
[AT&T Samsung Galaxy S 4 Original Android Developme] joogle:
Hi - so I got a brand new AT&T S4 and just did the unlock method on the XDA forums. I need to use this on T-mobile and was going to the AWS band method but had a few questions.

1) The version number shows this

4.2.2

I337UCUAMDL

I believe this can be rooted. What is the easiest method to root, is it the the steps mentioned in this thread?

2) Should I root first and then do the AWS band unlock?

3) Can someone advise of a t-mobile stock type rom that has wifi calling as well.

If someone could provide me the order of the steps I should perform in regards to AWS/root/rom I would appreciate it.

Thanks!
[AT&T Samsung Galaxy S 4 Original Android Developme] joogle:
I need some desperate help, after performing a successful root, I am no longer getting like data signal. I am using it on t-mobile, and I see the bars but no connection, it even tells me when i try to access anything that there is network issue.

i am not sure what to do here, I even did the AWS band unlock and still have the same issue.

apparently after the root is when this problem started.

---------- Post added at 09:45 AM ---------- Previous post was at 09:42 AM ----------

nevermind i guess it took some time is working now.

my data had stopped working after the root.
[AT&T Samsung Galaxy S 4 Original Android Developme] RockRatt:
Also check your APN settings and make sure they are the correct one for tmobile

Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
[AT&T Samsung Galaxy S 4 Original Android Developme] jjwatmyself:
MDL permits the hack to load a custom recovery. I would jump straight to the very nice one click CASUAL for windows (Requires Java). Then you can install any ROM including KitKat. Don't take am OTA update as once you move off MDL this option is gone.

http://www.xda-developers.com/android/casual-root-recovery-for-the-att-samsung-galaxy-s-4/
[AT&T Samsung Galaxy S 4 Original Android Developme] datura77:
N/a
[AT&T Samsung Galaxy S 4 Original Android Developme] alfa156v:
Hello Dan,

I have Motorola XT621 Primus, after some playings with it and trying to root and add RTL patching i got a brick.

Now the status is that i have fastboot mode working but bootloader is locked, no recovery working and no ADB working, no boot too.

I tryed many ways to flash or unlock bootloader but nothing works. Any commands like fstboot oem got output like (...)

Is there any way to unlock bootloader via fastboot and flash new rom or it completely bricked?

Thanks!
[AT&T Samsung Galaxy S 4 Original Android Developme] mintdub:
This is Incredible! thankyou
[AT&T Samsung Galaxy S 4 Original Android Developme] Captain Zero:
Why is ESET blocking the motochopper site?
[AT&T Samsung Galaxy S 4 Original Android Developme] Bud Wilkinson:
[Error] The Superuser binary (su) must be updated,

So I followed the OP to the letter on 2-1-14

When I try to open Super user I get the error message "The Superuser binary (su) must be updated" Choices are "Cancel-Recovery Install-Install" No matter which option I choose I get the message "There was an error installing Superuser. Please send a log of the error to the developer."

Went to Play Store and updated Superuser from ClockworkMod.Same errors.and no root access is available to apps requiring it.

Reran the run.bat and now Superuser update is not available on Play Store. Same result.

Samsung Galaxy S4 SGH-i337. AT&T

Android Version = 4.2.2

Baseband version = I337UCUAMF3

Kernel version = 3.4.0-812098, se.infra@SEP-103 #1, Wed Jun 5 15:49:36 KST 2013

Build number = JDQ39.I337UCUAMF3

Any help would be appreciated.

TIA
[AT&T Samsung Galaxy S 4 Original Android Developme] DeadlySin9:
This method doesn't work on MF3. You'll have to find the MF3 root method from jortex in the general section, or find the link to it in the big stickied guide post.
[AT&T Samsung Galaxy S 4 Original Android Developme] Bud Wilkinson:
[Solved] Root I337UCUAMF3

Copy That DeadlySin9.

A search here only got me to this thread so I had to search Google with Root I337UCUAMF3, I did find it here,

http://xdaforums.com/showthread.php?t=2387577

and it worked like a charm from an extSdCard and Terminal Emulator.

Thanks
[AT&T Samsung Galaxy S 4 Original Android Developme] K-alz:
Hi all. I am not an S4 owner, but my wife is. She has been asking me "can you make my phone look like yours?". Now I'm working on rooting it and flash a custom ROM on it, but honestly I don't know anything about the S4. I need some help, please.

1: is the bootloader locked like the note 3?

2: does this method still work on the s4? Her phone was on the 4.3 with all that KNOX crap right out of the box. Or should I do the Kingo method (if it does work on the s4).

If you guys need any further info about the phone just quote me.

Thank you all very much in advance.
[AT&T Samsung Galaxy S 4 Original Android Developme] Bud Wilkinson:
K-Alzwayed,

read this and see if it applies this for the SGS4 i337 for AT&T with 4.3. Worked great for 4.2.2.

http://xdaforums.com/show....php?t=2387577
[AT&T Samsung Galaxy S 4 Original Android Developme] K-alz:
Non of the methods indicate that I'd be able to install a custom recovery. Is there any recovery? Or is it something like safe strap that we have on the note 3 side?
[AT&T Samsung Galaxy S 4 Original Android Developme] cadj:
Hello, not working i dont know why.

I install sumsung drivers and working on windows 8
[AT&T Samsung Galaxy S 4 Original Android Developme] DeadlySin9:
What firmware version are you running on the phone? Go to Settings> About Device and find the build number

Sent from Black<3's I337 running Foxhound ROM
[AT&T Samsung Galaxy S 4 Original Android Developme] cadj:
android 4.3

kernel 3.4.0-2082040
[AT&T Samsung Galaxy S 4 Original Android Developme] sanriver12:
my phone I337MUMUEMK6 blocked the exploit, denied access. do i have to disable a particular security setting? im on 4.3
[AT&T Samsung Galaxy S 4 Original Android Developme] DeadlySin9:
You need to use either Saferoot or Kingo. Check the All Things MK2 thread in the General Section.

This doesn't work on 4.3, I believe you need CF Auto Root.
[AT&T Samsung Galaxy S 4 Original Android Developme] Ghost Protocol:
Hello, I have a question that I have not been able to find on this forum.

Can I use this for the Samsung Galaxy S3 on the Metro PCS service?

Some Info for the device:

* Device name: SCH-R530M

* Model number: SCH-R530M

* Android version: 4.3

* Baseband version: R530MVQUBNA1

* Build number: BNA1 (Last Four)
[AT&T Samsung Galaxy S 4 Original Android Developme] Dhs92:
Anyone tried this with 4.4.2 on the GS4 I337?
[AT&T Samsung Galaxy S 4 Original Android Developme] Dhs92:
Fails
[AT&T Samsung Galaxy S 4 Original Android Developme] twistmycap:
Dose anyone know a root method outside of This method for Mac? this method wont work i guess because of Samsung Knox.. Or if there is a way to disable knox without being rooted would be awesome..... Someone please help me with this
[AT&T Samsung Galaxy S 4 Original Android Developme] Dhs92:
Have you tried SafeRoot?
[AT&T Samsung Galaxy S 4 Original Android Developme] haoyangw:
Hello, I have a question that I have not been able to find on this forum.

Can I use this for the Samsung Galaxy S4 GT-19505 with Android 4.3 on the Singtel service?
[AT&T Samsung Galaxy S 4 Original Android Developme] iheartsamsung:
Failed

Windows 7 with current drivers. daemon started then everything moves quick and says failed. I never got a pop up for ADB connection. What am I doing wrong?
[AT&T Samsung Galaxy S 4 Original Android Developme] RockRatt:
What firmware do you have on your phone? MDL or MDB? Or MF3 or newer?

Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
[AT&T Samsung Galaxy S 4 Original Android Developme] iheartsamsung:
Failed

ucufnb1
[AT&T Samsung Galaxy S 4 Original Android Developme] RockRatt:
Sorry this will not work for you then. It ONLY works on the first two firmwares, the phone came with MDB and also works on MDL. ANY firmware beyond those they (Samsung/ATT) fixed the bypass that was being used with this method.

Your only option is to wait for a new version of safestrap if one is made for this firmware.

Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
[AT&T Samsung Galaxy S 4 Original Android Developme] iheartsamsung:
Failed

Thank you for the info. Starting to wish I suck with my s3. I really miss the PAC ROM :(
[AT&T Samsung Galaxy S 4 Original Android Developme] dc41:
Upgrade to 4.4.2?

I have a GS4 with 4.2.2 that I rooted using the method described in this thread. It has work perfectly with the exception of firmware upgrades. I'm unable to upgrade it to 4.4.2. The "software upgrade" function on the phone does not do anything. Keis tells me I have the latest firmware installed.

I'm planning on selling the phone so I don't care if root is retained after the upgrade. Am I missing something basic? Any help would be appreciated.

Thanks!
[AT&T Samsung Galaxy S 4 Original Android Developme] RockRatt:
Since you were able to use this you must still have MDL or MDB bootloader. The easiest for you would be to flash the Odin MDL or MDB firmware complete package. This will put it back to pure stock. Just check to make sure which bootloader you have first and then flash the Odin package that is the same.

This way it is PURE stock but you could also sell it for a tiny bit more to someone that would want an exploitable firmware. Sell it on swappa labeling at the MDL or MDB firmware.

Or just wipe all your data and accounts off of it and sell it on swappa as already rooted MDL/MDB loki'd phone.

Kids will not work because you have a extra recovery on the phone (TWRP or CWM). so that is why you would need the Odin package if you go that route.

Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
[AT&T Samsung Galaxy S 4 Original Android Developme] JT1510365:
can't root my device

Hey i have the samsung usb drivers from my tab 3 installed and they seem to work with the s4. I try to run the setup and it is stuck at the waiting for device stage. Do i need to install adb drivers as well? Someone please help all i want to do is get my device rooted and get a recovery installed. All of this is seeming very difficult!

Also I am on the latest kitkat firmware on the SGH-I337 model!

Thanks if you can help me!
[AT&T Samsung Galaxy S 4 Original Android Developme] DeadlySin9:
This doesn't work for Kitkat. Read in the general section, the All Things MK2 and NB1 thread can help.
[AT&T Samsung Galaxy S 4 Original Android Developme] Holmes.Sherlock:
Can usage of Motochopper brick my phone?
[AT&T Samsung Galaxy S 4 Original Android Developme] DeadlySin9:
Not unless you're above the MDL firmware, but even them it shouldn't (since the root won't work in the first place it can't flash recovery and soft brick).

Sent from my SGH-I337 running Blackbox 3.0
[AT&T Samsung Galaxy S 4 Original Android Developme] Holmes.Sherlock:
What is MDL firmware?

Also, does Motochopper unlock the bootloader?
[AT&T Samsung Galaxy S 4 Original Android Developme] RockRatt:
MDL is the first firmware update 4.2.2 that came out just after the phone was released. MDB was the original firmware the phone came with.

Those two firmwares were able to use MotoChopper to "BYPASS" the locked bootloader and allow us to run actual recoveries like CWM or TWRP.

With the second firmware update MF3 Android 4.3 the firmware was patched so Motochopper would not work any longer. That has stayed true for any further firmwares that have come out for the phone.

So if your phone does NOT have firmware version that ends in MDB or MDL then you CANNOT use this bypass as it won't work.

Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
[AT&T Samsung Galaxy S 4 Original Android Developme] FezK:
Android 4.4.2 on AT&T SGH-i337

I searched this thread and much of XDA and it looks like there's no way to use Motochopper on AT&T SGH-i337 with Android 4.4.2

Is that correct? Has anyone tried it?

Fezk
[AT&T Samsung Galaxy S 4 Original Android Developme] RockRatt:
Nope. Won't work. ATT/Samsung patched the exploit in the MF3 Firmware and Newer firmware versions. Only worked on MDB and MDL firmwares.