Axon 7 A2017 problem - ZTE Axon 7 Questions & Answers

Hi, i'm domenico, i read everyday your forum from italy. I decided to write here becouse i don't know how to solve this damage.
I have the same problem reported here
https://forum.xda-developers.com/axon-7/help/signal-update-a2017gv1-2-0b02-t3602415
I read around that is needed to do a backup of modem and other file but i dont and now i can't use a sim card it says no network connection and when i try to call tell me airplane mode on.
Anyone please know if there is something i can do? i tried to run fastbot for use miflash and restore the original image but it doesn't work can't go in EDL mode

AmilDK said:
Hi, i'm domenico, i read everyday your forum from italy. I decided to write here becouse i don't know how to solve this damage.
I have the same problem reported here
https://forum.xda-developers.com/axon-7/help/signal-update-a2017gv1-2-0b02-t3602415
I read around that is needed to do a backup of modem and other file but i dont and now i can't use a sim card it says no network connection and when i try to call tell me airplane mode on.
Anyone please know if there is something i can do? i tried to run fastbot for use miflash and restore the original image but it doesn't work can't go in EDL mode
Click to expand...
Click to collapse
Flash universal bootloader and the modem for A2017 from the lineage os thread. Then you should get radio signal again.

I don't know how to do It Can you give me more information please?

AmilDK said:
I don't know how to do It Can you give me more information please?
Click to expand...
Click to collapse
Is your bootloader unlocked? Do you have TWRP? If you do, go to the LineageOS thread (located over 'ROMs, Kernels, Recoveries') and download the 'A2017X Universal Bootloader' and 'A2017 Modem' from there (there should be a link to androidfilehost where the universal bootloader and modem files are located). Be sure that you download the A2017 modem file (NOT the A2017G or A2017U one!).
After that simply put them on your phone and flash them via TWRP

Choose an username... said:
Is your bootloader unlocked? Do you have TWRP? If you do, go to the LineageOS thread (located over 'ROMs, Kernels, Recoveries') and download the 'A2017X Universal Bootloader' and 'A2017 Modem' from there (there should be a link to androidfilehost where the universal bootloader and modem files are located). Be sure that you download the A2017 modem file (NOT the A2017G or A2017U one!).
After that simply put them on your phone and flash them via TWRP
Click to expand...
Click to collapse
Thx for the help, i do not have bootloader unlocked and not have TWRP.

I've installed TWRP but when i try to enter in recovery (Power + volume up) nothing happen. Just blackscreen

AmilDK said:
I've installed TWRP but when i try to enter in recovery (Power + volume up) nothing happen. Just blackscreen
Click to expand...
Click to collapse
What version did you install? 3.1.1-0?

Followed a guide and with minimal fastboot and adb tool put in the phone the 3.0.4-0-ailsa_ii.img successful After that can't go on with steps and if try to open recovery nothing happen

Install Stock ROM from EDL with MiFlash.

WesTD said:
Install Stock ROM from EDL with MiFlash.
Click to expand...
Click to collapse
i tried with twrp 3.1.1.0 same can't access to recovery
miflash doesn't recognise my phone in edl

AmilDK said:
i tried with twrp 3.1.1.0 same can't access to recovery
miflash doesn't recognise my phone in edl
Click to expand...
Click to collapse
Is your phone on edl mode?

Yes i think had a problem with drivers. I out the phone in edl from cmd with adb then opened miflash but can't see the device

AmilDK said:
Yes i think had a problem with drivers. I out the phone in edl from cmd with adb then opened miflash but can't see the device
Click to expand...
Click to collapse
Try 'adb reboot recovery' from cmd

I don't know where i miss, i tried with adb and axon 7 tool, adb edl reboot, axon7tool axon7tool -r gpt boot recovery*, then axon7tool -w recovery, with twrp-3.1.1-0-ailsa_ii.img renamed in recovery bin, but from here nothing happen, i can't go in recovery if i try nothing happen black screen if i put the old recovery.bin can reboot in recovery but can't flash modem file or unlock bootloader. Tried with miflash but nothing happen give me error "cannot receave the hello packet"
PS my buil now is ZTE A2017GV1.2.0B04, the original one was ZTE_A2017V1.0.0B15
Choose an username... said:
What version did you install? 3.1.1-0?
Click to expand...
Click to collapse
i found a post with exactly my situation
https://forum.xda-developers.com/axon-7/help/sim-airplane-offbut-turnd-t3698325
perchance have you the file you talk in this post https://forum.xda-developers.com/showpost.php?p=74386034&postcount=24

i don't know how, but i did it.. with axon7toolkit, restored original rom, then updated to V.2.0.0B13, now works good

Related

Need TWRP Backup of UK version, a2017g

Hi,
I rooted my ZTE Axon 7 UK version, A2017G and i accidentally formatted the system, currently i have the US version of the software running but i dont have any WIFI
thanks for the help in advance
Can't help you with the European system
But have you tried flashing B20 boot.img from tenfar tool ? Might solve your wifi issue...
If that works, it's awesome !
shia786 said:
Hi,
I rooted my ZTE Axon 7 UK version, A2017G and i accidentally formatted the system, currently i have the US version of the software running but i dont have any WIFI
thanks for the help in advance
Click to expand...
Click to collapse
djona12 said:
Can't help you with the European system
But have you tried flashing B20 boot.img from tenfar tool ? Might solve your wifi issue...
If that works, it's awesome !
Click to expand...
Click to collapse
the A2017G have a FULL FACTORY UPDATE IMAGE (B02) you guys are actually lucky in that department, us A2017U we wish had one.
here : http://forum.xda-developers.com/axon-7/how-to/a2017g-b02-update-released-europe-t3440619
i cannot seem to find tenfar tool anywhere
DrakenFX said:
the A2017G have a FULL FACTORY UPDATE IMAGE (B02) you guys are actually lucky in that department, us A2017U we wish had one.
here : http://forum.xda-developers.com/axon-7/how-to/a2017g-b02-update-released-europe-t3440619
Click to expand...
Click to collapse
i have found the tool but i think i flashed the US version of the boot image now my phone does not boot up at all,
it goes to stock recovery
if i turn the phone on then it goes to ZTE LOGO for about half a second then the screen goes blank
i can access fastboot but only through stock recovery which when i go to bootloader i cannot run any fastboot commands, even if i run fastboot reboot it does not reboot the phone at all
shia786 said:
i cannot seem to find tenfar tool anywhere
Click to expand...
Click to collapse
Got the same problem, i've formatted the system and now i can only go to the stock recovery, i can't reboot to edl mode by pressing both volume buttons doing this a Handset Diagnostic Interface (DFU) appears in my Device Manager instead of Qualcomm USB device, so i can't install a TWRP.
shia786 said:
i cannot seem to find tenfar tool anywhere
Click to expand...
Click to collapse
Cricius said:
Got the same problem, i've formatted the system and now i can only go to the stock recovery, i can't reboot to edl mode by pressing both volume buttons doing this a Handset Diagnostic Interface (DFU) appears in my Device Manager instead of Qualcomm USB device, so i can't install a TWRP.
Click to expand...
Click to collapse
As I said before, YOU GUYS have full update file posted the link (thread) about... You DON'T need @tenfar tools to use the FULL A2017G update (B02) , download the file (like 2.2gb I guess) and flashed using stock recovery.
DrakenFX said:
As I said before, YOU GUYS have full update file posted the link (thread) about... You DON'T need @tenfar tools to use the FULL A2017G update (B02) , download the file (like 2.2gb I guess) and flashed using stock recovery.
Click to expand...
Click to collapse
When I press update from SD card it comes up with cannot update from SD card, when I try to do ADB side load and says cannot read file
shia786 said:
When I press update from SD card it comes up with cannot update from SD card, when I try to do ADB side load and says cannot read file
Click to expand...
Click to collapse
Try enable " OEM Unlocking " under developers option and try again
DrakenFX said:
Try enable " OEM Unlocking " under developers option and try again
Click to expand...
Click to collapse
I cannot access the software at all, all I got is stock recovery
shia786 said:
I cannot access the software at all, all I got is stock recovery
Click to expand...
Click to collapse
Try using that same full update with twrp,
As title said you can boot only to TWRP? From there you may be able to flash the zip.
DrakenFX said:
Try using that same full update with twrp,
As title said you can boot only to TWRP? From there you may be able to flash the zip.
Click to expand...
Click to collapse
I no longer have access to TWRP recovery as I flashed stock recovery to install the firmware file using stock recovery but somehow the os got screwed up and now the only thing I have access to is stock recovery
shia786 said:
I no longer have access to TWRP recovery as I flashed stock recovery to install the firmware file using stock recovery but somehow the os got screwed up and now the only thing I have access to is stock recovery
Click to expand...
Click to collapse
You can just boot into TWRP using tenfar tools and Flash the zip.
DrakenFX said:
You can just boot into TWRP using tenfar tools and Flash the zip.
Click to expand...
Click to collapse
For me to use the tool I need to access the phone in edl mode which I cannot do because I do not have access to ADB
shia786 said:
For me to use the tool I need to access the phone in edl mode which I cannot do because I do not have access to ADB
Click to expand...
Click to collapse
and not having access to adb, you meant don't have a PC/Laptop?
Cuz there is an alternative way how to boot to " edl "
- turn your phone completely off
- press and hold Volume DOWN & UP
- plug your device to your PC/Laptop
DrakenFX said:
and not having access to adb, you meant don't have a PC/Laptop?
Cuz there is an alternative way how to boot to " edl "
- turn your phone completely off
- press and hold Volume DOWN & UP
- plug your device to your PC/Laptop
Click to expand...
Click to collapse
so what i mean by i cannot access ADB is that the phone has stock recovery in which there is no ADB functionality, i cannot access the OS so i cannot use ADB that way either,
i tried the method above to go into edl mode but it just goes onto a black screen where the led light flashed red and green and the computer does not recognise anything being plugged in, not even the system sound,
I have the correct drivers installed as i used his before when the OS was working
shia786 said:
so what i mean by i cannot access ADB is that the phone has stock recovery in which there is no ADB functionality, i cannot access the OS so i cannot use ADB that way either,
i tried the method above to go into edl mode but it just goes onto a black screen where the led light flashed red and green and the computer does not recognise anything being plugged in, not even the system sound,
I have the correct drivers installed as i used his before when the OS was working
Click to expand...
Click to collapse
Hi,
I have the exact same issue
Did you find a way to get your phone booting again ?
DrakenFX said:
and not having access to adb, you meant don't have a PC/Laptop?
Cuz there is an alternative way how to boot to " edl "
- turn your phone completely off
- press and hold Volume DOWN & UP
- plug your device to your PC/Laptop
Click to expand...
Click to collapse
That doesn't work on the A2017G, you have to use "adb reboot edl", so you see the problem. Also, the A2017G doesn't actually have an EDL mode but something very similar that's ZTE call Handset diagnostic Interface - quite why, who knows, this is ZTE after all...

My lenovo a6000 is hard bricked. PC not detecting it.

Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?
arnab8820 said:
Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?
Click to expand...
Click to collapse
Try qfil method
JovanSijacki said:
Try qfil method
Click to expand...
Click to collapse
Can you give the link please..... please note the phone is no longer detected in pc
arnab8820 said:
Can you give the link please..... please note the phone is no longer detected in pc
Click to expand...
Click to collapse
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.
I already have installed the drivers. Still not detected. Even the device manager does not show a device is connected
sasukay said:
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.
Click to expand...
Click to collapse
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.
arnab8820 said:
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.
Click to expand...
Click to collapse
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.
sasukay said:
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.
Click to expand...
Click to collapse
There is only one pcb in it. Changing the cable does not make a difference
One update. I can get into the fastboot mode. But the bootloader is locked. What to do?
arnab8820 said:
One update. I can get into the fastboot mode. But the bootloader is locked. What to do?
Click to expand...
Click to collapse
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful​, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful​, type in
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"
arnab8820 said:
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"
Click to expand...
Click to collapse
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also​ try
Code:
fastboot boot recovery.img
Sometimes only this works which temporarily boots into the custom recovery.
sasukay said:
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also​ try
Sometimes only this works which temporarily boots into the custom recovery.
Click to expand...
Click to collapse
Ok friend i will post the results tonight
sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful​, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Tried the above method but no luck it gives an error: "unknown command or device is lock".
arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?
sasukay said:
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?
Click to expand...
Click to collapse
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed
arnab8820 said:
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed
Click to expand...
Click to collapse
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.
sasukay said:
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.
Click to expand...
Click to collapse
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.
arnab8820 said:
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.
Click to expand...
Click to collapse
Try fastboot oem unlock
arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
I think you are missing something (maybe).
The command is "fastboot flash recovery recovery.img"
If the recovery files name is twrp.img then command will be "fastboot flash recovery twrp.img".

P9 Lite Bricked. Help me!!!

Hello,
I was always a Samsung fanboy, but than I decided to buy the P9 lite (VNS-L21 single sim)
I wanted to flash the android 7 update for my phone, but I was such a noob in Huawei, that I didn't understand a word. But i tried to do what the instructions said. Now my phone is bricked. I can go to recovery, erecovery (which can't download anyithing) and download mode. I heard of this fastboot stuff as well, but I don't know how to do this. I tried to flash as many roms as I could with dload and it didn't work, after 5%, it said it failed... Now I don't know what to do. I think somebody (expert) should make a clear tutorial for noobs. Oh and I almost forgot that i don't have root, custom recovery, and things like that. I just bought the phone, I didn't want to make big changes, just new android. Is it possible that after this Huawei would fix my phone, if I couldn't? Or warranty is void? And sadly I don't know more of my phone because I'm not ina rom, and the phone and papers don't say more.
If you could help me, I would appreciate it:
Raul
Turn off your phone, connect to the pc while holding the volume down button, you will end up in fastboot mode.
I assume you have ADB and drivers installed (if not, install ADB and device drivers).
Optional: unlock your bootloader if it's locked.
Download the latest offical rom zip for your phone version (the marshmallow one), extract the update.app.
Use Huawei extractor to ectract the following files (google is your friend in this one, but its not difficult):
boot.img
recovery.img
cust.img
system.img
After you've done this, connect your phone to the PC in fastboot mode .
Open a command promt from the folder where the extracted files are (shift+right click, Open Command window here), enter the following commands
fastboot devices (you will see the list of attached devices with a lot of random number + fastboot)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
fastboot reboot
After all this, you should be good to go, just be sure you are using the correct rom for you version.
Or you can just serach on the forum and find this.
https://forum.xda-developers.com/huawei-p9lite/help/unbricking-vns-l21-vns-l31-tutorial-t3583400
(Sorry for my english.)
Fastboot says that it has failed command not alllowed, after I want to installl the files. And I couldn't unlock bootloader without phones information...
rr999999 said:
I would happily unlock my bootloader, but I don't know anyithing about my phone (except model...) without the os...
Click to expand...
Click to collapse
Post here IMEI and SN from the box of phone and i can try get your bootloader unlock code...
If I would unlock it, would fastboot work? Because fastboot pc app recognizes my phone, but my phone says in fastboot mode, that I should connect itself to pc and open hisuite. WTF?
rr999999 said:
If I would unlock it, would fastboot work? Because fastboot pc app recognizes my phone, but my phone says in fastboot mode, that I should connect itself to pc and open hisuite. WTF?
Click to expand...
Click to collapse
Until you have bootloader unlock you can not run any fastboot flash command...
rr999999 said:
If I would unlock it, would fastboot work? Because fastboot pc app recognizes my phone, but my phone says in fastboot mode, that I should connect itself to pc and open hisuite. WTF?
Click to expand...
Click to collapse
Heyho,
normally yes, after bootloader unlock u are able to flash via fastboot. But...
I tried to flash as many roms as I could with dload and it didn't work, after 5%, it said it failed...
Click to expand...
Click to collapse
What is the error? - Have u disconnected the device from the PC during the update?
If not, try to update again and just disconnect the device from any USB connection...
Regards,
Sebastian
k1ll3r8e said:
Heyho,
normally yes, after bootloader unlock u are able to flash via fastboot. But...
What is the error? - Have u disconnected the device from the PC during the update?
If not, try to update again and just disconnect the device from any USB connection...
Regards,
Sebastian
Click to expand...
Click to collapse
Hello. I disconnected it from everything (for example USB)When I tried to install it said something like incompatibility version, but it couldn't be because I tried many roms for my phone. And I tried some dual sim roms as well because, I thought that it might work... But then I will do that unlock if it will do good. Thanks for the help Without bootloader I can't flash from dload as well?
rr999999 said:
Hello. I disconnected it from everything (for example USB)When I tried to install it said something like incompatibility version, but it couldn't be because I tried many roms for my phone. And I tried some dual sim roms as well because, I thought that it might work... But then I will do that unlock if it will do good. Thanks for the help Without bootloader I can't flash from dload as well?
Click to expand...
Click to collapse
Heyho,
the dload method works always without unlock bootloader. But, u can't flash for example an B161 over an B3xx (what nougat is) if the update u installed modified already the oeminfo u are not able to flash any rom below B3xx (nougat) via dload.
-
In that case u might use the official rollback package (never tested it myself) or, u unlock ur bootloader, flash a TWRP recovery matching to ur current FW. Flash from there a oeminfo + custom.bin (lower than B3xx) and flash the FW matching to the new oeminfo via dload and stock recovery.
Regards,
Sebastian
If you have custom recovery, wipe everything. Data, system, boot. extract update app (which is your stock rom) with huawei update extractor. go to custom recovery, flash stock boot IMG and stock recovery IMG. Power off, use three button dload method, reboot, when booting press vol up for three second, now you are in e-recovery. Press shutdown. Press and hold power and vol up for stock recovery. Do factory reset. If need do the factory reset 2/3 times. Now you are with locked bootloader.
Sent from my NEM-L21 using Tapatalk[/QUOTE]
Sent from my NEM-L21 using Tapatalk

fastboot flashable boot.img

Hi !
I might have erased the boot partion. I still got the unlocked bootloader screen, and can still get in fastboot, but that's it. I can't boot in TWRP. I've tried to flash the boot.img from the stock zip, but it doesn't work... anyway to fix this ? It's the A2017G model. All i need is to get into TWRP.
Exnocte said:
Hi !
I might have erased the boot partion. I still got the unlocked bootloader screen, and can still get in fastboot, but that's it. I can't boot in TWRP. I've tried to flash the boot.img from the stock zip, but it doesn't work... anyway to fix this ? It's the A2017G model. All i need is to get into TWRP.
Click to expand...
Click to collapse
can't you flash recovery? I think someone made a flashable TWRP somewhere
Choose an username... said:
can't you flash recovery? I think someone made a flashable TWRP somewhere
Click to expand...
Click to collapse
I've tried to flash TWRP several time, but it won't boot...
Exnocte said:
I've tried to flash TWRP several time, but it won't boot...
Click to expand...
Click to collapse
you can try getting into EDL and using MiFlash to flash one of the zips on the Russian page 4pda. Go to the debrick page (the one with the phone carnage pictures inside), find the links for the chinese full recovery package. it will get you to the 4pda page. from there find a package that suits your needs (there is one with aboot and fbop) and flaah with MiFlash
Otherwise download the full B10 recovery package and flash it with MiFlash. you won't lose data but it might conflict if you were on Nougat
I'm in this situation for some days...
No EDL, No recovery, only fastboot and FTU modes are accessible.
And we can't flash via Miflash. It sees the phone only in fastboot mode, and can't flash it.
 @op : 2 ways to recover :
- Test points method to force EDL and flash via miflash
- Return to ZTE
If any1 has other solutions ...
FYI : My tests so far :
- Flash boot / reboot / flash recovery : Stuck on ZTE logo, red led on permanently
- Hot load recovery (fastboot boot twrp.img): Command unknown
- Format userdata/cache : No work
- Flash via Miflash in fastboot : "Can't find Eraseall except Data.bat"
- Change drivers by some others one : No luck
Sn8K said:
I'm in this situation for some days...
No EDL, No recovery, only fastboot and FTU modes are accessible.
And we can't flash via Miflash. It sees the phone only in fastboot mode, and can't flash it.
@op : 2 ways to recover :
- Test points method to force EDL and flash via miflash
- Return to ZTE
If any1 has other solutions ...
FYI : My tests so far :
- Flash boot / reboot / flash recovery : Stuck on ZTE logo, red led on permanently
- Hot load recovery (fastboot boot twrp.img): Command unknown
- Format userdata/cache : No work
- Flash via Miflash in fastboot : "Can't find Eraseall except Data.bat"
- Change drivers by some others one : No luck
Click to expand...
Click to collapse
I don't know what you mean with FTU mode, but if FTM is meant you should be able to send a "reboot edl" command to activate the EDL mode.
tron1 said:
I don't know what you mean with FTU mode, but if FTM is meant you should be able to send a "reboot edl" command to activate the EDL mode.
Click to expand...
Click to collapse
Humm ... Early morning for me ... i meant DFU. Vol+ & - while powering the phone Result on a black screen, and driver is recognized as Handset Diagnostic Driver (DFU COm port x)
Ind in that kind of brick, FTM is not accessible either.
tron1 said:
I don't know what you mean with FTU mode, but if FTM is meant you should be able to send a "reboot edl" command to activate the EDL mode.
Click to expand...
Click to collapse
Yeah that pretty much sums it up. If you get ZTE handset diagnostic driver on Ports COM&LPT you'll have to take your device apart and use the test point. If it is recognized as Qualcomm HS-USB QDLoader 9008 it means that you're on EDL. I'd reccomend trying to use miflash like i described, if it doesn't work return it or take it apart
Maybe a bit late for a reply, but I was able to get out of a similar situation (from DFU) by holding power and volume down for a long time. That got me to FTM and then I could reboot into edl via "adb reboot edl". Then I used the Axon7toolkit to flash fastboot and from there I could get to twrp and back in business. Any questions, let me know.
@Piet : How long for the PWR+DWN ? I've tried for something like 40/45 seconds, without success.
Sn8K said:
@Piet : How long for the PWR+DWN ? I've tried for something like 40/45 seconds, without success.
Click to expand...
Click to collapse
From what I read you have to let the device discharge totally, then you can get ftm. I had my battery fully charged when i bricked so i just did the 4th categ unbricking process

QFIL to Leeco le pro 3 (Lex722)

Hello everyone!
my problem is the next: I tried install a rom of MIUI but fail in my device, after, I tried to install differents roms but nothing work, just showed me the logo Leeco and no more, no avance from the logo.
But I still had recovery with TWRP and I thinked I can install official rom 26s, It was my error.
Now follow with the same problem but now I not have recovery mode (show me recovery with logo Leeco but it instantly turns off ) and bootloader is block.
My only hope, is QFIL to recover recovery mode o any rom, Does anyone have it or tell me how to create one?..
Please anybody will can help me, I have this problem 3 days ago.
Sorry for my bad english, I am learning.
PS. I tried with post of tora33 but no work
FlashOne2.0\le_zl1_qfil_ufs\prog_ufs_firehose_8996_ddr.elf"
22:00:34: ERROR: function: rx_data:247 Error occurred while reading from COM port
22:00:34: ERROR: function: sahara_main:854 Sahara protocol error
22:00:34: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Click to expand...
Click to collapse
Are you sure you got Qualcomm drivers installed and your phone is in 9008 mode? Also try rebooting and re-enter 9008 mode. But the biggest problem that there is no qfil restoration files for x722 if I remember correctly, chances to boot with x720 ones are quite low.
Does your fastboot work volume and power down same time??
Sent from my LEX727 using xda premium
---------- Post added at 11:09 AM ---------- Previous post was at 10:53 AM ----------
worked on the phone i got off amazon. thanks!
[quote name="wpbear" post=71566961]This works on lastest USA update Stock (21s).
Have ADB/Fasboot tools on your computer
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device
Put emmc_appsboot.mbn from this zip (Download: x727-5.8.019s_bootloader-unlock.zip) in your adb directory on your PC
Put twrp.img from this zip (Download: TWRP) in your adb directory on your PC
On PC open admin CMD prompt
go into fastboot mode on phone (hold power and VOL -)
on PC type:
fastboot devices
fastboot flash aboot emmc_appsboot.mbn
after flash force reboot using Power button. It will ask for a password, just ignore it and reboot back to fastboot by forcing power down then reboot to fastboot (hold power and VOL -)
on PC type:
fastboot devices
fastboot oem unlock-go
fastboot flash recovery twrp.img
boot into twrp (force power down, then hold POWER and VOL +)
TWRP will boot, choose modify system. Choose wipe - then swipe to factory reset, when that is done - then advacned then format data
In TWRP ensure MTP is enabled. In Windows File Explorer the phone should be visibile. Drag and Drop your new ROM.zip, gapps.zip, SU.zip etc...
In TWRP INSTALL new ROM and other zips; choose wipe/dalvik/cache
If you unlock bootloader push power off until it goes off then put it back into fastboot flash twrp .img them power off again power on when phone vibrate volume down you see stock recovery then twrp.
Reboot System.
DONE![/QUOTE]
Sent from my LEX727 using xda premium
voron00 said:
Are you sure you got Qualcomm drivers installed and your phone is in 9008 mode? Also try rebooting and re-enter 9008 mode. But the biggest problem that there is no qfil restoration files for x722 if I remember correctly, chances to boot with x720 ones are quite low.
Click to expand...
Click to collapse
Yeah, that is the problem, I have the drivers and my computer recognize it, the problem, always show the error sahara.
And flash in fastboot no work because bootloader is block and not let me to do flash of anything.
Someone know how to create a qfil? I am developer and I could try but I not found tutorial how to do and I do not have it clear.
zeckAlexs said:
Yeah, that is the problem, I have the drivers and my computer recognize it, the problem, always show the error sahara.
And flash in fastboot no work because bootloader is block and not let me to do flash of anything.
Someone know how to create a qfil? I am developer and I could try but I not found tutorial how to do and I do not have it clear.
Click to expand...
Click to collapse
Every so often the same questions and the same answers.
You should read more. The X722 subforum is for something.
There is no qfil for X722, and there are no magic solutions of X720 / X727. This is an X722, it is locked and NOTHING of X720 / X727 is going to fix it.
Read this:
https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
Greetings.
How do people keep ending up with bricks? Guess I'll have to find a mod to contact them about stickying a thread about the x722 here about stock 26s. It's a bad idea. Never update your x722 to stock 26s, because your bootloader will get locked when you try to flash TWRP. The only way to get out of 26s is to flash Batyan's 01D ROM (in the x722 Development section here), and then unlock your bootloader and flash TWRP. Flashing TWRP over stock 26s will cause a permanent brick because there's absolutely no QFIL file available for this device. Even in China.
sk8223 said:
How do people keep ending up with bricks? Guess I'll have to find a mod to contact them about stickying a thread about the x722 here about stock 26s. It's a bad idea. Never update your x722 to stock 26s, because your bootloader will get locked. The only way to get out of 26s is to flash Batyan's 01D ROM (in the x722 Development section here), and then unlock your bootloader and flash TWRP. Flashing TWRP over stock 26s will cause a permanent brick because there's absolutely no QFIL file available for this device. Even in China.
Click to expand...
Click to collapse
You know I don't really know how they keep doing it but I seen a lot new ones getting this phone and not really studying how to do this stuff and their not paying attention to what model this have this a solid phone.
Sent from my LEX720 using xda premium
This is true ?
https://dc5.androidfilehost.com/dl/...40/818070582850488404/le_zl1_qfil_ufs_fix.zip
paiktaras said:
This is true ?
https://dc5.androidfilehost.com/dl/...40/818070582850488404/le_zl1_qfil_ufs_fix.zip
Click to expand...
Click to collapse
ZL1 its x720/x727 not x722, it's a fix for ppl thata not work the normal qfil rom.

Categories

Resources