Develop Bugs

DOPOD 900 dead after upgrade

My DOPD - bought in China was running a chinese version of WM5.0 and I wanted to install a english version.
After upgrading my DOPOD 900 with the upgrade : Universal_Upgrade_v1.30.68_radio_1.09.0.zip I have problem.
It is really DEAD. soft reset does nothing and a hard reset only gives the option of "0" and "X" which do nothing.
the USB is no longer recognised and nothing seems to want to communicate with the Dopod. It seems the USB loader program is no longer running on the Dopod.
Has anybody any idea how I can attach to the device an install a new bootloader, or something.

I had the same issue and I have a solution. But, let me tell you my process that got me where you are.
I tried performing the update using the No_ID (or whatever) method and kept getting errors. I rebooted my PC and changed the Operator ID using the HTC64 Extended ROM Tool.
After this, I was able to use the typical installer. The flash went fine and I hard reset as instructed. From that point on, I had your exact problem.
A dead screen. I was able to redo the hard reset after pulling the battery but I would just end up with the dead (blank) screen again. ONCE, I did get it into boot loader mode where I could actually read the screen. But, of course I reset and again had a dead screen.
My solution was to revert back to a true O2 ROM. Even though I couldn't see the screen (still can't), the ROM update is proceeding as I type this. I'm at 44% of the radio ROM installed.
Hope this gives you hope!

Well, good news. I just finished the ROM update and I'm looking at the O2 boot image.
Is there any indication that the QTek ROM looks for the Carrier info to be QTek or it will fail once installed? Just wondering why I had this problem.

ARG! Reflashing with QTek ROM did the same thing. :evil:
Blank screen and all.

check 2 things
uncheck usb from active sync
hardreset after upgrade has been completed
just do the upgrade again and it should come alive again

Thanks and another question
Well thanks for the hope. but I have tried this already with no luck, however after this message I will try again. My biggest problem is that I cant regain communication over the usb.
I would like to know how your system behaved when you plugged in your apparantely dead device. My system just says device un recognised and I cant begin a download with or without active sync.
So I cant get another rom image to download.
regards
Nick

dolebole said:
check 2 things
uncheck usb from active sync
hardreset after upgrade has been completed
just do the upgrade again and it should come alive again
Click to expand...
Click to collapse
This was the first thing I did.
The problem is that I cannot get any communication over the USB.
The device is unrecognised on USB and after starting any ROM download it just timesout after "checking information from device" message .
Ever seen a dead USB interface like this ?
The USB PnP mgr sees the hardware but cannot establish the device type !!
Nick

@mobinick: You and I have the same situation.
I have 2 Universal dead like this. 1 Exec and 1 Jasjar.
Both dead, blank screen, can not enter bootloader, can not connect with PC. PC can not recognize the driver usb of the device.
I opened the phone and found that logically everything is so so. There is no clue about hardware.
So I think: the address of the bootloader with device ID maybe unlucky damaged.
Who can fix this problem pls share us some experience.
Thanksss

ta_mobile said:
@mobinick: You and I have the same situation.
I have 2 Universal dead like this. 1 Exec and 1 Jasjar.
Both dead, blank screen, can not enter bootloader, can not connect with PC. PC can not recognize the driver usb of the device.
I opened the phone and found that logically everything is so so. There is no clue about hardware.
So I think: the address of the bootloader with device ID maybe unlucky damaged.
Who can fix this problem pls share us some experience.
Thanksss
Click to expand...
Click to collapse
Why don't you guys take it to your respective service centres and get it fixed?
Even if you have to pay something, it will certainly be better than these bricks occupying table space.

Have you tried going back to an original O2 ROM? I went to 1.13.139 WWE and all is fine now.

Just to share my experience with you guys here:
I posted my problem way back during the Radio Upgrade from 1.04 to 1.06. My Dopod 900 got stuck on the splashscreen. I couldn't get my device to pass the splashscreen even after upgrading/downgrading the radio ROM back and forth two times.
Finally, I just forced my device into bootloader mode (Backlight+Reset+Power). Even after doing this, the dopod screen was completely blank (no indication of serial/usb letter on the screen). I downloaded the official O2 exec ROM and plug my device (in bootloader mode) back to the USB port. It said unrecognized port on my PC. Despite that, I reflashed my Dopod back with the NoID tool the complete O2 ROM (Radio, Main ROM & The extended). Once completed, my device regained its consciousness.
I managed to flashed back the 1.06 radio after that. And has since been upgraded 4 times (two i-mate, one Orange and the latest QTek ROM) with no problem whatsoever.

I had the exact same problem as you to guys, i tried to update it, and it wouldn't budge...
It constantly, without fail timed out... I tried everything...
As my hope started to wain, i gave it one last shot...
I took out everything, sim and sd and battery, then connect the battery back and from the bootloader menu, connected it to the pc, with usb cable...
Finally it worked!! Like normal, i was able to load any and all rom and radio updates...
Wouldn't work, from the normal working screen (which was working for a while, i later tested this out, and found out ) and also wouldn't work, from the bootloader (power+backlight+reset) with sim+flash in there....
Hope you guys have some luck.. I htink you should, because i was in the exact same boots as you guys...

It worked for me
My O2 Exec did exactly the same thing, and I spent (on and off) 24 hours trying to get the damn thing to go again - wouldnt charge either....
I too finally took out everything, SIM and sd and battery, then connect the battery back and from the bootloader menu (which I only found about from this site), connected it to the pc, with usb cable...
It worked as well - bloody brilliant. I now have the latest 02Exec Upgrade (Version 1.30.162 AKU2 Release) and all is great.
Cant believe that 2 days after logging email with O2 site, they have not responded...
Would almost kiss you guys.....

Solution for getting stuck in bootloader
http://wiki.xda-developers.com/index.php?pagename=Instructions for those stuck on Boot Screen

Need help. Tried to upgrade the ROM.

Hi guys.
Was hoping you could help me out.
I performed a search on the forums and didn't find the answer.
I have an O2 XDAII.
I tried to upgrade the ROM from the O2 site.
The upgrade somehow went south and the only thing I have on the sceen of the device is:
At the top - "Serial"
At the bottom - "v1. 06"
I tried taking out the battery and then putting it in again, but the same things appear on screen as detailed above.
Any suggestions/advice would be gladly appreciated.

I had that.
I plugged back in the USB cable and the message changed from Serial to USB - I then re-ran the ROM upgrade and it all worked OK.
Give it a try and let me know how you got on.

I'm getting the same problem. On my phone (UTStarcomm PPC6700), I have the Serial/USB header, with a V1.00 on the bottom.
When I first attempted the ROM Upgrade, it switched over to the screen. I've tried removing the battery, resetting, and re-launching the ROM upgrade app, but nothing.
Any other ideas???

solutions found?
Anyone know the solution?
larboleda said:
I'm getting the same problem. On my phone (UTStarcomm PPC6700), I have the Serial/USB header, with a V1.00 on the bottom.
When I first attempted the ROM Upgrade, it switched over to the screen. I've tried removing the battery, resetting, and re-launching the ROM upgrade app, but nothing.
Any other ideas???
Click to expand...
Click to collapse

ISTR that when you get to that screen it is after a hard reset.
You should just be able to hook up the USB cable and re-install the rom.
If you are having problems re-installing the rom, what sort of error messages are you getting?
Have you tried installing another ROM?

Serial v1.01
This is all that is written on the grey screen after trying to install ROM. Does anyone know how to proceed? I have an i-mate Jasjar.

It doesn't sound as though the rom is getting installed properly.
Do you get any error messages from the ROM installer?

I did not get any errors while installing. I did upgrade to 1.30.101 some weeks ago, but the phone turned very slow and froze. Therefore I now tried to install 1.30.77. Now the screen is grey and the only text is serial and v1.01. Anyone know how to proceed?

problems updating ROM
I have a Tmobile MDA PRO. I updated the ROM to the newest version, but now my phone only displays a screen with a tmobile logo, and the version information and thats it.
I tried to do a hard reset and still the same thing, I tried to redo the ROM install program, but its says[error message 101] that my phone is on but it cannot connect to it.
I have had my phone for one day and it is virtually useless.
Can someone please tell me how to flash the rom, or which is the best ROM to install for the mda pro/qtek 9000 series?
Help would be much appreciated!!!!!!!!!!

koolaid4star said:
I have a Tmobile MDA PRO. I updated the ROM to the newest version, but now my phone only displays a screen with a tmobile logo, and the version information and thats it.
I tried to do a hard reset and still the same thing, I tried to redo the ROM install program, but its says[error message 101] that my phone is on but it cannot connect to it.
I have had my phone for one day and it is virtually useless.
Can someone please tell me how to flash the rom, or which is the best ROM to install for the mda pro/qtek 9000 series?
Help would be much appreciated!!!!!!!!!!
Click to expand...
Click to collapse
Go and get your MDA PRO into Bootloader Mode: Press backlight + power button and do a reset. You should now see without backlight on top of your screen: serial and on the bottom: v.1.xx
Now connect MDA PRO with the USB datacable and run the ROM Update
again .. hopefully you have 50%+ battery capacity

ive got a wizzard .... my prob is that i installed da rong rom ... and now my usb port is not working ... its not charging neither is it connecting to da usb for active sync ... tell me wat to do ....

Unable to boot up after upgrade ROM to WM6

I follow instruction in http://forum.xda-developers.com/showthread.php?t=313486 but after hardreset.
My p800w is stuck in T-Mobile logo and version number. It can't continue booting up to windows mobile.
Question: How to flash ROM without ActiveSync?
How to recovery my Artemis?
Welcome any advice,
Thanks in advance.

Yea me to, mine is now a brick after that upgrade? No active sync connection possible and all I get now is the blue O2 start screen after the hard reset with the red writing and numbers in the top left hand corner..
Phone is an UK XDA Orbit
IPL 1.25.0001
SPL 1.11.0000
GSM 02.67.90
OS 3.4.0.0
HELP!!!!!!!

yeah, I had the same problem and have created a thread for it already. unfortunately I got no useful replies, and it seems that I am stuck waiting for an official o2 ROM so that I can recover my Orbit.

It seems there is a way to un brick our phones I just need to get my phone bootted into bootlader mode which no one seems to say how to do??
Can anyone help how I can boot my Orbit , like what combo of keys I need to press to boot it into bootloader mode then XP will see it at a driver level apparently Active Sync still won;t but I will be able to run some German ROM update with the ROM file replaced with the other ones and it may come back to life..
Help how can I boot my phoen in bootloader mode???

motomob said:
It seems there is a way to un brick our phones I just need to get my phone bootted into bootlader mode which no one seems to say how to do??
Can anyone help how I can boot my Orbit , like what combo of keys I need to press to boot it into bootloader mode then XP will see it at a driver level apparently Active Sync still won;t but I will be able to run some German ROM update with the ROM file replaced with the other ones and it may come back to life..
Help how can I boot my phoen in bootloader mode???
Click to expand...
Click to collapse
I read in here that you hold the voice button and soft reset.

Decaf said:
I read in here that you hold the voice button and soft reset.
Click to expand...
Click to collapse
Correct and use mtty
Already see in the forum ....

Thanks guys and apologies for the spelling..I ran the Artemis_USPL before I tried upgrading to WM6 and again have been able to run it after with my new brick now with the phone in bootloader mode but still when I try and run the german ROM update a) it will only work with the german file which freezes @ 3%? This seems to be a known problem reading around and b )when I replace it with the smaller ROM file, 54MB the german one is 66MB, I originally tried to use it doesn't read the ROM file or the update utility doesn't want to read it. I reckon I might be able to get it back if I can get one of the ROM update utilities to read a good ROm file and send it to the phone.
I can;t find this MTTY program to sniff the USB port and return the code of if the USPL util wokred as I think that could be key to all of this.
Can anyone post a quick how to here for
1) install MTTY from somewhere
2) what command to run agaist the phoen to see if the USPL util worked and what values I should be looking for
3) another WM6 ROM version (that the update utils can read) download location I can download from to try and send to the phone using the German update util
Not asking for much am I but I desperately need my phone back WM5 or 6 in the next day or so so really can't send it off.
Thanks

Error message I recive at the 3% stage when using the German ROM and english update util.

use the file attach and read that :
http://forum.xda-developers.com/showthread.php?t=285112

Thanks but I'm not that cleud up on what commands I'm meant to be sending. It works in Bootloader mode I ge a response from the phone by send it a command. But even if I get a response telling me what the CID status is its not much help as I think ti shoudl have tekane BEBEs ROM by now as I've got the german ROMUpdateUtility sending that 54,272KB file to the phone but it stops after 3%. What are my options?

motomob said:
But even if I get a response telling me what the CID status is its not much help as I think
Click to expand...
Click to collapse
That's right. On older models MTTY was quite useful, but not on the Artemis. You cannot use it to read the CID status anyway. If you are not sure about the status, run the USPL tool, just to make sure.

I've already re run the USPL ROMUpdateUtility and it completes 100% okay in bootloader mode. But after I hard reset and then try and flash the WM6 BEBE ROM or any ROM German etc back onto it it either fails with the error code I posted up earlier or gets to 3% and fails.
What are my options at this stage? Does anyone have a link to another ROM I can try like the original WM5 O2 ROM or any other WM6 ROm that might work. I'm willing to give them all a try as it's just a useless phone right now and I haven;t sent it off as 1) I need it before the weekend and 2) As I can flash some ROMs with the USPL and others have done this no problem I really feel there must be a solution as I can still falsh the phone.

What can I say RTFM... I did it all right and I didn't have a brick, I missed out one small detail... loading on the ROM with the extended ROM. All now running and it does seem a little faster than WM5.
Thank you to all those that tried to help out. To the others that are still having probs.. Don't try and run the update in the middle of a busy day in the office whilst trying to manage 100 other things meaning you are probably missing out a line like me...
One question though how do I get back my O2 power and storage meters on the today screen back as I liked them and the WiFi seems to have a bug where when it is enabled and you click on the WiFi symbol up the top it only allows you to switch it on, when it is already on.. so you have to open up the COMM manager to switch it off.

So how did you fix it exactly? I have read this thread thoroughly and can't find out what you did!

ERROR[206] occurs while trying to update ROM to WM6
While tring to update ROM to WM6 on O2 XDA Orbit i encounter ERROR[206].
I wanted to attach the screen shot but dont know how to do that, but anyway what i am doing is i attached my pda to my pc via activesync using supplied usb cord. Everything goes well till i reach a screen where it says "You are now ready to update your ROM image...." and once i click next a progress bar apperas and my pda shuts and activesync exit's automatically and my pda tries to restart with RBG band and some text:RUU, IPL 1.25.0001, SPL 1.25.0000 and USB. And thats it after few seconds or a min i get the ERROR[206] and my pda hangs.
I dont know why Activesysn shutsdown ???
Just an additional in i want to tell that without installing activesync i am not able to connect/pair my pda with my pc. So do i need to install the drivers and then try or it doen't matter cause once i install Active sync i can connect the device.
Please help me with this....
Thanks

unable to load bootloader!!!!!!!!!!!!
HELP!!!!!!!!
I have HTC3300, tried to update rom, now its bricked. I tried to start bootloader by pressing the voicebutton and softreset but loads in t-mobile screen and hangs, im unable to start the bootloader.
Is this end of story or are there any other options to get the bootloader to start????
please help

Bootloader
I had a problem with my phone loaded touch flow 4 and cid unlocking, everything was fine then after a while it froze at boot up.
I look put the battery and did a hard reset, put it into bootloadeder mode, reflashed with a t-mobile rom does not need to be cid unlocked to do that.
Once origonal rom was working, cid unlock again, flashed back to touchflow 4.0 - sorted

Where did you got an tmobile rom from can you tell me. Mine is also freezing on booting almost once every day or so after I've upgraded to 4.0

RUUClientDriver.dll error when trying to Flash ROMs to iPaq

EDIT: I found info that claims these updates can't be installed on Vista, and I'm running Vista. I will try again on an XP machine. Can someone confirm/discredit this? Thanks.
Hi all,
I have an iPaq hx2410 and whenever I try flashing ANY ROM (even official HP ROMs that I downloaded from their site), all seems to go well at first, but then my progress bar goes to 0.1%, the unit resets to BL mode with the "USB" on the screen and nothing happens. It never advances past 0.1% and after a minute or two, the Flasher quits with the error about "RUUClientDriver.dll" I've tried all sorts of things, from switching USB ports to resets but nothing... I'll try it on another computer today, but does anyone have any suggestions? I can't even update to the latest wm2003SE ROM, let alone WM5 or 6 because of this problem! Yes, I searched the forum(s) already. Thanks a lot!
-Morris

im getting upset over a hx210 one minute it says bad activesync, then wrong ruuclientdriver.dll file, the ruu software says for the pre-bl mode, the handset says no turned on normally, and yet, no answer from anyone about this,i hope this is the right place.

Hi,
i've same problem !

Help, stuck in bootloader after bad flash

Hello, I cant follow/or understand the guides found here or in
trinityguides to recover my device.
I have successfully flashed severa cocked roms before, however this last one failed and left me in tri-color screen displaying SPL-9.99-CP
What do i need to do, my active sync want connect and give me the green OK.
It say it cant detect my device when i connecs it?
Please help, im not good at this, how can i get the device to be recognized by
active sync?
Any help very much appreciated!

allanredo said:
Hello, I cant follow/or understand the guides found here or in
trinityguides to recover my device.
I have successfully flashed severa cocked roms before, however this last one failed and left me in tri-color screen displaying SPL-9.99-CP
What do i need to do, my active sync want connect and give me the green OK.
It say it cant detect my device when i connecs it?
Please help, im not good at this, how can i get the device to be recognized by
active sync?
Any help very much appreciated!
Click to expand...
Click to collapse
In bootloader mode AS will not recognized the PDA. As I see there is DES crash proof hard-spl on your PDA. Stay in bootloader mode, and try to flash an other rom, or the original offical rom. If does not work here is a useful link:
http://forum.xda-developers.com/showthread.php?t=308691

thanks for your quick reply!
how can i flash without the active sync is connected?
i have tried but the rom update utility says it cant find device and exits
or can it be done withot connection, if so how?
thanks for all input, as i said im not an experienced "flasher".

I don't know why, but after successfull cooked rom update (Schap, Faman, etc..) the last one didn't work and stick to 3-color (I'm under olipro 1.3)
I just made a spl update without any pb (take a look if on your pda screen it shows USB instead of serial) don't care about activsync
Then a radio update (1.40 instead of 1.50).
Shap rom update didn't work anymore (cache issue), so I'd just copied RUU_signed.nbh from SChaps replacing the one into Fman folder, and just working fine...
If it can help you.

Had this kind of problem
Simplest thing is to load rom from SD card (do search on this).
In short get the ROM you want - ROM***.nb file and rename it as TRINIMG.NB put it on the SD card. Launch bootloader and follow instructions. Otherwise check thread VISTA FLASH DISASTER...
Good luck,

Solved!
I reconnected the phone ( it sad USB in the bootloader btw)
Downloaded schaps wm6pro and unzipped, enterd the ruu and flashed, even thoug active sync was inactive.
I didnt have to go any further than this.
Many thanks, now i might dare to try som more roms, done ax3ls and karmba's so far looking forward to test schaps now.

Look in the Trinity Wiki. It describe how to flash from the SD card. this will fix you up.