TWRP flash not allowed - General Questions and Answers

I'm trying to flash TWRP on my Pixel 3. I have bootloader unlocked and made sure several times all my settings were correct. Any help on if this could be caused by missing drivers or something? i'm new to custom ROMs. Thanks
here is what i get:
.\fastboot flash recovery twrp.img
Sending 'recovery' (65536 KB) OKAY [ 1.645s]
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed

Run
Code:
fastboot getvar all
and check for bootloader status: locked or unlocked?

Related

[Discussion] Rogers Post-911 Rooting

I wanted to bring this in here, as I found a way to enable fastboot to flash recovery!
Quick device info update:
HBOOT-1.33.0010
Radio-3.22.26.17
Ok, first put the phone into fastboot mode. Then execute the command:
fastboot oem rebootRUU
Wait for it to reboot in RUU mode. Then, when I execute fastboot flash recovery recovery-RA-dream-v1.6.2R.img, I get the following:
sending 'recovery' (4568 KB)... OKAY [ 1.721s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 3.036s
So, is there a signed recovery we can launch?
As an update, booting recovery:
downloading 'boot.img'... OKAY [ 1.647s]
booting...
hangs here

Failed remote command not allowed custom Rom (twrp)

Hi.
I've been trying to flash twrp my Huawai Mate 8 for a couple of weeks. I keep getting the error I mentioned in the title. The bootloader is unlooked, frp is looked. USB debugging is enabled. OEM is grey.
Android version 7.0, emui version 5.0.1. I've been using the official twrp and used adb files and fastboot from other sources as well as official files. The phone is NOT rooted.
Here is the full message:
fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (22142 KB)...
OKAY [ 0.470s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.477s
I would appreciate any help as this problem has bugged me for so long by now. Thanks!!

Is it possible to reunlock a relocked bootloader without the unlock code?

I have an honor 9 (stf-l09). Yesterday I flashed the stock firmware via HURU. Now I have the bootloader locked but when I go in bootloader mode it says "Phone Unlocked / FRP Unlock" but when I try to flash something via adb it says :
[email protected]:~$ fastboot flash recovery_ramdisk '/home/me/desktop/stf-twrp-zxz-0.3.img'
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (27144 KB)...
OKAY [ 0.903s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.910s
What can I do?
I'm on ubuntu 18.04 but it does the same on windows.
AirPl said:
I have an honor 9 (stf-l09). Yesterday I flashed the stock firmware via HURU. Now I have the bootloader locked but when I go in bootloader mode it says "Phone Unlocked / FRP Unlock" but when I try to flash something via adb it says :
[email protected]:~$ fastboot flash recovery_ramdisk '/home/me/desktop/stf-twrp-zxz-0.3.img'
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (27144 KB)...
OKAY [ 0.903s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.910s
What can I do?
I'm on ubuntu 18.04 but it does the same on windows.
Click to expand...
Click to collapse
Are you sure that you have USB debugging enabled in developer options on the device? Do you have OEM unlock enabled?
Sent from my LGL84VL using Tapatalk
Droidriven said:
Are you sure that you have USB debugging enabled in developer options on the device? Do you have OEM unlock enabled?
Click to expand...
Click to collapse
Yes, I've already done that but nothing happens, same command and same result

TWRP Not Booting

Hey guys,
I recently flashed HAVOC OS on my 1+7 Pro.
I got to TWRP by using the boot command, however now I cannot boot to TWRP. When using the command:
Code:
fastboot flash recovery twrp.img
I get the following error:
Code:
sending 'recovery' (31440 KB)...
OKAY [ 0.697s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.733s
Then when I try:
Code:
fastboot boot twrp.img
I get the following error:
Code:
downloading 'boot.img'...
OKAY [ 0.698s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.728s
Is anyone able to help?
Why not try installing TWRP via magisk?? Its easier that way
/\ agree /\
:angel:
lawrence_craig said:
Hey guys,
I recently flashed HAVOC OS on my 1+7 Pro.
I got to TWRP by using the boot command, however now I cannot boot to TWRP. When using the command:
Code:
fastboot flash recovery twrp.img
I get the following error:
Code:
sending 'recovery' (31440 KB)...
OKAY [ 0.697s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.733s
Then when I try:
Code:
fastboot boot twrp.img
I get the following error:
Code:
downloading 'boot.img'...
OKAY [ 0.698s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.728s
Is anyone able to help?
Click to expand...
Click to collapse
Make sure you are using the latest TWRP img.
Never flash recovery. Always boot recovery and then install TWRP zip. Have you not read the instructions?
As others mentioned, easier way to recover TWRP is to flash a magisk patch boot.img and flash TWRP zip in magisk.
Thanks for the tips guys, all sorted!

Flashing is not allowed for Critical Partitions

Hello guys!
Today I unlocked my old oneplus 6 phone,I wanted to flash google rom,so I execute
Bash:
adb reboot bootloader
and run flash script inside google android images.
Bash:
└─$ ./flash-all.sh
Sending 'bootloader' (4620 KB) OKAY [ 0.154s]
Writing 'bootloader' FAILED (remote: 'Flashing is not allowed for Critical Partitions
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.051s
I have no idea why this happpened,so I searched on google but got nothing.
And I've tried
Bash:
└─$ fastboot flashing unlock_critical
FAILED (remote: ' Device already : unlocked!')
Since I am new to these kinds of topics,any advice would be appreciated.
did you already set fastboot flashing unlock ?
makesure your adb / platform-tools is the latest too

Categories

Resources