yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] Wicked68:
Does everything dealing with the S3 have to be done with Odin? Can't do the boot animation the old way? Like just putting the boot animation zip into the correct folder? Or do it using ROM Toolbox?
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
you don't need odin for anything. It is one of many ways to root. You surely don't need it after rooting for boot ani's or flashing anything. What can't be done with simple root access can be done with a non-stock recovery.
[T-Mobile, Samsung Galaxy SIII] skytechja:
Quick Question

Ok, my question here is not related to what yall just been saying....

Has anyone installed and used Titanium Backup after root?

does this trip the counter as well ?

by the way, the counter can be reset
[T-Mobile, Samsung Galaxy SIII] Perseus:
Installing Titanium from Google Play will never Trip Flash Counter.
[T-Mobile, Samsung Galaxy SIII] anil2653:
NO it will not trip flash counter but it depends how you root

I am using Titanium Backup after rooting with root66 and my flash counter shows 0 only system status is as Modified rest every thing is normal.

Yes counter can be reset to 0 by using Triangle away.
[T-Mobile, Samsung Galaxy SIII] isa_rod:
Odin Flashable TWRP Recovery - openrecovery-twrp-2.3.1.0-d2tmo.tar.md5

Where do I put this in Odin at?? PDA as usual??
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
Yes.
[T-Mobile, Samsung Galaxy SIII] krntehknik303:
Thank You! Thank You!
[T-Mobile, Samsung Galaxy SIII] frettfreak:
So this is my second s3 that i am rooting and the first one i did the unified toolkit. While the unified was simple and pretty easy, this was WAY easier and i didnt loose anything (which has never happened when i rooted any phone before).

Was able to download goo manager, afterward and install twrp and my flash counter is still on zero!! This rocks and SHOULD BE STICKIED!!

Thanks a ton mrRobinson!!!
[T-Mobile, Samsung Galaxy SIII] seshaz:
Have you booted into recovery or flashed another kernel?
[T-Mobile, Samsung Galaxy SIII] frettfreak:
Booted into recovery but actually just installed a new Roman and noticed my flash counter went to 1 :( however triangle away took care of it without any issue so no worries.
[T-Mobile, Samsung Galaxy SIII] seshaz:
I wish there was a way to flash **** and still be able to watch downloaded movies from media hub or any DRM content
[T-Mobile, Samsung Galaxy SIII] Perseus:
If you use Mobile ODIN & SuperSU Pro then this is possible. I am not sure which one or both are needed. But this will do it. Besides donating Chainfire for both is worth your money since you have the S3. Besides he is one of the best persons around here.
[T-Mobile, Samsung Galaxy SIII] frettfreak:
I am not sure I understand. Why wouldn't you be able to watch those?
[T-Mobile, Samsung Galaxy SIII] Perseus:
If your Flash counter is >0 or Device Status is Modified then Samsung Media Hub won't play or download movies. It will throw some sort of DRM Error.
[T-Mobile, Samsung Galaxy SIII] reapur:
Can someone please remind me how to handle OTA updates. I just got a Samsung Push Update notification. Do I ignore it or is it safe to let it do its thing? I'm up to date as of the OP of this thread.

Thanks
[T-Mobile, Samsung Galaxy SIII] Towle:
If you have zero flash counter and normal status, you can use OTA Root Keeper to take the OTA. What firmware are you on right now?
[T-Mobile, Samsung Galaxy SIII] reapur:
the FW same as Build? JRO03L.T999UVDLJC
[T-Mobile, Samsung Galaxy SIII] Towle:
Can you post a screenshot of the notification in the chat thread?

http://xdaforums.com/showthread.php?t=2002730
[T-Mobile, Samsung Galaxy SIII] reapur:
I'm sorry. I was afraid to activate the update (last time I did that it screwed up the phone)

but it looks like a samsung apps update, from the pictures?

cheers
[T-Mobile, Samsung Galaxy SIII] Perseus:
I am current as of OP. I too did get that Samsung Push Notification. Turns out it was an update to a single App called "Samsung Apps". This is nothing but Samsung's Version of Google Play. I updated it just fine.
[T-Mobile, Samsung Galaxy SIII] rddocke:
Stock image

Cant get stock image for tmobile to show up under PDA Missing something im sure. all I get after download is the .7z file. and I unable to open with 7zip. Im a little rusty :rolleyes:
[T-Mobile, Samsung Galaxy SIII] #1n00b:
I installed an app from the play store called zarchiver unzipped and put the file on my computer.

https://play.google.com/store/apps/details?id=ru.zdevs.zarchiver
[T-Mobile, Samsung Galaxy SIII] Perseus:
If you are unable to open the .7z file with 7Zip /WinZip / Winrar on a PC then the dowload is corrupt. Please download again. No point in flashing otherwise. You may end up with Boot Loop or brick.
[T-Mobile, Samsung Galaxy SIII] rddocke:
@ perseus71, #1n00b. Thanks fir the responses guys ive done both re-download and zarchiver however zarchiver unzips the files to .tar.md5 and still no luck with the odin PDA. anyone have a copy of the unzipped file maybe? it would be greatly appreciated
[T-Mobile, Samsung Galaxy SIII] #1n00b:
Mine did the same. No issues in Odin. Click PDA, choose the file and wait a moment for it to load. After you click start it takes like ten minutes.
[T-Mobile, Samsung Galaxy SIII] Perseus:
What you downloaded on pc as .7Z should have been opened by 7zip program. Inside you should find a .TAR file. Just save that TAR file someplace. Don't try to open the TAR file with 7Zip or any other Archive program. From inside ODIN click on PDA Button. Then in the File Select Box, point to the TAR file.

Let me know how it goes.
[T-Mobile, Samsung Galaxy SIII] rddocke:
I got all that figured out. What was going on was the. .tar file wasn't Coming up under the folder after selecting PDA. I had to search for it under My computer. Weird. However after flashing the t999uvalem file my phone got stuck in boot loop at the Samsung logo. Then I factory reset in recoverya and got the phone to turn on. However lol using root keeper didn't prevent me losing root with an its update, even tho root keeper says I'm rooted. I'm trying again. With a different file.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Oh Ok. Let me know how it goes.
[T-Mobile, Samsung Galaxy SIII] Leoniums:
Hi there and thanks again for all the infos.

I would like to ask:

if i install ClockworkMod recovery using Rom Manager from the Play store then my status will say modified right?
[T-Mobile, Samsung Galaxy SIII] Towle:
You got it.
[T-Mobile, Samsung Galaxy SIII] Leoniums:
Is there any way to keep the root66 rom, install stock recovery and set the status on normal again?

Or can i just keep the CWM and use triangle or something like that?

And thanks for your reply!
[T-Mobile, Samsung Galaxy SIII] Towle:
Your system can become modified from a lot of things, such as freezing system apps. Flashing a custom recovery will trip your flash counter. Both are reversible, but you need to be on stock recovery.
[T-Mobile, Samsung Galaxy SIII] christucker97:
Mr. Robinson thanks for the injected root 66. Its awesome. Jus wondering, I odin and extracted the tar as posted flashed root 66 and all works good. Even able to use allshare cast :) But when I download goomanager from market and installed TWRP it indeed tripped the counter but I have Triangle away and flash counter remains at 0 but now when allshare trys to connects it simply appers to connect then immediately disconnects. Is there another way to keep root 66 apply custom rom, and use allshare cast? Any help is greatly appreciated. Great work with Root66.

P.S. I tried also extracting TWRP tar u posted as well, but as I put it in odin I get invalid md5 and it would not flash.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Samsung Keeps track of the Modifications in two different places. One is the Flash Counter as you saw. There is another place under Settings > About > Status > Device Status. If this latter is Marked as Normal, then All Sharecast and other Samsung Apps such as Samsung Media Center will work fine. This status is not completely changed by Triangle Away. You may find some Workarounds in this thread.

If you install any custom Recovery, then the Device status will be Marked as Modified. In that case you will not be able to use Samsung Apps. So if you want Allsharecast to be normal then I suggest, take the Root offered by this ROM, Freeze (do not remove) any Bloatware that you want and you should be good to go.
[T-Mobile, Samsung Galaxy SIII] victorbrca:
Has anyone tried the new OTA update after installing this ROM? Do you loose all your apps/configs (like installing a ROM manually)?
[T-Mobile, Samsung Galaxy SIII] truckerdewd:
What new OTA update?

Sent from my wickedly awesome Galaxy S3 using my fingers. Duh!!!
[T-Mobile, Samsung Galaxy SIII] yakabud:
Basically it's still the same rom, with root injected in it. You will still have your stock apps. The apps you installed will be deleted. All you need to do is reinstall them.

And yes, OTA update is still working on mine.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes OTA works. Yes You get notified of a new update being available. Yes it will even download successfully.

However will it actually Install ? Highly unlikely. Especially considering your Device Status is likely Modified. Also take it VERY Seriously when Samsung says your phone will Brick if you try OTA on top of this Root Injected ROM. There are cases (here on forum as well) where OTA Flash on top of Rooted ROM SoftBricked.

If you want OTA, go back to stock and then download and install manually. If not, then wait for rooted release being made available.
[T-Mobile, Samsung Galaxy SIII] joselamar:
What version of the new OTA update is that?
[T-Mobile, Samsung Galaxy SIII] rookiegenius:
I have a question. As in OTA update, he said:

"...As such it still does all the checks so if you have deviated from the rooted stock image above by modifying system files this will fail"

Can someone explain this to me ? what does "modifying system files" mean? thanks :)
[T-Mobile, Samsung Galaxy SIII] Perseus:
Ok In short, if you did one of three things bellow,

1. Root your Device.

2. Install different Recovery from Stock.

3. Flash anything to the device.

Then there are programs running in your phone that will detect the above and prohibit OTA updates. The OTA notification will come and even download. But won't install due to above.
[T-Mobile, Samsung Galaxy SIII] allendon:
Rooted with custom recovery

Just rooted my s3 with cwm. thanks a lot mrRobinson.

All is working fine on my end except that when i make a nandroid backup the date on the file is set to the 1970's.

Any way to remedy this?
[T-Mobile, Samsung Galaxy SIII] Perseus:
This is a problem prevalant with Custom Recoveries. In my case with TWRP Recovery, this is expected behavior. All you can do is set the timezone correctly. For the Nand backups, I tend to manually type the date.
[T-Mobile, Samsung Galaxy SIII] xenine:
"OTA Updates:

Stock Recovery: Once rooted with above method, if you receive a notification for an OTA update, it has been verified you can use OTA RootKeeper to retain root through the update process."

ok i 'm confused.. if you rooted with the 'no-tripping the counter' method, why do u need 'OTA RootKeeper' to retain root when getting an OTA to a stock rom? shouldnt the 'no-tripping the counter' method prevent u from tripping the counter so u dont need another app to retain root?
[T-Mobile, Samsung Galaxy SIII] Towle:
I think you're a little confused about what root means. Being rooted means that you have root (administrator) access to your phone. The flash counter is something Samsung uses to see if you have modified your phone. This method of rooting basically hides root so your flash counter doesn't trip.

If you're rooted, you won't be able to accept an OTA update. You would need to unroot in order to update. But with the root keeper app, you can temporarily disable root to accept the OTA update then enable it again.
[T-Mobile, Samsung Galaxy SIII] Misterjunky:
re: OTA Update

Yes, I read about the root keeper app but I think one little thing is being over looked, even with the

root keeper app in order to get the OTA updates the phone needs to have the stock rom flashed first.

It cannot be done if you run customized roms like "Wicked 9.1" (jb 4.1.1) or any ported roms.

(or am I wrong?)

If that is the case what advantage is there in using root keeper?

It's not that difficult to re-root the phone after OTA update in the first place.

I do have one question, when doing an OTA update does the update include the modem image

or is it like all the custom rom zips here which do not include the modem images ?

The reason I ask is that I have a Samsung AT&T Unlocked I747 and if I were to flash the

stock ODIN flash firmware for Tmobile it would include the modem image file which would

cause my phone not to be able to make/receive any calls as well as data would not work.

I would have to flash the stock AT&T modem in order for it to work properly.

Thanks!
[T-Mobile, Samsung Galaxy SIII] Towle:
You're right about needing to be on a stock rom to update, but the firmware in this thread is stock; which is why it is being discussed here. Many people just root without flashing a custom rom, so that's where root keeper comes in handy. However, your device status needs to be normal to accept an OTA, even with root keeper. So if you have removed carrier iq or done any modifications, you will need to go back to stock to take an OTA update.

OTA Updates do include the modem. But you will never receive an OTA from Tmobile, even if you're using your i747 on their network.
[T-Mobile, Samsung Galaxy SIII] xenine:
i'm getting a galaxy note 2 soon.. does mr. robinson have a ROM with root for the note 2 that doesnt trip the flash counter?
[T-Mobile, Samsung Galaxy SIII] Wicked68:
I was minding my business and all of a sudden I see a TMo update package notification in my status bar. Didn't even ask me if I wanted to download the update. It's about 185MB, so I'm thinking it may be the Jelly Bean update. I'm not gonna install it because I don't want to lose root, before you have a rooted ROM up.
[T-Mobile, Samsung Galaxy SIII] Misterjunky:
re: update

Do you have any more information about the download like the exact filename or version number?

If you have a file manager perhaps you can find the file and let us know some more information about it.

For some reason when I tried to google for Galaxy S3 T999 Tmobile OTA updates for the past two months I found none.
[T-Mobile, Samsung Galaxy SIII] Wicked68:
I'll try to look. Now, the download has finished I think. And now it's saying "Connecting to Server"

Zapped form Samsung Galaxy S3, Rooted (Stock)
[T-Mobile, Samsung Galaxy SIII] Wicked68:
Zapped form Samsung Galaxy S3, Rooted (Stock)
[T-Mobile, Samsung Galaxy SIII] Wicked68:
It's an update.zip file

Zapped form Samsung Galaxy S3, Rooted (Stock)
[T-Mobile, Samsung Galaxy SIII] Misterjunky:
re: update.zip

Looks very interesting, perhaps you can find a free uploading site

like filesend at: http://www.filesend.net and upload the file and then

post the link to it here in XDA so the developers can check it out

and see if it's something they can use for the custom roms here.

Thanks for checking it out.
[T-Mobile, Samsung Galaxy SIII] Wicked68:
Checked the TMO forums, and apparently, it is the Android 4.1.2 update

Zapped form Samsung Galaxy S3, Rooted (Stock)
[T-Mobile, Samsung Galaxy SIII] Misterjunky:
re: thanks again

Yes it is, and I have just seen other posts about it already here in XDA

from people who have already installed it.

This update contains the multi windows and other new stuff.

The sooner the devs can get their hands on this the sooner we

will all see new v4.1.2 custom roms based on this update.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Kindly note, its Samsung Implementation of Multi-Window support. Its limited and based on Samsung Window Manager. Also I think it only works on Touchwiz ROMs.

I don't think it is related to Android's internal Multi Window support.
[T-Mobile, Samsung Galaxy SIII] Hekademos:
has anyone successfully run this OTA on stock recovery with RootKeeper?

Every time I try, the installation fails.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Who cares? Just reroot it. It takes literally 20 seconds.
[T-Mobile, Samsung Galaxy SIII] M9x3mos:
How would one go about rerooting though
[T-Mobile, Samsung Galaxy SIII] karipay:
Hopefully Mr. Robinson will give us the root66 file. Thanks in advance!
[T-Mobile, Samsung Galaxy SIII] rookiegenius:
pls update the 4.1.2 rooted OTA. THis is quite surprising since I dont' expect this update in 1 or 2 months
[T-Mobile, Samsung Galaxy SIII] joeym11:
So I just got my phone tonight and I used this method with my wind mobile phone, And I downloaded the wind mobile tar. It seemed to go well, but at one point, I noticed that there was 2 com things there, and the first one said fail at one point, and then in the text box it said

It seems to have worked, and I have Superuser, but I just want to make sure this is normal.

Thanks

Joe

Also

I have always used CWM, what is the difference between using that and TWRP?

Thanks again,

Joe
[T-Mobile, Samsung Galaxy SIII] Wicked68:
Does OTA Rootkeeper actually work? Never tried. I'd rather stay rooted, than install the update. Is there a way to root/just get superuser again, without needing a stock ROM to Odin? Like when you could root previous HTC phones? I know Samsung has a different boatload, or whatever, haha?

Zapped form Samsung Galaxy S3, Rooted (Stock)
[T-Mobile, Samsung Galaxy SIII] karipay:
It worked for me. I was using the root66 v4.1.1. Ran rootkeeper, applied v4.1.2 update then restored root.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
You talk about rooting as if it's hard. It took you more time to type your post than it did to root. Just root again. Who cares?
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
OP Updated with :: root66_TMO_T999UVDMD5.7z
[T-Mobile, Samsung Galaxy SIII] Mordred:
Debloat

Do we need a new debloater for this? I tried running the new version and the signature failed.
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
You're the man! Thank you.
[T-Mobile, Samsung Galaxy SIII] joselamar:
I'm not seeing the SU app after flashing the new update (4.1.2) through Odin. I even reverted back to 4.1.1 then 4.1.2 and still the SU app doesn't appear. What am I doing wrong? I had flashed 4.1.1 before without issues and had SU access.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
Will the new ROM also be available as a flashable update ago we don't have to wipe?
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Not possible to upgrade in this manner. Have you verified you do not have root from a root app?

No. That is not the purpose of root66. There are other ROMs for this purpose.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
I thought the last 2 updates were posted like that in the OP at the bottom of page. If I remember right, the last update was posted like this one is and I flashed it with a full wipe and then it was later posted as a flashable update. Maybe I don't remember this correctly.

I also don't know what you mean by " there are other ROMs for this purpose" I want stock. I thought that was the reason for root66.
[T-Mobile, Samsung Galaxy SIII] eagle63:
The last 3 or 4 roms here have all been the kind that don't wipe your phone.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
It does not wipe your data partition. It wipes everything else.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
That is great.

Thanks
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
Worked perfectly with no wiping using Mobile Odin. Thank you Mr. Robinson and alll.
[T-Mobile, Samsung Galaxy SIII] scifan:
Hmmm... is there a backup link for downloading this? (the hosting site appears to be having connectivity issues... or I am... but nobody's really using either my primary or secondary links right now...)

ok, they seem to be back on-line and happy... 22 minutes left instead of ~ 6 days...)
[T-Mobile, Samsung Galaxy SIII] simpl3lang:
hi, my gf t999 was recently updated to the latest 4.1.2 ....just want to verify that if i use this root66 method, it will not delete anything from her phone? like her apps, contacts, photos, etc. please advice. thanks
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Correct.
[T-Mobile, Samsung Galaxy SIII] simpl3lang:
Thank u

edit: the download broke for me, cant seem to pass the 402mb mark. anyone have a mirror link?
[T-Mobile, Samsung Galaxy SIII] soberarmy:
md5 not matching up?? Tried downloading multiple times. Any help would be appreciated, Thanks
[T-Mobile, Samsung Galaxy SIII] Perseus:
Weird Camera Issue.

For those with SGH-T999, the T-Mo edition of Galaxy S3, a word of caution.

I do not want to Re-Post. So please see my post here.

In Short, T-Mobile 2nd Level Tech Support admitted that the recent Software Update dubbed T999UVDMD5 has caused widespread issues on this phone. In my case, Camera failed. For others Contacts were wiped out, Sound not working, and so on.

According to T-Mo, Samsung is aware of this issue. There is no answer weather this can be fixed with Software or the Camera is permanently damaged. They are offering me Replacement phone since I have Warranty.
[T-Mobile, Samsung Galaxy SIII] simpl3lang:
Are you saying right after you updated it caused the camera issue. I updated my gf's t999 to the new firmware that tmobile pushed and so far no issues with the camera. Could your issue started because you flashed a custom firmware?
[T-Mobile, Samsung Galaxy SIII] Perseus:
I am not sure. Liquidsmooth v2.4 is what I installed. But then I tried to restore my Nandroid too. I might have blamed that version of Liquid. Only thing is the T-Mo rep admitted being flooded with calls after the update. Your GF's case might be a lucky one. I am trying to log on to T-Mobile Support Group but my ID's locked.

Anyway, my point was to provide a word of Caution with regards to the T999UVDMD5 Update T-Mo has out and is on this thread. Your mileage may vary.
[T-Mobile, Samsung Galaxy SIII] the00guy:
Managed to downgrade back to 4.1.1 It was a pain since certain apps needed to have their data cleared and rebuilt (and would incessantly force close while trying to clear them lol) but I'm back up. I miss the new gallery though..
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
In your post you said there's were other posts about problens with MD5, but the link just goes to the liquidsmooth thread.

I have personally not seen enough of any issue to say there is a problem with the firmware or caution folks against using it. I know tmobile confirmed to you there are problems, but they will have some issues with some people with every build they release.

I'm not saying you're wrong, as there could very well be problems with the fw. But I do think if it were a major issue we would see a lot more threads and posts about the same problem over and over. As far as I can tell, most are working fine.

Contacts, sound, camera, etc are things a few people seem to report problems with after every update.

Not trying to argue with you, but just state a different opinion for consideration. I just think we would see a lot more about this stuff if it were a widespread problem. Dont forget too, that more often than not tmobile support only knows what their computer program tells them to know! They have often been wrong on a number of things.

Has anyone else seen these widespread problems? I'm using MD5 now with no issues so far.
[T-Mobile, Samsung Galaxy SIII] eagle63:
Remember the golden rule: most wireless carrier employees don't know anything. Just because some guy at tmobile said people were having problems doesn't mean it's anything out of the ordinary. (the update is working fine for me, fyi)
[T-Mobile, Samsung Galaxy SIII] Perseus:
I talked to 3 different Second Level Tech Supports Plus one Store Tech. FYI.

Doc, I agree with you. For the other problems what I said is based on What T-Mo told me. I did try to search for threads on this problem and others, but did not find any. However, since I ran into it, (may be I am minority) I thought of letting others know. The intent is only to document my issue so if someone searched for it or was considering that update, are informed. That is all.