Develop Bugs

Hour 3 of unsucessfully attempting to update Rom

Alright I'm finally going to throw a post up, go ahead and get all your "use search" "it's on search" "it was in a thread" out of the way now, cause I've gone through 76 thread pages of reading and searches and I can't find an answer that works.
I am continually getting the ERROR 262 in RUU everytime I attempt to use it to flash.
- I am running Vista 64bit (not sure if that is the problem or not)
- Using WMDC 6.1
- I have uninstalled and reinstalled WMDC 6.1 a total of 7 times
- I have used every single USB port on my computer.
- I have restarted a total of 15 times, both the computer and hard resets of the phone.
- I have tried both the Unlocker (I'm not sure if I have to unlock a second time or not after my WM 6.1 update) and just the ROM Update.
- I have tried doing the forced bootloader mode (Power+Camera+Reset) and simply allowing the program to do it on it's own.
Everytime it drops into Bootloader (3 color) mode, it drops Activesync and then obviously errors out because of lost connection. I've tried simply running the program and never unplugging the USB cable, I've also tried unplugging the USB cable when the DOSprompt part of the batch tells me to. Everything I've read says to do this, but I don't remember doing this for the 6.1 WM Update. It also doesn't make sense.... if you unplug the device, it's going to drop activesync everytime....
I've just updated every program, reinstalled everything more then 5 times, done countless resets, tried every USB plug and nothing is working. Hopefully this is something easy I'm just overlooking -- or something easy like "It doesn't work with Vista 64" so I can at least get an answer.
Again, I apologize if this was answered somewhere previously. I genuinely tried for 3 hours using search, on and off XDA, so that I wouldn't have to post a question thread but never found a "fix" that worked.
Thanks in advance.

Traumatique said:
Alright I'm finally going to throw a post up, go ahead and get all your "use search" "it's on search" "it was in a thread" out of the way now, cause I've gone through 76 thread pages of reading and searches and I can't find an answer that works.
I am continually getting the ERROR 262 in RUU everytime I attempt to use it to flash.
- I am running Vista 64bit (not sure if that is the problem or not)
- Using WMDC 6.1
- I have uninstalled and reinstalled WMDC 6.1 a total of 7 times
- I have used every single USB port on my computer.
- I have restarted a total of 15 times, both the computer and hard resets of the phone.
- I have tried both the Unlocker (I'm not sure if I have to unlock a second time or not after my WM 6.1 update) and just the ROM Update.
- I have tried doing the forced bootloader mode (Power+Camera+Reset) and simply allowing the program to do it on it's own.
Everytime it drops into Bootloader (3 color) mode, it drops Activesync and then obviously errors out because of lost connection. I've tried simply running the program and never unplugging the USB cable, I've also tried unplugging the USB cable when the DOSprompt part of the batch tells me to. Everything I've read says to do this, but I don't remember doing this for the 6.1 WM Update. It also doesn't make sense.... if you unplug the device, it's going to drop activesync everytime....
I've just updated every program, reinstalled everything more then 5 times, done countless resets, tried every USB plug and nothing is working. Hopefully this is something easy I'm just overlooking -- or something easy like "It doesn't work with Vista 64" so I can at least get an answer.
Again, I apologize if this was answered somewhere previously. I genuinely tried for 3 hours using search, on and off XDA, so that I wouldn't have to post a question thread but never found a "fix" that worked.
Thanks in advance.
Click to expand...
Click to collapse
Try another computer. It does work with Vista 64 (I've done it many times), but there's no point in beating your head against the wall for this. There are so many things that it could be you might as well try another computer so that you at least now it is the computer and not your Vogue.
-GT

You phone is not unlocked and you are trying to flash a custom ROM.
Try following the instructions in this thread found about halfway down the first page of the forum.
http://forum.xda-developers.com/showthread.php?t=508544

atoz350 said:
You phone is not unlocked and you are trying to flash a custom ROM.
Try following the instructions in this thread found about halfway down the first page of the forum.
http://forum.xda-developers.com/showthread.php?t=508544
Click to expand...
Click to collapse
Be it locked or unlocked is beside the point. As I stated before, I unlocked it once for the WM 6.1 upgrade and being as I wasn't sure if I had to do it again, I attempted to do it again.
Regardless of if it's trying to flash the ROM, or use the Unlocker, the same thing always happens. Windows Mobile Device Center (ActiveSync) drops connection once the phone goes to the Bootloader (3 color screen), and it errors out 262 (Connection Lost).
I have attempted to give as much information as possible so I can get input on if I'm missing a step or if it's simple bugging out. I will try what gt! suggested and attempt this on a different computer. However, from the information I've given can anyone confirm that I'm at least doing the correct steps -- there's just some gremlin popping up keeping me from completing it?
Thanks again.

Flash via SD card. There are instructions in CodyBear's FAQ thread.
From experience...use a blank or backed up card.

Traumatique said:
Be it locked or unlocked is beside the point. As I stated before, I unlocked it once for the WM 6.1 upgrade and being as I wasn't sure if I had to do it again, I attempted to do it again.
Regardless of if it's trying to flash the ROM, or use the Unlocker, the same thing always happens. Windows Mobile Device Center (ActiveSync) drops connection once the phone goes to the Bootloader (3 color screen), and it errors out 262 (Connection Lost).
I have attempted to give as much information as possible so I can get input on if I'm missing a step or if it's simple bugging out. I will try what gt! suggested and attempt this on a different computer. However, from the information I've given can anyone confirm that I'm at least doing the correct steps -- there's just some gremlin popping up keeping me from completing it?
Thanks again.
Click to expand...
Click to collapse
CONNECTION DROPS BUT............ it should be installing new drivers.
When i flash my phone on windows 7 it loses connection when it enter bootloader just like you.
And by the time the drivers for the qualcomm chip on my htc touch vogue gets installed (this is the recognized driver when your phone is in bootloader)
the RUU rom updater/installer times out.
After it times out for me i make sure that the driver for the qualcomm chip (the driver that is seen by windows when your phone is in bootloader) is installed, i run the updater again.
Now it should run through smoothly again.
Alternate method:
Flash by ur sd card.
or
Try a different computer.

start it up on serial mode then plug it in to USB, go to device manager make it search for new devices. Driver should start loading and start RRU, if all else fails use the SD CARD for The Flash

Alright, well now I guess a second question looms. I was going to take everyones advice and attempt to flash with the MicroSD Card, but now I'm having problems with that one as well.
Yes it has to be 2GB or less and formatted FAT32
I always find my original 512MB works perfect for flashing from
as to how to get it to your card...
Extract the ROM you want to use
Find the largest *.NBH file and copy it to your desktop
at the desktop rename it to VOGUIMG.NBH (I believe the caps in naming is important)
Copy that file to the root of your formatted FAT32 2GB or less SD Card
enter bootloader mode and it should go from there.
Click to expand...
Click to collapse
Those are the directions on the FAQ. I have the original 512mb card, formated to FAT32. I went into the Unlocker RAR, found the Voguimg2.nbh, renamed it to VOGUIMG.NBH as instructed in the FAQ. Placed the file on the freshly formatted MicroSD Card, put it in the phone and went to bootloader mode and... nothing.
I attempted putting the card in, then going to Bootloader. I tried going to bootloader, then putting in the card. I tried putting it from USB to Serial and vica versa. Tried hitting all the buttons. Nothing happens, it just hangs out on the 3 Color Screen.
Am I missing something, or am I just cursed to not flash my phone more then once? Heh. Thanks again for all the help.
[EDIT] For clarification, since I don't know if I have to unlock before every flash or not, I'm just attempting to unlock it again and hense only using the Unlocker ROM. It was previously flashed for the 6.1 update, but I figured it couldn't hurt to try the unlocker again so that's been the ROM I've been trying to run currently.

Traumatique said:
Alright, well now I guess a second question looms. I was going to take everyones advice and attempt to flash with the MicroSD Card, but now I'm having problems with that one as well.
Those are the directions on the FAQ. I have the original 512mb card, formated to FAT32. I went into the Unlocker RAR, found the Voguimg2.nbh, renamed it to VOGUIMG.NBH as instructed in the FAQ. Placed the file on the freshly formatted MicroSD Card, put it in the phone and went to bootloader mode and... nothing.
I attempted putting the card in, then going to Bootloader. I tried going to bootloader, then putting in the card. I tried putting it from USB to Serial and vica versa. Tried hitting all the buttons. Nothing happens, it just hangs out on the 3 Color Screen.
Am I missing something, or am I just cursed to not flash my phone more then once? Heh. Thanks again for all the help.
[EDIT] For clarification, since I don't know if I have to unlock before every flash or not, I'm just attempting to unlock it again and hense only using the Unlocker ROM. It was previously flashed for the 6.1 update, but I figured it couldn't hurt to try the unlocker again so that's been the ROM I've been trying to run currently.
Click to expand...
Click to collapse
As explained in Cody's FAQ, once your phone is unlocked to flash, it stays unlocked. The only thing you MIGHT want to do other than just flash the new ROM is to flash a stock ROM, then the new ROM.
Go ahead and try putting the VOGUIMG.NBH from the ROM on the card and see what happens. From what I remember, you should have the card in the phone then put it into boot mode. I believe that was what I did for my first flash ever.
What method did you follow when you flashed to 6.1? Has anything changed about what you are doing now?
Also it might be important to know that when flashing via USB on a 64-bit machine the RUU program will give you an error about not working on a 64-bit computer. Just ignore the error and click ok, it will pop up a few times just keep hitting ok and it will work. That error pops up even though it's false.

when i first tried flashing a custom rom, i extracted the downloaded file and when i clicked on the ruu i had the same error... i then tried just running the downloaded file without extraction and it worked fine.

same thing happend 2 me Just run the RUU do not extract files!!!!!!!((-;

Barogi44, JFive1182 -- You are both princes among men.
The Unlocker will only run on the first auto-extract of the file. You cannot run the batch from the extraction folder afterwards, eventhough all it does is auto-extract the contents and then auto-run the batch file.
Out of curiosity... and being infuriated I went and tested this again just to see. On 3 other computers the same thing happened. I have no clue why it would bug out that way... or if it was written that way that's a pretty bad design.
In any case, someone should put that in the FAQ. You have to let it start the process from the auto-decompressing RAR, you can't start it again after the fact by running the batch file from the extracted folder. If it said this anywhere, the 3 guides I read never mentioned that (nore the unlocker's thread at ppcgeeks) so I didn't catch it.
Thanks again for everyone's input, and obviously JFive1182 & Barogi44 for actually letting me know how to make it work!

your welcome

Traumatique said:
[..]The Unlocker will only run on the first auto-extract of the file.
[...]someone should put that in the FAQ. You have to let it start the process from the auto-decompressing RAR, you can't start it again after the fact by running the batch file from the extracted folder. If it said this anywhere, the 3 guides I read never mentioned that (nore the unlocker's thread at ppcgeeks) so I didn't catch it.[..]
Click to expand...
Click to collapse
Bump for emphasis. I had the same problem.
Tutorial said this: "Use WinRAR and extract both the files into separate folders,"
ONLY extract the NFSFAN rar.

Stuck/freeze (Hero) while downgrade. Not working now at all!!

Helo dear friends.
Well I just wanted to get some Hebrew in my Hero.
I have the Orange hero in Spain. Upgraded to official rom - 2.73.61.5, worked fine.
Now i am trying to downgrade it, so i can root it, so i can add all the fun stuff (including hebrew).
Did the gold card, since i understood that this hero is CID locked. (and maybe i am wrong). Then failed few times with error 140 when tried the 1.76.405.6 and 1.76.405.1 rom downloads. Then tried to downgrade to 2.73.405.5 rom as someone suggested here... and the process started happily, downloaded Splash1 ok, system ok, userdata ok, boot ok, bootloader ok, then GOT STUCK ON "Radio-V2 - updating" (at about 85%.. froze!)
(I attached a picture).
This happened few times, sometimes never even started to download, was just froze at the beginning of the process with: "zip header checking..."
So every-time this happened i had to disconnect it, pull the battery out or something, and try again. (I also found out that for some-reason things moved forward when restarting windows which by the way, works on parallels, mac ...)
Now the hero is stuck on the white error screen i guess, pictures attached.
Mmmm... hope someone can suggest something... straight and to the point, i feel i am going circles will appreciate allot.
Thanks in advance
Cheers!

First off ... KEEP THE PHONE PLUGGED IN! (So the battery doesn't die... If i remember right... fastboot chews through battery)
Next.. how long has it been stuck?

Well, first time for 30 minutes of no movement, then at the rest of the attempts i kept losing my patient each 20-30 minutes... in a process that might take 10?
yeah the battery ran out once..
thanks.

Trying again, now it's stuck on "system - updating". 20 minutes.
Please help.. someone?
Should i try another rom? any suggestion for Orange Spain?
Someone experienced problems via Parallels ?

Parallels as in your trying this from a VM? I would bet thats your problem! While it techincally shouldn't make a difference... I would try with real PC!

yes, virtual machine...
Ok, and that PC, should it have all the drivers for the phone? i mean now that the hero is stuck, would a different computer recognize it?
I should just download the rom to the computer and try to install it?
thanks.

You'll want to install the USB drivers (The HTC Sync download from htc.com likely has these included...)
If the VM still see's it - any PC with the drivers installed correctly will see it.
If you get the the custom recovery image flahed, you'll be able to do everything from your mac after that...

ho really? can you elaborate a bit on that? start with: " custom recovery image flahed"
Thanks.

Details @ http://forum.xda-developers.com/showthread.php?t=561124

Thanks. and this i do after i downgrade successfully the rom (with lets say a proper PC?) ?
Do i need to root after downgrading?

As far as I remember - Yes - you will need to root the phone, then:
adb remount
adb shell rm /system/recovery.img (If this fails with file not found dont worry about it)
I seem to remember needing those when I rooted my hero ...

Thanks kiall, resolved it at the end, without downgrade, no PC, just pushed the Recovery to the formatted sdcard, flashed it and the modaco rom and then radio and hebrew fonts, all is ok now...
Thanks for you time.

How to get to recovery if i can't see the screen?

Can you help me, i've made a mistake attempting to downgrade and root an HTC Desire on Voda UK from hboot 0.93. Downgrade seemed to be successful, but the device was stuck in bootloader mode. Since then i have managed to lose my goldcard and flash an uncompatible RUU. And now the screen is dead but if i pop out the battery and put it back in i can hear the start up animation sounds. What can i do to recover my screen? Your advise would be appreciated. Mat

Old versions do not support SLCD (Your Display) hence it turn black (i had hard time, believe me), i personally installed newest official RUU and everithing went OK. But there other solutions, read here http://forum.xda-developers.com/showthread.php?t=748498
wish You luck

Wish i could help you but i don't remember. Been pre-occupied with trying to find a fix and move forward. Can't guarantee that i wouldn't make the same mistake again either. Currently flying blind withthe 'SLCD BRICK FIX Method1' without success.

download ADB to your computer
open up a command prompt/terminal window
cd to your adb/tools directory and type:
adb reboot recovery

Thanks for your reply. I downloaded adb sdk etc but my lack of skill in the command promt is holding me back, not to mention that the Device screen is still black and it isn't recognised by my pc when i plug it in. Don't know what to try next..

With goldcard inserted, started phone in fastboot mode (back key and power button). Flashed back to stock htc rom. Screen is back on and i'm up and running.
Thought i had tried this before but it worked this time (so happy!). Thanks for reading and helping.

Woulda been easier following this guide - as should everyone else currently:
http://forum.xda-developers.com/showthread.php?t=768256

]SK[ said:
Can I ask which method you were using? I see your on Vodafone the same as me. I got my Desire yesterday and want to use OpenDesire however I fear that I will make a mistake and end up in the same situation as yourself.
I was going to follow this http://forum.xda-developers.com/showthread.php?t=768256 guide although I can't as I don't have a SD caddy to plug it into my PC.
*Mods*
Can a mod please fix it so I can post URL's please?
Click to expand...
Click to collapse
URL privileges will be working soon.
And if I come across any new members URL issues I put them in for them.

Bricked!fastboot works in cmd, no adb, recovery/bootloader menus

Would appreciate your help on the following issue (amoled display):
- phone doesnt boot up, it is stuck to a screen showing htc in the middle and 4 small triangles in the corners; if I unplug the pc cable it goes to a RUU menu
- no access to recovery or bootloader menus (by holding power + vol down/back)
- installing stock RUUs dont work; there is a 110 error saying that the RUU is not complete (tried 5-6 RUUs, both 2.1 and 2.2). there is a progress bar on the phone's screen that is normally green, but turns red when the radio is being written (as per the install wizard on the pc) and there is another triangle showing up at the end of the progress bar
- fastboot oem boot restarts the phone, but then it gets stuck to the white screen having htc in the middle (like when you start up the phone and after this quietly brilliant shows under htc, for me it doesnt go beyond this initial point)
- fastboot reboot-bootloader restarts the phone into the same 4triangles screen with htc in the middle
- adb doesnt work as it doesnt show my device
- any power + vol down/back combination brings the phone to the 4triangles screen
- if I run the stock RUU after fastboot oem boot (white screen with htc in the middle) there is a menu showing up on top of the white screen showing up the progress (1-bootloader, 2-radio_v2, 3-radio, then system, recovery, user data, etc.); bootloader is updated ok but then it gets stuck when updating radio_v2 and doesnt move further from that point)
- after the RUU install fails, I plug out the pc cable and see the RUU menu; depending on the RUU that I try to flash the hboot version changes up and even goes down after, but the firmware (what the RUU installer "sees" on the phone) and radio (seen on the RUU menu) remains the same: 1.21.405.1 and 4.06xx; the date on the RUU menu also changes depending on the RUU that I try to flash
Any suggestions to get my desire unbricked?
Bit of a background to the problem:
- rooted (unlockr) and was having Paul's r3 rom (2.1)
- updated the radio to 5.10xx
- got into silly restarts when using gps and thought to reflash a new rom and went for Paul's r8
- restarts were there also when using the phone normally
- thought to re-do all the rooting, wiping out everything from the phone, etc; so having r8 as the rom (pre-baked version) I started the rooting process with creating again the goldcard, etc etc
- error message at some point saying partition update fail (following the steps from theunlockr as I did the first time when rooting) and then the phone got to this triangles screen with htc in the middle
- strange though that this screen is different than the one when I first rooted when there was just one big triangle in the middle
Thanks a ton guys!

I've seen a few posts about this screen with the 4 triangles, but never seen the result of any potential fixes, or if it was ever actually fixed.
Just an idea, but it was maybe a bad radio flash if you are saying it started playing up after that? Unfortunately a bad radio flash is fairly terminal so I hope that's not your problem.
Good luck with this one and if you get it fixed then post the result here if you don't mind!

Will definitely post the solution when found; so far though nobody has any thoughts around what might be the reason behind this problem and how to get around it. I dropped a few PMs to the people that had this problem in the past and contacted Paul at Modaco, but so far no replies...

You can fix this with an RUU, I've had the same issue when I unplugged too early after flashing, but you are asking for help in the wrong section.

thought that the dev's section is where the best knowledge exists...
about the RUU process, I am trying to flash stock RUU.exe files, but there is a problem when the radio is being written and then I get a 110 error from the RUU install wizard saying that the RUU is incomplete.
for you the RUU install worked smoothly?

If you get a write error during an RUU flash (i.e. while the flashing is taking place, not before) it probably means there's a hardware fault.

Could be hardware, but I find it hard to believe as the phone is new and it is network locked, hence I didnt even use it for real, apart from some wifi and gps activities. Besides, the phone worked very well when I first rooted with Paul's r3 and the whole mess with restarts when using gps started after I upgraded the radio to 5.10xx having a 2.1 OS.
I feel that the problem started when I tried to root the phone being on Paul's r8 2.2 OS (tried to root with a 2.1 system and then it got messed up in the process).
I am not saying that it is not hardware as it is a possibility, but still think that it might be a messy software aspect, as if the radio is messed up from a hardware perspective, then at least the system should boot up and then wifi, gps, gsm and the things that are controlled by the radio shouldnt work...but somehow the OS should start-up.
Basically I dont get a write error, it's just that the error comes up when the radio is being written, hence I think that there is something wrong with the radio set-up that I have now on the phone...
Maybe somebody knows how to flash the system from scratch using only fastboot in cmd (having the right zip or img files properly signed), or maybe just the radio to start with.

This is not a Development question and thus should not be posted in the Development forum.
Thread reported.

have a look here. i do not know if it helps though. and i know it is not a Desire
http://forum.ppcgeeks.com/htc-hero/118035-error-110-ruu.html
i also found this. sounds familiar? not for desire but might do the trick http://forum.androidcentral.com/htc-hero-roms-hacks/13171-110-error-ruu-1-56-fix-100-unroot-too.html
sorry if i wasted your time.

acolwill said:
This is not a Development question and thus should not be posted in the Development forum.
Thread reported.
Click to expand...
Click to collapse
Well, I thought that as various solutions to root the phone, to get past different restrictions in the OS, etc. were discussed here, it might be a good thing to develop a way to bring back to life a OS being in this situation like mine...come on...

mariosraptor said:
have a look here. i do not know if it helps though. and i know it is not a Desire
http://forum.ppcgeeks.com/htc-hero/118035-error-110-ruu.html
i also found this. sounds familiar? not for desire but might do the trick http://forum.androidcentral.com/htc-hero-roms-hacks/13171-110-error-ruu-1-56-fix-100-unroot-too.html
sorry if i wasted your time.
Click to expand...
Click to collapse
Thanks anyways man, I looked at that already, but cant get it done as I dont have adb commands available in cmd, only fastboot. Dont worry about waisting my time, I really want that these days

I had the same problem. Passed the device in service center. Changed the motherboard under warranty. It took one month's time.

but to get adb you need to download and install android sdk. look here http://developer.android.com/sdk/index.html system dependands download.
install it here are instructions on how to use if you aren't familiar with.
http://www.londatiga.net/it/how-to-use-android-adb-command-line-tool/
for anything else just use google.
i'm pretty sure that your device is fixable and you can fix it without any service center. cheers and post what ever happens.
popepope said:
Thanks anyways man, I looked at that already, but cant get it done as I dont have adb commands available in cmd, only fastboot. Dont worry about waisting my time, I really want that these days
Click to expand...
Click to collapse

I know how to use adb commands...pretty new to android and everything, but lately I roamed a lot through various things about it and learned a lot.
The problem is that adb doesnt list my phone when I run adb devices, it shows only when I run fastboot devices, I am sure you know what I mean...hence I cannot push any files to the phone, etc., at least not using adb in cmd.
That's actually the problem, that I cannot get adb to work, I only have fastboot commands. At least the way I see it now the question is how can I work with the phone to fix it just by having fastboot access in cmd.
I searched quite a lot various forums, etc, but I never came across a solution that will get things going just by having fastboot in cmd (without adb working). Maybe somebody here will come up with some magic trick...

Nerten said:
I had the same problem. Passed the device in service center. Changed the motherboard under warranty. It took one month's time.
Click to expand...
Click to collapse
How did you end up having this problem, just like that or after some update, flash, etc?
Thanks!

have a look here mate http://forum.androidcentral.com/htc...9-bricked-my-evo-but-there-away-un-brick.html

same story unfortunately, doesnt apply to my problem. in the link they use a terminal emulator, but I cant use that as it doesnt work...it's basically an alternative to using adb directly in cmd, and this doesnt work for me.
if I am to get adb functionality back, then I'm done with the problem in 5 mins probably...
thanks anyways, keeping the hope alive!

sorry idf i don't underdstand, but if you have fastboot working in your device and sdcard also then you should be able to push files to device via fastboot making as clean installs as possible.so if your device is picked up by command line type fastboot to see command list. i'am a bit comfused. pretty sure you should fix it through fastboot though.
popepope said:
same story unfortunately, doesnt apply to my problem. in the link they use a terminal emulator, but I cant use that as it doesnt work...it's basically an alternative to using adb directly in cmd, and this doesnt work for me.
if I am to get adb functionality back, then I'm done with the problem in 5 mins probably...
thanks anyways, keeping the hope alive!
Click to expand...
Click to collapse

right, I can run 2 things with fastboot in cmd: (name of the files just an example)
1. fastboot update update.zip
here I get that the archive doesnt contain android-info.txt or android-product.txt
2. fastboot flash update.img
here i get signature verify fail
for example, fastboot erase radio says FAILED, remote: not allowed
there are some fastboot commands related to the kernel and some others, but dont know how to make use of them for my problem.
sd card is accesible for sure and it is a goldcard.
I saw some linux/ubuntu methods to simulate adb usage in cmd, but I dont think it will work...will try to find an ubuntu image and mount it under windows, but dont have time now...
anyways, thanks to everybody for the suggestions and interest, maybe we'll crack it some day

You need to use an official RUU zip image - i.e. a PB99IMG.zip. Not an update.zip.

Htc desire hd - sd card unavailable

Hi guys and girls.
New to XDA but not to Android.
I need some help big time as I'm totally stuck and I'm about to send my phone to "will it blend".
Long story short my memory card will not read when inside the phone all I get under phone storage is "unavailable" with mount being greyed out.
HTC DESIRE HD 2.3.3 (Not Rooted)
Things I have tried:
Factory reset soft/hard both through phone and through power + vol down.
Tried two different mem cards both coming up in storage as "unavailable" the general fix seems to be formatting in fat32 on desktop pc I have done that for both cards (which are both readable on PC) and have even tried formatting through command prompt still no luck.
read alot in ADB/fastboot as it is something I'm abit unfamiliar with saw that users where able to restore sd card function by installing adb then running command prompt: "fastboot oem enableqxdm 0" I get a message saying it was successful I reboot guess what...same problem. One thing I have noticed is if I type "adb shell" I get "Daemon started on port 5079". (I have enable debugging) followed by device not found. have tried two diff usb cables both work with my S2 on either media faceplate or backplate usb ports still no luck. Trust me on this one guys I have searched far and wide and I'm just about read to quit on this. I'm at a dead end any advice would be awesome.
I've tried to resolve the adb method by installing various drivers (running windows 7pro 64bit) the issue I seem to get is that windows doesnt like the drivers Im trying to assign so im forced into have to update them manually through "let me choose a driver from location" blah blah blah...
There is a system update available which may possibly fix my issue however suprise suprise I can't download the update without having an sd card. I have even tried downloading a HTC sdmount widget whether Im downloading the wrong one I dont know? I have got HTC sync installed as others claimed this helped windows detect the correct drivers but then technically speaking its not an ADB interface?? just like to point out that both of the sd cards work flawlessly in my s2. anyone who can help me will get paypal'd a beer!
Thanks
Seb.

OK, I had same problem with my Desire S. I'm running Win7 64bit as well. I un-installed HTC sync, including the drivers. Control Panel>Programs & Features. I then download the latest HTC sync. Went back to Programs & Features and un-installed HTC sync but, left the drivers. Rebooted PC and Win7 picked up Desire S.
Hope this helps

How old is your phone? Depending in which country you are in you may still be under warranty.
Try cleaning the contacts?
Not too sure if you can mount the sd card on phones that are not rooted, or if you have the hboot option/recovery. Fastboot turned off, phone off, then press and hold the down volume button and while pressing it down, press the power button.
If you are not sure what you are looking at do not play around with those options, and it may not work. Not sure if you get those options if you are not rooted.
Do not root your phone, it is improbable it will help, and chances are, it may cause more problems than help.
First option, find out about the warranty.
Edit: just noticed you can boot into hboot. Not too sure if you have the option for recovery and even less if you get the option to mount sd card through there.
2nd edit: I'm not responsible for bad advice. I still haven't had my second cup of coffee
3rd edit: to find out if the adb is working properly and you got the htc sync installed type in whatever the command is in adb to see if it detects your device.
However, try cleaning the contacts and find out about the warranty.
Sent from a dream.

eloquence intshe
Thanks for the reply.
Hehe dont worry you can have some of mine I'm on the 4th cup thats how stressed I am getting with this. Just trying Taysider's method for trying to re-enable the sd card function. I have disabled fastboot using your method so is there a way of mouting sd in recovery? because Im sure I may have tried that already and all I got was an icon of a phone with a red exclamation mark infront of it?
thanks

3rd edit: to find out if the adb is working properly and you got the htc sync installed type in whatever the command is in adb to see if it detects your device.
However, try cleaning the contacts and find out about the warranty.
Sent from a dream.[/QUOTE]
How do I clean the contacts on the sd reader? it doesnt look very accessible unless I remove part of the housing? also what command prompt do you recommend I try first? like I said I tried "adb shell" and got no device found I'll update in a second as soon as I have tried this I have just uninstalled htc sync now all I need to do is assign driver to "android 1.0" in device manager then I'll take it for a spin.
Thanks dude

Ironman MarkV said:
Thanks for the reply.
Hehe dont worry you can have some of mine I'm on the 4th cup thats how stressed I am getting with this. Just trying Taysider's method for trying to re-enable the sd card function. I have disabled fastboot using your method so is there a way of mouting sd in recovery? because Im sure I may have tried that already and all I got was an icon of a phone with a red exclamation mark infront of it?
thanks
Click to expand...
Click to collapse
Re-read my previous post, there' another edit.
Thing is, Im not too sure what options you get nor l, well, anything related to non rooted phones. Do not root your phone as I mentioned previously. Mainly because first you ought to find out if you are still under warranty. If you are, send it to them.
Exclamation mark? Do a search, there were a few threads talking about that a few weeks back, but I believe it was about something else entirely, people effen up their phones trying to root.
From here on, the best advice I can give you is step back, take a break, continue later. There is probably too much info in your head right now.
1- see if adb can detect your phone.
2- try cleaning the contacts, do a search cause I can't remember if the cleaning of contacts was also for the sd card or only the wifi antenna.
3- Check your warranty, I can't stress this enough.
4- Coffee is kicking in
5- Check if you can detect the sd card through recovery. My assumption is that recovery works something like safe mode in windows, only an assumption.
6- Wait till someone more knowledgable than myself joins in. Chances are it would either be darunion, gleviatan or some chap who's nick I cant remember but starts with an M.
@guyinthecorner: you can skip this one - and I'm still waiting for that flashable zip.
Sent from a dream.

Teichopsia said:
Re-read my previous post, there' another edit.
Thing is, Im not too sure what options you get nor l, well, anything related to non rooted phones. Do not root your phone as I mentioned previously. Mainly because first you ought to find out if you are still under warranty. If you are, send it to them.
Exclamation mark? Do a search, there were a few threads talking about that a few weeks back, but I believe it was about something else entirely, people effen up their phones trying to root.
From here on, the best advice I can give you is step back, take a break, continue later. There is probably too much info in your head right now.
1- see if adb can detect your phone.
2- try cleaning the contacts, do a search cause I can't remember if the cleaning of contacts was also for the sd card or only the wifi antenna.
3- Check your warranty, I can't stress this enough.
4- Coffee is kicking in
5- Check if you can detect the sd card through recovery. My assumption is that recovery works something like safe mode in windows, only an assumption.
6- Wait till someone more knowledgable than myself joins in. Chances are it would either be darunion, gleviatan or some chap who's nick I cant remember but starts with an M.
@guyinthecorner: you can skip this one - and I'm still waiting for that flashable zip.
Sent from a dream.
Click to expand...
Click to collapse
Lol, already saw your username and was like 'Yup, problem solved ;-)'
Flashable zip is being a pain in the rear, should have it soon (reading a crap-ton of tutorials to help me)
Sent from my Desire HD using Swype beta for Android!