yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] creepyncrawly:
UCLE5 Stock ICS plus Root for SGS II.

And again, thanks for the help, especially linking the posts you used in the OP. Those were recipes, you know, type this, then type this, then do this...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Oh sweet. good job.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
I'm at work now, so I don't have ADB on this laptop. I've already done the ODIN part last night, and I'd like to flash CWM v4 on there now. This is my first Samsung phone, so forgive my ignorance here :)

Can I flash the recovery.img through Terminal Emulator, and if so, will it increase the flash counter since it's not in CWM(or is that just for ODIN)?

What would the Terminal Emulator commands be to flash through the phone (if it's possible)?

Would this work:

su

dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] altitude909:
Yup. That's how i did it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
Thanks, I appreciate it. I'd thank you if I hadn't used my 8 already. I'll go flash it now with terminal emulator, I feel naked with a stock recovery...

Edit: Worked! Thanks again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bravomail:
Thanks!

Worked for me with Odin 3.04 running as Administrator. :)

Odin 3.07 did not work. :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
That's odd, I just used 3.07 without any issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
If you have problems flashing with ODIN, sometimes try switching USB ports or even cables. ODIN seems to be particularly picky about these things and sometimes can be as simple as switching one of those (that and doublechecking the source file is intact)

---------- Post added at 01:40 PM ---------- Previous post was at 01:38 PM ----------

Cool - congrats on the ROM release! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] creepyncrawly:
And thanks for your advice as well. I wound up with the latest Ubuntu 12.04 running in virtualbox. Very slick and easy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jirv311:
Disregard.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
you mean UCALEM? you'll be fine just running the method...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jirv311:
Oh eff me. Yes. Sorry, disregard. I was looking at the baseband version. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
just making sure there isn't a different s/w version floating around...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jirv311:
No, I just bailed from Samsung and went on the HTC thing for the last 6 months so just getting reacquainted. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Uss_Defiant:
Hey guys,

I've got a bell version and I understand that I cant use this without having my phone look like its from ATT....

Is there a Bell firmware that has been rooted to use instead of the ATT version? Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Bell is CDMA carrier... You wouldnt even be able to use the ATT version because it's GSM firmware... unfortunately no, there isn't a rooted Bell version that can be flashed with this method... is there an official bell firmware available? That's what would be needed to create a rooted odin rom, that maintains samsung's signature, which is what has been done here...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Uss_Defiant:
Thanks for the response. Bell finally moved from CDMA to GSM about 2-3 years ago, so hardware wise, it seems like the ATT SGS3 == Rogers == Bell.

I have not found a flashable bell firmware, however I do have the bell phone, so perhaps a system dump from my phone can be used to create a stock bell rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
No, to not trip the flash count, it would have to be a taken apart and rebuilt version released from Samsung, which means a stock Bell version from Samsung is needed... Sorry for the misinformation... according to this chart it's the same phone....So this would work for you... It will look like an ATT phone but isn't the point of root and custom recovery to load a custom ROM? Then it will be as debranded as the custom ROMs currently are... What is your S/W and Baseband versions? It should be at least the same baseband as the ATT models...

---------- Post added at 08:57 PM ---------- Previous post was at 08:53 PM ----------

Take a look at this thread:

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

Before you do anything, they may need a system dump from you for development...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sicwan:
has anyone figured out a way to install busybox with out having the status set to "modified"?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
not to my knowledge and i'm not sure the motivation behind trying. if you need to return phone you just flash back to stock and it goes back to normal. if you haven't tripped the download mode counter then you'd be all set.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
Not sure if there was a difference between 66 and 67 other than you redoing compression, but I swear my email app was all black on 66. When I flashed the newer 67 with ODIN, my email app is white/gray. Is there a setting for a light/dark theme or was it a different email apk?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sicwan:
ok. thanks for the reply!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Uss_Defiant:
Thanks, i posted in that thread. The reason why I'm hesitant to flash now is that should i need to return the phone, it would need to have the stock bell rom on it, which I believe there's no way to get currently.

Plz correct me if I'm wrong though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Currently it's only AT&T, T-Mobile, and Sprint official ROMs that are available...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bird333:
I installed root and CWM. Thanks for the great work!

Questions:

1. I installled Rom Manager and it doesn't recognize that the CWM recovery is on the phone. Can I install the recovery from Rom Manager over the top of the first recovery without tripping the counter?

2. Newb question. How do you exit 'Download mode' with installing anything?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
1. Please don't use rom manager. Nothing good can come from it. Don't think it even works on our phones.

2. I just pull battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] posthold:
2. You can also just hold the power button for about 10 seconds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spdapimp217:
Everything worked like a charm. I couldn't even wait a day to root and put CWM recovery, also had to get the bloat off. I was also able to flash the tether and cell standby fix in CWM. Everything is still running smoothly. Thanks for all your hard work!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the1stSecond:
Did the cell standby fix trip the counter or change device status to modified?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
I am going on a serious hunt for a stock.tar rogers file as I really want root without tripping the flash counter. I will get this to you guys as soon as I find it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
My device status was normal..or whatever it said. Im not sure when but it changed to modified. I dont have any of those fixes or anything installed. Seems like it happened after a reboot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Uss_Defiant:
If you find a Bell/Tellus, let us know too!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dbzgod:
Bell, Telus and Rogers firmwares are not yet on Samsungs Kies servers but they should be soon hopfully this week.

Sent from my SGH-I747M
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mpazevedo:
Ahh, ROM Manager. That is something that should be posted somewhere on the Samsung Galaxy forums. You are asking to mess up your phone with that program. That app did not work well with the Galaxy S 2 at least the AT&T version, and I'm thinking it will not work well with the S3 also. Though it might look like its working it doesn't even know that CWM is already installed. There are other folks that can explain it better but I would stay clear of ROM manager and just use CWM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Uss_Defiant:
Thx for the info, but is the source reliable? Also, does that mean we can flash the ATT version listed here to root, then go back to stock firmwares, all without tripping the counter?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EugeneR:
A bunch of thanks to mrRobinson for this root! Applied without any issues. Only question is: what's wrong with applying Epic team CWM recovery tar file directly via Odin? Why one needs to extract recovery.img from it and dd it manually? Any difference?

Thanks again for great job!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] N1ESE:
mrRobinson. thank you for this. My phone arrived here at 1pm. It is now 2:50pm and I am successfully rooted using this and Odin 3.07. Time for CWM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Mr Robinson. Anyway you can make a compatible aroma that works with the gs3? I tried using the one you made for the gs2.boots fine but it didn't change a thing. I just want some inverted apps :D

Mms and Gmail. Tired of the white. It's so bright...

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dbzgod:
Ive been checking the samsung servers everyday a few times a day since launch. As for it being released soon, no source just going on the fact that for recovery purposes through Kies software samsung requires the carriers firmware to be on there and given the fact that the US firmwares were up a few days after launch we should be having our Canadian ones too. Its just a waiting game atm so hopfully this week they will be avaliable.

Sent from my SGH-I747M
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
if you flash that recovery via odin you will increment your flash counter. for those that don't care about incrementing the counter then it could be easier to just flash that then superuser and call it a day.

:eek: don't use that man. i specifically mount / wipe etc for the gs2 in there...

I haven't even officially switched to the gs3 yet. when i do i guess i can throw together an aroma for a few extras like inverted apps or some mods if the orig author lets me. Maybe this weekend.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] creepyncrawly:
What do you mean by "samsung servers"? You must mean samsung updates, or is there some site I am unaware of?

By the way, if MrRobinson is busy, I could cook up your rooted tar. You'd have to test it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dbzgod:
No not a website but Samsungs kies servers which hold all the firmwares for all there phones.

Sent from my SGH-I747M
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
Samsung FUS servers (Kies source), but the recent treasure trove of leaks were posted recently at samsung-updates.com (which presumably gets their firmware from FUS).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
True, but i747 firmware for Rogers, Bell & Telus are not there either.

I have looked everywhere and cannot find stock firmwares for the Canadian I747 variants. I am hoping a leak surfaces or we will just have to wait for the carriers/samsung to make these available.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] creepyncrawly:
Correct me if I'm wrong, but wouldn't the Telus version be a varriant of the T999?

How do you check the server, by connecting your phone to kies?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
Nope. T999 are Mobilicity, Wind, Videotron & T-mobile.

Rogers, Bell, Telus, Sasktel & AT&T are I747.

This post is very helpful in sorting out this mayhem: http://xdaforums.com/showpost.php?p=27938452&postcount=2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] creepyncrawly:
I just wondered, because the Telus SGS II is SGH-T989D.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dbzgod:
I just had another person ask me how 2 days ago, my post here http://xdaforums.com/showthread.php?p=28152978#post28152978 I explained how its works and give an example on how you can manually check it. The GUI version of the software has a drop down menu that lets you select firmwares by model and carrier, but when something is new the program doesn't have the information in their list yet to do that, so you half to do it manually.

This is how websites like samsung-updates check and get the firmwares in the first place. It is also how twitter feeds like the ones Rizdroid has setup works in conjuntion with a automated script to keep checking all and new firmwares so everyone gets updated ASAP when new ones come out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MallCop:
Worked like a charm! Rooted in ten minutes!

I'll be waiting until CWM is a little more stable, then I'll be taking care of that

EDIT:

On restart, entering download mode I have the following:

ODIN MODE

Product Name: SGH-I747

Custom Binary Download: No

Current Binary: Samsung Official

System Status: Official

Qualcomm secureboot: Enable

Just confirming the info for those who want to make sure that this method doesn't trip the counter...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gnash.s:
+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bird333:
Can someone explain what actions actually trip the counter? For example, does deleting certain AT&T/Samsumg apps ever trigger it? Is it truly known at this point what does it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Only flashing unofficial images in download mode trip it. Nothing you do with your apps thereafter will harm that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anethema:
I'm told though stuff like getting busybox on there etc will trip it.

Hopefully someone just finds a way to pwn the bootloader and not worry about it anymore haha. Really puts a damper on tryin to mod.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
No. that will change device status in the "About" screen to modified. And that is no worry as if you flash back to stock that will go back to normal. Whereas if you trip the flash counter, going back to stock does not reduce it. We'd need a mod/hack etc to reset flash counter which doesn't exist yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bird333:
So what about mods applied through CWM? I just want to get this straight in my head.

1. Only unofficial images in download mode trip the counter.

2. Mods applied through CWM or done in the phone could change the 'device status' to modified, but 'modified' isn't permanent.

Correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
There are two things people are referring to:

1. The binary flash counter - which is the counter that exists when you enter download mode. This is tripped by flashing unsigned code to your phone via Odin or other methods (other than the root in this thread). Once you follow the instructions to root and get CWM in this thread, flashing further items via CWM or installation (like busybox) from the Play store should not affect the counter.

*At this time, once you trip this counter there is no known way at this time to reset it*

2. There is another area called "Device Status" which can be found by navigating to Settings > About Phone > Status > scroll to the bottom. At this time messing with different things seems to change this value to 'Modified' such as installing Busybox or LBE, or making other changes.

*I personally am not too concerned about this one because flashing the stock ROMs posted in the sticky will revert you back to stock (recovery and all) and revert this device status back to the original state if you need to return your phone, sell it, etc.

Hope this helps.

---------- Post added at 08:12 AM ---------- Previous post was at 08:08 AM ----------

You got it. For item #1 unless someone specifically says "Doesn't trip counter" I personally wouldn't flash anything through Odin (or Heimdall when it's compatible) to be on the safe side.

For item #2, once you follow the root and CWM install routine in this thread, further flashes through CWM (and probably Mobile Odin if/when it becomes compatible) and ADB/Terminal command lines should leave the Download counter alone - but may mess with the device status - which as stated before is easily reverted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bird333:
Good to hear! Time to start removing some AT&T and Samsung apps. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moedin:
I don't really follow here, I am trying to figure out what the deal is with the AT&T vs Canadian variants, besides the M at the end ... what would happen if I tried to apply this procedure to root my device?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
You would have a rooted phone with AT&T software on it... but the ability to load a custom ROM... No way to go back to your carriers stock firmware until it surfaces...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moedin:
thank you for the quick and informative reply!

If I made a backup using the current stock recovery would that allow me to revert back?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
It's not possible to make a backup with the stock 3e recovery, it's only for flashing OTA updates... who is your carrier? This thread may need a system dump from you...

There's only 2 ways to go back to stock... Having the official firmware from Samsung or the carrier to be completely stock, or having a CWM rooted stock flash for your carrier, which has only been made for AT&T so far, and you'd still be rooted with CWM... or of course an nandroid you'll eventually make...

---------- Post added at 04:15 PM ---------- Previous post was at 04:08 PM ----------

ATM, you're only way to have a stock nandroid would be to trip the flash count using the other root method...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drawde40599:
Installing busy box 100% changes the normal to modified . Trio counter all good tho; )
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 420SYN:
Has anyone tried this on rogers or Canadian version?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Read and search, please - it's even discussed on this page.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 420SYN:
ya I saw that I just wanted confirmation from someone who did it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RTBee:
So just for clarification, if I don't want to trip the counter, the only way to flash CWM is with the adb method? :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
yes or with a terminal emulator right on your phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RTBee:
Thanks! The rooting was going quite smooth when for some unknown reason my computer shut down, as in completely turned off at exactly half way thru the process. I held my breath as I rebooted,started Odin back up and then started the process again. Good way to acquire a paperweight. So I'm being a bit cautious now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anethema:
Didn't work :(

Telus phone here, 747M.

Odin fails, the phone shows 'secure check fail: aboot' in the download mode screen.

This is Odin's output:

<ID:0/003> Added!!

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

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

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

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

<ID:0/003> aboot.mbn

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

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

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

I read the instructions quite a few times but cannot find where I went wrong.

Thanks for your help guys.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Latty:
You can't use this method with the Telus SIII, because it's a UCALEM-specific flash.

You have to use the root method as listed here: http://xdaforums.com/showthread.php?t=1726960

Yes, it'll increment your flash counter, but that's the only method to root the Canadian phones at this point in time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anethema:
Thanks Latty. The previous posts right near yours indicated it would work just fine you'd just end up with the ATT software.

So in reality, it just simply will refuse to flash and thats that on anything but an ATT phone.

EDIT: The applicable quotes:

So yes, this is not the case, apparently it just refuses to flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Voicebox:
I don't know if this version will work on your phone or not, but I got that same fail when I tried, and I mean it stopped with aboot also. Minutes later it would finally fail. Tried different USB, diff computer, one XP and one Win 7, Odin 3.04, 3.07. Ended up being the cable. Switched out and then went through first try.

I have ATT version of phone though so no compatibility issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 420SYN:
Hey Mr. Robinson, looks like Rogers/Bell/Telus officials are out in the general section. Will you now be working your magic for us?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] creepyncrawly:
I think MrRobinson probably has to work today.

I can work on these today. Downloading all three now. My internet connection is pretty slow, and then the actual work will take some time, but should have something ready before the end of the day.

@MrRobinson, let me know if you would rather work on this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
Thanks man, that is very much appreciated!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 420SYN:
Aren't they all identical?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
No, different branding. Also att doesn't have option to toggle lte.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
I can bang these out fast at work. Esp without spending the time to test them since i can't ;)

I'll upload the initial images, if there are issues etc. please step in as I won't have time to troubleshoot continually. As always I'll also only have them on a temp download location so some extremely kind person will have to host longer term.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anethema:
My telus phone has not branding at all either in software or in hardware that I can tell. Do the others?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
Thanks for this! Are you able to post md5's for the images?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anethema:
Depending on what kind of bandwidth it needs I could prob throw a mirror up, and do some testing for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
I think I had the same problem - but luckily it worked another time. All other operations with my cable are fine, and the odin instructions say the #1 reason for bad flash is a bad cable - so I assume mine is 'iffy' (and I tried two). Is there a way to 'test' the cable first to make sure it will work besides messing with terminal processes??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] csingh:
Can anyone confirm this working with Rogers?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Geezer000:
Worked for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RTBee:
Download mode

I have a question, maybe a little bit off topic. I successfully rooted my phone then used terminal emulator on my phone to flash CWM - successfully!, just like MrR suggested...

Here is output of what I did (using v4):

Code:

shell@android:/ $ su

shell@android:/ # dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18

13992+0 records in

13992+0 records out

7163904 bytes transferred in 1.672 secs (4284631 bytes/sec)

shell@android:/ # reboot recovery

I'm not real familiar with Terminal Emulator and my question is, on the last line I typed 'reboot recovery' which did exactly that. If I were to type 'reboot download' would that boot it into download mode (should I ever need to start over)?