Develop Bugs

[CWM Scripts] Relatively painless backup/mod/restore scripts

Ok, these are specifically for MIUI, but they can easily be adapted to any other rom by editing the shell scripts. I'll explain how they work and it should be fairly apparent how one would need to modify for their particular rom/needs. Don't know if anyone will actually use these, but I thought I'd share. I also think it's a really good example of how CWM can be used for more than just flashing stuff.
So I've been running MIUI for a while now and I'm really happy. One little issue that popped up was every Friday when the rom was updated, the OTA update app icon gained a little "1" badge, indicating an update was available. While it's nice to be notified of the update, I occasionally didn't have the time or interest in updating so the little badge remained. I put that app in a folder, but then the folder had the little 1 badge. After a while, I started deleting the update app after install since I could always download and install updates through ROM Manager just as easily. Then I started deleting the update app from the downloaded ROM zip, along with several other apps I didn't want (Facebook, Twitter, the MIUI FileExplorer, etc) before flashing it. But this entailed downloading the Friday update on my phone, transferring it to my desktop, opening the zip in 7 Zip, deleting the unwanted files, uploading it back to my phone and then flashing. Quite a PITA.
Another issue I ran into was that the built-in MIUI backup app failed to backup my SMS/MMS messages. Actually, I don't know if it was failing to back them up, or failing to properly restore them, but at the end of the day, it wouldn't keep my text messages. I know I could avoid this by just installing each update over the current ROM, but I've always believed cleanly installing an OS helps avoid issues. I prefer to wipe everything, install clean and then restore my data.
So, the solution(s) I came up with was to mod the downloaded ROM zip file right on the phone, and manually backup and restore my data. While it took a little while to get set up, I find it actually works considerably faster and smoother than using MIUI's backup/restore app. I now have 3 simple shell scripts that are run through Clockwork Recovery just like installing any zip - one to mod the ROM after downloading, and two to backup and restore my data. Here they are:
MIUI-Mod.zip
This contains a shell script and a zip binary to handle the adding and deleting of files to/from the downloaded rom zip. When run through CWM, it copies zip and the script to /tmp and runs the script. Because the ROM zip is named differently every Friday, I figured the easiest solution was just to rename it manually. So, this script assumes the ROM zip is named "miui.zip" and is located in the root of the SD card. It's a simply matter to download the ROM on Friday, move it to /sdcard and rename it miui.zip. Here's what the script does in 2 commands:
/tmp/zip -d /sdcard/miui.zip /data/app/Twitter.apk /data/app/Facebook.apk /system/app/Email.apk /system/app/FileExplorer.apk /system/app/Gmail.apk /system/app/MIUI.us_Forums_1.1.2_AdSupported.apk /system/app/Superuser.apk /system/app/Updater.apk /system/app/MIUIStats.apk /system/media/lockscreen/* /system/media/wallpaper/*
/tmp/zip /sdcard/miui.zip /system/app/Gmail.apk
Click to expand...
Click to collapse
The first line simply opens the zip and deletes the listed files: Twitter, Facebook, Email, etc. It also removes all the wallpapers for the lock and main screens (I don't use them, so I didn't want them, but it's a good example of the use of wildcards like *).
The second line adds in the Gmail.apk from my current ROM. The latest versions of the Gmail app included in MIUI lock the mail database, which conflicts with a widget I use, so I just replace it with an older version. Every time I run the script, it removes the included Gmail app and adds in my current one. If you didn't want to add anything to the ROM, you could just delete this line entirely.
Data-Backup.zip
This just runs a shell script that creates a tar file in the root of your sdcard containing the listed files and directories. Tar files retain file permissions and owner information, so everything can be restored seamlessly. Here's how it works, it's pretty simple:
tar -c -f sdcard/backup.tar data/app/com.adobe.flashplayer-1.apk data/data/com.adobe.flashplayer data/app/com.speedsoftware.rootexplorer-1.apk data/data/com.speedsoftware.rootexplorer data/app/com.touchtype.swiftkey-1.apk data/data/com.touchtype.swiftkey data/data/com.android.browser data/data/com.android.deskclock data/data/com.android.launcher data/data/com.android.mms data/data/com.android.phone data/data/com.android.providers.contacts data/data/com.android.providers.settings data/data/com.android.providers.telephony data/data/com.android.providers.userdictionary data/data/com.android.thememanager data/data/com.android.vending data/data/com.google.android.gsf data/data/com.miui.camera data/data/com.miui.notes data/data/com.noshufou.android.su data/system data/misc/wifi
Click to expand...
Click to collapse
This creates the tar file and includes Adobe's Flash player and it's data, Root Explorer and it's data, and SwiftKey and it's data (I paired it down to just these three for this example). After that, it backs up a bunch of other data directories which include the current Browser settings, alarms, launcher settings and home screen layouts including widgets, phone logs, the current theme settings, any MIUI notes, current Wifi connections and, yes, SMS and MMS messages.
Obviously, you'd want to add in your specific apps and data directories. Sure, it takes a little work to set this up, but as I said, backing up is very quick and easy afterwards.
Data-Restore.zip
This just runs a shell script that restores all the files from the backup.tar on your SD card:
tar -xf /sdcard/backup.tar
Click to expand...
Click to collapse
Doesn't need much explanation.
So, the process is:
1-Download the Friday update through ROM Manager, move it to the root of my SD card and rename it to miui.zip
2-Reboot into CWM and run Backup-Data.zip to back up my apps and data
3-Run MIUI-Mod.zip to modify the downloaded MIUI rom
4-Wipe everything (cache/data/system)
5-Install the modded MIUI rom
6-Run Data-Restore to restore apps/data
7-Reboot
It's literally about 5 minutes after downloading the ROM and I'm updated and rebooted with a CLEAN os install and all my apps, data and settings intact, my home screen layouts, keyboard, wallpapers, wifi settings and everything retained.
Some notes:
1-Before running these in CWM, you have to make sure you have system, data and sdcard mounted since the scripts will be reading and/or writing to all of these. When you first reboot to CWM, just go to mounts and manually mount each one. The scripts could certainly be set up to mount them automatically, but mount points vary from phone to phone, and it's not difficult to mount through CWM. Also, after flashing a ROM, the ROM install script may unmount some of these, so before you restore your data, you might have to manually remount.
2-If you're adding anything from your current ROM to the zip (like how I add in my current Gmail.apk), make sure you wipe everything *after* running the mod script, otherwise you're deleting everything and then trying to copy file(s) that were just deleted.
3-I would highly recommend using Notepad++ to edit scripts, since it properly saves Unix line breaks.
4-as always, use at your own risk and a full CWM backup is highly recommended before messing with these.
That's pretty much it. Again, it does take a little while to get set up, but once it is, it's really simple. If you install a new app between updates, you just have to edit the backup script, or you can just keep the scripts maintaining a base setup and reinstall various apps through the market each time. This specific process is probably most useful for ROMs that are updated regularly - nightly or weekly, although I'm sure people can find other uses for running scripts through CWM.
Hope someone might find these useful.

This is really cool. I run Miui and would really like to be able to do a fresh install each week, but hate the hassle of resetting up my phone, even using Titanium backup, it's still a time consuming process. So needless to say, I flash the new rom over top of the old version without wiping just to save time.
So, basically I can open up the data restore zip in 7 zip, add in a few of my apps/data such as Tasker and so forth, close it and flash? If so, that will be great.
Thanks for sharing this!!!

You don't need to touch the Data-Restore.zip, all that does is extract the backup.tar file created with the backup script. What you'd do is open the Data-Backup.zip and edit the backup file (it's just a text file). Add in any of your apps and their corresponding data directories and when you flash the Data-Backup.zip in CWM, it'll back up those files/folders.
To find the files you want to backup, use something like Root Explorer and look in /data/app. There you'll find all the 3rd party apps you've installed. Add each one to the tar command in the backup file just like the ones I included. Then go into /data/data and find each app you want to back up's corresponding data folder. Add them to the tar command too.
Save the file, re-zip it and when you flash it through CWM, it'll back up the new files.

Just what i wanted
I also always install everything from clean system so setting up everything is a pain.
Would this work for Internal storage? I have a Motorola RAZR XT910 and running JBX roms.
Google does install all the apps when i sign in into the new rom but then i always had to move each folder to the correct destination manually using some file explorer. was thinking of making something like this but didnt know how to start. Thanks, I will now try and mod these to suit my phone :good:

[23/09/12][Scripts][CM10] App Mover Suite 0.5 (low /data space fix)

WITH THE NEW CM10 PARTITION LAYOUT THIS SET OF SCRIPTS HAS NO USE ANYMORE, USE IT ONLY IF YOU KNOW WHAT YOU ARE DOING AND YOU ARE SURE YOU NEED THIS.
WHY?
Many people have complained that the new Cyanogenmod 10 partition layout reserved too little space for user application and their data. While I don't find this to be a great deal (having 100+ installed apps usually means many of them are not even used) the solution to the problem is pretty simple, so I've created this tool suite.
FAQ
WHAT DOES THOSE SCRIPTS DO?
Automatic Edition
0.4 AppMover Enabler.zip
When you flash this file if necessary your apk files will be moved to system and a new script will be put in addon.d, this will backup and restore automatically your apps every time you update your rom
This require the rom support, you can check it out HERE if your rom support this function.
0.4 AppMover Disabler.zip
This file will revert everything disabling the automatic backup and restore system and moving apps back to /data. If there is not enough space in /data the script will exit with an error without removing anything.
Developer Edition
0.3dDeveloperEdition.zip
This file contains a modified updater-script and a shell script so that when installing a rom patched with them it will move, backup and restore apks files according to necessity: if the apps are already been moved to /system it will backup them, update the rom and restore the apps; if the apps are still in /data it will update the rom and then move the apps to /system/user_app
Compact Edition
AppToggler.zip
This files moves /data/app to /system/user_app or moves them back to /data/app if you already activated this. If there is not enough space to move the files the script just revert back to a safe condition. You can check the results of the operation in /sdcard/AppMover.txt.
Since the apk files are written only during application installation/updates this should have little to none performance impact while freeing about 70% of the space in /data.
You should use this script just once to move your apk files to the bigger, slower /system partition. Use it again if you want to move them back to the faster /data partition
BackupAndRestore.zip
This files create a backup of /system/user_app to /sdcard/AppBackup.tar. If /system/user_app doesn't exists but there is /sdcard/AppBackup.tar the script assumes you have just updated your rom and restores the backup.
You should use this script before and after every rom update since the CM10 update script formats the /system partition wich now contains your apk files
Normal Edition (Discontinued)
AppMover.zip
This script moves /data/app (the folder where downloaded apk are stored) to a new directory in system (/system/user_app) and then create a symlink to that directory.
AppReverter.zip
This script moves back app to /data/app and deletes /system/user_app.
WARNING: Flash this file only if you are sure there is enough space in /data for all the apps! If not you will end with a full /data partition (and relative forcecloses) and you will lose some apps
AppBackup.zip
This script will backup all your app files in an archive in /sdcard
WARNING: Make sure you have enough space in /sdcard for all your apps.
AppRestore.zip
This script will restore the apps from the archive in /sdcard
HOW TO USE:
Automatic Edition
If you want to move your apps to /system just flash AppMover Enabler.zip, this will take care of moving the apk files and preserve them during rom updates
WARNING: During rom updates ensure you have enough space in /emmc and/or /sdcard for the backup of your apk files, if not you will lose all your apps. Ensure your rom is supported (you can check it here). Consider that rom updates will now take longer, even 3 or 4 times what it used to be depending on how many apps you have installed.
If you want to move your apps back to /data flash AppMover Disabler.zip, this will also disable the backup and restore function. If there is not enough space in /data the script will exit with an error before doing anything.
Developer Edition
Replace the rom files with the one in the archive and then flash the rom normally. Make sure you have backupapps.sh in the root of the rom archive and that updater-script is correctly replaced in /META-INF/com/google/android
Compact Edition
To move your apps to /system you have to flash AppToggler.zip. This should be the first and only time you flash this file since now the fix is applied to a directory level. Newer apps will be installed directly to /system/user_app.
BEFORE flashing/updating your rom you will have to run BackupAndRestore.zip and AFTER flashing the rom you will have to run BackupAndRestore.zip again, not doing so will remove all the apps from your phone since at every update /system dir gets formatted.
If you want to move back all your apps to /data you can just flash AppToggler.zip again.
Normal Edition (Discontinued)
To move your apps to /system you have to flash AppMover.zip. This should be the first and only time you flash this file since now the fix is applied to a directory level. Newer apps will be installed directly to /system/user_app.
BEFORE flashing/updating your rom you will have to run AppBackup.zip and AFTER flashing the rom you will have to run AppRestore.zip, not doing so will remove all the apps from your phone since at every update /system dir gets formatted. Note that AppBackup.zip and AppRestore.zip will work both with /system/user_app and with /data/app, so you can use this two file for backup and restore apps (but not their data) in any rom/occasion.
If you want to move back all your apps to /data you can flash AppRevert.zip
If you done everything good and you get a bootloop try to fix permissions in CWR
If the phone works fine but reboots when you try to install new application it is probably because the OS can't write on /system/user_app for some reason.
Try those steps and report if any of those solves the problem:
Open the terminal or use adb shell and type
Code:
su
mount -o rw,remount /system
and/or
Code:
su
chmod 0777 /data/app
chown 1000:1000 /data/app
In alternative you can try this:
feroxxx said:
[...]
i have problem with reboot issue but solved it wipe cache,dalvik,fix permission and remove google play app's update.no reboot now.
[...]
Click to expand...
Click to collapse
Try to keep in mind that this scripts completely moves /data/app to /system partition. This normally is not a problem, however if you flash something in CWR that needs to read/write something in /data/app (like fixing permissions) make sure to mount /system partition manually
This script should have little to no impact on your rom performance but you may notice some performance loss installing/updating apps.
You may use this script in your rom (integrating the backup/restore into the installation script of a rom would make life simpler for everyone) or improve it, I just ask you to give me some credit.
DISCLAIMER:
This script may contain bugs and is far from perfect. Read instruction twice and make a full nandroid backup before flashing anything, since human errors could be pretty devastating. Anyhow in case of problems I will try to help and improve the scripts but I won't be responsible for any damage to your phone or data, including -but not limited- to: bootloops, app or data loss, alien invasion and thermonuclear war.
==================================================
DOWNLOAD LINK
==================================================​
CHANGELOG:
23th September 2012
V 0.5 (All versions) - Updated init.d script, renamed again as S99SystemApps to make it work on devil kernel. Now the script renames init.d scripts that doesn't start with S#. Is still possible that some scripts get executed after mine, but should be pretty rare.
V 0.5 Automatic Edition - Modified so that in case of problems the phone will reboot before deleting anything, thanks to Silentbob999 for the idea.
19th September 2012
V 0.4.2 Compact Edition - Fixed a typoes in AppToggler and BackupAndRestore.
V 0.4.2 Automatic Edition - Fixed the error you get if you try to flash the Enabler this just after formatting data (didn't test it, but it should work).
V 0.4.1 Init.d Updater - Published a flashabile file to update the init.d script so that you can use the updated one without having to toggle apps or extract it manually from the archive.
V 0.4.1 Compact Edition - Little update to AppToggler so that even if exits on error it still updates the init.d script
V 0.4.1 (All Versions) - Updated init.d script, added some fixes for problem no norma user should ever experience
17th September 2012
V 0.4 Automatic Edition - Automatic version published
V 0.4 Developer and Compact Edition - Renamed /etc/init.d/S99SystemApps in /etc/init.d/z99SystemApps, this will make less likely that some script gets executed after it and sets back /system to read only
14th September 2012
V 0.3.2 (both) - Hotfix, looks like the hotfix applied to init.d did the trick, same correction applied to remaining scripts
13th September 2012
V 0.3.1 (both) - Hotfix, seems that on some phones /system is mounted as read only. Modified init.d script to remount /system in RW if needed
V 0.3 developer edition - Almost rewritten from scratch, now there should be no problems if flashing from gingerbread and if any problem occurs the script should stop before deleting anything. Completely rewritten log system. Temporary apk backup will now be placed in /data /emmc or /sdcard, according to where there is enough space. Added file in init.d that helps preventing corruptions, hopefully system reboots when new applications are installed are gone.
V 0.3 compact edition - Added a lot of space checks. The backup is now saved on /emmc, if there is not enough space there is saved on /sdcard. If there is not enough space anywhere script will now exit with error. Completely rewritten log system. Added file in init.d that helps preventing corruptions, hopefully system reboots when new applications are installed are gone.
Normal Edition - Dropped unless I get enough requests to work on it, is almost equivalent to the compact version and having to work and test 3 version instead of 2 is just time consuming.
5th September 2012
V 0.2.5 developer edition - New version to replace CM10 stock update script, intended to be used by developers in their rom
30th August 2012
V 0.1c compact edition - Initial compact edition Release
V 0.2.5 - Fixed the error where app folder was restored in /system/user_app for good
25th August 2012
V 0.2 - Fixed an error in AppBackup.zip that could lead to follow recursively the symlink of the app directory (again and again and again..)
22th August 2012
V 0.1 - Initial Release

Sounds good. Thanks.
It would be better if we can choose the apps to be removed. Thus an app is needed, I think.

what's the difference with titanium backup?

dongfangri said:
Sounds good. Thanks.
It would be better if we can choose the apps to be removed. Thus an app is needed, I think.
Click to expand...
Click to collapse
You are right, but yhea... without an app would be pretty hard to setup the script. Maybe I could make so that moving apps with root explorer to another dir will trigger a script in init.d to create the symlink, but I think it doesn't make much sense since the performance loss of apk on /system is near to 0 (CM9 and all the rom before that had apks on the partition we now use for /system)
forziere said:
what's the difference with titanium backup?
Click to expand...
Click to collapse
It's not intended to be a backing up tool (even if at some degree works for app backup/restore) but just to move ALL apks in /system where there is a lot of unused free space. You can do it pretty easily by hand if you know some basic linux commands but is still more complex/time consuming than using an automated script like this

Hey, thanks, it's that I was loonking for, works great on MIUIV4 Jelly Bean by Andy Thomson !

Great idea
If i will flash the cm10, i will use your scripts

It's a great idea, but then the app work very well from system/user_app?

esticbo said:
It's a great idea, but then the app work very well from system/user_app?
Click to expand...
Click to collapse
I've published this set of scripts also to get some feedback. Personally I can't find any problem nor performance differences (except the fact that before I had 40mb free in /data and now there are 300) between having apk in /data or in /system but I guess different people with different phones may have different perceptions and results.
By the way my phone is pretty old and it lagged a lot before Pawitp introduced the new memory layout, so I guess I have the old, slower, memory. Fact is I read somewhere (on the CM10 thread I think) that old memory is slow just in writing operations and apk files are written just during installation/update.
As soon as I get some more feedback, I will update the OP with this informations, but before this I have to know if the script can create problems or slowdowns of any sort.

This sounds like a really good idea. Does this do the equivalent of Wendigogo's script by moving the lib files to the slower partition only? Or does it move more than just the lib files?

Vertron said:
This sounds like a really good idea. Does this do the equivalent of Wendigogo's script by moving the lib files to the slower partition only? Or does it move more than just the lib files?
Click to expand...
Click to collapse
It's /data/app that is moved so it's only apks.

Updated with a bugfix to the AppBackup.zip file, if anyone is using this is way better to update

Vertron said:
This sounds like a really good idea. Does this do the equivalent of Wendigogo's script by moving the lib files to the slower partition only? Or does it move more than just the lib files?
Click to expand...
Click to collapse
It's not like "my" datafix because CM move all /data to the speedy partition (and increase its size to 420Mo).
I've made something equivalent on my phone to move apk (on /data/app) to the /system partition. And I brake my CM when upgrading it cause installation process format /system and I forgot to backup my apks.
The best solution was to create a specific /data partition and use the speedy partition for /datadata (as in CM9/7) but pawitp's don't want to do that cause the partition layout will be SGS specific and CM is NOT an SGS rom...
For now this is the best solution ( do you backup users:groups a specific rights for each app?).
Bad news for those having lots of big apps...
Envoyé depuis mon GT-I9000 avec Tapatalk

Wendigogo said:
It's not like "my" datafix because CM move all /data to the speedy partition (and increase its size to 420Mo).
I've made something equivalent on my phone to move apk (on /data/app) to the /system partition. And I brake my CM when upgrading it cause installation process format /system and I forgot to backup my apks.
The best solution was to create a specific /data partition and use the speedy partition for /datadata (as in CM9/7) but pawitp's don't want to do that cause the partition layout will be SGS specific and CM is NOT an SGS rom...
For now this is the best solution ( do you backup users:groups a specific rights for each app?).
Bad news for those having lots of big apps...
Envoyé depuis mon GT-I9000 avec Tapatalk
Click to expand...
Click to collapse
DerTeufel1980 is using a different partition for his Helly Bean rom that has a /data and /datadata partition, so your datafix script should work for his rom at least.
Hopefully other roms will use DerTeufel1980's layout instead as they don't have the same limitations as CM10.

Happy to report this fix has been working perfectly for me on CM10. Thanks so much!

Kino87 said:
WHY?
Many people have complained that the new Cyanogenmod 10 partition layout reserved too little space for user application and their data. While I don't find this to be a great deal (having 100+ installed apps usually means many of them are not even used) the solution to the problem is pretty simple, so I've created this tool suite.
WHAT DOES THOSE SCRIPTS DO?
AppMover.zip
This script moves /data/app (the folder where downloaded apk are stored) to a new directory in system (/system/user_app) and then create a symlink to that directory.
AppReverter.zip
This script moves back app to /data/app and deletes /system/user_app.
WARNING: Flash this file only if you are sure there is enough space in /data for all the apps! If not you will end with a full /data partition (and relative forcecloses) and you will lose some apps
AppBackup.zip
This script will backup all your app files in an archive in /sdcard
WARNING: Make sure you have enough space in /sdcard for all your apps.
AppRestore.zip
This script will restore the apps from the archive in /sdcard
HOW TO USE:
To move your apps to /system you have to flash AppMover.zip. This should be the first and only time you flash this file since now the fix is applied to a directory level. Newer apps will be installed directly to /system/user_app.
BEFORE flashing/updating your rom you will have to run AppBackup.zip and AFTER flashing the rom you will have to run AppRestore.zip, not doing so will remove all the apps from your phone since at every update /system dir gets formatted. Note that AppBackup.zip and AppRestore.zip will work both with /system/user_app and with /data/app, so you can use this two file for backup and restore apps (but not their data) in any rom/occasion.
If you want to move back all your apps to /data you can flash AppRevert.zip
If you done everything good and you get a bootloop try to fix permissions in CWR
This script should have little to no impact on your rom performance but you may notice some performance loss installing/updating apps.
You may use this script in your rom (integrating the backup/restore into the installation script of a rom would make life simpler for everyone) or improve it, I just ask you to give me some credit.
DISCLAIMER:
This script may contain bugs and is far from perfect. Read instruction twice and make a full nandroid backup before flashing anything, since human errors could be pretty devastating. Anyhow in case of problems I will try to help and improve the scripts but I won't be responsible for any damage to your phone or data, including -but not limited- to: bootloops, app or data loss, alien invasion and thermonuclear war.
==================================================
DOWNLOAD LINK
==================================================​
CHANGELOG:
V 0.2 - Fixed an error in AppBackup.zip that could lead to follow recursively the symlink of the app directory (again and again and again..)
V 0.1 - Initial Release
Click to expand...
Click to collapse
Errors found in AppRestore.zip. The script moves the fold /data/app into /system/user_app. It should be all apks in /data/app, isn't it?

zhuzf said:
Errors found in AppRestore.zip. The script moves the fold /data/app into /system/user_app. It should be all apks in /data/app, isn't it?
Click to expand...
Click to collapse
Depends, AppRestore.zip is used to restore the backup created with AppBackup.zip.
AppBackup.zip creates a .tar file that includes the path from the root (so if you have your apps in /data/app you will have those two directorys in the .tar, otherwise you will have /system/user_app). At the restore time the .tar is simply extracted to the root.
Maybe you are confusing AppRestore (used to restore backups) with AppRevert (used to move back apps in /data/app), but still... it does what it should do (I think).
Soon I will release a 0.3 version that aggregate AppMover and AppReverter in a single package that toggles the place where apps are stored and aggregate AppBackup and AppRestore so that if it finds /system/user_app it will create a backup and if it doesn't find it it will restore it (bringing down the number of zips from 4 to 2, but the operations you have to do remains the same). Less chances to human errors and more to script bugs, so if something happens you can blame it on me
Right now I'm thinking to a complete rework with a couple of alternatives since I think this suite is a little bit impractical:
- create something that changes the partition layout splitting /system in a 512mb partition for /system and a 1536mb partition for /data/app... Still I'd prefear to find some alternative since this solution could create pretty big problems if something goes wrong and it won't have native support in the roms/kernels (wich means you would still have to flash a file every time you update the rom to tell it how to manage the partitions and I'm not really shure what would happen when the CM updater script tries to format system and it finds is smaller than intendend, so it may be impossible to do).
- Create an alternative update script that replaces the one in the CM10 zip and does what I wrote above (you would have to modify the CM10 zip every time, but it would be as simple as drag and drop one file in it).
- As alternative to the the repartitioning create an image file of an ext4 partition and mount it runtime (like we did with One Click Lagfix a couple of years ago). It should be easy to customize the zip so that you can chose where to create this file and how big it has be so that you can place it in /system but also in /sdcard or in /emmc. Still... you will have to flash something that teaches how to handle it to the rom every time you update it and if you put in /system you will still have to backup and restore it every damn time (so I guess is pretty useless).
To be honest I don't think that altering the partition layout without official support in the rom is a practical solution since I think negative aspects are way bigger than positive ones but I still think this solution is quite annoying if you update your rom often as I do, so if anyone has suggestions they are welcome.
By the way while I can see the actual rom partitioning has some serius limitations but I understand the reasons behind Pawitp decisions and I hope we won't get different partition layouts on different roms (that will just be a mess e we will end up with different version of kernels ad patches.. We need no more fragmentation than we already have with our device being 2 years old and having roms starting from 2.1 to the actual 4.1.1)

Kino87 said:
- create something that changes the partition layout splitting /system in a 512mb partition for /system and a 1536mb partition for /data/app... Still I'd prefear to find some alternative since this solution could create pretty big problems if something goes wrong and it won't have native support in the roms/kernels (wich means you would still have to flash a file every time you update the rom to tell it how to manage the partitions and I'm not really shure what would happen when the CM updater script tries to format system and it finds is smaller than intendend, so it may be impossible to do).
- Create an alternative update script that replaces the one in the CM10 zip and does what I wrote above (you would have to modify the CM10 zip every time, but it would be as simple as drag and drop one file in it)
Click to expand...
Click to collapse
That looks like the best solution imo. Changing the update script on each rom before you update it. I assume this will work on all roms, not just CM10?
I assume that will make the partition layout similar to DerTeufel1980's new layout?

I thought of a hopefully good idea that would allow you to update nightly roms. If it is possible and someone is willing to develop it.
For this to work you'll have to create an ext4 partition on an external sdcard of about 700mb.
Basically there will be 4 scripts, 1 of them to move /data/app to /system/app with a symlink. One for simply moving it back to /data/app if wanted. Then the other 2 scripts is to move /app to the sdcard partition when you want to update a nightly.
So my idea is; you install the rom for the first time, then run the 1st script to move /data/app to /system/app.
If you want to update the rom. Run a second script which moves /system/app to the external sdcard partition. Then flash the nightly rom as normal. Then install a 3rd script which moves /app from the external sdcard partition back to system/app.
The 4th script is to simply move everything back to /data/app if wanted.
The only downside to this is losing some space from your external sdcard. But it's worth it imo for having alot more storage space and having the ability to update nightly roms.
Do you think this is a feasible idea, or will updating the rom break the symlink?

Vertron said:
I thought of a hopefully good idea that would allow you to update nightly roms. If it is possible and someone is willing to develop it.
For this to work you'll have to create an ext4 partition on an external sdcard of about 700mb.
Basically there will be 4 scripts, 1 of them to move /data/app to /system/app with a symlink. One for simply moving it back to /data/app if wanted. Then the other 2 scripts is to move /app to the sdcard partition when you want to update a nightly.
So my idea is; you install the rom for the first time, then run the 1st script to move /data/app to /system/app.
If you want to update the rom. Run a second script which moves /system/app to the external sdcard partition. Then flash the nightly rom as normal. Then install a 3rd script which moves /app from the external sdcard partition back to system/app.
The 4th script is to simply move everything back to /data/app if wanted.
The only downside to this is losing some space from your external sdcard. But it's worth it imo for having alot more storage space and having the ability to update nightly roms.
Do you think this is a feasible idea, or will updating the rom break the symlink?
Click to expand...
Click to collapse
This is how it works already.. well.. almost.
The Backup and Restore scripts do exactly what you want to do on an external partition (the only difference is that they don't copy the apk on an ext4 partition but they store them in a tar archive on /sdcard that preserve users and permissions regardless of the filesystem in use).
Would make a little more sense to use directly an ext4 partition on the sdcard or external sdcard since it would avoid you the trouble to backup your apps every time you update the rom (but then you will still have to flash a file at every update that tells to mount this external partition) but even then... I'm not fond of altering the partition layout at all even if doing it on /sdcard or /emmc would make it pretty easy to restore in case of problems.
By the way: I've finished the compact version of the suite (0.1c) and fixed a couple of bugs in the old version. Is actually online BUT IS NOT TESTED IN ANY WAY. Don't use it until I update the OP and even then do a nandroid backup before using it, it may be pretty buggy.
Hopefully if there are no bugs in a couple of hours of test I will report back

If your apps are backed up by using AppBackup.zip and you flash a updated rom, do you have to flash AppRestore.zip before the device boots with the new rom or can you let it boot then turn it off and run the script in recovery after?

MicroG working

Got MicroG working on XA Nougat. I can't give a very clear guide, since it was all trial and error for me, but here's what I did:
- Patched framework.jar, (attached below), required to use MicroG.
- Made a backup of my rom, then deleted 10 folders from /system/priv-app, (after copying them to a temp directory): GmsCore, GoogleBackupTransport, GoogleExtServices, GoogleFeedback, GoogleLoginService, GoogleOneTimeInitializer, GooglePackageInstaller, GooglePartnerSetup, GoogleServicesFramework, and Phonesky.
- Factory reset, and flashed MicroG unofficial installer by @ale5000, (linked below). Phone didn't boot, (not surprised).
- Gradually added back some of the folders until the phone booted. I found out that the phone wouldn't boot without these 3: GoogleBackupTransport, GoogleExtServices, and GooglePackageInstaller.
- After I got the phone to boot, I found that I was stuck at "adding some finishing touches", after going through the setup screens, so I deleted SetupWizard folder.
- After rebooting, I got to home screen, but SystemUI was messed up, (no lock screen, no quick settings, etc.), so I did another data wipe/factory reset, then rebooted, and everything good now.
So, theoretically, with patched framework jar, you should be able to delete those 8 folders, (the 7 Google folders in priv-app, and Setup Wizard), then flash MicroG installer, and factory reset, and be good to go. I'm going to test more and see if there's a way to get rid of the remaining 3 files, since I wonder if they might defeat the purpose of having MicroG, (if they do the same background data/tracking-type stuff that the other Google apps do)...
MicroG installer - https://forum.xda-developers.com/android/development/microg-unofficial-installer-t3432360

@levone1: Did you notice that microG unofficial installer already delete GApps (not everything but the things that most likely conflict)?
About background data/tracking-type stuff of 3 files I don't know since they aren't open source.
---------- Post added at 17:52 ---------- Previous post was at 17:33 ----------
Also deleting the Setup Wizard may cause unwanted side effects.
I'm not sure about all ROMs but in some ROMs some things doesn't get inizialized and you have less options in the ROM menu and possible other problems.

ale5000 said:
@levone1: Did you notice that microG unofficial installer already delete GApps (not everything but the things that most likely conflict)?
About background data/tracking-type stuff of 3 files I don't know since they aren't open source.
---------- Post added at 17:52 ---------- Previous post was at 17:33 ----------
Also deleting the Setup Wizard may cause unwanted side effects.
I'm not sure about all ROMs but in some ROMs some things doesn't get inizialized and you have less options in the ROM menu and possible other problems.
Click to expand...
Click to collapse
Thanks. I don't know much, just experimenting. I decided to manually delete, because I remember it not working when I tried to flash over stock on another Xperia, but didn't try on this one. I would be fine with keeping Setup Wizard, but I couldn't get past the 'few more things' part. Any ideas?

Have you tried this?
- Flashing ROM
- Applying signature spoofing patch (when the phone is inside recovery)
- Flashing microG unofficial installer
- Wipe cache, dalvik/ART cache, data, internal memory
- Restart phone
This procedure should be foolproof (almost).
The first start of the phone will be really long since it have to recreate the dalvik/ART cache.
PS: If there are other problems at boot please post a logcat.

About the 3 apk GoogleBackupTransport, GoogleExtServices, and GooglePackageInstaller:
- GoogleBackupTransport, generally you can remove this so I'm not sure (maybe try to disable backup in the settings first)
- GooglePackageInstaller, you cannot remove this because it replace the standard PackageInstaller and removing GooglePackageInstaller don't restore the original one
- GoogleExtServices, I don't know about this

[ROM][NN][7.1.2]CyanogenMod 14.1 (UNOFFICIAL) (EOL)

CM14.1 For Galaxy Wonder​
THIS RELEASE IS THE FIRST AND LAST RELEASE, No more builds or development for this device. RIP
What's working:
Audio
Wifi
Adoptable sdcard
Doze
Receiving and making calls
SMS
GPS
Compass
Proximity sensor
Bluetooth
USB mass storage
HW accelerated GUI
HW accelerated video
Camera
Torch
Wifi/USB tethering
USB OTG (Requires external power source)
Vsync
Hybrid ION/PMEM
What's not working/Buggy Functions:
Mobile Data
720p recording
CM-14.1 Install Guide
Note: CM for Galaxy W is provided with no warranty. You are installing this software at your own risk. You may be violating your warranty.
NB! All CM builds from 2014-12-23 and after requires a new recovery! Read info further down.
Download CM-14.1 and gapps package and put in /sdcard
Download recovery: recovery-clockwork-6.0.5.1-ancora.zip
Flash it in old recovery. Then go to "advanced" menu, and select reboot recovery. When new recovery has loaded, select wipe data/factory reset, then go to "mounts and storage" menu and select format /system. Then select "format /data and /data/media" (NB. only needed the first time installing the rom). Now you should make sure you have put the rom file on an external sd card. Install that and gapps the normal way. You can also use adb sideload.
The change of partition layout is done because CM14.1 requires it, and implementing the same in CM12,CM11 make it easier for everyone to switch between them, since the same recovery can be used. For more info on the new layout, see here: https://github.com/arco/android_devi...a878aa294f168d
Another benefit is that it's now possible to install the full gapps package.
Download Section:
CM-14.1-UNOFFICIAL-EOL Download Link: http://www.mediafire.com/file/huqs206snuib325/lineage-14.1-20170603-UNOFFICIAL-ancora-EOL.zip
* First and Last release
***Please Do not mirror the links!
Note: Build date is old. İ will release new build with upstream synced ASAP
Google Apps (UPGRADE REQUIRED)
PA GApps
Micro Modular recommended
Before you install CM-14.1: Preparation (First three are optional. If you want to start fresh, these can be skipped)
Install AppBak from Market, run it and save a list of all your apps.
Install SMS Backup and Restore from Market, run it and backup your SMS history.
Install Call Logs Backup and Restore from Market, run it and backup your call log history.
Boot into CWM5 recovery. Make a full backup. You will need this backup later if you decide to go back to your previous ROM and data.
WARNING: Many apps will Force Close crash if you restore data from a previous ROM.
Install
Use CWM6.
Warning: Only use this recovery to flash CM-13.0. Otherwise, you risk bricking your phone, or you might experience boot and stability issues!
-Wipe data/factory reset
Under the "mounts and storage" menu:
-Format system
-Format data and data/media
Flash update*.zip.
Flash gapps*.zip. You must flash gapps after every upgrade to CM13.0 since /system is formatted, wiping your previous add-ons.
Reboot phone.
After you setup your Google account, reinstall the three apps from Market in order to restore most of your apps, call log and SMS history.
Warning: Do not restore backup data of system apps!
If you restore a bad backup with cached settings in telephony.db in data/data/com.*.*.telephony it can break MMS.
It seems that restoring backups can also break Calendar sync.
Credits
CyanogenMod Team
Arco68
AriesVE DevConnection Team
Everyone that donated beers (Paypal link is in my profile)
Enjoy

sir mordred said:
CM14.1 For Galaxy Wonder​
THIS RELEASE IS THE FIRST AND LAST RELEASE, No more builds or development for this device. RIP
What's working:
Audio
Wifi
Adoptable sdcard
Doze
Receiving and making calls
SMS
GPS
Compass
Proximity sensor
Bluetooth
USB mass storage
HW accelerated GUI
HW accelerated video
Camera
Torch
Wifi/USB tethering
USB OTG (Requires external power source)
Vsync
Hybrid ION/PMEM
What's not working/Buggy Functions:
Mobile Data
720p recording
CM-14.1 Install Guide
Note: CM for Galaxy W is provided with no warranty. You are installing this software at your own risk. You may be violating your warranty.
NB! All CM builds from 2014-12-23 and after requires a new recovery! Read info further down.
Download CM-14.1 and gapps package and put in /sdcard
Download recovery: recovery-clockwork-6.0.5.1-ancora.zip
Flash it in old recovery. Then go to "advanced" menu, and select reboot recovery. When new recovery has loaded, select wipe data/factory reset, then go to "mounts and storage" menu and select format /system. Then select "format /data and /data/media" (NB. only needed the first time installing the rom). Now you should make sure you have put the rom file on an external sd card. Install that and gapps the normal way. You can also use adb sideload.
The change of partition layout is done because CM14.1 requires it, and implementing the same in CM12,CM11 make it easier for everyone to switch between them, since the same recovery can be used. For more info on the new layout, see here: https://github.com/arco/android_devi...a878aa294f168d
Another benefit is that it's now possible to install the full gapps package.
Download Section:
CM-14.1-UNOFFICIAL-EOL Download Link: http://www.mediafire.com/file/huqs206snuib325/lineage-14.1-20170603-UNOFFICIAL-ancora-EOL.zip
* First and Last release
***Please Do not mirror the links!
Note: Build date is old. İ will release new build with upstream synced ASAP
Google Apps (UPGRADE REQUIRED)
PA GApps
Micro Modular recommended
Before you install CM-14.1: Preparation (First three are optional. If you want to start fresh, these can be skipped)
Install AppBak from Market, run it and save a list of all your apps.
Install SMS Backup and Restore from Market, run it and backup your SMS history.
Install Call Logs Backup and Restore from Market, run it and backup your call log history.
Boot into CWM5 recovery. Make a full backup. You will need this backup later if you decide to go back to your previous ROM and data.
WARNING: Many apps will Force Close crash if you restore data from a previous ROM.
Install
Use CWM6.
Warning: Only use this recovery to flash CM-13.0. Otherwise, you risk bricking your phone, or you might experience boot and stability issues!
-Wipe data/factory reset
Under the "mounts and storage" menu:
-Format system
-Format data and data/media
Flash update*.zip.
Flash gapps*.zip. You must flash gapps after every upgrade to CM13.0 since /system is formatted, wiping your previous add-ons.
Reboot phone.
After you setup your Google account, reinstall the three apps from Market in order to restore most of your apps, call log and SMS history.
Warning: Do not restore backup data of system apps!
If you restore a bad backup with cached settings in telephony.db in data/data/com.*.*.telephony it can break MMS.
It seems that restoring backups can also break Calendar sync.
Credits
CyanogenMod Team
Arco68
AriesVE DevConnection Team
Everyone that donated beers (Paypal link is in my profile)
Enjoy
Click to expand...
Click to collapse
Amazing , i will try but please do something for mobile data [emoji25]
Inviato dal mio Mi Note 3 utilizzando Tapatalk

You really awesome bro,tqvm

very very smooth rom

when will update
can not enter the internete without mobile data can only enter with wifi
help

alp48 said:
when will update
can not enter the internete without mobile data can only enter with wifi
help
Click to expand...
Click to collapse
Is specified that don't work mobile data [emoji6]
Inviato dal mio Mi Note 3 utilizzando Tapatalk

Thanks
My bro for this great job .
Special thanks

AOSP Keyboard keeps on crashing everytime I try to do the setup. Which Gapps should I use? I used BeanGapps and OpenGapps.

Zjune said:
AOSP Keyboard keeps on crashing everytime I try to do the setup. Which Gapps should I use? I used BeanGapps and OpenGapps.
Click to expand...
Click to collapse
The solution for aosp keyboard is on the cm13 thread , in a post near the end
Inviato dal mio Mi Note 3 utilizzando Tapatalk

Thanks for your favorite
Sorry camera app doesn't work and crashed after opening app !
Can you help me ?

@Zjune, did you find a fix for the AOSP app? I tried the aosp fix in CM13 suggested by @andydj but it crashed also.

I have downloaded GBpard from the playstore and it works

Thanks for the RoM and the work you have done.
Could you please tell me if this Rom CyanogenMod 14.1 work without gapps?
Thank you

[ROM][NN][7.1.2]CyanogenMod
Sent from my W_P200CM using XDA Labs

[ROM][Unofficial][ResurrectionRemix-P-v7.0.0][manta] -> 20190208 (DISCONTINUED)

DISCONTINUED
Sorry .. due to limited time I have stopped this ROM.
Pls find the last downloads here ..
https://androidfilehost.com/?w=files&flid=289294
Thanks for understanding ..
Resurrection Remix for manta ..
RR-P-v7.0.0-20190208-manta-Unofficial.zip
Known issues:
- HWC (hardware composer) is partly broken (icons are not shown correctly and black home screen)
- NavBar is not visible - same hwc issues like above !
- Encryption seems not work - and has not been tested. -> Pls do not encrypt your data partition yet.
- NFC has been taken out - still not working.
- Camera is not working .. same problem like on Nougat. (broken HAL1 camera and unsupported HAL2 camera)
- If you set pin, pattern or password to unlock the device pls be patient - if you press "confirm" the system is freezing for a few minutes - just wait.
RR-O-v6.2.1-20181209-manta-Unofficial.zip
Known issues:
- Encryption seems not work - and has not been tested. -> Pls do not encrypt your data partition yet.
- NFC has been taken out - still not working.
- Camera is not working .. same problem like on Nougat. (broken HAL1 camera and unsupported HAL2 camera)
- If you set pin, pattern or password to unlock the device pls be patient - if you press "confirm" the system is freezing for a few minutes - just wait.
System and Cache repartitioning / Opengapps: Error 70
The current system partition is (getting) full !
You need to do repartition your system and cache partitions .. either via TWRP package or manually via shell.
It's an one time task.
But the filesystem of the system.img inside the ROM will keep always the same size .. approx. 800mb.
The filesystem does not know the "real" size of the actual partition.
In general .. If you install an image into a partition the filesystem will have the size of the image (in our case 800mb).
The free space we got thru repartitioning needs to be allocated again.
For this reason we need to enlarge/resize the filesystem after each ROM update and/or clean install.
Only the filesystem .. the partition itself will stay untouched.
The automatic enlarge/resize of the filesystem is part of the ROM installer.
For manual repartitioning have a look here:
https://forum.xda-developers.com/showpost.php?p=77759823&postcount=953
https://forum.xda-developers.com/showpost.php?p=77762148&postcount=954
For automatic repartitioning have a look here:
https://forum.xda-developers.com/showpost.php?p=77764246&postcount=957
https://forum.xda-developers.com/showpost.php?p=77770425&postcount=960
@ipdev - Thanks for your TWRP flashable repartitioning package !
Installation:
1. Boot into TWRP
2. Wipe system, cache, dalvik and data. (Not required if you upgrade from previous build)
3. Install RR-O-v6.x.x-yyyymmdd-manta-Unofficial.zip
4. install Opengapps or other Gapps package
5. install Magisk.zip
6. Reboot into system ..
- Please install Magisk.zip (17.x) yourself.
- If you had gapps installed before you don't need to install gapps again - the installer will take care.
- If you face any strange issues, pls do a factory reset via TWRP first.
SOURCES:
If you want to build your own ROM ..
https://github.com/followmsi/manifests/tree/manta-rros-lineage-16.0
https://github.com/followmsi/manifests/tree/manta-rros-lineage-15.1
Download:
https://androidfilehost.com/?w=files&flid=289294
https://drive.google.com/open?id=0By6p5AdQfavBNHkxVWhNOW5CdVk
Enjoy Resurrection Remix on your Nexus 10 ..

Finally it's own thread ..
August 2018
RR-O-v6.1.0-20180814-manta-Unofficial.zip
Changes:
- Google August 2018 Security updates
- Adjust DRM blobs
- ro.opa.eligible_device=true -> Google Assistant
- Latest LineageOS and RR changes
Enjoy

Awesome mate. You never think for abandon the old device. Thanks for your patience and dedication to the device.
Here one thing I want to know, is it first needed the lineage-xx.x-yyyyyyyy-UNOFFICIAL-manta.zip to flash on the device what you have mentioned on your first post then the RR-O-v6.1.0-20180814-manta-Unofficial.zip on the second post.??
Again appreciate your hard work Thanks so much.
Triggered from RN5pro

amitroutray said:
Awesome mate. You never think for abandon the old device. Thanks for your patience and dedication to the device.
Here one thing I want to know, is it first needed the lineage-xx.x-yyyyyyyy-UNOFFICIAL-manta.zip to flash on the device what you have mentioned on your first post then the RR-O-v6.1.0-20180814-manta-Unofficial.zip on the second post.??
Again appreciate your hard work Thanks so much.
Triggered from RN5pro
Click to expand...
Click to collapse
No .. RR is it's own ROM .. Even it's based on Lineage you don't need to install it first.
Just corrected the typo ..
3. Install RR-O-v6.x.x-yyyymmdd-manta-Unofficial.zip
Cheers

followmsi, great work, thanks.
FYI I think this latest build might be a little bigger than previous builds? I used your pico w/ the 6mb buffer, and it was still giving me the not enough space error. I tried it with latest open gapps and changing buffer to 2mb, with the same result. So I deleted some system apps like Easter egg, calculator, camera, etc., and then the pico gapps installed. Then I reinstalled the ROM to get those apps back, realizing that the ROM keeps existing gapps (thanks for mentioning it). Seems to have worked.
Giving it a test run over the next couple days. I used f2fs for data and cache, btw. Thanks again.
Edit: I got the google play services error and reinstalled like this: wipe system, install ROM, delete camera and onetimeinstall and calculator (IIRC), install latest pico open gapps w/ 6mb mod. Took a few flashes and reboots for magisk to install. Everything seems to be working now, at least everything that is supposed to work for oreo on N10. Seems pretty smooth.

Wow this is great, can I dirty flash this over the recnt nougat build? RR-N-v5.8.5-20180413-manta-Unofficial.zip

yeoldeusrename said:
followmsi, great work, thanks.
FYI I think this latest build might be a little bigger than previous builds? I used your pico w/ the 6mb buffer, and it was still giving me the not enough space error. I tried it with latest open gapps and changing buffer to 2mb, with the same result. So I deleted some system apps like Easter egg, calculator, camera, etc., and then the pico gapps installed. Then I reinstalled the ROM to get those apps back, realizing that the ROM keeps existing gapps (thanks for mentioning it). Seems to have worked.
Giving it a test run over the next couple days. I used f2fs for data and cache, btw. Thanks again.
Edit: I got the google play services error and reinstalled like this: wipe system, install ROM, delete camera and onetimeinstall and calculator (IIRC), install latest pico open gapps w/ 6mb mod. Took a few flashes and reboots for magisk to install. Everything seems to be working now, at least everything that is supposed to work for oreo on N10. Seems pretty smooth.
Click to expand...
Click to collapse
Yes .. it's actually 2 things .. gapps pico packages has been grown ... From ~105mb (may) to ~125mb (today)
As well RR made some additional changes (not part of lineage code) to optimize the compression of aapt. (.apk sizes)
I have taken out the changes now.
For next release camera will be taken out from build.
You may take gapps config file using "smallbuffer" parameter to use 2mb right away.
Or change buffer inside installer to another value.
Similar problems will happen for los-15.1 if the pico gapps size is still growing.

someguyatx said:
Wow this is great, can I dirty flash this over the recnt nougat build? RR-N-v5.8.5-20180413-manta-Unofficial.zip
Click to expand...
Click to collapse
Yes, still take backup before.
Wipe system and install ROM and pico gapps and maybe magisk.
Wipe cache and davlik and reboot into system.
Good luck !

@followmsi I am getting Error: 7 while flashing the ROM.
Triggered from RN5pro

followmsi said:
Yes, still take backup before.
Wipe system and install ROM and pico gapps and maybe magisk.
Wipe cache and davlik and reboot into system.
Good luck !
Click to expand...
Click to collapse
Thanks I will give it a try tonight. Nothing important enough to backup this is just my entertainment tablet.

amitroutray said:
@followmsi I am getting Error: 7 while flashing the ROM.
Triggered from RN5pro
Click to expand...
Click to collapse
Wipe system before rom install and get started again.. use older gapps because of space situation on system partition.

followmsi said:
Wipe system before rom install and get started again.. use older gapps because of space situation on system partition.
Click to expand...
Click to collapse
I always do a clean flash. Wiped System, Data, Delvik Cache & Cache. Downloaded the Gapps mentioned on the OP.
Triggered from my Nexus 10

amitroutray said:
I always do a clean flash. Wiped System, Data, Delvik Cache & Cache. Downloaded the Gapps mentioned on the OP.
Triggered from my Nexus 10
Click to expand...
Click to collapse
For now .. after ROM Installation and before gapps installation do mount /system in twrp - but untick read-only.
Go to system/app (priv-app) and remove the camera2 apk.
Unmount system and install mentioned gapps pico.
It's a space problem !
Will check if I can reduce system space usage a bit more ..as well reducing buffer for gapps down to 2MB.
Cheers

followmsi said:
Wipe system before rom install and get started again.. use older gapps because of space situation on system partition.
Click to expand...
Click to collapse
This process worked except I had to do this to get gapps to work
“For now .. after ROM Installation and before gapps installation do mount /system in twrp - but untick read-only.
Go to system/app (priv-app) and remove the camera2 apk.
Unmount system and install mentioned gapps pico.”
One more question do I need to install that audiojack kernel or is already in the rom?

someguyatx said:
This process worked except I had to do this to get gapps to work
“For now .. after ROM Installation and before gapps installation do mount /system in twrp - but untick read-only.
Go to system/app (priv-app) and remove the camera2 apk.
Unmount system and install mentioned gapps pico.”
One more question do I need to install that audiojack kernel or is already in the rom?
Click to expand...
Click to collapse
Audio jack kernel is part of this ROM ..
Depending on the gapps package size you may have to delete camera2.apk - to increase free space for gapps installation.

September 2018
RR-O-v6.2.0-20180909-manta-Unofficial.zip
Changes:
- Google Security updates -> September 2018
- moved shim libs to vendor
- Latest LineageOS and RR changes (update to version 6.2.0)
Enjoy

Hi !
I flashed the September version with a clean flash (full wipe). I tried to flash both "manta_open_gapps-arm-8.1-pico-20180702-UNOFFICIAL.zip" and "open_gapps-arm-8.1-pico-20180902-UNOFFICIAL.zip" from your GDrive, but after a (sucessful) flash in TWRP 3.2.0, the First time Pixel setup has Google Play services crashing in loops in anytime.
This prevents me from going further into using Gapps.
I also tried removing stuff from priv-apk in system, but I couldn't find the camera apk. I got rid of EasterEgg, but that didn't cut through.
Any help for troubleshooting ?

Don Moahskarton said:
Hi !
I flashed the September version with a clean flash (full wipe). I tried to flash both "manta_open_gapps-arm-8.1-pico-20180702-UNOFFICIAL.zip" and "open_gapps-arm-8.1-pico-20180902-UNOFFICIAL.zip" from your GDrive, but after a (sucessful) flash in TWRP 3.2.0, the First time Pixel setup has Google Play services crashing in loops in anytime.
This prevents me from going further into using Gapps.
I also tried removing stuff from priv-apk in system, but I couldn't find the camera apk. I got rid of EasterEgg, but that didn't cut through.
Any help for troubleshooting ?
Click to expand...
Click to collapse
- install latest TWRP (3.2.3)
- Wipe systen first.
- Install current ROM
- Install just one Gapps package (manta_open_gapps-arm-8.1-pico-20180702-UNOFFICIAL.zip - buffer has been reduced to fit into manta system partition)
- Wipe cache / dalvik
- Reboot system
If SetupWizard is crashing we will need logs for further troubleshooting.

Somehow it immediately worked by following closely your instructions. I must have done something wrong before then.
Thanks a lot still, and very kudos for this ROM : )

root access
Fyi it did not like addonsu 15.1 for what ever reason, it was flashed via TWRP and turned on in dev mode but never gave access .. However Magisk flashed fine from TWRP and gave root access so no problem. had to have my Adaway from XDA.