[GUIDE]Aroma Installer on any rom[Easy and simple] - Android General

Hello XDA member, i have little guide to add Aroma In your rom, this guide very easy to use, just need little change, and i gave the clues what you can change and can't change
Ok, to the point of the guide
Download the latest AROMA installer from this thread or my edited Aroma installer here
Then follow these little instructions
loadlang("langs/en.lang");
change "langs/en.lang" to change language, see in the aroma folder
theme("sense");
change "sense" to change aroma theme, see in the aroma folder
Added changelog/features
write your rom features or changelog in this files the file is in META-INF\com\android\google\android\aroma\changelog.txt
Little tutorial
Note :
> "xxx" means the words inside this ""
> you can change all xxx words
Option 1 : Option for select devices
> In aroma-config
);
selectbox(
#-- Title
"xxx", > you can change the "xxx" words
#-- Sub Title
"xxx", > you can change the "xxx" words
#-- Icon: <AROMA Resource Dir>/icons/default.png or <ThemeDir>/icon.default.png
"@default",
#-- Will be saved in /tmp/aroma/mods.prop
"system.prop",
"xxx","", 2, > you can change the "xxx" words
"xxx","xxx",1, > you can change the "xxx" words
"xxx","xxx",0, > you can change the "xxx" words
"xxx","xxx",0 > you can change the "xxx" words
#--------[ Initial Value = 0: Unselected, 1: Selected, 2: Group Item, 3: Not Visible ]---------#
);
> In updater-script
# xxx
# xxx
if
file_getprop("/tmp/aroma/system.prop","selected.1") == "1"
then
ui_print("xxx");
package_extract_dir("model/p760", "/system");
endif;
> you can change the "xxx" after "package_extract_dir" words depend on your own,
i use p760, which is the file is located in model/p760 folder,
make sure you put the right position of the file,
example :
i want to put "ducati-m3.bin" file in system/vendor/firmware
then that file should be in model/p760/vendor/firmware (look at the folder)
do the same thing for the rest of it
Option 2 : Option for add or remove apps
You can edit what you to install or remove from your rom, i used "Live Wallpapers" and some apps, you can edit yourself
> In aroma-config
checkbox(
"Install apps", > you can change the "xxx" words
"Uncheck items to remove", > you can change the "xxxx" words
"@default", > you can't change the "xxx" words
"remove.prop", > you can't change the "xxxx" words
"Live Wallpapers","",2, > you can change the "xxx" words
"Basic Dreams","",1, > you can change the "xxx" words
"Cosmic Flow","",1, > you can change the "xxx" words
"Photo Table","",1, > you can change the "xxx" words
"Applications","",2, > you can change the "xxx" words
"Carhome.apk","Carhome",1, > you can change the "xxx" words
"Protips.apk","Pro tips",1, > you can change the "xxx" words
"QuickBoot.apk","Quick Boot",1, > you can change the "xxx" words
);
> In updater-script
For install apps
# xxx > you can change the xxx words
# xxx > you can change the xxx words
if
file_getprop("/tmp/aroma/xxx.prop","selected.1") == "1" > you can change the xxx.prop words
then
ui_print("xxxx"); > you can change the "xxx" words
package_extract_file("camera/GoogleCamera.apk", "/system/app/GoogleCamera.apk");
endif;
> you can change the "xxx" after "package_extract_file" words depend on your own,
i use camera, which is the file is located in camera folder, then name of camera app
then i want to install in system/app folder, do the same thing for the rest of it
For remove apps
# xxx > you can change the xxx words
# xxx > you can change the xxx words
if
file_getprop("/tmp/aroma/remove.prop","item.1.1") == "0"
then
delete("/system/app/CarHome");
endif;
> change this "/system/app/CarHome" depend on what you want to remove, i used CarHome app
do the same thing for the rest of it
Last step : Change Updater script for installing rom
=> Step one : Device initial
Fine these lines
assert(getprop("ro.product.device") == "p760" || getprop("ro.build.product") == "p760" || abort("This package is for \"p760\" devices; this is a \"" + getprop("ro.product.device") + "\"."); );
mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.1/by-name/system", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
set_perm(0, 0, 0644, "/tmp/backuptool.functions");
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
show_progress(0.200000, 0); >until this
Replace those lines with your updater.scirpt until show_progress line
=> Step Two : Format system
Fine these lines
format("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.1/by-name/system", "0", "/system");
mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.1/by-name/system", "/system");
Replace those lines with your updater.scirpt
=> Step Three : Extracting files and setup symlink
"xxx" means skiping
Fine these lines
ui_print("@ Extracting System Files..");
package_extract_dir("system", "/system");
symlink("../bin/fsck.f2fs", "/system/bin/dump.f2fs");
symlink("../xbin/su", "/system/bin/su");
symlink("Roboto-Bold.ttf", "/system/fonts/DroidSans-Bold.ttf");
symlink("Roboto-Regular.ttf", "/system/fonts/DroidSans.ttf");
symlink("busybox", "/system/xbin/[", "/system/xbin/[[",
"/system/xbin/adjtimex", "/system/xbin/arp", "/system/xbin/ash",
"/system/xbin/awk", "/system/xbin/base64", "/system/xbin/basename",
"/system/xbin/bbconfig", "/system/xbin/blkid", "/system/xbin/blockdev",
xxxxx
xxxxx
show_progress(0.600000, 0);
Replace those lines with your updater.scirpt until show_progress line
=> Step Four : Setting permission
"xxx" means skiping
Fine these lines
ui_print("@ Setting Permissions");
set_metadata_recursive("/system", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644, "capabilities", 0x0, "selabel", "u: object_r:system_file:s0");
set_metadata_recursive("/system/addon.d", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755, "capabilities", 0x0, "selabel", "u: object_r:system_file:s0");
set_metadata_recursive("/system/bin", "uid", 0, "gid", 2000, "dmode", 0755, "fmode", 0755, "capabilities", 0x0, "selabel", "u: object_r:system_file:s0");
set_metadata("/system/bin/app_process", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u: object_r:zygote_exec:s0");
set_metadata("/system/bin/clatd", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u: object_r:clatd_exec:s0");
xxxx
xxxx
ui_print("@ Done");
ui_print("@ By nasheich");
ui_print("@ If you like this new build");
ui_print("@ Go back to my thread and press THANKS button");
show_progress(1.000000, 0);
unmount("/system");
Replace those lines with your updater.scirpt until unmount("/system"); line
Click to expand...
Click to collapse
Credit :
- amarullz for Aroma Installer
- nasheich for this little guide

Tips and Trick
- For rom under Android 4.4.2 (Kitkar), skip the step 3 and step four,
- After installation, take a log, it's easier if your get installation failed, like status 6, status 7, etc
note : status 0 it's mean working or installation successful

Questions and Answers
Q : Can i use this on my rom ?
A : Yes, this cam be used for any roms
Q : I got error on installation, status 6/7
A : Check your updater.script, there must be something wrong
Q : I've checked it all, look like nothing wrong in updater.script, any idea ?
A : Try another recovery, in some device, aroma didn't work

@Nasheich Xfiles the link to your installer is broken.

Related

Update script permission?

I am finishing off an update script and ran into a problem trying to set the permissions on an init.d script that I am loading to the system. Here are a few things I have tried to set on "crystal_clear" without success.
set_perm_recursive(0, 0, 0777, 0777, "/system/etc/init.d");
set_perm(0, 0, 0777, "/system/etc/init.d/crystal_clear");
Am I even close with this? This is my first update script. I bet i'm just missing something stupid but it's been killing me for hours and tried so many variations.
Here is everything so far. If there is something else you see here that doesn't look right please let me know.
show_progress(0.1, 0);
ui_print("Mounting System Partition");
mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system");
package_extract_file("tweaks/buildprop.sh", "/tmp/buildprop.sh");
package_extract_file("tweaks/sysmount/sysrw", "/tmp/sysrw");
package_extract_file("tweaks/sysmount/sysro", "/tmp/sysro");
set_perm(0, 0, 0777, "/tmp/buildprop.sh");
set_perm(0, 0, 0777, "/tmp/sysrw");
set_perm(0, 0, 0777, "/tmp/sysro");
ui_print("");
ui_print("Patching Build.prop");
run_program("/sbin/sh", "/tmp/sysrw");
run_program("/sbin/sh", "/tmp/buildprop.sh");
ui_print("");
ui_print("Patching adreno_config.txt, and egl.cfg");
package_extract_dir("system", "/system");
run_program("/sbin/sh", "/tmp/sysro");
show_progress(0.1, 10);
ui_print("");
ui_print("All tweaking processes are done");
ui_print("Adjusting framebuffer and color depth");
package_extract_file("system", "/system/etc/init.d");
set_perm(0, 0, 0777, 0777, "/etc/init.d/crystal_clear");
show_progress(0.2, 0);
unmount("/system");
ui_print("DONE");
General comments.
A simple
Code:
set_perm_recursive(0, 0, 0755, 0755, "/system/etc/init.d");
after I've extracted the all the files I've wanted to the right place has always worked fine in the CWM ZIP I keep for personal use to install BusyBox etc.
razz1 said:
package_extract_file("tweaks/sysmount/sysrw", "/tmp/sysrw");
package_extract_file("tweaks/sysmount/sysro", "/tmp/sysro");
set_perm(0, 0, 0777, "/tmp/sysrw");
set_perm(0, 0, 0777, "/tmp/sysro");
run_program("/sbin/sh", "/tmp/sysrw");
run_program("/sbin/sh", "/tmp/sysro");
Click to expand...
Click to collapse
You don't need these. CWM/TWRP will mount /system rw by default and you don't really need to remount it ro in CWM.
package_extract_dir("system", "/system");
package_extract_file("system", "/system/etc/init.d");
Click to expand...
Click to collapse
Is "system" a directory or a file?
That said, I think you want the former - just have a system folder in the root of your ZIP mirroring where you want the files to be placed (so in your ZIP, create a "system" folder at the same level as META-INF and then have a "etc" folder inside that, then a "init.d" folder inside "etc" with your script inside "init.d").
THANK YOU!
I'm going to try a few things you said and go from there.
Here is my current hierarchy...
4xMultiSampling_Antialiasing.zip
......META-INF
..........com
.............google
................android
.....................update-binary
.....................updater-script
......system
.........etc
.............Init.d
................crystal_clear. <-----this is what would not change to 0777
......lib
........egl
..........egl.config
......tweaks
.........build.prop.sh
.........sysmount
..............sysro
..............sysrw
razz1 said:
.............Init.d
Click to expand...
Click to collapse
If that's not a typo, it needs to be init.d - ext* file systems, unlike Windows', are case-sensitive
Yes that was a typo, but I appreciate your attention to detail because that's is exactly what I need. As you know, its that sort of thing that can kill a script. Critique away!
It appears I was able to pull it off with your help. Thanks. All is well here now.
Glad to hear it.

[Q] Help with update-script (status 6)

Hi guys, I have this error on my own update.zip, so I need help
- Edited with notepad++
- I checked, end of line, it's correct
- I checked, unix system, not windows.
So, I think is a bad mount command, my file system it's rfs (i think, just flashed with odin) , not ext4.
Paste my script:
show_progress(0.500000, 0);
ui_print("========================");
ui_print("== Value.and.Fast 2.5 ==");
ui_print("========================");
run_program("/sbin/busybox", "mount", "/system");
assert(is_mounted("/system"));
package_extract_dir("system", "/system");
ui_print("Asignando permisos...");
set_perm(0, 0, 0644, "/system/build.prop");
set_perm(0, 0, 0644, "/system/app/AxT9IME.apk");
set_perm(0, 0, 0644, "/system/app/ClockWidgets.apk");
set_perm(0, 0, 0644, "/system/app/Home_MultiResolution.apk");
set_perm(0, 0, 0644, "/system/app/WidgetPicker.apk");
ui_print("Eliminando aplicaciones...");
delete("/system/app/BuddiesNow.apk");
delete("/system/app/BuddiesNow.odex");
delete("/system/app/Dlna.apk");
delete("/system/app/Dlna.odex");
delete("/system/app/Signin.apk");
delete("/system/app/Signin.odex");
delete("/system/app/Days.apk");
delete("/system/app/Days.odex");
delete("/system/app/DualClock.apk");
delete("/system/app/DualClock.odex");
delete("/system/app/Gallery3D.apk");
delete("/system/app/Gallery3D.odex");
delete("/system/app/Email.apk");
delete("/system/app/Layar-samsung.apk");
delete("/system/app/Maps.apk");
delete("/system/app/MiniDiary.apk");
delete("/system/app/MiniDiary.odex");
delete("/system/app/MinimalHome.apk");
delete("/system/app/MinimalHome.odex");
delete("/system/app/MobileTrackerEngineTwo.apk");
delete("/system/app/MobileTrackerEngineTwo.odex");
delete("/system/app/MobileTrackerUI.apk");
delete("/system/app/MobileTrackerUI.odex");
delete("/system/app/Protips.apk");
delete("/system/app/Protips.odex");
delete("/system/app/RoseEUKor.apk");
delete("/system/app/SamsungApps.apk");
delete("/system/app/SamsungAppsUNA3.apk");
delete("/system/app/SamsungWidget_FeedAndUpdate.apk");
delete("/system/app/SamsungWidget_FeedAndUpdate.odex");
delete("/system/app/SamsungWidget_StockClock.apk");
delete("/system/app/SamsungWidget_StockClock.odex");
delete("/system/app/ShareApp.apk");
delete("/system/app/ShareApp.odex");
delete("/system/app/Street.apk");
delete("/system/app/Swype.apk");
delete("/system/app/syncmldm.apk");
delete("/system/app/syncmldm.odex");
delete("/system/app/thinkdroid.apk");
delete("/system/app/UnifiedInbox.apk");
delete("/system/app/UnifiedInbox.odex");
delete("/system/app/WriteandGo.apk");
delete("/system/app/WriteandGo.odex");
delete("/system/app/MagicSmokeWallpapers.apk");
delete("/system/app/MagicSmokeWallpapers.odex");
run_program("/sbin/busybox", "umount", "/system");
ui_print(" === FIN === ");
show_progress(0.200000, 0);
show_progress(0.200000, 10);
show_progress(0.100000, 0);
Click to expand...
Click to collapse
Thank!!
check on CMW - advance - show log
it will show what wrong after you flash the zip
Nevermind, i fix the problem
deleting line:
ui_print("=================");
how can it fix your problem? I got a staus 6 too
You mean if I remov this lines
set_progress(0.95);
ui_print("**************************************** ******");
ui_print("* Creating system links *");
ui_print("**************************************** ******");
and this...
set_progress(0.99);
ui_print("**************************************** ******");
ui_print("* Install kernel *");
ui_print("**************************************** ******");
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "/dev/block/mmcblk0p8"),
delete("/tmp/boot.img"));
unmount("/data");
unmount("/system");
unmount("/custpack");
set_progress(1.00);
ui_print("**************************************** ******");
ui_print(" DONE !!! ");
ui_print("**************************************** ******");
will fix it

[GUIDE][PORTING] OTX - Bloatware Remover

Here, I present you the quick guide on porting my project (codename: OTX) which is capable of removing bloatwares that are selectable by the user in the aroma-installer. You may think that this script has already been made for your device. But you can notice a new thing in my project that it is user selectable. Nobody has made it till now. I think it is because of the limitations in the aroma installer that made people stop working on this very type of project. I too had the same feel when I was working on it. I asked my friends, posted on facebook, asked a question on aroma-installer thread but no support came from any of them. So I figured it out myself and made the project. And now, let me not make you feel bored and start the work.
Download the file from my original thread. Link: Click here to view thread
If you use Samsung Galaxy Y, you can directly download and use it. I have made this guide for other devices.
Extract the zip named "signed_OTX_BLOAT.zip" and look into its contents.
Now go to META-INF > com > google > android > place_holder
In the aroma-config, you will see something like this:
Code:
###################
#Install Select box
###################
checkbox("","<b>Bloatware Remover</b>",
"@alert",
"checkbox.prop",
"Select what you want", "", 2,
"<b>Alert Recipients</b>","", 0,
"<b>AxT9IME</b>","", 0,
"<b>Bluetooth</b>","", 0,
"<b>Bluetooth Pbap</b>","", 0,
"<b>Bluetooth Test Mode</b>","", 0,
"<b>Browser</b>","", 0,
"<b>Calculator</b>","", 0
);
checkbox("","<b>Bloatware Remover</b>",
"@alert",
"checkbox1.prop",
"Select what you want", "", 2,
"<b>Calendar</b>","", 0,
"<b>Calendar Provider</b>","", 0,
"<b>Clock Widget</b>","", 0,
"<b>Default Container Service</b>","", 0,
"<b>Desk Clock</b>","", 0,
"<b>Dual Clock</b>","", 0,
"<b>Email</b>","", 0
);
checkbox("","<b>Bloatware Remover</b>",
"@alert",
"checkbox2.prop",
"Select what you want", "", 2,
"<b>Email Widget</b>","", 0,
"<b>Factory Test</b>","", 0,
"<b>Fm Radio</b>","", 0,
"<b>Fotaclient</b>","", 0,
"<b>Gallery 3D</b>","", 0,
"<b>Genie Widget</b>","", 0,
"<b>Gmail</b>","", 0
);
checkbox("","<b>Bloatware Remover</b>",
"@alert",
"checkbox3.prop",
"Select what you want", "", 2,
"<b>Google Backup Transport</b>","", 0,
"<b>Google Calendar Sync Adapter</b>","", 0,
"<b>Google Contacts Sync Adapter</b>","", 0,
"<b>Google Feedback</b>","", 0,
"<b>Google Quick Search Box</b>","", 0,
"<b>Google Services Framework</b>","", 0,
"<b>HTML Viewer</b>","", 0
);
checkbox("","<b>Bloatware Remover</b>",
"@alert",
"checkbox4.prop",
"Select what you want", "", 2,
"<b>Job Manager</b>","", 0,
"<b>lcdtest</b>","", 0,
"<b>Live Wallpapers Picker</b>","", 0,
"<b>Maps</b>","", 0,
"<b>Market Updater</b>","", 0,
"<b>Media Uploader</b>","", 0,
"<b>Memo</b>","", 0
);
checkbox("","<b>Bloatware Remover</b>",
"@alert",
"checkbox5.prop",
"Select what you want", "", 2,
"<b>Mobile Tracker Engine Two</b>","", 0,
"<b>Music</b>","", 0,
"<b>My Files</b>","", 0,
"<b>Network Location</b>","", 0,
"<b>PCWClientS</b>","", 0,
"<b>Phonesky</b>","", 0,
"<b>PicoTts</b>","", 0
);
checkbox("","<b>Bloatware Remover</b>",
"@alert",
"checkbox6.prop",
"Select what you want", "", 2,
"<b>PopupuiReceiver</b>","", 0,
"<b>PowerOnOffTest</b>","", 0,
"<b>Protips</b>","", 0,
"<b>Quickoffice</b>","", 0,
"<b>Samsung Apps</b>","", 0,
"<b>Samsung Apps UNA2</b>","", 0,
"<b>Samsung Apps UNA3</b>","", 0
);
checkbox("","<b>Bloatware Remover</b>",
"@alert",
"checkbox7.prop",
"Select what you want", "", 2,
"<b>Samsung Widget_ProgramMonitor</b>","", 0,
"<b>Samsung Widget_StockClock</b>","", 0,
"<b>Samsung Widget_WeatherClock</b>","", 0,
"<b>Screen Capture Service</b>","", 0,
"<b>Security Provider</b>","", 0,
"<b>SelfTest</b>","", 0,
"<b>Share App</b>","", 0
);
checkbox("","<b>Bloatware Remover</b>",
"@alert",
"checkbox8.prop",
"Select what you want", "", 2,
"<b>signin</b>","", 0,
"<b>SnsAccount</b>","", 0,
"<b>SnsProvider</b>","", 0,
"<b>Stk</b>","", 0,
"<b>Street</b>","", 0,
"<b>Swype</b>","", 0,
"<b>syncmldm</b>","", 0
);
checkbox("","<b>Bloatware Remover</b>",
"@alert",
"checkbox9.prop",
"Select what you want", "", 2,
"<b>syncmlds</b>","", 0,
"<b>TalkorHangouts</b>","", 0,
"<b>talkback</b>","", 0,
"<b>TtsService</b>","", 0,
"<b>TwWallpaperChooser</b>","", 0,
"<b>UnifiedInbox</b>","", 0,
"<b>UserDictionaryProvider</b>","", 0
);
checkbox("","<b>Bloatware Remover</b>",
"@alert",
"checkbox10.prop",
"Select what you want", "", 2,
"<b>VoiceRecorder</b>","", 0,
"<b>VoiceSearch</b>","", 0,
"<b>VpnServices</b>","", 0,
"<b>wipereceiver</b>","", 0,
"<b>WlanTest</b>","", 0,
"<b>wssyncmlnps</b>","", 0,
"<b>YouTube</b>","", 0
);
In aroma-config, change the names of the applications that you want to include as bloatware and make sure these apps are safe to be removed and does not cause any stability issues to the device.
I have declared more separate checkboxes for giving the selection. It is because of the limitation in aroma-installer. You will surely think that it has more number of pages are there for selection. But it is far better than typing one by one that you want to delete. I have made 7 selection per checkbox concept. After I made the script and published, I heard that there is upto 10 selection per checkbox option. I don't know whether it is true or not because I haven't tried it yet. You can try it out and if it works, then great. Make a note of the order of the applications written here because correspondingly you are going to delete the bloatwares. Also give separate names for these checkboxes. I have just named it checkbox1.prop, checkbox2.prop, ..., etc. Youi can give any name. But make sure you remember it.
After making changes, just save the file and exit.
In the file updater-script, you will see something like this:
Code:
if
file_getprop("/tmp/aroma-data/checkbox.prop","item.1.1") == "1"
then
show_progress(0.1, 0);
package_extract_file("busybox", "/tmp/busybox");
set_perm(0, 0, 0777, "/tmp/busybox");
run_program("/tmp/busybox", "mount", "/system");
run_program("/tmp/busybox", "mount", "/data");
show_progress(0.1, 0);
package_extract_file("busybox", "/tmp/busybox");
set_perm(0, 0, 0777, "/tmp/busybox");
run_program("/tmp/busybox", "mount", "/system");
run_program("/tmp/busybox", "mount", "/data");
delete("/system/app/AlertRecipients.apk");
delete("/system/app/AlertRecipients.odex");
ui_print("-> Done");
endif;
if
file_getprop("/tmp/aroma-data/checkbox.prop","item.1.2") == "1"
then
show_progress(0.1, 0);
package_extract_file("busybox", "/tmp/busybox");
set_perm(0, 0, 0777, "/tmp/busybox");
run_program("/tmp/busybox", "mount", "/system");
run_program("/tmp/busybox", "mount", "/data");
delete("/system/app/AxT9IME.apk");
delete("/system/app/AxT9IME.odex");
ui_print("-> Done");
endif;
if
file_getprop("/tmp/aroma-data/checkbox.prop","item.1.3") == "1"
then
show_progress(0.1, 0);
package_extract_file("busybox", "/tmp/busybox");
set_perm(0, 0, 0777, "/tmp/busybox");
run_program("/tmp/busybox", "mount", "/system");
run_program("/tmp/busybox", "mount", "/data");
delete("/system/app/Bluetooth.apk");
delete("/system/app/Bluetooth.odex");
ui_print("-> Done");
endif;
if
file_getprop("/tmp/aroma-data/checkbox.prop","item.1.4") == "1"
then
show_progress(0.1, 0);
package_extract_file("busybox", "/tmp/busybox");
set_perm(0, 0, 0777, "/tmp/busybox");
run_program("/tmp/busybox", "mount", "/system");
run_program("/tmp/busybox", "mount", "/data");
delete("/system/app/BluetoothPbap.apk");
delete("/system/app/BluetoothPbap.odex");
ui_print("-> Done");
endif;
if
file_getprop("/tmp/aroma-data/checkbox.prop","item.1.5") == "1"
then
show_progress(0.1, 0);
package_extract_file("busybox", "/tmp/busybox");
set_perm(0, 0, 0777, "/tmp/busybox");
run_program("/tmp/busybox", "mount", "/system");
run_program("/tmp/busybox", "mount", "/data");
delete("/system/app/BluetoothTestMode.apk");
delete("/system/app/BluetoothTestMode.odex");
ui_print("-> Done");
endif;
if
file_getprop("/tmp/aroma-data/checkbox.prop","item.1.6") == "1"
then
show_progress(0.1, 0);
package_extract_file("busybox", "/tmp/busybox");
set_perm(0, 0, 0777, "/tmp/busybox");
run_program("/tmp/busybox", "mount", "/system");
run_program("/tmp/busybox", "mount", "/data");
delete("/system/app/Browser.apk");
delete("/system/app/Browser.odex");
ui_print("-> Done");
endif;
if
file_getprop("/tmp/aroma-data/checkbox.prop","item.1.7") == "1"
then
show_progress(0.1, 0);
package_extract_file("busybox", "/tmp/busybox");
set_perm(0, 0, 0777, "/tmp/busybox");
run_program("/tmp/busybox", "mount", "/system");
run_program("/tmp/busybox", "mount", "/data");
delete("/system/app/Calculator.apk");
delete("/system/app/Calculator.odex");
ui_print("-> Done");
endif;
show_progress(0.100000, 0);
ui_print("The process is complete. Reboot the system to use");
ui_print(" ");
ui_print("Made by: the_pirate_predator");
In updater-script, give the names of the checkboxes inside if-loop condition and using item number to check on the selectable options which are inside these checkboxes. Due to limitation of aroma-installer, the item numbers are from item.1.1 to item.1.7. If the limitation is 10, you can try to implement it. Also I recommend using busybox for running this script. You can place it along with META-INF folder at the beginning by creating a folder with a name called tmp. I have made a mistake in my package by not putting it inside the tmp folder, but you should do it. But for me, it still works.
After making changes, just save the file and exit.
Now a important part comes to play in making this project suitable for your device. As I have used update-binary for my device (obtained from hells kernel for sgy) it runs perfectly on my device. If you can find a previously made program which uses aroma for your device, you can copy that. If you dont have such files, then try to get the file from aroma installer itself http://forum.xda-developers.com/devdb/project/?id=330#downloads by extracting the zip and replacing that file in the project. Just try it out. Till then I will search for any alternative (if required).
Now after doing everything, repack the zip properly and sign it using dsixda's android kitchen and check everything is proper and error less.
Now test your device and if it works, just give a credit. Report problems and I will try my level best to correct it. I think I have explained everything clearly.
A Pictograph
Goto my website and click on the link.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download the zip file
Extract the zip file
After extracting the zip, you will see something like this.
Goto META-INF > com > google > android > place_holder
Inside aroma-config
Ignore my last message, I was figuring stuff out lol
First try: used an updater-binary which I have used before to make an aroma zip. Failed to execute updater-binary in recovery.
Got it working now. thank you for your work

Editing build.prop via flashable zip

Hey folks,
to avoid doing this manually with every nightly, I wanted to change some build.prop values via a flashable zip, which doesn't seem to work.
I used the script from here and modified it for my needs. It doesn't throw an error in recovery, but doesn't change any values, either.
Here are my files:
updater-script
Code:
ui_print("fixer");
ui_print("Mounting System partition...");
#mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
#Properly unmounting to avoid issues
run_program("/sbin/busybox", "umount", "/system");
run_program("/sbin/busybox", "mount", "/system");
ui_print("bloat removal..");
delete_recursive("/system/app/Apollo");
delete_recursive("/system/app/BasicDreams");
delete_recursive("/system/app/Browser");
delete_recursive("/system/app/Calculator");
delete_recursive("/system/app/CMHome");
delete_recursive("/system/app/CMWallpapers");
delete_recursive("/system/app/Development");
delete_recursive("/system/app/Email");
delete_recursive("/system/app/Galaxy4");
delete_recursive("/system/app/GoogleTTS");
delete_recursive("/system/app/HoloSpiralWallpaper");
delete_recursive("/system/app/Launcher3");
delete_recursive("/system/app/LiveWallpapers");
delete_recursive("/system/app/NoiseField");
delete_recursive("/system/app/OmaDmclient");
delete_recursive("/system/app/OpenWnn");
delete_recursive("/system/app/PrebuildExchange3Google");
delete_recursive("/system/app/PhaseBeam");
delete_recursive("/system/app/PhotoTable");
delete_recursive("/system/app/PicoTts");
delete_recursive("/system/app/PrintSpooler");
delete_recursive("/system/app/SprintHiddenMenu");
delete_recursive("/system/app/Stk");
delete_recursive("/system/app/Trebuchet");
delete_recursive("/system/app/UpdateSetting");
delete_recursive("/system/app/VisualizationWallpapers");
delete_recursive("/system/priv-app/CellBroadcastReceiver");
delete_recursive("/system/priv-app/CMUpdater");
delete_recursive("/system/priv-app/GoogleFeedback");
delete_recursive("/system/priv-app/VoiceDialer");
delete("/system/media/audio/ui/camera_click.ogg");
delete("/system/media/audio/ui/camera_focus.ogg");
ui_print("tweaking build.prop...");
package_extract_dir("tmp", "/tmp");
set_perm(0, 0, 0777, "/tmp/mytweaks.sh");
run_program("/tmp/mytweaks.sh", "mytweak");
unmount("/system");
run_program("/sbin/busybox", "umount", "/system");
ui_print("Completed.");
mytweaks.sh
Code:
#!/sbin/sh
bp="/system/build.prop"
busybox mount /system
busybox mount /data
if [ -f /system/build.prop.bak ];
then
rm -rf $bp
cp $bp.bak $bp
else
cp $bp $bp.bak
fi
echo " " >> $bp
echo "# build.prop editor" >> $bp
echo " " >> $bp
for mod in misc;
do
for prop in `cat /tmp/$mod`;do
export newprop=$(echo ${prop} | cut -d '=' -f1)
sed -i "/${newprop}/d" /system/build.prop
echo $prop >> /system/build.prop
done
done
misc
Code:
ro.sf.lcd_density=420
drm.service.enabled=false
wifi.supplicant_scan_interval=60
dalvik.vm.isa.arm.features=lpae,div
dalvik.vm.dexopt-flags=m=y,v=a,o=v,u=y
Furthermore, my device runs on TWRP 2.8.1.0 and CM12. I suspect the path to the shell is wrong, but couldn't find anything on that. Any suggestions?
Anyone?
I haven't time to troubleshoot your zip and script but attached is the one I wrote. In the uodater-script, its the part after wireless charging you want. I've removed my files that I also flash via this zip, but left the shell script.
In the shell, the sed lines are original_value/new_value and the echo lines add new lines at the bottom.
Hope this helps.
Not sure but if you unmount the system can you modify after that?
Sent from my Nexus 5 using XDA Free mobile app
shri_chanakya said:
Not sure but if you unmount the system can you modify after that?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
You'll need /system mounted to make changes in the /system/build.prop (good point)
rootSU said:
I haven't time to troubleshoot your zip and script but attached is the one I wrote. In the uodater-script, its the part after wireless charging you want. I've removed my files that I also flash via this zip, but left the shell script.
In the shell, the sed lines are original_value/new_value and the echo lines add new lines at the bottom.
Hope this helps.
Click to expand...
Click to collapse
THank you, that worked marvellously!
anon768 said:
THank you, that worked marvellously!
Click to expand...
Click to collapse
No probs;
I know this is an old thread, but I have a question for Dan or whomever else could answer it.
I was trying to integrate this script into another updater-script that I use for other stuff. so (since it uses the new updater-binary) I put these lines in it
set_metadata_recursive("/system/build_prop.sh", "uid", 0, "gid", 0, "dmode", 0777, "fmode", 0777, "capabilities", 0x0, "selabel", "ubject_r:system_file:s0");
run_program("sbin/sh", "/system/build_prop.sh");
delete("/system/build_prop.sh");
It works sort of fine. All the sed lines replace some text with some other text as expected. However, the echo lines, rather than appending the build.prop file, instead make a totally new build.prop file, with an identical name, sitting right next to it. I didn't even know that could happen.
Any thoughts on how to fix it?
oh ps an example of a line that works and one that doesn't are as follows
sed -i 's/telephony.lteOnCdmaDevice=0/telephony.lteOnCdmaDevice=1/g' /system/build.prop;
echo -e "telephony.lteOnGsmDevice=1" >> /system/build.prop
nevermind. turns out the echo lines were just missing semicolons. at first I thought it was a permissions issue on build.prop, so i set it to universal read/write then set it back to what it was supposed to be after script finishes
set_metadata("/system/build_prop.sh", "uid", 0, "gid", 0, "mode", 0777, "selabel", "ubject_r:system_file:s0", "capabilities", 0x0)
set_metadata("/system/build.prop", "uid", 0, "gid", 0, "mode", 0777, "selabel", "ubject_r:system_file:s0", "capabilities", 0x0)
run_program("sbin/sh", "/system/build_prop.sh");
delete("/system/build_prop.sh");
set_metadata("/system/build.prop", "uid", 0, "gid", 0, "mode", 0644, "selabel", "ubject_r:system_file:s0", "capabilities", 0x0)

[GUIDE] [TUT] Enable Bootanimation Sound On/Off Device For CyanogenMod - ‏LineageOS

Today Present way to enable sounds at bootanimations turn on/off device
if you open that file named bootanimation in system/bin, will find the way and follow, i have prepared the guide for cyanogenmod lollipop & marshmallow & nougat​​
Let's Start​Marshmallow & Lollipop :​​just i explain to you how to find it go to system/bin and open bootanimation
will conclude the following :
1 - codec for audio file must be [only 16 bit WAV files are supported]
2 - file will put in system/media [boot.wav & shutdown.wav]
3 - file zip will be named [shutdownanimation.zip & bootanimation.zip]
4 - open your build prob and add this lines
PHP:
ro.config.power_on=boot.wav
ro.config.power_off=shutdown.wav
​
Nougat :​​just i explain to you how to find it go to system/bin and open bootanimation
will conclude the following :
1 - codec for audio file must be .wav
2 - file will put in system/media [audio.wav]
3 - file zip will be named [bootanimation.zip]
4 - open your build prob and add this lines
PHP:
ro.config.power_on=boot.wav
ro.config.power_off=shutdown.wav
persist.sys.bootanim.play_sound=true
marshmallow & lollipop guide may work with some of nougat's roms
app help you to get and set audio file 16 bit WAV
Guide not confusing, it's very easy just put audio files and lines in build prob, guide long because i explaining with details
​Updater Script for Patching​
PHP:
ui_print("Installing Patch Boot Audio...");
run_program("/sbin/busybox", "mount", "/system");
show_progress(1, 15);
delete("/system/media/shutanimation.zip");
delete("/system/media/boot.wav");
delete("/system/media/bootanimation.zip");
delete("/system/media/shutdown.wav");
delete("/system/media/shutdownanimation.zip");
package_extract_dir("system", "/system");
show_progress(1, 15);
ui_print("Setting metadata...");
set_metadata_recursive("/system/bin", "uid", 0, "gid", 2000, "dmode", 0755, "fmode", 0755, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata("/system/bin/bootanimation", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:bootanim_exec:s0");
set_metadata_recursive("/system/media", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
run_program("/sbin/busybox", "umount", "/system");
ui_print("Done!");
Download files audio and bootanimation for testing​
​
Support me, don't forget to hit thanks button​
well-done
Nice

Categories

Resources