Question [RESOLVED] Cannot flash recovery - Partition/Volume full - Xiaomi 12S Ultra

So, I upgraded from MIUI 13 Stable to MIUI 14 Weekly today (clean flash via fastboot). What I hadn't realized is that my TWRP was still on A12, so TWRP couldn't read internal storage.
But when I tried to flash the A13 TWRP via Fastboot, I get this error:
Code:
Warning: skip copying recovery image avb footer (recovery partition size: 104857600, recovery image size: 201326592).
Sending 'recovery' (196608 KB) OKAY [ 6.370s]
Writing 'recovery' FAILED (remote: 'Error flashing partition : Volume Full')
fastboot: error: Command failed
So, somehow, my recovery partition is way too small (or it is just full? But I already erased the old TWRP, so currently I have no recovery)
And the only way I can boot into TWRP is to use the fastboot boot command to temporarily boot into it.
Is there a way to deal with this without doing a wipe?
EDIT: My dumbass was trying to flash the Boot version of TWRP instead of the Rec version

TWRP
BOOT VERSION
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.

NOSS8 said:
TWRP
BOOT VERSION
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
Click to expand...
Click to collapse
Thanks for the reply, but I don't think the issue is related to fastboot since I can't flash the image in TWRP either.

wizpizz said:
Thanks for the reply, but I don't think the issue is related to fastboot since I can't flash the image in TWRP either.
Click to expand...
Click to collapse
Which img?

NOSS8 said:
Which img?
Click to expand...
Click to collapse
skkk's A13 TWRP image

wizpizz said:
skkk's A13 TWRP image
Click to expand...
Click to collapse
Btw the error message I get after trying to 'flash current TWRP' is this:
Code:
cd /tmp/abrec/ && /system//bin/magiskboot repack -n /dev/block/bootdevice/by-name/recovey_a /tmp/abrec/rec_a.img process ended with ERROR: 1
Error repacking image.

wizpizz said:
Thanks for the reply, but I don't think the issue is related to fastboot since I can't flash the image in TWRP either.
Click to expand...
Click to collapse
And if I try to flash it via 'Install', I get:
Code:
size of image larger than target device

wizpizz said:
skkk's A13 TWRP image
Click to expand...
Click to collapse
Installing Twrp and rooting are two different things.
No need for Twrp to root.
Is it weekly stock rom or Xiaomi Eu rom?

NOSS8 said:
Installing Twrp and rooting are two different things.
No need for Twrp to root.
Is it weekly stock rom or Xiaomi Eu rom?
Click to expand...
Click to collapse
I am such a moron lmao. I was trying to flash the Boot version of TWRP instead of the Rec version... Just flashed the Rec version and it works now. You made me check back on the TWRP thread, so thanks I guess ahah

Related

The stock recovery comes up instead of flashed twrp

Hello,
When I try to reboot to recovery the stock recovery comes up instead of twrp.
I have flashed multiple versions (through adb) of compatible twrp recoveries, but the issue was the same with all of them.
I am on android oreo with the latest update.
I just want to access twrp.
Did anyone experienced the same, or does anyone know hot solve this problem?
How are you booting to TWRP?
Which command are you using to flash TWRP?
Unplug usb + power + vol up, release pwr when phone vibrates/huawei logo is seen.
Or use 'adb reboot recovery'
ante0 said:
How are you booting to TWRP?
Which command are you using to flash TWRP?
Unplug usb + power + vol up, release pwr when phone vibrates/huawei logo is seen.
Or use 'adb reboot recovery'
Click to expand...
Click to collapse
Im using fastboot flash recovery_ramdisk recovery.img through adb
And im using power+volume up
MLGarlic said:
Im using fastboot flash recovery_ramdisk recovery.img through adb
And im using power+volume up
Click to expand...
Click to collapse
Post output from command prompt when flashing.
ante0 said:
Post output from command prompt when flashing.
Click to expand...
Click to collapse
I cannot access it but as i remember its output was successful. Nothing failed.
But somewhere it wrote that 31 version doesnt match 39 killing. But i could still flash the recovery afterwards successfully
ante0 said:
Post output from command prompt when flashing.
Click to expand...
Click to collapse
Hi
I have the same problem... Let me just round up the facts:
I have a Huawei Mate 9 Pro
The phone is unlocked, when i boot in to bootloader (adb reboot bootloader) it says PHONE Unlocked + FRP Unlock
When I flash twrp I get:
fastboot flash recovery_ramdisk twrp-3.1.1-0-hi3660.img
Sending 'recovery_ramdisk' (27944 KB) OKAY [ 0.658s]
Writing 'recovery_ramdisk' OKAY [ 0.268s]
Finished. Total time: 0.943s
When I afterwards try to boot into recovery (adb reboot recovery)
Error
Please update your system
Error
Func NO 11 (Recovery image)
Func NO 2 (Load failed)
I currently have build no LON-L29 8.0.0.323(C432LOG)
All I want to do is flash a newer image, can I do it with adb/fastboot directly?
i am using this recovery for my Mate 9 (L29) at https://forum.xda-developers.com/p10-plus/development/recovery-twrp-3-2-1-0-oreo-t3734993. Works fine. I suggest when you flash it via fastboot, please don't use command to reboot phone. Instead, just unplug phone and manually shut it off. Then, hold vol up + power buttons, it should load TWRP. I experienced that the reboot command loads eRecovery than TWRP.
martinhinge said:
Hi
I have the same problem... Let me just round up the facts:
I have a Huawei Mate 9 Pro
The phone is unlocked, when i boot in to bootloader (adb reboot bootloader) it says PHONE Unlocked + FRP Unlock
When I flash twrp I get:
fastboot flash recovery_ramdisk twrp-3.1.1-0-hi3660.img
Sending 'recovery_ramdisk' (27944 KB) OKAY [ 0.658s]
Writing 'recovery_ramdisk' OKAY [ 0.268s]
Finished. Total time: 0.943s
When I afterwards try to boot into recovery (adb reboot recovery)
Error
Please update your system
Error
Func NO 11 (Recovery image)
Func NO 2 (Load failed)
I currently have build no LON-L29 8.0.0.323(C432LOG)
All I want to do is flash a newer image, can I do it with adb/fastboot directly?
Click to expand...
Click to collapse
Only reason it would do this is because you're flashing an image meant for Nougat.
Try this one: https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353
ante0 said:
Only reason it would do this is because you're flashing an image meant for Nougat.
Try this one: https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353
Click to expand...
Click to collapse
And when you say image, you mean the twrp image, right? Which one of the four download links should I use? the one for mate 10 pro?
Thanks for your help
martinhinge said:
And when you say image, you mean the twrp image, right? Which one of the four download links should I use? the one for mate 10 pro?
Thanks for your help
Click to expand...
Click to collapse
What?
The thread I linked is for Mate 9, only one download link is in there.
Direct link: https://mega.nz/#!tgd2BIRS!NOk3XkSaBX8PC5xjyrZNyIIz52aSoPZFphQNauhTKGQ

Can't flash stock boot image

I am stuck in fastboot. The bootloader is unlocked and I do not have twrp. Everytime I try to install twrp I get this message "FAILED (remote: Failed to load/authenticate boot image: Load Error)" I think it is because my boot image is not there.
When I try to install factory boot image (fastboot flash boot.img) I get this message:
PS C:\platform-tools> fastboot flash C:\Users\Admin\Downloads\boot_stock.img
unknown partition 'C:\Users\Admin\Downloads\boot_stock.img'
error: cannot determine image filename for 'C:\Users\Admin\Downloads\boot_stock.img'
HELP PLEASE
fastboot flash boot boot.img
u missed the boot partition
Bradl79 said:
fastboot flash boot boot.img
u missed the boot partition
Click to expand...
Click to collapse
Just tried and it looks to have flashed, but I am still stuck in bootloader/fastboot menu
here is the output:
PS C:\platform-tools> fastboot devices
efba8ca6 fastboot
PS C:\platform-tools> fastboot flash boot C:\Users\Admin\Downloads\boot_stock.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.118s]
writing 'boot'...
OKAY [ 0.393s]
finished. total time: 2.520s
did you flash the correct boot.img for the correct phone model and os version?
you may just want to flash the fastboot rom
Bradl79 said:
did you flash the correct boot.img for the correct phone model and os version?
you may just want to flash the fastboot rom
Click to expand...
Click to collapse
Thank you! That fixed my problem. I flashed 10.0.1-GM21BA-OnePlus7ProOxygen_21.E.21_OTA_021_all_1910071445_8d6a-FASTBOOT
Now I'm back to stock and not rooted. Good thing I backed up my software before flashing.
What's the easiest way to gain root access again? Which specific files do I need?
My phone is GM1917 on Android 10 Oxygen OS 10.01.GM21BA
champstar said:
Now I'm back to stock and not rooted.
Click to expand...
Click to collapse
That is what flashing a stock boot.img does. What were you trying to accomplish by flashing stock boot.img?
champstar said:
Now I'm back to stock and not rooted.
What's the easiest way to gain root access again? Which specific files do I need?
Click to expand...
Click to collapse
Fastboot boot TWRP, then flash Magisk zip.
Use TWRP unofficial version -70 if you are on Android Q.
redpoint73 said:
That is what flashing a stock boot.img does. What were you trying to accomplish by flashing stock boot.img?
Fastboot boot TWRP, then flash Magisk zip.
Use TWRP unofficial version -70 if you are on Android Q.
Click to expand...
Click to collapse
Thank you! I am now rooted again. There's so much information available online, it is hard to nail down exactly what to do once something messes up.
Now my wifi is not working. I flashed the stock boot image so my kernel should be back to stock right?
I am on TWRP 3.3.1-70 and Magisk is up to date.
champstar said:
Now my wifi is not working. I flashed the stock boot image so my kernel should be back to stock right?
I am on TWRP 3.3.1-70 and Magisk is up to date.
Click to expand...
Click to collapse
Broken wifi probably means you flashed the wrong stock boot.img.
redpoint73 said:
Broken wifi probably means you flashed the wrong stock boot.img.
Click to expand...
Click to collapse
That did the trick, I flashed modded magisk for OS 10 and now wifi is working.

[UNOFFICIAL] [RECOVERY] [OnePlus 7 Pro] OrangeFox Recovery Project [R10.1]

[Deleted]
The flashing instruction makes no sense to me
Spookybear said:
INSTALLATION:
0. Backup your ROM, your data, your internal storage, and your settings/apps, to an external device
1. Reboot to your custom TWRP-based Recovery
2. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
3. Enjoy!
(Note: There is no zip file because this recovery is too big to fit in the ramdisk.
Click to expand...
Click to collapse
Can you please clarify this?
I assume install .IMG to Ramdisk? It will likely come up, so just want to cover all bases.
gorilla p said:
Can you please clarify this?
I assume install .IMG to Ramdisk? It will likely come up, so just want to cover all bases.
Click to expand...
Click to collapse
I tried that...no dice...
Flash to both _a and _b using trwp but recovery does not boot... so back to trwp til some future info...
I flashed via TWRP, via flash .img to ramdisk, rebooted to recovery and nothing.
Stuck at "Bootloader unlocked" screen
Tried to boot via fastboot and it failed.
Was this recovery tested on the OP7 Pro? If so, what ROM was being used and what was the flashing process?
Gungrave223 said:
The flashing instruction makes no sense to me
Click to expand...
Click to collapse
Sorry, fixed the instructions.
avid_droid said:
Yeah directions are honestly the worst I've seen on XDA yet.
Click to expand...
Click to collapse
Sorry, fixed the instructions.
I have a feeling these new instructions aren't going to work either, considering we don't have a recovery partition.
Spookybear said:
Sorry, fixed the instructions.
Click to expand...
Click to collapse
still no dice
HTML:
Writing 'recovery'
FAILED (remote: '(recovery_a)
No such partition'
I guess the command should be
fastboot boot /path to recovery
But again this wont flash recovery permanently AFAIK, everytime we need to boot into recovery we have to flash it via fastboot
insaneparnoid said:
I guess the command should be
fastboot boot /path to recovery
But again this wont flash recovery permanently AFAIK, everytime we need to boot into recovery we have to flash it via fastboot
Click to expand...
Click to collapse
He updated it with fastboot flash, indicating that this is to be installed, however it doesn't appear to work at all at this point.
For me is working , latest OOS beta. Just had to disable vbmeta in order to boot.
we need a flashble zip for this.
is OTG working with OrangeFox ?
otakutw said:
we need a flashble zip for this.
Click to expand...
Click to collapse
Not exactly, try - fastboot flash recovery *drag the image into the cmd then press enter*
Can this recovery be decreased in size so that it can be flashed to the ramdisk?
EDIT: It seems twrp is even bigger than this. Twrp img is 30.7mb while this is 29.4mb. Twrp does flash to the ramdisk. If this could be permanently flashed, it would be perfect. If the size needs to be decreased, certain graphics could be moved to the internal storage to save space on the ramdisk.
Hahaha wow what are you doing here it's like you didn't even test this at all. I'm tried to flash the installer in twrp and it tells me that this recovery is only for guacamole not OnePlus 7 pro. So it does not support custom roms clearly cause I'm on bliss
shadowikr said:
Not exactly, try - fastboot flash recovery *drag the image into the cmd then press enter*
Click to expand...
Click to collapse
There is no recovery partition on modern Android devices. The boot.img ramdisk contains the recovery

How to backup stock recovery before flashing TWRP?

Hi. How can I backup the stock recovery on my Xiaomi Poco X3 NFC before flashing the TWRP?
I tried executing following code while the phone is in fastboot mode but it never actually boots the custom recovery. It get's stuck at the poco boot logo. Yes my phone has unlocked bootloader.
Code:
fastboot boot TWRP.img
In terminal I get this output:
Code:
[email protected]:/# fastboot boot twrp_3.4.0-15_mauronofrio.img
downloading 'boot.img'...
OKAY [ 3.080s]
booting...
OKAY [ 5.088s]
finished. total time: 8.168s
Does anybody know why this command is not working? Thanks.
lebigmac said:
Hi. How can I backup the stock recovery on my Xiaomi Poco X3 NFC before flashing the TWRP?
I tried executing following code while the phone is in fastboot mode but it never actually boots the custom recovery. It get's stuck at the poco boot logo. Yes my phone has unlocked bootloader.
Code:
fastboot boot TWRP.img
In terminal I get this output:
Code:
[email protected]:/# fastboot boot twrp_3.4.0-15_mauronofrio.img
downloading 'boot.img'...
OKAY [ 3.080s]
booting...
OKAY [ 5.088s]
finished. total time: 8.168s
Does anybody know why this command is not working? Thanks.
Click to expand...
Click to collapse
I have had the same issues with that TWRP from mauronofrio and our stock ramdisk image. However, using Orangefox or the latest 3.5.0 TWRP which can be found in the Index for our device (everything can be found there lol) solved that issue, also, you don't need to backup the recovery partition, because the stock can be easily found and flashed the same.
Thanks but that still doesn't explain why the command fastboot boot twrp.img doesn't work on the Xiaomi Poco X3 NFC with unlocked bootloader.
EDIT:
Ok good news. I've actually managed to boot into the TWRP before flashing it.
As soon as it's done uploading the recovery to the phone you must unplug the USB cable. The timing is very important.
Good luck!
lebigmac said:
This appears to be a more widespread issue than I had originally thought:
Fastboot boot <boot.img> doesn't work but flash does
Hi there ! I compiled a kernel for my DB410. I am trying to boot it using $ fastboot boot boot.img Following the instructions that can be found here: https://builds.96boards.org/releases/dragonboard410c/linaro/debian/17.06.1/ Unfortunately, the device doesn’t boot. It starts the booting...
discuss.96boards.org
fastboot boot TWRP.img Not working
I'm trying to just boot the TWRP image for my OnePlus 5t to then install a custom ROM. So I typed fastboot boot "C:\Users\Elias\Downloads\twrp-3.3.1-0-dumpling.img" and it seemed to work and I got ...
android.stackexchange.com
https://www.reddit.com/r/LineageOS/comments/arakiy
After Android Q upgrade fastboot boot doesn't work on guacamole · Issue #1530 · TeamWin/Team-Win-Recovery-Project
I am running an official build of TWRP, downloaded from https://twrp.me/Devices/ I am running the latest version of TWRP I have read the FAQ (https://twrp.me/FAQ/) I have searched for my issue and ...
github.com
Can't boot TWRP image using fastboot boot
I'm trying to root my Moto Z3 Play. I'm on Windows 10, I have already unlocked the bootloader, however, I can't boot the twrp.img. I got the twrp.img from here https://twrp.me/motorola/motorolamoto...
stackoverflow.com
Click to expand...
Click to collapse
try latest OFOX or TWRP (OFOX image needs to be extracted from zip file), I'm really interested if some of these will boot via "fastboot boot recovery.img", thanks
lebigmac said:
Hi. How can I backup the stock recovery on my Xiaomi Poco X3 NFC before flashing the TWRP?
I tried executing following code while the phone is in fastboot mode but it never actually boots the custom recovery. It get's stuck at the poco boot logo. Yes my phone has unlocked bootloader.
Code:
fastboot boot TWRP.img
In terminal I get this output:
Code:
[email protected]:/# fastboot boot twrp_3.4.0-15_mauronofrio.img
downloading 'boot.img'...
OKAY [ 3.080s]
booting...
OKAY [ 5.088s]
finished. total time: 8.168s
Does anybody know why this command is not working? Thanks.
Click to expand...
Click to collapse
You don't need to backup the sock recovery.
Everything you need to do is download the stock rom and extract recovery.
@jeryll thanks for chiming in. All of these TWRP images will boot via "fastboot boot recovery.img" on our device.
It's important to unplug the USB cable at the right moment as soon as it's done uploading. Good luck!

How To Guide Xiaomi 12S Ultra TWRP(unofficial)

12S Ultra unofficial TWRP - link MEGA
Credit - UnofficialTWRP
They released TWRP under 12S Pro, but the code name is Thor which stands for 12S Ultra, and after flashing, I do confirm this is for 12S Ultra.
now they have a proper 12S Ultra section!
Download the image and rename as recovery.img for simplicity.
fastboot boot recovery.img (or full file name)
in TWRP, go to "Advanced" and "flash this twrp."
edit: the recovery image file is too large to be flashed directly via fastboot, so you need to boot first then flash using twrp!
edit2: backup and restore function may not be working properly on this version of twrp! I get boot loops everytime I do a full system backup and full restore after bricking the device, especially on the data partition. Clean installing rom then restoring data only still get boot loops. so use it with caution.
I suggest you to use 3rd party backup apps to do backups on apps and data, and stick to the flashing and other functions only for twrp.
original source unofficialtwrp.com
Nabicook said:
12S Ultra unofficial TWRP - link MEGA
Credit - UnofficialTWRP
They released TWRP under 12S Pro, but the code name is Thor which stands for 12S Ultra, and after flashing, I do confirm this is for 12S Ultra.
Download the image and rename as recovery.img for simplicity.
fastboot boot recovery.img (or full file name)
in TWRP, go to Advanced and flash this twrp.
original source unofficialtwrp.com
Click to expand...
Click to collapse
Awesome thanks. But why not Fastboot flash recovery recovery.img?
No. You must type fastboot flash boot recovey. img
dungnghien said:
No. You must type fastboot flash boot recovey. img
Click to expand...
Click to collapse
No I'm pretty sure it's:
fastboot flash recovery twrp.img
However my question was why the method outlined by @Nabicook vs this method. Is it because of the dual partition?
GodKingKnight said:
Awesome thanks. But why not Fastboot flash recovery recovery.img?
Click to expand...
Click to collapse
Because not only it is the method unofficialtwrp suggested, but also the size of the recovery img file is too large to be flashed via fastboot.
I already tried
fastboot flash recovery recovery.img
fastboot flash recovery_a recovery.img
and so on, but all failed.
only way to properly install this version of twrp is to boot first then let twrp to install itself to both a/b partitions.
Hi!
I'm following your guide...and after uploading recovery nothing happens
rebooting into recovery through ADB or just using buttons...still sends me into fastboot mode
What can I do?
joiliko said:
Hi!
I'm following your guide...and after uploading recovery nothing happens
rebooting into recovery through ADB or just using buttons...still sends me into fastboot mode
What can I do?
Click to expand...
Click to collapse
are you sure you did
fastboot boot (your recovery file name).img
it should automatically boot into twrp without touching anything from fastboot mode.
then install twrp through the advanced option in twrp
Nabicook said:
are you sure you did
fastboot boot (your recovery file name).img
Click to expand...
Click to collapse
Great many thanks! I was actually doing flash boot
Nabicook said:
then install twrp through the advanced option in twrp
Click to expand...
Click to collapse
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
joiliko said:
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
Click to expand...
Click to collapse
yeah you can try flashing stock boot img, and if that doesnt work, you can download fastboot rom and flash stock rom using flash all without wiping data(there is .bat file that says something like install without formatting).
That will fix any kind of brick issues of xiaomi device, and you just redo the twrp part.
joiliko said:
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
Click to expand...
Click to collapse
How to Extract payload.bin and get stock boot image file
To extract the payload.bin file from Android stock firmware and get stock boot image file, you should refer to the instructions given in here.
www.droidwin.com
My idea worked!
I used the method above to extract boot.img & flashed it successfully
Can someone tell me why wipe data and settings dosent work on my 12s ultra every time reboots the twrp after i press the icon... Im try at 7.5 version the same and on 7.2

Categories

Resources