yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] magistrateee:
Geh ah well I guess I have to start from the beginning again. It's fine though just takes time.

Yeah I flashed the JB version but while testing some OC and then trying to put it back to default with and without VC app it gets messy.

I will probably just nandroid, reflash, then restore data.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Just reflash the ROM. That will replace the kernel files. You won't lose any of your data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
If anyone wants my gapps inverted package

http://xdaforums.com/showthread.php?t=1796568
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
So on AOKP there is no conversion of SMS-> MMS and it still concatates? I ask because MMS actually uses more battery. It will knock off at least 30 minutes of battery life with the amount of texting I do. Partially since I use DeskSMS to text (keeps the screen off) and DeskSMS won't work with the SMS->MMS and partially because MMS does use a data connection.

I'm sticking with CM9 right now (which has the same bug), but in the end, I need A2DP before switching up. I use it all over my house/office/car so missing that can't fly for me there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gromet:
Before I get pissed off can you please link me to this post you are claiming I made in Q&A? I for damn sure don't remember ever asking this question before...

..Gromet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polo045:
What he said!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] majingrim:
This thread in Q&A has the same answer that was given here:

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

I think maybe what he was trying to say was that these questions should be put into the Q&A section, not the development section.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] therealdamiani:
Hold down vol up and vol down at the same time with the power button. As soon as the screen comes on and flashes the samsung logo, let go of the power button while still holding the up and down vol button. Works for me everytime.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nikopatel:
Viber App is not working

Any one has a fix for Viber not working?

I make calls with viber to my friends out of country for free and also send messages and MMS for free.

I really wanna keep this ROM. i hope someone has fix for it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnclevenger:
I'm getting weird haptic issues on the 7/25 build. Sometimes the haptic feedback is _really_ strong (usually only with the hardware soft keys), sometimes it's normal, and at other times it appears to not work at all (usually only with the stock keyboard) . I've reinstalled the 7/25 build a few times, wiping everything, so I'm fairly sure it's endemic to the build. Anyone else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nikopatel:
yes I get that too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gtluke:
I get the strong haptic with swiftkey also, and only with 7/25
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
http://review.cyanogenmod.org/#/c/37792/

Cyanogen himself just approved it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danvdh:
yep, its merged :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Nice! I'm surprised there isn't a way for them to update the bootloader during the update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fpshah:
Is any one facing the problem that when in call, the screen goes off and doesnt respond to any buttons and it requires multiple key presses to get to the home screen?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
Distributing bootloaders is probably frowned upon by samsung's lawyers

Sent from my Galaxy S3 [AT&T][CM10.1]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
Plus an easy way to brick devices.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Yep...I can just imagine all the bricks that would be occurring if CyanogenMod decided to include bootloaders in their packages. If something goes wrong during the flashing process, you're left with a hard-brick that can only be revived using JTAG.

Also, CM is not allowed to distribute bootloaders anyway because it is proprietary software.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Thanks a lot for this! Being a Canadian user I'm very grateful.

In theory, there is a Mexican version (Telcel) and a Puerto Rican (PCT) version which are both 747M varients that have a third "latest" bootloader tied to them. The bootloader number is I747MUMBLL1. To be fair and include all who might use this d2att ROM, those should be added to the assertion as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] statickiwi:
Will there be benefits to updating the boot loader? I presume that no Canadian users have tried flashing the at&t bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Fair point. Let me rephrase: I'm surprised someone hasn't figured a way to update just the bootloader without having to reflash the entire Sammy image.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
I remember back with my Galaxy Player that bootloaders could ONLY be flashed from an official package...a few people tried to 'dd' them into the correct partitions and were left with hardbricks.

I'm not sure if it's the same for the GS3, but I'm not willing to take the chance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
It can be done. I don't know how much work would be involved. My understanding is that there were updates to the trustzone code to go with the kernel update. Trustzone code is verified in the boot chain so every other relevant part has to be updated at the same time. I don't know how difficult that would be to dig out of the stock rom or how many devices could be bricked if a mistake was made.

Sent from my Galaxy S3 [AT&T][CM10.1]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
I managed to update the bootloaders(yes, Qualcomm uses a 4 stage bootloader set-up but you can only modify 2) without completely flashing a stock ROM. I booted the phone into download mode and used heimdall to flash the partitions. First of all, always do --no-reboot in all of the commands to prevent your phone from booting into Android but reboot your phone back into download mode after each flash(hold down the power, home, and Vol-Down buttons at the same time). I did "sudo heimdall print-pit --no-reboot" to get the list of partitions. Then "sudo heimdall flash --[partition name] [new partition image] --no-reboot" for each partition I reflashed. I updated the ABOOT, RPM, SBL2, SBL3, TZ and MODEM partitions. I'm not entirely sure what ABOOT or RPM is(supposedly, RPM has something to do with power management), but SBL2/3 are bootloaders, TZ is ARM TrustZone data, and MODEM is the radio firmware.

You'll need to extract the new partition images from this: http://hotfile.com/dl/182224582/7ad...I747_ATT_1_20121116120521_7p9l4qgqoh.zip.html Unzip it and un-TAR the archive inside and you'll have your partition images.

After everything, it raised my flash counter so I had to use TriangleAway which you can find here: http://xdaforums.com/showthread.php?t=1494114

As for Qualcomm's 4 stage bootloader, you can find more information here: http://xdaforums.com/showthread.php?t=1856327

Sorry for the rambling reply but the process was really nerve-racking to do for the first time and I just want to share how I managed to accomplish this.

EDIT:It appears that the flash counter goes back up to one after I reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] minnick:
Thanks for testing the link bro... saved a lot of people headache and time
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
Does anyone know how to accomplish this with Odin? I would like to simply delete /system and /cache from the Odin rom but I don't really know the first thing about how Odin works.

Sent from my Galaxy S3 [AT&T][CM10.1]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
I've never used ODIN but there may be a way to flash individual partitions(after you un-TAR the complete package). You could always try Heimdall which definitely allows for flashing individual partitions.

---------- Post added at 10:14 PM ---------- Previous post was at 10:12 PM ----------

Just a heads-up, after manually updating my bootloaders, my flash counter keeps going up to 1 after I boot up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Yes that will work, there are reports people are able to flash the reports following these exact steps. Ensure you install the stock, unmodified ROM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
And all is restored with the world........
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Psychosi42:
My counter goes up as well. Triangle Away clears it but it goes back to 1 after a boot. Oh well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
15/03 nightly installed just fine on d2can for the record.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
This is in today's nightly already....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes, because he submitted it yesterday... lol

15 is the tomorrow of the 14. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I was just reporting it worked just fine, in case someone wasn't aware of the merge of the new commit to allow d2can.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kenlester:
5/15 not working on att, same as 5/14, getting assert failed for bootloader. == "I747MVLDLK4"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
you should probably read the last 3-4 pages of posts...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
What does your bootloader say?

Whether you have d2att or d2can, you still have to make sure your bootloader is the latest version available.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] detdett:
Same here :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Can you guys check your bootloader version?

You can use Root Checker here:

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

Build info section, BOOTLOADER part. Mine shows I747MVLDLK4 and it works fine (latest available for Canadian users).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kenlester:
Thanks, I have read the posts...

I747UCALH9... but i don't believe this is a permanent issue. ie, requiring the latest bl. just letting other know to give it a few day and see if its resolved.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You don't believe it's a permanent issue? It is, if you don't update.

The bootloader, tz and rpm most of us have been using are outdated and are creating issues with our roms right now, which might have just been the cause for certain people getting reboots. I don't think this requirement is going to get removed from CM nightlies.

You can workaround that if you don't want to update your bootloader by editing your CM nightly and removing the check, but then you can't complain if you're having issues down the road.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kenlester:
(speculations?)

i see you've put a lot of work into the last couple pages, thanks. up to now bootloader has not caused me any issues. i sure your knowledgeable on this but some of us would rather wait and see if the assert is removed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Why wouldn't you want the latest bootloader? You think they released inferior software just for the heck of it? Obviously a new release of software is going to be better, improving performance on your phone. Even if this wasn't a requirement, which it is and is going to remain, it's still in your best interest to update.

I've never had a single reboot issue that people are complaining about and last night I discovered that older bootloaders can cause random reboots and what do you know, I've had the latest bootloader the whole time which explains why I don't have any problems.

---------- Post added at 10:44 AM ---------- Previous post was at 10:41 AM ----------

Really? Cyanogen himself added the first d2att bootloader assertion and he also approved last nights addition of the 747M varient bootloader. Something tells me he knows what he is doing and wants it in there. If it was just going to be removed, why would he go out of his way to add more. This helps make sure everyone is on the same page. Development is much easier if everyone is on a level playing field.

Have fun waiting around on 5/13 while the rest of us move on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
More or less, arguably.

I understand you never had any problem as far as you know (and you might never get a problem at all!) with your bootloader, but in strive to attain a stable build I think they're trying to root out any possible cause. The bootloader doesn't get updated for no reason anyway, so it's not a bad thing to do if you can. Just cumbersome at the moment though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kenlester:
lord, my apologies, i humbly submit to your greatness. let it be know to all, do not update to last build if you don't have the extra time (atm) to up date your bootloader.

---------- Post added at 10:01 AM ---------- Previous post was at 10:00 AM ----------

cool, thanks, ill update soon...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You just won't be able to update, will not flash the rom, so no harm done I imagine (just time wasted :p)

Someone might find a simple and quick approach to just updating the necessary components in the next few days if you're not in a hurry to update to the latest nightly. This change is going to touch quite a few people and that's usually a good enough motivator for at least someone somewhere to put in some extra efforts.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
I just failed hard. Didn't have my media and crap backed up. It was lost when flashing stock due to reformatting. The default nandroid storage is included here. I was prepared for that thanks to this thread. I made a nandroid on my external sd. Unfortunately, when I went to use it, it failed the md5 check and would not work.

It turns out that my tibu backups aren't up to date either but they are there.

I just want this to serve as a reminder. I hope you guys don't have so many issues while updating your bootloaders

Sent from my Galaxy S3 [AT&T][CM10.1]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] quick6black:
Used this method, was able to update to the latest nightly. Also carrier unlocked my phone:laugh: No issues so far
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
You can turn off MD5 verifications or even generation in TWRP. Maybe you can turn the verification off and still use it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
As flexfulton said, you can turn off MD5 verification. What recovery and what version do you have? Some have had problems if I'm not mistaken.

As a last resort, TIBU is also able to open TWRP/CWM backups (CWM I'm sure, TWRP I'm not so sure) and extract your user apps + data from it. I've used it in the past and it works moderately well, as good as it gets I imagine.

Sorry to hear all hell went loose on you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bfaber:
If its not hard bricked, my motto is its allllll good. (sorry about the problems)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackwing182:
Can you add this one

i747MUMBLL1

its from Claro Puerto Rico Galaxy s3, Same Phone as US and Canadian Sgs3. that is my lastest bootloader update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] araemo:
When you flashed the stock rom in ODIN, did you check both PDA and Bootloader boxes?

As for why the assert is there.. some of the non-system partitions being updated include fixes that are needed to prevent crashes with the latest kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spacr:
For those that are currently running the newest nightly:

I am still having issues with streaming music over bluetooth. The audio kinda skips (best way I can describe it) for a second probably about 1-3 times per song. It does not matter if I use google music or Pandora. I'm not as well versed in ROMs as I wish I were so if someone knows why this happens can they please let me know so I have a better understanding of why this is happening. I've used stock and ktoonsez's kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] carbon12:
Still? Sigh, I have been waiting and waiting for this to be fixed... I would have assumed A2DP was fairly mature by now. Le sigh...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Are you guys sure it's a ROM issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Last time I streamed BT to my car I was in 5/11, but it played without issue for the whole ride (30 minutes). I'll try again on 5/14 with ktoonsez's 5/14.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spacr:
I'm open to any suggestions of what the issue may be. I just know TW ROMs work fine with the exact same apps installed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
Hey guys, any idea why Google Wallet is unavailable in the market for this ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Might be a good idea to try another rom, based off AOSP, that isn't CM to see if the issue is still there. Don't forget to nandroid prior!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
You can get it by changing your build prop to a compatible device such as the nexus 4. You can use this app to install it.

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

Once you have it installed and finished setting it up completely, you can restore your build prop, but you'll have to reinstall after flashing a new rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
What about nightly upgrades - do I have to do this every nightly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
Sorry, I meant every flash which includes every nightly. It's not too bad because it takes less than 5 minutes to set up. It's definitely worth it to be able to use this app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Did you rename your Nandroids on external SD? If so do not put any spaces there and you shouldn't get MD5 Sum miss match error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Just PDA, but the bootloader gets updated alongwith.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pdelponte:
I am super confused by this whole bootloader issue. I have read posts from the past couple of days and I still don't understand what it is all about, if I need to update my firmware, and how to update my firmware if need be.

My phone is a model number SAMSUNG-SGH-I747

My baseband version is I747UCLG1

My phone is rooted and running the 4/23 CM10.1 nightly

Any help would be greatly appreciated
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
I wish there was a way to automate this. Is there any?

Perhaps I could create a zip that would install the wallet .apk in /system/app/ (to be flashed after every nightly flash) and then it won't crap out? Anyone tried this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Just flash the zip with wallet in it after u flash the Rom/gapps. I dirty flash everyday and do this with no issues. Wallet runs like u just did a restart.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
Is there a way to do this with Mobile ODIN?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
mic not working in new hangouts app... any work around?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] araemo:
Cool.. I'm about to do this, I'm going to validate that rpm and tz get updated properly, not just bootloaders.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
RE: changing script to remove validation of an assert

https://plus.google.com/u/0/117962666888533781522/posts/UzrLe6wtk5d
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] araemo:
I was seriously interested in doing this, but print-pit and dump-pit were NOT working on my system, no clue why. So I'm using ODIN for the full update.

I do seriously wonder what would have happened if I had stripped boot.img, cache.img.ext4, recovery.img, and system.img.ext4 out of the tar and re-checksummed it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
The md5 verification failed because the backup was bad. I tried extracting the data using tibu but it crashed and rebooted. Whatever is wrong with that backup it's useless. Thanks for the suggestion

Sent from my Galaxy S3 [AT&T][CM10.1]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vvelvetelvis:
I'm sorry to ask a stupid question but I can't find where you set the rows and columns. It used to be under launcher/home screen. Can you still do this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
Settings > launcher > home screen > grid size

Sent from my Galaxy S3 [AT&T][CM10.1]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vvelvetelvis:
I don't have the Gris size option. I'm on rc2 if that makes a difference.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
You should just download apex or nova Launcher. It'll allow you to toggle more settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodrench:
Has anyone found a workaround for the phone only ringing once? Is there a setting that I missed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Longer ringtone works just fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
All these issues since 3.4 was introduced seem silly. Why not just do a complete wipe and flash 3/17, which has no problems whatsoever? There haven't been any big improvements since then, anyway. Seems pointless to spin our wheels over these really big inconveniences (such as the bootloader) when a 2-month-old rom works much better - with zero issues. I'm up to 1253 straight HOURS of uptime on 3/17. Everything works flawlessly and smoothly!

Here's the link to CM 3-17 in case anyone's fed up with nightlies and ready to try it. Make sure to do a clean flash, though! :)

There are no features that warrant or demand a 3.4 kernel upgrade. Why switch? I'm only posting to try to save you guys some hassle.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AlbertoM:
From Twitter

CyanogenMod

4 hours ago Edited Public

+1'd by

PSA - US Galaxy S3 Variants

As we march towards the 10.1 release of CyanogenMod, we have folks updating from older ICS stock builds. However, there is an incompatibility between the ICS bootloader firmware and Android 4.1 and above releases. As such, some users are reporting updates failing in recovery, or other boot issues when applying the 10.1 Release Candidates. When they do install, random crashing ensues.

To counter the inevitable freak-out and vague recovery messages, we have merged in additional validations into the d2att, d2tmo and d2spr releases. If you attempt to flash any future build and are on an incompatible baseband or firmware, the flash will abort with an assert failure.*

Some people are advising editing the installation script to remove the validations. Don’t do that. Seriously. Find a heimdall/odin or recovery-installable package of your device’s firmware, and install it.

To make sure your device is primed and ready for this state, the following lists the bootloaders compatible for each device:

d2att: I747UCDLK3 & I747MVLDLK4

d2tmo: T999UVDLJA, T999UVDLJC, T999UVDMD5 & T999VVLDLL1

d2spr: L710VPBMD4