Database Users

[SOLVED]non booting rom?.....now make a bootable rom

hi all..
we all have suffered from one common things while making a rom..
after all your hard work and spending so much time and reading on and on for improvements u encounter this
stuck at smart mobility
so i request all people who faced such problems and have solved them,,plz write here about it..
what u have done..??
what is the cause??
this will easier for lots of people to understand why they have non booting rom..
so afterall i got this solution..
1.Make sure the following packages are cooked:
. NetCF or NetCF 3.5
. Dummy FWUPDATE
. Dummy SQM
. WinCENLS_WWE
byDOTCOMPT
2.if your rom gets stuck on radio screen and the screen doesnt dim after a lil bit then you have problem with xip...if the screen does dim it usually means a problem with system.
byTWOPUMPCHUMP
3.recmod ALL modules in your EXT folder
recmod these three folder in sys...browsing, browsingcore, and browsingie
BYTWOPUMPCHUMP
4.ALSO SEE THE ATCHED TXT FILES BY KOKOTAS FOR WHICH FILE TO RECMOD ON PAGE 3

This could be caused by many things.
I suggest you check all last changes you did, which packages/edits etc...
Before I edit my kitchen I always make sure I have a backup incase stuff like this happens so I can refert back.
I recommend editing step by step and not edit to many things at once.
Grtz Leo

Totally agree with Laurentius.
Just some points to look:
1.wince.nls
2.XIP
3.boot.rgu
4.UPXed files
Best Regards!
ps:A Hard Reset would be nice after flashing

kokotas said:
Totally agree with Laurentius.
Just some points to look:
1.wince.nls
2.XIP
3.boot.rgu
4.UPXed files
Best Regards!
ps:A Hard Reset would be nice after flashing
Click to expand...
Click to collapse
almost done..
ok i made a rom 23544..works like a charmm..
but i just upgrade new build like 23548,49,52
all have non booting issue..
no changes have been made from 23544 build not even new application added..
but no luckk.
checked wince..found xip is ok..
also done recmod but no luck..
so now???
i tell u what i just change build 23544,,i got bootable rom..then just chang build ..48..49
non bootable rom

Try XIP 23544, SYS 23548,49,52.
Maybe a bad XIP source?!

If you change to a new MS build you only need MSXipkernel plus SYS.
No recmod is needed, I never use recmod.
Try playing with wincenls, move it from SYS to XIP or maybe viceversa.

Laurentius26 said:
If you change to a new MS build you only need MSXipkernel plus SYS.
No recmod is needed, I never use recmod.
Try playing with wincenls, move it from SYS to XIP or maybe viceversa.
Click to expand...
Click to collapse
but without recmod the kitchen even not building a rom

That's weird, the kitchen should run without recmodding modules.
Maybe you have a conflict in your kitchen where a file is overwriting a module?
saurabh88 said:
but without recmod the kitchen even not building a rom
Click to expand...
Click to collapse

so your rom gets stuck at first screen, with radio info ect on bottom of screen? what modules are you recmodding? do you have hidden and system files visable on your pc? what kitchen are you using? there are alot of things that could cause your rom not to boot, the more info you give the easier it is to help

twopumpchump said:
so your rom gets stuck at first screen, with radio info ect on bottom of screen? what modules are you recmodding? do you have hidden and system files visable on your pc? what kitchen are you using? there are alot of things that could cause your rom not to boot, the more info you give the easier it is to help
Click to expand...
Click to collapse
i use evk..
other things i have already stated before that with same kitchen i can make rom of 23544;but what the fkkkk..i just change build to23548;4951 non bootibg rom...
strange but true.
i just use extra button in evk to recmod as someone already made a post to use extra button via batch file..

saurabh88 said:
i use evk..
other things i have already stated before that with same kitchen i can make rom of 23544;but what the fkkkk..i just change build to23548;4951 non bootibg rom...
strange but true.
i just use extra button in evk to recmod as someone already made a post to use extra button via batch file..
Click to expand...
Click to collapse
Make sure the following packages are cooked:
. NetCF or NetCF 3.5
. Dummy FWUPDATE
. Dummy SQM
. WinCENLS_WWE
Could you post your Build_log.txt here.
-

saurabh88 said:
i use evk..
other things i have already stated before that with same kitchen i can make rom of 23544;but what the fkkkk..i just change build to23548;4951 non bootibg rom...
strange but true.
i just use extra button in evk to recmod as someone already made a post to use extra button via batch file..
Click to expand...
Click to collapse
then obviously something different has been done with the newer builds you are trying to use that wasnt done with 23544. did you recmod 23544 the exact same way as you did the newer ones that didnt work? if your rom gets stuck on radio screen and the screen doesnt dim after a lil bit then you have problem with xip...if the screen does dim it usually means a problem with system. you can use beyond compare to compare the working build to the non-working one, if there is something different you will be able to tell.

twopumpchump said:
then obviously something different has been done with the newer builds you are trying to use that wasnt done with 23544. did you recmod 23544 the exact same way as you did the newer ones that didnt work? if your rom gets stuck on radio screen and the screen doesnt dim after a lil bit then you have problem with xip...if the screen does dim it usually means a problem with system. you can use beyond compare to compare the working build to the non-working one, if there is something different you will be able to tell.
Click to expand...
Click to collapse
yes screen does not dim..
so what is your suggestion??

Then XIP(MSXIPKernel) is probably the cause.
Did you try a different XIP or a combination of XIP(MSXIPKernel) 23544 and SYS 23548 as I told you before?
From where did you get the 23548-49-52 builds?
Maybe you should download them again?
Best Regards!

saurabh88 said:
yes screen does not dim..
so what is your suggestion??
Click to expand...
Click to collapse
thats why i asked if you have hidden and system files showing on your pc...maybe you left some files/dsm/rgu out of msxipkernel.

kokotas said:
Then XIP(MSXIPKernel) is probably the cause.
Did you try a different XIP or a combination of XIP(MSXIPKernel) 23544 and SYS 23548 as I told you before?
From where did you get the 23548-49-52 builds?
Maybe you should download them again?
Best Regards!
Click to expand...
Click to collapse
yes did it but no luck.....
i download them from da_g thread..
if u can plz give me the link of them to dwnld again

twopumpchump said:
thats why i asked if you have hidden and system files showing on your pc...maybe you left some files/dsm/rgu out of msxipkernel.
Click to expand...
Click to collapse
ok i will compare them and see.l

saurabh88 said:
yes did it but no luck.....
i download them from da_g thread..
if u can plz give me the link of them to dwnld again
Click to expand...
Click to collapse
Have you tried the 23554 that I posted (It is in my Rollups folder, link can be found in NRGZ sticky in this forum)

build log of 23554
still stuck at smart mobility,,,here i attached file plz someone look at it and help me...
i have just sorted them through dump sorter..

Saurabh: see also this post by twopumpchump: http://forum.xda-developers.com/showpost.php?p=6032341&postcount=14

Cooking Sense 2.5

Hey guys, could use a little help. I've been trying to cook a ROM for the Rhodium using osKitchen.
I've been able to cook a basic rom from the stock USCC rom using WM6.5 build 23541.
However, I can't seem to get sense 2.5 to work. I've tried multiple ext packages from different sources, and either a) Sense doesn't show up at all (goes straight to Titanium and Sense is not an option in the Today Items menu) or b) Sense gets stuck at the "Tap here to launch sense"/"Launching HTC Sense."
Sense 2.1 from the stock rom works (except it is misaligned vertically on the screen). Is there something special that needs doing to get 2.5 to work?
Any help is appreciated!

vicbush said:
Hey guys, could use a little help. I've been trying to cook a ROM for the Rhodium using osKitchen.
I've been able to cook a basic rom from the stock USCC rom using WM6.5 build 23541.
However, I can't seem to get sense 2.5 to work. I've tried multiple ext packages from different sources, and either a) Sense doesn't show up at all (goes straight to Titanium and Sense is not an option in the Today Items menu) or b) Sense gets stuck at the "Tap here to launch sense"/"Launching HTC Sense."
Sense 2.1 from the stock rom works (except it is misaligned vertically on the screen). Is there something special that needs doing to get 2.5 to work?
Any help is appreciated!
Click to expand...
Click to collapse
Hi, I have this problem too but on X1 and i aksed question herelink
I think the answers maybe help you

Do you have all info from initflashfiles.dat? Manila XML files needs to placed in ManilaXML folder. Make sure you have that info as app.dat or in your initflashfiles.dat.

Thank you both for your help, I think you've got me in the right direction now!

ai6908 said:
Do you have all info from initflashfiles.dat? Manila XML files needs to placed in ManilaXML folder. Make sure you have that info as app.dat or in your initflashfiles.dat.
Click to expand...
Click to collapse
wait... if you create an app.dat you don't need to amend your initflashfiles.dat?

titan427m said:
wait... if you create an app.dat you don't need to amend your initflashfiles.dat?
Click to expand...
Click to collapse
Yep, i think this is the easiest way to go. In my manila folder i have an "Manila_XXX" folder with an app.dat and some edited manila files. If i change any packages in my manila folder, i just update the "Manila_XXX".

(Solved) QuickGPS not updating

hi guys,
i have a problem with quickgps.
It doesnt update. When i try to update it says
DATA ACTIVATION FAILED
Location settings must be on so that downloading satelites can be used to speed up GPS startup time
I have tried several packages but none of them worked.
i have searched a lot but nothing helps
Everything else is working fine only this little isseu is driving me mad
thx for the help
edit i have atached the reg file what i have for quickgps
EDIT :
the reason was Boot_Launcher.
If you guys want to use Quick Gps include Boot_Launcher

If you don't provide some info of what kitchen you use/what base you use/which build, there is no one who can help you I ques.
Grtz Leo

Laurentius26 said:
If you don't provide some info of what kitchen you use/what base you use/which build, there is no one who can help you I ques.
Grtz Leo
Click to expand...
Click to collapse
well i use Os kitchen and EVK
i use the com2 branch (21898) same thing in com5
It doesnt matter which build i use, I have the same problem with quick gps
I have read somewhere it is related to the oem packages?
I have tried it with different manila packs like from rhodium an hd2 2.07 2.10
last but not least i have used as base the latest oem drivers from HD (1)
thx for the reply

I actually just had the issue-it was because I was testing out removing things from the startup queue to get faster reboots, and I removed bootlauncher, mainly to kill startkey.exe and sipgt_app, because I use FNKBD. Anyway, I overlooked the fact that bootlauncher also kick-starts some services (some totally effing useless, like usb2pcpopup). Among the services is gpsaux.dll-make sure it's loaded. If it isn't, the download doesn't work.

Sorry mate but that's what I'm asking, 'which base are you using OEM/EXT'.
Maybe a packages list would be wise if you made a hybrid rom I'm just quesing
rambo12345 said:
well i use Os kitchen and EVK
i use the com2 branch (21898) same thing in com5
It doesnt matter which build i use, I have the same problem with quick gps
I have read somewhere it is related to the oem packages?
I have tried it with different manila packs like from rhodium an hd2 2.07 2.10
last but not least i have used as base the latest oem drivers from HD (1)
thx for the reply
Click to expand...
Click to collapse

Farmer Ted said:
I actually just had the issue-it was because I was testing out removing things from the startup queue to get faster reboots, and I removed bootlauncher, mainly to kill startkey.exe and sipgt_app, because I use FNKBD. Anyway, I overlooked the fact that bootlauncher also kick-starts some services (some totally effing useless, like usb2pcpopup). Among the services is gpsaux.dll-make sure it's loaded. If it isn't, the download doesn't work.
Click to expand...
Click to collapse
that could be the problem because i have removed some of the startup queue
i will look in that
thx
Sorry mate but that's what I'm asking, 'which base are you using OEM/EXT'.
Maybe a packages list would be wise if you made a hybrid rom I'm just quesing
Click to expand...
Click to collapse
i use leo 2.10 packages as ext and http://forum.xda-developers.com/showthread.php?t=466040 as mine Oem
thx
edit: attached build log

Looking at your buildlog I would try to downgrade the commmanager as well to a Blackstone compatible one.
rambo12345 said:
i use leo 2.10 packages as ext and http://forum.xda-developers.com/showthread.php?t=466040 as mine Oem
thx
edit: attached build log
Click to expand...
Click to collapse

Since i have had the same problem with Kaiser and Mega EXT packages,never had QuickGps working, how can be the communication manager involved in this such a problem?
Laurentius26 said:
Looking at your buildlog I would try to downgrade the commmanager as well to a Blackstone compatible one.
Click to expand...
Click to collapse

Hi,
Because it has several components for Internet and bandswitching and Quickgps can only do a upgrade if your Internet connection is working 100%.
If you check the dlls/exe in commmanager it has a lot of dependencies.
ril.dll
dnsapi.dll
iphlapi.dll
to name a view.
Not that I'm such a expert but these dlls could affect Quickgps if you ask me.
af974 said:
Since i have had the same problem with Kaiser and Mega EXT packages,never had QuickGps working, how can be the communication manager involved in this such a problem?
Click to expand...
Click to collapse

Yes of course, but the error gotten is "Enable to retrieve data , location service must be on"....i switched to the old QuickGps and it works.....i guess ill go to check some dependency.
Laurentius26 said:
Hi,
Because it has several components for Internet and bandswitching and Quickgps can only do a upgrade if your Internet connection is working 100%.
Click to expand...
Click to collapse

Sorry added some extra to my previous post.
af974 said:
Yes of course, but the error gotten is "Enable to retrieve data , location service must be on"....i switched to the old QuickGps and it works.....i guess ill go to check some dependency.
Click to expand...
Click to collapse

Mostly QuickGps.exe dependency are into Shared_Modules but i cant find a dll into the dump folder IESHIMS.DLL, using depends Walker though.

I know most people like to use the latest packages but sometimes it's good to dowgrade certain components so they suite better to your oemdrivers.
A componont like commmanager is trivial in this case.

af974 said:
Yes of course, but the error gotten is "Enable to retrieve data , location service must be on"....i switched to the old QuickGps and it works.....i guess ill go to check some dependency.
Click to expand...
Click to collapse
try changing this reg in mega pkg to dword:00000001
Code:
"EnableInitData"=dword:00000000

Laurentius26 said:
I know most people like to use the latest packages but sometimes it's good to dowgrade certain components so they suite better to your oemdrivers.
A componont like commmanager is trivial in this case.
Click to expand...
Click to collapse
I'd like to adopt this post as my own.

Yes you are right, indeed i gave up with new QuickGps but honestly i feel good if i can find a solution to let it work .
Laurentius26 said:
I know most people like to use the latest packages but sometimes it's good to dowgrade certain components so they suite better to your oemdrivers.
A componont like commmanager is trivial in this case.
Click to expand...
Click to collapse
Thanks Shane im going to try it ....just need to cook it again.ill let yoknow later if it work.
twopumpchump said:
try changing this reg in mega pkg to dword:00000001
Code:
"EnableInitData"=dword:00000000
Click to expand...
Click to collapse

Unfortunaly no luck with that reg key,still getting same error.
I would try to change CommManager but damn the old one for Kaiser its so ugly

Haha.. well you can try first and see if QuickGPS works.
What Commmanager are you using btw, a converted 2.10 WVGA to QVGA?
af974 said:
Unfortunaly no luck with that reg key,still getting same error.
I would try to change CommManager but damn the old one for Kaiser its so ugly
Click to expand...
Click to collapse

Ehehe...yup just for try if QuickGps work otherwise i will delete
Im using the Original from Mega Touch 2.
Laurentius26 said:
Haha.. well you can try first and see if QuickGPS works.
What Commmanager are you using btw, a converted 2.10 WVGA to QVGA?
Click to expand...
Click to collapse

Man it's just wild quesing as I don't know your kitchen LoL.
Maybe you need to downgrade Quickgps and the depended packages as well.
Best advise I can give is to keep everything from the same source close to your device specs and upgrade packages one by one and see yourself if everything functions.
Sorry old boring story but that's how I work testing many times.
af974 said:
Ehehe...yup just for try if QuickGps work otherwise i will delete
Im using the Original from Mega Touch 2.
Click to expand...
Click to collapse

[Q] how to cook sense?

I apologize if this has been covered, but I can't find specific info with my search terms.
I'm cooking for Rhodium, WVGA, WM 6.5.x sys 21682. My base ROM is ATT's stock august 30th 2010 ROM. Using OSKitchen Zero, latest release.
Basically, I can't get any version of sense to work. I've tried cooking 2016, 2018, and 2019, and can't get any of them to work. The problem is that when I try to import the EXT packages with OSKZ, I get an error stating: "The OEM package you've selected doesn't seem to be valid..."
So, I thought maybe it was just being strange. So I placed the packages manually into the kitchen and tried to build the ROM and platform builder would hang and I'd have to cancel the process.
Any tips tricks or ideas?
Thanks a lot!
Smith

Where are you sourcing your sense files from?
Have you got the additional dependencies covered (ie starticonloader?)

crazyC said:
Where are you sourcing your sense files from?
Have you got the additional dependencies covered (ie starticonloader?)
Click to expand...
Click to collapse
I'm not sure what you mean by sourcing exactly, but on my PC they're located on my desktop, and I've also tried placing them straight into my kitchen without using the GUI to do it.
I got the files from a post here on XDA.
Yeah, I believe I have all the additional dependencies as well.
I've been reading and it looks like I have to modify the app.dat file and some other files?
Regards
Smith

smithisize said:
I'm not sure what you mean by sourcing exactly, but on my PC they're located on my desktop, and I've also tried placing them straight into my kitchen without using the GUI to do it.
I got the files from a post here on XDA.
Yeah, I believe I have all the additional dependencies as well.
I've been reading and it looks like I have to modify the app.dat file and some other files?
Regards
Smith
Click to expand...
Click to collapse
OK so you got them from XDA - as I am assuming you are not using the At&T standard ones. (that was what I meant).
The ones I got from XDA were already CFC'd and were already in EXT format not OEM and so did not need any importing as such, just copying into the directory.
I did not need to modify anything - cannot remember the thread I got them from tho.
I will try and have a look, but my kitchen is now such an amalgamation of packages that I couldn't be sure where it all came from.

Ahhhh ok, i was confused because it says's import, ext package then it asks for an oem location.
Ok, with that cleared up, place straight into kitchen, gotcha. How many dependencies are there, can you recall? I think i have them all but I want to make sure.
Thanks a lot!
Regards
Smith
Edit:
No go, but here's the error (attached in the pic)

You've got files inside of modules. You need to clean your modules up.

Farmer Ted said:
You've got files inside of modules. You need to clean your modules up.
Click to expand...
Click to collapse
Alright, is there any reading I could do to help me figure out what to clean and what to keep?
Thanks
Smith

Try looking inside the corrupt modules, then look in some clean ones, and figure out what doesn't belong. It should be obvious.
Someone else is just going to tell you the answer, but you're better off figuring it out yourself.

Farmer Ted said:
Someone else is just going to tell you the answer, but you're better off figuring it out yourself.
Click to expand...
Click to collapse
Couldn't agree more. I'll check it out.
Thanks for the info, much appreciated!
Regards
Smith
Edit: one last question. It's killing me finding all the WVGA dependencies for this package, they're all vga is appears. This is what I'm using: http://forum.xda-developers.com/showthread.php?t=797602
and when it lists the "required packages" when I download it it's labled VGA, not WVGA, and I think that'll be a problem. Will it?

Right, cooking sense is not my strongest point so I will probably leave it to others to take it further, but
Modules vs files - you need one or the other I think. Look up recmod and reversemod.
I just used a set of Manila files uploaded and CFC'd by someone from the latest official LEO ROM.(By Patensas I think) and maybe updated the HTC framework as well.

crazyC said:
Right, cooking sense is not my strongest point so I will probably leave it to others to take it further, but
Modules vs files - you need one or the other I think. Look up recmod and reversemod.
I just used a set of Manila files uploaded and CFC'd by someone from the latest official LEO ROM.(By Patensas I think) and maybe updated the HTC framework as well.
Click to expand...
Click to collapse
Alright, so I've figured out which packages I need to recmod and have done so. I haven't found those leo files yet, but I'm looking. Just got home. I'll post back when I see how that goes!
Regards
Smith

I have never had to recmod any of the sense files.
What you need to do is delete the files (ie the .dll) within the module. The kitchen will use the module to create the file on the device, it does not need the file as well. Hence the kitchen is giving the warning.
I think.

Hi, just re read your first post.
Could you confirm you have done the following:
Dumped the ATT base rom and rebuilt using just that with the EXTs that came from it, flashed it, and checked it worked? (So you should have had a working Sense in that) as per the Oskitchen instruction set?
If there have been problems with that, try ticking the box next to recmod on the Phone Canvas Enhancement package. I think there was an issue with the ATT ROM around this.

crazyC said:
Hi, just re read your first post.
Could you confirm you have done the following:
Dumped the ATT base rom and rebuilt using just that with the EXTs that came from it, flashed it, and checked it worked? (So you should have had a working Sense in that) as per the Oskitchen instruction set?
If there have been problems with that, try ticking the box next to recmod on the Phone Canvas Enhancement package. I think there was an issue with the ATT ROM around this.
Click to expand...
Click to collapse
Yeah, I did that. Here's the weird part though. That worked the first time. But after having all these difficulties, seeing as I haven't made much real progress, I rebuilt my kitchen. Then it wouldn't work. I would get the exact same runtime error, eventhough it worked before and I've installed all the libraries.
So, as of now the problem lies somewhere with my kitchen. I'm trying to troubleshoot it right now.
Any ideas as to why that might be? I've tried the FAQ's in the OSK thread and haven't fixed the problem :/
Regards
Smith

No sorry.
I had some kitchen problems when upgrading from oskitchen 1.32 (tried to completely reorganise my EXTs at the same time and it went horribly wrong), so went back to 1.32 to sort it out and will upgrade in due course.
If platform rebuilder crashes during the build then you dont need to waste time flashing.
Disable all EXTs and build and then add them in blocks till you identify what is causing the crash.
If it crashes with no EXTs then try the original sys, and if no joy reimport the rom?
Are all the recommended packages ticked for Recmod?

smithisize said:
Alright, so I've figured out which packages I need to recmod and have done so. I haven't found those leo files yet, but I'm looking. Just got home. I'll post back when I see how that goes!
Click to expand...
Click to collapse
I can't help you on Sense, as I don't use it, but why would you recmod anything? That's a bad idea. If you have a 6.5 kernel, use it.

crazyC said:
No sorry.
I had some kitchen problems when upgrading from oskitchen 1.32 (tried to completely reorganise my EXTs at the same time and it went horribly wrong), so went back to 1.32 to sort it out and will upgrade in due course.
If platform rebuilder crashes during the build then you dont need to waste time flashing.
Disable all EXTs and build and then add them in blocks till you identify what is causing the crash.
If it crashes with no EXTs then try the original sys, and if no joy reimport the rom?
Are all the recommended packages ticked for Recmod?
Click to expand...
Click to collapse
Actually recmodding ATT Phone Canvas fixed the problem.
I was able to generate the ROM image with sense 2017 cooked in, but sense won't launch now. "Tap to Start Sense" so I'm double checking dependencies, exe and dll files as we speak.
Thanks a lot for all the help!
Regards
Smith

So i got sense 2017 to at least load. now, however, none of the softkeys work, and tapping on a message in the message tab doesn't work.
So far so good. lots of learning to do yet, but I'll get there.
Thanks a lot for al the info!
Regards
Smith

Alright, I can't get sense to work again lol. It just kinda stopped, eventhough I'm using the same packages for manila and its dependencies.
Any ideas?
Regards
Smith

Does anyone know how to cook sense with old kitchen style(build os) for Omnia II?
Thanks in advance

[Q] How update kernel

Hey everybody,
I'm cooking a WM6.5.x ROM for HTC Touch Pro / Fuze / Raphael (you call it how you like it). I'm using WM build 23699. Everything is fine, that's no problem But I have a question related to the kernel. I have not updated the kernel, so I only have slot 0 and 1. But are there much advances on updating my kernel to the 'native' one? And where can I find it? And how should I do it?
Thanks in advance!
MadMatt

The advantage to have a native 6.5 Kernel is that you will have a more smooth rom because you will not need to recmode any module thrn the standard for having a booting rom (Ntconfig.dll).
I dont know if it does exist for your phone but you must search for it in its thread,you need to search for Nk.exe.Once you will find it just replace it with the old one in OEMXIPKernel.

af974 said:
The advantage to have a native 6.5 Kernel is that you will have a more smooth rom because you will not need to recmode any module thrn the standard for having a booting rom (Ntconfig.dll).
I dont know if it does exist for your phone but you must search for it in its thread,you need to search for Nk.exe.Once you will find it just replace it with the old one in OEMXIPKernel.
Click to expand...
Click to collapse
The NK.exe is the only thing you need? And is it possible that it is the same as the one from the HTC Diamond? (as the only difference between those two is the keyboard)

Yes ,only nk.exe you need and i doubt that Nk.exe from another device should works.
_Madmatt said:
The NK.exe is the only thing you need? And is it possible that it is the same as the one from the HTC Diamond? (as the only difference between those two is the keyboard)
Click to expand...
Click to collapse

af974 said:
Yes ,only nk.exe you need and i doubt that Nk.exe from another device should works.
Click to expand...
Click to collapse
Okay, I'll search for the NK.exe. And OsKitchen will automatically detect that it is a newer kernel than?

If you will replace the old kernel then OsKitchen will does all the process automatically.
_Madmatt said:
Okay, I'll search for the NK.exe. And OsKitchen will automatically detect that it is a newer kernel than?
Click to expand...
Click to collapse

Good lord, update the kernel!!! There's one posted in the native kernel thread.
Here's the one I've been using. I think it's the latest. Just swap it into your xip folder and you'll be good to go. And quit recmodding!!!

Farmer Ted said:
Good lord, update the kernel!!! There's one posted in the native kernel thread.
Here's the one I've been using. I think it's the latest. Just swap it into your xip folder and you'll be good to go. And quit recmodding!!!
Click to expand...
Click to collapse
Thanks, will I need to update OEMDrivers too? Because I read that sometimes that is needed too And will I be able to un-RecMod everything after updating the kernel?

Look for one of Da_G's kitchens (23016 was the last full one). It has the oem. But the drivers are all the same. I use drivers from the Orange/20779 final raphael rom. Convert all the drivers to modules.

Farmer Ted said:
Look for one of Da_G's kitchens (23016 was the last full one). It has the oem. But the drivers are all the same. I use drivers from the Orange/20779 final raphael rom. Convert all the drivers to modules.
Click to expand...
Click to collapse
Didn't understand what you are saying here So I need all the OEM packages execpt the OEMDrivers? The OEM packages I have right now are those from the RUU_Raphael_HTC_WWE_5.05.405.1_R_Radio_Signed_Raphael_52.58.25.30_1.11.25.01_Ship.exe
Are that good ones too? Convert all drivers to modules? What do you mean by this? Convert the OEMDrivers in the OEM tab to EXT packages? (Using osKitchen)

Sorry, all you need is the 20779 or 20771 oem. But if you don't want to dump it yourself, get Da_G's kitchen, which is cleaned up a bit. The drivers aren't 6.5-specific. You should convert them all to modules, though.

Farmer Ted said:
Sorry, all you need is the 20779 or 20771 oem. But if you don't want to dump it yourself, get Da_G's kitchen, which is cleaned up a bit. The drivers aren't 6.5-specific. You should convert them all to modules, though.
Click to expand...
Click to collapse
Allright, if the drivers aren't 6.5 specific, then I can just convert my drivers I have now to EXT-packages?

_Madmatt said:
Allright, if the drivers aren't 6.5 specific, then I can just convert my drivers I have now to EXT-packages?
Click to expand...
Click to collapse
Why convert them to EXT's? Just leave them in your OEM Drivers folder. And convert them to modules.

Farmer Ted said:
Why convert them to EXT's? Just leave them in your OEM Drivers folder. And convert them to modules.
Click to expand...
Click to collapse
Okay. and how do I do that in osKitchen? This is my first kernel update

I don't use that kitchen, but if it doesn't have module creation built-in, get reversemod.exe and manually do the conversion by dragging and dropping the files onto the exe. You should do all the oem driver dll's (they get loaded at startup, anyway, and this will save some virtual memory).