Recently bought a laptop and it have windows 8. Are there any drivers, adb, root method for the Nexus 7 or any other android device for windows 8?
I know the this windows is too new. But I figure as people that make this kind of stuff would update to work on windows 8. Or I would it work If I download them from windows 7?
gypsy214 said:
Recently bought a laptop and it have windows 8. Are there any drivers, adb, root method for the Nexus 7 or any other android device for windows 8?
I know the this windows is too new. But I figure as people that make this kind of stuff would update to work on windows 8. Or I would it work If I download them from windows 7?
Click to expand...
Click to collapse
I've read that there are issues with fastboot on Win8. Specifically when trying to fastboot flash stock images etc. Your results may vary, but I think it's too new yet for the support to be there. It'll come with time, but right now it's been iffy.
There are no issues with windows 8...fastboot works good...refer to this
http://forum.xda-developers.com/showthread.php?p=34085361#post34085361
look at my post there(post 7)
I rooted from Windows 8 yesterday. Had some trouble getting it to boot from pushed images with the toolkit. Worked around it by doing the unroot option to get into CWM, where i flashed SuperSU and it worked great
Related
hi,
im in need of help, i just bought my nexus 7, within the first hour of course i wanted to unlock, root and flash CWM on it, this is what happened, i downloaded the files necessary, went on cmd on my computer and fallowed some simple directions and i unlocked it, the problem started when i couldnt copy and paste the CWM file onto my nexus 7 it just wouldnt copy, so i went to do install the drivers for my nexus 7 on device manager, and my computer sees my nexus 7 as my previous tablet samsung tab 2, now after trying to make it work, my computer wont recognize the device at all,
so im trying to get it back to stock, factory rom when everything was working okay, because i think i somehow renamed the device as my old tablet samsung tab 2, im suprised as it still works fine, however i cant transfer files over, and i cant root because the toolkit program on my computer wont recognize the nexus 7, if there is a simple method to fix this problem or bring my nexus 7 to the way i bought it please do tell, it will be highly appreciated,
Thanx
It sounds like the drivers got messed up.
Get http://forum.xda-developers.com/showthread.php?t=1766475
it includes a tool & instructions for fixing the drivers under the "full driver installation guide".
You can also download a stock image here https://developers.google.com/android/nexus/images#nakasi
I think uninstalling the previous drivers with USBDview (step 1 in the full driver installation guide) will help.
Note that while it says "guide" it includes buttons for launching included programs and scripts.
Use Wugs toolkit, click on the big button to install drivers manually/automatic I think is how it's labeled.
One of the first step offers a tool to view and delete drivers and it even specifically tells you which drivers to delete to prevent it being misrecognized and/or having conflicts.
Once you've uninstalled those just follow the instructions to install the correct ones. Once they're uninstalled you will see it in device manager as something else until you install the new drivers.
Sent from my ADR6425LVW using xda premium
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
So let me start by saying I'm not new to this. However I generally stick to nexus devices, so I haven't had to deal with Odin before. I have a Mac, and I have come to realize that Odin is a windows only program. Is there a good alternative to Odin for macs? I've seen heimdall mentioned, but from what I can tell, its buggy, and I haven't been able to find a good tutorial. What I'm looking for is a way to restore the device from a situation like a bootloop (so mobile Odin won't work)
Sent from my Nexus 7 using Tapatalk 4 Beta
Fu5ion said:
So let me start by saying I'm not new to this. However I generally stick to nexus devices, so I haven't had to deal with Odin before. I have a Mac, and I have come to realize that Odin is a windows only program. Is there a good alternative to Odin for macs? I've seen heimdall mentioned, but from what I can tell, its buggy, and I haven't been able to find a good tutorial. What I'm looking for is a way to restore the device from a situation like a bootloop (so mobile Odin won't work)
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
you could:
- use bootcamp to install and boot into windows to use ODIN in a windows environment
- run a virtual windows machine in OSX (i've tried this, it was too much trouble to get the usb devices to mount in virtual machine)
- find someone with a windows pc that you can use
- use Heimdall while booting from a live ubuntu cd
I tried a few times in internet cafes but was unable to root this phone, i got my young son a PC for xmas as his old one was broken, it runs windows 10, im wondering if anyone has successfully rooted this phone using windows 10, do you follow the same procedure or anything different?
anyone know at all?
of course, no difference to win8 or win 7, install samsung usb drivers if needed, and use odin to flash custom recovery, then flash su zip, done!
I have rooted mine with same procedures arter suggested in win 10 worked well
it works great too with odin and CF-Auto-Root
thanks folks ill give this a go tomorrow evening if i can drag the young lad off the computer lol
First, I'm not a newb, but I'm at my wits end so I'm swallowing my pride and posting this here.
I recently wiped my hard drive and reinstalled Windows 10. Prior to that Windows could see my v20, I could transfer files and ADB worked fine.
I installed command line tools to install ADB/drivers and tried both LG mobile 4.20 drivers and even tried the Intel drivers. Along the way I dusted off usbdeview to clear out the drivers and start over so likely further screwed things up.
I was able to eventually get ADB functional but no matter what I did the device wouldn't show up as a portable device under My PC.
I've finally said screw it and am currently reinstalling windows 10 from scratch for a fresh start.
So, looking for input as to the best way to proceed on fresh Windows install. Is best way to install adb/adb drivers by installing command line tools rather than full android studio? Does it matter what order I install LG drivers/ADB?
I'm running the notsostock 5.5 dirtysanta rooted on a verizon v20.
Thanks.
I haven't been able to get it to show as a portable device since flashing the NotSoStock rom. I'm on Windows 7, it was visible just fine prior to flashing and I haven't done anything to the computer in the meantime.
I've been assuming it was something goofy in the rom rather than windows drivers... It just hasn't been a big enough deal for me to monkey with, I don't often need that, and adb still works fine so I just push/pull stuff if I need to move anything...
ZachJohnson said:
I haven't been able to get it to show as a portable device since flashing the NotSoStock rom. I'm on Windows 7, it was visible just fine prior to flashing and I haven't done anything to the computer in the meantime.
I've been assuming it was something goofy in the rom rather than windows drivers... It just hasn't been a big enough deal for me to monkey with, I don't often need that, and adb still works fine so I just push/pull stuff if I need to move anything...
Click to expand...
Click to collapse
I came to the same conclusion about 4 hours ago. It was the NotSoStock rom that broke it. I wiped my v20 and installed the WETA rom and everything works perfectly. The dialer lock issue I had with that rom is gone. The hotspot issue is gone, etc. I've only been on it for a few hours, but it's definitely better than what I was on before.