Recovery flashing issue - Moto G7 Power Questions & Answers

I am trying to install lineageos to my moto g7 power 2021.
I have followed all the instructions here https://wiki.lineageos.org/devices/ocean/install up until
Now reboot into recovery to verify the installation.
Use the menu to navigate to and to select the Recovery option.
under Booting a customer recovery using fastboot.
When I select recovery mode I get an android on its back with an open chest door with a red triangle with an exclamation point. Under that it says "no command."
Does anyone know what's going on and how I can if it?
If it helps, this is the result in got when flashing the recovery:
Sending 'boot_b' (25028 KB) OKAY [ 0.805s]
Writing 'boot_b' OKAY [ 0.109s]
Finished. Total time: 0.961s
I did this a few times and at one point it flashed to boot_a for as well.

Related

unlock before install recovery?

i rooted my tf300 when on stock ics. i used the method that doesnt require bootloader unlocking.
couple of days later the jb ota came along, so installed that, and restored root with voodoo
i want to install a custom rom, but i can't get the recovery working. the tablet boots fine, and the behaviour is the same now im on jb, as it was when on ics
basically, i power on + vol down, then select the rck icon, and it loads to an android with a blue loading animation, then changes to a 'dead' android with a red exclamation just above.
the tablet still boots fine otherwise.
question is, do i have to unlock the bootloader before i can install/run the recovery, or is there a way i can do it without unlocking?
edit: i tried also flashing via fastboot (tried first with terminal, when trying twrp for ics) and this is what it comes back with, same thing for cwm and twrp:
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery CWM-Touch.blob
sending 'recovery' (6370 KB)...
OKAY [ 2.646s]
writing 'recovery'...
FAILED (remote: (InvalidState))
finished. total time: 5.901s
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (7304 KB)...
OKAY [ 3.538s]
writing 'recovery'...
FAILED (remote: (InvalidState))
finished. total time: 6.779s
You have to unlock to install a custom rom. Think it over and do some more reading. You could build a house since there is no shortage of bricks. :banghead:
Still Charged Up
do you think there's any chance of being able to do this without unlocking in the future?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Nope. One requires the other. Simply put - ASUS does not want to deal with true user-created bricks. That's why they make it optional.
Still Charged Up

Unable to flash recovery through fastboot

Hi,
I am trying to install cwm recovery through fastboot but consistently this error arising.
<bootloader> Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' <8480 KB>...
OKAY [ 0.700s]
writing 'recovery'...
OKAY [ 2.219s]
finished. total time: 2.929s
after this when I go to recovery the screen remains black.
can anybody please help me regarding this issue that how could I flash custom recovery through fastboot.
Thanx.
This is normal (sort of) for KKBL recoveries -- it's a screen dimming issue; if you're using PhilZ the "fix" is to use the following:
- middle of screen; swipe left-to-right twice
- middle of screen; swipe right-to-left twice
- push a volume up or down button
Screen should come alive.
This affected TWRP too but I don't use it so not sure if there's a similar workaround.
I am not using Philz, using CWM Recovery 6.0.4.9.

[Q] boot to black screen, can not get into recovery

I just flash a rom(white-heat 5.0.1) onto my phone (nexus 5 rooted, bought from google) and after t was done booting all i have is a black screen with the clock and signal at the top right and a arrow at the bottom left, i can not get into phone to try to fix. so i tried to boot into recovery and see if i could just try it again but when the twrp logo comes up i wait to get into recoovery but it passes by and then boots regular and back to black screen from before.
adb and fast boot are not seeing phone on linux or mac
there must be something i can do,, when the phone boots to black screen when i press the power button i can see home screen for second then black i could hear emails coming in to phone but is all i can do...
You can't boot into recovery because you have TWRP 2.8.2.0 with SMTP enabled.most likely. Flash back to previous version
gordonrjones said:
I just flash a rom(white-heat 5.0.1) onto my phone (nexus 5 rooted, bought from google) and after t was done booting all i have is a black screen with the clock and signal at the top right and a arrow at the bottom left, i can not get into phone to try to fix. so i tried to boot into recovery and see if i could just try it again but when the twrp logo comes up i wait to get into recoovery but it passes by and then boots regular and back to black screen from before.
adb and fast boot are not seeing phone on linux or mac
there must be something i can do,, when the phone boots to black screen when i press the power button i can see home screen for second then black i could hear emails coming in to phone but is all i can do...
Click to expand...
Click to collapse
Try getting into the bootloader and look if the device is detected, if so relash a factory image and start over. At least that what i would do.
need to get into phone to do anything
rootSU said:
You can't boot into recovery because you have TWRP 2.8.2.0 with SMTP enabled.most likely. Flash back to previous version
Click to expand...
Click to collapse
i can not get into my phone to do anything like flashing or settings or recovery, I am not sure if smtp is enabled in TWRP or what version for sure but the last time i was looking at it it has 2.7.? installed
thanks
yes
gee2012 said:
Try getting into the bootloader and look if the device is detected, if so relash a factory image and start over. At least that what i would do.
Click to expand...
Click to collapse
I can get into bootloader but not into recovery, it just shows TWRP for maybe five seconds then continues to regular boot
gordonrjones said:
i can not get into my phone to do anything like flashing or settings or recovery, I am not sure if smtp is enabled in TWRP or what version for sure but the last time i was looking at it it has 2.7.? installed
thanks
Click to expand...
Click to collapse
So you can`t power down the phone and get into bootloader by pressing volume up and down and the power button?
yes
gee2012 said:
So you can`t power down the phone and get into bootloader by pressing volume up and down and the power button?
Click to expand...
Click to collapse
I can power down the phone and get into bootloader, but when i pick recovery it does not go there it starts to but the just continues to boot into black screen, thanks
gordonrjones said:
I can power down the phone and get into bootloader, but when i pick recovery it does not go there it starts to but the just continues to boot into black screen, thanks
Click to expand...
Click to collapse
If you are in bootloader mode connect the phone to the pc and see if it is connected and detected. If so flash a factory image and you`re phone is running again.
gordonrjones said:
i can not get into my phone to do anything like flashing or settings or recovery, I am not sure if smtp is enabled in TWRP or what version for sure but the last time i was looking at it it has 2.7.? installed
thanks
Click to expand...
Click to collapse
You don't need to. Use fastboot.
been trying
rootSU said:
You don't need to. Use fastboot.
Click to expand...
Click to collapse
fastboot has been showing no devices but it just showed me one i am waiting for the thing to stop and boot and see if i still have black screen, if all is good ...
Thanks to you all for your words of wisdom on this Miserable(here) Friday night, cold and wet,... will keep my fingers crossed till then thanks again
hmmmmmm
Still booting 6:45pm:
:hammerhead gordonrjones$ sh flash-all.sh
sending 'bootloader' (2579 KB)...
OKAY [ 0.198s]
writing 'bootloader'...
OKAY [ 0.514s]
finished. total time: 0.712s
rebooting into bootloader...
OKAY [ 0.091s]
finished. total time: 0.091s
sending 'radio' (45521 KB)...
OKAY [ 1.624s]
writing 'radio'...
OKAY [ 3.124s]
finished. total time: 4.749s
rebooting into bootloader...
OKAY [ 0.085s]
finished. total time: 0.085s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12d
Baseband Version.....: M8974A-2.0.50.2.22
Serial Number........: 03bcc840437d66db
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8852 KB)...
OKAY [ 0.520s]
writing 'boot'...
OKAY [ 0.765s]
sending 'recovery' (9552 KB)...
OKAY [ 0.546s]
writing 'recovery'...
OKAY [ 0.802s]
sending 'system' (981472 KB)...
OKAY [ 30.972s]
writing 'system'...
OKAY [ 65.984s]
erasing 'userdata'...
OKAY [ 9.308s]
erasing 'cache'...
OKAY [ 0.570s]
rebooting...
finished. total time: 110.169s

bricked due to S3 vs. S4 CPU mixup?

I have an old HTC ONE S (z560e => S3 CPU as I now know).
1) I managed to unlock the boot loader (htcdev)
2) Probably managed to get root access (r3-ville-superboot was fast and error free)
3) However them "recovery install apps" (CWM, TWRP) still clamied they'd need root
access but "superuser or su are not to be found"; weird, considering success of 2)
4) hence I tried to flash twrp recovery manually via
Code:
fastboot.exe flash recovery twrp-3.0.0-0-ville.img
message was
Code:
sending 'recovery' (11896 KB)...
OKAY [ 2.078s]
writing 'recovery'...
OKAY [ 3.845s]
finished. total time: 5.931s
And that's it. won't boot anymore. I apparently got the S4 version of twrp-3.0...
Holding in power button for ~10 secs has it very shortly flash the screen and turn on the oragne LED for ~4 secs, then it's black again.
Any idea what went wrong?
Any chance how to save that situation?

Fastboot mode freezing

Hi. I was following the instruction<oneplusDOTgadgethacksDOTcom/how-to/update-your-oneplus-7-pro-without-losing-root-no-computer-needed-0208078> to upgrade the os on the pro. One step is to install TWRP. I followed the instruction<twrpDOTme/oneplus/oneplus7proDOThtml> and run "fastboot boot twrp-xxxx.img". It finished and my phone displayed "fastboot mode" and freezed there. I tried to hold the power button and hold power button & volume down button. Neither worked. Aappreciate any help.
I only have a macbook pro.
Log:
> fastboot boot twrp-xxxx.img
< waiting for any device >
Sending 'boot.img' (31704 KB) OKAY [ 0.682s]
Booting OKAY [ 0.121s]
Finished. Total time: 0.868s
screenshot: i.ibb.co/pRtwJ4L/IMG-1533.jpg
buy pc
other solution is maybe to use usb2.
superflb said:
Hi. I was following the instruction<oneplusDOTgadgethacksDOTcom/how-to/update-your-oneplus-7-pro-without-losing-root-no-computer-needed-0208078> to upgrade the os on the pro. One step is to install TWRP. I followed the instruction<twrpDOTme/oneplus/oneplus7proDOThtml> and run "fastboot boot twrp-xxxx.img". It finished and my phone displayed "fastboot mode" and freezed there. I tried to hold the power button and hold power button & volume down button. Neither worked. Aappreciate any help.
I only have a macbook pro.
Log:
> fastboot boot twrp-xxxx.img
< waiting for any device >
Sending 'boot.img' (31704 KB) OKAY [ 0.682s]
Booting OKAY [ 0.121s]
Finished. Total time: 0.868s
screenshot: i.ibb.co/pRtwJ4L/IMG-1533.jpg
Click to expand...
Click to collapse
You can upgrade the is without twrp,just go for local upgrade in updater app.
Also the terminal should show downloading boot.img message which is not shown in your case and it is evident that something is wrong.
Mess around a bit and you will figure it out

Categories

Resources