yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] jmikeb92:
A friend of mine just received a used vzw S3 and attempted to root it with casual root unsuccessfully. He said it kept freezing on the 'pushing exploit' step. He is wondering if it has anything to do with his newer build number (JZ054K.I535VRBMF1). Any one have any suggestions?
[Verizon Samsung Galaxy S III] droidxxxxx:
That's what I'm on..worked fine for me. At first it didn't..then I realized usb debugging was un checked..
[Verizon Samsung Galaxy S III] jmikeb92:
I remember him saying that he specifically ticked USB debugging and still a no go. It would freeze on the pushing exploit part and then he would have to pull the plug, do a battery pull and that's it. Nothing. No root, not bricked, Nada.
[Verizon Samsung Galaxy S III] iwearthebelt:
Make sure the phone screen is unlocked, I ran into that issue once before and keeping the screen unlocked while running the exploit fixed it. Can't explain why but it worked.
[Verizon Samsung Galaxy S III] jmikeb92:
Thanks I will pass that advice along and report back with the results.
[Verizon Samsung Galaxy S III] aypeeootrek:
isnt this method supposed to unlock the bootloader as well? or is using ez recovery because he had an issue?
[Verizon Samsung Galaxy S III] annoyingduck:
For some of us the method is injecting root only...
[Verizon Samsung Galaxy S III] aypeeootrek:
ok, gotcha.

another question. just got my new phone in today and i have a mac running 10.5.8. believe its running java 6. anyone successfully use this method on this software?
[Verizon Samsung Galaxy S III] sixteen2nd:
I was running 10.6.8 and the Java version was too far out of date for this utility, so I suspect 10.5 is also. I ended up using a Windows 7 machine at work.
[Verizon Samsung Galaxy S III] aypeeootrek:
Figured that. Going to use a friends computer to root when I get a chance
[Verizon Samsung Galaxy S III] BeansTown106:
updated casual to more of a toolkit style approach instead of a 1click do all now there is a menu section to pick what you want( for some people that only want root)

if doing all three u need to root first, then flash insecure aboot, then recovery of your choice. should be very self explanatory when looking at the application
[Verizon Samsung Galaxy S III] suchavibrantthang:
tested it on a replacement running mf1. followed step by step, device never showed "connected", but ran the program anyway (root, aboot, twrp). running windows 7, updated java, and updated drivers. very happy it didn't brick.

anyone see disconnected state through the whole process?
[Verizon Samsung Galaxy S III] zsibisi:
recently picked up this phone to use for a bit and trying to use this rooting method but I think it keeps hanging on pushing exploit.

I even did a full hard/factory reset as well and didn't put anything in. Has anyone run into this issue? Also to how long does the process take as I've only waited 15min and just assumed that the program hung up on me.

Any help would be greatly appreciated.

side note: using windows 7, latest java update. and running MF1 ....

thanks,

Z.
[Verizon Samsung Galaxy S III] cstone1991:
3 things to try

1. Make sure the phone's screen is unlocked while running the program (set it a longer timeout interval if needed.

2. Make sure USB Debugging is turned on. Launch the program THEN plug the phone in.

3. Make sure you are using the OEM USB cable.

Good luck :thumbup:

*Edit* I haven't used the new version of this but with the last version it worked so fast that I didn't really think that it did anything until it rebooted into TWRP.
[Verizon Samsung Galaxy S III] junowhoo:
Is this for ics or jelly bean?
[Verizon Samsung Galaxy S III] jackrabbit72380:
I cant run this file I am on windows 8 enterprize

I have java installed latest version.

even watched the tutorial in witch he used a mac

even read the whole thread.

if I try and launch I get an error.

if I right click hit open with . I get option to open with (Keep using JavaTM Platform SE Bianery)

it wont work how can I open launch the program?

I cant believe this info is not in first post.

please can someone help?
[Verizon Samsung Galaxy S III] manbat:
Used this to "just root" my wife's new S3 today. Casual never showed as connected? I opened up a cmd windows and did command to check for connected devices. The S3 showed up in the command window as connected...but never showed up in Casual as connected. I tapped root S3 and "do it". Was succesful !! :) I was using my favorite XP computer...could that have caused the "Not connected" issue? Thanks again!!
[Verizon Samsung Galaxy S III] zsibisi:
thanks for the input.

I gave it another go and ran in to the same issue. Hanging on pushing exploit.

It was tried on another pc using windows 7, latest java (7 update 25), made sure screen stayed on.

So I tried it the longer way using Odin. I went to run the VLREC etc and it connected, turned blue ran, got pit,sending etc. and then on the screen in the corner box it said aboot.mdn or whatever that was and was hanging on that.

I had the same results above on 2 different pc's.

I attempted to just downgrade to VRMB1 not the F1 as I have and Odin failed to "write"

after all this, I just wanted to see what was what so I went to storage section when going in to computer and went in to the SD card, tried to copy files and then windows told me that file could not be copied to the card.

I swapped out to a different SD and same result.

I'm thinking something is just hinky with the phone itself or is that not something that I'm not doing right.

I would have assumed that you can just plug in the phone and keep it on MTP to transfer files but wouldn't let me.

I did try and do this all over again using the other option ( phone says its a camera) and still ran in to issue.

Any help or any advice would be greatly appreciated.

MF1 base, latest java, running windows 7, I do have drivers installed and USB debugging on.

Thanks again,

Z.
[Verizon Samsung Galaxy S III] Elihue:
This does not work for me. The script does not see my phone. The old script (Casual R630) will. Will this be fixed anytime soon?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I haven't tried the new version but for everyone having issues, could you try the initial Casual version and see how it works?
[Verizon Samsung Galaxy S III] jpierson:
Worked like a charm, followed everyone's advice, it never did see the device, but flashed it with no problems.
[Verizon Samsung Galaxy S III] dbroadus2007:
Works

I followed the instructions, and my phone is rooted with TWRP recovery on it. I have not flashed any roms yet though...:good:

---------- Post added at 11:20 PM ---------- Previous post was at 10:46 PM ----------

Still secure bootloader though...
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Having an unlocked bootloader is not reflected in Odin.
[Verizon Samsung Galaxy S III] dbroadus2007:
Yes I noticed the bootloader is still locked...How can I unlock it?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
If you followed the steps to unlock and root in Casual then you've already done so. Did you? Odin won't change either way.
[Verizon Samsung Galaxy S III] dbroadus2007:
I did follow all of the steps. I am trying to avoid making the mistake I did before. I thought the bootloader was unlocked and it wasn't. I ended up Odin back to stock.
[Verizon Samsung Galaxy S III] thirdcoastraised:
just used this method to reroot, and unlock and install CWM, all were successful, including unlocking the bootloader as i have installed and am successfully running a custom rom now.
[Verizon Samsung Galaxy S III] t1gartist:
ok got issue i rooted the device everything was good so i proceeded to flash insecure bootloader everything appeared fine reboot into download it went from samsung offical to custom so t appeared fine to i proceeded to reboot into os and flash recovery cwm touch everything appeared fine adb shell was granted su flash went fine so i reboot to recovery to make a backup and blam

SECURE FAIL: KERNEL is at the top of the screen

System software not authorized by Verzion Wireless has been found on your phone please turn off your phone and go to the nearest Verzion wireless store for help

in download mode i got

ODIN MODE

PRODUCT NAME: SCHI535

CUSTOM BINARY DOWNLOAD: YES(1 COUNTS)

CURRENT BINARY: Custom

SYSTEM STATUS: Custom

QUALCOMM SECUREBOOT: ENABLE
[Verizon Samsung Galaxy S III] dbroadus2007:
Thanks for the update. I will go ahead flash a rom. I will downlod the stock files just in case though!
[Verizon Samsung Galaxy S III] PsiPhiDan:
Worked like a charm with a brand new S3 my friend bought (MF1). It always displayed "Disconnected" as others have mentioned, but everything worked.

Interesting note: first time I tried, everything said it worked but it actually didn't. Found out my friend had no SD card when I was attempting a slower way to root/unlock, then we bought one. Tried the one-click method again for the heck of it, and it worked immediately! I don't quite know if that was a coincidence, but worth noting in case it isn't a coincidence!
[Verizon Samsung Galaxy S III] SilverFox66:
I would think it a coincidence. I had no SD card in mine when I ran casual. I didnt have one for a good while even after flashing CM either
[Verizon Samsung Galaxy S III] dbroadus2007:
Which ROM did you flash?
[Verizon Samsung Galaxy S III] PsiPhiDan:
I went with LiquidSmooth 2.9.

I showed him CleanROM 7 and LiquidSmooth. Ultimately, he preferred the ridiculous speed and customization of LiquidSmooth and AOSP in general.
[Verizon Samsung Galaxy S III] dbroadus2007:
That's the exct rom I am going to! Thanks for the recommendation :good:
[Verizon Samsung Galaxy S III] PsiPhiDan:
It's an incredible ROM. I've been on it for months. No issues at all so far for my usage.

I recommend pairing it with ktoonz kernel (kt747). You'll need the AOSP 3.4 version. Oh believe the latest is from 7/19. It comes with a sweet app called ktweaker that allows you to tweak it to your liking. You can even download settings other people determine to be awesome if you look in the Team Kernelizers thread in the general section. It really helped me get even better battery life without sacrificing performance.
[Verizon Samsung Galaxy S III] dbroadus2007:
Thanks for the info on ktoonz kernel. I'd flash that after flashing the room and gapps, plus after a reboot right? I think the last time I had liquid smooth battery life wasn't that great, but maybe that kernel will fix it!
[Verizon Samsung Galaxy S III] PsiPhiDan:
Flash ROM, flash Gapps, flash kernel, reboot.

That's what I've always done. My battery life has been on par with any other ROM. I have the ZL battery now, so I don't think this will help you, but I'm getting 10-12 hours of screen on time now.
[Verizon Samsung Galaxy S III] bluremi:
I searched through this thread and nobody answered this question:

If I just ODIN back to stock 4.0.4 ICS (because I bricked it), will this root my phone or do I need to accept an OTA update first?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Short answer: it should work on ICS. Long answer: seems like everyone is using this root tool on JB, so you can try and tell us. It should work though.
[Verizon Samsung Galaxy S III] bluremi:
Okay, I tried it and it worked. Now I'm on cleanROM 7, awesome!

Please note, I did not try to unlock the bootloader or flash a recovery since that's what bricked my phone in my previous attempt. I only rooted it and used EZ Unlock + GooManager for everything else.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Perfect! Did you report earlier in this thread about the brick incident? Out of curiosity of course.
[Verizon Samsung Galaxy S III] bluremi:
I didn't report because I didn't have enough useful information to indicate why the bootloader failed to unlock. It said it had succeeded in unlocking and installing TWRP, but it booted into default recovery instead of TWRP.

Being new to this I misdiagnosed the problem as a bad recovery, and instead of making sure the bootloader was unlocked I flashed TWRP manually and gave myself the "unauthorized software" verizon screen of death.
[Verizon Samsung Galaxy S III] zsibisi:
Ok just an update:

I re downloaded everything and still ran in to an issue.

So I went and used an aftermarket cable (not oem) that does data/charge.

And behold the flash went through fine, but I did make an error on my part.

I flashed all 3 in a row, double checked su etc and that was fine. I flashed step 2 and then 3 to unlock it all and then phone

rebooted and I was stuck on the "triangle" and please see verizon store etc.

I was glad that I d/l the MF1 firmware prior.

I used Odin and flashed back to stock firmware and then it was back to the norm.

So I thought why not one more time.

I rooted and that went well, checked su and it was good.

I flashed the second step and this time I did look at my phone and what I found out was that I didn't allow

usb adb to have root to properly unlock bootloader and then flashing the recovery right away is what gave me my error.

So I made sure I allowed adb# etc unlocked the bootloader then flashed my recovery and all was well.

I just wanted to say great work on this unlocking procedure. !!!!!!!!!!!!!

Now I'm running dirty unicorns 4.2.2 flawlessly ( chose this as it is the same on my evo3d)

I think what got me was that this process was almost too easy and it went to fast! LOL

Anyway, great work and maybe my experience can help someone else.

(side note)

When flashing this I made sure that the screen stayed on when charging option and held it to 10 min option during this process as to use some

of the advice that was posted earlier.

Thanks again!!!

Z.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Ahh, I see. The tool just did not work for you initially. Glad you resolved everything! I think you experienced what I am detailing below.

[MENTION=3544615]beanstown[/MENTION], I think I am seeing the same issue that everyone else is having with Casual r734. Using ML 10.8.4 on my MBP and the OEM usb cable, I played with r734 and r634 for about thirty minutes. R634 recognized and connected to my phone however r734 never showed as connected. I could open r634 and it would show as connected, immediately close it out, then open r734 but it would never change from "disconnected." This persisted over reboots and through my choosing MTP, PTP, and enabling/disabling USB debugging. Could you take another look into Casual r734? After this troubleshooting period, I ran r734 twice despite my device being disconnected. R734 failed to root the first time but successfully rooted the second time. Unlocking worked on the first try. Next I removed root using SuperSU then ran r634 and this rooted/unlocked just fine. I don't believe Casual r734 recognizes the device at all.
[Verizon Samsung Galaxy S III] jnehama:
Unfortunately, when I used the program to load the custom recovery on the insurance replacement I got secure Kernel fail and am stuck at go to Verizon store. Am downloading stock rom for odin and hopefully, this will work as I seem to get into bootloader, download mode without a problem. The firmware was the same as my original phone which rooted and unlocked without issue so I am not sure why this one had issues. I will update once I have corrected the problem.
[Verizon Samsung Galaxy S III] tdawg0213:
OK, I posted some issues I had using this method on my wife's phone and updated the post saying mission accomplished. But when I try to flash a custom ROM, everything goes through but I can't sync contacts. I tried flashing a different radio, Odin back to unrooted stock, and flashing a different ROM. The radio flash fails, different ROM doesn't sync, and the Odin says md5 not valid. I've checked the md5 on all files downloaded and all match. Also the sdcard is r/o now. I can't copy files to sdcard or delete files. Reason I'm posting here is because I rooted my phone old school and running smoothly but this way has borked my wife's phone. Any help would be appreciated.
[Verizon Samsung Galaxy S III] bondisback:
can i root my SCHi200 samsung galaxy stellar running android 4.1.2 with this method??
[Verizon Samsung Galaxy S III] maypo52:
question on cwm touch...

Hello All,

I just rooted my Verizon GS3 using Casual with seemingly no problems so far. I got to the point where I flashed CWM Touch and the phone rebooted into CWM as expected. I ran a backup at this point and saved it to the SD card. Now when I want to reboot the phone back to normal operation it asks the question "ROM may flash recovery on boot. Fix?" I'm not quite sure what to choose here. The choices are "No or Yes, disable recovery flash". Which do I choose? Also, When I looked for the backup files I found them in the folder clockworkmod/backup/1970-12-11.13.50.06. Is that folder name supposed to be the date and time of the b/u?

Thanks for any help.

Mark
[Verizon Samsung Galaxy S III] tdawg0213:
The op says it all..... NO!!! Please read the whole op before posting.
[Verizon Samsung Galaxy S III] cnlson:
twrp does this automatically but cwm does not and you have to select yes or you lose cwm each time you reboot.

when you phone is shut off it can lose the time at which point it goes to zero hour zero day which in the 'nix world is 12-11-1970. a point of interest, if you have a problem entry in your google calendar and your calendar will not sync it can be because the date is prior to 12-11-1970 at which point google's 'nix servers cannot deal and repeatedly regenerate the entry choking each time until your calendar is hundreds of megs at which point your phone will no longer be able to sync and will act very broken.

exporting the calendar, deleting it from google. loading it in, of all things, microsofts calendar. going back to zhzd and deleting the, by now, seemingly millions of entries, then exporting from MS cal and importing to google will cure it. for me this was caused by an app that had calendar priviledges.
[Verizon Samsung Galaxy S III] maypo52:
Thank you cnlson. I guess I will have to try flashing cwm again and choose yes to fix.
[Verizon Samsung Galaxy S III] tluley51:
i am not sure how you can screw this up, but I am seeming to be doing that...

I am not new to rooting/romming ect., but I am trying to just plug it in, enabled MTP and root it and it just hangs. The tool is showing as disconnected and it just is "[*] Waiting for device...

Waiting for ADB device connection. When your OS recognizes the device, we will continue. Don't touch anything." and it has been hanging here for about 10 minutes...

EDIT: To note, I am using the OEM cable and believe it or not, I CAN follow instructions and use the search bar...Still having issues

EDIT 2: Boy, that was nerve racking. After reinstalling the drivers 3 times, it would go through the root process but get hung up because it detected an anti virus software. Had to disable trend (stupid work computer) and continued and seems to be going along just fine.
[Verizon Samsung Galaxy S III] thefatalepic:
Is there a way to get this to work if the s3 is on 4.2.1/4.2.2?
[Verizon Samsung Galaxy S III] checkthisSH:
This method works with Android 4.1.2, right?

Just want to proceed with caution and verify before I continue.

Thanks!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
No, this is for the d2vzw/sch-i535. Nothing else.

We're officially on 4.1.2 so you're in the wrong forums.

Correct. That's our latest official Android version.
[Verizon Samsung Galaxy S III] checkthisSH:
Excellent, thanks for the quick response! And just another quick question, if you're up to answer it: I've been milling around on the CM Wiki for our device as well, as I'm looking to flash CM10, and I ran into another method to load recovery and flash the rom that requries the use of Heimdall.

I can't get Heimdall to work properly for me, so I'm looking into using this method (and honestly, this looks much better!). However, the CM Wiki describes having to load an older bootloader and flash an older kernel in order to flash the custom recovery THROUGH Heimdall, and I've noticed that the Casual method doesn't require either. Just to make sure, all I should have to do to go from stock to CM10 is run Casual to obtain root and to flash the custom recovery, then flash CM10 from said custom recovery?
[Verizon Samsung Galaxy S III] Burkejt1:
Could anyone help me out with a download for casual, every time I try to download it, it stays searching for mirrors, maybe a dropbox link or something? Thanks!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
To be honest, Heimdall has probably zero support here. Odin is by far the only program anyone provides help with and I think its cuz a majority of us use Windows. I don't know anything about Heimdall to comment but this Casual method roots, unlocks, and also flashes TWRP 2.6 if you just follow the prompts. Casual R734 is somewhat finicky if you can't tell from the previous few pages but it works so long as you see SuperSU in your app drawer after rooting it.

Downloaded just fine using Chrome in 30 seconds. Maybe try now or a different browser?
[Verizon Samsung Galaxy S III] Vfan23:
Last login: Sun Aug 11 13:06:59 on ttys000

new-imacs-imac-2:~ imac$ java -jar D2VZW-CASUAL-R734bBeansTown106.jar

Unable to access jarfile D2VZW-CASUAL-R734bBeansTown106.jar

new-imacs-imac-2:~ imac$ java -jar /Users/imac/Downloads/D2VZW-CASUAL-R734bBeansTown106.jar

Exception in thread "main" java.lang.UnsupportedClassVersionError: CASUAL/CASUALApp : Unsupported major.minor version 51.0

at java.lang.ClassLoader.defineClass1(Native Method)

at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)

at java.lang.ClassLoader.defineClass(ClassLoader.java:615)

at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)

at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)

at java.net.URLClassLoader.access$000(URLClassLoader.java:58)

at java.net.URLClassLoader$1.run(URLClassLoader.java:197)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(URLClassLoader.java:190)

at java.lang.ClassLoader.loadClass(ClassLoader.java:306)

at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)

at java.lang.ClassLoader.loadClass(ClassLoader.java:247)

new-imacs-imac-2:~ imac$

Thats the error i get when i try to run this on my Intel Mac 10.6.8 ......help please...
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Look above, might be too out of date for this. It works great on OSX 10.8 with Java 7. Have a spare Windows machine lying around?
[Verizon Samsung Galaxy S III] Vfan23:
Sure don't. I have the Droid DNA right now and just spent 3 days setting up ADB on my Mac and manually using a program called Revone to unlock and gain s-off on it. I used ADB for all the commands, didn't have to run a program. Now I'm thinking about downgrading to the S3 with some cash :) but didn't want to do it if I can't get it rooted. I'm extremely well versed in ADB but can't find a way to root it and unlock it that way. :/ But no, just have my Mac
[Verizon Samsung Galaxy S III] Sevinex:
Would you be opposed to running a virtual machine on your Mac?
[Verizon Samsung Galaxy S III] Vfan23:
I have Ubuntu set up like 95%. Enough to boot into it and surf and download stuff but I can't figure out how to install it completely. I'm basically using it live. But I can't install Windows on the BootManager because I don't have a 'legal' copy of Windows. Or any copy for that matter. I have my Hard drive partitioned, 20gb of it, for Linux and I can boot into it, but when I choose 'Install' it starts downloading all the packages and stuff and exits out but its still not 100% installed. Lol
[Verizon Samsung Galaxy S III] sixteen2nd:
I haven't done any research, just thinking out loud, but this should work on Linux so you could download a live distro with java runtime and use that couldn't you?