yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] hccaus:
I didn't know where to get the JIG at 3PM on Sunday afternoon and was in a rush.

Hopefully the repair store will call me with a good news.

I assume JTAG will fix it.. :(
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
JTAG most likely will.

In the event you get it back without them fixing, there is a debrick thread at the top of this very forum.
[T-Mobile, Samsung Galaxy SIII] ultrairon:
Hi

This is what i did

Flashed the official 4.3 ota

Flashed Twrp

Flashed knox free version of 4.3

Flashed dandroid so now if i try to odin back to 4.1.2 will i brick my device
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Odin will fail. Flash the older firmware in this thread and yes, bricked.
[T-Mobile, Samsung Galaxy SIII] ultrairon:
ok thanks

OK thanks so this is what im going to do

flash official 4.3 odin file T999UVUEMJC

flash twrp and root via chainfire cf-root

the flash aosp and edit the assert file like u told me to do in the other thread?

thanks in advance doc uv been so helpful
[T-Mobile, Samsung Galaxy SIII] mondokat:
cm updated the bootloader assert

https://github.com/CyanogenMod/andr...mmit/d2e2dd1cd4538b24ff1bb17d6dfd3fda987fa9fb

Here's the commit that updated the bootloader check to include the latest UVUEMJC firmware. It was committed Nov 25 and was included in CM10.2.0 stable. It's a bit safer to flash the new firmware now, since CM will now run like it always has.
[T-Mobile, Samsung Galaxy SIII] andrewnelson23:
Hi I'm a little bit confused. I flashed the t999uvuemjc modem to my phone and all is working fine on cm11. But some Roms are not compatible with it quite yet. Can I downgrade the modem or will that brick? Or does brick only happen with full firmware or boot loader? Sorry I can't do a search on my phone but I don't wanna do anything that'll brick my phone. Better to be safe.
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Exactly. It only happens when you flash the ODIN firmware. A firmware, as in ODIN firmware, already includes everything, including modem and bootloader. In my case, since I flashed the MJC ODIN firmware, I can't flash any other past ODIN firmware such as MD5 or LJA.
[T-Mobile, Samsung Galaxy SIII] andrewnelson23:
OK thanks. So I should be able to flash the md5 modem no problem and then flash an att ROM so long as the att one supports the md5 modem?
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Yes. I've previously flashed an AT&T ROM followed by a T999 modem.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Yeah, just don't flash any of the stuff in this thread if you're running MJC because all the stuff in here also flashes firmware and results in brick for MJC firmware devices. Check the modem thread for a flashable modem-only update.
[T-Mobile, Samsung Galaxy SIII] PhrostB:
Do I understand correctly that cm11 will require the T999uvueMJC bootloader? Is it safe to flash as long as we don't flash an older bootloader over?

edit: Nevermind, I see it's not a requirement. Looking forward to getting an official version of cm11 to play with. I plan on formatting all the whole phone... ROM, user space, everything..
[T-Mobile, Samsung Galaxy SIII] jtford:
using AT&T baseband

I have an AT&T i747 that I sim-unlocked so I could use NET10/T-Mobile. I've been on Wicked for the most part but recently flashed Hyperdrive. I flashed the T-Mobile version of both roms and recently cherry-picked from the two roms to my liking. In settings it's always showed me to have a t-999 since I run T-Mobile roms but the stock baseband of i747uclem. I wondered what it would do if I flashed a t-999 radio. Doesn't work. I tried a kitkat rom that required all the latest t-999 FW which I flashed with no problem except I couldn't get any service or signal of any kind. I read somewhere it would brick you if you tried to downgrade. I flashed every downgrade I could with no brick but still service. So I flashed back to i747 baseband and viola, back to perfection. I've found, at least in my case, that I can flash whatever I want as long as I stay with an i747 baseband everything works like a champ. Just wanted to post this for those that have sim-unlocked and have issues with roms for other carriers.

I'm not a full blown dev, just learned thru trial and error and help from other devs, so check it out with others before if your not sure. You'd be surprised how much you can learn from actual devs just by hitting "thanks" and throwing a little green into their PayPal. Most of them have other jobs as well so it's worth it if your serious about learning.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Negative, my S3 is running CM11 happily on MD5 :) If you haven't switched yet, now's perfect!
[T-Mobile, Samsung Galaxy SIII] jtford:
Yes, this sounds true in my case as well.

Edit: in reverse. TMO followed by ATT modem.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Interesting. Thanks for this. So, I've gone through similar stuff but didn't go through the same steps as you did. I bought an ATT i537 (S4 Active) with the intent of using it on T-Mobile. Keep in mind the i537 is fully bootloader locked so I cannot flash anything on it.

(1) Obtained SIM unlock code from ATT. Added TMO APNs and verified I could now use TMO with the phone. Verified LTE works great.

(2) Noticed at home the phone was very bad at making / receiving calls despite our Cel-Fi repeater that works great with my TMO S4. I suspected something with the radio or ROM but then realized the issue was that the i537 was not using H/H+/DC -- just E and LTE. No LTE signal at home so that explained it!

NOTE: i537 is an AWS capable device -- maybe it's the same for i747? Because it has AWS support, it can be enabled and the phone would then support TMO's HSPA frequencies. This required some hacky procedure involving exposing the phone's modem over USB and using some special Qualcomm tool and restoring someone's modem NVRAM on top of mine to get the AWS toggle enabled.

I made a thread about it here that points to the original instructions I followed. The instructions are for i337 but will work for i537. They will most probably not work for i747, at least not with the NVRAM file they provide. If i747 is AWS capable, you should be able to find a similar procedure for it. Or maybe those steps you did somehow got the flag enabled :)

http://xdaforums.com/showthread.php?t=2441211
[T-Mobile, Samsung Galaxy SIII] jtford:
I did play around in engineering mode so I guess it is possible I enabled it. That's got me wondering now! :)
[T-Mobile, Samsung Galaxy SIII] jtford:
Galaxy S4?

So is the i537 the AT&T GS4. I'm just confused because if so, I've rooted, recovery, sim-unlocked, etc., many AT&T S4's. Just wondering if we're talking about the same S4?
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Yes. The latest ATT and VZW S4s come with a locked bootloader that the Loki exploit doesn't work with. Originally it was not a problem. S4 Active, however, was never unlocked.
[T-Mobile, Samsung Galaxy SIII] jtford:
Hate to hear this!

Interesting. Thanks for the info. Since I don't own an S4 I don't really keep up with the latest that's going on with it. Good to know though because I have people left and right wanting me to set-up their S4's and I always reply with, "sure. Just get in line and I'll get with you as soon as I can. " Now I know what to look for. Thanks again.

---------- Post added at 01:57 PM ---------- Previous post was at 01:45 PM ----------

Off topic really quick; does everyone see their own "Thanks" button or just other posters? Makes sense why you wouldn't see your own I've just never noticed it until now. :silly: Derrrrrrrr!:p :p

---------- Post added at 02:18 PM ---------- Previous post was at 01:57 PM ----------

I have a JTAG RIFFBOX with full set-up and can verify your t-999 is just a little sick right now. JTAG done correctly with bring it right back to life. No worries. :good:

---------- Post added at 02:22 PM ---------- Previous post was at 02:18 PM ----------

BTW, Sorry for the multi-quoting. Just realized it was doing it.
[T-Mobile, Samsung Galaxy SIII] Kamau54:
Do I need to update my firmware? Right now, I'm running a 4.3 rom, and have no intention of going back to a 4.2 or lower firmware.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
You're on MJC which is the latest. This thread is for the MD5 firmware. (J comes after D, so MJC is newer).

There are currently no updates available past MJC and, in fact, you can't downgrade from it. Please don't flash the MD5 firmware script on your phone or you will end up with a brick.
[T-Mobile, Samsung Galaxy SIII] Kamau54:
Thanks. I just was making sure..

Sent from my Xoom using a Starfleet secured channel
[T-Mobile, Samsung Galaxy SIII] kingston73:
I've searched and didn't find anything, is there an MJC flashable zip yet, or is that not possible with the newest firmware?
[T-Mobile, Samsung Galaxy SIII] jtford:
From what I gather, MJC is the latest FW. Someone correct me if I'm wrong.
[T-Mobile, Samsung Galaxy SIII] kingston73:
Right, I know MJC is the newest, I was just wondering if there was any other way to update it other than Odin.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
I have decided not to make an MJC flashable zip because I don't see the value in it and don't want to make something that puts people's devices into a corner they can't back out of. You can always Odin or make a flashable zip of your own. If you unzip the .zip file you'll see how trivial it is. You just replace the files and edit the script which reads pretty much like English.

PM me if you want help doing it.

Correct. And can't downgrade from it unfortunately.
[T-Mobile, Samsung Galaxy SIII] jtford:
Ah, I'm following you now. If there's not one, it shouldn't be to hard to create one. Don't quote me as I'm running my mouth from work and haven't really looked into it. I will later though if someone doesn't already have one.
[T-Mobile, Samsung Galaxy SIII] PhrostB:
Why do you want one in the first place? MD5 is the best.
[T-Mobile, Samsung Galaxy SIII] jtford:
Personally, I don't. However, someone else does. I use neither.
[T-Mobile, Samsung Galaxy SIII] PainfulLover:
Mjc is required for 4.3 and 4.4. Search the forum.
[T-Mobile, Samsung Galaxy SIII] PhrostB:
You search the forums.. CM11 installs not only with MD5 but older bootloaders as well. MJC bootloader is poison to flashers.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Really? So that's why I can run CM10.2 and CM11 latest nightlies (which I've even built myself) on my T999 with MD5 firmware? You should really search the forum.

Folks, please avoid making false statements. If you're not sure whether they're true, do some fact checking first. It really doesn't help people who read through threads to read posts that are misinformative :(

MJ* firmware is not and will not be a requirement to run CM on your T999. I don't believe that you even need MD5 firmware to run CM11 -- I'm confident that it'll even run on LJC firmware.

CM does not typically EOL certain bootloaders / firmwares but they did with some old T999 firmwares due to stability issues that seemed to be related to the firmwares. This was done by Steve Kondik a while back.
[T-Mobile, Samsung Galaxy SIII] PhrostB:
Exactly.. and here's which bootloaders it allows:

assert(getprop("ro.bootloader") == "T999UVDLJA" ||

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

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

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

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

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

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

so in regards to the standard t999 that I have, it'll work fine with bootloaders as old as DLJA (android version 4.1.1, released november 14, 2012).

I don't understand why you people want to update your bootloader to EMJC. You don't make any sense to me...
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Thanks, that's exactly what I wanted to pull up but am at work and didn't have quick access to it. It doesn't make sense why people would want MJC bootloader either.

I'm thinking about making an MJC firmware flashable .zip that'll update non-bootloader stuff (power management, trust zone (?), modem (optional)) though there may or may not be a benefit to doing so. I'm honestly really worried that touching any of those separately could end up with a brick. It's quite possible it may be safe but I only have one T999 to practice on and I don't have JTAG or anyone with a JTAG setup who could fix it for me afterward.

But, like I said, the benefits / risks are not known. As a software engineer, I know well that while new releases often fix bugs, they can also introduce other issues. Unless I find someone who's got JTAG or a phone they don't mind bricking for science, I'm afraid I'm not going to dive into the MJC stuff.
[T-Mobile, Samsung Galaxy SIII] PhrostB:
I get where you're going with that. Here's what I know and don't know.

I know the MJC modem is available. I'm using it myself. I don't know what trust zone is.. and I don't know what you mean by power management.. I always thought that was a kernel function, but then again I'm not an engineer like you. Just a Linux geek :D

I guess my only advice to you would be to see what people are doing on other devices... I mean if you're really interested in it. If you're not that interested, I would just give up and keep telling people to run MD5 bootloader.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Hm, how's the MJC modem? I was hoping (and good to hear it's confirmed) that flashing the modem firmwares separately is safe.

I don't know what Trust Zone is exactly either but it's tz.bin, one of the firmware blobs that's applied when doing Odin or my MD5 firmware update. My goal when I initially created this script was to replicate what Odin does without having to lose any data.

As far as power management, there's another firmware blob that gets flashed: rpm.bin -- rpm stands for Resource/Power Management.

If you look through this thread, there have been reports of some people claiming better battery life with certain combinations of ROMs and PM firmwares. Not sure which is the one that works the best with CM on T999... Aside from playing around with it and building CM11 and such, I haven't really used my T999 since about July, when I got my M919.

I think my M919 may have a similar firmware update I've been avoiding dealing with. I should at least check out the modems I suppose :)
[T-Mobile, Samsung Galaxy SIII] PhrostB:
Well the modem runs fine for me... but here's the thing, I actually don't use this phone in the United States.. I bought my phone there a couple years ago (also wanted to buy the S4 last time I was there, but couldn't justify paying so much for such a small upgrade) and I since I live in Israel, I use my t999 here instead.

So I can't really objectively say which modems are better or worse.. I just kind of run off of the assumption that modems are constantly being improved, but I really have no evidence to base that on.. truthfully I think most people that claim that they get improvements in "snappyness", battery life and signal strength are just bull****ters.
[T-Mobile, Samsung Galaxy SIII] kingston73:
I guess I don't really want it, seems like there's no real reason to change from the md5 bootloader. I am using the newest modem and it definitely works better than md5 for me with the AOKP based 4.3 rom I'm using.

So tell me if I have this correct, if you update to the newest bootloader you are stuck with it. Is there any way at all to factory reset your phone after you've done this or will tmo and/or samsung be able to tell if you've put a custom rom and recovery on?
[T-Mobile, Samsung Galaxy SIII] PhrostB:
I think the problem with the latest firmware in general is the NOX security and inability to downgrade to an earlier version. I'm not an expert though..
[T-Mobile, Samsung Galaxy SIII] mnasledov:
A factory reset is just a data wipe basically. That doesn't downgrade or upgrade firmwares. You'll still be stuck with MJC.

We can still use custom ROMs and recoveries with MJC but it adds the Knox security stuff, so you will not be able to downgrade firmware blobs, at least not bootloader related ones.
[T-Mobile, Samsung Galaxy SIII] kingston73:
I guess I worded that wrong, I meant by "reset" putting the phone back to factory condition if you wanted to send it in for a warranty exchange or repair. I know with the md5 firmware you can still use Triangle Away and reset all the counters back to 0 so it looks like the phone was never changed.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
No. If you try to do so -- putting your phone back to say MD5 from MJC -- then you will brick the phone and end up unable to fix it without a JTAG rig. I don't even have one of those.

There's a $2870 bounty right now for being able to reset the Knox counter: http://xdaforums.com/showthread.php?t=2486346

Any more questions? :P
[T-Mobile, Samsung Galaxy SIII] PhrostB:
That was an interesting thread, spasiba! :D
[T-Mobile, Samsung Galaxy SIII] jtford:
That's weird, because I go back and forth all the time. Just posted a topic in att and tmo S3RX threads talking about how my signal sucks on MJB & MG2 so I went back to bootloader/modem package LK3.

BTW, I do have a riffbox if you need any JTAG work. ;)
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Here to confirm I did the same thing with the new firmware NC2 as with MJC when I reported in this thread. I mean, flashing official ODIN firmware, then flashing TWRP via ODIN, wiping (/data, /system and both caches) and then restoring my good old 4.1.2 nandroid backup. I can go back and forth between ROMs no problem, as always. :good:
[T-Mobile, Samsung Galaxy SIII] mnasledov:
But of course. The problem is you won't be able to go back to any previous bootloader. Not sure what MJC and NC2 offer for a non-TW ROM.
[T-Mobile, Samsung Galaxy SIII] nirogu325:
That's not a problem. MD5 or earlier bootloaders don't offer me anything either. It's all a non-issue, really. Also, the newer bootloader and modem might have something to do with this and that is more important than keeping MD5 or earlier.
[T-Mobile, Samsung Galaxy SIII] rigel1326:
I am running 4.3 with baseband/modem MJC and firmware MJC. My phone intermittently drops calls as this is a known problem/issue. Is there a flash for the MD5 baseband/modem only? I don't seem to see it, although I thought it use to be there, and there are explicit warnings not to flash the complete update zip if you are on MJC. I just want to get my calls to stop dropping. What should I do? Thanks!
[T-Mobile, Samsung Galaxy SIII] kingston73:
You can flash whatever modem alone you want, I think if you try to flash any other older firmware you will brick your phone though. The baseband/modem thread lists all the available modems and there is also now the nc2 modem that was just released you could try. I'm still on the md5 firmware but I'm using the nc2 modem and for me it's working well.
[T-Mobile, Samsung Galaxy SIII] qzmicro:
I currently received a new T999. I read up about installing CM11 and most info was a bit dated. I finally found a thread that looked like the information I needed and it stated that I should use the bootloader/modem firmware on this post. I downloaded it, installed it and just like kingston told rigel1326, I bricked my phone. First time I have ever done so. I was looking for something that would support Kit Kat and the first few pages of this specify to use the file in this post.

My question is... am I dead in the water? Phone doesn't seem to want to start up. :( Please advise, thank you.

-Tony
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Oh no, please don't tell me you tried to flash this older firmware onto a T999 with newer, non-downgradable firmware :( I hate to be the bearer of bad news, but it's in bold and red in the first post and as far as I've seen it invariably results in a hard brick. You can get it repaired by someone with a JTAG rig or if you've received a phone from say a T-Mobile store just claim it stopped working on you and try to get them to replace it.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
You can also try the debrick method stickied in this very forum. But please make sure you read ALL the information before attempting.
[T-Mobile, Samsung Galaxy SIII] notufatjesus:
OK...MY BASEBAND SAYS....T999UVUEMJC (UNDER SETTINGS/ABOUT PHONE). Means I can't flash UVDMD5 firmware? Just want to make sure...not sure if baseband is the same thing as firmware. Also....how can we find out what bootloader we are on?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Baseband is not a reliable way to determine your firmware/bootloader build. Many people are running a mix of the two. To find your firmware version, install terminal emulator and enter this:

getprop ro.bootloader
[T-Mobile, Samsung Galaxy SIII] qzmicro:
I hat to admit, but I have been putting ROMs on this phone without a problem for a very long time. I usually read very carefully but I must admit, I am willing to try anything to both learn from this and fix it if possible. Last case scenario I will attempt to return it. I do have RMA warranty on it. What are the odds that if it doesn't even turn on that T-Mobile will take the time to check it for tampering? Any insights fellas?

-Tony
[T-Mobile, Samsung Galaxy SIII] qzmicro:
Will this work for me? I can't seem to turn on my phone...

Hi DocHoliday,

Would you be able to tell me if this will work for me? My device won't turn on at all. No lights, no screen, no nothing. However, when I hold down the power button it flickers my computer screen (when plugged into the USB) every few seconds as if it was trying to power on. I have no signs of live otherwise. The debrick method is for someone who can see the red led when plugged in or something, right? Should I try it anyway? Please advise, thank you.

-Tony
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Check device manager. If it says QHSUSB_DLOAD, its hard bricked and the debrick thread should help.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Easy. I don't have an S3 anymore so this is on my S4. If your S3 has any bootloader newer than MD5 such as MJC or that new N one, don't even dare flashing this. It will hard brick your phone. And if you have MD5 bootloader already, no point in flashing this.

[11:18:56] [misha@galileo:~]
$ adb shell
shell@jfltetmo:/ $ getprop ro.bootloader
M919UVUAMDL
shell@jfltetmo:/ $
[T-Mobile, Samsung Galaxy SIII] qzmicro:
Hi Doc. I do indeed see the the Qualcomm HS-USB QDLoader 9008 (COM10) on my device manager in windows. It detects the drivers for this just fine as I do not have an exclamation mark or question mark around it. I tried a first go at the SD but it did not work. Any suggestions?

-Tony
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Don't give up! Many people had to run through the debrick method several times before it actually worked.

If you cant get that method to work though, you'll need to send it somewhere for a jtag service. I heard about one only costing $28 the other day, so let me know if you decide to go that route and ill find out who it was for you.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
[MENTION=3090489]mnasledov[/MENTION]

Just fyi, packages like these for the kk firmware are not a good idea right now. People in Sprints forums were having problems with it, maybe even bricking. Just letting you know because we all know someone is going to "ask for it"!
[T-Mobile, Samsung Galaxy SIII] qzmicro:
Hi Doc,

After flashing 4.3 firmware and then flashing the bootloader/modem firmware I shouldn't have... I am ready to try a JTAG service. The unbrick method with the SD card isn't working. Even though I see the COM device in windows (it is a known device when I plug it in) it does not boot from the SD card after writing the image to it. I have tried with windows and Linux. I have tried with 4.3 and non 4.3 just for kicks. I have also tried battery pop'ing and re-seating the SD over and over. I tried with the USB cable plugged in and without. I am not sure what else to do.

Would you be able to recommend one to me? I was thinking of brickedmyphone.com.... but I do not know them from Jon Doe. Any recommendations as to who to use? I sure would appreciate it. Thanks!

-Tony
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Mobiletechvideos.com is the only one I know about.