Hello, I flashed a firmware update through a modified recovery and now phone doesn't boot. It doesn't even show the logo, seems completely dead.
I've tried all combinations of keys, none work; if I push vol+ & vol- and connect it to pc nothing happens, it's not detected by windows or MSM Tool
Could anybody help me?
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Click on Target button and select O2 while using international tool or India while using indian tool or EU when using european tool.
Power your device off.
Maintain volume up and volume down keys to get into Qualcomm EDL mode.
Plug your device to your computer using stock OnePlus cable. (You may let volume keys go once done.)
Click on Enum to be sure your device is detected and press Start.
Wait ~300 seconds.
If this does not work, plugin your device and hold vol-,vol+ and power for a long time.
Make sure that you have qualcomm drivers etc installed.
Win11 can cause problems.
I think I didn't make myself explain correctly; the phone is off and I can't make it switch on. I already tried to enter EDL mode with vol+ and vol- pushed, but the phone is not detected by windows nor by msmtool.
Hammerhand.17 said:
I think I didn't make myself explain correctly; the phone is off and I can't make it switch on. I already tried to enter EDL mode with vol+ and vol- pushed, but the phone is not detected by windows nor by msmtool.
Click to expand...
Click to collapse
You did explain yourself correctly. I had the same problem and by pressing buttons i somehow entered edl mode and it was working.
I think it worked that way for me:
I started MSM tool, changed to eu and pressed start. Than i connected my phone and held down power, vol+ and vol-. But it could be that i hold the buttons before i connected the phone.
It will work somehow im sure. Its nearly impossible to brick a a/b device with a simple rom flash.
As english is not my mother language, I always doubt if I explained correctly, thanks!
Do you remember if there were any sound in windows when you plugged the phone? In mine, nothing happens, as if I wasn't connecting anything.
I've been bricked before but I always got to oneplus logo, but now I have an all-black screen and no reaction at all.
Hammerhand.17 said:
As english is not my mother language, I always doubt if I explained correctly, thanks!
Do you remember if there were any sound in windows when you plugged the phone? In mine, nothing happens, as if I wasn't connecting anything.
I've been bricked before but I always got to oneplus logo, but now I have an all-black screen and no reaction at all.
Click to expand...
Click to collapse
English is not my native language, too.
I had no windows sound, no nothing. My pc didnt know there was something connected.
Did you use the MSM tool before? Because you have to make sure that all drivers are installed.
Yes, I have used it several times but any time I used it, the pc made the sound for device connected. Anyway, I'm gonna search the drivers and install them again just in case.
Your phone was completely dead too?
Edit: the drivers I found are for the case I have an unknown device in device administrator, but windows doesn't recognice no device, so I can't use them.
Hammerhand.17 said:
Yes, I have used it several times but any time I used it, the pc made the sound for device connected. Anyway, I'm gonna search the drivers and install them again just in case.
Your phone was completely dead too?
Edit: the drivers I found are for the case I have an unknown device in device administrator, but windows doesn't recognice no device, so I can't use them.
Click to expand...
Click to collapse
My phone was dead too. But it did something if i hold all 3 keys together for a very long time but i dont remember completly. But i guess you know how a/b devices work, you never flash both slots at the same time so a hard brick by flashing is nearly impossible.
So the drivers wont help until your pc recognice the phone. ANd if you used msm before, the drivers should be installed.
Are you using the original 1+ cable? if yes try a third party cable.
Try switching the usb ports too.
Yes, my only doubt is that I flashed several partitions from a payload (just as I did several times before, to update firmware), but they were from oos open beta 1. Don't know if this flask affects to both slots or just live any other flash.
I've tried all key combinations, with three different cables and in four different ports. I have to be skipping something.
Hammerhand.17 said:
Yes, my only doubt is that I flashed several partitions from a payload (just as I did several times before, to update firmware), but they were from oos open beta 1. Don't know if this flask affects to both slots or just live any other flash.
I've tried all key combinations, with three different cables and in four different ports. I have to be skipping something.
Click to expand...
Click to collapse
hello did you get solution i have same phone in same state what is needed here is opening phone and using testpoint to get edl mode but question is how to locate the testpoint
jroki said:
hello did you get solution i have same phone in same state what is needed here is opening phone and using testpoint to get edl mode but question is how to locate the testpoint
Click to expand...
Click to collapse
No, I didn't. I didn't even know that you could achieve edl mode this way. If you make some progress, please share it.
i have opened phone but still failed to locate the edl testpoint incase i succed will make updates here
jroki said:
i have opened phone but still failed to locate the edl testpoint incase i succed will make updates here
Click to expand...
Click to collapse
Have you tried to use deep flash cable?
If you have a voltmeter that can help you in your search.
You're looking for a pair of points, conspicuously by themselves.
They could be blocked by a connector for something like a camera.
One point should measure 1.8V That is the internal power supply.
One point should measure 0V That is the sensing input pin.
If you have any resistors of say 200-3000 ohm that is a safer thing to jump test points that you're not sure of.
When you jumper the points the 1.8V stays the same and the 0V goes to 1.8V
If all else fails you can try to disable the flash by using a 100-200 ohm resistor to ground on testpoints near the flash memory.
If the ROM bootloader finds it can't even access the flash it will also go to EDL mode.
I believe (but don't know) that the "deep flash" cable support is part of the SBL/XBL (and not the boot ROM) and so it may not work on all models.
I've never got one to work, but that may be my fault.
In any case, if someone has authoritative info on it, I'd love to know.
Related
HI everybody, I have a very big problem with my zuk. Trying to solve a problem about network, I thought to come back to stock via fastboot. But given that I was tired doing so many tries, I wrongly flash a zip file via fastboot instead of use adb, so the phone didn't turn on anymore. I must say first of all that it isn't my first phone, so I'm not a newbie. The real problem is: When I plug Zuk into my Pc( Windows 10) it isn't recognized as qhsusb_bulk ( It could be easy to solve the problem) but as "unknown usb device (Device Descriptor Request Failed)". I try to plug the phone pressing every button like Vol+ and power, Vol- and power but nothing to do. I' m already in Test Mode on Windows 10 and I deleted every Zuk or Qualcomm Drivers. Anyone can help me?
Thank you
Ps: Even If the screen is always off, Is there a way to boot into fastboot mode with hardware keys?
Xluk3 said:
HI everybody, I have a very big problem with my zuk. Trying to solve a problem about network, I thought to come back to stock via fastboot. But given that I was tired doing so many tries, I wrongly flash a zip file via fastboot instead of use adb, so the phone didn't turn on anymore. I must say first of all that it isn't my first phone, so I'm not a newbie. The real problem is: When I plug Zuk into my Pc( Windows 10) it isn't recognized as qhsusb_bulk ( It could be easy to solve the problem) but as "unknown usb device (Device Descriptor Request Failed)". I try to plug the phone pressing every button like Vol+ and power, Vol- and power but nothing to do. I' m already in Test Mode on Windows 10 and I deleted every Zuk or Qualcomm Drivers. Anyone can help me?
Thank you
Ps: Even If the screen is always off, Is there a way to boot into fastboot mode with hardware keys?
Click to expand...
Click to collapse
Not that I know,do you have the stock recovery or twrp?
I have the exact problem with my new zuk z1. Any idea is appreciated. The nice phone seems lost now.
Seems like you'll have to restore your zuk to the zui version again. Do you have qrst and zui version downloaded??
The service port never pops up
I do have the qpst and the zui rom. The main obstacle is that qualcomm service port never pop up.
Setup.zuk said:
I do have the qpst and the zui rom. The main obstacle is that qualcomm service port never pop up.
Click to expand...
Click to collapse
try this:
start QFIL from the QPST folder
Click browse on the programmer path row and select prog_emmc_firehose_8974.mbn from the directory where you unzipped the QPST ZUI ROM
and then click browse on the search path row and select the xml file + the other patch file which comes after it.
When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone,
you may need to select port in the QFIL program and be quick with it, took me a few tries before I got it right so just take out the cable
and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal.
If everything went well then you should have ZUI loaded onto your phone and you are met with Chinese language as default.
On the first screen you are met with, just press the button in the bottom (on screen), then press cogwheel (which is the settings),
scroll down to yet another cogwheel in here which should be below a lock icon, then press second option in here and then the top option
to change language to english incase you cant make out the chinese and you should be good to go
Nikosstamatiou said:
try this:
start QFIL from the QPST folder
Click browse on the programmer path row and select prog_emmc_firehose_8974.mbn from the directory where you unzipped the QPST ZUI ROM
and then click browse on the search path row and select the xml file + the other patch file which comes after it.
When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone,
you may need to select port in the QFIL program and be quick with it, took me a few tries before I got it right so just take out the cable
and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal.
If everything went well then you should have ZUI loaded onto your phone and you are met with Chinese language as default.
On the first screen you are met with, just press the button in the bottom (on screen), then press cogwheel (which is the settings),
scroll down to yet another cogwheel in here which should be below a lock icon, then press second option in here and then the top option
to change language to english incase you cant make out the chinese and you should be good to go
Click to expand...
Click to collapse
So i am having the same problem. The phone is not being recognized by the software. That is the whole problem. Any ideas?
Tarsa said:
So i am having the same problem. The phone is not being recognized by the software. That is the whole problem. Any ideas?
Click to expand...
Click to collapse
Actually, I think the problem is, that it will not reach the fastboot mode, due to the non-stop process of system-updating and boot-loop. I can observe for a very short time the message 'systemupdate will be installed' and then the screen becomes black again. This procedure is repeating every time. I will wait till the battery is empty and see, whether the boot with Volume-+--USB-cable will work.
mikarbach said:
Actually, I think the problem is, that it will not reach the fastboot mode, due to the non-stop process of system-updating and boot-loop. I can observe for a very short time the message 'systemupdate will be installed' and then the screen becomes black again. This procedure is repeating every time. I will wait till the battery is empty and see, whether the boot with Volume-+--USB-cable will work.
Click to expand...
Click to collapse
PLease do update me if you manage to fix it. This is getting very frustrating
I have the same problem, caused after a cyanogenmod update... Did someone fix this??
Another hard bricked Z1 here.
QFIL recognizes the phone (as Qualcomm 9008 etc.). So I am able to click Download, but after a few seconds, it fails with these errors:
Code:
[...]
Sending NOP
NOP: Fail Code: 9
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
in QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
in QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
I've tried many many times, and many different things. Still no luck .
I'd appreciate if anyone could input some new ideas of other stuff to try. Thanks
CarlosAir said:
Another hard bricked Z1 here.
QFIL recognizes the phone (as Qualcomm 9008 etc.). So I am able to click Download, but after a few seconds, it fails with these errors:
Code:
[...]
Sending NOP
NOP: Fail Code: 9
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
in QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
in QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
If tried many many times, and many different things. Still no luck .
I'd appreciate if anyone could input some new ideas of other stuff to try. Thanks
Click to expand...
Click to collapse
No idea, my device is actually dead.
mikarbach said:
No idea, my device is actually dead.
Click to expand...
Click to collapse
Aw .
I don't want to lose hope, but everything I've tried so far has failed. :| , and I don't know what else to try.
CarlosAir said:
Aw .
I don't want to lose hope, but everything I've tried so far has failed. :| , and I don't know what else to try.
Click to expand...
Click to collapse
Try another cable, another USB slot, another pc/laptop
mikarbach said:
No idea, my device is actually dead.
Click to expand...
Click to collapse
try to flash cos 12.1 with qfil.
its there somwhere on 4pda forum(search there).
Sent from my Z1 using XDA-Developers mobile app
So guys if I try to flash unofficial CM 13 do I risk bricking the device for good???
t.h.i said:
try to flash cos 12.1 with qfil.
its there somwhere on 4pda forum(search there).
Sent from my Z1 using XDA-Developers mobile app
Click to expand...
Click to collapse
Of course I have tried this, with two different computers and two different USB cable, both actually working on my N5X. But the point is, that I do not reach the point, that qfil recognizes the phone. Also not with the trick of starting with power-button/USB-cable. It constantly tries to reboot and with adb I get a message 'not authorized' .
---------- Post added at 11:17 AM ---------- Previous post was at 11:05 AM ----------
carlese said:
So guys if I try to flash unofficial CM 13 do I risk bricking the device for good???
Click to expand...
Click to collapse
I think in my case the after the first successful CM13-snapshot-installation was two fold:
1. I have not enabled USB-debugging and do not have had connected it to my computer after the first CM13-installation.
2. Due to some unknown reason the automatically update via CM itself has boot looped.
The second point is not a real problem, I think. I have had a bootloop many times before with other phones, as well as with the Zuk, but I was always able to resolve the problem with adb. I think the first point was the problem, so adb wasn't possible, due to authorization problems. The reason why qfil does not work, I really do not know exactly, but qfil in fact was not able to recognize the phone.
I have the same problem. Totally bricked.
No charge, no PC recognise, nothing.
I tried with QFIL but the PC does not recognise the port.
I don't know what else I can do. Any ideas?
Thanks!
alexisdance said:
I have the same problem. Totally bricked.
No charge, no PC recognise, nothing.
I tried with QFIL but the PC does not recognise the port.
I don't know what else I can do. Any ideas?
Thanks!
Click to expand...
Click to collapse
Sry, no I do not have
Hello!
I have dealt with this sort of problem before and have successfully un-bricked my friend's device. I will be posting a guide to solve this problem soon.
Hang-on!
Hello!
As title says i bricked my Axon :crying:
I followed http://forum.xda-developers.com/showpost.php?p=68738854&postcount=100 (and the german one that linked to this one) but couldnt do the fastboot unlock.
So i couldnt finish this and my phone required a pin number to start android: bootet and started up but wanted a pin code to start/enter system.
Wasnt able to fix that with googling for answers so i went back to edl mode and rewrote my backup boot/recovery images with axon7backup.
Had no errors with that but it wont start now:
After the ZTE Logo the display goes black but it connects as "handset diagnostic interface (DFU) (ComX)" to my computer.
I fiddled around with driver installing etc and forced the HS-USB QDLoader 9008 on it but no luck, axon7backup/root can not connect.
When i did the actual flashing yesterday it never connected with the hold both vol-keys and connect usb way either, always had to reboot into edl via adb.
I cant boot anything else (no twrp/recovery) it just goes to the diagnostic interface mode.
Thanks in advance
you can try to get into adb mode with this:
- power off your device
- hold the vol down key while plugin in the usb-c cable (connected to your pc)
- keep holding
- you should get a white box with FTM factory test mode
- you are free to use adb again - so you can get into edl mode as well....
for pin part that'S normal while unlocking your device encryption gets deleted and you have to abort and factory reset your device in twrp....
Starvirus said:
you can try to get into adb mode with this:
- power off your device
- hold the vol down key while plugin in the usb-c cable (connected to your pc)
- keep holding
- you should get a white box with FTM factory test mode
- you are free to use adb again - so you can get into edl mode as well....
for pin part that'S normal while unlocking your device encryption gets deleted and you have to abort and factory reset your device in twrp....
Click to expand...
Click to collapse
Thanks. I tried it but it wont go to FTM. Only goes to diagnostic com port.
It seems i cant even turn it off. The little red light on the front is on the whole time .
sadly the disadvantage of a built in battery, so you have to wait till the battery is empty and try my instructions then....if it's not realy off it won't work, the mode you are currently in you usually only reach if you switch it on while holding both volume buttons, the edl mode is sadly not reachable with a key combination directly on G models.
adb don't show your device?
Starvirus said:
sadly the disadvantage of a built in battery, so you have to wait till the battery is empty and try my instructions then....if it's not realy off it won't work, the mode you are currently in you usually only reach if you switch it on while holding both volume buttons, the edl mode is sadly not reachable with a key combination directly on G models.
Click to expand...
Click to collapse
Oh ok. I expected ftm to work from vol-down and power-button till restart.
@adb: sadly no connection possible since it goes straight to Comport Connection.
Edit:
Couldnt make that work. It was off and i connected the usb. So it showed me the loading battery picture where i cant do anything. held the vol-down the whole time. But as soon as it had some battery it went straight to comport-connection again
im sorry to say, but ur device is bricked to a degree where you would need ZTEs Flashtool to fix it. Unfortunately we dont have that tool, so you might have to send it in
i have the same exact problem :'(
Have u been able to fix it?? I'm in a situation that i cant even send it to ZTE to fix it :'(
nsabir said:
i have the same exact problem :'(
Have u been able to fix it?? I'm in a situation that i cant even send it to ZTE to fix it :'(
Click to expand...
Click to collapse
Hi,
couldnt fix it myself so i had to send it in.
Unless some tool/rom was released in the last few months to fix it yourself i would guess your device is bricked.
Hi I have almost the same problem, I tried to unlock bootloader and now I don't have the recovery, I can boot and use my mobile but I can't restore it or update it because I don't have the recovery
I try whit axon7tool to restore the recovery but I got a error.
MaxRink said:
im sorry to say, but ur device is bricked to a degree where you would need ZTEs Flashtool to fix it. Unfortunately we dont have that tool, so you might have to send it in
Click to expand...
Click to collapse
Hi, do you have any idea, if there will be such a flashtool to work with DFU mode? I'm thinking that there are a lot of guys have bricked their devices (including me).
((
Hey guys,
Guess today it was my turn ****ing up.
I apparently have completely bricked my Axon 7 after trying to go from LOS 15.1 to stock oreo beta. The only thing I seem to be able to boot to is DFU mode and for some reason, if I press the Power button + Vol Down I will get stuck on the ZTE Logo and my PC will detect my phone through the ADB interface but every time I try doing something it says my device is unauthorized. Is there any way I can authorize the device whilst being completely bricked?
The only other thing I get is the unlocked bootloader warning screen. If I don't press anything the phone will be stuck there, if I select recovery the phone will simply shut down and anything else will result in a reboot. I have also tried a deep flash cable that that only results on the phone being stuck at the unlocked bootloader screen.
I cannot access the bootloader,
I cannot access EDL mode
I can access ADB, but device shows as unauthorized.
I can access DFU mode.
Any suggestions would be appreciated. I have looked at the Hard brick guide that involves taking the phone apart but that's not something I really want to do.
Thanks in advance.
Edit: My phone gets detected by MiFlash but every time I try flashing I get a cannot receive hello packet and object reference not set to an instance of an object.
ZTE axon 7 EDL tool detects it in ADB mode but says ERROR! NO ANSWER FROM PHONE!. Possibly since its not authorized with ADB.
Ouh....DFU? I think this thing is totally bricked.
I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?
Victor13f said:
I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?
Click to expand...
Click to collapse
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !
raystef66 said:
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !
Click to expand...
Click to collapse
Thank you for your help . It's a risk you take when flashing phones.
Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.
stinka318 said:
Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.
Click to expand...
Click to collapse
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!
Victor13f said:
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!
Click to expand...
Click to collapse
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....
stinka318 said:
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....
Click to expand...
Click to collapse
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!
Victor13f said:
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!
Click to expand...
Click to collapse
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable
Choose an username... said:
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable
Click to expand...
Click to collapse
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!
Victor13f said:
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!
Click to expand...
Click to collapse
In that case you can just pretend that the phone got in that state by itself, it's not too morally correct but some people here pulled it off...
twice now i have gotten an axon 7 into this state. while mine have been a2017u models, i dont know that they are different than yours in that regard.
What worked for me the first time was letting the phone completely die. Being unable to boot into anything, it was somewhat a task to actually make it die, so i kept powering it on (which merely made the red led indicator come on). i did this over and over again over the course of a day at work whenever i noticed it had powered off.
eventually, the phone had no response at all. then, i plugged it up to my laptop, and left it, convinced i had killed it. a dialogue popped up after a minute or two on the phone screen saying to charge the phone by plugging it up. i had no access to fastboot or EDL mode prior. once i got that 'plug in to charge' screen, i switched it to the wall charger, and left it to charge a bit (50-60%) from that state, then, i unplugged it again, and somehow, i managed to get edl mode to work by unplugging it and pressing all three buttons and holding them (typical edl boot).
once there, i reflashed via MiFlash an earlier build. i rolled back using MiFlash as far back as i could. in the process, i lost my imei and serial, which i have yet to successfully recover, but i did get out of DFU pergatory. the imei thing seems to be caused by going back to MM which i did on both of my IMEI-less a2017u boards, but im only guessing. my dd axon 7 is the only one of the three boards with imei and serial, so maybe MM is a bad idea. lol.
The first time i recovered from DFU, i did it inadvertently by letting the phone die and then flashing in EDL mode as well. (i left it for a few weeks as i had given up on it.) after it died completely, and i plugged ut up to the computer and had the same experience, I flashed the beta oreo build for a2017 using miflash. the screen had stopped responding. and i ended up doing a RMA. I now know the screen response thing was bc of a faulty EDL file of B15. (happened again to another of my axon, so i retraced my steps and realized it was when i flashed b15 that it died) . the fix if your screen ever stops responding, but isnt physically damaged? re-flash via EDL a different file. it may take a few tries, but eventually a build will work. for me, it was Marshmallow. I still do not know for certain, but that possibly is what killed my IMEI. but hey, it boots and the screen works.
I genuinely hope posting my idiocy in toying with axon 7s has helped someone out there.
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?
OP 8 Pro (Global-US) is horribly MUCKED UP!
I am in need of some high-level assistance, hoping someone here is able to help me.
Here’s what I know: My phone got messed up when I was attempting to install Magisk to android 12 C33. (Not really sure why) I tried you using various tools and methods to fix it. Each time I hit one roadblock or another. Biggest issue was I was never able to boot to EDL mode.
At this stage, no matter what key combo I use, the phone only boots to fastboot mode. Selecting any of the other options has no effect, it simply boots back to fastboot. At the time, that this happened, the bootloader was unlocked and developer options with USB debugging WAS active.
I have tried multiple times to install OnePlus_8_Pro_Global_OxygenOS_11.0.4.4.zip via fastboot, but it always fails with several 'Flashing is not allowed for Critical Partitions” and partition not found, etc
At this stage, I don’t know what to do. I am hoping one of you can help me restore my phone back to factory.
PS - would OnePlus reset/restore it for a fee?
SteveHebe said:
OP 8 Pro (Global-US) is horribly MUCKED UP!
I am in need of some high-level assistance, hoping someone here is able to help me.
Here’s what I know: My phone got messed up when I was attempting to install Magisk to android 12 C33. (Not really sure why) I tried you using various tools and methods to fix it. Each time I hit one roadblock or another. Biggest issue was I was never able to boot to EDL mode.
At this stage, no matter what key combo I use, the phone only boots to fastboot mode. Selecting any of the other options has no effect, it simply boots back to fastboot. At the time, that this happened, the bootloader was unlocked and developer options with USB debugging WAS active.
I have tried multiple times to install OnePlus_8_Pro_Global_OxygenOS_11.0.4.4.zip via fastboot, but it always fails with several 'Flashing is not allowed for Critical Partitions” and partition not found, etc
At this stage, I don’t know what to do. I am hoping one of you can help me restore my phone back to factory.
PS - would OnePlus reset/restore it for a fee?
Click to expand...
Click to collapse
Try firing up MSM and click the start button before connecting your phone. You should have at least 1 COM port listed with a N/A status. Now plug your phone in to the computer and let it boot to fastboot. Now hold down VUP,VDO & Power all at the same time until MSM starts the install. You should be good to go, if you get a good MSM install.
I tried what you suggested with no success. I am using the instantnoodlep_15_O.34_210201 MSM. Any thoughts?
HolyHog said:
Try firing up MSM and click the start button before connecting your phone. You should have at least 1 COM port listed with a N/A status. Now plug your phone in to the computer and let it boot to fastboot. Now hold down VUP,VDO & Power all at the same time until MSM starts the install. You should be good to go, if you get a good MSM install.
Click to expand...
Click to collapse
I tried what you suggested with no success. I am using the instantnoodlep_15_O.34_210201 MSM. Any thoughts?
SteveHebe said:
I tried what you suggested with no success. I am using the instantnoodlep_15_O.34_210201 MSM. Any thoughts?
Click to expand...
Click to collapse
DId you install all the drivers correctly? DId you try another cable? Did you try another usb port?
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
xtcislove said:
DId you install all the drivers correctly? DId you try another cable? Did you try another usb port?
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
I have current drivers, tried different machines, different ports and different cables.
SteveHebe said:
I have current drivers, tried different machines, different ports and different cables.
Click to expand...
Click to collapse
Is your phone regognized in device manager?
No, it is not
SteveHebe said:
No, it is not
Click to expand...
Click to collapse
Your phone boots ot fastboot and your pc does not regonize it? You need to make sure to install the drivers correctly imo.
Please read this sections carefully https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/