Database Develop

Returning the device to factor settings?

I'm having problems running the ROM upgrade by iMate. I keep getting Error 101 connection error, and I had grown to assume this was a problem relating to running from Virtual PC on a Mac rather than a real PC.
Today I at last managed to get access to a PC running Windows XP, activesync 3.7.1, and got exactly the same problem. I tried it several times.
I'm beginning to wonder if any of my past failed attempts on my mac have done something to the phone that is preventing it from being controlled properly by the ROM upgrade software?
Is there anything more than a hard reset to take the device back to factory settings?
Please - if anyone can help me get this sorted I'd be really grateful. The device is just too unreliable in it's current state, and I just cannot manage to get the ROM upgrade working. It's just unbelievably frustrating!

A hard reset will take the device to the last rom upgrade.
Now in your case this could be the failed rom upgrade which you did over the mac. You would have to look at the device info to check that.
If I was you I would do a rom upgrade of a PC and not off a mac, not that I have anything agaist macs (apart from ...) Its just that I know it works of a pc.

I tried a ROM upgrade from a PC this morning and it didn't work. It kept reseting the device, then said Error 101 connection error (even though it was connnecting fine to Activesync 3.7.1).
I've made a little progress since then. I've pressed power-reset-record to put it into the 'bootloader'? and this allows the installer to go one step further and says installing the radio rom (but never gets beyond 0%). I now get the error 114.
Now that I've got this far, I will have another go with a PC on Monday and see if that makes any difference.
I've just bought the SE K700i which I hope will be a little more reliable. I really just want to get the PDA2K upgraded so it's in a fit state to sell, and perhaps I might even consider keeping it if the ROM makes a radical difference to reliability. It's so nice to go back to just using iSync with the K700i without go-between software and Virtual PC and all that hassle. My plan is to use the K700i until something comes along that catches my attention (I'm still not convinced by the Treo 650 or P910, and I wont forget my experience of Pocket PC for a while!).

If I may add my experience on similar situation, I got a device which was upgraded using a wrong ROM file, and now it ended up with no radio and no operator ID :shock: ... and can't accept "standard" ROM upgrade ... I managed to be able to upgrade the ROM or Ext ROM individually by using null operator ID ... but when it comes to Radio upgrade it doesn't start at all giving failure.

Biso007
So what is the story if you let the device drain down and then take out the battery. Would a Normal offical update not work then.
I have yet to read anything about were on the device the Opid is coded in the hardware. What I know is that the ndf have the opcode in the header and this is checked against the getdevicedata.
I have had check for the opcode in regedit with no luck. (this I some what expected as I did not feel that it is part of the OS).
anybody have a better understanding on that issue?

when I run getdevicedata.exe I get nothing except "PH20B" ... so I used NULL opid to upgrade ROM and Ext ROM ... but this trick didn't work with the Radio part ... more over, I tried the trick of draining the battery down ... it worked only once and the radio is back (I don't know how!!) however, with the last reset after the upgrade the Radio is gone again!!
My suggestion so far is that the Radio part is there but it's inactive due to a problem with the charging circute ... and since the Radio is the 1st stage of the upgrade, it holds the whole process failed.
maybe someone with solid experience with the device design itself can shed more light on this issue.

Hum!
Well what I know about the radio is that it is Lang independent, which means what ever check is run on the upgrade it does not look for the lan code.
Further it must check against the radio type as this is part of the config file that is in the upgrade.
I know that a hardreset will load what ever file is around (so it must be stored in the orignal format on the device, then loaded on hardreset). This seems not to be true for the EXTrom as this seems to be extracted as files on the device (thus you can flush it).
So we have a hardcored opid somewere on the device that now shows zero for you. What was the shipped version of it. Have you tried a ship.exe from your original device without using the xda-tools.
Can you tried a radio only upgrade and used your shipped opid in the fix.bat (maybe after a battery drain again)
Seems a shame to have a paper wheight and not a phone.

Crossing my fingers, but now it worked!! :lol:
The only additional action I took this time is to take the battery out and close the bottome notch which I believe has something to do with the backup battery.
When the device restarted, the Radio part is back with the original version, IMEI and call durations which confirms my idea that the Radio part was always there but blocked by a power charging issue.
Update [27/2/2005 6:40 pm GMT +2]:
I checked the devicedata.txt file and it has nothing except "PH20B" ... this means for me that this device will never accept any official ROM upgrade in the future ... and doing a hard reset is a potential risk to loose the Radio again :?

Problems Updating ROM

Hello everyone,
I have problems updating my SPV M3000. I've been tryin' it for a month now but it just won't happen. Every Rom i download i get the same problem: I just follow the steps of the wizard. But when the installation begins, my device's screen flickers and then it looks like it starts to glow. At the same time my activesync connection drops. The PC gives the [ERROR 260] this makes sense because i lost the connection. Then i have to soft reset my phone. I have Sim and CID Unlocked the phone.
My current version is 1.3.1.13.
Can somebody please help me.
thnx,
Dennis

have you tried changing your use cable? Seems like it's the source of the trouble...

dbleliev said:
Hello everyone,
I have problems updating my SPV M3000. I've been tryin' it for a month now but it just won't happen. Every Rom i download i get the same problem: I just follow the steps of the wizard. But when the installation begins, my device's screen flickers and then it looks like it starts to glow. At the same time my activesync connection drops. The PC gives the [ERROR 260] this makes sense because i lost the connection. Then i have to soft reset my phone. I have Sim and CID Unlocked the phone.
My current version is 1.3.1.13.
Can somebody please help me.
thnx,
Dennis
Click to expand...
Click to collapse
Have you tried flashing an "official" 2.xx rom?
--M

I did all of that... but still no succes.... Anybody have other solutions??
Thnx

Did you ever get your issue resolved?
I've got the same problem and I've tested my MDA with two seperate USB sync cables. Both sync with ActiveSync and actually transfer data with no issues, but I get the 260 error EVERY time.
Does anyone know if there is a MS service that needs to be running that maybe we're missing? I thought all of mine were, but might not be.
Any updated info would be WONDERFUL.

Read this, at the bottom of the file are the error-codes and try to use another USB-port (preffering at the BACK! of your PC)
ftp://xda:[email protected]/Wizard/Roms/ROM/Update Utility Readme.rtf

nabibakhur said:
Did you ever get your issue resolved?
I've got the same problem and I've tested my MDA with two seperate USB sync cables. Both sync with ActiveSync and actually transfer data with no issues, but I get the 260 error EVERY time.
Does anyone know if there is a MS service that needs to be running that maybe we're missing? I thought all of mine were, but might not be.
Any updated info would be WONDERFUL.
Click to expand...
Click to collapse
Maybe try to use activesync 2,5 beta.

Actually, I have the most recent ActiveSync beta and all. And that nice ftp link doesn't work, which I've noticed seems to be the case most of the time.
Can I download that file elsewhere?
I've actually plugged the USB cable in every USB port I have to test that theory and still no-go.
I'm currently on the phone with T-Mobile PDA Tech Support ( BLECH! KILL ME NOW! )
If I get a solution I'll post it and a walkthrough on how to fix it.
Ok, so, just got off the phone with the T-Mobile PDA Tech Support people and here's the lowdown...
It's the phone itself. Somehow my phone is bugged, go figure. Sorry to break the news to the guy who started this thread, but hey, I'm getting a free T-Mobile Dash out of it

ROM upgrade issues...

So, I've unlocked my T-Mobile MDA G3 phone both CID and otherwise using loki. I've tried the T-Mobile update off their own site, and here is what happens. I suspect I need a different data cable, but I might be wrong there, so I figured I'd bring the issue to you all because you are the gurus of all gurus...type peoples.
So, here's what goes on. I download the software. I sync my MDA and my notebook. I ensure both machines are on and set to stay on. I check the connection and all is good. Heck, I've even backed up my MDA system using one of those backup utilities for Smartphones available online for trial download(which worked great, btw). So I run the software and click next and check everything it says the check and then it begins. This is where my problem begins and the goodness ends...
The MDA shuts off and just sits there. I don't touch it for fear of what might happen by being impatient, but every time, no matter which ROM I've tried to use for update purposes, the notebook pops up saying that it encountered a "communications error". It doesn't brick the phone, thank God. It simply just requires removal of the battery for 5-10 seconds after disconnecting the USB, then turning it on. It boots fine and all is good, except, no new ROM, same old 1.0.8.something version and bah!
I want to update my ROM and am stuck. I've tried at least 5 DIFFERENT ROMs and loaders and still the same thing.
I'm running the original T-Mobile ROM 1.0.8.something, IPL 1.X, and SPL 1.X. The phone says it's unlocked using the CheckLock program you can download from the forums, or elsewhere, I forget which. I've run the cidunlock with the loki tool multiple times and it finishes no issues.
If anyone has ANY ideas or thoughts, or even if they've run into this I'd like to know.
I'm pretty sure my phone right now won't do the whole A2DP via bluetooth bit, and that's what I'm REALLY wanting. I just got those Motorola HT820's and am anxious to play around with them more.
Anywho. You all rock and I've only been here like a day, but your information, walkthroughs, and just general geekiness(oh yeah, I work for the Geek Squad and we ALL use either the Verizon or Sprint version of the MDA, heh heh) have been most appreciated!
-----------
Originally posted under xda-developers > Wizard (Oops? )

Stuck after ROM flash:error 206

I decided to reflash my wizard after it continually getting slower and slower after a year. I haven't done it in awhile. It is already unlocked. I flashed the 1.05 rom and it was working. I was going to go up in steps ending with the touch rom. I flashed the wrong rom evidently and now am downgraded to 1.01 on spl/ipl and os 2.26.10.2. The wizard won't activate Activesync and I can't get any communication. I tried rebooting the pc and the wizard multiple times. Still nothing. Need something quick to fix this. Everytime I tried to launch a rom flash I get an error 206.

digitalmayhem said:
I decided to reflash my wizard after it continually getting slower and slower after a year. I haven't done it in awhile. It is already unlocked. I flashed the 1.05 rom and it was working. I was going to go up in steps ending with the touch rom. I flashed the wrong rom evidently and now am downgraded to 1.01 on spl/ipl and os 2.26.10.2. The wizard won't activate Activesync and I can't get any communication. I tried rebooting the pc and the wizard multiple times. Still nothing. Need something quick to fix this. Everytime I tried to launch a rom flash I get an error 206.
Click to expand...
Click to collapse
If it was already CID unlocked,there was no need to downgrade again 1.05,once CID unlocked will remain unlocked forever,unless you intentionally don't flash back the locking code back on to it.
Now try to get into Bootloaders (multicolor screen) hook up the phone with pc via usb cable and check small usb appear at the bottom of the bootloaders,if it appears then download the official stock rom and flash to recover back to the default status,then download the WST 4.2.2 tool and run the 'CID Action' button to verify the CID lock/unlock status of the phone.if its still CID unlocked then upgrade to any wm6 rom of your choice,otherwise perform the unlocking method again.If the usb doesn't appear,then you have a connectivity problem,check the usb cable or the mini usb port of the phone is faulty.Assuming you are doing on winXP.

"and check small usb appear at the bottom of the bootloaders..."
I don't understand what your talking about when you say bootloader. The bootloader is the ROM installation program is it not. How do you check an icon in that? If you mean system trays on the PC or PDA, no USB icon shows. I got no radio or sync services working. The OS is corrupted and operates extremely slow. I can't get any kind of communication between the PDA and PC. Not even through windows explorer (running XP). It's not the cable, I just used it to downgrade to 1.05 and it was working fine. It wasn't until I tried to upgrade to back up, and selected the wrong ROM off my USB storage, that it flashed the wrong ROM and caused all this. Mostly because I hate trying to remember what the longs string of digits mean on each ROM. Especially after I haven't looked at all the files and haven't done a flash in a year.
So no communication. That's the issue.

So does anyone else have any info? As I stated, I can't get any communication between the MDA and the PC. So I don't know how I can flash a stable ROM.

I repeat again,Get the phone in Bootloaders mode (multicolor screen) by pressing and keep holding down the camera button and at the same time either 'Soft Reset' or 'Power On' the phone,but keep holding down the camera button,till phone boots up in Bootloaders mode(multicolor screen),hook up the phone with pc via usb cable and check if small usb appears "At the bottom of the Bootloaders Screen" and not in the system tray of the pc. If it appears then follow the advise I gave you in my above post,but if doesn't appear then you have a connectivity problem.

digitalmayhem said:
"and check small usb appear at the bottom of the bootloaders..."
I don't understand what your talking about when you say bootloader.
Click to expand...
Click to collapse
The Wiki as all the (basic) info to get you started.

It doesn't work
I can get into Bootloaders mode with usb at the bottom. BUT, I can't get any connection to ActiveSync, any of the ROM update utilities and no radio network connections. That was the specific thing I'm telling you. If the Desktop and the PDA won't talk to each other, what am I gonna do? It's not the cable either. The Wizard Tool will not pick it up either when I used it to try to get device info. If your going suggest any kind of ROM or software off the forum, please specify exact version and title so I don't have to go through 100+ pages doing a search to find a specific piece of software off a vague title such as "stock ROM". You may know what it means because your always on the forum. When someone hasn't been back here in awhile they aren't going to remember some arbitrary string of numbers and letters indicating a certain ROM that they haven't used for a year. Too many of you "regulars" get all pissy about things when someone asks a question. If someone keeps asking the same questions, it's because the forum is NOT laid out in an easily searchable fashion unless you have specific search criteria for things such as CUSTOM_RUU_Wizard_1050412_WWE_10111210_WWE instead of "stock ROM".

Have you read the Wiki?
http://wiki.xda-developers.com/index.php?pagename=Wizard Windows Mobile 6 for newbies
Or other posts?
You'd know by now that in bootloader mode ActiveSync or any other tool (that uses ActiveSync) can't communicate with the phone but that it's possible to upgrade a ROM using the official upgrade utilities.
Have you tried making a search and getting hundreds of undesired and repeated posts which makes you lose days searching for a specific thing?
If you'd been here as long as many of us you'd also be tired of people asking same questions. I was once a fresh member and i would always 'waste' my time than others'.
Also the forum search feature has been enhanced by using Google's search engine instead of internal.

There is simply no way I can express my deep and sincere gratitude for the information available in this forum. Let me explain and I think you may understand why.
Several days ago my wife and I received a couple of HTC 8125's from Ebay. Being a tinkerer I wanted to see what I could do so I upgraded mine to Mobile 6 with Touch-Flo.
The wife was skeptical and waited to see how it worked out. Of course she eventually decided to go for the Bling and handed me hers to upgrade as well.
As soon as the upgrade started on hers the pda went bootscreen and locked up. Sooooo I'm sweating bullets and searching the forums as fast as I can go before she finds out. Then I find this thread and the last post... Don't need Activesync to update as long as the device pops up a little usb on the screen when you plug up... I flashed the 8125 upgrade and *Bang*! Back in business. Continued the upgrade and all is well. The wife is now walking around with her "Bling" and happy and I am off the hook!
Thanks for the GREAT FORUM!

Rowdyone said:
There is simply no way I can express my deep and sincere gratitude for the information available in this forum. Let me explain and I think you may understand why.
Several days ago my wife and I received a couple of HTC 8125's from Ebay. Being a tinkerer I wanted to see what I could do so I upgraded mine to Mobile 6 with Touch-Flo.
The wife was skeptical and waited to see how it worked out. Of course she eventually decided to go for the Bling and handed me hers to upgrade as well.
As soon as the upgrade started on hers the pda went bootscreen and locked up. Sooooo I'm sweating bullets and searching the forums as fast as I can go before she finds out. Then I find this thread and the last post... Don't need Activesync to update as long as the device pops up a little usb on the screen when you plug up... I flashed the 8125 upgrade and *Bang*! Back in business. Continued the upgrade and all is well. The wife is now walking around with her "Bling" and happy and I am off the hook!
Thanks for the GREAT FORUM!
Click to expand...
Click to collapse
Thankz !
We all highly appreciate it,glad you got it working .Thats what this Forum is sooo famous for "Help & Care"

no four colored boot screen?

Hi guys..
I'm using O2 XDA IIs, and I'm trying to upgrade to WM 6.5.
I've downloaded the ROM and other misc applications to upgrade, and also read the walkthrough in the XDAdevelopers Wiki page. But I find my device have no four colored boot screen but instead an O2 image with some color information as such :
Code:
R : 1.02.00
G : 1337.32
B : 1.31.00 WWE
in the bottom right of my screen. I also can't see the four colored screen with options to format storage which is one of the point mentioned in the upgrade section.
That's why I've been hesitating to upgrade it since I have this phone, because I can't follow the upgrade walkthrough completely which might caused my phone to brick.
Anyone can help?
Thanks

the four colour boot screen is a bug/feature of any cooked rom, meaning any wm5 and higher rom, you can download here. since you are still using the stock rom it is normal to have a carrier's boot screen. it will go away once you upgraded your device.
since the wiki is quite outdated, you should follow the tutorial link in my signature. it will provide you with the newest step by step instructions, that i wrote with a lot of user feedback, to make sure, people would understand it correctly, at some points, the wiki instructions are mistakable.
also, while i really appreciate being cautious (since it is always easier to guide in before, than to repair afterwards), you shouldn't worry about bricking the device. if you follow the tutorial word by word, there should be no risk of failing to upgrade. and even if an upgrade fails, you can always start over again.

Just read all the tutorial firstto have some sense of it, and the follow it while doingthe upgrade. Make sure that your battery is at least 50% charged and you'll be good to go.
Good luck and if you have questions, please post them in the q&a thread...
Good luck

Chef_Tony said:
the four colour boot screen is a bug/feature of any cooked rom, meaning any wm5 and higher rom, you can download here. since you are still using the stock rom it is normal to have a carrier's boot screen. it will go away once you upgraded your device.
since the wiki is quite outdated, you should follow the tutorial link in my signature. it will provide you with the newest step by step instructions, that i wrote with a lot of user feedback, to make sure, people would understand it correctly, at some points, the wiki instructions are mistakable.
also, while i really appreciate being cautious (since it is always easier to guide in before, than to repair afterwards), you shouldn't worry about bricking the device. if you follow the tutorial word by word, there should be no risk of failing to upgrade. and even if an upgrade fails, you can always start over again.
Click to expand...
Click to collapse
thanks for the help chef..
I've visited the link on your signature, and it really helps. unfortunately, I'm using Vista in my notebook. since there's no guide for that in your thread, should I just try the steps for Vista user mentioned in the wiki? or should I just find another computer with windows XP on it? I already have the Windows Mobile Device Center installed on my notebook by the way.
also, there are some other things I'd like to know. I've tried putting my device into bootloader mode by pressing power + record button and then reset. but there's nothing changed, just looks like a normal soft reset. is it really supposed to looks like that? or there's something wrong with me or my device?
and when I do the hard reset, just like I've mentioned above, there's no menu appears. is the menu also part of bug in the cooked ROM and not supposed to appear in the carrier's boot screen?
thanks for the answer.
egzthunder1 said:
Just read all the tutorial firstto have some sense of it, and the follow it while doingthe upgrade. Make sure that your battery is at least 50% charged and you'll be good to go.
Good luck and if you have questions, please post them in the q&a thread...
Good luck
Click to expand...
Click to collapse
yes, I've always searched for more and more informations before doing something this risky. I'll visit the Q&A thread after posting this reply. thanks for the support.
---
btw, sorry if my English is mixed up. it's not my primary language, so please endure with my bad English.

for the bootloader mode, you might have to press and hold the power+record button a little longer while resetting and only release them, when the display is grey and shows SERIAL on top and v2.0x (where x is between 5 and 7) at the bottom.
the mentioned hard reset method is also only suitable for windows mobile 5 and higher. for windows mobile 2003 a hard reset is done by simply pressing power+reset (also maybe holding the power button for a second). there is no hard reset necessary before the upgrade, but afterwards, and then, using a higher rom, you will have the 4 coloured screen with the menu. there is really no way to make a dry run on this.
as a first time upgrader it would be much easier for you to use a windows xp machine. it simply works because activesync provides all the necessary drivers, for syncing (of course), and also for flashing, while on vista/7 you have to replace the driver with a custom one depending on your version (x86 or x64). those drivers are not digitally signed, which, especially on x64 machines means more trouble to go through. in d-two's thread, you will find a how-to for vista/7 flashing if you find no other way. i think that is just an option for experienced windows and blueangel users, that are already running a cooked rom and want to change to another one. with a first time upgrade you have so much stuff to read through, so many more steps to actually prepare the device for the first time upgrade... xp would be your better choice.

alphadeeto said:
thanks for the help chef..
I've visited the link on your signature, and it really helps. unfortunately, I'm using Vista in my notebook. since there's no guide for that in your thread, should I just try the steps for Vista user mentioned in the wiki? or should I just find another computer with windows XP on it? I already have the Windows Mobile Device Center installed on my notebook by the way.
also, there are some other things I'd like to know. I've tried putting my device into bootloader mode by pressing power + record button and then reset. but there's nothing changed, just looks like a normal soft reset. is it really supposed to looks like that? or there's something wrong with me or my device?
and when I do the hard reset, just like I've mentioned above, there's no menu appears. is the menu also part of bug in the cooked ROM and not supposed to appear in the carrier's boot screen?
Click to expand...
Click to collapse
There is a set of instructions for Vista in the wiki (the ones you are referring to). They seem to work well afaik, but I agree with Chef... do it from a XP computer to avoid any issues.
Bootloader (the easiest way) is to hold power +record and then put the stylus in the hole. Doing the three of them at the same time might not get you anywhere. For the hard reset (WM5 and up), you can simply use the stylus and as soon as you get the stylus out, hold the two side buttons (camera/WMP and record) and you'll be able to see the options mentioned by Chef.
Good luck!

thanks for all the help, both of you..
I finally upgraded my BA to WM 6.5, and it turns to be a success. I'm using the steps from wiki to upgrade in vista since it's hard to find someone who's using XP in my neighborhood.
Nothing's wrong until I tried to send SMS messages. I can't either send or receive any SMS's. The messages are delivered to me but it doesn't appear in inbox, only in today screen notification. Fortunately, the other function works really well, the phone, GPRS, bluetooth, ad even the wi-fi.
I'll upload the screenshots later when I'm using my notebook since the internet fee using GPRS in my country is really expensive.
Can I reflash using another ROM? or is there something I can do to fix the problem?
oh, and another thing : my USB active sync can't work. Should I reinstall the WMDC or what?
thanks for the support guys.

alphadeeto said:
thanks for all the help, both of you..
I finally upgraded my BA to WM 6.5, and it turns to be a success. I'm using the steps from wiki to upgrade in vista since it's hard to find someone who's using XP in my neighborhood.
Nothing's wrong until I tried to send SMS messages. I can't either send or receive any SMS's. The messages are delivered to me but it doesn't appear in inbox, only in today screen notification. Fortunately, the other function works really well, the phone, GPRS, bluetooth, ad even the wi-fi.
I'll upload the screenshots later when I'm using my notebook since the internet fee using GPRS in my country is really expensive.
Can I reflash using another ROM? or is there something I can do to fix the problem?
oh, and another thing : my USB active sync can't work. Should I reinstall the WMDC or what?
thanks for the support guys.
Click to expand...
Click to collapse
Most of those issues sound like issues present in my rom. Is that the one you flashed? If so, it would be wise to flash to something else... I never really got that rom working the way I wanted... Go with 28232 or one of d-two's releases.

egzthunder1 said:
Most of those issues sound like issues present in my rom. Is that the one you flashed? If so, it would be wise to flash to something else... I never really got that rom working the way I wanted... Go with 28232 or one of d-two's releases.
Click to expand...
Click to collapse
excellent!
I've flashed with the latest ROM from Sun Dream. and it works superb!
there are lots of changes from my previous ROM. the today's screen, start menu, and the buttons position (the start button is on the top of the screen previously, and now it's in the bottom. )
well, the only problem I encounter is that I can't sync with WMDC on my Vista.

alphadeeto said:
excellent!
I've flashed with the latest ROM from Sun Dream. and it works superb!
there are lots of changes from my previous ROM. the today's screen, start menu, and the buttons position (the start button is on the top of the screen previously, and now it's in the bottom. )
well, the only problem I encounter is that I can't sync with WMDC on my Vista.
Click to expand...
Click to collapse
You have to use a newer driver which if I am not mistaken comes with WMDC 6.1