yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] RonH54:
Well I think I got it straighten out. I uninstalled Drivers and rebooted PC. Device Manager now Shows S4 in Portable Device area and also a Samsung Mobile Composite device listed under Universal Bus Controllers. I now start CAUSAL and I get the "Green Device Detected" so I guess I can now "DO IT"

---------- Post added at 01:17 PM ---------- Previous post was at 12:30 PM ----------

Guess it did not work. Here what Causal shows:

[*] 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.

adb server is out of date. killing...

ADB server didn't ACK

* failed to start daemon *

error:

[*] Device found.

[*] Pushing exploit...

adb server is out of date. killing...

ADB server didn't ACK

* failed to start daemon *

error:

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

* daemon started successfully *

error: device offline

[*] Pushing root tools...

adb server is out of date. killing...

* daemon started successfully *

error: device offline

Disconnect and reconnect your device. Check the device for instructions.

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

* daemon started successfully *

2936 KB/s (1578585 bytes in 0.525s)

[*] Pushing recovery to device...

protocol failure

[*] Rooting phone...

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

* daemon started successfully *

/system/bin/sh: /data/local/tmp/pwn: not found

installing superuser to system partition

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

ADB server didn't ACK

* failed to start daemon *

error: cannot connect to daemon

error: device offline

This is not for your device, halting.

done

Script Complete

Any ideas? I had used abd years ago to push some things on my GalaxyS. I do have an ASUS Prime that I connect now and then to this computer but I don't see that being a conflict since Device Manger showing I have Samsung device. When I do plug into USB port my Computer reads the phone twice it seems. I get pop up screen 2 times showing I337 then Pop up 2 times for Auto Play the phone files.
[AT&T Samsung Galaxy S 4 Android Development] RonH54:
Another update: I have a 2nd Windows 7 computer in my bedroom that has never had any shape or form of Android device plugged to it. So I plug my phone in and Windows find Phone and shows i337. But in "Other Devices" in Device Manager it has 2 listings with Yellow Mark : CDC Serial and Samsung_Android. I try to update drivers using Windows internet search but it can't find anything. Where can I find these Drivers?
[AT&T Samsung Galaxy S 4 Android Development] RonH54:
Not sure exactly what I did...LOL but finally got CAUSAL to Install Recovery and Root on my S4 using my Bedroom Computer. The problem I had on Main Computer must have been due to some Universal Drivers I installed when I was Flashing Recovery and ROMs to my ASUS Prime.
[AT&T Samsung Galaxy S 4 Android Development] maldinimi:
Amin!
[AT&T Samsung Galaxy S 4 Android Development] sw1173:
Will this work with Note 2 Sgh-i317

Would like to use this on my Note 2 since I used it on my S4 and it worked without any issues. If not is there one coming for the Note 2?

Thanks
[AT&T Samsung Galaxy S 4 Android Development] force70:
Going to find out shortly if this works on i337m models :D.
[AT&T Samsung Galaxy S 4 Android Development] Mike3.14159:
Can't get this to work....

Have usb debugging enabled, says that it is connected in CASUAL, on java version 7 update 25

This is what I get when I run it:

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

[DEBUG]sending

[ERROR][CRITICAL]Cannot run program "C:\Users\temp\AppData\Local\Temp\tempTEMPCASUALF2524334\adb.exe": CreateProcess error=5, Access is denied

Cannot run program "C:\Users\temp\AppData\Local\Temp\tempTEMPCASUALF2524334\adb.exe": CreateProcess error=5, Access is denied

java.io.IOException: Cannot run program "C:\Users\temp\AppData\Local\Temp\tempTEMPCASUALF2524334\adb.exe": CreateProcess error=5, Access is denied

...........

Update:

Dual booting Ubuntu, so tried it there and it ran fine the first time!!
[AT&T Samsung Galaxy S 4 Android Development] skizzz:
Question,

Just got my S4, and what build is the recommended one to run.

The one link on original post as May 27 or the latest nightly build?

And what is the difference between instaBuild and nightly?

Thanks
[AT&T Samsung Galaxy S 4 Android Development] :
run the latest nightly and read OP carefully to make sure it all applies to you. once rooted to an immediate nandroid

on instabuilds, i think they are for one time issues or for a particular member. kinda forget--:(
[AT&T Samsung Galaxy S 4 Android Development] AdamOutler:
Nightlies are built every night and instabuilds are built on command. If there was an instabuild, its usually because we fixed something and wanted a newer build.
[AT&T Samsung Galaxy S 4 Android Development] :
Appreciate that Adam. I remember it being talked about. But, forgot :)

Sent From My 32gb Samsung Galaxy S4 Running Tapatalk 4 Beta
[AT&T Samsung Galaxy S 4 Android Development] Mike3.14159:
Does this run a script to freeze system updates??? Saw that the new update for the Verizon version breaks root and replaces the bootloader. The girlfriend just let me mess with her s4 and gonna go pick it up from her work and do whatever I have to to not lose the ability to play with it if it dies the same on the ATT version!
[AT&T Samsung Galaxy S 4 Android Development] AdamOutler:
unfortunately not. I never got around to that. I've been busy, if someone wants to submit a patch, the code is here: https://code.google.com/p/android-c...re/src/SCRIPTS/GS4 Root and Loki Recovery.scr

line 38 would be an excellent place to insert $ADB shell 'su -c "rm whateverFiles.apk"'

I'm just running low on time between work, videos, other work and my job. I do reveiw submitted Pastebins and fix problems as I find them in the nightlies though.
[AT&T Samsung Galaxy S 4 Android Development] Poke01:
Thanks Adam

Great work Adam. Works as expected with no issues. Also thanks to the other developers involved. :victory:
[AT&T Samsung Galaxy S 4 Android Development] Mike3.14159:
Thanks for the quick reply! Wish my coding skills were better so I could help out!
[AT&T Samsung Galaxy S 4 Android Development] Faultyy:
So I can run this tool as long as drivers are installed and Java is installed then I can flash a touchwiz based rom? Is that correct?
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
Looks like you took an update today? You're on MF3 build which is now unrootable at this time

---------- Post added at 08:05 PM ---------- Previous post was at 08:04 PM ----------

As long ad you are not on the latest MF3 update
[AT&T Samsung Galaxy S 4 Android Development] Faultyy:
How can I check? I want to flash this rom http://xdaforums.com/showthread.php?t=2317772 after rooting+recovery. Thanks for your help
[AT&T Samsung Galaxy S 4 Android Development] ^tyrant^:
I used the motochopper to root my phone already but i want to get the recovery image flashed as well,, could i just run this on my phone to get the recovery added to it?
[AT&T Samsung Galaxy S 4 Android Development] the_KEV:
Is there going to be an update to this for the firmware update
[AT&T Samsung Galaxy S 4 Android Development] fukenbiker:
yes but not if

It's starting to look like I was lucky to notice the very first over the airwaves update from AT&T a month or so ago, and got a bee in my bonnet over it forcing it's way through after trying to decline it. I used motochopper to get root after that.

In my "about phone" my build number says JDQ39.I337UCUAMDL. I saw a report there was another update I did not have jammed into my device over the airwaves from AT&T because I have that function of my S4 frozen using Titanium Backup. Casual worked for me as delivered in the original post.

The report I see says Casual doesn't work on build number JDQ39.I337UCUAMF3 so check your "about phone".
[AT&T Samsung Galaxy S 4 Android Development] :
think you will need to install twrp thru goo manager from playstore
[AT&T Samsung Galaxy S 4 Android Development] LordGeek:
Does anything work for the JDQ39.I337UCUAMF3 build ? or do I need to ODIN back to JDQ39.I337UCUAMDL ?
[AT&T Samsung Galaxy S 4 Android Development] RTBee:
Once you upgrade to mf3 you can't go back. Odin or otherwise. You'll have to wait till more is developed or circumvented.
[AT&T Samsung Galaxy S 4 Android Development] neo_styles:
Except for the fact that good ole Mr. Crosler has a MF3 ROM that lets you retain root. You will have to flash the modem separately, but I've confirmed that it works (running it now as we speak).

---------- Post added at 07:56 PM ---------- Previous post was at 07:26 PM ----------

Just so nobody thinks I'm trolling:

Also tweaked DPI to 360. Ever since SlimBean, I've grown accustomed to it.
[AT&T Samsung Galaxy S 4 Android Development] LordGeek:
Yeah .. just found that out .. ODIN wont do it and neither will KIES Emergency Recovery .. phone will not boot now !!

Firmware upgrade encountered

an issue. Please select

recovery mode in Kies & try again.

ODIN and KIES both come back with errors and on my phone in red, it states:

START [224,1440]

SW REV. CHECK FAIL : fused : 2, Binary : 1

So .. learnt here. Samsung states that I can take my phone to Best Buy or Carrier Store and they can fix the issue right then and there on the spot. So tomorrow, will head to Best Buy and see if Samsung is correct !!
[AT&T Samsung Galaxy S 4 Android Development] RTBee:
I would be interested in knowing what or how Best Buy can 'fix it right there on the spot'. If you take it there, please post how it goes. Hopefully they'll get it right for you ;)
[AT&T Samsung Galaxy S 4 Android Development] LordGeek:
WoW .. what a day. Well, I got to Best Buy this morning at 10 am (when they open) .. found out there Samsung Expert (which is a Samsung Sales Consultant !!) doesn't come in until 12 noon. So, wondered around for 2 damn hours .. The Samsung Rep showed up finally, explained what was going on .. he basically just replicated exactly what I did last night via the guidance of Samsung about KIES and the Emergency Recovery !!! Nothing new, nothing different. Now its getting to 3 pm .. so 5 hours already .. the Samsung Rep couldn't do anything .. Best Buy couldn't do anything. Recommended I take it to a AT&T Store and see about the Warranty Exchange.

Went to local AT&T Store .. they couldn't do anything. They called there local AT&T Warranty Repair Center .. don't have the red SGS4 .. only white. AT&T Rep called Warranty Repairs, sending out replacement phone today, should have hopefully tomorrow or Thursday.

So yes .. once you have MF3 on your phone .. you CANNOT go backwards. Whats even more surprising is that Samsung's KIES software isn't even up to date for firmwares on our phones !!! They had no answer for that question when I asked them.
[AT&T Samsung Galaxy S 4 Android Development] AdamOutler:
Was this a result of CASUAL? Should I throw the kill switch?
[AT&T Samsung Galaxy S 4 Android Development] alacrify:
He either updated OTA or got an MF3 phone new - it wasn't CASUAL as far as I can tell.
[AT&T Samsung Galaxy S 4 Android Development] RTBee:
I think this was a result of trying to odin back to mdl from mf3. Afaik it shouldnt have anything to do with casual per sie.
[AT&T Samsung Galaxy S 4 Android Development] LordGeek:
Adam .. no, not at all. I did however try the latest nightly build of CASUAL to see if it would do anything for MF3 .. but it did not. So my stupidity, tried ODIN back to MDL .. did not work and what started this whole problem I got myself into. KIES, however, was trying to throw the exact same firmware on my phone from the Emergency Recovery .. KIES doesn't even have MF3 available yet !!!

I did however, later today, found up here a thread in which I thought was real interesting in regards to "Qfuse" and it also included a fix via ODIN for what I was experiencing .. I ran this fix via ODIN and poof .. my phone is now back up and running just by doing this quick 20 sec flash !!!!

The Cure for Kies Update Error Triangle Screen
[AT&T Samsung Galaxy S 4 Android Development] neo_styles:
I don't understand why people are saying they're having a problem using Odin to go back to MDL. I just performed a full factory wipe from MF3 to MDL, base included. Watching the Odin process, modem.bin is one of the last files to be pushed.
[AT&T Samsung Galaxy S 4 Android Development] :
What?

I don't think you know what you just said...

So you updated via OTA to MF3 THEN downgraded to MDL ?

lol.:confused:
[AT&T Samsung Galaxy S 4 Android Development] neo_styles:
I think you should find my post earlier in this thread where I mentioned I pushed the MF3 modem on Scott's MF3 ROM, THEN successfully did Odin back to MDL. Just a response to those who are saying there's no way you can go back from MF3 without being more specific. I think you forget how many noobs come to this thread daily. Last thing they need is misdirection.
[AT&T Samsung Galaxy S 4 Android Development] :
Yeah I get what you mean, but what people are saying is that you cannot downgrade from MF3 as in the OTA not the modem. The modem doesnt change the firmware which removes the loki exploit...

You can NOT take the MF3 OTA and then downgrade. Impossible as of now.

QFuse is blown.
[AT&T Samsung Galaxy S 4 Android Development] neo_styles:
I wholeheartedly agree.
[AT&T Samsung Galaxy S 4 Android Development] LordGeek:
And to clear things up here .. I ain't exactly someone you would class as a noob !!

Yes, there are ways around getting back to MDL .. but having to take steps in order to successfully do this can be tidiest to the simplest minds. But for an everyday joe that comes in and wants to root there phone with MF3 installed, are going to find out the hard way if they have already installed the OTA .. the fact there is NO simple way to get back to MDL or even MDB.
[AT&T Samsung Galaxy S 4 Android Development] RTBee:
So you are back in business? That's great. I'm assuming, however, that you're now on MF3?
[AT&T Samsung Galaxy S 4 Android Development] LordGeek:
That I am back in business .. I posted in this thread about "The Cure for Kies Update Error Triangle Screen" in which I included the link to the original thread .. I ran this through ODIN and was back up and running in 20 secs .. and yes, MF3 is still on my phone.
[AT&T Samsung Galaxy S 4 Android Development] IEatKittys!:
Have you got your replacement phone yet? If so did it come with MF3 installed? And if you haven't got it yet, can you let us know if it does come with it pre-installed? Im thinking about asking for a replacement just so that i can root, but i wanted to be sure before i asked for it. Thanks
[AT&T Samsung Galaxy S 4 Android Development] LordGeek:
Replacement received .. and the winner is ...... I337UCUAMDL :victory:
[AT&T Samsung Galaxy S 4 Android Development] IEatKittys!:
Sweeettt. Now i know to ask for one lol. Thanks
[AT&T Samsung Galaxy S 4 Android Development] sprhwk:
I'm up to date on my OSX 10.8.4 updates but I still can't run it, I keep getting this exception:

Exception in thread "main" java.lang.UnsupportedClassVersionError: CASUAL/CASUALApp : Unsupported major.minor version 51.0
[AT&T Samsung Galaxy S 4 Android Development] :
it would help to know things like phone version/build number/carrier etc

doesn't hurt to have that in sig--:)

are you on mf3

do you have kies installed

try another cable and/or port

or a pc if you have access to one
[AT&T Samsung Galaxy S 4 Android Development] krips2003:
As far as I know, currently there's no way to go back to MDL or MDB if people have already applied the MF3, until and unless you meant by swapping it with another one after bricking the one you have.
[AT&T Samsung Galaxy S 4 Android Development] ALBERTOSCLN:
thank you so much adamoutler:good:
[AT&T Samsung Galaxy S 4 Android Development] McAwesome:
Casual is fine on mf3 not effective but not damaging.
[AT&T Samsung Galaxy S 4 Android Development] AdamOutler:
if youd like to go further with that shell script, you could always download a new copy of casual http://goo.im/devs/AdamOutler/VZWGalaxyS4

then download the CASPAC. https://android-casual.googlecode.com/svn/trunk/CASPAC/Root-and-Recovery-ATT-TMO-GS4.zip

then execute from the command line with java -jar casual.jar --caspac Root-and-Recovery-ATT-TMO-GS4.zip
[AT&T Samsung Galaxy S 4 Android Development] BloomTwig:
I just very recently got my new canadian (Fido) sgs4 and would really like to root it. This seems awesome, but I'm a bit confused with regards to the rootable builds. I see talk about MDL and MF3, the first one being unrootable, right? My build is MDJ (last three characters, right? :o), will that be rootable, if you are unsure, will there be any risks in trying this method?

All the best,

BloomTwig
[AT&T Samsung Galaxy S 4 Android Development] STVERDI:
So you no longer have to flash Loki after everything? This automatically does it?
[AT&T Samsung Galaxy S 4 Android Development] t4duzan:
I337UCUAMF3 in the future?

For those of us that have already used the OTA to get to I337UCUAMF3, will this be rootable using Casual in the future? I've tried CF-AutoRoot and Motochopper, but with both methods I can't obtain root. Hoping this will be an option someday.
[AT&T Samsung Galaxy S 4 Android Development] fukenbiker:
telephony tyranny

Outler was grateful for Bliss' exploit, I remember at the start of all this, as there was a lot of discussion whether to allow the updates, the first one back in May was ok, but the one July 9 AT&T sent over the airwaves patches the exploit closed so you're out of luck. You can't even Odin back to MDL because it blows an "e-fuse" of some sort. You're stuck with MF3 stock and no way to root.

I was lucky to be paying attention and had the AT&T Software Update 'frozen' using Titanium Backup back in June.

I hear they're working on finding a new exploit, and I wouldn't sell these whiz kids short. I bet they actually pull it off, but I wouldn't hold my breath.

If you are considering a class action against the powers that be, who keep us from taking complete control over our handsets with their locked bootloader, I'll be all on board with you for that!
[AT&T Samsung Galaxy S 4 Android Development] kevnuke:
This is my primary concern at the moment because I dropped my phone after work yesterday. I hit the "sweet spot" on the top left corner near the headphone jack and now I have nothing but a blank screen looking back at me. The phone boots, but the screen is blank and doesn't respond to touch. I'm not even sure just replacing the screen would fix the problem.

I'm worried that the warranty replacement that's inevitably in my near future will yield a handset sporting MF3. Which I will promptly use to call AT&T and make my disgust blatantly apparent.
[AT&T Samsung Galaxy S 4 Android Development] gage0727:
adam, or some one who is a lot more skilled at this then me. can someone answer a question for me please. I rooted my s4 with casual back when this thread was started. Did nothing else but install root explore and titanium backup. then the other day i started getting sd card errors. saying sd card was removed. i removed sd card and put it back in a few times. go to storage options and i can not re-mount my sd card. I restart phone and my memory card is back, and then a little later it was gone again. i finaly odin my phone back to stock ie i took root out. for the past couple days now no issues at all with sd card again. I frozen a lot of the att stuff using titanium, but it was at least a good week since i had done that before this issue started up. any ideals would be great. I do not like this non rooted phone. lol
[AT&T Samsung Galaxy S 4 Android Development] S0AndS0:
@ AdamOutler

So the script will download bothe files now, however, after many downloads of a few of the ".jar" file versions (multipule successful downloads on a few versions) I still receve the same error... I'll be trying OpenJDK next to run it on the off chance that Java's JDK is at fault, there's also a version 8 hard-float of Java's JDK availible, so I've a few more avenues to try. On your Raspberry Pi running Casual; what version of Java, .jar file version did you use?

@ gage0727

I've had sd card issues; bellow is a link to a post I ran across dealling with many ways to fix it, and, a breef summery of what you can do without reading those 12 pages. Hope it helps.

[Q] any advice on fixing sdcard problems?

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

Mainly what I would sujest is to

-Back up all data on SD card

-In a PC; Reformat the SD card ( don't use "quick" format )

-In your device; Reformat the SD card

-Conect device to PC; copy back ups back over to SD card

-Hope that it's not a hardware problem

-- total time that it takes to do this?

-- about an hour and a half (for an 15 gig SD card) when I last had this issue

-- if its a hardware issue try looking up your device on the following sites

_ www.repairsuniverse.com

_ www.globaldirectparts.com

-- and see if there are parts and guides availible

--- if there be guides and parts; Then use ebay and the like to grab a cheep "copy" of your device and then chop shop yourself a repair ;)

I'll be working on a screen replacment for an Epic 4G (slide) and documenting the repaire as well as how I found all the info too.

Sent from either my SPH-D700 or myTouch3Gs

Debian Kit Install guide for all android devices that I'm writing:

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

Or

https://docs.google.com/document/d/1ssVeIhdBuuy8CtpBP1lWgUkG6fR6oHxP20ToYPPw6zI/edit?usp=drive_web
[AT&T Samsung Galaxy S 4 Android Development] gage0727:
thanks a bunch will check the info out thanks for posting that for me. I do not see how it is a hard ware issue. Only being that it only happens when i root it. maybe i freeze something i shouldnt, or change something i don't know yet. thanks again.
[AT&T Samsung Galaxy S 4 Android Development] ctleng76:
How to Update to MF3 After Root

Is it possible to update to MF3 after rooting with TWRP installed? I know it breaks root, and that's ok with me. However, when I let the OTA update run, it reboots into recovery (TWRP recovery) and never actually installs the update. Is there a way around this? If not, what is the best way for me to flash back to stock?

Thanks