Database Users

[FIX] Asus Zenfone 2 Laser ZE550KL Marshmallow update problem, failed to mount /asdf

I have good experience with other phones but this is my first time working with ZE550KL.
So I took my uncle's phone and he asked me to update his phone to the latest firmware to get the VoLTE feature.
He is was on ZE550KL_WW_21.40.1220.1708 which is Marshmallow of the ZEN UI.
I have downloaded the latest firmware from the ASUS website but I couldn't update it because the recovery which came with the marshmallow update is broken.
These are the errors I got
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is what I did, and hope this works for everyone.
Hoping that you already went and searched about the problem over the internet.
These are the things you need to download :
ADB and fastboot
https://drive.google.com/file/d/0B0aDjdU4gTwZZW1HUHhqWnEteXM/view
Recovery image file
https://drive.google.com/open?id=0B0aDjdU4gTwZa1MyUmVPN3BhQjQ
Latest firmware:
https://www.asus.com/in/support/Download/39/1/0/22/ZROQURlyupei1ZQz/32/
1. Download the adb and fastboot drivers. Download the latest firmware and copy it onto your internal storage.
2. Boot into the bootloader.
3. Download the recovery image and paste it into the adb folder.
4. Now type the following command.
Code:
fastboot flash recovery recovery.img
5. This step is very important.
Now, all you have to do is hold the power button and the volume down button to boot into the installed recovery.
Remember that if you restart your phone after step 4, your old recovery(which does not work) will still be there.
6. Now select update from sdcard and select the zip file of the latest firmware you downloaded.
7. It will take at least 10 minutes to install, don't panic if you think the screen froze.
I hope this solves the issues many users are facing.
Feel free to ask questions, I will be very happy to answer.
The recovery we installed is the recovery of Android Lollipop version of the Zen UI ROM.

Thanks. It worked. The only difference is that after flashing the old recovery, my SD card was showing blank. So i selected the adb sideload option and flashed the new build.. Thanks for your guide.

Thanks but few doubts remain. The recovery you used is from Lollipop`s 1.17.40.1503 right?
Can we not do this by installing a temporary recovery image (twrp)?
I have also read elsewhere ( https://devs-lab.com/e-unable-to-mount-asdf-recovery-error-solved.html ) that you would need the boot image too. But your instructions are way too easier and easy to follow. Why don't you use boot image?
If we are using the boot image then which version of it should we use?

hellbraker said:
Thanks but few doubts remain. The recovery you used is from Lollipop`s 1.17.40.1503 right?
Can we not do this by installing a temporary recovery image (twrp)?
I have also read elsewhere ( https://devs-lab.com/e-unable-to-mount-asdf-recovery-error-solved.html ) that you would need the boot image too. But your instructions are way too easier and easy to follow. Why don't you use boot image?
If we are using the boot image then which version of it should we use?
Click to expand...
Click to collapse
Before I tried any of this... First thing I did was boot TWRP and install the lastest firmware.
But I couldn't do so because TWRP doesn't let you flash .img files.
And for the best result it is always better for you to use the official recovery to flash an official firmware.
Because ASUS f***ed up, I needed to install the previous version of the recovery to flash the firmware.
And I'm very happy that my guide worked for you.
Don't forget to give thanks. :laugh:

I haven't tried it yet. So you didn't tamper with boot.img at all. Right?
Also as previously asked what's the build number from which you extracted the recovery.img? Is it from .1503?
My current build is .1708 same as what you worked on. And will data get erased during this process?

How can I boot into the bootloader? is it by unlocking it? or is there any other non-invasive way?
Update: I installed as per your instructions. Device shows "Optimizing app 5 of 51".
Thank you.

Thank you
Thank you sir, this helped me a lot.

recovery link is asking need access plzz help

My Asus Zenfone doesn't boot anymore and doesn't even allow me to factory reset it from the bootloader. How to force reset it??

Error mode: error 11 no recovery, error 2 failed to load

Help
I tried to relock my bootloader but when the device restarted it went straight to error mode.
I managed to boot straight back to full system but whenever I restart it goes back to error mode. I cant enter fastboot or recovery mode.
I sont know what to do now any help
Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Try to boot it again in the full system and from there try to unlock your bootloader.
If you done that, reinstall the software.

How can I unlock bootloader without fastboot? If I attempt to enter fastboot or anything that requires reboot I end up on that screen.

Hmm....
Have you tried rebooting to fastboot using adb?

Johnny TDN said:
Try to boot it again in the full system and from there try to unlock your bootloader.
If you done that, reinstall the software.
Click to expand...
Click to collapse
Johnny TDN said:
Hmm....
Have you tried rebooting to fastboot using adb?
Click to expand...
Click to collapse
I tried but still get to error mode.....I have tried many times

Then i don't know anymore dude. Have you tried reinstalling the firmware using the 3 button method?

elliotn said:
I tried but still get to error mode.....I have tried many times
Click to expand...
Click to collapse
Hello
tested with the toolkit 0.0.0.12.
to see if he recognizes the phone.
he should at least write your serial number.
if that is the case.
you can use DC-unlocker. to open FRP and can be the bootloader.
just an idea.

Dc unlocker needs cash and it doesn t always work.

I am doubting buying DC,unlocker in case,it doesn't work and I will lose money.... I will try toolkit.

3 button upgrade doesn't work either.

I have the same problem after I tried to relock my bootloader using SRKToolHuawei-STABLE-V1.3-20160619 with my bootloader code.
Have you found a solution?
I can boot back into os b394 after I let the battery run out to 0%
I haven't found a way to repair my recovery and fastboot yet because rebooting into fastboot always get's me back to that first error
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)
Then I have to wait for my battery to run out again
Any help to get fast boot and a working recovery back would be appreciated.

Use Huawei multi tool ,then flash system, custom,recovery image ,
If stock recovery opens then use Dload method

shankarjdhv125 said:
Use Huawei multi tool ,then flash system, custom,recovery image ,
If stock recovery opens then use Dload method
Click to expand...
Click to collapse
I got stock recovery back with the warning that my device is unlocked. Now I get stuck at 'Your device is booting now'. After some time it reboots and opens eRecovery which I cannot use.
How do I get anything on my phone to continue with dload and which firmware would you advice me to flash if I finally get there.
Should I, if even possible at the moment, choose an older firmware version?
Edit: Would the original service rom help? Found it here https://forum.xda-developers.com/huawei-p9lite/help/original-service-rom-huawei-p9-lite-vns-t3688120 but my build number seems too high as the version I need only mentions b381 and b383 not the 394 I currently have..

Same problem for me
No way to shutdown the phone, someone have solved?
Now I'm waiting for the battery to full drain

Hi guys i ve made mistake because i wanted to update to latest release media pad m3 but i could not be able to boot to stock recovery after i flash recovery img extracted from update.app and second time i flash recovery2.img to erecovery partition and i got the same issue error Func No 11(recovery image) and Error NO 2 (load failed) . I also put the update.app to dload folder on sd card but update system is not starting i press volume up and down and power button at same time but is not working.I tried also with huawei multitool but is not working is not recognize my device. Please guys is any other solution to fix this ?Thank You!

I just fixed after power off device and then press volume down and plug the usb cable to pc and i was able to recognize my device and i have use huawei multiTool to unbrick my tablet media pad m3 and has work.

Almost the same problem, help please!!!
Hi guys someone can help me? I have a Honor 9 lite(LLD-L31). Android version 8.0
I apologize but I'm a new user and i don't have much practice with modding in general.
I tried to install root permission in my device. I get bootloader unlock code by DC-unlocker and installed TWPR on my device.
When i went in recovery the error " Failed to unmount '/system'(Device or resource busy)" rushed, so I tried to format data in order to give partition available. I tried again to flash file.zip but the search was empty so I downloaded a most recent version(3.2.3) of TWPR in recovery ramdisk.
Now if i try to log into recovery mode appear the same error (Error! func NO 11 / NO 2).
I can do everything aside going in recovery mode. How can I resolve it? Is it possible to reset to factory settings and try again?
I hope I have explained well the problem.

elliotn said:
3 button upgrade doesn't work either.
Click to expand...
Click to collapse
how about this 3 button method??

Astarothkun said:
I got stock recovery back with the warning that my device is unlocked. Now I get stuck at 'Your device is booting now'. After some time it reboots and opens eRecovery which I cannot use.
How do I get anything on my phone to continue with dload and which firmware would you advice me to flash if I finally get there.
Should I, if even possible at the moment, choose an older firmware version?
Edit: Would the original service rom help? Found it here https://forum.xda-developers.com/huawei-p9lite/help/original-service-rom-huawei-p9-lite-vns-t3688120 but my build number seems too high as the version I need only mentions b381 and b383 not the 394 I currently have..
Click to expand...
Click to collapse
Could you write down the steps you took to get back in fastboot for me? I'm having troule geting there myself after draining battery.

I fixed it after nothing else here worked.
So this is mostly so I dont ever forget the solution again, but also to possibly help others.
I also have to say that I had the problem with an P8 Lite, but all my problems matched almost exaclty, so It might help you too.
And a third disclaimer: I have no idea if you can flash the stock firmware without having the bootloader unlocked.
If you dont have it unlocked, try this wonderful updated guide: [Links are disabled for me so google this: "Droidhunter unlock huawei bootloader" and pick the article by droithunter.com]
And yes DC-Unlocker, suprisingly actually works (at least for me) and buying their bootloader unlock code was worth the 4 bucks.
So here is the solution:
1. Somehow, however needed get into fastboot. As I couldn't use the volume/power key combo myself, I somehow force reset the phone, pressing various buttons until I managed to boot into it again. I then used the adb bridge to boot into fastboot (google how to connect adb, then use "adb reboot bootloader" to get into the fastboot menu).
2. Download your phone models default stock rom/Update.app (also google that).
3. Extract the Update.app file.
4. Download and use the HuaweiUpdateExtractor tool and open the Update.app file (google again helps).
5. Select the "09.recovery.img" entry (the one with the green arrow on the left), rightclick and select "extract selected" and save it somewhere where you can find it.
6. Open your Fastboot console on PC (its often the same as the ADB console used before, especially if you use Minimal Fastboot and ADB, which I would recommend).
7. Make sure your phone is in Fastboot mode (not recovery) and connected to the pc.
7.1 Make sure your bootloader is unlocked. It might work with a locked one because youre just flashing stock firmware but eh might break more. Its worth the 4 bucks to unlock the bootloader first. (and yes DC unlocker looks super sketchy but somehow it actually worked for me and wasnt a scam).
8. Flash a custom recovery onto the phone (pretty much the same way you flash twrp, but instead of the twrp image you use the .img file you just extracted from the Update.app; Also dont try flashing twrp directly, it will probably not work).
The command to do so is: "fastboot flash recovery [filepath to the .img file without the brackets]".
9. Use the command "fastboot reboot".
10. If your phone doesnt boot normally, use the key combinations to get into the normal recovery screen and recover from a file or whatever (other guides should work from here).
Extra Steps:
As my recovery image was obviously so broken that even flashing twrp on top of it didnt work until I flashed the original reovery image, I went into my phones settings and did a factory reset. Directly after I installed twrps (see google) and set it up so it had full control. Afterwards I rooted and installed LinageOS cause frick EMUI rn).
Hope this helps anyone. If you have any questions feel free to ask me.

Phone bricked, need help fast

I wanted to reinstall the stock rom (B360). I booted into TWRP and for some reason I wiped System, Dalvik cache, cache and internal memory (I dont know why I did that). Then I installed the Firmware but it failed probably because my frp was locked and I didnt know about it. Then I rebooted and now I cant boot to the system. When I boot into TWRP it just hangs on the TWRP logo and doesnt go on, eRecovery doesn't work. I can boot into fastboot. Its says that phone is unlocked but frp is locked. I hope that there's a way to unbrick my phone without dc-phoenix

DeathBell said:
I wanted to reinstall the stock rom (B360). I booted into TWRP and for some reason I wiped System, Dalvik cache, cache and internal memory (I dont know why I did that). Then I installed the Firmware but it failed probably because my frp was locked and I didnt know about it. Then I rebooted and now I cant boot to the system. When I boot into TWRP it just hangs on the TWRP logo and doesnt go on, eRecovery doesn't work. I can boot into fastboot. Its says that phone is unlocked but frp is locked. I hope that there's a way to unbrick my phone without dc-phoenix
Click to expand...
Click to collapse
Install the stock recovery and then stock ROM. (You can install the stock recovery when your phone is in bootloader mode and you install it by the cmd in Windows)

Tiagohsoares said:
Install the stock recovery and then stock ROM. (You can install the stock recovery when your phone is in bootloader mode and you install it by the cmd in Windows)
Click to expand...
Click to collapse
Sorry for the late reply. Whenever I try to flash the stock recovery it says FAILED (remote: Command not allowed):crying:. I tried both fastboot flash recovery_ramdisk and fastboot flash recovery, neither of them worked.

After doing some more research (like 3+ hours) I think that the error can't be easily fixed:crying:. Some solutions that I've found that may work all involve either disabling USB debugging and then rebooting and re-enabling it or somthing like that which I can't do since I can't boot into the system or relocking and then unlocking my bootloader which I also can't do without dc-phoenix since my frp is locked. Also I don't know if the dload method will work as I can't access the sd card when I plug my phone to the PC. It may be possible to push files there using adb but I'm not sure if it will work even when I get the right files to my sd card. So unless you guys don't have a better solution, I'm probably going to buy the HCU + DC-Phoenix 3 day licens for 20€ (still a lot better then changing my motherboard for 100+€). Also here's the adb window with the error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: I'm not going to buy DC-Phoenix until somebody says that there's no way to fix my device without it. It's so unfortunate that I probably can't fix my phone for free even when things like fastboot, charging and adb are working and bootloader is unlocked.

DeathBell said:
After doing some more research (like 3+ hours) I think that the error can't be easily fixed:crying:. Some solutions that I've found that may work all involve either disabling USB debugging and then rebooting and re-enabling it or somthing like that which I can't do since I can't boot into the system or relocking and then unlocking my bootloader which I also can't do without dc-phoenix since my frp is locked. Also I don't know if the dload method will work as I can't access the sd card when I plug my phone to the PC. It may be possible to push files there using adb but I'm not sure if it will work even when I get the right files to my sd card. So unless you guys don't have a better solution, I'm probably going to buy the HCU + DC-Phoenix 3 day licens for 20€ (still a lot better then changing my motherboard for 100+€). Also here's the adb window with the error.
Edit: I'm not going to buy DC-Phoenix until somebody says that there's no way to fix my device without it. It's so unfortunate that I probably can't fix my phone for free even when things like fastboot, charging and adb are working and bootloader is unlocked.
Click to expand...
Click to collapse
It seems that you need just to perform FRP unlock with HCU client.... After that you can flash twrp, etc....
Also you can try method from @vovan1982
"Small manual: removing frp lock.
If you have frp_lock and have not TWRP. Download in FF (FirmwareFinder) third file of firmware (example: update_full_WAS-L21_hw_ru.zip), unpack. Run DCPhoenix small update.app, and when DC Phoenix open back_door, detach usb-cable. On PC run cmd.exe and flash this frp.img"
Good luck!

Alexxxx1 said:
It seems that you need just to perform FRP unlock with HCU client.... After that you can flash twrp, etc....
Also you can try method from @vovan1982
"Small manual: removing frp lock.
If you have frp_lock and have not TWRP. Download in FF (FirmwareFinder) third file of firmware (example: update_full_WAS-L21_hw_ru.zip), unpack. Run DCPhoenix small update.app, and when DC Phoenix open back_door, detach usb-cable. On PC run cmd.exe and flash this frp.img"
Good luck!
Click to expand...
Click to collapse
I fixed my phone using the 1th method in dc-phoenix already :laugh:, the HCU frp thing didnt work because my device model wasn't supported. And I didn't know where to flash the frp.img file. But now my device is working great:fingers-crossed:.

if someone read this or newers, watch this video: it works for frp lock

Bricked Zenfone 3 ZE552KL - This package is for "WW_Phone" device. This is a ""

Bricked Zenfone 3 ZE552KL - This package is for "WW_Phone" device. This is a ""
I'm handling a bricked Zenfone 3 ZE552KL WW model, but I am unable to flash the stock rom back into the device.
For context, this device has never been unlocked, rooted, and always worked under its original factory Android. As told by the owner, he received an OTA update notification last week and confirmed all prompts to initiate the update. As instructed, he plugged the device to its original charger, left the update running and went by with his day doing other stuff. When he returned, the device was completely OFF with 0% battery. We figured the charging cable disconnected due to a bad connector endpoint, and the phone ran out of juice while the update was running!
The result is a bricked Zenfone unable to boot beyond the ASUS logo. It keeps crashing and gets into a boot loop.
I have tried most of the basic tech support I can give him.
I have downloaded a fresh copy of the official ZE522KL firmware from the ASUS website.
I can boot the phone into recovery, which is still the original ASUS recovery. But as I try to flash the firmware, I get this lovely error message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ERROR: This package is for "WW_Phone" device. This is a "".
I know for a fact this is a WW_Phone device because when I try to flash the JP firmware, the error message is different.
ERROR: This package is for "JP_Phone" device. This is a "WW_Phone".
Already tried "Wipe data/factory reset" and "Wipe cache partition" from the recovery menu, but that didn't help.
Already tried pushing the firmware via "adb sideload" and placing it in a SD card. Those didn't help either.
I am also willing to flash a community ROM, like LineageOS or Mokee, but I first need to unlock the bootloader. I'm running adb and fastboot from Linux, and I can't find a descent tool to unlock using Linux is proving to be a real pain. Every tool seems to be made for Windows only.
So, I'm resorting to anyone here, hoping anyone could give me a light before we send this phone directly to ASUS tech support, not available in our region (we'll need to ship it to another city).
Anything I can try before that? I'm running out of ideas.
Best regards and thanks in advance for any help.

Trying to post a screenshot of the error:
https://i.imgur.com/5RHXM3c.jpg

Flash the latest stock recovery thru fastboot and then flash the latest raw firmware.
Otherwise try launching, not flashing, twrp thru fastboot and then flash any raw firmware with the updater script edited.

wang1chung said:
Flash the latest stock recovery thru fastboot and then flash the latest raw firmware.
Otherwise try launching, not flashing, twrp thru fastboot and then flash any raw firmware with the updater script edited.
Click to expand...
Click to collapse
Since his phone is locked, he can't flash anything except RAW firmware.
---------- Post added at 11:52 AM ---------- Previous post was at 11:41 AM ----------
juliohm said:
Trying to post a screenshot of the error:
https://i.imgur.com/5RHXM3c.jpg
Click to expand...
Click to collapse
Hey juliohm,
Just follow these steps & your device will operate normally
1) Download and install ASUS Flash Tool :
2) Download Latest Oreo RAW
ZE520KL:
ZE552KL:
3) Enter Fastboot Mode (Power + Volume Up)
4) Open ASUS Flash Tool
5) Select device & select firmware (select YES on wipe data tab too)
6) Connect phone to PC
7) Hit Start and wait 10-15 minutes (ignore the error 5 [FRP])
MOD EDIT: PAY-PER-CLICK LINKS REMOVED

Thank you, Saktis_STi. But these are Windows tools and I'm running Ubuntu on my local system. No Linux tools available for this task?

juliohm said:
Thank you, Saktis_STi. But these are Windows tools and I'm running Ubuntu on my local system. No Linux tools available for this task?
Click to expand...
Click to collapse
Check PM

Try unlocking your bootloader using the unofficial way located in the Zenfone 3 forum. It should be doable because you only have to boot into your bootloader. You can then flash a custom recovery, such as TWRP, and go in and wipe data, cache + dalvik, and then install a custom ROM. In your case, it looks like the stock recovery can't detect the device model (WW_Phone), so it's most likely that something is wrong with the system partition.

GrenadeofTacos said:
Try unlocking your bootloader using the unofficial way located in the Zenfone 3 forum. It should be doable because you only have to boot into your bootloader. You can then flash a custom recovery, such as TWRP, and go in and wipe data, cache + dalvik, and then install a custom ROM. In your case, it looks like the stock recovery can't detect the device model (WW_Phone), so it's most likely that something is wrong with the system partition.
Click to expand...
Click to collapse
No need. Flash RAW firmware is enough.

Just a quick follow up.
The owner decided to take it a local assist shop. I don't know what method they used, but they managed to reflash the stock firmware back into the device, and it's working fine again.
Thank you all for the tips. If this was my own device, I would be tinkering a lot more. But the owner decided to play safe and pay for repair in some authorized assistence shop.
Best regards all!

Unlocked, can't be trusted, can only boot system via bootloader

EDIT: I don't think it's verity. I think something more is going on. I tried installing another rom with its own kernel, and the problem did not go away. So what's keeping me from getting rid of this nuissance and booting normally?
I've done some searching around to try to fix this problem, and frankly, I've got a headache now. Ok. I've got my bootloader unlocked, and I've installed TWRP and Magisk. Now I want to disable DM Verity so my device will boot normally. As it is, I have to go into the Bootloader in order to get the system to boot: no other option. Edit: Is it even verity doing this? Is it something else?
The guides for disabling dm verity have not worked. Iinstalled Magisk, and some people said that that would disable dm verity all on its own. It didn't. I installed the no-verity-opt-encrypt thing, hoping that would disable dm verity. I actually tried that option before installing Magisk. It didn't work.
Well, any ideas? Do I have the right dm verity thing? Is there more than one? Did I maybe use the one for the G5 by mistake? How do I get past this annoying thing? Please advise.

I'm not familiar with the layout of the Moto G5, so I can only relate what I've learned on Pixel devices.
I assume this is what you're seeing when you attempt to boot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What this means is that a verification error was encountered during run time. This is a function of Android Verified Boot; more details here.
Disabling dm-verity is generally done by flashing the [icode[vbmeta[/icode] image with the --disable-verity --disable-verification arguments, as such:
Code:
fastboot flash vbmeta <vbmeta image> --disable-verity --disable-verification
However, this may not apply to the Moto G5, as I'm not sure its partition structure is similar to the Pixels. Additionally, this should generally be unnecessary if you're on a stock ROM with a stock kernel.
It seems others have encountered the same problem before. It's rather wise to search before posting. Check out this thread:
Stuck at 'Your device has been unlocked and can't be trusted'. Can't enter recovery
I was flashing a rom and followed all the steps correctly: unlocked bootloader, flashed twrp, rooted and then flashed. Everything worked fine on the first go but the phone app was foreclosing instantly so i rebooted into recovery to wipe data and...
forum.xda-developers.com

No, that's not it. What happens is that when I reboot it tells me:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: N/A
Your device will boot in 5 seconds.
Click to expand...
Click to collapse
And then it boots into recovery.
My device is by no means "stuck". It boots into recovery. In order to actually boot the system, I have to choose the option Reboot > Bootloader. And then when the bootloader comes up, I choose Start, and then the system boots. But this is not what I want my phone to do! I want it to, you know, behave!
There doesn't appear to be a separate vbmeta thing. There's just boot.img. AND when I tried installing a custom rom that came with its own kernel, it did not solve the problem. So something else must be going on here.
And I did everything this guy said to do regarding flashing the stock rom: https://forum.xda-developers.com/t/guide-moto-g5-plus-flashing-stock-firmware-rooting-2021.4205293/
No good. Need more help.

For anyone who goes searching desperately for a solution to this same problem: There is a workaround, and that seems to be the best we can do.
Step 1: Get the raw boot.img from your firmware package.
Step 2: Patch boot.img with Magisk. Copy it to your PC.
Step 3: Get TWRP. But you've gotta get an older version, because it's smaller. Get 3.5.0. It's going to matter in a moment.
Step 4: Reboot to Bootloader (hold Vol- while phone is turning on or rebooting).
Step 5: Use fastboot to flash the modified Boot image to the Recovery partition (fastboot flash recovery <themodifiedbootimage>). It's not where a Boot image is supposed to go, but in this case, it's what needs to happen.
Step 6: Likewise, flash TWRP to the Boot partition (fastboot flash boot <twrp.img>).
So far, that seems to work. Now, when you reboot, your phone will boot into the system like it's supposed to. If you want to launch Recovery, what you now have to do is boot into the Bootloader (see Step 4 above) and choose Start. This would normally start the system, but because TWRP is sitting in the Boot partition, it will launch TWRP instead.
I don't have a guide yet for how to make the Boot partition bigger, so that the latest version of TWRP can comfortably fit into it. And I don't know where this whole problem came from in the first place, and how to fix it the right way. But this is what we've got for now, and as far as I can tell, it works pretty well.
But remember: Your Boot and Recovery images are switched now. So any time you want to make any modifications to either, you have to remember where they are.