Database Info

can I update my op6 after this...

Hi guys,
I'll tell you the story first, so you can see the whole picture and answer me based on it.
A few days ago I was trying to flash twrp and magisk on my op6 oos 9.0.3. I failed a lot and went into a lot of bootloops and crashdump and black screen but got out of these situations somehow. eventually, I found a way to root using patched magisk and it worked, but I didn't have twrp. So I uninstalled magisc from the app itself and rebooted, but that caused my op6 to get into a bootloop. Luckily I was able to get to the fastboot mode but after trying to flash different twrp imgs, and failing becasue I was just trying without any previous experience and that's stupid, I know. Anyway, fastboot started to give me this error "downloading 'boot.img'... OKAY [ 0.769s] booting... FAILED (remote: Failed to load/authenticate boot image: Load Error) finished. total time: 0.784s " so I used this command "fastboot --set-active=B" to switch to slot b and it worked, then I flashed twrp and magisk successfully because I learned a lot from those failures.
So, idk what happened to slot a, so when I recieve an update in the future for op6, can I update normally from updates in settings or do I have to do it manually or what? I really have no idea and I would like to have an expectation to what may happen.

olik2000 said:
Hi guys,
I'll tell you the story first, so you can see the whole picture and answer me based on it.
A few days ago I was trying to flash twrp and magisk on my op6 oos 9.0.3. I failed a lot and went into a lot of bootloops and crashdump and black screen but got out of these situations somehow. eventually, I found a way to root using patched magisk and it worked, but I didn't have twrp. So I uninstalled magisc from the app itself and rebooted, but that caused my op6 to get into a bootloop. Luckily I was able to get to the fastboot mode but after trying to flash different twrp imgs, and failing becasue I was just trying without any previous experience and that's stupid, I know. Anyway, fastboot started to give me this error "downloading 'boot.img'... OKAY [ 0.769s] booting... FAILED (remote: Failed to load/authenticate boot image: Load Error) finished. total time: 0.784s " so I used this command "fastboot --set-active=B" to switch to slot b and it worked, then I flashed twrp and magisk successfully because I learned a lot from those failures.
So, idk what happened to slot a, so when I recieve an update in the future for op6, can I update normally from updates in settings or do I have to do it manually or what? I really have no idea and I would like to have an expectation to what may happen.
Click to expand...
Click to collapse
As per my knowledge, since you already have your bootloader unlocked and have custom recovery, you might no lt be able to install updates directly. You will have to download them from oneplus' official website and then manually flash the updates. This has to be followed with the normal twrp recovery or unlocked bootloader.
I am not too sure about slot a and b, but I hope the procedure will be same. If you want to directly get updates, you will have to flash original recovery and OOS from oneplus' website.

Download and flash manually using twrp. Should be just fine.

happiy91 said:
As per my knowledge, since you already have your bootloader unlocked and have custom recovery, you might no lt be able to install updates directly. You will have to download them from oneplus' official website and then manually flash the updates. This has to be followed with the normal twrp recovery or unlocked bootloader.
I am not too sure about slot a and b, but I hope the procedure will be same. If you want to directly get updates, you will have to flash original recovery and OOS from oneplus' website.
Click to expand...
Click to collapse
That's really helpful, thanks :highfive:

My OnePlus 7 Pro is bricked.

My OnePlus 7 Pro keep booting into fastboot mode. Neither I can access recovery nor can start the phone. It's always comes back to recovery.
Please help me getting it done.
Bootloader is unlocked.

You haven't given enough info, tell us step by step how your "Bootloader is unlocked".
We would need to know if you did it properly, you probably need to go into the recovery and perform a "Full wipe". Unlocking the bootloader usually does that anyway.
The normal method is:
Enabled developer settings by pressing the version number in the about section 7 times and entering your pin
Copy the adb developer folder from the mounted OnePlus driver partition you usually get on your computer when attaching the phone, into a folder on your hard drive, and enable adb in developer settings.
In developer settings enable "OEM unlocking"
Reboot into fastboot mode
Open a command window (with admin privileges) in the folder you copied to your hard drive (In Windows, hold down shift and right click inside the folder, then click "Open Command Window..."
Run the command "fastboot oem unlock"
Accept the prompt shown on the phone
This will wipe the phone back to factory reset so ensure you have backed up your data, although you should be doing that before you even start.
Flash the appropriate TWRP recovery partition (which afaik isn't even available yet so I'm not sure why you would unlock the bootloader so soon to be honest
If you didn't perform those steps or performed them in the wrong order then you've done it wrong.
Performing a factory reset in the recovery partition may get it booting again but it's hard to know with the minimal information you've provided.
Although again, why are you unlocking the bootloader when there hasn't been a TWRP version released yet? You won't be able to flash anything, not even Magisk.

I've unlocked bootloader by command of OEM unlocking.
After than the unlock, I rebooted it's again And installed some Magisk file, which made it stuck at fastboot.
I can't access the Recovery nor can restart Phone.
All I can do is switched it off And get back into fastboot again after.

Yeah, you can't flash things with the default recovery (That's just made for flashing the default builds), that's most likely why. Magisk was made to be flashed with TWRP.
Did you use the test TWRP here? If so, then go to that thread for help.
If you can get into the OnePlus recovery you could maybe grab a build from here and flash the default rom back, then start again using the guide I showed you but, tbh, I would wait until a good TWRP build is established and Magisk is confirmed to be working.
That thread also looks like it has the default recovery image too so you can flash that back on the phone with :
fastboot flash recovery filename (Just put the recovery image into the same folder as your adb.exe and fastboot.exe
Then see if you can reboot into it and flash the stock rom back on from the same thread.

How can I get things done back, all I've is fastboot.
It's a New set, please help (

dmishra639 said:
How can I get things done back, all I've is fastboot.
It's a New set, please help (
Click to expand...
Click to collapse
If you have fastboot, I've just told you how to get the default recovery back in above.
---------- Post added at 05:45 PM ---------- Previous post was at 05:28 PM ----------
Reading that thread again, flashing recovery is not as simple as it used to be due to the A/B partition model used now, so you'll need to read the instructions shown for recovery. My guess is that you didn't read them properly and flashed the recovery to the wrong partition. If you have flashed that TWRP then you need to seek support in that thread.

It's not gonna work with me,
Even if I'll download the zip file it's only flashable with a Twrp or Stock recovery. As stock recovery is not working.
Even if I'll try to flash a Twrp recovery it's showing up an error to me :
PS C:\adb> fastboot devices
420bdc60 fastboot
PS C:\adb> fastboot boot C:\adb\recovery.img
downloading 'boot.img'...
OKAY [ 0.585s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.636s
PS C:\adb> fastboot flash recovery C:\adb\recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (18828 KB)...
OKAY [ 0.575s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.580s
PS C:\adb>

dmishra639 said:
It's not gonna work with me,
Even if I'll download the zip file it's only flashable with a Twrp or Stock recovery. As stock recovery is not working.
Even if I'll try to flash a Twrp recovery it's showing up an error to me :
PS C:\adb> fastboot devices
420bdc60 fastboot
PS C:\adb> fastboot boot C:\adb\recovery.img
downloading 'boot.img'...
OKAY [ 0.585s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.636s
PS C:\adb> fastboot flash recovery C:\adb\recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (18828 KB)...
OKAY [ 0.575s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.580s
PS C:\adb>
Click to expand...
Click to collapse
This will sound stupid, but I had similar issues with the pixel and it was due to drivers and the port. Tried from a different machine and worked. Do you have the luxury to do so ?

Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.

dmishra639 said:
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
Click to expand...
Click to collapse
Grab this fastboot rom and flash...
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424

Why are you trying to flash recovery partitions when they don't exist on this device? Recovery is on the boot partition.

dmishra639 said:
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
Click to expand...
Click to collapse
Since you are familiar with custom rom,unlocked bootloader etc you should had known already that you must NOT flash any kind Magisk staff without having proper and functional twrp.
Even if it flashed successful that doesn't mean will work after reboot and normal restart.
That why you've brick your device.
And on the other hand with A/B partition things has changed dramatically evolving all custom made staff and how they works.
Oneplus device not work the same way as Xiaomi you've described.
Sent from my iPad using Tapatalk Pro

LLStarks said:
Why are you trying to flash recovery partitions when they don't exist on this device? Recovery is on the boot partition.
Click to expand...
Click to collapse
paatha13 said:
Since you are familiar with custom rom,unlocked bootloader etc you should had known already that you must NOT flash any kind Magisk staff without having proper and functional twrp.
Even if it flashed successful that doesn't mean will work after reboot and normal restart.
That why you've brick your device.
And on the other hand with A/B partition things has changed dramatically evolving all custom made staff and how they works.
Oneplus device not work the same way as Xiaomi you've described.
Sent from my iPad using Tapatalk Pro
Click to expand...
Click to collapse
Any post that describe exactly what changed? I havent flashed custom roms/kernels in close to two years due to OOS being satisfying enough. What I have done is fastboot into twrp and flash magisk(I believe). Will I still be able to do that with OP7 Pro?

dmishra639 said:
My OnePlus 7 Pro keep booting into fastboot mode. Neither I can access recovery nor can start the phone. It's always comes back to recovery.
Please help me getting it done.
Bootloader is unlocked.
Click to expand...
Click to collapse
I forget the command, but change the boot slot and try to reboot.

tech_head said:
I forget the command, but change the boot slot and try to reboot.
Click to expand...
Click to collapse
Fastboot flash boot C://path/to/recovery.img

SysAdmNj said:
Any post that describe exactly what changed? I havent flashed custom roms/kernels in close to two years due to OOS being satisfying enough. What I have done is fastboot into twrp and flash magisk(I believe). Will I still be able to do that with OP7 Pro?
Click to expand...
Click to collapse
You can read over here on 6T device details of how thing work with A/B partition.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
https://twrp.me/oneplus/oneplus6t.html
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
Also follow this thread about 7 Pro situation and how well work over time
[RECOVERY][3.3.1-2][guacamole]Unofficial TWRP recovery for OnePlus 7 Pro(Testing)
Sent from my iPad using Tapatalk Pro

joemossjr said:
Fastboot flash boot C://path/to/recovery.img
Click to expand...
Click to collapse
Man, thank you so much
You literally made my day,
Wht I've did wrong in a flow was I had given the command: fastboot flash boot and the magisk location.
That was a stupidity, all I forgot was the command.
Now I used the same command and then used oxygen os fastboot flashable all bat file, as suggested by a member.
And here's my phone back. )
Thanks

In case, I'm completely New to OnePlus
It someone suggest me how to Root OnePlus 7 Pro normally, cuz I've to edit the build prop due to some reason.
My bootloader is unlocked but can't flash custom recovery.

dmishra639 said:
In case, I'm completely New to OnePlus
It someone suggest me how to Root OnePlus 7 Pro normally, cuz I've to edit the build prop due to some reason.
My bootloader is unlocked but can't flash custom recovery.
Click to expand...
Click to collapse
I remember when I edit the buildi prob on my v20 to be recognized as a pixel so google assistant can work and that bricked my device.

Robert235 said:
I remember when I edit the buildi prob on my v20 to be recognized as a pixel so google assistant can work and that bricked my device.
Click to expand...
Click to collapse
Man I've a 2gb daily add on (for 3 months), which will only gonna work with my previous device (Redmi note 5 pro).
So, I've to change OnePlus as Note 5 Pro as same.
I've did that tons of time on my past phone,it never did a brick TBH.

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.

Flash TWRP via fastboot android 10

Hello guys, as we known that it is unable to use command in fastboot to boot into TWRP if we are on Android 10 (both OOS and Custom rom) at the moment, so here is the simple command allow us to do that if you want to roll back android 9 or any rom by TWRP
fastboot flash boot_a <twrp name.img>
fastboot flash boot_b <twrp name.img>
fastboot reboot
Your phone will automatically boot into TWRP, so you can flash another rom

Can anyone confirm this works?
I tried something similar when I first installed OOS 10, and I successfully booted TWRP, but I ended up getting a bootloop (stuck at the g.co/ABH warning thing) when I rebooted to system. I don't know if I did something wrong, or flashing twrp to both boot partitions caused it.
I would try again, but I'm on a critical work trip until the end of the month, so my phone's uptime is expected to be 100% until then.

worked for me while anything else didnt

LazerH said:
worked for me while anything else didnt
Click to expand...
Click to collapse
Does it wipe your data?

Didn't work for me. My boot image was patched already this is probably why.

ok, I tried this, but as reported above, now also stuck on this same: "I tried something similar when I first installed OOS 10, and I successfully booted TWRP, but I ended up getting a bootloop (stuck at the g.co/ABH warning thing) when I rebooted to system. I don't know if I did something wrong, or flashing twrp to both boot partitions caused it."
How do I resrore operation for my phone? (help?)

Well, I met this issue before, and ended up with using this method to successfully boot into twrp.
This issue seems to appear on OOS, when I using `fastboot boot xxx.img` on other ROM like omni, I'm able to boot into twrp, thanks!

can someone help me please. my phone is stuck in a fastboot bootloop. everything I try doesn't work.
fastboot boot TWRP.img NOTHING
tried your solution above and still nothing
Still stuck in fastboot this is what I get:
PS C:\Users\Les Brown\Desktop\OnePlus 6> fastboot boot twrp-3.3.1-17-enchilada-Q-mauronofrio.img
downloading 'boot.img'...
OKAY [ 0.617s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.655s

@killathenoob Download DECRYPTED OOS 10.3.0 with this help if you don't really know what to do with this.
For others people (and you if you want to root or just install TWRP after fresh OOS10 Decrypted install) don't forget to OEM unlock before doing anything.
Download this
Copy "twrp-3.3.1-17-enchilada-installer-mauronofrio.zip" into internal storage of your OP6
Power it OFF
Power it ON in fastboot mode
Launch "Boot TWRP.bat"
Connect your OP6 to your PC and wait for TWRP to boot
Install twrp-3.3.1-17-enchilada-installer-mauronofrio.zip
Reboot to recovery and install magisk if you need to.
Source
Hope I helped a bit.

[TWRP] TWRP 3.4-0-0 For Umidigi A7 Pro[MT6763][Android 10]

TWRP for Umidigi A7-Pro phone.
Whats working:
Adb
Mtp
USb-OTG
MicroSD
Flash Image
Mount System , Vendor, product (contents of SUPER).... mount allows reading the partitions, but was not able to write to them
Back-Up/Restore to/from usb (or micro sdcard).... Due to size of super.img needed to format card ext4
Logcat
Screenshot
Known bug:
data decryption is not working, so not able to read or backup internal storage.
Built with Minimum Manifest _branch 10.0 :
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni
Kernel source :
****USED STOCK PREBUILDT___MFG Not RELEASED SOURCE*****
Device Tree :
https://github.com/mrmazakblu/Device-TWRP-Umidigi-A7-Pro
Download : https://github.com/mrmazakblu/Device-TWRP-Umidigi-A7-Pro/releases

Thanks for your work!
Does "Flash Image" mean it is now possible to flash Custom Rom's like Lineage OS?
If so which version would I need to download?
Would [GSI][10] LineageOS 17.x GSI (all archs) be the correct version?

torusJKL said:
Thanks for your work!
Does "Flash Image" mean it is now possible to flash Custom Rom's like Lineage OS?
If so which version would I need to download?
Would [GSI][10] LineageOS 17.x GSI (all archs) be the correct version?
Click to expand...
Click to collapse
No, not directly , anyway. You can flash boot
Img, recovery.imf, and super.img.
You could use lpmake and unpack your super.img and repack with the gsi-system.img on your pc and flash that new super.img
There are people using similar tools on the recovery, but I have not tried it.
There is one that cought my attention "system swapper". Unfortunatly I have not tried it yet.
If all you want is to try gsi, stock fastbootD can flash it

i just got this device for my little ones for xmas
so i have time to test whatever until then....
as long as i can still spflash stock image afterwards

mrmazak said:
No, not directly , anyway. You can flash boot
Img, recovery.imf, and super.img.
You could use lpmake and unpack your super.img and repack with the gsi-system.img on your pc and flash that new super.img
There are people using similar tools on the recovery, but I have not tried it.
There is one that cought my attention "system swapper". Unfortunatly I have not tried it yet.
If all you want is to try gsi, stock fastbootD can flash it
Click to expand...
Click to collapse
how to flash gsi on umidigi a7 pro using fastboot bro? or can you put the link of the Ipmake tool for unpacking and repacking super.img thanks

Kidkulafuw8 said:
how to flash gsi on umidigi a7 pro using fastboot bro? or can you put the link of the Ipmake tool for unpacking and repacking super.img thanks
Click to expand...
Click to collapse
I have it written in another device thread. But steps are the same.
[stock Rom] Blu G-90 G0310WW
Blu G90 device shipped from factory with Android 10 as with other devices from blu they do not have a public download of there roms. So here is the stock rom pulled from the device with SP-Flash tool. Both the shipped rom build fingerprint...
forum.xda-developers.com

For now there are still some problems to install .zip, like magisk and gapps, for example, but I hope that it will continue in development until reaching a stable version. Thanks!

Hello may i ask how do i patch vbmeta?

Hello, do you think you will be able to get data decryption working anytime in the future? I need help with a bricked phone...

Hi, I did not find twrp umidigi a3s do you have please

Alucard said:
Hello may i ask how do i patch vbmeta?
Click to expand...
Click to collapse
adb reboot bootloader
fastboot --disable-verification flash vbmeta vbmeta.img

mrmazak said:
No, not directly , anyway. You can flash boot
Img, recovery.imf, and super.img.
You could use lpmake and unpack your super.img and repack with the gsi-system.img on your pc and flash that new super.img
There are people using similar tools on the recovery, but I have not tried it.
There is one that cought my attention "system swapper". Unfortunatly I have not tried it yet.
If all you want is to try gsi, stock fastbootD can flash it
Click to expand...
Click to collapse
Can you please tell me how to do it?
I've tried flashing DotOs 5.2, I extracted it then compressed it back into a zip file then tried to flash it using FastboodD (selecting The option "apply update from Sd Card") but it always gives me the same error "Footer is wrong, Signature verification failed, error 21, Fota installation aborted, Bad file descriptor" Pls help what should I do?

imfedupwiththisphone said:
Can you please tell me how to do it?
I've tried flashing DotOs 5.2, I extracted it then compressed it back into a zip file then tried to flash it using FastboodD (selecting The option "apply update from Sd Card") but it always gives me the same error "Footer is wrong, Signature verification failed, error 21, Fota installation aborted, Bad file descriptor" Pls help what should I do?
Click to expand...
Click to collapse
Your process is not correct. And not along the outline I mentioned in the quoted post.
You cannot flash zip file in fastbootd.
There are more detailed guides here on xda. I do not have a link at the moment. But try and search for "flash gsi with fastbootd" I'm sure you can find guide available.

mrmazak said:
Your process is not correct. And not along the outline I mentioned in the quoted post.
You cannot flash zip file in fastbootd.
There are more detailed guides here on xda. I do not have a link at the moment. But try and search for "flash gsi with fastbootd" I'm sure you can find guide available.
Click to expand...
Click to collapse
It's no problem, I've already solved it

Hello mrmazak, how are you?
I finally managed to flash a GSI on the Umidigi A7 pro. Flashed PHH's GSI AOSP, version 411 - Android 12.
The problem is that when flashing your TWRP, I can't boot, it's in a loop.
I flashed like this:
[email protected]:~/Documentos/A7pro/twrp 340 MRMazak$ sudo su
[sudo] senha para edupaz:
[email protected]:/home/edupaz/Documentos/A7pro/twrp 340 MRMazak# adb devices
List of devices attached
A7PRO205020712 device
[email protected]:/home/edupaz/Documentos/A7pro/twrp 340 MRMazak# adb reboot fastboot
[email protected]:/home/edupaz/Documentos/A7pro/twrp 340 MRMazak# fastboot devices
A7PRO205020712 fastboot
[email protected]:/home/edupaz/Documentos/A7pro/twrp 340 MRMazak# fastboot --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta' OKAY [ 0.014s]
Finished. Total time: 0.027s
[email protected]:/home/edupaz/Documentos/A7pro/twrp 340 MRMazak# fastboot flash recovery recovery.img (I renamed the image)
Sending 'recovery' (23168 KB) OKAY [ 1.389s]
Writing 'recovery' OKAY [ 0.330s]
Finished. Total time: 1.732s
[email protected]:/home/edupaz/Documentos/A7pro/twrp 340 MRMazak# fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.052s
Click to expand...
Click to collapse
Can you give me an idea how to fix the problem?
Now, after writing this message, which I called myself, that this version of TWRP is for Android 10. Do you have any predictions to launch for Android 12?

Umidigi A7 Pro
So ive been out of the loop for several years. I did manage to get root on stock rom finally, now that magisk has been fixed. Been impressed with the ease of use with magisk modules. Its nice to have access to root apps too.
Of course, im still running stock recovery, but am interested in getting custom recovery in there to have the ability to backup/restore, and possibly flash a rom, if any were available.
Thats not really a priority tho, and im wondering if, at this point, if its worth bothering spending the time to change recovery? For a layman, and fairly avg user, would it be beneficial, or would you all say best to just wait and enjoy rooted stock rom for the time being?
Thanks for the effort in developing for this device. Its a solid phone for the money. Only issue ive had is with it not notifying of message push notices in certain apps. Seems to be the rom, cause i can tether to it and get notices on time with every other device