Related
Ouch!!!!!
I tried the radio update, during which I got a communication error.
Now I have a brick!
The blue i-mate screen comes up. the rom info is displayed (radio still says 1.03.00) and there it is stuck.
Now what? Hard reset? (how do you hard reset from that point?)
Bootloader? How is that done?
Please help. I am off to go under my blanket to cry.
Just retry the radio update again and again, put it in bootloader
How do I get bootloader? I tried the camera+power+reset combination but it still does the same thing, no bootloader menu.
Or do I have to have the bootloader files in the storage card first?
Can I also get help on how to extract the files. I don't know where the installer is putting the binaries, and at this point I would very much prefer not guessing what files to put where.
bootloader
try this
light + power + reset
Re: bootloader
dherrero said:
try this
light + power + reset
Click to expand...
Click to collapse
That did something. Now I have a white screen (no light) that says "Serial" on top and "v 0. 60" at the bottom.
I have the following files in the sd:
EnterBL.exe
GetServiceData.exe
radio_.nbf
RUU.conf
RUU.dll
UI.dll
But it is not doing anything.
yes, now it's in bootloader. Now connect the jasjar to your pc and execute the upgrade. If it doesnt work kill the activesync processes (WCESMgr.exe and wcescomm.exe) and repeat the upgrade
OK! That seemed to work, but it still gets stuck at the bootup screen (except now it shows the new radio version).
The update program asks for a hard reset, but others in another thread mentioned they did not need a hard reset after this update.
Is there something else I can try before trying a hard reset?
I just spent a week to set the damned thing to the way I like, and don't want to do all that again.
I didnt hard reset. try resetting 2 or 3 times. If it doesnt work then hard reset
I took out the battery. Will wait a bit and try resetting a few times.
How long does it take for yours to show some activity after the rom versions are displayed?
It does take longer for this device to bootup, but I wonder if the new rom made a difference there.
Usually the blue boot screen disappears in 30 seconds. But when i installed pocket plus many times it keeped freezed and a had to reset 3 o 4 times.
Is your case?
dherrero said:
Usually the blue boot screen disappears in 30 seconds. But when i installed pocket plus many times it keeped freezed and a had to reset 3 o 4 times.
Click to expand...
Click to collapse
Hmm. I don't have pocket plus, but I have the spb gprs monitor (or whatever it is called) at the startup. Maybe that's causing a problem with the new radio.
I will reset 3 - 4 more times and then do a hard reset.
If it does not come back from hard reset, the bawling you hear all the way out there is me.
he he . I ve spb gprs monitor too and it works fine.
good luck :wink:
When perform soft reset, wait 1 or 2 minutes before doing other soft reset
OK, now it is time to cry.
It is not coming back from hard reset either.
It is officially a brick. Any more ideas? Please?
thy to make the update again. Perhaps this revives it
if a radio update is available, maybe a rom update is around the corner.
Or just a recovery standard rom
Does exits an official rom to reinstall jasjar rom?
I am doing the radio update again to see if that helps.
I will probably need to contact imate support for a recovery rom image I suppose. I suppose I should tell them what I was doing.
But this update was from imate, right, so I didn't do anything "wrong".
If someone has a rom, please let me know.
So, I am getting the runaround.
iMate says they don't have the rom to send me and I should send the device to the service center. The service center says they don't work on JasJars there.
So I am stuck with a paperweight?
Try Hard reset....
Just try to Hard reset .. most probably one of your already installed S/W causes the machine to hangup.... once you clear after Hard reset it should boot up.. worse while before sending it back to imate and being blamed for loading un-official and not released update... Unfortunatly there no "shipped rom" yet. you best choice to recover the paper weight is to hard reset and perhaps load S/W again. ... I have been trying to dump the rom for days with no success .. once one of us can do it we are releaseed.
Good luck
Re: Try Hard reset....
Dubi said:
Just try to Hard reset .. Good luck
Click to expand...
Click to collapse
Already did the hard reset (many times) and nothing changed.
The problem started after the radio update, and the hard reset does not reset that update (I see the new version on startup).
Unless there is a harder reset I can do, I suppose I will have to wait for the rom.
makes a grown man cry...
i was installing new rom on my device.when it was 12%, the computer got locked and i had to reset.Now,my baby did not reflash again.i tried again but himaupragadeutility gave : communication problem. what can i do now? can anyone help me? so a few people know this device, the others even do not know what pda is. what i can do?????????????????????????????
keep on doing a hard reset until you reach bootloader mode. from there try upgrading again. were you upgrading to 2003se or wm2005?
i was installing the rom from 02 web site
i was installing the rom from the 02 web site.i had tried but it did not open boatloader.what i can i do?
anything showing on your xda screen? if it's blank then you have to continue doing hard resets. a buddy of mine had the same problem and he was able to bring it back to bootloader mode after 10 or so hard resets.
if something is showing on the screen (like "usb version...something") then this is already bootloader mode. what you do is put the xda back on the cradle but don't expect activesync to recognize it. just put it back on the cradle and then rerun the upgrade.
hope it works.
rob
there is only o2 logo on the device,i tried hard reset but it did not open boatloader
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
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
Hello,
been trying to upgrade the software on my XDA Exec yesterday, but it halted during the upgrade procedure and just hangs, then I get an error connection box.
Have tried to put it in bootloader mode, and now the device just has an unlit screen, with 'Serial' at the top and 'v1.00' at the bottom. I try again to re-install the ROM software, but the same thing happens again.
Can anybody please help with any suggestions as to how I can overcome this. In addition, is there any particular software or program I need to run to get things back working again.
Your help is much appreciated.
Tim.
Remove any memory cards and your SIM, make sure you untick USB connection in AS, try to flash again. If doesn't work - MTTY, followed by a ROM flash, if no joy - factory ROM.
Unlit screen with 'Serial' on the top and bootloader version on the bottom - you are in bootloader mode. The 'Serial' will change to 'USB' when you connect your device.
Hey there,
thanks for the prompt reply.
Not sure what MTTY is, but I have tried again and getting nothing.
Would obtaining the original software make any difference? If the ROM update I obtained from here didn't work, does the device recognise original manufacturer software? Also, where can I get this, as O2 no longer support this device.
Thanks,
Tim.