Develop Bugs

[Q] P350 fastboot bricked

So I used ROMmanager to get clockwork recovery mode. Now when my phone entered the recovery mode it just say:
"Fastboot mode started"
"udc_start()"
If i connect my USB cable to it it says --suspend--
Now i tried using KDZ_FW_UPD in Emergency mode to restore original firmware but it cant find the phone. The log is:
[R&D Test Tools Log File]
10:50:59 : Launching SW update
10:50:59 : Unpacking KDZ
10:51:14 : KDZ file extraced
10:51:17 : Files were extracted.
10:51:17 : LGMobileDL Load.
10:51:17 : Port = -1
10:51:17 : Connecting to phone
10:51:17 : PHONE WAS NOT FOUND!
10:51:19 : ===FINISHED=== ​
I tried this procedure on 2 pcs but no luck. It seems that my phone can't connect to PC with usb cable.
I installed LG Moblie United drivers and disabled the lg modem thing in device manager. I am using Windows xp Proffesional SP3.
So does anyone has any clue what I am doing wrong ? If u need more info just ask.
Maybe if I try from some linux distro it will detect my phone ? But what tools to use then ?

Use fastboot to recover the phone. Check the wiki at the Troubleshooting section.
---------- Post added at 03:31 PM ---------- Previous post was at 03:12 PM ----------
I recommend using drivers latest version. Last time I checked, United Mobile Driver was version 3.7.2 release 4.9.8.1 and Modem Link Driver was 1.0. I'm providing links for download from my personal Dropbox folder because I don't remember from which LG site I downloaded them from.

Vangoda said:
So I used ROMmanager to get clockwork recovery mode. Now when my phone entered the recovery mode it just say:
"Fastboot mode started"
"udc_start()"
If i connect my USB cable to it it says --suspend--
Now i tried using KDZ_FW_UPD in Emergency mode to restore original firmware but it cant find the phone. The log is:
[R&D Test Tools Log File]
10:50:59 : Launching SW update
10:50:59 : Unpacking KDZ
10:51:14 : KDZ file extraced
10:51:17 : Files were extracted.
10:51:17 : LGMobileDL Load.
10:51:17 : Port = -1
10:51:17 : Connecting to phone
10:51:17 : PHONE WAS NOT FOUND!
10:51:19 : ===FINISHED=== ​
I tried this procedure on 2 pcs but no luck. It seems that my phone can't connect to PC with usb cable.
I installed LG Moblie United drivers and disabled the lg modem thing in device manager. I am using Windows xp Proffesional SP3.
So does anyone has any clue what I am doing wrong ? If u need more info just ask.
Maybe if I try from some linux distro it will detect my phone ? But what tools to use then ?
Click to expand...
Click to collapse
i had the same problem few days back... (ROM Manager sucks).... ok.. so.. before connecting the phone to the PC.. remove the battery, press both the volume keys (no need to press the power button)... and connect the usb.. now the cell phone will be in emergency mode.. try launching the software with kdz updater now... it should detect it.. after its detected.. connect back the battery (without disconnecting the USb cord ofcourse)... hope this works.. good luck

Good tip, adding to wiki later...
Sent from my LG-P350 using Tapatalk 2

http://multidroid2.feed.nu/2012/03/27/how-to-unbrickflash-your-optimus-melg-p350-2/

Nothing new to what's already posted in the wiki...

response
madmanzrocks said:
i had the same problem few days back... (ROM Manager sucks).... ok.. so.. before connecting the phone to the PC.. remove the battery, press both the volume keys (no need to press the power button)... and connect the usb.. now the cell phone will be in emergency mode.. try launching the software with kdz updater now... it should detect it.. after its detected.. connect back the battery (without disconnecting the USb cord ofcourse)... hope this works.. good luck
Click to expand...
Click to collapse
Didn't I said i did that ? My PC wont recognize my phone in fastboot or emergency mode, with fastboot being stuck at udc_start() and when i connect USB it says "-- suspend --" ,
I tried this guide madmanzrocks still dont see phone.
deleted lg modem, reinstalled all usb hubs, tried 10 versions of LGunited drivers, used both official update tool and kdz nothing works(can't detect phone), and also tried from cmd.
My problem isn't how to unbrick but rather why my pc won't recognize my phone :/

So, no feedback (USB Device connected sound) when conneting the phone? I assume you have tried all ports available.... Long shot, but maybe the phone's USB connector is dead... You have some background on electronics? If so, you can follow the service manual I reposted recently at the General section to check if the connector is gone (p. 113).

dbarrera said:
So, no feedback (USB Device connected sound) when conneting the phone? I assume you have tried all ports available.... Long shot, but maybe the phone's USB connector is dead... You have some background on electronics? If so, you can follow the service manual I reposted recently at the General section to check if the connector is gone (p. 113).
Click to expand...
Click to collapse
yeah tried all ports, I¨ll try on several other pc's. no connection sound, but phone is charging. I have quite some background on electronics so ill check it out when i try this on couple others pc's. Don't want to dissaemble it quite yet and if it rly is dead repair will probably take more money then i spent to buy it(I got it 2nd hand for around 50 $). It happened before that my PC coudn't recognize some devices but never like this. I ussualy get device not recognized, malfuctioned or smthing like that .

Vangoda said:
yeah tried all ports, I¨ll try on several other pc's. no connection sound, but phone is charging. I have quite some background on electronics so ill check it out when i try this on couple others pc's. Don't want to dissaemble it quite yet and if it rly is dead repair will probably take more money then i spent to buy it(I got it 2nd hand for around 50 $). It happened before that my PC coudn't recognize some devices but never like this. I ussualy get device not recognized, malfuctioned or smthing like that .
Click to expand...
Click to collapse
as I mentioned the same problem was solved bu connecting the cell phone with the battery removed. But if even that doesnt works for you, then maybe there is a fault in your PC. Does your PC instantly recognizes USB Pendrives? And which OS are you using?

madmanzrocks said:
as I mentioned the same problem was solved bu connecting the cell phone with the battery removed. But if even that doesnt works for you, then maybe there is a fault in your PC. Does your PC instantly recognizes USB Pendrives? And which OS are you using?
Click to expand...
Click to collapse
I'm using Windows XP Proffesionall, all the other usb devices at least give a message if my PC can't recognize them. You know that yellow box that pops out saying device malfuctioned or smthing like that.

Hey, i have the same problem, and i also can' t fix it, i tried all ways, but my pc dont detect my phone... so i hope that someone will find a way how to fix it... but it' s not normal what is happening with this phone...

Don't know if it helps or you already tried it.
Start fastboot v2 and start the flash so it waiting for device.
Then plug in usb and start phone in fastboot.
That worked for me before.
Sent from my LG-P350 using xda app-developers app

powerdust said:
Don't know if it helps or you already tried it.
Start fastboot v2 and start the flash so it waiting for device.
Then plug in usb and start phone in fastboot.
That worked for me before.
Sent from my LG-P350 using xda app-developers app
Click to expand...
Click to collapse
Can you please describe step by step, how to do this? maybe it works...

nr4400 said:
Can you please describe step by step, how to do this? maybe it works...
Click to expand...
Click to collapse
I can try.
First start fastboot v2 on your computer.
Load the recoveryimage amonra or cwm5 (not cwm6)
Start flash so it say searching for device.(or something like that)
Plug in usb in computer.
Start your phone in fastboot.
Plug in usb in phone.
If that don't work you can try to instead of start phone first start it with usb cable.
Can need to unplug usb and plug it in a few times if the device say suspend.
Hope it helps.
Sent from my LG-P350 using xda app-developers app

powerdust said:
I can try.
First start fastboot v2 on your computer.
Load the recoveryimage amonra or cwm5 (not cwm6)
Start flash so it say searching for device.(or something like that)
Plug in usb in computer.
Start your phone in fastboot.
Plug in usb in phone.
If that don't work you can try to instead of start phone first start it with usb cable.
Can need to unplug usb and plug it in a few times if the device say suspend.
Hope it helps.
Sent from my LG-P350 using xda app-developers app
Click to expand...
Click to collapse
Can you please add the links to this files or the files? I would be very thanksful...

Up to this point i tried all the methods you guys told me and some i found myself. Nothing worked for me as my PC stil won't recognize my phone, I have also tried all this methods on 4 PCs(2 had windows XP Proffesional SP3 with all the updates, and 2 had Windows 7 SP1 with all the current updates installed(note that 1 version was 32-bit and other was 64-bit).
My conclusion is that the USB connector is DEAD, even thought i can still charge my phone trough it. I probably won't be trying to fix this anymore as I've found an 4th gen iPod and i'll be using that from now on.It is true that i can't make calls(at least not the standard way, you know, it doesn't support SIM cards), but i have my old dumbphone phone for that and this will be used for just about anything else.
So thanks to all of you guys that tried to help me but i fear this is unrepairable. If anyone want's this phone I'll give it to you for free so you can have some fun cracking your head to see what is wrong . I only ask that if you find a way to fix it you post it here and notify me about it(send me pm).Otherwise do whatever you with it.

I have solution
Vangoda said:
So I used ROMmanager to get clockwork recovery mode. Now when my phone entered the recovery mode it just say:
"Fastboot mode started"
"udc_start()"
If i connect my USB cable to it it says --suspend--
Now i tried using KDZ_FW_UPD in Emergency mode to restore original firmware but it cant find the phone. The log is:
[R&D Test Tools Log File]
10:50:59 : Launching SW update
10:50:59 : Unpacking KDZ
10:51:14 : KDZ file extraced
10:51:17 : Files were extracted.
10:51:17 : LGMobileDL Load.
10:51:17 : Port = -1
10:51:17 : Connecting to phone
10:51:17 : PHONE WAS NOT FOUND!
10:51:19 : ===FINISHED=== ​
I tried this procedure on 2 pcs but no luck. It seems that my phone can't connect to PC with usb cable.
I installed LG Moblie United drivers and disabled the lg modem thing in device manager. I am using Windows xp Proffesional SP3.
So does anyone has any clue what I am doing wrong ? If u need more info just ask.
Maybe if I try from some linux distro it will detect my phone ? But what tools to use then ?
Click to expand...
Click to collapse
I had the same problem
1.You must have LG P350 drivers
2.Install KDZ updater
3.Download LG P350 software (I recommend V10c)
Now I will explaine steps
1.You have to charge your battery to 100% (Just leavit on charger in fastboot mode)
2.When you connect your phone to PC hit Start,go on devices and printers and disable USB Modem (Win 7)
3.Take your phone,get the battery out,then hold vol+ and vol- at the same time and plug in USB cable
4.Then you should see cheesy color screen(emergency mode)
5.Put the battery in
6.Open KDZ updater,put Type:3GQCT PhoneMode:Emergency
7.Browse downloaded software in your PC (V10C)
8.Hit ,,Launch software update"
Then just wait max.20min and your phone reboots that is it my fried
If triangle apears on screen just get the battery out and put back in
Let me how it went,or for help on [email protected]

need help
Help pls,i have LG P350 running froyo 2.2.2,and i changed software with KDZ updater to V10c but now i cant reboot in recovery,on the screen appears ,,fastboot mode start",i think i lost recovery image but i dont know hov to install it again on froyo 2.2.2

Masimo x said:
Help pls,i have LG P350 running froyo 2.2.2,and i changed software with KDZ updater to V10c but now i cant reboot in recovery,on the screen appears ,,fastboot mode start",i think i lost recovery image but i dont know hov to install it again on froyo 2.2.2
Click to expand...
Click to collapse
Read the wiki... RTFM!
Sent from my MB525 using Tapatalk 2

How to set device tampered back to false?

I will explain how to set the device tampered back to "false" on the Wileyfox Swift.
Required:
7z
WFS.7z (https://drive.google.com/file/d/0B6Ge199bCD5_NF9RWGhVLVhxajA/view?usp=sharing)
Windows 7 or 8
Driver Signature Enforcement disabled
Step 1: Brick the device on purpose
Hold Volume Up button+Volume Down button while plugging in USB
You should be see QHS_USB BULK in Device Manager
S
Step 2: Install Driver
Reboot with Driver Signature Enforcement disabled ( Google if you must)
Plug device in and make sure you see QHSUSB BULK in Device Manager
If you see Relink HS QDLoader 9008 uninstall it and delete driver software
Then refresh and you should see QHS USB BULK
Manually Update Driver software and navigate to driver folder extracted in WFS.7z
Step 3 : Install QPST provided in WFS.7z
I think its pretty straight forward
Step 4: Flash Firmware
Open QFil
Select Port and choose your device if not already chosen
Select Flat Build
Programmer Path must be prog_emmc_firehose_8916.mbn in the Maincode folder from WFS.7z
Build Path should automatically appear
Hit load XML.
Click rawprogram_upgrade.xml
Click patch0.xml
Click Download
Once done remove and reinsert battery
Step 5: Verify Tampered:False
boot into fastboot
type the following:
fastboot oem device-info
and it should say Device tampered : false and Device Unlock : False
NB: If you get a SaharaDownload fail or something just remove battery and USB for 5 seconds. Plug battery in. Then plug USB in.
NB: I do not accept any responsibility for damaged devices or anything. You point your finger at me and I will laugh at you
If it works don't hesitate to donate me a cup of coffee
PayPal : [email protected]

yasteellutch said:
Step 2: Install Driver
Reboot with Driver Signature Enforcement disabled ( Google if you must)
Plug device in and make sure you see QHSUSB BULK in Device Manager
If you see Relink HS QDLoader 9008 uninstall it and delete driver software
Then refresh and you should see QHS USB BULK
Manually Update Driver software and navigate to driver folder extracted in WFS.7z
Click to expand...
Click to collapse
This does not work for me, no matter wht I try, in the device manager I just get "Android" with a yello triangle.
No manual driver install / update (or update via windows update) solve that problem.
Try it on two Windows 7 PCs (x32 & x64) with Firewall, Antivirus and driver signature are disabled.
On a Windows 10 PC, the device connects as "Marshall London Device".

I don't think ur swift is bricked

when puting battery in jut get the screen "wileyfox"; recovery does not start (vol- and pwr) but fastboot mode ist working (vol+ and pwr). so it's not bricked?
so I repeat step 1 but still in windows 7 device manager having "Other Devices -> Android" with no yellow triangle.

I get SaharaDownload fail. Removing battary is useless. What else can i try? Thanks in advance

Now you get Sahara Fail. I think this is some sort of 'Lock Mode'. I fixed it by removing battery. Reinserting battery and immediately plugging in USB and hitting download

yasteellutch said:
Now you get Sahara Fail. I think this is some sort of 'Lock Mode'. I fixed it by removing battery. Reinserting battery and immediately plugging in USB and hitting download
Click to expand...
Click to collapse
I try and try do it again but i have only got sahara fail again and again.....

void2000 said:
I try and try do it again but i have only got sahara fail again and again.....
Click to expand...
Click to collapse
Upload a screenshot

yasteellutch said:
Upload a screenshot
Click to expand...
Click to collapse
Probably I have to use a special cable?

See it gets the SharaVersion right so I'm guessing that phone is in a correct state. The problem there could be that it didn't decompress properly. Maybe the integrity of your decompressed WFS.7z is not intact. Go to Android One(2nd Gen) dedicated page. I got help there. I guess all you need is to look there.

Maybe u didn't installQPSt right or the driver is a issue. I flashed stock like 3 days ago and it works perfectly

cyaneo said:
This does not work for me, no matter wht I try, in the device manager I just get "Android" with a yello triangle.
No manual driver install / update (or update via windows update) solve that problem.
Try it on two Windows 7 PCs (x32 & x64) with Firewall, Antivirus and driver signature are disabled.
On a Windows 10 PC, the device connects as "Marshall London Device".
Click to expand...
Click to collapse
Hey @cyaneo. If you still have the Yellow Android triangle this is because your drivers aren't installed correctly. I tried it. But that also means your fastboot is working.

Hi all,
Ive been a way from Android for a long time so I'm no expert but the method posted above failed for me. Like others, all my PC would recognise the phone as was "Marshall London Device" and essentially my phone was useless.
Can I ask why we need to erase and/or brick the phone?
Instead what worked for me was to reboot into fastboot mode, download Cyanogen OS signed zip, extract and run flash-radio.sh, then flash recovery and system manually. Reboot phone into working OS and then turn off OEM Unlock.
Once that's done I rebooted into fastboot and confirmed bootloader was locked and that tampered was false (as an official signed OS is installed I take it?).
Anyway as I say, I'm no expert but surely that's an easier and cleaner way than erasing/bricking a phone and only needs fastboot and the latest official signed rom from Cyanogen OS directly?

void2000 said:
Probably I have to use a special cable?
Click to expand...
Click to collapse
Hi,
This is my first post. (active lurker previously) hopefully its not too late.
In my experience on other device running 8916, a sahara failure can be overcame by holding the power button when entering download mode. (E.g: if you enter download mode by pressing and holding vol+/- simultaneously and plugging in usb cable, try holding the power button as well when you plug in the cable). This is normally a result of battery too low.

After bricking my Swift with some gymnastics around Android One firmware images, this tool worked flawlessly!
I was a bit confused when it came to the part of deleting/ manually reinstalling the driver. After the device was shown as "QHS_USB BULK", I manually installed the " Relink HS QDLoader 9008". Everything else went really smoothly. The device is good as new
For the adventurous ones with a Swift- this is one tough little phone. Hard-brick ain't a reason to stop

Pak0St said:
After bricking my Swift with some gymnastics around Android One firmware images, this tool worked flawlessly!
I was a bit confused when it came to the part of deleting/ manually reinstalling the driver. After the device was shown as "QHS_USB BULK", I manually installed the " Relink HS QDLoader 9008". Everything else went really smoothly. The device is good as new
For the adventurous ones with a Swift- this is one tough little phone. Hard-brick ain't a reason to stop
Click to expand...
Click to collapse
Lol I agree. This baby took some hits. I clocked it to 1.6 at stable. At 1.9 she became instable and started crashing #YeahITakeRisks

xfile087 said:
Hi all,
Ive been a way from Android for a long time so I'm no expert but the method posted above failed for me. Like others, all my PC would recognise the phone as was "Marshall London Device" and essentially my phone was useless.
Can I ask why we need to erase and/or brick the phone?
Instead what worked for me was to reboot into fastboot mode, download Cyanogen OS signed zip, extract and run flash-radio.sh, then flash recovery and system manually. Reboot phone into working OS and then turn off OEM Unlock.
Once that's done I rebooted into fastboot and confirmed bootloader was locked and that tampered was false (as an official signed OS is installed I take it?).
Anyway as I say, I'm no expert but surely that's an easier and cleaner way than erasing/bricking a phone and only needs fastboot and the latest official signed rom from Cyanogen OS directly?
Click to expand...
Click to collapse
Of course there is. Don't get me wrong I understand your point. But you need to remember there are log files and a bunch of other stuff lying around if you fastboot. When you use QFil it basically rewrites all the partitions thus no logs. I returned my first Swift with the IMEI issue and they gave me a new one in a week

Hi,
my Swift is also Bricked.... that means no bootloader boot or etc. i tried to flash the phone with this method but no success. my error with QFIL is this
COM Port number:20
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
bei QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
bei QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Click to expand...
Click to collapse
Thanks for response

Error
Download failded
Code:
Dowload fail:House fail failed to Upload the emmc images to phone using firehouse

vadimnew said:
Download failded
Code:
Dowload fail:House fail failed to Upload the emmc images to phone using firehouse
Click to expand...
Click to collapse
You made a mistake @vadimnew

Lumia hard bricked

lumia hard bricked ,i'm connecting to PC ,PC shows unknown device and another time i'm try to connect to PC ,it shows USB device ,PC did't shows qualcomm boot loader,i'm install qualcomm boot loader driver but PC did't recognized my device... please help

more info... which device? did you tried WDRT?

dxdy said:
more info... which device? did you tried WDRT?
Click to expand...
Click to collapse
lumia 820,yes i'm tried WPRT

check this topic, helped me to restore bricked 925
https://forum.xda-developers.com/windows-phone-8/development/help-programmer-unbrick-jtag-t3082592
(btw, i used hex file from lumiafirmware.com)

@Gokul Rajan, sorry for stupid question but have you tried another USB cable and/or another USB port? Also not too bad to give a try on the another PC before starting flashing your handset...

sensboston said:
@Gokul Rajan, sorry for stupid question but have you tried another USB cable and/or another USB port? Also not too bad to give a try on the another PC before starting flashing your handset...
Click to expand...
Click to collapse
i'm tried 4 more laptops and tried different USB cable but every laptops showed That.... any suggestion you have?

What do you do to brick your phone?
Did you tried Windows Phone Internals?

titi66200 said:
What do you do to brick your phone?
Click to expand...
Click to collapse
Yeah, very reasonable question!

titi66200 said:
What do you do to brick your phone?
Did you tried Windows Phone Internals?
Click to expand...
Click to collapse
i'm tried WPinternals, WDRT,some cmd prompt codes , the main problem is PC didn't shows Qualcomm Bootloder

is not need to show qualcomm bootloader (if i remember).. only imported is to not have conflict in drivers
just use tutorial posted in post #4
also in all tutorials say to use "Drivers_X2_Flash_Emergency" but this not helped to me, i used Drivers_Lumia_WP8x_2016-06.7z (from link in tutorial). have Windows 10 x64 PC
for step 2 download files from lumiafirmware.com
also, is little confusing for step 4 converting bin to hex but i downloaded hex file from lumiafirmware.com and worked for lumia 925...
important steps:
-drivers
-WDRT
-HEX.hex and msimage.mbn
- now you use command (put location and real names for hex and mbn file)
thor2 -mode emergency -hexfile HEX.hex -mbnfile msimage.mbn -orig_gpt
- remove battery
- put battery
- connect phone and you must get red screen on phone (this important)
- flash vpl file (enter location and name where vpl and other downloaded ROM files is)
thor2.exe -mode vpl -maxtransfersizekb 1 -vplfile C:\****************
-when done screen must change to green
- use commend
thor2 -mode rnd -bootnormalmode
and thats all

this lumia phones never been hard bricked! you can fix boot loader without battery too thor is best way to fix bootloader....

fullcontrol said:
this lumia phones never been hard bricked! you can fix boot loader without battery too thor is best way to fix bootloader....
Click to expand...
Click to collapse
how to FIX it

fullcontrol said:
this lumia phones never been hard bricked! you can fix boot loader without battery too thor is best way to fix bootloader....
Click to expand...
Click to collapse
need your help , how to fix it??

Gokul Rajan said:
need your help , how to fix it??
Click to expand...
Click to collapse
Find in pcb testpoint or resistor cpu pin# SDC1_CLK first remove battery and usb cable too. short with ground. SDC1_CLK plugin usb cable and battery u will be see in Device Manager QHSUSB_DLOAD. 90008 com device. then leave to short with ground
Next step Folow this link
dxdy said:
check this topic, helped me to restore bricked 925
https://forum.xda-developers.com/windows-phone-8/development/help-programmer-unbrick-jtag-t3082592
(btw, i used hex file from lumiafirmware.com)
Click to expand...
Click to collapse
(if you have recognized QHSUSB_DLOAD. 90008 com device. You can fix boot with WPinternals try with old versions. 1.1 or 1.0 enginering sbl's unlock bootloader method...)
If not help, possible to failure any components in pcb give it to repair service!

fullcontrol said:
Find in pcb testpoint or resistor cpu pin# SDC1_CLK first remove battery and usb cable too. short with ground. SDC1_CLK plugin usb cable and battery u will be see in Device Manager QHSUSB_DLOAD. 90008 com device. then leave to short with ground
Next step Folow this link
(if you have recognized QHSUSB_DLOAD. 90008 com device. You can fix boot with WPinternals try with old versions. 1.1 or 1.0 enginering sbl's unlock bootloader method...)
If not help, possible to failure any components in pcb give it to repair service!
Click to expand...
Click to collapse
Any other sollution???

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.

Invalid IMEI

My Pixel 3 XL shows Invalid IMEI and not connecting to any network? How can I flash the original IMEI...I tried resetting, flashing Stock ROM everything but no luck...I found a method to do it via QPST I have connected my phone with QPST but when I restore QCN file it goes till end but IMEI is still the same.
Also when I try QPST Service programming it gives NV_read_s error

Which mode is your device in when trying to restore your QCN?

Andrologic said:
Which mode is your device in when trying to restore your QCN?
Click to expand...
Click to collapse
Diag

Andrologic said:
Which mode is your device in when trying to restore your QCN?
Click to expand...
Click to collapse
QFIL also detects the Com port and recognizes the phone but when I restore or try to backup QCN file it says "checking if phone is connected" and keep saying until it stops and gives error message while QPST is backing it up fine

Daniyal48 said:
QFIL also detects the Com port and recognizes the phone but when I restore or try to backup QCN file it says "checking if phone is connected" and keep saying until it stops and gives error message while QPST is backing it up fine
Click to expand...
Click to collapse
Strange if your device is confirmed to be in Diag mode (not EDL).

Andrologic said:
Strange if your device is confirmed to be in Diag mode (not EDL).
Click to expand...
Click to collapse
I also tried removing modemst1 and modemdst2 but no luck....am I doing something wrong....what is the proper way to do it via QPST

Daniyal48 said:
I also tried removing modemst1 and modemdst2 but no luck....am I doing something wrong....what is the proper way to do it via QPST
Click to expand...
Click to collapse
Which mode is your device appearing as on your computer? Assume you're using below in QFIL?

Andrologic said:
Which mode is your device appearing as on your computer? Assume you're using below in QFIL?
Click to expand...
Click to collapse
Yes....it is detected as a modem SD845 something ...can the QFIL version be a problem?? I am using the lastest