Moto X 1095 with 24.11.18 6.0 update doesn't boot into recovery. Everytime I try to fastboot flash a recovery, it prompts a mismatched partition.
If I try to reboot into recovery, it will give me a blank, black screen.
Any advice would be appreciated.. I am not sure what to do. No one has a solution to this. I've tried to look for a factory recovery.img but no where to be found.
Can I downgrade to 5.1 using the Motorola Factory Image ? If so, how?
I have a similar problem
Does the black screen have the Android robot with an exclamation mark in it? If so, that's the stock Recovery. Press Power + Vol Up, and you should be able to access it.
When flashing a custom Recovery, make sure that after issuing "fastboot reboot" you don't let the phone boot into system, otherwise you'll end up with the stock Recovery again. After the reboot, you should access the bootloader again and enter Recovery for the custom Recovery to take place.
Related
I have a rooted and unlocked bootloader nexus one. I previously had cm7 on it but decided to flash an ics rom without having the blackrose hboot. I need help to get into recovery as I can get to the point where to select recovery I need the power button. Is there another way of getting into recovery thru fastboot or something?
Sent from my SPH-D700 using XDA App
try
Code:
fastboot boot recovery.img
Adb reboot recovery. Adb should work within 10 seconds of booting. I had a problem once that wouldn't even get past the X to the boot animation.
You can also install blackrose which enables you to press the trackball instead of the power button.
I think you need to be able to boot normally to install blackrose.
But if you have a broken power button, get blackrose and 4ext touch recovery on your phone as soon as you can boot normally.
If you're not getting far enough into the boot for ADB to work and can't do the fastboot stuff because you never unlocked the bootloader (and don't want to), you can toss a passimg on your sd card to go back to stock. Then you can reroot.
I can't get into adb, but my bootloader is unlocked. Is there any way of getting into recovery without having to reroot.
Take a look here
http://forum.xda-developers.com/wiki/HTC_Nexus_One/Recovery_Images
Thanks for the link, it somewhat helped but I was able to get it to work with lots of flashing via fast boot and whatnot
I had the same problem. I flashed back to stock. Flashed the userdata, system image, recovery image, boot image, and radio.
Trying to update GPE to the latest OTA 5.1.
Unfortunately when I enter stock recovery to flash the OTA I am greeted with "no command" underneath a green robot.
I power down, hold volume down when restarting, into bootloader, select recovery and it loads the above.
Any ideas?
Thanks.
I have tried the methods described online, hold volume up and pressing the power button but the no command/robot remains on the recovery screen. I am running a newly flash GPE 5.0.1 stock image.
Anyone have any idea or seen this before. I can get to the bootloader menu and can select recovery, it then boots to a robot and "no command" message.
I have tried holding up volume and pressing power as suggested on other sites, this does nothing. If I keep pressing power the phone just ends up rebooting.
No matter what I do I can enter the recovery menu.
Frsutrating as I wanted to flash an OTA.
Ps. Is this because I am s-off and/or have an unlocked bootloader?
maritimesbob said:
Anyone have any idea or seen this before. I can get to the bootloader menu and can select recovery, it then boots to a robot and "no command" message.
I have tried holding up volume and pressing power as suggested on other sites, this does nothing. If I keep pressing power the phone just ends up rebooting.
No matter what I do I can enter the recovery menu.
Frsutrating as I wanted to flash an OTA.
Click to expand...
Click to collapse
Re-install stock recovery, firmware or RUU then try the OTA update.
@maritimesbob Reflash the right stock recovery from fastboot
Ok, here's where I am at.
I flashed GPE stock 5.0.1 using the conversion method
http://forum.xda-developers.com/showthread.php?t=2358781
As my phone was originally sense based. As this is a stock rom, with stock recovery I thought I should be ok, as it flashes recovery, radio, firmware, system etc,
When accessing recovery I get the robot and no command.
I managed to find a copy of the 5.0.1 gpe stock recovery, and tried flashing that, I appears to have got a little further, now I have the robot with an exclamation mark.
No matter what method of keys, volume up and whatever, I cannot get into recovery to flash an OTA. I was hoping to upgrade to 5.1
Would an unlocked bootloader and being s-off cause recovery to be locked out, if indeed it is locked out?
I have the "no command" screen with the android man , however it flashes in and out. when i hold down the power button and go into ap fastboot mode, i cannot go into recovery (it just shutdown the phone) and factory reset does not work. My phone is a non dev version, is there anything i can do?
Hoping I can get some help with the same issue.
I sent my 6P back in for a warranty repaid so I'm using this phone (XT1095) for now. I'd like to put LineageOS on it and root with Magisk BUT I'm having a ridiculous time getting TWRP to flash.
I certainly know how to flash images via fastboot and have done it for years but this is seriously pissing me off lol.
I got the code from Moto and unlocked the bootloader. I tried a simple "fastboot flash recovery _____.img", I've tried "fastboot boot _____.img".
At first, I was booting back into the system first but now I've tried it both ways. Regardless of what I do, after flashing the recovery, it boots into the system. The ONLY I can get this thing into recovery is if I boot into the system and just use "adb reboot recovery" but it's obviously the stock recovery because the phone keeps overwriting TWRP upon boot.
Just so we're clear:
1. Reboot into bootloader
2. Confirm bootloader unlocked
3. Fastboot flash recovery _____.img
4. Volume button to boot into recovery
Result = Boots into system
1. Reboot into bootloader
2. Confirm bootloader unlocked
3. Fastboot flash recovery _____.img
4. Fastboot reboot bootloader
5. Bootloader reboots
6. Volume button to boot into recovery
Result = Boots into system
1. Fastboot boot _____.img
Result = Boots into system
If it helps at all, upon flashing recovery I get this message 100% of the time "mismatched partition size", similar to the case on this thread: https://goo.gl/6Nm9cu
By dumb luck I found where someone used the "fastboot boot ____.img" with a pretty old version and it worked just fine. I'll root and such with that and upgrade the recovery later.
jonzey231 said:
Just so we're clear:
1. Reboot into bootloader
2. Confirm bootloader unlocked
3. Fastboot flash recovery _____.img
4. Volume button to boot into recovery
Result = Boots into system
Click to expand...
Click to collapse
For clarification of step 4. I think recovery is the second or third option in bootloader. You are hitting volume down twice and then volume up correct
Volume up selects.
The mismatched partition size doesn't matter everyone gets that error.
Visi0nofExcellence2 said:
For clarification of step 4. I think recovery is the second or third option in bootloader. You are hitting volume down twice and then volume up correct
Volume up selects.
The mismatched partition size doesn't matter everyone gets that error.
Click to expand...
Click to collapse
You know what, I am so used to newer devices like N6 and 6P that I completely overlooked that the Volume Up button was the selector instead of the power button. It was rebooting into the system EVERY TIME because I was hitting the power button. Recovery installed successfully and running LineageOS with Magisk with Android Pay and Direct TV Now working just fine.
Thanks for your help and I'll be sure to actually READ from now on :laugh::laugh:
I need help. I deleted/wiped in advanced mode in twrp the system and now I have No OS installed. I don't kow what to do now the phone does not bood except into twrp.
Use NOST
Sent from my NB1 using XDA Labs
After hours of "work" I have my phone running again. I was able to get the phone run stock recovery again and then was easy to just flash the oreo zip.
well good to know you solved the problem.
but just in case keep your phone bootloader critical unlocked so you can use NOST if you face such problems again.
Just happened again. I wanted to put twrp img back on the phone and as it reboots... its stuck on "Powered by Android". I cannot flash or do anything since its stuck and does not turn off. I tried all combinations of volume/power button and hold them for minutes... just does not turn off. So its not recognized by NOST or anything. Now I am really screwed as it seems...
theviking33 said:
Just happened again. I wanted to put twrp img back on the phone and as it reboots... its stuck on "Powered by Android". I cannot flash or do anything since its stuck and does not turn off. I tried all combinations of volume/power button and hold them for minutes... just does not turn off. So its not recognized by NOST or anything. Now I am really screwed as it seems...
Click to expand...
Click to collapse
I am at such condition too... how long battery lasts? I think it's possible to wait for the phone to fully discharge and then we may have access to recovery. right?
theviking33 said:
Just happened again. I wanted to put twrp img back on the phone and as it reboots... its stuck on "Powered by Android". I cannot flash or do anything since its stuck and does not turn off. I tried all combinations of volume/power button and hold them for minutes... just does not turn off. So its not recognized by NOST or anything. Now I am really screwed as it seems...
Click to expand...
Click to collapse
If you tried to "fastboot boot" the TWRP image: thats "normal", fastboot boot is broken on every firmware since august. You have to flash TWRP to your active boot partition to boot it. However, at least for me, when being stuck in that screen I can still use "fastboot reboot" or "fastboot reboot-bootloader" to get the phone back in a working state.
Also, if you try to flash TWRP to your active boot: Please don't flash the image from the official site, since that is unable to boot into the system normally. Use my recompiled generic TWRP boot image that you can flash, regardless of security patch version: https://forum.xda-developers.com/nokia-8/development/twrp-data-decryption-android-9-t3911411
If you did not fastboot boot an image: Hold down volume up, volume down and power for multiple minutes until the phone turns off. Then hold volume down while connecting the phone to a computer through USB, and it will start into fastboot mode. Then just revert whatever you changed and reflash the stock image.
THMSP said:
If you tried to "fastboot boot" the TWRP image: thats "normal", fastboot boot is broken on every firmware since august. You have to flash TWRP to your active boot partition to boot it. However, at least for me, when being stuck in that screen I can still use "fastboot reboot" or "fastboot reboot-bootloader" to get the phone back in a working state.
Also, if you try to flash TWRP to your active boot: Please don't flash the image from the official site, since that is unable to boot into the system normally. Use my recompiled generic TWRP boot image that you can flash, regardless of security patch version: https://forum.xda-developers.com/nokia-8/development/twrp-data-decryption-android-9-t3911411
If you did not fastboot boot an image: Hold down volume up, volume down and power for multiple minutes until the phone turns off. Then hold volume down while connecting the phone to a computer through USB, and it will start into fastboot mode. Then just revert whatever you changed and reflash the stock image.
Click to expand...
Click to collapse
It turns out that there was Pie on my partition B and I was not aware of that. Booting into TWRP wasn't working, so I flashed it and then factory reset system. And it broke the phone.
Now I tried to boot the TWRP from slot B and rebooted partition A. Now the phone is up... Thanks
Where can I find the appropriate stock boot image for my partition B? and should I fastboot it with boot_b command or what?