Ubuntu for N80xx - Galaxy Note 10.1 General

{
"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.

Related

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

[Linux] [DEV] [WIP]Backtrack 5 on the gtablet HYBRID. 7/18/11 1.2 BL kernel

6/13/12 update
updated links and some instructions.
I currently do not have time to do any work on this currently as i have been working 18+ hours a day. Hopefully if i ever get some time again I will continue it.
Jaybob413 built the kernel for 1.2 Bootloader. Link is posted below
Thanks jaybob413
*PLEASE READ AND UNDERSTAND EVERYTHING HERE BEFORE ATTEMPTING THIS*
BACKTRACK 5 IS running on the GTABLET in Hybrid mode!
http://www.youtube.com/watch?v=kJb3mwBhMik video up now =)
http://www.youtube.com/watch?v=be-9F_VzbHY Dual boot video
working
boots natively into backtrack
X11 desktop works
wifi
TOUCHSCREEN!!!!!
4 buttons. Search opens firefox, home opens users home dir, settings toggles the Onscreen keyboard, and back switches through virtual desktops.
Not Working
sound
bluetooth
battery stats
------------------------------------------------
I currently have this set up for windows. It can be done from linux but will link everything for windows in this post.
you must have ADB installed on windows working with the gtablet. see http://forum.xda-developers.com/showthread.php?t=902860
required files:
bt5.tar.xz http://d-h.st/YZ4
restore_droid-kern.zip http://dev-host.org/qsbz1s7xbebt/restore_droid-kern.zip
droid-kern_backup.zip http://dev-host.org/evmqb1yrd0tn/droid-kern_backup.zip
1.1 bootloader:
bt5kern-01-20110525.zip http://dev-host.org/s4d4pp1wvxx4/bt5kern-01-20110525.zip
1.2 bootloader: thanks jaybob413 for the 1.2 kernel.
http://forum.xda-developers.com/showpost.php?p=15703493&postcount=137
optional files:
nvidia_windows.zip http://dl.dropbox.com/u/4917587/nvflash_windows.zip
kernel config file http://dl.dropbox.com/u/4917587/config this file is only for reference. you do not have to download it or install it
the root password is "toor"
THIS MAY ERASE EVERYTHING ON YOUR TABLET!!!!
Do this at your own risk!! I take no responsibility for anything that happens to your tablet.
Start by installing your favorite ROM and kernel.
Make sure you have adb working and CWM installed
turn off the device then boot into recovery. (vol+ and power).
once in recovery you must format the EXTERNAL sdcard into ext3.
Code:
adb shell
parted /dev/block/mmcblk2
mkfs 1 ext2
confirm
exit
tune2fs -j /dev/block/mmcblk2p1 to format the external SDcard to ext3
mkdir /tmp/ext-sd
mount /dev/block/mmcblk2p1 /tmp/ext-sd/
exit adb and run
* this will take a long time *
Code:
on a linux box unxz bt5.tar.xz
adb push c:\path\to\bt5.tar /tmp/ext-sd/bt5.tar
adb shell
# cd /tmp/ext-sd/
tar xvf bt5.tar
rm bt5.tar
cd /
umount /tmp/ext-sd/
reboot the device into android and connect the INTERNAL sdcard to the computer to place files on to the sdcard.
make a directory called kernels on the sdcard and put the 3 zips from above in that folder.
bt5kern-01-20110525.zip
droid-kern_backup.zip
restore_droid-kern.zip
reboot into recovery and flash the
droid-kern_backup.zip this will create a backup of the android kernel. This will ONLY need to be done any time that you UPGRADE or CHANGE your android kernel.
once this is done you switch back and forth between android and backtrack with:
bt5kern-{date}.zip to boot into backtrack
restore_droid-kern.zip to boot into android
******* You do NOT have to wipe cache or anything when switching back and forth. Just flash whichever you want to boot into and you are done************
http://forum.xda-developers.com/showpost.php?p=16223052&postcount=139 WICD fix
Linux touchscreen drivers and settings
xf86-input-multitouch https://launchpad.net/debian/+archi...ut-multitouch_1.0~rc2+git20110312.orig.tar.gz
libmtdev1 http://ftp.de.debian.org/debian/pool/main/m/mtdev/mtdev_1.1.0.orig.tar.gz
************OLD WAY******************
How to install backtrack 5 to run on the gtablet with out gtab filesystem modification.
You must recreate the img file to be less then 4Gb. The img file is currently 4.6Gb. The new image created will be 2.9Gb. this is a vfat limitation
this has been tested on vegan 5.1 with the gtab/zpad 1.4 OC kernel. Its still a little buggy with random reboots depending on what your are doing but it is a WIP
The kernel must have loop devices support. Also looks like the kernel needs swap functionality to be enabled.
I could release the img file that has already been created but backtrack would prefer that people not release other images so this will allow you to create your own after downloading it from them so it remains trusted.
you either need:
linux with ADB working on the gtab
OR
windows with ADB and access to a linux box with about 10gb of free space.
Backup your sdcard because it needs to be repartitioned with CWM.
In CWM under advanced > Partition SD Card > 2048 > 128
download the arm version of backtrack from www.backtrack-linux.org/downloads/
and extract the files. you need to copy the bt5.img.gz to the linux box and do all the following steps.
make a working directory for all the files, copy and gunzip the img file
Code:
mkdir bt5
cp /root/bt5.img.gz bt5
cd bt5
gunzip bt5.img.gz
rename the old bt5.img to something else and create a new image that fits onto the gtabs vfat filesystem.
then create 2 directory to mount each image and copy the files over to the new img file.
Code:
mv bt5.img bt5.old.img
dd if=/dev/zero of=bt5.img bs=4k count=900000
mke2fs -F -i 8192 bt5.img
mkdir bt5old bt5new
mount -o loop bt5.old.img bt5old
mount -o loop bt5.img bt5new
cd bt5old
cp -rp * ../bt5new
*****************************************
since the system does not go through the full startup scripts once you run "sh bootbt" you must run /etc/rc.local from the chroot to start the vnc server if you add these lines otherwise you must type them each time.
Code:
cd ../bt5new/
vi etc/rc.local and add the following 2 lines before the exit 0 line
export USER=root
/usr/bin/startvnc
save the file and then continue on.
also you can edit /usr/bin/startvnc and modify the screensize to fit the tablet
the gtablet is 1024x600
Code:
vncserver -geometry 1024x600
*****************************************
after all files have been copied over you just unmount the 2 directories and gzip the new image.
Code:
cd ..
(you should now be in the directory with the 2 img files and 2 directories)
umount bt5old
umount bt5new
gzip bt5.img
edit the bootbt file and change the line
Code:
mount -o remount,rw /dev/block/mmcblk0p5 /system
with
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
*** this needs to be changed to whatever your /system is on your tablet or phone if it is something other then the gtablet.
now copy this new bt5.img.gz file over to the directory where you got the original image from and then follow the instructions that are included with the download in the README file.
a good VNC viewer is located
http://code.google.com/p/android-vnc-viewer/downloads/list
and also install a terminal emulator so you can start Backtrack 5 from the device.
---BUGS---
running from a terminal emulator everything runs fine but running VNC gnome takes up way to much RAM currently. Looking at fluxbox and/or swap as a fix. causes the tablet to lock up and must be powered off by holding the power button.
---Thanks---
The Backtrack Team -- for coming up with an amazing security distro
The G-TabDevs Team -- for the vegan 5.1 Rom
Pershoot -- for maintaining the 1.4 kernel for the gtab and hopefully adding support for needed features =)
Sorry for the flash in the pictures
{
"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"
}
sorry for the noob question.....
where we need to run all the commands you have stated????
fauz33 said:
sorry for the noob question.....
where we need to run all the commands you have stated????
Click to expand...
Click to collapse
They must be run on a linux box. I bolded it just now in the first post. I would do it all and just release the gzip file but backtrack does not want that.
slimm609 said:
They must be run on a linux box. I bolded it just now in the first post. I would do it all and just release the gzip file but backtrack does not want that.
Click to expand...
Click to collapse
sorry....
i have googled it for hours.....
what is mean by linux box??
fauz33 said:
sorry....
i have googled it for hours.....
what is mean by linux box??
Click to expand...
Click to collapse
_almost_ any version of linux installed on a computer (laptop or desktop).
you need about 8-10gb of free space after linux is installed.
like fedora, centOS, ubuntu, suse, slackware, etc.
90+% of the versions on this site would work www.distrowatch.com
I'll talk to Muts and see if he will allow the gzip. Maybe if it is maintained by you but released by them they might consider it.
These instructions are for running BT5 in a shell, not actually installing it as the working OS on the gtablet - right?
Similar to:
http://www.backtrack-linux.org/forums/backtrack-5-how-tos/40376-%5Bhow-%5D-backtrack-5-motorola-xoom-gnome-ui-via-tightvncserver.html
runner989 said:
I'll talk to Muts and see if he will allow the gzip. Maybe if it is maintained by you but released by them they might consider it.
These instructions are for running BT5 in a shell, not actually installing it as the working OS on the gtablet - right?
Similar to:
http://www.backtrack-linux.org/forums/backtrack-5-how-tos/40376-%5Bhow-%5D-backtrack-5-motorola-xoom-gnome-ui-via-tightvncserver.html
Click to expand...
Click to collapse
This runs the same way that it does on the Xoom. Just making it fit onto the gtab and Evo 4g
here is CHS (runner989)
Is packet injection working with the wireless adapter?
kdj67f said:
Is packet injection working with the wireless adapter?
Click to expand...
Click to collapse
most of the tools for wireless were removed when they created the arm version.
I am going to try and compile them and see if they work when i get a chance (hopefully soon)
Ugh! That sucks! I did not know they did that. Since the gtablet has a USB port the USB wireless adapters (like the Alfa adapter) should work just as they do in the regular Backtrack builds.
slimm609 said:
most of the tools for wireless were removed when they created the arm version.
I am going to try and compile them and see if they work when i get a chance (hopefully soon)
Click to expand...
Click to collapse
runner989 said:
Ugh! That sucks! I did not know they did that. Since the gtablet has a USB port the USB wireless adapters (like the Alfa adapter) should work just as they do in the regular Backtrack builds.
Click to expand...
Click to collapse
The internal card is a broadcom 4329 so it should support everything also. have to wait and see.
Major progress made on booting native backtrack linux. Kernel boots but it missing a driver so it drops into a ramfs but getting close.
off to bed
I was so excited I forgot we run an arm processor! Good work to the devs on this. And although it was probably an ethical thing to remove all the wireless functions for ARM builds, It would be much handier than lugging around my old laptop with it's ancient battery that barely last 45 minutes under load.
Many thanks, I am subscribing. Just wish I could help
This is pretty awesome. Might want to check the debian or ubuntu ARM community to find out how the wireless drivers work there. I'm assuming our ARM runs in it's normal little indian, not ARMEB mode, right?
muqali said:
This is pretty awesome. Might want to check the debian or ubuntu ARM community to find out how the wireless drivers work there. I'm assuming our ARM runs in it's normal little indian, not ARMEB mode, right?
Click to expand...
Click to collapse
the wireless card is a broadcom 4329
slimm609 said:
the wireless card is a broadcom 4329
Click to expand...
Click to collapse
The driver source thread is http://forum.xda-developers.com/showthread.php?t=906628
wifi is working now. tested with wpa-psk
New files coming tomorrow with wifi included.
the touchscreen is seen by the system and xorg just need to find the right configuration for it to work
now trying to compile as a single touch device because Xorg does not support multi-touch displays
touchscreen is working. just working on calibration of it now. only single touch currently
This is awesome...
Sent from my Droid using XDA App

[n80xx] CyanogenMod 10.2 Dual Boot

{
"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"
}
For anyone interested, below are the steps for getting your device dual-booting with CyanogenMod 10.2.
Why?
I don't want to erase native firmware and want to give a try to CyanogenMod
I want to have both native and CM, because I like native Samsung S-Pen apps, but want to have more fresh Android too
I like experimenting - it's cool!
The Idea
Our Android device has 2 boot partitions - for normal boot, and to boot into recovery. If I want to boot CyanogenMod, I need to place its boot image instead one of those boot partitions. E.g. if I want to have both native firmware and cyanogen - then obviously I need to replace recovery partition. However I can do the backup of recovery and restore it later if needed.
But, I also need to place cyanogen system and data partitions somewhere. Putting it on the external sdcard makes CM working really slow, repartitioning internal memory might be good idea, but it is not so easy and is not necessary for experimenting. Thus I've created 2 image files and put it to native data partition (mmcblk0p12) to media folder, e.g. into internal sdcard, then changed cyanogen boot image to mount those image files on boot as system and data partitions.
Prerequisites:
Rooted Samsung Galaxy Note 10.1 2012 Edition
2GB of free disk space at internal sdcard
Recovery partition backup, because we are going to replace it with CyanogenMod boot image
Clear understanding of what you are doing, because you potentially can break your device
Downloads:
CM 10.2 boot image
CM 10.2 data partition image
CM 10.2 system partition image
Steps
This manual suggests that you are going to do the recovery backup to external sdcard and has native firmware which means that recovery partition is mmcblk0p6, data partition is mmcblk0p12 and internal sdcard is /mnt/sdcard folder (otherwise you need to change the commands appropriately and might need to fix cyanogen boot image too).
Download 3 files by the links above and upload to internal sdcard of your device. Connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to external sdcard to create recovery backup
cd /mnt/extSdCard
dd if=/dev/block/mmcblk0p6 of=./recovery.img
# go to internal sdcard folder
cd /mnt/sdcard
# unpack partition images - each is 1Gb of disk space
gunzip ./system.img.gz
gunzip ./data.img.gz
# write CM boot image to recovery partition
dd if=./cyanogen.img of=/dev/block/mmcblk0p6
# finish
exit
exit
Now you can reboot your device into recovery mode and see CyanogenMod booting.
Restoring native recovery:
If you got tired from CyanogenMod and/or would like to take back your recovery, please use the backup you've done before. Lets say it is placed on your external sdcard, then connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to the folder with recovery backup
cd /mnt/extSdCard
# write recovery image over recovery partition
dd if=./recovery.img of=/dev/block/mmcblk0p6
Please let me know If I missed anything in my steps.
P.S. What I've changed in Cyanogen boot.img to make it using img files instead of partitions in form of patch: View attachment cyanogen_boot_img.patch. It is also necessary to create /host folder in initrd folder tree.
wow!!
it's really hard to be done xD
i thought it will be as easy as it was on my old Galaxy S2
all what i needed to do is to restart the phone and press home to boot to second Rom
i hope it's going to be easier soon
and thank you for you efforts toward our device Development
MoNsTeRmUk said:
wow!!
it's really hard to be done xD
Click to expand...
Click to collapse
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps
X-Stranger said:
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps
Click to expand...
Click to collapse
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support
MoNsTeRmUk said:
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support
Click to expand...
Click to collapse
Thanks for kind words Actually you don't need to have the computer to change ROM, you can type commands from terminal emulator directly from Android. I'm also thinking about creating small Android app which can be installed to each ROM and will be able to switch boot partition within one click.
Thanks for this superb work. Can't download last file ?
Please if can make someone flashable zip it would be great I am a noob but I want try this thanks again
Sent from my GT-N8000 using Tapatalk HD
other roms
Can I do this this with another rom
maro_X said:
Can I do this this with another rom
Click to expand...
Click to collapse
It is possible, but your another rom must be specially modified for this.
What rom are you talking about exactly?
Multi-boot solution
I've tired of writing images to boot partition every time I want to switch between native firmware and Cyanogen, so decided to compose a little program that I was talking before. So let me introduce you N8xx Boot Manager!
The idea:
You put your boot images files to some folder on your sdcard, lets say to /mnt/extSdCard/images/boot
And recovery boot images to /mnt/extSdCard/images/recovery
Now you run Boot Manager and select what you want to boot as normal boot or as recovery
As soon as you selected it, the application asks you if you would like to write this image to the appropriate partition (boot or recovery)
After successful writing it will ask you for booting from that partition, e.g. propose to reboot into your another rom or recovery
For sure all the settings like path where to keep images and boot/recovery partition names can be fixed appropriately to your device at the Settings tab
For sure the application requires root permissions, e.g. your device must be rooted. You can also check this from Settings tab
The application file: View attachment bootmanager-1.0.apk - feel free to install it to your device and use posting me bug reports
P.S. The only thing I've forgotten - the button to create native boot image file backup You still need to do it manually, sorry Hopefully in next release, if there be people interested in N8xx Boot Manager
P.P.S. Generally this program can be used for any device - just put correct images and correct boot partition names
P.P.P.S. Why N8xx and not N8xxx or N80xx? Because I've missed one symbol when typed application name in Android Studio and was too lazy to change that later :laugh:
N80xx Boot Manager
Updated version of N80xx Boot Manager: View attachment bootmanager-1.1.apk
Changelog:
Fixed application name
Fixed images path detection when no settings were changes
Added "Backup boot partiton" and "Backup recovery partition" buttons
Thus, now to install CM 10.2 as dual boot you don't need to go to ADB or terminal - just upload 3 img files to your device proper locations, installl boot manager apk, create stock boot/recovery partitions backup, then select what you want to boot and boot to that rom!
P.S. Going to update first post of this thread with steps based on Boot Manager, just would be nice if someone confirm that it works.
swamimahesh said:
Can't download last file
Click to expand...
Click to collapse
Re-uploaded.
I love u man
Finally alittle love for our device :crying:
Do I have to reinstall apps when booting to cm?
edit: I dont really understand the first step when you extract data and system.img. Can you explain more clearly the procedure?
edit2: did anyone do this dualboot successfully?
data.img.gz
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:
I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk
netj said:
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:
Click to expand...
Click to collapse
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment data.img.gz and let me know if it works for you.
muop_92 said:
I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk
Click to expand...
Click to collapse
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.
X-Stranger said:
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.
Click to expand...
Click to collapse
Where is /mnt ? I saw in my device only /storage/extSdCard
Sent from my GT-I8160 using Tapatalk 2
muop_92 said:
Where is /mnt ? I saw in my device only /storage/extSdCard
Click to expand...
Click to collapse
It's the same. External sdcard is available on both these paths as far as I know. You can change it otherwise in application settings tab.
Ok !
X-Stranger said:
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment 2519204 and let me know if it works for you.
Click to expand...
Click to collapse
Hi,
It's Ok !
Thanks !
I have just modify the paths :
dd if=/dev/mmcblk0p6 of=./recovery.img --> dd if=/dev/block/mmcblk0p6 of=./recovery.img
dd if=./cyanogen.img of=/dev/mmcblk0p6 --> dd if=./cyanogen.img of=/dev/block/mmcblk0p6
:good:

[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

[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.

Categories

Resources