yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] jaliscojorge:
I hadn't even heard of the efs issues until right after i rooted mine. Then used rom manager for cwm. No problems yet:)

typed from my white sgs3 hungry for some Zen
[T-Mobile, Samsung Galaxy SIII] RaymondPJR:
I'm not finding a lot of information on the problem. As long as it doesn't happen while rooting the phone, I think you are safe as long as the first thing you do is back up the efs partition (devs are unsure if this is the location of the IMEI) I plan to just back up everything, lol. I'm doing it all a$$ backwards. I'm in a coffee shop with dreadfully slow internet. It would've taken 7 hours to download the Rooted ROM, so I downloaded to my phone then will extract it there, then copy to my computer thereby sidestepping 7zip. I don't like any of those Windows applications. I don't use them often enough to remember what I'm doing. Makes me nervous.
[T-Mobile, Samsung Galaxy SIII] fireboypr:
Good luck man, I hope that everything goes well.
[T-Mobile, Samsung Galaxy SIII] rakeshchn:
Mr Robinson would you please make root injected stock firmware whenever t mobile and Samsung like giving us updates...like say jelly bean ;-)

With love....

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] stevessvt:
Supposedly chainfire is possibly releasing triangle away for the US GS3's...so releasing ROMs with root already in them will become unnecessary.

http://xdaforums.com/showthread.php?t=1781104
[T-Mobile, Samsung Galaxy SIII] DenisGuy:
Hi! Thanks for the help. Unfortunately I'm an idiot and I hard-bricked my phone.

And I'm a super-idiot because I'm gonna try again.

Here's the thing:

I'm trying to install cm 10.2 on a t999v Videotron.

I installed, with Odin, root66_VTR_T999VVLUEMK5.7z

You guys are telling me that I need to tap build number 7x. Done.

Then you told me to go to Dev options, Root, and add APP and ADB. There was no root option. However SU was installed and worked after activating the Dev options.

Next problem: the official Cyanogenmod website says that I need to install the T-Mobile version on my t999v Videotron. Fine.

However ROM Manager says that I'd need to install the MetroPCS version of CWM. I did. Then, I installed CWM Touch. So far, so good.

Reboot to recovery and try to install T-Mobile cm10.2. Status 7.

Then, I installed cm10.2 for MetroPCS. Everything boots fine, however the 3g icon top-right wont light up. I get to connect, call and use the internet. However, SMS and Google Play refuse to work.

After ****ing around with it, I lose patience, think foolishly that the only way to install the T-Mobile cm10.2 is to use the T-Mobile CWM. I install that and brick.

NOW, PLEASE, PEOPLE. What's wrong? Is there a cm10.2 I can install on my t999v Videotron? What am I doing wrong (other than forcing a CWM on my phone)?

Sorry for the long post. I just had to vent.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Take a Deep Breath. You could/should have read the instructions more thoroughly. Water under the bridge.

Always be mindful that your Device is T999V. So you should not follow instructions for other variants of T999.

You may wish to follow the De-Bricking thread in Android Development Sub Forum.
[T-Mobile, Samsung Galaxy SIII] sonwon:
LOL, my phone isn't hard bricked. I was just expressing my disappointment with Samsung.
[T-Mobile, Samsung Galaxy SIII] cyclonend:
I have read through the posts, but still have a few questions. I am currently running a completely stock T-Mobile T999. It been updated through OTA with stock 4.3 (T999UVUEMJC).

I am not concerned with warranty. I want to end up running a CM11 Nightly. Can I use Route66 to get there? I would use Route66 to acquire root and then flash a custom recovery. From there I can flash the CM11 Nightly with CWM.

Is this viable option?

Thank you
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes the route is logical. Only thing you must remember is to only use the UVUEMJC Root66.
[T-Mobile, Samsung Galaxy SIII] DenisGuy:
Thanks for that.

However I still haven't found straightforward instructions to install cm 10.2 on my t999v Videotron. Can you point me to a thread like that? The only one I found is an outdated one...
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
I am running the 4.1.2 from the Root_66 T999UVDMD5. I tried flashing the "Gummy" CM Kitkat ROM a couple times from TWRP recovery but it always fails. What am I doing wrong?
[T-Mobile, Samsung Galaxy SIII] Perseus:
We can get to that in a bit. Last you mentioned, your phone is bricked.Is that still the case. If it is not, then please mention current state of Rom, Kernel and Recovery.

Update TWRP to latest version then try.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
I thought I was but I will double check. Thanks
[T-Mobile, Samsung Galaxy SIII] DenisGuy:
I unbricked it and flashed root66_VTR_T999VVLUEMK5.tar. We're back to stock. Everything works and Dev options are activated.

I was going to try Goo Manager as my next option but obviously I'll wait for your precious advice.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Go with Goo. If it says D2TMO version of TWRP 2.6.3.x then go ahead and get it over. Note, I personally am having issues with the latest Goo Manager version in that, it will download the recovery Tar but won't flash it. So use PC based ODIN instead or Mobile Odin. Once you get on latest TWRP, Do

1. Take a Complete Nandroid

2. Follow through and do an NV Backup. This thread will help.

Once that is done, Flash the Correct CM Version via Recovery. D2TMO version of CM will do fine.
[T-Mobile, Samsung Galaxy SIII] DenisGuy:
It's not booting. I'm stuck at the blue Samsung logo. Also, it wont boot in recovery, only download mode.

I Odin-flashed root66_VTR_T999VVLUEMK5.tar then openrecovery-twrp-2.3.1.0-d2tmo. Still can't boot.

What am I doing wrong?

EDIT: Nevermind, got it on the 3rd try. Thanks again for everything.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Flash This Recovery

http://techerrata.com/file/twrp2/d2tmo/openrecovery-twrp-2.6.3.1-d2tmo.tar

Then Flash this CM in Recovery.

http://get.cm/get/cqu
[T-Mobile, Samsung Galaxy SIII] DenisGuy:
Here we go again.

When I install GOO Manager, it downloads and installs openrecovery-twrp-2.6.3.1-d2can.tar

When it does that I get to reboot into recovery, but when I try to install cm 10.2 d2tmo it gives me a "ro.product.device" error.

Then, when I Odin-flash openrecovery-twrp-2.6.3.1-d2tmo.tar, it wont boot into recovery anymore.

What now?

(Sorry guys I'm getting a bit frustrated here.)

---------- Post added at 10:45 PM ---------- Previous post was at 10:40 PM ----------

And I'm one step ahead, again.

I can't boot into recovery using the 3-button method. However it did boot into recovery when I asked GOO Manager to do so.

Now, when I try to flash cm-10.2.0-d2tmo, it gives me the following error: Assert failed: getprop(ro.bootloader)

What now?

:(

EDIT: Aaaaaand my phone is bricked.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
I just installed the latese TWRP with Goo Manager. The first thing I did is run a Nandroid Backup. The second thing I did was try to verify the backup with AFV app. The verification failed saying that the file was not formatted like a Nandroid.md5. I tried doing the backup twice with the same result. Now I am afraid to flash until I can get a verifiable backup.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Before all this began, what did you have on the phone ? At any point in this process, did you happen to flash a Stock Based Rom if so what? If the phone still boots, install Getprop app and then Lookup what it has to say for ro.bootloader.

Please don't call it a brick unless you can't even get into Download mode. Anything else is called Soft Brick.

What TWRP Version did you flash ? When you do Nandroid, enable compression and remove MD5 generation. Then try either Nandroid Manager to verify the backup. If you do make Nandroid with MD5 Enabled, use Md5 Checker app to do so.
[T-Mobile, Samsung Galaxy SIII] DenisGuy:
root66_VTR_T999VVLUEMK5.tar (Which is 4.3, root66'd)

T999VVLUEMK5 (which is the root66 I installed.)

It wouldn't even give any signs of life. I had to re-follow the De-Bricking thread in Android Development Sub Forum, like you said earlier.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
I installed the latest version because I was unable to flash a ROM. I just installed Nandroid Manager and it verifies the files. The problem must have between with the app I used. I contacted the developer and he is already working on the fix.

It's it generally recommended not to enable md5 generation?

Now on to flashing a Rom!

Thanks!
[T-Mobile, Samsung Galaxy SIII] DenisGuy:
Alright, people, so I think I'm giving up.

Here's the conundrum:

I have a t999v Videotron. It had already been updated to Android 4.3 when I got it.

According to all I read, the right version for TWRP, CWM and CM for my phone is the d2tmo version.

After I install a recovery (TWRP or CWM) for d2tmo on my t999v, the phone refuses to boot into recovery, whatever I do.

ROM Manager suggests I install the MetroPCS version of CWM.

GOO Manager suggests I install the d2can version of TWRP.

In either case, I cannot install CM10.2 for d2tmo using these recoveries because it gives me Status 7 errors.

Also, whatever I do, the root66 I installed loses root after the first boot. There's no saving it.

I tried many, many different things, and now I'm tired.

Thanks for all of your help.

If anyone sees what I'm doing wrong, please let me know!
[T-Mobile, Samsung Galaxy SIII] Perseus:
Well that depends. If you were going to move the Nandroid from Device to Device or wanted to make sure its valid before restoring it, then you'd want MD5. Otherwise no need. But compress you must.

That should not give any Bootloader issues on CM unless you had restored or flashed a prior version of Root66. Since you didn't, I'd suspect the CM. Can you try some other Rom such as Pac Rom, LiquidSmooth or Slim Bean ?

When you say you can't boot into Recovery after flashing D2TMO version of Recoveries, was that despite using the 3 button combo ? Would you say combo of just the Root66 Rom and Custom Recvoeries were able to co-exist ? Doesn't matter which Custom Recovery you use. Either D2Can or D2TMO.Just don't do MetroPCS.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
I always verify the Nan right after I create it but I have never compressed. Why do say I must compress?

Thanks
[T-Mobile, Samsung Galaxy SIII] Perseus:
The Recovery makes a tarball after compressing. Not only makes for less space on the SD Card, but makes efficient to manage.

This is getting Off Topic. If you have additional questions, please PM me.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
Thanks
[T-Mobile, Samsung Galaxy SIII] DenisGuy:
Yes, exactly. When I hold the 3 buttons, it just boot-loops.

Exactly. The auto-suggested recoveries (TWRP d2can and CWM MetroPCS) will boot fine, I can also get in them using the 3-button combination, and I can flash the CM versions that go with the recoveries. However when I get in CM from there, I can't send SMS's, Google Play doesn't work (says it can't connect) and there are no bars in the cellular signal triangle. Back to square one.

Unfortunately I don't have more time to spend on that little machine. It's a shame. I'll trade it for a i9300 I think...

Anyway, thanks again.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
I'm running UVDMD5 root66 and have TWRP. I've tried several times to flash CM kitkatI from this forum. always get stuck in boot screen. Should this be able to flash?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Please post in the appropriate Rom's thread. Not being able to flash CM isn't really an issue of Root66.

To your issue, all I can say is please make sure your Recovery is the latest version.
[T-Mobile, Samsung Galaxy SIII] Christopher4tw:
Root with 4.3 installed?

I currently have T-Mobile's stock 4.3 UVUEMJC on my SGH-T999, and I was wondering if this root method will still work (even with the Knox issue). It may have been clear in the OP, but I just want to be sure, as this is my favorite of the devices I own, and do not want a brick because I didn't ask. And the phone is unrooted and never been rooted, btw.

With Future Thanks,

Christopher4tw
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
Well I posted here because I am running the root_66 and thought my problem may be related. BTW, I took your advice and updated TWRP. Now I the flash process succeeds in recovery but I get stuck at boot. Thanks again.
[T-Mobile, Samsung Galaxy SIII] Proxin:
Edit: Deleted
[T-Mobile, Samsung Galaxy SIII] dja2k:
If my friend's S3 has the Root66 T999_UVDMD5 Official JB Firmware - Latest JB 4.1.2 Firmware, would I encounter any problems just Odin the latest Root66 T999_UVUEMJC Official JB Firmware - Latest JB 4.3 Firmware. Thanks!

dja2k
[T-Mobile, Samsung Galaxy SIII] ortind200:
ok guys.. those of u who upgraded to 4.3 and want to root ur S3s with root66 without issues, u still can. just odin root66 and u will all be rooted. just remember that if u install CWM that u will trip the flash counter and ur warranty will be broken. those with old S3s shouldnt worry if u bought ur phone more than a yr ago since the warranty has expired. u got nothing to lose.

im glad to return after a long hiatus.. looks like someone had to kick me out cuz they couldnt take the truth.. i feel like tupac or jesus. feels good to be back tho.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes it will. The only downsides is that, it will flash latest Bootloader in the process. If you are ok with that, then go ahead. Otherwise use UVDMD5 Root66 image.

Please do a Factory Reset in Recovery then re-flash.
[T-Mobile, Samsung Galaxy SIII] Christopher4tw:
Thanks

Thanks, I wish I would have read that warning a little earlier, as I just rooted the UEMJC 4.3. Do you know if a CM 10.2 flash is safe with this bootloader? I had a very easy and successful root (thank you Mr. Robinson) and have the latest TWRP recovery installed.
[T-Mobile, Samsung Galaxy SIII] scooter1942:
So I haven't been on xda in a while, and my gf tells me her verizon S3 has an update. I decide to check back here and see if anything was going on with mine, and found this mess. I tried to make sense of all the posts in the past couple weeks, but I still have a couple questions. First, if I decide to update using odin to go from UVDMD5 to UVUEMJC using the image found here, will it retain root, or is that still being tested? Second, could anyone provide links for further reading about the new changes and specifically the warranty bit I've seen mentioned a couple times?
[T-Mobile, Samsung Galaxy SIII] calisoldier83:
Help please!

I updated to 4.3 using the T999LUVUBMK4 rom in this thread. All was dandy, and it booted fine. I thought I could do a factory reset from the settings menu in the OS. After performing the factory reset, it sent my phone into boot loop. I tried flashing CWM and factory resetting from there, but I run into the same issue.

Tried reflashing the rom multiple times and it still is stuck on the T-mobile white screen.

I'm sure there's a straightforward fix for this since I can access ODIN and flash stuff. Just not sure if it's documented because of the infancy of the 4.3 rom.

I'm coming from T-mobile stock version 4.2.2.

NM it worked after doing the data wipe on the standard bootloader. I realized I tripped the warranty bit after playing with CMW, lame.

BTW, not sure why De-Bloater is being advertised if it's not applicable for 4.3?
[T-Mobile, Samsung Galaxy SIII] Perseus:
CM 10.2 should be safe enough. Just never try previous versions of Root66 now. In particular, any prior OTA Firmwares that include older Bootloader should not be flashed.

The UVUEMJC image here works just fine. It will Update you and provide Root. Unfortunately Samsung has introduced some problematic items in this update, so you might be better off not updating. This post seems good enough to explain some details.

Any Stock Rom does have Bloat. So you are better off without it.
[T-Mobile, Samsung Galaxy SIII] scooter1942:
I understand it will provide root, but I read some posts where people claimed that root access had been lost after a certain amount of time. Though, I am curious, what are these "problematic items" that you speak of?
[T-Mobile, Samsung Galaxy SIII] ortind200:
those of u who upgraded to 4.3 and want to root ur S3s with root66 without issues, u still can. just odin root66 and u will all be rooted. just remember that if u install CWM that u will trip the flash counter and ur warranty will be broken. those with old S3s shouldnt worry if u bought ur phone more than a yr ago since the warranty has expired. u got nothing to lose.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Oh the Root is pretty stable now. It was not permanent before in the process. I'd not worry about that one. For the problem areas, see the link in last post.
[T-Mobile, Samsung Galaxy SIII] culson_35:
Works great for me
[T-Mobile, Samsung Galaxy SIII] headsh0tshurt:
thx. will definitely try this when i get home tonight.
[T-Mobile, Samsung Galaxy SIII] lanzero:
Welcome back Ortind, man. Dont let any mods bully you. Everyone knows their egos are bigger than their brains.

Would like to get your insight on something. Have you had any issues with root66?
[T-Mobile, Samsung Galaxy SIII] Mekanikz:
WIND June 2013 - 4.1.2 JellyBean download is not working

Edit: It's working now.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Try this link for Wind VLDMF2 Firmware. Thanks to [MENTION=4081205]DocHoliday77[/MENTION] for hosting.
[T-Mobile, Samsung Galaxy SIII] Mekanikz:
Thanks bro. It seems it's working again now though. I think it was an issue with their current site updates.
[T-Mobile, Samsung Galaxy SIII] X-Nemesis:
Can you flash this with TWRP instead of Odin? If not, is there a way to flash with TWRP and just do a dirty flash coming from the 4.1.2 root66 rom?
[T-Mobile, Samsung Galaxy SIII] Perseus:
No and No.
[T-Mobile, Samsung Galaxy SIII] yeeahnick:
Just letting you know T999VVLUEML2 is out for videotron, would be nice to have it root injected! Thanks!
[T-Mobile, Samsung Galaxy SIII] cuzmonote:
is this our second 4.3 update ... T999VVLUEMK5 ---> T999VVLUEML2

EDIT : nevermind ...wifey gave me the answer lol

what did they change exactly ?? any idea ??
[T-Mobile, Samsung Galaxy SIII] yeeahnick:
yes this is our 2nd 4.3 update, no idea what was changed because im only using the new modem with CM11. I guess they are bug fixes and performance improvements.

MK5 = 19.11.2013

ML2 = 27.12.2013
[T-Mobile, Samsung Galaxy SIII] Perseus:
There were reports of users bricking their phones when applying this update via Kies. Possibly that's what is fixed.
[T-Mobile, Samsung Galaxy SIII] yeeahnick:
i thought the bricking issues were only with the i9300 models, guess i was wrong thanks for the info!
[T-Mobile, Samsung Galaxy SIII] calexchelse:
1: yes

2: no

3: yes

However, once you have custom recovery, most, and I think all but one, of the custom Roms are knockless
[T-Mobile, Samsung Galaxy SIII] yeeahnick:
If you go on page 131 and read comments 1303 and 1307 all your questions are answered =)

If i read corretly root66 does not have Knox but it has the bootloader that will flag 1 of the counters, the 2nd counter will be flagged when flashing a custom recovery.
[T-Mobile, Samsung Galaxy SIII] flip3601:
U won't trip the flash counter but the warranty bit will switch from 0>1. Well that's what happened to me. Not sure about everyone else
[T-Mobile, Samsung Galaxy SIII] Perseus:
It is my understanding that Root66 does contain KNOX.
[T-Mobile, Samsung Galaxy SIII] yakabud:
That's the answer on your question #1
[T-Mobile, Samsung Galaxy SIII] masondoctorjt:
I believe the ROM does not contain Knox, BUT the bootloader still has the Knox warranty bit, so that if you flash a recovery it will trip to 1 and cannot be reversed. Somebody correct me if that is wrong.
[T-Mobile, Samsung Galaxy SIII] dave843:
I updated my phone (T-Mobile original Galaxy S3) to 4.3 using Kies, so I am on the latest official build for my phone.

I would like to root my phone, so I came here, and followed the directions in the first post:

* I downloaded Odin 3.07

* I downloaded the root66_TMP_T999UVUEMJC file and verified the md5

When flashing with Odin, it starts and then fails. After it fails, I have to do a firmware recovery in Kies before the phone will work again.

The messages in Odin follow:

<ID:0/004> Added!!

<ID:0/004> Removed!!

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

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

<OSM> Please wait..

<OSM> root66_TMO_T999UVUEMJC.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> sbl2.mbn

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

<ID:0/004> sbl3.mbn

<ID:0/004> aboot.mbn

<ID:0/004> rpm.mbn

<ID:0/004> tz.mbn

<ID:0/004> boot.img

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

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

<ID:0/004> Removed!!

<ID:0/004> Added!!

<ID:0/004> Removed!!

Does anyone know what I'm doing wrong? Or how I can root my phone?
[T-Mobile, Samsung Galaxy SIII] heiNey:
i have tmobile, and my phone currently has T999UVDLJA. which one should i flash? the tmobile image, or the tmobile LTE image?

im assuming it's root66_TMO_T999UVUEMJC_2.7z, but want to make sure
[T-Mobile, Samsung Galaxy SIII] culson_35:
Yes

Beanstalks 4.4.2 (sgh-t999l)
[T-Mobile, Samsung Galaxy SIII] dave843:
I have tmobile, and my phone currently has T999UVUEMJC. Which version should I flash? I'm assuming it is the root66_TMO_T999UVUEMJC, but that didn't work for me.
[T-Mobile, Samsung Galaxy SIII] Perseus:
You assume correct. If it does not work, you will have to elaborate and provide specific information in order for us to help.
[T-Mobile, Samsung Galaxy SIII] dave843:
Here is more information.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Either you can make sure you have correct Dowload mode drivers setup before you start Odin and put in Download mode. Or otherwise you could flash a custom recovery and then flash a Superuser zip.
[T-Mobile, Samsung Galaxy SIII] dave843:
Is being new to rooting a problem?

I very carefully followed the directions given in the first couple of posts to root my phone, and it didn't work.

In the post you quoted, I tried to give enough information to get some help rooting my phone.

Can you help troubleshoot the issue?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Did you follow my last post ?
[T-Mobile, Samsung Galaxy SIII] dave843:
Actually, I tried a different computer (10 year old Dell laptop running XP), and it worked.

Thanks for your help.
[T-Mobile, Samsung Galaxy SIII] dave843:
No, it is Windows 7 Ultimate, but that is running in a virtual machine. The VM is running on my 2013 Macbook Pro using VMWare Fusion 5.0.3. This setup works fine to update the firmware using KIES, but does not seem to work with Odin.
[T-Mobile, Samsung Galaxy SIII] Perseus:
ODIN uses ADB. So it needs physical Port connectivity.
[T-Mobile, Samsung Galaxy SIII] dave843:
I can ADB to my phone just fine from my VM.
[T-Mobile, Samsung Galaxy SIII] timmyd463229:
im trying to root my brothers gs3 that is on stock 4.1.2 and im flashing the tar file with odin and it seems stuck at setup connection? any ideas..... never mind figured it out
[T-Mobile, Samsung Galaxy SIII] jtl_777:
Question about the new bootloader

I updated to 4.3 and had trouble with MJC modem, I flashed a backup I had of 4.1.2 and also reflashed the MD5 modem and I still have 4G data and everything is back to normal. Should that have bricked my phone or is it only flashing a past bootloader that will brick it? I'm just making sure it's safe to continue flashing 4.1.2 roms and to keep the MD5 modem with the newer bootloader. I DEFINITELY don't need a SGS3 paperweight hahaha.
[T-Mobile, Samsung Galaxy SIII] masondoctorjt:
I believe you can flash older than 4.3 ROM's through recovery and you'll be ok but if you do it through Odin, many times those ROM's includes the older boatloader, and that is what bricks the phone. But please get a second opinion before taking my word as fact.