Welcome to CyanogenMod
|Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
How To Update Bootloader, And Do I Need To Do This?
Posted 15 May 2013 - 07:17 PM
When the cm-10.1-20130514-NIGHTLY-d2att.zip nightly was released, I tried to update to it, but the update failed with an assertion about the bootloader. I dismissed this as possibly just a bad nightly build, but when the same thing happened with the next nightly build, I began to suspect that it may be something else.
I looked at the changelog for the first nightly build which failed, and I found what I believe is the culprit:
It looks like the bootloader assertion was added in that nightly build, and it is designed to make sure that the phone has a recent bootloader level on it. My phone reports its baseband version as I747UCLH9, which my research indicates is not the latest level.
So my assumption is that I need to update my bootloader to a more recent level. However, I'm not sure how to do this. I've Google, searched through these forums, and looked through the wiki, but to no avail. I apologize if this is a total noob question. I try not to ask something unless I've had no luck figuring something out on my own. Any help would be very much appreciated. Thanks!
Oh, and in case it's relevant, I've got what I believe to be the latest version (220.127.116.11) of Clockwork Recovery Mod installed on the phone.
Posted 15 May 2013 - 07:20 PM
Posted 18 May 2013 - 06:30 AM
adb shell getprop|grep UCDLK3 [gsm.version.baseband]: [I747UCDLK3]
The bootloader remains at the older version, though:
adb shell getprop|grep bootloader [ro.boot.bootloader]: [I747UCALG1] [ro.bootloader]: [I747UCALG1]
I'm quite out of my depth at this point; I don't know which of the 28 partitions on my phone need to be changed or if there's some other method to change the bootloader. Any help is appreciated!
Posted 18 May 2013 - 07:24 AM
In short, I extracted a PIT file for my phone, downloaded a stock I747 UCDLK3 firmware, extracted the various partition images, and then ran several Heimdall commands in sequence, restarting download mode each time. The PIT file was extracted by Heimdall while in downoad mode. The firmware is just a ZIP with a TAR archive inside; the interesting bits are in the TAR archive. To get the phone back into download mode without showing the charging screen, I found I had to press and hold volume down, home, and then power, waiting for the screen to blank. Once the screen blanked, I had to count out five seconds and then release the power button while maintaining my grip on the other two buttons. Once the warning screen appeared, I then let go of the other two buttons and pressed volume up to enter download mode.
The sequence of Heimdall commands I ran was:
heimdall flash --no-reboot --pit ../2013-05-17.pit --ABOOT aboot.mbn heimdall flash --no-reboot --pit ../2013-05-17.pit --RPM rpm.mbn heimdall flash --no-reboot --pit ../2013-05-17.pit --SBL2 sbl2.mbn heimdall flash --no-reboot --pit ../2013-05-17.pit --SBL3 sbl3.mbn heimdall flash --no-reboot --pit ../2013-05-17.pit --TZ tz.mbn heimdall flash --no-reboot --pit ../2013-05-17.pit --MODEM NON-HLOS.bin
After restarting a final time, I was able to flash the latest CM 10.1 nightly.
Posted 21 May 2013 - 06:03 AM
In short, is there a clear method for upgrading a bootloader for the US T-Mobile SGH-T999 Galaxy S3 to allow for CM-10.1 installs?
Posted 21 May 2013 - 02:12 PM
You can flash this using Odin as PDA file. I tried it and successfully updated to new baseband and bootloader.
That's an attractive, low fuss, option for AT&T GS3.
For my T-Mobile GS3, unless I find a similar bootloader package, the other option appears to be nandroid backup, flash the latest stock Jelly Beam ROM, re-install CWM, and restore nandroid backup.
Posted 12 June 2013 - 05:12 PM
And it shouldn't erase anything, but backups are always a good idea, just in case.
Posted 13 June 2013 - 01:04 PM
Thanks for the new link.
Posted 14 June 2013 - 06:02 PM