Related
Hi all
I have a problem with my hero not being recognized by my PC. This happened after a weekend trip and i charged the phone with iphone USB adapter as i lost my one and now after returning from my trip i connect my hero to my PC to be greeted with the "USB Device Not Recognized" message.
Also my Amon_Ra recovery i used has been wiped and i cant get into recovery or install any rom at all.
I am thinking this might be the same USB brick that affected some Desire owners but i am not sure.
So please if anyone can help me, please do.
Thanks in advance.
fizzle101 said:
Hi all
I have a problem with my hero not being recognized by my PC. This happened after a weekend trip and i charged the phone with iphone USB adapter as i lost my one and now after returning from my trip i connect my hero to my PC to be greeted with the "USB Device Not Recognized" message.
Also my Amon_Ra recovery i used has been wiped and i cant get into recovery or install any rom at all.
I am thinking this might be the same USB brick that affected some Desire owners but i am not sure.
So please if anyone can help me, please do.
Thanks in advance.
Click to expand...
Click to collapse
this happen to me. What i did was switch my phone off, plug in the usb and switched it back on. then wait for windows to say it not recognised. then go to to device and printers and uninstall the drivers for the phone. Disconnect and reconnect the usb back to the phone and it it will pick it up.
Can you try booting in fastboot and tell me if that is recognized?
it still doesnt recognize it in fastboot
fc_Kuro said:
this happen to me. What i did was switch my phone off, plug in the usb and switched it back on. then wait for windows to say it not recognised. then go to to device and printers and uninstall the drivers for the phone. Disconnect and reconnect the usb back to the phone and it it will pick it up.
Click to expand...
Click to collapse
i have tried that and it doesnt help
fizzle101 said:
i connect my hero to my PC to be greeted with the "USB Device Not Recognized" message
Click to expand...
Click to collapse
Sounds like its just a driver issue. Have you tried plugging it in, when you get that message open DEVICE MANAGER,... Find the yellow "!", right click it, uninstall, unplug phone, reboot PC.
.... Then use BTDAG's [Guide] How to Setup Correct Hero Drivers (for x86 & x64 users)
I hav the same problem. In recover mode it works but then turn on the phone, there is no popup options as before. Tried around with drivers but didnt work either. But found a solution which is very convenient. I dont know if it works on other ROM versions but I'm on 2.1 (Villain10).
- Install extended control widget (dont remember where I got it but you can google, it seems I cannot find it on the market)
- Add this widget to the home screen: Menu/Add to Home/Widget/ Extended Control bar (you can choose the size from 1x1 to 1x4) then select "Mass storage" at the bottom, apply.
Now you have a widget to turn on/off USB storage. When you connect Hero to the PC, just click on this widget then the PC will connect to the SD card, and click one more to turn it off.
ok i will give that a try
crk23 said:
I hav the same problem. In recover mode it works but then turn on the phone, there is no popup options as before. Tried around with drivers but didnt work either. But found a solution which is very convenient. I dont know if it works on other ROM versions but I'm on 2.1 (Villain10).
- Install extended control widget (dont remember where I got it but you can google, it seems I cannot find it on the market)
- Add this widget to the home screen: Menu/Add to Home/Widget/ Extended Control bar (you can choose the size from 1x1 to 1x4) then select "Mass storage" at the bottom, apply.
Now you have a widget to turn on/off USB storage. When you connect Hero to the PC, just click on this widget then the PC will connect to the SD card, and click one more to turn it off.
Click to expand...
Click to collapse
that didnt work. o well i guess i am stock with the rom i have there.
fizzle101 said:
that didnt work. o well i guess i am stock with the rom i have there.
Click to expand...
Click to collapse
i've got this problem once and it was as simple as the cable was damaged...
i changed the cable and since then, everything works try that.
robocik said:
i've got this problem once and it was as simple as the cable was damaged...
i changed the cable and since then, everything works try that.
Click to expand...
Click to collapse
i have tried everything. changed the cable, used different pc but nothing works. i think is a hardware problem, something might be broken inside or something like that
Did you ever got this solved? I have the same problem only i use stock rom 2.1 Hero.. driving me nuts ...
baklap said:
Did you ever got this solved? I have the same problem only i use stock rom 2.1 Hero.. driving me nuts ...
Click to expand...
Click to collapse
No i havent and i gave up trying because i dnt think there is a fix for it. if yours is unrooted and the warranty is still valid you should consider returning it to HTC maybe they might replace it
got the same problem. Any solution so far ??
ddotpatel said:
Sounds like its just a driver issue. Have you tried plugging it in, when you get that message open DEVICE MANAGER,... Find the yellow "!", right click it, uninstall, unplug phone, reboot PC.
.... Then use BTDAG's [Guide] How to Setup Correct Hero Drivers (for x86 & x64 users)
Click to expand...
Click to collapse
Did you try that?..... You need to do the reboot PC/Laptop after uninstalling ALL HTC drivers! Then when you reboot PC, plug phone back in, should say "not recognised" again,... then follow BTDAG's guide. T'is definitely a driver issue!
tried flashing 3 roms, modaco, radug and now kimera... none working.
can connect in fastboot, it shows up in device manager as android 1.0
ive tried 3 different usb cables and 4 differet pcs, still there is no response on my phone !!!
using villian rom 10.0 rite now.
okay it boots up into fastboot and fastboot usb shows up on the screen in red,
BUT when i use the "adb devices" command in adb it doesnt show the device,
it is showing as android 1.0 in devices and printers (windows 7)
You need to use....
fastboot devices
....when your are in fastboot.
What happens when you go into your recovery, select "Toggle MS/USB" with USB connected to PC?
okay
fastboot devices command shows some serial number.
then i tried adb remount, it gave an error....
enabling usb-ms with cable attached gives no response
ok i think it might be USB driver like ddotpatel said but i am not sure.
i reinstalled my whole windows 7 to 32bit now instead of the 64bit version i was using before and today i just connected my hero to my PC and windows 7 did its thing and installed the drivers and finally my hero can mount the SD card in my PC again although i kept getting this can perform faster in USB 2.0 port or something like that i didn’t care as long as i can mount my SD card again.
now went into fastboot and used the fastboot device command and i could see my hero serial no. but when i try to flash the amonra recovery i got the permission error (i cant really remember). i tried flashing using the adb method but still no luck.
so i went to market and downloaded rom manager and used it to flash clockwork recovery and now i could boot to clockwork recovery.
from this recovery i can now flash any rom i want and although there are still a few more problems i am glad now that i can flash custom roms again.
the problem i can see so far but i can deal with is
1. i don’t think fastboot commands work even if the phone is detected.
2. SD card mounts at USB 1.1 speed. (i have tried different ports and cable but still the same thing and this is the ports i use for my N1, Desire and my other android phones with USB 2.0 speed)
PS: adb commands for pushing and removing apps is working.
Hope this can be helpful to those experiencing the same problem.
Instead of re-installing your entire OS just use usbdeview to remove the failing drivers.
Also remove any old HTC Sync installs and install the latest version.
Hi guys, was having a few problems with my phone and decided that I'd flash the stock ROM again.
Went into ODIN as you do, and as I was flashing the stock ROM, for some reason or another I heard the disconnect/reconnect noise that Windows makes when you remove a device then FAIL came up in ODIN.
Now my phone's stuck with a phone connecting to a computer on the charge screen, it can't go into recovery mode but it can go into download mode.
Tried connecting it to my PC in download mode, and even though I've got the Samsung USB Drivers installed I get the 'USB Device Not Recognized' message, which means I can't flash the stock ROM in ODIN anymore.
Does anyone have any advice? Thank you.
JoshS2 said:
Hi guys, was having a few problems with my phone and decided that I'd flash the stock ROM again.
Went into ODIN as you do, and as I was flashing the stock ROM, for some reason or another I heard the disconnect/reconnect noise that Windows makes when you remove a device then FAIL came up in ODIN.
Now my phone's stuck with a phone connecting to a computer on the charge screen, it can't go into recovery mode but it can go into download mode.
Tried connecting it to my PC in download mode, and even though I've got the Samsung USB Drivers installed I get the 'USB Device Not Recognized' message, which means I can't flash the stock ROM in ODIN anymore.
Does anyone have any advice? Thank you.
Click to expand...
Click to collapse
Try installing samsung kies. The usb drivers are included.
princeownt said:
Try installing samsung kies. The usb drivers are included.
Click to expand...
Click to collapse
I have it installed, and I installed the USB drivers from the soft bricked sticky in this section. Neither have helped.
Hi!
Hi, you guys install ADB on your system? And also USB debugging mode on the phone?
Should be turned on which can be done by going to Settings>Applications>Development and select USB debugging.
Try this, for me its works
MafiaDroid said:
Hi, you guys install ADB on your system? And also USB debugging mode on the phone?
Should be turned on which can be done by going to Settings>Applications>Development and select USB debugging.
Try this, for me its works
Click to expand...
Click to collapse
I can't even turn the phone on at the moment. Only thing I can do is go into Download mode.
Help
Try this, take out the battery, then press and hold the ON button for 7-10 seconds (the longer the better). Reinsert the battery, then press ON button to start it. This is a soft reset, and wipes the temporary memory and empties all remaining power in the circuits. This helps on many phones and even laptops that won't start properly or show anything on screen.
If this does not work, try the next step. Again, do as above. But after inserting the battery, do not turn the phone on, but press and hold the ON button and the HOME button at the same time for 7-10 seconds. This is a hard reset, and works best if done after a soft reset. Just be sure the battery has at least some juice in it and isn't empty. If possible, try with another battery if this does not work.
Hope this helps!
Try going to device manager, you will probably find your device as an unrecognized device, uninstall the drivers, unplug and then plug it again and see.
if the prblm is hard then do a fresh installation of kies,device etec etc.....but if u have ur device in the device list on pc then first uninstall it...if possible try recovery mode and reset...
I tried everything you guys have suggested and none of that worked. Anyone else got any ideas?
Try everything (and I mean everything) on the following list. Given the problems you've had & that you've already tried some of these things, I'd try another PC. And if it doesn't work first go on another PC, then go thru the list & try everything on the 2nd PC.
*Ensure Kies & it's processes aren't running in Windoze task manager. Kill them if they are.
*Try different USB ports; you must be using a 'powered' or mainboard port.
*Try different USB cables (particularly the cable that came with the phone if you're not using it now)
*Try different versions of Odin (search on here/Google)
*Uninstall Kies, reboot, redownload & reinstall it, reboot, try the flash again. Also run Windoze Update.
*And if all this fails, try a different PC.
Tried all the above and a different PC.
It didn't work. I could fix the phone if the computer would pick up that the phone's connected - it just doesn't.
Total Removal of KIES including registry entries .
Reboot PC install a new copy of Kies .
Phone backup data and factory reset .
Set phone to USB storage mode using the Samsung cable connect to PC and wait for Windows to find USB drivers .Remove cable reboot phone .
Start Kies connect with cable wait for Kies to find the phone .
Note USB Debugging OFF and cable connects to a direct motherboard port only .
Nothing then only further suggestion would be to Format the PC and start over with a clean Windows install .
jje
I can't turn the phone on, it's stuck on the phone, triangle, PC screen.
I've tried fresh installs on three different PC's.
JoshS2 said:
I can't turn the phone on, it's stuck on the phone, triangle, PC screen.
I've tried fresh installs on three different PC's.
Click to expand...
Click to collapse
That's a forced download mode.
Try a blind flash to a stock firmware from Odin while connected to your computer with the phone on this screen. Even if Odin doesn't seem to register that it's connected. I've heard of at least one person this worked for.
At this point, you really have nothing to lose by trying this.
Bit of an update, I plugged it in again and it installed some drivers and ODIN picked it up. Only for it to disconnect a few moments later, now it keeps disconnecting and reconnecting over and over but ODIN's not picking it up.
JoshS2 said:
Bit of an update, I plugged it in again and it installed some drivers and ODIN picked it up. Only for it to disconnect a few moments later, now it keeps disconnecting and reconnecting over and over but ODIN's not picking it up.
Click to expand...
Click to collapse
I know you said you tried a different cable, but that sounds suspiciously like a bad cable.
It's not the cable, thanks any way.
Update 2: I managed to get it to connect long enough to flash the stock Kernel. Still didn't reboot. Then I connected it again and flashed the stock ROM, which bricked it again. Then I flashed the stock kernel and it works!
However, there is a problem:
When the phone gets turned off, it constantly shows the charging battery icon with warning triangle and a thermostat next to it. I can't turn the phone on because of this unless I go into Recovery mode and reboot system.
Any ideas? Thanks.
JoshS2 said:
It's not the cable, thanks any way.
Update 2: I managed to get it to connect long enough to flash the stock Kernel. Still didn't reboot. Then I connected it again and flashed the stock ROM, which bricked it again. Then I flashed the stock kernel and it works!
However, there is a problem:
When the phone gets turned off, it constantly shows the charging battery icon with warning triangle and a thermostat next to it. I can't turn the phone on because of this unless I go into Recovery mode and reboot system.
Any ideas? Thanks.
Click to expand...
Click to collapse
Now this sounds like a faulty/dirty/bad usb port.
ctomgee said:
Now this sounds like a faulty/dirty/bad usb port.
Click to expand...
Click to collapse
This was my original thought and my reasoning for flashing a stock ROM in the first place!
JoshS2 said:
This was my original thought and my reasoning for flashing a stock ROM in the first place!
Click to expand...
Click to collapse
I in no way recommend this, and not sure I would do it if I ever started having this issue...
BUT - I have heard that some people faced with this condition have fixed it by physically moving the small wafer board inside the USB port with a precision screwdriver (gently!) to a more "centered" position.
If that doesn't work, look at replacing that part. Either via warranty service if you still have it, or a service center.
Hi guys!
I have tried to get Android onto my phone and I'm stuck. I'm using the files/instructions from this thread. (HSPL has been done and confirmed)
I noticed there's a similar thread, but they seem to be talking about a different problem, even though it happened at the same step.
Looking at the step-by-step list from that thread, I am stuck between step 10, step 11 and step 12:
- I successfully flashed RHODIMG.NBH
- Took out the battery, booted up with USB and there's the blue screen of the miniPoopLoader (tee-hee, it says poop ).
- Text scrolls by, ends with -- suspend --.
That's it, nothing happens. I can reboot, and it just goes there again. One of the snippets of text reads "flash_read_image: failed 0 errors"
I thought this might be all fine afterall and that I just had to use Fastboot erase blabla to go ahead. But obviously that doesn't work. Most likely because step 12 says install drivers, but no request to install any drivers comes up on my Windows (using Win 7 64 - also, drivers in the package are all Vista - will those work?), which I assume is either because the phone never boots up "far enough" for windows to detect the device, OR because I'm a retard to all major phone hackers here, because I just have to copy them somewhere. (didn't find anything on the boards to suggest the later is true, but then again, who knows).
So, where's the stupid newbie mistake that I overlooked? This isn't the first flash I'm doing, flashed win 6.1/6.5 onto my Touch Pro (1 ), using a fine how-to on this board, and constantly tweaking my S2 and S3, but this seems to be too much for me to figure out.
Thanks for any help!
What phone are you using?
Basic trouble shooting would be.
Task 29, re-download & reinstall minipooploader.
This video gives some idea of what you should expect.Useful info starts around 7:00
http://www.youtube.com/watch?v=_qNCHqGPofI
I have never heard of a suspend error/dialog. Perhaps someone else can chime in.
I think he just hasn't prepped for fastboot properly.
Sometimes I have to reboot a few times to get the cable plug timing or *something* right... Not sure what it is, but occasionally when doing a new flash to Android I had issues with fastboot not being recognized - and obviously you won't be able to flash recovery without fastboot being functional.
So before you task29 and reinstall OP - try a few different things - try plugging the cable in BEFORE you boot the phone. Try pulling the battery again, and do the plug in cable before you turn it on. I can't remember what the secret is here, I know for getting into recovery you have to start holding power as soon as you see the blue screen - but obviously this is beyond where you are at.
arrrghhh said:
I think he just hasn't prepped for fastboot properly.
Sometimes I have to reboot a few times to get the cable plug timing or *something* right... Not sure what it is, but occasionally when doing a new flash to Android I had issues with fastboot not being recognized - and obviously you won't be able to flash recovery without fastboot being functional.
So before you task29 and reinstall OP - try a few different things - try plugging the cable in BEFORE you boot the phone. Try pulling the battery again, and do the plug in cable before you turn it on. I can't remember what the secret is here, I know for getting into recovery you have to start holding power as soon as you see the blue screen - but obviously this is beyond where you are at.
Click to expand...
Click to collapse
To enter fast boot you need to have the phone totally off (not rebooted) with the usb cable removed. Then plug usb cable into the phone with the phone off. Then press and hold the power button until the blue screen is done. Sadly I have been doing this all morning trying to resolve a problem of my own.
Tried that, resulting in a slightly different screen (see attached image). Other than that, no difference. I still don't get any request for the HTC drivers and going Fastboot erase recovery results in "waiting for device".
Could you check the list at the thread I linked in the original posting and tell me if I somehow missed something?
Step 10 worked fine.
Step 11 I guess is what Wizardknight commented on.
Step 12 is what confuses me and what's possibly the culprit here?
I bet it's just that without the drivers my PC can't send the Fastboot commands to the phone.
Everything before that worked fine with no errors and everything after that, is just hammering away at the console.
Thanks guys!
Sent from my GT-I9300 using xda premium
Urgh, no idea why it uploaded the picture sideways, sorry.
When instead I press the power button as soon as I see blue (as opposed to hold it all the time), I get the following (see image)
Sent from my GT-I9300 using xda premium
Looks like it is working ok on the phone. I am assuming you installed fastboot and ADB on the PC.
What happens when you open a command prompt and type fastboot devices?
BTW here are the more official install directions.
Lists nothing. After hitting enter, I'm back at the \android-sdk\platform-tools promt.
Sent from my GT-I9300 using xda premium
Was the usb port on the phone working ok in WM? Could you sync and other data related activities?
Does any unknown devices show up in your device manager on the pc?
Have you tried any other usb cables?
Solved.
I tried different ports and a different cable before, even though my cable worked fine before (and so did the port). Guess I have two dead cables here, because the third one did the trick.
Drivers installed at once, Android installed and I feel very stupid now. Thank you very much for being so patient with something this stupid.
wizardknight said:
Was the usb port on the phone working ok in WM? Could you sync and other data related activities?
Does any unknown devices show up in your device manager on the pc?
Have you tried any other usb cables?
Click to expand...
Click to collapse
This might be where you're going to have to go next OP. Sounds like it's all OK - so try different cables, different USB ports on the PC, and if you can - an entirely different PC altogether.
Vortagh said:
Solved.
I tried different ports and a different cable before, even though my cable worked fine before (and so did the port). Guess I have two dead cables here, because the third one did the trick.
Drivers installed at once, Android installed and I feel very stupid now. Thank you very much for being so patient with something this stupid.
Click to expand...
Click to collapse
Had that problem before too. Glad you got it sorted.
Hello everyone!
Sometimes when I connect my S3 to my computer, some files do not appear when I try to access them from the PC. Until today, rebooting the phone solved the issue but now I am having a hard time to get some data from the phone... Has anyone had the same problem?
Thank you!
Anyone?
I've seen some similar threads in the forum but none of them give me a good solution, still having the same problem...
Backup data possible faulty sd card or phone storage .
Check Lost Dir for files .
jje
happens sometime. just reconnect phone or insert your data cable into another USB Jack
blackyz said:
happens sometime. just reconnect phone or insert your data cable into another USB Jack
Click to expand...
Click to collapse
Still not working. Even having rebooted the phone several times and tried several different usb slots...
When entering recovery mode, what should be mounted and what should not?
Same issues here, switching the usb to camera and back to mtp usually helps
asc366 said:
Same issues here, switching the usb to camera and back to mtp usually helps
Click to expand...
Click to collapse
Thanks for the idea, but still nothing... It is unbelievable how a simple thing like this can become such a pain...
Sometimes I get the "Hardware ID could not be found" message and the only way I've found to reliably get the PC to recognise the S3 is to reboot the PC!
Changing USB ports, unplugging and replugging the phone or rebooting the phone doesn't work!
fortunately my PC boots almost as quick as the phone and I don't need to connect it that often.
My computer won't recognize my gs4. I have the latest drivers installed and have re-installed many times. The only thing it does when I plug it in is charge. It sometimes says windows is searching for the latest driver when I plug it in, but it then it then says it was unplugged. ODIN did manage recognize it once and that was enough for me too root it and then flash the stock kernel back on. My phone then soft-bricked at the padlock after some rom flashing and I had to go to my friends house to flash it back to stock. Is there anything else I can do?
Am I the only one with this problem?
Does it give you the error "USB device not recognized"? If so there are some fixes for it. I fixed my friends when I sold him my S3. His PC did it.
Yes, a couple of times it did that. Now it just does nothing.
If you try and remove the device from your device manager does it do anything?
Right click on computer and go to properties to get to the device manager.
What would it be named? I looked through all the usb stuff and everything else and couldn't find anything that would be my device.
d03p3yy said:
What would it be named? I looked through all the usb stuff and everything else and couldn't find anything that would be my device.
Click to expand...
Click to collapse
It would be any device with a yellow Triangle and an Exclamation point on it. Also uninstall KIES and your Samsung USB drivers, then reboot. Get updated USB drivers from the S4 link in my signature.
It did the same thing and game me the unknown device thing. It also said that the device malfunctioned. I guess ill just try again.
d03p3yy said:
It did the same thing and game me the unknown device thing. It also said that the device malfunctioned. I guess ill just try again.
Click to expand...
Click to collapse
Ok let's try this fix first.
1. Remove phone from PC and shutdown and remove battery to shut off phone.
2. Plug USB cable into PC and phone.
3. Put battery back in and boot phone but…
4. As the phone boots, hold down Volume up and down and don't let go until you see you are in safe mode on the phone. It should say safe mode on the front screen.
5. This should reboot your phone into download mode and install drivers that are needed.
6. Your PC will indicate and recognize the phone.
7. Now if you check the notification drop down on your phone you should see USB/MTP options there in the notification area. MTP should be checked.
Still no luck. Maybe later I will re-install windows or just re install every driver on my computer.
The other fix to try is listed below.
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
---------- Post added at 08:33 PM ---------- Previous post was at 08:31 PM ----------
If that doesn't work PM my your system specs IE RAM, CPU, and HDD Space and current OS.
The computer doesn't do anything when I plug the phone in. The only thing that starts to happen is that the phone starts charging.
d03p3yy said:
The computer doesn't do anything when I plug the phone in. The only thing that starts to happen is that the phone starts charging.
Click to expand...
Click to collapse
Send me the PM with the requested info.
I'm not really requesting anymore info. I am just going to re install windows because I have done so much stuff to this install that it is time for a new one.
Bump
Any luck? My computer won't recognize my phone either anymore.
PeterifficX said:
Bump
Any luck? My computer won't recognize my phone either anymore.
Click to expand...
Click to collapse
have you done the simpliest thing like reboot your computer?
PeterifficX said:
Bump
Any luck? My computer won't recognize my phone either anymore.
Click to expand...
Click to collapse
My experience with the "Device Malfunctioned" thing was due to a bad cable. It would charge, but wouldn't allow me to connect.
You might also try a different USB port on your computer. Often times the connectors on the back of a desktop system, which are hardwired to the motherboard, work more reliably than the front ones.