Database Users

Jeff's Exe

OK, I'll start by saying sorry for my stupidness and thankyou for listening to my plea.
I downloaded Jeff's XDA special edition .exe file and unzipped it to a Dir seeing all the files needed to upload a new ROM to my XDA.
I (in all my wisdom) decided to run the osimagetool with the --register and proceeded to right click on the nbf 30mb rom image and selected burn...thinking this was the way to do it (not even trying to run the original exe)
The "programme a" program started and started updating my xda. It started off updating and after a few seconds i heard the "BLIMP" of the activesync telling me it has disconnected, then another blimp telling me it had restarted and re-connected to active sync, but the loader on the screen quickly zipped to 100% done and told me to remove and reboot the xda. The xda however was telling me "upgrading... It will take about 5 minutes". Urk
Now im left with an XDA that sit's on this upgrading screen even after reboot of it.
OK... ive done wrong.. im silly... would any one step up and help me out here (BIG PLEASE AND TY also). Ive got an XDA serial cable sitting here next to me as well as the usb cradle (which im sure wont help now the xda cant run active sync)....
Ideas? Can i run the original rom uploader (xredit?) rather than osimagetool with the serial cable to upload either the new rom i have or the rom i backed up of my old device before doing all this (yes i did back it up to my harddrive first - phew?).
Thanks for reading, and i hope someone can point me to a place in the forum where all people like me end up, or even better send me an email pointing me in the right direction.
Thank you! (email Tony at [email protected])
Note: my original version was 3.17.03 and the "programme a" upgrade program said it was upgrading to 3.16.

can you tell me what splitrom says about the nk.nbf that is now in the 'english' subdirectory of the path
pointed to by the registry key "Software\\XDA Developers\\OsImageWriter", "Programme A Path" ( in current-user )

thanks for coming back to me.
unfortionately, i dont have perl installed on my windows xp machine so the batch file you linked to do doesnt work. If you have a link for a perl install anywhere I'll be happy to install and run it.
In the key you mentioned, here is the value: D:\XDAtools-Jeff\binaries
The directory i unzipped Jeff's version of your tools to.
Im not sure if you perl script does other things, so in the meantime, i'll go and try and find perl (im sure ive installed it on a work machine i had years ago - seem to remember adding local path variables for it)... i'll check my cd archive for it.
Thanks for the help, much appriciated
Tony.

perl can be obtained from either http://www.cygwin.com/setup.exe or http://www.activestate.com/Products/Download/Download.plex?id=ActivePerl

cheers, i'll dl then run the script....
n1 guv

C:\Documents and Settings\tkett.ADPLATES>D:\splitrom.bat
Can't locate List/Util.pm in @INC (@INC contains: C:/Perl/lib C:/Perl/site/lib .
) at D:\splitrom.bat line 86.
BEGIN failed--compilation aborted at D:\splitrom.bat line 86.
^^
Thats the error message i get when running that perl script.
Ive searched the hdd for Util.pm and its sitting in my c:\perl\lib\sgi dir
Things just arent going right for me at the mo.

this module is standard with perl 5.8, with perl 5.6 you have to install
it manually.
as a quick fix, you may also just add a 'min' function manually
Code:
sub min {
my $min;
for (@_) {
$min= $_ if (!defined $min || $_ < $min);
}
return $min;
}
and uncomment the line
Code:
#use List::Util qw(min);

C:\Documents and Settings\tkett.ADPLATES>D:\splitrom.bat
Usage: splitrom <romimage(s)> [options]
-wx xipchain where to write xipchain
-wo osrom where to write output image
-wb bitmap where to write bitmap
-wl bootloader where to write bootloader
-rl bootloader which bootloader to use for NBF
-n nbfinfotext what NBF header to use [ex: PW10A1-EN
-ri nbfinfofile or where to read NBF header info from
-wi nbfinfofile where to save NBF header info
-rx xipchain where to get xipchain from
-rb bitmap where to get bitmap from
-rm [email protected] insert new romsection.
-ob offset where to find the bootup image
-oe offset the end of the desired os image ( def
0000 )
-t NBF | B000FF | NB? | IMG type of result image (default is NB1)
^^^^ Ive put your routine in replacement of that line and am given the options above when running splitrom now. What parameter would you like me to run ?
As always.... a big thanks for the help.
Tony

Itsme, thanks for your interest in my problem. And im very glad people like you are around to help
I have however and thankfully repaired the fault.
Here, (for other newb's like me that get stuck) is how i done it:
I had already backed up my ROM using the osimagetool program to a nb1 file on my pc called "oldrom.nb1". Now because my XDA wasnt booting into Pocket PC windows, i couldnt use active sync to sent the rom image I backed up, back to the XDA...so I had to go and buy a cheap SD reader from my local Dixons store and run osimagetool again. This time writing the rom i had backed up to the SD card in the new SD reader.
Then I rebooted the XDA into the bootloader (hold down the top power button and do a soft reset) and selected to reflash the XDA using the SD card.
If you havent already backed up your rom from your xda to file, then I presume, you have to find another person with an XDA so you can download thers to your SD card (once your in the bootloader menu, press the contacts button to get the options to dump their rom to your card). OR find an NB1 file on the internet that matches your phone version.
These may be simple instructions for most of you, but i've seen a few posts that directly relate to the problem i had, and saw people crying for help, just like i did...hopefully this will help those few.
I did also have a serial cable, and im sure there is a way to upload roms you have on your pc to the XDA via that (using the xda developers old rom tool), but im afriad i didnt read into that after finding out this method. (this way may be better for the skint people who dont want to buy an SD reader, but can get hold of a serial cable for cheap)
REMEMBER FOLKS
It was silly of me to try and flash the device in the first place without reading loads and loads of entries on these forums and really finding out what is going on instead of just flashing blindly in the hope that it would work first time.... please dont follow my lead. :shock:
Thanks again for your help Itsme...and one last question... do you think that with that registry entry as it was above, that i can try again with the .exe jeff made (possibly downloading it again in case of corruption)
(yes i am a glutten for punishment)
Tony

still I'd like to know what went wrong in your case.
can you type 'splitrom nk.nbf' ( in the 'english' subdirectory )

sure:
D:\XDAtools-Jeff\binaries\English>splitrom.bat nk.nbf
this rom seems to be 3.17.03 ENG 2003-05-15 o2euro
this bootloader seems to be V5.15 2002-06-06 20:29:17
no bitmap found
80000000 - 80040000 -- bootloader 0 files 1 modules
80040000 - 8026a804 -- kernel 13 files 11 modules
802c2000 - 8057d330 9 OS 15 files 32 modules
80580000 - 8075a69c 8 SHELL 79 files 27 modules
80780000 - 80a13b04 7 BROWSING 9 files 14 modules
80a40000 - 80d8a33c 6 COREAPPS 46 files 30 modules
80dc0000 - 80ebd150 5 SYNC 12 files 22 modules
80ec0000 - 810388e0 4 24MAPPS 13 files 13 modules
81080000 - 81348248 3 24MCONSUMER 69 files 1 modules
81400000 - 81401484 -- xip chain 8 xip entries
81440000 - 817f6f14 1 MISC 209 files 40 modules
81940000 - 81d2d2b5 -- operator rom 81 files
Tony.

ahhh... haNG ON.... the one i used was in the .exe's folder.. not jeffs tools folder:
D:\XDA-developers-SER-v12\English>splitrom.bat nk.nbf
this rom seems to be 3.16.52 ENG 2003-03-10 XDASER-12
this bootloader seems to be V5.22 2003-05-15 17:46:55
no bitmap found
80000000 - 80040000 -- bootloader 0 files 1 modules
80040000 - 8026a804 -- kernel 13 files 11 modules
802c2000 - 8057d330 9 OS 15 files 32 modules
80580000 - 8075a69c 8 SHELL 79 files 27 modules
80780000 - 80a13b04 7 BROWSING 9 files 14 modules
80a40000 - 80d8a33c 6 COREAPPS 46 files 30 modules
80dc0000 - 80ebd150 5 SYNC 12 files 22 modules
80ec0000 - 810388e0 4 24MAPPS 13 files 13 modules
81080000 - 81348248 3 24MCONSUMER 69 files 1 modules
81400000 - 814019a4 -- xip chain 10 xip entries
81440000 - 817f6f14 1 MISC 209 files 40 modules
81800000 - 818e0c14 10 XDA_DEVELOPERS1 13 files 0 modules
81940000 - 8198b6e5 -- operator rom 20 files
819c0000 - 81ee9a58 11 XDA_DEVELOPERS2 202 files 0 modules
hence the 3.16 now.

Hi Ajkett,
Thanks for sharing your knowledge of how to resolve your problem with us. I have however used a new 64 mb sd card to flash my old rom (3.16) to it before trying out the Jeff rom kitchen exe and thank god things are fine for me. Now I have bought a cheap 6 in 1 card reader/writer and would like to keep the old rom in a safe place in my hard disk hence freeing my sd card so that I could use it. I have read those threads in the rom tool section many times and still can't work out how to use the osimagetool. When I clicked on it, it gives me the interactive screen but always do not read my sd card. Even with the card reader, it seems to "think" that the sd card is unformatted and ask to format the card for me. Now the question is whether the rom is inside or not? How can I use the rom tools to read the sd card and copy the rom to the hard disk? What does a rom file appear as? Is it like the nk.nb1 file created in Jeff's rom kitchen?
Cheers
Vic

ahhh your trying to read the rom from the sd card after dumping it to the sd card from the xda?
the way i got it onto my harddrive was without an sd card. Just run the osimage tool and select the xda current memory as the source and then type c:\oldrom.nb1 as the destination.... it will use activesync to read the rom straight from the device.... you dont need the sd card to back it up.
Then when i ****ed my xda up, i run the osimage tool again and wrote from source - oldrom.nb1 to the sd card reader to a formatted sd card.
When it writes it, it gets rid of all the formatting so you wont be able to see whats on it on your pc....the only thing its good for then is to use on the xda to overwrite the rom, until you format it again that is.
Its not like a file on the sd card... its like a bootdisk with the rom written in a way that the xda will understand that its a bootdisk and will boot from it to overwrite itself... like the file is in raw format... not a nb1 file or anything (looks like lots of gobbledigoop) and the pc will not read it.

Thanks Ajkett,
Thanks for your kind reply anyway.
Got it done. The osimagetool could read but I did not write the path correctly; it has to be rom.nb1 apparently for it to work. I even used the card reader and managed to write the rom again the same way to my hard disk. I hope this is the correct way of doing it and it seems that the rom.nb1 file on my harddisk is about 30.5 mb which is probably about right for the old 3.16 rom I had dumped onto it by the XDA.
What puzzles me is that if it can read as source rom.nb1 file when you say you rewrite it to the sdcard, it becomes mumbo jumbo again but it should flash ok within bootloader mode via the XDA. Is this correct?
Cheers
Vic

yep your correct... even thogh it doesnt write a nice 30mb rom.nb1 file to your sdcard, the xda still reads it to boot from.... it must need it a raw info.

I can't upgrade to the official Siemnes sx56

HI,
I'm trying to upgrade my sx56 to the new rom (ruuv1.11_cea.20.17wwe_aws.exe) but i got the follwing error :
---------------------------------------------
The rom Image is not compatable ....
your current device info is PW10A1
Rom ver. 3017
Language :english
your upgraded image info :
Model PW10b1
Rom: A.20
Language :English
------------------------------------------------
What should i do ??
I have sx56 updated with xda-developers rom v1.2
now my device info is :
Rom ver. : 3.17.03 Eng
Rom date: 05/15/03
radio ver.: A.20.10
Protocol : 324e4

balo, if I am correct... you can't use Siemens update since it's now modified to o2 rom. If you didn't make a SD backup, you can ask the forum for the original Siemens ROM.
I did exactly what you did... upp'ed my Siemens SX56 rom to T-Mo 4.0.16 and didn't backup to SD first (since I didn't own an SD card before).

Your best bet is to use the bootloader SD card upgrade method.
But if you don't have a PC SD card reader the below is your next
option.
You need to download and run AdaptROM.
AdaptROM can be found at:
http://xda-developers.com/adaptROM/
Place AdaptROM.exe in the C:/Programs Files/SX56 upgrade
utility folder.
Now go to DOS and run AdaptROM.exe from the C:/Programs Files/SX56 upgrade utility folder. Now try upgrading again by running the upgrade.exe from the C:/Programs Files/SX56 upgrade
utility folder.
HTH

Hi,
the update that i have is .exe ,i unzip it and do the adaptrom.exe thing ,but how can i convert it again to .exe ,i tried to run upgrade.exe and i have the following error :
------------------------
Cannot fined the Rom image to upgrade you Pocket Pc Phone.
------------------------
and please could any one tell me step by step or refer me to a link to do the sd card method (knowing that i have ruu.exe file)
Thanks

Confirming you didn't have a C:\Program Files\SX56 upgrade utility folder and thats why you unzipped the upgrade file?
If so thats strange because this folder should have been created the first time you ran the upgrade utility.
BTW the reason the upgrade.exe cannot fined the Rom image to upgrade you Pocket Pc Phone is because its not being ran from the C:\Program Files\SX56 upgrade utility folder.
Anyhow heres my step-by-step for the bootloader SD card method:
Qman's how to use XDArit to write nk.nb1 or nk.nbf to your SD card aka the Bootloader Method!
1. Place XDArit and the nk.nb1 or nk.nbf file in the same folder and start XDArit.
2. Select your SD card (disk drive) from the drop down menu.
3. Select Write to SD
Notice that the Windows CE box is already checked so just click the browse button at the end of that window.
4. Select your (nk.nb1 or nk.nbf) image and then Open
Notice by default XDArit will open looking for a *.nb1 file but if you’re going to use a .nbf file you’ll have to manually change the “Files of Type” to *.nbf
Notice that nk.nbo / nk.nbo was automatically added as your boot-loader and its check box is unchecked so leave it that way and click OK. XDArit should start writing to the card.
When XDArit has finished writing the image put the SD-card into the XDA and hold the power button and soft reset. You’ll be taken to the below screen:
SD DOWNLOAD
Card Type:
CE OS & BOOT
Press action to Download
Or
Press REC to Exit
Press action to download and it will start the download/restore from the SD card.
Follow the on screen instructions once its "Completed" which will consist of a "Soft Boot/Reset".
BTW the above is based on using XDArit version 1.0 which can be download from the software section at:
http://www.yorch.net and a PCI USB 3-One Travel Flash reader P/N FPT-D bought at Fry's.
HTH

Thanks Qman ,you helped me alot ,I appreciate it
Thanks you

Dopod 828 CHT ROM 1.12.06 installed on i-mate JAM

I have just installed the new Dopod 828 Chinese ROM on my i-mate JAM and created the 27M BigStorage on it.
The radio ROM is 1.13.
I have also extracted the Extended ROM for those interested.
ftp://xda:[email protected]/Uploads/Magician/Extended_ROM_Dopod_CHT_112_177/
There are quite a few interesting add-on softwares such as
- Skype For PocketPC
- Iconlab Intervision
- Polaris PWinner
- wLAN11b (for the Dopod "short" SD wifi card)

Talents,
Can you upload the CHT 1.12 Rom also? Thanks a lot

The full OS ROM was uploaded on 11 August by someone else.
ftp://xda:[email protected]/Magician/Dumped_ROMs/Dopod828V112OS.zip

opps. mislook it tim..

Talents said:
The full OS ROM was uploaded on 11 August by someone else.
ftp://xda:[email protected]/Magician/Dumped_ROMs/Dopod828V112OS.zip
Click to expand...
Click to collapse
Hi, Talents
Could you teach me how to install this rom file, after zip the rom is .bin format.
thanks you

thanks for info,it works fine with my 818!!

Please note that in Device Information, it will show Model to be PM10B instead of PM10A. This should cause no problem to installing almost all softwares, but Pocket Hack Master fails to recognise it.
My i-mate JAM has been upgraded to 128M RAM. So, the configuration is no different from Dopod 828.

Talents said:
Please note that in Device Information, it will show Model to be PM10B instead of PM10A. This should cause no problem to installing almost all softwares, but Pocket Hack Master fails to recognise it.
My i-mate JAM has been upgraded to 128M RAM. So, the configuration is no different from Dopod 828.
Click to expand...
Click to collapse
Hi Mate,
How to install this rom on the I-mate.
Thanks & Regards,

Use the standard SD method to install. You can find a lot of postings about the method in this forum.
As a short summary:
1. Use RomUpdate.exe to dump your orginal ROM to a 128M or 256M SD card.
2. Use ntrw.exe to read the ROM file on the SD card and save it to your hard disk.
3. Use HexEditor to replace the first 416 bytes of the downloaded ROM by the same of your original ROM.
4. (BigStorage option) Change the bytes 80 00 to b8 01 at locations 7e4a and 1fc232e.
5. Use ntrw.exe to write the modified ROM file to SD card.
6. Insert the SD card and set the ppc to bootloader mode.
The above may appear complicated if you are new to ROM upgrade procedures. Please search the forum for more detailed instructions before you attempt.

Compare with o2 mini ROM and 828 rom
have imporove quantity of carmera ?
thank You

Talents said:
Use the standard SD method to install. You can find a lot of postings about the method in this forum.
As a short summary:
1. Use RomUpdate.exe to dump your orginal ROM to a 128M or 256M SD card.
2. Use ntrw.exe to read the ROM file on the SD card and save it to your hard disk.
3. Use HexEditor to replace the first 416 bytes of the downloaded ROM by the same of your original ROM.
4. (BigStorage option) Change the bytes 80 00 to b8 01 at locations 7e4a and 1fc232e.
5. Use ntrw.exe to write the modified ROM file to SD card.
6. Insert the SD card and set the ppc to bootloader mode.
The above may appear complicated if you are new to ROM upgrade procedures. Please search the forum for more detailed instructions before you attempt.
Click to expand...
Click to collapse
Hello, Talents
Thanks a lot of for ur help, i had done the upgrade, thanks u very much.

Can this work on the Xda II mini?
Thank you!

adeliang said:
Can this work on the Xda II mini?
Thank you!
Click to expand...
Click to collapse
THX TOO

Talents said:
Use the standard SD method to install. You can find a lot of postings about the method in this forum.
As a short summary:
1. Use RomUpdate.exe to dump your orginal ROM to a 128M or 256M SD card.
2. Use ntrw.exe to read the ROM file on the SD card and save it to your hard disk.
3. Use HexEditor to replace the first 416 bytes of the downloaded ROM by the same of your original ROM.
4. (BigStorage option) Change the bytes 80 00 to b8 01 at locations 7e4a and 1fc232e.
5. Use ntrw.exe to write the modified ROM file to SD card.
6. Insert the SD card and set the ppc to bootloader mode.
The above may appear complicated if you are new to ROM upgrade procedures. Please search the forum for more detailed instructions before you attempt.
Click to expand...
Click to collapse
Why I got 11.03 MB of my Rom Storage when I Finished the rom upgrade?
And also my radio Version still in 1.11 ?

Thanks a lot! Although I haven't 828.

can I flash it to Eng O2Mini if no RAM upgrade (still 64MB) and how to do? Is there any improvement such as carmera and phone?

and how to use your .bin file? thank you.

Thanks, it's very useful

Still having trouble with BIN file
What do we do with the bin file? I downloaded the full OSDopod828 and have no idea what to do. I see nb1 files and then bin files. do we rename it or what? Can you guys help and clarify. Getting really frustrated.
What's the purpose of editting the 416bytes. If i just want the standard OS, did i have to back up anything at all? Why cant it be just as easy as the EXE which does everything for you...geeesh
C.

How to use BIN Files and SD upgrade?
Read a few posts which arent as clear for me at least. Maybe i'm just slow. I want to upgrade my dopod 828 back to CHT. Any easy way to do it next to the SD method which doesnt work with me. I didnt back up my CHT before i went for the WWE. What do i do with the bin file. Rename it or edit it what? Need desparate help here guys.
Sorry for multiple posts.

Is Dopod 828 Cht Possible to upgrade to english ROM

Hi everyone:
I just bought my Dopod 828, however it language is Traditional Chinese, and I want to change the ROM to englisg.
So where I can find the english rom for this pda and what is the procedure and precaution I need to take during the upgrading.
Joel

Hi...
go to the ftp from here,and download a WWE ROM of ur liking (1.12WWE is an example),also download MaUpgradeUt_noID.exe and flash ur device....
RAGO :lol:

Thanks,
I logged in to the ftp site, there are many folder and many ROM, however what is the different between them?
Shipped_ROMS
Dumped_ROMs
Modified_ROMs
Extended_Roms
BigStorage_ROMs
Radio
Unlock
Thanks Joel

joelwu said:
Thanks,
I logged in to the ftp site, there are many folder and many ROM, however what is the different between them?
Shipped_ROMS
Dumped_ROMs
Modified_ROMs
Extended_Roms
BigStorage_ROMs
Radio
Unlock
Thanks Joel
Click to expand...
Click to collapse
Shipped=original ROM provided from factories(ex:O2,T-mobile,I-mate...)
Dumped=ROMs dumped for SD memory cards upgrades(forget about them for the moment)
Modified=Modified ROMs using kitchens(forget about them also)
Extended=ms_.nbf=not ROM image,but extended ROM where softwares are preinstalled,and start automatic installation after a hard reset...(also forget about them)
Big storage=enlarge ur storage space by freeing the extended ROM memory..(not now,so also forget about them)
Radio=radio_.nbf=not ROM image but ur phone part upgrade(ur device is a phone and a PDA,these ROMs take care of the phone part)
Unlock=not ROMs but tools to unlock ur device if it's locked from communication networks like t-mobile,etc....
so,as a conclusion,use shipped ROM folder... :wink:
RAGO :lol:

Very detailed explaination!
Thank you very much.
I will try to upgrade my device in this week end, good luck to me
Just curious about how other customer the extended rom etc.....
And I saw many CAB file to install... is this those modification that other have make to improve the device?
RAGOv said:
joelwu said:
Thanks,
I logged in to the ftp site, there are many folder and many ROM, however what is the different between them?
Shipped_ROMS
Dumped_ROMs
Modified_ROMs
Extended_Roms
BigStorage_ROMs
Radio
Unlock
Thanks Joel
Click to expand...
Click to collapse
Shipped=original ROM provided from factories(ex:O2,T-mobile,I-mate...)
Dumped=ROMs dumped for SD memory cards upgrades(forget about them for the moment)
Modified=Modified ROMs using kitchens(forget about them also)
Extended=ms_.nbf=not ROM image,but extended ROM where softwares are preinstalled,and start automatic installation after a hard reset...(also forget about them)
Big storage=enlarge ur storage space by freeing the extended ROM memory..(not now,so also forget about them)
Radio=radio_.nbf=not ROM image but ur phone part upgrade(ur device is a phone and a PDA,these ROMs take care of the phone part)
Unlock=not ROMs but tools to unlock ur device if it's locked from communication networks like t-mobile,etc....
so,as a conclusion,use shipped ROM folder... :wink:
RAGO :lol:
Click to expand...
Click to collapse

joelwu said:
Just curious about how other customer the extended rom etc.....
And I saw many CAB file to install... is this those modification that other have make to improve the device?
Click to expand...
Click to collapse
Hi...
In the Magician,extended ROM customization is not as easy as other devices.
For himalaya devices,u can use ER2003edit to open ms_.nbf files,edit them by replacing the cabs,or u can unlock and unhide ur extended ROM using extrom unlocker,then u wille able to see extended ROM as a removable drive,and u can edit cabs within...(note that cabs are *.cab files,or cabinet files,those files are executable on ur PPC,almost every program or software is a cab file,even if it doesn't look like,cab file must be contained in,exept executable applications on PPC like .exe that runs directly by clicking on)
In BlueAngel,ER2003edit don't open it's ms_.nbf,but still u have an extrom unlocker for BAs....so u can also edit ext ROMs...
Now in Magician,and due to the difference in hardware architecture(Magician have one rom slot of 64mb),this device don't have (yet) an ext ROM unlocker,and ER2003edit do not open it's ms_.nbf files....(and the member (Anansky) who did the big storage and we all believe he can make or help in making extrom unlocker,seem to have vanished... :? ...)still,there's advanced methods to customize ur ext ROM,but take into consideration that they r not easy....
1-by dumping the ROM to storage card,then using ntrw and a hex editor to cut a partition of the decoded ROM(the ext ROM),mounting it as virtual drive using total commader plugin,editing it,and reflashing using SD method....ouff...read more about this method from here...
2-by freeing ur ext ROM memory using big storage,then making a folder called 2577 on ur storage card,put in autorun.exe and a .zip file containing ur cabs,so,once u do a hard reset,the cabs will be installed automatically from ur SD card....read about big storage from here and here...learn about 2577 folder from buzz's site... http://www.buzzdev.net/
note that this method does not make u an extended ROM like ms_.nbf,but will do the job as it will install ur favorite cabs directly after hard reset....
Good luck...
RAGO :lol:

Just to share with everyone after few days trying, I have succesfully upgrade my dopod 828, the main problem is facing the Error 150, the Upgrade utility is not designed for this device
The procedure is more or less the same as pervious post in this forum, but just little bit different
1. Right click on the EXE-file and extract to a named folder (using Winzip or something similiar)
2. You should end up with about 6 - 8 individual files; ms.nb1, radio.nb1, nk.nb1 ruu.conf, ruu.dll, enterbl, getdevicedata and maupgradeut, the maupgradeut is the file that runs the upgrade
3. Download the MaUpgradeUt_noID.exe
4. Once you have this file you will need to add this to the folder created above as this is the file needed to initiate the upgrade.
----- until step is exactly the same
Skip this step-> In ActiveSync, click on file and connection settings and untick the USB connection.
5. In ActiveSync, go to option -> Schedule, Set it to Manual, this is to make the PPC USB connection to ActiveSync active but don't do any Sync with your PC and PPC during the upgrade process.
6. Connect the phone to the USB, manually sync once. From now onwards, the step is the same.
-----
7. Now run the MaUpgradeUt_noID.exe
8. The upgrade Wizard will start, go through a few checks then eventually come up with the country Id error.
9. Run the MaUpgradeUt_noID.exe file again and this time it should allow you to run the Wizard.
10. The process should then go through 3 stages which should last about 10 - 15 minutes.
11. When finished you should get the upgrade successful notification and a prompt to reset the device
12. In ActiveSync, click on file and connection settings and tick the USB connection.
13. Enjoy your new ROM
I am trying to upgrade my Dopod 828, and I get a error no. 150 said the ROM is not designed for this device... oh.....
RAGOv said:
joelwu said:
Just curious about how other customer the extended rom etc.....
And I saw many CAB file to install... is this those modification that other have make to improve the device?
Click to expand...
Click to collapse
Hi...
In the Magician,extended ROM customization is not as easy as other devices.
For himalaya devices,u can use ER2003edit to open ms_.nbf files,edit them by replacing the cabs,or u can unlock and unhide ur extended ROM using extrom unlocker,then u wille able to see extended ROM as a removable drive,and u can edit cabs within...(note that cabs are *.cab files,or cabinet files,those files are executable on ur PPC,almost every program or software is a cab file,even if it doesn't look like,cab file must be contained in,exept executable applications on PPC like .exe that runs directly by clicking on)
In BlueAngel,ER2003edit don't open it's ms_.nbf,but still u have an extrom unlocker for BAs....so u can also edit ext ROMs...
Now in Magician,and due to the difference in hardware architecture(Magician have one rom slot of 64mb),this device don't have (yet) an ext ROM unlocker,and ER2003edit do not open it's ms_.nbf files....(and the member (Anansky) who did the big storage and we all believe he can make or help in making extrom unlocker,seem to have vanished... :? ...)still,there's advanced methods to customize ur ext ROM,but take into consideration that they r not easy....
1-by dumping the ROM to storage card,then using ntrw and a hex editor to cut a partition of the decoded ROM(the ext ROM),mounting it as virtual drive using total commader plugin,editing it,and reflashing using SD method....ouff...read more about this method from here...
2-by freeing ur ext ROM memory using big storage,then making a folder called 2577 on ur storage card,put in autorun.exe and a .zip file containing ur cabs,so,once u do a hard reset,the cabs will be installed automatically from ur SD card....read about big storage from here and here...learn about 2577 folder from buzz's site... http://www.buzzdev.net/
note that this method does not make u an extended ROM like ms_.nbf,but will do the job as it will install ur favorite cabs directly after hard reset....
Good luck...
RAGO :lol:
Click to expand...
Click to collapse

another wm6 for spv c500

i edited this rom to make it work for the spv c500. I present a new wm6 rom for c500.
1. Rebuilt from M$ dogfood build packages, didnt modify anything with rgucomp
2. Added Total Commander,CeleTask, Tao 10, STK, USSD, T9 (tegic) russian and english
3. Removed Catalog, ApproveUpdate, AutoUpdate,Sqm,Sql server mobile, WinLive (you can find a cab or make one), Office (there are cabs with office for wm5 ripped from new builds floating)
4. Coredll 5.2.1235 (well, i am going to port a newer build later), changed compression of imgfs to LZX (os image is 27 mb, you can flash with old wm5 spl or with new from wm6, if you use new spl, type in mtty before loading rom)
format BINFS 01b00000
format FATFS
you should now have more storage
5. Camera works with pictures and videos, if you push camera button, it opens pictures and videos
6. Removed HTC debug apps (except Registry Editor)
7. fixed imgfs, no module overlaps))
8. Removed hd.dll, osaxst0.dll, relfsd.dll from XIP - boots faster, freed several KB of ram
9. Security Policy - Security Off - no confirmations on cab and exe launch
10. Added lots of htc and wm6 sdk test certificates
11. cabs don`t get removed after installation
Edit: oh, i forgot to add total commander shortcut and it seems camera key doesnt open pictures and videos, if any shortcuts are missing - find them in \windows dir and add manually - seems to be a bug of the build 15341
original rom found there http://forum.xda-developers.com/showthread.php?t=323668
new rom http://rapidshare.com/files/50848036/wm67.rar

where are the german roms for feeler and amadeus? there was a version with german language... is there no one out there who can modify it??? there are enough roms for typhoon/c500!

Doesn't work with my C500 :
[Cmd>format BINFS 01B00000
Format BinFS partition.
Format BINFS...
Format BINFS Completed. Continue to set BINFS type.
Set BINFS_TYPE success.
Format is completed!!
Cmd>format FAT
Format FAT partition.
Format is completed!!
Cmd>l c:\wm67.bin
clean up the image temp buffer at 0x8C080000 Length 0x01B00000
MTTYDownloadImage "c:\wm67.bin"
Sync bytes error(0) 77 != 42Error : DownloadImage return error (code = 0xFFFFFFF
F)​
What I'am doing wrong?

Perhaps you typed the wrong filename
wm67 ??

try it again thats what happen to me on the other wm6 rom any ways you already formated so no going back

karhoe said:
Perhaps you typed the wrong filename
wm67 ??
Click to expand...
Click to collapse
That the name of file included in wm6.rar from link.
I have tried tu rename-it in wm6.bin same thing append
Before I try this rom I had 565wm6 that work great (but without customisation)

laurent91 said:
That the name of file included in wm6.rar from link.
I have tried tu rename-it in wm6.bin same thing append
Before I try this rom I had 565wm6 that work great (but without customisation)
Click to expand...
Click to collapse
rename to wm6.bin and it will work

rickwyatt said:
rename to wm6.bin and it will work
Click to expand...
Click to collapse
I already try that without success...

I have change from TeraTerm to MTTY 1.42 tu upload the rom file and it work!.
So that TeraTerm who blocking me
Thanks for help guys

camera working very slowly ;/ and MMS don't work ;/