Related
What am I doing wrong? I get "error in /tmp/sideload/pkg" when I flash. here is my script:
#BiteBlaze updater scriptui_print("Welcome to mod installer for ReloadedROM")run_program("/sbin/busybox", "mount", "/system");
show_progress(1, 15);
package_extract_dir("system", "/system");
run_program("/sbin/busybox", "umount", "/system");ui_print("Installation Succesful!");
help please!
I also Attached an example of a Win7 SoftKey Mod for more info. I just can't see what I'm missing/doing wrong!
And by the way, this is for my thread as I am testing v1.2 right now and I'm going to release it and the mods to testers once these work... so, motivation!
I can't figure it out ether I read it could be a signature issue .... if you figure it out i can be one of you testers
Sent from my HellfireKindle using Tapatalk 2
The following are the mount points for the Sprint Samsung Galaxy S3:
mmcblk0p1: /Firmware (MODEM.bin) vfat
mmcblk0p7: /Boot
mmcblk0p11: /Efs EXT4
mmcblk0p13: /AMSS.bin
mmcblk0p14: /System EXT4
mmcblk0p15: /Data EXT4
mmcblk0p16: /Persist/Tombstones EXT4
mmcblk0p17: /Cache EXT4
mmcblk0p18: /Recovery
Excellent Thanks
myn said:
Excellent Thanks
Click to expand...
Click to collapse
Come on Myn, we're waiting for some Warm Goodies.
JK, take your time. Glad to see you here.
Yes, I am waiting for some "Warmth", Myn.:fingers-crossed:
anyone know if we're capable of yaffs2? i thought ics was supposed to use it by default.
hoffman1984 said:
anyone know if we're capable of yaffs2? i thought ics was supposed to use it by default.
Click to expand...
Click to collapse
Nevermind... answered my own question. We're not capable of yaffs2 by default. -.-"
Next project anyone? lol
EDIT - looks like Recovery is on 18.
nkawal said:
Come on Myn, we're waiting for some Warm Goodies.
JK, take your time. Glad to see you here.
Click to expand...
Click to collapse
gingson said:
Yes, I am waiting for some "Warmth", Myn.:fingers-crossed:
Click to expand...
Click to collapse
Jeff and I have started our planning to determine what direction we want to go and mods we are aiming for.
We're as anxious as anyone to get going
Question on this, hoping you guys dont mind.
This script is for the international gs3 to flash a theme (framework, systeui) as you can see it points to 0p9.
International code
Code:
show_progress(0.500000, 0);
mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");
package_extract_dir("system", "/system");
unmount("/system");
show_progress(0.500000, 0);
said I changed the code to 14 could I flash a new framework with a zip?
Code:
show_progress(0.500000, 0);
mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system");
package_extract_dir("system", "/system");
unmount("/system");
show_progress(0.500000, 0);
bizdady said:
Question on this, hoping you guys dont mind.
This script is for the international gs3 to flash a theme (framework, systeui) as you can see it points to 0p9.
International code
Code:
show_progress(0.500000, 0);
mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");
package_extract_dir("system", "/system");
unmount("/system");
show_progress(0.500000, 0);
said I changed the code to 14 could I flash a new framework with a zip?
Code:
show_progress(0.500000, 0);
mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system");
package_extract_dir("system", "/system");
unmount("/system");
show_progress(0.500000, 0);
Click to expand...
Click to collapse
I already have a updater-script that works perfectly for our device. Took me a while to make and clean up the bugs but its done I will release when the ROM is ready. For this specific line ill get on my computer and get it for you bud just wait a bit.
Sent from my SPH-L710 using Tapatalk 2
clark44 said:
I already have a updater-script that works perfectly for our device. Took me a while to make and clean up the bugs but its done I will release when the ROM is ready. For this specific line ill get on my computer and get it for you bud just wait a bit.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Sweet! thanks ya I deodexed my stock rom but these damn scripts are always scary. I wanted to theme my systemui.
bizdady said:
Sweet! thanks ya I deodexed my stock rom but these damn scripts are always scary. I wanted to theme my systemui.
Click to expand...
Click to collapse
I am a man of my word put anything you want in system folder and flash away
PROCEED WITH CAUTION!
Anyone know wwhat partition is for the modem?
im on my phone. expect terrible typos.
Hey guys
Hope you don't mind me dropping in here.
I am a bit puzzled about the EFS in these variants of the S3.
I myself have an I9300, so can't investigate myself.
The question at hand is, due to the lack of a "nv_data.bin" in /efs, is it still enough to backup this folder and dump it's partition (mmvblk0p11) to have a proper backup for when the IMEI corrupts and these things....
Background is, I am working on tweaking my app "kTool" to be compatible with these variants of the S3 to make proper EFS backups....
Anyone able to shed some light into the pitch black dark here?
Hi,i have a question
when i modify the archive "update-script" of a zip flasheable , then proceed to install the "x.zip" but the recovery aborts the installation , i only modified in the archive "update-script" the "ui_print" .Eg
Code:
ui_print("Installing the bootanimation ^^")
mount("MTD", "system", "/system");
show_progress(0.500000, 40);
package_extract_dir("system", "/system");
show_progress(0.200000, 10);
ui_print("Install complete!");
unmount("/system");
i also want to ask , the source i used in update-script is correct for the installation of a bootanimation ?
Thanks for reading i hope your answers
lans_98 said:
Hi,i have a question
when i modify the archive "update-script" of a zip flasheable , then proceed to install the "x.zip" but the recovery aborts the installation , i only modified in the archive "update-script" the "ui_print" .Eg
Code:
ui_print("Installing the bootanimation ^^")
mount("MTD", "system", "/system");
show_progress(0.500000, 40);
package_extract_dir("system", "/system");
show_progress(0.200000, 10);
ui_print("Install complete!");
unmount("/system");
i also want to ask , the source i used in update-script is correct for the installation of a bootanimation ?
Thanks for reading i hope your answers
Click to expand...
Click to collapse
in the mount function you must tell the system the file system too! You must say it before the partition type (e.g. MTD). It should be yaffs2 or ext4. So, if it's yaffs2, it should be mount("yaffs2", "MTD", "system", "/system")
Other things are ok. Be sure the boot animation is in /system/media and that you created that zip with store compression type.
---------- Post added at 05:53 PM ---------- Previous post was at 05:28 PM ----------
Ah yes I remembered now... P350 (as well as many low legacy lg & non devices) has yaffs2 file system, so you shall want to definitely add this to your updater-script.
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
hi, guys
i have 2 questions which can be a piece of cake for our galaxy y developers.
1) i read somewhere that we can edit the build.prop to make the make the system think it has an armv7 hardware. What do i have to write in place of armeabi???
2) usually many of us use kitchen to create the roms. can you give me the file you used to add galaxy y to kitchen. i already made one but i don't know what mistake i made but it's not working. you can check my file in attachment. please help.
1 - no you cant - just because you set it to armv7 in build prop you cant magically install armv7 apps and you will find you probably cant install any apps after changing it
2- dont know what you mean but if you are trying to create a rom the way to do it is pull the system using terminal emulator in the phone then copy the system.tar file into the original_update folder then create a working folder from the system.tar file
and please as this is getting really annoying now - Questions go ironically in the Q & A section NOT the general section!
marcussmith2626 said:
1 - no you cant - just because you set it to armv7 in build prop you cant magically install armv7 apps and you will find you probably cant install any apps after changing it
2- dont know what you mean but if you are trying to create a rom the way to do it is pull the system using terminal emulator in the phone then copy the system.tar file into the original_update folder then create a working folder from the system.tar file
and please as this is getting really annoying now - Questions go ironically in the Q & A section NOT the general section!
Click to expand...
Click to collapse
hey marcussmith2626 im saying that when we are creating a rom kitchen turns the update script into updater script using the mount points in the file given with the name of device e.g gt-s5360. i need that file.
and i know we cant install armv7 apps but i still want to know how to edit it.
xday123 said:
hey marcussmith2626 im saying that when we are creating a rom kitchen turns the update script into updater script using the mount points in the file given with the name of device e.g gt-s5360. i need that file.
and i know we cant install armv7 apps but i still want to know how to edit it.
Click to expand...
Click to collapse
you dont need to use any other files
once you have built the rom extract the updater script
open it in notepad++
delete everything above the symlink lines
replace with the following (for stock based roms only)
Code:
show_progress(0.1, 0);
ui_print("Rom Name");
ui_print("By Your Name");
mount("rfs", "EMMC", "/dev/block/stl19", "/system");
mount("rfs", "rfs16", "/dev/block/stl11", "/data");
delete_recursive("/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");
ui_print("Installing system");
package_extract_dir("system", "/system");
ui_print("Installing data");
package_extract_dir("data", "/data");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
package_extract_dir("system", "/system");
you will also need to change the update binary with one for galaxy y - take it from any rom zip for 5360
marcussmith2626 said:
1 - no you cant - just because you set it to armv7 in build prop you cant magically install armv7 apps and you will find you probably cant install any apps after changing it
2- dont know what you mean but if you are trying to create a rom the way to do it is pull the system using terminal emulator in the phone then copy the system.tar file into the original_update folder then create a working folder from the system.tar file
and please as this is getting really annoying now - Questions go ironically in the Q & A section NOT the general section!
Click to expand...
Click to collapse
marcussmith2626 said:
you dont need to use any other files
once you have built the rom extract the updater script
open it in notepad++
delete everything above the symlink lines
replace with the following (for stock based roms only)
Code:
show_progress(0.1, 0);
ui_print("Rom Name");
ui_print("By Your Name");
mount("rfs", "EMMC", "/dev/block/stl19", "/system");
mount("rfs", "rfs16", "/dev/block/stl11", "/data");
delete_recursive("/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");
ui_print("Installing system");
package_extract_dir("system", "/system");
ui_print("Installing data");
package_extract_dir("data", "/data");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
package_extract_dir("system", "/system");
you will also need to change the update binary with one for galaxy y - take it from any rom zip for 5360
Click to expand...
Click to collapse
now thats what i meant. thnks