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!!!

[DEV] Tutorial for installing ubuntu on Iconia

For those who want a tutorial, here's my experience in installing the system:
(PS: FOR those who want a really simple command-by-command tutorial, please see #26 post. That's part 1 of the tutorial on how to boot ubuntu up without wireless. If you need wireless working and want a command-by-command tutorial on that, just reply and I'll make it. )
I mainly referred to sp3dev's thread: http://forum.xda-developers.com/showthread.php?t=1158260
I've make ubuntu run on my iconia, but I cannot let bluetooth run so you'd better have a usb keyboard and (if you could find the trick to use the touch screen, no need of) a usb mouse.
Tools to prepare:
1. Ubuntu OS on PC with adb tool.
2. A >=4GB microSD card and make sure iconia can identify it.
3. USB keyboard and USB mouse
4. rooted iconia with acer recovery installer, busybox, terminal emulator.
5. Perhaps more that I didn't listed
Files to download:
1. rootfs: http://www.dmmhosting.co.uk/tegra-rootfs.tar from Digitaldaz;
2. precompiled header: http://www.mediafire.com/?ucvk6x66129igzc from sp3dev;
3. itsmagic: http://forum.xda-developers.com/showthread.php?t=1121543&highlight=itsmagic from sc2k;
4. source code: https://github.com/astarasikov/iconia-gnu-kernel from sp3dev;
5. Perhaps more that I didn't listed
Procedure to install ubuntu:
1. Use your computer to format your microSD card into two partitions: one is in FAT32, to be used as normal external storage. Suggested minimum size is 1GB, to store backup file in step 2. The other is ext4, to store root filesystem of ubuntu. Suggested minimum size is 3GB. Tools: fdisk, mkfs.vfat, mkfs.ext4. Using sudo when making filesystem. Refer to rkaszala's post for further information: http://forum.xda-developers.com/showthread.php?t=1158260&highlight=itsmagic&page=12
(Comment: I use computer to format while he/she uses iconia to format.)
Make sure the formatted sdcard can be recognized by iconia as /dev/block/mmcblk1p1 and /dev/block/mmcblk1p2 .
2. Backup all data using itsmagic link above. Be familiar with usage of itsmagic, esp. use it to recalculate the checksum.
3. use tools here: http://forum.xda-developers.com/showthread.php?t=1126364 to flash the newrec.img file onto the /dev/block/mmcblk0p1, and use itsmagic to recalculate checksum.
3.1. on android system, use terminal emulator to copy /system/etc/nvram.txt out as bcm4329-fullmac-4.txt .
4. USING SUDO to unzip the rootfs tarball referred in Files:1 into the ext4 fs mentioned in step 1. If you do not use sudo, some device nodes will not be able to be created.
5. SUDO EDIT the etc/fstab IN YOUR UNZIPPED ROOT FILESYSTEM NOT IN YOUR OWN UBUNTU SYSTEM to one line:
proc /proc proc defaults 0 0
6. compile source code using instructions by sp3dev here: http://forum.xda-developers.com/showthread.php?t=1158260&highlight=itsmagic&page=9 in the middle part of the page.
7. copy the compiled bcm4329-fullmac-4.bin firmware (should be at lib/firmware/brcm/) to sdcard's root filesystem's location: /lib/firmware/brcm/ folder and copy the previous bcm4329-fullmac-4.txt here.
8. copy the compiled modules into sdcard's root filesystem's /lib/modules/ (I forget the name of the folder so be sure to name it correctly. )
9. insert the sdcard into iconia and reboot with wolume down key pressed (the way to boot into recovery img.)
and now, you should have reached what I have reached.
If you failed on some step please tell me. All I summarized is what I have done, so please refer to their original post for more information.

impressive...

Can you make more detailed tutorial?

can you make video tutorial, because some people don't understand how to do this things. Sorry for bad english

Tautvaldas said:
can you make video tutorial, because some people don't understand how to do this things. Sorry for bad english
Click to expand...
Click to collapse
My opinion: tutorial in first post is good enough. If someone don't understand is better not to try!

PhilipZ said:
My opinion: tutorial in first post is good enough. If someone don't understand is better not to try!
Click to expand...
Click to collapse
Sorry if I've missed something here but I didn't realize your comprehension ability was the benchmark for tutorials being "good enough"
Troll or not, I hate attitudes like this. If everybody followed this line of thought we'd still be in the stone ages.
The whole purpose of a tutorial is to show people how to do something that is outside of there general knowledge. If adding more details to a tutorial will allow it to be useful a wider audience then surely that can only be a good thing for knowledge sharing and the author.
A video tutorial, if somebody can spare the time of course, would be great.

Hi guys:
Sorry I'm really busy these days so I didn't have time to give more detail on that. This weekend I will reinstall the ubuntu on my Iconia and will post a more detailed command by command tutorial here. I don't have a camera nor a phone with good camera so I'm afraid I cannot make a video, but if u have any question pls just reply here and I will get an email notification and I'll reach back asap.
The installation is tough yet exciting so I understand your feeling of getting ubuntu running on your iconia, but my word now is don't expect too much, it's just running yet still slow and I didn't patch some drivers on (At least now I cannot get bluetooth and nvidia drivers work but wifi works!).
Anyway, even if you're new here, I recommend you to read the links I posted above as they're good place to learn stuff.

sirzen said:
Hi guys:
This weekend I will reinstall the ubuntu on my Iconia and will post a more detailed command by command tutorial here.
Click to expand...
Click to collapse
Thank you! We are waiting
You used rootfs from Digitaldaz or from rkaszala ?
(Sorry for my english)

I'm planning a video tutorial once I work the bugs out, right now still having wifi (it loads firmware but I'm not offered any networks, it statys "disabled") issues, and I'm working it out on Ubuntu 10.10 which doesn't have unity, unity is a POS, requires far too much of the gpu, and for our tab we can live without.
wish me luck!

Nice thread i am still working thru the wireless card issues
You cleaned up most of thenative linux thread nicely. I am still struggling with wifi. I made a 250mb rootfs trying for minimalize size
{
"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"
}

rkaszala said:
Nice thread i am still working thru the wireless card issues
You cleaned up most of thenative linux thread nicely. I am still struggling with wifi. I made a 250mb rootfs trying for minimalize size
Click to expand...
Click to collapse
Noob question!
Can I use all 2gb SD Card to ext partition,and will linux fit in >2gb ?

Currently I'm using the one from Digitaldaz since I have not get a usable rootfs, but I strongly suggest u to use something built by yourself if you could.
ZeRo_samdroid said:
Thank you! We are waiting
You used rootfs from Digitaldaz or from rkaszala ?
(Sorry for my english)
Click to expand...
Click to collapse

I originally couldnt get the rootfs posted by Digitaldaz to untar tons of symlink errors. So i installed Ubuntu 11 on a desktop , built rootfs using rootstock.

Cool......
rkaszala said:
I originally couldnt get the rootfs posted by Digitaldaz to untar tons of symlink errors. So i installed Ubuntu 11 on a desktop , built rootfs using rootstock.
Click to expand...
Click to collapse

Still havent been able to get the wireless to work, found out that the brcm-bcm4399 had to remove the brcm- from the front. No more firmware errors. just not getting any wlan0 , when i dmesg | gregp brcm no errors there. Any ideas what to try now?

Get your wifi working? I did the bcm4329-fullmac-4.bin and nvram > bcm4329-fullmac-4.txt and then copied the 2 .fw files from the github. I am still not having any luck with wifi.
Wifi Update,
rfkill listall showed the wifi blocked , odd. So i did a rkfill unblock wifi and now i can get the wlan0 to ifup. But using wicd both wext and nl80211 i cant get it to do anything. thoughts?

rkaszala said:
Get your wifi working? I did the bcm4329-fullmac-4.bin and nvram > bcm4329-fullmac-4.txt and then copied the 2 .fw files from the github. I am still not having any luck with wifi.
Wifi Update,
rfkill listall showed the wifi blocked , odd. So i did a rkfill unblock wifi and now i can get the wlan0 to ifup. But using wicd both wext and nl80211 i cant get it to do anything. thoughts?
Click to expand...
Click to collapse
That's how I get my wifi work. I don't know more about the detail. I think Digitaldaz add something in his rootfs as his rootfs tarball is ~400MB while the rootstock stuff is less than 300MB.

same root fs? cause last time i tried his was 1.5 gig

rkaszala said:
same root fs? cause last time i tried his was 1.5 gig
Click to expand...
Click to collapse
I mean his tarball. After untar it should be about 1.5gig. I installed some updates and it grows up to 2.0gig on my one. Should be same?

what about the touch screen ... any prograsess ???

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.

[Root] How to root Phoenix OS without replacing system.img

Hey guys, recently a member from Discord channel (ikkun) showed me steps on how to root Phoenix OS by just placing the su binary in the system folder. This method is so much easier and convenient than replacing the system.img, that it should be the main way to root your Phoenix OS installation.
Advantages:
No need to wait to download and extract a 500MB system.img. Instead, download a 5MB .zip file
No need to do a fresh install. You can root an existing installation without removing all your data.
Play store and Google Calendar sync work
Tested and works with:
v2.2.0 64-bit
v2.2.1 64-bit
v2.5.0 64-bit
v2.5.3.64 64-bit
v2.5.7.348 64-bit (Tested myself)
(Probably works on your system too. Why not test it and post your results below?)
Instructions:
Download and extract the .zip file. For the purposes of the tutorial, I'm going to assume that you extract it in the Download folder and rename the SuperSU folder to su. Inside su, you should see META-INF, x64, x86, etc folders.
{
"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"
}
Open the terminal by pressing Alt+F1
If you have Phoenix OS 32-bit, type in these commands:
Code:
cd /system/xbin
mv su su.orig
cp /sdcard/Download/su/x86/[B]su.pie[/B] su
chmod 4751 su
su --install
su --daemon
If you have Phoenix OS 64-bit, type in these commands:
Code:
cd /system/xbin
mv su su.orig
cp /sdcard/Download/su/x64/[B]su[/B] [B].[/B]
chmod 4751 su
su --install
su --daemon
This screenshot is for 64-bit:
Note 1:
If after typing in the mv su su.orig command, you get an error saying:
mv: rename su to su.orig: No such file or directory
Click to expand...
Click to collapse
That means your Phoenix OS installation does not come with the su binary. Skip the mv command and proceed to the next step since there is nothing to make a backup of.
I usually install my Phoenix OS using the .exe installer and always see the su file in that folder during the rooting process so I never see this error. It was never clear to me why people are missing the su binary, but my observations tell me it could be because people are installing it using the ISO file or using 32-bit. I never had the opportunity to test this out, but if you have this error, please post your Phoenix OS version, architecture, and installation method.
Click to expand...
Click to collapse
Note 2:
Make sure you type in the commands exactly as provided. I saw other people were having trouble because they typed in the command incorrectly; they were missing a period after a space. It should be with a period and a space after the command (if you're rooting x64):
Code:
cp /sdcard/Download/su/x64/su [B].[/B]
and not:
Code:
cp /sdcard/Download/su/x64/su
The dot simply tells the cp command to place the file in the working directory (which was set earlier by the cd /system/xbin command). Alternatively, you can replace the dot with the current directory, the new command being:
Code:
cp /sdcard/Download/su/x64/su /system/xbin
It's just easier to type a dot then type out the whole directory, especially considering the fact that you can't copy-paste in the terminal (as far as I know, could be wrong)
Click to expand...
Click to collapse
Close the console by pressing Alt+F7. (If you have trouble exiting the console, post below with your Phoenix OS version and architecture. Then, try pressing Ctrl+Alt+F7)
Phoenix OS might crash and restart. Using the File Manager, go to the Download folder. Navigate to su>common> and install Superuser.apk
Launch SuperSU app from the app drawer. Press Continue, then select Normal to update the binary normally. Exit out of the app after the update is successful.
Launch Security app from the app drawer. Click AutoRun.
Toggle SuperSU to enable it so that it can automatically run when other apps request Superuser access. Exit out of the app.
History:
Added notes for common errors people were having
Added another keystroke to exit console (Ctrl+Alt+F7)
Added screenshots. Removed unnecessary steps. Fixed grammar mistakes.
These instructions were posted in the Phoenix OS Discord Server by ikkun. Thanks to Chainfire for SuperSU.
Instructions ported from tutorial Installing SuperSU on Remix OS 2.0
Attached zip file in case their website is down.

Thanks, it works

jamarita said:
Thanks, it works
Click to expand...
Click to collapse
Thank you for the confirmation! What device do you have and what GPU does it come with?

Does not work on hp 655 32 bit

lomax84 said:
Does not work on hp 655 32 bit
Click to expand...
Click to collapse
First of all, what kind of a computer is an "hp 655"? Second, can you provide more details to what exactly doesn't work? What step are you failing at?

Working fine for me on PhoenixOS 2.2.1. My computer is a HP Spectre x360.

ariadnejro said:
Working fine for me on PhoenixOS 2.2.1. My computer is a HP Spectre x360.
Click to expand...
Click to collapse
Awesome, thanks for letting us know!

The method here is which I use to make a partition of demarage for another os, the method is simple and it erases nothing in the PC videos Show a complete installation has 2m30 you can see the procedure. On the second video we little to see how installing Android 7.1 Phoenixos 2.2 new version the whole in two-tier and triple boot.
Phoenixos 1.1
Partition at 2mn30
https://youtu.be/NUCsSkbooqw
https://youtu.be/LWYU3eIp-Zk
Phoenixos 2.2
https://youtu.be/fYpLOBjnYxM
https://youtu.be/W0kz9LUXdiA
Here is I hope to have taken forward l.

This method still causing the Play Services sync problems with Gmail, etc. Any fix?

mic1000s said:
The method here is which I use to make a partition of demarage for another os, the method is simple and it erases nothing in the PC videos Show a complete installation has 2m30 you can see the procedure. On the second video we little to see how installing Android 7.1 Phoenixos 2.2 new version the whole in two-tier and triple boot.
Phoenixos 1.1
Partition at 2mn30
https://youtu.be/NUCsSkbooqw
https://youtu.be/LWYU3eIp-Zk
Phoenixos 2.2
https://youtu.be/fYpLOBjnYxM
https://youtu.be/W0kz9LUXdiA
Here is I hope to have taken forward l.
Click to expand...
Click to collapse
I'm sorry, it's kind of hard to understand what you're trying to say, but I'm assuming this is a guide on how to set up a triple-boot system.
jbardi said:
This method still causing the Play Services sync problems with Gmail, etc. Any fix?
Click to expand...
Click to collapse
This method only roots the system, it's not supposed to fix the sync problems with Gmail. The problem exists even before you root, so we need to search around for a solution. I would recommend asking in the Discord channel and someone might shed you some light on this issue.

It is exactly it, forgiveness if my English is not very clear. It is a method to install a dual boot or a triple boot in this particular case on a tablet Teclast x98 or on a mini PC Pipo X7 that have the same characteristics it does not solve at all the problems of synchronization of Google moreover I have no problem of synchronization on Phoenix os 2.2

mic1000s said:
It is exactly it, forgiveness if my English is not very clear. It is a method to install a dual boot or a triple boot in this particular case on a tablet Teclast x98 or on a mini PC Pipo X7 that have the same characteristics it does not solve at all the problems of synchronization of Google moreover I have no problem of synchronization on Phoenix os 2.2
Click to expand...
Click to collapse
Oh okay, thank you for the guide, I hope others find it useful. The other reply was to another user, not to you. Phoenix OS has a Gmail sync issue. So if you try to install and sign into the Gmail app, you will not be able to synchronize your mail. You actually do have a synchronization issue, it's just that you haven't experienced it yet because you haven't tried using the Gmail app.

meanhacker said:
I'm sorry, it's kind of hard to understand what you're trying to say, but I'm assuming this is a guide on how to set up a triple-boot system.
This method only roots the system, it's not supposed to fix the sync problems with Gmail. The problem exists even before you root, so we need to search around for a solution. I would recommend asking in the Discord channel and someone might shed you some light on this issue.
Click to expand...
Click to collapse
when I type the 2nd command, mv su su.orig it says no such file, what am i doing wrong ?
Im single OS booting and the files are as you laid out, but in the Download folder from within Phoenix OS

Seanie280672 said:
when I type the 2nd command, mv su su.orig it says no such file, what am i doing wrong ?
Im single OS booting and the files are as you laid out, but in the Download folder from within Phoenix OS
Click to expand...
Click to collapse
It sounds like you're not in the right folder. What Phoenix OS version do you have and what processor architecture? (32/64-bit) are you sure you're running the first command correctly (cd /system/xbin)? In the terminal, type in pwd and press enter. Post the output here. It should say /system/xbin. If not, use the command cd /system/xbin. If that doesn't work, type in ls -a and post the output here. Can you find su in that list of files? If so, all we're trying to do is make a backup of it before replacing it with the one we downloaded from Chainfire

meanhacker said:
It sounds like you're not in the right folder. What Phoenix OS version do you have and what processor architecture? (32/64-bit) are you sure you're running the first command correctly (cd /system/xbin)? In the terminal, type in pwd and press enter. Post the output here. It should say /system/xbin. If not, use the command cd /system/xbin. If that doesn't work, type in ls -a and post the output here. Can you find su in that list of files? If so, all we're trying to do is make a backup of it before replacing it with the one we downloaded from Chainfire
Click to expand...
Click to collapse
Im running the latest version x86-64bit ver: 2.21.247
Ive manually had a look in the system xbin folder and can see all of the above mentioned files and commands etc, mv, su.orig etc etc thats why I dont understand why its not working, so ill try your other commands now and let you know.
EDIT: running it on a packard bell easynote TE, Intel celeron N2820 CPU, 4gb DDR3l with a samsung evo 120gb ssd
EDIT 2: when im in system/bin and type pwd it gives the result /system/xbin, posted a couple of pictures below.

Seanie280672 said:
Im running the latest version x86-64bit ver: 2.21.247
Ive manually had a look in the system xbin folder and can see all of the above mentioned files and commands etc, mv, su.orig etc etc thats why I dont understand why its not working, so ill try your other commands now and let you know.
EDIT: running it on a packard bell easynote TE, Intel celeron N2820 CPU, 4gb DDR3l with a samsung evo 120gb ssd
EDIT 2: when im in system/bin and type pwd it gives the result /system/xbin, posted a couple of pictures below.
Click to expand...
Click to collapse
Great, thanks for the pictures. So it looks like you already made a backup of the su, which is now named su.orig. Proceed with the rest of the steps

meanhacker said:
Great, thanks for the pictures. So it looks like you already made a backup of the su, which is now named su.orig. Proceed with the rest of the steps
Click to expand...
Click to collapse
Thanks for all of your help, all the commands went in ok this time, however a little problem, ALT+F7 isnt working to close down terminal, so I have to force restart, then once its back up and running, continuing with the instructions to install super SU says not root found.

Seanie280672 said:
Thanks for all of your help, all the commands went in ok this time, however a little problem, ALT+F7 isnt working to close down terminal, so I have to force restart, then once its back up and running, continuing with the instructions to install super SU says not root found.
Click to expand...
Click to collapse
I don't remember off the top of my head, but try Ctrl+Alt+F7. Also, try other numbers for the F (Function) keys. If superuser doesn't work for you, go into the Security app and enable SuperUser for AutoRun.

meanhacker said:
I don't remember off the top of my head, but try Ctrl+Alt+F7. Also, try other numbers for the F (Function) keys. If superuser doesn't work for you, go into the Security app and enable SuperUser for AutoRun.
Click to expand...
Click to collapse
Thank youu very much, strangest thing happened, just reinstalled the whole OS and all the commands went in this time perfectly fine, the keys to get out of Terminal are indeed Ctrl+Alt+F7.
Managed to have a bit of a play and sort of get the latest version of showbox running, also installed it through Kodi where it appears to be working perfectly fine, going to stick with this OS for a while now, does everything that I need it for, without the crap sluggishness of Windows, looking out for any future updates.

Seanie280672 said:
Thank youu very much, strangest thing happened, just reinstalled the whole OS and all the commands went in this time perfectly fine, the keys to get out of Terminal are indeed Ctrl+Alt+F7.
Managed to have a bit of a play and sort of get the latest version of showbox running, also installed it through Kodi where it appears to be working perfectly fine, going to stick with this OS for a while now, does everything that I need it for, without the crap sluggishness of Windows, looking out for any future updates.
Click to expand...
Click to collapse
I'm glad you got it to work! I will update the OP with the new information. What made it work? Was it the fact that you could now escape the terminal or letting Superuser in AutoRun?

[LINUX][POSTMARKETOS] Native Linux on the Asus Eee Pad Transformer TF101

Instructions HERE.
TO DO:
- Other things mentioned in the wiki:
https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101)
VERSION INFORMATION (CHANGELOG)
A newer MATE image is available to download. Download it here or here.
Notes about this release:
v4.0
- Please read the updated instructions.
- Vast performance improvements overall (because it's using mainline 5.12.8 grate kernel).
- It's trickier to get it working, if you cannot follow the instructions please change to v3.0.
v3.0
- Firmware has to be renamed at first boot.
Do the following command as root or using sudo:
Code:
sudo ash rename-firmware.sh
Those who are migrating from older versions or want to know what this .sh file is:
https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101)
Follow the wiki, look into Wi-Fi section.
Reboot and done.
- Bluetooth is working, but only from terminal.
Code:
sudo hciconfig hci0 up
hcitool scan
hcitool pair, etc etc
- Buttons from trackpad are working, mousepad not yet.
- Updated kernel zip. Latest release here: https://github.com/antonialoytorren...rnel_zip/PostmarketOS-kernel-3.1.10-15-r2.zip
v2.0
- Changed icons (https://github.com/vinceliuice/vimix-icon-theme) and GTK (https://github.com/vinceliuice/vimix-gtk-themes) of XFCE. Now it is a modern XFCE.
- Removed second panel to save space.
- The XFCE Whiskermenu does not close when typing in onboard.
· Other things that will be included in the next release:
- Make a desktop shortcut opening a browser linking this XDA thread.
- Try to get trackpad working
v1.0
- Initial Release

Screenshots
MATE 4.0 (mainline PostmarketOS kernel)
See HERE.
https://imgur.com/a/Sf7BbFt
XFCE 2.0
{
"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"
}
XFCE
MATE
JWM

Dual Booting Android and PostmarketOS
You can only dual boot if you have installed postmarketOS in your microSD or SD Card. If not, you (probably) have to wipe your partition where postmarketOS is located for booting Android again.
Well, the easiest way to do dual boot is this:
In the sdcard folder or whatever folder you want, put the Android ROM zip and PostmarketOS' kernel zip.
Note: Be sure to run the TWRP version 2.8.1.1, otherwise Android won't flash.
The Android ROM (I'm using timduru's ROM: https://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496) can be downloaded here: https://downloads.timduru.org/android/tf101/K.A.T/KatKiss/6.0/dev/KatKiss-6.0_034.zip
The PostmarketOS' kernel zip can be downloaded here: https://github.com/antonialoytorrens/TF101-linux-images/raw/master/postmarketOS/kernel_zip/PostmarketOS-kernel-3.1.10-15.zip (has some issues with WiFi, flashing the blob using dd and adb is more recommended, https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101))
If you want Android, go to recovery and flash timduru's ROM.
If you want PostmarketOS, go to recovery and flash my kernel zip (please, disable signature verification when flashing)

Reserved
Reserved

aat596 said:
XFCE
MATE
Click to expand...
Click to collapse
WOW! I was in the last days researching something about it because I found this machine stopped and it has a good relative hardware to run light applications, really a waste not to have more updates.
I have a question: In this procedure, I would like to leave Linux in the internal memory, what would it be like to do this and leave it as a single system instead of Android?
And congratulations

be.sign said:
WOW! I was in the last days researching something about it because I found this machine stopped and it has a good relative hardware to run light applications, really a waste not to have more updates.
I have a question: In this procedure, I would like to leave Linux in the internal memory, what would it be like to do this and leave it as a single system instead of Android?
And congratulations
Click to expand...
Click to collapse
Having the PostmarketOS system in internal memory is harder and more difficult. You cannot install it on the bigger partition (the 30 GB one), I once tried and almost bricked my tablet because fails to boot due to media/ symlinks.
Unfortunately, you have to install it on /dev/block/mmcblk0p1 (533 MB partition).
I'm trying to make an usable small desktop image for /dev/block/mmcblk0p1 , XFCE is too big for that.
Nevertheless, you can enter recovery mode, do a Factory Reset and wipe Internal Memory to delete Android; then boot Linux from SDCard and use all available space to store your files.
If you want to make your image yourself, please look at https://wiki.postmarketos.org/wiki/Installation_guide and https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101)

be.sign said:
WOW! I was in the last days researching something about it because I found this machine stopped and it has a good relative hardware to run light applications, really a waste not to have more updates.
I have a question: In this procedure, I would like to leave Linux in the internal memory, what would it be like to do this and leave it as a single system instead of Android?
And congratulations
Click to expand...
Click to collapse
EDIT: A mini JWM image is available for download. It has the size to fit in the Asus TF101 first partition (/dev/block/mmcblk0p1). Download here: https://downloads.sourceforge.net/project/tf101-linux-images/postmarketOS/minijwm-postmarketOS-TF101.zip
Then execute exactly the following commands:
Code:
$ unzip minijwm-postmarketOS-TF101.zip
$ cd minijwm-postmarketOS-TF101
$ adb push blob-asus-tf101 /cache
$ adb push minijwm-tf101.img /sdcard
$ adb shell
# dd if=/cache/blob-asus-tf101 of=/dev/block/mmcblk0p4
# dd if=/sdcard/minijwm-tf101.img of=/dev/block/mmcblk0p1

Hello, thanks a lot for your sharing
I have an error with the XFCE image. When in try to boot from an external SDCard, following message occurs : "Initramfs-extras not found".
It work's without any problem when i boot from a custom built flashed on internal storage.
Do you have an idea from the causes ?

Raphzer said:
Hello, thanks a lot for your sharing
I have an error with the XFCE image. When in try to boot from an external SDCard, following message occurs : "Initramfs-extras not found".
It work's without any problem when i boot from a custom built flashed on internal storage.
Do you have an idea from the causes ?
Click to expand...
Click to collapse
This means that initramfs-asus-tf101-extra file is missing from pmOS_boot partition. All files located in this partition are strictly required.
EDIT: Btw, now I have download the XFCE image from sourceforge, flashed it into a new SD Card and boots fine.

aat596 said:
This means that initramfs-asus-tf101-extra file is missing from pmOS_boot partition. All files located in this partition are strictly required.
EDIT: Btw, now I have download the XFCE image from sourceforge, flashed it into a new SD Card and boots fine.
Click to expand...
Click to collapse
I don't understand why it doesn't work with sdcard. I have tried to flash my working build on the sdcard and the same error occurs
No file are missing on the sdcard, very strange.

Raphzer said:
I don't understand why it doesn't work with sdcard. I have tried to flash my working build on the sdcard and the same error occurs
No file are missing on the sdcard, very strange.
Click to expand...
Click to collapse
If it's your own working build then try these steps:
Code:
$ sudo pmbootstrap init (select asus-tf101 device, select [I]none[/I] when prompting graphical interface)
$ sudo pmbootstrap install && sudo pmbootstrap export
$ sudo dd if=/tmp/postmarketOS-export/asus-tf101.img of=/path/of/sdcard status=progress
$ adb push /tmp/postmarketOS-export/blob-asus-tf101 /cache
$ adb shell
# dd if=/cache/blob-asus-tf101 of=/dev/block/mmcblk0p4
And then insert your sdcard and reboot.
Hope this helps. I have extracted it from https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101). The only difference is flashing onto internal memory or the sd card.
EDIT: Are you using a reliable SD Card (Kingston, SanDisk, ...)? It could lead to random errors or not identify it if not.

This is what i did :/
Yep,i used this sdcard on a raspberrypi before.
I think he problem come from partition label name. As i have flash everything on internal memory and sdcard, i have 2 partition named pmos_boot. In the initramfs init script, there is multiple references to label name especially for loading initramfs-extras.
I will do some tests in that way.

Raphzer said:
This is what i did :/
Yep,i used this sdcard on a raspberrypi before.
I think he problem come from partition label name. As i have flash everything on internal memory and sdcard, i have 2 partition named pmos_boot. In the initramfs init script, there is multiple references to label name especially for loading initramfs-extras.
I will do some tests in that way.
Click to expand...
Click to collapse
Yes, it could be the reason. If you run into multiple problems, try to format /system in TWRP and then try it again with only the SD Card.
Btw, what version is your TF101? SBKv1 or SBKv2? I have SBKv1, that could be another problem (but I'm not sure, as the SD Card is partition-independent, and the kernel blob file is compatible for both versions)

Very nice image !
Just tested and looks very promising.
USB mouse and keyboard gets detected but don't work.

oink666 said:
Just tested and looks very promising.
USB mouse and keyboard gets detected but don't work.
Click to expand...
Click to collapse
Yep, that's one of the things mentioned in the TODO list in my guide (look at nearly the end)
We have to compile xf86-mtrack-driver to get it working (there's no such driver in Alpine repos)
I lack a bit of C knowledge to get it working (because it fails when compiling), so help is appreciated

Awesome work.
Any chance of dual boot?
Thank you

riptide981 said:
Awesome work.
Any chance of dual boot?
Thank you
Click to expand...
Click to collapse
You can only dual boot if you have installed postmarketOS in your microSD or SD Card. If not, you (probably) have to wipe your partition where postmarketOS is located for booting Android again.
Well, the easiest way to do dual-boot is this:
In the sdcard folder or whatever folder you want, put the Android ROM zip and PostmarketOS' kernel zip.
The Android ROM (I'm using timduru's ROM: https://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496) can be downloaded here: https://downloads.timduru.org/android/tf101/K.A.T/KatKiss/6.0/dev/KatKiss-6.0_034.zip
The PostmarketOS' kernel zip can be downloaded here: https://github.com/antonialoytorrens/TF101-linux-images/raw/master/postmarketOS/kernel_zip/PostmarketOS-kernel-3.1.10-15.zip
If you want Android, go to recovery and flash timduru's ROM.
If you want PostmarketOS, go to recovery and flash my kernel zip (please, disable signature verification when flashing)

XFCE 2.0
A newer XFCE image is available to download. Download it here: https://sourceforge.net/projects/tf101-linux-images/files/postmarketOS/xfce-postmarketOS-TF101-v2.0.zip
A little screenshot:
Notes about this release:
v2.0
- Changed icons (https://github.com/vinceliuice/vimix-icon-theme) and GTK (https://github.com/vinceliuice/vimix-gtk-themes) of XFCE. Now it is a modern XFCE.
- Removed second panel to save space.
- The XFCE Whiskermenu does not close when typing in onboard.
· Other things that will be included in the next release:
- Make a desktop shortcut opening a browser linking this XDA thread.
- Try to get trackpad working
v1.0
- Initial Release

Cool stuff - i tried the latest v2.0 image but ran into some issues:
If I have the keyboard docked it won't boot - it ends up with a blinking cursor top left of the screen and a bunch of errors are shown repeatedly during bootup.
Without the keyboard it boots correctly - keyboard wont work if attaching the keyboard after the system is up.
https://photos.google.com/share/AF1...?key=UUFNdVNfZ3N6X0ZOX054eDJLYWxWd0tPYThCV1dR
Any idea on what I could try to get this going?

gh05tface said:
Cool stuff - i tried the latest v2.0 image but ran into some issues:
If I have the keyboard docked it won't boot - it ends up with a blinking cursor top left of the screen and a bunch of errors are shown repeatedly during bootup.
Without the keyboard it boots correctly - keyboard wont work if attaching the keyboard after the system is up.
https://photos.google.com/share/AF1...?key=UUFNdVNfZ3N6X0ZOX054eDJLYWxWd0tPYThCV1dR
Any idea on what I could try to get this going?
Click to expand...
Click to collapse
I have just redownloaded zip file from sourceforge and I don't have this problem, so I don't know what it could be...
But there are some questions I would like to ask you:
- Does your keyboard work on Android? You can test it by flashing Timduru's Android image (https://downloads.timduru.org/android/tf101/K.A.T/KatKiss/6.0/dev/KatKiss-6.0_034.zip).
- Have you tried to do your own XFCE from scratch? https://github.com/antonialoytorrens/TF101-linux-images#doing-xfce-from-scratch. Hope this works, otherwise a patch for this kernel is needed.
- By the way, what version is your TF101? SBKv1 or SBKv2? I have SBKv1.