• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root helping please

zixxorb said:
@EarlyMon
Does Linux not use drivers at all? (idk much about Linux but I'm trying to learn.)
I have some Bootable cds/dvds with Linux but I don't use them often.
Click to expand...
Linux, a version of Unix, does not use hardware-connection device drivers, never has.

It does use software-transformation device drivers - examples are printer drivers or video drivers that shape information flow for the end device - but it doesn't care how the relevant devices are connected. Connections are either byte by byte or block by block for the most part. Not difficult.

Files, data streams, and devices connect to one another using very straightforward means (in very early Unix, everything was just a type of file). It's up to the application software and the user to make connections that result in meaningful actions.

With USB debugging on, Android (actually a real-time Apache/Linux distribution) runs the adb daemon (basically a kind of server) and the PC runs adb designed to talk to that daemon.

You don't need anything extra - Android is dying to talk to anything that will listen and talk back. Get a Mac on the other end of the wire and it's Android (Linux) talking to BSD Unix, connect to Linux and it's a straight Linux to Linux communication. Nothing fancy needs to occur with a USB port - and this is exactly why wireless adb just works. No drivers of any kind needed.

It has nothing to do with file format.


Connect to Windows, first thing that happens is that adb isn't allowed to talk to whatever is on the end of the wire - it talks to Windows, that in turn talks to the right idea of a USB driver.

There's nothing weirder than Windows - perfectly good messages are deconstructed, sent through endless software layers so you can get this result from Windows with the right driver - "Oh gee, these two things are designed to talk to one another - thank God that I, the mighty Windows operating system - could make that possible by reconstructing exactly the same message I was given in the first place." I'm not exaggerating. I wish I were.

By the way - all open source software stems from one guy needing a data-transforming printer driver for a minicomputer.

Hope that clarifies.

There's no issue running a live cd or DVD compared to a live usb except speed.
 
Last edited:
I'm fixing to just give up on this.....

So, I am on my live cd of Ubuntu.....
Extracted Sdk-tools and the root zip to the Home directory on the left...
In The terminal I run sh sdk.sh and it says
Terminal said:
sdk.sh: 18: sdk.sh: [[: not found
sdk.sh: 22: sdk.sh: [[: not found
sdk.sh: 36: sdk.sh: [[: not found
Mini-SDK already in path, installation complete.
Click to expand...

Then When I try to run any adb commands it tells me that adb isn't installed..... I feel like I've tried everything now..... What am I doing wrong?
 
I may have borked the guide - sorry about that, I was sure I'd fixed that.

Try instead -

bash sdk.sh

And then in a new Terminal Window say -

which adb

And let me know what that says.
 
Linux/Mac OS don't need drivers (in the Win OS sense) because the architecture is completely different. Everything required is either compiled into the kernel or there as pre-installed support libraries.

edit: ninja'd by EM (yet again! :D )
 
OK (sorry I took so long) when I first did bash sdk.sh it told me that mini-sdk installed. Then I tried running adb commands and it says adb isn't installed. When I type "which adb" it just goes to a new line/entry (whatever it's called for a new command).

Still confused on what I'm doing wrong....

Edit:
When I type just "adb" :

Terminal said:
The program 'adb' is currently not installed. You can install it by typing:
sudo apt-get install android-tools-adb
You will have to enable the component called 'universe'
Click to expand...

If I put "sudo adb devices"
Terminal said:
sudo: adb: command not found
Click to expand...
 
Last edited:
Find the sdk-tools folder, tell me what you have there.

If you have adb-linux then the installer failed for whatever reason.

In the Terminal Window open to the sdk-tools folder, say -

mv adb-linux adb
mv fastboot-linux fastboot
chmod 755 adb
chmod 755 fastboot

Then try from there -

sudo adb devices

If that fails, then -

sudo ./adb devices

Let me know what happens.
 
*sighs* so complicated lol

Everything went OK until
Sudo adb devices
sudo: adb: command not found
adb devices
same not installed message
sudo ./adb devices
sudo: unable to execute ./adb: No such file or directory

(sidenote: I'm typing on my tablet and I hate autocorrect with periods)
 
If it makes any difference, I extracted the root zip and the sdk-tools to the home directory (everything from inside the sdk-tools is there now, besides what we just moved via those commands)
 
From the sdk-tools folder??

Please try (and these are lowercase L in both spots and a space after ls) -

ls -lFa

You should see a directory listing and in it, a line that says -

-rwxr-xr-x (stuff relating to owner, date and size) adb
 
zixxorb said:
If it makes any difference, I extracted the root zip and the sdk-tools to the home directory (everything from inside the sdk-tools is there now, besides what we just moved via those commands)
Click to expand...
Ok, so that broke the path that the installer set up before failing.

So now try -

ls -lFa $HOME adb*

If just adb exists it has to begin the listing with rwxr-xr-x.

If it does, then try -

sudo $HOME/adb devices

If you still have an adb-linux file, just use that -

sudo $HOME/adb-linux devices

If the listings do not begin with rwxr-xr-x, then try again -

chmod 755 $HOME/adb*
chmod 755 $HOME/fastboot*
 
EarlyMon said:
From the sdk-tools folder??

Please try (and these are lowercase L in both spots and a space after ls) -

ls -lFa

You should see a directory listing and in it, a line that says -

-rwxr-xr-x (stuff relating to owner, date and size) adb
Click to expand...

adb and fastboot both are green and with those permissions
 
Dammit. No such luck.....

sudo $HOME/adb devices
sudo: unable to execute /home/ubuntu/adb: No such file or directory
 
Idk if this helps but
IMG_20150620_135955.jpg
 
Then from the folder where the adb listing was correct, do -

sudo ./adb devices

The "./" says that "file is right here" so note the space after the sudo, and no space after the slash.
 
uname -a
Linux ubuntu 3.13.0-24-generic #46-Ubuntu SMP Thu April 10 19:11:08 UTC 2014 x86_64 x86_64 x_86_64 GNU/Linux

Any idea what I'm doing wrong? Is there an easier way to do this? (granted this is kinda interesting and im kinda learning but still)
 
You must log in or register to reply here.
Back
Top Bottom