Note to teddog : 'adb' doesn't need JAVA or flash to be installed
to obtain the basic commands like 'push' and 'pull'.
I did have to install the JDK(Java Development Kit)
to take a screenshot of Android device.

Note to esrom2: Puppy linux always runs as the root user so
you should never get the message 'permission not permitted'

Some linux apps don't like to run by the root user, but adb isn't one of them.

I wonder if your phone manufacturer has found some way of blocking
adb commands?? Android devices have ways of blocking viruses.
So maybe your phone thinks it's being attacked by a virus.

All I can suggest is use the latest version of adb and cross your fingers.

I have been using Puppy Linux 5.2.8 V4 successfully with adb on my first generation Kindle Fire tablet.

I have used Puppy and adb to flash various recovery partition programs and Android Gingerbread and Jellybean ROMs designed for the first generation Kindle Fire via an ordinary micro USB cable.

(I've learned from the forums on xda-developers.com that, there is a forum for many of the different models of phone and tablet hardware. There may be user developed flashable ROMs and/or installable apk programs for many of the specific models there too.)

As don570 reported above, some of these phones or tablets require the normally unused pin 4 of the micro USB cable end to be grounded (in the case of the OTG ("On the Go") cable), but some other brands or model phones or tablets sometimes need the unused pin 4 of the micro USB cable end to be connected to the +5 volt wire with a current limiting resistor (these micro USB cables are called a "Factory Cable").
The xda-developers.com has lists of what cable is required for a specific model phone or tablet with adb or what cable is required for even resurrecting a "brick"!

Also I wanted to thank 01micko for mentioning the useful Android apk: airdroid.
As a newbie in the world of Android, I have found the sheer number of available apps (even just ones with four or five star reviews) to be overwhelming.

For my simple needs, I haven't wanted to go through an endless cycle of installing, trying and then un-installing hundreds of apps.

To buy a new cable is not expensive but few stores have this special
cable in stock.
___________________________________________________
It's possible to attach keyboards and USB sticks to nexus7
and probably other tablets.

1 of 1 people found the following review helpful
5.0 out of 5 stars OTG good ta go!
This little cable lives up to it's name. Works fine on a rooted Nexus 7 combined with stickmount app to add much needed USB storage to the tablet. You can't go wrong for $6.00 free shipping. You just have to wait two weeks for it to get here from Hong Kong.

Has anybody figured out how to get over the error message that /system is Read Only?

I'm trying to root an HTC Wildfire S with Android 2.3.5 - a previous poster on this thread has done this, so it must be possible.

When I enter the commands to push Superuser.apk, etc., from /root on my Puppy laptop to /system on the phone, I get the message that /system is Read Only. I've searched, but can't find how to make /system Read/Write.

I have now tried an OTG cable and neither tablet did anything different. I then got a "factory cable" and tried. At least this time the tablets indicate "USB debugging connected, but "adb devices" still shows nothing for these two tablets and trying touch or ls gives a device not found.

Trying the OTG and factory cables on the phone gives the debugging connection like the regular USB cable but push still gives me permission denied like with the regular USB cable.

How do I get past this permission denied on the phone and the lack of any kind of response in ADB from the tablets?_________________"Cogito, ergo es. I think, therefore you is." Ray D. Tutto (King of the Moon) to Baron Munschaussen

Thank you, don570 for providing the information in this post. I have two android tables that I have been using for experiments. Both have already been rooted by another method. But, I have not had much luck in getting adb to work. It is working now for me. Both tablets have android version 4.2.2 version on them. Here is some additional information for everyone's use.

Both tablets required these steps to get the developer option to work. First with the settings application under the "About Tablet" menu entry, one has to "tap" the "Build Number" seven (7) times to get the developer permission so the "Developer Options" menu entry to be shown. Once the "Developer Options" menu entry is available, then one has to turn them on by moving the unlabeled switch (upper left corner) to the left so it has a green bar shown. Once that is done, all the developer options are available for use.

The first tablet is a Lenovo Model B6000F. I found once I used the adb you listed, my previous problems disappeared. The Lenovo did not require a special cable. It connected with its normal charging cable, a micro USB to a normal male USB connector. Using the information on adb including its internal help discription, I was able to access and manipulate the tablet's files.

The second tablet is an inexpensive NextBook model NX785OCBG sold by Walmart. I got it to use it as an Internet radio. I could not connect adb to it using the usb interface. I tried several different cable configurations using a standard charging cable or OTG cable. It would not connect. I do know the USB port is a OTG type. I did find the reason, the tablet does not correctly identify itself to adb. The vendor usb ID (2922) is not listed in the available vendor databases. I managed to connect it using a wifi IP connection. Because the tablet is already rooted, I was able to use the android application ADB Wireless Port by Lu Chao to set up the tablet to connect to adb via wifi. It did work. There are many other andriod adb wireless applications available that claim to be able to do this without root privileges. I have not tested them because Lu Chao application worked so well for me. It is very simple to use. This does solve the cable problem. In a terminal window, one uses the command adb connect ###.###.###.### to make the connection to the adb deamon. So far, it appears all adb operations can be done.

I an using Fatdog64 700 beta 1 to do this. I hope this helps._________________Enjoy life, Just Greg
Live Well, Laugh Often, Love Much

I solved the problem of my Nextbook not connecting to adb via USB. When adb is first run, it creates a hidden directory (.android) in the root directory. The .android directory contains the keys to connect with Android version 4.2 or newer. After some web research, I found adb also needs another file, adb_usb.ini in this directory.

The file adb_usb.ini contains the vendors' usb ID value. I created it with Geany (or another text editor), provided the needed hex values. The Nextbook now connects using USB with the standard charging cable to adb for adb operations.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum