Related
Will it be possible to boot from external USB flash or hdd?
Seems xoom already support bootloader unlocking - details here - http://forum.xda-developers.com/showthread.php?t=967065&page=2
Will it be possible to do the same with a500
Bump this...I'm thinking about getting one.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Just thinking, that now when we can flash custom roms. Would it be possible to code grub like bootmanager?
I know its not the same layout.but...the nook color is able to boot into different Roms ect. While holding the n while booting.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Im no expert but the a500 doesn't have an unlocked bootloader so until someone can crack it (if that's even possible) or Acer unlocks it we're sol in this dept. At least that's what I've garnered from reading these forums
Sent from my Acer Iconia Tab A500 using XDA Premium App
You can flash custom kernel with custom ramdisk instead of recovery and force the external root device in the command line.. Although that kinda sucks. I'm booting my test system from external micro sd card now (will release sources a bit later, need to push a lot of traffic) but I want to port uboot though.
sp3dev said:
You can flash custom kernel with custom ramdisk instead of recovery and force the external root device in the command line.. Although that kinda sucks. I'm booting my test system from external micro sd card now (will release sources a bit later, need to push a lot of traffic) but I want to port uboot though.
Click to expand...
Click to collapse
Will be great if you can reveal bit more details. I'm looking into booting ubuntu or other distro without sacrificing the existing android system.
I'm still not sure do we have 2 kernels one in the main boot and one for recovery or we have one kernel that gets different rootfs - either normal boot or recovery
Will be happy if someone can clarify a bit more onto this.
yodor said:
Will be great if you can reveal bit more details. I'm looking into booting ubuntu or other distro without sacrificing the existing android system.
I'm still not sure do we have 2 kernels one in the main boot and one for recovery or we have one kernel that gets different rootfs - either normal boot or recovery
Will be happy if someone can clarify a bit more onto this.
Click to expand...
Click to collapse
My kernel tree is here - https://github.com/astarasikov/iconia-gnu-kernel
My plan is to port iconia to chromium tree and possibly integrate into mainline tree and get rid of proprietary stuff (i.e., make camera work via v4l2)
Right now, the framebuffer, mmc card and usb host are working and I'm struggling to make usb client and touchscreen to work with mainline drivers
And yes - we have two kernels, 'normal' and recovery. So we can ditch recovery and put our custom kernel there. Sure that's not good - ideally we should port uboot and repartition internal storage to install linux there but we need to get basic hardware working first
sp3dev said:
My kernel tree is here - https://github.com/astarasikov/iconia-gnu-kernel
My plan is to port iconia to chromium tree and possibly integrate into mainline tree and get rid of proprietary stuff (i.e., make camera work via v4l2)
Right now, the framebuffer, mmc card and usb host are working and I'm struggling to make usb client and touchscreen to work with mainline drivers
And yes - we have two kernels, 'normal' and recovery. So we can ditch recovery and put our custom kernel there. Sure that's not good - ideally we should port uboot and repartition internal storage to install linux there but we need to get basic hardware working first
Click to expand...
Click to collapse
Great thinking. Thank you for your hard work.
So is it not possible to install second boot loader in the recovery area like u-boot or lilo, that will give us ability to boot further from external hdd or usb flash or else.
In other words, we have locked boot loader but can it be tricked like if it is loading a recovery kernel and in turn it loads other bootloader on top?
Ok, got something to brag about. The kernel in git has now usb client (cdc ethernet) and touchscreen (sic!) working. GNU/Linux is coming to our place
So, let's get linux installed natively on our Iconia.
As some of you I have been working on porting Iconia to chromeos 2.6.38 kernel (to get rid of Acer crappy moron-written drivers (well.. nothing personal, but most code written for commercial embedded devices is a pile of crap and you have to rewrite everything to update kernel or integrate upstream))
For now, I have hardcoded the kernel command line in the boot config to boot off /dev/mmcblk1p2 (that is, you must create ext4 (this is also hardcoded.. uhh)) second primary partition on your sd card with the root fs). For now, until all hardware is working fine and userland is ready, let's boot off micro sd. We don't have nvflash yet so let's leave repartitioning internal storage aside.
Flash the kernel image instead of boot.img to LNX or instead of recovery to SOS. And make sure to write your UID in a secure place before messing with the device - this is the only way to flash your device if you have checksum errors (you should contact sc2k in that case). Okay, even if you eff up here, there is still a way to get UID from a brick so take it easy. But if you do screw it, be prepared to work hard and use some command-line tools.
You should be able to use any armel rootfs. For X11, use fbdev driver and evdev for touchscreen.
For the proprietary NVIDIA accellerated drivers for X11, OpenGL ES and OpenMAX, download the nvidia-tegra package from AC100 PPA https://launchpad.net/~ac100/+archive/ppa (probably you have to manually download using this link http://ppa.launchpad.net/ac100/ppa/...dia-tegra_12-0ubuntu1~alpha1monson6_armel.deb as the package didn't show in aptitude for me after adding to sources.list.. or i was doing sth wrong) or the tarball from nvidia. A newer package of tegra drivers is available at https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-tegra. You may just add an alternative to mesa EGL/GLES library path via update-alternatives to always use nvidia libs.
precompiled kernel image [15 August 2012]
http://www.mediafire.com/?p32l949n2s7la43
xorg.conf
http://pastebin.com/0a6T6c18
Here is some video
http://www.youtube.com/watch?v=NlGHZ5VTAr8
And now - we need developers, developers, developers.
The git is https://github.com/astarasikov/iconia-gnu-kernel
The main branch is chromeos-2.6.38 that is more stable. The 3.0 branch is unstable (network traffic causes virtual memory trashing).
For now, the following stuff works
-Panel/framebuffer/backlight
-Touchscreen
-Internal eMMC
-microSD slot
-usb gadget
-usb host
-gpio keys/buttons [rotation switch acts as wifi/bluetooth power blocker. iirc, left position disables wireless, right - enables]
-charger
-battery
-shutdown
-LEDs
-bcm4329 wifi (don't forget to copy bcm4329-fullmac-4.bin to /lib/firmware/brcm and nvram.txt from android's /system/etc to the same dir as bcm4329-fullmac-4.txt) [causes lockups with 3.0 kernel]
-nct1008 temperature sensor for cpu throttling
-sound. external speakers and headphones.
-bcm4329 bluetooth. accessible at 115200 on /dev/ttyHS2. Look at http://htc-linux.org/wiki/index.php?title=Ubuntu/Leo/Bluetooth to get it running at higher speeds with proprietary firmware patches (hcd files from android)
-suspend. Although will probably drain a bit more power than android because mmc power is not disabled (due to a race condition in kernel. and because we have rootfs on micro sd). Two glitches are: sometimes, the device freezes for several seconds after suspend (will test later if playing with wifi clock fixes it) and fonts get corrupted after suspend if using proprietary nvidia X11 driver. [suspend works in 2.6.38 only]
-kxtf9 accelerometer
-mpu3050 gyroscope
-ak8975 magnetometer
The following stuff is broken or not implemented at all
-hdmi video. May be working but no one has tested. hdmi audio is not implemented.
-light sensor
-video cameras, focus, torch.
-gps. To turn on the chip, it should be enough to enable gpio 203 via sysfs. Unfortunately it uses the proprietary MEIF protocol which can probably be obtained from Nokia under NDA. And I don't feel like disassembling the whole megabyte of the gps daemon
-3G. I don't have the modem in my iconia. So I don't care. But should be easy to add.
And one notice for those who want to join in. I don't care if hardware works properly. I want 'beautiful' code. That is, please, when you make patches to add functionality, do not follow the path of corporate coders and do not invent custom interfaces and sysfs hacks. Use rfkill for bt/3g power control, for example. And don't be selfish - please share your patches and userland stuff.
TODO:
-fix framebuffer issues (no console till X boots, X fonts and window decorations get corrupted after suspend with proprietary drivers) it kinda works.
-video camera
-port meego or build the list of good software in ubuntu for handling sensors, virtual keyboard etc
I'm not currently working on the project and don't have the device anymore. Feel free to PM me if you need help with some tegra hackery
good job...
Hi sp3dev,
Cooooool, you rock
Thanks
FANTASTIC WORK!!!!
Guys... I'm not so clued up on the bootloader here, but is dual boot possible with this setup?
"so I guess I need to switch distro to try out this cool stuff"
What distro are you considering switching to?
tholmewood said:
FANTASTIC WORK!!!!
Guys... I'm not so clued up on the bootloader here, but is dual boot possible with this setup?
"so I guess I need to switch distro to try out this cool stuff"
What distro are you considering switching to?
Click to expand...
Click to collapse
Yes, dual boot is possible - the android is in internal memory, our stuff is on micro sd card. It should be possible to even dual boot from internal memory, but not right now
I am switching to ubuntu because it has a lot of packages prebuilt
sp3dev said:
Yes, dual boot is possible - the android is in internal memory, our stuff is on micro sd card. It should be possible to even dual boot from internal memory, but not right now
I am switching to ubuntu because it has a lot of packages prebuilt
Click to expand...
Click to collapse
Man I cant wait to get Netbook Remix dual booting on this badboy... Living the dream I tell ya...
Thanks again
Would booting a distro from say the usb work?
Sent from my HTC HD2 using XDA Premium App
M..N said:
Would booting a distro from say the usb work?
Sent from my HTC HD2 using XDA Premium App
Click to expand...
Click to collapse
I see no reason why not. But you'd have to hardcode the uuid of the boot partition in kernel command line or build a ram disk. Anyway having to use a heavy and power consuming external storage sounds like an extremely stupid and useless idea
what about Gentoo?
This is great! i would love a dual boot. and ubuntu! i just got done reading that the asus got this and was like. i want it now. now we almost have it keep up the great work!
sp3dev said:
I see no reason why not. But you'd have to hardcode the uuid of the boot partition in kernel command line or build a ram disk. Anyway having to use a heavy and power consuming external storage sounds like an extremely stupid and useless idea
Click to expand...
Click to collapse
Not even from a USB flash drive? Wouldn't it be the same as say booting it from a microsd card?
Sent from my A500 using XDA Premium App
Have Anyone seen this LINK?
Hope it can help!
OrionBG said:
Have Anyone seen this LINK?
Hope it can help!
Click to expand...
Click to collapse
That sounds like the place to start!
Thanks
Thanks man you really rock !
I cant wait to try it out. Hope you will continue working onto this.
can you share the steps after compiling the kernel ?
I would like to try with different kernels but I'm still not confident on how to do this.
If I use dd if=zImage of=/dev/mmcblk00p1
will this effectively boot this kernel after pressing power and vol- keys ?
Hello, do you think that Dvb t is possible if Linux is running on the acer?
yodor said:
can you share the steps after compiling the kernel ?
I would like to try with different kernels but I'm still not confident on how to do this.
If I use dd if=zImage of=/dev/mmcblk00p1
will this effectively boot this kernel after pressing power and vol- keys ?
Click to expand...
Click to collapse
No.. You need to build boot image with android's mkbootimg and flash instead of recovery. And then, mkfs.ext4 on your sd card on partition mmcblk1p2 and untar rootfs there
Thanks man, this is really getting clear to me now.
I'm going to try and post results here. I will love to try and see how arch, fedora and ubuntu will run on A500.
http://dev.gentoo.org/~armin76/arm/tegra2/install.xml
There are two apps in the Android market that will install either Ubuntu or Backtrack for you- they are not native installs though I can confirm they perform well even if it is chroot and I can also confirm they work on the iconia great! Search ubuntu installer or backtrsck5 linux install in the mmarket....
I was wondering if it would be possible to install linux (ubuntu) on the Nexus Player? I feel like this would be the perfect device for this.
No. Seriously. This is worthwhile. Small footprint, capable hardware. No significant hurdle.(?)How? Tutorial! Please!
lefigue said:
No. Seriously. This is worthwhile. Small footprint, capable hardware. No significant hurdle.(?)How? Tutorial! Please!
Click to expand...
Click to collapse
Agreed. The only thing I can see possibly being a problem is getting 3D acceleration working because of the PowerVR GPU. Everything else on this device seems well suited for Linux. Would just need a boot image akin to Ubuntu Touch on the old Nexus 7. Sadly I haven't seen anything that would help get this started on the Player, and I currently don't have the experience to start it myself.
Uh, it's already running Linux. It sounds like you just want to run a different Linux distribution than Android. Shouldn't be difficult. You can run debootstrap on a clean system partition from recovery. You'll need to modify the boot image to run your distribution's init instead of trying to boot android. I would just look at the Ubuntu phone images for an idea of how they do it.
hackel said:
Uh, it's already running Linux. It sounds like you just want to run a different Linux distribution than Android. Shouldn't be difficult. You can run debootstrap on a clean system partition from recovery. You'll need to modify the boot image to run your distribution's init instead of trying to boot android. I would just look at the Ubuntu phone images for an idea of how they do it.
Click to expand...
Click to collapse
It's usually not that simple. The boot partition from the examples I've seen (Ran Ubuntu desktop on my Nexus 7 2012) has to contain the kernel for the regular Linux install. I haven't looked into how big the partition is on the Player, but I know I had issues getting a mainline kernel to fit on the 8MB of the N7 2012. Plus most of the people here (including myself) wouldn't know where to even start at trying to get this to work for the Player (Hence why we ask in a community that has the expertise to possible pull it off). Specs wise the Player could be a fairly nice cheap NUC (If the PowerVR has support, that would be even better)
parkerlreed said:
It's usually not that simple. The boot partition from the examples I've seen (Ran Ubuntu desktop on my Nexus 7 2012) has to contain the kernel for the regular Linux install. I haven't looked into how big the partition is on the Player, but I know I had issues getting a mainline kernel to fit on the 8MB of the N7 2012. Plus most of the people here (including myself) wouldn't know where to even start at trying to get this to work for the Player (Hence why we ask in a community that has the expertise to possible pull it off). Specs wise the Player could be a fairly nice cheap NUC (If the PowerVR has support, that would be even better)
Click to expand...
Click to collapse
You are not making sense. Usual linux distro has a boot partition that contains 1 or more kernels, and 1 or more ramdisks that match those kernels. Usual linux distro also has a multi-boot boot loader, which is able to select between the available kernels and ramdisks. An android device is arranged such that it has a SINGLE-boot bootloader, and its boot partition is just a kernel+ramdisk stuck together. You can stick a ubuntu kernel and ramdisk together in the EXACT SAME WAY, if that is what the bootloader requires.
As far as "getting a mainline kernel to fit... blah blah blah", the thing is... mainline kernel isn't any bigger than what you have. The difference with a "typical linux kernel" is that it isn't built with just the drivers that support that specific device, it is built with pretty much EVERY common driver built in, so that it will work on most hardware without being rebuilt. Delete the crap that you don't need, and it should fit just fine.
OR for that matter, what makes you think that something like Ubuntu won't work just fine with a kernel built for Android? Android runs on a LINUX KERNEL. Just change out the ramdisk for one more suitable for... whatever, and call it good.
Now the big question I would have about doing this.... is WHY? Nexus Player is awesome BECAUSE it runs Android TV. If you are looking to run a desktop linux on a thing that plugs into your TV, look into something like an INTEL COMPUTE STICK.
Hello there fellow user! I decided to make a dedicated thread for all the things concerning the K1 after having been one of the first with a borked wifi chip.
Wifi:
View attachment 3555900
My phone refuses to focus + bad light. Either way, it seems that the lower right cable easily comes lose. From holding the tab in portrait mode, it's very easy to press on this certain spot which is located just 2-3 cm below the volume down and microSD-slot. Now I''m not sure if I'm only one with this issue and I'm sure others will probably pop up soon enough. Now the question is... Bad design? Yes! Fixable? Hard to say... Using loctite would be one solution.
Battery:
View attachment 3555842
Clearly the K1 battery is only 5100mAh vs 5200mAh on the "1st gen". Least we don't have to worry about issues from the past(?)
Stylus:
View attachment 3555883View attachment 3555895
As you can see. The space used for the stylus is still there but sealed up in the top, and the part that detected removal is no longer there. With some modification of the upper part of the tablet and securing the speaker flex cable, you should be able to ghetto mod it back.
Screen:
Some backlight bleed on one side, but this is pretty normal with LCD type screens. Nothing you can really manually fix.
Some things to consider (both pros and cons):
+ AVC/HEVC (H.264/H.265) support up to Main 10 profile. While it supports Main/Main 10 on all levels it lacks a hardware deblocker unfortunately, so you'll have artifacts appearing all over the place when running 10bit content. The general rule is to use a software decoder for 10bit media while running 8bit on hardware if/when possible.
+ "Decent" speakers compared to other tablets of the same size (exluding addons here).
- It has mini HDMI (1.4a) output over SlimPort (MHL 3). Even though both can handle 2160p @ 30hz, the difference being that MHL 3 supports both charging and A/V output at the same which is rather odd as it would've lowered the costs even further.
- 16GB eMMC being the only option, and it's not exactly the fastest. 32GB should be the minimum size for any Android device over the low-tier.
- Gimped microSD card slot resulting in really really slow i/o (reads/writes). This seem to effect general performance overall if you like to hog a lot of files (i.e pictures of manga pages in my case). Just enter any file explorer over time and you'll notice the initial slowdown when browsing.
- Stylus holder (and dedicated hardware for detection) is missing on the K1 making it rather hard to keep track of the DirectStylus 2 unless you mod the holder back of course. They could've left the hole intact at least.
- QC 2.0 (3.0?) or quick charging at all has been disabled for some safety reasons. But can be brought back.
- Power button and volume toggles lack any decent height or size for that matter making them rather hard to press for general usability when compared to even smaller devices.
Click to expand...
Click to collapse
SHIELD Hub (GeForce NOW/Experience) vs Moonlight:
GeForce NOW
View attachment 3791736
As seen in the screenshot I snagged while trying to find a game that has a benchmark mode I managed to find what hardware is being used to host the streaming/cloud platform itself. I assume they are running a few of these in a cluster for each region.
Loading a new game fresh from the app takes about ~15 seconds.
There is a resume function which works as long as you don't exist the app itself. And if you do, all progress is lost unless the game supports on the fly saving when you quit the game, so if you lose your connection you're screwed pretty much.
Very low input lag (<20ms) when streaming over distance from Nvidia servers though ymmv.
You're pretty much bound to the subscription service if you're a casual gamer/kid wanting your break free from mainstream mobile games which is sadly the whole idea of this service.
You can buy some games that'll work without a subscription. A key is also provided for Steam or GOG.
First 3 months are free if you take the offer, after that it's $7,99 or your region equivalent per month.
If you only plan on streaming your own game library then this app make very little sense and I would strongly recommend on using Moonlight instead for this purpose or GeForce Experience at least if you're afraid of fiddling on your own.
Click to expand...
Click to collapse
GeForce Experience:
If Moonlight is too much for your then this should work as intended.
Sadly there's no separate app just for this feature and you're stuck with the rest of the above mentioned. Unless that is, you go with the bare minimum setup for Moonlight.
Click to expand...
Click to collapse
Moonlight:
Opensource.
Lots of customization options.
You require your own dedicated machine and games for it to work, not to mention a GTX 600/M series or newer, and this applies to SHIELD Hub as well if you plan on running your own games from say Steam, GOG or Origin via GeForce Experience.
Click to expand...
Click to collapse
Personal thoughts and recommendations:
Works excellent with BT Keyboard and Mouse (I've used a Logitech K810 Keyboard and Logitech MX Anywhere 2 in conjunction as my daily portable workbench) say if you prefer a really minimalistic BT peripheral approach.
You got Google Docs at your disposal. There's also Microsoft Office as well if you prefer that.
FL Studio Mobile (that is getting a huge update soon with v.3) for you audio composers out there.
Various approaches to gaming both via Moonlight and NVIDIA SHIELD Hub w/ either the Shield wireless controller or <insert BT controller here>.
There's Squid or Evernote (which I highly recommend, though you really want the premium features that comes with a subscription fee) a must have if you're a student on the go and prefer having a really portable work device instead of a chrome/netbook or regular laptop/ultrabook if your pockets aren't overflowing with gold coins.
Moon Reader +/Pro for your ebooks on the go, if you dislike Amazon Kindle or Google Play Books that is if you prefer maintaining your own collection from other sources. I use it strictly for AO3 content for example.
Excellent emulator support with RetroArch, PPSSPP, ePSXe and Drastic.
Great size for Manga or Comics (although I must say Nexus 7 takes the first spot when it comes to that).
Infinite Painter, SketchBook or ArtFlow if you prefer more than just doodling when on the go. I hear krita might happen in the near future.
Click to expand...
Click to collapse
Drivers & Tools:
Official drivers directly from Nvidia to get adb/fastboot working (Windows)
Recommended tool to use for adb and fastboot: Minimal ADB and Fastboot (Windows)
For de/compressing files I recommend 7-Zip (Windows)
Click to expand...
Click to collapse
adb/fastboot commands of ease:
When using Android OS:
adb reboot bootloader
adb reboot recovery
adb shell wm density XYZ && adb reboot (changes DPI to your preferred value by modifying XYZ. i.e 240, 360, 480 and so forth and reboots the device)
When in bootloader:
fastboot oem unlock/lock
fastboot flash recovery twrp.img/recovery.img (i.e flashing TWRP) depending on what your img is called and located in same folder as Minimal ADB and Fastboot i.e C:\Program Files (x86)\Minimal ADB and Fastboot (Windows)
Click to expand...
Click to collapse
Tips:
Flash a custom dtb to enable QC 2.0 among other things.
In developer options:
Enable Force GPU rendering for a more fluid GUI experience.
Set Window animation scale to .5x.
Set Transition animation scale to .5x.
Set Animator animation scale to .5x.
Click to expand...
Click to collapse
Custom Recovery
TWRP 3.0.2-3-M (only works on MM due to blob changes.) [courtesy of jcadduono] - As stable as it can get. Still suffers from refresh/redrawing issues though.
DO NOTE: AROMA installers will be upside down. This will happen with any AROMA installer in conjunction with TWRP recovery due to the placement of the actual screen.
Click to expand...
Click to collapse
Custom ROMs:
Bliss [* CM13 Based] (+ requires MM blobs)
Temasek's UNOFFICIAL CyanogenMod 13 (*+)
Resurrection Remix (*+)
Dirty Unicorns [AOSP Based with CMTE support] (+)
DO NOTE: All available Custom ROMs mentioned above do NOT I repeat NOT support the Shield Controller or the Twitch integration or what other Nvidia tools are integrated into the Stock ROM. This might happen at a later date, who knows.
Click to expand...
Click to collapse
Custom Kernel:
BitO-K (don't forget to flash the custom dtb!.
NetHunter kernel - Support for DriveDroid, F2FS, Multi-ROM among other things.
Click to expand...
Click to collapse
Recommended GApps:
Official Slim GApps Zero or Mini, whichever you prefer.
Open GApps - AROMA supported.
Click to expand...
Click to collapse
SuperSU:
SuperSU STABLE | SuperSU BETA (flash via TWRP)
Click to expand...
Click to collapse
Root supported Apps:
AdAway - Adblock on a host level.
Amplify (Xposed version avail) - Wakelock killer extraordinaire.
FlashFire - Flash files without a custom recovery.
Flashify - Flash files if you're scared of the custom recovery UI.
Xposed (flash via TWRP) + Material Installer.
Solid Explorer [PAID] (Comes with root support for extra fiddling and other goodies!)
Titanium Backup [PAID] (Free version offers basic features but the paid version is recommended.)
Click to expand...
Click to collapse
General Apps I recommend:
Super Simple Sleep Timer - Silence any audio app after a period of time.
NoChromo - Chromium with builtin adblocking. (enable all permissions to get google sync working on MM)
Lightning Browser - Probably the smallest and fastest browser out there if you can live without google sync support.
Click to expand...
Click to collapse
Xposed Modules:
PLACEHOLDER
Click to expand...
Click to collapse
Emulators:
PPSSPP - PSP Emulator with great scaling potential (does not support PS1 or PSX2PSP packaged games)
ePSXe [PAID] - Probably the best b... PS1 emulator in the world! Supports PSX2PSP packaged games.
DraStic [PAID] - One of the few DS emulators that actually does the job well with games that require dual screen/touch support.
RetroArch - A mixed bag due to a poor GUI and touch sensitivity being way to high on some devices. It does the job however once you've gotten past setup. Best used with a controller due to not supporting touch input on Custom ROMs (all above). Works flawlessly on Stock ROM though for some reason.
Click to expand...
Click to collapse
Stock Shield Tablet K1 ROM/Firmware:
Stock K1 FW 5.1.1 "Flashable via fastboot.
Stock K1 FW 6.0 Feb 2016 - "
Stock K1 FW 6.0.1 March 2016 - "
Stock K1 FW 6.0 FULL OTA Dec 2015 - *Flashable via Stock Recovery through adb.
Stock K1 FW 6.0 FULL OTA Feb 2016 - *
Stock K1 FW 6.0.1 FULL OTA March 2016 - *
Stock K1 FW 6.0.1 FULL OTA June 2016 - *
i.e you can flash 5.1.1 then go to the latest OTA via recovery. This is why only FULL OTAs are posted.
Click to expand...
Click to collapse
How to: Root/Flash a Custom ROM/Recovery/Setup (assuming you are running Windows 7-10) with ease:
Unlocking the bootloader:
#1 - Assuming you recently bought your device, I would recommend to fully update your K1 to 6.0.1 at least for Doze or later, Custom ROM support covered here. Lollipop and Marshmallow are not compatible with each other, so different TWRP recoveries are needed due to blob-changes. I won't go into this since you really shouldn't care, only that the two Android versions are incompatible with each other, end of story.
#1X - If you are already running 5.1.1 rooted with TWRP recovery and SuperSU. Then I would suggest you to redo your device to stock status, that being either flashing Stock K1 FW 5.1.1 or Stock K1 FW 6.0.0, whichever you prefer really, as with 5.1.1 it'll only take a little bit longer due to updates and whatnot.
#2 -
Get the Nvidia Shield Drivers in the link further up in this post and while you're on it, install Minimal ADB and Fastboot (link above as well).
Now turn off your K1 (keeping it disconnected from your PC while doing so) and press and hold Power + vol down until fastboot/bootloader kicks in and select Fastboot protocol.
Start by typing fastboot oem unlock once in fastboot mode via Minimal ADB and Fastboot and follow the instructions.
You should end up with a unlocked bootloader and wiped data partition (all personal data, settings etc will be lost, and it'll be just like when you bought it).
Now you can freely connect it to your Windows PC to do the following:
Flash TWRP custom recovery and later SuperSU/Custom ROMs and what not.
Click to expand...
Click to collapse
Custom Recovery (TWRP):
#1 - Download the latest (thx jcadduono!) available TWRP build for K1.
Choose: i.e in this example twrp-3.0.2-3-M-shieldtablet.img and rename it to something simple like twrp.img.
Now put the twrp.img file into the same folder as Minimal ADB and Fastboot.
Above in this post I have noted the folder structure should you be running a x64 build of Windows 7-10.
Type in: fastboot flash recovery twrp.img and wait for the magic to happen.
You now have a Custom Recovery installed. Enter Recovery in the bootloader for the rest below, should you so desire.
Click to expand...
Click to collapse
SuperSU:
If successful, enter recovery through the bootloader menu on your K1 and go into Install.
Here you can transfer over (mostly) any files into your device or SD Card (if you have one), but I prefer working from the device directly in case of any hiccups.
Go and download SuperSU BETA or SuperSU STABLE and put it on your K1.
Go to Install and pick either (not both) and let it finish installing.
Once it has finished doing so you can reboot.
You now have a unlocked bootloader, TWRP recovery, and root support... now how about that huh?
Click to expand...
Click to collapse
--- To be revised later
Flash a Custom ROM, GApps, and/or Xposed:
#1 - Assuming you've already done all above, you can skip to this point and begin flashing your first Custom ROM with a compatible GApps and SuperSU package.
#2 - I recommend Open Gapps pico for starters as you can install the rest through Play Store, but if not, you are free to go with the bigger packages, while avoiding the AROMA one as it's rather difficult to navigate on our device as noted above. As for SuperSU, the latest SuperSU v2.68 BETA works fine.
When you're done downloading the two, pick your favorite looking ROM out of the links above (hint: I would recommend Dirty Unicorns or Temasek's UNOFFICIAL CyanogenMod 13 for now). And then put them on the device by enabling Mount in TWRP or if not, I think TWRP 3.0.0-0 auto mounts as of now. I don't have the device with me as of me typing this but I'm 99% sure it auto mounts.
#3 - Assuming you are starting anew and know how to enter TWRP by now, go wipe all partitions (all data on the device). The easiest way to do this is by entering TWRP>Wipe>Format Data>Type Yes>and then wait.
Go to Install and pick the folder (if you made one) or the root of your K1 where you put the files and flash in this order:
DU_shieldtablet_6.0.1_20160311-2210.v10.0-WEEKLIES.zip or cm-13.0-20160225-UNOFFICIAL-temasek-shieldtablet-V4.6.zip (currently available)
open_gapps-arm-6.0-pico-20160315.zip (*)
BETA-SuperSU-v2.68-20160228150503.zip
and xposed-v80-sdk23-arm.zip if you're interested in Xposed modules, but if not, having it there is always an added bonus as you can start playing around with it should you so desire at some point. But if not, hey... I won't judge you.
Then reboot and let it compile all apps via ART which can anything between 2-5 minutes, so grab a coffee or tea (or whatever you prefer... water, milk you get the idea) as the wait can be quite bothersome during your first run.
And huzzah!!! You're on your first Custom ROM, ready to take on the world!
Click to expand...
Click to collapse
Xposed:
#1 - Xposed. I would recommend Amplify (also available as a separate app via Play Store) that works like a separate Doze mechanic where you can play around with settings and rules, but you're on your own on that one. It does however save some battery juice if you pay the minimum, like $2 or something which I think it's totally worth. Next up is YouTube Background Playback (works like in Youtube Red in a way) and does what it's called. Then there's various adblock modules for Youtube, Tumblr etc, just search for Adaway and you'll find them. This ends my super duper long guide.
Click to expand...
Click to collapse
this year I hope. ---
Benchmarks (NOTE! This was done with Stock 6.0.1 June patch + AOSP Based ROM Dirty Unicorns 6.0.1 June patch/10.3 Weekly.)
Pictures are ordered as: Max Performance, Optimal and Battery Saver/Power Saving.
Antutu
Dirty Unicorns 6.0.1 June 10.3 Weekly:
Stock ROM 6.0.1 June:
View attachment 3791773View attachment 3791774View attachment 3791775
Click to expand...
Click to collapse
3DMark
Dirty Unicorns 6.0.1 June 10.3 Weekly:
Stock ROM 6.0.1 June:
View attachment 3791461View attachment 3791462View attachment 3791463
Click to expand...
Click to collapse
PCMark (Storage Test w/ Sandisk UHS-I 80MB/s 128GB microSD card)
Dirty Unicorns 6.0.1 June 10.3 Weekly:
Stock ROM 6.0.1 June:
View attachment 3791770View attachment 3791771View attachment 3791772
Click to expand...
Click to collapse
Geekbench
Dirty Unicorns 6.0.1 June 10.3 Weekly:
Stock ROM 6.0.1 June:
View attachment 3791253View attachment 3791254View attachment 3791255
Click to expand...
Click to collapse
Accessories/Reviews:
Nvidia:
Shield Controller [PLACEHOLDER]
Shield DirectStylus 2 [PLACEHOLDER]
Shield Tablet Cover [PLACEHOLDER]
Sandisk:
Mobile Ultra microSDXC Class 10 UHS-I 48MB/s 128GB
Mobile Ultra microSDXC Class 10 UHS-I 80MB/s 128GB
Mobile Ultra microSDXC Class 10 UHS-I 90MB/s 200GB [PLACEHOLDER]
Logitech:
Bluetooth Illuminated Keyboard K810 [PLACEHOLDER]
MX Anywhere 2 [PLACEHOLDER]
Anker:
TBA
iClever:
Ultra Slim 3 Color backlight Bluetooth Keyboard [PLACEHOLDER]
8bitdo:
8Bitdo NES30 Pro [PLACEHOLDER]
8Bitdo FC30 Pro [PLACEHOLDER]
8Bitdo Zero [PLACEHOLDER]
Click to expand...
Click to collapse
Hey there, good post! Thanks for the info.
I am a new owner of a Shield Tablet K1 and looking at modding some things (like adding the stylus features back in and gaining root). I am quite experienced in modding and that stuff, I do know how to operate fastboot and adb, so the basics are covered.
I still have some concerns and wasn't able to find something yet since most posts are about the "old" Shield Tablet, so I am sorry to bother you with a few questions (since I want to be extra sure and not assume both are the exact same).
Can you tell me whether unlocking the bootloader leaves a trace? If I happen to need to file an RMA request, will flashing back the stock stuff and relocking the bootloader make the tablet look "as new"? I know some devices put a "tampered" flag in the bootloader screen or say "relocked" instead of just "locked" so anyone looking at that will instantly know that I've tampered with the software and deny warranty claims. Could you please tell me what you know about the possibilities of reverting to stock without leaving a trace?
Thanks in advance
Oh, and have fun with the new hardware!
Heya. As for losing warranty due to unlocking the bootloader, that's something you'd have to ask Nvidia since they also tell you do it when re-flashing as seen in this README.
Either way, a retailer couldn't tell otherwise unless they were provided by some diagnostics tool that specifically showed some hidden logs unless a dev here could fill us out on that? I'm in the process on getting my K1 replaced by a new one since the wifi related issue I have is due to borked hardware.
PixelVixen said:
Heya. As for losing warranty due to unlocking the bootloader, that's something you'd have to ask Nvidia since they also tell you do it when re-flashing as seen in this README.
Either way, a retailer couldn't tell otherwise unless they were provided by some diagnostics tool that specifically showed some hidden logs unless a dev here could fill us out on that? I'm in the process on getting my K1 replaced by a new one since the wifi related issue I have is due to borked hardware.
Click to expand...
Click to collapse
Okay, thanks for the answer!
I think I'll do some further research and then see if I go ahead and root it. What's that re-flashing thing about? Is it a guide by Nvidia to restore if something gets corrupted?
Hope your replacement goes through without problems!
What version of firmware is installed on Shield tablet K1?
Where it can be downloaded?
robstyleX said:
What's that re-flashing thing about? Is it a guide by Nvidia to restore if something gets corrupted?!
Click to expand...
Click to collapse
Indeed it is
They actually offer you files to reflash Stock in case of any hiccups or whatever. Warranty at best is covered by Nvidia but not by the retailer if they're still living in the 80s.
Vartom said:
What version of firmware is installed on Shield tablet K1?
Where it can be downloaded?
Click to expand...
Click to collapse
K1 firmware is not yet available. But flashing the firmware for 1st gen is there and compatible with K1 (both are 3.1.1/5.1.1)
Nm...still confused. Lol the firmware links posted are stock or modified? How did you get max performance?thanks!
markstibbyspot said:
Nm...still confused. Lol the firmware links posted are stock or modified? How did you get max performance?thanks!
Click to expand...
Click to collapse
Firmware links are directly from Nvidia. As for Max Performance, Optimal, and Power Saving... It's in SHIELD Power Control.
Ahh makes more sense! Works perfect!
@PixelVixen did you try @lj50036's 2.8.7.3 TWRP he released? Could you try it please.
If it works we know that the K1 is compatible with our roms going forward as well
Do you think there would be enough room to fit a pigtail over to a dipole wifi antenna where in the stylus chamber?
Ok it looks like you could get a u.fl to sma cable to fit but you will need to have the sma connector protrude out of the case, I guess it will then look like a old portable tv with an antenna sticking out of it... If I was not giving this as a gift I would experiment further but I will leave that decision to the person receiving the tablet.
sbdags said:
@PixelVixen did you try @lj50036's 2.8.7.3 TWRP he released? Could you try it please.
If it works we know that the K1 is compatible with our roms going forward as well
Click to expand...
Click to collapse
Heya. I'll do some testing come weekend as I've been quite busy with IRL and projects that I've been working on!
edit: 2.8.7.3 is working as intended \o/
Any room to add wireless charging?
Sent from my SHIELD Tablet using Tapatalk
T-Keith said:
Any room to add wireless charging?
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
It's a hardware thing, not a "room" thing.
Just a head's up: Flashing 3.1.1 FW will brand your K1 to a 1st gen device and the 6.0 update now avail will not appear (yet).
edit: I'm still surprised we still have no ways of recovering K1 devices to K1 3.1.1 FW or Android 6.0 for that matter in case of any borkups.
Nvidia if you see this, push it to your dev section! Source is not enough!
Link of Stock Lollipop K1:
http://developer.download.nvidia.co...age-shield-tablet-sb_na_wf-37154_590.0364.zip
Muchas gracias!
Hi, friends. I've just got my new SATV PRO 2015 and I'm going to revert it to linux development station for some python stuff. To do this I need to make a lot of work on unlocking bootloader, rooting, flashing, etc.
So I need a fully backup first. I know, I could make one with copying inner HDD, but I don't want to open Shield due to the warranty.
Are there any ways to backup all important partitions, files, data, IDs with use only of ADB and FASTBOOT? Maybe I can somehow copy the whole HDD to my 1TB drive without disassembly?
Thank you!
No. You need to backup your partitions (not entire hdd as that would not be practical) with tools like dd from Linux distro.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
armitagebron said:
Hi, friends. I've just got my new SATV PRO 2015 and I'm going to revert it to linux development station for some python stuff. To do this I need to make a lot of work on unlocking bootloader, rooting, flashing, etc.
So I need a fully backup first. I know, I could make one with copying inner HDD, but I don't want to open Shield due to the warranty.
Are there any ways to backup all important partitions, files, data, IDs with use only of ADB and FASTBOOT? Maybe I can somehow copy the whole HDD to my 1TB drive without disassembly?
Thank you!
Click to expand...
Click to collapse
It's really not a problem to open up the SATV and make a proper DD backup of the drive.
But, you should be able to boot linux L4T from the SD card or a USB key, and from there use DD to make the backup.
I'm just not sure that you have full access to the HDD from within that environment.
A friend of mine recently introduced me to Flashfire by Chainfire.
You can backup partitions from there too and apparently "TrustZone" is the relevant partition or just backup all the ones tagged as (protected partitions). I only have 16gb model but partition names should be the same.
The problem might be when you ever need to restore, if partition is writable and let you flash it. This needs to be tested to be 100% sure.
That app would be only for prevention for now
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
Yeah, guys. You were right. I was not smart enough to figure it out. I'm not sure about booting in Linux, but I'm sure, Flashfire will work. But, if you've rooted the device. ADB backup -all works just with /data partition. So, I opened the shield and cloned the whole HDD.