dsixda's Android Kitchen - Now for Huawei Ideos X6
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own custom ROMs for Huawei Ideos X6 variants with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project dsixda started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android.
[MAIN PAGE for kitchen] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
PROCEDURE
First, you need a Huawei Ideos X6 variant device with a ClockworkMod custom recovery. The kitchen supports the Spice Mi410, but should also support most of its variants, such as the CherryMobile Magnum, WellcoM A99, Cincinnati Bell Huawei Ascendi X.
Visit the Android Kitchen thread to download the kitchen. Then, follow the link to the FAQ which will show you how to install it on Windows, Linux or Mac OS X. Ensure you read the FAQ carefully.
Support for Huawei Ideos X6 variants:
Download attached file ( Huawei Ideos X6 related files.zip) and extract it.
Copy mi410 in kitchen's "tools/edify_defs" folder.
Copy IdeosX6_permissions_correction.plugin in kitchen's "scripts/plugins" folder.
DO NOT RENAME THESE FILES
IMPORTANT: If your device is not Spice mi410 then so as to verify your variant of the Huawei Ideos X6 works in the kitchen, read this post.
Put your base (stock/custom) ROM(s) under the original_update folder. There is support for the following formats which can be placed in that folder (you can place multiple ROMs there):
Stock firmware:
First unpack nb0 file using nb0-utils.jar tool. And rename respective images of system and boot as boot.img and system.img before placing them in original_update folder.
(Follow this guide to unpack nb0 files and use nb0-utils.jar attached)
Custom ROM:
ZIP file originally created by the kitchen from the stock firmware (NOTE: The kitchen does NOT support custom ROMs created through other methods, due to potential file structure incompatibility issues)
Nandroid backup from ClockworkMod recovery
system.img and boot.img (Currently .tar backups support is not included for nandroid backup from CWM 5)
Here are some basic steps to creating your first ROM after you have your base of files under original_update (more options are available in the kitchen):
Start the kitchen with: ./menu
Create a working folder (by choosing your base ROM)
Root your ROM
Add Busybox
In the Advanced options menu: De-odex your ROM (Please be sure to wipe Data and Cache before installing this custom ROM, if you do this. And this removed camera app from app drawer of my system - I don't know why)
Remove bloatware system apps from /system/app (Please note that some system apks are required for normal functioning of system. So delete any apk if you are sure that it does not affect your system.)
When you are done with all modding run plugin script "IdeosX6_permissions_correction.plugin" from Advanced Options menu >>> Miscellaneous options / Plugin scripts option, if you have not done this before.
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu.
Some notes:
IMPORTANT: Open generated custom ROM zip using any archive viewer and open updater-script from META-INF/com/google/android folder and check that it has "format("ext3", "EMMC", "/dev/block/mmcblk0p7");" as a format command. If it is not the same then read this post before flashing this ROM.
IdeosX6_permissions_correction.plugin has some property changes specific for Stock ROM / Andro-ID ROM. So, this plugin or cooked ROM will not support for MIUI or Cyanogenmod ROM's releases. OR it might have some non functional features.
Just select the defaults whenever you are asked about something in the kitchen and are unsure whether to type 'y' or 'n'.
A more detailed procedure for installing and using this kitchen is given in the FAQ in Posts 3 of the main Android Kitchen thread. (FAQ - page 1 link given above)
There are lots of questions answered in the FAQ in Post 4 of the main Android Kitchen thread. (FAQ - page 2 link given above) So please go through that first if you have any issues.
ACKNOWLEDGEMENT
dsixda for his contributions in developing this amazing kitchen. Please donate to him.
dsixda again since I have used his thread from Galaxy S forum as a template for this by adding few modifications. I hope he/any moderator does not have any problems with that.
Vladimir Baryshnikov for his nb0-utis.jar file.
All of you guys for having patience.
*****Let the Game begin*****
Support for Huawei Ideos X6 variants other than Spice MI 410
Support for Huawei Ideos X6 variants other than Spice MI 410
Open build.prop file from /system/ folder for your working device in any text viewer/root explorer
Search for property ro.product.device value.
If the property value/ device name is other than mi410 then download Huawei Ideos X6 related files.zip from first post and extract mi410 file from it.
Rename mi410 to property value for ro.product.device
For example:
..
..
ro.product.model=FIH-FB0
ro.product.brand=FIH
ro.product.name=FIH-FB0
ro.product.device=FB0
ro.product.board=qcom
..
..
If this is how your build.prop file looks then rename mi410 to FB0
Please note that this file name is case sensitive. So do not rename it to fb0 instead.
Now copy this file in kitchen's tools/edify_defs folder.
Reserved for future use, if any.
hi
great effort thanks for the same & i have added this to the rollup thread
how to start what to do first of all ..? downloaded all the files now how to run menu file ..?
ok i found out how to do thanx already ...
ohhhh tooo much complicated ... ahhh
when i double click the desktop shortcut for cygwin.. bang nothing happens ... why i have java already installed too
some one gonna reply to me plzz... i want to know how to set up a kitchen i read full guide bt nothing happning
kshitij_bhatt said:
how to start what to do first of all ..? downloaded all the files now how to run menu file ..?
ok i found out how to do thanx already ...
ohhhh tooo much complicated ... ahhh
when i double click the desktop shortcut for cygwin.. bang nothing happens ... why i have java already installed too
Click to expand...
Click to collapse
Sorry, I use Linux machine (Ubuntu), so can not help much with Cygwin installation.
Anyway if you have installed JAVA Development kit (JDK) before cygwin then you use this guide to add path of jdk in your cygwin's .bash_profile:
http://forum.xda-developers.com/showpost.php?p=14474038&postcount=4877
P.S. Or if you are wiling to, install dual boot linux distro on your machine. If you have enough disk space.
Updated the kitchen thread with link to this thread, thanks
Napstar said:
Sorry, I use Linux machine (Ubuntu), so can not help much with Cygwin installation.
Anyway if you have installed JAVA Development kit (JDK) before cygwin then you use this guide to add path of jdk in your cygwin's .bash_profile:
http://forum.xda-developers.com/showpost.php?p=14474038&postcount=4877
P.S. Or if you are wiling to, install dual boot linux distro on your machine. If you have enough disk space.
Click to expand...
Click to collapse
ok u can tell me the linux method too as i use a dual boot and on ubuntu i had installed jdk 6 already so u can tell me that thing too plzzz i wanna do some thing now
and also java jdk is already installed on windows too...
and plzz also explain what this one wanna say i found it pretty interesting
http://forum.xda-developers.com/showthread.php?t=622666
kshitij_bhatt said:
ok u can tell me the linux method too as i use a dual boot and on ubuntu i had installed jdk 6 already so u can tell me that thing too plzzz i wanna do some thing now
Click to expand...
Click to collapse
As already stated in post #1, ensure you read the FAQ carefully. I have taken many steps to describe the installation with as much detail as possible in the FAQ.
dsixda said:
As already stated in post #1, ensure you read the FAQ carefully. I have taken many steps to describe the installation with as much detail as possible in the FAQ.
Click to expand...
Click to collapse
thanx i had read that before posting there are certain things i didn't understood thats why i asked for help i had read all the faq..
the basic problem i faced in window part that cygwin doesn't do anything though i have jdk already installed ... second in the faq there is no guide about linux except downloading java... so how can i do further if i dont have the guide
by the words cygwin doesn't do any thing is that when i double click the desktop shortcut ... it pops up a window and with an error that i cant even read it closes it self...
by taking a screen shoot i come to know that the error is in attachment
kshitij_bhatt said:
second in the faq there is no guide about linux except downloading java... so how can i do further if i dont have the guide
Click to expand...
Click to collapse
What do you mean there is no guide about Linux? There is a complete section in the FAQ on installing Linux under Windows, with VirtualBox and with Wubi; plus there is a section on how to install the kitchen if you already have Ubuntu on a dedicated Linux partition (for which you only really need to install JDK). This is all stuff I tested individually before describing it in the FAQ for people to follow.
NOTE -- I didn't go into detail on how to install Linux on a separate partition. I would doubt a new user would go that far (I'd recommend Cygwin or Windows virtualization of Linux), but even if they did, there is information on the internet on how to do it. I trust people know this (i.e. using Google). I don't want the FAQ to get into one long spoonfeeding exercise.
BTW - didn't you just say you had Ubuntu installed on a partition already?
by the words cygwin doesn't do any thing is that when i double click the desktop shortcut ... it pops up a window and with an error that i cant even read it closes it self...
by taking a screen shoot i come to know that the error is in attachment
Click to expand...
Click to collapse
I don't know about this, make sure you followed the instructions in the readme.txt carefully. I have never had problems installing Cygwin with my provided tools, as I have tried it on 3 different PCs which are either running XP or Windows 7. I didn't do anything extra, I just followed all the info I provided in the FAQ. Go to the Cygwin support pages for help if your PC is having trouble.
dsixda said:
What do you mean there is no guide about Linux? There is a complete section in the FAQ on installing Linux under Windows, with VirtualBox and with Wubi; plus there is a section on how to install the kitchen if you already have Ubuntu on a dedicated Linux partition (for which you only really need to install JDK). This is all stuff I tested individually before describing it in the FAQ for people to follow.
NOTE -- I didn't go into detail on how to install Linux on a separate partition. I would doubt a new user would go that far (I'd recommend Cygwin or Windows virtualization of Linux), but even if they did, there is information on the internet on how to do it. I trust people know this (i.e. using Google). I don't want the FAQ to get into one long spoonfeeding exercise.
BTW - didn't you just say you had Ubuntu installed on a partition already?
Yes i have linux on other partition
I don't know about this, make sure you followed the instructions in the readme.txt carefully. I have never had problems installing Cygwin with my provided tools, as I have tried it on 3 different PCs which are either running XP or Windows 7. I didn't do anything extra, I just followed all the info I provided in the FAQ. Go to the Cygwin support pages for help if your PC is having trouble.
Click to expand...
Click to collapse
then it seems to be a problem with my system ...
and okk let me try by googled ways that i m still trying out actually i am very new to development my knowledge is basically based on XDA only .. i knw only that much that has been written here or by googled ways,.... yet i understand little about codes and all stuff thats why i m taking a deep intrst in developing a custom rom which could be used as totaly bug free rom
there are three custom roms one is personally developed by Tj_style and other is miui ported by tj_style and cyanogenmod 7. 1 ... nd i found them little buggy... as i understand doing thing of a full team by one person is so hard that's why i wanna contribute by this way..
i had read all ur intrctions as i always do.. bt the problem is of some other kind... im now focusing on linux method i had installed java on that bt still lot of work to understand is left
thanx for ur gr8 help ur guide is full actually the problem might is with my system... if u could help me setup then i m ready to give a remote connection to u if ur intrested....
kshitij_bhatt said:
ok u can tell me the linux method too as i use a dual boot and on ubuntu i had installed jdk 6 already so u can tell me that thing too
Click to expand...
Click to collapse
As you have already set up JDK on your linux OS, all your kitchen setup is done.
Just follow the "After following the setup for the kitchen, how do I use kitchen?" section from FAQ-page1. And go ahead in playing with kitchen.
A brief process summary of what still needs to be done:
Extract the kitchen's .zip file to a folder under your home directory. (Upper Panel Places>Home folder)
Open terminal and cd into kitchen's directory.
Fire ./menu command in it.
If all goes well, you should see all options of kitchen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
okk working now,.. having little trouble bt okk
finally done with one rom... though it didnt get installed was palying with tj_style miui
bt i came to know very much about what i was actually looking out for... thankx Napstar and dsixda for helping and answering such wired nob question thank you
i m playing with miui
as u mentioned
IMPORTANT: Open generated custom ROM zip using any archive viewer and open updater-script from META-INF/com/google/android folder and check that it has "format("ext3", "EMMC", "/dev/block/mmcblk0p7");" as a format command. If it is not the same then read this post before flashing this ROM.
when i build the rom it was ext4 insteed of ext3 though i named it fb0 becoz it was the name in miui
it was the name in the miui so do i changed
i also ported ur uc kernal bt all of it didnt worked ... becoz the rom didn't get installed showing error at the recovery menu,,... haah more work
Napstar indicated in the first post that the kitchen may not work with this device's custom ROMs that were not made with the kitchen. ie. MIUI may have issues due to updater-script and file location incompatibilities.
ya i read that bt what's the big deal in trying... last night it was done i posted uc-kernal in the custom miui and it was installed properly and also that wifi restart problem was solved and camera was also working
bt i wiped data again and then restored my backup as i m nt pretty sure abt miui now working with the stock
btw my phone is now givin some problem will go to service center tomorrow
Napstar said:
Support for Huawei Ideos X6 variants other than Spice MI 410
Open build.prop file from /system/ folder for your working device in any text viewer/root explorer
Search for property ro.product.device value.
If the property value/ device name is other than mi410 then download Huawei Ideos X6 related files.zip from first post and extract mi410 file from it.
Rename mi410 to property value for ro.product.device
For example:
..
..
ro.product.model=FIH-FB0
ro.product.brand=FIH
ro.product.name=FIH-FB0
ro.product.device=FB0
ro.product.board=qcom
..
..
If this is how your build.prop file looks then rename mi410 to FB0
Please note that this file name is case sensitive. So do not rename it to fb0 instead.
Now copy this file in kitchen's tools/edify_defs folder.
Click to expand...
Click to collapse
extracted nb0. using .nb0 utils
and in the build.prop it show's this
ro.product.model=Commtiva-HD710
ro.product.brand=Commtiva
ro.product.name=Commtiva-HD710
ro.product.device=HD710
ro.product.board=HD710
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=FIH
ro.product.locale.language=en
ro.product.locale.region=US
why.. i m extracting spice mi-410 not commtiva-hd710
same happed when i extracted wellcom a-99 update
Napster here is my updater script for today's work
i never understand why .nb0 when extracted says hd 710 insteed of csl mi410
show_progress(0.1, 0);
format("MTD", "system");
mount("MTD", "system", "/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");
mount("MTD", "userdata", "/data");
package_extract_dir("data", "/data");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
package_extract_dir("system", "/system");
symlink("toolbox", "/system/bin/write");
symlink("toolbox", "/system/bin/getevent");
symlink("toolbox", "/system/bin/log");
symlink("toolbox", "/system/bin/rmdir");
symlink("toolbox", "/system/bin/qxdmlog");
symlink("toolbox", "/system/bin/hd");
symlink("toolbox", "/system/bin/sendevent");
symlink("toolbox", "/system/bin/vmstat");
symlink("toolbox", "/system/bin/id");
symlink("toolbox", "/system/bin/ioctl");
symlink("toolbox", "/system/bin/watchprops");
symlink("toolbox", "/system/bin/df");
symlink("toolbox", "/system/bin/netstat");
symlink("toolbox", "/system/bin/mkdir");
symlink("toolbox", "/system/bin/lsmod");
symlink("toolbox", "/system/bin/rmmod");
symlink("toolbox", "/system/bin/notify");
symlink("toolbox", "/system/bin/ifconfig");
symlink("toolbox", "/system/bin/cat");
symlink("toolbox", "/system/bin/start");
symlink("toolbox", "/system/bin/setconsole");
symlink("toolbox", "/system/bin/top");
symlink("toolbox", "/system/bin/dd");
symlink("toolbox", "/system/bin/renice");
symlink("toolbox", "/system/bin/ps");
symlink("toolbox", "/system/bin/lsof");
symlink("toolbox", "/system/bin/route");
symlink("toolbox", "/system/bin/printenv");
symlink("toolbox", "/system/bin/sleep");
symlink("toolbox", "/system/bin/kill");
symlink("toolbox", "/system/bin/ln");
symlink("toolbox", "/system/bin/getprop");
symlink("toolbox", "/system/bin/iftop");
symlink("toolbox", "/system/bin/schedtop");
symlink("toolbox", "/system/bin/chown");
symlink("toolbox", "/system/bin/ionice");
symlink("toolbox", "/system/bin/mv");
symlink("toolbox", "/system/bin/chmod");
symlink("toolbox", "/system/bin/nandread");
symlink("toolbox", "/system/bin/umount");
symlink("toolbox", "/system/bin/setprop");
symlink("toolbox", "/system/bin/reboot");
symlink("toolbox", "/system/bin/uptime");
symlink("toolbox", "/system/bin/date");
symlink("toolbox", "/system/bin/sync");
symlink("toolbox", "/system/bin/newfs_msdos");
symlink("toolbox", "/system/bin/stop");
symlink("toolbox", "/system/bin/wipe");
symlink("toolbox", "/system/bin/rm");
symlink("toolbox", "/system/bin/mount");
symlink("toolbox", "/system/bin/smd");
symlink("toolbox", "/system/bin/cmp");
symlink("toolbox", "/system/bin/ls");
symlink("toolbox", "/system/bin/dmesg");
symlink("toolbox", "/system/bin/insmod");
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, 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(1010, 1010, 0550, "/system/etc/init.qcom.sdio.sh");
set_perm(0, 0, 0755, "/system/etc/wifi/cert_chmod.sh");
set_perm(0, 0, 0555, "/system/etc/ppp/ip-up-vpn");
set_perm(0, 0, 0666, "/system/etc/hostapd/hostapd.conf");
set_perm(0, 0, 0666, "/system/etc/hostapd/hostapd.accept");
set_perm(0, 0, 0666, "/system/etc/hostapd/hostapd.deny");
set_perm(0, 0, 04755, "/system/bin/bash");
symlink("/system/bin/bash", "/system/bin/sh");
set_perm(0, 0, 0777, "/system/bin/a2sd");
set_perm(0, 0, 0777, "/system/etc/init.d/00banner");
set_perm(0, 0, 0777, "/system/etc/init.d/01sysctl");
set_perm(0, 0, 0777, "/system/etc/init.d/02firstboot");
set_perm(0, 0, 0777, "/system/etc/init.d/04apps2sd");
set_perm(0, 0, 0777, "/system/etc/init.d/99complete");
set_perm(0, 0, 0777, "/system/bin/launcha2sd");
set_perm(0, 0, 0777, "/system/bin/starta2sd");
set_perm(0, 0, 0777, "/system/bin/jita2sd");
set_perm(0, 0, 0777, "/system/bin/chka2sd");
set_perm(0, 0, 0777, "/system/bin/zipalign");
set_perm(0, 0, 0777, "/system/bin/sysinit");
set_perm(0, 0, 0777, "/system/bin/busybox.a2sd");
set_perm(0, 0, 0644, "/system/bin/apps2sd.hlp");
set_perm(0, 0, 0777, "/system/xbin/a2sd");
set_perm(0, 0, 0777, "/system/bin/dtinstall");
set_perm(0, 0, 06755, "/system/bin/su");
symlink("/system/bin/su", "/system/xbin/su");
set_perm_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
set_perm(0, 1000, 0755, "/system/xbin/busybox");
symlink("/system/xbin/busybox", "/system/bin/busybox");
package_extract_file("installbusybox", "/tmp/installbusybox");
set_perm(0, 0, 0777, "/tmp/installbusybox");
run_program("/tmp/installbusybox");
show_progress(0.1, 10);
show_progress(0.2, 0);
run_program("/data/dtinstall.launch");
delete("/system/bin/dtinstall");
delete("/data/dtinstall.launch");
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
show_progress(0.2, 10);
unmount("/system");
unmount("/data");
Related
I don't like flashing things without knowing what do they do.
So it helps that I'm a programmer by day, and I make it a point to look at the code of the scripts I'm CWM-flashing.
I downloaded a modem from Perka's stash and I'm not sure what I'm looking at with this one:
Code:
package_extract_dir("updates", "/tmp");
show_progress(0.100000, 10);
set_perm(0, 0, 0755, "/tmp/redbend_ua");
set_perm(0, 0, 0777, "/tmp/redbend_ua");
run_program("/tmp/redbend_ua", "restore", "/tmp/modem.bin", "/dev/block/bml12");
set_perm(0, 0, 0777, "/tmp/redbend_ua");
run_program("/tmp/redbend_ua", "restore", "/tmp/zImage", "/dev/block/bml7");
show_progress(1.000000, 0);
I'm unsure about a few things here:
1. Why is there a need to chmod redbend_ua twice, and then again after running it?
2. We've run the first run_program, and we have a modem. Lovely. Why is the script then messing with the kernel? Especially since there isn't a kernel in this package. I have a suspicion this is simply a sort of template package, and you can put in a kernel, modem or both and it will work, but I'm unsure about this. (Also, how would it react in the case of a file being missing?)
On the whole - What scripting language is this? Where can I find a proper documentation for it? How do I create one myself? I've googled it plenty and didn't seem to come to a proper conclusion..
Why dont you PM Perka himself/herself? she/he would be the best person to answer your questions!!!
Good Luck
The purpose of this thread is to discuss the issues so far in putting out ROMs for the SGH-i957, and to see if we can work out some of the issues.
The current status of the SGH-i957
Previous Work:
CWM: http://forum.xda-developers.com/showthread.php?t=1462770
Root: http://forum.xda-developers.com/showthread.php?t=1401100
OC Kernel: http://forum.xda-developers.com/showthread.php?t=1402643
Stock Rooted Deodexed ATT ROM: http://dev-host.org/3qr <--this is near unusable and lags, we are trying to figure out why. Thank jomeister15
DEV ONLY WILL NOT BOOT ICS 4.0.3 for the LTE Tab: http://dev-host.org/5w0 DEV ONLY WILL NOT BOOT Thank jomeister15
With these in place, we should be able to start making some ROMS. We initially were having issues creating an updater script which would work correctly with CWM.
Myself and Scarchunk both attempted to make ROMs, but could not get working updater scripts. jomeister15 managed to deodex, zipalign, and root the stock ROM from sammobile.com, and then create a CWM flashable zip which flashes and boots successfully. This is the update script.
Code:
show_progress(0.1, 0);
format("ext4", "EMMC", "/dev/block/mmcblk0p24", "0");
mount("ext4", "EMMC", "/dev/block/mmcblk0p24", "/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");
package_extract_dir("data", "/data");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
package_extract_dir("system", "/system");
symlink("dumpstate", "/system/bin/dumpcrash");
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("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, 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_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
set_perm(0, 1000, 0755, "/system/xbin/busybox");
symlink("/system/xbin/busybox", "/system/bin/busybox");
package_extract_file("installbusybox", "/tmp/installbusybox");
set_perm(0, 0, 0777, "/tmp/installbusybox");
run_program("/tmp/installbusybox");
show_progress(0.1, 10);
show_progress(0.2, 0);
package_extract_file("boot.img", "/dev/block/mmcblk0p8");
show_progress(0.2, 10);
unmount("/system");
unmount("/data");
The issue now is that any ROM that is flashed through CWM is experiencing considerable lag. Even just the stock unmodified ROM (applies to Telus as well) in a CWM flashable zip lags.
Any insight on what could be causing this would be appreciated, and as further issues may come up, we can discuss them here.
__________________
Accompanying Information
Code:
C:\Users\Ryan\ADB>adb shell mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p24 /system ext4 ro,relatime,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
,noauto_da_alloc 0 0
/dev/block/mmcblk0p25 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordere
d 0 0
/dev/block/mmcblk0p21 /efs ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p13 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_uti
me=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p17 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0000,
dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,e
rrors=remount-ro 0 0
/dev/block/mmcblk0p27 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=o
rdered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,d
efault_permissions,allow_other 0 0
Most Recent Firmwares:
ATT: I957UCKJ7 (10/26/2011)
Bell: I957MUGKK4 (11/14/2011)
Telus: I957DTLKL2 (12/9/2011)
orlandoxpolice Hi! glad to see that someone is coordinating the development of roms for the i957. I'm from Russia and i'm using i957 here. It's nice and beautiful, but it doesn't contain my native language here.
I try to deodex stock rom but my knowledge isn't so good to complite deodexing.
Can you provide links for deodexed cwm rom? I want to start translating it to Russian language.
ps i'm ready to donate 25$ for developers who will work on i957!!!
Orlando, are you using the above updater script exactly as you've posted? If so, you're not deleting out the old /system.
In the original updater script you pm'd me the other night you had a format system command listed as the first line of the script. It immediately errored out on that line. I assume that's why you removed it. I flashed my rom with the exact script above and it did boot, but I was left with a mess of my old /system and the new /system that I was attempting to flash.
I imagine thats why you're seeing the odd behavior.
Just to be clear, the Telus & Bell firmwares are okay to flash on the i957 correct?
Sent from my SAMSUNG-SGH-I777 using XDA
Scarchunk said:
Orlando, are you using the above updater script exactly as you've posted? If so, you're not deleting out the old /system.
In the original updater script you pm'd me the other night you had a format system command listed as the first line of the script. It immediately errored out on that line. I assume that's why you removed it. I flashed my rom with the exact script above and it did boot, but I was left with a mess of my old /system and the new /system that I was attempting to flash.
I imagine thats why you're seeing the odd behavior.
Click to expand...
Click to collapse
Argh, must of missed a line in the copy paste. Sorry about that. I'll fix it tonight.
EDIT: Fixed the updater script paste in OP
Sent from my SAMSUNG-SGH-I727 using xda premium
neubauej said:
Just to be clear, the Telus & Bell firmwares are okay to flash on the i957 correct?
Sent from my SAMSUNG-SGH-I777 using XDA
Click to expand...
Click to collapse
Yes I believe multiple people have flashed each on the att version. You will have some differences though.
Edit: I was thinking, do you think the lag could be a permissions issue?
Sent from my SAMSUNG-SGH-I727 using xda premium
I will donate if devs start cooking some Ics ROMS or better HC roms for the LTE connectivity.
orlandoxpolice said:
Argh, must of missed a line in the copy paste. Sorry about that. I'll fix it tonight.
EDIT: Fixed the updater script paste in OP
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
What update binary are you using? I've tried a couple different ones and they don't like the syntax that you're using on that format command.
Some roms to choose from would be nice. Hoping somebody starts whipping some up. Even something stock based tweaked/debloated/rooted would be a good start. ICS would be cool
Scarchunk said:
What update binary are you using? I've tried a couple different ones and they don't like the syntax that you're using on that format command.
Click to expand...
Click to collapse
I believe he is using the one from da-g's skyrocket kernel.
"One that Da_g used in his overclocked kernel."
http://www.ponack.net/TPC/dagnarf/dagkernel-0.42-cwm-att.zip
you'll find it in there.
Code:
package_extract_file("boot.img", "/dev/block/mmcblk0p8");
Why you choose extract file for the kernel? , why not this
Code:
package_extract_file("boot.img", "/tmp")
write_raw_image("/tmp/boot.img", "/dev/block/mmcblk0p8");
motley kernel zip file and overcome for example..and no lag from my experience
I'll upload my laggy, flashable build later today if anyone wants to take a more in-depth look.
Hmmm I wonder what it could be then...
Sent from my SAMSUNG-SGH-I727 using xda premium
Any Rom any where??? is it uploaded some where??
Please read the entire thread before posting. We have roms made but when flashing through cwm they become laggy and we don't know why.
Sent from my SAMSUNG-SGH-I727 using xda premium
jomeister15 said:
I'll upload my laggy, flashable build later today if anyone wants to take a more in-depth look.
Click to expand...
Click to collapse
i read all tread before ask my question. Now pls look yourself two posts earlier.
i want to use i957 with my native language. I will translate rom to russian language for i957 users from Russia. But first i need deodexed rom. I try but i cant deodex it by myself. If somebody provide deodexed stock rom i can start translation work now. And when some devs relized first working rom i will need only change original .apk files with already translated. And my localized rom will be just on time.
that's why i'm asking about stock deodexed rom even if it don't working for now.
Jomeister15 has it. Don't know if he uploaded it anywhere yet.
Sent from my SAMSUNG-SGH-I727 using xda premium
So I am thinking that the lag problem lies in either some conflict with the device having a double mounted internal sd card....or a problem when deodexing the framework or system.
maybe check out these links?
http://code.google.com/p/smali/issues/detail?id=75
http://droidangel.blogspot.com/2011/08/solution-how-to-fix-deodexed.html
orlandoxpolice said:
So I am thinking that the lag problem lies in either some conflict with the device having a double mounted internal sd card....or a problem when deodexing the framework or system.
maybe check out these links?
http://code.google.com/p/smali/issues/detail?id=75
http://droidangel.blogspot.com/2011/08/solution-how-to-fix-deodexed.html
Click to expand...
Click to collapse
Pardon my total noob-ness but do we have access to any logs from boot up or shortly after? And if I flash the root package for this might the logs become accessible?
testulous said:
Pardon my total noob-ness but do we have access to any logs from boot up or shortly after? And if I flash the root package for this might the logs become accessible?
Click to expand...
Click to collapse
isn't there logcat?
hey devs , i came above something made me thinking , if i just copy the init.d scripts in their folder in a rom made of flashable zip ex.cm10 the permition of these files doesnt be the same if i install the musing pimp my rom aroma ,, is these permition neccesary to scripts to work ??, if yes how can i set them right
rrgrrg said:
hey devs , i came above something made me thinking , if i just copy the init.d scripts in their folder in a rom made of flashable zip ex.cm10 the permition of these files doesnt be the same if i install the musing pimp my rom aroma ,, is these permition neccesary to scripts to work ??, if yes how can i set them right
Click to expand...
Click to collapse
Permissions are important yes (Sometimes more permissions than necessaries are given to account for differences across devices and they will change per script)
Are they not working, since your asking?
If they aren't run, there are a few things I can think of.
You need to mod the ramdisk to run the scripts on startup or make a file that is already being run on startup to run the scripts in init.d. (CM10 already has it included, don't think any repack got it included - didn't check all of them, so some might have)
The permission the scripts are being run at are the same as what the permissions are from what executed them. Most tweaks need to be run from root so make sure that they are being executed as root if they don't need to be executed as root and aren't run with root permissions make sure that they have sufficient permissions to be run as that user.
Making init.d scripts run a echo command to a file is a good way to check if they are being executed.
And that's what I can think of at the moment.
ok so how can i apply their permitions from the zip of the rom ,, what lines should i add to the updater-script that fixes their permition ? ,, also im using cm10 as a base so its ok with the ramdisk
Code:
set_perm(0, 0, 0755, "/system/etc/init.d");
Ilko said:
Code:
set_perm(0, 0, 0755, "/system/etc/init.d");
Click to expand...
Click to collapse
this to be in the updater-script right ??..
,, i already have these both lines in my cwm script
set_perm_recursive(0, 2000, 0755, 0755, "/system/etc/init.d");
set_perm(0, 0, 0755, "/system/etc/init.d");
Click to expand...
Click to collapse
in your code perms are set two times (first line is useless I think and may apply wrong perms on the etc dir). I don't have much knowledge about these kind of scripts, but I can say that the recursive parameter is used for direcories. also, perms have to be set at the end of scripts (before unmountin of course) so they're applied permanently.
it must be something like this (in short) :
Code:
# mount
run_program("/sbin/busybox", "mount", "/system");
# remove previous bin
delete("/system/etc/init.d");
# copy file from source
package_extract_file("system", "/system/etc/init.d");
# ser perm
set_perm(0, 0, 0755, "/system/etc/init.d");
# unmount
run_program("/sbin/busybox", "umount", "/system");
Yes yes I know there are various threads with this reported issue.
Have tried the suggested solution
still getting the same error
need some hands on help with getting it fixed or how to debug where the issue is exactly
gone through the logs in CWM
seems there is an issue with 3 of the lines
set_perm(0, 0, 04755, "/system/xbin/zipalign");
set_perm(0, 0, 0777, "/system/bin/sysinit.bak");
efaustino84 said:
Yes yes I know there are various threads with this reported issue.
Have tried the suggested solution
still getting the same error
need some hands on help with getting it fixed or how to debug where the issue is exactly
Click to expand...
Click to collapse
S III Mini is not supported by Android Kitchen.
Benzonat0r said:
S III Mini is not supported by Android Kitchen.
Click to expand...
Click to collapse
okay so what do you use?
could one of the dev please do up a simple how to guide for setting up the environment best recommended for building a custom rom for the S3 mini
so far i have not found anything on S3 mini forums that details this information
infected_ has been kind enough to give me some help on building my dev environment
once I have everything setup and working I will try draw up a thread
efaustino84 said:
infected_ has been kind enough to give me some help on building my dev environment
once I have everything setup and working I will try draw up a thread
Click to expand...
Click to collapse
That would be great!!
been going over on how to add another device to kitchen supported devices list
and have created the required edify_defs file
has anyone else tried this?
Code:
# International Samsung Galaxy S3 Mini GT-I8190
change_mnt=yes
param1=ext4
param2=EMMC
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/mmcblk0p22
cache_mnt=\/dev\/block\/mmcblk0p23
boot_mnt=\/dev\/block\/???
data_mnt=\/dev\/block\/mmcblk0p25
sdcard_mnt=???
modem_mnt=\/dev\/block\/mmcblk0p12
preload_mnt=\/dev\/block\/mmcblk0p24
fix_boot2=yes
efaustino84 said:
been going over on how to add another device to kitchen supported devices list
and have created the required edify_defs file
has anyone else tried this?
Code:
# International Samsung Galaxy S3 Mini GT-I8190
change_mnt=yes
param1=ext4
param2=EMMC
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/mmcblk0p22
cache_mnt=\/dev\/block\/mmcblk0p23
boot_mnt=\/dev\/block\/???
data_mnt=\/dev\/block\/mmcblk0p25
sdcard_mnt=???
modem_mnt=\/dev\/block\/mmcblk0p12
preload_mnt=\/dev\/block\/mmcblk0p24
fix_boot2=yes
Click to expand...
Click to collapse
Was mucking around with that too, a few days ago. I wasn't to sure about the format so didn't want to flash anything. I guess we could just try and see whats happens
my concern is that if i have the mount points wrong will i hard-brick my phone?
This is what i have:
Code:
change_mnt=yes
param1=ext4
param2=EMMC
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/mmcblk0p22
cache_mnt=\/dev\/block\/mmcblk0p23
boot_mnt=\/dev\/block\/mmcblk0p20
data_mnt=\/dev\/block\/mmcblk0p25
sdcard_mnt=/dev/block/mmcblk1 /dev/block/mmcblk1p1
modem_mnt=\/dev\/block\/mmcblk0p12
preload_mnt=\/dev\/block\/mmcblk0p24
fix_boot=yes
I'm not 100% sure about the last line (fix_boot=yes)?
Original recovery.fstab below:
Code:
# Mount point fs device
/system ext4 /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p23
/data ext4 /dev/block/mmcblk0p25 length=-16384
/efs ext4 /dev/block/mmcblk0p11
/sdcard vfat /dev/block/mmcblk1 /dev/block/mmcblk1p1
/boot emmc /dev/block/mmcblk0p20
/recovery emmc /dev/block/mmcblk0p21
/preload ext4 /dev/block/mmcblk0p24
tried it with my config and the rom failed to load, will try with yours and see what happens
tried with yours and it also failed
would be nice if the other devs shared what they were using
I was going to try it out last night, but got too tired after having to re-install my Ubuntu VM.
From kitchen: Device name in kitchen, or variant of: golden
dsixda kitchen tells me it uses "golden" as devicename so I made a golden-file in
edify_defs.
Code:
# Samsung Galaxy S3 Mini GT-I8190
change_mnt=yes
param1=ext4
param2=EMMC
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/mmcblk0p22
cache_mnt=\/dev\/block\/mmcblk0p23
boot_mnt=\/dev\/block\/mmcblk0p20
data_mnt=\/dev\/block\/mmcblk0p25
sdcard_mnt=\/dev\/block\/mmcblk1 \/dev\/block\/mmcblk1p1
preload_mnt=\/dev\/block\/mmcblk0p24
efs_mnt=\/dev\/block\/mmcblk0p11
fix_boot=yes
When looking at the updater script generated it looks ok I guess.
Code:
show_progress(0.1, 0);
format("ext4", "EMMC", "/dev/block/mmcblk0p22");
mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system");
package_extract_dir("system", "/system");
symlink("dumpstate", "/system/bin/dumpcrash");
symlink("toolbox", "/system/bin/cat");
symlink("toolbox", "/system/bin/chmod");
symlink("toolbox", "/system/bin/chown");
symlink("toolbox", "/system/bin/cmp");
symlink("debuggerd", "/system/bin/csview");
symlink("toolbox", "/system/bin/date");
symlink("toolbox", "/system/bin/dd");
symlink("toolbox", "/system/bin/df");
symlink("toolbox", "/system/bin/dmesg");
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/touch");
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, 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_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor/etc");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
set_perm(0, 1000, 0755, "/system/xbin/busybox");
symlink("/system/xbin/busybox", "/system/bin/busybox");
run_program("/system/xbin/busybox", "--install", "-s", "/system/xbin");
set_perm(0, 0, 06755, "/system/xbin/su");
symlink("/system/xbin/su", "/system/bin/su");
show_progress(0.1, 10);
show_progress(0.2, 0);
package_extract_file("boot.img", "/dev/block/mmcblk0p20");
show_progress(0.2, 10);
unmount("/system");
Pretty much like the benzrom script except those "show_progress" lines.
Havn't tried to flash it yet . Don't got time to f**k up my phone at the moment :silly:
tys0n said:
From kitchen: Device name in kitchen, or variant of: golden
dsixda kitchen tells me it uses "golden" as devicename so I made a golden-file in
edify_defs.
Code:
# Samsung Galaxy S3 Mini GT-I8190
change_mnt=yes
param1=ext4
param2=EMMC
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/mmcblk0p22
cache_mnt=\/dev\/block\/mmcblk0p23
boot_mnt=\/dev\/block\/mmcblk0p20
data_mnt=\/dev\/block\/mmcblk0p25
sdcard_mnt=\/dev\/block\/mmcblk1 \/dev\/block\/mmcblk1p1
preload_mnt=\/dev\/block\/mmcblk0p24
efs_mnt=\/dev\/block\/mmcblk0p11
fix_boot=yes
When looking at the updater script generated it looks ok I guess.
Code:
show_progress(0.1, 0);
format("ext4", "EMMC", "/dev/block/mmcblk0p22");
mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system");
package_extract_dir("system", "/system");
symlink("dumpstate", "/system/bin/dumpcrash");
symlink("toolbox", "/system/bin/cat");
symlink("toolbox", "/system/bin/chmod");
symlink("toolbox", "/system/bin/chown");
symlink("toolbox", "/system/bin/cmp");
symlink("debuggerd", "/system/bin/csview");
symlink("toolbox", "/system/bin/date");
symlink("toolbox", "/system/bin/dd");
symlink("toolbox", "/system/bin/df");
symlink("toolbox", "/system/bin/dmesg");
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/touch");
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, 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_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor/etc");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
set_perm(0, 1000, 0755, "/system/xbin/busybox");
symlink("/system/xbin/busybox", "/system/bin/busybox");
run_program("/system/xbin/busybox", "--install", "-s", "/system/xbin");
set_perm(0, 0, 06755, "/system/xbin/su");
symlink("/system/xbin/su", "/system/bin/su");
show_progress(0.1, 10);
show_progress(0.2, 0);
package_extract_file("boot.img", "/dev/block/mmcblk0p20");
show_progress(0.2, 10);
unmount("/system");
Pretty much like the benzrom script except those "show_progress" lines.
Havn't tried to flash it yet . Don't got time to f**k up my phone at the moment :silly:
Click to expand...
Click to collapse
tried it out and it gave an error in cwm
let me try it again and post the error here
I:Checking for extendedcommand
I:Skipping execution of extendedcommand, file not found...
I:Can't format partition non-vfat: datamedia
I:Can't format unknown volume: /emmc
Device name in kitchen, or variant of: golden
Please ensure these device mount statements are correct:
--------------------------------------------------------------------------
mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system"); mount("ext4", "EMMC",
"/dev/block/mmcblk0p25", "/data");
write_raw_image("/tmp/boot.img", "/dev/block/mmcblk0p20"),
--------------------------------------------------------------------------
Copying update-binary ...
`../../../../../tools/update_files/emmc-update-binary' -> `update-binary'
--------------------------------------------------------------------------
I get this from kitchen
Code:
Please ensure these device mount statements are correct:
--------------------------------------------------------------------------
mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system");
package_extract_file("boot.img", "/dev/block/mmcblk0p20");
--------------------------------------------------------------------------
Copying update-binary ...
”../../../../../tools/update_files/emmc-update-binary” -> ”update-binary”
--------------------------------------------------------------------------
Do you have "fix_boot=yes" at the end of "golden"-file in edify_defs?
tys0n said:
I get this from kitchen
Code:
Please ensure these device mount statements are correct:
--------------------------------------------------------------------------
mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system");
package_extract_file("boot.img", "/dev/block/mmcblk0p20");
--------------------------------------------------------------------------
Copying update-binary ...
”../../../../../tools/update_files/emmc-update-binary” -> ”update-binary”
--------------------------------------------------------------------------
Do you have "fix_boot=yes" at the end of "golden"-file in edify_defs?
Click to expand...
Click to collapse
yup i do
though from what i can see the issue lies in the fact that not all components are being mounted which Benz has done in his Updater script
efaustino84 said:
yup i do
though from what i can see the issue lies in the fact that not all components are being mounted which Benz has done in his Updater script
Click to expand...
Click to collapse
Just asking, as you get :
"write_raw_image("/tmp/boot.img", "/dev/block/mmcblk0p20")"
while im getting :
"package_extract_file("boot.img", "/dev/block/mmcblk0p20")"
Anyway, I had some time to test and my script worked.
Testrom installed but because format system I had no network.
Restored backup and all ok now but atleast I know there's no error during flash.:good:
i will give it another try this evening if i have time and see if i get the same results as you do
efaustino84 said:
i will give it another try this evening if i have time and see if i get the same results as you do
Click to expand...
Click to collapse
Sounds good. Hope we can make it work
Oh, one other thing. I made a folder named "golden" in /tools/samsung_files/model_variants, and inside that folder an empty file named "golden", to point at the "golden"-file in /tools/edify defs.
tys0n said:
Sounds good. Hope we can make it work
Oh, one other thing. I made a folder named "golden" in /tools/samsung_files/model_variants, and inside that folder an empty file named "golden", to point at the "golden"-file in /tools/edify defs.
Click to expand...
Click to collapse
now that i did not see as a requirement, well spotted
will also add it in on this end
once we get it working we can then ask disxd to add it into the next update of kitchen for future use
i make a rom - well as written here: http://forum.xda-developers.com/showthread.php?t=2266842
all things are work. i flash the rom ... works too ... BUT: wifi not work, usb not work, phone not work!
What am I doing wrong? even if i flash "multi csc" ... nothing ...
My folderinfo:
Code:
Android OS version : 4.1.2
Device : golden
Model : GT-I8190
ROM Name : JZO54K.I8190XXAMD3
CSC version : I8190OXAAMD3
Rooted (Superuser app + su) : No
Rooted (unsecured boot.img) : No
BusyBox installed : No
BusyBox run-parts support : No
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : No
/system/framework is deodexed : NO
/system/app is deodexed : NO
radio.img found : NO
ROM will wipe all data : NO
than ... i install root, busybox and change the rom name. NOTHING more!
But doent works after flash ...
pls help me
hurricane2012 said:
i make a rom - well as written here: http://forum.xda-developers.com/showthread.php?t=2266842
all things are work. i flash the rom ... works too ... BUT: wifi not work, usb not work, phone not work!
pls help me
Click to expand...
Click to collapse
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p22");
That line gave me same problem.
Instead I used
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/data");
mount("ext4", "EMMC", "/dev/block/mmcblk0p23", "/cache");
delete_recursive("/data/dalvik-cache");
delete_recursive("/data/Test.log");
delete_recursive("/cache");
delete_recursive("/system/app");
delete_recursive("/system/framework");
Can you post the updater-script?
my updater script (autogenerated)
Code:
show_progress(0.1, 0);
format("ext4", "EMMC", "/dev/block/mmcblk0p22");
mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system");
package_extract_dir("system", "/system");
symlink("dumpstate", "/system/bin/dumpcrash");
symlink("toolbox", "/system/bin/cat");
symlink("toolbox", "/system/bin/chmod");
symlink("toolbox", "/system/bin/chown");
symlink("toolbox", "/system/bin/cmp");
symlink("debuggerd", "/system/bin/csview");
symlink("toolbox", "/system/bin/date");
symlink("toolbox", "/system/bin/dd");
symlink("toolbox", "/system/bin/df");
symlink("toolbox", "/system/bin/dmesg");
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/touch");
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, 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_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor/etc");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
set_perm(0, 1000, 0755, "/system/xbin/busybox");
symlink("/system/xbin/busybox", "/system/bin/busybox");
run_program("/system/xbin/busybox", "--install", "-s", "/system/xbin");
set_perm(0, 0, 06755, "/system/xbin/su");
symlink("/system/xbin/su", "/system/bin/su");
show_progress(0.1, 10);
show_progress(0.2, 0);
package_extract_file("boot.img", "/dev/block/mmcblk0p20");
show_progress(0.2, 10);
unmount("/system");
when i create the working folder - this warning
Code:
Warning: No cache.img.ext4 found. You can unpack this file separately
by running the plugin script in the kitchen's Advanced menu options.
If your device doesn't use a CSC, then just ignore this message.
what should I do? In folderinfo
Code:
CSC version : I8190OXAAMD3
is now included or not?
after flash: "sim card not found - please insert"
Yeah. it must be that line as it gave me the same problem.
Use notepad++ to edit the script manually.
Remove that line and replace it with:
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/data");
mount("ext4", "EMMC", "/dev/block/mmcblk0p23", "/cache");
delete_recursive("/data/dalvik-cache");
delete_recursive("/data/Test.log");
delete_recursive("/cache");
delete_recursive("/system/app");
delete_recursive("/system/framework");
delete_recursive("/system");
or maybe:
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/data");
mount("ext4", "EMMC", "/dev/block/mmcblk0p23", "/cache");
delete_recursive("/data/dalvik-cache");
delete_recursive("/data/Test.log");
delete_recursive("/cache");
delete_recursive("/system");
tys0n said:
Yeah. it must be that line as it gave me the same problem.
Use notepad++ to edit the script manually.
Remove that line and replace it with:
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/data");
mount("ext4", "EMMC", "/dev/block/mmcblk0p23", "/cache");
delete_recursive("/data/dalvik-cache");
delete_recursive("/data/Test.log");
delete_recursive("/cache");
delete_recursive("/system/app");
delete_recursive("/system/framework");
delete_recursive("/system");
or maybe:
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/data");
mount("ext4", "EMMC", "/dev/block/mmcblk0p23", "/cache");
delete_recursive("/data/dalvik-cache");
delete_recursive("/data/Test.log");
delete_recursive("/cache");
delete_recursive("/system");
Click to expand...
Click to collapse
ok i test it ... take some minutes
hurricane2012 said:
when i create the working folder - this warning
Code:
Warning: No cache.img.ext4 found. You can unpack this file separately
by running the plugin script in the kitchen's Advanced menu options.
If your device doesn't use a CSC, then just ignore this message.
what should I do? In folderinfo
Code:
CSC version : I8190OXAAMD3
is now included or not?
after flash: "sim card not found - please insert"
Click to expand...
Click to collapse
I did extract the cache.img. You'll get a sec_csc.zip.
Just extract it and place the folders/files into your rom.
when i replace the line with your code ... in cwm abort install error 6
okay i used a wrong texteditor ... i replaced the errors ... flash again ... take some minutes ...
hurricane2012 said:
when i replace the line with your code ... in cwm abort install error 6
okay i used a wrong texteditor ... i replaced the errors ... flash again ... take some minutes ...
Click to expand...
Click to collapse
Yeah it have to be notepad++ if you're on a windows machine.
Also, you might have to flash official firmware in order to get your phone capabillities restored now that "/system" got formatted.
I do't know..
tys0n said:
Yeah it have to be notepad++ if you're on a windows machine.
Also, you might have to flash official firmware in order to get your phone capabillities restored now that "/system" got formatted.
I do't know..
Click to expand...
Click to collapse
must i deodex?
hurricane2012 said:
must i deodex?
Click to expand...
Click to collapse
Odexed vs Deodexed
You can use my updater script if you want tell me if it works!
Sent from my GT-I8190N using xda app-developers app
dariolob said:
You can use my updater script if you want tell me if it works!
Sent from my GT-I8190N using xda app-developers app
Click to expand...
Click to collapse
where can find it?
Take the v4 one! Not v5 because of the AROMA installer
Sent from my GT-I8190N using xda app-developers app
I do following steps:
- extract "HOME_I8190XXAMD3_I8190OXAAMD3_1154865_REV00_user_low_ship.tar"
- create a new zip with boot.img and system.img
- open Cygwin Terminal as adminsitrator
- open android kitchen
- extract cache.img (0 -> 18 -> 3)
- setup working folder
- copy the folder "system" (frome extracted cache.img) into workingfolder
Now folder information
Code:
Working folder information (v0.223)
Android OS version : 4.1.2
Device : golden
Model : GT-I8190
ROM Name : JZO54K.I8190XXAMD3
CSC version : I8190OXAAMD3
Rooted (Superuser app + su) : NO
Rooted (unsecured boot.img) : NO
BusyBox installed : NO
BusyBox run-parts support : NO
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : NO
/system/app is deodexed : NO
radio.img found : NO
ROM will wipe all data : NO
- add root ( 2 -> c )
- add busybox ( 3 )
- add running parts (busybox: 0 -> 14)
now my folder information
Code:
Working folder information (v0.223)
Android OS version : 4.1.2
Device : golden
Model : GT-I8190
ROM Name : JZO54K.I8190XXAMD3
CSC version : I8190OXAAMD3
Rooted (Superuser app + su) : YES
Rooted (unsecured boot.img) : YES
BusyBox installed : YES
BusyBox run-parts support : YES
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : NO
/system/app is deodexed : NO
radio.img found : NO
ROM will wipe all data : NO
- build rom ( 99 )
* build option 1
* optimize apk: no
* updater-script: yes
* sign your rom: yes
* rename the zip-file: no
- open zip in outputfolder
- replace the updater-script with updater-script from DMod v4
- copy on sd-card
- boot into recovery
* format data
* format system
* wipe cache
* wipe dalvyk cache
- install my rom
* data/factory reset
- reboot
Result: no phone, no wifi, no usb connection with pc ...
what is wrong?
I just only want a working cwm rom without any mods
the v4Script:
Code:
assert(getprop("ro.product.device") == "golden" || getprop("ro.build.product") == "golden" ||
getprop("ro.product.device") == "i8190N" || getprop("ro.build.product") == "i8190N" ||
getprop("ro.product.device") == "GT-I8190N" || getprop("ro.build.product") == "GT-I8190N");
show_progress(0.500000, 0);
unmount("/system");
unmount("/cache");
format("ext4", "EMMC", "/dev/block/mmcblk0p22");
format("ext4", "EMMC", "/dev/block/mmcblk0p23");
mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/data");
mount("ext4", "EMMC", "/dev/block/mmcblk0p23", "/cache");
delete("/data/system/batterystats.bin");
delete_recursive("/data/dalvik-cache");
delete_recursive("/data/boot-cache/");
delete_recursive("/data/nos_injection/");delete_recursive("/data/resource-cache/");
delete_recursive("/data/system/usagestats");
delete_recursive("/data/app");
delete_recursive("/data/app-asec");
delete_recursive("/data/app-private");
delete_recursive("/data/backup");
delete_recursive("/data/data");
delete_recursive("/data/drm");
delete_recursive("/data/log");
delete_recursive("/data/local");
delete_recursive("/data/misc");
delete_recursive("/data/property");
delete_recursive("/data/time");
delete_recursive("/data/user");
delete_recursive("/data/system");
package_extract_dir("data", "/data");
set_perm(1000, 1000, 0771, "/data");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
unmount("/data");
package_extract_file("initd.sh", "/tmp/initd.sh");
set_perm(0, 0, 0777, "/tmp/initd.sh");
run_program("/tmp/initd.sh", "/tmp/initd.sh");
package_extract_dir("system", "/system");
symlink("dumpstate", "/system/bin/dumpcrash");
symlink("toolbox", "/system/bin/cat");
symlink("toolbox", "/system/bin/chmod");
symlink("toolbox", "/system/bin/chown");
symlink("toolbox", "/system/bin/cmp");
symlink("debuggerd", "/system/bin/csview");
symlink("toolbox", "/system/bin/date");
symlink("toolbox", "/system/bin/dd");
symlink("toolbox", "/system/bin/df");
symlink("toolbox", "/system/bin/dmesg");
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/touch");
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, 0755, 0755, "/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_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor/etc");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
set_perm(0, 0, 0755, "/system/etc/be_movie");
set_perm(0, 0, 0755, "/system/etc/be_photo");
set_perm(0, 0, 04755, "/system/xbin/sysrw");
set_perm(0, 0, 04755, "/system/xbin/sysro");
set_perm(0, 1000, 0755, "/system/xbin/busybox");
symlink("/system/xbin/busybox", "/system/bin/busybox");
run_program("/system/xbin/busybox", "--install", "-s", "/system/xbin");
set_perm(0, 0, 06755, "/system/xbin/su");
symlink("/system/xbin/su", "/system/bin/su");
set_perm(0, 0, 0777, "/system/bin/nos_entropy");
set_perm(0, 0, 0777, "/system/bin/4cylturbo");
set_perm(0, 0, 0777, "/system/bin/sysro");
set_perm(0, 0, 0777, "/system/bin/sysrw");
set_perm(0, 0, 0777, "/system/bin/rambooster");
set_perm(0, 0, 0777, "/system/bin/zipalign_apks");
set_perm_recursive(0, 2000, 0777, 0777, "/system/etc/init.d");
set_perm_recursive(0, 2000, 0777, 0777, "/system/etc/zram");
set_perm_recursive(0, 2000, 0777, 0777, "/system/etc/nos_scripts");
set_perm(0, 0, 0777, "/system/etc/nos_scripts/nos_entropy");
set_perm(0, 0, 0777, "/system/etc/init.d/nos_entropy");
set_perm_recursive(0, 2000, 0777, 0777, "/system/etc/nos_scripts");
set_perm(0, 0, 0777, "/system/etc/zram/nose_zram_swap");
set_perm(0, 0, 0755, 0644, "/system/etc/resolv.conf");
set_perm(0, 0, 0755, 0644, "/system/etc/sysctl.conf");
set_perm(0, 0, 0777, "/data/nos_injection/4cylturbo/etc/cron");
set_perm(0, 0, 0644, "/data/nos_injection/4cylturbo/etc/cron/root");
set_perm(0, 2000, 0777, "/system/xbin/rngd");
set_perm(0, 2000, 0777, "/system/xbin/entro");
set_perm(0, 0, 04755, "/system/xbin/sqlite3");
set_perm(0, 0, 04755, "/system/xbin/zipalign");
show_progress(0.500000, 25);
show_progress(0.500000, 75);
package_extract_file("boot.img", "/dev/block/mmcblk0p20");
show_progress(0.500000, 100);
unmount("/system");
unmount("/data");
unmount("/cache");
Please help
Why you don't follow my "Howto" ? .... and btw i think your problem is that youre modem.bin is from AMB3 not updated to AMD3...
Sent from my Nexus 4 using xda premium
enox.co said:
Why you don't follow my "Howto" ? .... and btw i think your problem is that youre modem.bin is from AMB3 not updated to AMD3...
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
on which position i not follow your howto?
info from settings: Basibandversion: I8190XXAMD3
-wipe data / factory reset after flashing your rom should fix the problems....
enox.co said:
-wipe data / factory reset after flashing your rom should fix the problems....
Click to expand...
Click to collapse
View my post:
- install my rom
* data/factory reset
- reboot
Click to expand...
Click to collapse