Database Users

Help with 23112 port for the Blue Angel

I posted a thread asking for help on cooking for older devices, but no one seemed to have an answer for it. I figured I would give this thing another shot and the device gets past the first screen, but it never gets out of the second boot splash. I have attached the kitchen that I am using with SYS already ported.
Without further ado, here is my attempt to a kitchen (based off on sun_dream's 28230 kitchen)
http://hotfile.com/dl/36427122/da04c1f/HTC_BlueAngel_WM6.5.3_23112.rar.html
Any help will be appreciated!

did you recmod any of the files in sys? or ext? ive never cooked for blue angel but im sure it doesnt have a native 6.5 nk.exe and that means you need to recmod some files for kaiser i always recmodded my whole ext folder, and all modules in browsing, browsingcore, browsingie...give that a try and see if it helps

twopumpchump said:
did you recmod any of the files in sys? or ext? ive never cooked for blue angel but im sure it doesnt have a native 6.5 nk.exe and that means you need to recmod some files for kaiser i always recmodded my whole ext folder, and all modules in browsing, browsingcore, browsingie...give that a try and see if it helps
Click to expand...
Click to collapse
Hey twopump,
I tried recmodding the modules that you described there (which I also saw on another thread that you replied to). As far as the ones in the EXT folder (my kitchen has a OEM folder, which I think is the same), they were all recmodded by sun_dream. BTW, you are absolutely correct about the BA not having a native 6.5 nk.exe.... that is usually the downfall of a 5 year old device , but I know that it can be done since there are newish roms out there for the BA (28230 being one of them).
There is no way you can look at my kitchen and tell me what's wrong is there, is there? (I guess the answer is no, but it is always worth asking).
Thanks for the help.

ok i took a look at your kitchen, and im pretty sure i know whats wrong. the first thing i did was open up your sys folder to check if you had recmodded browsing, browsingie, browsingcore, and you hadnt they all still had the modules in them....except you didnt even have browsingie in your rom only the 0409 pkg lol. then i noticed that you deleted the netcf pkg from sys as well, that will cause your rom not to boot. here is my solution to your problems, start over with a fresh complete sys, only delete the things that arent needed, then convert every module in browsing, browsingcore, browsingie to a file. make sure you have netcf and cook you should have a booting rom

twopumpchump said:
ok i took a look at your kitchen, and im pretty sure i know whats wrong. the first thing i did was open up your sys folder to check if you had recmodded browsing, browsingie, browsingcore, and you hadnt they all still had the modules in them....except you didnt even have browsingie in your rom only the 0409 pkg lol. then i noticed that you deleted the netcf pkg from sys as well, that will cause your rom not to boot. here is my solution to your problems, start over with a fresh complete sys, only delete the things that arent needed, then convert every module in browsing, browsingcore, browsingie to a file. make sure you have netcf and cook you should have a booting rom
Click to expand...
Click to collapse
Thanks for the advice. I honestly cannot put browsingie and netcf at the same time simply because the BA only has 32 mb for rom and the kitchen essentially errors out before getting to the end. The other issue is that the rom will not even boot if I take either one of them out. I did recmod all that you suggested, but still nothing...

egzthunder1 said:
Thanks for the advice. I honestly cannot put browsingie and netcf at the same time simply because the BA only has 32 mb for rom and the kitchen essentially errors out before getting to the end. The other issue is that the rom will not even boot if I take either one of them out. I did recmod all that you suggested, but still nothing...
Click to expand...
Click to collapse
can I be of some help?if I get u correctly u want to cook a rom OS 23112 for blue angel.right ?if so must one use the kitchen u have posted?or any kitchen ?
regards

deepankerjha said:
can I be of some help?if I get u correctly u want to cook a rom OS 23112 for blue angel.right ?if so must one use the kitchen u have posted?or any kitchen ?
regards
Click to expand...
Click to collapse
I would appreciate all the help that I can get . The kitchen that I posted is a modified version of a 28230 kitchen by sun_dream. Basically, I ported the XIP and the SYS folders from 23112 into the 28230 kitchen. Originally, I had included the same exact components in the SYS that sun_dream had included in his kitchen (his is fully functional btw), so I am at the point where I am running out of ideas on what I could be doing wrong. I know that you cook for the Nike, so the way of cooking will be completely different, but some of the core knowledge is still the same. Any suggestions are welcome

egzthunder1 said:
I would appreciate all the help that I can get . The kitchen that I posted is a modified version of a 28230 kitchen by sun_dream. Basically, I ported the XIP and the SYS folders from 23112 into the 28230 kitchen. Originally, I had included the same exact components in the SYS that sun_dream had included in his kitchen (his is fully functional btw), so I am at the point where I am running out of ideas on what I could be doing wrong. I know that you cook for the Nike, so the way of cooking will be completely different, but some of the core knowledge is still the same. Any suggestions are welcome
Click to expand...
Click to collapse
well mate we can ddo two things. I can give u my sys/common folder of 23112 and u can try that .i have cooked with 23112 for nike and neon both.
2nd u will have to provide me the stock rom so that I can give a try using my kitchen to cook for u .
btw which kitchen is posted in ur link
regards

deepankerjha said:
well mate we can ddo two things. I can give u my sys/common folder of 23112 and u can try that .i have cooked with 23112 for nike and neon both.
2nd u will have to provide me the stock rom so that I can give a try using my kitchen to cook for u .
btw which kitchen is posted in ur link
regards
Click to expand...
Click to collapse
Original kitchen by sun_dream here
My modified kitchen is the one posted above
Link for the stock rom can be found here
I will certainly appreciate any help I can get

egzthunder1 said:
Original kitchen by sun_dream here
My modified kitchen is the one posted above
Link for the stock rom can be found here[/ucouldn'trl]
I will certainly appreciate any help I can get
Click to expand...
Click to collapse
sorry,u didn't get me,or I couldnt put right words.is that evk kitchen or some other.2ndly would u like to try my sys 23112 ?

deepankerjha said:
sorry,u didn't get me,or I couldnt put right words.is that evk kitchen or some other.2ndly would u like to try my sys 23112 ?
Click to expand...
Click to collapse
No, these are "old style kitchens" I am pretty sure that EVK will not work with these kind of roms (they are of the nbf type and not nbh). If you would like to send me your SYS, I would not mind taking it for a spin.

egzthunder1 said:
No, these are "old style kitchens" I am pretty sure that EVK will not work with these kind of roms (they are of the nbf type and not nbh). If you would like to send me your SYS, I would not mind taking it for a spin.
Click to expand...
Click to collapse
ok I will upload the common folder for u once I am home,say within an hr

deepankerjha said:
ok I will upload the common folder for u once I am home,say within an hr
Click to expand...
Click to collapse
Thank you. I will post my findings after I test it.

egzthunder1 said:
Thank you. I will post my findings after I test it.
Click to expand...
Click to collapse
sorry for being late 23112

I would give atry to Recmod all EXT packages as TPC said.
Your FWUPDATE and SQM in sys folder are dummy or M$ originals?
You need absolutly Net and Browsingie as TPC said ,at least delete some useless apps in OEM packages.
I made a 23112 SYS within only the needed and already recmoded plus the dummy fwupdate and sqm, you must put them in an EXT folder or convert them in OEM.
http://www.4shared.com/file/7miAPvVw/SYS_XIP_DUMMY_23112.html

af974 said:
I would give atry to Recmod all EXT packages as TPC said.
Your FWUPDATE and SQM in sys folder are dummy or M$ originals?
You need absolutly Net and Browsingie as TPC said ,at least delete some useless apps in OEM packages.
I made a 23112 SYS within only the needed and already recmoded plus the dummy fwupdate and sqm, you must put them in an EXT folder or convert them in OEM.
http://www.4shared.com/file/7miAPvVw/SYS_XIP_DUMMY_23112.html
Click to expand...
Click to collapse
I believe I have the real FW and SQM folders in there. It is truly weird though, if you take a look at the original sys folder of the 28230 kitchen, sun_dream has no netcf nor browsingie in there, and he has no recmodded files in the browsing folders either, yet his kitchen spits out a working rom...
At this point, I am beginning to think that my xip might be bad...

egzthunder1 said:
I believe I have the real FW and SQM folders in there. It is truly weird though, if you take a look at the original sys folder of the 28230 kitchen, sun_dream has no netcf nor browsingie in there, and he has no recmodded files in the browsing folders either, yet his kitchen spits out a working rom...
At this point, I am beginning to think that my xip might be bad...
Click to expand...
Click to collapse
You dont need netcf to build a ROM. Ofcourse most of our programs these days wont run unless you install it after...
I do agree that it doesnt make sense...

ai6908 said:
You dont need netcf to build a ROM. Ofcourse most of our programs these days wont run unless you install it after...
I do agree that it doesnt make sense...
Click to expand...
Click to collapse
NetCF can be installed post flash either by hand or some customization method (sdcustomization, uc, sashimi, etc)
Let me go a little deeper into the world of the BA. The process is pretty much the same as it is with all devices... flash a rom, hard reset, and reboot. Depending on the packages that I am adding to the SYS, the rom will either get stuck while hard resetting (which is the same as getting stuck in the tri-colored screen (keep in mind that for the BA, the tri-colored screen is *not* bootloader, but the first bootsplash)), or will go through the first screen and get stuck in the second bootsplash (here is the kicker, if you connect the device to a computer, Activesync will see it and try to connect, which means that some of the windows OS components are loading...)
I am finishing charging up my BA and I will flash deep's SYS and will let you all know what comes out of it

If I look in your common folder I see Chome is still in, that's a huge memory eater, not sure what you are cooking and if you need it.
Another thing; if I take out NETCF in my rom device setup starts looping in a continue circle and I get a warning about AutoVer.exe.
I hope this is of any help.
egzthunder1 said:
NetCF can be installed post flash either by hand or some customization method (sdcustomization, uc, sashimi, etc)
Let me go a little deeper into the world of the BA. The process is pretty much the same as it is with all devices... flash a rom, hard reset, and reboot. Depending on the packages that I am adding to the SYS, the rom will either get stuck while hard resetting (which is the same as getting stuck in the tri-colored screen (keep in mind that for the BA, the tri-colored screen is *not* bootloader, but the first bootsplash)), or will go through the first screen and get stuck in the second bootsplash (here is the kicker, if you connect the device to a computer, Activesync will see it and try to connect, which means that some of the windows OS components are loading...)
I am finishing charging up my BA and I will flash deep's SYS and will let you all know what comes out of it
Click to expand...
Click to collapse

deepankerjha said:
sorry for being late 23112
Click to expand...
Click to collapse
Thanks... I tried it but no dice I ran out of space (the BA only has 32 MB available for the ROM)

How to update SYS

Here is a very very n0000000000000000b question for Chef Central, sorry if I annoy the masters .
I have Installed EVK 1.8.2 as well as osKithcen 1.25 and also dumped HTC Asia ROM (official) for my Touch2 T3320 its 21854 Build.
Now I want to make a ROM with a new build, so I have downloaded
SYS_23638_XIP.rar
SYS_23638_Common.rar
SYS_23638_96DPI_0409.rar
Click to expand...
Click to collapse
After unzipping the files, how should I incorporate them into my ROM using EVK (or osKitchen).
P.S. Please do not go by my number of posts, most of them were used in appreciating the great work from chefs of Vox & Gene.
Help please

well...
this is not for gene or vogue or whatever... is for hermes but as an examnple to know wich pkgs goes where?? you can take a look in this pictures of this tutorial hope it can helps you the info is kinda old thats why I told you just see the pics...
http://forum.xda-developers.com/showthread.php?t=533423
And i know its not your languaje but take a look at this videos you will se the estructure perfectly for the EVK
part 1 http://www.youtube.com/user/moonspell83?feature=mhw5#p/u/12/wt5rdOrQ9_Y
part 2 http://www.youtube.com/user/moonspell83?feature=mhw5#p/u/11/724u0LKhvfo
part 3 http://www.youtube.com/user/moonspell83?feature=mhw5#p/u/10/j7FeQ7YFgP4
part 4 http://www.youtube.com/user/moonspell83?feature=mhw5#p/u/9/5uYye3uShSM
Any questions.. here please

+ Que PPC said:
well...
this is not for gene or vogue or whatever.......
Click to expand...
Click to collapse
Thanks a lot! You are really really very helpful .
Will have a look.... and bug you again

Yes no prob thats why i made that tutorials but because my english spoken is toooooo baaaaad i just do the videos in my native spanish lang

Where to find newer sys builds? I downloaded one from htcpedia, but its .dio file. Don't know what do do with it
EDIT:
Found it in Da_G's thread, just need to start from the last page .

here in the same sub forum http://forum.xda-developers.com/showthread.php?t=650783

ceesheim said:
here in the same sub forum http://forum.xda-developers.com/showthread.php?t=650783
Click to expand...
Click to collapse
I guess they are not compatible with OSKitchen, I tried one of them using Import Sys option, and it said that it is not a valid dump to parse.
Any idea ?

OsKitchen? are you in oskitchen or ervius?
.dio file needs to be dumped with Xidump tool search there on the Da_G thread there are so many tools to dump .dio files

Addicted2xda said:
I guess they are not compatible with OSKitchen, I tried one of them using Import Sys option, and it said that it is not a valid dump to parse.
Any idea ?
Click to expand...
Click to collapse
i think the OS kitchen import build feature is designed for the "rollup" builds...all pkgs inside a single folder. the ones you tried are divided into language, dpi, ect for ervius visual kitchen. all you have to do is open each of those folders and copy/paste all of them into one single folder, then run the import on OS kitchen i think it should work.

Are you in Erivius Kitchen or OS Kitchen
Click to expand...
Click to collapse
Well I have downloaded both, since I am new to this stuff.. want to check out both. And will ultimately adapt to the one which I am more comfortable with (i.e. get more help on )
Now I have downloaded these three files
21898_Rollup_All_Packages.7z
21898_XIP.BIN_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409_041D_0414.7z
21898_XIP.BIN_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409_0419.7z
Click to expand...
Click to collapse
from Da_G's thread
Now here is what I did:
1. Unzipped all the files in a single folder named 21898 , it had two folders SYS and XIP.
2. Copied the SYS folder under EVK and renamed it to 21898.
3. Copied the content of the XIP folder to "C:\Ervius\Tools\xip.bin_new"
Now the problem is when I am trying to cook a ROM with this (Oh that kitchen is based on WM 6.5 Stock ROM (WWE ASIA) for Mega, it stops saying that I am using 6.1 NK.exe with 6.5 XIP and since the number of modules are too many, it will make an unbootable ROM. But I guess WM 6.5 have 6.5 nk.exe?
Where did I do wrong?
EDIT:
Even after deleting the existing kitchen and re dumping the stock wwe asia ROM, it is still saying that nk.exe is of 6.1!

Addicted2xda said:
Are you in Erivius Kitchen or OS Kitchen
Well I have downloaded both, since I am new to this stuff.. want to check out both. And will ultimately adapt to the one which I am more comfortable with (i.e. get more help on )
Now I have downloaded these three files
from http://forum.xda-developers.com/report.php?p=6017583
Now here is what I did:
1. Unzipped all the files in a single folder named 21898 , it had two folders SYS and XIP.
2. Copied the SYS folder under EVK and renamed it to 21898.
3. Copied the content of the XIP folder to "C:\Ervius\Tools\xip.bin_new"
Noup...
1.- Unzipped all files and put them togheter is just for oskitchen import sys feature... if you want it in EVK style you must to use the packer.jar... is floating arround is friendly to use and easy.
you dont need to modify nothing in Tools folder... dont touch it
From the pkgs you extract you just need to msxipkernel folder... that must be in C:\Ervius\ROM\shared\21898\
Click to expand...
Click to collapse
Now the problem is when I am trying to cook a ROM with this (Oh that kitchen is based on WM 6.5 Stock ROM (WWE ASIA) for Mega, it stops saying that I am using 6.1 NK.exe with 6.5 XIP and since the number of modules are too many, it will make an unbootable ROM. But I guess WM 6.5 have 6.5 nk.exe?
Where did I do wrong?
Click to expand...
Click to collapse
What is your device??? does it has native kernel 6.5???
tell us more about your device and if you can... upload your current EVK to give it a shot
Click to expand...
Click to collapse
Click to expand...
Click to collapse

+ Que PPC said:
Addicted2xda said:
Are you in Erivius Kitchen or OS Kitchen
What is your device??? does it has native kernel 6.5???
tell us more about your device and if you can... upload your current EVK to give it a shot
Click to expand...
Click to collapse
I have Touch2/ Mega T3320 (Not T3333), which have native 6.5 Kernel (it came preloaded with 6.5). The problem is I am constantly travelling ... So I have to use GPRS / Edge for surfing and browsing and ...... Bugging . so you can understand - I won't be able to upload the kitchen. Even to download the SYS etc, it takes me around 5-6 hours! But ... what to do??
EDIT:
I have even deleted the Existing EVK folder and redumped the HTC WWE Asia ROM for Touch2 / Mega but still EVK is telling me that nk is of 6.1!
But osKitchen says its 6.5 (which I guess is right)
Click to expand...
Click to collapse
Click to expand...
Click to collapse

mmm in fact you must to say to the kitchen if is or not a 6.5 in OSK... well... in evk you just need to be sure where to put ROM cause i see you dont know how to arrange the XIP in EVK look in the tutorials

+ Que PPC said:
mmm in fact you must to say to the kitchen if is or not a 6.5 in OSK... well... in evk you just need to be sure where to put ROM cause i see you dont know how to arrange the XIP in EVK look in the tutorials
Click to expand...
Click to collapse
Sorry, I am must be appearing to be lazy, but I am not . At the moment I am downloading the videos from Youtube and will check them out ASAP. Also have saved your tutorial and will take a printout to read it properly. Sorry I can not focus on Monitor .
Will study it tomorrow and revert back for clarifications .

Yeah no prob we know that this is just hobbies... we all had real life to attend firstly

+ Que PPC said:
Yeah no prob we know that this is just hobbies... we all had real life to attend firstly
Click to expand...
Click to collapse
But it is becoming an Addiction

welcome to real XDA and late night and prepared to drink so much coffee

Finally finished your great tutorial... but the thing is even with the stock ROM of Mega as base, EVK says that nk.exe 6.1 and not 6.5.
I simply dumped the Stock ROM and recooked it, no changes nothing. BTW I did got the nbhutil.xml with mega settings though...
Is there any other setting that needs to be changed So that EVK recognizes the nk as a native 6.5???
P.S. clicking on the Native check box does have no effect

i guess it isnt another settings the kitchen reads what you have in the nk.exe
wich build is your Original rom?
is 6.5?

+ Que PPC said:
i guess it isnt another settings the kitchen reads what you have in the nk.exe
wich build is your Original rom?
is 6.5?
Click to expand...
Click to collapse
Yeah, its WM 6.5 ROM,
RUU_Mega_hTC_Asia_WWE_1.28.707.3_Radio_Signed_61.41t.25.31_3.48.25.27_Ship
downloaded from http://forum.xda-developers.com/showthread.php?t=578915
???

[FYI] Things to know when use TMOUS_HD2_2.13 as Base

Is it save to cook a TMOUS 2.13 stock rom for a HD2 WWE??? I would like to use the 2.13 as base... are there things i have to look out for? Here r some tips i got from some helpful people..
millski said:
There's no connectiondb oem or connectionsetup/connectionsetup_wvga packages ext in the 2.13 stock rom, you'll probably want to get those from somewhere else (so that connections are correctly set for other networks on first boot). Also the TMOUS 2.13 operatorpkg is full of TMO theme stuff (boot screen, WM 6.5 tsk, TMO app icons etc). I replaced my operatorpkg with an HTC stock pkg...
Click to expand...
Click to collapse
see attachment.... Load Connectionsetup to EXT and Connectionsetup to OEM... I also copied the lines u find in the app.reg file, paste it in initflashfiles.dat... for sure. i believe that connection setup will be loaded on startup this way, correct me if i'm wrong...
NIKOSXRI said:
.......All externals work fine, but if the touch feeling is not good for you, then just replace the touch.dll and touchgl.dll from stock rom.Then touch is much better and soft.
Click to expand...
Click to collapse
got these attached too..
Look into \OperatorPkg\mxipupdate_oemoperato rs_102.provxml
this provxml sets all 9 quicklinks that comes with TMoUS. You might edit them to set your personal quicklinks right after flash... Thanks tidus18
Thanks for these tips... Tested and working tips r always welcome ofcourse

it is save! nothing to look for

Edited to clarify things...
Solved

Thanx!!.........

There's no connectiondb oem or connectionsetup/connectionsetup_wvga packages ext in the 2.13 stock rom, you'll probably want to get those from somewhere else (so that connections are correctly set for other networks on first boot). Also the TMOUS 2.13 operatorpkg is full of TMO theme stuff (boot screen, WM 6.5 tsk, TMO app icons etc). I replaced my operatorpkg with an HTC stock pkg...

millski said:
There's no connectiondb oem or connectionsetup/connectionsetup_wvga packages ext in the 2.13 stock rom, you'll probably want to get those from somewhere else (so that connections are correctly set for other networks on first boot). Also the TMOUS 2.13 operatorpkg is full of TMO theme stuff (boot screen, WM 6.5 tsk, TMO app icons etc). I replaced my operatorpkg with an HTC stock pkg...
Click to expand...
Click to collapse
Yeah found out after flashing my own rom.... working on it now!

millski said:
There's no connectiondb oem or connectionsetup/connectionsetup_wvga packages ext in the 2.13 stock rom, you'll probably want to get those from somewhere else (so that connections are correctly set for other networks on first boot). Also the TMOUS 2.13 operatorpkg is full of TMO theme stuff (boot screen, WM 6.5 tsk, TMO app icons etc). I replaced my operatorpkg with an HTC stock pkg...
Click to expand...
Click to collapse
You should take the one from stock rom and also you must do changes in the operator package oem, of course, if you dont live in the USA.
You may also have to replace the tmous phcanoverbmp dll in this oem package.I dont know if this dll works because i use my custom dll.
All externals work fine, but if the touch feeling is not good for you, then just replace the touch.dll and touchgl.dll from stock rom.Then touch is much better and soft.

NIKOSXRI said:
You should take the one from stock rom and also you must do changes in the operator package oem, of course, if you dont live in the USA.
You may also have to replace the tmous phcanoverbmp dll in this oem package.I dont know if this dll works because i use my custom dll.
All externals work fine, but if the touch feeling is not good for you, then just replace the touch.dll and touchgl.dll from stock rom.Then touch is much better and soft.
Click to expand...
Click to collapse
Ahaaa... I thought so that the touch was different... It was freakin me out!! I had better on other ROM's indeed. Thanx for the great tip man...
+ Que PPC... Changed the title of this thread... hope u don't mind...

No prob for me... but you need to change it again man... why? cause you are talking of some other things now... keep it up

NIKOSXRI said:
You should take the one from stock rom and also you must do changes in the operator package oem, of course, if you dont live in the USA.
You may also have to replace the tmous phcanoverbmp dll in this oem package.I dont know if this dll works because i use my custom dll.
All externals work fine, but if the touch feeling is not good for you, then just replace the touch.dll and touchgl.dll from stock rom.Then touch is much better and soft.
Click to expand...
Click to collapse
Very good tip indeed...i feel the touch in this rom is not as good as the stock rom. i was thinking of using some older based as i thought i screwed up something in this base.
Thanks NIKOSXRI!
P/s: As +Que PPC said, i propose to change topic to tip/things to look out for when cooking with Base 2.13.

Hopefully this title means a general topic jiji
Mod edited to change the title.... again

tidus18 said:
Very good tip indeed...i feel the touch in this rom is not as good as the stock rom. i was thinking of using some older based as i thought i screwed up something in this base.
Thanks NIKOSXRI!
P/s: As +Que PPC said, i propose to change topic to tip/things to look out for when cooking with Base 2.13.
Click to expand...
Click to collapse
Also i noticed that touch response (I mean the software), if you use it, though is very helpfull and i like it, changes the responsiveness (sometimes you tap a button with no response) because it uses its own driver.
If anyone uses it i want to hear his comments on this.

any one knows where to find the reg file to modify those tmous quicklinks... found they where in HKLM\Software\HTC\Manila\Home, but in which EXT pack (app.reg) lies these reg keys???? tried to look in OperatorPkg, but no go...

kurniawan77 said:
any one knows where to find the reg file to modify those tmous quicklinks... found they where in HKLM\Software\HTC\Manila\Home, but in which EXT pack (app.reg) lies these reg keys???? tried to look in OperatorPkg, but no go...
Click to expand...
Click to collapse
Hope this is what you mean:
EVK\OEM\LEO\0409\OperatorPkg\mxipupdate_oemoperators_102.provxml
Click to expand...
Click to collapse
this provxml sets all 9 quicklinks

ROM Loads but Freezes before Homescreen

Hey All, Im new to cooking ROMs and am trying to make one for TP2 Rhodium US.
Initially I was having issues with .netCF but that is fixed.
Now when I am flashing my ROM, I get no errors, but the HTC sense and Titanium interfaces wont load.
I can open the start menu and see about half of the things i installed, and half missing.
Any ideas?
Im using 23128 Sys and Ext files, Manila 2016, with the official HTC OEM 21887 base.

Sounds like you dont have netcf in the ROM!!

ai6908 said:
Sounds like you dont have netcf in the ROM!!
Click to expand...
Click to collapse
I just did a search, it is located in my Sys>23128>Shared>COMMON folder
I have added many files that I had previously removed to save space, and now I am getting this error when trying to create the build
"692 Modules present; Too many modules.... with 6.1 NK.exe and 6.5 XIP you' ll have non-bootable ROM.... Exiting..."
EDIT: I am now trying to recreate it in osKitchen Zero, and I see that I have SYS Build 21887, but i also have the 23128 file, could this be what is causing issues?
I have one zip file that has 23128 ZIP and SYS folders, and one that has 23128 Shared, MSXIPKernel and 0409... Do i just replace these over the 21887 files?

You need to check that box it says real wm6.5 kernel I think. Its been so long since I used EVK, I forgot what it says exactly.

ai6908 said:
You need to check that box it says real wm6.5 kernel I think. Its been so long since I used EVK, I forgot what it says exactly.
Click to expand...
Click to collapse
Okay, it looks like it is going now, if it doesnt work this time Im guessing maybe im not using the newer 23128 files and folders in the correct place?

Post Deleted

Post Deleted

[SOLVED] Touch Pro/Fuze with WM Build 23103?

Hey,
I have the ROM dump of my HD Mini, wich is WM build 23103. But I was wondering if that should work on a Touch Pro/Fuze too. The Touch Pro/Fuze has another screen resolution. Is that a huge problem?
MadMatt

No you cant do this.
Screen resolution is an huge problem thats why there are differents res for any builds.
Perhaps you can try but i doubt that you will pass the second boot screen.

af974 said:
No you cant do this.
Screen resolution is an huge problem thats why there are differents res for any builds.
Perhaps you can try but i doubt that you will pass the second boot screen.
Click to expand...
Click to collapse
Okay, and can I use the Language Pack from build 23103 (of my HD mini) for build 23146? And will the 23146 build run if I copy the OEMDrivers folder only? Or should I copy other folders as well?
Btw, I'm using osKitchen 1.33

I gave a try with 23146 and Language pack from 21913 and rom worked fine so i guess you can go with 23103 LP.
You need also MSXIPKernel in addiction to OEM Drivers , your rom will boot but you will lack a lot of features like Phone,Wi-FI,Services.If you want a lite but functionally build try to exclude Youtube,Facebook,IME,Opera,Radio and so on,then you can try to leave one by one the other packs that you think useless and see if the rom works fine.
_Madmatt said:
Okay, and can I use the Language Pack from build 23103 (of my HD mini) for build 23146? And will the 23146 build run if I copy the OEMDrivers folder only? Or should I copy other folders as well?
Btw, I'm using osKitchen 1.33
Click to expand...
Click to collapse

af974 said:
I gave a try with 23146 and Language pack from 21913 and rom worked fine so i guess you can go with 23103 LP.
You need also MSXIPKernel in addiction to OEM Drivers , your rom will boot but you will lack a lot of features like Phone,Wi-FI,Services.If you want a lite but functionally build try to exclude Youtube,Facebook,IME,Opera,Radio and so on,then you can try to leave one by one the other packs that you think useless and see if the rom works fine.
Click to expand...
Click to collapse
So, if I understood this good, my ROM won't do much more than booting if I copy the OEMDrivers and MSXIPKernel from old build to new build? And how can I get everything back to work? :s
Sorry, newbie in ROM cooking...

I'm afraid that i dont understand what you wnat to do .
Now you have 23103 build for HD Mini in OsKitchen right?
And you want to do a rom with 23146 build in you Language (German) right?
If it is correct then import build 23146 with OsKitchen and after that go into you windows mobile folder and grab your language folder from 23103 and copy to 23146 folder.
Restart OsKitchen ,select the new builds with German language,select all the EXT package that you had before and start cooking.
Why did you ask about cooking with only OEM Drivers folder if you want a fully functional rom ( like the original i suppose)?

I think you've not understood me good. Okay, I'll clarify myself
I have a HD Mini ROM with build 23103. I want to make a Touch Pro ROM with the build of the HD Mini. Will the thing be okay when I just change the build number in OsKitchen? (because the Windows Mobile builds are all together in the three structure of osK).
PS: It's Dutch, no German

Nope, if you use the Original HD Mini 23103 build you will need the native resolution for Touch Pro (480x640).
My suggestion is:
Dump an original TouchPro rom.
Import 23146 build from OsKitchen (im not sure if you will find any 23103 build )
Change the language folder.
You cant use many of the EXT packages from HD Mini because the low resolution against the TouchPro.
_Madmatt said:
I think you've not understood me good. Okay, I'll clarify myself
I have a HD Mini ROM with build 23103. I want to make a Touch Pro ROM with the build of the HD Mini. Will the thing be okay when I just change the build number in OsKitchen? (because the Windows Mobile builds are all together in the three structure of osK).
PS: It's Dutch, no German
Click to expand...
Click to collapse

af974 said:
Nope, if you use the Original HD Mini 23103 build you will need the native resolution for Touch Pro (480x640).
My suggestion is:
Dump an original TouchPro rom.
Import 23146 build from OsKitchen (im not sure if you will find any 23103 build )
Change the language folder.
You cant use many of the EXT packages from HD Mini because the low resolution against the TouchPro.
Click to expand...
Click to collapse
Okay, but when I download a new build such as 23146, and I want to import it in osKitchen, the kitchen always says "no valid ROM dump in folder"... And indeed, when I look in the folders, the MSXIPKernel contains a lot of folders, but all those folders are empty... And the MSXIPKernelLTK is empty as well. The folder COMMON contains much folders wich aren't empty. But in my dumped stock ROM of Touch Pro, there are a lot of S000 files and S001 and so on. But the download does not have these files... And what should I do to get the newer build over there?

Download the new build.
Extract it.
Run oskitchen and choose import new build and follow what i made in the attached pic,thats always work for me.
_Madmatt said:
Okay, but when I download a new build such as 23146, and I want to import it in osKitchen, the kitchen always says "no valid ROM dump in folder"... And indeed, when I look in the folders, the MSXIPKernel contains a lot of folders, but all those folders are empty... And the MSXIPKernelLTK is empty as well. The folder COMMON contains much folders wich aren't empty. But in my dumped stock ROM of Touch Pro, there are a lot of S000 files and S001 and so on. But the download does not have these files... And what should I do to get the newer build over there?
Click to expand...
Click to collapse

When I do exactly the same I get this...

Thats strange,did you try with other builds?
Post here the link where you downloaded that build so i can try.
I suggest you to post this error in OsKitchen thread otherwise.
_Madmatt said:
When I do exactly the same I get this...
Click to expand...
Click to collapse

af974 said:
Thats strange,did you try with other builds?
Post here the link where you downloaded that build so i can try.
I suggest you to post this error in OsKitchen thread otherwise.
Click to expand...
Click to collapse
Haha, I disabled "Auto detect build number" and it worked Stays strange, but okay for now I'm now building. I hope I won't brick my device, as it's not mine ;D Can I brick it by upgrading 6.1 to 6.5?

Glad that you sorted it.
Nope you cant brick it while upgrading from 6.1 to 6.5 just remember to recmode some modules (oskitchen tell you which one when you dump for the 1st time a new build) otherwise check in TouchPro forum if there is a 6.5 Kernel ready,this should be better for performance.
_Madmatt said:
Haha, I disabled "Auto detect build number" and it worked Stays strange, but okay for now I'm now building. I hope I won't brick my device, as it's not mine ;D Can I brick it by upgrading 6.1 to 6.5?
Click to expand...
Click to collapse

af974 said:
Glad that you sorted it.
Nope you cant brick it while upgrading from 6.1 to 6.5 just remember to recmode some modules (oskitchen tell you which one when you dump for the 1st time a new build) otherwise check in TouchPro forum if there is a 6.5 Kernel ready,this should be better for performance.
Click to expand...
Click to collapse
Okay, Thanks for everything mate!