yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flashedmytiltblind:
I've had multiple crashes resulting in automatic reboot of the phone with RC2. I thought it was supposed to be stable? Anyone else having issues? I did a factory reset as well as davlik and cache wipes.

Spotify seemed to cause the crash twice. A couple of other non related crashes also occurred.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Try the latest nightly, they have done couple of kernel fixes after the RC2. Report the bug on the CM Bug Tracking system along with the log cat, this will help the CM team to kill the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
Edited

Have you updated your bootloader to DLK3 or the foreign equivalent? RC2 doesn't have the new asserts to the best of my knowledge.

Sent from my Galaxy S3 [AT&T][CM10.1]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
So I guess if I want the GPS issue fixed I'm going to have to flash back to RC2 and get a log huh....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
What is the issue you are facing with GPS?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Did you tried clearing the cache for Maps and re installation and you are not restoring maps through TIBU or TWRP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
It's not a MAPS issue because it happens when using ANY GPS app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iNeedICS:
Am in the only one getting an error whenever I try to flash this? It's one of those get build prop errors, I do have an i747 though (d2att)

Sent from Squishy's S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
We all assume you've read the last 5+ pages talking about the bootloader, right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikewestlake:
Thanks for this but I have a few questions. I'm on Canadian Bell I747M

1) Are the flashable with Mobile Odin? Can it be flashed without reverting to stock rom? Nandroids, of course..

2) using Root Checker as mentioned a few pages back, have DLK4 modem (I know I flashed that a while ago) but my bootloader is version I747MVLALH1. I thought I flashed this using Mr. Robinsons thread so I would have flashed the entire Stock rooted rom.

I can't find a listing of bootloaders against modem version numbers and I've seen it mentioned that bootloaders may not be at same rev number as the modem.

So, Can someone tell me that my bootloader is correct or not and can I flash the linked files through Mobile Odin?

I try to read as much as I can but some of it is not entirely clear since I don't have a Linux/Android developer background.

Thanks for the help,

Mike
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
On a side note, anyone using BetterBatteryStats can create a dump file of their stats and find their bootloader version in there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
1) I don't think so. I tried to flash via mobile Odin, and got stuck in an Odin flash loop. Powered down and booted into download mode and cancelled ton get back to cm without any issues except no recovery for the moment. YMMV. The description for these files says they are to help you not flash touchwiz. You flash it just to update the firmware.

2) yes, you need to flash the boot loader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Many people have issues with d2can.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ryanallan:
Check out cyanogen's post on g+.

He talks about why were having issues and what bootloaders will work.

https://plus.google.com/117962666888533781522/posts/UzrLe6wtk5d
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] r3dd09:
I recently upgraded to the 5.10 ROM and I haven't been able to send or receive mms/picture messages. Could this be related to the rom?

I've also noticed that a month or two ago I drop service randomly when it never did before and I was on the same rom for almost half a year.

When ever I drop service, I either have to toggle airplane mode or data to get it back on in a timely manner. Any suggestions?

Another thing, I've never had a backup fail until recently and it is happening more frequently. All happened when I flashed the new CWM. Any suggestions for this as well?

I'm off to bed, I can respond to questions once I wake up. Thanks in advance!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sirdizzle415:
I too have issues with mms. I dont think it is cm10.1 related in particular. I had the issue on slim bean and now on aokp.

EDIT: Found out that it was my ad blocker causing the issues. For anyone having issues with MMS not sending or receiving, try getting rid of your ad blocker before complaining on any of the forums.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Report the issue on cm bug tracking system. This will help the cm team to nail down the issue quickly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] minuteZERO:
I thought that too, but nothing in /sdcard is backed up. Thankfully I was using G+ instant upload so all my pics are safe! phew...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Nandroids backup /data (along with other things). They don't backup the internal SD card. Normally, when Android is running, the SD card is mounted to /data/media (someone correct me here if this is wrong), but if you just wipe /data in recovery, it absolutely doesn't wipe the internal SD card. I know this because that's exactly what I did when I flashed back to TouchJizz to handle this bootloader issue. The contents of my internal and external SD cards was left entirely untouched.

Doing a factory reset is entirely different than wiping /data in recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Exact. But when I flashed Touchwizz full stock rom via ODIN, my "internal" SD (emulated) was wiped. All in all, not a bad idea to make a backup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Interesting, I flashed a rooted Touchwizz ROM. They must have pulled out the bit that wipes the internal SD when they rooted it?

I backup like crazy. I backup before and after every ROM I flash, every time. Backup, flash new hotness, reboot, backup again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I don't know, maybe?

I was sad when my SD got wiped. :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Skdi:
Anyone having issues installing the latest updates? I can install up to the 13th but after that I keep getting failed to get build prop error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Read all the last pages and your questions will be answered.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] poetikal:
This question is not related to the bootloader issue, because I know I have the latest bootloader, but rather it's a question about updating.

I currently flashed to RC2 and I absolutely love CM, but is it worth my time to update to the most recent Nightly? Everything right now works, but I'm afraid if I update something will not function correctly.

Could I get someone's opinion? :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It's up to you. During nightlies, there's very little changes getting done daily. In the big picture, it matters, but for most you can stay on RCs and stable without any big issue.

Don't forget to update to the stable release chances are you will need to update your bootloader if it's not up to date.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Yea....that's no good. A little OT, but, I remember way back on the Nexus S, I accidentally wiped /sdcard instead of /system. I hadn't pulled a backup to my computer yet, so I basically had to rebuild everything from backup settings files. That took forever. I tweeted Koush and told him I could definitely say that the wipe for /sdcard worked in CWM. He laughed at me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
At least I had a backup of my pictures. The irony is working in the computer field, telling people the importance of having backups, yet not having one yourself. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
For real. I'm right there with you. I'm a software engineer and I'm always like, that can't happen to me. And then it happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ryanallan:
Haha +1

This is why I've started using the "cloud" more often. Automatic uploads can be a good thing.

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

Yep. Pretty much like reinstalling windows.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Yea I have Titanium Media Sync backing up everything important. And Dropbox backs up all my photos. And TiBi backs up all my apps and data nightly. Specific hardware is irrelevant. My life is in the cloud.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
I just flashed the latest nightly without updating the bootloader. Is that okay?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
I don't think it would let you flash if you weren't on the latest bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Yea how'd you get that to happen?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
You just need to delete the asserts at the beginning of the updater-script. That way it will bypass the bootloader check when flashing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Yea, I know how you got it to happen. The implication was that you shouldn't. The reason the bootloader is a requirement is for major stability reasons. I bet you spend more time fooling around with asserts than it would take to make a backup, ODIN the stock ROM with the updated bootloader, and restore your backup. (Obviously, it's your phone, do what you want.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
I have been on cm10.1 since it came out and decided to flash the latest nightly today and it worked. I didn't do anything differently, it was the same as before. I didn't update the bootloader or anything like that but somehow it worked. Maybe I was already on the latest bootloader????
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I suppose it's possible. The DLK3 modem (along with the rest of that firmware version) came out in November. When did you get your phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
It's been a year since I got the phone and it wasn't on the lk3 modem when I got the phone. I had to update it to the lk3 modem. Is there away that I can verify my bootloader so I can make sure I'm on the latest version?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
Root checker in the play store is quick and easy. There's a command you can use in terminal, but I don't remember.

Edit: getprop ro.bootloader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Use this app: https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker

Check under Build Info.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
It says "BOOTLOADER I747UDLK3". Isn't that the baseband tho? Or are they the same?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danvdh:
No, and no

The baseband is your modem

Your bootloader is your bootloader

your good to go, flash away ;) you meet the requirements to flash the new nightly builds

I'm only wondering how long until a stable is released

FOR ANYONE ELSE WHO NEEDS HELP WITH BOOTLOADERS

Task has tested these confirmed and working, REFER HERE

you don't have to install a full stock rooted/un-rooted rom, I can also confirm they work. Jiang is also the one responsible for submitting canadian and mexican bootloaders to CM allowing us to flash the newest nightly builds :)

also, forums have previous pages containing TONS of information that I see many people are asking here, Please use the search button :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
You're good to go. The modems and the bootloaders tend to share version numbers because they are released together with the same stock images. That number is actually the build number for a Samsung image. I think.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] equlizer:
Its been a while since ive flashed anything using odin (a few years) and just wanted to make sure of a few things. Im currently with bell and running AOKP 4.2.2 5/7/2013. Do i need to boot the phone into any specific mode? In odin, do i just load the file in PDA then hit start? What should/shouldnt be ticked? After flashing this, will i loose anything? Thank you :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AlbertoM:
And why do you think CyanogenMod himself would write it in there? That he was bored? Think!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Yes, boot to Download mode. The URL below is the page recommended on the CM wiki for those having trouble heimdall, but it goes over ODIN.

http://galaxys3root.com/galaxy-s3-root/how-to-root-att-galaxy-s3-sgh-i747/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] equlizer:
My F reset time is ticked by auto. should i untick it and just have auto reboot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AlbertoM:
Use it just as he said!

Thank you! Thank you! Thank you! Works great! You saved me a bunch of time!

Hsie hsieh!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] equlizer:
Still doesnt answer my question :( my reset time is checked. should it be? thx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
Leave it like that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
Have you tuned the feedback in the settings of SwiftKey

Sent from my GALAXYSIII running Jelly Bean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dmize:
Messaging app still has problems sending a new message to someone in my contacts list. Selecting them from the my peoples list doesnt show the whole number or anything part of it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
Must not have wiped. I don't have that problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
Not just you. Also, it does it with both AOKP and CM10s latest updates. Strange...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ghstudent:
Did they ever fix the issue of audio sources (such as music players) going quiet after receiving a text message?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aznkenshin:
Yep, it's been like that for me as well. Even back when I had SGS2 using AOKP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
Play music does the same thing to me on stock based roms... Maybe it's a Sammy thing not aosp thing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dmize:
I did a full wipe in recovery then installed. Wiped davlik and cache.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
Well I dont know what happened. I can go to the people list click a name and click the text and there number shows up normally for me.

Also dumb question did you wipe data also?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dmize:
Yup, wipe and factory reset before installed. I'm not sure, this happens on all jellybean installs. Cm10 and aokp. Using the jb 7 26 12 build for jb apps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
Funny thing, is I answered it, the only thing I can think of is, my reply got lost in the thread migration.

My bad
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drawde40599:
Only getting this issue when typing , works fine for everything else
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mocsab:
Problems installing Free aps

I am on CM10 - and I am getting an error when I try to install free aps from Google Play - "error processing purchase df-bpa-09" - it doesn't happen with previously purchased aps - or aps I have downloaded previously - but just about any new ap I try to install gives me the same message.

I found a post in another thread that suggested I unsync and resync GMAIL - and then reboot - but that didn't work for me - I tried clearing data and fixing permissions and that didn't work either - I am a little frustrated and dont know what to try next? Suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theadb:
Clear the data for Google sync services and Google Play. Reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkeyman:
Try what the last post suggested but what has worked for me everytime from flash to flash when this error pops is to clear the data from the Google Framework in the Applications menu.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Scottyedmonds:
Confirmed working LTE on Bell,

I'm running 07/25 and I just reflashed over 07/20 without wipe
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrakifa:
I had the same issue did a clean install and problem was solved.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tiffany84:
Getting some pretty great battery life:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cyanogen:
New build is up.. Theme engine is in and other CM features.. Video rotation hang is fixed.

Looking into the weird haptics. I just noticed it myself recently.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mem4720:
I just discovered that I cannot open the "share" menu from the gallery during a phone call. After I hung up, it worked normally. I don't know if this is a JB limitation or bug.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mahler47:
Don't delete asserts

I can confirm that updating firmware to I747UCDLK3 has solved my random reboot problems with 3.4 kernel. Previously, I was on I747UCLEM and I could not flash any version of CM with a 3.4 kernel (any version past 3/17) without getting random reboots. It's been two days now and I can confirm no random reboots.

By the way, I suggest using something like Bootlog Uptime ( https://play.google.com/store/apps/details?id=se.mumu21.bootlog ) to keep track of reboots. Those of you who are deleting the assert to avoid updating your firmware with these recent builds are probably getting random reboots but you just don't know it because you don't notice it when it happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Penguyen:
Does anyone else get random reboots while in a Skype call? I'm on the latest nightly with LK4 and my phone reboots occasionally during a Skype call.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AlbertoM:
My apologies. I wasn't answering you, but I should have. Yes. Download the right file for you. Search for it on PDA and then hit start. The only thing I had checked was Auto Reboot. Which means that after it's done the phone will reboot. I did not have the F. Reset Time checked but YMMV. I don't see how that'd hurt.

If you look under XDA for [ODIN] Desktop ODIN ver 3.07 for use with Galaxy S III

It has the Odin details.

Best.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bleedingthru:
im probably gonna get flamed but here it goes ... got my phone in last month and the phone came with ucdlk3 so i should be good to go when the stable comes out correct ??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] C2Q:
Hey folks. Haven't updated to a new nightly in a while (still using 4/13, running fairly stable with no issues). Any recent nightlies that are stable and worth upgrading to?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jorgeszabo:
Run this app: https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker

If you have root, your phone is unlocked and your bootloader is one of the newer ones (I747UCDLK3) then you are good to go.

If your bootloader is one of the older versions then follow the instructions a few posts back on how to update it without flashing a full TW ROM.

---------- Post added at 08:37 AM ---------- Previous post was at 08:35 AM ----------

You are missing out. A few good features made it in after that. Run any of the latest ones that came after RC2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] r3dd09:
I deleted ad blocker and did a reset, still having the same issue

I've never had to really report an issue, even though I've used CM for about 2 years in total. Guess I get lucky with a nightly that's super stable.

how do access cm bug tracking system?

I'm just going to start my phone from a clean slate. Delete everything as when it tried to save things to my sd card, it's actually saving it to the phone, and with the backup failures I've had, figure it's time for a full delete.

I'll also flash the new broadband this weekend and try out one of the new nightlies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pseudoware:
My bootloader is LG1, and I flashed RC2. Four days without a random reboot. Am I missing something?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rrolov:
I have the same issue. My bootloader is updated and I still can't install any new updates. I've even tried downgrading my bootloader and then upgrading it again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] r3dd09:
Flashed the new bootloader and I was able to receive the mms messages I wasn't able to before while on the same ROM.

Can someone enlighten me correcting the path the phone uses to transfer files to the sd card?

somehow it made a sd file on the phone and likes to transfer files there instead of sending them to the actual sd card.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] C2Q:
Do I need to update the bootloader or something if I'm coming from the 4/13 build to any of the the recent nightlies? Or can I just dirty flash the rom as usual?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I recommend searching a little next time, but recent nightlies have a bootloader requirement. Your bootloader must end in DLK3. Check under Build Info in the app below on your device.

https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Once Android is booted, I think you'll want /storage/sdcard0 for internal and /storage/sdcard1 for external.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
I WAS NOT recommending him to do it at all. I know that steve himself added the extra asserts and I think that it is good to ensure that CM10.1 runs best on every device. I personally do not touch the updater-scripts because I updated my firmware the moment I saw the commit on Gerrit for d2vzw. All I was saying is that if he wants to take the risk and flash without the bootloader requirements, he can do it by modifying the updater-script.

Did I encourage him to do it? No.

Did I answer his question of how to bypass the check? Yes.

Maybe you should be the one to think!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 2new2care:
Settle down peeps. Lol. Thanks for the great directions and updates on bootloader issues guys.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] montrealcityboy:
Who is this cyanogenmod person that you speak of? Never heard of him.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moose&beer:
:eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] minnick:
Haven't been hearing much recently about the actual nightlies themselves, everything about the bootloader. I will assume that means they're working great and flash the latest! Woohooooo

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
I think so. I haven't had any issues on the last week or so worth of nightlies
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fpshah:
Does anyone face the issue of not being too access the phone screen when in a call... Like you are on some customer care website and we want to use the touch pad to use some options ... The screen doesnt wake up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] knightblaze:
I get that as well. Simple press of the home button fixes it though. So long as it's nothing major I can deal with that until it's fixed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Latest nightly is silky smooth, no random reboots. I'm getting 4-5 hrs of screen time which is awesome. :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
Wonder why I'm getting a failed flash in odin?

edit:

actually it may have been my version of odin:

look right?