Hi everyone,
Sorry for my possible extremely noobish question, but can anyone direct me to some location from where I can download the s2vep driver?
Under Device Manager\Other Devices, it is listed as "s2vep" with an exclamation mark and "The drivers for this device are not installed. (Code 28)".
This happens ONLY while I booted my phone in ClockworkMod Recovery 6.0.2.8 and probably this is the cause of "adb.exe devices" not showing any device. If the phone has booted normally, I don't get this error and even more, adb shows the device.
Thank you very much,
Dyptorden said:
Hi everyone,
Sorry for my possible extremely noobish question, but can anyone direct me to some location from where I can download the s2vep driver?
Under Device Manager\Other Devices, it is listed as "s2vep" with an exclamation mark and "The drivers for this device are not installed. (Code 28)".
This happens ONLY while I booted my phone in ClockworkMod Recovery 6.0.2.8 and probably this is the cause of "adb.exe devices" not showing any device. If the phone has booted normally, I don't get this error and even more, adb shows the device.
Thank you very much,
Click to expand...
Click to collapse
I think you can only download samsung mobile usb driver. With it, your device will be recognised perfectly
Related
Hi,
I'm kind of a noob at this rooting stuff. I've looked ariund, done my research and everything but it never seems to go smoothly??..
I think the main problem is with the drivers. After following instructions the android drivers still said 'Android 1.0'. So I installed Pda net and then I got 'Android ADB Interface' drivers. Soo the thing is, after searching for 'adb devices' in cmd prompt, It says 'list of devices' but there's nothing in the list....?
For some reason it won't do any commands like 'adb reboot bootloader' or 'fastboot oem lock'. It says not found. I have installed all the sdk and packages...
Would really appreciate some help from you guys. I didn't think rooting would be so complex??...
Thanks
can you post screenshot??
Ok for some reason, after starting the cmd again today and typing adb devices, it has listed my device. But when I type 'fastboot oem lock' (because my bootloader is already unlocked) it says not found as shown in the screenshot.
Am I doing something stupid??...
70 views?... cant anyone help ... please..
soulja786 said:
70 views?... cant anyone help ... please..
Click to expand...
Click to collapse
If adb devices lists your device you're not in the boot loader, the ONLY place fastboot will recognize your device and function or you have a driver issue. You're either in recovery or booted up. Reboot into the boot loader to use fastboot.
If you get into the boot loader and fastboot still doesn't show your device it's a driver issue. Update the driver manually and point it to the SDK USB driver provided with the SDK.
For reference....
Booted into boot loader:
Fastboot OK
ADB NO
Recovery / Fully booted
Fastboot NO
ADB OK
Hi guys,
I really do think this is a driver issue... any idea on how to solve it? I do have PDA Net installed... ?
@krohnjw ... could you please clarify.. Im a bit lost.
Thanks!
Did you try something like oneclickroot?
http://forum.xda-developers.com/showthread.php?t=1138755
Well I also had a lot of issues trying to root my i9020t so let me try to help..
Phone will be recognized with ADB when u select enable debug on developer options. You ll see "Android ADB Interface" on SYS DRV.
On other hand , when U start phone on fasboot mode, it should install something like "Android Bootloader Interface " , if U keep seeing "Android ADB Interface" , its wrong, but took some time to realize that.
That happened to me when I was using WinXP x32 to root my phone, ironically thinking it would be more compatible an less prone to bugs... When done it on W7 x64 , my fastboot driver was discovered correctly (Android bootloader Interface) using x64 PDA drivers, and all went good then!
Hope this may help!
Hello,
Sorry if this has been asked before. I have a TF300T that I can see when the tablet is booted when I connect it to Windows (Win7 x64). However, when I boot to TWRP, I can't seem to access the device. It shows up in Device Manager as 'Transformer' with the typical yellow triangle. I can't seem to find any drivers that make it work. Any suggestions would be greatly appreciate. Thanks.
Aesrys said:
Hello,
Sorry if this has been asked before. I have a TF300T that I can see when the tablet is boohen I connect it to Windows (Win7 x64). However, when I boot to TWRP, I can't seem to access the device. It shows up in Device Manager as 'Transformer' with the typical yellow triangle. I can't seem to find any drivers that make it work. Any suggestions would be greatly appreciate. Thanks.
Click to expand...
Click to collapse
Just curious why you would need to connect your tablet to your computer while in the recovery mode? Honestly I don't think you can do this.
Aesrys said:
Hello,
Sorry if this has been asked before. I have a TF300T that I can see when the tablet is booted when I connect it to Windows (Win7 x64). However, when I boot to TWRP, I can't seem to access the device. It shows up in Device Manager as 'Transformer' with the typical yellow triangle. I can't seem to find any drivers that make it work. Any suggestions would be greatly appreciate. Thanks.
Click to expand...
Click to collapse
I have seen several posts using transformer 201 drivers to correct this problem. I'll try to locate them shortly and report back.
This mode will work with adb and sideload adb.
Looks like this is most popular now. http://forum.xda-developers.com/showthread.php?t=1766220
Note: For this version of twrp if adb fails update your adb.
Hey all,
I've got a new-to-me TF700. Got CROMBi-KK installed, which took some backflips as I could not get fastboot connectivity.
I'd like to be setup for NvFlash (but then never need it), so even though I don't need fastboot right now, I'm feeling the lack.
Data transfer works fine.
ADB (not fastboot) works fine (adb shell gets me a shell, etc, etc)
When I put the phone in fastboot/bootloader "fastboot devices" gets an empty response "fastboot reboot" gets no response.
In Win7 device manager, the TF700, which appears in the "portable devices" section normally when I plug it in, does not appear.
So... probably device drivers.
Have you had this problem on your w7/64 box? How did you fix it? Sorry, but "install linux" isn't all that helpful.
Thanks!
From a semi-related question I'd asked, berndblb mentioned
berndblb said:
Windows is infamous for driver problems.....
Connect the tab in fastboot and open device manager. Near the top you should have an entry for Android device, bootloader mode or something similar, and probably a yellow ! next to it.
Right click it and choose "update driver", let Windows search for it.
If you're lucky it'll install the driver by itself.
If not: What Windows version are you running?
Click to expand...
Click to collapse
Yep, I get an "unknown device" in the USB section when I connect a TF700 in fastboot. Win can't find an appropriate driver. I've tried (manually) ASUS_Android_USB_Drivers and Universal_Naked_Driver_0.72 (both, AFAIR, from the xda tf700 forums). Neither worked.
So... if you got this going, what driver did you use? Thx!
I have a Win7 32 bit laptop and this cool little tool installed the drivers for me:
http://forum.xda-developers.com/showthread.php?t=2588979
berndblb said:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
I'd installed that previously (easiest way to setup fastboot). Re-downloaded, re-installed. Went fine. Still no fastboot.
Unzipped the exe, looked at the drivers being installed - labeled "google". No google driver in the driver cache (so no device ever associated with it.)
Looked at the driver error again. Code 43. That means hardware or driver. I'd been taking it to mean driver, but... switched the USB cable to a port in the rear of the PC - and it worked.
Thanks!
So, for anybody with a similar issue, install the package above. If that doesn't work, maybe try a different USB port.
It works when booted into the OS but in recovery ADB is not recognized.
What drivers are you all using ?
stanglx said:
It works when booted into the OS but in recovery ADB is not recognized.
What drivers are you all using ?
Click to expand...
Click to collapse
On my mac ADB would not work in the stock recovery but it would work in CWM and fastboot. Think it is a driver issue.
I cant get it work anywhere and now I cant get stock recovery to work!
OK.. got the stock recovery - I didnt actually know you had to do volume up when at the "no command" screen..
and also I figured out how to fix the driver issue...
For anyone else having the issue you need to uninstall the driver until it shows up as Shield with the exclamation. You must be in the recovery in an area like sideload.. (Not in android OS)
Then Update Driver, Browser and then click on "Let Me Pick from a list on my computer"... find Android then select "Android Composite ADB Interface".
Now the driver works in ADB and in the OS
stanglx said:
OK.. got the stock recovery - I didnt actually know you had to do volume up when at the "no command" screen..
and also I figured out how to fix the driver issue...
For anyone else having the issue you need to uninstall the driver until it shows up as Shield with the exclamation. You must be in the recovery in an area like sideload.. (Not in android OS)
Then Update Driver, Browser and then click on "Let Me Pick from a list on my computer"... find Android then select "Android Composite ADB Interface".
Now the driver works in ADB and in the OS
Click to expand...
Click to collapse
Thank you so much for this, I was pissed that I couldn't sideload.
On another note, does anybody see their device without the driver as "wx_un_mo"? I didn't think this was a valid model number considering the post at http://forum.xda-developers.com/shield-tablet/general/shield-tablet-otas-t2847116 says it's a modem/wifi version.
Yes.. it was showing up as this for me too when in recovery but when in android OS it was fine... that is just the device ID . I kept uninstalling it until it showed as shield tablet with an ! in front of it. Now I think that was over kill.
Make sure your using the Nvidia Windows driver... There are two drivers that load
1. Bootloader driver
2. ADB Composite Driver
1 loads in fast boot only (bootloader)
2 loads in andorid OS (no issues typically) but when in recovery you have to force the driver install. If it doesnt work when in android OS (ie Lollipop, etc.) then do the same.. pick ADB composite driver.
MidgetMob said:
Thank you so much for this, I was pissed that I couldn't sideload.
On another note, does anybody see their device without the driver as "wx_un_mo"? I didn't think this was a valid model number considering the post at http://forum.xda-developers.com/shield-tablet/general/shield-tablet-otas-t2847116 says it's a modem/wifi version.
Click to expand...
Click to collapse
stanglx said:
Yes.. it was showing up as this for me too when in recovery but when in android OS it was fine... that is just the device ID . I kept uninstalling it until it showed as shield tablet with an ! in front of it. Now I think that was over kill.
Make sure your using the Nvidia Windows driver... There are two drivers that load
1. Bootloader driver
2. ADB Composite Driver
1 loads in fast boot only (bootloader)
2 loads in andorid OS (no issues typically) but when in recovery you have to force the driver install. If it doesnt work when in android OS (ie Lollipop, etc.) then do the same.. pick ADB composite driver.
Click to expand...
Click to collapse
Yea I figured out the driver install fortunately, I was just curious as to why it was showing up as such. I didn't think that the specific model number was valid and was curious if anyone else had the same thing.
Hi all,
sorry if there is plenty of these threads already floating around but wasnt able to find a relevant one to my problem. I'm hoping someone here might be able to help.
This is the primary XZ rooting guide i have been following, with other supplimentary guides 1 & 2
These have been my steps:
- Managed to successfully update fastboot driver with "android_winusb.inf-file" from 'Google USB Driver' within android studio.
- Unlocked bootloader
- Installed AndroPlus Kernel sucessfully "fastboot flash boot boot.img"
Now went to reboot device as stated by instructions (mistake) and now the device is not recognized in cmd "waiting for device". I've replugged the usb in multiple ports and the device shows up as "android" in devices and printers. I go to update the android "SOMC Flash Device" to the platform tools directory but makes no difference in cmd. Still "waiting for device". In Device Manager there is no sign of the device either.
When the phone is turned on it shows your device has been "unlocked and cant be trusted will reboot in 5 seconds" then proceeds to xperia logo and freezes. With no recoveries theres not much options.
Is there a way to continue from here or even return to a previous state? It seems like i hit a brick wall. Please help
MugenG said:
Hi all,
sorry if there is plenty of these threads already floating around but wasnt able to find a relevant one to my problem. I'm hoping someone here might be able to help.
This is the primary XZ rooting guide i have been following, with other supplimentary guides 1 & 2
These have been my steps:
- Managed to successfully update fastboot driver with "android_winusb.inf-file" from 'Google USB Driver' within android studio.
- Unlocked bootloader
- Installed AndroPlus Kernel sucessfully "fastboot flash boot boot.img"
Now went to reboot device as stated by instructions (mistake) and now the device is not recognized in cmd "waiting for device". I've replugged the usb in multiple ports and the device shows up as "android" in devices and printers. I go to update the android "SOMC Flash Device" to the platform tools directory but makes no difference in cmd. Still "waiting for device". In Device Manager there is no sign of the device either.
When the phone is turned on it shows your device has been "unlocked and cant be trusted will reboot in 5 seconds" then proceeds to xperia logo and freezes. With no recoveries theres not much options.
Is there a way to continue from here or even return to a previous state? It seems like i hit a brick wall. Please help
Click to expand...
Click to collapse
Installed adb SystemWide?
adb drivers are Installed corrcetly? , better to reinstall them.