Database Develop

Useing XDATools: Getting Error 102 CE Image File Checksum

heya,
i downloaded my actual ROM from my MDA III useing the XDATools to my PC. I named the file to nk.nbf. When I start the BAUpgradeUt.exe then after a short check the following error appears:
ERROR 102: CE IMAGE FILE CHECKSUM ERROR
How can i correct this?
I used the latest TMA GER Update from T-Mobile. I changed some programs in the \Extended ROM\ Folder ... can this error come from this?
Pls help me

XdaTools is a backup utilitty just for HTC Wallaby series i.e O2 Xda, T-Mobile MDA, Siemens SX56... and not for the MDAIII (HTC Blue Angel series). You have to use another tool, mtty I guess

If you dump or flash a ROM to your PC, you can not simply name it *.nbf.
The dumped versions are all *.nba files, and need to be converted (=coded) to *.nbf files to work again with the BaUpgradeUt.exe tool.
Conversion goes via the xda3nbftool or by hand (XOR it).
Also not that your PDA has 3 ROMS...

Qtek 9090 would not update and is dead now

Hi,
i tryed updating the qtek 9090, after i changed the country id type 1 it started.
It controlled my device and said : update from 1.12 to 1.40 and all the specs.
Then i hit next and id says checking information. It saysthat about 30 minutes now and the active sync connection is lost. Also my qtek looks dead.
I tried the installer again but it wouldn't work
I did a soft-reset and that didn't work also.
What now ? Hard-reset or ?.....
Thanks dudes

Ok, after a hard reset my device shows USB v 2.03 again so that's good ins't it
Now the country id error keeps coming, type is at 1 so what can i do more ?

Hi ThEScReW,
I've had the same problem while trying to downgrade to 1.22GER after flashing my device to 1.40WWE. I found out the modified version of MAupgradeUT that normally works for the Magician was able to flash my device with any BA rom I tried. It doesn't matter whether it's a type I or type II rom. Follow my instructions in the readme.txt and it should work.
Good luck!!!

Ok, i'm real thanks for that but i'm also really not that smart if you think i am.
What should i do with al those files? What to put where and what to do first and what last ?
Thanks :lol: you will be a great help
Where do you live btw in germany ?

Take the 1.40_shipped.exe you have and use winrar to unzip the files in a folder. After that you can copy the 3 .nbf files (nk.nbf, ms_.nbf and radio_.nbf)into the BA_upgrade no more errors folder. Then you start the MAUpgradeUT.exe. If the software says there is an error just press quit and restart the MAUpgradeUT.exe. Next time you try it should work making no problems.
Ps: I live in Bavaria about 50 km away from Munich.

berni_1980 said:
Take the 1.40_shipped.exe you have and use winrar to unzip the files in a folder. After that you can copy the 3 .nbf files (nk.nbf, ms_.nbf and radio_.nbf)into the BA_upgrade no more errors folder. Then you start the MAUpgradeUT.exe. If the software says there is an error just press quit and restart the MAUpgradeUT.exe. Next time you try it should work making no problems.
Ps: I live in Bavaria about 50 km away from Munich.
Click to expand...
Click to collapse
Ok thanks but the roms i have are just 1 exe file and that's an installer. It's as easy as hell. I just have to run de exe and follow the rules on the screen.
If i do what you tell me to do, then i need to download a rom from the ftp with al the files in. Then what do i do with those files? what first, what next , ..... :roll:

When using winrar you can extract all the files of your exe into one folder.
(Right click the exe and under options use "copy all files into folder"
Then take the 3 .nbf files and copy them into the folder with my files. Then start the MAupgradeUT.exe.

berni_1980 said:
When using winrar you can extract all the files of your exe into one folder.
(Right click the exe and under options use "copy all files into folder"
Then take the 3 .nbf files and copy them into the folder with my files. Then start the MAupgradeUT.exe.
Click to expand...
Click to collapse
Ok i'll try it tonight THX

Problem : if i use the rom from dangaard then the exe isn't a rar file, it's just an installer with everything in de exe ..
If i take a rom from the ftp and i unrar it then it are all CAB files and no .nbf files :roll:
Am i stupid or what? Witch version do i need and where do i get it? Maybe a link would do good :lol:
I'm really sorry for those questions, but here normally we just do the installer. I did allready a QTEK S100 and a QTEK 2020 with the installer from dangaard and everything worked fine. I just don't get it why i get the country id error now.

Try this one: ftp://ftp.xda-developers.com/BlueAngel/BlueAngel_Roms/BA_1.40_radio_1.20_untested_extrom/

DIY ExROM?

pls tell me how to delete files included in ms_.nba image file?
it promted me to enter password when i use rom editor.
when i ran xda3tool-x,it released a nba file,and when i renamed the nbf file,it could not be read all the same,pls tell me how can i corect this

I found the following procedure the easiest way to cook my own extended rom:
Load the ms_.nbf file onto your PDA as supplied.
Then unhide the extended rom.
Then add or take away cab files to your hearts content!
Be sure to adjust the cfg.txt file accordingly
If you are using Tuma 1.3 then this rom will look to your storage card for EXTROM on boot up so you can always keep & edit a visible version of your extended rom here.
If you are using 2003 SE, just use the no ID installer on this site and be sure NOT to install ms_.nbf on your PDA when upgrading your ROM
Regards,
Simon

here:
http://en.pdamobiz.com/en/forum/PDAforum_posts.asp?TID=395&PN=1
But, hint don't the format turn, this is why?

initflashfiles.dat -- Help Needed

So I've been playing around for a little while with the intention of creating my own custom ROM. I think I've got everything all figured out - however I'm having a problem that I think is related to the initflashfiles.dat file. Basically, after flashing my new OS ROM, my 8125 hangs at the splash screen with the version numbers on it. As a test, I redid my modified ROM, except I used the original initflashfiles.dat - this worked just fine. Tried it again by building the ROM with my modified initflashfiles.dat - same problem.
Here are the steps I'm going through.
1. Parse out the nk.nbf file using typhoonnbfdecode -x
2. prepare_imgfs 80040000-OS.nb -nosplit
3. viewimgfs imgfs_raw_data.bin
4. Modify contents of dump directory. Basically I've deleted files I don't need and added new ones.
5. Modifiy initflashfiles.dat (which I've attached). After modifying the file I open it in a hex editor and remove the first two bytes - making the first byte 3B (";"). I save it and mark it as read-only.
6. buildimgfs
7. make_imgfs 80040000-OS.nb -nosplit
8. Run nb2nbf_tornado.exe. I do run this correctly, using the correct memory address for the OS .nb file.
9. Put the new nk.nbf into an existing RUU self-extracting archive and run it.
It really seems like it's the initflashfiles.dat file - as I've successfully loaded this ROM with the original file (its really not the original, it's from a summiter ROM that I'm basing mine off).
Any thoughts?

I'm going to bump this once just in case people missed it originally.
I've messed around a bit more, and have pretty much isolated that this is my problem - but for the life of me I can't figure out what I'm doing wrong.

CameronJ said:
I'm going to bump this once just in case people missed it originally.
I've messed around a bit more, and have pretty much isolated that this is my problem - but for the life of me I can't figure out what I'm doing wrong.
Click to expand...
Click to collapse
Hi,
i see that the file you've attached isn't actually a .DAT file. It is a .dat.TXT that's the same that saying it's a TXT file!!!
If the file you're putting inside your ROM is this very same file (.dat.txt) then you've found your problem: you need a .DAT and NOT a .dat.txt file!!!
Try following this procedure on your PC (i suppose you're using XP or 2003 server):
- open a folder (whichever folder you like, it's not important)
- on the Tools menu click Folder Options.
- click the View tab.
- clear the Hide extensions for known file types check box.
- press OK
PS: Here is an illustrated guide on how to show file extensions
Now go to the place where your initflashfiles.dat is. If the file is named 'initflashfiles.dat.TXT' (like the file you uploaded in this forum) then:
- select the file
- press F2 (or right click and choose 'Rename')
- remove the tailing .txt from the name
Finally:
- let us know if it worked
Bye bye

risidoro said:
i see that the file you've attached isn't actually a .DAT file. It is a .dat.TXT that's the same that saying it's a TXT file!!!
Click to expand...
Click to collapse
:lol: Thanks for the reply.
I had to add the .txt extension otherwise the forum wouldn't let me upload the file (.dat files are not on the list of available file types for upload).
When I loaded the file I meant to put that explanation in there but forgot before I finished the post.

Hi. I don't know if you're still working on this, but I'd like to share with you my experience last night. I examined your initflashfiles.dat, and it is perfectly ok.
As I see in your initflashfiles.dat, there are a lot of folder customization like:
Directory("\Program Files\Task Manager"):-File("taskmanager.exe","\Windows\taskmanager.exe")
There is nothing wrong with this as we need the file to be in the right location. BTW, THIS FORMAT WORKED FOR ME. Just a thought, you might be editing the default.hv and user.hv (hives) to put in the registry keys of some applications?
My device (Himalaya) did not start out correctly and did not execute the initflashfiles.dat, BUT when I connected my Hima through active sync, you can actually explore the contents. SO, in this non-working state, I experimented in tracing the culprit, by restoring a couple of the original files I edited. I found out that it has something to do with the way I edited the hives.
Steps I made in experimenting:
1. I sync my Hima to my PC.
2. Copied the original default.hv to \windows directory
3. Hard Reset Hima, BUT answer NO to all three boot options
4. My Hima started normally and executed initflashfiles.dat to the detail.
Discovery from experiment:
1. The files were only copied to the directory were we wanted it, BUT the original file is still in the \windows directory. Therefore, we did not save storage memory.
2. We only benefitted from an already installed app built into the ROM.
Hope this gives you some insight.

[How To] Step by step guide to Backup your Shift to nbh (All Steps!)

Please rate this thread if it was useful...
I know that stuff like this has been posted before but I have never seen a full guide begining to end on how to backup your rom so here is the complete guide (with links) beginning to end of how to backup your WM6X ROM on HTC's Shift to an NBH
To do this you will need a HTC Shift (dir), and basic knowledge of Windows Mobile, Vista, the command prompt and Syncing a WM device with a computer.
NOTE: I am NOT sure if you need HardSPL on the device to flash the ROM back onto your Shift (if someone could let me know that would be great), my guess is that you do as the created nbh will not be signed with HTC's Cert - HardSPL can be found here http://forum.xda-developers.com/showthread.php?t=406606 and is compatible with GSM Shifts only (x9500)
If anyone has any suggestions as to how this post could be improved or tell me if something needs a more in-depth explanation, let me know - Thanks.
First you will need to Liberate your shift; instructions on how to do this can be found here: http://www.modaco.com/content/windows-mobile-news/266537/liberate-your-htc-shift/ (this step will "unlock" the restrictions on windows mobile - this is not necessary but makes installing RAPI tools and other files easier later.
Download HardSPL (we are not going to install HardSPL in this post, but the download includes RAPI that is needed prior to the next step) from here: http://forum.xda-developers.com/showthread.php?t=406606
When the download has finished extract the contents and copy EnableRapi.cab to your device (To do this select Settings from the today screen > USB Tool > Options > Detach from Vista > Options Attach to Vista - yes detach is not always required but seems to solve some issues with syncing).
Your device will now appear in "My Computer"; copy the file somewhere to your device then switch to Windows mobile and run the file.
Download the latest version of itsutils from: http://www.xs4all.nl/~itsme/projects/xda/tools.html (Look under download section) then follow the instructions on http://forum.xda-developers.com/showthread.php?t=382609
After you have followed the instructions there you will have created RAW files of your Windows Mobile ROM (on the post you will notice the the code window in color - these may be different depending on your device and may need to be changed)
Now we need to convert the raw file to an nbh to do this you will need to download the shift kitchen from: http://forum.xda-developers.com/showthread.php?t=422914 then extract the files from the rar archive (using winrar, winace etc)
On some computers the below operation may fail saying "Error loading dll msvcr71.dll" so you should download and extract the attached zip file (msvcr71.zip) to the Tools directory
When you have done that put the *.raw files created by itsutils into the BaseROM directory and run the !BEGIN.cmd file
Select option 2 when asked to rebuild a ROM and follow instructions.
When the command has completed run the !COOK.cmd file; When a window appears titled BuildOS Click on the Play button and wait for the process to complete then close the BuildOS window
Follow further instructions; until another window appears, Select Shift as the "Target Device" and under "OS" select os-new.nb, then click "Build NBH!",
A window will appear asking you to save the NBH - DO NOT CHANGE THE PATH as it kept crashing when I tried to save elsewhere and call the file RUU_Signed.nbh
Copy the file RUU_Signed.nbh where you want and download and extract CustomRUU.zip (attached) to the same path
To restore the ROM all you need to do is Sync with Vista and run CustomRUU.exe
Feedback is always welcome,
Thanks,
Kris

*RESERVED*

All done! But when performing this process
BuildOS Click on the Play button and wait for the process to complete
I have Error window:
Error: File `ROM\XIP\boot.rgu` not found.
and when I click `OK` - process stops!?
What is wrong?

All done without errors!
Previous Error was under XP on D:\ with many subdirs to `shiftkitchen`.
Now all OK is under Vista with `shiftkitchen` in root of C:\
Thanks!
Little question. I am backuping original Russian ROM... an in the ending window (when I choose "Shift" and "os-new.nb") there is Language:WWE. Is there have to be something else?...

sardonix said:
All done without errors!
Previous Error was under XP on D:\ with many subdirs to `shiftkitchen`.
Now all OK is under Vista with `shiftkitchen` in root of C:\
Thanks!
Little question. I am backuping original Russian ROM... an in the ending window (when I choose "Shift" and "os-new.nb") there is Language:WWE. Is there have to be something else?...
Click to expand...
Click to collapse
When you flash your ROM it will be the Russian ROM ... the WWE setting there and the version are just what is displayed in the ROM flashing tool (CustomRUU.exe)
I had the Spanish version and used this process beginning to end - and it says WWE in the flasher but still installs the Spanish version
Kris

Kris, thanks! Believe that I`ll not have reason to use it. But with this reserved ROM it is composed to make any ROM manipulatios.
Thanks once more!

can i request this to be a stickey?
thanks

Great work i00
I have added it to the WIKI and the FAQ thread.

I confirm that you DO need to install HardSPL on the device PRIOR to flashing the ROM back onto your SHIFT.

it's work

someone got shipped UK rom backup ?

kgx said:
someone got shipped UK rom backup ?
Click to expand...
Click to collapse
Radio is here .. will upload the ROM shortley
http://rapidshare.com/files/232295760/Shift_Origional_UK_Radio.zip
Regards,
Kris

kgx said:
someone got shipped UK rom backup ?
Click to expand...
Click to collapse
Orig UK ROM can be downloaded here:
http://rapidshare.com/files/232298625/Shift_Origional_UK_ROM.zip
Regards,
Kris

Sorry when I try following your tutorial,
I have not os-new.nb file what could I do wrong?

Back-up the rom and radio files
Hi i00, absolutely great guide, thank you for the hard and tidy work!
Since I'm a beginner in this area, before doing the dump job myself, kindly ask you to advise if the dump operation leaves the Shift unchanged on the winmo side and I can use it further, i.e. it is a read-only operation OR do I need to load back (flash back) the resulting back-up files (ROM and radio)?
Thank you!

rom
Hi all
i just bought a brand new shift and want to have a back up of the ROM
I've exacted 4 parts of the rom, but unable to convert it back into a NBH
i cant seem to figure out if i need the RUU_Signed.nbh , and where do i get it from, i thought i was making RUU_Signed.nbh from the 4 raw part files.
if anyone can re upload the complete UK ROM.NHB i would be grateful
i have uploaded the 4 part files and the boot loader
www(dot)filedropper(dot)com/rawfiles
part00.raw
part01.raw
part02.raw
part03.raw
SPL.nb
also do i need hardSPL to even load the original back up rom?
thanks
is this the file i need to include in my baserom folder?
forum(.)xda-developers.com/showthread(.)php?t=1875806
Need Radio ROM GPS+Phone Modded 1.27
here is my error code:
Welcome to Kaiser ROM Kitchen
-----------------------------
Please choose the way for Kaiser ROM Kitchen to work:
Enter 1 if you want just to cook ROM
(RUU_signed.nbh required in BaseROM folder)
Enter 2 if you want to rebuild and cook dumped ROM into flashable ROM
(RUU_signed.nbh, dumped part01.raw and part02.raw required in BaseROM folder)
Please choose 1 or 2: 2
Could Not Find C:\kaiserkitchen\baserom\os.nb
Could Not Find C:\kaiserkitchen\baserom\0*.*
Path not found - C:\kaiserkitchen\temp
The system cannot find the file specified.
The system cannot find the file specified.
=== NBHextract v1.0
=== Extract contents from HTC NBH files
=== (c)2007 xda-developers.com
=== by: pof & TheBlasphemer based on itsme perl scripts
Error: Could not open 'RUU_signed.nbh'
The system cannot find the file specified.
The system cannot find the file specified.
1 file(s) copied.
1 file(s) copied.
Press any key to continue . . .