Database Users

[Q] Cannot get adb to connect to Nook Color

Ok I've researched this to death and tried in on both Windows 7 and osx 10.6.6 to attach using adb and install a couple of .apk's and the same thing happens on both platforms - NOTHING :-(.
You would think this would be pretty basic, but I am missing something somewhere.
Summary:
1. Am running the stock rooted b&n rom.
2. Can access both the internal and SD cards on the nook on both windoze and
osx. Eliminates cables, drivers etc...
3. Debug is selected in the nookstools settings
On both OSX and Win 7 installed the latest version of the Android SDK - both installs provided me with the platform-tools directory from which I will initiate all adb commands. So far so good...
on mac: ./adb devices returns:
$ ./adb kill-server
$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
$
As you can see I never get any device information returned, does not matter if Im on Windows or mac - same response.
Just for grins I downloaded the wireless app and tried to connect adb that way...no luck...
I could go into everything that i have tried over the last 24 hours...but that would also be pointless.
Bottom line...assuming this is something simpleI am just missing. Assuming since the symptoms are the same on both platforms that the issue lies on the nook but for the life of me I cannot find it.
Assuming if I cannot figure this out I will slowly go insane..my next step is to flash either froyo or honeycomb rom and see if this helps with the problems. Of course I MUST have the market available to me or I will not b able to load any .apk's.
Hpe Im in the right place. Any guidance is GREATLY appreciated.
Love this little Nook....BG

I know this will sound stupid, but I had this same problem and the only way I found to fix it is to adb while I have the superuser app running.
YMMV, but it solved that issue fo me.

Who Swami - It Worked
Swami,
I fall to my knees and bask in your knowledge: It WORKED!
I knew it was something simple, there is not a post on the entire Internet in any forum I have ever found (and I may have searched them all!) that mentions superuser needs to be running for adb to be able to communicate with the device. I wonder if this is a nook issue only. Will test on my wife's Epic this evening and post the results tonight.
My sanity now restored I bid you all a hearty SEE-Ya!
-BG

Omg I actually helped someone!
Glad it worked for ya I'm sure you felt the same relief I did when I finally stumbled across that fix.. I was pulling my hair out for hours LOL

Thanks Once More
As was I such a simple fix you would think I would have thought about permissions on the client side , such is life and tech thats why we all hang together.
Must say I was going to purchase the iPad 2 when it came out (NEVER buy 1st gen Apple) but now I'm not so sure...LOVING my Nook.

themirthfulswami said:
I know this will sound stupid, but I had this same problem and the only way I found to fix it is to adb while I have the superuser app running.
Click to expand...
Click to collapse
I'm not sure if this is related but I *think* that what made it work for me was to freshly enable the Debugging USB mode immediately before connecting the USB cable. Maybe that also triggered the Superuser app??? It's always the small things in life that make us smile

my problem is a little different.... I have sd cards with honeycomb (no market) and froyo (market and other apps). I can see the NC in adb with both, but honeycomb shows the device offline... and adb cannot talk to it. froyo show the device online and I can use adb. Both honeycomb and froyo show up in windows too.
I can't find anything that talks about getting the NC to show online to adb.

Same Problem
I have the same problem of trying to get my nook recognized. The only thing I can see different between my setup and the instructions on NookDevs was that they said I should see Android ADB Composite Interface on my Device Manager. Mine reads Android ADB Interface.
Tried the Superuser and the USB Debugging with no luck. Just really trying to get this set up so in case I need to factory reset. Because the 8x method manually is way too hard.

Have you guys read though this thread?
http://forum.xda-developers.com/showthread.php?t=910008&highlight=ADB
it worked for me like a charm.

that thread didnt work for me..
i tried lots more ways. just not able to get my nook (running honeycomb) online.
adb devices
just shows a serial code and says offline.
what do i do?
i want to install the G-apps.

I had intermittent ADB success with my Mac. After installing the ADB Wireless app there have been no problems.

Seaweedbrain said:
that thread didnt work for me..
i tried lots more ways. just not able to get my nook (running honeycomb) online.
adb devices
just shows a serial code and says offline.
what do i do?
i want to install the G-apps.
Click to expand...
Click to collapse
nvm
i connected my nook to the back of the cpu.
for some reason, it seemed to work fine.
it read the device as online.
got the g-apps

[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.

rooting the fire on linux

i have adb set up on my linux mint box adb works for all my other devices except the fire. jcases method seems quite easy buite it wont recognize my device any help. and yes I have java and sdk and everything installed perfectly ive been searching many hours with no solution any help is greatly appreciated im not a novice to adb or rooting but this is driving me crazy please help. thanks im oon 1.6.2 by the way

Find one of the old guides to rooting, with instructions on getting it recognized by adb. Mostly need to edit a config file, iirc.
Sent from my Kindle Fire using xda premium

oxlong27 said:
i have adb set up on my linux mint box adb works for all my other devices except the fire. jcases method seems quite easy buite it wont recognize my device any help. and yes I have java and sdk and everything installed perfectly ive been searching many hours with no solution any help is greatly appreciated im not a novice to adb or rooting but this is driving me crazy please help. thanks im oon 1.6.2 by the way
Click to expand...
Click to collapse
adb kill-server
sudo -s
adb devices
---
or add it to your udev rules

jcase said:
adb kill-server
sudo -s
adb devices
---
or add it to your udev rules
Click to expand...
Click to collapse
What exactly do I add to the udev rules in my 51. Android rules? Any way someone can type it exact so I can copy and paste? I never ran into issues like this usually rooting my devices on Linux is smooth as butter. Thanks jcase
Could u elaborate a little I'm a little new to linux
Sent from my ADR6425LVW using xda premium

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] Having trouble getting Mac OS X to see N4 with adb and fastboot

Hello,
My N4 is soft-bricked. Well, hopefully that's all it is.
I want to sideload a ROM onto it, via Mac OS X 10.9.3
I have found plenty of instructions on how to do that with a Mac.
But I can't get ADB or fastboot to see the device.
When I go to the system information on this Mac and looked at the USB devices, I see the Nexus there... along with its serial number, etc. But in Terminal I get a device not found error in ADB and nothing at all in fastboot.
It is my understanding I don't need to install any special drivers on Mac for it to detect the device. Is that correct?
If not, does any one have any suggestions on how I might get this device connected properly?
Thank you...

With further research, I have made some progress. I found this: http://stackoverflow.com/a/7169048
It says:
Also, if that does not work, check to see if the device shows up under USB in the System Profiler (included in OS X). If it is showing up there, but not in ADB, try adding the USB Vendor ID of the phone to ~/.android/adb_usb.ini
This file can be created if it does not already exist. The Vendor ID of the Nexus S is 0x18d1. Please make sure the last line of the file is a Vendor ID, do not leave a blank line at the end.
Click to expand...
Click to collapse
After doing that, I can now see my N4 listed. Well, at least it does when I am in recovery mode.
Now I shall see if I can make some progress with pushing a ROM to this thing (I am new to all this, so I'll see how this goes...)

Can you get to the bootloader screen? Only there fastboot will work.

Way easier if you just set up a virtual machine and run Odin from Windows.
Sent from my SM-T320 using Tapatalk

coolqf said:
Way easier if you just set up a virtual machine and run Odin from Windows.
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
Thanks. I have a VM on this Mac... so i'll try doing this through that.

AndroidWelcome said:
Thanks. I have a VM on this Mac... so i'll try doing this through that.
Click to expand...
Click to collapse
Let me know if you run into any problems. It's how I change ROMs on my Tab Pro. I use OS X 10.9.3

Thanks
coolqf said:
Let me know if you run into any problems. It's how I change ROMs on my Tab Pro. I use OS X 10.9.3
Click to expand...
Click to collapse
Sorry I never replied. Thank you. I got it sorted. Nice to have my N4 up and running again.