Related
I would love to help the community by using your kernel for the newer radios to port any roms for the older radio... is there any help you can give me? should i use your boot.img from the test-donut.img/test-eclair.img?
Click to expand...
Click to collapse
first, a thing we must know for porting job is what boot.img included.
here: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
the ramdisk do some initializing jobs, so if we port a ROM, we should ensure that the content in ramdisk and files which are included in ramdisk (like init.rc), have necessary things the ROM needed.
for the first step, we can just extract the boot.img from the ROM, and extract the ramdisk from the boot.img which extracted just now, then repack it with my kernel (you can extract the kernel from my boot.img with same tools).
(to execute the perl script in link above, you need linux or just cygwin. )
but if we are sure that the ROM we want to port have nothing special with ramdisk, just like common ROMs, we can use my boot.img files directly. for eclair ROM, I suggest you extract the boot.img from my ROM, and don't use the first boot.img (test-NOCDB.img) I had posted.
after this, make our update.zip (use other's ROM as an example, especially the update-script in META-INF directory). sign our zip with testkey and apply it, then we can make our phone booting into desktop.
(you can find information about sign and download tools here: http://forum.xda-developers.com/showthread.php?t=471586, though the thread is not talk about how to sign things)
the main troubles we may meet probably are symlinks and setperm* in the update-script. if there is already a file/link has a name we want to symlink to, or if there isn't a file we want to symlink from or setperm, we will fail. so check the files carefully.
the next step is make everything work properly. we can use file from a ROM which made for new radio (and work well of course) to replace the one in the ROM we are porting. we can find these files in my 2.x ROM for eclair, or other's 1.6 ROM for donut (and for new radio, since the maker of them tested them already).
the most important files are (to my knowledge):
system/lib/libhtc_acoustic.so
system/lib/libhtc_ril.so (if something wrong with mobile network)
system/lib/libcamera.so
system/lib/libcameraservice.so
system/lib/liboemcamera.so (for 2.x) or system/lib/libqcamera.so (for 1.6)
system/lib/libgps.so
system/bin/akmd
(are there something I missed?)
(if we want to use NCommander's work on CameraHardwareInterface with a 2.x ROM, we should use my kernel for DONUT instead. I didn't try it, and I don't recommend it.)
these files are some thing work with hardware partially, so different radio may need different files. but if something just work fine, don't hurry to replace the file for it.
and now...., I don't have more thing to talk about, since we have most things work well. but for further tweaks, there are lots of things to do.
everyone can post your question here. if I know the answer I will post it. if I don't or I am not online, I think others will response you. and if there are things I missed or made some mistake, plz point it out
I will update this post when we collection more info or correct something. I find that I don't organized everything in order . I will update it later.
Thanks for the post... what's the difference between your eclair/donut kernel? (This is based on your original post about your kernel... is there an updated kernel somewhere i should know about?)
Edit
Nevermind i figured it out by reading your post more. carefully thanks for the detailed instructions
Thank you very much for this sanpei. This is the type of posts that really should be on this forum
Appreciated so much. waiting for your next updates.
Phil_McRevis said:
Nevermind i figured it out by reading your post more. carefully thanks for the detailed instructions
Click to expand...
Click to collapse
sorry for my poor ability of expression
asero said:
This is the type of posts that really should be on this forum
Click to expand...
Click to collapse
I expect more people can share their knowledge, and we can make a wiki for all
Hello!
I have to edit some lines of init.rc of your kernel. I've thus extracted the ramdisk, edited the file, repacked and tried booting with fastboot boot kernel-img ramdisk-img, but the phone hangs on the operator logo. I've tried even just extracting kernel+ramdisk and boot them - same result (the boot.img works well).
how can I fix it? Thanks
Wrong post
I have an Iorgane F22 and the released android rom 2.2 byt the have look the phone with there standar keyb and the own theme , i have manege to unlook root acces to the phone how do i remove the custum theme and where kan i edit to unlock the defualt keyb
thanks
Erik
.........................................................?
Hi!
Maybe this ROM is the answer for the MiPhone-Topic. It seems to be the same hardware. Can you upload your rom somewhere please?
Can someone who has this device with 2.2 installed please image the system and post a link where the system.img can be downloaded. I need it to put 2.2 on another device with the same processor. Thank you.
Edit: Here is a forum with the download link for the rom. If you use this link and update your phone to 2.2 please image the system files and give me link to download the image. Also, during the upgrade process a directory should be created in the same directory as the flasher. This directory will have all the images. If you can just copy this directory and then zip it up, provide a download link and give me link, that will work to.
http://www.androidicecream.com/forum/viewtopic.php?f=37&t=34
dsixda's Android Kitchen - Now for Samsung Galaxy S Plus (I9001)
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy S Plus custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of version 0.182, you can now create your own Galaxy S Plus ROMs with the kitchen.
I'd like to thank the guys in this thread, especially crybert, oisis and mbba67 for helping me out, as well as for testing on their devices and providing feedback. I only have a Bell Galaxy S2 I9100 so their assistance was greatly appreciated!
[MAIN PAGE] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
PROCEDURE
This guide may be a bit basic right now but I will update it later if required.
First, you need a rooted Samsung Galaxy S Plus (I9001) with a ClockworkMod-based custom recovery.
Visit the Android Kitchen thread to download the kitchen. Then, follow the link to the FAQ which will show you how to install it on Windows or Linux or Mac. Ensure you read the FAQ carefully.
Put your base ROM(s) under the original_update folder. For the Samsung Galaxy S Plus, there is support for the following formats which can be placed in that folder (you can place multiple ROMs there):
Stock firmware:
system.img.ext4 and boot.img (and optionally: cache.img.ext4)
TAR file containing system.img.ext4 and boot.img (and optionally: cache.img.ext4)
ZIP file containing system.img.ext4 and boot.img (and optionally: cache.img.ext4)
Custom ROM:
ZIP file created by the kitchen from the stock firmware (NOTE: The kitchen may NOT support custom ROMs created through other methods, due to potential file structure incompatibility issues)
Nandroid backup from ClockworkMod recovery
system.img, cache.img and boot.img
system.ext4.tar, cache.ext4.tar and boot.img
Here are some basic steps to creating your first ROM after you have your base of files under original_update (more options are available in the kitchen):
Start the kitchen with: ./menu
Create a working folder (by choosing your base ROM)
If you used a system.img.ext4 but then didn't include the cache.img.ext4, then you have the option to add a cache.img.ext4 later using the Extract SGS2 CSC script in the Advanced menu's 'Plugins' section.
Root your ROM
Add Busybox
In the Advanced options menu: De-odex your ROM
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin.
Some notes:
Here are some screenshots of how to use the kitchen for the I9001, thanks to crybert.
Just select the defaults whenever you are asked about something in the kitchen and are unsure whether to type 'y' or 'n'.
There are lots of questions answered in the FAQ in Posts 3 and 4 of the main Android Kitchen thread. So please go through that first if you have any issues.
For the benefit of other readers and to prevent confusion, please only discuss Samsung Galaxy S Plus in this thread!
Most of all, have patience, take your time and enjoy!!
Reserved...
Reserved, just in case
Great stuff .. Thanks for ur work
great work!
did anyone tried the porting option in this kitchen?
could be very usefull to port miui or cyanogenmod to our device
i know its signed as experimental but anyone know the chances that this option will lead to a success?
Blumdum said:
great work!
did anyone tried the porting option in this kitchen?
could be very usefull to port miui or cyanogenmod to our device
i know its signed as experimental but anyone know the chances that this option will lead to a success?
Click to expand...
Click to collapse
Would be kind of hard to do..., but I heard that the SGSPlus is similar to the Desire HD, so I would start with a ROM from there.
You think the Cyanogenmd for the DesireHD would work? And if I try the porting thing. Is there a big chance to full brick my phone. I know I have to look that the boot.img and the system is flashed on the right partition. So if something goes wrong I think I can enter Download-Mode anyway?
Desire HD uses the same cpu/gpu as i9001 so there should be a big similarity
im asking myself the same question wether there is a chance for a full brick
but the boot.img will be written on the right partition
I don't know much about porting apart from the generic steps in the kitchen scripts. But if you have a nandroid backup, how would you brick (unless you mean the wrong partition would mess it up.. In that case just double check the updater-script before building).
maybe a wrong boot.img could lead to a brick
crybert said:
You think the Cyanogenmd for the DesireHD would work? And if I try the porting thing. Is there a big chance to full brick my phone. I know I have to look that the boot.img and the system is flashed on the right partition. So if something goes wrong I think I can enter Download-Mode anyway?
Click to expand...
Click to collapse
I dont know about porting or boot.img, but what if you just replace SGS+ boot.img over the DesireHD Cyanogenmd Rom boot.img then just fix them in the kitchen. I dont know..........
crybert said:
You think the Cyanogenmd for the DesireHD would work? And if I try the porting thing. Is there a big chance to full brick my phone. I know I have to look that the boot.img and the system is flashed on the right partition. So if something goes wrong I think I can enter Download-Mode anyway?
Click to expand...
Click to collapse
if the porting of cynogenmod from DHD succeeds we will be able to port their ICS too then. with some modifications to boot.img, build.prop. etc.. , replacing drivers, maybe we can try camera drivers and libs from I9000 port , of course we'll need someone to compile the right kernel. imo it can be done if we put a team work into it
but we can first try to port the desireHD rom to our device using the kitchen and then see if the device boots
Blumdum said:
but we can first try to port the desireHD rom to our device using the kitchen and then see if the device boots
Click to expand...
Click to collapse
the rom from DHD won't boot on I9001 without the right kernel.
Can you tell me where can I find an information how to add to my fresh cooked rom CWM FeaMod Recovery?
rayiskon said:
the rom from DHD won't boot on I9001 without the right kernel.
Click to expand...
Click to collapse
did you try it?
EDIT:
when we need a CM kernel we could build one
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
mr_omega said:
Can you tell me where can I find an information how to add to my fresh cooked rom CWM FeaMod Recovery?
Click to expand...
Click to collapse
1. just add the recovery.img to the main directory of your rom. Where /system and META-INF is located
2. add the following line to your updater-script:
package_extract_file("recovery.img", "/dev/block/mmcblk0p13");
P:S.
We should move the discussion about CM to another thread. I think this is a bit offtopic
Hi guys, I have updated the kitchen to 0.182. See the main thread (linked on post #1) for full release notes.
dsixda said:
Hi guys, I have updated the kitchen to 0.182. See the main thread (linked on post #1) for full release notes.
Click to expand...
Click to collapse
Hi, how come i can extract boot.img but cant repack, there is no option for repack
try porting MIUI instead of CM7. MIUI is not only fast but customize able and i think dsixda does the work for you and then minor bugs can be fixed.
hello guys,
First thing is I'm a noob here, totally noob, altough I have used galaxy fit for almost one year now and have tried many, many custom roms here, I think it is already the time that I'm making my own.
So I read many tutorial how to make a custom rom, with dsixda kitchen. I read there on the original thread that dsixda kitchen didn't support our device, but I was persistent, downloaded all the requisites, and skip skip, finally I understand now why, because the file system of DXKT7 is rfs (system.rfs), it must be converted into ext4, or at least has system.img (am I wrong?), so I search every tutorial about converting file system into ext4, and almost all suggest it should be done on the device itself, or should I say, flashing this stock rom via ODIN, root it, and then u can convert it into ext4.
isn't there any way to make it done in PC so I can start edit this rom in kitchen?
I read it somewhere about extracting initframs.cpio from zimage, please, if anyone know this way, please teach me how
any explanation are appreciated, thank u in advance guys, n sorry for my english
edit:
pratyush.creed said:
not very hard ,just extract initramfs.cpio from the zImage ,add this line
CONFIG_EXT4_FS=y in filesystems,then change Mount points in init.rc of Ramdisk
and then Format All Dev Blocks e.g. System,Data,Cache to ext4 !!
Click to expand...
Click to collapse
Prodai said:
hello guys,
First thing is I'm a noob here, totally noob, altough I have used galaxy fit for almost one year now and have tried many, many custom roms here, I think it is already the time that I'm making my own.
So I read many tutorial how to make a custom rom, with dsixda kitchen. I read there on the original thread that dsixda kitchen didn't support our device, but I was persistent, downloaded all the requisites, and skip skip, finally I understand now why, because the file system of DXKT7 is rfs (system.rfs), it must be converted into ext4, or at least has system.img (am I wrong?), so I search every tutorial about converting file system into ext4, and almost all suggest it should be done on the device itself, or should I say, flashing this stock rom via ODIN, root it, and then u can convert it into ext4.
isn't there any way to make it done in PC so I can start edit this rom in kitchen?
I read it somewhere about extracting initframs.cpio from zimage, please, if anyone know this way, please teach me how
any explanation are appreciated, thank u in advance guys, n sorry for my english
edit:
Click to expand...
Click to collapse
copy system.rfs and csc.rfs from a stock rom and boot.img from custom rom to ur original_update folder and extract it...follow onscreen instructions in the kitchen and use magiciso to extract system folder and then do the mods and all u want and pack it now it will work meta-inf folder will be autogenertaed but replace the update-binary in ur created rom from anyother custom rom and it will surely work
yeshwanthvshenoy said:
copy system.rfs and csc.rfs from a stock rom and boot.img from custom rom to ur original_update folder and extract it...follow onscreen instructions in the kitchen and use magiciso to extract system folder and then do the mods and all u want and pack it now it will work meta-inf folder will be autogenertaed but replace the update-binary in ur created rom from anyother custom rom and it will surely work
Click to expand...
Click to collapse
I have unpacked boot.img using advanced options in kitchen's menu, now I have folder ramdisk and zImage, what to do now to convert it to ext4?
oh, I followed ur instruction, extract system.rfs with magicIso and put them together with boot image (the one from stock) and others in original update folder and now I can deodex it.
my question, should I change the boot.img with custom rom's boot image so it can support ext4 file system or just go with the stock?
or how can I change the kernel?
edit : oh, after hours searching I just found this thread, everything I need is here--> http://forum.xda-developers.com/showthread.php?t=1414534
anyway thank u guys.
Prodai said:
oh, I followed ur instruction, extract system.rfs with magicIso and put them together with boot image (the one from stock) and others in original update folder and now I can deodex it.
my question, should I change the boot.img with custom rom's boot image so it can support ext4 file system or just go with the stock?
or how can I change the kernel?
edit : oh, after hours searching I just found this thread, everything I need is here--> http://forum.xda-developers.com/showthread.php?t=1414534
anyway thank u guys.
Click to expand...
Click to collapse
ur boot.img from stock is rfs format so it wont work if u use that...use boot.img from any custom rom that is also based on ur baseband version(DXKT7)man..the boot.img will automaticaly have the ext4 filesystem(in custom boot.img not stock)....kernel is later part of ur rom man better not go into that now .....copy boot.img from custom rom of ur baseband version then system.rfs and csc.rfs file from stock rom and do as i said above and dont forget to replace update-binary in ur rom after creating the output_zip file from any other custom rom or ur rom wont install
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