@stenstorp
Yeah. I’ve got my fault - I’ve been doing it on Galaxy Tab 2 10.1
Just not noticed that you are using galaxy NOTE (because of the name of article)
hey hey!
i have a european Tab 2 7.0 (P3110), running some custom linage OS and probably CWM as well. Would this work on it? if so, what would i need to modify?
i guess the 10.1 and 7.0 are using the same SoC, so it shouldn’t be that big of an issue.
thanks!
Sorry about the late reply, unfortunately this guide will not work for the tab 2. The kernel is specific for the Tab 1 10.1".
I have found and old guide from 2013 to get Ubuntu touch working on your device here: https://forum.xda-developers.com/showthread.php?p=40470153#post40470153 However, the download links are dead. It’s also in the ‘Seemingly abandoned’ list on the Ubuntu touch device list: https://wiki.ubuntu.com/Touch/Devices. I would search further but I don’t have the tablet to test on.
It seems that it is possible but I’m afraid I can’t help you. Best of luck though!
Hey, thanks you for this fantastic tutorial since I’ve been able to compile and boot myself the kernel but I have some problem with that.
The problem I’ve noticed in my n8000 are that in Debian 7, Wi-Fi and Bluetooth don’t work and I can’t make appear xvkbd at login screen, in Debian 8 Wi-Fi and xvkbd work but Bluetooth still doesn’t , what have you done to make it work? I’ve heard about some tricks with valgrind but still can’t find any devices. Thanks for your help!
Awesome! Finding this guide, and updated it’s awesome to me.
I have a SGN 10.1 N8013 and I will try it to follow all this steps.
It’s time to bring it to a new life with Linux.
A question? can I use some other distro to do this (in a near future)? Like a Slackware?
Thank you once more for this post.
After I try I will get back to tell how was it the experience.
See ya guys.
Regards.
If I make a virtualbox with debian (8) jessie it means I could update the kernel to version 4?
Can I try to do this update (like instructed here: https://gist.github.com/minazou67/4bf63b463347558f3f01) and continue follow this guide?
Unfortunately I don’t think so. The kernel for the SGT contains drivers not found in upstream kernels. This is the main reason it’s only on Jessie. Newer distros require newer kernels.
just for learning, there is a way to list the drivers used by SGT?
And just to record, I have a Galaxy Note 10.1 N8013 (https://www.samsung.com/us/support/owners/product/galaxy-note-10-1-wi-fi)
In posts above I see the N8013 citation, but don’t understand why referenced as SGT… so I am just want make sure…
So… If it’s necessary to keep the release fixed on ubuntu 14.04 (or debian 8 jessie) no problem if I make a virtualbox with minimal ubuntu 14.04 iso and after make it the installation(your guide) works, gradatively install other packages, like x-window, i3wm etc…
thanks for your response
Regards
It can be done. You need to get the upstream source for the kernel version being used and do a diff on the tree. I have tried this but there are a number of differences, it would take a lot of time and effort to port those to a newer kernel.
I’ve always seen it refered to as the Samsung Galaxy Tab 10.1, hence SGT.
I don’t have enough knowledge about Kernel developing, but, for learning again, it’s just a lot of effort to fix differences or there will be dependencies to look and compile to make this fixes work?
when I say:
I was asking it is possible to do this gradatively installations or not a good approach?
Another curiosity: I always see as solutions Debian or Ubuntu.
But I remember that centos 7 use Kernel version 3.x.
It’s possible to use too?
Thanks for the reply and sorry for my rust english.
Regards.
You are going to be dealng with ABI changes and what not. It is not worth the effort. The better thing to do would be to run the most recent working image for your hardware and compile the newest versions of software that you want to run on that distro version. Things that require new kernels are out of the cards if the drivers are closed source, period.
In regards to GNU/Linux distros, you can use what you want. The thing is that Debian is a universal OS (runs on the most CPU architectures) and Ubuntu is based on Debian Unstable plus Canonical’s own tweaks. Ubuntu has one of the largest user support communities.
If you are looking at CentOS, then you are better off just running Fedora.
Hi Mastic_Warrior, thanks for your reply.
Actually I would like to use slackware in my tablet.
But I think in terms of usability it would be mandatory to have wi-fi working and would be good to have keyboard dock working too 
At moment, my galaxy note 10.1 n8013 it’s not root.
So, I start to follow the link to root in this guide and I see most steps use fastboot tool .
So I download bootloader and recovery images from https://desktop.firmware.mobi/ (because cf auto root recomended to do so.)
My machine is an ubuntu 18.04.
adb tool find my tablet, no problem.
but fastboot not. I try various solutions, but simply nothing happen.
Finally, I found a page that uses adb to do everything, meaning: flash bootloader and recovery just using adb.
This would be my next step.
After that I would use virtualbox to build my image, but I still not solve what image would be.
If debian 8, ubuntu 14, or even ubuntu 18 or who knows, be brave and try slackware 14.
Someday I willl decide and make it.
Regards,
Looking in http://docs.slackware.com/howtos:hardware:arm:start
I found there is Slackware 14.2 for HummingBoard (http://docs.slackware.com/howtos:hardware:arm:hummingboard) and that uses the same CPU inside in my n8013 (armv7/Cortex-A9)
That’s a good thing right?
Using the kernel and recovery provide by desktop.firmware.mobi
And the minirootfs (http://slackware.uk/slackwarearm/slackwarearm-devtools/minirootfs/roots/)
With this instructions (http://slackware.uk/slackwarearm/slackwarearm-devtools/minirootfs/README.txt)
Should be give me some funcionality I list in my previous post.
I think now I decide what to do… But first rooting my n8013 
Regartds,
You can probably get into fastboot manually by turning the tablet off and pressing and holding power+vol down at the same time. Then cycle through boot options with the volume buttons. Power button is select.
I discover that my N8013 don’t have a fastboot mode, instead has a download mode.
So, the only way in Linux (looking on web) is to use heimdall (https://glassechidna.com.au/heimdall/)
So I used, flash boot and recovery and I expected this root my n8013, but don’t.
Now I see that what miss is to download CF-Auto-Root ( I just download boot.img and recovery.img)
I will try heimdall once more, but now include the CF-Auto-Root
til next
Regards
1 Like
I dont know much about that tablet, but if you can get custom recovery options on it like TWRP you could have it root the fs for you.
I just came across this article and was wondering if anyone has done a similar article for the Samsung Galaxy Tab 2 (GT-P5113)…? I use my Tab 2 as a monitor attached to my RC Transmitter while flying my 500mm Drone Quad-copter w/Telemetry… It would be advantageous to me to have Linux on my Tab 2 instead of carrying my Dell Laptop along to make adjustments through QGroundControl… Thanks in Advance,
James…
This is closed as it is outside the revived thread guidelines. Feel free to create a fresh topic, or PM one of the Leaders if you think this was incorrectly closed. See here for more info.