Booting always to no command screen - Moto G4 Plus Questions & Answers

After every restart, phone boots to recovery mode and it always boots with no command screen. I also tried clean fastboot rom flashing procedure but it still boots to no command screen.
Please guide how do I make phone normally boot to system?
I am on XT1643 Indian.

facing same issue tried a lot of things still no luck
edit:
https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
try this it worked for me.

Related

Not booting into TWRP

Hey everyone,
I decided to root my lg g6 and got a fickle. After unlocking the device and flashing TWRP I tried to boot into it (''adb reboot recovery'' command) and it deleted all data and then twrp shows on screen for a split second and almost instantly boots normally into android so I set it up while still being unable to access twrp and any of it's functions. Does anyone have any idea what could be the problem?
P.S. Of it helps: before that i had a problem that every time I tried to use the ''adb reboot recovery'' command the console said ''no devices/emulators found''. After a couple tries I wanted to check whether the phone was connected just to make sure (''adb devices'') and after that it worked and I ran into the problem above.
Thanks for all the answers
When you first unlock BL and flash recovery you have to manually enter recovery mode.
Hold power and vol down till it turns off. Hold same buttons again until you see lg logo. Release power and press and hold again.
Then ask you to wipe etc hit yes both times and it will boot to twrp.
I tried that but it still doesn't go into twrp. After confirming that wipe stuff it just boots into android (without wiping)
Ulrih said:
I tried that but it still doesn't go into twrp. After confirming that wipe stuff it just boots into android (without wiping)
Click to expand...
Click to collapse
You have to flash TWRP recovery and when it complete then use the button combo to boot into twrp, otherwise it will boot and restore the recovery.
flash twrp
button combo to twrp
done
Yes I've done that but the problem still exist.
btw thanks for the help
Maybe try fastboot flash recovery recovery.img
Try the all-in-one tool on this forum
By the way, I am running into the same issue.. I have a LG G6 US997,.. I have tried installing TWRP unofficial ones so many times and every time i manually try to access the recovery.. the phone simply wipes all my data to default
Hello,
I have the same problem. Did anyone figure out how to solve it? I'd highly appreciate any help.
If I try to boot into recovery, it asks me to factory reset, i hit yes twice and then the phone just goes on to boot normally. The data is not wiped but I can't get into TWRP.
If I enter "fastboot reboot recovery" after flashing TWRP it returns "fastboot: usage: unknown reboot target recovery"

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

Can't flash recovery, boot into recovery or do anything.

Hello!
I just repaired the display of my OP2 and when turning it back on it went straight into bootloop. Only showed the OP Logo and android on the bottom. ADB obviously doesnt work and tried to all partitions via fastboot to get fresh start. After completely resetting I unlocked the bootloader again just to be sure. Then I tried to flash twrp 3.2.1-0. it say dtb not found error. I tried a twrp 3.0.0-0 and it said succesfully flashed but after automatically rebooting the screen just turns black. I can the into fastboot mode or into bootloop can't do anything else. I also tried the MSM8994DownloadTool.exe but it just returns into bootloop again or turns black.
Help pls

MI A1 can't boot in either stock or custom rom

Hi all,
I hope someone can guide me through. My MI A1 device has suddenly stopped booting for no reason. To fix up I tried many thing but with no luck.
here is link to one of the thread I have followed
Reddit thread
This guy exactly had the same issue as mine but on different model and I followed all the instruction as in this thread.
Summary of things I tried so far (Including instructions from the thread I mentioned) :
- Try mi flash tool to flash stock rom (Which succeeds and nothing actually works )
- Tried my luck with lineage os 17 and GPAPPS but no luck. (Interestingly, when I Install LOS and I the reboot device, it boots in LOS recovery fine but when I try to boot system it just keep rebooting and then finally stops at charging screen.)
PS. One more observation, when I flash it with MIflash tool with stock rom and it boots up for the first time, an intermediate screen with circle logo and erasing text appears just like when we get update screen not sure why!
Guys, this is my last bet on XDA. I almost wasted my whole day searching for solution on #Youtube and other forums, nearly read a ton of things but still no luck!
Please Help!
UPDATE :
Here is a little more progress,
So, I tried flashing the original stock rom boot image with fastboot
Code:
fastboot flash boot boot.img
and as usual first it just got rebooted with no luck but later somehow booted the device. I tried the same with recursion OS ROM and then again flashed boot image and just like prev attempt it rebooted first & then booted normally.
Also, when device was booted normally, I received a call and when I tried to pick it, It just got rebooted and I am where I started!
I really don't get the point why it boot when I manually boot it with fastboot and its not able to boot itself.
Anyone knows, why this is happening? Is there a way to clean whole and then install? am I doing something wrong here?
Update :
Yes, confirmed when I flash the boot image from fastboot it does boots up. the only problem is after a few seconds/minutes it just reboot and goes back to problematic state.
This thing is really pissing me off! Can someone help?
Update:
After a few more attempts now, it seems like the device is completely broken! It only boots up in fastboot and does not even boot in recovery ( Volume up + Power)
I also tried with pushing twrp recovery image with fastboot but even though the command succeeds the device just reboots with MI logo continuously.

asus zenfone max m1 recovery, rom not working. help

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?

Categories

Resources