Database Users

[guide] ubuntu on your gtab

hello. i managed to get ubuntu running on my tablet, and i thought i'd share how i did it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
note that this does not change your android setup, ubuntu will run on top of android. you will not lose any data if everything goes well.
all credit goes to user houzuoguo for his guide and the people he cites for their work. this post is based on this one.
my setup
zpad clean 3.0 with pershoots latest kernel. i don't know if it will work with other combinations, so if you try and succeed with a different system please tell me. also, if it doesn't work try using pershoot's kernel on your current rom and trying again.
when reporting success or failure, make sure to note whether you are using any of the new data2loop, data2ext, or other weird fs hacks.
what you'll need
the main ubuntu package. download with a torrent client (much preferred to save the devs bandwidth) here. if you don't know how to use torrent clients or can't for some reason, you can direct download from here.
android vnc viewer. it's on the market.
better terminal emulator, also on the market.
the attached zip file.
maybe adb, depending on your storage situation (more later.)
NO APPS ON YOUR SD CARD. just move them all to your internal storage with the built in application manager. the guide i linked above has instructions for trying to do it with apps on your sd, but i'm not even gonna bother. do it at your own risk and all that.
get to it
1. extract the attached zip. you should have a folder called "ubuntu" with three scripts (one letter filenames) inside.
2. open the ubuntu package you downloaded, go into the "linux" directory, and extract JUST "rootfs.ext2" to the "ubuntu" folder you just made.
3. rename "rootfs.ext2" to "ubuntu.img"
4. okay, decision time. you want at least 2gb free on the partition you're putting ubuntu. if you have the room on your sd card, you can just put it there with android's built in mass storage mode. if you need more room and it has to go on your internal storage, you can put it there.
if you decide to put ubuntu on external storage (i did) you need to make one small change to the "b" script in your ubuntu folder. open "b" with notepad or your favorite text editor, and change line 15 (losetup /dev/block...) to say "sdcard2" instead of "sdcard". again, this is for zpad clean. i don't know if other roms mount storage in the same way. (EDIT: looks like TNT stock and TNT Lite do, at least)
also if you decide to use external storage, the built in mass storage mode won't work to mount it. instead you can use an ftp server or adb to get your files on internal storage. i use the swiftp android app from the market and coreftp for windows to transfer files. this is very slow, so you can use "adb push file\path /sdcard2/file/path" to transfer over usb if you'd like. also, i guess, you could just pull the sdcard and throw it in a reader.
btw, if you do have adb running you can use it to do most everything below, it's handy. i'd recommend hooking a keyboard up to your tablet if not, there's a lot of typing. hint: control + d twice in adb will send it to the shell
5. ok, so now you have a directory called "ubuntu" with 4 files (u, e, b, ubuntu.img) inside. it's either on your internal flash, or on your sd card with the modified "b" file. if that sounds like you, move on.
6. because we don't have a trackball, and we need a special key for some of the stuff we're doing, you need "better terminal emulator" from the market. open the preferences and change your "Control Key" to volume down. also check "start as root" while you're in there.
7. in the terminal, type "cd /sdcard2/ubuntu" (or sdcard/ubuntu, depending on where you got it. i'm not going to differentiate again, you can figure it out)
8. now "sh u" (ignore rm -r -f errors)
9. when it tells you to, type "b" and hit enter.
10. if you see “[email protected]:/#” then you've successfully booted into a ubuntu shell. you can be done now, if you want, but most people want to see the gui, so keep going.
NOTE: always use "exit" to leave the ubuntu shell. don't just quit stuff willy-nilly. if you do quit stuff willy-nilly, open your terminal again and type "e" to clean up. you can do this a couple of times as an OCD check.
11. while in the ubuntu shell (and while connected to wifi) type "apt-get update", wait for it to finish and return a new line, then type "apt-get install tightvncserver". wait for that to finish.
12. type "cd /bin". this is where it get's really fun. now type "cat > x". this will not return a new command line, just a blank one. now type the following, hitting enter after each line, even the last one, and another one at the bottom.
Code:
rm -r -f /tmp
mkdir /tmp
chmod 777 /tmp
export USER=root
export XKL_XMODMAP_DISABLE=1
vncserver -geometry 1024x600
now press and hold volume down, and hit d. this should take you back to a new command line.
13. one more. this time do "cat > s" and enter:
Code:
export USER=root
vncserver -kill :1
vncserver -kill :2
sudo reboot
sudo halt
do volume down + d again.
14. to make those scripts executable, type "chmod 777 x" and then "chmod 777 s"
15. you're about ready. type "x" and hit enter. it will ask you for a password, which you should make, and then verify. answer "n" to the view-only password. it will only do this password stuff once, each subsequent time you run it will just do it.
16. leave the terminal app and open android-vnc-viewer. give the new connection a nickname, enter the password you just made in the terminal, choose port 5901 and use 24-bit color. hit connect.
17. in a minute you'll see ubuntu! be patient. play around when it's up, wee!
there's no sound yet, and you need to use ftp to connect to your gtab's internal storage (see bottom of post), but you get firefox! no flash.
keyboards and mice (including bluetooth HIDs) will work in ubuntu if they work in android.
some programs won't run, it's because android has stricter memory management policies than ubuntu. i'd like to get a list going of successfully run apps in ubuntu so post if you get something working.
NOTE: for some weird reason, ubuntu is using the keyboard key "d" by itself as a shortcut key, so whenever you use it it just minimizes everything. to fix this, go to the top and click (system -> preferences -> keyboard shortcuts) and look for one using "d". i think it was the very bottom one. just click the shortcut and use backspace to clear the shortcuts' function. you may have to restart your ubuntu shell for it to take.
18. to exit, hit menu -> disconnect, then in your terminal app again type "s" to stop vnc, and "exit" to leave ubuntu.
from houzuoguo in the original guide
If you have GUI running, you * MUST * type “s” (enter) to stop VNC server before you exit from Ubuntu terminal!
In case that your Android kills your Android Terminal application and you still have VNC server running, do the following steps:
a. Start Android Terminal
b. type “b” (enter) to bring back Ubuntu terminal
c. type “s” (enter) to stop VNC server
d. type “exit” (enter) to exit from Ubuntu terminal
Fail to do so you will have problem with VNC connection next time you use it.
Click to expand...
Click to collapse
from houzuoguo in the original guide
A little trick to access SD card from your Ubuntu:
1. Install “SwiFTP” from Market (freeware)
2. Set up FTP server using SwiFTP
3. In Ubuntu, “Places → Connect to Server” then:
Service type: FTP (with login)
Server: localhost
Port: (port number specified in SwiFTP, default is 2121)
Folder: /
User Name: (user name specified in SwiFTP)
Then press “Connect” and enter your password specified in SwiFTP. Now feel free to access your phone's file system!
Click to expand...
Click to collapse
19. i suspect that i'm going to have to revise this guide a lot if anyone ends up being interested, so let me know if you think i should change something.
cheers!

Ha, Good Work!
But I am expecting an full Boot to Ubuntu instead of using VNC

heeae said:
Ha, Good Work!
But I am expecting an full Boot to Ubuntu instead of using VNC
Click to expand...
Click to collapse
doesn't this thread acomplish that,
http://forum.xda-developers.com/showthread.php?t=894960

Might be a silly question but... is this a dual boot kinda thing? I've none experience with Ubuntu, but would like to.

Hi,
I have the same question as jpmi above.
Also, is this apparoach similar to this thread:
http://forum.xda-developers.com/showthread.php?t=908502
If it is, it's great that you got it working!
Having said that, I have a couple of questions, because I'd really like to do this with my Gtab:
- I know you said that you're running Zpad firmware. I'm still on stock TNT 3452, and I'd really like to get this working on stock. FYI, with stock:
/sdcard == internal SDCARD
/sdcard2 == external microSD card
Can you tell me (us) what changes in the b/e/u files need to be changed for stock?
- FYI, I had started to look into what was in that thread I linked above, and ended up borking my Gtab. However, one of the things that I noted when I was reviewing the scripts from that other implementation was that it expected to use an ext2fs for the .img, and TNT stock doesn't have the ext2fs module. I noticed that your scripts use yaff, which I think the stock TNT also uses, i.e., the big .img file is an ext2fs, and that gets mounted using a loop mount. Is that correct.
- Again, I have the same question as jpmi above. I'd really like to be able to put this ubuntu stuff JUST on the external microSD, not affecting the stock TNT stuff on the internal SDCARD (/sdcard), and be able to boot into stock TNT, start a term, and then run a (or some) command lines to bring the Gtab up in Ubuntu. Does what you describe in this thread do that?
Thanks for this, and sorry for all the questions!!
Jim

hey jim
that approach looks very similar, although it's for the nook color and wouldn't work on your gtab.
you're right, i'm going to update the OP, /sdcard points to internal and /sdcard2 to external on my ROM as well. got 'em switched. you would want to change your "b" script to use /sdcard2 and make sure that the ubuntu folder is on the external storage.
also, i'm not sure about ext2fs on TNT stock, but you can download and flash pershoots gtab kernel which will work with TNT but give you the correct support. this won't change your rom, you probably won't notice any difference at all.
the "e" and "u" scripts are all good. you don't need to mess with them.
yes, you're correct in assuming that the .img file gets mounted as a loop device. (losetup). you're also correct in saying that you will be able to boot into TNT and run ubuntu from the terminal without derailing TNT. in fact, because the ubuntu shell happens in better terminal and the gui happens in android-vnc, you can use the home button to get back into your android launcher at any time, and back into ubuntu without interrupting anything. it's pretty cool.
i hope i got you on the right track. keep in mind that this isn't my work, just adapted a teeny bit for the gtab from a guide in the nexus one forums.
good luck!

iammuze said:
hey jim
that approach looks very similar, although it's for the nook color and wouldn't work on your gtab.
you're right, i'm going to update the OP, /sdcard points to internal and /sdcard2 to external on my ROM as well. got 'em switched. you would want to change your "b" script to use /sdcard2 and make sure that the ubuntu folder is on the external storage.
also, i'm not sure about ext2fs on TNT stock, but you can download and flash pershoots gtab kernel which will work with TNT but give you the correct support. this won't change your rom, you probably won't notice any difference at all.
the "e" and "u" scripts are all good. you don't need to mess with them.
yes, you're correct in assuming that the .img file gets mounted as a loop device. (losetup). you're also correct in saying that you will be able to boot into TNT and run ubuntu from the terminal without derailing TNT. in fact, because the ubuntu shell happens in better terminal and the gui happens in android-vnc, you can use the home button to get back into your android launcher at any time, and back into ubuntu without interrupting anything. it's pretty cool.
i hope i got you on the right track. keep in mind that this isn't my work, just adapted a teeny bit for the gtab from a guide in the nexus one forums.
good luck!
Click to expand...
Click to collapse
Hi,
Thanks for the info.
The ext2fs thing is a stopper for me, as I don't want to (permanently) switch off of stock TNT yet, so the kernel thing is a kind of no-go.
At one point, I thought that it was possible to add filetype support using modules, e.g. using modprobe and the appropriate .so, but haven't figured that one one.
Another way: I think you did this with Zpad? So, I'm assuming that comes with ext2fs support? Is that via modprobe, or is it built into the Zpad kernel?
Again, thanks for the info.
Jim

Running with vnc, meaning where

Got it running, but when I type a 'd' the current app minimizes, rather useless like that

I followed your instructions to the letter but after i run "sh u" and then hit b to boot I get the following error. What did I do wrong, or is it a simple mistake?
Edit: should probably mention I am using data2loop. Might be the cause of my problems...
Type 'b' to boot Ubuntu
# b
b
SET VARIABLES
SET UP LOOP DEVICE
losetup: /dev/block/loop1
MOUNT
mount: Device or resource busy
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
SET UP NETWORK
net.ipv4.ip_forward = 1
b: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexistent
b: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexistent
b: cannot create /data/local/ubuntu/etc/hosts: directory nonexistent
ENTER UBUNTU
chroot: can't execute '/bin/bash': No such file or directory
UMOUNTING
umount <path>
umount <path>
umount <path>
umount <path>
losetup: /dev/block/loop1: Device or resource busy
Click to expand...
Click to collapse

jimcpl said:
Hi,
Thanks for the info.
The ext2fs thing is a stopper for me, as I don't want to (permanently) switch off of stock TNT yet, so the kernel thing is a kind of no-go.
At one point, I thought that it was possible to add filetype support using modules, e.g. using modprobe and the appropriate .so, but haven't figured that one one.
Another way: I think you did this with Zpad? So, I'm assuming that comes with ext2fs support? Is that via modprobe, or is it built into the Zpad kernel?
Again, thanks for the info.
Jim
Click to expand...
Click to collapse
you could technically use insmod to push the correct kernel module, but in all honesty it's probably not worth it. you'd have to do it at every boot. do you have clockworkmod recovery installed? installing a new kernel is as simple as flashing it like a rom, and going back to stock is just as easy. there's nothing permanent about any changes you make, especially because the gtab comes with root access already.
and no, i have a viewsonic gtablet, i'm just using the zpad clean rom with pershoot's kernel, which comes with the ext2fs pieces built in.
bigideasmb said:
Running with vnc, meaning where
Click to expand...
Click to collapse
i suppose with a local vnc viewer (or a forwarded port) you could run ubuntu and android simultaneously with another computer. i can't imagine why, except just to do it.
Xerion said:
Got it running, but when I type a 'd' the current app minimizes, rather useless like that
Click to expand...
Click to collapse
i had this stupid-ass problem too. it turns out that ubuntu is using "d" as a keyboard shortcut, for some reason. while in the ubuntu gui, go to (system -> preferences -> keyboard shortcuts) i think it's the very bottom one. just click it and hit backspace to clear the key, and you may have to restart your ubuntu shell to see the change, it'll stick. thanks for bringing this up, i'll throw it in the OP.
dekkon said:
I followed your instructions to the letter but after i run "sh u" and then hit b to boot I get the following error. What did I do wrong, or is it a simple mistake?
Edit: should probably mention I am using data2loop. Might be the cause of my problems...
Click to expand...
Click to collapse
like i said, i haven't tried or heard of anyone trying with data2loop, so that could be your problem. also make sure that there are no apps installed to your sd card (see "what you'll need" in the OP) and try again if there are.

i said, i haven't tried or heard of anyone trying with data2loop, so that could be your problem. also make sure that there are no apps installed to your sd card (see "what you'll need" in the OP) and try again if there are.
Click to expand...
Click to collapse
I borked something and needed to do a factory reset (no big deal) which I think should have cleared out data2loop after I reinstalled my rom (TnT Lite 4.1.0 w/pershoot's 1/12 kernel). I am however trying to run this from the internal sdcard (/sdcard/ubuntu) instead of the external /sdcard2. I still get the same error.

iammuze said:
i had this stupid-ass problem too. it turns out that ubuntu is using "d" as a keyboard shortcut, for some reason. while in the ubuntu gui, go to (system -> preferences -> keyboard shortcuts) i think it's the very bottom one. just click it and hit backspace to clear the key, and you may have to restart your ubuntu shell to see the change, it'll stick. thanks for bringing this up, i'll throw it in the OP.
Click to expand...
Click to collapse
Haha, I looked everywhere except in Ubuntu itself Thanks, now I can at least play with it a bit

I ran into an issue when trying to execute the code after step 15 (the typing "x" part) in the terminal emulator. It gives me an error saying the user variable is not defined, any ideas what's going bonkers?
Unrelated to this I had to do a data/cache wipe and after that I had no issues booting up ubuntu
my setup:
zpad 3.0
pershoot's kernel
no other hacks or updates yet

This worked very well for me so far. Thanks!!!

[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!)

Ok, so I'm going to make a little write up on how to easily install ADB and fastboot on a Mac. It's actually quite simple, and plus you don't have to worry about drivers like in Windows.
Instructions
First, make a folder named "android" (no quotes of course ) You can place it anywhere on your hard drive, it doesn't really matter. Put it somewhere you'll easily remember, because you're going to be using it a LOT. I placed mine on my desktop.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next, you'll want to download the android SDK from Here. (you won't need to install Java first like you would on a Windows PC, though I would recommend it anyway)
(As pointed out by Wlmeng11, you could skip this step just download a zip that I will have attached at the bottom of the page containing the adb and fastboot files instead of downloading the whole SDK)
When the SDK finishes downloading, Unzip it and the contents of the "android-sdk-mac_x86" folder into your android folder.
Once you have done that, open your android folder. Go into the tools folder inside of it. Double click on the file called "android" (possibly called android sdk) This file is a UNIX executable and will open within a Terminal window.
When it finishes opening, check the folder called tools. Make sure both "Android SDK Tools" and "Android SDK Platform-tools" are selected within the tools folder. Click install and wait for them to download.
When they finish downloading, go into the platform-tools folder inside your android folder, then copy adb and fastboot and paste them into the root of your android folder.
Now that you have adb and fastboot installed, we're going to want to test them to make sure they work.
Go ahead and plug in your android device at this time. Make sure android debugging is enabled in settings. Go into Settings > Apps > Developer and check it there (for Gingerbread 2.3 and lower) or go into Settings > Developer Options and check it there for Ice Cream Sandwich or Jellybean. As of now, there are two ways to access adb and fastboot.
Open a Terminal window (look in Applications > Utilities if you can't find it). Type "cd" followed by the path you saved your android folder to (I'm going to use the Desktop for this demonstration) it should look like this
Code:
cd /Users/<yourusername>/Desktop/android
Press enter.
Now you need to actually execute an adb or fastboot command. To do this, you'll need to type "./adb (or fastboot) <command>" For this tutorial, we will use "ADB devices" since it doesn't actually do anything to the phone. (we won't use fastboot since it requires rebooting to the boot loader which is different for every device)
In the same terminal window as before type the following:
Code:
./adb devices
then hit enter. It should turn up your device's serial number. If it does, proceed to the next step, if not recheck your steps, then leave a post in this thread.
(if it says * daemon not running. starting it now on port 5037 *
* daemon started successfully * that is perfectly normal)
Now, at this moment, ADB and Fastboot are both completely useable. However, it's very annoying to have to CD into the directory and use ./ in front of every terminal command. I'll show you how to add it to your path so you don't have to do any of that.
Open a new Terminal window and type
Code:
nano ~/.bash_profile
it will open a window that looks like this:
(Yours will probably be blank, because I've added a lot of stuff to mine over the years)
Add a line to it that contains the path to your android folder. (again, I'm using Desktop) It should look like this
Code:
export PATH=${PATH}:/Users/<yourusername>/Desktop/android
Once you have added that, press CTRL+X to exit, then Y to confirm the save then press enter. It will close the nano editor. You can close the Terminal window now.
Now we need to verify that it works. Open a new Terminal window and type
Code:
adb devices
If it shows the serial number, then you have set it up successfully and are good to go!
If you have any questions or issues let me know in the thread below.
If this has helped, please press thanks!
Awesome! This made the front page of XDA Thanks guys!​

Added screenshots

you won't need to install Java first like you would on a PC
Click to expand...
Click to collapse
So... Macs are Impersonal Computers?
---------- Post added at 06:24 PM ---------- Previous post was at 06:17 PM ----------
Nice guide though btw

wlmeng11 said:
So... Macs are Impersonal Computers?
---------- Post added at 06:24 PM ---------- Previous post was at 06:17 PM ----------
Nice guide though btw
Click to expand...
Click to collapse
Lol I'll fix that. Thanks btw. I'm out today, but I'll give you one tomorrow (too lazy to use my phone)

To save time, you might want to just have a adb/fastboot combo instead of the entire sdk.
(BTW it's tomorrow )
Sent from my HTC Rezound

wlmeng11 said:
To save time, you might want to just have a adb/fastboot combo instead of the entire sdk.
(BTW it's tomorrow )
Sent from my HTC Rezound
Click to expand...
Click to collapse
Maybe, I actually use other parts of the SDK . Ill look into that though

AshtonTS said:
Maybe, I actually use other parts of the SDK . Ill look into that though
Click to expand...
Click to collapse
Well since this guide is primarily aimed towards users who only want to root their phone, rather than developers, adb/fastboot is really all you need.
So it would save time to just use an adb/fastboot combo.

I still prefer linux
I still prefer the linux enviroment, although its handy to have the adb on my macbook for when I'm not at home and have bricked my device :S
I had already got this setup, I just didn't know the ~/.bash_profile bit Now I know had to add my own programs as actual programs and not just aliases XD

First off, nice guide. I am still trying to understand why you've moved adb and fastboot from platform-tools, rather than export the path to that directory. Is there any particular reason?
EDIT: BTW, you've hit the front page on XDA.

Hi.
Would it be valid on a very old Powerbook Pismo running 10.4 Tiger??
Thanks in advance and regards.

wlmeng11 said:
Well since this guide is primarily aimed towards users who only want to root their phone, rather than developers, adb/fastboot is really all you need.
So it would save time to just use an adb/fastboot combo.
Click to expand...
Click to collapse
Indeed, though this method allows you to update your adb and fastboot via Android SDK Manager (ASM). Also, in cases where all you need is adb and fastboot, you can speed up future update checks by going to "Tools"->"Manage Add-on Sites..." in ASM and click on "Disable All" button in "Official Add-on Sites" tab. From there on Android SDK Manager will check only the default repository containing tools and APIs.

visor said:
First off, nice guide. I am still trying to understand why you've moved adb and fastboot from platform-tools, rather than export the path to that directory. Is there any particular reason?
EDIT: BTW, you've hit the front page on XDA.
Click to expand...
Click to collapse
It could be done that way, but I personally put other stuff in the android folder on my Mac, and also it's a bit quicker to just drag a file into one folder on your desktop than into a folder within a folder

straycat said:
Hi.
Would it be valid on a very old Powerbook Pismo running 10.4 Tiger??
Thanks in advance and regards.
Click to expand...
Click to collapse
You won't be able to install the SDK, but you can extract the android.zip to a folder named android on your desktop or wherever and use that in place of the SDK step

AshtonTS said:
You bet! this will work on any mac running any OS X (unless Google blocks the install of the SDK, but I have a way around that.
Click to expand...
Click to collapse
Actually, that's a PowerPC Mac, so Intel OSX software will not work.
There is no official support for PowerPC that I know of, but someone on XDA did make binaries for PowerPC.
Sent from my HTC Rezound
Edit: yup, official sdk is x86 only.
BTW, here's the link to the ported binaries.
http://forum.xda-developers.com/showthread.php?t=898744

So many graces, this thing has saved the life because I have not a PC windows, thank you still

varanhia said:
So many graces, this thing has saved the life because I have not a PC windows, thank you still
Click to expand...
Click to collapse
Glad it worked for you

Hi,
Thank you very much. Worked like a charm.
Regards,

Awesome thread. Thanks for taking out the time

DarkSorcerer said:
Hi,
Thank you very much. Worked like a charm.
Regards,
Click to expand...
Click to collapse
nigameash said:
Awesome thread. Thanks for taking out the time
Click to expand...
Click to collapse
Glad it helped you two
Sent from my HTC Sensation

Hi thanks so much for this. Ive been wanting something like this for months/ almost a year.
All the other guides didnt work for me, but this was simple and easy to follow.
Ive encountered one problem and its device specific. My nexus 7 tablet works great with adb, but my htc evo 4g lte doesnt. its rooted, and running cm 10 4.1.2. its debugged any idea how to make it see the device?
UPDATE. so i turned on my usb storage on the device and it now sees the phone. Great work!!!!
Am i going to have to connect storage to mac all the time for this to work on any device?

Ubuntu for N80xx

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In addition to GNU/[email protected] topic, this one is a separate for Ubuntu users. Read below if you want to have native Ubuntu 13.10 wih Gnome/LDXE/XFCE at your Galaxy Note 10.1 device (2012 models only).
Screenshots:
Please be aware, that stuff I share with you is experimental, it does not work 100% correctly and there are some lags and bugs.
Some technical details:
The approach is based on using custom recovery (e.g. custom kernel and initrd image) which boots into Linux. All Linux files are stored at data partition (it is mmcblk0p12 when using standard firmware, which also is internal sdcard) in a separate folder. Initrd script mounts data partition and looks for the special file /media/rootdev - this file contains the path to the Linux root folder. Script sets the Linux root device to be this folder specified and invokes /sbin/init. You see Linux booting - Ubuntu in our case.
However I've also prepared the second folder with native recovery files. E.g. if you change rootdev content to point to recovery files folder, you will boot into recovery. Generally, you can boot any other recovery or Linux distro using this approach. And hosting it at sdcard in a folder much easier than re-partitioning tablet or using loop-device in a file. Free space for your Linux depends only of free space you have at data partition.
Prerequisites:
Rooted GT-N80xx device
Busybox tools installed
Desktop computer with ADB tools
Custom recovery image (with or without menu), native recovery, Ubuntu image files downloaded (see downloads section)
Understanding of what are you doing
Downloads:
Custom recovery image which boots to Linux (no menu) - recovery_nomenu.img
Custom recovery image which boots to Linux (with menu) - recovery_menu.img
Native recovery files archive - recovery.tar.gz
Ubuntu 13.10 files archive - ubuntu.tar.gz
Steps:
Connect your device to the desktop computer with USB cable. Make sure your device is visible when you run "adb devices"
Rename downloaded recovery image to "recovery.img"
Upload downloaded files to the internal memory:
Code:
adb push recovery.img /sdcard/
adb push recovery.tar.gz /sdcard/
adb push ubuntu.tar.gz /sdcard/
Now you need to get into device, so run "adb shell", then type the next commands (the lines beginning from # are the comments, you don't need to type it ):
Code:
# 4. become root user
su -
# 5. go to the internal sdcard real path, where you uploaded files
cd /data/media
# 6. write custom recovery to the special partition, by default it is mmcblk0p6
dd if=./recovery.img of=/dev/block/mmcblk0p6
# 7. unpack native recovery files, the "recovery" folder will be created
gunzip -c ./recovery.tar.gz | tar -x
# 8. unpack Ubuntu files, the "ubuntu" folder will be created
gunzip -c ./ubuntu.tar.gz | tar -x
# 9.1. Now, if you downloaded custom recovery without menu - set what to
# boot, in our case it is Ubuntu, and go to step #10
echo "/media/ubuntu" > ./rootdev
# 9.2. OR, if you downloaded custom recovery with menu - add menu entries
echo "Ubuntu=/media/ubuntu" > ./rootdev
echo "Recovery=/media/recovery" >> ./rootdev
echo "Reboot=reboot" >> ./rootdev
# 10. remove files that we don't need anymore and quit
rm ./recovery.img ./recovery.tar.gz ./ubuntu.tar.gz
exit
exit
Now you should reboot your device to recovery mode. If you did all correctly (and I did not miss anything in steps) you should see Linux booting (and menu if you are using custom recovery with menu).
Please use your S-Pen as mouse, button on the pen works as "right-click".
The password for root user and android user is "q" (small q-letter without quotes).
Notes:
The Ubuntu image I shared with you is v13.10 and Gnome-based (Unity does not work due to Compiz issues).
Regular Gnome session works at most, but have some bugs, due to 3D acceleration support issues. For example, window dragging does not work and the session hangs (sorry, I have not found why, please fix if you can and share your workaround with us).
Gnome Fallback works better, but might not start properly from the first time. E.g. you should boot to regular Gnome session, then log out and login to Fallback (also have no idea why it works like this, please help if have experience).
Due to the issues with Gnome, I've also installed LXDE and XFCE, so you could try login to it. However I would recommend booting to regular Gnome session at least to configure your Wi-Fi connection.
Internal and external sdcards are mounted to /mnt/intSdCard and /mnt/extSdCard paths.
Important notes:
The Ubuntu image has ADB installed. E.g. if something goes wrong at the screen and you are not able to manage your device, connect it to the desktop with USB cable, run "adb shell", then "sudo su -" and you become root user. To restart graphical session you need to invoke "service gdm restart" command.
If you are using custom recovery without menu and want to boot native recovery instead of Ubuntu, edit "rootdev" file at internal sdcard to contain "/media/recovery" path (without quotes). You can do that via ADB shell, using any Android text editor, or directly from Linux.
The last thing to know:
Not all is working from Ubuntu. Currently there is no 3G support and some other things. All of them are discussed in the parent thread
Please let me know if I have missed something and my steps do not work for you. Any other feedback will also be appreciated

downloading right now... just one question! can i do all this with terminal emulator on android?
edit: forget about that last question, tried from terminal emulator and it worked.

X-Stranger said:
In addition to GNU/[email protected] topic, this one is a separate for Ubuntu users. Read below if you want to have native Ubuntu 13.10 wih Gnome/LDXE/XFCE at your Galaxy Note 10.1 device (2012 models only).
Screenshots:
View attachment 2432486 View attachment 2432487 View attachment 2432488
Please be aware, that stuff I share with you is experimental, it does not work 100% correctly and there are some lags and bugs.
Some technical details:
The approach is based on using custom recovery (e.g. custom kernel and initrd image) which boots into Linux. All Linux files are stored at data partition (it is mmcblk0p12 when using standard firmware, which also is internal sdcard) in a separate folder. Initrd script mounts data partition and looks for the special file /media/rootdev - this file contains the path to the Linux root folder. Script sets the Linux root device to be this folder specified and invokes /sbin/init. You see Linux booting - Ubuntu in our case.
However I've also prepared the second folder with native recovery files. E.g. if you change rootdev content to point to recovery files folder, you will boot into recovery. Generally, you can boot any other recovery or Linux distro using this approach. And hosting it at sdcard in a folder much easier than re-partitioning tablet or using loop-device in a file. Free space for your Linux depends only of free space you have at data partition.
Prerequisites:
Rooted GT-N80xx device
Busybox tools installed
Desktop computer with ADB tools
3 files downloaded (see downloads section)
Understanding of what are you doing
Downloads:
Custom recovery image which boots to Linux - recovery.img
Native recovery files archive - recovery.tar.gz
Ubuntu 13.10 files archive - ubuntu.tar.gz
Steps:
Connect your device to the desktop computer with USB cable. Make sure your device is visible when you run "adb devices"
Upload downloaded files to the internal memory:
Code:
adb push recovery.img /sdcard/
adb push recovery.tar.gz /sdcard/
adb push ubuntu.tar.gz /sdcard/
Now you need to get into device, so run "adb shell", then type the next commands (the lines beginning from # are the comments, you don't need to type it ):
Code:
# 4. become root user
su -
# 5. go to the internal sdcard real path, where you uploaded files
cd /data/media
# 6. write custom recovery to the special partition, by default it is mmcblk0p6
dd if=./recovery.img of=/dev/block/mmcblk0p6
# 7. unpack native recovery files, the "recovery" folder will be created
gunzip -c ./recovery.tar.gz | tar -x
# 8. unpack Ubuntu files, the "ubuntu" folder will be created
gunzip -c ./ubuntu.tar.gz | tar -x
# 9. set what to boot, we want Ubuntu
echo "/media/ubuntu" > ./rootdev
# 10. remove files that we don't need anymore and quit
rm ./recovery.img ./recovery.tar.gz ./ubuntu.tar.gz
exit
exit
Now you should reboot your device to recovery mode. If you did all correctly (and I did not miss anything in steps) you should see Linux booting.
Please use your S-Pen as mouse, button on the pen works as "right-click".
The password for root user and android user is "q" (small q-letter without quotes).
Notes:
The Ubuntu image I shared with you is v13.10 and Gnome-based (Unity does not work due to Compiz issues).
Regular Gnome session works at most, but have some bugs, due to 3D acceleration support issues. For example, window dragging does not work and the session hangs (sorry, I have not found why, please fix if you can and share your workaround with us).
Gnome Fallback works better, but might not start properly from the first time. E.g. you should boot to regular Gnome session, then log out and login to Fallback (also have no idea why it works like this, please help if have experience).
Due to the issues with Gnome, I've also installed LXDE and XFCE, so you could try login to it. However I would recommend booting to regular Gnome session at least to configure your Wi-Fi connection.
Internal and external sdcards are mounted to /mnt/intSdCard and /mnt/extSdCard paths.
Important notes:
The Ubuntu image has ADB installed. E.g. if something goes wrong at the screen and you are not able to manage your device, connect it to the desktop with USB cable, run "adb shell", then "sudo su -" and you become root user. To restart graphical session you need to invoke "service gdm restart" command.
If you want to boot native recovery instead of Ubuntu, edit "rootdev" file at internal sdcard to contain "/media/recovery" path (without quotes). You can do that via ADB shell, using any Android text editor, or directly from Linux.
The last thing to know:
Not all is working from Ubuntu. Currently there is no 3G support and some other things. All of them are discussed in the parent thread
Please let me know if I have missed something and my steps do not work for you. Any other feedback will also be appreciated
Click to expand...
Click to collapse
Hi! What about the Source Code for your custom recovery and stuff?

Simon94 said:
Hi! What about the Source Code for your custom recovery
Click to expand...
Click to collapse
In ubuntu or debian:
Code:
apt-get install abootimg
abootimg -x recovery-1.img
After this you will have a folder with all the contents of the img. Some of which you can edit the scripts. You can extract the initrd and kernel even further with abootimg-unpack-initrd

i must say this is pretty awesome very few bugs, and xfce works perfect

Can't risk ruining my tablet until after the semester ends but as soon as it does I'll be trying this! Sounds awesome...

THANK YOU, and THANK YOU for returning! Note 10.1 is currently in hands of Samsung for repairs. Hopefully I can have some fun with this once it is back.
Please check drivers here: http://forum.xda-developers.com/showthread.php?p=45340017#post45340017
I think the driver for Mali acceleration may be possible (you are using Hardkernel from ODROID, correct?).

Simon94 said:
Hi! What about the Source Code for your custom recovery and stuff?
Click to expand...
Click to collapse
My latest kernel sources (arch branch) and toolchain (in the toolchain branch): https://github.com/X-Stranger/N8000
Kernel sources, patched video driver and other stuff: https://code.google.com/p/opensgn/
Recovery can be unpacked/fixed/repacked using abootimg tools as mentioned

dwegiel said:
THANK YOU, and THANK YOU for returning!
Click to expand...
Click to collapse
Don't forget to press "thanks" button (or even "donate to me" )
dwegiel said:
Note 10.1 is currently in hands of Samsung for repairs. Hopefully I can have some fun with this once it is back.
Please check drivers here: http://forum.xda-developers.com/showthread.php?p=45340017#post45340017
I think the driver for Mali acceleration may be possible (you are using Hardkernel from ODROID, correct?).
Click to expand...
Click to collapse
Yes, I'm using Mali acceleration in my Ubuntu image. It is still not 100% working though, that is what I'm talking about, when describe Gnome issues. If you can fix that - please do and share your experience, I'll update the image then.
I would also like someone to help with migration to the latest kernel, which has support for our Exynos board. Exception13 was going to do that, but looks like he is very busy person (and I can understand that).

Have composed a small menu program and added it to custom initrd. Now it is possible to select what to boot (see screenshot), e.g. don't need to edit rootdev file every time, only when adding new menu entry.
Updated first post of this topic with instructions how to get this.

X-Stranger said:
Have composed a small menu program and added it to custom initrd. Now it is possible to select what to boot (see screenshot), e.g. don't need to edit rootdev file every time, only when adding new menu entry.
View attachment 2436305
Updated first post of this topic with instructions how to get this.
Click to expand...
Click to collapse
This is fantastic news for Note 10 owners out-there. I never read about another tablet with a bootmenu to native linux and recovery, so Y'all are lucky to have X-Stranger on the case =] because also now the Ubuntu flavor is on the go.
For all you Note 8 owners out-there I am trying to port the images over with as few changes as possible but my skill level at this type of task is 1/10 that of X-Stranger, so bare with me! (Or you can try and get a package together faster than me =] ).
My process so far is to use the initrd from X-Stranger's recovery_menu.img, and use a zImage from CWM, TWRP, and stock. All that they do is loop back to the note's defalt splash screen. I used X-Stranger's entire recovery_menu.img too and it boots to just a black screen on the Note 8. So my WIP conclusion thus far is that I or someone (volunteer required) has to compile a kernel with some patches just like X-Stranger did on page 3 of the previous thread.
Enjoy Ubuntu all the Note 10 owners....

at the first boot it says "failed to mount extsdcard, press S to skip ....." of course there's nothing to press anything on. I guess it's because my 64gb microsd is ntfs formated. Should I convert it to exfat from windows, should I attach a usb keyboard with OTG and press s?
Sent from my GT-N8013 using Tapatalk

Anyone tried this on the n8020?
I cant get it to work.
Nothing happens
Edit: Wrong recovery partition...for me it is mmcblk0p9

I'm having the same the same issue as panoz, error mounting /mnt/extSdCard. Also tried removing it before boot, but it complains that there's nothing to mount. I only have a Bluetooth keyboard, no otg, so is my only option to format the card?
Btw thanks X-Stranger and all the devs involved for all your work!!

panoz said:
at the first boot it says "failed to mount extsdcard, press S to skip ....." of course there's nothing to press anything on. I guess it's because my 64gb microsd is ntfs formated. Should I convert it to exfat from windows, should I attach a usb keyboard with OTG and press s?
Sent from my GT-N8013 using Tapatalk
Click to expand...
Click to collapse
Yes, it is expecting FAT to be mounted. As a workaround you can disable ext sdcard mounting. Just go to ubuntu image directory, etc folder, find fstab file and comment out the line related to external sdcard (put # symbol in the beginning).

emptynick said:
Anyone tried this on the n8020?
I cant get it to work.
Nothing happens
Edit: Wrong recovery partition...for me it is mmcblk0p9
Click to expand...
Click to collapse
Didn't know n8020 has recovery partition different. Is data partition the same? Or also differs? Did you finally get it working or still need help?

X-Stranger said:
Didn't know n8020 has recovery partition different. Is data partition the same? Or also differs? Did you finally get it working or still need help?
Click to expand...
Click to collapse
Userdata is mmcblk0p16.
It starts to boot but tells me that the path "new_root/linux" and "new_root/ubuntu" couldn't be found.
I read about it recently, but dont know where anymore

What im mostly curious about right now are the bugs you talked about. Are they comparable to the archlinux ones? Worse? Better?
Does it have mali hardware accel?
Does the entire thing crash after a while?
Does the img itself get corrupted every few boots?
Wifi works fine?
Sorry for the barrage, but these are important for me to know before i make the switch
Sent from my Nexus 4 using xda app-developers app

emptynick said:
Userdata is mmcblk0p16.
It starts to boot but tells me that the path "new_root/linux" and "new_root/ubuntu" couldn't be found.
I read about it recently, but dont know where anymore
Click to expand...
Click to collapse
Okay, in your case I need to fix recovery partition to look for mmcblk0p16 instead of mmcblk0p12 in my case. Please send me your email, I'll generate and send special version for you to try fixing that.

younix258 said:
What im mostly curious about right now are the bugs you talked about. Are they comparable to the archlinux ones? Worse? Better?
Click to expand...
Click to collapse
This really depends. I would say that it is the same. The bugs I'm talking about: the graphics may hang it you try to move window in Gnome for example, but works perfectly in Gnome Fallback. You should give it a try.
younix258 said:
Does it have mali hardware accel?
Click to expand...
Click to collapse
Yes, it has the same accel that ArchLinux has. But after summer upgrades Gnome did not want to work in ArchLinux and I was not able to fix that. That is why there is no new ArchLinux images.
younix258 said:
Does the entire thing crash after a while?
Click to expand...
Click to collapse
Have not faced this yet.
younix258 said:
Does the img itself get corrupted every few boots?
Click to expand...
Click to collapse
Nope. There I use new approach without img. All the files are stored and the data partition and it is fsck-ing every boot. Even more - it is easier to have Ubuntu and ArchLinux together. I just need to to prepare the Arch files folder for you when have free time. Or you can do it by yourself.
younix258 said:
Wifi works fine?
Click to expand...
Click to collapse
WiFi works the same. The only thing is better - it does not require to off/on to start seeing hotspots.

[GUIDE][XT1254]Getting Xposed Working

Guide: Getting Xposed Running​This morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
What you'll need:
A paid copy of Mofo (obviously)
Either a modified system image containing Xposed already, or if you like, you can modify one yourself as described in this tutorial. I've already created a modified system image to include Xposed as well as Wifi Tethering and a modified hosts file for ad blocking.
The Xposed Installer apk
Xposed Installer needs to be installed on your phone
Terminal Emulator and ES File Explorer from the play store need to be installed on your phone
A rooted image flashed to your phone
Before flashing anything, this is what you need to do:
On your computer, find your de.robv.android.xposed.installer_v33_36570c.apk and rename it to be a .zip file.
Open this .zip file and extract /assets/XposedBridge.jar and, if you're modifying your own system image, extract /assets/arm/app_process_xposed_sdk16 as well.
Put XposedBridge.jar somewhere on your phone, I like to use the Downloads folder so I don't lose track of it later.
In ES File Explorer, navigate to /data (NOT SDCARD/DATA)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure it doesn't say sdcard > data!
Create a folder called "xposed"
Long press the folder, select properties, and set permissions to 755
Set the owner of the folder to root and the group to shell
Move XposedBridge.jar into the xposed folder we just created.
Make the permissions of XposedBridge.jar 644
As before, make the owner root and the group shell.
Open the Xposed Installer app on your phone.
Open terminal emulator and type
Code:
ps | grep xposed
This will return a pattern like the following. Make a note of the first seven characters, as shown (the first is a lowercase u)
Return to /data/xposed
Create two new files: modules.list and modules.whitelist
Make the permissions on both files 644 as above
Set the owner to the seven characters we noted down earlier and the group to shell on both files
If you're flashing a pre-compiled image with Xposed, you're done here! Go ahead and flash, and enjoy!
If you're modifying your own system image, you've got some more work to do. Take app_process_xposed_sdk16 from the Xposed apk and rename it to app_process.
In your turbo system image, navigate to /bin/ and replace app_process with the one from Xposed Framework. Make sure its permissions are set to 755:
Code:
sudo chmod 755 /path/to/img/bin/app_process
Linux does not allow setting the group of a file to a nonexistent group, so on your pc you'll have to make a shell group:
Code:
sudo groupadd shell
Change the group of app_process to shell:
Code:
sudo chgrp shell /path/to/img/bin/app_process
You're ready to flash!
NOTE: If XposedBridge.jar reports problems, try setting installation mode in the Xposed installer app to recovery (flash manually) and hitting install, then reboot.
You're done! Xposed should show up as installed! Don't use any modules that require system write access, such as replacing system icons, but most modules (ie GravityBox) work fine without it.

Ekkoria said:
This morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
Click to expand...
Click to collapse
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.

ntxct said:
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
Click to expand...
Click to collapse
Same here! When I finally opened Xposed Installer and saw it read the framework as installed, I've almost never been so excited about something Android.

i dont need it but its a great guide, easy, short and with pictures!

Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.

Thanks so much man, about to flash. Will let you know how it goes.

Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours

It did not work for xposedbridge.jar

aven1357 said:
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Click to expand...
Click to collapse
Yes, you will need to be rooted first to perform these actions. Apologies for not originally including this. OP updated

savagebunny said:
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
Click to expand...
Click to collapse
Yes please do so. I'd be very interested.
Sent from my XT1254 using XDA Free mobile app

I am having trouble with es file explr it tells me the operation failed when trying to do anything I have root and I enabled root for ES it seemed to work on root browser fine (I reset my device and just installed es so far)
edit checked and the root enhancement options are greyed out?

After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?

I am having same problem as u smokie

smokie75 said:
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
Click to expand...
Click to collapse
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.

Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
Thanks! That worked!

Thanks for this , works great , now we just need one with busybox preinstalled

Stuck at this point any help?[/ATTACH]
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse

so will doing this enable gravitybox to work on the turbo?

hmltnjrmy7 said:
Stuck at this point any help?[/ATTACH]
Click to expand...
Click to collapse
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces

rayjr13 said:
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
Click to expand...
Click to collapse
Lol the dead droid freaked me out at first, but I'm so happy xposed finally works!!!

[CLOSED]Android ON Linux (AoL) and not the standard other way around

@MikeChannon removed OP. please close
what? lol

Good good. Can't wait! :silly:

workdowg said:
Good good. Can't wait! :silly:
Click to expand...
Click to collapse
i'm working on an automated deploying (kind of the one for restoring the bios) and i will start with the 1050f one. automated because otherwise things can get messy
maybe you can prepare some tutorial for the X part based on your experience (tho i, as a proud windows user, didnt believed people use that stuff and i'm sure goes the other way around )

ionioni said:
i'm working on an automated deploying (kind of the one for restoring the bios) and i will start with the 1050f one. automated because otherwise things can get messy
maybe you can prepare some tutorial for the X part based on your experience (tho i, as a proud windows user, didnt believed people use that stuff and i'm sure goes the other way around )
Click to expand...
Click to collapse
Will do Master Chef! It really was simple once the base is done...
Proof of concept (Actually it just plain works...):
Arch x86_x64 - LXDE (with Pulse sound) running on Xsdl
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If Installed, Can I steam game?

neverapple88 said:
If Installed, Can I steam game?
Click to expand...
Click to collapse
Most likely, if the linux graphics driver works with the embedded SoC graphics driver. And it seems Android also uses the same i915 driver.

update: need a 1050F owner to test the AoL deployment tool... my device is a 1380F so i cannot test thoroughly, i want to test it with a real owner. pm for details. worst case: you will have to flash kitkat rom back, best case: it keeps all the existing files in place, stealing space from data partition for the new linux. waiting...

ionioni said:
update: need a 1050F owner to test the AoL deployment tool... my device is a 1380F so i cannot test thoroughly, i want to test it with a real owner. pm for details. worst case: you will have to flash kitkat rom back, best case: it keeps all the existing files in place, stealing space from data partition for the new linux. waiting...
Click to expand...
Click to collapse
Anyone??? Everybody was so excited and no one wants to try? I'll do it if nobody else will. For me it means backing up my current Linux and Android partitions (been working hard at getting them lean and mean) partitions and going through the whole flash from kitkat ordeal again... for probably the 10th time at least...
Sent from my YOGA Tablet 2-1050F using Tapatalk

workdowg said:
Anyone??? Everybody was so excited and no one wants to try? I'll do it if nobody else will. For me it means backing up my current Linux and Android partitions (been working hard at getting them lean and mean) partitions and going through the whole flash from kitkat ordeal again... for probably the 10th time at least...
Sent from my YOGA Tablet 2-1050F using Tapatalk
Click to expand...
Click to collapse
yeah, funny thing...
upped a first version of the tutorial

and the first batch of files (for 830 and 1050)

I could not wait a few days ago. I excited.
But I can't English well. So it is difficult to test.
I wanted the first Windows. But if Linux works reliably, I would choose Linux. (I'm ubuntu user)
I think Intel graphics drivers are going to be good as the performance by Android. (for steam game!)
However, one problem occurred.
I used data parted More than 20GB. (sry my english)
This space is insufficient to install Linux and applications and steam game.
The workaround is to install a Linux partition on the sd card.
Can I install a Linux partition on the sd card? (and run)
ps. After entering the text has been changed the post. I'll go to see the Thread.

neverapple88 said:
I could not wait a few days ago. I excited.
But I can't English well. So it is difficult to test.
I wanted the first Windows. But if Linux works reliably, I would choose Linux. (I'm ubuntu user)
I think Intel graphics drivers are going to be good as the performance by Android. (for steam game!)
However, one problem occurred.
I used data parted More than 18GB. (sry my english)
This space is insufficient to install Linux and applications and steam game.
The workaround is to install a Linux partition on the sd card.
Can I install a Linux partition on the sd card? (and run)
Click to expand...
Click to collapse
this IS ONLY FOR UNCHANGED STOCK PARTITIONS LAYOUT (it will refuse to install if it detects that your data partition is not having the original configuration), it CHANGES your partitions by adding two more partitions a big one (min. 1024MB but you can make it bigger durin installation) and a small one for the original Android initramfs (read the tutorial to understand more) and that space is taken (ripped off) from the data partition. and whenever you will uninstall it will remove the two new partitions and restore the data partition to the original size
i did not did (i had a manual setup at some point) a setup to sdcard s it is too slow ( @workdowg can give you more details, as he stayed on that configuration more i went for the on the internal partition variant quickly when i've seen how much it takes to work with files when you 're having linux on sdcard)
also on the X related issues you should talk with him (i didn't used X on AoL, i only use shell tools/servers)
you should flash back your Android and check that you have the original partitions (number, size and names) before trying to install.

I have made a mistake when installing. (no insert rootfs file, uninstall, etc ...)
now. my /data partition 11.11GB (OMG,,,)
I've tried a factory reset. but no change. (GB)
how to? ...
ps. I want to work with the command.

neverapple88 said:
I have made a mistake when installing. (no rootfs file, uninstall, etc ...)
now. my /data partition 11.11GB
I've tried a factory reset. but no change.
how to? ...
Click to expand...
Click to collapse
use the corresponding tool from this post (if youre on lollipop use the lollipop one) it will open a root shell on a very early boot (without Android loading), you have to start in DnX mode then start the tool
after the shell opens, open another command window and push the extracted (attached) gdisk (it's a static IA32 version i compiled for working with GPT partitions) to your tab
adb push gdisk /tmp/gdisk, return to the root shell and input
chmod 755 /tmp/gdisk
/tmp/gdisk -p /dev/block/mmcblk0
and post the result
the partition.txt attached shows how ot should be default configurations of the partitions on a 1050 (830) device

ionioni said:
use the corresponding tool from this post (if youre on lollipop use the lollipop one) it will open a root shell on a very early boot (without Android loading), you have to start in DnX mode then start the tool
after the shell opens, open another command window and push the extracted (attached) gdisk (it's a static IA32 version i compiled for working with GPT partitions) to your tab
adb push gdisk /tmp/gdisk, return to the root shell and input
chmod 755 /tmp/gdisk
/tmp/gdisk -p /dev/block/mmcblk0
and post the result
the partition.txt attached shows how ot should be default configurations of the partitions on a 1050 (830) device
Click to expand...
Click to collapse
I first start DnX mode -> run tmp-root-1050F-lollipop -> run normal cmd
(cmd) >adb push gdisk /tmp/gdisk
adb server is out of date. killing...
* daemon started successfully *
5597 KB/s (492988 bytes in 0.086s)
after root cmd is shutdown(end)

neverapple88 said:
I first start DnX mode -> run tmp-root-1050F-lollipop -> run normal cmd
(cmd) >adb push gdisk /tmp/gdisk
adb server is out of date. killing...
* daemon started successfully *
5597 KB/s (492988 bytes in 0.086s)
after root cmd is shutdown(end)
Click to expand...
Click to collapse
but the root shell opens??? you must wait until it opens the root shell yeah, it opens otherwise you would not be able to push (i was reading too fast)
the window gets killed because the temp_root has a differnet version of adb and on your pc there is another and when you try to do the adb push you kill the adb from the tmp_root, but that is not a problem, just do a adb shell after you did the push and it will open anothe root shell and you can enter and input the other commands
also, have you seen the text file with the partitions? you seemed surprised and i don't know why, on the default configuration the data has around 11GB, do not confuse that with the whole mmc that has 16

ionioni said:
but the root shell opens??? you must wait until it opens the root shell yeah, it opens otherwise you would not be able to push (i was reading too fast)
the window gets killed because the temp_root has a differnet version of adb and on your pc there is another and when you try to do the adb push you kill the adb from the tmp_root, but that is not a problem, just do a adb shell after you did the push and it will open anothe root shell and you can enter and input the other commands
also, have you seen the text file with the partitions? you seemed surprised and i don't know why, on the default configuration the data has around 11GB, do not confuse that with the whole mmc that has 16
Click to expand...
Click to collapse
Thank you! It has been recovered.
This was a fun experience. (and risk...) XD
I'd like to know more, but do not know the English language. :silly:
So I'll use the Arch Linux.
Your articles are hard to read, But Thank you for your time.

neverapple88 said:
Thank you! It has been recovered.
This was a fun experience. (and risk...) XD
I'd like to know more, but do not know the English language. :silly:
So I'll use the Arch Linux.
Thank you for your time. : D
Click to expand...
Click to collapse
Theres an Ubuntu too now...

ionioni said:
Theres an Ubuntu too now...
Click to expand...
Click to collapse
C
===============================================
Found ready-made linux rootfs.tgz file, pushing to device...
Checking for valid deployment enviroment
Error! Invalid <failed check> data partition end sector.
Have you already deployed Linux? If so try restoring first.
ABORTING! Nothing was changed!
OMG.. (I try fix)

neverapple88 said:
C
===============================================
Found ready-made linux rootfs.tgz file, pushing to device...
Checking for valid deployment enviroment
Error! Invalid <failed check> data partition end sector.
Have you already deployed Linux? If so try restoring first.
ABORTING! Nothing was changed!
OMG..
Click to expand...
Click to collapse
nothing to be scared of, it has not changed anything, just detected that something is wrong and exited
what is your partition layout? it compares what he reads against the stock values and if they don't match he gives error.... can you run a command so that we see the EXACT layout of your partitions? (number, start_sector, end_sector, name)
you could use the commands i asked you previously to run
temp_root -> adb push gdisk... etc and you will get a print of the partitions on your device
what is your mmc capacity (16GB?) if your mmc is a 32GB one then download and use this