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
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
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
Hello,
Sorry for my poor english, I try as much as possible.
I followed this tutorial on my Galaxy Nexus with the official ROM JB 4.2.2 and ubuntuTouch Saucy in 2nd ROM.
http://forum.xda-developers.com/showthread.php?t=2183721
I use the kernel lk_gnex_Hyuni_Dual_jb42_v.zip provided.
But when I boot ROM on the 2nd, I am running CyanogenMod logo loop (bootloop).
I have no CM ROM installed on my phone.
I download :
- saucy-preinstalled-touch-armel+maguro.zip
- saucy-preinstalled-touch-armhf.zip
- Kernel : http://www.4shared.com/zip/dE6mqokX/lk_gnex_Hyuni_Dual_jb42_v.html?
I fix install script :
- In "saucy-preinstalled-touch-armel+maguro.zip" i modified "/META-INF/com/google/android/updater-script" by
Code:
assert(getprop("ro.product.device") == "maguro" || getprop("ro.build.product") == "maguro");
mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
set_perm(0, 0, 0644, "/tmp/backuptool.functions");
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
show_progress(0.500000, 0);
[STRIKE]format("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system", "0", "/system");[/STRIKE]
mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/[B]cache[/B]", "/system");
package_extract_dir("system", "/system");
symlink("/factory/hdcp.keys", "/system/vendor/firmware/hdcp.keys"); ...
...
show_progress(0.200000, 10);
package_extract_file("boot.img", "/dev/block/platform/omap/omap_hsmmc.0/by-name/boot");
show_progress(0.100000, 0);
ui_print("Fixing fs_size in crypto footer...");
assert(samsung.fs_size_fix());
unmount("/system");
- In "saucy-preinstalled-touch-armhf.zip" i modified "/META-INF/com/google/android/updater-script" by
Code:
ui_print("");
ui_print("Welcome to the Ubuntu RootFS Updater");
ui_print("");
show_progress(1.000000, 60);
ui_print("Mounting system and userdata partitions...");
[B]mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/cache", "/system");[/B]
[B]mount("ext4", "EMMC", "/dev/block/mmcblk0p12","/data");[/B]
set_progress(0.100000); ...
...
- Push files to my phone.
- Reboot in recovery with TWRP.
- Wipe cache.
- Install in the order saucy-preinstalled-touch-armel+maguro.zip & saucy-preinstalled-touch-armhf.zip.
- Install this kernel
- I reboot; 1st ROM ok; But the 2nd I have a sceen locked to CyanogenMod logo (instead of ubuntu).
Have you a answer? Thx
About the dual booting issue: post in that dev thread, better chances to get help IMO, since it's a specific issue; and you're seeing cyanogenmod boot anim because Ubuntu touch is based of it
a maguro wrote this.
bk201doesntexist said:
About the dual booting issue: post in that dev thread, better chances to get help IMO, since it's a specific issue; and you're seeing cyanogenmod boot anim because Ubuntu touch is based of it
a maguro wrote this.
Click to expand...
Click to collapse
Ok thank you.
I can't post to dev forum, because of newbie status of my account.
jelebi said:
Ok thank you.
I can't post to dev forum, because of newbie status of my account.
Click to expand...
Click to collapse
Engage in conversation with other xda members, ask pertinent questions in the right places, learn and help others learn or redirect them to the available resources, stickied on this forum.
a manta wrote this.
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