yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ak789:
Rooted with no Trip counter increment. [ATT]

Removed the bloatware using titanium backup.

Nothing from SDCARD got removed. All apps/settings in place

Waiting for Free Unlock s/w from Play Store - Please point if someone knows

Cheers :) :good::laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] saj222:
Another Telus user here. Instructions were very clear and my S3 is now rooted.

No counter trip and no apps/data lost.

Thanks OP!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ak789:
Another update ..installed the CWM with no issues :)

All set for custom ROMs :angel:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lensgrabber:
Does CWM support ext4? Can I format the card ext4 from the phone or do I need to load up ubuntu in a virtual machine and do it from there?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] creepyncrawly:
Odin is windows only. There is a program that will flash similarly to Odin, called Heimdall, which is open source, and works on Linux. But I havn't seen whether it will work on the SGS III. On the SGS II, it is best to use the command line version of the program to flash, since the graphical front end is said to be unreliable. For now, I think the safest route is to find a windows computer you can use.

---------- Post added at 09:08 AM ---------- Previous post was at 09:07 AM ----------

What is the model number of your phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markysd:
will this work on mac? just use heimdall?

first timer :o also if i unroot it will clear the counter ?

going to try and pull the trigger today and root my GS3..me no like crap ware

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobapunk:
Awesome, I had a bit of a refresher with ADB, I have not used it in a LONG time and had to re-install a newer version since the old one I had kept getting stuck trying to install updates...

Anyway, I am making a nandroid of the stock ROM now.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkey28rb:
I have been trying to root mine on my mac. No luck so far. Attempted to use heimdall, but it fails. Everyone on these forms use a pc so there is not much help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] creepyncrawly:
Mac and Linux users can go to the Heimdall website and use the contact form to ask Benjamin Dobell for support.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
can anyone tell me why my cwm is saying it cant make a backup because of an unknown path? im confused here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
It can't find the external card (yet). Try "backup to internal sdcard". You can move that with a file manager after.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
thanks man, backing up now. appreciate the help! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eddalysse:
Everything installed and is working perfectly. No issues so far!! Many thanks to the devs involved, now I'm a happy owner of a rooted SGS III :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markysd:
are you getting error when you hit start to flash?

i get error after i hit it..i also tried all the 3 terminal commands and use 2 different macs..install the sammy keis/heimdall and rebooted the computer and same error..

anyone know why im getting error? i download the latest software on mac/keis/heim ect and rebooted..:confused:

thanks guys:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phaze13:
Meh!

'su' is not a recognized as an internal or external command,

operable program or batch file.

What am I overlooking here?

ADB is installed, Path is taken care of. I can type ADB in the command promt and get the list of stuff but I'm stuck there.

Any help please :fingers-crossed:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brianaro:
Will this method install super user?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mpazevedo:
Wow, what do you think rooting is? Yes it does that. I am seeing the same posts over and over again. Try reading the thread or use the search.

Sent from my Samsung Galaxy S™III, an AT&T 4G LTE smartphone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] creepyncrawly:
@MrRobinson,

Samsung update has posted another Canada varriant for sasktel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bazald:
adb root

Should it be possible to run "adb root" after following this guide? I thought everything was working just fine until I tried to debug an app with ndk-gdb --verbose. Now I'm seeing the error "Cannot attach to process #: Operation not permitted (1)", and I'm not sure what to do about it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
99% you need a different cable. That's the number one problem so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Knight613:
How long is Odin supposed to be on aboot.mbn? Is it safe to unplug and try a different cable?

Edit: Okay nevermind. Just unplugged it and tried a different port and it seems to be going through now. That was kind of scary for a second.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkey28rb:
Yeah that's the error I am getting. I have tried everything. Very annoying.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkey28rb:
I am using the cable that came with the phone? I wouldn't see how that is the problem? :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Doesn't mean it still couldn't be a problem. I would try a different cable just to rule it out. I would also search the thread to see if anyone did this successfully on a mac (I don't remember offhand).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markysd:
thanks i tried it same error ''ERROR: Failed to initialise protocol!''

i used the cable it came with and its long also used a bit shorter one same issues..will using a USB Hub be safe? maybe it needs more juice due to longer cable:confused: idk:eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Knight613:
So I got up to here...

<ID:0/005> system.img.ext4

<ID:0/005> __XmitData_Read ..

<ID:0/005> XmitData Fail..

<ID:0/005> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

Does that mean I have to redo it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
holy #$%$ how many of these variants are there?!

I'll wait for someone to ask.....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gadgetz:
Couple questions....

As for the AT&T download, I used the file provided in the Temp Mirror 1 cause it downloaded very fast. Is that the new d/l that has addressed the system size issue? If not, which one should I use?

I understand the Odin part of the process but I've never used adb before. Should I put the phone in d/l mode first, then connect it to the pc, then open the adb prompt? Once in there you say run su, but it looks like you entered "$ su" is the dollar sign needed? Then when you entered the next command there is a hash mark at the beginning, is that needed?

^^^That should show up after entered the last command? And lastly, I should enter "# reboot recovery"? What happens after I enter that command? How do I know when I can unplug my phone from the pc? Should I reboot the phone immediately after unplugging it or can I just start using it as normal?

Sorry for all the questions but this is my first Samsung phone, first time using Odin, first time using adb so I just want to know what i'm doing before I dive in.

Thanks guys
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
yes and try a different cable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Knight613:
How long is the system.img.ext4 part supposed to take? I feel like it takes a good 20-30 minutes just to get through.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
you boot your phone up normally for adb. if you aren't fam with adb just grab terminal emulator from the market and run the commands in there. yes you would type su <hit enter> then your prompt will change to the hash.

then the other commands just as in the OP. the reboot recovery reboots your phone into recovery just to verify its there but that is optional.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
it's def the longest but i'd say more like 10min if i recall correctly.

maybe re-download.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Knight613:
I got it to work finally. Switched USB cable and used Odin 3.04 instead of 3.07 just in case.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
I don't think 3.07 works quite right (yet) - you're not the first to mention that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] egyptshun:
If I do this will it wip all data on my phone? and not tripping the counter will maintain the warranty?

sorry for the noob question, new to samsung... (not android...)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
No and yes respectively.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gadgetz:
Alright, rooting via Odin went smooth! Confirmed root by installing MyBackup Root. Booted back into d/l mode and my flash counter shows "none".

Now i'm at the CWM part, the instructions say to d/l and extract a file from the CM link provided, but when I d/l the file, titled "CWM Recovery LTE SGS3 v4 tar md5, I can't extract anything. I use winrar. Am I supposed to extract anything or simply place that file onto my internal sdcard on the phone and proceed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] majingrim:
I've received a couple PM's asking about rooting my Bell SGS3, so I just thought I'd say that this works great on a Bell phone, and any Bell customizations that might be missing are definitely not missed. I didn't have to change any settings, or even wipe any date.

I'm even using KyanROM v1.1 with no issues whatsoever. If anyone would like me to test something on it just to make sure, let me know and I'll be happy to give stuff a try.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gadgetz:
First of all, thanks to all who were a part of making this happen for us. I commend you guys and your talents are undeniable.

This is my first Samsung smartphone, first time using Odin, first time using ADB.....I was able to pull this off without any surprises by following this guide here. However, just wanted to let you guys know that when I was flashing via Odin I had unchecked F. Time Reset. I had found a video on YouTube that showed this process and he said to uncheck it, so I did only to find in the tutorial here that I should have left it checked. I was worried it would increase my flash counter but it hasn't. In d/l mode my phone shows:

Product Name: SGH-I747

Custom Binary Download: No

Current Binary: Samsung Official

System Status: Official

Qualcomm Secureboot: Enable

When it came time to push recovery via adb I was stuck. I had downloaded the recovery file but the extension was .tar md5, wasn't able to extract it. I deleted the md5 part and extracted it via winrar and proceeded. One thing that concerned me once I got into adb was when I typed in adb shell, I didn't see anyting about running daemons or starting it or anything....it showed that in the video. But I was able to run the commands listed and all went well.

Thanks again guys
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hunmin:
The Virgin Mobile S3 is I747M. It would be nice if someone can post an official rom for Virgin too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
after the phone rebooted, my language is in korean. how do i get it back to english?

*after flashing a custom ROM, it fixed itself. language is now in english
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gadgetz:
Apparently there's an update for SU available via Google Play Store....is it ok to update it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
yea, you'll be fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Unfortunately you need to do the first part using odin and that requires windows. The linux equivalent is heimdall and it currently does not support the s3. I was in the same boat as all my computers run linux... Had to borrow my step son's laptop.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RTBee:
I used 3.07 without any problems.

Interesting, Canadians Rogers is also the I747M I believe. If so then I would suggest that they would be compatible?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
Just wanted to say Thank You to all you guys that put in the hard work of making these phones better. Worked flawlessly. Thanks again.

PS. Now I'm just waiting for Task and Ktoon. :highfive::)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Planswalker89:
So I followed all the steps for the recovery, but when I put in reboot recovery (I was using the shell emulator) I got the standard android 3e recovery and not CWM. Should I just try again?

EDIT: Tried again, it worked this time. :/ Hopefully I didn't screw something terrible up the first time or something. I guess I'll find out sometime in the future...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Ktoonsez is already here - rocking his kernel already :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
:good::highfive: Ten fo. I've been watching KT747. Task even chimed in from the deep woods. :good: It's like you know what you are getting for Christmas and you really want it now, but you can't open it. :crying:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] qwer777:
Dammit! ok. Does running odin require admin access? If not, I can just use campus computers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
How will you get the drivers installed on a locked down campus computer?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dbzgod:
Finished work on my own Bell Official Root Injected rom here:

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

It took me longer because I had to do it without a Linux box, funny enough I manage to do it using my Rooted S2 phone lol.

If anyone is interested in it I did make it with 1 small difference over MrRobinson's ones, I used Chainfires SuperSU root rather then superuser as its what I perfer to use.

Also I noticed some people were saying the ones MrRobinson's made were taking between 10 and 20minutes to flash, I used my injected Rom myself on my own S3 and it flashed in 6 minutes from start to finish.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] qwer777:
Good point. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Consider running Windows on your Mac...

VMWare or

Bootcamp
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] qwer777:
Are you saying you found a way to do it without Odin?

---------- Post added at 11:15 AM ---------- Previous post was at 11:13 AM ----------

Linux, not mac, but I guess I could try that, if my pc can handle running a VM(its an old piece of crap.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
My bad... Windows XP would be suffcient...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhinez:
Just did this on Windows 8 64-bit. Worked perfect. Thanks.:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cracjackson:
is the .tar file for the att stock_root67 supposed to be 1.5 gb? When I download the zip and extract the .tar it still shows up to be a winrar file. It does say stock_root.67.tar on it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhinez:
I noticed this too. If you was to put extracted file in odin it will show up as a .tar file. The un-extracted file doesn't even show up as a pda/.tar file on odin. It's funny to see a zipped file of a zipped file.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cracjackson:
Yes putting the extracted file in Odin does show up as tar even though it looks like a winrar zipped file. Yea Ive never seen that before I was little confused by it. So there is no reason to worry about this it'll flash fine?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brianaro:
I have Superuser on my phone was I suppose to get Supersu after the root?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
NM misread.

Edit- sorry I misread. I thought he asked if he was suppose to get superuser.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skatin707:
That's what it shows for me.

I want to give this a shot, but I need to make sure there is a solid way to reverse root access.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] creepyncrawly:
No, not if you used the file from the OP. A user posted a download with Supersu here.

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

You can remove root by using a root file explorer to remove /system/app/superuser, /system/bin/su and /system/xbin/su. After you reboot, you'll not longer be rooted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skatin707:
Perfect, I'll run this then.

The file is supposed to be 1.5gb, correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] creepyncrawly:
Yes, it is that large.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dbzgod:
Anyone who has used MrRobinsons root injected roms, can you please do a *#1234# on your phone and tell me if the CSC is listed properly or left as unknown?

I noticed on my root injected rom that I made the cache file didn't install properly when the phone boots after flashing and are left with a blank CSC, this doesn't hurt your phone ofcourse, it just doesn't install any of the carrier extra apps from it not being setup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brianaro:
How do I replace superuser with supersu?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gadgetz:
If you're talking about the root injected file we flash in Odin in the OP, I ran it and just entered the above code and this is what I got:

Version:

AP: I747UCALEM

CP: I747UCLEM

CSC: I747ATTALEM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dbzgod:
Thank you.

I don't know why but on my rom it doesn't install properly, and I didnt do anything to the cache csc file itself either. Maybe it is a bust file from Bell to begin with? I dont know.

Can someone who used the Bell Image to root their phone do a check to see please?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dbzgod:
Thanks bobapunk

Btw what systemui mod is that from? That is what im looking for on my S3 as I had that on my S2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobapunk:
Go to the SGS III themes and apps forum and find the thread named, " [THEME][PORT]ICS DOMINATION v5.0 (07.08.2012.) SPRINT, AT&T AND T-MO WORKING!!"

It says version 2.0 is for at&t, but I am running v4.0 on diet ICS just fine. I am about to flash v5.0 to see if it works too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skatin707:
Well it worked, as expected. However I got superuser, not supersu. I clicked the link above, but it lead me to a post. That post contained a link that lead me back to this thread.

Anyways, is this a problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
No, now that you are rooted you can install whatever su you want. I stuck with the traditional ones.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skatin707:
That's what I figured, but I got confused by the previous question. I wasn't sure if getting superuser instead of supersu was an undesirable outcome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gadgetz:
Why is it an issue to get superuser rather than supersu? What difference does it make? Those of us who don't have SuperSU, can we just d/l it from the play store and delete the existing SU app? And if so, why should we do so?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dbzgod:
I havn't been able to fixed the issue with the cache CSC file not installing properly so I have taken the link down from my thread, for anyone who wants SuperSU root instead of superuser, just flash MrRobinson's firmware for your phone and change it out to SuperSU from the play store.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ak789:
Same for me all the values match.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
A little off topic, but something I found interesting. There is a lot of news around the Locked-Bootloader version of the Verizon variant, and that some folks have "uncovered the mystery" of unlocking and rooting it.

I read the method, and it looks strangely familiar to the detailed outlined in the OP, from the flashing of the root-injected ROM to the ADB shell command sequence for CWM.

Who would have known? :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] umvagia0:
Do I have to use ADB to install CWM for the no tripping flash counter? Or can I use Cyangenmod's method of installing CWM (using Odin) in order to get the same result?

I rooted my phone as per the steps outlined in this thread with no issues.

Thanks for your help, I truly appreciate it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anethema:
Do NOT NOT NOT used Odin to flash CWM, or your counter will increment. The only thing you can ever flash with Odin is the rooted system image in the OP.

After that you need to flash CWM using dd, whether through a terminal, ssh, adb, whatever.

After that you have CWM and all your flashing should be from CWM to not trip counter.

If you ever flash anything through Odin other than one of these images designed not to trip the counter, it will trip it.

Good luck!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stickem601:
Anyone else having issues with the data connection not working for Att sgs3, has all the apn info entered, but phone will not connect. I've tried different apn's from the one i have and its not working. I've also reset to default a few times and thats not working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] umvagia0:
Thanks for the clarification. The Odin method just looked way easier. Not familiar with adb but I'll read the entire thread and then give it a go.

Thanks again for the help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vlara:
Hey guys just letting you know that I thought I had bricked my phone cause odin would continually hang during flashing. Tried it atleast 5 times on 2 different computers using my old gs2 usb cable and it would never finish even after leaving it for 3 hours, then I used the usb cable that came with the gs3 and it worked the first time...... so I would suggest everyone use the cable the phone came with to avoid thinking they have a bricked phone lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
Never used ADB myself, I just read the instructions a couple times and used terminal emulator. Just follow these guys instructions they know their shiz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Did anyone else get the issue where CWM can't mount your sdcard? I am using the AT&T GSIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Yea it's been mentioned a lot in this thread now. with your addition I should prob add this as a little fyi to the OP. thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Format as FAT32
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Stoneyguy:
Could I get a bit more detailed explanation of where to put the recovery.img file? I tried to access it via adb but it keeps telling me there is no such file or directory. I placed the file in both the root of the SD card and in a folder marked sdcard in the internal memory.

I'm sure it's just some bonehead mistake on my part. I'm new to adb and it's been years since I had to mess with a dos prompt.

Thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
are you successfully running adb shell and getting an android prompt? once you do that if you ls /sdcard do you see it list recovery.img there? if not its in the wrong place. how are you copying it to your sdcard? you are extracting the recovery.img from the download first correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lastimp:
Worked awesome on my AT&T SIII. Just one question, sorry if its been asked before I could not find the answer.

After a reboot the market said there is an update for superuser, is it safe to just update or will that bork the version of superuser installed from the original post?