Changing ROM Version and Date. - Windows Mobile

How can i change ROM Version Number and ROM Date? I used Ervius Visual Kitchen Tool but ended with non booting ROM.

Diagrafeas said:
How can i change ROM Version Number and ROM Date? I used Ervius Visual Kitchen Tool but ended with non booting ROM.
Click to expand...
Click to collapse
You can use Xipporterex & ROM and change date and ROM version both in payload and in nk.exe and you can edit these registry :
[HKEY_LOCAL_MACHINE\SOFTWARE\OEM]
"ROMVersion"="INSERT ROM NAME"
"OperatorVersion"="INSERT ROM NAME"
"ROMDate" value="INSERT DATE"
hope this was helpful!

man u should ry this..
http://forum.xda-developers.com/showthread.php?t=564130

Remember that those signs must have the same character number...

Diagrafeas said:
How can i change ROM Version Number and ROM Date? I used Ervius Visual Kitchen Tool but ended with non booting ROM.
Click to expand...
Click to collapse
I used HxD Hexeditor an opened S000 form the nk folder and searched for the Kernel Build but make sure the search unicode string box is ticked and shortly after that you will find the build number.
Make sure you leave the first digit in e.g in my case it is 2 so after it has being edited it would look like .2. .K.a.o.s. . . and what ever comes after.
As for the date it should be just before or just after the ROM Build.
Hope this helps

Related

how can we change the build of a ROM??

if i want to keep a certain rom but change its (as in trinity from 20273 to 22222) then how to do it.
Simple, you don't!
You have to port the ROM over. If you're refering to just changing the ROM number without actually changing the ROM itself, why would you do that? (Well, to be fair, my LZX ROMs report the wrong number, so this might be something I'd be interested in knowing, too.
ivanmmj said:
You have to port the ROM over. If you're refering to just changing the ROM number without actually changing the ROM itself, why would you do that? (Well, to be fair, my LZX ROMs report the wrong number, so this might be something I'd be interested in knowing, too.
Click to expand...
Click to collapse
of course not, Why would i just change the number??
I mean when rom cookers release new roms with new build, then the whole rom is extracted from another phone (e.g. samsung omnia)??. so what are the base files that represent this built ?? those files which i will then add new programs upon to cook my rom??
In other words "WHAT IS THE BUILT?? WHICH FILES??"
thanks for your help
aalim said:
of course not, Why would i just change the number??
I mean when rom cookers release new roms with new build, then the whole rom is extracted from another phone (e.g. samsung omnia)??. so what are the base files that represent this built ?? those files which i will then add new programs upon to cook my rom??
In other words "WHAT IS THE BUILT?? WHICH FILES??"
thanks for your help
Click to expand...
Click to collapse
The 22222 build isn't real. As far as porting, you grab the sys folder and the part of the XIP corresponding to WM without the device specific items. It really depends on the phone you have.
this is what i use and it works all the time:
http://forum.xda-developers.com/showpost.php?p=2051339&postcount=2
oh, and build 22222 is not real, as aforementioned. someone just hex edited the numbers
mbarvian said:
this is what i use and it works all the time:
http://forum.xda-developers.com/showpost.php?p=2051339&postcount=2
oh, and build 22222 is not real, as aforementioned. someone just hex edited the numbers
Click to expand...
Click to collapse
That's exactly what i needed
Have Trinity, hope it works for it smoothly
thanks mbarvian
thanks everybody
Hi, This link which wrote few post ago is dead. Can some explain here how to change build of windows mobile in 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
???

[SOLVED] How do chefs change "Model No"?

[I asked this in the wrong forum previously -- sorry for the repeat topic]
I would like to understand where the Model No string comes from. This value is shown in device info and apparently checked by some software to determine if it's running on "known" or "supported" phones (e.g., Bing).
For example this is "T-Mobile_LEO" on a US HD2.
How does a chef influence this value, and more importantly, is it possible for me to change it without needing a new ROM image or having to reflash (e.g., via the registry, or updating a file, etc)?
Some pieces of software simply check model.txt (in the windows folder).
[HKEY_LOCAL_MACHINE\Security\Internet Explorer\User Agent]
Click to expand...
Click to collapse
is used for internet based stuff
[HKEY_LOCAL_MACHINE\Software\Microsoft\ActiveSync]
"DeviceModel"="XV6875"
Click to expand...
Click to collapse
can be used
Just do a search for the model number shown in device info in total commander (do a search in the registry section), and see what comes up.
WoZZeR999 said:
Some pieces of software simply check model.txt (in the windows folder).
is used for internet based stuff
can be used
Just do a search for the model number shown in device info in total commander (do a search in the registry section), and see what comes up.
Click to expand...
Click to collapse
User-Agent is possible, but I don't think he's referring to the others. He said "T-Mobile_LEO", but HTC won't show out code names in these places except User-Agent. Maybe the OP can specific this question?
On an HD2, Settings tab -> "About Phone" -> Phone Identity
Bing picks this up:
NOTE: the above is on a cooked ROM where the chef has gratuitously changed the Model No (on a stock ROM, it's something like T-Mobile_LEO). Unfortunately this causes Bing to think it's in beta mode because it doesn't recognize the phone it's running on. I want to know if I can change it back without reflashing.
Thanks for the tips, folks. Both registry settings mentioned above have "T-Mobile_LEO" in them.
However \windows\ModelName.txt contains the value the chef changed it to ("HTC HD2").
Is it possible for me to change ModelName.txt even though it's a ROM file?
Secondarily I'm also curious about how the registry values got initialized to T-Mobile_LEO -- where specifically did *that* string come from, given that ModelName.txt contains a different string?
I created a cab with the WM6.1 SDK and it worked. My phone identifies as a T-Mobile_LEO and Bing (after being uninstalled and reinstalled) stops identifying itself as beta.
Thanks for the tips folks.
Ok happy ending lets change the name as OP didnt do it
tai4de2 said:
Thanks for the tips, folks. Both registry settings mentioned above have "T-Mobile_LEO" in them.
However \windows\ModelName.txt contains the value the chef changed it to ("HTC HD2").
Is it possible for me to change ModelName.txt even though it's a ROM file?
Secondarily I'm also curious about how the registry values got initialized to T-Mobile_LEO -- where specifically did *that* string come from, given that ModelName.txt contains a different string?
Click to expand...
Click to collapse
Yes, you can. Copy it out and edit it, then use 3rd-party file explorers such as Resco or Total Commander to overwrite the ROM file. The identity string is also a registry:
Code:
[HKEY_LOCAL_MACHINE\Ident]
"Name"="T-Mobile_LEO"
+ Que PPC said:
Ok happy ending lets change the name as OP didnt do it
Click to expand...
Click to collapse
May I know for my knowledge what does this [OP] indicate?
I have searched my kitchen endlessly for the T-Mobile_LEO string that shows up as per picture one in the earlier post, and cannot find it. The ModelName.txt file contains the correct text (as I have a Touch Pro 2).
The reg key that seems to set this is HKLM\system\platform\OEMString but I cannot find the source of this in the kitchen.
Any help would be greatly appreciated.
c_shekhar said:
May I know for my knowledge what does this [OP] indicate?
Click to expand...
Click to collapse
Original Poster
NRGZ28 said:
Original Poster
Click to expand...
Click to collapse
Thanks.......
crazyC said:
I have searched my kitchen endlessly for the T-Mobile_LEO string that shows up as per picture one in the earlier post, and cannot find it. The ModelName.txt file contains the correct text (as I have a Touch Pro 2).
The reg key that seems to set this is HKLM\system\platform\OEMString but I cannot find the source of this in the kitchen.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Does anyone have any further sugegstions? I am at a loss with this as to where this is being set. My best guess is Manila and that is why the search is not picking it up? I am no good with manila so am seeking guidance.
Cheers
It depends which kitchen or tools you are using.
In Oskitchen you can find it in 'NBH Structure.xml'
It contains the rom version and settings to create the nbh.
The kitchen uses nbImageTool.exe made by Da_G which reads this file to create the nbh.
crazyC said:
Does anyone have any further sugegstions? I am at a loss with this as to where this is being set. My best guess is Manila and that is why the search is not picking it up? I am no good with manila so am seeking guidance.
Cheers
Click to expand...
Click to collapse
Thank you for the reply.
The nbh structure.xml correctly identifies my device as a RHOD 300. The T-Mobile_LEO must be coming from somewhere else.
I use OsKItchen and the source dumped rom was from a Rhodium and so my OEM and device profile comes from that. The erroneous model no must be coming from an EXT package as far as I can see.
If you are looking for a package I would say Oemversion.
crazyC said:
Thank you for the reply.
The nbh structure.xml correctly identifies my device as a RHOD 300. The T-Mobile_LEO must be coming from somewhere else.
I use OsKItchen and the source dumped rom was from a Rhodium and so my OEM and device profile comes from that. The erroneous model no must be coming from an EXT package as far as I can see.
Click to expand...
Click to collapse
crazyC said:
Thank you for the reply.
The nbh structure.xml correctly identifies my device as a RHOD 300. The T-Mobile_LEO must be coming from somewhere else.
I use OsKItchen and the source dumped rom was from a Rhodium and so my OEM and device profile comes from that. The erroneous model no must be coming from an EXT package as far as I can see.
Click to expand...
Click to collapse
If you have swype, it would probably be coming from there.
Aaaahhhhh - now that would explain why I cannot find any reference to it in my kitchen. I could never get swype to work as an EXT package the way I wanted so it installs within XDA-UC.
Time to pull that cab apart I think.
crazyC said:
Aaaahhhhh - now that would explain why I cannot find any reference to it in my kitchen. I could never get swype to work as an EXT package the way I wanted so it installs within XDA-UC.
Time to pull that cab apart I think.
Click to expand...
Click to collapse
If you do change the Model name, Swype probably won't work. It looks at the model name.
rgb-rgb said:
If you do change the Model name, Swype probably won't work. It looks at the model name.
Click to expand...
Click to collapse
Yes - just worked that out the long way.
Oh well, at least I know how and why its there now.
Thanks all for the help.

[SOLVED] Non-booting ROM - I'm doing it wrong

Greetings!
First off, I have little idea what I'm doing, this is my first attempt to create a custom ROM. I've searched around and can't seem to find a solution.
I've got an Xperia X1 and am using osKitchen.
The ultimate goal is to have a Japanese ROM with WM build 25369 with no additional UIs, i never use sense or whatever anyway, just the old today screen with cal, messaging, and time/date items.
I have:
Latest stock ROM for X1 (GENERIC_NAM_R3AA011)
23569_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409 (Just Eng)
initflashfiles-dat-all-langs-updated-feb-24-2010.zip
RUU_Diamond_eMobile_JPN_1.81.881.2_Radio_Signed_Diamond_52.48.25.26_1.09.25.07_Ship.exe (6.1 JPN ROM)
Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65.zip
WM6550-23563-Rollup-All-Pkgs.rar (This has all languages)
Here's what I'm doing, anyone of them (or all) could be very wrong, hopefully I've done at least one thing right:
Imported X1 ROM for OEMDrivers, OEMApps, OEMOperators, oemversion, oem_dpi
Imported 6.1 JPN ROM for OEM Lang 411
-What i did here is i copied everything over from the JPN rom's oem 411 folder into the X1 OEM Lang folder, overwrote any conflicts, deleted any 0409 muis, and copied over the file from initflashfiles zip for 0411.
Replaced OEMXipKernel with the one from Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65.zip and selected custom XIP when making the rom with the one also found in that zip. Put the rest of the files (os.nb.payload, xip.bin, uldr.nb0, romhdr.bin) into the ROM Parts folder.
Then, I Used OS, OSFiles, MSXIPKernel, MSXIPKernelLTK from the 23569_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409 zip, and the rest of the packages i used from the WM6550-23563-Rollup-All-Pkgs rar (because it had 0411 files).
I deleted dpi and lang folders that my device doesn't use (it uses 192dpi 480x800 and 0411) and built the ROM, flashed, and it shows the Sony Ericsson splash screen, and then goes black forever.
I know I must be doing something very wrong, any hints as to what?
Thanks
Pfff, what a big list,
Okay I did it this way, and I make my rom in 12 languages and they are all working.
1. Install oskitchen and import xperia rom
2. After finishing import 23563 build
3. Install another oskitchen and import diamond jpn rom
4. Copy the oem_lang 0411 and the ext packages to your kovsky kitchen be aware you put them in the right place.
5. Open the kovsky kitchen and select the Japanese language and select the packages you wanna use in your rom and you're done.
Regards,
Cool thanks!
That would be for 23563 though right? What if i wanted to use 23569 with 23563 packages? ....No real reason, higher number, figure it's better somehow....that even possible?
nemasu said:
Cool thanks!
That would be for 23563 though right? What if i wanted to use 23569 with 23563 packages? ....No real reason, higher number, figure it's better somehow....that even possible?
Click to expand...
Click to collapse
Just start with 23563, it's a good package and if you have a working rom you can alway's make the change.
Greetz,
Rataplan said:
Just start with 23563, it's a good package and if you have a working rom you can alway's make the change.
Greetz,
Click to expand...
Click to collapse
Ok sounds good, I was just thinking I probably shoulda tried with something a bit easier haha.....how would i make the change? is my approach correct?
nemasu said:
Ok sounds good, I was just thinking I probably shoulda tried with something a bit easier haha.....how would i make the change? is my approach correct?
Click to expand...
Click to collapse
If you extract the 23569 build, you only have to change the All and Common folder, but in your first post you where talking about a 25369 build and I didn't know what kind off build that was.
Succes buddy,
Make sure you have the proper wince.nls in your build. If you leave it out, the rom won't boot.
Farmer Ted said:
Make sure you have the proper wince.nls in your build. If you leave it out, the rom won't boot.
Click to expand...
Click to collapse
I used the one that came with the Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65 zip.
nemasu said:
I used the one that came with the Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65 zip.
Click to expand...
Click to collapse
I don't think there is any difference between those 2 wince.nls but if you wanna be sure just use the one in the 23563/COMMON folder.
Rataplan said:
I don't think there is any difference between those 2 wince.nls but if you wanna be sure just use the one in the 23563/COMMON folder.
Click to expand...
Click to collapse
Hmm, I've got a wince.nls in:
Sources\Devices\HTC Kovsky\Profiles\default\OEMXipKernel
Sources\Windows Mobile Builds\23569\0411\WinCENLS_Lang_0411
and
Sources\Windows Mobile Builds\23569\Common\WinCENLS_WWE
they are all different sizes....should they all be the same? or only have one? or?
nemasu said:
Hmm, I've got a wince.nls in:
Sources\Devices\HTC Kovsky\Profiles\default\OEMXipKernel
Sources\Windows Mobile Builds\23569\0411\WinCENLS_Lang_0411
and
Sources\Windows Mobile Builds\23569\Common\WinCENLS_WWE
they are all different sizes....should they all be the same? or only have one? or?
Click to expand...
Click to collapse
No I have them also, never take a look at it, only checked the file when I cooked my rom's never changed anything or replaced it with another version or from another build.

[SOLVED] The Rom I cooked has lower version than my stock rom

I try to cook a WM 6.5.x rom for my Mega. But When I try to install I've noticed that(picture). So Am I did something wrong? I used ROM_Mega_HTC_WWE_EastEurope_1-28-479-4 for this as base and this
29007_XIP_HVGA_QVGA_VGA_WWQVGA_WWVGA_0409 for 6.5.x
Is this normal? Or What?
Whatever. I'm installing rom.
Well, It's sure now there is a problem with that. It stucks at 18% and don't installs.
Well, I guess this:
ROM_Mega_HTC_WWE_EastEurope_1-28-479-4
is a keyword. You have the ROM version in the file name and it's actually lower than you currently have in device.
I think this number is stored in nk.exe (it's a part of XIP -> OEMXipKernel). I have no idea if this file should be changed when porting ROM to 6.5.x. Someone else must answer it.
Normally MSXIPKernel is included in build, so perhaps nk.exe must match it. I don't know.
I figure it out. When installing it says base builds version but when installed its becomes the name I put like Fattur's Rom v1.0
how to upgrade htc touch 3g. thanks

Categories

Resources