I wanted to install my favourite apps easier, after flashing a new rom, so i wanted to make a zip file to install them over recovery. Therefore I downloaded an .zip file that installed just one app into /system. But the apps needed to be in /data/app so i edited the updater-sript. Here it is:
ui_print("Install Apps");
run_program("/sbin/busybox", "mount", "/data");
show_progress(1, 15);
package_extract_dir("app", "/data/app");
run_program("/sbin/busybox", "umount", "/data");
ui_print("Installation complete!");
I made an app folder in the zip file named app with my favourite apps inside. But I always get "installation aborted (status 6)" when I want to install it. What do I do wrong?
I have a Concern about SuperSU root files, while i have been always using Super User for a long time, i could say that SuperSU is much better, but the issue is that i was browsing inside the zip file of the SuperSU and i came to the script file and i opened it with a notepad, while i am not a developer to fully understand whats is written but a few line about copying and fixing permissions for both Maps and youtube make me wonder whats the relation between SuperSU and those apps specially that the script file for Super user never had such lines
This is the Content of the Script file included with the SuperSU:
ui_print("*********************");
ui_print("SuperSU installer ZIP");
ui_print("*********************");
ui_print("- Mounting /system, /data and rootfs");
run_program("/sbin/busybox", "mount", "/system");
run_program("/sbin/busybox", "mount", "/data");
run_program("/sbin/busybox", "mount", "-o", "rw,remount", "/system", "/system");
run_program("/sbin/busybox", "mount", "-o", "rw,remount", "/", "/");
ui_print("- Disabling OTA survival");
package_extract_dir("tools", "/system");
run_program("/system/chattr", "-i", "/system/bin/.ext/.su");
delete("/system/chattr");
ui_print("- Removing old files");
delete("/system/bin/su");
delete("/system/xbin/su");
delete("/system/bin/.ext/.su");
delete("/system/app/Superuser.apk");
delete("/system/app/Superuser.odex");
delete("/system/app/SuperUser.apk");
delete("/system/app/SuperUser.odex");
delete("/system/app/superuser.apk");
delete("/system/app/superuser.odex");
delete("/system/app/Supersu.apk");
delete("/system/app/Supersu.odex");
delete("/system/app/SuperSU.apk");
delete("/system/app/SuperSU.odex");
delete("/system/app/supersu.apk");
delete("/system/app/supersu.odex");
run_program("/sbin/busybox", "rm", "/data/dalvik-cache/*com.noshufou.android.su*");
run_program("/sbin/busybox", "rm", "/data/dalvik-cache/*Superuser.apk*");
run_program("/sbin/busybox", "rm", "/data/dalvik-cache/*SuperUser.apk*");
run_program("/sbin/busybox", "rm", "/data/dalvik-cache/*superuser.apk*");
run_program("/sbin/busybox", "rm", "/data/dalvik-cache/*eu.chainfire.supersu*");
run_program("/sbin/busybox", "rm", "/data/dalvik-cache/*Supersu.apk*");
run_program("/sbin/busybox", "rm", "/data/dalvik-cache/*SuperSU.apk*");
run_program("/sbin/busybox", "rm", "/data/dalvik-cache/*supersu.apk*");
ui_print("- Creating space");
run_program("/sbin/busybox", "cp", "/system/app/Maps.apk", "/Maps.apk");
run_program("/sbin/busybox", "cp", "/system/app/GMS_Maps.apk", "/GMS_Maps.apk");
run_program("/sbin/busybox", "cp", "/system/app/YouTube.apk", "/YouTube.apk");
run_program("/sbin/busybox", "rm", "/system/app/Maps.apk");
run_program("/sbin/busybox", "rm", "/system/app/GMS_Maps.apk");
run_program("/sbin/busybox", "rm", "/system/app/YouTube.apk");
ui_print("- Extracting files");
package_extract_dir("system", "/system");
ui_print("- Restoring files");
run_program("/sbin/busybox", "cp", "/Maps.apk", "/system/app/Maps.apk");
run_program("/sbin/busybox", "cp", "/GMS_Maps.apk", "/system/app/GMS_Maps.apk");
run_program("/sbin/busybox", "cp", "/YouTube.apk", "/system/app/YouTube.apk");
run_program("/sbin/busybox", "rm", "/Maps.apk");
run_program("/sbin/busybox", "rm", "/GMS_Maps.apk");
run_program("/sbin/busybox", "rm", "/YouTube.apk");
ui_print("- Setting permissions");
set_perm(0, 0, 0777, "/system/bin/.ext");
set_perm(0, 0, 06755, "/system/bin/.ext/.su");
set_perm(0, 0, 06755, "/system/xbin/su");
set_perm(0, 0, 0644, "/system/app/Superuser.apk");
set_perm(0, 0, 0644, "/system/app/Maps.apk");
set_perm(0, 0, 0644, "/system/app/GMS_Maps.apk");
set_perm(0, 0, 0644, "/system/app/YouTube.apk");
ui_print("- Unmounting /system and /data");
unmount("/system");
unmount("/data");
ui_print("- Done !");
hmm, good question. I use SuperSu as well.
This is making me worried
tbodner said:
hmm, good question. I use SuperSu as well.
Click to expand...
Click to collapse
Well i tried replying on the main thread of chainfire "the one behind SuperSU and a lot of awesome hacks" but because i have a very few posts am not allowed to post in the developer section
amrabdelaziz said:
Well i tried replying on the main thread of chainfire "the one behind SuperSU and a lot of awesome hacks" but because i have a very few posts am not allowed to post in the developer section
Click to expand...
Click to collapse
I'll post in the SuperSU thread and link Chainfire to this thread. Maybe he'll stop by if he's not too busy. Doesn't hurt to try.
Same here, it seems I've hit my 10 but still unable to post there
This has actually been discussed several times before. A proper search should turn it up (yes, I am also to lazy to search it for you, so I'll just explain).
Some devices - especially older ones - do not actually have free space in /system, so trying to add SuperSU APK and binaries would simply fail, you won't get root. So what the script does, is copy the Maps and YouTube packages (which should be larger than SuperSU files) to memory (ramdisk location), then deletes them from /system. It then installs SuperSU files, and attempts to copy those packages back into place.
So, in the worst case there is no space in /system, you still get SuperSU installed, but you lose Maps and/or YouTube. That is no big problem though, because you can re-download both of them from Play. That is one of the main reasons I picked these two - they are easily available to restore.
If there is enough space (virtually all devices from 2012 and later) you won't notice anything. Both SuperSU will be installed, and Maps and YouTube will still be there.
Though really, just reading the ui_print lines should have clued you in on what is going on
Thank you so much that makes sense You are awesome man
tbodner said:
Same here, it seems I've hit my 10 but still unable to post there
Click to expand...
Click to collapse
may need some time...
Thank You
Chainfire said:
This has actually been discussed several times before. A proper search should turn it up (yes, I am also to lazy to search it for you, so I'll just explain).
Some devices - especially older ones - do not actually have free space in /system, so trying to add SuperSU APK and binaries would simply fail, you won't get root. So what the script does, is copy the Maps and YouTube packages (which should be larger than SuperSU files) to memory (ramdisk location), then deletes them from /system. It then installs SuperSU files, and attempts to copy those packages back into place.
So, in the worst case there is no space in /system, you still get SuperSU installed, but you lose Maps and/or YouTube. That is no big problem though, because you can re-download both of them from Play. That is one of the main reasons I picked these two - they are easily available to restore.
If there is enough space (virtually all devices from 2012 and later) you won't notice anything. Both SuperSU will be installed, and Maps and YouTube will still be there.
Though really, just reading the ui_print lines should have clued you in on what is going on
Click to expand...
Click to collapse
Thank you so much that makes sense You are awesome man
amrabdelaziz said:
Thank you so much that makes sense You are awesome man
Click to expand...
Click to collapse
of course he's awesome.
he made me buy donate for sSU Pro MODIN Pro and TA from gPlay...
My1xT said:
of course he's awesome.
he made me buy donate for sSU Pro MODIN Pro and TA from gPlay...
Click to expand...
Click to collapse
i am considering "buying" sSU pro too i think we should support caring developers :angel:
I want to create a flashable zip for my mt6572 device .
i am having cadvik recovery 2.2
i used the android kitchen to create the stock zip
it created a zip .
now the problem is :
when i try flash it through cwm , it saying that you have to do it again .
it showing errors .
so i chech the updater script .
i noticed that . it starts with like :
***************
***************
** format("MTD", "system");
mount("MTD", "system", "/system");
i think it should like this right
Should be:
format("ext4", "EMMC", "/dev/block/mmcblk0p5");
mount("ext4", "EMMC", "/dev/block/mmcblk0p5", "/system"); **
******************
*****************
i made that zip using my stock system.img
but still i not get succeed to flash it via cwm .
any one know why that update script is like that ..
any solution for that .
Hi there,
There is many threads that are describe how to make flashable zip for many things. Here are few of them:
[GUIDE][NOOB FRIENDLY]How To Make Aroma Installer Flashable Zip/update.zip
[GUIDE]How to extract a Firmware and make a flashable ZIP
Good luck
Device details:
YU Yuphoria YU5010
Software: CyanogenMod 12.1 (Nightly)
Root Access: Yes (By Default)
Bootloader: Unlocked
Recovery: TWRP v2.8.7.0
I made a simple flashable zip which I want to use for installing a different camera app in my device's /system partition. The app works. I've tried it by installing it the traditional way (apk). However I'm not able to flash the zip file. Whenever I try to flash it I get an error
E:Error executing updater binary in zip '/sdcard/cam.zip'
I researched on Google for that error and found many solutions from people facing the same problem. However all those solutions were only for this issue when faced while flashing a new custom ROM, not any other zip. So they were futile for me. Obviously I haven't been wiping anything before flashing my zip file.
My updater-script code:
ui_print("*********************************");
ui_print(" ");
ui_print("********** MIUI Camera **********");
ui_print("*** By Tanmay Vij ***";
ui_print("**********************************");
ui_print("Mounting System...");
run_program(
"/sbin/busybox",
"mount",
"/system"
);
ui_print("Installing Camera...");
package_extract_dir(
"system",
"/system"
);
ui_print("Fixing Permissions...");
set_perm(0, 0, 0644, "/system/app/Redmi1s_MIUICamera.apk");
ui_print("Unmounting System...");
run_program(
"/sbin/busybox",
"umount",
"/system"
);
ui_print("MIUI Camera successfully installed!");
I wonder whether this is gonna happen with me only in TWRP or in other recoveries as well (can't test in CWM as it is not supported for my device). Please correct if any errors in the script..
P.S. I took the update-binary from some random flashable zip as I've heard that it's the same for any zip file..
tvij123 said:
Device details:
YU Yuphoria YU5010
Software: CyanogenMod 12.1 (Nightly)
Root Access: Yes (By Default)
Bootloader: Unlocked
Recovery: TWRP v2.8.7.0
I made a simple flashable zip which I want to use for installing a different camera app in my device's /system partition. The app works. I've tried it by installing it the traditional way (apk). However I'm not able to flash the zip file. Whenever I try to flash it I get an error
E:Error executing updater binary in zip '/sdcard/cam.zip'
I researched on Google for that error and found many solutions from people facing the same problem. However all those solutions were only for this issue when faced while flashing a new custom ROM, not any other zip. So they were futile for me. Obviously I haven't been wiping anything before flashing my zip file.
My updater-script code:
ui_print("*********************************");
ui_print(" ");
ui_print("********** MIUI Camera **********");
ui_print("*** By Tanmay Vij ***";
ui_print("**********************************");
ui_print("Mounting System...");
run_program(
"/sbin/busybox",
"mount",
"/system"
);
ui_print("Installing Camera...");
package_extract_dir(
"system",
"/system" <--- This is the error....!!!
);
ui_print("Fixing Permissions...");
set_perm(0, 0, 0644, "/system/app/Redmi1s_MIUICamera.apk");
ui_print("Unmounting System...");
run_program(
"/sbin/busybox",
"umount",
"/system"
);
ui_print("MIUI Camera successfully installed!");
I wonder whether this is gonna happen with me only in TWRP or in other recoveries as well (can't test in CWM as it is not supported for my device). Please correct if any errors in the script..
P.S. I took the update-binary from some random flashable zip as I've heard that it's the same for any zip file..
Click to expand...
Click to collapse
Try zip me app..
Just make a flashable zip of camera in system...
Unpack it..
Delete the apk file inside..
Paste miui camera apk...
Pack it and flash it that's all..
And extract dir should be /system/app ...
ARAVIND_PAVAN said:
Try zip me app..
Just make a flashable zip of camera in system...
Unpack it..
Delete the apk file inside..
Paste miui camera apk...
Pack it and flash it that's all..
And extract dir should be /system/app ...
Click to expand...
Click to collapse
I've tried Zip Me app.. It works fine.. But this time I wanted to do it from scratch..