I have been working on a project to insert debug messages in low level dlls [like coredll, ws2.dll] and so on. The testing so far was done on device emulators and the .nb0 image seems to be pretty stable on it now.
Where I need help from xda community is how to take the next step - how to generate a ROM image for my kaiser. Specifically what all build options should be specified to my platform builder to get the right image for my device.
I tried to search previous postings for help but could not find one - may be I did not search thoroughly. My apologies if I did not search thoroughly - if it has been discussed in the past - would be great if someone could point me a link to it.
Thnx
TPC and myself has kitchens available for download. Pick one and replace your files, and build ROM.
To be precise - download a kitchen from here?
http://m-s-j.net/tpckitchen/kitchens/
poifgh said:
To be precise - download a kitchen from here?
http://m-s-j.net/tpckitchen/kitchens/
Click to expand...
Click to collapse
yes any one will work
Thnx for helping .. have a few hickups setting the ROM up.
1. Downloaded http://m-s-j.net/tpckitchen/kitchens/TPC_KITCHEN_6.120146.7z
2. Doing a build_rom.bat results in the following errors
Failed to set data for 'htcrt_backup'
"There is no device found to meet your project configuration. Try to update your devices file with new one."
"Access Violation - read at 000000"
Do I need to setup some config file somewhere - do we have a README for the process?
3. I dont quite understand the point "replace your files, and build ROM."
I have changes done to coredll and ws2.dll which were compiled using the 'emulator' flag in platform builder
a. What compile flags should the I use before I copy/paste my dlls into the kitchen
b. In the current kitchen - coredll is a directory containing 5 files S00 to S04 and also contains imageinfo files. Do I put in my coredll.dll file? or is there a step in between?
As you could see from my questions, I am complete newbee in building ROMs for phones - would appreciate any help from the community
thnx
I guess you're using Vista, right? It did me too. There are two (three?) solutions:
1. Disable UAC
2. Ignore it and via htc rom tool build .nbh by yourself (click right -> run as administrator on TOOLS\htcrt.exe) - OS.nb is in TMP directory
3. (not confirmed) Run the build script via cmdline manually, AFAIK TPC has got it written somewhere there.
poifgh said:
Thnx for helping .. have a few hickups setting the ROM up.
1. Downloaded http://m-s-j.net/tpckitchen/kitchens/TPC_KITCHEN_6.120146.7z
2. Doing a build_rom.bat results in the following errors
Failed to set data for 'htcrt_backup'
"There is no device found to meet your project configuration. Try to update your devices file with new one."
"Access Violation - read at 000000"
Do I need to setup some config file somewhere - do we have a README for the process?
3. I dont quite understand the point "replace your files, and build ROM."
I have changes done to coredll and ws2.dll which were compiled using the 'emulator' flag in platform builder
a. What compile flags should the I use before I copy/paste my dlls into the kitchen
b. In the current kitchen - coredll is a directory containing 5 files S00 to S04 and also contains imageinfo files. Do I put in my coredll.dll file? or is there a step in between?
As you could see from my questions, I am complete newbee in building ROMs for phones - would appreciate any help from the community
thnx
Click to expand...
Click to collapse
this is not the right place to be asking this, if you have questions about my kitchen you need to look in my kitchen thread. you will find the answers to your questions have already been posted there and if you need more help ask there and we will help you.
twopumpchump said:
this is not the right place to be asking this, if you have questions about my kitchen you need to look in my kitchen thread. you will find the answers to your questions have already been posted there and if you need more help ask there and we will help you.
Click to expand...
Click to collapse
you know how it is anymore, Have a question = START A NEW THREAD.
msd24200 said:
you know how it is anymore, Have a question = START A NEW THREAD.
Click to expand...
Click to collapse
= Flying Fishheads lol
Related
Okay after reading through a few threads on XDA I thought I might take a stab at writing a Simple tutorial of the knowledge I know of cooking a rom
Step 1: Download a kitchen of your choice I think the Kitchens from Matt are the best to use only my recommendion
Step 2: Download the OEM packages you'll need..Leave them in a different folder then the Kitchen right now..
Step 3: Make a OEM folder in the kitchen folder if theres not one already and place it in the kitchen folder
Step 4: Take the OEM packages from the desktop and drag the ones needed for your rom
Step 5: Click Build OS check the files your going to have in your ROM to be built..if it errors look at where it errored and check the OEM package to see if it meets the standered below
Step 6: Now add any thing you need to edit in the dump or replace files (EX: Welcome Screen, themes, initflashfiles.dat file ect)
Step 7: Now run the CreateROM.bat once finished you'll have a new file in the temp folder
Step 8: In the kitchen there will be a nb2nbf_wizard.exe if not search the forums..open that model ID will say Wizard.. change the language to WWE then on the bottom you'll see empty fields..those are self explanatory pick OS for the ROM then locate the file in the TEMP folder of the Kitchen
Step 9: Now once its finished translating where ever the output direction was it will be your file to flash, now move that to the RUU and flash and say Hello to your own Cooked rom
PS Steps will varies from Kitchen to kitchen but this covers the jist of basic ones
nows for the complex parts how to make an OEM package...Information from double_ofour
Step 1: Vist http://www.famkruithof.net/uuid/uuidgen the Create UUIDs of another type should be set to Version 4: random then a code like this "6bfb7458-6a83-450a-9da5-b5feabba8335" will be made
Step 2: make the code the name of the 2 text files you have in the OEM package folder, Change one Text file extension to RGU and the other DSM
Step 3: now the RGU is where the Reg hacks are the first line MUST be REGEDIT4 then you list your Reg hacks.. in the formate like this
[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\MASD]
"TaskManager"="1_5_29968_1"
Step 4: Leave a space after the last reg hack and save as UNICODE
Step 5: add any files to the OEM package Folder they will be put in the /Windows directory
to make an extension into the programs folder you should edit the initflashfiles.dat
How to edit the initflashfiles- Should be done between useing the Build OS and Create Rom
Step 1: open the file with note pad
Step 2: remove any lines that aren't needed..sometimes you'll see likes to create a folder for a shortcut when your not using the program
Step 3: add a line to create a shortcut for a program from your own OEM package...Most packages here already do it for you
sigh I'm tired of typing but theres a basic out line of what cooking a rom consists of..feel free to add anything I might of missed
Just thought I'd help out anyone looking to cook a rom and needs a little guide
Please don't ask for help here..I'm not text support..I think there shoul dbe one thread for all cooking questions..you guys could even use the thread when i asked for help
PS again thanks to all the people here at XDA that made cooking simple easy even ifs making a OEM pack or a fix or even a kitchen thank you all
thanks ANTC!!!
thanks dude! can we have pictures too? (what the heck - had to ask )
thanks this is EXACTLY what I was looking for
mattk_r said:
thanks dude! can we have pictures too? (what the heck - had to ask )
Click to expand...
Click to collapse
sigh..sure once i can release my full touch rom using your kitchen
so no deal matt...lol not like you need a tut how to make a rom...maybe you could help with the cam issue to for my rom
everytime I click buildos.exe I get an error. No matter what folder I try it in, it just wont work.
How do I dump an official rom?
maybe some one can help you with the dump question its hard for me to put into words since core does it by it self
and th build os problem is something to take up with the maker of ur kitchen try doing a windows update you may need sp2 or net framework
I suggest making this thread sticky, removing all unnecessary posts, including this one and transform it into an How To thread. Where everybody can post tutorials on different aspects of rom cooking.
dferreira said:
How do I dump an official rom?
Click to expand...
Click to collapse
Same you do with an unofficial one lol The difference is that you won't find any missing files and that means less work for you.
anichillus said:
I suggest making this thread sticky, removing all unnecessary posts, including this one and transform it into an How To thread. Where everybody can post tutorials on different aspects of rom cooking.
Same you do with an unofficial one lol The difference is that you won't find any missing files and that means less work for you.
Click to expand...
Click to collapse
It won't dump using your kitchen... Try the last oficial RUU Prodigy of WM5 and you'll see that it seems to be protected, since it can't extract the 8004000 :s
anichillus said:
I suggest making this thread sticky, removing all unnecessary posts, including this one and transform it into an How To thread. Where everybody can post tutorials on different aspects of rom cooking.
Same you do with an unofficial one lol The difference is that you won't find any missing files and that means less work for you.
Click to expand...
Click to collapse
Coming from you thats a huge compliment..
what can i do if i want to add programs like TNT, i have few apps compared to mfrazz's build or TNT and now if i add 1 more program in my kitchen it crashes the buildimgfs.exe, anything i can do to add more? i am using faria's kitchen tool
nycelitemaster said:
what can i do if i want to add programs like TNT, i have few apps compared to mfrazz's build or TNT and now if i add 1 more program in my kitchen it crashes the buildimgfs.exe, anything i can do to add more? i am using faria's kitchen tool
Click to expand...
Click to collapse
Try using Core kitchen that should do the trick
hopefully as a newbie I can make my own rom with this
and please do help me if i encounter any problems
thanks in advance
Personally, I would suggest doing a topic like this in the Wiki. Then have a topic here that is stickied to point to the Wiki entry.
Here's a page I started for the Faria Kitchen last May. http://wiki.xda-developers.com/index.php?pagename=FPRK_Cooking_Instructions
You could take what ANTC posted and merge with the info I provided and come up with a nice generic page for cooking )most of the kitchens work the same since they all use basically the same set of tools).
Here's a page on making OEM packages that da_jojo added on:
http://wiki.xda-developers.com/index.php?pagename=FPRK_Creating_ROM_Packages
BTW: If you do the instructions in the Wiki then any / all of us can help maintain it (where posts here can only be maintained by the original poster).
i think this is good for those who already know how to cook, but too brief for beginners who know little about cooking a rom.
My problem when building the rom is when it is finished this error comes up
"c:\DocumentsandSetting\M541378\ApplicationData\hIqInc\PPC-BuildOS\9.05.3.0Temp\ROM\XIP"
so in my ROM folder there is no XIP, I create the folder, and I re-create, it and then the XIP folder erases. I have no idea why this happens? Can anyone please help....
Updating rom image USING FARSTONE DRIVE CLONE
Hi all i'm new at the forum, i would like to know if i can create an image with farstone drive clone of all the programs i have and configurations and then upload it to the phone?? I would like that even if i have to perform a hard-reset on the device it would still have all the progs and configurations created on the image uploaded.
Any suggestions are welcomed!!!!!
hi, I am a newbbiess... i am totally not understand what do u mean by kitchen... but i am intrested in generate a ROM myself.. please advice..
Hey guys im trying to build my own rom using a tutorial i found on this site. the thing is that im at the section where im suppose to put the missing files where they r to go but i cant seem to get pass that section.
my problem is that the PKG Tool shows me the missing files, but where do i find them using the explorer window opened.
i am frustreated man and really need help.
Tambuyeye said:
Hey guys im trying to build my own rom using a tutorial i found on this site. the thing is that im at the section where im suppose to put the missing files where they r to go but i cant seem to get pass that section.
my problem is that the PKG Tool shows me the missing files, but where do i find them using the explorer window opened.
i am frustreated man and really need help.
Click to expand...
Click to collapse
When creating packages with Package tool it creates the following folders:
SYS
OEM
Missing <-- Thats what you are looking for.
I suggest that if this is your 1st attempt and you are building based on a custom rom, use HyperCore Kitchen. Its very easy to use and does the extraction much quicker and easier than doing it by hand. Once you have the hang of it then just move your stuff to another kitchen. Nice part about HyperCore you can dump just about any rom if you set it for that specific device. Just a note: some cookers protect their roms and you end up with almost everything in Missing. You can dump WizFlo from 6.1.1.3 upwards easily
When you have run the PkgTool - Build Packages option, don't mistaken the Missing Manifests for the same thing as Missing Files or Missing Packages. The missing "dsm" manifest files the Pkg Tool refers to are contained in the XIP files (which you will be doing next, i.e., extract XIP). So, you can just ignore the Missing Manifest message and continue on, however be aware that you must use compatible XIP that contains these "missing" dsm manifest files when you go to re-build your rom.
If there are indeed missing packages or missing files, it will tell you exactly what they are and where (what folder) they are supposed to go into. These missing packages/files will be in the dump folder along side the OEM and SYS folders after you run the Build Packages option in the PkgTool app.
This took me a while to realize as it was not explained (or at least I did not see it anywhere) in the various forums/threads on rom building.
If I am wrong on any of this someone please correct me as I too am relatively newbie to this and still learning.
Good Luck!
Guy's,
This is my 2nd attempt to build a useful kitchen for Uni lovers. It uses a new set of tools and technology and you can customize/cook the rom exactly the way you like it. Porting or building XIP was a real pain but the kitchen builds the XIP and IMGFS together and importantly without manual intervention.
I believe this is the easiest kitchen ever built for Uni and you'll simply enjoy it.
The OS has been included in the kitchen is a fresh new Core - CE OS 5.2.21014.
OK, let's go for working part -
Unrar the kitchen in any of the drive in your PC (but must be in root) and it should look like - D:\TML_UNI_KITCHEN.
You'll find a command script "build_rom.cmd" under the TML_UNI_KITCHEN directory. Now, make a coffee, then just hit on this script and reluxe. Your ROM will be cooked within couple of minutes. Well, a little dialog box will pop-up at the asking what to do, select Encode to encode the rom and then exit.
You can follow the encoding steps like:
>>Encode>>Browse>>open nk.prj>>Encode>OK>>OK>>Exit.
Now, got to RELEASE directory, open ROMUpgradeUt.exe and flash the ROM to your device.
Advance part -
You can modify few parameters under the build_rom.cmd to make your custom rom.
set BUILD_TYPE=Regular
This is the type of your ROM to be cooked. The value "Regular" has an association with the directory \TML_UNI_KITCHEN\EXT\Regular. Put all the packages here, those you want to include in Regular build.
set BUILD_TYPE=Vanila
The value "Vanila" has an association with the directory \TML_UNI_KITCHEN\EXT\Vanila. Put all the packages here, those you want to include only in Vanila build.
PLease note, packages under the Regular directory will not be included in Vanila build and vise versa. There is also a Common directory inside the \TML_UNI_KITCHEN\EXT. You can put the packages here, those you want to include in Regular and Vanila both the builds.
set BUILD_NO=21014
This is the build number of the rom. The value "21014" has an association with the directory \TML_UNI_KITCHEN\21014. Actually you can put any value you want but whatever value you put must be associated with the same directory. Importantly SYS and XIP must be located under this BUILD_NO directory, i.e. \TML_UNI_KITCHEN\21014\SYS, \TML_UNI_KITCHEN\21014\XIP.
ROM template located under the \TML_UNI_KITCHEN\ROM directory.
OEM drivers located under the \TML_UNI_KITCHEN\OEM directory.
ROM will be transfered to \TML_UNI_KITCHEN\RELEASE directory after the successful build.
Directory Structure:
\TML_UNI_KITCHEN\21014
\TML_UNI_KITCHEN\21014\SYS
\TML_UNI_KITCHEN\21014\XIP
\TML_UNI_KITCHEN\21014\romhdr.bin
\TML_UNI_KITCHEN\EXT
\TML_UNI_KITCHEN\EXT\Common
\TML_UNI_KITCHEN\EXT\Regular
\TML_UNI_KITCHEN\EXT\Vanila
\TML_UNI_KITCHEN\OEM
\TML_UNI_KITCHEN\RELEASE
\TML_UNI_KITCHEN\ROM
\TML_UNI_KITCHEN\ROM\nk.nba
\TML_UNI_KITCHEN\TOOLS
\TML_UNI_KITCHEN\build_rom.cmd
Please note the kitchen is still in beta so you may notice some unwanted thing which I haven't noticed earlier. Also, the XIP inject part has not been finished yet. But it's not a big deal and not necessary for the current build.
You can easily inject it using Bepe's Xiptool if you want. Just pick the xip.bin from "temp" directory after the build, rename it to xip_out.bin and write to nk.nba.
There is also some other secret thing which I forgot to mention and love to forget.
Acknowledgment:
Major credit goes to Bepe as it was not possible to built this kitchen without his great tools.
Uni Kitchen v2.0 (beta):
http://vidmes.com/xda/Uni/ROMs/Tomal/TML_UNI_Kitchen_2.0_Beta.rar
http://vidmes.com/xda/Uni/ROMs/Tomal/TML_UNI_Kitchen_OEM.rar
Cheers!!!
Gr8 news Tomal.
Thx 4 you hard work.
Good job!Thanks!
Hm, i tried to start kitchen, but unfortunately getting error:
Code:
PLATFORMREBUILDER Copyright (c) 2008-2009 bepe Jan 4
Build: Regular
Locale: 0409
Preparing release structure...
... done!
Collecting standard packages and initializing hives...
XIP: 3 packages
IMG: 71 packages
Error: 0x8000000a
'initflashfiles.dat' does not exist in the specified paths!
ERROR! (errorlevel: 1)
Press any key to EXIT
I get the same initflashfiles error. It occurs in this command line:
.\tools\platformrebuilder.exe
in .\tools\buildOS.cmd
Same error here.. :/ If there is a fix it looks pretty good! Well done, Tomal
opppppsss...my mistake!
I forgot to include the OEM pack. Don't worry, I'll upload it asap.
Update:
OEM part has been uploaded (in 1st post). Extract it under \TML_UNI_KITCHEN directory.
regards
tomal said:
[...]
There is also some other secret thing which I forgot to mention and love to forget. [...]
Click to expand...
Click to collapse
LOL how nasty
gonna try and study it...
thx a lot for your work! hope my little donation was appreciated more than simple words
Wonderful!!!! Thank You
And with VInit help we can add flashdisk until he gets a way to make combined storage work for G4.
this could be the start of something new for uni lovers, many tnx tomal
Thanks a lot Tomal!
Hopefully on my vacations I can get into it!
Cheers,
Great work, Tomal I have just one question. I started build_rom.cmd and after some time a window pop-uped asking for HTC64 EXT rom... and there were 3 options : Encode, Decode and Exit. Afraid of doing something wrong I clicked Exit. Can you give some instructions how to continue the process and if there are any additional settings to make.
Thanks in advance .
simeonfilipov said:
Great work, Tomal I have just one question. I started build_rom.cmd and after some time a window pop-uped asking for HTC64 EXT rom... and there were 3 options : Encode, Decode and Exit. Afraid of doing something wrong I clicked Exit. Can you give some instructions how to continue the process and if there are any additional settings to make.
Thanks in advance .
Click to expand...
Click to collapse
Select Encode>>browse (to open the project file)>>open nk.prj>>Encode>OK>>OK>>Exit.
Cheers
Thank you! I just flashed with the Vanila ROM and it seems to be very good - it's fast, after soft reset there is ~28 mb free RAM. Again - thanks for your hard work .
it's possible to do a multilanguage/region kitchen? almost for common applications and configuration applets.
thx.
tomal said:
Please note the kitchen is still in beta so you may notice some unwanted thing which I haven't noticed earlier. Also, the XIP inject part has not been finished yet. But it's not a big deal and not necessary for the current build.
You can easily inject it using Bepe's Xiptool if you want. Just pick the xip.bin from "temp" directory after the build, rename it to xip_out.bin and write to nk.nba.
There is also some other secret thing which I forgot to mention and love to forget.
Click to expand...
Click to collapse
I tested it, and its working fine 100%, 1000 thanks Tomal for the great work!!!! I also used the optimize tool from HyperCore kitchen and the final nb.nbf is only 44M, but what about the XIP is it in my new rom or is it not and if not how do I inject it? I tried the implantxip tool from the TOOLS directory but I seam to not getting it how it works. Please help!!!
With the OEM directory in place, this kitchen produces great ROM's!
Thanks Tomal!
Thanks Tomal !
May i know how to use your kitchen to dump other ROM ?
Very appreciated your reply !!!
Thanks & Regards,
Upload This ROM
Can you guys help in uploading a ROM produced by this kitchen new Core - CE OS 5.2.21014
I would like to try it out.
Appricated ...
Vanilla nk.nbf
Here you are Fast and stable :]
I am a linux user...
Anyone can share the howto or if there are any guides?
+1 bumping this thread
Second that...
http://www.koushikdutta.com/2009/08/build-configuration-for-t-mobile.html#links
He seems to have a script to compile the Kernel...
I don't know to what extent this would help us but it is a start. I dont quite know how the apps are installed on a new ROM....
It would be nice if someone can explain what is needed and what is optional in the kernel and some of the mods that other people are doing and how they integrate in the OS.
I see a lot of improvements in the new ROM's but no how-to on doing it your self. I thought that was the point of having open source OS.
I would quite like this as well =o)
Have made a bit of a start by following this:
http://source.android.com/download
Shows you how to get all the code and do a build.
I believe the next thing would be to pick the required files from the output folder of the build, dump the boot.img and replace the kernel with 32B or 32A one, add the Magic model config file (to ramdisk) and recreate the boot.img
Replace/Add any modules required like maybe wifi or bluetooth, then need to change the build.prop file and put it all in to update.zip and sign the file.
Haven't had time to test this out but seems kind of logical...maybe?
Hello!
I'm following the android.com tutorial, but I want to ask: how can I download the donut branch? There's no mention in the entire site about it... Also, the cyanomod's multitouch and so on, where does it come from? Is it made by himself or it's somewhere in the net?
Thanks
Learn how to use GIT to get the donut branch from here: http://android.git.kernel.org/
Proble is that it doesn't specify the donut project path
Is there a command to list all project paths? I can't seem to find it
L10nH34Rt said:
Proble is that it doesn't specify the donut project path
Is there a command to list all project paths? I can't seem to find it
Click to expand...
Click to collapse
Code:
git branch -a
in any local git directory
Ok, then so far I've downloaded the donut branch, and compiled too. What now?
1. how to create a ROM from the made files?
2. how to compile the kernel / how to replace the one created with the make command with the one I'm running on?
3. is there any option I can configure to fit my phone? (HTC Magic 32A)
4. how can I root my ROM?
thanks
there is this guide that i have found:
http://www.koushikdutta.com/2009/08/build-configuration-for-t-mobile.html
'make' finished with success but i can't find how to transform it into 'update.zip' file...
anyone?
It says that in the link you have posted yourself.
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