Bricked stuck on "no command" loop - Asus ZenPad 10 Questions & Answers

I was tinkering with my Z500m after a factory reset seemed to cause issues. As I could not boot into recovery I ended up, stupidly it now seems, running "fastboot erase cache", which led to a boot loop on the Asus splash page. I then thought I could do a factory reset through fastboot by erasing system, data and cache (I may have read this somewhere in xda), but this resulted in the tablet booting just to Asus splash and then straight to the 'dead android' with the red triangle and exclamation. This flashes every few seconds. All combinations of post, vol up, vol down, result in nothing, and I cannot get it to boot to fastboot or recovery, let alone a normal boot. If I connect it to my pc, there is a beep from the pc suggesting it is not totally bricked.
I have scoured this site and other useful web sites, but can find no solution. Does anyone have anything to suggest?

Hello, have you found a solution for this problem ?

Related

N7 in an erase loop

I tried to install LineageOS on my N7. When I tried to perform a factory reset, the system went into an erasing state, but it stays there fore-ever. It is not rebooting completely, but the erasing animation is restarted every x seconds.
I am not able to enter recovery / bootloader. All combinations with power + volumeUP / volumeDOWN don't do anything. After the Google logo is continues to the Erase situation.
So I am not able to enter fastboot.
But I am also not able to use ADB. The device is recognised, but unauthorized.
Has anyone an idea how to proceed?
i had the same problem, and i think that your device is hard bricked. i recently replaced the motherboard with a new one and solved the problem!

ultratablet bricked? using factory reset...

i tried to do a factory reset on my ultratablet using the option in settings, but the process seems to have hung. after about 45 minutes i force-shutdown and rebooted, but it boots into recovery and says "Formatting /data..." it seems to be stuck there.
i can access the ultratablet with fastboot and i have tried flashing boot/recovery/system that way, and my computer shows all signs it works... but when i fastboot reboot, i am back in the same recovery as before, with the "formatting /data..." message.
is there any way, through fastboot, to tell the tablet to stop doing everything, so i can flash the images?
or is this thing finally dead?

lg k20 plus won't boot into twrp

So im trying to root my lg k20 plus. I flash the twrp recovery image and it says everything is successful. Then reboot to the factory reset screen by holding volume down and power then releasing power when i see the lg logo and pressing again. I guess the k20 plus doesnt have a regular recovery screen all it is is a factory reset anyways select yes twice to reset and it should boot into twrp recovery. only mine won't.. it goes to the screen with a yellow exclamation point that says "your device software cannot be checked for corruption. lock bootloader", and then will flash the lg logo and go straight back to the other screen and just cycle over and over forever. i can just press power and it will boot up like normal but i can't get to twrp recovery. I;ve tried recovery images from two other sources but nothing still any help would be appreciated
Randallray2711 said:
So im trying to root my lg k20 plus. I flash the twrp recovery image and it says everything is successful. Then reboot to the factory reset screen by holding volume down and power then releasing power when i see the lg logo and pressing again. I guess the k20 plus doesnt have a regular recovery screen all it is is a factory reset anyways select yes twice to reset and it should boot into twrp recovery. only mine won't.. it goes to the screen with a yellow exclamation point that says "your device software cannot be checked for corruption. lock bootloader", and then will flash the lg logo and go straight back to the other screen and just cycle over and over forever. i can just press power and it will boot up like normal but i can't get to twrp recovery. I;ve tried recovery images from two other sources but nothing still any help would be appreciated
Click to expand...
Click to collapse
Try this thread.....
https://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-k20-plus-t3616248
Did you save the twrp "recovery.img" as a different name? At first i named it something else and had the same problem. I just renamed it "recovery" and all was well.
Randallray2711 said:
So im trying to root my lg k20 plus. I flash the twrp recovery image and it says everything is successful. Then reboot to the factory reset screen by holding volume down and power then releasing power when i see the lg logo and pressing again. I guess the k20 plus doesnt have a regular recovery screen all it is is a factory reset anyways select yes twice to reset and it should boot into twrp recovery. only mine won't.. it goes to the screen with a yellow exclamation point that says "your device software cannot be checked for corruption. lock bootloader", and then will flash the lg logo and go straight back to the other screen and just cycle over and over forever. i can just press power and it will boot up like normal but i can't get to twrp recovery. I;ve tried recovery images from two other sources but nothing still any help would be appreciated
Click to expand...
Click to collapse
Did you find a solution? 3 yrs later.

Stuck at "Google" screen after TWRP wipe

Hi,
I did a TWRP wipe (everything checked) to prepare for a restore to stock, but my device is now stuck at the very first "Google" screen with the pad lock icon at the bottom. How do I get it to boot?
goister said:
Hi,
I did a TWRP wipe (everything checked) to prepare for a restore to stock, but my device is now stuck at the very first "Google" screen with the pad lock icon at the bottom. How do I get it to boot?
Click to expand...
Click to collapse
So since everything was checked, that means you wiped the system partition. The device will not boot if you do that unless you flash a factory image via fastboot or new ROM via TWRP
OK, I thought wiping /system would just bring it back to factory state. 2 questions now
1. How do I get to recovery when it's always stuck at the Google screen with no adb access? Would I have to wait for the battery to run out (hence turn off), charge it for a while, then use the buttons to boot to recovery, or is there a faster way?
2. I am actually trying to revert to stock ROM (downloaded at https://developers.google.com/android/images#angler) by following step 10 of the Heisenburg guide (https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928) which advises me to use fastboot to flash the individual images. In my case, how do I boot to fastboot?
OK, so I managed to boot to the bootloader and run the following commands as per the Heisenberg guide (using the stock MTC20L firmware)
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Everything was successful, and I did a fastboot reboot after that.
However, my device still doesn't boot up. This time. It's boot loops for a few times before turning off.
I tried booting up to bootloader with power/vol-. Curiously, I can now only do this when cable is connected. If cable is disconnected, the orange LED just blinks once when power button is pressed, and nothing happens. Once cable is connected, then I'm able to boot up to bootloader with the button combination. I then retried the flash process again, but still no go. I noticed after fastboot reboot that the orange LED blinked a few times before rebooting and boot looping.
Kinda stuck now, any ideas?
Try booting into recovery and doing a factory reset. I've had that happen to me a few times after flashing factory images and a wipe in recovery always fixed it.
Just for future information: if at any time the device is stuck in a bootloop you can get it to robot into recovery by holding the power and volume down buttons for 10 seconds, or get it to boot into bootloader by holding power and volume up buttons for 10 seconds.
Face_Plant said:
Try booting into recovery and doing a factory reset. I've had that happen to me a few times after flashing factory images and a wipe in recovery always fixed it.
Just for future information: if at any time the device is stuck in a bootloop you can get it to robot into recovery by holding the power and volume down buttons for 10 seconds, or get it to boot into bootloader by holding power and volume up buttons for 10 seconds.
Click to expand...
Click to collapse
Thanks. Booting into stock recovery shows an exclamation sign with "no command", since I don't have TWRP anymore. Would I need to first flash TWRP before I can do a factory reset?
I just tried flashing to the same sock firmware as before the problem happened (7.1.2 N2G47W) but still same problem. I notice that after the Google logo disappears and the screen goes blank, the orange LED blinks 10 times before rebooting.
Edit: Tried factory resetting in stock recovery (by holding down power button and pressing vol+), the rebooting after factory reset. Still getting a boot loop.
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.
goister said:
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.
Click to expand...
Click to collapse
brother help me! i am facing same issue
first little info abt my device.
my device was running on android nougat with twrp recovery installed but the device was not rooted.
so get back to stock and install oreo I followed every step given on http://www.androidexplained.com/nexus-6p-revert-stock/ but somehow my phone is stuck at bootloop with no recovery installed.
Please help me here.
As per the Heisenberg guide, if you don't install root (SuperSU or Magisk), TWRP won't stick, so you'll go back to stock recovery.
For me, simply unplugging the USB cable after rebooting after a flash solved my problem. For some reason, if the cable is connected during reboot, it would boot loop.
brother, somehow I managed to install twrp. but everytime I touch it 2-3 times the phone gets switched off.
then it keeps rebooting to 'Google' logo.
can you tell me what should I do now?
@goister Hi how you manage to get to recovery when it's always stuck at the Google screen with no adb access. Please I am stuck there
tommast said:
@goister Hi how you manage to get to recovery when it's always stuck at the Google screen with no adb access. Please I am stuck there
Click to expand...
Click to collapse
hi, did youmanage to solve this problem? I am aving the exct same problem. Disconnecting the ucb isnt working for me

Advice on getting back into fastboot

OK, so I did something stupid.
I have backups for my device I made by using dd. I decided to try to flash a recovery.img I put together. After flashing it, I erased the cache partition and rebooted it. The issue is, I can't get into fastboot because of it. If I try to access either recovery (holding volume up on boot) or factory mode (holding volume down on boot) it just tries to boot into android. However, android won't boot so it's just stuck on the nook loading logo. As well as that, whenever I hold the power button for a while to power it off, it just reboots. So I need a bit of advice. What should I do from this point? Should I let it die, or should I keep trying to get it to boot into either recovery or factory mode? Maybe I'm not hitting the buttons at the right timing.
Just have to say quickly, I did figure it out. The issue was that I had at some point in that process formatted the cache partition improperly, so Android couldn't boot. The solution was to leave it until it died and plug it in until it was charged up again, and then I was able to get into recovery first try after that (dunno the reasoning behind that, maybe it was continuously trying to reboot because of the fastboot reboot command). In recovery, I tried to reformat cache (which failed) and I turned it off, and then put it back in recovery. That time cache formatted properly and android was able to boot.
Thread closed as user figured it out on their own

Categories

Resources