Related
I wanted to get a thread dedicated to getting the applications out of the Touch .nb, and into the Wizard - and specifically the "cube" and "touch" functionality that is the trademark of the new phone.
Please save "oh, I'd like" or "oh, wow" stuff for other threads - this is a dev discussion.
Criteria: Working discussions on what's been done, what are we doing, and what could be done to get the excellent new features to work.
I hope that by sharing information - we can key in on the results much faster then everyone working on their own.
Software Packages
This post is a running list of applications, and their status:
Application............. .Status:
HTC Camera ............. .???
MediaHubMini ............. .???
QuickDial ............. .???
Streaming Media ............. .???
Streaming Player ............. .???
Cube ............. .French rom working, no WWE yet
Dialer Pad ............. .Done
Comm Manager ............. .Done
Today Home Theme ............. .Done
If someone can PM me who's current on this thread, I'll update the remaining items.
.
Kickoff Status
Here's what I've tried so far:
Using the 1413 as a base, I've taken and replaced the OEM folders from the touch build and replaced the 1413 folders -completly. This resulted in the phone self power cycling at the 3rd splash screen.
I've also taken the entire touch build, replaced the ROM contents with the one from 1413 (and I might have replaced the /SYS/OS folder as well - going off memory). This was the most successful, as I was able to boot the phone and get a lot of the touch's functionality. Issues were: SID Lock error, no "touch" function, and button mapping was wrong - only button 1 showed up on settings - buttons.
More info (a little)
Well, to follow up on my note in the other thread. I did pretty much what you did and ended up in the same place.
I did discover that the two other "raw" files in the original leak contained xip contents. I'm not sure why there are two of them, and they contain similar contents. I ran a build using the one I've labeled xip1 and it gave an error about missing build.rgu in buildos. I then ran a build using the one I labeled xip here (which has a build.rgu) and it built and booted, but worked essentially the same as when using an older wizard xip.
Anyway, time for bed now.
PS I tried to upload a zip of the two xip sections but it failed. Forum maintenance I suppose. Maybe I'll try again tomorrow if anyone seems interested.
Edit: Tried again to upload, failed.
I think we should start by the Dial Pad... I think it will be the easy thing to do.
Check this Hermes Rom:
http://wmblack.info/
and this:
http://www.4winmobile.com/forums/hermes-black-rom-support/9792-released-black-iv-shadow.html
Why not port the entire ROM ?
Just a thought.
BTW, from what I know, in order to make it work, you will have to use the XIP from the Wizard, not the one from Touch.
I have some work now...but i will try and do that bit later...today or tomorrow.
anichillus said:
Why not port the entire ROM ?
Just a thought.
BTW, from what I know, in order to make it work, you will have to use the XIP from the Wizard, not the one from Touch.
I have some work now...but i will try and do that bit later...today or tomorrow.
Click to expand...
Click to collapse
I also thought this... But now we have an official build from ms... I think it is a bit more stable than a ported version (if i'm wrong, please correct me).
@joaosousa:
I tried to port the Dialpad yesterday... But it seemed that I missed some needed files/registry hacks.... Still trying.
Vi
I also think we should keep the official build from ms... It's very stable...
any luck with touch dialer skin?
In all seriousness... the Today plug-ins for the HTC touch are fricking ugly.
Anything new in here?
joaosousa said:
Anything new in here?
Click to expand...
Click to collapse
Ya... I just flashed my wizard... Without the correct XIP partition -> stuck at 87% but bootloader works... so i think i'll get my wizard back
vi
omg... Hope all goes right with your wizard...
For those who want to play...
OK, for those who want to play with the Touch Rom, here's a rapidshare link to download a "working" nk.nbf. I've also included total commander, and a registry editor for those who might want to tinker with getting things to work.
The main issues are these:
1) Pull the sim card before flashing, or you won't be able to to get to the today screen.
2) Since the elf is only a one button machine, most of the buttons do nothing, including the power button. You'll have to take out the battery to turn it off. (Unless you can figure out the registry changes needed to make it work.)
3) Don't worry about setting your timezone in the initial screen. You can set it later from the settings menu.
4) Be ready to flash back from bootloader mode when you're done exploring!
5) I pulled adobe acrobat, catalog, autoupdate. Everything else is pretty much stock. So you can get a feel for what's included, and what you might want to pull for use in the Wizard!
This is OS only.
Have fun!
Rapidshare Link: http://rapidshare.com/files/36574080/TouchROM-nk.nbf.rar
Here's a question to those who have tried it so far: has anyone seen it working, or know which application controls the 'cube' function? Is it the biotouch app?
edhaas said:
OK, for those who want to play with the Touch Rom, here's a rapidshare link to download a "working" nk.nbf. I've also included total commander, and a registry editor for those who might want to tinker with getting things to work.
The main issues are these:
1) Pull the sim card before flashing, or you won't be able to to get to the today screen.
2) Since the elf is only a one button machine, most of the buttons do nothing, including the power button. You'll have to take out the battery to turn it off. (Unless you can figure out the registry changes needed to make it work.)
3) Don't worry about setting your timezone in the initial screen. You can set it later from the settings menu.
4) Be ready to flash back from bootloader mode when you're done exploring!
5) I pulled adobe acrobat, catalog, autoupdate. Everything else is pretty much stock. So you can get a feel for what's included, and what you might want to pull for use in the Wizard!
This is OS only.
Have fun!
Rapidshare Link: http://rapidshare.com/files/36574080/TouchROM-nk.nbf.rar
Click to expand...
Click to collapse
what do you mean of working nbf, did you mean it is Touch fully rom, or mixed with wizard rom??
anichillus said:
Why not port the entire ROM ?
Just a thought.
BTW, from what I know, in order to make it work, you will have to use the XIP from the Wizard, not the one from Touch.
I have some work now...but i will try and do that bit later...today or tomorrow.
Click to expand...
Click to collapse
Yes, understood. I think the fact that it works just as well with either XIP just shows how similar the two machines actually are. Either that, or whoever "leaked" the rom included an appropriate XIP on purpose.
its right said:
what do you mean of working nbf, did you mean it is Touch fully rom, or mixed with wizard rom??
Click to expand...
Click to collapse
Fully Touch Rom. But it has been restructured to fit inside the partition settings of the Wizard.
mattk_r said:
Here's a question to those who have tried it so far: has anyone seen it working, or know which application controls the 'cube' function? Is it the biotouch app?
Click to expand...
Click to collapse
For me it didn't work. Did you notice a kind of "klick" every 2 - 5 seconds? it sounds like if the speaker are turnend on and off...
Vi
its right said:
what do you mean of working nbf, did you mean it is Touch fully rom, or mixed with wizard rom??
Click to expand...
Click to collapse
The SYS and OEM folders from Touch, the ROM folder from 1413 (going off assumption here - correct me if I'm wrong )
I've been struggling for the past few days to convert my (working) Voice Command UK cab into an OEM. I've taken the OEM for the US Voice Command from Alex's ROM Kitchenfor reference, but I'm having problems. I've tried:
- Replacing the files inside the US OEM with those from the UK cab, and changing the file names in the reg file,
- Making an OEM from the files and registry entries in the cab
- Making an OEM from the files in the cab, and the registry entries that show as changed in a reg dump before and after installation
So far, the best I can manage is for Voice Command to be assignable to a button, but then she doesn't speak! It understands some commands (for example, pressing and saying "Open Windows Media Player" will open WMP, but without her being able to talk the applications 90% useless).
I'm sorry to be asking to take up the time of our experts, but I'm at a serious brick wall and don't know which way to go now. Could anyone suggest where I'm going wrong? I can't seem to attache the working US OEM, the working UK cab, and the non-working UK OEM (keeps saying Upload Failed), so I've stuck them on MegaUpload: http://www.megaupload.com/?d=210FSFHW
Thanks for reading, and for any help everyone.
No entries in initflashfiles.dat (for startup, or files to a specific dir)?
Just a taught
I will have a look at your files later.
Laurentius26 said:
No entries in initflashfiles.dat (for startup, or files to a specific dir)?
Just a taught
I will have a look at your files later.
Click to expand...
Click to collapse
Thanks for the reply Laurentius.
The initflashes file has the same two entries as the original US OEM version, a link going to the helpfile, and a link to Voicecmd.exe going into the Startup folder. I'm not saying that's NOT where my problem lies (haven't got a clue where it is!) but I've even checked the links through Notepad and they're pointing to the right files.
Should probably say, don't try installing any Voice Command on your ROM, as the VC program doesn't play well with the Vodafone 3.08 ROM. It works fine on the 3.02 ROM, so I'm using a custom version of Slueth's 6.1 ROM at the moment. It works fine with the cab installed, so I don't think the ROM is the reason my OEM's not working.
Thanks again for the reply, any and all help is very greatly appreciated for my little problem.
What I usualy do is....
Install the cab and check the directory's and shortcut directory's!
In your case you have the US cab already, so next one is easy!
I use Registry Workshop to Explore and dump registry entry's on the device!
So if you compare the values with the US one's it should be easy!
I just released my V4 ROM, but I promise I will look into it later
Regards,
Leo
Confused Stu said:
Thanks for the reply Laurentius.
The initflashes file has the same two entries as the original US OEM version, a link going to the helpfile, and a link to Voicecmd.exe going into the Startup folder. I'm not saying that's NOT where my problem lies (haven't got a clue where it is!) but I've even checked the links through Notepad and they're pointing to the right files.
Should probably say, don't try installing any Voice Command on your ROM, as the VC program doesn't play well with the Vodafone 3.08 ROM. It works fine on the 3.02 ROM, so I'm using a custom version of Slueth's 6.1 ROM at the moment. It works fine with the cab installed, so I don't think the ROM is the reason my OEM's not working.
Thanks again for the reply, any and all help is very greatly appreciated for my little problem.
Click to expand...
Click to collapse
I have a working OEM package for UK VC 1.60.4622.0. There is one annoyance however and that is if you open the Voice Command settings and then hit OK you get two error bleeps and a window titled 'Voice Command' with a red cross and the text 'Cannot save all changes'. Voice Command does work though, however I have only had my Kaiser a few days and I haven't done any extensive testing - I probably need to go for a drive with my Bluetooth Headset and call a few people....
I created this package previously for my HTC Wizard and with WM6 running on that I don't get the same error.
To get this working on the Kaiser all I have done is changed the Key mapping in the .RGU registry file so the top left button (6) activates VC.
If I install the VC UK Cab the error I described does go away.
Andy
Just a quick update. I rebuilt my ROM with VC 1.60.4622.0 US (this is the original OEM package I found that I based my UK OEM one on, I can't quite remember where I got this?) and you get the same results with the two error bleeps and the 'Cannot save all changes' dialogue box.
Andy
i'm just quickly looking at it. Theres some missing files like comt3s51.dll, conveng.dbr and some random dlls here and there. Not sure what they do, but missing couple files here and there could be it. i have to get going, but decide to help with that.
FIX FOR WINDOWS MEDIA PLAYER
Carbon1.0~
.NET CF:
3.5
Registry:
Aserg Policies
Disable Sliding Sounds
Hide Sim Contacts
Multimedia:
Arcsoft MMS 4.2
HTC Album
AudioManager
Games:
DopeWars
PocketSand
Apps:
ClearTemp
Connection Setup
Microsoft Office
SPB Touch Calculator Skin
Touch Comm manager
Touch Dialer(with good looking background)
PocketRAR
PHM RegEdit
PIM Backup
PocketScreen
Internet Sharing
Home Plugins:
HTC Home
BatteryStatus
UltimateLaunch-PURCHASE!
Thanks:
anichillus for hypercore kitchen
Ivanmmj for alot of oems that used from his kitchen
Itje for wonderful, crystal clear instructions on how to use hypercore.
ICP-fan giving me good info so working on a new project right now.(build 19209)
PURESKILLZZZ for testing like 4 roms in one day and helping me fix them since i didnt have a phone to flash on.
Perfection3 for testing all my roms that ive built and telling me the problems
and whosever name ive forgot, sorry!
So this is the first EBO-generated rom to be released, is it not? congratulations!
Next step is to learn how to use hypercore to cook so your roms are even better (Ivan's base still has some stuff)
yeah i would but hypercore doesnt work on vista
i used to use hypercore but on my dads computer and now he upgraded to vista(his computer crashed so i installed vista)
Albert,
Please don't take this like I'm trying to be a butthole. I'm really just trying to figure out the whole custom rom scene so I can get my Wing working the way I want. You call your rom "clean" but then list a bunch of applications that aren't built into wm 6.1.
The tweaks I get, but to me it seems that if you are making a clean rom, it wouldn't have any 3rd party apps. But maybe I don't understand clean in context.
And for us new people, could you explain what exactly "Carbon1.0" and "CleanVista" mean / why we should care?
Finally, Thank you. I really am glad there are people willing to put work into these things and share with the rest of us. Keep up the good work.
custom roms are just handy instead having to install all these apps.
and i call it clean just because i used the "JustClean ebo" kitchen.
carbon1.0 is my kind of like "open touch" or "touch-IT"
then vista part is because most of the apps are vista skinned.
hope that answers all your questions.
-Albert
Maybe you should just call it "Carbon 1.0 Vista" (sounds better in my ears) and mention Ivan and his EBO in your credits in your first post
Also congratulations on your ROM
how do you install?
how do you install this im new to roms and hacking my phone
get this:
FLASH CENTER
then put the .nbh into the "RUU" folder
im really slow
RUU?
if you downloaded the flash center,
follow this picture:
Thnx ^.~
kool thnx lot
if the ROM doesnt work download the new one i posted
thanks for trying my ROMS!
umm...
the flash center isnt working for me it always comes up with a blank screen
run the herald-uspl in the flash center main folder
I did
but when i run it after step 2 my wing is blank
aznterrorist55 said:
but when i run it after step 2 my wing is blank
Click to expand...
Click to collapse
At 75% of step 2 the screen is supposed to turn white.
ICP-Fan said:
At 75% of step 2 the screen is supposed to turn white.
Click to expand...
Click to collapse
ok... then what happens after that?
aznterrorist55 said:
ok... then what happens after that?
Click to expand...
Click to collapse
I'm actually flashing my phone as I'm typing. You should see this in a DOS window if you are using USPL:
Phone screen should now be blank and the activesync icon gray
if not, the loading procedure has failed and you'll have to repeat again.
If all was OK hit ENTER and the standard "PDA Phone ROM Update Utility"
window will start, allowing you to flash patched SPL on your device.
Hit CTRL+C to Cancel or ENTER to continue... Press enter and follow the instructions in the application that pops up.
ICP-Fan said:
I'm actually flashing my phone as I'm typing. You should see this in a DOS window if you are using USPL:
Phone screen should now be blank and the activesync icon gray
if not, the loading procedure has failed and you'll have to repeat again.
If all was OK hit ENTER and the standard "PDA Phone ROM Update Utility"
window will start, allowing you to flash patched SPL on your device.
Hit CTRL+C to Cancel or ENTER to continue... Press enter and follow the instructions in the application that pops up.
Click to expand...
Click to collapse
???? i dont get the instructions because it says to connect your phone so what do u do soft reset it?
Okay. I have exhausted all possibilities that I can think of for this problem. The last few ROM's I've ported have been fine, except for one thing. After flashing (or hard reset) the ROM displays the splash screen and then goes to the welcome screen (displays welcomehead.96). However, when the LogoMsg.bmp popups up (the text that says, "The device is clearing the storage. Please wait.) it only displays for a few seconds then leaves. A few seconds later the tone that accompanies the "Tap screen to begin setting up your device" sounds. The words, "Tap screen..." do not show. However, a second or two later the tone sounds again, this time followed by the text, "Tap screen to begin...". From here everything in the ROM works fine. I just cannot figure that part out.
The LogoMsg.bmp is located in OEMDrivers, so I thought I might have accidentally removed something from the OEM folder. However, I have not found anything seemingly related. Also, I thought it might have been related to welcome.exe. Though, I've tried replacing it with an older version; still no luck. Unfortunately, I have tried so many things that I cannot remember exactly what all I have tried. I've re-ported XIP's (using Ervius' kitchen and by hand) and SYS's, as well as taking a fresh copy of my base OEM.
Essentially, I am asking if anyone has come across anything like this in your cooking, and if you have any tips. I would be more than happy to upload a copy of my ROM for you to test or upload my kitchen folders. I appreciate any help that anyone can provide.
EDIT: I'll try and upload a video later to show exactly what is happening.
Hi KMFM$
I use an official rom iolite ita for porting the xip e Sys to my kaiser. After cooking i have the same problem that you describe.
After 2 mounth there is some solution... i'm crazy for this problem
Bye
Daniele
i have the same issue when flashing any of the wm 6.5 ROM's. not sure what kitchen the chefs use but it doesnt seem to effect anything.
Well, I have yet to find a "solution" to this. However, I have just simply learn to deal with it. It does not effect the ROM in any noticeable way, and from what I've heard from other chef's, this is common in all new ROMs. Not sure what is going on in the ROM during that time frame, but again, it does not effect the standard operation of the ROM.
well dont sweat it then. yeah, i think its normal for 6.5
yep been a normal thing for all my 6.5's
hi KMFM$
the ROM is 6.1 or 6.5?
When it comes to porting it depends on build ver. ect ect. Its a big try and fail operation for moust of us when thing doesnt work as planned. But to get a true port you have to use m'relloc and manual change values in the modules, there is alot of guides on how to.
On dump of nbh in kitchen it unpacks diffrently (provider to provider or if its a "pure" HTC nbh), anyway the cue is that some of the chef`s use xip files in the ROM folder while other make mxipkernel + mxipkernelLTK in SYS and oemxipkernel in OEM then os.nb+ a folder named XIP in ROM and THAT contains boot.rgu I use the last method which for some reason works best for me.
- shifu - said:
hi KMFM$
the ROM is 6.1 or 6.5?
Click to expand...
Click to collapse
Both, actually. WM6.1 builds from about CE OS 5.2.20757+, I believe, have all given the "extra" notifier. Again, I'm over it. I've just accepted the extra tone and moved on. No big deal.
I don't know much at all about Windows Mobile Emulator, but I have been trying to get TouchFlo 3D to run on it as a today screen. I install HTC_Manila.cab which is a touchflo3D cab I have found and then it says this was written for a previous version of Windows Mobile (the emulator is 6.1) so may not work properly. I then go to settings, today, select HTC Black and click ok. When I go to the home screen it says tap here to launch TF3D and then it says launching then its says tap here..., then launching and eventually gets stuck saying tap here.
Can anybody tell me how to install TouchFlo3D on the emulator? Or perhaps it is something that can't be done.
mike_dangerous said:
I don't know much at all about Windows Mobile Emulator, but I have been trying to get TouchFlo 3D to run on it as a today screen. I install HTC_Manila.cab which is a touchflo3D cab I have found and then it says this was written for a previous version of Windows Mobile (the emulator is 6.1) so may not work properly. I then go to settings, today, select HTC Black and click ok. When I go to the home screen it says tap here to launch TF3D and then it says launching then its says tap here..., then launching and eventually gets stuck saying tap here.
Can anybody tell me how to install TouchFlo3D on the emulator? Or perhaps it is something that can't be done.
Click to expand...
Click to collapse
it can be done but it will not have textures nor be fast...very slow in fact
but here is how to install any program...set a folder where the instaler as shared in options (dont remember extact item)...it will show up as memorycard in wm's explorer... cheers
I had worked that out. I set My Documents as the memory card selected the .cab for TF3D and installed. Then it said that it was for a previous version of WM and may not work properly. I selected HTC Black under Today screen options and then it said tap her to load, then loading then back to tap here to load so TF3D never actually loaded.
Edit: You say it is slow so maybe I will try leaving it for a long time to see what happens, maybe it jsut takes an age to load.
I just doesn't seem to get past tap here to launch TouchFlo 3D and loading touch flo 3D, is jsut a loop.
Can anybody suggest what I might try to get it to work? I don't know if I am using the wrong file or the wrong version of the emulator because it might have something to do with the message saying it was written for a previous version of WM.
Has anybody had it running on their PC? It would be good if someone has already done it.
I have the same problem. I'm trying to setup an emulator that's supposed to run like an out-of-the-box HTC Diamond.
I can install the CAB, but it barely fits on the memory that the emulator has available as device memory, with other Diamond applications.
And when installed, it hangs at boot at that same message to tap to load TF3D, but it never loads.
Btw that's not all problems I have with HTC applications on the MS emulator. Tried to install HTC Home but after installation it made the emulator completely hang, and hang again right away after every reboot.
hi
Any one got any idea how to install touch flow in in WM emulator5.0 i am using touch flow 1.4
Regards
balu
hay plzz help e i want to install touch flo in my windows 6.1