yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] invisiblek:
Ok, first off the rom had nothing to do with you bricking your device. If you were to give me a step by step recount of what you did I'll tell you exactly what you did to brick. I guarantee, 100%, that you followed something for a different device or did something that was not documented anywhere. I know this device inside and out and there is absolutely no chance of bricking it by flashing this rom.

This will flash your system and boot partitions only. You could even write zeros to these partitions and still recover with no ill effects.

To everyone else out there: do not be scared! Devs are very careful to not document or guide users to do anything dangerous and cyanogenmod is no exception.
[Verizon Samsung Galaxy S III] aquaurchin99:
Since I've flashed 10.1 and reverted to 10 like 3 times I've got sdcard0 crap filling up my internal memory. I am still on 10, gonna wait a few days for 10.1. I just wanted to know what I am safe deleting. I see my old stuff in sdcard0/0/0. Should any of this stuff be in my internal memory anyways?

I just want to get this sdcard and internal memory junk sorted out.
[Verizon Samsung Galaxy S III] 996:
My IMEI is intact. My device is not bricked though. I used ODIN to get back to stock unrooted and locked verizon. I still have no data, just roaming. Any suggestions?

invisiblek? lol
[Verizon Samsung Galaxy S III] Aashiqmunda:
well.. i pretty much did nothing.. and like other people i started getting that roaming stuff.. and i reverted back to original rom and played with it but nothing.. so i rooted it and restored my backed up efs file and it went bricked on me.. basically i was unable to fix that roaming stuff and it went on to activating the device afterwards and it wouldn't budge from it..
[Verizon Samsung Galaxy S III] aquaurchin99:
Anyone have an answer?
[Verizon Samsung Galaxy S III] renzo.olivares:
ur safe deleting the 0 folder as long as nothing in there is important to you pictures..etc...don't delete the sdcard folder itself just the 0 folder as long as none of your personal stuff is in there it shouldn't matter
[Verizon Samsung Galaxy S III] droidstyle:
you can not bull **** people that know what they are doing! Invisiblek is correct...you had to do something out side of whats posted in the d2vzw section to brick your device.
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Same boat here, my sdcard has like 2 an 3 copies of the same file. I'd like to get that **** sorted an clean my sdcard up to free space

Sent from my rOot3d Samsung Galaxy S3
[Verizon Samsung Galaxy S III] aquaurchin99:
Okay, I'll copy what I need from the 0 folder and then delete it. Thank you!
[Verizon Samsung Galaxy S III] Aashiqmunda:
umm.. i wasn't bs'ing anyone.. i was only giving my experience to others from what i've gotten after flashing to cm10.1... also my point was that there is almost no other way to fix your device from that roaming stuff.. and its almost like in between the scale of soft brick and hard brick.. since you have no data? my phone also didn't send/receive any phone calls or anything..(it basically didn't had no service.. but it said roaming).. i had my sim card replaced from the Verizon store and still nothing..
[Verizon Samsung Galaxy S III] invisiblek:
There are so many threads and posts about this. I've heard of nobody else bricking while trying to recover their data.

Let's face the facts here, you f'ed up, missed a step somewhere on the restore or just plain can't read. Please leave, this is not constructive.
[Verizon Samsung Galaxy S III] tv31284:
I had the roaming issue. My imei was still intact but my phone number was unknown. It sounds like people have fixed this just by restoring a stock ROM. I managed to just reboot a couple of times and regained my number and full working data. I believe you're only supposed to install the efs file when you've lost your imei. So I wonder if that's why your phone got bricked.

In any case, I trust invisiblek implicitly. He's done a ton for this device if you follow the gerrit commits.
[Verizon Samsung Galaxy S III] bose301s:
So I have the official 10.1 and the 12/12/12 gapps, and now all the pictures that are on my phone are acting like videos, showing the play icon and trying to open in the video player even though they are .jpg extensions and showed correctly as pictures before. Anyone know what's going on or how to fix it?
[Verizon Samsung Galaxy S III] Aashiqmunda:
i respect invisiblek's credibility, but i was only speaking my voice here.. i hope that someone posts a fix for this issue for those who are experiencing this problem.

---------- Post added at 08:43 PM ---------- Previous post was at 08:26 PM ----------

okayyy.. i fk'd up... missed a step somewhere.. and/or i can't even read.. "please leave...?" no offense but i thought you were mature invisiblek?
[Verizon Samsung Galaxy S III] Deevious88:
This about it from a developer or newbie's standpoint:

Developer's point of view: You're leading people to believe (whether you intend to or not) that they are responsible for bricking your device.

Newbie's point of view: Already in this thread is a plethora of (unwarranted) complaints about roaming/no data/no voice when the two first posts EXPLICITLY state how to avoid these things AND how to recover from them. Now added to the mix is your insinuation that they risk hard bricking their device by installing the ROM.

And yes, while I also posted about the roaming/voice/data I'm also responsible for the diagnosed fix being included in the OP (which is constructive). Your issue is most assuredly that you flashed something incorrectly.

He's not being immature, he's trying to keep this thread clear of all these kinds of posts which don't add anything to the discussion.
[Verizon Samsung Galaxy S III] msburr87:
I had the roaming issue and with just five minutes and a search I was able to fix it. Frustrating yes but this is a risk you take when trying to flash the most cutting edge stuff.

And the fact that Verizon replaced a phone your broke is a joke.

The sure fire fix to this is odin back to 4.0.4 with root 66 then factory reset via dialer *2767*3855# at which point the phone will reboot and voila.. after that I odined the factory rooted OTA jb leak following instructions in that thread. This leaves you with a bone stock completely updated device to start flashing with again
[Verizon Samsung Galaxy S III] dave_k605:
I've flashed a few of the 4.2 builds and ended up with only roaming and couldn't get my phone activated, I've fixed it both times by flashing my synergy rom imei backup and flashing a rom I know works fine.

Much easier/faster than odin....this backup is something every gs3 owner in this forum should have stored on the ext card
[Verizon Samsung Galaxy S III] fillyfloater:
I also had the roaming issue in cm10.1 unofficial 1223, but I just went back to cm10 1216 after backing up what I wanted and doing a clean install along with formatting everything but the external sdcard. Got it up and running again then just dirty flashed the official cm10.1 1224 which in using now. Only problem is I can't send or receive text messages.
[Verizon Samsung Galaxy S III] bose301s:
Anyone, sorry for bumping but it got buried really quick.
[Verizon Samsung Galaxy S III] Chris123NT:
I'm seeing that as well, far as I can tell it's a bug with either the gallery or the media storage scanner assigning the wrong tag to jpg files. As a temporary fix I installed Quickpic from the play store, it's actually a pretty nice gallery app.
[Verizon Samsung Galaxy S III] bose301s:
Ok, glad to see it's not just me, will download that. Mainly I am home for Christmas so want to show off some pictures to parents/relatives, lol.
[Verizon Samsung Galaxy S III] chrisharper9643:
I agree always nandroid and back up ur imei there is always a risk that u wipe it all. Btw when I had this problem and didn't back up my imei (had roaming, activation loop, and a unknown number. I restored to factory rooted ota got a new sim then then had tech support reprovision it and all was good again.

---------- Post added at 12:26 AM ---------- Previous post was at 12:22 AM ----------

U must not dirty flash from unofficial to official cm its highly not recommended
[Verizon Samsung Galaxy S III] Chris123NT:
Check your CDMA subscription and make sure it's set to RUIM/SIM instead of NV.
[Verizon Samsung Galaxy S III] chrisharper9643:
Either one or two things need to happen... noobies need not to flash crap or devs need to start throwing in a imei back up script during rom installation like I believe synergy rom has so there are not so many ppl whinning that the borked their phones data.
[Verizon Samsung Galaxy S III] yznhmr:
So I have figured out that Data wasn't working (roaming), until I unplugged my Verizon Network Extender.. 4G popped right in

Also, Any one know if there is a kernel for this, so I can use fast charge?
[Verizon Samsung Galaxy S III] Chris123NT:
The roaming issue you are seeing is because the Jelly Bean Modems for the S3 are the first ones to support actually telling you that you're on the Network Extender, except CM10/10.1 don't actually support this function so the ROM thinks you're roaming. So your choices are to either let it roam, and allow data roaming so you can send/recieve mms while on the extender, or flash an ICS Modem which does not have the ability to tell you you're on the extender instead of verizon wireless (so you'll have to dial #48 to make sure you're on it) and the phone will no longer show roaming when in range of the extender.
[Verizon Samsung Galaxy S III] tv31284:
I'm on the latest nightly (12/24) and I've had this issue where if I'm listening to streaming music (its happened on both tune in radio and Google music) and I'm browsing the web, the phone will inevitably freeze and reboot itself. Anyone else experiencing this issue? I never noticed this on any of the prior unofficial builds and I'm wondering if the new audio commits have to do something with it.
[Verizon Samsung Galaxy S III] ka1z0ku:
Running 12/24 official and got a freeze/reboot using the Facebook app. Dunno if its related to the problems people have had with streaming apps causing reboot.
[Verizon Samsung Galaxy S III] fowen:
I first flashed CM 10.1 on the 18th when it showed up in updater. Like a dumbass I flashed it over CM10, and I got no data. I thought it was because I did a dirty flash so I tried to do a clean flash and then I had the same roaming issue everyone else seems to be facing. Fixed it by going back to stock and using *2767*3855#.

Fast forward to today, I saw a new release came out that fixed the Roaming issue. I rooted, and did a clean flash (after clearing system, boot, cache and dalvik) and I have the same issue. Activation loop, roaming, no phone calls in or out, and no data. My IMEI is in tact, but my phone number is all screwed up.

I am going back to stock again, but I am wondering if anyone has an idea why this is happening with a clean flash. Is it something I am doing (or not doing) when I flash the ROM? I am using the newest version of Clockworkmod.
[Verizon Samsung Galaxy S III] tv31284:
Might be it was just a coincidence I had a freeze and reboot while streaming and browsing. I wonder what could be causing the issue then.
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Ive got a similar problem myself, but when i go into my file manager it don't give me the option to delete the whole 0 folder. I can long press the legacy folder and it does give me the option to delete the whole legacy folder. Is there a file manger i can use to get the job done, i really want to get the storage issue cleaned up somewhat, im down to less than 4G's of storage.
[Verizon Samsung Galaxy S III] Aashiqmunda:
i was not able to go back to 4.0.4 and i did knew of this method but couldn't even able to be in the 4.0.4 operating system. it was stuck on boot screen
[Verizon Samsung Galaxy S III] renzo.olivares:
i used es file explorer
[Verizon Samsung Galaxy S III] fowen:
After re flashing to stock so I could stop from roaming. I re-rooted, flashed CM10, rebooted. Cleared cache & dalvik, flashed 10.1 and gapps and it worked!

Just to see what would happen, I did a factory reset after flashing 10.1, and the roaming issue came back.
[Verizon Samsung Galaxy S III] cgulliver:
Looks like The Grinch stole the nightly.
[Verizon Samsung Galaxy S III] fillyfloater:
I don't have that as a setting anymore. I'll have to add a screenshot unless theres another way to fix it?
[Verizon Samsung Galaxy S III] cbrehob:
Holy ****, read the past posts. If you have the roaming issue there is an EASY fix.

I cannot believe how many people think their problem is unique and don't read the forum.

If you call Verizon, or send your phone back, I hope they don't send you another one cause you don't deserve to be clogging up these forums.
[Verizon Samsung Galaxy S III] Chris123NT:
LOL yeah, invisiblek has an unofficial up but I have no idea if it has the 12/25 fixes for the official in it.
[Verizon Samsung Galaxy S III] Restola:
I usually use TWRP. Just for fun I flashed CWM again and tried to reinstall official 12/24 over my existing (working) 12/24. Stuck at roaming/activating again.

Thats 2 for 2 in recent days of CWM flashing CM10.1 and sticking me at 'roaming/activating', while TWRP has a flawless track record for as long as I can remember.

Not sure if anyone has had a problem after flashing via TWRP, but CWM fails (me)!
[Verizon Samsung Galaxy S III] invisiblek:
Resync'd right before the build and cherry picked this: http://review.cyanogenmod.org/#/c/29078/
[Verizon Samsung Galaxy S III] jbombs16:
Where are here development settings? I can't seem to find how to turn on usb debugging.

Also, is there a way to select external sdcard for camera storage? My gallery doesn't find any of my pics as they are all stored there.

Thanks.
[Verizon Samsung Galaxy S III] CKtheProblem:
Just wanted to report that I successfully dirty flashed the official 12/24 (cm10.1) over my cm10 (12/16 I think) without an issue. I simply rebooted to recovery, flashed the cm10.1 12/24 nightly, flashed the 4.2 gapps, and rebooted. Data didn't come up immediately, but I let the phone sit for a minute or so and it came up without me messing with any settings. I had one random freeze yesterday that required a battery pull, but I fixed permissions in recovery after that and since then everything has been smooth.

Just figured I'd post my experience so far for people on the fence about flashing cm 10.1.
[Verizon Samsung Galaxy S III] Chris123NT:
Flashed 12/25 unofficial. MMS now accounts for rotation which is very nice. Gallery still thinks my pictures are videos which is kind of funny but no big deal, I'll just use quickpic for now.
[Verizon Samsung Galaxy S III] mastamoon:
Merry Christmas everyone (or happy holidays to ya'll who dont celebrate)..

Here is a 12/25 unofficial build, straight repo sync as of about 10:30am today. No cherrypicks.

http://d-h.st/nRW

Enjoy.
[Verizon Samsung Galaxy S III] ddggttff3:
just flashed invisiblek's unofficial over the last CM 10 nightly. so far so good! Only thing I have noticed is that the overall GUI is a little choppier, but this is a unofficial build, and CM 10.1 is very new to this device so no complaints here due to the fact almost everything else works great! Got my new daily driver here.

EDIT: Never mind about the daily driver part, audio distorts too much at high volumes for me, back to CM10 for now, but im VERY thankful for the devs and there hard work on this device!
[Verizon Samsung Galaxy S III] funkymonk101:
roaming/activation fix

Hey all, I haven't been following this thread too closely, but for anyone else whose S3 got stuck in roaming/activation after installing CM 10.1, here's how to fix it:

http://xdaforums.com/showthread.php?p=35875331

For me, here's what happened, in case it helps shed any light on things:

1. Flashed 10.1 over 10.0 without wiping data. No roaming/activation problems, but a lot of system apps were FCing, so I decided to do a data wipe

2. After the data wipe, had roaming/activation problems, no voice/sms service

3. After trying a number of things, fixed the connectivity by flashing stock ICS thru Odin (as per link above)

4. Tried a clean install of 10.1 straight from the working stock ICS, this too led to roaming/activation problem, re-flashed ICS thru Odin

5. Finally settled back on 10.0, no issues

So I have a feeling that this problem only happens after a data wipe or on a clean install. I'm going to stay away from 10.1 until this is fixed, was a real ***** to recover from.
[Verizon Samsung Galaxy S III] iofthestorm:
I flashed I think invisiblek's 1216 10.1 build using TWRP and i had data/roaming issues but restored back to stock and back to 10.1 and things were fine. So in my experience TWRP is not necessarily immune. I've been on that since then because it's been working fine and I've had no flickering issues.

Edit: incidentally I was trying to set up a build environment again, but I got some error about target cm_d2vzw_defconfig not existing or not having rules to make the target. Any ideas? I started from an old repo from CM10 and did repo init -b cm10.1 to switch to 10.1, repo synced again and then 'brunch d2vzw' and it did pull down the d2vzw stuff so I dunno why it was missing the defconfig. Not really urgent or anything since I'm not at home for a week or so anyway.
[Verizon Samsung Galaxy S III] Chris123NT:
Actually it's hitting you with the activation/roaming stuff because of the CDMA subscription not being set correctly on first boot.

http://review.cyanogenmod.org/#/c/29078/ this should fix it, this fix is in invisiblek's 12/25 so it should fix the issue.
[Verizon Samsung Galaxy S III] mastamoon:
Probably have to edit your local manifest.
[Verizon Samsung Galaxy S III] Chris123NT:
Settings, more, Mobile Networks, CDMA subscription, set to RUIM/SIM and reboot.

If you are on a jelly bean Modem you will still show roaming because of the extender, so either flash an ICS modem or enable data roaming to send/receive MMS.
[Verizon Samsung Galaxy S III] bose301s:
So I have a concern. Do we think that will ever get as smooth and stable on the GS3 as on the Galaxy Nexus? It's 90% of the way there but there are a few things that aren't as good. Nenamark1 runs faster on the Galaxy Nexus than the GS3 as does Quadrant. the GS3 also gets stuttery after them in the menu etc. but putting it to sleep and waking it back up fixes it. Just a couple of examples but there's a few more. so, with the GS3 being much more locked and not having access to drivers and binaries do we think the GS3 will get to the level of the GNex?
[Verizon Samsung Galaxy S III] Hippoman13:
This is a question I've had in my mind since day 1. I've wondered how the s3 could be twice as powerful as the nexus but it still lags behind. I'm very sure this will change with Android 4.2; let's give it a month or so.
[Verizon Samsung Galaxy S III] odub303:
This is 100% wrong. The development section is not the place for anything other than discussion of DEVELOPMENT. Just because everyone asks general questions doesn't mean that it is proper. It just means there aren't enough mods to clean up the muck.

Sent from my Verizon SGS3
[Verizon Samsung Galaxy S III] odub303:
So you want the developer to start a new thread because people won't/can't read the op and a few pages of recent posts? I think this illustrates pretty clearly why all of this general charter doesn't belong here. And spare me the " but you're doing the same thing" nonsense. At least I'm trying to help keep the thread on track.

Sent from my Verizon SGS3
[Verizon Samsung Galaxy S III] Restola:
I think the OP and post 2 cover all the basics. If anything else should be added PM me. For anyone who wants a clean thread direct people to the OP if it's covered or ignore them?

VZW Galaxy S3 via Tapatalk
[Verizon Samsung Galaxy S III] soapinmouth:
I have no clue what you are are talking about in terms of smoothness I've never had as much lag on my gs3 as my gnexus, and I had my nexus overclocked and gs3 usually is underclocked. In terms of stability, eventually, hopefully, the nexus was stable because aosp was built specifically for it.

Sent from my liquid smooth gs3
[Verizon Samsung Galaxy S III] VECTUS:
Everyone, I have cleaned a few pages and got tired. This is a development thread. If its NOT development take it to general. I agree with Restola to just ignore non-dev questions or report them and I'll be glad to come back in and clean again... And hand out infractions... So I am ASKING everyone to please stop taking this off development and stop bickering... Just report things and let us Mods take care of the issues... I realize we mods can't monitor every thread and stay on top of everything thats why we need YOUR help. Just report violations and ignore the trivial stuff... Thanks and everyone have a Merry Christmas!! :D
[Verizon Samsung Galaxy S III] PerCompLLC:
Manage Apps > ALL > Phone and Clear Data. After that you'll be golden.
[Verizon Samsung Galaxy S III] aj8600:
Is mms broken for anyone else using mistamoons build?
[Verizon Samsung Galaxy S III] Chris123NT:
What kind of a problem are you having? I'm not on mastamoon's build but MMS works fine on invisiblek's.
[Verizon Samsung Galaxy S III] cbrehob:
Anyone else have GPS issues with these ROMs? Can't even get phone to find 1 satellite. Nexus 10 right next to me picks up 16 of them.
[Verizon Samsung Galaxy S III] invisiblek:
check out this post under "Special Attention":

http://rootzwiki.com/topic/35602-romcm10-official-cyanogenmod10-nightly-builds/#entry1000232

worked for me (Restola, you might consider putting a quote of that or something in the OP for now)

also, for those with the gallery bug with jpegs showing up as videos: http://review.cyanogenmod.org/#/c/29120/

that is merged, next nightly should have it
[Verizon Samsung Galaxy S III] ricecake2000:
Is it recommended to dirty flash from cm10 to the latest build of cm10.1?

I have tried just flashing 10.1 and was back in roaming.
[Verizon Samsung Galaxy S III] Chris123NT:
I had that at first, what I ended up doing was nandroiding back to a TW ROM, turning on GPS, getting a lock and then flashing back to CM 10.1 and it locked right away. Weird but it worked, invisiblek's solution might actually work better, and it's easier so I would try that first.

Awesome to hear the gallery bug will be fixed. I was hoping that would get resolved soon as that's the only thing left that's making things a bit inconvenient for my daily usage, although I have been using 10.1 for the last 3 days or so, before that I kept nandroiding back to TW :laugh:
[Verizon Samsung Galaxy S III] mastamoon:
Works on my phone :D
[Verizon Samsung Galaxy S III] Chris123NT:
It would be awesome if you kanged a build with the gallery fix that was merged about an hour ago :P.

Although I guess we could just wait for tomorrow's build :P
[Verizon Samsung Galaxy S III] WhiteBoy997:
Is it just me or is video borked on this rom? I'm using 12/24
[Verizon Samsung Galaxy S III] STVERDI:
I've been looking into 4.2 and it looks awesome. It this worth flashing yet?
[Verizon Samsung Galaxy S III] cbrehob:
Yeah, that's what I did. Worked too... strange.
[Verizon Samsung Galaxy S III] Chris123NT:
Describe what you mean by borked. Things seem fine here for me but if you're seeing something odd I'll see if I can reproduce it.
[Verizon Samsung Galaxy S III] WhiteBoy997:
When I play videos from YouTube I get a messed up video but audio works.

Sorry for the blurriness
[Verizon Samsung Galaxy S III] fillyfloater:
SMS still doesn't work on mine. Using iks new unofficial 1225. Can't find the cdma subscriptions anymore.
[Verizon Samsung Galaxy S III] Chris123NT:
Try booting into recovery and clear cache and dalvik cache. Video is working fine for me, AFAIK that was a bug in 12/20 and earlier that was fixed. Also, did you flash a custom kernel? I know the KT747 4.2 kernel will re-introduce the video bug since the bug was kernel related.

Settings, More, Mobile Networks, CDMA Subscription. Select RUIM/SIM and either reboot or toggle airplane mode on and off.