Share this Story

Unofficial CM10 and AOKP Builds Released for Verizon’s Galaxy S3

The locked bootloader on Verizon’s Galaxy S3 hasn’t stopped development much to this point. Last week, we saw the device receive an unofficial CM9 port, but over the weekend, things turned up another notch. Two unofficial ports of AOKP and CM10 popped up, with each either being as close to fully working as possible or with a couple of minor bugs that will soon be worked out.

AOKP Milestone 6 appears to be ready for prime time and a daily driver without any known bugs. CM10 is definitely still being referred to as an “alpha“, however, data and all of the other most important features are working. If TouchWiz is too painful and stock Android is your saving grace, you may want to consider looking into either one of these.

As a reminder, these ROMs are possible thanks to CVPCS’s kexec boot sequence and will appear to boot twice during bootup. That’s normal and is simply the kexec doin’ work.

Via:  DroidHive (CM10) | RootzWiki (AOKP)

Cheers Jon and Steve!

  • Matt

    “System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help.” I’m not sure why this happened – everything seemed to be going fine, then it restarted to this. Can anyone help? Please?! Thanks in advance.

  • billybobjon

    oops wrong topic lol

  • billybobjon

    ok sorry to be a chatty kathy here but i just actually went to USE root access and it didnt work after a couple a reboots to my s3 i was kinda confused because the super user icon was there…hmm….just wanted to let everyone know if you have this problem, go into superuser.apk app and slide over to “info” then a button that says “tap to check for updates” click this and then click update at the bottom of the screen….for some reason that fixed the root and it started working…for me anyways…

  • the link for droidhive is down, it just takes me to godaddy.com

  • Ken D’Ambrosio

    Stupid question: I’ve flashed my Droid-X several times, but now that I have an S3 (Verizon), is there a step-through on how to do this? I *really* don’t wanna make it an unrecoverable, unsupported brick. But hoo-boy, do I want Jelly Bean.

  • LT

    Do any of these builds bring back proper text reflow on pinch/tap-zoom on the stock browser? That’s really what I want on this phone, don’t want to compromise a feature I <3 on my Thunderbolt.

  • Silent

    I’m having issues with the AOKP I can’t connect to 4g anyone know how to fix it

  • ChrisTraeger1

    God damn I love that wallpaper. Anyone know where I can find it?

  • J Dub

    CM10 seems to work better than AOKP right now. There is a method to use to backup your IMEI in the event you muck it up and lose it somehow. Currently the Phone Info app is needed to accurately set your mobile data mode correctly. I think the newest CM10 build is dated for today, 7/23.

    I am running the 7/21 build and it is pretty solid. A few bugs, but nothing that makes it not worth a DD.

    • Jordan


      • J Dub

        And yes, GO HOKIES!

    • Mykich

      Go Hokies!

  • Blixdevil

    Soooo, until these are deemed stable does anyone know of an app to tether with that does not require root?

    • smer


      • Blixdevil

        Thanks! Is that a suggestion though or is that confirmed to work for the S3?

        • marty jones

          Why don’t you try it and see if it works?

        • Ya-Ta

          Confirmed it works on VZW GS3.

    • dcvolcom909

      https://play.google.com/store/apps/details?id=com.svtechpartners.wifihotspotdemo&feature=search_result#?t=W10. Worked with Galaxy Nexus before I rooted, not sure if it works with GS3… but it worked good for me on the Nexus!

    • mrvelous01

      Pdanet 3.5. works fine with Verizon GS3 using USB or Wifi Hotspot.

      • mrvelous01

        oops – needs foxfi for the wifi hotspot, too (but IIRC installation tells you that).

  • muffnman
  • Caleb Shahamat

    I have a GS3 with VRLG1. Anyone know if it’s safe to root with the current method??

  • Destroythanet

    Devs > Verizon all day, everyday.

  • crane476

    I would hold off on flashing these. A very serious issue has been found when dd’ing the fake clockworkmod recoveries used to flash these roms. There is a chance when pushing the recovery the efs partition will be corrupted and you IMEI will be wiped. Simply put, it means you wont be recognized by verizons network. This has been confirmed by several devs on IRC.

    • While I normally just ignore the people who have random problems with their devices…Yes. This is confirmed. Be careful guys!

    • The first guy reporting in the XDA thread had edited his original post stating that it was only wiped because he interrupted the activation (that would ultimately fail but still work) on the CM9 port. I just waited on mine and had no issues. Still a scary situation, just be careful.

      Otherwise, I used it all weekend pretty extensively on a little road trip almost without a hitch. The only thing I noticed is a weird little SMS bug where it can’t send a ‘joined’ message >160 chars. The stock app visibly split them into two and I had to change Hancent’s settings to force the split. But it even fixed an annoying BT Audio bug with the stock version, so it comes out ahead for me 🙂
      Just updated to CM10 a little bit ago and the activation actually went through without any fuss. I’ll see if I can find any new bugs.

      • Thanks for the info. Keep it coming. I am a little scared on this one but JB on SGSIII is my dream device right now. Damn Verizon…

      • crane476

        You see, the issue isn’t with the activation because it has nothing to do with ROM itself. The problem occurs when pushing the recoveries used to flash these ROMS or a custom kernel.

        • That may be, I’m not terribly familiar with most of the different partitions and what gets touched when you flash what. All I know is the one user who reported the IMEI wipe for himself and another user (I reread the thread and could not locate anyone else who got his IMEI wiped) said that it happened because he powered it off during the activation. He could be wrong, or maybe that could be causing it in some other unexpected way.

          • crane476

            Powering off during an activation could have very well caused it. But talking to some people on IRC last night, I found out the problem is occuring on the stock rom as well.Thats why they think custom recoveries and kernels are causing it since the exploit used to load them pushes them to the mmcblk0p18 block which is where the IMEI is stored in the EFS partition. Some think the partition is becoming corrupted, but don’t know how or why yet. I heard you can now back up your efs data, but I’ve heard mixed results on getting it to restore correctly.

          • dk0r

            I don’t know where you were or who you talked to but there have been no reports on freenodes #verizons3 of lost/corrupted imei’s when flashing STOCK roms.

            It appears you are mistaken on this point.

    • rossguy

      There is now a solution on XDA to backup your IMEI / MEID / EFS in case they get wiped. http://forum.xda-developers.com/showthread.php?t=1791291 If they do, you can restore and be good to go. I too have been nervous to flash because of this issue. However, with the ability to back these up, I am going to go for it as soon as I have time. These devs are awesome!!

  • Buckoman

    Quick question – is the AOKP based off of ICS or JB?

  • G8orDroid

    Since when has CVPCS been working on kexec? I thought it was Kholk,
    [MBM] ,Hashcode and others. Guess I’m out of the loop.

    • He is just referring to CVPCS laying it all out for verizon sgs3 a week ago or so

  • CVPCS did amazing work for the development of the Droid X, which also had a locked bootloader. This guy is awesome!

  • Daniel Marchena

    You should mention that CM10 is JB whereas AOKP is not as of that build 🙂

  • Please put the warning of IMEI wiping happening.. play with at own risk

  • I’m on CM10 and it is sick how good it’s working.

    • KleenDroid

      Jellybean is awesome….

    • I can’t even guess at why anyone would downvote someone who is thrilled their phone with a locked bootloader is running a custom rom (seemingly) without issues.

      I’ve been running CM10 on my VZW GS3 all weekend (flashed 7/3 from the link below this morning with no issues):


  • SomeDooD123

    Awesome news! Locked bootloaders can suck-a-dick.