Related
Hi,
I am gettings this error when ever I do ADB commands to my SU660. Here what I have tried to do:
1. Restart the Phone and even the PC
2. Change Cable
3. Get latest ADB Tools
Hope some one can help me. I need to upgrade my brother's phone
God Bless!
Thanks,
Thomie
tjsas1 said:
Hi,
I am gettings this error when ever I do ADB commands to my SU660. Here what I have tried to do:
1. Restart the Phone and even the PC
2. Change Cable
3. Get latest ADB Tools
Hope some one can help me. I need to upgrade my brother's phone
God Bless!
Thanks,
Thomie
Click to expand...
Click to collapse
If your phone is running Android 4.2.2, and you are sure that you got the updated Android SDK tools for this particular version, then on enabling USB debugging, you should get a prompt on your phone "Allow USB debugging?" after connecting and running "adb devices", to which you need to answer "Ok"
If you are not running Android 4.2.2, try using ADB through wifi
rugglez said:
If your phone is running Android 4.2.2, and you are sure that you got the updated Android SDK tools for this particular version, then on enabling USB debugging, you should get a prompt on your phone "Allow USB debugging?" after connecting and running "adb devices", to which you need to answer "Ok"
If you are not running Android 4.2.2, try using ADB through wifi
Click to expand...
Click to collapse
Hi,
Thanks for you reply. The phone is on Android 4.0.4, also tried enabled USB Debugging but no popup is showing.
Hope you can help me
God Bless!
Thanks,
Thomie
Try the following:
1. A different port (are you using a USB 3.0 port? If so, try a USB 2.0 port). Try changing the port anyway even if you were using 2.0 too. You may need for windows to install the driver after changing the port.
2. Restarting adb service by executing "adb kill-server" and "adb start-server"
3. Uninstall the driver from device manager and restarting, and letting windows install the driver on its own
4. If none of these works, reinstall the SDK Tools and in that make sure that "Google USB Driver" is installed.
Lets hope one of these works
tjsas1 said:
Hi,
I am gettings this error when ever I do ADB commands to my SU660. Here what I have tried to do:
1. Restart the Phone and even the PC
2. Change Cable
3. Get latest ADB Tools
Hope some one can help me. I need to upgrade my brother's phone
God Bless!
Thanks,
Thomie
Click to expand...
Click to collapse
Try this one http://forum.xda-developers.com/showthread.php?t=1752074
Maybe your adb is out of date,get a new version
Sent from my XT875 using XDA Premium 4 mobile app
Hello
I really need help, my phone are not recognized by my pc
no adb no mtp no fastboot
even i use official charger it says "charging usb"
so it's something to do with the software
i just bought new charger, it's the same.
i didn't did anything important modification..
just flash custom multi rom, recovery,
i have s-off, unlocked bootloader rooted...
can anyone help me ?
Kigsuha said:
Hello
I really need help, my phone are not recognized by my pc
no adb no mtp no fastboot
even i use official charger it says "charging usb"
so it's something to do with the software
i just bought new charger, it's the same.
i didn't did anything important modification..
just flash custom multi rom, recovery,
i have s-off, unlocked bootloader rooted...
can anyone help me ?
Click to expand...
Click to collapse
Have you turned on ADB on the phone?
Jackering;Form:4290 said:
Have you turned on ADB on the phone?
Click to expand...
Click to collapse
Yes.
Maybe it's the firmware. I can't flash new firmware without fast boot..
Add : hboot 1.54
Firm : 3.22.154.......
I didn't relocked bootloader when flashing the new firmware
Mate what's the output from adb devices or fastboot devices command?
Guich said:
Mate what's the outputdevices"b devices or fastboot devices command?
Click to expand...
Click to collapse
Nothing
It's empty after "adb devices" or "fastboot devices"
Kigsuha said:
Nothing
It's empty after "adb devices" or "fastboot devices"
Click to expand...
Click to collapse
Umh, seems that the phone wasn't recognized by pc.
Which OS are you using?
If windows go to Device manager and check if you can see your one
Guic" said:
Umh, seems that the phone wasn't recognized by pc.
Which OS are you using?
If windows go to Device manager and check if you can see your one
Click to expand...
Click to collapse
W7 64
Only "unknown device"
No One
Can u tell me if it's bad that I flashed new firmware before relocking the bootloader ?
Kigsuha said:
W7 64
Only "unknown device"
No One
Can u tell me if it's bad that I flashed new firmware before relocking the bootloader ?
Click to expand...
Click to collapse
Are you on android right?
Have you tried to unistall the device from device manager and after re-connect the phone at the pc for the drivers?
Guich said:
Are you on android right?
Have you tried to unistall the device from device manager and after re-connect the phone at the pc for the drivers?
Click to expand...
Click to collapse
Yeah
Tried uninstall and usbdeview. Not work
On my other w7 pc windows say " drivers install failed"
Kigsuha said:
Yeah
Tried uninstall and usbdeview. Not work
On my other w7 pc windows say " drivers install failed"
Click to expand...
Click to collapse
Have you tried linux?
However, seems strange.
You're running 3.22 firmware and in android device isn't recognized...
Guich said:
Have you tried linux?
However, seems strange.
You're running 3.22 firmware and in android device isn't recognized...
Click to expand...
Click to collapse
Didn't try linux
Will do when I can
Kigsuha said:
Didn't try linux
Will do when I can
Click to expand...
Click to collapse
Tried on ubuntu.
Nothing. Phone only charges..
Do I have to retry? Installing adb/usb/fastboot drivers?
Kigsuha said:
Tried on ubuntu.
Nothing. Phone only charges..
Do I have to retry? Installing adb/usb/fastboot drivers?
Click to expand...
Click to collapse
So seems an hardware issue.
Maybe i can try to help you tomoz with teamviewer
Mobile Post
Guich said:
So seems an hardware issue.
Maybe i can try to help you tomoz with teamviewer
Mobile Post
Click to expand...
Click to collapse
Hardware really ?
So there's nothing I can do ?
I'm now with stock Rom stock recovery no root
I can do nothing without usb working..
Seems...
In fastboot, with all os you've tried, no answer by terminal?
Mobile Post
Guich said:
Seems...
In fastboot, with all os you've tried, no answer by terminal?
Mobile Post
Click to expand...
Click to collapse
No answer
I had the same problem a few weeks back. The phone was not recognised by any computer. If you fiddle around with the micro usb on the phone it would recognise the phone for a second. It took me nearly two weeks of trying, to flash a RUU and get the phone back to stock for a repair.
I asked in the shop if this was common and the lad said it has happened to others. It is dust that gets in the usb and people cleaning shorts the motherboard???? I didn't clean anything so I don't know if this is true.
Anyway I got a replacement phone. Maybe you should keep it at stock and get a replacement. If it happens once it will happen again.
Try uninstalling HTC Sync, if you haven't already, uninstall driver, reinstall HTC Sync and see if you can't get the PC to see it. And when the pop up on the phone comes, check always allow.
When I type lsusb : I don't see my One..
htc drivers and htc sync don't works everytime it say unknown device..
Hi guys
Really need urgent help on this one
I wanted to update my nexus 6 to latest5.0.1.
Usually i flash factory images but this time i tried to sideload. This is what i did.
I wanted to factory reset my phone and wipe everything and then side load. so i used TWRP and wiped by mistake the android OS. Now im left with nothing but twrp which also deleted my recovery file.
Now i can access my bootloader and twrp.
My main problem is that when i plug my phone to my pc it does not recognize it and i tried every possible way suggested by NRT tool to update my driver and no luck?
When i plug it to the pc it charges and i get baloon message that pc did not recognized the device.
Im using original cable.
Any help is really appreciated
Thanks
if your pc can recognize your device in fastboot mode then you can go this thread
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
fethi2 said:
if your pc can recognize your device in fastboot mode then you can go this thread
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
As i said earlier my pc wont recognize my device.
Some said that my motherboard could be damaged is it true?
try the universal adb driver http://adbdriver.com/
you can try this one too.
Najeeb Al Busaidi said:
As i said earlier my pc wont recognize my device.
Some said that my motherboard could be damaged is it true?
Click to expand...
Click to collapse
simms22 said:
try the universal adb driver http://adbdriver.com/
Click to expand...
Click to collapse
Najeeb Al Busaidi said:
As i said earlier my pc wont recognize my device.
Some said that my motherboard could be damaged is it true?
Click to expand...
Click to collapse
If mother board was damaged, you were not able to enter in bootloader Try installing universal driver as other suggested above or install motorola's driver
Najeeb Al Busaidi said:
As i said earlier my pc wont recognize my device.
Some said that my motherboard could be damaged is it true?
Click to expand...
Click to collapse
Enable usb debugging in developer options on the phone, then choose either the drivers posted above or the Google usb drivers from the sdk. Choose to install the drivers manualy in device manager when connected to the pc.
gee2012 said:
Enable usb debugging in developer options on the phone, then choose either the drivers posted above or the Google usb drivers from the sdk. Choose to install the drivers manualy in device manager when connected to the pc.
Click to expand...
Click to collapse
Debugging is both impossible and useless.
Can't set USB debugging if android is not installed. USB debugging only works in android anyway. It has no affect on bootloader or recovery
rootSU said:
Debugging is both impossible and useless.
Can't set USB debugging if android is not installed. USB debugging only works in android anyway. It has no affect on bootloader or recovery
Click to expand...
Click to collapse
Oke thanks, never to old to learn
gee2012 said:
Oke thanks, never to old to learn
Click to expand...
Click to collapse
99.99999999 .... % of the issue is USB Drivers on the PC in question.
I'd uninstall, then reinstall, or try the universal ones.
Try on another PC if available, once seen you can get it back.
fethi2 said:
if your pc can recognize your device in fastboot mode then you can go this thread
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
My pc cant recognize the phone while in fastboot
Hi guys
Check the attachment
And let me know if u found the problem.
Hello.I am in some kind of a trouble..I just bought a phone with firmware problems,hoping i could make it work.The problem is this,someone tried to update the firmware,unsuccesfully,and now it's stuck with no OS.I can only start recovery and bootloader.
Recovery is Teamwin 2.6.3.3.Already tried to clear cache and everything,to use an USB with OTG,but it's not recognised,ADB sideload also it's not working.
adb devices shows the phone is not connected,and FastBoot says "Waiting for device".Any idea? I've tried,read a lot,but I can't really work it out..
Also,I can't find the device in Device Manager,neither in ADB nor Fastboot.
I tried using Windows 8.1 and 7..Same deal.
Thank you!
chris_b0ss said:
Hello.I am in some kind of a trouble..I just bought a phone with firmware problems,hoping i could make it work.The problem is this,someone tried to update the firmware,unsuccesfully,and now it's stuck with no OS.I can only start recovery and bootloader.
Recovery is Teamwin 2.6.3.3.Already tried to clear cache and everything,to use an USB with OTG,but it's not recognised,ADB sideload also it's not working.
adb devices shows the phone is not connected,and FastBoot says "Waiting for device".Any idea? I've tried,read a lot,but I can't really work it out..
I tried using Windows 8.1 and 7..Same deal.
Thank you!
Click to expand...
Click to collapse
Is it a M8 or a M7, because your title says M8 but you have posted in the M7 forum.
Sorry,I am quite scared.It's M7.
chris_b0ss said:
Sorry,I am quite scared.It's M7.
Click to expand...
Click to collapse
First, follow instructions given in this post to install the latest android sdk-tools and the latest htc drivers. Also make sure you don't have HTC Sync installed on your computer.
Then connect your phone to you computer with the original cable (or any other cable already known to work for data transfer - some usb cable are only providing power), reboot the phone in bootloader mode by holding vol down and power. Make sure you see the red "fastboot usb" caption on the screen, if not use vol up/down and power to select the "fastboot" menu. Once there open a command window form the android sdk-tools folder and type "fastboot getvar all". Copy/paste the ouput of this command here (except the imei and serialno).
I've followed that,and still not working.pics attached.
It's very weird,because I was expecting for a soundfrom the Windows,like a new device connected .But ..nothing
Sent from my GT-I9100 using XDA Free mobile app
chris_b0ss said:
I've followed that,and still not working.pics attached.
It's very weird,because I was expecting for a soundfrom the Windows,like a new device connected .But ..nothing
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
With your phone in bootloader/fastboot mode, go to your windows device manager, take a screenshot of your device manager and post it here please.
The unknown device is related to my laptop.Nothing happens when I connect the phone.
chris_b0ss said:
The unknown device is related to my laptop.Nothing happens when I connect the phone.
Click to expand...
Click to collapse
Ok so its not detected at all
Might be caused by
a bad usb cable --> Try another one that you are 100% sure its working
a bad usb port on the computer (use only usb 2.0 ports btw)
a problem with the computer ---> Try another computer.
a bad usb port on the phone ---> need to replace the usb/front mic board
Might also worth to fix your laptop drivers problem. Might be causing problem if the "unknown" device is an adapter or usb controller...
Then reboot the computer.
I think we can exclude the first two,because I've tried 2 different USB cables,and with my S2 ,both of them are working,even ADB.I will try to replace the usb port from the phone,and then try again.But,do you think it will work ?
Thank you!
chris_b0ss said:
I think we can exclude the first two,because I've tried 2 different USB cables,and with my S2 ,both of them are working,even ADB.I will try to replace the usb port from the phone,and then try again.But,do you think it will work ?
Thank you!
Click to expand...
Click to collapse
Its hard to tell, there isn't any background info about what was done on that phone. The usb board is pretty cheap so it worth a try if you are 100% sure everything else is fine (computer, cables etc..)
I understand,but,I mean,as far as I know,it's not hard brick,because the phone is still booting..in some way ..so if I manage to connect it,I can flash the rom..am I right?
Sent from my GT-I9100 using XDA Free mobile app
chris_b0ss said:
I understand,but,I mean,as far as I know,it's not hard brick,because the phone is still booting..in some way ..so if I manage to connect it,I can flash the rom..am I right?
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
Normally it should be pretty easy to fix if you can get fastboot and adb connectivity. You could then update the firmware so you can flash the correct RUU to restore the phone back to stock, already made the research and all the files (firmware and ruu) you'll need are available.
alray said:
Normally it should be pretty easy to fix if you can get fastboot and adb connectivity. You could then update the firmware so you can flash the correct RUU to restore the phone back to stock, already made the research and all the files (firmware and ruu) you'll need are available.
Click to expand...
Click to collapse
Sorry for the late reply,the phone is now in service,in 1-2 days they should fix the USB board,and I will get back with more info soon.
Thank you very much for your quick answers and for taking time to help me!
Good news,I've managed to unbrick it.I asked a friend with a Mac to check it out,and his Mac recognized with no problems.Installed the Os,but still,Windows can't detect it.I've tried on 2 pc's(7 and 10) with the proper drivers.Weird..
Anyway,thank you for your time @alray !
I found out this morning that my phone had cut off during the night. When I tried to turn the phone back up it just stayed at the loading screen and does not go any further than that. I can get into Fastboot/recovery but not sure what is going on. Phone is locked as well.
I am running on Developer preview 5 and I assuming it has something to do with this. I have read up on others having issues and talk about sideloading the OTA that has resolved the issue but my computer does not even detect the device, so adb does not see the device. Feel like if I can just get my computer to detect my phone I'll be in business.
Really need some help on this one as it is starting to look like I am going to have a nice paper weight the rate its going. Thank you in advance.
cjsill9473 said:
I found out this morning that my phone had cut off during the night. When I tried to turn the phone back up it just stayed at the loading screen and does not go any further than that. I can get into Fastboot/recovery but not sure what is going on. Phone is locked as well.
I am running on Developer preview 5 and I assuming it has something to do with this. I have read up on others having issues and talk about sideloading the OTA that has resolved the issue but my computer does not even detect the device, so adb does not see the device. Feel like if I can just get my computer to detect my phone I'll be in business.
Really need some help on this one as it is starting to look like I am going to have a nice paper weight the rate its going. Thank you in advance.
Click to expand...
Click to collapse
If I understand correctly, you can get to fastboot mode. If you then plug in the usb cable, and type fastboot devices, does the computer recognize it?
Have you ever connected to the phone using your computer and either adb or fastboot? In other words, is there a high level of confidence that the drivers are setup on your computer?
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
I've had experience with using adb/fastboot on my moto x 2014 but this is the first time doing this on my nexus and I am pretty sure I had never hooked up my nexus to this computer before this issue happened. So I wouldn't be surprised if it is a driver issue but I have downloaded Android sdk and gone into sdk manager to have it install google drivers. I just now now played around with Nexus Root toolkit to assist in installing drivers with the same results. I had used the tool to uninstall any drivers that could have impacted this and reinstalled with no luck.
ktmom said:
If I understand correctly, you can get to fastboot mode. If you then plug in the usb cable, and type fastboot devices, does the computer recognize it?
Have you ever connected to the phone using your computer and either adb or fastboot? In other words, is there a high level of confidence that the drivers are setup on your computer?
Click to expand...
Click to collapse
cjsill9473 said:
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
I've had experience with using adb/fastboot on my moto x 2014 but this is the first time doing this on my nexus and I am pretty sure I had never hooked up my nexus to this computer before this issue happened. So I wouldn't be surprised if it is a driver issue but I have downloaded Android sdk and gone into sdk manager to have it install google drivers. I just now now played around with Nexus Root toolkit to assist in installing drivers with the same results. I had used the tool to uninstall any drivers that could have impacted this and reinstalled with no luck.
Click to expand...
Click to collapse
Do you have an otg cable? Does that work?
I do but I don't have one on me currently. I am currently at work but will be home in about 2 hours.
ktmom said:
Do you have an otg cable? Does that work?
Click to expand...
Click to collapse
cjsill9473 said:
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
Click to expand...
Click to collapse
When you are in fastboot mode, and connect to your computer, you should run "fastboot devices", instead of "adb devices".
You are correct, device does show up when type in fastboot devices. Guess that is what I get when trying to do this while I am at work and haven't messed with this type of stuff in months. I really appreciate the fast response on this and my derp moment. Now to try and side load the OTA to see if I can bring my phone back to life. Looks like I just need to go into custom recovery and select "Apply Update from ADB" and hopefully I'll be in business.
jj14 said:
When you are in fastboot mode, and connect to your computer, you should run "fastboot devices", instead of "adb devices".
Click to expand...
Click to collapse
Well at this point I was able to side load the OTA DP5 build and its doing the same thing. Trying a factory reset now to see if that will make a difference but if not looks like I am going to have to go out and get me a new phone till I can get this one fixed or RMA'ed. Just stuck at the loading animation.
Edit: Factory restore finally brought it back to life. Thank you again for the quick help and assistance on this!