Related
[Q] New Nexus 7, Win 7, Nexus 7 Toolkit can't boot into Fastboot, "Too Many Links"
SOLVED!
So I went ahead, tried flashing the stock recovery, no joy (no recovery menu at all - just a bad-android image). After a while, tried flashing CWM touch (via Toolkit) - and now it's working. So, everything seems good now.
----------------
UPDATE 5 - PARTIALLY SOLVED:
So, after the last couple of things, I began to suspect bad hardware, as I alluded in those updates. And I was right.
But... it wasn't the hardware you might have thought.
It was...
(this is embarrassing)
The USB cable.
Yes, the USB cable. It was the wild variations in recognizing the fastboot mode that made me suspicious. Replaced the USB cable with another one and... stability, achieved. Unlock, root, recovery program and SU program all went without a hitch. In fastboot mode, for the first time, the device serial number shows.
HOWEVER - things are not perfect. The recovery mode from the bootloader still gives the bad-android icon.
I just used the toolkit to reflash stock recovery back to the device. This completed rapidly, without error. I then tried the recovery option in the bootloader, but again, no joy.
So at this point, I point a finger partly at the tools used to flash this - they claim there is no problem, yet the flash doesn't take at all, and no error is given. As a sometimes firmware developer, I'm used to flash being followed up by a checksum or other test to verify success of the flash. Is that not being done (shame, if not). If it is, then apparently the flash works, but the software being flashed doesn't? The stock recovery???
Any ideas on how to get this back? I just did the full unlock, which wiped all user data, and proceeded from there. I now have a solid connection, but don't really know how to get things back.
Perhaps I need to manually reinstall 4.2.2?
----------------
UPDATE 4:
So, on a lark, from fastboot in Android, I selected the "Recovery" option - it starts to boot that, then gives the Android with red triangle and exclamation point. So, looks like the recovery was toasted.
This was a brand new device earlier today. It has been completely wiped twice, and none of this has gone away. Seriously: bad device?
-----------------------
UPDATE 3:
So, I thought I'd try the direct approach, as outlined here:
http://forum.xda-developers.com/showthread.php?t=1741395
Device is in Fastboot, Device Manager shows it as ok.
I run fastboot flash recovery <file> -- and IMMEDIATELY get "fastboot has stopped working" - that's right, a hard crash in fastboot. And this is repeatable.
Am I wrong in thinking this looks more and more like a driver problem? I note that fastboot is recognized as a device maybe half the time - the other half, it gets an exclamation point in Device Manger. All I do then is restart the bootloader using the bootloader menu, and usually it fixes right up. But that's obviously a huge red flag, as the device should be recognized every time.
Is this a defective Nexus? The only thing that seems dicey is anything relating to fastboot/bootloader (which is, however, unlocked - or at least it says it is).
----------------
UPDATE 2: Using the "restart bootloader" in fastboot results in slightly worse non-recognition of the device. When I do that, I get a straight "USB Device Not Recognized" from windows - the device manager doesn't even show "Android Phone" as a class of device in this case.
---------------------
UPDATE 1: I found the thread talking about missing entries in the INF file. I added these, and got a somewhat, but not entirely, stable recognition of the Nexus 7 when in fastboot mode. Basically, sometimes it is recognized, other times it is not. By "recognized", I mean that the Windows Device Manager shows the device as "Android Bootloader Interface", with no indication of a problem (which it only does in fastboot mode - it shows as a composite ADB device when booted normally).
However - it seems it fails to recognize fastboot about half the time, although it seems that that is related to reboots - that is, a fresh boot, then going to fastboot through adb seems to work. But restarting fastboot manually fails to be recognized (Windows shows a bang by the "Android Bootloader Interface", and says the device "failed to start").
So, using 4.3.5 Nexus 7 toolkit, I tried to unlock the bootloader. Windows recognized fastboot mode, but the process errored out anyway, after maybe 15 seconds, saying "Too Many Links" - the same error as before.
Again, brand new 32gb wi-fi-only Nexus 7, with 4.2.2 update and the most basic configuration only (dev mode, usb on, etc.)
Any ideas?
-------------------------------------------------------
ORIGINAL
So this is a new, out of the box nexus 7. The only setup has been to connect to wifi, update to 4.2.2, and enable developer mode and USB debugging.
Running latest paid-for toolkit - Update 29 Feb 13, version 4.3.5
Just about everything requires the insecure fastboot, but every time I try any operation that attempts it, I get:
Booting into fastboot mode
downloading 'boot.img' ...
FAILED <status read failed <Too many links>>
I basically can't do anything - in this case, I was trying to backup.
It is being done on 64-bit win7 system that had drivers, and worked for another nexus 7 a couple months ago. But, just to be safe, I uninstalled the drivers, rebooted, and installed.
However, I see this on the home page of the toolkit:
FASTBOOT MODE [If serial shows, drivers are installed]
List of Devices attached
ADB Mode
List of devices attached
<numeric code> device
From this, it seems I should expect the word "serial" to show up if the drivers are installed?
I then unplugged the Nexus, refreshed the menu, and both Fastboot and ADB show no devices.
I then plug in the nexus - I get the usual two tone "device attached" sound, no warning or error message from Windows.Checking the Windows device manager, I see a section "Android Phone" with the entry "Android Composite ADB Interface". There are no unknown devices, which would seem then that drivers are working.
So, another refresh of the main menu, and again, I see, under ADB MODE, a single device ID number, and the word "device".
I don't know what to make of this. Apparently, per the "if serial shows" message in the main menu, drivers a NOT installed. But according to Windows, they are.
This perhaps matches the fastboot failure.
Should I see "serial"?
In any case, what do I do to get the drivers to work properly if they aren't?
And if they ARE working, then what is wrong with fastboot?
At this point, I think the toolkit is broken, and worked a couple months ago.
No, you should not see "serial". Your devices serial number should be displayed under whichever path is valid at that time. If you are in the bootloader, your device serial number should be under "fastboot". If you are booted normally, your device serial number should be under "ADB".
I used this guide:
http://forum.xda-developers.com/showthread.php?t=1741395&highlight=guide
Erik.Leach said:
No, you should not see "serial". Your devices serial number should be displayed under whichever path is valid at that time. If you are in the bootloader, your device serial number should be under "fastboot". If you are booted normally, your device serial number should be under "ADB".
I used this guide:
http://forum.xda-developers.com/showthread.php?t=1741395&highlight=guide
Click to expand...
Click to collapse
I've since figured that out. There was nothing at all, when in fastboot mode, only ADB. But then I found the thread describing two missing INF entries. I added those, updated the driver, and now the fastboot mode (which wasn't even recognized by windows) is now ok in the Device Manager. However, in the main menu, it shows, literally, "??????????" instead of a serial number - that is, there are question marks instead of serial number, Following that, a few spaces and then "fastboot".
Apparently, there are still inadequacies in the driver as relates to very, very new models running 4.2.2 (which this is).
BTW, I do believe I read somewhere that the stock recovery initially comes up with just the android on his back with the warning sign. You then have to hold power and tap volume up or something like that and the recovery menu becomes visible. I could be wrong, I know I had to do this on my old GNex, and those were the steps that worked.
Erik.Leach said:
BTW, I do believe I read somewhere that the stock recovery initially comes up with just the android on his back with the warning sign. You then have to hold power and tap volume up or something like that and the recovery menu becomes visible. I could be wrong, I know I had to do this on my old GNex, and those were the steps that worked.
Click to expand...
Click to collapse
Interesting. I did re-flash the stock recovery, and could get that without the android image.
stickplayer said:
Interesting. I did re-flash the stock recovery, and could get that without the android image.
Click to expand...
Click to collapse
That may have been a GNex thing that I am remembering. Either way, I'm glad you got everything all straightened out. :good:
I'm still kinda new at this stuff too, but if you need any more help, feel free to hit me up. Even if I don't know the answer to the question, I'll help you find it.
Erik.Leach said:
That may have been a GNex thing that I am remembering. Either way, I'm glad you got everything all straightened out. :good:
I'm still kinda new at this stuff too, but if you need any more help, feel free to hit me up. Even if I don't know the answer to the question, I'll help you find it.
Click to expand...
Click to collapse
Thanks! Next is trying to put 4.x on a Samsung Vibrant.
Hi guys,
I had posted a brief thread a couple weeks ago stating that my Nexus 4 restarted by itself, and got stuck in the bootloader animation loop. I couldn't remember whether I had enabled USB debugging in my phone prior to it killing itself (not rooted, completely stock, did the OTA 4.4.3 update just a few days before my phone died, and phone's been out of warranty for quite a while now ).
So I installed the SDK developer tooklit, and followed instructions to set up ADB.
However, everytime I boot my nexus 4 into recovery mode/"safe" mode, I get the following screen ("Screenshot 1" below).
From there, when I boot into recovery mode, I get the following screen ("Screenshot 2").
Every time I connected my phone to my laptop (keep in mind that I cannot start it .. I always plug it in when I'm in "Screenshot 1" mode) and try to used "adb devices", I get the following cmd screen ("CMD ADB Devices" picture below). I've repeated this process and tried plugging the nexus in during various points in different "safe mode" options. Same result: nothing is detected.
So I got frustrated at trying to backup any data from my phone, and just chose the "wipe data/factory reset" option from the nexus recovery mode, and I got this screen ("Screenshot 3"). I've tried this several times, and I keep getting this screen.
So my nexus committed suicide, and I'm totally not sure what to do. I've been trying to learn how to use ADB etc for the past couple of days by scouring through the xda nexus 4 forums, but I'm still very much a n00b. Do you guys have any advice as to what I can do to get my nexus 4 back to a usable state again?
Things I've already tried (in order):
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
I also tried to ADB sideload a stock Nexus 4.4.3 factory image, but it is useless since my device won't even show up in CMD when i enter ADB devices.
However, the problem is that my nexus is never detected in CMD no matter what combination of things I tried, so I can't even do half of the things both of those thread instructions state.
I would greatly appreciate ANY ways to factory reset or flash working firmware on my phone! :highfive:
Edit: I reinstalled Android SDK, and connected my nexus to my laptop after entering fastboot ("safe" mode; volume down + power from phone off state), and I was able to get a slightly better looking CMD window when running ADB Devices command (See "CMD ADB Devices 2" picture). However, same problem as before, where my phone isn't even registering via ADB.
So again, your input would be tremendously appreciated.
If you boot in the bootloader (Volume- and Power) it's normal that you can't use adb. You have to use fastboot in the bootloader.
What is the output of fastboot devices?
Code:
fastboot devices
Have you already tried to flash the factory image or did this fail, too? You have to download the factory image from google, extract it and connect the phone in the bootloader/fastboot mode. Run the flash-all.bat then and it will reflash the stock rom. This will wipe your data, but I guess this shouldn't be a problem for you anymore because you already tried to do a factory reset!
If this worked, boot your phone and if it works fine, I would recommend to relock the bootloader (because it gets unlocked automatically if you flash the factory image and if you don't want to root/modify your phone in any way, your bootloader is usually locked):
Code:
fastboot oem lock
Try it and if there are any other problems or if it doesn't work, just ask again
I really need the help of one or more of this forums intelligent minds. As I'm sure you'll see, I've posted this in the QA forum, but have had no hits so far....thus the reason for posting here.
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance! I'm at my wits' end
Try fastbooting a recovery like TWRP thati s updated then flash a rom.
disclaimer: I might be no help at all!
You have fastboot -- go learn all the fastboot commands... you need to know the tools and figure a solution!
erase... hmm? why? What about factory reset? I see you are not using LOS 13 but stock image... need root? Basically, I would factory reset/wipe sdcard, then install recovery (TWRP) [okay, so first you would need to use fastboot to install custom recovery)...THEN, push (fastboot an image.zip (LOS or stock) to sdcards, install, and reboot!
Good to have WUG... another tool in the chest (I have never seen it or used it)
Ok, so one clue is that if your computer cannot see it, that says to me RED FLAG... ADB drivers? but you say fastboot works, hmm... I think this is the problem... Koush's universal ADB drivers? official Google drivers? Could these help!
Erasing screen? Hmm...
I would say, for the hell of it, try flashing different ROMs, Recoveries, and Drivers.... you are basically trying to...
Factory Reset/wipe SDcard [system, cache, ... everything], Flash custom recovery (optional), then, some how (fastboot or mycomputer) get an image on to /sdcard, then, install, then, reboot!
Good luck!
luckyheel said:
I really need the help of one or more of this forums intelligent minds. As I'm sure you'll see, I've posted this in the QA forum, but have had no hits so far....thus the reason for posting here.
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance! I'm at my wits' end
Click to expand...
Click to collapse
Why not try this
I have not had this problem with my Nexus 10 but I did once with my Nexus 7 and it may help you.
Instead of trying to flash TWRP and run it (which is not working for you) why not boot into a temporary copy of TWRP and then work from that? To flash TWRP normally (persuming you had renamed the img file to TWRP which makes it easier) you would enter 'fastboot flash recovery twrp.img'. Instead of doing that type 'fastboot boot twrp.img'. This boots into TRWP and from there you will be able run all the options and from there flash TWRP and other images as normal.
If you are having problems with drivers have you used 'USBDeview' ? Run this as Administrator and delete all references to any phone or tablet USB driver and particularly look for devices with Vendor ID '18d1' or '04e8'. Just select them, right click on them and select 'Uninstall Selected Devices'. When they are all cleared reboot your computer and plug your tablet in and it should install the correct driver.
Another option I used successfully with a Nexus 7 in a boot loop was to connect it while running Linux. I don't have a Linux on a computer so I installed one in 'Oracle VM VirtualBox' I don't know Linux but after Googling for help I installed Peppermint Linux and then ADB for Linux. I downloaded the 'TWP' image into a folder in Linux and any other images I wanted. Connect your tablet to the USB port and then on the top menu in VirtualBox select 'Devices' then 'USB' and tick the option which shows your tablet. I then went into what we call a command prompt in Windows but which they call 'Terminal'. Then type 'ADB devices' and if you see it on the list use ADB instead of fastboot. As I mentioned my Nexus 7 was in a boot loop so I typed 'ADB wait-for-device' and as soon as it looped to a point where ADB could see it then the looping stopped and I could flash the images and recover the tablet.
All the best. I hope you are successful.
As long as you can get into bootloader mode, your good.
NOW
If you can't get into boot loader mode? as far as I know...
You're ****ed.
Unless you want to set up usb boot (might not work on Exynos, idk, this is magic to me) and solder the connectors and flash it like they do in factories. That's next level **** too, and considering an N10 is 100$ on amazon you're better off just grabbing a new one.
I realize there are many other threads on this, bear with me please, I was not able to find a solution that works.
-display is broken, shows light but nothing else
-digitizer is 99%? broken, back and menu buttons work, there is some heptic feedback in upper part of the screen
-phone does not have a lock pattern or password, just swipe to unlock
-voice commands work
-phone was rooted a long time ago, I don't recall the mehod, I think the current OS is likely 4.4 but i'm not sure (is there a way to check)?
-I had a custom recovery on it which i think was CWM, again, not sure how to check this now
-I can install apps via web appstore
-At some point I installed a clockroot app (never worked) it's probably still on the phone
-I don't have OTG, ordered one
-I don't want to order a new digitizer
Here are somethings that kind of work and some that don't
-dr.fone shows a USB debug promt with instructions on how to accept the RSA key. I'm guessing USB debugging mode is on but it's not the same computer
-if I have the device in download mode, it is "sometimes" recognized by dr.fone, just says its in download mode and asks to reboot
-if I have the device in recovery mode (i think), it's not recognized at all, does not even show up in device manager
-when phone is just on, it's recognized by the computer, I can browse and backup files (i need to backup google auth app)
-with phone on, its recognized by windows and adb, adb says the device is not authorized.
-however adb does not recognize it if I boot into recovery
I think my best best to just to push the rsa key to the phone in recovery but I'm stuck because the phone is not recognized. I will try re-installing drivers next but I doubt this will help.
Lastly, I wasn't sure if I really do have CWM installed or its stock recovery. So I tried to flash CWM using Odin, with phone in download mode, recognized by Odin, the flash fails with an auth error, i'm reading that might mean the phone is not rooted which is 100% not the case here, maybe the rootclock app is doing something to it.
Any advice?
I'm starting to recall the rooting process a bit and I'm fairly sure I used safestrap method, as I was on 4.4.2-4 NJ something kitcat at the time. So I may not have CWM installed after all.
little bit of progress to report. I'm fairly certain i have safestrap recovery on this phone. So booting into recovery must have been bringing me to the safestrap screen that needs a screen tap to recovery or continue. If I hit power it reboots, if its only 2 options recovery or continue to normal boot, volume down move me to the other option, + power....now adb detects the phone! in sideload mode, lets see if I can do something with this, fingers crossed.
no luck, sideloading seems useless. How can i get myself into recovery!?
I think if I can push the adb rsa key I would be set to use one of the screen mirroring apps. How can I sideload it in?
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?