yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] laughingT:
Worked great for me, using odin 1.85, reboot unchecked as suggested. I pulled the battery after odin reported successful flash, reinserted battery then reboooted to recovery and saw the script completing the installation.

Just got a refurb SIII from AT&T, with 4.3 already installed and a ridiculous amount of AT&T bloat. It has an August 2013 build date.

I'm now using TiBu to freeze and/or uninstall all the junk.

Thanks - your third post in the thread is key.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Torlugic:
So the Canadian S3 i747m doesn't need anything special to root just flash cf then a recovery and good to go eh.

SlimKat powered

1337m

4.4.2 build 2.6 RC 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mscott998:
download is no good

! C:\Downloads\CF-Auto-Root-d2att-d2uc-samsungsghi747.zip: Unexpected end of archive

download is no good. anyone have a good copy?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
http://download.chainfire.eu/235/CF-Root/CF-Auto-Root/CF-Auto-Root-d2att-d2uc-samsungsghi747.zip

Works just fine for me. Packed with ODIN v1.85. Chainfire doesn't want people to redistribute it, so get it from the page I linked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -Epix-:
ugh the process that i forgot was that if your not a Samsung user anymore and doing this for your wife you require keis installed on your computer ..lol :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ruler1976:
im on i747 att 4.3 supersu just crashes thats all i can get it to do

---------- Post added at 09:59 PM ---------- Previous post was at 09:59 PM ----------

knox is blocking is there a fix im missing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jack0131:
Make sure to update the busybox in Play Stroe.

jack Bell SGSIII:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ruler1976:
what app do you use to do that

---------- Post added at 10:15 PM ---------- Previous post was at 10:07 PM ----------

if you mean update super su in playstore than i have
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jack0131:
After Super SU updated, it should detect Knox and tell yo that is going to try disabling it, at least mine did.

Jack
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] collad0:
I don't think you understand. After using auto root, knox completely blocks supersu and you can not open it up to update it. I am having the same problem any help would be aprreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mscott998:
Go here

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

There is a link for a recovery flashable Knox remover. Flash it and your problem is fixed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Does this method work for a recently acquired phone with att 4.3 and mjb bootloader?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bzow:
I would also really like to know. It seems like some people have had success with this or the CM Installer method, but I haven't tried either yet. I'm still researching.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] laughingT:


Yes.

It did for mine, acquired from ATT in February.

Look at the 2nd post in the thread by chainfire and use the links and methods there. I used odin version 1.85 and the separate tar file in that post.

-make sure you uncheck reboot in odin, then reboot directly into recovery before doing a normsl boot. The reboot into recovery executes a script that makes root and su stick. If you reboot normally immediately after, without recovery boot first, the changes will be overwritten by stock boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arthurearl:
I have used this method to root my phone back in February of this year. All of a sudden my phone is telling me that it has no root, so I re root via CF Auto-Root thru Odin and ten mins later it's unrooted again. I'm running Stock 4.3 with root only. Does anyone know why this would be happening and if so is there a fix for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] josue276:
I can do this in i747uclh9?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melkis:
flashing CF-Auto-Root-d2att-d2uc-samsungsghi747.zip into a samsung galaxy s3 i747 4.3 OTA can cause uknown imei?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baghera1979:
followed OP instructions to the "T" and Odin is stuck at "get PIT for mapping".

been like this for few minutes. i know it should of taken alot shorter than this.

should i just plug plug from phone and retry?

EDIT: You can just pull plug and go with root method #2 from here http://xdaforums.com/showthread.php?t=2538991
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bozob:
I had done this successfully on a previous version of this phone just a month ago. But I had to have that phone replaced under insurance (took a swim with it) and the new phone won't root using this method.

I've enabled USB debugging, run Odin3-V1.85, loaded the ATT-sgh-i747 tar.md5. It loads, reboots to recovery, I see that it's loading into recovery mode and running the necessary processes before rebooting. But SuperSU doesn't get loaded on, and when I try to use the store to load it, it says that it can't find the SuperSU binary.

I've loading TRWP(?), but it won't see any files on the SD card and won't mount the card.

Any suggestions on what's going wrong and how I can fix it?

NOTE: I just found out that every time I try to do a recovery reboot (volume-up/home/power) it loads the red log and does a CF-auto-root. It's as if the efforts to write the SuperSU binary and copy back in the standard recovery don't work. I don't know what could be causing this.

Thanks

Baseband version: I747UCUEMJB

Kernel version: 3.0.31-2024954

se.infra@R0210-11#1

Oct 31 01:05:53 KST 2013

Build #: JSS15J.I747UCUEMJB

SE for Android status:

enforcing

SEPF_SAMSUNG-SGH-I747_4.3_0010
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] venkatx2:
Works like Charm on AT&T I747

It took less few minutes to root. Never done root so fast like this before. :cool:

Kudos to the author and team. :good:

Galaxy S3 I747 Android 4.3 :cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] socheat:
Going to try with my old S3 Rogers :D

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MWTTRON:
USB debugging mode ATT I747 Android 4.3

This is a really NOOB question !

I am embarrassed to ask it but here goes...

I just got a new ATT S3 I747 Android 4.3

I cannot find developer option anywhere in the settings menu!!!

I install the drivers on my server and get the Blue com in Odin 3.7 but only when booted up normally.

There are two options there if I select the NON MTP option the blue com light goes out in ODIN.

I gotta be brain farting this!

Someone "Stop laughing at my ignorance" and HELP!!!

OK OK I figured it out. Dang I need a drink!!!

tapped build 7 times! Woo Hoo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
Just go to settings, about and in the build number just tap continously until you see the message that the developers options are unlocked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Murshad007:
I am having exactly the same issue.. On bell canada i747M 4.3 stock... Please help... I have dowmload 4 different stock 4.3 roms of canada as my phone is unlocked.. but I cant super su installed by cf auto root... I insatlled su from play store but it keep saying that no binary installed and whenever i goes to recovery... it shows in red that it tries to install su and cleraing recovery
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bozob:
What I found was that when I did a factory reset it came up with an option from Samsung to have the phone protect itself from malicious software. When I allowed this option I couldn't get in with any of the rooting programs. But if I disallowed it I could run not only CF-Auto-root, which would trip the warranty bit, but also Safe Root (http://xdaforums.com/showthread.php?t=2732695) which wouldn't.

I don't know how to disable this option without going through a factory reset. You'll have to look that up yourself.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Murshad007:
Non, I rooted with saferoot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] merlise:
Thanks for the easy to follow instructions :3! Everything is rooted perfectly!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eddberkel:
Hey, I have done the instructions on my SGH-i747M, and it says unfortunately SuperSU has stopped working. Is it because stock rom is now 4.4.2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheemer:
Latest Rogers release does not work with this method or towelroot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XBrav:
I think I have it working. It takes a bit of time, but so far no issues.

1) Install TWRP through ODIN: http://teamw.in/project/twrp2/104

2) Install Team Epic root through TWRP http://www.epiccm.org/2012/06/team-epics-root-from-recovery.html

3) Reboot, and install SuperSu through the Market: https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en

4) Boot SuperSu, and upgrade the binary (normal seems to work fine). Allow it to remove SuperUser. I also allowed it to remove KNOX.

5) Reboot, and you have the latest SU binary working.

I can confirm this is working on NF2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wash23:
This method, using the Team Epic Root, worked for me when other methods failed. SGH-I747 stock 4.3. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jetdoBAO:
sgh i747m work for me

thank you;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dalanis 12:
i747 checking in, and it worked too from 4.3 stock! Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vietcool:
help please

My windows 8 doesn't reconigze My samsung galaxy s3 att. What can i do??? help please
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hossy923:
[MENTION=631273]Chainfire[/MENTION]:

Today I downloaded the CF-Auto-Root for my AT&T GS3 (SGH-I747) from the web site. I noticed that the file time stamp within the ZIP is 8/7/2014. The last version I had was 5/21/2013 which matches the latest forum update. Can you tell me what changed with the 8/7/2014 update other than the newer version of ODIN? The .tar.md5 files are different.

The reason I ask is that I'm still running I747UCDLK3 (4.1.1) and I'd like to upgrade to the latest OTA from AT&T and I've been having trouble. Already bricked the phone once, but miraculously was able to recover it although I'm back to 4.1.1 again. The OTA app is downloading 2400258.cfg (to /cache/fota), but when I move and rename to a .zip for Mobile Odin Pro, it's been telling me there are corrupt files. I believe the OTA version is I747ATTEMJB (./system/CSCVersion.txt). From what I'm reading online (here), I need to flash a new kernel to allow the OS to boot because the bootloader I have won't load the new ROM. However, I like to keep everything as close to stock as possible (if possible). IIRC, CF-Auto-Root either replaces or modifies the kernel. I'm wondering if I apply the 8/7/2014 update to my 4.1.1 ROM before attempting to flash I747ATTEMJB, will that provide me what I need to boot the new OTA ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hossy923:
UPDATE: I got it working, but wasn't able to use CF-Auto-Root to regain root. I had to use Towelroot. Then used SuperSU (after it updated su) to disable KNOX. Is there going to be a version of CF-Auto-Root that won't trip the warranty bit?

For the curious...

The OTA download (2400258.cfg) was not corrupt. The files that Mobile Odin Pro was indicating were corrupt was actually the result of the assert checks failing in the update_script (although, it would be nice to see a list of failed statements from Mobile Odin). I ended up downloading OTA Verifier which was able to provide details about what was failing. Turns out the ExchangeHack contributed to 2 files, ddexe contributed to 1, and the others were the result of using Link2SD to integrated updated APKs into the system (which I will never do again). Re-flashing the ROM when I first bricked the phone resolved the Link2SD items, so I just used the ExchangeHack restore script and ES File Manager to fix rename ddexe. Then, Mobile Odin Pro had absolutely no problem applying the OTA update (and no bricking this time).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VancouverGreek:
I tried this method when i opened SUPERSU it says "THERE IS NO SU BINARY INSTALLED AND SUPERSU CANNOT INSTALL IT. THIS IS A PROBLEM. IF YOU UPGRADED TO ANDROID 4.3 YOU NEED TO MANUELLY REROOT"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ShadowVlican:
worked great on my Rogers S3 (I747MVLUFNF2_I747MOYAFNF2_I747MVLUFNF2_HOME.tar.md5 latest)

now i can install slim rom on this old pos

thanks for this super easy root!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tank Weston:
Root

Quick question, will I lose any internal data?

Just found my answer, never mind. thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dsilx:
confused

OK so from my understanding I can use this method to root s3 i747 on 4.4.2 software

Way different from other devices if rooted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbygfy:
I am on NE4 as well and would love to know if I can root my phone with this method.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stickus:
Bandwidth exceeded?

I'm getting a bandwidth exceeded message from the download link. Cause it's the last day of the month? Anyone have an alternative link?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arasarn:
worked great on my rogers galaxy s3 with the most recent software.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawiejr:
Schweet

Easy Root - $1 on the way. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ekoo:
Can someone confirm that this root method works with the new NK2?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jigsatics:
I'm also interested in knowing. My wife wanted a rooted S3. I rooted mine a long time ago with an older MK5.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ordio:
FYI. Got a new Galaxy s3, and it updated to build KOT49H. I747MVLUFOB1. Used this to root, disabled KNOX and all done. For anyone unsure with this new version (dated feb 4, 2015), it does work.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Old School Joe:
Making an image of a SGH-I747 with 4.4.2 - KOT49H.I747UCUFNJ2

Hello,

First thanks for such a great forum, new to Android (I'm a late adopter LOL)

I'm an older guy and coming from an old Nokia running symbian, for many years I have made backups of the phones for my three kids and I, so if something happened we lost nothing, it also helped rolling out modded phones by doing all the work once on my phone and then restoring for my kids phones

Correct me if I'm wrong but my understanding is I have to root my phone so I can make a complete backup of all my phones settings, passwords, screens, etc ?

So I want to make an image (or just a backup) of a SGH-I747 with 4.4.2 - KOT49H.I747UCUFNJ2

My research says the KOT49H.I747UCUFNJ2 came out later in the year and most of the programs I read about say it can be a problem

After CF-Auto-Root will I be able to back up everything on the phone ?

Much Thanks !!

Joe
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Old School Joe:
So I used CF-Auto-Root and rooted the phone, then I used CWM Recovery to make a backup of the phone, Then after rebooting I used CWM Recovery to restore the phone, Now I get app errors from Google saying they have to all be shut down (I think its a cached certificate problem), is there something better to use for what I think is called a "Nandroid Backup" How about TWRP ?

Should I load some other ROM ? Please help I am the worst thing (An "old" Noob LOL)

Joe
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] OneLonelyPolka-Dot:
Did you ever get an answer? This is exactly what I have as well and everything I've found is for 4.3 or earlier.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Slik50:
I have the galaxy express prime will it work ??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] josephjq:
Thanks for getting me started.

I just rooted my first phone thanks to you making it accessible like this. I'm trying to follow the first step of making sure that I have good backups, and I am inclined to take your advice of going with Mobile Odin Pro and Titanium Backup Pro due to your established reputation, but I recognize that this post might be outdated. Do you still recommend this, or would it be better for me to go with TWRP Manager Pro which seems very user-friendly for beginners such as myself?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
The op is a bit outdated. I recommend using TWRP 3.0.2 (if you're not already) as its the only recovery being maintained currently and making the backup in recovery is much safer then using an app. The TWRP app is great for keeping your recovery up to date but I've never done a backup with it. For backing up your apps & data I strongly recommend using Titanium Backup Pro. Its about $8 but its totally worth every penny in so many ways. There's a free version as well. Good luck & enjoy your freedom that is your newly rooted device!

Edit: Oh yeah... Welcome to the threads ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] josephjq:
Thanks

I know this thread is old, but thank you so much for taking the time to get me up to speed with your suggestion.

---------- Post added at 10:29 AM ---------- Previous post was at 10:16 AM ----------

I just want to make sure that I'm understanding you correctly. You are suggesting that I use the TWRP Manager app and install 3.0.2-0 as I already have for my Nandroid backups and then also get Titanium Backup Pro for my regular backups?

Or were you just saying to root using TWRP 3.0.2-0 and then use Titanium for backups? If so, I would love if you would check out the description video for the TWRP manager app in its current state and tell me what you think cause I think it's new and it seems to have some cool features which may be good to have as well as Titanium.

I would send a link but I don't think they will let me yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Roy@lty1102:
I used Odin on the PC to get TWRP recovery...it's different from an app. The manager app helps make sure it's up to date...this phone is old and there's not a lot of updating for it left. I'm not saying development has stopped, it's ongoing and I appreciate all the work people are doing but the reality is it's an old phone so TWRP manager isn't necessary.

Now, boot into recovery to use TWRP to make a nandroid backup. Essentially it's a disk image of your phone. Titanium land yes the Pro version is worth it) backs up your apps so that you can change ROMs or even upgrade android versions and then "bring" all your apps and data, even call log and SMS messages along.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] josephjq:
Thank you very much, and thank you for taking the time to explain things a little bit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Zratinel:
SGH-i747M

i just done rooting my phone Samsung S3 SGH-i747m.. and now im wondering if my phone is AT&T, Rogers, Bell, or Telus.. and my question is how to know if my is AT&T or Rogers etc.. i was a little bit worried.. i really need to know what's the correct one.. i wish someone would notice my question. :o:o:o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
If it is an i747m, then it is the Canadian variant. Check the model number under the battery to be sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] proza:
I downloaded the auto root zip file for i747m. Inside the zip, there is odin 3.10.6, tmax.dll, and zlib.dll. I have dowloaded the odin 3.10.6 zip from the official site, the zip contains the .exe, S1PlugIn.bundle_141117.zip, and SS_DL.dll. which odin should I use?

Is it possible to flash TWRP using odin after the root is done?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] proza:
This CF-Auto-Root works for both JellyBean and KitKat?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sledjunk:
I have a 'new to me' S3 i747m that I am trying to root.

I tried odin 1.85 and supposedly flashed RecoveryGalaxyS3USCanada.tar, but it did not come up with the expected recovery. However, now when I try to connect to odin to upload cf-auto-root, odin does not see my phone connect or disconnect. If the phone is not in recovery, windows 7 gives me a device driver error. This is all with the same cable, and if I use my original working S3, it connects and is recognized.

BTW, the USB port on the phone does work to charge the phone.

Any assistance would be greatly appreciated.

Thanks
[Captivate Q&A, Help & Troubleshooting] jes24cap:
I am rooted and trying to install a custom recovery. I have Rom manager but it will not allow.me.to choice the captivate as my phone. It gives ne the i9000 or the epic or the nexus s. I did try the i9000 but it did.not work. Here is what i have tried.

1. ensure that my phone info.shows the i897 - yes

2. try down loading from cwm website. - when.installing still shows not signed.

3. Google for an answer - no luck

Please help
[Captivate Q&A, Help & Troubleshooting] 4-2ndtwin:
U should have looked a few threads down at a thread started 2 days ago... Here ya go... http://xdaforums.com/showthread.php?p=33400589

:thumbup:
[Captivate Q&A, Help & Troubleshooting] up_on1:
clockwork mod

Did you figure your problem out yet? You have to flash a kernel w/cwm; Other than that, in my opinion clockwork mod is racist towards i897 (captivate) If your still struggling; let me know and I'll walk you through from start to finish! I'm newbie so I know how things may get frustrating at times. Oh and don't worry about me being a newbie; I learn quickly!
[Captivate Q&A, Help & Troubleshooting] jes24cap:
Yes I finally got it but it was a pain. I did what the link told me to and bricked my phone. Then I had to use Odin to bring it back to stock and my phone would not update from elcair. I then went to Samsung's website and downloaded the updates and tried to follow what the link above said and it worked. I am now on JB with no issues.

I bought this phone from craigslist and I think I bricked it because the phone was running eclair and I was trying to go straight to ICS.
[Sprint Samsung Galaxy S III] jdelano:
A strange thing happened between my last change (last night) and this morning.

My previous charge I got 2+ days on battery.

I charged it to 100% and went to bed, woke up with 39% battery :eek:

I checked better battery stats and msm_otg is at 16+ hrs.

I've never seen this before on my phone and nothing changed at all yesterday.

I did some searching and I found that it may be used when the the phone is connected to the computer.

I started charging it via my computer but when I moved from my office to the living room later; I connected it to an AC charger.

I'm going to reboot and then recharge. I hope that it clears.

Anyone else seen this wake lock?
[Sprint Samsung Galaxy S III] xerigen:
Same exact thing happened to me on my Sprint SGS3 after upgrading to the official Jelly Bean. I'm not rooted. Figure anything out? I've been searching my brains off.
[Sprint Samsung Galaxy S III] jdelano:
I restarted my phone and it is nearly fully charged (charging via USB on my PC so it takes a while)

I'll update this tonight with whether or not it did the same thing.

EDIT: well after nearly 7hrs; battery seems to be fine. the msm_otg wakelock still is listed at the top, though I suspect that is only due to the fact it was listed before and it will slowly go away, we'll see.

I am at 92% so my battery life is back to normal. The other thing that was different was a charger I used, I switched it to the proper on after a little bit. Maybe the wrong charger caused it to act the way it did.
[Sprint Samsung Galaxy S III] jdelano:
Still ok

Well this morning, I have 20hrs off charger with 82% battery left.

I am thinking that it had to be the charger it was on after charging for a bit on my PC.

Moral of the story is to always be 100% you're using the proper charger for your phone :)