Ok, so here is a problem I have never had with an android device....
I cannot get my tablet to boot into recovery..I have done it in the past as I installed revolver a long time ago (HTK75.revolver-3.11_epad-8.6.5.21-20111216)
Now I cannot get into the recovery to install a new rom....
I have rooted the phone, Good to Go.
I have downloaded and ran the recovery installer app....
I have tried using the reboot to recovery app (reboot to recovery) which just reboots and keeps my transformer at the ASUS boot screen.
I have tried the power + volume down option and this is what I get:
Android US_epad-user bootloader <e> released by "US_epad-8.6.5.21-20111216
checking for android ota recovery
skiping android ota checking
checking for RCK.. press key <VOL_UP> in 5 sec to enter RCK (So I press it)
Booting recovery kernel image
Thats is...it jsut sits there until I reboot it back to normal again....
Any advice!? I have tried so many different options I have read about on the boards...(plus google)
Try using PERI rooted option to reflash recovery, or run in term emulator with blob on device,
su
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
reboot
I have tried so many different apps and this one finally worked!!!!!
Your awesome, thanks man!
Thanks given
Glad it worked well :]
reset in a circle while trying to flash
Sorry for my english
Can I ask you to describe step by step how you recovered your tablet
updating its firmware tf300t 4.0.3 to 4.1 encountered a similar problem:
The Device is Unlocked.
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.3.30-20120604" A03
Checking for android ota recovery
Booting recovery kernel image
When rebooted around and only the volume up button can turn it off.
How do you advise to try to recover it, if you can explain step by step
Alternatively see the use of this program [TOOL]PERI-0.4
http://forum.xda-developers.com/showthread.php?t=1681155
p.s. missed one point in which the boot program and should be used as a stop / pause
this cycle if it is necessary to use the program as confused with one thing:
(EG don't let any commands run at the splash screen or in recovery.)
I did a factory reload of a rooted phone with CWM.
Now for the CWM issue the Moto G loaded OK and then said there was an update for android to fix some bugs. This was 4.4.3. I loaded it and it gets half way and it then says
"Signature verification fail"
at the bottom of the screen and
" Install Untrusted Package"
The options are yes, no or go back
at the top....
whichever one I try it then tries to boot shows the Android / Motorola screen and starts up gets a txt message for 2-3 seconds... it then goes back to Android CWM recovery with the same options as above and repeats the process. again and again and again. No function keys will stop this cycle which just repeats again. This continues until the battery dies.
any ideas ? how can I override this action in CWM v6.0.4.6 and force it to do a factory reload ? any help or advice much appreciated.
The following thread had a similar problem and was fixed... http://forum.xda-developers.com/showthread.php?p=53404637
NerdNoob1210 suggested...
"If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose."
unfortunately I can't get into bootloader. I can connect usb and it makes no difference. therefore adb commands dont work. it just goes straight into screen described with those three options. I'm hoping that there is an override action in CWM which isn't power and volume down which do nothing.
If not how can I force it into bootloader instead please ? any suggestions appreciated.
First of all, I have gone through every similar post, but none helped and so created a new post
Device: Nexus 5
Tried to flash: Stock 5.0 image from Google's website
Bootloader unlocked: Yes
Method used: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Tried step 1, it gave an error: archive does not contain system.sig, but it still went ahead with the process and when tried to boot into recovery to perform a wipe data/factory reset, it showed a small Android logo with a red triangle and exclamation mark.
So I tried step two and manually flashed all the files in the order and in the end (after erasing cache), I tried booting into recovery again and got the same thing. Android logo with a red triangle and exclamation mark inside it. I thought the recovery wouldn't have flashed properly, I booted into bootloader again and manually flashed recovery.img and tried. Still the same. WIthout doing a wipe data/factory reset, I do not think the phone will boot up properly. What am I to do here? Stuck in this and cannot use the phone at all. Any help at all is welcomed. Thanks in advance!
Any questions, please ask me.
Edit: I tried locking and then unlocking the bootloader and tried step 2, while booting into the recovery mode, instead of the red triangle, I got the standing Android logo with the blue sphere sort of thing revolving in it. What do I do next when I see that Android logo? Thank you
troll_warhead said:
First of all, I have gone through every similar post, but none helped and so created a new post
Device: Nexus 5
Tried to flash: Stock 5.0 image from Google's website
Bootloader unlocked: Yes
Method used: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Tried step 1, it gave an error: archive does not contain system.sig, but it still went ahead with the process and when tried to boot into recovery to perform a wipe data/factory reset, it showed a small Android logo with a red triangle and exclamation mark.
So I tried step two and manually flashed all the files in the order and in the end (after erasing cache), I tried booting into recovery again and got the same thing. Android logo with a red triangle and exclamation mark inside it. I thought the recovery wouldn't have flashed properly, I booted into bootloader again and manually flashed recovery.img and tried. Still the same. WIthout doing a wipe data/factory reset, I do not think the phone will boot up properly. What am I to do here? Stuck in this and cannot use the phone at all. Any help at all is welcomed. Thanks in advance!
Any questions, please ask me.
Edit: I tried locking and then unlocking the bootloader and tried step 2, while booting into the recovery mode, instead of the red triangle, I got the standing Android logo with the blue sphere sort of thing revolving in it. What do I do next when I see that Android logo? Thank you
Click to expand...
Click to collapse
I just flashed my nexus 5. i am getting the *.sig error too. After flashing, it was taking very long time in boot animation. I nearly to force shutdown. But after around 10 minutes, it is successfully boot.
sorry for my english, just wanted to share my experience. hopefully it help
troll_warhead said:
First of all, I have gone through every similar post, but none helped and so created a new post
Device: Nexus 5
Tried to flash: Stock 5.0 image from Google's website
Bootloader unlocked: Yes
Method used: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Tried step 1, it gave an error: archive does not contain system.sig, but it still went ahead with the process and when tried to boot into recovery to perform a wipe data/factory reset, it showed a small Android logo with a red triangle and exclamation mark.
So I tried step two and manually flashed all the files in the order and in the end (after erasing cache), I tried booting into recovery again and got the same thing. Android logo with a red triangle and exclamation mark inside it. I thought the recovery wouldn't have flashed properly, I booted into bootloader again and manually flashed recovery.img and tried. Still the same. WIthout doing a wipe data/factory reset, I do not think the phone will boot up properly. What am I to do here? Stuck in this and cannot use the phone at all. Any help at all is welcomed. Thanks in advance!
Any questions, please ask me.
Edit: I tried locking and then unlocking the bootloader and tried step 2, while booting into the recovery mode, instead of the red triangle, I got the standing Android logo with the blue sphere sort of thing revolving in it. What do I do next when I see that Android logo? Thank you
Click to expand...
Click to collapse
The first boot takes a LONG time. Just let it go for a while.
jsgraphicart said:
The first boot takes a LONG time. Just let it go for a while.
Click to expand...
Click to collapse
So, I did try as you said. I left it but it kept booting for more than 20 minutes. What to do now?
Same thing happened to me.. You just have to do a factory wipe and then reboot..
When you get to the screen with dead android, with the power button pressed, press vol up key once and you will be in the recovery screen. Do a factory wipe from the screen and reboot..
It should be working now..
manujosephv said:
Same thing happened to me.. You just have to do a factory wipe and then reboot..
When you get to the screen with dead android, with the power button pressed, press vol up key once and you will be in the recovery screen. Do a factory wipe from the screen and reboot..
It should be working now..
Click to expand...
Click to collapse
Incredible. That, worked! I did a rookie mistake by pressing both at the same time which led to nothing. Got it up and running. Thank you everyone for their inputs, couldn't have done without it
The factory wide and reset does not work for me. Stills tuck at the boot animation.
I recently had the same issue with my Nexus 5 and have been back and forth with Google Play support to resolve the issue with no success on that front. However I did get my issue resolved, which was caused by a corrupt /persist filesystem. What I did was this:
Flash CWM Recovery
Reboot into Recovery
notice that /persist isn't mounted, try mounting it and it will fail
Launch and ADB shell
run 'e2fcsk /dev/block/platform/msm_sdcc.1/by-name/persist'
let it fix any errors found
try to mount the /persist partition, it should work now
(Optional) reboot to bootloader, flash whichever recovery you want or stay with CWM
reboot into system, all should be fine now
After successfully repairing and mounting /persist within CWM Recovery I powered off and just flashed the stock 5.0 image from the Google Factory Images page.
A special thanks to bitdomo for his information here which ultimately fixed my issues:
http://forum.xda-developers.com/showpost.php?p=54252961&postcount=3
Hi all!
My Shield Tablet was running the latest Lollipop (Rooted, of course) & had TWRP installed. Everything was happily cooperating...until tonight. Over the last few nights, I kept getting the notification that a system update was available, but I kept dismissing it. I assumed it was Marshmallow. I've been reading about the Wi-Fi issues, so I waited for the re-release.
Long story short here. I downloaded the newest Marshmallow OTA zip from Nvidia (through a weblink) & was going to wait until this weekend to install it. Well, tonight came, so I booted into TWRP & flashed the OTA, then flashed the SuperSU. Rebooted. NOW, comes the fun part...
It's stuck on the Nvidia logo & won't boot further. I've waited around 15 minutes & still stuck at the boot screen! I then forced power off, pressed & held the power button & volume down. I wanted to get into TWRP & go back to Lollipop, as I still have that OTA file in there. Turns out that TWRP is now gone! It just won't boot up or go into recovery. Nothing, but the boot screen, even from recovery.
I think I screwed up big time here! How can I get my tablet working again? If it's already been answered, please point me in the right direction. Obviously, I have to use my laptop to make it work again, so I need help with this one. If there's a step-by-step on getting my laptop to feed the Shield with a ROM, recovery & such, that is my goal. This forum is very large & it could take hours to find the right answer. Someone in here might remember where that topic is.
Thanks a bunch!
By the way, since the K1 is only $199, it may very well be worth buying it & having Marshmallow as an OS. I have the Nexus 6P with Marshmallow & I like it far better than Lollipop. Then later down the road, I can get the Shield Tablet working again & give it to a family member.
***EDIT*** I failed to mention after sleeping on this post, that I was STOCK rooted Lollipop, & I have a full backup of the system just after rooting & SuperSU'ing (if that's a word!) Lollipop on the microSD card, if that helps get the tablet back. I'm able to place the microSD card in a USB card reader in the laptop for transfer too.
I am stuck on bootloop too after the update (mine was stock non k1) I can only get into fastboot, tried factory image to no avail
madasahat said:
I am stuck on bootloop too after the update (mine was stock non k1) I can only get into fastboot, tried factory image to no avail
Click to expand...
Click to collapse
Same issue here, I did a backup of my tablet before I did the update and it wont go past the nvidia shield logo. Also when I try to do the power and volume up to factory reset it, it will end up showing the andriod laying down with an exclamation mark and red triangle saying no command.
It says that [nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - Locked
serial number
press power up and down etc
continue
fastboot protocol
recovery mode
reboot
power off
Mine is stock as well weird thing is ti will have me put in my combo to un-encrypt it. Mine was an over the air update.
It seems that we have a genuine problem upgrading to Marshmallow from Lollipop, something out of the norm here...unless we've just forgotten how to upgrade a rooted device.
snukkums said:
Same issue here, I did a backup of my tablet before I did the update and it wont go past the nvidia shield logo. Also when I try to do the power and volume up to factory reset it, it will end up showing the andriod laying down with an exclamation mark and red triangle saying no command..
Click to expand...
Click to collapse
I did that just a little while ago & the screen stays black when I press the power button to bootup, even volume down + power. It simply won't come on. BUT...after waiting for around 20 minutes, I can now power + volume down with the choices of:
continue
Fastboot Protocol
Recovery mode
Reboot
Poweroff
That's all it will do. None of the first 4 selections do anything but go to the boot screen which stays on indefinitely, except for Fastboot Protocol, which will only turn the screen black. I never got Andy lying down with the spinning atom in his chest, which I would see while OTA'ing a stock non-rooted device (my Nexus 6P for example), as you saw.
snukkums said:
Same issue here, I did a backup of my tablet before I did the update and it wont go past the nvidia shield logo. Also when I try to do the power and volume up to factory reset it, it will end up showing the andriod laying down with an exclamation mark and red triangle saying no command.
It says that [nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - Locked
serial number
press power up and down etc
continue
fastboot protocol
recovery mode
reboot
power off
Mine is stock as well weird thing is ti will have me put in my combo to un-encrypt it. Mine was an over the air update.
Click to expand...
Click to collapse
Exactly the same problem and same screen
It says that [nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
---------- Post added at 03:49 PM ---------- Previous post was at 03:29 PM ----------
A quick update looks like it is going to be an RMA! Again for me. We really need the full 4.0 recovery img from nvidia to try and get us going without sending it back
Well I guess I am going to talk to nvidia support. I also RMA'd mine for the battery issue. Did Nvidia say they would send an RMA right away?
Update: So I talked to Nvidia support and they are in the process of getting an rma set up for me I just sent them all of my info.
***UPDATE!!***
I was able to ADB & Fastboot into my Tablet & loaded it back to Lollipop using the directions & images here...https://developer.nvidia.com/gameworksdownload. Look for the NVIDIA SHIELD Tablet WiFi Recovery OS Image about a quarter way down the page. Click on those words, then click Download. Then I Accept. Then once the download is going, click on Instructions. It tells you step-by step how to install the recovery image to get you back up & running.
It wiped my tablet, but there wasn't much on there to begin with & Google Play apps are downloading in the background after going through the initial welcome screen once the tablet boots back up.
I haven't checked if TWRP is back on there, but I'll do that at a later time. And then root again to get my rooted apps back on.
*** No recovery, as I see Andy lying on his back with a red triangle over his gut. I fastboot flashed TWRP into it, it accepted it, but it didn't stick. Keeps showing the red triangle. I'll keep trying to load TWRP.
snukkums said:
Same issue here, I did a backup of my tablet before I did the update and it wont go past the nvidia shield logo. Also when I try to do the power and volume up to factory reset it, it will end up showing the andriod laying down with an exclamation mark and red triangle saying no command.
It says that [nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - Locked
serial number
press power up and down etc
continue
fastboot protocol
recovery mode
reboot
power off
Mine is stock as well weird thing is ti will have me put in my combo to un-encrypt it. Mine was an over the air update.
Click to expand...
Click to collapse
There is a way to boot recovery without flashing but can't remember the command and not sure if I can do it from fastboot. Thanks for the info I have tried the factory images but with no luck
so i found that flashing a file called tegra124-tn8-p1761-1270-a04-e-battery.dtb via "fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb"
fixed [nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
to show a build from there I did a factory image flash-all.bat in fastboot and bam all good
This is a really easy fix! Happened to me too, it's not a big issue. It has to do with the version of SuperSU not being compatible with the shield.
BEFORE CONTINUING!!!!!! ALL OF THESE ARE UNDER THE ASSUMPTION THAT YOU HAVE THE OG TABLET AND NOT K1!!!!!
Here is a link to TWRP for 6.0. It's really glitchy UI wise, but everything else works just fine. I would recommend flashing it to your recovery.
Here is a link to a stock rooted 6.0 ROM. The only difference between this ROM and full stock, is that tegraOTA is removed.
Once you have these files downloaded, you're going to need an ADB and fastboot suite, as well as shield ADB drivers. If you still have these from the first time you installed TWRP, you won't need to redownload them.
First, you're going to want to boot into the TWRP image without flashing to make sure that it works.
Code:
fastboot boot </path/to/twrp/recovery>.img
then, if the image booted successfully, reboot into fastboot and then you need to flash TWRP using this command.
Code:
fastboot flash recovery </path/to/twrp/recovery>.img
Next, boot into TWRP and push the ROM file to your SD card
Code:
adb push <path/to/ROM>.zip /sdcard/TWRP/rom.zip
Finally, flash the ROM as normal and wipe cache/dalvik. If you're having trouble finding the zip, it should be located on the internal storage in a folder called TWRP.
Happy Marshmellow-ing!!!
Links there to all three ROM's have been removed.
But at least I have TWRP again. Thanks!
/Now if I can figure out why the SuperSU in that edition of TWRP won't root it for me. I slide it & the unit powers off. Every. Time. Oh, well...small steps. Small steps!
madasahat said:
so i found that flashing a file called tegra124-tn8-p1761-1270-a04-e-battery.dtb via "fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb"
fixed [nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
to show a build from there I did a factory image flash-all.bat in fastboot and bam all good
Click to expand...
Click to collapse
OMG DUDE YOU SAVED MY SHIELD!!!!!!!!
Thanks man
madasahat said:
so i found that flashing a file called tegra124-tn8-p1761-1270-a04-e-battery.dtb via "fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb"
fixed [nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
to show a build from there I did a factory image flash-all.bat in fastboot and bam all good
Click to expand...
Click to collapse
hi, where can i find this file?
rhamnik123 said:
hi, where can i find this file?
Click to expand...
Click to collapse
Google it
When i choose "fastboot protocol" it reboots and returns to the same menu, my windows 10 does not detect the Shield.
chapas said:
When i choose "fastboot protocol" it reboots and returns to the same menu, my windows 10 does not detect the Shield.
Click to expand...
Click to collapse
Hi, had the same problem getting it detected, so I went to device manager, located fastboot device with a yellow mark, uninstalled it and then plugged it again and it got the correct drivers automatically.
Hope it'll help you...
madasahat said:
so i found that flashing a file called tegra124-tn8-p1761-1270-a04-e-battery.dtb via "fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb"
fixed [nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
to show a build from there I did a factory image flash-all.bat in fastboot and bam all good
Click to expand...
Click to collapse
That didnt work for me I flashed 4.3 Update Stock Rom.
Any ideas
Wolf2231 said:
That didnt work for me I flashed 4.3 Update Stock Rom.
Any ideas
Click to expand...
Click to collapse
Flash everything then the db file without restarting so do it all at once. Do you get to the nvidia boot screen? As mine took 30 minutes to boot after a reflash
madasahat said:
so i found that flashing a file called tegra124-tn8-p1761-1270-a04-e-battery.dtb via "fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb"
fixed [nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
to show a build from there I did a factory image flash-all.bat in fastboot and bam all good
Click to expand...
Click to collapse
How did you manage to figure this out? When I flashed the stock image I was unable to boot. After flashing this then doing the recovery again it worked fine. This is very strange.
rasstar said:
How did you manage to figure this out? When I flashed the stock image I was unable to boot. After flashing this then doing the recovery again it worked fine. This is very strange.
Click to expand...
Click to collapse
Wonder if this would work on my Sheild K1 6.0 rooted with twrp-3.1.1-1 bricked tablet? No problem getting into twrp recovery now...