Hey,
I stuck in a bootloop and can't solve the problem via Bootloader/Recovery,
because both modes are not working at all.
The problem occured when i tried to install TWRP via fastboot.
[TWRP 3.0.2-2 for Nvidia Shield Tablet]
I didn't know if this is only for the previous Tablet version, so i tried it.
But there weren't a version for K1.
Every time i use the keybuttons to use Recovery/Bootloader,
the device turns black for a while and boots again.
I already tried to use ADB/Fastboot/Odin to solve the problem, but none of these are detecting the device.
I looks like it is bricked, or some sort of it.
Is there anything i could try to use it again?
Any suggestions?
Does your computer see the device in fastboot mode? "fastboot devices" If not it could be your drivers.
It's IMHO not possible to brick a K1. TWrP is the same for both tablet versions.
edisso10018 said:
Does your computer see the device in fastboot mode? "fastboot devices" If not it could be your drivers.
It's IMHO not possible to brick a K1. TWrP is the same for both tablet versions.
Click to expand...
Click to collapse
I'n not able to get my device into fastboot mode, it turns black immediately after pressing the buttons.
Related
Hi All,
i have unlocked bootloader, Rooted ICS
now i installed the latest JB update via the SD card method (renaming it to E201_768_SDUPDATE).
did the power+vol down method. intstalled it and reboot.
now all i get is this message coming up.
"The Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image"
and it gets stuck there at the ASUS screen.
i have tried to install the APX driver from universal driver 0.7 TF700, and all i get is unknown device in win7 device manager.
hence i cant get into NVflash or Fastboot.
is there anything else that i can do to unbrick this tablet.
are there any other drivers that i need to install in win7 x64 or it to recognize that it is an asus tablet.??
Looks like the JB update didn't write everything properly - you still have the old bootloader. You should really have created backups for nvflash before trying to upgrade to JB.
But it's still not too late. Can you switch yout device to fastboot mode? If yes, then it's just a matter of getting your PC configuration right.
Then the next thing I would do: re-flash some custom recovery via fastboot, make sure it works and you have adb root access, check if /sdcard is ok, then install the AndroidRoot bootloader to create your blobs for nvflash, reboot into recovery, pull the blobs to your PC via adb, and only then try to upgrade to JB again.
_that said:
Looks like the JB update didn't write everything properly - you still have the old bootloader. You should really have created backups for nvflash before trying to upgrade to JB.
But it's still not too late. Can you switch yout device to fastboot mode? If yes, then it's just a matter of getting your PC configuration right.
Then the next thing I would do: re-flash some custom recovery via fastboot, make sure it works and you have adb root access, check if /sdcard is ok, then install the AndroidRoot bootloader to create your blobs for nvflash, reboot into recovery, pull the blobs to your PC via adb, and only then try to upgrade to JB again.
Click to expand...
Click to collapse
Hi, no unfortunately i cant access fastboot, i have tried using the TWRP method of and all i get it a message saying waiting for device. when i try to push the TWRP.blob file.
i think my problem is that the usb device drivers are not working hence win7 x64 cant recognize the tablet when it is turned off (APX mode i believe)
dazzyd said:
Hi, no unfortunately i cant access fastboot, i have tried using the TWRP method of and all i get it a message saying waiting for device. when i try to push the TWRP.blob file.
Click to expand...
Click to collapse
Let's check it step by step:
- On the device, can you still activate the fastboot mode (USB icon)?
- On your PC, you should see a USB device with vendor ID 0b05 and product ID 4daf. Should be visible somewhere in Device Manager under Windows, maybe someone else can give you details (under Linux everything is much simpler with lsusb).
- On the PC, "fastboot devices" should give you more than no output at all (some question marks, AFAIR).
_that said:
Let's check it step by step:
- On the device, can you still activate the fastboot mode (USB icon)?
- On your PC, you should see a USB device with vendor ID 0b05 and product ID 4daf. Should be visible somewhere in Device Manager under Windows, maybe someone else can give you details (under Linux everything is much simpler with lsusb).
- On the PC, "fastboot devices" should give you more than no output at all (some question marks, AFAIR).
Click to expand...
Click to collapse
Hi again, no i cant see the usb icon,
i am only getting this Asus screen
the Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image"
and it gets stuck there at the ASUS screen.
dazzyd said:
and it gets stuck there at the ASUS screen.
Click to expand...
Click to collapse
And if you hold down Volume-down while powering on, it's the same? In that case, 3 icons should appear before it tries to start the recovery kernel.
_that said:
And if you hold down Volume-down while powering on, it's the same? In that case, 3 icons should appear before it tries to start the recovery kernel.
Click to expand...
Click to collapse
yes i have tried holding down the volume-down while power on and still nothing. no icons appear.
dazzyd said:
yes i have tried holding down the volume-down while power on and still nothing. no icons appear.
Click to expand...
Click to collapse
Sorry, then I am out of ideas.
dazzyd said:
Hi All,
i have unlocked bootloader, Rooted ICS
now i installed the latest JB update via the SD card method (renaming it to E201_768_SDUPDATE).
did the power+vol down method. intstalled it and reboot.
now all i get is this message coming up.
"The Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image"
and it gets stuck there at the ASUS screen.
i have tried to install the APX driver from universal driver 0.7 TF700, and all i get is unknown device in win7 device manager.
hence i cant get into NVflash or Fastboot.
is there anything else that i can do to unbrick this tablet.
are there any other drivers that i need to install in win7 x64 or it to recognize that it is an asus tablet.??
Click to expand...
Click to collapse
You're done. You need to send out for repair. Sorry, but I haven't see any one here able to recover the device with the above message.
buhohitr said:
You're done. You need to send out for repair. Sorry, but I haven't see any one here able to recover the device with the above message.
Click to expand...
Click to collapse
hmm bummer.. no other way to force install a device driver to detect the tablet on my win7 pc.? all i need is a glimmer of hope that i can still talk to the tablet at the lowest level interface. ie APX mode.
dazzyd said:
hmm bummer.. no other way to force install a device driver to detect the tablet on my win7 pc.? all i need is a glimmer of hope that i can still talk to the tablet at the lowest level interface. ie APX mode.
Click to expand...
Click to collapse
The driver on your PC is not the problem. For using nvflash in APX mode you'd need the Secure Boot Key, which is unique for each device and which Asus does not give us, or the blob for the wheelie tool that can be created with the AndroidBoot hacked bootloader, which is also unique for each device. But for creating this blob, you need working fastboot access.
My explanation for my problem is pretty simple. My TWRP Backup is causing a soft-brick. I've soft bricked my TF300T before, but I was able to get my PC to detect it right away. Now I'm having a problem again.
Attempted to flash a custom ROM (Blackbean 6) on my stock, rooted, fully updated tf300, and it caused a soft brick. I had the problem still, after attempting to reflash BB6. I was using TWRP, and loading the ROM from my SD card.
After no luck with that, I attempted to reinstall the stock ROM from the Asus website. (10.4.3.18)
However, with my tablet being bricked I attempted to flash via Fastboot.
Problem 1: Soft bricked out of the device.
Problem 2: Fastboot won't detect the device on either Ubuntu 12.04, or Windows XP.
I have the drivers installed on XP, so I'm not sure what the problem is...
I hold pwr+vol down, and I go to the usb icon, and it says "Starting Fastboot USB download protocol" on the tablet.
But fastboot does not detect the device with the "fastboot devices" command, and using "fastboot -i 0x0b05 flash system [rom directory]" doesn't work either. It says Waiting For Device on ubuntu, and nothing on XP.
Same with both 10.4.3.18 and .13 ROMs.
I need to get this unbricked and back to stock asap...
I have no idea what else to do...
I have stupidly bricked my SHIELD why trying to root it. Before you ask, ADB and Fastboot does not work, I have no recovery and cold booting linux does not work.
tyushk said:
I have stupidly bricked my SHIELD why trying to root it. Before you ask, ADB and Fastboot does not work, I have no recovery and cold booting linux does not work.
Click to expand...
Click to collapse
Any information on how you got it in that state would be useful. However if you can't even get into the bootloader to use fastboot, there isn't much that can be done. Does the device not boot into bootloader at all or is it just not recognized as USB or by fastboot devices?
durgis said:
Any information on how you got it in that state would be useful. However if you can't even get into the bootloader to use fastboot, there isn't much that can be done. Does the device not boot into bootloader at all or is it just not recognized as USB or by fastboot devices?
Click to expand...
Click to collapse
My computer recognizes that a device was plugged in, but fastboot doesn't recognize the SHIELD. Something I may have forgotten to mention is that I have a microSD card I can use. The way that I got to this was by flashing the SuperSU update zip through ADB, flashing the CyanogenMod for the original SHIELD Tablet, then "flashing" (accidentally deleting recovery thinking that I was flashing the CyanogenMod one,) the recovery and rebooting.
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
mattlokk said:
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
Click to expand...
Click to collapse
Did you set:
Allow oem unlock in dev opt.
Fastboot protocol into BL?
Twrp app & manager need root to work.
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
thanks for the help, i'll try and work through this soon.
fpozar said:
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
Click to expand...
Click to collapse
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
mattlokk said:
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
Click to expand...
Click to collapse
Okay so I'm guessing you have stock ROM.
To flash TWRP you have to enter fastboot mode (vol down + power I believe) and flash the twrp image with fastboot flash recovery twrp.img (rename the shield tablet twrp to just twrp.img and place it into your easy adb and fastboot folder)
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
fpozar said:
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
Click to expand...
Click to collapse
Agreed. This is probably what is happening (as described on the TWRP webpage here:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Alternately, immediately rooting (flash SuperSU or Magisk) right after flashing TWRP, will prevent TWRP from being replaced with stock recovery.
Although the inconsistent fastboot connection, and how much trouble you had flashing TWRP initially, is a bit worrisome. Try using a different cable (maybe the one you are using is not connecting well?) try another USB port on the computer, and don't use a USB hub (connect direct to the PC).
Well, like they say: persistence is key. I kept pushing and trying new things until eventually.... I bricked the device. No, not really, it's working great now on LineageOS.
Thanks again to everyone who helped me out :good:. I'm still not sure exactly what caused TWRP to stop working on my device, however following this guide helped me fix it: https://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
The "flash-all.bat" restored everything to stock (including the recovery mode) and after that I was able to flash the latest TWRP and install Lineage.
Hi everyone.
Well it's a well known issue of yuphoria to get stuck on bootloop and you can find many youtube video to fix it too. My yuphoria is now experiencing the same problem. It is stuck in bootloop. Thing that is different in my case is it bootloops on anything. Even if i connect it to a power source or a laptop, it start itself and get stuck in bootloop. I also noticed that it is not recognized by my laptop in adb command prompt so i cant even rely on traditional "boot in recovery method". I tried to put it manually on fastboot mode by pressing down the pwer key along with vol down key. It does reboot in fastboot mode but still is unrecognizable by adb fastboot commands. I flashed bootleggers rom that was based on oreo 8.1 and was my daily driver on this device. Worked quite well too. I also installed twrp recovery but it seems to be absent now as I cant enter in recovery mode in anyway. Please suggest some means to fix this device. Thanks in advance.