nokia 6 dead - Nokia 6 Questions & Answers

hello
i got a problem with my nokia 6 im hoping someone here is able and willing to help me with.
The phone started doing a system update, but went dead and afterwards it just says that the phone has ever been rooted and that may lead to security risks and malware and instability or something like that. the phone wont even enter the revocery mode or anything, just keeps flashing the same text.
Looking forward to any help offered. since i dont know much about this kind of things id appreciate a thorough and simply put guide on how to fix it.

I reckon it's the same security patch that messed up my phone. What device do you have TA-10?? It's on the back of the device at the bottom. What version of android were you running?
Sent from my MHA-L09 using Tapatalk

imediax said:
I reckon it's the same security patch that messed up my phone. What device do you have TA-10?? It's on the back of the device at the bottom. What version of android were you running?
Sent from my MHA-L09 using Tapatalk
Click to expand...
Click to collapse
yeah its ta-1021. unfortunately i dont know what version of android was i running.

janekkkk said:
yeah its ta-1021. unfortunately i dont know what version of android was i running.
Click to expand...
Click to collapse
Hold down power and volume up until the device powers off. Now, plug the phone into your PC while holding voldown and pwr. It should now say "Download mode" in the bottom right. You can now flash MENA firmware with ost 6.0.4
Let me know if the problem persists.

quagsirus said:
Hold down power and volume up until the device powers off. Now, plug the phone into your PC while holding voldown and pwr. It should now say "Download mode" in the bottom right. You can now flash MENA firmware with ost 6.0.4
Let me know if the problem persists.
Click to expand...
Click to collapse
thank you for answering. the phone is always shut off so i cant do the first step. Neither will the phone go to download mode, simpli says the root stuff again. Only time it does something else is when trying to do a hard reset, then it will also say shutdown device: under the root stuff.

janekkkk said:
thank you for answering. the phone is always shut off so i cant do the first step. Neither will the phone go to download mode, simpli says the root stuff again. Only time it does something else is when trying to do a hard reset, then it will also say shutdown device: under the root stuff.
Click to expand...
Click to collapse
When turned off, open OST and connect your phone when it tells you to do so. It will boot into download mode automatically. (Mine did, so I assume yours will do the same)

ZeroPointMax said:
When turned off, open OST and connect your phone when it tells you to do so. It will boot into download mode automatically. (Mine did, so I assume yours will do the same)
Click to expand...
Click to collapse
got the phone into download mode now i think, atleast it says so on the bottom left corner, but when i try to do the ost la thing it gives an error everytime.
the update process failed !
error code 0xc6da
error: download fails
error=se_err_adb_cmd_GET_FAIL_result(0xc6da)

janekkkk said:
got the phone into download mode now i think, atleast it says so on the bottom left corner, but when i try to do the ost la thing it gives an error everytime.
the update process failed !
error code 0xc6da
error: download fails
error=se_err_adb_cmd_GET_FAIL_result(0xc6da)
Click to expand...
Click to collapse
Can you go into recovery? Grab the dec 2017 update and Flash it from there. This is for downgrading some mechanics that changed with Android Oreo. OST should work again. For more detail, you can look around the many threads and answers on xda.

nokia products
janekkkk said:
hello
i got a problem with my nokia 6 im hoping someone here is able and willing to help me with.
The phone started doing a system update, but went dead and afterwards it just says that the phone has ever been rooted and that may lead to security risks and malware and instability or something like that. the phone wont even enter the revocery mode or anything, just keeps flashing the same text.
Looking forward to any help offered. since i dont know much about this kind of things id appreciate a thorough and simply put guide on how to fix it.
Click to expand...
Click to collapse
I used the nokia products and realized the quality of the product. There is really a special magic in the products that attract the customer. I suggest you use nokia products. I have a site that I've introduced about the popular nokia products. Visit my blog :

@yarimehdi33 this is spam

nokia 6 dead during update Orio to Pie
imediax said:
I reckon it's the same security patch that messed up my phone. What device do you have TA-10?? It's on the back of the device at the bottom. What version of android were you running?
Sent from my MHA-L09 using Tapatalk
Click to expand...
Click to collapse
same problem with my mobile plz help how to fix this problem

Bilal Rehman said:
same problem with my mobile plz help how to fix this problem
Click to expand...
Click to collapse
Boot to download mode by pressing volume down and power button continuously when phone is off.
Download OST 6.0.4 and flash nb0 firmware.
It'll only work if you're max on Dec update.. if later then that than first flash ota from recovery to downgrade bootloader.

Related

Quick Qusetion regarding failed updates

So Orange are supposed to be pushing the 7392 update tomorrow. I have the 4.10.1.9 bad bootloader so am not expecting the update to install however i read here that a few people on 4.10.1.9 were able to do so.
My question is if i try and install and it gets stuck in the reboot loop, what is the correct procedure to abort the update?
Disconnect the cable then pull the battery and reboot? Just pull the battery?
And will i need to recover it at all via zune or will the update just fail and when i reboot the phone it will be ok?
Thanks!
Freypal said:
So Orange are supposed to be pushing the 7392 update tomorrow. I have the 4.10.1.9 bad bootloader so am not expecting the update to install however i read here that a few people on 4.10.1.9 were able to do so.
My question is if i try and install and it gets stuck in the reboot loop, what is the correct procedure to abort the update?
Disconnect the cable then pull the battery and reboot? Just pull the battery?
And will i need to recover it at all via zune or will the update just fail and when i reboot the phone it will be ok?
Thanks!
Click to expand...
Click to collapse
I'm on Orange too but so far no update
Freypal said:
So Orange are supposed to be pushing the 7392 update tomorrow. I have the 4.10.1.9 bad bootloader so am not expecting the update to install however i read here that a few people on 4.10.1.9 were able to do so.
My question is if i try and install and it gets stuck in the reboot loop, what is the correct procedure to abort the update?
Disconnect the cable then pull the battery and reboot? Just pull the battery?
And will i need to recover it at all via zune or will the update just fail and when i reboot the phone it will be ok?
Thanks!
Click to expand...
Click to collapse
The update will just fail once it realised it's booted up again into the OS. Just disconnect and pull the battery. Once you put it back in, it should boot up fine. Connect the cable once again and Zune should say it's failed applying the update.
I'm on Three and still can't get past this issue, even with the Samsung fix.
That's annoying to hear
I suppose you have tried the usual steps of freeing up lots of space on your device and using different USB ports... ?
Then the annoying step of a hard reset?
I pre-emptively applied the Samsung patch as i did not want to be stuck in a boot loop! I don't suppose anyone knows what it actually does? I'm guessing since it only takes like 10 seconds to patch it is just overwriting a possibly faulty file in the phone somewhere that should prevent the update from finishing.
I'm still on 7008! did ya'll get the update?? Or did you all update to nodo post april 11?
comeradealexi said:
I'm still on 7008! did ya'll get the update?? Or did you all update to nodo post april 11?
Click to expand...
Click to collapse
Apparently us poor sods on Orange aren't getting 7392 anytime soon.
http://windowsteamblog.com/windows_phone/b/windowsphone/archive/2011/05/25/more-7392-update-deliveries-underway.aspx
"7392 is now rolling out to Windows Phones on Sprint in the U.S. and Orange in Europe. If you have an Omnia 7 on Orange, you won’t be receiving an update just yet. We are going to update those phones separately."
God knows what that means. Really pissed off about it.
Grrrrr ¬¬ it has been a mahusive **** up the whole NoDo update! they really need to get Mango perfect!
Yup. Really frustrating isn't it!
Freypal said:
Yup. Really frustrating isn't it!
Click to expand...
Click to collapse
Turn off your phone.
Keep holding down the camera button and turn on your phone. If you see the USB to PC mode, your phone will be able to update.
Zune only requires that your phone be able to enter USB to PC download mode(Camera+PowerOn) and not the other Download mode (VolumeUp+Camera+PowerOn).
VoodooKing said:
Turn off your phone.
Keep holding down the camera button and turn on your phone. If you see the USB to PC mode, your phone will be able to update.
Zune only requires that your phone be able to enter USB to PC download mode(Camera+PowerOn) and not the other Download mode (VolumeUp+Camera+PowerOn).
Click to expand...
Click to collapse
That's interesting... Just tried it and my phone does enter the connect to PC mode.
I do have the bad bootloader 4.10.1.9 however i Jigged mine using 301k resistors and installed the Samsung patch so I don't know if this has anything to do with it. No one seems to know what the patch actually does :s
This is good news though! Thanks for the heads up.
VoodooKing said:
Turn off your phone.
Keep holding down the camera button and turn on your phone. If you see the USB to PC mode, your phone will be able to update.
Zune only requires that your phone be able to enter USB to PC download mode(Camera+PowerOn) and not the other Download mode (VolumeUp+Camera+PowerOn).
Click to expand...
Click to collapse
did this, came up saying "restoration error" :s but it wouldnt let me scan for updates so didnt work
Freypal said:
That's interesting... Just tried it and my phone does enter the connect to PC mode.
I do have the bad bootloader 4.10.1.9 however i Jigged mine using 301k resistors and installed the Samsung patch so I don't know if this has anything to do with it. No one seems to know what the patch actually does :s
This is good news though! Thanks for the heads up.
Click to expand...
Click to collapse
The Samsung patch is supposed to fix phones that cannot enter USB > PC download mode. But it doesn't work for some, that is why during Zune patching process, the phone will enter rebooting loop at step 6 because it is trying to enter USB > PC download mode.
If yours is working fine now, you don't have to worry.
VoodooKing said:
The Samsung patch is supposed to fix phones that cannot enter USB > PC download mode. But it doesn't work for some, that is why during Zune patching process, the phone will enter rebooting loop at step 6 because it is trying to enter USB > PC download mode.
If yours is working fine now, you don't have to worry.
Click to expand...
Click to collapse
Ahh right, thanks again. So I guess the lack of being able to enter download mode without the resistor jig is another side effect of this bad bootloader. And without this ability the Samsung patch cannot be applied and the update cannot subsequently complete and update the bad software.
The update from 7008 isnt even available yet though?
comeradealexi said:
The update from 7008 isnt even available yet though?
Click to expand...
Click to collapse
I went from 7008 to 7390 before it was pulled a month or so ago.
For Orange customers though, No it isn't available yet.
Ahh right fair enough, yea i did the same but phone broke and got a replacement but just waiting for nodo update now!
comeradealexi said:
Ahh right fair enough, yea i did the same but phone broke and got a replacement but just waiting for nodo update now!
Click to expand...
Click to collapse
I have to say I would rather them just get the issues with the Omnia sorted and out the way now. I don't really care about receiving 7392 as it adds little / nothing.
If Mango is delayed or Omnia owners i will be infuriated though.
Yes definatley!! The mango update HAS to be smooth because Nodo has been a disaster...
Freypal said:
Ahh right, thanks again. So I guess the lack of being able to enter download mode without the resistor jig is another side effect of this bad bootloader. And without this ability the Samsung patch cannot be applied and the update cannot subsequently complete and update the bad software.
Click to expand...
Click to collapse
No. If your phone can enter USB > PC download mode, Microsoft can choose to fix your bad bootloader through Zune.
Tmobile Omnia 7 users have had their phone firmware upgraded in through Zune.
As long as your phone can enter USB > PC download mode, do not do anything to the phone.

[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

Qualcomm hs-usb qdloader 9008 nexus 6P (HELP!)

Hi there, I've been browsing through the threads related to unbricking of the Nexus 6P stuck in qualcomm hs-usb qdloader 9008 mode, really desperate to get my device working again if even possible however I've tried for about four days now different ways and files and I've had no luck.
My bootloader is locked and no ADB etc managed to get my device showing as the 9008 port so I think it's stuck in EDL.
Following guides, this is the furthest I've yet to get (In screenshot)
Could anyone shed some light and some assistance please? what am I doing wrong!?
attempted to apply for heat some to the device then re flash ?
blackcell1 said:
attempted to apply for heat to the device then re flash ?
Click to expand...
Click to collapse
Sorry, I don't quite understand what you mean?
Clarkeofcurtis said:
Sorry, I don't quite understand what you mean?
Click to expand...
Click to collapse
Use a hairdryer to warm up the back of the phone.
Are you pulling my leg? Warm it up then reflash?
nah im not trying to make you destroy your phone, being rather serious with this method. i use it on a daily basis to solve phones that fail during restoring factory images. i wouldn't know how long to give it with a hair dryer as i have access to a heat gun/heat mats .
just think of it as a cheap mans re balling method
blackcell1 said:
nah im not trying to make you destroy your phone, being rather serious with this method. i use it on a daily basis to solve phones that fail during restoring factory images. i wouldn't know how long to give it with a hair dryer as i have access to a heat gun/heat mats .
just think of it as a cheap mans re balling method
Click to expand...
Click to collapse
Sorry haha, I'm a noob with most of this android stuff bar rooting and flashing a few devices prior! I shall give it a go now and get back to you - thank you for the advice
Clarkeofcurtis said:
Sorry haha, I'm a noob with most of this android stuff bar rooting and flashing a few devices prior! I shall give it a go now and get back to you - thank you for the advice
Click to expand...
Click to collapse
good luck, id give it a good couple of minutes on the highest setting, just so its a little hot to the touch. and attempt the flashing of the files when its still hot/warm.
blackcell1 said:
good luck, id give it a good couple of minutes on the highest setting, just so its a little hot to the touch. and attempt the flashing of the files when its still hot/warm.
Click to expand...
Click to collapse
thank you so much that worked, it has said flash successful, first time I got a google logo but now nothing, what would be my next step please?
if the bootloader is unlocked then you can directly flash the firmware. but if its not google "nexus ota" and then on your phone jump into the recovery and check the firmware model number and download the same ota and adb sideload it.
im not 100% sure on the next step as I've never had a nexus 6p with a dead bootloader. but thats what id do.
---------- Post added at 04:50 PM ---------- Previous post was at 04:49 PM ----------
but from my personal experience with having to heat a phone up to restore factory images, it kinda means the phone is nearing the end of its life and id start thinking about buying your next phone before it sh*ts the bed.
blackcell1 said:
if the bootloader is unlocked then you can directly flash the firmware. but if its not google "nexus ota" and then on your phone jump into the recovery and check the firmware model number and download the same ota and adb sideload it.
im not 100% sure on the next step as I've never had a nexus 6p with a dead bootloader. but thats what id do.
Click to expand...
Click to collapse
Thank you for the reply and continuing to help, after seeing the google logo just once I'm getting nothing again - I'm even more determined now though as It's been dead for 2 months so this is the furthest I've gotten - the application of heat is what did it for me and fixed the error I was getting, can't get into recovery now though holding power + down etc
Clarkeofcurtis said:
Thank you for the reply and continuing to help, after seeing the google logo just once I'm getting nothing again - I'm even more determined now though as It's been dead for 2 months so this is the furthest I've gotten - the application of heat is what did it for me and fixed the error I was getting, can't get into recovery now though holding power + down etc
Click to expand...
Click to collapse
yeah can you access the bootloader at all ? does it say that the bootloader is locked ? from trying to restore LG's it sometimes has to be re heated a few times, but yeah if you need to re heat it to get further into the phone then its pretty much a lost cause. the only reason i do it is to remove the data so we can resell the device.
blackcell1 said:
yeah can you access the bootloader at all ? does it say that the bootloader is locked ? from trying to restore LG's it sometimes has to be re heated a few times, but yeah if you need to re heat it to get further into the phone then its pretty much a lost cause. the only reason i do it is to remove the data so we can resell the device.
Click to expand...
Click to collapse
I can get into the andriod screen where you can select recovery and such, with the BL, Baseband product variation and such, where should I go from here?
Oh right, so even once restored to firmware, will it be useless do you think if I can even manage to?
Clarkeofcurtis said:
I can get into the andriod screen where you can select recovery and such, with the BL, Baseband product variation and such, where should I go from here?
Oh right, so even once restored to firmware, will it be useless do you think if I can even manage to?
Click to expand...
Click to collapse
Sorry if you can't access the recovery from the bootloader and its in locked state then your a member of the lovely group of BLOD (bootloader of death) if you hit recovery does it show a little android logo and sit there?
Sorry for the late reply
blackcell1 said:
Sorry if you can't access the recovery from the bootloader and its in locked state then your a member of the lovely group of BLOD (bootloader of death) if you hit recovery does it show a little android logo and sit there?
Sorry for the late reply
Click to expand...
Click to collapse
I believe so, I can just about get into the bootloader at the best of times and when I do I can select options but once proceeding to start said mode phone freezes so can't get into recovery mode :/
Thank you for your continuous help, only way i can get it into bootloader is by heating it up so does that mean for the device to ever work It'll need heat every time? looking like a spares and repairs listing on ebay
Clarkeofcurtis said:
I believe so, I can just about get into the bootloader at the best of times and when I do I can select options but once proceeding to start said mode phone freezes so can't get into recovery mode :/
Thank you for your continuous help, only way i can get it into bootloader is by heating it up so does that mean for the device to ever work It'll need heat every time? looking like a spares and repairs listing on ebay
Click to expand...
Click to collapse
Hello....
How did you manage to get in to EDL mode..? I'm really curious. With stock bootloader? Since you can't access recovery
Also what is exactly displayed in Windows device manager?
You are using an outdated QFil version... It is from 2014 àr 2015.
Do a google search with: QPST_2.7.453.0 . This version seem to be from 2016.
Use the first link from the result. I analysed the files with virustotal, those seem clean or malware...
Also when plugging your usb cord to your PC, does your phone vibrate? Or does the LED blink in red?
You may have to press power button when plugging the usb cord or press power button for a certain amount of time before you plug the usb cord. I'm not completly sure, but your phone may not be in the "proper" EDL state to accept the QFil flash.
Good luck... :good:
Is it possible to send me the guide you used? Thanks.
Clarkeofcurtis said:
Hi there, I've been browsing through the threads related to unbricking of the Nexus 6P stuck in qualcomm hs-usb qdloader 9008 mode, really desperate to get my device working again if even possible however I've tried for about four days now different ways and files and I've had no luck.
My bootloader is locked and no ADB etc managed to get my device showing as the 9008 port so I think it's stuck in EDL.
Following guides, this is the furthest I've yet to get (In screenshot)
Could anyone shed some light and some assistance please? what am I doing wrong!?
Click to expand...
Click to collapse
Hey there sorry for slow replies, will be back on my desktop in an hour I'll send you links for what I followed and such, I think the only reason my device was in EDL mode was due to a hardware fault? As my device is faulty indefinitely as I had to use a hairdryer to warm it up while flashing this then allowed it to enter firehose state which a lot of people seem to error with - after all my attempts and research I'm to velieve there's a fault with the phone itself the only way I could get it to even power up was applying heat to it after removing the back panel
As blackcell said deballing or something? Worked a treat!
Furthest I've managed to get now is into my boot loader however everything is locked - when I press enter recovery my handset just freezes ?
5.1 said:
Hello....
How did you manage to get in to EDL mode..? I'm really curious. With stock bootloader? Since you can't access recovery
Also what is exactly displayed in Windows device manager?
You are using an outdated QFil version... It is from 2014 àr 2015.
Do a google search with: QPST_2.7.453.0 . This version seem to be from 2016.
Use the first link from the result. I analysed the files with virustotal, those seem clean or malware...
Also when plugging your usb cord to your PC, does your phone vibrate? Or does the LED blink in red?
You may have to press power button when plugging the usb cord or press power button for a certain amount of time before you plug the usb cord. I'm not completly sure, but your phone may not be in the "proper" EDL state to accept the QFil flash.
Good luck... :good:
Click to expand...
Click to collapse
Thanks pal if you check last post I wrote about my EDL mode forgot to tag you my apologies, as for my LED I've never seen that light up since I bricked it, even when google logo came up etc and while in the boot loader
Clarkeofcurtis said:
Thanks pal if you check last post I wrote about my EDL mode forgot to tag you my apologies, as for my LED I've never seen that light up since I bricked it, even when google logo came up etc and while in the boot loader
Click to expand...
Click to collapse
Light usually a red LED blink while in proper EDL state as far as I know. Could be something else on the N6P. Well, it looks like you are SOL. Sorry, I don't know what else to say, since you exhausted all possibilities...
Good luck...

I have totally bricked my zte axon 7 a2017g and i seriously need help!!

So guys, i have tried to downgrade my phone from android 7.1.1 to 6.0 which ended in a softbrick, after that i tried 2 flash a stock rom but that completely bricked it and now my phone wont dont anything anymore except for some kind of mode that my computer can detect in device it sees the qualcomm port 9008 device but there a thing it just wont work miflash doesnt recognize it and i cant find any sollutions online please help
tnhx
Daan_K said:
So guys, i have tried to downgrade my phone from android 7.1.1 to 6.0 which ended in a softbrick, after that i tried 2 flash a stock rom but that completely bricked it and now my phone wont dont anything anymore except for some kind of mode that my computer can detect in device it sees the qualcomm port 9008 device but there a thing it just wont work miflash doesnt recognize it and i cant find any sollutions online please help
tnhx
Click to expand...
Click to collapse
I wonder:
-Which is your phone model, as stated on the back of the phone?
-Which is the file that you used to downgrade?
-Which stock rom did you try to flash?
The fix is pretty simple but seeing how you borked three simple procedures I'd like to know everything and lay it out for you precisely. You have to have done something horribly wrong to softbrick a phone with the stock updater system...
Choose an username... said:
I wonder:
-Which is your phone model, as stated on the back of the phone?
-Which is the file that you used to downgrade?
-Which stock rom did you try to flash?
The fix is pretty simple but seeing how you borked three simple procedures I'd like to know everything and lay it out for you precisely. You have to have done something horribly wrong to softbrick a phone with the stock updater system...
Click to expand...
Click to collapse
Okay at first my phone model on the back of my device is, as i mentioned before, "zte a2017g" thats the european version of this phone, chinese is "a2017" and the us version is "2017u".
The file i used 2 downgrade was the stock rom from the official website of zte
it was the full edl file buildnumber b10.
and again i once sofbricked it, i know how 2 fix that, but now it hard bricked, well i think so at least, i cant get it to boot into bootloader, recovery or anything, when i hold the power button it shakes the device, and it shows the zte logo for about 2 seconds then it disappears, and nothing happens but my computer does recognize it as a connected device but i cant use miflash of something else because those programs dont see it.
Daan_K said:
Okay at first my phone model on the back of my device is, as i mentioned before, "zte a2017g" thats the european version of this phone, chinese is "a2017" and the us version is "2017u".
The file i used 2 downgrade was the stock rom from the official website of zte
it was the full edl file buildnumber b10.
and again i once sofbricked it, i know how 2 fix that, but now it hard bricked, well i think so at least, i cant get it to boot into bootloader, recovery or anything, when i hold the power button it shakes the device, and it shows the zte logo for about 2 seconds then it disappears, and nothing happens but my computer does recognize it as a connected device but i cant use miflash of something else because those programs dont see it.
Click to expand...
Click to collapse
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Choose an username... said:
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Click to expand...
Click to collapse
allright allready thanks loads for your support but could you maybe send the right file to flash because i have no idea, and please, the files for a2017g not a2017 or a2017u thankyou so much
Daan_K said:
allright allready thanks loads for your support but could you maybe send the right file to flash because i have no idea, and please, the files for a2017g not a2017 or a2017u thankyou so much
Click to expand...
Click to collapse
they are in the guide. at the top, there's a link to WesTD's EDL flashable files. Get one for A2017G, for example B09
Choose an username... said:
they are in the guide. at the top, there's a link to WesTD's EDL flashable files. Get one for A2017G, for example B09
Click to expand...
Click to collapse
Allright, thankyou so much my dude
Choose an username... said:
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Click to expand...
Click to collapse
aight, as i thought this didnt work, i tired it but miflash basicly just gave me an error notification.
also when i go into device manager i can see that my device is connected but i show the name with a yellow triangle with a ! in it i have no clue what this means can u please help me with this. i rlly want my phone back
Daan_K said:
aight, as i thought this didnt work, i tired it but miflash basicly just gave me an error notification.
also when i go into device manager i can see that my device is connected but i show the name with a yellow triangle with a ! in it i have no clue what this means can u please help me with this. i rlly want my phone back
Click to expand...
Click to collapse
First of all, if you get an error TELL ME what it says!
Send me a screenshot of the device manager, i can do very little with "yellow triangle"
Don't bother? That guy is using XDA as a free emergency support without looking for one second.
He probably would like you to do a teamviewer while he's watching football with a beer and not even say thank you.
I'm horrified.
RedWave31 said:
Don't bother? That guy is using XDA as a free emergency support without looking for one second.
He probably would like you to do a teamviewer while he's watching football with a beer and not even say thank you.
I'm horrified.
Click to expand...
Click to collapse
rlly m8. im just a guy who needs help with his phone the guy "choose a username..." i helping me with it, ive been unable 2 fix my phone with any of the other threads i just need some help and i have said thanks alot, dont call me that
Daan_K said:
rlly m8. im just a guy who needs help with his phone the guy "choose a username..." i helping me with it, ive been unable 2 fix my phone with any of the other threads i just need some help and i have said thanks alot, dont call me that
Click to expand...
Click to collapse
Sorry, I don't believe you for one second. Like litterally THOUSANDS of people here and here opening "bricked plz hlp" threads, you didn't even have the BASIC, LOWEST courtesy of writing more than 10 words of gibberish whining about your situation, without a single usefull element of context.
Proof of that in the NUMEROUS questions asked about ELEMENTARY elements about your situation. You're litterally the kind of person that would go to a car mechanic, drop the keys on the counter saying "my car is broken, fix it" and just leave without a single word added. That's RUDE and, yeah, I'm tired AF of people like you who can't READ THE DAMN XDA RULES and got NOT education whatsoever.
Nd writng frm a phone in T9 mde dsnt rlly bring nythng mre on the tble either.
Too bad you found somebody to help, as it's only encouraging that kind of behaviour.
//Rant off//
@Daan_K this EDL Tool can help https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Choose an username... said:
First of all, if you get an error TELL ME what it says!
Send me a screenshot of the device manager, i can do very little with "yellow triangle"
Click to expand...
Click to collapse
this is a screenshot of my device manager, and what I meant with yellow triangle, also it doesn't work with the edl-tool nor the axon7tool
Daan_K said:
this is a screenshot of my device manager, and what I meant with yellow triangle, also it doesn't work with the edl-tool nor the axon7tool
Click to expand...
Click to collapse
Okay, let's try two things:
First right click on it and uninstall the device, also delete driver software for the device (it will be a checkbix asking for that after you hit 'uninstall device'). After that, hold Volume up, Volume down, and Power until the Device manager refreshes. After that the driver should reinstall itself. If it still shows with the yellow triangle, right click it, click on Properties, and send me a screenshot (or translate me what it says on the status part)
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
if you can only get to dfu mode and nothing else, use thise guide, you'll have to dismantle your phone. Had to unbrick mine with this from a hardbrick, worked flawlessly
IvI97 said:
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
if you can only get to dfu mode and nothing else, use thise guide, you'll have to dismantle your phone. Had to unbrick mine with this from a hardbrick, worked flawlessly
Click to expand...
Click to collapse
Hey, a couple of things: one, i've updated the guide, it's around, much simpler to use. just saying. Two, this guy has the right driver. Don't confuse him with DFU while at least for now it is not.
Choose an username... said:
Okay, let's try two things:
First right click on it and uninstall the device, also delete driver software for the device (it will be a checkbix asking for that after you hit 'uninstall device'). After that, hold Volume up, Volume down, and Power until the Device manager refreshes. After that the driver should reinstall itself. If it still shows with the yellow triangle, right click it, click on Properties, and send me a screenshot (or translate me what it says on the status part)
Click to expand...
Click to collapse
omg the triangle is gone, thankyousomuch, but what can I use now 2 fix it further?? is that in your guide maybe?
choose an username... said:
hey, a couple of things: One, i've updated the guide, it's around, much simpler to use. Just saying. Two, this guy has the right driver. Don't confuse him with dfu while at least for now it is not.
Click to expand...
Click to collapse
omygod it ****ing working, choose an username man, i can't thank you enough, seriously ur the best man lots of love for doing this

Any help with fully bricked device

Hello!
THink I have bricked my phone, but just checking before I go through what I suppose is a long process with oneplus.
Looking for any help. I had a working device - unlocked bootloader and installed TWRP and magisk using MauronofrioTool. ok - however, I found out I couldn't use a fingerprint security option on that would have been anoying. So... Long story short. I used MauronofrioTool to relock bootloader. Oops - so that didn't work. THen found out I couldn't do anything except stare at g.co/ADH message on my screen. Couldn
't get to fastboot or TWP. ANyway, so I managed to up and down volume and enter into TWRP. Was still connecting to the tool, so I downloaded factory Zips and tried to install via tool after unlocking - Seemed to be working ... but it stopped mid way through a process and hasbn't come back! NOthing at all. I wonder if I could have triggered an OEM thing? ANyway - literally nothing no buttons work no screen action. I see a QUSB_BULK_CID:etc number when connecting the phone, but that is it. No fast boot or any other actions available.
PLease, pretty devastating, Anyone know if I can do anything?
I'm no pro but I use this tool which helped me:
henk-jan said:
I'm no pro but I use this tool which helped me:
Click to expand...
Click to collapse
Thank you. I feel I am little past this stage now though.. Also trying the brick reprieve software . Just can't get my computer to recognise the phone now. No ability to get to emergency download path - think it is my crappy cihinese pc (old Huawei tablet basically) or Windows via apple that have me stranded.
**********SOLVED
THe crappy Chinese language Windows tablet worked as the unbrick OP said WIndows would. Must be a kink in the Windows via Mac that could get me into the situation, but not out.
Very relieved... Even though I still am not 100% sure what I actually ended up clicking to get it to register and connect with the unblock tool (which of course was in Chinese) hahaha.
Cheers
CHeers though
Glad you got it sorted out! Cheers
Need Help, please
Just received my OnePlus 8 pro, decided to Root and unlock the bootloader---this went fine.
I then went and upgraded to Android 11 DP3.
I'm now only able to get into Fastboot. at points it will try to boot but only get to the logo screen and then goes black.
When the phone boots up, it goes to Qualcomm CrashDump Mode.
I've been attempting to solve this for half the day with no luck. I've tried Msmtool, but it doesn't recognize the device, even after loading drivers again.
Is there a way to load a ROM from fastboot mode?
Hoping someone can assist, this is super frustrating and I would appreciate any help, please.
Rick
rickhurl said:
Just received my OnePlus 8 pro, decided to Root and unlock the bootloader---this went fine.
I then went and upgraded to Android 11 DP3.
I'm now only able to get into Fastboot. at points it will try to boot but only get to the logo screen and then goes black.
When the phone boots up, it goes to Qualcomm CrashDump Mode.
I've been attempting to solve this for half the day with no luck. I've tried Msmtool, but it doesn't recognize the device, even after loading drivers again.
Is there a way to load a ROM from fastboot mode?
Hoping someone can assist, this is super frustrating and I would appreciate any help, please.
Rick
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-8-pro/how-to/rom-stock-fastboot-roms-oneplus-8-pro-t4083997
cultofluna said:
https://forum.xda-developers.com/oneplus-8-pro/how-to/rom-stock-fastboot-roms-oneplus-8-pro-t4083997
Click to expand...
Click to collapse
Thanks so much. I ended up getting Msmtool to work. Although my device wasn't on (black screen) and it didn't fully show up in the tool, I decided to start the process anyway and it began to load.
I've been on here for over 10 yeas (XDA) I've just lost my account info and made a new one.
Thanks for taking the time to respond. Much appreciated.

Categories

Resources