Related
Im trying to make a flashable zip but it seems the X2 works diffrently than others...i tried using the examples given in forums and it doesn't work...can someone give me a quick example?
I was trying to make a script to install a bootanimation and it just hangs on installing.
Here is my update-script
Code:
ui_print("=============================================");
ui_print(" =========== ");
ui_print(" ================= ");
ui_print(" ");
ui_print(" ## ## ## ## ## ## ");
ui_print(" ### ### ## ## ## ## ");
ui_print(" #### #### ## ## ## ## ");
ui_print(" ## ### ## ##### ### ");
ui_print(" ## ## ## ## ## ## ");
ui_print(" ## ## ## ## ## ## ");
ui_print(" ## ## ## ## ## ## ");
ui_print(" ");
ui_print(" ================= ");
ui_print(" =========== ");
ui_print(" ");
ui_print(" ======Blue Droid Eye BootAnimation===== ");
ui_print(" ");
ui_print(" ======Created by MattFox27===== ");
ui_print("=============================================");
ui_print("Installing ...");
show_progress 0.1 0
copy_dir PACKAGE:media SYSTEM:media
show_progress 0.1 100
I can't get it to install...any help please
File...http://db.tt/nGms7W0p
From what I've done with all the bootanimations is push the files to system/media
Sent from my DROID X2 using XDA App
Ya i have made some bootanimations and im trying to make it easy for people to install them but my zip scripts fail...im using uato zip maker program...weird...i will post example later
Are you making them in Linux. I tried a few times but when I copied them to the phone they always were blank. Maybe a link to point me in the right direction? Sorry to ask a question on top of yours.
Sent from my DROID X2 using XDA App
Mr_GreenJeans said:
Are you making them in Linux. I tried a few times but when I copied them to the phone they always were blank. Maybe a link to point me in the right direction? Sorry to ask a question on top of yours.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
No im using windows...sometimes i get an error like E: something or it will look like its installing but just sit there...i have it all on my other computer and im at work right now so i can't post my script...lame sorry
R you talking about animations or boot logos?
Sent from my DROID X2 using XDA App
script posted...
Mr_GreenJeans said:
R you talking about animations or boot logos?
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Boot Animations, not logos i make them all the time and usually just copy them over with file explorer but im trying to make a flashable zip just to learn and what works normally on android phones seems to not work on X2 because other examples of update-script i have looked at for X2 stuff looks more complex then what i have in OP which is what i got from searching around.
bump...for some help.
try Amend scripting your example uses edify. ui_print is edify
Your not setting permissions. Ill look for the syntax ina second.
I'm going to make a tutorial on making these kind of files when I get the chance(and figure out the permissions).
By chance is the file named updater-script? Just curious.. and does the rest of the script work(ie you see the progress bar)?
First off, you have to mount /system if you're going to copy anything to it.
Second, pick update-script style or updater-script style. The updater-script style is the one I use, and the update-script style is the one that nitro uses (if you want examples). You are using both, so of course it's going to hang.
@Peperm1nt, I appreciate you trying to help, but what exactly are you trying to set permissions for? You don't have a file pointer in that instruction.
Try this:
(Make sure you are naming this updater-script.)
Code:
mount("ext3", "EMMC", "/dev/block/mmcblk0p12", "/system");
ui_print("Installing ...");
show_progress(0,0);
delete("/system/media/bootanimation.zip");
set_perm(0, 0, 0755, "/system/media/bootanimation.zip");
show_progress(10.000000, 1);
ui_print("Done");
ui_print("Now reboot");
0vermind said:
@Peperm1nt, I appreciate you trying to help, but what exactly are you trying to set permissions for? You don't have a file pointer in that instruction.
Click to expand...
Click to collapse
lmao, I just noticed that. I edited it after I reread the script and for some reason in my head, I put the link haha. My bad ill edit it since you got it cleared up.
EDIT: I think you forgot to add unmount in your fix 0vermind.
EDIT#2:
update-script is amend scripting and DOES NOT REQUIRE update-binary
updater-script is edify scripting and it REQUIRES update-binary
SO in other words,
amend=
Code:
show_progress 0.1 0
delete SYSTEM:media/bootanimation.zip
copy_package SYSTEM: SYSTEM:
set_perm 0 0 0755 SYSTEM:media/bootanimation.zip
show_progress 10.000000 1
edify=
Code:
mount("ext3", "EMMC", "/dev/block/mmcblk0p12", "/system");
ui_print("Installing ...");
show_progress(0,0);
delete("/system/media/bootanimation.zip");
copy("/system", "/system");
set_perm(0, 0, 0755, "/system/media/bootanimation.zip");
show_progress(10.000000, 1);
ui_print("Done");
ui_print("Now reboot");
NOTE: ui_print is not a command in amend; only edify! And these will only work if your folders are set up correctly in the update.zip.
bootanimation.zip is in
Code:
UPDATE.ZIP(the actual zip file)>system/media/bootanimation.zip
;otherwise, you would need to edit the locations in the script. Someone please correct the copy command if it is incorrect in the edify script. hope this helps.
OK...so question on permissions. I created a zip file (Amend) that I install after I flash a rom...basically contains my ringtones that installs into system/media/ringtones and installs my titanium backup apk into the system/app folder. I do not set permissions, just copy them over and everything works fine. Now if I were to copy a bootanimation over as well and not set permissions, what would happen? How do we determine what needs permissions to be set? when I look at my ringtones ...the permissions are exactly like the other ringtones.
Sent from my DROID X2 using XDA App
mjdavis871 said:
OK...so question on permissions. I created a zip file (Amend) that I install after I flash a rom...basically contains my ringtones that installs into system/media/ringtones and installs my titanium backup apk into the system/app folder. I do not set permissions, just copy them over and everything works fine. Now if I were to copy a bootanimation over as well and not set permissions, what would happen? How do we determine what needs permissions to be set? when I look at my ringtones ...the permissions are exactly like the other ringtones.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
all those files need permissions. what is your update-script syntax?
Peperm1nt said:
all those files need permissions. what is your update-script syntax?
Click to expand...
Click to collapse
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
show_progress 0.1 10
I install my .ogg ringtones and my titanium backup apk using this update-script with no issues
Sent from my DROID X2 using XDA App
that is a correct script to a point i guess.... here use this.
Code:
show_progress 0.1 0
delete_recursive SYSTEM:media
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:media
show_progress 1.0 10
this is assuming the zip structure is correct.
.zip>system/media
media contents:
audio(folder)
bootanimation.zip
audio contents:
alarms
notifications
ringtones
and you have the respected files within those folders that you want.
also, if you have any other files in other folders.. system/app etc. you need to fix those as well.
Peperm1nt said:
that is a correct script to a point i guess.... here use this.
Code:
show_progress 0.1 0
delete_recursive SYSTEM:media
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:media
show_progress 1.0 10
this is assuming the zip structure is correct.
.zip>system/media
media contents:
audio(folder)
bootanimation.zip
audio contents:
alarms
notifications
ringtones
and you have the respected files within those folders that you want.
also, if you have any other files in other folders.. system/app etc. you need to fix those as well.
Click to expand...
Click to collapse
The million dollar question is why does this still work without setting permissions?
Sent from my DROID X2 using XDA App
.. does your phone show the custom boot animation? tibu redoes everything you set it to. So if permissions were set a certain way, then it would put them back. BUT TiBu has nothing to do with that folder.
Peperm1nt said:
.. does your phone show the custom boot animation? tibu redoes everything you set it to. So if permissions were set a certain way, then it would put them back. BUT TiBu has nothing to do with that folder.
Click to expand...
Click to collapse
I haven't tried a custom boot animation yet...just ringtones and titanium backup. I'm gonna give it a shot...and let you know.
Sent from my DROID X2 using XDA App
Hi friends of XDA,
I created this tutorial especially for noobs who would like to know how the clockworkmod uses the .zip
file and what and all goes into the process of flashing a .zip file and mainly about the format and syntax used in updater-script.
first is first!
#include
/*
* I am not responsible for bricked devices, dead SD cards or
* thermonuclear war.
* do some research if you have any concerns.
* YOU are choosing to make these modifications.
* yes, i copied this disclaimer from FXP because it is cool and i am lazy!
*/
now what is the updater-script and update-binary present in the META-INF>com>google>android in any flashable zip package?
1. updater-script - it is just a text file which contains all the commands which tells the clockworkmod what to do with the given
zip file. the updater-script is written in the edify scripting language.
2. update-binary - it is a binary which is requiered by the clockworkmod to translate the human readable format of the updater-
script to machine readable format for execution of the updater-script in our device.
exploring the updater-script:
now let's start exploring the updater-script !
1. open the updater script with notepad++ (strongly recommended)
2. now i will try and explain commands generally used in the updater-script,
assert(getprop("ro.product.device") == "ST15i" || getprop("ro.build.product") == "ST15i" ||
getprop("ro.product.device") == "ST15a" || getprop("ro.build.product") == "ST15a" ||
getprop("ro.product.device") == "smultron" || getprop("ro.build.product") == "smultron");
the above bunch of lines checks the device model to confirm that the zip file is flashed on the device
for which it is specifically created for. These bunch of lines are very important because it prevents
flashing of zip file which is not intended for the device hence avoiding any problems due to flashing
the wrong zip. for example the above lines checks for the value of "ro.product.device" and
"ro.build.product"in the build.prop file of the already existing rom in the device, if any of the three
defined values ST15i, ST15a, smultron are found it will continue with the next line of updater-script
otherwise flashing gets aborted with error in getprop.
format("yaffs2", "MTD", "system", "/system");
the above command explains itself, it is used to format the specified partition
syntax explanation:
format - the main command to direct the cwm to format using the following parameters
"yaffs2" - filesystem type used in the device
"MTD" - type of the partition used in the file system
"system" - name of the partition to be formatted
"/system" - location of the partition to be formatted
ui_print("Format Completed");
the above command is also self explanatory, it directs the cwm to display the following text
enclosed in double quotes in the user interface (display).
after succesful formatting it displays "Format Completed" in the device screen.
mount("yaffs2", "MTD", "system", "/system");
the mount command directs the cwm to mount the following file system and the following partition
the syntax is just as explained in the format command except that this command mounts the
defined partition whereas the format command formats the defined partition.
let's review what we have done till now,
1. we have checked the device to confirm that this is the device for which we created the zip.
2. we have formatted the system partition of the device.(this is only done when a new complete rom is being flashed, for flashing mods you
should never format the system partition!)
3. we have mounted the system partition of the device.
now let's continue,
package_extract_dir("system", "/system");
this command searches for the directory (folder) named "system" in the root of the zip file and
copies all the content of the "system" folder from the zip file into the "/system" partition
which is already mounted by the previous mount command.
remember the structure of the file system in the zip file and the "/system" partition of the device must be always identical.
for eg., you have created a mod by editing the systemUI.apk and you want to flash it, the system UI.apk resides in "/system/app"
so the structure of the file system in the update zip should be "/system/app/systemUI.apk"
ie., the update zip should contain folder named "system" at the root of it and folder named "app" inside the "system" folder and the
modded "systemUI.apk" must be placed inside the "app" folder.
package_extract_file("autoroot.sh", "/tmp/autoroot.sh");
this command searches for the file named "autoroot.sh" in the root of the zip file and
copies the file to "/tmp" folder and names it as "autoroot.sh" (here it does not change the name)
symlink("mksh", "/system/bin/sh");
the above command creates a symlink.
okay, now let's see about symlinks,
symlink is nothing but shortcuts, for example if a file is requiered in two different places instead of copy pasting the file
in two different locations, the file is copied to one of the two locations and in the other location a shortcut to the file(symlink)
is created. the source and the symlink can have different names (actually this is the prime use of symlinks).
to explain in a noob friendly manner,
take the above symlink, it creates a shortcut(symlink) for the command "mksh" and places it in the path of the operating system.
the shortcut(symlink) directs to the file "/system/bin/sh" , so whenever the os gets a request to execute the "mksh" command, the actual
binary that gets excuted will be "/system/bin/sh" .
creating symlinks saves a lot of space because instead of copying the whole file and placing it in requiered places we are just
creating shortcuts which directs to the source file which can be placed anywhere in the file system (generally placed in the path of the os).
set_perm_recursive(0, 0, 0755, 0644, "/system");
the above command is used to set permission recursively for the files and folders present inside a folder (in this case for "/system" folder).
syntax explanation:
0 - uid - it defines that the following permission is set for the user id 0 .
0 - gid - it defines that the following permission is set for the group id 0 .
0775 - dirmode - it defines that 0775 permission to set to directories contained within the specified directory.
0644 - filemode - it defines that 0644 permission to set to files contained within the specified directory.
"/system" - target directory to set the above mentioned permissions.
set_perm(0, 3003, 06755, "/system/bin/ip");
the above command is used to set permission for a individual file (in this case for "/system/bin/ip" file).
syntax explanation:
0 - uid - it defines that the following permission is set for the user id 0 .
3003 - gid - it defines that the following permission is set for the group id 3003 .
06775 - it defines that 06775 permission to set to the specific file.
"/system/bin/ip" - target file to set the above mentioned permissions.
run_program("/tmp/autoroot.sh");
remember the file autoroot.sh from package_extract_file command?
that file is supposed to be a shell script, the above command directs cwm to execute the "autoroot.sh" shell script present in "/tmp" folder.
unmount("/system");
the unmount command directs the cwm to unmount the following partition
the syntax is just as explained in the mount command except that this command unmounts the
defined partition whereas the mount command mounts the defined partition.
Okay now going into slightly complex and/or not widely used updater-script commands,
Ifelse
Syntax:
Ifelse(condition),(do_this),(else_do_this);
Example:
ifelse mount("yaffs2", "MTD", "system", "/system") == "system", ui_print("Mounted!"), ui_print("Mount Failed!");
Ifelse command can be explained simply as asking the system to do something based on the result of a condition.
From the example:
The ifelse command would attempt to mount the MTD partition named "system" to "/system".
If the mounting process succeeds (the condition), the script will display "Mounted!", else it will display "Mount Failed!"
abort()
It just abort's the script execution
Note: it is usually paired with some other command for example the getprop command or with ifelse.
Independently specifying abort() in the updater-script will kill the script abruptly right there so use this command carefully.
ALWAYS LEAVE A BLANK LINE AT THE END OF THE update-script (if the code contains 50 lines then 51 lines should be visible
in the notepad++ including a blank line after the end of the script)
ALWAYS REMEMBER TO SET THE EOL (end of line) CONVERSION OF updater-script
IN UNIX FORMAT BEFORE SAVING (notepad++ > edit > EOL conversion > UNIX format)
the above mentioned commands are just basic edify scripting commands which are generally used in updater-script.
for detailed scripting and coding in edify scripting language check out the following sources:
source of update-binary
introdution to edify
http://forum.xda-developers.com/wiki/Edify_script_language
scratchpad-documenting-edify-commands-for-android-updater-scritps
http://forum.xda-developers.com/showthread.php?t=1290062
HIT THANKS IF I HAVE HELPED YOU!
Nice tut bro
bandarigoda123 said:
Nice tut bro
Click to expand...
Click to collapse
thanks friend
Great piece of work buddy.... :good:
This is good for me:beer:
Sent from my HTC EVO 3D X515m using xda app-developers app
What l must to change here? I got error 7
Sent from my HTC EVO 3D X515m using xda app-developers app
analoncarkg said:
What l must to change here? I got error 7
Sent from my HTC EVO 3D X515m using xda app-developers app
Click to expand...
Click to collapse
Have you set the eol conversion to Unix format as described?
Have you left a blank line as described?
Make sure that Cyanogenmod Rom is for your device. Then try flashing again.
If the above mentioned steps fails and you still get a status 7 error or assert failed error then make SURE that the Rom is really specific for your device and remove the first three lines from the script
Remove lines starting From "assert" to "smultron");
Make sure that after removing the above specified three lines there is no blank line at the start of the script And flash again
Usually status 7 errors are due to bad formatting of the updater-script or in rare cases it is due to corrupted or incomplete download of the Rom.
hit thanks if I've helped!
sent from my smultron
here are some more commands if you like:
sleep();
show_progress(1.0, "1000"); more on this here: http://forum.xda-developers.com/showthread.php?t=1290062
if/ then/ endif; syntax
iONEx said:
here are some more commands if you like:
sleep();
show_progress(1.0, "1000"); more on this here: http://forum.xda-developers.com/showthread.php?t=1290062
if/ then/ endif; syntax
Click to expand...
Click to collapse
Thanks iONEX I knew them before but didn't add sleep and show_progress because they are just mere cosmetic changes and don't serve any serious purpose anyways I'll add them after understanding and testing
And about if/then/endif/ifelse , generally they are used rarely in updater-script but I'll add them anyways after understanding testing!
Thanks!
hit thanks if I've helped!
sent from my smultron
If anyone is interested in the source of the update-binary, I've added the link to it in the first post
hit thanks if I've helped!
sent from my smultron
Hello! How exactly should I write in the updater-script if I need to make the system folder rewriteable and then delete the existing framework-res.apk from system/framework and then copy a new framework-res.apk from the .zip file, then change the permissions of it and finally make the system folder write-only again?
My "idea" is something like this:
1. Content of the updater-script:
ui_print("Please wait...");
mount("MTD", "system", "/system");
delete("/system/framework/framework-res.apk");
package_extract_dir("system", "/system");
set_perm(0, 0, 04755, "/system/framework/framework-res.apk");
ui_print("Done");
unmount("/system");
2. Make a signed .zip file that would contain:
- system\framework\framework-res.apk
- META-INF\com\google\android\updater-script
3. Run the .zip from memory card via recovery
Would it work like this?
Note: My phone is bricked because of framework-res.apk and USB debugging is off, so this is the only way I could unbrick it.
You must have a unmodified updater-script in your meta-inf folder right?? Paste the "mount" command syntax here. It must be in the first few lines.
#pitchblack5691#
Actually I don't. I have to create it from scratch.
No. . . You need a meta-inf folder to work with which contains the signature files and a update-binary to create a flashable zip.
#pitchblack5691#
I only created those folders and an updater-script file and then I packed it & signed it using Update Zip Packager 3.0. The only update-binary file that I have is the one that's included with Update Zip Packager.
Code:
mount("MTD", "system", "/system");
ui_print("started. . . .");
delete("/system/framework/framework-res.apk");
package_extract_dir("system", "/system");
set_perm(0, 0, 0644, "/system/framework/framework-res.apk");
unmount("/system");
ui_print("finished");
This should work and you need a meta-inf folder extracted from some flashable zip. You can't create a meta-inf folder from scratch without using signature files and update-binary.
EDIT: what you said above will work. You either should have a meta-inf folder with signature files or a signing software.
And you don't have to give 755 permissions to an app because even though they are apps, technically they are not executed and only read from so no need for 755 permission. 644 permission should suffice and it's the default permission for a system app. . . 755 permissions is only useful for executable binaries and scripts.
#pitchblack5691#
I've just tried it. It returns this error:
...
Installing update...
E:Error in /tmp/sideload/package.zip
(Status 2)
Installation aborted.
E:Can't find misc
What does it mean please?
What code exactly you are using in the updater-script?? Paste the full code and paste the name of files present in the zip file in a hierarchical order.
#pitchblack5691#
The .zip contains these files:
Code:
META-INF\CERT.RSA
META-INF\CERT.SF
META-INF\MANIFEST.MF
META-INF\com\google\android\update-binary
META-INF\com\google\android\updater-script
system\framework\framework-res.apk
The code of updater-script:
Code:
mount("MTD", "system", "/system");
ui_print("started. . . .");
delete("/system/framework/framework-res.apk");
package_extract_dir("system", "/system");
set_perm(0, 0, 0644, "/system/framework/framework-res.apk");
unmount("/system");
ui_print("finished");
Bootloader unlocked?? Custom kernel?? Or installed cwm in a bootloader locked phone??? Looks like your cwm is not working properly. . .
#pitchblack5691#
Hi,
I use JB 4.1.2 ROM in 2nd ROM on my I9100.
Sometime, i want to have an approximate LITE version of ROM i modded in 2nd ROM.
For that, i move some apks from \data\sec_data\ to \data\sec_data\retired\ (retired is a personal name given to this folder, name it as you want), and as a purist maniac, i delete the correspondant symlink in\system\app\.
At this point, another maniac purist can tell me that it's not necesary to delete LN apk's files from \system\app\ folder too because if real apks are removed from \data\sec_data\ they become unexecutable during 2nd ROM playing even with LNs unecesary residual files in \system\app\.
After some tests, i have to re-imput some apks from \retired\ folder i move them, to their \data\sec_data\ original folder, but symlink are also necesary in \system\app\ folder too else they never work .
So, how to re-enable LN apk's files in \system\app\ from APKs present in \data\sec_data\ folder ?
According Many40 in this source which give me the idea to create this thread, there is a way to execute shell command from terminal emulator, to create a symlink from source location to desired location of destination folder :
ln -s TARGET_PATH SYMLINK_PATH
for example :
ln -s /data/sec_data/program.apk /system/app/program.apk
I tried <> method to automate the symlink managment and i usually flash a ZIP i make for this :
create_data_sec_data-vs_system_app_symlinks.zip
In this flasher, we have :
create_data_sec_data-vs_system_app_symlinks.zip\META-INF\com\google\android\updater-script :
show_progress(0.900000, 120);
ui_print("*********************************");
ui_print("SYMLINKING DATA_SEC_DATA to SYSTEM-APP FOLDER");
mount("ext4", "EMMC", "/dev/block/mmcblk0p12", "/preload");
mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p10", "/data");
mount("ext4", "EMMC", "/dev/block/mmcblk0p7", "/cache");
show_progress(0.100000, 0);
sleep(1);
package_extract_dir("tmp", "/tmp");
set_perm(0, 0, 0755, "/tmp/create_sec_data_symlinks");
run_program("/tmp/create_sec_data_symlinks");
show_progress(0.100000, 0);
sleep(1);
unmount("/system");
unmount("/data");
unmount("/cache");
unmount("/preload");
ui_print("Symlinks OK");
and
create_data_sec_data-vs_system_app_symlinks.zip\tmp\create_sec_data_symlinks :
#!/system/bin/mksh
mount -o remount rw /system
cd /data/sec_data
# Can't create array with /sbin/sh, hence we use mksh
apk_list=( `ls | grep .apk` )
odex_list=( `ls | grep .odex` )
items=${apk_list[*]}" "${odex_list[*]}
for item in ${items[@]}
do
ln -s /data/sec_data/$item /system/app/$item
done
the 2nd file in attachment ( create_preload_symlink_system_app_vs_system_app_symlinks.zip) is for users of JB 4.1.2 ROM in 1rst position with managed APKs in \preload\symlink\system\app\ folder symlinked to \system\app\
Hope many much user of JB 4.1.2 ROM in 2nd position and expect my method acceptable .
Thanks
Other Idea for dual-boot (i think dorimanx v8 only)
I want to thank Nemotatu for his Rom you can see here and for his great idea which consist to use a script to to move system APKs
from /preload/symlink/system/app/ to /data/sec_data/ and re-symlink them too.
In his original script, he moves /preload/symlink/system/app/*.apk to /data/app/app/*.apk , i prefer use the path
/data/sec_data/ as usual.
QUESTION :
Instead of rescript updater-script in a ZIP of a ROM to adapt it for 2nd position ROM, can we flash original ZIP
without any modification on updater-script, reboot recovery a loose dorimanx kernel but reboot recovery
once more time, have a reflash of dorimanx V8.xx, reboot recovery one more too, and finally flash this script
to move /preload/symlink/system/app/*.apk to /data/sec_data/*.apk and symlink them too to /system/app/ as
usual for 2nd ROM (also in 1rst habitual position, it's not my pb here)
Can we have a discuss here about this idea ? other purpose about this?
what modification i give :
In attachments, the original file from Nemotatu, and mine.
After reflexion, it could be an idea to avoid two JB 4.1.2 in dualboot ?
imagine we flash this script on 1rst rom and with dorimanx v8.xx, clone it after in 2nd rom.....
what append if you flash another jb 4.1.2 rom in 1rst rom and dorimanx v8.xx after, is you cloning process gave before make 2nd rom working ?
Great work, bro = )
Edit:little more explanation to my script
1st moving system apps ( not the symlinked apks) like Superuser,... etc to /tmp.
2- cleaning /system/app folder from old links
3- moving preload apps to data/app/app
4- re-symlink from /data
5- restore system apps from /tmp
Whenever I try flash a new nightly, my custom sounds go away. So, I created an update file with the ringtones, and some notification sounds. But every time I try to install the file, I get a error 0 in CWM. Here is my script file, what am I doing wrong. I use Notepad++ for editing the file. Any help is appreciated. Thanks.
ui_print("............................");
ui_print("............................");
ui_print("Mounting system...");
run_program("/sbin/busybox", "mount", "/system");
ui_print("Copying files...");
package_extract_dir("system", "/system");
ui_print("Unmounting system...");
run_program("/sbin/busybox", "umount", "/system");
ui_print("Installation done!.........");
prabs99 said:
Whenever I try flash a new nightly, my custom sounds go away. So, I created an update file with the ringtones, and some notification sounds. But every time I try to install the file, I get a error 0 in CWM. Here is my script file, what am I doing wrong. I use Notepad++ for editing the file. Any help is appreciated. Thanks.
ui_print("............................");
ui_print("............................");
ui_print("Mounting system...");
run_program("/sbin/busybox", "mount", "/system");
ui_print("Copying files...");
package_extract_dir("system", "/system");
ui_print("Unmounting system...");
run_program("/sbin/busybox", "umount", "/system");
ui_print("Installation done!.........");
Click to expand...
Click to collapse
Usually a status 0 error refers an incompatible update-binary in the zip file. I would recommend replacing it with a compatible one (Can be pulled from a ROM or other flashable zip that you know will flash successfully), then re-signing the zip file, will usually fix this error.
Sent from my SCH-I535 using xda premium
I pulled the update-binary from the cm 10.1.2 nightly. I know it works, because I can flash it, but the update file I created does not work.
shimp208 said:
Usually a status 0 error refers an incompatible update-binary in the zip file. I would recommend replacing it with a compatible one (Can be pulled from a ROM or other flashable zip that you know will flash successfully), then re-signing the zip file, will usually fix this error.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
prabs99 said:
I pulled the update-binary from the cm 10.1.2 nightly. I know it works, because I can flash it, but the update file I created does not work.
Click to expand...
Click to collapse
Interesting, do you have the correct folder structure for the flashable such as META-INF->com->android and google folder->google folder->android->update-binary and updater script? Also do you have the correct folder structure for the ringtones and sounds? If you have named the .zip file update.zip try renaming it to something else (For example ringtonessounds.zip). Finally not that this should make a difference by try replacing:
Code:
run_program("/sbin/busybox", "umount", "/system");
With:
Code:
unmount("/system");
Is busybox installed in your device since you use busybox commands in your updater-script?
Also try to sign your zip file,, download signapk and run this command:
Code:
java -Xmx512M -jar signapk.jar -w testkey.x509.pem testkey.pk8 <Your zip file> <Your result zip file>
ensure you have installed java environment,,
..
shimp208 said:
Interesting, do you have the correct folder structure for the flashable such as META-INF->com->android and google folder->google folder->android->update-binary and updater script? Also do you have the correct folder structure for the ringtones and sounds? If you have named the .zip file update.zip try renaming it to something else (For example ringtonessounds.zip). Finally not that this should make a difference by try replacing:
Code:
run_program("/sbin/busybox", "umount", "/system");
With:
Code:
unmount("/system");
Click to expand...
Click to collapse
It was my directory structure that was bad. Thanks for your help.
Sent from my Galaxy Nexus using xda app-developers app
majdinj said:
Is busybox installed in your device since you use busybox commands in your updater-script?
Also try to sign your zip file,, download signapk and run this command:
Code:
java -Xmx512M -jar signapk.jar -w testkey.x509.pem testkey.pk8 <Your zip file> <Your result zip file>
ensure you have installed java environment,,
..
Click to expand...
Click to collapse
Have busybox installed. I am signing the zip with the test key. I don't have a private key.
Sent from my Galaxy Nexus using xda app-developers app
Hello Everyone
I created a small flashable zip in order to remove the apps I don't want COMPLETELY from /system/app but for no apparent reason it doesn't remove anything.
Here's what I have wrote inside the updater-script file :
Code:
unmount("/system");
unmount("/data");
unmount("/preload");
ui_print(" ");
ui_print("Mounting partitions..");
run_program("/sbin/mount", "-t", "auto", "/system");
run_program("/sbin/mount", "-t", "auto", "/data");
run_program("/sbin/mount", "-t", "auto", "/cache");
ui_print("Partitions mounted.");
ui_print("Starting debloat process..");
ui_print("Removing apps from /system/app");
delete_recursive("/system/app/BookmarkProvider");
run_program("/sbin/rm", "-rf", "system/app/Browser");
run_program("/sbin/rm", "-rf", "system/app/FaceUnlockService-res");
run_program("/sbin/rm", "-rf", "system/app/NfcNci");
ui_print(" ");
ui_print("Removal Process Finished.");
ui_print(" ");
ui_print("Cleaning Cache");
run_program("/sbin/rm", "-rf", "/cache");
ui_print(" ");
ui_print("Unmounting partitions: /system /data /cache");
unmount("/data");
unmount("/cache");
unmount("/system");
ui_print(" ");
It's mind boggling because the script runs flawlessly when I flash it through Recovery except it doesn't remove ANYTHING!
Some one please tell me what am I doing wrong here?
I've also attached the flashable zip file.
Device : Samsung Galaxy Note 3
Rom : LineageOS (Rooted with Magisk)
Recovery : TWRP 3.4.0-1 (Latest)
Busybox : Installed through Magisk.
Thanks.
Excerpt of known commands in OTA updater-script
unmount
Syntax
unmount <mount_point>
Description
Unmounts the filesystem mounted at mount_point.
run_program
Syntax
run_program <program-file> [<args> ...]
Description
Run an external program included in the update package.
delete_recursive
Syntax
delete_recursive <file-or-dir1> [... <file-or-dirN>]
Description
Delete a file or directory with all of it's contents recursively.
mount
Syntax
mount <fs_type, partition_type, name, mount_point>
Description
Mounts a filesystem of fs_type at mount_point. partition_type must be one of these: system , userdata, etc.pp.
This in mind the main failure in your script is misuse of run_program, IMHO
Spoiler
Mount.
You could test those using terminal first...
But why not just use TWRP's file manager?
jwoegerbauer said:
Excerpt of known commands in OTA updater-script
unmount
Syntax
unmount <mount_point>
Description
Unmounts the filesystem mounted at mount_point.
run_program
Syntax
run_program <program-file> [<args> ...]
Description
Run an external program included in the update package.
delete_recursive
Syntax
delete_recursive <file-or-dir1> [... <file-or-dirN>]
Description
Delete a file or directory with all of it's contents recursively.
mount
Syntax
mount <fs_type, partition_type, name, mount_point>
Description
Mounts a filesystem of fs_type at mount_point. partition_type must be one of these: system , userdata, etc.pp.
This in mind the main failure in your script is misuse of run_program, IMHO
Click to expand...
Click to collapse
Can you please point out to where the problem comes from precisly and what's wrong with the run_program command I wrote? Sorry I'm total noob
CXZa said:
Spoiler
Mount.
You could test those using terminal first...
But why not just use TWRP's file manager?
Click to expand...
Click to collapse
I appreciate your help but I still cannot figure it out. This is just a snip from a big list of apps that I try to debloat so that's why I created this flashable zip.
Marvino. said:
I appreciate your help but I still cannot figure it out. This is just a snip from a big list of apps that I try to debloat so that's why I created this flashable zip.
Click to expand...
Click to collapse
Deleting those with file manager is much faster than typing that script...
How about mounting them first in TWRP and then running the script? Of course edit it 1st so it skips the mounting part...
BTW, yours looks like very much like this one.
Easy debloat script for Oreo Stock ROMs
I haven't seen anyone post any easy debloat script, so here is my personal one for N8. This is made for OREO - but it will work for Nougat-based ROMs too, as long as the file names haven't been changed. This could also work well for S8, S9 and...
forum.xda-developers.com
Marvino. said:
Can you please point out to where the problem comes from precisly and what's wrong with the run_program command I wrote? Sorry I'm total noob
Click to expand...
Click to collapse
Why not simply carefully read my post? And also why do you ignore that within an updater-script the built-in mount and delete_recursive functions have to be used, instead of run_program - what indeed serves a complete other purpose?
Again:
Mount
This built-in command mounts a partition, so if you want to operate on files within system and/or data partition you have to mount system partition, data for data partition with this built-in function.
To mount system :
mount(“ext4″, “EMMC”, “/dev/block/mmcblk0p5″, “/system”);
Here mmcblk0p5 is the name of system partition for mtk 6589 chipsets (this name varies from device to device)
To mount data:
mount(“ext4″, “EMMC”, “/dev/block/mmcblk0p7″, “/data”); (partition name varies from device to device)
Take the time and look inside here.
CXZa said:
BTW, yours looks like very much like this one.
Easy debloat script for Oreo Stock ROMs
I haven't seen anyone post any easy debloat script, so here is my personal one for N8. This is made for OREO - but it will work for Nougat-based ROMs too, as long as the file names haven't been changed. This could also work well for S8, S9 and...
forum.xda-developers.com
Click to expand...
Click to collapse
Only to have said it: The updater-script, which is offered with the link - what also circulates under different names on the internet - is crap: the author(s) have no idea how to write a updater-script.
@Marvino.
Code:
delete_recursive("/system/app/BookmarkProvider");
delete_recursive("/system/app/Browser");
delete_recursive("/system/app/FaceUnlockService-res");
delete_recursive("/system/app/NfcNci");
jwoegerbauer said:
Only to have said it: The updater-script, which is offered with the link - what also circulates under different names on the internet - is crap: the author(s) have no idea how to write a updater-script.
Click to expand...
Click to collapse
Well, it might have worked in his device okay. Busybox mount use fstab in /etc. Not normally there in TWRP. So one should use device path as well.
The hardiest part I guess is to select what to remove really. What might work for some, might make a nice little sushi tray for another...
Have never understood it why people use true EDIFY conformant synthax when creating an OTA package: An OTA script can get realized as plain shell script - what makes things drastically easier and device independent.
BTW: All EDIFY functions can get replaced by equivalent user-written functions. See also here,