yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Invalid md5 sum has nothing to do with drivers or kies. It is a number generated through a crap load of variables that is unique to that file. Because it is a tar.md5, that means the check sum (aka md5 sum) was (must likely) created and attached when the tar file created. If you get continued failures, either your internet connection is to blame or the upload was corrupt. Since no one else has complained about it, and you've tried multiple mirrors, I would say it's your internet connection. UNLESS. You should never try to rename a tar.md5 file. Sometimes that in itself can cause a check sum failure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Night_1:
OK...i am going away to work and will have use of a different service provider...ill try download from there....

I have not however renamed the file....used 7zip and winrar to try decompressing...still errors...

ill download from work and try that....:)

Still a no go for me...same checksum error...Had a PM from someone else having the same problem....ill copy paste what they said to me...

Sometimes it just sucks being stuck in a contract with a phone company lol....if bell and telus had better data plans (Sasktel is unlimited) i'd go with them and be able to use the root rom from here hehe
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Night_1:
Re: sasktel

Quote:

Originally Posted by neoaddict

Hey, I don't have 10 posts yet so I can't post on the dev forums yet, but I wanted to say that I'm also experiencing the same problems as you are (failed MD5 checksum) when trying to flash the rooted version of android 4.3 for the S3 on Sasktel. I tried flashing it without the .md5 extension, and it generally worked, except the phone's modem did not work at all (maybe some kind of problem in the rooted file related to that?). I flashed the stock version with Odin and it had no problems, so it seems like more of an issue with the rooted .tar.md5 than your computer or mine.

---------- Post added at 11:38 AM ---------- Previous post was at 10:44 AM ----------

here is a question....

if i pay for a carrier unlock code (phone is currently locked to Sasktel).....would it be possible to flash with a Telus (or Bell) root injected image and still be able to use my Sasktel SIM card?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Night_1:
ok...i have downloaded the file (sasktel one) 3 times from each of 4 mirror...on 3 different internet providers...and i still get the same md5 checksum error....

i downloaded the 4.1.1 and 4.1.2 files just to check and they check ok...

is it possible the file is not good... or am i doing something wrong?...:(

i am still on mrRobinsons 4.1.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Night_1:
Is the wifi the same for telus, bell and sasktel? I flashed stock Rom with mobile Odin pro everroot supersu and mobile Odin injected and everything works but wifi..... Would flashing the root injected Rom for Bell (from mrRobinson) work on my sasktel phone?

---------- Post added at 10:09 PM ---------- Previous post was at 10:04 PM ----------

Or would flashing that brick my phone? Knox has been tripped already so warranty doesn't matter to me.... Just don't want a brick.... Lol..... Im getting more adventurous now that it doesn't really matter hehe :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Night_1:
ok...so today i flashed sasktel stock rom (no root) with mobile odin pro....flash worked...wifi did not.....then i flashed with odin3 (on computer) same results (with md5 extension deleted)then tried bell version rom....md5 error....deleted the .md5 and voila...everything works....wifi included....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Night_1:
Having a bell Rom on my sasktel phone won't affect my phone plan will it? Everything will still go through sasktel right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Yes, it will go through your phone plan as long as you have a Sasktel sim in the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bcduma:
I've searched the forums and searched Google but was unable to find a clear answer to my question:

Can this or the actual stock firmware be flashed over the 4.3 OTA?

I'm currently running CM11 with the newest bootloader on Telus and wish to return to stock as I'll be selling the phone.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jrico2:
Yes, it can, as long as you don't go back below 4.3.

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

Or if do want to go back to previous versions, than you'll need to reload all files in your phone using ODIN: The PDA, PIT, BOOTLOADER, PHONE and CSC....

I've done it before, and it's not that quick process, also a risk of Bricking you phone is greatly high.

Hope this answers your question.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bcduma:
Thanks. I know of the high risk of bricking, I just wanted to know if it was possible. Thanks again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
It's possible if the stock firmware is actually available. Att hasn't released (last time i checked) firmware for MJB 4.3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
damn. this was what i was coming here to find out. i've been using cm10.2 for a while and i wanted to try 4.3 stock rooted. oh well. guess ill have to wait till the att leak.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] laptopdragon:
is this still current ?

the (best) way to root a samsumg Galaxy s3 (at&t version), is with Autoroot ?

just checking,

just bought this phone used, and am up to my neck in text atm.

any direct links is greatly appreciated.

thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AceTrader:
http://xdaforums.com/showthread.php?t=2538991
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eri000:
quick question

if i have flashed insecure boot image and renamed restore recovery files right now and i want to go back to stock rooted can i just flash this or do i need to do sth else first ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GAPY427:
I'm trying to fix my soft-bricked AT&T SGS3. Previously, I was trying to flash CM11 ROM to my phone via TWRP. After I flashed the TWRP, my phone would boot into recovery, but there would be a blank screen. So, I found your XDA thread and used ODIN to flash a new AT&T stock ROM. It passed ODIN, but I'm stuck at the SAMSUNG logo. Should I just wait for the phone to completely boot up, or have I done something wrong? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eri000:
boot recovery and wipe data/factory reset and wipe cache :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] artbybart:
Downgrading from 4.3 to 4.1.1

Hello,

This is my current setup running stock:

Carrier = AT&T

Android = 4.3

Baseband = I747UCUEMJB

Build Number = JSS15J.I747UCUEMJB

I'm trying to get the phone rooted and it seems that this is the way to go. However, I only see version 4.1.1 for at&t.

If I follow the instructions in the OP, I should expect to be on 4.1.1 stock rooted ROM without tripping counters etc.?

Thanks for the help!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bhiga:
You CANNOT downgrade from 4.3 - it will BRICK your phone.

This thread has root instructions for ATT 4.3:

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

I rooted successfully using method 2 there, but be aware it WILL trip the warranty status.

Sent from a device with no keyboard. Please forgive typos, they may not be my own.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ariesdroid:
flash stock rooted rom in recovery??

Hey guys...does anyone know if a stock rooted flashable zip exists for the sasktel i747m (baseband mf1) I want to flash a stock rooted jb 4.1.2 zip in cwm recovery to avoid the whole odin process...does a cwm flashable zip exist for the sasktel variant ??Ive searched and came up empty handed...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xxsxx:
Everything went fine here. Easy to do and I have my favorite root level apps back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Latty:
Looking forward to a Telus version of this "No Tripping Flash Counter" root :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PMad:
I used V3. When i saw it, i remembered reading that everyone was using V2 and it was from the Sprint version, so i wanted to make sure V3 was compatible because 2 wasnt on that site. Found that it was working and used it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sinichi21:
So after waiting for this root method I finally got my phone root without tripping the flash counter :D. I just have one question about the CWM recovery if ever I want to go back to stock recovery will I just pull off the recovery.img from the stock_root67.tar and do the 3rd instruction on the op will go back to stock recovery? or do i have to flash the stock firmware from samsung to get back the stock recovery
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scotteb:
Root or Not?

Just got a quick question, thread says at&t variant, I have Bell which is I747m, being the same as the at&t version as far as i know, can use this root method as well. Only asking because I remember back to the Atrix days when the US version was diff than the Canadian version, also the same for the galaxy nexus.

This maybe the wrong section for post but, its under the root Thread, any input would be helpful thanks. Need root back!!! lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
either will work. dd'ing it prob simpler.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
There is a stickied thread just for Odin. I don't want to dupe that here. The first time I mention Odin now I created a link to that thread. Hopefully that shall suffice.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lensgrabber:
Also found out if you have LBE Privacy Guard autostart enabled it also shows as modified. It's a toggle switch so easy to turn on and off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] robstunner:
I don't think anyone answered this? Just because I'm too lazy to setup my phone again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Only wipes /system. Data stays intact (at least for me it did).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
Actually I've got LBE Privacy Guard and didn't have any issue with the modified tag.

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

Actually this method is ROM specific, so if you were to flash this you "may" be rooted, but you would end up with an AT&T specific UCALEM system and lose all the Bell customization.

Not sure what specific items that are in the Bell code, and if you needed to return to stock you'd be out of luck until someone posts the leak of the Bell firmware.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheWyzeMan:
Has anyone been able to successfully send an mms after flashing this ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
Yep, just sent a test one to my wife's iphone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KappaG9:
Anyone else hold their breath while using odin? 0.o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
no...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] robstunner:
So I won't need to reinstall apps and setting?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caveman999:
Correct, all of m my data and settings were left alone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KappaG9:
Everything went smooth, thanks for this mrRobinson!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheWyzeMan:
Hmm. Can someone posted their AT&T apn settings for me, por favor?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Krynn!:
Ok, did some more testing, and I've got it narrowed down to Busybox from stericson (shows up as "Busybox" in the store, and as "Busybox Free" once installed). First thing I did was reflash stock_root67, then install Clockwork recovery v3, then the tethering patch. Checked the system status, it showed normal. I tried installing busybox to /system/bin, rebooted, and the system showed modified. I checked /system to make sure it was mounted ro, which it was. Uninstalled busybox (not the app), and it switched back to normal. Reinstalled it to /system/xbin and rebooted, and it's back to modified. Uninstalled it again (had to remove /system/xbin/busybox by hand for some reason) and rebooted, and it's back to normal.

One thing I did notice: If you install busybox and do not reboot, the system status still says normal. I don't know if the system periodically scans for changes, but it does do it every time after a boot.

So if you've installed Busybox Free from stericson, rebooted, and your system still shows normal... Well, the only other thing I can guess is that it might be the path that you installed the busybox binary to? Although when I try it to any custom path the install fails. Other than that, I'm out of ideas.

Of course, I don't see that any of this really matters... if I'm going to be doing anything with the system where having the device appear unmodified matters, I'll be re-flashing to stock anyway. I'm just curious as to why something triggers the switch on mine and not on someone else's.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HiKsFiles:
Is the current Bell 4.3 image still having the WiFi issue or is it safe to flash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shoryuken_2020:
I've flashed the Bell 4.3 on a couple of phone without a glitch. On a side note. Wifi and all working great. If you haven't unlocked your phone yet with the free method do that before flashing 4.3. I learned that the hard way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HiKsFiles:
Cool, thanks! :)

On a side note too, unlocking the phone was the second thing I did to it... first one being to root it! ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ozzman54:
Hey guys,

Seems like I'll be OK on this, but wanted to ask just in case. I am currently running CM10.2 on my AT&T S3. I never installed the 4.3 OTA, so I am still on the 747UCDMG2 bootloader. Will I be in the clear using ODIN to get back to stock with the I747UCDLK3 (JB 4.1.1) image in this thread? http://xdaforums.com/showthread.php?t=1739426

Thanks for the help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
You are good to proceed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bass_me:
I was in the same position as you are except I was on CM11. I just used the rooted stock recovery AT&T image and ODIN and was fine. I then used TB to freeze the OTA updater as I didn't want the OTA. I did however do a wipe data/factory reset prior to going back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ozzman54:
Thanks. I'll give it a go!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bass_me:
as long as you're still on stock jelly bean boot loaders you should be okay with flashing any other jelly bean based rom. That said there is always a possibility that something can go wrong.

So I'd suggest doing a nandroid backup of your current ROM from recovery to an external SD card prior to flashing just in case.

Good luck
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] witchcraftz:
I installed the Samsung drivers, set the phone to USB debugging, went into download mode.

Then plugged the phone in and waited for the drivers to load.

Then loaded Odin, went to PDA and loaded the file for Fido.

The check sum came back okay.

I clicked start and then:

<ID:0/006> Odin v.3 engine (ID:6)..

<ID:0/006> File analysis..

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

<ID:0/006> Get PIT for mapping..

<ID:0/006> Firmware update start..

<ID:0/006> sbl2.mbn

<ID:0/006> NAND Write Start!!

<ID:0/006> sbl3.mbn

<ID:0/006> aboot.mbn

<ID:0/006> FAIL! (Auth)

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

<ID:0/006> Removed!!

I've tried the process a dozen times with the exact same result.

On regular boot the phone goes to a screen with "Firmware upgrade encountered issue - please select recovery mode in Kies & try again"

Kies says it can't communicate with the phone and can't get into recovery mode to do a hard reset so for now it's bricked.

Help?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Try rebooting the computer. Pull the battery on the phone. Start over.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] witchcraftz:
Uninstalled Kies

Restarted the PC

Pulled out the phone battery for 24h.

Installed the latest drivers from Samsung

Ran ODIN as Administrator

Same error on ODIN as before.

Phone says:

SV REV CHECK FAIL : Fused 1 > Binary 0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
I'm not sure. After you get the message that it's installing drivers in dl mode, did you reboot phone and computer?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] witchcraftz:
Yes. I have tried rebooting both phone and computer a couple of times.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
Have you tried a different computer? Might be something iffy going on with the one you're using.

If you get the same issue with another computer, chances are it's something with the phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Have you verified you are attempting to use the proper firmware package for your device?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] witchcraftz:
I tried to use a different computer but I got the same result.

I am using the correct image (I am on Fido)

Update: I went and downloaded the custom ClockWork Recovery CWM-Recovery-LTE-SGS3-V5.Tar.Md5 (http://d-h.st/am8)

Flashing this file with ODIN did work

I am able to enter recovery now by pressing volume up + menu

Should I try putting TeamEpic-Root-From-Recovery-V5.Zip (http://d-h.st/Gax) and flashing from my SD card?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bass_me:
Fused 1 ?? Were you on 4.3 with KNOX bootloaders and now trying to downgrade? If so that can be an issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] witchcraftz:
I am on 4.3 with Stock Rom, I haven't done any modifications until this.

UPDATE: In recovery>choose zip from sd card> install zip> I ran the TeamEpic-Root-From-Recovery-V5.Zip

The root worked.

I then did a factory wipe from recovery. The wipe worked and my phone has rebooted.

Everything is working again. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bass_me:
Glad that worked. I think your original problem was that you were on a stock 4.3 ROM which I'm pretty sure has KNOX enabled. If you try to downgrade to an earlier JB ROM without KNOX the phone will bootloop or fail flashing. Which in turn sets the "fuse" counter to 1. Binary stays at 0 until you load a custom recovery or custom ROM. Then the binary counter will increment upwards each time you flash custom. Take a look in your device status and see what it says under SELinux status. Does it say "enforcing"? If so your device has KNOX installed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] witchcraftz:
You are correct, I read up and apparently all Canadian 4.3 stock roms have Knox.

The interesting part is that the factory wipe did nothing of the sort, all my apps, settings, lock screen, background, etc are still there. However it did fix the bootup issue.

Now to figure out how to root with knox...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
SeLinux and Knox are separate of each other. Knox is a Samsung thing, SeLinux is an android thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bass_me:
Thanks for the correction
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] marioperez:
root TWRP

hi i installed the image file for telus and now i get root acces but ive installed many version os twrp and cwm and it ask for pswd and does not mount sd card, and when selecting reboot it says no os installed but if i reboot everything is normal...i just cannot install anything via recovery...please help anyone!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mirrored:
How come there are 4.3 imgs for every carrier besides ATT?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bhiga:
I believe it as mentioned before that it's because there is no full image released.

-= this post enhanced with bonus mobile typos =-
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xCAVEMANx:
There is an Odin flashable 4.3 for AT&T....just not in this thread. I have used it to recover a bricked AT&T GS3 and have used it to upgrade and root. Search the forums. It requires Odin 3.09.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bhiga:
Found it thanks!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] horga_83:
Anyone have a Telus image root66_TLS_I747MVLUEND2.7z yet?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ali7000:
Try installing TWRP again, from GOOManager this time. It will flash the correct recovery. You probably have the wrong recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mukesh_thiru:
Help!

I upgraded to 4.4 and I tried to Root the phone with the steps.

I have a rogers version of the phone.

When I followed the step and tried to root, I got error in the ODIN. I see error "SW REV CHECK FAIL " FUSED 2 > BINARY 1"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
That's because you tried to flash an older build than what you currently have. As of 4.3 you can no longer flash older firmware. Only the same or newer as your current build. I haven't looked, but im betting he hasn't released a root66 build for kk. Unless you have the I747M on NF2 firmware, Towelroot is an easier and safer method of gaining root. Because of this, I dont believe he is planning on releasing a root66 build for those. He may do one for the NF2 firmware though. But I cant speak for him on that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Scyzor:
use Towelroot - works fine with 4.4.2 OTA
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naveenii1991:
worked perfect,thanks so much

only problem was I got stuck with samsung logo after restart

go to recovery mode >> do factory reset >>> done

:laugh::good::)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatkabab:
Anyone know where I can get the root66_ATT_I747UCDLK3.7z in a .zip format to be flashed from recovery? I can't plug my phone into the computer anymore, the port isn't reliable...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Root66 is firmware only. There is no recovery flashable version of it. Im sure there's a stock rom around somewhere though. Alternatively, if you are rooted, and trying to restore what you currently have (not updating), you can use Mobile Odin. Don't use this if you are wanting to fully update your firmware though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mukesh_thiru:
KitKat Rogers Rooted System image

Will there be a Rogers rooted system image for Android 4.4 ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
If Rogers was one that got the 2nd kk update, maybe. But if its on the NE6 firmware, just use Towelroot instead.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I think the latest s3 kk update is NF4 released in July for Canada rogers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mukesh_thiru:
I installed Towelroot and I got a message that "Your phone is not supported"

---------- Post added at 07:34 AM ---------- Previous post was at 07:32 AM ----------

I installed towelroot, I get the message " This phone isn't currently supported"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Then use cf-autoroot. Or just flash the SuperSU update zip with recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] droideastcoast:
can someone pls re-upload "root66.stock_Telus_I747MVLALH1.7z" please and thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Mirror 1 is working.