yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
You're on the latest Canadian firmware so you should be good to flash later builds
[T-Mobile, Samsung Galaxy SIII] wangxp:
SO ,you'd mean that we flash the Bootloader only for CM 10.1 ROM?

SO ,you'd mean that we flash the Bootloader only for CM 10.1 ROM?

---------- Post added at 06:07 AM ---------- Previous post was at 05:57 AM ----------

Does someone has posted thread like how to restored original Bootloader?

It's important , I only know that I used HTC Phone before It has Bootloader. It's the same thing???????
[T-Mobile, Samsung Galaxy SIII] mnasledov:
I only had HTC phones before too. It's a bootloader -- just like HTC has HBOOT. It's a bit different in how you interface with it and what limitations it presents (on SGH-T999 it's just "secure" but unlocked, the "secure" flag really means nothing for our purposes.)

The latest CM10.1 nightlies require a bootloader with minimum version of UVDLJ4. Cyanogen made this so as there were reports of lots of random crashes/reboots that seemed to be correlated to older bootloaders. I'm calling this overall package the "firmware" as it's the collection of the bootloader, various bootloader related partitions, and the modem.

You can always go to this firwmare or back to any other using Odin or heimdall but this packages it up in a convenient update.zip. This is what the latest OTA from T-Mobile would install on your phone, too.

If you have the minimum bootloader version and aren't having problems, you don't necessarily have to flash this update.

It's also easy to roll your own update.zip if you take mine as an example and substitute the correct files and edit the script with the correct SHA1 sums. Or maybe I'll make that self-serve update.zip firmware flasher generator script thing soon... You should run the backup script linked to in the first post if you're concerned about rolling back. Also make sure you have the US T999 not the Canadian T999V.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Thanks to GenericAsianGuy I've been able to confirm the partition tables for T999 and T999V are the same at least as far as these firmware blobs are concerned.

I'm downloading the VLDLL1 Odin package and will be making an update.zip for the T999V.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Ah, thanks! Too late, though, I just checked my email / XDA and have already made it from the full downloaded package (I know, what a waste of 700MB!) I'm going to make a separate thread for it and link to it shortly. Thanks for all your help man.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Here it is for all y'all Canadian folks! http://xdaforums.com/showthread.php?p=41701398

Sorry I don't have any maple syrup to go with it ;)
[T-Mobile, Samsung Galaxy SIII] droidsung:
Just updated my LJC with your custom UVDMD5 zip and I must say the coverage and DL speeds have definitely improved.

If it helps anyone, I'm using the SGH-T999 in India on an Airtel sim right now.

Thanks.
[T-Mobile, Samsung Galaxy SIII] LoopDoGG79:
Someone correct me if I'm wrong, but the bootloader will have no effect on DL speeds and coverage. I'm calling this placebo effect.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
The bootloader shouldn't, but this update.zip flashes over the UVDMD5 modem as well.

It's interesting, though, that Cyanogen had to up the minimum bootloader version to fix rampant reports of random crashes/freezes. Kind of makes me think it's somehow involved beyond the boot process.
[T-Mobile, Samsung Galaxy SIII] theinitial21:
this is interesting.... so then if I'm on the LJC then mine is apparently old?
[T-Mobile, Samsung Galaxy SIII] mnasledov:
LJC was the one right before MD5. I've found better radio performance under MD5. LJC will work, though, with current CM10.1 nightlies.

Note this update contains the bootloader and modem (baseband).
[T-Mobile, Samsung Galaxy SIII] theinitial21:
better performance is always nice. i live out in the sticks so I get 2 bars of signal, i'll flash ur version and see if it improves. just one question tho. if i was to flash other roms like a TouchWiz one, that will still work right?
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Correct. The newest TW ROM flashes all this bootloader + modem stuff my update.zip does. Some tweaked stock ROMs have even begun to use UVDMD5 firmware as you can see in the T-Mobile Galaxy S III Android Dev forum.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Just fyi, there are many modems you can try out. If you have a weak signal it can't hurt to try the others too. Check the map in the modem thread as well to see if anyone has reported for your area.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
For sure. Maybe I should make another bootloader update.zip that doesn't update the modem for people who know what they're doing with the modem.
[T-Mobile, Samsung Galaxy SIII] xxtavarxx:
What does this do?:confused:
[T-Mobile, Samsung Galaxy SIII] PainfulLover:
Worked like a charm! Thank you :thumbup:
[T-Mobile, Samsung Galaxy SIII] mnasledov:
In a nutshell, this basically has the effect of flashing the latest TouchWiz ROM, as you would get it from T-Mobile, via Odin but without touching your system, kernel, recovery, or data.

It just updates some of the underlying software like the bootloader and modem to the latest versions without requiring the inconvenience of flashing another ROM and then restoring from backup to do it.

If you're already able to install the latest CM10.1 nightlies, then you have a recent enough bootloader and it's not certain if the newer MD5 bootloader provides benefit over a version or two earlier. It certainly doesn't appear to make anything worse by any measure.

The other added benefit is it updates your modem to the latest one, but there's a thread that has all the modems as separate flashable updates and a collaborative Google Map that allows people to share their modem performance as it's been reported people have different experiences with the same radio version depending on where they are.

Using this firmware update doesn't preclude you from flashing other compatible radios afterward either.
[T-Mobile, Samsung Galaxy SIII] Woody:
I would suggest doing this. Some people don't necessarily want the new modem because of one reason or another. If you put too many variables in there, someone is bound to ask/imply/assume more than they really need too. Keep it simple, you know.

Funny story btw. When I first got this phone I was on ICS/LH2. I have flashed almost all the ROMs we have available, all the leaks and modem in one form or another and have never Odin'd back to stock beyond LH2 (I made my own rooted, Odin package way back when). I did the getprop command and even though I am currently running the latest RootBox (JB Rom) nightly, I still had the LH2 (ICS) bootloader. I flashed this package and updated just fine. But it made me think to myself that maybe I need a house cleaning of sorts on my phone, although it runs like a dream and I might not want to mess with it at this point ;).
[T-Mobile, Samsung Galaxy SIII] shenry1307:
[MENTION=3090489]mnasledov[/MENTION] - Just flashed your radio (only)... No problem... I'll monitor performance and let you know how it does in SE Texas. :good:
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Just updated the thread with more details as to what the "firmware" files are and made a version of the script that doesn't flash the radio.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
So it turns out this also updates other stuff like firmware for power management and "trust zone" (whatever that is)

I wonder if the MD5 RPM (Resources & Power Management) blob has any real improvements. I do seem to be getting superb battery life lately but thought it was a combination of uninstalling some crap and CM's last nightlies being particularly good.

I updated the OP with details as to what is updated with this package.
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
Funny thing was I thought it would help but I quickly found out my random reboots were going no where.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Well then you've got other issues going on. Sorry this didn't fix your problem. I advise you take a close look at what's installed, what services are running, etc.

I recommend highly ES Task Manager -- you can prevent a lot of crap from starting up with the Startup Manager.

FWIW, CM10.1 nightlies have been pretty flawless lately. blk_jack has been egging me to try SlimBean but I'm a CM purist.

EDIT: CM10.1 has been so great lately on its own, I've even stopped using Imoseyon's LeanKernel which I used to consider a must-have for running CM10.1 smoothly. He made a great kernel but doesn't seem to have been updating it recently and now CM10.1 stock kernel is working well enough for me.
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
Thanks for your help and your work it is highly appreciated. Slim bean was the only 3.4.y ROM that wouldn't give me random reboots actually. I've since jumped back to Liquid Smooth 2.1 where everything has been flawless on 3.069.
[T-Mobile, Samsung Galaxy SIII] thatsaabguy:
So, I just did the download and install, and it went well...but now, my phone is hanging on the Samsung screen, after the animation, jingle and the flying Android robot. I tried an Odin install to overwrite it, but no change. I'd been running the CM 13 May ROM on here before the flash, but that shouldn't make the thing freeze on first boot, would it? As of right now, I appear to be bricked, which sucks. Any suggestions?

---------- Post added at 08:26 PM ---------- Previous post was at 08:12 PM ----------

Of course, doing a data/cache wipe got it to boot. I feel stupid now. Crawling back under my rock...sigh...
[T-Mobile, Samsung Galaxy SIII] mnasledov:
That's a bit strange. Can you guide me through the steps you did? The firmware and even modem update shouldn't need a wipe data/cache. I'm glad you got your stuff working again but I'm regretful that it forced you to do a wipe.
[T-Mobile, Samsung Galaxy SIII] thatsaabguy:
Meh, no big, I've had to wipe plenty of times with CM10 updates over the last year.

I simply followed the directions you offered at the beginning of the thread: download, install, boot to Samsung screen and stop cold. I tried a different version of the same thing from another website, one that requires you to run Odin, which I did and got a green-light install, but the exact same thing happened - froze on Samsung screen.In the end, the only thing that got me rolling again was the hard wipe. I'm reinstalling apps and such now, nice way to kill a rainy afternoon in Seattle :)
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Hm, if you were stuck at that screen then the device was booting the kernel and trying to init the main processes but something kept failing. Very strange.

My scrpt only touches the appropriate partitions of the eMMC so somehow the system must have not liked the different firmware during boot-up.

I wonder if a simple Wipe Cache (incl. Wipe Dalvik Cache) would've worked. At least you're used to wiping -- to be honest, wiping my system drives me nuts. I wish I could take it that easily :)

(Unrelated) I had some corruption on my system once after flashing a nightly and trying to restore to previous backup, which ended up failing due to ext4 errors. Spent an entire day trying to chase down problems on my phone instead of just biting the bullet and wiping. It did feel good at the end when I finally had my backup restore working. For some reason the eMMC had become corrupted on my phone and I had to wipe the system and data partitions and actually reformat them...

I think your experience warrants updating the OP with a warning and suggestion to wipe cache if one encounters the situation you were in, though it's not clear if that would help yet. Someone else would have to repro this and try the suggestion.

Did you flash the full firmware update w/modem or w/o modem?
[T-Mobile, Samsung Galaxy SIII] thatsaabguy:
Err, whatever the main link off the first post gave me. I saw that you'd created a non-radio version, but I just clicked on the biggest link and ran with whatever it sent me, because I'm lazy like that :)

Now I'm trying to recall how to root this bloody thing, because doing this lost me root, PLUS a hard wipe, so I'm back to remembering how I did all this almost a year ago...sigh...
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Flashing over with Odin will do that. What you want is to use Odin or heimdall to flash ClockworkMod Recovery in Download mode. Once you have that, you can flash any rooted ROM you want again.

I just had to root one of these the other day and since I use heimdall, it turned out to be a pain in the ass. Heimdall 1.4rc1 (current release) has a bug where it fails to upload the recovery and earlier Heimdall 1.3.1 doesn't seem to work at all. I found a thread about this heimdall bug and compiled the latest heimdall from GitHub and that version worked.
[T-Mobile, Samsung Galaxy SIII] j_smith305:
Thanks for this. Worked flawlessly! :good:
[T-Mobile, Samsung Galaxy SIII] postrero:
Giving it a try

Since its crazy how I get no reception in the bank, I'm gonna give this a try and see if switching to uvdmd5 actually gives me better reception. Did the flash with Odin and lost recovery but went to goo manager and all was good. Will post results after messing with it for a few days. :o
[T-Mobile, Samsung Galaxy SIII] PainfulLover:
Have you tried stepping out of the vault? Lmao
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
Agreed. Maybe the no reception in the bank is interference or a jammer set up by the bank to prevent collaboration for robberies or something.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Most likely just the material it is made out of.
[T-Mobile, Samsung Galaxy SIII] postrero:
Logic

My logic is in line with you guys but when the att and verizon people are texting away with full bar reception, I have deduced that its my tmobile carrier. :)
[T-Mobile, Samsung Galaxy SIII] Dano79:
Just the way it goes its who owns more of the airwaves in your locale
[T-Mobile, Samsung Galaxy SIII] VolcanicSkunk:
Thanks so much for this zip!!! I recently flashed AOSPWIZ v4 (UVDMD5) on my T999 S3, and was getting abhorrent battery life. Changing kernels didn't change the battery life I was getting.

I used the 'getprop ro.bootloader' and found that I was still on UVALH2 bootloader. I flashed this yesterday, and today my battery is giving me the kind of life I've come to expect with this phone.

Thanks again!!!
[T-Mobile, Samsung Galaxy SIII] LoopDoGG79:
Um, bootloaders have nothing to do work battery life. :what: The radio it flashes has minimal effect. Most likely restarting your phone is what helped.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If he still had LH2 bootloader, then its highly likely everything else was also from build LH2.

The rest may or may not have any impact on battery, but we know so little about some of it that it wouldnt surprise me.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
To settle this once and for all... I wasn't sure about better battery life with new bootloader either, but please see the updated OP with details of what is flashed.

One of the files flashed is rpm.bin which stands for Resource and Power Management.

So, it is possible that this improves battery life. I've been thinking I've had better battery life lately and wasn't sure if it was due to some recent CM kernel improvements or some other tweaks I had done recently to my system. Prior to upgrading from the original bootloader / firmware (was already running UVDMD5 radio ), I was using LeanKernel on top of CM10.1 nightlies to make battery life more reasonable.

So, while bootloaders are unlikely to have effect on battery life, this is a more holistic "firmware update" and does update the firmware for the Resources & Power Management hardware.
[T-Mobile, Samsung Galaxy SIII] VolcanicSkunk:
Considering the only thing that I changed is that I flashed the new bootloader and firmware and somehow I am getting several more hours of battery life and Android System is no longer the top consumer of my battery (as it should be), I'd say that the new firmware has a pretty good possibility of being the reason why. I doubt that a simple reboot would have that kind of effect (especially when it hadn't in the past). Not to mention that the battery troubles only started on UVDMD5; when I ran Frosty Jellybean I got phenomenal battery life.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Hm, yeah, now that you mention it, my phone seemed to drain more battery once I went with UVDMD5 radio. But this problem went away once I did the full firmware upgrade and got better than it was before. I had really good results with the UVDMD5 radio too, improving downlink and uplink by a megabit or two.

Also interesting point of note: 6/01 CM10.1 nightly has something about swtching d2 RIL over to MDx. It sounds like they're going with supporting the latest firmware best. I'm very happy witth the 6/01 nightly so far. I flashed it just an hour after it dropped last night.
[T-Mobile, Samsung Galaxy SIII] bosna110:
going through and reading every page, I have T999UVLI5 as baseband, Is this something I should be precautious about or dont even flash at all? I dont want to have something I can't fix once f'd up. Thanks for any or all the support given. Also i am running on CM June 2nd build nightly.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Flash it. Full speed ahead!
[T-Mobile, Samsung Galaxy SIII] SomebodyEpic:
?

so if i dont flash this i will not be able to flash cm 10.1 what about aokp or liquidsmooth do i need to upgrade bootloader for these roms to work properly ?
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Flash away. I had an older baseband than yours when I started.

This is agnostic of whatever baseband you already have on there and is a safe operation since you're doing it on a T999 device.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Cyanogen made a decision a while back to not support earlier bootloaders in CM10.1 due to people experiencing lots of crashes / random reboots. So, at some point either back in April or May (I can't remember at the moment), the nightlies started asserting the bootloader versions.

I don't know about AOKP or LiquidSmooth. If LiquidSmooth is a CM fork, you'll probably have to do the same thing, unless they removed the bootloader assertion from the installer (yup, it's only in the installer that the check is done.)

I highly recommend upgrading to the latest firmware anyway -- if you want to keep your radio, just get the radio-less update. It's generally accepted now that the UVDMD5 firmware update is overall beneficial as it has improvements to the Resource and Power Management firmware and such.
[T-Mobile, Samsung Galaxy SIII] unciviilized:
I get an error when trying to download the new bootloader zip:confused:
[T-Mobile, Samsung Galaxy SIII] mnasledov:
What are you downloading it with? It's just a Dropbox link -- works for me, just tested both the links I put up. I hope you didn't copy-paste the text of the link than the link itself as XDA shortened it

Oh, looks like you were trying to get the first link which I linked to for the LJC firmware to credit the original guy. Looks like he took it down. Editing OP.
[T-Mobile, Samsung Galaxy SIII] SpinTX:
Installed this recently and flashed a few roms, just LS and CM RC. I was able to the send MMS initially; then one time, 20 minutes after I successfully sent one, I get the error "Service not available on network". So get this, I clean install the same LS rom, then magically it works! But no, after 2 MMS or so the error came back. I figured it was the app or the rom and switched to CM and tried Handcent. No dice. So naturally, I am wondering if anyone is experiencing this problem and if they know of a solution. I find it very strange that it worked initially. You'd think it would either work or not work. I am going to troubleshoot some more. Thanks
[T-Mobile, Samsung Galaxy SIII] mnasledov:
Do you know what was your baseband (modem firmware) before? You can always run that if UVDMD5 modem doesn't work well for you. I've seen people report mixed results based on location as far as modem firmware.

That's really strange, though. I actually had the positive effect of this modem / firmware update finally being able to set my phone settings such as forwarding numbers which didn't work from the start for me.

You can try flashing other modems and see if it makes a difference. I've also retained a copy of the UVDLJC firmware update script I originally found + modified to make the UVDMD5 firmware update script.

If changing modems doesn't work you can always see what downgrading to LJC firmware does, if it fixes the problem:

https://dl.dropboxusercontent.com/u/173554095/T999 Devel/T999UVDLJC_firmware.zip
[T-Mobile, Samsung Galaxy SIII] SpinTX:
I was on the modem/firmware you linked me to, before I updated. Will downgrade and report back. Thanks

---------- Post added at 04:48 PM ---------- Previous post was at 04:24 PM ----------

The "JC" modem did not work. Same error message.
[T-Mobile, Samsung Galaxy SIII] mnasledov:
I went ahead and did a bit of leg-work for you and found this thread: http://androidforums.com/official-u...0m-baked-rom-blackbean-8-3-16-official-4.html

To quote, " to fix my MMS issue, i installed GO SMS, sent a picture and it worked. I then used the stock messaging app and sent a picture, voila, it worked. I then deleted GO SMS and now everything is functioning properly. "

I haven't been able to find an explanation for this issue but it's affected a small number of people over a variety of phones for yet to be determined reasons.

So you have a bunch of options. You can try that and see if it fixes it and keep LJC firmware+modem. Or you can try it, upgrade to MD5, and if you have problems again, try that solution. At this point it's really up to whether you want MD5 or LJC radio.

It would be interesting to know if you can fix it that way, then upgrade back to MD5 and see if that upgrade process breaks it again.

Did you flash the update with radio or without? Both are safe but would like to know for future reference. Thanks.
[T-Mobile, Samsung Galaxy SIII] TheKucho:
So, just to get this straightened out, if i was on Android 4.1.1 with Baseband T999UVDLJA; what would flashing this do for the device?

Does flashing this update my Android version? If so, to what version? Thanks!
[T-Mobile, Samsung Galaxy SIII] mnasledov:
(1) Depending on where you are, you may get better signal as a result of the modem part of the update.

(2) As a result of the Resources and Power Management firmware update, you might get an improvement in battery life, though we don't have any numbers on how much improvement there is.

LJA is fine for flashing CM10.1 nightlies so you don't need to update firmware to use those.

Otherwise, there might not be anything you'd get out of it. But, hey, you can always downgrade your firmware and/or modem if something about it doesn't work out for you. It's not like it's got some mechanism that prevents dd from overwriting your firmware with an older rev ;)
[T-Mobile, Samsung Galaxy SIII] SpinTX:
Installed GO SMS, successfully sent a MMS, then uninstalled it, and finally through the native text app, successfully sent another MMS. I had read that quote you showed me earlier and tried Handcent instead, assuming I just needed a 3rd party text app. My bad! And to answer your question I installed the update with the firmware together. I am more than willing to try to break it again though. Should I try updating just the modem to see what happens? Thanks again!
[T-Mobile, Samsung Galaxy SIII] TheKucho:
Thanks! Just one more quick question, does flashing this upgrade me to Android 4.1.2?
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Yes. MD5 is Android 4.1.2!
[T-Mobile, Samsung Galaxy SIII] LoopDoGG79:
No, I'll upgrade your bootloader and modem, not your ROM. You will not get multi window or all the other goodies that come with 4.1.2. For that, you will need to flash, Kies or Odin update to 4.1.2.