Database Develop

Repair Corrupted/Invalid IMEI/No Signal

Requirements:
*) Phone with unlocked boot loader.
*) Windows PC (preferable win7)
*) IMEI and S/N writer tool
*) Drivers of CND and our mobile drivers installed
1. EXTRACT IMEI_FILES AND IMEI TOOLS ON THE DESKTOP OF UR PC
2. NOW OPEN IMEI TOOL ( IMEI&SN Writer.exe)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. NOW IN PLATFORM SELECT SMARTPHONE AND SELECT USB (SEE BELOW PLATFORM IN TOOL)
4. IN WRITE TOOL TICK IMEI 1 AND IMEI 2 AND WRITE THERE BOTH UR IMEI
5. NOW CLICK ON SELECT DB AND BROWSE TO THE FOLDER DATABASE AS DIRECTED IN STEP 2
6. SELECT THE FILE WHICH IS IN DATABASE FOLDER AND AGAIN IT ASK U TO SELECT AP FILE
7. THEN SELECT FILE WHICH IS IN AP FOLDER AND CLICK ON START
8. NOW SWITCH OFF UR CELL AND CONNECT
9. NOW GO TO DEVICE MANAGER ( BY RIGHT CLICK ON MY COMPUTER ICON AND CLICK ON PROPERTY ,AFTER OPENING WINDOW CLICK ON DEVICE MANAGER FROM SIDE BAR IN WIN 7 AND ABOVE...
10. AFTER OPENING OF DEVICE MANAGER ,GO TO CDC DRIVER WHICH WILL SHOW RED OR YELLOW CROSS SIGN ,NOW RIGHT CLICK ON AND CLICK ON UPDATE DRIVER .
11. NOW EXTRACT THE CDC DRIVER IN NEW FOLDER ANYWHERE AND BROWSER TO THE CDC DRIVER LOCATION AMD SELECT FOLDER AND CLICK OK TO UPDATE THE CDC DRIVER.. AFTER SUCCESSFULLY DONE
12. AGAIN CLICK ON START AND CONNECT UR PHONE ....MAKE SURE YOU SELECT PROPER COM PORT. CHECK IT IN YOUR DEVICE MANGER. MY COMPUTER-->PROPERTIES-->DEVICE MANAGER-->PORTS AND COMS. NOW IT WILL WRITE IMEI PERMANENTLY
13. AFTER PROCESS FINISH REBOOT AND ENJOY.....
Download All in One Zip
​

Reserved
Sent from my Micromax AQ4501 using XDA Free mobile app

Shrihari007 said:
Requirements:
*) Phone with unlocked boot loader.
*) Windows PC (preferable win7)
*) IMEI and S/N writer tool
*) Drivers of CND and our mobile drivers installed
1. EXTRACT IMEI_FILES AND IMEI TOOLS ON THE DESKTOP OF UR PC
2. NOW OPEN IMEI TOOL ( IMEI&SN Writer.exe)
3. NOW IN PLATFORM SELECT SMARTPHONE AND SELECT USB (SEE BELOW PLATFORM IN TOOL)
4. IN WRITE TOOL TICK IMEI 1 AND IMEI 2 AND WRITE THERE BOTH UR IMEI
5. NOW CLICK ON SELECT DB AND BROWSE TO THE FOLDER DATABASE AS DIRECTED IN STEP 2
6. SELECT THE FILE WHICH IS IN DATABASE FOLDER AND AGAIN IT ASK U TO SELECT AP FILE
7. THEN SELECT FILE WHICH IS IN AP FOLDER AND CLICK ON START
8. NOW SWITCH OFF UR CELL AND CONNECT
9. NOW GO TO DEVICE MANAGER ( BY RIGHT CLICK ON MY COMPUTER ICON AND CLICK ON PROPERTY ,AFTER OPENING WINDOW CLICK ON DEVICE MANAGER FROM SIDE BAR IN WIN 7 AND ABOVE...
10. AFTER OPENING OF DEVICE MANAGER ,GO TO CDC DRIVER WHICH WILL SHOW RED OR YELLOW CROSS SIGN ,NOW RIGHT CLICK ON AND CLICK ON UPDATE DRIVER .
11. NOW EXTRACT THE CDC DRIVER IN NEW FOLDER ANYWHERE AND BROWSER TO THE CDC DRIVER LOCATION AMD SELECT FOLDER AND CLICK OK TO UPDATE THE CDC DRIVER.. AFTER SUCCESSFULLY DONE
12. AGAIN CLICK ON START AND CONNECT UR PHONE ....MAKE SURE YOU SELECT PROPER COM PORT. CHECK IT IN YOUR DEVICE MANGER. MY COMPUTER-->PROPERTIES-->DEVICE MANAGER-->PORTS AND COMS. NOW IT WILL WRITE IMEI PERMANENTLY
13. AFTER PROCESS FINISH REBOOT AND ENJOY.....
Download All in One Zip
​
Click to expand...
Click to collapse
What's CND
Sent from my A1 using XDA Free mobile app

Error while installing Cds Drivers
Error = the third party INS does not contain digital signatures or something like that Plz help OS = 8.1

For windows 8.1/8.1 Disable driver signature enforcement checking....
How to here :
https://learn.sparkfun.com/tutorial...abling-signed-driver-enforcement-on-windows-8

Now on Window 7 it says enter meta mode failed
Hi
i Switched form 8.1 to window 7:crying: just for this method but in window 7 i installed every driver but when i connect my device the imei writter says enter meta mode failed:crying::crying::crying::crying::crying: and there is mmx logo on my A1
what to do bro guid plz!

Select correct com port
Sent from my Micromax AQ4501 using XDA Free mobile app

Code:
Steps:
1,Please power off the phone
2,Then plug in the USB cable
USB Bootup
Meta_DB Init Start:
Meta_DB Init PASS
Enter to ModemMeta Start:
Enter to ModemMeta Fail:
It is over !!
Error Message : Falied to enter meta mode.
Other than that CDC driver does not show up in the device manager either.
Any help please?

Please Help Mine Same Problem
mine too same problem what can i do
if you"ve fixed this problem plz tell me please help..!!!!!!!! I Am ****ed Up
PLEASE HELP................!!!!!!!!!!!!!!!!!!!!!!!!!!
please.!!!! reply:crying::crying::crying::crying:
:crying::crying:
Saatvik Shukla said:
Code:
Steps:
1,Please power off the phone
2,Then plug in the USB cable
USB Bootup
Meta_DB Init Start:
Meta_DB Init PASS
Enter to ModemMeta Start:
Enter to ModemMeta Fail:
It is over !!
Error Message : Falied to enter meta mode.
Other than that CDC driver does not show up in the device manager either.
Any help please?
Click to expand...
Click to collapse

Me too had same problem..... All you need to do is select proper com port
Sent from my Micromax AQ4501 using XDA Free mobile app

Shrihari007 said:
Requirements:
*) Phone with unlocked boot loader.
*) Windows PC (preferable win7)
*) IMEI and S/N writer tool
*) Drivers of CND and our mobile drivers installed
1. EXTRACT IMEI_FILES AND IMEI TOOLS ON THE DESKTOP OF UR PC
2. NOW OPEN IMEI TOOL ( IMEI&SN Writer.exe)
3. NOW IN PLATFORM SELECT SMARTPHONE AND SELECT USB (SEE BELOW PLATFORM IN TOOL)
4. IN WRITE TOOL TICK IMEI 1 AND IMEI 2 AND WRITE THERE BOTH UR IMEI
5. NOW CLICK ON SELECT DB AND BROWSE TO THE FOLDER DATABASE AS DIRECTED IN STEP 2
6. SELECT THE FILE WHICH IS IN DATABASE FOLDER AND AGAIN IT ASK U TO SELECT AP FILE
7. THEN SELECT FILE WHICH IS IN AP FOLDER AND CLICK ON START
8. NOW SWITCH OFF UR CELL AND CONNECT
9. NOW GO TO DEVICE MANAGER ( BY RIGHT CLICK ON MY COMPUTER ICON AND CLICK ON PROPERTY ,AFTER OPENING WINDOW CLICK ON DEVICE MANAGER FROM SIDE BAR IN WIN 7 AND ABOVE...
10. AFTER OPENING OF DEVICE MANAGER ,GO TO CDC DRIVER WHICH WILL SHOW RED OR YELLOW CROSS SIGN ,NOW RIGHT CLICK ON AND CLICK ON UPDATE DRIVER .
11. NOW EXTRACT THE CDC DRIVER IN NEW FOLDER ANYWHERE AND BROWSER TO THE CDC DRIVER LOCATION AMD SELECT FOLDER AND CLICK OK TO UPDATE THE CDC DRIVER.. AFTER SUCCESSFULLY DONE
12. AGAIN CLICK ON START AND CONNECT UR PHONE ....MAKE SURE YOU SELECT PROPER COM PORT. CHECK IT IN YOUR DEVICE MANGER. MY COMPUTER-->PROPERTIES-->DEVICE MANAGER-->PORTS AND COMS. NOW IT WILL WRITE IMEI PERMANENTLY
13. AFTER PROCESS FINISH REBOOT AND ENJOY.....
Download All in One Zip
​
Click to expand...
Click to collapse
whether it can be done to overcome Invalid IMEI on Samsung Galaxy Note 2, bro?

No its only for mediatek devices

what are the ways that a imei number can get damaged?
hi all.
just asking this question to take care of not to do such things.
how can a imei number get damaged?

How to?? How to select proper driver
And How TO Do That?? please Explain i am in big trouble
Shrihari007 said:
Me too had same problem..... All you need to do is select proper com port
Sent from my Micromax AQ4501 using XDA Free mobile app
Click to expand...
Click to collapse

Does this work on every android phone?
Mine is galaxy note 10.1 n8000, with gnabo rom 4.4.2 running on it.
Sent from my Xperia Acro S using Tapatalk

Araragi said:
Does this work on every android phone? Mine is galaxy note 10.1 n8000, with gnabo rom 4.4.2 running on it.
Click to expand...
Click to collapse
the answer is here.

why he is not replying????
I am in invalid imei
Why the thread maker is not replying instead you check this video on YouTube for repair the another way
https://youtu.be/8DT-32tPbMY
Sagar Kapasi said:
And How TO Do That?? please Explain i am in big trouble
Click to expand...
Click to collapse

Enter to ModemMeta Fail
Now what to Do ? I install the CDC Driver but it still says failed to enter meta mode ? i am on win7 32bit! is this only for 64 bit ?
I have lost my imei, wifi Mac Address, and Serial Number ?
I am in a Big Trouble ...PLZ help me!

srikantrn said:
Enter to ModemMeta Fail
Now what to Do ? I install the CDC Driver but it still says failed to enter meta mode ? i am on win7 32bit! is this only for 64 bit ?
I have lost my imei, wifi Mac Address, and Serial Number ?
I am in a Big Trouble ...PLZ help me!
Click to expand...
Click to collapse
Read the thread carefully!

Flash the stock ROM via SP flash tools.
Sent from my Sparkle V

Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Driver install tutorial M2

Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Driver install tutorial
To determine the version of Windows 10 that you have (32 bit or 64 bit):
- Right-click on Start then click on System
- In the System window that opens, in System section, you will find your version of Windows next to System type
To disable Windows 10 64 bit driver signature enforcement:
- On your 64 bit Windows 10 desktop click on Start then on Settings
- Click on Update & security then in the left pane click on Recovery
- Under Advanced startup click on Restart now button
- Click on Troubleshoot then on Advanced options
- Click on Startup Settings then on Restart button
- The computer will restart with the Startup Settings screen
- To disable the driver signature enforcement until next restart press on number key 7 or F7 on your keyboard.
- After restart you can proceed with the unsigned MTK drivers installation for your 64 bit Windows
- After you install the unsigned drivers, to use them again in the future, you have to repeat this procedure
To install the MTK VCOM USB Drivers on 32 & 64 bit Windows 10:
- Download the drivers *.zip archive and extract the folder from inside on to the desktop:
https://www.androidfilehost.com/?fid=24269982087012126
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Right-click on Start then click on Device Manager
In the Device Manager Window click on the first item – your computer name
Click on Action then Add legacy hardware
On the Welcome to the Add hardware Wizard window click on Next button
Select Install the hardware that I manually select from a list (Advanced) and then click on Next button
Click on Show All Devices then on Next button
In the Add Hardware window click on Have Disk… button
In the Install From Disk windows click on Browse… button
In the next window – Locate file – browse for the folder that you have extracted on the desktop at the beginning
Select the version of the driver according to your Windows 10 version – x64 for 64 bit and x86 for 32 bit and click Open button
Click the OK button to load the driver
From the list of drivers select MTK USB Port and click on Next button
If a red warning window will open, click on Install this driver software anyway
This action will add the following drivers in to the operating system:
- MediaTek DA USB VCOM Port
- MediaTek PreLoader USB VCOM Port – for transferring the firmware to your device
- MTK USB DEBUG Port
- MTK USB Modem Port
- MTK USB port – for transfering PreLoader to your device (and recovery in case of bad or corrupt firmware)
Now we need to remove the device that we have installed but leave the drivers in the operating system.
To do that, in the Device Manager window we expand Ports (COM & LPT) section
Right-click and click Uninstall on the MTK USB Port
- In the Confirm Device Uninstall window make sure that the box Delete the driver software for this device is empty
- You need to leave the drivers in the operating system and only remove the device that you added
- Click on the OK button to finalise
Now, when you will connect your turned off MTK device to the Windows 10 computer by USB, the device will be recognized either trough a MediaTek Preloader USB VCOM Port interface or as a MTK USB port if it is bricked or it has bad/corrupt firmware. The SP Flash Tool will be able to transfer the firmware to your device trough this interfaces. Make sure you connect the device after you press the Download button in SP Flash Tool, as the communication interface will only be alive for 2 seconds if no data is being sent.
Download SP Flash Tool v3 & v5 – Latest versions:
http://laurentiumihet.ro/technology/download-sp-flash-tool-v3-v5-latest-versions/
TUT found here : http://laurentiumihet.ro/technology...-for-32-64-bit-drivers-installation-tutorial/
cheers​

Hi, in my computer doesn´t appears the red window. Are you know Why?

amilcar50 said:
Hi, in my computer doesn´t appears the red window. Are you know Why?
Click to expand...
Click to collapse
You used win7/8? If yes its normal.
If win10. Then you have luck
Gesendet von meinem Elephone P8000 mit Tapatalk

I use Windows 10 64 bits

hi mate , in win10 64bit it says "error does not contain digital signature information"
edit: i installed with digital signature disable in win 10

lost3 said:
hi mate , in win10 64bit it says "error does not contain digital signature information"
Click to expand...
Click to collapse
It happens to me too . once.
I did it with that
http://bbs.elephone.hk/thread-1037-1-1.html#.VWgkX_RAU-0
Take the drivers from there and make it the dirty way.
It will say signature fails.. Then look into c:/windows/program/ mtk drivers or mediatek folder.
Open the device manager and plug in the phone.
You will see a new USB connection. Klick there and install the drivers from the folder above. .
I did it 2 times. Then it works on win10 64bit
Gesendet von meinem Elephone P8000 mit Tapatalk

now we can solve LeTv Le 1s Bootloop Issue on windows 10
thanks alot now we can solve LeTv Le 1s Bootloop Issue on windows 10 .. :happytears:

What should I do when "Eror code 10: device can't start" popped up? Thanx.

all steps done still not detecting my phone
pls help...

ghanta said:
all steps done still not detecting my phone
pls help...
Click to expand...
Click to collapse
Restore the imei manual
.try this
http://forum.xda-developers.com/elephone-p8000/help/wrong-imei-t3187059
Gesendet von meinem Elephone P8000 mit Tapatalk

skeleton1911 said:
Restore the imei manual
.try this
http://forum.xda-developers.com/elephone-p8000/help/wrong-imei-t3187059
Gesendet von meinem Elephone P8000 mit Tapatalk
Click to expand...
Click to collapse
Sorry but did not understand what are you referring to?

saved my bricked Lenovo A296i
Updated the firmware(Android 2.3.6) of my phone successfully after researching for almost 26 hours. My phone got bricked after I accidentally deleted google services framework, it stuck on the startup logo. I tried to flash the stock rom from sd card but the message was"E: Signature verification failed, installation aborted". then I used SP flash tool and stock rom "Lenovo_A269i_2.3.6_(by_xdafirmware.com).zip" and followed this thread and was finally able to unbrick my phone after updating the firmware. thanks guys:good::good::good::good::good::good:

I tried this method but my lenovo vibe X2 is still nog recognised.
My computer keeps giving an error code 43 (A request for the USB device descriptor failed.)
Does anyone have an idea what to do?

I own Doogee F5. It is bricked.
I used your routine but at the end F5 is not recognized by the PC and Flash Toll does not work.

Would this be any use for a UMI Super? I'm running 32bit windows 10 build 10586 and need a driver to be able to use spflash tool to flash TWRP. Will this driver work?

When plugging in the phone while turned off, the phone is only recognized for 2 seconds and SP Flashtool doesn't seem to be starting the download fast enough to catch on. Does anyone know how to solve the issue?

pohlipit said:
When plugging in the phone while turned off, the phone is only recognized for 2 seconds and SP Flashtool doesn't seem to be starting the download fast enough to catch on. Does anyone know how to solve the issue?
Click to expand...
Click to collapse
Normal. Klick download in flash tools then connect the phone while holding vol+
Gesendet von meinem P9000 mit Tapatalk

Windows 7
Bonjour,
connaissez vous un lien pour un pilote windows 7 pour MTK VCOM USB Drivers for 32 & 64 bit ?
par avance merci
Claude

In my case it's about a smartwatch, the DZ09. I followed the tutorial step by step and it does not work. Everything goes fine but when I connect my device (powered off, of course) it plugs and unplugs (that's what the Windows sound reports) constantly, like a couple of times, and then starts to charge battery (which I guess it shouldn't).
Any ideas? Thank you <3 ((((((((

Andreuu_u said:
In my case it's about a smartwatch, the DZ09. I followed the tutorial step by step and it does not work. Everything goes fine but when I connect my device (powered off, of course) it plugs and unplugs (that's what the Windows sound reports) constantly, like a couple of times, and then starts to charge battery (which I guess it shouldn't).
Any ideas? Thank you <3 ((((((((
Click to expand...
Click to collapse
Hold vol+ while you plug it in
Gesendet von meinem Metal mit Tapatalk

Brick nubia z9 mini

Hello guys, I hard brick my nubia z9 mini (chineese version). The phone is not responding to anything (power button press at the same time that volume +, I can't disconnect the battery cause it is screwed inside and I don't have tools to unscrewed it). Pc recognize the phone as Qualcomm HS-USB QDLoader 9008 (COM4) so I think it still as a chance to recovery but I don't know how, I've already try a few stuff:
- QFIL : but it was a problem about Sahara that failed
- ZTEMT ToolStudio(Common) 4.4.58 : but in ComPorts the qualcomm thing is there but not when I go to eMMCDownload, nothing appear
- nubia recovery tool : but recovery work once and then it failed (the phone still not gave any sign of life)
I've installed drivers for qualcomm devices version 2.0.8.7
I'm a little noob in this field so I'm pretty sure you can help me because I don't understand everything in all those stuff, please help me !
Thank you already

Unbrick your Nubia Z9 mini using "Nubia Toolstudio V 4.6.90."
Step 1: Connect your phone with Your Computer PC in "Qualcomm HS-USB QDLoader 9008" mode by pressing volume -,+ and power buttons, press all three buttons Simultaneously for 15 sec. (Note: Driver need for PC for connection, I used Nubia emergency tool 1.0.6 for driver purpose, don't use it for recovery purpose.)
ttps://drive.google.com/open?id=0B8joXHOIogfeOUVJanpnN1I0UjQ (Download All software From this given link, In this link "https"---"h" is missing, add by ur self)
Step 2: Install "Nubia Tool Studio V.4.6.90" in Your PC.
Step 3 : Open Nubia Tool Studio, Select model "NX511J" and "Firehouse Download" in menu list, click referesh button, it will shows connected port.
Step 4: Extract the firmware that you have downloaded, and shows the file path of Firmware folder. (Use any one Firmware file "Z9(Mini)_NX511J_XVV" or "Z9(Mini)_NX511J_XVV2".)
Step 5: Click "Start" button, it will start download to your phone's emmc. After completing download 100%, your phone automatically restart to normal, and you will be happy:laugh:

[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 5

Hello Everyone !!​
=>A hard bricked OP5 has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition (It might be a flickering OnePlus logo). The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OP5 should be detected as QHUSB_BULK,Unknown Device,Qualcomm something. You might have a bricked OP5 as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition. Most of the times, it is needed because OEM Unlocking is disabled, and phone can't boot and no recovery.
=>The solution for OP5 hardbrick is similar to OP3,OP3T- you just need a Qualcomm driver and a recovery package.it'll help to get out from one of the most weird state of the phone.(file is exact file from OnePlus)
METHOD​
This method is easy to use and flashes OxygenOS 4.5.10 on your phone. It wipes all your data and restores all partitions to stock. It will work in any condition unless it is a hardware damage.
Step 1 :- DOWNLOADS :- https://drive.google.com/drive/folders/0B7PMif5jp70BRmpSX1Nzb2JhRGs?usp=sharing
Step 2 :- Extract Drivers and Recovery Tool files on Desktop.
Step 3 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 6 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices.If you are unable to see 9008,see the end of post for various other methods to show Qualcomm 9008.
Step 7 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 8 :- Click start at top left corner and wait for it to finish (green text will come).
Step 9 :- Disconnect phone from PC and boot into system.
How to Make the device show as Qualcomm 9008​
1.) Make sure driver signature enforcement is disabled.
2.) Try these drivers,one of them might work too :-
https://www.androidfilehost.com/?fid=24052804347799753
https://www.androidfilehost.com/?fid=24269982086990168
https://www.androidfilehost.com/?fid=24349802275800175
https://www.androidfilehost.com/?fid=24349802275800173
https://www.androidfilehost.com/?fid=24349802275800171
3.)Download this :- http://www.mediafire.com/download/4a...6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
Click thanks IF i helped you

reserved

@vasu97
We already have a dedicated thread on the same topic.

what can i edit so it won't relock the bootloader? or does it relock it?

vasu97 said:
Hello Everyone !!​
=>A hard bricked OP5 has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition (It might be a flickering OnePlus logo). The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OP5 should be detected as QHUSB_BULK,Unknown Device,Qualcomm something. You might have a bricked OP5 as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition. Most of the times, it is needed because OEM Unlocking is disabled, and phone can't boot and no recovery.
=>The solution for OP5 hardbrick is similar to OP3,OP3T- you just need a Qualcomm driver and a recovery package.it'll help to get out from one of the most weird state of the phone.(file is exact file from OnePlus)
METHOD​
This method is easy to use and flashes OxygenOS 4.5.10 on your phone. It wipes all your data and restores all partitions to stock. It will work in any condition unless it is a hardware damage.
Step 1 :- DOWNLOADS :- https://drive.google.com/drive/folders/0B7PMif5jp70BRmpSX1Nzb2JhRGs?usp=sharing
Step 2 :- Extract Drivers and Recovery Tool files on Desktop.
Step 3 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 6 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices.If you are unable to see 9008,see the end of post for various other methods to show Qualcomm 9008.
Step 7 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 8 :- Click start at top left corner and wait for it to finish (green text will come).
Step 9 :- Disconnect phone from PC and boot into system.
How to Make the device show as Qualcomm 9008​
1.) Make sure driver signature enforcement is disabled.
2.) Try these drivers,one of them might work too :-
https://www.androidfilehost.com/?fid=24052804347799753
https://www.androidfilehost.com/?fid=24269982086990168
https://www.androidfilehost.com/?fid=24349802275800175
https://www.androidfilehost.com/?fid=24349802275800173
https://www.androidfilehost.com/?fid=24349802275800171
3.)Download this :- http://www.mediafire.com/download/4a...6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
Click thanks IF i helped you
Click to expand...
Click to collapse
Holy crap! I literally spent the last 12 hours trying to get my phone fixed. This was the only solution. Thank you so much!!!

If anyone had problems with the MSM tool "Sahara communication failed," unplug your phone. Turn it off by holding the power button for a while. Hold the power up for 10 seconds, then keep holding the volume up and plug your phone in to the PC. The MSM tool should automatically detect and restore your phone.

vasu97 said:
reserved
Click to expand...
Click to collapse
thank you so much

I've tried all the steps on multiple ports and different computers but I got always the errno 258 while loading the cache.img. Don't know what else to do...

Which Qualcomm interface driver for download mode?

Hi all!
I am trying to flash QFIL file to my Nokia 7 plus (TA-1046), but with no success because the Qualcomm driver is not installed automatically.
I have the 1.0 Qualcomm driver collection installed, but when I plugin my phone in download mode, I see it appear in device manager under "other devices" as "Android". I can update the driver to any other Qualcomm driver, but I don't know which one to choose. I tried the "QDLoader 9008" and it installs fine, but in QFIL.exe I can't flash my phone. I still get sahara errors.
What driver (type number) do I need to install to connect my phone's interface (download mode)?
EDIT:
Forgot to mention the obvious, it's Windows 7...

sbsoft said:
Hi all!
I am trying to flash QFIL file to my Nokia 7 plus (TA-1046), but with no success because the Qualcomm driver is not installed automatically.
I have the 1.0 Qualcomm driver collection installed, but when I plugin my phone in download mode, I see it appear in device manager under "other devices" as "Android". I can update the driver to any other Qualcomm driver, but I don't know which one to choose. I tried the "QDLoader 9008" and it installs fine, but in QFIL.exe I can't flash my phone. I still get sahara errors.
What driver (type number) do I need to install to connect my phone's interface (download mode)?
EDIT:
Forgot to mention the obvious, it's Windows 7...
Click to expand...
Click to collapse
When you install QPST Too,l all qualcomm drivers are installed to your pc. if your device is not detected by your pc try restarting your pc. if restart not working the. open device manager and search for unknown device then install driver manually.

sarath medithi said:
When you install QPST Too,l all qualcomm drivers are installed to your pc. if your device is not detected by your pc try restarting your pc. if restart not working the. open device manager and search for unknown device then install driver manually.
Click to expand...
Click to collapse
Thanks for your reply!
I did all you said (incl installing QPST tool), but still see "Android" under "Unknown devices". It is not recognized at all by Windows.
I want to install manually, but don't know which driver to choose from. I see a list of about 50 Qualcomm port drivers (MSM xxxx, QDLoader xxxx, Diagnostics xxxx), so which one is the correct one? What do you see under your "Ports (COM and LPT)" in device manager when you connect your phone in download mode?

QFIL Flashing Procedure
sbsoft said:
Thanks for your reply!
I did all you said (incl installing QPST tool), but still see "Android" under "Unknown devices". It is not recognized at all by Windows.
I want to install manually, but don't know which driver to choose from. I see a list of about 50 Qualcomm port drivers (MSM xxxx, QDLoader xxxx, Diagnostics xxxx), so which one is the correct one? What do you see under your "Ports (COM and LPT)" in device manager when you connect your phone in download mode?
Click to expand...
Click to collapse
Please confirm your qfil version.
Tool frome here:
https://aiomobilestuff.com/download-...st-flash-tool/
Drivers from here:
http://www.mediafire.com/file/j3g88d...r+V1.1.0.0.rar
Steps to flash the phone
Step1: To use QPST, some drivers need to be installed on your Computer.
Note: While installing driver avoid using cable for successful installation.
When Drivers installed, Attach Phone to PC via USB cable.
While connecting to PC, phone should be switched off and press volume up & down as boot key.
If it Create Qualcomm HS-USB QDLoader 9008 port in device manager , then driver has been successfully installed.
Once driver installation is complete, follow the instructions below to flash the MBN firmware file to your Qualcomm device.
Step 2. Make sure your device is charged to at least 30%.
Step 3. Run QFIL tool.
Step 4. Now Browse under the Programmer path to Chose the B2N-0-132E-prog_emmc_ufs_firehose_Sdm660_ddr.elf File.
Step 5. As soon as the elf file is selected, Select Build will automatically select the Update or Stock ROM.
Step 6. Next Go To Load XML, selectB2N-0-132E-rawprogram0.xml and Select B2N-0-132E-patch0.xml
Step 7. Turn off the Phone and Attach it to PC by pressing Vol up & down button.
Step 8. Click on Select Port and choose the port.
Step 9. Click on Download to start flashing.
Step 10. Disconnect device from USB cable once Finish Download appears.
That’s all!
Hit thanks button if you find this helpful
Happy flashing
Note: If you get the Sahara Errors Place Firmware folder in QFIL\Bin folder. Check whether programmer file is available in your firmware folder. It is an elf file (B2N-0-132E-prog_emmc_ufs_firehose_Sdm660_ddr.elf). Use recent version of QPST. earler versions cant flash .elf programmers.

sarath medithi said:
Please confirm your qfil version.
Tool frome here:
https://aiomobilestuff.com/download-...st-flash-tool/
Drivers from here:
http://www.mediafire.com/file/j3g88d...r+V1.1.0.0.rar
Steps to flash the phone
Step1: To use QPST, some drivers need to be installed on your Computer.
Note: While installing driver avoid using cable for successful installation.
When Drivers installed, Attach Phone to PC via USB cable.
While connecting to PC, phone should be switched off and press volume up & down as boot key.
If it Create Qualcomm HS-USB QDLoader 9008 port in device manager , then driver has been successfully installed.
Once driver installation is complete, follow the instructions below to flash the MBN firmware file to your Qualcomm device.
Step 2. Make sure your device is charged to at least 30%.
Step 3. Run QFIL tool.
Step 4. Now Browse under the Programmer path to Chose the B2N-0-132E-prog_emmc_ufs_firehose_Sdm660_ddr.elf File.
Step 5. As soon as the elf file is selected, Select Build will automatically select the Update or Stock ROM.
Step 6. Next Go To Load XML, selectB2N-0-132E-rawprogram0.xml and Select B2N-0-132E-patch0.xml
Step 7. Turn off the Phone and Attach it to PC by pressing Vol up & down button.
Step 8. Click on Select Port and choose the port.
Step 9. Click on Download to start flashing.
Step 10. Disconnect device from USB cable once Finish Download appears.
That’s all!
Hit thanks button if you find this helpful
Happy flashing
Note: If you get the Sahara Errors Place Firmware folder in QFIL\Bin folder. Check whether programmer file is available in your firmware folder. It is an elf file (B2N-0-132E-prog_emmc_ufs_firehose_Sdm660_ddr.elf). Use recent version of QPST. earler versions cant flash .elf programmers.
Click to expand...
Click to collapse
Thanks for your replay!
I did all you said and I think the driver is now installed correctly. Only problem that remains is the locked bootloader, which is preventing flashing.
I have tried to disable it by "fastboot oem unlock", but no success, because access is denied. (I have enabled OEM unlock in dev options).
QFIL keeps reporting me "100 Unable to connect to port". Sahara is not an issue anymore (I guess).
Do I really need to unlock bootloader to flash the elf?
EDIT: I've read another article on XDA that states that Nokia devices cannot be flashed???

sbsoft said:
Thanks for your replay!
I did all you said and I think the driver is now installed correctly. Only problem that remains is the locked bootloader, which is preventing flashing.
I have tried to disable it by "fastboot oem unlock", but no success, because access is denied. (I have enabled OEM unlock in dev options).
QFIL keeps reporting me "100 Unable to connect to port". Sahara is not an issue anymore (I guess).
Do I really need to unlock bootloader to flash the elf?
EDIT: I've read another article on XDA that states that Nokia devices cannot be flashed???
Click to expand...
Click to collapse
QFIL don't need unlocked bootloader as it uses EDL Mode for flashing. I suggest you to change the usb port and try with another data cable.
---------- Post added at 12:13 PM ---------- Previous post was at 12:12 PM ----------
sbsoft said:
Thanks for your replay!
I did all you said and I think the driver is now installed correctly. Only problem that remains is the locked bootloader, which is preventing flashing.
I have tried to disable it by "fastboot oem unlock", but no success, because access is denied. (I have enabled OEM unlock in dev options).
QFIL keeps reporting me "100 Unable to connect to port". Sahara is not an issue anymore (I guess).
Do I really need to unlock bootloader to flash the elf?
EDIT: I've read another article on XDA that states that Nokia devices cannot be flashed???
Click to expand...
Click to collapse
can you share the qfil log or screenshot

sarath medithi said:
QFIL don't need unlocked bootloader as it uses EDL Mode for flashing. I suggest you to change the usb port and try with another data cable.
---------- Post added at 12:13 PM ---------- Previous post was at 12:12 PM ----------
can you share the qfil log or screenshot
Click to expand...
Click to collapse
Here we go:
(I have Dutch language version of Windows 7, so no English in some pictures)
1. The driver is installed correctly and working fine. (I need to boot Windows in testsigning mode with no driver signature checking, because the driver is not signed correctly?)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Phone is in Download mode.
When I click Download in QFIL, this is the output and nothing happens.
The configuration of QFIL looks like this:
Is this enough for you? If not, please let me know. I am starting to get headaches of this problem...
Thanks!

sbsoft said:
Here we go:
(I have Dutch language version of Windows 7, so no English in some pictures)
1. The driver is installed correctly and working fine. (I need to boot Windows in testsigning mode with no driver signature checking, because the driver is not signed correctly?)
Phone is in Download mode.
When I click Download in QFIL, this is the output and nothing happens.
The configuration of QFIL looks like this:
Is this enough for you? If not, please let me know. I am starting to get headaches of this problem...
Thanks!
Click to expand...
Click to collapse
Try to update your QFIL.i think there is a new version available. update it and try again. may be it is giving an error due to the programmer file which is an elf file. earlier it is .mbn or .bin file. hope you understand.

Did you succede in using QFIL ? @sbsoft