Help with phone not turning on. Used Axon7tool.exe - ZTE Axon 7 Questions & Answers

Hi,
I wanted to post this in the thread here but I don't have the permissions yet.
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
I was using the axon7tool.exe just for backup and now my phone won't turn on. It shows up in Windows as a USB Serial Bus Device called QUSB_Bulk.
I did not attempt to write to the device, just do a backup and got this error message and now the phone does not turn on. I'm a bit new to this so if anyone can help that would be much appreciated!!!
Code:
Connecting to 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
I saw that other people get this if they don't run as administrator but I am running as administrator.

some more info I'm on A2017U and it was stock nougat b19.

igbee said:
Hi,
I wanted to post this in the thread here but I don't have the permissions yet.
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
I was using the axon7tool.exe just for backup and now my phone won't turn on. It shows up in Windows as a USB Serial Bus Device called QUSB_Bulk.
I did not attempt to write to the device, just do a backup and got this error message and now the phone does not turn on. I'm a bit new to this so if anyone can help that would be much appreciated!!!
Code:
Connecting to 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
I saw that other people get this if they don't run as administrator but I am running as administrator.
Click to expand...
Click to collapse
Did you reboot your device back into EDL mode after you replaced the driver to QUSB__BULK? If not try it as apparently changing the driver mucks up the current EDL state.

bkores said:
Did you reboot your device back into EDL mode after you replaced the driver to QUSB__BULK? If not try it as apparently changing the driver mucks up the current EDL state.
Click to expand...
Click to collapse
I'm not actually sure. Assuming I'm in a mucked up EDL state...any next steps I can try?

igbee said:
I'm not actually sure. Assuming I'm in a mucked up EDL state...any next steps I can try?
Click to expand...
Click to collapse
Just reboot back into EDL mode:
Press and hold power for 10-15 seconds.
Once your device has booted up execute in windows command prompt:
Code:
adb reboot edl
And try again.

bkores said:
Just reboot back into EDL mode:
Press and hold power for 10-15 seconds.
Once your device has booted up execute in windows command prompt:
Code:
adb reboot edl
And try again.
Click to expand...
Click to collapse
THANKS! I didn't know you could long hold to get the device to reboot. Might wait a bit to try again.

igbee said:
Just reboot back into EDL mode:
Press and hold power for 10-15 seconds.
Once your device has booted up execute in windows command prompt:
THANKS! I didn't know you could long hold to get the device to reboot. Might wait a bit to try again.
Click to expand...
Click to collapse
I think there is another way to get EDL to reset itself without having to reboot and stuff, you have to hold the 3 buttons (vol up, vol dn, power) until the red light turns on, then wait 5 secs
That works on A2017Gs

Related

Stuck in RESCUE MODE screen in Huawei p8 lite

Hi everyone!
I think I bricked my phone :crying:
Everytime I try to turn it on I see this on the screen (see pic)
And the worst of all is that my windows laptop doesn't recognize the phone when I connect it via usb, the pc tells me that it's an unknown device and there's an error code 43...
Help me pls!
just press and hold volume up and your phone will restart
cristi.blidariu said:
just press and hold volume up and your phone will restart
Click to expand...
Click to collapse
It's the first thing I did but It didn' work
you must keep press up to 10 sec,i have try this method my self and he work,if is not work,then i suggest you to put i higher version on your sd card and make a force upgrade by press and hold volume button up and down and power button
cristi.blidariu said:
you must keep press up to 10 sec,i have try this method my self and he work,if is not work,then i suggest you to put i higher version on your sd card and make a force upgrade by press and hold volume button up and down and power button
Click to expand...
Click to collapse
I did it but it doesn't work. the phone tells me this everytime:
can you upload a photo with your screen phone were is sow locked?
Fastboot or downloading mode, once your in there you should be able to install a custom recovery if you already did that already go to your computer and find your firmware for your phone online, put it on your sd card and install it from your custom recovery and it should work or a simple factory reset would work IF you DO NOT know what all of this is or how to do it everyone on here should know how to help you
Hostliner said:
Fastboot or downloading mode, once your in there you should be able to install a custom recovery if you already did that already go to your computer and find your firmware for your phone online, put it on your sd card and install it from your custom recovery and it should work or a simple factory reset would work IF you DO NOT know what all of this is or how to do it everyone on here should know how to help you
Click to expand...
Click to collapse
good point
Hostliner said:
Fastboot or downloading mode, once your in there you should be able to install a custom recovery if you already did that already go to your computer and find your firmware for your phone online, put it on your sd card and install it from your custom recovery and it should work or a simple factory reset would work IF you DO NOT know what all of this is or how to do it everyone on here should know how to help you
Click to expand...
Click to collapse
I have the official firmware and everything, I put it all in the sd card and press the up, down and power buttons but it keeps telling me this (see pic) and as I said before my windows laptop doesn't recognize the phone when I connect it via usb, the pc tells me that it's an unknown device and there's an error code 43...
cristi.blidariu said:
can you upload a photo with your screen phone were is sow locked?
Click to expand...
Click to collapse
It doesn't tell me "locked" it only tell my this:
you need to enter in recovery mod and wipe data and cache,keep try by press and hold volume up and power,and you will need to install hi suite on your pc,download this https://mega.nz/#!Pc9zjDYB!X0wTeiFdY-ca70K9tI-b5fYf40LpcVExIEim0Xk9v14 is the adb and fastboot,conect your phone to pc,extract the file an you will find a folder adb,open,press and hold shift and right click,search for open command here it will open a cmd window,now run the command adb reboot bootloader and wait till reboot in to fastboot mod,now run the command fastboot reboot
Download other version of your firmware. Then do a manual installation. An older firmware maybe.
cristi.blidariu said:
you need to enter in recovery mod and wipe data and cache,keep try by press and hold volume up and power,and you will need to install hi suite on your pc,download this https://mega.nz/#!Pc9zjDYB is the adb and fastboot,conect your phone to pc,extract the file an you will find a folder adb,open,press and hold shift and right click,search for open command here it will open a cmd window,now run the command adb reboot bootloader and wait till reboot in to fastboot mod,now run the command fastboot reboot
Click to expand...
Click to collapse
What's the password? the site asks me for a password
HeyAnas98 said:
What's the password? the site asks me for a password
Click to expand...
Click to collapse
try this https://mega.nz/#!Pc9zjDYB!X0wTeiFdY-ca70K9tI-b5fYf40LpcVExIEim0Xk9v14
cristi.blidariu said:
try this https://mega.nz/#!Pc9zjDYB!X0wTeiFdY-ca70K9tI-b5fYf40LpcVExIEim0Xk9v14
Click to expand...
Click to collapse
Okay, I'll try to do what you told me later. Then, I'll tell you if that worked. Thanks!!!
k,good luck
Had the same problem. Try this, switch off the phone and unplug from pc, hold volume down then then plug usb back in whilst holding vol down. Should boot to fastboot mode...if not, you can disconnect phone battery and follow above steps again whilst battery is disconnected.
But sadly the p8 lite didn't have removable battery
I know...which is why I took off the back cover and disconnected the battery from the circuit...
HeyAnas98 said:
Hi everyone!
I think I bricked my phone :crying:
Everytime I try to turn it on I see this on the screen (see pic)
And the worst of all is that my windows laptop doesn't recognize the phone when I connect it via usb, the pc tells me that it's an unknown device and there's an error code 43...
Help me pls!
Click to expand...
Click to collapse
download this version of HiSuite 4.04.301,it has a option of system recovery,all you have to do is to have usb debugging enable and conect your phone to pc via usb cable

Phone boots normally but can't enter Fastboot, no recovery.

Hi guys, I'm having a weird problem with my zenfone 5 (a501cg). I have searched a lot but still can't find out a proper solution So I post it here and try to provide as much information as possible so hopefully developers at xda can help me.
My phone is rooted and I'm currently using modded rom called "bazzrom pinaslang" in the forum. Recently I want to use another rom so I decide to use adb sideload again.
However, the problem occurs: using adb sideload only show "error" message". BUT Adb devices show the phone.
Then I decide to use adb reboot fastboot to enter fastboot. But the phone only show a usb icon, and using "fastboot devices" doesn't show the device anymore.
I try other way by enter recovery mode "adb reboot recovery". The phone show resting android with "no command" message. I also try hold power and press down volumn after that but nothing happend. I try anything with that "power" + "volumn" combo but nothing happend (or it just shutdowns the phone).
Also, using "power" + "up volumn" to enter Droid boot doesn't work.
Driver is install. In device manager it shows "Android composite adb interface".
The only good news is my phone still boots normally and I can use it. Please help me get back my fastboot so I can upgrade my phone to Lollipop and other modded ROM.
Thank you so much !!!!
techgeard said:
Hi guys, I'm having a weird problem with my zenfone 5 (a501cg). I have searched a lot but still can't find out a proper solution So I post it here and try to provide as much information as possible so hopefully developers at xda can help me.
My phone is rooted and I'm currently using modded rom called "bazzrom pinaslang" in the forum. Recently I want to use another rom so I decide to use adb sideload again.
However, the problem occurs: using adb sideload only show "error" message". BUT Adb devices show the phone.
Then I decide to use adb reboot fastboot to enter fastboot. But the phone only show a usb icon, and using "fastboot devices" doesn't show the device anymore.
I try other way by enter recovery mode "adb reboot recovery". The phone show resting android with "no command" message. I also try hold power and press down volumn after that but nothing happend. I try anything with that "power" + "volumn" combo but nothing happend (or it just shutdowns the phone).
Also, using "power" + "up volumn" to enter Droid boot doesn't work.
Driver is install. In device manager it shows "Android composite adb interface".
The only good news is my phone still boots normally and I can use it. Please help me get back my fastboot so I can upgrade my phone to Lollipop and other modded ROM.
Thank you so much !!!!
Click to expand...
Click to collapse
Hi,
Have you tried to boot into your system, enable USB debugging and run
Code:
adb reboot-bootloader
?
dgadelha said:
Hi,
Have you tried to boot into your system, enable USB debugging and run
Code:
adb reboot-bootloader
?
Click to expand...
Click to collapse
Hi dgadelha, thanks for your reply.
I have tried your suggestion before but phone only reboots and display usb icon. I also try power volumn combi like i did in my post but still nothing happened.
Usb debugging is enabled.
Techgeard.
techgeard said:
Hi dgadelha, thanks for your reply.
I have tried your suggestion before but phone only reboots and display usb icon. I also try power volumn combi like i did in my post but still nothing happened.
Usb debugging is enabled.
Techgeard.
Click to expand...
Click to collapse
In that case, follow the "Last resort" part of this guide http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=33800
It will reinstall your fastboot when the USB icon appears
dgadelha said:
In that case, follow the "Last resort" part of this guide
It will reinstall your fastboot when the USB icon appears
Click to expand...
Click to collapse
Hi dgadelha,
I have seen your link before my post, but I still wonder because the "last resort" in the link is used for "bricked" phone or the one that doesn't start up or stuck in somewhere. My phone can still boot and use quite normal : ( except one thing that my sd card always unmounted in this Pinaslang modded rom.
TG.
UPDATE I decide to try xFSTK but my computer still recognizes the device as "adb..." . if I turn off developer mode it becomes "portable device" in Window Device Manager.
The xFSTK can't recognize any Cloverfieldplus. (it shows "CLOVERFIELDPLUS...: 0")
TG.
techgeard said:
Hi dgadelha,
I have seen your link before my post, but I still wonder because the "last resort" in the link is used for "bricked" phone or the one that doesn't start up or stuck in somewhere. My phone can still boot and use quite normal : ( except one thing that my sd card always unmounted in this Pinaslang modded rom.
TG.
Click to expand...
Click to collapse
Hi,
Because the last resort will use a hardware function (xFSTK way) to update your dnx, ifwi and fastboot images. This way you can restore your fastboot.
Thanks.
techgeard said:
UPDATE I decide to try xFSTK but my computer still recognizes the device as "adb..." . if I turn off developer mode it becomes "portable device" in Window Device Manager.
The xFSTK can't recognize any Cloverfieldplus. (it shows "CLOVERFIELDPLUS...: 0")
TG.
Click to expand...
Click to collapse
You must instal the drivers it mentioned.
Also it will appear as Cloverview when the USB logo appears
Thanks!
dgadelha said:
Hi,
Because the last resort will use a hardware function (xFSTK way) to update your dnx, ifwi and fastboot images. This way you can restore your fastboot.
Thanks.
You must instal the drivers it mentioned.
Also it will appear as Cloverview when the USB logo appears
Thanks!
Click to expand...
Click to collapse
Hi dgadelha,
After a while I can start the xFSTK and begin download. However, after some attempts it always say error. The same messages show up as below:
Code:
start
sending dner
writeoutpipe dner
writeoutpipe 0
write----> dner
windriver Error: 0x20000015, Timeour expired
LogError
Error Code:1 - Connection Error
Failed to start Dldr state matchine, aborting...
void CloverviewPlusDownloader::do_abort()
Abott
FAIL
.....
techgeard said:
Hi dgadelha,
After a while I can start the xFSTK and begin download. However, after some attempts it always say error. The same messages show up as below:
Click to expand...
Click to collapse
Hi techgeard,
Looks like it's a driver timeout.
Which OS are you using? I see they used Windows 7 or before on the tests.
Also you should try getting xFSTK developers (on SourceForge) to help about this issue.
Thanks.
dgadelha said:
Hi techgeard,
Looks like it's a driver timeout.
Which OS are you using? I see they used Windows 7 or before on the tests.
Also you should try getting xFSTK developers (on SourceForge) to help about this issue.
Thanks.
Click to expand...
Click to collapse
Iam using Win7x64. The same with the guy posting in the link.
TG.

Amazfit - boot into fastboot directly

Hi,
I finally found the real method to boot our Amazfit watch into fastboot. It is difficult to success at any time, but you should be able to boot fastboot directly after some try.
Here is the procedure : (I've made a video : https://www.youtube.com/watch?v=ZlXoeq30vM0 )
When you try, I advice to put the watch in its charging base, the usb Cable connected to the base, but not on the PC.
Here are the steps to go in fastboot mode :
1) press the power button 2 seconds
2) release the button et repress it again without releasing it
3) when the screen of the watch switch off, plug the usb cable.
4) when the screen turn on, count from 1 to 4. At 4 release the power button. You are now in fastboot.
If it fails, try again. It is a little difficult.
Hope this helps.
kiralex
OMG!
edit:
how the hell do i get those files inside with only wastboot mode ... FFS
2nd edit: @Neuer_User, I have the pulled mmcblk0p7 on the storage, is there any possible way of pushing it back into the system via fastboot?
Guys, that is so great! And @kiralex1995 deserves highest thanks for his finding! We need to get a stickied post for this!!
@1immortal: I'll prepare instructions for you. You will need a modified boot image and then boot this. Then you can flash system from there!
Accidentally opened fastboot with a different method.
My device didn't show up under Windows 7, after I installed adb and fastboot drivers.
So with device connected to usb I typed adb kill-server, then adb start-server and adb wait-for-device then I switched it on and off... tadaa fastboot. See picture with command lines.
MyriaBoa said:
Accidentally opened fastboot with a different method.
My device didn't show up under Windows 7, after I installed adb and fastboot drivers.
So with device connected to usb I typed adb kill-server, then adb start-server and adb wait-for-device then I switched it on and off... tadaa fastboot. See picture with command lines.
Click to expand...
Click to collapse
Interesting. See if you can make it reproducable. That would be great!
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
I wrote some unbricking instructions and a flash script to recover bricked watches with @kiralex1995 method of entering fastboot.
Hope, it helps recover the small number of watches known to be bricked through flashing.
https://forum.xda-developers.com/sm...tches/tutorial-unbrick-huami-amazfit-t3547300
Neuer_User said:
Guys, that is so great! And @kiralex1995 deserves highest thanks for his finding! We need to get a stickied post for this!!
@1immortal: I'll prepare instructions for you. You will need a modified boot image and then boot this. Then you can flash system from there!
Click to expand...
Click to collapse
You're welcome
@kiralex1995 , Thanks a Gazillion !!!
it worked and with @Neuer_User help, the watch came back to life !!!
My fastboot method was reproducable on a different machine on Windows 10 . Needed 2 attempts. Seems a question of timing. Right before it happens, the computer makes the notification sound for 'new usb device detected'.
MyriaBoa said:
My fastboot method was reproducable on a different machine on Windows 10 . Needed 2 attempts. Seems a question of timing. Right before it happens, the computer makes the notification sound for 'new usb device detected'.
Click to expand...
Click to collapse
maybe you need to explain a little bit more detailed? is the watch running and completely booted when you connect to usb and type those adb commands or is it switched off? when you turn it on, how fast do you turn it off? i didn't get it yet. please explain a bit more.
MyriaBoa said:
Accidentally opened fastboot with a different method.
My device didn't show up under Windows 7, after I installed adb and fastboot drivers.
So with device connected to usb I typed adb kill-server, then adb start-server and adb wait-for-device then I switched it on and off... tadaa fastboot. See picture with command lines.
Click to expand...
Click to collapse
It is interesting. Does it work with out th.e adb kill-server and adb start-server commands? I do not see, how they could be involved...
The adb wait-for-server might be the key. So, when the watch is started, there is some USB communication on-going. I'd love to do some testing on that. Will do that for sure, when I get the development watch
I' m not near my computer, so I can't do more tests now.
As I wrote in my first post, it wasn't my intention to open fastboot, when it accindentally happened for the first time.
The kill and start commands were given, because my Windows 7 machine pretended not to see the watch in adb (only as usb), and I thought, maybe it's detected, when I turn it on while adb is waiting for device and the usb notification 'kicks in'.
But nothing happened, so I pushed the button, to turn the watch off again.
To my surprise the result was fastboot.
I repeated the same steps today on my Windows 10 computer that always detects the watch in adb and it opened fastboot again.
Could you specify for which build or version you tried this? I (unfortunately) had the update to 1.3.5 and there seems to be no way to enter fastboot. It also is not recognised as an adb device
I have a amazfit pace but he is stucked on a update screen and when I try entring in fast boot mode he doesn´t enter and goes to update again and don´t conclude that. What can I do?
Did anybody managed to get Amazfit 2 (stratos) to fastboot using this method? thx...
EDIT: Yes, I can confirm it works! However it is really kind of tricky. Embrace yourselves!
Many thanks to you guys for finding this out, you are the best!
Thanks.
kiralex1995 said:
Hi,
I finally found the real method to boot our Amazfit watch into fastboot. It is difficult to success at any time, but you should be able to boot fastboot directly after some try.
Here is the procedure : (I've made a video : https://www.youtube.com/watch?v=ZlXoeq30vM0 )
When you try, I advice to put the watch in its charging base, the usb Cable connected to the base, but not on the PC.
Here are the steps to go in fastboot mode :
1) press the power button 2 seconds
2) release the button et repress it again without releasing it
3) when the screen of the watch switch off, plug the usb cable.
4) when the screen turn on, count from 1 to 4. At 4 release the power button. You are now in fastboot.
If it fails, try again. It is a little difficult.
Hope this helps.
kiralex
Click to expand...
Click to collapse
can confirm that this method (sort of) works for stratos as well.
i guess the important part is the 4 seconds after the light goes on. i have done it in like the 8th try.
i guess pulling the usb cable and reattaching it is not really required...
Hello my device is waiting for the logo, it is not opening.
endrancer said:
can confirm that this method (sort of) works for stratos as well.
i guess the important part is the 4 seconds after the light goes on. i have done it in like the 8th try.
i guess pulling the usb cable and reattaching it is not really required...
Click to expand...
Click to collapse
Hi all together,
yes I can confirm that plugging the cable is not neccessary. Went back to stock yesterday. Got into fastboot on first try.
I'm trying that on an actual Stratos watch way longer than 40 minutes - maybe you could help me: I have an "A1619"-model with firmware 2.3.5.0. Same for other Stratos users?
Unlike in the linked video, when I'm at step #4, the "A."-logo appears after about 2 seconds again, so if I release the power button after 4, it's already visible and bootup goes on as normal. Did you notice the same behavior with the "A."-logo before accessing fastboot?
E-lian said:
I'm trying that on an actual Stratos watch way longer than 40 minutes - maybe you could help me: I have an "A1619"-model with firmware 2.3.5.0. Same for other Stratos users?
Unlike in the linked video, when I'm at step #4, the "A."-logo appears after about 2 seconds again, so if I release the power button after 4, it's already visible and bootup goes on as normal. Did you notice the same behavior with the "A."-logo before accessing fastboot?
Click to expand...
Click to collapse
Hello
I've bricked my Pace and cannot enter fastboot.
When I try to enter fastboot I have the same behaviour on my Amazfit Pace. Have You managed some how to enter the fastboot without connection to the PC?

Bricked Chinese version, only ADB sideload is working. Appreciate any help.

Hi,
Messed up badly Furious that ZTE made the phone incompatible with Daydream, decided to root the device. Tried various ROMs, but could never get the modem to work in the UK. Eventually tried to reinstall Chinese stock ROM and, to my surprise, the modem still didn't work. Attempted to restore the modem files from TWRP backup and bricked the phone completely. Can only boot into Chinese recovery where only ADB sideload enables the phone to be seen by Windows as Android ADB Interface. EDL mode cannot be seen and Axon7toolkit cannot see the phone even in ADB sideload mode. Attempts to update software result in this message: Package expects build fingerprint of ZTE/P996A03/ailsa_ii:6.0.1/MMB29M/20161027.021856:user/release-keys or ZTE/P996A03/ailsa_ii:7.1.1/NMF26F/20170224.135053:user/release-keys ; this device has ZTE/P996A03/ailsa_ii:7.1.1/NMF26V/20170912.013327:user/release-keys. Most likely, updates won't work anyway, because when the phone was running, updates resulted in a mismatch. Any feedback would be much appreciated.
tretayuga said:
Hi,
Messed up badly Furious that ZTE made the phone incompatible with Daydream, decided to root the device. Tried various ROMs, but could never get the modem to work in the UK. Eventually tried to reinstall Chinese stock ROM and, to my surprise, the modem still didn't work. Attempted to restore the modem files from TWRP backup and bricked the phone completely. Can only boot into Chinese recovery where only ADB sideload enables the phone to be seen by Windows as Android ADB Interface. EDL mode cannot be seen and Axon7toolkit cannot see the phone even in ADB sideload mode. Attempts to update software result in this message: Package expects build fingerprint of ZTE/P996A03/ailsa_ii:6.0.1/MMB29M/20161027.021856:user/release-keys or ZTE/P996A03/ailsa_ii:7.1.1/NMF26F/20170224.135053:user/release-keys ; this device has ZTE/P996A03/ailsa_ii:7.1.1/NMF26V/20170912.013327:user/release-keys. Most likely, updates won't work anyway, because when the phone was running, updates resulted in a mismatch. Any feedback would be much appreciated.
Click to expand...
Click to collapse
You messed up real bad. I assume you forgot to flash the modem files when you flashed the custom ROMs?
EDL mode cannot be seen? What do you mean by that? Keep the Device Manager open, phone disconnected; then hold both volume buttons, wait 5 seconds, connect the USB cable while you are holding them, and wait 3 seconds more before releasing them. The device manager should refresh.
The phone should appear under Ports (COM & LPT) or under USB devices as QUSB_BULK. If it is under USB devices you have to right click on it, Uninstall -> Delete driver software. After that hold all 3 buttons for a long time (both volume buttons and power) and device manager should refresh itself. It should install the Qualcomm driver then. If the driver is ZTE handset diagnostic interface, you'll have to disassemble the phone
Choose an username... said:
You messed up real bad. I assume you forgot to flash the modem files when you flashed the custom ROMs?
EDL mode cannot be seen? What do you mean by that? Keep the Device Manager open, phone disconnected; then hold both volume buttons, wait 5 seconds, connect the USB cable while you are holding them, and wait 3 seconds more before releasing them. The device manager should refresh.
The phone should appear under Ports (COM & LPT) or under USB devices as QUSB_BULK. If it is under USB devices you have to right click on it, Uninstall -> Delete driver software. After that hold all 3 buttons for a long time (both volume buttons and power) and device manager should refresh itself. It should install the Qualcomm driver then. If the driver is ZTE handset diagnostic interface, you'll have to disassemble the phone
Click to expand...
Click to collapse
Thanks. The phone is listed as ZTE Handset Diagnostic Interface(DFU) (COM10) in Ports. It is listed as Unknown USB Device in USB Controllers and following the procedure you described doesn't install the Qualcomm driver. I take it, then, that an engineer would have to disassemble the phone.
tretayuga said:
Thanks. The phone is listed as ZTE Handset Diagnostic Interface(DFU) (COM10) in Ports. It is listed as Unknown USB Device in USB Controllers and following the procedure you described doesn't install the Qualcomm driver. I take it, then, that an engineer would have to disassemble the phone.
Click to expand...
Click to collapse
Or you. Follow the 4th category brick repair manual. I'm just rewriting it but it'll take time
Where are you getting adb sideload from?
Choose an username... said:
Or you. Follow the 4th category brick repair manual. I'm just rewriting it but it'll take time
Where are you getting adb sideload from?
Click to expand...
Click to collapse
Well, with your help I may snatch victory from the jaws of defeat. I'll ask one of the local engineers to dismantle the phone according to your guide and we'll see what we can do. The adb sideload screen is in this photo.
Thanks again.
tretayuga said:
Well, with your help I may snatch victory from the jaws of defeat. I'll ask one of the local engineers to dismantle the phone according to your guide and we'll see what we can do. The adb sideload screen is in this photo.
Thanks again.
Click to expand...
Click to collapse
You still have one other option though. May save you.
Do you have an SD card? If not, get at least a 4 GB one (or one with 3gb free), download an official A2017 update package, unzip it and put the update.zip in the sd card. (If you get a bunch of folders instead of a file called update.zip just take the original zip and put it in the SD).
after that, put it in the sd card and select the option that says 'sd'.
It may work. Right now it's your best shot at not taking it apart
Choose an username... said:
You still have one other option though. May save you.
Do you have an SD card? If not, get at least a 4 GB one (or one with 3gb free), download an official A2017 update package, unzip it and put the update.zip in the sd card. (If you get a bunch of folders instead of a file called update.zip just take the original zip and put it in the SD).
after that, put it in the sd card and select the option that says 'sd'.
It may work. Right now it's your best shot at not taking it apart
Click to expand...
Click to collapse
That's forbidden. When I've tried to update from the SD card using that option, I get a message saying I don't have permission to update from the SD card. I will, however, try again because you've mentioned some things that are slight variations on what I've done before.
tretayuga said:
That's forbidden. When I've tried to update from the SD card using that option, I get a message saying I don't have permission to update from the SD card. I will, however, try again because you've mentioned some things that are slight variations on what I've done before.
Click to expand...
Click to collapse
Yeah, it's possible. But I have one more idea. Can you try one other thing?
There's a way to get to EDL if you have only DFU mode, which is by getting adb (not adb sideload, just normal adb) and issuing "adb reboot edl". If you can get adb (i think you may have adb from the main recovery screen) then you can get to EDL and flash stuff with MiFlash. Try to issue 'adb reboot edl' when you are on the main screen of the recovery mode.
The other way, which might work on your state, is turning the phone off and holding volume down + power. It might open FTM mode (it's a white rectangle in the middle of the screen with the words FTM written on it, can't miss it). If you get there just issue 'adb reboot edl' and flash with MiFlash
Choose an username... said:
Yeah, it's possible. But I have one more idea. Can you try one other thing?
There's a way to get to EDL if you have only DFU mode, which is by getting adb (not adb sideload, just normal adb) and issuing "adb reboot edl". If you can get adb (i think you may have adb from the main recovery screen) then you can get to EDL and flash stuff with MiFlash. Try to issue 'adb reboot edl' when you are on the main screen of the recovery mode.
The other way, which might work on your state, is turning the phone off and holding volume down + power. It might open FTM mode (it's a white rectangle in the middle of the screen with the words FTM written on it, can't miss it). If you get there just issue 'adb reboot edl' and flash with MiFlash
Click to expand...
Click to collapse
Thanks, but I've already tried it. The phone only communicates with the computer in adb sideload mode, so trying adb reboot edl results in an "error:closed" message. If not in sideload mode, adb cannot even register a device. Occasionally, I've seen a small Linux penguin in the middle of the screen and today it hung on the MiFavor logo for some time. If those are significant, I don't know how to get them back. The ZTE engineers have been very thorough. It's frustratiing because the adb sideload thing might work with the right software package, and I can clear the cache and wipe the system; but then I'm back to square one. Your suggestion about dismantling the phone sounds like the most promising path forward and I will have a go tomorrow.
tretayuga said:
Thanks, but I've already tried it. The phone only communicates with the computer in adb sideload mode, so trying adb reboot edl results in an "error:closed" message. If not in sideload mode, adb cannot even register a device. Occasionally, I've seen a small Linux penguin in the middle of the screen and today it hung on the MiFavor logo for some time. If those are significant, I don't know how to get them back. The ZTE engineers have been very thorough. It's frustratiing because the adb sideload thing might work with the right software package, and I can clear the cache and wipe the system; but then I'm back to square one. Your suggestion about dismantling the phone sounds like the most promising path forward and I will have a go tomorrow.
Click to expand...
Click to collapse
So you get the 5 seconds screen? Have you tried to enter fastboot?
If I'm right, you get the Linux penguin when you hit the power button when you are on the 5 seconds screen (the 'Your device can't be checked for corruption' screen). If it appears, use a volume button to get to the options, select 'Bootloader' and try to enter Bootloader mode. It should have fastboot, being an A2017.
If you get to fastboot you can issue 'fastboot boot twrp.img' and your phone will boot into TWRP. Take Lineage, the Universal Bootloader and the A2017 modem and flash them, then format data, and you'll be good to go.
Choose an username... said:
So you get the 5 seconds screen? Have you tried to enter fastboot?
If I'm right, you get the Linux penguin when you hit the power button when you are on the 5 seconds screen (the 'Your device can't be checked for corruption' screen). If it appears, use a volume button to get to the options, select 'Bootloader' and try to enter Bootloader mode. It should have fastboot, being an A2017.
If you get to fastboot you can issue 'fastboot boot twrp.img' and your phone will boot into TWRP. Take Lineage, the Universal Bootloader and the A2017 modem and flash them, then format data, and you'll be good to go.
Click to expand...
Click to collapse
I do indeed get the 5 seconds screen, but the reason I didn't mention it is that it does nothing from what I can see. The phone "boots" after five seconds, but if I press the volume buttons to enter options, Bootloader is not one of them. The Fastboot option just makes the phone reboot and the Recovery option sends me to the screen in the photo upthread. Like I say, they've been very thorough.
Choose an username... said:
So you get the 5 seconds screen? Have you tried to enter fastboot?
If I'm right, you get the Linux penguin when you hit the power button when you are on the 5 seconds screen (the 'Your device can't be checked for corruption' screen). If it appears, use a volume button to get to the options, select 'Bootloader' and try to enter Bootloader mode. It should have fastboot, being an A2017.
If you get to fastboot you can issue 'fastboot boot twrp.img' and your phone will boot into TWRP. Take Lineage, the Universal Bootloader and the A2017 modem and flash them, then format data, and you'll be good to go.
Click to expand...
Click to collapse
Curioser and curioser. I went through the steps to short circuit the test point on the motherboard and MiFlash successfully flashed the Unbrick ROM which you advised. Obviously, the Qualcomm drivers were recognised e.t.c. The state of the phone now is that it is caught in a boot loop. It shows the ZTE screen and the 5-second screen. Going into recovery on the 5-second screen causes the ZTE logo to appear again, then the battery icon keeps showing, switching off and showing again. The Fastboot mode on the 5-second screen now takes me to the Fastboot screen, but entering recovery causes the same battery loop. Did I make a mistake reassembling the phone perhaps? Should I try to flash a different ROM from the test point?
tretayuga said:
Curioser and curioser. I went through the steps to short circuit the test point on the motherboard and MiFlash successfully flashed the Unbrick ROM which you advised. Obviously, the Qualcomm drivers were recognised e.t.c. The state of the phone now is that it is caught in a boot loop. It shows the ZTE screen and the 5-second screen. Going into recovery on the 5-second screen causes the ZTE logo to appear again, then the battery icon keeps showing, switching off and showing again. The Fastboot mode on the 5-second screen now takes me to the Fastboot screen, but entering recovery causes the same battery loop. Did I make a mistake reassembling the phone perhaps? Should I try to flash a different ROM from the test point?
Click to expand...
Click to collapse
So now you have fastboot? Put the TWRP-3.2.1-0.img on the adb folder, then open CMD, navigate to that folder, write 'fastboot boot TW" and press Tab, the filename should appear, if it does hit Enter
If you get to TWRP don't turn the phone off, and flash the universal bootloader, Lineage, the A2017 modem, and Magisk 15.2
Choose an username... said:
So now you have fastboot? Put the TWRP-3.2.1-0.img on the adb folder, then open CMD, navigate to that folder, write 'fastboot boot TW" and press Tab, the filename should appear, if it does hit Enter
If you get to TWRP don't turn the phone off, and flash the universal bootloader, Lineage, the A2017 modem, and Magisk 15.2
Click to expand...
Click to collapse
Sorry, I didn't make that clear. The 5-second screen directs me to Fastboot, but there are only four options there: Start (doesn't work, obviously), Restart Bootloader (brings you back to the same place), Shut down and Recovery (goes to battery icon). Don't know what went wrong--maybe a connection got damaged when the phone was dismantled--but I discover I can't repeat the short circuiting thing and, even though the phone is seen on the system as Qualcomm 90.., MiFlash cannot flash anything different. I despair. I'll send the phone for recycling. Making the Axon 7 incompatible with Daydream was the last straw. I very much appreciate your help just the same.
tretayuga said:
Sorry, I didn't make that clear. The 5-second screen directs me to Fastboot, but there are only four options there: Start (doesn't work, obviously), Restart Bootloader (brings you back to the same place), Shut down and Recovery (goes to battery icon). Don't know what went wrong--maybe a connection got damaged when the phone was dismantled--but I discover I can't repeat the short circuiting thing and, even though the phone is seen on the system as Qualcomm 90.., MiFlash cannot flash anything different. I despair. I'll send the phone for recycling. Making the Axon 7 incompatible with Daydream was the last straw. I very much appreciate your help just the same.
Click to expand...
Click to collapse
No, when you are on the screen with the 4 options you have Fastboot. That is the bootloader mode. Get there and issue 'fastboot devices' and you'll see that you got fastboot from there.
Don't repeat the 4th category manual, just turn the phone off and hold volume up and down, then connect the USB. If it appears as Qualcomm HS-USB QDLoader 9008 you're in EDL.
What's the name of the package that you flashed?
Choose an username... said:
No, when you are on the screen with the 4 options you have Fastboot. That is the bootloader mode. Get there and issue 'fastboot devices' and you'll see that you got fastboot from there.
Don't repeat the 4th category manual, just turn the phone off and hold volume up and down, then connect the USB. If it appears as Qualcomm HS-USB QDLoader 9008 you're in EDL.
What's the name of the package that you flashed?
Click to expand...
Click to collapse
You star! I've followed your advice and now it is exactly the phone I was looking for. (I had made a mistake and forgotten to reconnect something in the internals, but the ROM worked just fine once that was sorted and I've flashed all the things you recommended.) Your name will be sung down the ages in my household, Choose an username. Many thanks

Stuck at FTM (Factory Test Mode) - Axon 7

Hello, I turned on my phone this morning as usual however was instead presented into a Factory Test Mode, has happened for the first time. I then long pressed the power button but still no luck, after trying every combination possible I gave up. I charged the phone last night at 100% and turned it off as usual. (On stock rom, Oreo 8.0 not rooted or anything. - A2017GV1.3.0B03 ) Also, don't really want to disassemble or reset my phone. Any help would be much appreiated. Thanks!
owerevoke said:
Hello, I turned on my phone this morning as usual however was instead presented into a Factory Test Mode, has happened for the first time. I then long pressed the power button but still no luck, after trying every combination possible I gave up. I charged the phone last night at 100% and turned it off as usual. (On stock rom, Oreo 8.0 not rooted or anything. - A2017GV1.3.0B03 ) Also, don't really want to disassemble or reset my phone. Any help would be much appreiated. Thanks!
Click to expand...
Click to collapse
what is "long pressed"? You have to hold it for about a minute or so, did you?
If it doesn't work, FTM mode has ADB, so you should be able to hook it up to a PC and issue "adb reboot" from the terminal. If you end up in FTM again then your phone is just borked or something, you can attempt to fix it by using "adb reboot recovery" instead and reflash stuff
Choose an username... said:
what is "long pressed"? You have to hold it for about a minute or so, did you?
If it doesn't work, FTM mode has ADB, so you should be able to hook it up to a PC and issue "adb reboot" from the terminal. If you end up in FTM again then your phone is just borked or something, you can attempt to fix it by using "adb reboot recovery" instead and reflash stuff
Click to expand...
Click to collapse
Thanks, adb reboot solved it! Can't thank you enough!
Same case to me on OreoB03. Power button long pressed didn't respond. I used "minimal_adb_fastboot_1.4.1_portable" and command reboot.
svsavic said:
Same case to me on OreoB03. Power button long pressed didn't respond. I used "minimal_adb_fastboot_1.4.1_portable" and command reboot.
Click to expand...
Click to collapse
Same problem here.
But i do not know how to use ADB tool.
I dowloaded minimal adb fastboot tool and i have now 3 executable (adb, fastboot, MAF32) in a directory but I do not know how to use them in order to reboot my Axon 7.
I would appreciate a step by step guide, made for a very beginner.
Note also that I may not have already the device drivers on my computer.
Find cmd.exe in syistem32, run as administrator, drag adb.exe in cmd window. Write command adb reboot.
Impossible for me.
I am not even able to have the phone recognized since the drivers are not correctly installed and Zadig tools wont help.
I'm really stuck.
Would any Belgian Guys be able to help me having a computer with adb WinUSB drivers correctly installed so that we can reboot my phone with his PC with any adb tool ? Please PM me is so.
Phone is recognized as adb device (w/o driver). Just try this and write command adb reboot or reboot (i don't remember).
It is said that no devices is found.
?
Also had the same FTM problem and can confirm that power button did not work in stock Oreo.
If can't get adb reboot work, one simple way is to discharge the phone - USB type C connection is fully working in FTM mode (u can simply check that). Connect one or few (use simple usb spliter) USB devices (the best way is to connect devices, for example power bank, some bluetooth speaker, which actually suck energy etc.) to your phone in order to charge them and it will fully discharge the phone in a few hours. Then on phone turned off connect power charger, wait about 15-20 minutes to charge and turn on the phone as usual (using only power button for a few seconds).
Hello, i actually thought about this option of waiting for the battery to be discharged but did not dare to take the risk. I finally found someone that will "adb reboot" my phone tomorrow, fingers crossed.
Hi,
OK, let's hope that "adb reboot" option will succeed.
However, personally I see no risks in discharging the battery - when the phone discharges it just safely automatically turns off - no data loss, no need to reflash the ROM etc. I went through this route myself.
I think it could be another bigger risk to keep the screen on (not moving screen) for a longer time - possible burn in of screen etc. But not sure about this risk and don't want to frighten, maybe others have more knowledge on possible screen burn in issues. In my case after discharging the battery no burn in or other screen problems.
I ordered a OTG cable that should arrive tomorrow to discharge the phone if adb reboot does not work. Thank you for ur feedback.
Have you tried this tool to get to EDL and then you can use Miflash to flash back to stock https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229
billjim24 said:
Have you tried this tool to get to EDL and then you can use Miflash to flash back to stock https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229
Click to expand...
Click to collapse
that's not remotely useful to the situation
please read up before posting lmao
Mine Axon 7 did just that, couldn't turn it off in any way, also on b03 Oreo rom. So I let it discharge completely, and just did a normal power on, and it worked again.
I think that the Oreo Rom is in an awfully bad beta Rom rushed out from a sinking mobile company, that don't give a s... about their customers.
Will never buy ZTE again.
A friend could reboot mine with adb reboot. Problem solved.
I guess adb drivers did not worked well on m'y computer.
Next thing to do : downgrade to Nougat in order to get Daydream. What a shame.
Chinesur said:
A friend could reboot mine with adb reboot. Problem solved.
I guess adb drivers did not worked well on m'y computer.
Next thing to do : downgrade to Nougat in order to get Daydream. What a shame.
Click to expand...
Click to collapse
G B03 has daydream, hasn't it?
No, it doesn't have
Boot in FTM,open axon7toolkit,connect phone to laptop and follow instructions in axon7toolkit.It will reboot in edl and you can flash a firmware

Categories

Resources