Database Users

[Q] The phone stuck at the LG loop, bricked, help needed!!

Australian unblocked version, said D802T I think. 4.4.2 official kitkat upgraded.
I rooted the system this afternoon using Ioroot25, and it seems like succeeded, coz I saw the supersu icon.
Then I installed the Autorac.app, which said to be working on all models, but later the admin told me not fitted for this D802T, I got really confused honestly. What's the difference between this D802T and international D802? Even installing firmware haven't seen any Australian version, for gods sake!
Anyway, I could get access to TWRP interface, and could go to download mode.
How should I bring the system back?
And plus, or maybe later, how to install TWRP on my G2? Just need that bloody 4K/120fps camera rom...
Really appreciate your help!!!

Download some aussie rom(not aware if there are any?)
then adb sideload rom.zip (enable ADB option in twrp).
+
Wait..you can go to dload mode ?
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=your_imei
replace "your_imei" with your proper imei and paste to browser to see your kdz link (i hope it works..)
If not, visit bigboy's kdz thread.

[HELP] Need Expert Help! Asus Zenfone 5 LTE (A500KL)

First of all, I wanted to apologize if I'm posting at a wrong section but please do move this thread if necessary.
Second, I know some of you have already read a bunch of problems regarding to this model of zenfone 5 but I'm still hoping that one day someone can help us A500KL users. I've spent sleepless nights browsing the internet for solutions. I've been through different websites like taiwanese, chinese, russian and many more but still can't seem to find any guides or solution to my problem.
The thing is, one day after booting my phone and making it to home screen a few seconds later it's restarting on it's own. restarted and same thing happened over and over again. I didn't mind losing my files so i went to recovery to do a factory reset hoping it will resolve the problem. But the moment I press enter, a bunch of errors saying E:failed to mount...... (invalid argument) showed up. It failed wiping to factory reset. i tried wiping cache but still gets a bunch of those error. I know little about flashing so I came to a place where they said that i have to download the stock firmware from asus website with the same version and same SKU. so i did that and stored the stock rom on my external SD card (can't save in internal since I can't boot to homescreen anymore. Just ending up in Asus logo loading forever.) but still no luck. I Searched some more and found a guide about flashing using AFT. I tried but still no luck, says it needs a .raw firmware. unfortunately anywhere i go there is no .raw firmware for my phone. so I explore some more and came across about bootloader. but recently i found out that my bootloader is locked. Neither can I flash using sideload.
My phone is not rooted, no custom recovery installed, no option to install update from ADB and can't install from recovery. BUT still able to go to recovery, boot until asus logo, when charging battery icon still shows. still vibrates when powered.
I really hope someone out there can help me with my current problem. I still think this can be done cause i don't think theres a problem with the hardware. Been searching for days and I really need to recover my phone. Oh and not to mention there are 2 more of this phone on my relatives and all of them have the same problem. So please help us A500KL users. Sorry for the long message, I'm just so desperate to recover my phone. God Bless

hi bro
well firstly bootloader unlock is NOT needed for sideloading stock firmware.i'm giving you the link to one of my tutorials,follow the procedure carefully.note one thing that do NOT download the firmware whose link is given in tutorial,instead use kitkat firmware of your phone(download from asus support page)....use only kitkat firmware pls.coz my experience says that flashing lollipop directly gives errors.http://forum.xda-developers.com/zenfone-5/help/bootlooped-bricked-returning-to-stock-t3358662

[email protected] said:
hi bro
well firstly bootloader unlock is NOT needed for sideloading stock firmware.i'm giving you the link to one of my tutorials,follow the procedure carefully.note one thing that do NOT download the firmware whose link is given in tutorial,instead use kitkat firmware of your phone(download from asus support page)....use only kitkat firmware pls.coz my experience says that flashing lollipop directly gives errors.http://forum.xda-developers.com/zenfone-5/help/bootlooped-bricked-returning-to-stock-t3358662
Click to expand...
Click to collapse
That method only work for A500/501 cg models. Not A500KL .It will not work. I already came across this problem. There is NO RAW FIRMWARE FOR ZENFONE 5 LTE

ChristopherXI said:
That method only work for A500/501 cg models. Not A500KL .It will not work. I already came across this problem. There is NO RAW FIRMWARE FOR ZENFONE 5 LTE
Click to expand...
Click to collapse
but when did i say that you need raw firmware??
what we are doing is flashing fastboot,recovery and then sideloading the zip firmware which is available on asus website...

[email protected] said:
hi bro
well firstly bootloader unlock is NOT needed for sideloading stock firmware.i'm giving you the link to one of my tutorials,follow the procedure carefully.note one thing that do NOT download the firmware whose link is given in tutorial,instead use kitkat firmware of your phone(download from asus support page)....use only kitkat firmware pls.coz my experience says that flashing lollipop directly gives errors.http://forum.xda-developers.com/zenfone-5/help/bootlooped-bricked-returning-to-stock-t3358662
Click to expand...
Click to collapse
Hello bro.. your tutorial is well said but unfortunately Zenfone 5 LTE is different. Yes i do have a firmware downloaded at the official asus website and it doesn't contain any recovery.img and fastboot.img there's only boot.img inside. and yes its only kitkat. its WW 11.4.6.94
Lastly, zenfone 5 LTE doesn't have "apply update from ADB" option in recovery by default so sideloading is not really possible. I can only depend on fastboot with locked bootloader. so yeah that makes things difficult.

[email protected] said:
but when did i say that you need raw firmware??
what we are doing is flashing fastboot,recovery and then sideloading the zip firmware which is available on asus website...
Click to expand...
Click to collapse
You din't get what i mean.... His system partition is MESSED UP. The partition also contains fastboot and recovery partition. Flashing fastboot and recovery WILL FAIL. He will have to find AND RAW FIRMWARE NOT A ZIP FIRMWARE FROM ASUS.
I already searched for Raw firmware for zenfone 5 lte. There is no raw firmware for that model. Using that guide requires the raw firmware. In the process that tool will use the RAW firnware to fix the partition table.
Hopes that clears everything up

Hi Bazerald,
My 18-month old A500KL has exactly the same problem as you had described - startup never get pass the Asus logo screen, got a bunch of "E: failed to mount ....." error messages in Recovery. I was told by the Asus Service Centre technician that the problem was caused by a broken ROM and to revive the phone, a replacement of the mother board was required and they were charging megabuck for the job. I ended up taking my phone back without fixing and here I am browsing in this forum hoping to find an alternative solution.
Since I know everything else on my A500KL is still working except the internal ROM, what I am hoping to do is to find if there is a way to load the stock firmware onto an external SD card and boot up the phone from there, in other words, I would like to swap the internal and external memory. I can find a few discussions on this topic for the Samsung Galaxy, but I have yet to find a viable solution for our A500KL.
Any member has any suggestion on this idea?

ChristopherXI said:
You din't get what i mean.... His system partition is MESSED UP. The partition also contains fastboot and recovery partition. Flashing fastboot and recovery WILL FAIL. He will have to find AND RAW FIRMWARE NOT A ZIP FIRMWARE FROM ASUS.
I already searched for Raw firmware for zenfone 5 lte. There is no raw firmware for that model. Using that guide requires the raw firmware. In the process that tool will use the RAW firnware to fix the partition table.
Hopes that clears everything up
Click to expand...
Click to collapse
hi friend
i'm really sorry,i just somehow missed the line saying that he has system error..
thanks for noting

Toki Yoki said:
Since I know everything else on my A500KL is still working except the internal ROM, what I am hoping to do is to find if there is a way to load the stock firmware onto an external SD card and boot up the phone from there, in other words, I would like to swap the internal and external memory. I can find a few discussions on this topic for the Samsung Galaxy, but I have yet to find a viable solution for our A500KL.
Any member has any suggestion on this idea?
Click to expand...
Click to collapse
I agree, I was hoping for the same thing here since xda is very popular for fixing tons of problems. I guess we'll just have to wait for THE ONE who can help us.. since A500KL doesn't seem have a raw firmware I'll be very happy if anyone can spend a time and make a raw firmware for us (if it's possible). Recovering the 3 A500KL here will be very rewarding.
Also, I'm trying to not depend too much on the raw firmawre cause the main reason is the messed up partition. Still searching for a way to fix it manually and getting some ideas on how it is done on other phones.

Unless you guys found a RAW firmware for the LTE model. It's preety much hopeless. Sorry........

does anyone know if repartitioning the messed up partition of A500KL manually is possible?

I got the same problem a few months ago. I searched through the Internet and found that many many people having such problem, I concluded that it is the quality of the chips (usually 15 months of usage), not software problem alone (the phone just died suddenly, I did nothing at all!!). This was the first time I had hardware failure in phones (in the past 20 years!). I WILL NEVER BUY ASUS phone again.

Ok guys, give me a sec and i'll find the firmware. Theres one on the website thats a revert firmware that will fix it. I had the same issue with mine. This firmware will revert it back to Kitkat. Yes.. Its DOES have the stock Recovery,Boot.img and System.img files.
This is the firmware your looking for Version WW_11.4.6.94 (Downgrade Version)
http://www.asus.com/us/support/Download/39/1/0/6/8/
ONLY FLASH THAT VERSION! Only Version WW_11.4.6.94 (Downgrade Version) (WorldWide) Version..
Only the Downgrade Versions have the complete files needed to repair a bad flash or root attempt.
Follow the directions Vaib posted on the previous page, but use the firmware file above.
Should fix the software,recovery and partition issue. Also, the bootloader unlock provided by Asus is hit and miss.
I've used it to root,but alot of the files are interlinked. So you run the risk of another app not working when trying to debloat the rom. As of now there is no Alternate non Stock Rom for the A500KL. Note: After flashing the WW firmware you phone will be recognized as an Asus "T00P". This is normal and doesnt cause any issues.
If all else fails, go here for more info on the A500KL. http://www.asus-zenfone.com/search/label/Zenfone 5 LTE
Good Luck. Happy Flashing

TabascoTX said:
Ok guys, give me a sec and i'll find the firmware. Theres one on the website thats a revert firmware that will fix it. I had the same issue with mine. This firmware will revert it back to Kitkat. Yes.. Its DOES have the stock Recovery,Boot.img and System.img files.
This is the firmware your looking for Version WW_11.4.6.94 (Downgrade Version)
http://www.asus.com/us/support/Download/39/1/0/6/8/
ONLY FLASH THAT VERSION! Only Version WW_11.4.6.94 (Downgrade Version) (WorldWide) Version..
Only the Downgrade Versions have the complete files needed to repair a bad flash or root attempt.
Follow the directions Vaib posted on the previous page, but use the firmware file above.
Should fix the software,recovery and partition issue. Also, the bootloader unlock provided by Asus is hit and miss.
I've used it to root,but alot of the files are interlinked. So you run the risk of another app not working when trying to debloat the rom. As of now there is no Alternate non Stock Rom for the A500KL. Note: After flashing the WW firmware you phone will be recognized as an Asus "T00P". This is normal and doesnt cause any issues.
If all else fails, go here for more info on the A500KL. http://www.asus-zenfone.com/search/label/Zenfone 5 LTE
Good Luck. Happy Flashing
Click to expand...
Click to collapse
Tabasco , WW_11.4.6.94 (Downgrade Version) did not have recovery.img and fastboot.img inside as well.

kenooi1984 said:
Tabasco , WW_11.4.6.94 (Downgrade Version) did not have recovery.img and fastboot.img inside as well.
Click to expand...
Click to collapse
It should have, unless i accidentally linked to the wrong one. Let me see what happened.
The downgrade version should have recovery and fast-boot. It kicks it from L to KK. Since the fast-boot and recovery aren't compatible from L to KK, it should flash it. When i boot looped mine trying to a flash an alternate recovery i re-flashed using the downgrade version to fix it. I guess possibility that it could be in another WW Version, but im pretty sure i remember flashing the first WW Downgrade. I'm going to look at WW_11.4.6.71 and see if it in there.
OK, WW_11.4.6.71 has a script to install recovery. So the recovery.img is in the firmware somewhere. Try WW_11.4.6.71 instead and see if that fixes it for you.

TabascoTX said:
It should have, unless i accidentally linked to the wrong one. Let me see what happened.
The downgrade version should have recovery and fast-boot. It kicks it from L to KK. Since the fast-boot and recovery aren't compatible from L to KK, it should flash it. When i boot looped mine trying to a flash an alternate recovery i re-flashed using the downgrade version to fix it. I guess possibility that it could be in another WW Version, but im pretty sure i remember flashing the first WW Downgrade. I'm going to look at WW_11.4.6.71 and see if it in there.
Click to expand...
Click to collapse
thanks for tried to check , i downloaded WW-11.4.6.107 it did not have it either.
due to my super slow internet speed ,it took me abt 3 hours to downloaded 1 firmware....... i wish to download all to check but...... poor me..

kenooi1984 said:
thanks for tried to check , i downloaded WW-11.4.6.107 it did not have it either.
due to my super slow internet speed ,it took me abt 3 hours to downloaded 1 firmware....... i wish to download all to check but...... poor me..
Click to expand...
Click to collapse
OK, WW_11.4.6.71 has a script to install recovery. So the recovery.img is in the firmware somewhere. Try WW_11.4.6.71 instead and see if that fixes it for you.
The recovery isnt exactly named recovery.img, there's a script that refers to installing the recovery from another location. So i'd try flashing the downgrade version after getting the phone into fastboot. And unfortunately it can be difficult to tell if the phone is actually in fastboot.

TabascoTX said:
OK, WW_11.4.6.71 has a script to install recovery. So the recovery.img is in the firmware somewhere. Try WW_11.4.6.71 instead and see if that fixes it for you.
Click to expand...
Click to collapse
ok thanks , will try it later on.

Wow.
You people really didn't read the comments section throughly.
Trying normal or downgrade firmware will not work.
This procedure requires a RAW firmware.
And using the offline update tool provided by @dgadelha.
If any of you found a RAW firmware for the A500KL model.
You can easily adapt the script from his Offline update tool.
It will repartition the device.
AGAIN. trying normal firmware is not going to fix the problem

@Bazerald (i think that your a500kl is WW) Try: with stock recovery try wipe the phone (data, cache), flash the firmware downloadable from asus site UL-ASUS_T00P-WW-11.4.6.94-user, (not the downgrade version), if not success, try UL-ASUS_T00P-WW-12.4.5.22

Stock recovery extraced from BTV-W09C233B019 ROM - untested

Hi M3 users,
I'm a long time lurker and reader on XDA. Now it's time to give something back or at least participate
Following my recent M3 purchase a dugg a bit deeper into this topic and tried to get us the stock recovery for our devices.
I'm not really a dev. I just used the information I found here and in the russian forum where greatslon (thank you guy) is posting his work.
If you find an error in the process please let me know. The files have not been tested in any way. I have no idea if this would even work (encryption and so on).
So I managed to extract the recovery.img file from the chinese rom. This method will also work for the LTE variant.
Maybe @greatslon or @somboons can share their view on the topic or maybe @somboons can even use it in his tool.
Resources
http://4pda.ru/forum/index.php?showtopic=780572&st=120
http://forum.xda-developers.com/showthread.php?t=2433454
http://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder
Tools used
Huawei Firmware Finder (Team MT)
Huawei Update Extractor
Download
M3_BTV-W09C233B019_recovery.zip
Process
1. Start firmware finder (did use the android version)
2. Change device to BTV-W09C233
3. Downloaded the firmware B019 for BTV-W09C233 (no firmware for other variants present ATM)
4. Extracted and copied update.app to SD card
5. copy to PC
6. Extract recovery.img and recovery2.img using Huawei Update Extractor
Best regards,
Benjamin

Don't quite understand what's this for. First of all, recovery should be the same version as your ROM. I don't know if their mismatch will immediately lead to some malfunction, but some people on 4pda said they should match. Second - stock recovery's functions are limited to factory reset (wiping data, cache, etc.) and installing OTA updates. Without changing OEMINFO (and it's still unconfirmed), you won't be able to install any OTA except those, intented for your model and region, so again there's no need to install a higher version of recovery than your ROM is. But anyway, thank you for the extraction instruction.
P.S. I think there's no need to flash both recovery and recovery2. Recovery2 can be successfully replaced with TWRP and this combination is really great, cause you can launch TWRP by holding Volume Up button only.
And the only reason why you should keep recovery original is that it doesn't really wipe /data - it also creates some files there like custom.bin, containing your regional settings.

Hi Slavon,
Thanks for your highly appreciated comment. @somboons was looking for a stock recovery so I thought this might help.
Your given information are really helpful. I did not know that you could flash TWRP in recovery2 and replace erecovery Handy information.
I'm pretty new to the Huawei structure so always glad to learn something.
EDIT
A lot of good information can be found here: http://forum.xda-developers.com/honor-7/general/dual-recovery-honor-7-t3308398
Thank you very much,
sselpeelsxx

Giving Back
Benjamin,
I've also been a long time XDA lurker. Most of the devices I have owned were mainstream and thus already had a very active XDA developer community; Even if root had yet to be achieved, there would be hundreds of messages on the topic.
It seems the Mediapad M3 is just getting started. I am a developer of over 20 years, but very little android experience. However, I have recently spent a considerable amount of time (about 50-100 hours) working with the low level ADB protocol source code. And I have rooted and flashed no less than 50 devices, everything from cell phones to Android TV devices to routers.
I'm going to take this device on as my first real dev effort in this arena.
I have a few goals:
1. Get working backups for people that soft-brick or need to revert (including myself).
2. Recompile TWRP for the M3 to confirm greatslon's work, and better understand the process.
3. Release a stock rom that's pre-rooted and cleaned up (not that there was a lot of bloat on my device).
4. Release a custom rom that's not MIUI (perhaps based of CyanogenMod).
Since I have virtually no experience, I am sure these goals are quite lofty and will take some time. But hey, you got to have a plan, and I don't have anything else to work on right now.
Let me know if you want to work on anything together, or if you need any help with anything development related.
- 0D0A

Hey hey 0D0A,
I totally agree with you regarding the backups, I think once the first OTA update is pushed for the EU and US devices we have a good and safe way to go back.
Especially the US owners are struggling with greatslons TWRP version, that's the first thing we should tackle after the backup topic is cleared
I will contact you regarding possible work
Best regards,
Benjamin

can flash twrp via fastboot but get error saying and no recovery
hi, first thanks greatslon for doing the work on m3.
i seem to have succeeded in getting stuck and can't get it to boot into your custom twrp. adb on linux was working fine, but no longer. ditto for fastboot just get "waiting for devices" now. i switched to win10 and installed the hisuite app so i can use fastboot but still no adb. so i have tried to flash recovery and recovery2 but when i try to boot recovery i get error "Func NO: 11 (recovery image) ERROR NO: 2 (load failed)."
i then downloaded your custom rom and tried to flash the boot for that still no luck. i can't use adb so i am not sure how to just flash the custom rom with fastboot without being able to get into any recovery.
i did have this all rooted and working with your twrp but kept having issues with dpi and there was an ota update (b003) which wouldn't apply. so i tried to restore backup and it wen't south from there. basically now can't do much other than see the unlock "can't be trusted" page and bootloader.
any suggestions?

Desperately need stock recovery img, not sure exactly what when wrong, but it is stuck in a horrible boot loop. Tried Benjamin's recovery files and they seem to remove twrp and put it somewhat back to normal, but can only access the emui recovery and that fails to load the files. Put twrp back and tried greatslon's ROMs, they load but goes back to boot loop. Wipe and format everything, install my original backup through twrp recovery, it says it works, but again, back to boot loop... at this point I think I'm dead... any ideas, any word on the official recovery img? anything? Help!!

What device do you have? And what version were you on?

sselpeelsxx said:
What device do you have? And what version were you on?
Click to expand...
Click to collapse
I have the M3, BTV-W09, not sure what version, MM6.0 EMUI 4.1

Anyone have any other ideas on horrendous boot loop?

sselpeelsxx said:
Hey hey 0D0A,
I totally agree with you regarding the backups, I think once the first OTA update is pushed for the EU and US devices we have a good and safe way to go back.
Especially the US owners are struggling with greatslons TWRP version, that's the first thing we should tackle after the backup topic is cleared
I will contact you regarding possible work
Best regards,
Benjamin
Click to expand...
Click to collapse
Hello, I am unlocked, TWRPed, and rooted, but am trying to reverse all of that. My build number is BTV-W09C128B002. Is it safe to download the stock recovery from the OP for my device? Or do I really need the C128 version?

Hello and sorry for the late response, you would need the matching version for your C128 device.
I may be able to extract recovery from an update, I have to look into this tomorrow.
Regards

sselpeelsxx said:
Hello and sorry for the late response, you would need the matching version for your C128 device.
I may be able to extract recovery from an update, I have to look into this tomorrow.
Regards
Click to expand...
Click to collapse
Thanks! I have been able to use the Huawei Extractor to extract a recovery.img from OTA updates, but have been afraid to try flashing it. It has been recommended to hold off on trying that since that recovery.img is from an OTA and not a FULL update. Any thoughts?

How to unbrick my ZTE Axon 7 mini b2017g

Dear Seniors.
I am facing great hardship because my phone is stuck at boot logo.
No booting in recovery mode to flash another rom.
I did unlock bootloader of it by using tuliptool with success. After that i flashed custom rom in it. after reboot it is happening that.
Please suggest to recover it.

Did you flash twrp after unlocking? Did you make backup of stock ROM? Perhaps find a version of the factory firmware and flash that.

Dear I have no backup and i flashed TWRP recovery.......
It is to aware you that i did relock bootloader now my phone is working properly. but i am unable to enter recovery mode. !!!
Now my phone is running android 6.0.1 B02
But i am failed to root this rom uptill now due above mentioned problem.

modorate said:
Dear I have no backup and i flashed TWRP recovery.......
It is to aware you that i did relock bootloader now my phone is working properly. but i am unable to enter recovery mode. !!!
Now my phone is running android 6.0.1 B02
But i am failed to root this rom uptill now due above mentioned problem.
Click to expand...
Click to collapse
I found software update notification but when i update an error accruing while update. (This update not compatible with this device"
In easy words......... my recovery.img has been corrupted. I have no idea to get rid of this situation.

I planned to unlock my Mini's bootloader this weekend. After reading this post, I decided to act later until the root cause has been figured out.

bao_gg said:
I planned to unlock my Mini's bootloader this weekend. After reading this post, I decided to act later until the root cause has been figured out.
Click to expand...
Click to collapse
Several people myself included have been able to use tuliptool to successfully unlock and root the device.

mine is hard bricked too. but I think it is worse than the case listed on the op.
if you want to hard bricked these are the steps:
follow the procedure to install the Spanish ROM 6.1, than another android m b12, than finally the android seven......use tulip tool and install twpr fine, root ect. amazing ROM.......buuuuut......I lost my IMEI somewhere in this process, and the original FTM which had a small menu changes to another static one, without the menu.
I needed this menu to open the com port to fix the IMEI. than I had the brilliant idea to re-flash android M via twrp (without modifying the zip file to remove the recovery, something I knew so well from the older axon mini).
results:
-lost twpr because the stock ROM wrote over it,
-cannot boot the OS because I flashed android m but the phone had the aboot 7.
-i now have a brick
I need a genious to sujest something to bring it back to life........sh....t...sh...t.....sh...t
any chances I could inject aboot7 via ADB through my dead recovery which somehow the phone recognises? ADB shell still seems to be working
thanks

(SOLVED) I used TWRP and accidentally wrote over the boot recovery partition

Hello,
In a late-night act of utter stupidity, when over-tired, I re-flashed the boot recovery with TWRP and bricked my M3. It obviously can't now enter boot recovery.
I've used TWRP and successfully re-flashed custom roms on my original Mate, and changed regions. (Not in any way an expert, I know how to follow instructions.)
I was trying to convert my Chinese (I was living there) ROM to UK. It's tricky nowadays.
This was a stupid error when tired. Any way back?
I read somewhere that people with the right hardware can do it, but finding someone. I'm in Leeds, UK.
The pad does (did) what I need, and I'm not in a position to buy a new one. If it's dead, it's dead; and I can move on.
Cheers in advance for any input.
SOLVED
See my last post on this thread.
After using Multi Tool V8 to enquire into the machine I switched off and rebooted.
It came back with a "Wipe cache" and "Reset to factory settings" Huawei screen, so I did both and - It booted!
It had spectacularly failed to do anything but boot-loop since coming out of a very dead battery yesterday.
1) Boot recovery, OTA recovery, and dload recovery from SD were all unavailable after the original overwriting of the bootloader.
2) After being dead for months, all recovery options booted from power button plus vol- Vol+ and Vol+/- - but still bootlooping.
Then, suddenly it booted into wipe cache/factory reset screen.
Android 7, EMUI 5.1.3
I have no idea why.
Now fully working. (Including restarting)

I fell in a similar situation after having flashed a magisk module .. unfortunately my nandroid backup didn't restore my devices, but I was able to enter in twrp recovery.. so,..
if you can boot in twrp recovery, not all hopes are lost..
first of all, you must download a stock firmware for your device (i suggest to download trough huawei firmware finder: https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/amp/)
You must download a fullota version of stock firmware
then, you can flash this firmware (3 zip files) trough hurupdater via twrp recovery: https://forum.xda-developers.com/ho...lash-official-firmware-recovery-t3769279/amp/
in order to not overwrite twrp recovery, put the twrp.img file in the same folder and rename it to recovery.img
you can find more info in this topic (follow the instructions, in particular those on how to use hurupdater): https://forum.xda-developers.com/me...ting-btv-dl09-to-unapproved-firmware-t3817541
in order to find a firmware suitable to your device, try to find info on it: you have a mediapad m3 European? American? asian? just wifi or also 4G-LTE (whit a sim and phone functions)? lite or normal version? 10 inches or 8.4?
everyone of these devices have different codenames and suitable firmwares
I found exact firmware for my devices with the procedure described here:
https://forum.xda-developers.com/showpost.php?p=77241673&postcount=3
.. but, if you flashed a wrong firmware, i really don't know if it might help you..
anyway, i wish the info above could help you.

qllkevuoi said:
I fell in a similar situation after having flashed a magisk module .. unfortunately my nandroid backup didn't restore my devices, but I was able to enter in twrp recovery.. so,..
if you can boot in twrp recovery, not all hopes are lost..
first of all, you must download a stock firmware for your device (i suggest to download trough huawei firmware finder: https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/amp/)
You must download a fullota version of stock firmware
then, you can flash this firmware (3 zip files) trough hurupdater via twrp recovery: https://forum.xda-developers.com/ho...lash-official-firmware-recovery-t3769279/amp/
in order to not overwrite twrp recovery, put the twrp.img file in the same folder and rename it to recovery.img
you can find more info in this topic (follow the instructions, in particular those on how to use hurupdater): https://forum.xda-developers.com/me...ting-btv-dl09-to-unapproved-firmware-t3817541
in order to find a firmware suitable to your device, try to find info on it: you have a mediapad m3 European? American? asian? just wifi or also 4G-LTE (whit a sim and phone functions)? lite or normal version? 10 inches or 8.4?
everyone of these devices have different codenames and suitable firmwares
I found exact firmware for my devices with the procedure described here:
https://forum.xda-developers.com/showpost.php?p=77241673&postcount=3
.. but, if you flashed a wrong firmware, i really don't know if it might help you..
anyway, i wish the info above could help you.
Click to expand...
Click to collapse
Thanks for the reply, and sorry for the delay. New child has somewhat taken over our lives!
I'll take a look at the tablet again when I have time, probably next month.

Update - Bootloader working after battery drain: Now what?
[Edit] Post redundant as it started working - see OP.
NwotNot said:
Thanks for the reply, and sorry for the delay. New child has somewhat taken over our lives!
I'll take a look at the tablet again when I have time, probably next month.
Click to expand...
Click to collapse
Well...
After being without power for so long I turned the tablet on and it booted!
However, it then went into OTA and updated - rebooted - and locked the damned bootloader.
1) It's showing as rooted.
2) Boot loader is locked.
3) Fastboot & rescue mode comes up.
4) Recovery (OTA) still comes up but "Fails" this time.
I don't recall how I unlocked it last time. I don't ever rememebr an unlock code.
Status:
Fastboot reports it exists.
ADB reports "Null" not found. (ADB drivers installed).
Firmware version: CPN-AL00C233B078
Device name: CPN-AL00
Serial Number: Showing
IMEI: Showing
Bootloader state: LOCK
I have an old TWRP backup - don't know how to use it.
Solutions?
a) Any kind devs prepared to work with me and find the boot unlocker code for this 5-year old tablet?
b) Any other solutions now we know what's what?
I'm self employed without income in this pandemic and can't really afford to buy a new tablet. If I have to, it won't be Huawei.
(There's a T3 10.6" at £89, but I'm not biting - I need to sort out a budget tablet with at least the oomph of the M3.)
Any help much appreciated. :good:
David.