Database Users

[ROM][ASUS HC3.1][27-06][Kernel: angel] PRIMEE p8-3

Originally i ported PRIMEv1.4 by Roach2010, an honeycomb 3.1 rom from Asus to Iconia A500..Its now a more Acer specific rom based on acer drivers and software but with 3.1 features. We are still waiting for the kernel source, so limits of a stock kernel apply, which is one, using the new feature PS3 controller joypad's. Until source is out, these functions are missing.
You can also follow updates on Twitter now: Dexter Picard (DexterPicard) on Twitter or
me a Red bull, and you're sure i stay up working on this mod or you can visit my new homepage at Dexter's mods
Kernel source of "angel" is found here
BRIEF HOWTO
Download AcerRecoveryInstaller from Market or from apps section of A500 here. or use the old solution from this post .
Boot into ClockWorkRecovery (POWER ON + VOL-) and do a full backup.
put PRIMEE v1.4 zip on your sdcard and install using ClockWorkRecovery
NEW USERS - do a factory reset (WIPE) in ClockWorkMod when installing for the first time.
What does this rom offer
99% of all the new 3.1 features including;
Google Video (i think it was 3.1 only)
Google Books (i think it was 3.1 only)
Google VideoEditor
Asus Book Reader
Enhanced exchange support
Faster Browser
resizable widgets (new launcher 3.1)
multilanguage
enhanced task manager
added filesystem tweaks (kernel 2.6.36.3 features)
added 3G Huawei dongle support
added international keyboard layout support
SIP supported & SMS supported
enhanced network driver
root'd + superuser.apk included
DLNA support
Latest updates (P8-patch3)
[*] 2.6.36.4 kernel with CIFS/NFS/3G support. Optional OC upto 1700Mhz.
[*] Now with PS3 controller support
[*] A Splashtop HD fix here in this attachment
[*] Asus book reader app fix.
added SMS functionality with 3G, and enable SIP phone over wifi function, use SMS app from Market(handcent sms) with mobile part.
rearranged boot image parameters a little.
Media scanner both see internal & external directories now perfectly.
disabled adb at bootup, so Internal storage shows on windows ( through Portable devices - A500)
GoogleVideos app added (tested and working from USA)
Changed boot.img, so "am,install" etc works from adb again.
Added AcerSync (Request)
Replaced Asus Camera with Acer Camera (Request)
changes to mounted ext4 filesystems (small optimization)
Wifi fix added for EU users to build.prop "ro.wifi.country=EU"
Full fix for storage locations: Now its simple /mnt/sdcard , /mnt/external_sd , /mnt/usb_storage
bootanimation update .. Thanks to boggio95
Dock station + remote controller fix
LetsGolf included in full image , i just had to
Settings -> Battery stats is now included
[Bugs confirmed]
rotation lock key does not work (it serves no function in Asus firmware)
Don't mess with! (NOW YOU ARE WARNED!)
Disabling Phone+TelephonyProvider can cause unstable OS, settings crash, tablet freeze etc..
Removing apps from system folder can cause bootloop's
[PRIMEE_p8-3.zip] (patch goes on top of above existing full p8 image)
MD5: 4a48c21b4dc6cbfd6d074105318c88c4
[PRIMEE_acerA500-p8.zip]
MD5: 4efd9fcfdbe918c8ac696467a05a0ae7
See post #2 for installation and all other guides
You do all this and you take the risk. But remember if you got the CWM working, you should be safe and you can run itsmagic from CWM if you are in doubt. I take no responsibilites if you damage or brick your device. But if you do think its bricked, and you get checksum errors both at boot and recovery, sc2k might be able to help if you saved your UID number.

The GUIDES!!
INSTALL RECOVERY.IMG with ITSMAGIC (proceed at your own risk) Recommended is to follow original guide
Alternatively, a new easy installer solution for adding the new recovery.img see AcerRecoveryInstaller from Market.
0. Please read the guide below to get your UID ( see How to get the USB serial number for more info)
1. Extract the recovery.zip and copy the contents, recovery.img, to your a500. normally /data/local is a sure location to write it to.
2. so copy using adb like this
adb push recovery.img /data/local
adb push itsmagic /data/local
3. open adb shell
4. execute commands
su -
chmod 755 /data/local/itsmagic
/data/local/itsmagic
5. if the itsmagic works, you see the "done" information etc... BUT if its not working, don't do the commands below...try and figure out why its not working.
6. IMPORTANT - if all is ok, continue with the commands to remove any chance of corrupting recovery.
mount -orw,remount /system
rm /system/etc/install-recovery.sh
(this command can fail ie. not found (its ok if it does))
mount -oro,remount /system
6a. Next these commands below will install the new recovery.
cat /dev/block/mmcblk0p1 >/data/local/oldrecovery.img
chmod 777 /data/local/oldrecovery.img
cat /data/local/recovery.img >/dev/block/mmcblk0p1
/data/local/itsmagic
sync
Copy the /data/local/oldrecovery.img to your pc.
Execute this command on your pc.
adb pull /data/local/oldrecovery.img oldrecovery.img
1. with adb you can restore the "oldrecovery.img" like this
adb push oldrecovery.img /data/local
adb push itsmagic /data/local
2. open adb shell
3. execute commands
su -
chmod 755 /data/local/itsmagic
/data/local/itsmagic
5. confirm itsmagic works.
6 if all is ok, continue with the commands
cat /data/local/oldrecovery.img >/dev/block/mmcblk0p1
/data/local/itsmagic
sync
INSTALL CUSTOMROM GUIDE (proceed at your own risk)
make sure you validate the MD5SUM of the rom zipfile if possible for you, to ensure file is ok, or manually extract content on pc/mac/windows to verify zipfile is ok.
copy the PRIMEEv14_acerA500.zip to your sdcard, if md5sum / zip file is ok.
run the recovery (POWER off tablet.. then press and hold POWER button and hold VOL- until text in upper left corner appear and stop pressing VOL-)
use ClockWorkMod as normal (assumed is you tried cwm before) and wipe data/cache areas.
install zip file sdcard, and select the PRIMEEv14_acerA500.zip, and chose YES to install.
wait for installation to finish, and then choose reboot now
the zip file contains itsmagic and will execute at finish, so a reboot should run fine and boot your new custom rom.
How to get the USB serial number:
1. Connect Iconia to your PC
2.a Linux
call lsusb -v
read the value of iSerial for Iconia
2.b Windows
- Open Device manager
- Goto Properties of Android USB Devices->Acer Composite ADB Interface
- Goto "Details" Tab
- Select "Parent" from the property selection.
- Read the value. It looks like this:
USB\VID_0502&PID_3325\370014740c00594
- The number after the last "/" is the UID.
2.c Windows (alternative method)
Download this tool (download link is nearly at the end of the page):
- Open the tool
- Sort after VendorID
- Check all devices with VendorID = 0502 and ProductID = 3325 . There is also a "Serial Number" column.
Backup all of your partitions on your iconia A500
Connect Iconia to your PC or open a terminal on your tablet. make sure you got a sdcard inserted to with at least 1GB free space
if you are on stock rom, location of sdcard is /mnt/external_sd , if you are already on 3.1 its /data/Removable/MicroSD, put that into first step below, where i wrote you should.
so execute the commands below, and you got a full backup of your device..Remember to execute the "itsmagic" command, if you restore this backup.
BACKUP COMMANDS
export SDCARD=[YOUR SDCARD LOCATION] (ie. SDCARD=/mnt/external_sd)
cat /dev/block/mmcblk0p1 >$SDCARD/mybackup_mmcblk0p1
cat /dev/block/mmcblk0p2 >$SDCARD/mybackup_mmcblk0p2
cat /dev/block/mmcblk0p3 >$SDCARD/mybackup_mmcblk0p3
cat /dev/block/mmcblk0p5 >$SDCARD/mybackup_mmcblk0p5
cat /dev/block/mmcblk0p6 >$SDCARD/mybackup_mmcblk0p6
cat /dev/block/mmcblk0p7 >$SDCARD/mybackup_mmcblk0p7
RESTORING FILES
If you want to restore the files, open the CWM recovery you installed and log in with adb.
make sure all partitions are unmounted. execute the commands in the adb here.
make a copy of the "itsmagic" application to your sdcard location as well.
RESTORE COMMANDS
mount /sdcard
export SDCARD=/sdcard
cat $SDCARD/mmcblk0p1 >/dev/block/mmcblk0p1
cat $SDCARD/mmcblk0p2 >/dev/block/mmcblk0p2
cat $SDCARD/mmcblk0p3 >/dev/block/mmcblk0p3
cat $SDCARD/mmcblk0p5 >/dev/block/mmcblk0p5
cat $SDCARD/mmcblk0p6 >/dev/block/mmcblk0p6
cat $SDCARD/mmcblk0p7 >/dev/block/mmcblk0p7
mount /system
copy $SDCARD/itsmagic /system/bin/
chmod 755 /system/bin/itsmagic
/system/bin/itsmagic

Wow! very prompt progress to custom rom. Thanks dexter!
Is that the recovery you included the CWM?
Can I understand that the recovery.img should be flashed using itsmagic method. After that, we get a custom recovery (CWM) to restore your update.zip.
And your update.zip will not contain anything that would alter the kernel such that you will not run itsmagic again in your update.zip. Am I correct? Thanks.

ardatdat said:
And your update.zip will not contain anything that would alter the kernel such that you will not run itsmagic again in your update.zip. Am I correct? Thanks.
Click to expand...
Click to collapse
my update.zip WILL install a custom boot.img , as HC3.1 uses a different boot, so its unavoidable..
but i have included itsmagic in the zip, and when the "system" is unpacked, it leaves it unmounted until itsmagic has run, so the libraries are available to execute the application which is done at the end in the updater-script.
I have tested it and it works and installs the new boot with this recovery.img (this image got busybox in /sbin which is important)
sorry, little tech, but required to explain how i did it.

So exciting cant wait to try this out tomorrow

Oh YEAH! Was still hoping for this coz customROMs came to other devices with locked bootloader too!
Now its here!
Will definetly try this when i have time this afternoon

OMG so greaaaaat, thanks pal!!!
edit: downloading

dexter, can you make a guide for newbie to install this rom ? or may be any one?

Working great so far. Quite stable.

interqd said:
dexter, can you make a guide for newbie to install this rom ? or may be any one?
Click to expand...
Click to collapse
Soon, i will do even better.. ill dig up an old application used on FlipOut to install a recovery.. this app will then install the recovery.img and run the "itsmagic" application. but that for later.
but here is my way of seeing it simple, if you can use adb and a shell in a rooted a500.
See post #1 for the GUIDE(s)

Dexter_nlb said:
Soon, i will do even better.. ill dig up an old application used on FlipOut to install a recovery.. this app will then install the recovery.img and run the "itsmagic" application. but that for later.
but here is my way of seeing it simple, if you can use adb and a shell in a rooted a500.
See post #1 for the GUIDE(s)
Click to expand...
Click to collapse
I got a itsmagic: not found
when I try to execute :S i dont understand why, is there a permission to be set or something?
on itsmagic post just say "call itsmagic" but bunno what this mean its a command? just #itsmagic?
thanks in advance
EDIT:
I think this need to be posted on OP
2. so copy using adb like this
adb push recovery.img /data/local
adb push itsmagic /data/local
3. open adb shell
4. execute commands
cd /data/local
su -
chmod 755 itsmagic
./itsmagic
Click to expand...
Click to collapse

Alejandrissimo said:
I got a itsmagic: not found
Click to expand...
Click to collapse
thanks.. i updated post #1.

Boot perfectly!!!! thanks a TON for your work!!!!
btw, this recovery its 100% functional? for custom.zip files and stuff?

Can root explorer and terminal emulator be used to execute the above commands from the device or is adb the only option?
Sent from my A500 using XDA Premium App

bochocinco23 said:
Can root explorer and terminal emulator be used to execute the above commands from the device or is adb the only option?
Sent from my A500 using XDA Premium App
Click to expand...
Click to collapse
I think yes, you can use terminal emulator

Any impressions so far?

huxflux2003 said:
Any impressions so far?
Click to expand...
Click to collapse
marvelous just want to figureout how play videos everything else its a lot of smooth (youtube HD works)

It plays YouTube videos fine...

Alejandrissimo said:
marvelous just want to figureout how play videos everything else its a lot of smooth
Click to expand...
Click to collapse
what about install moboplayer?
even 3rd party cant play videos?
and, does usb host is functioning?
keyboard, mouse, gamepad, hdd, td, etc
3.1 should have them to run by default right ?

Language support
Hi, does your ROM supports all languages like Android 3.1, or did you remove e.g. Czech language?
Anyway, sounds great, I will try it today.

[Guide][NOOB-Friendly] How to share your Nandroid Backup and Modem

As we are having a lot of Jelly Bean leaks lately, a lot of users want to share the Nandroid backup to others but sometimes they make mistakes which ends up in md5 mismatches or some of them don't know how to create a share-able zip.
I have tried to create this guide to enable them in doing so. Hope this will help everyone.
Requirement:
CWM Recovery
7zip, Winrar or any file compressing tool
ADB setup in your PC
Click to expand...
Click to collapse
Once you have applied the OTA and done a factory reset, Follow the process given below:-
If your have ClockworkMod Touch Recovery 6.0.1.2 (Believe me it is easier and better in Touch recovery - Get it from here) follow these:-
In CWM Recovery
Reboot into Recovery => Hold Volume Up + Home + Power buttons together for about 5-7 seconds, release the buttons when you see the recovery menu
Choose -> Backup and Restore
Chooose -> Choose Backup Format (Optional)
Change Backup format to tar (Optional)
Choose -> Create image.zip
This will create an image.zip and an image folder in your Internal Sdcard inside the clockworkmod>backup folder
Copy the image.zip file to your PC, rename it to the software version you are sharing for e.g. GT-I9300-XXXXXXXX. Important do not put spaces in the name.
Upload this zip to whichever Filehosting site you want to share with.
*this image.zip can be flashed in CWM directly without having the need to extract the files inside*
Click to expand...
Click to collapse
If you have ClockworkMod Recovery 5.5 (Get it from here) Follow these:-
In CWM Recovery
Reboot into Recovery => Hold Volume Up + Home + Power buttons together for about 5-7 seconds, release the buttons when you see the recovery menu
Choose -> Backup and Restore
Choose -> Backup (either Internal or External SDcard by default it will backup to ExtSDcar)
Your Backup will now be there inside the clockworkmod>backup folder, Copy this folder to your PC
Zip the Folder and give it a name for e.g. GT-I9300-XXXXXX (Dont use spaces)
Now you can upload this zip to any filehosting service of your choice
Click to expand...
Click to collapse
How to extract the modem:-
For extracting the modem you need to be rooted (If you are not or want to know how go here)
Using ADB (Go here if you want to know how to set up ADB)
Connect your phone to you PC (Please ensure that ADB debugging option is checked in Developer Options)
Type
Code:
adb devices
You will get something like this:
Code:
List of devices attached
XXXXXXXXXXXXXX device
It shows your device is connected via ADB
Type
Code:
adb shell
You will get a output like this:
Code:
C:\adb>adb shell
[email protected]:/ $
Type
Code:
su
You will get:
Code:
su
[email protected]:/ #
(Those who are using Terminal Emulator can start from this step)
Type
Code:
dd if=/dev/block/mmcblk0p7 of=/sdcard/modem.bin bs=4096
You will get
Code:
[email protected]:/ # dd if=/dev/block/mmcblk0p7 of=/sdcard/modem.bin bs=4096
dd if=/dev/block/mmcblk0p7 of=/sdcard/modem.bin bs=4096
8192+0 records in
8192+0 records out
33554432 bytes transferred in 2.892 secs (11602500 bytes/sec)
[email protected]:/ #
Your modem.bin file is copied to the root of your sdcard, copy it to your PC and upload it to the file hosting site of your choice
Click to expand...
Click to collapse
I have tried to write everything to the best of my knowledge. If anyone feels that I have missed something or I have written something wrong please let me know. I will make the changes.

Thanx for this very useful
Sent from my GT-I9300 using Tapatalk 2

anurag549 said:
Thanx for this very useful
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
will be helpful for many ... nice work buddy

Q: When I dump modem I get a modem.bin and its ~30mb, while shipped modems in stock fw is ~12mb, why is this?

Perka said:
Q: When I dump modem I get a modem.bin and its ~30mb, while shipped modems in stock fw is ~12mb, why is this?
Click to expand...
Click to collapse
Well that escapes me..may be someone knowledgeable can shed some light on it..
Sorry..
Maybe the that provided with the firmware is a patch..I know OTA files are patches but can't say much about full firmwares..

I'm trying to do this using the terminal emulator in Rom toolbox and u keep getting permission denied?
(from what I understood we had two ways of doing this correct? A computer and adb or TE, correct?)

Danielhammons1 said:
I'm trying to do this using the terminal emulator in Rom toolbox and u keep getting permission denied?
(from what I understood we had two ways of doing this correct? A computer and adb or TE, correct?)
Click to expand...
Click to collapse
You have to type su in terminal to gain root access. It's just like a standard Linux terminal.

[GUIDE] Revert from ART to Dalvik if boot fails

Today I tried to enable ART on my S3 Mini running Maclaw's CM11. After the phone was shut down, the CM loading circle stayed there forever and the phone didn't boot.
To fix this you can boot the phone into recovery (I'm using CWM) and use ADB to revert the runtime back to Dalvik.
There are 3 ways to do this:
Use the following manual instructions
Download the second attachment and run the batch file, while the phone is connected using a USB cable and in recovery mode. For this you need USB drivers installed.
Download the first attachment and flash it in recovery
Manual instructions
Boot to recovery
Open the shell
Code:
adb shell
Now, while in the shell, the data filesystem must be mounted.
Code:
mount /data
Still staying in the shell, use the following command to set Dalvik as the runtime of choice.
Code:
setprop persist.sys.dalvik.vm.lib libdvm.so
Now the /data-filesystem can be unmounted using
Code:
umount /data
Type exit in the shell to exit ADB shell.
Reboot the phone and it should get past the loading circle again
If anything goes wrong, I'm not responsible

Very good idea. Thanks
I am not sure, but maybe it is possible to set property from recovery update script?
Such script, downloaded onto phone and accessible from recovery would be better, than PC with USB drivers and a cable

piskor said:
Very good idea. Thanks
I am not sure, but maybe it is possible to set property from recovery update script?
Such script, downloaded onto phone and accessible from recovery would be better, than PC with USB drivers and a cable
Click to expand...
Click to collapse
Thank you for the idea, implemented it now and added to the OP.

dextrey said:
Thank you for the idea, implemented it now and added to the OP.
Click to expand...
Click to collapse
Excellent, thanks

Updated to mount the /data filesystem directly using the fstab entry. Also changed the recovery-flashable .ZIP to use a temporary BusyBox for all commands, because I'm not completely sure about the filesystem differences between different ROMs and recoveries (the locations of binaries such as mount and umount)

Thanks!!!
Very useful!!

Thanks, this worked. I was on CM11 nightlies and read an article about ART and switched it from Dalvik, phone app crashed and wouldnt let me boot in. Although I'm using HTC One, this method worked for me.
For TWRP users, boot into recovery and go into Advanced, and then use terminal to command the type the main line to switch to Dalvik, no need to adb shell and mount data.

Fixed my HTC ONE m7 that got brinked when selecting ART.
dextrey said:
Today I tried to enable ART on my S3 Mini running Maclaw's CM11. After the phone was shut down, the CM loading circle stayed there forever and the phone didn't boot.
To fix this you can boot the phone into recovery (I'm using CWM) and use ADB to revert the runtime back to Dalvik.
There are 3 ways to do this:
Use the following manual instructions
Download the second attachment and run the batch file, while the phone is connected using a USB cable and in recovery mode. For this you need USB drivers installed.
Download the first attachment and flash it in recovery
Manual instructions
Boot to recovery
Open the shell
Code:
adb shell
Now, while in the shell, the data filesystem must be mounted.
Code:
mount /data
Still staying in the shell, use the following command to set Dalvik as the runtime of choice.
Code:
setprop persist.sys.dalvik.vm.lib libdvm.so
Now the /data-filesystem can be unmounted using
Code:
umount /data
Type exit in the shell to exit ADB shell.
Reboot the phone and it should get past the loading circle again
If anything goes wrong, I'm not responsible
Click to expand...
Click to collapse
Thank you, thank you, I'm in great debt for this.
Can recommend the method if you are running viperOne 6** on a HTC one m7 (bulletproof kernel).
NB:
My ADB was totally broken, but I wrote all commands in the TWRP terminal window, and it reverted my phone back to dalvic from ART!

How can i copy Rom zip to phone, i formatted, no rom to flash but i have recovery

I deleted Rom file in sdcard. I cant flash a rom. I have recovery, root and Philz Touch.
How can i copy Rom zip file from computer to Phone? Any idea. I have rooted KK, i dont want to do all things again.
How to: Copy ROM zip file to the freshly wiped device
I found and share with you, it worked.
Have you ever been in a situation where you mistakenly (or not) wiped the content of the internal storage (including system partition and virtual SD card) on your phone or tablet and unfortunately it doesn't support external storage? Now you can't flash desired custom ROM because you removed it and the device can't be booted due to wiped system partition. Don't worry - it's very easy to fix!
Here are the steps you need to follow to copy the correct rom.zip package to your internal storage:
Download this mini-sdk package and extract it to c:\mini-sdk
Rename the custom ROM package you want to flash to "rom.zip" and copy it to c:\mini-sdk
Connect your device to the PC
Boot your device in recovery mode
Open a command prompt on the PC (cmd.exe), type and confirm each command with ENTER:
cd /d c:\mini-sdk
adb shell
mount /data (error might mean that /data partition is already mounted)
on Android 4.2 and above: mkdir -p /data/media/0
on Android 4.1.2 and below: mkdir -p /data/media
exit
on Android 4.2 and above: adb push rom.zip /data/media/0
on Android 4.1.2 and below: adb push rom.zip /data/media
Wait for a few minutes until the file is copied. It will looks like command shell is not responding, but that means it's still copying. Wait patiently until you'll see blinking cursor again.
Depends on your custom recovery, use the navigation keys to flash the custom rom.zip package in a typical way you used to flash custom ROMs. It should be on your internal storage now. Done! http://android-revolution-hd.blogspot.com.tr/2013/12/how-to-copy-rom-zip.html

easier solution:
*bring device in recovery mode
*open cmd, go to adb.exe
*type adb.exe push *filename.zip* /sdcard/your path **/sdcard is already linked to /data/media/0
*wait after pushing the file, reboot recovery again
*choose file and flash
*** other method ***
*use the sideload function in recovery
*adb.exe sideload *rom.zip* in cmd

it says usb device descriptor failed...is it due to bad cable??
it says usb device descriptor failed...is it due to bad cable??

[GUIDE] MoFo - Image Modification Methods

MoFo - Image Modification Methods
I have been helping people with other devices to make rooted ext4 images for their devices using @btdownloads7's method here:
http://forum.xda-developers.com/showpost.php?p=60389310&postcount=177
Works great. If they have the system images as sparse chunks, you can use @tal.aloni's SparseConverter.exe found here:
http://forum.xda-developers.com/showthread.php?t=2749797
to make an ext4 single image system.img but you have to use a hex editor to remove the header and the footer following tal.aloni's instructions in the thread, which I summarized here:
http://forum.xda-developers.com/showpost.php?p=61130622&postcount=41
Then you can use btdownloads7's method above to root it.
The problem is that for some devices like the XT1058 there was only the fxz available as a single file system.img, which is not an ext4 file. I don't know how to convert it to an ext4 image but I have an unlocked XT1060 and at least for the XT1058 what I found I could do was flash the XT1058 system.img to my XT1060 using mfastboot, then boot into recovery and go to Mount and check System. Then from an adb shell run the mount command. That told me where the system image was. On the XT1060 it was /dev/block/mmcblk0p38. Then from the adb shell I ran the command:
dd if=dev/block/mmcblk0p38 of=/sdcard/new_image.img
where if = input file, of = output file and dd is a command that copies the data in the input file to the output file.
Then I exited the adb shell and ran the command
adb pull /sdcard/new_image.img
to get the new_image.img on my computer. new_image.img is an ext4 file that you can flash using mfastboot if your bootloader is unlocked or mofo.exe if your bootloader is locked.
Since my XT1060's bootloader is unlocked and the XT1058 image boots on the XT1060, I could mod the XT1058 image while running android - install Xposed, busy box, etc. - then boot into recovery and run the commands above. I am sure I can also install a custom ROM in TWRP and then pull the image. The point being that for the XT1058 and the non-Dev Ed XT1060's,, which have locked bootloaders, I can modify the images using this method. My XT1060 won't work as a phone running an XT1058 image, but I can use wifi to connect to the playstore to download apps and then install them.
So, I was hoping that this would work the same for the XT1095 and our XT1096 devices. I can boot the Pure Edition XT1095 ext4 image fine on my XT1096 after flashing it with mofo.exe (although it won't make calls) so I think the XT1096 image would run on the XT1095. If someone has an XT1095, they should be able to make a nandroid of their sytem, do all of that above, add in whatever we want to the XT1096 image while running it, then boot into recovery, do the steps above and pull it as an ext4 file using adb, then restore their phone using the nandroid.
To summarize the method:
1) Make a nandroid of XT1095;
2) Use mfastboot to flash XT1096 system.img to XT1095;
3) Boot into TWRP recovery, wipe cache and data partitions, adb push SuperSU zip to /sdcard, install SuperSU zip and then boot into system;
4) Enable USB Debugging, add in Xposed, CFLumen, etc. while running Android and reboot as necessary;
5) Boot into Recovery;
6) Open an adb shell and type the command mount to determine where /system is in /dev/block;
7) Run the command dd if=dev/block/correctplace of=/sdcard/new_image.img, where correctplace is wherever /system is in /dev/block;
8) Exit adb shell and run command adb pull /sdcard/new_image.img; and
9) Restore the XT1095 to its previous state using the nandroid backup.
new_image.img would be an XT1096 rooted ext4 mofo.exe flashable file with Xposed, CFLumen, etc. baked in. In step #1, I would also copy the nandroid to my computer so that I would have a backup copy in case anything strange happened. It shouldn't but it is always better to be safe.
Note that my qe converts to 2/1 when I flash a different model's image but it returns to 1/1 once I reflash an XT1096 image.

How To Make an Ext4 Image from a Single File System.img
Requires an Android device of the same model as the system.img is for with an unlocked bootloader and TWRP installed as the custom recovery.
1) Flash the system.img using mfastboot;
2) Boot into TWRP, start an adb shell and run the command mount - note what folder /system is in /dev/block;
3) From the adb shell run the command:
dd if=dev/block/correctplace of=/sdcard/new_image.img
where correctplace is the folder you noted in Step #2.
4) Exit the adb shell and run the command
adb pull /sdcard/new_image.img
to get the new_image.img onto your computer. new_image.img is an ext4 file that you can flash using mfastboot if your bootloader is unlocked or mofo.exe if your bootloader is locked.

How To Make an Ext4 Image From Sparse Chunks
If you have the sparse chunks for your model - i.e., system.img_sparsechunk1, etc. - then you can use SparseConverter.exe to make a single file ext4 system.img that is flashable by mfastboot and mofo.exe:
http://forum.xda-developers.com/showthread.php?t=2749797
The command is:
SparseConverter.exe /decompress C:\system.img_sparsechunk1 C:\system.img
And it is run from the directory where SparseConverter.exe is. Of course, if your sparse chunks aren't in c:\ you would put in the path to where they are in the command above. And sometimes the first sparse chunk is not sparsechunk1 but rather sparsechunk0 and if so, of course you would start with sparsechunk0.
The system.img you make using SparseConverter.exe will have a header and a footer in it that need to be removed before the system.img is flashable by mfastboot and mofo.exe. The instructions for how to do that are here.

How to Root an Ext4 Image - Requires a Bootloader Unlocked Android Device With TWRP
Requires an Android device with an unlocked bootloader and TWRP installed as the custom recovery. Originally posted here.
btdownloads7 said:
Yes, but there was a slight change in the process (at least on the Nexus 7) from they way I described it originally. Since the image is huge, and wouldn't fit onto the system partition of the Nexus 7, i couldn't just flash it as a system image from fastboot. Here's what I ened up doing:
1. Make sure that you have at least 6 GB free on the SD card, and boot into TWRP
2. Copy the clean ext4 image file to the SD card (the links are a few pages back in this thread)
3. Create a "supersu" folder on the SD card
4. Download the SuperSU update zip (the current version is 2.46)
5. Extract the "armv7" and "common" folders from the update zip to the "supersu" folder from Step 3.
6. Extract the "update-script" binary from the attached zip, and copy it to the same "supersu" folder. It's a script from tha update binary that I modified for our purposes.
7. In TWRP gui, wipe the system partition (this may not have been necessary, but I did it just in case)
8. In TWRP gui, unmount the system partition from the TWRP menus
9. open ADB shell
10. run "rm -r /system", and disregard any errors that it gives you. This will clear the mount point for our image
11. run "mkdir /system", and ignore any errors it gives you
12. run "mount -t ext4 -o loop /sdcard/system.img /system"
13. run "chmod +x /sdcard/supersu/update-script"
14 run "cd /sdcard/supersu" followed by "./update-script". You might see some errors when it's running, but you can disregard them
15. In ADB shell, run "mount", and that should list all the partitions. Remember which path is for the system partition (on my end it was "/dev/block/loop0")
16. run "dd if=dev/block/loop0 of=/sdcard/new_image.img". Obviously replace "/dev/block/loop0" with whatever you got in the previous step
And thats it. Copy the new image back to your PC, and you're ready to flash it with mofo
Click to expand...
Click to collapse

General Info On Modding Images Using Linux
@Ekkoria's tutorial here provides general information on how to mod images using linux.
@ClydeDroid - can you give a synopsis of what needs to be done to add a symlink for the AdAway hosts files? I would like to add it to this thread. Thanks!

Adding Free WiFi Tether to a System Image
To add free WiFi tether to a system image, the /system/build.prop file needs to be edited to include the following line:
net.tethering.noprovisioning=true
The line can be added anywhere in the build.prop file. Please note that editing the build.prop file in some instances resulted in HDR camera problems (force close when a picture was taken with HDR on). Be sure to use NotePad++ to edit the build.prop file, not another editor.

Adding Xposed for Lollipop to a System Image
Here and here are the instructions for @mikeoswego's method for installing Xposed for Lollipop in a system image.
You need to download both the apk and the zip from this thread:
http://forum.xda-developers.com/showthread.php?t=3034811
as well as the script that is attached to this post (unzip the script).
mikeoswego said:
1) You must mount the image that you want to install Xposed to /system on your Linux box (or edit the script some more.)
2) Make the script executable (chmod 755) and then run the script like this:
sudo [full path to script] [full path to zip file]
On my system it looks like this:
sudo /home/mike/InstallXposed /home/mike/xposed-sdk21-arm-20150430.zip
There will be some chcon errors but it still sets the permissions correctly.
3) Before you flash the image having Xposed in it to your device, download the XposedInstaller apk to your phone from the first post in this thread: http://forum.xda-developers.com/showthread.php?p=58948978#post58948978 and delete the following folders from your /data partition:
/data/dalvik-cache/arm
/data/dalvik-cache/profiles
4) On reboot, it will take a little longer at the red Verizon screen, then it will upgrade/optimize apps claiming a very large number of apps to process but most of them go by very quickly. On subsequent reboots it upgrades/optimizes one app each time. Otherwise I've not noticed any other problems or side effects.)
Click to expand...
Click to collapse

reserved 7

JulesJam said:
reserved 4
@btdownloads7 Is it possible for you to write up a synopsis of how you got Busy Box and SQLite into the image? It doesn't have to be a step by step guide, but whatever insight you could give even a high level summary would be appreciated. Thanks!
Click to expand...
Click to collapse
Sqlite is easy -- you just put the binary into /system/xbin, and chmod 755 it.
Busybox is harder. The overall process is very similar to rooting it, but you have to run most of the script in a virtual machine, and one command in TWRP. You have to get the update zip for it, extract the proper binaries for the arm7 architecture, and extract the update script. Then modify the update script to remove any mention of the mounting/dismounting of partition, and to move the the extracted binaries instead of having the script extract them. At the very end of the script, it runs a "busybox --install" command, and that has to be run on the actual device (in TWRP).

@mikeoswego - did I get the instructions correct here? I wanted to combine 2 of your posts into 1 set of instructions. Please let me know if I paraphrased you correctly, thanks!

JulesJam said:
@mikeoswego - did I get the instructions correct here? I wanted to combine 2 of your posts into 1 set of instructions. Please let me know if I paraphrased you correctly, thanks!
Click to expand...
Click to collapse
Looks good!
---------- Post added at 06:45 PM ---------- Previous post was at 06:41 PM ----------
JulesJam said:
net.tethering.noprovisioning=true
Click to expand...
Click to collapse
I'm not sure this works for carriers other than Verizon.

mikeoswego said:
I'm not sure this works for carriers other than Verizon.
Click to expand...
Click to collapse
AFAIK it works for ATT but the problem is that ATT is not subject to the Block C license restrictions so if you enable it, you still need to hide the fact that you are tethering from ATT. There are ways to modify the /system partition to do that but idk how to do it.
If you have UDP and don't tether very much, from all I have read, ATT lets it go. But if you are going to use lots of data per month tethering, they send you a letter telling you that you are violating their TOS and if you don't stop, they will take away your UDP or terminate your contract, I can't remember which. So those with UDP have to hide that they are tethering somehow.

JulesJam said:
6) Open an adb shell and type the command mount to determine where /system is in /dev/block;
7) Run the command dd if=dev/block/correctplace of=/sdcard/new_image.img, where correctplace is wherever /system is in /dev/block;
Click to expand...
Click to collapse
Just so you know, there's an easier way to do this part. The directory "/dev/block/platform/msm_sdcc.1/by-name" contains links to all the partitions so you don't have to remember weird numbers like "mmcblk0p38". The app "DiskInfo" can also show you which partitions map to which block devices, and it doesn't even need root. Hope this helps.

Mmcblk0p38 on my XT1095

btdownloads7 said:
Sqlite is easy -- you just out the binary into /system/xbin, and chmod 755 it.
Click to expand...
Click to collapse
Where do you get the binary and what is "out"?

JulesJam said:
Where do you get the binary and what is "out"?
Click to expand...
Click to collapse
I don't remember where I originally got the binary, but if you do a google search, you should be able to easily find it. Here's a good place to start.
And "out" was a typo. Should have said "put"

btdownloads7 said:
And "out" was a typo. Should have said "put"
Click to expand...
Click to collapse
I thought so but I wanted to make sure in case it was some linux command I am not familiar with, lol!

I'm trying to do something that should be very simple using the Linux method: change the boot animation. No matter what bootanimation.zip I put into /system/media, set permissions to 644 and ownership to root:root, the animation seems to default to a pulsating text "android" logo. When I also change the bootanimation file in /system/bin I only get the pre-boot Motorola logo until boot up is complete.

Pulling a MoFo Flashable Image From an XT1095
This is useful for the AT&T XT1097. You can flash modified XT1095 images to an AT&T XT1097 since they both work on AT&T. Here is how you can pull a MoFo flashable image from an XT1095.
Open an adb shell by typing adb shell at the command prompt. Then type the command su. Then run this command:
dd if=/dev/block/mmcblk0p38 of=/sdcard/system.img
Then pull the image using the adb pull command:
adb pull /sdcard/system.img c:\

joshnat said:
I'm trying to do something that should be very simple using the Linux method: change the boot animation. No matter what bootanimation.zip I put into /system/media, set permissions to 644 and ownership to root:root, the animation seems to default to a pulsating text "android" logo. When I also change the bootanimation file in /system/bin I only get the pre-boot Motorola logo until boot up is complete.
Click to expand...
Click to collapse
@mikeoswego may be able to explain to you how to do it.