yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] droidstyle:
I have not tested but it should work like this

-open odin

-put the vralf2 stock.tar in the pda function

-uncheck auto reboot

-hit start wait for it to say pass/reset

-put the vralf2 stock bootloader.tar in the bootloader function

-uncheck auto reboot

-hit start, wait for pass/reset

-pull and reinsert battery

-three finger into stock recovery, wipe data/factory reset

Now I have not tried this, thats why its not in the guide yet...waiting for confirmation on it.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Thank you for that breakdown, that helps out a lot. I understand why it's not confirmed, this unlocking tool has only been out for a few hours. I may wait to root and unlock just so that I can see how to properly return back to stock locked.
[Verizon Samsung Galaxy S III] Nsx93:
ok well i just followed this. very helpful, thank you.

one thing i notice. I did section 1 and 3.

Followed section 3 to a T, chose to run Beans custom rom.

ran into a lil issue, kept getting stuck in Recovery after reboot.

i found out that you HAVE to use CWM 6.0 or above ..u CAN'T use CWM touch..

Which is where the conflict came in. This guide said to Flash CWM Touch but in Beans Custom Rom thread it said to use CWM 6.0 and up.. which work perfect..

so far so good...

thanks for an excellent guide.
[Verizon Samsung Galaxy S III] davidnc:
So if you are already rooted and on a stock rom ,if all you want to do is unlock the bootloader then in part 7 of the guide is it just a 3 step procees using Terminal Emulator and the bootloader is unlocked ? Thats it ?Thanks just wanting to make sure thats all the steps invovled in unlocking and I am understanding it correct

Edit : Nevermind I got the answer to my question ,I was correct in my thinking
[Verizon Samsung Galaxy S III] Khishawn:
Unlocking Bootloader

So I am currently rooted and running a Beans B8 as well as Lean Kernel. For unlocking my bootloader would Section 7 or Section 8 be better? Or is it just a matter of personal preference? Also, when you place the image on the sdcard, I just want to verify it would be the external SD Card (I know when going through CWM recovery you can access either).?

Last, thanks again for keeping a thread up to date with all the latest!!

:laugh:

Edit: I downloaded the Emulator and thought Id just check if it works but when I typed SU it says it cant find it.

When I start terminal it says:

export Path=/data/local/bin:$path

app_142@android:/ $ export Path=/data/local/bin:$Path

I typed in

app_142@android:/ $ -SU

It then kicks back /system/bin/sh: -SU: not found
[Verizon Samsung Galaxy S III] droidstyle:
Yea will fix that! Cwm touch worked before he added imoseyons kernel. But yea use cwm6 for everything! Thx
[Verizon Samsung Galaxy S III] droidstyle:
Make sure you didnt use capital letters.... su not SU
[Verizon Samsung Galaxy S III] th3taman:
Thanks Droidstyle, section 7 via terminal emulator...very easy. And guessing my fast boot up time is my indication it worked, lol.

Suck it VZW...I'm unlocked!!! :good::laugh:
[Verizon Samsung Galaxy S III] RoboJoe:
So, I've been patiently waiting for the developer version to be released by Samsung. Is there any reason to keep waiting? I'm paying full price, either way.
[Verizon Samsung Galaxy S III] droidstyle:
nope we are officially DIALED!
[Verizon Samsung Galaxy S III] RoboJoe:
Sweet! So, I guess I'll go get one today from a VZW store. Anyone want to buy a gently used Bionic? :P
[Verizon Samsung Galaxy S III] Khishawn:
Heh thanks! Dont know why I was using caps.

I really should buy you a beer after all the questions you've answered for me
[Verizon Samsung Galaxy S III] droidstyle:
buy adam outler and crew a beer...Im just a messenger :laugh:
[Verizon Samsung Galaxy S III] droidstyle:
ok guys, I overhauled the guide a bit...eliminated section 1: rooting with odin. I no longer see a point in doing this now we have Adam Outler's Casual program for rooting/cwm/unlocking bootloader/and more. Also noxous ninjas DebugFSroot tool! Also section 2 was updated, adding relocking the bootloader. I feel this is the proper place to put this since going back to stock is required before relocking bootloader. Also, stay tuned as I will be phasing anything kexec out of the guide. There is a non version of cm10 and a insecure Touchwiz kernel out already thats no kexec, but I will wait another day or two for all devs to make the transition,,then Ill update the guide. Thanks and stay tuned, things are moving at a rapid pace!!
[Verizon Samsung Galaxy S III] gzsmooth:
Why wont this work? I have TE installed and the aboot.img on the root of my sd card via root explorer. type the commands in TE which has SU already but I keep getting : cannot open for read: No such file or directory

Any ideas?

Edit-I fig it out
[Verizon Samsung Galaxy S III] Khishawn:
Make sure its on your internal sd card not external.
[Verizon Samsung Galaxy S III] pdinphx:
Droidstyle,

Do you have an MD5 for the aboot.img file?

Even though it is a small file, it would suck if someone followed all the directions and ended up pushing a corrupt file to their bootloader partition ...

--------------------

I successfully pushed the aboot.img file using terminal emulator and rebooted. Here is the md5 for the file:

0ba9ad45fc15cf3d62af7dd363686b3f
[Verizon Samsung Galaxy S III] kuntri:
So to do this correctly!

Odin back to Stock Rooted or Unrooted TWiz?

Then follow steps 1, Flash Custom Stock / Deox'd Stock, Unlock Bootloader!?
[Verizon Samsung Galaxy S III] trevoryour:
I have probably a stupid question but I thought I would ask anyway.

In Section 5 it says to you can flash any of these roms using CWM6. I seem to recall that AOSP ROMs had to be flashed with the kexec recovery in order to circumvent the locked bootloader. Is this no longer necessary since its possible to unlock the bootloader or is CWM6 the same as the Kexec recovery?

OK, two stupid questions.

Second, on the note of loading an AOSP ROM, the only thing that has kept from from diving in is that reports to flashing an AOSP ROM resulted in the IMEI disappearing and the phone being bricked. Is this still a problem? I really want my navbar back and I think loading JB is the only way to get it back.
[Verizon Samsung Galaxy S III] droidstyle:
Cwm6 works for both kexec and non kexec kernels/roms. Yes imei is still a issue, just back it up and flash away.
[Verizon Samsung Galaxy S III] droidstyle:
Thanks ill add that to the op!
[Verizon Samsung Galaxy S III] droidstyle:
No just follow section 1 to root and unlock bootloader, then flash rom of choice!
[Verizon Samsung Galaxy S III] Vorfidus:
So is the process of relocking the bootloader (flash stock, then locked bootloader) actually PROVEN to work? I'm trying to make sure there's a way to undo it in case I have to make a warranty claim.
[Verizon Samsung Galaxy S III] jdk2:
Not proven in a court of law, if that's what you mean. But it does work. Been there, got the t-shirt.
[Verizon Samsung Galaxy S III] droidstyle:
Im not promising you anything, but a couple other members confirmed it working.
[Verizon Samsung Galaxy S III] BloodKil:
so im having issues *facepalm* (on what should be the simplest root as its click a button and done)

Was running through the steps for option 1.

Got to point after restart and clicked ok when on lock screen... It scrolled through a bunch of stuff and at the end said su not found then done.

I then check out phone and see superuser is installed so dl titanium and pro key, then attempt to use titanium...

it give me greif about improper root or busy box, so install latest busy box and still no luck.

At that point im thinking ok something messed up in root and proceed to reflash debugfsroot with casual and bam BSOD as soon as i hit do it. (wtf?)

pc restarts and i again attempt to reflash debugfsroot and it gets to step 2 rooting loads daemon and just hangs there for past 20 min...

normally i would think patience is key, but with the other issues im wondering if something went very wrong on first attempt and idk where to go from here

any help would be appreciated *ashamed*
[Verizon Samsung Galaxy S III] droidstyle:
Sounds like a communication issue between device and pc. When you open casual and connect the device, do you see the "device connected" in green letters.
[Verizon Samsung Galaxy S III] kuntri:
@droidstyle

To be clear:

Backed up imei > if missing, do i use this tutorial to fix my imei and make it stick?[HOW-TO][FIX] Repair your IMEI with QPST - updated w/ info

---------- Post added at 10:06 AM ---------- Previous post was at 10:02 AM ----------

@droidstyle

which Recovery? CWM Touch or CWM6.x.x.x or TWRP?

For example, Flashing Stock Rooted TWiz = CWM Touch? Flash AOSP/AOKP JB Rom = CWM 6?
[Verizon Samsung Galaxy S III] droidstyle:
back up your imei regardless if you lost it or not... if it is missing then yes use qpst to backup. I believe the guide says to use cwm 6 as it works for everything.
[Verizon Samsung Galaxy S III] kuntri:
Cool, thanks bro!

:good:
[Verizon Samsung Galaxy S III] droidstyle:
No problem! Thanks for posting your question here instead of clogging up a dev thread or starting another thread about the same topic. My intentions of creating this guide was to answer all the simple questions here, thinking it would help keep dev threads clean...but it was a failed attempt! lol this forum is so cluttered it gives me a migraine!
[Verizon Samsung Galaxy S III] sbenson1226:
Edit: Removed.

I kept trying and it finally worked.
[Verizon Samsung Galaxy S III] strung:
Just a heads up to anyone, the CASUAL method didn't quite work for me (it seemed to have trouble keeping the ADB daemon) going but the alternative root method (with the batch script) worked fantastically!
[Verizon Samsung Galaxy S III] BloodKil:
yeah i get device connected on both initial connection and when device fully reboots for second portion it pops up as device connected again before i hit ok...

when i get home ill give it another run, but may have to run a different root method... my main reason for this was the bootloader and root all in one interface, but the market app seems ridiculously easy for BL as well. (and coming from an moto/htc past it probably wouldnt hurt me to check out odin anyway)

Hoping at this point its something stupid like my cable or usb port being screwy though as i have plenty more ports and cables to try when i get home.

As a bit of an update:

I still have no idea what was/is going on with my phone and casual, but through multiple ports/cords the process never fully completed and I never had the option of aboot... With that said it did get about 80% complete (the bar) on my last attempt out of 4 and I seem to have root privileges now even though it never completed.

Went ahead and got the unlocker from market and have Unlocked BL now and checked root with Ti, root checker, and a couple other root only apps which all showed successful. This does leave me concerened about an issue with my phone, but other than that im all good. (just wish I knew what was/is wrong)

Thanks again for the full featured post and great thread droidstyle
[Verizon Samsung Galaxy S III] Pixelation:
Thank you droidstyle for another great thread!! I'm so happy this one actually got Stickied... :) :) :D :) :)
[Verizon Samsung Galaxy S III] indyssee:
Thanks for this thread, droidstyle. Does anyone know if it will be possible to modify the Odin stock packages to include the new aboot.img? That way we could Odin back to a stock unlocked and be ready to go from there? Seems like that would be really handy if possible. Thanks.
[Verizon Samsung Galaxy S III] Coderedpl:
Forgive me as I'm a bit confused now, to revert back to stock with a locked bootloader.

Do we odin the stock image and then use the ez unlock app to relock it or is that step not necessary?

I'm assuming reflashing stock image using odin still keeps the unlocked bootloader, correct?
[Verizon Samsung Galaxy S III] droidstyle:
I believe the guide says to flash back to stock then lock the bootloader.
[Verizon Samsung Galaxy S III] Coderedpl:
Section 2 says:

Step 1: Download/Install Odin and Samsung drivers from section 1:

You dont have odin linked
[Verizon Samsung Galaxy S III] droidstyle:
Yea i forgot to relink odin after updating section 1...will fix asap.
[Verizon Samsung Galaxy S III] droidstyle:
ok for the folks that are having trouble rooting with casual using windws try loading it thru the program WUBI (Windows Ubuntu Installer)
[Verizon Samsung Galaxy S III] Hypnosis4U2NV:
Don't understand why people are using programs or apps to unlock the bootloader when using one command (2 commands if you type reboot) from the terminal on your phone achieves the same thing..

From rooted SGS3 terminal (with aboot.img in root of sdcard directory):

su -c "dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5

reboot

Sent from my Commodore 64..

READY.

load"*", 8,1
[Verizon Samsung Galaxy S III] Mystikalrush:
Is flashing a stock modem or kernal required when flash factory roms? On that note, do custom roms need this? Im not too fond on what kernals are and needed for.
[Verizon Samsung Galaxy S III] droidstyle:
Have you tried casual? Look at all the options it has and you will see why i added it to the op.
[Verizon Samsung Galaxy S III] kuntri:
Freezes

anyone experiencing freezing after the root then reboot with the Adam Outler's Casual program?

Edit:

Got it to work. have to wait until the SD card is read and the Casual says " system ready connected "

Also, I saw this:

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

Success

1159 KB/s (1468798 bytes in 1.237s)/system/bin/sh: /system/xbin/su: not found

Not found? Just ran Root Checker and it says that I am not Rooted? any suggestions?
[Verizon Samsung Galaxy S III] frankiedizzle87:
i cannot get Ubuntu to install on my computer it always says MBR file or something error upon reboot. i just sold my mac a couple of weeks ago too. :-/ guess i have to do it the long way lol. Did anyone using windows get Adams Casual to work
[Verizon Samsung Galaxy S III] droidstyle:
Yea i did
[Verizon Samsung Galaxy S III] kuntri:
I got it to work .. but my phone is still not rooted so im afraid to move forward ...

---------- Post added at 08:37 PM ---------- Previous post was at 08:35 PM ----------

i ran root checker and it says my device was not rooted. .. what did u do to verify root. also i got this prompt

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

Success

1159 KB/s (1468798 bytes in 1.237s)/system/bin/sh: /system/xbin/su: not found
[Verizon Samsung Galaxy S III] droidstyle:
Oh i was already rooted prior...just used casual to unlock and played with the other options.

Do you have busybox installed?
[Verizon Samsung Galaxy S III] kuntri:
No.

Should i root via ODIN then flash Unlocker from Casual?
[Verizon Samsung Galaxy S III] frankiedizzle87:
ok i got it too start this is where i am

Step 2 - Rooting...* daemon not running. starting it now on port 5037 *

ADB server didn't ACK* failed to start daemon *error: cannot connect to daemonerror: device not founderror: device not found

Cleaning up...

Restoring tmp...error: device not founderror: device not found

...done restoring tmp

Removing files...error: device not founderror: device not founderror: device not foundrm failed for /data/local/tmp/Superuser.apk, Not a directory

error: device not found- waiting for device -/system/bin/sh: /system/xbin/su: not found

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

* daemon started successfully *

/system/bin/sh: /data/local/debugfs: cannot execute - Permission denied
[Verizon Samsung Galaxy S III] droidstyle:
Try installing busybox first...if nothing then root with DebugFSroot by noxous ninja... link in section 1. If folks keep having problems rooting with casual on windows, ill put the odin method back up!
[Verizon Samsung Galaxy S III] frankiedizzle87:
will attempt busy box but i did use debugfsroot thats the only method i used
[Verizon Samsung Galaxy S III] droidstyle:
Debugfsroot thru casual or adb?
[Verizon Samsung Galaxy S III] frankiedizzle87:
OK busy box didn't work I get this (pictures)
[Verizon Samsung Galaxy S III] frankiedizzle87:
I have only used casual
[Verizon Samsung Galaxy S III] kuntri:
What if i did the the ODIN Root Method ... then unlock bootloader with Casual ?!
[Verizon Samsung Galaxy S III] droidstyle:
that will work or use the EZ-Unlock app...
[Verizon Samsung Galaxy S III] droidstyle:
try the debugFSroot method thats linked at the very bottom of section 1.
[Verizon Samsung Galaxy S III] frankiedizzle87:
ok i didnt get any errors this time this is what came up

Step 1 - Setup...

Copying files:

Copying su:4371 KB/s (380532 bytes in 0.085s)

Copying debugfs:5286 KB/s (1862336 bytes in 0.344s)

Copying debugfsinput:70 KB/s (144 bytes in 0.002s)

...done copying files.

Linking /system to tmp...

...done linking /system

Rebooting...

Step 2 - Rooting...* daemon not running. starting it now on port 5037 *

* daemon started successfully *

but the green bar on the bottom right of the screen isnt all the way full so... should i wait for more or its just done?

---------- Post added at 09:15 PM ---------- Previous post was at 09:11 PM ----------

ok root has been established and then i believe i unlocked my bootloader. how do i check that? so far i got this --Flash Unsecure Aboot--

This will flash an unsecure bootloader to your device.

*WARNING* It is possible that updating your device with any firmware past 15AUG2012 may cause this exploit to render your device inoperative. Please look at the comments on the thread on XDA-Developers.com

preparing to flash6076 KB/s (2097152 bytes in 0.337s)

Flashing4096+0 records in

4096+0 records out

2097152 bytes transferred in 0.440 secs (4766254 bytes/sec)

Done.

So lol what next? it isnt all that self explanatory i am dumb i guess lol this means i can start adding custom roms? or i have anything else to do?
[Verizon Samsung Galaxy S III] kuntri:
Cool! Just did the DebugFSroot method. So now i am going to try Casual .. :D
[Verizon Samsung Galaxy S III] droidstyle:
yes now you can start flashing custom roms! Use casual to flash cwm, then go to section 3 or 5 and flash a rom of your choice. Ill edit section 1 to explain this. I apologize for thinking it was self explanatory...I thought it was :o

Edit* I made some changes to section 1 for ya...hopefully that helps. Remember I am always open for suggestions and if you see a typ or a error let me know. This guide literally has been updated daily to keep up with things, so Im bound to make a mistake or two...thx!
[Verizon Samsung Galaxy S III] kuntri:
Lol it was self explanatory .. just did not expect different issues. I suggest reposted our errors to help others that maybe come across the same thing! Thanks for the help!

BTW my THANK Meter is wrong I've thanked more than 1 person since 2010 ...

Edit:

1. Flashed DebugFSroot method

2. Ran Casual Unlocker

3 Ran Casual CWM Recover

---------- Post added at 09:32 PM ---------- Previous post was at 09:26 PM ----------

Just to be sure that my bootloader was unlocked i downloaded Ez Unlocker and it showed "unknown" or still locked? Should I unlock it this way or just leave it based on Casuals results?
[Verizon Samsung Galaxy S III] RKramden:
I have been running just the root66 rom and just today d/l'd the EZ-Unlocker (had used the term. editor version to unlock the other day) ran it and got the same results as you. I just clicked unlock and now it says unlocked and experienced no ill effects.
[Verizon Samsung Galaxy S III] droidstyle:
reboot and if you dont get the custom unlock screen your is bootloader unlocked!!
[Verizon Samsung Galaxy S III] streetracer8605:
you guys are amazing, thank you soo much for doing this. This is my first Samsung device coming off of several HTC's, I am so glad I went with this phone.
[Verizon Samsung Galaxy S III] kuntri:
Ah yea i noticed that.. So I'm good, awesome!
[Verizon Samsung Galaxy S III] Mystikalrush:
If "Qualcomm secure boot : enabled" does that mean it's unlocked or locked?
[Verizon Samsung Galaxy S III] droidstyle:
it will always say enabled even when unlocked
[Verizon Samsung Galaxy S III] Dokted:
CAnada

Forgive if already answered, but will this workon my canadian s3? I bought it locked to rogers, but unlocked and am on mts. Thanks, Ted
[Verizon Samsung Galaxy S III] droidstyle:
Only if you like bricks!
[Verizon Samsung Galaxy S III] 420fan:
Great thread! I used your fascinate thread all the time, and I'm sure I'll be using this one quite a bit too. Thanks for putting it all in one place for us flash-a-holics
[Verizon Samsung Galaxy S III] aznguyen316:
I got my S3 rooted as I was able to install TiBackup and got that going. However, I needed to do a factory restore and stupidly thought I needed to unroot to do so, so I used the casual program to unroot.

So now if I want to re-root I am unable to? I'm not getting any uid gid on the easy root and casual just stops after loading a daemon tool. Ideas? If I am unable to root again, which what the warnings showed on the Casual program, then so be it as I did this myself. Thanks a head of time.
[Verizon Samsung Galaxy S III] mariod505:
This guide is a little unclear as to which sections are pre-requisites for other sections. For example, I had an issue with CM10, went back to stock, and now that the new bootloaders are available.... should I re-use the old method in section 3-4 or try section 1 (or now even 7) ? :confused:

Also, the IMEI backup reference link says (DO NOT USE THIS). Although I think it's referring to the restore process, it should be clarified.

---------- Post added at 06:57 PM ---------- Previous post was at 06:21 PM ----------

....Another thing that needs to be clarifies is what state the phone should be in when using Casual's method (section 1). ODIN, I'm guessing?
[Verizon Samsung Galaxy S III] incubus26jc:
iss there certain drivers being used for adb win7 64bit ?
[Verizon Samsung Galaxy S III] droidstyle:
I use the samsung drivers with everything that they apply to in my guide and everything works fine running windows 7 64bit. Not sure if this helps?
[Verizon Samsung Galaxy S III] incubus26jc:
do u use adb?
[Verizon Samsung Galaxy S III] droidstyle:
I have not on this device...however on my fascinate(GS1), I used the google nexus drivers. Not sure if they would work on the GS3 or not?
[Verizon Samsung Galaxy S III] Droopie28:
the casual link does not work for me right now, neither the one from his original post
[Verizon Samsung Galaxy S III] droidstyle:
I want to Thank You for the constructive criticism, or atleast im interpreting it as that? Anyway, I went back over the guide and made some changes...organizing all the sections in chronological order...Anyway now you as a new user should be able to follow the guide from section 1 on and have no issues...obviously there will be some spots that will require common sense. One example would be, you dont need to do section 1 and 2...the latter is just a alterate method. same goes for section 3 and 4... Pick one or the other and move on to section 5 if you want a custom kernel. Also some roms are already packaged with custom kernels. So do some research on your end and get familiar with what your doing before actually doing it!
[Verizon Samsung Galaxy S III] droidstyle:
posted a temporary link! :)