Develop Bugs

[Q] NOKIA X dead

Dear sirs & all friends
I have nokia x & I had rooted it to install swapper 2
I had enabled swap space & to activate the swap memory on external sd card swapper 2 told me to reboot the device.
This was a mistake since now My nokia x will not boot in any case & is completely dead.
It even fails to boot into recovery mode.
It even does not show nokia logo.
Screen remains blank even after a removing battery and powering up again by putting battery back
Windows 8 detects it as a usb drive & asks to format it.
I am afraid to format it since it may completely make the device dead
I have tried nokia care to flash rom but it also fails to detect the phone even after pressing volume down button and power button(given procedure on nokia care)
I tried nokia x toolkit but it even fails to detect the phone
I searched the internet but every method on internet asks to boot into recovery mode which will not work in my case since my phone is not booting in recovery mode.
/COLOR]Please help me recover restart my nokia x["
Whatisbad17

First of all, congratulations for getting your device bricked.
Well, jokes apart, I might be able to help you on how to fix this. Just follow step by step everything.
1. Download Nokia X Flasher from here: http://forum.xda-developers.com/showthread.php?t=2744881
2. Install it. Run it and keep it ready.
3. As your phone is dead, I advise you take out the SIM and SD card and keep them away.
4. Now you need to flash the latest v1.2.2 update. For that, you need to follow the great tutorial here: http://forum.xda-developers.com/showthread.php?t=2744881
If this works, you could always thank me or buy me a bear.
If any problems, I'm alive. Cheers.
One thing i'd like to add, that in the guide it tells you to enter bootloader mode via power button. I advise you to simply turn your phone off, hold the volume button down and insert the usb cable. It should go into bootloader mode.

i have same problem, brick nokia x, try that flasher but it didnt detect my phone

Nokia X dead
Dom3616 said:
First of all, congratulations for getting your device bricked.
Well, jokes apart, I might be able to help you on how to fix this. Just follow step by step everything.
1. Download Nokia X Flasher from here: http://forum.xda-developers.com/showthread.php?t=2744881
2. Install it. Run it and keep it ready.
3. As your phone is dead, I advise you take out the SIM and SD card and keep them away.
4. Now you need to flash the latest v1.2.2 update. For that, you need to follow the great tutorial here: http://forum.xda-developers.com/showthread.php?t=2744881
If this works, you could always thank me or buy me a bear.
If any problems, I'm alive. Cheers.
One thing i'd like to add, that in the guide it tells you to enter bootloader mode via power button. I advise you to simply turn your phone off, hold the volume button down and insert the usb cable. It should go into bootloader mode.
Click to expand...
Click to collapse
Dom3616
Sorry but your Nokia X flasher does not detect my nokia X because whenever I remove battery & replace battery, & then power up device by pressing volume down & power button, & releasing vol down button after 15 seconds of vibration of device, the device does not show anything on screen.
I am still stuck with dead nokia X.
Please help again with different solution
Anybody please help
Whatisbad17

Does the phone not show up at all on your computer?
One thing I must add is that you need to enter bootloader mode, by simply pressing volume down button when inserting usb cable. No need to power up device. And although you may not see anything on screen, you'll still be in bootloader mode.
---------- Post added at 09:23 PM ---------- Previous post was at 09:15 PM ----------
Check these softwares out:
http://news.softpedia.com/news/Noki...y-Tool-for-Fixing-Bricked-Phones-424125.shtml
http://www.softpedia.com/progDownload/Nokia-Software-Updater-Download-141287.html
I've heard these have unbricked many phones. Try these out and report back.

not working too

Nokia x dead
:crying::crying::crying
I powered down device by removing battery & replacing battery
Then I pressed vol down button as suggested by you & connected it to usb cable
A windows dialog box pops us asking me to format the phone which I always deny
Then I tried to recover the firmware by trying nokia care suite but in vain .
The device is simply not detected by nokia care suite or adb
what should I do?

Nokia x dead
:crying:
Even I tried nokia software updated & nokia software recovery tool but these softwares I think are for LUMIA devices & nokia x
They both fail to detect my phone
:crying:
HELP

nokia x dead bricked
I cannot use this tool, my pc only detect Qualcomm CDMA Technology MSM... i try volume down then insert usb, but still the same detection pls help...

Same here...my pc also detects my nokia x as Qualcomm Device....i accidentally formatted my phone using pc
Please help XDA....We need your help !

k3t3k said:
I cannot use this tool, my pc only detect Qualcomm CDMA Technology MSM... i try volume down then insert usb, but still the same detection pls help...
Click to expand...
Click to collapse
basit21 said:
Same here...my pc also detects my nokia x as Qualcomm Device....i accidentally formatted my phone using pc
Please help XDA....We need your help !
Click to expand...
Click to collapse
whatisbad17 said:
:crying:
Even I tried nokia software updated & nokia software recovery tool but these softwares I think are for LUMIA devices & nokia x
They both fail to detect my phone
:crying:
HELP
Click to expand...
Click to collapse
Try Installng qualcomm pc drivers : http://www.driverscape.com/download/qualcomm-cdma-technologies-msm
After that, charge your phone for atleast an hour and check whether pc detects adb or fastboot. I hope this fix runs. Give me feedback.

Dom3616 said:
Try Installng qualcomm pc drivers : http://www.driverscape.com/download/qualcomm-cdma-technologies-msm
After that, charge your phone for atleast an hour and check whether pc detects adb or fastboot. I hope this fix runs. Give me feedback.
Click to expand...
Click to collapse
i have this problem and my device breaked . :crying:
in cmw i format sys boot and now when i power my device just vibrate and when i connect to pc detect qualcomm pc drivers
pls help me how to fix this problem ?

gandolf007 said:
i have this problem and my device breaked . :crying:
in cmw i format sys boot and now when i power my device just vibrate and when i connect to pc detect qualcomm pc drivers
pls help me how to fix this problem ?
Click to expand...
Click to collapse
Install the drivers above, and then see if you can enter adb or fastboot. Hope this works.
---------- Post added at 07:42 PM ---------- Previous post was at 07:09 PM ----------
gandolf007 said:
i have this problem and my device breaked . :crying:
in cmw i format sys boot and now when i power my device just vibrate and when i connect to pc detect qualcomm pc drivers
pls help me how to fix this problem ?
Click to expand...
Click to collapse
You can also try this.
For all those who have bricked their phones.
Download Nokia Flasher.
Remove the battery and sd card from the device,
Without the battery in, hold down the volume - key while inserting the usb cable into your phone.
If it detects you in adb or fastboot, use this guide to flash the stock rom: http://forum.xda-developers.com/showthread.php?t=2747262
If it detects Qualcom device, download and install the drivers which I have provided in the previous post. After you have done this, you just might be able to connect to adb.
Report back if it works.

Dom3616 said:
Install the drivers above, and then see if you can enter adb or fastboot. Hope this works.
---------- Post added at 07:42 PM ---------- Previous post was at 07:09 PM ----------
You can also try this.
For all those who have bricked their phones.
Download Nokia Flasher.
Remove the battery and sd card from the device,
Without the battery in, hold down the volume - key while inserting the usb cable into your phone.
If it detects you in adb or fastboot, use this guide to flash the stock rom: http://forum.xda-developers.com/showthread.php?t=2747262
If it detects Qualcom device, download and install the drivers which I have provided in the previous post. After you have done this, you just might be able to connect to adb.
Report back if it works.
Click to expand...
Click to collapse
tanx but nokia x flasher not detected my device !!

gandolf007 said:
tanx but nokia x flasher not detected my device !!
Click to expand...
Click to collapse
Did you install qualcom drivers?

Dom3616 said:
Did you install qualcom drivers?
Click to expand...
Click to collapse
I think he broke his bootloader partition..

Hi, please check out this link
http://news.softpedia.com/news/Nokia-Launches-Software-Recovery-Tool-for-Fixing-Bricked-Phones-424125.shtml
EDIT:
i think this one is more useful.
http://www.seidea.com/2014/05/25/dead-flashing-nokia-x-with-nokia-care-suite/

Surpriser said:
Hi, please check out this link
http://news.softpedia.com/news/Nokia-Launches-Software-Recovery-Tool-for-Fixing-Bricked-Phones-424125.shtml
EDIT:
i think this one is more useful.
http://www.seidea.com/2014/05/25/dead-flashing-nokia-x-with-nokia-care-suite/
Click to expand...
Click to collapse
"Nokia Software Recovery Tool is now available for download via company’s support site, but is only compatible with Windows Phone 7 and newer."

Ok maybe secound link become usefull.
Sent from my Xperia Play using Tapatalk

I am facing the same issue. I ve installed quallcom driver but its not detecting fastboot [vol- and without battery]
Please help me out? What should I do now??

HELP! Fully Bricked LG G3 D855 Blank Screen

Hi,
I think I mistakenly flashing the Fastboot partition with all wrong version of Boot, Recovey and the rest of other partition.
Now phone is only turn with BLANK BLACK SCREEN, but USB Connection still active with COM assigned at port 41 (saw under device manager).
Anyone have idea how to flash it back to work, please .....
mKHMER

mkhmer said:
Hi,
I think I mistakenly flashing the Fastboot partition with all wrong version of Boot, Recovey and the rest of other partition.
Now phone is only turn with BLANK BLACK SCREEN, but USB Connection still active with COM assigned at port 41 (saw under device manager).
Anyone have idea how to flash it back to work, please .....
mKHMER
Click to expand...
Click to collapse
Search for latest stock rom 29 at the end of version number download an unzip to desktop.
Flash in Flashtool,at first take battery out and and flash only the bootloader uncheck everithing else !!!,when finisht disconect phone ,put battery in ,now in flashtool flash whole rom

Does your PC recognize your phone as Qualcomm HS-USB QDLoader 9008 or something else?

ludoke said:
Search for latest stock rom 29 at the end of version number download an unzip to desktop.
Flash in Flashtool,at first take battery out and and flash only the bootloader uncheck everithing else !!!,when finisht disconect phone ,put battery in ,now in flashtool flash whole rom
Click to expand...
Click to collapse
It dosn't recognize my USB driver, is there any driver needed to manually install? but if we put the battery it does [LGE AndroidNET COMx]

mkhmer said:
It dosn't recognize my USB driver, is there any driver needed to manually install? but if we put the battery it does [LGE AndroidNET COMx]
Click to expand...
Click to collapse
If PC doesn't recognize your device as Qualcomm HS-USB QDLoader 9008, you need to JTAG your device, or short pin.
Information about short pin;
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359

That look like we need to work direct on mainboard of the phone? anyway withou touching inside the phone?

mkhmer said:
That look like we need to work direct on mainboard of the phone? anyway withou touching inside the phone?
Click to expand...
Click to collapse
You have to disassembly your device.

My LG G3 is not recognised as stated above but as Android device LGE MOBILE ADB INTERFACE and i have no issues on Win 10.
The phone is also imidiatly detected by LG Pc Suite

ludoke said:
My LG G3 is not recognised as stated above but as Android device LGE MOBILE ADB INTERFACE and i have no issues on Win 10.
The phone is also imidiatly detected by LG Pc Suite
Click to expand...
Click to collapse
But when I remove the back cover, I see another stainless steel cover on those chip/board, how to remove it? Too risky!

http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359/page8#post63750296
Here is a brioef guide i am also facing that issue from alst five days.. hope some master help to solve that situation

HELP!
Soooo... I have LG G3 D855 32GB, i think i installed wrong version of TWRP recovery (for another phone). Phone is not charging, so battery is dead. NO boot, NO recovery and NO download mode. PC does not recognize phone with LG drivers and QDLoader USB driver installed. I already do a "short pin" and nothing changes at all. I am out of solutions, please help me.
I already tried:
https://www.reddit.com/r/LGG3/comments/41wbo3/how_to_unhardbrick_your_lg_g3_jtag/
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
http://forum.xda-developers.com/sprint-lg-g3/general/guide-how-to-restore-sprint-lg-g3-ls990-t2852042

ExtremeD722 said:
Soooo... I have LG G3 D855 32GB, i think i installed wrong version of TWRP recovery (for another phone). Phone is not charging, so battery is dead. NO boot, NO recovery and NO download mode. PC does not recognize phone with LG drivers and QDLoader USB driver installed. I already do a "short pin" and nothing changes at all. I am out of solutions, please help me.
I already tried:
https://www.reddit.com/r/LGG3/comments/41wbo3/how_to_unhardbrick_your_lg_g3_jtag/
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
http://forum.xda-developers.com/spr...de-how-to-restore-sprint-lg-g3-ls990-t2852042
Click to expand...
Click to collapse
Your computer recognize any serial port when you connect g3

[email protected] said:
Your computer recognize any serial port when you connect g3
Click to expand...
Click to collapse
Computer doesn't recognize anything... I tried all 4 ports (2 ports 3.0, 2 ports 2.0), with original cable and non-original(Sony) cable.

ExtremeD722 said:
I tried all 4 ports (2 ports 3.0, 2 ports 2.0), with original cable and non-original(Sony) cable.
Click to expand...
Click to collapse
I mean any responce in pc device manager when u connect ur mbl

[email protected] said:
I mean any responce in pc device manager when u connect ur mbl
Click to expand...
Click to collapse
No, device manager detects nothing. I have windows 10 (i tried in normal mode and test mode). And if I connect my G3 Beat computer crashes because of LG driver.( I tried different versions of LG drivers and always the same crash(error)).

ExtremeD722 said:
No, device manager detects nothing. I have windows 10 (i tried in normal mode and test mode). And if I connect my G3 Beat computer crashes because of LG driver.( I tried different versions of LG drivers and always the same crash(error)).
Click to expand...
Click to collapse
I think crashing driver due to window .Try to connect ur device at window 7 .Hope device manager show serial port or qhbulk.I was have same problem my g3 but i resolve by short wire method.Good luck
---------- Post added at 03:01 PM ---------- Previous post was at 02:53 PM ----------
ExtremeD722 said:
Soooo... I have LG G3 D855 32GB, i think i installed wrong version of TWRP recovery (for another phone). Phone is not charging, so battery is dead. NO boot, NO recovery and NO download mode. PC does not recognize phone with LG drivers and QDLoader USB driver installed. I already do a "short pin" and nothing changes at all. I am out of solutions, please help me.
I already tried:
https://www.reddit.com/r/LGG3/comments/41wbo3/how_to_unhardbrick_your_lg_g3_jtag/
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
http://forum.xda-developers.com/sprint-lg-g3/general/guide-how-to-restore-sprint-lg-g3-ls990-t2852042
Click to expand...
Click to collapse
Bro firt change ur window then install ur variant driver and qhbulk driver.After that if device manager show qhsub bulk port or something like then all problem will solve.If ur device manager show only lge serial port then use short wire method.:good:

[email protected] said:
I think crashing driver due to window .Try to connect ur device at window 7 .Hope device manager show serial port or qhbulk.I was have same problem my g3 but i resolve by short wire method.Good luck
Click to expand...
Click to collapse
I will try with other computers, but i have on all 3 computers win10...
Thx for respond !

ExtremeD722 said:
I will try with other computers, but i have on all 3 computers win10...
Thx for respond !
Click to expand...
Click to collapse
Then u should install window 7 because qhsub bulk will not dect on window 10.
---------- Post added at 04:11 PM ---------- Previous post was at 04:07 PM ----------
Bro when u install window 7 reply me if u get any issue.Be careful when u use short wire method because due to this method my g3 baseband and imei are unknow

[email protected] said:
Then u should install window 7 because qhsub bulk will not dect on window 10.
---------- Post added at 04:11 PM ---------- Previous post was at 04:07 PM ----------
Bro when u install window 7 reply me if u get any issue.Be careful when u use short wire method because due to this method my g3 baseband and imei are unknow
Click to expand...
Click to collapse
I will reply u soon. Why do u even need baseband and imei ?

Because my baseband. Unknown and imei is null

lg g3 bricked shows qdloaderboard diag says ap check failed device not in dwnld mode

i rooted my lg g3 d 855 lollipop and tried to install TWRP
but it was not a success i lost recovery + download mode but it boots perfectly into android system and can use it normally
to install twrp again i tried to flash it again and again but no success
then i flash aboot.img and it all went blank not booting not rrecovery etc
i tried board diag method to unbrick it shows up in my system as qcomm hs usb 9008
but when using board diag it says DEVICE NOT FOUND IN DLOAD MODE
plz help this is my first android phone after months of hardwork
i dont think i have enough money to replace the mobo or buy a new one:crying:

Hello,
it's recoverable, but you need to read and some knowledge...
Refer to this thread. Proceed point by point and use willcracker boarddiag.

halekhonza said:
Hello,
it's recoverable, but you need to read and some knowledge...
Refer to this thread. Proceed point by point and use willcracker boarddiag.
Click to expand...
Click to collapse
brother i used board diag method it is succesfully able to show my device as qcomm hs usb 9008
and im able extract the files with program
but when i click start after some time it says ap check failed ,device not found in dload mode
i desperately need ur help IM NEW TO XDA FORUMS I HOPE ANYONE WOULD BE ABLE TO SOLVE PROBLEM
tnx in advanc

adilismail62 said:
brother i used board diag method it is succesfully able to show my device as qcomm hs usb 9008
and im able extract the files with program
but when i click start after some time it says ap check failed ,device not found in dload mode
i desperately need ur help IM NEW TO XDA FORUMS I HOPE ANYONE WOULD BE ABLE TO SOLVE PROBLEM
tnx in advanc
Click to expand...
Click to collapse
I understand. I'm just asking if you really using right boarddiag (thread that I mentioned - willcracker.rar)
Also be sure that you have a phone connected to right port (check it in device manager)

halekhonza said:
I understand. I'm just asking if you really using right boarddiag (thread that I mentioned - willcracker.rar)
Also be sure that you have a phone connected to right port (check it in device manager)
Click to expand...
Click to collapse
halekhonza said:
I understand. I'm just asking if you really using right boarddiag (thread that I mentioned - willcracker.rar)
Also be sure that you have a phone connected to right port (check it in device manager)
Click to expand...
Click to collapse
yes im using the r8 port it shows in device manager and in board daig also i gave port 14
before my phone was going to get bricked its battery was low
is it affecting the procedure i think my battery is not charging
when i remove battery and connect to pc phone shows battery not inserted sign when i insert the batery it disappear and no sign of charging
i thought this might help:good:

You have to use the original LG usb cable. Dont try with fake china cables because its a lot possible to have troubles with them.

{Solved}I gotta super slim brick !!!!

I attempted to flash Dirty Unicorn from they're site, which appeared to go well, then I proceeded to flash the TWRPinstaller.zip that was suggested from the maintainer for our device. when I tried to reboot from recovery I got a no OS message. I ignored the message and attempted to reboot. Now the phone doesn't normally power on or off(which may change once the battery dies), no boot animation, no recovery, no fastboot recognition. The computer recognizes the phone as Qualcomm HS-USB QDLoader 9008. I googled for hours last night trying to fix to no avail. Has any of our great devs found a way to atleast recover the bootloader screen. I think I can handle it myself from there with adb.
Solved: Use the first blank flash from the link to get back to bootloader screenhttps://firmware.center/firmware/Motorola/Moto%20Z2%20Force/Blankflash/
From bootloaderscreen put your ADB skills to work. I'm not too good with guides but this just saved me $175

mookiexl said:
I attempted to flash Dirty Unicorn from they're site, which appeared to go well, then I proceeded to flash the TWRPinstaller.zip that was suggested from the maintainer for our device. when I tried to reboot from recovery I got a no OS message. I ignored the message and attempted to reboot. Now the phone doesn't normally power on or off(which may change once the battery dies), no boot animation, no recovery, no fastboot recognition. The computer recognizes the phone as Qualcomm HS-USB QDLoader 9008. I googled for hours last night trying to fix to no avail. Has any of our great devs found a way to atleast recover the bootloader screen. I think I can handle it myself from there with adb.
Click to expand...
Click to collapse
I did the same, got the same. Can't confirm the Qualcomm HS-USB QDLoader 9008 device will be there.
No charge, no screen, does not turn on/off, no vibration. Worst: no bootloader... Again, could be different if the battery dies.
mookiexl said:
Solved: Use the first blank flash to from the link to get back to bootloader screenhttps://firmware.center/firmware/Motorola/Moto%20Z2%20Force/Blankflash/
From bootloaderscreen put your ADB skills to work. I'm not too good with guides but this just saved me $175
Click to expand...
Click to collapse
Three questions:
1. File there is NDX26.183-15_17. Is it the same for OPXS27.109-34-10 on which I'm now? I suppose I need to use the "Oreo" version (2nd file in the list).
2. Which tool/software did you use to flash it? Is there a step by step tutorial?
3. You say "from bootloader screen". What about if we do not have a bootloader screen but a black brick in our hands?

Technical said:
I did the same, got the same. Can't confirm the Qualcomm HS-USB QDLoader 9008 device will be there.
No charge, no screen, does not turn on/off, no vibration. Worst: no bootloader... Again, could be different if the battery dies.
Three questions:
1. File there is NDX26.183-15_17. Is it the same for OPXS27.109-34-10 on which I'm now? I suppose I need to use the "Oreo" version (2nd file in the list).
2. Which tool/software did you use to flash it? Is there a step by step tutorial?
3. You say "from bootloader screen". What about if we do not have a bootloader screen but a black brick in our hands?
Click to expand...
Click to collapse
Answers
1.NDX26.183-15_17 (All it does is get your boatloader screen back
2. If you go to the device menu on your computer and your phone reads as Qualcomm HS-USB QDLoader 9008, all you have to do is click on the Blank flash all file and from the extracted folder and command prompt will do the rest. If the device is not recognized QDLoader 9008 then you will need to download qualcomm drivers to your computer
3.That is exactly what the file is for. Getting your black brick to at least the bootloader screen. From there you can adb recovery or stock rom.
What I ended up doing was adb push the bootable TWRP from the this thread https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932.
Flash the TWRP the official for our device from they're site(the bootable TWRP will give you access to extsd and thats where I had the official TWRP )
Rebooted back to bootloader and adb the firmware files for my device from the AOISP thread and rebooted my phone and I was booting DU.

Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment

Dany XP said:
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Click to expand...
Click to collapse
Before connecting the phone, start the blankflash program. Maybe you have to repeat it a couple of times. Also try different cables, ports and computers.

Dany XP said:
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5

mookiexl said:
Answers
1.NDX26.183-15_17 (All it does is get your boatloader screen back
2. If you go to the device menu on your computer and your phone reads as Qualcomm HS-USB QDLoader 9008, all you have to do is click on the Blank flash all file and from the extracted folder and command prompt will do the rest. If the device is not recognized QDLoader 9008 then you will need to download qualcomm drivers to your computer
3.That is exactly what the file is for. Getting your black brick to at least the bootloader screen. From there you can adb recovery or stock rom.
What I ended up doing was adb push the bootable TWRP from the this thread https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932.
Flash the TWRP the official for our device from they're site(the bootable TWRP will give you access to extsd and thats where I had the official TWRP )
Rebooted back to bootloader and adb the firmware files for my device from the AOISP thread and rebooted my phone and I was booting DU.
Click to expand...
Click to collapse
Can somebody please help me, my laptop isn't even detecting my device as QDLoader 9008, can you please tell me which windows os version did you use, also did you use the usb cable came in the box and did you use usb 2.0 port or 3.0?

LØNEWØLF said:
Can somebody please help me, my laptop isn't even detecting my device as QDLoader 9008, can you please tell me which windows os version did you use, also did you use the usb cable came in the box and did you use usb 2.0 port or 3.0?
Click to expand...
Click to collapse
Well, you need of course, Qualcomm loader driver, to at least having your device recognized as 9008. There u go: https://www.androidbrick.com/download/latest-2017-qualcomm-diag-qd-loader-windows-10-drivers-signed/
After that, go ahead with blankall and stuff...
P.s. and yes ..stay away from USB 3.0! ???

Dany XP said:
Well, you need of course, Qualcomm loader driver, to at least having your device recognized as 9008. There u go:
After that, go ahead with blankall and stuff...
P.s. and yes ..stay away from USB 3.0!
Click to expand...
Click to collapse
Thanks for the reply bro....but I have that driver installed...I installed before connecting it....still not detecting... I'm gonna try this once more in my friend's pc... let's see what happens

LØNEWØLF said:
Thanks for the reply bro....but I have that driver installed...I installed before connecting it....still not detecting... I'm gonna try this once more in my friend's pc... let's see what happens
Click to expand...
Click to collapse
I know it's a long shot but...do u have any other Qualcomm device to try?
U can enter EDL mode with adb command "adb reboot edl". Yes, it's that simple. ?

Dany XP said:
I know it's a long shot but...do u have any other Qualcomm device to try?
U can enter EDL mode with adb command "adb reboot edl". Yes, it's that simple. ?
Click to expand...
Click to collapse
OK I'll try...but how would I get back from edl to Normal without doing anything in the edl?

LØNEWØLF said:
OK I'll try...but how would I get back from edl to Normal without doing anything in the edl?
Click to expand...
Click to collapse
Uh...good question

Oneplus 3 bricked

I bricked my op3 and tried this guide https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/ but at step 5 my phone is not under device manager. Neither unknown device or QHUSB_BULK .

xxxfuq said:
I bricked my op3 and tried this guide https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/ but at step 5 my phone is not under device manager. Neither unknown device or QHUSB_BULK .
Click to expand...
Click to collapse
Can you enter in fastboot mode ? If yes try with command fastboot oem edl
If not you must turn off your phone ( press for 40 seconds power button - yes 40 seconds ) . Then press volume down button and connect your phone with pc . Now if you've installed drivers properly you should be in edl mode and it should show Qualcomm HS-USB QDLoader 9008 in device manager .

mar.ur said:
Can you enter in fastboot mode ? If yes try with command fastboot oem edl
If not you must turn off your phone ( press for 40 seconds power button - yes 40 seconds ) . Then press volume down button and connect your phone with pc . Now if you've installed drivers properly you should be in edl mode and it should show Qualcomm HS-USB QDLoader 9008 in device manager .
Click to expand...
Click to collapse
I cant enter fastmode. I get this but not exactly https://forums.oneplus.com/attachments/img_0387-jpg.452451/
I tried this with volume down but nothing happens in device manager. I installed the qualcomm driver but can you send me other drivers if necessary maybe thats why it wont show.

xxxfuq said:
I cant enter fastmode. I get this but not exactly https://forums.oneplus.com/attachments/img_0387-jpg.452451/
I tried this with volume down but nothing happens in device manager. I installed the qualcomm driver but can you send me other drivers if necessary maybe thats why it wont show.
Click to expand...
Click to collapse
I've installed Qualcomm drivers with miflash . Try this one from zuk z2 pro
https://androidfilehost.com/?fid=24659325368664618
Remember , you must disable drivers verification if you have windows 8 and above

mar.ur said:
I've installed Qualcomm drivers with miflash . Try this one from zuk z2 pro
https://androidfilehost.com/?fid=24659325368664618
Remember , you must disable drivers verification if you have windows 8 and above
Click to expand...
Click to collapse
didnt work

xxxfuq said:
didnt work
Click to expand...
Click to collapse
Did you disable drivers verification before you start install it ? It works on all Qualcomm devices . If you've installed drivers properly it must works. Maybe your phone is not turn off . Try to press power button longer than 40 s .
Edit @xxxfuq Sorry , my fault
Press volume up and connect with pc to enter in edl mode

mar.ur said:
Did you disable drivers verification before you start install it ? It works on all Qualcomm devices . If you've installed drivers properly it must works. Maybe your phone is not turn off . Try to press power button longer than 40 s .
Edit @xxxfuq Sorry , my fault
Press volume up and connect with pc to enter in edl mode
Click to expand...
Click to collapse
Yes i disabled drivers verification. My phone is turned off. I press 10 sec volume up and connect but in device manager my phone wont show.

xxxfuq said:
Yes i disabled drivers verification. My phone is turned off. I press 10 sec volume up and connect but in device manager my phone wont show.
Click to expand...
Click to collapse
Are you sure ? It is under ports ( com & lpt )

mar.ur said:
Are you sure ? It is under ports ( com & lpt )
Click to expand...
Click to collapse
So now I changed the usb hub and it shows now under Qualcomm HS-USB QDLoader 9008 (COM6) but there is a yellow symbol. I tried to update the driver manually with the inf file but it says that the file is damaged.

xxxfuq said:
So now I changed the usb hub and it shows now under Qualcomm HS-USB QDLoader 9008 (COM6) but there is a yellow symbol. I tried to update the driver manually with the inf file but it says that the file is damaged.
Click to expand...
Click to collapse
Hmm, it is diagnostic mode . I usually switch from 900e to 9008 with deepflash cable or with testpoints method . But I don't know if it works with OnePlus 3 .Try to restart phone an pc and repeat all ones again .

mar.ur said:
Hmm, it is diagnostic mode . I usually switch from 900e to 9008 with deepflash cable or with testpoints method . But I don't know if it works with OnePlus 3 .Try to restart phone an pc and repeat all ones again .
Click to expand...
Click to collapse
So finally after many hours I was able to install the driver. Thank you for your help!!

xxxfuq said:
I bricked my op3 and tried this guide https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/ but at step 5 my phone is not under device manager. Neither unknown device or QHUSB_BULK .
Click to expand...
Click to collapse
It means that the proper drivers are not installed. Are you running Win 10?
If you follow that guide and use Method 2, any bricked OP3 can be revived. You may have to repeat some steps till it starts working. I restored mine with the same guide in XDA just three days back. Ensure that you have the latest ADB and other files since some of the files linked in that guide may have become outdated.
Edit: Sorry, didn't notice the subsequent posts.