I have searched through many microphone issue threads and none seem to help. I have a T-mobile htc g2 which has been unlocked and using my AT&T SIM Card. The phone works perfectly, except no one can hear me during phone calls. The voice search app works perfectly -text,navigation, etc. (so it should not be a hardware problem) which leads to a software problem. I have factory reset the phone several times, but it doesn't fix the problem. I have tried to flash ROM the phone, but I cannot get the phone to ROOT. I have tried Visonary (which failed since I have Android 2.3.4) and the xda wiki page, but my phone is not recognized by HTC Sync or adb.
Either way, I need help figuring out if I can ever fix the microphone issue this phone has. If there is another way to install a ROM, please let me know. I have been trying for days to get my phone rooted.
For more information:
I have tried both versions 3.2.20 and 3.0.5551 of HTC Sync (and neither worked). I've restarted my computer and the phone, turned off antivirus, followed HTC instructions; but nothing worked.
When trying adb, in the command prompt after typing "adb devices" I received this message: " 'adb' is not recognized as a internal or external command, operable program or batch file " To my knowledge I followed all the previous steps correctly, although I have windows 7 and not vista (but I still got to the same properties).
Anyway, please help me with any information.
UPDATE:
I finally rooted and downgraded the phone to 2.2 Android and then flashed a sense 2.0 ROM (although it was force closing applications), but it did not fix the microphone issue. People still cannot hear me during phone calls. So it seems that this must be a hardware problem, but if the mic works for some applications, is it the microphone that is broken? Or could it be something else?
Right now my phone is still in 2.2 Android since I may be flashing the Sense 3.0 ROM soon. But does anyone know what the problem could be and how to fix it?
if adb is not recognized then you are not pointed to it. you need to either
change directories in cmd and point it to the folder adb is in
or
change the path in system variables so when you type "adb" into cmd it will always find the path no matter where you are directing it
or if these steps are above your head,
open the folder adb.exe is located, hold shift and right click in the folder - then choose open command here
once in cmd, type
adb devices
if your phone is plugged in, debugging turned on, proper drivers installed you will see a serial number, that's good - continue
if you see waiting for device, then adb.exe is now working but your phone isn't being detected
if you get the same error as before you need to one of the other ways I mentioned
Sent from my HTC Vision using xda premium
demkantor said:
if adb is not recognized then you are not pointed to it. you need to either
change directories in cmd and point it to the folder adb is in
or
change the path in system variables so when you type "adb" into cmd it will always find the path no matter where you are directing it
or if these steps are above your head,
open the folder adb.exe is located, hold shift and right click in the folder - then choose open command here
once in cmd, type
adb devices
if your phone is plugged in, debugging turned on, proper drivers installed you will see a serial number, that's good - continue
if you see waiting for device, then adb.exe is now working but your phone isn't being detected
if you get the same error as before you need to one of the other ways I mentioned
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
That worked perfectly and I guess my phone is seen by adb. However, I realized the link of the xda wiki for the clockwork recovery is not working. I am trying to find another download link, but does anyone know where else you can download the clockwork recovery for htc g2?
go to the cyanogen wiki (just google it)
but I would recommend 4ext recovery, (you can google this too) it far nicer than clockwork for the vision
on a side note, find strawmetal's guide to rooting, its in pdf format and also has all the downloads needed
Sent from my HTC Vision using xda premium
demkantor said:
go to the cyanogen wiki (just google it)
but I would recommend 4ext recovery, (you can google this too) it far nicer than clockwork for the vision
on a side note, find strawmetal's guide to rooting, its in pdf format and also has all the downloads needed
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Thank you. I will try to strawmetal's guide first since the xda isn't working for me right now.
That Strawmetal's guide worked wonderfully! I finally rooted and downgraded the phone to 2.2 Android and then flashed a sense 2.0 ROM (although it was force closing applications), but it did not fix the microphone issue. People still cannot hear me during phone calls. So it seems that this must be a hardware problem, but if the mic works for some applications, is it the microphone that is broken? Or could it be something else?
the mic is part of the main flex cable, it is possible it cuts in and out because the flex is going bad and the mic is fine.
either way sounds like the only fix will be to replace your flex about 35~40 on ebay and 30~60min depending on how novice/pro you are
Sent from my HTC Vision using xda premium
demkantor said:
the mic is part of the main flex cable, it is possible it cuts in and out because the flex is going bad and the mic is fine.
either way sounds like the only fix will be to replace your flex about 35~40 on ebay and 30~60min depending on how novice/pro you are
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Thank you for your advice. I flashed the Virtuous Unity ROM and it fixed the microphone, somehow. However, if it shuts off (I pray it wont) I will try to see if replacing that will make a difference.
Mic Not Working in Calls Only
nds623 said:
Thank you for your advice. I flashed the Virtuous Unity ROM and it fixed the microphone, somehow. However, if it shuts off (I pray it wont) I will try to see if replacing that will make a difference.
Click to expand...
Click to collapse
I have qmobile noir a10 which is same as micromax a110.. From few days i have got this mic problem in voice calls. I can hear voice of ppl calling me but they cant hear me.. while microphone is working quite fine in sound recorder application.. i flashed custom ROMS but no success yet.. Plz help me!!
Related
wdfowty said:
I'm having a few issues using my bootcamp partition for this (in Parallels), following eugene and king_fyo's tutorials, and was wondering what it would take to root my MyTouch3gS using osx?
I am semi-familiar with ADB, and I have made the loop.sh script, but i'm stuck at that point.
Here are my main questions:
-How to you get the loop to stop? I have to quit Terminal app to stop it.
-Any other things to know? Tips? Success stories? Tutorials maybe (or even a quick and dirty how-to?)
Thank you for your time, and for not flaming the newb
Click to expand...
Click to collapse
EDIT: SOLVED!
So, I'm waiting for my Nexus one to come in the mail, and I think to myself, "Why not give rooting the slide another go?"
Worked second try. How's that for random....
So, here's how I made it work...Dunno if it was 'luck of the draw', but here ya go anyways...Hope it helps someone!
1. Instead of turning off the phone normally, I rebooted straight into recovery, with the phone being on first.
Code:
./adb reboot recovery
2. While rebooting, MANUALLY search for devices as soon as you can type it in, repeating rapidly (This made the difference for me).
Code:
./adb devices
3. You should catch the device in offline mode right before the recovery screen. Unplug device for 5 seconds or so, then plug it back in.
Code:
./adb devices
List of devices attached
HT05MPS02279 recovery
4. You should see your device in recovery, then you're good to go. If not try again.
How to you get the loop to stop? I have to quit Terminal app to stop it.
Click to expand...
Click to collapse
No, simply hit <control> c from inside the Terminal app to break out of the shell script.
Any other things to know?
Click to expand...
Click to collapse
Not really, it may take you several tries to get this as it did for people using M$ Winblows. I tried it about 20 - 30 times on XP and never was successful. After switching to my mac, I got root on the 5th try!
My suggestion is to follow Eugene's guide, it worked great for me! If you have problems, post them here and myself or others will try to help you.
Good luck!
wdfowty said:
I'm having a few issues using my bootcamp partition for this (in Parallels), following eugene and king_fyo's tutorials, and was wondering what it would take to root my MyTouch3gS using osx?
I am semi-familiar with ADB, and I have made the loop.sh script, but i'm stuck at that point.
Here are my main questions:
-How to you get the loop to stop? I have to quit Terminal app to stop it.
-Any other things to know? Tips? Success stories? Tutorials maybe (or even a quick and dirty how-to?)
Thank you for your time, and for not flaming the newb
Click to expand...
Click to collapse
So I set up my camera to record myself rooting my phone using OSX and a couple friends walked into the room. I got distracted explaining what it was I was doing and didn't make the how to. If I have free time tomorrow afternoon I can make a how to vid. My girlfriend just got her slide yesterday and I believe she wants me to root it.
it's exactly the same doing it in Mac OSX as doing it in Windows except you don't have to worry about drivers. Make sure you get android SDK for Mac OSX and that you put it somewhere that is in your PATH variable.
But if you feel more comfortable doing it from Bootcamp Windows partition -- by all means do that.
Don't boot camp it... lol
I'll be posting a Mac OSX version of Eugene's Root Method shortly.
sk8rbebop, Fordude, stangri, Thanks for the quick replies! Wasn't expecting anything so soon!
I think I have tried to press CMD+C to stop the script, must have been my problem. lol.
@stangri What do you mean by PATH variable? I have the Android SDK installed in my home folder...
@sk8rbebop That's pretty funny . I'm going to have a go at it right now, I'll edit this post with my results.
edit: I don't know if this is right, but I stop the script when I see the device in offline mode. But when I unplug device, re-plug and run ./adb devices nothing shows up. The same happens if I don't unplug.
edit2: Still nothing. adb never recognizes device after I stop the loop.
I threw up a guide. Hope it helps.
Don't shut off the loop until something displays under the devices.
Re: Question: How to root MyTouch Slide using OSX?
When u connect the slide to your mac and type "adb devices", do you see your phone listed? Crucial first step before moving on.
To make things a little easier for me, I put the sdk tools folder in my path so I could issue adb commands in any directory I want to.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
@sk8rbebop Read the guide and i'm still stuck at the loop. I'm having the same issues as earlier, the device will show for a little bit but right before the recovery screen shows, it dissapears. I was stopping the script once I saw the device, before it "dissapeared". Stopping the script after it dissapears does the same...
BTW, I've noticed that I need to start the adb daemon before I run the loop in order for it to even see the device in the loop. Odd.
@Fordude Yes, if I run ./adb devices when the phone is on I get my serial number and it says "device".
edit: I found that I am running an out of date SDK revision, so I am updating to the newest (revision 6), lets see if that makes any difference...
edit 2: No dice. Lame. Oh well I guess...Try try again. My mac seems to be determined not to let this happen
update: So, I'm getting a nexus. Thanks all for your help, happy hacking!
SOLVED
post removed
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.
Hi - I was trying to create a partition on my Sd card using the sdparted method. It gave an error after writing the commands to Shell. After that i rebooted my phone and it won't respond. It won't respond to the power Button, Recovery mood or any thing. If i'll plugin to my computer it would play a sound as if a device has been connected but it wont respond. I have pulled out the battery reinserted it but still its not functional or responsive. Can any one guide me any fix regarding the same.
Error I received was : /dev/mmcblk0p2 does not exis
what i followed was :
http://forum.xda-developers.com/showthread.php?t=905003
What version of cwm?
DoeBoi said:
What version of cwm?
Click to expand...
Click to collapse
Hi Thanks for your response. Latest one. 3.0.0.26
This might and might not..
I would format the sd card, then connect the phone to the PC and flash an ruu file.
Sent from my Desire HD using XDA App
People I am really looking forward to your replies over here Kindly help me out =)
Well I am just waiting to get my hands back on the phone and I am thinking of doing the same. Should i remove the SD card during that or i keep it in? I am flashing the RUU 1.32 one. Whats your suggestion?
I would format the sd card, insert it back into the phone and flash an ruu of your choice.
I had an issue where the screen stopped completely responding (wiping, switching roms and restoring the nandroid backup didn't work. I flashed 1.32 that's what I would recommend.
Sent from my Desire HD using XDA App
Hmmm Thank you I am going to do the same.
vyqas said:
Hmmm Thank you I am going to do the same.
Click to expand...
Click to collapse
No problems , let us know how it goes?
Sent from my Desire HD using XDA App
AndriodLover said:
I would format the sd card, insert it back into the phone and flash an ruu of your choice.
I had an issue where the screen stopped completely responding (wiping, switching roms and restoring the nandroid backup didn't work. I flashed 1.32 that's what I would recommend.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Sure i will, So other people can take the benefit too if it works out.
vyqas said:
Sure i will, So other people can take the benefit too if it works out.
Click to expand...
Click to collapse
Getting Error 170
vyqas said:
Getting Error 170
Click to expand...
Click to collapse
Sorry that was the only suggest I have, please other than that you can try different ruu.
Sent from my Desire HD using XDA App
AndriodLover said:
Sorry that was the only suggest I have, please other than that you can try different ruu.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
No need to apologize at least you replied. I am worried I am in love with this phone. And it is frustrating me and no body else is there to help me
hi, there...
plug your DHD into your computer and try adb
type
>adb devices
IF your device is listed, then type....
>adb logcat
and paste the message here (upload it on a .txt file) or just paste it here, your choice.
EDIT: does the HTC splash screen appear? (White BG with HTC logo)?, is that where it hangs?
CodeNameUnknown1 said:
hi, there...
plug your DHD into your computer and try adb
type
>adb devices
IF your device is listed, then type....
>adb logcat
and paste the message here (upload it on a .txt file) or just paste it here, your choice.
EDIT: does the HTC splash screen appear? (White BG with HTC logo)?, is that where it hangs?
Click to expand...
Click to collapse
it doesnt hang. As i mentioned it doesnt boot at all. Its totally unresponsive.
CodeNameUnknown1 said:
hi, there...
plug your DHD into your computer and try adb
type
>adb devices
IF your device is listed, then type....
>adb logcat
and paste the message here (upload it on a .txt file) or just paste it here, your choice.
EDIT: does the HTC splash screen appear? (White BG with HTC logo)?, is that where it hangs?
Click to expand...
Click to collapse
Nope no device is shown
The main concern i have is if the device is dead or has a faulty hardware which it should cuz i just tried to partition the sd card why does it make a connecting sound with the pc when attached without an SD card. It shouldnt. It needs to be worked out.
People I've read some awesome work of you guys here. I am sure you can easily break this issue down i need your attention.
have you tried adb logcat without typing adb devices? (it worked with me once, it didnt show up under devices but logcat worked)
Also, go to 'Device Manager' in windows. Do you get an unrecognized device? or a 'Android USB Device' or something of the sort?
EDIT: leave the sd-card out for now...or format it (not quick format) and put it back in
It is displaying an unrecognized device as QHUSB_DLOAD
so i sucessfully rooted my DZ but i have a problem with my computer now after i rooted, i have a fair idea of what caused the problem but dont know how to fix it.
CMD commands dont work on my computer (like ipconfig and ping etc) giving an error that "ip config" isnt a recognized as an internal or external command.
i think the issue is due to changing the "Enviroment Variables > Path" on my computer as it was in the guide i was following to make things easier, i removed the default path and replaced it with what i have now being
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\PROGRAMS\Other\HTC\SDK\platform-tools;C:\PROGRAMS\Other\HTC\SDK\tools;C:\Program Files\Windows Live\Shared
however i think there may be a command i deleted that i need.
if anyone has any suggestions please post your advice
thanks in advanced Penfold
Add this to it:
%SystemRoot%\system32;%SystemRoot%;
-Nipqer
Ouch, yeah ... what Nipqer said will fix the cmd problem but if there were any other paths set up by other applications you might run into more problems down the line. The guide wasn't stating to replace the paths but to add to them by adding '; c:\new_path\'.
You might just want to roll back with System Restore if there's a very recent one and then readd the adb path properly.
Sent from my HTC Vision using XDA App
Good Idea with system restore.
Looking at my Path the only other ones neccesary are possibly nvidia drivers.
-Nipqer
ok will do, so i dont have to make a new topic ill ask here...
does any1 know of any app that can give me notifications via the LED light.
ive tried LED me know but i dont think that works (the notification is always the same no matter what option you try)
I tried LED me know without any success on my G2. I currently use MIUI and LED notifications work for all apps.
Sent from my HTC Desire Z using XDA App
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!