upgrade Bootloader V5.17 - MDA, XDA, 1010 Software Upgrading

hi, my O2 XDA is using the V.17 bootloader, last time i upgrade to win2003 but now i want to return to the original ROM, how can i do this? i try to run the original upgrader (from O2 web site) it can't work. then i try using the cooked ROM when it start, it said "ERROR: GetDeviceData - An existing connection was forcibly closed by the
host." how can i return back my original ROM? because this cooked ROM give a GSM Problem, that every few (2-3) hours i need to softreset my PDA, otherwise i can't make/recevice call/sms. please kindly help and guide me to return my original ROM
FYI: i have-> 1GB SDCard, 1 card reader, and a O2 XDA + cradle.
Regards,
Freddy

Extraction of some part of the Wiki:
# Wipe the SD card (format FAT). Stick the SD card back into the pda and soft reset, then cradle it.
# Go to a DOS prompt and CD to where you have extracted the XDATools
# Type 'pnewbootloader bootloader_v5_15.nb0' to write the Wallaby 5.15 boot loader to the device.
The output looks like this:
D:\XDAtools\binaries>pnewbootloader_40116 bl515.nb0
Copying D:\XDAtools\binaries\itsutils.dll to WCE:\windows\itsutils.dll
in FindFlashInfoOffset
protection found at 8c0d60f8
result: 00000000 00000000
Click to expand...
Click to collapse
HTH
Stefan

this is how i done.
C:\XDATools>pnewbootloader.exe bl515.nb0
Unable to find flash info offset, cannot disable bootloader writeprotect
C:\XDATools>
can help me again \
Regards,

problem solved, due to lack of files hehe. Thanx anyway.

Related

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...

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.

69xx bootloader command for extracting ROM

Hello,
please, if somebody has more information about bootloader commands supported by HP iPAQ hw6900 series (HTC Sable) to share on this thread with us
Will be very helpful if we can extract ROM image through the bootloader of this iPAQ
I dont know much, i know nothing indeeed, however i found somewhere a pack of files for the Wizard that were supposed to work for the sable, however they didnt, but there is this particular file, that when ran in the sable made appear a folder called "2" with an icon of a storage card and which rpely the contents of the root of the device (but for itself i mean no 2 folder inside the 2 folder lol)
I dont know if it is of some use but i definitevely want to perform a corporate install of windows in my sable and kill all that HP crap that comes in bundled
How to enter bootloader
Just press ACTION+POWER+reset with stylus and hold this combinaison for a few seconds, you'll see a screen without backlight (so you must be under bright light to see it) going into bootloader mode.
Put your device on the cradle (which I suspect you had connected it to your PC)
using mtty, connect to your USB Port (or Serial port if serial cradle)
type "password BOOTLOADER" and use "h" as an help command.
Now you can dump a ROM from Bootloader
The command should be sth like "r2sd"
Read the manual of this command "h r2sd full" and use it to dump your ROM on the SDCard
Now you can dump the raw ROM image from SD Card Reader using ntrw.exe
EDIT: going to bootloader mode seem to hard reset your device, backup FIRST!
HI Boris,
where to find the manual ETC.
A RAW ROM maens a bin file? how to convert then to something readable modifiable.... i understand that this is the main issue now.
I want to see a computer file which isn't binary based....
or a full text ROM
In fact, for me a raw ROM is a ROM-file which has been extracted from the device... The difference with a ROM-to-install is the encryption which is not present with raw dumps (to be checked).
Raw dumps can be modified and then re-updated but it needs some operations that are command-line based...
Once you got your raw ROM on SD, copy it to PC using ntrw, you have to find the correct tool to dump the content (dumprom should do the work)
Remember to keep the raw ROM as a backup, and work with a copy of the raw ROM.
You can also cut/paste the file into parts (OS, EXTROM...).
Logically, if you got the original ROM file (the german one) and the same taken from the device (raw ROM), we should be able to modify some existing tools to work with 69xx ROM files and cook some ROMs.
in bootloader mode: type
"h COMMANDNAME full" should show full manual of COMMANDNAME.
To have more informations, once you know if your bootloader has d2s or r2sd ... command name, search for it on wiki and you should have more informations and examples on the specific command.
I need to extract the ROM from one of these as well. I am getting into bootloader and trying to dump the rom to 256MB SD as follows...
USB>
USB>
USB>password BOOTLOADER
HTCSPass.<YHTCEUSB>d2s
SD:Waiting for card insert.........
CMD3 for SD, it's OK, ready to get RCA from response.
SDetected one card
SD:ready for transfer OK
d.total_lba=7A000
d.block_size=200
d.RCA=B368
d.drv_type=40000000
d.busWidth=1
Total card size=F400000
SDCARDD2S+,cStoragePlatformType=FF
Then the device just sits there with Cal Checksum on the screen. I get no response from NTTY or device until I restart.
I read on another thread that it might be locked. I also read that there may be a password to get into another level of access. See http://mobilitytoday.com/forum/showthread.php?t=15217 for details.
I have to get this cracked as I want to restore my good any network ROM onto a network specific device.
Anyone got any other ideas?
Matt4444 said:
Then the device just sits there with Cal Checksum on the screen. I get no response from NTTY or device until I restart.
Click to expand...
Click to collapse
The checksum calculation is a long process, try to wait longer...
Anyway your SD should have been written... have you tried to read it?
EDIT: Does it show ******** or direct checksum calculation? (how long is the process)
I let it run for over an hour the first time but that was with a 1GB SD card and I understand that it would take longer with 1GB.
I haven't actually looked to see if there is anything on the card(s) as I just assumed it hadn't worked. Other threads say that the device gives you progress or at least some response from the MTTY to say it was done.
I have to shoot to a meeting but will try again when I get back...
b0ris747 said:
Just press ACTION+POWER+reset with stylus and hold this combinaison for a few seconds, you'll see a screen without backlight (so you must be under bright light to see it) going into bootloader mode.
Put your device on the cradle (which I suspect you had connected it to your PC)
using mtty, connect to your USB Port (or Serial port if serial cradle)
type "password BOOTLOADER" and use "h" as an help command.
Now you can dump a ROM from Bootloader
The command should be sth like "r2sd"
Read the manual of this command "h r2sd full" and use it to dump your ROM on the SDCard
Now you can dump the raw ROM image from SD Card Reader using ntrw.exe
EDIT: going to bootloader mode seem to hard reset your device, backup FIRST!
Click to expand...
Click to collapse
yes, nice but does not work in 69xx's bootloader. while executing d2s command the device loops on "Calculating checksum" point and nothing happens even after an hour of waiting .. :-(
That is the same problem I am having. I read on another thread that dmc874 (who seems to know what he is talking about) thought it was related to the device being locked. See http://mobilitytoday.com/forum/showthread.php?p=68783
I am now trying to research the locking to see if there is anything I can do to unlock it... anyone else got any ideas?
Does anybody tried to upload a .NBA image through bootloader?
Someone to know the command for sending through bootloader to certain address locations?
What about pdocread or such tools?
Method to dump ROM from wizard using pdocread: http://www.spv-developers.com/forum/showthread.php?t=2888
Does Anyone Know Where I Can Get A English Rom For My IPAQ hw6955 Whitch Is Currently In French Please Help..
b0ris747 said:
Just press ACTION+POWER+reset with stylus and hold this combinaison for a few seconds, you'll see a screen without backlight (so you must be under bright light to see it) going into bootloader mode.
Put your device on the cradle (which I suspect you had connected it to your PC)
using mtty, connect to your USB Port (or Serial port if serial cradle)
type "password BOOTLOADER" and use "h" as an help command.
Now you can dump a ROM from Bootloader
The command should be sth like "r2sd"
Read the manual of this command "h r2sd full" and use it to dump your ROM on the SDCard
Now you can dump the raw ROM image from SD Card Reader using ntrw.exe
EDIT: going to bootloader mode seem to hard reset your device, backup FIRST!
Click to expand...
Click to collapse
..hey great info on how to get to bootloader,, i have a tmobile wing and need to get to the boot loader screen please tell me specifically wat i have to do.. also wat do u mean by action button???????
mafioso617 said:
..hey great info on how to get to bootloader,, i have a tmobile wing and need to get to the boot loader screen please tell me specifically wat i have to do.. also wat do u mean by action button???????
Click to expand...
Click to collapse
Action button = push directional pad in no direction
Anyway it won't work...
Maybe a method based on this:
http://forum.xda-developers.com/showthread.php?p=1480853
I'm looking for a french dump!
I'm also looking for a crazy volunteer to test an english ROM (It probably won't update, but I'd like to see the resut and I've got no such device Magician, Beetles and Prophet only...)
b0ris747....
My pda Hp 6915..normal english 1.21UK rom. hp sites german rom download. Hp6915 update error. error code display vG.30.
Hard reset end soft reset not fonksionert.
Help me.
Not: not english speak sory.
http://forum.xda-developers.com/showthread.php?t=309357
good! Can it works for eten x500?
nixo79 said:
Does anybody tried to upload a .NBA image through bootloader?
Someone to know the command for sending through bootloader to certain address locations?
Click to expand...
Click to collapse
This is information for the BEETLES, Should not be too different than the 6900, If anyone could backup a 6900 series radio, and upload it, alot of us would be grateful.
Source: http://blogs.unbolt.net/index.php/brinley/2007/07/31/ipaq_6515_dead_gsm_after_failed_firmware
Extract of my RadioROM
I extracted from start address of 60000000 with a length of 800000 what I think is my radio rom and this can be downloaded at
http://www.bold.net.au/~behave/radioROM.zip
I came up with this address from experimentation and addresses from other XDAs and extracted with the following command
USB>d2s 60000000 800000
SD:Waiting for card insert.........
CMD3 for SD, it's OK, ready to get RCA from response.
SDetected one card
SD:ready for transfer OK
pc->drive.total_lba=1EB400
pc->drive.num_heads=0
pc->drive.sec_p_track=0
pc->drive.num_cylinders=0
pc->drive.block_size=200
pc->drive.features=0
pc->drive.RCA=CFAD
pc->drive.drv_type=40000000
pc->drive.securedAreaSize=0
pc->drive.securityDrv=0
pc->drive.busWidth=1
pc->drive.erasedSize=0
Total card size=3D680000
SDCARDD2S+,cStoragePlatformType=FF
********************************
Store image to SD/MMC card successful.
Anything higher and the dump fails.
USB>d2s 60000000 800001
SD:Waiting for card insert.........
CMD3 for SD, it's OK, ready to get RCA from response.
SDetected one card
SD:ready for transfer OK
pc->drive.total_lba=1EB400
pc->drive.num_heads=0
pc->drive.sec_p_track=0
pc->drive.num_cylinders=0
pc->drive.block_size=200
pc->drive.features=0
pc->drive.RCA=CFAD
pc->drive.drv_type=40000000
pc->drive.securedAreaSize=0
pc->drive.securityDrv=0
pc->drive.busWidth=1
pc->drive.erasedSize=0
Total card size=3D680000
********************************Read radio flash is fail!
The size of the uncompressed ROM is around 1gig because I only have 1gig sd cards to dump the ROM on.
You will probably need a 1gig or larger SD card, dim92 tried writing to a smaller card and the IPAQ doesn’t recognize it but you are welcome to give it a try on smaller cards as most of the image are 0s anyway.
Once you have written the image on to an sd card (use any of the bigrom guides using ntrw), pop it into the IPAQ and enter boot loader mode (power + joystick + reset). It should show up with “Download Sections: 1 press power to start".
Press power button and it should show “Updating radio". Let it finish and if it completed with no errors, power up to see if the mobile phone works. If it still does not work, try running the beetles radio patch now. If this too does not work, try running the LATEST rom from HP.
Useful utilities
iPAQDisk
http://www.xs4all.nl/~itsme
HOWTO: Change serial number and model number for HP IPAQ 6515
HP IPAQ 6515 Bootloader password
Exploring HP IPAQ 6515e bootloader
Nazeroth said:
I dont know much, i know nothing indeeed, however i found somewhere a pack of files for the Wizard that were supposed to work for the sable, however they didnt, but there is this particular file, that when ran in the sable made appear a folder called "2" with an icon of a storage card and which rpely the contents of the root of the device (but for itself i mean no 2 folder inside the 2 folder lol)
I dont know if it is of some use but i definitevely want to perform a corporate install of windows in my sable and kill all that HP crap that comes in bundled
Click to expand...
Click to collapse
Hi buddy,thanks for your attachment.
But I gotta tell ya this doesn't work in hp6915,coz all the ROM in the internet do not have ExtRom.nbf,so nobody's device had flashed the Extended Rom in device...then the Unlock tool will not work in this.
Anyway,thank you
Brose

XDA tools problem

hy there,
when i was updating a qtek1010 to wm2003SE rom, that was cooked in romkitchen, the upgrade stoped at 99%.
now i can only get into the bootloader.
bootloader version : 5.15
i've searched, and now i'm trying to upgrade from SD MMC, when i'm using OSImageTool.exe , i open the nk.nbf, destination SD MMC, then it displays this error, (NK.nbf:incorrect filesize(33554463), file should be exactly 32505888 bytes. error opening input file)
What should I do???
Thanks
Download an other ROM. THE NK.nbf-Fiel you have is the WM2003SE ROM. This file can not be written through XDA-Tools.
Download anoteher WM2003 or PPC2002 ROM, flash your device via SD-Card and the run the exe File of the WM2003SE-ROM.....
Stefan
thanks so much, it worked
but now, when i put the sdd in the qtek1010, on the bootloader nothing apears.. only :
WALLABY
Bootloader
V5.15
GSM OK
and when i press action button it displays a diagnostics list like "ram, display, touch etc..."
what am i doing wrong?
what can i do?
i've putted the sdd card in a HP photosmart to copy the .nb1 file.. is this wrong?
thanks,
Luis Martins Portugal
Looks like the ROM isn´t written correct to the card.
Otherwise it will show directly in bootloader that you can install the new ROM.
I´m nearly sure the HP Photosmart causes this problem. Do you have access to another SD-Card writer?
Stefan
ok, i'll buy a card reader and try again
thanks Stefan
i'll post here the results.
gretz
Just to ensure. You have copied the ROM using XDA Tools to the SD Card, or?
Normal paste & copy does not work......
Stefan

Stuck on bootloader menu after error upgrading ROM

Help,
Is there a way to get the OS and boot img for my o2 XDA to put on my SD card so i can recover it?
I'm stuck on the boot-loader screen (version 5.22) i can not use active sync as it comes up as unrecognized device, im at my wits end, i just want to get my phone working again. is there any place i can get the O2 ROM file from? or anything that can be done, or do i have a useless brick now?
i tried upgrading with the developers ROM using the auto install, it got to the "it will take 5 mins to upgrade" screen then active sync lost connection, there was nothing showing in the progress bar, when i tried to restart, active sync could not connect. now im stuck with the boot-loader menu after a soft reset.
Sorry for the double post,
Right sorted the problem out, got a cooked ROM from a different site as no link i clicked on here was still active.
I found out that if you Format the SD card to Fat32 when in bootloader it doesn't recognize the ROM, so a format to just FAT under windows XP sorted it out, and now I'm back up and running again, though now i cant get my phone unlocked to Vodafone as the XDAunlock returns "error getting code" message. here are my Device info
Rom version 3.17.03
Radio version 4.21.X1
Protcal version 32S54
problem resolved by updating the Radio stack to 6.24 (placing the files onto the device and upgrading from there) once that had done, i had no signal, so downgraded it back to 4.21 and now I'm fully functional
Where did you get the ROM?
I have a similar problem with an XDA which failed whilst being flashed via active sync and now will not start apart from via bootloader. Where did you get the ROM that you mention please?
Thanks
Geezer
use this ROM from http://www.romkitchen.de/ choose one that u will use to cook, PC2002 or WM2003/SE, (WM2003SE cannot use SD Card, only can use activesyn) then downgrade bootloader from v5.22 to v5.15,
using MMC (flash SD) continue to special rom 1.2, Go to the bootloader utilities. Hit Contacts button and you'll get the boot loader option stuff. If the bootloader utilities you get to right away takes you to a menu with things like Boot+CE-->SD then you don't have to worry about hitting the contacts button. You only need Contacts button if when you get to the bootloader screen you see nothing more than some nice colors, the bootloader version and "GSM OK" message.
Take the Boot+CE-->SD option to back everything up. This will take a few minutes.
Once it's done pull the SD out ofthe ppcpe and stick it into your SD card reader. Bring up XDArit and chose your removeable device.
If you have more than one MMC slot select the different ones until you get one that says 'Wallaby' in the hex codes at the bottom of the XDArit screen. You'll be writing out two files, the first is the NB0 file (which is the bootloader) and the second is the NB1 file (which is the OS or ROM). Name these something like original.nb0 and 1.
Wipe the SD card (format FAT). Stick the SD card back into the pda and soft reset, then cradle it.
Go to a DOS prompt and CD to where you put 'pnewbootflash_40116.exe.' Type 'pnewbootflash_40116 nbl515.nb0' to write the Wallaby 5.15 boot loader to the device. If when you downloaded the 5.15 bootloader you called it something else (like 'wallaby_boot_loader_V5.15.nb0' you should of course use that name instead!
The output looks like this:
D:\XDAtools\binaries>pnewbootloader_40116 bl515.nb0
Copying D:\XDAtools\binaries\itsutils.dll to WCE:\windows\itsutils.dll
in FindFlashInfoOffset
protection found at 8c0d60f8
result: 00000000 00000000
for the complete, read this web :
http://www.romkitchen.de/
http://www.romkitchen.de/tools/
http://www.romkitchen.de/tools/manual_unlock.htm
*read careffuly and try it, you can read my post, almost similiar problem but i can solve it by read one by one,hehehhe.. never give-up, ok ^_^V
any help with magician rom?
OK I found this thread and this is what I need to do but I don't follow any of this. what is the ROm image and how do I cook? I'm totally lost and My phone is wrecked or bricked as you say???

Categories

Resources