yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] nirogu325:
I thought I told you NOT to use ODIN again, but to flash normally via recovery...
[T-Mobile, Samsung Galaxy SIII] krazyq:
I think I might not have been clear in my earlier post.

I was able to find a stock rom (4.0.4) and flash that by doing a restore in custom recovery.

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

So then I was at 4.0.4

I tried using odin again since you mentioned that the security was on 4.3

Since I'm not on 4.0.4, Odin should work, right? But it didn't.

I'm fine since I'm on the 4.0.4

I just tried flashing it again via odin to see if it would work but it still doesn't.

Hopefully that made sense
[T-Mobile, Samsung Galaxy SIII] masondoctorjt:
If you are above 4.3 I do not beleive you can go below that.
[T-Mobile, Samsung Galaxy SIII] krazyq:
I was able to get it to 4.0.4.

I posted a link in my earlier post on the instructions I followed to do it.
[T-Mobile, Samsung Galaxy SIII] Perseus:
What's your Baseband ?
[T-Mobile, Samsung Galaxy SIII] masondoctorjt:
Yeah, sorry, I replied to your post before I read the next page.
[T-Mobile, Samsung Galaxy SIII] krazyq:
T999UVUENC2 which is 4.3 so that's weird because it says 4.0.4 for the Android version and the build no. is T999UVALEM
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
you are confusing the firmware (boot loader and modem) with the rom. once you go to the newer bootloaders you can not flash back to older ones with odin or you brick.

you can however, flash with recovery an older rom on the newer bootloader and modem. most of the time it works ok.
[T-Mobile, Samsung Galaxy SIII] Perseus:
^^^ What He said.
[T-Mobile, Samsung Galaxy SIII] krazyq:
So does this look right?
[T-Mobile, Samsung Galaxy SIII] EmpiricalDepth:
I take that as a no? (I was hoping to find this too)
[T-Mobile, Samsung Galaxy SIII] qwerty3656:
Sorry for confusion. It has been a while since I have played with ROM's. Could someone give me some guidance. I am currently rooted on T999LUVUBNC1. I am trying to get to a rooted status on T999LUVUBNF4.

1) Can I accept the OTA software update for T999LUVUBNF4 and then just re-root (or is this a problem because I am rooted)?

2) If not #1, what would be the best way to get my phon on T999LUVUBNF4?

Thanks
[T-Mobile, Samsung Galaxy SIII] EmpiricalDepth:
I used easyroot before mine updated to NF4 and lost root after the update. I'm still waiting for someone to tell me if flashing route66 NC1 is going to be ok. I didn't notice a bit of difference going from NC1 to NF4 except losing root. Not worth updating IMO. If you think theres a good reason to, please let me know.
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
you can't odin back to older firmware. I had nf4 on my t999l. I odined twrp for t999 then flashed root. then wiped system and flashed a different rom. but you could stay stock rooted with twrp. let supersu disable knox once you reboot after rooting. if I remember right.
[T-Mobile, Samsung Galaxy SIII] nirogu325:
???

1. Flash TWRP

2. Flash SuperSU .zip

3. ???

4. Profit!

Also, having the latest bootloader brings more compatibility for custom AOSP ROMs. You don't lose anything whatsoever.
[T-Mobile, Samsung Galaxy SIII] nae10135:
I am having serious difficulty getting ODIN 3.07 to flash ANY tar.md5 file to my T999. It just doesn't do anything after "downloading to device". I left one attempt up overnight, and ODIN closed but the phone was still in download mode. Can anyone help me out?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Either the ADB Drivers are not correctly installed or are corrupted. Please remove any trace of the drivers and follow the instructions from the Root66 thread linked in OP.
[T-Mobile, Samsung Galaxy SIII] fdecker:
Need zip of T999UVUENC2 for TWRP flash

My T-Mobile Galaxy S3 was sitting and charging and I saw it was frozen on the second screen (The larger Galaxy S3 logo) I could not get it to boot. I tried to go into safe mode, but it won't go. I can get into my TWRP recovery mode, but it says there is no OS. It is like a virus wiped my system.

I put the root66_TMO_T999UVUENC2.tar.md5 file onto an external SD card to use TWRP to flash it, but it doesn't see it. How do I get or make a zip file? Do I just zip the md5, or do I have to extract it and zip it up somehow.

I also tried to used Odin 3.09, but as soon I press start, it says wirte fail. So I am stuck no matter what I do. I cleared the cache and dalvik cache, but that didn't help. Thanks.
[T-Mobile, Samsung Galaxy SIII] audit13:
It's possible that the flash memory in the phone has failed. Did you try using Odin to flash back to stock? TWRP cannot flash tar files, only Odin.
[T-Mobile, Samsung Galaxy SIII] fdecker:
I haven't yet. This is so time consuming, I have to try things one at a time. I am guessing because the file system can't mount, that is why Odin isn't working, but who knows. I saw there is a way to go into terminal mode and typ commands to reset partitions. I may have to try that at some point. I was so hoping to NOT lose my data, but oh well.

---------- Post added at 02:00 PM ---------- Previous post was at 01:59 PM ----------

Do you know how to take a tar.md5 file and create a zip in the right format? Do I untar it and then just zip up what it extracts? Or I need to find a link to the root66 tar I have that is already in zip format
[T-Mobile, Samsung Galaxy SIII] audit13:
The stock ROMs on sammobile.com are zipped. Just unzip the file and you will get a tar file to flash in Odin. Flashing via Odin will not automatically wipe data.

Since you cannot access the data partition via twrp, I know of no other way to access the data. You could try looking in the i747 xda forum.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I'm baaaaaccckkk!!!!!

Hey everyone!!! I am so sorry for my extremely long absence. I won't get into reasons and excuses here, but basically I simply had no means to use the internet for some time. (no I wasn't in jail or anything like that!!!)

Things are looking up and I am hoping to get back to being active around here again. Though I'm guessing there aren't many S3 users around these days.... I sure have missed it though....

Well, for those who haven't seen, there has been new firmware released for the T999, T999L and T999N. It has been posted in the OP. I may make a stock rom out of it here in the next few days, but no promises yet. I will get the modems posted as well. This is still just 4.3 JB firmware btw. Not sure what the reasons are for its release as I have seen no changelog as of yet.

Oh and sorry if the format of the OP got a little screwy. The edit post function does not work like it used to so I am going to have to take some time to figure why it wont do what I want it to do! But the links are there and should be just fine.

Enjoy!
[T-Mobile, Samsung Galaxy SIII] Perseus:
Good to see you back. We all know RL can be uncooperative monkey wrench at times.

I didn't realize there is a new Firmware released by Sammy. I will take a look as well. I am sure the Stock rom would be welcomed by many. Yes we still have a loyal group on this device yet.

Will you by chance inject Root in UVUEOH1 as well ?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Hey bud! Good to see you still around!

RL definitely had it in for me for a while there! But hey, life's a struggle at times, we all have things to overcome on the journey!

As for the root injected, are you referring to the root66 builds? Those were always done by [MENTION=3355398]mrRobinson[/MENTION]. I never was able to get it down myself. I will contact him and ask if he can assist one more time though.

I'm currently in the middle of a reformat/reinstall on my computer. After that I have to fix my own phone... (another glass and motherboard replacement). Once done I'll get a stock rom tested and released. (it's half done tbh, but I had to stop to fix my computer)

I'll also get the modems posted as soon as I'm done with the computer. Finally, I believe [MENTION=2972841]enewman17[/MENTION] updated S3Rx recently, so I'll check it out and if needed will make any changes needed to port it over here. (it's probably good to go as is though)

After my little hiatus, I am very much looking forward to working on this stuff again!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Oh and BTW, don't forget about Towelroot guys. It should still work on the OH1 firmware since it's still a 4.3 build. Probably a lot better than trying to get another root66 build out at this point, imo.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
If towelroot still works, stick with that. I'd hate to resurrect those old tools.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Thank you. I wasn't sure but be happy to look into TowelRoot with this code.

How come, this August build didn't get pushed out to phones I wonder ?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Maybe there just aren't enough S3's still on the T-Mobile network to warrant it.
[T-Mobile, Samsung Galaxy SIII] nirogu325:
It got pushed to a spare T999L I have, it installed but it never installed a newer modem unlike when I manually flashed the firmware to my main T999 unit. Both bootloader and modem now end in OH1 on my T999 (I never checked if the bootloader updated on T999L).
[T-Mobile, Samsung Galaxy SIII] Perseus:
Ah well. Modem could be the only thing that'd make me flash since the last modem NC2 plays funny on LP. :/

Say, how'd you root OH1 ? Towle or Custom Recovery ?
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Oh, I never stayed on stock OH1. I quickly ODIN'ed TWRP and did a nandroid restore of my previous functioning TW ROM (S3Rx). I still haven't tested the OH1 modem outside TW.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Thank you Nitrogu!

Doc you were right. Towel Root did the job in 1 second flat. I am going to flash TWRP anyway.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
For anyone who still has the T999V and is keeping up around here, a new 4.4.2 build was recently released. I'll have it and the modem posted later today.

The interesting thing this time is all carriers builds are identical now. So one firmware build for all instead of each carrier having slightly different ones.
[T-Mobile, Samsung Galaxy SIII] tw39515:
If they are all the same was there a tmo version with wifi calling? I have been away for a while too. Thanks Tw
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Afraid not. Just all the T999V models were the same. (They all had identical file hashes).

The T999 is different. In fact, the T999 is still stuck on 4.3, while the T999V got 4.4.2.

Plus, WiFi calling is very carrier specific. Even if you had a T999 it would only work if you were with T-Mobile.
[T-Mobile, Samsung Galaxy SIII] tw39515:
OK that's what i thought, i have tmo. probably time for a band 12 phone anyway. thanks
[T-Mobile, Samsung Galaxy SIII] freeridindirtbiker:
Great to have you back Doc.

If you were still wondering, the OH1 update focused on patching the Stagefright vulnerability that was made public in late July. According to T-Mobile, that was the only change made in the update unfortunately.
[T-Mobile, Samsung Galaxy SIII] xdamember143:
Hey guys how do I do this with twrp/ coming from a lollipop rom?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Firmware is only for flashing via Odin. You can't use it in TWRP.
[T-Mobile, Samsung Galaxy SIII] AjvarXX:
My update by Odin seems stuck. Too long, should I disconnect?

Hey guys. I am using Odin 3.07 from the 2-nd post and it's been 20 minutes at least (if not 40) but I still see Frimware flash start... aboot.mbm

I first connected phone to computer and then launched Odin, could that bring this? Also drivers are v1.5.45.0

Phones screen remains intact - Green Android, text info in top left and DOWNLOADING... Do not turn off target! Warning, same after boot.

How long should it take? I know that firmware is huge but shouldn't there be few steps flashing in Odin so I wouldnt see same aboot.mdn for 30-45 minutes?

P.S. I am flashing it because it couldn't get booted and couldn't enter recovery.

/it didn't start the flashing. With another driver when I tried 4.1.1 it gave me

software revision check fail t999 fused 1

Then I tried latest official firmware and got this

<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUEOH1_T999TMBEOH1_T999UVUEOH1_HOME.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> SingleDownload.
<ID:0/004> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
[T-Mobile, Samsung Galaxy SIII] Perseus:
Did you set the phone in Download/ bootloader mode and THEN plug in before opening Odin ?
[T-Mobile, Samsung Galaxy SIII] AjvarXX:
Well, for the last 10 hours of the last day of this Year I did everything with this phone including different combinations of ROMs (4.3 and 4.1) Odins (3.07/3.09/3.10) and Samsung drivers (.09 and .45).

Usually I launched Odin, launched phome in Download mode, connected phone, set AP/PDA and then press Start.

With older ROMs I get typical error because it's impossible to downgrade from 4.3. But with 4.3 ROMs it just fails.

I appreciate for help. I am thinking to use debrick image on the microSD card if it helps me. But I am not sure if it helps of if it is good idea because my only card >16GB is semi working.

Did somebody have same problem with a way to solve it? Because I read many similar things but there was no CM or other non-official ROMS on this phone.
[T-Mobile, Samsung Galaxy SIII] Perseus:
I am missing something here. Did you have some other problem, for which you chose to Odin ? If so please elaborate. I thought you''re just doing ODIN so you get latest firmware.

There's Definitely CM for this device. CM is not per Rom Basis. Its versioned per android version.
[T-Mobile, Samsung Galaxy SIII] AjvarXX:
Sorry if didn't tell important info. Phone is soft bricked and I didn't do it. My father just dropped this phone with another new one into New Year parcel saying that "it just broke". He is one of those who doesn't even know how to enter recovery mode so he wouldn't install any unofficial mod. Looks like phone bricked when auto-updating itself or whatever.

It doesn't enter recovery showing blue text message "Entering recovery mode" but then fails and is trying to reboot... with stuck logo of course.

So I was just trying to fix this soft bricked phone flashing official ROMs from this thread without a success. Should I go to a different subforum or create new topic here? Are here many devs who still browse SIII topics? Thanks.

P.S. I am not some reseller/repair manager or whatever of this sort.
[T-Mobile, Samsung Galaxy SIII] Perseus:
You are in right place. I was just trying to ensure I have complete story so that I can give a better answer. So, here's the thing. If it was a failed update, your Partitions might be corrupted.

1. First and foremost, make sure you have a D2TMO by looking at the Sticker behind Battery. It should say SGH-T999. As you might be aware, there are 6 known US Variants of this phone. Get the right Stock firmware for the phone. Needless to say use the very latest firmware for the device.

2. The Drivers could be wrong. There's a link to Right and updated drivers in [MENTION=4081205]DocHoliday77[/MENTION] 's signature. Close Odin, Install them, then put the phone in download mode and connect to PC. All the time leave Odin closed. Reboot PC and then try Odin. If you still have error. remove the Driver completely from Windows including the files in c:/windows/system folder, reboot and repeat the install.

3. If your partitions are indeed corrupted and you keep getting errors, despite step 2, then you need to grab a PIT file to be used with Odin at the same time as you try the Stock Firmware. PIT files for all US SGS3's
[T-Mobile, Samsung Galaxy SIII] AjvarXX:
I will try again now but you should know:

1. When I try to use PIT + stock ROM I get red "Secure Check FAIL: PIT" text message in the phone and Odin error. I assume it is "kronos" or "knox" or whatever Samsung's security thing which prevents from repartitioning. I really think it is messed partition table but how can I force repartition?

2. I always uninstalled drivers by Uninstall Tool which logs installation and deletes everything which was installed.

ADDED: It's funny that I have exact same errors as this guy here. his error was because he was using 999L but tried 999 roms and pit file. I am so desperate that soo I will try 999L files too even though it's written SHG-T999.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Knox can mess things up. But not the way you are describing. Did you check the sticker behind Battery ?
[T-Mobile, Samsung Galaxy SIII] AjvarXX:
Yes. Also when I enter Download Mode it clearly says it's SGH-T999 - that is what stopped me from using another firmware.

I am trying Kies now, I chose Iinitialize and flash, typed SGH-T999 and S/N, now it asked me to enter Download Mode and it's downloading latest firmware. But yesterday it finished with "unexpected error" and didn't give me a code which I could enter when choosing Emergency Firmware Flash in Kies.

What I think is... that PIT file on 4.1 has been changed since phone was updated to 4.3 and that is the reason you can't downgrade without bricking. What do you think about that?

Maybe just somebody on 4.3 should upload his PIT and we compare?

P.S. Also it is written on the back 16GB/12GB so I am using right size pit too. It's my 3-rd Android phone.

ADDED: Yep, after Kies downloads 911MB file of OH1 firmware it gives notification of "Unexpected Error" at 0% of flashing firmware and tells me that I should continue to use Emergency Flashing procedure. But it gives me no code and I see zero entries in Emergency Flashing window.

BTW, why it is just 911MB? I couldn't unzip it with 7-zip.

ADDED 2: Also I can flash recovery through Odin successfully but that gives me nothing because I still can't enter it.

ADDED 3: OK, I can be officially announced as morron. I just found out that t999 pit file I downloaded somewhere actually isn't for T999. I don't know how that happened (broken link or I misclicked link) because I definitely was looking for T999 16GB pit... but now I looked at 32GB pit file and saw that it is 3KB size instead of 8KB and yeah, I found the proper pit file.

Anyways, now I have no Security Check FAIL: PIT, now it just doesn't want to flash as usual.

Will have to do all over again: different sets of drivers, Odins and ROMs. But I have a feeling it is still not gonna be flashed.
[T-Mobile, Samsung Galaxy SIII] Perseus:
The reason you can't go back is that the bootloader now contains an eFuse. It will blow if you tried to downgrade the bootloader. That hardbricks the device.

From what you have tried, I think you might be trying to flash the pit file on its own in Odin. It doesn't work that way. You will have flash the Firmware and the pit file at the same time in Odin. Make sure you confirm and reconfirm both the files, since wrong files will hardbrick your phone.

If this fails, please review [HOWTO] UnBrick T-Mobile S III QHSUSB_DLOAD w/Video Walkthrough
[T-Mobile, Samsung Galaxy SIII] AjvarXX:
My problem is that I can't enter Recovery. Even when flashing Recovery with PIT. I believe I need to Wipe DATA and CACHE from Recovery but I can't enter.

Today I tried to flash PIT + Recovery (both stock and TWRP), PIT + ALL stock ROMs with different drivers and Odins.

I also tried Erase NAND + PIT + Recovery as well as Erase NAND + PIT + ROM. Whenever I try Erasing NAND I see blue text on the phone "Erasing DATA" but it obviously does nothing hence I see error in Odin.

I see same blue text "Entering recovery" when I hold Vol.Up+Home+Power yet it can't load to Recovery and just reboots after that.

I have a feeling that my father told that he brought this phone to "technicians" but they did not repair it. I guess they Erazed NAND without wiping Data and Cache but this is all speculations.
[T-Mobile, Samsung Galaxy SIII] Perseus:
err, Ahem, Odin can not Flash any Roms. Period.

What you should be doing is flash PIT+Stock Firmware from OP. That's it. Anything else will fail.

By stock firmware I specifically mean the T999UVUEOH1_T999TMBEOH1_T999UVUEOH1_HOME.tar.md5. This is inside the zip file called T999UVUEOH1_T999TMBEOH1_TMB.zip downloaded from

https://www.androidfilehost.com/?fid=24052804347821128
[T-Mobile, Samsung Galaxy SIII] AjvarXX:
​

Yes, forgive me my way of spelling. By ROM I mean stock firmware. I tried latest 3. Will post a video of doing this. Perhaps this will hekp.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Can you post Odin's log when you tried to flash T999UVUEOH1 as PDA and PIT file in PIT ?
[T-Mobile, Samsung Galaxy SIII] AjvarXX:
Nothing unusual, I would post it earlier otherwise.

<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUEOH1_T999TMBEOH1_T999UVUEOH1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

It's the same with unbrick microSD card inside and without.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Either your Drivers are clobbered or the failed update seriously messed up your Partition table. Create a Thread under Q&A, and others who have gone through this might be of help.
[T-Mobile, Samsung Galaxy SIII] wulfie66:
UVUENC2

I'm on OctOS-M and want to go back to stock, since my baseband version is UVUENC2, do I also have to flash the same stock version UVUENC2?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes, that or UVUEOH1. No prior versions though.
[T-Mobile, Samsung Galaxy SIII] wulfie66:
do we still have to use triangleaway to reset our counter or is that a thing of the past now?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes we still do. But for any firmware 4.3 and beyond, its pretty much useless.
[T-Mobile, Samsung Galaxy SIII] wulfie66:
one last dumb question, if we flash the root66 variant via mobile odin, do we need to select everoot since this version is already rooted?
[T-Mobile, Samsung Galaxy SIII] Perseus:
There is no such thing as a dumb question. Understand that we all were Newbie at one point or the other. (This is different from Noob by the way)

You are right don't need to select Everoot. Also I wouldn't flash this firmware with Mobile Odin. Go with PC based Odin.
[T-Mobile, Samsung Galaxy SIII] wulfie66:
why PC based Odin instead of Mobile Odin?
[T-Mobile, Samsung Galaxy SIII] Perseus:
The Stock firmware is going to wipe, among other things, modem and internal memory, both of which are active when the phone is on. There is a potential for things to go wrong during the flash.
[T-Mobile, Samsung Galaxy SIII] wulfie66:
so I know it's been said that since 4.3, triangle away and your flash counter isn't really important, but what chances of a brick do I have if I don't reset my flash counter and flash the root66 variant of this? The reason I ask is because I've run triangle away and it resets my flash counter, but as soon as I reboot it goes back to 1. I'm assuming that this is because I have TWRP flashed as well?