yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You have no clue of the changes then. And that's perfectly fine. I might suggest that you do a little research on all of the changes though. But that's not the point of these nightlies that are being released. One of the major purposes of the nightlies are for users to try them out, find the remaining bugs, and then report them to get them fixed and move on to the next. So I'm quite unsure why you would be posting this in a nightly thread. If its a hassle for you, then stay where you're at on whatever release you choose. Its pretty simple. Nightlies are definitely not the type of releases for everyone. If your not running the nightlies, then it looks at though you have nothing to do with this thread as you are not attempting to contribute to the development of this ROM like the majority of users that are using the nightlies. The whole point is to progress these releases and to make this ROM better. Staying on "3/17" doesn't accomplish anything. That's just staying stagnant on one particular release that works for you. That's definitely not what the purpose of this thread/ROM is about.

Try not to take any of this in the wrong way as that's not how I'm intending it. But this is a nightly thread. Nightlies are incremental builds that may or may not have new/existing bugs. Its all for the better development of this ROM. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VeryCoolAlan:
Haven't been on CM since last year.

Does this still have any major bugs

?

Click here ! really helps me out!

http://highonandroid.com/contest/?id=50
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Nandroid and try for urself. This is a nightly thread what do u expect from nightlies?

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
I have been quite annoyed by this as well. The included ringtones repeat but custom ones do not. This probably isn't a huge issue for most people but it caused me to miss a few calls before I figured out what was wrong. Does anyone know which nightly they stopped working on? I would like to track down that commit.

Sent from my Galaxy S3 [AT&T][CM10.1]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
I remember reading about adding the "loop" flag to the audio file using Audacity a long while back. I think the files had to be OGG for this to work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
This is correct. I brought it up a whole ago. Create ogg files and set android loops in them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] araemo:
So, what I ended up doing is using ODIN, and then my phone hung at the samsung logo (Because I didn't do a data/factory wipe). I rebooted into 3e recovery and connected adb.. did adb push of my recovery.img, and used dd to overwrite recovery from within recovery. Waited a minute or so to make sure nand writes had finished, pulled battery, booted to recovery and got CWM. Restored my nandroid.

No need to restore all my /sdcard data manually.

I did see that ODIN reported flashing both RPM and TZ, and I also for my sanity pulled the partitions before and after and compared, and they did update.

So, I'm on 5/15 and we'll see if it is really stable. :) (The firmware difference does explain why some users had repeated problems while others didn't though, so it's nice to see a resolution)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Penguyen:
I know that my S3 is a Canadian model but does it matter which Canadian stock ROM I flash onto my phone in order to update my bootloader?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] patthe:
Same for me in canada try to update nightly and say something about the boot loader.

What need to be done?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
I get it and I appreciate your reply. :) I posted because most of the comments here are complaints, not bug reports, just as you and many others have noted in the past (and in your own thread). It may have started out as one (I'm dubious of this assertion), but this really isn't a development thread at all anymore. Heck, even one of your collaborators (IIRC), justin860 of inverted apps fame, has made several comments nearly exactly like mine (about going back to 3/17) in the last couple of months of this thread, and nobody bothered him about it. ;)

The point was that, if people are having lots of issues (and surely they are), 3-17's something that just works. There haven't been huge feature set improvements that I can see in the changelog since 3-17. Yes, there have been tons of committed changes, but I'm just not seeing big, additional features. If what most of the users here are looking for is a daily driver, and I'd wager they are since there are almost no bug reports with logs in this thread, then don't repeatedly beat your heads against the wall when you don't have to. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Wanted to return to stock yesterday to carrier unlock my phone, so I made a nandroid, restored stock rom, went back to restore my nandroid made minutes ago... failed. Thanks TWRP 2.5! My data was not restorable yet the archive wan't corrupt (backup went just fine).

Let that be a lesson, heh!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
You may have to flash a CM10.1 zip over touchwiz before you can restore a 10.1 backup. I recall having to do that in the past on my capitvate. Something about partitioning tables.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No, the data TAR from TWRP was not getting restored properly because it stopped on a 0 byte file in it (and that exploded everything)

TWRP issue really, just suck. :[
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
I'm finding myself lost with the bootloader issue, I'm running the 10.1 M2 build and it appears i'll need to look at updating my bootloader to be able to flash the upcoming stable (according to CM on G+) .

Question: Can you flash the latest version from the modem thread? http://xdaforums.com/showthread.php?t=1831898

if not, is there a guide somewhere about how to update everything then get back to CM?

Thanks, Russell
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
No, the modem and the bootloader are different. They have the same version number because they align with builds from Samsung (someone correct me on this if I'm wrong). The correct process is going to be to do A FULL BACKUP WITH CWM OR TWRP, restore to a rooted stock image with the correct bootloader, then restore the backup you made earlier. You need bootloader versioned I747UCDLK3, the modem version is your choice, but I'm using the modem versioned I747UCDLK3 and I'm generally happy with it.

Do a backup as you would normally.

Did you make a backup?

Does the backup restore properly?

Follow the instructions in this thread to update to the latest Samsung ROM (with the correct bootloader): http://xdaforums.com/showthread.php?t=1739426

I found that I had to wipe data in order to get the Samsung ROM to boot at all.

I assumed my recovery was overwritten when I ODINed over the Samsung ROM, so I reflashed it with heimdall. See the CM wiki if you need help with that: http://wiki.cyanogenmod.org/w/Install_CM_for_d2att

Wipe system, data, and cache.

Restore your NANDroid.

Reboot.

Check that you have an updated bootloader using this app (check under Build Info): https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker

Update to the latest nightly as you normally would.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Bootloaders and modems are very different but usually share the same build number as they were part of the same software release package. Modems can be flashed easily and freely to help improve your phones radio related operations. The bootloader on the other hand is much more difficult to flash or tamper with and if done incorrectly can brick your phone which is why going back to the latest stock firmware is required to update.

If you read back a couple of pages you will find lots of discussion on this matter including links to stock firmware and the steps they have taken to complete the task of updating the bootloader.

To save you a little trouble, here is the link to the latest stock firmware. http://xdaforums.com/showthread.php?t=1739426 Make sure you use the "current" one and the right one for your phone.

---------- Post added at 10:39 AM ---------- Previous post was at 10:36 AM ----------

As some people have been reporting borked backups, it might be a good idea to try and restore from your nadroid backup right after you make it just to make sure it's good before proceeding with the stock F/W load. If its not, make another.

Furthermore, some are reporting needing to flash a CM10.1 ROM before being able to restore your nandroid. Restoring to a CM10.1 directly from a TW flashed phone might not work.

Lastly, it might be a good idea to store your backup on an external SD card or transfer it off to your computer or the cloud just to make sure it doesn't get deleted during the upgrade process.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I edited my post to suggest testing the backup as well as wiping system, data, and cache at various points to ensure stability.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
excellent, thank you this is what i was looking for and kept missing and thanks for the additional tips to keep from screwing myself with backups :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Honestly I don't want to be a party pooper, but indeed test your backup right after doing it if you can afford to. It's a PITA to have to set everything back when you didn't do any TiBU backups and your nandroid is borked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
can all this be done without ever booting into TW?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes.

Edit: Although if you haven't done so, you can carrier unlock your phone from within TW for free and 5 minutes of your time.

http://xdaforums.com/showthread.php?t=2014982
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SomethingAwesome:
I followed a variation (used the Rogers Roms, and CWM) of this and now all is working. :)

My biggest hurdle was getting CWM recovery back onto the device to restore my backup (I used online Nandroid Backup and it put the file in the wrong folder/I forgot to tell it where it should put it), I ended up:

-flashing the latest nightly via TWRP, booting up and then using adb to push the latest CWM img file.

-Moved the nandroid backup to the correct folder on the internal SD.

-Restored my nandroid, clear caches, and installed then re-installed the latest rom, all without rebooting. Booted up and all works as expected.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
it sounds like

once this is installed that I would be running a rooted TouchWiz. So, If I boot into TW sounds like I can install rom manager and flash recovery and CM at the same time, does that sound feasible?

I don't necessarily want to restore my nandroid because I would want to go from M2 to whatever the new "Stable" is 10.1.0 when it's released. and i'll probably starting clean anyway other then maybe restoring titanium backups.

Thoughts?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Sure, that would work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
After upgrading my bootloader to i747UCDLK3, I noticed that it the 'fingerprint' in Root Checker still shows "samsung/d2uc/d2att:4.0.4/IMM76D/I747UCALEM:user/release-keys". Is that a permanent fingerprint that shows what the phone was first using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes, ignore the fingerprint part. It's not relevant. Only the bootloader is, so if that shows the updated one, you're good to go.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
So I am stuck at the Samsung boot logo I guess because I haven't deleted my data partition. I didn't realize I would have to do that, so I didn't back it up (other that with Titanium backup).

I there a way to back it up now? Remember I am stuck at the Samsung logo...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
You didn't make a NANDroid beforehand?

I think you can do an advanced backup with CWM and just backup data, but that partition is likely fubared now because it has CM and TW stuff in it. Best bet is to pray your TiBi backups are good, wipe data, boot to TW, (carrier unlock your phone if you want), then flash CWM and CM, then restore apps individually in TiBi.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
No, I DID do a nandroid backup, but that doesn't backup /data/media, does it?

Edit: Does it backup the entire internal SD card?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
It backs up...

/system

/cache

/data

It does NOT backup /sdcard
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
No, NANDroids don't backup the SD card. However, wiping data won't wipe the SD card because the SD card isn't mounted to /data/media until you boot to Android (someone correct me on this if I'm wrong). Wiping data would only wipe app data, not the SD card.

I did a NANDroid as you did, ODINed over the rooted TW image, wiped data, and booted. Ran TW for like 30 minutes just to play with it because the first thing I did when I bought this phone was wipe it and carrier unlocked the phone. Then I flashed the latest CWM Touch recovery, wiped system, data, and cache, then restored my NANDroid without issue. The contents of my internal and external SD cards was untouched.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Can't say I didn't warn you guys enough things could f-up easily. @_@
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
My method for doing clean backups is:

1. Nandroid to external sd and tibu (if desired) to ext sd.

2. Format data, system, cache.

3. Flash new ROM and gapps.

4. Restore from nandroid or tibu if desired

Or

4. Set up phone as brand new.

I also copy all pics, ring tones, Nova launcher backups, random other app data, to ext sd. Then I copy back to my new phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
How does one tell what bootloader version one has please? Is the bootloader version supposed to be the same as the baseband version?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trecko1234:
Look it up, I don't know the exact command but I know you can check it though ADB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Either adb or root checker from play store. Read earlier posts.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Psychosi42:
In a windows command prompt enter the following:

adb shell getprop | find "ro.bootloader"

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

Bootloader and Baseband are different parts. It's the bootloader you are interested in for this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Febby:
People must not read Lol... Least everyone is spreading the word about the root checker app that can tell you the boot loader version. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
You could also just run "getprop ro.bootloader" in Terminal Emulator on your phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Thanks. That was the simplest solution in my case. Question: now that I found out I have the I747UCDLK3 bootloader, is that older than the I747MVLDLK4 version? If yes, should I bother looking into how to flash I747MVLDLK4? Would I be gaining anything by doing so?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
UCDLK3 is the latest for the AT&T variant.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
I believe dlk3 is att, dlk4 is Canadian carriers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
That's correct.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
On Rogers (Canadian) and i have DLK4 now.

Was still running my original bootloader (release day SGS3), with CM10.1 20130513.

I updated it today to the latest rooted Rogers to get latest bootloader.

Didnt even boot the rom.

Made a full backup using TWRP, flashed Rogers rom (root66_RWC_I747MVLDLK4) thru Odin, then flashed TWRP thru Odin and restored my backup.

Then did my usual CyanDelta update (with Kernel) and all is fine now :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
Easiest way to tell if you have compatible bootloaders: try to flash a >5/14 nightly. If you get a bootloader assertion error, you aint got the right one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MystikMajik:
I did the same as you. Flashed latest rogers, Restored my backup, root checker confirms bootloader, still get assertion error when flashing new cm. What am I doing wrong?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Penguyen:
I own a Canadian S3, does it matter which Canadian stock ROM I flash to update my boot loader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
What's your current bootloader according to Root Checker? Which daily are you trying? You have to try 15/05 and up, 14 didn't have the commit to accept d2can.

---------- Post added at 04:50 PM ---------- Previous post was at 04:49 PM ----------

Yes, flash the one for your carrier.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Penguyen:
Is there any way I can find out what my carrier is? I can't seem to find out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fallen9999:
who do you pay your bill to that your carrier
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Penguyen:
I pay my bill to Fido but my phone was carrier unlocked. So I don't know what the original was.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Nandroid

I Odined over Cyanogen. Installed rooted bell Rom. Restarted the phone it wont boot and stuck on Samsung Logo. Went into recovery factory reset. Got in on TW. Used ADB to install latest CWM 6.0.3.1. (had 6.0.2.3 earlier)

Tried to restore my Nandroid from external SD. It is restoring all installed Apps, but none of the data such as TIBU backups, ringtones, wallpapers, game saves is getting restored. Any ideas why?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] minuteZERO:
When you did recovery factory reset, that did it. Sorry mang.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jiangyi:
Submitted a commit to add the remaining bootloaders for those using Mexican/Puerto Rican variants: http://review.cyanogenmod.org/#/c/37896/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MystikMajik:
So I''ve figured out I'm getting the 'Status 7' Error. Anyone else updating to the Latest Canadian Bootloader getting this problem? I can restore my Nandroid backup, but it just gives me the same error when I try to update.

Anyone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Sounds like you are running an old recovery. Are you?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MystikMajik:
I downloaded TWRP from the GooManager app. Would it give me the old recovery?

Yes. It says I have version 2.5.0.0 which is the latest one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
I am getting the assert failure on a Bell Canadian with the latest DLK4 bootloader when trying to update my 5/14 to either 5/15 or 5/16 through cmupdater.

Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackwing182:
if the assert gets merged 2 day, we can flash it on almost i747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jiangyi:
I made some ODIN-flashable files that contain the bootloader, RPM, TZ, and baseband of the stated versions, so that people won't have to go completely back to stock TW. It's intended for those not on the necessary bootloaders yet so that they can flash future CM builds. Put them into the PDA section in Odin and flash away.

I747UCDLK3 (AT&T): http://d-h.st/L64

http://www.mediafire.com/?pu279m19ob7ufru

I747MVLDLK4 (Canadian): http://d-h.st/yqV

http://www.mediafire.com/?74b1e321p537f5d

Tested by fellow users, works fine. Please flash at your own risk!

EDIT: Threw up Mediafire mirrors, since d-h.st seems to be down randomly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MystikMajik:
I have solved my problem. If you are Canadian and use TWRP, and you're getting the assertion error even though you've updated to latest bootloader, try installing the latest recovery for the d2att, not d2can. It doesn't like to flash d2att roms for some reason. I switched to the d2att TWRP and have been able to install what need.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] squirreltech:
How do I get the Samsung 3 way headphone buttons to work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ryanallan:
For the record:

Hoping to help out my fellow Canadians.

How I got into and out of this mess.

1. 1 year ago - Stock Telus GS3 with ICS.

2. Rooted and installed CM9.

3. Been flashing CM nightlies for the past year.

4. Received status 7 error when attempting to install the may 15th nightly.

5. Download latest Telus 4.1.1 image (with a root injected) linked a couple pages back.

6. Flash this with ODIN.

7. Reboot into a boot loop.

8. Boot into stock recovery and clear cache.

9. Now able to boot into stock Telus ROM.

10. Use root toolbox to change build.prop from d2can to d2att.

11. Download ROM manager and flash clockwork mod for gs3 att.

12. Using clockwork mod, download and install CM RC2 for d2att.

Now running CM10.1 RC2 without issues. *knocks on wood.

Hope this helps. I think the build.prop was a critical step not really mentioned in this thread (but many times in others).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
Flashed the d2att version of TWRP (instead of the d2can version), and I was able to update to 5/15.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vln004:
Thanks mate. I just used your att file, saved me a ton of time having to download the stock samsung image
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Shouldn't the Nandroid have all of that data in it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hopoholic:
+1 on the LK4 Canadian (on Bell) Worked a breeze, and fast! This was after spending the last couple hrs flashing back to stock rooted, flashing CWM again etc only to get the stat 7 error again. Good work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Penguyen:
My question is still left unanswered. Does it matter which Canadian stock ROM I flash onto my Canadian S3? I do not know which carrier it came with.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Doesn't matter they are all the same. Rogers, Bell or Fido would work. The only difference would be the bloatware the carrier includes with the Rom which for this particular exercise is moot. The firmware and base stuff is the same. So pick one and flash away!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Penguyen:
Thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] te_quiero_forever_girl:
i'm on the 05/11 nightly can got into this bootloader issue trying to flash the latest one. Can I just flash a rooted touchwiz rom, then flash to the latest cm in CWM recovery ? Or do i have to use odin ? Thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Flashing a zip via CWM or TWRP will not update the bootloader firmware. You have to do it via Odin which is a more thorough flash and includes things like the bootloader firmware etc. Read through the last few pages to see some of the steps people have been using.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AlbertoM:
For the very timid, like me, how do you use this, exactly?

Never mind. Just do it as he says. Works wonderfully!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Why are they reverting most of the changes?