Hello all,
I want to start off by apologizing if this has been answered somewhere else........because if it has....I simply just cannot find it. I have been looking for hours and hours because i know people don't like reposts, but alas I don't know what else to do.
My Dad brought me his HD2 about a year ago complaining that he didn't want windows mobile anymore and he had actually been trying to install android following the instructions here on xda. Well I helped him get it installed using magldr and it has been working great. The other day he dropped his phone about 8 feet and broke the screen. The phone still worked fine, just a nice crack or 2 or 3 in the middle of the screen. He had the phone replaced but now whenever he boots it just gets stuck at go go go!
I have tried task 29, but when it comes to the screen that says current phone version it is blank then the next screen it tries to update but then it fails (see attachment). So i opened the Windows mobile device center to see if it was seeing the phone and sure enough it isn't syncing and i am not sure how to get it to sync. I did read however that I could just take the phone to the bootloader (the screen with the 3 colors), make sure that it said usb at the bottom and task 29 from there, but i got the same result.
I am pretty sure the radio is a 2.15.5* version, although i dont remember for sure because i did this so long ago. I thought it showed the radio on the bootloader screen, but now that i look it does not. It is on SPL-2.08.
Any ideas, thoughts or suggestions would be greatly appreciated. Thanks in advance for the help.
signed -senior frustrated
try using windows XP (activesync) and reflash...
troubleshooting step 1
phezthie said:
try using windows XP (activesync) and reflash...
Click to expand...
Click to collapse
Thanks for the suggestion!
I am using windows 7, but i do have windows xp mode. I installed activesync in the VM but it still cannot see my phone. I went into the bootloader and connect the cable, it changed to usb so i thought i would try and run the RUU exe and see if i would have any luck, but i am getting the same result. I am guessing the phone has to be recognized by the active sync, am i right? How can i go about getting it to recognize it?
You should try to reflash it with a stock ROM from microSD and see if everything else, but usb port, is OK.
NB It seems your usb port is faulty...
Related
any help is gratefully received.
i was doing a rom update(pugs) and the unit has become stuck in what i think is bootloader mode. the screen is dark and displays "serial v1.01
after much searching on this forum i tried to hard reset then run maupgradeut again.
problem is that activesync no longer detects my device.
ive tried pressing power/reset/action buttons to no effect.does this mean i now have a pretty coffee coaster.
now you were at bootloader mode. try remove the device n put it back on cradle, for sure windows will detect it. after that, try run the upgrade again. The problem that you're having now are same like me when I first bought my device. The answer is good being a newbies n ready to ask question at here. hahahahah
thanks
now youve hit the nail squarely on the head. i thought i knew enough to update but when its gone boobies up realised i dont.
ive tried resetting the device and then connecting to my pc several times with no success.
anyone know how to take the device out of bootloader mode. im hoping theres a backup stored on the device that will boot...or...anyone know how to get the pc to recognise the damn thing before i launch it out of the window(all the way to an o2 shop).
im sure im not alone(can hear the voices)
took some brain power on my part. turns out microsoft activesync was the problem.
upgraded to the latest version and everything went as it should.
I've got a problem with my XDA Mini S. It's been sitting in a box in my shed for about a year, before I got it out yesterday to have a play around with it, and possibly try some software I found on it.
I put my sim card in, plugged it in to charge, and turned it on. It worked absolutely fine.
I haven't done anything with it yet, but I've turned it on now, and the colours are messed up on the screen. For example there is a red hue over the today screen, and on certain screens (like in bootloader mode) the colours appear to be inverted (I will post pictures later if needed).
I've tried reformatting the device, but this has not fixed the problem. I thought I would try reflashing the rom on it. I used to have the original o2 rom on my old laptop, but lost that when I had to reload windows.
I downloaded the original rom from here, along with the Rom Update Utility, and attempted to reflash it. It gets as far as 'verifying the information on your PDA phone', then crashes with the error: Rom update utility MFC application has stopped working.
I'm running windows vista on my laptop, and read that the RUU won't work until the drivers are updated. Following the instructions on mrvanx.org, I have downloaded the driver for vista and installed it, but i'm still getting the problem when I try and reflash the device.
I've also tried running the RUU in compatibility mode for XP as it worked fine on my old laptop which was running xp, but it still crashes, every time.
I'm beginning to wonder if reflashing it will even work though, since the colours are messed up in bootloader mode as well, which leads me to think it may be a hardware problem.
I know next to nothing about repairing these though, and probably wouldn't bother if it's a hardware problem, but until I can reflash the firmware, I won't know whether this is a case.
I'll get the photo's of what the screen is like uploaded to my server later on, and post the links here, so you can see what the problem is.
Photo's now available
I've uploaded a couple of photo's to show what the screen is like:
http://csc2ya.co.uk/images/bootloader.jpg
http://csc2ya.co.uk/images/startup.jpg
Update
i've got my old laptop out, reloaded xp on that, and attempted the flash using that. However, I get the message 'rom update utility MFC has encountered an error and needs to close'
I just want to get it to reflash to see if it fixes the screen, but so far i'm having no luck at it.
I've sucessfully reflashed it in the past with the o2 rom using my old laptop, so I can't figure out why it isn't working now.
Update: I didn't have activesync installed on my laptop which was why the updater was crashing. I've installed activesync, but now i've got another problem that is preventing me from reflashing it. I start the updater, and click through the prompts. It gets to 'verifying the information on your pda phone', stays like that for about 30 seconds, then activesync disconnects, and I get the error: microsoft activesync cannot recognize this device for one of two reasons: then the other information that the dialog gives. I'm not going to bother typing it all out, as i'm sure nearly everyone has seen it at least once before.
Additional info: No idea if this is relevant or not, but the extended rom has been formatted using the service tool.
Another update: I have now managed to get the device to reflash, but it boots up afterwards as if I had just turned it off and back on again. I have tried a hard reset afterwards, but cannot seem to get any of the o2 stuff back. It appears that the screen problem is hardware related though, as it is still present even after reflashing.
I can also no longer get it to go into bootloader mode, but the phone will still boot normally.
csc2ya said:
It's been sitting in a box in my shed for about a year.
Click to expand...
Click to collapse
Not to be flippant, but there's your problem right there. Two things: extreme temperature, and moisture. Both are the enemy of electronics. Chances are very good that you're screwed.
The first thing I'd do is buy (or even better, borrow) a new battery. Yours is probably done for.
If that doesn't fix the problem, I recommend disassembly and thorough cleaning with isopropyl alcohol, followed by at least 24 hours of strong, dry airflow between 50-80 Fahrenheit. Any floor or desk fan would do. Reassemble and pray. If that doesn't do it, you're going to have to find your fun elsewhere, I'm guessing.
Myrddin Wyllt said:
Not to be flippant, but there's your problem right there. Two things: extreme temperature, and moisture. Both are the enemy of electronics. Chances are very good that you're screwed.
The first thing I'd do is buy (or even better, borrow) a new battery. Yours is probably done for.
If that doesn't fix the problem, I recommend disassembly and thorough cleaning with isopropyl alcohol, followed by at least 24 hours of strong, dry airflow between 50-80 Fahrenheit. Any floor or desk fan would do. Reassemble and pray. If that doesn't do it, you're going to have to find your fun elsewhere, I'm guessing.
Click to expand...
Click to collapse
The battery appears to be fine. I charged it overnight, and it still seems to hold a decent charge.
I haven't really got the tools to dissasemble it fully, but I will give it a go sometime in the next few weeks (i've got a copy of the service manual on my computer, so that shouldn't be a problem).
I only really got it out to play around with it again, and possibly try some apps on. It still appears to work fine apart from the screen (and the o2 applications now missing due the extended rom format, but i'm not bothered about those). I've installed the my mobiler screen program on my laptop so I can at least view the screen properly using that.
Thanks for the suggestions anyway.
csc2ya said:
I've installed the my mobiler screen program on my laptop so I can at least view the screen properly using that.
Click to expand...
Click to collapse
Well, this certainly changes things. You have a bad screen, or a bad connection to the screen. You can get replacement for around $100USD, or you can try to get a broken unit with a good screen for less (maybe). I'd still disassemble it first, though, in case it's just a weak connection.
Many ppl have problems with "black" screens that "stop" working.
my HD: Stock rom, radio, europe location, non modified, non damages.
Screen is just black, but phone,sound and touch panel! work
first time when screen gone black i make hardreset by (unplug touchpen)press vol-up + vol-down + power. after HR screen work again !.
7-14 days ago screen gone black again ... HR dont help, unload&load battery dont help, so i use product Warranty, and now w8 for back HD & summary.
If you have the same problem just post here.
I have the same problem and sent it back for servicing.
Apparently needs to change the whole board.
Looks like there is a defective batch of HD. Reported also by another user.
I have the same problem, sometimes screen goes black about 5-6 times for day,sometimes 2-3 day is ok! im sending back to store
Mine is doing the exact same thing, touch still works fine but screen shows nothing on it. Lucky i had MyMobiler installed so i can see the screen through activesync on my PC
I have this problem too. This is becoming quite a common problem with HD.
I sent mine back for repair where they have to replaced the mainboard.
Definitely a hardware problem. Hope you have warranty.
How will warranty go with a custom (Dutty's) ROM installed?
Was installed using USPL, has never had HardSPL installed on there
Pugsley_21 said:
How will warranty go with a custom (Dutty's) ROM installed?
Was installed using USPL, has never had HardSPL installed on there
Click to expand...
Click to collapse
You won't have warranty with a custom ROM. Did you backup your stock ROM?
Stock ROM can be downloaded from the HTC site, but how to install it without a working screen?
Pugsley_21 said:
Stock ROM can be downloaded from the HTC site, but how to install it without a working screen?
Click to expand...
Click to collapse
I had this problem with black screen though I could still feel vibrations when clicking soft keys etc, so I knew phone was on.
What I did:
Removed battery overnight
Inserted battery and turned on device
Device worked normally again.
If this doesn't work then you definately have a faulty motherboard.
This also means you would be unable to flash custom rom on device. This could void your warranty. However I have heard of people getting phones fixed under warranty with same problem due to HTC not being able to check wther or not you had changed rom beforehand
Hmmm, well currently my phone is back where i bought it, they wanted all packaging so they haven't sent it off yet. I'll get it back tomorrow and try removing the battery overnight, as mine sounds just like yours in that it still turns on but with no screen
According to the HTC site the stock ROM should install as long as activesync can see the phone. So there might be hope in flashing a stock ROM back on before warranty
Pugsley_21 said:
According to the HTC site the stock ROM should install as long as activesync can see the phone. So there might be hope in flashing a stock ROM back on before warranty
Click to expand...
Click to collapse
If your phone turns on and still connects to pc, then yes its possible. Try it and see what happens. You should still be presented with standard flash pop up screen on pc as well as % flashed etc which will change to flashing finished so you know you have completed flash process.
I've found out that MyMobiler will automatically install itself onto the phone when it is plugged into the PC, so there's still hope to see the screen after a reflash. Just need to get my phone back
Went to the shop and managed to flash the stock ROM back onto the phone, after downloading it from the HTC website. Now it's going back (hopefully) to HTC, or possibly Telstra. I'm hoping they send me a new one, as they wanted all of the accessories that came with it, box etc
Yep, same problem here. And mine is also a Telstra T8285. Maybe the bad batch is mostly in those?
Anyway, I have managed to re-load the stock rom with no screen. It's quite easy actually. Just make sure ActiveSync sees the phone, and you're good to go. No need to have to see the screen of the phone.
I'm in the US and was routed to HTC's support here in the US. Of course when I told them the model I have, they said they don't have the parts to repair it here in the US, so I'd have to send it overseas. He said they will contact me from HTC over there within 2 WEEKS. What? So I sit here and wait... blah.
stpete111 said:
Yep, same problem here. And mine is also a Telstra T8285. Maybe the bad batch is mostly in those?
Click to expand...
Click to collapse
btw, mine is also a Telstra T8285 so it definitely seems to be a problematic batch for Australia. Mine took three weeks to return and they replaced the mainboard. So far so good.
Hi,
I have exactly the same issue. The screen is black, but the phone does operate. I can connect it to my PC and even "see" the screen using EveryWAN remote.
The problem is, I have the Energy 6.5 ROM and Hard SPL 1.56 installed, and I cannot flash it back to the stock ROM and SPL, so that I can send it back under warranty.
I have tried 2 ways:
1. Putting it into Bootloader by pressing Vol down and ON - but it is impossible to tell if it actually goes into it because the screen is black, and when I try and run the ROM update utility, it cannot connect (error 260).
It seems like I cannot actually get it into the bootloader. I have tried lots of times...
2. Running the installer from when the phone is on and connected to the PC by activesync. In this method, the update utility gets as far as starting the progress bar, but then the phone seems to disconnect from the PC and again I get connection error 260.
This is really frustrating, any ideas would be greatly appreciated...
stutjones said:
Hi,
I have exactly the same issue. The screen is black, but the phone does operate. I can connect it to my PC and even "see" the screen using EveryWAN remote.
The problem is, I have the Energy 6.5 ROM and Hard SPL 1.56 installed, and I cannot flash it back to the stock ROM and SPL, so that I can send it back under warranty.
I have tried 2 ways:
1. Putting it into Bootloader by pressing Vol down and ON - but it is impossible to tell if it actually goes into it because the screen is black, and when I try and run the ROM update utility, it cannot connect (error 260).
It seems like I cannot actually get it into the bootloader. I have tried lots of times...
2. Running the installer from when the phone is on and connected to the PC by activesync. In this method, the update utility gets as far as starting the progress bar, but then the phone seems to disconnect from the PC and again I get connection error 260.
This is really frustrating, any ideas would be greatly appreciated...
Click to expand...
Click to collapse
What I'd try is running USPL before running RUU
Quote from wiki
ERROR [260] : CONNECTION
This error occurs when the RUU cannot make a connection to the device right before flashing. This typically happens when you try to flash a new SPL to your device. Use Soft-SPL before attempting the RUU again.
Click to expand...
Click to collapse
Thanks for the help Fallen Sparten.
Unfortunately it does not work.
The USPL also cannot find a connection. I think it is because I cannot actually put the phone into the bootloader - It is impossible to tell because the screen is blank. What I can say, is that when I press both the volume down and power key, nothing seems to happen. There is no connection sound from my computer and the RUU does not detect the phone.
I also get the same error if I try and update the phone from an activesync connection. i.e. when the phone is operating normally - I can tell it is operating normally because I can view the files with activesync.
Please any more ideas?
This happened to me as well. Was there some kind of software update that HTC pushed out that affected a few phones?
I see about 10-15 people on here that got hit with the same thing at the same time.
well I've had this issue as well, I have flashed back to stock rom (blind as activesync could see it tho I couldnt so no idea whats gone on)
When I called customer service they barely batted an eye and ahve arranged a replacement to be shippped to me tomorrow.
Be interesting to see what they say (if anything when they get mind back)
so, i've been around xda for awhile, but I have a problem with a t-mobile wing
i used to use this wing way back when i got it new when it came out, but i got a g1 when that came out, so i totally don't remeber how to mess with it, and I gave the phone to my father.. now it has some problems and i was wondering if anyone had a similar experience...
i know that i hard spled it and put on some sort of windows 6.1 rom a year or two ago, and it had been running fine, syncing with both a windows 7 and a windows xp computer... however, recently, it has been very random in when it syncs, and when it has an error. my t-mobile shadow and the tp2 both sync fine with the computers, so i feel that the error is on the wing's side. when i try to put on a new rom via sd card or with the launcher from my computer, it starts up, and then suddenly says something about the certificate not being correct, and reboots back into the old windows mobile i had
i assume that since i had problems with both usb and with microsd, the problem doesnt lay with the usb port which i previously had considered as the source of errors, so i was wondering if there was something i had forgotten to do to the phone in order to put on a new rom, or if there was something speical required to flash new roms using a windows 7 x64 install.
sorry for the long kinda rambling post, but if anyone could shed some light on this, it would be nice! thanks
So you can NOT flash via MicroSD? That's weird. Make sure you're following the instructions correctly.
Also, if that still fails, try re-HardSPLing your phone...it shouldn't hurt anything, and hopefully would help!
Tell us how that all goes.
A few weeks ago I purchased an Orange SPV M5000 (HTC Universal) from a company in the UK (I'm South African). It was running perfectly and I was quite happy with the windows mobile 5.0, but I wanted to be able to run Whatsapp on it, so I tried to upgrade it to windows mobile 6.5, but as I was trying to upgrade it using the suggested roms and programs on this website and it's now completely dead. Before it would show "serial" and "version" on the screen, just the back light was off, I managed to fix it when is that mode following advice from your community by merely running the program "nuetty" and reset the device, both hard and soft. It was running perfectly even though I messed it up, but now I can't even get my Windows 7 starter edition to even recognize the phone when I plug it in as a usb. It says "USB device not recognized" and nothing I do can get recognized or even turn the phone on.
I love the phone and I'm a film maker and playwright and I'm supposed to be in contact with a few producers about having my work shot and filmed, but alas since I broke the phone (it seems) I can't get in contact with them, and that's bad news.
Please anyone please I am so desperate, what do I do? It's not a hardware error I'm certain, but here's what happened: I downloaded a few roms I expected would work, but none did. When I would run them my Mobile Device Centre just exits and though my phone is connected. via usb it just can't be picked up by the Device Center. It seems as though I wiped everything from the phone, not just the data, but the OS and everything, I imagine because the screen is completely blank (not even serial written on it) and resetting does nothing. This at least is my theory. I hope I'm wrong.
I am so desperate, please guys help me! There's no place I can take my phone to to repair it where I live, so I need your professional, and kind help. Please save me guys!
Jack-of-Plays said:
A few weeks ago I purchased an Orange SPV M5000 (HTC Universal) from a company in the UK (I'm South African). It was running perfectly and I was quite happy with the windows mobile 5.0, but I wanted to be able to run Whatsapp on it, so I tried to upgrade it to windows mobile 6.5, but as I was trying to upgrade it using the suggested roms and programs on this website and it's now completely dead. Before it would show "serial" and "version" on the screen, just the back light was off, I managed to fix it when is that mode following advice from your community by merely running the program "nuetty" and reset the device, both hard and soft. It was running perfectly even though I messed it up, but now I can't even get my Windows 7 starter edition to even recognize the phone when I plug it in as a usb. It says "USB device not recognized" and nothing I do can get recognized or even turn the phone on.
I love the phone and I'm a film maker and playwright and I'm supposed to be in contact with a few producers about having my work shot and filmed, but alas since I broke the phone (it seems) I can't get in contact with them, and that's bad news.
Please anyone please I am so desperate, what do I do? It's not a hardware error I'm certain, but here's what happened: I downloaded a few roms I expected would work, but none did. When I would run them my Mobile Device Centre just exits and though my phone is connected. via usb it just can't be picked up by the Device Center. It seems as though I wiped everything from the phone, not just the data, but the OS and everything, I imagine because the screen is completely blank (not even serial written on it) and resetting does nothing. This at least is my theory. I hope I'm wrong.
I am so desperate, please guys help me! There's no place I can take my phone to to repair it where I live, so I need your professional, and kind help. Please save me guys!
Click to expand...
Click to collapse
Hi I'm relatively new to flashing etc etc and have just managed to resurrect one of my HP6915 which locked after an attempted WM6 upgrade.
I used "Uni_Exitbootloader" perhaps this will bring yours back to life, also try another OS perhaps XP as w7/Vista are a little fussy about port release/control i believe.
Also which rom/s have you attempted to flash ? i have an SPV 5000 lying about some where if i can find it ill attempt one of your upgrades.
Good Luck
PIP