Search results

Hi! I still need to put my hands on a Shield device to be honest. I have been making progress on the GPU front though, to a point where acceleration is now starting to work with upstream to a point where it should be soon possible to use X. Thanks for pinging me though, I will ask for a Shield...

You are correct, staging/work is the branch you should use for any upstream-based X1 work. staging/nouveau is my staging area for Nouveau-related patches. staging/work is the same branch merged with the latest -next and many staging Tegra-related patches (including decent X1 support) from the...

I am *very* interested in knowing which kernel you have used for this. Upstream, L4T, Android? This looks very promising in any case.

OTA link for Wifi version: http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-incremental_ota-from-28311_475.5300-to-29082_493.9700.zip

It does work, but there is a trick: make sure you do not maintain the power button pressed (but keep volume down pressed). If you keep both buttons pressed, the tablet will not enter the bootloader.

Nope, the HDMI port on ST is output, not input. I don't think the hardware is even capable of working that way.

I am also seeing this since a few days, this is quite strange.

That's how it is explained in the recovery flashing instructions, although I agree this is somehow confusing.

Hold Volume down pressed, but release Power immediately after pressing it and you will enter the bootloader. When this succeeds you should never see the nvidia screen.

After I reverted to Dalvik I found the tablet to be very stable, so I am out of clues here. Power saving settings maybe?

You don't happen to have enabled ART instead of Dalvik in the Developer Settings, do you? I remember having similar issues when I did.

You are not bricked. Get the recovery image from https://developer.nvidia.com/develop4shield, and enter the bootloader and flash it following the instructions at https://developer.nvidia.com/sites/default/files/akamai/mobile/shield/SHIELD_tab/HowTo-Flash-Recovery-Image.txt. In your case you...

Well I have read the posts and my answer was not specifically targeted at you, but first and foremost to the people who spent 200+ on it and specifically to the OP who was worried his unit could stop working after a few months. It is possible that your unit is a pre-production one that was...

Why so much hate towards the iPhone when it first got out? Because it is a new, largely misunderstood product and those who call it crap typically never touched it. The relevant thing about the SHIELD is that the vast majority of its owners seem to love it. The opinion of uninformed people...

Just try it and you will know! (Spoiler: it still works)

If you just want to use your SHIELD as an office device, your needs may be better served by one of the many "Linux on Android" apps, e.g: https://play.google.com/store/apps/details?id=com.zpwebsites.linuxonandroid This will allow you to run a Linux desktop alongside with Android, without...

Since your unit is a developer one anyway, why don't you just root it and do what is necessary to get the mount points right?

Hi, Good news - Wifi and SD cards are now working (well, most SD cards at least) on my roth_next branch: https://github.com/linux-shield/kernel/tree/roth_next Bluetooth is still out of luck for now. All USB devices supported by Linux should be working with SHIELD, as long as the kernel driver...

Doing as vostok4 said should bring your SHIELD back to life. Just a quick question though: have you rooted your SHIELD, installed CWM recovery or twiddled with it whatsoever after unlocking the bootloader? Because if you haven't, and if the OTA process completed normally, there is no reason for...

You will need to revert to the stock recovery before you perform the update, as CWM cannot do it for some reason. If you are not using CWM features outside of rooting, you might prefer this rooting method which does not require installing it so you can just do OTA upgrades without worrying...

No need to unroot. You will have to reapply root (not unlocking) after the update though.

Just read the page, it contains download links and instructions.

Ok, rooting method on https://github.com/linux-shield/shield-root should work again for TN7. It will now create space on /system by removing Maps and Youtube from it - if these applications have disappeared after rooting, just reinstall them from the play store.

I'm booting the Note into Linux using my custom kernel and simple user space below: https://github.com/linux-shield/kernel https://github.com/Gnurou/bbfs These are also the basis for my rooting method.

Can you paste the whole line as I requested? I'd like to see the size of the partition as well. It seems like the /system partition has been shrinked to minimum, and the free space is now less than what we need to install root. ext4 is supposed to reserved a bunch of blocks for the root user...

Mmm that's strange, I will check tomorrow but I'm pretty sure I tested it with 4.4.2 already... Could you run adb shell to log into your TN7, type "df" and copy/paste the line that starts with "/system"? The "No space left on device" message would mean that your /system partition is full, but...

$ arm-none-linux-gnueabi-gcc --version arm-none-linux-gnueabi-gcc (Sourcery CodeBench Lite 2013.05-24) 4.7.3

Mmmm yeah. I'm afraid I'm clueless here, at least until the Tegra MMC driver gets an update. :( Sorry.

mmc1 shows as UHS in your log, and I'm pretty sure the driver can handle the drop to 1.8V (IIRC). On other boards this driver is known to work fine (if a little bit slow), so I really don't know what I screwed up here. I find it surprising that you are having issues with USB mass storage...

It should be possible to charge your SHIELD while using it as a USB host with a Y cable to provide power to the SHIELD and some more kernel hacking. Let me know if you really need it, if so I will try to find the time to implement it (it should work *in theory*, but no guarantee of course)...

Yeah, the upstream SD driver is clearly behind the Android one. :( That or I did a poor job in the SHIELD's device tree. Well, actually since you have a USB hub, and USB works at boot already, you can also use a USB mass storage device as your root filesystem. That would certainly work and you...

Yeah, you will need an OTG cable to get your keyboard to work. I suggest connect the OTG cable to a self-powered USB hub, and then plugging your keyboard, mouse, and network adapter there. If you get a powered OTG cable (like this one...

What type of SD are you using exactly? (SDHC, XDHC?). For use with upstream kernel I would not go beyond SDHC 32GB. The steps on my Github page should be correct, I did them myself many times. The initramfs can be a pain in the ass sometimes, I did it for people who want to be able to keep...

Booting a userspace stored from a microSD is possible, yes. However, the kernel itself must be on the internal memory (or sideloaded using fastboot). SHIELD's bootloader does not support booting a kernel directly off a microSD card, unfortunately. The CPU errors are because Trusted Foundations...

Just to let everyone know that I have updated the instructions on https://github.com/linux-shield/shield-root to support the latest TN7 4.3 OTA. You now need to manually unlock your device before rooting, so the instructions in the first post of this thread should be updated accordingly (doing a...

Both answers are correct - it all depends on which software (on the device) is used to flash, and what format it accepts. With Tegra devices you have at least 3 ways to flash stuff, from lowest to highest level: - nvflash/tegrarcm mode. This is a very small firmware that is burnt in ROM and is...

They will root any version that is currently installed. But you will have to do it again after every OTA (excepted for the bootloader unlocking part) since OTA rewrites the system partition entirely and thus will remove root.

Yes, that's how unlocking is done and it's identical to the procedure for Nexus devices. The reason there is no boot.img involved for unlocking is that unlocking is precisely what allows you to boot an unsigned image. This unsigned image then starts a small script that installs SuperSU and the...

Strange, I just unrooted my device and tried again with the latest image, and it did work for me. Are you guys seeing any error message during the rooting procedure? Is the SuperSU icon visible in the program launcher? Does it say you are not rooted when you launch it? Also, can you tell me...

This is totally unrelated to custom recoveries/roms since my effort was mostly to get the Linux kernel (as in, not Android) to boot. I could have used the Android kernel but my goal is to get pure Linux on TN7 and getting this root script to work looked like a nice first milestone. As expected...

So, I have finally updated my SHIELD rooting method to support Tegra Note 7 as well, so you guys don't need to install weird programs on your PCs: https://github.com/linux-shield/shield-root Rooting by itself is quite easy, you need to have adb and fastboot on your system then: 1) Enable USB...

Correct, the insecure boot image mounts the system partition read-write and then install the su binary there. Hence su resides in system, not boot. Edit: ah, I think I understand why you want the boot image now - it is to be able to mount system and install su by yourself, right? Edit 2: note...

Root is not in the boot image, but in the system image. If you can wait some more I will make another rooting method (similar to the one of SHIELD) available soon.

Yes, it does.

Interestingly the icon issue fixed itself for me as well.

FWIW I ran into the same problem of game icons disappearing. No fix for now but will investigate.

Custom recovery is definitely not needed. Root by itself also does not interfere. I updated without trouble. Maybe try reflashing the boot and system partitions to stock and try the update again?

Just wait a bit more and I will update it with TN7 support.

I will probably release a Tegra Note rooting method similar to the one I did for SHIELD (https://github.com/linux-shield/shield-root ). Just give me a few more days/weeks. Btw, how come there is no Tegra Note forum on XDA yet?

Guys, what's wrong with https://github.com/linux-shield/shield-root ? Its supposed to work with OTA64 so I don't understand why you are bothering so much with doing it manually...