Database Users

[Q] Help! Lumia 520 dead during restoring from WP10 preview

So I intstalled the WP10 preview which includes support for the 520, but the settings app didn't work and I couldn't reset the device so I used the Windows Phone Recovery Tool to revert to 8.1. However, as the firmware was about to install, the device went into flash mode (as it does while installing a firmware) and an error dialgue opened on my laptop saying that there was an error. After that my phone's screen went black and its not vibrating or powering on even when connected to a power source. I doubt that it is restorable, but any help would be much appreciated
Thank you guys for letting me know about the link I'm posting it in the OP so that everyone having this issue can upvote on that thread.
Link: https://social.technet.microsoft.co...e-recovery-possible?forum=WinPreview2015Phone

theevilpotato said:
So I intstalled the WP10 preview which includes support for the 520, but the settings app didn't work and I couldn't reset the device so I used the Windows Phone Recovery Tool to revert to 8.1. However, as the firmware was about to install, the device went into flash mode (as it does while installing a firmware) and an error dialgue opened on my laptop saying that there was an error. After that my phone's screen went black and its not vibrating or powering on even when connected to a power source. I doubt that it is restorable, but any help would be much appreciated.
Click to expand...
Click to collapse
I've just got the exact same error and I've spent the last hours trying everything possible and every tutorial to make it work. I'm afraid it's completely bricked. It's not responding to anything, when plugged into the pc it shows up as "QHSUSB_DLOAD" which is usually a very bad sign, and every software recovery or phone recovery tool I've tried from MS and Nokia either don't detect it or say it's not supported.
It's dead.

520? :/ Same here. Time to get a new phone for school, I guess.

Yes, a 520 as well.

Just a heads up, if you give the windows phone subreddit a quick read you'll notice we are not the only people to have this issue. Apparently several other people trying to roll back their phone have it completely bricked and in the QHSUSB_DLOAD situation.
I don't think MS can do anything about it, since the boot crapped out you either need to buy the tools or get it repaired by someone having them, but at least it proves there is some kind of problem with rolling back from the preview.

angstdasein said:
I've just got the exact same error and I've spent the last hours trying everything possible and every tutorial to make it work. I'm afraid it's completely bricked. It's not responding to anything, when plugged into the pc it shows up as "QHSUSB_DLOAD" which is usually a very bad sign, and every software recovery or phone recovery tool I've tried from MS and Nokia either don't detect it or say it's not supported.
It's dead.
Click to expand...
Click to collapse
same here

After a bit of reading more and more people are reporting this, so please put your own experience on this technet thread, it's a good idea to centralize reports where Microsoft can see it.
I can't link it here (don't have the permission to post links yet) but it's the first result by typing "Lumia 620 bricked during rollback procedure: recovery possible?" in google.

NL525 w/ red screen here.
feherneoh, pls make tutor!

feherneoh said:
Here it is:
...
Click to expand...
Click to collapse
Praise the Lord feherneoh!
Greatest thanx to ya!

Same error here, black screen and phone do nothing.
Tried with Thor2 but didn't work.

azogh said:
Same error here, black screen and phone do nothing.
Tried with Thor2 but didn't work.
Click to expand...
Click to collapse
Be sure using good cable. Try few times (i did 3)

[QRCODE][/QRCODE]The same problem with L520. There is already post on Technet regarding this problem
You can search Google by typing in: QHSUSB_DLOAD technet
Please upvote, then we would have some respond from Microsoft, maybe alternative driver, tool or something...

My Nokia does not turn on
The same problem! My Nokia does not turn on. I've tried everything! Any solution?

rickmaran said:
The same problem! My Nokia does not turn on. I've tried everything! Any solution?
Click to expand...
Click to collapse
I don't think there is a solution yet. Just keep and eye on this and hope for the best: https://social.technet.microsoft.co...e-recovery-possible?forum=WinPreview2015Phone

Have you anyone has try using Lumia Recovery Tool ?
1. Download ffu saperatly. (8.1 GDR1)
2. Install Lumia Software Recovery Tool.
3. Launch recovery tool.
4. Remove battery, usb, device.
5. Select my phone doesn't respond in recovery tool.
6. Insert battery, usb, plug it to pc.
7. A- Press and hold volume down.
B- Press and hold Power + volume down
8. Flash it.
Hope this will work.

feherneoh said:
Here it is:
1: Find your Recovery Tool folder on your harddisk. Mine is "C:\Program Files (x86)\Microsoft Care Suite\Windows Phone Recovery Tool"
There should be a file called thor2.exe there.
2: Open an administrator command prompt here
3: Find the ROM Recovery Tool downloaded. Should be in "C:\ProgramData\Microsoft\Packages\Products"
You will need the FFU file for your device.
Mine is "C:\ProgramData\Microsoft\Packages\Products\rm-914\RM914_3058.50000.1425.0005_RETAIL_eu_hungary_429_05_443088_prd_signed.ffu"
4: To flash your device with THOR2, enter this to commandline:
Code:
thor2 -mode uefiflash -ffufile "C:\ProgramData\Microsoft\Packages\Products\rm-914\RM914_3058.50000.1425.0005_RETAIL_eu_hungary_429_05_443088_prd_signed.ffu"
Replace filename with your own
5: After flashing completes, reboot your phone by entering this:
Code:
thor2 -mode rnd -bootnormalmode
Click to expand...
Click to collapse
It says this error:
THOR2 1.8.2.14 exited with error code 393220 <0x60004>
Click to expand...
Click to collapse

zuchit said:
It says this error:
Click to expand...
Click to collapse
Same case

Same problem with DLOAD
The solution seems to do a JTAG... Bad news for normal people ::crying:

Bricked Nokia Lumia
Actually, the red screen means that the phone went into its UEFI MODE.
In UEFI MODE your phone could be restored as normal by a HARD RESET (see key combo).
If you have a hard luck, your phone will automatically start in Flashing Mode (IMO(0x0000001)) which only works on the downloading procedure when on Rolling back.
The RollBack program has to put your phone in Flashing Mode in order to gain access to it's microchip.
Well the app itself knows what to do, but something failed.
In this point, you disconnected the phone and tried all you've known to power it on. Meanwhile the app deleted it's cache file, it no longer knows why your phone is in that state and your PC will get it as QHSUSB_DLOAD which is a Side_Load driver for Qualcomm Enabled Phones.
At this point, RIFF JTAG is the only solution as your BOOTLOADER is dead.
Good thing? It could be fixed by any GSM Service and the price could be small.
DO NOT try any Nokia Care / Refurbish / Restore app. All of them are created to work with a phone that has it's bootloader working.
None of them will cooperate to reflash it.
Even if you manage to reflash the OS, you don't have a BIOS / BootLoader....
Hopefully, Microsoft will create a tool to fix this as it only occurs when Rolling Back from Windows 10 Tech. Prev. and 8.1 to 8.
But until that, your phone is dead.
Source of info: I'm working as an G.S.M. RepairMan.

feherneoh said:
Maybe some error message before this?
Click to expand...
Click to collapse
at the moment, i get this error when i cmd thor right after connecting phone to usb. (screenshot 1)
i58.tinypic. com/2qnz51d.jpg
Click to expand...
Click to collapse
these is what it says when i try cmd thor after red screen with Nokia logo appers.. (screenhot 2)
i61.tinypic. com/jkftq8.jpg
Click to expand...
Click to collapse

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!

Hard brick SM-N910F

Tried installing custom recovery didn't work out like I had hoped now im stuck with a phone that isn't detected by odin or kies but by MiFlash
Please tell me there is something I can do to fix it or get it to some sort of working order..? Is there a jtag tool or usb jig I can use?
Update - I found out the phone was still under warranty so I sent it away to be repaired. It was repaired and I now have a working phone !

ylmcc said:
Tried installing custom recovery didn't work out like I had hoped now im stuck with a phone that isn't detected by odin or kies but by MiFlash
Please tell me there is something I can do to fix it or get it to some sort of working order..? Is there a jtag tool or usb jig I can use?
Click to expand...
Click to collapse
What have you done to reach that state? I know that you're desperate but you must give some details if you want help.

It was given to me with 5.1.1 installed however it failed mid process and while on 5.1.1 it kept freezing and acting weird such as boot with weird errors and they only appeared after it was updated, I decided to root it with odin and it never fully rebooted after the was root applied. I finally got it to boot to stock and rooted and decided to install a custom recovery which was twrp while selecting the recovery it said if its a wrong location it will brick, with this in mind I checked the model with the one on their site and it seemed to make sense and applied it.
This caused the original problem which made it boot straight to download mode with it saying it could not normal boot. I then googled the problem and one said the pit was corrupted and downloaded the correct file. I then applied this through odin with stock firmware and it refuse to flash. At the time I was thinking a restart on the device would help, but it resulted in not booting at all and not being detected....
It does not light up or make a vibration when its connected or powered on if there is any solution it would be great...

Can anyone help or point in the right direction?

Hard brick SM-910F
Hello! If this is the good recovery for the N910F he would have from start.
Try to boot via the recovery flight up + home + power.
If you TWRP flash a custom in a first time rom

[email protected] said:
Hello! If this is the good recovery for the N910F he would have from start.
Try to boot via the recovery flight up + home + power.
If you TWRP flash a custom in a first time rom
Click to expand...
Click to collapse
Nothing however the pc did detect a new driver called qualcomm hs-usb qdloader 9008

ylmcc said:
Nothing however the pc did detect a new driver called qualcomm hs-usb qdloader 9008
Click to expand...
Click to collapse
qualcomm emergency download mode. is it called.

Tunestwo said:
qualcomm emergency download mode. is it called.
Click to expand...
Click to collapse
Anything I can do to get some sort of os on the phone now?

in this case via Odin tries to reinstall the tar of the official rom N910F .

ylmcc said:
Anything I can do to get some sort of os on the phone now?
Click to expand...
Click to collapse
Can you tell us if you can get on recovery screen, either TRWP or stock, or download mode.

You could try installing these drivers:
https://www.androidfilehost.com/?fid=24499762636000789
Reboot just in case and try to connect your device again.
(In download mode, with the key combination)

mangui said:
Can you tell us if you can get on recovery screen, either TRWP or stock, or download mode.
Click to expand...
Click to collapse
The phone does not display or respond when the keys are pressed, just a black screen..
Battlehero said:
You could try installing these drivers:
https://www.androidfilehost.com/?fid=24499762636000789
Reboot just in case and try to connect your device again.
(In download mode, with the key combination)
Click to expand...
Click to collapse
Chrome detected a virus in the rar

ylmcc said:
The phone does not display or respond when the keys are pressed, just a black screen..
Chrome detected a virus in the rar
Click to expand...
Click to collapse
Really? I just scanned it with VirusTotal and it is clean.
Virus Total Results
32Bit.exe scan results
64Bit.exe scan results

Battlehero said:
Really? I just scanned it with VirusTotal and it is clean.
Virus Total Results
32Bit.exe scan results
64Bit.exe scan results
Click to expand...
Click to collapse
I'll download it again but windows defender detected it too.
Edit - Yep did it again, here is a link to a photo of what I get but from virus total I don't get why its being flagged perhaps false positive ??

Update
Found a jtag service that is cheap will update once I get it back...

sm-n910f
I got a brick note 4 and i want to fix it
I search over the internet for this solution and found a method
Sd card repair boot but it did not work at all
I need help
thank you in advance

need help unbricking ny nokia 6

I have a TA-1033 version and a deep flash engerneering cable but im stuck of how to unbrick, my device is detected as QDLoader 9008, also if i try to flash using NOST i get "polling USB device" then a "DEVICE_NOT_CONFIGURE" its an 0x4000 error
if anyone can help me out that would be great!
Sent from my AGS_W09

I have same problem. I don't know what i do, but seems to when i charge my phone over 80 %.
Then i get it download mode and i change edl cable to regular usb cable and then fastboot reconise my phone and i can flash it succesfull.

DoggyStar said:
I have same problem. I don't know what i do, but seems to when i charge my phone over 80 %.
Then i get it download mode and i change edl cable to regular usb cable and then fastboot reconise my phone and i can flash it succesfull.
Click to expand...
Click to collapse
Its completely dead, only detected as QHSUSB BULK and like i said i got one of those deep flash cables from shenzen

When you but it on, can you see android text or just "you phone is unlocked text"?
My phone only shows that unlock text, but after I use edl cable i can get android text showing up.

DoggyStar said:
When you but it on, can you see android text or just "you phone is unlocked text"?
My phone only shows that unlock text, but after I use edl cable i can get android text showing up.
Click to expand...
Click to collapse
No mine just doesnt vibrate or anything

And you have full battery?

DoggyStar said:
And you have full battery?
Click to expand...
Click to collapse
I dont know because its dead as in it wont show any signs of life

Yes yes, but put it ac charger for 2-3 hours and see if you then see something or can you then get it fastboot mode.
My phone has low battery but when I charge it, fastboot start working magically.

DoggyStar said:
Yes yes, but put it ac charger for 2-3 hours and see if you then see something or can you then get it fastboot mode.
My phone has low battery but when I charge it, fastboot start working magically.
Click to expand...
Click to collapse
I modified my aboot.img because i thought i could downgrade but that killed my device

mattwhite7102 said:
I modified my aboot.img because i thought i could downgrade but that killed my device
Click to expand...
Click to collapse
Does qpst tool worked for you?

Emmykay223 said:
Does qpst tool worked for you?
Click to expand...
Click to collapse
Nope, i dont have the files for QPST, but i do have the qfil files and one of those deep flash cables, if you can get my phone fixed i will respect you forever!

mattwhite7102 said:
Nope, i dont have the files for QPST, but i do have the qfil files and one of those deep flash cables, if you can get my phone fixed i will respect you forever!
Click to expand...
Click to collapse
No no i don't want that , if i could help you surely i will .. download qpst tool and Qualcomm drivers on your pc or laptop , if you did all the things and nothing happened yet, so why you don't try this too? We never know which things could give us better results. Hope for the best ??
https://www.qpstflash.com
Download qpst from here

Emmykay223 said:
No no i don't want that , if i could help you surely i will .. download qpst tool and Qualcomm drivers on your pc or laptop , if you did all the things and nothing happened yet, so why you don't try this too? We never know which things could give us better results. Hope for the best ??
https://www.qpstflash.com
Download qpst from here
Click to expand...
Click to collapse
Well i downloaded the 2.7.453 of qpst and flashing with qfil gives me SAHARA_NAK_MEMORY_DEBUG_NOT_SUPPORTED though whats strange is different versions of qfil gives me different errors...

mattwhite7102 said:
Well i downloaded the 2.7.453 of qpst and flashing with qfil gives me SAHARA_NAK_MEMORY_DEBUG_NOT_SUPPORTED though whats strange is different versions of qfil gives me different errors...
Click to expand...
Click to collapse
Does it able to be detected by qpst.
And did you install Qualcomm drivers?
Just look at this .
Hope all of your problems would clear

Emmykay223 said:
Does it able to be detected by qpst.
And did you install Qualcomm drivers?
Just look at this .
Hope all of your problems would clear
Click to expand...
Click to collapse
It does get detected by qpst, might be a driver issue

Emmykay223 said:
Does it able to be detected by qpst.
And did you install Qualcomm drivers?
Just look at this .
Hope all of your problems would clear
Click to expand...
Click to collapse
Nope tried it but coming up with "unable to download flash programmer with sahara protocol"

mattwhite7102 said:
Nope tried it but coming up with "unable to download flash programmer with sahara protocol"
Click to expand...
Click to collapse
Download another android flash zip files from here, 8.0 or 9.0 directly hope it would work

Emmykay223 said:
Download another android flash zip files from here, 8.0 or 9.0 directly hope it would work
Click to expand...
Click to collapse
Can you link me for the TA-1033? its gotta be qfil because my phone doesnt show any signs of life!

mattwhite7102 said:
Can you link me for the TA-1033? its gotta be qfil because my phone doesnt show any signs of life!
Click to expand...
Click to collapse
https://www.google.com/amp/s/forum....-6/help/nokia-6-ota-update-ddls-t3721424/amp/

Emmykay223 said:
https://www.google.com/amp/s/forum....-6/help/nokia-6-ota-update-ddls-t3721424/amp/
Click to expand...
Click to collapse
I cant install these because my phone gets detcted as QHSUSB BULK

Hardbricked to Qualcomm USB 9008

Really hoping someone can help me out here. I have a Nexus 6P, Non-BLOD. Yesterday, after clean flashing the latest version of EvoX, while setting some things up, device randomly crashed. No Shut down animation or anything. Just black screen. Tried turning it on via Power Button and then Power And Volume Buttons but nothing works. Connected it to PC and see it's Detected as Qualcomm USB Bulk (9008) in Coms and Ports. Did some research and found out I have to flash via QFIL. And this is where I am stuck. I tried several versions, but it doesn't flash/gives Shara error. I tried reinstalling driver. I also read a guide here. But the Firmware link is dead and it says to flash via MiFlash, something I can't even try since the Link in the OP is dead. I tried some different versions of QFIL but all of them give a Sahara Communication error. Now I'm pretty much at a loss on what to do. I'd really like to fix my 6P. And I would appreciate anyone taking the time to point me in the right direction, or help me fix it. Thanks in Advance.

DarthVader said:
Really hoping someone can help me out here. I have a Nexus 6P, Non-BLOD. Yesterday, after clean flashing the latest version of EvoX, while setting some things up, device randomly crashed. No Shut down animation or anything. Just black screen. Tried turning it on via Power Button and then Power And Volume Buttons but nothing works. Connected it to PC and see it's Detected as Qualcomm USB Bulk (9008) in Coms and Ports. Did some research and found out I have to flash via QFIL. And this is where I am stuck. I tried several versions, but it doesn't flash/gives Shara error. I tried reinstalling driver. I also read a guide here. But the Firmware link is dead and it says to flash via MiFlash, something I can't even try since the Link in the OP is dead. I tried some different versions of QFIL but all of them give a Sahara Communication error. Now I'm pretty much at a loss on what to do. I'd really like to fix my 6P. And I would appreciate anyone taking the time to point me in the right direction, or help me fix it. Thanks in Advance.
Click to expand...
Click to collapse
Same thing happened to me in the same ROM (Weird) .. but i managed to flash the qfil successfully .. but still phone doesnt boot up .. here's what you should do ... try to hard reset the phone until you hear the disconnecting sound from pc . Ready all the necessary flash in the qfil and as soon as u hear the device connected hit the download button .. it will flash without the sahara protocol error . Be quick ! tell me if that fixed ur problem . Peace

hk1271 said:
Same thing happened to me in the same ROM (Weird) .. but i managed to flash the qfil successfully .. but still phone doesnt boot up .. here's what you should do ... try to hard reset the phone until you hear the disconnecting sound from pc . Ready all the necessary flash in the qfil and as soon as u hear the device connected hit the download button .. it will flash without the sahara protocol error . Be quick ! tell me if that fixed ur problem . Peace
Click to expand...
Click to collapse
Thanks. Can you share the files you used please? I can't for the life of me, find the correct download files. There was a Nexus6P_Unbrick by TenFar but all the links are down.

DarthVader said:
Thanks. Can you share the files you used please? I can't for the life of me, find the correct download files. There was a Nexus6P_Unbrick by TenFar but all the links are down.
Click to expand...
Click to collapse
I used another qfil firmware
https://drive.google.com/file/d/1PixuumVVzxBKUsQ88X3AJ21Hsi2mV3Zq/view
Here is the link .. you can find the firehose and all files in the firmare folder . Best of Luck

I have a similar situation where I am unable to power on the phone in any way, and I am only able to communicate with the qualcom USB 9008 driver.
I am following your instructions using the firmware files you provided (thank you!) and I can see an attempt is being made to download the files before sahara error occurs.
I don't think I enabled developer options when my Nexus 6P was working and wondered if sahara error is due to that.
I was wondering if you had previously enabled developer options by tapping on the build number several times, once the operating system booted and if that is a critical step in being able to recover the Nexus 6p from this hard bricked state where I am stuck in EDL 9008 mode, and unable to access bootloader, and volume+power keys do not do anything...I feel like I'm screwed (and already moved on) but using time these days to learn about android devices!
thanks!