Related
Phone: EXCA200 (as read on the back) AZERTY keyboard. ActiveSync says is a HTC-S620
Story: My best friend bought this phone in France and some guy tried to be nice and apparently tried to install some games on it. He broke it. She came to me after and said, "if you fix it you can keep it-- but i don't think you can". ( She was using the phone in the US with a US carrier at that time i think it was Cingular)
When I turn on the phone and after the HTC and WinMobile screens the sim error screen appears (the phone has no sim) and 999999 as if the "9" key is stuck. After that, the phone just goes crazy with alarms and if I'm lucky and get over that just 9999999999999 endlessly. I thought at first that it was water damage so i took it apart and found no evidence of water whatsoever.
I found the HTCwiki and tried the hard reset technique (pressing power button while pressing the two open keys) and after 50+ tries i gave up. No luck.
I found a couple good threads that describe how to reflash the phone with RUU_Excalibur_SPL-1.11_UpgradeOnly.exe" and RUU_Excalibur_HTC_GER_1.11.407.2_4.1.13.28_02.63.90_Ship.exe
I get "ERROR 294" INVALID VENDOR ID
Please!! Help!! My experience with smart phones is 2 days with a broken one.
I live in Mexico and smart phones are still something you only see on TV. No one to ask, nowhere to go.
Sincerely,
Salvador333
Where is everyone?
Nobody has any advice?
Nothing?
Do i have to unlock the phone? Can you use a locked phone in France and then in the US without unlocking it?
Should I pay 38 dlls?
salvador333.
Please try one of the two methods explained in the brief post below:
http://mike.temporale.com/archive/2007/01/23/236.aspx
monakh said:
Please try one of the two methods explained in the brief post below:
http://mike.temporale.com/archive/2007/01/23/236.aspx
Click to expand...
Click to collapse
Mr monakh:
Ive tried the reset sequence many times before starting a new thread. Ive spent many hours just doing that in all the imaginable different timings. All I get is the HTC screen first and the Windows mobile screen second, after that, without a SIM, a screen telling me i have no sim and in the cursor just 99999 and after many alarms it crashes; with a sim, it will boot and 9999999... and the the screen locks and its impossible to press "unlock *"
This is the reason I'm asking for help. The only thing I can imagine is to re-flash the phone. I tried to re-flash it, but apparently i have to pay to get my phone unlocked before being able to re-flash. Is this true?
I really appreciate your help. Thank You.
Salvador.
I also want to add that i know its not a hardware problem, I disconnected the keyboard from the motherboard and the 99999 still there.
Is it possible that the hard reset sequence described above doesn't work? --(both soft keys work)
Is there a way to remap the 9 key into a harmless key, so i can hard reset the phone trough software?
(the phone syncs normally to my computer)
Thanks.
The hard reset sequence should work. I don't know of any reason, short of hardware failure, why it wouldn't.
I think you can try re-flashing the ROM, if you like, but it really is more likely to be a hardware problem than a ROM issue. It doesn't necessarily have to do with the keyboard (you actually disconnected the keyboard?!) but you can still can get the '9' for other reasons.
You don't need to get the phone CID unlocked to get a different ROM, but you do have to play around a bit to get it done. I am sorry, I can't offer more step by step help but it might be beneficial for you if you read through the following two threads:
http://forum.xda-developers.com/showthread.php?t=287316
http://forum.xda-developers.com/showthread.php?t=288230
http://forum.xda-developers.com/showthread.php?t=282199
monakh said:
The hard reset sequence should work. I don't know of any reason, short of hardware failure, why it wouldn't.
I think you can try re-flashing the ROM, if you like, but it really is more likely to be a hardware problem than a ROM issue. It doesn't necessarily have to do with the keyboard (you actually disconnected the keyboard?!) but you can still can get the '9' for other reasons.
You don't need to get the phone CID unlocked to get a different ROM, but you do have to play around a bit to get it done. I am sorry, I can't offer more step by step help but it might be beneficial for you if you read through the following two threads:
Click to expand...
Click to collapse
I thought it was water damage at first, but when i took it apart, i couldn't find anything to indicate there was any liquid in there. I thought maybe the keyboard was the problem and, yes, i did disconnect it from the motherboard (its actually really easy) and the same 9999. What other hardware reasons could make the "9" problem? I cant find any reason to believe its hardware. I boots kind of normally, it goes into manual bootloader no problem, it syncs with my computer etc. It just wont go into the hard reset mode! WEIRD.
I read the threads and the only clue i found to re-flash was to downgrade the bootloader by getting the phone in manual bootload (camera button and connecting USB) and run the .exe. I did, and INVALID VENDOR ID. Is anything i missed in the threads to be able to re-flash?
I truly appreciate your comments.
Salvador.
Try Reseting the CID.. 111111. I suppose that will work.
tejasphatak said:
Try Reseting the CID.. 111111. I suppose that will work.
Click to expand...
Click to collapse
tejasphatak:
CID, 111111, google.
Im on it.
Thanks!
dude why not replace it its under warranty man stop making an issue of this do your hoemwork read just like everyone else !!
I did it!
I tried the cid 111111 bla bla, and it was jut to much effort for a phone so i just went to imei-check and unlock everything. Damn! 40dlls, many Mexican pesos. So i installed the German version ROM and the F... 99999999 was still there!!!! I wanted to kill myself, monakh you were right. I opened the phone for like the 20th time and i knew it was hardware... and there it was, lead rust in the keyboard connector. I took a tooth brush, some alcohol and i brushed. Voilà! no more "9" I could have saved money time and effort if i just had looked close enough.
I'm happy i got into this, i love to learn new tricks.
You guys were really helpful, and a bit shady, i have to say.
Thank you.
Salvador.
. I think i am smart dumb!!.. <<-"Try Reseting the CID" haha.
This happens when you have too much of knowledge...!! truely education spoiled me!!
Glad it worked out for you and I am sorry you had to pay $40 but hopefully it will pay off for you in the long run.
leoiden, if you note, he is in Mexico and has no reasonable means to exchange the phone under warranty. It was acquired in France. Please pay more attention to the original post before prancing down someone's throat. Thanks.
Hello everybody,
I seem to have a major problem with my XDA Orbit: Not only it shuts down with no apparent reason so that I have to reset it, but it shows sometimes the dreaded "white screen of death" - from now on "WHISOD". The screen all of the sudden slowly goes white and sometimes shows dark vertical bands. After that - if I am lucky - I can reset the device, however a couple of times I already had to hard reset end even reflash it.
I have already checked software and plugin problems and would rather say that it seems to be a hardware problem. Any ideas out there. They would be highly appreciated.
Best regards,
Smack
i had the same problem and as at now my phone is dead becuase i did not flash it with the original rom. look for the rom it came with and flash it to the phone ,like how u first got the phone or u will loos ur phone very soon
I am not at all sure if it has to do with the ROM. I have tried different ROMs to check the error but it appeared with all of them. However the next time I will try again with the latest official ROM.
Thanks for the comment and your help. BTW Did you send your Orbit in for repair?
Regards,
Smack
Hi, do you use the uspl before every new rom install? Try it.
I have the same problem, my htc3300 is almost dead I think. No way I can even turn it on, allways end in the windows screen, and it was because I didn`t use the uspl before last rom install.
Give it a try, and let us know.
See ya.
Thanks. No flashing problem. I have flashed a couple of devices (always unlocking them before ;-) )and have had no problems whatsoever.
The problem I mentioned is not connected to any earlier flashing. The device works a couple of hours perfectly. However suddenly it starts to behave like crazy.
Now to your problem: If you can get into boot loader modus you will most probably be able to unlock your item. Search for uspl and download it. Then get into boot loader mode (press voice recorder button and power button while resetting the device) and you will get a three colored screen. Then connect the USB cable. You will see "usb" in small fonts on the screen of the device. Now you can run uspl. With a little luck the device starts again. However you can flash it again with a fresh ROM the same way (after unlocking it). This may (!) work.
Regards,
Smack
Hello,
I have the same problem, I already hard reset end even reflash my p3300 many times with different ROM.
I even tried running it for some time with and without the micro SD, ending with the same result: the screen of death.
Any ideas , tips, anyone ?
Thanks,
Roundi
Ok, I tried the following: Just take the battery out for six or seven hours and insert it again. The device seems to run smoother. Will keep you posted. Tell me if it works out for you.
Regards,
Smack
Ok, just removed the battery, I will leave till tomorrow morning.
I will keep you updated.
Thanks,
Roundi.
I have same problem here - though mine is the second phone and the fifth motherboard I've had. HTC just don't seem to able to fix it. I'm now trying to get a refund.
Hi, Jem.
Yes that's something I have thought about too. Did you you use the original ROM? However right now the system seems to be more stable. I have had only one blank screen after removing the battery (and one shut down).
Regards,
Smack
I have just put in the battery and switched on the phone after almost 24h.
So far so good.... I will try to use it for a while and will let you know.
Regards,
Roundi
Had the same problem again, when using Mortplayer. I have Mortplayer installed on the SD card. Could it be that the problems arise, when there is heavy usage of the SD Card?
Any ideas are welcome.
Regards,
Smack
Again it went SOD shortly after turning it on. I didn't launch any applications.
I am stuck here.....
I upgraded to Kavanna's 6.1 version yesterday and it was doing ok for a couple of hours. I changed my internet setting to T-mobile then awhile later my phone started locking up. Now, I can get it to turn on and get pass the Windows Mobile green screen. I have called myself checking the stickys but haven't found a solution.
I was going to go back and install the 6.0 version from Tmobile but my phone can syncronize with the pc.
Any help would be very appreciated or the phone will be tossed.
I had this same sort of thing when I upgraded to Rickys v24_with Opera Rom. The only thing I can suggest is to try and boot up without SIM and SD card in with it connected to the PC. This may allow you to synch to the PC. If not there is a thread in the WIKI on how to hard reset your phone on boot up.
you didnt by any chance over clock it using omap to say 288mhz did you ?
I don't think so. Put it to you like this - if I did I didn't do it intentionally and don't remember seeing anything like that while making any changes. I would like to get it to a point where I can try to make a change to it. Like I stated - it won't get pass the windows mobile window and it just sits there. You can turn it off sometimes and others you have to take the battery out. I do not know how to do a hard reset or anything else.
Just call me a dumb blonde female! BUT I have researched and researched and have NOT given up the battle yet.
Thank you.
tmac123 said:
I don't think so. Put it to you like this - if I did I didn't do it intentionally and don't remember seeing anything like that while making any changes. I would like to get it to a point where I can try to make a change to it. Like I stated - it won't get pass the windows mobile window and it just sits there. You can turn it off sometimes and others you have to take the battery out. I do not know how to do a hard reset or anything else.
Just call me a dumb blonde female! BUT I have researched and researched and have NOT given up the battle yet.
Thank you.
Click to expand...
Click to collapse
reflash it...see what happens.
http://www.htcwiki.com/page/The+Dash+FAQ?t=anon <--reset procedure is in there
blonde you say?
tmac123 said:
I don't think so. Put it to you like this - if I did I didn't do it intentionally and don't remember seeing anything like that while making any changes. I would like to get it to a point where I can try to make a change to it. Like I stated - it won't get pass the windows mobile window and it just sits there. You can turn it off sometimes and others you have to take the battery out. I do not know how to do a hard reset or anything else.
Just call me a dumb blonde female! BUT I have researched and researched and have NOT given up the battle yet.
Thank you.
Click to expand...
Click to collapse
Try a hard reset - (If I remember it's like this)
1. hold the two soft keys down,
2. press the power button for two seconds (while still holding down the softkeys)
3. release the power button
4. wait a little more and release the softkeys
OK everyone I have tried & tried to execute the "hard reset" with no luck. Same as before - when it turns on it is a white screen with HTC and it's symbol THEN it goes into the green Windows Mobile screen and sits there without any functions whatsoever. I can turn it back off sometimes with the on/off button then other times you have to take the battery out to get it to turn off.
It is so frustrating but thank all of you for your help/tips.
Blonde-yes Dumb-yes! Apparently!!
you must not be performing the hard reset operation correctly then. Itf you do it right, you wont see the HTC screen first, you'll see a black screen with white text saying to press the send or the 1 key to perform a hard reset.. you may need to try it a few more times.
view this video of a dopod 720 ( same as the dash and excalibur for how to do this... the hard reset part is around the 1:30 mark )
http://www.youtube.com/watch?v=0zstJkD8OkE
I swear - that's exactly what I have been doing! I bet I have done it 100 times or close to it.
Thank you...
tmac123 said:
I swear - that's exactly what I have been doing! I bet I have done it 100 times or close to it.
Thank you...
Click to expand...
Click to collapse
c'mon lucky 101!
More like "tired fingers"!! HeHe!
I'm not ready to give up - I'm too stubborn to let this beat me.
Update - I finally was able to reboot my phone last night after many many tries. It wasn't text book style but I kept pressing buttons until finally... AND NO is wasn't lucky 101!!! But you were definitely encouraging.
I haven't changed any settings because I'm scared to now.
Thank each of you for your kind replies and patience.
anything for a blonde.
I'm going to hold you to that!
Ummmm this isn't a dating forum lol
If i was you though, i would definitely clear storage command your phone.
Clears everything and hopefully reset the bug that was fondling with the wrong file.
Mikey1022 said:
Ummmm this isn't a dating forum lol
Click to expand...
Click to collapse
back off..i saw her first.
LOL!!
I spoke too soon! My phone definitely has problems. If I can ever get back to the "hard reset" beginning again I will try to start from scratch. It has some bugs in it for sure.
Thank you for the suggestions.
Hey Guys..
I have a Desire here in my Hands with a strange type of Brick.. (at least one I've never seen before) ..
It just does not react to anything at all. The battery is charged and I tested with another cell to be sure that is not the trivial cause.
No Bootloader, No HTC Logo, No reactions at all..
Did happen while flashing a Froyo 2.2 Rom + Radio + App2SD (from the xda forums) via ClockworkMod Recovery but I wasn't there to witness the actual Flash.
After flashing the device hung desperately in a screen with the robot in front of a box with an arrow .. looked like unpacking or so, but wasn't doing anything at all for at least half an hour.
Then battery removed -> Brick.
Anyone got any Idea?
messywrk said:
After flashing the device hung desperately in a screen with the robot in front of a box with an arrow .. looked like unpacking or so, but wasn't doing anything at all for at least half an hour.
Click to expand...
Click to collapse
I suspect you removed the battery whilst it was flashing the radio. This is insta-brick territory and as far as I'm aware there is no cure other than sending it in to HTC.
Regards,
Dave
If you can access fastboot as opposed to bootloader you might be talking failing that back to HTC it goes
if your phone can not turn off whilst holding either volume down or the back button then yeah it's a brick, send it off to htc, just say it overheated and wont turn on again
foxmeister said:
I suspect you removed the battery whilst it was flashing the radio. This is insta-brick territory and as far as I'm aware there is no cure other than sending it in to HTC.
Click to expand...
Click to collapse
The battery was removed after flashing and rebooting.
Installed in the following order:
32.41.00.32U_5.08.00.04.zip
LeeDrOiD_V1.2b.zip
942_desire_froyo_a2sd-signed.zip
every process seemed to work normal, no error happened.
Then rebooted the Desire and the "Box with Android-Bot" Screen appeared.. this hung for 30 min or more when I could not think of any other solution than removing the battery to reset..
After this -> nothing.
I suppose as you say it has to do something with the Radio ROM..
Been coming from OpenDesire 1.6b - every flash ran perfectly up to this point.
Damn, I think this one has to go back to HTC.
Is there any possibility to unbrick a phone thats not responding at all?
Could HTC be aware of the modifications or will they really just go with the "overheated and won't turn on again" explanation?
Thanks for your help so far guys!
Yea, the little Droid with the box thing is during a radio flash and you should never pull the battery during that as it does result in a brick.
Can you reach fastboot as mentioned up above?
..tried pressing the "back" button with the power button and the vol-down button together with the power button..
even did the "insert the battery while holding the button" method..
I don't think I can get the thing to Fastboot..
But I will look further into this and try..
..
Has anyone had a Radio Brick and sent this to HTC before?
Is the repair covered by warranty?
Do you guys think they even get this is no real HW failure?
messywrk said:
Has anyone had a Radio Brick and sent this to HTC before?
Is the repair covered by warranty?
Do you guys think they even get this is no real HW failure?
Click to expand...
Click to collapse
I know someone who sent their phone back with a pretty much identical issue and the phone was fixed under warranty no problem.
Regards,
Dave
yay!
you know, even one post of you telling me it went allright for another guy is a big relief..
EDIT: just wanted to let you know I tried invoking fastboot via usb and the android PC tools..
just keeps waiting for the device.. and waiting ..
..will analyse USB traffic in general to conclude if there is a little itsy bit of life left in the phone, but I think this is a dead end too.
thank u all for ur help i have managed to unlock the phone as described
thanks alot every1
saifiraq: You seem to have stumbled in the wrong thread or could we help by coincidence?
..UPDATE:
Did usb-sniffer analysis while pulling battery, trying to turn on, plugging usb in etc.
NOTHING at all..
My baby is on it's way to HTC now.. wish me luck guys!
Hi,
Right in the middle of use, my ATT Tilt 2 went to a basic, dead screen with red, green, blue, and white bars that says Rhod300 32m SS-BC, etc.
The operating system seems have gone down--it won't respond to anything. Hard reset produces the same results.
Can I flash a cooked or official Rom back onto this? I think activesynch is needed for a normal flash and of course I can't use active synch with the phone in this condition.
I think probably what I need is an original ROM install. Is this possible with a normal Windows 7 PC and a dead phone?
I have so many Windows Mobile programs and peripherals that I am trying to avoid going to Windows Phone at all costs--at least until they have basic stuff like file systems, a way to port over notes, etc. Also need a hard keyboard.
Right now using an older Fuze, which works, but is slower, worse screen, smaller, and lacks some of the features I like.
Thanks for your help.
You sound like you're in the bootloader mode. Tri-color screen.
You can flash from USB or from SD at that screen. I'd recommend trying to flash a stock ROM - as it flashes everything. Assuming that works, hopefully you can flash back whatever ROM you were on.
The phone isn't dead if you're at the tri-color screen. It should say 'serial' at the bottom - when you plug in your USB cable, it should say 'USB' and install some drivers. Then with the RUU software that comes with every ROM, you should be able to flash it.
Phone won't reboot--stuck on tricolored boot screen
Hi,
Thanks so much for replying. I appreciate you pros helping us novices.
Just after I posted the first note, I pulled the battery and hit the power button, it rebooted, and everything was still there in the OS--working fine. But whenever the device had to be rebooted, I would have the same problem of it getting stuck in the boot screen. After that, for the last several days once in awhile, randomly, it would finally reboot from the boot screen after I pulled the battery and hit the power button. The rest of the time (about 5/1) it would just sit there in the boot screen no matter what I did. The "Serial"/"USB" thing would change when I plugged it in, but that's all.
Thought it was the OS, so at a lucky moment where the "pull battery, hit power button" strategy actually worked, I installed the latest official HTC/ATT Rom--it's the next to last one issued that ends in .4.
It was gorgeous and I got all excited--started installing stuff thinking my problem was solved.
Had to reboot to install some programs--now it is stuck again on the boot screen. Tried 30x again--no luck with the "pull battery/hit power button"
strategy. Sometime it would flash a white screen really quickly saying something like "Can't read image!" before going into permanent boot screen. The boot screen will switch from "Serial" to "USB" if you connect it to the computer. So, the problem doesn't seem to be in the OS--rather, in the ability of the device to "read" the OS from the boot screen.
I would be grateful if you or anyone else may know what's going on here, and any ideas on how to fix it. Is there any manual way to get it to read the OS from the boot screen when that's not happening?
I have two guesses (both of which may be wrong):
1. It may be something in the hardware is just worn out and is less and less able to read the Rom--any ROM. I got the phone new off Amazon for a profit of $50 ($.01 cost plus a refund for an older phone) in the summer of 2010 when it was already outdated. and WP was replacing WM. I've certainly gotten my money's worth after 18 months!
Of course we now know that a brand new ROM has the same problem as the older one--which suggests to me it's in the hardware. I'm sure the new OS and the stuff I installed is still there on the phone, but something it appears is not reading something in order to allow the boot up.
2. I have a squirrely free program called Rax Reset (from Windows Mobile Marketplace) that does a software-based hard or soft reboot from inside the OS. The very last time the device went down and didn't come back up, I had used that program to soft reset it. Might have been a big mistake. Could this program be causing the problem? If so, just one reboot would allow me to get rid of it or even hard reset to remove everything but the new OS--but can't get it to boot.
If it turns out the phone is just worn out, I've certainly gotten my money's worth.
I still love WM even with all its problems--and especially the newer Sense version. If this one is shot, I'm thinking about just buying a new Touch Pro2 on Ebay to avoid all of the sacrifices and backwards steps involved with Windows Phone.
Thanks for any help anyone can provide.
Phil Butin
Why are you crossposting? I read this EXACT same post in a thread just below this, in the same section. That's pretty low.. Crossposting across forums isn't welcome, crossposting within forums IN THE SAME SECTION is definitely not welcome.
Don't do it again.
Sorry, just trying to get help
Sorry, just trying to get help, not that familiar with the rules.
I searched on "bootloader" and found a thread (wrote a comment there too), but it's old....
Here is the thread. It doesn't really provide any solution.
HomeArrow
Legacy & Low Activity DevicesArrow
HTC Rhodium: Touch Pro2, Tilt 2Arrow
Touch Pro2, Tilt 2 GeneralArrow
issues with bootloader.
Either way, whether you know the rules or not - why would you think copying and pasting the exact same words in the exact same forum help you any more...
Anyhoo, have you tried the usual? Flash stock? Sometimes I've heard you have to flash several times, I never really understood that logic tho.
I'll try to reinstall the HTC/ATT Sense OS again. I guess you're saying active synch doesn't need to be working in order to do that. I'm at work now--have to wait until i get home. Nothing to lose at this point.
But I'm seriously wondering whether the problem is the OS install or whether there is something in the device that is supposed to read the ROM and start the bootup that is just wearing out.
Thanks.
"No Image File"
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
[email protected] said:
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
Click to expand...
Click to collapse
That error message is 'normal'. Basically the phone checks the SD card for a file labeled "RHODIMG.nbh". If said file exists, it will flash from it. If no file exists, or no SD present - it continues loading bootloader and should say "Serial" at the bottom. This indicates that it's ready to be flashed. If you plug in your USB cable, it will install some drivers and then it should change to "USB" at the bottom instead of "Serial".
Now you should be ready to flash from a normal RUU. I would recommend flashing STOCK, because this flashes everything.
It might also be good to note a lot of people have experienced something similar - the phone getting "stuck" in bootloader mode, and only occasionally making it to WinMo. I'd guess it's failing hardware in some way shape or form, as none of my RHOD's or RAPH's have ever done this.
Good News--at least for now
Good news--I hooked it up to the computer with the USB cable for awhile and the Windows 7 computer did set up some drivers. For some reason after I disconnected it I reset it, and the reboot worked. Then I immediately uninstalled the squirrely reset program and removed it.
Everything I installed yesterday is working fine--I have soft reset it about 5 times now and each time it has rebooted. So I think maybe I'm back in business. Too soon to tell--but we will pray and keep our fingers crossed.
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
[email protected] said:
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
Click to expand...
Click to collapse
You're welcome. Basically if I or someone else posts something helpful, click the "Thanks" button under that post.
15 hours later, Tilt 2 is still working fine on the newly installed Sense OS. I have rebooted freely (using the stylus button on the side) since removing the program "Rax Reset," and everything seems to be going well. I'm keeping my fingers crossed, and will end my contributions to this thread with a warning about using "Rax Reset."
Thanks to all.