A while back I upgraded my imate PDA2k from WM2003 to WM6 and it was working fine, a bit slow but everything was working
however recently I left the wifi on and left the phone at home and I guess all the battery was drained or something
I couldn't turn the phone on, so I decided to charge the battery and try again
The phone boots, enters windows, comes to the homescreen and then freezes (totally unresponsive... buttons dont work, touchscreen dont work)
So then I tried to downgrade the ROM back to WM2003 by following the wiki but I cant seem to be able to do so.
could anyone help guide me side by side?
Thank you,
Chan
UnholyGod said:
A while back I upgraded my imate PDA2k from WM2003 to WM6 and it was working fine, a bit slow but everything was working
however recently I left the wifi on and left the phone at home and I guess all the battery was drained or something
I couldn't turn the phone on, so I decided to charge the battery and try again
The phone boots, enters windows, comes to the homescreen and then freezes (totally unresponsive... buttons dont work, touchscreen dont work)
So then I tried to downgrade the ROM back to WM2003 by following the wiki but I cant seem to be able to do so.
could anyone help guide me side by side?
Thank you,
Chan
Click to expand...
Click to collapse
You have to put the device in bootloader before up/downgrading. Don't worry if ActiveSync doesn't see it (in fact, you should kill ActiveSync before flashing). Good luck
if you follow the procedures in my thread linked in my signature, you will succeed. it covers the complete down- and upgrade procedure.
Related
I was attempting to upgrade the rom image (to an O2 rom for an O2 device), when the device powered itself off. It hadn't written anything, it just got to the splash screen where it said checking device.
My PC never shut down, just my Exec. I thought it was one of the various power offs that the devices do during rom flashing.
I can do a hard reset, and I get the screen that says press zero or x, but after that I never get anything. even if I plug the device in, I don't even get a charging light.
can anyone help me with where I should begin troubleshooting????
well, I just tried re-updating it, just to see what woudl happen, even though there is no display. I used the WM6 I found, and it made it through the radio stack (screen is now dark, no back lit, but can see X% upgrade completed), so it looks liek its working, just needs to finish the rom. I hope, lol!
well, it made it all the way through the rom update, and asked for a cold boot, but the screen just stays dark, even after the hard reset.
Any ideas anyone???
okay, problem solved! I was able to get the device into bootloader mode, and then ran a flash for WM6.
toast said:
I was attempting to upgrade the rom image (to an O2 rom for an O2 device), when the device powered itself off. It hadn't written anything, it just got to the splash screen where it said checking device.
My PC never shut down, just my Exec. I thought it was one of the various power offs that the devices do during rom flashing.
I can do a hard reset, and I get the screen that says press zero or x, but after that I never get anything. even if I plug the device in, I don't even get a charging light.
can anyone help me with where I should begin troubleshooting????
Click to expand...
Click to collapse
hi toast
i got the same problem with xda exec. i read all your thread but cant find any instuction which you might got. can you please let me know what you have done to solve that issue. cheers
how did you get it through!!
hey, you the got the problem to be solved, please help me too in solving this porblem. I am getting the same problem of that screen scrambleness. Please help through step by step information.
LMAO....help me too...it wont even sync with with the ative sync program...how am i supposed to even begin fixing this problem????
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
I was in the middle of upgrading my version of WM6 and i got unplugged and now it wont resume and the phone is stuck at the loading screen that says "HTC" mobile.htc.com
what the heck do i do? it wont budge.. it wont sync with active sync, it wont resume.. i'm flipping out.
did you try get your phone in the tri color bootloader screen and then running the Hard SPL program again?
god, I'm gonna admit, I have no idea what any of that stuff is. I know the tricolor screen, I dont know what an SPL is.. a friend of mine usually sends me the upgrades for my programs and i just follow his instructions, but as i was loading the new version it got unplugged and when i tried to follow the restore options it wouldnt restore the upgrade.. so I've learned the term is bricking.
Activesync won't reconnect the phone.. it tries, then doesnt recognize the device.. so even if i try to downgrade to 1.04, it wont work because it wont sync with the damn computer.. I hard reset, i soft reset, i got it to the tricolor screen, i tried all the stuff in the hermes upgrade problems thread, but i dont know wtf i'm doing. the file mtty.exe wont work.. it just freezes at whatever screen i happen to get it to, be it the tricolor or the HTC screen.
please, someone help me out.. I apologize in advance for not being as savvy as everyone else, but I need some advice here.
Go the tri colour screen
press both soft buttons (the ones that interact with the screen) and insert the stylus and reset.
from here you can make an hard reset. Whenever my phone hangs (or whatever) I use this way BUT i use the cancel button (X) and the phone simply restarts fine
Did u hard SPL your device?
Costanza said:
press both soft buttons (the ones that interact with the screen) and insert the stylus and reset.
from here you can make an hard reset. Whenever my phone hangs (or whatever) I use this way BUT i use the cancel button (X) and the phone simply restarts fine
Click to expand...
Click to collapse
I hard reset, I soft reset, it freezes either way. The only way the computer recognizes the phone is when I get the tricolor screen but active sync wont connect to FINISH loading the upgrade.
antonlim1999 said:
Did u hard SPL your device?
Click to expand...
Click to collapse
I cant because it wont connect to activesync to install anything else.. i cant dongrade, upgrade, nothing! i cant get to version 1.04 from the 1.06 im running because activesync wont recognize my phone.
I think antonlim1999 mean, did you hard-spl before you even upgrade to wm06 or not ?
sg10 said:
I think antonlim1999 mean, did you hard-spl before you even upgrade to wm06 or not ?
Click to expand...
Click to collapse
I already had wm6, i was just getting a better version that didnt have as many bugs.. I began loading it, it got to 45%, then the cat knocked the cable out and it got messed up.. I dont believe it was hard-spl beforehand.. im gonna go with no.
Could you try to SPL in the tri colour mode (as you have contact between the unit and the PC)?
Link below has all (almost) info
http://wiki.xda-developers.com/index.php?pagename=HTC_Hermes
A warning to those with an aversion to reading
This is a warning to those who don't really know what they're doing. Upgrading a ROM on a WinMo device is something that should only be done when you know what you're doing.
Hope your device can upgrade well, but please, take the time to actually read the wiki and forum before upgrading again, for your own wallets sake.
hiddenconcepts said:
I was in the middle of upgrading my version of WM6 and i got unplugged and now it wont resume and the phone is stuck at the loading screen that says "HTC" mobile.htc.com
what the heck do i do? it wont budge.. it wont sync with active sync, it wont resume.. i'm flipping out.
Click to expand...
Click to collapse
You are not even in the right forum, you'll get better help elsewhere.
Start reading here: http://forum.xda-developers.com/showthread.php?t=286755
Hard SPL thread: http://forum.xda-developers.com/showthread.php?t=296722
philjohn said:
This is a warning to those who don't really know what they're doing. Upgrading a ROM on a WinMo device is something that should only be done when you know what you're doing.
Hope your device can upgrade well, but please, take the time to actually read the wiki and forum before upgrading again, for your own wallets sake.
Click to expand...
Click to collapse
thanks, but I've upgraded before to other versions without a problem and I know that pulling the plug out is a bad idea.. the cat jumped up and ripped it out causing it to brick.
What all the smart arses on this site should be telling you is that you don't need activesync to run the upgrade - it will work just fine from the tri-colour screen.
First off, when you get your phone into the tri-colour screen, check the SPL version - if it isn't 2.10 olipro, the first thing you need to do is read the vanx guide's (link in my sig) and get hard SPL 2.10 olipro on there ASAP - this will prevent you from bricking your phone.
If it is already 2.10 olipro, then breathe a sigh of relief as everthing is OK - just put it into the tri-colour screen and run the upgrade again - it should start again with out a problem.
Cheers,
Smiffy.
Sorry if the post has already been mentioned in another forum before.
I have an O2 XDA Orbit and i'm looking to put Fracoons Artermis rom on it http://forum.xda-developers.com/show...o♦.
I'm pretty new to flashing phones and PDA's but i'm quite experienced with a PC so shouldnt need to much help!
I was wondering what steps I should ensure to take to make sure that I dont turn it into a brick, I could do with a complete guide! I've also been told that i'll need to run the Artermus USPL program after connecting the phone. But any help and advice would be a great help. Is there anyway to backup the phone in the state it is at present if or if it doesnt go wrong?
Thankyou for the help and sorry again i've this has already been asked by someone else! Will really appreciated it!
There is no assurance that the process will not make your device a brick. But it happens only on a rare case. Many 1000s of users have upgraded without problems however a few has got their devices a brick.
There is no point taking a backup as the new ROM will give you different files. Anyway, to make sure you don't end up with a bricked device:
-Charge your device fully
-Run USPL
-The process should complete successfully!
-Upgrade ROM.
-Never disconnect your Pocket PC or turn of your PC when the upgrade is going on.
-If your stuck anywhere, don't try to do anything stupid but come here and post.
-Your device should be fine
-Even if some devices get bricked during one of the upgrade process, there is still a high chance of bringing your device back to good working condition with the help of a Factory ROM and so don't worry and go ahead.
Regards,
Carty..
that's my biggest concern so far... my XDA II SHOULD be able to run WM5 but i'm very concerned that i could turn it into a brick... the reason for this is: the XDA is the only phone i have at the moment.
If it bricks, then i'm literally screwed... i have the HimaUpgrade File that does not need an ID, and as i'm pretty fluent with English, i see no problem in using an English ROM.
The Wiki is a good place to start... but i still don't know if i REALLY need active sync to be running or not, since i cannot understand what good that would do if the device is in Bootloader Mode anyway.
Reason for this is that sometimes i read "Active Sync should be on" and sometimes i read the complete opposite... it's freaking me out.
Device should be Synchronized always for the best choice. All un-official ROMs will require this. However, factory ROMs can be flashed directly from Bootloader mode.
That is why I said when you think you screwed the process of upgrading, mostly your device will be stuck at bootloader or you can access bootloader screen and only a factory rom can go from here.
PS: I wont guarantee if the above will be true on all conditions.
Regards,
Carty..
I flash all my ROMs in bootloader mode, including my own, so it's not restricted to the official ROMs. But you need a working ROM to get it back alive.
I'd recommend using a laptop for flashing or use a USV. If some guys cut your power your computer would crash right in the middle of the flashing process - won't happen on a laptop with a working battery.
This is what I want to know. How do I flash in bootloader mode?
okay, i did it this way: first of all you need a rom to flash your device with, but i guess that should be clear
To put your device into Bootloader Mode you have to press the On/Off Button, the Directional Pad AND the reset button (mostly at the lower left corner) simultaneously.
Release the Reset Button first after about a second, and then the other two Buttons.
Your Device should say "Serial" on its Screen... by that time you can put your Device in the Cradle or connect it via a USB Datacable to your PC.
Also: connect the Cable/Cradle directly to your PC, not to a hub as that could cause Problems during the Flashing Process.
Now you can start the Flash-Program, wait approximately 30 Minutes (if you are just flashing the ROM and nothing else) and follow the Instructions that came with your ROM WORD FOR WORD as these instructions are working for most people.
I'm not saying that flashing is without Problems though... when i flashed my XDA II with WM2005 yesterday, i was not able to send/receive Textmessages (SMS), so i had to reflash the device again with the last ROM released by O2, which sucks.
hi all,
i'm hoping someone might have some suggestions to fix my x50v. i have been given an x50v that wont turn on, so far ive
- checked the backup batt holds charge
- lock switch works
- battery cover switch works
- reflashed wm2003se rom
- reflashed wm5 A02 bootloader and rom
the reflashes will complete sucessfully but when i do the hard reset after flashing the rom it is still dead. the only key combination that will show anything on the screen is wifi+power+reset and the bootloader comes up.
does anyone have any suggestions? I've searched the forum for days looking for things to try, seems like a common problem.
bump... anyone???
Not sure if you've still got the same problem but it sounds identical to what happened to me after flashing WM5 A02. I'd successfully gone from WM2003 > WM5 A01 but after A02 it just wouldn't boot. I could still get to the bootloader but no amount of flashing got it working.
Eventually I tried flashing LennySh WM6.1 A09 just see if it would work, it didn't. Still same problem. So I gave it up for dead. Then a few weeks later, I came back to it, the charge had gone completely. Plugged it in, let it charge a bit, switched it on and bam, it began the boot process and worked just fine.
I've no idea why, I was shocked, maybe something to do with the battery dying completely. But I'd done multiple hard resets, recovery attempts all with no luck. So why it just started working I don't know. But if you've left it in a cupboard somewhere and given up on it, it might just be worth giving another try!