yashsingh1/xdaforums huggingface dataset:
[Shield Android Development] gogul1:
It WORKED!

WOO HOO!

Thanks to all you guys who helped, really appreciate it what a great and patient bunch of people you are!

Thank you Thank you Thank you!
[Shield Android Development] MakiManPR:
There's a new Update/OTA for the Shield
[Shield Android Development] MakiManPR:
I rooted mine with that. But now with the new OTA I can reroot. I need help!!
[Shield Android Development] shimp208:
The manual method I posted in this thread should still work with the latest OTA update if you follow the procedure in the OTA :good:.
[Shield Android Development] MakiManPR:
When in Normal Shield Boot Mode my PC(Win8) does detect it. I can even give it the command to go to Fastboot. But when in Fastboot my PC doesn't recognize it anymore.

This is after going to Fastboot

---------- Post added at 01:06 PM ---------- Previous post was at 12:24 PM ----------

Fixed everything thanks to this vid

[YOUTUBE]http://youtu.be/XSisjVwcPbE[/YOUTUBE]

---------- Post added at 01:44 PM ---------- Previous post was at 01:06 PM ----------

PLEASE!
[Shield Android Development] shimp208:
For the One-Click Root I'll be happy to create that over the next week or so :) I'm currently in the process of moving into College that's why I'm a little behind on some of my projects.
[Shield Android Development] Faithinchaos21:
Has anyone tried Triangle Away when unrooting shield? Will this take away all traces of root?
[Shield Android Development] shimp208:
Triangle away is not compatible with the Nvidia Shield and is only meant for supported Samsung devices to rest the download mode flash counter to zero. Unfortunately once you unlock your Shield's bootloader before the rooting process you permanently set a flag in the bootloader that marks your devices warranty as void, granted there are some exceptions to the warranty being void.
[Shield Android Development] Faithinchaos21:
What kind of exceptions if you don't mind? It'd save me the trouble on finding them myself...
[Shield Android Development] shimp208:
For exceptions, it refers to your devices hardware failing due to causes unrelated to unlocking your bootloader and rooting. For example, if you root your Shield and then the next day the screen randomly won't turn on, then Nvidia will likely honor the warranty because it was unrelated to any modifications you may have made as a result of unlocking the devices bootloader.
[Shield Android Development] Faithinchaos21:
Oh ok, well that's all I'm really hoping for anyway. If I screw up my shield because of something I did to it, that's on me. Thanks
[Shield Android Development] wwjoshdew:
I made two videos on the NVIDIA Shield. Please let me know what you think [MENTION=3558630]shimp208[/MENTION].

How To Unlock the Bootloader: http://www.youtube.com/watch?v=7Am5WYRojMs

How To Root the Nvidia Shield: http://www.youtube.com/watch?v=_4-C0CzKoFs
[Shield Android Development] shimp208:
Very nicely done my friend, these video's will definitely be very helpful to people you do a very good job of explaining things in a simple easy to follow and concise manner :).
[Shield Android Development] wwjoshdew:
Good enough to maybe be linked to in the OP? :D
[Shield Android Development] shimp208:
Of course man :) I linked your rooting video to this thread and the unlocking bootloader video to my unlocking bootloader thread.
[Shield Android Development] jhonnyrazorback:
Sorry for the noob question, but i don't understand this: you need to to unlock the bootloader first to root the shield? :-/

for me, that would suck. I had a couple of android devices wich i rooted with programs like 1 click root but never unlocked them! I really DON'T want to unlock it. So, here is my (actually second) question:

Is there/there will be a way to root the shield without unlocking the bootloader????

thanx for your time, amigos!!! :)
[Shield Android Development] shimp208:
At this time there is no way to root the Shield without unlocking the bootloader. Unfortunately, until a root exploit is discovered that doesn't require you to unlock the bootloader to function properly then unlocking the bootloader

will be necessary.
[Shield Android Development] Kwongger:
Hi,

You do in fact have to unlock your bootloader but, Nvidia is still great with hardware warranty issues (so far).

A easier method of rooting would be to use my Toolkit. It is great for people with less experience. You can use it to out-of-box restore and to Re-Lock Bootloader.

http://xdaforums.com/showthread.php?t=2444525
[Shield Android Development] jhonnyrazorback:
Unlocked only, right? Damn... :crying:

Well, good to see that thanx to you guys is still doable (and even fairly easy). Cool, looking foward to get the shield!!!

Thanx for the replies:good::good::good:
[Shield Android Development] trdpatrick:
Any idea if this method still works for update 63? (Android 4.3)
[Shield Android Development] shimp208:
This root method should still work fine with update 63.
[Shield Android Development] Furyus:
I can't get my original root method to work after the update 63. The SuperSU binary is missing-- I'm trying to apply your insecure boot img, how long should it take the device to reboot? Mine hung for ages, I did a hard shut down and when it came back up I'm getting an 'Operation not permitted' when running the mount command. I'm guessing the boot img didn't take. Any thoughts?
[Shield Android Development] seaking177:
i unplugged the shield from the computer and plugged it back in, it popped up a message about allowing the computer to debug the device. i am guessing that is why the image didn't take?

will try this again, be back in a few minutes.

nope, the boot image does not work anymore :(.
[Shield Android Development] shimp208:
Thanks for letting me know that my insecure boot images don't work with the latest OTA update. To obtain root what you can do is download CWMR for the Shield from this thread and then flash it, then once you have flashed CWMR you can download the latest version of SuperSU from this thread and flash the SuperSu .zip file in CWMR to obtain root access. After you guys obtain root access if you can dump your boot.img and upload it I can modify it to be insecure then produce a 1-click root method.
[Shield Android Development] Doodle210:
Can you explain how to dump the boot.img for the Shield?
[Shield Android Development] shimp208:
Just to verify you have root access now correct? Please navigate to the /cache/recovery directory and then please upload here the contents of the recovery_log file that is in the /cache/recovery directory. The recovery_log file will allow me to determine which partition is the /boot partition for you to dump.
[Shield Android Development] Doodle210:
This is what was in the /cache/recovery/ directory.

https://drive.google.com/file/d/0B7j6Imwr_sirOTBwalVvWldHczg/edit?usp=sharing

Is this it?

https://docs.google.com/file/d/0B7j6Imwr_sirTEtLRExLLXV5cms/edit?usp=drive_web

I used

in Terminal Emulator.
[Shield Android Development] wrc1010:
After update the shield to the latest firmware with android 4.3. It look like cant root it anymore.

Does anyone have update his shield and success root it with android 4.3?
[Shield Android Development] Doodle210:
It's pretty fast and simple.
[Shield Android Development] aDigitalPhantom:
here are two methods both need root

1. dd if=/dev/block/platform/sdhci-tegra.3/by-name/LNX of=/storage/sdcard0/boot.img

I think this needs adb to be ran as root

2. adb shell "cat /dev/block/platform/sdhci-tegra.3/by-name/LNX">boot.img
[Shield Android Development] shimp208:
The Original Post has been updated to include a new insecure boot.img that is compatible with OTA update 63. The new updated insecure boot.img will allow you to flash it through fastboot and follow the rooting procedure from the original post. If anyone has any questions please let me know.
[Shield Android Development] Doodle210:
Yeah, I figured it out as I looked through the files. Wish someone would have posted it somewhere so I could have gotten a better nights sleep :p
[Shield Android Development] Entropy512:
Yeah. I flashed agrabren's CWM recovery after updating to 4.3 (you need to be on stock recovery for official updates to work), flashed SuperSU 1.65 in recovery, and it worked perfectly.
[Shield Android Development] Bubleman77:
Update 63 root ploblem - need help

I had my Shield updated to 59 with root.

I let it upgrade to update 63 without precautions.

The upgrade was successful but I lost root access.

So I read a bit about it and decided to flash my Shield back to original, in hope to do the 63 upgrade later and succeed with rooting.

Then I download original image from : http :// goo.im / devs / agrabren / shield / original_images (without spaces)

Use Minimal ADB & Fastboot with followings commands :

fastboot erase system -w

fastboot erase boot

fastboot flash recovery recovery.img

fastboot flash system system.img

fastboot flash boot boot.img

fastboot reboot

At reboot Shield quickly (lees than 1/2 sec) displays BOOT FAILED and freeze on bootloader screen (unit is completely frozen, nothing works).

I can stop it by pressing Shield button for 10 seconds, and restart in booloader mode by pressing the three buttons.

So bootloader mode is OK so I can try to push another boot.img. but I dont know how to fix this ?

Anybody can help ? Thanks
[Shield Android Development] Gnurou:
Not sure why it fails (missing blob maybe?) but the following is the "official" recovery method:

1) Get the release 59 images from https://developer.nvidia.com/develop4shield#OSR, unpack and flash them using the .bat or .sh script (will reset your user data, remove the line that flashes it if you don't want to lose it)

2) Boot and upgrade to 63

3) Root by either flashing CWM and then SuperSU or by using my boot image (https://github.com/linux-shield/shield-root , now updated to support 4.3). The advantage of the latter is that it does not require you to flash your recovery, so OTA updates will work normally (but you will need to re-root after each of them).
[Shield Android Development] aDigitalPhantom:
That is not "official" as "officially" rooting and software mods are not supported.

Linux is needed to extract the images that you get from https://developer.nvidia.com/develop4shield#OSR

I am not sure what the blobs are for here is part of the blob file in update 63...

-SIGNED-BY-SIGNBLOB-\ME.....MSM-RADIO-UPDATE....
[Shield Android Development] Bubleman77:
Solved !

OK, I did as you suggested.

Download official Nvidia image Rel 59. Extract with Cygwin, flash it, reboot, went through update 63, root with your kernel image and everything went perfect.

My Shield is now upgraded to Release 63 and rooted.

Thanks Gnurou.

(Still unclear to me what went wrong on previous attempt, but thanks again I needed that support when it was frozen)
[Shield Android Development] Doodle210:
IDK what the blob is for either, but it seems you won't be able to do a complete recovery without it... :\ Took me hours to learn that lesson, not even Nvidia's "specialist" knew that I needed to flash the blob.
[Shield Android Development] Gnurou:
Well it comes from NVIDIA servers complete with instructions so its as close to official as you can get.

Anyway yes, the blob seems to be needed to do a complete recovery, just keep that in mind and you should be safe.
[Shield Android Development] themichael:
How are you extract with cygwin. I am getting the below error. driving me nuts.
[Shield Android Development] DogmAxCDXX:
This method is not working with Update 64...I reflashed my Shield with factory firmware (original release) and then did OTA to update 64...when I try to mount the drive in ADB Shell it doesn't let me...any help would be greatly appreciated...
[Shield Android Development] shimp208:
To regain root access I would recommend flashing Clockworkmod Recovery for the Shield from this thread. Then once you have flashed Clockworkmod Recovery I would recommend flashing SuperSU in Clockworkmod Recovery to regain root access. Once you have regained root access if you can dump your boot partition and upload the resulting boot.img I can modify that image to allow root access :).

You can run the following command from terminal emulator to dump the boot partition to boot.img:

su
dd if=/dev/block/platform/sdhci-tegra.3/by-name/LNX of=/sdcard/boot.img

Let me know if you still have questions I'll be happy to help you out.
[Shield Android Development] Bubleman77:
I also had a failure at first attempt.

Then I have reinstall Cygwin 2.830 64bit and in "Select package" option I have added the ARCHIVE package (not installed by default).

(I believe it's mandatory to decompress the archive).

Then it succeed.
[Shield Android Development] Modjoxtrem:
Rooting process on 4.3

hi,

in regard to the rooting process, i had already unlocked the boot loader and root process went on well old android version. However after the firmware update to 4.3 android version.. the rooting process stopped working, as you had already mentioned that we are suppose to get t 2 files which is Clockworkmod Recovery for the Shield and SuperSu ( updated Ver ) ... i can't seem to find the CWMR file from the link specified !:confused:
[Shield Android Development] shimp208:
Here is the Clockworkmod Recovery Image you were looking for, let me know if your still having trouble.
[Shield Android Development] suppertime:
can't root after OTA 64

Can anyone share what they did to get root back after OTA 64?
[Shield Android Development] Gnurou:
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...
[Shield Android Development] suppertime:
THANK YOU!!!!!

:cyclops:

That was exactly what I needed. I confirm that this works flawlessly with OTA 64.

Thanks!!!!
[Shield Android Development] wrc1010:
Hello guys. After i update my shield to 64 today and i use same method to root my shield as last time before from https://github.com/linux-shield/shield-root and i can see 4 penguins on my screen, then after the shield reboot, i cant find superuser and i use the root checker to check and it just keep loading without stop.

Any idea how can i root back my shield?

Edit: Finally i manage to root my shield. After follow the method from https://github.com/linux-shield/shield-root and when finish and my shield reboot, it is actually already root but cant find the superuser only, so i try to install the supersu from google play store and my shield is root again.
[Shield Android Development] WARKRIME:
If anyone is having any trouble at all on any version then this is the option for you!!

Thank You so Much Gnurou!!!

So simple!
[Shield Android Development] XSYLUS:
Tegra Note 7 + Root

Will this method work on the EVGA Tegra Note 7 or should I wait for a more tried and true method? Thanks.
[Shield Android Development] Gnurou:
Just wait a bit more and I will update it with TN7 support.
[Shield Android Development] ricardo85x:
Does https://github.com/linux-shield/shield-root work with last shield update?
[Shield Android Development] Gnurou:
Yes, it does.
[Shield Android Development] ricardo85x:
thanks, I jus did it

edited:

In fact it is not rooted.

I saw the 4 pinguins but it is not rooted...
[Shield Android Development] Genghis_Tron:
Same problem here. My device is unlocked and when I run the command:

fastboot boot root_shield.img

I see the 4 penguins but it never appears to be rooted. I also cannot find a valid link for CWM recovery for the sheild, so that method is no go for me right now.
[Shield Android Development] Gnurou:
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 what makes you think your device is not rooted?
[Shield Android Development] Genghis_Tron:
No error messages on adb/fastboot or on the shield itself. The 4 penguins page shows everything it should (I think) with no errors. When I boot up the shield, SU is nowhere to be found and rootchecker displays a message saying the operation is taking longer than expected, like it's not rooted. Would dropping the SU APK on the shield and installing it work you think? I can give that a shot.
[Shield Android Development] zhangsta:
Would I still be able to gamestream after rooting?
[Shield Android Development] Genghis_Tron:
Yes, you should still be able to gamestream after you root.

Also, I found the solution to my problem. Turns out the device is indeed rooted, I just installed the APK and now everything works as expected.
[Shield Android Development] phunky123:
Just got mine and update to 64 then got 65 and updated, still working for 65 with the 63.img?
[Shield Android Development] shimp208:
Should still work if it doesn't you can use this then.
[Shield Android Development] Nersta:
Hello, i followed your instructions and it seems fine so far. Buuut, Superuser says the binary is outdated and i haven't root access. I want to mention that i can see the su binary in the xbin directory in es explorer.

Any suggestions?

edit: i'm on update 64

edit 2: with https://github.com/linux-shield/shield-root it works! Thanks
[Shield Android Development] gregdeberg:
Hello :)

Sorry to bother you but is this method correct to unlock the bootloader ?

Connect your device to your computer using a USB cable.

On your computer, enter the following command:

fastboot oem unlock

This will display the unlock menu. Read the disclaimer and think one last time about what you are doing. This is your last chance to stop.

As simply as this ? no boot.img or something else ?

Thank you !
[Shield Android Development] Gnurou:
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 su binary on your system partition.

So after you unlocked your device, you will still need to boot a custom image to get root (as explained in the remainder of the document you cited), but unlocking itself only requires fastboot.
[Shield Android Development] gregdeberg:
Hello :)

Thank you !

So if i understand after unlock bootloader, these steps (https://github.com/linux-shield/shield-root) will root the last rom shield version ?

Regards,
[Shield Android Development] Gnurou:
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.
[Shield Android Development] gregdeberg:
Thank you :)
[Shield Android Development] roustabout:
This was my mistake on the HP slate - I expected oem unlock to do what it said it would, and wipe the device.

The script HP set up refreshed all the files HP shipped the device with in /system but didn't wipe it, so the su I'd dropped in with Chinese tool stayed onboard.

Which is why - since I could see the boot and had root - I didn't realize my mistake until later, then read Gnurou's script, then found the Cydia impactor.
[Shield Android Development] :
please anyone can give me the adb file for the nvidia shield
[Shield Android Development] shimp208:
Which files are you specially looking for the factory restore images?
[Shield Android Development] :
Thanks for helping me i dont need the factory images....i was stuck accidentally on recovery mode in the booatloader menu.Its passed 1 hour to regain full control on my nvidia shield.I was thinking if i a enter in the recovery mode on the bootloader menu and access cwm recovery to install root (using a zip file) in my nvidia shield,i made huge mistake doing that xDDD but now im happy my nvidia shield its fine and i have root,thats all i wanted to my nvidia shield.The next time i would be handy to know how the enter cwm recovery because the thread of the cwm recovery doesnt explain that part.
[Shield Android Development] seaking177:
Even with kitkat, https://github.com/linux-shield/shield-root still works, cool!
[Shield Android Development] granduke:
Did you use this method to both unlock and root?
[Shield Android Development] seaking177:
I had it unlocked before kitkat
[Shield Android Development] Evo_Shift:
Mine just hung after I input that line of code to root. I guess I'll try again.

Edit - Second time worked. Not sure what I did wrong the first time. Oh well.
[Shield Android Development] Nikojiro:
That's good to know :D
[Shield Android Development] uoykcuf86:
I cant get it to work...

C:\>NSRoot\fastboot devices

0513713809415106AC20 fastboot

C:\>NSRoot\fastboot boot root_shield.img

cannot load 'root_shield.img' :No error

Thats what i see everytime i try...

Im on the new KitKat,CWM, and unlocked bootloader.

worked no problem on JellyBean.
[Shield Android Development] dragxdk:
hi bro, which cw has you have on your shield 4.4.2 please?

Because i have just updated on kitkat my shield and i search a method for root it... :(
[Shield Android Development] dragxdk:
Victory :victory: :good: My shield is on kitkat 4.4.2 and rooted with cw installed ;)

i ve found a method, use shield ram and respect the steps and before the third step put the zip su on your sd card and after flash it, fix it.

When the root is fixed, the cw is fixed too and when you restart your shield your cw is again here :)

enjoy : http://youtu.be/TlkfzyW8SEs

more question no problems :)
[Shield Android Development] granduke:
I'm wanting to root and I'm on update 65. I really don't want to move up to 72 and KK now.

So i could unlock, root, and keep the standard recovery which would let me easily OTA 72 when I'm ready and then probably will need to re-root.

Or do you think it is better just to update to 72 now and do the process which will make things easier for the future.
[Shield Android Development] shimp208:
It would be just be better to update to 72 now because you will want to update your device eventually so it's always better to get the hard work out of the way sooner rather then later.
[Shield Android Development] hurrpancakes:
Thank you very much for your method. Worked perfectly for me! Haven't rooted my Shield till now, so I downloaded Shield RAM, unlocked the bootloader, copied supersu.zip from the Shield RAM folder to the Shield, installed CWM, flashed the supersu, and now my Shield on 4.4 is rooted!
[Shield Android Development] dragxdk:
Yep :)
[Shield Android Development] Kite-G:
Hi, and sorry to bother. Would this manual rooting method (and bootloader unlock) work if I'm on latest 4.4 OTA?

I'd prefer doing it myself instead of using Shield RAM because I got a slow connection, so it would take me quite while to download that.
[Shield Android Development] shimp208:
The manual method for unlocking the bootloader will still work, but the root method won't work anymore unless you modify several things in the original post. Also by the time you downloaded the items required for the manual method, it would have been easier to just download the Shield RAM root method. Let me know if you still have questions.
[Shield Android Development] Kite-G:
Thanks. I really couldn't have downloaded Shield RAM since it would take me 2~ days (stuck on 3G atm) so I went ahead and tried manually. Didn't need the drivers since my SDK recognized Shield no problem. Bootloader unlocking went fine and was simple, same for installing CWM. The gripe was on rooting, since OP method wouldn't work on latest OTA (I even tried knowing) I turned to https://github.com/linux-shield/shield-root which failed the first 2 tries for no reason, but then I unplugged and plugged back in the Shield, and it worked. Though I lost CWM in the process, so I re-flashed it. Now working and rooted.