yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi 2] 5ulo:
That was my try with / without image.. It's still the same

e@arch ~/aries-image-builder-master $ ./flashtool/flash.sh /home/e/aries_core_unified
DEVICES:
Bus 002 Device 038: ID 05c6:9006 Qualcomm, Inc.

Would flash to 05c6:9006(/dev/sdc) in sd mode

Continue? [y/n]: y
Programming /dev/sdc with /home/e/aries_core_unified
Traceback (most recent call last):
File "./flashtool/program.py", line 72, in <module>
do_program(sys.argv[1], sys.argv[2])
File "./flashtool/program.py", line 15, in do_program
dom = parse('out/images/rawprogram_core.xml')
File "/usr/lib/python2.7/xml/dom/minidom.py", line 1918, in parse
return expatbuilder.parse(file)
File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 922, in parse
fp = open(file, 'rb')
IOError: [Errno 2] No such file or directory: 'out/images/rawprogram_core.xml'
Patching /dev/sdc with /home/e/aries_core_unified
Traceback (most recent call last):
File "./flashtool/patch.py", line 121, in <module>
do_program(sys.argv[1], sys.argv[2])
File "./flashtool/patch.py", line 85, in do_program
dom = parse('out/images/patch0.xml')
File "/usr/lib/python2.7/xml/dom/minidom.py", line 1918, in parse
return expatbuilder.parse(file)
File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 922, in parse
fp = open(file, 'rb')
IOError: [Errno 2] No such file or directory: 'out/images/patch0.xml'
Done.
[Xiaomi Mi 2] m11kkaa:
ah it looks like I've hardcoded the path LOL

just copy the rom directory to "out" in the aries-image-builder dir so you have aries-image-builder/out/images/...
[Xiaomi Mi 2] 5ulo:
I was wondering what the out path should be :D Anyway.. this is the output

e@arch ~/aries-image-builder-master $ sudo ./flashtool/flash.sh /home/e/aries_core_unified
[sudo] password for e:
DEVICES:
Bus 002 Device 038: ID 05c6:9006 Qualcomm, Inc.

Would flash to 05c6:9006(/dev/sdc) in sd mode

Continue? [y/n]: y
Programming /dev/sdc with /home/e/aries_core_unified
103821+0 records in
103821+0 records out
53156352 bytes (53 MB) copied, 10.8393 s, 4.9 MB/s
103821+0 records in
103821+0 records out
53156352 bytes (53 MB) copied, 98.3917 s, 540 kB/s
164+1 records in
164+1 records out
84124 bytes (84 kB) copied, 0.0308909 s, 2.7 MB/s
256+1 records in
256+1 records out
131080 bytes (131 kB) copied, 0.0276654 s, 4.7 MB/s
592+1 records in
592+1 records out
303492 bytes (303 kB) copied, 0.0705037 s, 4.3 MB/s
273+1 records in
273+1 records out
139944 bytes (140 kB) copied, 3.04486 s, 46.0 kB/s
392+1 records in
392+1 records out
201136 bytes (201 kB) copied, 2.94644 s, 68.3 kB/s
2175+1 records in
2175+1 records out
1113900 bytes (1.1 MB) copied, 40.9303 s, 27.2 kB/s
23620+0 records in
23620+0 records out
12093440 bytes (12 MB) copied, 201.923 s, 59.9 kB/s
34+0 records in
34+0 records out
17408 bytes (17 kB) copied, 0.000204826 s, 85.0 MB/s
33+0 records in
33+0 records out
16896 bytes (17 kB) copied, 0.000184656 s, 91.5 MB/s
Patching /dev/sdc with /home/e/aries_core_unified
Update last partition 26 'userdata' with actual size in Primary Header.
Update last partition 26 'userdata' with actual size in Backup Header.
Update Primary Header with LastUseableLBA.
Update Backup Header with LastUseableLBA.
Update Primary Header with BackupGPT Header Location.
Update Backup Header with CurrentLBA.
Update Backup Header with Partition Array Location.
Update Primary Header with CRC of Partition Array.
Update Backup Header with CRC of Partition Array.
Zero Out Header CRC in Primary Header.
Update Primary Header with CRC of Primary Header.
Zero Out Header CRC in Backup Header.
Update Backup Header with CRC of Backup Header.
Done.

It looks all went well.. After reboot still no recovery. Only fastboot.

edit: after chatting with m11kkaa I resigned - the eMMC is faulty. It means replacing whole motherboard, which is too expensive comparing to buying used mi2 phone.

Thanks M11kkaa for your time
[Xiaomi Mi 2] madpanter:
Hello.

I have sucesfuly flashed this: aries_core_unified_single.zip and CM11. But i have now problem that i can not access internal storage via USB in windows. In telephone i see 12.97gb of internal storage (have 16gb mi2s). What can i do? If i flash aries_core_separated_single.zip the CM11 wont boot. I would like to try OMNI rom or some other because i have large battery drain on CM11 and camera is not also working.

Thanks for help
[Xiaomi Mi 2] m11kkaa:
you have to use the latest version of CM12, AOSP5 or MIUI to use merged partitions.

If you wanna use cm11, you have to revert to the old layout.
[Xiaomi Mi 2] madpanter:
Ok, but how can i doo that? If i use aries_core_separated_single.zip the CM11 will not boot (it is always in boot loop), shuld i use this aries_core_separated.zip?
[Xiaomi Mi 2] m11kkaa:
did u recreate all filesystems using TWRP and reflash your rom after changing the table?
[Xiaomi Mi 2] madpanter:
This is how i got in this mess:

When i was stil stock on MIUI V5 and dualboot i flashed this with miflash: aries_core_unified_single.zip

Then i flashed in recovery your CM12.1 but girlfriend didnt liked it because frequent reboots

I then flashed cm-11-20150906-NIGHTLY-aries.zip but did not changed anything with miflash (this is wher i got in this mess probably)

I now want to flash some other rom because the camera is not working in CM11 and huge battery drain.

Does this answers you question?

Thanks m11kkaa for your quick replys and help.
[Xiaomi Mi 2] madpanter:
I am unable to find that option in advanced wipe...
[Xiaomi Mi 2] cogano:
Wipe / Advanced / Repair or Change / and then choose Change (to the same FS as currently used).

This should format the corresponding partition.
[Xiaomi Mi 2] madpanter:
Ok i did that but still can not copy anything to the internal memory of the phone. Shuld i flash via miflas this: aries_core_separated.zip or aries_core_separated_single.zip?

If i use aries_core_separated_single.zip i get this errors in recovery:

[IMG="MI2s recovery"]http://shrani.si/f/2N/X1/4Xc5f8AE/img20151003211203.jpg[/IMG]

It seams that i made a nice paperweight out of this phone...
[Xiaomi Mi 2] SkiFire13:
aries_core_unified_single.zip -> only MIUI > 5.4.x or M1cha's CM12.1 or latest AOSP5 works (only they can see Internal Storage, that now is a virtual sd-card in /data/media/0)

aries_separated_single.zip -> other roms
[Xiaomi Mi 2] MyNameIsKappa:
Hi Mikka! I'd like to know if you ever made those flash packages to reverse engineer the new layouts. I'm with unified_single now and I'd like to go back to Xiaomi's unified partitions (no system).

Thank you for your work!
[Xiaomi Mi 2] m11kkaa:
"unified" is Xiaomis new layout. "unified_single" is Xiaomis new layout with dualboot stuff removed so you can install full gapps.
[Xiaomi Mi 2] MyNameIsKappa:
Yeah I know, but if I try to flash any other partition table I'll get error. Can you please help me?

EDIT: I solved on my own using fastboot commands and flashing MIUI7, then flashing with MiFlash unified.

Anyway, just to let you know, if you try to flash any other partition table or fastboot rom from unified_single using MiFlash it won't work and it'll give error 0x80004005. I hope you'll do something about it. Thanks
[Xiaomi Mi 2] seities:
Hello: I flashed the unified+repartition option after flashing unified core first. It seems to work, except now my internal storage shows only around 10GB. The phone is a 32GB model Mi2. Wondering where did the rest of the stroage go? I finally got to install gapp pico (minimum) so I assume dual boot partition is gone and system has more storage than before.

Hoping to get those strage back. Please help. Thanks. (I did repartition before to get more app storage, but forgot what I did. Some procedure on mi.com?)
[Xiaomi Mi 2] m11kkaa:
did you recreate all filesystems using TWRP?
[Xiaomi Mi 2] seities:
Hi: No I did not. I did just wipe these partitions by selecting them and wipe. I looked into other options and see resize, repair, and change file system for each partition. What exactly should I do for each? I did try resize for /data and it seems to have expanded to 26GB or so. I also wiped /system. Not sure what to do with the rest of the paritions, though a lot of them don't seem to exist anymore ("internal storage" became invalid, cache and system can't change size but can be wiped and repaired, dalvic cache is invalid, etc.). I just ended up resizing everything (only data could be resized), wiping everything, repairing everything, and then check to see if all of those are in ext4. Only data, cache, system can be modified at all. others don't seem to exist or shows invalid.

I tried to load up the CM12.1 ROM by plugging in the usb cable in TWRP. The device shows up but no storage is availble (no internal storage or anything shows up as available option, even after /data is expanded and formatted). How do I get the /data/media to show up in MTP mode? update:nevermind. wiped /data again and it shows up in MTP. Loading up ROM now to reflash. Should work.

Thanks for helping (a noob). Also this script is way easier than when I had to manually expand partition for Apps following a mi.com direction. It's amazing to see all these operations done in just a few seconds. I appreciate your work very much, both for this and CM12.1. Thank you!
[Xiaomi Mi 2] No-New-Phone:
I had the idea to flash ivans aosp to see wheather my bluetooth devices show up in that ROM. But trying to wipe my /data partition fails:

Updating partition details...
...done
Full SELinux support is present.
MTP enabled
E:Unable to wipe '/data' -- unknown file system 'auto'
E:Unable to format to remove encryption.
Updating partition details...
...done

In the recovery, wiping /system works fine, but wiping /data ends in a second. Flashing AOSP ends with an error: Cannot flash older image over newer image.

So what I did was executing the core_unified_single-script again. Still no luck. Phone didn't enter recovery, but I could get in fastboot mode and I flashed recovery from there. Not sure if the partition is somehow corrupt, restoring the nandroid seems to work (still running).

Not sure how to proceed. CM12.1 is running smoothly, but not very stable (soft-reboots nearly every day).
[Xiaomi Mi 2] SkiFire13:
Did you recreated all the partitons?

~ Xiaomi Redmi Note 2 Prime ~
[Xiaomi Mi 2] No-New-Phone:
No, but I don't know how to do so, as the 'format' option leads to the error.
[Xiaomi Mi 2] cogano:
[MENTION=3530648]m11kkaa[/MENTION] how about including this info in the OP? I have also spent some time trying to find out what the "original" and "new" layout means and to which ROMs it actually applies.
[Xiaomi Mi 2] m11kkaa:
Good idea. I didn't know myself which ROM's support it because I didn't use MIUI for years.
[Xiaomi Mi 2] No-New-Phone:
[quote name="wbcl" post=59907496]

you can easily check current status via adb<br />

<br />

Is there any other way of getting this information? Parted is neither present in m11kkaas cm12 nor in the actual twrp (I have tried both).

My formatting problem is described as follows:

Factory Default and Format Data both use the fstab to determine how to format the partitions. fstab is set to auto, so those functions don't know what filesystem to format the partitions as. (see http://xdaforums.com/showthread.php?p=57568995)

Solution can be to write

make_ext4fs /dev/block/mmcblk0pxx

In twrp terminal directly. Would it be correct to change xx for the partition number?
[Xiaomi Mi 2] m11kkaa:
it looks like TWRP's fdisk supports GPT now:

fdisk -l /dev/block/mmcblk0

what's meant by "recreating filesystems" is going to advances wipe options in TWRP and select "change filesystem"(u need to do it one by one for every partition)
[Xiaomi Mi 2] No-New-Phone:
Thanx. This is the output for core_unified_single:

/ # fdisk -l /dev/block/mmcblk0
I:Actual command is: 'cd "/" && fdisk -l /dev/block/mmcblk0 2>&1'
Found valid GPT with protective MBR; using GPT

Disk /dev/block/mmcblk0: 61071360 sectors, 1148M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 28 entries
First usable sector is 34, last usable sector is 61071326

Number Start (sector) End (sector) Size Code Name
1 34 348191 169M 0700 modem
2 348192 348193 1024 0700
3 348194 349217 512K 0700 sbl1
4 349218 350241 512K 0700 sbl2
5 350242 352289 1024K 0700 sbl3
6 352290 354337 1024K 0700 rpm
7 354338 356385 1024K 0700 tz
8 356386 357409 512K 0700 DDR
9 357410 365601 4096K 0700 aboot
10 365602 367649 1024K 0700 misc
11 367650 373489 2920K 0700 logo
12 373490 375049 780K 0700 m9kefs1
13 375050 376609 780K 0700 m9kefs2
14 376610 376611 1024 0700 m9kefsc
15 376612 393215 8302K 0700 bk1
16 393216 394775 780K 0700 m9kefs3
17 394776 524287 63.2M 0700 bk2
18 524288 585725 29.9M 0700 boot
19 585726 585727 1024 0700
20 585728 616447 15.0M 0700 recovery
21 616448 638975 11.0M 0700 bk3
22 638976 655359 8192K 0700 persist
23 655360 2752509 1023M 0700 system
24 2752510 2752511 1024 0700
25 2752512 3538943 384M 0700 cache
26 3538944 61071326 27.4G 0700 userdata

You have posted an layout with 27 partitions in post 21, so I guess your layout there is the "unified" (not "unified_single"), right? In the "_single" layout the partition "storage" is mounted within the "userdata" at /data/media/0".

Reformatting every partition, I still cannot install AOSP 5.5.3 (for merged partitions) from @zipalign thread. Installation aborts with errors:

Installing '/sdcard/MEGA/MEGA Downloads/aosp-aries-5.5.3-Vv1zRSVsav-5.1.0.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: Can't install this package (2015年 05月 03日 星期日 19:12:17 CST) over newer build (Sa 13. Jun 21:04:42 CEST 2015).
Can't install this package (2015年 05月 03日 星期日 19:12:17 CST) over newer build (Sa 13. Jun 21:04:42 CEST 2015).
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/MEGA/MEGA Downloads/aosp-aries-5.5.3-Vv1zRSVsav-5.1.0.zip'
Error flashing zip '/sdcard/MEGA/MEGA Downloads/aosp-aries-5.5.3-Vv1zRSVsav-5.1.0.zip'
Updating partition details...

I use the wipe for a fresh install of the 20150730-CM12.1-build.
[Xiaomi Mi 2] SkiFire13:
[MENTION=3501710]No-New-Phone[/MENTION] he has unified single because there isn't the second system

~ Xiaomi Redmi Note 2 Prime ~
[Xiaomi Mi 2] No-New-Phone:
I ran the unified single script as well, shouldn't it be the same then? [MENTION=3530648]m11kkaa[/MENTION] has the /storage in partition #27, in my case it's mounted inside #26.
[Xiaomi Mi 2] m11kkaa:
I'm sry to stop this funny debate but I'm using separated_single :)

unified_single is the best imo but I kept it so I can test backwards compatibility.
[Xiaomi Mi 2] youxiaojie:
I generated smiui 5.11.5 for mi2s but it could not be boot after flashed in by twrp 2.8.7 with merged partition, stopped in "white mi", whereas the cm 12.1 is ok in the same step. Why? any idea? I use unified flash core and partition shell script to chandge partition and install twrp. is it because i should use single and unified partition layout?
[Xiaomi Mi 2] cogano:
I had a similar problem (coming from aries_core_separated_single with CM11.2 to aries_core_unified_single for CM12.1):

TWRP / Wipe / Advanced / Change FS - ext4 did not work (it wrote "wiping data without wiping /data/media...) and the filesystem size remained small like in "_separated_" (about 3.5 GB).

Wipe / Advanced / Change FS - ext2 turned out to be a simple workaround! Then, I changed FS to ext4 again. FS size is now 27.65 GB. This is easier and safer than typing in terminal.

Then, "adb whatever" did not work due to missing authorisation, hence I used TWRP / Advanced / ADB sideload for flashing CM12.1 and opengapp-aroma packages.
[Xiaomi Mi 2] cogano:
[MENTION=3530648]m11kkaa[/MENTION] would you mind adding yet another layout to the flashtools? The one supported by Miui 5.11.19 and newer.
[Xiaomi Mi 2] steely.wing:
Help, I flash aries_core_unified_single.zip or aries_core_separated_single.zip, both of them change my bootloader back to Mi fastboot, how to change to the custom fastboot?
[Xiaomi Mi 2] m11kkaa:
Done :) (aries_core_unified_single_xiaomi.zip)

I stopped support for the custom bootloader previously included in miflash for two reasons:

1) it was from Grub4Android, and these packages should just get u back to a flashing base(correct partitiontable, recovery etc) asap.

2) Grub4Android got discontinued in advance of EFIDroid, so this UI doesn't exist anymore anyway. (it looks like this now: http://puu.sh/mfVHh/34233edaf5.jpg)
[Xiaomi Mi 2] steely.wing:
Thanks for your fast reply, I flash "aries_core_separated_single.zip" and CM11, but the native camera FC and Google Camera says no SD card, but I can see the SD card in file manager (ES / FX), before flashing "aries_core_separated_single.zip" the camera is working, how can I fix?

Edit: apps can't write to the /storage/sdcard0
[Xiaomi Mi 2] m11kkaa:
CM11 doesn't support this layout :)

you sure could get it working by modifying fstab and framework-res but I don't have exact instructions for that either.
[Xiaomi Mi 2] steely.wing:
I see :) , I try to flash back your first version of fastboot (aries_core_recovery.zip), but it says the bootloader mismatch, if I force to flash it, will it be bricked? :confused: I am trying your CM12 and bugers CM12, looks great :good:

Edit: I flash aries_core_unified_single, but SD card partition is missing (in TWRP and CM12), and I flash back "aries_core_separated_single.zip" and CM11, that works without problem :rolleyes: , very strange, after that I format the sdcard, it can't write again. :(
[Xiaomi Mi 2] cogano:
Danke!

BTW, the scripts try to flash both modem+modem1, while only one modem partition exists. It went on w/o error, though.
[Xiaomi Mi 2] steely.wing:
I finally found out why "aries_core_separated_single" sdcard cannot be access on CM11, "aries_core_separated_single" will not update the owner of the /sdcard and /vsdcard, you need to run below code in recovery's adb:

# Check the owner of sdcard and vsdcard
ls -ld /sdcard
ls -ld /vsdcard
# If the owner is not media_rw:media_rw
chown media_rw:media_rw /sdcard
chown media_rw:media_rw /vsdcard
[Xiaomi Mi 2] Exterminator13:
I've managed the problem: the cause was recovery image (see attachment, remove ".log" at the end).

I repacked it.

What was changed:

ramdisk/default.prop: ro.adb.secure=0 ro.secure=0

added parted app
[Xiaomi Mi 2] cogano:
What you could have done is to sideload any suitable ROM temporarily, boot to it and give your computer authorisation.
[Xiaomi Mi 2] gonzametal:
So I have to boot in bootloader mode, and run the "flash_partition_table_and_core". Then I will get the new partition layout, and twrp 2.8.7.0 installed. That's all? I am confused with the red warning in the first page:

"USE THIS WITH THE CUSTOM BOOTLOADER INSTALLED BY ONE OF THE CORE PACKAGES ONLY. Xiaomi's bootloader will format your whole MMC device. THIS WOULD ERASE YOUR EFS AND YOU CAN'T MAKE CALLS ANYMORE"

What does it mean???

If I want to convert filesystems to f2fs, what can I do? Is there a tutorial for this?
[Xiaomi Mi 2] cogano:
yes, it is somewhat confusing. To be safe, first flash flash_core.sh (this will give you also the custom boot loader, but it will not touch the partition layout.

Try to reboot to recovery (TWRP now) and backup EFS (I recall this version can do it already) to your computer.

Reboot to boot loader (the custom one now) again and flash the other script, which does the same as the former one, but also changes partitions (all data lost!).

BTW, I do not use F2FS.
[Xiaomi Mi 2] leo1leo2leo3:
A quick and small question: How can I check if installation of the custom bootloader was succesful? If I reboot to bootloader after flashing flash_core.bat, I end up at an identical bootloader screen as stock (the bunny repairing the android..). Does the custom bootloader have the same screen?
[Xiaomi Mi 2] m11kkaa:
yes :P

fastboot getvar supports_partition_erase

true: custom bootloader

false/not found: original bootoader
[Android Q&A, Help & Troubleshooting] sophie132:
Hi there,

Im on galaxy tab pro 12.2 Sm-t900 rooted with odin , cf-autoroot... i would like to enable fast charge command. But when i type the line in terminal emulator : $ su then # fcon (echo 1 > /sys/kernel/fast_charge/force_fast_charge) (copied in system/bin) it fail cos it can't create :sys/kernel/fast_charge/force_fast_charge. I did change the fcon permission to 755, but i think i need to flash my kernel. And i dont know how.. thank you for the help.
[G 2014 Q&A, Help & Troubleshooting] endless98:
I am a big noob when it comes to this. I flashed the xposed installer zip file and now my phone says that my memory is full.

I have 9 gb internal storage free and 5 gb external.

HELP ME PLEASE!
[G 2014 Q&A, Help & Troubleshooting] Imperious Rooster:
You have to wipe dalvic / cache from recovery and then it will be fixed.
[Xperia Z1 Android Development] OmarEinea:
.

.

.

.

​

AICP​

Android Ice Cold Project​

AICP is known by everyone as Ice Cold Project that started on Desire HD and since then evolved into a mature ROM with the BEST community you can find!!!

Until Lollipop, Rom has always been AOKP based. Unfortunately, since AOKP either stopped development or will make a comeback later this year, we changed our base to CM when it comes to hardware, drivers and some features.

If there are any bugs, either we will sort them or CM team if it concerns their modifications. This rom isn't CM supported so no need to report errors or bugs to them!!

.

.

.

.

.

​

In the beginning we would like to thank:

CM team

maxwen

Thoemy

SlimBean rom team

CarbonRom team

LiquidSmooth rom team

Omni rom team

DU team

teemodk

audahadi

Community

​

@LorD ClockaN

@zipsnet

@n3ocort3x

@semdoc

@eyosen

@alienmind

@Chezbel

@Drgravy

@eboye

​

We are now paying for servers that build nightlies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.

Thank you!!

​

​

OFFICIAL AICP NIGHTLY BUILDS

For GAPPS use PA's or SLIM's [recommended]

Stable Release [Not Available YET]

​

A file named "aicp_honami_lp-8.0-NIGHTLY-20150xxx.zip.html" under every build contains full changelog.

​

Don't disable Heads-Up. You wont be able to answer phone calls otherwise.

Minor bugs, same as CM, Mainly:

Some issues while Adaptive brightness is enabled

Ambient display isn't working

You tell... :P

​

ROMS should contain everything you need to enjoy Lollipop. You are not required to install any Add Ons, simply download the latest ROM, gapps, flash it, and go!

You are STRONGLY recommended to fully wipe your device before flashing, and if possible avoid restoring system apps and system data with Titanium Backup - these can cause stability issues that are very hard to debug. If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience strange behavior.

How to flash:

Download the latest build & Gapps

Take a nandroid backup

Recommended - Full wipe and factory reset

Flash ROM & Gapps using latest TWRP recovery

Reboot & Enjoy!

KERNEL:

Kernel in this rom follows SlimRoms source.

PREREQUISITE FOR OTA:

To be able to flash over OTA app, TWRP recovery is needed.

You can still use CWM and OTA app, but only to download zip file and flash it manually from within recovery. Zip gets saved under AICP_ota folder on your internal SDcard.

If you want to contribute to the AICP or wanna see what is being worked on/merge feel free to visit our gerrit, link is at the bottom!!!

​

IceColdJelly AICP G+ community

kernel github

rom gerrit

You want to see a normal night at the DEV office, click here!!

XDA:DevDB Information

AICP Lollipop - Honami, ROM for the Sony Xperia Z1

Contributors

OmarEinea

Source Code: https://github.com/AICP

ROM OS Version: 5.1.x Lollipop

ROM Kernel: Linux 3.4.x

ROM Firmware Required: Unlocked Bootloader

Based On: CyanogenMod

Version Information

Status: Nightly

Current Beta Version: NIGHTLY

Created 2015-02-21

Last Updated 2015-07-08