Database Users

[Q] adb USB access from LXC container

Hi All,
This is a bit of a weird one - hope it's not totally off topic.
I am attempting to get adb to detect my device when adb is running inside a container/virtual machine. Specifics as follows: I am setting up a development environment in a container, specifically LXC (Linux Containers - similar in spirit to OpenVZ). I have managed to bind mount /dev/usb and /dev/bus. Running lsusb in the container properly detects the phone being attached and detached. I also have the relevant device files (e.g. with my current HTC Wildfire connected to the same USB port, /dev/sdd - with the correct permissions from within the container as far as I can tell...)
However adb still does not see the device ('adb devices' returns nothing, the server successfully starts up). I guess my question is how does adb determine the existence of device?
PS I know there are workarounds like running it over WiFi, or using the host machine for adb - it just defeats the purpose a bit of using a VM. Actually running over WiFi is nice, but Eclipse - I am not sure I can make it talk over wifi automatically... perhaps that's another avenue. I just want nice clean integration from a container. Too much to ask?

[Q] How to Access the device using Ubuntu?

Does anyone now how I can access the internal storage of my transformer through Ubuntu? I have the transformer connected via USB but it does not auto-mount or appear to be recognised as a storage disk
thanks for any help

I'm using SSHDroid and usb tethering when tablet is connected, find out the tablet ip, then you can use the ubuntu built-in "Connect To Server" via ssh.

readonlycn said:
I'm using SSHDroid and usb tethering when tablet is connected, find out the tablet ip, then you can use the ubuntu built-in "Connect To Server" via ssh.
Click to expand...
Click to collapse
Would you be able to explain the method you use a bit more thoroughly? I too am having frustrating problems getting my transformer mounted under Linux, and am sick of transferring everything via SD card
I tried over SSH, but Android automatically refuses connection. And why do we need to have it tethered via usb to SSH?

The transformer acts as an MTP device. I had some issues with it appearing properly in Ubuntu 10.04, but I believe is because I did something wrong. I have it all working now and mounted as /media/transformer - but I am also running 11.04 now.
This has been asked on the forum before and this answer assisted me in solving it[Full thread].
You also have some links in a different thread here.

poltak11 said:
I tried over SSH, but Android automatically refuses connection. And why do we need to have it tethered via usb to SSH?
Click to expand...
Click to collapse
What's your SSHD application? I recommend sshdroid, you search it in the market.
You needn't tethering if pc and android are in one lan (connected to same wifi for example). Getting android ip is the only purpose of tethering, you can run 'route' command in ubuntu to find out the gateway of usb0, which is the ip of android.

I use a combination of swiftp and droidsshd to access device from ubuntu. Works well. You might need to get the programs from code.google.com, as they are not in the market.

People... they aren't looking for an SSH application, they are looking to MOUNT THE DEVICE OVER USB.
You need to install either libmtp or mtpfs. On Arch Linux, libmtp is in the repos, while mtpfs is in AUR. I use mtpfs.
After getting mtpfs, all you need to do is: sudo mkdir /media/tf && mtpfs -o allow_other /media/tf.

I do it with ADB. adb push and and pull does the job easily, unless you've a ton of different files you want to place in different places.

Using gnomad2 from repo @ Fedora 15 Gnome3
since there is no flashy mtpfs for my distro :/
(to lazy to compile)

[Q] help for nook touch rooting from China

Hi everyone, I've been trying to root my nook2 and I've been over all the steps many times, and I can't achieve ADB over USB or WIFI.
I've used the nooter technique and the device looks rooted, I can log into Gmail and get new mail, but as youtube is blocked in China, I can't login to youtube as i'm supposed to in the process described on nookdevs. (is youtube loging really important?)
I can install apps from the market, but can't use the search field (no results, no matter what I type).
I decided to try adb access from there anyway (before asking for help...), and here's where I'm stuck :
I installed the light sdk combo found here : "hXXp://forum.xda-developers.com/showthread.php?t=910008" and followed all the steps
I can connect to the device using wifi ADB, but the shell cmd doesn't get me anywhere (I get a hash mark and an endlessly flashing underscore)
I can't get adb access over USB, because no matter how many times I try uninstalling the basic drivers in the device manager(all of them), they always come back within 5 seconds when I plug the nook (and yes, I seem to have disabled automatic driver update in Gpedit.msc)
when I try to load the adb drivers manually over the preexisting ones it tells me no suitable drivers where found in my *.inf file (or that it already has the best driver for the device)
I've been over everything (apparently) countless times and I'm still stuck.
do you have any idea what the problem could be?
If I had to guess, it's either :
-It's not completely rooted (for lack of youtube login) so it will always be recognized as a Nook and nothing else in the device manager
-the factory defaults nook drivers are lurking somewhere on my laptop and prevail over the adb_usb drivers.
-there is another move to disable automatic drive install in Gpedit.msc which I haven't attempted yet.
Please if you have any ideas... My nerdy ego is absolutely hurt by this and it's begging for relief.

I've been thinking about this, and if I could just set up the android version of astrill directly in the micro sd (directly set up on nooter) I could then access youtube and finish the job properly.
Do you know if it's in any way possible to do that?

I wonder if you'd be able to use Orbot to be able to gain access to Youtube...

Karibou3 said:
Hi everyone, I've been trying to root my nook2 and I've been over all the steps many times, and I can't achieve ADB over USB or WIFI.
I've used the nooter technique and the device looks rooted, I can log into Gmail and get new mail, but as youtube is blocked in China, I can't login to youtube as i'm supposed to in the process described on nookdevs. (is youtube loging really important?)
I can install apps from the market, but can't use the search field (no results, no matter what I type).
I decided to try adb access from there anyway (before asking for help...), and here's where I'm stuck :
I installed the light sdk combo found here : "hXXp://forum.xda-developers.com/showthread.php?t=910008" and followed all the steps
I can connect to the device using wifi ADB, but the shell cmd doesn't get me anywhere (I get a hash mark and an endlessly flashing underscore)
I can't get adb access over USB, because no matter how many times I try uninstalling the basic drivers in the device manager(all of them), they always come back within 5 seconds when I plug the nook (and yes, I seem to have disabled automatic driver update in Gpedit.msc)
when I try to load the adb drivers manually over the preexisting ones it tells me no suitable drivers where found in my *.inf file (or that it already has the best driver for the device)
I've been over everything (apparently) countless times and I'm still stuck.
do you have any idea what the problem could be?
If I had to guess, it's either :
-It's not completely rooted (for lack of youtube login) so it will always be recognized as a Nook and nothing else in the device manager
-the factory defaults nook drivers are lurking somewhere on my laptop and prevail over the adb_usb drivers.
-there is another move to disable automatic drive install in Gpedit.msc which I haven't attempted yet.
Please if you have any ideas... My nerdy ego is absolutely hurt by this and it's begging for relief.
Click to expand...
Click to collapse
Read this, its all contained on my manual tutos, adb is gained just by changing uramdisk, there is one for wifi and another for usb, please, check which one you are using, then, follow this:
Here there is a list of all the tutos:
http://forum.xda-developers.com/showthread.php?t=1380400
and here the ones you should read:
Setting up adb manually on the nook touch:
Making the manual process LESS PAINFULL
Setting up root access on NST through adb and installing busybox:
Hope it helps.
For the youtube thing, just set adb correctly (when you get it right) sideload an app to use a proxy, or tor, or anything you like, and try to login on Youtube.

I'm really sorry for not responding to this
I managed to get it rooted in the few days after my post, and I didn't any email notifications of your replies (didn't check on control panel, i'm new here, please don't hurt me )
I found a chinese source for rooting (a seller on taobao.com explained it. The Chinese are quite fond of the nook because it's the only foreign e-reader you can use to read Chinese apparently, and Chinese e-readers are both more expensive than the nook AND crappy.
Anyway I painstakingly translated it and got it to work
what you tell me about the proxy is new to me though, I thought android couldn't run a proxy, that's great news not just for youtube but the zillions of website China blocks and that I could use my nook to check, I'll have a go at it when I get near a wifi network.
cheers

Advice on "unbricking" a soft-bricked stick

I've been scouring different forums for nearly a month now and can't find a solution that works for my situation. I resisted posting here, hoping to find the info on my own without any luck. I have a handful (6) of these generic MK809III Rockchip 3188 based sticks, with 4.4.2 KitKat. All identical. I have no idea which Chinese manufacturer assembled them. Four of them work perfectly. Two of them have been corrupted by me. I inadvertently wiped out the build.prop files. The files are there, but they are empty. (I know this because the last one I botched, I could see the file in the open editor with no content, as a read-only. The moment I closed the screen... that was it.
Using the "hold the pin in hole, then power up, wait 5 or 10 seconds, then release the pin" method of recovery (sorry, I don't know the proper name) does boot it into recovery mode, but the screen shows this:
Failed to mount /mnt/external_sd (No such device)
Failed to mount /mnt/external_sd (No such device)
Failed to mount /mnt/external_sd (No such device)
one_data_if_exist->can't find databk partition
Formatting /data...
Formatting /cache...
Booting...
--- then, a stuck boot animation.
My problem, is that I cannot connect to these via USB to do anything to them. My system tools are:
Linux Ubuntu 14.04 LTS workstation
RK_Flashtool_1.7
Android Studio
Latest Android tools sdk
Other tools available to me: A Mac (running Yosemite OSx)
Notes:
- Adb drivers, I assume, are correct, because I can access the working stick computer via ADB
- The RKFlashtool will not recognize any of the corrupted units, or show that it is even connected
- Obviously, I cannot set the "Connect to PC" flag without the OS booted
- In a terminal window, adb does not show the usb device as being connected
- I do not have a back up for any of these. I tried, but both Clockwork and TWRP would not recognize the unit to permit a backup. The working units are recognized as: "gxt_dongle_3188".
I really need some advice. I must be overlooking something, I admit to being somewhat new to Android. I wish it were possible to backup one of the working units, and install it on the corrupt units. But no backup app was installed in the boot loader of the corrupted units (that I'm aware of).
Thanks for your time!

Judging from the lack of responses, this problem must have a lot of people as perplexed as I am. I really thought someone here might have an idea.

Recover rooted NST with broken LCD?

Just checking it there is some way to recover files. I previously rooted it and can't remember if that means there's any way to get at it via ADB or otherwise to recover files before transfering to a new device

Well, if you have ADB working you can just transfer the files.
Or you could use my AdbSync.exe (along with ADB) to backup.
Code:
C:\>mkdir whatever
C:\>adb devices
C:\>adbsync /hcsu /s /v C:\whatever sdcard

ADB doesn’t seem to be working or at least via USB… And I can’t get on it to select a Wi-Fi network. Wondered if there is some way of forcing it to boot in Adb mode or something that doesn’t rely on screen interaction

mrbryan said:
ADB doesn’t seem to be working or at least via USB… And I can’t get on it to select a Wi-Fi network. Wondered if there is some way of forcing it to boot in Adb mode or something that doesn’t rely on screen interaction
Click to expand...
Click to collapse
You're the second person in a week or so that seems to have this issue and it got me curious. There's a message at the beginning of NookManager about starting WiFi if you want to directly connect with the device via SSH(?) or ADB. I've always ignored it but I just tried it to see what would happen. After you elect to start WiFi (your NST must have been known to your network beforehand, password entered, etc.), you are given the option to start either SSH or ADB (the IP address is displayed at the top of the screen).
When I chose ADB I was then able to start up ADB on my PC and connect to the IP address shown on the NST screen. Of course.....if your screen is broken........Maybe you know the IP address of your NST already or could find it by starting WiFi and then consulting your router?
Anyway, the advantage with NookManager is that everything is done with the side hardware buttons. If you can't read your screen at all I can see that even that would be a problem, though. If you have some partial display, you might be able to limp along until you have ADB connected and then handle everything from your PC. Or I could supply you with a button-push sequence to try.
To just get this working you can make a NookManager card--no need to make the updates I described elsewhere.

thanks so much for the suggestion. I'll have to think that through and whether I have my current wifi set up ( edit: in the nook already).
maybe I can hack around in the scripts for nook manager in case I can set it to go right to the ADB on boot and inject a wifi name & key too

Get an image for the old noogie and put it on an SD card.
Boot up, you should have ADB.
Or do the whole OmapLink procedure and boot from there.
Or connect to the 1.8V UART root console inside the case.