Related
Hey everyone , so I installed Android SDK on my Ubuntu 9.10 machine, the IDE works fine, my problem arises when I want to send commands to the phone using the fastboot command in the terminal. I get command not found error.
I followed both of these procedures:
http://forum.xda-developers.com/showthread.php?t=537508
http://wiki.cyanogenmod.com/index.php/Fastboot
any help would be greatly appreciated.
try this out......(link)
Follow this its better . Just got passed to me I think its cool. Try it out.
http://dennis.christilaw.com/?p=135
blackerwater said:
Follow this its better . Just got passed to me I think its cool. Try it out.
http://dennis.christilaw.com/?p=135
Click to expand...
Click to collapse
well i did try it , and still nothing it still says adb:command not found , fastboot: command not found
i don't know how good your linux skills are. but you might need to
Code:
chmod +x adp
, then you can run it from it's dir with
Code:
./adb
or you can ln or cp it to your bin dir. for fastboot the same applies (mutatis mutandis).
you might have to use sudo, too.
hope that helps
tried that too
Ubuntu still doesnt recognize it
i should tell you im trying to run it from the terminal window.
pk198105 said:
tried that too
Ubuntu still doesnt recognize it
i should tell you im trying to run it from the terminal window.
Click to expand...
Click to collapse
do this:for jaunty/karmic..
step 1
sudo touch /etc/udev/rules.d/51-android.rules
step 2
sudo gedit /etc/udev/rules.d/51-android.rules
#and add this line and save/close:
SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0666″
step 3 (modified permission)
sudo chmod a+rx /etc/udev/rules.d/51-android.rules
step 4( testing device)
./adb devices
step 5 (if works say thanks!))
note: some linux terminal accept ./adb devices or adb devices
Also before that you might want to check and see if the device ids show up when you plug the phone in. Might be something else with your device or rom your running......good luck.
pk198105 said:
Hey everyone , so I installed Android SDK on my Ubuntu 9.10 machine, the IDE works fine, my problem arises when I want to send commands to the phone using the fastboot command in the terminal. I get command not found error.
I followed both of these procedures:
http://forum.xda-developers.com/showthread.php?t=537508
http://wiki.cyanogenmod.com/index.php/Fastboot
any help would be greatly appreciated.
Click to expand...
Click to collapse
These are the best instructions I've found for setting up the Android SDK on Ubuntu:
http://www.futuredesktop.org/developing_android_apps_on_ubuntu.html
The bit you need to get right it setting up the "udev" policy file. The permissions you set here allow you to access the phone from Ubuntu's point of view.
Also....Do you know that to run a program FROM ITS FOLDER from the command prompt in Linux you need to put "./" in front of it? This is telling to look in the current folder for the program to execute it. But you have to be in that folder.
So you would go to [sdk-folder]\tools and type in (you may have to use 'sudo') "sudo ./fastboot devices" and it should list any attached phones that have USB debug turned on in the phone settings (you do have it turned on, right?)
You should see something like (from my phone):
[email protected]:~/android-sdk-linux/tools$ sudo ./fastboot devices
HT95SKF07937 fastboot
If you see this, then you can move to booting a recovery on your phone. If fastboot doesn't list any devices, then your udev probably isn't set up right.
Here is an extract. This works *every* time. The lines below mean you must use sudo to run fastboot or adb....and to start the adb server ("sudo ./adb start-server"). Butif you add GROUP="plugdev" to the end of each line and also add your username to the group "plugdev" (via SYSTEM -> Administration -> Users and Groups), then you don't need to use sudo.
*****
10d) In Ubuntu, create a new rules file for these vendor:device IDs.
Type this command to create the file.
$ sudo gedit /etc/udev/rules.d/51-android.rules
Add the following blue lines (rules) to it and save the file. If your lsusb command reports other, newer product IDs for vendor 0bb4, add them also to the file.
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c01", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c02", MODE="0666"
--
10e) Re-connect your phone.
Your phone should be detected if you unplug and reconnect it to the computer.
*****
List devices again and you should be fine.
If you're reading and understanding the instructions, it should work. If you're skipping the bits you don't understand.....then go back and understand them. No other way. I'm assuming here that your phone is able to handle fastboot. If you see the three dancing androids, it most likely can.
Try this write up by Google. Hope this one helps. If not then ill do an easy step by step. ....good luck. You know now that I think about it its easy doing it on windows witch doesn't make since it should be easier on a unix box for crap sakes!
http://www.google.com/gwt/n?u=http://developer.android.com/sdk/eclipse-adt.html
finally got it to work. It seems I was missing a file from the Android SDK. Everything is running smoothly, thank you all for your help.
Unfortunately it didnt say which file was missing..
pk198105 said:
finally got it to work. It seems I was missing a file from the Android SDK. Everything is running smoothly, thank you all for your help.
Unfortunately it didnt say which file was missing..
Click to expand...
Click to collapse
try using the sdk manager to update your sdk...see if that gets you the missing file...
-BMFC
i can't get fastboot to work. i placed it in the tools folder. if i enter "fastboot" in a terminal, i get the command line options. "fastboot devices" does not work, though adb and the android sdk are running fine. i'm able to make screenshots, but i'm not able to explore the phone or use fastboot. ideas?
when it says "adb: command not found" it usually isn't in your .bashrc path, or if you did put it in possibly you didn't log out/log back in or restart your computer.
PATH=”$HOME/bin:$PATH:/home/{USERNAME}/android-sdk-linux_86:/home/{USERNAME}/android-sdk-linux_86/tools"
glad you got it working though
could you help me, too?
if i enter fastboot in my terminal i get all the options:
Code:
[email protected]:~$ fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
so the program is working, executable and in my path.
adb does work, as well as the sdk.
i can connect to my phone via ddms and adb, but not via fastboot. it does not find anything....
ADB COMMANDS
This is just a simple guide on how to open up and run adb commands from your windows based operating system.
Open up run by simultaneously pressing the windows flag key and r.
In the window that pops up type cmd. Now command prompt is open
type the commands each followed by the enter key: cd\
cd androidsdk/tools
Now your in your in your androidsdk/tools folder. You can do several things in here but i'll start with some basics each
of the following commands is to be followed by the enter key
adb devices (this lets you know what devices are attached to the computer in usbdebugging)
How to get your logcat (this will put your logcat in txt format in your sdk tools folder)
adb logcat > logcat.txt
copy an app from your phone to your computer
adb pull /system/app/whatever.apk C:\ateam (replace whatever.apk with the app your pulling also replace ateam with the
folder your placing the app in
Install an app from your computer on your phone
adb install whatever.apk (put an apk in your sdk tools and replace"whatever" with the name of the apk and it will install it)
also you can add either -r or -s to reinstall or install on the sdcard for instance: adb install -r Rosie.apk
this command will reinstall the new rosie from your tools file and still keep the same user data as before.
-r for reinstall
-s for sdcard (gotta test this)
Push an app from your computer to your phones filesystem (in some cases also installs)
adb remount
adb push whatever.apk /system/app (put an apk in your sdk tools and replace "whatever" with the name of the apk and this
will push it to your system app folder. You can change the destination as well for example: You want to push Launcher2.apk
to your data/app folder: adb remount
adb push Launcher2.apk /data/app )
Remove an app from your phone
adb remount
adb shell
cd /system/app (this will change your disk to system/app you may also change to another folder as well)
ls -a ( a list will show of all the apps inside your system app folder)
rm whatever.* (replace the whatever.* with the name of a apk you want to remove )
Flash a recovery image to your phone
First pace the recovery image in your sdcard root and rename it to recovery (so the full name will now be recovery.img)
adb shell
flash_image recovery /sdcard/recovery.img (wait till this# sign shows up again before you type the next command)
reboot recovery
get your current battery level
adb shell cat /sys/class/power_supply/battery/capacity
get your current rom build
adb shell getprop ro.build.description
Reboot into fastboot ruu
adb shell reboot oem-78
How to run the ruu via adb
First thing first start the ruu give it permissions and so fourth
When it gets to the part where it says "Follow the instructons below..."
Move the ruu window out of the way and start your task manager
Go to processes right click on ARUWizard.exe and choose open file location
A new window will open scroll till you see ROM.zip
Copy and paste Rom.zip to your desktop
Once you have copied it to your desktop shutdown the ruu and task manager
Click start menu then click computer
A window will open up click the c drive
now click create new folder and name it test
put the rom.zip in the test folder
plug your phone in and open command prompt and type
Code:
adb devices
adb shell reboot oem-78
fastboot devices
fastboot getvar boot-mode
fastboot erase cache
fastboot flashzip C:\test\rom.zip
fastboot devices
fastboot getvar boot-mode
fastboot reboot
Very useful man thanks for the guide. I also think newbies would use this guide as its in the right catagory and not in some G1 section or Mt3g section.
Edit** isnt this already in the tuorials section?
sandboxlove said:
i think its a great idea, we need a more compilied list to refer to
add more!!!!
Click to expand...
Click to collapse
I'm going to try to add one everyday. tomorrows lesson how to run the ruu from adb
Powers16 said:
Very useful man thanks for the guide. I also think newbies would use this guide as its in the right catagory and not in some G1 section or Mt3g section.
Edit** isnt this already in the tuorials section?
Click to expand...
Click to collapse
Where? Pagelink
http://forum.xda-developers.com/showthread.php?p=5799939#post5799939
but its a less in depth reference so i hope this gets added into the tutorial section as here are no in depth tuts about adb in there..
also to remove apk
adb shell rm /system/ (then put in either app or media or what ever folder name /whatever.apk
Papa Smurf151 said:
also to remove apk
adb shell rm -r /system/ (then put in either app or media or what ever folder name /whatever.apk
Click to expand...
Click to collapse
rm -r is a recursive deletion and can have a lot of unwanted and harmful side-effects if used incorrectly. To just remove apks, a simple rm works just fine. If they typed the wrong directory, file name, whatever, a recursive deletion would clear the entire folder... Not really something you'd want.
This is great, I will be coming back for more.
Thanks a lot
DevinXtreme said:
rm -r is a recursive deletion and can have a lot of unwanted and harmful side-effects if used incorrectly. To just remove apks, a simple rm works just fine. If they typed the wrong directory, file name, whatever, a recursive deletion would clear the entire folder... Not really something you'd want.
Click to expand...
Click to collapse
thanks...i knew that but wasnt paying attention. I just copied and pasted from my adb notepad file. i edited my post and removed the -r
DevinXtreme said:
rm -r is a recursive deletion and can have a lot of unwanted and harmful side-effects if used incorrectly. To just remove apks, a simple rm works just fine. If they typed the wrong directory, file name, whatever, a recursive deletion would clear the entire folder... Not really something you'd want.
Click to expand...
Click to collapse
LOL, yeah, I've done that
Might want to also include a note that says when using linux or mac shell you replace the "adb" with "./adb" (I believe that is correct or at least what I do now when reading the windows cmd guides)
tejasrichard said:
LOL, yeah, I've done that
Click to expand...
Click to collapse
I wiped out 16 years of source code with it once....I got fired.
Kcarpenter said:
I wiped out 16 years of source code with it once....I got fired.
Click to expand...
Click to collapse
Oh damn that's crucial man. Hope they had backups
Screwin around
So I was screwin around with adb tryin to learn this stuff and I stumbled across this by just typing adb after cd'ing in. Hopefully its useful. Mind you I am a total noob to android/linux and this was a total accident. I am sure you all know about it though. Useful info though
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\>cd\
C:\>cd android-sdk-windows
C:\android-sdk-windows>adb
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB device.
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with the given serial number. Overrides ANDROID_SERIAL environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must be an
absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloade or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
C:\android-sdk-windows>
Hi, I'm abcdfv, and I approve this thread.
abcdfv said:
Hi, I'm abcdfv, and I approve this thread.
Click to expand...
Click to collapse
LOL Thanks
I've always been an advocator of EVERYONE learning the ADB basics at least.
updated with run the run the ruu via adb commands
I'm trying to flash my recovery image. I need help. What is the first comand I type at C:\Windows\System32> normally I type cd:\android-sdk-windows\tools
then i adb remount, then adb shell. When I do that now I get "remount failed: Invalid argument" I'm not TOTALLY clueless, although it may turn out that I am after this. any help would be great. I am booted in recovery, but since my recovery image is gone, its just an exclamation in a triangle. if i adb devices, i can see my phone and it says i'm in recovery. Thanks.
I need some serious help with this.....do you need to download anything on your computer?? can you explain all the stuff you need to do leading up to what you type into command prompt...anyone..i need help..i flashed darchstar froyo build and the recovery is all messed up..i cant flash anything..so i need to push a new recovery img.but i don't know anything about adb shell or anything .....please........ive never had to push anything..everyone always just puts flashable zips out for you...HELP
I can't login as root on ubuntu 0.3 on my htc hd2, any help?
sudo passwd
by default ubuntu doesn't have a root password,so set it via sudo.
this will solve your problem. but why?are you going to purge sudo?
option1:
Open terminal
sudo su -
option2:
create a new user and put in admin group
(as dhayman11 pointed out, "unknown sources" is in security settings, not developer options. but no luck anyway, like most of the settings app, it also crashes if you try to set it.)
instead, here is an extremely stupid idea that just came to me.
1. turn on adb wifi debugging
2. sideload your favorite terminal, e.g.
http://jackpal.github.com/Android-Terminal-Emulator/downloads/Term.apk
(ok I lied. you will need your desktop/laptop/phone/whatever, exactly 1 time. step 2 will be skipped forever after that 1 time.)
3. fire up said terminal from the settings->applications menu.
4. (LOL!)
$ adb devices
4a. if the above command shows no devices,
$ adb connect localhost
and proceed to step 5.
4b. if the command shows exactly 1 device, e.g. "emulator-5554", proceed to step 5.
4c. if the command shows more than 1 device (wtf?!) then you will need to specify a device of your choice ("-s somedevice") in every subsequent adb command, e.g.
$ adb -s emulator-5554 <whatever>
$ adb -s localhost:5555 <whatever>
etc.
5. e.g.
$ adb install /sdcard/Download/foobar.apk
$ adb shell
$ adb uninstall -k com.something.somethingelse
etc. etc.
6. profit? profit!
ok here is a slightly-less incoherent form of the senior-moment-reply I posted earlier
several days ago it occurred to me to alternatively use sshd for terminal access, because:
-a) I feel a little unsafe leaving adb wifi enabled all the time (ok it's only a small thing to turn it on and off, but still) - and for security reasons there is no way to enable/disable it programmatically e.g. from a script/shell/terminal/app (well theoretically this is not exactly true, but practically it is)
-2) some people (i.e. me) would like to do shell/terminal remotely sometimes, rather than on the AFTV (and other people don't have/want a keyboard)
ssh access makes a great alternative to Term.apk, but the problem is:
- Term.apk and/or (pick your favorite android ssh server) don't have permission to run e.g. "pm install foo.apk" - it will fail. (btw 'pm' is a great command, take a look sometime at all the options. it shares a lot of functions as the adb command itself. 'am' is another fun command...)
- so, the hilarious workaround of enabling adb wifi, "adb connect", and then finally "adb shell" or "adb install" etc., is still required. (b/c the adb user is in the 'shell' group, among others - giving it permission to run /system/bin/pm) - oh well.
for random reference:
Code:
127|[email protected]:/ $ id
uid=2000(shell) gid=2000(shell) groups=1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)
[email protected]:/ $ exit
[email protected]:/ $ id
uid=10009(app_9) gid=10009(app_9) groups=1015(sdcard_rw),1028,3003(inet),50009(app_40009)
(also note it appears the adb shell user might possibly have 'mount' abilities, but since the /dev/block/sd* nodes permissions' are really locked up, who knows...)
How to host a WordPress website from home on a Raspberry Pi Zero.
You will need:
-A Raspberry Pi
-A wireless adaptor
-A bit of time
This guide assumes you already have Raspbian running on your Pi.
All commands can be run over ssh but you will need to VNC into it
a bit later. So you could also do all of it through VNC if you wish.
WARNING:
This is a fun little project but it's not advised to run a website
from your home network. If you miss-configure something or don't keep
things updated on your Pi the risk is greater than if you use a
web hosting service because if your Pi gets compromised, the attacker
now has a full Linux distro already authenticated on your network.
The risk of this actually happening is about as low as getting mugged.
It's not likely but...better safe than sorry.
Now for the good bit:
Ssh to your Pi, change the default password to a strong one and lets get started:
Install apache2:
$ sudo apt-get install apache2 -y
$ sudo apt-get install apache2-util
install mysql and php:
$ sudo apt-get install mysql-server php5-mysql -y
(mysql will prompt you for setup)
Restart apache:
$ sudo service apache2 restart
Move to this directory:
$ cd /var/www/
create a new folder:
$ sudo mkdir wordpress
Move to the new directory:
$ cd wordpress
Get wordpress:
$ sudo wget http://wordpress.org/latest.tar.gz
Extract wordpress:
$ sudo tar xzf latest.tar.gz
Move the contents of the wordpress folder to the current directory:
$ sudo mv wordpress/* .
Delete the now empty folder and the tar:
$ sudo rm -rf wordpress latest.tar.gz
Set perms:
$ sudo chown -R www-data: .
Create a database:
$ mysql -uroot -p (this assumes username is root and will prompt for password)
$ create database WordPress;
Forward port 80 to your Pi:
There is no 'one way' to do this. it depends on what router you have.
If you don't know how to do it, use Youtube and Google to find out how.
What you want to do though is forward port 80 to your Pi's LAN adress.
(the adress you used to ssh to the Pi).
Note: Some internet service providers block traffic on port 80 by
default so you may need to use different ones. If thats the case you might
also need to setup apache differently.
Get a domain name:
Go to a freedns site(https://freedns.afraid.org/) and register a subdomain to
your Pi's EXTERNAL IP adress. You can find your external address by visiting
'whatismyip.com' however this requires a screen so you will have to enable VNC
on your Pi by typing '$ sudo raspi-config' and going to the 'advanced' menu.
You then need a VNC viewer on the computer you are setting this up from. So type
'$ sudo apt-get install xtightvncviewer' then connect to you Pi by typing
'$ vncviewer the.Pi.lan.ip:5901'.
Next we need to point apache to the right directory for Wordpress because
you may have noticed that at the moment your subdomain just takes you
to the apache startup page.
$ sudo nano /etc/apache2/sites-enabled/000-default.conf
This will open a config file. Make sure the directory listing in there
is pointing to your Wordpress directory and add your site alias within
the virtual host tags. It should look something like this:
<VirtualHost *:80>
# blah blah blah
# blah blah blah
# blah blah blah
ServerAdmin [email protected]
DocumentRoot /var/www/wordpress
ServerAlias yoursubdomain.here.com
#My changes
<Directory "/var/www/wordpress">
AllowOverride All
</Directory>
# blah blah blah
# blah blah blah
# blah blah blah
/VirtualHost>
press ctrl+o to save it. Hit enter to confirm then exit by
pressing ctrl+x
Now we need to install Wordpress.
In a browser type you Pi's LAN IP address and Wordpress will guide you
through the installation and setup.
(leave the database host as localhost when prompted)
Now we need to change the URLs in the database we created to
the URL of our subdomain.
For this you need to install PHPmyadmin:
$ sudo apt-get install phpmyadmin
You will be prompted to configure it and you will need to put
database username and password in.
The installation process actually adds the phpMyAdmin Apache
configuration file into the /etc/apache2/conf-enabled/ directory,
where it is automatically read.
The only thing we need to do is explicitly enable the php5-mcrypt
extension, which we can do by typing:
$ sudo php5enmod mcrypt
Afterwards, you'll need to restart Apache for your changes to be recognized:
$ sudo service apache2 restart
You can now access the web interface by visiting:
http://localhost/phpmyadmin (through vncviewer) or
http://lan_ip_of_Pi/phpmyadmin(from another machine on the network)
From here, once logged in, you should be able to see a collapsed directory
tree on the left side of the page. One of the databases listed here
should be named 'wordpress'. expand it by pressing the '+' then
click on 'wp_options'. Now in the main window you should see a
table with various entries. The ones we are interested in are
the ones named 'siteurl' and 'home'. Click the edit button to the
left of them and change the value of both of them to:
'http://YOUR_DOMAIN_HERE.com.'
Now there is just one last place to change the URLs.
In the browser of a machine on the same network as your Pi go to the
LAN IP of your Pi adding '/wp-admin' at the end. Log in with the
details you supplied during the setup. At the top of the page you will
now see an admin toolbar. Hover over the icon that looks like a dial
and click on 'dashboard'. When it loads the side bar, scroll down to
'settings' and select 'general'. Here you change 'Wordpress address URL'
and 'site address URL' to your shiny new domain name.
Voila! You should now have a live to the world Wordpress site
running off a cheap home server, with no hosting costs.
This guide 'should' get you all the way to a live site but there
is a chance that extra configuration is needed or that I forgot
something.
Similar steps can be used for all kinds of different servers. If You just want to serve files straight from an apache index style page you can follow this guide, missing out the wordpress stuff and leaving your apache configs alone. Implementing htaccess you can also password protect your files or a folder. If you do this I highly recommend not adding a directory listing for the folder that is 'private'. even if it is password protected.
Enjoy!!