Database Info

Thinking about unrooting Read this first!!!! ALL MODELS

**********Please Sticky**********
(MOTOROLA HAS RELEASED ALL THE IMAGES FOR ALL COUNTRY VERSIONS OF THE XOOM RECENTLY MAKING THIS A UNIVERSAL TUTORIAL AT THIS POINT)
Listen I notice recently there is a flood of issues with the xoom using different unrooting methods. I personally will say to unroot your device just bring it back to stock images. Its the safest method with the other methods if you do not know what you are doing you will find yourself sending your device to motorola for warranty repairs.
Here is a short and sweet way to unroot your xoom. by doing this you will lose your data and information so start by backing up your stuff to a computer if you have any important things on there.
if starting fastboot is on your xoom screen open up a command prompt:
0. For those who've modified their boot splash graphic with Team Eos' Splash Screen Logo Maker make sure to restore the stock Motorola boot splash FIRST as this process doesn't touch that part of the system. (Posted by Bait-Fish *Thanks for the update*)
1. Goto: http://forum.xda-developers.com/showthread.php?t=1049485 for stock USA 3G and Wifi Images
2. download the files you need
3. extract all the img's into the tools folder
4. with the command prompt open type: cd "replace with tools directory location"
5. disconnect your xoom from your computer and shut off the xoom
6. at the prompt type: fastboot oem unlock
7. it will say waiting for device
8. now plug it into your computer and reboot into fastboot by holding the down volume button and power on
9. follow the on screen instructions and agree to everything
10. your device will reboot you will get the motorola dual core window
11. force restart device by holding volume up and pressing the power button right after the device shuts off hold the down volume button and press power button
12 you should now be in fastboot mode
13. then copy each line one by one into the command window. This will allow you to go back to factory settings like you bought it from the store
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Note: If no userdata.img file is present in your download, please issue the command:
fastboot erase userdata

Good write up. +1 for sticky if there's not something already.
Sent from my SPH-D700 using XDA Premium App

whats good about this post is that it has been fully tested by me with wifi and 3G versions of the xoom with no problems reported. This method has also fixed some RSD issues. I say some because some people have flashed wrong boot images and ruined fastboot on their xooms from seeing the desktop.

wow you would think with all the issues happening with oneclick root etc you would think this would be a highly read thread. lol.

Nice guide man.

Good to have a thread like this as I was one of those one-click rooters. Unrooted, semi-bricked and learned ADB. If you're going to play with your Xoom, at least have a general idea of ADB.

Please add that this instruction (original post) is only appliable to US Xooms. Not EUs

Thanks!
Thank you so much!
I was also a clueless one-click rooter. I'd tried everything to get rooted again. This was by far the clearest and saved my hanging around waiting for a one-click unroot solution.
Cheers

your welcome enjoy your xoom.

I already upgraded to 3.1, and I unlocked it, but I can't get CWM to work, so I can't root. Can I use this method to go back to the older HC and relock, then go back to 3.1? I bricked mine before, trying to unroot and relock (I know...I know...) I've been adb'ing like crazy trying to get CWM to work, but I feel like giving up and going back to lock, stock, no barrel.

you can if you want it wont hurt the xoom which xoom do you have wifi or 3g?

I have the wifi, running 3.1, build HMJ37

if you go back to 3.0.1 you can root it, install clockwork, then upgrade to 3.1 using clockwork method. its pretty simple. within 25-30 minutes you can be running with clockwork and 3.1 rooted.

I learned my lesson! And the forum saved me.
I did the one-click root back when I got my Xoom a couple months ago, and then when I tried un-rooting and relocking to get the 3.1 update, I bricked it (you're welcome, angel) and sent it back to Motorola. When I got it back, I tried rooting the long way, but couldn't push CWM onto it. I got lots of help and tireless support from a forum member, and finally got it unlocked, rooted, CWM'd with SD support....re-lovin' the Xoom now. And I'm glad the guy that helped me out made me re-check re-download, and redo everything just to make sure we weren't missing any steps.
I love the Xoom NOW, but when I got it back from getting fixed, I was so not happy with it being unrooted! I love to toy with stuff, and this was a real learning experience. Doing all the commands, getting the stock images, re-flashing....it was very rewarding, even though it took so long to figure out how I screwed up. (can you believe it was a usb cable that wasn't working that made it so difficult! Pushed some things, but not others....changed cables, and everything worked fine.)

Nice walk through. I don't think I'll be unrooting anytime soon but its good fyi.
Sent from my Xoom using XDA Premium App

this tutorial should be more helpful now.

dirtymindedx said:
this tutorial should be more helpful now.
Click to expand...
Click to collapse
You could link to my sticky instead of moto if you want. Its the same 20 images but you don't have to login.
Sent from my Xoom

bwcorvus said:
You could link to my sticky instead of moto if you want. Its the same 20 images but you don't have to login.
Sent from my Xoom
Click to expand...
Click to collapse
how do i go about doing that.

dirtymindedx said:
how do i go about doing that.
Click to expand...
Click to collapse
I would just edit line 1 to say you can get from moto at blah blah or download from blah blah so you don't have to log in.
http://forum.xda-developers.com/showthread.php?t=1049485
Sent from my Xoom

nice set of links definitely treasure in my book. Can you post a link on there to this thread since they still haven't stickied this yet?

Bricked PLEASE HELP REALLY PLEASE IM BEGGING :(

Eee Pad is bricked. Here's the story. I used http://forum.xda-developers.com/showthread.php?t=1125714 (pure root) to root the device about less than a month ago.
Just today i saw an update for the OS and i updated, but when i turned it back on it was bricked. WHAT DO I DO? PLEASE HELP

try this
turn off your TF
plug it to your computer
turn on your TF while holding the "up" volume key
if your computer detects your TF, then good news, there's hope for you. your TF is not bricked, and you still have access to NVFLASH.
you can use it to restore your TF into a functional state in many ways.
one of those ways is enumerated here: WARNING, this will erase all your data.
http://forum.xda-developers.com/showthread.php?t=1123429
remember that the image files gets extracted to the same folder as the .bat or .sh files, (some people misplace them and think it didn't work)
Sent from my Transformer TF101 using Tapatalk

ilive12 said:
Eee Pad is bricked. Here's the story. I used http://forum.xda-developers.com/showthread.php?t=1125714 (pure root) to root the device about less than a month ago.
Just today i saw an update for the OS and i updated, but when i turned it back on it was bricked. WHAT DO I DO? PLEASE HELP
Click to expand...
Click to collapse
I agree with finalhit about how to fix it, but am curious what you actually did where you say " Just today i saw an update for the OS and i updated ". ?
Did you apply an OTA update, apply some other thing , and if so, which other thing? You might just be a quick partition 5 nvflash from success (restoring CWM to a reasonable version for your system). Which flavor of TF? US, WW, TW? more info.

THANKS IT WORKED!
Well actually it was my father who updated. I rooted his TF for him (to get netflix working) back on 3.1, and today he just decided to update OTA to 3.2 (the US version.). Glad its working again or i would have been screwed

[GUIDE] How to fix "Failed image LNX 0x0002 / RSD mode 2

I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!

mowassasin said:
I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!
Click to expand...
Click to collapse
So I went and bought the factory cable from the Black Hat guys, and luckily haven't had the need to use it. Any advice you'd like to give in case I need to at some point?

I guess the only advice I can give is: don't re-lock the boot loader when you have a custom rom loaded

You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk

bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
It wouldn't recognise any fastboot commands nor the RSD Lite program for me.
But if it does, then thats good.
Merely a heads up for those who were in the same situation I was

bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.

yaturner said:
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.
Click to expand...
Click to collapse
Over the course of a few hours I was able to fix this, so I am going to write this little walkthrough for you using a rom from bwcorvus's page (CLICK HERE) and then used the guide from dirtymindedx -(CLICK HERE)
The reason it took me this long (as well as doing other things) was because I used the wrong set up to unroot my tablet. I was using the Unofficial images that are on bwcorvus's link. Because I didn't read thoroughly enough in his breakdown, I made myself look like a fool...
What you want is NOT
UNOFFICIAL STOCK IMAGES
Click to expand...
Click to collapse
because you will not be able to lock the bootloader (IF you want it to be that way, which I did, and so it gave me a 0x000004 Error, and yes i see that you are having a 0x000002 but somewhere i read this could help that.) I just wanted to get rid of Clockwork Recovery Manager cause it was not working on my 3.2 rooted tablet, and thought that because i messed up teh whole image with playing around and upgrading and seeing how i could break the image without overclocking, i thought i should actually try and make it back to stock too. With this... I needed to do these steps...
1. Upgrade the Motorola drivers while the XOOM was plugged in, so then I would be able to use the Fastboot Correctly.
2. Download the correct roms for my tablet, (Wi-Fi is mine, just grab the one that fits your version and just follow along.)
3. Upgrade my ADB from google because for soem odd reason my fastboot did not like the xoom till i did that...
4. Used the STOCK CABLE. I can Confirm that the STOCK CABLE that allows you to recharge the phones, WILL WORK for this...
5. Once the ADB was set up, I restarted it, aka Hit the red X and then loaded it back up and then closed it again, just to make sure the services were updated somewhat...
6. Opened Command prompt and navigated to the folder that help the zipfile for the fastboot flashing guide (aka dirtymindedx's guide at the top), be using CD (Drive Letter):/location/of/the/folder/that/is/unzipped
7. I then checked over the information in the folder by using dir /a and then proceeded to read through the guide
7-1. A note here... I did the fastboot erase userdata instead, because I wanted to see if it would brick it again... (sorry, I was in a fowl mood with the world last night so I was waiting for it to get bricked so i had a reason to use it as an ice scraper on my car... (not like i would really do it... just wanted a reason for justification haha)
8. ???
9. Profit
This is only to get rid of a "already slightly bricked" device... which I had done after relocking the Rom that was not official to Motorola and now, after a few updates, i now have Android 4.0.3 for the Xoom that was OTA'ed, looking to see how easy it will be to root to reload my rpg game saves that i got caught up in (hence my disappearance from the forums haha...) but I hopefully helped you out in a direction to heads towards... and as long as you don't lock the boot-loader (which someone posted about it before i did...) you should be fine with any changes to the rom after the updates... Also, you can skip steps on this too... you can just flash the image and not the recovery menu and so forth, allowing you to keep other settings that are not part associated to the rom image.
Also sorry for the insanity in my words... I have been up for a good 36 hours with a half hour nap somewhere in there...

[Q] Stuck @ Boot Screen

Hey Everyone
I've done quite a bit of reading and nothing seems to quite fit the issue I am having so I thought I'd post and seek help.
Some background info...I've unlocked the bootloader and also generated the NVFlash files when I first bought the tablet. It was running the stock ICS Rom. I had CWM Recovery and it was rooted.
I wanted to try a new ROM called BlueAndroid as I read it was really good. I followed all of the instructions and flashed from the sdcard. It appeared successful but when I went to restart the system, it kept boot looping at the ASUS Screen. Then I thought I'd just go back to what I had before by restoring it from CWM Recovery but to my surprise, it didn't work and now it isn't even looping, just stuck on the ASUS Screen.
I tried to fastboot CWM and TeamWin Recovery. Although they were both successful writes to the tablet, they won't load. I can only get to the fastboot screen where it shows the 'wipe data' and 'USB icon'. There used to be an Android Robot icon too but it is gone now.
I even tried to NVFlash. It worked but I'm still stuck on Asus Screen.
Lastly, when I select wipe data, it erases and the Team WIN logo appears for a split second and then it goes back to Asus Screen.
I keep reading something about the possibility of incorrect partitions but I have no idea what that means.
Any help would be greatly appreciated.
Thanks
A
P.S. In the meantime, is there any way to shut the tablet off? I've tried holding the power button down but it just reboots.
Solved: Used blobunpack to get bootloader files from the stock ICS ROM (blobunpack the blob file from the ROM). Then used NVFlash to download those files to tablet. Hope this helps others with same problem. I can elaborate more tomorrow...it is really late and very sleepy but relieved!

xxboarderxx said:
Hey Everyone
I've done quite a bit of reading and nothing seems to quite fit the issue I am having so I thought I'd post and seek help.
Some background info...I've unlocked the bootloader and also generated the NVFlash files when I first bought the tablet. It was running the stock ICS Rom. I had CWM Recovery and it was rooted.
I wanted to try a new ROM called BlueAndroid as I read it was really good. I followed all of the instructions and flashed from the sdcard. It appeared successful but when I went to restart the system, it kept boot looping at the ASUS Screen. Then I thought I'd just go back to what I had before by restoring it from CWM Recovery but to my surprise, it didn't work and now it isn't even looping, just stuck on the ASUS Screen.
I tried to fastboot CWM and TeamWin Recovery. Although they were both successful writes to the tablet, they won't load. I can only get to the fastboot screen where it shows the 'wipe data' and 'USB icon'. There used to be an Android Robot icon too but it is gone now.
I even tried to NVFlash. It worked but I'm still stuck on Asus Screen.
Lastly, when I select wipe data, it erases and the Team WIN logo appears for a split second and then it goes back to Asus Screen.
I keep reading something about the possibility of incorrect partitions but I have no idea what that means.
Any help would be greatly appreciated.
Thanks
A
P.S. In the meantime, is there any way to shut the tablet off? I've tried holding the power button down but it just reboots.
Solved: Used blobunpack to get bootloader files from the stock ICS ROM (blobunpack the blob file from the ROM). Then used NVFlash to download those files to tablet. Hope this helps others with same problem. I can elaborate more tomorrow...it is really late and very sleepy but relieved!
Click to expand...
Click to collapse
I had the same problem. I think it is bricked. I called ASUS, told them it was unlocked, they told me to ship it to them and they would fix it. I boxed it up, and shipped it off. Could not turn it off. Hope the box did not catch on fire.

OP, where were you a week ago when I "bricked" my tablet?
I had the -exact- same issue, btw, although with different circumstances. I can verify with 100% confidence that using NVFlash successfully restores the ICS bootloader. How I understand our situation is that when you tried to flash a ROM or anything based on JB over an ICS-device, it confuses things and causes issues. So you basically have to restore the ICS bootloader to get any progress.
But you hit the nail on the head describing my problem, although I would have ended up typing a dissertation to get across the same information you did. So touche on that
I used the same steps, as well. I blob unpacked my ICS stock firmware (.29 version from ASUS website). I used the boot.blob from my NVFlash files, along with the files I unpacked from the stock blob and flashed them over NVflash.
After a week of a useless tablet, I'm up and running.
I'm going to write a guide about my experience for anyone else and I would welcome your input sir.

I think you could mean a kind of recovery loop: There is a file called "command" on the cache partition which causes the recovery image to boot. But if the recovery is broken then it will not empty cache. The recovery will boot but does not update screen (showing just boot splash). On the next time it will boot again ...
Please be just carefully: "wipe data" in the fastboot menu will create the "command" file.

ScottBroker said:
I had the same problem. I think it is bricked. I called ASUS, told them it was unlocked, they told me to ship it to them and they would fix it. I boxed it up, and shipped it off. Could not turn it off. Hope the box did not catch on fire.
Click to expand...
Click to collapse
Sorry...if I could have made this attempt last week, I may have been able to help you then. :sly:
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

opethfan89 said:
OP, where were you a week ago when I "bricked" my tablet?
I had the -exact- same issue, btw, although with different circumstances. I can verify with 100% confidence that using NVFlash successfully restores the ICS bootloader. How I understand our situation is that when you tried to flash a ROM or anything based on JB over an ICS-device, it confuses things and causes issues. So you basically have to restore the ICS bootloader to get any progress.
But you hit the nail on the head describing my problem, although I would have ended up typing a dissertation to get across the same information you did. So touche on that
I used the same steps, as well. I blob unpacked my ICS stock firmware (.29 version from ASUS website). I used the boot.blob from my NVFlash files, along with the files I unpacked from the stock blob and flashed them over NVflash.
After a week of a useless tablet, I'm up and running.
I'm going to write a guide about my experience for anyone else and I would welcome your input sir.
Click to expand...
Click to collapse
Well, I'm sure you learned a lot during your experience of trying to get it working again - I know I did so that's a +1. I wasn't worried that my tablet was bricked because I was told that if I had the NVFLASH files, I could recover from anything save dropping it and breaking it that way. I was also able to connect to the PC using fastboot and adb so that was another positive.
If you write a guide, that would be great as while I was trying to piecemeal information together to get my tablet running again, there seemed to be dozens of people out there with a similar problem and being unable to get it working again and having to send it off to Asus. Would probably be a great contribution.
The one thing I learned though this ordeal is that the stock bootloader needs to be the same as the custom ROM before installing. I wish ROM guides would tell you this REALLY important fact...
Cheers
A
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

xxboarderxx said:
Well, I'm sure you learned a lot during your experience of trying to get it working again - I know I did so that's a +1. I wasn't worried that my tablet was bricked because I was told that if I had the NVFLASH files, I could recover from anything save dropping it and breaking it that way. I was also able to connect to the PC using fastboot and adb so that was another positive.
If you write a guide, that would be great as while I was trying to piecemeal information together to get my tablet running again, there seemed to be dozens of people out there with a similar problem and being unable to get it working again and having to send it off to Asus. Would probably be a great contribution.
The one thing I learned though this ordeal is that the stock bootloader needs to be the same as the custom ROM before installing. I wish ROM guides would tell you this REALLY important fact...
Cheers
A
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
Really? I didn't know that....that might explain why none of the ROM's I'm flashing will work.....
At this point, I'm just going to upgrade to the stock JB firmware and flash the new JB roms. I've got my NVFlash ICS files (which saved my frickin life) so I have no hesitations about doing anything, and I really understand the NVFlash process well having bricked myself so hard.
My guide is mostly done. I spent more time writing it than I did focusing on schoolwork so I will finish it up hopefully this weekend. It's rather long and quite details so I hope it will help everyone.

I was smiling as I read the first post, but this is going to come in real handy if I nuke my bootloader. Thanks. I wish I had gotten to this first, heh, I could have told you don't flash a Jellybean ROM over an ICS bootloader, it won't boot.
Good information to have though. Thank you!

opethfan89 said:
Really? I didn't know that....that might explain why none of the ROM's I'm flashing will work.....
At this point, I'm just going to upgrade to the stock JB firmware and flash the new JB roms. I've got my NVFlash ICS files (which saved my frickin life) so I have no hesitations about doing anything, and I really understand the NVFlash process well having bricked myself so hard.
My guide is mostly done. I spent more time writing it than I did focusing on schoolwork so I will finish it up hopefully this weekend. It's rather long and quite details so I hope it will help everyone.
Click to expand...
Click to collapse
:good:

Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that

elesbb said:
Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that
Click to expand...
Click to collapse
You can do it if you have a custom recovery already flashed like TWRP or CWM. But I agree with you - after you start having a basic understanding of Android customization, there's no reason why you would want to use 'wipe data' from the volume down+power.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

elesbb said:
Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that
Click to expand...
Click to collapse
That finally explains why it wouldn't work, thank you for elaborating on that!!
Is there a guide on how to get the stock recovery back, or does it automatically get flashed when you flash stock?

opethfan89 said:
That finally explains why it wouldn't work, thank you for elaborating on that!!
Is there a guide on how to get the stock recovery back, or does it automatically get flashed when you flash stock?
Click to expand...
Click to collapse
Automatically gets flashed when you flash stock.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

If you are in recovery loop you cannot go into the fastboot menu. The only way to get the stock recovery back is to use nvflash.

Purchased a Shield K1 Tablet: Should I Root?

Purchased a Shield K1 Tablet
Which will arrive this week, and there are things I would like to know about it, i.e notably on whether or not I should unlock and root it, despite the potential risk of doing so.
What I plan on using this for is primarily emulation (Snes through PSP and maybe Dolphin, no idea how well that works yet) That being said, are there things I should do to it?
Do as in, things I can root or flash to give myself the best possible experience, to get the most out of this? I've seen a lot of custom ROMs, Cyanogenmod (which I have on my
Nexus 7 2012, along with a dual boot OS). I have been thinking about having the stock Android 5.1.1, alongside Android 4.1.2 for the sake of Wii remote support since Google
foolishly broke that part of Bluetooth (and the part that never will be fixed again). The problem is, I don't know how hard or cumbersome it would be to do such a thing
without bricking the Shield tablet and ending up with a pricey paperweight. What tutorials, guides, etc should I look into before I consider such an undertaking? I want
to be sure I pick the right files and OS image(s) to install so I can do this right, if that makes sense.

I just bought it too and was coming from a Nexus 7 2012.
Rooted with the latest CM 12.1 nightly, no issues so far.
Wifi is slowish/buggy and the touchscreen has some issues, but afaik these issues are there on stock, too.
Just get the latest CM12.1 from their site, flash it with TWRP. I had issues with open gapps and ended up using CM's gapps.

koichirose said:
I just bought it too and was coming from a Nexus 7 2012.
Rooted with the latest CM 12.1 nightly, no issues so far.
Wifi is slowish/buggy and the touchscreen has some issues, but afaik these issues are there on stock, too.
Just get the latest CM12.1 from their site, flash it with TWRP. I had issues with open gapps and ended up using CM's gapps.
Click to expand...
Click to collapse
Fair enough, and I know that no device is perfect, everything has their own set of issues, so I don't think I'll regret getting a Shield Tablet, that much I know. I was going to get a Samsung Tab E 9.6, but the specs just didn't figure, esp. for someone who wants more power, you know? What about the Android OS ROM you install it with? Should I go with Android 5.1.1 or dual boot it with 4.1.2 instead so I can have Wii remote support? Thanks.

I don't know, that's your choice. I don't have that requirement, so I went with CM12 (5.1.1), single OS

koichirose said:
I don't know, that's your choice. I don't have that requirement, so I went with CM12 (5.1.1), single OS
Click to expand...
Click to collapse
Fair enough, I'll keep looking around the forums to gauge what I need to do. I can't help but feel a bit nervous on rooting and voiding the warranty on a device I just spend 200 bucks on, maybe that's just me though :laugh:

the_randomizer85 said:
Fair enough, I'll keep looking around the forums to gauge what I need to do. I can't help but feel a bit nervous on rooting and voiding the warranty on a device I just spend 200 bucks on, maybe that's just me though [emoji23]
Click to expand...
Click to collapse
Nvidia has stated that it will still honor the warranty despite it being unlocked or rooted in most cases. I'm just gonna guess that unless you accidentally wipe your bootloader, or use an overclocked kernel that fries it you should be good. What they said is if YOU fubar it that voids the warranty, but if it's anything normally covered by warranty your good.
That said, I rooted, unlocked, and installed an oc kernel as well as recovery within an hour of receiving mine and it runs beautifully. Better than pure stock actually.
Sent from my SM-G386T1 using Tapatalk

Exile1975 said:
Nvidia has stated that it will still honor the warranty despite it being unlocked or rooted in most cases. I'm just gonna guess that unless you accidentally wipe your bootloader, or use an overclocked kernel that fries it you should be good. What they said is if YOU fubar it that voids the warranty, but if it's anything normally covered by warranty your good.
That said, I rooted, unlocked, and installed an oc kernel as well as recovery within an hour of receiving mine and it runs beautifully. Better than pure stock actually.
Sent from my SM-G386T1 using Tapatalk
Click to expand...
Click to collapse
Okay, I wasn't 100% sure, only device ever rooted and unlocked was a Nexus 7 2012, never had a problem with it once I got it up and running. I don't feel comfortable with OC at all, as the power is
definitely more than enough for my needs, if that makes any sense. That being said, I don't know what kernel I need since this is my second time ever doing something like this, a little green in the gills so to speak (sad, I know). Anyways, would you guys advise to having dual boot install on this, or just a better 5.1.1 Android ROM than the stock version? I feel a bit overwhelmed at it all, and I don't know what tutorial I should truly follow, that's why I feel overwhelmed, you know?
Reasons for the tablet:
1 - The specs are insanely powerful for emulator apps, my Nexus 7 struggles with even 2D PSP games and some PSX games, lots of stuttering in the audio department, so my primary use is gaming
2 - Multimedia, movies, YT, music and so on
So really, I don't need anything fancy OS wise, just enough to help get the most out of it without having to overclock the hardware. What order would I need to do everything in? Are there good step by step guides for people like me?

http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
INSTALL DRIVER
-enable Developer Options
-enable Debugging Bridge
-do a 'adb devices' and check the dialog on your mobile and allow it 'every time'
-shutdown
-hold Volume down and Powerbutton at same time
if the bootloader showed up
-do a 'fastboot devices' if it shows your device online then
-do 'fastboot oem unlock'
after that you have flash your recovery
go to the directory where the file is and
-do 'fastboot flash recovery your_file_here'
after that you can reboot to bootloader and go to recovery
copy the SuperSu.zip which you downloaded at chainfires site or on xda and push it to your internal memory (/sdcard)
and flash it over recovery.
reboot enjoy!
the_randomizer85 said:
Okay, I wasn't 100% sure, only device ever rooted and unlocked was a Nexus 7 2012, never had a problem with it once I got it up and running. I don't feel comfortable with OC at all, as the power is
definitely more than enough for my needs, if that makes any sense. That being said, I don't know what kernel I need since this is my second time ever doing something like this, a little green in the gills so to speak (sad, I know). Anyways, would you guys advise to having dual boot install on this, or just a better 5.1.1 Android ROM than the stock version? I feel a bit overwhelmed at it all, and I don't know what tutorial I should truly follow, that's why I feel overwhelmed, you know?
Reasons for the tablet:
1 - The specs are insanely powerful for emulator apps, my Nexus 7 struggles with even 2D PSP games and some PSX games, lots of stuttering in the audio department, so my primary use is gaming
2 - Multimedia, movies, YT, music and so on
So really, I don't need anything fancy OS wise, just enough to help get the most out of it without having to overclock the hardware. What order would I need to do everything in? Are there good step by step guides for people like me?
Click to expand...
Click to collapse

wiQbold said:
http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
INSTALL DRIVER
-enable Developer Options
-enable Debugging Bridge
-do a 'adb devices' and check the dialog on your mobile and allow it 'every time'
-shutdown
-hold Volume down and Powerbutton at same time
if the bootloader showed up
-do a 'fastboot devices' if it shows your device online then
-do 'fastboot oem unlock'
after that you have flash your recovery
go to the directory where the file is and
-do 'fastboot flash recovery your_file_here'
after that you can reboot to bootloader and go to recovery
copy the SuperSu.zip which you downloaded at chainfires site or on xda and push it to your internal memory (/sdcard)
and flash it over recovery.
reboot enjoy!
Click to expand...
Click to collapse
So I just follow the guide on the thread, or do I follow the guide you just posted?. The reason I ask is because in the thread's guide, past the parts where it said to install the ADB driver and then the USB drivers for the device, I'm not sure what "debugging bridge" is, unless you meant enable USB debugging, IDK.
- Enable USB developer mode
- Enable USB debugging
- Copy the recovery image and supersu.zip to where the ADB install folder is
- Open the program to open a CMD window to the install location
- Type "adb reboot bootloader"
- Etc
I mean, because the two guides are confusing me more, the forum guide, the thread, how it's worded...now I don't know. Sorry. Is that thread and your guide the same thing, all leading to ultimate unlock and root the device using ADB and the recovery image? And is it not feasible to install Android 4.1.2 as a dual boot OS image so I can test out the Wii Classic Controller since Google broke that part of the Bluetooth code in 4.2+?

there is another tutorial from SuperPichu I think. this is the best for my understanding but I didn 't find it , up in hurry(?)
http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
and yes. usb-debugging

wiQbold said:
there is another tutorial from SuperPichu I think. this is the best for my understanding but I didn 't find it , up in hurry(?)
http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
and yes. usb-debugging
Click to expand...
Click to collapse
Okay, that thread says flashed to OTA 2.0 already, not entirely sure what that means, to be honest, or of the bootloader is locked on it, haven't gotten it yet. I take it I follow the first thread you posted, then
the one above?

the_randomizer85 said:
Okay, that thread says flashed to OTA 2.0 already, not entirely sure what that means, to be honest, or of the bootloader is locked on it, haven't gotten it yet. I take it I follow the first thread you posted, then
the one above?
Click to expand...
Click to collapse
it is a old thread. It s for kitkat..
I think you go like I said.
be sure. adb drivers are installed
Developer Options
Usb debugging
cmd
'adb devices'
check dialog
'adb reboot-bootloader'
'fastboot devices'
look for output
'fastboot oem unlock`
'fastboot flash recovery /directory/to/your-recovery-file'
'fastboot reboot-bootloader'
go to recovery
flash SuperSU.zip
reboot

wiQbold said:
it is a old thread. It s for kitkat..
I think you go like I said.
be sure. adb drivers are installed
Developer Options
Usb debugging
cmd
'adb devices'
check dialog
'adb reboot-bootloader'
'fastboot devices'
look for output
'fastboot oem unlock`
'fastboot flash recovery /directory/to/your-recovery-file'
'fastboot reboot-bootloader'
go to recovery
flash SuperSU.zip
reboot
Click to expand...
Click to collapse
And I go into recovery mode by holding vol. down and power, right? And in that mode I flash the SuperSu.zip correct? And I did get the recovery.img from nVidia's source, which I assume is the one I use in Command. Okay. Rebooting I assume is well, heh, also by holding down power. I also noticed both of those threads have the OS name Lollipop in the thread title.