yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangtastic:
hi pwn...

I'm on the latest cwm and mjb(baseband)/lk3(bootloader) and I'm getting the assert prop errors too when trying to install 3.3... I've read you can brick trying to go back to mg2... any thoughts on how to proceed?

UPDATE:

my bootloader was lk3, not mjb - so I've now updated with i747ucuemj2 bootloader and baseband and v3.3 installed without a flaw.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
On stock camera, when taking a video and then switching to camera kills the camera. But on camera fx, I can switch from video to camera with no problems
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pilothaz:
I'm on this bootloader too, and it keeps giving an error even though I see it in the error saying it isn't one of them...

On twrp on the latest, 2.6.3.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
error 7 update to twrp or cwm, one or the other based on what you currently have,,,,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theyurtingyeti:
I'm on the MJ2 bootloader. Do I need to switch to the MG2 pwn has up?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MaxGQC:
I can't boot the phone in recovery mode or download mode and Odin doesn't seem to recognized it... Looks like a hard brick doesn't it ?

Windows seem to see something when I plug it in.. I hear the "usb device connected" sound
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jakers1991:
Hey man I have MJB modem and MJ2 bootloader. can I flash MG2 modem and it won't brick my phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
Just sitting here at my desk, flipping the boom open and closed on my H720, watching the bluetooth connect, disconnect, connect, disconnect... :D Thanks Pwn!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
In on MJB modem and MJ2 boot loader as well. It's working fine for me. I'm not changing it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jakers1991:
Thanks for the help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baskln:
Has anyone got ART working? I got everything installed, restored my TiBU backups, then trying to switch to ART and I'm stuck at the Google boot logo. I don't know if its optimizing apps or not in the background, it's been stuck for awhile. I pulled the battery to restart and its doing the same thing. Any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
clear dalvik and cache? :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] colhavoc:
Not sure if anyone else is having this... problem but here it goes:

Installed latest Quantum 3.3 using the included 2/9 kernel, and 0-Day PA Gapps (20120207). Fresh instal (factory rest/wipe dalvik/wipe cache/format system). Upon boot (and reboot) I am sometimes getting a 'chiming sound', almost like a door bell in sound and it repeats... and repeats.. and repeats and won't go away unless I reboot, and hopefully it doesn't start that time. Not sure what the sound is, never used it before for any of my system sounds.

Anyone else getting this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baskln:
Just tried it, same thing just stuck at the boot logo....sigh
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
Downloaded 3.3, but phone says i'm still on 2.7 WTF?:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
Did you inadvertently flash 2.7? Mine says 3.3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baskln:
Clearing cache didnt work, had to do a restore. Tried switching to ART after my restore, which was a fresh 3.3 install and still it just hangs at the google logo. I guess this build just won't work with ART
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PlayingPoise:
Running like a charm over here, loving all of this! Fast charge is sure to come in handy too, thanks so much!

Sent from my Quantum-powered SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Anyone help me as to what this is? Just flashed and tibu'd and this....

Complete clean flash an internal format.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] poppo101:
Good to know. Right now have have 3.3 loaded on my play around phone which is running MJB bootloader and modem.

Stock camera working just fine. LG camera working just fine.

Don't really use bluetooth on the play phone however it did connect to both my house phone and the speakerphone in my car.

My daily driver is running MJ2 bootloader and MJB modem. Will probably flash 3.3 on DD this evening.

.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Nice new boot logo! :P is there supposed to be a welcome to cyanogenmod window?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
Didn't do the full system wipe. O.K., i'm planning on doing a nandroid back-up(for the first time). After i back-up, and install the new rom & gapps, do i restore from back-up first and then reboot, or the other way around? I don't want to screw this up. Thanks for any help.:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
3.3 is now in my eyes an almost completely stable release. It's been doing amazing on battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
First try a dirty flash if your on 2.7.

Make a backup.

Do an advanced wipe and wipe system, dalvik and cache.

Flash ROM and gapps.

Wipe dalvik and cache.

Reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
Nice. Tapping the alarm icon in the quick settings takes you directly into the alarm list, it doesn't assume you want to add an alarm first :)

Been wondering since the beginning of Quantum... If I'm on a bluetooth call and I end the call from the headset (or the other party hangs up first), the phone goes to my PIN lockscreen. Which of course is a bummer because then I have to unlock the phone. Is it at all possible to add a checkbox to disable that? I can see where that would be a security feature so it should be an option...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baskln:
Any ideas on why ART won't work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
O.K. When do i apply the "back-up"? After the Reboot, or before?:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
Don't apply the backup. It'll overwrite what you just installed. When you do the advanced wipe do NOT wipe data.

I'm using TWRP as my recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Thanks so much for your work! (These last few pages are why I hate upgrading my bootloader)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
What Gapps package are you using? ART is not Xposed compatible either..

Just listing options you might have gone through already.

Are you doing a full clean install?

clear:

cache

dalvik

wipe data/factory reset

mounts and storage - format system

Install rom, Gapps, reboot.

Lol I don't have much else for an option. IMO ART is not worth it, I have way more battery life in dalvik and can use xposed for many good reasons. (main goal of my battery guide - Greenify paid) to name one.

Edit: see pwn's post below.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] UnicOrnseeD:
Where can I find the latest cwm flashable zip?

Skablorp!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bloodfart:
?

Boots great into setup....pick language..and get system ui crash, reflashed without gapps..booted fine

Anyone else have this issue? what gapps everyone using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Art has to be fixed in the next update. Sorry about that. It's still not supported :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
3.3 won't go in. I'll try a fresh download. Maybe the first one was corrupted?:eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
Get rom manager on playstore, update there.

Edit: wrong person on second quote lol..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Been on carbon since its kk builds came out, but I think I'm going to come back to this. Battery life just isn't there for carbon even using quantum kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
What error are you getting? I had to update my bootloader in order to get 3.3 to install.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
I'm downloading another 3.3. How do you update bootloader?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
If you are on AT&T, I believe Pwn has a bootloader on his dev host page. Search this thread for the link.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Flash in Odin. Which one are you on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kinjo1023:
Fast charge....is it auto enabled or is there a setting? Brief look through and I'm not seeing it. But I'm also retarded tired.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaspah:
You can flash a bootloader update through CWM (or whatever the other recovery is) just fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
O.K. soft-bricked the phone, but got back into recovery. Now i'm downloading the 3.27 rom, and waiting for all my apps to come in. Will try to update bootloader when this is done.:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] colt45x:
I loved Quantum it was a great ROM. Unfortunately some low life decided to steal my phone out of my bag at work, so no more S3. It was fun while it lasted. I don't what I'm gonna do for a new phone, maybe I'll try to find a used S3. Thanks for the ROM Pwn!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaspah:
Ugh, this ROM was super smooth on ART. Could have at least given a heads up in the changelog. Bit disappointing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danman0:
Dear Pwncakes, Is there any possible way to fix subway surfers?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PlayingPoise:
Do you think you could add the DSP Manager from Carbon into a new build? It worked really well, and it was one of my favorite things. The current DSP is way outdated compared to it. Just a suggestion

Sent from my Quantum-powered SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BottleB:
AT&T Bootloader should be fine on Telus i747m right? Same phone afterall.....but can never be to cautious :
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
No good. Can't install 3.3, so it's back to 3.27 for now. Went through Rom Manager this time, but failed. Don't know anything about bootloader, but Rom Manager is 6.0.4.7. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
No it won't. Canadian bootloader works just fine. https://www.dropbox.com/sh/a8fvzrow4gwmuqi/O9FMQ6dDZ3/I747M/boot_CWM_I747MVLUEMK5.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Pwn, what do you use for App Ops, because I tried a fresh install and using App Ops Xposed it still FC'd.

EDIT: Never mind, I disabled that module and App Ops works just fine now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdpeek3:
I had the same issue, assuming you were getting "Error 7". I updated to 6.0.4.7 and my modem was up-to-date as well but still couldn't get it to install.

The only thing left to do was to force the install by deleting the assert prop lines in the updater-script. After that, everything worked like a charm. Happy to be on 3.3 and excited to see the battery life. Thanks for everything PWN!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
Can you send me a photo of what you're talking about? Where do i find the updater-script? It's the only way that this noobie can learn. Thank you.:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdpeek3:
Are you getting the "Error 7" message when you install through CWM? If so, check this out, it's a good explanation of the asserts.

http://www.youtube.com/watch?v=QW1znjDLe-k
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
Wish I had read this before trying to update with the MG2 bootloader on Pwn's D-H.

Yeah, I'm dumb. Looking for a JTAG service now...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] X_Fact0r:
I got the same error at first. What I did was:

1) Update CWM to the latest version.

2) Update to the most recent bootloader from this link: http://xdaforums.com/showthread.php?t=2321310

Then I tried to install the Quantum 3.3 but still got the error in CWM. So I then did a 3rd step

3) Update to the most recent modem from this link: http://xdaforums.com/showthread.php?t=1831898

After completing these 3 steps, Quantum 3.3 flashed successfully. I didn't have to delete anything in the updater-script. Just an FYI for people who got the same error and didn't want to mess with the updater script :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Valepato:
Ok, so I'm on Quantum v3.21 and I want to install the latest ROM, in order to do so I have to update my bootloader, but i'm not sure which one to pick. Now I have this one I747UCDLK3, I see that the newest one is this I747UCUEMJB, but Pwn suggested this http://d-h.st/rZT to another user. Which one should I go for? Also, I need to update my modem too? I just want to be sure to not brick my phone.

Thanks in advance!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
I beleive you will have to update bootloaders as that's an old one I used to have. I have I747UCUEMJB and 3.3 installed fine and is running great
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
Bootloaders

Remember guys, if you elect to flash the official MJB boot loader, you are stuck with it. Attempting to downgrade will brick your device. Option A below is the MJ2 bootloader and is working fine for me. You can downgrade back to an older boot loader if you ever need to. Option B is the MJB BOOTLOADER THAT YOU CAN'T DOWNGRADE FROM.

Complete recovery flashable I747 and I747M 4.3 bootloader and modem packages.

*

AT&T I747 ONLY, AT&T I747 ONLY, AT&T I747 ONLY

AT&T I747 ONLY,AT&T I747 ONLY,AT&T I747 ONLY

Option A: MJ2 bootloader and MJB modem

http://www.androidfilehost.com/?fid=23269279319197286

If you choose to flash the official MJB bootloader and modem package DO NOT try to install any older bootloaders or use any odin.tar, you will brick your phone.

Option B: Official MJB 4.3 bootloader and modem

http://www.androidfilehost.com/?fid=23269279319197285

==================================================

I747M ONLY, I747M ONLY, I747M ONLY

I747M ONLY, I747M ONLY, I747M ONLY,

Official MK5 bootloaders and modem

http://www.androidfilehost.com/?fid=23269279319197493
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FirstROMQuantum:
https://www.google.com/android/devicemanager

Try out that ^ hopefully you had it enabled :(. Sorry to hear about the scumbag thief. If you do have the device manager enabled under Settings/Security/Device administrators/Android Device Manager, then you might be able to lock it down and locate it. You may not want to confront the person yourself, but perhaps by police officer? It's up to you.

If you're unable to have your phone returned then this will just be a bummer, but also a learning experience.

Next time around I would recommend enabling Android Device Manager and maybe even purchasing Cerberus anti-theft app.

https://www.cerberusapp.com/ | https://play.google.com/store/apps/details?id=com.lsdroid.cerberus

EDIT: ALSO!!! Since you're obviously experienced in flashing ROMs: https://www.cerberusapp.com/download.php

---- If you purchase Cerberus from the playstore, you can alternatively flash the Cerberus App into the ROM itself. (This is good if the thief performs a factory reset on your phone as the app will stay installed)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
I remember I had to flash the MJB BL for a 4.3 ROM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FirstROMQuantum:
You want to have I747UCDMG2. Pwn even posted earlier that this is his favorite bootloader version.

So yes, you'll want to use this one: http://d-h.st/rZT
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bloodfart:
show me how to delete prop lines plzzzz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Use 7-ZIP and go into META-INF/google/android and edit the updater script but only delete up to and including the " ; " you don't want to include.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] poppo101:
I have option A on one phone and option B on another. I had no problems installing Quantum 3.3 on either one. Just remember, as stated above, there is no going back to an older bootloader if you choice option B. Trust me, you will brick your phone. Had that happen when I took the OTA 4.3 update and then accidently flashed an older bootloader. With option A and the MJ2 bootloader, you can flash an older bootloader like MG2.

If you do accidently brick your phone, as I did, the information in this thread will help you unbrick your phone. It worked for me.

http://xdaforums.com/showthread.php?t=2549068
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alkiter:
3.3 rocks, fastest rom ever on this device!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
I read this comment made all the time. How can you tell unless you're using an app to measure? Personally I really can't tell any speed difference between updates. I also can't tell between ROMS unless of course one is laggy. If it is faster it would be in milliseconds, something I can't see.

Now battery life, that I can tell and Quantum is hands down the best battery life of any ROM I have flashed. It's the reason it's my DD.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alkiter:
I use a benchmark program. It doesn't matter which if you only compare the same device. But you're right, most roms are so fast that you can't tell the difference just from a user standpoint.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
FWIW, I'm using an AT&T S3 (SGH-I747), MJ2 baseband and boot loader, and TWRP 2.6.3.1. Did a full wipe (cache, dalvik, system, data) and installed 3.30 without a hitch... after I made a backup of my V2 installation, of course. :) After rebooting the phone, tweaking various settings to my liking, and installing my own personal collection of "essential apps" (Titanium Backup, ES File Explorer, and Trickster MOD), I made a backup and went back to V2, as I didn't have time to restore all of my apps and customizations. It'll be waiting for me, though, so I can start testing V3 in earnest!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theyurtingyeti:
Glad you'll finally be joining us. I know you've been patiently waiting for the right version :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Pwn can we have download mirror. Dev host is thw worst download hosting.. Tryto download the latest juste since last 7-8 hours
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
So i guess that you flash this bootloader

after

you wipe the whole system?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
Can't speak to the AT&T bootloader but I was able to flash the Canadian version b4 I flashed the latest Quantum update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] poppo101:
that's what I would do. Not sure if I saw you mention what bootloader you currently are running. Just make sure that you are NOT currently on MJB bootloader or you will brick your phone. The MG2 bootloader is a downgrade from MJB which will brick you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
i read somewhere on xda that you have to reboot to see the new version so what I did was.......

twrp and flashed the bootloader (MG2) and modem (MJB) rebooted

back to twrp for a full wipe......install rom, superuser, gapps..........set up and enjoy.

not sure of the proper ettiquite, but this is what worked for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sandman97289:
Yup, rebooting did the trick after new bootloader/modem install.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
Thank you. This did it for me, and i'm running the new rom. Have to give that new launcher a try, as i'm so used to Nova. Thanks, again.:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Well, there's still no AM/PM :D, but I think I can live without that for now. The true test of whether or not I'll stick with V3 is Bluetooth, specifically if it connects to my car and stays connected without a hitch. Otherwise, it's back to V2 and the waiting game. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theyurtingyeti:
Yeah, bt hasn't been the same for me since 3.15. It's worked ok, but not great. I hope 3.3 will be gold :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] i5lee8bit:
Loaded ROM last night as soon as it was uploaded (vodka edition lol). I was on the road a lot today. Worked with no problems at all on JVC KDX250BT head unit. Several times getting in and out and turning car off parking etc, even synced even with phone book first try in seconds.

Also at this moment I'm watching YouTube and voice searching with LG HBS700.

I lurked this thread until some people reported Bluetooth was working good so I decided to try it. I'm lovin' it. Ba da ba ba ba

---------- Post added at 11:37 PM ---------- Previous post was at 11:27 PM ----------

Although I did get a random reboot right before my last post. While I was trying to log in (typed turbo j in user name box then screen went black for a few seconds and rebooted). First one I had but otherwise extremely stable under heavy usage since flashing last night at 2am.

Last k msg attached.

edit: oops apparently i suck and didn't attach file
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarKnight6969:
Downloaded and clean installed 3.3 VE, absolutely no probs with anything! BT working perfectly with disconnecting and reconnecting, power on, off(both earpiece and bt) and out of range. This is the best one yet!! Most awesome job! Great kudos to Pwn!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] UnicOrnseeD:
hard bricked!!!

The new bootloader hardbricked my gs3 on rogers in canada. super bummed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MaxGQC:
Same here :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
Which exact bootloader are you speaking of?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
You guys.. its so easy to find. http://xdaforums.com/showthread.php?t=2321310

Bet you can get it working. Follow instructions, don't downgrade, thats how you brick.

If you are on I747MVLUEMK5 bootloader, you own a Canadian phone. You don't need to update, this is as new as it gets. But if not up-to-date, get there with the link above. Hopefully nobody is downgrading bootloaders. There's a difference between USA, CND and International etc.

Hopefully there's a way to fix bricks..

You'll find more answers searching AT&T Galaxy S III

Q&A, Help & Troubleshooting

and

General

thread areas of this forum.

For those not able to flash pwns rom, update recovery, cwm from Rom Manager on playstore, thats all I did.

Hope this helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I'm very disappointed to see that it's STILL an issue that nobody can understand to research before upgrading something so utterly crucial. It's been stated a million times that it's for AT&T only, and this isn't our first rodeo with this bootloader stuff.

Come on guys, actually read stuff before blindly flashing stuff.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
On a more positive note, this update just sips battery better than ever, and screen on with simple GPU is great. Thanks for your awesome work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] UnicOrnseeD:
I Upgraded my recovery and read through a lot of the thread leading up to, but I mistook a secondary mirror link for a bootloader I thought was for my phone. It wasn't. Now I have a fancy piece of ****. Nobody to blame but myself.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bogdaryl:
Working great thus far! I really appreciate all your hard work PWN. Thanks. Running ROM on both the daily driver and backup with no problems on either one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xsever:
I kept getting status 7 error even after i updated the bootloader. My cwm was already the latest version.

All I needed to do, which was in the changelog, was to CLEAN FLASH.