Linux on nvidia shield

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

linux-shield / shield-root Public archive

Basic rooting method for SHIELD

License

linux-shield/shield-root

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Sign In Required

Please sign in to use Codespaces.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

Root for NVIDIA SHIELD & Tegra Note 7

WARNING: this root method will not work with Android 5.0 (Lollipop) and later images. Generally speaking this method should be considered obsolete, using SuperSU is preferred: http://forum.xda-developers.com/showthread.php?t=1538053

This rooting method for NVIDIA SHIELD and Tegra Note 7 uses a Linux kernel and a simple ramdisk to install SuperSU [1] on an unlocked device. It should work with any Android version.

This method does not require you to install a custom recovery, which means you will be able to receive and apply OTA updates. However, it also means you will likely need to re-root your device after each update.

Obligatory Scary Disclaimer

Please read this section at least 3 times before proceeding.

This is not for the faint of heart or the clueless. This method comes without any warranty and you take sole responsibility for anything bad that might happen. You really want to make sure that you understand this document fully and consider the consequences of unlocking and rooting your device before proceeding. Following this guide will irreversibly VOID YOUR WARRANTY and ERASE YOUR USER DATA. There is no way back — your device will be marked as having been unlocked and WARRANTY-VOID FOREVER, even if you re-lock the bootloader afterwards. Also, unlocking your device will leave you more vulnerable to malware and errors that can potentially damage it and turn your new Tegra Note into a breadboard and your shiny SHIELD into a slightly oversized belt buckle.

Do not expect any kind of support from anyone if you don’t understand this guide or if something goes wrong. It goes without saying that everything said here is unofficial and unsupported by NVIDIA.

You have been warned! If you are happy with your device, it’s probably better to stop now.

Getting root is done in two steps: first, we will unlock the bootloader, then boot a custom OS image that will add SuperSU to our Android system partition.

If your device is already unlocked, you can skip this section. Otherwise, remember that you only need to perform this operation the first time you root your device (i.e. you don’t need to do it again when you re-root after an OTA).

SHIELD and Tegra Note 7 ship with an unlockable bootloader. The bootloader is locked by default, which prevents anyone (including yourself) from booting custom OSes and changing system partitions to potentially obtain extra privileges. This is a significant security feature: in the event that your device gets stolen, an attacker will not be able to retrieve your personal data or use your device if your lock screen has a password set.

By unlocking the bootloader, you allow anyone with physical access to your device to boot custom images and flash system partitions. This opens the way for an attacker to access your personal information or physically damage your device. For this reason, unlocking the bootloader will erase all your personal data like a factory reset does (so a potential thief cannot get it) and will also void your warranty.

If you know you really, really want to take these risks, here is how you unlock the bootloader.

1. Switch your device off (long press the power button and select Power off ).
2. For SHIELD: power your SHIELD on while maintaining the back and home buttons pressed (these are the two buttons that lie under the big NVIDIA-logo button, on its left and right). Release them once you see the bootloader screen. For TN7: power the tablet on while maintaining the volume up button pressed. Release it once you see the bootloader screen. Then select Fastboot Protocol and press the power button. If the above does not work, try enabling USB debugging in the Developer options from Android, then issue adb reboot-bootloader while your device is connected to your PC via USB.
3. Connect your device to your computer using a USB cable.
4. On your computer, enter the following command:

Now your bootloader is unlocked, but you still don’t have root access. For this, we need to install SuperSU, and we will do so by booting a custom Linux image that will install it for us.

Note that you rooting may result in removing the Google Maps and Youtube applications installed on your system partition. If this happens, you can reinstall them from the Play Store.

1. Download the boot image corresponding to your device: For SHIELD:https://github.com/linux-shield/shield-root/blob/master/root_shield.img?raw=trueFor TN7:https://github.com/linux-shield/shield-root/blob/master/root_tn7.img?raw=true
2. For SHIELD: power your SHIELD on while maintaining the back and home buttons pressed (these are the two buttons that lie under the big NVIDIA-logo button, on its left and right). Release them once you see the bootloader screen. For TN7: power the tablet on while maintaining the volume up button pressed. Release it once you see the bootloader screen. Then select Fastboot Protocol and press the power button. If the above does not work, try enabling USB debugging in the Developer options from Android, then issue adb reboot-bootloader while your device is connected to your PC via USB.
3. Connect your device to your computer using a USB cable
4. On your computer, navigate into the directory containing the downloaded image and enter the following command: For SHIELD: fastboot boot root_shield.img For TN7: fastboot boot root_tn7.img

The image will be downloaded and started. You will see 4 penguins on your screen, and the root procedure will start. It should take a few seconds to complete. Once it is done, your device will reboot. Congratulations, you are rooted!

For some unknown reason USB debugging in Developer options might become unchecked after rooting. You will need to re-check it if you want to use ADB.

It is safe to perform the rooting operation as many times as you want (e.g. after an OTA). Your user data will not be erased by rooting itself, it is the act of unlocking the bootloader that does.

If for some reason you want to unroot and re-lock your device, this is possible. It won’t bring your warranty back, but you will at least enjoy the security benefits of a locked device.

Unrooting the device can be done by running the SuperSU application, going into its settings, and choosing Full unroot . This will remove all traces of SuperSU.

Then you will likely want to relock your device. Enter the bootloader again, connect your device to your computer via a USB cable, and issue the following command:

Then on the screen, select Lock . Your bootloader will be locked again. Note that your warranty is not coming back — that red message in the bootloader menu is here to stay forever.

This method is completely unofficial and you are on your own. Do not expect any support whatsoever from anyone. Don’t do this if you don’t understand and accept the potential consequences.

If the SuperSU application icon is not visible in the launcher, just install it from the Play Store. Look for «eu.chainfire.supersu» to make sure you are picking the right package.

If you see no reaction when trying to run «su» from adb the first time, run the SuperSU application and try again.

The necessary binaries are already in this repository, but if you want to build things by yourself, here is how you do:

1. Compile a bootable kernel zImage from this project: https://github.com/linux-shield/kernel, and copy it into this directory. The binary included replaces the ignore_loglevel kernel command-line option with loglevel=0 to remove kernel log messages.
2. Also copy the tegra114-roth.dtb and tegra114-tn7.dtb files into this directory.
3. Run make into the present project to rebuild it. The SuperSU binaries are in the rootkit subdirectory and the script that performs rooting is /init .

You can now run fastboot boot to boot on the images you built yourself.

This binary release uses an unmodified version of Busybox, which source code can be downloaded at https://github.com/linux-shield/busybox. User-space is built from the examples/bootfloppy directory with slight modifications to use mdev , mount filesystems, and install SuperSU.

This package, as Busybox, is distributed under the terms of the GNU General Public License, version 2. See the LICENSE file for details.

SuperSU is redistributed in its free, unmodified version as kindly permitted by its author.

Источник

Running Ubuntu natively on Nvidia Shield Tablet

Thanks to Nvidia’s Linux4Tegra and work of Bogdacutu and Steel01, as of today I’m running desktop Ubuntu on my Shield Tablet. And it works surprisingly well. Except some tablet-specific hardware like the modem, accelerometers and such, of course.

All it takes is to install MultiROM, patch the kernel and install the appropriate Linux4Tegra installation archive next to existing Android system and there you go:

You can even reasonably play OpenTTD. Amazing. Finally this thing beats the N900. Also this way you can get X forwarding working. Just open remote connection with ssh -CX @ and voilà, you can run Eagle on your tablet. Tablet seems to be fast enough for this kind of use, in my case the bottleneck seems to be network connection (even with the compression switched on). I should start looking for some ethernet adapter…

There seem to be some issues with keyboard, or more precisely the absence of it. But since bluetooth works, you can connect wireless keyboard and there is no reason to fiddle with the imperfect onscreen keyboard.

The touch screen works reasonably well. You only get what seems to be single touch, or more precisely mouse emulation. I tried to dump touch events from the driver by evtest, but the touchscreen stopped responding at all.

Some other problems with touchscreen include breakage with system update (you need to manually switch X and Y axes in Xorg config files after running apt-get update, apt-get upgrade) and the axes sometimes switch incorrectly after changing screen orientation as well and get fixed after reboot.

Alright, let’s get back to playing with this little wonder.

1 thought on “ Running Ubuntu natively on Nvidia Shield Tablet ”

Hi there, I am having problems installing it on my NVIDIA shield tablet. I can’t seem to find a MultiROM TWRP image that works. When I reboot onto recovery mode, it crashes. I can install any other TWRP image, and works fine, but it doesn’t have the multirom application in it. Any help is very appreciated

Источник

AIGLX на NVIDIA Shield Tablet

Вот и наступил тот день, когда можно поставить Linux на планшет и запускать полноценные OpenGL-приложения.
Однако ещё больше порадовало, что работает аппаратная отрисовка не только в локальных arm-приложениях, но и в x86, запущенных через транслятор от eltechs.
На скрине можно наблюдать arm-версию nvidia-settings и x86-версию glxgears. Никакой дополнительной настройки не потребовалось, aiglx (проброс gl через x11) работает из коробки.
Скрины с winecfg и xash3d, запущенными через транслятор.
http://en.zimagez.com/zimage/105710851080108410861082110110821088107210851072.
http://en.zimagez.com/zimage/105710851080108410861082110110821088107210851072.
производительность такой конфигурации не очень высока. Если нативно xash3d выдаёт больше 100 fps, то в exagear 30-60. В glxgears разницы с нативной версией нет.
Под wine же обламывается SetPixelFormat. Скорее всего надо патчить.
Система ubuntu пока не наладил suspend в ядре, потом, возможно, gentoo соберу.

Cool! А за порт, отдельный тебе респект, бро!

Porthos ★★★★★ ( 29.08.16 02:25:53 MSK )
Последнее исправление: Porthos 29.08.16 02:29:09 MSK (всего исправлений: 1)

Чего именно? Это готовая сборка болгеноса с XDA.
http://forum.xda-developers.com/shield-tablet/development/running-ubuntu-nati.
Драйвера от l4t.
Илм ты про Xash3D? Он тут для демонстрации аппаратного ускорения

Из-за первого сообщения подумал, что вы автор.

Источник