Database Users

ROM Kitchen for Herald

Here is a new rom kitchen which also can be used for Herald roms.
Anichillus is working on it to make it completely automatic for Herald. At the moment some files have to be copied manually - but it works.
Just have a look at:
http://forum.xda-developers.com/showthread.php?t=309562

really really sweet, anichillus, awesome! but i'll wait for the Herald compatibility first

Thats definitly good news for the Herald community

Yeah it already works great. I used it to create a wm6 rom based off the wing os dump and it couldn't be easier (coming from a first time cook). I definitely recommend giving it a whirl if you're interested.

Guys, sorry i said that i will upload your kitchen today...but i might not
I think i have been hacked ...so the website doesn't work, and i lost all my stuff cos i had to format my PC (it wouldn't start lol)...I downloaded the one i customised for the hermes and i will start modding on yours, but it might take little more so i don't know if i can finish it today considering i have some personal stuff to do...
Untill then, tell me what RUU to include in yours...or other method for flashing ?
For now it was only meant to be installed in the system drive...and most of us have that drive only for windows.. So i figured that if i am going to modify it, i might as well make it path free so you can install wherever you want...and that also eats little time...
Cheers

anichillus said:
Guys, sorry i said that i will upload your kitchen today...but i might not
I think i have been hacked ...so the website doesn't work, and i lost all my stuff cos i had to format my PC (it wouldn't start lol)...I downloaded the one i customised for the hermes and i will start modding on yours, but it might take little more so i don't know if i can finish it today considering i have some personal stuff to do...
Untill then, tell me what RUU to include in yours...or other method for flashing ?
For now it was only meant to be installed in the system drive...and most of us have that drive only for windows.. So i figured that if i am going to modify it, i might as well make it path free so you can install wherever you want...and that also eats little time...
Cheers
Click to expand...
Click to collapse
Here you are. It is the Aserg-Zip folder only containing teh programs for flashing (perhaps you can delete some unused ones) and i deleted the OS.nb. But the RUU doesn´t work for herald.
An sorry for your PC - don´t get in trouble.

The Begining! The search for a real sable flash utility.

We have heard that there might be such a thing as a sable_ruu.exe flash utility for the sable if anybody finds any such utility for the 69XX phones. Please inform or post such a beast. (This is unconfirmed until utility is found and tested as well as any accompanying rom that will flash with it)

see : http://forum.xda-developers.com/showthread.php?t=313403&page=3
Jussi77 has uploaded the utility

Just for reference here is the link to this update utility. I will see what can be done by looking at the known 65XX utility. This seems what hp would use themselves for flashing without the guider file from the 65XX. Then it would just be a matter of trapping some code to remove device authentication and we have ourselves a utility. (I havent done this in a long time)
Here it is for your studying purposes!!!
http://forum.xda-developers.com/attachment.php?attachmentid=43063&d=1183675670
And thank you Jussi77

Does anybody know first hand the real differences of the 65XX and 69XX... I mean detailed hardware differences. I wish to see how compatible a possible rom might be from each other. (just os)

Where could I find original English ROM in the .nbf format for hw6915?

Ive checked it and it is the full fledge flash utility for the HTC Sable. Funny I'm trying to look at this and don't even have a 69XX device yet!! Should be in the mail LOL
On the other hand if somebody has a stock NBF OS and EXTROM NBF that is known working with the 69XX, factory English is fine; then please inform us of this. (This can expedite work incredibly.) Or if not and you do know how to DUMP your rom please inform us as well.
IF SOMEBODY ALREADY HAS THESE (STOCK OS,EXT ROM NBFS) PLEASE INFORM US OF THIS

process
i could be like this
1) dump the current rom
http://forum.xda-developers.com/archive/index.php/t-306293.html
2) process dump.bin to nbf files
http://forum.xda-developers.com/archive/index.php/t-306293.html
3) verify the flasher by flashing above mentioned files back to hw69xx
4) if that worked ok, i would try to modify/replace nbf files with "some other" files , patch the flasher (checksum checking) and flash again

I have a supposed dump from a 6915, however it is a straight dump and I have not found how to convert it yet. The task is further complicated since these HP people haven't ever released ANY kind of update... so nothing to compare it to. If we had just one CEOS.NBF file to work from for this device we could conceivably start a wm6 version utilizing the current OEM drivers from WM5.

hmm
i do have ceos.nbf for hw69xx... i'll check with hp (since im under nda) if i can make it public...

Jussi77 said:
i do have ceos.nbf for hw69xx... i'll check with hp (since im under nda) if i can make it public...
Click to expand...
Click to collapse
probably cant since its windows licence which is going to be vailated...

maybe...
maybe hp could post initial firmware (which contains all the nbf files)

HP has release a so called driver update for the HW6910 vodafone on the website, sadly it is just a cab install, which may means that HP does not want to release update in the ROM NBF format so to prevent users from play with the ROM switching. Let's wait and see.

Remember guys this is a HTC device so I am willing to bet that somebody at HTC might have some information on what we need.

machbaba said:
HP has release a so called driver update for the HW6910 vodafone on the website, sadly it is just a cab install, which may means that HP does not want to release update in the ROM NBF format so to prevent users from play with the ROM switching. Let's wait and see.
Click to expand...
Click to collapse
I think its not that.. HP does not have any update to english OS so there is no need to post image files if all the english devices are at latest version... when / if they do an update, then you will have image on their site...
But WM6 guess wont happen...

I have checked the list of the bug fixes of the cab update, it includes a lot OS side fix, naturally this can be included in a full ROM update but as HP released it as CAB update, i really doubt if they will release a ROM update in any near future.

The OS side fixes seem to be related to how the unit interfaces with their particular network(vodafone). That's actually not bad news since this was probably a vodafone pushed update not an hp issue. We might get better response from the carriers than HP, they have more muscle than a bunch of online guys *****ing about no WM6.

Found some interesting news. The recent flash utility found was taken from a radio rom update found on HPs site..... HP is having problems with this radio rom update and has informed many customers that they are aware of the problem and if the update damages their device they will have to send it in for repairs. So this might point to problems with the flash utility itself (maybe just the radio rom), they have said that they will be updating the update soon....
Maybe this is why HP doesn't release a rom update, they might be getting sloppy and don't want to risk it.
I hope this little update bricks enough phones so that they will have to release a "restore" utility.. Sorry I don't wish anybodies phones to be bricked but if it happened already!

which driverbase to use
anyone got a clue which wm6 ceos.nbf would contain most probaple set of drivers compatible with hw69xx ?

proceed..?
i did some testing and while i threw in some xda wm6 ceos.nbf the obvious thing happened -> Unit just froze during flashing ceos.nbf and then it locked into BL mode. I'll try to push valid rom back and then we only need correct ceos.nbf

Yeah it wont work. The rom alone as WM6 put into an NBF format for that particular phone at the right offset with the right drivers will start. However the file names being the same extension (NBF) says nothing of the formatting let alone the drivers for the rom. Is like mixing a poddle with a shark, LOL...
What we still need is an original WM5 CEOS.NBF rom not a dump, and you know what we should all have this at least, dont you get a factory restore cd with any bought pc with an os. You have already paid for the rights to use the PC with the os and as well as a means to restore your investment in case of failure like ALL pcs out there.
I wont ask for HP to create WM6, thats their choice, but for the love of god release a freaking restore rom or update for WM5. Is something I already paid to use illegal for me to have a copy off? NO ITS NOT!

[Help Request] Live ROM Update

Objective :
Create an Update Utility based on the Windows Update in Official ROMs
Description :
My idea is to create a ROM that can be updated without the need of RUU we use now. For example, you have Core2.0n version of my ROM and since you installed it, I created another version, for example Core3. In order to update you'd normally have to download the latest ROM to your PC and re-flash your HTC Wizard.
I want to allow you to go online directly from your Wizard and check for new version. If new version found, then automatically download and flash. All you'd need is an Internet connection.
Limits/Problems :
There are some problems about this. This is where I need help.
Usually the PPC turns OFF and then the RUU writes the ROM. With the way I want it, the ROM must be written while the device is ON...and then it would do a Hard Reset in order to complete the Update.
I don't know yet if this is possible, but I am willing to try.
What I need :
People with Assembler knowledge
People with good PPC knowledge and understanding
Huge amount of luck
I remember someone here already tried to restore the Windows Update components. Unfortunately I can't remember who and if he succeeded or not.
I'll search for his thread and post any update.
The ORIGINAL thread is located HERE. Please feel free to join the development crew.​

The idea looks cool, it will allow us to redistribute updates and fixes to our roms more easy
But we have to figure out how the windows update feature is working, and how it manages to flash the downloaded update
I think that it downloads the updates to the storage card (in most cases there is not enough space in storage to store whole rom image) and then instructs the boot loader to flash the file from the card (this way it will be logical)
Also that way will be similar for all devices not just the wizard.
So the rom cookers can personalize windows update settings to update their roms trough it (of course separetely for every device)

xplode said:
The idea looks cool, it will allow us to redistribute updates and fixes to our roms more easy
But we have to figure out how the windows update feature is working, and how it manages to flash the downloaded update
I think that it downloads the updates to the storage card (in most cases there is not enough space in storage to store whole rom image) and then instructs the boot loader to flash the file from the card (this way it will be logical)
Click to expand...
Click to collapse
I think we'll try to do that. However I doubt that Microsoft intended to use a Storage Card for update. This makes me curious on what method they would have used.
Other problem would be error checking...We must know for certain the OS is not corrupted before attempting the update.
Maybe I didn't said it...but I will say it now. My intention is only to flash through the air an OS, that means no other components, like SPL, IPL , radio or SplashScreens will be altered by the Update so no chance of bricking the device plus making the whole process easier to accomplish.
Other idea is to study the way that security programs (anti theft) use they're software so that the data is included in the rom with a simple install.(they say the program will be there even after a hard reset...though i didn't tried any)

I am sad to notice so little enthusiasm from people around here.
This would affect chefs more than regular people but still.
Back to business...
Questions :
Is it possible to flash directly the ROM with the PDA turned on ?
If so, how can we access the ROM directly ?
How to use .pkg ? Can we make use of them ?
Considering the Update deals only with relative minor changes, this means we can leave the XIP out. We can think of new Builds as major upgrades and require the use of normal flash. The big problem..and unfortunately the thing I know less about it's managing to insert the new update in a very "raw" manner.
I am firmly convinced that few people here posses the knowledge to do this.
Please come in front and let's make this thing happen.
I could try to reverse engineer the default windows update but it would take a great deal of time and I would probably get stuck without some help.
P.S. I managed to find the thread I was talking about before. It's located here.

I think is a great idea my friend. However there are many things to think before trying to do it. First of all to flash the new files you shall need to make a pdoc write but i have now idea how can be made via the device itself.
Where are the "patches" being stored before they are updated?
May be the process of hard reset shold be manual. This are only some toughts.

i would help u as much as i can...

great idea !
the update can be on the storage card and one can put the device into
bootloader/update mode by running this little program in the windows dir
to switch it to the 3 color screen.
With this WM5torage program i can acces the romchip itself and write it.
not sure wether it messes up things.

not sure if this will delete contents of the storagecard itself...
another thought... why not make the updatepackage and let windowsupdate install it for you ?

I think the best way to procede is to find out how to make a pkg file (faria seems to know) and then to sniff what the windows update app does when connecting to the MS server and see if we can emulate that on a test server.

Midget_1990 said:
I think the best way to procede is to find out how to make a pkg file (faria seems to know) and then to sniff what the windows update app does when connecting to the MS server and see if we can emulate that on a test server.
Click to expand...
Click to collapse
All your ideas are great. But this was exactly what i had in mind. It seems the easiest way....only so little time right now. So...where`s Faria ?
P.S. Sorry for late reply...i thought ppl don`t care and i didn`t checked the thread

Does somebody of you have such a pkg file?
As I understand it right, this file will be delivered by windows update to the client?
I never got an Update via Windows Update... Everytime I try, there are no updates available ^^
Sniffing the Windows Update would be easy, I think. I could bet that all this stuff is done via a Webservice. That's the I would do it

Has anyone ever updated anything using that Windows Update? It's highly unlikely it will download a whole new ROM, maybe just some cabs which won't touch the ROM altogether, just mess around in registry.
And who needs to keep the device on while updating if you'd make a hard reset afterwards?
It can even be done now...
any back-up program
a cook who's willing to release ROMS on some stable host (NOT rapidshare where address changes)
a diff utility to download only the parts of the ROM that changed
A small app which writes XXXXIMG.BIN to storage card and enters bootloader.
Much harder task is to get rid of ROMs altogether and take control of the only advantage they give: XIP. I mean, why don't use a tool to convert the new apps to XIP format making them a part of the ROM?

@anichillus
I can provide u with the package but it will take some time..u see i have WM6 Emulator..but cant make it to use Internet Connection of my PC..so the Update manager starts but doesent download (no connectivity)..will see what i can do

i got the internet working..but when i click update..it doesent give any packages..what now

did i brick my device with rilphone.dll??

I installed the radio stated by energy rom and replaced rilphone.dll....now the radio doesn't work....what am i doing wrong?
the phone boots up fine, i just cant make calls...help please
thanks!
rilphone_2.07
Leo_RADIO_2.07.50.27_2
did i brick it?

remove rillphone and reboot so the original comes back from rom. should be ok then.
no one has shown any benefit or even much success messing with rillphone.

samsamuel said:
remove rillphone and reboot so the original comes back from rom. should be ok then.
no one has shown any benefit or even much success messing with rillphone
Click to expand...
Click to collapse
Not entirely true.
http://forum.xda-developers.com/showthread.php?t=494632
If you want to make .cabs for the rilphone.dll files just use Chainfire method for creating .cab for windows mobile internal or driver .dll's
http://forum.xda-developers.com/showthread.php?t=495145

true, it can be cooked in, or cab installed, but you cant just copy it over, like most people try to do, and to be honest, anyone seen any difference when matching it to the radio? (cos if they HAVE, then maybe ill have a go!)

[Q] The files inside modules are required for cooking 6.1?

Hello ppl, after so much cooking in 6.5 i decide to play a lil into 6.1... well i never cook for 6.1
Ok here is teh question as the title says... i jump into 21057 build 6.1 and I have a weird thing that is annoying... A mouse pointer (a lil arrow) does any body knows how to get rid of that arrow in my screen?
thanks a lot
Im usin HTC Hermes 6.1 build 21057 QVGA 0409 EVK 1.8.2

So 71 views and none idea? OMG i need to start over with an old build... maybe is a feature in the gwes shell or other core file

mmmm interesting experience... if I reply myself in this thread, i gain 18 views... and none answer... well... i talked last night with Da_G, he told me that some driver of my old OEM is causing troubles.. maybe the ddi.dll:
1.- made a search... then i see i had it twice... and i see a file inside a module.... is aid!!! OMG that is stupid!!!
2.- went running to my OEMdrivers and check that module "ace_ddi.dll" and yes it has a file ace_ddi.ddl inside so i said FK!!!! checkk all my modules and fK!!! all has the same issue... but the kitchen ddint told me about it.... i erase them all... and now the platform rebuilder crash...
The new question is... In WM6.1 the file inside the modules are needed?

+ Que PPC said:
mmmm interesting experience... if I reply myself in this thread, i gain 18 views... and none answer... well... i talked last night with Da_G, he told me that some driver of my old OEM is causing troubles.. maybe the ddi.dll:
1.- made a search... then i see i had it twice... and i see a file inside a module.... is aid!!! OMG that is stupid!!!
2.- went running to my OEMdrivers and check that module "ace_ddi.dll" and yes it has a file ace_ddi.ddl inside so i said FK!!!! checkk all my modules and fK!!! all has the same issue... but the kitchen ddint told me about it.... i erase them all... and now the platform rebuilder crash...
The new question is... In WM6.1 the file inside the modules are needed?
Click to expand...
Click to collapse
to my experience - NO
i did always delete all of them..
did you track your crash down to OEM/SYS?

+ Que PPC said:
mmmm interesting experience... if I reply myself in this thread, i gain 18 views... and none answer... well... i talked last night with Da_G, he told me that some driver of my old OEM is causing troubles.. maybe the ddi.dll:
1.- made a search... then i see i had it twice... and i see a file inside a module.... is aid!!! OMG that is stupid!!!
2.- went running to my OEMdrivers and check that module "ace_ddi.dll" and yes it has a file ace_ddi.ddl inside so i said FK!!!! checkk all my modules and fK!!! all has the same issue... but the kitchen ddint told me about it.... i erase them all... and now the platform rebuilder crash...
The new question is... In WM6.1 the file inside the modules are needed?
Click to expand...
Click to collapse
What kitchen did you use to dump the rom? I ask because I've played around some with cooking 6.1 roms and using EVK to dump shipped roms (20771 and 20779) for the raphael, and every time I do it, I get the files inside of modules phenomenon. And let me say, the roms I cooked SUCKED! They had all sorts of issues (even after deleting all the files). I recently dumped the 20779 rom with OSKitchen (first time I'd ever used it) to get a few drivers out, and it dumped everything properly. I'm not sure if I was doing something wrong or not with EVK-is there a setting for dumping 6.1 roms? I don't have much experience dumping roms, since there hasn't been a new one for the Raph in over a year and Da_G basically did all the hard work setting up 6.5 kitchens. I removed recmod.exe from the tools folder (thinking maybe it was kicking in somehow and recmodding the modules), but that didn't make a difference.
Anyway, you may want to try a different kitchen if you're using EVK. I also didn't get any file/module errors, and it was just blind luck that I found out the every IMGFS module had a file inside of it (but not in the dump, so I guess that's a good thing, although the rom I was working on was a turd).

Nope not necassary.
You need GReloc to reloc sys, some changes to your kitchen batch and a 6.1 nk.exe if you ask me.
+ Que PPC said:
mmmm interesting experience... if I reply myself in this thread, i gain 18 views... and none answer... well... i talked last night with Da_G, he told me that some driver of my old OEM is causing troubles.. maybe the ddi.dll:
1.- made a search... then i see i had it twice... and i see a file inside a module.... is aid!!! OMG that is stupid!!!
2.- went running to my OEMdrivers and check that module "ace_ddi.dll" and yes it has a file ace_ddi.ddl inside so i said FK!!!! checkk all my modules and fK!!! all has the same issue... but the kitchen ddint told me about it.... i erase them all... and now the platform rebuilder crash...
The new question is... In WM6.1 the file inside the modules are needed?
Click to expand...
Click to collapse

Farmer Ted said:
What kitchen did you use to dump the rom? I ask because I've played around some with cooking 6.1 roms and using EVK to dump shipped roms (20771 and 20779) for the raphael, and every time I do it, I get the files inside of modules phenomenon. And let me say, the roms I cooked SUCKED! They had all sorts of issues (even after deleting all the files). I recently dumped the 20779 rom with OSKitchen (first time I'd ever used it) to get a few drivers out, and it dumped everything properly. I'm not sure if I was doing something wrong or not with EVK-is there a setting for dumping 6.1 roms? I don't have much experience dumping roms, since there hasn't been a new one for the Raph in over a year and Da_G basically did all the hard work setting up 6.5 kitchens. I removed recmod.exe from the tools folder (thinking maybe it was kicking in somehow and recmodding the modules), but that didn't make a difference.
Anyway, you may want to try a different kitchen if you're using EVK. I also didn't get any file/module errors, and it was just blind luck that I found out the every IMGFS module had a file inside of it (but not in the dump, so I guess that's a good thing, although the rom I was working on was a turd).
Click to expand...
Click to collapse
Thats true, my 6.1 rom is a mess i will try that thanks
Laurentius26 said:
Nope not necassary.
You need GReloc to reloc sys, some changes to your kitchen batch and a 6.1 nk.exe if you ask me.
Click to expand...
Click to collapse
mmm interesting where can I learn more about that Changes you talk about?

to be homest i have the same thing
when i look at modules i have a dll in it called the same as folder
i have this since the beginning i started cooking and thought it whas meant this way but here im reading its not:-o
will the rom become faster if i delete all the dll's from the modules?
definetly gonna give it a go tomorrow:-o

yes... we are wrong, as the kitchen warns us when in SYS and EXT is a module with a file inside... but it dont happends when we got them in OEM.
The idea to have modules instead of files is cause the file is already recmoded when the cooking process starts at IMGFS merging (maybe im wrong) doing the recmod into slots by the reloc tool... so... in 6.1 the Greloc did it in the oem and goes wrong, and the same happends for WMreloc for 6.5 cooking.
and yes having modules allows us to have correctly recmoded files at the end to have faster roms so... the files inside modules is a wrong way to cook
i will try to dump again the stock... in OSkitchen zero... then i will add it into my 6.1 kitchen... but something is weird in my case... cause my device dont has stock rom for 6.1 ( we have wm6 shipped roms) but i will try it anyways

It never affected me (I think, lol) but you can use PreKitchen tool to delete all files with the same name as the folders that they are in. Its a lot quicker then manually deleting each duplicate

seeM_ZA said:
It never affected me (I think, lol) but you can use PreKitchen tool to delete all files with the same name as the folders that they are in. Its a lot quicker then manually deleting each duplicate
Click to expand...
Click to collapse
muchias gracias for this s my entire ext folder is full of files inside modules:S
:verry nice program and verry quick
edit2: gonna flash my new rom without the files inside modules and see what happens
i deleted them from the oemdrivers folder and all the ext packages(im hoping for some nice extra speed)
edit3: just looked at the kitchens i made for tp2 and leo and they have the exact same thing files in modules in ext packages and oemdrivers:s
and the strange thing none of the kitchens told me this and all gave nice working roms where evrything works like it should:S
edit4: hmmm looks like weather animation is slower after deleting all the files in modules:s

Im pretty sure it shouldnt affect the speed at all :? Because if you look in the dump folder it doesn't happen there. Maybe its just in your head? Lol, I could be wrong though, so please correct me if I am.

seeM_ZA said:
Im pretty sure it shouldnt affect the speed at all :? Because if you look in the dump folder it doesn't happen there. Maybe its just in your head? Lol, I could be wrong though, so please correct me if I am.
Click to expand...
Click to collapse
for the weather animation im quite sure as yesterday i let it run the weather animation for rain ten times after eachother and it whas ten times smooth
now i did it 5 times and 5 times with stuttering in it:s

Strange :? You sure you didnt change anything else?

seeM_ZA said:
Strange :? You sure you didnt change anything else?
Click to expand...
Click to collapse
100% sure
i downloaded the program you mentioned and let it run over the entire ktichen so all files in flders with the same name got deleted then i cooked the rom and flashed it
gonna reflash the rom i used before i deleted all those files to doucble check if im right about the weather animation but im 99% sure about the outcome

Try task29 before you reflash also. Otherwise I have no idea glad you backed up though hehe

seeM_ZA said:
Try task29 before you reflash also. Otherwise I have no idea glad you backed up though hehe
Click to expand...
Click to collapse
lol it went from rain to clouded
gonna flash back to the rom without the dll in the modules and do a task 29 before flashing and use it a day then i know for sure if its faster or slower

miniterror said:
lol it went from rain to clouded
gonna flash back to the rom without the dll in the modules and do a task 29 before flashing and use it a day then i know for sure if its faster or slower
Click to expand...
Click to collapse
Haha, I hope it works out for you bro
I tested out my weather animations and they're perfectly fine, without the dlls in modules. Im running 21909 and sense 2016 CFC'ed (from Leo 3.04) on TP2.

So... laurentius, how can I use Greloc instead of WMreloc in EVK to cook 6.1 ROMs???
i have this using WMReloc in a vanilla ROM 6.1
Memory Map...
SLOT 0: 0x02000000 - 0x01660000 (END: 0x00060000, 64 MODULES)
0x02000000 - 0x01fe0000 - ROM 0
0x01fa0000 - 0x01e20000 - ROM 1
SLOT 1: 0x04000000 - 0x02020000 (END: 0x02020000, 253 MODULES)
RAM IMAGE: 0x80000000 - 0x8029cc34
RAM: 0x8029d000 - 0x802cc000 - Used for kernel modules
0x802cc000 - 0x83a00000 - 55 MB free
... done!
I guess this 64 Modules in slot 0 are causing troubles

I'm not too familiar with 6.1 but what I do know is you want as little modules as possible in slot 0, so ideally you want no modules there.
EDIT: Wrong info here, my bad.
All the best