Database Develop

Problems After Flashing Back to OxygenOS from LineageOS

I was successfully able to install TWRP and LineageOS on my OnePlus3T. However, due to the bugs in LineageOS, I downloaded the latest (non-Beta) OxygenOS from the OnePlus website and flashed that back onto my phone. I didn't realize that this would remove TWRP and give me an error screen about dm-verity error (in red) during the boot process. I have tried many things to get rid of the dm-verity error and to put TWRP back on the device so that I can eventually move back to a custom ROM. However, I am unable to get rid of the dm-verity error and everytime I try to install TWRP, it gets stuck on the TWRP splash screen. Then, I have to hold down the power button to power off, power back on, re-encounter the red dm-verity error and I am back into OxygenOS.
How can I get rid of the dm-verity error and get TWRP back on my phone?

Try sideloading any OOS version 4.0.2 or below, then use the following commands in fastboot:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
This will reset dm-verity, remember to root or flash the no-verity zip after flashing TWRP or it will trip dm-verity again.
This will not work in OOS 4.0.3 or the latest open beta as OP has patched out those commands.

Anova's Origin said:
Try sideloading any OOS version 4.0.2 or below, then use the following commands in fastboot:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
This will reset dm-verity, remember to root or flash the no-verity zip after flashing TWRP or it will trip dm-verity again.
This will not work in OOS 4.0.3 or the latest open beta as OP has patched out those commands.
Click to expand...
Click to collapse
I can do that. However the latest version of the fastboot command does not allow for fastboot oem disable_dm_verity (assuming that this command runs from the PC and is executed against the phone via USB). For example, in command prompt, if I type fastboot help, there are no options for oem disable or oem enable.

oem disable_dm_verity doesn't show up in my fastboot prompt either when I enter "fastboot", but it was able to lock and unlock dm-verity when I used it a few weeks ago. I'm not entirely sure what version of fastboot I have, though are you sure the command was removed and not just hidden?

Anova's Origin said:
oem disable_dm_verity doesn't show up in my fastboot prompt either when I enter "fastboot", but it was able to lock and unlock dm-verity when I used it a few weeks ago. I'm not entirely sure what version of fastboot I have, though are you sure the command was removed and not just hidden?
Click to expand...
Click to collapse
I used it earlier today and it said that it is an unknown command. However, I attempted it against OOS 4.0.3. I don't think this should matter.

You could try using older versions of minimal adb and fastboot:
https://forum.xda-developers.com/showthread.php?t=2317790

Thanks. I will try an older version this evening and let's see what happens. I should be able to get OOS 4.03 correct? Is there a reason you are recommending OOS 4.02 and lower?

Oneplus patched out the fastboot oem lock/unlock commands in the OOS 4.0.3 update. The phone will refuse the commands outright, technically it was a vulnerability. I suspect that the reason your fastboot was unable to run the command was because the phone's firmware didn't recognize it, not because the commands were removed from fastboot.
Those commands will only work on OOS with firmwares from 4.0.2 or below.
You could flash only the 4.0.2 firmware without replacing the entire 4.0.3 ROM by using this guide, though I'm not sure if you can do it without TWRP.
After resetting dm-verity on an older version, you can dirty flash OOS 4.0.3 (or just the firmware if you followed the guide).

weaponG said:
IHowever, everytime I try to install TWRP, it gets stuck on the TWRP splash screen. Then, I have to hold down the power button to power off, power back on, re-encounter the red dm-verity error and I am back into OxygenOS.
How can I get rid of the dm-verity error and get TWRP back on my phone?
Click to expand...
Click to collapse
TWRP Is already flashed on your phone
You just have to wait a while as oxygen os uses f2fs system and it takes time to boot into twrp
For the dm verity error you can follow the guide which is mentioned above
But as the error does not affect any functionality of Rom it should not be bothered with

Thank you all for your help. I did wait out the TWRP splash screen for about 20 minutes and it didn't seem to make any difference. The resolution was to download and install OOS 4.02 via adb sideload and then perform the following commands: fastboot oem disable_dm_verity, fastboot oem enable_dm_verity. The sideload of OOS 4.02, itself, did remove the dm-verity error. However, I wanted to be sure and performed the fastboot oem commands. (As speculated earlier in this post, fastboot oem enable_dm_verity and fastboot oem disable_dm_verity are known and working commands against OOS 4.02, but NOT against OOS 4.03.) I was then able to install TWRP and am now running a version of CM which has been modded by Sultan. This is a very stable ROM and is exactly what I was looking for. The issues which I had with LineageOS do not occur in Sultan's ROM.

Solved with Corrections: Unable to flash TWRP, Failed (Remote: command not allowed)

Hi,
I just purchased a used Xperia Z1 C6903 and I am trying to put the latest Nougat Resurrection Remix on it. I need to get TWRP going first which I got stuck at trying to flash it.
I was able to get the phone downgraded to 14.1.G.1.534 using flash tool (ver 0.9.24.3). I did this following the guide here https://forum.xda-developers.com/showthread.php?t=2439328.
I was able to root it using Kingoroot.
I was able to unlock the bootloader using flashtool. Using *#*#7378423#*#*, the phone now reports Bootloader Unlocked: yes. See attached screenshot.
The part that I got stuck at is trying to flash TWRP in Fastboot. The command lines and error are below. The main error being "FAILED (remote: Command not allowed)"
I don't have an option in developer's options to "Unlock OEM bootloader". I read some other Xperia users being able to fix this problem by checking this.
I am running Windows 8.1. I am relatively sure that my drivers are correct. I had gotten a "drivers too old" error before in Flashtools but I was able to correct it by reinstalling new drivers.
I tried having debugging checked and unchecked before going into Fastboot and made no difference.
Tried both twrp-2.8.7.0-honami and twrp-3.0.2.0-honami with no success. Tried shortening file name to trp.img with no success.
Tried different 2 different adb files around the web with no success.
I read somewhere someone mentioned briefly that TWRP can be flashed using Flashtools. Is that true? I wasn't able to find a full guide for it.
Any help would be appreciated!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery trp.img
target didn't report max-download-size
sending 'recovery' (13672 KB)...
OKAY [ 0.433s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.439s

Well I was able to get TWRP on there by installing the XY Dual Recovery. The problem with it is that the Resurrection Remix's installation instruction says to use TWRP 3x or higher. TWRP on XY is only at 2.8.7.0. I couldn't find a TWRP 3x flashable zip file for Honami and TWRP wouldn't flash TWRP 3x IMG file I found. Fastboot is still giving me the same Command Not Allowed error.
Any ways, I went ahead and flashed RR with 2.8.7.0. When I tried to flash GAPPs after it says there is insufficient space. I have at least 9GB+ internal storage. So not sure what the deal is there.
I also lost Dual Recovery and root after first RR boot.
Looking into getting re-rooted and reinstalling XY Dual Recovery now.. And then flashing GAPPS after.
Anyone know what the consequences are for installing RR with a lower rev of TWRP?

So the RR Rom does have root but it just doesn't have apps root. Only ADB root. I cant flash the su add on from Lineage's site since I lost recovery. I ended up FTF back to stock and then reflashed everything, the ROM then pico version of GAPPs (pico worked) and then the su addon. The su addon had an error when flashing in TWRP.
Any ways, long story short the whole thing didn't work. Still stuck with RR Without recovery. Su addon didnt work from the flash. And for whatever reason my SIM is not detected and I lost my IMEI in RR. I read that this is a known issue with C6902 but I have the C6903 and I had confirmed this through the service menu before ROM flash. Maybe problems with flashing RR without the latest TWRP.
The Command Not Allowed is still an issue that I dont know how to resolve. So I still can't flash newer version of TWRP.
Any help would be appreciated....
I guess I will try to find a ROM that 's compatible with TWRP 2.8.7.0.

OK! I figured out what the Command Not Allowed problem is!
I've been following the flash guides from a few websites. And they all reference this syntax for flashing TWRP.
Fastboot flash recovery twrp.img.
This syntax didn't work for me. All those websites properly copycat each other.
That syntax is either incorrect or just didnt work for my setup for some reason. I kept searching for ways to flash TWRP and found another website that uses a different syntax. I gave it a go and TWRP flashed right away. This is the syntax that worked for me.
Fastboot flash boot twrp.img
At least that part of the problem is resolved.
Even after flashing RR with TWRP 3.0.20, the SIM/IMEI is still not showing. Recovery is still lost on first boot. Reinstalling TWRP on top of RR causes RR to not boot any more. I will have to look into the RR thread to investigate more.
I will mark this thread as Solved for the Command Not Allowed.
Crossed out everything cause that was not the correct solution. Striked them out to keep them as part of the troubleshooting steps history.

Oops duplicated post.

OK! So it looks like I have to correct myself here on my previous solution.
My solution from earlier for using "Fastboot flash boot twrp.img" is incorrect apparently. Don't use this!
That was the reason why my TWRP was lost after RR boot. The recovery partition comes after the boot and system partition. By flashing the recovery into boot, it screws up the order.
Nevertheless, the Command Not Allowed was still a problem if I tried to use "Fastboot flash recovery twrp.img"
Any ways I was still looking into this problem and started looking into the boot.img stuff and saw someone uses this command line: "fastboot erase boot". This helps someone being able to flash a boot.img when the user was having the Command not Allowed problem trying to flash a different img for the boot partition.
This gave me an idea to try and use "fastboot erase recovery".
I gave it a try and I was able to use "fastboot flash recovery twrp.img" afterwards! It was done in a second.
Then I went through the normal steps of flashing RR and TWRP stayed this time. So now all is good with everything!
Any ways to recap, my full steps used for my RR Installation:
1. Flashtool to flash an Android 5.1.1 stock rom. I used C6903_14.6.A.1.236_1276. (obtained through Flashtool, Xperifirm) Your phone has to run in 5.1.1 for the SIM and IMEI to work in RR. Don't need to flash modem.zip, that's for C6902 only.
2. Fastboot flash erase recovery
3. Fastboot flash recovery twrp.img
4. Follow instructions to flash RR normally.
5. Resize system partition size (for flashing GAPPS micro size or larger).
6. Flash GAPPS.
7. Flash su addon from Lineage's website to allow root for apps and ADB.
I hope this helps someone with similar problems in the future. Thanks to those who stop in to see me ramble to myself about silly stuff

I had the same error message and was able to successfully flash using the phone and the Android Studio Emulator app.
I was already rooted and had an unlocked bootloader.

I tried this solution and it said error: cannot "recovery": No such file or directory LOL even though it's right here and I use it all the time..........I just can't figure it out.

Troubles reinstalling TWRP [Failed to load/authenticate boot image: Load Error]

I dirty flashed a new version of xiaomi.eu stable build, and it caused TWRP to uninstall itself.
Whenever I hold power on and volume up it just goes to fastboot.
Now I tried reinstalling TWRP like I've done many times before, but it keeps throwing an error. The error I get is when trying to boot without flashing the img. When I do this, I get the error:
Code:
fastboot boot TWRP.img"
downloading 'boot.img'...
OKAY [ 1.609s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.675s
Anyone gotten any ideas on what could be going on here? I'm scared to try anything as my phone currently works, but I need TWRP back to update my phone to a different versions and to install the clock mod again.
Thanks!

Got it to load once, but now back to square one. Throwing same error.

Now when running the command fastboot reboot recovery it's saying
Code:
fastboot: usage: unknown reboot target recovery
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.

Try on a computer with a USB 2.0 port, or a different usb cable, had the same issue once

Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.

I have the same error. How can I fix this pls?

MrkoZino said:
I have the same error. How can I fix this pls?
Click to expand...
Click to collapse
Flash the latest official rom then start all over again. Follow the post above you about miflash.

Hello, I've had the same problem, then flashed latest dev rom via MiFlash and it booted, but now after I flash any custom ROM in TWRP i have this issue again and need to reflash chinese ROM. How can I flash any custom rom?

i'm stuck in the same issue. stuck in fastboot and it would not load recovery. any fix?

Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
greendra8 said:
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Click to expand...
Click to collapse
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?

DJPlaya said:
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
Click to expand...
Click to collapse
long time ago now. but i remember at one point having to flash the stock firmware using the mi unlock tool. i also remember trying every single version of twrp and rom until one finally worked. sorry i can't help much but i believe that's how i eventually fixed it.

hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp

Marihot said:
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Click to expand...
Click to collapse
Where do you get these .img files?

iconoclasthero said:
Where do you get these .img files?
Click to expand...
Click to collapse
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder

Marihot said:
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Click to expand...
Click to collapse
Please tell the details for this method

greendra8 said:
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
Click to expand...
Click to collapse
BROOOOOOOOOO HAHAHAHAHAHA I LITERALLY JUST READ YOUR COMMENT AND 10 SECONDS LATER I FLASH THE ROM WITH "CLEAN ALL AND LOCK" Im a f-king dumb bro

Marihot said:
你好，我也经历过同样的事情。
这个方法帮助我摆脱它。
尝试使用 adb 从要在 hh 中安装的 rom 中重新刷新一些文件映像。
将下面的文件从 rom 映像复制到 adb 文件夹
1.system.img（adb >> fastboot flash system system.img中的命令）
2. boot.img（adb 中的命令，如#1，更改 img 文件的名称）直到 #6
3. 供应商.img
4.dtbo.img
5. 自定义.img
6. 杂项.img
7. 现在用adb刷twrp/recovery.img（选择twrp与你要安装的rom兼容）
8. adb 的“fastboot boot recovery.img”
9. twrp刷入rom
Click to expand...
Click to collapse
Thank you, brother

try fastboot set_active a
or fastboot set_active b

Need help cannot re-install twrp or flash to stock rom

Hi everybody
Tried to install a custom rom on my device and it has turned out to be a disaster. I'm completely stuck and have no idea what to do next. Tried everything i could find but i keep having the following problem.
Device: mi k20 davinci
Bootloader: unlocked
TWRP file: twrp-3.3.1-0-davinci.img
ROM: davinci_global_images_V11.0.4.0.QFJMIXM_20200117.0000.00_10.0_global_4c094d085a
TWRP had been succesfully installed but i broke it somehow and now i'm back in the fastboot mode. When trying to re-flash and boot twrp i recieve the following error:
"FAILED (remote: Failed to load/authenticate boot image: Load Error)"
If i try to flash the stock ROM with the miflash tool i receive the error
"Antirollback check error" "error"
if possible i just want to go back to stock and forget about this for now

Post it in K20 and not K20 Pro section.
I didn't know K20 had antirollback protection. Maybe try to flash a newer miui version, maybe a beta ?
Have you also tried "fastboot boot twrp.img" ?

oldbait said:
Hi everybody
Tried to install a custom rom on my device and it has turned out to be a disaster. I'm completely stuck and have no idea what to do next. Tried everything i could find but i keep having the following problem.
Device: mi k20 davinci
Bootloader: unlocked
TWRP file: twrp-3.3.1-0-davinci.img
ROM: davinci_global_images_V11.0.4.0.QFJMIXM_20200117.0000.00_10.0_global_4c094d085a
TWRP had been succesfully installed but i broke it somehow and now i'm back in the fastboot mode. When trying to re-flash and boot twrp i recieve the following error:
"FAILED (remote: Failed to load/authenticate boot image: Load Error)"
If i try to flash the stock ROM with the miflash tool i receive the error
"Antirollback check error" "error"
if possible i just want to go back to stock and forget about this for now
Click to expand...
Click to collapse
Flash Fastboot ROM through Command Prompt. https://in.c.mi.com/thread-334-1-1.html?t=1586384142148

Question Impossible to boot custom recovery

For my new Redmi 9T (EEA ROM, 2010j19sy) i wanted to install an unofficially twrp recovery but i was not able to boot any non-stock recovery out on the web. I also found that other people in this forum have the same problem.
The unlock and everything else worked without problems.
This qoute from GrandTouqe describes my problem exactly:
Rename the file change nothing to me.
As information, when I try in try
Bash:
fastboot boot recovery.img
i get :
Code:
Bash:
FAILED (remote: unknown command)
in fastboot
and
Bash:
FAILED (remote: Unrecognized command boot)
in fastbootd
I've test lineage recovery and that's the same : impossible to boot on other recovery except the stock MI-Recovery 3.0 .
Click to expand...
Click to collapse
My OS is Windows 10 on an x64 intel CPU.
The ADB Fastboot binaries are like 3 weeks old, may they cause this strange behavior?

I figured out that my product is not lime, its lemon now. Can anybody tell me what to do?

Hey !
I've found this one who works in this topic.
But after, I can't install the unofficial ROM that I find here.