Database Users

Post Your Current or Last Boot Issues here (READ BEFORE POSTING PLEASE)

Hi A7 users,
Let's start this off be saying, bare with me English is not my primary language.....
OK now, the reason for this Thread is to find a definite solution for current users and future users who have run into boot issues cuz they were trying to :
A- Go back to Un-rooted and lock bootloader state.
B- Started Playing with root tools and make a huge mistake
C- Started playing with twrp not knowing what they were doing
D- All the above + started flashing images files and got worts.
E- Any other type of situation.
I Know we make mistakes and we learn from them and well here today we are going to try or rather say Find a permanent /define solution to all this issues with your help, so PLEASE ONLY POST IF YOU HAVE RUN INTO ANY OF THIS ISSUES AND HOW YOU GOT INTO THE ENCHILADA ( MESS ) .
If you have the solution to your previous boot problems send me a PM and I'll keep this Thread updated for everyone to see with your solution and of course credit to the user/s.​
NOTE : Please mention which Axon 7 you are using e.g. :
- A2017 (Chinese Variant)
- A2017U (USA Variant)
-A2017G (UK/Europe/International Variant)

reserve 1

reserve 2

reserve 3

reserve solution 4

reserve solution 5

Anyone this issues please post you issue, how to got into the problem, device model and if you got it fix let us know.

https://www.youtube.com/shared?ci=05LD4Ja-h3k
You'd think with all the other posts about problems there'd be something here by now.
Always thank those who are helpful...and just ignore those who aren't.

Mine happened when I wiped Internal storage from twrp. This caused the phone to only see 4gb of internal storage. Came to xda and it was suggested to flash back original boot.img. once that was done 4gb issue was fixed and the radio was gone.
I did indeed try every solution offered (thanks again for all the effort, DrakenFX and others). But, I've come to the conclusion that this is not going to get fixed until XTE releases US images. For other people's sake I hope I am wrong, but I myself decided to proceed with the exchange where I bought it, as I was right at the end of my 14 days (newegg doesn't seem to give the 30 days that xte does). I may be out of an Axon 7 for a while, so for now I am on my amazon ads, Blu R1 HD (with ads defeated

Is there a guide to go back to stock for the A2017G?
i'm on B02 with root and the bootloader still locked.
Like to go back to stock now that ZTE is working on an update to give the A2017G an unlocked bootloader.

Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!

aPexalpha said:
Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!
Click to expand...
Click to collapse
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++

I am was rooting my axon a2017 on b10 chinnese version without any backup after rooting got password screen after boot then i was do factory reset and format data and all looking good but after that i saw that i dont have google play app so i installed macro gapps 6.0 after flashing phone stuck on axon screen (after zte logo) for long time i been wait up to 30 minutes and nothing was done..also i have the message on twrp about the modification(dont understand why i have this message all the time) i saw in xda forum that need to install supersu so i search on internet and was flash super su 2.65 and then when i am was boot device go to zte logo screen and then turning off when i connect the device as mtp device named as a2017u (whats worng with it??? I was flashed b10 root boot.img)
I regret about this root and want to back all to stock without any problems need help from someone
I need stock b10 boot.img if someone can upload
Many thanks!
---------- Post added at 04:23 AM ---------- Previous post was at 04:11 AM ----------
DrakenFX said:
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++
Click to expand...
Click to collapse
Its will help me too i think

Dear All,
ZTE Axon 7 A2017 (Chinese version) Stuck on Bootloader mode.
Device after power on will Stuck on ZTE logo even power button press longer also will Off and came back to square one and the only way to power off is via selection on bootloader page via volume button which consists of Recovery mode, Power Off, Bootloader and some other mode which I can't recall.
History of this issue. Please bear with long story.
Manage to install MM ROM with B13 via sd card installation via update software in phone setting. follow by Unlocked bootloader and Install TWRP 3.1.1.0 then try few different ROM until one day when I use Xiaomi flashtool my PC crash half way through during flashing resulting in device with Pure Chinese ROM and TWRP also got corrupted, when I said corrupted because I install TWRP 3.1.1.0 but when I go to Recovery mode it shows TWRP 3.0 something. with this corrupted TWRP when I try to install ROM it will show loading but end result is NIL meaning same ROM nothing change.
Until this stage I never did a TWRP backup because all this while the ROM is Not my type of ROM from this junction when I boot back to TWRP and I did Advance Wipe most of it except external sd card thinking that I may be able to install fresh TWRP but my Recovery TWRP is residing in phone storage resulting in No more TWRP recovery software. next thing I did was I connect phone to PC and ran adb fastboot tool to detect device and managed to detect device in recovery mode and I make decision to Locked back the bootloader and did just that and Locked bootloader is Succes and it also Erased everything during the process.
To cut short the story after Locked back bootloader only Bootloader mode is accessible and when I connect to PC and enable Recovery mode (Black screen) and EDL mode (Black screen) from Windows PC Device Manager COM port able to see Qualcomm 9008 for this 2 mode.
I must admit after few days of trying to resolve this Stuck Bootloader issue I almost give up.
Then I remember this Woodo magic by jcadduno which recommends XM flashtool version 2016.08.30.0 but unable to flash after trying few version Xiaomi flashtool and the very latest and I mean from Xiaomi Flashtool webpage http://xiaomiflashtool.com/
version 20170425 that break the ice and finally able to load A2017U ROM because this US ROM my phone No Network detected.
From here onwards I unlocked bootloader and install back TWRP (Installation of TWRP via Axon7toolkit) because of Network issue since I got TWRP I install back A2017 ROM but still Not satisfied because Chinese ROM certain Apps having issue because of Google services and I chance upon this Conversion A2017 to A2017U ROM (Hybrid ROM caused ROM is US and Modem from Chinese Modem)
that I'm stay put right now and my phone now is A2017U model.
I hope this experience can help others with similar Stuck bootloader and those who wish to convert A2017 to A2017U ROM.
below is the link that I described Woodo magic.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Straight forward Axon7toolkit, please don't use Chrome browser cause Chrome will Automatically Delete it after complete download for my case I used Microsoft Edge.
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
below is the link to Hybrid ROM for A2017U
https://androidfilehost.com/?fid=457095661767154458 by Michael Warner After flash install No verity patch for the bootloader.
Cheers.

I am stuck in a position where I can restore my nandroid backups but get Error 7
when trying to reinstall any Rom on a2017u I was able to fix the unlocked bootloop
by the EDL method. The Rom's are the same as the backups. I think I tried to role back to B29 Causing the bootloop) and have had problems ever since.
Should I try flashing A2017Uv1.1.0B32_Bootstack_by_DrakenFX since the Rooms are all B32?
The B15 and B19 Nandroid's still Restore fine.

Hello all,
i don't get onto forums very often but i thought this was a nice one to add to. i've rooted a few motorolas, a few ztes, a cat; i've also bricked those ztes, cat & a few samsungs. i'm dealing with two Axon7U's; one is factory MM-b29, the other is N-b35.
while screwing around with TWRP, i bricked the b35 (the b29 has been bricked for a month at this time) after i had it almost perfected. by perfected i mean a custom recovery & root user access fully acquired. with DrakenFX's {YOURS; thanks so much. i'm learning to get along with linux} extensive files created to save people from themselves i was able to unbrick the b35. albeit its CELLULAR DATA became unhinged; that's something i could've lived with except it was a loaner and had NO CAMERA! it's camera (along with the ability to push both volume buttons at once for say EDL mode...) was damaged having been beaten across a steering wheel several times. so with my newfound unbricking superpowers i decided to take another crack at the b29. managed to get it unbricked but couldn't get it setup with both TWRP & SuperSU without losing one, the other or, both. at times it didn't even boot up. i was doing pretty much everything cited above for reasons 'why'. best way to learn is by trial & error (if one can afford it).
the b29 is rooted right at this moment; i'm working on it as soon as i leave this posting. i used Axon7_EDL_Tool. i used Axon7root. i used MiFlash. i used Fastboot. I used ADB App Controller software too. back & forth i fought for three days mostly due to downloading glitches and i prevailed. i manipulated a stock OTA full system update.zip by happenstance and it Auto_Updated over itself. in other words it already had the same ROM installed. i don't know what it tested to realize it needed to update to what it already had. it didn't have CELLULAR DATA either. just like the b35, it broke somehow while flashing TWRP or SuperSU. funny thing is it still wanted to update that same ROM after it did. while perusing the system update setting(s) i noticed it had downloaded N-b15 and it wanted to update b29 AGAIN! i opted for the Nougat update. it did alright and appears to have fixed it's CELLULAR DATA too. i haven't looked at it since but i'm confident i can gain root user access with a minimal amount of effort.
The main problem i've had with dealing with bricked devices is the age of the file downloads. most of them are simply GONE!, expired links and whatnot. if i'd had a clear path say from a custom recovery and rooted boot image of my factory version or the path that leads to it, i'd have been fixed up long ago. i've found partial 'paths' if you will that almost get me there but no quite all the way. flashing images & zips through fastboot are different from their counterparts entered through TWRP or Emergency Download Mode which of course are both different too. three different ways to get into one's phone makes it almost impossible to keep them perfected.
i'm not sure i did what i'm supposed to regarding this thread. Thank you DrakenFX for your time & knowledge; you've saved my old Axon7!

Hello all update;
b35 Nougat phone is retired. b29 managed to update itself to b35 7.1.1. however, its CELLULAR DATA is still broken. i haven't managed to figure out how or where it's broken so i cannot fix it.
what i'm trying to do now is flash Magisk instead of SuperSU and using a TWRP version 3.0.3-1. heck i've used all of TWRP's versions in my efforts to reacquire CELLULAR DATA.
crazy part is the phone knows its CELLULAR DATA carrier and freely displays all of its hookup info. this is very frustrating.

P9 lite custom rom setup troubles + softbrick

Hi everyone,
i hope someone has time to help me on this. I had some experience with flashing custom roms with Lenovo a6000 and some Samsung phones, but it seems there's some things that are different with p9 Lite (L21), or some things i don't understand.
First things first, i've followed steps on how to install LineageOS (LineageOS-14.1-20171228-hi6250-UNOFFICIAL-HassanMirza01) over stock Nougat rom (B381), so i've unlocked the bootloader, flashed Revolution recovery via fastboot, and then installed the rom, gapps, magisk... What happened after installing magisk is a sudden restart, and after that, i got stuck at the LineageOS boot logo (i've let it work for over an hour until i gave up)... Thinking magisk was a problem, i also tried SuperSU, but had the same situation - restart before it finnished. Afterwards i've tried flashing EliteTWRP and after success, i've flashed the Omni-7.1.2-20171201-hi6250-HOMEMADE-HassanMirza01.zip, which also got stuck at the Omni boot logo, but i was able to do installation both with magisk and then again with supersu. Reading through XDA gave me some suggestions, one of them being to format userdata, which gave me a message that the command is not allowed.
Then i made a huge mistake of accidentally formatting internal dalvik+cache+data+system+INTERNAL STORAGE via recovery... After that, the Omni boot logo stopped showing, and i've been trying to repair it since then.
What i've tried so far is:
- fastboot flash boot, recovery (stock), system:
from what i've read there's also a CUST.img that i need to flash, but when i extract update.app that i had installed before all this, it doesn't contain it. I've tried flashing cust.img from another package, but it gives an error.
- after flashing boot, recovery and system.img, i've tried copying various update.app versions to dload on sdcard, then forcing update via pwr+volup+voldown, but every single one gives me "Software install failed - incompatibility with current version - please download the correct update package"... the same happens with downgrade package update.app.
It seems that only B381 update.app, when copied to sdcard and executed in the same way, gives a somewhat different message, instead of "incompatibility with current ver..." it says "Get help from http:..."
- adb shell dd if=/external_sd/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo // re-locked my bootloader
- i can unlock the bootloader and install twrp again via fastboot oem unlock *************** and fastboot flash recovery
- i've also tried unbricking options via P9 Lite Toolkit app, no success.
- HiSuite recovery option says device is not supported for system recovery
Any suggestions ?

hexahive said:
Hi everyone,
i hope someone has time to help me on this. I had some experience with flashing custom roms with Lenovo a6000 and some Samsung phones, but it seems there's some things that are different with p9 Lite (L21), or some things i don't understand.
First things first, i've followed steps on how to install LineageOS (LineageOS-14.1-20171228-hi6250-UNOFFICIAL-HassanMirza01) over stock Nougat rom (B381), so i've unlocked the bootloader, flashed Revolution recovery via fastboot, and then installed the rom, gapps, magisk... What happened after installing magisk is a sudden restart, and after that, i got stuck at the LineageOS boot logo (i've let it work for over an hour until i gave up)... Thinking magisk was a problem, i also tried SuperSU, but had the same situation - restart before it finnished. Afterwards i've tried flashing EliteTWRP and after success, i've flashed the Omni-7.1.2-20171201-hi6250-HOMEMADE-HassanMirza01.zip, which also got stuck at the Omni boot logo, but i was able to do installation both with magisk and then again with supersu. Reading through XDA gave me some suggestions, one of them being to format userdata, which gave me a message that the command is not allowed.
Then i made a huge mistake of accidentally formatting internal dalvik+cache+data+system+INTERNAL STORAGE via recovery... After that, the Omni boot logo stopped showing, and i've been trying to repair it since then.
What i've tried so far is:
- fastboot flash boot, recovery (stock), system:
from what i've read there's also a CUST.img that i need to flash, but when i extract update.app that i had installed before all this, it doesn't contain it. I've tried flashing cust.img from another package, but it gives an error.
- after flashing boot, recovery and system.img, i've tried copying various update.app versions to dload on sdcard, then forcing update via pwr+volup+voldown, but every single one gives me "Software install failed - incompatibility with current version - please download the correct update package"... the same happens with downgrade package update.app.
It seems that only B381 update.app, when copied to sdcard and executed in the same way, gives a somewhat different message, instead of "incompatibility with current ver..." it says "Get help from http:..."
- adb shell dd if=/external_sd/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo // re-locked my bootloader
- i can unlock the bootloader and install twrp again via fastboot oem unlock *************** and fastboot flash recovery
- i've also tried unbricking options via P9 Lite Toolkit app, no success.
- HiSuite recovery option says device is not supported for system recovery
Any suggestions ?
Click to expand...
Click to collapse
http://www.meticulus.co.vu/p/hi6250-custom-rom-installation.html

Thanks.
I've managed to revert to stock by following one thread here on XDA. What I did was install L21C432oemInfo-DS.zip, then wipe everything via TWRP, and finally copy the L21C432B130 update app to dload folder on sd card, then the setup went without any problems.
I am now doing a full backup via Meticulus TWRP before i do anything.
There's one thing i dont understand about AOSP and RessurectionRMX roms, it says they're EMUI5 based - does that mean i'd have to update to EMUI5 based stock rom before i try installing it (prerequisites don't mention anything emui related) or that simply means the rom contains EMUI5 ?

hexahive said:
Thanks.
I've managed to revert to stock by following one thread here on XDA. What I did was install L21C432oemInfo-DS.zip, then wipe everything via TWRP, and finally copy the L21C432B130 update app to dload folder on sd card, then the setup went without any problems.
I am now doing a full backup via Meticulus TWRP before i do anything.
There's one thing i dont understand about AOSP and RessurectionRMX roms, it says they're EMUI5 based - does that mean i'd have to update to EMUI5 based stock rom before i try installing it (prerequisites don't mention anything emui related) or that simply means the rom contains EMUI5 ?
Click to expand...
Click to collapse
You must already be on EMUI 5 to install EMUI5 based ROMs.

[SOLVED] Huawei nova bricked

I folowed this tutorial https://forum.xda-developers.com/nova-plus/development/rom-aospextended-v4-6-t3717372 and all flashing was fine. Due to some inconveniences of this new flashed rom i decided to restore to default rom. I extracted recovery and update.app version Can-L11 B396 i think from firmware finder and flased with adb this recovery. After that, it asked me to do an factory reset, i did it, but it wont boot any of huawei or Aosp Extended. The main problem i have is i can`t acces any more my phone with adb terminal, maybe after flashing the new original recovery usb debbuging reverted to un-enabled. How can I do now? Thanks in advance.

campeadore said:
I folowed this tutorial https://forum.xda-developers.com/nova-plus/development/rom-aospextended-v4-6-t3717372 and all flashing was fine. Due to some inconveniences of this new flashed rom i decided to restore to default rom. I extracted recovery and update.app version Can-L11 B396 i think from firmware finder and flased with adb this recovery. After that, it asked me to do an factory reset, i did it, but it wont boot any of huawei or Aosp Extended. The main problem i have is i can`t acces any more my phone with adb terminal, maybe after flashing the new original recovery usb debbuging reverted to un-enabled. How can I do now? Thanks in advance.
Click to expand...
Click to collapse
Check this post.

I cant access my phone via adb or twrp recovery. I wonder why. Before flashing a stock recovery all Was fine, adb Was connecting with no problem.

campeadore said:
I cant access my phone via adb or twrp recovery. I wonder why. Before flashing a stock recovery all Was fine, adb Was connecting with no problem.
Click to expand...
Click to collapse
Try to flash the TWRP again with fastboot.
PS: I don't understand how you people end up like this. It never happened to me.

I cant, adb cant be connected to device. Says null operation.

finally i succeed to revert o stock rom. Now i have on About phone CAN-L11C432B397, Emui 5.0 and Android 7.0. One question please, I dont see anymore the Update system tab or something, "Actualizator" on romanian language. Is that normal? How i can check for updates?

campeadore said:
finally i succeed to revert o stock rom. Now i have on About phone CAN-L11C432B397, Emui 5.0 and Android 7.0. One question please, I dont see anymore the Update system tab or something, "Actualizator" on romanian language. Is that normal? How i can check for updates?
Click to expand...
Click to collapse
You need to install the other zip too which has the word "data_full" at zip's name or something like that.
EDIT: @campeadore, i suggest you to edit the thread name and add "[SOLVED]" at begin and write the way you've fixed your phone (the solution), so it'll help other people who might run into the same problem as you.

I`ll do it as soon i fully resolve the problem. I followed your link and everything went fine at step 1 (Go back to EMUI 4.1 (MM). System is booting, but system update is not working. So, i want to flash EMUI 5, but can-l11c432b330 or can-l11c432b396 cant be updated, around 45% gives an error. The only version who work is can-l11c432b320 but i dont have update_full_CAN-L11_hw_eu, only the first update.zip.

campeadore said:
I`ll do it as soon i fully resolve the problem. I followed your link and everything went fine at step 1 (Go back to EMUI 4.1 (MM). System is booting, but system update is not working. So, i want to flash EMUI 5, but can-l11c432b330 or can-l11c432b396 cant be updated, around 45% gives an error. The only version who work is can-l11c432b320 but i dont have update_full_CAN-L11_hw_eu, only the first update.zip.
Click to expand...
Click to collapse
Newer / newest firmware downloaded from Firmware Finder needs to be approved by Huawei and that can take some time. It's failing to install because it wasn't approved. I've read this in past somewhere.
Try B381 or B382 as i've always installed that one when i've went back to EMUI 5.

Yes, i did it now with can-l11c432b330. I think my mistake was trying to flash to EMUI5 with usb cable connected. With cable off all went fine like a charm. Now i do all approved updates with system update. Thank you so much man, really appreciated.

Seeking help: I have a smartphone huawei nova lite plus (TRT LX1) that fails to restart. It goes continuously in a loop. Entering recovery only the first 2 functions come out: wipe wash factory reset and wipe wash partition. Then using eRecovery from PC with the USB cable, proceed up to a certain point and then not continue. I think it's in soft brick. I definitely need the right software for flashing, stock roms and usb drivers. Where can I find them? Many thanks

Nova Plus MLA-AL10 signal and flashing

Hi, I met some problems with my Nova plus mla-al10.
In short, the phone cannot boot and I need help with getting the offical emui5.0 dload upgrade package. (probably)
Below is the whole story:
1. The phone is unlocked.
2. Upgraded emui4 180 to emui5 in the emui4 system. The system indicated the target version is emui5 352. After updated, my version turned into NRD 90M test-keys without many huawei custom apps. ( I think it's because of the lack of data-update package, but it's too late now)
3. I tried to solve the version problem and I flashed the phone through fastboot with RECOVERY, BOOT, SYSTEM & CUST extracted from the downloded update packages. ( First 358, later I tried several other versions, same failing)
4. Then I cannot boot my phone. Just enter erecovery after 2nd reboot, and I cannot get the Rom downloaded through erecovery. Error reported.
5. Then I tried the dload update mode with a certain emui4 dload rom which I can only got from the internet for the MLA version. I cannot make sure what the ROM version was, like b122 or b133, emui4. I failed during update in the official recovery. 5%, 45% ,several times.
6. So I tried to use the twrp and both lineage and asop rom from #Henkate. Thank you #Henkate, the phone booted again. The system worked fine, except for one problem: When I use the China mobile(TD-LTE) and China unicom(WCDMA/LTE), I cannot dial out or dial in ( busy line). The sms and data(internet) worked fine. The signal is good. The sim card seemed to be successfully registered. China telecom seems worked fine(FDD-LTE) with dialing, sms and network. By the way, the china telecom simcard is the first card I used in the first lineage's first boot. I just found it abnormal with the problem above recent days.
7. Then I flashed the asop from #Henkate after wiping the system, cache and data. The same problem.
8. Now I cannot get where the problem is. I guess maybe the baseband software got wrong, so I wanted to flash the modem.img into the phone. The only way I think possible is to flash the dload package with version above 358 (or 360 which I also flashed through fastboot)through the huawei official recovery. The question is where I can get the package and is it the right thing to do? If not, how can I get back to the offical EMUI or other roms functioning normally?
Please help!
Thank you in advance!

Please HELP ME LENOVO COMMUNITY ??

I am having some issues when its in download mode my pc shows alot of drives n asking me to format it n the downloder is not reading my phone n the fastboot is showing the remote error n adb doesnt detect my phone at all......i need helppp*
I tried installing the stock os several times before but my phone boots to the 'lenovo for those who do' part n then reboots....it reboots before even the logo completes......it booted once n there is no sound no readings for sim at all......I NEED SERIOUS HELP
:crying:
:crying:
:crying:

Which version os did you have when the phone got bricked? I suppose you have twrp installed. First try to wipe data partition in twrp and reboot.
If that won't work then try installing a custom rom same as the android version you had on your phone (for example, if you had marshmallow os the find a marshmallow custom rom).
You can also try the same with any latest stock firmware. Make sure it is a flashable zip.
Hope this helps.