[Brick?] How to solve problem with A2017G (every mode available) - ZTE Axon 7 Questions & Answers

Good evening, guys,
I'm at a loss as to what is happening with my A2017G.
I had TWRP 3.1.0-2, B04 and SuperSU, but the SU wasn't working properly (the message that root privileges were given to my root apps kept popping up but the actual apps didn't work as intended, so to flash the alternative file that I found somewhere in the forums here.
After that, I could not pass the ZTE logo in order to boot the system.
Went back to TWRP, flashed bootstack and stock system by tron again, SuperSU - and the same result.
Without knowing what else to do, I grabbed the full stock B04 file and tried to flash it.
Now, I have a phone whith stock recovery working, without fastboot, with FTM mode, with EDL mode all working, but I can't seem to use one of those in order to restore my phone that, when I try to boot to system, keeps stuck at the screen with the message that the bootloader has been unlocked.
I tried flashing twrp and the update.zip through Mi Flash, but I get a syntax error (my device shows as COM3);
In recovery, when I choose to apply upgrade through SD, a message appears "You can't upgrade from SD card, sorry";
FTM mode works and my phone loads as an adb device (seeing in Axon 7 tool), but if I try to sideload the update.zip through the Windows 10 cmd it crashes with a message saying "bad alloc", or something.
So, I'm at a loss here. I have every modes working, and I still cannot flash anything to my device?
Or am I doing it wrong?
Thank you.

I'm almost sure you can't just flash an official update zip with MiFlash, so do this:
Download this zip, comes from djkuz. It is the full A2017G system with fbop and fastboot
https://mega.nz/#!ZhwR1BAD!PuIWa5Viv...iR-j1U8wZZidTw
After that unpack it and use MiFlash to get it flashed nicely on your device. When you finish, you'll have B10 I think. I experienced random reboots without any thermal problems (even rebooted while it was in my pocket) so you might be better off going to RR but be real careful if/when going back to stock if you decide to do this (i had a DFU brick )

Choose an username... said:
I'm almost sure you can't just flash an official update zip with MiFlash, so do this:
Download this zip, comes from djkuz. It is the full A2017G system with fbop and fastboot
https://mega.nz/#!ZhwR1BAD!PuIWa5Viv...iR-j1U8wZZidTw
After that unpack it and use MiFlash to get it flashed nicely on your device. When you finish, you'll have B10 I think. I experienced random reboots without any thermal problems (even rebooted while it was in my pocket) so you might be better off going to RR but be real careful if/when going back to stock if you decide to do this (i had a DFU brick )
Click to expand...
Click to collapse
Flashing the extracted B10 package solved it, thanks!
Until now, everything's smooth, running B04.
Thank you.

Related

Bricked/bootloop B15 A2017u

I was previously on CM13 rooted and unlocked. Decided to upgrade to B15 today. Everything went great and installed Beast mode rom with Magisk (hopefully to allow DTVnow app to work). Magisk showed my safetynet was still tripped so I figured I would need to lock the bootloader. Used adb to fastboot oem lock and immediately the phone rebooted. It will now flash the ZTE logo and then the red led flashes twice and it turns off.
I can get into EDL mode. I can successfully send a recovery using tenfar's tool, but I have not been able to get into any of the recoveries I have tried so far. I tried Mi Flash, but I get an error from that as well. Any ideas what I should do next? I think I need to find a stock A2017u B15 recovery, but I have not been able to find that yet.
Code:
[0.00 COM4]:[COM4]:start flash.
[2.05 COM4]:cannot receive hello packet,MiFlash is trying to reset status!
[4.61 COM4]:cannot receive hello packet,MiFlash is trying to reset status!
[7.17 COM4]:try to reset status.
[7.17 COM4]:Switch mode back
[7.17 COM4]:cannot receive hello packet,MiFlash is trying to reset status!
[7.19 COM4]:eek:bject reference not set to an instance of an object.
So shortly after I typed this I realized I could grab the recovery out of the miflash B15-NEW_FULL. Flashed that with the tenfar tool and although I still couldn't access recovery, I can now use miflash! Did the full install and things seem to be working now!
wolly6973 said:
So shortly after I typed this I realized I could grab the recovery out of the miflash B15-NEW_FULL. Flashed that with the tenfar tool and although I still couldn't access recovery, I can now use miflash! Did the full install and things seem to be working now!
Click to expand...
Click to collapse
Gotta keep that bootloader unlocked on any kind of custom software, man. Lol. Did you enable Magisk Hide in the Magisk Manager before you checked SafetyNet? That's the only reason I can think of that it wouldn't have passed, but hey, at least you were able to get everything working again.
wolly6973 said:
So shortly after I typed this I realized I could grab the recovery out of the miflash B15-NEW_FULL. Flashed that with the tenfar tool and although I still couldn't access recovery, I can now use miflash! Did the full install and things seem to be working now!
Click to expand...
Click to collapse
What is the file you were able to flash with the tenfar tool? I am stuck!
I'm completely bricked. I've even contacted ZTE support via chat.
2017U on stock B15 w/ TWRP 3.1 & SuperSU 2.69; I then flashed the stock recovery and attempted to updated to the latest 7.1.1 (I forgot to unroot). It said it was successful, however when it rebooted, the phone set up like a brand new phone (still on B15 though :/). Shortly after finishing the initial set up, I received the same OTA notification for 7.1.1. It tried to install, and never booted back up. Refuses to go to recovery or fastboot, and PC does not recognize ADB or EDL - is says it's in DFU (which ZTE support said was "Device Firmware Upgrade" mode). It just sits on a black screen with a constant red LED.
Any help at all is appreciated. I'm pretty much left with a $400 paper weight.
t2jbird said:
I'm completely bricked. I've even contacted ZTE support via chat.
2017U on stock B15 w/ TWRP 3.1 & SuperSU 2.69; I then flashed the stock recovery and attempted to updated to the latest 7.1.1 (I forgot to unroot). It said it was successful, however when it rebooted, the phone set up like a brand new phone (still on B15 though :/). Shortly after finishing the initial set up, I received the same OTA notification for 7.1.1. It tried to install, and never booted back up. Refuses to go to recovery or fastboot, and PC does not recognize ADB or EDL - is says it's in DFU (which ZTE support said was "Device Firmware Upgrade" mode). It just sits on a black screen with a constant red LED.
Any help at all is appreciated. I'm pretty much left with a $400 paper weight.
Click to expand...
Click to collapse
Have you try this:
Option 1: Zadig driver not going to work if you want to use MiFlash. Try to use in this post https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Option 2: if 1 not work, i found this http://www.modaco.com/forums/topic/337757-update-save-ur-bricked-v880-and-also-the-imei/
You can do similar using full firmware B29/B15
Tell me if it works
tamahouse02 said:
Have you try this:
Option 1: Zadig driver not going to work if you want to use MiFlash. Try to use in this post https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Option 2: if 1 not work, i found this http://www.modaco.com/forums/topic/337757-update-save-ur-bricked-v880-and-also-the-imei/
You can do similar using full firmware B29/B15
Tell me if it works
Click to expand...
Click to collapse
Option 1 does not work and in the instructions for option 2, the links to the necessary files just take me to this wheretowatch website.. so i don't know if that would work or not.
jwilensky said:
What is the file you were able to flash with the tenfar tool? I am stuck!
Click to expand...
Click to collapse
Tenfar allows you to flash a recovery. I used the stock recovery.img file from miflash. You will want to try using a recovery from whatever version you have installed.

Please help! ZTE Axon 7 won't boot after deleting Lineage and TRWP

Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Try to boot into bootloader interface, and issue command "fastboot flash recovery TWRP.img" on your computer( the current working directory should contain the TWRP.img file) . If your bootloader is unlocked, you should see no error of this command. Then press up/down button to select recovery mode. You should see the familiar TWRP again. Good luck!
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
If you dont have recovery, flash it from edl mode, you can flash twrp or stock.
Once you install it, performa a full wipe from stock recovery, and flash a full zip.
I have similar problems, I dont loose recovery, but stock dont boot after coming back from aosp, a factory reset did the job. I think is because different filesystems in data partition
Choose an username... said:
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
Click to expand...
Click to collapse
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
tempest89 said:
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
Click to expand...
Click to collapse
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Choose an username... said:
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Click to expand...
Click to collapse
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
tempest89 said:
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
Click to expand...
Click to collapse
Lol fastboot is not something like EDL, it looks similar to the 5 sec screen...
When you get the 5 sec screen, use the vol keys and pwr to get to the Fastboot option and enter - it should reboot and get to fastboot after some time
You should look up what fastboot, EDL, ADB and DFU are before doing all this stuff - you can mess up badly, and by not knowing you're complicating everything - my explanation and your understanding

Can anyone help me fix my Axon 7.

I tried to unlock my phone (A2017G) and flash lineage OS today following Controllerboys guide, but must have done something wrong, I managed to unlock it and flash the bootstack, but I hit an error when trying to flash LOS and so decided to reboot the system and try again, however when rebooting the system I got the error "Your device software can't be checked for corruption, Please lock the bootloader". And I cant seem to access TWRP anymore just the stock recovery.
Is there a way that I can just flash stock OS and be able to use my phone?
King Norman said:
I tried to unlock my phone (A2017G) and flash lineage OS today following Controllerboys guide, but must have done something wrong, I managed to unlock it and flash the bootstack, but I hit an error when trying to flash LOS and so decided to reboot the system and try again, however when rebooting the system I got the error "Your device software can't be checked for corruption, Please lock the bootloader". And I cant seem to access TWRP anymore just the stock recovery.
Is there a way that I can just flash stock OS and be able to use my phone?
Click to expand...
Click to collapse
That's not an error message, it's the unlocked bootlaoder screen. get used to it, you're gonna see it every time you reboot
You probably didn't flash the Universal Bootloader. You didn't even read. You should install TWRP again with axon7tool, then get there and flash the Universal Bootloader, then the A2017G modem, the the ROM. If that doesn't work just download MiFlash and the latest G package and flash it

Corrupted recovery, no o/s, what to do now?

I have a Axon 7 A2017U, bootloader unlocked. My recovery is corrupted after attempting to flash a older version of TWRP in recovery. I can no longer reboot into TWRP via recovery, it hangs at the ZTE powered by screen. I can't boot into the o/s, it too was corrupted while attempting to restore to stock using the DrakenFX's guide.
Booting into fastboot is a no go either, it just hangs at bootloader screen.
Any suggestions on where to go from here or how to fix the corrupted recovery?
You need to go into EDL mode and use MiFlash and flash a back to stock package. You can find a package here: https://androidfilehost.com/?w=files&flid=160532
Hello maybe i have same problem here. I have A2017G and maybe i have only woked unlocked bootloader. I dont think my EDL is working becouse i cant connect with ADB. Dont have any acces to recovery... i messed up step by step remember.
1. downloaded toolkit and woked fine - 2 installed drivers and working fine with EDL. 3 unlocked with no problems , 4 flashed TWRP with no problems and then i wanted to install lineage os. Downloaded last version lineage , and google apps and one file "A2017G_N_Modem.zip" and put all 3 files on my SD card. I wipe everything and then first installed modem file OK, but on second try with Lineage OS i have any errors and i just cant continue. After this i wanted to go back to original OS and i just locked my bootloader with axon toolkit and after restart i have acces only to Unlocked Bootloader. tryed everithing with axon7toolkit but nothing working. If i try to EDL mode when press volumeUP+volumeDOWN+power my phone have black screen and i thing is powered OFF.
OMFG i just typed "fastboot oem unlock" 5-6 time when i started phone to my bootloaders and now it unlocked and have acces to my TWRP.
Teet1 said:
You need to go into EDL mode and use MiFlash and flash a back to stock package. You can find a package here: https://androidfilehost.com/?w=files&flid=160532
Click to expand...
Click to collapse
Thanks, I flashed it with A2017U_B19-NOUGAT_FULL_EDL and was able to flashed twrp recovery. I was hoping the o/s would be fixed too but I get this error message as soon as o/s load "settings keeps stopping, close app". It appears it's a bad or incorrect stock file. I had to format data in TWRP recovery as the drive was encrypted. So now i'm back at square one.
Bad o/s but working recovery, so I attempted to flash these files to get back to stock but was unsuccessful. It would flash halfway and then just restarts and hung at the bootloader unlock screen.
A2017UV1.0.0B29_RollBackModded.zip
A2017UV1.1.0B32_bootstack_by_DrakenFX.zip
A2017UV1.1.0B32_StockSystem_by_DrakenFX.zip
Am I on the right track? Or should I be flashing with a different os variant?
freeb0rn said:
Hello maybe i have same problem here. I have A2017G and maybe i have only woked unlocked bootloader. I dont think my EDL is working becouse i cant connect with ADB. Dont have any acces to recovery... i messed up step by step remember.
1. downloaded toolkit and woked fine - 2 installed drivers and working fine with EDL. 3 unlocked with no problems , 4 flashed TWRP with no problems and then i wanted to install lineage os. Downloaded last version lineage , and google apps and one file "A2017G_N_Modem.zip" and put all 3 files on my SD card. I wipe everything and then first installed modem file OK, but on second try with Lineage OS i have any errors and i just cant continue. After this i wanted to go back to original OS and i just locked my bootloader with axon toolkit and after restart i have acces only to Unlocked Bootloader. tryed everithing with axon7toolkit but nothing working. If i try to EDL mode when press volumeUP+volumeDOWN+power my phone have black screen and i thing is powered OFF.
OMFG i just typed "fastboot oem unlock" 5-6 time when i started phone to my bootloaders and now it unlocked and have acces to my TWRP.
Click to expand...
Click to collapse
So you didn't read all of the hurdles and warnings about locking the bootloader with non-stock firmware?
Plus you also didn't find out about the Universal Bootloader? Did you even read the installation steps???
You had an error 7, which is that you forgot to install the Universal Bootloader. Do so this time.
EDL has nothing to do with ADB. You can access it with the phone completely off... (volume up and down, and insert usb)

re-installing stock recovery on Nexus 6P

I installed TWRP custom recovery on my Nexus 6P. I was able to boot into it ONCE. When i next tried to enter Recovery, i get a screen showing the Android Robot and the following statement: NO COMMAND
I tried to re-install TWRP using adb twice, but the result is the same.
How can i either fix TWRP, or re-install the stock recovery
I am basically a beginner here, so any help would be appreciated
If you installed the stock system image and then booted into it, it likely automatically reinstalled stock recovery also. I don't know why it does that, but it does. This is why I usually just reinstall TWRP again after each monthly update is completed.
You should use fastboot to install the images, not adb. The command should look like:
fastboot flash recovery twrp.img
I think i just worded it wrong - I used the above command (fastboot flash recovery twrp.img) to install twrp, and then, when i couldn't get back into recovery (Power - Volume Up combo just lest to screen that stated "No Command".), i used the fastboot flash recovery twrp.imp twice to try to re-install TWRP, but it didn't work
I also downloaded the latest stock Oreo ROM, copied the recovery.img file, and used fastboot.flash.recovery.img to try to re-install the stock recovery, but that didn't work either
The once time that TWRP work, it asked it I wanted to use TWRP is read only, to twice i selected NO (don't know if this matters)
Any other suggestions to fix TWPR, or re-install the stock recovery image???
When you say it didn't work, can you expand on that? Was there an error or anything?
hmodiano said:
I think i just worded it wrong - I used the above command (fastboot flash recovery twrp.img) to install twrp, and then, when i couldn't get back into recovery (Power - Volume Up combo just lest to screen that stated "No Command".), i used the fastboot flash recovery twrp.imp twice to try to re-install TWRP, but it didn't work
I also downloaded the latest stock Oreo ROM, copied the recovery.img file, and used fastboot.flash.recovery.img to try to re-install the stock recovery, but that didn't work either
The once time that TWRP work, it asked it I wanted to use TWRP is read only, to twice i selected NO (don't know if this matters)
Any other suggestions to fix TWPR, or re-install the stock recovery image???
Click to expand...
Click to collapse
If you want TWRP to stick, you need to flash either SuperSU or magisk. The Android with the exclamation mark is what stock recovery looks like.
Once you have TWRP installed and wish to keep it, you don't need to flash stock recovery in the monthly update. Just boot into TWRP after flashing update and root again.
chaoticyeshua said:
When you say it didn't work, can you expand on that? Was there an error or anything?
Click to expand...
Click to collapse
When the phone is turned on, it never progresses beyond the first screen. No error codes, it just does not proceed to boot up.
I had to buy a new phone (need it for business, but i given up on trying to install Resurrection Remix on the Nexus 6P, which was the reason I was trying to install TWPR and SuperSU. So far, I have only accomplished turning the phone into a brick door stop!!!
hmodiano said:
When the phone is turned on, it never progresses beyond the first screen. No error codes, it just does not proceed to boot up.
I had to buy a new phone (need it for business, but i given up on trying to install Resurrection Remix on the Nexus 6P, which was the reason I was trying to install TWPR and SuperSU. So far, I have only accomplished turning the phone into a brick door stop!!!
Click to expand...
Click to collapse
Use Magisk it's the better solution for root. Never had boot up issues with it just stock you have to boot once through before flashing. Custom ROMs you can flash right away.

Categories

Resources