i can't figure out how to put the bootloader 5.17 fix on the sd card using xdarit1, do i only put the diagnostics?? or do i also put the bootloader 5.17?? if so where can i get the bootloader file?? guys please help, i really wanna have my phone back :/ and oh, while trying to put only the diagnostics xdarit1 crashes and doesn't write anything, i'm using XP sp2 and some gembird all in 1 card reader to do that..
GUYS, MY XDA IS WOOOOOOOOOOORKING!!!!!!!!!!!!!!!! Thank You for your FAQs and everything!!!!!!!!!!!!!!!
It's so easy and helpful here.... ;-)
Stefan
Where can I get this FAQ ?
bad-dog said:
Where can I get this FAQ ?
Click to expand...
Click to collapse
What are you searching for exatcly? Most of the questions are answered here in the forum. You can also take a look at the Wallaby section in Wiki.....
Stefan
Wiki ? can I've a URL ?
I tried to upgrade my Qtek 1010 from 2002 to 2003 although I can't start it now. The windows stops on the loading screen.
I tried to use a few things like XDAarit and stuff, but I did it with MMC.
I didn't get any reply to my MMC question in the forum ( Post ). So I guess that is not the problem, that guy here said he used a FAQ I wanted to know where it is, maybe it might help me out.
http://wiki.xda-developers.com/index.php?pagename=Wallaby
Never tried flashing with a MMC. Used everytime a SD-Card....
So I'm not sure, but I'm nearly sure that's your Problem....
So try getting a (at least) 64 MB SD-Card and try it again....
Stefan
Thanks dude, problem solved.
I'm pretty sure it wasn't the MMC problem but the Xdarit and my card reader. After taking a different card reader from my fathers PC shop and taking an SD card with a new xdarit. It all worked out just fine, Although I still got one issue, I'm trying to put 2003 and still it never works, I tried all kind of versions, only 2002 works great. Can you give me any hint ?
Don´t know where the problem is. Have you tried XDATools and the OSImageTool?
Stefan
I didn't but that shouldn't be the issue, because I can install 2002 and upgrade with active sync. which pretty much the same thing, in both ways it doesn't work. only pocket pc 2002 works fine.
bad-dog said:
I didn't but that shouldn't be the issue, because I can install 2002 and upgrade with active sync. which pretty much the same thing, in both ways it doesn't work. only pocket pc 2002 works fine.
Click to expand...
Click to collapse
I remember an other guy, who had the same problem. PPC2002 ROMs went fine, but all WM2003 didn't work. But i don't remeber if, and how he solved the problem. Maybe you take a search in the forum and contact him personally....
Stefan
Sure, thanks a lot ! I hope I'll find that topic
Related
Sorry folks but I have already posted this and don't know how to delete the previous post. after I reviewed the previous post I don't think I made myself clear enough. Please accept my apologies. But would appreciate help on this.
I have read the majority of the info on XDAtools on the forum and installed I believe correctly. I currently run on Win98SE. I have installed Jeff summers version of XDA tools. And though I think I understand what I am doing I am not totally convinced. Before I embark on cooking roms and upgrading etc I would like to be able to do the following:
1: Dump my current rom from my device to my PC I can do this using
XDAtools OSImage. But have noticed that I can only appear to dump
this as NB1(windows CE(*.nb1) type files if I try to call this NBF I get
the following errors:
”error opening C:\program files\xdatools\bootloader_v5_15.nb0ea for
reading. the system cannot find the file specified”
”error opening source bootloader from C:\program
files\xdatools\bootloader_v5_15.nb0ea. error opening target device”
Is it possible to dump my ROM to a file called ‘xxxx.NBF’? or must I stick with *.NB1? this is not a problem as long as the NB1 file can be reloaded.
2: When I try to upgrade my ROM by using OSImage tool and selecting
source as:
‘C:\PROGRAM FILES\XDATOOLS\BINARIES\ATT160204.NB1’
Select destination as ‘device memory (via Programme A) ‘
When attempting to load an ‘NB1’ ROM from my PC to my device memory
(via Programme A) I always get the following message:
”Programme A not found - run with --register error opening target device”
I originally ran the ProgrammeA with ‘--register’ when first installed and tried numerous times since. Can someone please help as I am sure it is something simple I am missing. I only want to be able to use XDAtools to dump and restore ROMs.
I have tried searching for a solution but to no avail. Any help appreciated.
Thanks in advance John.
May you tell your current ROM version and device type?
Some ROMs do not accept the EXE or the XDAtools with NBF files upgrading methods. You may have to use the SD card flashing in this case.
Thanks Bis
Thank you Biso007 I am currently running A.30.09.ENG and my device type is an XDA1. But I believe the problem is associated with XDAtools ProgrammeA as it cannot find the specified files. Though I have followed all instructions for definition. There is probably something simple I am missing. You see I only want to be able to use XDAtools to dump and restore Roms without the need for SD/MMC cards.
Thanks John
Try downloading the XDATools from Jeff Summers site, it has all the missing bits, including the required batch file :
http://cuba.calyx.nl/~jsummers/XDA/XDAtools-Jeff.exe
That's from the sticky XDATools thread, probably read through there and you will find most questions answered if you continue to have problems.
Remember though that the SD card method is the preferred option, and if you burn any T-Mobile ROM's the SD card is *required* to reverse that.
Re: Thanks Bis
jdoherty76 said:
Thank you Biso007 I am currently running A.30.09.ENG and my device type is an XDA1. But I believe the problem is associated with XDAtools ProgrammeA as it cannot find the specified files.
Click to expand...
Click to collapse
XDAtools cannot work with WM 2003.
and you no need to backup A.30.09.ENG (ATT USA version WM2003), you can get it from online!
cgigate said:
XDAtools cannot work with WM 2003.
Click to expand...
Click to collapse
is that confirmed ??
Biso007 said:
cgigate said:
XDAtools cannot work with WM 2003.
Click to expand...
Click to collapse
is that confirmed ??
Click to expand...
Click to collapse
Yes, it for sure!
XDAtools only works with Pocket PC 2002 or some test version WM2003.(<4.0.11)
It cannot work with WM2003 official release (AT&T A.30 or T-mobile).
Thats weird, I am positive I used xdatools to program my sd card through reader writer after downloading the official WM2003 upgrade, in fact I must have used that method because I had to seperate out the radio stack and program just the ce rom, I have no other tools to do this.
XDAtools only works with Pocket PC 2002 or some test version WM2003.(<4.0.11)
Click to expand...
Click to collapse
I think you'll find that it only does *not* work with T-Mobile WM2003 ROMs. That's only because they lock up their OS to try and prevent us from changing ROMs. I don't think that's the case with any other manufacturer. I also think it doesn't make any difference whether it's WM2003 or WM2002, it solely depends on whether the manufacturer locks the OS.
Thank you cgigate & ebswift re XDAtools/WM2003
Thank you Cgigate and ebswift maybe this is why I am encountering problems with my download and restore of my ROM. I inadvertently choose a WM2003 AT&T rom to practice with. Maybe I should have chosen a PPC 2002 ROM to test??
I thought I had a problem with XDAtools and that I did not have all the correct links/files in place. Maybe I should dump my ROM and try restoring a PPC2002 and then re try my test. Thanks again guys.
i used xda tools with the AT&T WM2003 rom on my uk o2 xda with no problem. I wanted to keep my old radio stack as it was working fine and just used the os upgrade file, via SD card.
I would recommend updating activesync to 3.7 if you are doing it via the XDA cradle.
maltloaf
Did you use XDAtools to copy direct to device
Thank you Maltloaf, when you upgraded your rom did you use XDAtools directly from PC to device or copy the file onto your SD/MMC card and use the bootloader program to load ?? If so maybe you can answer the problem I am encountering. Thanks john
i have flashed twice (had to go back to 2002 for a short while)
both times using the SD card/bootloader method and I transferred the file onto the card using xdatools in the xda/cradle
Thank you Maltloaf
Thank you Maltloaf this seems to be clearer now, but in the context of upgrading etc XDAtools is only being used to copy the file from source to SD/MMC card. I was under the impression that XDAtools did not require the use of SD/MMC card. But maybe it's a matter of finding out what works for you. John
well xdatools should be able to flash directly to the xda as far as i know but it's always the safest way to do it sdcard style
Thanks to all
My thanks to all you helped with my recent questions. Thanks John
Since updating to the T-Mobile Rom for my XDA, nearly everythiung has gone wrong.
And when I tried to downgrade it.... Nothing happens.
I used to use a modified Program A to upload it to my phone but it continues to say that the USB devide gets remotely stopped. the only thing that I can think is that my phone is cancelling the upgrade/downgrade.
I have also tried using a copy of the XDATools program to try and:
Upload another Rom.
Copy the rom to an SD card so I can use the bootloader method.
Change the Bootloader so I can use the SD card method.
None of there are working.
Help :-(
I really want to go back to the ATT rom, it might have the annoying thing with the sound but at least it doesn't mess up as much, doesn't format my SD/MMC cards and lets the alarms actually work for me.
if i'm not wrong, it seems you upgraded using the TMO exe file which updated both ROM & RSU.
check ur boot loader version, if it's 5.22 or higher, i think you need to dowgrade to 5.15 ... use the exe file that comes with the XDAtools in the binaries directory .. its name is fixbootloader.exe .. it should update ur boot loader to 5.15 by which you can use XDAtools or the SD method.
Tried that. I do have XDA tools on my machine and used that program but my CDA still has the bootleader of 5.22
And both of my machines don't like trying to update my XDA :-(
This Rom is the most annoying one I have tried mainly becaise now I can't go back to even my original one that I backed from the XDA when I got it.
Am I stuck with this ROM?
omg, i think i am having the same problem. In my case, since ive installed the new rom, i cannot sync with activesync, well very slow anyway. Activesync on my pc stops responding for a while and suddenly it says connected. However when i then run the executable created by the kitchen, it just flashes a command line window for a second.
When I try XDA-toolz with an nbf file, i get the following message:
ERROR: GetConnectionType - An existing connection was forcibly closed by the rem
ote host.
error getting connectiontype
Click to expand...
Click to collapse
Please someone help, because i am really stuck now.
I checked, my bootloader is 5.14, so that shouldnt be the problem, perhaps i need to reinstall activesync, or perhaps lumpistefans kitchen cooks up bad roms. :?:
Nothing wrong with any kitchen ROMs so far ... when ActiveSynce can't recognize the XDA then it's either a PC problem which uninstall/reinstall will solve it ... or it's a wrong RSU update.
The best option so far in case it's a wrong RSU is to copy the proper RSU upgrade (4 files) to the SD card ... insert the SD card into the XDA and copy those 4 files to the \windows\startup directory ... then soft rest.
If the RSU flash works fine the ActiveSync will recognize the XDA again then you can preform a new ROM update
Note: RSU flashing is risky ... do this action on your own responsibility!!
Biso007 said:
Nothing wrong with any kitchen ROMs so far ... when ActiveSynce can't recognize the XDA then it's either a PC problem which uninstall/reinstall will solve it ... or it's a wrong RSU update.
The best option so far in case it's a wrong RSU is to copy the proper RSU upgrade (4 files) to the SD card ... insert the SD card into the XDA and copy those 4 files to the \windows\startup directory ... then soft rest.
If the RSU flash works fine the ActiveSync will recognize the XDA again then you can preform a new ROM update
Note: RSU flashing is risky ... do this action on your own responsibility!!
Click to expand...
Click to collapse
I dont understand how i can have a wrong rsu? I didnt update it , as far as i know , i just updated the pda part. I only saw programme A.
Activesync does recognise my xda, because i can synchronize and explore my device. It does however take a long time before activesync sees the device after its connected. It also stops responding when its connecting, for a few minutes. I tried reinstalling activesync, this didnt help.
prowling said:
ActiveSync does recognise my XDA, because i can synchronize and explore my device. It does however take a long time before ActiveSync sees the device after its connected. It also stops responding when its connecting, for a few minutes. I tried reinstalling ActiveSync, this didnt help.
Click to expand...
Click to collapse
If there is something wrong with the RSU it will defeinitly slow the USB performance, not neceassary by wrong RSU flashing ... otherwise, check the pins of your cradle or the 22-pin connector of the XDA ... maybe one or more pins are bent or weared.
Tried upgrading the radiop stack and although the reception is slightly better... It still won't let me upload,
and its a new cable too :-(
Oh well looks like I am stuck with it.
Another way to upgrade firmware
Are there other ways to upgrade the bootloader from SD card from within the device or even to upgrade the OS from within the phone itself?
You know... as a last alternative?
You can use SD reader/writer from the PC using XDAtools ... once the .nbf file is on the SD card, use the normal SD flashing method.
Or you can use another XDA device from a friend to copy the file to your SD card
I am having the same problem. I have TMO 4.01.16 and since I installed I can't down/upgrade my ROM through EXE or XDA tools, it says my device isn't connected, but I can still connect with Active Sync and all that jazz
ha ha
I can fix all your problems!
How?
Finally got it to work, Although it was a little bit of effort to do so.
I went back to the kitchen and downloaded a NB1 cooked rom with the "B" Signature. Then I basically ran the TMobile Setup again...
Once the setup files were on my computer I overwrote their .NB1 file with the one I just cooked.
But.... I forgot to change the file for the Radio Stack.
The machine worked except for the phone and as something is still stopping me. *it was my first reboot* It wouldn't let me use a new radio stack.
Ended up that i kept on going in to the bootloader and eventually turned my radio off altoghether before trying an update.
Now I am back to a decent rom... (Cooked and modded version of the ATT Wireless rom) and I am almost really happy.
Now to figure out how to stop the annoying sounds starting off really low.
But til then... I'm 90% happy
Thespus2002 said:
How?
Click to expand...
Click to collapse
Use the Sd Method flashing!!
Tmobile roms won't let you upgrade from the usb, here's the link and it will guide you how to flash your device from the SD good luck
http://forum.xda-developers.com/viewtopic.php?t=3274
The way I described.. I had to use the USB method.
my current bootloader (6.22) will not allow me to boot from an SD card.
And XDATools will not allow me to downgrade it... Yet
on ur PC at \xdatools\binaries run this command: pnewbootloader.exe bootloader_5_15.nb0
Wish it was that easy. The phone still appears to be locked in the rom so I can't update the Bootloader. I keep getting a message that says.
Unable to flash in to offset, cannotg disable bootloader write protect.
Help pleas,e
My Wallaby is dead after trying upgrade rom, but in my wallaby is not responding bootloader.
I trying put softreset and pw an nonthink.
I can not start mda
I can not start bootloadet
I can not connect to activesync
Is my MDA really dead ?
How to vitalize
Please help me...
How vitalize this Wallaby ?
Search under wallaby and look for ROMS or rom kitchen and build yourself a new rom.
ghost0815 said:
Search under wallaby and look for ROMS or rom kitchen and build yourself a new rom.
Click to expand...
Click to collapse
I know, how kitching rom for my wallaby, bud I can´t connect to my pda with activesync.
It may be possible to do an SD Card reinstall on the wallaby though, they tend to be pretty robust and hard to kill on the whole.
Crash Override said:
It may be possible to do an SD Card reinstall on the wallaby though, they tend to be pretty robust and hard to kill on the whole.
Click to expand...
Click to collapse
¨
I know how to upgrade wallaby from sd card, but I have dead bootloader.
That´s the reason, why i can´t upgrade wallaby from sd card.
I tried to hardreset, softreset, PW+SWreset.........and nothing hapend.
Same case here
As I see, there's no answer to this problem yet.
Yesterday I fell in the same case!
Please, somebody say something hopefully!
Hi there,
I have a MDA Compact III from T-Mobile, but I upgraded it to WM6 from o2 in former times.
Now the USB-Connection is broken (don´t ask me why - I don´t know) and I want to send the Artemis to my provider for repairing or changing (btw loading is working by USB, but Windows Vista, XP etc. wont identified the Artemis - tested on serveral PCs).
Because of the guarantee I have first to downgrade the o2-OS to the original T-Mobile-OS. I´ve tried it by SD-Card, but I doesn´t work.
The bootloader shows IPL 3.04.0001 and SPL 3.04.0000. As I understand it, I have to use first Artemis_USPL, but without a working USB-Connection it wont work.
Can someone help me?
Many thanks in advance.
I have still the same problem. Any ideas yet?
Just an idea.but have you tried to activesync your device thru bluetooth and installing the Artemis uspl and then flashing your rom via SD card?
Edit .
Sorry mate, tested it on my Artemis and doesn't work.
I'm having the same problem here.
When i connect it to my pc it starts charging but there is no connection with the pc
Someone knows a fix?
sammis said:
Just an idea.but have you tried to activesync your device thru bluetooth and installing the Artemis uspl and then flashing your rom via SD card?
Edit .
Sorry mate, tested it on my Artemis and doesn't work.
Click to expand...
Click to collapse
Thanx for Testing...
By the way ,did you try to activesync thru bluetooth?
Yes mate. The Artemis was connected but didn´t synchronize.
And bluetooth can't be used to flash
RikP said:
And bluetooth can't be used to flash
Click to expand...
Click to collapse
No,it can't ,but,what i had in mind was this:
What if you extracted the ruu-signed.nbh from the USPL app renamed it to arteimg.nbh and put it in the root of your sd card which you then put in your Artemis.
Now create a bluetooth activesync connection with your PC "It's a ***** but it can be done" ,run the USPL app and once it reaches the point where the Dos window "Black screen" exits you manually enter bootloader and run the arteimg.nbh.
Do you think it might work?
Edit:
If this works then you will have a CID unlocked Artemis and you'll be able to flash any rom thru the SD card.
With "ruu-signed.nbh" you mean an original t-mobile-rom?
rumms said:
With "ruu-signed.nbh" you mean an original t-mobile-rom?
Click to expand...
Click to collapse
No, i mean the one that is inside the USPL app released by Pof.
sammis said:
No,it can't ,but,what i had in mind was this:
Do you think it might work?
Click to expand...
Click to collapse
Doesn´t work.
Just purchsed the Orange M3100 phone but I cant sync it on my pc. Ive downloaded Windows Mobile Device Center driver for Vista 64bit. It doesnt pick up my phone. Please help, ive googled etc.
Running WM 5.
In settings>connections>usb to pc, uncheck "advanced network functionality". That might work...
Cheers...
also make sure its pluged directly into your pc (one of the ports on the back) not though a usb hub, thats the prob i had syncing my 3100
thanks ultramag69. it seemed to work
now can i use FREE HTC HERMES UNLOCKER v3a by pof using vista?
the instructions talk about active sync and windows xp but no vista
sorry but ive only used this phone for few hours
you can use the sd card method as described in its readme.txt that comes with it
thats the problem I dont have a sdcard yet. Just thought the XP instructions may work using Vista and WMDC.
I believe you need to update to the latest version of WMDC through my reading but you may want to confirm that. If you do a search through the wiki using terms like "vista activesync hermes" you should get a hit as it has been extensively talked about. Also please make sure you check what radio rom you have as unlocking the hermes will downgrade the radio rom to 1.16.00.10. MAKE SURE YOU KNOW WHAT RADIO YOU HAVE SO YOU AN PUT IT BACK...
If you want to use the sd card method (I find it safer than from the pc) then you need an sd card 2 Gb or smaller as though the OS can read a higher card the bootloader (the software in the hermes used to flash) can't. Don't forget to Hard SPL your hermes after you unlock it, I didn't need to do this but you can check by putting a sim from another carrier into your hermes. However, Hard SPL is a MUST. You can get instructions from here - http://forum.xda-developers.com/showthread.php?t=296722
Sd card method on page 116, post 1160. It has all the apps needed to flash both through pc and sd card.
Then you're good to go for flashing a new os.Look into each os on your own, read the post and make up your own mind, DON'T ASK WHICH IS THE BEST..... There is no "best" for everyone, you need to choose on your own. As for the Radio Rom, I would suggest ONLY using the sd card method as if you flash this it the thing that is MOST likely to brick your device if something goes wrong. DON'T INTERRUPT THE FLASH FOR ANYTHING!!!!!
As stated the unlocking will change your radio rom.
Read carefully each step of the guides and don't skip anything and you'll be fine...
Welcome and happy flashing,
Cheers...
hi ultramag69. flashed the phone today and it worked fine. the only problem i have now is when trying to update to wm6 i just get the 4 colours screen and lose sync. same when trying to hard spl 2.1. any ideas?