Related
21193 QVGA CHS DUMP
21193 VGA CHS DUMP
I think sun_dream is already working with build 21193 since he've just released a rom for universal. way to go sun_dream.
Enjoy.
red_hanks said:
Nice one bro... Where did you ripped that?
Click to expand...
Click to collapse
I didn't ripped/dump this files, Just saw it at ppcgeeks, and decided to post it here for our great chefs to cook with.
April 1 said:
To me it looks inappropriate to put these links to BA section in the current state, many of us will download it for no good reason. Lets put something which is directly useful to most of BA users. There are very few who could use the dump effectively. This is my view, others may differ.
Click to expand...
Click to collapse
I agree, mods can this be moved to the Development and Hacking Section or wherever is appropriate.
Thanks mods...
Thanks April 1 for the suggestion.
xplode said:
it is VGA and there are some things missing from it - it is not the full dump (and i do not mean the OEM folder) - this are most needed packages for porting
Click to expand...
Click to collapse
Link updated thanks to xplode for pointing it out.
The file only includes SYS and XIP Out.
Nice one bro... Where did you ripped that?
What's password?
Are they for BA? Size looks too big for BA. Are these Chinese versions?
This is merely a dump of the build 21193 for qvga and it is in chinese.
You still need to convert it to WWE.
again, this is a dump, not a rom, it is not for BA alone but also for models with qvga screens, it still needs to be ported to a model of your choice.
Mnemonique said:
This is merely a dump of the build 21193 for qvga and it is in chinese.
You still need to convert it to WWE.
again, this is a dump, not a rom, it is not for BA alone but also for models with qvga screens, it still needs to be ported to a model of your choice.
Click to expand...
Click to collapse
To me it looks inappropriate to put these links to BA section in the current state, many of us will download it for no good reason. Lets put something which is directly useful to most of BA users. There are very few who could use the dump effectively. This is my view, others may differ.
I agree, mods can this be moved to the Development and Hacking Section or wherever is appropriate.
Thanks mods...
Thanks April 1 for the suggestion.
What's password ?
it is VGA and there are some things missing from it - it is not the full dump (and i do not mean the OEM folder) - this are most needed packages for porting
red_hanks said:
Nice one bro... Where did you ripped that?
Click to expand...
Click to collapse
I didn't ripped/dump this files, Just saw it at ppcgeeks, and decided to post it here for our great chefs to cook with.
xplode said:
it is VGA and there are some things missing from it - it is not the full dump (and i do not mean the OEM folder) - this are most needed packages for porting
Click to expand...
Click to collapse
Link updated thanks to xplode for pointing it out.
The file only includes SYS and XIP Out.
What's the password !?
archive is decrypted.
cool your head.
well tonight i will play with it
Oh sorry, I downloaded from first links it was encrypted ! :$
Moved to D&H on OP request.
Thanks and more power!
it is ready for blueangel, but i will upload it later
Wow!
Be flashing my BA as soon as I get a GO Signal for the download wooot!
hmm, waiting for the translated version....
Samsung Epix
I hope i could get WM6.5 on my samsung epix
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
???
I'm making ROM for my Acer S200...
Much things run correctly, except HTC Album. There is no any error pop up.
However, manila Photo tab "seems" work. I could not set wallpaper in setting tab and could not select pic in contact tab.
I have these packages got from
RUU_Leo_S_HTC_Asia_TW_3.04.709.1_Radio_Signed_15.40.50.07U_2.12.50.02_2_Ship.exe
Code:
PACKAGE_LEO_S_Album
PACKAGE_LEO_S_Album_0404
PACKAGE_LEO_S_AppointmentEditor
PACKAGE_LEO_S_AppointmentEditor_0404
PACKAGE_LEO_S_App_Service
PACKAGE_LEO_S_App_Service_0404
PACKAGE_LEO_S_Audio_Manager_Engine
PACKAGE_LEO_S_Audio_Manager_Engine_0404
PACKAGE_LEO_S_Boot_Launcher
PACKAGE_LEO_S_Boot_Launcher_0404
PACKAGE_LEO_S_BrowserSnapshot
PACKAGE_LEO_S_BrowserSnapshot_0404
PACKAGE_LEO_S_CommManager_HTC_ALL
PACKAGE_LEO_S_CommManager_HTC_ALL_0404
PACKAGE_LEO_S_Contact_Picker
PACKAGE_LEO_S_Contact_Picker_0404
PACKAGE_LEO_S_Contact_Utility_Engine
PACKAGE_LEO_S_Contact_Utility_Engine_0404
PACKAGE_LEO_S_DataDisconnect
PACKAGE_LEO_S_DataDisconnect_0404
PACKAGE_LEO_S_DeviceInfo
PACKAGE_LEO_S_DeviceInfo_0404
PACKAGE_LEO_S_DRM_Middleware
PACKAGE_LEO_S_DRM_Middleware_0404
PACKAGE_LEO_S_Dshow
PACKAGE_LEO_S_Dshow_0404
PACKAGE_LEO_S_Facebook_Engine
PACKAGE_LEO_S_Facebook_Engine_0404
PACKAGE_LEO_S_GoogleLocationService
PACKAGE_LEO_S_GoogleLocationService_0404
PACKAGE_LEO_S_GroupEditor
PACKAGE_LEO_S_GroupEditor_0404
PACKAGE_LEO_S_HTCAnimation
PACKAGE_LEO_S_HTCAnimation_0404
PACKAGE_LEO_S_HTCApplication
PACKAGE_LEO_S_HTCApplication_0404
PACKAGE_LEO_S_HTCBookmark
PACKAGE_LEO_S_HTCBookmark_0404
PACKAGE_LEO_S_HTCFramework
PACKAGE_LEO_S_HTCFramework_0404
PACKAGE_LEO_S_HTCGeoService
PACKAGE_LEO_S_HTCGeoService_0404
PACKAGE_LEO_S_HTCScroll
PACKAGE_LEO_S_HTCScroll_0404
PACKAGE_LEO_S_HTCStartUp
PACKAGE_LEO_S_HTCStartUp_0404
PACKAGE_LEO_S_HTCUtil
PACKAGE_LEO_S_HTCUtil_0404
PACKAGE_LEO_S_Manila_Calendar
PACKAGE_LEO_S_Manila_Calendar_0404
PACKAGE_LEO_S_Manila_Core
PACKAGE_LEO_S_Manila_Core_0404
PACKAGE_LEO_S_Manila_Home
PACKAGE_LEO_S_Manila_Home_0404
PACKAGE_LEO_S_Manila_Internet
PACKAGE_LEO_S_Manila_Internet_0404
PACKAGE_LEO_S_Manila_Mail
PACKAGE_LEO_S_Manila_Mail_0404
PACKAGE_LEO_S_Manila_Message
PACKAGE_LEO_S_Manila_Message_0404
PACKAGE_LEO_S_Manila_Music
PACKAGE_LEO_S_Manila_Music_0404
PACKAGE_LEO_S_Manila_People
PACKAGE_LEO_S_Manila_People_0404
PACKAGE_LEO_S_Manila_Photo
PACKAGE_LEO_S_Manila_Photo_0404
PACKAGE_LEO_S_Manila_Settings
PACKAGE_LEO_S_Manila_Settings_0404
PACKAGE_LEO_S_Manila_Stock
PACKAGE_LEO_S_Manila_Stock_0404
PACKAGE_LEO_S_Manila_Twitter
PACKAGE_LEO_S_Manila_Twitter_0404
PACKAGE_LEO_S_Manila_Weather
PACKAGE_LEO_S_Manila_Weather_0404
PACKAGE_LEO_S_Media_Tool_kit
PACKAGE_LEO_S_Media_Tool_kit_0404
PACKAGE_LEO_S_Menu_Enhancement
PACKAGE_LEO_S_Menu_Enhancement_0404
PACKAGE_LEO_S_mHub_VO
PACKAGE_LEO_S_mHub_VO_0404
PACKAGE_LEO_S_MyCPL
PACKAGE_LEO_S_MyCPL_0404
PACKAGE_LEO_S_New_Contact_Card
PACKAGE_LEO_S_New_Contact_Card_0404
PACKAGE_LEO_S_Phone_Canvas_Enhancement_2G
PACKAGE_LEO_S_Phone_Canvas_Enhancement_2G_0404
PACKAGE_LEO_S_Power
PACKAGE_LEO_S_Power_0404
PACKAGE_LEO_S_Resource_Proxy
PACKAGE_LEO_S_Resource_Proxy_0404
PACKAGE_LEO_S_Sensor_SDK
PACKAGE_LEO_S_Sensor_SDK_0404
PACKAGE_LEO_S_Settings_Improvement
PACKAGE_LEO_S_Settings_Improvement_0404
PACKAGE_LEO_S_SharedResource
PACKAGE_LEO_S_SharedResource_0404
PACKAGE_LEO_S_Shared_Modules
PACKAGE_LEO_S_Shared_Modules_0404
PACKAGE_LEO_S_Social_Networks_Engine
PACKAGE_LEO_S_Social_Networks_Engine_0404
PACKAGE_LEO_S_StartIconLoader
PACKAGE_LEO_S_StartIconLoader_0404
PACKAGE_LEO_S_Text_Selection
PACKAGE_LEO_S_Text_Selection_0404
PACKAGE_LEO_S_TimeZoneAutoFix
PACKAGE_LEO_S_TimeZoneAutoFix_0404
PACKAGE_LEO_S_VBookmarkMgr
PACKAGE_LEO_S_VBookmarkMgr_0404
PACKAGE_LEO_S_zlibce_m
PACKAGE_LEO_S_zlibce_m_0404
Nagato Yuki said:
I'm making ROM for my Acer S200...
Much things run correctly, except HTC Album. There is no any error pop up.
However, manila Photo tab "seems" work. I could not set wallpaper in setting tab and could not select pic in contact tab.
I have these packages got from
RUU_Leo_S_HTC_Asia_TW_3.04.709.1_Radio_Signed_15.40.50.07U_2.12.50.02_2_Ship.exe
Code:
PACKAGE_LEO_S_Album
PACKAGE_LEO_S_Album_0404
PACKAGE_LEO_S_AppointmentEditor
PACKAGE_LEO_S_AppointmentEditor_0404
PACKAGE_LEO_S_App_Service
PACKAGE_LEO_S_App_Service_0404
PACKAGE_LEO_S_Audio_Manager_Engine
PACKAGE_LEO_S_Audio_Manager_Engine_0404
PACKAGE_LEO_S_Boot_Launcher
PACKAGE_LEO_S_Boot_Launcher_0404
PACKAGE_LEO_S_BrowserSnapshot
PACKAGE_LEO_S_BrowserSnapshot_0404
PACKAGE_LEO_S_CommManager_HTC_ALL
PACKAGE_LEO_S_CommManager_HTC_ALL_0404
PACKAGE_LEO_S_Contact_Picker
PACKAGE_LEO_S_Contact_Picker_0404
PACKAGE_LEO_S_Contact_Utility_Engine
PACKAGE_LEO_S_Contact_Utility_Engine_0404
PACKAGE_LEO_S_DataDisconnect
PACKAGE_LEO_S_DataDisconnect_0404
PACKAGE_LEO_S_DeviceInfo
PACKAGE_LEO_S_DeviceInfo_0404
PACKAGE_LEO_S_DRM_Middleware
PACKAGE_LEO_S_DRM_Middleware_0404
PACKAGE_LEO_S_Dshow
PACKAGE_LEO_S_Dshow_0404
PACKAGE_LEO_S_Facebook_Engine
PACKAGE_LEO_S_Facebook_Engine_0404
PACKAGE_LEO_S_GoogleLocationService
PACKAGE_LEO_S_GoogleLocationService_0404
PACKAGE_LEO_S_GroupEditor
PACKAGE_LEO_S_GroupEditor_0404
PACKAGE_LEO_S_HTCAnimation
PACKAGE_LEO_S_HTCAnimation_0404
PACKAGE_LEO_S_HTCApplication
PACKAGE_LEO_S_HTCApplication_0404
PACKAGE_LEO_S_HTCBookmark
PACKAGE_LEO_S_HTCBookmark_0404
PACKAGE_LEO_S_HTCFramework
PACKAGE_LEO_S_HTCFramework_0404
PACKAGE_LEO_S_HTCGeoService
PACKAGE_LEO_S_HTCGeoService_0404
PACKAGE_LEO_S_HTCScroll
PACKAGE_LEO_S_HTCScroll_0404
PACKAGE_LEO_S_HTCStartUp
PACKAGE_LEO_S_HTCStartUp_0404
PACKAGE_LEO_S_HTCUtil
PACKAGE_LEO_S_HTCUtil_0404
PACKAGE_LEO_S_Manila_Calendar
PACKAGE_LEO_S_Manila_Calendar_0404
PACKAGE_LEO_S_Manila_Core
PACKAGE_LEO_S_Manila_Core_0404
PACKAGE_LEO_S_Manila_Home
PACKAGE_LEO_S_Manila_Home_0404
PACKAGE_LEO_S_Manila_Internet
PACKAGE_LEO_S_Manila_Internet_0404
PACKAGE_LEO_S_Manila_Mail
PACKAGE_LEO_S_Manila_Mail_0404
PACKAGE_LEO_S_Manila_Message
PACKAGE_LEO_S_Manila_Message_0404
PACKAGE_LEO_S_Manila_Music
PACKAGE_LEO_S_Manila_Music_0404
PACKAGE_LEO_S_Manila_People
PACKAGE_LEO_S_Manila_People_0404
PACKAGE_LEO_S_Manila_Photo
PACKAGE_LEO_S_Manila_Photo_0404
PACKAGE_LEO_S_Manila_Settings
PACKAGE_LEO_S_Manila_Settings_0404
PACKAGE_LEO_S_Manila_Stock
PACKAGE_LEO_S_Manila_Stock_0404
PACKAGE_LEO_S_Manila_Twitter
PACKAGE_LEO_S_Manila_Twitter_0404
PACKAGE_LEO_S_Manila_Weather
PACKAGE_LEO_S_Manila_Weather_0404
PACKAGE_LEO_S_Media_Tool_kit
PACKAGE_LEO_S_Media_Tool_kit_0404
PACKAGE_LEO_S_Menu_Enhancement
PACKAGE_LEO_S_Menu_Enhancement_0404
PACKAGE_LEO_S_mHub_VO
PACKAGE_LEO_S_mHub_VO_0404
PACKAGE_LEO_S_MyCPL
PACKAGE_LEO_S_MyCPL_0404
PACKAGE_LEO_S_New_Contact_Card
PACKAGE_LEO_S_New_Contact_Card_0404
PACKAGE_LEO_S_Phone_Canvas_Enhancement_2G
PACKAGE_LEO_S_Phone_Canvas_Enhancement_2G_0404
PACKAGE_LEO_S_Power
PACKAGE_LEO_S_Power_0404
PACKAGE_LEO_S_Resource_Proxy
PACKAGE_LEO_S_Resource_Proxy_0404
PACKAGE_LEO_S_Sensor_SDK
PACKAGE_LEO_S_Sensor_SDK_0404
PACKAGE_LEO_S_Settings_Improvement
PACKAGE_LEO_S_Settings_Improvement_0404
PACKAGE_LEO_S_SharedResource
PACKAGE_LEO_S_SharedResource_0404
PACKAGE_LEO_S_Shared_Modules
PACKAGE_LEO_S_Shared_Modules_0404
PACKAGE_LEO_S_Social_Networks_Engine
PACKAGE_LEO_S_Social_Networks_Engine_0404
PACKAGE_LEO_S_StartIconLoader
PACKAGE_LEO_S_StartIconLoader_0404
PACKAGE_LEO_S_Text_Selection
PACKAGE_LEO_S_Text_Selection_0404
PACKAGE_LEO_S_TimeZoneAutoFix
PACKAGE_LEO_S_TimeZoneAutoFix_0404
PACKAGE_LEO_S_VBookmarkMgr
PACKAGE_LEO_S_VBookmarkMgr_0404
PACKAGE_LEO_S_zlibce_m
PACKAGE_LEO_S_zlibce_m_0404
Click to expand...
Click to collapse
I`m guessing you're using latest Media_Tool_kit? I faced the same problem when cooking com2 with latest Media_Tool_kit.
patensas said:
I`m guessing you're using latest Media_Tool_kit? I faced the same problem when cooking com2 with latest Media_Tool_kit.
Click to expand...
Click to collapse
Yes, I'm cooking COM2 build 21911... Sorry for not mention at first post.
Maybe Media_Tool_kit from Leo S 3.04 could be the latest one, but I'm not sure that Official Leo one (with Sense 2.5.1921) could be used or not, as I'm at work now, much thanks for your information.
Edit: But I thinks that I'm lack something instead of package version, seems that Arto could use the Official Leo one (1_2_19203325_0)...
Nagato Yuki said:
Yes, I'm cooking COM2 build 21911... Sorry for not mention at first post.
Maybe Media_Tool_kit from Leo S 3.04 could be the latest one, but I'm not sure that Official Leo one (with Sense 2.5.1921) could be used or not, as I'm at work now, much thanks for your information.
Edit: But I thinks that I'm lack something instead of package version, seems that Arto could use the Official Leo one (1_2_19203325_0)...
Click to expand...
Click to collapse
Well who knows, let me know
patensas said:
Well who knows, let me know
Click to expand...
Click to collapse
I found the strange problem, even the version of HTCAlbum was the same, but the size of them are different !
The usable HTCAlbum.exe could be 483,288 Bytes, but one I get form Leo could be 1,293,824 Bytes !
I don't know the different of them...
Try adding the picture_enhancement package
When I found the size of these files change, I know I'm fail to recognize these files are UPX compressed.
I'm flashing my rom to test whether this cause the problem...
I could report it later
BTW, could any one know what's the maximum executable file size?
Media Toolkit is the one responsible to perform 'Photo picker' .
But finally I could not use either HTC Album and Media Tool kit from Leo HK or Leo S TW ROM, but from Arto's Acer ROM
It seems the problem could not be solve until reason found...
Then, I put these two file here, to let someone help me
The non-working one is from
RUU_Leo_HTC_WWE_1.66.405.2_Radio_Signed_15.30.50.07U_2.06.51.07_Ship.exe
and The working one is from Arto's Acer ROM
http://forum.xda-developers.com/showthread.php?t=642654
Bump for visible
The diffrent between your two exe's is, that the file in your HTCAlbum_workone.zip is upx-comressed. That's all.
icke said:
The diffrent between your two exe's is, that the file in your HTCAlbum_workone.zip is upx-compressed. That's all.
Click to expand...
Click to collapse
Yes, one is upx-compressed. However, even both uncompressed, it seems I have to patch it from official ROM to be used on non-HTC phone...
rafyvitto said:
HI, im sorry to say but i was not the one who patched these packages to skip device id check, it was dimice from acerclub.ru il try to contact him and get back to you.
rafyvitto
Click to expand...
Click to collapse
Since I could not understand Russian, then I still have no idea to patch them...
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!
Hi,
I am looking to cook WM6.5 ROM for my HTC Diamond. I would like to have native XIP with OEMDrivers from un-touched donor ROM, based on the leaked WM6.5 Diamond ROM called "pine ROM" from the thread "WM6.5 Native Kernel (nk.exe) for Diamond (stable now!!!)"
http://forum.xda-developers.com/showthread.php?t=546174
Unfortunately, most of the source on rayfile and rapidshare are long gone. Can someone who still keep it please kindly upload the file for download.
Thank you in advance.
kjliew said:
Unfortunately, most of the source on rayfile and rapidshare are long gone.
Click to expand...
Click to collapse
Funny that you've written that now. Just a day ago I checked pine rom link at rayfile - it works.
HD2Owner downloaded it and cooked for Diamond the day before yesterday. PM him - he's a nice guy and will share the source.
here we go... finally two days ago i was able to get my hands on this one...
searched long time for a working link. here is my re-uploaded file.
RUU_Diamond_HTC_CHS_Pine_Diamond_WM6.5_23009_debug.rar (64.29 MB)
to properly dump it with osbuilder i had to rename flash.nb0 to flash.nb
i also recomment to check out my new diamond pine based osb-kitchen (link below):
http://forum.xda-developers.com/showthread.php?p=17180071
Thanks, folks. I finally get hold of "pine ROM".
Hi,
There seems to be another source of Diamond native kernel by Monkey Bape as of:
NEW NATIVE KERNEL FOR DIAMOND POSTED by MonkeyBape
http://bbs.rombeta.com/thread-29326-1-1.html
The mirror in rapidshare is long gone. The original source seems to be from rayfile, but I cannot find its link to it. Can someone who still has the copy upload it somewhere for sharing? Link to the original rayfile source is also ok.
Thank you in advance.
kjliew, actually - the links posted by HD2O - downloadable.
If you prefer to choose the hard way - it's up to you:
This is a pine rom at raysource: http://www.rayfile.com/zh-cn/files/a6382cfa-7cf0-11de-8774-0014221b798a/
This is 6.5 XIP only: http://forum.xda-developers.com/attachment.php?attachmentid=214501&d=1249849540
Hi AndrewSh,
I already got the Pine ROM. What I meant to find is another ROM posted by MonkeyBape. The Pine ROM is build 23009, the one from MonkeyBape seems to be build 21867. Both leaked ROMs are in flash.nb0 format.
kjliew, I suppose changing sys for new one in this rom is not a big deal. The main thing is 6.5 kernel and compatible OEM, no? And I doubt that monkeybape had different nk than that one posted.
HD2O posted ready kitchen with latest COM2 included. Why not to cook a new stuff?
AndrewSh, I am not after the SYS of the leaked ROM, but the OEMDrivers. I am wondering if that ROM has a more recent OEMDrivers than the one from Pine ROM. I have no issue cooking up WM6.5 ROM with the Pine ROM I have by importing the latest SYS from TMO Leo 3.14 ROM.
Yes, it is a different nk, and it is available in another post as NATIVEdiamond6050.7z. Unfortunately, that source has been EVK-lized, but I don't use EVK for cooking. That's why I am looking for the untouched flash.nb0 to dump it in my own kitchen.
Anyway, thanks for you help.