yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] heybobitsme:
I've added everything that shows up when the phone is connected. When just powered on, it's Samsung T999, in dl mode it's Sasmung MSM8960. I'm probably going to have to try it with my wife's laptop.

Edit: I used my wife's laptop and it worked flawlessly. I need to do some more research on how to get it to work in VB. Thanks for putting up with me. :cool:
[T-Mobile, Samsung Galaxy SIII] SkeptiK21:
Im in a bit of a bind here. I have a bad flash any I am trying to get into ODIN to get a new OS on my phone. The problem is that my VOL UP button doesn't work. Only my vol down works. Therefore, when trying to get into download mode I can't because it requires me to push VOL UP to continue. Can someone help me regarding this? It's really a pain right now. Any help would be greatly appreciated. !
[T-Mobile, Samsung Galaxy SIII] Arhtard:
can you get into android at all? if you can, hopefully adb was enabled and you could open command prompt on your computer and type - adb reboot download - if you can't boot into android at all, i'm not sure what to do next, hopefully someone else has another suggestion. also do you have stock recovery or something like cwm installed?
[T-Mobile, Samsung Galaxy SIII] SkeptiK21:
Hey thanks for the help... but it seems that I was finally able to get into download mode. However, when I go to Odin and reflash an original rom when it goes to reboot for the first time it gets stuck on the samsung logo. I've tried several types and have also checked the md5 but no cigar. Do you know what it could be?
[T-Mobile, Samsung Galaxy SIII] Arhtard:
reboot into stock recovery and wipe data + cache - i think i remember someone saying this was the solution

just note, this will erase your user installed apps

edit: added quote from jovy23
[T-Mobile, Samsung Galaxy SIII] SkeptiK21:
It didn't work. I previously flashed a stock firmware using Odin that was not pre rooted. Will that erase my CWM? If so, then I am unable to get in using this method.
[T-Mobile, Samsung Galaxy SIII] LordPhong:
I have no problems with Windows 7 64bit and ODIN. I don't know if it makes a difference bit I did install the Android SDK with their drivers, I believe.

Sent from my Frosty Jellybean fingers.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes it. Will. You can get it back easily. Follow the steps bellow if you have not covered them already.

1. Restore to Original Stock (Make sure fully working as Factory)

2. Root the phone and then Flash SIYAH Kernel using either ODIN with Download mode or put the zip on SD Card and Flash in Recovery Mode.

3. Wipe Cache. Wipe Dalvik Cache.

4. Reboot. You will get Rooted phone with CWM. From then on you can get the ROM you want.

Replace ADB Drivers you installed with Samsung's own drivers and you should be all set.
[T-Mobile, Samsung Galaxy SIII] titaneds73:
you dont need a custom recovery to clear cache or data,after you finish with odin boot into stock recovery and clear cache and factory reset,but since your vol+ button doesnt work you cant boot manually into stock recovery unless you do it with adb,
[T-Mobile, Samsung Galaxy SIII] _MrAwesome_:
Mobilicity 4.1.1 or 4.1.2

Any clue when Mobilicity will get 4.1.1 or 4.1.2. Its been forever.
[T-Mobile, Samsung Galaxy SIII] Gil1957:
I followed the instructions, and after it reboots, after the android moves up, it seems to freeze on "Samsung". How long after that should the phone finish booting?

Thank you.

---------- Post added at 03:06 PM ---------- Previous post was at 02:39 PM ----------

Found it. Thank you for all the info
[T-Mobile, Samsung Galaxy SIII] Perseus:
I believe you have a Reset Button on the phone depending on model. I was under the impression that you are trying to get back to Factory Defaults so you can exchange....

---------- Post added at 09:19 AM ---------- Previous post was at 09:16 AM ----------

You were supposed to Clear Caches in the order given. Let me know if still issues.
[T-Mobile, Samsung Galaxy SIII] LoGiK915:
How did u go from ics to jb? Pc odin or mobile odin? I used mobile odin and my flash counter never went up either because mobile odin doesn't update all 10 partitions. I think it only does five. Once I did a full update using pc odin my flash counter went up really fast(I flash a lot).
[T-Mobile, Samsung Galaxy SIII] Perseus:
You are correct. Just to prove the point, I flashed CM10 on a Galaxy SII with PC ODIN. The counter went up. Then I made the Triangle go away and used Mobile ODIN for Resurrection Remix. No Counter Change.

P.S. I know I digress away from OP subject. So Mods please apologize for this..
[T-Mobile, Samsung Galaxy SIII] waste55:
newb question...couldn't seem to spot this.

With this method, does it flash and erase the stock image along with user settings, app data etc when using this rom with root injected in? Even if planning on just rooting and sticking with stock rom?

thanks!
[T-Mobile, Samsung Galaxy SIII] EhdisChris:
This flashes stock everything (image,recovery,etc) and injects root, with no negative effect to user data.
[T-Mobile, Samsung Galaxy SIII] Daguse:
Thank you!! Awesome job, still works today. :)
[T-Mobile, Samsung Galaxy SIII] _MrAwesome_:
Mobilicity Update Out

the Mobilicity update is out could you inject root into that?

I got it through Kies not the phone
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
Thanks OP. I'm getting my GS3 tomorrow, and this looks sick. I have a question however, maybe I missed it, not sure?

If I use this method, and then get CWM installed, can I use CWM to flash TWRP as a recovery, and then flash .zips and ROMs from TWRP without tripping the flash counter?

Thanks.

NVM : Answered above. Thanks.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
Updating Wind, Mobilicity, and Videotron to T999VVLDLL1 now.
[T-Mobile, Samsung Galaxy SIII] gypsy214:
I may be doing something wrong? The first time I downloaded the new jb from tmobile the file was 600mg and when I extracted the folder It gave me was empty, Then I downloaded it again and it was 90mg and the folder was empty too. By the way .7zip wont work. I used winrar
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
All JellyBean Canadian variant images are live in the OP.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Try via Kies if needed. Better yet, Check OTA from System > Software Update
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
for future reference, twrp will trip the counter. Go back to rooted stock rom thru odin and stock recovery and run triangleaway.

(If you need to RMA)
[T-Mobile, Samsung Galaxy SIII] inkemplete:
Should I be wiping cache/dalvik and factory reset before doing this? Im running frosty jb right now.
[T-Mobile, Samsung Galaxy SIII] Perseus:
I Don't think you need to. If you have funny errors or stuck at Samsung Logo then yes do at that time.

That's assuming you are not going to RMA or Want to Force back to Stock
[T-Mobile, Samsung Galaxy SIII] inkemplete:
What is RMA?
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
Return Merchandise Authorization. Typically is a number so you have an RMA number means you are returning the device and its been authorized.
[T-Mobile, Samsung Galaxy SIII] kashinc:
no more 4g or 3g

Hello,

I attempted to update to the new cm nightly and had some issues so I reflashed back to stock using this method. I have not been able to get my 3g or 4g running since. It is just stuck on the edge network. Does anyone know how to fix this??!?!?!

-kash
[T-Mobile, Samsung Galaxy SIII] Kryo_genik:
Now correct me if I am wrong here....

I am stock unmolested t-mo 4.1.1 jelly bean.

If I ODIN to the rooted rom my apps will stay put since I am not wiping any cache folders out correct?

I just hate redownloading all my crap and I am wanting to root.
[T-Mobile, Samsung Galaxy SIII] RaymondPJR:
Sounds like the IMEI bug. Read up about it. I'll see if I can find a link. http://xdaforums.com/showthread.php?t=1804123

To check if you've lost your IMEI, go to Settings>About phone>tap Status>scroll down to IMEI. If there is not a long number there, you've been hit. If that is so, go the the link. In the first post scroll down to "IMEI already corrupted" and follow those instructions in that part of the post.
[T-Mobile, Samsung Galaxy SIII] neysito:
That is correct, you will keep all your settings, apps, everything. The only things that will be added is root and the superSU app for superuser management.
[T-Mobile, Samsung Galaxy SIII] LordPhong:
Correct.

Sent from my Frosty Jellybean fingers.
[T-Mobile, Samsung Galaxy SIII] kashinc:
my dude good looks, I had to do the last part with his program... worked like a charm im back up and running!

Thanks Again
[T-Mobile, Samsung Galaxy SIII] WoodmanMN:
Yes. MrRobinson's root doesn't touch your data.
[T-Mobile, Samsung Galaxy SIII] RaymondPJR:
Ur Welcome!
[T-Mobile, Samsung Galaxy SIII] unk2009:
Looking forward to giving this a go... Coming from HTC One S..Thanks for your hard work. .

:cool:
[T-Mobile, Samsung Galaxy SIII] RaymondPJR:
I had to refer to this thread again as I had forgotten how to install the cwm image file I downloaded from their site. Thanks so much, MrRobinson!:)
[T-Mobile, Samsung Galaxy SIII] RaffieKol:
Can I downgrade???

Can I downgrade???

Since 4.1.1 will trip the counter if I flash CWM can I flash the Stock 4.0.4 then flash the CWM so I dont trip the counter ???

and if I do trip it is there a way to reset it on 4.1.1

Thanks

FOUND The answer.... Thanks
[T-Mobile, Samsung Galaxy SIII] elracing21:
Im having an issue. I searched the thread and saw one person had it before...

Anyway... I was already rooted and rocking a custom rom but When I went from ics to JB I dirty flashed all the way thru so things would randomly stop working after a while. I finally decided to use odin to get to stock jb and flash custom rm thru there. I followed instructions and once im in odin and I start the process Odin gets thru the first stages (boot, cache, image, recovery, etc.) but once it hits system it stops for about 15minutes then fails.

I tried re downloading the firmware and even odin just in case to no avail. I've tried 3 different times. I even tried a ics firmware and still fail. Now im stuck with my phone and no firmware.

I tried booting into recovery just to see if i can flash something thru there and it starts booting but turns into a bootloop... I'm still able to get into download mode so this is not a brick.

Any ideas what I can try here?
[T-Mobile, Samsung Galaxy SIII] LoopDoGG79:
Reinstall the drivers and make sure kies is not running in the background on your PC.
[T-Mobile, Samsung Galaxy SIII] elracing21:
Still no go. =/
[T-Mobile, Samsung Galaxy SIII] LoopDoGG79:
Try to odin flash CWM. Hopefully if out works, you can flash another ROM after that
[T-Mobile, Samsung Galaxy SIII] Ir0nsh007er:
Great tuto

Work fine for me.. No problem :victory:
[T-Mobile, Samsung Galaxy SIII] elracing21:
Thanks for trying to help. I tried that and it didn't work either. I started switching usb cables as I have like 6 of them all looking like the original one and only about 3-4 of them actually being original. On my 3rd cable it worked. I re tried with the others and had some fails and pass and weeded out the non original usb cables.

Again the problem was in the cable. I thought I was using the right one. Hope this issue helps others that try after me and again thanks!
[T-Mobile, Samsung Galaxy SIII] crossfx77:
Hi guys,

I had a successful root when I was on ICS. But I could not update to JB without reloading stock. Anyways I went through the process to root my JB 4.1.1 and odin gave me a "passed" but my tmobile galaxy s3 is not rooted. It shows "normal" status and i used SU checker and it says "su declined/not found" I also should note that the SU app did not load on the phone automatically after root attempt. I tested with titanium and it fails finding root as well. Any information as to why this might have happened would be useful. Thank you!

i only did the process up to the first section, I wanted a rooted stock for now.

Phone Tmo samsung galaxy s3 jb 4.1.1 stock.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
Can you boot to recovery and factory reset? that would prob fix whatever is wrong.
[T-Mobile, Samsung Galaxy SIII] kingoftheroad40:
Thanks.

Replaced my HTC G2 in Nov. with the T Mobile GS lll just got done rooting it used root 66 rooted stock rom Great job thanks for all the hard work so we can enjoy our phones even more.

Again thank you.:)
[T-Mobile, Samsung Galaxy SIII] tsuujin:
Why isn't this thread stickied? Very useful.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
Simply cause it is one option of many. Best if there is one stickied thread that covers all the ways to root with video tutorials maybe etc.

This way the number of sticky posts don't get out of hand.
[T-Mobile, Samsung Galaxy SIII] Ditamae:
New to the SGS3... this guide was simple and worked like a charm. Thanks for all your hard work!
[T-Mobile, Samsung Galaxy SIII] jake9891:
Any chance of putting ROMs as torrent? I can't download entire file at once :/ it keeps cutting my download half way
[T-Mobile, Samsung Galaxy SIII] anteko:
How long is this supposed to take? I've been sitting here with it connected to my phone for 15 minutes and it still says "Downloading... Do not turn off target!!!".
[T-Mobile, Samsung Galaxy SIII] cuzmonote:
what does it say on your computer ???
[T-Mobile, Samsung Galaxy SIII] Ditamae:
It took me approximately 12 minutes... or so... you should be able to see the progress on your PC.
[T-Mobile, Samsung Galaxy SIII] jay661972:
Mrrobinson i will use your rte66 next week. Im getting tmobile note 2.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
I don't recommend that.
[T-Mobile, Samsung Galaxy SIII] tmobilewinguser:
hi im already rooted and on JB but want to reflash and start fresh does this thread have a flashable file in it so i can flash through TWRP. sorry for the dumb ? I've read through the op but since im reading it through my phone i may have missed it thanks in advance.
[T-Mobile, Samsung Galaxy SIII] aviseqdas:
Phone came with stock JB, now install custom rom without tripping the counter?

Noob question,

I got a S3 recently and it came with JB. What I observed in the download/recovery screen an extra line Qualcomm Secure Boot. This line was not there is S2 and Note 1 so I guess Samsung did something to prevent flashing. Can anyone explain if this is new or it was always there with S3?

Q2. Once I install the root injected stock image through odin and then install custom recovery with rom manager from playstore, can I flash any ROM from CWMR and it will not trip the counter? I just want to install a debloated ROM, I have a T-mobile phone which I use with straight talk and I just want a clean ROM with no t-mobile junk.

PS:

Why I am worried is in the triangleaway thread I read, that the phone during boot reads if anything has been changed to the system files and if so it any way increments the counter. So if you install busybox it will start incrementing your counter everytime you reboot your phone. And I definitely don't want to end up doing this, I would rather stay stock at least for while till my phone gets old enough ;)
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Only Odin trips the flash counter. And only on non-official firmware.
[T-Mobile, Samsung Galaxy SIII] aviseqdas:
Installed CWMR from ROM Manager and it did trip the counter.

Hi flashed the root injected tar, in the OP. Flash counter was zero. Now installed ROM Manager from google play and installed CWMR and it did trip the counter to 1. So it does not matter if the custom recovery is installed via Odin or via ROM Manger, the counter gets tripped. I just voided the warranty of my 1 week old phone for absolutely nothing....I really did not needed a root, could have lived with it.:rolleyes:
[T-Mobile, Samsung Galaxy SIII] Towle:
Correct, it doesn't matter how recovery is installed. Look up Triangle Away, it will be your best friend if/when you want to unroot and set the counter to 0.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
Under 3rd section you didn't see that bolded blue Note: line?

Regardless, as Towle said the triangle away app works with these phones. You can use that to reset the counter. However don't waste your time if you want to leave that non-stock recovery as it'll go back to 1. Just do it when/if you need to do a warranty return of the phone, Flash stock and use triangle away and it'll be same as the moment you took it out of the box.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
"device modified" confusion

I have been searching the thread this morning but I am still no sure how to proceed. My phone status reads "modified". My phone will not check for OTA updates and gives me the "your device has been modified" error message. I am assuming the flash counter on my phone is tripped.

I rooted my S3 a few months ago after getting the OTA JB update. I flashed and I am still running the root injected root66...T999UVDLJA image. I then used Goo manager to install TWRP. I cannot even remember how I installed the rooted image. I cannot find Odin on my PC but I assume, unless there is another way to do it without a PC, I must have used it on my PC to flash the root66 image. A screenshot of my software status is attached.

How do I get my phone stock-rooted with the status "unmodified". 0 flash counter would be a plus. Not having to wipe would be incredible and is too much to ask for.

Thanks
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
its the non-stock recovery... Use triange away then just re-flash the root66. if you dn't want to use the pc use mobile Odin. and you should then be 0 counter and unmodified status.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
I will try it with Odin Mobile now. Thank you mrRobinson for your help and for your your great contribution to the forum users! googookachoo to you mrRobinson :)

update: Good now! Thanks again
[T-Mobile, Samsung Galaxy SIII] gordomao:
Stuck... Plz Help

**EDIT** I pulled the battery and restarted my computer, it went through all the way this time with no problems.

I followed the guide and Odin hasn't finished in over 40 minutes. The progress bar appears to be at 10% and in the box it has been sitting at

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

and its been stuck on this line for the majority of the time.

In total its done all these steps:

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

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

<OSM> Please wait..

<OSM> root66_TMO_T999UVDLJA.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

Should I wait another hour? Any suggestions. I'm just a nervous noob.

Thank You
[T-Mobile, Samsung Galaxy SIII] victorbrca:
Tried doing it a few times with the original cable and it goes trough, but it gets stuck on the boot screen. Is there any other way I can apply the original ROM rooted? I had a custom ROM before.
[T-Mobile, Samsung Galaxy SIII] victorbrca:
Got it to work.. just not sure how.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
with custom rom prior, you needed to get into recovery and factory wipe.
[T-Mobile, Samsung Galaxy SIII] netfortius:
[OT] is USA (T-Mobile) 2013 January T999UVDLJC T999TMBDLJC worth a look

Referring to:

http://www.hotfile.com/dl/191743281/1c0c7ef/T999UVDLJC_T999TMBDLJC_TMB.zip.html
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
will upload pre-rooted shortly.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
OP Updated.
[T-Mobile, Samsung Galaxy SIII] wideasleep1:
While I've moved on to Nexus 4, wife got hand-me-down SGS3. She updates with the new OTA and began whinging when adfree and adaway no longer worked. I tried OTA Rootkeeper with no success, and was thrilled to see you had already updated the new OTA and posted it on AFH. MUCH thanks for keeping on top of this, VERY appreciated! Cheers!
[T-Mobile, Samsung Galaxy SIII] Wicked68:
So, I rooted a few months ago. I'm still running rooted stock, haven't installed a 3rd party recovery. I checked for status update, and it found the new 1. Should have install through the OTA, or should I flash the new updated image in this thread, through Odin? If I install the OTA update, will it unroot the phone? If I flash the image through Odin, do I have to factory reset first? I appreciate the forthcoming answers. Thanks.
[T-Mobile, Samsung Galaxy SIII] anil2653:
If you are directly downloading update from tmo over the air then it will be unrooted so to keep root you can use some root keeping application before updating

Else you flash this pre rooted image using Odin and no need to wipe or factory reset :)
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
Yes as anil stated, you can try using voodoo ota rootkeeper to preserve root through the update process. You could try this first. If you lose root simply flash the Odin image here and no harm done. This will not wipe your data, put you on the latest, and root your phone with the latest (as of today 1.04) SuperSu and su binary.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
SysScope and modified status

I ran "Triangle away" to get my status back to "unmodified" but I soon ended up back to modified, maybe from rebooting. I thought it might be because I had frozen a system app so I checked in Titanium and found SysScope 1.1.15 frozen. I unfroze it and rebooted and I was good.

Just now I ran a nandroid in preparation for installing the new OTA update. After I rebootd I was back to modified again. I checked in Titanium and sure enough Syscope was frozen even though I had not done it. Also, this time I searched for SysSope instead of frozen status and I see there is another one called Enterprise Syssope...e 4.1.1-T999UVDLJA

I have again frozen the Syssope 1.1.15 and have "normal" status and will try to run the OTA. Hopefully OTArootkeeper will work.

Can anyone tell me what is going on here? What is the deal with Syscope and how should I manage it?

BTW- do I need to temp unroot with Rootkeeper before I run the OTA?
[T-Mobile, Samsung Galaxy SIII] magicland:
Getting a "FAIL" (can't open the serial (COM) port) when attempting to load the TMO_T999UVDLJC.tar via Odin onto a stock TMO S3 updated via KIES to the latest OTA. All previous ones flashed with no problems.
[T-Mobile, Samsung Galaxy SIII] wideasleep1:
Try reloading fresh drivers from Ssmmy..in OP.

---------- Post added at 09:38 AM ---------- Previous post was at 09:33 AM ----------

I might have failed to mention in my post above..but OTA Rootkeeper did NOT work for me on this OTA..and I had 'protected root'. If it does work for others..I wish they'd post accordingly...don't mind being wrong.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
I'd kill syscope cause its a bad app. there are actually 2 processes and a library to remove to completely remove it.

Don't get confused with triangle away resetting the binary counter and showing a "modified" status. they are two completely different things. Unless you need to use drm protected content in allshare you can ignore the modified status when you are rooted and are modifying stock system apps (like removing syscope etc). It's not harming you or anything you can do at that point. If your flash counter is 0 and you need to return the phone then you'll odin back the stock rom and be set. Running rooted and modifying system apps AND caring about the "status" is an effort in futility.
[T-Mobile, Samsung Galaxy SIII] Wicked68:
Thank you, and you too Mr. Robinson