Has anyone been able to successfully root their Nexus 7 on a Mac using Parallels? Or VM Ware? Both rooting methods in the development section are Windows only, so a little cautious about trying it on a virtual machine. Any help would be appreciated.
Forget Parallels just have the Android SDK and Superboothttp://forum.xda-developers.com/showthread.php?p=28267712
Sent from my i777 using xda app-developers app
Agreed, forget VM solutions on OS X.
Install the Mac sdk, open up Terminal and have a play with adb and fastboot, plenty of guides around for the details
I tried using one click root (written for windows), with XP on my iMac via VMWare. It did not work. The problem relates to tablet could not reconnect in time to virtual machine in between reboots.
I ended up going to a Windows laptop, and it worked.
if you're comfortable with adb & fastboot, can search and read, you dont need one clicks or windows.....
tehSmoogs said:
if you're comfortable with adb & fastboot, can search and read, you dont need one clicks or windows.....
Click to expand...
Click to collapse
+1
Sent from my i777 using xda app-developers app
Well, I'm not but I think I'm about to be! Reading about and installing adb on my Mac now. That part was easy! We'll see how it goes from here. Thanks.
I use Parallels on my Mac ALL the time and have never had an issue. In fact, if you have multiple devices and worry about conflicting drivers simply copying the VM and having one for each device is the way to go. Do it all the time and I have MANY devices from different manufactures.
Edit.... BTW ... I used parallels to s-off an HTC Rezound which had many steps where the device would reboot. Re-connecting to the VM was never an issue for me.
I rooted LGL21 using Parallels on Macbook(OS X)
I'm using Parallels 9 on Macbook(OS X) and ther is Windows7 Pro.
I made trial and error using Android SDK and LG's ADB, and the beginning did not reach well.
Windows was not able to find LGL21.
but I changed USBcable 1m to 10cm
But Windows came to be able to find LGL21 when I changed a USBcable 1m to 10cm.
I thought the cause to be a ADB driver, but might be a problem of the hardware.
When you change hardware and try it, how about?
However, I'd changed both the hardware and the ADB at the same time, and the connection of the USB port changed ! I confirm an exact cause from now on !
Related
Long time abuser of Android devices and very happy with the SGS2. However, as Mac user, the tools required to mod the SGS2 are not Mac friendly. So I'm turning to the excellent minds of the XDA community to help me enjoy my device.
I run virtualization software which in the past was more than sufficient for any device I wanted to root, hack, etc. So using VMware installed Kies and downloaded the drivers fine (I've even manually installed the drivers to make sure I got them all). The problem primarily is with Odin. In download mode, the device is not recognized. So I figured it was VMware so I tried Parallels and Virtualbox with the same results. Even tried Heimdall which is supposedly more VM friendly but no luck.
Am I just overlooking something or do I really need to use a PC? Your thoughts would be greatly appreciated. TIA
Bootcamp. Doesn't work vm.
Sent from my GT-I9100 using XDA App
cdd543 said:
Bootcamp. Doesn't work vm.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Are you using it with bootcamp?
jlevy73 said:
Are you using it with bootcamp?
Click to expand...
Click to collapse
I used Odin through bootcamp with no problems at all.
But heimdall should run natively on mac and Linux, you just need mono.
? I thought EVERYTHING sucked for a MAC user....
jlevy73 said:
Long time abuser of Android devices and very happy with the SGS2. However, as Mac user, the tools required to mod the SGS2 are not Mac friendly. So I'm turning to the excellent minds of the XDA community to help me enjoy my device.
I run virtualization software which in the past was more than sufficient for any device I wanted to root, hack, etc. So using VMware installed Kies and downloaded the drivers fine (I've even manually installed the drivers to make sure I got them all). The problem primarily is with Odin. In download mode, the device is not recognized. So I figured it was VMware so I tried Parallels and Virtualbox with the same results. Even tried Heimdall which is supposedly more VM friendly but no luck.
Am I just overlooking something or do I really need to use a PC? Your thoughts would be greatly appreciated. TIA
Click to expand...
Click to collapse
I have not got a mac, but have done the following:
ODIN on native PC
ODIN in VMware virtual machine (host = windows xp, guest = windows xp)
Heimdall in Windows (native)
Heimdall in VMWare virtual machine (host = windows xp, guest = ubuntu 11.04)
I don't know what the drivers are like on VMWare for OSX... But I had no issues in any of the above, beyond occasional glitches with ODIN that are likely due to poor coding, or just limited error checking, given it's internal software not really intended for our use.
Bootcamp is the way to go. I also tried with vmware but I think there is some strange stuff with network sharing which messes up the usb connection, both to osx and the vm.
Sent from my GT-I9100 using XDA Premium App
Thanks everyone for your quick replies. Bootcamp did the trick.
After searching a bit it seems most if not all rooting methods require the use of a Windows machine. Are there any resources for us mac users in terms of rooting the TF?
I'm not sure if there is an nvflash version for Mac. The nvidia developer's website show flashing features for Win and linux. I assume this means nvflash.
sent from my cyanogen(mod) vision
eep2378 said:
After searching a bit it seems most if not all rooting methods require the use of a Windows machine. Are there any resources for us mac users in terms of rooting the TF?
Click to expand...
Click to collapse
I've done it with Windows Seven on Parallels 6.
Be carefull to assign at the first time the asus usb to virtual machine in static way, otherwise you can loose the connection during the procedure and the software re-ask you where do you want to connect the usb...
DLuke77 said:
I've done it with Windows Seven on Parallels 6.
Be carefull to assign at the first time the asus usb to virtual machine in static way, otherwise you can loose the connection during the procedure and the software re-ask you where do you want to connect the usb...
Click to expand...
Click to collapse
I do have vmware on my Mac running win 7. Assign asus to virtual machine in static way? How would I go about that?
Sent from my GT-I9000 using XDA App
I never used VMWare...
But in parallels, with vm running, when i insert something in the usb, it prompt where the device will be seen, on the mac or on the vm.
There, there is a check box to "remind this selection" and it never ask you again pairing always taht device with vm.
Sorry, but i don't know where and if there is something like in VMWare
I think this will get you rooted on a Mac. You will need adb.
http://androidroot.mobi/asus-eee-pad-transformer-tf101-root-cwm-recovery/
eep2378 said:
After searching a bit it seems most if not all rooting methods require the use of a Windows machine. Are there any resources for us mac users in terms of rooting the TF?
Click to expand...
Click to collapse
When I rooted mine at the very beginning of June I just used this guide as a template.
Didn't need to install any extra drivers like Windows users do, I got adb from the link provided at the beginning of the guide and the followed each of the steps including downloading the rooting tools. The commands are the same but are entered slightly differently in OSX.
Example
In OSX you would type:
Code:
./adb devices
instead of Windows:
Code:
adb devices
If you've used OSX terminal before you should be fine.
I've tried every driver known to man. I've tried the official Google drivers, I've tried the naked drivers, I've tried the ones that come with PDANet.
I've tried rebooting, uninstalling all other drivers, etc. I tried on my Windows 7 desktop, I tried on my Windows 8 laptop after disabling driver enforcement.
Every single time, the ADB driver installs fine, but adb itself sees no devices. I develop, I have many other Android devices (I am moving from a One XL) and they all just need one quick install and are detected. I have the same issue with my Nexus S - getting it consistently recognised on ADB is near impossible.
What am I doing wrong? I've waited three months for this thing and I want to set it up.
'USB Debugging' enabled?
Of course. It will install drivers for the ADB device, it just won't be detected by adb.exe.
I tried the 'switch to Photo MTP' mode trick too. I am having no issues with adb to a One XL, One V, Defy, Aurora II or U8800. This is really bizarre.
Do you have java jdk installed correctly?
http://www.oracle.com/technetwork/java/javase/downloads/index.html
I wasn't aware java was relevant to adb at all (and I don't think it is) but yeah I have the JDK installed and it works fine for my app dev.
I had the same issue. Drivers installed correctly (and worked on other phones) but not the N4.
In the end i used an Ubuntu Virtual machine, attached the phone, followed a guide on XDA for getting ADB drivers in linux, and it worked straight away.
Days of trying in windows, and done in 5 minutes through linux.
Yep, I too went the virtual machine route.
Ridiculous. The only two developer devices I've owned (Nexus S and Nexus 4) and they've both been impossible to get the adb drivers going...
Passa91 said:
I wasn't aware java was relevant to adb at all (and I don't think it is) but yeah I have the JDK installed and it works fine for my app dev.
Click to expand...
Click to collapse
Yes you have to have installed the java jdk to run adb, it doesn't work without it. Java jdk is supposed to be setup first before you install the sdk so that it finds it. One issue why people can't get adb working is that the path environment variables are not set up and need to be manually entered.
Example of setting your windows path environment variables for jdk version 6 windows 32 bit on Windows Vista.
right-click on My Computer, and select Properties
under the Advanced tab, hit the Environment Variables button
in the dialog that comes up, under System Variables double-click on Path
Add ;C:\Program Files (x86)\Java\jdk1.6.0_18\bin to the Path variable (or wherever the jdk was installed)
Add ;C:\android\android-sdk-windows\platform-tools to the Path variable (or wherever you installed the sdk)
Passa91 said:
I've tried every driver known to man. I've tried the official Google drivers, I've tried the naked drivers, I've tried the ones that come with PDANet.
I've tried rebooting, uninstalling all other drivers, etc. I tried on my Windows 7 desktop, I tried on my Windows 8 laptop after disabling driver enforcement.
Every single time, the ADB driver installs fine, but adb itself sees no devices. I develop, I have many other Android devices (I am moving from a One XL) and they all just need one quick install and are detected. I have the same issue with my Nexus S - getting it consistently recognised on ADB is near impossible.
What am I doing wrong? I've waited three months for this thing and I want to set it up.
Click to expand...
Click to collapse
I posted a solution some time a go find it in my posts
Sent from my Nexus 4 using xda premium
davehunt83 said:
I had the same issue. Drivers installed correctly (and worked on other phones) but not the N4.
In the end i used an Ubuntu Virtual machine, attached the phone, followed a guide on XDA for getting ADB drivers in linux, and it worked straight away.
Days of trying in windows, and done in 5 minutes through linux.
Click to expand...
Click to collapse
The linux guides include editing the udev rules so that you manually enter the Nexus 4 into the list of devices in order to get adb to recognize the phone. Could be the same issue with windows. I only have the sdk installed on a Linux box and haven't used it on windows since I installed it on a Vista box a few years ago but I would imagine windows would have the same problem recognizing the phone.
Linux Install Instructions
http://rootzwiki.com/topic/20770-gu...-adb-and-fastboot-in-linux-ubuntu-and-mint12/
Passa91 said:
I've tried every driver known to man. I've tried the official Google drivers, I've tried the naked drivers, I've tried the ones that come with PDANet.
I've tried rebooting, uninstalling all other drivers, etc. I tried on my Windows 7 desktop, I tried on my Windows 8 laptop after disabling driver enforcement.
Every single time, the ADB driver installs fine, but adb itself sees no devices. I develop, I have many other Android devices (I am moving from a One XL) and they all just need one quick install and are detected. I have the same issue with my Nexus S - getting it consistently recognised on ADB is near impossible.
What am I doing wrong? I've waited three months for this thing and I want to set it up.
Click to expand...
Click to collapse
I used the Universal_Naked_Driver_0.72. It worked for me. I did not install Java.
http://dl.dropbox.com/u/18573149/Universal_Naked_Driver_0.72.zip
RacerXO said:
I used the Universal_Naked_Driver_0.72. It worked for me. I did not install Java.
http://dl.dropbox.com/u/18573149/Universal_Naked_Driver_0.72.zip
Click to expand...
Click to collapse
You shouldn't even be able to install the sdk properly without having java jdk installed first as the windows installer checks to see if its there.
http://developer.android.com/sdk/installing/index.html
Edit: and by installer I meant SDK Manager, what you use to download and install the android usb drivers. I suppose you can get past the java limitation by just downloading the sdk and copying the needed files into the c directory then using 3rd party drivers but java jdk is what controls the phone once its connected so I don't know how you are getting it to work.
Edit 2: I guess I was wrong in part, I installed the sdk without java jdk on a windows xp box, used the universal drivers linked to above, and it recognized my phone in adb devices and I was able to reboot it. But I can't use sdk manager as it requires java jdk to be installed.
had the same issue... you must be using a usb port on the front/side of the computer
use one of the usb ports on the back, and you should be just fine.
This happens to me too. On all windows computers I have used for ADB and all phones it will work the first few times, and then it won't work no matter what. I can usually get fastboot to work reliably but that is it.
Sent from my Nexus 4 using Tapatalk 2
Hi guys,
I'm currently experiencing a probem with my Nexus 4. No matter what OS I use (Linux or Windows) or what driver I use adb keep saying that my device is offline. As I saw elsewhere I tried an other usb cable or port but nothing seemed to work. Does anyone got an idea for this ? This thing is gonna drive me crazy !
Thanks
Task Manager, then kill the ADB one. Then open ADB, adb devices again.
Otherwise, did you check the debugging =.= Or reinstall the driver manually (not by WIndows).
I have had a problem with this and it has been unsolved as of yet, but I may be able to help you. In the SDK Manager, there is an extras area, if you don't have the drivers from there I have found you may have trouble. It could be something else, but this should be a sufficient launchpad.
Sent from my ADR6425LVW on GrayTheWolf's CM10 build.
Thanks to you both, but I mainly use Ubuntu and not Windows. I've tried killing and restarting adb a lot of times.
saintjimmy said:
Thanks to you both, but I mainly use Ubuntu and not Windows. I've tried killing and restarting adb a lot of times.
Click to expand...
Click to collapse
Are you on 4.2.2 they changed somethings with the update. Have you updated your SDK?
Try installing PDAnet drivers. They will make it work.
xdaOSdev.team said:
Try installing PDAnet drivers. They will make it work.
Click to expand...
Click to collapse
I can verify this, it solved the problem I have been having for a few months in Linux OSes.
Sent from my ADR6425LVW on GrayTheWolf's CM10 build.
saintjimmy said:
Thanks to you both, but I mainly use Ubuntu and not Windows. I've tried killing and restarting adb a lot of times.
Click to expand...
Click to collapse
Guys, he said he's using ubuntu lol there are no usb drivers to install
try this...it sounds like your adb may be out of date. This will also reinstall fastboot, unless you leave 'android-tools-fastboot' off the last command
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
btw, if you haven't already done so, you should get the full sdk installed. It's better to have it and not need it than to not have it and realize after three hours of pulling your hair out you should have had it all along lol (I've done it, so I speak from experience)
Thanks @hp420 but sadly the device is still offline. I'm just realizing it now but I didn't have the warning message about the association with the computer that I usually have when activating USB debugging with 4.2.2
Load latest SDK version. Load driver inf fix. Search forum. Known problem. Easy fix.
sent from my nexus 4; cat on lap, beer in hand
This is due to the new whitelist for adb in 4.2.2.
Some of these steps may be unnecessary, but I know this works (I've had to do it a few times to all my devices that have been upgraded to 4.2.2).
You need the adb from the latest SDK.
Untick USB Debugging.
Reboot the phone.
Tick USB Debugging.
Reboot the phone.
On your PC, make sure you add the new SDK/tools to the PATH then do adb kill-server; adb start-server
Unlock your phone.
Plug it in to your PC.
A message on your phone will appear asking to add the PC to the whitelist.
Accept this and your phone should appear when you do an adb devices
No need for driver i'm running linux...
Sent from my Nexus 4 using xda app-developers app
Nark.GA60 said:
This is due to the new whitelist for adb in 4.2.2.
Some of these steps may be unnecessary, but I know this works (I've had to do it a few times to all my devices that have been upgraded to 4.2.2).
You need the adb from the latest SDK.
Untick USB Debugging.
Reboot the phone.
Tick USB Debugging.
Reboot the phone.
On your PC, make sure you add the new SDK/tools to the PATH then do adb kill-server; adb start-server
Unlock your phone.
Plug it in to your PC.
A message on your phone will appear asking to add the PC to the whitelist.
Accept this and your phone should appear when you do an adb devices
Click to expand...
Click to collapse
Tanks fort that answer I'll try it as soon as possible !
Sent from my Nexus 4 using xda app-developers app
Try typing
adb kill server
adb start-server
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
Try typing
adb kill server
adb start-server
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Already did that countless times...
Sent from my Nexus 4 using xda app-developers app
saintjimmy said:
Already did that countless times...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
try a live cd of ubuntu and see what happens. that will at least narrow it down to whether it's your ubuntu installation or your phone. if it still won't mount in the live cd we can assume it's an issue with your phone. from there you can run a nandroid backup and reflash the factory images to see if that fixes the issue. if it does, you can try a fresh install of the rom you're using. if it still works, then restore all your apps/app data
if it's your ubuntu installation there are other avenues you can try.
saintjimmy said:
Already did that countless times...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You can try uninstalling SDK and perform a fresh install. Move your platform tools to a more convenient locations and change the path under windows properties.
I don't know if you tried this already but..
Have you tried uninstalling and reinstalling the drivers for phone?
switch to another USB port? A different usb cable?
scream4cheese said:
You can try uninstalling SDK and perform a fresh install. Move your platform tools to a more convenient locations and change the path under windows properties.
I don't know if you tried this already but..
Have you tried uninstalling and reinstalling the drivers for phone?
switch to another USB port? A different usb cable?
Click to expand...
Click to collapse
UBUNTU!!!!!
lol
hp420 said:
UBUNTU!!!!!
lol
Click to expand...
Click to collapse
Or try using Ubuntu. LOL.
But dual-booting to another OS is a hassle.(?) If ubuntu is not your daily driver, you're gonna have to keep rebooting in between OSs.
scream4cheese said:
Or try using Ubuntu. LOL.
But dual-booting to another OS is a hassle.(?) If ubuntu is not your daily driver, you're gonna have to keep rebooting in between OSs.
Click to expand...
Click to collapse
Thann you all for your answers! I use linux mint which is my main OS. I manage to resolve my problem in a weird way: first I push a CWM recovery with fastboot and then I flash the ZIP from SuperSu ! From now USB debugging is working properly and I get the usual warning !
What I would like to know now is why ? Does the SuperSU ZIP reset something ?
Sent from my Nexus 4 using xda app-developers app
Hey everybody,
I got my Oppo since 3 days now and I am very satified with it. But this morning I was trying to connect the device via USB to continue developing an app in Processing and the IDE didn't find my device. The IDE is waiting for the device to become available and that's it.
After this, I tried the universal adb drivers, the usb drivers of the SDK and the usb drivers of the pdanet app. Nothing worked for me so far. In the device manager the device is listed as "Android ADB Device", so it should be working, right? I am working on Windows 8 on my laptop right now and I think this is where the evil comes from
Any Processing developers here, which got Processing working with their Oppo??
Greetings
digga_mies
I use windows 8 on my PC, but OPPO is recognized when plugged in. I'm pretty sure my correct drivers were installed when I connected the phone.
sent from my Find 5 using Tapatalk 4 Beta
Coreym said:
I use windows 8 on my PC, but OPPO is recognized when plugged in. I'm pretty sure my correct drivers were installed when I connected the phone.
sent from my Find 5 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Okay, and what drivers did you use? The stock drivers of Win 8? Or do you have downloaded others?
I don't know if it helps, but I have installed the stock firmware X909EN_12.A.09_GLO_009_130514
digga_mies said:
Okay, and what drivers did you use? The stock drivers of Win 8? Or do you have downloaded others?
I don't know if it helps, but I have installed the stock firmware X909EN_12.A.09_GLO_009_130514
Click to expand...
Click to collapse
I remember having some issues trying to get Casual to work as it wasn't seeing my phone. I'm pretty sure I used this reference to get everything working correctly.. Install Drivers for any Android
Okay, tried it again with pdanet and got no success again. Even the platform tools adb.exe doesn't recognize my phone as an adb device. I'm getting a little bit frustrated right now.
By the way, I tested it on Windows 7 and it doesn't work either.
Anyone got another idea?
digga_mies said:
Okay, tried it again with pdanet and got no success again. Even the platform tools adb.exe doesn't recognize my phone as an adb device. I'm getting a little bit frustrated right now.
By the way, I tested it on Windows 7 and it doesn't work either.
Anyone got another idea?
Click to expand...
Click to collapse
Try wireless adb, and connect manually to your phone via command line (something like: adb connect YOURIP). I pretty much use only wireless adb (as I do tend to develop stuff that relies a lot on the 9 DOF sensors...) Cheers.
I got it. My device was shown in the device manager all the time as adb device, but the Processing IDE didn't found it. In the Oppo forums is the same error described with eclipse.
The solution was, to change the adb_usb.ini in "C:\Users\YOURUSER\.android". In my file wasn't any entry and I simply added "0x22D9". That's it! Worked for Windows 7 and 8.
:victory::victory:
digga_mies said:
I got it. My device was shown in the device manager all the time as adb device, but the Processing IDE didn't found it. In the Oppo forums is the same error described with eclipse.
The solution was, to change the adb_usb.ini in "C:\Users\YOURUSER\.android". In my file wasn't any entry and I simply added "0x22D9". That's it! Worked for Windows 7 and 8.
:victory::victory:
Click to expand...
Click to collapse
I dont understand what you mean adb_usb.ini
can you make a guide?
digga_mies said:
I got it. My device was shown in the device manager all the time as adb device, but the Processing IDE didn't found it. In the Oppo forums is the same error described with eclipse.
The solution was, to change the adb_usb.ini in "C:\Users\YOURUSER\.android". In my file wasn't any entry and I simply added "0x22D9". That's it! Worked for Windows 7 and 8.
:victory::victory:
Click to expand...
Click to collapse
Thanks for the device code!