Database Users

RUU.. upgrade does not complete

Hi,
This is the first time I try to upgrade my Qtek :roll: . I downloaded the RUU3.16.52.exe and RSU3.23.01.exe .
But I run the RSU3.23.01.exe (by mistake ) which completed successfully. When I run the RUU3.16.52.exe it continues until the last step where it say connecting to device and then exists and nothing happens on Qtek nor on the PC.
Any help appreciated.
ReNEGade

I have a stupid idea if the flash utility doesn't work for your machine.
You need a SD card and SD card reader, and the XDArite.exe (XDA rom image tool) , extract the rom files from the ruu3.16.52.exe (nk.nbf) and write it to the card.
Then insert your SD card to the Qtek and enter the Bootloader, flash the rom , everything will be ok.

Xdarit doesn't write with new .nbf files ?

I use the Xdarit to read & write the Rom image from my MDA.
I managed to read from the SD card and stored on my harddisk.
When I create back with a new rom .nbf files to the SD card and read back again to the harddisk, the SD show the original files size that from my MDA not the one that I'm going to upgrade to ? I rename the files to .nb1 extension.
Do I need to reformat the SD Card ? Do I need a new SD Card for the download ?
Dear XDA developer #..., please advice. I have been posting and yet to get some good advice and replies.
I would appreciate very much of your expertise in this matter.
Thanks again

they should be the same size, nb1, and nb0 files always are fixed size

more answer:
- when using xdarit you never have to format sd cards.
- renaming files will probably confuse XDARit, since this
is how xdarit recognizes what kind of file it has.

What I meant original file sizes.
1. Read from SD Card ( backup from MDA )
bootloader 5-15.nb0 256 K
WindowsCE 5-15.nb1 32,512 K
2. Write to SD Card ( with new ruu extract from O2 ie )
bootloader 5-15.nb0 256 K
WindowsCE NK_Wallaby31413wee_O2_Fulll.nbf 31,745 K
3. Read back the backup step 2.
bootloader 5-15v1.nb0 256 K
WindowsCE 5-15v1.nb1 32,512 K
As you mentioned, the files size are fixed, therefore my files of
the 5-15v1.nb1 should have the content of the NK-Wallaby.....
and I should had leave the file extention as .nbf without rename it to .nb1
Or should i had wite back using the step 1 files name ?
Please advice, many thanks

if you rename an .nbf file to .nb1, you will burn an incorrect os image
to your xda. making it unbootable in OS mode.
( your bootloader will still work )
also, be careful updating your bootloader, if it fails somehow
it is very difficult to restore your xda
if you just want to update your OS, only write the ..nb1 file
or select the .nbf from your distribution, without renaming it.
this http://openwince.sourceforge.net/jtag/iPAQ-3600/ might
give you an impression on what you would have to do, to repair
your xda after you've trashed your bootloader

Bootloader still appear but buttons not working ?
Thanks XDA developers,
My case is that I might accidently overwrite the bootloader.
The bootloader still be able to appear and the GSM OK showed but none of the functions button be able to work.
Do you think there is a way to work around ?
Many thanks for your replies

can u tell about bootloader version?

Bootloader v 5.15 on a T-Mobile MDA with 3.13.12 GER & Radio T310.

i think u can try to make sd card that contain wallaby path (.nb2) using xdarit... logically u can access "action button" to flash the rom.... this is only way to activate "action button"
after insert sd card u can go on bootloader and see wallaby path, press action button, if it work u can flash the rom (may be u should find exact rom that installed before xda died, more work?)
hope u can fix this prob
regards

Hello All,
I can't write new ROM image to SD card with XDArit: I can read image from card, but when I try write new ROM image, I get "Failed to open device \\Physical device12" error message. I try both USB and PCMCIA card readers, but don’t work… What is the problem? (My PC is an Asus P4 notebook with WinXP Pro)
Thx your help & sorry my bad English
Hanzy

try to change device "mass storage device" with driver from manufacture, use one of xdarit executable 180kb or 1.39mb (find out in other thread)

Hello,
I install manufacturer's drivers, but isn't work
I download (found) only 180kb version of XDArit (and source code, but my C++ knowledge... khm...)
Can you write the 1,3mb version's link from me?
Thx

from http://xda-developers.com/forum/viewtopic.php?t=1094&highlight=xdarit
found this link, try it
http://givemebeer.com:8080/warez/XDA/xdarit.exe

Hi,
thx your help...
I read on another thread, XDArit work only with USB 1.1 ports... My laptop have only USB 2.0 ports... :roll: I changed my laptop with one old IBM Thinkpad and XDArit work correctly...
Regadrs & thanks
Hanzy

Not really, coz im using usb 2.0 and its work normally

I only have USB 2.0 ports too and it worked fine.

fastblazer said:
try to change device "mass storage device" with driver from manufacture, use one of xdarit executable 180kb or 1.39mb (find out in other thread)
Click to expand...
Click to collapse
Just searching for why I couldn't get XDArit to work with my system - seems the larger (presumably debug) build of XDArit has what's needed to work with the v4 nbf's - thanks for the pointer!

How to fix failure during upgrading ROM

I have a siemens sx56 with AT&T. I was trying to upgrade the ROM version to unlock it. Using XDA developer software and during this process, somehow the connection between the computer and the phone stopped (active Sync). Now the phone is not responding and the screen still displaying the upgrading process. I tried to reconnect but the Active sync does not recognize the devise. I read in this forum that you can solve this problem by using SD card with a good ROM version. Here is what I did. I copied the NK.nbf to the SD card using my computer SD read/write slot. I inserted the SD card in the phone and did the boot loader mode. What I got is "Wallaby boot loader v5.22 GSM OK" that set. Does the phone will automatically ask to press action to start flashing or I have to press a certain key. I tryed all the keys but they give me different tests that they work fine. So far I am not able to find the key that will install the the cooked rom. After that, when I tried to use the SD card in the computer, it did not recognize the card and ask me to format the SD card. I tried the fat and the fat 32 format and download NK.nb1 and/or NK.nbf and again I got the samething. Do I need to down load the ROM file using the XDAtool or just copying the file from the computer to sd directory will do it. I would really appreciate it if someone points out the best way of handling this problem (i.e. get the phone to work with the appropriate ROM and unlocking it) thanks.

Seif said:
I have a siemens sx56 with AT&T. I was trying to upgrade the ROM version to unlock it. Using XDA developer software and during this process, somehow the connection between the computer and the phone stopped (active Sync). Now the phone is not responding and the screen still displaying the upgrading process. I tried to reconnect but the Active sync does not recognize the devise. I read in this forum that you can solve this problem by using SD card with a good ROM version. Here is what I did. I copied the NK.nbf to the SD card using my computer SD read/write slot. I inserted the SD card in the phone and did the boot loader mode. What I got is "Wallaby boot loader v5.22 GSM OK" that set. Does the phone will automatically ask to press action to start flashing or I have to press a certain key. I tryed all the keys but they give me different tests that they work fine. So far I am not able to find the key that will install the the cooked rom. After that, when I tried to use the SD card in the computer, it did not recognize the card and ask me to format the SD card. I tried the fat and the fat 32 format and download NK.nb1 and/or NK.nbf and again I got the samething. Do I need to down load the ROM file using the XDAtool or just copying the file from the computer to sd directory will do it. I would really appreciate it if someone points out the best way of handling this problem (i.e. get the phone to work with the appropriate ROM and unlocking it) thanks.
Click to expand...
Click to collapse
Bro, you shouldn't change the Sd fat you erased what's written on it anyway your unit is still on the safe side and you can bring it to normal.
First of all downgrade your bootloader to 5.15 >>>
goto this http://forum.xda-developers.com/viewtopic.php?t=3274

Hi,
I also have exactly the same problem with my Siemens SX56 as those of Seif's. My Wallaby's boot loader version is 5.22. Ramram said that the first thing to do is to downgrage bootloader. But I couldn't understand how to downgrade the bootloader because I do not have a copy of old bootloader. Should I use 'OSImageTools' or 'XDArit' to write backed up CE image to SD card?
Seif, how did you solve your problem?
Best Regards

rafia said:
Hi,
I also have exactly the same problem with my Siemens SX56 as those of Seif's. My Wallaby's boot loader version is 5.22. Ramram said that the first thing to do is to downgrage bootloader. But I couldn't understand how to downgrade the bootloader because I do not have a copy of old bootloader. Should I use 'OSImageTools' or 'XDArit' to write backed up CE image to SD card?
Seif, how did you solve your problem?
Best Regards
Click to expand...
Click to collapse
You need XDArit to write the rom to your SD read the past post on how to copy rom to your SD which is the safest way of installing the rom into the device, by using XDAtools press on FIX BROKEN BOOTLOADER this will downgrade you bootloader to 5.15 don't forget to connect your unit to the cradle when you want to downgrade.
I recommend 1rst of all to make a quick search in threads to be totaly ready for this
this would help :
http://forum.xda-developers.com/viewtopic.php?t=6581&highlight=downgrade+bootloader
http://forum.xda-developers.com/viewtopic.php?t=2068&highlight=downgrade+bootloader
Good Luck now.

Update : How to fix failure during upgrading ROM
The problem was solved. Here is what I did. I copied the NK.nbf file to the SD card using the XDAtools. It seems that the XDAtools uses special format for the bootloader that well recognize the ROM file on the SD card. Rafia your bootloader (v5.22) is fine you do not need to downgrade it.
You should follow this procedure:
1. Install ActiveSync that comes with the device.
2. download XDAtools from this site and install it in your computer.
3. Cook the ROM ( or get it by extracting the zip file from the XDA developers special edition ROM.)
4. Use the XDAtools to copy the cooked NK.nbf file from your computer to the directory of the SD card
5. Insert the SD card in the dead device and go to the bootloader mode (soft reset while pressing power key). Make sure it has more than 80% battery before starting.
6. If it is still working and the bootloader ver. is older than 6.22, it will ask you to press action to start flasing.
7. Once finished, remove the SD card and hard reset, wait 60 sec and hard reset again.
Good Luck and special thanks to Biso for his help.

Re: Update : How to fix failure during upgrading ROM
Seif said:
The problem was solved. Here is what I did. I copied the NK.nbf file to the SD card using the XDAtools. It seems that the XDAtools uses special format for the bootloader that well recognize the ROM file on the SD card. Rafia your bootloader (v5.22) is fine you do not need to downgrade it.
You should follow this procedure:
1. Install ActiveSync that comes with the device.
2. download XDAtools from this site and install it in your computer.
3. Cook the ROM ( or get it by extracting the zip file from the XDA developers special edition ROM.)
4. Use the XDAtools to copy the cooked NK.nbf file from your computer to the directory of the SD card
5. Insert the SD card in the dead device and go to the bootloader mode (soft reset while pressing power key). Make sure it has more than 80% battery before starting.
6. If it is still working and the bootloader ver. is older than 6.22, it will ask you to press action to start flasing.
7. Once finished, remove the SD card and hard reset, wait 60 sec and hard reset again.
Click to expand...
Click to collapse
Thanks a MILLION for this info. I'm in the same boat, with bootloader 5.22. One question though, when I'm in bootloader mode, which option do I choose from the menu to transfer the ROM to my device from the SD card? Will there be something automatically coming up? Or will I use one of the options listed below:
1. CE ROM TO SD
2. BOOT TO SD
3. CE + BOOT TO SD
4. GSM ROM TO SD
5. CE + GSM TO SD
By the way, so I never do anything to ruin my device again, can someone please explain what each option does?? I really don't have a clue.

as you can read from the menu you type in all these options are to the SD card
and they are to backup i suppose
rom upgrading should start automatic when a sd card with valid rom is in the sdport
and you are in the bootloader
maybe it ask you i forget but it's not something you have to find browsing
the menu's

Rudegar said:
as you can read from the menu you type in all these options are to the SD card
and they are to backup i suppose
rom upgrading should start automatic when a sd card with valid rom is in the sdport
and you are in the bootloader
maybe it ask you i forget but it's not something you have to find browsing
the menu's
Click to expand...
Click to collapse
Thanks for answering my question. Now I simply need to find a really good ROM to use to load back onto my device. What I would like to do is end up with Windows Mobile 2003, but the device is locked at the moment.
Can someone recommend a ROM for me to load onto the device so that I can then unlock it and THEN upgrade to 2003? Or is there a 2003 ROM out there that will also unlock? Originally, I ended up in this predicament by upgrading to the 2003 upgrade from Rogers AT&T, but that locked the device on me. I then tried to use a cooked 2003 ROM, and that's where I am now, without a useable device.
Thanks for all replies!

Linger1974 said:
Rudegar said:
as you can read from the menu you type in all these options are to the SD card
and they are to backup i suppose
rom upgrading should start automatic when a sd card with valid rom is in the sdport
and you are in the bootloader
maybe it ask you i forget but it's not something you have to find browsing
the menu's
Click to expand...
Click to collapse
Thanks for answering my question. Now I simply need to find a really good ROM to use to load back onto my device. What I would like to do is end up with Windows Mobile 2003, but the device is locked at the moment.
Can someone recommend a ROM for me to load onto the device so that I can then unlock it and THEN upgrade to 2003? Or is there a 2003 ROM out there that will also unlock? Originally, I ended up in this predicament by upgrading to the 2003 upgrade from Rogers AT&T, but that locked the device on me. I then tried to use a cooked 2003 ROM, and that's where I am now, without a useable device.
Thanks for all replies!
Click to expand...
Click to collapse
First of all get the "Special Edition Rom" to your device Unlock it then cook any other Rom you prefer
Special Edition Rom at http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
Good luck

First of all get the "Special Edition Rom" to your device Unlock it then cook any other Rom you prefer
Special Edition Rom at http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
Good luck[/quote]
Thanks, Ramram. I'm sure I'll have more success this time, but it's just odd that I went from a 2002 ROM, which was unlocked, to the Rogers 2003 ROM, and the phone was locked after that.
I guess I should stay away from that Rogers ROM then?

Linger1974 said:
First of all get the "Special Edition Rom" to your device Unlock it then cook any other Rom you prefer
Special Edition Rom at http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
Good luck
Click to expand...
Click to collapse
Thanks, Ramram. I'm sure I'll have more success this time, but it's just odd that I went from a 2002 ROM, which was unlocked, to the Rogers 2003 ROM, and the phone was locked after that.
I guess I should stay away from that Rogers ROM then?[/quote]
Why to worry about the Rogers Rom you know now a way to unlock your phone.
I assume the Rogers rom is based like the At&t rom which it has the sound clipping bug , so I'd rather say that you could cook a T-mobile rom 4.01.16 WM2003 and try it it does not have the sound clipping bug..

Problems after Flashing - XDA1

Hi!
I flashed my O2 XDA // Wallaby 5.15
to WM2003SE.
The first Boot worked, after that, I wanted to switch the language to german, I had to reboot, and from there on, my problems began....
i read about the possibility to re-flash my os with an sd card.
everytime i plugin that card to my notebook, winxp says, i have to format that card.
after that, i tried to copy the nk.nb1 file to this card, with success...
and then, i plugged in that card back to my xda.... nothing happens...
if i press the "contactlist" button ( in bootloader ), i come to some backup modes, but not to read an new os-image from sd card.....
i'm getting crazy :/
can someone help me plz ???

You have to use xdatools to copy the Image to the sd-Card. It is written in a special format. Copying with the explorer is useless for flashing...
HTH
Stefan

i tried this some times....
but do i have to save "NK.nb1" to sd-card (( h:\nk.nb1 )) or in another format ?? for example sd-card image ( *.img ) or *.nbf .... etc
my last try for this evening....
must go to work in some minutes.. ;(
damn night-shift ^^ ( but good thing: nothing to do... just sit there and wait )

Download http://lumpistefan.dyndns.org/tools/XDATools.zip unzip it and run osimagetool.
Select the nb1 or nbf file in source and select your card reader with inserted SD-Card as Destination. Press Copy and wait until process has finished.
Insert the card into your xda. If there comes a message to format the card press no or do directly a softreset wirh power button to enter bootloader. Than the image should be recognized ....
HTH
Stefan

doesn't work....
what have i done ? *omg*
if i want to write an image to my sd card, my winxp wants me to format it....
if i do this, the writing works fine, but my xda doesnt recognize the new nb1....
i get no connection to my pc with the cradle ( but there is something being found in windows while my xda is in bootloader mode.... )

hi.
i've read something about problems with winXP, if you want to write a new os to sd card... is that true?
btw. it's still not working....
my pc - sd - card - reader/writer cannot write the file in that way my xda could read it as an new os......
holy ****

i solved the problem i think
the xda os image tool doesnt work with notebook internal sd-card-reader/writer.... or winxp is the problem....
now with win2k3 server it works..... *omg* i'm so happy
thx!!!!!!!!!!!!!!!!!!!!!!!

oppaunke said:
the xda os image tool doesnt work with notebook internal sd-card-reader/writer
Click to expand...
Click to collapse
I think that is the problem heard a few times, that the internal card reader made some trouble.
Glad to hear, that your device is working again....
Stefan

Probs flashing any rom via ntrw with my NEW mdacompact

:evil:
Hi everyone,
am deperately needing your advice!!!
Just yesterday I rechieved an exchange mdac from tmobile showing serial version v1.02 when put in bootloader mode(previously v1.01).
When trying to flash whatever rom once transferred via ntrw to my sd card, my mdac does simply nothing but stay in bootloader showing serial v1.02. No flashing like in my old one starts.
On removing the sd card it comes out freshly formatted, before it definately was formatted with raw as usual once working with ntrw.
Result : I can not upgrade my system to mksbigstorage or any other rom like i could with my" old one". (same sd card!!!)
Tried downgrading to an older rom version via original upgrade routine and from there flashing via sd card: same problem!, tried other sd card: no solution either!
Any ideas, solutions, people with the same problems?
:?:
Appreciate your help
Thanx

romflashing
Seems to have nothing to do with flashing routine.
Card simply gets formatted once inserted.
Any way to stop this?

Hi! I have had many problems after flashing and re-flashing my rom.
Try boot loader mode and USB then execute (from your PC)MaupgradeUT_noid with a Shipped_rom on XDA ftp. It may work.
Have a look at this link: http://www.mtekk.com.au/forums/viewtopic.php?p=32876
Regards

Try to write SD card with winhex not ntrw. Simply choose open disc feature and write file directly do SD it works every time for me (with ntrw it was roulette). I have 1.02 bootloader

Thanks Shamus but can you explain in details how do you do this with Winhex? my bootloader is 1.00
SPV_M500, ROM 1.12.02 FRE
RADIO 1.12.10
EXTRom no more