Database Info

TOUCHFLO v4.17.07.14 PDAVIET - For Wing's users only

Here is the brand new rom version for T-mobile Wing. It has been modified based on the OS of Wing (thanks to Mr PhamQuang from PDAViet) and included TouchFlo.
This rom is the same as the version TOUCHFLO v4.17.07.12 PDAVIET (based on HTCs' OS), but for Wings' users only because of the keyboard. I am sure that from now on there is no more complain about the keyboard problem.
How to flash it? Just extract the nbh file by nbhtool. Then you can flash the extracted OS with Aserg's method.
It has a quite big storage compared with the original Shipped rom and TouchFlo runs well!
Link: http://tom-love.net/ROM/Herald/HERA_Wing_v4.10.07.14_PDAVIET_NBH.rar

i Might try this later so my keyboard gets fixed. If this version the keyboard is indeed fixed 100%, I hope it's my final version! TouchFLO + Keyboard fixed = masterpiece!

nugift said:
Here is the brand new rom version for T-mobile Wing. It has been modified based on the OS of Wing (thanks to Mr PhamQuang from PDAViet) and included TouchFlo.
This rom is the same as the version TOUCHFLO v4.17.07.12 PDAVIET (based on HTCs' OS), but for Wings' users only because of the keyboard. I am sure that from now on there is no more complain about the keyboard problem.
How to flash it? Just extract the nbh file by nbhtool. Then you can flash the extracted OS with Aserg's method.
It has a quite big storage that the original and TouchFlo runs well!
Link: http://tom-love.net/ROM/Herald/HERA_Wing_v4.10.07.14_PDAVIET_NBH.rar
Click to expand...
Click to collapse
I tried this version on my wing, but it never worked. I've being using PDAVIET since version .07 - .15 but .14 did not complete the flash for some reason.

Same here. Doesn't finish and when I try to extract the SYS and OEM files from it I get errors.

mikenaustin said:
Same here. Doesn't finish and when I try to extract the SYS and OEM files from it I get errors.
Click to expand...
Click to collapse
The same thing happened to me twice (did not know the reason). But the 3th time the flashing ran smoothly and now my device works perfectly.
You can try again, but remember to softreset after installing Aserg.Policy.cab. Then you need to turn you PPC to Flightmode.

New Download Option!!!!!!!
Here's the way to get the original package from PDAVIET:
Goto: http://www.pdaviet.net/showthread.php?t=13288
and get part 1
Then download part 2 from here and extract the rar file below:
EDIT: It's still hanging during the upgrade at copyFileToTFFS

nugift said:
The same thing happened to me twice (did not know the reason). But the 3th time the flashing ran smoothly and now my device works perfectly.
You can try again, but remember to softreset after installing Aserg.Policy.cab. Then you need to turn you PPC to Flightmode.
Click to expand...
Click to collapse
Thanks! You've given me new hope.
Did you upgrade from the original TMO USA Ship version?
Thanks,
M

mikenaustin said:
Thanks! You've given me new hope.
Did you upgrade from the original TMO USA Ship version?
Thanks,
M
Click to expand...
Click to collapse
From what I know there is only one rom for Wing at the moment. This is the original TMO USA Ship version. The cooked rom v14.PDAViet is based on this rom. Mr PhamQuang removed some APP from T-mobile and added some new things as follows:
- ArcSoft MMS v4.2.8.1
- BT FTP v1.2 Build-30234
- StreamingMedia v2.20h Build-615718
- HTC Audio Manager v1.02 Build-725711
- Esmertec Jbed Java v2.1 20070802
- CommManager 1.72 với 10B
- HTC Touch UI HOME v2.0 Build-814722 (Kaiser)
- NetWizard v1.0 Build-29982
- Voice Speed Dialer v1.2 Build-070612
- X-Button v1.51 Build-30744
- SIM Manager v6.25

Is there a thread that shows what has been changed/added/deleted to this rom?
I would like to know what was taken off, and what was changed from the original tmobile ship before I switch to it.

nugift said:
The same thing happened to me twice (did not know the reason). But the 3th time the flashing ran smoothly and now my device works perfectly.
You can try again, but remember to softreset after installing Aserg.Policy.cab. Then you need to turn you PPC to Flightmode.
Click to expand...
Click to collapse
Hi,
I've tried to flash this rom a lot of times without success. I'm just wondering how you were able to, since I think their is some thing wrong with the OS.nb file.
I'm able to reflash back to version .12 or even .15 but not .14.
Any help would be great.

ttran001 said:
Hi,
I've tried to flash this rom a lot of times without success. I'm just wondering how you were able to, since I think their is some thing wrong with the OS.nb file.
I'm able to reflash back to version .12 or even .15 but not .14.
Any help would be great.
Click to expand...
Click to collapse
Why did I introduce only the nbh file here? There is a reason! At first I started many times flashing with the OS.nb but no success like you. So I requested the rom-cooker to provide the nbh file.
I got the OS.nb from the nbh file by using nbhtool. With the new OS.nb I also failt twice. By the 3th time the falshing was succesful. I think you should turn your phone to Flightmode.
Has anybody been succesful with the flashing this version?

I ve got message
CopyFileToTFFS(OS.nb:0, 0, 04100000)
ERROR: ITWriteDisk - An existing connection was forcibly closed by the remote host.

ulrakhma said:
I ve got message
CopyFileToTFFS(OS.nb:0, 0, 04100000)
ERROR: ITWriteDisk - An existing connection was forcibly closed by the remote host.
Click to expand...
Click to collapse
I received the same error message.
Well, I've wasted enough time on this, going back to version .12 until they fix the OS.nb file for this version.

nugift said:
Why did I introduce only the nbh file here? There is a reason! At first I started many times flashing with the OS.nb but no success like you. So I requested the rom-cooker to provide the nbh file.
I got the OS.nb from the nbh file by using nbhtool. With the new OS.nb I also failt twice. By the 3th time the falshing was succesful. I think you should turn your phone to Flightmode.
Has anybody been succesful with the flashing this version?
Click to expand...
Click to collapse
I have but to no avail. Same problem. It just hangs while copying.

Hi nugift,
Have you made any mods to the radio or anything else prior to flashing this?

1st link dead cant wait for this to work looks promisin

Getting same error
CopyFileToTFFS(OS.nb:0, 0, 04100000)
ERROR: ITWriteDisk - An existing connection was forcibly closed by the remote host.
I've tried 5 times to no avail. I have no issues with the other PDAVIET releases for the P4350.

i renamed the nbh file to os.nb and overwrote the one in pdaviet it installs all the way but after hard reset wont pass tmobile boot screen ima have to retry

Smilez_c said:
i renamed the nbh file to os.nb and overwrote the one in pdaviet it installs all the way but after hard reset wont pass tmobile boot screen ima have to retry
Click to expand...
Click to collapse
your not sposed to rename it. you have to use nbhtool to get os.nb out of the .nbh file.
also
i've learned through experience that in order to flash the rom successfully without error you should
1.backup up any data you want to keep
2.install Tmob RUU factory shipped wm6 version
3.install the Asearg Policies cab file
4.soft reset
5.begin the upgrade rom flash batch file

applecarriage said:
your not sposed to rename it. you have to use nbhtool to get os.nb out of the .nbh file.
also
i've learned through experience that in order to flash the rom successfully without error you should
1.backup up any data you want to keep
2.install Tmob RUU factory shipped wm6 version
3.install the Asearg Policies cab file
4.soft reset
5.begin the upgrade rom flash batch file
Click to expand...
Click to collapse
well it gave me a windows.nb file so i renamed that and copied it to the touch folder i already had

WM 6.1 19202 rebuild

Hi,
I am a litte bit confused.
I took the latest build from NoThrill (WM 6.1 19202) and wants to add some more tools. (Using the kaiserkitchen from Alexis kaiserkitchen_01-20-08.rar).
The orginal RUU_signed.nbh has a size of approx. 90 MB, but after cooking the rom with the "HTC Rom Tool 1.1.0" the new nbd has only a size of 80MB.
I checked in "HTC Rom Tool" only the OS-File. Is that the reason ?
Regards
kuzco1

if you used kaiser kitchen then the OS.nb was run through Taz's imgfs tools so it makes the rom have more storage and also shrinks the rom size down a bit so you should be fine if you got no errors while building it.

Sounds about right, the NoThrills version has an OS but also has Radio rom and a SPlash screen, these will add to the size of the nbh

ATT WM6.1 Official Build Failures

Ok I have taken the official windows mobile 6.1 rom from att and used the kitchen to extract RUU_signed.nbh which was successful in unpacking. I added one Package to oem folder and used kitchen buildos option. Rom was built successfully however when flashed to device it never even boots. More interesting than that is the New RUU_signed.nbh files is actually smaller than the original Ruu_signed.nbh file that was in the Cingular Official 6.1. Anyone with any ideas. Keep in mind that I have successfully built several roms based on the latest official cingular 6.0 rom with out any problems. Has something changed? Do I need a special WM6.1 Kitchen? Please Help me.

first, which kitchen are you using?

the (!!!readmefirst!!!.txt) says kitchen 0.3.

Pampered4Life said:
the (!!!readmefirst!!!.txt) says kitchen 0.3.
Click to expand...
Click to collapse
kaiserkitchen?
I would try updating to the latest version just to make sure, then we'll continue

Same situation. Kitchen RAR FIles says KaiserKitchen 1-20-08.rar extract and build succeeds however same scenario as decribed in original post. Strangely enough can use the same kitchen but using the att official wm6.0 rom and works flawlessly. If you would like I am willing to send an invitation for remote assistance via email to you for help?

I doubt it...
but, just out of curiousity, can you attach your one package that you are adding?

Fixed. Forgot I disabled a .net assembly in the configuration. Thanks anyways man.

A question for the cookers

Say I downloaded "frauhottelmann"'s GUI kitchen and I grabbed the original, unmodified S740 SYS and OEM folders from a thread here.
What would I need to replace in order to build a ROM that will bootup on an Excalibur ? I have the "dump" of the original 6.1 ROM from the Excalibur. Some drivers maybe ? Any help ? Thanks

Oh, so you got it already. You should start with the OEM folder of the Excalibur. Then you might have to add some of the *.cpl.xml from OEMMISC to get all settings to work. The new packages are a bit trickier to use. You need more files from the new OEM. And don't use the new Connection Setup, it doesn't work. You should be able to use the whole SYS folder though.

This is going to be difficult then. The only kitchen that exists for the Excalibur, dumps the contents of the ROM in one folder and doesn't seperate the foldes out to OEM, SYS, etc...
So is the SYS folder where all the drivers are then ?

No. There are two main folder. SYS is for the general Windows Mobile OS part. OEM is what the manufacturer or you add. The folder for drivers is on OEM and is called OEMDrivers. If you have a dump, you can make "packages" with PKGTools. There is no official 6.1 ROM right? So I guess this will be a problem, because then it doesn't sort the packages right. You'll have to try. Maybe send me a screen shot of the files or the result!

Well the original 6.1 ROM for the Excalibur (the ONLY one) was made by this guy Kavana. I'm pretty sure it was based on the files from the MS emulator and drivers from the OEM WM6. IS PkgTools included in your kitchen ? Should I try to dissassemble the ROM with your kitchen ?

yes pkgtools included.
give it a try and post if it worked!
good luck mate... i saw your prog for the weather! really nice!!
htc sliding plugin also rocks! anyway keep it up!

Well I managed to make an excalibur ROM that works (partially) with the VOX GUI kitchen, and replacing the OEMDrivers with the drivers from my official WM6 ROM. Problem is, the center button on the keypad doesn't work. Everything else is fine... although WI-FI and BT don't turn on. Any ideas what I'm doing wrong ? Oh and the startup screen is all skewed and in 4 pieces, right after the splash screen, bu before the usual winmo 6.1 splash screen.

Well I'm over that road bump now, and I'm trying to port the S740 XIP and SYS over to take advantage of the new CHOME
So far, so good...

Thanks guys for the support. I was able to make a new ROM based on the 20279 core from the S740 ALL by myself. Reading these forums for a few days is what did the trick... heh. THe ROM runs great and I have to say that BuildOS+package tools is my best ROM cooking friend right now...

NRGZ28 said:
Well the original 6.1 ROM for the Excalibur (the ONLY one) was made by this guy Kavana. I'm pretty sure it was based on the files from the MS emulator and drivers from the OEM WM6. IS PkgTools included in your kitchen ? Should I try to dissassemble the ROM with your kitchen ?
Click to expand...
Click to collapse
There is no rgu file in the rom you dumped.
and the one is not official 6.1.
You can dump the
moto q8 WM6.1 rom
s740 official rom
C810 official rom for your resource.

I know.. that was my original problem. No worries though, as I used the SYS folder from the S740 and all is well now

Cleaning up Operator PKG after stock ROM dump?

I am using OsKitchen to build a ROM for a Kaiser. I have dumped the final WM 6.1 ROM and overwritten the nk.exe with the Native 6.5 one as well as overwritten the OEMDrivers with the 3.57 ones also available. I have rebuilt the ROM using a few different versions of WM 6.5 and its all working. However I want to clean up the Operator PKG folder and split it into more friendly EXT Packages like you get when dumping the Topaz 6.5 ROM. The dump of the 3.57Kaiser ROM seems less sophisticated.
I also want to get Manila installed like lots of the cooked ROMs available on here. Does anyone have a pre-built EXT Packages folder I can use?
Thanks
Andy

OK - solved this myself. Downloaded the latest HTC Mega ROM and spent a couple of hours 'trial-and-error' building a ROM. Replaced the OEM_Lang_0409 & OEMApps folders with the MEGA ones and deleted drivers/files/Registry entries in the Kaiser OEMDrivers folder that had overlapping ones in the MEGA's EXT Packages folder.
I have to say this took way less time than I was expecting and the resulting ROM is excellent and quick )
Andy