yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
Rooted my Telus S3 using the method in the OP, running 4.1.1 and my flash counter is still 0. Yay!

Now, is there a way to get TWRP or CWM recovery on to the phone without incrementing the flash counter?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
If you are on jb already I believe you will trip the flash counter no matter which method you use to flash a custom recovery. From what I've read, mobile Odin from the play store will not trip the counter though.

I am not sure how well mobile Odin works though as it only has a few reviews on the play store from gs3 users.

Might I add that if you do trip the counter, you can buy triangle away from the play store to reset the counter to 0.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mjt143:
I have an ATT at 4.0.4 do I use ATT I747UCALG1 (ICS 4.0.4) with Odin or I747UCDLK3 (JB 4.1.1) ?

Thanks Mike
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
FYI I flashed TWRP using Mobile Odin and upon loading TWRP recovery it did indeed trip the counter, so it was 1. Triangle Away resets it to 0 but every time I go into TWRP it goes back to 1. No big deal; if I need warranty then Triangle Away will save the day.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cnewsgrp:
Thanks. I was under the impression based on few earlier posts that mobile odin will not trip the flash counter.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fookolt:
Just had to use Odin to get back to stock and it's taking a long time (like 5 minutes) to boot. I'm stuck at the black screen that just says "Samsung" and has the notification LED go from light blue to dark blue.

I think the only thing I did differently this time is that I previously had a 4.2 ROM on there and I flashed back to 4.0.4 (since that's the stock Odin package I had lying around).

Could that be causing this really long first boot? I haven't gotten past the Samsung screen yet.

Figured it out: I had to fully wipe the phone in recovery before doing Odin.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
I uploaded the PCT (Puerto Rico) variant for anyone using that...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] filipinowise:
Cool... But you will run into problems when trying to flash AOKP or CM Roms.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skatin707:
I never had a problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbogdann:
Can you make a rooted Koodo ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vanisleguy1976:
Since Koodo is a subsidiary of Telus, I would imagine it's the same hardware variant as AT&T/Rogers/Bell, etc.

Before you go and root, have a look in settings > about device and report back what you see there!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
If your phone is an SGH-i747m then just grab the rooted TELUS image, remove the TELUS apps and install the Koodo ones. I did that w/the Rogers image. Went from Bell to Fido. Removed the rooted Bell image, stuck the rooted Rogers image on it. Removed the rogers apps and installed the Fido ones.

Now I'm waiting on the rooted 4.1.2 images...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Or just use the root66_KDO image... :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
I missed that one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] urtruelove78:
I followed this guide successfuly before and root and everything worked.

I tried on other phone same steps and no matter what, root was not sticking to it.

Have to odin to lg1 and back to jb, few times. No dice.

Finally, I tried clearing wipe and cache when doing flash using mobile odin which I was not doing before. This time root sticked and showed up in flash counter reset app as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sahuja:
Excuse me if it has been asked (and answered) earlier, I was unable to search in the ocean of great work

Will this method "re-lock" the sim unlocked AT&T SGS3 (i747) ?

(a thank you in advance)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
No. Sim Unlock is not affected by rooting. I've flashed, god knows how many roms to my phone, and it's still unlocked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Uzi578:
So I just tried to flash my phone back to stock via Odin because the data on my LiquidSmooth ROM wasnt working.

I just flashed it twice and neither download worked. Everything is successful. But after the phone starts to reboot, it gets past the ATT image part, then Samsung pops up, and it just sits there indefinitely.

I have a USB gig. See if that helps. Not sure why I cant flash to stock...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
Boot in to the (stock) recovery, and perform a full wipe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Uzi578:
Thank you, it just booted up. Didnt need to flash it. TY again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
Not extracting correctly?

Forgive if this has been covered. After numerous searches I could not find the answer. I flashed JB from here w/ no issues. I am trying to revert back to ICS. However, every file I try to download and extract extracts ending in .tar vice .tar.md5. Am I missing something? I am using the most up to date version of 7 zip (not beta).

I am thinking I just have to add the ".md5" at the end. I don't want to do so until someone verifies. I don't want a bricked device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
I think on my ics versions I didn't do the md5 so you will just see the tar. No reason to use ics though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
I am reverting back to try and flash cwm without tripping counter. Going to do full factory wipe, install ics via odin, and then cwm.

Update: Thank you MrRobinson for your fantastic work and support. This goes for everyone who worked toward keeping the trip counters to 0. With the support of this forum I was able to revert to ICS, install CWM, then install the JB stock rooted from here via Mobile Odin. I did a nandroid and then proceeded to install CM10. And my flash counter has remained at 0. Of course with Triangle Away I was not too worried but I like having one less thing to worry about. I am now happily running CM10.0.0 after installing the 4.2 keyboard and camera.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chuckado:
I have rooted my at&t galaxy s 3 and now i would like to look into custom roms. It seems like the easy method is just to install rom manager from the play store. Is there anything that needs to be done after that or is there another guide which has the next steps after rom manager is installed? Thanks for any help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
First off, are you rooted AND do you have a custom recovery installed? You only mentioned rooted. You will need a custom recovery. There are several ways to install one. Rom Manager is one way to go about installing CWM. It did not work for me for installing CWM and I had to do it the terminal emulator way (which was no biggee because I have used terminal often enough). There are a lot of forum postings here at XDA that give the steps to install one so do some searching and reading until you are comfortable.

I could give you the step by step on how to install a rom, but this has been plastered everywhere here in XDA and numerous other forums. For your own sake, I would highly recommend you do some searching and a lot of reading before you start. Most of us have started this way as well. Worse case scenario is that you will actually learn some things along the way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Scyzor:
fixed...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mooshon:
how do i extrcact 7z file????
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
Use winrar
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
7Zip works better with extracting 7z files
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
After giving CM10 and AOKP a run, I am back over to the stock rom. While the battery life on the AOSP roms was not quite up to par with a stock debloated rom (at least not for me) I would have been content with it. However, one of my wants is the ability to switch to GSM only during most of the week because of poor 3G and LTE signals at my place of work. Could not get it to work with an AT&T SGS3 for GSM only and thanks to someone figuring out how to do a temp removal of RAT restrictions, I can do it on stock.

I can confirm this works. However it broke the ability to use some dialer codes such as *#*#4363#*#* and *#2263#. Tried several times and did factory resets to no avail. I ended up using ODIN to install fully (with stock recovery) because I need *#2263#.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Yea you'd want to flash the cache. That's where it's loading the csc and all those codes would work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
Ok. So I go through and flash ICS again (after doing factory reset), install custom recovery, and then mobile odin install JB stock with the EXCEPTION of recovery. Would flashing the cache cause the custom recovery to start tripping the flash counter if I were to get into it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
I'd have to take apart the files again and look. Not sure if you can flash cache without stock recovery. If i remember correctly the cache uses the stock recovery to flash those files that are signed. Let me look at it tmr and if i can grab the csc stuff to flash with a non stock recovery.

If i can do that you would follow the steps previously posted then flash the file i give you with your cwm/twrp.

that being said, if you don't need a non-stock recovery cause you are happy with rooted stock then we don't need to go down this road.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
No need to go down the road at all. Given the work it would take and I am probably one of a very few wanting what I do, it is just not worth asking you to put in the effort. I am perfectly good at the moment as is. I take functionality of what I want over looks and one of the functions I want is 2G only...which as stated earlier, full stock (with stock recovery) gives me the ability to do. If and when some AOSP roms solve the issue of switching preferred networks (and hopefully get the battery life a slight bit better) then it will no longer matter anyway as I prefer AOSP over TW and will switch.

If I get to the point that I want the 2G only capability and stock recovery, I will just have to give up a clean trip counter. Besides, that is why Triangle Away was created.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kal*El:
Can someone help me out on this one? I selected the 4.0.4 update for AT&T from page 1 of this thread and used ODIN to flash back to stock. ODIN appeared to do everything successfully.

I let the phone reboot per step 2 and now it just stays at the Samsung screen..:eek:

What do I need to do to clear that up so the phone boots up?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Boot to recovery and factory wipe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kal*El:
You know..... that is such a rookie mistake..LOL!! Thank you so much. I slapped myself after I saw your post.:laugh:

It worked like a charm! Thanks again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kal*El:
So I flashed back to stock ROM- Ever since then I'm noticing my S3 freezing and I have to press power to restart. This didn't happen before and now this freezing is to the point of annoying.

Is anyone else getting that issue? If so what fix is there? I'm flashing back to 4.0.4 ATT and then using Kies to update to see if that resolves the issue.

Is there a software update from Samsung that just wipes- no root- but installs as if its right from the factory???

Maybe flashing back to 4.0.4 and then updating via Kies will help.

Options? :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
You can download a stock (no root) firmware from here (free registration), then just use Odin to flash. Boot in to recovery and do a full wipe of everything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ehaze:
After rooting my phone, I'm not able to access the web.

Any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
Are you connected to a wireless network, or your cellular network?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ehaze:
I can access the web if wifi is turned on.

otherwise no.

able to make calls and send texts.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
You should check your APN settings. What carrier are you on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ehaze:
Weird.

APN is showing Cingular 410.

ATT is my provider.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
I'm trying to find the APN settings. What I'd also suggest doing, is removing any APN connections on your phone, and then selecting the "Reset defaults" option.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Check your EMEI. You probably lost it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ehaze:
IMEI is listed.

Mobile network state:

Disconnected

-----

My phone is showing a t-mobile model number. sgh-t999

this gets even more fun!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
're flash. Check to make sure your download is not corrupt
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
You sure you didn't accidentally download the tmobile root66?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ehaze:
no f-ing idea.

i downloaded the files from this thread.

currently building a VM so I can reflash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ehaze:
When I got to the office, my browser was open to the Tmobile subforum.

:eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kal*El:
Thanks for the advice :good: I tried my option first by flashing back to ICS and then the phone prompted for an update. I let the phone update, then root again, and so far so good.

I hope this helps anyone else that may be experiencing "freeze" issue with the S3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jsick:
So I flashed the Sasktel stock JB rom and have been using it for a few weeks, but there is something wrong...last night, out with friends who are on their stock S3 (they dont know what xda, rooting, etc is) ion Sasktel, I noticed their phone says LTE when connected to LTE, but mine says 4G.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fredrik949:
Odin not seeing phone

Trying to root stock ATT S3, but when I put phone in download mode and connect to computer Odin does not see the phone. Any suggestions?

I tried installing the latest drivers off Samsung website, they install but at the end it says there was a problem installing the following diver:

Intel Centrino Advance-N Wimax6250 Could that be the problem and if so any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] undergrad:
I keep getting stuck at tz.mbn

Im on virgin 4.1.1 using the bell root SGH-I747M.

right now its been over 25 min and im stuck at "tz.mbn"

Anyone dealt with this before?

I have kies installed but not running

I have the drivers installed

I want to try to uplug the phone restart it, but im worried it will brick it.

Any Ideas?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Yea try again. Reboot computer. You got past boot so you won't brick it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
NM. Found the answer while looking for something else.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GAPY427:
What do you do if you're stuck at the "SAMSUNG" screen after returning your rooted phone back to stock?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
Boot in to recovery, run a full wipe then reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
Whoa!!! This thread used to be a Sticky. What happened? Is it just me?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FlKTION:
I had a tough time finding it too. Can't wait for the new 4.1.2 Rogers root from Mr Robinson!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Just find it in the sticky roll up thread now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] badbambam:
JB 4.1.2

Any news on when we get 4.1.2? or 4.2 for that matter??

Thanks

BBB

Edit: Oh yeah, Bell SGH-i747M ver. here.

btw how do i get verified so I don't have to wait five minutes between posts??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imcol:
I am on tasks rom and wanted to go back to stock for a while. Any prerequisites before using Odin like formatting anything? Also If i just use Odin from a functioning phone now, does it automatically format everything?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
When changing ROMs, even when updating your current one, always,

ALWAYS

backup the contents of your phone. Just in case.

Other than that, just fire up Odin, pop your phone in to download mode, and flash away, after picking the right file of course. You'll loose your custom recovery, but the counter will still be tripped.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andy442:
Thanks mrRobinson, worked like a champ!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xXFl4sh:
I am so confused. Are the blue font names has a rooted system image injected into it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hiflyer29:
Yes, the one's listed in Post #1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sakdroid:
I followed the Procedure, I am getting Fail! in ODIN,

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> root66_ATT_I747UCDLK3.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

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

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

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

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

<ID:0/004> aboot.mbn

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

<ID:0/004> boot.img

<ID:0/004> cache.img.ext4

<ID:0/004> NON-HLOS.bin

<ID:0/004> recovery.img

<ID:0/004> rpm.mbn

<ID:0/004> sbl2.mbn

<ID:0/004> sbl3.mbn

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

<ID:0/004> __Xmit Write fail

<ID:0/004> XmitData Fail..

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

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

<ID:0/004> Removed!!

<ID:0/004> Added!!

Any help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Try my root method... Should work a lot easier and the files arent as big... Ur getting a write fail at system it seems. So odin stock and make sure u boot. Then try my method...

trolol and awayyy!! Expect typos this is my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sakdroid:
On Reboot i keep getting Firmware upgrade error and says connect to Kies to restore.

I tried Kies and used Force Recovery it didn't work.

I restarted everything including my Laptop and retried using ODIN and this time it worked.

I had this rooted earlier with this method and worked fine and since i need to replace LCD, I restored and removed root and send to Samsung for service.

Thanks for quick update.. I am now fine.. Not sure what exactly went wrong first time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Question...I have already used this method a long time ago when I first got the phone..so first off thanks! Im looking to go back to stock to hopefully resolve my LTE connection issues. Do I need to Odin back to total stock (not rooted) first and then use these steps again or can I just follow these steps and Odin stock with root injected? I hope that made sense
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Randomsanity:
Hi Guys,

Sorry for the noob question but I've already rooted a few months back using an older rom so I have CWD flashed already but I want to update to stock JB.. do I still need to follow this method to flash the rooted rom or should I be downloading something else and flashing from CWD?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
No you can start right with the root66 here. But if you are coming from a different rom base you want to factory reset.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
If you want just stock + rooted just flash the root66 here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Thanks..running 4.2 So I can just factory reset...and then just follow steps here again

Think phone was originally on LG1 but I assume Id be better of using the LK3 download..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Randomsanity:
Thanks, but is there a way to flash this through CDW or am I forced to use ODIN again? I just want to update my old stock rom + root to the new stock JB rom + root.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
The root66's must be flashed using ODIN. They will overwrite CWM with stock recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iwebsource:
Help

Hey guys,

I have a telus I747M SGS3 and I'm coming from stock.

I;ve downloaded Odin 3.07 and the telus stock rooted image. Extracted the .tar file and flashed it as usual (I have an SGS II).

This is the third time around now but everytime it seems to stick on the boot screen, the "Samsung" logo.

I've let it site for at least 15 - 20 minutes but nothing happens, same thing.

I hope I'm not screwed here.. What should I try here?

Is there a stock telus rom I can go back too??

Thanks guys
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
Boot in to recovery and perform a full wipe. Data and all cache. Then reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iwebsource:
Sorry for the noob question but how does one boot into recovery?

Tried holding down both up and down volumes when rebooting, also tried with the power button too but no luck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
What I do when it doesn't work right, is pull the battery for a few seconds. Put it back in and then you hold vol down + home and press power. When you see it power on, let go of power and when you see the Samsung logo let go of the other buttons.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
Vol down + home + power = download mode

Vol up + home + power = recovery
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
Oops, thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Longstreet:
Howdy all. Just got my S3 over the weekend, and have been playing with it in between reading about root. I’m about a quarter way through this thread, but still confused about custom recovery.

In the OP it says “Third, (optional) On JellyBean versions, flashing a custom recovery will trip your counter no matter the method used.”

But then at the end of the thread, it says “Thanks to pinoymutt for this: http://xdaforums.com/show...1&postcount=26

which is the method above to getting recovery in without tripping counter.”

So....will it or won’t it? And just which one of the methods discussed is pinoymutt’s “no trip” method for installing a custom recovery?

I’m pretty happy with my phone the way it is, and don’t plan on any custom roms (yet; that bug will bite again soon enough). I would like to have root so I can debloatify my S3, and run Tibo and a good recovery.

Thanks for any help you can give. I was pretty comfortable tinkering with my old Inspire, but things work a bit differently here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xCAVEMANx:
OTA update is being pushed to my AT&T phone!?!

An OTA is being pushed to my AT&T GS3 right now as I type...330 something MB. Any ideas? I was on LK3 root66 stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Maybe 4.1.2