Develop Bugs

[MOD][SOLVED] Ubuntu install on G2

Unable to install ubuntu on the G2 i get an error when i run the ubuntu.sh and bootubuntu commands , see attached . i got the files from http://nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-nexus-oneandroid/
Please help !!! Also i am running this rom ROM] (ext3-sdcard-based) - StockG2 (optional Manup456 Themed) - v1.1 - 10/14/2010 .
UPDATE I was able to get the following method to work on my root G2 running the desire z rom . http://forum.xda-developers.com/showthread.php?t=836022 .

*bump*
Id actually really like to see this able to be accomplished

I have Debian working perfectly in a chroot. I'll give Ubuntu a shot this weekend.

keenerb said:
I have Debian working perfectly in a chroot. I'll give Ubuntu a shot this weekend.
Click to expand...
Click to collapse
What steps did you follow to get debian to work ? It shout be the same process just sub out the debian image for the ubuntu image . Are you running the enomther themed rom off the sdcard? do you have the instructions in a step by step format i could try ? Thanks in advance i was able to get this running on the mytouch slide but no luck on the G2 , i think i just need an updated install.sh or ubuntu.sh script to write to the corect paths .

bled82 said:
What steps did you follow to get debian to work ? It shout be the same process just sub out the debian image for the ubuntu image . Are you running the enomther themed rom off the sdcard? do you have the instructions in a step by step format i could try ? Thanks in advance i was able to get this running on the mytouch slide but no luck on the G2 , i think i just need an updated install.sh or ubuntu.sh script to write to the corect paths .
Click to expand...
Click to collapse
My method used actual linux partitions.
http://forum.xda-developers.com/showthread.php?t=811765
It was based on my Cliq Ubuntu chroot here:
http://modmymobile.com/forums/403-m...ent/526845-successful-debian-chroot-cliq.html
The Cliq chroot guide worked perfectly except the filesystem for /system is EXT3 now instead of yaff2, and the partition numbers have changed.
mount -o rw,remount -t yaffs2 /dev/block/mtdblock1 /system
Needs to be
mount -o rw,remount -t ext3 /dev/mmcblk0p25 /system
And
mount -t ext2 -o noatime /dev/block/vold/179:2 /system/debian
Needs to be
mount -t ext2 -o noatime /dev/block/vold/179:34 /system/debian
Everything else should pretty much be identical.
You may want to substitute /data/debian for /system/debian, since /system gets wiped every reboot.
If you used the parallel SD-card based rom that enom posted the debian block device might be 179:35 or 179:36, depending on whether you added one or two partitions for that rom.

keenerb said:
My method used actual linux partitions.
http://forum.xda-developers.com/showthread.php?t=811765
It was based on my Cliq Ubuntu chroot here:
http://modmymobile.com/forums/403-m...ent/526845-successful-debian-chroot-cliq.html
The Cliq chroot guide worked perfectly except the filesystem for /system is EXT3 now instead of yaff2, and the partition numbers have changed.
mount -o rw,remount -t yaffs2 /dev/block/mtdblock1 /system
Needs to be
mount -o rw,remount -t ext3 /dev/mmcblk0p25 /system
And
mount -t ext2 -o noatime /dev/block/vold/179:2 /system/debian
Needs to be
mount -t ext2 -o noatime /dev/block/vold/179:34 /system/debian
Everything else should pretty much be identical.
You may want to substitute /data/debian for /system/debian, since /system gets wiped every reboot.
If you used the parallel SD-card based rom that enom posted the debian block device might be 179:35 or 179:36, depending on whether you added one or two partitions for that rom.
Click to expand...
Click to collapse
Cool thanks i bet the partion was what was hanging my up ill try it later and let you know

Since im running the rom of the sdcard i would need to place my img on the ext3 correct ? in which cause i guess placing it in the system folder should work then ? Just wondering if i can get it on my ext partition without running linux , they switched out my work pc and i dont have time to setup a vm right now .

Quick question.
Dont bash me please
What is the point of doing this? other then the fact of being able to do it?

keenerb said:
I have Debian working perfectly in a chroot. I'll give Ubuntu a shot this weekend.
Click to expand...
Click to collapse
Hey just wondering if you gave this a try over the weekend i was away from my pc all weekend so i did not try any thing .

Has anyone been successful in getting the n1 method to work on the g2, it doesn't look like anything propitory to the N1 is done....think ima give it a go tomorrow

i was able to get debian to natively install on my g1, being g1 is very slow compared to the processing power the g2 can give out i might give this a go and see how well it will run along side with android. if i remember correctly g1 was very slow running along side android like this hope g2 would be way much better.
native debian g1
hXXp://novaspirit.com/blog/?p=6
i will give this a go for the g2 =)
p.s. replace hxxp with http

This is as far as I got...I'm thinking its because the fs isn't ext2?
Not sure, ima try playing with the script and see what I can come up with.
Curently runin CM 6.1.0-RC2
Sent from my two cans and a peice of string.

This is what happenes with the 'updated' bootubuntu script :/
Sent from my two cans and a peice of string.

This worked for me, but a) I can't figure out how to right-click in VNC, b) it starts and runs as root, c) why is it Karmic? Is there something wrong with Ubuntu Maverick under ARM? d) can I expand the size of the .img loop-file so that I can install more stuff?
EDIT: BTW, I fixed the above problem that MrOtsKrad was having by doing "sh bootlinux" at the command line instead of just "bootlinux." Or bootubuntu, whatever it was

Is there a way to get this working natively? Booting ubuntu/debian on the G2 without booting into android first? I tried building a boot.img, but I just end up in reboot loop after the white HTC screen and I haven't been able to debug anything yet.

bdogg64 said:
Is there a way to get this working natively? Booting ubuntu/debian on the G2 without booting into android first? I tried building a boot.img, but I just end up in reboot loop after the white HTC screen and I haven't been able to debug anything yet.
Click to expand...
Click to collapse
I get the impression that is a SERIOUSLY non-trivial project, hence the reason we haven't seen (for example) MeeGo ported yet.
So, I figured out a, above: just hold the camera button while tapping. Still don't know how to not be root. Haven't tried an upgrade to Maverick yet mostly because the loopimg only has 111MB (roughly) free.

starkruzr said:
This worked for me, but a) I can't figure out how to right-click in VNC, b) it starts and runs as root, c) why is it Karmic? Is there something wrong with Ubuntu Maverick under ARM? d) can I expand the size of the .img loop-file so that I can install more stuff?
EDIT: BTW, I fixed the above problem that MrOtsKrad was having by doing "sh bootlinux" at the command line instead of just "bootlinux." Or bootubuntu, whatever it was
Click to expand...
Click to collapse
Yes you can change the img size . You can follow the instructions here that where made for the debian image on the g1 . http://www.androidfanatic.com/community-forums.html?func=view&catid=9&id=1610

Can someone post step-by-step instructions to get Ubuntu Maverick working? I tried getting Debian to work on my G1 a while ago and it always rebooted my phone.

I get nothing when I do "sh ./ubuntu.sh" (and it IS there, I checked by doing ls)
And of course if I try "sh bootubuntu" after that, I won't get results.

What rom are you trying this on ? When i did this i was on either stock or one of the very first roms . if you can provide the rom i can flash it and test and see what the issue is .

G-Slate root

There's no G-Slate forum yet, so this goes here.
How to root your T-Mobile G-Slate
This process works under Linux. The hard part under Windows would be mounting a file as an ext4 filesystem, but if you can do that you win.
You need:
The four files in the gslate_root.zip archive attached to this post.
To root:
Put those four files in a directory and open a terminal to there.
Shut down your G-Slate and plug it into your computer via USB.
Hold down both volume buttons and press the power button. The G-Slate will not appear to turn on, but it'll go into APX mode.
Running "lsusb" should show an entry "0955:7820 NVidia Corp."
Run the command "sudo su" to get a root shell. Running "ls" should still show the four files.
./nvflash --bl bootloader.bin --getpartitiontable ptable.txt
./nvflash -r --read 8 system-orig.img
Wait while 400 meg of data copies.
cp system-orig.img system.img
mkdir system
mount -o loop system.img system
cp su system/bin
chmod 4755 system/bin/su
cp Superuser.apk system/app
umount system
./nvflash -r --download 8 system.img
Wait while it copies back.
./nvflash -r --sync
Press the reset button under the sim cover to reboot.
There's your rooted G-Slate. Making that process "one click" is going to suck.
Troubleshooting:
You may need to install the package libstdc++6 or lib32stdc++6 to get nvflash to run.
You may need to use "sudo" on the nvflash commands.
If you want to try to make this work on Windows, the nvflash.exe binary and the APX USB drivers are are available from nvidia.com

This is unbelievable! Can't wait to give it a shot.

EDIT: For future reference, DO NOT use Virtual Box to try and root your device. There are issues getting the drivers to work properly. Lsusb will not work. The following methods have been tested and work:
1. Wubi install of Ubuntu Linux
2. VMware install of Ubuntu Linux
3. Dual-boot install of ""
4. Dedicated Linux box (duh)
And remember: If at first you don't succeed, try try again. Then visit our IRC channel.
Trying this on Windows 7 is gonna be a trip. Never workt with ext4 before.

Install Ubuntu and you can dual boot into Windows or Ubuntu. That's what I do.
Sent from my LG-V909 using XDA Premium App

This method is confirmed working. Thank you so much for the hard work Chandon. It wasn't very hard to complete on Linux. I can't believe my G-Slate is rooted!!!! Hell yes! Oh and the device is not wiped during the process either just to let everyone know!

Some More Help
Would it be possible to pull the recovery partition off now?
Why I ask. I am in a bit of a pickle. My slate will get to the first LG boot screen and then freeze. It does not even go to the boot animation. I can still get into fastboot and APX mode and it is seen by my computer.
How did i get here. While poking around in fastboot I am pretty sure i wiped they recovery partition D'OH.
I was able to complete the steps listed (for root) with out issue but still cannot get past the boot screen since this is only modifying the system partition.
I am thinking that if that could be pulled from the device i could flash it to mine and bring my slate back to life?
Am I way off on this one?

SmellyTunic -
Attached are all the reasonably small partitions that I could pull off my device with nvflash. This should be everything except /system, /cache, and /data.
I suggest backing everything up before flashing any of these, on the off chance that there's some difference between devices.

Thanks so much for this! Is there a good linux live cd(or bootable usb flash drive) someone could suggest where this could be accomplished easily? Not ready to take the plunge actually installing linux on my system yet >.>

Here you go
shinkinrui
Info and steps can be found here http://www.ubuntu.com/download
Pretty easy to set up a dual boot machine.
Chandon,
Any chance you know off hand which one of those partitions is the recovery?

I suggest doing a Wubi install [1], where Ubuntu pretends to be a Windows app (which you can then uninstall like any other app later). Alternatively you could try using VirtualBox [2], but that's less guaranteed to work.
The only reason I wouldn't do this with a Live CD is that you'd risk losing your backup of the stock /system partition when you reboot. It would also make losing power in the middle of the flash really annoying.
[1] https://wiki.ubuntu.com/WubiGuide
[2] (edit: virtual box doesn't easily see the USB device)

Thanks guys, reading about that Wubi solution looks like the simplest way to have a dual-boot system. I like it! I'll be getting my root on later tonight

i prefer Ubuntu just cause you can install it in windows then simply restart and boot into Linux or Windows. This way you don't need to worry about not having Linux again.

SmellyTunic said:
Any chance you know off hand which one of those partitions is the recovery?
Click to expand...
Click to collapse
I'm sure that /system is 8 and the kernel is 13, but don't know about anything else. You might be able to figure it out by reading the ptable.txt file generated by the --getpartitiontable command - it's pretty clear except for the part where it uses 3 letter partition names.

Thanks. I will take a look when i get home from work.
Sent from my GT-I9000 using XDA App

While we are on the topic of development, we really need a forum over here at XDA for the G-Slate!

deez1234 said:
While we are on the topic of development, we really need a forum over here at XDA for the G-Slate!
Click to expand...
Click to collapse
I definitely concur.

thengkiu so much
works like a charm

I have no idea why I'd ever need/want to root my G Slate, I'm fairly simple in my desires for my device - but I have to say I'm delighted to see it is possible and am ever so grateful for folks who figure this stuff out because it keeps moving G Slate towards legitimacy.
Thank you!!

The hard part under Windows would be mounting a file as an ext4 filesystem, but if you can do that you win.
Click to expand...
Click to collapse
No kidding. Since the linux method failed miserably for me, I've decided to press forward with trying to do it on Windows. Problem is, I have yet to find any way to mount an ext4 filesystem on Windows. There are several options out there that will allow you to read ext4 filesystems on Windows, but not write. Any suggestions?

my friend will be happy to see that this is possible.

[N2E] Nook 2nd Edition Touch - Development

Until we get a dedicated forum, at that time this thread can be moved, we can talk about development and progress aside from rooting. I'll start off with remapping the buttons on the front of the device.
In DOS you can pull the keyboard map file below
Code:
adb pull /system/usr/keylayout/TWL4030_Keypad.kl
Once pulled you can edit it in a program like Notepad++ and edit the following lines
Code:
key 407 RIGHT_NEXTPAGE
key 412 LEFT_NEXTPAGE
key 139 LEFT_PREVPAGE
key 158 RIGHT_PREVPAGE
You can change LEFT_NEXTPAGE to MENU and LEFT_PREVPAGE to BACK and now you have hard mapped Menu and Back buttons. I have ordered my own nook I've just been messing with a co-workers so I haven't found the Power button or "n" button mappings if they are in fact in the file.
Finally you can push the file back to the nook
Code:
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb push TWL4030_Keypad.kl /system/usr/keylayout/
adb shell chmod 644 /system/usr/keylayout/TWL4030_Keypad.kl
zonyl said:
I've locked it up before when trying to boot nookie. Called tech support and they told me that holding down power button more than 20 secs, does a hardware reboot. Works.
Click to expand...
Click to collapse

elmonica said:
I installed the Android app store, but I am receiving the following error message:
"For security your phone is set to block installation of applications not sourced in Android Market"
How do I turn that off?
Thanks.
Click to expand...
Click to collapse
This will allow non-market installs [unzip sqlite3.zip]
Code:
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db "update secure set value=1 where name='install_non_market_apps';"
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
del settings.db
Also if you want to install SQLite3 to the N2E you can just push it to the device. [unzip sqlite3 (push to n2e).zip]
Code:
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb push sqlite3 /system/bin

hey, i dont own nook touch, but this should work, just as on Nook color (from video I seen):
to go BACK, you dont need to remap key, just swipe with finger from right-to-left in clock area (on nook color it was at bottom, but on nook touch it should be at top position).
post results..

xmas_spirit said:
hey, i dont own nook touch, but this should work, just as on Nook color (from video I seen):
to go BACK, you dont need to remap key, just swipe with finger from right-to-left in clock area (on nook color it was at bottom, but on nook touch it should be at top position).
post results..
Click to expand...
Click to collapse
Yes, I've been doing this.

Nook 2nd Ed. Touch --from an SD card?
(First, sorry if this isn't the perfect place to post this...so feel free to move it if there's a better place.)
Ahem...uh, well...this question comes up because I happen to work at a business that is currently selling Nooks, and we've just received the new Touch version. However, for some brilliant (<<sarcasm) reason the demo units we've received are not really demo's, they only play a little presentation that shows how what the features are, and it loops over and over. So, we're very surprised that with this new touch sensitive Nook the user really doesn't have any chance to see how it actually works. No ability to test it, read, use the touch screen..nada! Wtf??
I'm curious whether someone might be able to make a bootable copy of the Touch software that will run off a SD card? If we could at least boot off the SD card so customers could at least see how the thing really functions, then it sure would make selling them easier...and no harm done afterward
-JTT

jttraverse said:
(First, sorry if this isn't the perfect place to post this...so feel free to move it if there's a better place.)
Ahem...uh, well...this question comes up because I happen to work at a business that is currently selling Nooks, and we've just received the new Touch version. However, for some brilliant (<<sarcasm) reason the demo units we've received are not really demo's, they only play a little presentation that shows how what the features are, and it loops over and over. So, we're very surprised that with this new touch sensitive Nook the user really doesn't have any chance to see how it actually works. No ability to test it, read, use the touch screen..nada! Wtf??
I'm curious whether someone might be able to make a bootable copy of the Touch software that will run off a SD card? If we could at least boot off the SD card so customers could at least see how the thing really functions, then it sure would make selling them easier...and no harm done afterward
-JTT
Click to expand...
Click to collapse
Of course this might be possible, but considering the limitations of this device (black and white, not meant to be a tablet) this would be very hard to achieve. The first step would be finding out if the thing can boot sd cards with a custom boot image.

ikingblack said:
Of course this might be possible, but considering the limitations of this device (black and white, not meant to be a tablet) this would be very hard to achieve. The first step would be finding out if the thing can boot sd cards with a custom boot image.
Click to expand...
Click to collapse
I do not see why it couldn't boot from SD since it boots from the SD to actually root it. I see ALOT of the original Nook color mod's and scripts working on this little device since it does not deviate from the Nook color design much.

Some more resources available here, including the installation for Kindle app

What does the partition shceme look like on the Nook Touch? Is it anyway similar to Nook Color? Don't have one yet, but plan on picking one up soon.
Thanks,
Racks

ikingblack said:
Of course this might be possible, but considering the limitations of this device (black and white, not meant to be a tablet) this would be very hard to achieve. The first step would be finding out if the thing can boot sd cards with a custom boot image.
Click to expand...
Click to collapse
10 char
Sent from my BAMF Thunderbolt powered by Sense 3.0

I was hoping that mapping HOME to one of the left buttons would bring up my launcher (ADW) but instead it it brings up the same menu as the N button. Any ideas how to map a button to a launcher?
I have found that Button Savior dies a lot, which means I can't get back to the launcher.

I remap the left keys as follows:
key 412 VOLUME_DOWN
key 139 VOLUME_UP
In Kindle, I set Kindle to use volume buttons for page turning. Then I can use the hard buttons for page turning in Kindle ! This also works in other reading programs for example Aldiko, NewsRob.
Does anyone know the key code of the Nook button and the action to launch the launcher ?

aruangra said:
I remap the left keys as follows:
Does anyone know the key code of the Nook button and the action to launch the launcher ?
Click to expand...
Click to collapse
Looks to be hard coded into the framework or something.

In trying to install the gapps on my NT, I've had to restore to factory twice. I started using the instructions for the NC here:
http://nookdevs.com/NookColor:Manua...gapps_google_applications_onto_your_NookColor
Code:
adb push nc_gapps.zip /media
adb shell
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
cd /media
miniunz -x nc_gapps.zip -d /system/
echo "ro.config.nocheckin=no" >> /system/build.prop
exit
After installing the signed_youtube.apk I reboot.
Can someone who's done this post some details?

jocala said:
In trying to install the gapps on my NT, I've had to restore to factory twice. I started using the instructions for the NC here:
http://nookdevs.com/NookColor:Manua...gapps_google_applications_onto_your_NookColor
Code:
adb push nc_gapps.zip /media
adb shell
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
cd /media
miniunz -x nc_gapps.zip -d /system/
echo "ro.config.nocheckin=no" >> /system/build.prop
exit
After installing the signed_youtube.apk I reboot.
Can someone who's done this post some details?
Click to expand...
Click to collapse
I know framework.jar does not like Nook Touch. BTW how did you factory reset?

To do a factory reset reboot x 8. Interrupt each boot with a powercycle prior to the "Nook..." screen.
It's really getting tough to find things, I'm following multiple nt threads, and I could swear someone wrote about installing gapps.

remount
Below is a handy script for mounting /system I keep in my /system/xbin directory. Originally from sdx for my epic, modified for the nook touch.
Code:
#!/system/bin/sh
case $1 in
rw)
echo "Remounting /system in read/write mode"
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system ;;
ro)
echo "Remounting /system in read-only mode"
mount -o ro,remount -t ext2 /dev/block/mmcblk0p5 /system ;;
*)
echo "usage: remount rw -or- remount ro";;
esac
/system/xbin does not exist, it needs creation. I keep personal scripts there, and binaries such as busybox, bash, su, etc.

Extracting the root filesystem
These instructions assume using a linux console.
The root filesystem lives in a u-boot/PPCboot ramdisk. These instructions tell you how to extract it.
Boot your nt with the "rooted forever" sdcard while connected with usb.
Make a copy of the boot partition. After this you may reboot your nt normally.
$ tar -cf boot.tar boot/
$ tar xvf boot.tar
$ cd boot
Extract the uRamdisk file. first 64 bytes is the u-boot header, we need to skip it.
$ dd if=URamdisk bs=64 skip=1 of=ramdisk.gz
ramdisk.gz now contains the root file system.
Copy ramdisk.gz to a empty directory, then extract it:
gunzip -v ramdisk.gz
cpio -iv < ramdisk
Now the root file system has populated your work dir. Delete the file ramdisk. You can now make changes to the root file system, and using mkimage (in theory) reconstruct the uRamdisk.
That part I haven't done yet.

racks11479 said:
What does the partition shceme look like on the Nook Touch? Is it anyway similar to Nook Color? Don't have one yet, but plan on picking one up soon.
Thanks,
Racks
Click to expand...
Click to collapse
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 113.8M 0 113.8M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mmcblk0p2 15.7M 118.5K 15.6M 1% /rom
/dev/block/mmcblk0p5 278.9M 187.2M 88.8M 68% /system
/dev/block/mmcblk0p8 789.3M 80.2M 701.1M 10% /data
/dev/block/mmcblk0p7 232.4M 6.1M 223.9M 3% /cache
/dev/block//vold/179:6
236.3M 682.0K 235.6M 0% /media
/dev/block//vold/179:17
7.4G 3.1G 4.3G 42% /sdcard

dropbear & rsync
Dropbear and rsync are installed and working well on the nt. This setup allows me sync the libraries on most of my reading devices (exceptions PlayBook & iPad - walled gardens).

[SCRIPT]Debian Image Builder (01-22-2012)

Debian Image Builder...
So basically, I've been reading several different articles, etc. on running Debian and/or Ubuntu on Android. I did this on my Eris and D1 in the past, and I figured that it would work even better on the Galaxy Nexus. Of course it does... Anyway, it can be run from a loop mounted image or a separate partition on most phones. However, for phones like this one with no sdcard slot, it makes sense to just do the image thing.
After building and rebuilding an image a few times, I decided to do what I normally do and turn those crazy linux commands into a script. It's not really all that complex or fancy, but it works and can be improved. I hope you find it helpful.
NOTE: This is really just the first step in getting Debian running on your phone. This will just create the image. You still have some work to do. There are other ways to do this, but I like having control of the initial image...
1/14/2012 - fixed some typos and added 'apt' as a default package (debootstrap did this by default, but apparently multistrap doesn't)
1/16/2012 - removed multistrap and went back to debootstrap for now
1/21/2012 - added a setup script to do the second stage and updates after booting into Debian on the phone, fixed extra package install code
1/22/2012 - updated variable code per swordrune10's suggestion
Download: https://github.com/gnarlyc/DebianImageBuilder
Currently requires Debian 6, but feel free to fix that for me.
Rock on.

Thanks. I had fun with Debian on my Eris back when that was being worked on. I am sure this will be much faster on this beast.

synesthete said:
Thanks. I had fun with Debian on my Eris back when that was being worked on. I am sure this will be much faster on this beast.
Click to expand...
Click to collapse
It does, and it's pretty sweet with a bluetooth keyboard & mouse and a monitor via a MHL video cable. I've even compiled a kernel or two on it.

Where do we put the image? Do we have to create a new partition?
Sent from my Galaxy Nexus using XDA App

ttereve said:
Where do we put the image? Do we have to create a new partition?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
No, you don't have to create a partition. Here's what I do:
I use Connectbot for a terminal emulator, but there are others out there.
One time:
1) 'mkdir /data/local/debian' (don't type the single quotes)
2) copy the image to /sdcard/
Each time I start up (actually, I've made a script for this too):
1) 'su'
2) 'mount -o loop -t ext2 /sdcard/linux.img /data/local/debian'
3) 'chroot /data/local/debian /bin/bash'
4) ta-da!
You should be at a Debian bash prompt. Check /etc/apt/sources.list to make sure it's there and has 'deb http://ftp.us.debian.org/debian squeeze main'. You might also have to do 'dkpg --configure -a'. If it looks like that's needed each time, I'll automate it. If you install a desktop gui like xfce or whatever, you'll probably want to install tightvncserver in Debian and get an Android VNC client from the Market. I'll probably add more options to make these things a little easier in the future.
I'm still going through the entire process over and over until I get things how I want it, so the script will be updated as I get the time.

I'm guessing we can use ext3 (or even ext4) instead of ext2?

ttereve said:
I'm guessing we can use ext3 (or even ext4) instead of ext2?
Click to expand...
Click to collapse
I dunno. It won't hurt to try!

Is there any chance that this will work on GSM GN?
Sent from my Galaxy Nexus using xda premium

JTECJ said:
Is there any chance that this will work on GSM GN?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes. This just builds the rootfs in an image. It should work for nearly any arm based Android device. I'm still working out some kinks with getting vnc and SSH servers working though. These worked fine when I used debootstrap to create the rootfs, but multi strap is much more flexible. So, I'm going to keep trying multi strap for a bit.

alright I can get into [email protected] bash but i can't start ssh because well, there is no ssh in/etc/init.d/ how do I get it in there? (i built my own ubuntu rootfs with rootstock)?

ttereve said:
alright I can get into [email protected] bash but i can't start ssh because well, there is no ssh in/etc/init.d/ how do I get it in there? (i built my own ubuntu rootfs with rootstock)?
Click to expand...
Click to collapse
Did you install openssh-server?
EDIT: Yeah, some things aren't working quite right with installing and updating packages. I might have to re-work it with debootstrap again... Oh well.

Ok. Give me a day or two. I've re-written the script using debootstrap instead. I'll update the repo as soon as I do my initial test, which should be later tonight.

sweet I got it all to work! I'll try and get a script up for the way I did it.
btw I used a rootstock ubuntu rootfs
now I need to figure out how to setup gnome through command line!

ttereve said:
sweet I got it all to work! I'll try and get a script up for the way I did it.
btw I used a rootstock ubuntu rootfs
now I need to figure out how to setup gnome through command line!
Click to expand...
Click to collapse
Cool! I read something about rootstock, but never really looked too deep. Yeah, post your code. That would be great. I have used debootstrap before, so I know it works. The thing that I never liked is that you have to run '/debootstrap/debootstrap --second-stage' after you boot into Debian on the phone. With multistrap, the packages are supposed to all be there and ready to go. (At least, that's how I understand it.) Anyway, I'm working out debootstrap again, and will just do a one-shot startup script or something. Or maybe, I'll switch gears and do it your way instead...

from: http://androlinux.com/android-ubuntu-development/how-to-build-chroot-arm-ubuntu-images-for-android/
build rootfs
Code:
sudo rootstock \
--fqdn ubuntu \
--login ubuntu \
--password ubuntu \
--imagesize 4G \
--seed linux-image-omap,build-essential,ssh,tightvnc
then make an image:
Code:
dd if=/dev/zero of=ubuntu.img bs=1MB count=0 seek=4096
format as ext4
Code:
mkfs.ext4 -F ubuntu.img
mount empty image
Code:
sudo mount -o loop ubuntu.img /mnt
extract rootfs inot image
Code:
sudo tar -C /mnt -zxf armel-rootfs-datetag.tgz
and unmount
Code:
sudo umount /mnt
this is my script to get chroot working (but this script fails and idk why so any help would be appreciated) (modified from the script http://burningbroccoli.se/post/949205350/chrootd-ubuntu-on-samsung-galaxy-s-android):
Code:
#!/bin/sh
echo "mount the image"
mount -o loop -t ext4 /sdcard/ubuntu.img /data/local/ubuntu
echo 'Mounting proc,sys and dev'
busybox mount -t proc proc /data/local/ubuntu/proc
busybox mount --bind /sys /data/local/ubuntu/sys
busybox mount --bind /dev /data/local/ubuntu/dev
echo 'Exporting a proper path'
export PATH=/bin:/usr/bin:/sbin:/usr/sbin:$PATH
echo 'Chrooting and starting ssh server'
chroot /data/local/ubuntu /bin/bash
echo "And your ip is:"
busybox ifconfig | busybox grep "inet addr"

I looked at rootstock. It doesn't appear to be Debian friendly, but maybe I'm just missing something. As soon as I'm happy with this on Debian, I'll look into making it work on Ubuntu also. I also realized that debootstrap has an option to install extra packages, so that's cool.
Right now, this is working well for me, but there are things that I would like to add.

ran into a problem, apparently it doesnt know let so it pretty much didnt work..
Code:
./debianImageBuilder.sh: 20: let: not found
running oneiric and the UI is gnome3
---------- Post added at 04:53 PM ---------- Previous post was at 04:37 PM ----------
nvm, i got it to work by modifying it to this.. u can do whatever to the code, im just happy to help... tho im not sure why let doesnt work for me x.x
Code:
export image_name=debian.img
export build_folder=image_folder
real_image_size=$(6442450944)
echo "******************************"
echo "Installing dependencies"
echo "******************************"
apt-get install debootstrap
echo "******************************"
echo "Gather info"
echo "******************************"
echo -n "What size image would you like to create? (in GBs): "
read image_size
real_image_size=$(((($image_size * 1024) * 1024) * 1024))

swordrune10 said:
ran into a problem, apparently it doesnt know let so it pretty much didnt work..
Code:
./debianImageBuilder.sh: 20: let: not found
running oneiric and the UI is gnome3
---------- Post added at 04:53 PM ---------- Previous post was at 04:37 PM ----------
nvm, i got it to work by modifying it to this.. u can do whatever to the code, im just happy to help... tho im not sure why let doesnt work for me x.x
Code:
export image_name=debian.img
export build_folder=image_folder
real_image_size=$(6442450944)
echo "******************************"
echo "Installing dependencies"
echo "******************************"
apt-get install debootstrap
echo "******************************"
echo "Gather info"
echo "******************************"
echo -n "What size image would you like to create? (in GBs): "
read image_size
real_image_size=$(((($image_size * 1024) * 1024) * 1024))
Click to expand...
Click to collapse
Cool. That does look a bit cleaner. The code for installing extra packages wasn't right/all there, so I'm working on that now.

Thanks for this script. It worked perfectly for me. It's great to be able to apt-get things on my phone, and it's interesting to run debian's utilities on Android. A lot of other methods are about getting some sort of Linux desktop on Android, but I really appreciate the barebones CLI that this provides. To my knowledge this is the only way to be able to run ping6 on Android.
To anyone thinking of setting this up - make sure to install busybox!
I made a couple of helper scripts to get cleanly in and out of the chroot, and to make the sdcard directory available within debian. I'm keeping this stuff stored in /sdcard/debian:
Code:
[email protected]:/sdcard/debian # ls
debian.img
debroot
start.sh
stop.sh
start.sh
Code:
mount -o loop -t ext2 debian.img debroot
busybox mount --bind /sdcard debroot/mnt
chroot debroot /bin/bash
stop.sh
Code:
umount /mnt/sdcard/debian/debroot/mnt
umount /mnt/sdcard/debian/debroot/dev/pts
umount /mnt/sdcard/debian/debroot/proc
umount /mnt/sdcard/debian/debroot/sys
umount /mnt/sdcard/debian/debroot

[Tip] Mounting swapfile from init.d

After some experimentation, I finally figured out how to mount a swapfile from init.d
But first! A disclaimer!
STANDARD DISCLAIMER: I am TOTALLY not reponsible if you brick your own phone. This procedure is provided 'as-is', with no guarantee of non-damage, or functionality.
I *do* use this script, and it's working as I expected, but YMMV.
Now, on with the Tip...
SAFETY PRECAUTION
Install (flash) the TWRP recovery first. If all goes well, you can flash your favorite recovery back.
PREREQUISITE
You need:
A rooted phone (of course!)
.
A kernel that supports swapfiles
.
A busybox that provides the following applets: nohup, basename, dirname, renice
The latest busybox by @stericson happens to provide all needed applets.
.
A working init.d infrastructure
PROCEDURE
Make sure that the directory /data/scripts exists (create one if it doesn't)
Create a swapfile by running the following commands from within Terminal (change "64" to the size (in MiB) of the swapfile you want):
Code:
su
TARG=/sdcard/.swapfile
dd if=/dev/zero of=$TARG bs=$((1024*1024)) count=64
mkswap $TARG
echo "SWAPFILE=$TARG" > /data/scripts/wait-mount-swap.conf
Download the attached script, rename it to "wait-mount-swap.sh"
Copy the script to the /data/scripts folder
Run the following commands from within Terminal:
Code:
su
WMS=/data/scripts/wait-mount-swap.sh
FIL=/system/etc/init.d/99swap
chmod 0777 $WMS
mount -o remount,rw /system
echo "#!/bin/bash
nohup $WMS &
" > $FIL
chmod 0755 $FIL
WARNING: Unless you know exactly what you're doing, you must follow the above code *exactly*!! DO NOT add spaces to 'make it easier to read'; DO NOT forget to enter the whole line (including that ampersand '&' symbol).
Reboot
Wait up to 1.5 minutes
Check the /data/scripts/wait-mount-swap.log; the last line should declare "..successful!"
Check using the 'free' command from Terminal
Got Stuck in BootLoop?
Power off your phone, then boot into TWRP recovery.
Tap "Mount".
Check (X) "Mount System"
Tap "Home icon"
Tap "Advanced"
Tap "File Manager"
Go to /system/etc/init.d
Tap on "99swap"
Tap "Rename File"
Append ".disabled" (that's dot-disabled), and tap Enter
Swipe to confirm
Tap "Home icon"
Tap "Reboot"
Tap "System"
--- Sent from Opera on Lenovo T420 ---

Technical Explanation
The gist of the method are two parts: The script and the nohup line. We'll begin with the latter.
If you analyze the 99swap file in /system/etc/init.d, you can see that it has only one all-important line:
Code:
nohup /path/to/script.sh &
The ampersand "&" at the end of the line means: Run this line as a background (separate) process.
The 'secret sauce' is the "nohup" command: It makes the background process stay alive even when the invoking process (i.e., the init.d script) terminates.
So, at the end of the 99swap initscript, the initscript terminates, but wait-mount-swap.sh is still running in memory.
Now, for reasons unknown, the SD Card is not mounted during init.d processing. So, the wait-mount-swap.sh script must wait until the SD Card is available before it can activate the swapfile located in the SD Card.
If you analyze the wait-mount-swap.sh script, you can see that after being invoked, the script will sleep for 30 seconds before attempting to activate the swapfile. If after the 'initial sleep' the script doesn't find the swapfile, it sleeps again for 10 seconds, and repeat the process. If after 5 attempts the swapfile still hasn't appear, it gives up and exits gracefully.
-- Sent from Opera on Lenovo T420 --

Wow! You finally did it man.
Congrats! Will try this asap. Thank you.
Sent from my GT-I8150 using xda app-developers app

pepoluan said:
Technical Explanation
The gist of the method are two parts: The script and the nohup line. We'll begin with the latter.
If you analyze the 99swap file in /system/etc/init.d, you can see that it has only one all-important line:
Code:
nohup /path/to/script.sh &
The ampersand "&" at the end of the line means: Run this line as a background (separate) process.
The 'secret sauce' is the "nohup" command: It makes the background process stay alive even when the invoking process (i.e., the init.d script) terminates.
So, at the end of the 99swap initscript, the initscript terminates, but wait-mount-swap.sh is still running in memory.
Now, for reasons unknown, the SD Card is not mounted during init.d processing. So, the wait-mount-swap.sh script must wait until the SD Card is available before it can activate the swapfile located in the SD Card.
If you analyze the wait-mount-swap.sh script, you can see that after being invoked, the script will sleep for 30 seconds before attempting to activate the swapfile. If after the 'initial sleep' the script doesn't find the swapfile, it sleeps again for 10 seconds, and repeat the process. If after 5 attempts the swapfile still hasn't appear, it gives up and exits gracefully.
-- Sent from Opera on Lenovo T420 --
Click to expand...
Click to collapse
very clever, i remember my good dos/windows days, how i wish i could do the same with linux/android
just looking and understanding your script, i feel i feel like i've gained additional 50% knowledge in linux scripting :good:
Edit: Man i have a joke for you, i mean it's not really a joke but sort of. If you decide to venture into rom development, i want to be the first person to try and test it.

Tq for tips

try your method..
Sent from my GT-I8150 using xda premium

I've figured out a way to make installation *much* easier... stay tuned for R2
Sent from my GT-I8150 using xda app-developers app

pepoluan said:
I've figured out a way to make installation *much* easier... stay tuned for R2
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
looking forward

Hello, I tried this but when I do 'chmod +x $WMS', then shel tell me 'Bad mode'. What's wrong?
Sent from my GT-I8150 with CM 10.1 by Arco using xda premium

honzin2009 said:
Hello, I tried this but when I do 'chmod +x $WMS', then shel tell me 'Bad mode'. What's wrong?
Sent from my GT-I8150 with CM 10.1 by Arco using xda premium
Click to expand...
Click to collapse
Oops, I made a mistake there. I replaced 0777 with +x post-facto.
Try entering 'chmod 0777 $WMS' instead.
The OP has now been fixed, thanks for the report
Sent from my GT-I8150 using xda app-developers app

pepoluan said:
Oops, I made a mistake there. I replaced 0777 with +x post-facto.
Try entering 'chmod 0777 $WMS' instead.
The OP has now been fixed, thanks for the report
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Thank you, script now working well but the swap file is still not mounted after boot .
I will solve it by manual mounting of swap file after each boot, as I do now.
Sent from my GT-I8150 with CM 10.1a2 by Arco using xda premium

honzin2009 said:
Thank you, script now working well but the swap file is still not mounted after boot .
I will solve it by manual mounting of swap file after each boot, as I do now.
Sent from my GT-I8150 with CM 10.1a2 by Arco using xda premium
Click to expand...
Click to collapse
Hmmm, strange.
It does take up to 30 seconds after boot for swap to be activated.
However, I will not pursue this issue anymore with the current version; I'll be releasing version 2 sometime later this week
Sent from my GT-I8150 using xda app-developers app

boot
pepoluan said:
Hmmm, strange.
It does take up to 30 seconds after boot for swap to be activated.
However, I will not pursue this issue anymore with the current version; I'll be releasing version 2 sometime later this week
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
:good:

pepoluan said:
Hmmm, strange.
It does take up to 30 seconds after boot for swap to be activated.
However, I will not pursue this issue anymore with the current version; I'll be releasing version 2 sometime later this week
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
so is the simpler version 2 out yet? cuz the current one seems slightly overwhelming for me haha!

mount -o remount,rw /system
Click to expand...
Click to collapse
on terminal emulator, this will not run becoz of the comma after remount.
it works if it busybox b4 mount like this:
busybox mount -o remount,rw /system
Click to expand...
Click to collapse
or replace the comma with a space, like this:
mount -o remount rw /system
Click to expand...
Click to collapse

Great mounting with delay
Hi everybody
too late to post in this forum?
I see last reply is of 2013
The man who invented this delayed engine did a great thing :good::good::good::good::good:
The Background is a GT-P5200 stock ROM - android 4.4.2. In less words: Samsung Galaxy Tab 3.
I tried different methods, apps and scripts, but without lucky. I tried with Rhoesoft RAMExpander Test, that told me: your device is compatible...
Not sure 100%, I tried some free apps, with the target to see confirmed that swapfile works, before spending money and discovering that the swap don't autostart at boot. The apps I tried, they created the swapfile, but at boot it was never loaded... Furthermore I don't like having one more app continuously in execution, only to drive the swapfile. So with many doubts, I tried some scripts... But one of them tolds me that my (stock) kernel hasn't swap support :crying:
I'm little stubborn, because I began my swapfile adventure, inputting commands on terminal emulator, forced to learn what does every command. And learning I had feeling that swapfile works, with the only exception of being constrained to swapon manually from the emulator.
So (stubborn) I tried other scripts, to perform this autoload on boot... but never working! I read so many things in many forums, looking for a solution, but for an inexperienced ... things too heavy to digest.
The turning point is thanks to you, @pepoluan
You must know that after every boot, if I open the terminal rapidly, the cursor becomes active after a few minutes.... about 3-4 minutes.
So maybe... if my device is slow to boot, when the SD card will be available?
The conclusion: I took the pepoluan script, and modified the swapfile lines, and initial delay: where there was 30 I put 250
it is better to wait 5 minutes, as long as they are quiet