yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Yes. But first I need to know the model of your phone so we know if thats even the actual problem.
[T-Mobile, Samsung Galaxy SIII] oreice:
Ok funny stuff I just went to check what it was and up ubtil this time its always said sgh-t999 now I go and it says sgh-i747 how the hell did that happen?
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Can you give us an idea of your exact phone setup?

Model:

Carrier:

ROM (incl. vers#):

Recovery (type & vers#):

It's interesting that your phone would suddenly say I747 from flashing UVDMD5 stuff as it's all T999-specific. Anyway, we'll be in better shape to help you with more information.

Thanks.
[T-Mobile, Samsung Galaxy SIII] oreice:
Ok fixed model problem it was the Rom I flashed so its sgh t-999 t-mobile currently on hyperdrive rls 15 recovery clockwork mod v6.3.0.1

---------- Post added at 10:43 PM ---------- Previous post was at 10:39 PM ----------

Update I got it I literally just had to update cwm
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
I'm guessing you were on SlimROMs lol
[T-Mobile, Samsung Galaxy SIII] samipsth:
Please Help

help needed

i flashed the zip through CWM everything went good but after the re boot phone no more boots up, unable to goto download or recovery mode

thanks
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Whoa, no need to quote my entire post! That sounds like a not fun situation. Are you sure you flashed it on an SGH-T999? If you try to flash on SGH-T999V or SGH-T999L or any other variant this is what happens :(

You still have hope for recovery I think. There's a way to get a phone into Download Mode with a special USB jig (costs $2)

However it's possible that may not work. Check out mobiletechvideos.com -- they have the USB jig (which you can also find on eBay) and there's also an "Unbrickable Mod" that is supposed to fix even hard bricks. I have not attempted it, but last I heard it works on T999. I'm not sure about variants such as T999L.

Here's a thread about it... You might want to just contact the people on the mobiletechvideos.com site. http://xdaforums.com/showthread.php?t=2023069

If all else fails, do you still have warranty? When did you buy it? If it's new enough, you can just claim "It doesn't work" and have TMO replace it for you. It's not like they can prove you bricked it since they can't get it on either..
[T-Mobile, Samsung Galaxy SIII] Kelevro:
Sorry for the really nooby question, but, to reiterate: all I have to do is flash it via recovery - and I don't even have to push it using ODIN (that program scares me)?

Will this work for my device:
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
You would be better off checking under your battery. Make sure it says T999 and not T999L, etc. If so, then yes, assuming you have the correct device, all you would need to do is flash the zip in twrp or cwm.
[T-Mobile, Samsung Galaxy SIII] Kelevro:
Nailed it - right under the batter it says "SGH-T999." Thanks for the help! Hope all goes well!
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Yes. But I wouldn't recommend flashing MD5 firmware on top of stock LH2 ROM. I don't think it will brick but I do think that it would be sub-optimal. Either upgrade to MD5 stock ROM (use Odin), install a custom stock ROM based on MD5 + this, or install CyanogenMod + this.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
That's just his baseband. Rom appears to be md5 based.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Ah, OK. Don't know stock ROMs at all. Then go for it!!!
[T-Mobile, Samsung Galaxy SIII] Kelevro:
Sorry, I should have said the ROM that I'm using was based off that! Thanks for the help; time to flash.

Oh, wow. The new modem and baseband upped my internet (WiFi - have yet to test 4G) speeds by ~6-7Mbps. Adding another thanks to your meter, mna!
[T-Mobile, Samsung Galaxy SIII] maxxcool7421:
good morning, er evening if your way overseas.

i am trying to install this bootloader + baseband update but and getting a very simple error that is not making sense : assert 7

opened the zip and took a look at the install script and it only has one device check : assert(getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo");

I grabbed build.prop off the store and took a look even though i have looked previously and i am still listed as :

ro.build.product=d2tmo

ro.product.model=sgh-999

ro.product.name=d2tmo

ro.product.device=d2tmo

ro.build.hidden_ver=t999uvalh2

so both check are 'good' but the script fails. thoughts? is it a permission issue ? the device is rooted from way back when it 1st came out using odin3 v1.85 in a prepacked 4 click tool. :p

thoughts? I am afraid to remove the assert line since this is the bootloader and i am terribad with adb and full phone partition recoveries.

thanks in advance..
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
You probably need to update your recovery. But also, don't trust an app or settings to tell you your device model. Look under the battery instead.
[T-Mobile, Samsung Galaxy SIII] maxxcool7421:
phone settings are sgh-t999 as well.

as for updating recovery .. ? ? not sure how beyond what i have installed.. i have cwm 6036... so really recent but not 100% current.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
After attempting a flash again, copy log to sd, it should tell you more about what exactly is causing the problem.
[T-Mobile, Samsung Galaxy SIII] maxxcool7421:
filename / location ?:confused::confused:

---------- Post added at 11:35 AM ---------- Previous post was at 11:13 AM ----------

odd... it is not generating a log ..

just get a assert failed code 7.. not text/log file in the cwm folder.. will try from external sd card and not the internal card .. brb

---------- Post added at 11:42 AM ---------- Previous post was at 11:35 AM ----------

double confirmed. no report.log is generated on the external sdcard or internal sdcard in the clockworkmod folder.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I won't just be there after a flash. Are you telling recovery to copy the log?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Ok, no you have a regular T999. LH2 bootloader wouldn't be there otherwise.

Go to /system/build.prop and open it as a text file. Look for the device model. Does it say T999, I747, or a variant of either? If so change to T999 if need be.

Do you see any entry saying d2att, or d2can, or similar? Make sure all say d2tmo.

Save and try again.

---------- Post added at 03:18 PM ---------- Previous post was at 03:17 PM ----------

Long way around...

Flash TWRP from my Sig first (don't think.I put any asserts in there) then if you still want CWM, flash from TWRP. (Or just flash the firmware).
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Wow! You certainly have a, unique, issue!

I think if you delete the assert lines and signatures, you should be fine to flash it. I honestly cant see any logical reason it would fail or hurt the device. In the end, it is your call though!
[T-Mobile, Samsung Galaxy SIII] maxxcool7421:
I know right ?? for some reason the s3rooter used a hacked recvoery file.. not suer if that was part of the root method *back then* or not but yeah... wierd and dumb.

thanks for pointing me to the report.log... that started the ball rolling. thank you for your help!

---------- Post added at 07:09 AM ---------- Previous post was at 06:59 AM ----------

JJUUUUUSSSTTTT out of pure curiosity ... what signatures? the sha hashes ? the items in red after the assert line I might delete ?

assert(getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo");

ui_print("");

ui_print("T999 UVDMD5 Firmware Upgrade (w/Modem)");

ui_print("");

ui_print("Extracting files and setting permissions...");

package_extract_dir("files", "/tmp");

set_perm(0, 0, 0777, "/tmp/dd");

ui_print("Verifying checksums...");

if

sha1_check(read_file("/tmp/dd")) == "980a4022e8171e67d038d8f44db3992363e33083";

sha1_check(read_file("/tmp/aboot.mbn")) == "38a7a53a8dabd727d5a1cb15e8fca0977d91d9fe";

sha1_check(read_file("/tmp/NON-HLOS.bin")) == "4f86bb4f1bd4bbeb3147ce0add167263556ffb05";

sha1_check(read_file("/tmp/rpm.mbn")) == "c20cef874ea59150f0a140da62caab2275b0d121";

sha1_check(read_file("/tmp/sbl2.mbn")) == "63d4eae21c100ff686fa4e2deeac4ade2465fb23";

sha1_check(read_file("/tmp/sbl3.mbn")) == "3fb10c767bb9234ac09c1f76c71ec9e2d99e7c74";

sha1_check(read_file("/tmp/tz.mbn")) == "0d51c8887ccbc6829d34dce6aa3c3b31a64e8e08";

then

resulting in this update script ? :

ui_print("");

ui_print("T999 UVDMD5 Firmware Upgrade (w/Modem)");

ui_print("");

ui_print("Extracting files and setting permissions...");

package_extract_dir("files", "/tmp");

set_perm(0, 0, 0777, "/tmp/dd");

ui_print("Updating firmware...");

run_program("/tmp/dd", "if=/tmp/aboot.mbn", "of=/dev/block/mmcblk0p5");

run_program("/tmp/dd", "if=/tmp/NON-HLOS.bin", "of=/dev/block/mmcblk0p1");

run_program("/tmp/dd", "if=/tmp/rpm.mbn", "of=/dev/block/mmcblk0p6");

run_program("/tmp/dd", "if=/tmp/sbl2.mbn", "of=/dev/block/mmcblk0p3");

run_program("/tmp/dd", "if=/tmp/sbl3.mbn", "of=/dev/block/mmcblk0p4");

run_program("/tmp/dd", "if=/tmp/tz.mbn", "of=/dev/block/mmcblk0p8");

ui_print("Done!");

else

ui_print("File corruption is present, aborting upgrade.");

endif;

ui_print("Cleaning up...");

delete("/tmp/dd", "/tmp/aboot.mbn", "/tmp/NON-HLOS.bin", "/tmp/rpm.mbn", "/tmp/sbl2.mbn", "/tmp/sbl3.mbn", "/tmp/tz.mbn");
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
No, just the assert line and the signatures are the files under Meta-Inf, if they are there. If they are not, then disregard. Do not remove the sha checks though, that is all that is protecting you in the event of a bad download.
[T-Mobile, Samsung Galaxy SIII] maxxcool7421:
Triple confirmed ...

C:\Users\Downloads\T999_UVDMD5_firmware_v4\META-INF\com\google\android

only other file that exists is the "update-binary" in the full meta-inf filepath ..

so in theory ... were i brave. i could delete the assert line and go for it.

will a full backup from cwm recover in the event of a full on cluster-ffff? or is the recovery image and radio separate from cwm backups ?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Nandroid generally only include /system, /data, modem, and kernel. This flashes everything from the official firmware which is much more, so no a CWM backup won't protect you from messing up.

The signatures would be under Meta-inf, not all the way down with the script and binary.

As long as you are certain yours is a T999, it should be ok to flash without the assert line.
[T-Mobile, Samsung Galaxy SIII] maxxcool7421:
Thanks!! :o

---------- Post added at 12:22 PM ---------- Previous post was at 12:03 PM ----------

Since this is a modem update, do i need to do anything to the dalvik cache? clear system or any of the other things normally done to flash over a new rom ? I assume not... but better to ask than brick ignorantly ..

---------- Post added at 12:50 PM ---------- Previous post was at 12:22 PM ----------

still failed. grr. will get the log later. but onto a bigger project now..

how do i replace the "hacked' recovery image / loader i ended up with? i assume i just need to get a good recovery image and drop it back on. Is there a samsung repository of stock images that xda trusts ?

such as this link : http://samsung-updates.com/device/?id=SGH-T999

thanks in advance... i think my goal now is to get back to stock, then root the right way, then go after a cynogen 10.x ... thoughts ?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
There are recovery files in my signature you can try if you want.
[T-Mobile, Samsung Galaxy SIII] maxxcool7421:
sweet... thanks! again!:p:p
[T-Mobile, Samsung Galaxy SIII] jtford:
Should be able to open terminal and type [fastboot getvar version] (Without block ends of course)
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
just curious, does that return the same info as "getprop ro.bootloader"? Sounds like it would, but i wasnt familiar with it so am curious....
[T-Mobile, Samsung Galaxy SIII] mnasledov:
There's your problem... You're trying to use it on a dtatt? That'd be a brick.

EDIT: If that's a d2att ROM on a d2tmo, then it's OK to install but it explains why it fails the assert. You can comment it out. I wonder if there's a better way to check in my script.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Well in theory, but I think getprop reads from the build.prop file while fastboot actually talks to the bootloader. I didn't know fastboot worked on Samsung devices,I thought we had to use heimdall entirely.

In theory someone could be running a d2att ROM on their d2tmo and this check would then fail because getprop isn't actually querying the true data from the bootloader like fastboot or heimdall should be able to.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
so if you are correct and fastboot does query the bootloader directly, it would be a more reliable check than getprop, right? if it does indeed work on our device, i wonder why no one uses it.

wish i could try....
[T-Mobile, Samsung Galaxy SIII] mondokat:
New OTA is out

time for an update to this zip...
[T-Mobile, Samsung Galaxy SIII] joss7099:
What is the difference T999UVDMD5 and T999TUBEMJC? http://support.t-mobile.com/docs/DOC-4446
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Thanks! Didn't realize this was out now.

You do realize the new one adds Knox support though? The next firmware updater has to specifically not include whatever security stuff Samsung throws in -- or perhaps offer several variants of it (secure and non-secure)

I've upgraded to a M919 a few months back but I still have my T999 for dev purposes. It looks like the only real value proposition of this update is Samsung Gear support and *possibly* a better modem (uncertain), as well as KNOX, which breaks installation of custom stuff.

I've been reading up on the KNOX stuff but have to read up more on it. I'll guinea pig my own T999 but I want to be certain before locking myself out of it potentially. Also as I've been busy lately and I haven't touched my T999 in months, I can't guarantee I'll get around to it soon unless there's enough demand.
[T-Mobile, Samsung Galaxy SIII] jtford:
You can also look in Root Explorer or similar, or extract from rom.zip, look under system/CSCVERSION.TXT
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
knox + seLinux = suck!

they do seem effective though when working together. all roms are going to have to have knox removed and the insecure kernel which sets seLinux to permissive.
[T-Mobile, Samsung Galaxy SIII] mondokat:
Does Knox prevent the boot loader from running custom code? Just curious the extent of the lockdown. It would block running modified stock, but not something completely custom like cm10.2, right? Although cm's assert check probably hasn't been updated with this version yet...
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
knox does partially include the bootloader, but the meat of it is built into touchwiz
[T-Mobile, Samsung Galaxy SIII] mnasledov:
As long as it doesn't prevent flashing of custom recovery and ROMs, I have no issue with making the full firmware updater. I just don't want to be the one to write someting to lock people out of their phones, of course.

Has anyone done a full Odin flash of it yet and gone back to CM? Any issues? If none, I'll go ahead and make a new updater and test it on my T999 before releasing it.
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Well, I ODIN'ed to 4.3 earlier today, and got back to 4.1.2 via nandroid just fine (hate how TW looks in 4.3, especially Settings). I did the getprop ro.bootloader command and it says MJC at the end. All good here. Haven't yet tested an AOSP ROM.
[T-Mobile, Samsung Galaxy SIII] mondokat:
I think what knox does is in the bootloader is a checksum of what the contents of the system directory should be. It sounds like you probably still have the new bootloader but the old system files, so the bootloader won't prevent booting if the checksum doesn't match. That means that touchwiz itself, the os in the system directory, must reference the bootloader to see if it matches (the os verifies itself) before running. That means modified stock 4.3 will likely have issues (rooting will be hard with knox turned on).

The other thing that will likely have issues is that the cm10.2 installer checks the ro.bootloader value and if it's not in the list, it bails out of the install. This won't affect nandroids, but will affect clean installs and upgrades. Luckily, cyanogen just needs to add that new string to their installer and it should be fine again.

Since the bootloader doesn't seem to not run custom code (yes, there was a double negative there), it should run CM just fine, since CM doesn't use knox to verify the system. CM just needs to update that string and we'll be good to go.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
[MENTION=3090489]mnasledov[/MENTION] You can reflash CM after the firmware upgrade. I did it, working fine.

However, I strongly advise against making a new firmware package at this time due to issues we are having with downgrading back to MD5. It looks like MJC might be a one way upgrade.
[T-Mobile, Samsung Galaxy SIII] mondokat:
Not sure I believe this.

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

this is the latest commit I can see in github that references the bootloader versions. that was 4 months ago...

Here is the updater script from the latest nightly on get.cm:

assert(getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999VVLDLL1" ||
getprop("ro.bootloader") == "T999LUVAMB7" ||
getprop("ro.bootloader") == "T999VVLDMF2");

Not to be an ass, but you are wrong, unless you mean your nandroid restore worked, but that doesn't use the updater script. Next upgrade, you will be screwed.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Aerowinder is plenty smart enough to solve a simple issue like that. He does things like that and much, much more all the time.

You can pretty much always rely on what he has to say.
[T-Mobile, Samsung Galaxy SIII] nirogu325:
I wiped everything (in TWRP) before ODIN'ing using the Sammobile file so I don't think I have the "old system files". I flashed SlimBean just fine yesterday.

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
[MENTION=3090489]mnasledov[/MENTION] Can you put a disclaimer in the OP to ward off those that are on 4.3 and attempt to go backwards? This will 100% cause a brick in which I'm unable to recover as of right now. I am going to try some things tonight to try to get [MENTION=4081205]DocHoliday77[/MENTION] and another user back online. Then the s3 has to 100% go away as it is now technically my mother-in-laws.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
i agree that a warning would be good idea.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Ouch! OP updated. I remember talk on the S4 forums of the new firmware with Knox. Downgrading or trying to even flip the Knox flag = brick. However, if you can get latest firmware back on there with Odin or something, it should work. Have you tried the USB jig to get it into Download Mode yet?
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Wait, how do I know I have the Knox thing? Because in Download Mode, I don't see anything that says Knox.

Sorry for crappy pic - was taken with the old Vibrant.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
I forget what the visual indicator(s) are (there's a whole discussion thread on this on XDA), however the latest firmware explicitly adds Knox support according to Samsung's own site.

The newest Galaxy firmwares, as far as I understand, blow efuses on the device to prevent firmware downgrade.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
confirmed 2 devices bricked trying to downgrade with this method. i had hoped that by being recovery flashable, it would allow us to get around the downgrade block...

if im not mistaken, a jig just forces it to boot whatever downliad mode is already present on the device.

ours doesnt have the knox counter exactly. the one we have to worry about is the Warranty Bit. itll probably break knox containers like the Knox counter does on other devices though. (not confirmed)
[T-Mobile, Samsung Galaxy SIII] nirogu325:
The Warranty Bit turned to 1 as soon as I flashed TWRP through ODIN right after booting up MJC. Since my device is more than a year old (and I'm no longer with T-mo) I don't worry about it.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Yes, it's worth trying to see if it's possible to get it to at least get into Download Mode. From there it's easy to get it back to latest MJC firmware to unbrick a failed downgrade, assuming getting it into Download Mode works at all. Hopefully fixing it doesn't require JTAG.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Looks like I9300 has a KNOX-free update: https://www.xda-developers.com/android/knox-free-android-4-3-leak-now-official-for-the-galaxy-s-iii/

I don't know too much about I9300/T999 compatability though. I'm pretty much assuming taking some of the lower level firmware blobs like aboot would probably result in brick.

Here's an XDA thread on the I9505 forum that discusses the Knox stuff and current discoveries / findings around it.

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

Warning: Lots of people posting referring going "back" to previous version are actually referring to the ROM, not the whole firmware package. As far as I know, it is not possible to downgrade any device firmware after going to MJC.

Since MJC's lockdown is limited, this may not be completely undesirable. However, it certainly boxes a T999 owner into a corner for reasons I can't really justify. Yes, if you run the stock TW stuff, it will let you use their Galaxy Gear stuff. Correct me if I'm wrong but there's nothing stopping someone from interfacing with the Galaxy Gear stuff with a T999 on MD5 or even older firmware and CM10.x?

At this point in time, I'm not sure about writing the updater. It would only take a couple of minutes but I don't want to box my phone into a corner, so I wouldn't want to flash my own T999 over. I also don't want to provide some script that some people may use without reading all my warnings / understanding the full consequences. The MD5 update is safe since you can jump between it and older firmware sets.

If there's enough demand and someone wants to guinea pig it, I can write an MJC updater. It's trivial to update my updater -- I think I'd spend 99% of the time just downloading the Odin image and spending several minutes checking everything over multiple times... I would only release it with a lot of cautions and preface the entire thread with, "Do you really need this???"

EDIT (warning bad joke): If it were ever possible to write something to free the firmware of KNOX, that piece of software ought to be named Octane or Lead or Plumbum or something ;)
[T-Mobile, Samsung Galaxy SIII] truckerdewd:
You might want to check out the links in this post. I only skimmed through part of the second link since I was driving and couldn't really devote time to it.

http://xdaforums.com/showthread.php?p=47694353

Sent from my wickedly awesome Galaxy Note 2 using my fingers. Duh!!!
[T-Mobile, Samsung Galaxy SIII] hccaus:
did not read this warning. and now i completely bricked my T999 :(

just handed over to a repair store today but they are not sure yet since they are going to send it to different store for JTAG fix...

T_T... I tried to downgrade without reading the description carefully....

any luck from JTAG fix might bring my phone back to life?
[T-Mobile, Samsung Galaxy SIII] mnasledov:
D'oh! :( JTAG ought to save it from what I've seen on forums with people messing with this firmware and bricking their phones.

I'm curious if you tried to see if the USB Jig would initialize download mode or not?
[T-Mobile, Samsung Galaxy SIII] anil2653:
+1

Thanks mnasledov

You are 100% correct

Even after putting warning to not to flash / downgrade firmware, if anyone is on latest official bootloader

Still people are doing and bricking devices

It is better to keep this POISON away from the reach of........