Hello,
I wanted to update the ROM I am using, went through all of the steps and ran into a "set_metadata_resursive: some changes failed (Status 7)" error - this is apparently caused by an old version of the recovery. I am using CWM V6.0.2.5 (very outdated) so this seems correct. I already did a full wipe and currently only have a single rom.zip file which is unflashable because of the error.
I was unable to connect to computer using the USB Mass Storage on any computer (Windows). I used to get the error 28 (Drivers are missing) message in Device Manager. I tried to install Google USB drivers, Windows was however unable to find them when I point it to the directory containing the drivers. I figured out the Hardware ID and modified the Google USB drivers to install.
Now I have my Nexus connected to my laptop, it shows up as an Android Composite USB Interface and nothing happens when I use the 'mount USB storage' option. What should I do next?
I am using the 9023 version of Nexus S with the v6.0.2.5 version of CWM.
Hardware ID from Device Manager: USB\VID_18D1&PID_D001&REV_0231
Try Universal Naked Driver and install a new recovery using fastboot.
http://forum.xda-developers.com/showthread.php?t=2263822
Resolved
Thank you, that worked
This is now resolved.
here how usb is working on me :http://forum.xda-developers.com/showpost.php?p=48666642&postcount=227
Related
Hi
Some background. Like many, I bought a TF700T and like a fool installed the OTA update to JB. I then downgraded, rooted in .30, then upgraded again and flashed SU to keep root in JB. I am now, therefore, running the stock OTA JB ROM, rooted. My bootloader is also unlocked.
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
I want to get files on and off the *internal* storage (I don't have an external sdcard)
Things i have tried:
- Using a different USB port
- Using one of the USB ports on the back of the machine, instead of the front ones
- Uninstalling the MTP drivers
- Using the ASUS drivers from the website
- Cleaning out all my old unconnected USB devices (show devmgr_unconnected_devices=1 or whatever) and uninstalling all THOSE drivers
- Cleaning out with USBDeview
- Fresh install of the OTA ROM, after a data wipe/factory reset and wiping cache and dalvik
The only things I haven't tried are a new USB cable (damn you ASUS and your proprietary connector), and a clean install of Windows (major ballache).
Any ideas about what I could do to sort this would be greatly appreciated.
Since I only want to be able to move files on and off the device, I tried a workaround. I tried mounting the sdcard (internal) in windows manually through adb but the command I used to use on my old S2 through adb shell (echo dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file) but it errors with No such path or similar. I'm unsure if the mount points are different (I guess they will be, can anyone help with telling me what the mount point for the internal emmc is on the tf700?)
Really hope someone will be able to help me!
Thanks in advance guys
I'm in a similar situation except I'm not rooted or unlocked. I've tried just about all the steps you've mentioned w/ no luck. I've even tried to three different PCs running XP, Vista, and 7 and get the same result. What makes the situation even worse is my brand new 32GB microSD card won't read on my desktop as well.
m000se said:
Hi
Some background. Like many, I bought a TF700T and like a fool installed the OTA update to JB. I then downgraded, rooted in .30, then upgraded again and flashed SU to keep root in JB. I am now, therefore, running the stock OTA JB ROM, rooted. My bootloader is also unlocked.
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
I want to get files on and off the *internal* storage (I don't have an external sdcard)
Things i have tried:
- Using a different USB port
- Using one of the USB ports on the back of the machine, instead of the front ones
- Uninstalling the MTP drivers
- Using the ASUS drivers from the website
- Cleaning out all my old unconnected USB devices (show devmgr_unconnected_devices=1 or whatever) and uninstalling all THOSE drivers
- Cleaning out with USBDeview
- Fresh install of the OTA ROM, after a data wipe/factory reset and wiping cache and dalvik
The only things I haven't tried are a new USB cable (damn you ASUS and your proprietary connector), and a clean install of Windows (major ballache).
Any ideas about what I could do to sort this would be greatly appreciated.
Since I only want to be able to move files on and off the device, I tried a workaround. I tried mounting the sdcard (internal) in windows manually through adb but the command I used to use on my old S2 through adb shell (echo dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file) but it errors with No such path or similar. I'm unsure if the mount points are different (I guess they will be, can anyone help with telling me what the mount point for the internal emmc is on the tf700?)
Really hope someone will be able to help me!
Thanks in advance guys
Click to expand...
Click to collapse
First check make sure you have your "USB debug" and "Unknow software" checked in settings. Then go here and install the pda software for your windows. Once installed, it will installed all the driver for your tab automatically. You don't need to use the software, you can uninstall it later, but the driver will stay.
http://junefabrics.com/android/download.php
I haven't picked up a TF700 yet (out of stock locally), so these are just general suggestions...
From adb, shell into the OS (adb shell) and list the directories to try and determine their structure. If the device is booted, the internal SD should already be mounted.
I would start by looking for the following folders:
/sdcard
/mnt/sdcard
/data/media
m000se said:
Hi
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
Click to expand...
Click to collapse
I had the same problem getting MTP to work on old XP machine. The following worked for me...see post #12
http://www.transformerforums.com/fo...ormer-manual-usb-drivers-sync-software-2.html
Thanks for the replies, everyone. I installed PDANet and was initially hopeful once the drivers started installing. Sadly, Windows still doesn't see my device.
adb shell-ing into the device --> mounts
This lists /dev/fuse as the internal storage. I can't echo this to /sys/devices/usb_mass_storage/lun0/file because when I do it returns "No such file or directory"
The solution posted as working on XP machines doesn't work either.
This is seriously annoying. I'm tempted to just give in and get myself a 32GB SDHC and card reader and just use that instead - at least that way I can move the files across with Root Explorer or something...
i try to flash a rom and failed in the middle.
i have cwm version 6, while i select "mount USB storage" nothing happen,
while the recovery menu is open i have adb access but if i use "push" command it get stuck.
on the bootloader menu i dont have access to fastboot, i get on windows "usb device not recognized" under universal serial bus controllers in device manager.
any help here?
doesn't belong here!!!!
can the admin move it to where it belongs?
can the admin move it to where it belongs?
Fix your fastboot issue by properly installing the drivers (I suggest PDANet Android drivers, usually work fine) then flash Clockworkmod Recovery 6.0.1.0 or earlier OR TWRP latest version. The later versions of CWM Recovery have issues mounting USB.
Then mount USB, transfer a rom and flash away.
Edit: Oh and can't you restore your nandroid backup?
i think the problem is the cable driver is not installed properly ..
Keep calm, and check your driver or cable
fixed!
strangely the device gave the same error in my laptop and pc in all USB connection instead of 1.
only in my pc in specific USB connection at the back it works! i reflashed old cwm and it's all good now, thanks!
Hi all,
I was having a strange problem with my USB dropping out when using the NEWER recovery (TWRP and Philz). Which meant I couldn't push files via ADB or Sideload. Here is my solution....
Before starting
I am using Windows 7
Download Google USB driver
Make sure you have TWRP 2.7.1.1 loaded as your recovery
You may have slightly different devices show up maybe, but this is what mine showed...
Open device manager
Plug phone in and power up to bootloader
Device manager should show 'Android Device' or similar
Open recovery
**This is where my USB was dropping out**
Make sure TWRP 2.7.1.1 loads
Look at device manager and should show 'One Mini' with a yellow exclamation mark
I tried updating the drivers automatically and browsing to the Google USB folder that we downloaded above but just kept saying 'device driver loading failed'.
The only way I found worked was
Right click 'One Mini' and update driver
Browse my computer for driver software
Let me pick from a list of device drivers
If you have Android device listed click that, if not choose Portable device.
Click 'Have disk' and locate the Google USB Driver folder and should be able to load the .inf file.
Click from the list ADB USB device and click ok.
This should load your device and install properly.
You shoud now be able to use ADB and Sideload in Recovery now.
Let me know if this works or not as there are a couple of bits that I can't replicate as the driver is already there!
**My First Post**
I am trying to resurrect my HTC One S. I accidentally wiped it without making a backup and using CMW.
The main issues I am having are as follows:
- E:/cannot mount sdcard
- When plugged into a computer through usb, Windows gives me a "Device Descriptor Request Failed" box and says my device is unrecognisable (code 43).
- I have tried but cannot get the device to show up in adb. (I have installed many different drivers, HTC, google's driver from sdk, etc.)
Is this device as good as garbage now? I can load it into CMW and in bootloader just fine.
If more information is needed please let me know.
Thanks in advance for the help
Hello there,
I'm running CM11 20141223 NIGHTLY on my XT1033, and everything is working fine so far, with the exeception of USB communication. I develop my stuff on my desktop, which is running W7. Consider the following scenarios:
1) If I plug it in MTP mode (debugging deactivated), it won't find. Windows tries to install a USB Composite Device driver and fails.
2) If I plug it in PTP mode (debugging still deactivated), Windows installs a Moto G driver and access the DCIM camera folder normally (that's what I've been using to "push" files into it, and then move it with file manager with temp su access).
3) In both MTP and PTP mode, but with debugging activated, Windows detects it as a USB Composite Device. On Device Manager it shows up with the yellow triangle warning icon, but I can't seem to update it (tried with the extra Android drivers that comes with ADT).
4) Neither adb nor fastboot can detect the device. Which is weird because on my notebook, running windows 8.1, I got the same situation but adb (only, fastboot still can't) can detect it.
5) I also installed Koush universal ADB Drivers on both machines.
Does anyone have some insight on the matter? Should I get rid of Koush?
I don't intend on upgrading to CM12 anytime soon. In fact, I did it some weeks ago, but I'm more confortable with CM11 so I rolled back to it.
Hoping it's okay to bump my thread after a month.
Does anyone know what to do in this situation?
Thanks!
jorge_quintanilha said:
Hello there,
I'm running CM11 20141223 NIGHTLY on my XT1033, and everything is working fine so far, with the exeception of USB communication. I develop my stuff on my desktop, which is running W7. Consider the following scenarios:
1) If I plug it in MTP mode (debugging deactivated), it won't find. Windows tries to install a USB Composite Device driver and fails.
2) If I plug it in PTP mode (debugging still deactivated), Windows installs a Moto G driver and access the DCIM camera folder normally (that's what I've been using to "push" files into it, and then move it with file manager with temp su access).
3) In both MTP and PTP mode, but with debugging activated, Windows detects it as a USB Composite Device. On Device Manager it shows up with the yellow triangle warning icon, but I can't seem to update it (tried with the extra Android drivers that comes with ADT).
4) Neither adb nor fastboot can detect the device. Which is weird because on my notebook, running windows 8.1, I got the same situation but adb (only, fastboot still can't) can detect it.
5) I also installed Koush universal ADB Drivers on both machines.
Does anyone have some insight on the matter? Should I get rid of Koush?
I don't intend on upgrading to CM12 anytime soon. In fact, I did it some weeks ago, but I'm more confortable with CM11 so I rolled back to it.
Click to expand...
Click to collapse
Have you tried Motorola's drivers? It installs separate drivers for adb, fastboot, mtp. https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/97326/p/30,6720,9050