Axon 7 bricked after installing TWRP - ZTE Axon 7 Questions & Answers

Hi! I am following this guide: https://www.droidviews.com/unlock-bootloader-install-twrp-and-root-zte-axon-7-a2017g/, and after using the axon7tool to install TWRP my device seems to be bricked and only shows up as QUSB_BULK in device manager - as if its in EDL mode. Adb doesn't recognize it - and the axon7tool throws a runtime error, I have seen previously when it couldn't detect the device
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
Click to expand...
Click to collapse
. I have tried using the MiFlashtool but I can't seem to find the right ROM - it always gives me a couldn't find flash script error. I have tried using both the Qualcomm and both ADB axon7 USB drivers (https://androidfilehost.com/?w=file...2ca06f4305d7074d4465bc289db2d49d5f99cdde608bf) and both of them yield the exact same result. What should be my next step of action, should I try to save the current firmware or get MiFlashTool working?

Update: let the phone die, then I booted into android, used abd to get into EDl which again showed a blackscreen and the edl tool nor miflash seem to be able to work as if its not in edl but in DFU and the DFU multitool cant get it out of there. Booting by pressing the volume up button and power button, causes a blackscreen with the same problem.

Related

HELPPPP!!!

hello guys, well i got a huge problem, i bricked the zuk z1, i tried to flash the system.img with adb, and it failed. now i cant get into recovery, can't get into fastbood, when i use the command "adb devices" it says "509cad02 unauthorized"
please tell me there's a way to fix it! please:crying:
Just follow this tutorial to unbrick your phone :
Link : http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
Zui Qfil ROM : https://yadi.sk/d/IistjFPhyrg7N
If Cm qfil doesn't boot then try with zui qfil ?
I tried, but it says download failed switch to edl, when i try to switch into edl by using adb it says that the device is unauthorized
hadef said:
hello guys, well i got a huge problem, i bricked the zuk z1, i tried to flash the system.img with adb, and it failed. now i cant get into recovery, can't get into fastbood, when i use the command "adb devices" it says "509cad02 unauthorized"
please tell me there's a way to fix it! please:crying:
Click to expand...
Click to collapse
https://mega.nz/#!RFUw2CbZ!GXS6KeOy_8n2y_rOBJUS5WJSP5kchODcGUF0U1TxYO8
Download this package, drivers and download qfil
Load xml file firehose file
Turn off your device press holding volume up and connect to pc
Then press download
You are back to stock cyanogen OS

Hell to unlock Bootloader Please...

Hi there,
i'd Like to flash the Ressurection Remix Oreo Rom, but i don't get it to unlock the bootloader. I'm on Stock A2017GV1.2.0B10 Nougat. TWRP and Backups are done, but when i try to unlock the Bootloader i geht this message in cmd:
adb: error: connect failed: no devices/emulators found
Tried with Zadigs Drivers, ADB divers are installed and it is showed as QS_Bulk.
Are there still some drivers missing or what am I doing wrong there???
Did you enable USB Debugging on your phone?
Victor13f said:
Did you enable USB Debugging on your phone?
Click to expand...
Click to collapse
Yes, i have OEM unlock and USB Debugging enabled. Dont understand why this is not working at all. Tried it many times, but every Try I get this message in the CMd. Sideload isn't working too...
Have you installed the Google USB drivers and checked in Device manager if everything is working okay? Here's a link to a guide: https://www.drivereasy.com/knowledge/solved-adb-device-not-found-error-on-windows/
HeikoNote3 said:
Yes, i have OEM unlock and USB Debugging enabled. Dont understand why this is not working at all. Tried it many times, but every Try I get this message in the CMd. Sideload isn't working too...
Click to expand...
Click to collapse
Just use the EDL Tool from @djkuz, install it, put your phone into EDL mode and unlock.
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
raystef66 said:
Just use the EDL Tool from @djkuz, install it, put your phone into EDL mode and unlock.
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Click to expand...
Click to collapse
So, Tried this one too. Doesn't work, phone isn't found, error adb interface not found...
HeikoNote3 said:
So, Tried this one too. Doesn't work, phone isn't found, error adb interface not found...
Click to expand...
Click to collapse
Uninstall all drivers you see relating to your phone (adb, usb...)
Try install : http://adbdriver.com/downloads/
And https://androidfilehost.com/?fid=24588232905723896
And see if you can perform with the EDL Tool again or adb
raystef66 said:
Uninstall all drivers you see relating to your phone (adb, usb...)
Try install : http://adbdriver.com/downloads/
And https://androidfilehost.com/?fid=24588232905723896
And see if you can perform with the EDL Tool again or adb
Click to expand...
Click to collapse
Installed the ADB Drivers but in EDL tool the Phone is not recognised. Dont know what could the Problem...
HeikoNote3 said:
Installed the ADB Drivers but in EDL tool the Phone is not recognised. Dont know what could the Problem...
Click to expand...
Click to collapse
First boot into twrp, connect your phone, run the EDL Tool. Normaly the tool should reboot itself into EDL mode
Or try : run EDL tool, instead of power off phone, hold vol down+power, connect usb, just do the same by holding the 3 buttons ( i did that once when my phone was in a state of 'shock' and the 2 button way didn't work)
Btw, did you install the 2 drivers i gave you ?
raystef66 said:
First boot into twrp, connect your phone, run the EDL Tool. Normaly the tool should reboot itself into EDL mode
Or try : run EDL tool, instead of power off phone, hold vol down+power, connect usb, just do the same by holding the 3 buttons ( i did that once when my phone was in a state of 'shock' and the 2 button way didn't work)
Btw, did you install the 2 drivers i gave you ?
Click to expand...
Click to collapse
Yes they're installed. I'm wondering that edl tool shows first ZTE ADB handset etc. And after boot into edl mode it shows no ADB interface... With axon7tool I can choose unlock Bootloader, then MI flash starts and then I don't know the files to flash for an unlock...
HeikoNote3 said:
Yes they're installed. I'm wondering that edl tool shows first ZTE ADB handset etc. And after boot into edl mode it shows no ADB interface... With axon7tool I can choose unlock Bootloader, then MI flash starts and then I don't know the files to flash for an unlock...
Click to expand...
Click to collapse
MiFlash? Where did you read that you had to use MiFlash? ?
You need to use EDL Tool
Edit: Okay, I think I got it. You thought "EDL Tool" was actually axon7toolkit. Well, it isn't. Axon7toolkit, axon7tool, and EDL Tool are 3 different things
Choose an username... said:
MiFlash? Where did you read that you had to use MiFlash?
You need to use EDL Tool
Edit: Okay, I think I got it. You thought "EDL Tool" was actually axon7toolkit. Well, it isn't. Axon7toolkit, axon7tool, and EDL Tool are 3 different things
Click to expand...
Click to collapse
OK, then which tool should I prefer now? In EDL tool I was on a good way to unlock the Bootloader, but when I choose Yes, the unlock begins with load programmer something and stucks until I reboot EDL mode. Then it gives me an error message with: your device could be in Sahara mode. I don't understand anything anymore. Tried every driver, every tool but nothing will work. That drives me crazy...
HeikoNote3 said:
OK, then which tool should I prefer now? In EDL tool I was on a good way to unlock the Bootloader, but when I choose Yes, the unlock begins with load programmer something and stucks until I reboot EDL mode. Then it gives me an error message with: your device could be in Sahara mode. I don't understand anything anymore. Tried every driver, every tool but nothing will work. That drives me crazy...
Click to expand...
Click to collapse
Did you enable OEM unlock and USB debugging?
If you did and it still does that error, just use the manual method and follow Controllerboy's guide. That one uses axon7tool, which is much more finicky and ran by commands, but it works
Thanks for all Tipps. Finally did it. Running RR Oreo!

Can't Get into EDL even with ADB

I have an A2017U, Android 7.1.1, build B35, on MiFavor 4.2 and was looking to upgrade to 5.2/Oreo. I get stuck because I can't boot into EDL mode. I have not unlocked the phone but do have developer options & USB debugging enabled. If I boot with vol up + vol down + power, nothing happens even if I wait 120 seconds. I get a slowly flashing red dot. ADB works fine -- my device is recognized -- and "adb reboot EDL" reboots the phone, but not into EDL mode, just into standard mode. MiFlash doesn't see the phone.
I'm clearly doing something wrong but I'm at a loss what, given how simple the instructions are.
prestonmcafee said:
I have an A2017U, Android 7.1.1, build B35, on MiFavor 4.2 and was looking to upgrade to 5.2/Oreo. I get stuck because I can't boot into EDL mode. I have not unlocked the phone but do have developer options & USB debugging enabled. If I boot with vol up + vol down + power, nothing happens even if I wait 120 seconds. I get a slowly flashing red dot. ADB works fine -- my device is recognized -- and "adb reboot EDL" reboots the phone, but not into EDL mode, just into standard mode. MiFlash doesn't see the phone.
I'm clearly doing something wrong but I'm at a loss what, given how simple the instructions are.
Click to expand...
Click to collapse
Try "adb reboot edl" from a booted phone.
EDL actually IS a black screen, usually without an LED though it might be red. Open Device manager and check under "unrecognized devices", or under "Ports (COM & LPT)". Should be there. If it is under Ports and it is callee Qualcomm HS-USB QDLoader 9008 then MiFlash should work
What are you planning to do? EDL back to B19 then unlock? Just curious
Choose an username... said:
Try "adb reboot edl" from a booted phone.
EDL actually IS a black screen, usually without an LED though it might be red. Open Device manager and check under "unrecognized devices", or under "Ports (COM & LPT)". Should be there. If it is under Ports and it is callee Qualcomm HS-USB QDLoader 9008 then MiFlash should work
What are you planning to do? EDL back to B19 then unlock? Just curious
Click to expand...
Click to collapse
I plan to update to Oreo/MiFavor 5.2.
How do I issue the command from a phone? I know how to use ADB from a PC but not from a phone. That is what I have done -- enable developer options, connect the phone, verify that it is connected (adb devices) and then issue the command (adb reboot EDL).
Use the Edl tool by Djkuz
Install it to PC or laptop with all updated drivers
Open edl tool with run as admin
Boot your phone into ftm
Turn your phone off
Press and hold vol dn + power till you see ftm screen
Plug in your phone
Follow the on screen till it detects your phone
Select unlock then edl fix
Edl tool is here
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
prestonmcafee said:
I plan to update to Oreo/MiFavor 5.2.
How do I issue the command from a phone? I know how to use ADB from a PC but not from a phone. That is what I have done -- enable developer options, connect the phone, verify that it is connected (adb devices) and then issue the command (adb reboot EDL).
Click to expand...
Click to collapse
Yes, but what are you going to do BEFORE updating to MF5.2?
you can't edl mifavor 5.2 because you will break stuff, besides you need an unlocked bootloader or you'll DFU brick your phone and you'll have to throw it in the trash.
I meant to issue adb reboot edl from your pc but with your phone on
On a side note, I recommend not using EDL Tool or axon7toolkit to unlock your phone. EDL Tool has a much better track record than other apps but it still has margin for error. The best way to unlock an A2017U is get a B19 EDL package and install it with MiFlash, then enter Fastboot and do "fastboot oem unlock".
Worked!
Syberclone said:
Use the Edl tool by Djkuz
Install it to PC or laptop with all updated drivers
Open edl tool with run as admin
Boot your phone into ftm
Turn your phone off
Press and hold vol dn + power till you see ftm screen
Plug in your phone
Follow the on screen till it detects your phone
Select unlock then edl fix
Edl tool is here
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Click to expand...
Click to collapse
That worked, thanks!
Ive used all of the Axon 7 tools as well as adb commands and all work well in there own ways.
Script errors or command errors can be an issue as well as some software (ROMs, recovery and boot imgs) a few times I've had to edit a zip or img to make it work.
After a few boot loops on my HTC.
Is there an official MiFavor Update on 5.2?
My phone is still on 4.2 and can't find any updates.
SebaSnow said:
Is there an official MiFavor Update on 5.2?
My phone is still on 4.2 and can't find any updates.
Click to expand...
Click to collapse
only for Chinese (A2017) phones. It's 8.0 mifavor with the new mf5.0 interface (way more Chinese-looking). If you want to install it on a G or U you'll have to use one of the packages made for them (Usually for an update from other model to work you need to change its modem file to the one that your model uses, i.e. swap the chinese modem with the G's).

your device is corrupted and cannot be trusted and may not work properly

Hi all, I ended up with this:
"your device is corrupted and cannot be trusted and may not work properly"
I can access Fastboot mode but can't flash any TWRP
Any help?
I tried to install LOS with Universal Bootstack...and Axon 7 Tool open a window just for one second so I can't access the command
amus76 said:
Hi all, I ended up with this:
"your device is corrupted and cannot be trusted and may not work properly"
I can access Fastboot mode but can't flash any TWRP
Any help?
I tried to install LOS with Universal Bootstack...and Axon 7 Tool open a window just for one second so I can't access the command
Click to expand...
Click to collapse
All right, do this:
-Put the phone in Fastboot
-Open command prompt
-Run "fastboot erase userdata"
If it doesn't work, do this:
-Set up a TWRP on your fastboot folder (rename it to "recovery.img" [BE SURE THAT YOUR PC SHOWS FILE NAME EXTENSIONS] and put it on the folder where fastboot is located)
-Open command prompt in the folder where Fastboot is located
-Run this command:
fastboot boot recovery.img
Your phone should enter TWRP. It's not installed, it just boots it once.
Then try to format data from TWRP. Right after that, use "adb push recovery.img /sdcard" to push the recovery img to your internal storage. Then go (on your twrp) to "Install" - hit "Install image", then select the recovery.img, and select "recovery" and swipe to confirm.
After it is done, install LOS again. If it is 15.1 or 16 you have to have a Vendor compatible TWRP, such as Ordenkrieger's TWRP (From LOS16 thread). Follow the instructions precisely
As soon as TWRP is flashed, i get the warning screen with : "your device is corrupted and cannot be trusted and may not work properly"
And no recovery then after reboot
No FTM mode and I can't enter EDL
And I have to say my device is recgnised as DFU by the PC so maybe trying the EDL cable?
amus76 said:
As soon as TWRP is flashed, i get the warning screen with : "your device is corrupted and cannot be trusted and may not work properly"
And no recovery then after reboot
No FTM mode and I can't enter EDL
And I have to say my device is recgnised as DFU by the PC so maybe trying the EDL cable?
Click to expand...
Click to collapse
yes, an edl cable might work. Otherwise I think you can get some fastboot images and attempt to install them to the right locations
Did you do "fastboot boot recovery.img"? It shouldn't reboot the phone. TWRP should appear right after the transfer is done
If you still have access the fastboot
Enter, reboot dm-verity enforcing
Check here
https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-15-1-zte-axon-7-t3800214
Choose an username... said:
yes, an edl cable might work. Otherwise I think you can get some fastboot images and attempt to install them to the right locations
Did you do "fastboot boot recovery.img"? It shouldn't reboot the phone. TWRP should appear right after the transfer is done
Click to expand...
Click to collapse
I did the fastboot boot recovery.img the phone reboot, i get the warning screen for unlocked bootloader and straight after "your device is corrupted and cannot be trusted and may not work properly" with the same style as the bootloader warninr screen.
So without a recovery I can't flash fastboot images
For those in my case:
When you get the warning screen with the red message, just push once the button power, a Linux logo will appear, and another push on the button will boot you in TWRP
I didn't manage to get the command to work : adb reboot "dm-verity enforcing", I tried Terminal in TWRP but with no luck.
Did you get access to Edl mode, via button combo or through adb?
If not can you get to the FTM screen?
I know you couldn't access these earlier, has that changed?
Also what apps do you have?
Edl tool?
Axon 7 tool kit (you did mention this)
Miflash?
Qualcomm drivers and Zadig drivers?
Syberclone said:
Did you get access to Edl mode, via button combo or through adb?
If not can you get to the FTM screen?
I know you couldn't access these earlier, has that changed?
Also what apps do you have?
Edl tool?
Axon 7 tool kit (you did mention this)
Miflash?
Qualcomm drivers and Zadig drivers?
Click to expand...
Click to collapse
I didn't get access to EDL mode even through ADB, nor FTM screen. So MiFlash is useless
With Axon 7 tool, I tried to flash TWRP with no success, my phone was on DFU
Then I managed to dm-verity encrypted through ADB but the phone was not rebooting on recovery, still fastboot but the phone was not recognize by the PC
I have Qualcomm Drivers installed
Right now with Lineage, I can't acces FTM screen
I just pushed the button twice when I was with the red warninr screen and get access to TWRP (or Lineage boot screen)
Try installing the Zadig drivers and the bulk USB drivers for the axon to help detect the correct device.
Then see if the Axon tool kit will work properly.
DFU mode shows for a number of reasons.
In your windows device manager it needs to show
"Qualcomm HS-USB QDLoader 9008" if all drivers are setup properly.
When I soft bricked mine I was trying to install Los 15.1
I had the corrupt device message you are getting.
I used all 3 apps to eventually get mine running.
I made sure all drivers were installed and up to date, I switched between the Axon tool kit, edl tool and Miflash to get my laptop to recognise.
I ran the Axon tool kit to setup adb (a few attempts before it worked)
I then ran Edl tool to get some form of Edl
Then ran Miflash (latest version) I had to try this several times too (constant error messages) it finally started the flash process but would fail (I was using the turkdev edl)
I swapped it for the B12 Edl on Raystefs page and it worked, I then had to reflash with the correct modem though.
Anyway I truly hope you get it sorted
Syberclone said:
Try installing the Zadig drivers and the bulk USB drivers for the axon to help detect the correct device.
Then see if the Axon tool kit will work properly.
DFU mode shows for a number of reasons.
In your windows device manager it needs to show
"Qualcomm HS-USB QDLoader 9008" if all drivers are setup properly.
When I soft bricked mine I was trying to install Los 15.1
I had the corrupt device message you are getting.
I used all 3 apps to eventually get mine running.
I made sure all drivers were installed and up to date, I switched between the Axon tool kit, edl tool and Miflash to get my laptop to recognise.
I ran the Axon tool kit to setup adb (a few attempts before it worked)
I then ran Edl tool to get some form of Edl
Then ran Miflash (latest version) I had to try this several times too (constant error messages) it finally started the flash process but would fail (I was using the turkdev edl)
I swapped it for the B12 Edl on Raystefs page and it worked, I then had to reflash with the correct modem though.
Anyway I truly hope you get it sorted
Click to expand...
Click to collapse
Thanks a lot, I have it sorted!
But what strange is a lot of people is facing this problem recently in a short time
amus76 said:
Thanks a lot, I have it sorted!
But what strange is a lot of people is facing this problem recently in a short time
Click to expand...
Click to collapse
Can I ask how you got it fixed? I would be handy to know for others that end up in this position.
Syberclone said:
Can I ask how you got it fixed? I would be handy to know for others that end up in this position.
Click to expand...
Click to collapse
Just with "dm-verity enforcing" with ADB
Then: press button power when on the red warning, a pinguin will appear and again press the power button, it will reboot on TWRP or Lineage
My fasbtoot was inefficient a part for the dm-verity enforcing, no FTM also
amus76 said:
For those in my case:
When you get the warning screen with the red message, just push once the button power, a Linux logo will appear, and another push on the button will boot you in TWRP
I didn't manage to get the command to work : adb reboot "dm-verity enforcing", I tried Terminal in TWRP but with no luck.
Click to expand...
Click to collapse
I know this is an old reply, but I arrive from a google search. Sir, thanks a lot for this reply. I was stuck in your same situation and pressing the power button with the linux icon allowed me to go to TWRP. THANKS!
I get the pinguin, but if i press Power again, nothing happened. I have to wait for a while it reboots to System. I tried to hold Power while it is rebooting, but it always reboots to System. No chance to enter twrp...

Need some help after messing up my Lineage OS installation on A2017U

My phone has no OS. Factory reset is unavailable to my knowledge (attempted volume up and power).
I can go into fastboot and TWRP, but I can't seem to install the stock OS nor Lineage OS. In fastbootmode, I see the following
Product name - AILSA_II
Variant - MTP eMMC
Bootloader version -
Baseband Version -
Serial Number 9e28c2da
Secure Boot - enabled
Device State - unlocked
Click to expand...
Click to collapse
I cannot use ADB commands. My phone isn't listed under ADB devices. EDL does not work. However in Fastboot mode, MiFlash recognizes a device 9e28c2da. Whenever I try to flash a full EDL however, miflash brings up errors saying it cannot find script and it cannot find file.
When attempting to install in TWRP, I get the respective errors "Invalid zip file format!" for "A2017U_B19-NOUGAT_FULL-EDL.zip" when I try to install the stock. When I try to install Lineage, I get "E3004L This package is for device: ailsa_ii,axon7; this device is ."
I am able to successful install A7LOSv1_UniversalBootStack.zip as well as the UniversalBootstack by DrakenFX. I then install OreoModem.zip after that, but the phone won't let me install any OS afterwards.
Am I trying to install the wrong arrangement of files? What can I do to get an OS back on my phone?
Firstly it sounds like the drivers need an update.
Try updating the USB drivers and try Zadig drivers as well.
Your PC/laptop should see your phone as ...
"Qualcomm HS-USB QDLoader 9008"
In the device manager on Windows. If you are using Miflash it should see it as Com 4 or similar.
Make sure you have the correct Edl package for your phone eg: A2017G, A2017U or A2017.
Extract the Edl package using WinZip or Winrar and take note of the folder name and location.
Boot your phone into Edl mode, via button, adb command or using the Edl tool by @djkuz
Open Miflash tap refresh, if it sees com4 or similar you are good to go.
Tap the browse button and pick the Edl package location on your PC/laptop and then tap flash.
The flash will take a few minutes and when done you will get a green flash success.
Unplug your phone and press and hold the power button till it boots.
Hope this helps
If you get stuck,
I have an Edl help page here >
https://forum.xda-developers.com/axon-7/help/bad-flash-help-page-axon-7-t3839700
There are many others on XDA too

Categories

Resources