TWRP remote image verification failed - Pixel C Q&A, Help & Troubleshooting

PRODUCT NAME: GOOGLE Smaug
HW VERSION: 5
BOOTLOADER VERSION: Google_Snaug.7900.139.0
LOCK STATE: Unlocked
Hello. After doing the wipe of System, Data , Cache and Davlik..., I tried to install another PixelExperience ROM and it has given me an error of format as soon as start the installation on the TWRP and when the tablet restarting again at FastBoot I try to enter in TWRP again but give me the following error.
C:\ADB>fastboot boot twrp.img
creating boot image...
creating boot image - 16893952 bytes
Sending 'boot.img' (16498 KB) OKAY [ 0.419s]
Booting FAILED (remote: 'image verification failed')
fastboot: error: Command failed
So I can not enter the TWRP to install another ROM and the previous one does not boot, so when the tablet boot in normal mode, return again to wait for a FastBoot command.
Can you please help me?. I do not know what else to do
Thank you

Nobody can helpme with this error please?
I need to use TWRP again.

Related

Help - I've stuffed my Pixel C up and cant get beyond recovery

Hi everyone,
I was in the process of unlocking my bootloader, flashing a recovery and rooting my Pixel C with the Skipsoft Toolkit when something went wrong.
The bootloader unlocked (30 sec screen and chirp) and I flashed TWRP but it got stuck there.
TWRP kept asking for the password to decrypt data, and now everytime I start my Pixel C it goes straight there again.
I've tried different options in the Skipsoft Toolkit but nothing seems to work and goes back to the 'Mount Decrypt Data' TWRP screen.
A few things that Ive tried are listed below.
Any help with me getting back to stock and having the Pixel C working again would be greatly appreciated.
Thankyou
4. Root/UnRoot/Disable Encryption/Flash Stock Boot/Check Root Status [ADB Mode]
7. Unroot, Uninstall Busybox and Restore Stock Boot/Recovery [ADB Mode]
1. Push file, reboot to Custom Recovery and install manually [simplest method]
Working out the best location to set for Internal Storage..
Waiting for Adb Mode ...
Device mode detected [recovery adb]
Android Version Detected: 7.1.2 Serial Number:
Pushing Unroot-SuperSU.zip to: /sdcard/
root\Unroot-SuperSU.zip: 1 file pushed. 0.1 MB/s (3574 bytes in 0.064s)
File/s pushed successfully
Device mode detected [recovery adb]
Device Serial Number:
Rebooting to Fastboot Mode and continuing..
Device mode detected: Fastboot Mode
Device Serial Number:
Device Bootloader State: Locked
Booting TWRP recovery-twrp-3.1.1.1-ryu.img ..
creating boot image...
creating boot image - 13051904 bytes
downloading 'boot.img'...
OKAY [ 0.323s]
booting...
FAILED (remote: image verification failed)
finished. total time: 0.328s
An Error Occured
Press any key to return to the Main Menu..
5. Rename Recovery Restore Files [Fix system flashing stock recovery on boot]
Device Bootloader State: Locked
Booting TWRP recovery-twrp-3.1.1.1-ryu.img ..
creating boot image...
creating boot image - 13051904 bytes
downloading 'boot.img'...
OKAY [ 0.331s]
booting...
FAILED (remote: image verification failed)
finished. total time: 0.331s
An Error Occured
Press any key to return to the Main Menu..
9. Download/Extract/Flash Google Factory Stock Image [Flash Part or Whole Rom]
2. Flash Google Stock Image [in the put_google_factory_image_here\device folder]
image-ryu-opm1.171019.015.zip
ryu-opm1.171019.015-factory-64c65be2.zip
Are you ready to proceed? Type y[yes] or n[no]:
Google Stock Image found [.zip format] in the correct folder.
Filename of image to flash: ryu-opm1.171019.015-factory-64c65be2.zip
Processing archive: put_google_factory_image_here\GooglePixelC\image-ryu-opm1.171019.015.zip
Extracting android-info.txt
Extracting boot.img
Extracting cache.img
Extracting recovery.img
Extracting system.img
Extracting vendor.img
Everything is Ok
Starting Flash Process..
Flashing Bootloader Image..
target reported max download size of 268435456 bytes
sending 'bootloader' (16384 KB)...
OKAY [ 0.416s]
writing 'bootloader'...
FAILED (remote: unsupported command)
finished. total time: 0.431s
An error occured when flashing the image
Try rebooting the device manually back to fastboot mode:
1. Unplug the usb cable
2. Stand the tablet in landscape mode [power button on top] and Press and Hold the
Power and Volume Down buttons for 10-15 seconds until it reboots to Bootloader
mode. Then select 'Switch to fastboot mode' using the volume button and press
the power button. The device will say 'Waiting for fastboot command...'
From the main menu in the Toolkit choose the Download/Extract/Flash menu, then
select Flash previously downloaded image.
Sometimes there is a glitch in the flash process and doing it again will fix it.
You can skip the password and change data file system partition to ext3. Then install custom systems like lineage os.
rhmanoa said:
You can skip the password and change data file system partition to ext3. Then install custom systems like lineage os.
Click to expand...
Click to collapse
Hi and thanks for the response.
How do I change data file system partition to ext3?
I can skip the decrypt password screen in TWRP and go into the general settings, but I dont know how to convert the system partition to ext3.
Thanks
Go to wipe data/cache then advanced wipe then change partition setting select data partition change to ext3.

Unable to flash TWRP after flashing factory image (Not allowed to flash (recovery))

I wiped my device and flashed the latest factory image. I am now trying to install TWRP but fastboot returns the following:
Code:
./fastboot flash recovery ./twrp.img
Sending 'recovery' (65536 KB) OKAY [ 1.860s]
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
The bootloader is unlocked, and I have tried relocking and unlocking it to no effect.
pismosi said:
I wiped my device and flashed the latest factory image. I am now trying to install TWRP but fastboot returns the following:
Code:
./fastboot flash recovery ./twrp.img
Sending 'recovery' (65536 KB) OKAY [ 1.860s]
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
The bootloader is unlocked, and I have tried relocking and unlocking it to no effect.
Click to expand...
Click to collapse
twrp doesn't work for android 10. please be specific about versions of android and twrp you are using
pismosi said:
I wiped my device and flashed the latest factory image. I am now trying to install TWRP but fastboot returns the following:
Code:
./fastboot flash recovery ./twrp.img
Sending 'recovery' (65536 KB) OKAY [ 1.860s]
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
The bootloader is unlocked, and I have tried relocking and unlocking it to no effect.
Click to expand...
Click to collapse
As already noted, TWRP has never worked with 10. If you are on 9 then head over to the dedicated TWRP thread and get yourself up to speed.
if on android 9 it would be fastboot boot twrp. img. (if on Pie)
A/B slot devices don't have a dedicated recovery partition. (reason why flashing to recovery didn't work)
Android 10 doesn't have working TWRP yet. ( can't decrypt data or something)

Rooting Motorola One Action w/ Android 10

I have Motorola One Action w/ Android 10 running. I need to root this phone to recover the data. However, when following the instruction, I received the following error message.
C:\adb>fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
downloading 'boot.img'...
OKAY [ 1.118s]
booting...
FAILED (remote failure)
finished. total time: 1.305s
Can anyone help me what to do?
Thank you very much for your help.
[email protected] said:
I have Motorola One Action w/ Android 10 running. I need to root this phone to recover the data. However, when following the instruction, I received the following error message.
C:\adb>fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
downloading 'boot.img'...
OKAY [ 1.118s]
booting...
FAILED (remote failure)
finished. total time: 1.305s
Can anyone help me what to do?
Thank you very much for your help.
Click to expand...
Click to collapse
Hi!!
I have a model XT2013-1. I was having the same problem as you, so I updated TROIKA-RETBR on 02/22/2020.
After updating, I did the procedure of this link "https://forum.xda-developers.com/one-action/how-to/twrp-magisk-root-motorola-one-action-t3975883", skipping the step "8.2- Now tap on Wipe> Format Data> Type Yes and go back to the home screen again. " This step gave me the looping error.
Now root works perfect !!
Thank you very much. I will try it.
BL1ND4D0 said:
Hi!!
I have a model XT2013-1. I was having the same problem as you, so I updated TROIKA-RETBR on 02/22/2020.
After updating, I did the procedure of this link "https://forum.xda-developers.com/one-action/how-to/twrp-magisk-root-motorola-one-action-t3975883", skipping the step "8.2- Now tap on Wipe> Format Data> Type Yes and go back to the home screen again. " This step gave me the looping error.
Now root works perfect !!
Click to expand...
Click to collapse
I am still getting the following error message. I have no idea why. Would you please help me what to do? Thank you very much.
fastboot flash recovery twrp.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (37524 KB) OKAY [ 1.209s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
[email protected] said:
I am still getting the following error message. I have no idea why. Would you please help me what to do? Thank you very much.
fastboot flash recovery twrp.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (37524 KB) OKAY [ 1.209s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
It's A/B device so it doesn't have dedicated recovery partition. It's inside boot.img.
Use fastboot boot twrp.img
Once booted to twrp, you can use the twrp installer zip to flash twrp recovery ramdisk to your boot.img for permanent installation.
tys0n said:
It's A/B device so it doesn't have dedicated recovery partition. It's inside boot.img.
Use fastboot boot twrp.img
Once booted to twrp, you can use the twrp installer zip to flash twrp recovery ramdisk to your boot.img for permanent installation.
Click to expand...
Click to collapse
Thank you very much for your help. I tried but I was still getting the following error message.
fastboot boot twrp.img
Sending 'boot.img' (37524 KB) OKAY [ 0.990s]
Booting FAILED (remote: '')
fastboot: error: Command failed
Would you tell me what to do?
[email protected] said:
Thank you very much for your help. I tried but I was still getting the following error message.
fastboot boot twrp.img
Sending 'boot.img' (37524 KB) OKAY [ 0.990s]
Booting FAILED (remote: '')
fastboot: error: Command failed
Would you tell me what to do?
Click to expand...
Click to collapse
Did you follow all instructions from twrp thread. like flashing modified vbmeta and wipe data before booting twrp?
Also take a look at the original thread for one vision as it has a newer zip that contains only one modified vbmeta.img instead of two different ones in the older zip that is posted in one action's twrp thread.
I rooted using fastboot, I could never get into TWRP to flash anything.
In fastboot, I flashed the modified vbmeta.img, then flashed the magisk patched boot img file (I created this with magisk), then flashed the patched vbmeta.img file, then did a fastboot wipe.
Rebooted, set up the phone, installed magisk manager and opened, it needed to update some files. Rebooted, and the device was rooted.
goofball2k said:
I rooted using fastboot, I could never get into TWRP to flash anything.
In fastboot, I flashed the modified vbmeta.img, then flashed the magisk patched boot img file (I created this with magisk), then flashed the patched vbmeta.img file, then did a fastboot wipe.
Rebooted, set up the phone, installed magisk manager and opened, it needed to update some files. Rebooted, and the device was rooted.
Click to expand...
Click to collapse
Thank you very much for your input. You must be an expert! WOW! Sorry I am not that expert........ Would you mind explaining (1) how to modify vbmeta.img and (2) how to patch boot.img? It is very impressive to read what you have done, but sorry I am still a beginner. Also, when I flash, "fastboot flash (File Name)" ok?
Thank yuo very much for your help.
[email protected] said:
Thank you very much for your input. You must be an expert! WOW! Sorry I am not that expert........ Would you mind explaining (1) how to modify vbmeta.img and (2) how to patch boot.img? It is very impressive to read what you have done, but sorry I am still a beginner. Also, when I flash, "fastboot flash (File Name)" ok?
Thank yuo very much for your help.
Click to expand...
Click to collapse
You don't need to modify vbmeta.img. I am using the older version of the root Moto Vision package, which has a vbmeta.img file, and a patched vbmeta.img file.
For the modified boot img, I downloaded the full image from https://mirrors.lolinet.com/firmware/moto/troika/official/
Extract, and then take the boot.img file, you will want that saved to a phone that has Magisk installed.
Follow these instructions to patch
https://www.ytechb.com/how-to-patch-a-file-in-magisk-manager/
Once you have that, you will want that patched file into the fastboot directory on your computer. You will also want the vbmeta and the patched vbmeta img files (from the root moto vision package) in this directory. I have not used the updated version, I am using the older. I don't know about using the newer package which only has 1 vbmeta file.
Put your phone into fastboot mode.
Flash the vbmeta.img file, then the magisk patched boot file, then the vbmeta patched file. Then do a fastboot wipe of the phone.
Reboot the phone.
Set it up again, install magisk manager, then open it, and it should ask to configure. Let it do that, it should reboot and after that, you should be rooted.
[email protected] said:
I have Motorola One Action w/ Android 10 running. I need to root this phone to recover the data. However, when following the instruction, I received the following error message.
C:\adb>fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
downloading 'boot.img'...
OKAY [ 1.118s]
booting...
FAILED (remote failure)
finished. total time: 1.305s
Can anyone help me what to do?
Thank you very much for your help.
Click to expand...
Click to collapse
I guess goofball2k detailed reply might have helped by now. On the other hand, I'm just curious to know that the next time you or anyone else for that matter face the same issue, please flash the stock firmware (using any of the Android 10 tools from here ) at that instance, then again start the same process and let me know whether you succeed or not (you will still have to execute the fastboot boot twrp command around 4-8 times, but during all these attempts, you should now get the success message, and after x number of attempts, you should succeed). So in short, if flashing the stock firmware after that error helps you out, do let me know
Thank you
binary**# said:
I guess goofball2k detailed reply might have helped by now. On the other hand, I'm just curious to know that the next time you or anyone else for that matter face the same issue, please flash the stock firmware (using any of the Android 10 tools from here ) at that instance, then again start the same process and let me know whether you succeed or not (you will still have to execute the fastboot boot twrp command around 4-8 times, but during all these attempts, you should now get the success message, and after x number of attempts, you should succeed). So in short, if flashing the stock firmware after that error helps you out, do let me know
Click to expand...
Click to collapse
Thank you very much for your input.
How are you!!
It doesn't leave me at all ... everything I want to flash throws the same error:
C:\platform-tools>fastboot boot vbmeta.img
creating boot image...
creating boot image - 6144 bytes
downloading 'boot.img'...
OKAY [ 0.013s]
booting...
FAILED (remote failure)
finished. total time: 0.184s
What can be?
Polnareff said:
How are you!!
It doesn't leave me at all ... everything I want to flash throws the same error:
C:\platform-tools>fastboot boot vbmeta.img
creating boot image...
creating boot image - 6144 bytes
downloading 'boot.img'...
OKAY [ 0.013s]
booting...
FAILED (remote failure)
finished. total time: 0.184s
What can be?
Click to expand...
Click to collapse
You aren't flashing, your command is trying to boot from vbmeta.img. You are missing the flashing command.

Need Urgent help regarding my Realme 3 pro very Hard Brick...

Today i tried to install custom rom on my realme 3 pro and i was successful in doing it, later decided to revert back to stock Realme UI so i downloaded the Ozip from official site of realme, flashed it using twrp and rebooted......
Device is not booting to the system instead it is booting back to Fastboot mode and i even tried booting to recovery from fastboot and it is coming back to fastboot mode..
tried flashing recovery image from fastboot and it is throwing error
./fastboot flash recovery recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.424s]
Writing 'recovery' FAILED (remote: 'unknown command')
fastboot: error: Command failed
what ever command i try to pass, i am getting the same error...
HELP NEED ASAP please...

TWRP failed install on 3a XL Android 9

I have been trying and failing to get TWRP installed on my Pixel 3a XL running Android 9 stock image
Trying the recommended install instructions from the TWRP website, I keep getting the following error;
Code:
C:\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (65536 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
C:\platform-tools>fastboot recovery twrp.img
fastboot: usage: unknown command recovery
C:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (65536 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
I have ensured the bootloader is unlocked, I have updated drivers from the OEM package, I can see devices properly with fastboot and adb, and I've even flashed stock images with fastboot. I've tried looking up this error, but all results point to solutions that don't work, or deleted posts. If anyone has some insight, I'd very much appreciate it.
Update to the latest version of Android or try an older version of TWRP. The latest version of TWRP doesn't like Android 9 (possibly other versions as well).
I believe this was the last update for twrp on android 9
Download twrp-installer-3.5.2_9-0-bonito.zip
Download page for twrp-installer-3.5.2_9-0-bonito.zip
dl.twrp.me

Categories

Resources