Database Info

Root Nvidia Shield clarification

Hi after reading through the post on GitHub on how to simply root your shield I have a few questions that the tutorial doesn't make clear:
1)There are a ton of files at the top and not sure what to do with them...
2) There is a bit where it explains "On your computer, navigate into the directory containing this file and enter the following command:
fastboot boot zImage_dtb ramfs.img.gz"
But it doesn't say that after you open the directory what you do with it?
Do you keep the window open and that's fine?
Do you type in it's location into command prompt before you type in: fastboot boot zImage_dtb ramfs.img.gz?
Just a bit confused as to what all the files are and where I put them and how they have to be utilised etc
Just need clarification for peace of mind
wanted to post the link but forum won't let me yet

Root explanation
Hi here is the main walkthrough from github but as I said there are a few plot holes for people who are new.
If your SHIELD is already unlocked, you can skip this section.
SHIELD ships with an unlockable bootloader. The bootloader is locked by default, which prevents anyone (including yourself) from booting custom OSes and changing system partitions to potentially obtain extra privileges. This is a significant security feature: in the event that your device gets stolen, an attacker will not be able to retrieve your personal data or use your device if your lock screen has a password set.
By unlocking the bootloader, you allow anyone with physical access to your SHIELD to boot custom images and flash system partitions. This opens the way for an attacker to access your personal information or physically damage your device. For this reason, unlocking the bootloader will erase all your personal data like a factory reset does (so a potential thief cannot get it) and will also void your warranty.
If you know you really, really want to take these risks, here is how you unlock SHIELD's bootloader.
Switch your SHIELD off (long press the NVIDIA logo button and select Power off).
Power your SHIELD on while maintaining the back and home buttons pressed (these are the two buttons that lie under the big NVIDIA-logo button, on its left and right). Release them once you see the bootloader screen.
Connect your SHIELD to your computer using a USB cable.
On your computer, enter the following command:
fastboot oem unlock
This will display the unlock menu. Read the disclaimer and think one last time about what you are doing. This is your last chance to stop.
Use the back and home buttons to select your option. If you decide to continue, select Unlock and press the NVIDIA-logo button to validate. Your personal data will be erased and your device marked as warranty-void permanently.
Regardless of your choice, you will be back to the bootloader screen. Using the same buttons, navigate to Poweroff and select this to power your SHIELD off.
Rooting SHIELD
Now your bootloader is unlocked, but you still don't have root access. For this, we need to install SuperSU, and we will do so by booting a custom Linux image that will do this for us.
Power your SHIELD on while maintaining the back and home buttons pressed (these are the two buttons that lie under the big NVIDIA-logo button, on its left and right). Release them once you see the bootloader screen.
Connect your SHIELD to your computer using a USB cable
On your computer, navigate into the directory containing this file and enter the following command:
fastboot boot zImage_dtb ramfs.img.gz
The kernel and ramdisk will be downloaded and started. You will see 4 penguins on your screen, and the message ROOTING SHIELD will appear. Shortly after, your device will reboot. Congratulations, you are rooted!
For some unknown reason USB debugging in Developer options might become unchecked after rooting. You will need to re-check it if you want to use ADB.
It is safe to perform the rooting operation as many times as you want (e.g. after an OTA). Your user data will not be erased by rooting itself, it is the act of unlocking the bootloader that does.
Is there anyone who can add a little to this to make it more simple for a noob like me?
I understand there is a file set that is at the top of the page and I downloaded the files which include zImage_dtb ramfs.img.gz
but don't know how to utilise them etc
There are no videos on youtube of how to do it and if anyone can add just a few more steps so that I know where I'm going with this (don't want to brick my system).
I just want controller support installed like Tincore or gamekeyboard so I can unlock the potential of the games library on GooglePlay.
Thanks for reading.

you copy those two files "zImage_dtb" & "ramfs.img.gz" to the same directory your adb and fastboot executeables are (same directory you issued the oem unlock command from)
then navigate to the same directory you did the oem unlock from via command line then issue the command "fastboot boot zImage_dtb ramfs.img.gz"
it's pretty simple but I can run you through a simple example of what I did
1)download android sdk
2)copy platform tools folder to a directory on c drive (exp c:\tools\ )
3)copy the 2 files above to the same folder along with cwm recovery(optional)
4)boot shield into fastboot mode (home+back+power)
5)navigate to the folder with adb, fastboot, and the above files in it.
Code:
cd c:\tools
6)detect if fastboot driver is installed with "fastboot devices" if result, then continue, if no result, then check if correct driver and check connection
7)issue oem unlock command and follow the onscreen prompts
Code:
fastboot oem unlock
8)restart device, after a full boot cycle(wipes data), power back into fastboot
9)issue the "rooting image" command, device with automatically reboot
Code:
fastboot boot zImage_dtb ramfs.img.gz
*10) optionally reboot back into fastboot and install cwm recovery
Code:
fastboot flash recovery recovery.img
pretty simple

thanks for fast reply.
Ok so I have Two different versions of Android SDK (32 bit and 64 bit) which one do I use?
"copy platform tools to a directory on C drive (exp C:\TOOLS\)"
What are platform tools?
"copy the two files above to the same folder along with cwm recovery"
What two files? do you mean the zImage_dtb and ramfs.img.gz? Do they go into the C:\TOOLS\ folder?
"navigate to the folder with adb, fastboot, and the above files in it"
What do you mean by navigate? Do you simply mean open the folder or do I use a program to do this?
"Detect if fastboot driver is installed with "fastboot devices" if result, then continue, if no result, then check if correct driver and check connection"
What's fastboot devices? What does result and no result mean? What does Check driver and check connection mean? how dod I do that?
I'm confused by all the lingo, what applications I should be using and when exactly do I start using command lines etc
Thanks for help so far been great but I need step by step instructions eg
open folder, copy and paste file1 and file 2 to this folder
open application X
click import file 1 and file 2
type XXXXXX\root\cdrive into command
press enter
see?
I do not know what some of the words mean and how to do some of the stuff the tutorial says. It's jargon and I have all these files, in all these folders with no idea how to do this from start to finish.
Appreciate the help so far but you are dealing with a novice. I know the work won't take long but I need all the relevant info, in one list, with consistent language to ensure I do everything as it should be done.
Bless you sir and...
Good luck

If your confused by my instructions you need to wait for a "one click" installer, sorry.

gogul1 said:
Ok so I have Two different versions of Android SDK (32 bit and 64 bit) which one do I use?
"copy platform tools to a directory on C drive (exp C:\TOOLS\)"
What are platform tools?
"copy the two files above to the same folder along with cwm recovery"
What two files? do you mean the zImage_dtb and ramfs.img.gz? Do they go into the C:\TOOLS\ folder?
"navigate to the folder with adb, fastboot, and the above files in it"
What do you mean by navigate? Do you simply mean open the folder or do I use a program to do this?
"Detect if fastboot driver is installed with "fastboot devices" if result, then continue, if no result, then check if correct driver and check connection"
What's fastboot devices? What does result and no result mean? What does Check driver and check connection mean? how dod I do that?
I'm confused by all the lingo, what applications I should be using and when exactly do I start using command lines etc
Thanks for help so far been great but I need step by step instructions eg
open folder, copy and paste file1 and file 2 to this folder
open application X
click import file 1 and file 2
type XXXXXX\root\cdrive into command
press enter
see?
I do not know what some of the words mean and how to do some of the stuff the tutorial says. It's jargon and I have all these files, in all these folders with no idea how to do this from start to finish.
Appreciate the help so far but you are dealing with a novice. I know the work won't take long but I need all the relevant info, in one list, with consistent language to ensure I do everything as it should be done.
Bless you sir and...
Good luck
Click to expand...
Click to collapse
Step by step instructions like that would take quite a long time to write. Its basically assumed that navigate is a straight forward instruction, namely, open My Computer, click C:\, click something else, etc etc. 32 bit vs 64 bit, again, you should know what your computer is running and use the correct one respectively.
The reason they dont issue novice instructions is for 1 reason only. People who such as yourself claim to not understand the "jargon" are also those who are more likely to make a mistake when rooting. This can lead to a completely bricked device, ie one that will no longer turn on and load up android, totally dead device. As far as the manufacturer is concerned, a bricked device unless bricked by one of their own updates on a non rooted shield installed correctly, is not covered by warranty. This leads said novice to accuse the tutorial writer of having something wrong in the tutorial when in reality they have clicked the wrong thing etc.
Either way, end result: dead device.
Rooting is not aimed at the novice. It is aimed at the advanced user.

Thank you
I understand that and appreciate the explanation. I can work my laptop and I know that my laptop is 32bit or 64bit but it did not say at any point that it was referring to my computer. It just said download the 32 or 64 bit version. Well I have to make sure what they are talking about before I go and try to root my device as I like clarification on everything I do so that I get it right (and don't brick it). At the moment the explanations are all over the place, some info here, another bit there and was hoping somebody could link it all for me and make sense of the order in which I would do things. I have installed graphic cards in my laptop, put custom firmware on to ipods, psp's, computer etc but this is my first foray into android territory and would like to get it right. I am trying to follow a video tutorial but my computer's reaction to driver updates for the ADB/Fastboot drivers is telling me my drivers are up to date and I'm not getting the error message his is. This means I'm not sure where to go as the situation is diffferent s He is trying to get motochopper working for shield so it will root the device and hoped it would do the same for me.
Hopefully some clarification will come sooner rather than later but won't venture fourth until I'm absolutely sure of what needs to be done.
Again, thanks for the help it is appreciated.:laugh:

Sorry for being so abrupt, it wasn't my intension, you are trying to learn. I will not give a step by step which I feel would be the best, yet potentially more dangerous option for you though.
The parts written in the "code" blocks are what you copy and paste into the command line. When I say navigate I mean by changing directory via command line. You can copy files with a graphical file manager as it's quicker but navigate could also mean graphically.
Google search how to tell if you are running 32 or 64 bit windows, there are better guides and videos than I would be able to describe in a few lines. I was assuming you had already unlocked your bootloader as it is required before root, I covered it as point of reference only.
Platform tools is a folder in the SDK, if you install the SDK you will see that folder where you install it.
Fastboot is the utility also in the SDK that you run from command line that's in the code blocks I posted. If you run the command it will either give a result saying a device is detected or it won't show anything (no result) and you have an issue. If you have a driver issue then that's a whole other problem with a specific forum topic for, but I also assumed you unlocked your bootloader which would require you have fastboot and driver issue resolved.
Main cause of my snappiness is it says the requirement (first line of what you quoted) is unlocked bootloader and you are asking questions about rooting (step two after unlocking bootloader) didn't realize you were stuck in step 0, trying to figure out where to start.

gogul1 said:
I understand that and appreciate the explanation. I can work my laptop and I know that my laptop is 32bit or 64bit but it did not say at any point that it was referring to my computer. It just said download the 32 or 64 bit version. Well I have to make sure what they are talking about before I go and try to root my device as I like clarification on everything I do so that I get it right (and don't brick it). At the moment the explanations are all over the place, some info here, another bit there and was hoping somebody could link it all for me and make sense of the order in which I would do things. I have installed graphic cards in my laptop, put custom firmware on to ipods, psp's, computer etc but this is my first foray into android territory and would like to get it right. I am trying to follow a video tutorial but my computer's reaction to driver updates for the ADB/Fastboot drivers is telling me my drivers are up to date and I'm not getting the error message his is. This means I'm not sure where to go as the situation is diffferent s He is trying to get motochopper working for shield so it will root the device and hoped it would do the same for me.
Hopefully some clarification will come sooner rather than later but won't venture fourth until I'm absolutely sure of what needs to be done.
Again, thanks for the help it is appreciated.:laugh:
Click to expand...
Click to collapse
Download 64 bit software for 64 bit windows and 32 bit on 32 bit windows. Only notable exceptions are where a guide explicitly says to get 32 bit for some particular reason (in my case the only time I have come across this is MSI afterburners screen recording facilities only functioning on a 32 bit program for some reason, no 64 bit version) or if you are running 32 bit windows and physically cannot run 64 bit software even though a guide says "use 64 bit java etc etc".
rather interested in installing a graphics card in a laptop seeming as laptops use graphics cards that are soldered down to the motherboard not on a seperate removable card in all with very few (but existant) exceptions.... I think asus, dell and someone else did offer them at one point, its actually what the MXM connector was invented for (but its used for a few other things now instead).
Anyway. Its always good to have clarification. I think the post above me gives a few starting points and as always: google is your friend (so are bing and yahoo, but they are those friends where once you leave your job or school or whatever you probably wont ever see again).

boot achieved
I boot loaded the Shield through dab and boot loader.
Shield restarted once I chose to unlock the shield. I lost all my stuff (as expected) and it restarted. The drivers then reinstalled on my laptop.
I restarted my laptop and the shield again and tried to reinstall the drivers that were made for the ADB but sadly I get this message now...
"Windows has determined that your driver software is up to date MTP USB DEVICE"
So I restarted everything and the device is now showing up in the Andriod Device driver list.
I am using minimal adb and Fastboot application. It opens the command menu
I type in
adb reboot bootloader and I get the reply "error:device not found"
any ideas?
Sigh!

gogul1 said:
I boot loaded the Shield through dab and boot loader.
Shield restarted once I chose to unlock the shield. I lost all my stuff (as expected) and it restarted. The drivers then reinstalled on my laptop.
I restarted my laptop and the shield again and tried to reinstall the drivers that were made for the ADB but sadly I get this message now...
"Windows has determined that your driver software is up to date MTP USB DEVICE"
So the shield is now showing up in my computer manager under Portable Devices and not under the Android Devices like it did when I installed the custom drivers the first time.
Will this be an issue when I come to root?
Sigh!
Click to expand...
Click to collapse
the MTP driver is for plugging the shield in and viewing the file system. If the device isn't under android devices in device manager then you may need to reinstall the ADB drivers or just double check that the ADB can see the device (it may).
Open a command prompt. type "cd [path to the android sdk]\platform-tools"
Then type "adb devices".
It should list all the android devices it can make a debug connection to. If the Shield is in that list your good, otherwise don't proceed any further until you can rectify that.
The other solution is that you dont need ADB drivers on a linux system for some reason. Don't ask why. I havent a clue. But that would necessitate installing linux.
And something that is useful for finding the adb on the command line again in future for windows. You don't want to "cd" into the correct folder every time (the command line equivalent of opening folders). Sometimes you just want to be able to open the command prompt, type "adb devices" and it to just work. That's doable by altering your system PATH variable.
Open my computer. Right click > Properties, should open the System window.
Left side there should be a button saying "Advanced system settings".
It will open the "System Properties" window to the "Advanced" tab (if it isnt on that tab just switch).
Bottom of the window should be a button saying "Environment Variables...". Click it.
Now the window that appears will be split in 2. User variables and System variables. There is a PATH entry in both, it is best that you only change 1. If you are the only user or you only want your user to be able to access the adb, you can change the User variable. Otherwise you can change the system variable for the adb to work on all users. For me I had to add python to my path once but I wanted to do this for all users so I changed the system one, the PSP SDK I installed however altered the User variable by default. Make your choice and find the variable "PATH" in either one.
Click Edit. A window will appear with Variable name and Variable Value. At this point what I recommend doing is copying the entire contents of value into a notepad file and saving them as a backup. Then cancel and go back into it.
Code:
C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Lua\5.1;C:\Program Files (x86)\Lua\5.1\clibs;C:\Python27;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\
That is my Path variable.If you look the path variable is mostly a series of filepaths (or other variables too) which are seperated with ";". When you type a command such as "adb" into a command prompt what windows does is searches the current command prompt directory for a file it can execute which is called "adb" (it ignores extensions unless explicitly given one), if it doesnt find it in the current directory it searches each folder in the system path variable for the same executable (it ignores sub directories, it will only search the folders above on my system). So if we want to be able to type adb from any folder, we need the folder the adb is in to be added to the system path variable.
Simply add this to the end of it
Code:
;[whatever the path to the adb folder on your system is]
It will be whatever you had to add after "cd" to get to the adb earlier (must not leave out the C:\Users etc etc if its stored in your documents, cd will let you get away with ignoring that, the variable requires the FULL filepath).
Save the variable. Open a command prompt. Type adb, should work. If not, QUICKLY RESTORE THE BACKUP BEFORE WORKING OUT WHAT WENT WRONG. Should be safe with the broken variable to be fair, but you don't want to risk anything. If you dont think your going to use the adb often then simply dont bother updating the path variable rather than taking the (minimal) risk.
Wow my path variable is beginning to get a bit long now I only manually added python and lua to it. The rest will be the default entries and the SQL server stuff appears to be from installing visual studio. Yours probably wont match.

hehe you're going to hit me in a minute...
message deleted as I was being a moron....

ok I should be entirely clear as you guys are trying to help
ok I should be entirely clear as you guys are trying to help me so it's best i let you know what I have done up until this point.
Ok so I boot loader my shield.
I downloaded minimal ADB and Fastboot. I also downloaded the drivers you recommended in the forum.
I installed the drivers:
My shield showed up in the computer Manage list as a Portable device.
I chose to install the new drivers, it asked if I still wanted to go ahead as the drivers could not be verified and I said yes.
The drivers installed and the Shield changed from being in the portable list to showing up as an Android device.
Success I believe.
I then opened ADB BOOTLOADER and booted my Shield Manually.
I then typed in the relevant prompts in the command and a list of options showed up on the shield.
It showed my device number in the command prompt which was the one on my shield screen.
I then command the unlock function and the shield offered me the option to lock or unlock.
I chose Unlock and it then rebooted.
When it restarted, my computer reinstalled the device drivers and my shield had reset to factory settings (as it should).
I then looked in the Computer Manage list and my Shield had reverted back to being in the Portable Devices list.
I restarted both again and the Shield then showed up under Android Devices like it did when I installed the custom drivers the first time.
But the name of the device is Nvidia Shield - not Nvidia Shield ADB like in the tutorial video... not sure it that helps.
I enabled USB Debugging,
put the Superuser.apk and Su bin file into the minimal AADB and Bootloader folder.
I then put the Thor-insecure-boot.img in the Minimal ADB and Bootloader folder too.
I started up the command prompt from the minimal ADB and Bootloader.
I then saw this
C:\Program files <X86>\Minimal ADB and Fastboot>
I then typed in adb reboot boot loader and pressed enter
I got
error: device not found
So I decided to take the above advice and opened a command prompt
I typed in cd C:\tools\adt-bundle-windows-x86_64-20130729\sdk\platform-tools
and pressed enter:
It repeated what I typed and I then put in adb devices.
It then came back with:
List of Devices attached
but nothing was listed....
doh!

Progress!
Ok so I uninstalled my drivers to start again, plugged in the shield and it reinstalled my drivers and now under Android Devices it shows NVIDIA SHIELD ADB
Result!
Now I opened the dab cmd prompt
typed in
adb reboot fastboot
and it booted my shield! jolly good
But then I typed in
fastboot boot thor-insecure-boot.img
I then had
<waiting for device>
show up in the command window.
This is where it stayed.
On the screen of my shield I have options:
continue
restart bootloader
recovery mode
poweroff
Do I have to choose one of these in order for it to begin the thor img command?

C:\tools\adt-bundle-windows-x86_64-20130729\sdk\platform-tools Just incase you didnt get it earlier. That would be the path required for the variable change above. Just whack a ; on the end of the existing variable and throw that new path on the end and done.
But yes, adb devices not listing shield is not a good thing. Try reinstalling the ADB driver for the shield manually (you cant do it via device manager etc).

cool
I'm past that and now <waiting for device> problem to rectify. Am looking online now but there isn't much on there so far...
looking under device manager it shows up under Android Device as Nvidia Shield ADB but it also shows up under portable devices as SHIELD.
Whilst in boot mode the device only shows up in portable devices with a exclamation mark next to the device.
*UPDATE*
I uninstalled the portable device driver because I think it may have been causing confusion.
I then typed adb devices into CMD and a list of devices showed the serial number of the nvidia Shield.
I then typed in adb reboot bootloader in and it booted.
I then tried adb devices again and nothing showed up.
When I go into bootloader The Android Device: Nvidia Shield ADB driver disappears in manager once I go into bootloader mode. Is this normal?
Hmmmmmmm
definetly something to do with the drivers.
I'm on windows 7 64bit by the way.
Going back into device manager I noticed that there is another device under Other devices, upon looking at it it is Fastboot and has an exclamation mark in a yellow triangle next to it (Minimal dab and fast boot is open though).
Such a bummer as I'm so close yet so far

picture
ok so here is a pic of my devices list fastboot is there

before boot
This is the devices it can see before I put the shield in boot mode

devices seen after shielf in boot mode
the are the devices seen after I put the Shield in boot mode. It can't see any devices

waiting for devices
This is the screen on the shield in boot mode. The CMD screen says "Waiting for Devices"

Root installation and drivers issue

I installed the custom ADB drivers from this site, I then booted my Shield and am stuck on the command prompt screen as it says
<waiting for devices> when I try to install the thor.img
The Shield is unlocked and the usb debugging option is on.
Cannot work out what the issue is.
looking under device manager it shows up under Android Device as Nvidia Shield ADB but it also shows up under portable devices as SHIELD.
Whilst in boot mode the device only shows up in portable devices with a exclamation mark next to the device.
*UPDATE*
Ok so I uninstalled my drivers to start again, plugged in the shield and it reinstalled my drivers and now under Android Devices it shows NVIDIA SHIELD ADB
Result!
Now I opened the dab cmd prompt
typed in
adb reboot fastboot
and it booted my shield! jolly good
But then I typed in
fastboot boot thor-insecure-boot.img
I then had
<waiting for device>
show up in the command window.
This is where it stayed.
On the screen of my shield I have options:
continue
restart bootloader
recovery mode
poweroff
I uninstalled the portable device driver because I think it may have been causing confusion.
I then typed adb devices into CMD and a list of devices showed the serial number of the nvidia Shield.
I then typed in adb reboot bootloader in and it booted.
I then tried adb devices again and nothing showed up.
When I go into bootloader The Android Device: Nvidia Shield ADB driver disappears in manager once I go into bootloader mode. Is this normal?
Hmmmmmmm
definetly something to do with the drivers.
I'm on windows 7 64bit by the way.
Going back into device manager I noticed that there is another device under Other devices, upon looking at it it is Fastboot and has an exclamation mark in a yellow triangle next to it (Minimal dab and fast boot is open though).
Such a bummer as I'm so close yet so far

pictures
These are the pictures of the command promt when it is in boot mode, unboot mode and the devices installed.
When I go into boot mode on the shield the device called Nvidia Shield ADB dissappears from the computer manager window and the fastboot device has a yellow triangle with an exclamation mark next to it.
Very odd.

Yellow triangle means driver or device error (either one). The rest you have reached the limits of my knowledge.

appreciate the help
appreciate the help from everyone so far. I got through the bootloader stuff easily enough and now the shield is unlocked. This next bit is just knocked me for six as I have followed the instructions step by step and even taught myself some new stuff but this is not going according to plan.
So far:
I downloaded Andriod SDK
Ran SDK
clicked install and it installed lots of stuff including Android SDK tools, SDK platform tools and SDK Platform & ARM EABIv7a a system image in the Android 4.3 section.
I downloaded minimal adb and fastboot v1.1.3
I downloaded Superuser
I downloaded thor-insecure-boot.img
I downloaded the Universal_Naked_Driver_0.73 package
I then installed the Universal Naked Driver package which shows up on computer manager Devices under Android Devices as NVIDIA SHIELD ADB
I then dragged the thor and superuser files into the minimal adb and fastboot folder
I then plugged in my Shiled via USB 2.0
I started up the adb and fastboot CMD window
I first typed in adb devices and the shield showed up.
I then Typed in adb reboot bootloader
The shield went into boot mode.
I then retyped adb devices into the CMD window
The shield did not show up.
I the typed in fastboot boot thor-insecure-boot.img
The CMD window then said <waiting for Devices>
The shield screen showed that the device is unlocked and gave me 5 options:
Continue
Restart Bootloader
Recovery Mode
Reboot
Poweroff.
And then nothing.
This is the point I am at in terms of rooting.
The Device shows up in the Computer/manage window when plugged in but when I execute the adb reboot bootloader command it dissapears.
There is a Device in the Other Devices section of the Computer/manage window called Fastboot. This has a yellow triangle with an exclamation mark in it.
The CMD window can communicate with the Shield as it can make it go into boot mode but that's it.
Appreciate any help that can be given. Apologies for the length of post but it's only fair you know what I have done so far. Knowledge is power etc
I'm on windows 7 64bit os.

Latest pictures of the system
Ok so these are the latest picture of the system as it is now.
Currently there are two drivers showing for the Shield. One under Android Devices as Nvidia Shield ADB
The other is under Portable Devices as SHIELD. (picture 4 from the left)
When in boot mode the Android Device dissappears (picture 2 from the left)
There is a picture of the minimal adb and fastboot folder where I put the Superuser.apk file, the Su file and the Thor file - picture 3 (Is that all correct?)
There is also a picture of the command window when the shield is in boot mode. I type in adb devices and nothing shows up (picture 1)

Android SDK pics
And here is the SDK app running...

When your shield is waiting for fastboot commands it should show up as fastboot in device manager.
I had a terrible time with drivers too. My advice is to uninstall as many shield drivers as you can and then try to manually update the drivers making sure to get the fastboot driver installed. When you select have disk for the drivers the correct one will say Shield Fastboot

time to go fishing!
Ok I will try to uninstall drivers but not sure how to do it due to not exactly knowing which ones there are and where they are kept. Will take a look around. Thanks for the help though will try and find the fastboot drivers

gogul1 said:
Ok I will try to uninstall drivers but not sure how to do it due to not exactly knowing which ones there are and where they are kept. Will take a look around. Thanks for the help though will try and find the fastboot drivers
Click to expand...
Click to collapse
When I did it I plugged in my Shield and went into the device manager and uninstalled everything Shield related. I think it showed up in two places. Then I unplugged the Shield and when I plugged it back in I went back to the device manager and found the Shield again since Windows will auto install some sort of driver when you plug the shield in. I think this is when either there will be a yellow exclamation point next to one of them or windows will actually allow you to update the driver without giving you the stupid "driver is up to date" message.
That's when I right clicked on it and selected to update driver. At that point I made sure to use the "Have Disk" option and browsed to the universal driver folder. Once the universal driver list populated I was able to find the Shield fastboot driver in that list. I think my original problems started when I installed the Shield ADB driver which isn't needed and once that driver is installed the fastboot driver seems impossible to install because stupid windows keeps telling you the driver is up to date. By booting your Shield up using the home and back keys you are manually placing it in fastboot mode so you never need to use adb commands.
It is hard to remember but I do remember uninstalling everything I could and when I did finally update a driver I used the one with the word fastboot in it.
---------- Post added at 12:27 PM ---------- Previous post was at 12:21 PM ----------
gogul1 said:
These are the pictures of the command promt when it is in boot mode, unboot mode and the devices installed.
When I go into boot mode on the shield the device called Nvidia Shield ADB dissappears from the computer manager window and the fastboot device has a yellow triangle with an exclamation mark next to it.
Very odd.
Click to expand...
Click to collapse
If you get to this point again select to update that driver for the exclamation point and go to have disk and find the fastboot driver which you somehow get to by using the "have disk" option and browsing the universal drivers folder when you update the driver. Don't install the other drivers in the list, just the fastboot driver.

don't get the have disk option
uninstalled everything again. Next will be finding the Have disk option.

ah ha
I kinda see, when I go into Update driver Do I go into "let me pick from a list of device drivers?"
I click on that option and it gives me a list of devices but not sure what to choose. There was an android device option so chose that. I then went into the folder and clicked the "Have disk" option. I then navigated to the universal folder but there was nothing like bootloader or boot device in the folder.
I go into computer, right click, choose manage.
Go down to devices.
See OTHER DEVICES
In that folder is the SHIELD device with the yellow triangle next to it.
Right click it, choose update driver.
I choose let me pick from a list of device drivers on my computer.
It opens the window - select your device type from the list below
I choose show all devices
It opens the window - select the device driver you want to install for this hardware
I click the HAVE DISK button
I chose Install from disk option
I clicked the browse button
I navigated to the Universal naked driver folder and clicked open.
List of items in the folder are:
amd64 - folder
i368 - folder
android_apxusb.inf
android_winusb.inf
and that's it. So I chose android_apxusb.inf
right clicked on it to install.
window asking if I wanted to cancel or install anyway popped up.
chose install anyway.
Driver installed but still the same as before.
sigh

hmmmm
ok so this time I installed the ADB driver.
I then deleted the Portable Devices Driver named SHIELD.
I then booted my shield up again.
This time the Android Device Nividia Shield ADB turned into Fastboot and had the yellow triangle on it.
I then clicked on that chose to update drivers.
I then chose the Have Disk option. Chose the android_apxusb.inf file and clicked ok. There was the a long list of devices including asus eepad etc and I scrolled down to Nvidia Shield Fastboot.
I highlighted it clicked ok, it warned me that it didn't know if the driver was reliable, I clicked ok to install it anyway and the driver then went back up into the Android Devices folder in the device manager and was named Nvidia Shield fast boot.
So I opened up minimal adb & fastboot, then typed in adb reboot boot loader. The Shield booted, I then typed in adb devices but nothing showed up.
I then tried to do command the thor.img anyway, it say:
downloading boot.img
OKAY (0.810s)
booting...
OKAY (0.020s)
finished. total time 0.830s
The shield the rebooted and came back on as normal.
I then cut a paste the command lines:
adb shell
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
exit
but when it came to the mount command it said:
mount: operation not permitted.
hmmmm something is not right but cannot put my finger on it....:roll eyes:
When I went back into the Device Manager I saw that under Android Devices there are now two drivers
Nvidia Shield ADB
Nvidia Shield Fastboot
Not easy this stuff eh?

20 times
I have uninstalled and reinstalled the drivers 20 times now. Always the same result.
I am going to start this all over again.
Don't think I will get any luck.
I uninstalled drivers, plugged in the shield, the updated the drivers via the have disk method. The booted shield.
Then changed fastboot driver to updated driver again.
The results of the whole thing can be seen here

Please help
Right I uninstalled all drivers again.
When I restart and plug the shield back in it automatically installs two drivers.
One is in the Other devices folder named SHIELD and has a yellow exclamation mark next to it.
The other is in Portable Devices and looks to install ok.
What am I meant to do with these?
I try to update the Portable device driver but it doesn't allow me to update it.
I update the other one as nvidia shield fastboot but the when I actually boot the Shiled up it moves from the Android devices folder to the other devices folder and calls itself Fastboot (it has a yellow triangle next to it.
So I then update that one to Nvidia shield fastboot and everything goes ok installng the thor.img.
The the shield roboots and reinstalls the same driver... Now I have two Nvidia Shield Fastboot drivers in my Android folder.
Really Really could do with some help people please please please

Ok, if you have the fastboot driver installed which you should if device manager says fastboot without any yellow exclamation. Windows device manager needs to say fastboot while your shield is connected in fastboot mode (hold home and back while powering the shield up) Download these two files that I link below (or go directly to Gnurou's site and get them if you feel more comfortable https://github.com/linux-shield/shield-root) and put them in the same directory that your fastboot android package is in.. They are the two files needed from gnurou's site for rooting. One is a text file and one is some sort of .gz file (don't unzip this .gz file.
http://db.tt/oPHjgctM
http://db.tt/S0p9KMPi
If your shield is not yet unlocked do this:
1. Switch your SHIELD off (long press the NVIDIA logo button and select Power off).
2. Power your SHIELD on while maintaining the back and home buttons pressed (these are the two buttons that lie under the big NVIDIA-logo button, on its left and right). Release them once you see the bootloader screen.
3. Connect your SHIELD to your computer using a USB cable.
4. open a command window from your fastboot folder and type this (I am assuming you have the android fastboot all set up properly):
fastboot devices
4a. That should list a big long number. If it does that means your fastboot is working.
5. On your computer, enter the following command:
fastboot oem unlock
6. This will display the unlock menu. Read the disclaimer and think one last time about what you are doing. This is your last chance to stop.
7. Use the back and home buttons to select your option. If you decide to continue, select Unlock and press the NVIDIA-logo button to validate. Your personal data will be erased and your device marked as warranty-void permanently.
Regardless of your choice, you will be back to the bootloader screen. Using the same buttons, navigate to Poweroff and select this to power your SHIELD off.
Rooting (Shield should be unlocked at this point)
1. turn your shield off.
2. turn your shield on while holding the home and back buttons until you are in the bootloader.
3. plug the shield into the computer
4. open a command window from your fastboot folder and type this (I am assuming you have the android fastboot all set up properly):
fastboot devices
4a. That should list a big long number. If it does that means your fastboot is working.
Now type this:
fastboot boot zImage_dtb ramfs.img.gz
You should see the shield do it's thing with the penguins and then you're rooted.
This is how I rooted mine. It's way easier than doing that manual method. I copied some of the instructions directly from Gnurou's git site but the formatting is a little different. It all boils down to getting those drivers installed properly and you will know those damn things are installed properly when you have your Shield plugged into your computer while in fastboot mode (you held home and back before turning the shield on) and you can type fastboot devices and it lists a long number. I think people are shying away from this method because github can be confusing as far as how to download files and people seem to be confused about what all the other files are for on Gnurou's site when really you only need the two I linked.
Keep at it man. I know you'll get it.

Thanks
I was given a package of developer tegra nvidia drivers adk drivers to install.
Now I can boot my shield
When I type in fastboot devices my shield shows up as a long number
but when I type in fastboot boot zimage_dtb-ramfs.img.gz
I replies
cannot load zImage_dtb': No error
I put the files in the Minimal ADB and Fastboot folder.
Odd.
The drivers I have installed now are in this picture it works up until the point I need to execute the root
View attachment 2209196
This was my original issue in video form so you can see my problem.
http://youtu.be/amk7fkKJtSc

I was going to try and help here but after seeing how many different threads gogul1 has spread his issues though, I don't fell like spending 2 days trying to figure out what order his posts are in from thread to thread.

Guide to fix TWRP or CWM bootloop

This is how i fix my TF300TG stuck on recovery. I hope the steps descried below will help.
Long story, short:
For some reasons, seems like the WIPE command from TWRP and CWM recovery screw the partitions.
No partitions or microSD card can be mounted.
The tablet is now booting only in recovery mode or in fastboot mode (the screen with three icons - RTK, Android and WIPE) instead of Android.
IMPORTANT:
If your tablet reboot in fastboot mode DONT WIPE IT AGAIN! Just skip step 4.
First of all, MAKE SURE YOR BATTERY IS CHARGED!
Recharge your tablet for at least two hours.During the flashing process the tablet doesn`t charge.
Use the original Asus USB cable that came with the tablet or a high quality replacement cable. Cheap cables can and will cause problems.
Use a laptop or desktop with known good USB ports. If you have problems, try a diferent computer, some USB chips can cause troubles.
Disable the antivirus or screensaver, sleep etc...
1.Download these files:
from ASUS website: http://www.asus.com/Tablets_Mobile/ASUS_Transformer_Pad_TF300TG/#support
Drivers&Tools, on the OS tab select Android
click on Utilities and download latest version of ASUS PC Sync (you will need this for drivers)
click on Firmware and download the lastest available (you will need this for BLOB file)
Minimal ADB and Fastboot: http://d-h.st/gbx
install ASUS PC Sync and Minimal ADB and Fastboot (on fastboot installer check the box that make a shortcut to desktop)
unzip the firmware file downloaded from ASUS site
you will get a second zip file, unzip this one too
the folder unzipped from the second one contain a file called blob
copy or move the folder to the root of your drive C: or D: or whatever drive letter you have
2.Installing drivers:
connect your tablet to PC
you will get a message about Windows couldnt find driver bla...bla, ignore it and keep your tablet plugged
IMPORTANT: even if you previously installed ASUS PC Sync or other drivers and Windows recognize your tablet, you still need to change the driver.
right-click on My Computer-Properties and click Device Manager
find the Asus Android device - should be with an exclamation mark on it (the driver is not installed sign)
right-click on it and choose:
Update Driver Software..., Browse my computer for driver software, Let me pick from a list of device drivers on my computer, Have disk, Browse
go to C:\Program Files or Program Files (x86), ASUS, ASUS Android USB Drivers, Android and select android_winusb.inf
Asus Android Composite ADB interface will appear in the list of device drivers - don`t hit next yet!
uncheck Show Compatible Hardware and select Asus Android Bootloader Interface from the list, now hit next
3.ADB mode:
open Minimal ADB and Fastboot from desktop - from this point, keep it open
type: adb devices - and you should see some numbers under the List of device attached - thats your tablet
if you can`t see the tablet, try this command: adb start-server
4.Booting to "fastboot":
there are two ways to do this:
a) from adb window type: adb reboot bootloader
or
b) reset and hold vol-down (didn`t work for me, but maybe will work for someone else)
the three icons will appear on screen - NOW YOU ARE IN FASTBOOT MODE
if none of the above work try this:
in adb window type: adb reboot
wait until the tablet enter in recovery menu and type in adb window:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3
adb reboot bootloader
5. Flasing the blob
the credits for this part goes to buster99. He is the one who figured out the right commands for formatting partitions and flashing back the OS
here is his post: http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
here we go, one at the time in adb window:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system x:\your blob folder\blob (here you enter the path to your blob file, must end with blob, to point at the file)
fastboot -i 0x0B05 reboot
THE FLASH SYSTEM COMMAND WILL TAKE SOME TIME
be pacient and wait until the progress bar is 100% full on the tablet and you get the command prompt back in the adb window.
After reboot, the Android is back on.
Cheers and good luck!!

A big thank you alexhosu,
several months ago that my tablet was blocked, but I still kept hope
a solution would be found. I'm really happy for you and thank you again for sharing.
Long live XDA

me too
Thanks from me too; was enjoying 5.0 (timduru) on my TF300 when I went to upgrade and idiotically managed to get into a TWRP bootloop(interrupted a format of \data and then used 'wipe' from the boot screen by mistake...)
Your solution has saved my tablet
Am now carefully reinstalling Katkiss

Thanks
This saved my (veggie) bacon too, something went wrong when flashing new ROM (most likely user error - e.g. my fault). Tablet woud go into an eternal boot wouldn't finish booting, nandroid recovery did the same. Used this technique and have a working stock ROM from which I intend to reinstall TimDuru's Lollipop.
Thanks again

Followed the instructions.. Worked well, but getting error 963 when installing/updating anything in Play Store. Seems to be related to storage permissions. Some users are suggesting using format instead of erase. What's the difference? Could that help.
I did factory reset, reflashed and used fix permissions in TWRP but no luck...
alexhosu said:
This is how i fix my TF300TG stuck on recovery. I hope the steps descried below will help.
Click to expand...
Click to collapse

Big thanks from me.
I killed my tablet with an accidental restore to factory defaults while in cm12, an got stuck in an endless bootloader boot loop.
my tablet came back too life at the end of section 4 after adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3.
although getting adb to talk to the tablet was a fluke.
I just kept trying to send "adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3" while the tablet was loading (boot looping)

6 months of believing my tablet was dead, after letting CM12 do its own update thing, and now, thanks to the above instructions, I'm back online and its working with the stock rom.
Thank you so much for this. No idea why I couldn't find these instructions before, then I just gave up, back in business now!

Thanks a lot for your guide, this is what helped me fortunately unbrick my device, i was stuck in a boot loop with a broken recovery

Another tablet saved. Know your work is appreciated.

i have the same problem, the system doesn't pass the ASUS logo, i tired to log into fastboot (reset + volume down) and i was able to see the three icons but adb doesn't recognize my device. i see the drivers are correctly installed but no working adb. Any help is highly appreciated.

ajeevlal said:
i have the same problem, the system doesn't pass the ASUS logo, i tired to log into fastboot (reset + volume down) and i was able to see the three icons but adb doesn't recognize my device. i see the drivers are correctly installed but no working adb. Any help is highly appreciated.
Click to expand...
Click to collapse
Did you try entering "fastboot devices" or just "adb devices"? adb wont find your device in the bootloader, but using fastboot commands should unless it truly is not connecting for some reason.

Act32.97 said:
Did you try entering "fastboot devices" or just "adb devices"? adb wont find your device in the bootloader, but using fastboot commands should unless it truly is not connecting for some reason.
Click to expand...
Click to collapse
yeah Fastboot devices worked but it was not letting me flashing the rom, when i push the blob file it says 'sending' and stays in the same state for days.

ajeevlal said:
yeah Fastboot devices worked but it was not letting me flashing the rom, when i push the blob file it says 'sending' and stays in the same state for days.
Click to expand...
Click to collapse
I would try moving the blob to the root of the C drive and try the 7th command "fastboot -i 0x0B05 flash system C:\blob" just to make sure sometime of file permission type issue isn't happening on the pc side. Other than that the only kind of issue I think it could be would have to be the connection with the drivers, although if erasing the partition's works fine, I don't really see what could be going on.

I followed all the steps and delete, but when loading the file update.blob I get this error:
C: \ Users \ mikel> C: \ Users \ mikel \ Android \ android-sdk \ platform-tools \ fastboot flash system update.blob
error: can not load 'update.blob'
Can someone help me out?

TF300T KissKat
Theziggy said:
This saved my (veggie) bacon too, something went wrong when flashing new ROM (most likely user error - e.g. my fault). Tablet woud go into an eternal boot wouldn't finish booting, nandroid recovery did the same. Used this technique and have a working stock ROM from which I intend to reinstall TimDuru's Lollipop.
Thanks again
Click to expand...
Click to collapse
Hey, I know that I'm a couple years late on this. But, I was just given a Asus Transformer TF300T, and attempted to install the Kisskat custom rom. I unlocked the device with little issues. Rooted with little issues. But when it came to flashing the rom. I get his error saying that "no MD5 file found" and holds it there for a couple of minutes. Then gives me the failed install. My only option is to boot into recovery and restore the stock JB 4.2. If you could point me in the right direction, I would greatly appreciate it. I've searched the forum for someone with a similar issue, and couldn't find it. I hope that I'm not alone on this one. It would kill me to be stuck with the stock rom.

Hi i made a format data from TWRP recovery, and now i am in a recovery loop and got error of mount partitions, i can access to recovery and the screen with 3 icons, but when i plug to my pc it shows as uknown usb, i install the drivers but dosent reconose as a fastboot device, in minimal adb when i write fastboot devices the result is empty pleace help me.

Muito obrigado!
I know this must seem odd, being such an old thread and all but, after several years adding apps and changing ROMs on my wife's TF300T (my gift!) only these past weeks I had the need to search for help, after installing nougatella 7.1, which I did with success, only to stumble on endless logo loops and loading processes without conclusion. Don't get me wrong, the ROM looks great and it wasn't that hard to install but, after two weeks or so, gave me this problem and after correcting it and installing again the ROM, I got in trouble again...
After some five hours googling and trying different stuff, I finally found this thread and twenty minutes ago (around 2:AM) my ASUS returned to its (Jellybean) life!
Alexhosu, thank you so very much for such a detailed, yet easy to follow guide and, if you happen to come to Portugal on vacation and visit Setúbal, I'll have a bottle of Moscatel waiting for you!
Many thanks to Droidbound (who got me off the hook the first time the tablet went nuts!), and also Kevinthefixer, Gtanner00 and some other very inteligent, patient and thoughtful people, and all the guys who shared their difficulties and in a way helped me find the people with the fix.
For anyone interested in trying this method, I would say that it's paramount that you should stick exactly with what is asked and should pay real atention to what is the correct ROM update to download and use. If anyone needs help with translation to Portuguese, just say so.
Again, thank you so much for this!
JMonteiro

alexhosu said:
This is how i fix my TF300TG stuck on recovery. I hope the steps descried below will help.
if none of the above work try this:
in adb window type: adb reboot
wait until the tablet enter in recovery menu and type in adb window:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3
adb reboot bootloader
5. Flasing the blob
Click to expand...
Click to collapse
Thanks for your help :good: and I'm sorry for my basic English, but here is another tablet saved. Your instructions were clear and my tablet is working.
I hope this information helps, based in the next link (user sszyman): https://forum.xda-developers.com/showthread.php?t=2275035&page=9
in which he recommends using the following commands too:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p2
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p8
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p1
With these commands and "adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3" I was able to solve my Bootloop problem.
Honestly I don't know which of the commands worked, I used all several times.

How to unroot, lock bootloader and go back to stock?

For background, I have Verizon pixel 2 and am using a Mac.
I went down a massive rabbit hole last night reading through these forums and all the posts and was able to unlock bootloader, flash the January OTA and then root by doing the modified boot file with magisk. (interestingly enough the booting into recovery gives me red ! Over a dead Android and I could not load the OTA that way, nor did the adb sideload OTA comand work either, I had to push the extracted walleye img and then the zip file as discussed in one of the steps in some other thread here)
So anywho, in the end I now have a phone that gives me 2 errors when it reboots, one for unlocked bootloader and another for root telling me something is wrong with my phone and i should contact the manufacturer (which I read on here is normal), but my biggest issue is that my ADT alarm app doesn't work anymore (even if i check it off for hide in magisk). I feel like the root is just not worth it for me and I want to revert to completely stock image, even if it resets my phone and I have to re back everything up all over again like did when i had to do the unlocking of the boot loader.
So -- What are the steps I should take?
1)uninstall magisk from magisk manager?
2)delete magisk manager?
The above will unroot me, correct?
3)Do I push the stock boot image file onto the phone?
4) do I have to repush the latest OTA walleye image and zip file onto the phone again?
5) do I then do the adb reboot and do the flashing lock command (same command i did to unlock the boot loader) to lock up the bootloader and reset to stock?
If someone could be as explicit as possible in correctiong or validating my steps above it would be much, much appreciated.
I don't want to do any more unnecessary steps in flashing things than is needed so if I have extra steps above (perhaps 4 is not needed?) Let me know.
Thanks

Proceed with Caution
I am not an expert by any means, but can speak from personal experience. I was in the exact same situation as you. I followed the detailed steps to unlock the bootloader on my pixel 2, received similar issues, and the same prompt when the phone rebooted. All that to say proceed with caution.
My thoughts on questions 1 & 2: I personally wouldn't recommend you remove or delete magisk from the manager. When I did i had to reinstall it via twrp. My phone functioned fine, apart from the error at reboot.
My thoughts on questions 3 -5: When I followed the steps on XDA for your questions here I ended up bricking my Pixel 2 with locked bootloader from Verizon. Probably an error on my part, but wouldn't want someone else to go through the headache, hours of issues, and then an expensive paper weight.
My suggestion would be to:
1. Leave your phone as is and attempt to trouble shoot the app or apps you are having issue with
2. contact Google support on your phone and see if they would replace it
3. wait for an established method to unroot the pixel 2 here
Thankfully Google replaced my phone due to the error after rebooting, prior to me bricking it. I knew I had a replacement phone coming. So I attempted to go back to stock and that is when I messed it up.
Note sure this is exactly what you were looking for, but hope this helps you.

Dozens of posts with hundreds of pages on how to root but no advice on how to go back to stock cleanly?

iridium7777 said:
Dozens of posts with hundreds of pages on how to root but no advice on how to go back to stock cleanly?
Click to expand...
Click to collapse
Your version is Verizon which is making things more complicated. Generally when the bootloader is unlocked, you just hit flash-all.bat and then relock the phone. Given that the Verizon I'm not sure.
So you are on stock ROM with all these apks loaded ? If you go to settings, then do a factory data reset, you'll reset the phone back to stock and completely wipe the phone and return it to stock, at that point you can go into bootloader mode and relock.
Again your bootloader is unlocked, so the flash-all is your best option. If you see the red exclamation point with the error android laying on his back, you press power and up volume and toggle that and it will bring in the stock recovery which you can sideload the OTA however it may fail since you have magisk.
I bought my phone stock last year and have not rooted it or modified it in anyway. Too many problems and it only gets harder and harder as Google releases a new phone.

@mikeprius -- thank you for replying. after reading more on here, it seems like that's the way to go -- flash-all script, seems like i don't really need to do 1&2 that i wrote above as the flash-all will wipe that out by itself.
at that point i should be running the latest stock 8.1 but with an unlocked bootloader (and according boot up message screen) and i should be able to re-do the fastbook unlocking command to lock the phone back up.
(and yes, after reading even more now -- and i tried this yesterday -- i completely missed the portion about PWR + Vol Up button, that's why i think i had that issue, but still, i was able to push the update by pushing img and then the zip through).

iridium7777 said:
@mikeprius -- thank you for replying. after reading more on here, it seems like that's the way to go -- flash-all script, seems like i don't really need to do 1&2 that i wrote above as the flash-all will wipe that out by itself.
at that point i should be running the latest stock 8.1 but with an unlocked bootloader (and according boot up message screen) and i should be able to re-do the fastbook unlocking command to lock the phone back up.
(and yes, after reading even more now -- and i tried this yesterday -- i completely missed the portion about PWR + Vol Up button, that's why i think i had that issue, but still, i was able to push the update by pushing img and then the zip through).
Click to expand...
Click to collapse
If I were in your situation and the bootloader is unlocked, just use flash-all which has a wipe script then call it a day. I think trying to screw around even more is just a waste of time and I wouldn't even bother with the OTA, just erase and flash stock. You don't have to relock your bootloader if you don't want to, if you stay fully stock you may still be able to get OTA updates. I'm not sure if a bootloader locked is required someone can chime in as it has been awhile since I've done this, but over 1 yr ago, I just kept the bootloader unlocked, kept things stock and everything was good to go. Obviously there are security issues with an unlocked bootloader, but I'm sure you know this already

@mikeprius you keep saying reset/erase, do you suggest i re-set the phone and then flash the stock image?
i was just going to flash the stock image, i figured it already wipes the phone, and locking the bootloader would wipe it again, so what's the point of erasing all data prior?

Not to hijack this thread, but a question to add... I thought that there were kernels that would mask certain things to allow all of those apps to work, and get rid of the "problem with device" message.
Is that correct?

iridium7777 said:
@mikeprius you keep saying reset/erase, do you suggest i re-set the phone and then flash the stock image?
i was just going to flash the stock image, i figured it already wipes the phone, and locking the bootloader would wipe it again, so what's the point of erasing all data prior?
Click to expand...
Click to collapse
Just flash the stock images. It will auto reset.
Again, don't mess with anything just flash stock images, then go from there.
Also flash the newest version of the stock images out there. The pixel 2 will error if you try to downgrade any version.

here are all the steps to UNROOT and LOCK the boot loader on your Pixel 2 on a Mac (windblows users simply ignore all the "./" references).
1) download the latest ADB tools from google
2) download the latest factory Walleye image
3) unzip files from 1&2 into a common directory
4) edit flash-all.sh file and add "./" infront of every instance of "fastboot" in the script [windows users ignore this step]
5)hook up your phone to your computer in debug and file transfer mode. check that "./adb devices" loads your devide
6)type " ./adb reboot bootloader"
7) check that your device is still connected by typing "./fastboot devices"
8) type "./flash-all.sh"
===the script will run and your phone will be restored to stock, and UNROOTED. upon boot up skip through all of the setup steps and get to the phone settings as fast as you can. enable developer option, enable debug mode, set phone to data transfer ====
9) check that your phone is connect to your computer by "./adb devices"
10) type "./adb reboot bootloader"
11) check your devices is still connected by "./fastboot devices"
12) type "./fastboot flashing lock"
===== this will re-wipe your device again, you'll see the circle of death, and this will LOCK your boot loader back up again======
side note, feel free to skip over the steps where you check that your phone is still connected to the computer (./fastboot devices) if you're less paranoid and comfortable.

iridium7777 said:
here are all the steps to UNROOT and LOCK the boot loader on your Pixel 2 on a Mac (windblows users simply ignore all the "./" references).
1) download the latest ADB tools from google
2) download the latest factory Walleye image
3) unzip files from 1&2 into a common directory
4) edit flash-all.sh file and add "./" infront of every instance of "fastboot" in the script [windows users ignore this step]
5)hook up your phone to your computer in debug and file transfer mode. check that "./adb devices" loads your devide
6)type " ./adb reboot bootloader"
7) check that your device is still connected by typing "./fastboot devices"
8) type "./flash-all.sh"
===the script will run and your phone will be restored to stock, and UNROOTED. upon boot up skip through all of the setup steps and get to the phone settings as fast as you can. enable developer option, enable debug mode, set phone to data transfer ====
9) check that your phone is connect to your computer by "./adb devices"
10) type "./adb reboot bootloader"
11) check your devices is still connected by "./fastboot devices"
12) type "./fastboot flashing lock"
===== this will re-wipe your device again, you'll see the circle of death, and this will LOCK your boot loader back up again======
side note, feel free to skip over the steps where you check that your phone is still connected to the computer (./fastboot devices) if you're less paranoid and comfortable.
Click to expand...
Click to collapse
hey there. what is the command suppose to look like? every combination I try gives me an error:
first, I don't even enter the Fastboot command the same wayit given me an error:
Asads-MacBook:~ asad$ ./fastboot devices
-bash: ./fastboot: No such file or directory
so I try this: Asads-MacBook:~ asad$ fastboot devices
[serial #] fastboot
these are all the errors I get:
Asads-MacBook:~ asad$ cd /Users/asad/Desktop/walleye-opm1.171019.021
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: fastboot./: No such file or directory
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: ./fastboot: No such file or directory
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
fastboot: usage: unknown command ./flash
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: fastboot./: No such file or directory
...
how is the command suppose to look that I can edit it the right way?

"fastboot: No such file or directory" means that you didn't do step 1, step 3 on the file you didn't download, and there should probably be a "cd /<whatever the 'common directory'>" is. (I just created a directory named adb. That's good enough for me to know what it's for.)
You have to download adb and fastboot (which come in the adb tools file), unzip them to whatever directory you're going to use for flashing the phone, and cd to that directory.
Then, since you're evidently on MacOS, each command has to have ./ in front of it (that says "the current directory"). Try all that, then see what happens.

Rukbat said:
"fastboot: No such file or directory" means that you didn't do step 1, step 3 on the file you didn't download, and there should probably be a "cd /<whatever the 'common directory'>" is. (I just created a directory named adb. That's good enough for me to know what it's for.)
You have to download adb and fastboot (which come in the adb tools file), unzip them to whatever directory you're going to use for flashing the phone, and cd to that directory.
Then, since you're evidently on MacOS, each command has to have ./ in front of it (that says "the current directory"). Try all that, then see what happens.
Click to expand...
Click to collapse
yayy! that worked!
so i had adb and fastboot in a folder (platform-tools) and i had the factory image in its own seperate folder (walleye-files). i was making the cd; walleye folder and trying to flash-all.sh there.
so i had to put the files from the walleye folder into the platform-tools folder. Then I made platform-tools the cd. now when . i could now follow all the steps from 4-12 and got the pixel 2 the way it was OTB.
thanks!

Great! I'm not a Mac expert (last time I used one was the 128K Mac in 1985), so I'm not sure how to export a path in MacOs, so I gave you the complicated way, but you got it done anyway. (If you ever find out how to add the platform-tools folder to your path, you can leave adb and fastboot in there and keep the ROMs [walleye] in their own folder, cd to it and adb and fastboot will still work.)

delete don't work

Thread Closed Per OP Request
Don't work,
I give up
Thanks in advanced. All comments can help!

I have a tablet I can depure via USB and where I can root the tablet. But if I connect to the internet, the "registration and password" of university program enters and is saved (even after formatting it is stuck on this screen) blocking the tablet, I believe that after the internet loads, it installs this locking program ... What would be the name of this type of application? I'd like to know, how remove this app, to If connect in internet, we can block (and try install TWRP via internet with TWRP Management)...

C.Modica said:
Hello everyone !
I've been trying to resolve this issue for weeks. I have a tablet that I can't unlock (it's super hard, it's like Dark Souls of tablets). Well let's start.
He has a program that blocks asking for password and user (this a old from a university), where you request access via wireless or 2G/3G. without it you can't access it, so I believe I have to change his firmware instaled in, but I'm having a hard time to make it.
• Let's go to basic product information:
The chip is a RK3066 (same from TV BOX based on rockchip).
The model is YPY L1050 from POSITIVO (it's from Brazil).
- Software and Items
I have the drivers installed (correctly);
I have adb installed;
I have SD_Card;
I have acess from PC;
The tablet is unroot;
• Back to the items:
So, the good news is that I have the same tablet model, unlocked (with another type of ROM that I am unaware of). That works normally, without problems. Well, I saw a procedure that basically it is possible to extract this image from the good tablet, to the locked tablet. I did that, I ended up extracting a series of .img files from the unlocked tablet: boot, cache, kernel, system, etc... ok.
• Trying a extract from unlock same tablet:
I try transfer the copied files from "good unlock tablet" (extrated with AndroidTool), and put in (with the same tool) in the lock tablet... There is a problem, even before starting the operation, I have the error "Test Device Fail ", in the last is not possible to transfer files via USB (I can only do commands like" ResetDevice ", or export the images from the blocked tablet via AndroidTool... and yes I have the drivers instaled, commands like adb sideloader in the fastboot works).
• Trying a firmware found in internet:
Well, I tryed to download the firmware found on the internet corresponding to the device model, but unfortunately I have the same error as above. I download the .img firware original and using the RKBatchTool and have the same error (the operation don't start, give "Test Device Fail" in "Upgrade" and "Restore").
I believe that both operations do not accept transferring via USB.
PS: The tablet unlocked the command of "TestDevice" works fine.
• What I was thinking of doing:
1 - I think I need to take the all .img(s) files extracted from the unlocked device, put it in a single image (.img), put it in a SD_Card and in the "fastboot" take the option "update rkimage from external storage". But I don't know how to do this. (I try search for it);
2 - Somehow being able to do "apply update from external storage", maybe doing the same procedure above with an "update.img", but I also don't know how to do that (put all img. files together in the form of a one update.img).
3 - Have anothers options, like "apply update from ADB", the PC response this conection with tablet, (I can see the device with ''adb device'' cmds in sideload mode in PC). The problem is that I don't know how I'm going to send the .img file, if I send it inside a .zip (I even tried that, send all the .img files inside a .zip to see if it works. The tablet arrives to read the files but in the end the operation aborts). So my knowledge is lacking in this part.
4 - Another would be such a "ROM Dump." I'd like to do a "ROM dump" with an SD card, I even researched it on the internet but I didn't find this procedure to rockchip (only for Amlogic).
With SD Card:
There was a youtube that managed to unlock a tablet like that, but it was a previous model that I'd like to unlock (and different version of firmware, android etc). His method was to put a bootable sd_card, but he doesn't explain how he does it (he only gives the file done) and looking at the files internally, I just think they were converted to linux formats (system.tar.gz, userdata.tar.gz, some .sh .so files, and a bootenv.img, uImage etc) and with completely different names from .img... It is a pity that it is not for my Tablet model .
Well, that's it in the end, I need to change the firmware and I don't know how to do it.
PS: I tried other operations/methods as well, but I will not comment so that this post doesn't get big.
Thanks in advanced. All comments can help!
Click to expand...
Click to collapse
Instead of trying to package the .img files into one file, you should try flashing each .img individually via fastboot using commands with the following structure:
fastboot flash <name of partition> <name of partition.img>
The following commands are examples.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
You will need to use a separate command for each individual .img.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Instead of trying to package the .img files into one file, you should try flashing each .img individually via fastboot using commands with the following structure:
fastboot flash <name of partition> <name of partition.img>
The following commands are examples.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
You will need to use a separate command for each individual .img.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Hi, thanks for the reply. Well I can make it via adb sideload? I can't use the command "adb reboot fastboot". Because this command "adb reboot fastboot" only turns off the tablet don't restarting into fastboot/download mode (just turns off). But If I manually enter on the bootloader, I can access the adb sideload option, where the adb install on computer can detects the device via the "adb devices command" with sideload.

C.Modica said:
Hi, thanks for the reply. Well I can make it via adb sideload? I can't use the command "adb reboot fastboot". Because this command "adb reboot fastboot" only turns off the tablet don't restarting into fastboot/download mode (just turns off). But If I manually enter on the bootloader, I can access the adb sideload option, where the adb install on computer can detects the device via the "adb devices command" with sideload.
Click to expand...
Click to collapse
It isn't going to work via adb unless the device is rooted and then it won't be via adb sideload, it would be done by using dd commands to dd the .img files directly to their partitions.
Sent from my SM-S767VL using Tapatalk

I just found a solution. It requires some tinkering, though.
I had to use a machine running windows 7, because that's the only OS that the drivers worked.
Download the firmware for the Ypy L1050F here: https://www.stockrom.net/2018/07/l1050.html
It comes with the drivers, the ROM, and a tool called RKBatchtool 1.8
You'll have to decompress everything, open RKBatchtool and choose the firmware that is in the ROM folder (Not the DEMO one).
Now comes the tricky part: You gotta undo the 3 screws aroud the tablet, then pry it open with your fingers(remember to remove microSD and SIM first, to avoid breaking stuff!). I recommend startind by the side with the usb, hdmi and power ports to get some leverage. The back cover should pop right off. Then you have to locate the NAND chip in it. Should be a Micron one with 48 pins. The small circle at one of the corners of the chip represents pin 1. Plug your usb cable to the tablet. With the tablet TURNED OFF, use a SIM removal tool or very fine tip metallic screwdriver to short pins 17 and 18 on the NAND chip and plug the power jack into the tablet. RKBatchtool should show that a device was connected. You can release the screwdriver now and just click the "Upgrade" button in RKBatchtool. Now this is very important: DO NOT UNPLUG your tablet until everything is done. It'll tell you when it's done uploading the firmware and checking it. Enjoy your new usable tablet!
I scoured the internet and found this procedure being used for TV Boxes with the same RK3066 SoC. AFAIK, nobody else managed to do it so far, so spread the word.

You are awesome. Broke the internet! I will follow your procedures to try to unlock it. Many thanks again xmas for you.
[edit] don't work