Nvidia Shield Tablet K1 stuck on Bootloader Info Screen / Bootloops -- Need help - Shield Tablet Q&A, Help & Troubleshooting

Hey everyone. So some time ago I unlocked the Bootloader, rooted and flashed with custom ROM my Nvidia Shield K1 and flashed TWRP. All was going well untill I decided to flash another ROM with an app (which was stupid indeed) Long story short it seems now as if I have no ROM and no recovery and all I got is the "Bootloader info screen" or whatever its called.
So the only thing I can make it display is:
[nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - Unlocked
Serial Number xxxxxxxxxxxxxxxxxxxxxxx
Press <Power> to select [...]
Continue
Fastboot Protocol
Recovery mode
Reboot
Poweroff
1. Using Continue does nothing, just says booting failed for like 100ms and goes back to where it was.
2. Fastboot Protocol just reboots the devices to the same thing after like 2 sec
3. Recovery mode same as Fastboot Protocol
4.Reboot and Poweroff does what it says
I've tried everything I could find online with it. No physical key combination can make it boot the ROM or TWRP.
I tried adb fastbooting with minimal adb and fastboot like Ive done times before with this Shield K1 and I cant make it see this device. ( "adb devices" wont list it)
I have tried using different USB ports, usb drivers, usb cables, PCs, fastboots and reinstalled everything multiple times and nothing changes.
I tried using any and every USB driver, ADB fastbooting Nvidia offers for this device.
The PC itself seems to detect the tablet just fine. Pluggin and unpluggin results in a notification and the android device is detected in Device Manager properly.
Powering off and on the tablet also results in a notification on the PC.
I have no idea what to do at this point and my last hope is this thread.

I had the same issue. Finally decided to reflash to stock and all is well

Related

[Q] Unable to fastboot or recovery mode; just unlocked

Hi. I've recently bought my TF700 and upgraded to JRO03C.US_epad-10.4.4.25-20121228 (JB 4.1.1). Now I want to root my device, so I first unlocked the bootloader using the ASUS unlocker. That went fine, since it says "the device is unlocked" in the boot sequence. The device boots and works properly.
Now I wanted to get to the stock recovery mode for a backup, but it fails miserably. I get to the four icon menu (RCK, Android, USB, Wipe) and select RCK. Then an android icon with a blue rotating icosahedron in its chest apears for a couple of seconds and then a "dead" android with it's cover opened and a "!" enclosed in a red triangle. After a couple of minutes, the device reboots normally (I can force that by pressing down the power button for 10 seconds).
I tried to get to fastboot by choosing the USB icon, but it does nothing (just freezes in the four icon screen and stops responding to any other buttons); the PC doesn't see an USB device of any kind. I tried connecting the USB cable both before and after selecting the USB icon with no difference. I'm sure I have at least some good drivers because I can use adb with my device when the OS is running.
I'm new to this device, so I may be doing something wrong. Any suggestions? Thanks in advance.
The stock recovery can only apply stock updates, you cannot use it for making backups.
Fastboot mode should display some message similar to "fastboot protocol enabled", the rest appears to be driver problem on your PC. Fastboot mode uses a different USB ID, so having ADB working does not mean that also Fastboot will work.
_that said:
The stock recovery can only apply stock updates, you cannot use it for making backups.
Fastboot mode should display some message similar to "fastboot protocol enabled", the rest appears to be driver problem on your PC. Fastboot mode uses a different USB ID, so having ADB working does not mean that also Fastboot will work.
Click to expand...
Click to collapse
Thank you, _that. Whatever drivers it might need, I cannot install them because no USB device of any kind appears in my computer besides my keyboard. I think I should be getting "Starting Fastboot USB download protocol" or something. How can I get fastboot to work?
Sorry, it seems it was a USB port problem! I changed the port and the fastboot device is now available in my PC. Fastboot is now able to send commands like 'reboot' to my device.
Thanks for your clarification about the stock recovery mode, _that.

TWRP Trashed my tab. ADB shows offline. Fastboot unresopnsive.

Hi folks. My rooted and unlocked tablet got a TWRP update to try a new rom. I was running KatKiss for around a year. I'm not unfamiliar with flashing and mods for routers, phones, and Androids. So here goes.
I have read much of fixes before posting. So far, no joy!
A reboot after updating TWRP just sits at the ASUS screen, shows the device is unlocked.
Holding the power button until it switches off and then vol down and power on shows:
Key driver not found Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.27.5-20130902" A03
I get a winking RCK. RCK, android, wipe data options. Selecting it gives a:
Starting Fastboot USB download protocol
Booting Recovery kernel image
Booting failed
And a red Unrecoverable bootloader error (0x00000000).
Restarting with vol down and powering up shows Asus Fastboot Interface with :
USB\VID_0B05&PID_4DAF&REV_0000
USB\VID_0B05&PID_4DAF
As hardware id's. Started out as unknown device and I have used several ADB/Fastboot drivers after text searching the inf files.
If I force an ADB driver I can adb devices and get a serial number and offline.
Stopping the server and doing it all over again gives the same results.
No fastboot ever. No response when I enter fastboot devices, using the fastboot driver or adb driver. Device manager will not show both devices, and I can get APX mode to work. But I'm pretty much thinking that is useless for me.
If I remember correctly I had both fastboot and adb in my device manager before. I have a newly reformatted pc with win 7 64. Also have a 32 bit win 7 box.
I wish I could give more preliminary info. But so far none of the sure fire methods have worked. It has been my assumption that if a device is soft bricked, you can usually get it working again
Can anyone help? If only so I can get it working to get files off of it stuck in internal memory.
Thanks!
supwiddiss said:
Hi folks. My rooted and unlocked tablet got a TWRP update to try a new rom. I was running KatKiss for around a year. I'm not unfamiliar with flashing and mods for routers, phones, and Androids. So here goes.
I have read much of fixes before posting. So far, no joy!
A reboot after updating TWRP just sits at the ASUS screen, shows the device is unlocked.
Holding the power button until it switches off and then vol down and power on shows:
Key driver not found Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.27.5-20130902" A03
I get a winking RCK. RCK, android, wipe data options. Selecting it gives a:
Starting Fastboot USB download protocol
Booting Recovery kernel image
Booting failed
And a red Unrecoverable bootloader error (0x00000000).
Restarting with vol down and powering up shows Asus Fastboot Interface with :
USB\VID_0B05&PID_4DAF&REV_0000
USB\VID_0B05&PID_4DAF
As hardware id's. Started out as unknown device and I have used several ADB/Fastboot drivers after text searching the inf files.
If I force an ADB driver I can adb devices and get a serial number and offline.
Stopping the server and doing it all over again gives the same results.
No fastboot ever. No response when I enter fastboot devices, using the fastboot driver or adb driver. Device manager will not show both devices, and I can get APX mode to work. But I'm pretty much thinking that is useless for me.
If I remember correctly I had both fastboot and adb in my device manager before. I have a newly reformatted pc with win 7 64. Also have a 32 bit win 7 box.
I wish I could give more preliminary info. But so far none of the sure fire methods have worked. It has been my assumption that if a device is soft bricked, you can usually get it working again
Can anyone help? If only so I can get it working to get files off of it stuck in internal memory.
Thanks!
Click to expand...
Click to collapse
nobody?

[Q] no adb and fastboot access - no root possible?

Hello everyone!
I'm trying to root my Shield K1 (Android 6.0) since hours, without success because:
I have no acces via adb. Im using the latest adb and also the right drivers (see picture) but I alwas get the message "unauthorized" in adb.
I can't boot my tablet into fastboot mode. When I press the power button + volume up to come into the menu and I select fastboot protocol, the tablet just starts again into the same menu - so i don't get into the fastboot mode. Pressing the powerbutton + volume down don't works either.
I have tried already almost everything: uninstallig drivers/reinstalling it, factory reset on my K1,...
So how I can root my phone without adb or fastboot? Can anyone help?
Even the recovery mode is broken I think, after booting into it, the green android with an red triangle is shown.
Is there something wrong with my K1?
PS: In the menu, which is shown after pressing power + volume up, is standing:
[nvtboot] (version UNDEF_BUILD]
[bootloader] (version UNDEF_BUILD]
Device - locked
You need to enable USB debugging in the developer settings and then allow debugging access from your computer by accepting a popup on your tablet.
Yes, I know this and I did this of course. But there never poped up something on my tablet.
So I also resetted the debugging setting, wiped the tablet, but nothing helped.
1. Sometimes the micro USB cable you use can be bad so I would suggest trying a different cable (especially since you have a K1 which doesn't come with a charger or cable).
2. Fastboot mode is that screen with the menu, that's why "fastboot protocol" just takes you back to the same screen. Also, recovery mode on the stock tablet just shows the android icon and triangle, so your recovery mode is fine.
I would suggest booting the tablet into android (so not the fast boot or recovery mode) and connect it to the windows PC using different cables until the authorisation pop up come up.
I am having the same issues as the OP, the only difference is my bootloader says "unlocked."
I was able to get authorization from the computer, no issues there, however fastboot will not find the device and neither will adb when at the "fastboot mode."
I'm trying to get fastboot so I can flash a recovery, but no luck to this point.
Anyone have any ideas or suggestions?
fl4r3 said:
Fastboot mode is that screen with the menu, that's why "fastboot protocol" just takes you back to the same screen.
Click to expand...
Click to collapse
Thanks so much mate! :good: That's the sentence, that helped me. I didn't know this menu is already the fastboot mode. So if one know this it's quite easy to proceed.
Problem solved - tablet already rooted
The adb access is still "unauthorized" but doesn't matter anymore.
No problem, glad you you got it sorted.
It's odd your ADB access is still unauthorised, but at least it still works.
jpk17 said:
I am having the same issues as the OP, the only difference is my bootloader says "unlocked."
I was able to get authorization from the computer, no issues there, however fastboot will not find the device and neither will adb when at the "fastboot mode."
I'm trying to get fastboot so I can flash a recovery, but no luck to this point.
Anyone have any ideas or suggestions?
Click to expand...
Click to collapse
Just as an FYI....I got mine working. Needed to reinstall the nvidia drivers... Got authorization, etc... so assumed working and as we all know assuming is bad!
Sent from my wx_na_wf using Tapatalk

Shield Tablet problems: ADB, Recovery Mode, Fastboot... = DEAD?

I can imagine that you all are tired of reading this headline, but seriously, ME TOO.
I have been looking for information about this issue during several weeks and I have not found any solution, so I would extremely thank you if you take your time reading this problem and trying to help me finding a solution.
Some months ago I tried to flash a ROM on my Shield Tablet, I followed all the steps from a topic in this forum: [Complete Guide] SHIELD Tablet K1 Root, Custom Rom and Xposed Framework but I wanted to try a different ROM: CARBON-CR-5.1-MOO-WEEKLY-shieldtablet-20170216-0454 (the name of the file) And now I have a tablet that is stuck on the Carbon launch screen every time I turn it on, when I press volumen down + power it goes into the screen buttt as soon as I press recovery mode the only thing it does is to restart itself and stays stuck in the NVIDIA screen. The Minimal ADB and Fastboot do not recognize the tablet with the adb devices command.
When I turn on the tablet (and stays stuck into the IOS icon as I mentioned before) and connect it to the PC the device manager recognize the tablet as a Portable device with the name: MTP USB device, when I press the power+volumen down the PC recognize the tablet as an Android Device -> Android Bootloader Interface. And this is all the information I have about my problem...
May you help me?
Thank you in advance. I hope your knowledge will help me and other people with the same problem. If you need more information of this problem let me know and I'll answer ASAP. If you have any idea tell me and I'll try it.
Warlain said:
when I press volumen down + power it goes into the screen buttt as soon as I press recovery mode the only thing it does is to restart itself and stays stuck in the NVIDIA screen. The Minimal ADB and Fastboot do not recognize the tablet with the adb devices command.
When I turn on the tablet (and stays stuck into the IOS icon as I mentioned before) and connect it to the PC the device manager recognize the tablet as a Portable device with the name: MTP USB device, when I press the power+volumen down the PC recognize the tablet as an Android Device -> Android Bootloader Interface. And this is all the information I have about my problem...
May you help me?
Click to expand...
Click to collapse
Your device is not, dead, it's only taking some time to reflect
First of all, I understood that you're able to access to the device's bootloader menu, through the button combo (black screen with white text, "continue","restart bootloader","recovery mode"), and you selected "recovery mode".
Now, unless you have flashed a custom recovery, there's nothing to do with the shield's stock recovery, so, just enter in the bootloader menu as you did, without selecting any option.
You are now in "fastboot mode", in order to check your device's connection you have to write in the adb shell
Code:
fastboot devices
If you see your device you can now boot a custom recovery that will help you to fix the problems you caused, I would follow this link: (copy-paste, can't post links)
"nvidiashieldzone.com/shield-tablet/shield-tablet-root/root-shield-tablet-v1-marshmallow/"
And do the 8th step, in "Root procedure"
Fastboot with TWRP
Type “fastboot devices” Copy and make sure your Shield Tablet is visible.
If your Shield Tablet is listed, type “fastboot boot twrp-20151227-EXPERIMENTAL-shieldtablet-m.img” Copy (or whatever you named it) and hit enter. If your TRWP image filename has a space in it, you may have issues.
After 15 seconds or so (be patient), you should see the TWRP Recovery screen. Note: This experimental version has some UI issues, just keep at it.
You may be prompted with something to do with the system being READ ONLY. Accept the default and swipe.
Click to expand...
Click to collapse
Use fastboot to wipe cache (fastboot erase cache) then try to flash TWRP (with fastboot) again. This will often clear up issues with being unable to boot to TWRP (at least on other devices).
If you are able to boot TWRP, restore the TWRP backup (if you made one) or put another ROM on the phone, and flash it.
I also have this kind of problem. After i update twrp by flashing it and restore a backup the sistem doesnt show. Stucks on nvidia logo. I tried even restore my recent backup but nothing also. Any idea ?
'Artemis' said:
Your device is not, dead, it's only taking some time to reflect
First of all, I understood that you're able to access to the device's bootloader menu, through the button combo (black screen with white text, "continue","restart bootloader","recovery mode"), and you selected "recovery mode".
Now, unless you have flashed a custom recovery, there's nothing to do with the shield's stock recovery, so, just enter in the bootloader menu as you did, without selecting any option.
You are now in "fastboot mode", in order to check your device's connection you have to write in the adb shell
Code:
fastboot devices
If you see your device you can now boot a custom recovery that will help you to fix the problems you caused, I would follow this link: (copy-paste, can't post links)
"nvidiashieldzone.com/shield-tablet/shield-tablet-root/root-shield-tablet-v1-marshmallow/"
And do the 8th step, in "Root procedure"
Click to expand...
Click to collapse
Done, Thank you a lot! It starts working again!!!

Neffos X-1 stuck in bootloop

Heya folks,
I have just attempted my first time flashing TWRP on my TP-Link Neffos X-1 following this guide: https://rootmygalaxy.net/twrp-root-...nd_Install_TWRP_Recovery_On_TP-Link_Neffos_X1.
Its looking kinda grim. It starts with the orange state Message and that the device will boot in 5 seconds, however after that it starts with an infinite bootloop. I also cannot access the Recovery (vol up + power), for it simply doesnt work anymore after the guide. When I plug it into my pc, it will automatically start with the bootloop (I can shut the phone off with vol down + power).
Attempting to get into fastboot mode over ADB (adb reboot bootloader), returns with the message error: device '(null)' not found. I think that is due to it not being recognized in the device manager(it doesnt show my phone anymore but unknown device). I tried to install the phone driver for the uknown device, however that keeps failing. I think its due to the phone permanently connecting and reconnecting to the pc.
So I'm wondering of what to do. I guess the biggest issue is that the drivers are not recognized, but as long as the phone keeps on restarting every couple of seconds i doubt i can properly install the driver. You guys got any ideas?
My guess is you haven't installed on Windows PC the appropriate Android USB Driver matching the device
I mean the appropriate USB driver had to be there for me to flash it with the TWRP in the first place, right?
Think I clearly said that the additionally required USB-driver has to be installed on Windows PC.
I have this one installed https://rootmydevice.com/download-neffos-usb-drivers/, is this the additionally required usb driver?
So far, despite what driver I pick for the device, it shows the code 10, device couldnt be started - probably because it never gets past the starting screen but keeps rebooting
slayingduck said:
Heya folks,
I have just attempted my first time flashing TWRP on my TP-Link Neffos X-1 following this guide: https://rootmygalaxy.net/twrp-root-...nd_Install_TWRP_Recovery_On_TP-Link_Neffos_X1.
Its looking kinda grim. It starts with the orange state Message and that the device will boot in 5 seconds, however after that it starts with an infinite bootloop. I also cannot access the Recovery (vol up + power), for it simply doesnt work anymore after the guide. When I plug it into my pc, it will automatically start with the bootloop (I can shut the phone off with vol down + power).
Attempting to get into fastboot mode over ADB (adb reboot bootloader), returns with the message error: device '(null)' not found. I think that is due to it not being recognized in the device manager(it doesnt show my phone anymore but unknown device). I tried to install the phone driver for the uknown device, however that keeps failing. I think its due to the phone permanently connecting and reconnecting to the pc.
So I'm wondering of what to do. I guess the biggest issue is that the drivers are not recognized, but as long as the phone keeps on restarting every couple of seconds i doubt i can properly install the driver. You guys got any ideas?
Click to expand...
Click to collapse
Try this TWRP file: TWRP_3.2.3_NeffosX1_TP902A_by_kiruha_21.img
The thing is, I cannot flash anything due to my phone constantly rebooting while inserted in the pc usb-slot. Neither ADB nor my device manager recognize the device and as mentioned before, I cannot install any drivers
slayingduck said:
The thing is, I cannot flash anything due to my phone constantly rebooting while inserted in the pc usb-slot. Neither ADB nor my device manager recognize the device and as mentioned before, I cannot install any drivers
Click to expand...
Click to collapse
Some MTK devices has this: Press both VOL+ & Power buttons. Only remove 2 buttons when you see Bootloader mode (recovery; fastboot; reboot system) or directly in the Recovery mode. Now you can use fastboot.
With the SPFT you can use same tip above. In the SPFT choose DOWNLOAD and plug USB device. Process to flash stock ROM or stock recovery.img & boot.img start.
If not start pugging USB: choose DOWNLOAD - press VOL- and plug USV device. You can try with buttons like only VOL- or VOL+ or combo buttons VOL+&VOL- or VOL-&VOL+ or other button combination.
You can try FIRMWARE UPGRADE too.
That's depend about LOCKED or Unlocked bootloader process that you made before actions!
If you unlocked bootloader so only need patience. If not so that's no good.

Categories

Resources