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!
Related
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
Hello everyone !
I was trying to put a LineageOS on my OP7P with this rom.
I unlocked the bootloader, boot onto the TWRP image (this one), flashed the ROM and then I got into troubles.
When I flashed the ROM, I didn't see any "go back" button, so I just pressed the "reboot system" one.
I came back to recovery, only of course to see that I have the "basic" recovery menu. So I got into the bootloader mode and tried to fix this, nothing I did fixed it...
I tried and got :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrpop7pro.img
downloading 'boot.img'...
OKAY [ 0.692s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.692s
I have no idea why is it not working. I tried the fastboot oem unlock, but it tells me it's already unlocked.
Then, by seaching, I tried but got this :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.3.1-74-guacamole-unified-installer-mauronofrio.zip
target reported max download size of 805306368 bytes
sending 'recovery' (17872 KB)...
OKAY [ 0.389s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 0.405s
Which seemed logical to me as the OP7P has 2 slots, but when I searched alternative to this answer it only brought me back to the first answer.
So now I don't know what to do to boot again on a TWRP and fix all this. Thankfully, I can boot on my main system and my LineageOS is working. But I still want to root it with Magisk and use the NanoDroid installer.
Anyway, if anyone here has any idea to help me, I would be very grateful
Hi all,
Long story short, I did wanna install Snapchat, but my phone was rooted with magisk, so I did wanna do an reinstall of the latest OP6 10 andr. version.
But now I get in a bootloop the issue I see now when I try with ADB on Windows laptop is the following: "FAILED (remote: Failed to load/authenticate boot image: Load Error)".
My commands I tried:
PS C:\adb> fastboot flash recovery_a C:\adb\twrp-3.4.0-1-enchilada.img
target reported max download size of 805306368 bytes
sending 'recovery_a' (31072 KB)...
OKAY [ 0.792s]
writing 'recovery_a'...
FAILED (remote: (recovery_a_b) No such partition)
finished. total time: 0.819s
PS C:\adb> fastboot flash recovery_b C:\adb\twrp-3.4.0-1-enchilada.img
target reported max download size of 805306368 bytes
sending 'recovery_b' (31072 KB)...
OKAY [ 0.793s]
writing 'recovery_b'...
FAILED (remote: (recovery_b_b) No such partition)
finished. total time: 0.834s
PS C:\adb> fastboot boot C:\adb\twrp-3.4.0-1-enchilada.img
downloading 'boot.img'...
OKAY [ 0.794s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.833s
PS C:\adb>
Help... I know how to unbrick this device, but I can't lose the WhatsApp data etc, I didn't back up.
Thanks!
Hey! I've run over a similar issue on op6t.
I'd recommend you doing what I've mentioned in this reply: https://forum.xda-developers.com/showpost.php?p=82995393&postcount=2
trying to install twrp,the bootloader is already unlocked.
this is what happens:
fastboot flash recovery recovery.img
target reported max download size of 805263360 bytes
sending 'recovery' (34200 KB)...
OKAY [ 0.728s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.841s
fastboot boot recovery twrp.img also give a error
what is the solution ?
neozbr said:
trying to install twrp,the bootloader is already unlocked.
this is what happens:
fastboot flash recovery recovery.img
target reported max download size of 805263360 bytes
sending 'recovery' (34200 KB)...
OKAY [ 0.728s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.841s
fastboot boot recovery twrp.img also give a error
what is the solution ?
Click to expand...
Click to collapse
OK:
1. First you need to root the device. Follow this guide. You will use adb to patch the boot.img file of your current firmware.
2. After you have rooted, you can install the unofficial TWRP for Android 10 Moto G8 Plus from here. The zip file will install through magisk. Works fine; I tested it last night.
!!!!!DISCLAIMER!!!!!! --- below info is provided as is without any warranty, do it on your own risk
I ported TWRP for Tab E10 from Asus Nexus 7 2012.
Installation:
1. Unlock bootloader.
2. Flash in fastboot (fastboot flash recovery <File name>)
3. Reboot to recovery from bootloader interface with volume buttons.
4. Uncheck Mount system partition read-only in Mount, and remount it.
5. In Advanced/File manager erase recovery-from-boot.p inside /system/
6. Done!
Bugs:
Encryption. You can use adb sideload or external sd.
Changelog:
26/12/2022
Initial port release.
27/12/2022
Userdata now uses F2FS.
Encryption fixed.
Added option to flash IMG to system.
17/02/2023
Added initial support for X104L.
Credits:
@Augustoandro for his guide "[GUIDE]Porting TWRP without source"
@jskelgaard for test with X104L model.
can't get it to work
C:\Users\jh\Downloads\platform-tools>fastboot flash recovery x104f\twrp-3.7.0_9-0-v2-x104f.img
Sending 'recovery' (15502 KB) OKAY [ 0.500s]
Writing 'recovery' OKAY [ 0.336s]
Finished. Total time: 0.880s
C:\Users\jh\Downloads\platform-tools>fastboot boot x104f\twrp-3.7.0_9-0-v2-x104f.img
Sending 'boot.img' (15502 KB) OKAY [ 0.490s]
Booting FAILED (remote: 'dtb not found')
fastboot: error: Command failed
jskelgaard said:
can't get it to work
C:\Users\jh\Downloads\platform-tools>fastboot flash recovery x104f\twrp-3.7.0_9-0-v2-x104f.img
Sending 'recovery' (15502 KB) OKAY [ 0.500s]
Writing 'recovery' OKAY [ 0.336s]
Finished. Total time: 0.880s
C:\Users\jh\Downloads\platform-tools>fastboot boot x104f\twrp-3.7.0_9-0-v2-x104f.img
Sending 'boot.img' (15502 KB) OKAY [ 0.490s]
Booting FAILED (remote: 'dtb not found')
fastboot: error: Command failed
Click to expand...
Click to collapse
You are sure to have "TB-X104F"? Exists others models like X104L.
Try to reboot from bootloader, maybe hotboot not work properly
mr.lfrl990 said:
You are sure to have "TB-X104F"? Exists others models like X104L.
Try to reboot from bootloader, maybe hotboot not work properly
Click to expand...
Click to collapse
as far as i can reed the x104l and x104f is the same except lte connection, but yes...i have two of the x104l versions.
Reserved