Related
gapps-slim1.6_CM11_kk4.4.4.zip (your link to simplicity) change-log coming to post #7.
Recent changes:
Google Play 5.0.31
Google Play services 6.1.74
new Link2SD script added to avoid remounting script and reboot after gapps flash; thanks to Fiouz @ XDA for original script
edited 70-gapps.sh to set default media tones; no guarantees, seemed to work the one-time I tried it. Test it; adjust to preference.
Removed Google Calendar and corrected script to allow CM Calendar to update with nightlies, when applicable.
more script changes to hopefully make the important steps 2-4 below less important (let me know)
more suggestions at post 6
Important! (prior to flash):
1) BACKUP; if you want to skip steps 2-4 or if your encounter problems, goto recovery and wipe data, manually format system, flash CM ROM, flash gapps, restore user apps only (not any Google Apps unless they are missing; ie, Google Search. Missing apps found in Google Play store)
2) goto Manage apps/Downloaded and uninstall updates to Google Play and Google Play Services (this update places Google Play 4.9.13 and Google Play Services 6.1.09 in /system
3) launch a root browser and goto /system/addon.d and delete 70-gapps.sh and 91-cm.sh
4) it's helpful to uninstall keyboards other than the Google L development keyboard used in this gapps (use Titanium Backup or Link2SD to uninstall it); the integrated scripts will remove CM-AOSP KB (Have a preference for a different keyboard? -see post 5)
Note: Your CM Nightly updates can be downloaded and installed by the integrated CMUpdater without overfilling system. Also, gapps will be restored as flashed until 70-gapps.sh is removed or the system is manually formatted prior to ROM flash. Relax; it's auto-magically done without returning to recovery each update. More bloat is being removed -see change-log post 5
Suggested use: Flash prior to next CM11 nightly update to:
1) automatically remove CM wallpapers and AOSP keyboard with each CM11 update. Still supported but epicmtd is now a mini ROM build
2) automatically backup and restore /system gapps with each CM11 update (includes: Google Play version 5.0.31, Google Play Services 6.1.11 and Google L developer edition keyboard (with three themes in advanced settings).
(suggestions and disclaimers)
*Recommend flashing initially as clean install; scripts have been modified to flash prior to nightly but dirty flash at own risk. Subsequent updates of CM 11 nightlies can be done retaining userdata, if preferred, but do so at own risk.
**If not using with clean install on initial flash, may require manual removing of original keyboard in /data partition.
***A recommended trial of these gapps could be done prior to flashing another CM nightly. Backup first. If flashing this shows problems, the userdata may need wiping or manual cleaning prior to flashing nightly and gapps. Once in place and functioning, the /system/addons.d scripts will restore minimal gapps and Google L keyboard as well as remove the bloat each update. Therefore, you can simply use the integrated CM Updater in System settings/About phone/CyanogenMod updates to download and update without manually flashing in recovery.
****Any missing Google apps should be available in Google Play.
FYI: deleting the /system/addon.d scripts manually or manually formatting system partition will defeat the auto backup and restore of this custom gapps with bloat melt.
Advantage? Free up available system and data space occupied by infrequently used gapps or outdated ones. No manual bloat melt or modifying ro partitions required. Automatically repeats manual steps... advanced users can modify to automate most manual steps repeated in CM nightly updates. (One step I still repeat manually after each boot is to cycle location toggle.)
(hints and suggestions for advanced users)
You can add your own preferred user apps at /data/app location of .zip archive using your computer but only recommend that for clean installs. If so, use this once for dirty flashing over existing userdata, your updated custom version once for each clean install. (more after disclaimer)
*disclaimer: nightlies sometimes require clean installs due to changes; dirty flash and customize this at own risk. Always backup prior to flash in case of problems.
Within reason, I can attempt to help with in-demand changes to this. To edit for more /system app removal, look into META-INF\com\google\android\updater-script and follow the method in original to make changes take each gapps flash for clean install. You'll also need to edit /system/addon.d/91-cm.sh following that method to make same changes permanent. To add user apps for clean installs, simply download to computer, open the archive and copy your preferred user apps to /data/app folder (updater-script is already modified for permissions).
Note: for those of you that like to manually format /system prior to flashing nightlies, I've looked at the CM11 updater-script and normal format does indeed take place after backing up per addon.d scipts. For example, the CM50 script actually backs up your /system/etc/hosts and rewrites to same location after its normal system partition format. This is useful for those that use apps that modify hosts to block ads. But, formatting prior to flashing could be useful if you happen to suspect a /system/addon.d backed up script was causing you problems.
Note2: I had given up on using addon.d scripts to restore scripts like Link2SD or Xposed framework but now seem to have some scripts that work for CM Updater updates over userdata; they simply eliminate a couple of manual steps within the applications and the reboot that would follow those steps. This is a safer mod, minimizing risks using the existing user scripts rather than flashing an individual's personal script. Post 3 may contain a future update for advanced users with additional scripts for backing up and restoring Link2SD sdext2 partition remount script backup and restore during CM update as well as Xposed framework /system/bin/app_process and app_process.orig backup and restore as needed. WIP; update coming soon.
Note3:There is potential to gain more system partition space available but preferences vary. Keep in mind that scripts will only impact /system partition. A customized version would be required if advanced users wish to add user apps to /data/app like user tools and apps that load quicker in a flash rather than download or side-load apps.
Note4: I've read other CM forums and latest gapps are recommended. Looking through the changes, I agree. I will try to keep this updated, if needed.
added CM Updater support!
Thanks to CMNein and blowtorch in this thread:
[Tutorial] CM9/CM10/CM10.1 back up script along with one other source that I lost in tapatalk, got this CM Updater support working for CM11 Nightlies for both backup and restore gapps as well as melting the bloat. If anyone knows the other source, please let me know so I can thank and give credit but the script is almost identical to the one linked.
Same apps; different scripts. Flash this one to make the backup and restore proper and continual (follow the asterisk comments for conditions)
change log:
1) added appropriate support to 70-gapps.sh to backup the right gapps and keyboard when flashing new nightly without requiring flash of gapps each time(*)
2) added new 91-cm.sh script to melt the bloat each time OTA CM Nightly is flashed.
3) consequently, changes 1 & 2 now make it possible to update CM Nightlies without having to flash gapps each time(**). I came to this realization a bit late
(*)provided that system is not manually formatted (Allow the CM scripts to backup, format system and restore gapps.)
Note: to use different gapps, format system manually or delete /system/addon.d/70-gapps.sh prior to flashing new gapps)
(**)System settings/About phone/CyanogenMod updates/update types: All versions (press the nightly version for changelog; icon gives option to download, install or indicates current version installed) Limit visits to recovery:good:
In summary: you can flash this once and forget about flashing gapps again on nightlies. Works with the integrated CM Updater also (manually formatting system or deleting /system/addon.d/70-gapps.sh and 91-cm.sh will keep these changes from automatically restoring. Editing those scripts can save you time and pose less risk editing ro partition prior to boot.)
version 1.1
advanced user scripts for Link2SD and Xposed framework
gapps-SlimAdv1.2_kk-20140606-signed.zip
(Outdated; merged scripts into one release. See post #4)
refer to edited OP for advanced user discussion (spoiler or hidden text)
same gapps but added a couple of new scripts to support backup and restore of Link2SD and Xposed framework when updating CM with integrated updater while retaining userdata
changelog:
1) added 89link2sd.sh script to backup and restore user's mount script at /system/etc/init.d when updating CM
2) added 90-exposed.sh script to backup and restore /system/bin/app_process if using Xposed framework. Thanks to rovo89; script pulled from link in his OP
Note: if not using either of the above applications, just use version 1.1 referenced in previous posts.
Note2: if one of these scripts do not apply, you can open archive of zip and delete the script not needed without breaking the zip for flashing.
Disclaimer: Use at own risk; currently testing on CM Nightly 20140809.
If you've encountered CM theme or theme update install errors with Google Play since the 4.9.13 update, this gapps update may help; install and use the workaround below the changelog... if not having issues, stay with what works until a CM 4.4.4 Gapps is released.
changelog:
1) updated Google Play to 4.9.13; installs to system partition
2) removed backup/restore of /system/priv-app/GmsCore.apk in /system/addon.d/70-gapps.sh (no longer needed for CM updates)
(after next CM update, you should see a little more system partition available space)
Note: this update includes the advanced scripts 90-xposed.sh and 89link2sd.sh; open zip archive and delete from /system/addon.d if not needed (optional but not necessary; the scripts are there if ever needed for Link2SD or Xposed framework mods).
Note2: this update is only intended for those encountering update or install error in the new Google Play version 4.9.13 (don't update if not having issues; follow the workaround, if needed).
Install instructions:
If you have Google Play version 4.9.13, it's most likely on the data partition. Wipe its data in System settings/apps/Downloaded/Google Play Store and Uninstall the update.
Flash the updated Gapps. If having problems, go to System settings/apps/All and clear data to Google Play services, Google Play Store and Google Services Framework and reboot.
Workaround:
for Google Play Store install errors -24, -110: go to System settings/apps/All and clear data to Google Play services, Google Play Store and Google Services Framework and reboot.
If you encounter Google Play install install error -401 or -400, consider your CM theme may be causing this and revert back to original CM holo (Default) theme in System settings/Themes, freeze Link2SD and Link2SD Plus, go to System settings/apps/All and clear data to Google Play services, Google Play Store and Google Services Framework and reboot. After successfully installing or updating the problematic application, select desired CM theme and unfreeze Link2SD. The 400 hundred series install errors may be rare but I've notified the application developers of the issue.
Notes for Link2SD users:
1) after a CM update, launch the Link2SD application, wait for it to load and "clean up the 2nd partition" in the "more"/left tab slide-out. Don't click OK but read the details and note that you most likely need to "Link dalvik-cache" files in the "more"/left tab slide-out after each update. I've found it's important to wait until the application fully loads to check; otherwise, you may be causing more steps to get your linked files restored and keep the redundant files out of the internal memory.
2) if you have Google Play services update 5.0.89 in Downloaded tab of System settings/Apps, you no longer need the dalvik-cache file [email protected]@[email protected] (you can safely delete it when running the "clean up the 2nd partition" in the "more"/left tab slide-out (if deleting, reboot once more) . You should not see it again after updating CM with the CM updater.
gapps-Slimv1.3-_kk-20140606-updated.zip
change-log for gapps-slim1.4_CM11_kk4.4.4.zip update
Still don't see an official CM gapps for Android 4.4.4; this is an OTA update pulled from apk's pushed to my phone by Google
gapps-slim1.4_CM11_kk4.4.4.zip
Important: see OP (post 1) for update instructions; the old scripts need to be flushed and replaced. The gapps flash/updater-script should take care of that but to be sure, follow the manual steps.
Themes: some themes or theme updates pulled from Google Play WILL (if you have Link2SD installed and sdext2 partition is visible) give you an update error -401 If this happens to you, the workaround in post # 4 above still applies.
change-log:
removed cm-91.sh bloat remover script and integrated into a new 70-gapps.sh
removed more bloat; necessary for larger Google Play and Google Play Services moving to /system
want custom ring tones? look into /system/addon.d/70-gapps.sh for ideas (for those that can edit scripts)
Warning: many media tones were removed as bloat. Check your tones for correctness; if needed, I can add these back in.
Note:
there is a limited space left in system if you choose to risk adding some back in. During testing, the old method was actually maximizing system capacity before the bloat was removed. Therefore, a change to delete the bloat prior to writing/restoring the larger apps from gapps was necessary. If you've ever experienced lag after installing or restoring gapps during CM updates, these scripts are necessary to avoid that mishap. The scripts and updates also keep the updates from landing in /data partition, using more of your internal storage space while the system space is not utilized to its fullest capacity (until next Google update pushed OTA). If you've tried this update before, please try it again and make sure no redundant updates are in /data partition.
Tones retained:
ringtones: Orion, Themos, Kuma
alarms: Argon
notifications: Argon, Altair, Proxima
Extra bloat removed:
Apollo.apk
Galaxy4.apk
NoiseField.apk
HoloSpiralWallpaper.apk
LiveWallpapers.apk
LiveWallpaperspicker.apk
MagicSmokeWallpapers.apk
VideoEditor.apk
VisualizationWallpapers.apk
PhaseBeam.apk
PhotoTable.apk
PhotoPhase.apk
MediaUploader.apk
New Google Play, Services and more scripts
gapps-slim1.5_CM11_kk4.4.4.zip
What's new:
Google Play 5.0.31
Google Play services 6.1.11
new 88-link2sd.sh script added to avoid remounting script and reboot after gapps flash; thanks to Fiouz @ XDA for original script
more script changes to hopefully make the important steps 2-4 from OP less important (let me know)
What's important?
see OP, post 1. You can try the easy way of flashing prior to next nightly or unofficial nightly; the scripts should restore gapps and keep the ROM build "mini"
Check your tones; pull from another nightly ROM or customize as this is done in /system/addon.d/70-gapps.sh script
Xposed framework support was removed; if you need the script, pull from an older gapps version or from here; the bottom script. Hit the thanks button while you're there (the script inspired the latest 88-link2SD.sh used in this gapps release)
gapps-slim1.6_CM11_kk4.4.4.zip (Update)
gapps-slim1.6_CM11_kk4.4.4.zip
Changes:
Removed Google Calendar and corrected script to allow CM Calendar to actually update, when CM applies applicable update
updated Google Play Services to 6.1.74
attempted to set default media tones within the 70-gapps.sh; no guarantees. Thought it worked the one time I tried it but without data wipe so IDK.
FYI: can't test the flashes against the Epic any longer; mine got traded-in for the Note 4 ($200 BB gift card), Friday Oct. 17, 2014. Retired. Farewell Epic forum. Peace.
Hi,
can anybody confirm that in the current Cyanogen NIGHTLY for amami :
http://download.cyanogenmod.org/?device=amami
the Swipe keyboard feature ( in the default android keyboard AOSP) is not working?
it draws the swiped line, but does not write a word. I've checked the settings did a cache wipe and dalvic cache wipe and deleted the data for the keyboard APP in the settings all without any success
thanks in advance for your help
Nobody a hint for me?
The SwiftKey App is working, but I like to use the stock Version, or does anybody knows an reliable open source keyboard App alternative?
Solved!
Okay, I found out that it was the Google Apps (gapps package) that causes problems.
I did a complete new Install (formated /system /boot /cache /data and reinstalled cm11)
then I used the micro package from here:
http://forum.xda-developers.com/showthread.php?t=2397942
and up to now everything works as expected (though it has google launcher inside. is there ANY way to JUST get the playstore?`)
kind regards
raver
Dual Boot Patcher - Dual boot any ROMs on your Galaxy Grand Prime VE
Huge thanks to @chenxiaolong for his wonderful app, bringing a new life to our device
Now let's get started!
This app patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads:
[LINK] Dual Boot Patcher
[LINK] DualBootUtilities.zip
Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
XDA:DevDB Information
Dual Boot Patcher, Tool/Utility for the Samsung Galaxy Grand Prime
Contributors
doesntexits, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Testing
Created 2016-12-21
Last Updated 2016-12-21
Reserved
Reserved
Whats dual boot do?
Owen007 said:
Whats dual boot do?
Click to expand...
Click to collapse
That means you can install both rom and use it both. Its like when you install another OS on top of Windows
naimrlet said:
That means you can install both rom and use it both. Its like when you install another OS on top of Windows
Click to expand...
Click to collapse
Oh ok like in windows gr8 thing. Mean I can have two os.
Owen007 said:
Oh ok like in windows gr8 thing. Mean I can have two os.
Click to expand...
Click to collapse
Like cm13 and 14.1on the same phone or touchwiz and cm
Not Working
it's a great utility bt needs fix. I tried dual booting cm13 but image verification failed when flashing the patched image then i looked up updater-script and removed code block of SHA verification. pathced zip flashed successfully this tym bt still i m not able to boot cm13. dual boot patch app says cant switch the rom then i tred dual boot utilities frm recovery but it also dnt let to continue after the device information screen is shown
d1v1n3 said:
Not Working
it's a great utility bt needs fix. I tried dual booting cm13 but image verification failed when flashing the patched image then i looked up updater-script and removed code block of SHA verification. pathced zip flashed successfully this tym bt still i m not able to boot cm13. dual boot patch app says cant switch the rom then i tred dual boot utilities frm recovery but it also dnt let to continue after the device information screen is shown
Click to expand...
Click to collapse
First, to work with CM13, you have to edit updater-script of the patched ZIP a little bit
Find any lines with "/dev/block/bootdevice/by-name/XXXX", for example:
Code:
block_image_update("/dev/block/bootdevice/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
Change "bootdevice" to "platform/sdio_emmc", like this:
Code:
block_image_update("/dev/block/platform/sdio_emmc/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
The partitions path I used before for CM13 was for recovery usage only, and DBP seems couldn't find bootdevice path from /dev/block. Also, there's no need to remove system verification from updater-script
Cheers,
working perfectly
doesntexits said:
First, to work with CM13, you have to edit updater-script of the patched ZIP a little bit
Click to expand...
Click to collapse
Thank you so much. i am happy that u have fixed this in the new update of cm13 and yes it's working now. without updating the updater-script i've another question too. there is app sharing feature bt when i try to open that it says that mbltools not enabled and ramdisk needs update. it would be so nice if app sharing can be enabled. any solution for this?
waleeds1 said:
Like cm13 and 14.1on the same phone or touchwiz and cm
Click to expand...
Click to collapse
Any rom m8
naimrlet said:
Any rom m8
Click to expand...
Click to collapse
I know mate. I was giving an example
---------- Post added at 04:55 PM ---------- Previous post was at 04:53 PM ----------
Btw will it heavily affect the space as 8gb rom is really less with arround 3 gb left for use apps and after another rom it will be even less
Thanks for this man !
Can this work on g530h xxu,?
naimrlet said:
Any rom m8
Click to expand...
Click to collapse
Is it safe to use this with the 8.0 ROM with Los 14.1 ?
waleeds1 said:
Is it safe to use this with the 8.0 ROM with Los 14.1 ?
Click to expand...
Click to collapse
Yes, of course. I use this app for the whole time to test new Oreo builds
remilia15 said:
Yes, of course. I use this app for the whole time to test new Oreo builds
Click to expand...
Click to collapse
Thanks gonna try both of em now, Oreo and this because I was reluctant to switch from your los 14.1 to Oreo untill stable build for Oreo would have been released but now I'll try it.
remilia15 said:
Yes, of course. I use this app for the whole time to test new Oreo builds
Click to expand...
Click to collapse
Can you tell me how much system space does the ROM needs as I am running out of system partition while flashing the ROM I have applied the screen shot of how much space I have, the system size is the free storage as I will be removing that ROM. You could look it in the patcher app
waleeds1 said:
Can you tell me how much system space does the ROM needs as I am running out of system partition while flashing the ROM I have applied the screen shot of how much space I have, the system size is the free storage as I will be removing that ROM. You could look it in the patcher app
Click to expand...
Click to collapse
For convenience, better keep system partition more than 700MB free space. IMO, most of our N ROMs are more than 600MB big
Or you can install the secondary ROM on SD card or the data partition instead. DBP has that option tho
remilia15 said:
For convenience, better keep system partition more than 700MB free space. IMO, most of our N ROMs are more than 600MB big
Or you can install the secondary ROM on SD card or the data partition instead. DBP has that option tho
Click to expand...
Click to collapse
Thanks for the reply, I know it has that option but but I want it to be in system partition so that it doesn't take up other space and also to maintain stability.
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
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.