Can anyone help me. Stuck in fastboot. - ZTE Axon 7 Questions & Answers

Hi,
Today I decided to finally try fix my A2017 (Google crashed constantly and I couldn't download apps).
Anyway, in order to unlock the bootloader and install twrp, I decided to follow the guide posted here: https://www.reddit.com/r/Axon7/comments/8n3mpw/axon_7_unlock_root_and_rom_installation_guide/ I think everything was going well until I got to step 12.
I managed to unlock the bootloader, however, afterwards, the phone didn't reset. When I reset the phone manually, it simply shows a green ZTE logo, then boots straight into 'fastboot mode'. I am able to get back to 'recovery mode' from within fastboot, but that’s it.
I have no clue how to fix it. Ultimately, I was trying to follow the guide posted here: https://forum.xda-developers.com/axon-7/development/rom-slm8-t3947376
However, in order to do that, I had to unlock the phone. Which is why I followed the first guide.
I have searched around trying to find a solution, but I can't. I thought maybe my phone was stuck in DFU mode. So I tried to follow a guide to get me out of it, but when I installed ZTE DFU_MultiDL app, it tells me that 'the computer doesnt have USB ports' whenever I port scan trying to find my phone.
I am fed up searching. Can anyone help? Thanks.

I suggest using this tool. You can also flash full firmware corresponding to your phone version.
Axon 7 EDL tool:
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759

Related

[Q][SOLVED] Bricked ZTE Libra

Hi! I have a bricked ZTE Libra (Sapo A5 in Portugal) and no mather how much I search for solutions I only seem to make things worse, so I was hoping someone here could help me.
Things started to go wrong after flashing a CyanogenMod rom. Everything worked except two things: I couldn't use anything that required my SIM card (so no phone or messaging) and I could not access the recovery screen (clockworkmod).
Without the recovery screen, I turned to ROM Manager but since it uses clockworkmod to do its work it didn't help.
Then I started trying other ways to recover my phone, until I tried ADB which allowed me a shell in my android. But then I broke it all by doing "wipe system" which cleaned my system of everything that was still working and left me with an expensive brick.
Now all I can do is boot until I see the green droid. If I don't press the volume buttons it goes into "device" mode and I can see it listed under "adb devices" but have no idea what to do with it.
If I press the volume button down to go into recovery mode it keeps flashing but never really goes anywhere.
If I press it up to go into the bootloader it stays the same and the only thing I can use to tell me something is different than the normal mode is that lsusb reports the vendor as "Google Inc." instead of what it reports in normal mode: "ONDA Communication S.p.A.".
With this I'm not even sure if I can get to the bootloader or not, but even if that is the bootloader, I have no idea what to do with it that might help me recover my phone.
By the way, I'm trying all this on Linux, although I could try solutions in Windows if required.
Can anyone tell me what can I do in this situation?
Ok, maybe my first post wasn't that easy to answer, so I'll make a simpler question to see if someone can help me.
What can be done at my android's bootloader? What is it for and what tools do I need to use to do it?
You could try installing ClockworkMod recovery using wbaw's guide here http://forum.xda-developers.com/showthread.php?t=1319257 Once that's installed you should be able to flash a new rom with it.
In bootloader mode you can flash a new kernel or recovery image using fastboot.
If you follow that guide that I wrote & Amphoras linked to then you should be able to get a working clockworkmod installed and then you can use that to flash a working rom, or restore a backup.
Thank you both, I'll try what you said as soon as I can and then I'll let you know if it worked!
Ladies and gentleman, today a miracle happened, my ZTE came back from the dead!
Apparently the problem was that I installed some GEN2 applications on my GEN1 model.
I found this while reading the tutorial you suggested, after which I upgraded my ZTE to GEN2 which allowed me to slowly recover everything else.
So, I have to say, thank you very much, and I hope I won't need your help again anytime soon! xD

after rooting and unlocking bootloader my PC won't recognize my phone through ADB

TWRP is still installed and magisk as well, but now it's not rooted and the bootloader is still locked. I am so confused about how this happened, does anyone have any ideas why this happened, or what I can do to repair it? The phone still works but it won't update and it's a little wonky. msm download tool doesn't even recognize it. thank you for any help!
EDIT: now it won't boot up to anything, only boots into the bootloader, won't go into recovery or anything. please help! haha
msmdownload tool, grab the one fitting to your phone, see in Guide News section
The msmtool won't even recognize it, that was the first thing I tried
RMA
I faced a similar issue but I was able to get it working through the MSM tool. Make sure you are holding the volume up and volume down for 15 seconds before connecting it to MSM. It should work if you follow the guide.

Un-debrickable state ?

Hello guys,
I'm fairly certain I'm stuck in an un-debrickable state but I'll ask just in case. My phone is F800K.
I was toying around with LGUP in order to downgrade and root my phone. So far, so good.
I then tried to update to the latest android 9 again, but keep the root active. That's where things started to go south, so I decided to go back.
I followed a couple of "back to stock" guides but now I'm screwed.
- The phone does not boot.
- Download mode is broken, the phone doesn't connect to my computer while in download mode, so it's unusable.
- TWRP is gone. When I try to boot to recovery after yes both times I get nothing. Not the stock recovery and not TWRP, it just tries to boot as usual.
- Can't seem to go back into fastboot either. I tried VOLDOWN + plug-in the phone about 200 times now, to no avail.
Is there another way that I'm missing ?
Thanks.
growiel said:
Hello guys,
I'm fairly certain I'm stuck in an un-debrickable state but I'll ask just in case. My phone is F800K.
I was toying around with LGUP in order to downgrade and root my phone. So far, so good.
I then tried to update to the latest android 9 again, but keep the root active. That's where things started to go south, so I decided to go back.
I followed a couple of "back to stock" guides but now I'm screwed.
- The phone does not boot.
- Download mode is broken, the phone doesn't connect to my computer while in download mode, so it's unusable.
- TWRP is gone. When I try to boot to recovery after yes both times I get nothing. Not the stock recovery and not TWRP, it just tries to boot as usual.
- Can't seem to go back into fastboot either. I tried VOLDOWN + plug-in the phone about 200 times now, to no avail.
Is there another way that I'm missing ?
Thanks.
Click to expand...
Click to collapse
It does sound like a hard brick... you said fastboot is hosed, do you have access to adb in any way?
Sent from my moto g(6) play using Tapatalk
None that I know of, that's the issue. If I had access to either fastboot, adb or download mode, I could most likely salvage this, but I can't seem to be able to.
The weirdest thing is the broken download mode, I couldn't find anybody with the same issue...
growiel said:
None that I know of, that's the issue. If I had access to either fastboot, adb or download mode, I could most likely salvage this, but I can't seem to be able to.
The weirdest thing is the broken download mode, I couldn't find anybody with the same issue...
Click to expand...
Click to collapse
On my lg tribute HD (ls676) fastboot was removed by lg themselves on Android 6.0.1 quietly with a security update and download mode never worked right for me. Without access to fastboot, adb or even diag mode it really sounds like you have a hard brick. if i can find a solution of some kind, I'll definitely let you know.
Sent from my moto g(6) play using Tapatalk
What would "diag mode" be and how can I check if I can access it ?
Small update for people who stumble upon this thread, I managed to save my phone by using the Qualcomm Test Point, see here: https://forum.xda-developers.com/showpost.php?p=81697447&postcount=128

What to do if you didn't follow the QFIL directions?

Hi, and please tell me there's something that can be done to help. I have the AT&T V35 and was really happy to see the bootloader was unlockable, so I went ahead and downloaded QFIL and thought I was following the step by step directions for putting it into the correct download mode. There were no issues at all, but I did have a few more things open on my laptop that were partially covering the directions that could have led to my problem. There was a part of the directions where there are 6 or so partitions that needed to be backed up and substituted, I only saw 2. That's when I thought I was finished and proceeded to reboot the phone, having only 2 of the partitions saved and that caused me issues because now I can plug the phone into any USB port and the computer doesn't even recognize anything there. Also the top left corner just says "..ANY BUTTON TO REBOOT PHONE".
I think if I could get it into download mode or something I could at least reflash the .kdz file and replace the damaged firmware with good firmware, but I got to get the drivers to recognize the phone even being plugged into the USB port first. It seems like I'm going to have to repair it with Octoplus at this point, but maybe someone here has a better option, as I do not have the Octoplus or any other JTAG equipment to use. Any thoughts?
This has been answered by several people, if you can search the forum. In the original root thread, OP cmrntnnr (original post) and vlad48 (post #11) talks about it. I also provided some information regarding this in post #74. If you get stuck post in the thread instead of private message so others can see it. Make sure you thank the contributors. Here is the thread link:
https://forum.xda-developers.com/lg...loader-unlock-root-instruction-t4052145/page8
Edit: Also, you shouldn't need Octoplus or JTAG since the engineering bootloader is out and QFil can be used to fix almost any state the phone is in. Just follow instructions to get in QFil mode (may take several tries because it is tricky, hard key combination), flash the files for abl_a and laf partitions, you can use the ones i provided. Just remember once bootloader and laf partitions are restored, even if phone can't finish booting, you can still put it into download mode by holding the vol+ button while plugging in the USB cable.
ELutts said:
Hi, and please tell me there's something that can be done to help. I have the AT&T V35 and was really happy to see the bootloader was unlockable, so I went ahead and downloaded QFIL and thought I was following the step by step directions for putting it into the correct download mode. There were no issues at all, but I did have a few more things open on my laptop that were partially covering the directions that could have led to my problem. There was a part of the directions where there are 6 or so partitions that needed to be backed up and substituted, I only saw 2. That's when I thought I was finished and proceeded to reboot the phone, having only 2 of the partitions saved and that caused me issues because now I can plug the phone into any USB port and the computer doesn't even recognize anything there. Also the top left corner just says "..ANY BUTTON TO REBOOT PHONE".
I think if I could get it into download mode or something I could at least reflash the .kdz file and replace the damaged firmware with good firmware, but I got to get the drivers to recognize the phone even being plugged into the USB port first. It seems like I'm going to have to repair it with Octoplus at this point, but maybe someone here has a better option, as I do not have the Octoplus or any other JTAG equipment to use. Any thoughts?
Click to expand...
Click to collapse

Lumia 520 Unable to enter flashing mode

Hello!
I recently got my hands on a Nokia Lumia 520 for tinkering with. Its running on really old firmware, and I figured before I try anything weird, I'd mess around with it in its stock state. Thus, I tried updating the firmware.
The internal updater returned an error, stating that it could not contact the server for whatever reason. I figured this is most likely due to the Windows phone being discontinued, so I scoured the internet for firmware files. I eventually stumbled upon a YouTube guide that linked to a guide on Microsoft's Own guides page. It explained how to reinstall the firmware to a stock state. Desperate for progression. I gave it a shot.
The guide provided the "windows Device recovery tool", Which I would install on my windows 11 machine. I then proceeded to run the software and plug in the phone. HURRAY! It was able to tell me exactly what type of phone it was. Clicking the option to proceed, I was shown a screen explaining just how dated my firmware was. Suggesting It would fetch newer if not the latest firmware for me. I clicked on install and it started downloading.
I waited patiently for the software to download the firmware. After which it went to the installation screen. It then attempted to put the phone in flashing mode. Explaining that in this mode, the phone would restart, then have a blank screen. Instead what happened was that the system restarted normally, asking me to unlock the device. I wondered if maybe I had been impatient, so I waited for another while. The phone restarted again, still on the normal lock-screen. This happened another two times before the Recovery tool gave up and told me it had failed.
My question: Is there any reason why it would do this? Are there any methods to get it into flash mode?
I would hate to discard the potential of this device simply due to the inability to flash it. And I really hope it can be helped. Please let me know if there's anything else I should share about this. I'll happily take any help I can get!
Thanks in advance!
Edit, after a lot of trial and error, I managed to force it into flashing mode. Turns out the guides I followed missed a step. Pressing the Power and Camera buttons did the trick

Categories

Resources