can i use this guide for creatingrom for sgy
http://forum.xda-developers.com/showthread.php?t=1272270
reply guys
brightjohn007 said:
can i use this guide for creatingrom for sgy
http://forum.xda-developers.com/showthread.php?t=1272270
reply guys
Click to expand...
Click to collapse
for which device u want to create ??
it can work but you should know how to debug errors in case any of them comes
be carefull...dsixdia generated updater script isn't work.
kurotsugi said:
be carefull...dsixdia generated updater script isn't work.
Click to expand...
Click to collapse
wat do u mean by dat .. ??
dat means we will have to paste any other updater-script in meta-inf folder?
well...it seems that you never create a rom for SGY. many people have reported that the script won't work.
write_raw_image PACKAGE:boot.img BOOT:
those script made the installation failed. in mini and some old custom rom, we use this script.
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
it doesn't install the kernel. if we want to install the kernel, we use this one.
package_extract_file("bmlunlock", "bmlunlock");
package_extract_file("boot.img", "boot.img");
set_perm(0, 0, 0755, "bmlunlock");
run_program("bmlunlock");
run_program("/system/bin/dd", "if=boot.img", "of=/dev/block/bml7");
its easier if we copy the script from other rom but we need to copy anything from /system/bin and /system/xbin as well since custom and stock rom have different files on both folder.
Just try customising the ROMS available for now. You can build ROMs when you really get to know everything. You cant just build ROMs outta thin air! You need some experience.
http://forum.xda-developers.com/showthread.php?t=1590330
I made this guide for a rom customization but some people use it as a guidance for make a rom. its not popular since it is difficult for a noob but once we have mastered the basic stuff we can create our own rom.
kurotsugi said:
well...it seems that you never create a rom for SGY. many people have reported that the script won't work.
write_raw_image PACKAGE:boot.img BOOT:
those script made the installation failed. in mini and some old custom rom, we use this script.
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
it doesn't install the kernel. if we want to install the kernel, we use this one.
package_extract_file("bmlunlock", "bmlunlock");
package_extract_file("boot.img", "boot.img");
set_perm(0, 0, 0755, "bmlunlock");
run_program("bmlunlock");
run_program("/system/bin/dd", "if=boot.img", "of=/dev/block/bml7");
its easier if we copy the script from other rom but we need to copy anything from /system/bin and /system/xbin as well since custom and stock rom have different files on both folder.
Click to expand...
Click to collapse
But while creating rom through cygwin meta-inf is creatd already !!
We use updater script nt update script !!
N no point of touching da bin and xbin foldr by a new bee who does nt knw much abt creatng rom
Sent From my lovely FIT..... !! lOvE u Fit
to make things clear...the installer script is of course an edify one. the file name is updater-script. the problem is that the script generated by dsixdia kitchen use 'write_raw_image PACKAGE:boot.img BOOT:' to install the kernel. it didn't work thus make the installation failed. i thought you didn't know this since you haven't make a rom for sgy. well...its up to you to believe or not. you may try to cook a sgy rom as many as you want with dsixda kitchen without modifying the script to prove my words.
Kurotsugi is right that the scripts wont work... I hav worked with the updater script by kitchen but it never installs
Sent from my GT-S5360 using XDA
hell_lock said:
Kurotsugi is right that the scripts wont work... I hav worked with the updater script by kitchen but it never installs
Sent from my GT-S5360 using XDA
Click to expand...
Click to collapse
yup i knw it too !!
So i use ubuntu instead f cygwin!
Ny ideas to make it work so dat i can get back to win7 ??
As i hate ubuntu
Sent From my lovely FIT..... !! lOvE u Fit
kurotsugi said:
to make things clear...the installer script is of course an edify one. the file name is updater-script. the problem is that the script generated by dsixdia kitchen use 'write_raw_image PACKAGE:boot.img BOOT:' to install the kernel. it didn't work thus make the installation failed. i thought you didn't know this since you haven't make a rom for sgy. well...its up to you to believe or not. you may try to cook a sgy rom as many as you want with dsixda kitchen without modifying the script to prove my words.
Click to expand...
Click to collapse
as i am working on dev of Fit rom wil dat script work on fit ?
As one guy told me dat while flashing rom it says error 7 .. I suggestd him to use ubuntu so it may be the script problem ri8 ?
Then pm or gve me a tutorial for correcting the script and make the rom flash
Sent From my lovely FIT..... !! lOvE u Fit
@hell_lock: thanks for the confirmation. dsixda kitchen surely help us to cook the rom. we still can do many things like deodexing, signing, or zipalign, with dsixda kitchen. it runs well in both windows and linux.
btw, ubuntu support multi-OS platform. we can make two separate partition to run both linux and ubuntu in our computer.
---------- Post added at 03:00 AM ---------- Previous post was at 02:50 AM ----------
avilove4u said:
as i am working on dev of Fit rom wil dat script work on fit ?
As one guy told me dat while flashing rom it says error 7 .. I suggestd him to use ubuntu so it may be the script problem ri8 ?
Then pm or gve me a tutorial for correcting the script and make the rom flash
Sent From my lovely FIT..... !! lOvE u Fit
Click to expand...
Click to collapse
the problems doesn't comes from the OS. it comes from the kitchen. it doesn't matter which OS did you use to cook the rom, it will be failed to install the rom to sgy. if the dsixda script didn't work you may replace
write_raw_image PACKAGE:boot.img BOOT:
with
package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
you may also try to use
package_extract_file("bmlunlock", "bmlunlock");
package_extract_file("boot.img", "boot.img");
set_perm(0, 0, 0755, "bmlunlock");
run_program("bmlunlock");
run_program("/system/bin/dd", "if=boot.img", "of=/dev/block/bml7");
you'll need bmlunlock file from custom rom to enable the script and make sure that '/dev/block/bml7' is the correct partition of your kernel .
i wil edit updater script ?
Sent From my lovely FIT..... !! lOvE u Fit
you should check the script used by gal-fit's custom rom for more accurate information. they are basicly same. I learn spesifically only on SGY thus don't know much about custom rom in other device. if you want, you may send me the script to me so that I could analyze the script for you.
yeah these are the scripts ...
http://www.mediafire.com/?5sggs2i0k7g3tou
http://www.mediafire.com/?p0c4a9dpb577q1t
download and tell me...
kurotsugi said:
you should check the script used by gal-fit's custom rom for more accurate information. they are basicly same. I learn spesifically only on SGY thus don't know much about custom rom in other device. if you want, you may send me the script to me so that I could analyze the script for you.
Click to expand...
Click to collapse
you're joking. this script is used to install theme and I think its not an efficient one. the original script is
run_program("/sbin/busybox", "mount", "/system");
delete("/system/framework/framework-res.apk");
package_extract_dir("framework", "/system/framework");
run_program("/sbin/busybox", "umount", "/system");
run_program("/sbin/busybox", "mount", "/system");
delete("/system/app/SystemUI.apk");
package_extract_dir("app", "/system/app");
run_program("/sbin/busybox", "umount", "/system");
ui_print("Applying UOT fonts");
run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("fonts", "/system/fonts");
run_program("/sbin/busybox", "umount", "/system");
we can reduce the script into
run_program("/sbin/busybox", "mount", "/system");
delete("/system/framework/framework-res.apk");
package_extract_dir("framework", "/system/framework");
delete("/system/app/SystemUI.apk");
package_extract_dir("app", "/system/app");
ui_print("Applying UOT fonts");
package_extract_dir("fonts", "/system/fonts");
run_program("/sbin/busybox", "umount", "/system");
we can't use these script to install any rom. its only used to install a theme. you need a script from a custom rom, not a custom theme.
kurotsugi said:
you're joking. this script is used to install theme and I think its not an efficient one. the original script is
run_program("/sbin/busybox", "mount", "/system");
delete("/system/framework/framework-res.apk");
package_extract_dir("framework", "/system/framework");
run_program("/sbin/busybox", "umount", "/system");
run_program("/sbin/busybox", "mount", "/system");
delete("/system/app/SystemUI.apk");
package_extract_dir("app", "/system/app");
run_program("/sbin/busybox", "umount", "/system");
ui_print("Applying UOT fonts");
run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("fonts", "/system/fonts");
run_program("/sbin/busybox", "umount", "/system");
we can reduce the script into
run_program("/sbin/busybox", "mount", "/system");
delete("/system/framework/framework-res.apk");
package_extract_dir("framework", "/system/framework");
delete("/system/app/SystemUI.apk");
package_extract_dir("app", "/system/app");
ui_print("Applying UOT fonts");
package_extract_dir("fonts", "/system/fonts");
run_program("/sbin/busybox", "umount", "/system");
we can't use these script to install any rom. its only used to install a theme. you need a script from a custom rom, not a custom theme.
Click to expand...
Click to collapse
lol while creating the rom it gives this script only !!
I had asked other devs also
And do u want any other custom roms script ??
Sent From my lovely FIT..... !! lOvE u Fit
the dsixda's generated script is this one.
#
# Generated by dsixda's Android Kitchen
# xda-developers.com
#
show_progress 0.1 0
format SYSTEM:
copy_dir PACKAGE:system SYSTEM:
symlink toolbox SYSTEM:bin/cat
symlink toolbox SYSTEM:bin/chmod
symlink toolbox SYSTEM:bin/chown
symlink toolbox SYSTEM:bin/cmp
symlink toolbox SYSTEM:bin/date
symlink toolbox SYSTEM:bin/dd
symlink toolbox SYSTEM:bin/df
symlink toolbox SYSTEM:bin/dmesg
symlink dumpstate SYSTEM:bin/dumpmesg
symlink toolbox SYSTEM:bin/getevent
symlink toolbox SYSTEM:bin/getprop
symlink toolbox SYSTEM:bin/hd
symlink toolbox SYSTEM:bin/id
symlink toolbox SYSTEM:bin/ifconfig
symlink toolbox SYSTEM:bin/iftop
symlink toolbox SYSTEM:bin/insmod
symlink toolbox SYSTEM:bin/ioctl
symlink toolbox SYSTEM:bin/ionice
symlink toolbox SYSTEM:bin/kill
symlink toolbox SYSTEM:bin/ln
symlink toolbox SYSTEM:bin/log
symlink toolbox SYSTEM:bin/ls
symlink toolbox SYSTEM:bin/lsmod
symlink toolbox SYSTEM:bin/lsof
symlink toolbox SYSTEM:bin/mkdir
symlink toolbox SYSTEM:bin/mount
symlink toolbox SYSTEM:bin/mv
symlink toolbox SYSTEM:bin/nandread
symlink toolbox SYSTEM:bin/netstat
symlink toolbox SYSTEM:bin/newfs_msdos
symlink toolbox SYSTEM:bin/notify
symlink toolbox SYSTEM:bin/printenv
symlink toolbox SYSTEM:bin/ps
symlink toolbox SYSTEM:bin/reboot
symlink toolbox SYSTEM:bin/renice
symlink toolbox SYSTEM:bin/rm
symlink toolbox SYSTEM:bin/rmdir
symlink toolbox SYSTEM:bin/rmmod
symlink toolbox SYSTEM:bin/route
symlink toolbox SYSTEM:bin/schedtop
symlink toolbox SYSTEM:bin/sendevent
symlink toolbox SYSTEM:bin/setconsole
symlink toolbox SYSTEM:bin/setprop
symlink toolbox SYSTEM:bin/sleep
symlink toolbox SYSTEM:bin/smd
symlink toolbox SYSTEM:bin/start
symlink toolbox SYSTEM:bin/stop
symlink toolbox SYSTEM:bin/sync
symlink toolbox SYSTEM:bin/top
symlink toolbox SYSTEM:bin/umount
symlink toolbox SYSTEM:bin/uptime
symlink toolbox SYSTEM:bin/vmstat
symlink toolbox SYSTEM:bin/watchprops
symlink toolbox SYSTEM:bin/wipe
set_perm_recursive 0 0 0755 0644 SYSTEM:
set_perm_recursive 0 0 0777 0777 SYSTEM:etc/init.d
set_perm_recursive 0 2000 0755 0755 SYSTEM:bin
set_perm 0 3003 06755 SYSTEM:bin/ip
set_perm 0 3003 02750 SYSTEM:bin/netcfg
set_perm 0 3004 02755 SYSTEM:bin/ping
set_perm 0 2000 06750 SYSTEM:bin/run-as
set_perm_recursive 1002 1002 0755 0440 SYSTEM:etc/bluetooth
set_perm 0 0 0755 SYSTEM:etc/bluetooth
set_perm 1000 1000 0640 SYSTEM:etc/bluetooth/auto_pairing.conf
set_perm 3002 3002 0444 SYSTEM:etc/bluetooth/blacklist.conf
set_perm 1002 1002 0440 SYSTEM:etc/dbus.conf
set_perm 1014 2000 0550 SYSTEM:etc/dhcpcd/dhcpcd-run-hooks
set_perm 0 2000 0550 SYSTEM:etc/init.goldfish.sh
set_perm 0 0 06755 SYSTEM:bin/su
symlink /system/bin/su SYSTEM:xbin/su
set_perm 0 0 0544 SYSTEM:etc/install-recovery.sh
set_perm_recursive 0 0 0755 0555 SYSTEM:etc/ppp
set_perm_recursive 0 2000 0755 0755 SYSTEM:xbin
show_progress 0.1 10
show_progress 0.2 0
write_raw_image PACKAGE:boot.img BOOT:
show_progress 0.2 10
I'm pretty sure that your script is generated by 'uot kitchen', not 'rom kitchen'. you can get a complete installer script for a rom on my post. don't use it to install any rom in gal-fit. use them to for a comparison and learn more about installer script.
Related
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
i m cooking rom..
i cooked flashable zip in uot .
now how can i integrate that flashable zip in my rom zip?
should i just paste it some where and then in updater-script i should add that code (will search on what code to write) to flash it after instalation of my rom [but will this work cuz its writen on the uot kitchen webpage that do not flash on the first boot]
plz help
i did one thing..
i read the update-script
and it was
Code:
ui_print("Applying UOT framework");
run_program("/sbin/busybox", "mount", "/system");
delete("/system/framework/framework-res.apk");
package_extract_dir("framework", "/system/framework");
run_program("/sbin/busybox", "umount", "/system");
run_program("/sbin/busybox", "mount", "/system");
delete("/system/app/SystemUI.apk");
package_extract_dir("app", "/system/app");
run_program("/sbin/busybox", "umount", "/system");
ui_print("Applying UOT fonts");
run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("fonts", "/system/fonts");
run_program("/sbin/busybox", "umount", "/system");
ui_print("Applying UOT bootanimation");
run_program("/sbin/busybox", "mount", "/data");
package_extract_dir("data", "/data");
run_program("/sbin/busybox", "umount", "/data");
i removed the framework-res.apk from my rom zip file
and then pasted the one from the zip i got from uot
then i removed systemui.apk
and pasted from the one i got from uot in to my roms zip file..
and then took the zip file and pasted in my cell,
flashed the rom.zip in via cwm recovery ..
unforrtunately i dont have a status bar :O plz some one gimme a hand and guide a lil to integrating uot and my rom .. and making one flashable zip
ny one der to help ? :'(
will someone help me plzzzz??/
sorry, i just replied on your other thread, lol. After you have cooked up your uot theme, download it and copy it to your sd card. then just go into cwm recovery and flash the .zip of the theme u built, any mods you made in the uot kitchen will be applied to your rom. Thats the simplest way to do it.
hi
I want to cook my own rom. I downloaded a stock rom and extract the files. I want to make it cwm flashable. There are many files and i dont know which files are needed to make it cwm flashable . These are the files: arm11boot, csc.rfs, mibib, oemsbl, qcsbl, amss, recovery.img, boot.img and system.rfs.
Also i want to convert it to ex4 and use phiexz kernel. I downloaded phiexz kernel and there is a boot.img, a system folder and a META-INF folder. I think i must replace the stock roms boot.img by the boot.img from phiexz and copy the system folder from phiexz's kernel to the system folder of the stock rom. But what is the META-INF folder?
I already searched for guides to cook own rom but all of them are for modifying cwm flashable custom roms and not stock roms. It would be nice if someone can help me
Sorry for my bad english
Take system.rfs from stock, boot.img from phiexz stockkernel
Extract system.rfs with terminal in linux or on windows use magic iso
Take the META-INF folder from another rom and edit it to be like yours.
Sent from my GT-S5660 using xda premium
okay thank you
but how do i sign the zip file? In cwm the installation aborts...
i tried to sign with dsixdas kitchen but no sucess...
Sorry for my bad English
You can flash unsigned zips from recovery
Wich error you get in cwm?
Sent from my GT-S5660 using xda premium
i get this error when Signature Check is enabled:
Code:
Finding update package...
Opening update package...
Verifiying update package...
E:failed to seek in /sdcard/MyRom.zip (Invalid argument)
E:signature verification failed
Installation aborted.
and this when Signature Check is disabled:
Code:
Finding update package...
Opening update package...
E:Can't open /sdcard/MyRom.zip
(bad)
Installation aborted.
//Edit: Now i get a "Status 7" Error
Status 7 is updaterscript error, you didnt modify it..
Follow the guides
Sent from my GT-S5660 using xda premium
okay the installation is working
but i dont know how to set the permissions and how to "symlink". Because of that the rom doesnt boot.
I have already copied the "set permission and symlink script" from this page http://www.androidpit.de/de/android/forum/thread/439522/Workshop-Rom-koecheln and this page http://forum.xda-developers.com/showthread.php?t=936175 but it doesnt work
this is my script without set permission and so on
Code:
ui_print("");
ui_print("");
ui_print("Installation of MyRom");
ui_print("------by [email protected]");
ui_print("");
#Mounting
ui_print("Mounting...");
ui_print("mount /system");
run_program("/sbin/busybox", "mount", "/system");
ui_print("mount /data");
run_program("/sbin/busybox", "mount", "/data");
ui_print("mount /cache");
run_program("/sbin/busybox", "mount", "/cache");
ui_print("Mounting finished");
ui_print("-----------------");
ui_print("");
#Wiping
ui_print("Wiping...");
ui_print("wipe /system");
delete_recursive("/system");
ui_print("wipe /data");
delete_recursive("/data");
ui_print("wipe /cache");
delete_recursive("/cache");
ui_print("Wiping finished");
ui_print("-----------------");
ui_print("");
#Installation
ui_print("Installing...");
package_extract_dir("system", "/system");
ui_print("Installation finished");
ui_print("-----------------");
ui_print("");
#InstallationKernel
#Thanks to phiexz :)
ui_print("Installing Kernel...");
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
ui_print("Installating Kernel finished");
ui_print("-----------------");
ui_print("");
#Unmount
ui_print("Unmounting...");
ui_print("unmount /system");
run_program("/sbin/busybox", "unmount", "/system");
ui_print("unmount /data");
run_program("/sbin/busybox", "unmount", "/data");
ui_print("unmount /cache");
run_program("/sbin/busybox", "unmount", "/cache");
ui_print("Unmounting finished");
ui_print("-----------------");
ui_print("");
ui_print("Installation of MyRom finished");
ui_print("Please Reboot Your Phone");
emyaz said:
okay the installation is working
but i dont know how to set the permissions and how to "symlink". Because of that the rom doesnt boot.
I have already copied the "set permission and symlink script" from this page http://www.androidpit.de/de/android/forum/thread/439522/Workshop-Rom-koecheln and this page http://forum.xda-developers.com/showthread.php?t=936175 but it doesnt work
this is my script without set permission and so on
Code:
ui_print("");
ui_print("");
ui_print("Installation of MyRom");
ui_print("------by [email protected]");
ui_print("");
#Mounting
ui_print("Mounting...");
ui_print("mount /system");
run_program("/sbin/busybox", "mount", "/system");
ui_print("mount /data");
run_program("/sbin/busybox", "mount", "/data");
ui_print("mount /cache");
run_program("/sbin/busybox", "mount", "/cache");
ui_print("Mounting finished");
ui_print("-----------------");
ui_print("");
#Wiping
ui_print("Wiping...");
ui_print("wipe /system");
delete_recursive("/system");
ui_print("wipe /data");
delete_recursive("/data");
ui_print("wipe /cache");
delete_recursive("/cache");
ui_print("Wiping finished");
ui_print("-----------------");
ui_print("");
#Installation
ui_print("Installing...");
package_extract_dir("system", "/system");
ui_print("Installation finished");
ui_print("-----------------");
ui_print("");
#InstallationKernel
#Thanks to phiexz :)
ui_print("Installing Kernel...");
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
ui_print("Installating Kernel finished");
ui_print("-----------------");
ui_print("");
#Unmount
ui_print("Unmounting...");
ui_print("unmount /system");
run_program("/sbin/busybox", "unmount", "/system");
ui_print("unmount /data");
run_program("/sbin/busybox", "unmount", "/data");
ui_print("unmount /cache");
run_program("/sbin/busybox", "unmount", "/cache");
ui_print("Unmounting finished");
ui_print("-----------------");
ui_print("");
ui_print("Installation of MyRom finished");
ui_print("Please Reboot Your Phone");
Click to expand...
Click to collapse
1. way too much ui prints
2 you dont do wipe /system (ref. to other roms for right FORMAT values)
3 make sure boot.img is called boot.img and not kernel or else
4 the /sbin/busybox does problably not exist in stock roms so that doesnt work, enter unmount codes manually from another roms script
5 permissions have to be right
6 ever heard of symlinks? need to be added too..
that said, you do better use a rom as base, add your desired apps to /system/app and flash that without publishing on XDA. much easier
Just use cygwin and dsixda android kitchen... after cooking change mtd format/mount lines to ext4 from other rom ...
Wysyłane z mojego GT-S5660 za pomocą Tapatalk 2
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.
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