Related
Okay a little backstory:
I was on an early version of CM9 but as i am selling the phone i decided to put a more stable version of it on there and downloaded CM7 -stable.
I flashed this in CWM and it worked fine.
I gave it a quick test and noticed all the google apps were missing, most importantly the market. So i booted into recovery and realised i had forgotten to put the zip on the SD card.
I then went into mounts and mounted USB, nothing happened...
From that point onwards the phone would not talk to the PC. even if i booted up into the phone, it would just show it as charging. I could not find any options in the menus for USB options.
After some extensive reading, i tried a few things, none of them had worked. I found a post mentioning some kernels have issues with USB, so i downloaded the recommended one and flashed it in CWM.
After rebooting, CWM was now orange and not blue and the option to flash from external card has gone.
I have also done some digging and there is a good posibility that the kernal that i flashed was for the GT I9000 (which is the american one, right?)
So as it is at the moment:-
I can get into CWM.
I can get into download mode through the 3 button combo.
I can get into download mode using home made jig.
I can boot the phone, but it boot loops.
I can not get the phone to be detected on the pc.
Things i have checked:
Cable will connect other phones.
Tried different cable to be sure.
Phone used to be detected, but downloaded drivers through kies again to be sure.
Closed Kies using task manager.
Nothing is coming up in network connections in device manager when phone is connected.
I'm out of ideas now, so £10 PayPal donation for anyone that comes up with the solution to fix it
If i can get it detected, i can use Odin to flash what i want.
Sounds like a drivers problem. You may need the 'Google driver' developer.android.com/sdk/win-usb.html
When I had bootloops when I first installed CM9 I used heimdall to flash a the stock CM9 kernel. This gave me back CWM.
heimdall flash --kernel 'kernel.zip'
In the commandline.
Thanks for that,
I already had the Google USB drivers from when i installed the SDK to make some apps.
So i then gave Heimdall a try (Graphical Version), it seemed to suffer the same problem.
Reporting "Failed to detect compatible download-mode device."
I seem to remember the GUI saying I didn't have the correct drivers and it downloaded them for me.
The other thing worth a try is changing the USB port and reinstalling the correct drivers on that port.
I've not seen anything like that, it has not asked me for any drivers.
It's like the phone is not connected at all. nothing will detect it, i have even tried it on another PC.
Sorry, I'm not sure what you mean by installing on a port.
Well sometimes changing USB port will allow you to install new drivers. Although if you've tried it in another computer and it doesn't work then changing port may not help.
Does the phone appear in device manager when it's connected and in download mode?
Nope. Not coming up at all in the device manager. It didn't when it was booting fine. And it still doesn't in download mode. :-( I'm thinking the usb connector on the phone might be faulty.
But it was working up until trying to mount the USB in CWM
Sent from my GT-N7000 using XDA App
I don't suppose you have access to a Linux PC do you? Windows USB drivers are notoriously sucky. If you could plug it into a Linux PC and type 'lsusb' at a command line, that would at least show you that the device is really there.
I think I have a spare pc kicking around that I could use. I'll give it a go when I get home tonight.
Sent from my GT-N7000 using XDA App
Remove all the drivers completely from device manager for Samsung, then install fresh drivers and connect the cable when in download mode, hopefully it will recognize it
Are you sure the connector is clean? e.g. maybe there's dust in it.
I had that problem once, the connector was full of fabric fibers from some coat's pocket I had the phone in.
Suggestion 1 (Linux): I installed ubuntu, did not detected anything to even install any drivers. Detected my new phone fine.
Suggestion 2 (Uninstall drivers from device manager): I could not find any drivers named with the name Samsung in there.
Suggestion 3 (Clean port): I have some compressed air that i sprayed inside, it does look pretty clean and will continue to charge but still not connection on the pc.
To install the drivers for heimdall you have to run zdiag from inside the driver folder. Had to do this earlier on, the phone the other appeared as something other than Samsung composite usb or whatever it normally says
I tried this, and it displayed 9 devices after selecting show all. I seemed to recognise all of the items in the menu.
To be sure, I then disconnected the phone and re ran it to see if one of the items were missing, but it was the same number.
I too had problem with the usb connection on my i9000, and I was pretty sure my usb connector on the phone is somewhat damaged since it sometimes can only go to charging mode without being detected by my pc as a usb device. CWM instal is fine but ODIN can only detect the phone without able to flash the rom to the phone. The flashing will always stuck at the message "Setting Up Connection", I waited for 15 minutes and the flashing will eventually died. I retry the odin flash for 40 to 50 times and eventually the flashing will go through one time. Tried heidmall command line and the result is the same.
I have problem with Odin in the past. I bought a new laptop, running Win7 64 bit. Installed Samsung Kies to install the correct USB drivers for the phone. Then made sure that Kies wasn't running in the background. So tried using Odin. Odin was detecting the phone, but it was hanging at initialising connection. Odin was working fine on my old laptop running Win7 32bit. Long story short, I was having a few issues with my new laptop, reinstalled Win7 64bit, now Odin is working fine, have flashed the phone a few times using the new computer.
After flashing which kernel you started facing this problem?
Wipe ur phone,re-flash CM7(flash the nightly 181,it's completely stable),uninstall KIES,uninstall old usb drivers,install these usb drivers http://forum.xda-developers.com/showthread.php?t=961956 ,check that USB storage mode is set as Mass Storage and then connect your phone. Also try enabling/disabling USB debugging
lovedonator said:
After flashing which kernel you started facing this problem?
Wipe ur phone,re-flash CM7(flash the nightly 181,it's completely stable),uninstall KIES,uninstall old usb drivers,install these usb drivers http://forum.xda-developers.com/showthread.php?t=961956 ,check that USB storage mode is set as Mass Storage and then connect your phone. Also try enabling/disabling USB debugging
Click to expand...
Click to collapse
The point at which i could no longer mount the USB was when i selected "mount usb" from CWM. I later installed a new kernal which downgraded my CWM, removing the install from external SD option.
So I cant flash a re-flash a rom unless i can it onto the phone which without the USB working is near impossible.
Xyis said:
The point at which i could no longer mount the USB was when i selected "mount usb" from CWM. I later installed a new kernal which downgraded my CWM, removing the install from external SD option.
So I cant flash a re-flash a rom unless i can it onto the phone which without the USB working is near impossible.
Click to expand...
Click to collapse
You can directly download the ROM on your internal sd using dolphin browser or opera mobile
I can't do that either as the phone is currently boot looping.
Sent from my GT-N7000 using XDA App
Hey guys!
In advance I'm sorry for asking something that has probably been asked many times before, but I'm unable to find the right answer.
Okay let's start at the beginning. My HTC one with an unlocked bootloader on stock started to display a very irritating bug in that sometimes the screen would not rotate and was stuck in landscape mode. Nothing would help nor rebooting, nor calibrating the sensor. Only booting into the bootloader would somehow help.
Until it did not.
I tried a factory reset, which did not help and then tried just wiping Dalvik and Cache, which did not help too.
Then I tried wiping Data and System, which I now know was very stupid.
The current problem is that I can't figure out how to send a new ROM to my HTC one using adb, when typing adb devices the device does not show up.
My computer does see the device, listed under Android USB devices ad My HTC. I think Fastboot too, recognized the device, because I am able to get the Identifier token.
I have installed the drivers and installed HTC Sync manager. I have restarted my Pc multiple times and changed the USB port the device is connected to.
I too, tried mounting the USB, but either I'm doing it wrong, or it does not work.
Hope one of you can help me! I've been at this all day long...
Adb commands only work when you're booted in the rom or recovery. Fastboot uses fastboot commands. Do you have a custom recovery? If so, you can adb sideload a rom. If not, you can fastboot flash a custom recovery assuming your bootloader is unlocked. You may have mentioned it in your post I just can't remember. Good luck!
Sent from my HTC One using xda app-developers app
Thanks for the help!
Yes, I unlocked my bootloader and have twrp installed.
I think I have narrowed down the problem: that my device is not recognized by the computer in twrp.
When in fastboot, My computer does recognize the device, listed as an HTC one, so the drivers are not the problem.
When booting into recovery, me computer only recognizes the phone for about 3 seconds, when it dissapears.
I have been able to see the device in Adb (using Adb devices).
What could I do? Adb sideload does not work because the computer does not recognize the device.
Hi,
You're on Windows? If yes which version?
Windows 7, but if needed I do have access to a win 8 PC as well.
All x64 by the way.
Ok, maybe take a look here if you use USB 3.0?: [FIX]Fastboot problems on Windows 8 x64 with USB 3.0? Solution inside.
It might work on Windows 7 too, there is a link for the drivers for x64.
Maybe using a toolkit to use ADB/fastboot? Take a look here:
[TOOL]HTC One (M7) All-In-One Toolkit V3.1
[TOOL]HTC One (M7) AIO Toolkit | v1.4
Okay, from now on I'll only use USB 2.0.
I tried these two toolkits, but they suffer the same problem as me in that in order for adb sideload to work the device has to be recognized for longer than 3s after booting into recovery.
I just bought a female-female USB adapter, hopefully installing a rom from a usb stick will work
Ofcourse help would still be greatly appreciated as i will have to wait for over a week till the USB adapter arrives.
cannot connect to pc i have unlocked bootloader with htcdev and installed cwm touch v 6.0.4.4 one Flyhalf205's thread. that all worked fine.
but after doing a nandroid backup for my uk EE htc one cid htc_001. i then rebooted phone from recovery but now when i connect phone to laptop it does not recognize it through windows. nothing happens when i fastboot devices either please help thanks.
nathlynn22 said:
cannot connect to pc i have unlocked bootloader with htcdev and installed cwm touch v 6.0.4.4 one Flyhalf205's thread. that all worked fine.
but after doing a nandroid backup for my uk EE htc one cid htc_001. i then rebooted phone from recovery but now when i connect phone to laptop it does not recognize it through windows. nothing happens when i fastboot devices either please help thanks.
Click to expand...
Click to collapse
You cannot do fastboot devices in recovery mode.
in recovery mode you can do adb devices to check if your phone is recognized by your laptop
in fastboot usb mode, you can do fastboot devices to check if your phone is recognized by your laptop
I have the same. Was working fine beforehand now nothing. When I connect to the PC with the phone booted it connects then a second or two later disconnects, like it "doesn't like" the connection. It tried to install HTC MTP driver but fails as it says the "device is disconnected." Fastboot USB works fine though and I can carry out fastboot commands from bootloader, but no ADB
[email protected] said:
You cannot do fastboot devices in recovery mode.
in recovery mode you can do adb devices to check if your phone is recognized by your laptop
in fastboot usb mode, you can do fastboot devices to check if your phone is recognized by your laptop
Click to expand...
Click to collapse
I tried fast boot devices in fast boot USB by going into minisdk. Didn't try in recovery would have been good to try adb devices in recovery because I was stuck in that when first tried the custom recovery but a hard reset kicked it back out. Got recovery sorted just wanted to take nandroid backup off phone to PC and put root files which I'm still trying to get best 1's any idea where to get them where URL link is working? I've tried fastboot so doesn't work and basic trying to connect phone to PC for file transfer doesn't work either
stovie_steve said:
I have the same. Was working fine beforehand now nothing. When I connect to the PC with the phone booted it connects then a second or two later disconnects, like it "doesn't like" the connection. It tried to install HTC MTP driver but fails as it says the "device is disconnected." Fastboot USB works fine though and I can carry out fastboot commands from bootloader, but no ADB
Click to expand...
Click to collapse
Ok so not only person. When I try connect mine doesn't even flag up I've connected a device USB debugging starts up on phone but have just noticed USB connection doesn't show. Plus I connect to PC and doesn't make the sound as I've it recognized my connecting anything. Fastboot USB comes up empty. I've been spending a couple hours here and there for past 2 nights trying to set phone up ready for rum runner. But my other question is if I'm already on htc_001 there's no need for me to change CID num anyways? Thanks
Try going to command prompt and typing in set devmgr_show_nonpresent_devices=1 followed by start devmgmt.msc
Click on view and show hidden devices. This will show devices which are not connected but have been installed. Look for something like android phone or android device and update the drivers by selecting update driver > let me select > have disk and then select the driver from here:
http://forum.xda-developers.com/showthread.php?t=2386956
Try that and see if it works
I'm all sorted now thanks just kept at it.
Sent from my HTC One using XDA Premium 4 mobile app
Phone Information : HTC Incredible S, S-ON, 4EXT Recovery
I was using SVHD 2.1 ROM from quit some time, since last week, phone was lagging too much and when I connect phone to PC it was not showing me storage options. Phone was charging but I did not see any increase in battery percentage. I wanted to try VIVOKAT by szezso so went for flashing the ROM. This is where the problem started.
I did wipe data, wipe cache, wipe dalvic and wipe boot. After that I flashed VIVOKAT and when I try to flash boot.img, I found that it was not showing me "fastboot usb" mode. I tired different cable with no luck. And as expected phone is stuck in boot animation.
I thought there might be driver issue, so I re-installed HTC Sync but that also did not help.
Later I did restore of backup taken using CWMR before rooting, Now, restore appears to be successful, but phone is not booting, when I try to start it, it restarts into recovery.
can you guys please help me in resolving this issue
I tried with other PC and other HTC phone combination, USB Cable is fine and other phone is detected so I believe my phone's USB is not working.
When I restarted my phone with USB connected windows indicates that device is connected/disconnected and gives USB error. If I click that message USB devices window opens and it says - Windows has stopped this device because it has reported problems. (Code 43).
What options I have now?
I reflashed SVHD 2.1 and kangaroo kernal v19 on which I was earlier and phone booted
will check USB again after full recharge and will let you guys know.
anyone knows if replacing USB port (phone hardware) will help? asking as phone is charging normally when connected to charger but not when connected to PC
I was gonna flash and prior to doing so I accidentally wiped internal memory. When trying to reboot I received a message in TWRP saying no ROM found. Phones does not boot since the OS was wiped.
I'm able to get back into recovery but there is no ROM to flash and Unfortunately there's no memory card slot on the phone. If there was I could have transfer a ROM over to sd card and installed it.
I've tried installing from a RUU file using a windows 7 laptop but I get an error message 170 USB not connected. I'm not sure why its not recognizing my phone. I have htc drivers installed. I have also unistalled the htc drivers, rebooted laptop and installed drivers again with no luck. I have also tried ADB side load in TWRP but adb is not recognizing device, Im unable to push a rom. I just do not get why it is not recognizint my htc one. I'm able to charge it so I assume the usb port on the device is not the issue. Strange, My other devices get recognized through usb.
Any suggestions on what I can do to install a ROM or get my laptop to recognize my phone? The last 2 days I have done reasearch without any luck, I hope someone here can help. If only if this phone had a SD slot, then this wouldn't be an issue as I'm able to get into recovery.
You can use adb to push the ROM to /sdcard/ while in recovery and you should be able to install it from there.
makaveli0622 said:
I was gonna flash and prior to doing so I accidentally wiped internal memory. When trying to reboot I received a message in TWRP saying no ROM found. Phones does not boot since the OS was wiped.
I'm able to get back into recovery but there is no ROM to flash and Unfortunately there's no memory card slot on the phone. If there was I could have transfer a ROM over to sd card and installed it.
I've tried installing from a RUU file using a windows 7 laptop but I get an error message 170 USB not connected. I'm not sure why its not recognizing my phone. I have htc drivers installed. I have also unistalled the htc drivers, rebooted laptop and installed drivers again with no luck. I have also tried ADB side load in TWRP but adb is not recognizing device, Im unable to push a rom. I just do not get why it is not recognizint my htc one. I'm able to charge it so I assume the usb port on the device is not the issue. Strange, My other devices get recognized through usb.
Any suggestions on what I can do to install a ROM or get my laptop to recognize my phone? The last 2 days I have done reasearch without any luck, I hope someone here can help. If only if this phone had a SD slot, then this wouldn't be an issue as I'm able to get into recovery.
Click to expand...
Click to collapse
i also had the exact same problem with my sprint htc one... while installing an RUU my laptop showed an error that device is not connected (it was running windows 8.1 x64 i think that was the problem) then i disconnected and connected the phone again it showed "USB device not recognised" and even fastboot could not detect the phone ....
when i switch on the phone it would go straight to TWRP... i tried adb push and flashing through USB-OTG cable with no luck..
but when i connected my phone to my friend's desktop running windows 8 x86... it did not show up in my computer but fastboot detected it and i was able to flash this RUU http://www.androidfilehost.com/?fid=22926241640219526 ... and now my phone is up and running...
now first try USB-OTG method, if it fails try flashing RUU.zip from other computer it might get detected...
:good: