Database Info

bricked from downgrade

I tried to downgrade from L29C185B320 to L29C185B200 however I'm now faced with the following:
(Prior to the downgrade I did flash the B320 recovery.img as I was on TWRP before)
On boot, Huawei logo displays then display goes black. Still powered on but not displaying anything
eRecovery is accessible, tried wiping cache but no change, also tried factory reset. The "download latest version and recovery" option isn't possible, "getting package info failed"
Can't access device over ADB as it doesn't detect in "adb devices"
Bootloader is now locked (was unlocked before)
I can "fastboot reboot" but no other command works due to bootloader locked
I can do Vol Up+Down reset but takes me right back to blank screen after installing. I've tried with various update versions (B162, B180, B200, even going back to B320) but its the same result every time.
Afraid I now have a brick, would appreciate any help I can get.

MuPp3t33r said:
I tried to downgrade from L29C185B320 to L29C185B200 however I'm now faced with the following:
(Prior to the downgrade I did flash the B320 recovery.img as I was on TWRP before)
On boot, Huawei logo displays then display goes black. Still powered on but not displaying anything
eRecovery is accessible, tried wiping cache but no change, also tried factory reset. The "download latest version and recovery" option isn't possible, "getting package info failed"
Can't access device over ADB as it doesn't detect in "adb devices"
Bootloader is now locked (was unlocked before)
I can "fastboot reboot" but no other command works due to bootloader locked
I can do Vol Up+Down reset but takes me right back to blank screen after installing. I've tried with various update versions (B162, B180, B200, even going back to B320) but its the same result every time.
Afraid I now have a brick, would appreciate any help I can get.
Click to expand...
Click to collapse
I have same problem...
And cant find any solution for adb commands work again. I don't know where is the problem.Tryed everythink. And nothing. Maybe problem is FRP lock, but in bootloader its nothing showing. Just phone unlocked. I saw many users have this problem.

delete

Same problem
Hi guys,
I'm new here and I have the same problem after my try to downgrade from EMUI5 to EMUI4.1 Mashmallow.
My Phone bootload twice and after my only choice is to use eRecovery taht don't work. I tried to use italian swiss knife nad the other from Asia to unlock the phone but it don't work at all, I got the same message Failed : remote command unaviable, or something like that.
Please can you help me to recover my phone?
Thank you in advance for all your suggestions

lecsolo said:
Hi guys,
I'm new here and I have the same problem after my try to downgrade from EMUI5 to EMUI4.1 Mashmallow.
My Phone bootload twice and after my only choice is to use eRecovery taht don't work. I tried to use italian swiss knife nad the other from Asia to unlock the phone but it don't work at all, I got the same message Failed : remote command unaviable, or something like that.
Please can you help me to recover my phone?
Thank you in advance for all your suggestions
Click to expand...
Click to collapse
Try by dloadl UPDATE.APP (C185B521) from Update.zip.
After re-try rollback

pescixx79 said:
Try by dloadl UPDATE.APP (C185B521) from Update.zip.
After re-try rollback
Click to expand...
Click to collapse
Thank you, is the right update for an EU phone the C185B521?

lecsolo said:
Thank you, is the right update for an EU phone the C185B521?
Click to expand...
Click to collapse
I was on C185B521, flashed Rollback and tryed to downgrade to C185B180. Had ISSUE.
I extracted Update.app from C185B521 zip and Flashed (dload) (had keyboard issue and other not working)
Try to rollback again and alla woked fine.

pescixx79 said:
I was on C185B521, flashed Rollback and tryed to downgrade to C185B180. Had ISSUE.
I extracted Update.app from C185B521 zip and Flashed (dload) (had keyboard issue and other not working)
Try to rollback again and alla woked fine.
Click to expand...
Click to collapse
Ok I will try this, hope it will work on my phone
Thanks for your help

Problem solved this morning I try to boot with vol up and start bouton pressed, when wipe/factory reset appears and selected, then press ok. After that my phone reboot on EMUI 4.1/mashmallow and work fine.
Thank you very much for your help, much appreciated.

r4ason said:
I have same problem...
And cant find any solution for adb commands work again. I don't know where is the problem.Tryed everythink. And nothing. Maybe problem is FRP lock, but in bootloader its nothing showing. Just phone unlocked. I saw many users have this problem.
Click to expand...
Click to collapse
Sigh, that's a pity. I don't think it would be an frp problem in my case as I have my Google account details to login, rather just that it's failing to boot the os partition. What I've gathered from this is that something went wrong with the firmware installation and now that its relocked the bootloader there's no way to push the files into place with adb/fastboot.
Nevertheless, my device is still fairly new so I've sent it back to the supplier, will wait for their response...

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?

Honor 6x (BLN-L24) Twrp overwritten by Default Bootloader

I have a Honor 6x (BLN-L24) with EMUI 5+, Android Nougat, all updated. It is the U.S. edition. I unlocked the Bootloader, installed ADB / Fastboot tools and can flash the correct TWRP recovery image (3.1.1-0-berlin.img) but everytime I try to reboot into recovery, the standard EMUI recover overwrites TWRP and I just end up in the EMUI recovery.
I've looked at every forum I can find, articles, etc... but can't wrap my head around this one. If anyone with a similar experience and/or with a solution could help, I'd be most grateful.
Thank you!

I agree with with Rommco05. He IS correct, as I wondered the same thing till I realized to try unplugging it. Also make sure its the Power AND up buttons at same time. If you happen to hold only the up button it will take you to the erecovery feature where it trys hooking to WiFi for updates , which wont help you either.

Still doesn't work
Thanks for the responses. Unfortunately, unplugging doesn't do it either with the key combination you suggested. The following article is helpful for key combinations but alas, it still won't load into TWRP.
It is really strange as I can't even get past "Your device has been unlocked and can't be trusted" screen now. It just stays there...
Super frustrating. I didn't know if it had anything to do with my model being the BLN-L24 US version. I bought it at BestBuy unlocked.
Also, when I try to download "Latest Version and Recovery" from "Huawei eRecovery", I'm getting "Getting package info failed". I

Try OpenKirin twrp from recoveries section here on 6X forums

etmartinkazoo said:
Super frustrating. I didn't know if it had anything to do with my model being the BLN-L24 US version. I bought it at BestBuy unlocked.
Click to expand...
Click to collapse
That's not the cause. My phone is also a BLN-L24 purchased from Best Buy and I have no issues using TWRP. What did you do after you install TWRP? Did you let the phone just reboot or did you try to go into TWRP before rebooting?
This is straight from TWRP website:
"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."

Key combination timing?
galapagos said:
That's not the cause. My phone is also a BLN-L24 purchased from Best Buy and I have no issues using TWRP. What did you do after you install TWRP? Did you let the phone just reboot or did you try to go into TWRP before rebooting?
This is straight from TWRP website:
"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."
Click to expand...
Click to collapse
This is helpful, thank you. I found a page "Key Combinations Clarified for Honor 6x" which has a number of key combinations but nothing is helpful in my case that I know of. Do I use these key combinations imediately after the flash?
Is there a specific tutorial or guide that was helpful for you? I'd be grateful for any further assistance.
Thanks.

Rommco05 said:
You need enter to recovery? TWRP?
Click to expand...
Click to collapse
That is the problem, I'm unable to enter TWRP after flashing it, unplugging the usb cable, holding power/volume up...

Finally got Twrp installed. Rooted and installed custom Rom (lineageos) but when I reboot after flash screen, it's just blank...

If I were you, I would go completely back to stock and start over. Once you fastboot flash TWRP, it is imperative that you reboot back into TWRP before booting into the OS. Also, bootloaders don't overwrite recoveries. They are separate partitions, so your title is a bit misleading.
Regardless, you must still have stock recovery on your device since it is "defaulting" to that instead of TWRP. Like I said, it is extremely important to boot into recovery after you first flash it.
fastboot flash recovery recovery.img
let it do it's thing.
fastboot reboot recovery OR you can do it manually in TWRP right after the flash.

Have you tried rebooting to recovery from the system?
Connect your device to your computer, enable USB Debugging, and run
Code:
adb reboot recovery
from Windows CMD or Linux Shell, or any other one you prefer.
If this works, then you are doing the recovery key combination wrong.
Cheers

I'm having the same issue as OP. I have a BLN-L24 from Best Buy in the US. Reverted to emui 4.1 and android 6, unlocked bootloader, flashed twrp-3.2.1-0-berlin.img, and it keeps booting into huawei erecovery.
I didn't get any info on what the OP actually did to get twrp installed.
FWIW, there is no "fastboot reboot recovery"
FWIW2, you can't turn off the honor 6x from the bootloader. the best you can do is a hard reboot.

etmartinkazoo said:
That is the problem, I'm unable to enter TWRP after flashing it, unplugging the usb cable, holding power/volume up...
Click to expand...
Click to collapse
I'm having your exact same problem. I can get into fastboot mode, flash TWRP berlin, but I cannot enter TWRP after flash. It just goes back to the normal warning screen "this phone is unlocked", boot normally or go to EMUI recovery.
What worked for you?

hexag1 said:
I'm having your exact same problem. I can get into fastboot mode, flash TWRP berlin, but I cannot enter TWRP after flash. It just goes back to the normal warning screen "this phone is unlocked", boot normally or go to EMUI recovery.
What worked for you?
Click to expand...
Click to collapse
RedSkull fixed my problem!

[Help] Bootloop after re-locking Bootloader!

After reading the news that a new method had been found for Verizon/EE-UK Google Pixel (Sailfish) Phones to unlock the Bootloader - I decided to do so and then proceed to flash Magisk for root and other benefits however as there was recently a new update which was showing as 'Failed to Install'.
Of cause I wanted to update the device so I attempted to re-lock the Bootloader using 'fastboot flashing lock' and proceeding to select Yes from the prompt. Which seemed to be acceptable and worked to lock the Bootloader.
Now my phone is stuck in a crazy boot-loop where by the phone will turn on - flash the Google logo on the white background for a split second then shut itself down and repeat.
Does anybody have any tips for me to recover the phone from this awful state?

Mr Ian said:
After reading the news that a new method had been found for Verizon/EE-UK Google Pixel (Sailfish) Phones to unlock the Bootloader - I decided to do so and then proceed to flash Magisk for root and other benefits however as there was recently a new update which was showing as 'Failed to Install'.
Of cause I wanted to update the device so I attempted to re-lock the Bootloader using 'fastboot flashing lock' and proceeding to select Yes from the prompt. Which seemed to be acceptable and worked to lock the Bootloader.
Now my phone is stuck in a crazy boot-loop where by the phone will turn on - flash the Google logo on the white background for a split second then shut itself down and repeat.
Does anybody have any tips for me to recover the phone from this awful state?
Click to expand...
Click to collapse
Man, when you lock the bootloader you need to make sure you're 100% back on stock without any modifications flashed. Seems to me you tried locking while having magisk flashed.
Try to see if you're able to get into recovery. Get into bootloader menu by pressing power button+volume down and the press volume upp until you get to recovery and then press power button. If you're able to get into recovery then download the full ota image for Google pixel sailfish from here https://developers.google.com/android/ota and then while you're in there should be an option to update using adb. You need to adb sideload the update from your computer to your phone. I know this should work on a non Verizon phone but I hope and assume that is what's needed this time. If you're not able to get into recovery and your bootloader is still locked then you pretty much have a bricked device.

Arju said:
Man, when you lock the bootloader you need to make sure you're 100% back on stock without any modifications flashed. Seems to me you tried locking while having magisk flashed.
Try to see if you're able to get into recovery. Get into bootloader menu by pressing power button+volume down and the press volume upp until you get to recovery and then press power button. If you're able to get into recovery then download the full ota image for Google pixel sailfish from here removed-link and then while you're in there should be an option to update using adb. You need to adb sideload the update from your computer to your phone. I know this should work on a non Verizon phone but I hope and assume that is what's needed this time. If you're not able to get into recovery and your bootloader is still locked then you pretty much have a bricked device.
Click to expand...
Click to collapse
At the minute I've taken it to a Phone shop hoping they will be able to figure a way to get to the recovery menu - baring in mind I had TWRP flashed.
Yeah, It will go to the Bootloader menu but when trying to go into recovery it will just repeat the same process as before where by it will flash the Google splash-screen then restart. Any notes on how to go about hard flashing the image?

have you tried fastboot boot twrp.img? does it bootloop aswell? if so, you might have hard bricked your pixel... last solution is to try flash stock image and then try again with stock recovery / twrp img.

Mr Ian said:
At the minute I've taken it to a Phone shop hoping they will be able to figure a way to get to the recovery menu - baring in mind I had TWRP flashed.
Yeah, It will go to the Bootloader menu but when trying to go into recovery it will just repeat the same process as before where by it will flash the Google splash-screen then restart. Any notes on how to go about hard flashing the image?
Click to expand...
Click to collapse
If you can't access stock recovery and your bootloader is locked then your device is pretty much hard bricked unfortunately. Don't think the phone shop would figure it out, they might change the motherboard as a solution if they don't have the right tools to reflash on a deeper level. Hope they figure it out. Please let us know if they managed to fix it. If not then someone else might have some suggestions. I'll try to think of something else.
Try either of these commands to see if you can unlock the bootloader again:
fastboot oem unlock
or
Code:
fastboot flashing unlock
And then try what the post above me suggests.

Hey, did you ever figure out a solution to this? I did the same thing to myself today...

any solution??
---------- Post added at 03:49 PM ---------- Previous post was at 03:48 PM ----------
Mr Ian said:
After reading the news that a new method had been found for Verizon/EE-UK Google Pixel (Sailfish) Phones to unlock the Bootloader - I decided to do so and then proceed to flash Magisk for root and other benefits however as there was recently a new update which was showing as 'Failed to Install'.
Of cause I wanted to update the device so I attempted to re-lock the Bootloader using 'fastboot flashing lock' and proceeding to select Yes from the prompt. Which seemed to be acceptable and worked to lock the Bootloader.
Now my phone is stuck in a crazy boot-loop where by the phone will turn on - flash the Google logo on the white background for a split second then shut itself down and repeat.
Does anybody have any tips for me to recover the phone from this awful state?
Click to expand...
Click to collapse
Did you managed to unlock it???

You can unlock the bootloader with htc-fastboot if you have a bricked android 7-8.
They patched it on Android 9.
On android 9 your only chance is to reflash it in edl mode. Anyone here who can help me to enter edl mode with my pixel?

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