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
Related
I was trying to install a custom recovery (twrp) by several different methods, with absolutely no luck (but that's another secondary issue at this point) and i screwed something up. Not exactly sure but i think the last thing I did was:
using "Rashr - Flash Tool" i think i went to "flash kernel from storage" then flashed boot.img.
now the phone goes immediately, directly into fastboot even without being connected to computer.
so i tried getting into the stock recovery by holding "volume down" and "power" until lg logo, releasing the reholding until factory reset screen. after choosing yes 2 times i get a
"boot certicification verify" or something message for about a second then it goes to this screen (sorry but apparently i haven't had enough posts on the forums to include clickable links.)
h**ps://drive.google.com/file/d/0BwQdFsCQ9KZVaGM1eWdJb25WVVU/view?usp=sharing
slplsnphx said:
I was trying to install a custom recovery (twrp) by several different methods, with absolutely no luck (but that's another secondary issue at this point) and i screwed something up. Not exactly sure but i think the last thing I did was:
using "Rashr - Flash Tool" i think i went to "flash kernel from storage" then flashed boot.img.
now the phone goes immediately, directly into fastboot even without being connected to computer.
so i tried getting into the stock recovery by holding "volume down" and "power" until lg logo, releasing the reholding until factory reset screen. after choosing yes 2 times i get a
"boot certicification verify" or something message for about a second then it goes to this screen (sorry but apparently i haven't had enough posts on the forums to include clickable links.)
h**ps://drive.google.com/file/d/0BwQdFsCQ9KZVaGM1eWdJb25WVVU/view?usp=sharing
Click to expand...
Click to collapse
if u still have acces to fastboot use this or u see many disk at windows use srktool http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
amin44 said:
if u still have acces to fastboot use this or u see many disk at windows use srktool http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
Click to expand...
Click to collapse
ok, i do have access to fastboot (actually, as soon as i power it on, it immediately is in foastboot mode, even without being connected to computer). i tried using srktool's repair tools via fastboot. it seems like it's working (ie phone shows that it receives command) but that's it. does it take a loooooong time or something?
btw, i can also get into download mode by holding "vol up" while plugging into computer. so, i tried using srktool utilites via download mode and nothing.
also, i just noticed that while connected to computer in download mode, in device manager it shows G2 under "portable devices" with an exclamation point on it.
slplsnphx said:
ok, i do have access to fastboot (actually, as soon as i power it on, it immediately is in foastboot mode, even without being connected to computer). i tried using srktool's repair tools via fastboot. it seems like it's working (ie phone shows that it receives command) but that's it. does it take a loooooong time or something?
btw, i can also get into download mode by holding "vol up" while plugging into computer. so, i tried using srktool utilites via download mode and nothing.
also, i just noticed that while connected to computer in download mode, in device manager it shows G2 under "portable devices" with an exclamation point on it.
Click to expand...
Click to collapse
are u sure u do not have franken phone open battery cover and see model written inside motherbord
amin44 said:
are u sure u do not have franken phone open battery cover and see model written inside motherbord
Click to expand...
Click to collapse
I haven't taken the back off (yet) but all indications are that it's an AT&T (D800).
What part of my description makes you think that it might be a franken phone?
Did you try connecting the phone in download mode or fastboot to the LG Mobile Support Tool and performing an upgrade recovery?
audit13 said:
Did you try connecting the phone in download mode or fastboot to the LG Mobile Support Tool and performing an upgrade recovery?
Click to expand...
Click to collapse
not sure what you mean by "lg mobile support tool". i googled it and found and installed "lg pc suite". is that the same thing?
nevermind that last question. i found and installed and tried the upgrade recovery tool but for some reason the phone wont go into download mode anymore. when i power it up whith ""vol +" help down, it shows download mode for a second, but then goes right into fastboot mode.
Is it recognized by the program in fastboot mode?
Here's the program I was referring to: http://www.lg.com/ca_en/support-mobile/lg-LGD803
Even though the program says it is for the 803, I used it to recover my international d802.
slplsnphx said:
not sure what you mean by "lg mobile support tool". i googled it and found and installed "lg pc suite". is that the same thing?
nevermind that last question. i found and installed and tried the upgrade recovery tool but for some reason the phone wont go into download mode anymore. when i power it up whith ""vol +" help down, it shows download mode for a second, but then goes right into fastboot mode.
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
amin44 said:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse
Thanks for the reply! But when I have phone connected to USB in fastboot, it shows up in device manager as "android device > USB modem phone port". Is that method the right fix for my situation?
ok, so likei said my phone is indeed in fastboot mode, connected to computer via usb (shows up in device manager as "android device > USB modem phone port". using srktool, i can send commands to the phone (command shows up on phone but thats it.....doesnt matter what command, it just sticks there until i unplug the phone then srktool shows the operation competed and phone shows
https://drive.google.com/file/d/0BwQdFsCQ9KZVSVg3OTZLcXV0N0E/view?usp=sharing
but none of operations actually complete on the phone.
slplsnphx said:
Thanks for the reply! But when I have phone connected to USB in fastboot, it shows up in device manager as "android device > USB modem phone port". Is that method the right fix for my situation?
Click to expand...
Click to collapse
that method fix for all situation
amin44 said:
that method fix for all situation
Click to expand...
Click to collapse
ok i shorted the capacitors, and eventually have gotten to where i can get into twrp. i assume that is serious progress, but what do i need to do next?
slplsnphx said:
ok i shorted the capacitors, and eventually have gotten to where i can get into twrp. i assume that is serious progress, but what do i need to do next?
Click to expand...
Click to collapse
flash stock ROM via download mode or flash custom ROM via twrp.
the first choice (stock ROM) is better
thanks for the responses!!
before i saw your reply, i flashed the stock .tot firmware and now i have my phone back.
but, before all this started, it was lollipop(5.0.2) and now it's Jellybean(4.2.2). i bought phone on ebay, so im assuming that it got lollipop via an ota update. so now i'm looking into flashing it back to lollipop. what's the easiest method to install stock lollipop?
Hey guys, I have a A2017 axon 7, and I tried to upgrade from Marshmalow to nougat by flashing the B04 update from TWRP. I have now the factory recovery mode, and when I try to go in fastboot, it tries to launch the bootloader( which just tells me that my device software cannot be checked for corruption and that I need to lock my bootloader). When I try to boot normally it stays on the same "bootloader screen" and tells me to press the start button which makes the phone display the linux logo.... I'm a bit lost, I'm on ArchLinux could you pls help me ?
Thx !
Dr_Raider said:
Hey guys, I have a A2017 axon 7, and I tried to upgrade from Marshmalow to nougat by flashing the B04 update from TWRP. I have now the factory recovery mode, and when I try to go in fastboot, it tries to launch the bootloader( which just tells me that my device software cannot be checked for corruption and that I need to lock my bootloader). When I try to boot normally it stays on the same "bootloader screen" and tells me to press the start button which makes the phone display the linux logo.... I'm a bit lost, I'm on ArchLinux could you pls help me ?
Thx !
Click to expand...
Click to collapse
Well, you should use MiFlash and install the stock system through EDL. The problem is that MiFlash is for Windows x64. if you could get a win10 x64 pc, you could fix it in a minute.
Or get to the recovery if you can, and flash Nougat again but via an SD card. But maybe you won't be able to get to the recovery mode
Choose an username... said:
Well, you should use MiFlash and install the stock system through EDL. The problem is that MiFlash is for Windows x64. if you could get a win10 x64 pc, you could fix it in a minute.
Or get to the recovery if you can, and flash Nougat again but via an SD card. But maybe you won't be able to get to the recovery mode
Click to expand...
Click to collapse
I need help! I wanted to relock the bootloader but then I coulnd't enter the recovery or fastboot anymore. When I press any combination it always turn on for 1 sec and then the screen turns off again but it still GOT recognized as QUSB Bulk. After I installed MiFlash the device is recognized as QDLOADER 9008. I didn't flash anything and I don't kno how to unbrick my device now .
I use the A2017G model btw.
Kantastisch said:
I need help! I wanted to relock the bootloader but then I coulnd't enter the recovery or fastboot anymore. When I press any combination it always turn on for 1 sec and then the screen turns off again but it still GOT recognized as QUSB Bulk. After I installed MiFlash the device is recognized as QDLOADER 9008. I didn't flash anything and I don't kno how to unbrick my device now .
I use the A2017G model btw.
Click to expand...
Click to collapse
How did you relock the bootloader? If you used a guide, you should have found a warning, and if you used axon7toolkit a message should've popped up.
You messed up. Real bad. You are probably on DFU mode, and the only ways to get out of there are:
-discharge the battery completely and try to enter FTM mode (i think you have to do that while it is connected to a PC), I think it was with volume down + power. this method works for very few people. If you enter ftm mode, issue 'adb reboot edl' and use MiFlash right away with a FULL_EDL package
-use the 4th category brick repair manual (disassemble the phone, short some pins)
Choose an username... said:
How did you relock the bootloader? If you used a guide, you should have found a warning, and if you used axon7toolkit a message should've popped up.
You messed up. Real bad. You are probably on DFU mode, and the only ways to get out of there are:
-discharge the battery completely and try to enter FTM mode (i think you have to do that while it is connected to a PC), I think it was with volume down + power. this method works for very few people. If you enter ftm mode, issue 'adb reboot edl' and use MiFlash right away with a FULL_EDL package
-use the 4th category brick repair manual (disassemble the phone, short some pins)
Click to expand...
Click to collapse
I think DFU Mode is when I get recognized as ZTE Handset diagnostic .... according to this guide : https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898) It's a2017 but still.
"Axon 7 restore manual from bricked conditions when only ZTE Handset Diagnostic Interface(DFU) (COM...) mode is detected"
But I get recognized as QDloader 9008 and miflash also recognizes it as com10 or something.
Kantastisch said:
I think DFU Mode is when I get recognized as ZTE Handset diagnostic .... according to this guide : https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898) It's a2017 but still.
"Axon 7 restore manual from bricked conditions when only ZTE Handset Diagnostic Interface(DFU) (COM...) mode is detected"
But I get recognized as QDloader 9008 and miflash also recognizes it as com10 or something.
Click to expand...
Click to collapse
it's not necessarily like that. DFU mode is just a mode in which the phone can be. Sometimes Windows just installs the QDLoader driver even though it's not EDL. and if you tried miflash and it didn't work, then it's most probably that.
There's a way to check. If you go to Properties, there should be a number that identifies the mode. if you google it and 'dfu interface' appears, then you are dfu-bricked
But if you locked the bootloader without being fully stock then it's most probably dfu bricked anyways
Again, how did you lock the bootloader?
I don't actually know if I really locked the bottloader.
So, I had unlocked bootloader and twrp. I just bootet into the bootloader, typed "fastboot oem lock" in adb and it said OK on the PC.
But on the phone it never asked me if I want to lock it or anything. And I never said MiFlash isn't working. It recognizes my phone but i judt didn't TRY to flash anything because I didn't want to make the situation even worse perhaps
Choose an username... said:
it's not necessarily like that. DFU mode is just a mode in which the phone can be. Sometimes Windows just installs the QDLoader driver even though it's not EDL. and if you tried miflash and it didn't work, then it's most probably that.
There's a way to check. If you go to Properties, there should be a number that identifies the mode. if you google it and 'dfu interface' appears, then you are dfu-bricked
But if you locked the bootloader without being fully stock then it's most probably dfu bricked anyways
Again, how did you lock the bootloader?
Click to expand...
Click to collapse
I don't actually know if I really locked the bottloader.
So, I had unlocked bootloader and twrp. I just bootet into the bootloader, typed "fastboot oem lock" in adb and it said OK on the PC.
But on the phone it never asked me if I want to lock it or anything. And I never said MiFlash isn't working. It recognizes my phone but i judt didn't TRY to flash anything because I didn't want to make the situation even worse perhaps
Kantastisch said:
I don't actually know if I really locked the bottloader.
So, I had unlocked bootloader and twrp. I just bootet into the bootloader, typed "fastboot oem lock" in adb and it said OK on the PC.
But on the phone it never asked me if I want to lock it or anything. And I never said MiFlash isn't working. It recognizes my phone but i judt didn't TRY to flash anything because I didn't want to make the situation even worse perhaps
Click to expand...
Click to collapse
Lol it doesn't ask you if you want to lock it, that's the point with bootloader mode. there's no system, no UI, and you make stuff via commands.
This is why you shouldn't even attempt this kind of stuff without knowing how it works. At least if you had used axon7toolkit, it would've told you not to.
Find a FULL_EDL package for your model. If you have an A2017, simply use this one:
https://androidfilehost.com/?fid=817550096634790942
or
https://mega.nz/#!JqwEUDCa!lW3NDaBNbmMxhtw6XajspHBJaaEmLC8uNvMZS5ww0EQ
(they are the same file)
Unzip it, leave the folder somewhere handy, put the phone in what you believe is EDL, open MiFlash and select the folder, and flash
Choose an username... said:
Lol it doesn't ask you if you want to lock it, that's the point with bootloader mode. there's no system, no UI, and you make stuff via commands.
This is why you shouldn't even attempt this kind of stuff without knowing how it works. At least if you had used axon7toolkit, it would've told you not to.
Find a FULL_EDL package for your model. If you have an A2017, simply use this one:
https://androidfilehost.com/?fid=817550096634790942
or
https://mega.nz/#!JqwEUDCa!lW3NDaBNbmMxhtw6XajspHBJaaEmLC8uNvMZS5ww0EQ
(they are the same file)
Unzip it, leave the folder somewhere handy, put the phone in what you believe is EDL, open MiFlash and select the folder, and flash
Click to expand...
Click to collapse
Yeah, I screwed up, I know. But what is the point of flashing a full edl package for the phone if I have to put the phone in "what I believe id edl mode"?
And what shall I do if I succeed at something? Besided that, I can't find any EDL package for the A2017G?
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
This guide tells me NOT TO flash anything on a2017g...
Kantastisch said:
Yeah, I screwed up, I know. But what is the point of flashing a full edl package for the phone if I have to put the phone in "what I believe id edl mode"?
And what shall I do if I succeed at something? Besided that, I can't find any EDL package for the A2017G?
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
This guide tells me NOT TO flash anything on a2017g...
Click to expand...
Click to collapse
Okay let me tell you this real straight. I have done this. I have the G packages, I just thought you were the op for some reason. Look at the back of the phone and confirm whether you have an A2017G or an A2017 just in case, or you might mess up even more, as hard as that can be.
at any rate, your fears are all dumbfounded, because in the situation that you are in, you have 3 options:
a) disregard all the help that i'm trying to give you, even though I have already done the process; and keep your brick on a shelf.
b) search on google or xda yourself, then do the process, without bothering here with your lack of trust
c) follow my advice and do the damn process
Whichever option you choose, I'm gonna leave the package here:
https://mega.nz/#!UrxCRCrQ!a4sXVFu5oqct2sWStfN_luGpN5HEGXxE4FcrRteagQ4
or
https://androidfilehost.com/?fid=961840155545591863
Again, I HAVE FOLLOWED THE 4TH CATEGORY BRICK REPAIR GUIDE AND FIXED MY G. I flashed stuff through EDL at least 10 times. And there wouldn't be a bunch of EDL packages for the G if they had a 100% chance of bricking your phone
So. If you decide to do this, turn your phone off. connect the USB cable to the PC but not the phone. Hold both volume buttons (but not the power button) and insert the USB cable at the same time. Then fire up MiFlash and try to flash the file (you have to unzip the folder, then select the folder on miflash, then flash. Here 2 things may happen:
a) it flashes and you can just go bother someone else
b) it doesn't and you have to follow the 4th category brick repair guide
Simple as that. if it fails, you might want to check if the 'Qualcomm HS-USB QDLoader 9008' is actually EDL mode or DFU mode, so you can do that by going to properties and checking some device identifier number on google (haven't done that, i just read that it can be done somewhere here).
Choose an username... said:
Okay let me tell you this real straight. I have done this. I have the G packages, I just thought you were the op for some reason. Look at the back of the phone and confirm whether you have an A2017G or an A2017 just in case, or you might mess up even more, as hard as that can be.
at any rate, your fears are all dumbfounded, because in the situation that you are in, you have 3 options:
a) disregard all the help that i'm trying to give you, even though I have already done the process; and keep your brick on a shelf.
b) search on google or xda yourself, then do the process, without bothering here with your lack of trust
c) follow my advice and do the damn process
Whichever option you choose, I'm gonna leave the package here:
https://mega.nz/#!UrxCRCrQ!a4sXVFu5oqct2sWStfN_luGpN5HEGXxE4FcrRteagQ4
or
https://androidfilehost.com/?fid=961840155545591863
Again, I HAVE FOLLOWED THE 4TH CATEGORY BRICK REPAIR GUIDE AND FIXED MY G. I flashed stuff through EDL at least 10 times. And there wouldn't be a bunch of EDL packages for the G if they had a 100% chance of bricking your phone
So. If you decide to do this, turn your phone off. connect the USB cable to the PC but not the phone. Hold both volume buttons (but not the power button) and insert the USB cable at the same time. Then fire up MiFlash and try to flash the file (you have to unzip the folder, then select the folder on miflash, then flash. Here 2 things may happen:
a) it flashes and you can just go bother someone else
b) it doesn't and you have to follow the 4th category brick repair guide
Simple as that. if it fails, you might want to check if the 'Qualcomm HS-USB QDLoader 9008' is actually EDL mode or DFU mode, so you can do that by going to properties and checking some device identifier number on google (haven't done that, i just read that it can be done somewhere here).
Click to expand...
Click to collapse
THANKS SO MUCH , you saved my ass, it flashed without a problem and sorry for bothering you. Bootloader is locked now and it works fine. Thanks again!
So i wanted to create a key mapping for android over my android game using my xbox one controller but all the apps that allow it require rooting. So i quickly came here to see if it was rootable and surely my model was listed. LG k20 Plus MP260, So i go and download adb tap my build number, do the usb debugging, allow oem unlocking, downloaded the Lg drivers, moved the recovery.img to the adb file folder directory, moved the super user Zip file and the no-verity-opt-encrypt-5.1.Zip to the internal storage of the phone. Then run Shift+ Right click adb reboot bootloader using Windows powershell command line and i'm in fastboot mode (I can also just power the phone off and hold the volume down button and plug usb into phone to get into it). So i use fastboot devices to make sure the computer recognized my device and it does. Note: (the bootloader is already unlocked) Then i use fastboot flash recovery recovery.img and it flashes. what happens next is well. I use fastboot reboot and well i get "Your device software cannot be checked for corruption lock the bootloader" and below that it say "PRESS THE POWER KEY TO CONTINUE" i press the power key and it boots up normally. In the video's i've watched they say it will boot into the system twrp and my phone is not doing this. I'm willing to let someone team view me and skype me so we can work this out together and i'm even willing to pay 20$ if we can get this done. Please message me asap
I have the exact same problem. Did you ever figure it out?
Bumping an oldish thread, because this still exists. Custom recovery isn't very useful when you can't get to it without reflashing it every time.
dbsc said:
Bumping an oldish thread, because this still exists. Custom recovery isn't very useful when you can't get to it without reflashing it every time.
Click to expand...
Click to collapse
Did you find a solution? I've been fighting my LG K20 plus metroPCS for over 2 weeks. It won't go into download mode or recovery. In recovery it skips over the reset page. I think the phone is possessed lol.
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
Not sure how to title this forum post, but this is the best I got. Forgive my ignorance and lack of knowledge on these topics.
I was trying to root my Axon 7 mini. After some searching to find out how to unlock the bootloader (like needing JDK, older Android SDK version to run android.bat, etc.), I finally got it to work. Ran Recovery to "apply update from SD Card" (can not remember the file right now) and was then ready to load TWRP Recovery. When I rebooted to the recovery TWRP image, it told me something failed and the phone had to be factory reset. I took my SD card out in fear of my data being deleted and "accidentally" clicked the power button. It then reloaded with a password prompt where I typed some random password (1234 because I never set a pin password nor knew what to do here), clicked submit, and then gave me some error; now my phone doesn't work.
The Problem:
- I can enter bootloader, sometimes, but can only run fastboot commands; adb device does not detect phone so can't run adb commands (always says the server is old or something and reloads daemon successfully but never finds my device regardless). Also, I don't think I can get it to run in EDL mode; MiFlash gives out errors too when trying to flash recovery images.
- Recovery mode doesn't appear or work; not sure if the MiFavor command prompts on the phone is recovery or not, but it's safe to say this no longer appears. This is also where I believe the phone bootloops. I can get the fastboot commands to flash a TWRP recovery, but it never actually enters the TWRP dashboard.
- Can not turn off the phone... I think. None of the command options that appear on-phone shut it off; however, when the screen does stay black, I'm not sure if it's in EDL mode or plainly off.
- Device Manager shows the phone as different stuff (namely Kedacom USB Device and Portable Devices/MTB USB Device). Sometimes Qualcomm appears, but it depends. More often than not, when my device does appear, there's either an error code (like Code 10, Code 43) and/or the device is grayed out.
Conclusion:
I just want to get my phone to work normally again, if possible. Currently, I locked the oem to see if fastboot commands could still work and now I'm stuck at the ZTE logo, so can't try to unlock it right now. What are the proper tools, drivers, programs, etc I need to get this phone back to normal? I've scoured the web and these forums for 2 days now with no luck and lots of either missing info or obscure info.
I bought this at Best Buy, so I'm assuming it's US Axon7 Mini version in terms of drivers (not sure if the box specifies any info that could be useful here).
Un-brick Axon 7 Mini
Dear all,
I experienced the same issue with my phone after I tried to flash it with custom ROMs and recovery.
I thought I lost it as I was not able to enter adb mode (not recognized on the PC) or even not able to enter EDL mode with the button combination so not able to do anything with it.
Only watch it boot and display the ZTE logo.
After some research, here is what I had to do to get it recovered.
First thing you need to get is an EDL cable.
I let you search on your favorite site. Mine was a Generic eDL Deep Flash Qualcomm 9008 Cable 2 in 1 for Z3 X/Octopus.
Until you receive it, make sure you have the latest Qualcomm drivers installed on your PC.
You can find it easily.
Then, connect your phone and your PC with the EDL cable.
Press the button on your EDL cable (there should be one) for a few seconds and keep it pressed.
Then, press the power button and keep it pressed for at least 20 seconds.
At this stage, you should have both buttons pressed and after some time, you should feel the phone rebooting.
After 20 seconds, release the power button.
Then, after 10 other seconds, release the EDL cable button.
At this stage, your phone screen should stay black and your phone should appear in the device manager as Qualcomm USBHUB (or somehting similar)
You are in EDL mode and should be able to perform a recovery flashing using tuliptool.
Then I followed the steps I found here:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
If you are still stuck, pm me.
Be patient, all will be fine,
mariegalante55 said:
Dear all,
I experienced the same issue with my phone after I tried to flash it with custom ROMs and recovery.
I thought I lost it as I was not able to enter adb mode (not recognized on the PC) or even not able to enter EDL mode with the button combination so not able to do anything with it.
Only watch it boot and display the ZTE logo.
After some research, here is what I had to do to get it recovered.
First thing you need to get is an EDL cable.
I let you search on your favorite site. Mine was a Generic eDL Deep Flash Qualcomm 9008 Cable 2 in 1 for Z3 X/Octopus.
Until you receive it, make sure you have the latest Qualcomm drivers installed on your PC.
You can find it easily.
Then, connect your phone and your PC with the EDL cable.
Press the button on your EDL cable (there should be one) for a few seconds and keep it pressed.
Then, press the power button and keep it pressed for at least 20 seconds.
At this stage, you should have both buttons pressed and after some time, you should feel the phone rebooting.
After 20 seconds, release the power button.
Then, after 10 other seconds, release the EDL cable button.
At this stage, your phone screen should stay black and your phone should appear in the device manager as Qualcomm USBHUB (or somehting similar)
You are in EDL mode and should be able to perform a recovery flashing using tuliptool.
Then I followed the steps I found here:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
If you are still stuck, pm me.
Be patient, all will be fine,
Click to expand...
Click to collapse
I had a feeling an EDL cable was my only option left given everything I've looked up and the multiple methods I've tried. Wanted to avoid spending money on one but doesn't look like I have a choice given the circumstances - oh well. Regardless, thank you for the response and advice. Have to wait a while, though, to get the cable and test to see if this works.
If anyone else ever ends up in the same royally screwed situation as me, getting an EDL cable - or DIY one if you wanna be cheap and are confident enough to do so - is probably your saving grace.
Kuma21 said:
I had a feeling an EDL cable was my only option left given everything I've looked up and the multiple methods I've tried. Wanted to avoid spending money on one but doesn't look like I have a choice given the circumstances - oh well. Regardless, thank you for the response and advice. Have to wait a while, though, to get the cable and test to see if this works.
If anyone else ever ends up in the same royally screwed situation as me, getting an EDL cable - or DIY one if you wanna be cheap and are confident enough to do so - is probably your saving grace.
Click to expand...
Click to collapse
K, I can get tuliptool to work and run command, but i keep getting a "Failed: Unkown Error" response everytime i run a command. Can't unlock my bootloader, nor write a recovery disk due to this error. does anyone have any idea why this happens?