Database Develop

[HOW-TO] Run Debian Armel on your N1

Hi all!
I want to share the way i have to run Debian on Nexus One
I'm editing my own install of deb-armel and ill upload to everyone but first i need to finish it
By now, we will use a qemu image ready and edit it to your needs
You'll need a SD parted with Amon_RA recovery, few files i'll upload later and some skills with Debian, of course hehe
Partition could be user-alike but i recommend:
Im using a microsdhc 8gb class-2 from my magic
- EXT3: 2gb (nice for install a lot of stuff)
- SWAP: 150MB
- The rest as fat32
You need also a rom with app2sd or mount ETX3 partition under /system/sd, im using Modaco's 1.3
First of all, im working on archlinux but this can be done on windows too using the qemu version for windows
Install qemu on your machine.
NOTE: Also you can start a new installation from 0 using images (iso) and info found on google
Now we will use the following QEMU images:
http://people.debian.org/~aurel32/qemu/armel/
We will download the followings Of course you can choose the small or normal version with X preinstalled (the X version preinstalled is not tested by me and i dont know if works)
debian_lenny_armel_small.qcow2 150M
initrd.img-2.6.26-1-versatile 2.1M
vmlinuz-2.6.26-1-versatile 1.2M
Put they in your home folder or where u want.
Now, lets run it.
Use the following command (run it from the folder you have the downloaded files) :
qemu-system-arm -M versatilepb -kernel vmlinuz-2.6.26-1-versatile -initrd initrd.img-2.6.26-1-versatile -hda debian_lenny_armel_small.qcow2 -append "root=/dev/sda1"
Wait a moment... Debian-armel running under qemu
Here are the configuration by default:
- Keyboard: British English
- Language: English
- Mirror: ftp.uk.debian.org
- Hostname: debian-armel
- Root password: root
- User account: user
- User password: user
Edit the system to fit your needs, im not going to explain how to do this, im asumming you know how to. If u don't, use the debian reference guide:
http://www.debian.org/doc/manuals/debian-reference/
Of course, you'll need to edit basic things as locales, network, ssh preferences, etc...
Edit your system, update, configure packages, etc...
Once edited and configured, quit you virtual machine.
Now, we are going to convert the qemu image to a raw image, mount the fs and copy to your SD
Assuming you still in the same folder as the qcow2 image of debian (for windows, google a little, im sure there are something to do the same):
qemu-img convert -O raw debian_lenny_armel_small.qcow2 debian.raw
With this will obtain the qcow2 converted to a raw file (without touching the original qcow2 file)
Now mount it where u want or follow this steps:
sudo mkdir /media/debian
Before mount, lets see where start the partition on the raw file:
sfdisk -l -uS debian.raw
U will see a list of partions under the raw file, use the first, like this one:
debian.raw1 * 63 20225834 20225772 83 Linux
Now, we know the / starts at 63, mount this partition
sudo mount -o loop,offset=$((63*512)) debian.raw /media/debian
Ok, we have our partition mounted now, lets make a copy in our EXT3 partition on SD.
Use the USB Storage function from android, sd card reader... and mount the EXT3 partition
Once mounted, copy everything from /media/debian to /media/yourSDext3mounted
cd /media/debian
sudo cp -a * /media/yourSDext3mounted/
If everithing works as expected, umount the systems /media/debian/ and /media/yourSDext3mounted or use the Android notif to disconnect the USB storage function
Check if everything is now in the SD EXT3. Open a terminal and adb shell
adb shell
cd /system/sd
ls
U'll see the Debian / extructure and the app & app-private
Of course dont worry about this, u can still using apps2sd and debian at the same time
Now, it's time to boot debian
We need some modded files from the G1 version to boot it:
Download from Megaupload: http://www.megaupload.com/?d=Q67SNOBC
Download from MediaFire: http://www.mediafire.com/?mxgcyk3whdt
Also, files attached to post (rename the extension to tar.gz)
Put the files into your FAT32 SD partition, no in a folder just in "/"
Now, it's time to give it a try
U have two ways:
Open a terminal window in your PC
adb shell
cd /sdcard/
sh installer.sh
sh bootdeb
Or:
Open up a terminal in your N1, like Terminal Emulator on Market
cd /sdcard/
sh installer.sh
sh bootdeb
PROFIT!!!
Enjoy your debian-armel on your N1
For the next chapter, how to run X with VNC Viewer
Bye and thanks for reading!

Looks like Klingon to me.

I have Debian running too now

Nice! Cant wait to try it out!

nice, i've been looking for a n1 debian how-to

Installing debian is pretty much the same as running it on your g1. I had it working the day after I got mine using the g1 instructions.

So, what's the reason or running debian on your phone?
Jst wondering
u

The reason by now is just fun hehe
But, if we can run it natively via fastboot, would be awesome hehe
Sorry for the delay guys, ill do it now, the last night was too late for me 4am here hehe
EDIT: Just give some time more, i going to try it with the Cm 5.0 beta 1

jairuncaloth said:
Installing debian is pretty much the same as running it on your g1. I had it working the day after I got mine using the g1 instructions.
Click to expand...
Click to collapse
I couldnt get chmod or installer.sh from the g1 instructions to work. I tried it both with bacon and modaco 1.3. I skipped the jesusfreak part though so maybe thats why. Anyway seeing confirming instructions would be nice.

Because the g1 files need to be modded first
I have it running it under modaco 1.3 and now im going to try it with the new b1 from cyanogen

Guide ready
Enjoy it!

Hi,
i have one question about debian. Is the network traffic routed trough android, or does debian has direct access to the wlan adapter for monitor mode and aircrack ?
meld0

it's using the same ip and mac, so is shared for both
If there are the apropiate drivers maybe, don't really know

Calling Linux Experts!!! hehe
Is there any way to create a boot.img bootable via fastboot to run the ext3 partition of sdcard with debian?

Driskol said:
Calling Linux Experts!!! hehe
Is there any way to create a boot.img bootable via fastboot to run the ext3 partition of sdcard with debian?
Click to expand...
Click to collapse
sorry for being noob in this matter but, why do i need debian on my phone? what does it give me?
amir

The answer is a choice, Android or a Full Desktop OS with Firefox, Thunderbird, OpenOffice, etc...

When its booting I'm getting an error:
/system/bin/bootdeb: line 61: chroot: command not found
Doing "find / -name chroot" only returns binaries within the debian image.
Any ideas?

Driskol said:
The answer is a choice, Android or a Full Desktop OS with Firefox, Thunderbird, OpenOffice, etc...
Click to expand...
Click to collapse
How well does Firefox run?
Can anyone take some pics or video?

Any instructions for creating and mounting linux as an img file instead of using separate partitions?

tetlee said:
When its booting I'm getting an error:
/system/bin/bootdeb: line 61: chroot: command not found
Doing "find / -name chroot" only returns binaries within the debian image.
Any ideas?
Click to expand...
Click to collapse
Maybe your rom doesn't have Busybox
EDIT: Im going to make a img version tutorial
Of course, this version was without the highmem kernel, now with more ram, more flawlessly

[DEV-ADDON]DS7Ubuntu v1.0 --- Text Based Ubuntu 11.04 running on Dell Streak 7!

First of all, I need to give my thanks to great DevGhostofNet for his excellent work on getting Ubuntu 11.01 running on Xoom. I borrowed his template on this instruction page as I really don't have my template and using this way to show my appreciation to his work.
Second, I figured though I am not big dev by any means, hopefully any time I spent on such things can add some value to owners of either DS7 or Xoom, especially DS7, which really needs any effort on it in addition to testing help.
So I would throw in my two-cent hours/efforts to get this started. I see huge potential in it, though now it is quite WIP, because the non-graphical version is running well but not Gnome sessions.
1.What is working?
Shell Ubuntu 11.04
I modified the installation scripts to mount DS7 partitions correctly and copy some modified script into original image.
2. What is not working?
Gnome Session
I can install necessary components up to a point where the wall paper is loaded, sidebar is loaded but the guest system did not take/register input properly yet.
3. Why we care?
It has huge potential in it. It uses a part of your sdcard to run a guest system, and you can literally install all those great Ubuntu apps in it in future when more dev effort makes this happen.
4. What is the impact to my existing Android OS?
Minimal. The impacts are:
1. there will be ubuntu scripts in /system/bin/
2. Loop7 device will be borrowed while ubuntu is mounted.
3. under /sdcard, there is a folder ubuntu which pretty much contains everything
4. in LOST.DIR of your /sdcard, there may be lots of temp files if you experimented a lot of install/uninstall of this guest system.
If you still want to take a crack now.........
DISCLAIMER: I will not responsible for any bricked device. Please although this experiment won't affect your other files at all, but **** happens all the time, please do backup and understand what you are trying to do before proceed.
[Before Installation:]
1. You should know what you are doing at this step.
2. You have rooted your device already
3. You configured adb and have a terminal apps in your DS7. (Terminal apps can be found in market. Android Terminal seems to work fine)
4. You have a VNC client. (Android-vnc in market seems fine)
[Installation:]
1. Download the DS7Ubuntu files From my post at http://www.OpinionatedFool.com
2. Extract it into /sdcard/ubuntu folder
3. Open a terminal
Code:
su
cd /sdcard/ubuntu
sh ubuntu install
Just click yes when you are asked some questions. This process takes about 5 mins
reboot after installation
NOW after rebooting, you officially are running a text based Ubuntu 11.04
4. Open you terminal
Code:
su
ubuntu start
ubuntu shell
If you are interested to go further, I really encourage to because we need better devs to bring us further. I am willing to try more but it will take longer time as I have been away from Linux for a good 6 years.
5. After you are in Ubuntu Shell environment. you can do
Code:
vi /sbin/installubuntu
6. Inside installubuntu, the following are present:
Code:
#!/bin/sh
/usr/bin/apt-get -y -q update
/usr/bin/apt-get -y -q upgrade
/usr/bin/apt-get -y -q install python-software-properties
#/usr/bin/add-apt-repository ppa:unity-2d-team/unity-2d-daily
/usr/bin/apt-get -y -q update
/usr/bin/apt-get -y -q install tightvncserver xrdp
/usr/bin/apt-get -y -q install ca-certificates desktop-file-utils doc-base eog g
conf-editor gedit ghostscript-x gnome-about gnome-applets gnome-control-center g
nome-media gnome-menus gnome-nettool gnome-panel gnome-session gnome-session-can
berra gnome-system-monitor gnome-system-tools gnome-terminal gnome-themes-select
ed gnome-themes-ubuntu gnome-utils gtk2-engines gtk2-engines-pixbuf gucharmap hu
manity-icon-theme indicator-applet-session inputattach language-selector launchp
ad-integration lftp libgd2-xpm libgnome2-perl libpam-ck-connector libsasl2-modul
es libxp6 nautilus nautilus-sendto notify-osd rarian-compat screen smbclient sof
tware-center synaptic software-properties-gtk ttf-dejavu-core ttf-freefont ubunt
u-artwork ubuntu-extras-keyring ubuntu-sounds unzip update-manager update-notifi
er x-ttcidfont-conf xterm yelp zenity zip maximus
/usr/bin/dpkg-divert --local --rename --add /sbin/initctl
/bin/ln -s /bin/true /sbin/initctl
I am good up to completion of this step in the script above
Code:
/usr/bin/apt-get -y -q install tightvncserver xrdp
Then the following bulk apt-get process will cause issues. The main course is on gconf2 as far as I know.
I tried to install them separately after install gconf2, but it is not stably working.
i.e. sometimes I did install them all correctly, but sometimes I am getting segmentation error, which is annoying and requires wipe ubuntu folder and reinstall ubuntu.
I am too rusty on Linux now that better devs may figure it out easily.
[How to Uninstall it?]
In case you want to get rid of it. Here is how:
Through ADB or Terminal Simulator in your DS7
Code:
adb shell
su
mount -o remount,rw /dev/block/mmcblk3p3 /system
rm /system/bin/ubuntu*
mount -o remount,ro /dev/block/mmcblk3p3 /system
[Next Step]
Install and configure a working copy of Gnome-session on this successfully. Hopefully there will be Kernel Dev to have a Ubuntu kernel specifically for DS7? That will be the best.
We can then
1. Run Apache server and you will access your files through Dell Streak 7 as long as you are tethering in its own LAN. (or a lot more)
2. Run browsers in graphical version of Ubuntu on your DS7 so that you can do whatever with hulu or netflix or anything. Basically you are carrying a freaking DS7 laptop with you. with touch screen and huge mobility
[Notes]
1. pts need to mounted
2. use Unity-2d seems to be better than Unity
3. mtab need to be replace manually with the mtab I included in the zip file
4. kernel is not configured to have shared memory management ...

I'll definitely be following this thread with interest!

native ubuntu would be nicer rather than the crap of chrooted ones, they are just pointless IMHO as the device has to try and manage 2 oses at once, the 7 doesnt realy have the ram to manage that

Any updates on this project ?
Guess not :-(

Quick question to the op
Does wifi work so you can update / install packages?
If so, does it see the wifi cards chipset? I'm looking into getting aircrack-ng set up to tinker with. ( saves me from dragging out my laptop to test security on networks with my job )
Currently I'm using my Mac with kismac which does the job nicely , however, if I can use the ds7 under Ubuntu its one less reason to drag it along.
Can you copy the device information for me or does it act like a LAN card ?
Thanks !!

what is the latest development?

In a few weeks, i will tell my team to look at the cm7.1 things. I hope you will help us? I will send you a pm but remember me

ubuntu
is this still being worked on or attempted? or is there a ubuntu rom out already?

Is this anything like Ubuntu installer...
http://forum.xda-developers.com/showthread.php?t=1390351

[Dev] Modify stock image script

In case someone would like to build an own image based on the stock firmware,
I wrote a script that performs the neccessary steps (which where mostly described at the xda-forums) automatically on a linux based system.
It is very raw, and is not well optimized. It also is using many sudo calls for creating and modifying the image. Maybe someone has another, better solution.
Usage:
Download and unpack the ExtractAOS archive:
Code:
tar xfj ExtractAOS.tar.bz2
At first you need to place a AOS update file (firmware_archos_it4.aos) into the "dl" folder.
Then copy a busybox.tar.bz2 file, which contains the statically linked binaries of busybox (no subdirectories) inside the archive:
Code:
ash
busybox
cat
chgrp
...
Also make sure that following tools are installed on your system:
unsquash
unzip
tar
Then start the main script:
Code:
./unpackAOS
You will see a menu like this:
Code:
---------- Unpack and Modify Archos image -----------
1 Cleanup: Umount all mounted devices and delete all created files.
2 Download needed packages
3 Setup build directory
4 Create new Ext4 loop image and mount it to MOUNT_DIR
5 Extract AOS image
6 Copy AOS image contens into /data/ExtractAOS/archos_update_folder
7 Modify image in /data/ExtractAOS/archos_update_folder
8 Finish image and unmount it
88 Perform step 3-8 automatically
99 Exit
Then download needed tools via menu item "2".
If the download are successfully done, then you can enter "88"
to build your own archos.ext4.update image file.
Notes:
I'm on a 64 bit system. Letama seems to provide binaries also for 32 bit sytems. In that case, you can modify and set the correct binary within the script file.
This script is intended to provide a base for developers which want their own customisations
Special thanks to:
letama
surdu_petru

Thanks i will try it next weekend
Gesendet von meinem HTC Desire mit Tapatalk 2

Quallenauge said:
Also make sure that following tools are installed on your system:
unsquash
unzip
tar
Click to expand...
Click to collapse
On which firmwares did you test this script?
There was an error in squashfs header in 4.0.5-4.0.6 FW (including test releases)- androidmerged.squashfs.secure could be mounted as loop but not extracted

Hi,
I builded my image based on the current 4.0.7 aos-update file.
I'm using archlinux 64 bit.
Which arch are you using? Can you please verify that the correct extractAOS binaries are downloaded within the script?
The script doesn't mount the androidmerged.squashfs.secure as loop device, but copies all the data from androidmerged.squashfs to a temporary folder named "output_folder".
Can you please provide a console output? Maybe there is some more information?...

Quallenauge said:
Hi,
I builded my image based on the current 4.0.7 aos-update file.
I'm using archlinux 64 bit.
Which arch are you using? Can you please verify that the correct extractAOS binaries are downloaded within the script?
The script doesn't mount the androidmerged.squashfs.secure as loop device, but copies all the data from androidmerged.squashfs to a temporary folder named "output_folder".
Can you please provide a console output? Maybe there is some more information?...
Click to expand...
Click to collapse
I didn't test the script (I stick to 3.2.80).
For modifying I use LeTamas' "manual" method- correct binaries are present (linux 32bit). Unpacking .aos file works fine but I had problems with unsquashfs (header error in =<4.0.6 fw) so the only option was mount -o loop.
If it works for 4.0.7= Archos corrected the error

Hi!
I've just downloaded the 4.0.6 version from archos servers.
Code:
h**p:// update.archos.com/9/gen9/gen9_4.0.6/firmware_archos_it4.aos
Unpacking of the squashfs still works here...
Maybe you missed the needed steps:
Code:
cd $BASEPATH/firmware_archos_it4/root/data
dd if=androidmerged.squashfs.secure of=androidmerged.squashfs bs=256 skip=1
if [ -d output_folder ]; then
rm -f output_folder
fi
unsquashfs -d output_folder androidmerged.squashfs

Maybe stupid question but why we need this busybox ( this archive actually is missing)? I think there is busybox already from the archive is that archive is rooted or give us something more?

Hi,
I saw that another customized roms contains an updated busybox, which can provide more features.
(Honestly, I don't know which feature is it worth to replace the builtin busybox... . :angel
If you want to build an image without this step, just comment out the busybox call.
The busybox archive is missing, because I don't know If I have the permission to include a compiled (from other people) busybox by default.

[Dev] CM9 Mod Extension
Help!
I can't wait to try out the final build from Anybody interested in testing a CM9 super-alpha build in a week or so?, so I decided to try out a modification of the stock rom with CM9 by myself. And yes, today zygote has startet and I got a screen =)
I would like to share with you, what I did and I hope that you can give some code extensions to build a better mod script.
So, let's go:
1) Compile cyanogen mod
Install prerequisites
(I used Ubuntu Precise 32bit in a chrooted environment)
Then perform like suggested a repo init/sync:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b ics
repo sync
Then perform a compile action:
Code:
. build/envsetup.sh
lunch full_panda-eng
mka
PS: I had to modify the cyanogen_root/external/webkit/Android.mk
because there where build errors:
Code:
# Build the performance command line tool.
#include $(WEBKIT_PATH)/android/benchmark/Android.mk
Get some coffee I full build will take about an hour (on my system).
2) Unpack Archos stock image
You can use my tool at #1 of this thread!
PS: I used 407 stock image...
3) Create a loop image and mount it into a folder
You can use my script for that.
4) Get my new archive and unpack it.
Go into that folder and modify the bash script Porting.sh to match the folder paths:
Code:
export CYANOGEN=/cynogen_mod/out/target/product/panda
export STOCK=/ExtractAOS/firmware_archos_it4/root/data/output_folder/
export OUT=/Android/Development/mount
Run the script as root!
Code:
sudo ./Porting.sh
You get a file system contents in $OUT. Unmount the loop directory and
load it into the media update path as usual:
Code:
adb push archos.ext4.update /data/media/ && adb reboot
That's it! You should get a CM9 desktop.
------------ ------------ ------------ ------------ ------------ ------------ ------------ ------------ ------------
That was the good news! The bad:
The current state is a proof of concept.
I'm really hope that you can contribute to the modding script: I'm not an android expert!
Dirty technical details:
I had to use the existing vendor libraries especially the graphics drivers (I tried to use the panda binaries, with no luck :-/ ).
I moved them into the /system/vendor/lib folder and symlinked the libraries to /system/lib. This way it seems to much cleaner.
I modify the init.rc script to mount the data directory into /data2 to not interfere with existing archos installation. Later we should be able to point to that directory again. (Hint: to update the development you must use a adapted adb update command:
Code:
adb push archos.ext4.update /data2/media/ && adb reboot
From the first test, I saw that I have no real touchscreen, it worked like a "mouse" controlled environment. Maybe because the panda board has an mouse as input device.
Thanks.
PS: I'm curious how JackpotCalvin has solved the CM9 integration, It sounds way better than my solution...

Nice one
Some thoughts:
-why do you copy $STOCK/usr/bin/[binary name] when later all $STOCK/usr dir is copied?
-there should be no need to place PowerVR in /system/vendor/lib/[...], /system/lib/[...] should work fine
-check prelinks for existing libs and adjust prelink map for [repo path]/device/ (this may not be necessary, last system I compiled was Froyo)

I'm stopping my efford because I'm at a point, where I learned that just replacing the files between both sources (Panda Board CM9 builded binaries and Archos Stock ROM) is not a 100% solution.
I resolved my input devices setup, by copying the corresponding icd (and other) foles to the output folder. Then I had unresolved issues by getting WLAN to work. I found out, that in libandroid.so and libandroid_legacy.so are coded the modules which are needed for WIFI. Panda board is compiled w/o WIFI, so there are no
wifi modules loaded. (After I load wl12xx_sdio.ko manually by using insmod, the wlan was functional!).
The solution IMHO must be, to compile an adapted CM9 with all hardware specific settings. Maybe the customized files can also moved inside the device configuration directory so that the merge script is obsolete (my hope).
So I decided to either to wait until JackpotClavin is posting his CM9 configuration files
Code:
http://forum.xda-developers.com/showpost.php?p=28439197&postcount=80
or to learn how to make a new device on CM which maches our Archos device. (Maybe someone else can give me some archos specific instructions).
Update: Great! JackpoClavin has provided sources =)

[Installer] SMACKME 2.1 (kexec or moboot, native Linux or Android - with recovery!)

SmackMe 2.1 Installer
Read the whole post before doing anything.
Sorry this has been so long in the making. It underwent several rewrites and design changes.
SmackMe now supports recovery - individual recoveries will be installed along with kexec kernels - don't worry about the graphical corruption.
Supported Android Files:
Android 2.2: Froyo-*.zip|froyo-*.zip
Android 2.3 / CM7.1: update-cm-7*.zip|update-cm7*.zip|cm-7*.zip
Android 4.0 / CM9: update-cm-9*.zip|cm-9*.zip|update-cm9*.zip
Android 4.1 / CM10: cm-10*.zip|update-cm-10*.zip|update-cm10*.zip
Android 4.2: Evervolv-*.zip|evervolv-*.zip
Google Apps for Android: gapps-*.zip
Supported native-Linux Files:
Ubuntu: TouchPadBuntuRootfs*.tar.gz|TouchPadBuntuRootfs*.tgz
Split Ubuntu: TouchPadBuntuRootfs1210*.tar.gz.[123]|TouchPadBuntuRootfs1210*.tgz.[123]
Arch Linux ARM (untested but should work): ArchLinuxARM-touchpad*.tar.gz|ArchLinuxARM-touchpad*.tgz
Split Arch Linux: ArchLinuxARM-touchpad*.tar.gz.[1-4]|ArchLinuxARM-touchpad*.tgz.[1-4]
Debian (which fell off the face of the Earth, apparently, so also might not work): bodhi-touchpad-*.tar.gz|bodhi-touchpad-*.tgz
Split Debian: bodhi-touchpad-*.tar.gz.[123]|bodhi-touchpad-*.tgz.[123]
Fedora (ported by me, will release this month): HPTPFedora*.tar.gz|HPTPFedora*.tar.gz
Split Fedora: HPTPFedora*.tar.gz.[123]|HPTPFedora*.tar.gz.[123]
Slackware (ported by me): HPTPSlackware*.tar.gz|HPTPSlackware*.tar.gz
Split Slackware: HPTPSlackware*.tar.gz.[123]|HPTPSlackware*.tar.gz.[123]
Supported Miscellaneous Files:
uImage files: uImage.*
kexec kernel tarchives: kexec-*.tar
moboot (0.3.5, 0.3.8 tested only): moboot*.zip
You will need:
Computer with the HP webOS SDK installed, including Novacom and Novaterm.
A TouchPad (which I will refer to as HPTP)
All your files to install.
Patience. An install of the whole shebang on my 32GB test unit took almost 40 minutes.
Instructions for use:
Create a directory in the USB storage of your HPTP with the name "sminstall".
Copy all the files you want to install from your PC (refer to the lists above) into that directory.
Boot your HPTP into recovery mode.
Run the following command in your Terminal or Command Prompt:
Code:
novacom boot mem:// < uImage.SmackMe2
You should see the USB logo get replaced by the HP logo, then two Tuxes (Linux's mascot, the penguin - one for each CPU coer on the SoC) and scrolling text. Wait for the tablet to reboot to moboot. If you encounter any issues, please remember that I AM NOT RESPONSIBLE FOR YOUR ACTIONS, but I will certainly do my utmost to fix anything that I made. It is unlikely to brick your TouchPad using either this installer or ACME Installer. The worst that can theoretically happen is the "www.palm.com/ROM" screen, which IS NOT a brick, and IS EASILY FIXABLE.
DOWNLOADS
The main installer (what you feed into Novacom):
uImage.SmackMe2 - https://docs.google.com/file/d/0B4WUjKii92l2T1k5THhKNmNPVEk/edit?usp=sharing
Buiidables for the main installer: http://www.mediafire.com/?it96af7fvp39l9c
To use kexec for any OS, you need both "uImage.kexec" and the "kexec-<OSNAME>.tar" files.
MAIN FILE (uImage.kexec): https://docs.google.com/file/d/0B4WUjKii92l2RHJoNE93c2dVRlU/edit?usp=sharing
Android 2.2: https://docs.google.com/file/d/0B4WUjKii92l2d2cwQlBtVVd4aGM/edit?usp=sharing
Android 2.3: https://docs.google.com/file/d/0B4WUjKii92l2UGtETzBwNnNvckU/edit?usp=sharing
Android 4.0: https://docs.google.com/file/d/0B4WUjKii92l2UDc2cVZ2TjBWM2s/edit?usp=sharing
Android 4.1: https://docs.google.com/file/d/0B4WUjKii92l2d3g0U3p6c0l4NFk/edit?usp=sharing
Android 4.2: https://docs.google.com/file/d/0B4WUjKii92l2dlFzcFBacThSVXc/edit?usp=sharing
Ubuntu 12.10 final: http://www.mediafire.com/?uowhfd1sx1pppoa
Ubuntu 13.04: kexec kernel already included in the rootfs, DO NOT try to extract the 12.10 one on top!
Arch Linux: coming soon
Slackware: http://www.mediafire.com/?8kow2lrwnamuui1
Fedora: coming soon

dude amazing work really love to get all of this working
:crying:
Arch Linux: coming soon
Slackware: coming soon
Fedora: coming soon

netkillercat said:
:crying:
Arch Linux: coming soon
Slackware: coming soon
Fedora: coming soon
Click to expand...
Click to collapse
Detailed status:
Arch Linux should be easy once I fit the (LZMA'd) kernel+ramdisk under the 4MB limit.
Slackware is practically done-de-done-done but I have to remove some personal settings and make X launch by default.
Fedora is the farthest back, I haven't even yet compiled ts_srv for it.

So this installer creates the kexec<OS>files.tar from the roms that you supply it? Or are you simply stuck with the ones you provided?

sounds great man i have 32gig tp for testing let me know
castrwilliam;37601915]Detailed status:
Arch Linux should be easy once I fit the (LZMA'd) kernel+ramdisk under the 4MB limit.
Slackware is practically done-de-done-done but I have to remove some personal settings and make X launch by default.
Fedora is the farthest back, I haven't even yet compiled ts_srv for it.

The kexec-<OS> files are documented inside the ramdisk on the init script, I forgot to copy that documentation here. Nothing really strange has to be done to make them, but since it requires the might of a desktop PC to compile the kernel, I thought it'd be good to include the ones I've made so far.
(from /etc/scripts/kernel.sh of the ramdisk of SmackMe)
# install_kexec:
# $1: kexec tarchive
#
# these tarchives are always uncompressed and contain the following files:
# vmlinuz-<name> = the zImage to boot
# initrd.img-<name> = the initrd to boot
# boot.cfg = kexecboot boot.cfg file.
# smackme.cfg = installation parameters:
# - ROOTDEV=/dev/store/<lvname> the root device to install this on.
Click to expand...
Click to collapse
Basically, you need to recompile the (2.6.35 only) kernel with the patch from my kexec post, and use the zImage (NOT THE uImage) as vmlinuz-whatever. Then, you need to extract the old uImage from the same OS with uimage-extract from the moboot distribution. Use the "ramdisk.img" that is created in your current directory as "initrd.img-<name.>
Then, create a kexecboot config file of the form:
Code:
LABEL=<what shows up on the boot menu>
KERNEL=<what you named the kernel>
INITRD=<what you named the initrd>
APPEND=root=/dev/ram0
and save it as "boot.cfg".
Lastly, make a one-line smackme config file named smackme.cfg. ROOTDEV depends on what LVM volume you want SmackMe to store the kernel on. List:
Android 2.2: /dev/store/android22-system
Android 2.3: /dev/store/android23-system
Android 4.0: /dev/store/android40-system
Android 4.1: /dev/store/android41-system
Android 4.2*: /dev/store/android42-system
Ubuntu: /dev/store/ubuntu-root
Slackware*: /dev/store/slackware-root
Fedora*: /dev/store/fedora-root
Arch*: /dev/store/arch-root
Debian*: /dev/store/debian-root (or possibly bodhi-root, idk)
* means the tarchive for that OS hasn't been posted on my first post yet.
Lastly, put the four files (vmlinuz, initrd, boot.cfg and smackme.cfg) in an empty folder and do:
tar -czf ../kexec-<name>.tar *
Move it to the sminstall dir on the HPTP and run SmackMe to test.
Summary (ubuntu 12.10 host AND guest with the CodeSourcery toolchain in $PATH used as an example):
Code:
#setup
mkdir work
mv <PATH_TO_KEXEC_PATCH> work
mv <NORMAL_UBUNTU_KERNEL_UIMAGE> work
cd work
# compile kernel
git clone git://github.com/BodenM/ubuntu-kernel-tenderloin
cd ubuntu-kernel-tenderloin
patch -p2 < ../decomp-copy-atags.diff
export ARCH=arm
export CC=arm-eabi-gcc
make tenderloin_defconfig
make -j8 zImage
cd .
# extract ramdisk
git clone git://github.com/jcsullins/moboot
cd moboot/tools
gcc -lz -o uimage-extract uimage-extract.c
cd ../..
uimage-extract uImage.Ubuntu
#make boot.cfg file
echo 'LABEL=Ubuntu 12.10 final' > boot.cfg
echo 'KERNEL=vmlinuz-2.6.35-ubuntu' >> boot.cfg
echo 'INITRD=initrd.img-2.6.35-ubuntu' >> boot.cfg
echo 'APPEND=root=/dev/ram0' >> boot.cfg
#make smackme.cfg file
echo 'ROOTDEV=/dev/store/ubuntu-root' > smackme.cfg
#generate kexec tarchive
mkdir kexec
mv hp-kernel-tenderloin-ubuntu/arch/arm/boot/zImage kexec/vmlinuz-2.6.35-ubuntu
mv ramdisk.img kexec/initrd.img-2.6.35-ubuntu
mv *.cfg kexec/
cd kexec
tar -czf ../kexec-ubuntu.tar *
BTW, the kexec package is only half the story, you still need to copy the rootfs tarfile (native) or zip file and gapps (Android).

It worked but....when I get to Kexecboot I can't select anything? The up/down vol key works but the home button will not....
n/m....figured it out its the power button instead of home..... working good!

Re: [Installer] SMACKME 2.0 (kexec or moboot, native Linux or Android)
Does your version of Ubuntu contain the same bugs as the Ubuntu already posted in the forums?, and if I may ask what bugs are in your other Linux ports?
Sent from my Nexus 10 using xda app-developers app

My version of Ubuntu has audio and usability enhancements, as well as being lean/mean and faster due to the armhf architecture.
It's available near the end of the Ubuntu thread, make sure you get 12.10, "Final" and not "Beta".
In fact, I haven't tested my Ubuntu kexec tarchive with anyone else's implementation. Feel free to try and respond back with 11.10 or 12.04, or even my 12.10 beta.
Everyone, Slackware should be up by the time you read this post.

Little help please just in case is this right
just to make it clear for us dummies out here
novacom boot mem:// < uImage.SmackMe2 thats it right?

Re: [Installer] SMACKME 2.0 (kexec or moboot, native Linux or Android)
Hey castrwilliam nice job
I have a question. I already have cm10 and webos installed and want to get ubuntu 12.10. But i always had a problem with kernel panic error. So i came across your recent post. Can i just follow your instructins for ubuntu or do i have to install the rest too? I already have the moboot installed. Thanks for your response
sent from my hp touchpad 32gb dual boot CM10

just in case Waiting for some help
:silly::silly::silly::silly:

netkillercat
This is how I did it and it worked just fine:
In my sminstall folder on the TP I had: moboot_0.3.5.zip, uImage.kexec, kexec-ubuntu.tar, and TouchPadBuntuRootfs1210v2.tar.gz.
I ran novacom boot mem:// < uImage.SmackMe2, and let it run. Took probably 15 mins at least.
Rebooted, chose kexec, chose Ubuntu, all working ok....

i did move kexec and ubunt uimage to boot
viper3two said:
netkillercat
This is how I did it and it worked just fine:
In my sminstall folder on the TP I had: moboot_0.3.5.zip, uImage.kexec, kexec-ubuntu.tar, and TouchPadBuntuRootfs1210v2.tar.gz.
I ran novacom boot mem:// < uImage.SmackMe2, and let it run. Took probably 15 mins at least.
Rebooted, chose kexec, chose Ubuntu, all working ok....
Click to expand...
Click to collapse
thank you for you for answer

You're adding files that aren't concatenated yet. (hence the .1, .2. and .3 extensions.) This is what you need to do. I'm assuming you're going to be doing this on the same, Windows computer...
Code:
copy TouchPadBuntuRootfs1210v2.tar.gz.1+TouchPadBuntuRootfs1210v2.tar.gz.2+TouchPadBuntuRootfs1210v2.tar.gz.3 TouchPadBuntuRootfs1210v2.tar.gz
copy HPTPSlackware14test1.tar.gz.1+HPTPSlackware14test1.tar.gz.2+HPTPSlackware14test1.tar.gz.3 HPTPSlackware14test1.tar.gz
Transfer the HPTPSlackware14test1.tar.gz and TouchPadBuntuRootfs1210v2.tar.gz files to the TouchPad's sminstall folder, and delete the .1, .2, and .3 files.
Re-run SmackMe. You shouldn't need to redoctor your TP, assuming you didn't create any cm-* LVMs (e.g. by running normal ACME).
By the way, a few hints about my installer:
It saves a log in the sminstall folder if you want to find out what went right or wrong
It NEVER deletes original installation files. It will move them to either "invalid" or "finished" under the sminstall folder, and after you are satisfied with your installation, you can delete them.
It will soon be updated with support for concatenating archives during installation (which would make it work when you put in the .1,.2,.3 files.
I will also add recovery kernels to the kexec packages, and once I have the method for modding them, I will document it. It is likely to be more involved than what can be done by the installer itself, but if it isn't, I will add hotpatch support for uImage recoveries like it does with Android normal uImages.

roger that i see lol
castrwilliam said:
You're adding files that aren't concatenated yet. (hence the .1, .2. and .3 extensions.) This is what you need to do. I'm assuming you're going to be doing this on the same, Windows computer...
Code:
copy TouchPadBuntuRootfs1210v2.tar.gz.1+TouchPadBuntuRootfs1210v2.tar.gz.2+TouchPadBuntuRootfs1210v2.tar.gz.3 TouchPadBuntuRootfs1210v2.tar.gz
copy HPTPSlackware14test1.tar.gz.1+HPTPSlackware14test1.tar.gz.2+HPTPSlackware14test1.tar.gz.3 HPTPSlackware14test1.tar.gz
Transfer the HPTPSlackware14test1.tar.gz and TouchPadBuntuRootfs1210v2.tar.gz files to the TouchPad's sminstall folder, and delete the .1, .2, and .3 files.
Re-run SmackMe. You shouldn't need to redoctor your TP, assuming you didn't create any cm-* LVMs (e.g. by running normal ACME).
By the way, a few hints about my installer:
It saves a log in the sminstall folder if you want to find out what went right or wrong
It NEVER deletes original installation files. It will move them to either "invalid" or "finished" under the sminstall folder, and after you are satisfied with your installation, you can delete them.
It will soon be updated with support for concatenating archives during installation (which would make it work when you put in the .1,.2,.3 files.
I will also add recovery kernels to the kexec packages, and once I have the method for modding them, I will document it. It is likely to be more involved than what can be done by the installer itself, but if it isn't, I will add hotpatch support for uImage recoveries like it does with Android normal uImages.
Click to expand...
Click to collapse
thank you for all your work and your patient with dummies like me asking duh questions lol
well i tried again and got slack installed did not install but it did take up space and i see cm9 in moboot wont boot
cm10 dos not show up in moboot and ubuntu dont show in kexec menu
so thats it after runing it several time all i got was moboot kexce and slack on kexce menu

i get this when i want to use novacom /bin/sh: can't open uImage.SmackMe2: no such file

dam it
got ubuntu and slack installed android is on moboot but wont boot still happy to have slack and ubuntu working kexec is working now for me but no android
i did a lvm lvscan and i see it did not make partitions for android so i guess no harm was done
i removed android from boot folder
ACTIVE '/dev/store/root' [568.00 MB] inherit
ACTIVE '/dev/store/var' [64.00 MB] inherit
ACTIVE '/dev/store/update' [16.00 MB] inherit
ACTIVE '/dev/store/log' [24.00 MB] inherit
ACTIVE '/dev/store/mojodb' [256.00 MB] inherit
ACTIVE '/dev/store/filecache' [136.00 MB] inherit
ACTIVE '/dev/store/media' [22.52 GB] inherit
ACTIVE '/dev/store/swap' [512.00 MB] inherit
ACTIVE '/dev/store/slackware-root' [2.00 GB] inherit
ACTIVE '/dev/store/ubuntu-root' [3.00 GB] inherit

now that i have ubuntu and slack
im good till a get back to a pc
so ubuntu and slack are installed and working

alex1301 said:
i get this when i want to use novacom /bin/sh: can't open uImage.SmackMe2: no such file
Click to expand...
Click to collapse
You need to copy uImage.SmackMe2 to the locations of your novacom driver installation.

[GUIDE]BackTrack 5 Chroot (Backtop2)

[Project dormant unless someone else picks it up]
NOTE: This is a chroot for the Webtop, not the Android+VNC chroot method.
Hi everyone, this is my first guide (I'm not sure I can call it that yet, or if this is in the right section) so bear with me.
I tried the Debian chroot guide (http://forum.xda-developers.com/showthread.php?t=1093790), and I really liked the idea, but I had too many apt-get issues and it often crashed my Webtop, so I tried building my own Ubuntu Lucid chroot using rootstock, but internet didn't work.
I later saw this: http://forum.xda-developers.com/showthread.php?t=1184161, but the links were dead and the scripts it referenced were out of date. I'll sort of combine the two guides here since Backtrack actually works surprisingly well.
Just on a side note though, I haven't fully tested the Backtrack tools, but the only thing I haven't found to work are the wireless tools.
Let's start!
Required:
-Rooted Atrix (with Blur based ROM)
-LXTerminal installed on Webtop
-Enough free space (around 4 GB just for room)
-7-Zip
-Some Linux/Unix distro native or in a VM
1. Install the easy-signed.zip from the Debian chroot guide:
http://forum.xda-developers.com/showthread.php?t=1093790
but the other files aren't needed.
Make a folder called WebTopMOD (case-sensitive) on either external or internal memory for later.
2. Look here for reference: http://forum.xda-developers.com/showthread.php?t=1184161, but the links are dead. Active links are here:
Part 1: http://www.mediafire.com/?x9cgxzdx84vc6uj
Part 2: http://www.mediafire.com/?xaoidipkg1o7vgo
Part 3: http://www.mediafire.com/?po3nznbxgvdipur
Use 7-Zip to uncompress the three files (called bt.7z.001,002,003) and you'll get a bt.img.
Full bt.img in a zip:
DL from Mega or from Google Drive
3. The image isn't usable in this state yet, since the image is formatted with ext2, and we need ext3.
Copy the image over to your Linux VM or computer on a easy-to-find directory, and open up a Terminal window (usually CTRL+ALT+T).
In Terminal, type this in:
Code:
cd <directory where you put bt.img>
mkdir tmp tmpbt
sudo mount -o loop bt.img tmpbt
dd if=/dev/zero of=linuxdisk count=0 bs=1MB seek=4096 (This is the size of the chroot image you want, in MB)
mkfs.ext3 linuxdisk (just type y when it asks)
sudo mount -o loop linuxdisk tmp
sudo cp -rf tmpbt/* tmp
sudo umount tmp
sudo umount tmpbt
[Sorry, made a mistake twice] Copy the newly made linuxdisk file to a directory named WebTopMOD on your internal memory or sdcard-ext (folder and file names are case-sensitive).
4. Start Webtop, then open LXTerminal, then start the chroot by typing in:
Code:
/usr/sbin/linux
and after it loads for a bit, you'll get an xterm window with the shell for Backtrack!
If you want to quit the Gnome session, closing xterm doesn't work, since by issuing the commands to kill the webtop processes, it also kills the webtop window manager, and if you do close it there's some kind of weird glitch with a small popup window constantly disappearing and reappearing. (It'll be a WIP for now I guess, the only full solution is to reboot your Atrix). It seems to have to do with the way the linux command mounts the chroot disk under loop50, I'll try and make something to fix this later.
-----------------Extras moved below-----------------------
Pictures:
Chromium Running
BT Desktop (Gnome)
BT Desktop with AIW
THANKS TO:
k.taylor89 for the original Backtop Method
SystemR89 for the Debian chroot and scripts to make this work
The original developers of the Backtop chroot image
And any others I may have forgotten!

Extras:
If you want a GUI (Gnome):
k.taylor89 said:
You first need to kill off all the webtop crap do this by typing the following in xterm.
"ps ax|grep awn|awk '{print $1}'|xargs kill"
"ps ax|grep panel|awk '{print $1}'|xargs kill"
Then start gnome by typing "gnome-session" in xterm.
Click to expand...
Click to collapse
If you want to take it step further and start Gnome after bootup, this isn't a full solution yet but you could edit your start-oshwt-1.sh and 2 scripts so that the chroot automatically starts on bootup without anything else in Webtop, and from there start gnome-session. I'm testing that now.
Installing Apps:
Since this is based off of Ubuntu Lucid, you can install anything from the Lucid repos, you just have to fix the sources list since the Backtrack sources don't seem to work.
Code:
sudo cp /etc/apt/sources.list /etc/apt/sources.list.old (Backup just in case)
sudo nano -w /etc/apt/sources.list
Comment out (#) any line with the backtrack servers, and uncomment any line with the Ubuntu repos.
Press Control+X, Y, then Enter, then run apt-get update to update the repos.
Apps like Chromium install and run without a hassle (just run apt-get install chromium-browser), but I actually get the error "Bus error" for some reason when Chromium remains idle, it seems to be an unsolved bug in the version of Chromium for armel devices in the Lucid repos, if anyone else has a fix, please do tell.

First.
I think its only for lapdock ..........

3n3rg1c said:
First.
I think its only for lapdock ..........
Click to expand...
Click to collapse
Oh sorry yeah I forgot to mention that. I mean I guess if you have the mod that lets you use Webtop anywhere, that'll work too.

Hi,
The "Part 3: http://www.mediafire.com/?po3nznbxgvdipu" doesn't work.
Could you fix it.
Thank you.

sintoo said:
Hi,
The "Part 3: http://www.mediafire.com/?po3nznbxgvdipu" doesn't work.
Could you fix it.
Thank you.
Click to expand...
Click to collapse
Oh sorry I copied the link incorrectly, updated in OP.

i've gotten it running on my ubuntop model, when i ran it from the terminal it would not give me any issues when closing it back up. is there a way to only launch the gnome panel? running: gnome-panel in the terminal didn't work

etruj said:
i've gotten it running on my ubuntop model, when i ran it from the terminal it would not give me any issues when closing it back up. is there a way to only launch the gnome panel? running: gnome-panel in the terminal didn't work
Click to expand...
Click to collapse
I'm not sure if there is a way to start just gnome panel because of the way the chroot is implemented, since to run gnome-panel, an X session must already be running within the chroot and I need to figure that out.

My first two times i lUnched the session the wallpaper would flicker and then just the panels would come up. Now i get hit with the errors and loop pop ups. Maybe there is a way to launch the session then kill everything but the panel?
Sent from my MB860 using xda app-developers app

etruj said:
My first two times i lUnched the session the wallpaper would flicker and then just the panels would come up. Now i get hit with the errors and loop pop ups. Maybe there is a way to launch the session then kill everything but the panel?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
The workaround I found worked so far was to modify the start-oshwt-2 script so that it would run a very slightly modified version of the script that automatically starts gnome-session (gnome-panel alone is really stubborn, still haven't figured that out) and doesn't start whatever window manager in WebTop to avoid flickering errors and panel only errors (but of course you don't have access to anything from the actual WebTop, but you could also have start-oshwt open a Terminal window from WebTop too).

Can you attach the script?
Sent from my MB860 using xda app-developers app

etruj said:
Can you attach the script?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Just rename it to linux, and copy it to wherever you like on your Atrix. You can also copy it to a directory within your terminal path.
This isn't my script, it's from the Debian chroot, just modified to automatically start gnome-session (credit to SystemR89)
You might need to chmod +x the file.
Also, if you want to start it automatically from start-oshwt-2.sh, make sure you copy the file to a directory within the terminal path, and add the line
Code:
sfalv -i "linux"
and comment out any other line that starts a different X window manager.

running "sudo gnome-panel" gives me the panel while staying inside the original ubuntop. i think i can just swap out that one line in your script to get it working. thanks! also noticed my chrome crashes after a few minutes, ill post the error code and screen grabs soon but was wondering if you ever experienced anything like it?

etruj said:
running "sudo gnome-panel" gives me the panel while staying inside the original ubuntop. i think i can just swap out that one line in your script to get it working. thanks! also noticed my chrome crashes after a few minutes, ill post the error code and screen grabs soon but was wondering if you ever experienced anything like it?
Click to expand...
Click to collapse
Yes, in fact. It's a bus error, and I tried to fix it, but the fix doesn't work (and it only seems to affect Chromium).

Sorry for bumping such an old thread, but I was wondering if anyone wanted to take this project over, since I don't have an Atrix anymore and don't have anything to work with.
Thanks.