yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] Perseus:
You best Recourse is to ODin Back to stock. Please remember, you must use the same firmware as the one you had before you replaced it with Slim. Otherwise you might potentially hardbrick your phone. If in doubt, post what firmware or Android Version you had before you flashed Slim.

If Odin too has trouble with Data Partition (Which I doubt), we can help you repartition your phone. But let's not cross that bridge till we get there.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Odin will wipe ypur custom recovery. But you just have to reinstall is all.
[T-Mobile, Samsung Galaxy SIII] Ditamae:
Thanks for the reply. Just for clarification, you're saying I should use the same firmware I used prior to flashing my first custom ROM? I never flashed any official OTAs, my SGS3 shipped with UVDLJA bootloader/modem/firmware (Android version 4.1.1), and I flashed a version of Slimbean just after rooting. I tried the MD5 firmware package found here recently. Then I went back to UVDLJC baseband/firmware (pulled from the same thread) when I found battery life to be decreased with MD5. I'm still using LJC at this time. Honestly, from experimenting, I'd prefer to be back on UVDLJA bootloader/radio. I seemed to get the best battery life/cell reception with that original combo anyway. Tl;dr - the prerooted UVDLJA firmware is my best bet?

Thanks again for the help. :)
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Most people have updated up to or beyond 4.3, so rather than explaining it 100000000 times its easier to assume this and say only flash what you had before.

If you are on pre 4.3 firmware, you're pretty much free to flash whatever you want.

Once on 4.3, there's no going backwards anymore though.
[T-Mobile, Samsung Galaxy SIII] Ditamae:
Oh, okay, gotcha. I understand once you've flashed 4.3 and beyond you can't go backwards. I thought there might be some other reason I needed to revert to my original, specific stock firmware. Perseus71's comment makes more sense now. Sorry for the confusion (and repetition).
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yep LJA will work.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
The repetition comment wasn't aimed at you or anyone in particular. Was just explaining why we often don't go into detail on that anymore.
[T-Mobile, Samsung Galaxy SIII] frank_jaeger:
Hi I also have a Tmo S3 that I upgraded from root66 4.1.2 to root66 4.3 and am seeing similar behavior with root appearing/disappearing with reboots.

Did you try a factory reset? Were you able to clear this up and get root to stick full time?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Have you checked to see if there are any updates available for SuperSU?
[T-Mobile, Samsung Galaxy SIII] frank_jaeger:
I have, according to the play store I am up to date.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Not really sure what it could be tbh. Never seen it before myself. May try choosing Full Unroot in SuperSU settings, reboot, then reroot using Towelroot. (See my thread in General for instructions, super easy)
[T-Mobile, Samsung Galaxy SIII] frank_jaeger:
Whew boy this is odd.

I tried the following:

-full SuperSU unroot

-reboot

-towelroot root

-install superSU

-launch superSU

-binary update attempt failed

-reboot

-root binary is gone

-reboot

* towelroot re-try, couple more reboots

-SuperSU launch and update

-reboot

-root gone again

-towelroot

-no root

-reboot

-root back

I may try a factory reset.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Might be a good idea. That is really weird though!

If it happens again, check to see if this file is still in place. /system/bin/su
[T-Mobile, Samsung Galaxy SIII] Perseus:
When I read first few lines, I kind of expected this result. The thing is, the only guaranteed way to cleanly unroot is reflashing Stock firmware. Any other unroot process does leave vestiges of the binary and its Sqlite Entries in at least 3 different places. Which predictably leaves with you the results you experienced.

when I had to do a warranty exchange, I simply flashed stock firmware and sent it back.
[T-Mobile, Samsung Galaxy SIII] frank_jaeger:
This seems to occur on demand with reboot cycling. The thing is without root what app program can I use to explore the filesystem and confirm existence/nonexistence of the file?

With root I checked and /system/bin/su does not exist but /system/xbin/su does.

I'll try flashing on the matching stock software version rom from Docs FW+OTA thread and then towelroot after that.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Sorry, auto correct got me on the xbin. That's where su is supposed to be. You don't actually need root to browse the /system partition. You can still go in and see if su is there or not.
[T-Mobile, Samsung Galaxy SIII] frank_jaeger:
I re-booted and checked root is gone by launching Titanium Backup (says no root), SuperSU confirms the same thing.

I browsed with ES File Explorer and there is still a "/system/xbin/su" file present.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Try this,

Open /system/etc/install-recovery.sh in a text editor.

Change this:

/system/xbin/daemonsu --auto-daemon &

To this:

/system/xbin/daemonsu -daemon &

Then do the same for /system/etc/init.d/99SuperSU

Basically you are just removing --auto, so rather than su being run when needed it'll run persistently. Not sure if it'll help, but worth a shot.
[T-Mobile, Samsung Galaxy SIII] frank_jaeger:
I was able to edit the copy in /etc,/system/etc but I do not seem to have an "init.d" folder in etc.

EDIT: I went ahead and tried rebooting after editing the install-recovery.sh file and root seems to be sticking. I've rebooted several times now and it's still present. Thanks Doc!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Cool! Glad it worked! The init.d folder is only in some ROMs. If you don't have it don't worry bout it.
[T-Mobile, Samsung Galaxy SIII] frank_jaeger:
Urk, guess I spoke too soon. My 4G was acting odd/slow so I rebooted again, root was "gone" again.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I've no idea what is going on then. Maybe try reflashing the firmware and factory resetting. Start over. (Backup first of course).
[T-Mobile, Samsung Galaxy SIII] robijas:
Hi guys I have question and hopping somebody cen help.I am running KK4.4.4 and SU needed to upgrede but never did, now I don't have su, not rooted any more.I try towelroot it say not supported phone, tryed framaroot non of exploit option worked.do i need to use odin ( didn't try that yet) or .I try to install SU from play store but sead that i missing SU binary.any suggestion is welcome.thanks.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Don't use SuperSU from the store. Only use 2.00 or earlier from my sig.
[T-Mobile, Samsung Galaxy SIII] sonwon:
Why, just wondering?
[T-Mobile, Samsung Galaxy SIII] robijas:
Thx.Doc I was able to get my root back whit su 2.0.0 zip file I found on different website.Worked like charm.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Bugs like those mentioned before. Breaks root.
[T-Mobile, Samsung Galaxy SIII] sonwon:
I'm on V2.01 and so far no problems with root, using the 4.3 ROM. Ran this before I saw your post.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
With 2.01 I think it has to do with how it is installed/updated.
[T-Mobile, Samsung Galaxy SIII] Trooth412:
The best method to get root using stock or custom roms with out tripping counter. bump this should be on top!
[T-Mobile, Samsung Galaxy SIII] dkarmann:
Is there any possible way to get a root66 version of t999luvubnf4? I took the update and apparently they have patched towlroot and am stuck without root. I've tried flashing a recovery CWM 6.0.4.5 (that I've always used) and it is not sticking, it always boots to factory recovery. So, any ideas would be greatly appreciated.
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
did you try unchecking auto reboot, then after odin is done flashing recovery, pull the battery? then put battery back in and hold home and volume up press power button till you see small blue letters recovery booting. let go of power but not volume up and home until recovery boots.

also you might want to try latest twrp d2tmo. should be compatible with d2lte also.
[T-Mobile, Samsung Galaxy SIII] dkarmann:
Yes athalon, I did a little research and came across the uncheck boot and battery pull method. I've never used that before so I couldnt for the life of me figure out why recovery wasn't sticking. I did get root by flashing recovery and su zip. So at the moment i am on stock rooted with recovery. Thanks so much for the info!
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
thanks. I plan to do the same and then flash s3rx 3.0. just got the t999l and was concerned when a couple people said recovery didn't stick. didn't want to trip knox for nothing.
[T-Mobile, Samsung Galaxy SIII] cLogic:
check to see if you have the following files:

/system/recovery-from-boot.p

/system/etc/install-recovery.sh

if you have install-recovery.sh, have a look at its contents and see if it launches recovery-from-boot.p

if it does .. welcome to the world of samsung annoyance

that is their script to push the stock recovery back after each boot

use a root file explorer like ES to:

mount the system partition with read-write permission

rename or delete those two files

set system partion to read-only permission again and un-mount it

re-push your custom recovery

.
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
on your device info in the build prob does it say d2lte? or using root checker app under build info tab does it say d2lte?
[T-Mobile, Samsung Galaxy SIII] dkarmann:
d2ltetmo, sorry I haven't updated this thread but I was able to get root by using the uncheck reboot and battery pull method. I had never had to do that before because I was always able to just flash stock rooted with odin. I'm somewhat nervous about flashing any roms because of not having that stock odin saftey net but I'm ok with stock rooted for now.
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
I did the same. then I nandroided. then I flashed s3rx3.0 4-5-14 with the mj2 kernel. I like to edit the build prop back to show the correct model and device info. I changed the t999 to t999l in 2 spots but I hadn't changed the d2tmo. wanted to make sure it was right. I forgot to check before. glad I asked if yours is stock and shows d2ltetmo I would have put the wrong stuff.
[T-Mobile, Samsung Galaxy SIII] dkarmann:
How to do you like s3rx3.0 4-5-14? The only rom I've ran to date is the SlimKat 7.0 stable on the stock kernel and I liked everything except my PowerAmp music player would glitch during playback like a slight pause in the music every so often. It doesnt sound like much but it got on my nerves and I was never able to get Milk Music to work. I edited the build prop but it never never allowed me to download it from the play store. I'm sure I didn't edit it correctly but I found an app that lets you download anything from the play store by spoofing your phone. Even once I was able to download milk it would fail to install with "missing shared folder" error. I loved the rom but I just want things to work ya know.
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
thumbs up. sending pm so not to derail too much.
[T-Mobile, Samsung Galaxy SIII] narcisses:
A couple Quick question regarding Note II

1. I've upgraded the stock ROM to 4.4.2. Will the bootloader or anything else have been upgraded in a way that will brick my device? Anyone have any knowledge or experience in the matter?

I don't care about custom ROMs quite yet. My immediate end goal is to enable Chromecast screen mirroring.

*** I should add it's a Wind Mobile 4.4.2 stock
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
this is the s3 thread the note 2 is here:

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

[HOWTO] [ROOT] No Tripping Flash Counter - Stock Injected [TMO/MCT/GLW/VTR]
[T-Mobile, Samsung Galaxy SIII] joselamar:
What is the best way to update the T-Mobile GS3 SGH-T999 to kitkat 4.4.4? Freaking T-Mobile is not going to update crap on our phones.
[T-Mobile, Samsung Galaxy SIII] guest_2011:
i'm also waiting for 4.4. cm11 is ok but i lost 1080 video recording with cm..
[T-Mobile, Samsung Galaxy SIII] cLogic:
flash a 4.4.4 custom rom .. I use CM 11 and Omni

considering the device resolution is 1280x720 .. not much lost ;)
[T-Mobile, Samsung Galaxy SIII] guest_2011:
but then i could have saved $250 and bought any pos that can do 720 video. I don't watch recorded videos in my phone.
[T-Mobile, Samsung Galaxy SIII] joselamar:
I read some of the CM11 threads for KitKat 4.4.4 but looks like there are a few issues with WiFi, camera, etc... Looks like that ROM is full of issues and one has to flash a few zips to fix them.

This question is for mrRobinson.

Do you have KitKat 4.4.4 in mind to develop for the SGH-T999?
[T-Mobile, Samsung Galaxy SIII] Shack70:
I'm running T-Mobile build number T99LUVUBNF4. Can I use the newest version of route66 or am I upgraded to a firmware that is too new?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Well he hasn't Developed these Stock Firmwares. What he has done is to inject root in the Stock Firmware on this thread.

Having said that, There isn't likely to be a Kitkat 4.4.4 here unless Samsung Releases one for this device.

Think you have a the most recent version for your T999L.
[T-Mobile, Samsung Galaxy SIII] joselamar:
I'm still hoping that Samsung releases the kitkat version for the T-Mobile GS3. I don't know how T-Mobile can keep customers happy when they are always the last ones to release versions.
[T-Mobile, Samsung Galaxy SIII] Shack70:
Yeah I have the newest version. Is there a version of Route66 I can use to root my phone? I'm just looking to gain root without tripping the counter and Route66 seems like the best option. No need to run custom firmware such as kitkat, I just don't want to brick it.
[T-Mobile, Samsung Galaxy SIII] Perseus:
The latest for D2TMO is in OP. Use that with Odin.
[T-Mobile, Samsung Galaxy SIII] Shack70:
Install Odin and run cm11 from D2TMO?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Running CM 11 Will Trip Counter. Assuming that is what you want to do, then things are more simple. Install Custom Recovery for D2TMO, either CWM or TWRP (Or Even Philz). Flash CM 11 that way.
[T-Mobile, Samsung Galaxy SIII] Shack70:
No I don't want to run cm11. I just want to use Route66 to gain root and not have Knox. My problem is I have the newest firmware installed and there is no Route66 version that matches it. I'm not sure what to use or if it's even possible with this firmware. I saw another thread that I can't find now that said to use cm-autoroot but again I'm unsure as my firmware is not listed
[T-Mobile, Samsung Galaxy SIII] cLogic:
you have the tmobile t999 with firmware IMM76D.T999UVALEM ?

here's something http://autoroot.chainfire.eu/
[T-Mobile, Samsung Galaxy SIII] Shack70:
No T-Mobile SGH-T999L with JSS15J.T999LUVUBNF4 . I understand rooting the T999 and The T999L is the same, they just have different modems. I'm just not sure of the safest method. Root66 looks appealing because it removes Knox all together. If Autoroot by chainfire is proven and safe I'll use that. Just need someone to verify what to use for my current unrooted firmware. My phone is out of warranty so that's not an issue either. Thanks for any help.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Anything in the OP does not have Knox.
[T-Mobile, Samsung Galaxy SIII] Shack70:
Yes I understand that Knox is removed from route66, will it brick my phone if I just use the newest version for T-Mobile LTE with Odin to flash it or should I wait for a route66 version of what firmware i have or should I just use autoroot?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Go AutoRoot. If it fails use Towle
[T-Mobile, Samsung Galaxy SIII] Shack70:
Autoroot worked, thanks!
[T-Mobile, Samsung Galaxy SIII] EmpiricalDepth:
EDIT: moving on, doesn't look good. Gonna do this instead: http://galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-on-android-4-34-4-2-new/

someone in another thread said it worked for them and I don't care if I trip the warranty flag

.........................................................................

can I just use root66_TMO-L_T999LUVUBNC1.7z to root even though my firmware is stock T999LUVUBNF4? (newer) it is still 4.3

this may have already been answered but i'm not sure if it was made clear that the route66 is older than the stock on the phone
[T-Mobile, Samsung Galaxy SIII] saran.selva:
Not able to flash ROM after rooting the device

Hi All,

Need a favour of flashing my S3 SGH T999 to new ROM of 7.1.2; have downloaded the package and used the xda suggested app to root and tried installing, but getting the following error; any help would be of greatly regarded.

Getting the message as ::: E: Signature verification failed.
[T-Mobile, Samsung Galaxy SIII] fireboypr:
I don't think it matters anymore, but be careful people are losing their IMEI and serial number somehow, seems randomly so far. They are trying to figure out why is happening and how to get it back if possible. Be aware!
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
I think it depends on what you want. If you just want a stock rooted rom, I'd say this is the best path to take esp with the IMEI scares.

If you want to throw cwm on your phone and you know you'll be flashing things then it doesn't really matter. Though this isn't really any more difficult or involved than any other method (just a larger file) and then you don't have to worry about resetting the counter.
[T-Mobile, Samsung Galaxy SIII] fireboypr:
Yea, so far I am stock rooted. Happy with it so far. I'm tempted to try other roms but I'm scared about the IMEI thing. I think I'll use stock rooted until they find a solution for the IMEI.
[T-Mobile, Samsung Galaxy SIII] stevessvt:
I rooted using this stock rom, and yesterday got the nerve to adb push TWRP recovery to my phone. Im pretty sure I haven't read of anyone losing their imei while using TWRP, but maybe I just haven't come across it yet. Made a bck up, loaded a new kernel, and so far so good, trucking along at 1.7GHz.
[T-Mobile, Samsung Galaxy SIII] Diekrupt:
Can ACS please make a syn rom for Tmobile S3

Love to see acs syn Rom on T-Mobile.

Please Oh Please Oh Please

Please?

:D

DK
[T-Mobile, Samsung Galaxy SIII] sabreful:
wonderful > worked PERFECTLY

doesn't work with JB/cm10 though - sgh-t999
[T-Mobile, Samsung Galaxy SIII] Taco991:
Does mobile Odin work? And does it trip the counter? Not that it matters cause triangle away is working :)
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
Added Mobilicity and Wind for Canadian users.
[T-Mobile, Samsung Galaxy SIII] rayman2k1:
Actually a theory is that flashing cm roms from twrp is a cause for losing imei. Both cm OPs say to only use cwm recoveries. So, be warned.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
Are you responding to someone? the files here are flashed in ODIN and I have yet to see a report of someone losing IMEI via ODIN. Just not sure if you were making blanket statement or responding to someone in particular.
[T-Mobile, Samsung Galaxy SIII] AllAboutAndroids:
Thanks so much for the added Wind support! Unfortunately I couldn't wait and used mskips method to root and flash cwm :p

Oh mrRobinson, I'll try to provide mirror links once I get home :D

EDIT: 2hrs left to Complete the Uploads. I will post links once I wake up!
[T-Mobile, Samsung Galaxy SIII] AllAboutAndroids:
Mirror Links are up!

Hey Folks, I finally uploaded the files for the T-Mobile, Wind and Mobilicity Stock ODIN images.

Note: Always check the MD5 sums before using any of these! Thanks :)

T-Mobile Image

Note: This is based off of TMO T999UVALEM that was posted in this thread, thanks to AdamLange.

Perm Mirror: Download - MD5 Sum: c2bae57ad0dcfecc8c07b38d0e8da506

WIND Image

Note: This is based off of WIND T99VVLALE6.

Perm Mirror: Download - MD5 Sum: daf38b93401cc8187a04447f2665d9f7

Mobilicity Image

Note: This is based off of Mobilicity T999VVLALE6.

Perm Mirror: Download - MD5 Sum: 69d4ae29e578aa3359afa4ec9452e594
[T-Mobile, Samsung Galaxy SIII] pytyper483:
thanks!
[T-Mobile, Samsung Galaxy SIII] avataranjie:
So flashing these stock images along with the stock+root .tar in the OP will not increase flash counter right?
[T-Mobile, Samsung Galaxy SIII] daemonfly:
So, I've downloaded the T-mobile image (slowly), and each time the MD5 is wrong, on both the .7z file, and once extracted to the .tar (checked both). Also, the "wrong" values I got were exactly the same for both download attempts, using multiple md5 checking apps.
[T-Mobile, Samsung Galaxy SIII] deeznutz1977:
here s another link for the t mobile version http://www.4shared.com/archive/yz3_V8NZ/root66_TMO_T999UVALEM.html dropbox link also https://www.dropbox.com/s/uggqealtrvuguko/root66_TMO_T999UVALEM.7z
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
correct...
[T-Mobile, Samsung Galaxy SIII] deeznutz1977:
Download triangle away from the play store
[T-Mobile, Samsung Galaxy SIII] avataranjie:
It works now? Time to try
[T-Mobile, Samsung Galaxy SIII] eggnoodle:
I've too gotten incorrect MD5 for the TMO file. Is this suppose to be the right file?
[Galaxy S III General (US Carriers)] t061509j:
i've rooted my S3(T999) and installed another rom on there. i couldn't boot up the phone it just remain pitch black. what could i do? please help!!!!
[Galaxy S III General (US Carriers)] Bowsa2511:
Take out the battery, connect microusb and go into download mode, restore to stock with Odin
[Galaxy S III General (US Carriers)] SaHiLzZ:
What could you do? You read next time.
[Galaxy S III General (US Carriers)] t061509j:
i can't even go in download mode.

when i go in device manager it shows as HS-USB QDLoader 9008(com5)
[Galaxy S III General (US Carriers)] ghost77:
Did you install rom for international Galaxy S3 ? :silly:
[Galaxy S III General (US Carriers)] adslee:
That sounds like a hard brick, try and see if someone can fix it for you via jtag
[Galaxy S III General (US Carriers)] t061509j:
is there a way to fix it without jtag?
[Galaxy S III General (US Carriers)] t061509j:
im not sure. :(
[Galaxy S III General (US Carriers)] Jamin13:
Another one bites the dust.
[Galaxy S III General (US Carriers)] rakeshchn:
Search Google for mobiletechvideos.

Sent from my SGH-T999
[Galaxy S III General (US Carriers)] t061509j:
can i use Galaxy S3 toolkit to boot it in download mode

nevermind. it dont work it said no device found.
[Galaxy S III General (US Carriers)] babymatteo:
The volume down+power+home doesnt work?

Can you get into cwm?
[Galaxy S III General (US Carriers)] t061509j:
nope. can't do anything. when i hold and press the power my PC detect the driver as in HS-USB.
[Galaxy S III General (US Carriers)] dawsndev:
So you can't hold vol up and down pull battery connect usb and put battery back in and get to download mode at all?
[Galaxy S III General (US Carriers)] t061509j:
i've never tried that.

nope it dont work.
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] eraser0:
hello am asking this question, because i really wanna to update via kies if any update is coming... or at least get the warranty back

so it will be a helpful topic for all members

i have red some articles like this one here

and they all saying that the ace is the only phone that is not supported through this app here

so what is the real problem? how we can get rid out of this?
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] panpjp:
Use odin. Kies sucks.
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] eraser0:
okay am using it, but for warranty matters? :) and also to get the latest updates without needing to backup and restore all my apps and settings
[Galaxy S III Q&A, (US Carriers)] Jarrod357:
Has anyone been able to get nova 3 to work with full effects on us variants?. I tried using chainfire with nvidia plugin but I get a black screen. I can see the hud but everything else is black. Some times it flickers like a strobe light.