Develop Bugs

Creating an update zip

Hi am trying to create an update sip for my theme but everytime i try to flash it says syntax error in update script. This is my code can anyone help me.
show_progress(0.500000, 0);
mount("MTD", "data", "/data");
package_extract_dir("data", "/data");
unmount("/data");
mount("MTD", "system", "/system");
package_extract_dir("system", "/system");
set_perm(0, 0, 0755, 0644, "/system/framework/framework-res.apk");
set_perm(0, 0, 0755, 0644, "/system/app/Launcher2.apk");
show_progress(0.100000, 0);
unmount("/system");

[DEV Q] updater-script and edify

can someone smarter than me help me or point me in the right direction to convert my updater-scripts to edify. i think im sort of getting it but i want to make sure because i'm not a programmer. for instance, is the update-binary file required or just updater-script? also, the code posted below, it what i've come up with for flashing my themes, is it correct? and will it work with the new recoveries?
Code:
ui_print("Preparing system for istallation...");
ui_print("Wiping Cache / Dalvik...");
delete_recursive("/cache");
delete_recursive("/data/dalvik-cache");
ui_print("Installing Project_Bliss HD...");
show_progress(0.100000, 60);
package_extract_dir("system", "/system");
show_progress(1.000000, 0);
i am unsure whether or not i will have to mount the specific partitions for data and cache for this to work. i can always leave that part out but the less the person flashing needs to do the better. if i do have to mount in the script will the code below work for just a simple theme flash.
Code:
ui_print("Preparing system for installation...");
run_program("/sbin/mount", "/dev/block/mtdblock4", "/system");
ui_print("Installing Project_Bliss HD...");
show_progress(0.100000, 60);
package_extract_dir("system", "/system");
show_progress(1.000000, 0);

Anyone?
10 char

No one? Hmmmm?

I'm still not too too familiar but I have played around with them a little. From what I understand so far the binary is what the recovery actually uses. dsixda's kitchen will make them and you can have it convert update to updater scripts automatically.
Usually I just look at how others have done it and go from there.
[KITCHEN][DEC. 7 '10] HTC Android Kitchen, v0.110 [Linux / Mac / Windows]
I had another link somewhere that gave all of the different commands and their syntax but I can't find it for nothing atm.
git hub - android edify readme

Not sure that link (edify readme) is working--- is this the same one you were referring to?
https://github.com/koush/android_bootable_recovery/blob/eclair/edify/README

try this bro...
http://forum.xda-developers.com/showthread.php?t=936175

[Q] PLEASE HELP with Integrating Data Apps to CM7 Rom Zips for flashing purposes

Hi all,
I was just wondering whether there is someone here can help with my problem trying to integrate data apps into any and all future custom rom zips... A couple of good people at Modaco helped me with the coding to add into the updater-script file so that I can modify the CM7 custom rom zips so that after flashing this modified rom zip it will install additional apps into the data apps storage, however, in my current progress to flashing my modified cm7-buzz-rom-247.zip, none of the data apps will install, I found they just get extracted into the data/app folder!!!...
Here below is the coding in red that was given to me to add into the updater-script file so that I can add data apps to the phones internal app data storage, can someone here please help me with this problem and correct any of the coding below... I have very little coding experience, so can not see what the problem is that is causing the data apps to just be extracted into the data/app folder instead of installing them!!!...
Thanks in advance! ^_^
|
|
|
|
show_progress(0.200000, 0);
format("yaffs2", "MTD", "system");
mount("yaffs2", "MTD", "system", "/system");
package_extract_dir("recovery", "/system");
package_extract_file("check_data_app", "/tmp/check_data_app");
set_perm(0, 0, 0777, "/tmp/check_data_app");
run_program("/tmp/check_data_app");
format("yaffs2", "MTD", "userdata");
mount("yaffs2", "MTD", "userdata", "/data");
delete_recursive("/data");
package_extract_dir("data", "/data");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
delete_recursive("/system");
package_extract_dir("system", "/system");
symlink("busybox", "/system/xbin/[", "/system/xbin/[[",
|
|
|
|
unmount("/system");
unmount("/data");
Click to expand...
Click to collapse

UPDATE!!!
Problem should sorted... So yeah!... THANKS for all the help and replies to this post and problems

[TOOL/APP] [Dual-Boot][uBoot] Nexus DBB [v3.0]

Since the dual-boot kernels require some specialized modifications to the ROM zip that are leading to a little confusion, I threw together an app that will take the zip for the "second" ROM and modify it to be compatible.
Currently the included file browser can be used to select files, or you can open a third-party file browser, such as Root Explorer, and use the send option on the file you want modified. Once the file is modified, the required folders in /data/ are checked and created, if they are not already there.
Direct installation is now available as a post-modification option. This feature is in beta and uses a specialized class to read and translate the existing updater-script commands into busybox commands. This has only received limited testing, so please backup (including cache if coming from a previous dual-boot configuration)
Available through Litter Box on Google Play
Also built into SKU Kernel Remote - The All-In-One Modification Masterpiece

Re: [TOOL / APP] Dual-Boot Builder
Tested with Ubuntu and AIRKernel. Install the core Ubuntu zip, modify the device one, wipe cache, install the modified zip then the kernel.
Sent from my Galaxy Nexus using Tapatalk 2

Exuse me , I want to try this app but I don't understand if this app require to have a dualboot-compatible-kernel before to start , I've a gsm-maguro gnex whit official cm 10.1 and ak kernel 801, and I want a dual boot with miu can you help me???

diaboliko.hacker said:
Exuse me , I want to try this app but I don't understand if this app require to have a dualboot-compatible-kernel before to start , I've a gsm-maguro gnex whit official cm 10.1 and ak kernel 801, and I want a dual boot with miu can you help me???
Click to expand...
Click to collapse
You need a dual-boot kernel. The app modifies the second ROM, for example MIUI, to install properly for the dual-boot kernel to work. There are dual-boot kernels http://forum.xda-developers.com/showthread.php?t=2183721 and http://forum.xda-developers.com/showpost.php?p=39087629&postcount=1040

Re: [TOOL / APP] Dual-Boot Builder
I am preparing a new version that includes a walkthrough video of using the app. It seems the version on market had already started getting comments from people trying to use the app with OTAs. They really need to open that reply feature to all developers. Too many oblivious downloaders out there.
Sent from my Galaxy Nexus using Tapatalk 2

twistedumbrella said:
Since the dual-boot kernels require some specialized modifications to the ROM zip that are leading to a little confusion, I threw together an app that will take the zip for the "second" ROM and modify it to be compatible.
Currently the included file browser can be used to select files, or you can open a third-party file browser, such as Root Explorer, and use the send option on the file you want modified. Once the file is modified, the required folders in /data/ are checked and created, if they are not already there.
The next step is direct installation. Copying to cache instead of system is easy enough, but translating all of the additional install garbage in an updater-zip into live commands is where it gets tricky. This could be bypassed with the commands to gather a list of installs for recovery and send the zips there, but this will require some research to make sure one app works with every recovery.
Note to mods: The plan is to have the app become capable of also installing the kernel, the ROM, etc directly. This is a development thread.
Edit: There is a version available at https://play.google.com/store/apps/details?id=com.loungecat.dualbuild for automatic updates
Click to expand...
Click to collapse
You're now in the Galaxy Nexus Index.
Thanks for your interesting project, hope the videos will appear soon. :good:

twistedumbrella said:
I am preparing a new version that includes a walkthrough video of using the app. It seems the version on market had already started getting comments from people trying to use the app with OTAs. They really need to open that reply feature to all developers. Too many oblivious downloaders out there.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Very much looking forward for a walkthrough :good:

[TOOL / APP] Dual-Boot Builder
http://m.youtube.com/watch?v=YJ2AJctp4Cw
I have a basic video walk through that shows the process, but I am setting up to do something with better explanation instead of just the visual.

Yah, fancy graphical interface!
Attachment removed to prevent confusion, please see OP

i got FC
im using xylon unofficial+starkissed dual
so i find rom and extracting...and got fc

I am also having fc when trying to extract rom

When i flash the fix rom .... Error status 7 in cwm !!!!! why?

Re: [TOOL / APP] Dual-Boot Builder [3/16/13 1:20 AM EST]
vange said:
I am also having fc when trying to extract rom
Click to expand...
Click to collapse
Version 1.1 had an issue with not cleaning up the folder properly during extraction. This was fixed in 1.2 and the newest one (1.4) took care of when the line had additional parameters.
Pasquale91fg said:
When i flash the fix rom .... Error status 7 in cwm !!!!! why?
Click to expand...
Click to collapse
What are the contents of the original updater-script?
Sent from my Galaxy Nexus using Tapatalk 2

So just to get this correct:
1. Make sure dual boot kernel is installed.
2. Fix Rom with apk.
3. Reboot and install fixed rom.
Correct?

Re: [TOOL / APP] Dual-Boot Builder [3/16/13 1:20 AM EST]
iluvamk said:
So just to get this correct:
1. Make sure dual boot kernel is installed.
2. Fix Rom with apk.
3. Reboot and install fixed rom.
Correct?
Click to expand...
Click to collapse
Fix the rom
Reboot and install the rom then the dual-boot kernel
Sent from my Galaxy Nexus using Tapatalk 2

Re: [TOOL / APP] Dual-Boot Builder [3/16/13 1:20 AM EST]
Is there a free version available? I'm not sure xda allows only links to a paid versions in op.

Re: [TOOL / APP] Dual-Boot Builder [3/16/13 1:20 AM EST]
eqjunkie829 said:
Is there a free version available? I'm not sure xda allows only links to a paid versions in op.
Click to expand...
Click to collapse
Then perhaps you should read it more carefully

Re: [TOOL / APP] Dual-Boot Builder [3/16/13 1:20 AM EST]
Sorry, I didn't click on the second link to see what it was.

I'm getting a Status 7 error also on 2nd rom install using TWRP.
Ist rom updater script to be modified:
show_progress(0.500000, 0);
ui_print("Erasing System...");
format("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system", "0", "/system");
ui_print("Mounting System...");
mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system", "/system");
show_progress(0.500000, 40);
ui_print("Installing System...");
package_extract_dir("system", "/system");
ui_print("Creating Symlinks...");
symlink("/factory/hdcp.keys", "/system/vendor/firmware/hdcp.keys");
symlink("/system/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/[[",
After running ROM through Dual-Boot Builder:
show_progress(0.500000, 0);
ui_print("Erasing System...");
format("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/cache", "0", "/system");
ui_print("Mounting System...");
mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/cache", "/system");
show_progress(0.500000, 40);
ui_print("Installing System...");
package_extract_dir("system", "/system");
ui_print("Creating Symlinks...");
symlink("/factory/hdcp.keys", "/system/vendor/firmware/hdcp.keys");
symlink("/system/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/[[",
The only thing I can figure is that lines 5 do not have the "0" as do lines 3. Could this be what's causing Error 7? Very interested in getting this going.

Re: [TOOL / APP] Dual-Boot Builder [3/16/13 1:20 AM EST]
iluvamk said:
I'm getting a Status 7 error also on 2nd rom install using TWRP.
Ist rom updater script to be modified:
show_progress(0.500000, 0);
ui_print("Erasing System...");
format("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system", "0", "/system");
ui_print("Mounting System...");
mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system", "/system");
show_progress(0.500000, 40);
ui_print("Installing System...");
package_extract_dir("system", "/system");
ui_print("Creating Symlinks...");
symlink("/factory/hdcp.keys", "/system/vendor/firmware/hdcp.keys");
symlink("/system/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/[[",
After running ROM through Dual-Boot Builder:
show_progress(0.500000, 0);
ui_print("Erasing System...");
format("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/cache", "0", "/system");
ui_print("Mounting System...");
mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/cache", "/system");
show_progress(0.500000, 40);
ui_print("Installing System...");
package_extract_dir("system", "/system");
ui_print("Creating Symlinks...");
symlink("/factory/hdcp.keys", "/system/vendor/firmware/hdcp.keys");
symlink("/system/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/[[",
The only thing I can figure is that lines 5 do not have the "0" as do lines 3. Could this be what's causing Error 7? Very interested in getting this going.
Click to expand...
Click to collapse
It's not removing the format it's replacing it. I think it's probably checking that second and not first which would end up missing it

Is there a Fire TV Stick Lite (sheldon) updater-script rw?

Quick question relating to the rom aspect of things. Does anyone have an updater-script with rw access i.e. with the (mantis) roms? I'm compiling an OTA patched rom with no success. Constant ever ending boot loops unless I were to modify the updater-script. Here's the code down below for the (mantis) if someone would like to convert to (sheldon) for modified roms
Code:
(getprop("ro.product.device") == "mantis" || getprop("ro.build.product") == "mantis") || abort("This package is for \"mantis\" devices
this is a \"" + getprop("ro.product.device") + "\".");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp");
set_metadata("/tmp/backuptool.sh", "uid", 0, "gid", 0, "mode", 0755);
mount("ext4", "EMMC", "/dev/block/platform/soc/11230000.mmc/by-name/system", "/system", "");
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
ui_print("Copying system image...");
block_image_update("/dev/block/platform/soc/11230000.mmc/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print("Copying vendor image...");
block_image_update("/dev/block/platform/soc/11230000.mmc/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat", "vendor.patch.dat");
mount("ext4", "EMMC", "/dev/block/platform/soc/11230000.mmc/by-name/system", "/system", "");
delete("/system/bin/efuse_check.sh",
"/system/bin/ewriter");
unmount("/system");
ui_print("Updating TZ...");
package_extract_file("images/tz.img", "/dev/block/platform/soc/11230000.mmc/by-name/tee1_real");
package_extract_file("images/tz.img", "/dev/block/platform/soc/11230000.mmc/by-name/tee2_real");
ui_print("Copying kernel...");
package_extract_file("boot.img", "/dev/block/platform/soc/11230000.mmc/by-name/boot");
package_extract_dir("magisk", "/dev/tmp/install");
set_metadata("/dev/tmp/install/install-magisk.sh", "uid", 0, "gid", 0, "mode", 0755);
run_program("/dev/tmp/install/install-magisk.sh");
mount("ext4", "EMMC", "/dev/block/platform/soc/11230000.mmc/by-name/system", "/system", "");
run_program("/sbin/mkdir", "/system/addon.d");
run_program("/tmp/backuptool.sh", "restore");
unmount("/system");

Skel40 said:
Quick question relating to the rom aspect of things. Does anyone have an updater-script with rw access i.e. with the (mantis) roms? I'm compiling an OTA patched rom with no success. Constant ever ending boot loops unless I were to modify the updater-script. Here's the code down below for the (mantis) if someone would like to convert to (sheldon) for modified roms
Code:
(getprop("ro.product.device") == "mantis" || getprop("ro.build.product") == "mantis") || abort("This package is for \"mantis\" devices
this is a \"" + getprop("ro.product.device") + "\".");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp");
set_metadata("/tmp/backuptool.sh", "uid", 0, "gid", 0, "mode", 0755);
mount("ext4", "EMMC", "/dev/block/platform/soc/11230000.mmc/by-name/system", "/system", "");
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
ui_print("Copying system image...");
block_image_update("/dev/block/platform/soc/11230000.mmc/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print("Copying vendor image...");
block_image_update("/dev/block/platform/soc/11230000.mmc/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat", "vendor.patch.dat");
mount("ext4", "EMMC", "/dev/block/platform/soc/11230000.mmc/by-name/system", "/system", "");
delete("/system/bin/efuse_check.sh",
"/system/bin/ewriter");
unmount("/system");
ui_print("Updating TZ...");
package_extract_file("images/tz.img", "/dev/block/platform/soc/11230000.mmc/by-name/tee1_real");
package_extract_file("images/tz.img", "/dev/block/platform/soc/11230000.mmc/by-name/tee2_real");
ui_print("Copying kernel...");
package_extract_file("boot.img", "/dev/block/platform/soc/11230000.mmc/by-name/boot");
package_extract_dir("magisk", "/dev/tmp/install");
set_metadata("/dev/tmp/install/install-magisk.sh", "uid", 0, "gid", 0, "mode", 0755);
run_program("/dev/tmp/install/install-magisk.sh");
mount("ext4", "EMMC", "/dev/block/platform/soc/11230000.mmc/by-name/system", "/system", "");
run_program("/sbin/mkdir", "/system/addon.d");
run_program("/tmp/backuptool.sh", "restore");
unmount("/system");
Click to expand...
Click to collapse
What have you modified on the ROM?

SweenWolf said:
What have you modified on the ROM?
Click to expand...
Click to collapse
The OTA patches like the (mantis) to bypass updating

Skel40 said:
The OTA patches like the (mantis) to bypass updating
Click to expand...
Click to collapse
This update script should also work for sheldon, what files are you transplanting, maybe they are incompatible. Check Logs. I think you should never use official updator-script anyways.

can you test these patches on PS7273 (2622), for Sheldon/p
make sure you delete original odex and vdex files of these after replacing.
and also wipe cache / Dalvik cache just to be on safe side.
Changes:
Accessibility Services for 3rd party apps re-enabled.
Package protection is disabled.