Hello,
I have previously rooted my nexus 7 32 gb with the exact same computer that I have now and with the same exact software (Wugfresh Toolkit 1.6.2) and when I was finished previously, I set the drivers back to their stock google drivers that would be used as if I didn't change any of the drivers. I recently had issues updating to 4.2.2 and had to flash back a stock rom to get everything working again, now I have to re-root and re-flash my recovery.
When I now follow the same exact steps now, I keep installing an android composite adb interface instead of the android adb interface, which I know you need to restart the bootloader. I have tried rebooting after every step, removing every android driver, nearly everything and keep getting the google made android composite adb interface instead of Wug's android adb interface. I am running windows 7 64 bit. So anyway, does anyone have any ideas, and yes I have looked at other threads for this, but none of them really give me the answer to this question.
Thanks
Fishwithadeagle said:
Hello,
I have previously rooted my nexus 7 32 gb with the exact same computer that I have now and with the same exact software (Wugfresh Toolkit 1.6.2) and when I was finished previously, I set the drivers back to their stock google drivers that would be used as if I didn't change any of the drivers. I recently had issues updating to 4.2.2 and had to flash back a stock rom to get everything working again, now I have to re-root and re-flash my recovery.
When I now follow the same exact steps now, I keep installing an android composite adb interface instead of the android adb interface, which I know you need to restart the bootloader. I have tried rebooting after every step, removing every android driver, nearly everything and keep getting the google made android composite adb interface instead of Wug's android adb interface. I am running windows 7 64 bit. So anyway, does anyone have any ideas, and yes I have looked at other threads for this, but none of them really give me the answer to this question.
Thanks
Click to expand...
Click to collapse
There are new drivers for adb. Try looking for them in wug's toolkit thread.
Related
So The toolkit is not loading drivers from the menu, I am familiar with using it, version 4.0.0. Used the pdanet download it errors out now, Its install was removing the wireless when installed in the last couple of days.
I have had this all working with the pdanet, but had to do several restores to get wireless back, each one after loading the pdanet again and loosing wireless.
Running Android 4.2.0 rooted and boot unlocked.
So I was able to load the adb drivers with the NexusRoot kit 1.6.1 WugFresh
frankleee said:
So The toolkit is not loading drivers from the menu, I am familiar with using it, version 4.0.0. Used the pdanet download it errors out now, Its install was removing the wireless when installed in the last couple of days.
I have had this all working with the pdanet, but had to do several restores to get wireless back, each one after loading the pdanet again and loosing wireless.
Running Android 4.2.0 rooted and boot unlocked.
So I was able to load the adb drivers with the NexusRoot kit 1.6.1 WugFresh
Click to expand...
Click to collapse
Still can't get mine to work.. and i started with Wug in win8 x64
Phk said:
Still can't get mine to work.. and i started with Wug in win8 x64
Click to expand...
Click to collapse
There is a thread on here someplace - sorry, you'll have to search for it (I don't remember where it is) - but the gist of it is that Windows 8 mandatory requirement of using signed drivers is the root of the problem.
The thread in question details a rather involved method for turning off the signed driver requirements in Windows 8.
An alternative to this approach - which is arguably at least as much effort, if not more - is to use your PC hardware without Windows 8: boot a version of Linux (such as Ubuntu) from a USB key. The same thing could be accomplished from a Linux "Live CD" so long as you keep copies of the Linux versions of fastboot & adb (plus any dynamically-linked shared libs not in the distro as needed) lying around.
(Yes, I realize that suggesting the latter to someone that uttered the word "toolkit" is probably a waste of typing. But the Windows 8 issue is generic to everyone, and others besides the OP may read this post.)
[Edit] See this old post by WugFresh
http://forum.xda-developers.com/showpost.php?p=33288005&postcount=1368
and possibly a couple posts after it in the same thread. I'm not sure if this is the issue or not, but it is clearly evident that WugFresh has been aware of it for some time.
Is there some reason you are not asking this question in WugFresh's thread?
Excellent.... It works now
Thanks
Phk said:
Excellent.... It works now
Thanks
Click to expand...
Click to collapse
Good news.
For the benefit of others, what steps did you take?
uninstalled the driver several times until the option "delete driver" also appears in the uninstall
reboot
plug cable
manually choose new driver
Background, I've done this many times, I currently have the latest CWM installd on my manta and I change ROMS and Kernels pretty frequently (I just like trying new things).
Recently I tried the preview build of Ubuntu Tablet and I can't get it to boot. Problem is I don't have any other zips on my internal storage to flash back to.
No problem I thought, I'll just side load using adb and the sideload function of CWM.
I've done it before and it worked perfectly but now I'm getting an error.
I do have my rom .zip in the correct foler (platform-tools) and I am running my command prompt from the right place.
If I do adb devices I do see my tablet serial number and it says sideload, just like it should.
But when I use the adb sideload MYROMNAME.zip I get an error that reads, *Can't read `sideload`*
If I try to use adb push MYROMNAME.zip /sdcard/ it says error:closed.
I tried completely removing my ADT bundle and redownloading the latest version and reinstalling everything including the google usb driver but I get the exact same error... I'm using win 7 32 bit.
Any ideas??? My tablet currently is bricked until I find a solution.
parakalien said:
Background, I've done this many times, I currently have the latest CWM installd on my manta and I change ROMS and Kernels pretty frequently (I just like trying new things).
Recently I tried the preview build of Ubuntu Tablet and I can't get it to boot. Problem is I don't have any other zips on my internal storage to flash back to.
No problem I thought, I'll just side load using adb and the sideload function of CWM.
I've done it before and it worked perfectly but now I'm getting an error.
I do have my rom .zip in the correct foler (platform-tools) and I am running my command prompt from the right place.
If I do adb devices I do see my tablet serial number and it says sideload, just like it should.
But when I use the adb sideload MYROMNAME.zip I get an error that reads, *Can't read `sideload`*
If I try to use adb push MYROMNAME.zip /sdcard/ it says error:closed.
I tried completely removing my ADT bundle and redownloading the latest version and reinstalling everything including the google usb driver but I get the exact same error... I'm using win 7 32 bit.
Any ideas??? My tablet currently is bricked until I find a solution.
Click to expand...
Click to collapse
Grab one of the many toolkits from the development sections and flash the factory image. Then u can just start over. I've had to do this myself, thanks to the first release of Ubuntu for our tablets.
Sent from my Nexus 10 using Tapatalk HD
newellj79 said:
Grab one of the many toolkits from the development sections and flash the factory image. Then u can just start over. I've had to do this myself, thanks to the first release of Ubuntu for our tablets.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Thank you very much!! This fixed it and was super easy.
Appreciate your help getting me out of a sticky situation!
Last week my nexus 7 asked my permission to download kit kat, I said yes and it crashed and now I only get the google opening page it was rooted by my brother who owned it before me, the tablet is not recognized when I plug it into my computer either, can anyone point me to where I can find the drivers online and the os as well. Thank you in advance.
Install Wug toolkit and install the drivers that way... You can also return to stock via the toolkit.
Hi,
I'm currently ran into a very frustrating driver problem with my nexus and i was looking for some help.
I an having trouble with my nexus when i was in the middle of rooting it i had just unlocked it using Wugfresh's root toolkit when the drivers i used were no longer recognized it as as an ADB device and i couldn't carry on my rooting, i have tried reinstalling the drivers multiple times and it doesn't work and it has gotten to a point where it names it as unrecognized so i cannot even transfer files to it anymore, could anyone help me.
P.S. if you want more details about what i did ask me.
Benthrax said:
Hi,
I'm currently ran into a very frustrating driver problem with my nexus and i was looking for some help.
I an having trouble with my nexus when i was in the middle of rooting it i had just unlocked it using Wugfresh's root toolkit when the drivers i used were no longer recognized it as as an ADB device and i couldn't carry on my rooting, i have tried reinstalling the drivers multiple times and it doesn't work and it has gotten to a point where it names it as unrecognized so i cannot even transfer files to it anymore, could anyone help me.
P.S. if you want more details about what i did ask me.
Click to expand...
Click to collapse
Ran into same problem with this ****Wug's thing. Trash it and use Skipsoft Unified Android Toolkit instead. Took me a long time to erase all traces of Wurst. You need to uninstall and delete the Wurst' driver in device manager for Skipsoft to work.
Hey guys,
Got a Nexus Player running Android 6.0.1 Build MMB29M i am trying to root
i grabbed the SkipSoft toolkit and installed the koush universal ADB driver,
Fastboot worked fine and i unlocked the bootloader, but ADB just wont find the nexus player
USB Debugging is on*
after trying universal ADB, PDAnet, Official Google USB driver, lots of resetting in between and uninstalling etc etc, one of them finally worked, not sure which one but im afraid to touch anything to find out -_-
I am running into the same issue. Can't get ADB to find my nexus player at all.
kfernandes29 said:
I am running into the same issue. Can't get ADB to find my nexus player at all.
Click to expand...
Click to collapse
I had a similar issue. Turned out to be the version of ADB supplied with the toolkit was old, had to download the latest version.