yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Basically, your phone has to be on a more recent firmware version to work well with CyanogenMod. If you are having reboots, Odin the latest firmware and then restore your CM 10.1 and you will be all set. CyanogenMod now has a check for compatible firmware versions before installing for the d2's.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
So is there somewhere that we can know what the latest firmware is? When is the last time that the firmware was updated? Does the CM team assume that everyone who has been flashing CM for a while will have to restore to TW before going back to newer CMs?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
I agree that they should be more forthcoming about this firmware mess. Someone should edit the OP to include the firmware updating algorithm. Please!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I apparently don't have the latest firmware as I can't flash the latest nightly but my phone has been working GREAT with CM for a long time now. Never had ANY of the random reboots that people have reported. It's been very stable as far as I can remember back.

So I wouldn't agree with your statement that you have to be on a more recent firmware version for your phone to work well with CM. My phone is a perfect example of that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vcharette:
EDIT - The rom flashed just fine after removing the line mentionned below. Everything is running great. I have an I747M (Bell) running Baseband I747MVLDLK4

You can fix that error by removing the problematic check line in a file inside the rom zip file. You do not need to update your firmware. The updater script checks the baseband version of the I747 ATT in order to install. If you don't have that it fails. If you have an I747M (canadian version) you will NEVER be able to match the required baseband, no matter how many times you update.

1) open the zip

2) edit the file cm-10.1-20130514-NIGHTLY-d2att.zip\META-INF\com\google\android\updater-script

3) remove this line "assert(getprop("ro.bootloader") == "I747UCDLK3");"

4) try flashing the rom again and it should go through without any issues

Make sure you don't delete ANYTHING after the ; and you can also remove the reste that preceeds it. Just more checks to make sure you have a d2att device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mustangtyson:
System Settings->About Phone->Baseband Version

I747UCDLK3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
This is the version of modem not the bootloader. They are different (as far as I know).

Also, is there really no other way to update the bootloader besides flashing back to TW?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vcharette:
I just edited the file to remove the check. I will report back if it flashed OK or not.

Sucess. Installed 5/14 just fine on the I747M. I highly doubt it's about having the

latest firmware

. It just checks that you have the ATT version. The person that made the modification probably just didn't take into account that more checks had to be added. In other words, no matter how hard you try you cannot have the baseband version listed in the prop file when using a I747M.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
So...

1. Make a nandroid now

2. Odin to latest AT&T firmware

3. Install Cyanogenmod as per regular instructions

4. Restore nandroid.

Will that work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vcharette:
It's preventing you from installing because there's a line that checks for a particular baseband version (the I747 baseband for ATT).

For I747M owners like me, the simple fix is the remove the check from the updater-script file.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
Okay, I got confused by people saying "it's not the modem firmware, it's the bootloader".

Turns out it's the modem firmware: https://github.com/CyanogenMod/andr...mmit/efad9265de605ecb3b1578f8002e5dc36e1f0db9

require version-bootloader=I747UCDLK3

However... I have the exact baseband listed and yet I still can't install through TWRP. What gives?

http://i.imgur.com/RJ7Ulk0.png

I am interested in being able to use CyanDelta without mucking around with workarounds, editing installer scripts.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vcharette:
Interesting find. However it leaves the Canadian carriers in the dark. We cannot achieve that version. I guess another edit will come later to add the Canadian firmwares...

SGH-I747M	Canada (Bell)	2012 November	I747MVLDLK4

SGH-I747	USA (AT&T)	2012 November	I747UCDLK3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
I tried submitting the GPS issue discussed a few posts ago, but I had since updated to a nightly and they closed my JIRA submission for having a logcat on a nightly. Does anyone have the issue on RC2 that they could get a logcat for and submit so we can get this fixed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
The script is not checking the baseband, it's checking the bootloader. You can have the LK3 baseband with any number of bootloaders. Only way at this point to get LK3 bootloaders is to flash back to AT&T stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
So how do we find out what our bootloader is?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
That's going to be annoying as hell to fiddle with that every time I update my nightly on my d2can flashed to d2att. T_T
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vcharette:
so anything wrong with bypassing the bootloader check ? I bypassed it on my I747M and it installed fine. Been running on it for an hour or two and haven't experienced any glitches.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
Probably not, at least not now. If the devs impelment anything that requires newer firmware then maybe. Only thing now is that you'll need to remove that line from the update-script every flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Possibly that your phone would be unstable because of outdated tz as discussed earlier. But that wouldn't change from yesterday's rom, or the day before and so forth. This has been going for a while.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
Shouldn't there be a way to update the "tz/rpm firmware" without having to odin back to stock and letting it do the OTA updates from there?

Flashing back to stock, even the newest stock, doesn't mean that you have to newest bootloader. Assuming that the tz/rpm firmware is stored in the bootloader, all you should have to do is flash the bootloader in Odin.

Unless I'm mistaken, the bootloader is a seperate Odin flashable file than what I am finding in stock images posted in various threads on these forums. What I'm finding is only the PDA portion is included in those downloads. Not the bootloader, modem (Phone), or CSC portions. Now I know that the CSC portion isn't really used since that stuff is baked right into the PDA flashable file, so I could be mistaken and perhaps all we need is the PDA portion and it will flash the modem, bootloader, and recovery, as well as the /system and /cache partitions.

I'll grabbing another "stock firmware" to check to see what it has in it for actual flashables now. The two I tried so far both gave me errors in 7zip when I attempted to open the tar.md5 file, so its possible that they appear to be missing things because the files were not downloaded successfully.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
If you stumble on any of the bootloaders for any Galaxy S3 (d2vzw, d2att, d2can, d2spr, d2mtr, d2tmo, d2usc, d...id i forget anything??) it would be sweet if you could link them too. Since I believe there's not only d2att users in here. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] minnick:
http://xdaforums.com/showthread.php?t=1968625

Stock ROM Firmware Download Links HERE

Will these links work for the latest stock firmware? Apologies if I'm confused and pointing to the wrong thing.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
FYI: There is a silver lining to flashing back to stock besides getting an updated bootloader, which is that we need to be on the latest jellybean touchwiz in order for the carrier unlock "hack" to work. I've been putting it off, because I hate booting back into Windows just for ODIN (maybe heimdall works now?), but now I have two reasons: 1) the updated firmware assert might stop random reboots; 2) unlocked phones have higher resale values.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
^ That is where I tried to get the latest AT&T firmware - twice. Both time 7Zip gave me the following warning:

"There is no correct record at the end of this archive".

What I can see inside that tar.md5 file is files for the following:

system partition

cache partition

a file called NON-HLOS.bin

a file called sbl2.mdn

That's it. I believe my download did not finish properly though. I'm trying the AT&T "mirror" from that forum post this time. That file is 97% compete. I will let you know how it goes once complete.

edit:

Same error with the mirror file, however the actual downloaded file was the correct size this time, and this tar.md5 contains:

aboot.mbn

boot.img

cache.img

recovery.img

rpm.mbn

sbl2.mbn

sbl3.mdn

system.img

tz.mbn

So it looks like I have everything. I'm going to flash it via Odin now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vcharette:
http://samsung-updates.com/device/?id=SGH-I747M

http://samsung-updates.com/device/?id=SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] minnick:
Ty sir, I look forward to your response...

Thx I'm going to bookmark that page and pull the file. Not sure the difference between that link (samsung-updates) and the one I posted but saving in case the files on the XDA link are incomplete as DeathKoil mentioned.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vcharette:
I prefer samsung-updates over sammobile and the xda link.

XDA thread could be outdated and SamMobile requires registration to download.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
So is the boot loader issue only effecting Canadian phones or ATT as well?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
ATT as well (need the good bootloader to install latest CM10.1 nightly), but the biggest issue I believe is that d2att and d2can don't NECESSARILY share similar bootloaders. No stock roms from Canadian providers have the needed bootloader, but I believe you can take a d2att one and flash it on your d2can.

Now some people are trying to get hold of the needed d2att bootloader from stock roms so people just have to download the bootloader and flash with ODIN.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
Still flashing... its taking an eternity. It has finished flashing aboot.mbn (file size ~.8MB) and boot.img (file size ~5.4MB), but that took a solid 20 minutes. It has just moved on to Cache.img which is about 28MB. Then it needs to do system.img, which is about gigabyte. This could literally take all night.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I thought you would only flash the necessary parts? You're flashing the whole ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
I figured it would be the safest way. I also figured that it would only take 30-60 minutes. Now it looks like it is going to take all night, and I'm a bit afraid to stop it mid transfer and remove the cache, system, and recovery images then flash again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Let it's do its thing. ODIN's a tad slow when flashing the full rom, like 15 minutes when I flashed to a stock rooted ROM when I first got my S3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Febby:
That's interesting that its taking you guys to flash the smaller partitions so long. I've flashed many odin stock ROMS previously via team sextape testing and it never took that long given that the system partition was surely smaller but everything else similar in size. I was done normally in 10 mins or less

It should not take all night for sure. Don't unplug it either. Although nothing bad should happen if you do during the system process as long as you don't yank it during boot loader Odin process I would assume
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
Are you saying you've done a full flash in 15 minutes total? I'm at 45 minutes so far, and I'm not done flashing cache.img yet - so I've flashed less than 50MB of the other 1GB archive so far.

This is making me think I should pull the plug and try again using a different cable.

What's the risk in closing ODIN on the PC, and rebooting to download mode?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Full rom is about 15 minutes for all partitions, if it takes more there might be something awry with DeathKoil's USB port/cable/phone/computer etc etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
Confirmed that flashing LK3 firmware (from the no flash count trip thread - includes bootloaders) will allow a 5/14 flash. On AT&T, don't know what to tell you 747M guys :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Febby:
Im very aware of that. 15 mins sounds about right. Was just taking a wild 10 min guess since I haven't yet flashed a stock ROM for this device but have previous for the sgs2. I think either his USB is bad, drivers aren't install properly, or PC is having transfer issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Probably wouldn't be much harder to fix really, got the d2att TWRP running on my d2can since the day I got it.

Just need someone crazy enough to go and flash the bootloader ONLY on a d2can OR if coward enough edit roms manually everytime they update. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheCynick:
I'm on baseband version LK3 and I flashed 5/14 earlier and had two reboots in the space of an hour, so I reverted back to my Nandroid of the 4/13 nightly.

It then proceeded to reboot like crazy until I wiped cache and Dalvik, after which it has calmed down.

I have had a reasonable run with 3/14 - I went two full days without a reboot last week. But then I do turn my phone off at night while it recharges.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
If I remember 3/17 (or was it 3/21?? :S) was the latest version with a 3.0 kernel. I had good luck with it personally, but decided to move on to most recent builds after 3.4 kernels got a little better. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
<sigh> Dell puts USB 1.1 on the front of their Optiplex 980 series PCs apparently...

I pulled the plug, plugged into the back, and re-started the Odin without rebooting the phone (just in case). The entire copy took under 15 minutes.

I then flashed CWM Touch 6.0.3.0, and was able to install the 5/14 nightly without issue. So for AT&T users, the file here works just fine:

http://www.hotfile.com/dl/182319352/b8d55a6/I747UCDLK3_I747ATTDLK3_ATT.zip.html

For our Canadian friends, I have no idea if the boot loader for the AT&T model will work on your phones. I feel like it would be smarter to have the code to check the bootloader allow the installation on everything "but" a certain few older bootloaders. Otherwise they really need to have a list of usable bootloaders that would need to be updated each time new firmware came out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
So does anyone know an easy way to find out what version my current bootloader is? None of the dialer codes that I could find work because I'm not on a TW Rom and if I'm going back to a TW Rom to find out, I might as well just reflash the latest stock firmware.

I'm up here in Canada on the Rogers network with an M variant phone so I'm SOL without editing the scripts but I'd like to see what I have in case they change the code to also allow phones with the latest 'M' bootloaders (LK4 for Rogers) to be acceptable. I'd like to be ready and I'm just curious as it can't hurt to have the latest and greatest but if I'm already there, I can save myself the hassel.

Thanks in advance!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Ah the dreaded and painfully slow USB rev1.1. :p

I might go crazy and brick my phone later tonight. We'll see...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Psychosi42:
I just used this command to find mine ...

adb bugreport | find "bootloader"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Command line: console = null androidboot.hardware=qcom user_debug=31 zcache sec_

log=0x80000@0x88d00008 sec_dbg=0x40000@0x88d90004 sec_debug.reset_reason=0x1a2b3

c00 etb_buf=0x4000@0x8fffb9c0 androidboot.debug_level=0x4f4c sec_debug.enable=0

sec_debug.enable_user=0 androidboot.cp_debug_level=0x55FF sec_debug.enable_cp_de

bug=0 cordon=ef13c2344881da869492d88b29a1f30a sysscope=0xee000000 loglevel=4 sam

sung.hardware=SGH-I747M androidboot.emmc_checksum=3 androidboot.bootloader=I747M

VLDLK4 androidboot.nvdata_backup=0 androidboot.boot_recovery=0 androidboot.batt_

check_recovery=0 level=0x574f4c44 sec_pvs=0 androidboot.emmc=true androidboot.se

rialno=a902a9d8 androidboot.baseband=msm

Got it! Thanks buddy. Looks like I'm running the latest and greatest from Rogers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] marinierb:
I bet you anything that this assert in the install script was slipped in by accident and that it will be removed soon. Some folks are going through a lot of trouble for nothing. IMHO.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Go hard or go home. I...need...latest...nightly... :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] statickiwi:
This seems like a change that was not necessary
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Can't be by accident, there is a code review process. More than one person has to want it there.

---------- Post added at 04:45 PM ---------- Previous post was at 04:43 PM ----------

Yea.....link to that please?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Looks like Cyanogen himself wrote, reviewed and inserted into the code.

http://review.cyanogenmod.org/#/c/37696/

EDIT: Point being, it was meant to be there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Which just means he has reviewed it, not that it's indubitably right.

He's likely not aware that d2can users flash d2att roms since they're identical minus radio. No real use branching d2att to d2can only for the radio that is never included in CM.

The check itself is a good thing though, it forces you to have an up-to-date system.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Case in point
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Psychosi42:
Using adb bugreport | find "bootloader" I found my bootloader version to be I747UCLEM

I upgraded my bootloader by doing the following:

1. Nandroid Backup

2. I then flashed the I747UCDLK3 (JB 4.1.1) from http://xdaforums.com/showthread.php?t=1739426 via Odin.

3. Then I flashed TWRP from http://www.teamw.in/project/twrp2/104 with Odin as well.

4. Booted into recovery and restored my nandroid. Not sure If I needed to but I unchecked boot from the restore.

5. Finally I reflashed my ktoonsez kernel since the stock restore overwrote it.

Checking my bootloader version now shows I747UCDLK3

I'm assuming I can now flash the nightlies without issue, however I'm on RC2 for the time being. YMMV
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
http://xdaforums.com/showthread.php?t=1739426
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Febby:
You may also check your boot loader version by downloading and installed root checker by free android tools from the play store or use the link below as an alternative option to adb command.

https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker

Here is a screen shot showing the boatloader version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
adb shell getprop ro.bootloader is a little more concise. I had the old bootloader, with the new modem, and now both are up to date.

$ adb shell getprop |grep DLK
[gsm.version.baseband]: [I747UCDLK3]
[ril.sw_ver]: [I747UCDLK3]
[ro.boot.bootloader]: [I747UCDLK3]
[ro.bootloader]: [I747UCDLK3]

I did pretty much the same thing, but was a little more careful. FWIW:

1. Nandroid backup of yesterday's nightly to external SD in TWRP, then booted to windoze (I live in linux)

2. Updated Samsung windoze usb drivers to 1.5 from 1.4 (last summer).

3. Booted phone in download mode from TWRP and ODIN'd the pre-rooted stock jellybean touchpiz (root66_ATT_I747UCDLK3) from mrRobinson's no-trip flashcounter thread

4. OOPS... Stuck on SAMSUNG logo because I forgot to wipe data&cache in TWRP first. So, I 3-buttoned into stock recovery and wiped it there and then it booted up. Yay.

5. Took this opportunity to Carrier Unlock my phone from ATT for the 10 minutes my phone was running nasty Touchwhiz again (forgot how laggy Touchwhiz is). Now I can sell my phone unlocked in a couple months.

6. Installed the GooManager app and then used it to flash TWRP recovery (instead of doing it in ODIN, which trips the flash counter)

7. Nandroid backup of Touchwiz, just in case (1.2GB iirc).

8. Nandroid restore of last nightly & wiped caches

9. Booted up fine

10. Booted back to recovery and was successfully able to flash the 0514 nightly since the bootloader now matches the assert
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jiangyi:
Since the lack of Canadian bootloaders in the assert was probably an oversight, I just submitted patches to add them into the assert:

d2att: http://review.cyanogenmod.org/#/c/37792/

d2tmo: http://review.cyanogenmod.org/#/c/37791/

Let's see what happens.

(I don't own a d2 device myself, just helping out some friends who do own them)

EDIT: Merged, things should be back to normal for Canadian users starting tomorrow. :) (Unless you have an outdated bootloader, in that case, please update to I747MVLDLK4)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
Why don't you just find another zip and flash that when you flash this...

Sent from my GALAXYSIII running Jelly Bean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elementaldragon:
And it sucks when i bought the phone on Friday for the $200 + tax and whatever.... and today i was at WalMart and saw it for $150. :-/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Eliteranger12:
Do I need to do a full restore from built 7/19 if I don't how do I flash the ROM keeping everything I have on my phone now?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Latty:
Ah, I figured out what the issue was. The problem was with the inverted gapps I was using. I wiped, reflashed CM10, and flashed the official 07/26 gapps, and the 'network types' menu is still intact. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drawde40599:
mms

To any1 that wants sms to act like it has been in previous cm10 builds .. replace SMS .apk with this one http://db.tt/1awjdZFs, in system apps , reboot clear data , and SMS messages will work as they have been ( anything over 160 converts to multimedia message not multiple texts . Don't forget change permissions . Works great .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] magistrateee:
Is there CWM flashable default kernel for CM10 available somewhere (link)?

I flashed a different kernel (KT747) and i believe its giving me problems.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
No there isn't.... Did you flash the KT JB version? If you want the default CM10 kernal back, you'll have to reflash the whole ROM...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tiffany84:
Here is the Circle Battery Mod with the ICS blue colored icons for when you toggle something on in the notification pull down. It's the same thing I released last time but now based of the 7-25 build. Just download the .zip, reboot to recovery, wipe cache/dalvik and flash.

Circle Battery Mod for 7/25 Build:

http://d-h.st/UBq