Related
Hide/Show Hidden ROM (at least works on my TyTN - German ROM)
SHOWN:
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\EXT_FLASHDRV] "Bootphase"=dword:00000002
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\EXT_FLASHDRV] "MountHidden"=dword:00000000
HIDDEN:
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\EXT_FLASHDRV] "Bootphase"=dword:00000001
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\EXT_FLASHDRV] "MountHidden"=dword:00000001
For me this was the default:
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\EXT_FLASHDRV] "Bootphase"=dword:00000002
So, I only had to change this from 1 to 0:
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\EXT_FLASHDRV] "MountHidden"=dword:00000000
Now I can see the extended rom, my device is an HTC TyTN WWE, I will post the ExtROM to FTP in a while.
I also have updated the wiki page with your hack:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unhide_Extrom
Thanks!
pof said:
I also have updated the wiki page with your hack:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unhide_Extrom
Thanks!
Click to expand...
Click to collapse
GREAT !
Now we still need 2 very important Registry Hacks (or missing links to get them work):
1. A hack for presenting a differentiation between GPRS/EDGE and UMTS/HSDPA
2. A hack for invoking the EngineeringTest Mode
I've been unable so far to get that working on the Hermes platform. Keep trying.
pof said:
I also have updated the wiki page with your hack:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unhide_Extrom
Thanks!
Click to expand...
Click to collapse
GREAT !
Now we still need 2 very important Registry Hacks (or missing links to get them work):
1. A hack for presenting a differentiation between GPRS/EDGE and UMTS/HSDPA
2. A hack for invoking the EngineeringTest Mode
I've been unable so far to get that working on the Hermes platform. Keep trying.
pof said:
Now I can see the extended rom, my device is an HTC TyTN WWE, I will post the ExtROM to FTP in a while.
Click to expand...
Click to collapse
Thank you.
I finished uploading my ExtROM, I also created a wiki page with the contents of all the available Extended ROMs on FTP so far:
http://wiki.xda-developers.com/index.php?pagename=Hermes_ExtendedRoms
If anyone has a different version not listed, please do the following:
1) Unhide it
2) Zip it
3) Upload it
4) Update the wiki page
Thanks!
pof said:
I finished uploading my ExtROM, I also created a wiki page with the contents of all the available Extended ROMs on FTP so far:
http://wiki.xda-developers.com/index.php?pagename=Hermes_ExtendedRoms
If anyone has a different version not listed, please do the following:
1) Unhide it
2) Zip it
3) Upload it
4) Update the wiki page
Thanks!
Click to expand...
Click to collapse
Heh, youre busy one.
I added a registry tweak to change the titlebar clock to an annalog one, if someone is interested.
Hopefully we can keep the wiki growing and useful.
My default setup was also:
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\EXT_FLASHDRV] "Bootphase"=dword:00000002
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\EXT_FLASHDRV] "MountHidden"=dword:00000001
So I just changed to:
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\EXT_FLASHDRV] "MountHidden"=dword:00000000
and did a soft reset. The extended rom then appeared but it was still write protected. How do I get rid of the write protection?
LJ
Use the cab file in the wiki, it unlocks and unhides ExtROM.
After using the cab fille and/or making the tweaks myself, and the are the same as described as above, the result is that I can see the ext. rom, but it is still write protected. I can't delete any file or write a file to the ext. rom. I've got a Tytn WWE. What is the problem, or better: what is the solution???
Should be wrtitable using this cab:
ftp://xda:[email protected]/Hermes/Tools_and_Programs/HERMES_MountExtROM.CAB
If it's not, then try to hard reset and then use the cab without messing with registry keys before.
Problem with Extended ROM
I have tried all the methods in the wiki and also all the reg. edit trick but I still can't see my extended ROM. When I run the cab to Mount Extended ROM it crashes my TyTN. Locks it up befor making it to the windows screen. Does anyone have any ideas how to fix this or tell me where to look? I was going to mess around with bootloader but I am not that computer savy.
hard reset and install the unhider&unlcoker cab file. it should work after hard reset.
Have tried to Hard Reset my Taiwanese CHT9000 and only apply the HERMES_MountExtROM.CAB tweak, now can see the Extend ROM, but still cannot "unprotect" the ROM. Cannot make it writable. Any other methods? Like modifying the registry? Thanks a lot in advance!!
ghl10000 said:
pof said:
I also have updated the wiki page with your hack:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unhide_Extrom
Thanks!
Click to expand...
Click to collapse
GREAT !
Now we still need 2 very important Registry Hacks (or missing links to get them work):
1. A hack for presenting a differentiation between GPRS/EDGE and UMTS/HSDPA
2. A hack for invoking the EngineeringTest Mode
I've been unable so far to get that working on the Hermes platform. Keep trying.
Click to expand...
Click to collapse
On my Vario 2, when I'm using 3G (and therefore, HSDPA) the [3G] icon is shown in the top bar (and when it connects a small connecting icon with the moving arrows and 3G in it is diplayed, next to the square 3G indicator) - when it drops back to GPRS, it just changes to [G].
Does yours not do this?
rcyh said:
Have tried to Hard Reset my Taiwanese CHT9000 and only apply the HERMES_MountExtROM.CAB tweak, now can see the Extend ROM, but still cannot "unprotect" the ROM. Cannot make it writable. Any other methods? Like modifying the registry? Thanks a lot in advance!!
Click to expand...
Click to collapse
http://en.pdamobiz.com/en/forum/forum_posts.asp?TID=453&PN=1
Unsure whether it works myself, as I've not tried it yet, but I'd put (a small amount of) money on it that it works
Hi Chris, Thanks for your reply!!
Unfortunately, my device is still un-protectable after following the whole process. And the registry settings I have checked are exactly the same as the described. The Extended_ROM directory is still write-protected. Couldn't add or delete files in it.
Maybe I am the unlucky one that couldn't change the extended ROM at all...
Since the digital signature security autentification for CABs in ExtROM is on by default, putting in any CAB file that is either not digitally signed, or loses its authenticity because it was modified will not be installed during the Customization phase after a hard reset.
Any ideas how to solve this problen on TyTN?
There was the soluton for the Universal devices wiht the Default_Signed_DisabledSecurity.CAB. This CAB has the right signature for Universal, but it dosn’t work on TyTN.
From this MSDN discussion about Windows Mobile 5 code signing,
"Looks like you won't have to sign the cab if wceload.exe isn't used to install it. Although if it is used to install the cab file you will need to sign it."
Click to expand...
Click to collapse
http://blogs.msdn.com/windowsmobile/archive/2005/12/17/security_model_faq.aspx#506035
A possible gap? If someone could come up with a third party CAB installer that could be used during customisation, maybe it could bypass the official CAB installation procedure (and therefore the signed certificate verification) entirely? Just a thought.
For Universal this problem i think was decided here (http://forum.xda-developers.com/viewtopic.php?t=33638&postdays=0&postorder=asc&start=150) with the help of Default_Signed_DisableSecurity.CAB. But this CAB not work on my TyTN. I think it because of wrong digital sign.
As many of you will be glad to hear, I've begun working on typhoon wm5 build 5.1.29.14847.2.0.0
now i've added almost all necessary files. some drivers are left yet, though - camera, sim toolkit and htc obex driver.
Now I need help of real gurus like mamaic and buzz. Here is the point: drivers are added, but still only keyboard works. drivers are added correctly, like modules. I Guess there's something to do with the security. maybe, regenerate packages.sof? but how? also, how to create dsm and how to change offsets in modules? actually, i only need to know how to create dsm and how to add them to registry, and how to create packages.sof. Strange that i boot the os and all the files and registry entries are present, but i see phone of on today screen and only keypad and display work.
Hi, Do you have any working (even bugy) WM5 ready to install? I need it to fix my phone and revert back to W2003.
Thanks
Inquiry
Hey Sp3Dev, just wanted to know whats going on with the new build you have been working on. Did you manage to get the help that you were looking for. I just got this device yesterday to use until my Artemis arrives, but I think I will end up keeping it to replace my d600 just because I love customizing my devices. Hope you are still working on a little somthing for my SP3i.
sp3dev said:
As many of you will be glad to hear, I've begun working on typhoon wm5 build 5.1.29.14847.2.0.0
now i've added almost all necessary files. some drivers are left yet, though - camera, sim toolkit and htc obex driver.
Now I need help of real gurus like mamaic and buzz. Here is the point: drivers are added, but still only keyboard works. drivers are added correctly, like modules. I Guess there's something to do with the security. maybe, regenerate packages.sof? but how? also, how to create dsm and how to change offsets in modules? actually, i only need to know how to create dsm and how to add them to registry, and how to create packages.sof. Strange that i boot the os and all the files and registry entries are present, but i see phone of on today screen and only keypad and display work.
Click to expand...
Click to collapse
I can help a little. I only use the files already listed in the packages.sof. I don't know how to read the file though. I use Bepe's kitchen. When you seperate the files into OS and LOC, you may find some folders only contain a .dsm file. These are extra folders and can be either deleted, or used for holding additional files. these files should already be listed in the packages.sof. You may have to test them one at a time by using the createOS.exe. Now to rebuild a .dsm file, put the your folder in the OEM folder, and createOS. This will automatically rebuild the .dsm files in the OEM folder. I'm sure there is a more elegant method, perhaps by using the kitchen tools directly, but i don't know how. I recently had to translate a chinese AKU 3.2 set into english, and thats basically the method i used. This post was written w/ the assumtion that you are familiar w/ Bepe's kitchen.
Regards,
Jason
Hello.
How are you trying to create this build? Have you started off with the original Typhoon WM5 Beta, or do you use a "true" WM5 build and try to incorporate Typhoon drivers? I suppose you are doing the latter, which I really hope you'll accomplish!
If you need any help betatesting and stuff, please say so
Hi
When reading about XIP tweaks and increasing free memory, I usually end up seeing this mentioned. What exactly does it mean and how exactly do I do it?
Also, what other cooking tweaks are there for memory and performance that arent really mentioned a lot?
Thanks
I suggest you avoiding this. if you want a bit of speed up delete from xip hd.dll osaxst0 and osaxst1 (or something similar) and increase pagepool a bit
and try keeping wincenls in xip instead of imgfs
ps. doing what you requested is just cut things from xip and past somewhere in oem or sys
Interesting....can you explain what these modules needs to?
Its safe to delete them and this operation its the same for every device?
michyprima said:
I suggest you avoiding this. if you want a bit of speed up delete from xip hd.dll osaxst0 and osaxst1 (or something similar) and increase pagepool a bit
and try keeping wincenls in xip instead of imgfs
ps. doing what you requested is just cut things from xip and past somewhere in oem or sys
Click to expand...
Click to collapse
I delete them from my ROMs every time. It doesn't have any negative effects but I can't see major differences.
Here Hd.dll and Aosaxst0.dll are used for M$ debug. Like some times on pc the apps close itself, and windows asks you to send the details to M$ (example. error number : 893647). We ( users) don’t know what it means, only the developer in M$ know. But I never saw these files report anything to us. SO!!! We don’t need them! they are trash!!
Now Mencfilt.dll is for storage card encrypt. If you don’t use it, you can delete it as well. Have you had this experience where after flashing a new Rom every thing in storage card can’t show any more!!!! but its still use the space in the card. Yes it's because of this file only.
Click to expand...
Click to collapse
More: http://www.techparaiso.com/windows-...and-speed-up-your-windows-mobile-phone-device
Thanks TAEL,
well i do like the idea to not have useless things in Rom even if they doesnt improve the speed......i will cook a new rom soon with these tweaks soon.
Thanks for clarifing me.
So its just moving them to EXT or OEM? Maaan I thought it was way more complicated
Thanks
Hi Guys,
I'm currently attempting building a ROM using the OSkitchen. I've managed to get the ROM to boot and removed all the stuff i dont want.
I've figured out how to add CAB's to the EXT packages to install the stuff i want...
There's a few things i'd like to know how to do - i've tried searching but not really found any useful info for the following things - any help would be much appreciated and im looking forward to releasing my ROM for you guys
* How do i customise where an application is installed to in the start menu - As an example the icon changer application installs into its own folder 'JWD apps'?
* How can i apply Registry tweaks and other settings so i dont have to set them after Flashing?
* And Finally how do i enable the extra RAM? I'm using a T-mobile base and Radio version 2.10.50.08_2.
Thanks a lot for any help offered.
Paul
paulrgod said:
Hi Guys,
I'm currently attempting building a ROM using the OSkitchen. I've managed to get the ROM to boot and removed all the stuff i dont want.
I've figured out how to add CAB's to the EXT packages to install the stuff i want...
There's a few things i'd like to know how to do - i've tried searching but not really found any useful info for the following things - any help would be much appreciated and im looking forward to releasing my ROM for you guys
* How do i customise where an application is installed to in the start menu - As an example the icon changer application installs into its own folder 'JWD apps'?
* How can i apply Registry tweaks and other settings so i dont have to set them after Flashing?
* And Finally how do i enable the extra RAM? I'm using a T-mobile base and Radio version 2.10.50.08_2.
Thanks a lot for any help offered.
Paul
Click to expand...
Click to collapse
I have not dealt with the first question, but for #2 all you have to do is create a new EXT package and add app.reg with all of the registry settings and tweaks you want to do. Label is something like Z_Tweaks so it gets processed last.
paulrgod said:
* How do i customise where an application is installed to in the start menu - As an example the icon changer application installs into its own folder 'JWD apps'?
* How can i apply Registry tweaks and other settings so i dont have to set them after Flashing?
* And Finally how do i enable the extra RAM? I'm using a T-mobile base and Radio version 2.10.50.08_2.
Thanks a lot for any help offered.
Paul
Click to expand...
Click to collapse
1.- Many apps needs one special folder to be installed: like "Program files\JWD apps\" and many others run fine just in Windows\ so you can try to do this... open the file called app.dat in your app ext pkg... make a backup of your ext pkg... then delete all the entries in that file, but dont delete the entrie that puts the lnk into "windows\start menu\programs... It means that all the files will be intalled in windows folder... locate the lnk of that app open it with a txt editor like notepad and change the route to Windows\jwd icon changer.lnk or exe i dont know the exact name... and try to run the app from start menu... if it works ok... you will be able to run the app without double files in windows and programfiles... that lnk entrie in the app.dat allows you to select where does the icon will be in the start menu honeycomb... and you can edit all entries if you like into another folder... but remember not all apps works like this.
2.- already correctly answered
3.- there is an answer i guess.... mmm in the thread that says something like "is it safe to use tmous 2.10 as base rom to cook wwe?" or something like that search using the tool you have the right keywords you will have the right answer
Thanks so much for the answers guys - exactly what i was after - i'll get cracking with these tonight
I think i've found the info i need for enabling the 576mb RAM - i guess i'm just using the incorrect Tmous base, i'll download another and see what the result is...
Cheers
Paul
paulrgod said:
Thanks so much for the answers guys - exactly what i was after - i'll get cracking with these tonight
I think i've found the info i need for enabling the 576mb RAM - i guess i'm just using the incorrect Tmous base, i'll download another and see what the result is...
Cheers
Paul
Click to expand...
Click to collapse
you need the nk.exe from a tmous rom, plus a radio of 2.06.50.x or higher, but only with 50 in the radio version, not the 51 radios.
Hi,
I've been facing the following problem on my ROM: After a fresh flashing or hard reset, the device is unresponsible, and the start menu does not start and subsequently Manila doesn't start, until the taskbar is pressed.
Any ideas?
could it be something on the kitchen (osKitchen Zero 1.33.5) or OEM packages?
EDIT 4/OCT:
Solved.
I've started from scratch using LEO 3.14 initflashfiles and removing/changing only the necessary, and testing after each change.
Saved as Unicode UTF-16 with CR+LF (first 4 digits removed with HEX editor)
I didn't removed/changed the links that didn't create a shortcut. Only those which were creating links on the wrong place.
EDIT 1/Oct:
After rebuilding my whole kitchen, found the problem is related to Initflashfile.dat.
The dumped initflashfile.dat works without problems, but when I modify it, the problem appear.
I was editing using notepad2.
After found the problem, I searched the forum and found that after modification it needs to be HEXedited removing 4 first digits:
4. Install Hex Workshop Trial if you havent already. Open initflashfiles.dat in the hex editor.
The first 4 digits should say FFFE or something like this. Highlight those first 4 numbers and right click and delete. This is the header written in by notepad. This HAS to be removed for you initflashfiles.dat to work correctly. Then save.
Click to expand...
Click to collapse
But even after removing these digits I still have the problem.
Can someone give me some advise about how to modify the Initflashfile.dat?
I've attached the 2 files for your reference.
Thanks in advance.
Brgds
I use LockScreen from Huasan in COM3 without problems. It also may interact with your lockdevice 1.6 and you must put out Lock Screen App Launcher from Leo. Perhaps is this. I had this issue but I don´t remember why was. Sometimes was custom icons or backgrounds like "StartMenu_Background_Screen_480x800.png" & "StartMenu_Background_Screen_800x480.png". I didn´t be able to change these png´s. Get Lucky
This issue is driving me crazy.
I've just cook a ROM witout any external package only Sys and OEM and the problem is still there.
Also checked with a COM 2 build and the same issue.
I'm using osKitchen Zero v1.33.5, I've tried reimporting the original ROM and recoocking it with the same issue.
Any idea what else I can check?
Could it be a kitchen related problem?
I would suggest cooking with a different kitchen, but same pkgs and see if there is an issue. Sometimes kitchens do cause bugs...
Hi,
Finally managed to find what file was producing the problem.
I modified the first post and attached the files.
Hope someone can help me!
thanks in advance.