pc wont find my gs3?? hardwear id not found?? - Sprint Samsung Galaxy S III

Hello I just traded my evo 4g lte for the gs3!! im super happy but I installed the drivers and still when I plug the phone into my pc its says hardwear id not found.. windows cant find bla bla.. Im new to samsung how can i fix this?? Did I get burnt? Thanks ok this is what it says.. Hardwear id missing.. Windows cannot id the device plugged into the samsung mobile usb composite device? And i installed the drivers

Please search before starting a new thread: http://forum.xda-developers.com/showthread.php?t=1997915

Hi, I had a similar problem where my gs3 wouldn't show up as an mtp device on my win 7 laptop even tho it had b4 & even after going thru the whole driver reinstall process.
I almost gave up after googling the hell out of this issue, but then I happened upon a post somewhere recommending to shut the phone down, pull the battery out, & then replace it/turn it back on.
Alas, this did the trick. Don't know what caused it or why this worked but it wasn't just dumb luck, it fixed the problem.
Sent from my SPH-L710 using Tapatalk 2

Related

XDA Exec Now Zombiefied After Failed Upgrade. Is It Terminal

You've poss heard this un afore. But so far .. this `un aint been resolved, readers. Just got me a XDA Exec and daftily `upgraded' the ROM to exactly the same one as already installed (d'oh!). Aye .. but what happened was that the process failed just as the installation ended .. wih a communication error. Twixt PC and XDA. When I came to reboot .. the unit .. he dead!. The only spark of life is to hard reset. Do this . and you get the bootlaodaer screen showing the Serial 1.oo logo and Press X to quit and 0 to restore. You press 0 .. it just flickers the wee Red power light fleetingly .. but .. he dead, man!. And heres where the quandary comes in .. if you connect up .. even whenin the Bootloader screen. the unit is not seen as owt .. and Windows says its not being recognised when you plug it in .. so ActiveSync wont work and the ROM Updater cant see it .. failing before even trying to install. So there we have it. The unit has no ROM in it. Like a PC without a BIOS. Kinda Catch 22. ITs a dead unit ... only shwoing any life when yu do the hard reset. Shows a Bootloader screen. So do a soft reset? You get a dead unit again. If ou take out the battery and put on mains power ... then the red charge light comes on PUt in the battry.. unit goes blank again. Someone said you can link two XDAs together and do it that way. Really? Then how?. And how DO you get the PC to see it as a XDA?. Most infuriatingn. So really hardware wise its pristine .. its a software thingy!. If you know or even know a man who knows .. then point him/her this way and lets get this baby (XDA EXEC) back to post - resuscitated state Please. Cheers y'all in anticipation and sorry if this subject has already bin solved. Ive seen like-letters but no actual `fix' .. personally I think its return to Taiwan and get their EPROMmer guys to look into it. Can you help?Ta Bruce E Bonuspoints
Think you can edit your post and at least separate it into paragraphs?
Just some curiosity. I'd be willing to help, but I'm too lazy to read it like that.
If you bootup the XDA without the usb cable connected, when it goes into bootloader mode, it should say serial, if you then plug the usb sync cable, it should change to usb on the screen.
at this point, you want to run the rom upgrader software, it might take more than one try to get it to do the biz, I know, cause it took me three times via the sync cable when I tried to upgrade the rom via bluetooth (a mistake I won't be doing in a hurry ), thinking the cable connected was the usb sync cable and not the mains cable.
this might be of some help too http://forum.xda-developers.com/viewtopic.php?t=36115
p.s. take a deep breath and don't panic.
*edit* also found this, which might also help http://forum.xda-developers.com/viewtopic.php?t=37135
Exact thing happened to a friends JASJAR, this is what happened:
1. Same as above and it seems it corrupted the USB drivers so:
1.a. removed the USB drivers in device manager
1.b. rescanned for hardware changes to reload new USB drivers
2. Have to uncheck USB in ActiveSync Connection Settings
3. Hard reset your Universal till SERIAL shows
4. Plug the Universal and wait for SERIAL to change to USB
5. Unpack the ROM update to a directory
6. Delete all .nbf files except Radio_.nbf
7. Run the update (this will update radio only)
8. after Update, Hard reset ( __ + __ + Reset hole)
9. this should revive your Universal.
Then you can update normally again.
Don't forget to re-check USB in ActiveSync connection settings to enable active sync to work
Goodluck.... Just update us
Cheers for the responses .. EXEC lovers!. And sorry about the non-presence of paragraphs to the reader who doesn't like long sentences.. but thats nonstop streams of conscienceness f'yuz!
There .. happy now?. :twisted: Right .. will now nip off and read the links and take up the advice of the chaps who jolly well had the good decency to reply .. I'll let you know .. soon! Here goes, Ronnie! ...... :shock:
Cheers for the responses .. EXEC lovers!. And sorry about the non-presence of paragraphs to the reader who doesn't like long sentences.. but thats nonstop streams of conscienceness f'yuz!
There .. happy now?. :twisted: Right .. will now nip off and read the links and take up the advice of the chaps who jolly well had the good decency to reply .. I'll let you know .. soon! Here goes, Ronnie! ...... :shock:
:lol: Thanks to Messrs. WYTEY and in particular Mr. Jorgee ... MY XDA EXEC has risen from the dead! Thats right .. its back!. I WAS going to write and say it no go from Serial to USB ... mister!. But then tried it on missus's laptop .. it gets recognised.. but not on daughter's PC. Why Winston?. Then d'oh!. And Double D'oh!. The USB cable I am using is off an old memory card reader .. which cable is probably a bit crap. So I used the dedicated one... and .. voila! Back to life .. using the Radio ROM only. Tried the full install .. it no want to know .. back to lifelessness. Tried again .. this time its full and happy as it were. So once again great thanks directed to the Johnny JORG bloke and the WYTEY William whoc came to my assistance. You have just got me £500 of kit back!. I am writing to the Queen to see if you can both be knighted. I am also Royalty .. at least I think I am .. only today I cut this bloke up at a junction in my car and he called me a `Count'!. CHEERS YOU XDA HEROES!!!!!!!!!!
:lol: no probs
Glad to have helped in the resurrection of your phone. This wasn't the first time so I was kinda familiar with the process. Good thing that it was recognized in the laptop. How about now? Does your computer recognize it? My friends USB port of the PC suddenly wento into UNRECOGNIZED USB DEVICE mode mid-upgrading. Don't know what caused the problem though.
The unit has the `hump' now and then but now for general file transfers the cheap cable works fine . .when you do serious stuff like ROM upgrades.. tis the official cable. So its being recognised now and ActiveSync is fine. I do have probs finding a decent PDF viewer.. ClearVue and Adobe still cant display/flow the pages right .. never worked on the Nokia 9500 either really... and also want to know if its poss to use the videocam in MSN Messenger Mobile? But now.. its fine. it works .. and the upgrade fully happy! CHeers again!. Now . .whens the next upgrade coming? :roll: Aye!

USB Sync Problem

Hi all,
my TMO-MDAIIIc stopped syncing over usb cable!
I do not have any clue why!
Last thing i remember i installed the OpenVPN-Client!
I did this before on Windows Mobile 5 without problem.. So i presume it's not caused by OpenVPN!
Nevertheless i wonder if anyone has experienced this as well? I tried to connect the device to several computers without even ActiveSync recognizing it. But loading the battery over USB still works!
I also do not get a "Network Interface" if i connect the cable.
I searched several forums and find out there were similar problems, but unfortunately no solution for me...
It seems not to have something to do with the "Notification deleted" problem..
As i can see several replog.exe notifications. Also the one about RS232 Connections... Is there any other Notification missing maybe?
I also tried to play with the USB-to PC option in the settings menu. No effect.
Im totaly clueless i can sync via bluetooth, and irda, and of course wireless (gprs).
Any help would be much appreciated!
Cheers!
Syn
My phone stopped working the same as yours about 6 months ago. I recently found out that it was because i charge my phone in my car, which can damage the USB Interface Board in the phone. (usually when you have the phone on charge, and then start the car, causes a spike in the current).
As far as i know, the only way to fix it is to send the phone back to the supplier, who will replace the board under warrenty.
Assuming you have the same problem
Hi, thanks for reply!
could be true! I also charge it in the car frequently... I didn't payd a lot attention to if i plug it beofre starting the car or after...
So my last try now seems to be a "hard-reset".
I'll let you know if it fixes the problem.... If not....
I may need to "downgrade" the phone b4 sending it right?
Cheers!
Syn
Synablade said:
Hi, thanks for reply!
could be true! I also charge it in the car frequently... I didn't payd a lot attention to if i plug it beofre starting the car or after...
So my last try now seems to be a "hard-reset".
I'll let you know if it fixes the problem.... If not....
I may need to "downgrade" the phone b4 sending it right?
Cheers!
Syn
Click to expand...
Click to collapse
yeh, its probably a good idea to put the original ROM back on
What's really bugging me is:
Why is it still "loading" the battery after damage to the USB-Circuit??
Anyway.. i did the hardreset, and guess what...
no effect... my problem now is.. if usb stopped working.. how do i flash back to original rom? :->
bluetooth? *shudder*
Cheers!
Syn
hi,
I always clear the option usb to pc.I think this wil solve you problem
settings>connections>usb to pc
Cheers,
zaza
Synablade said:
What's really bugging me is:
Why is it still "loading" the battery after damage to the USB-Circuit??
Anyway.. i did the hardreset, and guess what...
no effect... my problem now is.. if usb stopped working.. how do i flash back to original rom? :->
bluetooth? *shudder*
Cheers!
Syn
Click to expand...
Click to collapse
yeh, same as me i havent been able to flash a cooked ROM to mine at all. You can change the ROM by using the MicroSD, as long as you are USPL unlocked. There is a section in the Wiki about how to do it.
You cant change the ROM using bluetooth, caus half way thru flashing, whats gonna control the bluetooth??!
The Battery still charges caus the battery charging circuit is seperate to the USB control circuit
Are you guys running XP on your comp/laptop? have you turned off your firewalls? i had problems syncing on my laptop with xp, now i use my comp, but i found if i removed firewalls all was ok. if you have tried reflashing, or if you havent flashed any new software if you have tried re-sinstalling active sync, try the above, im sure its somethign simple
patterns said:
Are you guys running XP on your comp/laptop? have you turned off your firewalls? i had problems syncing on my laptop with xp, now i use my comp, but i found if i removed firewalls all was ok. if you have tried reflashing, or if you havent flashed any new software if you have tried re-sinstalling active sync, try the above, im sure its somethign simple
Click to expand...
Click to collapse
I've tried everything... WinXP, WinXPx64, Win2000, Win Vista, active sync V.3-4.5... the only answer is to send the phone back to T-Mobile, they will fix it under warrenty tho, so it aint so bad.
hi thank you all for your replies!
unfortunately i think mugglesquop is right,
the device died from power overflow from car adapter...
funny thing here is: i use a motorola car adapter all the time! no problems.. then i changed to a tmobile provided adapter! And now it seems that tis one is vulnerable to power highs! Great!
You know what ? I love t-mobile for providing "cheap" "crappy" hardware!
actually im downloading the original rom i found and i will try to flash it back via sdcard. Then i will send it in!
Cheers!
Syn
What rom are you using ?
I had the same problem & i was using B&B4.3. It took me a couple of days of trying before i could get an activesync connection. I then flashed O2's mobile 6 Rom & hey presto everythings working again (now trying different rom). Not sure it was the Rom as only a few people seem to have experienced the problem. So it could have just been a coincidence. Also i would assume that the problem should be instant rather than after a few days of having the rom flashed. Have you tryed jiggling the usb cable about in the phone to try & get a connection ?
Synablade said:
hi thank you all for your replies!
unfortunately i think mugglesquop is right,
the device died from power overflow from car adapter...
funny thing here is: i use a motorola car adapter all the time! no problems.. then i changed to a tmobile provided adapter! And now it seems that tis one is vulnerable to power highs! Great!
You know what ? I love t-mobile for providing "cheap" "crappy" hardware!
actually im downloading the original rom i found and i will try to flash it back via sdcard. Then i will send it in!
Cheers!
Syn
Click to expand...
Click to collapse
lol, gotta love T-Mobile... No WM6 update as well
Good luck getting ur MDA sorted!

Dead Sprint 6600

I need help reviving my Sprint 6600. I tried upgrading with HA_SPCS_13600_113_00140_6600 a few moments llater it turned restarted and stayed on USB v1.02 or Serial v1.02. Ive tried pressing record+power+reset and record+camera+power+reset and some other combinations but it remains in the same screen. I cant connect to to activesync. Im using vista ultimate on a Laptop. I just need to know if anyone has been able to fix their Sprint 6600 an thus be hope for my device or should i just use it as a $350 paper weight.
Any feed back would be welcomed. Thank you.
thanks to this website i was able to fix my pda. if anyone has problems please please read through the tutorials that corresponds to your device.

[Q] DFS not recognizing Sprint Samsung Galaxy S3 - Flashing to Verizon Prepaid

Can someone help me with this? I think i've tried just about everything.
Specs:
sprint samsung galaxy s3 - phone
CDMA Tools DFS Demo version 4.0.0.5 - software
windows 7 ultimate 64 bit
Problem:
DFS seee the 'samsung mobile usb serial port' in the upper window of the port manager, but it does not appear on the 'devices online' portion. i have successfully had those ports appear there, but its like a flash in the pan on and off, and i have successfully flashed the phones but my goal was unsuccessful. since then DFS has stopped recognizing my s3.
I've put the galaxy into diag mode ##DIAG# and set it to CDMA Modem, and DM + MODEM + ADB for USB setting.
i have/had samsung galaxy s3 driver installed as well as generic samsung USB drivers installed.
I've done a combination of uninstalling and reinstalling them with no luck.
i've disabled kies.
i've factory reset the s3 and tried DFS with no luck.
i've uninstalled DFS and reinstalled different version with no luck.
i've gone into the registry and reset the port com values with no luck.
============================================
what i'm trying to do:
Get sprint s3 onto verizon prepaid. i have the following:
samsung gusto 2 (with 60$ of prepaid minutes)- donor phone
verizon fascinate s1 - dmu donor
sprint samsung galaxy s3 (naturally)
and i cant seem to get data to work on the s1 (calls and text work). i tried and tried but i'm having some major issues.
it was this thread's instructions i was following:
http://forum.xda-developers.com/showthread.php?t=1473141
and this thread
http://forum.xda-developers.com/showthread.php?t=1210240
i'd be very grateful for any input here
thanks
BUMP!!! Please I am having the same issue. I want to flash a Sprint version to Cricket Wireless but the phone has stopped being recognized, it only show up as a com port but there is no actual recognition of the phone by DFS, QPST, even CDMA workshop doesnt connect to it. Please helP
Ok its working for me but I suspect this is just temporary. Ok mine is a sprint s3 so I don't know if this works with other phones but instead of ##diag# I used *#7284# and I also plugged it into another usb port on my comp. I'm pretty sure our problem will occur again but for now it's working.
Sent from my SPH-L710 using xda app-developers app
Help Pleaseee!!!!!!!!
zen_phones said:
can someone help me with this? I think i've tried just about everything.
Specs:
Sprint samsung galaxy s3 - phone
cdma tools dfs demo version 4.0.0.5 - software
windows 7 ultimate 64 bit
problem:
Dfs seee the 'samsung mobile usb serial port' in the upper window of the port manager, but it does not appear on the 'devices online' portion. I have successfully had those ports appear there, but its like a flash in the pan on and off, and i have successfully flashed the phones but my goal was unsuccessful. Since then dfs has stopped recognizing my s3.
I've put the galaxy into diag mode ##diag# and set it to cdma modem, and dm + modem + adb for usb setting.
I have/had samsung galaxy s3 driver installed as well as generic samsung usb drivers installed.
I've done a combination of uninstalling and reinstalling them with no luck.
I've disabled kies.
I've factory reset the s3 and tried dfs with no luck.
I've uninstalled dfs and reinstalled different version with no luck.
I've gone into the registry and reset the port com values with no luck.
============================================
what i'm trying to do:
Get sprint s3 onto verizon prepaid. I have the following:
Samsung gusto 2 (with 60$ of prepaid minutes)- donor phone
verizon fascinate s1 - dmu donor
sprint samsung galaxy s3 (naturally)
and i cant seem to get data to work on the s1 (calls and text work). I tried and tried but i'm having some major issues.
It was this thread's instructions i was following:
http://forum.xda-developers.com/showthread.php?t=1473141
and this thread
http://forum.xda-developers.com/showthread.php?t=1210240
i'd be very grateful for any input here
thanks
Click to expand...
Click to collapse
so did you get 3g working?? Im stuck at this point. Sprint s2 flashed to verizon with working talk and text. Mc gusto 2 and i need that gin and juice. Lol. Naw.. But help me my friend.... Thanks in advance.
MajorCinema said:
so did you get 3g working?? Im stuck at this point. Sprint s2 flashed to verizon with working talk and text. Mc gusto 2 and i need that gin and juice. Lol. Naw.. But help me my friend.... Thanks in advance.
Click to expand...
Click to collapse
Still not working. Try following the thread nevell posted on flashing spring s3 to Page plus. And don't let this signature fool u I'm posting via wifi lol
Sent from my SPH-L710 using xda app-developers app
Man its working my nerves
zen_phones said:
Still not working. Try following the thread nevell posted on flashing spring s3 to Page plus. And don't let this signature fool u I'm posting via wifi lol
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Already tried it and a million things.
Looks like we all could use an expert here. IS THERE A SPRINT S3 TO VERIZON PREPAID DOCTOR IN THE HOUSE?!?!?! HALPPP
Sent from my SPH-L710 using xda app-developers app
Oh btw on the Sprint s3 when putting it into diag mode I used the pda instead of modem, which is different from what I been doing and from what I understand to be the correct way but it worked for me (this time). And of course under usb settings pick the bottom one.
Sent from my SPH-L710 using xda app-developers app
bountyboy8
PM me if you're still having the problem with D F S I may be able to help. [email protected]
you guys aren't gonna believe this but this worked for me. i am rarely able to get dfs and my sprint s3 to read on my laptop (i've had luck lately on my desktop...randomly), but i plugged in a usb hub/splittler thing then connected my s3 to that and now its reading and able to write in diag mode LOL.
annndddd its not able to read the port again. this just doesn't happen with DFS it happens with cmda ws and other programs. its a windows thing.
does anyone have a working consistent solution for this?
zen_phones said:
annndddd its not able to read the port again. this just doesn't happen with DFS it happens with cmda ws and other programs. its a windows thing.
does anyone have a working consistent solution for this?
Click to expand...
Click to collapse
are you using com port 2 or 3?
try that if you are not.
then open dfs/manage/hit reset system ports.
close dfs but release ports than reopen from app tray and
see if it recognize.
MajorCinema said:
are you using com port 2 or 3?
try that if you are not.
then open dfs/manage/hit reset system ports.
close dfs but release ports than reopen from app tray and
see if it recognize.
Click to expand...
Click to collapse
its usually like com 6 or higher. i guess i'll try those. hey are u referring to an older version of dfs as far as resetting port? i remember seeing that on 3.1 or so. i'll go test that out
Hey buddy, I was working on flashing my brand new never-activated S3 and became across the same issue with DFS not recognizing my S3. Here is my 100% working solution!!!
Step By Step. Sprint GS3 Instructions.
1. Put your S3 out of DIAG MODE,
---DIAL##3424#
-Select PDA, MTP + ADB. Then press back button all the way to homescreen.
2. Reboot phone.
3. Once your phone is back, put your S3 in DIAG MODE again.
----DIAL ##3424#
Select CDMA MODEM, DM+MODEM+ADB. Then press back button all the way to homescreen.
Plug it in, give it a second. And tada, DFS detects your S3 as an online device. I'm guessing Samsung limited the number of times you can plug in your phone and read/write programming settings, to 1 per boot. By the way, I'm working on flashing it to Virgin Mobile USA.
Oh man! I'm gonna run home and try this! Thanks for the response either way!
Hay would u know how to flash the MiFi 2200 to verizon prepaid by any cance?
Alexander243 said:
Hey buddy, I was working on flashing my brand new never-activated S3 and became across the same issue with DFS not recognizing my S3. Here is my 100% working solution!!!
Step By Step. Sprint GS3 Instructions.
1. Put your S3 out of DIAG MODE,
---DIAL##3424#
-Select PDA, MTP + ADB. Then press back button all the way to homescreen.
2. Reboot phone.
3. Once your phone is back, put your S3 in DIAG MODE again.
----DIAL ##3424#
Select CDMA MODEM, DM+MODEM+ADB. Then press back button all the way to homescreen.
Plug it in, give it a second. And tada, DFS detects your S3 as an online device. I'm guessing Samsung limited the number of times you can plug in your phone and read/write programming settings, to 1 per boot. By the way, I'm working on flashing it to Virgin Mobile USA.
Click to expand...
Click to collapse
just got home and tried it...
holy crap it worked! on my desktop comp, but not on my laptop (i think its my laptop).
hey thanks for this. i hope it will work again when/if it starts to not detect it again. but for now im happy as a clam to be able to access it lol. thanks again
Sent from my SPH-L710 using xda app-developers app
tested again after failing to getting it into devices online, and did what you said and it worked!! looks like you are right about samsung diag allowance per boot. thank you!!!!
Alexander243 said:
Hey buddy, I was working on flashing my brand new never-activated S3 and became across the same issue with DFS not recognizing my S3. Here is my 100% working solution!!!
Step By Step. Sprint GS3 Instructions.
1. Put your S3 out of DIAG MODE,
---DIAL##3424#
-Select PDA, MTP + ADB. Then press back button all the way to homescreen.
2. Reboot phone.
3. Once your phone is back, put your S3 in DIAG MODE again.
----DIAL ##3424#
Select CDMA MODEM, DM+MODEM+ADB. Then press back button all the way to homescreen.
Plug it in, give it a second. And tada, DFS detects your S3 as an online device. I'm guessing Samsung limited the number of times you can plug in your phone and read/write programming settings, to 1 per boot. By the way, I'm working on flashing it to Virgin Mobile USA.
Click to expand...
Click to collapse
zen_phones said:
tested again after failing to getting it into devices online, and did what you said and it worked!! looks like you are right about samsung diag allowance per boot. thank you!!!!
Click to expand...
Click to collapse
I'm glad it worked, and sorry I don't know how to flash the MiFi device.
Whenever you can't get your S3 to work, just repeat the steps.
zen_phones said:
Oh btw on the Sprint s3 when putting it into diag mode I used the pda instead of modem, which is different from what I been doing and from what I understand to be the correct way but it worked for me (this time). And of course under usb settings pick the bottom one.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Remarkably enough, this worked. I can't stop wondering why on this phone setting Phone Utils to MODEM does not work and PDA works...
Thanks again.
None of you guys are going to like this answer...but it's the truth.
This phone is crap. Period.
You want to know the ONLY real trick to get it to read in CDMA WS, DFS, QPST, etc?
Factory reset. A lot. Then try different cables. Factory reset again. Then a different USB port. Then factory reset AGAIN. And if it still don't work.
You guessed it. Factory reset AGAIN.
Reboot your computer. Factory reset.
The reason is this...the highest percentage of the time, if the phone restarts & is recognized as the same COM port, it will usually not allow any software to connect to it.
I've flashed hundreds of phones...way more than I care to think about, and the SGS3 (Verizon and Sprint) is the absolute most troublesome. It will make you second guess everything, over and over and over again. The Verizon SGS3 holds a special place in my heart as the phone I absolutely hate the most. It used to be the HTC Thunderbolt because you have to reboot after you do damn near anything with diag mode, etc...or LG when you make changes in EPST for mms/data/etc on the handset itself constantly rebooting but NOooooooooooooooo the Verizon SGS3 makes me want to kill it...and the Sprint one is close behind...
They're just quirky. If you can't connect your Sprint one, factory reset it, switch it back to Diag mode & plug it in....you'll almost always connect the first time, unlike the Verizon version which almost always takes multiple resets before it decides to do something. The only thing the posts in this thread that have worked have in common, is that they cause the device to be recognized on a different com port (or as a different device) each time it's restarted.
But, once you make it to the programming phase, WATCH OUT! This thing is FAST and reliable. For added fun, when I do the Sprint ones, I'll also install the SlimRom and OMG...talk/text/data wheeeeeeeeeeeeeeeeeeeeeeeeeeeeeee & SlimRom is lightweight & MMS will work without 3rd party apps. FUN!
If this helped, or was the least bit entertaining, please click "THANKS"!
androidjunkie71 said:
None of you guys are going to like this answer...but it's the truth.
This phone is crap. Period.
You want to know the ONLY real trick to get it to read in CDMA WS, DFS, QPST, etc?
Factory reset. A lot. Then try different cables. Factory reset again. Then a different USB port. Then factory reset AGAIN. And if it still don't work.
You guessed it. Factory reset AGAIN.
Reboot your computer. Factory reset.
The reason is this...the highest percentage of the time, if the phone restarts & is recognized as the same COM port, it will usually not allow any software to connect to it.
I've flashed hundreds of phones...way more than I care to think about, and the SGS3 (Verizon and Sprint) is the absolute most troublesome. It will make you second guess everything, over and over and over again. The Verizon SGS3 holds a special place in my heart as the phone I absolutely hate the most. It used to be the HTC Thunderbolt because you have to reboot after you do damn near anything with diag mode, etc...or LG when you make changes in EPST for mms/data/etc on the handset itself constantly rebooting but NOooooooooooooooo the Verizon SGS3 makes me want to kill it...and the Sprint one is close behind...
They're just quirky. If you can't connect your Sprint one, factory reset it, switch it back to Diag mode & plug it in....you'll almost always connect the first time, unlike the Verizon version which almost always takes multiple resets before it decides to do something. The only thing the posts in this thread that have worked have in common, is that they cause the device to be recognized on a different com port (or as a different device) each time it's restarted.
But, once you make it to the programming phase, WATCH OUT! This thing is FAST and reliable. For added fun, when I do the Sprint ones, I'll also install the SlimRom and OMG...talk/text/data wheeeeeeeeeeeeeeeeeeeeeeeeeeeeeee & SlimRom is lightweight & MMS will work without 3rd party apps. FUN!
If this helped, or was the least bit entertaining, please click "THANKS"!
Click to expand...
Click to collapse
I understand your feelings bro. Actually I felt this way before until I finally figured it out, after a lot of hair pulling and gnashing of teeth. When you enter DIAG mode MAKE SURE PDA IS SELECTED, NOT MODEM. Then tap Qualcomm settings and select the option with RMNET. Voila, phone will be seen by ANY programming tool (CDMA Workshop, QPST, DFS). Hope this saves someone from a lot of hair pulling and gnashing of teeth.

Hardware ID Missing HTC EVO

Last week, I called the wonderful HTC customer support about this error I'm having with my HTC Evo (same as htc one x) and they basically told me that it was androids fault. So then, I tried finding contact information for android, but to no avail. So, I decided to give sprint a try and they told me to call HTC.
So now, I am at lost as to how I can fix this error that I am having wth my phone.
This is what happens:
1. I connect my evo to my computer
2. An error on bottom right side appears saying "Hardware ID is Missing"
In otherwrods, my computer can't detect the phone and I don't know why. I've reinstalled the HTC syc program, uninstalled USB drivers and reinstalled, uninstalled phone drivers, and I turn the developer mode on and off, but the problem persists. Is my phone defective??? I don't know!!!
Does anyone have a solution to this error that the multi billion dollar bafoons can't solve? If so please help me!!!!
This is my last resort or else I will go back to sprint to get an Iphone 5 because I know that the Iphone f*cking works.
Also, I am having a problem with my android navgiation app because of the error "map has stopped working." If anyone has a solutiont to this error then please help as well.
Thank you
Nah, I don't think the evo and the hox are similar in any way...you should've seen that. Also there is a complete section for the evo.
Sent from my IdeaTabA2109A using xda premium
As this is posted in forum of wrong phone I have closed it. I would have moved it, but as there are more than one EVO version I didn't know which one is the right for your phone. So please make a new thread in the right section.

Categories

Resources