[SOLVED-Question] Little question prior rooting my 2017 Shield pro - Shield Android TV Q&A, Help & Troubleshooting

Hi there,
i got a little question prior rooting my Shield TV 2017 pro.
I read a bit about the L1 +L2 Widivine keys on the shield so my question is, does rooting the shield has any influence with the keys, for example will Amazon + Netflix 4k stream work after?
The second question is, is twrp on the shield able to create a backup of thoose partitions in case the hdd bricks or something went wrong during flashing?
EDIT:
In case anyone needs the answer, too just read the two following posts by lavero.burgos and mr-tee and some warnings from ichijoe in 3rd, which are very detailed and helpfull
Thanks in advance
JeckyllHavok

Hello, the answer is NO, rooting your device will NOT mess with your keys nor damage them, simply because as systemless root it only safely modify boot.img and the rest goes to the data partition, so it won't touch sensitive data. The recommended method is to install SuperSU which is developed by Chainfire (the guy know what he does, he's an excellent dev).
Netflix and Amazon work for me with root, but yes there are services out there with their own apps that don't allow root. If they detect root you won't be able to play their content (IMO bad practice, i would change service if that is the case).
About TWRP, no it won't allow you to backup the relevant partitions because TWRP handle standard partitions that every Android device has, so unless someone makes a custom TWRP to include that the only way i know off is running dd comands from linux distro to backup the needed partition(s). I have done it myself in the past (many years ago) with the old Nook Tablet.
I made videos about that but you first need to know the partition block name, for example mmcblk0p8, once you have that info you can go to YouTube and search how to backup partitions with dd command and also check the following playlist where you can find the videos i made long ago:
Community Forums: http://www.youtube.com/playlist?list=PL216837379418927A
I'm very curious why many 500 PRO users have bricked their devices. What you really need to be careful with is the bootloader (blob file), don't mess with it. You can no longer downgrade bootloader from Nougat or newer to MM or older and in case you want to upgrade your hdd with a ssd and clone it then you also have to prepare to damage your device in the way.
I only have the 16GB 2015 model but would be great if someone post a screenshot of the famous backup a user has posted for the 500GB PRO, i would like to see what is inside.
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

First of all I would say, try root first, see if it affects the apps you want to use.
Don't FLASH TWRP, yet tell fastboot to boot the recovery image. But even flashing it won't harm anything. There are stock ROMs on the nvidia developer website, with the original recovery image, so you can always flash back the stock recovery, but well, not flashing a different recovery will save some effort and time.
If you have installed supersu you'll be able to fully UNROOT inside the supersu app. So, first try it out, without changing any system files, see if the apps you use work, then you could consider going further with customizations. But you can always return to stock, just don't mess around with files outside the system or vendor folder. And especially not the bootloader (blob). But there is a blob file inside the official stock ROM from nvidia.
One warning: DON"T use the flash-all.bat file included in the nvidia ROM.. use the commands manually...!!

Thanks for the detailes answers, yeah i know about dd commands, and fastboot or adb, just wanted to be sure that nothing strange happens.
Cause i never got any Widevine L1 certified device
So tonight rooting a shield...

To answer some of your questions.
Rooting will NOT mess with your Keys directly. But, sooner or later nVIDIA are going to start lobbing Updates again. And, if you have a setup which involves say a 4k (2160p) TV*. Then you CAN NOT just simply load up TWRP from some location. To do your business (i.e. rooting it), then exit back out and leave the Shield otherwise stock. (e.g. you never actually replaced 3e (or whatever nVidia calles the Recovery, with TWRP.)
This does not mean that you can not install (i.e. replace) 3e, with TWRP, and then just boot into that. That, would work perfectly, and that's what got me into the deep Dodoo.
Again whatever you do DO NOT replace your Recover with TWRP! Sooner or latter this will bite you in the 455! The moment when nVIDIA decide to push out an update, and sends your Device into a bootloop. Which will make you want to downgrade, and then hardbrick the Device.
But, beyond all that, there are plenty of other good reasons to make that backup of the original SSHD. Beyond having a simple backup of just the Keys. As these Drives, like all Drives eventually fail.
* I gather those with them old fangled 720p, 1080p Sets out there will NOT have this problem. Which I can confirm, as I can load up TWRP just fine over the fastboot command line on my Old Man's 1080p Samsung. Alas back home it's just the One 4k Set. And that will not work. Unless loaded directly on the Device.

Ichijoe said:
To answer some of your questions.
Rooting will NOT mess with your Keys directly. But, sooner or later nVIDIA are going to start lobbing Updates again. And, if you have a setup which involves say a 4k (2160p) TV*. Then you CAN NOT just simply load up TWRP from some location. To do your business (i.e. rooting it), then exit back out and leave the Shield otherwise stock. (e.g. you never actually replaced 3e (or whatever nVidia calles the Recovery, with TWRP.)
This does not mean that you can not install (i.e. replace) 3e, with TWRP, and then just boot into that. That, would work perfectly, and that's what got me into the deep Dodoo.
Again whatever you do DO NOT replace your Recover with TWRP! Sooner or latter this will bite you in the 455! The moment when nVIDIA decide to push out an update, and sends your Device into a bootloop. Which will make you want to downgrade, and then hardbrick the Device.
But, beyond all that, there are plenty of other good reasons to make that backup of the original SSHD. Beyond having a simple backup of just the Keys. As these Drives, like all Drives eventually fail.
* I gather those with them old fangled 720p, 1080p Sets out there will NOT have this problem. Which I can confirm, as I can load up TWRP just fine over the fastboot command line on my Old Man's 1080p Samsung. Alas back home it's just the One 4k Set. And that will not work. Unless loaded directly on the Device.
Click to expand...
Click to collapse
Thanks for the hints, the way i would root the shield would be:
-Unlock Bootloader
-fastboot boot twrp.img
-flash the su stuff
I got no need atm to replace recovery, so i keep it stock, just want root for droid mote, launcher and maybe xposed, and a dd backup of the whole shield hdd

JeckyllHavok said:
Thanks for the hints, the way i would root the shield would be:
-Unlock Bootloader
-fastboot boot twrp.img
-flash the su stuff
I got no need atm to replace recovery, so i keep it stock, just want root for droid mote, launcher and maybe xposed, and a dd backup of the whole shield hdd
Click to expand...
Click to collapse
As long as you do NOT replace the Recovery with TRWP. But, just call it up though Fastboot ~boot recovery <path to TWRP> then you should be nearly 100% safe.
But, having learnt my own lessens I would personally recommend leaving the Shield alone I'm not sure what good Rooting it actually has. And I'm a very big fan of AdAway, but AdAway just doesn't seem to do jack on the Shield. And, though you have to root to add Unofficial channels to Plex. At the end of the day. Those Channels have like for like Kodi Addons.
But again as long as you don't flash (replace) the stock Recovery with TWRP, you should be ok. Assuming an Update rolls along, (as they do), you should just be able to load up TWRP, like before, and flash SuperSU, and then go on with your business.

JeckyllHavok said:
Thanks for the hints, the way i would root the shield would be:
-Unlock Bootloader
-fastboot boot twrp.img
-flash the su stuff
I got no need atm to replace recovery, so i keep it stock, just want root for droid mote, launcher and maybe xposed, and a dd backup of the whole shield hdd
Click to expand...
Click to collapse
Those steps are correct, just know that in a 500gb PRO model unlocking the device will securely wipe your device and that task takes around 2 hours to complete in that specific model.
You can also use adb to sideload SuperSU package while in TWRP (Advanced >> ADB sideload):
adb sideload supersu_package_name.zip
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

Related

Asus Transformer EPIC NOOB GUIDE.

In the process of updating information for ICS update and custom ROMs, please hold tight!
A lot of folks have been coming in with newly purchased TF101's lately, which is AWESOME, it means the community will go on longer than the expected life of the device probably, since the TF201 and TF700 have come out and are seeking to replace our beloved TF, this is good news that people still buy the OG Transformer.
That said, there have been the same problems posted by new users, over and over, and sure there are guides for just about everything. But why not one on..just...EVERYTHING?
Here we go, troubleshoot problems and learn your device, the noob way! The EPIC TF101 THREAD BEGINS!
All the typical disclaimers apply, if you mess your stuff up, it is your fault not mine. I did not discover any of these methods, develop any of these tools, or do anything else but compile it all in one epic post. This should be everything you need to know as a noob, I do not take credit for anything, except for making it all easily accessible to those who are unwilling/unable to spend the hours searching that I did. In other words, I did a lot of work for you, but others had done the work for me first. Full credit to them.
What is ROOTING? And why do it?
So you bought a new TF, and you want to root it? Or you want to know what rooting is, for that matter? Rooting is a method of obtaining what is called 'Root Access' to your device, giving you control of it. The 'Root' is the parent directory of your device's internal memory, where the system files are stored. Generally this is kept from your access, you will need to get your device 'rooted' in order to change the system. Once rooted, you will have an app installed called 'Superuser' which will selectively grant applications permission to alter or access your root directory. This method differs on every device, but don't worry- we have a very easy device to root.
VERY IMPORTANT! Do NOT use any of the tools here WHILE YOUR DOCK IS PLUGGED IN!! All these are for use with the TF101 unit BY ITSELF! Please don't brick your device or mess something up by trying it with the dock plugged in!
There have traditionally been several ways to accomplish this for our device, as new applications and tools are developed to make it easier it has gotten to be a very simple process. Which method you use will depend on what SBK version (Secure Boot Key) Transformer you have, and also that model's firmware version. Your firmware version can be located by going to Settings>About Tablet. Current version is 8.6.5.21 (TF101) or 8.6.6.23 (TF101G). When either firmware version (also referred to as the 'stock ROM' sometimes) can be used, it will be listed similar to '8.6.x.19', where x can be 5 or 6 for TF101 or TF101G, respectively.
KNOW YOUR SBK VERSION
As a TF owner looking to mod your device, you need to know that there are multiple SBK versions, primarily SBK1 and SBK2. There may possibly be other versions to come even. All you need to know is, that as of right now, SBK1 is the only model that can utilize a tool called NVFlash to UNBRICK your device if you mess it up too badly, and it is difficult to tell which SBK version you have. In order to find out, there are a few tools out there- one of them is for mac only, called SBKDetect found here
http://forum.xda-developers.com/showthread.php?t=1232612
Another is primarily for Linux, but saavy Windows users can always boot from a Linux live CD on their machines to use it, called SBKDetect v2, here;
http://forum.xda-developers.com/showthread.php?t=1290503
The other way, if you are like me, and don't have Linux-abilities at the time of this writing (I'm working on that), you can always just GO FOR IT and try to flash a modded ROM via NVFlash. If you are SBK1 it will succeed. If not, it will fail. No harm done. Of course that means skipping ahead of a lot of learning first, so it is not advised IMO. It also means that if you DO have an SBK1 tablet, you just wiped all your data. It is not absolutely necessary to determine which SBK you have in order to root and mod your device.
A hit-or-miss way of detecting your SBK version is by looking at your device's serial number, located on the bottom of the device on a sticker. It will take the form of:
B70KAS638075
The ONLY digits you need to know are the FIRST THREE. Older models are SBK1. Manufacturing started at Bxx, and has gone to Cxx this year. All Cxx serial numbers will be SBK2. In fact it was in the middle of the B70 manufacturing that they changed the SBK version, so if you are B60, B50, B40 etc..you are sure to be SBK1. If you are B80, B90, C10, etc, you are sure to be SBK2. B70 owners, it's a coin toss. You must use one of the other methods to determine it.
The only thing that differs between SBK1 tablets and SBK2 tablets is the use of NVFlash. SBK2 cannot use NVFlash, so if you end up botching both your recovery and your ROM, and cannot boot into either, then you are SCREWED, so I would suggest reading everything before attempting to mod your device if you are an SBK2 owner.
NVFlash and APX mode
This was an early method used to root and flash recovery/roms, and is still a very useful application to have saved on a disk somewhere in the event that you own an SBK1, as it renders your tablet practically unbrickable. It can be found here;
http://forum.xda-developers.com/showthread.php?t=1123429
To use it you must enter APX mode on your TF101. This is tricky and confuses many users. The procedure is;
1. Press and hold volume UP and POWER buttons at the same time (it doesn't matter if the TF101 is on or off, if it is on, simply wait until it shuts off before proceding).
2. HOLD these buttons for approximately SIX SECONDS.
3. Plug TF101 into PC and listen for it to chime that it has detected it, it should load drivers and device will be listed in Right Cick>Computer/Properties/Device Manager/USB Universal Serial Bus Controller (or similar) as NVIDIA, not as ASUS.
4. If it does not, power on the TF and try again until it does.
NOTE: This is the only way to know if it is in APX mode as the screen remains powered off completely.
Once in APX mode now you can use NVFlash tool, place the system, boot, and recovery .img files into the root of the folder you extract NVFlash into and execute the download.bat file. If at any point the flash fails, this likely means you are SBK2.
ADB Mode
This stands for Android Debugging Bridge. This is not to be confused with APX mode, which is a separate thing entirely. To learn more about your device's ADB mode, see this excellent thread here;
http://forum.xda-developers.com/showthread.php?t=1071584
Another quick guide for ADB can be found here:
http://www.droidforums.net/forum/droid-hacks/6865-how-use-adb-all-commands-options.html
(sorry for the off-site link, trying to keep it as xda pure as possible!)
Razorclaw Root Tool
Razorclaw is by far my favorite method of rooting for the TF, it can be found here;
http://androidroot.mobi/2011/11/14/introducing-razorclaw-v1/
It does not matter what SBK version you have to use Razorclaw, that is why I prefer this method of rooting.. HOWEVER, it does require you to be using an older firmware version though. If you are on version 8.6.x.21 or above, you cannot use razorclaw. It works best on firmware 8.6.x.19. You simply install the app and follow the instructions (Root me nao!). It is a one click, native rooting tool.
If you are not on this firmware version and razorclaw will not work, there are options. You can either roll back your firmware version, the method is located here;
http://forum.xda-developers.com/showthread.php?t=1417006
If you are unsuccessful or want to try another way, you can use Nachoroot or ViperMOD.
Nachoroot Root Tool
This is one of the newer root tools, it is for all firmwares and all SBK versions, and can be found here;
http://forum.xda-developers.com/showthread.php?t=1427838
Nachoroot uses the ADB (Android Debugging Bridge) via a command prompt or terminal, all necessary drivers must be installed.
I cannot personally get this method to work because my PC will not install the drivers properly, and since I don't need the tool any longer, I must admit I've never used it, thus my bias towards Razorclaw. So, if you are having similar driver issues, rolling back firmware and using RC might be quicker and more painless.
ViperMOD Root Tool
ViperMOD is another method, similar to and related to Nachoroot, in that it uses the PC to root your TF101 and will need the appropriate drivers installed. The main difference being that this method will install Superuser as well. The other major difference is that while Nachoroot is done with a command dialogue, ViperMOD is done with a much simpler command interface (choose a number from a list of options rather than typing out commands). Interestingly enough, both of these methods work on both the TF101 and the TF201, and both methods appeared about the same time (posted on January 4th 2012). ViperMOD and Nachoroot represent the most recent methods for gaining root on the TF101. ViperMOD is unique that it has a feature to unroot your device as well, though you will need to have the stock ROM and recovery files available to completely return to stock. Find out more about ViperMOD here;
http://forum.xda-developers.com/showthread.php?t=1427125
I also cannot attest to the use of ViperMOD personally, I have used other methods, but many users have reported it quite simple to root with.
A quick breakdown;
Razorclaw, Nachoroot and ViperMOD will ONLY ROOT your device. No data will be wiped and you will have to install recovery later. In the case of Nachoroot, you will have to download superuser from the market, Razorclaw and ViperMOD installs it for you.
NVFlash WILL WIPE EVERYTHING! So understand that it will rewrite your TF101 internal memory competely and install a rooted ROM (or whatever you tell it to) on your device, as well as a boot and recovery image.
REGARDLESS OF THE ROOTING METHOD YOU CHOOSE, PLEASE READ THAT METHOD'S INSTRUCTIONS VERY CAREFULLY!!!
[Q]How do I know if I am rooted?
[A] Simply check within your app drawer for the superuser application (or download it from the market if using Nachoroot), to verify it works, download titanium backup and begin a batch backup and see if it asks permission, and if the batch completes. If you are not rooted, either try your first method again or try an alternate method.
Tip: Immediately after rooting you should back up your system with Titanium Backup, skip ahead to that section to learn how before moving on.
Recovery Mode
The stock recovery mode on the TF101 shows one of two screens; a green android in the middle of the screen with gears turning inside it, or the same android with a yellow triangle with an (!) inside it instead. The gears obviously mean it is working (flashing firmware), the (!) means something has gone wrong (no file found, flash failed). To enter recovery mode, you need to press and HOLD Volume DOWN and POWER when the device is powered OFF. As soon as the screen comes on, RELEASE THE POWER BUT HOLD THE VOLUME STILL. You will see white letters appear in the upper left corner of the screen, it is now okay to release the Volume DOWN button and quickly (within 5 seconds) press the Volume UP button to enter recovery mode. There are also applications, such as Reboot to Recovery, available on the market, that will allow you to reboot your device with one click into recovery mode without having to toggle your power/volume buttons.
About Stock Recovery Mode
The stock recovery mode is absolutely required to install official Asus OTA (Over The Air) updates. Unless your device is unrooted with a stock recovery mode, you will not be able to install any OTA updates, this includes ICS!! It can also be used to install (or RE-install if it were) your STOCK ROM (only official, digitally signed files will be accepted by the stock recovery to flash over the firmware, no modded roms will work). The method for doing this is outlined in the link for rolling back your firmware version above but I will summarize;
Recovery mode searches your external SD card ROOT DIRECTORY(and the internal memory's cache directory, but this is not useful for any practical reason for you) for these Asus files. The files must be named either;
EP101_SDUPDATE.zip
or
XX_user-epad-Z.Z.Z.ZZ.zip (X = firmware region stamp, WW, US, DE, etc, and Z - firmware version, 8.6.5.19, 8.6.6.21 etc)
I personally find the second configuration to work best. If stock recovery finds a file named appropriately and signed with the proper digital signature it will install it, and you will see gears turning. Otherwise; (!). Remember, it has to be on the SD card in the ROOT, not in a folder or it won't find it.
CWM Recovery Mode
ClockWorkMod Recovery mode replaces your stock android recovery mode, and gives you control of;
Flashing (installing) ROMs, recovery, themes and app packs, patches, kernels and more
Wiping cache, dalvik cache, system, data, etc
Backup and Restore features
Advanced features you probably won't need like fixing permissions and mounting partitions etc.
The important thing to know is if you want to be able to change ROMs right from your device, you need this. In order to install it on the TF, you can use an app called RecoveryInstaller, located here;
http://forum.xda-developers.com/showthread.php?t=1346180
It is a one-click app just like Razorclaw, download and a single click will install CWM for you, though it may be an older version it will work fine to install the most recent version, directly from CWM once you enter it the first time. You will need to give it superuser permission as well. The newest CWM for the TF101 is called ROGUE XM and it is available here;
http://forum.xda-developers.com/showthread.php?t=1446019
Simply place the newest version on your SD card where you can find it, and use the 'install from SD card' option to navigate to the new version file and select it, which will flash the recovery..then you will need to reboot.
CWM Recovery can also be installed when flashing your device from NVFlash, and the NVFlash versions of ROMs almost always contain the most recent versions of the CWM recovery as well, thus making an NVFlash a one-step procedure (flashes both ROM and recovery at same time). The risk of the one-step procedure is if you are using corrupted images or something unexpected occurs you may end up BOTCHING both recovery and ROM at the same time..of course- if you are SBK1 anyways, just reflash it with a different ROM and it will be fixed.
Once you have installed the latest CWM recovery now you will want to start flashing ROMs and Kernels. I will not be posting links to the custom ROMs and Kernels because there are too many of them, that will be your homework.
Custom ROMs
We are blessed to have some great devs working on our humble TF101. That said, the procedure to flash a ROM through CWM is simple;
1: Download desired ROM and place into your external SD card somewhere you will be able to find it, it doesn't matter.
2: Boot into recovery and go to Backup and Restore and make a backup file. This is commonly referred to as a 'Nandroid' backup, and will backup everything from your ROM to your Kernel to user files.
3: Once backed up, proceed to factory reset and wipe cache partition and dalvik cache, located in the 'advanced' menu.
4: Install from SD card, navigate to your directory and find your ROM (ONLY FLASH THINGS THAT ARE MADE SPECIFICALLY FOR THE TF101! Be sure it is compatible with your device!) and select it, scroll to yes...read and follow instructions. Tapdance and sing ABC's while making some breakfast- and you are done!
5: Reboot device
Please be sure to flash only files that are meant to be flashed via CWM, as some ROMs will also have an NVFlash version, which will not work in CWM.
The Stock ROM currently provided with the TF101 is Android 3.2.1, which is called Honeycomb (HC) which is exclusively for tablets, we are all awaiting the release of Android 4.0 commonly known as Ice Cream Sandwich (ICS) which will merge the operating systems used on phones and tablets. Asus has said it will be out soon, so don't ask when it is coming! To learn more about the different Android versions, read this;
http://en.wikipedia.org/wiki/Android_version_history
I would suggest also to anyone wanting to modify their Android device to understand the history of Android itself and what it is, here;
http://en.wikipedia.org/wiki/Android_(operating_system)
Kernels
The kernel is the underbelly, the brain of the ROM. The kernel is what tells the hardware what to do when you interact with the software of the ROM. Most ROMs, I dare say almost every ROM unless specifically noted, does NOT come with it's own kernel but uses the kernel you have installed now on the device, unless it is a stock ROM, in which case most of them DO have kernels included. You want to be sure if what you are flashing has a kernel included or not, and you can always go back to another kernel version if you like, but understand that the OS will behave differently with different kernels. For example, if you wish to enable certain functions at the kernel-level, like overclocking, voodoo sound, etc, then you have to flash a customized kernel.
If you flash a custom kernel, then report your bugs to the developer of the kernel, not the ROM, as most bugs are produced by the kernel.
The procedure to flash a kernel is the same as with flashing a ROM, though you need not factory restore your device before installing, although every developer will agree that it is probably best to have what is called a 'clean install', where you would factory reset the device, flash your ROM, and flash your Kernel, and then restore your apps and information. How do you do that you say?
Titanium Backup
Titanium Backup is an app that is pretty self explainitory- it backs up all system files, data (this includes contacts, settings, call logs, etc) user apps, basically saves your state ON TOP of your ROM, where as the CWM Backup (commonly called a 'Nandroid') is the FULL ROM, Titanium Backup will only restore your settings and apps ON TOP of the ROM once installed. Therefore, you can backup all apps, safely factory reset. Install a clean ROM and Kernel together and then restore your data on top of them. This keeps your user files from either being accidentally overwritten or otherwise interfering with the installation of the ROM/Kernel whatever else you wish to flash.
IF YOU SKIPPED AHEAD READ THIS
Titanium Backup can be found on the market for free, if you like it, buy the paid version.
To backup and restore, simply press the settings softkey and choose 'batch' and select the appropriate action with caution. Press the 'RUN' button for the action of your choice and you will be prompted with a checklist of apps and data to run the batch on. Select which files you want or select all if it is your first time using the app and confirm the action. You will need to give Titanium Backup Superuser permission and make sure you have 'Unknown Sources' checked as well as 'Debugging Mode' checked in your settings/applications menu.
Ok, now go back to 'Recovery Mode' section and keep reading..
Also understand that if you are moving from a version that you have backed up in which apps will not be useable in the version you are moving to, the will not work either. For example, if you flash an ICS ROM and then save the ICS-only apps with titanium backup, and then try to move back to honeycomb or gingerbread (if you have a phone like I do) these apps will likely not install or if they do will FC (force close) constantly. Similar things can happen with user data, call logs from one dailer might not be compatible with an older version etc, so expect there to be instances where you have to selectively install apps one at a time to see if it causes bugs, testing the device for buggs, and uninstalling the app/data before proceding with your restore if it does.
Return to Stock
EDIT: While the below represents a review of how we used to unroot, I have now learned that merely flashing the stock ROM provided by Asus on their website will flash the recovery as well, and that there is a minor difference between the recovery img that came on the device stock versus the recovery img that comes loaded in the Asus firmware packages. If nothing else, the graphics are different, but I suspect that there could be other changes as well. To best unroot the device, simply watch and follow the video in the link.
Outdated info;
So, you played around, and you decided it was time to go back stock for that update, or maybe you just liked it better, or you wanted to give it to your grandma but knew Revolver was above her head- whatever the reason, you want to start fresh. The procedure requires you to get the Stock recovery image and a stock ROM. Luckily the stock ROMs are available on Asus' website, the recovery image isn't as easy to find, it is located here;
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
(Note: The recovery file is not region-specific, therefore it does not matter what version TF101 you have, it is one of the few 'universal' files for this device.
CAUTION: Unrooting with this procedure will only rewrite your system files on the system partition, if you have files located in your root directory that are user-created files that are not part of the system, these files will remain after unrooting, though you will not be able to view them as they are in the root directory, if you root the device again they will be visible. If selling your device or returning for an exchange and you are unrooting it, make sure to manually delete any files/folders that you created in your root directory and do a factory restore with CWM before flashing over your recovery.
Click to expand...
Click to collapse
Procedure:
Click HERE to watch my UNROOTING How-to video.
There should also be a distinction made here between unrooting and breaking root access, while breaking root access will prevent you from having root access to your device, it does not return your device to stock. For example, deleting your superuser application and su binary files can 'break your root' as it is referred to. Yet, in order to effectively unroot your device, you should return the device to it's 100% stock configuration. If you are giving the tab to your grandma or little sister, breaking root is probably enough. If you want to return the device or sell it on XDA, you should probably return to stock completely.
Now that you have read all of this (hopefully) here is the shortcut you wished you had;
My HOW TO ROOT video (Part one)
So, now you are a BUTTFLIPPIN' PRO, you can root, you can flash recovery mode, ROMs, even Kernels, and you can flash stock files from your SD card so you can unroot and return to stock if you want. What if something goes wrong? What if you want to expand your knowledge?
Well this is what we all fear, this section will attempt to address possible outcomes of bad flashes, corrupt ROM images, bad recovery images, etc. as well as help you diagnose your problem and determine whether you need an RMA or to ask for help in the forum.
[Q] My screen won't come on! Help!
[A] In order to determine what the problem is, first try to power on normally, if that does not work try to power on with the USB device plugged into a PC, if you hear it connect you unfortuntely likely have a screen malfunction. If not, try to enter APX mode and listen for notification of connecting to your PC, if still no notification, try charging your tablet overnight and see if it is over-discharged, mine did this once and scared the CRAP out of me, I thought it was bricked, after 10 minutes of fooing with it a battery warning finally popped onto the screen for 1 second before shutting off again. Repeat the previous steps after 24 hours of charging (if TF does not power on on its' own). If none of these solutions work, try powering on and listening for the camera to 'click', if you do not hear this, then it is very likely you have a brick or malfunctioning device.
[Q] My dock drains very fast..why?
[A] This is a problem with old firmware and certain docks. The docks themselves were manufactured with hardware that prevents the updated firmware from being installed in the dock itself, which results in being unable to change the battery consumption configuration. The dock was originally designed to keep the TF awake so that a quick key press would wake it easily, but this resulted in battery drain, when Asus updated the firmware they realized some docks simply needed to be RMA'd. To test yours;
1. Make sure you are updated to the latest firmware for the dock (in Settings?About Tablet), latest firmware is EP101-0213.
2. In Settings>Screen make sure "MobileDock Battery saving mode" is checked.
3. Press the power button on the TF101 to turn the screen off, then press a key on the keyboard (not the mouse buttons).
If any key wakes the TF, then you have the defective dock and must be RMA'd. However if it does not wake, and you still have severe drain, try to resolve it by shutting off background services and checking to see if drain is bad without the dock as well. If it is still draining, as mine has done previously, contact Asus for an RMA.
[Q] My dock is making a strange squealing sound??
[A] Yes, I received one that did this myself, and returned it to the store I purchased it. As far as I could tell it only presented an annoyance, but others reported the issue and suspected that it might have been connected with some people's battery drain issue, so I returned mine as you probably should as well.
[Q] My screen has light bleeding around the edges..is this common?
[A] Unfortunately, yes, light bleed on these devices is far too common. You can try to return the device and get a better one, depending on the severity of the light bleed, and unfortunately it seems every device has it's quirks, you may end up with one that doesn't have much light bleed but has another problem..
[Q] My case creaks, is this normal?
[A] Yes, unfortunately, the plastic backplate has notches that are supposed to affix into the bezel, and sometimes these come loose. However, some people have reported being able to 'snap' it into place again within the bezel, others had to remove the bezel and backplate partially to resolve the issue- others just ignore it as it is only cosmetic.
[Q] My Transformer won't charge! Help!
[A] There could be a few reasons for this experience- the connector is a proprietary connector, and the wires inside can be easily tangled and snapped according to user experience- to verify that the cable works try plugging the device while powered on into the PC and listen for audio confirmation. If your cable is working, but the tablet doesn't seem to charge, you can try to plug in the dock to see if the led on it lights up (unfortunately the TF unit has no charging indicator except for when powered on). The charging adapter itself sometimes has connection problems inside it, and some users have reported success in simply enclosing the charger in a ziplock bag and placing it in the freezer for several hours. I don't know why this works for some, but it does. If it doesn't for you, however, you may need to order a new power adapter from Asus, or you can make your own here;
http://forum.xda-developers.com/showthread.php?t=1087321
[Q] My TF keeps booting and booting but never loads into my ROM..
[A] This is called a 'bootloop', and depending on how far it loads can tell you the severity of the boot loop. First thing to do, is to attempt to boot into recovery. Unless you have an SBK1 tab, this is going to be the only way you will be able to stop this. If not, you have a soft-brick. Eee Pad logo loads and reboots after this, then you have a problem with the ROM itself not wanting to boot (corrupt image, files missing, etc), and usually reflashing your previous ROM without wiping will cure the issue. Sometimes the issue is within the ROM, settings that lock up your device while initializing. If it makes it to the boot animation and reloads, there is a possibility that it is a setting within a kernel if you have a custom kernel installed, try another one, if you aren't running a custom kernel it could be user settings and a factory restore may resolve the issue, and if that fails try another ROM. If the TF will not go into recovery mode and reboots within 5-10 seconds from powering on, you might have a major problem with your system in which case only NVFlash is likely to help.
[Q] I keep getting FC's and bugs..(OR) Do I need to wipe to install...?
[A] Making sure you wipe the correct partitions before you flash new software is vital to making sure it functions properly. This is your necessary wiping procedure, although always best to have a clean install as previously stated;
Nature of the flash| Wipe cache? Wipe Dalvik? Factory Reset?
Clean ROM Flash = YES YES YES
Kernel Flash = YES YES NO
App Pack Flash = YES YES NO
Theme Flash = YES NO NO
ROM Re-flash = NO NO NO
Recovery Flash = NO NO NO
Nandroid Restore = NO NO NO
(Will work on getting this more graphlike after dinner )
Of course always better safe than sorry, and unless you are trying to preserve user apps and data while flashing a kernel or theme then it is always best to reinstall everything after a clean wipe to avoid orphan files and other messy possible errors.
[Q] I can't get into recovery! Help!
[A] The only time you really need to start worrying about not being able to get into recovery is if your ROM also will not load, and vice versa. Since you can simply use the RecoveryInstaller app to fix your broken recovery, similarly if your TF will boot into recovery mode but NOT into the ROM you simply flash (or re-flash) your previous ROM to restore your OS. For this reason, when wishing to update BOTH ROM and recovery, DO NOT FLASH BOTH AT ONCE WITHOUT CONFIRMING THE FIRST FLASH WORKED!
My general rule is to flash my recovery mode first, and then flash my ROM, this is true whether going forward in versions or rolling back to older versions. This way, as soon as you are done flashing and restart (simply holding Volume DOWN as it reboots on its own is enough to initiate recovery mode, be sure to then press Volume UP), you will know if your flash was a success and can rest easy as you flash your ROM, if done the other way around you have to boot into your OS to confirm the flash worked and then reboot back into recovery. If your recovery flash fails, simply allow the OS to load, load recovery installer again and try again.
In the case in which your ROM or recovery will not load, again, your only hope is that you are an SBK1 device and can restore your device via NVFlash.
[Q] Help! My buttons (volume, power) don't work!
[A] Unfortunately this has been discussed quite a bit, sometimes it is related to poor manufacturing, or user damage, or even a poor RMA service. In this case you have only two options- you can try to RMA it, or you can try to tear down the TF101 yourself to try and repair it. It isn't advisable if you can get it repaired under warranty, but if not, you can find discussion with photos of a teardown of the unit here;
http://forum.xda-developers.com/showthread.php?t=1109928
[Q] How do I edit the files in my root directory?
[A] The File Explorer app provided by Asus by design will not allow you to access the root directory, you must use an app, like Root Explorer. In order to change or delete files directly from this app, you will need to make sure the root is mounted as R/W (readable/writeable) as opposed to R/O (Read Only), there will be an option to 'mount R/W' if it is mounted currently as R/O, and vice versa.
[Q] How do I remove Asus' Pre-Installed apps (Bloatware)?
[A]While you can simply delete the app file with your Root Explorer, this may not delete all user data. You could download a tool called Root Uninstaller from the Android Market, or you can use the functions in Titanium Backup to run batch uninstalls, or just 'deselect all' and delete one at a time.
[Q] How do I get back my Asus or Google apps after flashing a modded ROM?
[A]GApps and Asus apps generally are not included with many custom ROMs for copyright reasons, but GApps can be found here;
http://goo-inside.me/gapps/
Asus apps can be found in Gnufabios' package 'Asus Removed Apps' that can be acquired through his Revolver Parts package if you are running that ROM, or can be downloaded here if not;
http://www.gnufabio.com/revolver/dls/
Or you can always make a Titanum Backup of your valued system apps before you flash your ROM. You can then do what I do, find the Titanium Backup folder on your internal and rename it 'TitaniumBackupStockApps' and move it to your SD card, then backup your user apps, rename THAT folder 'TitaniumBackupUserApps' (you may even want to date it or name which ROM it came from, this is your choice), and remove that from your internal memory. You could then do the same with user data, if you decide to do that separately. To flash them back, simply replace the folder and rename it to the 'TitaniumBackup' as it was originally, or, if the folder already exists you can simply copy over the contents, run the batch, then delete the contents and copy the user data contents over as well. This is a great way to keep your apps and data organized and backed up safely. You should make sure this stays up to date and delete old backups after 2 to 3 iterations.
[Q] Can I run Linux?
[A] Yes, look here;
http://forum.xda-developers.com/showthread.php?t=1364095
[Q] How do I install themes?
[A] Depending on the ROM and Launcher you are using, some of the theming options can be built in and accessed in settings menus inside the Android UI (User Interface). However, there are other themes that change files within your root directories and these files will generally need to be installed either via CWM or via ADB. The themes' developer should have clear instructions on installing it.
One more reserved.. This one is for my thank-yous and anything else I miss guys
Roach2010, mike1986, gnufabio, xboxfanj, blades, Clemsyn, baseballfaz, danzano, paulburton, kaijura, daoist, supercurio, MrNago, jcarrz1, rayman84, lilstevie, rburrow, solarnz, fonix232, daxtsu, dipje, frankc123, Sharpe351, chatch15117 ,K900 ,earthbound, AproSamurai, TOO MANY TO REMEMBER YOU ALL!!
You guys are why I am able to do what I do now..
Mods: Stickie this!!!!
This is great! Have my tf a month and had to search all over to root/rom/etc.wish I'd had this info
Great help for us tf noobs.
Sent from my Transformer TF101 using xda premium
Thanks for taking the time to write this up!
Absolute champ!
nice one..thanks mate
Get work this is a must have guide
Sent from my EVO Titan 3D
Fantastic! Having current info all in one place is rare, especially on "older" devices.
Edit: Maybe add a section or note about ViperMOD
Nice job Luna.
+1 on the vipermod. That is what I used and it was extremy simple.
ViperMOD..the one thing I have no experience in on this device it seems; I did a crash course, seems it was actually based right off of Nachoroot, just a cleaned up command prompt interface, and interestingly works on TF101 and TF201. Perhaps that is why I never used it- the post is located in the Prime forum section
Added to OP, guys help me check for accuracy, and correct me if I get anything confused.
Next have some few things to polish up in my thank-yous and try not to leave anyone slighted. Also, thinking of a few more common problems to add to post two. Anything not addressed here just comment or PM me about it I will amend these posts.
THANKS!
Hi Luna
I tried to follow the Return to Stock instructions you listed but there seems to be some problems.
I know these problems are not your fault but maybe you know of another alternative which is as easy to follow as well?
I need a WW Version of the packed stock Rom but neither US nor WW are available due to the mediafire problem.
And the recovery is called 8239USrecovery so I assume I can't use it with my WW version?
Return to Stock
So, you played around, and you decided it was time to go back stock for that update, or maybe you just liked it better, or you wanted to give it to your grandma but knew Revolver was above her head- whatever the reason, you want to start fresh. The procedure requires you to get the Stock recovery image and a stock ROM. Luckily the stock ROMs are available on Asus' website, the recovery image isn't as easy to find, it i located here;
http://theunlockr.com/2011/11/28/how...s-transformer/
Place both files on your SD, but make sure the ROM file is in root (they can both be in the root it doesn't matter) and then use CWM to flash the recovery image, then WIPE EVERYTHING before rebooting into recovery mode again to confirm you have stock recovery in place, and allow it to flash stock ROM. Double check that you are unrooted by downloading superuser and installing it and seeing if it allows you root access (it should not).
Click to expand...
Click to collapse
luna_c666 said:
About Stock Recovery Mode
The stock recovery mode is absolutely required to install official Asus OTA (Over The Air) updates. It can also be used to install (or RE-install if it were) your STOCK ROM (only official, digitally signed files will be accepted by the stock recovery to flash over the firmware, no modded roms will work). The method for doing this is outlined in the link for rolling back your firmware version above but I will summarize;
Click to expand...
Click to collapse
So theoretically this stock recovery mode will allow us to recover to a stock Asus signed ROM in case the main ROM get damaged? for example if rooting goes wrong or any other reason?
I have an SBK2 TF101, and I don't want to install CWM for the moment but want to have root, and don't want to brick my pad.
Outstanding post. Thanks a lot...
Sent from my Transformer TF101 using Tapatalk
Malandro2011 said:
Hi Luna
I tried to follow the Return to Stock instructions you listed but there seems to be some problems.
I know these problems are not your fault but maybe you know of another alternative which is as easy to follow as well?
I need a WW Version of the packed stock Rom but neither US nor WW are available due to the mediafire problem.
And the recovery is called 8239USrecovery so I assume I can't use it with my WW version?
Click to expand...
Click to collapse
The recovery mode can be used regardless of region or firmware version, and if you are unable to locate the firmware files due to mediafire and megaupload etc. being down, simply retrieve them from Asus' website here;
http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download
I'll update the OP to make this more clear
mcbyte_it said:
So theoretically this stock recovery mode will allow us to recover to a stock Asus signed ROM in case the main ROM get damaged? for example if rooting goes wrong or any other reason?
I have an SBK2 TF101, and I don't want to install CWM for the moment but want to have root, and don't want to brick my pad.
Click to expand...
Click to collapse
Yes, if you retain your stock recovery mode then it will be able to flash your firmware in the event that your ROM gets messed up for whatever reason, so long as you use the Stock signed copies of your firmware from Asus (i.e. the official files), recovery mode as stated will only flash official Asus files, they are digitally signed by Asus and without the signature recovery mode will fail.
And to put you at ease, the likelihood of anything going wrong while rooting is much smaller than flashing custom ROMs or recovery mode. Rooting is fairly fail-safe if you follow directions well.
luna_c666 said:
Yes, if you retain your stock recovery mode then it will be able to flash your firmware in the event that your ROM gets messed up for whatever reason, so long as you use the Stock signed copies of your firmware from Asus (i.e. the official files), recovery mode as stated will only flash official Asus files, they are digitally signed by Asus and without the signature recovery mode will fail.
And to put you at ease, the likelihood of anything going wrong while rooting is much smaller than flashing custom ROMs or recovery mode. Rooting is fairly fail-safe if you follow directions well.
Click to expand...
Click to collapse
I am asking because, as mentioned earlier, I only need to root for now without going the whole mod thing, because at the moment I am still not convinced that an android tablet suits me, so in case I still don't like it I want to be able to restore the stock ROM without going more into modding CWM and risking a brick.
So, in the case I root then later decide that I want to unroot, it is enough to put the signed stock Asus firmware on the SD card and boot into recovery mode, and it will be unrooted? why is it then that most unrooting guides does this with a special repacked zip file? why not just stock asus zip?
sticky!
mcbyte_it said:
I am asking because, as mentioned earlier, I only need to root for now without going the whole mod thing, because at the moment I am still not convinced that an android tablet suits me, so in case I still don't like it I want to be able to restore the stock ROM without going more into modding CWM and risking a brick.
So, in the case I root then later decide that I want to unroot, it is enough to put the signed stock Asus firmware on the SD card and boot into recovery mode, and it will be unrooted? why is it then that most unrooting guides does this with a special repacked zip file? why not just stock asus zip?
Click to expand...
Click to collapse
First, you should know that if you do not install CWM and flash a custom ROM, you will never actually know what you can do with an android tablet
But to answer about why others use special zips, unrooting with the Asus file actually does not delete anything on your system partition, it will simply rewrite all the system files, if there are other files that are unrelated to the rooting process leftover in your system partition those files will remain after unrooting. That is what the unroot zip files do usually, is they delete everything and reformat the system partition before installing (instead of just overwrite installing) to avoid leaving orphan files. But these orphan files usually do not impact your system (the entire system has been rewritten anyway) and for sake of argument your TF is unrooted, as you no longer have root access. To avoid leaving anything in your system after unrooting you should factory restore and delete all user apps/data with something like titanium backup before installing the stock firmware over your old rooted ROM. I will think of how to add this to the OP to make it more clear.
Basically though, if you unroot you will want to manually remove any files that are in your system partition (root directory) that were not there when you first rooted your TF or flashing the stock ROM will simply leave those and overwrite the other folders/files.
Just to throw something in here about that. Vipermod does have an unroot setting in it's commands.
Or using terminal emulator or adb
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
reboot

Broken touch screen, need to get Stock

The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
drk.hd said:
The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
Click to expand...
Click to collapse
There is a way to do this with adb... I just do not know the proper commands. Sorry
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
sengwall said:
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
Click to expand...
Click to collapse
No, I don't think it does, but I'd rather not take the chance.
drk.hd said:
No, I don't think it does, but I'd rather not take the chance.
Click to expand...
Click to collapse
YES! It absolutely does. The second the device was rooted it broke warranty.
Sent from my myTouch_4G_Slide using XDA App
The same thing actually happened to me earlier today. I was just browsing some sites on the ICS rom when it just stopped responding. I couldn't get it to recognize any touches even after a bunch of reboots, so I just figured it to be some bug that hadn't been squashed yet. When I dropped down to recovery and saw the same issue, I knew I had a real problem.
Hoping against hope, I tried both CWMR and TWRP on it and got no results. Like you, I figured it would have to go back to Amazon, so I started searching for a way to get it back to stock... nothing obvious jumped out at me because everything is written with access to recovery in mind... which doesn't help.
So, I started reading about adb and going through the built-in help. As I was familiarizing myself with some basic adb commands and options, I left TWRP open in front of me. I don't know how long I had it that way when I mindlessly tapped on the screen and thought I saw it flicker. Yes! I had pressed the Wipe button and it had taken me to that section. It's been working fine ever since.
I'm not claiming I did anything and I don't have a how-to on how to fix it, but it couldn't hurt to just leave the thing running in recovery for a while and see if the touchscreen comes back to life for you too.
Still, I'd love to see someone with more adb knowledge provide a simple tutorial on how to get it back to stock without access to recovery. I'm sure it would be helpful to someone in the future... maybe even me if the same problem comes up again.
Best of luck to you.
Just ignore my comment
Sent from my Amazon Kindle Fire using Tapatalk
If your on the rooted stock rom you could always wait until Amazon pushing the next OTA
You will have to make a fastboot image and flash that with fastboot. But before you create the image, you will have to create all the appropriate symlinks. Then you run...
Code:
make_ext4fs -l 512m -a system -s /path/to/fastboot_system.img /path/to/system_folder
That will create the fastboot image. Then when FFF gives you fastboot access, you run...
Code:
fastboot flash system fastboot_system.img
You will also need a fastboot image for recovery and the bootloader.
Isn't there any easy way like with my desire, simple ruu.
Or hasn't anyone created these images to flash. I also need to get back to stock everything and send it to amazon, my wifi gets error after some period of time and some times when screen goes off, try'd 3 roms and stock.
There is a way to tell the device to install /sdcard/update.zip via shell commands. I forget what they are tho. Something about the extendedcommands. If I have time tomorrow I'll look it up.
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
b63 said:
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
Click to expand...
Click to collapse
Thanks for the link. I'm back on this thread because I think my Kindle Fire touchscreen is now dead for good. However, those instructions do not work as-is because you need to press a button on the screen to tell the Kindle Fire to allow the host to mount it as a USB Mass Storage device. Although those instructions don't get you all the way there, I was able to use the core idea to get my Kindle Fire back to stock. So, many thanks for pointing me in the right direction.
On top of the touchscreen not working, I ended up partially bricking the device trying to find a way to flash it back to stock, so I had also posted in the Unbricking thread. I posted my solution there....
http://forum.xda-developers.com/showpost.php?p=23226260&postcount=701
Odds are, if you have a device that is booting correctly, you will be able to ignore steps 3 and 4 and get it booting back to stock. I do have a couple of other suggestions... Leave your USB cable hooked up to the Kindle Fire as it boots into stock for the first time. This is the only time that it will automatically mount the /sdcard to your computer and you will have a chance to reclaim (and delete) all the files stored there. You can also do something like 'adb pull /sdcard C:\sdcard' before you flash. Also, depending on what ROM and apps you were using before starting the process, you might want to delete your user data and reset the device to factory defaults. You can do this with 'fastboot erase userdata' and the next time you start the device, you'll get a warning that it's about to reset. Hit the power button and you should have a clean, fresh from the factory Kindle fire... albeit with a broken touchscreen. Good luck!
After several failed attempts to follow this guide (no offense to posters; I appreciate your contributions), I found this to be the simplest method.
http://stackoverflow.com/questions/10817721/wipe-data-factory-reset-through-adb
Download stock update, then it's basic procedure in adb:
adb push C:/update.zip /sdcard/update.zip
adb shell
recovery --wipe_data
After reboot, go back into to adb shell and do "recovery--update_package=/sdcard/update.zip"
Factory reset, etc. and you're good to go.

How to recover fastboot deleted nvidia shieldTv 2015?

I have been reading for many days and there is no way I can get into fastboot , to install new system ,no boot logo, not fastboot.
I have some other way to repair fastboot?
Is it possible to delete the fastboot?
If so, can it be rewritten?
thanks
Pro, or Standard?! I don't know what to tell you about the Standard though.
If it's the Pro we're talking about I would slow down FAST! And, have a look at the SSHD to SSD Migration Threads here first. Namely the bits on cloning it. Which might at first seem to be pointless. But let me explain.
Each Shield TV has a hidden Partition inside the SSHD that contains the valid Widevine L1 Keys. In short you will want these if you have plans to use either Amazon, Netflix or <Insert other heavy handed OTT Service here!>.
While you may have forked the Bootloader to a permabricking state. You could use the Op's Backup Image of his own Shield TV which he was generous enough to make public.
That however would way out your own Keys FOREVER! The practical upshot would be like an XBOX Live Permaban.
So heres the "Idea", you backup what's left of your SSHD Under normal circumstances you should never have need to touch the Security Sectors of the SSHD. Once you have made that Backup... Following the info from that Thread. Go ahead and install Ops backup Image to your Shield.
(Full disclosure) It's to late for me, so I can't tell you exactly which Partition you need or which DD command to enter, in order to flash back your personal Security Sector to your Device. I think I may have inquired about it in that Thread. But not having bothered to make a backup even at that point means I no longer have those Keys, even if I do have a working Shield TV. But as long as you can replace the correct Partition with the One that came with the Shield you should be able to recover.
Now outside of that advice. You really don't need to ask me anything further. Again I never managed to get that far. I was going on what turned out to be false information at the time that only Netflix would be affected, by a broken ESN. What the people in that Thread probably faild to realize was that it was the Widevine Keys that were to blame. So I thought ok fork Netflix! As long as I can use Amazon.
Needless to say: WRONG ANSWER!
But, if I were in your shoes​ now, the above would be my plan of attack. But, I'm not the One to be asking about how to do all of that. Besides most of the foreseeable questions should already be answered there.
if you cant boot into bootloader or fastboot mode, at least in 16gb, your screwed. Better request for RMA.
Sent from my Tapatalk Hub
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee ~ Full Android for ShieldTV and Nexus Player
Ichijoe said:
Pro, or Standard?! I don't know what to tell you about the Standard though.
If it's the Pro we're talking about I would slow down FAST! And, have a look at the SSHD to SSD Migration Threads here first. Namely the bits on cloning it. Which might at first seem to be pointless. But let me explain.
Each Shield TV has a hidden Partition inside the SSHD that contains the valid Widevine L1 Keys. In short you will want these if you have plans to use either Amazon, Netflix or <Insert other heavy handed OTT Service here!>.
While you may have forked the Bootloader to a permabricking state. You could use the Op's Backup Image of his own Shield TV which he was generous enough to make public.
That however would way out your own Keys FOREVER! The practical upshot would be like an XBOX Live Permaban.
So heres the "Idea", you backup what's left of your SSHD Under normal circumstances you should never have need to touch the Security Sectors of the SSHD. Once you have made that Backup... Following the info from that Thread. Go ahead and install Ops backup Image to your Shield.
(Full disclosure) It's to late for me, so I can't tell you exactly which Partition you need or which DD command to enter, in order to flash back your personal Security Sector to your Device. I think I may have inquired about it in that Thread. But not having bothered to make a backup even at that point means I no longer have those Keys, even if I do have a working Shield TV. But as long as you can replace the correct Partition with the One that came with the Shield you should be able to recover.
Now outside of that advice. You really don't need to ask me anything further. Again I never managed to get that far. I was going on what turned out to be false information at the time that only Netflix would be affected, by a broken ESN. What the people in that Thread probably faild to realize was that it was the Widevine Keys that were to blame. So I thought ok fork Netflix! As long as I can use Amazon.
Needless to say: WRONG ANSWER!
But, if I were in your shoes​ now, the above would be my plan of attack. But, I'm not the One to be asking about how to do all of that. Besides most of the foreseeable questions should already be answered there.
Click to expand...
Click to collapse
Many thanks for your reply, but I do not have the pro and I do not have a backup.
demondhume said:
Many thanks for your reply, but I do not have the pro and I do not have a backup.
Click to expand...
Click to collapse
If you have a "Standard" (i.e. The 16Gb), then it's pretty much the end of the Road for you. As there is no way outside of a nVIDIA Factory, that I'm aware of that would allow you to recover your Bootloader on an eMMC Chip. Without some very expensive equipment, and some very MAD SKILLZ. Apperently someone here managed to do that by upgrading the Chip to 32Gb's, from the usual 16. But, this is likely beyond the scope of most People.
It kinda sucks to say it, but I think it's time to start looking for a replacement.
demondhume said:
I have been reading for many days and there is no way I can get into fastboot , to install new system ,no boot logo, not fastboot.
I have some other way to repair fastboot?
Is it possible to delete the fastboot?
If so, can it be rewritten?
thanks
Click to expand...
Click to collapse
It is possible to delete the fastboot if you've performed this command
fastboot erase bootloader
If not, I suspect that you just can't deal with the hardware trick to enter the bootloader which it is tricky indeed
- with the TV box disconnect from the power cable
- Connect the hdmi both to TV and TV box
- connect the USB cable to both pc /laptop and TV box
- connect the power cable and on the next split second hold the power button of the TV box for few seconds, it should go to bootloader
From there, use the Nvidia TV box recovery image to flash it, there are instructions on website about how to which consists on a set of fastboot commands
Before starting be sure that the fastboot drivers are correctly installed and functional
Sent from my Darkside of Oneplus 3T
it is clear that OP's device is in that state because he already flashed something (wrongly) and nuked the bootloader.
If he already flashed something, it means he knows how to get into fastboot or bootloader mode, so that is not the issue. The issue is that OP bricked his device by flashing wrong bootloader, and if the bootloader gets corrupted in 16gb model you won't be able to boot into that mode, thus not able to flash anything anymore.
Best advice is to request for RMA.
Sent from my Tapatalk Hub
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee ~ Full Android for ShieldTV and Nexus Player

SM-T280 I've made a huge mistake

I installed TWRP and tried to flash SuperSU according to the guide by ashyx here: https://forum.xda-developers.com/showthread.php?t=3475381
So, from what I can tell by reading this thread: https://forum.xda-developers.com/galaxy-tab-a/help/samsung-galaxy-tab-10-1-mount-data-t3544561, the problem is that my device was encrypted. I tried restoring the full image that I made using TWRP, before trying to flash the boot. Stuck on Samsung logo now. I should have seen this coming when I was getting "failed to mount /data" errors.
So I suppose I need to flash that zip https://www.androidfilehost.com/?fid=24591000424951049, but I thought I better ask specifically about my device and situation before blindly flashing yet another zip.
What steps do I need to take now?
thanx
update :: it sounds like my last resort option is to flash the stock ROM (can I do this in Odin?)
BUT I noticed that SuperSU saved a "stock_boot_*.img.gz" file, which I copied to SD root and also to my PC. Now I imagine that if I flash this, I might be able to regain access to the OS... that would be the best at this time. Then I can do more research and try root again later.
Is this true, and how should I flash the stock_root file?
I absolutely love doing research and answering my own questions! no sarcasm. after reading a whole bunch of general info about the Android system, partitions, boot process, TWRP... I forged ahead with 90% confidence, unpacking the "stock_boot_*.img.gz" and feeling for a way to flash it with TWRP... and more importantly, with 99.9% confidence that it won't wreck anything if I try.
So next time, I will first decrypt the system before trying to root, and pay attention to the log output, and only proceed when confident that I know what's happening next... this is all basic IT procedure. I should know this! Guess I was in a rush to get root. Still in a rush in a way tho.... want to recover deleted photos and can't do it without root. Anybody know if Android device encryption is proper full-disk? Like if the empty space will be decrypted just the same?
trefrog said:
I absolutely love doing research and answering my own questions! no sarcasm. after reading a whole bunch of general info about the Android system, partitions, boot process, TWRP... I forged ahead with 90% confidence, unpacking the "stock_boot_*.img.gz" and feeling for a way to flash it with TWRP... and more importantly, with 99.9% confidence that it won't wreck anything if I try.
So next time, I will first decrypt the system before trying to root, and pay attention to the log output, and only proceed when confident that I know what's happening next... this is all basic IT procedure. I should know this! Guess I was in a rush to get root. Still in a rush in a way tho.... want to recover deleted photos and can't do it without root. Anybody know if Android device encryption is proper full-disk? Like if the empty space will be decrypted just the same?
Click to expand...
Click to collapse
It doesn't really decrypt it, it does a full format using either no encryption or new encryption. I'm sorry, but the files are gone. To answer your question though, I believe the encryption is full-disk.
Going forward, check out TitaniumMediaSync. You can mirror your internal storage to a computer via FTP, so when these things happen (and they do happen), you won't lose anything. I'm sorry you lost your files in this.
actually I didn't lose my files! I was able to restore the backed up boot partition that twrp made and tucked into a folder.
happy af :laugh:
... so are you saying that the decrypt function in the Android settings just wipes everything? Then why is it even there, if it's basically a factory reset?
hmm associated with Titanium Backup? I have a license for that, and as soon as I root this, I'll be installing it. Currently, all my important stuff (just photos), are backed up to my PC via QuicPic's cloud backup feature.
I think i have found myself in the same situation as you. I dont have any files or data to lose. managed to do first step in using odin to install twrp. tried to follow additional steps of installing super su, then padded boot. now the tablet wont load past the first screen. I can still get into twrp. how can i get this fixed, rooted and a custom image installed? any help in the right direction would be appreciated.
find that "stock_boot_*.img.gz" using the twrp file browser thing. copy it to the root of your SD for safe keeping (even if the SD is encrypted, it seems that it does so only at the file level, rather than partition/disk level, so it will be written unencrypted). if ur plugged to PC, you can copy it across for even safer keeping
then... I don't recall how I found it, but it's in twrp. a way to flash that file. worked for me, because as far as I made it, only the boot partition was affected

Onn 7" SURF Model 100005206

I have since returned this tablet. The go edition was just too much, or way too little for me to deal with.
The 7" variant shouldn't be considered a variant as it is only similar in shape and color. It is however still rootable. I am assuming you have adb and fastboot set up and know how to use them. Also if on windoze you know how to adjust if needed and to connect device with usb and the other little details I've overlooked. If not then I am also assuming you don't need to try this yet.
The root process is not difficult but tricky in that it is different. Before doing this you need to go to Magisk release thread and check out link for running Recovery Mode and read it all. You must have unlocked bootloader. The process goes something like this:
Edit: You will need the latest platform tools for fastboot to work properly. This link https://www.xda-developers.com/what-is-adb/ provides instructions for windows and Linux. Yes, you may need to update the tools in some Linux installations as not all repositories are kept up to date with regards to android-sdk.
1) Download mtk-su by @diplomatic to your pc.
2) Open a terminal in window where you have mtk-su. You can cd to it but this seems easier. Type the following "adb push mtk-su /data/local/tmp/"
3)Type "adb shell chmod 755 /data/local/tmp/mtk-su
4)Type "adb shell" you will enter a shell with no need to cd to anywhere. If you cd /data/local/tmp then you need to cd back out of it when root shell is achieved. If you run it this way your ready to go without changing directories
5) Type "./data/local/tmp/mtk-su -v" you now have a root shell. If for some reason you do not have root access, run mtk-su again, it will work.
6)Now the confusing part. You need to copy your recovery to patch with Magisk. You use "dd if=/dev/block/mmcblk0p10 of=/sdcard/recovery.img your recovery should be in internal storage when you open your file manager.
7)Install Magisk Manager and open it to select install. Before install you tick advanced settings and tick Recovery Mode. You then select install. A toast will pop up and you select the bottom one which is to patch your boot.img file. Wherever you see boot you use your recovery instead.
8)Magisk will put your patched recovery labeled magisk_patched.img in your download folder. Transfer it to your PC.
9)In terminal on PC open window where you have your magisk_patched.img. Then use adb reboot bootloader.
10) Flash your patched img with "fastboot flash recovery magisk_patched.img" and you're done flashing.
11) Now the fun part, you hold power and volume+ until you first get a glimpse of the boot selection screen. AS SOON AS IT LIGHTS UP LET GO for a second,just a second, then scroll to recovery and hit volume- . If its already on recovery just use volume down, do not scroll around to it. Your tablet will boot into a Magisk rooted system and not recovery.
It can be tricky but however you boot your tablet determines if you're rooted or not. When Magisk Manager reboots after installing a module it know what it's doing and you don't have to do anything but wait on it. Whenever booting your system you need to make your first priority going to magisk to check if it's installed before trying anthing. You need to do this every time you boot until you have your timing right and confidence way up. Then you should probably still check.
From what I can see when not booted to Magisk rooted system, installed modules and changes made are obviously not working. It should stand to reason if Magisk is not installed that magisk modules won't work. Like I said, its not hard it's just odd to me. Don't know how porting recovery is going to go. Wondering if we will need to patch the ported img or port the patched img. It's is treble compatible, I've read a-only but don't know about gsi's yet. Keeping expectations low though.
When I had Magisk installed I was left with no recovery or I didn't keep it long enough to figure it out. When booting with hardware buttons and holding for recovery/unrooted system the tablet booted to an unrooted system bypassing recovery all together. Don't know if it was procedural error on my part or if that is the compromise that has to be made to have perm root for the time being. Flashing stock recovery via fastboot proposed no issues.
Good information, thanks!
What prevented the usual patched boot image method from working?
NFSP G35 said:
Good information, thanks!
What prevented the usual patched boot image method from working?
Click to expand...
Click to collapse
No ramdisk in boot.img. It works but just feels weird. Also from what I've gathered it can't be installed/upgraded via custom recovery. Not that there is one but down the road that's a bummer.
My apologies I withdraw my question.... I see that the 7 is different from the 8 & 10 where the recovery.img is being patched instead of the boot.img I will make note of that when I start my video tutorial series for the onn line of tablets.
The 7" definitely does not belong to the same family as the x003 and x002. The items partition (items.ini) only has hardware configuration for 10" and 8" tablets. I don't own the x007 keyboard variant, but I would not doubt the the 10" x003 dump would probably run on it. (speculation; not conclusive)
CaffeinePizza said:
The 7" definitely does not belong to the same family as the x003 and x002. The items partition (items.ini) only has hardware configuration for 10" and 8" tablets. I don't own the x007 keyboard variant, but I would not doubt the the 10" x003 dump would probably run on it. (speculation; not conclusive)
Click to expand...
Click to collapse
It's Android (go edition) and it appeared as if everything were different. Even its google apps are different. I don't think they show up in play store unless you are on a go edition device. I have an account but only have google services on one device so don't use playstore enough to be sure. But the names all have go on them as in maps go, youtube go and chrome go. Go is slow, no ? I don't believe I seen a /vbmeta partition either. I was going to install a gsi to get rid of go but it was a no go. Not aware of any documentation for installing gsi's on go edition devices although it is supposed to be compatible, what's the point? Modified should mean some type of performance gain, somewhere at least. Coming in with just over 900MiB of RAM (not 1G) it's only close but still roughly 10% down from advertised. I had referred to it as the runt at one point, and it is that in every sense of the word. Smaller, weaker and slower was more than I cared to deal with. You can polish a pile of crap all day long, and at the end of the day, the best you can hope for is just a shiny turd. Too many other options and way better things to waste 50 bucks on. I returned it after a couple of days. The 8" and 10" tablets could stand a little better build quality. But over all I believe they knocked it out of the park with them. The 7", well... foul ball!
tek3195 said:
It's Android (go edition) and it appeared as if everything were different. Even its google apps are different. I don't think they show up in play store unless you are on a go edition device. I have an account but only have google services on one device so don't use playstore enough to be sure. But the names all have go on them as in maps go, youtube go and chrome go. Go is slow, no ? I don't believe I seen a /vbmeta partition either. I was going to install a gsi to get rid of go but it was a no go. Not aware of any documentation for installing gsi's on go edition devices although it is supposed to be compatible, what's the point? Modified should mean some type of performance gain, somewhere at least. Coming in with just over 900MiB of RAM (not 1G) it's only close but still roughly 10% down from advertised. I had referred to it as the runt at one point, and it is that in every sense of the word. Smaller, weaker and slower was more than I cared to deal with. You can polish a pile of crap all day long, and at the end of the day, the best you can hope for is just a shiny turd. Too many other options and way better things to waste 50 bucks on. I returned it after a couple of days. The 8" and 10" tablets could stand a little better build quality. But over all I believe they knocked it out of the park with them. The 7", well... foul ball!
Click to expand...
Click to collapse
It's probably 1GB or 953MiB of RAM. Powers of ten rather than powers of two.
CaffeinePizza said:
It's probably 1GB or 953MiB of RAM. Powers of ten rather than powers of two.
Click to expand...
Click to collapse
May have been 953 can't remember now thankfully can't check either. But less than a G which is more like 1024 i believe. That would still be in the ballpark with what I called roughly 10 percent. I only put that because 10 percent could be huge considering a lot of times we tweak and modify for gains much smaller. It wasn't meant to be a technical review. When you get one, get as technical as you want with it. It will still be a piece of sh*t.
tek3195 said:
May have been 953 can't remember now thankfully can't check either. But less than a G which is more like 1024 i believe. That would still be in the ballpark with what I called roughly 10 percent. I only put that because 10 percent could be huge considering a lot of times we tweak and modify for gains much smaller. It wasn't meant to be a technical review. When you get one, get as technical as you want with it. It will still be a piece of sh*t.
Click to expand...
Click to collapse
I do not plan on supporting the 7" tablet. Probably just burst some bubbles.
tek3195 said:
No ramdisk in boot.img. It works but just feels weird. Also from what I've gathered it can't be installed/upgraded via custom recovery. Not that there is one but down the road that's a bummer.
Click to expand...
Click to collapse
What about modifying the boot.img to create the ram disk?
callihn said:
What about modifying the boot.img to create the ram disk?
Click to expand...
Click to collapse
Not sure I follow. The ramdisk it uses is in the recovery.img not sure what you would be trying to create or use it for. You lost me.
I've managed to unlock the bootloader, but the system boots up normally... Stock recovery if I choose recovery. Where did I go wrong?
i think your crazy also, I patched the recovery, and it doesn't work, it goes to a blank screen, if you had screen shots it might be more convincing, what does majick do taking over recovery, means using root from a p.c ???
https://gist.github.com/varhub/7b9555cdd1e5ad785ffde2300fcfd0bd
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
if goes to majick recovery see if it's rooted with adb
---------- Post added at 06:17 PM ---------- Previous post was at 06:10 PM ----------
when you say building, found an interesting article where you might build or free ramdisk, even boot to majick root recovery, I'm just researching the idea
https://source.android.com/devices/bootloader/partitions/ramdisk-partitions
have you tried flashing with a gsi ROM, this sounds great
https://forum.xda-developers.com/pr...hVM2htbVVRNGhnUzU5ZktDUUNSZjlzdGE2bkk4TjhZY3M.
flashing gsi rom on surf 7, changed vbmeta to dtbo.img, got a black screen with no way to fix, no recovery ? does anyone know the proper way to flash one

Categories

Resources