yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] djsiva:
This work on my boss' phone which lost root/recovery with the MF1 update. Thanks!!!
[Verizon Samsung Galaxy S III] bnmohler:
Getting a phone replacement in a few days.. apparently my board went bad as a new screen was tried and still no video output. everything else was working in background.. who knows.. but with this method is it still advisable to backup the imei/EFS or is that all pretty much a not needed process these days?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
It is permanently advised to backup your IMEI on this device.
[Verizon Samsung Galaxy S III] dweezle:
Arfy,

What can I say? Your post is one of those we all dread reading. You are careful, you read through the instructions and then still get blindsided. I was about to help a friend root his phone and now, I just don't know. If I bork my phone that is one thing, but to have something go wrong on someone else's phone is another thing. Were you ever able to figure what might have contributed to your disaster? Best of luck getting unscrewed. Have you thought about using a USB jig?
[Verizon Samsung Galaxy S III] twistedillutions:
That was one of the few post i read that ppl fones have gone brick i had mf1 and used windows 8 i was conscience wen i was going tru it bt i was lucky nothing bad happen sucks to read those type of post
[Verizon Samsung Galaxy S III] dweezle:
I want to make sure that this "casual" will actually do what I hope it does. All I want to do is root, unlock and install TWRP on a stock Verizon i535 VRBMB1. Once rooted I want to freeze SDM with Titanium to stop the phone from asking to update via OTA. This will accomplish that, correct?

EDIT: It was amazing! Everything went quick and smoothly. 100% success on my buddie's VRBMB1.
[Verizon Samsung Galaxy S III] mxracer185:
Can't flash CM

I just got a new s3 and this tool worked perfectly to root etc, however when I try and install CM (I have tried 10.1.0 and 10.1.0.3) it gets stuck at the screen with the two circles spinning opposite directions and I have to Odin back to stock. Anyone else having this issue? or am I doing something wrong? Any help would be appreciated. Thanks

Edit: also I have tried flashing with both twrp and cwm

Edit 2: Tried again and it worked fine, not sure what was causing the issues but now everything works perfect!
[Verizon Samsung Galaxy S III] funkpod:
How long is it stuck there? I think that sounds like the cyanogenmod boot animation. The first time you boot up after flashing a new Rom, it usually takes longer. Maybe up to ten minutes. Did you wait that long?
[Verizon Samsung Galaxy S III] ahoslc:
Will this allow me to just root and nothing else?
[Verizon Samsung Galaxy S III] funkpod:
I don't understand your question. What is the " this" that you are referring to?
[Verizon Samsung Galaxy S III] ghostofdavid:
Quick question and I'm sorry if I missed it. I did this on a stock ICS Verizon ROM. I have several Verizon OTA updates but when I try them, they fail. Hoe do I apply them? System goes to Team Win Recovery and fairs install. Help?
[Verizon Samsung Galaxy S III] sixteen2nd:
If you successfully rooted you can use an app on your phone like Titanium Backup or AntTek App Manger to freeze the SDM application. This is the app that checks for new OTA's.
[Verizon Samsung Galaxy S III] countryfolk07:
I think what he is saying is he WANTS TO Do the OTA. After this process. You don't want to do that. You'll lose root and/or get the unauthorized software warning. Just read around the forum, do the MB1 Odin. Take the OTA to the latest. Then do this process again. That will give you the latest with root and unlocked bootloader
[Verizon Samsung Galaxy S III] bgs_piece:
It Works!

The first time I tried this, I ended up with the yellow triangle and had to odin back to MD1. I was having issues with ADB recognizing my phone but I figured out it was due to Droidexplorer running on my computer which I was unaware was running. Once I set it to manual startup rather than automatic ADB works perfectly. I got this to work by using odin to go back to MD1 and then didn't root or unlock and went straight to the MF1 OTA and then tried this again and with 15~20 seconds script had completed and now am rooted, unlocked and using CWM touch version 3.something. I'm running Windows 8 Pro 64-Bit so there aren't any issues with this for anyone wondering if it works on 8.
[Verizon Samsung Galaxy S III] ShapesBlue:
I noticed on the model number it changed it from SCH - I535 to Galaxy Nexus. How do I change it back?
[Verizon Samsung Galaxy S III] ghostofdavid:
It didn't do that to mine but it sounds like something else you did changed the build prop of the phone.

http://xdaforums.com/showthread.php?t=1948558
[Verizon Samsung Galaxy S III] ShapesBlue:
It's odd because I used this method to a T and did everything it said to do. I've rooted my two previous devices just not by this method and they worked great.
[Verizon Samsung Galaxy S III] JMooney5115:
Hi. This looks like great software. I just got an OTA notification today for an update. I'm currently running 4.1.2, and software information is attached. Well this process work for me?

--

Mooney
[Verizon Samsung Galaxy S III] what be up:
yup it should work for all versions, if I'm not mistaken.
[Verizon Samsung Galaxy S III] lt37r4:
Worked like a charm!

Thanks....Worked perfectly, no problems at all!
[Verizon Samsung Galaxy S III] kgirlx:
MB1 baseband version

Just updating my earlier post on trying this on wifeys phone. Stock MB1. Ran it 1st time, got to the end where it says installing recovery and kind of hung there for a while. It then finished, phone booted into stock recovery with red triangle dead android. i just rebooted phone checked for superuser, updated it then ran Casual again. this time it went quicker and finished and phone rebooted into twrp recovery like it should. i did a backup and then when done it asked if i wanted to fix root which i said yes. phone booted up, checked su, installed ez-recovery and titanium backup. only yhing not sure about is if bootloader is unlocked. not sure on how to check that.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
It worked if it installed TWRP. When you reboot, the Samsung logo should just flash briefly. If you still have any doubts, download EZ Unlock v1.2 then unlock the bootloader.
[Verizon Samsung Galaxy S III] haza12d:
I just flashed back to Stock 4.0.4. Will this work for me? Or do I need to upgrade to MB1/MF1 first?
[Verizon Samsung Galaxy S III] kgirlx:
mb1 Casual worked

your so right SlimSnoop, my phone is rooted and the logo does flash buy in a second. i should of known better. The only reason we need the bootloader unlocked is to install ROM's, am i correct? My wife isnt really into ROM's. it took me since this past christmas to finally get her to let me do it. it wasnt until this mf1 ota showing up on her phone did i convince her to let me do it. thanks SlimSnoop and all on here on xda.
[Verizon Samsung Galaxy S III] ShapesBlue:
You got it. Rooted/unlocked is useful for installing roms and tweaking your phone. I've personally done it to 3 of my devices with no major headaches so far
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Correct, you need an unlocked bootloader to flash roms and kernels.
[Verizon Samsung Galaxy S III] chase7545:
I tried to root my phone using this on the latest ota and it seems to work but when it reboots it goes into the android stock recovery. When the phone starts up titanium backup is telling me it can't acquire root so I guess it didn't work. Any suggestions? ran twice same result.
[Verizon Samsung Galaxy S III] ShapesBlue:
Odd because before I rooted I was also on the latest OTA and it worked the first time like a charm. So it didn't install twrp either?
[Verizon Samsung Galaxy S III] P.Mobile:
ok im trying to root my friends phone i have rooted many galaxy phone in the past but i do not understand how to use this method?? i downloaded the file then what do i do with it?? i cant open it??
[Verizon Samsung Galaxy S III] chase7545:
Just tried it a third time and this time twrp came up and i rebooted to the system applying the fix. Tried titanium and also Opened terminal emulator and typed su command and no dice.
[Verizon Samsung Galaxy S III] ghostofdavid:
Did you download Java? I missed that step, too.
[Verizon Samsung Galaxy S III] P.Mobile:
no i did not i need to download java??
[Verizon Samsung Galaxy S III] ghostofdavid:
Yes. To open up the file you just downloaded requires java. Google for the 32 of 64 bit version you need. If you're unsure, get the 32 bit.
[Verizon Samsung Galaxy S III] ShapesBlue:
Java is needed on your pc/mac fyi

Sent from my SGS3 stock rooted
[Verizon Samsung Galaxy S III] P.Mobile:
ok now everything went fine went threw the steps phone rebooted in revovery but it stock recovery.. i have tried 2 diff root methods nothing works for me... i have rooted a few s3's and i have an s4.. i dont kno what the problem is??
[Verizon Samsung Galaxy S III] ShapesBlue:
I'm not sure as I didn't write this. I was a little leary at first but it worked great. Sorry wish I could help

Sent from my SGS3 stock rooted
[Verizon Samsung Galaxy S III] kgirlx:
Read Read Read

first thing is i would read this whole thread and see the others problems and what they did. this thread isnt long yet so it can be done. its what i did.

it took me 2x for it to work. first thing make sure phone in debug mode, when phone plugged into comp make sure it is recognized by comp, first time i did it, it was stalled at installing recovery, i swiped phone and it did something with su, after a few minutes, casual did say it finished but phone booted into stock recovery. i rebooted phone, updated su, plugged phone back into comp, reran program, 2nd time it went quick and phone rebooted into twrp. success.
[Verizon Samsung Galaxy S III] sixteen2nd:
I've been reading this thread since the beginning (which I highly recommend you do if you are having problems with the Casual root) and it seems that most people that have issues end up flashing the stock rom and then re-running Casual (sometimes multiple times).
[Verizon Samsung Galaxy S III] P.Mobile:
SWEET!! this was givivng my mad problems at first just because i downl;oad the wrong java file.. lol found the rite one and im good to go now!! thanks for this!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Thank you for posting back! Hopefully this will help someone else in the future.
[Verizon Samsung Galaxy S III] ShapesBlue:
I'm still on stock. Don't really want to change (not in the mood to flash roms) but have made some edits here and there. I ran this and it worked great except it for some odd reason changed my model number to Galaxy Nexus which I ended up changing back

Sent from my SCH-I535 using Xparent ICS Tapatalk 2
[Verizon Samsung Galaxy S III] SlimSnoopOS:
You could pm Beans and inquire why this may have happened to you. He may know more about the tool as far as an issue like that.
[Verizon Samsung Galaxy S III] ShapesBlue:
Naw not really too worried about it. I changed it back myself

Sent from my SCH-I535 using Xparent ICS Tapatalk 2
[Verizon Samsung Galaxy S III] Arfyness:
Where did you go to change your model name? Was it just an item in build.prop?

---------- Post added at 03:35 PM ---------- Previous post was at 03:00 PM ----------

Prior to sending my phone away, I did some research on USB download mode jig, and from what I've read, they are not useful in the case like mine. I had a "screen won't come on" type of hard brick condition. I did order one of these though, so I can go straight to download mode, and it was only a couple bucks.

Update on JTAG repair:

I got my phone back WORKING (!!) in pretty much the same state it was JUST BEFORE running Casual on it. The only difference is that it is rooted now with SuperSU, from the first part of the Casual script.

Where I sent it was to a guy in Michigan that I found on ebay. The whole thing took 7 days (shipping was USPS Priority Mail both ways). In case he changes the listing, Here's a link to his store. Also he asks to please send him a message detailing what you did to brick your phone, and wait for his reply before you purchase the service. Make sure you read the whole listing, there are some important details in there.

Anyway, I had a fair bit of communication with him, and he's really fast to reply, and quite personable. I highly recommend this guy for service if you happen to need JTAG repair. Total cost to me was $41. Here's a breakdown: $29 for the service, and $6 + $6 for shipping. At present, the listing specifies that if he's not able to resurrect your device, you get the $29 back in a refund.

So, everything turned out well, I'm rooted now, and I'm NOT going to be attempting any sort of unlocking or custom recovery.
[Verizon Samsung Galaxy S III] sipock97:
But you are so close..... Don't stop now... :D
[Verizon Samsung Galaxy S III] ShapesBlue:
I edited it in build.prop by using es file explorer
[Verizon Samsung Galaxy S III] jdiamond7:
+1
[Verizon Samsung Galaxy S III] andybones:
agreed.

If he is rooted. a simple press on the unlock button in EZ-unlock .apk will unlock bootloader, and with one click in the EZ-recovery .apk custom recovery is installed, all without even turning off the phone :)
[Verizon Samsung Galaxy S III] EindhovenOne:
Hmmmmmm....

Hey, everyone. I downloaded the .jar file and have the latest Java/driver version, ran the .jar file and it found the phone and went through its processes and says exploit applied (or however it is worded). It then reboots into recovery and I reboot the system and fix root permissions and all goes well. The problem is that when I shut the phone off I cannot boot back into recovery no matter how many times I try. I hold vol-up+power+home (pressing and holding in that order) and I cannot get into recovery. Suggestions? Thank you all for your time. -E
[Verizon Samsung Galaxy S III] iwearthebelt:
You have to release only the power button once the phone vibrates. Continue holding the volume up and home buttons.
[Verizon Samsung Galaxy S III] aaCharley:
I want to just say thanks for the excellent workup on the combined root and unlock.
[Verizon Samsung Galaxy S III] Dat108Kat:
Can you please post a link to the java you downloaded? Thanks!
[Verizon Samsung Galaxy S III] keithrich1990:
Install java on your cpu file will open after that
[Verizon Samsung Galaxy S III] Lorenzo VonMatterhorn:
is it safe to say that having your phone end up in JTAG condition is not typical for most users of this tool?

as long as java is up to date, and the correct drivers are installed, i should be good to go?

it really only seems like one person managed to do that, and then 30 other people were successful, but i would still like to make sure . thanks guys. :cowboy:
[Verizon Samsung Galaxy S III] Dillon610:
Error with tool

I'm getting an error trying to start this. I got it to open the first time, but it then randomly crashed before I could use it. Now, whenever I try to double click the file or run it with PowerShell, I get an error. You can only hear half of the "casual" before it cuts off now. I have my device plugged in with USB debugging on. I have the latest versions of Java. I rebooted my computer and I re-downloaded the tool, but I still get the same errors.

Here's what happens when I run the java tool in PowerShell:

[INFO]We are running Windows 7
Creating Temp Folder in:C:\Users\DRDINO~1\AppData\Local\Temp\Dr DinosaurTEMPCASUALC5675D1D\CASUAL Cross-platform Android
Scripting and Unified Auxiliary Loader
Revision:630 build:4,788
CASUAL Copyright (C) 2013 Adam Outler
This program comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it, under certain conditions; run
'C:\Users\Dr%20Dinosaur\Documents\Galaxy%20S3%20Tools\D2VZW-CASUAL-R634bBeansTown106.jar --license'
for details. http://android-casual.googlecode.com for source.
[DEBUG]Found Windows Computer
[DEBUG]Picking Jar File:/C:/Users/Dr%20Dinosaur/Documents/Galaxy%20S3%20Tools/D2VZW-CASUAL-R634bBeansTown106.jar
[DEBUG]Attempting to write C:\Users\DRDINO~1\AppData\Local\Temp\Dr DinosaurTEMPCASUALC5675D1D\Elevate.exe
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\DRDINO~1\AppData\Local\Temp\Dr DinosaurTEMPCASUALC5675D1D\adb.exe
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\DRDINO~1\AppData\Local\Temp\Dr DinosaurTEMPCASUALC5675D1D\AdbWinApi.dll
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\DRDINO~1\AppData\Local\Temp\Dr DinosaurTEMPCASUALC5675D1D\AdbWinUsbApi.dll
[DEBUG]File verified.
[DEBUG]Found 1 CASUAL scripts
[DEBUG]Found script: d2vzw toolkit
[DEBUG]Created zipResource at /SCRIPTS/d2vzw toolkit.zip
[DEBUG]Exiting comboBoxUpdate()
[DEBUG]attempted to lock controls but controls are not availble yet
[DEBUG]Extracting archive....
[DEBUG]Target Script Is resource
[VERBOSE]Unzipping busybox
[VERBOSE]Unzipping pwn
[VERBOSE]Unzipping Superuser.apk
[VERBOSE]Unzipping su
[VERBOSE]Unzipping recovery.img
[VERBOSE]Unzipping aboot.mbn
[VERBOSE]Unzip Complete
[DEBUG]Setting executable C:\Users\DRDINO~1\AppData\Local\Temp\Dr DinosaurTEMPCASUALC5675D1D\adb.exe. Result=true
[DEBUG]
###executing: C:\Users\DRDINO~1\AppData\Local\Temp\Dr DinosaurTEMPCASUALC5675D1D\adb.exe###
[DEBUG]Executing timeoutShellCommand
[DEBUG]The current time is: 1373438388741
[DEBUG]The thread will end at: 1373438391739
[Verizon Samsung Galaxy S III] sheanzyy:
I have been rooted for awhile, but this is still amazing. Mad props!
[Verizon Samsung Galaxy S III] Lorenzo VonMatterhorn:
to answer my own question, as long as you have an up to date java runtime , you toggle USB debugging on your phone and let it install its own drivers (which there are a few) , everything went perfectly smooth. took about 45 seconds. thanks for the help, self.

thank you for this incredibly useful tool. :cowboy:
[Verizon Samsung Galaxy S III] sixteen2nd:
I, for one, didn't reply to your original request because I was one of many that wasn't so lucky (at least not the first time around). I would safely say that there are many variables involved (many unknown) that can cause this process to fail even with up-to-date java runtime, usb debugging enabled and the proper drivers installed. I would just warn people to be prepared to do some troubleshooting before they start this process incase it does go belly up.

That isn't to say I'm not very, very happy the developers released this! Thank you again!
[Verizon Samsung Galaxy S III] tdawg0213:
I for one was very skeptically about a "one-click" but given beans rep, went ahead and tried this on my wifes phone. My device was already rooted the old school way and that's how I am, old school. First try, it got stuck on flashing recovery. "OH S***", I screwed my wifes phone!!! Of course I knew I didn't because even after unplugging it I was still able to use it and it is rooted. I rebooted into stock recovery and wiped in hopes it would fix, no dice. Finally I said screw it and ran it again, maybe 30 seconds later, SCORE!!!! Thanks for this beans and all the other devs involved, keep up the good work.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Any idea what may have caused you issues the first time?
[Verizon Samsung Galaxy S III] tdawg0213:
Not at all. I'm running w7 32, updated jre, and all the drivers up to date. Like I said before, the only problem I had was getting recovery installed. Before I used goo. im to install recovery I tried TE and typed it to the T, and fail. I noticed that before I successfully installed recovery I couldn't eject mine or my wife's device. I think after running the script it screwed with my reg or device manager.
[Verizon Samsung Galaxy S III] SilverFox66:
Bought new Verizon GSIII yesterday (VRBMF1). Downloaded this .jar to root and unlock. Installed the latest and greatest Samsung USB drivers and set phone to debug. Plugged the phone in, WIndows 7(64Bit) said the device was ready. an the jar file by "open with" and choosing java. Then:

"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...

* daemon started successfully *"

then it hangs there (waited 10min) with nothing else and progress bar @ about 33%. Any ideas?

Edit: Duh... forgot how HTC's Sync Manager likes to take control of everything, and has its own adb.exe

Deleted the HTC version of the file, everything went through smooth as silk!!!!

New Question: Was there supposed to be a "reboot to recovery" option now when power button is pushed? Or do you have to go to TWRP manually?
[Verizon Samsung Galaxy S III] what be up:
Reboot to recovery option is part of the ROM your are running (so yes you have to manually do it or download a tw ROM with that option)
[Verizon Samsung Galaxy S III] willit1016:
Great worked flawlessly. I recommend uninstalling your installing or updating Java to the latest version. I did this on Win7 & MF1:good:
[Verizon Samsung Galaxy S III] Chadashcroft22:
Awesome tool quick and easy! One question I have is in twrp i made a backup of my stock rom on the internal storage. When I got to flash a new rom you have to wipe data and caches and such. Will this erase my backup of my main rom when I do this?

Thanks
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Nope, only time your internal sd is wiped completely is if you perform an internal wipe. TWRP warns you before you swipe that it will wipe the internal storage.
[Verizon Samsung Galaxy S III] zcar.300:
When I try to use this it says it doesn't detect the phone. And if I start the app anyway it hangs at "Waiting for ADB device connection." I didn't have Kies installed on my PC at first but I've sense installed it trying to get this to work. I have used Odin the flash my phone so I thought I had all the necessary drivers. If I try to reinstall the Samsung drivers it says the drivers are already installed. If I tell it to install anyway it fails.

I'm at a loss.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Have you used adb for any other OEM device before (maybe with HTC Sync) cuz that interfered with this app for a previous user. If so, uninstall those drivers. You could uninstall the Samsung drivers, reboot, then plug your device while its in Download mode to force it to install drivers again, and finally running Casual again. Just to clarify, Casual does open for you but it's the connection with your device that is lacking correct?
[Verizon Samsung Galaxy S III] zcar.300:
I probably used it for my old original moto droid way back when I had it. Casual does run correctly. I've uninstalled the drivers for this phone and rebooted and tried letting it reinstall with the phone in download mode. It fails to install properly. I downloaded the adt bundle and installed the adroid sdk build tools.still doesn't install the drivers. The drivers that wont install only show up when it is in debugging mode.
[LG Optimus 2x] hanut1:
I have a class 4, 32 gb Sd card. And I am on Django Manouche Rom V30b. Internal storage's media scanning is pretty fast but it takes around half an hour (sometimes even more) to scan my external sd for media files. Same sdcard gets scanned quickly in other phones. Any advices?
[LG Optimus 2x] bitdomo:
Download rescan media root from playstore then disable media scanning. Restart your phone to make it sure media scanning is turned off
[Galaxy Note II Q&A, Help & Troubleshooting] viniciusrsouza:
Before moving between AOSP ROMs or making a clean install I always go back to the Brazilian stock Samsung ROM and root my device again, both using Odin PC and I do a full wipe, so that after all of this I flash the AOSP ROM using Recovery Mode. Is this all unnecessary? Am I losing my time?

For example, moving from Paranoid to Carbon, or even to move from a nightly to a stable Carbon, there will be no problem if I just make a full wipe using Philz Touch?

Just to explain... as a former Note I (N7000) user, I remember it was necessary to do all of this, but I think it was because the chance of a brick...
[Galaxy Note II Q&A, Help & Troubleshooting] Spitwista:
Every rom OP gives us a full installation guide on his/her thread.

Follow them step by step and happy flashing