Started to mess about with this earlier today, finally got the damn thing to work Turns out it is quite easy..
First, to get one thing straight, this will only boot the kernel, it will dump you at a shell which you have to remotely log on to via telnet over usb. There will be some (not so) fancy text appearing on your phone's screen but that is about it. Also, it only works on unlocked phones.
This is what you get:
On your computer you'll get this:
Cool, huh? Btw, this is running from a memory card, your OS will be untouched so as soon as you reboot the phone it will boot right back into WM2003/5/6.
1. What you need
* A HTC Typhoon running any rom of your choice (I did it on WM6).
* A miniSD memory card
* A Linux distro - I downloaded the Ubuntu Live CD and ran it through VMWare, no need to install anything or reboot your computer.
* miniSD image of Xanadux - this is the linux port for HTC devices. Grab the latest version here: http://rapidshare.com/files/92218185/Linux.zip.html
(these files are extracted from the miniSD image file found here: http://vivien.chappelier.free.fr/typhoon/download.html)
2. How to run linux on the Typhoon
1. Instead of installing linux properly on your phone which requires partitioning of the internal memory etc (a lot can go wrong) we'll put it on the memory card then a Windows Mobile program called HaRET will boot linux for us from WinCE. Completely non invasive in other words.
This bit is dead easy, just extract the Linux.zip file you just downloaded and copy the files to the root of your memory card (must be memory card, can't do this from the internal memory afaik). Next, go to the File Explorer on your phone and find the file HaRET.exe. Run it then press the run button (this button has focus when you execute HaRET.exe so just press the joystick when the windows appears) and you will see a message saying "Booting linux", then after a few seconds your screen will go black and some text will appear.
Voila! That's linux running on your phone!
2. Connect to the phone via telnet
If read the last line of text that appeared on screen you'll see that it says "Press enter to activate this console" but no matter what buttons you press on the phone nothing happens, some gibberish appears but that's it.
Solution: telnet to the phone from your computer.
Get Ubuntu to boot on your computer, then go to Applications->Accessories and run the Terminal. Next type in the following commands:
Code:
modprobe cdc_ether
modprobe usbnet
ifconfig usb0 up 192.168.9.1
and finally
Code:
telnet 192.168.9.10
Login with username root and you'll find yourself at a shell like the screenshot above. Everything you see from now on is coming linux from your phone!
I've noticed that Xanadux doesnt always initialise the USB port unless it is connected via USB when booting up so make sure you always have your phone connected via USB when you run HaRET.
Now I'm going to try to figure out how to get the GSM module to work...
LINUX based ROM??
Hi shandar,
I have read your post and I am interested to know if you are cooking a LINUX based ROM that will run in a WIndows Mobile device? That would be too good to be true.
Also another question is do you need to have Linux running on your desktop to make this tutorial work?
ryanchanmd said:
Hi shandar,
I have read your post and I am interested to know if you are cooking a LINUX based ROM that will run in a WIndows Mobile device? That would be too good to be true.
Also another question is do you need to have Linux running on your desktop to make this tutorial work?
Click to expand...
Click to collapse
Hey, well, I don't know enough to make a linux rom for smartphones. I'd love a working linux distro for Typhoons & Windows Mobile phones in general but it is way out of my league unfortunately.
Btw, I probably should clarify that I only wrote the tutorial, the actual linux port is made by someone else.
Hi,
I've rooted my phone and using jv1.5 adp firmware, during the rooting telnet was working fine without problems, but yesterday i flashed the boot images using information from these forums, and also installed a theme.
but later my phone showed telnet had just been installed, and now won't connect to phone, but standard terminal works, but had to tell it to allow me to use SU.
has anyone else had issues using telnet in the last 2 days on the phone...
thanks
Why are you using telnet? and how are you starting telnet?
I think you are a bit confused on what telnet is and why you needed it originally.
under the original instructions it tells you to use telnet to access the device
- Copy recovery_testkeys.img onto the Micro SD Card.
- Turn the phone on (if not already)
- Type enter telnetd enter to start telnet
- Telnet into the phone with telnet (telnet ipaddress) OR use the telnet application from the market and connect to localhost
- Run the following as root (in telnet)
Click to expand...
Click to collapse
but noticed today that telnet even though previously installed, states it just been installed after applying a theme and different boot up image
also not confused as to what telnet is, as you it on a daily basis at work under windows
If your phone is already rooted (I assume it is since you are applying themes) you do not need telnet anymore.
As long as you are using a custom firmware it should have root enabled in the shell so using the terminal will work just fine, no need for telnet.
yeh, using the terminal emulator, but couldn't work out why during the rooting process the telnet application worked and could connect to localhost, but now the connection is always refused
It is because you haven't started the telnet server.
Again I think you are a bit confused on what telnet is, how it works, and why you needed it to root in the first place. (and just because you "you it on a daily basis at work under windows" doesn't mean you aren't confused on what it is)
neoobs said:
It is because you haven't started the telnet server.
Again I think you are a bit confused on what telnet is, how it works, and why you needed it to root in the first place. (and just because you "you it on a daily basis at work under windows" doesn't mean you aren't confused on what it is)
Click to expand...
Click to collapse
no I am not confused as to what telnet is
i should still be able to use telnet on the phone and enter instructions (similar to how you would with most routers)
if doing enter, telnetd, enter and running telnet still refuses connection, and this has only happened since it advertised it has installed itself a day after already installing to firmware the phone
telnetd shouldn't advertise it has been installed.
Telnet is a protocol, technically it isn't a program, however telnetd is the server program (the kind that probably runs on your routers at boot) but you have to start it from a terminal in linux environments (like the G1)
The program you are trying to install would be a terminal prompt (the client side) this would allow you to connect to any terminal server you have network access to.
As said above you don't know what telnet is, you just think you do. The problem is you are trying to use the security hole (typing commands on the phone to run them as root) that has already been fixed. If you read a little more on how we have root you will find out that you can't just type telnetd anywhere you want. It has to be in a command prompt now because the security hole has been fixed.
this thread has gone off topic, and nothing to do with the original query
on my phone I have Superuser Permissions, Terminal Emulator and Telnet application
I use TE to access the phone to enter the commands via a prompt, but what I was saying was the telnet application you download to phone when doing the process of rooting allowed me to connect to localhost on port 23, which allowed me to enter commands as though I was using TE.
But after rooting, installing JV1.5 ADP, modifying bootimage and installing a theme, the phone reported it had downloaded and installed Telnet again, which I hadn't told it too, and if you then attempt to use it to connect to localhost it always refuses it.
So my question about anyone else having similar issues with telnet application still stands, ie has it reported it downloaded and installed itself again? after completing the rooting would it then prevent the telnet application from telneting to phone on port 23, meaning you can now only use terminal emulator? and can I easily remove the application without affecting terminal emulator?
thanks
It shouldn't download and install it self again without you helping or the rom you using having it built in.
I told you above and again you have to start the telnet server before you can use the telnet client. It isn't that hard to understand and if you really can't understand it then maybe you need to start looking into something else.
Telnet is not needed for terminal emulator.
Again I said it above you don't know what telnet really is. You don't understand server/client or protocols. Please google telnet and look for the wikipedia page and read about the protocol, the servers, and the clients.
neoobs said:
It shouldn't download and install it self again without you helping or the rom you using having it built in.
I told you above and again you have to start the telnet server before you can use the telnet client. It isn't that hard to understand and if you really can't understand it then maybe you need to start looking into something else.
Telnet is not needed for terminal emulator.
Again I said it above you don't know what telnet really is. You don't understand server/client or protocols. Please google telnet and look for the wikipedia page and read about the protocol, the servers, and the clients.
Click to expand...
Click to collapse
I know it shouldn't download and install again, this is my point for some reason it did and i'm not sure why and this is why I asked the question.
There is no need for you to constantly go on and flaming me by stating that I know nothing about telnet, this, that or the other. You don't know me from adam and I don't know you.
I do know what telnet is, it allows communication between 2 devices via CLI, and allows remote configuration of systems.
All I wanted to know was if this had happened to others, a simple answer of yes or know would have sufficed...
Wow, this got off topic quickly. I don't see why you'd need to assume he doesn't know what telnet is, neoobs. Just sounded like he had a problem and asked if anyone else is experiencing the same occurance. Personally, I prefer using telnet over the TE, for the simple fact, that I don't like looking at the bright blue screen.
In response to the original question, I haven't had anything download and install itself again. I have had the connection refused after starting the telnet daemon on several occasions, but that was due to either the Google servers syncing in the bg, or the browser or Market doing something.
Why don't you just uninstall and reinstall telnet?
First of all please notice, that this is not my own development project, it is just a port of the guide for HTC G1 from http://pdaclub.pl/forum/htc-dream/%28how-to%29-instalacja-debiana-%28na-g1%29/ for Xperia X8.
Please be aware, that this solution has been only tested with one Xperia X8 device running Floyo 0.30 (thanks to Racht for this great ROM !). I cannot guarantee that it will work on every other custom ROM as well as on the stock Xperia X8 ROM's.
Please also notice, that instructions in this tutorial in some cases can brick Your phone. I'm not responsible for any damage to the software or hardware caused by this tutorial. You can follow the instructions from this guide but only at Your own responsibility!
Please also notice, that I'm not an Android Developer. I'm just a user with some knowledge about Unix, so don't blame me if this tutorial won't work for You. You can post Your problems and we'll try to solve it together.
OK, I think that's all for the intro .
TABLE OF CONTENTS:
1) The purpose of this guide
2) Requirements
3) Things to prepare
4) Installation
5) Some known bugs
6) Some little tips
1) The purpose of this guide.
This guide reffers to the newbie users who want to run Debian Linux on their Xperia X8. Step by step I'll try to explain how to run Debian simultaneously (at the same time) with Android. To gain that we'll use a program/command chroot (http://en.wikipedia.org/wiki/Chroot) which will allow us to Run Debian in Android as something similiar to "virtual machine" on PC.
You may ask why to run Debian on Android device ?
There are several answers to that question:
a. For testing...
b. ...developing applications in for e.g. C/C++ for ARM platform and try to run them on Android OS.
c. Installing Linux applications (like web servers, WiFi cracking software) and test what is working and what isn't.
d. For fun
For those who are asking what Debian actually is - please refer to the page http://en.wikipedia.org/wiki/Debian.
2) Requirements.
Before continuing check if You and Your device meet the following requirements:
a. ROOTED Xperia X8 device (I recomend to have Floyo 0.30 by Racht ROM installed, because it was tested on this ROM. I don't know if it'll work on different ROM's.)
b. At least 800MB space free on Your SD Card
c. Access to PC computer
d. Basic knowledge about Windows command line and Linux shell
e. About 1 hour of free time to set up everything
3) Things to prepare.
a. Download one of the following packages:
http://rapidshare.com/files/327504536/debian750.rar
Click to expand...
Click to collapse
or
http://rapidshare.com/files/327491605/debian1.5.rar
Click to expand...
Click to collapse
These are the packages containing Debian drives image as well as all other files needed to install Debian on Android. The only difference is that the first one is 750MB and the second is 1,5GB. The second one is for bigger SD Cards, you'll get more free space in Your "virtual machine" after running it.
b. ADB Shell (can be found in Android SDK in folder platform-tools\ - http://developer.android.com/sdk/index.html)
c. SSHDroid from Market (only if You're planning to connect to Your Debian via SSH)
d. PuTTY for Windows (only if You're planning to connect to Your Debian via SSH - http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html)
e. ConnectBot or Terminal Emulator from Market (it's a good terminal application)
The bold items are necessary.
4) Installation.
PERFORM A FULL SYSTEM BACKUP USING XRECOVERY BEFORE PROCEEDING ANY FURTHER !
Now the best part !
There are several ways to install Debian:
1) Some are using Terminal Emulator application (preinstalled in Floyo 0.30)
2) Others are connecting with phone via SSH
3) But some are using adb shell command from Android SDK and that's the way we'll do this, because I know there are some differences between using adb shell and other ways. I tested it with adb and it is working so I think it is the right choice.
First, unpack the *.rar file of Your choice (debian750.rar or debian1.5.rar) to Your hard disk on a PC.
Replace file bootdeb which can be found in Debian folder after unpacking the archive with the one from bootdeb.zip file attached to this post. You need to do this, because the bootdeb file which is in the archive won't let You boot Debian correctly. It'll only cause Xperia X8 to restart after few seconds since execution. The file in bootdeb.zip has been corrected by me and it allows to boot Debian without any (known ) bugs.
Copy the Debian folder from the archive directly to the SD Card (also known as a root directory of Your SD Card). You should have the following directory tree on Your SD Card visible in Xperia X8:
/sdcard/Debian/bootdeb
/sdcard/Debian/debian.img
/sdcard/Debian/installer.sh
etc...
Click to expand...
Click to collapse
Enable USB Debugging in Xperia X8. To do this go to Settings->Applications->For programmers and check USB Debigging.
Connect Your phone via USB and don't mount the SD Card (just like You want to charge the phone via USB).
On Your PC click Start->Run, type cmd and cd to the directory where You installed Android SDK, then cd to platform-tools and execute command adb shell. After execution You should see a # symbol in the command line window like on a below screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now execute the following commands in ADB ahell on PC:
su
cd /
sh /sdcard/Debian/installer.sh
Click to expand...
Click to collapse
And You shoul get something like this:
VERSION 2.1
Custom Debian Bootloader is now installed! Quick huh?
etc...
Click to expand...
Click to collapse
And it's done ! Debian Linux has been installed.
Type in ADB Shell command
exit
Click to expand...
Click to collapse
As many times (I guess 3) until command line window disappears. Disconnect Your phone from PC and unplug the USB cable.
Now let's try to run Debian - on Xperia X8 run ConnectBot or Terminal Emulator and type:
su
sh /sdcard/Debian/bootdeb
Click to expand...
Click to collapse
Remember to allow the terminal application to run as a superuser.
After a while You should see a screen similar to the below screen shot:
I removed the lines (blured section) which You won't see after first boot. I have them, because I installed Apache Web Server and it is starting at the logon .
As You can see we are logged into Debian Linux !
Now, execute the following command:
/scripts/onetime.sh
Click to expand...
Click to collapse
It's necessary only after first logon. It'll let You to set up root password (only for Debian, not for Android) and do some more stuff (actually I didn't even check what this script is doing - forgive me).
And it's done... Now You are on Your own with Debian installed ! Go, play around, because it is a fully functional operating system for Your demand .
What about the performance ?
My Debian is still working since one day in the background (minimize the Terminal Emulator window after logging in) and I haven't suffer any problems with the low performance yet. I even set up an icewm window manager and VNC Server to be able to log in to my machine via VNC client and see the desktop and it isn't too laggy . But that's only a stupid future. The most power we get because of the access to Linux Shell (the command line which let us to use Linux applications on our Xperia X8).
4) Some known bugs.
For Your own safety read this short section.
1) Better don't try to unmount the SD Card from Xperia X8 (for e.g. when mounting the phone to the PC) when Debian is running. I didn't try this yet, but the bootdeb script is creating something called loop device in the Android system which should be properly unmounted. If this device will wanish due to some user activity the phone may not boot correctly any more.
2) When You finish playing with Debian always use the exit command to safely unmount the loop filesystem. After exit Your phone needs to be rebooted, better don't try to override this setting.
3) If somehow You will loose connection with Debian in Terminal Emulator You always can run:
sh /sdcard/Debian/bootdeb
Click to expand...
Click to collapse
And log in again. You'll just receive several errors on the boot screen, because the script will try to mount already mounted file system.
5) Some little tips.
1) After first logon execute the following commands:
cd /etc/apt
nano sources.list
Click to expand...
Click to collapse
And in the opened text editor add these lines (do not overwrite the file contents):
deb http://ftp.debian.org/debian lenny main contrib non-free
deb-src http://ftp.debian.org/debian lenny main contrib non-free
Click to expand...
Click to collapse
After this execute the command:
apt-get update
Click to expand...
Click to collapse
It will update Your applications repository available for Debian.
2) Running Apache Web Server:
Execute command:
apt-get install apache2
Click to expand...
Click to collapse
To install Apache Web Server. When the installer asks You if You want to proceed with the installation type Y.
After installation run command:
/etc/init.d/apache start
Click to expand...
Click to collapse
And then You can try to connect to Your phone on port 80 using HTTP browser and see if there's a message It works! .
3) Uploading files to Your Debian "virtual machine":
Install SSHDroid from Android Market.
Download program WinSCP and connect to Your device on port 22 using root as a user name and admin as a password.
After connection open location /data/local/mnt and You'll see Your Debian file system.
I think that's all for now.
I hope this guide will help "newbie" users to run Debian on their phones.
If You have any more questions or problems please let me know.
Regards,
Chris.
you should post this on development!
At the moment it's a little fiddling. Start phone -> connect bot -> su -> sh /sdcard/Debian/bootdeb -> from there I should be able automat anything
How can I use some kind of autostart?
Why I lose connection in ConnectBot when I disable mobile internet connection? Doesn't make sense to me. Mobile internet has nothing do do with local shell, or?
kingsize623 said:
you should post this on development!
Click to expand...
Click to collapse
He should. This is GREAT!
hello,
if i typ
su
sh /sdcard/Debian/bootdeb
and then come some text
and my phone does reboot.
what am i doing wrong?
kingsize623 said:
hello,
if i typ
su
sh /sdcard/Debian/bootdeb
and then come some text
and my phone does reboot.
what am i doing wrong?
Click to expand...
Click to collapse
I also had this problem. But try using ConnectBot - this is known for me to work.
kingsize623 said:
hello,
if i typ
su
sh /sdcard/Debian/bootdeb
and then come some text
and my phone does reboot.
what am i doing wrong?
Click to expand...
Click to collapse
Hi kingsize623!
As I said at the begining this script is highly ROM-dependent. It can run on some ROM's, but on the others there will be many problems.
I suggest You to edit file /sdcard/Debian/bootdeb in some text editor (I suggest Notepad++), locate the line:
busybox mount -o loop,noatime $kit/debian.img $mnt
Click to expand...
Click to collapse
(it should be line 47), and change it to:
mount -o loop,noatime $kit/debian.img $mnt
Click to expand...
Click to collapse
This should help. If it won't, there can be a lack of some module in Android on Your device which will prevent the script from running (no loop support for e.g.).
If You'll face some further problems let me know.
bagers said:
I also had this problem. But try using ConnectBot - this is known for me to work.
Click to expand...
Click to collapse
i've treid
and make a printscr
http://imageshack.us/photo/my-images/233/screenshot1315842466117.png/
http://imageshack.us/photo/my-images/18/screenshot1315842470958.png/
bagers said:
At the moment it's a little fiddling. Start phone -> connect bot -> su -> sh /sdcard/Debian/bootdeb -> from there I should be able automat anything
How can I use some kind of autostart?
Why I lose connection in ConnectBot when I disable mobile internet connection? Doesn't make sense to me. Mobile internet has nothing do do with local shell, or?
He should. This is GREAT!
Click to expand...
Click to collapse
Hi bagers!
Thanks for the comments on this post !
First of all, You're right, maybe I should post it on Dev section, but I didn't use XDA-DEVELOPERS much in the past, so I was afraid I may get kicked because of such information from "newbie user" in Dev section. This section (in my understanding) is for Android guru's, and I'm not one of them .
As for the autostart: the only thing You can automate in my opinion is the part where You type:
su
sh /sdcard/Debian/bootdeb
Click to expand...
Click to collapse
The only thing You need to do is to write a simple script which will look like the following:
su
cd /sdcard/Debian/
sh bootdeb
Click to expand...
Click to collapse
or
su
sh /sdcard/Debian/bootdeb
Click to expand...
Click to collapse
Name it for e.g. startdeb and place it in /system/bin for e.g. (I think bash will look for files in this directory by default, but I'm not sure about that).
Now, everytime when You'll try to run Debian, just open ConnectBot and type startdeb - this should automatically make You su and execute the startup script.
As for the dissconnections issue:
As far as I can see this problem exists on Floyo 0.30 as well. I'm not yet sure why it acts like that.
kingsize623 said:
i've treid
and make a printscr
http://imageshack.us/photo/my-images/233/screenshot1315842466117.png/
http://imageshack.us/photo/my-images/18/screenshot1315842470958.png/
Click to expand...
Click to collapse
As I wrote in previous post - try modyfying the startup script.
You also should have Busybox installed (if You don't have it download it from Market).
I installed also sshdroid and connected to the phone from Windows 7 using Putty. But, when I disconnect putty, then I will also see this "Rebooting device to ensure clean takedown.".
Ehrm, I just wanted to disconnect putty, not to shut down debian. Another bug?
Can you disable all this "Rebooting device to ensure clean takedown.", it's really disturbing.
krzysiek_grucha said:
As for the autostart: the only thing You can automate in my opinion is the part where You type:
The only thing You need to do is to write a simple script which will look like the following:
or
Name it for e.g. startdeb and place it in /system/bin for e.g. (I think bash will look for files in this directory by default, but I'm not sure about that).
Now, everytime when You'll try to run Debian, just open ConnectBot and type startdeb - this should automatically make You su and execute the startup script.
Click to expand...
Click to collapse
Okay, I done that and something really strange happened.
I made a files called "sd" in /system/bin with content:
su
sh /sdcard/Debian/bootdeb
Like you said.... But when I type sd in ConnectBot then, debian will start, and then the phone will restart...
But, when I type su and sh /sdcard/Debian/bootdeb, manually in ConnectBot, then debian will start with no error. Strange, huh? Any idea? Bug?
krzysiek_grucha said:
As for the dissconnections issue:
As far as I can see this problem exists on Floyo 0.30 as well. I'm not yet sure why it acts like that.
Click to expand...
Click to collapse
Please add it to the bug list. Maybe later someone will have an insight.
bagers said:
I installed also sshdroid and connected to the phone from Windows 7 using Putty. But, when I disconnect putty, then I will also see this "Rebooting device to ensure clean takedown.".
Ehrm, I just wanted to disconnect putty, not to shut down debian. Another bug?
Can you disable all this "Rebooting device to ensure clean takedown.", it's really disturbing.
Okay, I done that and something really strange happened.
I made a files called "sd" in /system/bin with content:
su
sh /sdcard/Debian/bootdeb
Like you said.... But when I type sd in ConnectBot then, debian will start, and then the phone will restart...
But, when I type su and sh /sdcard/Debian/bootdeb, manually in ConnectBot, then debian will start with no error. Strange, huh? Any idea? Bug?
Please add it to the bug list. Maybe later someone will have an insight.
Click to expand...
Click to collapse
Hi again !
There are lots of bugs as I can see . But... If You're connecting from Putty don't be surprised that the phone is rebooting after closing Putty window. It works like that:
1)You're running the sh /sdcard/debian/bootdeb from Putty - Putty is the only terminal for the script.
2)When You dissconnect suddenly the only terminal which was preventing the bootdeb script from running wanishes so the script continues working (so it's jumping to reboot section). That's not a bug, it was written to work like that.
I don't suggest You to disable the rebooting - it helps You to have a clean unmount. If You override this, strange things may happen when You'll boot for the next time, but it is not sure for 100% - check it for Yourself .
As for the not working script file - I thought that su command won't work in the script. That's why the bootdeb script doesn't already have it included.
If You want to know about some more bugs:
Don't try to set up OpenSSH on Debian - it won't work.
Don't run FTP server like proftpd or vsftp - port 21 is forwarded correctly, but port 20 is not, and that's why FTP is not working.
There are many bugs, but if You'll follow simple rules You won't have any problem with using Debian.
Can you think of some workarround in order to use Windows+Putty+Disconnect+Nophonereboot?
I really like to use that phone now as a server, because the power consumption is very very little (compared to a PC server). All time connected to charger (~3,5 W) would only coast me around 5 or 10 Eur per year. l So I plan to run Debian on the phone at all times and from time to time to administer my "server" using Putty and WinSCP.
But of course, at some time I'll have to quit Putty (and WinSCP)...
The problem is, that SSHDroid runs "outside" of Debian. The ssh would need to run "inside" Debian. You already told me not to try OpenSSH. Do you know any alternative to OpenSSH or an alternative protocol? Connect and remote administer by anything else, vnc server maybe (vnc for console?), but not ssh.
bagers said:
Can you think of some workarround in order to use Windows+Putty+Disconnect+Nophonereboot?
I really like to use that phone now as a server, because the power consumption is very very little (compared to a PC server). All time connected to charger (~3,5 W) would only coast me around 5 or 10 Eur per year. l So I plan to run Debian on the phone at all times and from time to time to administer my "server" using Putty and WinSCP.
But of course, at some time I'll have to quit Putty (and WinSCP)...
The problem is, that SSHDroid runs "outside" of Debian. The ssh would need to run "inside" Debian. You already told me not to try OpenSSH. Do you know any alternative to OpenSSH or an alternative protocol? Connect and remote administer by anything else, vnc server maybe (vnc for console?), but not ssh.
Click to expand...
Click to collapse
The workarround is very simple. As You said SSHDroid works on the "outside", but I'm telling You that it can work in the "inside" of Android as well. I tried to use X8 as a web server so this solution has been tested.
1) Run SSHDroid
2) Connect using ConnectBot to [email protected] and run:
su
sh /sdcard/Debian/bootdeb
Click to expand...
Click to collapse
You'll have Debian on the phone already started.
3) Connect to Your phone via Putty with Debian started in ConnectBot and type:
chroot /data/local/mnt /bin/bash
Click to expand...
Click to collapse
It will connect to the virtual Debian on Your phone and will let You to administer it, but on the second side it won't even touch bootdeb script which is annoying You so much, so the phone won't restart after logging off from Putty, because the "main" session will be still held by ConnectBot on the phone.
The only thing You need to remember is to safely kill Debian when You'll want to restart the phone using exit command in ConnectBot (which will cause the phone to restart as usual).
As I know, You'll very soon tell me, that there's a bug - don't let the Android device to go to "sleep" (turn off the screen), because the performance of the "server" will get very low because of lower CPU speed in sleep mode.
Hope it'll help
krzysiek_grucha said:
As I wrote in previous post - try modyfying the startup script.
You also should have Busybox installed (if You don't have it download it from Market).
Click to expand...
Click to collapse
I've treid it twice and i've bricked my phone twice
And now i can't instal gingerdx (i was on gingerdx)
So is there any way to deinstal the whole debian.
And trey it argain on froyo(i've learnt something!)
kingsize623 said:
I've treid it twice and i've bricked my phone twice
And now i can't instal gingerdx (i was on gingerdx)
So is there any way to deinstal the whole debian.
And trey it argain on froyo(i've learnt something!)
Click to expand...
Click to collapse
Hi !
I guess there's some problem with GingerDX.
To Deinstall Debian You just need to delete the Debian folder from /sdcard/ . Nothing has been installed into /system/.
krzysiek_grucha said:
Hi !
I guess there's some problem with GingerDX.
To Deinstall Debian You just need to delete the Debian folder from /sdcard/ . Nothing has been installed into /system/.
Click to expand...
Click to collapse
And You shoul get something like this:
VERSION 2. Custom Debian Bootloader is now installed!
Quick huh? etc... And it's done.
Click to expand...
Click to collapse
He instals a custom boatloader right?
Mayby it doesn't work with gingerdx becouse he restarts after the gingerdx logo but before the cyanogen mod 7 logo, i don't know how to name it
Btw, sorry for my bad english
kingsize623 said:
He instals a custom boatloader right?
Mayby it doesn't work with gingerdx becouse he restarts after the gingerdx logo but before the cyanogen mod 7 logo, i don't know how to name it
Btw, sorry for my bad english
Click to expand...
Click to collapse
No - if I am not completely wrong - the real bootloader of the x8 will not be changed in any way.
The debian bootloader is only needed to start debian inside android.
kingsize623 said:
I've treid it twice and i've bricked my phone twice
And now i can't instal gingerdx (i was on gingerdx)
So is there any way to deinstal the whole debian.
And trey it argain on froyo(i've learnt something!)
Click to expand...
Click to collapse
Don't panic, as long as you did not mess with the bootloader, you can always rescue your device.
I also bricked my device once, could not even get to xrecovery. Read this post.
http://forum.xda-developers.com/showpost.php?p=13341271&postcount=2
No worry, with PC Companion and repair (you'll loose all data) you will be able to recover your phone.
My phone has GPRS and WiFi enabeld at the same time.
Is it possible to tell the a few selected debian processes "use only GPRS, no WiFi"?
bagers said:
No - if I am not completely wrong - the real bootloader of the x8 will not be changed in any way.
The debian bootloader is only needed to start debian inside android.
Don't panic, as long as you did not mess with the bootloader, you can always rescue your device.
I also bricked my device once, could not even get to xrecovery. Read this post.
http://forum.xda-developers.com/showpost.php?p=13341271&postcount=2
No worry, with PC Companion and repair (you'll loose all data) you will be able to recover your phone.
Click to expand...
Click to collapse
so you can't HARD brick your device?
o, and thanx for your help
kingsize623 said:
so you can't HARD brick your device?
Click to expand...
Click to collapse
I also asked that myself....
http://forum.xda-developers.com/showthread.php?t=1239274
Afaik - from my knowledge from reading and searching the forums alot - a permanent (must send to se to repair) brick is only possible if you want to use the new cracked bootloader and mess up something.