yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I may be wrong as its been a while since I looked at this, but some apps will use the id to verify your licensing. So if you let it remain as is, and then manually install the app or use a previous backup it'll fail its market license check.

Simply reinstalling it from the market will associate the new id and it'll work. I seem to recall some mentioned problems with some cloud services (google maybe?) and they were not able to get tgeir data until restoring the old id. (I feel like I'm remembering that wrong fyi, just thought I'd throw it out there in case someone else remembers)

Personally, I have never had to revert to the old. I just tell it to ask later just in case. Some of my paid apps won't work though and require me to download them from the market. I think this is why.
[T-Mobile, Samsung Galaxy SIII] :
Interesting. Not to say you're not experiencing what you say you are, but I just did the JB load through ODIN and my phone status is still "Normal". Mind you, I haven't loaded a custom recovery on my phone yet.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Can you do me a favor an before loading anything, reboot the phone and let me know if it still says Normal? Thanks!
[T-Mobile, Samsung Galaxy SIII] :
I'll have to re-ODIN the file. I uninstalled a number of bloat apps and even moved Carrier IQ and now it's "Modified/Custom". :crying:

I'm planning on going back to ICS - at least stuff worked there.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Don't worry bout redoing anything just to check that.

It being modified isn't going to be a permanant problem. Don't know yet if it actually affects anything in jb but you should be fine with it.

Mine ALWAYS is modified! :D

I have had no problems with anything not working btw.
[T-Mobile, Samsung Galaxy SIII] :
The thing that broke for me was WiFi calling in JB. Since I travel to Canada a lot, I use WiFi Calling a lot to avoid roaming charges.

EDIT: Well, so much for that idea. WiFi calling in ICS build is just as bad as in JB. ODENing (?) back to JB.
[T-Mobile, Samsung Galaxy SIII] RaymondPJR:
I'd go back to JB, but try different modems 'till you get one that works best. I haven't had any real problems with wifi-calling since I left the UVALEM modem. It has worked well on every other modem I've tried since then except on slow wifi networks, of course. On slow networks or weak connections, it'll fail for sure.
[T-Mobile, Samsung Galaxy SIII] :
Thanks Raymond. I'll PM you for advice later.

Back on topic: interesting tidbit of info. I used stock Recovery and did a complete wipe (factory reset/davlik/cache), and then took the TMO ICS root66 injected file (October 4.0.4 ICS) and used ODIN to load it up. My device status was "Normal".

I then took the TMO JB root66 injected file and just loaded it through ODIN (no wipe). Phone status is now "Modified".

I'll try wipe and reload of the TMO JB file later today and see if I can get back to "Normal".
[T-Mobile, Samsung Galaxy SIII] raykovitz:
Doc.. The problem w/ system being modified is that now ny Samsung services apps will not work, like media hub or allshare.
[T-Mobile, Samsung Galaxy SIII] Arhtard:
Well just wanted to add to the confusion ..

Flashed root injected 4.1 firmware on stock 4.1 and deleted major bloat, swapped out build.prop for one with some minor additions, changed a lot of media files, rebooted to recovery, reset phone, and my device status is still normal. Pulled battery, rebooted and status is still normal.

Thanks for your work mrRobinson!

Edit: forgot to mention i added apps and lib files to /system as well
[T-Mobile, Samsung Galaxy SIII] :
Is is possible to provide a list of the bloat you pulled? Screen shot of status?

Thanks.
[T-Mobile, Samsung Galaxy SIII] neim81094:
Well you have to do is delete anything that you know you don't need

EG:

You could delete browser if you have other web browsers as your default

But don't delete SIM toolkit obviously

Some stuff I deleted were all.T-Mobile stuff except "my account", messaging cuz I use go sms pro, and animated wallpapers because I don't use them. Also other misc system apps that I don't use usually if you don't know what it is/does DON'T uninstall it and you should be fine :D

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] Arhtard:
Yeah i will make a list and add screenshot soon. Just clocking out at work and headed home.

Edit: added a text file with the list of bloat i removed and kept system status "normal" with full phone functionality except weather on lockscreen

Download video from MediaFire showing status here
[T-Mobile, Samsung Galaxy SIII] :
The reason I ask is because I used Titanium Backup to remove some bloatware and my status changed to "Modified". I was wondering what I deleted that caused the flag to flip.
[T-Mobile, Samsung Galaxy SIII] PDAras:
Can I use this if I am already on latest stock (October 2012 - 4.1.1 JellyBean) ? Since it wont be an upgrade or anything, will I lose all apps and setting?

Thanks!
[T-Mobile, Samsung Galaxy SIII] Arhtard:
Yes you can use it. I don't know about loosing your apps etc, sorry.

edit: actually, i thought i remembered if u flash same version your apps/settings stay, but i've worked on 5 devices in the last 2 days and honestly can't remember the result now. sorry
[T-Mobile, Samsung Galaxy SIII] Perseus:
Nice Work Mr. Robinson. Worked like a charm and did what promised. Now to go find that OTA Rootkeeper.

P.S. Apps, data etc remained as they were. No Reset or format there.
[T-Mobile, Samsung Galaxy SIII] jay661972:
Can you odin to this file (recent tmo update) if you are running deodex rom without wiping the data?
[T-Mobile, Samsung Galaxy SIII] t0mD:
Next question, following the steps on the provided page for CWM will also not raise the counter? O_o
[T-Mobile, Samsung Galaxy SIII] Lawful123:
It will say custom. The only way to set it back to normal is to ODIN the original software. And from what I read, ODIN the original software does not trip the counter. Wont help you if you already tripped it however. This is good if you have to send te phone in for warranty.

---------- Post added at 09:14 AM ---------- Previous post was at 09:09 AM ----------

If you use the method in the OP it wont. Its the one that uses the "dd" command to install CWM. If you ODIN CWM then your counter will trip.
[T-Mobile, Samsung Galaxy SIII] stevessvt:
Now if we can get a hold of this imei information vanishing, life will be perfect.
[T-Mobile, Samsung Galaxy SIII] Jaxidian:
That's simply a problem that can be fixed by backing up your EFS partition. This should be the very first thing you do after routing your phone. If your EFS partition gets corrupted, restoring your backup makes it all good.

(from my phone)
[T-Mobile, Samsung Galaxy SIII] stevessvt:
I thought the other thread about losing the imei said that it wasn't stored in the efs partition on the gs3. And nobody has been able to restore it yet.
[T-Mobile, Samsung Galaxy SIII] darren.wlsn1:
where is imei info or how do i know if its corrupt?
[T-Mobile, Samsung Galaxy SIII] Tho San Thanh Pho:
So to clear this up, If I flash any thing unofficial with Odin except for the method in OP post, then the counter will trip? Is this correct? Or is it anything flash via CWM and Odin will trip the counter? :confused:

I am still unclear from reading the posts.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
If you use ODIN to flash anything except what is in the OP, you will trip the counter.

You can flash anything with CWM without tripping counter.

Key is to get your phone up to the point where you have root and CWM without initially tripping counter. Once you do that you can flash away with CWM with no issues.
[T-Mobile, Samsung Galaxy SIII] Tho San Thanh Pho:
:highfive::good:

Thank you mrRobinson! You cleared this right up for me!
[T-Mobile, Samsung Galaxy SIII] neotoky:
Yes that's correct. Then flash the CWM by OP's instructions. From what I read anything flashed through CWM does not trip your country. I suggest an app called mobile Odin by chainfire which you can flash anything on Odin and it does not increase the counter. Root is needed to use the app so I suggest using OP's method.
[T-Mobile, Samsung Galaxy SIII] stevessvt:
Settings-about device-status-imei

If there is a huge number there, your good. If its 00 or something like that, it's bad. If its lost you lose 4g capability, and afaik there isn't a way to restore it yet.
[T-Mobile, Samsung Galaxy SIII] miked79928:
Just wanted to comment that this worked successfully on my T-Mobile variant.
[T-Mobile, Samsung Galaxy SIII] darren.wlsn1:
ty, im a gsm nOoB

yaaaa huge number.
[T-Mobile, Samsung Galaxy SIII] stevessvt:
Anytime, your always learning something new about this platform. I know I am.
[T-Mobile, Samsung Galaxy SIII] widto08:
What version of ODIN is everyone using to do this ROOT method?
[T-Mobile, Samsung Galaxy SIII] jaliscojorge:
Like i said root per op instructions then i used rom manager for cwm and no tripped counter:)

typed from my white sgs3 hungry for some Zen
[T-Mobile, Samsung Galaxy SIII] :
just installed Rom manager and then had it install cwm?
[T-Mobile, Samsung Galaxy SIII] moonfire711:
So, I am super excited about this. I wish it had come earlier so I hadn't already tripped my counter, but now I can flash my Dad's phone without the guilt. :)

Does anyone know where the imei info is stored if it's not in the efs partition? I backed that up, but if it doesn't protect me, I'd like to know what does. Thanks.
[T-Mobile, Samsung Galaxy SIII] jaliscojorge:
Yep:)

typed from my white sgs3 hungry for some Zen
[T-Mobile, Samsung Galaxy SIII] Lawful123:
+1
[T-Mobile, Samsung Galaxy SIII] Perseus:
I doubt it. You'd need 4.1.1 Deodexed ROM with just the SU injected to NOT wipe data.

P.S. IMHO It will still increment the counter.. Guess its already incremented for you since Deodex'd ?
[T-Mobile, Samsung Galaxy SIII] jay661972:
My counter is alread 1, just want to go back to odex. Im currently running deodex rom
[T-Mobile, Samsung Galaxy SIII] Perseus:
If that is so then in the original Post you have 4.0.4 ROM. You may want to grab and flash that and then flash the 4.1.4 after that.

Perhaps this may help. http://www.sammobile.com/firmware/?page=3&model=SGH-T999&pcode=TMB&os=1&type=1#firmware
[T-Mobile, Samsung Galaxy SIII] jay661972:
Thanks man already figure it out.
[T-Mobile, Samsung Galaxy SIII] M9x3mos:
So just to make sure I am understand this right from what I have read since is a little confusing with all the posts.

Just flashing the tmo 4.1 rooted overtop 4.1 already installed will not increase the counter.

but installing a different recovery thru the DD method or app in market will increase counter and or change status to modified?
[T-Mobile, Samsung Galaxy SIII] Perseus:
IMHO you understand correct.
[T-Mobile, Samsung Galaxy SIII] Dano79:
So when I extract the 7 file I only get the md5 am I missing something here
[T-Mobile, Samsung Galaxy SIII] Wicked68:
Once I root, using this method, I don't have to use Odin to flash custom ROMs right? I can use Clockwork recovery without tripping the counter right?

Also, OP says make sure the md5 matches. What is supposed to be matching what, haha?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Actually its a .tar.md5 file. Thsts normal. Flash in Odin and itll check the md5 portion automatically.

Well you have to use cwm or twrp to glash custom roms, or better yet, Mobile Odin, but as soon as you boot into recovery it'll trip the counter.

Reinstall stock recovery after flashing your rom, then Triangle Away to reset the counter.

If the rom you flash has a custom kernel, it will re-trigger the counter EVERY boot.

In root explorer, check properties of the file and it'll tell you the md5. Compare that to the md5 listed either in op or on download page.
[T-Mobile, Samsung Galaxy SIII] durps:
Quick questions. I did steps 1 and 2 to get root and remain stock. Can I flash kernels made for stock roms or do I have to get a custom recovery for that? And second question, where do you guys even see the flash counter? What do I have to press in order to see the counter when the phone is off. Thanks. Sorry new to the device.
[T-Mobile, Samsung Galaxy SIII] jay661972:
download rom manager and flash clockwork recovery and when you go to download mode, that's where you see the counter. i think volume down+power+home, i always use adb to go to download mode
[T-Mobile, Samsung Galaxy SIII] durps:
Ok sounds good but if I flash clockwork will it trip the counter?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Installing it shouldn't, depending on how you fo it, but on JB it'll set your counter to 1 every time you boot recovery. There's a lot more info about it at the thread in my sig.

I suggest reading it before you go any further.
[T-Mobile, Samsung Galaxy SIII] clninja:
My counter is at 3.... it doesnt bother me at all
[T-Mobile, Samsung Galaxy SIII] neim81094:
Mine is 4 surprisingly i guess restoring from backups isn't flagged

Sent from my SGH-T999

If I helped please press the thanks button :)
[T-Mobile, Samsung Galaxy SIII] Wicked68:
Ok, I have 1 more question before I go through with this. I know the OP says to download the Driver exe from the Samsung site, I just want to clarify that we are supposed to run the exe and install the drivers before rooting? Not just place the exe file in the same folder as Odin? I appreciate the answers. Thanks
[T-Mobile, Samsung Galaxy SIII] Cobra281:
Did you boot into recovery at all after installing the OTAs with root?
[T-Mobile, Samsung Galaxy SIII] reapur:
Yes, Install the drivers first thing, plug in your phone and wait for windows to do its thing identifying drivers and all that. Unplug the phone and then plug in back in and make sure windows is done before you run odin.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
This is the easiest thread for me to maintain... everytime I check there are always answers to people's questions. I never get a chance to post...:(

+1 XDA Community!
[T-Mobile, Samsung Galaxy SIII] DsturbD:
^^^totally agree there :good::good:
[T-Mobile, Samsung Galaxy SIII] heybobitsme:
Well, maybe you can answer this question: has anyone tried rooting with Odin in VirtualBox? My setup is Ubuntu 12.10 host with Win7 guest. I installed the Samsung drivers and Odin in the guest and set VB so it "sees" the phone when hooked up to USB. I stopped short of booting into Download Mode. I looked into Heimdal, but it doesn't support the U.S. Qualcomm S3's. I realize this is more of an Odin question than a TMo S3 root question, but I'd really appreciate your input.
[T-Mobile, Samsung Galaxy SIII] Perseus:
I have been so far a Lurker on this Forum. I decided to start with your thread to help others. ;)
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
I haven't personally done it myself but from a technical standpoint if the drivers are there and phone shows up correctly, you then see the Added! in Odin once connected in download mode, then i'd say all the needed communication is there and you should be good to go.
[T-Mobile, Samsung Galaxy SIII] Wicked68:
I flashed the official OTA, and planned on using this method to flash the rooted OTA over it, but now I want to go back to ICS 4.0.4. So, I have to wipe and then flash the ICS OTA in the OP, with Odin?

The main reason is the battery life. I was getting great battery life, and now with the JB update, it is terrible. Is anybody else experiencing this? Or does it get better after de-bloating the unwanted apps?
[T-Mobile, Samsung Galaxy SIII] heybobitsme:
That's what I was thinking. Thanks for the reply. :cool:
[T-Mobile, Samsung Galaxy SIII] otariq:
My bro bought a s3 and did ota to jb and now wants to root with custom recovery. I read the note on OP and wanna make sure if installing custom recovery with terminal emulator will trip flash counter or not. Also if it does trip counter can't we just use triangle away or is there new security with jb ota that prevents that?
[T-Mobile, Samsung Galaxy SIII] EhdisChris:
Triangle away works Yes and No.

So read up on this.

http://xdaforums.com/showpost.php?p=34748953&postcount=56
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
My battery life is the same but I did debloat.
[T-Mobile, Samsung Galaxy SIII] Wicked68:
Ok, well, I'll try the rooted JB first then, I guess. Thanks.
[T-Mobile, Samsung Galaxy SIII] Wicked68:
Ok, finally did it. And it was fairly painless, very straightforward. For now, I'm gonna stay stock rooted, but definitely will be removing lots of bloatware, and will be installing my usual rooted apps. Can somebody please direct me to an app or thread that will show me how to recapture the apps2sd feature? Or am I gonna have to flash a custom ROM to get apps 2 sd back? Let me know. Thanks.
[T-Mobile, Samsung Galaxy SIII] Wicked68:
Uh oh, having a bit of a problem. The rooting went fine. Then I was installing some apps it started rrebooting. It started when I ran LBE Security for the first time. Booted into recovery and wiped. While trying to run Titanium backup, it suddenly restarted again. Now it's running. So we'll see
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
I recall reading about a problem with lbe and jelly bean in general over on the att side. That app might need an update for jb.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Last time I looked, a couple weeks ago LBE wasnt compatible with jb at all. Wouldn't even start.
[T-Mobile, Samsung Galaxy SIII] Perseus:
If you are not too happy with Jellybean's App Management then you can merrily go get APP2SD or if you feel like it, LINK2SD

My Battery seems to be doing OK too. I too did my own flavor of De-Bloat.
[T-Mobile, Samsung Galaxy SIII] EhdisChris:
Quick Question, To debloat, you would need a deoxed rom correct?

How would I deox my rooted stock (root66) rom without tripping the flash counter? mobile odin and not flash as a zip?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
You dont need yo be deodexed to debloat. Just remove the .odex file with the .apk.
[T-Mobile, Samsung Galaxy SIII] Wicked68:
Ok, thanks. I don't use the current version anyway, with the Chinese characters. I was still using the old version, with the red button icon, haha. Any newer app that does the same thing?

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

Apps2sd is saying there is no real external storage, that it is emulated. So, now what?
[T-Mobile, Samsung Galaxy SIII] Perseus:
That's possible caused by the fact that on ICS & JB, /Storage/SDCARD is for internal partition. Your real SD Card is /storage/Ext-SD. Get APP2SD to look there and not on the phantom /SDCARD.

As Doc said you don't. I used Titenium Backup to back up and remove things I don't like. Especially SYS attributed Bloat. Think I need to follow Doc's point and delete the .ODX files too using ES Explorer.
[T-Mobile, Samsung Galaxy SIII] DsturbD:
i didnt think you can just delete the odex files. thought you had to merge the data that is in them back into the apk files?
[T-Mobile, Samsung Galaxy SIII] RaymondPJR:
They are de-bloating a ROM, nothing else.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
Right, to deodex a rom you can't simply delete the odex files. I've seem some so-called guides saying you can.

However to debloat a rom as long as you delete the corresponding apk with the odex you are good. no fc's.
[T-Mobile, Samsung Galaxy SIII] scooby-snack:
How do I go about Un-Rooting this back to complete stock? Sorry to sound ignorant but I cant seem to find a thread that shows on the T Mobile S3. WIFI calling is a deal breaker as I live in an area with ZERO reception. I plan on returning the phone to Tmobile today and want to make sure I return to stock 1st :)

Thanks for any help getting me to the correct guide-

Scoob
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Just flash the stock fw in Odin. Use Triangle Away first if needed.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Well you can also use OTA Root Keeper to Unroot it. Or as Doc said, Re-Flash Stock formware from SamMobile here.

To be honest, I have tried WiFi Calling myself even though I have good Coverage. I use it to skimp on my minutes.Seems to be ok so far. I do get a message on Screen at the start of the call that your call may drop due to poor Wi-Fi Coverage. Well My router pumps out enough to get signal 2 houses over. So No complaints.
[T-Mobile, Samsung Galaxy SIII] joselamar:
Hello everyone, I've been looking for answers and cannot get any in the forums. I followed all steps to root my GS3 from this thread, everything worked fine except the fact when I go to recovery mode I get the android robot lying on its back with the red error triangle. How can this be fixed, it's driving me nuts. All I want is to install the de-bloater file using CWM to remove all cr-apps
[T-Mobile, Samsung Galaxy SIII] DsturbD:
did you read the OP where it says if you want to install CWM then follow the steps in this thread? or that you can install CWM using Rom Manager or TWPR using Goo Manager?

you need either one of those recoveries so you can flash the debloater tool
[T-Mobile, Samsung Galaxy SIII] Wicked68:
Ok, my battery life seems to be back to being good on JB. Maybe it was something I had installed before
[T-Mobile, Samsung Galaxy SIII] _MrAwesome_:
Mobilicity

Does anyone know when the official jellybean update will come to T999V mobilicity?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Is your Phone Rooted ? Can you please give me the exact sequence of Steps you have followed so far?
[T-Mobile, Samsung Galaxy SIII] LordPhong:
I keep reading about the counters incrementing but I'm not experiencing any such thing and I flash like an alcoholic. I rooted my T999 with this then added TWRP. After that, loads of custom ROMs and kernels. My counter still says zero.

Sent from my Frosty Jellybean fingers.
[T-Mobile, Samsung Galaxy SIII] Perseus:
What pray the Device Status say in Settings > About Device ? Also what is the status of ROM displayed on Downloading Screen ?
[T-Mobile, Samsung Galaxy SIII] LordPhong:
That, however, says modified.

Sent from my Frosty Jellybean fingers.
[T-Mobile, Samsung Galaxy SIII] Perseus:
What about the Android Status on Download Screen ?
[T-Mobile, Samsung Galaxy SIII] crxforya:
Awesome worked like a charm!!

thanks
[T-Mobile, Samsung Galaxy SIII] LordPhong:
Custom, of course.

Sent from my Frosty Jellybean fingers.
[T-Mobile, Samsung Galaxy SIII] heybobitsme:
Odin in VirtualBox

Quoting myself for context:

I've tried running Odin in VB, with the configuration above. Interesting note, The phone in download mode shows up as SasmsungMSM8960 (note the misspelling) so I had to add it to the USB settings. My Win7 guest sees the phone in DL mode and tries to install drivers, although I already have the Samsung drivers installed. It fails, saying it can't find the drivers. Consequently, the phone never shows up in the ID:COM field in Odin. I tried changing the name in the device filter, but that didn't work. Any thoughts?
[T-Mobile, Samsung Galaxy SIII] M9x3mos:
I wonder if you put on custom recovery then custom stock ROM, put back stock recovery if then triangle away would work. Or if it just jelly bean recoveries that it don't work with.

Has anyone had Odin work on windows 8 so far?

I have not been able to get it to recognize my phone.

I am going to try completely removing the drivers from the system and reinstall and see if that helps.
[T-Mobile, Samsung Galaxy SIII] LordPhong:
Windows 8 also has XP Mode. I personally use VMWare.

Sent from my Frosty Jellybean fingers.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
you've added usb mass storage and other usb things to the device filter?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Forget Windows 8. I have devil of a time with Windows 7 Professional 64 Bit. Every time I run ODIN I get Blue Screen.

Not a show show stopper really. I have another Vista machine to use.

P.S. - Just to Clarify I can launch ODIN Program with or without Admin Mode or XP Compatible mode. However When the Flash actually tries to start, I get The Blue Screen of Death.

P.P.S - Windows ODIN will increment Samsung Flash counter some of the cases anyway.