[ProTekk (OP)]

• Check out the ROM Feature list here.
  
• Check out the comprehensive FAQ by brainfire!

Newest change logs are available at the AOKP site

• Make sure you're on the latest CWM
  
  
  
  
  
  
• MAKE A NANDROID
  
  
  
  
  
  
• wipe data/factory reset in recovery
  
  
  
  
  
  
• flash ROM
  
  
  
  
  
  
• flash boot.img in fastboot (just extract the boot.img from the zip and flash)
  
  
  
  
  
• flash GApps

Find the latest releases here

Find Build 35 here


We spend countless of hours doing this for next to nothing. Posts, views, and donations encourage me, and everyone else who helps out.

Donate to me
Donate to Whitehawkx
Donate to Jonathan Grigg
Donate to Zaphod-Beeble
Donate to ProTekk

Donate to CyanogenMod

Every donation is cherished and loved.

If you'd like to help contribute by writing code, feel free to stop by IRC and talk to us!

Check out the ROM source on github. Open source, in the spirit of community kangage.

If you'd like to help with AOKP, please don't hesitate to contact me. I'd love to get as many developers in on this as possible!


Best way to help out or contact us is via IRC.

Edited by ProTekk, 10 May 2012 - 04:15 AM.

[ProTekk (OP)]

Buglist:

Bluetooth

Edited by ProTekk, 09 May 2012 - 06:11 AM.

[jmercil]

Flashing now!

[trismegistos]

i love you for that!

EDIT: am i the only one who doesn't find one s in the device list of the releases? :)

Edited by trismegistos, 08 May 2012 - 01:32 PM.

[stan]

So One S is officially on 4.0.3 now, whereas AOKP M5 is 4.0.4. is that an issue at all or can I just flash as I would any other ROM. sorry for noob question. I'm trying to help a friend. Thanks!

[ProTekk (OP)]

trismegistos, on 08 May 2012 - 01:28 PM, said:

i love you for that!

EDIT: am i the only one who doesn't find one s in the device list of the releases? :)

Look at when M5 was released. The device just became a supported device today. That's why.

stan, on 08 May 2012 - 02:20 PM, said:

So One S is officially on 4.0.3 now, whereas AOKP M5 is 4.0.4. is that an issue at all or can I just flash as I would any other ROM. sorry for noob question. I'm trying to help a friend. Thanks!

Doesn't matter. Data/factory reset in recovery, format /system, flash ROM, flash boot.img through fastboot.

[nickmv]

Things I see still broken, in case you haven't spotted them:

• Torch toggle crashes system UI
  
• Tethering doesn't work, and kills wifi til you restart (or at least I think it kills it too)

Nice quick release. Daily driver already...

[ozzie1p]

Can't for the life of me get this to boot. I've double checked md5, flashed the kernel in fast boot. It shows it's flashing fine but can't make it out of the initial boot screen. It just reboots into recovery. Just in summary I wiped data/reset and system in recovery then flashed rom, flashed extracted boot image in fastboot, then flashed gapps in recovery again and reboot.....nothin. Any ideas would be appreciated.

[ProTekk (OP)]

ozzie1p, on 08 May 2012 - 04:01 PM, said:

Can't for the life of me get this to boot. I've double checked md5, flashed the kernel in fast boot. It shows it's flashing fine but can't make it out of the initial boot screen. It just reboots into recovery. Just in summary I wiped data/reset and system in recovery then flashed rom, flashed extracted boot image in fastboot, then flashed gapps in recovery again and reboot.....nothin. Any ideas would be appreciated.

fastboot flash boot boot.img

[ProTekk (OP)]

Updated