Database Users

Heavy Hard Brick Zuk Z1 international Version

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!

Recovery is not Seandroid Enforcing Odin isn’t detecting my phone, any suggestions?

Recovery is not Seandroid Enforcing Odin isn’t detecting my phone, any suggestions?
I successfully rooted my phone and was trying to install the exposed framework and i guess downloaded the wrong one. When i flashed it i ended up getting into boot loop. I am on N910F with the 2 Network.
I have tried factory resetting with the caches but to no avail. The only other option i found was Odin, the problem is Odin is not detecting my phone when in recovery mode but seems to have no problem coming blue when starting up giving the 3 logo startup which just goes when it start looping again. I have tried 2 computers, a different cable although old and all my USB ports and the same thing keeps happening. I have already reinstalled Samsung USB Drivers times. I am wondering if they are any others.
Please Help

Note44 said:
I successfully rooted my phone and was trying to install the exposed framework and i guess downloaded the wrong one. When i flashed it i ended up getting into boot loop. I am on N910F with the 2 Network.
I have tried factory resetting with the caches but to no avail. The only other option i found was Odin, the problem is Odin is not detecting my phone when in recovery mode but seems to have no problem coming blue when starting up giving the 3 logo startup which just goes when it start looping again. I have tried 2 computers, a different cable although old and all my USB ports and the same thing keeps happening. I have already reinstalled Samsung USB Drivers times. I am wondering if they are any others.
Please Help
Click to expand...
Click to collapse
are u sure ur phones usb port is working? did u connected another phone to the pc?

Note44 said:
I successfully rooted my phone and was trying to install the exposed framework and i guess downloaded the wrong one. When i flashed it i ended up getting into boot loop. I am on N910F with the 2 Network.
I have tried factory resetting with the caches but to no avail. The only other option i found was Odin, the problem is Odin is not detecting my phone when in recovery mode but seems to have no problem coming blue when starting up giving the 3 logo startup which just goes when it start looping again. I have tried 2 computers, a different cable although old and all my USB ports and the same thing keeps happening. I have already reinstalled Samsung USB Drivers times. I am wondering if they are any others.
Please Help
Click to expand...
Click to collapse
Are you connecting phone to Odin in Recovery mode or you mean to say download mode. You should put phone in download mode For connecting to Odin.

Ram121 said:
Are you connecting phone to Odin in Recovery mode or you mean to say download mode. You should put phone in download mode For connecting to Odin.
Click to expand...
Click to collapse
Ram121 said:
Are you connecting phone to Odin in Recovery mode or you mean to say download mode. You should put phone in download mode For connecting to Odin.
Click to expand...
Click to collapse
Thank you,
I just figured that out from some genius from Reddit Not 4 Thread. I guess the guy in the YouTube tutorial accidentally said "hold volume up" and so did everyone else I happened to come across which ended up wasting me a lot of time.
That was so lucky, because I really would have done some crazy stuff I didn't know about.
Thank you so much for taking the time to reply. Maybe I should contact the guy from YouTube to add an annotation or something.

shahram Ali said:
are u sure ur phones usb port is working? did u connected another phone to the pc?
Click to expand...
Click to collapse
Yes it was, the problem was I was given a bad tutorial and told to hold "volume up" to go into TWRP recovery instead of "Volume Down" into downloader.
Everything is working great now and my phone is working again.
Thank you for taking the time to reply. It's genuine people like you that make the internet great!

Note44 said:
Yes it was, the problem was I was given a bad tutorial and told to hold "volume up" to go into TWRP recovery instead of "Volume Down" into downloader.
Everything is working great now and my phone is working again.
Thank you for taking the time to reply. It's genuine people like you that make the internet great!
Click to expand...
Click to collapse
congratulations bro im happy cause ur phone fixed :victory:

VNS-L21 Stucked at Device is booting now.No access to ADB,Recovery,FastBoot,erecovery

Hello everyone! I have read almost a hundred threads and discussions about unbricking P9 Lite and none of them was my case. I have unlocked my bootloader and i can tell that by seeing the warning from huawei which says my device is not safe.
Okay, but the case is phone is stucked at Device is booting now and i dont have nothing to pick from because people can choose wrether to press power and continue to boot or hold volume up to go to recovery. But i can`t get anywhere because the phone just go straight to Device is booting now. I can`t get to fastboot, adb, erecovery, recovery or any kind of option instead of seeing Huawei logo when powering up and Device is booting now right after it. No sound from laptop when i connect usb and holding Volume down + Power. Nothing.
Any help would be really appreciated.

have you tried turning the phone on WHILE pressing those keys? volume up + power for recovery, or power down + power for fastboot?

SALVO9 said:
have you tried turning the phone on WHILE pressing those keys? volume up + power for recovery, or power down + power for fastboot?
Click to expand...
Click to collapse
yes, multiple times. that was the first thing to try. Anything else u could think of? :good:

What have you done?
So why is it bricked?

Schlengge said:
What have you done?
So why is it bricked?
Click to expand...
Click to collapse
Well, i updated to Nougat B336. It went all fine but it was slow. So i decided to downgrade to MM using oem-info after that flashing middle package and then MM. But in order to install these with Revolution Recovery you have to change data partition to f2fs than back to ext4 and then format data in order to be able to mount data. And then phone got bricked without any idea why. And then i tried numerous firmwares, extracting update packages flashing boot,cust and system. None of them made it. I had access to fastboot, recovery and emui recovery but recovies from huawei did nothing but to stop at 5% with package errors. Even ones from Huawei official website made exactly for VNS-L21 Dual Sim. The last thing i decided was to flash TWRP Meticulus because i thought partitioning will be better than Revolution but when i flash it i lost every access to this phone. No fastboot, adb, recovery, erecovery even dload\update.app on SD Card doesnt work. :good:

Drained battery in order to somehow make it to fastboot. No success. Even then when holding Vol+ + Vol- and Power i got to No battery symbol. When holding down Vol- + Power i got to Huawei logo and then straight to Device is booting now. If i just leave it as it is it goes to logo than Device is booting now... and nothing happens of course. Huawei got one of the worst support pages after Lenovo maybe. They are just useless

goretsov said:
Drained battery in order to somehow make it to fastboot. No success. Even then when holding Vol+ + Vol- and Power i got to No battery symbol. When holding down Vol- + Power i got to Huawei logo and then straight to Device is booting now. If i just leave it as it is it goes to logo than Device is booting now... and nothing happens of course. Huawei got one of the worst support pages after Lenovo maybe. They are just useless
Click to expand...
Click to collapse
When you connect the phone to the pc HiSuite launches?

Chisetdel31260 said:
When you connect the phone to the pc HiSuite launches?
Click to expand...
Click to collapse
Well, previously i always got in fastboot when i`m connected to HiSuite and click on Restore device (Not supported model for restore! Blaaa) but now i can`t connect even when i`m there. Can someone send me only the usb drivers for the VNS-L21 because i don`t have trust to this HiSuite thing? :highfive:

C`mon guys give us some ideas. I disassembled this little beast take off battery put usb in my laptop and then boom same thing. Huawei logo straight to Device is booting now...

You have to install hisuite because it needs the right drivers to run. Moreover it is a good indicator to know if there is a link between them.

Chisetdel31260 said:
You have to install hisuite because it needs the right drivers to run. Moreover it is a good indicator to know if there is a link between them.
Click to expand...
Click to collapse
Yes, i do know it and yes i do have it installed. This was the first thing i did when i bought this phone. I reinstalled it and it does not make any change. But i think there`s something not exactly right with the connection between the app and the phone because there`s no sound when plugging the phone. That`s a pretty solid clue that something is not right.

goretsov said:
Well, i updated to Nougat B336. It went all fine but it was slow. So i decided to downgrade to MM using oem-info after that flashing middle package and then MM. But in order to install these with Revolution Recovery you have to change data partition to f2fs than back to ext4 and then format data in order to be able to mount data. And then phone got bricked without any idea why. And then i tried numerous firmwares, extracting update packages flashing boot,cust and system. None of them made it. I had access to fastboot, recovery and emui recovery but recovies from huawei did nothing but to stop at 5% with package errors. Even ones from Huawei official website made exactly for VNS-L21 Dual Sim. The last thing i decided was to flash TWRP Meticulus because i thought partitioning will be better than Revolution but when i flash it i lost every access to this phone. No fastboot, adb, recovery, erecovery even dload\update.app on SD Card doesnt work. :good:
Click to expand...
Click to collapse
you could've flashed oeminfo in revolution recovery and then use the update.app of mm, no need to format the data partition.
have you tried booting to fastboot while connected with usb? and if you check device manager while connected, can you find your device in there?

mjz2cool said:
you could've flashed oeminfo in revolution recovery and then use the update.app of mm, no need to format the data partition.
have you tried booting to fastboot while connected with usb? and if you check device manager while connected, can you find your device in there?
Click to expand...
Click to collapse
Yes, i tried it as i said in the previous replies, no i can`t see it in device manager because Windows doesn`t recognise it when i plugged it to the usb ports. I say doesn`t recognise because there is no sound when the phone is being connected and i hold whichever combinations there are for VNS-L21. Thank you for your suggestion if you have any ideas i will appreciate them :highfive:

goretsov said:
Yes, i tried it as i said in the previous replies, no i can`t see it in device manager because Windows doesn`t recognise it when i plugged it to the usb ports. I say doesn`t recognise because there is no sound when the phone is being connected and i hold whichever combinations there are for VNS-L21. Thank you for your suggestion if you have any ideas i will appreciate them :highfive:
Click to expand...
Click to collapse
As i said i`ve read a lot of posts and comments of random users of P9 Lite and all of them doesn`t work for me. We need something out of the box, because i think this is not something you see every day. And it will be usefull to everyone who owns P9 Lite. :good:

goretsov said:
Yes, i tried it as i said in the previous replies, no i can`t see it in device manager because Windows doesn`t recognise it when i plugged it to the usb ports. I say doesn`t recognise because there is no sound when the phone is being connected and i hold whichever combinations there are for VNS-L21. Thank you for your suggestion if you have any ideas i will appreciate them :highfive:
Click to expand...
Click to collapse
did you check device manager itself? no sound playing doesn't mean the device isn't showing up in device manager, it is possible it shows up but isn't recognized. if device manager doesn't list it i haven't said anything

Used another pc

Chisetdel31260 said:
Used another pc
Click to expand...
Click to collapse
I`ll try another PC thank you for that advice. Well last time i checked device manager and nothing showed up even after scaning for changes nothing shows up. Interesting part is even without battery when usb is plugged in there`s no connection between PC and phone.

Can be battery and empty.
Connect it to a wall socket for 2 hours.

Chisetdel31260 said:
Can be battery and empty.
Connect it to a wall socket for 2 hours.
Click to expand...
Click to collapse
Nope i tried it. Doesn`t work. Another pc doesn`t recognize it too. Same thing. Can`t get into anything just logo and then Device is booting now. I`m starting to lose hope.

goretsov said:
Nope i tried it. Doesn`t work. Another pc doesn`t recognize it too. Same thing. Can`t get into anything just logo and then Device is booting now. I`m starting to lose hope.
Click to expand...
Click to collapse
I hope not to say stupidity.
So it makes see huawei logo. So it boots.
I think you deleted something at system.img.
So you have to take your time and make it go to fastboot and install recoverynougatb9, flash system.img b336, make it start again.

[SOLVED] A2017G Hard brick, Unauthroized ADB and DFU Only.

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.

Has anyone succeeded in repairing a bricked Poco M3?

My M3 was working perfectly. I put it to restart and then it didn't turn on anymore. It is now only recognized as "Qualcomm HS-USB QDLoader 9008" on Windows. I opened the phone and with some magical combination (remove/connect flat cables from the battery and display, connect the USB cable, press volume keys and short the test points) it started in fastboot. So I was able to flash the "fastboot ROM". Unfortunately, on the next boot it still does not turn on normally. Has anyone succeeded in repairing the Poco M3? In Mi Flash is requested an authenticated account to flash through it, is it worth paying someone to provide the account? Does anyone have the contact of someone who makes cheap? Any help is welcome, thank you!

me too

waiting, someone pls

LeandroFarias said:
waiting, someone pls
Click to expand...
Click to collapse
I kind of managed to get my Poco M3 to start on Android (but it's not fully fixed).

That is the points

vinod3362 said:
That is the points
Click to expand...
Click to collapse
What?

me too. after i reboot my poco m3. it came to black and wont boot up. i google everything, the only need to flash is to modified the firehose. badly needed.

KaMyKaSii said:
My M3 was working perfectly. I put it to restart and then it didn't turn on anymore. It is now only recognized as "Qualcomm HS-USB QDLoader 9008" on Windows. I opened the phone and with some magical combination (remove/connect flat cables from the battery and display, connect the USB cable, press volume keys and short the test points) it started in fastboot. So I was able to flash the "fastboot ROM". Unfortunately, on the next boot it still does not turn on normally. Has anyone succeeded in repairing the Poco M3? In Mi Flash is requested an authenticated account to flash through it, is it worth paying someone to provide the account? Does anyone have the contact of someone who makes cheap? Any help is welcome, thank you!
Click to expand...
Click to collapse
how do you get into fastboot?? i tried mine but it wont boot in fastboot. i'm stuck in QDLoader.

did someone successfully recover their bricked poco m3 ?

gasleak08 said:
did someone successfully recover their bricked poco m3 ?
Click to expand...
Click to collapse
nothing yet. we need firehose to bypass miflash authentication. or drain the battery then press vol down + power for 10secs.

KaMyKaSii said:
I kind of managed to get my Poco M3 to start on Android (but it's not fully fixed). Are you Brazilian too? Call me on telegram
Matheus
You can contact @MatheusCoelho1998 right away.
t.me
Click to expand...
Click to collapse
can u tell me how?mine too?

my phone has bricked with UBL condition and i flash whole partition with twrp and magisk to solve the heating problem now its alive again

I just wait till the battery totally discharge and then plug in the charger,sofar been through this problem for 2x,the first one for 2 days and 5 days for later because the battery was full.
This happens when Im restarting the device and now even there is a new update,Im still scare to update my device to the latest firmware incase it wont boot again.
Should I try to update or nah,guys?

Minoda86 said:
I just wait till the battery totally discharge and then plug in the charger,sofar been through this problem for 2x,the first one for 2 days and 5 days for later because the battery was full.
This happens when Im restarting the device and now even there is a new update,Im still scare to update my device to the latest firmware incase it wont boot again.
Should I try to update or nah,guys?
Click to expand...
Click to collapse
do not try to update it... i tried 3 times their own ota update broke the phone os which makes it unable to go to recovery or fastboot. i will try and see if i can update firmware and fix itself

yankee77 said:
do not try to update it... i tried 3 times their own ota update broke the phone os which makes it unable to go to recovery or fastboot. i will try and see if i can update firmware and fix itself
Click to expand...
Click to collapse
I did update it and now my phone wont boot at all,after the battery hits 1%,it just wont do anything and its been 2 weeks,pc does detect it as qualcom loader but flashing without auth wont work,Im just waiting for firehose file for this stupid phone.People with auth asking for $30 for fixing it but without guarantee that it will work,what a joke.
So did you fix your phone?

yankee77 said:
do not try to update it... i tried 3 times their own ota update broke the phone os which makes it unable to go to recovery or fastboot. i will try and see if i can update firmware and fix itself
Click to expand...
Click to collapse
Yeahhh,my phone finally boot up!
But sadly the latest update failed to install.Guess I should just wait until someone patch the firehose file and try not to update until then.Fingercross!

i fixed the deadboot issue. but it wont fix the restart deadboot. try to flash every region and version firmware both recovery and fastboot. the problem still there.

vinzikidz said:
i fixed the deadboot issue. but it wont fix the restart deadboot. try to flash every region and version firmware both recovery and fastboot. the problem still there.
Click to expand...
Click to collapse
how did u fix deadboot can you elaborate? how did you flash from edl ?

gasleak08 said:
how did u fix deadboot can you elaborate? how did you flash from edl ?
Click to expand...
Click to collapse
sorry, there's is no tutorial for this and it has a quite process. you just need to throttle the proc temperature of your phone board using hot blower or any device you have. while your phone is in high temp. both pin board and battery is in unplug hold vol down then put back the board pin and battery pin at the same time. it will vibrate and fastboot will be fine.

Guys this is my procedure to turn on the phone:
I can make it turn on Android after messing with the battery and sub-board cables but this is just a workahound, trying to turn it on normally through the power button always makes it turn on in edl mode
But opening the device voids the warranty, so anyone who has access to a repair center is better off asking for the warranty
What to do:
1. Disconnect the battery cable and the secondary board cable.
2. Connect charger.
3. Hold the power button.
4. Connect the secondary board cable and quickly connect the battery cable.
5. Release the power button when the device vibrates.
It doesn't always work the first time, you may need several tries to get it
VID_20210514_152510.mp4
drive.google.com