Related
We have lost the exteneded roms again.
This is the 2nd time that I know of.
I think this has to do with the fact that they were not linked to post thus unkonw files get killed. I read that some were when I first came here.
I have most of them and will start uploading them again, linking them to a post.
Anybody have a better idea or know why they have gone?
Not sure whether they've been deleted or not, unless you have been reposting. They are under BlueAngel_Roms instead of Extended_Roms. Things seem to keep getting moved.
And what are they doing there ?
Sure I have been uploading to ExtenedRoms for over an hour now.
I will move the buggers!
Rename The Folder Exteneded_Roms
Clean up the file names
Gee I love house work thought I was would be cooking in the Rom Kitchen, but no.
We are going to have to post the links as they got killed once before.
Thought you were out.
Can you belive this!
Got a folder name that says "Dont touch MDAIIIUser Uploading" and we have dowloades.
You around need so help.
ok done
cleaned up the Exteneded_Roms
Will post in the morning.
We need to take these apart and find what version they are then rename them.
ftp://xda:[email protected]/BlueAngel/Exteneded_Roms/IIs Asia WWE Ext ROM.zip
ftp://xda:[email protected]/BlueAngel/Exteneded_Roms/Seimens_SX66_Ext_ROM_ENG.zip
ftp://xda:[email protected]_MDAIII_Extended_Rom_Inc_DeviceInfo.zip
Do you need some assistance with the Excel sheet for ROM Versions and contained cab files?
Is there a neater way of structuring the ftp server directories? Is there any way of setting folder permissions on the server for read/write only and not alter/delete?
Bebbo
Do I need help in the Exteneded Rom Kitchen. Does the .... (ok no bad jokes)
Sure do BIG Time!!! Its not my kitchen, I just work there!
The Idea of the Kitchen is not realy to find out what version number Orange Rom A has for an application but to see if Orange's Rom A has application / Patches that are better than our base.
The Sheet just is a list of the files which go:
Base (I-mate) + Rom A + Rom B = Extended Rom Kitchen (ERK) Rom
My end goal is to generate a ERK Rom Version which is as upto date as possible.
And have this info on wiki so we dont need to hunt for it.
How far am I, Well The UK orange rom has been looked at but info not posted in the kitchen.
( I think RTP worked on that but I am not sure as I was haveing PMs with few people about that rom. )
We have the 3 roms above that need to be looked and info posted in the Kitchen and added to the Excel Sheet.
The Excel Sheet needs to be made to look nice so the rest of us can undersatand it.
We need to check against the "List of know Blue angels" to see what rom is missing and see if we can find it.
Oh yes and its friday, I get to pick my kids as its "The 3rd weekend of every month" and as my ex-wife has got a date, thus By 12:00.
Chances of me doing much till monday are ZERO.
So you want a job, pay is s**t, hours are bad, it can get hot in the kitchen when there is a fire and you lose all your stuff.
You need to understand Roms, read cab files, use your brain and most of all admit to the fact that you don't know everything and thus ask.
I am looking for Pastry Chef as well. One that can write applications.
Is there any way of setting folder permissions on the server for read/write only and not alter/delete?
Click to expand...
Click to collapse
Given that at the moment we are all the user XDA, I would say no.
What we need is a "BA_Admin" that revokes the rights of XDA to Read only, then we just get into the next problem, the person that posted (XDA) can't update it, so he needs to be BA_Admin...
The FTP site is a public place and like Toilets some people just can't pee in the Pot like the rest of us and sonebody has to clean up the mess.
Is there a neater way of structuring the ftp server directories?
Click to expand...
Click to collapse
Got some ideas, then share them with us.
Will have a look at dir structure but seems reasonable to me at the moment (Though Extended is the correct spelling ). Will use my WinCE CAB Manager to see what if anything is different on rom's you haven't had chance to view yet and generally assist where I can.
I will have a look at the orange rom as well, time permitting.
Would it be better to extract the .nbf files to sub dirs under the Extended_ROMS dir and have similar structure for radio and CE ROM?
ie ->
BlueAngel/Extended_Roms/Imate_PDA2k_WWE_12200_162_10600_SHIP/ms_.nbf
(With cabs extracted as well under a cabs sub dir?)
BlueAngel/CE_Roms/Imate_PDA2k_WWE_12200_162_10600_SHIP/nk.nbf
BlueAngel/Radio_Roms/Imate_PDA2k_WWE_12200_162_10600_SHIP/radio_.nbf
Or leave as is and use the kitchen with a CAB's dir under it with all known versions of cab files so we can select the most appropriate ones?
I've posted the document on the Orange 1.12.139 ROM into the Kitchen. It's fairly large since there is so much in the Orange ROM.
Here's a link:
ftp://xda:[email protected]_1_22/Docs/Orange_WWE_1.12.139_ExtROM.doc
Unfortunately nothing really new though (Wish I had known you were doing this rom - just wasted 2 hours!).
I haven't looked at the WModem.exe update yet - any ideas what this is for?
Who keeps moving files in the BlueAngel section of the FTP server? Makes life difficult having to keep searching each time. Please let us all know what you are trying to achieve as it keeps breaking links on other web pages!
Running it comes up with this text:
The utility will simulate this device as a wireless modem, and let your PC/Notebook be connected to network wirelessly.
Before you press the 'Start' button, please make sure you have connected the device to your PC/Notebook by serial or IrDA connection and disabled the Activesync.
When the wireless modem is activated you will not be able to receive any voice calls.
Click to expand...
Click to collapse
It then gives options for Serial, IrDA, USB and Bluetooth. Start, Stop and View Log buttons. Plus connection status LEDs - Connection, Send Data and Receive Data.
I've never tried it. I tend to use something more direct for dialup from my laptop.
OK guys!!!
I don't know what your naming system is but I've uploaded the O2 UK EXT ROM and I've called it "O2_UK_XDAIIs_Ext_ROM_112178_WWE.zip". This one is the original from my device.
Regards,
Dom
Ext_ROM password??
MDAIIIUser said:
ok done
cleaned up the Exteneded_Roms
Will post in the morning.
We need to take these apart and find what version they are then rename them.
ftp://xda:[email protected]/BlueAngel/Exteneded_Roms/IIs Asia WWE Ext ROM.zip
ftp://xda:[email protected]/BlueAngel/Exteneded_Roms/Seimens_SX66_Ext_ROM_ENG.zip
ftp://xda:[email protected]_MDAIII_Extended_Rom_Inc_DeviceInfo.zip
Click to expand...
Click to collapse
Any known pw's for those .nbf files? I tried Rom editor but couldn't recognize the pw's
Re: Ext_ROM password??
Cyber-mate said:
Any known pw's for those .nbf files? I tried Rom editor but couldn't recognize the pw's
Click to expand...
Click to collapse
They aren't .nbf files???????? They are zipped up (rar'd up) cab files extracted from the extended roms.
+*+*+*+ FOR INFO +*+*+*+
The xda3nbftool has an extra command line option of -t which attempts to discover the xor key used to encrypt the .nbf files. This seems to work well for all files except the radio_.nbf file which causes it problems. Try it on roms that you are having problems with to see if it is the correct key. You can check the resulting .nba file with a hex editor to ensure the PH20B and other data is shown at the beginning of the .nba file.
+*+*+*+*+*+*+*+*+*+*+*+
I have pulled the above ext roms apart and the version numbers are as follows:
IIs Asia WWE Ext ROM.zip = Version "1.12.925 WWE"
Seimens_SX66_Ext_ROM_ENG.zip = Version "1.20.115 WWE"
T-Mobile_MDAIII_Extended_Rom_Inc_DeviceInfo.zip = Version "1.06.117 WWE"
Files renamed appropriately so any links will now be broken (plus the fact that some kindly person has renamed the Extended ROM directory to its correct spelling!)
Hello,
As everybody already knows there are some serous problems with Qtek9090 device type models and carkits. A nice echo is produced when somebody is calling. I have a wavedev.dll file that should resolve this issue but I can't replace it on my Qtek9090 because it's a system file. How can I force this replacement?
Thanxz for any response, I bought this complete set and i'm thinking about it to return it. Operator T-Mobile, rom1.40, radio 1.20.
Peterpanman.
rename existing wavedev.dll to wavedev.bak, copy the new file and reboot.
Just curious but is it definitely Radio 1.20 or 1.12 as 1.13 is the latest I know of....
wavdev.dll
hello mamaich,
of course i can not rename the file because it is a system file, in use, attributes can not be removed. anybody has another idea?
peter
(sorry for the type mismatch radio 1.12)
Re: wavdev.dll
1. All files in ROM can be freely overwritten even if they are loaded by applications. But they of cause cannot be renamed.
2. Files in object store that are opened cannot be overwriten. So if you cannot do that - than this file is contained in object store and was already updated, probably by some CAB from extended ROM.
3. WM2003 allowed opened files from object store to be renamed. According to your post you have 2003SE.
If you cannot rename this file - the file may be in ROM, so you can freely overwrite it with explorer.
If you cannot overwrite it - you still can rename it. In this case after renaming there would 2 copies of file. One with the new name, and the old wavedev.dll would reappear (the ROM version would be visible again).
In some rare cases some program may completely prohibit access to the file, but i've never seen that for DLLs. Unless you are using some PocketPC antivirus (a completely silly idea by the way). In this case uninstall antivir and do a soft reset.
WM2005 does not allow user to overwrite ROM files, but they can be still overwritten by OS itself, for example by creating a custom CAB file. I do this in my WM5 patches.
Not working
Hello mamaich,
Thanks for the complete answer but unfortunally none of these options work. Renaming the file does not create a new copy of the renamed file. I can't even copy the file, it says \\Windows\wavedev.dll access denied. Maby you can tell me how to create a .cab file so that this file is copied and overwritten? something with .net or something?
Thanxz,
Peter
Re: Not working
Peterpanman said:
Hello mamaich,
Thanks for the complete answer but unfortunally none of these options work. Renaming the file does not create a new copy of the renamed file. I can't even copy the file, it says \\Windows\wavedev.dll access denied. Maby you can tell me how to create a .cab file so that this file is copied and overwritten? something with .net or something?
Thanxz,
Peter
Click to expand...
Click to collapse
You can use WinCe Cab Manager
So I thought it would be worthwhile to create a thread focusing on modified "cappackage.pxp" files. These are the files which control the default carrier specific configurations. In my case, I am running the Aussie "Three" WM6 OS, however I wanted some, but not all, of the ATT customizations. For example, I wanted the proxy tool, the logos and the certs . . . Attached is a modified version of the ATT cappackage.pxp file. I had difficulty configuring WindowsMobileLive.cab and the HTC task manager to automatically install as part of this new file so I will post those cab files as well for convenience (for those who may want it).
If you have a customized cappackage.pxp, please post it in this thread and describe how it has been modified so everyone can decide which they may want to use.
Here are the changes I made to the cappackage.pxp file. Note, all of these .cab files should be possible to install directly simply by extracting from original ATT WM6 cappackage.pxp in case you happen to need one of them:
delete getgood.cab
delete getmail.cab
delete realplayer.cab
delete getmobitv.cab
delete cmradio.cab
delete attmallandmusic.cab
delete musicid.cab
delete jarguarrm.cab
delete gettelenav.cab
alter "Att_Settings.prov.xml" to remove messaging and Windows Mobile Live registry customizations
add install of new devstate.dll (exists in 3AUS cappackage.pxp and also in ROW 2.23 cappackage.pxp)
ABS
EDITED 12-30-2007: Note - this altered cappackage.pxp file is based off the "leaked" ATT WM6 ROM.
abs99 said:
So I thought it would be worthwhile to create a thread focusing on modified "cappackage.pxp" files. These are the files which control the default carrier specific configurations. In my case, I am running the Aussie "Three" WM6 OS, however I wanted some, but not all, of the ATT customizations. For example, I wanted the proxy tool, the logos and the certs . . . Attached is a modified version of the ATT cappackage.pxp file. I had difficulty configuring WindowsMobileLive.cab and the HTC task manager to automatically install as part of this new file so I will post those cab files as well for convenience (for those who may want it).
If you have a customized cappackage.pxp, please post it in this thread and describe how it has been modified so everyone can decide which they may want to use.
Here are the changes I made to the cappackage.pxp file. Note, all of these .cab files should be possible to install directly simply by extracting from original ATT WM6 cappackage.pxp in case you happen to need one of them:
delete getgood.cab
delete getmail.cab
delete realplayer.cab
delete getmobitv.cab
delete cmradio.cab
delete attmallandmusic.cab
delete musicid.cab
delete jarguarrm.cab
delete gettelenav.cab
alter "Att_Settings.prov.xml" to remove messaging and Windows Mobile Live registry customizations
add install of new devstate.dll (exists in 3AUS cappackage.pxp and also in ROW 2.23 cappackage.pxp)
ABS
Click to expand...
Click to collapse
Thanks, any idea if we can add another carrier in the carrier_db file that isn't there?
john_99 said:
Thanks, any idea if we can add another carrier in the carrier_db file that isn't there?
Click to expand...
Click to collapse
I honestly do not know. Sorry. You might ask Olipro as he seems to be very knowledgeable.
abs99, what tool did you use to repackage your PXP file. I've tried several archive tools to .ZIP and rename, but no joy. I've looked, but can't find any info on PXP file creation. Surely, I'm missing something simple here.
TIA
I found that "winrar" can handle the files without a problem. I had also noticed that the date stamps were the same for all the files in the original package, so I also use a tool called "stamp it" to set all the dates on all the files in the new package to the same original date.
thanks. I found that 7-zip is working too.
Now, the next step, I'm trying to mod the capdata.xml file and for whatever reason the device will not recognize it after my mods.
Here's my version of an ATT config file:
Code:
<?xml version="1.0" encoding="utf-8" ?>
- <Varnish xmlns="http://www.ephox.com/product/editliveforxml/document/Untitled20062026011007629">
<Version />
<Notes />
<UpgradePath>always|</UpgradePath>
- <PolA>
- <Certificates>
<File>CingularCert.prov.xml</File>
</Certificates>
- <Certificates>
<File>Class3_PCA_G2_v2.xml</File>
</Certificates>
- <Certificates>
<File>entrust_gssl_ca.prov.xml</File>
</Certificates>
- <Certificates>
<File>RSA1024RootCA.prov.xml</File>
</Certificates>
- <Certificates>
<File>RSA2048RootCA.prov.xml</File>
</Certificates>
- <Certificates>
<File>VeriSign_C3_PCA_G3v2.prov.xml</File>
</Certificates>
- <Ringtone>
<File>AT&T Tone.wav</File>
</Ringtone>
- <ProvXML>
<File>ATT_Settings.prov.xml</File>
</ProvXML>
- <ProvXML>
<File>MSFPHeartbeat.prov.xml</File>
</ProvXML>
- <ProvXML>
<File>ResetRequired.prov.xml</File>
</ProvXML>
- <InstallApp>
<File>WindowsLive.CAB</File>
</InstallApp>
- <InstallApp>
<File>ATT_Theme.CAB</File>
</InstallApp>
- <InstallApp>
<File>ProxyManager.CAB</File>
</InstallApp>
- <InstallApp>
<File>ATT_Content.cab</File>
</InstallApp>
- <ExtractZip>
<From>DevState.zip</From>
<To>\Windows</To>
</ExtractZip>
</PolA>
- <Welcome>
<WaitImage>E_PolishImage.bmp</WaitImage>
</Welcome>
- <Sweatshop>
<AccountName>GEN</AccountName>
<VarnishName>ENG</VarnishName>
<BuildName>005</BuildName>
<User>[email protected]</User>
<Environment>Sweatshop QA Staging</Environment>
<CoreVersion>1.9.9</CoreVersion>
<Treo750Version>3.0.0</Treo750Version>
<DateStamp>Wed Aug 22 6:10:15 PDT 2007</DateStamp>
</Sweatshop>
</Varnish>
Any thoughts? This is just a basic mod and plan to get more detailed configs in there once I figure out what I'm doing wrong.
TIA
The issue with this file may be that editor you are using is adding "white space". I found that some editors caused this to occur. I ended up the file in notepad to avoid the problem as it was a real mess to deal with any other way. You should open the original unedited file and your new edited file in notepad and compare both. For whatever reason, the OS does not like to deal with a properly formatted .xml file!
Thanks mate, the white space and file size were the culprit. Was trying to cheat and use MS xmlnotepad - very easy to use, but it added the whitespace as it made it pretty to look at. I also was trying to cram too much into my archive; the extracted archives need to fit in the 8.4mb along with the archive itself.
Attached is a custom CapPackage.PXP with the following (based from ATT 2.25 ROW, CapPackage.PXP):
ATT Theme
Regional Settings: US, - 5 EST
ExtROM mount and rename
Custom ringtone
Custom Sounds Settings
Delete poutlook.lnk from startup
Set Hello to ATT
Disable CAB security policy
Removed all ATT applications (CV, real, win live, etc)
TODO: Incorporate RegHacks of additional settings customization and tweaks (lots of typing...), right now I install and merge the apps I want after initial setup completes.
Cheers
HOW TO
***always a good idea to backup existing files before attempting any modification***
1. mount your extended rom (search for the cabs and instructions on this site)
2. copy the CapPackage.PXP from ExtendedROM\Partition to your PC
3. extract the contents to a folder named CapPackage on your PC (any ZIP compliant archive tool will do)
4. remove/add the *signed* cab files your desire (unsigned cab files simply get passed over)
5. open capdata.xml in epcEDIT or notepad.
6. add/remove the configuration information as desired - this is where some trial and error comes in trying to determine what commands control what function.
7. ZIP (no other archive format seems to work) the CapPackage folder to CapPackage.PXP (or rename .zip to .pxp).
8. copy to ExtendedROM and hardreset.
TODO:
-Hope to be able to post a list of commands for the XML to enable configure of most if not all device "settings"
-Hope to figure out a way to get unsigned cabs to install (present workaround is a zip extract and registry commands if the app isn't too complex (e.g. lots and lots of typing required)
--Not sure yet if reg hack setting "HKLM\Security\Policies\Policies' valuename '0000101a' to dword:1" will resolve this during initial setup
Okay, after getting my questions about how this all works and saves the space on the phone, I took the plunge and upgraded from 2.23ROW to 2.25ATT. Went smooth as butter, and I have a "decrapified" phone with the official, supported ATT release (just in case I have any problems and need support).
Of course, being a hacker, now I'm totally intrigued by this cappackage customization, and want to play with it myself. So, Tim et. al., two questions:
Does the capdata.xml file have to match the contents of the archive? Or, if something's missing, it's just ignored? I'd like to be able to delete some more stuff and remake the PXP file without having to hassle with the XML file and run into the problems you have (workable, but I just don't want to waste time on whitespace issues if I don't have to).
Does the carrierDB file need to stay in the extended ROM for any reason after install and setup? I'd like to archive it on my PC, and delete it from the extrom so I can use that space for general storage.
microsoft word has a wonderful xml file editor. rather than try and keep everything straight in that jumbled up mess you get out of notepad or some other editor, word indents all the xml, and makes it look like it should. it was a snap to edit. I used Winrar and opened the PXP file. I never extracted the contents. Just the capdata file. I edited it, and then put the edited version back into winrar. using winrar I deleted the files I didn't want. saved the archive and moved it back to the device.
dwallersv said:
Does the capdata.xml file have to match the contents of the archive? Or, if something's missing, it's just ignored? I'd like to be able to delete some more stuff and remake the PXP file without having to hassle with the XML file and run into the problems you have (workable, but I just don't want to waste time on whitespace issues if I don't have to).
Does the carrierDB file need to stay in the extended ROM for any reason after install and setup? I'd like to archive it on my PC, and delete it from the extrom so I can use that space for general storage.
Click to expand...
Click to collapse
1. The XML will bypass anything it can't actually do.
2. I have tried it both ways and feel like I've had no issues, but I have seen some reports of strange behavior without it. I currently have it in my ExtROM since I hard reset my device often as I test apps and config settings. If you don't hard reset very often then once the device is hard reset you may delete and gain an additional 1.45mb.
The thing I intend to work on next is creating a provisioning XML to call an external XML (outside of the cappackage). I'm hoping this way I will be able to strip even more out of the cappackage (literally everything but the capdata.xml) and hav an on the fly configuration capability and call installations and configuration from the SD card. Haven't had much time to play with it though.
Can someone help point me in the right direction to get start loading the cappackage. I can't seem to find how to mount the extended ROM. I did a search for it and everything that came up didn't explain it (or at least I didn't understand it if it did).
Hmm, I can't seem to find the original thread either. Really just registry entries, but the cab's make it easier.
See attached...
Run each in order, then soft reset
Cheers
FYI: You can use my cappackage (see pg 1) as a starting/reference point for building the extROM mount into the initial config process after hard reset...
Try this. ...............
sodak said:
Can someone help point me in the right direction to get start loading the cappackage. I can't seem to find how to mount the extended ROM. I did a search for it and everything that came up didn't explain it (or at least I didn't understand it if it did).
Click to expand...
Click to collapse
Thanks to both of you for the quick response
I don't know whether it is because of this or because of something else. But I started modding this CapPackage file, and all of a sudden my treo just started acting weird. I had to hard reset it several times throughout the day. Then I upgraded to the 2.25 WM6. And that is where **** really hit the fan (I upgraded and put my own CapPackage version in it). And after that I've had nothing but trouble. Soft resets didn't work anymore, it just crashed on the boot screen. Hard resets work, but really slow, takes about 20min. So now I'm re-upgrading to 2.25 and just leaving that CapPackage file alone for now .
The tale away message: Don mess with this unless you know what you're doing, which isn't me
-Robert
(First post and not really good english)
One week after i bought my phone (HTC P4350, unbranded) i discovered this site/forum. A very usefull site, i learned much.
Now i am going to try to build my own rom. Based on this howto. (not Vista, but XP Professional)
(WM6: All WM6/WM6.1 ROMS --> All Official HTC Roms --> WWE version)
first i followed the howto without modifications to SYS and OEM to test if everything was working. result: as expected, a working phone.
next step was to remove some folder from SYS.
first try: remove 'windows update' (AUTOUPDATE, Autoupdate_Lang_0409)
flashed to phone, result: Start->Settings->Tab System->Windows Update fully functional, so it is not removed at al,
second try:
restored AUTOUPDATE, Autoupdate_Lang_0409
removed INTERNETSHARING
flashed to phone, result: Start->Programs->Internet Sharing, functional for so far i could test (no internet on phone, sim in other phone), but IntShrUI.exe was available in \Windows
Troubleshooting/Guesses about what went wrong
- Am i deleting stuf in the right directory (C:\Core\Hypercore\Build\SYS)
- Can i continue working in the kitchen after i flashed one time, or should i delete c:\core and start al over again by every modification?
after some houres searching on google and this site i did not found the solution or anyone with a problem like this.
i am doing something wrong, but do not know what.
'Met vriendelijke groet' (Greetings)
Robin
You're doing fine. Not sure why you would still have functioning parts after removing them... you took them off the SYS folder and place them where? (Somewhere NOT in the build folder.)
no, not in the build folder, i put a 'backup'/'copy' in a subfolder of 'my documents'
so i don't think that is the problem
edit:
i carefully read the howto for x time again and know i am wondering if (as below, quote) also goes for SYS folder, find everything with 'intshrui.exe', 'internet sharing', 'autoupdate', 'autoupdate.exe', etc
Add the oem packages into the oem folder. Total commander and networkwzard don’t require removal off default files from the oem folder, but comm. Manager do, and so do htc home. The way I use to find duplicate files, is before I add the oem packages, I open in.ex the new package with comm manager, and I highlight the OEM folder and rightclick and choose searchtab. Search for files, type in search “comm.” And all files containing the word “comm.” Will be displayed, dele them (make sure they belong to comm manager, that the names matches the one in your package)
When you have searched for all files in your package, and deleted them from the OEM folder, you can add you package.
Follow same steps for all packages you add, that can have duplicate files, if you don’t you will get error when building the rom, and the build process will terminate, tell you what file is duplicate. You must then find the file, and remove it (don’t remove the one in your new package)
Click to expand...
Click to collapse
You did it correctly... I wonder if it's really building the ROM or just flashing what's already in there...
I would offer that you use my kitchen, but I think you would definitively keep trying at the HyperCore because it sounds like you might be one of the next generation of cooks. My kitchen is more for the average person who doesn't want to or have the time to learn how to cook but wants their own custom ROM.
what i want for now i a rom with the software i 'need' of like.
i will give your kitchen a try, this link right?
but i don't give up with HyperCore because it should work. if other can do it, i can do it (i think)
r.g.j.jansman said:
what i want for now i a rom with the software i 'need' of like.
i will give your kitchen a try, this link right?
but i don't give up with HyperCore because it should work. if other can do it, i can do it (i think)
Click to expand...
Click to collapse
I'll be uploading Beta 2 soon with a LOT of fixes, you might want to wait until then. Any packages that you'd like to see there before I start uploading?
most packages that i need are in the list.
Basis apps like Office, audio manager are there, same goes for tools.
Your kitchen works easy. Nice work.
With the current release (downloaded at +/- 20:00 GMT+1) has some errors while building. Such as 'the file 'temp\dump\winlive.htm' already exists'.
i think i can handle those error my self, isn't it?
Greeting
Robin
r.g.j.jansman said:
most packages that i need are in the list.
Basis apps like Office, audio manager are there, same goes for tools.
Your kitchen works easy. Nice work.
With the current release (downloaded at +/- 20:00 GMT+1) has some errors while building. Such as 'the file 'temp\dump\winlive.htm' already exists'.
i think i can handle those error my self, isn't it?
Greeting
Robin
Click to expand...
Click to collapse
the double in \tem\ is not important... but there msut be a double in one of the sys or oem folders. try to search them and delete one of them....
Exactly. Do a search for the OEM and SYS folder for the files in question and delete the duplicate. All these errors have been fixed in the Beta 2, but I haven't had time to upload them, yet. (Tried last night but the connection went out half way through it.)
On a brighter note, I'm slowly buying all the parts I need this week to finally rebuild my computer!! (For those that have been here long enough to know my PC fried and I've been working off my ancient laptop for a while.)
when you have uploaded beta2 i will give it a try
good luck with (re)building your pc
i think i know what went wrong..
When starting Hypercore\Panel\Build\BuildOS there are for me 3 options
1. Start "Build OS"
2. Create OS.nb from Sys and OEM
4. Flash
The first time (without changes to SYS and OEM) i copied OS.nb to HyperCore\Tools\RUU for flashing my phone.
By the second test with changes to SYS and OEM i started BuilOS, followed all 3 steps but did not copy OS.nb to HyperCore\Tools\RUU so the first ROM is flashed again, and not my modified ROM
I will now give it another try and will let know the result. But i'm pretty sure this was the problem.
Thanks already for trying to help me.
That would DEFINITIVELY be a problem. lol
After you run 1, then 2, the os.nb will be at the build folder after.
Still some trouble
here i am again.
i don't know if i should start a new thread or go further with this one.
After i removed some software, i am now trying to add software (oem packages). As source i have some cab files. They have to be converted to an oem package, (i read, found on this forum). So i tried to.
Reading and applying this one, and this one BuildOS make trouble.
An messagebox appears with 'Data Exception' and in the bottom (status) is says
[ Error, Last status: "Processing: OEM\OEMAPPS... Searching for dsm file" ]
I tried also with an OEM Package (PocketRAR) downloaded from here.
It keeps saying the same error.
Who can help me?
if you need more information you can ask me for it.
Hi all
got wings with wm6, and it's working fine except a problem that from time to time while using all sorts of programs the device decides to soft-reset itself.
not sure what program is causing this problem, and it might be the OS itself.
anyway I want to flash the device with other ROM's but in XDA-DEV ftp there's only the *.nbh file, and I cannot flash this file only (or at least I don't know how... )
I'd be glad if someone could point me to the RomUpdateUtility or even post an adrress here, because I've also checked to post of alcalaine and the supposed RUU there is only the *.exe file and I cannot replace the *.nbh file with the one I want.
Thanks in advance...
Tomer
It's included in a official rom.
See here: http://forum.xda-developers.com/showthread.php?t=395575