JiT installation without OVERWRITING build.prop and manual edit.
Build.prop modification
replace :
dalvik.vm.heapsize=32m
add :
dalvik.vm.execution-mode=int:jit
backup build.prop,bin and lib files for uninstallation,so it will not stuck if uninstalled
make backup with xRecovery before making any change.
read instruction.txt for more info.
REQUIRED :
- busybox installed
- adb or terminal emulator
- xRecovery to make full backup
puppet13th said:
JiT installation without OVERWRITING build.prop and manual edit.
Build.prop modification
replace :
dalvik.vm.heapsize=32m
add :
dalvik.vm.execution-mode=int:jit
backup build.prop,bin and lib files for uninstallation,so it will not stuck if uninstalled
make backup with xRecovery before making any change.
read instruction.txt for more info.
REQUIRED :
- busybox installed
- adb or terminal emulator
- xRecovery to make full backup
Click to expand...
Click to collapse
keknya dlo udah ada yg posting gan,,, tapi nice inpoh ..
This probably belongs in the developer section, but I don't have permission to post there yet)
This work is very preliminary. It isn't really anything more than a starting point right now. It DOES NOT yet provide a faithful representation of a custom ROM in the emulator.
Current status:
emulator running 2.6.29 kernel with a combination of frankenstein of the emulator and devoid-franco system image.
I've been working to get a custom ROM working in the Android SDK emulator. There are several reasons for this, but in the end, it makes it a lot easier to test out different tweaks to get the ROM working as I'd like (I need some functions provided on the P509 ROM that aren't provided on any custom ROMS, and reinstalling the APKs isn't sufficient). I spent a lot of time looking for a thread about this, but nothing I could find discusses the specifics of working with a P500 based device
Things I've learned:
a) you need a kernel specifically compiled for the emulator, and the ramdisk image needs to be built to work with an emulator. For the moment i am using the SDK kernel (2.6.29) and ramdisk image to get going
b) the p509 libraries aren't compatible with the emulator, I needed to copy the libraries from the supplied emulator image
Here are some notes I took. I'll try to flush this out more as I make further progress:
Tools you will need:
Android SDK and 2.2 platform files (android-8)
unyaffs
mkfs.yaffs2.x86
a copy of the ROM image to install (devoid.franco.v5 in my case)
before beginning you should build a stock 2.2 emulator env to ensure everything is working (from sdk/tools run):
android list targets
find the id for 2.2 (was '4' for me)
android create avd -n test-froyo -t 4
(I used all defaults, except I set the RAM to 512MB and screen to HVGA)
emulator -avd test-froyo -show-kernel
(this should eventually bring up a running froyo)
you'll need to know where the avd lives. In linux, it should be in ~/.android/avd/test-froyo
I'm working on linux, but this should work in Windows if you can find a compiled version of mkfs.yaffs2 for windows (I've seen a compiled unyaffs version out there)
1) unzip the rom image. it should create a system/ directory.
We should execute the updater-script here, but we'll take a short-cut:
chmod -R 655 system/
2) uncompress the platfrom system image:
in a new dir:
unyaffs <sdk path>/platforms/android-8/images/system.img
3) copy all files from system/ in step-2 to system/ in step-1
we should really need to do this, it is probably sufficient to run the updater-script and then copy the framework/, lib/ and a couple qemu files, but this is just to get things going.
4) make dbus.conf readable:
chmod 644 system/etc/dbus.conf
5) remove system/app/LGSetupWizard.apk
This app relies on custom classes in the firmware that aren't present in the emulator base system. I'm still trying to build a custom firmware.jar that has both.
6) build a new system.img
mkfs.yaffs2.x86 system system.img
7) copy the system image to your avd dir:
cp system.img ~/.android/avd/test-froyo
If everything has gone well, you can now startup the emulator and boot into franco's rom:
emulator -avd test-froyo -show-kernel
Because we copied too much stuff from the default system.img, we've lost his themes and mst of his tweaks, so it isn't really a faithful representation of the ROM at all, but we've cleared the 1st milestone of being able to boot up.
I also booted a stock P509 kernel this way with a few changes:
a) I used nandroid to get the system image, and then unyaffs2 to extract it)
b) I removed all odex files:
find system -name "*.odex" | xargs rm
Again, this isn't really a custom ROM, it is actually the emulator rom with additional apps and customizations. The goal is to get to as close as possible to running a true custom ROM
A few other notes:
the following framework files can be preserved from the custom ROM (no need to overwrite):
Code:
am.jari : ok
android.policy.jar : not ok
android.test.runner.jar : ok
bmgr.jar : ok
core.jar : ok
ext.jar : ok
framework.jar : not ok
framework-res.apk : not ok
framework-tests.jar : ok
ime.jar : ok
input.jar : ok
javax.obex.jar : ok
monkey.jar : ok
pm.jar : ok
services.jar : not ok
svc.jar : ok
framework.jar is the most important of the 'not-ok' ones as far as I can tell, and is missing several classes. I am currently working to build a services.jar that is a merge of the P500 and emulator classes.
Installing the p500 framework,.jar requires many files from system/lib, but once all dependencies are solved, you eventually end up with a segfault. I've been unable to debug that, and am not sure I want to. The goal is to get a running dalvik VM with all classes needed to run P500 apps.
First blood!!!
I tried to install the dual touch mod on my X10 Mini.
I edited the hw_config.sh file and added this command on the beginning of the file
# dx: our modded touchscreen driver
insmod /system/lib/modules/x8gesture.ko
insmod system/lib/modules/cy8ctma300_ser.ko
Copied files x8gesture.ko and cy8ctma300_ser.ko to /system/lib/modules
and copied android.hardware.touchscreen.multitouch to permissions folder.
I also edited the build.prop file using build editor.
I have already mounted system ( Mount System RW ) as writable using app System RW/RO.
Kernel : nAa 2.6.32.62
ROM : Custom ROM PureSlim R4
Baseband Version : M76XX-TSNCJOLYM-53404015
Thanks in advance
This script removes unnecessary files and adds the file
Script deletes files...
Code:
system/app/Apollo.apk");
system/app/Browser.apk");
system/app/Calculator.apk");
system/app/Calendar.apk");
system/app/CMWallpapers.apk");
system/app/Email.apk");
system/app/LatinIME.apk");
system/app/Term.apk");
system/app/VideoEditor.apk");
system/app/CMFileManager.apk");
system/app/Exchange2.apk");
system/app/Galaxy4.apk");
system/app/Gallery2.apk");
system/app/NoiseField.apk");
system/app/LiveWallpapersPicker.apk");
system/app/MagicSmokeWallpapers.apk");
system/app/PhaseBeam.apk");
system/app/VoicePlus.apk");
delete_recursive ("/system/media/audio/notifications");
delete_recursive ("/system/media/audio/ringtones");
system/media/audio/notifications
system/media/audio/ringtones
Leaves only one ringtone and notification
Sets the modified host file patched program AdFree
With this script you can free up about 100 mb
Installation: Flash file via recovery
Download v1.0 :http://d-h.st/6ew
Download v1.1 : http://d-h.st/IQR
For version 22.05.14 CM 11 use version v1.0 which does not remove the standard live wallpaper, without them off point wallpaper
Q&A for [GUIDE] [PORT] [ROM] All About Mediatek ROM Porting
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
after unpack my boot.img with "MTK FirmwareAdapter Tool" i have in the folder:
1- rmdisk (folder)
2- kernel (file)
3- kernel_header (file)
4- ram_disk (file)
5- ram_disk.gz
6- ram_header (file)
Where is the zimage? Where is boot.img-ramdisk folder? How i doing:
"* Now Go back to the Rom folder and Take the boot.img and decompile it with any bootimg-unpack tool!
* Now delete the zimage and rename boot.img-ramdisk to PORT-Ramdisk
* Now Do the Same for Stock boot.img and open the folder named PORT-ramdisk and copy all the fil PORT-
ramdisk to boot.img-ramdisk of your Stock boot.img
* Now Go to boot.img-ramdisk and open init.rc" ?????????
thx
Click to expand...
Click to collapse
Port mtk6592 to mtk6589t
hi i try to port mtk6592 to mtk6589t and not working, you can help me?
Thanks
iphone 6 clone dead
hi i formate iphon6 clone using sp flash tool,now bootloader menu not opening even not charging. what can i do, please advice me.
sorry, i am new here.
I really doubt if this tutorial will work on Tablet Advan T5C.
I really want to Port MIUI Rom to this tablet. However, the developer is very rare for this vendor "Advan" so it's hard to get a Custom ROM.
What ROM of Tablet Vendor which can be ported to this spec?
8 "Inch IPS
MT6582
Mali 400
8 GB ROM
1 GB of RAM
Port MT6589 to MT6577
Thanks for the tutorial on first page.
Im alred try first metod but cellphone restart on CWM scren.
Now a gonna try secound metod.
Useful Post....
Tnx For Share.
teopro said:
after unpack my boot.img with "MTK FirmwareAdapter Tool" i have in the folder:
1- rmdisk (folder)
2- kernel (file)
3- kernel_header (file)
4- ram_disk (file)
5- ram_disk.gz
6- ram_header (file)
Where is the zimage? Where is boot.img-ramdisk folder? How i doing:
"* Now Go back to the Rom folder and Take the boot.img and decompile it with any bootimg-unpack tool!
* Now delete the zimage and rename boot.img-ramdisk to PORT-Ramdisk
* Now Do the Same for Stock boot.img and open the folder named PORT-ramdisk and copy all the fil PORT-ramdisk to boot.img-ramdisk of your Stock boot.img
* Now Go to boot.img-ramdisk and open init.rc" ?????????
thx
Click to expand...
Click to collapse
The zImage is the kernel file. boot.img-ramdisk is the main folder containing the zImage(kernel) and ramdisk, just you need rename the decompiled port boot.img to PORT-ramdisk, and your stock boot.img not rename folder.
I just want to ask how to fix this problem , I ported MT6589 to my MT6577 device, Seems there's no problem in flashing ROM but when its time to boot, it just hangs on the boot logo, it's not even trying to load bootanimation but rather it only flashes a white screen then it reboot to my recovery. Seems like I do something wrong?
My device is mp a818g duo
Kernel:3.4.0
Chipset: MT6577
Hope I receive help
---------- Post added at 03:57 PM ---------- Previous post was at 03:50 PM ----------
teopro said:
after unpack my boot.img with "MTK FirmwareAdapter Tool" i have in the folder:
1- rmdisk (folder)
2- kernel (file)
3- kernel_header (file)
4- ram_disk (file)
5- ram_disk.gz
6- ram_header (file)
Where is the zimage? Where is boot.img-ramdisk folder? How i doing:
"* Now Go back to the Rom folder and Take the boot.img and decompile it with any bootimg-unpack tool!
* Now delete the zimage and rename boot.img-ramdisk to PORT-Ramdisk
* Now Do the Same for Stock boot.img and open the folder named PORT-ramdisk and copy all the fil PORT-
ramdisk to boot.img-ramdisk of your Stock boot.img
* Now Go to boot.img-ramdisk and open init.rc" ?????????
thx
Click to expand...
Click to collapse
When you use android kitchen to decompile your boot.IMG then your kernel will named zimage, but when you use other unpack/repack tool for your boot.IMG, the equivalent of zimage in your decompiled boot.img is the files kernel and kernel header.
Click to expand...
Click to collapse
Xtreme Ornob Thanks
Thanks a lot for this extreame guide about Mediatek rom Porting
what is the tool download link, i am new
When I port by this guide I have problems, from 6582 to 6582
I have logo and then nothing when phone reboots after installing rom
I tried all things
changed kernel from stok to port rom and changed the lines in init.rc in stok rom and have the same result
Can some one help me?
iceman1966 said:
decompile the boot.img rom port and the boot.img of your stock rom. Replace the ramdisk rom port with ramdisk the stock rom. recompile and install the new boot.img.
Click to expand...
Click to collapse
I made that you write to me but situation is the same.
logo and nothing else
How to take the logcat when the phone goes to reboot after flashing the rom ?
I want to see what I made wrong?
query regarding porting from different versions
Hello xda.........i want to know the information about how to port the jellybean rom with kitkat to get kitkat in my phone.............
please explain me how to port to higher versions from our lower version of roms.............
Boot.img
im porting from a device to a device with different SoC.
i have followed instructions on this thread:
http://forum.xda-developers.com/showthread.php?t=2701283
i have done the steps and reached to the step where it says to unpack boot.img. i have unpacked the boot.img in both port and stock only to find the boot.img-ramdisk empty... what should i do now?
I want to know all about Porting
Hi sir Good day.
I want to know how to port a HTC one M8 ROM MTK6572 Chipset. Beacase I came from Samsung Dev. S5830 Galaxy Ace and its hard to understand how to flash ROM's of MTK's Devices. Please Reply Thanks in advance
camera degrades performance
nice tutor, i have sucessfully ported Lewa OS 5.0 rom from Lenovo S920 to my device HDC Galaxy S4 GT-I9500 Clone.
-MTK6589 Quad Core 1.2GHz
-2GB RAM (fake) 1GB RAM (real), 4GB ROM
-5.0inch HD IPS Screen
Display resulotion: 1280*720 pixel display, 320 dpi
GPU : PowerVR SGX 544MP
Build ID : JDQ39.I9500ZSUAMDF
Hardware : UNIVERSAL5410(exynos5) fake, MT6589
Model : GT-I9500
Build number : ALPS.JB2.MP.V1.26
Build date UTC : 20130904-125830
Android v : 4.2.2
Baseband v : MOLY.WR8.W1248.MD.WG.MP.V23.2013/07/25 04:17
Kernel v : 3.4.5 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC))#1 SMP Wed Sep 4 20.55.23 CST 2013
LCD Driver IC : 1-nt35590_hd720_dsi_cmd_truly
all work perfectly but the problem is camera quality really degrades when using Lewa OS. with stock rom my back camera 13MP, when i used custom rom Lewa my back camera only 2MP. i try to instal lenovo super camera, but camera resolution still same only 2MP.
how can i fix it please help me.....!
can you help me I am trying to port the ROM from mt6592 to mt6582 and have problems.
Do you have guide how to make a port from mt6592 to mt6582?
just wanna ask if im doing right,thanks in advance
I am porting custom rom MT6572 to my device MT6582
I decompile boot.img(MT6572) and boot.img(MT6582"stock")
I copy all files from ramdisk(MT6572) and replace it to ramdisk(MT6582" stock)
I edit init.rc and edit what i need to edit and do it like this
#Create Chip Property
on early_property:ro.hardware=mt6572
setprop ro.mtk.hardware mt6582
on early_property:ro.hardware=mt6589
setprop ro.mtk.hardware mt6582
I add and edit those line on the init.rc, am I doing right boss?
Good day Sir,just wanna ask if i am doing right.
I am porting custom rom MT6572 to my device MT6582
I decompile boot.img(MT6572) and boot.img(MT6582"stock")
I copy all files from ramdisk(MT6572) and replace it to ramdisk(MT6582" stock)
I edit init.rc and edit what i need to edit and do it like this
#Create Chip Property
on early_property:ro.hardware=mt6572
setprop ro.mtk.hardware mt6582
on early_property:ro.hardware=mt6589
setprop ro.mtk.hardware mt6582
I add and edit those line on the init.rc, am I doing right boss?