Now introducing... the HyperCore Athena ROM Kitchen!
First, though, props to anchillus and his HyperCore kitchen. I took it, and made a few small modifications so that it's built for the Athena instead.
Feature Highlight:
Since this is a full-blown ROM kitchen, you can tweak your own ROM however you like. You can do anything that you've seen other people do with their ROMs! All that customizability is at your disposal.
Prepopulated with Windows Mobile 6.1 from the HTC Diamond (5.2.19915).
Prepopulated with applications from the HTC X7501, HTC X7510, and HTC Diamond.
Pictures are not being posted because you already know what Windows Mobile looks like - it's up to you to make it look pretty.
Installation:
Unzip. The "Core" folder goes in as C:\Core. The "HyperCore" folder can go wherever you like; the default HyperCore installer puts it on your desktop.
If you're on SPL 1.2, you'll need to copy an SPL 1.2 OS.nb on top of HyperCore\Build\ROM\OS.nb.
Instructions:
If you want to get your hands dirty right away without reading through the HyperCore instructions, here's the extremely quick version (if you already know how to handle a ROM kitchen):
Make changes in HyperCore\Build. SYS contains the base Windows Mobile 6.1 files, while OEM contains folders that HTC or you provide.
Once you've tweaked SYS and OEM to your heart's content, under HyperCore\Panel\Build, run BuildOS. You'll need to run [1] and [2] to build OS.nb in HyperCore\Build, and then [3] to convert OS.nb to RUU_signed.nbh.
Flash your ROM onto your phone.
...
...
Profit! (j/k)
If you encounter the endless customization loop problem, edit HyperCore\Build\OEM\OEM_Lang_0409\initflashfiles.dat, then find and remove the section for AutoRun.
Known issues/concerns:
The XIP is the XIP from AP 5.0 beta (build 19588.1.1.4, which was from the Sony X1 Xperia ROM). I've tried to generate a matching XIP for the ROM, but it won't boot. Anybody around here know how to create a good XIP?
There seem to be some issues with the Bluetooth OBEX service not being able to start. That's true of this ROM as well. It's able to send files to a PC without a problem, but it can't receive files (although it can copy them).
Even though screen rotation works both in the operating system and in HTC Album, HTC Album's screen rotation has the chance to screw up the operating system's screen rotation. A workaround is to use an application that can restart services (such as the FdcSoft Task Manager) to restart HTC Sensor Service (Athena).
Although the phone skin does work on 128 and 96 dpi, the speed dial application can act flaky and start drawing itself off-screen, which can trigger an error. One workaround is to dial a single number, then rotate the screen, which forces a redraw, after which it functions properly.
The VGA HTC Home plugin could be in slightly better shape. The TabSetting registry entry doesn't seem to work (or at least nobody's responded to me here yet), and the Profile tab shows a keyboard vibration option that, naturally, doesn't work.
The enlarged start menu has some icon overlap on 128 dpi.
The nifty System Status popup on 96 dpi seems to trigger just to the left of the connectivity indicator, while not triggering on the connectivity or signal strength indicators. It does work, just a little strangely on the other dpi settings.
Sym-A now generates the _ character instead of the $ character.
During phone calls, the number keypad is active instead of the alphabetic keyboard.
NOTE:
Much as with Athena Project Kitchen, this ROM kitchen is not to be used for releasing ROMs. It's for personal use only. We really don't need twenty-billion ROMs flooding this forum from everybody who wants that one little tweak.
Exceptions can be made for people who have demonstrated a solid history of producing ROMs. Ask if you feel like you have a strong case for why your ROMs need this kitchen. The current exception list: irus.
Download links:
Megaupload
RapidShare
Other file sharing site suggestions welcome.
Fixes/patches:
Attached to this post. Replace:
HyperCore\Tools\RUU\Athena_RUU.exe with the one from Athena_RUU.zip
Core\ACK\Settings.txt (Updated: July 20, 2008)
I'll be adding additional information to the next few posts over the next several days as time permits (and questions pop up).
P.S. The restriction about personal use isn't about elitism. It's about keeping the forum organized. I just don't want to see every other thread in the forum being a ROM release thread, and there's no reason to make sergiopi's job harder by making him keep track of dozens of minimally different ROMs.
Additional OEMs
NOTE: If you're add OEM packages with modules, you will want to run G'Reloc in your HyperCore\Build directory before you run BuildOS.
HTC EzInput 1.5.31226.0/HTC XT9 1.5.31232.0:
A keyboard designed for use with fingers. There are two large button keyboards (portrait and landscape versions), along with a phone keypad keyboard. The portrait/landscape keyboards swap automatically with the screen orientation. Only works properly in 192 dpi.
Megaupload
HTC LongPressEndKey 1.1.33562.2:
A nifty quick menu program that provides a number of convenient functions. A little less useful on the Athena due to, well, the lack of an end key, but potentially useful regardless. Not tested in other resolutions yet, but likely only works properly in 192 dpi.
Megaupload
Microsoft .NET Compact Framework 3.5.7283.00:
Required for running .NET Compact Framework programs. Meant to replace SYS\NetCF.
Megaupload
WkTask 1.1.7.3c:
A task manager that alters the taskbar to function more like that in traditional Windows, in addition to providing a battery bar and task launcher.
Megaupload
If you would like to change your extended ROM to add packages there for automated installation upon hard reset, you can use the extended ROM editor. You can then convert that with Dutty's NBH tool (available in the kitchen in HyperCore\Tools\Convert) and reflash.
Kitchen Tweaks/Suggestions
Additional OEM Packages:
It's quite possible to find OEM packages out there for quite a bit of software, in order to save yourself time in making your own. If you can't find one, though, there are a number of links on how to assemble your own OEM package - for example, there's a wiki article about making your own OEM package, which also has a bunch of links to existing OEM packages. Just be aware that most of the OEM packages you'll find out there are designed for 96 dpi, and thus may not work on the Athena the way you might expect - the Spb applications are a pretty good example of these, as they come with separate VGA resources.
Package Recommendations:
If you're going to make registry changes, it's usually a good idea to make a custom EM package to contain them. I would recommend using the UUID ffffffff-ffff-ffff-ffff-ffffffffffff, as that will force it to be the last registry file processed (ensuring that your registry entries "win" over those in any other OEM packages).
Package Dependencies:
PACKAGE_Diamond_Album_HTC_ALL can't function properly without PACKAGE_Diamond_HTCGesture, PACKAGE_Diamond_SensorSDK, and X7510_GSensor
PACKAGE_Diamond_VolumeControl depends upon resources in Diamond_LargeTitleBar
RealVGA_DPI_96 depends upon the *_DPI_96 directories in SYS
RealVGA_DPI_128 depends upon the *_DPI_128 directories in SYS
X7510_AudioManager refers to X7510_AudioBooster (menu option)
X7510_TouchFlo depends upon PACKAGE_Diamond_SmartTouch
PROVXML Changes:
If you want to change how your ROM thinks of itself, change HyperCore\Build\OEM\OEMVERSION\mxipupdate_OEMVERSION_100.provxml. ROMVersion is currently set to "Athena_6.1", but feel free to change that to whatever you like.
Registry Changes:
Here's a starter list of potential registry changes.
Code:
[HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]
"Cache"="\MicroDrive\Internet Explorer\Cache"
"History"="\MicroDrive\Internet Explorer\History"
Move your Pocket IE cache and history to your MicroDrive.
Code:
[HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
"MaxConnectionsPerServer"=dword:00000008
Increase the number of simultaneous connections Pocket IE makes to servers to 8.
Code:
[HKLM\Comm\Security\LASSD\AE\{50C13377-C66D-400C-889E-C316FC4AB374}]
"AEFrequencyType"=dword:00000002
Prevent Windows Mobile from screen-locking while plugged in.
Code:
[HKLM\Software\Microsoft\Internet Explorer\Navigation]
"4-Way Nav"=dword:00000000
Have Pocket IE-based widgets scroll by screen, not by link.
Code:
[HKLM\Software\Microsoft\Today\Items\"Wireless"]
"Flags"=dword:00000000
"Options"=dword:00000000
"DLL"="netui.dll"
"Order"=dword:00000000
"Enabled"=dword:00000001
"Type"=dword:00000004
Enable the Today Screen Wireless plugin.
Code:
[HKLM\System\CurrentControlSet\Control\Power]
"WakeupPowerOff"=dword:0000003c
Go back to sleep faster when auto-waking (60 seconds).
Code:
[HKLM\System\GDI\GLYPHCACHE]
"limit"=dword:00008000
Increase the graphical caching. A good size has not yet been determined, although this is the value often recommended for QVGA devices (a VGA device likely needs more).
Code:
[HKLM\System\GDI\SYSFNT]
"CS"=dword:00001000
Increase font caching.
Code:
[HKLM\System\GWE]
"Animate"=dword:00000000
Disable window animation.
Code:
[HKLM\System\GWE\Menu]
"AniType"=dword:00000000
Disable Start Menu animation.
Kitchen History
To be filled in.
Good work!
But...the xip version is after 5.2.thisisxipver and system build is there (Build xxxxx.x.x.x)
You have got a little error
michyprima said:
Good work!
But...the xip version is after 5.2.thisisxipver and system build is there (Build xxxxx.x.x.x)
You have got a little error
Click to expand...
Click to collapse
That's the thing, though - it doesn't matter much to me that it displays the XIP/system version there. Now, if other people care enough to go and change that, it's entirely up to them.
Sogarth said:
That's the thing, though - it doesn't matter much to me that it displays the XIP/system version there. Now, if other people care enough to go and change that, it's entirely up to them.
Click to expand...
Click to collapse
okey...
But...i have my kitchen because previously there arent one...
I can download it for oem packages...
XIP and SYS porting Guide
http://forum.xda-developers.com/showthread.php?t=379598
Here a tutorial and many info... from ababrekar, witha a pictorial guided step by step to download
Sogarth,
Thanks for introducing this kitchen
When I unzipped the download, I had more than 4000 error displayed. Could I ignore them?
Also, you mentioned that for spl1.2, I need to replace the os.nb in the HyperCore\Build\ROM\ directory. But I found that directory to be empty to start with. Is there supposed to be an spl3.5 os.nb there already?
Is this base ROM the same as the one we have been testing in the base wm6.1 thread?
sergiopi said:
http://forum.xda-developers.com/showthread.php?t=379598
Here a tutorial and many info... from ababrekar, witha a pictorial guided step by step to download
Click to expand...
Click to collapse
xipport is old...i use dump rom and build xip by bepe... + ervius pkgtools&buildos
been waiting for a good kitchen for ages. thanks a lot. what build is actually included?
rory
Nice job sogarth, I was looking foward to this all week. i will be giving this a try today
eaglesteve said:
Sogarth,
Thanks for introducing this kitchen
When I unzipped the download, I had more than 4000 error displayed. Could I ignore them?
Also, you mentioned that for spl1.2, I need to replace the os.nb in the HyperCore\Build\ROM\ directory. But I found that directory to be empty to start with. Is there supposed to be an spl3.5 os.nb there already?
Is this base ROM the same as the one we have been testing in the base wm6.1 thread?
Click to expand...
Click to collapse
i am having the same problem is anyone else having this problem
irus said:
i am having the same problem is anyone else having this problem
Click to expand...
Click to collapse
Yep , same here!
michyprima said:
xipport is old...i use dump rom and build xip by bepe... + ervius pkgtools&buildos
Click to expand...
Click to collapse
That's exactly why I haven't linked the first post only but the THREAD address, 24 pages of Q&A, links and files
I have the same problems with sogarth kitchen, the file could be corrupted
Blah. I guess that's what I get for using 7-zip + .zip + BZIP to try and keep everything uber-small. I'll rezip everything and re-upload. *sigh*
works for me if you open in the latest 7zip beta proper, rather than right click and extract here.
Sogarth said:
Blah. I guess that's what I get for using 7-zip + .zip + BZIP to try and keep everything uber-small. I'll rezip everything and re-upload. *sigh*
Click to expand...
Click to collapse
Megaupload kitchen re-uploaded. Rapidshare kitchen in progress.
fards said:
works for me if you open in the latest 7zip beta proper, rather than right click and extract here.
Click to expand...
Click to collapse
I'm pretty sure it works for 7-zip - I think it just doesn't work for non-7-zip .zip supporting programs.
Sogarth said:
I'm pretty sure it works for 7-zip - I think it just doesn't work for non-7-zip .zip supporting programs.
Click to expand...
Click to collapse
well it's about time they started using proper software then
Related
DCD if you dont like what im doing just tell me to delete this post and i will.
All credit goes to DCD one of the best kitchen and Rom maker's out there.
If it wasn't for him our 6800's would be almost useless.
This is for the people who are using the titan kitchen. I took DCD's latest build and repackaged it for the PPCKitchen.org Titan Kitchen located
here http://forum.ppcgeeks.com/showthread.php?t=23206
Place it in your BuildOS/Kitchens directory and then extract "Titan_DCD_3.01_Selections.txt" and place it in the BuildOS/Projects directory.
Now you can create your own custom DCD rom using the new kitchen and DCD's latest build.
I've been using this for about 20 hrs and the rom is very stable.
Thanks again DCD u Da MAN!!!!!!!!
Make Sure to remove---> _fixed <---from the end of the file before u place it in the kitchens folder.
Download
http://rapidshare.com/files/108106961/Titan_DCD_3.0.4_FIXED.rar REALLY FIXED this time LOL
thank i'm looking for this. I ran into error error nk.dat
AstronusX said:
thank i'm looking for this. I ran into error error nk.dat
Click to expand...
Click to collapse
Sorry i forgot to change it from os.paylod to nk.fat, im up loading a fix right now thanks.
Errors in PPCkitchen
King - Thanks for putting this together
Unfortunately, I'm getting an error message (a bunch).
I downloaded the main file and did the updater.
When I go into BuildOS and select DCD 3.0.4 5054 or 5060, I am bombarded with error messages "Internal Error - Option.xml GUID not found (PROGRAM - xxxxxxxxxxxxxxxxxxxxx) where the "Program" is the name of the program and the x's are registry keys.
After I click ok 100 times to get through to the Kitchen, it allows me to select programs and build the OS, but once I install it, nothing actually gets installed on the phone.
Do you know what is causing this? Any help would be appreciated.
Thanks,
mfrish said:
King - Thanks for putting this together
Unfortunately, I'm getting an error message (a bunch).
I downloaded the main file and did the updater.
When I go into BuildOS and select DCD 3.0.4 5054 or 5060, I am bombarded with error messages "Internal Error - Option.xml GUID not found (PROGRAM - xxxxxxxxxxxxxxxxxxxxx) where the "Program" is the name of the program and the x's are registry keys.
After I click ok 100 times to get through to the Kitchen, it allows me to select programs and build the OS, but once I install it, nothing actually gets installed on the phone.
Do you know what is causing this? Any help would be appreciated.
Thanks,
Click to expand...
Click to collapse
Is this your first time using the kitchen?
King_tee - I had to do alot of editing to get ALL the errors to go away. I had to remove the welcomehead96.png, also had to remove a few other items.... like remotedesktop..... I guess I should have taken a log of what I did....
Edit - However - VERY nice job getting it to where it is..... Thank you
Thanks will try. The BuildOS in the regular kitchen is crashing so I can now cook a kitchen.
Also will my OEMs made for the 3.0.1 rom work if I put them in the build os directory. I didn't use the OEMizer w/ BuildOS. It appears to be the same just w/ a different save directory.
azclown said:
King_tee - I had to do alot of editing to get ALL the errors to go away. I had to remove the welcomehead96.png, also had to remove a few other items.... like remotedesktop..... I guess I should have taken a log of what I did....
Edit - However - VERY nice job getting it to where it is..... Thank you
Click to expand...
Click to collapse
No prob az i forgot about getting rid of those files. I thought i got all of them. I will upload a new file with the fixes for those who haven't downloaded it yet.
NEW FILE UP LOADED
Let me know if its working for you guys
As of this morning, the version I downloaded still gives an error (can't find HTC Sliding Sound module) when trying to load the selections.txt file for the DCD kitchen.
drgreenberg said:
As of this morning, the version I downloaded still gives an error (can't find HTC Sliding Sound module) when trying to load the selections.txt file for the DCD kitchen.
Click to expand...
Click to collapse
The sliding sounds module is in the DCD OEM's folder......when u open it up in the kitchen it should come up as a selectable OEM. At then point all you have to do is select it.
Bell?
Does the kitchen work for Bell phones? It does not seem to be in the carrier list.
jondixon said:
Does the kitchen work for Bell phones? It does not seem to be in the carrier list.
Click to expand...
Click to collapse
I don't know if it does.Are you are referring to the ppckitchen or DCD's Kitchen?
What i have provided is just a modified version of DCD's work (all credit goes to him) that will work in the ppckitchen.
You can check over here http://forum.ppcgeeks.com/showthread.php?t=23206
if you are talking about the ppckitchen, and they should be able to answer your questions.
If you asking about the DCD kitchen you can ask over here http://forum.xda-developers.com/showthread.php?t=385336 and im sure he will help you out.
I guess the obvious question is, what's the difference between the two kitchens?
DCD's kitchen is built around his ROM. The PPCkitchen kitchen isn't designed for any specific ROM or device.
Advantages of DCD's kitchen:
It's what DCD is using, so you know it builds his ROM like he intended it.
Advantages of PPCkitchen's kitchen:
Easy to install.
Prettier front end.
More error checking.
More OEMs to pick from.
Self updating.
Device dependency/exclusions supported
Carrier dependency/exclusions supported
OEM dependency/exclusions supported
Easy to move same configuration from one kitchen to the next.
Effortless switching between ROM configurations and kitchens
Splash/animation support
gguruusa said:
DCD's kitchen is built around his ROM. The PPCkitchen kitchen isn't designed for any specific ROM or device.
Advantages of DCD's kitchen:
It's what DCD is using, so you know it builds his ROM like he intended it.
Advantages of PPCkitchen's kitchen:
Easy to install.
Prettier front end.
More error checking.
More OEMs to pick from.
Self updating.
Device dependency/exclusions supported
Carrier dependency/exclusions supported
OEM dependency/exclusions supported
Easy to move same configuration from one kitchen to the next.
Effortless switching between ROM configurations and kitchens
Splash/animation support
Click to expand...
Click to collapse
I honestly don't think you give DCD enough credit for his work.... Here are some more Advantages....
Easy to use
Builds a basic ROM with only 2 clicks of the mouse.
Can be used behind firewalls.
No IP logging when you use it. (I had been told this was logged with your login name)
In all fairness both systems work very well, while the PPC kitchen has a more elegant streamlined interface, I do believe the end result is the same, a working ROM the way "I" want it.
error
hey guy anybody else getting an error unable to make file
when it goes to unpack the ppcgeeksoem rar
azclown said:
I honestly don't think you give DCD enough credit for his work.... Here are some more Advantages....
Easy to use
Builds a basic ROM with only 2 clicks of the mouse.
Can be used behind firewalls.
No IP logging when you use it. (I had been told this was logged with your login name)
In all fairness both systems work very well, while the PPC kitchen has a more elegant streamlined interface, I do believe the end result is the same, a working ROM the way "I" want it.
Click to expand...
Click to collapse
Could be because DCD has only a little to do with what we're talking about (which I gave him credit for). That's Bepe's buildos you're looking at, and essentially what we're comparing is Bepe's buildos w/ DCD integrated against PPCKitchen's buildos w/ DCD integrated.
You can't seriously suggest that Bepe's buildos is easier to use - the interface is practically identical! Both are about the same difficulty to use in their most basic, unaltered configurations, and both can build a basic rom w/ 2 clicks. Installing, configuring, starting, and maintaining is a lot different however...the nod hands down goes to ppckitchen there. Once you get past a basic configuration, PPCkitchen's buildos is unchallenged.
The proxy/firewall thing is fixed (general release this weekend) and it doesn't log IPs (never has).
Bepe's buildos get's the nod for no internet connection required, and the previous version (I don't know about v2) get's the nod for Linux compatible. Bepe's buildos also get's the nod for being more interfaceable to other projects and having more projects using it, but none of that is related to the original question (except maybe linux compatibility). [EDIT: v2 isn't native linux compatible, so no nod there.]
All of this is not too suprising, as PPCkitchen's buildos is, at it's core, an evolution of Bepe's Buildos.
I give credit to all sources DCD's kitchen / PPC Geeks kitchen and more.
They both offer the tools to make a ROM to your likings, some better then other, but the fact of the matter is that it gets the job done.
What PPC Geeks version is doing is making a bit more user friendly ( in my opinion ), but I still used DCD's kitchens because I really don't add any extra OEM's to my ROM's unless it is a specifically Themed ROM and then again I can get it done with both kitchens with ease.
I guess users will just have to test them both out themselves to see if they prefer one or the other.
What would be great is if we can have a Modifier / virtual simulator / kitchen where we can find ways to modify our ROM's / PPC's to their best potential ( such as drivers, RAM Management that works / compatibility with different OS and maybe interface change support ).
A virtual simulator to test out all of our modifications by simulating our respective device just as if we were to cook the ROM ( this could save tons of time rather then just flashing all the time or preventing an accidental bricking of your phone)
And a Universal kitchen for practically any Device ( well TITAN at least for our use ) that works on XP, Vista, MAC, and even Linux.
Im sure with all the developers on this forum and on ppcgeeks we would be able to get this done some time in the future.
Just an Idea....
[email protected]$ said:
What would be great is if we can have a Modifier / virtual simulator / kitchen where we can find ways to modify our ROM's / PPC's to their best potential ( such as drivers, RAM Management that works / compatibility with different OS and maybe interface change support ).
A virtual simulator to test out all of our modifications by simulating our respective device just as if we were to cook the ROM ( this could save tons of time rather then just flashing all the time or preventing an accidental bricking of your phone)
And a Universal kitchen for practically any Device ( well TITAN at least for our use ) that works on XP, Vista, MAC, and even Linux.
Click to expand...
Click to collapse
PPCkitchen buildos is actually the closest you can come currently for easily swapping components around, and there's a universal kitchen here on xda that supports many devices (way more devices than PPCkitchen does).
Don't hold your breath on the hardware emulator
lightbiter said:
hey guy anybody else getting an error unable to make file
when it goes to unpack the ppcgeeksoem rar
Click to expand...
Click to collapse
You'll have to elaborate a little better. If I had to guess, however, I'd say that you might have an older version of winrar installed. As a workaround, you can manually extract and modify the selections to use the extracted dir instead of the .rar.
26/04/08 Update: some "i dislike" solved, check AP4 FAQ for solutions, Tips and Tricks
I am trying to open this thread to help AP cookers to have a single point to check for pro and cons in AP4, avoiding to post BUGS here.
Please explain WHY you dislike something
I've tested it for a while and:
I LIKE:
better battery life in my regular usage
the self portrait/landscape function
touchflo responce (after some tuning)
WM6.1 (SMS and IE)
Latest opera
Stability
I DISLIKE
The BIG htc home (to much home screen real estate used), and resources hungry too! (FULL SOLVED BELOW, 4th post)
The new USB Storage can't show the microdrive (PARTIALLY SOLVED BELOW, 4th post)
The slow keyboard responce (I've installed RESCO too, same delays) (FULL SOLVED BELOW, 4th post)
The comm manager without 3g enable/disable (good for battery saving purposes)
The flashing process, without any user control (I've copied the file unzipped during the installation process and i've dome some "reverse enigineering") I believe it could be done using a simpler command file, from command prompt windows, explaining step by step what is going on. Less "tricolours screen" and better debugging
sergiopi said:
I am trying to open this thread to help AP cookers to have a single point to chek for pro and cons in AP4, avoiding to post BUGS here.
Please explain WHY you dislike something
I've tested it for a while and:
I LIKE:
better battery life in my regular usage
the self portrait/landscape function
touchflo responce (after some tuning)
WM6.1 (SMS and IE)
Latest opera
Stability
I DISLIKE
The BIG htc home (to much home screen real estate used), and resources hungry too!
The new USB Storage can't show the microdrive
The slow keyboard responce (I've installed RESCO too, same delays)
The comm manager without 3g enable/disable (good for battery saving purposes)
The flashing process, without any user control (I've copied the file unzipped during the installation process and i've dome some "reverse enigineering") I believe it could be done using a simpler command file, from command prompt windows, explaining step by step what is going on. Less "tricolours screen" and better debugging
Click to expand...
Click to collapse
thanx for the opinions and feedback. for the slow keyboard response i would try the tweak that turns off the et9. its found in the main thread and will come in the new version of the config app.
the comm mananger was already in the x7510 rom so i just kept it as it is. i see though that it would be a good idea to add the 3g. i need to check if this comm mananger supports changing its function like the one i have in my polaris rom. then i could just have cmonex add a new tab to the config app where u check what options you like in the comm mananger.
i believe the usb to pc tool when turned on to mass storage mode lets you add to the microdrive.
the big htc home can be replaced with the smaller qvga one via the addons rar.
the flash process you would need to discuss with olipro/cmonex. i though believe its as simple as possible right now but i could be wrong.
A problem, for my important one, is that it occupies much memory. It is to say..., in my single country exist maps for GARMIN XT and if I install MANILA to him DIALER does not load GARMIN to me XT by lack of memory, if I install plugins to him in the TODAY does not load the GARMIN to me by lack of memory...
in the AP3 no....
Some Dislike Solved
1. Big HTC Home
go to http://forum.xda-developers.com/showpost.php?p=2053447&postcount=2
download addons.rar
unrar and install HTCHome_1025_721_ALL.cab
FASTER, also in portrait/landscape switching!
2. USB to Storage and Microdrive
Miletb suggest to change:
HLKM\Drivers\USB\FunctionDrivers\Mass_Storage_Clas s\DeviceName from DSK2:
to
DSK1:
it will work fine - transfer speed is also good
If you want storage card later you will need to change back to DSK2:
3. SLOW KB FEEDBACK:
PAWEL sugges to to change:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Layouts\e0010409]
"Layout Text"="eT9 IME"
"Ime File"="\\windows\\eT9ime.dll"
to
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Layouts\e0010409]
"Layout Text"="COMP IME"
"Ime File"="compime.dll"
this will fix 1)the suggestions dialog in sms/emails being missing 2)the accented characters 3)the slow Kb feedback
P.S. To reduce/cancel the TT landscape/portrait switching during driving, just tune the position of the gooseneck support. It is stable in my tests in landscape mode leaving the top 2 cm backward from the bottom (the top is closer to the windscreen). I drive a Nissan Pathfinder http://www.nissanusa.com/pathfinder/ and my tests were really HARD
sergiopi said:
[*]The flashing process, without any user control (I've copied the file unzipped during the installation process and i've dome some "reverse enigineering") I believe it could be done using a simpler command file, from command prompt windows, explaining step by step what is going on. Less "tricolours screen" and better debugging
[/LIST]
Click to expand...
Click to collapse
sorry but I doubt what you did can be called "reverse engineering"
exactly what is your suggestion anyway? is the way HTC wrote ROMUpdateUtility.exe not good enough for you? or what did you mean, please elaborate.
cmonex said:
sorry but I doubt what you did can be called "reverse engineering"
exactly what is your suggestion anyway? is the way HTC wrote ROMUpdateUtility.exe not good enough for you? or what did you mean, please elaborate.
Click to expand...
Click to collapse
Reverse engineering in simple words means to use tools to monitor the program execution, dump the memory used, the data flow trought the USB port, then to have a team analyzing all the info and trying to understand what's going on (and I have time, tools, and team)
I mean the process control. RUU is just a PART of the AP4 flashing process. If I want to flash AP4 again I can't do without flashing the SPL again.
You've built a new tool, NOT a plain RUU. AP3 new version is a plain RUU, AP4 IMHO is a batch process launching RUU, undocumented
I like to have a clear view of the processes, is hard to ask to HTC to show their processes, and you and olipro (and some others, POF is great too..) have done a good job in RUU reverse engineeering (RUU is a batch process too, from HTC...). I would like to have the AP4 .exe documented, having also the view of the .nbh and of the other tools used. May be others can build a new ROM to share, based on the new partitioned ATHENA!
The ATHENA flashed with your tool now is the WORST ATHENA in the world
1) no warranty, no way to go back
2) the only ROM available are AP3 and AP4. None can put a new ROM on it!
3) no official ROMs anymore
4) no "self cooked" ROMs anymore
PRACTICALLY SPEAKING IS NEEDED:
1) a simple tool to go back
AND/OR
2) a clear documentation of the changes done and the tools used
BTW I respect your good job, a tuned AP4 is a good ROM, and we are here to help ATHENA/AP4 to be the best device (and to play with knowledge)
3G button in comm manager solved
Just use schap's advanced configuration tool and ADD it Download it from here: http://forum.xda-developers.com/showthread.php?t=367043
I've removed the push e-mail button because the AP4 comm mgr default layout can have 6 buttons only, and I've added the 3G on/off.
The tool could be "device customized" shoul be nice to have an ATHENA version....
sergiopi said:
Just use schap's advanced configuration tool and ADD it Download it from here: http://forum.xda-developers.com/showthread.php?t=367043
I've removed the push e-mail button because the AP4 comm mgr default layout can have 6 buttons only, and I've added the 3G on/off.
The tool could be "device customized" shoul be nice to have an ATHENA version....
Click to expand...
Click to collapse
so i guess i have the comm mananger in there that u can set what items you want in it. hehe ok there will 100% be a 4.1 I think that will be finally what people wanted from 4.0 and i'll make this one a public beta first so we wont have any issues like 4.0
thanks for your post, I might have previously misunderstand your word usage of RE. so what did you do exactly?
because you people were so impatient we just released AP4 and a flasher, if you all had waited patiently, you'd have got it with extras, such as AP4 vanilla (not requiring new SPL), a standalone AP4 full feature rom (with special NBH header so only new SPL will accept it so no risks!!), and a downgrader utility.
but you will get those anyway just wait a bit more patiently.
until then, if you have an urgent warranty problem and *must asap* downgrade to stock ROM, just let me know in a PM.
also, you are a bit wrong about flashing the SPL again - the AP4 flasher checks if you already got SPL 3.50 on, if you do have 3.50 then it will not reflash the SPL (as that would be pointless as we can agree).
what kind of documentation do you need of the AP4 flasher?
here's what it does:
1. you run the athenaupdater exe, it seems to be waiting for something while it extracts itsutils (pmemdump and stuff)
2. the something is to determine if the Athena is running WM or is put in bootloader (if some moron doesn't read the excellent HowTo a link to which is included at the athenaupdater download) - it does it in the following way: attempts to push pmemdump to the athena, if that fails then after 1 min of waiting it'll error out and shows you the ****sticks message
3. if it finds the athena running WM then it also checks the bootloader version by reading a fixed memory location. then compares bootloader version to 3.50, if it is 3.50 then it won't flash the new spl, if it is not 3.50 (can safely assume it is below 3.50) then launches RUU which then launches SSPL (named version 3.15 and will only accept signed SPL's, signed by public htcdevs cert) as the enterbootloader.exe
otherwise just launches RUU with normal enterbootloader and the overwrite protection of the SPL 3.50 won't let the SPL in the big NBH flash.
4. the NBH flashes and the athena is supposed to nicely reboot to AP4.
if you cancel the process you can be left with corrupt wifi/modelid.
+1: for extra safety the NBH has the special header already so no moron can flash it to SPL 1.20 if they manage to quickly put the device in bootloader after the pmemdump check ran.
well I think that's it.
one last question, what was the note about no self cooked roms?
it is entirely possible, you can take the nk.exe module either from AP4 or from AP3newSPL (or use AP3newSPL as base if you are afraid of xip) and use that to make your rom compatible with the new SPL.
and there'll be a downgrade tool anyway.
sergiopi said:
The tool could be "device customized" shoul be nice to have an ATHENA version....
Click to expand...
Click to collapse
yeah why not, if someone tells me exactly what options from that config app I should port to my config app
cmonex said:
yeah why not, if someone tells me exactly what options from that config app I should port to my config app
Click to expand...
Click to collapse
May be the best solution could be to build XML config file with AP4 cheats and import it into the Shaps default tool.
There are may tweaks in the "basic" tool usefull for AP4 too. Comm manager buttons and many others.
You have a great knowledge about AP4 and about the tweaks used, the fine tuning could be done using the Shaps tool, customized with your XML file as explained
From Schaps
(...) But things changed since 2.x releases, now you can add your own tweaks or translate Advanced Config. by yourself using XML files!
(...)
XML configuration files are named AdvancedConfig_XXXX.xml where XXXX is Locale ID (English and French available at the moment). They contain list of registry tweaks organized by categories.
Here is XML configuration file structure, which is quite simple:
Code:
<advancedconfig>
<category name="Category name" icon="Icon index">
<setting key="Registry key path" name="Registry value name" type="Registry value type">
<title>Tweak title</title>
<description>Tweak description</description>
<values default="Default value">
<value data="Value data 1">Value description 1</value>
<value data="Value data 2">Value description 1</value>
</values>
<restrict>
<value key="Registry key path" />
<value key="Registry key path" name="Registry value name"/>
<value key="Registry key path" name="Registry value name" data="Value data" />
<value key="Registry key path" name="Registry value name" data1="Value data 1" data2="Value data 2" data3="Value data 3" />
<devices>
<model>Device model 1</model>
<model>Device model 2</model>
</devices>
</restrict>
</setting>
</category>
</advancedconfig>Supported value types : integer, string, file, folder.
<values> tag can contain predefined value data for the tweak, which will be displayed in a list in Advanced Config.
<restrict> tag allows you to display the tweak only if it satisfies all the conditions bellow. In this example: Registry key must exist AND Registry value must exist AND value data must equal to specified data AND value data must equal one of those 3 value data AND device model must be one of those 2 models.
Don't hesitate to ask me if something is not enough clear.
You can download here English and French XML configuration files of the lastest Advanced Config. release (2.1.0.0), which is available in this sticky: http://forum.xda-developers.com/showthread.php?t=317070.
Click to expand...
Click to collapse
cmonex said:
(..)
because you people were so impatient we just released AP4 and a flasher, if you all had waited patiently, you'd have got it with extras, such as AP4 vanilla (not requiring new SPL), a standalone AP4 full feature rom (with special NBH header so only new SPL will accept it so no risks!!), and a downgrader utility.
(...)
Click to expand...
Click to collapse
Thank you, for the complete answer and the really interesting schedule
I am patient, as I told in other 3ds, and as many of us I like to play with WM6 knowledge.
I will suggest just a change in the schedule: Downgrader first, Vanilla second and AP4.1 (I've seen a lot of interesting improvements suggested from other users) third
So far these are my finding,
I LIKE:
1. the HTC and Athena Project logo - beautiful
2. the self portrait/landscape function – a little jumpy therefore disable it
3. touchflo response – excellence now I can brake
4. WM6.1 – no comments
5. Latest opera though not as responsive as IE, still trying hard diplomatically.
6. Stability – yes, as good as AP3
7. mic reception – great improvement compare to AP3, not sure is becuz of radio change, handfree call effortlessly
8. speed and memory – no issue so far with all my favorite sw running.
9. splash screen – beautifully done
10. HTC home – best with “ HTCHome_1025_721_ALL
11. AP 4.0 HTC X-Button – wonderful to kill background sw
12. WOW HD Setting – greatly improve audio quality in speaker and earpiece
13. GPS fix – better than before, could be due to radio version
14. Bluetooth - discovered range improved with my S705, never from AP3 or radio 1.50
sergiopi said:
Thank you, for the complete answer and the really interesting schedule
I am patient, as I told in other 3ds, and as many of us I like to play with WM6 knowledge.
I will suggest just a change in the schedule: Downgrader first, Vanilla second and AP4.1 (I've seen a lot of interesting improvements suggested from other users) third
Click to expand...
Click to collapse
we're considering this suggestion already
...and fourth is AP5! (yes we already have new interesting plans for that but shhhh for now )
sergiopi said:
1. Big HTC Home
go to http://forum.xda-developers.com/showpost.php?p=2053447&postcount=2
download addons.rar
unrar and install HTCHome_1025_721_ALL.cab
FASTER, also in portrait/landscape switching!
2. USB to Storage and Microdrive
Miletb suggest to change:
HLKM\Drivers\USB\FunctionDrivers\Mass_Storage_Clas s\DeviceName from DSK2:
to
DSK1:
it will work fine - transfer speed is also good
If you want storage card later you will need to change back to DSK2:
3. SLOW KB FEEDBACK:
PAWEL sugges to to change:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Layouts\e0010409]
"Layout Text"="eT9 IME"
"Ime File"="\\windows\\eT9ime.dll"
to
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Layouts\e0010409]
"Layout Text"="COMP IME"
"Ime File"="compime.dll"
this will fix 1)the suggestions dialog in sms/emails being missing 2)the accented characters 3)the slow Kb feedback
P.S. To reduce/cancel the TT landscape/portrait switching during driving, just tune the position of the gooseneck support. It is stable in my tests in landscape mode leaving the top 2 cm backward from the bottom (the top is closer to the windscreen). I drive a Nissan Pathfinder http://www.nissanusa.com/pathfinder/ and my tests were really HARD
Click to expand...
Click to collapse
Awsome
Would someone organise this in the wiki
http://wiki.xda-developers.com/index.php?pagename=HTC_Athena_AP4_FAQ
is4 said:
Awsome
Would someone organise this in the wiki
http://wiki.xda-developers.com/index.php?pagename=HTC_Athena_AP4_FAQ
Click to expand...
Click to collapse
Wiki updated with GPS best setting, PAWEL's Ftouchflo cab and et9 fix, CMONEX's AP4 installer info, HTC home fix and some others....
I will suggest to READ and WRITE the wiki....
READ and WRITE the wiki
sergiopi said:
Wiki updated with GPS best setting, PAWEL's Ftouchflo cab and et9 fix, CMONEX's AP4 installer info, HTC home fix and some others....
I will suggest to READ and WRITE the wiki....
Click to expand...
Click to collapse
thanks sergiopi
I appreciated your recent postings about the htc home alternatives and the trick about refinding a lost microdrive
I also recommend to others to READ and WRITE the wiki
http://wiki.xda-developers.com/index.php?pagename=HTC_Athena_AP4_FAQ
Can't help myself
This thread is one of the most useful (meaning: if the info's not in here I have found it from what is here) about a ROM I have ever read.
More than that, I saw lots of potential for heated defensiveness, but somewhere that energy got sucked up (I hope it got burned off in the right place). I can't tell you how personally edifying it was for me to read such a grown-up and intelligent conversation in this forum.
I'm glad I have a x7501. Thanks.
I have tried making some OEMs myself from Cabs (with some success).
I was wondering 2 things.
Does anyone know of anywhere that OEMs are downloadable. I am looking for programs like:
S2P
S2V
S2U2
TouchFlo
iContact
LiveSearch
Opera Mini
Mortscript
Weather Panel
Today Agenda
UL
I am thinking that my problems stem from the final stage
"The next window that appears, known as the 'initflashfiles tab' is for executable and help file links. Select which files you want your links and the folders to place them. Select and apply for each link and when finished, click done to proceed."
Can anyone explain this a little clearer? Do I actually have to do anything in this screen? I would love to be able to cook my own ROMS to make it easier to get my phone where I want it after a hard reset.
Also does anyone know if you can alter the OEMs and cook them. For example, could I replace the default themes in Weather Panel with the Diamond ones so that I do not have to copy from the card when resetting?
Sorry for all the questions but I recently did my first flash and now have the bug and it takes me ages to install everything every time i do it.
I get all mines from ppcgeeks some work with dcd some don't.
I use the UC option in the kitchen and use the OEMizer to create the info for it to install the CABs you want. They must be on your SD Card but it works great. It will also copy files from the SD Card to Main Memory as well. It is supposed to be able to make registry changes to but I never got that to work with just editing the provisional.xml file. OEMizer is great for several settings any ways and you will have your own personal OEM to put in the kitchen to bake.
PPC GEEKS oem.rar for the easy out way or if you are into learnning any of it oemizer works pretty good to.
I have use some on this post.
He does take request.
http://forum.ppcgeeks.com/showthread.php?t=25696
Wow, thanks for that last one, I will post some of my requests on there as well. Can't wait to get cooking!
Here are some I have made......
Update 2009/04/12
Here is a working cab to enable "Rogers/Fido Call Display" by Captain_Throwback. This cab has been tested and proven to work with many ROMs. I've personally tested it on "Energy" and "RoMEOs" ROMs and it work like a miracle. A big bravo to you, Captain
----------------------------------------------------------------------------
The QUICK/EASY method on Post #14 only work for ELITE RC2 (cab file included)
----------ROMs that work for Raphael----------
NATF's v4
Lantis OS 21009 AKU 1.5.0 v3.00
RRE Canadian 4.1
PROven ROM 1.12
Elite RC3 will include this option
For Da_G ROM and Shipped ROM, you simply have to replace the dll file
----------This is how you do it, for chefs----------
After 33 hours straight non-sleep, and plenty of pm to Da_G and NATF, I can proudly say that we've found the perfect answer for this problem
and finally we can put an end to this question "how to make Rogers/Fido Call display to work?"
I've tested this and believe that this solutions may work for any ROM. So far I've tested with 2 of NATF's ROMs, but I need someone to test
this on Kaiser and other device as well. You don't need to used a Shipped ROM, but you can apply these step to any of your favorite ROM.
2 simple steps in summary:
First you need to cook rilphone.dll file into your ROM in the folder /OEM/OEMDrivers/
Second, you need to change the file that setup all the registry key to your device when you flash
For Fuze (may be different for Kaiser), this is the file: /OEM/OEMDrivers/de3f3189-9f71-4162-9f26-39393dcc8c94.rgu
(I attach the original file from Da_G's clean ROM)You can either just replace this file or simply go in the file and Make
sure that all lines related to these regs are the same as the one I've posted here (took from Da_G's ROM)
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
[HKEY_LOCAL_MACHINE\Software\Microsoft\RIL]
POST #12 includes all registry lines that I've modified
The Files are attached.
----------How to cook rilphone.dll into your favorite ROM, from Da_G's words----------
Code:
[B][COLOR="Indigo"]-=01=-[/COLOR][/B] Download a ROM Kitchen for your device, for Fuze is RaphaelKitchen
[B][COLOR="Indigo"]-=02=-[/COLOR][/B] Extract Kitchen
[B][COLOR="Indigo"]-=03=-[/COLOR][/B] Copy your favorite ROM *.nbh file into \BaseROM\ folder (from extracted Kitchen)
[B][COLOR="Indigo"]-=04=-[/COLOR][/B] Rename your *.nbh file to RUU_Signed.nbh
[B][COLOR="Indigo"]-=05=-[/COLOR][/B] Launch "RaphaelKitchen.CMD" from *Kitchen\ folder
[B][COLOR="Indigo"]-=06=-[/COLOR][/B] choose "e" for extract, then "a" for from BaseROM "RUU_Signed.nbh
(if everything work so far, your dos should be running on it own now)
[B][COLOR="Indigo"]-=07=-[/COLOR][/B] When it's done, check if you have these three main Folders
+/OEM
+/SYS
+/ROM
(make sure they are not empty or only have 1 sub folder. if this is the case,
then your favorite ROM is protected... ask the cook nicely to share with you
those 3 folders)
[B][COLOR="Indigo"]-=08=-[/COLOR][/B] replace these 3 files into /OEM/OEMDrivers/
[URL="http://forum.xda-developers.com/attachment.php?attachmentid=141542&d=1230689478"]+"rilphone.dll[/URL]",
[URL="http://forum.xda-developers.com/attachment.php?attachmentid=141541&d=1230689478"]+"de3f3189-9f71-4162-9f26-39393dcc8c94.rgu"
+"de3f3189-9f71-4162-9f26-39393dcc8c94.dsm"[/URL]
[COLOR="Red"][B][SIZE="2"]It's recommended that you modify the *.rgu file instead of replacing it for a moded ROM,
because of all the tweaks chefs have added.)
For list of registries that I've changed in the *.rgu file, [URL="http://forum.xda-developers.com/showpost.php?p=3106249&postcount=12"]READ POST #12[/URL][/SIZE][/B][/COLOR]
[B][COLOR="Indigo"]-=09=-[/COLOR][/B] Launch "RaphaelKitchen.CMD" from *Kitchen\ folder again
[B][COLOR="Indigo"]-=10=-[/COLOR][/B] chose "cf" for cook and flash a ROM, then "b" for "if you want to use the
new BuildOS+Package..."
[B][COLOR="Indigo"]-=11=-[/COLOR][/B] Ervius Package _tool+BuildOS windows will launch, choose "BuilOS" tab
[B][COLOR="Indigo"]-=12=-[/COLOR][/B] click on "Load ROM", now choose your Kitchen/ Folder where you have
OEM/ROM/SYS folder, then click ok
[B][COLOR="Indigo"]-=13=-[/COLOR][/B] Click on RUN, once it finished loading the ROM. When you see the
word "Done" Close Ervius by clicking on the "X" button
(your DOS will run again, and ask you to press any key to start... Press
the "any key" :p )
[B][COLOR="Indigo"]-=14=-[/COLOR][/B] While it's running, it will open a tables with a bunch of numbers that
you don't understand
(it's checking the memory)... just close it by clicking on the "x" button.
(your Dos will run again, till you get your favorite Flash Window come up...
from here, you're on your own)
Don't forget to HardSPL your device before FLashing your device.
Let us know if this method work for you.
I'm also inviting all the Chefs to join the fun and provide us a Canadian version.
----------Credits----------
This tweak isn't perfect, but took me a while to make Rogers/Fido Display work. However I wouldn't be able to get this far without the helps of Da_G, NATF, trueg and a bunch of other people that I've bugged.
At least give some credits to those who have spent so much time to make this finally happened. Like Da_G said, a donation isn't required, but always appreciated.
Donate
Also, thank nitroblu and y2whisper and other Canadian users who has tested and post their results
There were many bounty offering for this discovery, but none of them keep their words... so disappointed... anyway
----------Found issues----------
1- Does not work while MSVC phone notification is activate.
2- May have issues with QuickGPS (not yet confirmed)
3- It froze my device every-time I run it with spb Wireless (need confirmation)
Can any Mod Change the topic of this one to "[Tut]First step to Canadian ROM, Rogers/Fido Display on your Fuze"
Click edit on the first post, then click advanced edit, you can change the topic from there
Da_G said:
Click edit on the first post, then click advanced edit, you can change the topic from there
Click to expand...
Click to collapse
Thank you... Now, I'll leave the Rom Cooking to the real Chef... I'm going to bed
so happy now
Hi pandaboyy,
Thanks for doing all the hard work. I am in Toronto and use Rogers and ever since I got my Tilt2 earlier this year I have been missing the name display. I just got my Fuze from the states today and installed NATF v3.2 rom. I look forward to having name display working again.
Just one question: any way to put this in a cab or build it into NAFT roms?
Thanks again.
Rob.
talonrob said:
Hi pandaboyy,
Thanks for doing all the hard work. I am in Toronto and use Rogers and ever since I got my Tilt2 earlier this year I have been missing the name display. I just got my Fuze from the states today and installed NATF v3.2 rom. I look forward to having name display working again.
Just one question: any way to put this in a cab or build it into NAFT roms?
Thanks again.
Rob.
Click to expand...
Click to collapse
Hey Rob,
I was about going to TO today to celebrate New Year Eve, but since I didn't sleep I got lazy out and drop the plan (true story). I don't think a cab would do the job. Da_G did explain it, but trust me, I still don't understand why
Da_G said:
Yes, the reason my method does not work is because the rilphone.dll is not signed with a trusted certificate as I stated..
Click to expand...
Click to collapse
And since I'm far from a chef, I really don't know how to cook a cab sorry.
However, try the cooking process that I mentioned in the first post. It's as easy as 1-2-3 and it's fun to start understand a little bit how your device work. Once you open the "de3f3189-9f71-4162-9f26-39393dcc8c94.rgu" file, you'll see that's the whole reg setting of your device. This may helps in the future, because you can actually customize your ROM so that whenever you re-flash it, your reg is already added.
Just try the Kitchen_Raphael (it's small and very easy). It'll take you about 15min to do the whole thing... with NAFT's permission, I'll try to release v3.2 with Rogers display. However, here is a good news for you; NATF is trying to release the first Canadian ROM very soon
Help me to Help you
I was trying change the entry in de3f3189-9f71-4162-9f26-39393dcc8c94.rgu file instead of replacing it to keep all the Tweaks that NATF has done. However, I come up with this error when I tried to build the ROM
"Error building default.hv and user.hv! (see "BuildOS-log.TXT")
I take a look at the file again, and I don't see any important different except for the file properties (ignore the size). Look at the image. The working file is hidden and the hidden option is disable. The non-working file is hidden, but not disable
how do I change make the file hidden and disable the option? I know that DOS can do it, but I just don't know the command.
EDIT---------------------- Solved the problem, but still want to know how to disable Hidden option-----------------------
Ok, I've read several post around the forum, and quite honestly, it didn't help much.
so I did a trial and error... If you want to edit your the de3f3189-9f71-4162-9f26-39393dcc8c94.rgu instead of replacing it, Don't overwrite the file.
1- After you finish to edit save it with another name eg: de3f3189-9f71-4162-9f26-39393dcc8c94_test.rgu.
2- Delete the original file (or move it somewhere else to be sure)
3- Rename your test file to the original name: de3f3189-9f71-4162-9f26-39393dcc8c94.rgu
4- Right click on the file, Properties then make it Hidden
(You may find this funny, but this is my amateur way)
monx said:
that file has system attributes. run this from command prompt to remove all attributes & locked attributes.
attrib -s -h -r -a filename.ext
your rgu file must hv unicode encoding, REGEDIT4 in line 1 & blank space on last line to avoid rgucomp error.
Hope this helps.
Click to expand...
Click to collapse
You mean
attrib +s +h +a filename.ext
then leave 1 empty line on the last line... do I have to add 1 space as well?
Just has to end with a blank line, rather than ending with a registry entry
Da_G said:
Just has to end with a blank line, rather than ending with a registry entry
Click to expand...
Click to collapse
Cool, thanks
Ok, I have successfully change the rgu file. It's one of these Lines, but I don't know which yet and I have no energy today to test 1 by 1 again... so if you can test it for me it would be great
Here are the lines that I've changed to make Call display work
Code:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL] ; for HTCmaskW1
"HTCmaskW1"=dword:1871
"HTCmaskW1BitMask"=dword:FFFFFF
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL] ;for A5/2, A5/3
"En52"=dword:1 ; A5/2
"En53"=dword:1 ; A5/3
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL] ;for remove RX Diversity
"RMRXDiv"=dword:0 ; Enable
[HKEY_LOCAL_MACHINE\Software\OEM\RIL]
"DisH"=dword:2
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"DisableAutoPickupAtSilentMode"=dword:1 ;disable by default
add ---> [HKEY_LOCAL_MACHINE\Software\Microsoft\RIL\APIInfo\69]
"Timeout"=dword:7918 ; 31 sec.
[HKEY_LOCAL_MACHINE\Software\Microsoft\RIL\APIInfo\82]
"Timeout"=dword:1D4C0 ; 120 sec.
[HKEY_LOCAL_MACHINE\Software\Microsoft\RIL\APIInfo\81]
"Timeout"=dword:1D4C0 ; 120 sec.
[HKEY_LOCAL_MACHINE\Comm\Cellular\RIL\RemoteCalltype]
"CalltypeDLL"=" PTTCalltypeCallback.dll" ; DLL containing the callback routine
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000100c"=dword:800 ;Service Loading (SL) Message Policy
[HKEY_LOCAL_MACHINE\Software\OEM\RIL\OperatorContexts\20801] ;Orange FR
"GPRSContextNumber"=dword:2
"UMTSContextNumber"=dword:2
[HKEY_LOCAL_MACHINE\Software\OEM\RIL\OperatorContexts\20810] ;SFR (Voda FR)
"GPRSContextNumber"=dword:2
"UMTSContextNumber"=dword:2
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"BattSuspendTimeoutBackup"=dword:3C
"BatteryTimeoutBackup"=dword:1E
"BattSuspendTimeoutInCall"=dword:30
"BatteryTimeoutInCall"=dword:30
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"EnableIMSIAttachedIcon"=dword:1
Perhaps someone can pick this up for me since I'm not much of a registry guy.
Here is a weird thing that I found about this Tweak
When someone call, the ID will display and all... However, in Call history, it will only display the caller Name if it's a missed call. If you answer it, then it won't show the name ID in call history, but only the number... I'm testing it with FuzeBerry v6 theme. Can anyone confirm this?
and if you know how to fix this, it would be great
Ok, for this tutorial, I deserved a kiss
History:
you all know how I didn't sleep for 2 days just to find what needed to be done to make it work. Now after my 10hr sleep and a bunch of parties for new years, I finally found a way to do this without cooking anything. I need someone to test it for me thou. I've tested on NATF's and Elite's ROM and it works. If this work, a thank you would do.
The Basic:
The Main idea to make this work is to replace the rilphone.dll file and add some registry into it, like I was explained in the first post. Some people claimed that those files need to be cooked in, well, you don't however, you can't just replace rilphone.dll it just doesn't work that way. But I found a way
So How to do it?
1- Download rilphone+reg.zip file from this post
2- Extract the file and you'll find
+rilphone.dll
+rilphone2.dll
+rilphone.reg
3- Copy rilphone2.dll into your Device in \Windows\ folder
4- Copy rilphone.reg anywhere
5- Importe rilphone.reg to your registry (I used resco registry to do this)
6- Change this registry from your device
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"Dll"="rilphone2.dll"
7- reboot
8- copy rilphone.dll into your device \Windows\ folder
9- Change the registry back to
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"Dll"="rilphone.dll"
10- Soft Reset
11- Delete rilphone2.dll
12- Soft Reset
13- Give me a hug
***Please report which ROM have you tried this method with and if it works or not***
--------Edit---------
Ok, so it doesn't work for every ROM. It worked with Elite RC2, thou... I'll give it more tries tonight. Stay Tune
If you want to try this process, please make backup of rilphone.dll first
And please try to put step 5 at the end.
Instead of trying all this, try the cab on post #26... if it doesn't work, just uninstall it. Backup rilphone.dll first. Worst case, just do a hard reset.
---------------------
--------ROM tested with cab-------
- Elite RC2 -> Work
- Proven 1.08 -> did not work
- Romeo -> did not work
-------- I'm sick of flashing and hard reset, so I'll stop here. If you're already on other ROM. let me know.
Good to see you we're able to get this working.
I didn't modify any part of the RGU file in OEMDrivers, so I'm just gonna drop the new DLL and the RGU/DSM you provided here into my v4.0 kitchen.
NotATreoFan said:
Good to see you we're able to get this working.
I didn't modify any part of the RGU file in OEMDrivers, so I'm just gonna drop the new DLL and the RGU/DSM you provided here into my v4.0 kitchen.
Click to expand...
Click to collapse
Ya, it should work... however, can you check if the RGU/DSM file didn't affect QuickGPS? I didn't make any change there, but just check for sure.
Finally, I can sleep with ease now...
My next wish, somebody make a cab or 2 to make my previous post easier
Only problem with non-cook method will be, if target ROM is not cert patched, or doesn't have certificate loaded from rilphone.dll signature it will refuse to load rilphone.dll due to not being signed with a trusted cert..
hey pandaboy,
tried this on my fuze but didn't work, (using proven rom right now) my wireless radio stops working after. i even tried starting over by deleting your rilphone.dll file and softresetting to get my phone working and did the steps again. no go.
Same, my radio is not working now either. Is there anyway to get my radio back?
just delete the rilphone.dll file from your windows directory and perform a soft reset
y2whisper said:
just delete the rilphone.dll file from your windows directory and perform a soft reset
Click to expand...
Click to collapse
When i try to delete it it says cannot delete the file.
Hi
I have been cooking ROMs for a week or so now and all has been great. I can't recall making any major changes, but I now get the following when the phone does it's initial boot (and every boot after that)...
"The file 'poutlook' cannot be opened. Either it is not signed with a trusted certificate? or one of its components cannot be found..." And I can't do anything. i have searched but i have nothing found related to this problem
I am using (and have been using) IOLITE 20765 ROM and SYS and OEM 5.50.
I have made no major changes - I was testing other ROM's and SYS's, but I have reverted back to 20765 and I get this error - I never got this error on the other versions of ROM's and SYS's.
I have also redownloaded the files and created a new Kitchen folder to cook in...
Please can someone help???
DT
An update.
Redownloaded SYS, ROM, OEM and Kitchen 1.2b and started from scratch. It now works, so I am not sure what the heck I did to the other folders ...but I am sure glad it is functioning again
Can anyone tell me how to associate extensions with a program? any images I have defaults to opening them in the Camera app (not sure why) - I want them like before - except I am not sure what app the standard WM6.1 opens images in - can some one advise please?
Thanks
DT
d_train said:
...but I am sure glad it is functioning again
Click to expand...
Click to collapse
That's why we have HardSPL. Some cooked ROMs will not even boot. In those cases, take battery out, replace battery, turn phone on with camera button held down. This will drop phone into bootloader mode and allow a new ROM to be flashed.
Can anyone tell me how to associate extensions with a program? any images I have defaults to opening them in the Camera app (not sure why) - I want them like before - except I am not sure what app the standard WM6.1 opens images in - can some one advise please?
Click to expand...
Click to collapse
These associations are done in registry. For packages, you need to hunt through the kitchen for the registry and make the appropriate changes.
When I needed to change association for videos to TCPMP, the way I took was:
1) Snapshot of registry
2) Ran TCPMP. Made the association changes in its options.
3) Resnapshot registry.
4) Compare the changes.
5) Scan through the entire kitchen and find and substitute the registry keys in the RGU files and also .dat files
6) An alternative is to create a registry change, to be applied after the main ROM is built (or run at first bootup) like all the registry packages.
Total Commander is great for this. It allow search of strings of text within files in a folder and display all files with the search text. It also allows comparison of 2 files, and highlights the differences. Good luck. This is very time consuming.