I´m tryng to port some roms to THL T11 (mtk6592). I have allready sucess with two but allways the same problem: touch keys (settings, home and back) and physical keys (power and volume) don´t work.
I have allready replace Generic.kl and mtk-kpd.kl from base to port but don´t fix my problem.
Wich more files i have to replace?
Can anyone help me?
Thanks
Hello, that method as followed for porting the mtk6592 rom since I only find for 6589 and previous.
carcaca said:
I´m tryng to port some roms to THL T11 (mtk6592). I have allready sucess with two but allways the same problem: touch keys (settings, home and back) and physical keys (power and volume) don´t work.
I have allready replace Generic.kl and mtk-kpd.kl from base to port but don´t fix my problem.
Wich more files i have to replace?
Can anyone help me?
Thanks
Click to expand...
Click to collapse
I may be very late but still replace lib>hw folder from stock to port delete the port lib>hw folder before copying from stock
carcaca said:
I´m tryng to port some roms to THL T11 (mtk6592). I have allready sucess with two but allways the same problem: touch keys (settings, home and back) and physical keys (power and volume) don´t work.
I have allready replace Generic.kl and mtk-kpd.kl from base to port but don´t fix my problem.
Wich more files i have to replace?
Can anyone help me?
Thanks
Click to expand...
Click to collapse
Hi,was wondering if you could share how you managed to port roms to mtk6592..Tried using some tutorials here but still didn't boot..Thanks
Aeonia said:
Hi,was wondering if you could share how you managed to port roms to mtk6592..Tried using some tutorials here but still didn't boot..Thanks
Click to expand...
Click to collapse
Hi, i´m no longer trying port because i'm theming official rom.
I tried to port some and the method i used is:
You need to port same version of android like 4.2 to 4.2 or 4.4 to 4.4.
Use the boot.image of your phone or decompile the boot.image of your rom and the boot.image of the rom you wanted and combine base’s zImage and port’s ramdisk and recompile to create new boot.img.
I normally replaced System/Etc/firmware from base to port.
Replace all the camera libs from base to rom.
Sometimes i have to replace audio libs if don't have sound.
Of course you need to edit buil.prop and i allways erase line in updater.script that contains install recovery.
If some thing don't work you need to try to replace some libs or else.
With this method i ported some roms and sometimes everything is allright ans sometimes i had some problems like the one i posted before but in 80% of the cases the rom boot.
The only thing that never works is gesture in locker screen.
Try this http://forum.xda-developers.com/showthread.php?t=2701283 and good luck.
carcaca said:
Use the boot.image of your phone or decompile the boot.image of your rom and the boot.image of the rom you wanted and combine base’s zImage and port’s ramdisk and recompile to create new boot.img.
Click to expand...
Click to collapse
Can't seem to find the zImage...all i have is
the rmdisk folder contains may files including the init.rc
Use android kitchen to decompile original boot.image and you get a new folder in kitchen called bootimg_xxxx_xxxx containing a folder named boot.img-ramdisk and a file named zImage.
Save the files in other folder outside android kitchen.
Erase folder bootimg_xxxx_xxxx in kitchen and replace original boot.image with port boot.image in working folder.
Now decompile again boot.image.
Now combine base’s zImage and port’s ramdisk and recompile to create new boot.img.
Try this.
carcaca said:
I´m tryng to port some roms to THL T11 (mtk6592). I have allready sucess with two but allways the same problem: touch keys (settings, home and back) and physical keys (power and volume) don´t work.
I have allready replace Generic.kl and mtk-kpd.kl from base to port but don´t fix my problem.
Wich more files i have to replace?
Can anyone help me?
Thanks
Click to expand...
Click to collapse
Did you solve the problem? How?
Related
After many many tweaking and cooking ROMs for WinMo I want to do same with Android. The reason I cooked for WinMo was speed, but since it is not an issue with mine Desire(but it can be better I want to customize ROM a little bit, so remove some stuff and later maybe add few apps. If this want be a problem I will try to tweak too.
However in WinMo I have always have served kitchen, I just tweaked removed and add few things and job done but here there are no kitchens..yet(I hope somebody will sooner or later post it
So is there anybody who can help to set up kitchen so that I can cook few roms for me and this community?
So if I understanded correctly I need following to start cooking
android sdk
java jdk
signing tool
stock ROM
I have downloaded them all, extracted SDK in D:\HTC Desire\Android SDK, installed Java JDK in C:\Program Files (x86)\Java and I don't know what to do next?
Extract ROM, where(?), extract system.img which is in rom.zip if yes how and where?
Thanks for your help
Benko, you can extract the ROM anywhere you want. But, you don't want images. You should look at Pauls rootedupdate.zip as a starting point. Unzip that.
eViL D: said:
Benko, you can extract the ROM anywhere you want. But, you don't want images. You should look at Pauls rootedupdate.zip as a starting point. Unzip that.
Click to expand...
Click to collapse
Ok extracted that rootedupdate.zip and found a lot of apks and obexes so after I delete those files that I dont want how to put that all back together to file that is flashable?
You'll have to resign the zip after removing stuff, otherwise it will give verification errors when trying to flash.
You need to remove the current certificates from the file, there are three files in the META-INF folder - delete those, but keep the update script (the COM folder inside), it's needed for flashing.
I use this little thingy for signatures: http://android-dls.com/wiki/index.php?title=Generating_Keys
Hope this helps!
PS-beware of any dependencies between the various apk's and any framework modding that might be needed, otherwise you'll get more fc's than you can carry; I know I did
PS2- if you want a served kitchen, you'll find one over at Modaco, for a CyanogenMod port (a link is posted in a thread here) - see if that suits you're needs.
PS3- check out the Chef Central sticky here, too - it should be easier to get quicker/more accurate info from the seasoned cooks there
benko286 said:
Ok extracted that rootedupdate.zip and found a lot of apks and obexes so after I delete those files that I dont want how to put that all back together to file that is flashable?
Click to expand...
Click to collapse
Rezip the folders: meta, system & boot.img.
Then resign them. You can then transfer it to sd and try to flash. If it doesn't boot, then you have to troubleshoot.
May I know that how to change layout of the home screen?
e.g. HTC sense has news/mail widget where first installed and booted.
Where can I change these settings?
Also , I want to know if I made my own rom, and updated to my desire.
If it doesn't boot or anything, can I updated the rootedupdate.zip from Paul to get the desire back working?
Thanks
eViL D: said:
Rezip the folders: meta, system & boot.img.
Then resign them. You can then transfer it to sd and try to flash. If it doesn't boot, then you have to troubleshoot.
Click to expand...
Click to collapse
kevin612 said:
May I know that how to change layout of the home screen?
e.g. HTC sense has news/mail widget where first installed and booted.
Where can I change these settings?
Also , I want to know if I made my own rom, and updated to my desire.
If it doesn't boot or anything, can I updated the rootedupdate.zip from Paul to get the desire back working?
Thanks
Click to expand...
Click to collapse
Ok zipped those folders(META-INF, system, boot.img) in rootedupdate.zip, used autosign.bat to manually sign that .zip and now it should be flashable?
@Kevin-yes if it is not bootable you can flash Pauls rom again
benko286 said:
Ok zipped those folders(META-INF, system, boot.img) in rootedupdate.zip, used autosign.bat to manually sign that .zip and now it should be flashable?
@Kevin-yes if it is not bootable you can flash Pauls rom again
Click to expand...
Click to collapse
Hopefully. After a few hundred times you'll get the hang of it. ;P
If it boot loops, it won't boot. Try again. Always remember what you're adding and subtracting. Maybe start out with only a couple things.
eViL D: said:
Hopefully. After a few hundred times you'll get the hang of it. ;P
Click to expand...
Click to collapse
OK Since I returned my device to my store because of warranty can you try that ROM, I will upload it for you ?
benko286 said:
OK Since I returned my device to my store because of warranty can you try that ROM, I will upload it for you ?
Click to expand...
Click to collapse
Sure, why did you return it?
Uploading it now
Some very very bad battery leaking...80% in one night and sync was off!
Thank you so much eViL D: and everybody else for help
Ok I also want to create my own rom but I don't know how to sign it..
Any help would be most appreciated.
ROM Link here
http://www.mediafire.com/?zt4ymz42jzj
I hope it works
So for now I even don't need Android SDK?
I downloaded the rom kitchen from Chef Central...Does the rom need to be sign after I built them out in Linux?
Also there are some folders I not understand yet....
Inside system folder - customize, etc, framework, usr and xbin I dont understand yet.
Cause looking at eVil D:'s rom and paul's rom is very different in those. And even paul's rom doesnt have customize folder.
Would like to understand all and see if I can make a rom out.
Thanks
Anybody tried my ROM ?
benko286 said:
Anybody tried my ROM ?
Click to expand...
Click to collapse
Got corrupted DL. Will have to try again.
kevin612 said:
I downloaded the rom kitchen from Chef Central...Does the rom need to be sign after I built them out in Linux?
Also there are some folders I not understand yet....
Inside system folder - customize, etc, framework, usr and xbin I dont understand yet.
Cause looking at eVil D:'s rom and paul's rom is very different in those. And even paul's rom doesnt have customize folder.
Would like to understand all and see if I can make a rom out.
Thanks
Click to expand...
Click to collapse
the kitchen signs the rom automatically. run the menu from terminal ( using linux) and u will see all the what the kitchen is doing.
do not try to compare custom roms ... they are different. some have extrafiles & folders depending on their customisations.
best thing is to compare with an original rom for the desire. and u see what has been added to get X and Y. involves a lot of trials and errors.
eViL D: said:
Got corrupted DL. Will have to try again.
Click to expand...
Click to collapse
I will try downloading too, if it wont work I will reupload it
I know that this can sound wierd but can anybody of you upload his kitchen?
Thank you all for help!
EDIT: File is corrupted, uploading again!
Reuploaded and tested, RAR file is ok
http://www.mediafire.com/?w5wommomzmk
Please somebody try ROM
Thanks
benko286 said:
Reuploaded and tested, RAR file is ok
http://www.mediafire.com/?w5wommomzmk
Please somebody try ROM
Thanks
Click to expand...
Click to collapse
Anybody tried ROM ?
P.S anybody has link to CyanogenMod port, anybody uses that kitchen?
Hi ppl, i'am from Portugal so sorry for my poor English, i'am a cooker for the Orange Boston (Aka Apanda A60, GigaByte Codefish, Wellcom etc etc), the issue it's this, i'am trying to change some thing's in the hidden partition, ok i have extracted the original hidden.img from the original ROM Apanda2.1Final.nb0 and with unyaffs in this point i have in that folder a custom.iso (this will be Virtual CD-ROM that will be mounted in windows) a settings.xml and boot animations, ok i change the boot png's and some settings in xml. now i repack the folder with mkyaffsimg in linux, ok now i flash with fastboot, now the problem is the Virtual CD-ROM its not mounted so the hidden it's not being linked to custom.iso the strange it's i had not changed anything in custom.iso.
Another issue with this terminal its (i think) i cant use mkyaffsimg in linux to creat a hidden.img so i run mkyaffsimg inside the phone by the adb shell with mkyaffs2image /hidden /sdcard/hidden.img ever with this method the result it's the same.
thanks in advance
+1 for an expert advice please.
And, if possible, anyone knows how do i sign the update.zip or where to find the keystore for the rom signing? How do you guys found the key for the other devices here @XDA?
Thank you in advance.
Regards from Portugal.
they find the key i think by reverse enginering or the HTC can be signed with a custom key or an developer Key, our phone it's stupid because with the google's developers key we can't sign
Anyone here @xda can please enlighten us about the questions above?
Ty in advance
Bump, anyone?
Regards from Portugal
Same problem here, i can't rebuild the hidden partition after modding the content. On pc or on phone, i can't get successfully to rebuild the hidden partition.
Sent from my NX-A890 using XDA App
CANCELLED! GOT A NEW PHONE
Tried so many methods , non worked , I'd keep trying until one works , then I could port hTC Aria's CM10 to hTC HD MINI and redo all this again so that we can have 4.1 on our devices. Till then , I'd love it if munjeni or schlund helped me with the process , because it seems that the kernel extracted from boot.img needs modification , and that every OS needs its own initrd , I hope someone can help.
Update:
I found the required file's details , I have the ramdisk , I have the system.ext2 , what I'm missing is the required kernel , 3.0.1 , I just need a download link to that kernel, can't seem to find any.
Hi,
So I recently got into Android Development and so far , everything is good.
What I'm doing is using munjeni's CM9 ROM as a base for me to get the boot.img and the files in the folder /system/.
I tried to use iPlasm's CM9 ROM but I got some extraction problems , which I'll look into later.
I'm also using the initrd found in Shlund's posts , and the original HD Photon (Froyo 2.2).
I compared the two initrds and found out that the Froyo one was smoother and had lots of unnecessary stuff and that the CM7 one is better , but it may freeze , so I'm going to test both for maximum results.
To-Do:-Ability to Extract zImage from boot.img Done
-Extract system files Done
-Put System Files into system.ext2 Done
-Use shlund's both kernels and see which one works.
-Create a system.ext2
-Extend Data.ext2's size to allow higher storage on higher SD cards.
If you are willing to help on this project...then please help me with these:
I need an empty system.ext2 in ext3 format (so I can put the system files inside).
Or I need someone to be able to empty the system.ext2 that I have which I got from the Froyo 2.2.
Problems :Currently I'm facing these problems that may get fixed later:
Cannot delete bin and xbin from system.ext2 , which leads to files to be read when they are not needed.
No empty system.ext2 file present.
Cannot Modify the initrd to increase the space , looking forward to use this code:
When using the kernel from munjeni (extracted) all what happens is G1 logo appearing and nothing else.
Bases :
zImage from mujeni's CM9 from boot.img
iPlasm's boot.img
initrd from either schlund's CM7.2 or shlund's Froyo 2.2
/system/ from munjeni's CM9
HARET_PHOTON7227.exe from PhotonAndroid Developement
Startup File from schlund's Startup.
All help appreciated
I found a 200mb system.ext2 , however , whenever i put files in it , the next time I mount it I loose everything I put inside , but everything deleted remains deleted. -_-
Glad to see you're trying to do some,
You should not try cm7 kernel with CM9, You're trying to make CM9 SDcard version so forget about cm7 kernel (you may do only for comparing)
please, try the munjeni's boot.img from (update 04.Jun. for rom 24.May.2012) or mine, because the munjeni's rom (24.May.2012) boot.img is older kernel. the new one includes bluetooth fix (NOT Handset Car).
what i see in system.ext2 i don't think you should empty or even use them, it should be writing in command (terminal) that will create those files into EXT2 file.
here is an example: http://forum.xda-developers.com/showthread.php?t=1055923
You can collect more informations in HTC HD2 forums which include SDCard versions,
Have fun,
Will try that , because the kernel from munjeni showed me .T...Mobile and then did nothing. hopefully yours work
I just tried your way iplasm , and guess what , I get the same splash screen G1 TMobile.
any thoughts?
thethiny said:
Will try that , because the kernel from munjeni showed me .T...Mobile and then did nothing. hopefully yours work
I just tried your way iplasm , and guess what , I get the same splash screen G1 TMobile.
any thoughts?
Click to expand...
Click to collapse
Sorry to say that, this htc mini is not my phone, so I'm so limited to work on it. especially going back to windowsmobile for testing sdcard again. :silly:
Let me say, are you still using both these together froyo and merging them with other? don't do that.. this won't work. froyo things with other ROMs won't work!
You should do one ROM for it's settings, don't catch another things, for example froyo or things.
just those files be their,
1- HARET.exe
2- STARTUP.TXT
and begin to do, and choose the only one ROM you want to make it SDCard version,
about splash screen, it means you didn't applied them correctly, because none of these bootscreen include t-mobile,
I remember the cotulla's version was include AT&T splash screen.
iPlasm said:
Sorry to say that, this htc mini is not my phone, so I'm so limited to work on it. especially going back to windowsmobile for testing sdcard again. :silly:
Let me say, are you still using both these together froyo and merging them with other? don't do that.. this won't work. froyo things with other ROMs won't work!
You should do one ROM for it's settings, don't catch another things, for example froyo or things.
just those files be their,
1- HARET.exe
2- STARTUP.TXT
and begin to do, and choose the only one ROM you want to make it SDCard version,
about splash screen, it means you didn't applied them correctly, because none of these bootscreen include t-mobile,
I remember the cotulla's version was include AT&T splash screen.
Click to expand...
Click to collapse
I found the problem , I'm using a new system.ext2 created by me , I put the /system/ files of yours inside , then I took the kernel from your rom , and then I used schlund's initrd (because I compared it to the original initrd and found that the only differences were in :
1-splash screen
2-mounting the sd or mounting the ext/sd
3-order of command execution)
so I found out the Cotulla (the original creator of the init inside the initrd.gz ) has put a G1 .T...Mobile splash screen , and when the kernel is loaded , it is loading it as rom , not as sd boot so it launches the splash screen instead of launching the android bootloader , I'll have a look and see and luckily munjeni will reply to the pm I sent him (he helped me with creating the system.ext2 and the initrd)
thethiny said:
Hi,
may you help me with something?
I have a ramdisk (initrd.gz)
and a kernel (boot.img)
and an zImage (kernel main)
however , I cannot seem to be able to extract the zImage , but I did extract the boot.img and the initrd .
In order for me to make it SD Boot , I should allow SD boot from zImage , but I can't open , do you think you can do that for me?
Click to expand...
Click to collapse
look, zImage is Kernel, you're doing to open Kernel.. zImage isn't an Archive file. so You don't need to edit or open zImage
Boot.img contains RAMDISK & Kernel, RAMDISK=intrd.gz, Kernel=zImage
You will need to extract the Boot.img from CM9, and convert them to initrd.gz and zImage,
iPlasm said:
look, zImage is Kernel, you're doing to open Kernel.. zImage isn't an Archive file. so You don't need to edit or open zImage
Boot.img contains RAMDISK & Kernel, RAMDISK=intrd.gz, Kernel=zImage
You will need to extract the Boot.img from CM9, and convert them to initrd.gz and zImage,
Click to expand...
Click to collapse
ok I already did that , but the zImage extracted from CM7 , doesn't match the zImage from CM7 SD Boot (same ROM , same Dev , diff size).
So I wanna extract the zImage so I can modify the Boot section to SD Boot.
it's not easy to edit kernels, just a Q: have you tried from extracted cm9 two files the kernel & ramdisk and rename them to zimage and initrd.gz to SDCard and see results?
and if you really want to modify zimage (needs unpacking and repack), click here: http://lmgtfy.com/?q=Modify+zImage+Android
iPlasm said:
it's not easy to edit kernels, just a Q: have you tried from extracted cm9 two files the kernel & ramdisk and rename them to zimage and initrd.gz to SDCard and see results?
and if you really want to modify zimage (needs unpacking and repack), click here: http://lmgtfy.com/?q=Modify+zImage+Android
Click to expand...
Click to collapse
Yes I tried , also I'm a Windows User , so I use Cygwin , and none of the commands above worked! I tried using Ubunty 12 and I get error at line 12
Hi I know there are lot of professional Rom mod-er here.
May I know which tool is use for deodex rom?
I'm working on J7108 firmware, I tried Assayed Kitchen, problem is when I flash the standalone file, the wifi is not working anymore. I'm not sure is due to deodexed error or what, I reflashed modem.bin but it's still the same.
Second question, which tool is use for edit service.jar and framework.jar? I have no idea it need dependency or what, I use batchApk but the recompiled file is causing the device stuck on boot screen. 3. What is the right step to do it?
I think i found a solution specially after porting a rom in the same MT6580 device suddenly one of the problem is unknown baseband, even u restore IMEI using chamelephone still not working. You can try those flashable zips below, i got those mtk-ril libraries in different Mt6580 devices try each zips and flash to your device and see which one is working. If its still not working pull your mtk-ril.so and mtk-rilmd2.so from stock to port and see if it works. Good luck.
link: https://mega.nz/#F!1gYCmLKJ!tT1eXce7fNAsrD4GqF4uxw
Press THANKS if i help :good:
RIL Part are more files than mtk-ril.so and mtk-rilmd2.so ... go go stock libs and bin folder and take search with *ril ... you will find many files ..gsmmux files in /bin are files of RIL part too ..maybe you have to change modem.init.rc in boot.img and maybe other initis .... take a look at init.rc at mounting point from sdcard mntblkXXXX...