Hello. i noticed that my computer(win 8.1) was giving a usb device not recognized error a few days ago. i didn't fix and eagerly updated to android 4.4.3, but forgot to disable freedom and now can't use google play services. i can fix that but the DAMN PHONE STILL ISN'T RECOGNIZABLE BY THE DAMN COMPUTER. i have tried multiple cables and installed win 8 dual boot but still got the same error. i also tried to reinstall drivers. but i think i didnot do it right.
both adb and fastboot are not working. if u could tell me a method to install a custom recovery without root and adb that would sove half my problems but still need help getting the computer to recognized the phone.
Normally this is a problem with charging block of the phone.
You have to root to flash recovery without a computer, towelroot works on 4.4.3. Once rooted you can use goomanager app to flash twrp recovery.
Does the PC making sound of connected I disconnected continually?
Related
Hello,
I've installed VillainRom 5.5 since a long time, and I think that I've never try to use adb since that.
Yesterday, I try to connect my phone on my computer to install VillainRom 12 based on officiel 2.1, and it tells me that the hardware is not reconize, and adb command didn't work.
So I used the Power and return combination to reboot to bootloader and from that, I managed to used fastboot to boot on RA recovery.
But even now, with my VillaimRom 12, Windows XP doesn't reconize my phone anymore....I can use it for charge or mounting the sd card, but adb doesn't work anymore...
I try to download http://dl.google.com/android/android-sdk_r06-windows.zip and the update package "usb driver rc3", but it changes nothing... :-(
A idea?
Edit: It works thanks to http://www.crazyws.fr/blog/tutos/votre-htc-hero-en-modem-usb.html
Thanks
First some background:
Playing around with some ROMs, I loaded up MIUI. I wanted to see what all the fuss was about. While installing from ROM Manager, the subsequent boot into CWM started my backup and installed the ROM. During the process CWM notified me the install was attempting to overwrite the recovery partition. I inadvertently said yes, one of the bad things about touch recovery...fat fingers.
Result:
CWM was blown away. MIUI failed to install Google Apps.
I connect the N7 up to my PC. It is not detected. No ADB available, however I can use wireless ADB so I installed ROM manager and reflashed CWM. This was were the fun began. Everything on my internal storage got nuked during the install and attempted recovery. I had to format internal storage.
No biggie, I have backups on my laptop through WUGFresh Root Kit. I will restore back to stock and start over.
Problem:
No computer I connect the N7 to detects it, regardless of USB connection method nor OS on the PC (Ubuntu, Win 7, Mint). I still have wireless ADB but that doesn't help with fastboot.
Current Status:
Currently I am running AOKP, after flashing multiple ROMs and Recovery between TWRP (current) and CWM. Also I have done many factory resets, cache cleaning, etc.
My diagnosis:
I think my boot, recovery or bootloader partition is borked due to the fat finger in CWM while installing MIUI. The added bonus...without being able to connect the N7 to any PC, I can't get into recovery unless I get lucky (1 out of 10 tries I get lucky and can get into recovery). I can get into recovery as long as I can boot into a ROM and do any common method to reboot recovery.
Question:
Now my question, does anyone have any ideas what I can do to get the USB connection working again to allow ADB/Fastboot connections?
Additional info/Review:
I have a GNex that I can ADB/Fastboot into without issue.
I have tried multiple different cables to connect to PC/Laptops.
As mentioned, I have tried multiple PCs to attempt a connection running everything from Windows 7 to variations of Linux (Mint and Ubuntu)
All the cables work fine with GNex, excluding one cable I deemed trashworthy.
I am fairly certain that the micro-USB port is fine, I can charge without issue even connected to a PC. OTG cable works perfectly fine.
I did something saying a port was open from the N7 that cause USB connection to fail. I forget what I did to find that message or what program I was using. I think I was trying to do a adb usb command from the command line on the N7.
USB Debugging is enabled.
More info:
No errors in logcat when connecting N7 to PC.
Try to do complete wipe & flash stock . My desktop has never detected the n7 but the fastboot works. I was able to flash stock using wugs toolkit.
Sent from my GT-I9300 using Tapatalk 2
That is the problem, I can't get any PC to recognize the n7 is connected. therefore, wugs root tool kit wont work. it uses fastboot and adb. without the drivers loaded and the device detected, I can't use wugs. this happens even on machines I have never plugged the n7 into.
If I could find a flashable zip of stock, that might do the trick.
I am wondering if I can use the otg cable and connect from my phone with adb? I don't think I can run fastboot commands from the phone though.
Sent from my Nexus 7 using Tapatalk 2
Doubt you could. Have you tried booting into bootloader then changing the usb port on the and also try reinstalling the drivers. When in bootloader try locating your device in device manager.
Good luck
Sent from my GT-I9300 using Tapatalk 2
panjaby said:
Doubt you could. Have you tried booting into bootloader then changing the usb port on the and also try reinstalling the drivers. When in bootloader try locating your device in device manager.
Good luck
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
even in boot manager, the device does not show in device manager on windows and it can't be seen on Linux either when looking for attached devices.
With my old viewsonic gtab I use to verify there was a device connected from command line, that doesn't work either. I'll post that command later today, just for reference.
Sent from my Nexus 7 using Tapatalk 2
OK, I have verified the problem is on the tablet side. I can connect my OTG cable to the tablet and mount my GNex allowing me to perform adb commands sent to the phone. I can not mount my tablet to the phone reversing the cable.
N7 ---> OTG ---> USB ---> GNex (works)
GNex ---> OTG ---> USB ---> N7 (fails, phone does not recognize the tablet being connected. I verified I could connect to a USB stick without issue.)
I think this narrows it down to MTP/PTP being disabled somewhere. Since it affects fastboot as well, I am assuming something in boot or bootloader. I ruled out recovery due to recovery working correctly when I can get to it.
Any ideas?
The problem is I can't unbrick and restore my nexus to stock rom.
I can't boot the device and I'm only able to boot to bootloader. However, my computer doesn't recognize the nexus. It keeps saying Window cannot recognize it whenever I plug my tablet to the computer in bootloader. I tried uninstall and reinstall driver several times, but none of them seems to work . ----> That means I can't even use adb to restore the phone simply because my tablet is not recognized in window.
Is there anyway to fix this problem? I really need your helps as soon as possible.
Thank you for reading !
Get to bootloader. Then use Wugs toolkit, open advanced options. On the very left is something like "temp boot to recovery". Once that boots it to recovery, ADB should work. It did for me. I was in some trouble last night and got out by this. If you know how to use adb/fastboot commands, you should be good. And I uninstalled my drivers and when I plugged it in the device automagically reloaded the drivers. But you have to do it a few times. Had to do it in bootloader, recovery, and another point. Anytime it asks to load drivers/etc do it.
I can't boot to recovery through Wug Tool Kit. It keeps saying Fastboot device was not found >"<
By the way, whenever I connnected my device to computer, the bootloader freezes :|
What were you doing before you go into this situation?
I was on Glazed Jelly Bean rom and wanted to go back to stock rom. I used nexus 7 toolkit to do all the work for me. However, there was something wrong like the toolkit didnt extract the stock img right or something like that, my tablet got bootloop, and what happened next was what i had been telling you guys.
Best bet is if somehow you could get into recovery or get adb working. Might want to uninstall drivers and install again and reboot computer. I would suggest using this thread and flash things manually back to stock. http://forum.xda-developers.com/showthread.php?t=1907796 but you would need adb working.
When you power off device and use volume and power can you get it to go into boot loader then plugged into computer try to get to recovery or adb.
Consider deleting the drivers from Windows after uninstalling them otherwise Windows may try to be "clever" and reinstall the bad driver when you plug the device in. The Nexus 7 drivers from Asus can be downloaded here and Google's USB drivers are here
Travisdroidx2 said:
Best bet is if somehow you could get into recovery or get adb working. Might want to uninstall drivers and install again and reboot computer. I would suggest using this thread and flash things manually back to stock. http://forum.xda-developers.com/showthread.php?t=1907796 but you would need adb working.
When you power off device and use volume and power can you get it to go into boot loader then plugged into computer try to get to recovery or adb.
Click to expand...
Click to collapse
What if I couldn't get adb working?
I tried everything and windows still doesn't recognize my device in fastboot
Have you tried Nexus Root Toolkit v .1.5.4?
kiddo94 said:
I tried everything and windows still doesn't recognize my device in fastboot
Click to expand...
Click to collapse
try connecting to the usb port at the back of your computer
Paranoid flashed with the bricked kernel did this to me once right after the move to 4.1.2. Even with a full wipe and all the usual safety precautions it just stuck on bootloop forever and wouldn't let me in. I chalked it up as that's what I get for being the guy that's never satisfied with stock. I was unable to get my nexus7 fixed. I sent you a suggestion on pm though.
Never mind everyone. Thank you so much for your help.
I tried install the nexus 7's driver on another computer and it recognized my device in bootloader mode, and restore everything back to stock now. Thank you so much!!!!
Mine did that to the first time I tried. After I got it to work, the permissions were all messed up and I could not get it to download anything off the web and I was getting a playstore error 90% of the time as well. I finally just wiped everything on my tablet, installed the stock rom via N7 toolkit, then reflashed smooth rom, and all is working now. It may have been a bug with the older version of N7 toolkit, as I updated it before I reran everything.
I'm having one heck of a problem here. So I've got my Nexus 7, on stock Android, but rooted and unlocked.
I wanted to try Paranoid Android, so I installed the TeamWin Recovery using the Nexus Root Toolkit, then flashed the ROM and wiped cache/dalvik. I tried to boot into the new ROM, but it just stayed on the boot animation. So I looked up the issue, and the solution seemed to be return to stock Android, then flash Paranoid Android again.
So I tried to use the 'Flash Stock and unroot functionality' of the Nexus Root Toolkit, which proceeded fine until the copying of 'system' onto the device... This lasted for about an hour without progress, so I decided to try again with a different version of stock Android. This too didn't work.
So then I (foolishly) rebooted the tablet. But when I got back to fast boot, it didn't show up in Windows (on either of the two machines I have here, and with two cables that have both worked previously, in multiple USB ports). The specific error is that it shows up as an unknown device (which is fine) but also in the device manager there is error 43, which states that the USB has malfunctioned so it has stopped.
For that reason, it's impossible for me to connect it to a computer or even re(install) the proper drivers for it. And as it doesn't have a working OS, i can't get to ADB either. So right now I can't think of anything that will work - no fast boot, no recovery, no connection to a PC.
Any ideas?
Really, no ideas? Come on XDA Developers, you're my only hope <3
Hi there!
ive got the same issue and i can tell what is NOT working to fix this problem:
deleting ALL usb drivers from pc and installing adb drivers, windows troubleshoot and nrt
i'm just like confused but i think it's all windows fault, if i could i would trie on linux or any other pc os
**UPDATE I have unbricked my phone and the whole time I thought it was a software issue on my phone but it was a cable, I guess my cable got broken when I bricked my phone and I thought it was a software issue but it was not the whole time**
I have a bricked device and I would appreciate your help and I have tried EVERYTHING!!
here is how my oneplus 2 got bricked, I was on stock oxygen os 3.0 and rooted and I had twrp recovery 3.0.
So I did a full wipe on my device and when I was flashing the resurrection remix rom in twrp it said "Error 7" so then I reboot my phone and I was in a bootloop with no os.
I went back to twrp and flash the rom again and it not work. So then I tryed to transfer a file through my computer to my device and twrp was not recognizing it and tryed adb sideload and same thing and even in cmd I
typed "adb devices" and it not recognize it and I have the drivers installed, the 15 second 1click adb and fastboot.
And then I went to fastboot mode and then I tried first aid kit and the qualcomm mega unbrick guide and all the methods and still my oneplus 2 is not being recognized by PC and I am using the official oneplus 2 usb type c cable.
I have tried 2 windows 10 PC and I turned driver signniture enforcement off for the qualcomm drivers and nothing in device manager
I tried 1 Windows 7 PC and same thing and nothing in device manager
And I tried a Linux Mint virtual machine and I typed adb devices and fastboot device in the terminal and it was not recognizing it even though I installed the packages
So do you think the problem might be the cable? because it is the official one. But my device charges through the cable to and the cable was working before my phone got bricked. Or is it a driver problem? What do you guys think and please help and I will really appreciate it and thank you.
fahad999 said:
I have a bricked device and I would appreciate your help
here is how my oneplus 2 got bricked, I was on stock oxygen os 3.0 and rooted and I had twrp recovery 3.0.
So I did a full wipe on my device and when I was flashing the resurrection remix rom in twrp it said "Error 7" so then I reboot my phone and I was in a bootloop with no os.
I went back to twrp and flash the rom again and it not work. So then I tryed to transfer a file through my computer to my device and twrp was not recognizing it and tryed adb sideload and same thing and even in cmd I
typed "adb devices" and it not recognize it and I have the drivers installed, the 15 second 1click adb and fastboot.
And then I went to fastboot mode and then I tried first aid kit and the qualcomm mega unbrick guide and all the methods and still my oneplus 2 is not being recognized by PC and I am using the official oneplus 2 usb type c cable.
I have tried 2 windows 10 PC and I turned driver signniture enforcement off for the qualcomm drivers and nothing in device manager
I tried 1 Windows 7 PC and same thing and nothing in device manager
And I tried a Linux Mint virtual machine and I typed adb devices and fastboot device in the terminal and it was not recognizing it even though I installed the packages
So do you think the problem might be the cable? because it is the official one. But my device charges through the cable to and the cable was working before my phone got bricked. Or is it a driver problem? What do you guys think and please help and I will really appreciate it and thank you.
Click to expand...
Click to collapse
If your recovery mode is TWRP.. Then goto Mount -> Data
Then your computer will show your oneplus 2.
If still its not showing then update Driver Software of phone in device manager.
eldos777 said:
If your recovery mode is TWRP.. Then goto Mount -> Data
Then your computer will show your oneplus 2.
If still its not showing then update Driver Software of phone in device manager.
Click to expand...
Click to collapse
I tried both mount data on and off and still no luck, I have mtp enabled in twrp. I also checked device manager and there is nothing showing up. But twrp says that my phone is charging when my phone is connected to pc. I think the problem is probably the cable because the usb end of the cable looks sort of damaged, And I tried a Type-C OTG and put a usb on that and TWRP was not recognizing it
eldos777 said:
If your recovery mode is TWRP.. Then goto Mount -> Data
Then your computer will show your oneplus 2.
If still its not showing then update Driver Software of phone in device manager.
Click to expand...
Click to collapse
Holy crap the cable was the problem the whole time!!! I just went to the store and bought A new 3rd party USB-C cable and I plug it in to my pc and phone and immediately the pc installed drivers and now I could transfer files to TWRP from my PC!! It was a really hot sunny day today and I walked to the store which took 30 minutes and both ways 1 hour. I am so tired right now from the walk but it was worth it since my phone will be brought to life!! I am so happy right now!!!
fahad999 said:
Holy crap the cable was the problem the whole time!!! I just went to the store and bought A new 3rd party USB-C cable and I plug it in to my pc and phone and immediately the pc installed drivers and now I could transfer files to TWRP from my PC!! It was a really hot sunny day today and I walked to the store which took 30 minutes and both ways 1 hour. I am so tired right now from the walk but it was worth it since my phone will be brought to life!! I am so happy right now!!!
Click to expand...
Click to collapse
:good:
eldos777 said:
:good:
Click to expand...
Click to collapse
Thanks for your advice to for fixing the phone! I appreciate it!!