yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
I don't know what the problem is, but if it were me, I'd Odin to mdl firmware and then try it. The OP didn't state you need to be on mdl but I'm guessing that's the issue as many roms do require it.
[AT&T Samsung Galaxy S 4 Android Development] sharpknight:
ok? My big question is do i run any rsik at all of locking the bootloader? MDL will NOT lock my bootloader correct? MF3 WILL lock my bootloader?

I restored my phone back to stock (the build i have now) using Adam Outlers post because i needed stock to do the AWS mod. Can you please send me a link to the MDL? How do i flash MDL with ODIN? I assume i would do it the same way as i did here: http://xdaforums.com/showthread.php?t=2261573 correct? Thanks for your help so far.
[AT&T Samsung Galaxy S 4 Android Development] Demented22:
Which do u have now mdl or mf3?
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
It's the exact same way except you flash the mdl firmware. You can get it at sammobile.com. You have to register but it's free. You'll download a zip. Use 7-zip to extract the .tar.md5 file. Use that in Odin.

Edit, mdl is just like mdb, you can root and flash roms. It's not like mf3. Just make sure you don't let it "upgrade" to mf3. Root it and flash a custom recovery and rom asap
[AT&T Samsung Galaxy S 4 Android Development] duckredbeard:
edited to delete post
[AT&T Samsung Galaxy S 4 Android Development] KingKash420:
Am I missing where to find the instruction on where to actually run this on mac?
[AT&T Samsung Galaxy S 4 Android Development] :
There are no specific instructions for Mac. Just have latest Java. Op says Mac is the easiest to run on--

I watched video and just ran the exploit--
[AT&T Samsung Galaxy S 4 Android Development] Bradl79:
Yeah he should have aleast put that u cannot use on mf3
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
Mf3 didn't exist when he wrote it.
[AT&T Samsung Galaxy S 4 Android Development] Bradl79:
Yeah I know but u can update posts
[AT&T Samsung Galaxy S 4 Android Development] Venom0642:
If you go back to first post he actually did update it look at the very top says this: Update: This will not work on Build Number I337UCUAMF3
[AT&T Samsung Galaxy S 4 Android Development] Bradl79:
lol my bad i didn't even see that
[AT&T Samsung Galaxy S 4 Android Development] sharpknight:
If your computer recognized (and installs drivers) when your S4 is connected via usb (not in developer mode) but does NOT recognize your S4 when connected (with USB debugging) this is what you might need to do. It took me 2.5 hours to find this. i will be a good guy greg and post my solution. you most likely get this problem if you did the AWS mod on you S4 and changed it from MTP + ADB to something else when you were changing the modem.

Remember to have your phone set to MTP + ADB mode.

to do this:

in phone mode type *#0808#

Choose : AP on upper part and

for USB Setting, choose : MTP.

http://forums.androidcentral.com/samsung-galaxy-s4/282817-pc-cant-detect-galaxy-s4.html
[AT&T Samsung Galaxy S 4 Android Development] the_KEV:
How can I update to MF3 after doing this? I saw it somewhere here but I can't find it
[AT&T Samsung Galaxy S 4 Android Development] Bradl79:
would not recommend b/c u will loose recovery atm and leave mf3 alone not worth upgrading to, just keep on mdl or whatever ur have and if u want mf3 so bad, download a custom rom with mf3 kernel and firmware and upgrade to the mf3 baseband, u will be as close as to mf3 without loosing ur recovery
[AT&T Samsung Galaxy S 4 Android Development] the_KEV:
I never really used root+recovery other than to make a nandroid backups, and for some apps that needed root. I just happened to notice that there was a root method for mf3 and figured I can get an updated rooted phone, but if you say the update is not worth it, I'll just stick with what I have
[AT&T Samsung Galaxy S 4 Android Development] Bradl79:
yeah its really not, it was pretty much so they lock the bootloader lol, but seriously if u screw up on mf3 right now u are screwed and cannot reflash if you accidentally screw something up
[AT&T Samsung Galaxy S 4 Android Development] izgil82:
My friend bought ATT S4 with a build number JDQ39.I337UCUAMF3 and asked me to root it (because my VZW S4 is rooted). However, there's apparently a different root method for this build version since the OP says that it won't work on I337UCUAMF3. Can somebody tell me please what I need to do in order to root this phone?
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
http://xdaforums.com/showthread.php?p=42320391
[AT&T Samsung Galaxy S 4 Android Development] izgil82:
"►►at&t sgh-i337 users: Do not use this guide if you are on mf3 firmware.◄◄"
[AT&T Samsung Galaxy S 4 Android Development] Demented22:
Dont be lazy asking others to tell u what u need to do... search the forums for the right thread and read....
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
What you looking for is this : http://xdaforums.com/showthread.php?p=44165374

Remember at the moment there is no way to install custom recovery on MF3 and there is no way to unbrick or revert or fix any mess ups you do with anything. If something goes wrong you're SOL

Sent from my SAMSUNG-SGH-I337
[AT&T Samsung Galaxy S 4 Android Development] izgil82:
You're not much of a help here. Take your negativity elsewhere. Forums aren't made for that.
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
There a section in it for those on mf3
[AT&T Samsung Galaxy S 4 Android Development] izgil82:
Got it, thank you.
[AT&T Samsung Galaxy S 4 Android Development] dh4645:
subscribed.

hope to get an MDL S4 at my best buy next month during the black friday sales.

i would bet they drop below $100
[AT&T Samsung Galaxy S 4 Android Development] Demented22:
If u are waiting tell next month ur chances will be like maybe 1% on getting it on mdl, most everyone getting them now have been on mf3
[AT&T Samsung Galaxy S 4 Android Development] dh4645:
do u think i should get a different phone? i usually try not to pay more than $100 for a phone when i upgrade.

coming from the S2. my wife has had the S3 since january, so i need to get something better than hers.:)
[AT&T Samsung Galaxy S 4 Android Development] ozziedog:
I must be missing something or in wrong post I've read so many of them but I'm rooted using CM and I don't see "Custom" or the "Lock" is it in DL mode or in phone settings? If I'm in the wrong place please point me in the right direction. I've searched and can't find it.
[AT&T Samsung Galaxy S 4 Android Development] chrisj22:
This seems to be finally what I'm looking for. I'm getting a new S4 next week and just started finding out how to root it. I loved my rooted S3
[AT&T Samsung Galaxy S 4 Android Development] Demented22:
Hope its not on the latest firmwares for whichever carrier ur with
[AT&T Samsung Galaxy S 4 Android Development] Grona:
Doesn't seem to work for me. after it runs the script and reboots my phone it doesn't go to TWRP.

edit: i accidentally a work
[AT&T Samsung Galaxy S 4 Android Development] doesntmatterx:
My phone was already set to this, but still casual wont detect my device. I have tried multiple USB drivers. Can anyone help?
[AT&T Samsung Galaxy S 4 Android Development] chrisj22:
I got one with AT&T what firmware should I be cautious of?
[AT&T Samsung Galaxy S 4 Android Development] ozziedog:
Is the 20131026 Nightly for those that have not rooted?
[AT&T Samsung Galaxy S 4 Android Development] happyhd2owner:
Can't download the nightly release of Casual on ATT S4

When I click on the link it takes me to a white screen with this in dark letters and an exclamation point afterwards at the top of the screen. Welcome to nginx!
[AT&T Samsung Galaxy S 4 Android Development] ravi_mytouch:
build JSS15J.I337UCUEMJ6 and I CANNOT ROOT IT or cannot SIM unlock it through any of

Thanks very much for the tool.

I am on build JSS15J.I337UCUEMJ6 and I CANNOT ROOT IT or cannot SIM unlock it through any of the methods.

PLease help

Here are the logs

[*]

[*] Motochopper: Android root exploit (Linux/OS X version)

[*] v1.1

[*] by Dan Rosenberg (@djrbliss)

[*]

[*] Tested on the Motorola Razr HD, Razr M, Razr Maxx HD, and Atrix HD.

[*] Supports lots of other devices as well. ;)

[*]"

[*] Before continuing, ensure that USB debugging is enabled and that

[*] your phone is connected via USB.

[*]"

[*] WARNING: This will likely void the warranty on your device. I am

[*] not responsible for any damage to your phone as a result using this

[*] tool.

[*]

[*]

[*] Waiting for device...

Waiting for ADB device connection. When Windows 7 recognizes the device, we will continue. Don't touch anything.

[*] Device found.

[*] Pushing exploit...

3752 KB/s (1283460 bytes in 0.334s)

[*] Pushing root tools...

3615 KB/s (96260 bytes in 0.026s)

4166 KB/s (1578585 bytes in 0.370s)

[*] Pushing recovery to device...

4223 KB/s (10484224 bytes in 2.424s)

[*] Rooting phone...

[+] This may take a few minutes.

[-] Failure.

installing superuser to system partition

/system/bin/sh: su: not found

[*] Installing Recovery

/system/bin/sh: su: not found

[*] rebooting into recovery. Ensure that you "Install Superuser" in after you reboot into Android for security reasons!

done

Script Complete
[AT&T Samsung Galaxy S 4 Android Development] AxAtAx:
Thanks a whole bunch for this. Perfect. As always nothing but the best.

So if we are already rooted and loki'ed, should we still go ahead and run this great tool?
[AT&T Samsung Galaxy S 4 Android Development] jm1999:
Successfully rooted and installed twrp. The only thing I had to do was install KIES. Thank you!
[AT&T Samsung Galaxy S 4 Android Development] artjrv:
That would be my question as well. I am already rooted and loki'ed. Do we need to run this tool?
[AT&T Samsung Galaxy S 4 Android Development] AdamOutler:
no. why would you?
[AT&T Samsung Galaxy S 4 Android Development] AxAtAx:
I ran it just for grins...it ran, had an error when it went to push superuser..if you all ready rooted an such..really not needed I suppose. Wife will be home later...I will run this..she is not rooted yet..still stock.

If there is some benifit to it...I will odin some stock and run this....anyone have input?

Thanks

---------- Post added at 02:23 PM ---------- Previous post was at 02:21 PM ----------

Thanks..sorry..I was posting when you said this. Umm thanks for the clarification.
[AT&T Samsung Galaxy S 4 Android Development] artjrv:
When the phone reboots or just turning it back on, it says "custom" with a unlock lock icon. This normal?
[AT&T Samsung Galaxy S 4 Android Development] sloanster:
As usual... your the man!!! Many thanks, especially from the cranks... WOW, that rhymes....:cool:
[AT&T Samsung Galaxy S 4 Android Development] paleman27:
Yes is "normal". There is a thread that shows you how to remove it.

http://xdaforums.com/showthread.php?t=2257058
[AT&T Samsung Galaxy S 4 Android Development] djmouse:
one quick question,in this package is the twrp version any different the from dl and installing from goo manager? i was running version 2.5.0.2 and was having so many problems,and it was a loki rom, twrp just freezing up one of my backups was saying the size of my data was 4840790,failed backups, wouldnt even do a factory reset,it would freeze up on me ,id have to manually reboot back into twrp bad experience,never had one problem with it on my s3, i tired to read all the posts here skimmed them trying to watch 4 kids and get my phone back up sorry for the stoopid question
[AT&T Samsung Galaxy S 4 Android Development] bbgt2:
Just used this tool and have to say this has to be the easiest method ever to root your phone.

Thanks OP.
[AT&T Samsung Galaxy S 4 Android Development] rcklss1:
Already rooted and have a recovery with auto Loki but just wanted to say thanks for making something Linux users can use too :thumbup::D
[AT&T Samsung Galaxy S 4 Android Development] cj2566:
Adam, would this work for the Verizon iteration of the S4?
[AT&T Samsung Galaxy S 4 Android Development] AdamOutler:
I haven't installed a custom ROM yet, I've been focused on deploying recovery thus far. I don't have that "custom" on my phone.

Don't do that... that's silly. That will undo the work that you did.

No, It will try to root, but it won't install the kernel. I've blocked that. I can whitelist that device if you can prove it works.
[AT&T Samsung Galaxy S 4 Android Development] cj2566:
What if I'm already rooted? Would it run the recovery script?
[AT&T Samsung Galaxy S 4 Android Development] AdamOutler:
Yeah. But not on the Verizon version.
[AT&T Samsung Galaxy S 4 Android Development] MaliciousIntent69:
Im getting a multiple devices error when i start casual. the only thing plugged into USB slots on my computer are my mouse, keyboard, Wireless card and my Galaxy S4. How can I fix this?

EDIT: After some digging around my computer I found out the issue was HTC Sync running on my computer. Exitted that and the program worked just fine. Thank you!
[AT&T Samsung Galaxy S 4 Android Development] lan78691:
Both CWM OUDHS 1.0.3.4 and TWRP 2.5.0.2 are auto loki
[AT&T Samsung Galaxy S 4 Android Development] family682guy:
Just did the exploit, everything went well! Recovery seems to be VERY slow though.. Like 30 mins for a backup. And the backup is around 4gb. Other than that, ballin!
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
Unless its changed in 24 hours twrp does not auto patch after every flash like cwm. From dees_troy's mouth. Heres to hoping that changes
[AT&T Samsung Galaxy S 4 Android Development] plwalsh88:
My understanding as well. The recovery itself is Loki patched, but it doesn't auto-loki the kernel being flashed.
[AT&T Samsung Galaxy S 4 Android Development] CZ Eddie:
Wow, I finally decided to give TWRP another try. I've been a TRWP user for well over a year, dating back to my Galaxy S3. Where it did pretty well.

But this entire S4 TWRP venture has been an absolute abomination.

It's just kind of sucked with every release on the S4, save for one that actually did almost everything properly (data wipe?!).

And since then it's just gotten worse and worse.

Holy heck TWRP. Thanks for the tool, but how about getting stuff figured out so I can feel like tossing in my annual donation with a smile on my face.

Two weeks with the latest release now. Yes, it works. But barely so. The random lag is sooooo annoying. And I've had to use TWRP about 30+ times over the last couple weeks as I've been doing a lot of testing. So, I kinda know what's up.

Btw, if TWRP locks up on you when booting into TWRP or while doing a flash or a data/cache wipe, then play with either connecting or disconnecting your charge/data cable. For some reason, that fixes a lot of the TWRP hang-ups or no-boots that I've had over the last 30-60 trips into recovery.
[AT&T Samsung Galaxy S 4 Android Development] love is me:
Hi,

Any new if Casual works with 4.3 MJ9?

I know it doesn't work with MF3 but was wondering if its the same case with MJ9.

Thanks
[AT&T Samsung Galaxy S 4 Android Development] v1nsai:
Can CASUAL be used to install only root? I'm still not sure if I'm keeping this phone I'd rather not mess with the recovery. Looks pretty neat though us Linux users appreciate the cross platform support!
[AT&T Samsung Galaxy S 4 Android Development] voidlogik:
issues

I am running Ubuntu 13.10

and i have 4.2.2 OTA installed on my att s4

here is my log

[DEBUG]return from ADB:/system/bin/sh: su: not found

[DEBUG]SCRIPT COMMAND:$USERNOTIFICATION Exploit complete, Press ok to reboot.

[DEBUG]SCRIPT COMMAND:$ECHO [*] rebooting into recovery. Ensure that you "Install Superuser" in after you reboot into Android for security reasons!

[DEBUG]Received ECHO command$ECHO [*] rebooting into recovery. Ensure that you "Install Superuser" in after you reboot into Android for security reasons!

[INFO][*] rebooting into recovery. Ensure that you "Install Superuser" in after you reboot into Android for security reasons!

[DEBUG]SCRIPT COMMAND:$ADB reboot recovery

[DEBUG]sending

[DEBUG]###executing real-time command: /tmp/TempCASUALB4DD54F1/adb###

[DEBUG]return from ADB:

[INFO]done

[INFO]Script Complete

[DEBUG]State Change Detected, The new state is: 0

[DEBUG]State Disconnected commanded

[DEBUG]State Change Detected, The new state is: 1

[DEBUG]State Connected commanded

Any chance someone could help me figure out whats going on. It states the script is complete and i hit OK to reboot but it puts me in the android recovery instead of TWRP or CWM i tried both. Any assistance would be greatly appreciated.

Edit: im on firmware MF3. Found a way to install root, now i just need a recovery...
[AT&T Samsung Galaxy S 4 Android Development] ozziedog:
Have you tried Safestrap?
[AT&T Samsung Galaxy S 4 Android Development] evilpenguin123:
1337ucuemk2 root?

Does anyone know of any methods that work for firmware 1337ucuemk2? I haven't seen much of anything on a root method.

Any info is appreciated.
[AT&T Samsung Galaxy S 4 Android Development] DevilDog512:
Look for safe root method on the general section. Here.....

http://xdaforums.com/showthread.php?t=2569827
[AT&T Samsung Galaxy S 4 Android Development] datura77:
I assume the build name is the same as baseband?

My phone has Baseband - i337UCUAMDB - only 2 last digits/letters are different. Is this still supported?

Many thanks in advance!
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
It definitely should, and you should make sure to get on that in case you get attacked by surprise OTA's.
[AT&T Samsung Galaxy S 4 Android Development] datura77:
What do you mean by "get on that"?
[AT&T Samsung Galaxy S 4 Android Development] ozziedog:
Okay let me see if I can explain. If you you go into Settings and scroll all the way down to the bottom you will see About Phone have way down it will say Baseband version (mine says I337UCUAMDL) yours will either say same as mine or it will have last three letters MDB. This exploit will work on these two and NOT on MF3 or anything after that. As to the post "get on it" I think they are saying to use the OP to keep from having OTA pushed to your phone it happened to a friend if mine. He couldn't make up his mind what to do and AT&T pushed MF3 to his phone over night, but hey the choice is yours. Good luck.
[AT&T Samsung Galaxy S 4 Android Development] datura77:
Worked on MAC!!!!
[AT&T Samsung Galaxy S 4 Android Development] paleman27:
I337ucuamf3

Hey guys... I just got a new S4; the former got run over by a car. My version is I337UCUAMF3. I looked and I looked in the development forum and I couldn't find a root method for this build. Is there one? Can anyone link me in the right direction?

Thanx!
[AT&T Samsung Galaxy S 4 Android Development] :
try general or q&a
[AT&T Samsung Galaxy S 4 Android Development] paleman27:
Found it and root it! Thanx... now I need to get rid of that "custom lock"...
[AT&T Samsung Galaxy S 4 Android Development] :
:good:

the lock never bothered me :)
[AT&T Samsung Galaxy S 4 Android Development] paleman27:
I can't sleep just knowing that it's still there. .. :)
[AT&T Samsung Galaxy S 4 Android Development] :
lol

gotta have more important things in life--;)
[AT&T Samsung Galaxy S 4 Android Development] MAFU21:
I took it it off making a nandroid of my stock rom and triangle away. Try it and let me know.
[AT&T Samsung Galaxy S 4 Android Development] ducksauce88:
Weird question for the dev who wrote this....how long did it take you to write this?
[AT&T Samsung Galaxy S 4 Android Development] smokarz:
wow...i've never seen unlocking/rooting a phone this easy.

so, after i run this i can install ROM i want?
[AT&T Samsung Galaxy S 4 Android Development] smokarz:
OK

My baseband version is I337UCUEMK2.

Can I run this tool for my phone?

Thanks
[AT&T Samsung Galaxy S 4 Android Development] :
Best advice I can give you is always read OP page and last dozen or so of thread pages. Your answer is only a couple pages back. Check it out--:good:

Short answer is you can't use this. You are mk2 and newer than mf3. Starting with mf3 Sammy locked down bootloader and you need to use SafeStrap. You are limited to no custom kernels or recoveries other than SafeStrap recovery.

You will find several threads on mf3 and mk2 in General and Q&A on rooting your device and flashing roms. You will also be limited on what roms you can flash, so be careful. Read up on them extensively and back up what you can before and after you root.

Good Luck--:)
[AT&T Samsung Galaxy S 4 Android Development] hednik:
Nope.
[AT&T Samsung Galaxy S 4 Android Development] dannieloco:
Just got an S4 and luckily it had MDL.. this tool worked in 1 minute.. thank u! time to do some ROMMING!
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
[MENTION=4721003]dannieloco[/MENTION] Just curious how the heck did you end up with MDL? Where did you get it?
[AT&T Samsung Galaxy S 4 Android Development] dannieloco:
I should have clarified.. I got it from my sister.. Its used.. lol.
[AT&T Samsung Galaxy S 4 Android Development] rotaryboy:
back to stock?

Currently rooted by CASUAL and on MDL. I'm selling the S4 so if I unfreeze the OTA update & let it install will this safely remove root and get me stock? Thanks
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
The update might not go through with root. Easiest way is to use the ODIN files. Then you could probably sell it for a bit more if the buyer has interest in custom ROMs.
[AT&T Samsung Galaxy S 4 Android Development] phillytemptation:
only one other person mentioned the multiple devices issue (they had to exit htc sync program), just in case anyone else has the same problem for me it was bluestacks that was giving me the error
[AT&T Samsung Galaxy S 4 Android Development] eachitandi:
Just upgraded to the AT&T S4 yesterday. I was amazed (and thrilled) that it came with the MDL build. Took no time at all to get rooted! Thanks for the instruction!
[AT&T Samsung Galaxy S 4 Android Development] jjschafe:
I've read through most of this thread and can't seem to find an answer to the issue I'm having. My device is connected and everything runs normal. Then it says:

[*] Installing Recovery

/system/bin/sh: su: not found

[*] rebooting into recovery. Ensure that you "Install Superuser" in after you reboot into Android for security reasons!

done

Script Complete

The phone then boots into Recovery. I reboot from there, and the phone is not rooted. Can anyone help?

I don't have a high enough post count on the forum to post the link to my log. If there is some other way to submit postbin, please tell me
[AT&T Samsung Galaxy S 4 Android Development] :
what model and what build version?
[AT&T Samsung Galaxy S 4 Android Development] jjschafe:
Model

ATT I337

Build

JSS15J.I337UCUEMK2
[AT&T Samsung Galaxy S 4 Android Development] ozziedog:
I maybe wrong but I don't think this will work on MK2, you may want to do little more research before out end up with a brick. Good Luck.
[AT&T Samsung Galaxy S 4 Android Development] :
It won't work. Need to research SafeStrap for MK2 to root. There are threads on it and you will limited on flashing roms. No aosp and 4.4.
[AT&T Samsung Galaxy S 4 Android Development] jjschafe:
Gotcha... Didn't see anything about MK2 in the OP so I thought I should be good. Thanks for the help.
[AT&T Samsung Galaxy S 4 Android Development] :
Yeah this is an older thread and maybe not updated that much anymore. It mentions MF3 and should probably add MK2--:good:

Adam and Dan did great work for early builds and many of us rooted this way--:)
[AT&T Samsung Galaxy S 4 Android Development] fumes007:
Installing custom rom

If i run this "CASUAL", will it enable me to install custom roms using the custom recovery or will i have to do any other thing to install custom roms?

Basically i'm asking, Do I still have to install safestrap to install custom rom?
[AT&T Samsung Galaxy S 4 Android Development] :
You can't run this if you are mf3 and above. Research SafeStrap threads.
[AT&T Samsung Galaxy S 4 Android Development] chinesestunna:
How do we update TRWP that's installed with this method? I've been on 2.5.0.2 for the longest time and GooManager install open recovery script will complete but when I reboot into recovery it's still stuck on 2.5.0.2