Database Info

Boot into recovery from fastboot?

Hello, I have an Honor 6x, with unlocked bootloader, and wanted to install TWRP so I booted into bootloader
and flashed twrp.img via fastboot, but now everytime I want to boot TWRP it just shows the message:
Your device has been unlocked and
can't be trusted.
To learn more, visit:
*some link I can't post cause I'm new here*
Your device is booting now...
and then it is stuck in this state...
could I eventually boot into TWRP directly from bootloader via fastboot?
Please help guys, thanks in advance. :fingers-crossed:

What version of EMUI are you on? If you're on the 7.0 beta there isn't a working twrp for it.

jarebear603 said:
What version of EMUI are you on? If you're on the 7.0 beta there isn't a working twrp for it.
Click to expand...
Click to collapse
Indeed, i am on Nougat, is there any way to downgrade?

pt_2001 said:
Indeed, i am on Nougat, is there any way to downgrade?
Click to expand...
Click to collapse
I know for my device BLN-L24 there is instructions on the honor website on how to downgrade.

jarebear603 said:
I know for my device BLN-L24 there is instructions on the honor website on how to downgrade.
Click to expand...
Click to collapse
Hm, can't find it. Where exactly are these instructions?

Hello. Replying here as I don't need a new thread for a very similar issue.
Brand new 6x with EMUI 4. Unlocked bootloader successfully. Using adb/fastboot tool I boot into bootloader, then flash my twrp img. For some reason this goes fine with no errors but takes less than two seconds (cause for concern?).
Now from this point is where I am having trouble. Regardless of what I do, the phone only boots into the EMUI recovery screen. I am aware of holding the volume up key on the first boot after flashing twrp so that it won't be overwritten. I have rebooted the phone manually and also through fastboot while holding the volume up button.
In a new city and only internet I have is thru my phone so this process is really slow due to all the restarts etc. Thanks in advance for the help!

pt_2001 said:
Hello, I have an Honor 6x, with unlocked bootloader, and wanted to install TWRP so I booted into bootloader
and flashed twrp.img via fastboot, but now everytime I want to boot TWRP it just shows the message:
Your device has been unlocked and
can't be trusted.
To learn more, visit:
*some link I can't post cause I'm new here*
Your device is booting now...
and then it is stuck in this state...
could I eventually boot into TWRP directly from bootloader via fastboot?
Please help guys, thanks in advance. :fingers-crossed:
Click to expand...
Click to collapse
i have the same problem with my Honor 6X (BLN-L21) but my phone is stuck at this screen. boot normally, i get that screen. fastboot/rescue mode, i get that screen. recovery, i get that screen. erecovery, i get that screen. aaaand twrp recovery. i get that screen.
also my phone does some weird stuff with the battery level.

Android Nougat and TWRP 3.1.0-2 berlin
MintCrystal556 said:
i have the same problem with my Honor 6X (BLN-L21) but my phone is stuck at this screen. boot normally, i get that screen. fastboot/rescue mode, i get that screen. recovery, i get that screen. erecovery, i get that screen. aaaand twrp recovery. i get that screen.
also my phone does some weird stuff with the battery level.
Click to expand...
Click to collapse
Same problem here. I have a Honor 6x (BLN-L21) with Nougat on it (Build BLN-L21C432B360), unlocked it with the unlock pwd and tried to flash the TWRP (twrp-3.1.0-2-berlin.img) with 'fastboot flash recovery twrp-3.1.0-2-berlin.img'. After that I get always the same message after reboot or if I try to enter the recovery mode.
Any suggestions?
Thank you

Hi there,
I have found it. To get the TWRP Screen I had to press all 3 Buttons (Volume Up, Volume Down and Power) at startup.
Hope this helps.

Sadly this doesn't work here, on a BLN-L21C432B130 with EMUI 4.x and Android 6.x
3 Button start method brings up always the EMUI recovery screen.
Power Button + Volume up Button works fine here with all TWRP versions up to 3.1.0-0, but never on a newer one.
Additional hint: It works only if the USB cable isn't plug into the device and if the phone was powered down before. That must me the reason why I never get that up, if I'm rebootin using the command $ fastboot reboot cause for this the cable connection has to be used

@all who stuck in bootscreen...flash THIS TWRP...

[LG G4 H815] Just need to reboot into recovery directly...
I have kinda the same problem: I flashed TWRP and a friend of mine told me that I need to reboot into recovery directly after flashing TWRP because otherwise the system replaces TWRP again when I type "fastboot reboot". The problem is I cant shutdown the phone and also the key combination of the LG G4 is not rlly working, I tried it dozens of times on my other one... Is there ANY other way of booting to recovery from bootloader / fastboot? Thanks in advance!
P.S.: I read something about "boot twrp.img"... Is that an option or does it just also flash TWRP?

I somehow broke TWRP

I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.

mattlokk said:
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
Click to expand...
Click to collapse
Did you set:
Allow oem unlock in dev opt.
Fastboot protocol into BL?
Twrp app & manager need root to work.

Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link

thanks for the help, i'll try and work through this soon.

fpozar said:
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
Click to expand...
Click to collapse
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.

mattlokk said:
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
Click to expand...
Click to collapse
Okay so I'm guessing you have stock ROM.
To flash TWRP you have to enter fastboot mode (vol down + power I believe) and flash the twrp image with fastboot flash recovery twrp.img (rename the shield tablet twrp to just twrp.img and place it into your easy adb and fastboot folder)
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck

fpozar said:
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
Click to expand...
Click to collapse
Agreed. This is probably what is happening (as described on the TWRP webpage here:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Alternately, immediately rooting (flash SuperSU or Magisk) right after flashing TWRP, will prevent TWRP from being replaced with stock recovery.
Although the inconsistent fastboot connection, and how much trouble you had flashing TWRP initially, is a bit worrisome. Try using a different cable (maybe the one you are using is not connecting well?) try another USB port on the computer, and don't use a USB hub (connect direct to the PC).

Well, like they say: persistence is key. I kept pushing and trying new things until eventually.... I bricked the device. No, not really, it's working great now on LineageOS.
Thanks again to everyone who helped me out :good:. I'm still not sure exactly what caused TWRP to stop working on my device, however following this guide helped me fix it: https://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
The "flash-all.bat" restored everything to stock (including the recovery mode) and after that I was able to flash the latest TWRP and install Lineage.

Boot brick - Can't power off, can't get to erecovery or recovery after rollback

Hey guys, my Honor is in brick state. I pushed a rollback package while I was in marshmallow (but with wrong ROM, so I was trying to rollback again and retry the procedure) and the phone got stuck in Honor blue screen at loop.
It won't let me power off, it justs turns on again. All button combinations won't work apparently. I can't get to recovery or e-recovery.
I tried depleting the battery. But as soon as I connect to the charger, it powers on. If I try the button combination before putting charge, it also doesn't work.
After the first successful rollback to MM, I think the bootloader got locked.
adb and fastbook can't seem to list the device.
I can get to fastboot and rescue mode, but I don't know the procedure from there.
So, is this a unsolvable brick? Or is there anything else that can be done to save this phone?
Thanks a lot for your feedback.

use dc unlocker to flash unlock bootloader and after dc flasher

valp88 said:
Hey guys, my Honor is in brick state. I pushed a rollback package while I was in marshmallow (but with wrong ROM, so I was trying to rollback again and retry the procedure) and the phone got stuck in Honor blue screen at loop.
It won't let me power off, it justs turns on again. All button combinations won't work apparently. I can't get to recovery or e-recovery.
I tried depleting the battery. But as soon as I connect to the charger, it powers on. If I try the button combination before putting charge, it also doesn't work.
After the first successful rollback to MM, I think the bootloader got locked.
adb and fastbook can't seem to list the device.
I can get to fastboot and rescue mode, but I don't know the procedure from there.
So, is this a unsolvable brick? Or is there anything else that can be done to save this phone?
Thanks a lot for your feedback.
Click to expand...
Click to collapse
It's easy. I had a similar problem too. Just when your phone attempts to boot, hold the Volume Down button and immediately connect it to the PC (within 1-2 second). It should go into fastboot mode. Now, open Huawei Multi Tool and unlock your bootloader then use the tool to unbrick your phone, start with flashing stock recovery and then the correct firmware.

SirDarknight said:
It's easy. I had a similar problem too. Just when your phone attempts to boot, hold the Volume Down button and immediately connect it to the PC (within 1-2 second). It should go into fastboot mode. Now, open Huawei Multi Tool and unlock your bootloader then use the tool to unbrick your phone, start with flashing stock recovery and then the correct firmware.
Click to expand...
Click to collapse
Thanks for repying. I unlocked my bootloader through fastboot and I'm trying to get multi-tool now!
i'm getting 404 from xda for the download link though.

SirDarknight said:
It's easy. I had a similar problem too. Just when your phone attempts to boot, hold the Volume Down button and immediately connect it to the PC (within 1-2 second). It should go into fastboot mode. Now, open Huawei Multi Tool and unlock your bootloader then use the tool to unbrick your phone, start with flashing stock recovery and then the correct firmware.
Click to expand...
Click to collapse
I flashed extracted and flashed images for B131 and B360, without luck. Stuck on the unlocked warning now: "Your device is booting now".
I can't seem to get to erecovery. Please let me know if you have any ideas.

valp88 said:
I flashed extracted and flashed images for B131 and B360, without luck. Stuck on the unlocked warning now: "Your device is booting now".
I can't seem to get to erecovery. Please let me know if you have any ideas.
Click to expand...
Click to collapse
If you're stuck on "Your device is booting now". This probably means your recovery is screwed. Don't worry, flash stock recovery and erecovery using Multi-Tool.
Then try the dload method. If the problem persists, then flash the correct TWRP then use HuRUpdater to flash the ROM you want. This will definitely fix the issue.

SirDarknight said:
If you're stuck on "Your device is booting now". This probably means your recovery is screwed. Don't worry, flash stock recovery and erecovery using Multi-Tool.
Then try the dload method. If the problem persists, then flash the correct TWRP then use HuRUpdater to flash the ROM you want. This will definitely fix the issue.
Click to expand...
Click to collapse
The recovery images from Multi-Tool servers seem to work! Thanks a lot. I was able to get to erecovery, now I'll proceed as decribed by you! :good::good::good:
Edit: dload failed at 99%, but I was able to factory reset and get to the system after all!

strange... brick? (SOLVED)

Hello friends
I have a problem, to see if you can help me
I was installing a custom rom, and when I tried to install the twrp, I did not get it
ADB apparently performs the process well, but when trying to enter twrp, it enters the recovery stock
the problem is that I do not have an operating system or access to twrp, so I do not know how to recover the phone
by not having access to twrp, it does not help me HWOta or Huru Updater ...
I have access to bootloader and to the recoveries of huawei
before the disaster was in oreo
The bootloader is unlocked
any ideas?

You want to flash TWRP correct? Well first I want you to confirm me following things.
What recovery are you using. You need an Oreo Compatible TWRP. Try the one in Elemental ROM thread in Honor 6X Roms.
What command are you using. This is the most common mistake people make. Just a reminder the command to flash TWRP recovery on EMUI 8 is :-
fastboot flash recovery_ramdisk RECOVERY-V2.img
RECOVERY-V2.img is the name of TWRP you will download from above-mentioned thread.
Now if you are doing all of the above, and still no success, tell me what the Command Prompt says when you try to flash. After you flash try to manually boot into TWRP by holding Volume Up and Power. Luck.

Mannan Qamar said:
You want to flash TWRP correct? Well first I want you to confirm me following things.
What recovery are you using. You need an Oreo Compatible TWRP. Try the one in Elemental ROM thread in Honor 6X Roms.
What command are you using. This is the most common mistake people make. Just a reminder the command to flash TWRP recovery on EMUI 8 is :-
fastboot flash recovery_ramdisk RECOVERY-V2.img
RECOVERY-V2.img is the name of TWRP you will download from above-mentioned thread.
Now if you are doing all of the above, and still no success, tell me what the Command Prompt says when you try to flash. After you flash try to manually boot into TWRP by holding Volume Up and Power. Luck.
Click to expand...
Click to collapse
thanks for your reply
Yes, I know the commands, and it's even the same recovery, from KingOfMezi
as I comment, he performs the process well:
PS C: \ adb>. \ Fastboot flash recovery_ramdisk RECOVERY-V2.img
Sending 'recovery_ramdisk' (9100 KB)............................................. OKAY [0.328s]
Writing 'recovery_ramdisk'........................................................................ OKAY [0.125s]
Finished. Total time: 0.516s
PS C: \ adb>
but when starting the phone with power + vol+ (releasing power when vibrating and without releasing it, I tried both ways) starts the recovery stock
the most curious thing is that I had done it more times, and I never had any problem with that, in fact, the last thing I did was in the twrp

That's odd. Try to reboot after flashing TWRP. Once you flash it instead of manually booting into TWRP type
fastboot reboot
Now when the device shows device has been unlocked message press Volume up to enter erecovery. From there turn off phone and then boot into TWRP by holding Power and Volume Up. Keep holding it until you see your device is booting now... Screen.
Alternatively try to use dload to restore the system.

about dload I have a doubt.
Being debranded as l22 and having installed oreo, where do I get update.zip? of a ROM l22 oreo, or of the l21 that corresponds to my device?

Download L22 Oreo from Firmware Finder website or Windows App

solved use the bat of kingofmezi, Elementary Kernel + ramdisk.zip.
this made the recovery disappear (if you tried to access, a screen appeared similar to when we accessed fastboot, saying there is no recovery) and then flashed twrp correctly. thanks for your help

You are in Elemental v2. Do you mind if I ask for a review. Was it a complete flash or in complete. i.ewas the wallpaper when you first booted Blue&Black or Pink one.

Mannan Qamar said:
You are in Elemental v2. Do you mind if I ask for a review. Was it a complete flash or in complete. i.ewas the wallpaper when you first booted Blue&Black or Pink one.
Click to expand...
Click to collapse
unfortunately I could not prove it. when flashing the bat, I only managed to recover twrp, and then I was able to return to stock, I did not dare to try it again out of fear (I feel the delay, I could not enter before due to personal problems)

vicent76 said:
solved use the bat of kingofmezi, Elementary Kernel + ramdisk.zip.
this made the recovery disappear (if you tried to access, a screen appeared similar to when we accessed fastboot, saying there is no recovery) and then flashed twrp correctly. thanks for your help
Click to expand...
Click to collapse
Where can i find the elemental kerrnel+recovery.zip....I am not able to find it in official thread

leagoo t5 wont boot after unlocking bootloader

Had a bad idea this morning and decided to try to root the phone, leagoo t5. The last time Im going to go messing with a phone that wasnt broken! after spending 10hrs trying to sort it! I downloaded adb tools and and twrp. I unlocked the bootloader with fastboot and installed twrp. However when I rebooted the phone it just booted straight into twrp. I cant get it to boot normally. I reinstalled the firmware but it will still not boot. I can get into recovery and factory modes but thats it. what can I do? Thanks

pcfreeze said:
Had a bad idea this morning and decided to try to root the phone, leagoo t5. The last time Im going to go messing with a phone that wasnt broken! after spending 10hrs trying to sort it! I downloaded adb tools and and twrp. I unlocked the bootloader with fastboot and installed twrp. However when I rebooted the phone it just booted straight into twrp. I cant get it to boot normally. I reinstalled the firmware but it will still not boot. I can get into recovery and factory modes but thats it. what can I do? Thanks
Click to expand...
Click to collapse
Have you tried factory resetting in recovery?

ktmom said:
Have you tried factory resetting in recovery?
Click to expand...
Click to collapse
Yes I did. No Joy. When I power on I just get the leagoo logo coming on and off repeatedly. Pressing the power button then will not turn the phone off again. I can switch it off by pressing vol- and pwr together though.
Is the problem caused by unlocking the bootloader with fastboot or that the firmware I installed is not suiting? Rebooting the phone after unlocking the bootloader before reflashing the firmware caused the leagoo logo to come on and off repeatedly accompanied by this message in very small text "Orange State - Your device has been unlocked and can't be trusted, Your device will boot in 5 seconds". After flashing the firmware with Sp Flash Tool this message is not being shown. Does reflashing firmware undo the action of unlocking the bootloader?

What your are describing is a bootloop. It sounds like the device can not find the system kernel to boot to. Did you boot the device after unlocking but before doing anything else?
Where did you get the TWRP recovery from?
Isn't this a mediatek chipset? If so, I think you need to use SP Flash Tool*to install.
I would look for a stock ROM for this device to revert to.
I'm not experienced on mediatek devices, but maybe @SubwayChamp could help.

pcfreeze said:
Yes I did. No Joy. When I power on I just get the leagoo logo coming on and off repeatedly. Pressing the power button then will not turn the phone off again. I can switch it off by pressing vol- and pwr together though.
Is the problem caused by unlocking the bootloader with fastboot or that the firmware I installed is not suiting? Rebooting the phone after unlocking the bootloader before reflashing the firmware caused the leagoo logo to come on and off repeatedly accompanied by this message in very small text "Orange State - Your device has been unlocked and can't be trusted, Your device will boot in 5 seconds". After flashing the firmware with Sp Flash Tool this message is not being shown. Does reflashing firmware undo the action of unlocking the bootloader?
Click to expand...
Click to collapse
Then to unlock bootloader is not normal that Android refuses to boot normally but when you flash a custom recovery or modify other partition this usually could happen so either or both you have to do a factory resetting/format data as @ktmom said or/and flash a kind of DM-verity for your device, this last avoids that bootloader checks the integrity of the partitions and can boot normally to system.
The warning message is normal then to unlock bootloader and reflashing the stock rom doesn´t relock it, you have to relock it at similar way that you unlocked it via fastboot command, most commom is "fastboot oem relock" but there are other variants and keep in mind that you have to return completely to stock before to apply it.

SubwayChamp said:
Then to unlock bootloader is not normal that Android refuses to boot normally but when you flash a custom recovery or modify other partition this usually could happen so either or both you have to do a factory resetting/format data as @ktmom said or/and flash a kind of DM-verity for your device, this last avoids that bootloader checks the integrity of the partitions and can boot normally to system.
The warning message is normal then to unlock bootloader and reflashing the stock rom doesn´t relock it, you have to relock it at similar way that you unlocked it via fastboot command, most commom is "fastboot oem relock" but there are other variants and keep in mind that you have to return completely to stock before to apply it.
Click to expand...
Click to collapse
I relocked the boot loader with the command "fastboot flashing lock". small white text dialogue on phone screen stated bootloader was locked successfully. rebooted phone then and it was still stuck in the boot loop. For a few seconds in between the leagoo logo a strange circular graphic was displayed on the phone with word "erasing" under it. What does this mean?
Can you tell me more about how to flash DM-verity?

pcfreeze said:
I relocked the boot loader with the command "fastboot flashing lock". small white text dialogue on phone screen stated bootloader was locked successfully. rebooted phone then and it was still stuck in the boot loop. For a few seconds in between the leagoo logo a strange circular graphic was displayed on the phone with word "erasing" under it. What does this mean?
Can you tell me more about how to flash DM-verity?
Click to expand...
Click to collapse
Ok, then to relock bootloader I guess that you did successfully boot to system again, right?
When you unlocked bootloader first then device is formatted to avoid a new user can access to the user´s data and when you relock it again the same happens.
As for DM-verity, newer devices strictly since nougat can´t boot to system after any partition was modified like happened when you flashed a custom recovery on it, here is when DM-verity can be useful, is used to avoid bootloader checks the integrity and allow a modified device can perform a reboot and more custom actions not officially permitted. You had to flash it through a custom recovery, sometimes flashing only Magisk is enough but not always.

You *might* be able to use this universal dm-verify script. It can be flashed only in a custom recovery and I'm not certain that is available to you.

ktmom said:
You *might* be able to use this universal dm-verify script. It can be flashed only in a custom recovery and I'm not certain that is available to you.
Click to expand...
Click to collapse
Good news and bad news! I got the phone to boot! I reinstalled twrp and the "magisk","no verity opt encrypt" and "disable dm verity" zips from the ext sdcard with fastboot. Twrp stated the zips installed ok but there were also some red line failure lines in the dialogue as they were being installed. I rebooted the phone via fastboot but this just resulted in it booting direct to twrp as before. I tried normal boot from twrp but it still booted straight back to twrp. I then tried selecting normal boot from the fastboot, normal, recovery option menu accessed on the Leagoo T5 by powering off the phone and then pressing the pwr and vol+ buttons together but this still resulted in it booting straight to twrp. I then decided to uninstall twrp by flashing the stock firmware recovery image to try to boot from stock recovery. I did same and rebooted from fastboot and it booted to system.
The bad news is there is an imei failure message and the sim is not connecting to the network.I googled imei failure and saw that its can happen when firmware is changed. I installed the "mobileuncle" app but according to a youtube video I watched, when I tap "Engineer Mode" there should be 2 further options available, one being MTK Mode. I am only getting one option "Engineering Mode (Android) which when I select just results in being returned to the previous menu. please say this is not a major problem!

@pcfreeze you quoted me, but as I said earlier, I'm not experienced with mediatek devices. You'd be better off quoting @SubwayChamp

pcfreeze said:
Good news and bad news! I got the phone to boot! I reinstalled twrp and the "magisk","no verity opt encrypt" and "disable dm verity" zips from the ext sdcard with fastboot. Twrp stated the zips installed ok but there were also some red line failure lines in the dialogue as they were being installed. I rebooted the phone via fastboot but this just resulted in it booting direct to twrp as before. I tried normal boot from twrp but it still booted straight back to twrp. I then tried selecting normal boot from the fastboot, normal, recovery option menu accessed on the Leagoo T5 by powering off the phone and then pressing the pwr and vol+ buttons together but this still resulted in it booting straight to twrp. I then decided to uninstall twrp by flashing the stock firmware recovery image to try to boot from stock recovery. I did same and rebooted from fastboot and it booted to system.
The bad news is there is an imei failure message and the sim is not connecting to the network.I googled imei failure and saw that its can happen when firmware is changed. I installed the "mobileuncle" app but according to a youtube video I watched, when I tap "Engineer Mode" there should be 2 further options available, one being MTK Mode. I am only getting one option "Engineering Mode (Android) which when I select just results in being returned to the previous menu. please say this is not a major problem!
Click to expand...
Click to collapse
It could be many reasons why device didn´t boot to system. Then to flash it you had to format data + flash DM-verity. Also is possible that this TWRP version is not completely suitable for your device or is unable to mount/unmount partitions correctly, you have to check from where you downloaded it and if some users are experiencing similar issues with it.
As per you IMEI lost, better is ever take a backup of the NVRAM through TWRP before to go further then it´ll be easy to recover it. In almost all firmwares for mediatek devices you´ll fnd inside the zips SPFT and SN Writer that is to recover your IMEI. Your IMEI is not really lost only got actually covered by blank codes due to a bad/incorrect flashing/wrong sequence firmware, so be careful what you do with Mobile Uncle tool if you´re not experimented with otherwise you´ll lost permanently.

SubwayChamp said:
It could be many reasons why device didn´t boot to system. Then to flash it you had to format data + flash DM-verity. Also is possible that this TWRP version is not completely suitable for your device or is unable to mount/unmount partitions correctly, you have to check from where you downloaded it and if some users are experiencing similar issues with it.
As per you IMEI lost, better is ever take a backup of the NVRAM through TWRP before to go further then it´ll be easy to recover it. In almost all firmwares for mediatek devices you´ll fnd inside the zips SPFT and SN Writer that is to recover your IMEI. Your IMEI is not really lost only got actually covered by blank codes due to a bad/incorrect flashing/wrong sequence firmware, so be careful what you do with Mobile Uncle tool if you´re not experimented with otherwise you´ll lost permanently.
Click to expand...
Click to collapse
I got into engineering mode via dialer code. CDS option was missing from connectivity. I installed https://m.apkpure.com/cds-mobile/com.doubleapaper.cds.cds_mobile but CDS is still missing from engineering mode

pcfreeze said:
I got into engineering mode via dialer code. CDS option was missing from connectivity. I installed https://m.apkpure.com/cds-mobile/com.doubleapaper.cds.cds_mobile but CDS is still missing from engineering mode
Click to expand...
Click to collapse
Sorry, just realised that this is the wrong app! nothing to do with cds in engineering mode! I triedhttps://apkcombo.com/common-data-service/com.mediatek.connectivity/
but got message that the file was corrupted and it would not install