To Install This Shizzle Press Continue
- Oct 24, 2007
- 15,259
- 6,962
- #141
Hi guys, I'm on the last software version of the k1 (5.4). Can I use this guide?
The general process should be okay, with some notes:
1) Best practice for rooting any Android device, you should typically use the most updated version TWRP. The linked TWRP page in the guide is automatically updated with the newest versions of TWRP, so you are good there.
2) You should also typically use an updated file for root (SuperSU or Magisk). Current version SuperSU is here: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Or consider rooting with Magisk, which has a lot of really cool features. I've switched from SuperSU to Magisk for a while now. But of course, the choice is yours: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
3) I don't personally use xposed. So I can't comment on how well it will work on your current version, current xposed files, etc.
- #142
- #143
Either you do not have the drivers installed, or you do not have permissions to do this.after i type fastboot oem unlock it seems to freeze..i cant type anything else into terminal. it just says waiting for any device.
The command should be run as administrator.
First try 'fastboot devices' it should report a serial number.
-your device should be in fastboot mode
-your device has to be bootloader-unlocked in developer settings
Verstuurd vanaf mijn SHIELD Tablet K1 met Tapatalk
- #144
I'm at a lose here. I have a K1 V1.0 and I followed your guide installing the Nvidia latest default factor recovery and rom. The rom have changed but the tablet is still stuck on the Nvidia boot screen, unable to boot into OS. Has this one been killed!
It was working before on an old Bliss Rom, but I changed the rom which installed a different recovery and it now fails to boot or install TWRP.
Help!
- #145
I'm at a lose here. I have a K1 V1.0 and I followed your guide installing the Nvidia latest default factor recovery and rom. The rom have changed but the tablet is still stuck on the Nvidia boot screen, unable to boot into OS. Has this one been killed!
It was working before on an old Bliss Rom, but I changed the rom which installed a different recovery and it now fails to boot or install TWRP.
Help!
It has been a little while since I last did anything related with rooting etc. I currently do not have the time to look into your problem but I would like to refer you to the Troubleshooting section of my original post and this post: https://forum.xda-developers.com/showpost.php?p=69316040&postcount=29
I hope this could help you.
- Toby
- Oct 24, 2007
- 15,259
- 6,962
- #146
I'm at a lose here. I have a K1 V1.0 and I followed your guide installing the Nvidia latest default factor recovery and rom. The rom have changed but the tablet is still stuck on the Nvidia boot screen, unable to boot into OS. Has this one been killed!
Which "guide" are you talking about? I only see in Post #1, the troubleshooting tip to flash stock boot.img, which is only the kernel (which is not the proper process to install recovery image). Unless you are talking about a subsequent post on this thread (I didn't look at all 15 pages!).
There are instructions on the NVIDIA download page where you get the stock recovery images. You need to flash system.img, boot.img and staging blob (all flashed separately in fastboot) in order to properly restore to stock. Missing any one of those, will likely cause the stock ROM to not boot.
You actually don't need to flash the recovery partition itself (even though the NVIDIA instruction say so). I've successfully restored the rest of the stock image (system, boot, staging blob), but purposely skipped to step to flash recovery.img (keeping TWRP).
If you want to get TWRP backup just fastboot flash recovery TWRP.img
- #147
Which "guide" are you talking about? I only see in Post #1, the troubleshooting tip to flash stock boot.img, which is only the kernel (which is not the proper process to install recovery image). Unless you are talking about a subsequent post on this thread (I didn't look at all 15 pages!).There are instructions on the NVIDIA download page where you get the stock recovery images. You need to flash system.img, boot.img and staging blob (all flashed separately in fastboot) in order to properly restore to stock. Missing any one of those, will likely cause the stock ROM to not boot.
You actually don't need to flash the recovery partition itself (even though the NVIDIA instruction say so). I've successfully restored the rest of the stock image (system, boot, staging blob), but purposely skipped to step to flash recovery.img (keeping TWRP).
If you want to get TWRP backup just fastboot flash recovery TWRP.img
The issue is that this one is one of the recalled versions. It works are you suggested with the stock NVIDIA rom (Removing the OTA files before connecting to the net.), but I don't trust this fix.
1. Issue with TWRP..
The latest Nvidia Shield Tablet version from TWRP site does not work after installing via ADB. The only version that works is 2.8.7 which wasn't from the official TWRP site. In fact all the versions from the official site fail to work on my Shield, I don't know why! I'm starting to think there is something wrong with their files.
2. Issue with Customs Rom..
Using the only version of TWPR that works (2.8.7) I've attempted to install Bliss, RR, Omni, CM and Lineage. All fail to install due to the first 2 line of their 'updater-script' file. The lines that start with 'assert'.
I've read that I needed to delete these lines with Notepad++, so I did. The installs seemed to work, but failed to write anything to the Shield! So it fails to boot.
So you see I'm at a loss with what I need to do next.
I guess install the stock NVIDIA rom and pray the fix works!
- #148
"4. Now type
Code:
adb reboot bootloader"
and
"5. Before you can do anything you must unlock the Bootloader
5.1 Type in
Code:
fastboot oem unlock"???
As soon as I type "adb reboot bootloader" it gives me an option screen that displays -
"Continue
Fastboot Protocol
Recovery Mode
Reboot
Poweroff"
and the CMD window displays
"<waiting for device>" endlessly.
Am I missing something, or is this guide missing a step? ---------- Post added at 11:20 PM ---------- Previous post was at 10:54 PM ----------
Am I retarded, or is something missing between"4. Now type
Code:
adb reboot bootloader"and
"5. Before you can do anything you must unlock the Bootloader
5.1 Type in
Code:
fastboot oem unlock"???As soon as I type "adb reboot bootloader" it gives me an option screen that displays -
"Continue
Fastboot Protocol
Recovery Mode
Reboot
Poweroff"and the CMD window displays
"<waiting for device>" endlessly.
Am I missing something, or is this guide missing a step?
EDIT 1:Yeah, you missed a step.
Between 4 and 5, there should be a step asking the user to check the device manager for a yellow "!" on fastboot devices. If its there, you need to install the fastboot drivers. Now it works.
EDIT 2: and it still doesn't work.... I was able to flash twrp 3.2.1-0 and access it once. I was unable to use it due to the lack of touchscreen function. Now, I cant get it to boot twrp again. I give up. Selling this unupgradeable pile-o-shizzle.
- Oct 24, 2007
- 15,259
- 6,962
- #149
The issue is that this one is one of the recalled versions. It works are you suggested with the stock NVIDIA rom (Removing the OTA files before connecting to the net.), but I don't trust this fix.
Is it recalled "pyro" tablet, or the K1? Since you've stated both in subsequent posts. The "pyro" tablet is the "original" (1st Gen) Shield tablet. The K1 is the 2nd gen version.
This post makes it sounds like you are scared to flash the stock image. But your previous post says you are having problem flashing the stock image. So again, you seem to be contradicting yourself, and I'm confused.
1. Issue with TWRP..
The latest Nvidia Shield Tablet version from TWRP site does not work after installing via ADB. The only version that works is 2.8.7 which wasn't from the official TWRP site. In fact all the versions from the official site fail to work on my Shield, I don't know why! I'm starting to think there is something wrong with their files.
Nothing wrong with the files from the official TWRP site. Those are all I've ever used. The much more likely and logical conclusion, is that something is going on with your particular tablet, that is causing the issue.
Try fastboot erase cache, and try flashing a different version TWRP from their website.
Or boot to TWRP 2.8.7 (which you presently have installed) and go into the "Wipe" options, and tap the "Format data" button. This sometimes solves problems with installing TWRP. But obviously, any user data on the phone will be wiped. Might not matter, since you have been trying different ROMs (should be wiping when doing so).
- #150
Is it recalled "pyro" tablet, or the K1? Since you've stated both in subsequent posts. The "pyro" tablet is the "original" (1st Gen) Shield tablet. The K1 is the 2nd gen version.This post makes it sounds like you are scared to flash the stock image. But your previous post says you are having problem flashing the stock image. So again, you seem to be contradicting yourself, and I'm confused.
Nothing wrong with the files from the official TWRP site. Those are all I've ever used. The much more likely and logical conclusion, is that something is going on with your particular tablet, that is causing the issue.
Try fastboot erase cache, and try flashing a different version TWRP from their website.
Or boot to TWRP 2.8.7 (which you presently have installed) and go into the "Wipe" options, and tap the "Format data" button. This sometimes solves problems with installing TWRP. But obviously, any user data on the phone will be wiped. Might not matter, since you have been trying different ROMs (should be wiping when doing so).
Thanks for your reply. I've got the Pyro version.
I've tried all of the Shield TWRP versions from the website and they don't work for me. The one I found was not from the TWRP site.
With every rom I tried I would always clear the caches with a format.
Also I get the Error 7 while installing ROMs so I have to delete the 2 lines from the install script, which seems to be a very common problem.
Anyway thanks again.
It's going back to the box .
- Oct 24, 2007
- 15,259
- 6,962
- #151
With every rom I tried I would always clear the caches with a format.
"Format data" (which I suggested) is completely different from wipe cache. Data is not even the same partition as cache. Plus, format is not the same as wipe. How about do as I suggested, instead of incorrectly dismissing it? It can't hurt, and might help.
- #152
Just curious as I'm purchasing this tablet soon, so I'm curious as to what some benefits are?
I'm also curious if we could update this thread with all current versions of gapps needed, twrp needed, and Nougat/ Oreo update (if needed.) The links in the beginning are old versions, and don't show which new updates are needed to use
- Oct 24, 2007
- 15,259
- 6,962
- #153
I'm also curious if we could update this thread with all current versions of gapps needed, twrp needed, and Nougat/ Oreo update (if needed.) The links in the beginning are old versions, and don't show which new updates are needed to use
I don't maintain the top post. But I can tell you:
- Top post contains link to the official TWRP webpage for Shield tablet, which lists all the versions (past and present), including the latest/current. It is generally recommended to use the latest (which currently is 3.2.1-0).
- Similarly, the link for SuperSU automatically will link to the latest stable SuperSU version. Again, the latest version is generally recommended. Currently, that is 2.82. And you can also verify that here: https://forum.xda-developers.com/apps/supersu
- You should also consider Magisk as a root solution (as opposed to SuperSU). Either will root your device.But Magisk has some very cool benefits that SuperSU doesn't. The current (and recommended) stable version Magisk is 16.0. https://forum.xda-developers.com/apps/magisk
- You don't need gapps unless you are flashing a custom ROM (which requires gapps to be flashed separately).
- I don't personally use Xposed, so can't really advise too much there.
- Don't know exactly what version TWRP I have on my Shield (the device is not with me ATM), but it is 3.xx something, and rooted with Magisk 16.0 on Nougat. So again, the latest versions TWRP and Magisk/SuperSU should work fine.
With the shield tablet receiving Nougat update, is it worth rooting/ Xposed?Just curious as I'm purchasing this tablet soon, so I'm curious as to what some benefits are?
I'm confused about what exactly you are asking here. Are you asking generally what the benefits of root are? Or something specific to Nougat?
- #154
"Continue
Fastboot Protocol
Recovery Mode
Reboot
Poweroff"
I select "Fastboot Protocol" - the screen flashes to black, and I see again
"Continue
Fastboot Protocol
Recovery Mode
Reboot
Poweroff"
What am i doing wrong?
- #155
That is the fastboot/bootloader screen iirc. Just move on to the next step of installing twrp recovery.After entry "adb reboot bootloader" i have in screen this:
"Continue
Fastboot Protocol
Recovery Mode
Reboot
Poweroff"I select "Fastboot Protocol" - the screen flashes to black, and I see again
"Continue
Fastboot Protocol
Recovery Mode
Reboot
Poweroff"What am i doing wrong?
- #156
- #157
My Sheild is getting pretty slow and sleepy these days, keen to flash a custom ROM but not sure what's the latest/greatest. Any suggestions? Thanks.
I am currently running LineageOS 14.1 and its working great. Its the best rom imho
- #158
I am currently running LineageOS 14.1 and its working great. Its the best rom imho
I went and followed the instructions and installed leneage OS and the instructions were more than fundamental, Thanks mate!!!!
Pimping it as I write this, I'm finally free of lots of crap. Once again running android as free as much as possible, at least I don't have to disable lots of crap (don't have another name for what I had).
Lots of thanks.
- #159
- #160
Try another usb port, if you have a pc, try a port which is directly at the back connected to the Mainboard, on a Laptop try a usb 2.0 port if available. Otherwise try restarting your PC, logging out and back in also works, the important part is restating the adb daemon and the reinitialization of the windows usb driver. Also try to install the shield driver again from the Device Manager.Hi there, I try to root my shield k1. It have Nougat. The thing is that when I type adb devices, doesn't list any devices. I checked the device manager and there was no problem with my device drivers.....Kingroot doesn't want to install and I really don't know what to do. Any suggestions?
Similar threads
Source: https://forum.xda-developers.com/t/complete-guide-shield-tablet-k1-root-custom-rom-and-xposed-framework.3315965/page-8
0 Response to "To Install This Shizzle Press Continue"
Post a Comment