PORTING ROMS FOR MEDIATEK
FEATURE OF THIS GUIDE- NOOB -> EXPERT
I DONT KNOW THE METHOD I USE TO PORT WILL WORK FOR OTHER CHIPSET DEVICES OR NOT AS I ONLY USED MEDIATEK DEVICE.
IF YOU ARE IN A HURRY THEN SEE HERE MY 1-MIN PORTING GUIDE.
AND YOU CAN FIND HERE MY TRICKY CONCEPT- "X" TO SAVE MONEY,TIME,NET DATA.
Credits
@dsixda for awesome android kitchen @rua1 for Mtk Dorid Tools @knzo for tweaks @https://www.otaupdatecenter.pro/ and their team for OTA. @tech mashido As Helper
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
WORK BEGINS
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
THINGS NEEDED
(INSTALL BELOW THINGS AS PER YOUR OS BIT VERSION,IF YOU HAVE 32 BIT OS THEN INSTALL 32 BIT STUFFS AND IF YOU HAVE 64 BIT OS THEN CHOOSE 64 BIT STUFFS.
WIndows Running PC or Laptop.
JAVA - Download
Cygwin - Download
7zip Compressor-Download
Notepad++ -Download
Android Kitchen- Download
Time(as per you how much take to understand)
Your Base Rom(stock Rom,in any format-CWM flashable or SP_tools Flashable,Prefer to have Both)
CWM Recovery
SD card & Card Reader.(some phones do not have SD slot so no worry for them,i have alternative way)
APKTOOL- DOWNLOAD
SP_Flash Tools to Unbrick In case Device Get Bricked- Download
SETTING UP IMPORTANT THINGS FIRST
JAVA
Download Java From Above link as per your OS type.
Install it by running its setup like normal softwares.
CYGWIN
Download Cygwin From Above link.
Extract the Zip
By default it will be installed at c:\cygwin .i also recommend to install at default location.
Run Setup and Select "Install from Local Directory"
Then is will ask for packages location.Verify it.
Hit next-next and finish at the end.
Now you see a Cygwin folder under "C" drive and a shortcut Icon at desktop.
*For some 64 BIT users this method might not work,they can download setup from here-Download & install it from internet instead from local packages and select all packages during installation.
7ZiP
Download 7Zip From Above link as per your OS type.
Install it by running its setup like normal softwares.
Notepad++
Download Notepad++ From Above link as per your OS type.
Install it by running its setup like normal softwares.
dsixda's Android Kitchen
Download dsixda's Android Kitchen From Above link.
Extract it and then it will be like this- Android-Kitchen-0.224\Android-Kitchen-0.224\orgianal_update,tools etc....
Now open Android-Kitchen-0.224 folder and you will again find Android-Kitchen-0.224 folder,then rename it to only " kitchen " (small letters).
Now directory will look like this- Android-Kitchen-0.224\kitchen\orgianal_update,tools etc....
Now copy that kitchen folder which we renamed and paste to c:\cygwin\home"your_username""paste here"
Now your cygwin directory will look like this- C:\cygwin\home\your_username\kitchen\orignal_update,tools,etc.....
To check Kitchen is working,open cygwin from desktop and type - "cd kitchen" and hit enter(small letters).
If no error shown then you have sucessfully installed it or if error like- bash:cd :kitchen:No such file or dirctory hen you should check above steps again.
>>OPENING KITCHEN- open cygwin,type "cd kitchen" hit enter,now type " ./menu " and hit enter.Now kitchen will load.
PORTING CWM RECOVERY(PORT IF YOUR DEVICE DO NOT HAVE IT)- ROOT REQUIRE
Download and install ADB drivers on PC first.DOWNLOAD
Get MTK Droid tools From Here and Extract-HERE
Now go to developers option and enable USB debugging.If you cant find Developers option then go to settings/about Phone and press 7 times on BUILD NUMBER then you will see Developers option under settings.
Open MTK Droid tools on pc and then plug your device(turned on) via usb cable.Now the tool will recognise your device and connect to it(if asked for root permission on device then grant).
If the colour indicator in the bottom left corner is green in MTK Droid Tools,then you already have root shell,and can go on to the next step, if it is yellow, click on the root button at the bottom, and wait for the progress bar, if the indicator stays yellow, or you get an error message, this probably means you do not have Busybox installed, you can install it from the Google play store. When the indicator turns to green you have root shell which is necessary for this operation.
Now click on 'root,backup,recovery' and then select 'to use boot from phone'
Now click on 'recovery and boot'
Then you will see a dialogue box will appear asking if you want to 'make cwm recovery automatically' click yes.
The tool will then create the recovery and then another dialogue box will appear asking to 'install created recovery to phone', click yes.
Now you reboot into recovery mode and check that it is working fine or not.
You can find generated cwm recovery under MTK Droid Tools location.
If you want to revert to stock recovery then take recovery.img from your stock rom(sp_tools) and paste into sd card.And then install mobileuncletools from playstore and click on update recovery and select your stock recovery from SD.Same method for installing CWM recovery.
WHICH ROMS YOU CAN PORT
Port rom should be of same android version as your stock rom.Like if your stock rom is 4.2 then you should only try with 4.2.In some cased you can port higher versions like kikat too,it will require Custom kernel but we are skipping that.
The device from you porting should have same chipset,like if your device is MT6589 then you shoul only try with MT6589 chip-sets.You can port from MT6589T to MT6589 or MT659M but you cannot port from MT6592.
Choose the port rom from most close specification device,like screen size,screen resolution,dual-sim,etc....higher resolution to lower resolution resolution or lower to higher can be ported but not all boots up.
Some Sites To get Port Rom:-
anzhuodiy.com
romzj.com
dashi.com
shendu.com
needrom.com
Porting begins
MAKING PORTING ENVIRONMENT
Registering Your Device To Kitchen:-This step will help to write updater script automatically.
Open kitchen and select option 0(advance options) and then select option 12(tools for unpack and repack boot.img etc.) and press "a"(Extract kernel+ramdisk from boot.img,recovery.img etc.) and hit enter.
Now a folder will be created Under kitcehn directory named like this- bootimg_040714_132352
Now copy your CWM recovery.img for your device to this folder and check that the name must be - recovery.img if not then rename it. and hit enter in kitchen terminal.It will extract your recovery in that folder.
Open up boot.img-ramdisk folder, and look for /system/etc/recovery.fstab or /etc/recovery.fstab or similar FSTAB file location. Open this file by notepad++ to find the mount points.
Download below file and paste it to C:\cygwin\home\username\kitchen\tools\edify_defs .Now rename it to your device code name.Mine is A110Q so i used this file. You can use as your choice also.
Then open this file and recovery.fstab with notepad++ and compare and replace mount points and save it.Means copy mount points from recovery.fstab and paste/replace into Your device codenamed file.
Now if you done all above steps right then kitchen will make updater script for you.
If you porting for Micromax A110Q then just Download the below File and paste it.No need to edit.Just paste it.
>>>>>>Micromax A110Q file - http://d-h.st/Qa5
>>>>>>IF you have any confusion or you are unable to create this file then PM me your recovery.fstab file and i will make it.
GET BOTH ROMS- STOCK AND PORT
STOCK-Your stock rom which was provided by device manufacturer.
PORT- The Rom you selected to port after comparing your device to port device.
GETTING STOCK ROM SYSTEM FOLDER
IF your Stock ROM is in already in form of CWM flashable zip then create a Stock Folder in any drive of Computer and extract it for further Use.
Basic Strurture od CWM FLASHABLE ZIPs
META-INF
SYSTEM
DATA
boot.img
IF YOUR ROM IS SP_TOOLS FLASHABLE THEN DO THESE TO EXTRACT SYSTEM FOLDER FROM IT:-
Basically IN SP_TOOLS flashable zips the folder structure is-
DATABASE
boot.img
cache.img
EBR1
EBR2
IK.bin
logo.bin
MBR
MT65xx_Android_scatter_emmc.txt
Preloaded_xxxxxx.bin
recovery.img
secro.img
system.mg
userdata.img
[STEPS]
Extract system.img from stock rom zip to C;\cygwin\home\username\kitchen\original_update
*You should add kitchen folder to favorites panel in my computer as you will be using this folder very frequent.
Now open cygwin,type "cd kitchen" hit enter,now press- " ./menu " then android kitchen will load with lots of functions numbering from 1 to ...
Press 1 to setup working folder now again hit Enter.Now it will ask you to choose an option to select working folder.Select system.img one folder by pressing its value and hitting enter.
Now it will ask about changing working folder name,leave it as default and hit enter.So kitchen will now start copying rom to working folder.
After Copying files it will auto prompt and open Ext2Explore application.In some cases it will show that error message that "unable to read disk,please make sure you are running appliacation with administrative rights."But don't worry,click ok.
Now after Ext2Explore opened,click on "FILE" on upper left corner and click on "OPEN IMAGE".Now browse to kitchen directory and go through newly created working folder and you will find "ext4_system.img" under system folder.Select it.
Right click on file selected in Ext2Explore and Click on SAVE,now browse to same folder where "ext4_system.img" was.Means newly created working folder/system under kitchen directory.
Then it will extract "ext4_system.img" to same folder.After finishing extraction close the Ext2Explore application.Now hit Enter in kitchen,again it will say "warning,no boot.img found" .Do not worry,HIT ENTER and go with default.
It will ask to view Rom info,you can skit this.
So finally you got system folder under working folder.So copy that system folder to any drive and rename it to Stock rom folder for further use.
[TIP:-]
>>IF your Rom is odexed then you should deodexed it before copying to any other drive for further use.<<
HOW TO CHECK THE ROM IS ODEXED:-
GO TO SYSTEM/APP and SYSTEM/FRAMEWORK folder and see that for every file there is clone file ending with .odex .If there is then your rom is odexed.
WHAT IS DEMAERIT OF ODEXED ROM FOR DEVELOPERS-
You will not able to theme and modify your rom if system and framework is odexed so better deodex the rom.Deodexing will combine file and its clone .odex to one unit.
DEODEXING:-
AFTER SETTING UP WORKING FOLDER AND DOING ALL ABOVE STEPS,now hit 0 in kithcen and select 11 option and hit enter.
IT will show number of odex files in your Rom.Now Select "b" option to deodexing all files,it will take some time.
After done,it will show that "0" files left odexed in Rom,now exit kitchen and Now you should copy your system folder to any drive for furter use.
GETTING STOCK ROM BOOT.IMG EXTRACTED
[STEPS]
Now open Kitchen and select 0(advance options) and Hit enter,now select option 12(tools for unpack and repack boot.img etc.)
Under 12th option,press "a"(Extract kernel+ramdisk from boot.img,recovery.img etc.) and hit Enter
Now a folder will be created Under kitcehn directory named like this- bootimg_040714_132352 Now copy your boot.img and paste into this folder.
Now switch to Kitchen Terminal and press Enter.Then it will do some process and extract your boot.img,Now copy that folder and save it to any drive and Rename it to stock boot for further use.
NOW DOWNLOAD PORT ROM YOU CHOOSED TO PORT AND MOVE TO NEXT STEP BELOW.
PORTING
PORTING
>>>>Follow STEP I if you have port rom flashable via cwm.To check that your rom is flashable vai cwm see above post for structure.Those who having SP Tools flashable port rom follow StepII directly.<<<<
First we will port and check that rom boots or not by simple way,then if it boots then we will modify it and tweak it by using kithcen.Or you can skip this step I and directly follow step II but you have to do almost all things from step I in Step II except modifying updater script.If you do these things in step I then no need to do in Step II.
STEP I
[*]Make a folder and name it as you want and copy and paste your port rom zip in it,means make a clone file of it and we will be working with clone zip,always keep in mind.I said to copy paste as if your rom did not boot up then you have a backup of clean port rom.
[*]Now create a folder under original update of kitchen- " WORKING_XXXX "
[*]Then open zip using 7zip(make 7zip is as default app) and drag drop boot.img to " WORKING_XXXX " folder.Now Open kitchen and Press 1 to setup working Folder.And go with default in all steps forward.(keep 7zip opened,you will need to drag back boot.img in it)
[*]After working folder setuped.Now press 0 for advance option and hit enter.Now press 12 and hit enter.Now you press "w" to extract boot.img from working folder.
[*]After sucessful extraction you will find a folder under kitchen named BOOT EXTRACTED.
[*]Now you have to copy zImage from stock boot extracted folder(which was created by you in second post last step) to this BOOT EXTRACTED folder and replace it.
[*]Then switch to kitchen and press "b" to build boot.img from BOOT EXTRACTED folder then after repacking boot.img finish,you have to drag and drop only boot.img(kitchen/working folder)(not meta-inf) to port rom zip.
[*]Now Open System Folder In port Zip and drag drop build.prop file out of it to anywhere you wish.
[*]Now edit it with Notepad++.
[*]Add this line if you are porting from a higher resolution device- ro.sf.lcd.density=220 .Change its value after rom boots as to your display resolution.If after rom boots up and everything looking large then reduce the value and if looking small then increase it.
[*]You can Edit These Values as desired:-
Code:
ro.build.id=
ro.build.display.id=
ro.custom.build.version=
ro.build.version.release=This is Andriod version That Displays in Settings
ro.product.model=
ro.product.brand=
ro.product.name=
ro.product.device=
ro.product.manufacturer=
ro.build.bluetooth.name=
[*]EDIT BELOW LINES TO SET YOUR TIMEZONE AND AREA REGION.You can find your default details in your stock rom's build.prop which you extracted earlier.
Code:
ro.product.locale.language=(en for English,ru for Russian and other similar codes for other language)
ro.product.locale.region=(us for usa, IN for india etc.)
persist.sys.timezone=( Asia/kolkata for india,Asia/... different for different regions)
[*]Now after editing done drag build.prop to port zip.
[*]Now keep opened port zip one side and open stock rom system folder which we extracted in post 2.
[*]Open System/etc/firmware in both zip and stock folder.Now drag modem.img from stock folder to zip and drop it.
[*]Now head to lib folder in both.Here you have to drag and drop libcamercustom.so file to port zip.
[*]Go to system/lib/modules now,here drag and drop mtk_stp_wmt.ko file to port zip.If rom did not boots forward then you should drag and drop whole modules folder under system/lib of port zip.
[*]Go to usr/keylayout in both and drag drop Generic.kl file from stock to port zip.
[*]Lastly drag and drop a launcher like nova,apex or any to system/app/ of port zip in case port launcher did not worked.
[*]IF you rom did not booted by applying all above steps then replace these folder/files from stock to port:-
1)system/etc/firmware
2)system/lib/hw
3)system/lib/modules
4)system/vendor
[*]If your cwm port rom zip have these files then delete those.
---uboot.bin
---preloader
---logo.bin(you can keep it but you need your stock logo.bin which is available in sptool flahable roms.I will also tell you how to create own logo.bin and bootanimation in below post.)
[*]Your zip should look like this-
--Meta-inf
--system
--boot.img
--data (in some roms)
[*]After deleting the extra files you need to modify the updater script which can be found under,Meta-inf/com/google/android/updater-script...we are modifying by own only this time as we have to check only.During building rom from kitchen,it will be automatically created
as we registered our device.If we do not register our device in kitchen then during making roms from kithcen our current updater script will converted to update script which will be again converted to updater script and that will cause installation aborted error.
[*]Now drag and drop updater script from zip to anywhere and open it with notepad++,now find lines below-
Code:
format("ext4", "EMMC", "/dev/block/[COLOR="DarkOrange"]mmcblk0p7[/COLOR]", "0");
format("ext4", "EMMC", "/dev/block/[COLOR="DarkOrange"]mmcblk0p5[/COLOR]", "0");
mount("ext4", "EMMC", "/dev/block/[COLOR="Red"]mmcblk0p7[/COLOR]", "/data");
mount("ext4", "EMMC", "/dev/block/[COLOR="Red"]mmcblk0p5[/COLOR]", "/system");
[*]Here you have to deal with text in red.Your updater script may be different so use your brain and understand what i am saying forward.Text in red is mount point.In above mmcblk0p7 is mount point of data folder and mmcblk0p5 is mount point of system folder.So you need to replace mount points of updater script with your device mount points.You must found mount points of your device during registering device to kitchen.So open recovery.fstab or that kitchen/tool/edify_defs/your file with notepad++ and copy replace mount points from your device file to updater-script of port zip.If you find those lines any more places in updater script then also replace there.Here you only need some mind to use.For example if you edited and replaced red text then you must also replace orange text as they are also same.
[*]Remove the lines of the files which you removed in zip if there,like uboot.bin,logo.bin,preloader etc...they will look like below codes,you only need to find the line matching to the file you removed and deleat that.
Code:
package_extract_file("uboot.bin", "/dev/uboot");
or
assert(package_extract_file("uboot.img", "/tmp/uboot.img"),
write_raw_image("/tmp/uboot.img", "uboot"),
delete("/tmp/uboot.img"));
or
assert(package_extract_file("preloader.img", "/tmp/preloader.img"),
write_raw_image("/tmp/preloader.img", "preloader"),
delete("/tmp/preloader.img"));
[*]And replace this line
Code:
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "bootimg"),
delete("/tmp/boot.img"));
From this if any error occurs during installtion like boot.img assert failed.
Code:
package_extract_file("boot.img", "/dev/boot");
[*]Drag back the updater-script to zip from where it was taken from.
What we have done above is that we drag and drop some stock files from stock rom to port zip without extrating it.
Now you are good to flash your ported rom.Make CWM backup if you want to go back to previous rom or rom did not booted.After that wipe data factory reset,wipe cache partition,wipe dalvic cahce under advance option and then format system under mount and storage OF CWM RECOVEY then install zip from sd card and install your zip.I said SD card in first post if your rom did not booted and you understood your mistake and modified your port rom zip then you can do that directly by transferring zip to sd and flash instead of installing or restoring another rom.But for the users with not sd card must save their CWM backup or a working cwm flahable Rom zip otherwise they will have to reflash the rom by SP tools if rom didnot booted.
STEP II
NOTES BEFORE BEGINNING STEP II :-
If you ported your ROM using STEP I and booted then for modifying use this STEP II.
If you tried porting rom using STEP I but it is showing installation aboted then follow this STEP II directly.
IF you have SP Flash tools format port rom and you extracted system folder and boot.img from your stock rom using my method then Follow STEP II directly.
STEP II contains some steps from STEP I,so if you already did those steps in STEP I and using same zip here then you can skip steps here.If you get confused then again do all steps.
STEP(A)- ADDING A WORKING FOLDER IN KITCHEN
FOR CWM ROM:-
Create a folder " WORKING_XXXX " under kitchen/original _update if you haven't.If you having it then check that it is empty.
Now open your port zip (or zip you ported through STEP I and was booted) and extract its System and boot.img to "WORKING_XXXX " folder.
Open kitchen and press "1" to setup a working folder.
Press Enter and select "WORKING_XXXX " folder by it assigned digit and hitting Enter
Now it will ask for name,you may change it or leave it,it does not matter.Skip it by pressing Enter.
It will start copying files to a working folder,wait sometime.
After it will ask to view Rom info,then press Y and see its info as your wish.
Now you have a working folder setup-ed.
FOR SP TOOLS ROM:-
Extract system.img & boot.img from port rom zip to C;\cygwin\home\username\kitchen\original_update
Run Kitchen and press "1" to setup working folder and hit enter.
Now again hit Enter,this time it will ask you to choose an option to select working folder,Select system.img&boot.img one folder by pressing its value and hitting enter.
Now it will ask about changing working folder name,leave it as default and hit enter.So kitchen will now start copying rom to working folder.
After Copying files it will auto prompt and open Ext2Explore application.In some cases it will show that error message that "unable to read disk,please make sure you are running appliacation with administrative rights."But don't worry,click ok.
Now after Ext2Explore opened,click on "FILE" on upper left corner and click on "OPEN IMAGE".Now browse to kitchen directory and go through newly created working folder and you will find "ext4_system.img" under system folder.Select it.
Right click on file selected in Ext2Explore and Click on SAVE,now browse to same folder where "ext4_system.img" was.Means newly created working folder/system under kitchen directory.
Then it will extract "ext4_system.img" to same folder.After finishing extraction close the Ext2Explore application.Now hit Enter in kitchen and go with default then Press y to view ROM info as per your wish.
Now you have a working folder setup-ed.
STEP(B)-Porting Rom
PATCHING BOOT.IMG:-
After successful creation of working folder you will find a new folder created named like-"WORKING_041214_135729".
Open kitchen then Press 0 for advance option and hit enter.Now press 12 and hit enter.Now you press "w" to extract boot.img from working folder.
After sucessful extraction you will find a folder under kitchen named BOOT EXTRACTED.
Now you have to copy zImage from stock boot extracted folder(which was created by you in second post last step) to this BOOT EXTRACTED folder and replace it.
Now switch to kitchen and press "b" to build boot.img from BOOT EXTRACTED folder then after repacking boot.img finish press x to exit and back to main menu.
Editing Build Prop:-
you will find build.prop under kitchen/your_working_folder/system/
Edit build.prop with notepad++
You can Edit These Values as desired:-
Code:
ro.build.id=
ro.build.display.id=
ro.custom.build.version=
ro.build.version.release=This is Andriod version That Displays in Settings
ro.product.model=
ro.product.brand=
ro.product.name=
ro.product.device=[B][U][COLOR="Red"]NAME OF FILE WHICH YOU USED TO REGISTER YOUR DEVICE TO KITCHEN[/COLOR][/U][/B]
ro.product.manufacturer=
ro.build.bluetooth.name=
EDIT BELOW LINES TO SET YOUR TIMEZONE AND AREA REGION.You can find your default details in your stock rom's build.prop which you extracted earlier.
Code:
ro.product.locale.language=(en for English,ru for Russian and other similar codes for other language)
ro.product.locale.region=(us for usa, IN for india etc.)
persist.sys.timezone=( Asia/kolkata for india,Asia/... different for different regions)
Add this line if you are porting from higher resolution deice or lower resolution device.If from higher to lower then put lower values and if lower to higher then put higher values.
Code:
ro.sf.lcd_density=xxx
Now after editing done save it and exit.
Patching Rom With Some STOCK Rom Files:-
Copy modem.img from stock Rom- System/etc/firmware to kitchen/working_folder/system/etc/firmware and replace it.
Copy libcamercustom.so file from stock Rom- System/lib to kitchen/working_folder/system/lib and replace it.
Copy mtk_stp_wmt.ko file from stock Rom- System/lib/modules to kitchen/working_folder/system/lib/modules and replace it.If ROM not booted then replace whole modules.
Copy Generic.kl file from stock Rom- System/usr/keylayout to kitchen/working_folder/system/usr/keylayout and replace it.
Download any launcher apk from net link nova,apex etc and paste into kitchen/working_folder/system/app/
If after Building rom from next step,your rom did not booted then replace these files from stock to port then build rom.
1)system/etc/firmware
2)system/lib/hw
3)system/lib/modules
4)system/vendor
Building Rom
After all above steps done,now switch to kitchen and press 99 to build ROM.
But before pressing 99 check that you put name of file by which you registered your device to kitchen in build.prop/ro.product.device="".If you registered with name x then put like this-ro.product.device="x"
If you have not done above step then you will get installation aborted error during installation.If you are confused to register device send me required fies as asked by me in above post.
After all checked now press 99
Select Build Option 1 then hit Enter
Now it will ask to zip-lang the apk,do as your wish.
After that step it will convert Updater Script and ask two option,Proceed or cancel,then Proceed by pressing "y".
It will then start making update.zip.Wait some time.
Next it will ask to sign the zip or not?You should go with default by signing update zip by hitting Enter or Pressing "y" then pressing enter.It will take some time.
After that if you want to change your ROM name then put desired name by pressing y or leave as it is by hitting Enter or 'N' then enter.
Collect you rom.zip from Output_zip folder created under kitchen directory.
Flash it and check it.
If you find some bugs then see post below to solve bugs or if you are not able to find bug solution below then post it.I will tell you how to solve it if i know.
I have ported 10+ Roms using this method,this should work for you too.Hopes that your ROM will boot.Good Luck.
SOLVING BUGS
BUG SOLVING USES HIT AND TRIAL METHOD.I mentioned one or more ways to solve,you try one by one and see which works for you.
FM NOT WORKING:-
COPY THESE FILES FROM STOCK TO PORT:-
\system\lib\libaudio.a2dp.default.so
\system\lib\libaudio.primary.default.so
\system\lib\libaudiocompensationfilter.so
\system\lib\libaudiocustparam.so
\system\lib\libaudioeffect_jni.so
\system\lib\libaudioflinger.so
\system\lib\libaudiosetting.so
\system\lib\libfmar1000.so
\system\lib\libfmcust.so
\system\lib\libfmjni.so
\system\lib\libfmmt6616.so
\system\lib\libfmmt6620.so
\system\lib\libfmmt6626.so
\system\lib\libfmmt6628.so
OR try this
system/etc/firmware/mt6620_patch_e3_hdr.bin
system/etc/firmware/mt6620_patch_e6_hdr.bin-> If yours is MT6628, you'll need to patch all mt6628_fm_*_*.bin too
system/etc/firmware/WMT.CFG-> This is the antenna cfg, without this, FMradio cannot receive clearly
system/lib/modules/mtk_fm_drv.ko
system/lib/libfmcust.so
For WiFi Bluethooth:-
system/lib/modules/mtk_wmt_wifi.ko -> After patching, both works & can be individually switch on/ off
system/lib/libbluetooth_mtk.so
system/lib/libbluetoothem_mtk.so -> MTK Engineering will show MT6628 if not patch...
system/etc/firmware -> if yours is MT6628, you'll need to patch all WIFI_RAM_CODE_* too
For GPS:-
->>>> system/xbin/libmnlp
or, If you porting From MT6628 to MT6620, some apps at system/vendor/operator/ is blocking GPS so just delete all apps & use MTK Engineering mode to confirmed it...
Edit in build.prop
fmradio.driver.chip=1 -> if yours is MT6628 then change it to 3
mediatek.wlan.chip=MT6620 -> if yours is MT6628 then change last digit to 8
mediatek.wlan.module.postfix=_mt6620 -> if yours is MT6628 then change last digit to 8
For Camera:-
->Unpack boot.img again and go to BOOT-EXTRACTED/boot.img-ramdisk/init.project.rc and edit with notepad++,also open stock bootextracted/ramdisk/init.project.rc.Now find camera permissions and replace whole camera line with stock camera lines.
->then open init.rc of both port and stock and find camera lines and copy/replace camera lines from stock to port.
->Now repack boot.img
OR
copy these from stock to port
system\lib\hw\camera.default.so --- (if you have two files like camera.goldfish.so delete this the one with the goldfish)
\system\lib\libcamera_client.so
\system\lib\libcameracustom.so
\system\lib\libcameraprofile.so
\system\lib\libcameraservice.so
or
copy from system/lib of stock to port.
- libmhal.so
- libmhalcontent.so
- libmhaldrv.so
- libmhalmdp.so
- libmhalpipe.so
- libmhalscenario.so
- libmhalutility.so
or
Put libcamdrv.so of rom only or campare the file of size of your porting rom file and the base rom then whose size is same leave it and whose size is greater in ur stock rom jst add and replace that file only.
or
lib3a.so
liba3m.so
libacdk.so
libaudioflinger.so
libc.so
libcam.camadapter.so
libcam.campipe.so
libcam.camshot.so
libcam.client.so
libcam.paramsmgr.so
libcam.utils.so
libcam_camera_exif.so
libcamalgo.so
libcamdrv.so
libcamera_client.so
libcamera_jni_eglfence.so
libcamera_metadata.so
libcameracustom.so
libcameraservice.so
libgn_camera_feature.so
libexif
libfeatureio.so
libfrsdk.so
libft.so
libgcomm_jni.so
libgoggles_clientvision.so
libgui.so
libimageio.so
libja3m.so
libjni_mosaic.so
(Skip if any missing)
or
Replace camera.apk in sysyem/app
And do a ctrl+f search in system/lib for anything called 'camera', 'camrecorder', or just 'cam' and replace those.
Storage mount Problem Fix:-
copy paste sytem/etc/vold.fstab from stock to port
USB NOT MOUNTING IN PC FIX:-
copy init.usb.rc from stock boot.img extracted to port and repack.
Audio Problem Fix:-
copy paste sytem/lib/all audio lib file from stock to port.(search by ctrl+f)
ICON RESIZER:-
see these
http://forum.xda-developers.com/showthread.php?t=2219584
http://forum.xda-developers.com/showthread.php?t=2380513
DATE AND TIME ERROR FIX:-
check build prop region and compare and replace from stock build prop.
or
Use gravity box date and time fix
Minimum Brightness:-
ro.init.screen_brightness=110 in build prop
If App Force Closing:-
Use Updated App or if only rooted apps are getting Force close then Check Root
If nothing helped then removed that apk from system folder.
If a weird image Showing Between Boot logo and boot animation:-
Use stock rom's system/media/images/boot_logo in port.
TWEAKING&MODIFICATION
BUILD.PROP TWEAKS
HOW TO ADD:-Open Build.prop with Notepad++ and copy and paste these tweaks lines and save it.
Force launcher into memory
Code:
ro.HOME_APP_ADJ=1
Raise JPG quality to 100%
Code:
ro.media.enc.jpeg.quality=100
VM Heapsize; higher the RAM, higher the hp can be.
Code:
dalvik.vm.heapsize=48m
Render UI with GPU
Code:
debug.sf.hw=1
Decrease dialing out delay
Code:
ro.telephony.call_ring.delay=0
Helps scrolling responsiveness
Code:
windowsmgr.max_events_per_sec=150
Save battery
Code:
wifi.supplicant_scan_interval=180
pm.sleep_mode=1
ro.ril.disable.power.collapse=0
Disable debugging notify icon on statusbar
Code:
persist.adb.notify=0
Increase overall touch responsiveness
Code:
debug.performance.tuning=1
video.accelerate.hw=1
Raise photo and video recording quality
Code:
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
Signal (3G) tweaks
Code:
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=10
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
Net speed tweaks
Code:
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
Disable blackscreen issue after a call
Code:
ro.lge.proximity.delay=25
mot.proximity.delay=25
Fix some application issues
Code:
ro.kernel.android.checkjni=0
Phone will not wake up from hitting the volume rocker
Code:
ro.config.hwfeature_wakeupkey=0
Force button lights on when screen is on
Code:
ro.mot.buttonlight.timeout=0
Disable boot animation for faster boot
Code:
debug.sf.nobootanimation=1
Miscellaneous flags
Code:
ro.config.hw_menu_unlockscreen=false
persist.sys.use_dithering=0
persist.sys.purgeable_assets=1
dalvik.vm.dexopt-flags=m=y
ro.mot.eri.losalert.delay=1000
Init.d TWEAKS
HOW TO ADD:-
-->>For adding init.d tweaks you must add init.d support from kitchen by using option "14" then you will see a new folder will be created under system/etc/"init.d"
-->>Now open a empty file with notepad++ and add- " #!/system/bin/sh " at top and then add below lines then save it with name as you wish.Make separate file for each tweak.
[*]Strict minfree handler tweak
Code:
echo "2048,3072,6144,15360,17920,20480" > /sys/module/lowmemorykiller/parameters/minfree
[*]Internet speed tweaks
Code:
echo "0" > /proc/sys/net/ipv4/tcp_timestamps;
echo "1" > /proc/sys/net/ipv4/tcp_tw_reuse;
echo "1" > /proc/sys/net/ipv4/tcp_sack;
echo "1" > /proc/sys/net/ipv4/tcp_tw_recycle;
echo "1" > /proc/sys/net/ipv4/tcp_window_scaling;
echo "5" > /proc/sys/net/ipv4/tcp_keepalive_probes;
echo "30" > /proc/sys/net/ipv4/tcp_keepalive_intvl;
echo "30" > /proc/sys/net/ipv4/tcp_fin_timeout;
echo "404480" > /proc/sys/net/core/wmem_max;
echo "404480" > /proc/sys/net/core/rmem_max;
echo "256960" > /proc/sys/net/core/rmem_default;
echo "256960" > /proc/sys/net/core/wmem_default;
echo "4096,16384,404480" > /proc/sys/net/ipv4/tcp_wmem;
echo "4096,87380,404480" > /proc/sys/net/ipv4/tcp_rmem;
[*]Vm management tweaks
Code:
echo "4096" > /proc/sys/vm/min_free_kbytes
echo "0" > /proc/sys/vm/oom_kill_allocating_task;
echo "0" > /proc/sys/vm/panic_on_oom;
echo "0" > /proc/sys/vm/laptop_mode;
echo "0" > /proc/sys/vm/swappiness
echo "50" > /proc/sys/vm/vfs_cache_pressure
echo "90" > /proc/sys/vm/dirty_ratio
echo "70" > /proc/sys/vm/dirty_background_ratio
[*]misc kernel tweaks
Code:
echo "8" > /proc/sys/vm/page-cluster;
echo "64000" > /proc/sys/kernel/msgmni;
echo "64000" > /proc/sys/kernel/msgmax;
echo "10" > /proc/sys/fs/lease-break-time;
echo "500,512000,64,2048" > /proc/sys/kernel/sem;
[*]Battery tweaks
Code:
echo "500" > /proc/sys/vm/dirty_expire_centisecs
echo "1000" > /proc/sys/vm/dirty_writeback_centisecs
[*]EXT4 tweaks (greatly increase I/O)
(needs /system, /cache, /data partitions formatted to EXT4)
Code:
tune2fs -o journal_data_writeback /block/path/to/system
tune2fs -O ^has_journal /block/path/to/system
tune2fs -o journal_data_writeback /block/path/to/cache
tune2fs -O ^has_journal /block/path/to/cache
tune2fs -o journal_data_writeback /block/path/to/data
tune2fs -O ^has_journal /block/path/to/data
[*]Perfect mount options
Code:
busybox mount -o remount,noatime,noauto_da_alloc,nodiratime,barrier=0,nobh /system
busybox mount -o remount,noatime,noauto_da_alloc,nosuid,nodev,nodiratime,barrier=0,nobh /data
busybox mount -o remount,noatime,noauto_da_alloc,nosuid,nodev,nodiratime,barrier=0,nobh /cache
[*]Flags blocks as non-rotational and increases cache size
Code:
LOOP=`ls -d /sys/block/loop*`;
RAM=`ls -d /sys/block/ram*`;
MMC=`ls -d /sys/block/mmc*`;
for j in $LOOP $RAM
do
echo "0" > $j/queue/rotational;
echo "2048" > $j/queue/read_ahead_kb;
done
[*]MicroSD card speed tweak
Code:
echo "2048" > /sys/devices/virtual/bdi/179:0/read_ahead_kb;
[*]Defrags database files
Code:
for i in \
`find /data -iname "*.db"`
do \
sqlite3 $i 'VACUUM;';
done
[*]Remove logger
Code:
rm /dev/log/main
[*]Ondemand governor tweaks
Code:
SAMPLING_RATE=$(busybox expr `cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency` \* 750 / 1000)
echo 95 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo $SAMPLING_RATE > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate
[*]Auto change governor and I/O Scheduler
Code:
echo "vr" > /sys/block/mmcblk0/queue/scheduler
or
echo "sio" > /sys/block/mmcblk0/queue/scheduler
[*]Governor (Best: Minmax > SavagedZen > Smoothass > Smartass > Interactive) - needs kernel with these
Code:
echo "governor-name-here" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
[*] Disable normalize sleeper
Code:
mount -t debugfs none /sys/kernel/debug
echo NO_NORMALIZED_SLEEPER > /sys/kernel/debug/sched_features
GPS.conf TWEAKS
How To:-Create or edit your /system/etc/gps.conf with a Notepad++.
Benefit:-For improving GPS lock time and signal.
-->>SE supl for A-GPS (better than Nokia's or Google's)
Code:
SUPL_HOST=supl.sonyericsson.com
SUPL_PORT=7275
Or DOWNLOAD this patched gps.config
APN TWEAKS
-->>apns-conf.xml located at system/etc/"apns-conf.xml"
-->>Edit apns-conf.xml with notepad++ to add desired apns.
-->>Use CyanogenMOD's APN list file - it's one of the most complete.Download from google.
-->>You can use Mine one too- Downlaod
ADS BLOCK TWEAK
(Lots of developers are supported Through it so please think twice before adding it.)
-->>You can use mine hosts file.Download
-->>You can refer these url for getting file content-
http://www.mvps.org/winhelp2002/hosts.txt
http://pgl.yoyo.org/adservers/serverlist.php?showintro=0;hostformat=hosts
-->>hosts file are located to system/etc/"hosts"
USE LATEST SUPERUSER APP AND SU BINARY
Downlaod From here
USE PORTED APPS IN YOUR ROM
HERE IS LINK OF HUGE COLLECTION OF PORTED APPS:-CLICK
How to Implemant Ported Apps?
->Download it and open its zip.
->Now open system folder in zip and drag and drop all files to port rom means copy all system folder contents only to port system folder.
More things will be added soon.
THEMING
I will discuss very short on Theming,rest search on Google.
[START]
SETTING UP APKTOOL:-
->>If you have installed apktool and java then you can start.
->>Now go to the extracted apktool folder and hold "SHIFT" keyboard button and then right click mouse.
->>Here select-Open command window Here" option.
->>For Theming you need to decompile the apk which you want to theme,so grab those apks first and put into apktool folder.
-->>Also take framework-res.apk and medaitek-res.apk and put these also in apktool folder.
->>For decompiling system folder apk,you need to install framework-res.apk and medaitek-res.apk first.So in command window input-
Code:
apktool if framework-res.apk
apktool if mediatek-res.apk
->>hit enter one after one.So you will get message that apk installed to....for both apks.
->>Always write words carefully in command terminal,write same words as apks in apktool folder.
NOW YOU CAN DECOMPILE SYSTEM APKS OF THE ROM WHOSE FRAMEWORK YOU HAVE INSTALLED.IF YOU DONE WITH THAT ROM AND WANT TO MODIFY NEXT ROM APKS THEN
GO TO C:\users\yourusername\apktool and delete all present apks.
Lets start Decompiling:-
->>Open command terminal under apktool,if you already opened then good.
Lets assume that you are decompiling launcher.apk then,
->>Type this below command to decompile apk.You need to replace only apk name....
Code:
apktool d launcher.apk
->>and hit enter.It will decompile in same apktool folder.
->>Now open it and modify it as you wish.
->>For editing its images and theme and look,go to drawable-hdpi folder replace pngs with same resolution pics or edit with photoshop or gimp etc.
->>You can do major modification in thems with systemUI.apk
->>And for rest take help from google.I will update this and add more stuffs when i get time.
->>Now after all modifications done,now lets compile apk.Use command below and replace apk name....
Code:
apktool b launcher.apk
->>Hit enter.Now you have to drag and drop meta-inf and AndroidManifest.xml of launcher.apk which was placed under apktool directory for decompiling(use 7 zip to open apk and drag files from it) to apktool directory/launcher/build/apk/ and replace when prompt.
->>Now again repeat this command in command bar-
Code:
apktool b launcher.apk
->>hit enter,Now this time you can collect you compiled apk from- apktool directory/launcher/dist/"launcher.apk"
->>I know you may get confused by all these steps so watch an awesome video by nero young to clear your confusions-VIDEO
MAKING PATCHES ZIP
IT WILL BE VERY EASY FOR YOU TO MAKE PATCHES ZIP IF YOU DOWNLOAD THESE BELOW 4 FILES :-
1) ONLY BOOT.IMG PATCH ZIP
2) ONLY SYSTEM FOLDER PATCH ZIP
3) SYSTEM FOLDER + BOOT.IMG PATCH ZIP
4) KERNEL ZIP & KEREL REVERT ZIP.
Download above Zips.
First zip is for extracting only boot.img patch .
Second zip will patch system folder's all folder.
Third Zip will allow you to patch both boot.img and system folder contents of your rom.
Fourth one will allow you to flash any custom kernel if available for your device.
How to use all above patches.zip?
->For first one open zip using 7zip and drag the boot.img you want to patch to it then flash it with cwm
->For second one,if you want to add an apk or any other lib files or replce lib file or any other system folder files to your rom then drag and drop that file to second zip with correct folder path.
->Third one will allow first and second to flash at once.
->Fourth zip is for custom kernel,Custom kernel contains two part,boot.img and another system/lib/modules/lots of file.For custom kernel flashing or reverting with stock kernel,you need to drag and drop boot.img and system/lib/modules/ to fouth zip and flash via cwm.
IF YOU WANT TO ADD UBOOT.BIN TO ROM OR FLASH UBOOT.BIN THEN USE BELOW LINE IN UPDATER SCRIPT:-
package_extract_file("uboot.bin", "/dev/uboot");
Click to expand...
Click to collapse
ADDING OTA UPDATE
You will need to download its apk first- OTA_UPDATER_DWONLAOD
You will also require all 4 patch zips from above post.
STEPS TO ADD OTA UPDATE :-
Put OTAUpdater-1.0.5.apk in system/app folder.
Edit build prop by notepad++ and add these three lines:-
Code:
otaupdater.otaid=<ROM ID any you can pick>
otaupdater.otatime=<Date/time of this build in yyyymmdd-hhmm format>
otaupdater.otaver=<The human-readable version number/name>
EXAMPLE FROM MY ROM:-
Code:
otaupdater.otaid=xos
otaupdater.otatime=20130930-1553
otaupdater.otaver=1.0
Now you are good to receive and send OTA update to your Rom....but first you have to setup account online.
Registering Device Online
Go to https://www.otaupdatecenter.pro/ and Register there.
After successful registration,click on +Add Rom.A form will be opened then.Fill it.
1)Enter Rom name same as you written in build prop display id.
2)Enter ROM OTA ID (as in build.prop)
3)Enter ROM version (as in build.prop)
4)Enter OTA date/time here (yyyymmdd-hhmm, as in build.prop).
5)Enter download url.(put any URL right now,we are just adding rom first)
6)Enter MD5 file-hash.(put any file md5 check sum.we will edit it when we provide update)
7)Put any Change log...write anything
8)On last column put the name of your device same as in build prop "ro.product.device= ".In my case i use a110q and here is my code in build prop:-
Code:
ro.product.device=a110q
Lastly do not tick on check box as it will make OTA private.
Now your device is registered.
PROVIDING OTA UPDATE:-
Create update using any of my 4 files which you need to update.Lets assume you want to update an apk or add an apk,so you will use my only system folder patch zip.
Now open my provide zip using 7zip and drag and drop your apk with its path.As i provided patch with only system folder and no path forward.So open system folder and right click and create folder,name it "app" and then open app and drag apk in it.
If you were updating bootanimation then you should create media folder under system folder of my zip.
Now after making patches done.Download the Sign-em! from HERE and extract it anywhere.
You will get input,output and some more files....put your zip in input and run "sign-em.bat",it will sign your update zip and also give you its md5checksum.Signing your update is necessary.
After signing zip upload it to drop-box (suggested and tested) and after upload finished,click on download button and copy its url which is generated after that.Means copy url which is prompt in download manager if you using.If you do not use this url then OTA will not work.
Again open https://www.otaupdatecenter.pro/ and go to rom list and click on update rom.
This time put download URL which was generated after clicking download button on dropbox in URL box and also put its md5 checsum which was generated in output folder text file of sign-em!!
And change version also,put 2.0 in version if earlier 1.0,you can also put 1.1 or 1.2 any you want but change it.
And lastly put new date and time as per its format and give your update description if you want.
Check all things then click Update.All done you are good to get update.
Your mobile should have data connection enabled all time during this process.
if any confusion ask me or see faq on https://www.otaupdatecenter.pro/
WIP
ADDING CUSTOM KERNEL
CUSTOM KERNEL ZIP STRUCTURE:-
->>Meta-inf
->>system/lib/modules
->>boot.img
For Adding it to your rom extract your kernel zip or drag and drop system/lib/modules/all files to port rom and replace all.
Then switch to kitchen and press "0" for advance option and then 12 for extracting boot.img.Here press "a" for extracting boot.img from any folder.Hit enter,you will see a folder created named like "bootimg_041114_230352" and put your custom kernel boot.img in it.
Now press Enter then kitchen will extract it in same folder.
Then back to kitchen 12 th menu of extraction of boot.img,here press "w" to extract boot.img from working folder,so it will extract boot.img from port rom(which is present in working folder) to BOOT-EXTRACTED folder under Kitchen.
Now copy zImage from previous extracted folder "bootimg_041114_230352" to BOOT-EXTRACTED folder and replace it.
Press b in kitchen to repack boot.img.All done.
What we have done above- We used zImage(from boot.img) of custom kernel in port rom boot.img and used all system/lib/modules folder from Custom kernel zip.
ADDING SMALL BUT COOL STUFFS
ADDING DESIRED TEXT DURING ROM INSTALLATION:-
After Finishing your Rom,drag and drop Meta-inf/com/google/android/"Updater-script" to anywhere in your pc.
Now open it with Notepad++,and use this code to dislpay your texts in installation:-
Code:
ui_print(" ");
Put any alphabet or symbol or digit between (" ") and it will show during Installation.
For generating cool Ui prints you can search Google about text to ASCII converter websites and put your text and get cool texts for installation window.
After all modifications done,drag and drop back updater script to zip.
For Example:-
Code:
ui_print("========STARTING INSTALLATION===========");
ui_print("========================================");
ui_print(" |\ _,--------._ / | ");
ui_print(" | `.,' `. / | ");
ui_print(" ` ' BEAST ,-' ' ");
ui_print(" \/_ _ ( / ");
ui_print(" (,-.`. ,',-.`. `__,' ");
ui_print(" |/*\ ),-','*\`= ,'.` | ");
ui_print(" `._/) -'.\_,' ) ))| ");
ui_print(" / (_.)\ . -'// ");
ui_print(" ( /\____/\ ) )`'\ ");
ui_print(" \ |V----V|| ' , \ ");
ui_print(" |`- -- -' ,' \ \ _____ ");
ui_print(" ___ | .' \ \ `._,-' `- ");
ui_print(" `.__,`---^---' \ ` -' ");
ui_print(" -.______ \ . / ______,- ");
ui_print(" `. ,' ");
ui_print("=== STOCK BEAST ROM BY DIGYVIJAY KR. ===");
ADDING AROMA INSTALLER:-
Take help from HERE
And here is an HELPFUL VIDEO.
I will explain these stuffs later
ADDING CUSTOM BOOT ANIMATION & SHUT-ANIMATION:-
You Can find bootanimation and shutanimation under system/media folder.If you ported from larger resolution device or smaller resolution device then animation will look weird.so you need to resize it or add own made one.
[*]For adding own or editing previous boot-animation you will need this software-Download thanks to @despotovski01 for this)
[*]Now install it.You will also need to know your mobile resolution for making or resizing boot-animation or shut-animation to your size.
FOR RESIZING BOOT-ANIMATION & Shutanimation:-
[*]Take bootanimation.zip from system/media and extract it to any folder.
[*]Now you will see lots of images in it under its sub folder like part0 part1...
[*]Resize all images to your screen resolution.You can use some softwares to resize them easily.Find on Google.(do not mess with serial number order)
[*]Now make a New folder and make another folder under it named- "part0" and put your all resized pngs to it.(from all folders you have in your bootanimation.zip)
[*]Start Boot Animation Factory and Click on "create a new boot-animation",then choose "folder" and click OK.
[*]Now click choose folder button and browse your created folder in which you put part0 folder.DO not choose part0 folder,choose is outer folder.
[*]Here Click on add loop then select part0 folder in prompt dialog box and click on add.
[*]If you want to repeat animation then tick repeat.Now you should preview it first before saving.you can adujust animation speed by clciking on text above your loop created,and click to edit it and then edit FPS according to need.Here is the example line:-30 is FPS here and rest is reso...
Code:
480,854,30
[*]If everything fine then click save boot-animation and save it with name same as in sytem/medaia folder and then replace it.Its all done.
[*]Same process for shut-animation.
FOR CREATING BOOT-ANIMATION & Shutanimation:-
You will have to use own creativity skill for creating its frames.Some knowledge of Photoshop required.
Design your boot animation frames and manage it serially.
Create a folder with any name and create another sub folder in it named "part0" and put all your designed pngs in it.
Start Boot Animation Factory and Click on "create a new boot-animation",then choose "folder" and click OK.
Now click choose folder button and browse your created folder in which you put part0 folder.DO not choose part0 folder,choose is outer folder.
Here Click on add loop then select part0 folder in prompt dialog box and click on add.
If you want to repeat animation then tick repeat.Now you should preview it first before saving.you can adujust animation speed by clciking on text above your loop created,and click to edit it and then edit FPS according to need.Here is the example line:-30 is FPS here and rest is reso...
Code:
480,854,30
If everything fine then click save boot-animation and save it with name same as in sytem/medaia folder and then replace it.Its all done.
Same process for shut-animation.
ADDING DESIRED BOOT LOGO:-
Download logo builder-Download And install.
Get Stock logo.bin -Get the file from your device (/dev/logo) or from stock Rom sp tools flasher.
Open Logo-builder and Click Create New Project
.,? ,1
Now Select the logo.bin file you extracted from the device or took from stock rom.
Make a new folder for the project, any name will work
0Select the folder and click on OK
You will see a progress bar running down. After finishing, you will get a whole bunch of images in the above selected folder
After that,Open the folder containing all the images which you made earlier.
Here Edit or replace" img1.png and img39.png " but keep one thing in mind that use same name and same resolution and same format(png) for replacing.
Click on "make" button on LogoBuilder and you will get update.zip in the folder you made for this project.You can flash this update.zip directly via cwm or you can add to your rom by using below step.
For using logo in your rom,extract logo.bin from update.zip and drag and drop to port rom zip or you can also put this in working folder of kitchen before making Rom.After that,add below code in updater-script to extract your logo-
Code:
package_extract_file("logo.bin", "/dev/logo");
Reserved.
Great Guide
Best Guide Thanks For Helping New Developer like me
yes best guide ever seen for Mediatek devices ....please add seperate section in this thread for MIUI and Lewa os framework and bug solving:fingers-crossed:
excellent guide
Not booting
Everything i done mentioned by you .... But, after flashing with the ported rom created by me , my device stucks in booting.... i don't understand where is the problem actually....
I just ported to this rom
http://forum.xda-developers.com/can...-april-note-3-chrizelnotethree-v3-7a-t2707462
for my mmx canvas 2 plus a110q....
plz help me.....
sawankumar2012 said:
Everything i done mentioned by you .... But, after flashing with the ported rom created by me , my device stucks in booting.... i don't understand where is the problem actually....
I just ported to this rom
http://forum.xda-developers.com/can...-april-note-3-chrizelnotethree-v3-7a-t2707462
for my mmx canvas 2 plus a110q....
plz help me.....
Click to expand...
Click to collapse
remove uboot.bin if present.And also try replacing bootclasspath from stock init.rc to port init.rc
srinath2912 said:
yes best guide ever seen for Mediatek devices ....please add seperate section in this thread for MIUI and Lewa os framework and bug solving:fingers-crossed:
Click to expand...
Click to collapse
Ok i will add them next time i modify the post.....all suggestions are welcome,,,
chanti548 said:
excellent guide
Click to expand...
Click to collapse
thank-you my friend.......
DevendraMilmile121 said:
Best Guide Thanks For Helping New Developer like me
Click to expand...
Click to collapse
thanks milee
digyvijaykumar123 said:
remove uboot.bin if present.And also try replacing bootclasspath from stock init.rc to port init.rc
Click to expand...
Click to collapse
In which directory i found init.rc & bootclasspath .........
sawankumar2012 said:
In which directory i found init.rc & bootclasspath .........
Click to expand...
Click to collapse
under extracted boot.img/ramdisk/init.rc.........you will find bootclass path there.
sawankumar2012 said:
In which directory i found init.rc & bootclasspath .........
Click to expand...
Click to collapse
I'm uploading some screenshot here... It may help u to find my problem... these are the port roms screenshot which i wanna port for my mmx a110Q
Related
This is how I made ROM, I'll try to write the steps as simple as I can. For advanced users only!
Update 22/08/11:
Revised packaging steps.
Update 13/08/11:
Removed unwanted method for ROM cooking.
Update 04/08/11:
Modified extract and repack ROM guide and added extracting system.rfs guide.
Things you need:
Base firmware
Archiver software (7zip recommended)
Any Linux environment to build ROM or Cygwin
APK Manager to optimize and decompile *.apk files
MagicISO (Optional) if you want to extract system.rfs
And the last thing is... You need enough experience in android world
So, here is the steps to cook a ROM:
Flash your phone with your desired base firmware
Make required modifications
Pull system.rfs from your phone by running this command on adb shell or Terminal Emulator:
Code:
dd if=/dev/stl12 of=/sdcard/system.rfs
Extract any *.tar.md5 files from your base firmware to your working folder with 7zip
Replace the current system.rfs with your modified one
EDIT: Pack your ROM by running this code via terminal or just pack it with 7zip/WinRAR as *.tar
Code:
tar -H ustar -c * >> ROMNAME.tar
change ROMNAME to your desired, well, ROM name.
Here is (yet) useful guide to modify your ROM.
Extract system files on system.rfs to make modding easier:
Extract PDA file (*.tar.md5) files with 7zip
Open system.rfs with MagicISO
To extract it, just drag and drop
NOTE: Never edit your ROM with MagicISO because the file permissions will be ignored, use MagicISO only for extracting files from system.rfs
Deodex, and Zipalign (optimize) your ROM apk files:
Ready to use deodex + root for KPN: http://forum.xda-developers.com/showthread.php?t=1196230
Ready to use deodex + root for KPH and other firmware: http://forum.xda-developers.com/showthread.php?t=1118048
Open APK Manager
To zipalign your apk files, in apk manager folder /place-apk-here-to-batch-optimize put your:
framework-res.apk, twframework-res.apk and all system apk
but not these:
AxT9IME, Calculator, Camera, Email, MMS, Phone, Screen Capture, Settings, Swype, Thinkdroid, Voice search
Choose Choose option 15
Then choose both (zp)
Let it run and done.
Now put back the apk files where they belong in the ROM.
How to put these apk files to my ROM? Copy these files to appropriate locations, such as /system/app to your ROM's /system/app, and etc.
Another handy modification guide:
Unpack and repack boot.img - http://forum.xda-developers.com/showthread.php?t=1173427
Convert firmware filesystem to ext4 - http://forum.xda-developers.com/showthread.php?t=1202049
Overscroll glow for any firmware - http://forum.xda-developers.com/showthread.php?t=1215933"
Give thanks to all dev who made that possible!
If you have more guides to put here, please PM me.
Am I pertamax?
hehe..just kidding.
Nice Info....great share.
I would want the Fla.sh Rom :'(
Thats a gr8 share...Thank you...)
saiftheboss7 said:
I would want the Fla.sh Rom :'(
Click to expand...
Click to collapse
sorry... once again, I'm sorry, I can't continue my ROM
Helpful thread man!
Thanks!
Great job taking your time to make this! Unfortunately, i dont even know the basics but now I know where to check when I do
fla.sh said:
sorry... once again, I'm sorry, I can't continue my ROM
Click to expand...
Click to collapse
Hey!
THX man, nice thread. Very useful!
Just PM to MOD, that they close you previous thread, a bout fla.sh.ROM. Or ppl just waiting it and asking.
CHEERS!
i think the most troublesome problem i encounter is to repack system.rfs. yes it can be mounted in magiciso, but howto repack/compile it back?
an0nym0us_ said:
i think the most troublesome problem i encounter is to repack system.rfs. yes it can be mounted in magiciso, but howto repack/compile it back?
Click to expand...
Click to collapse
Just save it.
didnt work when i just save it. my device got bootloop
an0nym0us_ said:
didnt work when i just save it. my device got bootloop
Click to expand...
Click to collapse
What modification you've added to your ROM? Maybe that modification causing the problem...
fla.sh said:
What modification you've added to your ROM? Maybe that modification causing the problem...
Click to expand...
Click to collapse
As Linux, MagicISO read RFS image as a FAT filesystem. File permissions can not be maintained. A better way but need linux:
1. Mount system.rfs as FAT and mount it to /tmp/rfs
2. Make ext4 image, and mount it to /tmp/system
3. Copy /tmp/rfs contents to /tmp/system
4. Make modification inside /tmp/system
5. Fix file permissions inside /tmp/system
6. Umount both image
7. Make ODIN flashable image, contains system.rfs (now in ext4 format) and CF-Root-S5830 boot and recovery image (for ext4 support)
8. Boot to Windows and flash your new firmware using ODIN.
ketut.kumajaya said:
As Linux, MagicISO read RFS image as a FAT filesystem. File permissions can not be maintained. A better way but need linux:
1. Mount system.rfs as FAT and mount it to /tmp/rfs
2. Make ext4 image, and mount it to /tmp/system
3. Copy /tmp/rfs contents to /tmp/system
4. Make modification inside /tmp/system
5. Fix file permissions inside /tmp/system
6. Umount both image
7. Make ODIN flashable image, contains system.rfs (now in ext4 format) and CF-Root-S5830 boot and recovery image (for ext4 support)
8. Boot to Windows and flash your new firmware using ODIN.
Click to expand...
Click to collapse
I use this command to mount rfs:
Code:
mount -o loop system.rfs /some_dir
Can you share us the command?
now thats really informative. thanks
ROM unpacking and repacking gude has been corrected. Tested by me. If you have any problems, just ask here.
Thanks.
I think you should add the date of update in the title, so that everyone can know about the update...
BTW thanks for this amazing guide...
Love it!!!
After making changes to system.rfs, how to save it as .rfs again?
adiles said:
After making changes to system.rfs, how to save it as .rfs again?
Click to expand...
Click to collapse
Please take look at the first page, it's updated, you know?
After I created md5 file and selected it in odin, it says "invalid image type" and "invalid model binary". How to solve that? After that I continued, skipped these errors and flashed, my phone stopped at boot screen with text "Galaxy ACE....". Plz help me
Newbies Thinks to make custom rom.. but dunno how
But when forever king's guide here NO prob!
Things we Need-
1 winrar or winzip
base rom
Brain
notepad ++
Things You will find in Rom (when will you extract-:
1- Boot.img (in some roms not)
2-System
3- Meta-inf
No need to touch Boot.img, Meta inf as i will tell later on
So open system folder
Open Build.prop in system folder and open with notepad++
Open this page
tweaks by forever king
See open build.prop tweaks
And open build.prop and scroll to last....
Press enter
and type
"#Tweaks"
Now add all tweaks in that Webpage
Mods
You can add many mods like
1 Beats Audio (2.3+)
2 Adrenaline Engine (2.3+)
3 SlaidyBoost (2.3+)
4 Megabassbeats (2.2+ need$ xloud)
U need to port them to ya fone , dont ask me as i also dunno l0l
Adding tweaks to ya rom (build.prop)
Open build.prop (system folder)
find line ' ro.build.id=xxxxxxx '
Now change this to ' ro.build.id=yournameorwhatever '
Adding Apps to your Rom
1 Open system>app (folder)
Add .apk files to it (copy n paste xD)
2 Adding Init.d tweaks (if your base rom having init.d support in boot.img)
Open this webpage
tweaks by forever king
Scroll down (lil bit)
and see init.d tweaks
Add like this
Make new file and paste any script
like
"echo "2048,3072,6144,15360,17920,20480" > /sys/module/lowmemorykiller/parameters/minfree"
this and save this file (no extention , save without .txt or any)
3 Adding bootanimation
Replacing bootanimation
-download bootanimation u want to use and rename it to "bootanimation.zip"
-delete animation u find in /./"rom"/system/media and then paste bootanimation u downloaded
Now modifying framework (u see statubar in rom and many tweaks)
Using UOT kitchen
Thanks to "CallMeVentus" for guide
Finnaly Done... will add more when i am freek xD >.<
Now Compress it in .zip
Now sign the Rom Signer
Open and see how
now flash Rom and test.....
if workeD then coool
Never say 'thanks' , hit it
Advance for N00bs
Never say thanks,hit it
How to make Rom transparent
See my guide = http://forum.xda-developers.com/showthread.php?t=1799373
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
How to decompile android app , u need this TUT for making rom transparent or editing apps..
See my guide= http://forum.xda-developers.com/showthread.php?t=1772220
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
How to add powermenu on your Rom
http://forum.xda-developers.com/showthread.php?t=811532
Thanks untermensch
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Some tweaks making Rom fast
http://www.mediafire.com/?t8rsdmedu5w2vo5 (by me)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
How to Deodex Rom and >odex back
Things nEeded
Code:
backsmali.jar
* smali.jar
* custom java.awt.jar
* dexopt wrapper
* recent version of busybox
Download this
Open CMD CD to folder extracted those scripts and type
1 Deodexing Framework files-
Code:
java -Xmx1024m -jar baksmali.jar -c :core.jar:bouncycastle.jar:ext.jar:framework.jar:android.policy.jar:services.jar:core-junit.jar -x android.policy.odex
(i am taking android.policy.jar as example , if framework.jar or whatever just change 'android.policy.jar' to 'framework.jar' and 'framework.odex'
This will make out folder
now smali that out folder by
typing
Code:
java -Xmx1024m -jar smali.jar out -o classes.dex
in CMD
HTML:
open android.policy.jar with 7zip without extracting
push the classes.dex created in the 7zip window in the root folder
close the 7zip windows and here is your deodexed android.policy.jar
2 Deodexing any App file i am taking systemUI.apk as example
Code:
java -Xmx1024m -jar baksmali.jar -c :am.jar:android.policy.jar:android.test.runner.jar:bmgr.jar:bouncycastle.jar:com.android.location.provider.jar:com.google.android.maps.jar:com.samsung.device.jar:com.yamaha.android.media.jar:core.jar:core-junit.jar:ext.jar:framework.jar:ime.jar:input.jar:java.awt.jar:javax.obex.jar:libvtmanagerjar.jar:monkey.jar:pm.jar:sec_feature.jar:seccamera.jar:sechardware.jar:secmediarecorder.jar:services.jar:sqlite-jdbc.jar:svc.jar:twframework.jar -x SystemUI.odex
Again out folder created now make it smali
by typing
Code:
java -Xmx1024m -jar smali.jar out -o classes.dex
in CMD
open SystemUI.apk with 7zip without extracting
push the classes.dex created in the 7zip window in the root folder
close the 7zip windows and here is your deodexed SystemUI.apk
Click to expand...
Click to collapse
3 Now we will learn to odexing back
1/ backup your original files (apk jar and odex) to /sdcard/Mod/
2/ copy modified deodexed files (.apk and .jar) in /system/framework/
3/ open a CMD prompt in the folder of adb.exe (usualy /android-sdk-windows/platform-tools/)
4/ type command :
Code:
adb shell
su
## for .JAR file :
dexopt-wrapper /system/framework/XXX.jar /system/framework/patched_XXX.odex /system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar
response must be :
--- BEGIN '/system/framework/android.policy.jar' (bootstrap=0) ---
--- waiting for verify+opt, pid=7194
--- would reduce privs here
--- END '/system/framework/android.policy.jar' (success) ---
## for .APK file :
dexopt-wrapper /system/framework/XXX.apk /system/framework/patched_XXX.odex /system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jaradb shell
su
## for .JAR file :
dexopt-wrapper /system/framework/XXX.jar /system/framework/patched_XXX.odex /system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar
response must be :
--- BEGIN '/system/framework/android.policy.jar' (bootstrap=0) ---
--- waiting for verify+opt, pid=7194
--- would reduce privs here
--- END '/system/framework/android.policy.jar' (success) ---
## for .APK file :
dexopt-wrapper /system/framework/XXX.apk /system/framework/patched_XXX.odex /system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar
It will makepatched_apknameyouodexing file now remove (renaming) "patched_" line so it will be "apknameyouodexing.odex"
Now copy Signatures- (in same CMD)
Code:
# if not already done ...
adb shell
su
# copy the original .odex and .jar in system/framework (not .apk) :
cp /sdcard/MOD/original.XXX.odex /system/framework
cp -f /sdcard/MOD/XXX.jar /system/framework # where XXX.jar is the original odexed .jar
# give all permissions to XXX.odex files :
chmod 777 /system/framework/original.XXX.odex
chmod 777 /system/framework/patched_XXX.odex
# copy signature :
busybox dd if=/system/framework/original.XXX.odex of=/system/framework/patched_XXX.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
response must be :
busybox dd if=/system/framework/original.XXX.odex of=/system/framewor
k/patched_XXX.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
20+0 records in
20+0 records out
20 bytes (20B) copied, 0.002042 seconds, 9.6KB/s
Done now odex/deodex your Rom , so easy!
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Changing splash Screen (bootsccreen before bootanimation)
Ok. 1st of all i dont maDe this script and i dont know who made it xD but i would day 'thanks' to Him
http://www.mediafire.com/?sr6lso6w7vj21o6
How to use this!! >>??
Decompile boot.img Scroll down to see HoW to decompile it/use DSIXDA kitchen
Ramdisk>initlogo.rle (make new folder and paste initlogo.rle into it)
now extract that downloaded kit in it
1 Now open CD to location and type
Code:
convert_image to rle.bat initlogo.rle
(if u named .rle file to 'yourfilename'
then type
Code:
convert image to rle.bat yourfilename.rle
2 the filename.raw file and filename.rle file will be created at the same location as filename.rle
Now yoU will see filename.png edit it like what you Want xD
3 For compiling filename.png to .rle , CD to that folder having dose files!
typE
Code:
convert rle to image.bat filename.png
Use this if you see Decompiled .rle Burred-
Code:
@bin\convert -depth 8 -size 333x774 rgb:initlogo.raw initlogo.png
(take your phone's size i just took which my mind told xD)
4 Now you will see new file named
filename.png.rle rename it to filename.rle
Done now replace it into your extracted boot.img and repack it
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Decompilng Boot.img
I didnt made this Script http://www.modaco.com/topic/340710-tool-edit-bootimg/ is originall thread thanks to him
Download Boot.img tools
So easy to use
Just extract it in folder
Now place boot.img also in it
Now open 'start.bat'
* Press 1 to decompile the boot.img
* replace the ramdisk.gz (if you want)
* replace the kernel (if you want)
* Press 2 and it will compile the boot.img again!
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Modifying updater-script (found in /META-INF/com/google/android)
Open with Notepad++
Now you can see in this pic theres written 'Welcome to Cm installer....'
{
"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"
}
How to make this!
open updater-script
you will see 1st line ! make enter so you can add 1 line (at first)
Now add
Code:
ui_print("your text anything");
Code:
package_extract_dir("system", "/system");
tells extract directory system to system (in android)
Code:
mount("system");
tells mount specific directory like u can change location to dev folder
Code:
unmount("/system");
means unmount from where you mounted ! before
Code:
show_progress(0.200000, 5);
tells us that show progress like you can see when installing Rom yellow lines comes (CWM) u can control by this. its by Seconds..
Code:
symlink("busybox", "/system/xbin/fold");
means make symbolic link to that file at folder 'xbin'
Code:
format("MTD", "system");
means format mounted system folder
Code:
delete("/data/local");
Tells that delete /data/local folder
Code:
set_perm(0, 0, 0777, "/system/bin/chka2sd");
set pem means setting permission like chka2sd permission rww-rww-rww
Code:
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
it means flash boot.img make raw file (image) at tmp/boot (afterwards android do which i dunno) and delete that file!
Now save this file
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Modifying settings.apk
Creed$ rom!
you can see 'author name' which is not in our normal settings!
how he D!d?
Decompile apk by apkmanager ( i wont tell again xD , not by apktool )
1 goto res>xml open "device_info_settings.xml"
2 scroll to last and add line before "</PreferenceScreen>" line
3 add this line
Code:
<Preference android:title="Rom name (or whatever" android:summary="My rom name (what ever)" style="?android:preferenceInformationStyle" />
you can add many of them
4 Now compile from apkmanager when ask delete any file from 'keep folder' delete this file from keep folder and Install apk
too easy!
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enabling CRT animation on 2.3x
CRT animation is dam cool animation effect when locking phone so see how to make in your rom
But what is it?
1 Decompile framework-res.apk
2 goto res>values>bools.xml
3 Change "<bool name="config_animateScreenLights">true</bool>" to "<bool name="config_animateScreenLights">false</bool>"
Done.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Swipe to clear notifications
http://forum.xda-developers.com/showthread.php?t=1483193
thanks hansip87
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
When i do something (just that thing which i moded) i got bootloap/loop!
1 Open that think you will get loop
2 open terminal
3 type
Code:
su
logcat>sdcard/logcat.txt
So end. i will add more if i got any in mind/guidE xD
A nice guide for the noobs, but I think all of this is a little basic. But if you keep adding onto this, then it will be a great guide.
Nice
asvantypography said:
Nice
Click to expand...
Click to collapse
thanks button dere
invasion2-- adding sooon!!
Is it possible to deodex from terminal emulator?
-XoRoX- said:
Is it possible to deodex from terminal emulator?
Click to expand...
Click to collapse
sooory dude! but u can thru fone.... I saw app' odex me ' or maybe it was 'deodex me' I dunno it works/not
Thanks for your work!
john9 said:
Thanks for your work!
Click to expand...
Click to collapse
button there >.< read....this..every user commenting btw welcome!
Thanks for this guide! I assume no linux dev environment is needed, cuz I can't, at least that's what happened with dsixda kitchen
Sent from my HTC_Amaze_4G using Xparent Green Tapatalk 2
eggydrums said:
Thanks for this guide! I assume no linux dev environment is needed, cuz I can't, at least that's what happened with dsixda kitchen
Sent from my HTC_Amaze_4G using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
press thanks n welcome...I will add sooon its long so its future plan xD
modifying settings tut is wrong.
we have to edit xml in strings and public also
lol ur wrong
Avilove.Cullen said:
modifying settings tut is wrong.
we have to edit xml in strings and public also
Click to expand...
Click to collapse
ps. I am not editing settings.xml!
its lyk this! I made it dude! public.xml?
which entry? of Icon? no Icon needed!
Well its comprehensive and noob proof
Just a side note: Always mention the link to original article of any forum especially the deodexing part!
Secondly as Avilove.cullen said the tutorial for modification in Settings is incomplete as you also have to kang up the respective strings in strings.xml
And FYI we need not modify public.xml only when you put icons or images
varun.chitre15 said:
Well its comprehensive and noob proof
Just a side note: Always mention the link to original article of any forum especially the deodexing part!
Secondly as Avilove.cullen said the tutorial for modification in Settings is incomplete as you also have to kang up the respective strings in strings.xml
And FYI we need not modify public.xml only when you put icons or images
Click to expand...
Click to collapse
ok... will makE comlelty fr noobs !
dude I sa!d credits to dere devs ok will add link soon xD
fr icons u r wrong
decompile microfire 2's rom decompil settings.apk lol seee fire icon deres entry in public.xml Icons- which sum roms having coloured icons ! seee I can calll aksh too he also say this!
its ofcourCe v need png entry in settings.xml (or whereva)
and 1 png of that name I'm drawable-xxx
For adding strings, adding those strings in string.xml and public.xml is not necessary.... u cat do that too... but it works without adding too... i checked it ma self.... just remv "@string\" and "your_text".....
When adding a new menu item you need to edit the layout right?
Sent from my LG-E739 using Tapatalk 2
mistere372002 said:
When adding a new menu item you need to edit the layout right?
Sent from my LG-E739 using Tapatalk 2
Click to expand...
Click to collapse
Actually this isn't fundamental
It depends on the original developer where he defines it
In case of settings.apk it is with xml folder.
varun.chitre15 said:
Actually this isn't fundamental
It depends on the original developer where he defines it
In case of settings.apk it is with xml folder.
Click to expand...
Click to collapse
OK so say you wanted to add a list item called start clock. You would add the preferencescreen code and specify the target in settings.XML only? You wouldn't add lines to Id.XML or strings.XML and values.XML and then specify where in the layout folder of the appropriate XML in that folder?
Sent from my LG-E739 using Tapatalk 2
Who knows the reason for always apps optimizing in my custom Rom in every reboot?( always android is upgrading)
Sent from my SK17i using xda premium
Sense Port Guide
Source:http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/164989-guide-how-i-port.html
This is NOT my guide, just posting it here!
This is a very difficult process that I hope you'll understand.
First step is to find a device that is preferably VERY similar to your device, in this instance I guess we would use the htc thunderbolt, which I've been told multiple times that it is used for the MT.
You're going to want to use CM7 for parts. Simple enough.
I will be referring the Sense ROM to SENSE and CM7 as BASE to simple things up. So remember that.
When I say replace, I would recommend deleting from one and adding it with the other
Open up Sense and Base in different windows.
Put in the boot.img from Base into Sense (make sure you put the original boot.img in some other place that you'll remember)
go into /system/usr on both
replace keylayouts and keychars from Base into Sense (this is just your keys)
download dsixda's kitchen (http://forum.xda-developers.com/showthread.php?t=633246)
Get the ROM you have so far set up in it and what not (I'm a little fuzzy at this part)
Once you get done with that, run the menu in terminal and navigate your way to decompile the boot.img (action key- "a") and then run the same thing except run the action key "w" to decompile the original boot.img. So the key here is to decompile both boot.img's.
Go into the ramdisk on both and go into init.rc
THE MOST IMPORTANT PART IN THIS (THE MATTER OF BOOT AND BOOTLOOP) IS THE LINE
"export BOOTCLASSPATH" near the top. It will have a bunch of lines after it. Now in the Base's boot.img, delete this whole line. Replace it with the lines from Sense's boot.img.
Now you can add anything else you want that looks like it belongs (preferably anything sense related)
Don't recompile the boot.img yet.
Now we add a2sd. To do this, just follow this guide (https://www.facebook.com/note.php?note_id=158823170833688)
The only thing you do in there is the edits to the init.rc, don't listen to the decompiling/recompiling mentions. Now you can go back into the menu for the kitchen and recompile the boot.img (action key - "b"). Now don't compile the WHOLE ROM, just take the new boot.img in working_** and put it into the Sense zip.
Now you're going to want to download my ROM (sorry, just don't feel like uploading each individual file) http://gannon5197.blogspot.nl/2012/03/got-sense-booted.html
And go into the /system/bin on both
these are the files you're going to need: a2sd, bash, apps2sd.hlp, busybox.a2sd, chka2sd, jita2sd, launcha2sd, starta2sd, and maybe possibly sh (try once without it)
And you're going to want to set permissions for each one of these in the updater-script (look at mine for references)
Now also look at my zip and you'll see move_cache_sd. Put that in yours and set permissions for it in updater-script (use mine for references)
After that, the other stuff is mainly just getting rid of all the bloatware, (look in /system/app and /system/media) I wouldn't delete any libs as of right now. If you try to flash it and it reboots recovery then it is too big.
If it is too big, you're probably going to want to move a lot of the apps to data. To do this, just make a file called data/app/put_your_apps_here on the root of the zip. You're going to have to set permissions for it in the updater-script, but use the test.zip I sent you in the original.
This will most likely get you booted. Nothing will likely work. Which is expected. If you have any problems, just use logcat. It will be your bestfriend.
Have fun porting
My Sense Rom
Based on sense 3.0 Htc Desire HD
Need Custom Partition : http://forum.xda-developers.com/showthread.php?t=1803746
Rom is here : https://www.dropbox.com/s/67gaqz6jgl8m3yr/u8800_sense_port_test.zip Not tested. Only devs and tester.
MiuiV4 Port Guide
Source:http://forum.xda-developers.com/showthread.php?t=1827256
This is NOT my guide, just posting it here!
The CM9 or ICS rom for your phone will be referred to as BASE. The MIUI Rom used for porting will be called PORT.
STEP 1:
Extract PORT to any folder and BASE to a working Kitchen folder or any other update.zip maker folder
STEP 2:
Delete app, framework and media folders from /system folder of BASE
Transfer these folders from PORT to BASE.
STEP 3:
Delete libandroid_runtime.so form /system/lib
Copy libandroid_runtime.so, content-types.properties and liblbesec.so from PORT /system/lib to BASE /system/lib
STEP 4:
Copy invoke-as from PORT /system/xbin to BASE
STEP 5:
Copy telocation.td , yellowpage.db and weather_city.db from PORT /system/etc to BASE
Copy miui-framework.xml from PORT /system/etc/permissions to BASE
STEP 6:
build.prop CHANGES:
ro.build.id=MIUI
ro.build.display.id=MIUI
ro.build.version.incremental=2.x.x (example: 2.8.3)
ro.config.ringtone=MI.ogg
ro.config.notification_sound=FadeIn.ogg
ro.config.alarm_alert=GoodMorning.ogg
THE ONES BELOW IF THERE..DONT ADD THEM NOR DELETE
ro.config.sms_received_sound=FadeIn.ogg
ro.config.sms_delivered_sound=MessageComplete.ogg
STEP 7
updater-script CHANGES:
1.) First to add a bit of style: put this: http://pastebin.com/iEDfSCdh
So as you can see...put it after the first line
2.) The important part
Code:
set_perm(0, 0, 06755, "/system/xbin/invoke-as");
FIX SUPERUSER ISSUES:
Download: http://download.chainfire.eu/204/SuperSU/CWM-SuperSU-v0.94.zip
Put the SuperUser.apk to /system/app and replace /system/xbin/su with BASE
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Added cm9 port from fb0(ideos x6) and cm9 compile guide.
I searched and reading a lot but can't find properly guide how to use miui patchrom for jellybean roms. So i decided share what i've found and put all in one guide.
1. First of all you need linux on your machine. I use kubuntu, installed from windows (wubi) ->http://www.kubuntu.org/getkubuntu/download
2. Now you need SDK tools for linux http://developer.android.com/sdk/index.html
-download and unzip it to for egz home/your_username/android-sdk-linux
-set PATH for tools and platform-tools folders
Code:
export PATH=/home/your_username/android-sdk-linux/platform-tools:/home/your_username/android-sdk-linux/tools:$PATH
On x64 systems you are required to install some 32-bit libraries so in a terminal write:
Code:
sudo apt-get install ia32-libs
3. Download ROM which you want to patch with miui patchrom, must be deodexed and rooted. For us it must be jellybean ROM for egz 4.1.2. I suggest to use CM or AOSP based roms because stock sammy roms have a lot of differences and it's not so easy to port them. After downloading your ROM base rename it to something short and easy i use stock.zip.
In home create folder i use patchrom folder in this folder create for egz stock folder and put downloaded rom to it.
4. Download from MiCode github all necessary files https://github.com/MiCode we need:
https://github.com/MiCode/patchrom_tools/archive/jellybean.zip tools
https://github.com/MiCode/patchrom_miui/archive/jellybean.zip miui
https://github.com/MiCode/patchrom_i9100/archive/jellybean.zip i9100
https://github.com/MiCode/patchrom_build/archive/jellybean.zip build
https://github.com/MiCode/patchrom_android/archive/jellybean.zip android
all zips for jellybean, why downloading zips? because for me repo don't download all files, that way is much easiest.
Unzip all files to your stock folder which you create in step 3. Rename all folders by this way patchrom_tools_jellybean becomes tools, patchrom_miui_jellybean becomes miui ...
5. In i9100 folder you can find makefile its first of configuring files which you need to copy to stock folder and edit it.
This is my makefile, you should edit using this explanations:
'local-zip-file' = Name of your original ROM zip
'local-out-zip-file' = Name for your finished MIUI rom
'local-modified-apps' = Apps that will be modified to fit in with the framework. They need to be modified because they contact with the system
'local-miui-apps' = MIUI Apps that will be integrated into the zip
'local-remove-apps' = Apps that will be removed from the original ROM
'local-pre-zip' = Refers to codeblock that should be executed before the zip is done.
'local-after-zip' = Refers to codeblock executed after the zip is completed
'local-zip-misc' = The codeblock just described at 'local-pre-zip'. It adds some Google Apps and a buid.prop
'local-test' = Another codeblock
Code:
#
# Makefile for i9100
#
PORT_BUILD=/home/jack/patchrom/build
PORT_ROOT=/home/jack/patchrom
# The original zip file, MUST be specified by each product
local-zip-file := stock.zip
# The output zip file of MIUI rom, the default is porting_miui.zip if not specified
local-out-zip-file := MIUI_i9100.zip
# the location for local-ota to save target-file
local-previous-target-dir := ~/workspace/ota_base/i9100_4.1
# All apps from original ZIP, but has smali files chanded
local-modified-apps := LogsProvider Phone MediaProvider Settings
local-modified-jars :=
# All apks from MIUI
local-miui-removed-apps := MediaProvider Stk
local-miui-modified-apps := MiuiHome Settings Phone Mms ThemeManager MiuiSystemUI
# Config density for co-developers to use the aaps with HDPI or XHDPI resource,
# Default configrations are HDPI for ics branch and XHDPI for jellybean branch
local-density := HDPI
include phoneapps.mk
# To include the local targets before and after zip the final ZIP file,
# and the local-targets should:
# (1) be defined after including porting.mk if using any global variable(see porting.mk)
# (2) the name should be leaded with local- to prevent any conflict with global targets
local-pre-zip := local-pre-zip-misc
local-after-zip:= local-put-to-phone
# The local targets after the zip file is generated, could include 'zip2sd' to
# deliver the zip file to phone, or to customize other actions
include $(PORT_BUILD)/porting.mk
# To define any local-target
updater := $(ZIP_DIR)/META-INF/com/google/android/updater-script
pre_install_data_packages := $(TMP_DIR)/pre_install_apk_pkgname.txt
local-pre-zip-misc:
cp other/spn-conf.xml $(ZIP_DIR)/system/etc/spn-conf.xml
cp other/build.prop $(ZIP_DIR)/system/build.prop
#cp stockrom/system/app/FFFFFFFF000000000000000000000001.drbin $(ZIP_DIR)/system/app
#cp -r stockrom/system/app/mcRegistry $(ZIP_DIR)/system/app
rm -rf $(ZIP_DIR)/system/csc
rm -rf $(pre_install_data_packages)
for apk in $(ZIP_DIR)/data/media/preinstall_apps/*.apk; do\
$(AAPT) d --values resources $$apk | grep 'id=127 packageCount' | sed -e "s/^.*name=//" >> $(pre_install_data_packages);\
done
more $(pre_install_data_packages) | wc -l > $(ZIP_DIR)/system/etc/enforcecopyinglibpackages.txt
more $(pre_install_data_packages) >> $(ZIP_DIR)/system/etc/enforcecopyinglibpackages.txt
out/framework2.jar : out/framework.jar
%.phone : out/%.jar
[user=279333]@ECHO[/user] push -- to --- phone
adb remount
adb push $< /system/framework
adb shell chmod 644 /system/framework/$*.jar
#adb shell stop
#adb shell start
#adb reboot
%.sign-plat : out/%
#%.sign-plat : /home/gexudong/libra.jbmiui/out/target/product/maguro/system/app/%
java -jar $(TOOL_DIR)/signapk.jar $(PORT_ROOT)/build/security/platform.x509.pem $(PORT_ROOT)/build/security/platform.pk8 $< $<.signed
[user=279333]@ECHO[/user] push -- to --- phone
adb remount
adb push $<.signed /system/app/$*
adb shell chmod 644 /system/app/$*
So, you have to change:
local-zip-file := stock.zip name of your base rom
PORT_BUILD=/home/jack/patchrom/build to your patch for build folder
PORT_ROOT=/home/jack/patchrom to your root folder
After edit in makefile and save it in patchrom/stock folder you sholud copy from patchrom/build folder these files: porting.mk and phoneapps.mk
you can edit phoneapps.mk too add or delete files which you want.
File structure must look like this:
home
-your_username
-android-sdk-linux:
(-extras
-platform-tools
-platforms
-system-images
-tools)
-patchrom:
(-android
-build
-i9100
-miui
-stock (including: stock.zip - your base rom, makefile edited by you, phoneapps.mk edited by you, porting.mk - copied from build folder)
-tools)
6. Ok, files is prepared, now we can start. Open console and type:
cd patchrom - go to patchrom folder
cd stock - go to stock folder
cd .. - go back
make workspace - this command create temp folder in stock folder, and decompile all necessary files from stock.zip and from miui patchrom, it decompile also files which you add in makefile 'local-modified-apps'
Now in temp you have 5 folders, in reject folder you can resolve any conflicts to prepare necessary files for miui rom.
7. After fixing problems with smali type in console
make firstpatch
this command will apply all rej changes and miui patch for your decompiled files.
8. In console type:
Code:
source build/envsetup.sh
cd stock
make zipfile
Thats all.
If you have problems google it
Don't ask me for anything, use your brain!
Thank you for the information!
I think, you should add a couple of words to help linux newbies.
1. To set $PATH variable you need to edit "bashrc" file.
open terminal, run following command
Code:
gedit ~/.bashrc
gedit is an editor in Ubuntu, you can use any other editor
add to the begining
Code:
export PATH=/home/your_username/android-sdk-linux/platform-tools:/home/your_username/android-sdk-linux/tools:$PATH
save file
reboot to activate changes
test - open terminal, and execute "echo $PATH"
2. You need to generate keys to sign your rom.
http://android-dls.com/wiki/index.php?title=Generating_Keys
can I use this guide to build a miui patch rom for my galaxy nexus toro? which rom do you guys suggest me to use?
Hi,
I just need to ask a few things.
1. How do we know which local apps need to be modified. and which miui apps need to be modified.? I mean is there a pre-defined list or its hit n trial??
I can follow the instructions and run the scripts, but i need to make sure how do we select the criteria for above files. Rest i'll try to figure out myself.
Regards
Yasir
I think a couple of mistakes there are, its make fullota where you have written make firstpatch because make firstpatch will create the temp poster where the 5 folders exist. Once you've fixed the rejects, that's when you make fullota. Also, we don't need PORT_BUILD and PORT_ROOT exports.
MTK Mediatek MIUI
will this work for MTK phones? if yes is it the same process??
rnovino said:
will this work for MTK phones? if yes is it the same process??
Click to expand...
Click to collapse
maybe and you can't use then the i9100 you need to find a phone with compatible hardware or just the phone
Thanks for the guide.
Going to try this out in a few hours, installing Linux in vmware workstation 10 currently
Sent from my GT-I9100 using Tapatalk 4
Need help..
i want to port miui to my mtk phone what are the required files for mtk.......
MTK 6575 - acer z2 JB4.1.1 dual sim
which branch do i used to patching MTK6575 JB4.1.1, JB4.2-MTK or JB4.1-non MTK?
[edit]
basicly as i know, that we have doing is:
- merged Miui framework(smali) to stock framework (smali), right?
- copy lib/etc/xbin ...
- edit bootclasspath if need.
- edit updater-script.
- repack all.
alfan.y said:
which branch do i used to patching MTK6575 JB4.1.1, JB4.2-MTK or JB4.1-non MTK?
[edit]
basicly as i know, that we have doing is:
- merged Miui framework(smali) to stock framework (smali), right?
- copy lib/etc/xbin ...
- edit bootclasspath if need.
- edit updater-script.
- repack all.
Click to expand...
Click to collapse
These pages are a great help. There are many others but start here.
Porting miui to other devices http://en.miui.com/thread-4569-1-1.html
Porting miui cm10.1 based devices http://en.miui.com/thread-6395-1-1.html
Porting miui patchrom guide http://en.miui.com/thread-9630-1-1.html
Q&A for [MOD]Stock SystemUI and Stock Firmware DXMD1[DEODEXED] for GT-S6102
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [MOD]Stock SystemUI and Stock Firmware DXMD1[DEODEXED] for GT-S6102. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
De-odexed!!!
Well, here again, hmm, it looks like the main problem with my swipe to remove is that I don't have a fully deodexed ROM(Xduos V3) which is why it's not working. sigh, and I was preparing myself to go for the hard way.
Guess my questions are answered here as for now.
marcussmith2626
Click to expand...
Click to collapse
will meet again.
New question
Can I save the little space I have in internal storage with a deodexed rom? deodexed rom is going to solve my issues with the rom's UI but I am concerned as to what effect it will have on my sgy performance?
billysam said:
Well, here again, hmm, it looks like the main problem with my swipe to remove is that I don't have a fully deodexed ROM(Xduos V3) which is why it's not working. sigh, and I was preparing myself to go for the hard way.
Guess my questions are answered here as for now. will meet again.
New question
Can I save the little space I have in internal storage with a deodexed rom? deodexed rom is going to solve my issues with the rom's UI but I am concerned as to what effect it will have on my sgy performance?
Click to expand...
Click to collapse
If the rom is odex you will see .odex files in system/app and framework
To deodex follow these steps
Requirements
Pc
Android kitchen
Cygwin
Rooted phone with Busybox & terminal emulator
Winrar
Notepad++ (different from the windows notepad)
Alot of patience & a little knowledge
Please note I'm writing this from memory - some steps may vary
First root your phone & install Busybox (open app & click install) from the playstore
Also install terminal emulator
https://play.google.com/store/apps/details?id=stericson.busybox
https://play.google.com/store/apps/details?id=jackpal.androidterm
Set your screen timeout to 30mins
Open terminal emulator
Type the following (a new line represent push enter after the line before)
Su
tar -c system/* >> sdcard/system.tar
Note it may take around 5mins to complete - You will know it's done when the prompt cursor returns
This will copy your phones system folder to the root of your site
card and call it system.tar
Copy this tar file to your pc
Next head to this thread
http://forum.xda-developers.com/showthread.php?t=2195858
Download and install Cygwin and Android kitchen
There is a YouTube video which explains how on the thread so watch it
This is the part I can't remember exactly from memory
You need to setup a working folder - I can't
remember if you place the tar file in the rom folder in the kitchen directory or you unzip it & copy it to a working folder - that thread will say
Start Cygwin as administrator (right click on icon & run as administrator) if you get a load of errors turn off your antivirus
Navigate to your kitchen folder (you can bring up a list of folders by typing ls and type cd to change directory
Type ./menu
Kitchen will start
You have the option to create a working folder which will look in the rom folder - if a tar file is acceptable it will extract your tar into a working folder - can't remember if that's how you do it
Next goto advance (or extra options can't remember what it says)
Goto deodex
You need to change the api level so it matches your Android version
Now you are finally ready to deodex
Deodex both folders
Once done build the rom (lazy mode options should be fine Think it signs rom create scripts & so on)
Once it's built collect your rom zip
Now download any custom stock rom - maybe hyperion 9 for 5360
Open your rom zip with winrar
Delete boot.img if present
Goto meta-inf folder and I think it's in com/google/andoid
Delete the update binary and replace with the one from hyperion9
Next open extract the updater script from both roms from the same folder the binary way in
Open them both in notepade++
Replace everything in your script above where the symlinks start with what is written in the hyperion9 one
Save & copy this script back to your rom zip meta in folder replacing the one that is there
Copy zip to sd card
Go into Cwm
Create a nandroid backup
Format system data cache
Mount system data cache
Flash your rom zip
Error codes
Status 0 wrong update binary
Status 6 error with updater script
Hopefully there will be no errors and it will flash and when you restart you will have a fresh deodexed rom
You can go into Cwm and advance restore data only
This should restore your contacts sms and app data
For extra storage create a 2nd ext partition on your site card in Cwm (note that this will format your ad card so copy it's contents to a pc then copy back once done)
Once you have a 2nd ext partition you can download link2sd from the playstore and link apps to sd card - you can also use the app to uninstall bloatware from the system
Note you will need to use a kernel that supports ext and try ext4 first from the link2sd menu that will pop up & work your way back up if that fails
I don't normally post such a long explanation but I'm feeling generous - anything else please research yourself
Very Much Appreciated
marcussmith2626 said:
If the rom is odex you will see .odex files in system/app and framework
To deodex follow these steps
Requirements
Pc
Android kitchen
Cygwin
Rooted phone with Busybox & terminal emulator
Winrar
Notepad++ (different from the windows notepad)
Alot of patience & a little knowledge
Please note I'm writing this from memory - some steps may vary
First root your phone & install Busybox (open app & click install) from the playstore
Also install terminal emulator
https://play.google.com/store/apps/details?id=stericson.busybox
https://play.google.com/store/apps/details?id=jackpal.androidterm
Set your screen timeout to 30mins
Open terminal emulator
Type the following (a new line represent push enter after the line before)
Su
tar -c system/* >> sdcard/system.tar
Note it may take around 5mins to complete - You will know it's done when the prompt cursor returns
This will copy your phones system folder to the root of your site
card and call it system.tar
Copy this tar file to your pc
Next head to this thread
http://forum.xda-developers.com/showthread.php?t=2195858
Download and install Cygwin and Android kitchen
There is a YouTube video which explains how on the thread so watch it
This is the part I can't remember exactly from memory
You need to setup a working folder - I can't
remember if you place the tar file in the rom folder in the kitchen directory or you unzip it & copy it to a working folder - that thread will say
Start Cygwin as administrator (right click on icon & run as administrator) if you get a load of errors turn off your antivirus
Navigate to your kitchen folder (you can bring up a list of folders by typing ls and type cd to change directory
Type ./menu
Kitchen will start
You have the option to create a working folder which will look in the rom folder - if a tar file is acceptable it will extract your tar into a working folder - can't remember if that's how you do it
Next goto advance (or extra options can't remember what it says)
Goto deodex
You need to change the api level so it matches your Android version
Now you are finally ready to deodex
Deodex both folders
Once done build the rom (lazy mode options should be fine Think it signs rom create scripts & so on)
Once it's built collect your rom zip
Now download any custom stock rom - maybe hyperion 9 for 5360
Open your rom zip with winrar
Delete boot.img if present
Goto meta-inf folder and I think it's in com/google/andoid
Delete the update binary and replace with the one from hyperion9
Next open extract the updater script from both roms from the same folder the binary way in
Open them both in notepade++
Replace everything in your script above where the symlinks start with what is written in the hyperion9 one
Save & copy this script back to your rom zip meta in folder replacing the one that is there
Copy zip to sd card
Go into Cwm
Create a nandroid backup
Format system data cache
Mount system data cache
Flash your rom zip
Error codes
Status 0 wrong update binary
Status 6 error with updater script
Hopefully there will be no errors and it will flash and when you restart you will have a fresh deodexed rom
You can go into Cwm and advance restore data only
This should restore your contacts sms and app data
For extra storage create a 2nd ext partition on your site card in Cwm (note that this will format your ad card so copy it's contents to a pc then copy back once done)
Once you have a 2nd ext partition you can download link2sd from the playstore and link apps to sd card - you can also use the app to uninstall bloatware from the system
Note you will need to use a kernel that supports ext and try ext4 first from the link2sd menu that will pop up & work your way back up if that fails
I don't normally post such a long explanation but I'm feeling generous - anything else please research yourself
Click to expand...
Click to collapse
Well, thank you for your valuable time and efforts in getting me involved to the basics. your generosity is very much appreciated, I am on my path to research it all myself.