Database Users

ROM Backup to MMC - Problem

I had an XDA Asia version. Bootloader version 5.17. My PC has WinXP SP1.
I want to backup my original ROM before I can load it with other intersting stuff from this excellent XDA developper site. My steps:
1. I used XDARit and write the wallaby-patch-tool.nb2 to a MMC card.
2. I put it in my XDA and do a bootloader reset. My XDA lead me to the patch menu as expected.
3. I insert another MMC Card (64MB) and dump the CE ROM to the card.
4. I inserted the MMC Card back to the card reader and click [READ FROM SD CARD] button of XDArit. XDArit told me that "in correct signature" and DID NOT write the ROM content from the MMC card to my harddisk file.
5. I looked at the XDArit window showing the card bytes and did not see "HTC$WALLABY", rather it show something "FAT". Seems that XDA DID NOT write anything to the card. But also seemed that XDA DID write something to the card as it become unformatted (can not be read by Windows Explorer, whilst before it ca read the card folders and files).
Can someone tell me somehint to back up my ROM. Because I do not dare to upgrade my XDA without backing up my original ROM.
I read thru this forum and seemed that the possible problems are:
- Incompatible driver of WinXP SP1 => XDArit can not read properly?
- Some new trick of the 5.17 bootloader with the rom patch tool can not "cheat"?
- USB 2.0 problem (but my PC used USB 1.1)
- XDArit problem (but I tried both old and new XDArit with no success)
It seems that the XDA did write something to the MMC card but XDArit can not see these.
Please someone help. :lol:
I really want to play my ROM with lot of new things on this site, but dare not until I can back up and restore my current original ROM.
Quan
PS. I used "Flash Mate" card reader (4 in 1).

Please any one advise your solutions... I really want to play with my ROM, but before I can back it up.
Quan

Dear Quan,
More detail, can you contact to me
I have been using XDA for 11 months now together Samsung i700,
Used the same OS-Windows XP 1sp, Office 2003 beta in IBM Netvista 2.4
Upgraded Diff. ROM - this moment "WM -cooked ROM 2003" :wink:
[email protected]
Regards,
Hanoi

Hi Van,
Glad to see you are from Vietnam also. I have XDA just for 15 days. I love it very much. I also had Nokia 9210, but now I throw it somewhere in my home and did not even bother to find where it is.
As noted, I could not backup my current ROM. Something wrong in the middle but I did not know why. I have just tried last night on Win2000... Unsuccessfully. The symptom is the same.
- My XDA backed-up its ROM to the card and message me that "back up successfully".
- But when I inserted the card to the card reader and use XDArit, it seems that the card was not written by the XDA as I always saw something "FAT" in the window of XDArit, not something "HTC$WALLABY..." as described in this forum for an XDA image file signature.
- That's why when I choosed "read from SD card", XDArit always tell me that "incorrect signature" and stop.
- For sure that XDA did write something to the card because after XDA writing, I could not read the card thru the OS Explorer anymore (unless I re-format it).
I have tried on WinXP SP1, on Win2000 Pro but... the same symptom.
Tomorrow I will buy a new card reader and try again. If not successful, I will buy a new SD card and try and try and try... again until I can back up my ROM
I need to back it up before I can try many other interesting stuffs from this forum. First time I saw such an open-minded forum with many high-techies who willing to help like this forum.
Share me some hints please. I can not wait longer. :evil:
Quan

Need to check:
Which version Active sync (best 3.7)
Which version XDARit (best old version)
Downgrade Boot loader version 5.17 to 5.15 better for bootloader SD method
SD Card better than MMC
Windows XP better than 98 versions
I think that
The easy way to upgrade your XDA-ROM: run .EXE file on your PC synch with your XDA
http://www.o2.co.uk/productsservices/xda/romupgradedownload/0,,170,00.html
xda System Software Upgrade
To install the upgrade (ppc2002) on your xda:
1. Download and read the upgrade instructions (528KB)
2. Download the Radio Stack Upgrade v4.21 (1.54MB)
3. Download the Radio Unit Upgrade v3.17.03 (14.9MB)
The best Option:
From JEFF you can download
http://cuba.calyx.nl/~jsummers/ROMkitchen/
Steps:
1. Full recharged battery
2. Back up your data
3. Soft reset your XDA
4. Sync to your PC
5. Plug your AC adaptor to Cradle
6. Run ROM.EXE in your PC
7. Total time about 5 minutes
8. Completed
9. Unplug your XDA from Cradle
10. Hardreset (2 times- interval 1 minute)
I can read more detail in your PC on the process upgraded
Do not be afraid, you can do it!
Good luck!

Hi Van,
To reply:
- I am using ActiveSync 3.7.
- Can you send me XDArit old version. By email to [email protected]
- Yes, I tried both SD and MMC. But no results.
- Never use Win98.
My questions:
- How can I get bootloader 5.15 image (.nb0 file, right?) to downgrade
- Or the EXE upgrade from O2 UK site include this 5.15 bootloader?
- I have also made 3.17 ROM from Jeff's kitchen. Do you know that this Jeff EXE include the 5.15 bootloader?
- Your advice is to upgrade using EXE from O2 UK? Or from Jeff's kitchen?
- Have you ever tried backup/upgrade using the bootlader way, any experience? Please share.
I am just afraid I did something wrong and can not revert my XDA back to the original status!!! A bit scared.
BTW your XDA original bootloader is 5.17 or 5.15? If 5.17 then please tell me how you downgrade it from 5.17 to 5.15?
Thanks very much for your helps
Quan

@ Quan
Fist time upgraded ROM I have the same feeling
For PPC 2002 no problem (6 times upgraded)
For WM 2003 Test ROM 4.00.01 some bugs- my XDA had loosed phone function 3 days :evil: but in the end everything is OK (advice from this forum)
http://www.o2.co.uk/productsservices/xda/romupgradedownload/0,,170,00.html
Try it and you can say so easy! :lol:
Anyway you can call me before...

unlocking problems

Hi !
My device (PW10B1
3.14) doesn't unlock !
xdaunlock util says can't find code
trying to upgrade to developers 1.2 failed cause it's ver. 3.14
kitchen packs are available for ver. 3.17 and up
don't have a serial cable so didn't try other stuff
what do I do ?
Thanks guys,
Gili.

gilicomps said:
xdaunlock util says can't find code
Click to expand...
Click to collapse
Xdaunlock requires the wmodem in PPC2002. This is available in ROM 3.17.03
gilicomps said:
trying to upgrade to developers 1.2 failed cause it's ver. 3.14
kitchen packs are available for ver. 3.17 and up
Click to expand...
Click to collapse
Why does it fail? How are you trying to upgrade?
Normally you can update to all versions....
Stefan

it says that it's for ver 3.17 and I have 3.14
so it won't let me upgrade

using exe
when tried using sd image and didn't work (don't recognize my sd)
the question is if there's an exe upgrade for 3.14 ?

Re: using exe
gilicomps said:
when tried using sd image and didn't work (don't recognize my sd)
the question is if there's an exe upgrade for 3.14 ?
Click to expand...
Click to collapse
How do you try it?
You mus copy the ROM-file via XDA-Tools to your SD-Card.
After inserting the card in your device a windows popup will format your card. Donßt agree to this.
Enter bootloader by pressing the powerbutton and perform a softreset.
Bootloader will automaticly detect, that there is a ROM-Image on the Card.
You have to press the Actionbutton to do it.
It should work....
A few days ago there was a link to a step-by-step description how to upgrade.
Search for it...
HTH
Stefan

d/l new OSImageTool it asks for source nb1 (and doesn't find anywhere ..)
and destination (Can't set to my flash card)
So I don't really know how to transfer the image

Burning ROM - phone not working

Hi, I'm hoping to get some help with cooking and burning ROMs to my o2 XDA.
My original product specs are:
ROM Version: 3.20.06 ENG
Radio version: 4.21.01
I cooked and then downloaded 4.01.00 ENG from Lumpi Stefan's site, then ran the rom.exe file that it produced for me. Everything worked fine, and then I rebooted my XDA. Upon first boot the phone appeared to work, but after performing a soft-reset because the XDA froze, all of the phone functionality appears to be not working.
When I do a hard-reset I get: Wallaby Bootloader v6.22 - GSM OK which I think looks good as far as the phone functionality is concerned. Looks like it's the OS that's on the XDA which is causing the phone difficulties.
I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started!
I don't have an SD card, and am in dire straits about getting my phone to work. Is it possible at all to get this to work, or perhaps to go back to my original ROM (I backed it up to orig.nb1) using XDAtools. Anytime I try to burn the .nb1 file back to my XDA it fails. Or is the ONLY way to get an SD card and use the Bootloader technique? I even tried downloading the 3.17.03 ROM upgrade directly from the o2 sitebut it fails.
Any help will be GREATLY appreciated.
Thank you.

[qoute]I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started![/qoute]
this is true with 4.00.10 and 4.00.16 but not anymore with 4.01.00.
if your xda still can be connected to activesync, try to reflash the ROM.
Otherwise, you have to use the SD flashing method.

[qoute]I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started![\qoute]
this is true with 4.00.10 and 4.00.16 but not anymore with 4.01.00.
if your xda still can be connected to activesync, try to reflash the ROM.
Otherwise, you have to use the SD flashing method.

Thanks, I will try. ActiveSync still works...
I notice you are running the same ROM version as me - sis your radio still work?

Can you verify that I am trying to Flash the ROM correctly?
1. Confirm that I have orig.nb1 - yes, it's there - backup of original ROM before I started this whole dilemma.
2. Ensure that XDA is Activesync'd - yes, as "Pocket_PC" - all working okay.
3. Right click on orig.nb1 and select "burn"
4. OSImageTool.exe then pops up and copies orig.nb1 to Programme A.
5. A DOS box then appears saying "ERROR: GetConnectionType - A
ote host. error getting connectiontype".
6. Programme A then runs and after pressing "next" a couple of times, I get an error - "Error 011: Cannot execute the remote communication program. Pleace make sure that the USB cable is properly connected."
And that's basically it.
I have tried different variances of this, but all without success.
Help!
BTW, I'm logged in to MSN Messenger now, could you let me know when you're online - or anyone else, for that matter. My address is [email protected]

This message means that the current ROM in your XDA can't be flashed through Program A ... not a big issue, for unknown reason it happened with me few times ... but now you have to use SD card to flash your ROM.

Here is an update...
I have played around some more with the XDA with no success. I have now bought a 64MB SD card and am unsure as to how the ROM image on my PC gets onto the SD card. This is how I have been doing it:
1) Insert SD card into XDA
2) Place XDA into cradle
3) XDA then ActiveSync’s to the PC
4) Run OSImageTool.exe and select the following –
a. Source: “C:\Documents and Settings\Paul\Desktop\orig.nb1”
b. Destination: “XDA SD card slot – unknown size”
5) Then I press “copy” and I see the progress bar go across to 100%. After this appears to finish, the program just sits there not telling me it’s finished. I assume that it’s all okay and I then close the program
6) Take XDA off cradle and hold power button down whilst doing a warm-reset
7) The following appears: “Wallaby Bootloader v6.22 – GSM OK” – nothing else happens, and from what I have read it is supposed to ask if I want to perform a ROM upgrade. However, I can get into the diagnostic and flash tools by pressing the action button etc, but nothing is in there to upgrade the ROM.
Does the fact the OSImageTool destination says “XDA SD card slot – unknown size” matter? I’m assuming not because when I have transferred the ROM using the above steps, the XDA asks if I want to format the card; meaning that the transfer worked okay. Do I have to have an SD card reader/writer on my PC to get the ROM onto the SD card?
I have read a little about a Bootloader patch – do I need to run this, and how do I get it onto the XDA – using the same method?
I would be very appreciative of any help that can fix this, as all I want to do is get my three-day old XDA working again!
Any other comments and help in relation to solving this hair-challenging issue would be great!
Thanks,
Paul…

Ok ... from what you wrote it seems your doing it correctly. However, I have doubts on the file orig.nb1 you are using ... maybe it wasn't copied properly.
Try to cook any ROM (TMO 4.01.00 is good) at Stefan kitchen and you can cook it as .nbf or EXE then extract the .nbf file using winzip or winrar.
Follow the same steps and let me know.
Good luck ...

Is bootloader v6.222 okay - will it allow me to overwrite my current ROM with this new ROM that you are suggesting? I have read that I may have to downgrade my bootloader to do the SD ROM writing thing.

I can't confirm that my self ... I used SD with 5.17 and 6.22 without problems but maybe it's my luck
Cook the 4.01.00 as EXE and try it as is or extract the .nbf file and use the SD method.

Okay I'll give that a go now... Will let you know how I go...

Nope - didn't work. I'm not getting a screen in the bootloader to update the ROM via SD - if I press the action button I get into dignostics...
Is this a bootloader issue, and if so, how do I downgrade?

Also just tried the following:
C:\Program Files\XDAtools\binaries>pnewbootloader bootloader_v5_15.nb0
And got the following error message:
Unable to find flash info offset, cannot disable bootloader writeprotect
Any ideas?

I don't get it ... you cooked and downloaded and tried a new nbf file for TMO 4.01.00 in less than 15 minutes ??!!!!
what is the nbf file size ??

Yes, I used Winzip to extract NK.nbf. It is 31,745kb.
I am now cooking on Lumpi's site a zipped NK.nbf file and will try that too...

ROM from Magican

Hi all,
for to get ROM from Magican you have:
-make a backup of your device with xbackup (it is a program in your MDA Compact).
-insert a sd card on your device,
-press and hold power and camera button and do a soft reset
-connect your device to your PC with the USB cable and disable USB on Active sync
-run MTTY.exe and select USB
-press enter, type d2s and press enter again (these command should backup ROM in to SD)
-when finish (you'll see it by device display) get the SD and insert it to a cards reader
-for to copy the file in SD Card to your PC you have to use NTRW and run it with this command: c:/ntrw read MDAc.nb1 x: (x is your card reader so replace with the letter of your card reader) and get NTRW in C:
-after that you should have in C: a file called MDAc.nb1
Now would be nice to upload it to FTP site or some where else.
For more information you can see here:
<http://www.xda-italia.com/modules.php?name=News&new_topic=5>
<http://forum.xda-developers.com/viewtopic.php?t=2110&highlight=mtty>
<http://forum.xda-developers.com/viewtopic.php?t=4557&highlight=bootloader+commands>
<http://www.xs4all.nl/~itsme/projects/xda/bl-ii-usage.html>
Ciao,
Gibbo.

"d2s 0" for dump bootloader (required for change language)

Xetra said:
"d2s 0" for dump bootloader (required for change language)
Click to expand...
Click to collapse
Thanks for the information!

how do you do to backup also the extended rom and the radio rom ?
thanks

Hi, when you backup the rom, the extended rom must be also included.

what do you mean by "must" : it's done when you enter "d2s" under Multi-Port/USB TTY ?
And for the radio rom ?
Thanks

jpa said:
what do you mean by "must" : it's done when you enter "d2s" under Multi-Port/USB TTY ?
And for the radio rom ?
Thanks
Click to expand...
Click to collapse
"d2s 0" to dump boot loader (required for language change)

Can you use the XDArit or SDCardTool GUI utilities to copy the ROM from the SD card to the computer?

aristobrat said:
Can you use the XDArit or SDCardTool GUI utilities to copy the ROM from the SD card to the computer?
Click to expand...
Click to collapse
I don't think so!
Anyway seems that nobody is able to dump the ROM of their English MDA Compact!!!

I have an English ROM from Dutch MDA Compact (Locked to T-Mobile) available for those who want it. Please PM me. (IMG file for use with Jeff's XDA Tools)

Wiz said:
I have an English ROM from Dutch MDA Compact (Locked to T-Mobile) available for those who want it. Please PM me. (IMG file for use with Jeff's XDA Tools)
Click to expand...
Click to collapse
Thanks Wiz.
Could you post your image to xda FTP site?
ftp://xda:[email protected]
Cheers.

@Wiz : your rom image was not good. You sent me a file with a size of 3 Mo on your last email.
Are you sure that Jeff Tools are ok for a magician ?
Thanks to try again maybe with mtty ?

MTTY gives the same result. Also 3Mb ... appears that the tools are not compatible with the Magician

with my german rom, when i use jeff tools the size of my image is 32 243 712 octets.

SD size
Wiz said:
MTTY gives the same result. Also 3Mb ... appears that the tools are not compatible with the Magician
Click to expand...
Click to collapse
The size of SD image should be the same size of the SD Card (if you use NTRW).
Wich command on bootloader are'u using for dumped the ROM to SD?
Any body knows the rights strings?
Thanks.

I am now uploading the English ROM dump from my Dutch T-Mobile MDA Compact to ftp://xda:[email protected]/Magician. The filesize is (zipped) 172Mb, so bear with me please, should be finished in 1 hour or so ...

thanks. I opened it with winhex. I am not a expert but something seems still strange. There is 256 Mo of data (and no blank) ?

Has the extended been posted yet? I really want that cool screen rotation app that sits in the system tray.

take note that the magician os rom is 36Mbyte.
see MagicianRomLayout in the wiki for more info.
the old xda-1 'jeff tools' will give you a very truncated rom.

outz said:
Has the extended been posted yet? I really want that cool screen rotation app that sits in the system tray.
Click to expand...
Click to collapse
hi,
it's not a cab since it's already instaled even if you don't let autoconfig run after hard-reset.
and it doesn't appear anywhere in the compact folders(windows, programme, etc...)!

Ther must be a way for UNBRICKING

Hi, I searched a lot on forum and found a way for flashing from sdcard in Hermes forum.
There for i took a RUU_signed.nbh file copied to the fromated SDcard
- renamed it to HERAIMG.nbh (similar to HERMIMG.nbh on hermes forum)
--> and put the phone in bootloader
--> it starts searching sdcard
AND THEN
--> a processbar appears and it says "Checking SD contents"
BUT
--> "Invalid Certificate" - press any key.
So there must be a way to flash from SD card.
I will try different RUU and tell more.
Someone wanne help?

It must be named
"HERAIMG.nbh"
then it stops on white screen saying: Checking SD contents
But i got
Invalid Certificate

AND when it is an official .nbh extracted from RUU_xxxxx
it stops for 5sec on
"Checking SD content"
but the processbar doesn´t change and then it goes to bootloader without changing anything.
????????????????????????????

I will test this method too, i saw some flash of SD hen going into bootloader mode, did'nt know there was an option like this i will post my experiences

I tried these two RUU nbh's:
- RUU_Herald_HTC_WWE_5.4.405.1_4.1.13.34_02.79.90_Ship
- RUU_Herald_HTC_WWE_1.8.405.1_02.71.90_Ship
I've firtstly formatted my SD card, then copied NBH file's to my SD and named them HERAIMG.nbh.
Both times there was only a statusbar that did not proceed loading, and my continues in bootloader after 3 seconds...
Also got the Invalid Certificate error when I copied the WM6 nb of ASerg and renamed it to HEARIMG.nbh.. what is this certificate? and can it be edited in a way so we can flash??
Talking about unbricking anyway, can Herald users use Platform Builder?? i read in a thread that you're phone has to have KITL, but i don't think the Herald has KITL.. Can anyone who knows for sure please tell?

The Dutchman said:
I tried these two RUU nbh's:
- RUU_Herald_HTC_WWE_5.4.405.1_4.1.13.34_02.79.90_Ship
- RUU_Herald_HTC_WWE_1.8.405.1_02.71.90_Ship
I've firtstly formatted my SD card, then copied NBH file's to my SD and named them HERAIMG.nbh.
Both times there was only a statusbar that did not proceed loading, and my continues in bootloader after 3 seconds...
Also got the Invalid Certificate error when I copied the WM6 nb of ASerg and renamed it to HEARIMG.nbh.. what is this certificate? and can it be edited in a way so we can flash??
Talking about unbricking anyway, can Herald users use Platform Builder?? i read in a thread that you're phone has to have KITL, but i don't think the Herald has KITL.. Can anyone who knows for sure please tell?
Click to expand...
Click to collapse
The .nbh are "signed" os files. you can generate these fiels by "nbhgen.exe" but i didn´t get it to work with an RUU - it allways says "image is corrupted" because it only contains OS.nb
when you extract an RUU_signed.nbh out of the RUU_xxx.exe it contaisn splash.nb, os.nb, extrom.nb, spl.nb etc.
That´s the certificate = the singend nbh

So that won't be an option I guess... too bad
but does the Herald have KITL in bootloader mode? if so, you could use Platform Builder to unbrick your phone.. that would be very very sweet.
And what is this mtty thing? should be some funky stuff to

The Dutchman said:
So that won't be an option I guess... too bad
but does the Herald have KITL in bootloader mode? if so, you could use Platform Builder to unbrick your phone.. that would be very very sweet.
And what is this mtty thing? should be some funky stuff to
Click to expand...
Click to collapse
MTTY never worked for me - but that could be my system. And KITL - i don´t know what this is. sorry.
I sent it to O2 and hope they will repair some minor bugs and also the booting problem.

Little thready about unbricking a Hermes with KITL + Platform Builder:
http://forum.xda-developers.com/showthread.php?p=1162054#post1162054
Hmm i'll have a look around to find out what this mtty thing does..
btw: KITL = Kernel Independent Transport Layer, it is the windows ce kernel debugger interface

Is there anyone continueing papamopps' solution to unbrick Herald?

^^no need anymore, you can just use an official WM6 RUU

blackout203 said:
^^no need anymore, you can just use an official WM6 RUU
Click to expand...
Click to collapse
That´s not right. For unbricking a XDA Terra we still need a soulution.
The Terra IS NOT the P4350!!!!!
And the RUU updates are for P4350 (and in some cases for VPA compact)
But not for terra - we have to wait for an O2 update....

Vendor Id
I have a Vodafone CID(?) locked bricked HTC P4350.
Using the HTC updates I cannot unbrick my phone, because it keeps saying "Invalid Vender Id".
This unbricking with flashcard could be a solution for me.

I already try with official rom, but my herald is still brick, i can not syncronize the herald with pc to run the official rom.
It is freeze in inicial boot with HTC logo.
help, please anyone....

You can't simply place the rom file to the card and hope the device will read it in this way. In my time working for pda service, we used WINHex to format the card (to RAW-unformatted) and then we wrote the rom file in RAW format to the card. Your card looks like an endless stream of hexazecimal values. Only winhex recognises this format, if you insert the card to the computer, it will simply ask you to format it. After inserting this card into the pda, it will start the upgrade . The order of this operation was, as I remember, to fill the card with 0000 values (there is an option in WINHex, a kind of format) then write the rom file to the card in RAW mode. Then insert the card to the device.
Another way was to use MTTY, connect the pda to the computer (PDA should be in bootloader), open MTTY and connect with the device. ActiveSync should be killed before this. In MTTY in the terminal window write "set 14 0" then remove the data cable, then close MTTY, reconnect data cable then run the RUU.
These methods worked on HP Ipaq's wich we were repairing in our service center some time ago. I don't know if it works for herald or htc products because their RUU has a different way to register with the device.