HI all,
yesterday my Orbit crashed. Whenever i try to turn it on, it gets stuck, and only shows the first 2 lines when loading, and does not show the GSM version and OS version, I tried to do a hard reset, nothing helps, it just keep stucking on the 1st screen with the first 2 red lines.
Anyone any ideas ???
Thanks
Worth a Try
You might just have a go at putting it into bootloader mode and flashing with a new or the same ROM.
I wouldn't like to suggest it would definitely work, but it'd be worth a go.
How do i do that ?
When in doesnt recognize a connection ?
igal said:
When in doesnt recognize a connection ?
Click to expand...
Click to collapse
It may be able to make a connection in bootloader mode. Like I say, it may not work, but have you tried it? Have you got a better idea?
igal instructions how to go into bootloader mode are in the first thread of the forum. You dont need an activesync connection just connect via usb.
As Mark has said above Activesync connection is not required for "connection" Bootloader mode activates a USB connection which allow ROM flashing.
Use an official O2 Rom or similar, which AFAIK does not require USPL'd ?
Check this thread, which succesfully fixed my bricked Orbit, Remember your on your own though, but if it is knackered now it can't get worse....
My instructions use the official German Rom to get it back up and running, as the English version had not been released. Once you get back up and running you can use any of the other cooked ROMS that are about.
http://forum.xda-developers.com/showthread.php?t=312495
DISREGARD the bit about WINRAR, just get an official ROM, stick your handset in bootloader mode and run ROMupdateUtility.exe
Report back on how you get on.....
I went in to..
Bootloader mode. and got the RGB screen with usb connection, but when i try to flash ( both the rom im using now B&B 4.1 and also an official ROM by O2 ), it quits after 3% altough i have a CID unlcoked by imei-check, and i flashed like 10 times before...
any ideas ??
Thanks!
You must use the factory rom specific to your device including language - did you?
Yes i did.
Not working....
Hi Igal,
which rom eaxctly did you try to flash with to rescue your Artemis from the bootloader?
Rgs
Cyber
I used O2's rom
I downloaded the official rom of O2 ( Windows Mobile 6 ). Once it told me "Invalid Vendor" and the other time " Image corrupted " ( I have O2 XDA ORBIT ).
Are you in the uk using a rom from 02 UK?
I had a similar problem like you are having and managed to rescue using the HTC WM5 standard rom.
Im not in the UK, But
The phone is a UK one, and i tried to rescue it with wm6 official rom, Do you think i should try with wm5 ? Where do i get it ?
igal said:
The phone is a UK one, and i tried to rescue it with wm6 official rom, Do you think i should try with wm5 ? Where do i get it ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=318696&highlight=mobile+5
Related
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 have upgraded my QTEK 9000 German version several times with different ROMs, including WWE versions without any problem. Needless to say that I have used the noID tool.
Now I want to install the new version from Jwrightmcps, but I always get the Country ID Error. I even could not install ROMs which I have installed in the past. Always the Error 120.
Any hints?
Regards,
Elmar
How about turning your firewall OFF?
Make sure when you plug-in your Universal, wait a couple of seconds for your computer to recognize the device before running the MaUpgradeNoID Tool.
cktlcmd said:
How about turning your firewall OFF?
Make sure when you plug-in your Universal, wait a couple of seconds for your computer to recognize the device before running the MaUpgradeNoID Tool.
Click to expand...
Click to collapse
Firewall is off (now). But the same behavior.
The device is recognized. The proof is that the screen with the old versions (radio etc.) and the new versions, are displayed correctly. After pressing "Upgrade" Active Sync 4.2 is disconnected, the QTEK is going into boot loader mode (USB v. 1.01) and after a few seconds the beloved Country Code Error appears on the PC.
uninstall active sync 4.2 and install version 4.1. that should fix the problem
ElmarK said:
Firewall is off (now). But the same behavior.
The device is recognized. The proof is that the screen with the old versions (radio etc.) and the new versions, are displayed correctly. After pressing "Upgrade" Active Sync 4.2 is disconnected, the QTEK is going into boot loader mode (USB v. 1.01) and after a few seconds the beloved Country Code Error appears on the PC.
Click to expand...
Click to collapse
I am confused. Aren't you supposed to put your device on boot loader mode first, then plug your Universal, then activate the MaUpgrade Tool. It is only after this that you will see the screen with the old and new versions.
cktlcmd said:
I am confused. Aren't you supposed to put your device on boot loader mode first, then plug your Universal, then activate the MaUpgrade Tool. It is only after this that you will see the screen with the old and new versions.
Click to expand...
Click to collapse
CktlCmd,
thanks for your confusion ;-)
Going manually in the boot loader helped. I havn't done this in the past, because it was not mentioned in the "official" readme.doc of MaUpgradeUt_noID, even it was mentioned in some posts of this forum.
But the disadvantage is that you do not see the version numbers of the current ROMs befor you click on "Upgrade". Correct?
ElmarK said:
CktlCmd,
thanks for your confusion ;-)
But the disadvantage is that you do not see the version numbers of the current ROMs befor you click on "Upgrade". Correct?
Click to expand...
Click to collapse
Correct. Glad you sorted it out.
Sorry I advised wrongly, I assumed you were trying this in bootloader mode.
mistake sry
hello every body
i need a help a got spv m2000 orange german and i want to make english or french ..my rom is
1.40.01.GER
1.40.228 GER
i have traid many times to update it by french rom or WWE rom always givening me country error 120 ...i have traid with many roms nothing work
i have traid with MAupgradeut.zip,,nothing work ...so i need a help please i don't speak german and i don't like it ....helpppppppppppppp
You're in the wrong forum !! Go there : http://forum.xda-developers.com/forumdisplay.php?f=244
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
Hi, hoping someone can help.
Getting the following. Can't get past it. Also what does the Diam100 stand for as I notice others have different.
A tri-colored screen that reads as follows:
Diam100 64M
SPL-1.37.0000
MicroP-Diam (LED) v.11
-----------------------
PSOC-Diam STAGE_PVT v0x30
Upgrade ROM code error
Please try again
Thanks for you help!
1: state the subject in the thread title, that's what it's for
2: search is your best friend; the issue you mention has been discussed in several threads
3: I'd recommend: get into bootloader mode (seems like you can); install hardSPL again, flash again with any ROM supported by hardspl.
4: insert [solved] in front of your thread title.
5: this is NOT a relevant subject for this forum (it's got nothing to do with rom development)
apologies, im new to this (only got the diamond today) and havent been able to use it yet and this forum was the closest thing i could find to getting it working.
Im unable to enter bootloader mode (volume down, reset?)
Also can't get my diamond to connect to pc and keep getting connection errors when trying to install Hard-SPL?
Thanks, your help is appreciated.
The tricolor screen IS bootloader mode.
Just run the HardSPL, then Rom upgrade utility from a rom, and that's it.
IF you got it in this state, you'd probably want to return it (you got warranty?)
Thanks for your help.
Is HardSPL going to install even though ActiveSync isn't recognising the device (ie not connected). When i run it it seems to work and then a grey screen with 0% shows. Then the install program comes back with a 'connection problem' message,i go through all the steps but just keeps happening. I read posts on this earlier today but it seems the install program is fixed and shouldnt do it any more????
...also ive done all the firewall changes to make sure it connects etc etc. Forgive me if im not doing something that has been posted already, but i couldnt find it.
Thanks.
I had the same problem make sure you install the HARD SPL but the unsigned version not the sign version.....it should work them.....
i think there's two issues people are describing here..
1) installing hard spl.. if you get the 0% error, then you need to follow the instructions in the thread and manually run SSPL from your phone and then start the RUU
2) if you keep getting errors while trying to install your rom AFTER installing hard-spl, then you probably are flashing an unsigned ROM on the signed hard-spl.. go to the sticky thread and download a signed version of the ROM you want..
Thanks guys. I dont see how i can do the manual install, as it requires me to copy a file onto the diamond and at this stage i cant even get activesync to connect to it. I dont beleive its a problem with activesync or the pc as ive tried many many things, but rather that the diamond isnt communicating properly.
Also i havent even got to installing the new ROM yet as i cant get past HARDSPL install.
Do you think installing the un-signed HARDSPL version will work? as in will it install when the signed version won't?
all your help is very much appreciated. I cant wait to actually turn my phone on for the first time!
you haven't turned it on yet
is that right?
you have not had it working yet?
or have you tried to update it even before using the phone???????
yeh unfortunatley thats right, yet to turn it on. hopefully will have it up and running shortly...
1) can you confirm exactly what happened to get you stuck in the bootloader screen? (it usually doesn't just happen by itself)
2) Have you tried to soft reset to get your device out of bootloader?
3) are you flashing in win xp or vista?
4) are you connected through a usb hub?
yes, tried soft rest but it just returns to bootloader screen.
using winXP SP3. Not using a USB hub. have tried different ports.
Have tried the signed and unsigned versions of HardSPL.
I keep getting to the 0% grey screen and then the communication error 262.
Maybe i should try and just flash the original ROM? Does anyone know where I can download it from and the HTC e-club doesnt have it? Or is this not the next step???
Thanks!
yeah try the original ROM..
but still i don't understand how you got to this point.. what were you trying to flash when it got stuck in bootloader?
I bought the phone like this.
Do you know where i can get the original ROM from? I tried e-club (both worldwide and SEA) no luck.
Appreciate your help on this.
?? that's quite strange... is there any reason why you're not just returning it for a new set?
try this thread for SEA ROM
I bought it whilst overseas last week in SEA. Im now back in australia and would like to try my best to fix it before going down the long and difficult warranty path.
Do you think its buggered? Or the fact that its in the bootloader screen and giving me this message quite common on failed ROM updates?
Do you think an orginal ROM install will fix it? if so where can i get it from?
Thank you.
well that's what i'm asking..
you got this screen when you pulled it out of the box, or tried to update the ROM and then hung on this screen. also, if you did try an update, was it a SEA update, or australian ROM
i wouldn't say its a common issue.. i also don't think your device is bricked, since its showing bootloader.. diamond is relatively new so i don't really know a lot about getting it out of this state.
trying to load original ROM is a good option.. one thing is for sure, before any further flashes (after you get out of this mess) you want hard-spl on your device.
If flashing original ROM doesn't work, i'd suggest PM'ing walshieau, olipro, or pof as they know a lot more about this type of stuff.. do post your results
Thanks for the link above. i'll give it a go. is it different from the one in the ROM list??
Hi all,
I have a huge problem and I hope you guys can help me. I tried to flash the orbit (german) artemis of my brother. First flashed the uspl and everything worked fine. At the end there came this penguin picture and the screen stayed black/blue. Then I flashed the rom (MossisROMV3.0GER Windows Mobile 6.5).
HOWEVER: Right then the battery of the laptop went down and the pc switched off. Unfortunately we couldnt plug it in, since we didnt have the cable with us. Now after pluging in the pc there were some connection error notices. Since I didnt know how to proceed I removed the battery of the artemis. I thought I should repeat everything from the beginning on. However the phone always got stuck at the blue o2 screen showing the data:
IPL 3.04.0001
SPL 3.04.0000
GSM 02.88.90
OS 3.13.0.0
Softreset and harrest doesnt make any difference. The phone always gets stuck here.
Is the phone bricked?? Why then does it start? Please help me out asap, since the phone is needed. What can I do?
Thanks in advance
brm
first you are NOT CID unlocked (SPL 3.04.0000)
so you can only flash german orbit ROM on the phone to revive it
1. get to bootloader (press and hold the record button and reset the phone using stylus)
you will get the tri colour screen
2. connect the phone via USB to PC (no need to look for activesync/WMDC connection in this case)
3. and run the RUU (official O2 german ROM for O2 Xda Orbit)
BTW i have official o2 UK ROM in my 4shared account
look for the link in my signature
you may try your luck on that
Hi,
thanks for the fast respond. I read the just before some where else and right now I am searching for the original german rom. However cant find it anywere.
Do you think the english one will work too?
best,
brm
sheennick123456 said:
BTW i have official o2 UK ROM in my 4shared account
look for the link in my signature
you may try your luck on that
Click to expand...
Click to collapse
very few chances of that ....
but you can have a go atleast
i might be having an german official ROM not sure though
if i have it i will upload it ASAP
Hi,
thanks sheennick123456. Really kind for your fast responses, Finally I found the original german rom and right now i am flashing it. Afterwards i am gonna flash a new rom and hopefully everything will wirk fine. But thanks again for your kind help.
best,
brm
LOL even i got 1
uploading it now as i type....
it might help someone .....
which rom
Hi again,
after installing a wm 6.5 ger rom i must say i dont like it at all. can you recommend me another one? i think one with htc touchflo would be great, but which one is it?
If i want to flash a new rom, do i first have to flash the original rom before proceeding?
best,
brm