yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] el_garicimo:
Ok, that makes sense. I'm having trouble flashing the custom recovery though--downloaded the d2tmo cwm from Docholiday 77's sig, but flashing the recovery is kind of confusing me...can you point to some recommended tutorials?

---------- Post added at 09:29 AM ---------- Previous post was at 09:05 AM ----------

specifically I've been trying to do this method http://www.addictivetips.com/mobile/how-to-install-a-custom-recovery-to-an-android-phone-device/ , using the flash image, but when I get to these instructions:

"

5. Open a Command Prompt window on your computer and enter the following commands:

adb push c:\flash_image /sdcard/

adb push c:\recovery.img /sdcard/

adb shell

su

mount -o remount, rw /system

cp /sdcard/flash_image /system/bin

cd /system/bin

chmod 777 flash_image

flash_image recovery /sdcard/recovery.img

"

At the "cp /sdcard/flash_image /system/bin" , I get " sh: cp: not found "

I realized that was because I didn't have busybox installed, so I installed that and got past that step... but now when I type the LAST command,

"flash_image recovery /sdcard/recovery.img"

I get

"error scanning partition: No such file or directory"

So close but so far...why is installing a custom ROM so difficult?! I guess SGS3 can't use the fast boot because it doesn't come with a fast boot loader, becuase samsung made it that way, so you have to use odin?

If that's the case, which odin TAR file will have the equivalent cwm to d2tmo ?

Sorry, this has de-volved into a bit of a rant at this point (have been chugging on all of this stuff for like 18 of the past 24 hours)...gotta go to work now :/
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Those instructions are for a recovery.IMG, and while they work if you unpack everything, its a ton of extra work and huge room for user error.

Recoveries for this phone are packaged as a tar file to be flashed in Odin. Download Odin (its linked on the forum, just search), open it up, put the tar file you already have in the PDA slot, boot to download mode (volume down, home, and power at the same time), attach phone to computer, then hit flash.

There are also video tutorials on YouTube that are easy to follow, I recommend qbking77 (just make sure to use the files for d2tmo).
[T-Mobile, Samsung Galaxy SIII] el_garicimo:
Work around!

Thanks a lot Adreaver. I work around I did was taking the plunge and buying the ROM toolbox pro--the advanced version for 5 bucks lets you manually adjust the device name, and then flash the recoveries related to that device in the interface of the app itself, which was pretty cool...the ROM Toolbox pro seems like it has a bunch of really useful features packed all together too, from what I can tell so far def. worth the 5 bucks

So specifically, the app sensed that my device was d2ltetmo, and when I tried to flash recoveries in the it said none were available for my device. But in the proversion, I could user-define my device to be d2tmo, and then after rebooting the phone, it listed the latest recoveries for d2tmo.

After flashing cwr Touch v. 6.0.3.1, the AOKP rom from post #150 still did not flash, but the CM ROM from post 5 did indeed post--FINALLY! :D

While frustrating at times, this has ultimately been very rewarding. A suggestion I would make to DocHoliday77 (who has done an amazing job starting this thread and hosting all the proper zip files!) is to emphasize in post #5, where it lists the CM Rom, that you still need the d2tmo version of clockwork recovery for that CM ROM to work--I guess the info is in the thread, but it's a little buried in one of the "click to expand" sections, and so wasn't as obvious to someone like me who is still just learning all this stuff.

Having a good nandroid backed up, I'll now practice using ODIN to to revert to stock, as well as Titanium Backup to more easily jump between ROMS...will also try the AOKP ROM from post #150, but this time with TWRP.
[T-Mobile, Samsung Galaxy SIII] el_garicimo:
Using TWRP v2.5.0.0, AOKP zip from post 150 still doesn't flash

Title says it all...has anyone else had this problem? I'm using the proper TWRP for the d2tmo ...
[T-Mobile, Samsung Galaxy SIII] Funsturr:
....attempt has been blocked

Hello all.. after installing recovery ( CWM_Touch_6031.tar ) onto device ( sgh-t999n t999NUVUBMK7 4.3 ), then flashing SuperSu ( UPDATE-SuperSU-v1.80 ) , all successful , I continue to receiving Security block. Any advice as to what to do, or where I might have gone wrong? my goal was for simple root access.

Thank you in advance...
[T-Mobile, Samsung Galaxy SIII] gabe05:
If you're on 4.3 tw this is due to the knox security, go on the play store and search SuperSU by chainfire, update the app and follow the prompts afterwards it should get rid of the problem
[T-Mobile, Samsung Galaxy SIII] Funsturr:
The Playstore SuperSU did not help, but downloaded Chainfires most recent zip update. Flashed and then it worked. after that i was able to freeze Knox. and several others using Titanium. Thanks for the help!
[T-Mobile, Samsung Galaxy SIII] gilberts555:
I need a lil help

I am using the T999L, and I tried to flash CM11. I followed the instructions, twice. I tried removing the asserts lines, didn't work. I just get "(Installation Aborted)" and the same thing when I add them instead. It is very frustrating because I can't stand Touchwiz. I like the normal, stock Android feel. I tried multiple roms, and I followed the instructions thoroughly and correctly. If anyone else has the same problem, or knows how to fix it, please let me know. It says installing update, but about a second later, as I have said, it just says installation aborted with no reason why. Thank you. :crying::confused::mad:
[T-Mobile, Samsung Galaxy SIII] serio22:
Did you verify md5? Also make sure you are on latest recovery
[T-Mobile, Samsung Galaxy SIII] culson_35:
I have this phone too and flash cm11,carbon rom and now a using beanstalk rom the best for flash ROM is use the last recovery TWRP 2.6.3.1

Beanstalk 4.4.2 (sgh-t999l) kt747
[T-Mobile, Samsung Galaxy SIII] gilberts555:
I am on using CWM 6.0.3.8. Not sure if latest version, haven't been following, but I know it is pretty recent. I did extract it, change the text and whatnot, then rezip it to a .zip named the same thing. What is exactly MD5? It doesn't say it in the post.
[T-Mobile, Samsung Galaxy SIII] culson_35:
You need to root you're phone first then flash the last recovery TWRP them flash any rom

Beanstalk 4.4.2 (sgh-t999l) kt747
[T-Mobile, Samsung Galaxy SIII] gilberts555:
Recovery

Does the recovery really matter? I use TWRP on one of my phones, but on my T999L I use CWM 6.0.3.8. If all it is is the recovery, I'll go through with changing it.
[T-Mobile, Samsung Galaxy SIII] culson_35:
There is the problems this recovery not work for flash kit kat rom

Beanstalk 4.4.2 (sgh-t999l) kt747

---------- Post added at 10:33 PM ---------- Previous post was at 10:24 PM ----------

Use this link to download the last recovery for you're s3 lte copy to sd-card and us terminal emulator to change the recovery.... http://teamw.in/project/twrp2/106

Beanstalk 4.4.2 (sgh-t999l) kt747
[T-Mobile, Samsung Galaxy SIII] gilberts555:
crep

Looks like there is a lot of conflicts or problems if you try to change. I don't want to change, but if I have to, then I will do some research and stuff. I am seriously going through too much trouble to get a custom rom though. Loving my old phones with no variants.

---------- Post added at 03:40 AM ---------- Previous post was at 03:34 AM ----------

I need clarification. So, I just download the file to SD, type the command in a terminal, and just hope that it works?
[T-Mobile, Samsung Galaxy SIII] culson_35:
Yes...

Beanstalk 4.4.2 (sgh-t999l) kt747
[T-Mobile, Samsung Galaxy SIII] gilberts555:
Humbug. I give up. Tried it multiple times, but it says there is no such directory. I know I put it in my SD card, and it is obviously there, and I obviously typed it correctly.
[T-Mobile, Samsung Galaxy SIII] NexusS4gFreak:
Okayy so is the t999n the same as t999l and can i use the t999l roms? Just got this phone today soooo im a lil lost
[T-Mobile, Samsung Galaxy SIII] NexusS4gFreak:
If the com port failed to open when trying to flash the recovery for root (option 2) what do i do to make it pass
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Uninstall kids, Odin, phone drivers from PC. Reboot PC. Reinstall drivers (they are linked in OP I think). Reinstall Odin. Do NOT reinstall kies.

Then try the Odin flash again.
[T-Mobile, Samsung Galaxy SIII] NexusS4gFreak:
This time it flashed but instead of saying pass it said reset! it restarted the phone and i tried going into recovery mode and it took me to android system recovery
[T-Mobile, Samsung Galaxy SIII] NexusS4gFreak:
Okayy i did it again and waited, pass came up an the box turned green but i still had stock recovery.
[T-Mobile, Samsung Galaxy SIII] serio22:
Reflash it with auto reboot unchecked, when it passes, remove battery, and then enter recovery
[T-Mobile, Samsung Galaxy SIII] Kyrros:
After searching for HOURS I finally recovered from my softbrick. If anyone has trouble getting Odin to work with any kind of error messages or fails to write:

UNCHECK AUTO-REBOOT. You need to wait for Odin to give you the pass, and then manually restart.

Start whatever you're flashing.

Let it fail.

Unplug USB.

Plug USB back in.

Start again while Odin still has the file loaded, and it should work.

Hopefully this helps somebody out some day, because I hated my life for about 6 hours. :rolleyes:
[T-Mobile, Samsung Galaxy SIII] gilberts555:
Yay!

Looks like the CyanogenMod team is officially supporting the d2letmo now. In fact, I have it on my phone already now and it is perfect. Really fast and buttery smooth. So, yey. It was actually supported on the 18th, but I didn't realize that. Oh, there is a Facebook post on CyanogenMod saying that the S3's and S4's were broken, mine wasn't so I am happy. But, when I flashed it at 3am yesterday, I was jumping for joy.
[T-Mobile, Samsung Galaxy SIII] OhTen40oz:
T999L cant write to /data

As mentioned in the title, my T999L cant write to /data. I read on another forum, i think verizon, they checked and [nand erased all] in odin but they also had bootchains which im finding no information on for Tmobile. I also read they they flashed their kernels, ive downloaded what i assume to be, the kernel i need. Im just at a complete loss.

Side info, i tried to do a LEGIT system restore and it bricked, just hangs at the tmobile screen. Any help is greatly appreciated.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Check the unbrick thread, not sure if anyone has adapted it for the t999l, (partitions may be different but you are already bricked...can't extra brick lol)

If not, swap the device under warranty.

Sent from my Cleared Out T999L on CM11
[T-Mobile, Samsung Galaxy SIII] kiluma:
Did not root using root66 method...

I used root66's method, and it still says I'm not rooted(Root Checker). I tried installing SuperSU from the market, and still no root.

The root66 method 'Passed', and all seemed proper. However, I can't get root on this device.

SGH-t999N(Metropcs).

Is there any other info you need? Or, can you offer guidance from here?
[T-Mobile, Samsung Galaxy SIII] sanmiguel30:
Hi,

I am new here. I checked the internet for answers to my questions and I was brought into this forum. I hope someone answer my question.

So, I restored the factory settings of my T Mobile Samsung Galaxy S3 SGH-4999L. Then when it restarted, only the tmobile 4g lte flashes with the white background, then it won't load.

Can someone please help me. It's been 2 days and it just keeps on going like that. I did everything I removed the battery, I tried to put it in download mode, I downloaded CWM, i rooted, but still won't work....

Please help...

Thanks!!!
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
Boot into the custom recovery and wipe dalvik/cache, then reboot.

Sent from Omicron Persei 8 via Planet Express.
[T-Mobile, Samsung Galaxy SIII] kiluma:
When I booted into recovery I wasn't given the option to wipe dalvik cache. It did give me the option to wipe cache, and I'm not sure if that is the same thing. I did it, anyway. After reboot, I checked to see if I was rooted, and it was not.
[T-Mobile, Samsung Galaxy SIII] threeddefect:
I'm sure this has probably been posted somewhere before but I'm still failing to see it.. I'm trying to install Cyanogenmod on my T999L. I'm not new to flashing but I'm just not sure what to do at this point (I'm faced with a disc image file instead of a tar file like I'm used to.) I've already got CWM Recovery flashed to my phone. Can someone nudge me toward the right direction please?
[T-Mobile, Samsung Galaxy SIII] serio22:
Well you have cwm, so flash cyanogen
[T-Mobile, Samsung Galaxy SIII] threeddefect:
Yeah, I know, but what I'm trying to say is I don't know what to do with a disc image. Heh.
[T-Mobile, Samsung Galaxy SIII] serio22:
Image of recovery? I have no idea what image you're talking about
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
its probably the recovery.img file he is talking about. Only good way of using it in this form is by dumping it to the phone using the dd command via terminal.

Open a terminal emulator (need to be rooted), enter this:

su

dd if=/path/to/recovery.img of=/dev/block/mmcblk0p18

(Its been a while since Ive messed with that, so if someone wants to verify the above command, I'd appreciate it!)

Otherwise, if you want to flash it in Odin, you will need the recovery.tar. Ill try to update my repo for recoveries and everything else over the next few days. Till then, you will just have to find one elsewhere here on the fourms. I am sure its around.

Hope that helps!
[T-Mobile, Samsung Galaxy SIII] serio22:
Yes that's what I assumed, all they said was disc image, and then I asked if it was image of recovery.. And the command is correct!
[T-Mobile, Samsung Galaxy SIII] opiumNOTO:
Soft Bricked. -____-

Original post:

Hello everyone! I'm relatively new to rooting, and somehow I mistakenly soft bricked my phone. Initially, I used the root66 method for my SGH-T999L and it worked great; however, somehow I may have installed the wrong version of CWM.(IF that's even possible.) All I know is that after I installed a version of CWM, my phone would no longer boot up, and it would become stuck on the 4g LTE loading screen. I tried installing the stock rom located in the third post using odin, however my phone then began freezing at the Samsung S3 logo instead. I re-ran the root66 method, and it's back to freezing at the T-MOBILE 4G LTE logo. Please someone!-- I'm in dire need of help! Help me get my phone running and out of soft brick mode. :c

Update:

Okay everyone, I was typing that while retrying the root66 method and it worked to get my phone out of soft brick mode! So to anyone who soft bricks their phone and is panicking, just re-root it using the root66 method. When the 4G LTE logo comes up, it'll take about a minute for your phone to actually boot up. Don't panic and just relax. Cheers!
[T-Mobile, Samsung Galaxy SIII] shonmac11:
I can't get GooManager or ROM Manager to install TWRP/CWM recovery on my T999L. Can someone please help me or explain why it's not working?
[T-Mobile, Samsung Galaxy SIII] serio22:
More details like error messages or something would help.. Have you tried using flashify?
[T-Mobile, Samsung Galaxy SIII] shonmac11:
In the last screenshot the sgh-t999l isn't listed
[T-Mobile, Samsung Galaxy SIII] shonmac11:
I just downloaded Flashify and this is what it showed me. I have a T999 TWRP recovery on my SD card because I read that it could be flash to a T999L but I'm afraid that it will brick my phone
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
It shouldn't. Many people are using the T999 recoveries on their T999L/T999V/T999N. Better compatibility with available roms.

Just make sure the md5sum matches your download.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Confirming that t999twrp from doc's Sig working fine for me since July last year

Sent from my Cleared Out T999L on CM11
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I haven't updated my repo in a while, but I'll try to get the latest of everything added in the next day or two.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If anyone with a T999L is running the latest (NC1?) Firmware, would you please consider going to the debrick thread stickied in development and creating a debrick image for that build? Read the op for more info. Thanks!
[T-Mobile, Samsung Galaxy SIII] werro6:
i need help i have just got my first smart phone i have rooted it and tryed a costom rom but my camera would not work with it i have a sgh-t999l tmobile doc could you please help me and post links to roms that will work on it i cant seem to find any for my modle i really want one that has performence and battery life no bloatware and costomizeabilty but more importently battery and performence please help me
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I don't have a T999L, so I don't know exactly what will work and what won't. Its been asked many times though, here and elsewhere, so I'd start by searching the thread to see what others found.

And just for future reference, if you have an issue, we'd need to know what rom, and firmware build you are on.
[T-Mobile, Samsung Galaxy SIII] werro6:
ok srry i am on stock jellybean 4.3
[T-Mobile, Samsung Galaxy SIII] henry8668:
I have t999l using 3/28 nightly, camera works. Battery better than cm10.2
[T-Mobile, Samsung Galaxy SIII] werro6:
so is the rom you posted on the 1 page

costomized at all or is it a stock rom

---------- Post added at 12:57 AM ---------- Previous post was at 12:16 AM ----------

could you link it please i would really apreciate it
[T-Mobile, Samsung Galaxy SIII] Johnnyy9262:
its completely different from stock, im looking for a stock firmware with 100% working root
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Root66 in development section is probably what you want.
[T-Mobile, Samsung Galaxy SIII] Johnnyy9262:
Im using that right now but it seems to have either root issues or its busybox either way some root apps that are supposed to work dont, like es file explorer
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I just flashed it yesterday and all works perfectly for me. Did you factory reset and start clean?

Root66 doesnt include busybox afaik.
[T-Mobile, Samsung Galaxy SIII] Johnnyy9262:
no do i have to? in his post he said it will just replace system files not /data files will be touched oh and i installed busybox trough playstore since all the root apps the im usong requires busybox, lets take sdmaid for example i touch on the overview it says

Busybox Installed:[External[System]] all other options like root are green and says normal, how can i get this to normal?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If an app says busybox installed external its just saying it sees the one on your phone. If it wasnt there it would use the internal (built in the app).

As far as needing to wipe data, this varies from person to person. If there is data from an app not coded to work right on 4.3 it can cause issues. We see in changelogs all the time where devs update for compatibility.

But regardless, things are not working as expected. The best way to solve is to start clean and restore only essential data such as contacts. Then if needed restore data to a few apps at a time until the problems start again.

Imo, its good practice to occasionally wipe everything anyway. I just did this myself and only restored contacts and one games data. I wasnt having any issues, but I believe I ofte have fewer than most people because I clean up occasionally.

Hope that all makes sense and helps!
[T-Mobile, Samsung Galaxy SIII] Fry-kun:
Which ROM do people recommend nowadays for T999L?

I'm still on CM 10.1.3...
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
S3Rx and StockMod are both very good roms. Both should work just fine on the T999L.
[T-Mobile, Samsung Galaxy SIII] jmanalp:
Replacement Parts

Can someone please direct me where to find replacement parts for the T999L? Does anyone know if parts for the T999 are compatible with the T999L? I need to replace the part that holds the SIM/ SD slots and can't seem to find parts for the T999L anywhere, though parts for other models are abundant.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Sim and sd reader is likely the same. Check disassembly vids and compare to yours.
[T-Mobile, Samsung Galaxy SIII] jmanalp:
Yes, it's the same. I know what part I need, the problem is I can't find one that says it is compatible specifically with the T999L... I wonder if T999 hardware is compatible with the T999L. Anyway thanks for the reply.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
When it comes to something like the reader, it most likely is. Not everything will be, but parts like that, the motor, prox sensor, are prob interchangeable.
[T-Mobile, Samsung Galaxy SIII] jmanalp:
Alright brother I will try it out, and I thank you.
[T-Mobile, Samsung Galaxy SIII] :
Thanks to OP, I was able to (successfully, and without bricking or getting in trouble with parents) flash TWRP on my sis's SGH-T99N. Removed everything MetroPCS, made a backup (Just in case something went wrong, and had to go back to stock NC1). Sis is now running CM11, it makes her happy how much better (in speed and battery life) the phone is.

She thinks I'm a wizard, lol. :good:
[T-Mobile, Samsung Galaxy SIII] gabe05:
So I just have a general question and I'm not sure where to ask, so I want to get the latest miui ROM, but its only available for the d2att but to my understanding that's identical to ours, now my question is why the ROM isn't flashing after I removed the assert lines and replaced the meta files from a d2tmo build to the d2att
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If you can tell us what errors you get itll help. After the flash fails, find and choose "save log to sd". Then attach it here.

You probably just need to remove the asserts and thats it for it to flash. As for getting it to run well.....that may be a different thing all together. The devices are not identical, but as far as roms are concerned, they are very compatible. You'll probably need to research and find what else needs to be done to get it running right if theres issues.

And just fyi, this thread is dedicated to the T999L and T999N. It looks like you have an original T999, so its a bit OT here. If you have more problems id suggest either starting a new q&a thread, or find a related one about porting roms to post in.

Good luck!
[T-Mobile, Samsung Galaxy SIII] gabe05:
Thank you very much doc! And no I have the LTE I'm just running carbon ROM right now and it changes my name to the regular t999 but I'll give it another shot and see what happens
[T-Mobile, Samsung Galaxy SIII] childsplay64:
What fits?

Does the screen, digitizer, and housing from t999 fit t999l?
[T-Mobile, Samsung Galaxy SIII] gabe05:
So trying to flash this ROM I get boot loader assert fails even though I have have the right boot loader Installing '/sdcard/Download/4.1.24 d2tmo-1.zip'...

Checking for MD5 file...

I:Cannot find file /sdcard/Download/4.1.24 d2tmo-1.zip.md5

Skipping MD5 check: no MD5 file found.

I:Zip does not contain SELinux file_contexts file in its root.

script aborted: assert failed: getprop("ro.bootloader") == "I747UCDLK3" ||

getprop("ro.bootloader") == "I747UCDMG2" ||

getprop("ro.bootloader") == "I747MVLDLK4" ||

getprop("ro.bootloader") == "I747MVLDMF1" ||

getprop("ro.bootloader") == "T999UVUEMJC" ||

getprop("ro.bootloader") == "T999LUVUBMK4"

assert failed: getprop("ro.bootloader") == "I747UCDLK3" || getprop("ro.bootloader") == "I747UCDMG2" || getprop("ro.bootloader") == "I747MVLDLK4" || getprop("ro.bootloader") == "I747MVLDMF1" || getprop("ro.bootloader") == "T999UVUEMJC" || getprop("ro.bootloader") == "T999LUVUBMK4"

E:Error executing updater binary in zip '/sdcard/Download/4.1.24 d2tmo-1.zip'

Error flashing zip '/sdcard/Download/4.1.24 d2tmo-1.zip'

Updating partition details...
[T-Mobile, Samsung Galaxy SIII] Perseus:
What is your Bootloader ? The Rom is looking for ATT Galaxy S3 but only one bootloader T999 & T999L apiece.