I was on 4.4.4 stock with bootloader unlocked. I flashed custom recovery from fastboot and rebooted into CWM. It was all fine till this point. On next reboot, It booted in OS all fine. I did adb reboot recovery and it got stuck at "No command" screen. waiting a long time ons creen it booted into OS.
I reboot into fastboot to reflash CWM and check but it wont detect my device in fastboot devices. I'm on OS x. I even tried windows (drivers installed) , its the same. fastboot is stuck at "waiting for device".
ps. I installed "recovery-clockwork-touch-6.0.1.6-manta-Wfix-by-damien667.img" from downloadandroidrom.com
Have you tried turning off the tablet, then booting by simultaneously holding the power, volume up and volume down buttons? This is the manual way to boot into CWM. After you are in cwm you should be able to reflash or just reboot into the OS.
uDude
The stock-Recovery is reflashed when you reboot to Stock OS, you have to disable that.
I rooted and changed kernel on my P9 lite single sim in order to use OTG, but then went back to full stock for OTA update.
Phone downloaded it but when it reboot to install, instead of booting recovery mode started a boot screen loop.
At this point, I can just let it go out of battery and then reboot in normal mode.
FASTBOOT DOESN'T WORK, as well. Both fastboot and recovery mode are broken. Both came up in a boot screen loop.
How can I solve this?
Thx.
The problem is, if I try to update with OTA, that the phone enter in a boot screen loop. Until the battery is down.
No recovery, nor bootloader.
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
Hi,
I have been using my P Smart (FIG-LX1) for a while with LineageOS 16 and decided to move on to Android 10. Installed LineageOS 17.1 (found it on this forum) and pph-Magisk 20.3 for root - it did work, but the system was unstable so i decided to try AOSP 10.0 instead. I entered TWRP, wiped cache,dalvik,system and data, flashed the ROM, gapps etc. It was advised to now flash stock recovery and use it to do a factory reset - and now i'm stuck here.
After flashing the recovery_ramdisk img the phone stopped being able to enter any recovery at all. The system itself does not boot (stuck on the "Your device has been unlocked (...) Your device is booting now..." screen forever), the recovery never appears (previously in the start screen with 'unlocked device' warning it used to suggest pressing volume UP to enter recovery, now it only shows "Your device is booting now"). As i can still access fastboot, I tried flashing TWRP again - the TWRP splash screen does appear, but the phone gets stuck on it. Also tried flashing another system's img - nothing changed.
Is there anything I can do or did i just brick it completely?
Thanks for help!
SOLVED:
Apparently running fastboot erase on system and userdata partitions made me able to boot into recovery/erecovery again. I do have another problem now, but it's not connected with this one so I will create another thread for that.
Could you try help me? I can't even get ADB to work anymore
Please HELP
I am writing here the whole story.
I unlocked the bootloader of my Asus zenfone max m1 (3/32GB) using the unlock tool which I downloaded from Asus's website.
Then, I went to fastboot mode and flashed TWRP recovery and then tried booting into it through the cmd screen using fastboot boot twrp.img command and it worked.
Then I followed a really good tutorial and flashed the pie firmware, Pixel Experience and magisk and ZIPs in order.
And it showed no error, everything was fine and then I clicked on the reboot system button, it rebooted the system but the phone was stuck at the google logo with a loading bar and didn't go beyond that even when left for 30 mins and I tried rebooting the phone multiple times and that did not help. the phone was stuck at the google logo every time.
Then I turned off the phone and tried going to TWRP to flash the pixel rom again but the phone only went into fastboot mode, it never booted into recovery even though I tried multiple times(I was trying to boot into the recovery through the volume and power buttons, not through fastboot mode).
I flashed the phone's recovery multiple times and also the boot image (I even tried flashing the stock recovery) but the problem is that everything goes fine in the terminal, it shows that it flashed the img file successfully and it is finished but the commands like fastboot reboot recovery don't work at all, they all just reboot the phone normally and the phone just shows the ASUS logo for few secs and then turns off.
Note: I used fastboot erase commands to remove the pixel experience rom and now I'm only left with a phone which boots only into fastboot with no rom and I don't know about the recovery because it shows that it flashed but it never opens.
Hi
I am having a similar problem in that I can oly get into recovery mode with adb reboot recovery. I researched and tried all possibilities with the phone key but I can only go into bootloader mode.
After flashing recovery successfully (?) I can only boot the phone normally and that seems to reinstall the default recovery manager.
While researching I found that there are some discrepancies with the ID out there. While my phone is a Zenfone Max (M1) with the ID X00PD some places (TWRP) confirm that but others refer to Z555KL.
Did you get any further?