Database Users

[Q] Rooting on a Mac?

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.

ADB on TF101

Yeah, its another 'ADB not working on device xxx' thread.. but this one really has me stumped.
Device in question is a TF101, PC in question runs Windows 7 64-bit.
PC has been used successfully to develop android apps. for a Samsung S Plus, with the entire toolchain working.
Same PC, running VMWare, virtualizing XP (32-bit), has also been used to develop/debug with the TF101.
Now the problem. Natively (without VMWare), I have been completely unsuccessful getting the TF101 to be recognized by ADB.
What has been tried:
- TF101 USB drivers from Asus
- TF201 USB drivers from Asus (which also include the TF101 drivers from the look of the .inf files)
- Hand-edited .inf file from the standard android ADB driver
- Adding the VID (0x0b05) to adb_usb.inf
- Uninstalling (and deleting the driver) for anything related to android devices (Samsung, and Asus)
So what happens is that the device does appear in device manager, with 'USB Debugging' checked on the Android device.
With one of the driver combinations I end up with 'Android Composite ADB Interface' in Device Manager, but for some reason its under a 'Samsung Android Phone' Folder, this may well be part of the problem.
No matter what I try, 'adb kill-devices/adb usb' always shows 'error: device not found'
I am two solid days into this now, after reading just about every TF101/ADB thread that google knows about.
Anyone else experienced this?, and might know how to resolve it?

Have you looked at this thread?
http://forum.xda-developers.com/showthread.php?t=1071584

baseballfanz said:
Have you looked at this thread?
http://forum.xda-developers.com/showthread.php?t=1071584
Click to expand...
Click to collapse
He's made it pretty clear that he uses ADB with other Android devices, so I don't think that a guide to installing ADB is going to be particularly helpful to him.
FWIW, I had the same issue. I installed the USB drivers from Asus and could never seem to get ADB to "see" the TF101.
So I ripped them out and installed the full ASUS desktop PC suite from their website. ADB now sees my TF101 just fine. I uninstalled the suite after I had the connection working and ADB still connects to my TF101 without issue. The Transformer PC suite is on the same download page as the stand alone driver.
If you can't find it, PM me and I'll get back to you with a link.

Col.Kernel said:
He's made it pretty clear that he uses ADB with other Android devices, so I don't think that a guide to installing ADB is going to be particularly helpful to him.
Click to expand...
Click to collapse
I too was using ADB already on my N1 but couldn't make it work with the TF.
After reading and following directions on that thread I got it working.
He might not need instructions to set up ADB from scratch but there's good infos about the Asus PC Suite.
Step 7
Basically same as what you just posted and same as what I did to get it working.

I can confirm that too that installing ASUS SUIT works better than just installing drivers, I don't know why but it does. It's the same with my phone. Sometimes installing usb drivers do not work but when I install Samsung kies then somehow that works better even though it includes the same drivers I am installing as stand alone which do not with properly.
Sent from samsung vibrant

Same thing happened to me had to buy a new cord.... does the computer recognize it at all
Sent from my Transformer TF101 using Tapatalk

im not sure if it would help but everyonce in a while ill have a hard time with my adb connection and ill start up wireless adb and can conect fine from that. i dont know why i think in wireless you use ip address on wifi so it might recognize and connect different.. of course this depends on if you want to use it and is alos hardware dependant mainly wifi.

Can't get my computer to recognize my kindle

I can not find a USB driver that will let my windows vista machine read my kindle. I tried the driver from kindle fire utility and that doesn't work. Any suggestions?
Sent from my LG-VM670 using Tapatalk

that doesn't work
Click to expand...
Click to collapse
is'nt really much information
would try to follow:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6

pbailey212 said:
I can not find a USB driver that will let my windows vista machine read my kindle. I tried the driver from kindle fire utility and that doesn't work. Any suggestions?
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
you running custom rom?
If so, after you hook up kindle, look in status bar of kindle for usb icon. Click that and turn on USB storage. That will make your kindle accessible as a drive in windows.

What I did when this happened to me was factory reset kindle (it was on stock rom in process of rooting) and then got recovery and stuff. Then mounted usb from recovery and flashed CM9

I'm running stock, I just got it last night and wanted to root it and put android market on it. And when my free month of prime expired I was going to put cm7 or 9 on it. I'm very familiar with android. Is there a way to turn on debug with stock?
Sent from my LG-VM670 using Tapatalk

on the stock rom usb debugging is allways enabled by default
there is no option to turn it off

I've found that Jayceooi's link on installing the ADB USB driver helped get the USB driver to install properly. Make sure to also check the link about installing the Android SDK Dev Environment.

YayILikePie said:
I've found that Jayceooi's link on installing the ADB USB driver helped get the USB driver to install properly. Make sure to also check the link about installing the Android SDK Dev Environment.
Click to expand...
Click to collapse
I already have android adk installed on windows. I finally decided to dual boot my PC with Ubuntu so hopefully I can get my fire rooted soon. I got Java 7 sdk. Installed, I just ran out of time and haven't loaded adb yet. Hopefully this will work
Sent from my LG-VM670 using Tapatalk

Rooting via Parallels on Mac?

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 !

[Q] Adb always says "Device offline"

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