Database Users

Bricked OP2 after flashing Nexus Stock ROM

Bricked OP2 ...
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance

If you flashed a ROM that's not for you're phone you're more than likely screwed

Could you try the following:
1, plug the phone back in recovery/fastboot mode
2, Open Computer Management and delete the drivers the OS finds for the phone
3, Download the ADB driver tool from here: http://forum.xda-developers.com/showthread.php?t=2588979
Try follow the steps and let me know if u get the drivers needed for the recovery
If the tool on the above link dont work, try this one: http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi

Bhups said:
Could you try the following:
1, plug the phone back in recovery/fastboot mode
2, Open Computer Management and delete the drivers the OS finds for the phone
3, Download the ADB driver tool from here: http://forum.xda-developers.com/showthread.php?t=2588979
Try follow the steps and let me know if u get the drivers needed for the recovery
If the tool on the above link dont work, try this one: http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Click to expand...
Click to collapse
Thank you for your response, the issue is that it's hard bricked, so no recovery mode no led , nothing ..
i uninstalled the drivers ( even that i had the adb working before ) and the device is detectable now only with as QHSUSB_BULK
the installation of any adb usb driver don't change anything, only qualcomm usb drivers work ( i have the 9008 only but i'm think it's not compatible with OP2) i could manually change it to adb ( mobistel Cynus f4 ADB interface ) but nothing new..
Help plz
thanks again

mG!X said:
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance
Click to expand...
Click to collapse
Two problems here. The first problem is that you didn't wipe properly when flashing Nethunter, that's why you ended up with Nethunter apps on your stock ROM. When flashing a ROM you must perform a full wipe, this consists of system, data, cache, and dalvik cache. This isn't what bricked your phone though. We know what bricked your phone; flashing a ROM for a completely different device. I'm not sure why you would flash a ROM from another device, maybe due to inexperience, but that's the last thing you should be doing, as you now know. Don't use the recovery tool that you have, it isn't for your chipset, it will only make matters worse. I honestly don't think there's any way to revive your device, you've pretty much rendered it useless. I'd strongly suggest you do a lot of research before deciding to mess with another phone, if you don't know what you're doing then don't do it. Venturing into unknown lands like this only ever ends in disaster.

Heisenberg said:
Two problems here. The first problem is that you didn't wipe properly when flashing Nethunter, that's why you ended up with Nethunter apps on your stock ROM. When flashing a ROM you must perform a full wipe, this consists of system, data, cache, and dalvik cache. This isn't what bricked your phone though. We know what bricked your phone; flashing a ROM for a completely different device. I'm not sure why you would flash a ROM from another device, maybe due to inexperience, but that's the last thing you should be doing, as you now know. Don't use the recovery tool that you have, it isn't for your chipset, it will only make matters worse. I honestly don't think there's any way to revive your device, you've pretty much rendered it useless. I'd strongly suggest you do a lot of research before deciding to mess with another phone, if you don't know what you're doing then don't do it. Venturing into unknown lands like this only ever ends in disaster.
Click to expand...
Click to collapse
Thanks for your response.
I made a full wipe with Twrp ( as mentionned in your tutorial ) and al steps run without issues.
The issue is that the next day i used the nethunter install tool instead of manually installing, in the steps for one plus one ( not oneplus 2) i mentionned the specific rom which can run on the phone but suddenly when i pushed next it was flashing stock for nexus ( and yes it's in the steps of oneplus1 :/ i verified ) , well i know that it's inadmissible and can brick it seriously
now i have the bulkusb when linked to windows8 and pressing on poweron+volumeup, what do you recommend please? there is no compatible driver for snapdragon 810?flashing to colorOS won't solve the issue please?
Thanks in advance

mG!X said:
Thanks for your response.
I made a full wipe with Twrp ( as mentionned in your tutorial ) and al steps run without issues.
The issue is that the next day i used the nethunter install tool instead of manually installing, in the steps for one plus one ( not oneplus 2) i mentionned the specific rom which can run on the phone but suddenly when i pushed next it was flashing stock for nexus ( and yes it's in the steps of oneplus1 :/ i verified ) , well i know that it's inadmissible and can brick it seriously
now i have the bulkusb when linked to windows8 and pressing on poweron+volumeup, what do you recommend please? there is no compatible driver for snapdragon 810?flashing to colorOS won't solve the issue please?
Thanks in advance
Click to expand...
Click to collapse
Well flashing ColorOS using the tool you have will attempt to flash ColorOS for the OnePlus One, because that tool is not for your device. As I said, don't use it, it's not for your device so it will only do more harm. I don't know if there's a recovery tool for the Two yet, I certainly haven't seen one.

Heisenberg said:
Well flashing ColorOS using the tool you have will attempt to flash ColorOS for the OnePlus One, because that tool is not for your device. As I said, don't use it, it's not for your device so it will only do more harm. I don't know if there's a recovery tool for the Two yet, I certainly haven't seen one.
Click to expand...
Click to collapse
Ok, i will search maybe the drivers come out or someone find a solution, i ill contact support and seek their help also. Thanks and i will keep you updated if i find something

mG!X said:
Ok, i will search maybe the drivers come out or someone find a solution, i ill contact support and seek their help also. Thanks and i will keep you updated if i find something
Click to expand...
Click to collapse
I just can say, your device is not hard bricked and will be recoverable.
You just need to be a bit patient. For the OPO, there was the ColorOs emergency recovery available (which helped me already 2x unbricking my OPO after I compiled a faulty kernel).
I just have not yet seen something similar for the OP2. But as you get the bulk_device still recognized via USB, this means the Qualcomm emergency boot loader is still intact and once the recovery stuff leaks somewhere, you will be able to fully recover your OP2.
Don't ask me when this will be available, think it also took weeks for the OPO before it was posted somewhere.
All the best!
Andi

mG!X said:
Thank you for your response, the issue is that it's hard bricked, so no recovery mode no led , nothing ..
i uninstalled the drivers ( even that i had the adb working before ) and the device is detectable now only with as QHSUSB_BULK
the installation of any adb usb driver don't change anything, only qualcomm usb drivers work ( i have the 9008 only but i'm think it's not compatible with OP2) i could manually change it to adb ( mobistel Cynus f4 ADB interface ) but nothing new..
Help plz
thanks again
Click to expand...
Click to collapse
You can try this (but with oxygenos), but I'm not sure if it works with OP2 snapdragon 810
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
EDIT: It seems you will need fastboot image of oxygenos and list of partitions ... anyway, good luck

yanick76 said:
You can try this (but with oxygenos), but I'm not sure if it works with OP2 snapdragon 810
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
EDIT: It seems you will need fastboot image of oxygenos and list of partitions ... anyway, good luck
Click to expand...
Click to collapse
It probably isn't the smartest idea in the world to recommend using a recovery tool from for an entirely different device unless you're 100% sure it's safe, which it probably isn't.

Heisenberg said:
It probably isn't the smartest idea in the world to recommend using a recovery tool from for an entirely different device unless you're 100% sure it's safe, which it probably isn't.
Click to expand...
Click to collapse
It's Qualcomm tool, but sadly OP2 is new device and there are no guides specific to OP2. He probably can resurrect his phone using QHSUSB_BULK device(*1)
EDIT: (*1) - It depends on correct driver and firmware files (images)

yanick76 said:
It's Qualcomm tool, but sadly OP2 is new device and there are no guides specific to OP2. He probably can resurrect his phone using QHSUSB_BULK device(*1)
EDIT: (*1) - It depends on correct driver and firmware files (images)
Click to expand...
Click to collapse
Yes, I'm aware that there is nothing specific available for the OP2. My point is that you're not even sure if this isn't going to damage the device further, let alone even help in any way.

Heisenberg said:
Yes, I'm aware that there is nothing specific available for the OP2. My point is that you're not even sure if this isn't going to damage the device further, let alone even help in any way.
Click to expand...
Click to collapse
His device is almost dead and this kind of damage is not covered by warranty. I think in this situation is not much to lose

Just to assure you that the hard brick issue on OPT is completely curable since I've revived two OPTs. No panic needed. I will update the complete procedure as well as the necessary files later today.

yanick76 said:
His device is almost dead and this kind of damage is not covered by warranty. I think in this situation is not much to lose
Click to expand...
Click to collapse
His device is not almost dead, it's in a bricked "like" state right now but it can be easily fixed with the correct tool. What you're suggesting is not the correct tool for this device at all. If you're comfortable with being so reckless with someone else's device, good for you, I'm certainly not.

Heisenberg said:
His device is not almost dead, it's in a bricked "like" state right now but it can be easily fixed with the correct tool. What you're suggesting is not the correct tool for this device at all. If you're comfortable with being so reckless with someone else's device, good for you, I'm certainly not.
Click to expand...
Click to collapse
Yes I understand you but my post was meant as suggestion to way how to fix it, not guide. If you think my post can lead him to kill his device you can delete my post (because I can't), I have no problem with it

yanick76 said:
Yes I understand you but my post was meant as suggestion to way how to fix it, not guide. If you think my post can lead him to kill his device you can delete my post (because I can't), I have no problem with it
Click to expand...
Click to collapse
I know you were trying to help, but that advice is the wrong advice. I don't want/need to delete your post. My point here is to try to help you to understand why giving advice when you're not 100% understanding the situation properly isn't a great idea. On a site like this, accuracy and knowledge are paramount because it can be the difference between helping someone revive their device or completely killing it.

mG!X said:
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance
Click to expand...
Click to collapse
Tutorial posted here http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449

Heisenberg said:
I know you were trying to help, but that advice is the wrong advice. I don't want/need to delete your post. My point here is to try to help you to understand why giving advice when you're not 100% understanding the situation properly isn't a great idea. On a site like this, accuracy and knowledge are paramount because it can be the difference between helping someone revive their device or completely killing it.
Click to expand...
Click to collapse
From this point I agree it was wrong advice.
I hope I never will be in situation like this But if, I will try to fix it based on what I suggest him + hours of google for correct files, correct drivers and correct download tool. I think this "misunderstood" was based on my advice like "here is direction and google for more", this is forum if he can find answer himself (google) he need not to ask for help here

i pay if some1 can unbrick my phone

i want help from some1 experienced to help me unbricking my phone

collisiion said:
i want help from some1 experienced to help me unbricking my phone
Click to expand...
Click to collapse
What happened what model pro 3 do you have.
Sent from my LEX727 using xda premium

mchlbenner said:
What happened what model pro 3 do you have.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
my phone only vibrates i cant turn it on, i have x720 model

collisiion said:
my phone only vibrates i cant turn it on, i have x720 model
Click to expand...
Click to collapse
Do you have fastboot working?
What is the last thing you flashed?
Sent from my LEX727 using xda premium

mchlbenner said:
Do you have fastboot working?
What is the last thing you flashed?
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
do u think you can help me? it is better to speak in teamspeak or something

If all you can access is fastboot, then check this guide out: https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340
Your device has a QFIL file you can use to resurrect it. Also, provide us with information, like what you were doing before you bricked your device, and so on. Can't help you without knowing your basic situation.

sk8223 said:
If all you can access is fastboot, then check this guide out: https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340
Your device has a QFIL file you can use to resurrect it. Also, provide us with information, like what you were doing before you bricked your device, and so on. Can't help you without knowing your basic situation.
Click to expand...
Click to collapse
i had a MIUI rom from a chinese forum for a few days and it was very stable and fluid, but when the battery ran out my phone shut down and I cant turn it on anymore. i tried to charge it for a few hours and it didnt turn on. only vibrates. I tried qfil unbrick method. it said success but i still cant turn it on, only vibrates.. my pc recognizes the phone but i dont know what do do.

collisiion said:
i had a MIUI rom from a chinese forum for a few days and it was very stable and fluid, but when the battery ran out my phone shut down and I cant turn it on anymore. i tried to charge it for a few hours and it didnt turn on. only vibrates. I tried qfil unbrick method. it said success but i still cant turn it on, only vibrates.. my pc recognizes the phone but i dont know what do do.
Click to expand...
Click to collapse
Well, you should have mentioned the situation in your first post. Sounds like a hardware issue. Never ever ever let a lithium-ion battery, like those in smartphones, drop to less than 5%. Never let them run out to less than 1% either. That's a surefire way to destroy a battery.
Plug your phone in using a certified USB-C cable (NOT the original LeEco cable that came with your phone) and wait a couple of days. It may begin charging after a while. But since you let the battery deplete to 0%, you might have to replace it.

sk8223 said:
Well, you should have mentioned the situation in your first post. Sounds like a hardware issue. Never ever ever let a lithium-ion battery, like those in smartphones, drop to less than 5%. Never let them run out to less than 1% either. That's a surefire way to destroy a battery.
Plug your phone in using a certified USB-C cable (NOT the original LeEco cable that came with your phone) and wait a couple of days. It may begin charging after a while. But since you let the battery deplete to 0%, you might have to replace it.
Click to expand...
Click to collapse
really? i didnt know that. is it possible to replace a battery on this phones? do you think i can still revive it?

collisiion said:
really? i didnt know that. is it possible to replace a battery on this phones? do you think i can still revive it?
Click to expand...
Click to collapse
Yeah, it should be pretty easy. Before doing that, look through this sub-forum for similar issues. A couple people here had the same issue--they let their battery drain to zero and wanted to revive their phones. I don't know if they managed to or not.
Just look for a Pro3 disassembly guide on Google. It's not hard. The Pro3's interior is similar to other LeEco phones, like the Le 2.
And Google is your friend. Google your issues instead of immediately making a thread here or wherever. This is a common issue on Android.

sk8223 said:
Yeah, it should be pretty easy. Before doing that, look through this sub-forum for similar issues. A couple people here had the same issue--they let their battery drain to zero and wanted to revive their phones. I don't know if they managed to or not.
Just look for a Pro3 disassembly guide on Google. It's not hard. The Pro3's interior is similar to other LeEco phones, like the Le 2.
And Google is your friend. Google your issues instead of immediately making a thread here or wherever. This is a common issue on Android.
Click to expand...
Click to collapse
i didnt know man, im sorry.. i thought it was really dead. thanks for your help

Can you get your phone into fastboot?
Let your phone for 5 hours then push down power button and connect to USB.
Never let your battery go under 15% especially a pro 3.
Your not first to have this problem and posting this issue is alright!
Sent from my LEX727 using xda premium

mchlbenner said:
Can you get your phone into fastboot?
Let your phone for 5 hours then push down power button and connect to USB.
Never let your battery go under 15% especially a pro 3.
Your not first to have this problem and posting this issue is alright!
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
thanks man i thought it was something worse than this, im going to investigate

collisiion said:
thanks man i thought it was something worse than this, im going to investigate
Click to expand...
Click to collapse
Let us know how you fix it, so other people that has same issue can read this, ok ?

Sweden.33 said:
Let us know how you fix it, so other people that has same issue can read this, ok ?
Click to expand...
Click to collapse
ok no problem

collisiion said:
thanks man i thought it was something worse than this, im going to investigate
Click to expand...
Click to collapse
You battery is not necessarily dead, you phone is just hard bricked, the symptoms you are having is exactly what happened to a friends phone and we were able to revive it. Just following the steps in the unbrick guide. https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340 If you check the last post you will see that someone just recently unbricked their phone.
Worst case there are services for repairing a bricked phone:
I have attached my notes below: The information came from multiple post by various people and my own research combined. Its unedited, I had planned on posting a more polished guide. So I am just copy pasting what I have so far. But the methods listed definitely works unless you do in fact have a hardware issue.
This Thread dedicated to unbricking The Leeco variants X720 and X727
These instructions may not work if you flashed with wrong firmware and you are stuck in Qualcomm Mode 9008.
* I plan to create a post that will share these thorough instructions with the public.
* After spending over an hour typing all of this out for you. I found this video that you can use a companion tutorial to walk your through the steps visually. https://www.youtube.com/watch?v=iN9Ce3hKlRA
* While there are s a couple of differences. For example, The person in the video is flashing a different phone.Most of the steps are the same.
https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340
1. Download Flash 2( Tool) here: https://mega.nz/#!ex5nmQxB!qXLIg3wpeQwuiTShdOz_DEStXFiKUPfSoXNLjomn4ag
2. Download the Qfil file for Lex Pro 3 file here: https://mega.nz/#!BJ52CApB!8lFCesula...e=DonanimHaber
3. Make sure you place and run this file from the root of your PC I.E : C:/
4. Do not unzip, when selecting it needs to stay a zip file
5. Keep these files. In case you ever need them again and if it works for you.
Instructions
* QFIL mode: Press on vol+ and vol- simultaneously while holding power
* Alternate way to get into edit mode ( Press vol+ and vol- while plugging usb into pc. enter in edl mode.
* Then start flash one
* Advance option Get HSCT
* Flash Type: Flash dead phone
* To Flash Developer Rom: rename of rom to 1.zip
* After completing the flash press and hold the power-button down for 30+ seconds and the phone will vibrate
* Release the power-button, it will vibrate again after 10-20 seconds*
After you have performed all of the steps
* Your Le Pro 3 will have the temporary repair version of EUI.
* The phone may not boot automatically.
* Press and hold the Power Button for two minutes or longer.
* iIt will leave the QFIL Mode, and will vibrate continuously for 20 seconds or longer.
* The phone could take as long as 15 minutes to start.
* Immediately you will notice that part of your storage is missing.
*
* Restore the storage back to default by going to Backup/Restore in Settings and Factory Resetting the Phone with the "Format Virtual SD Card" Option selected.
* *Next install the latest Official EUI download EUI 21S ( do mot load anything above this)
* Rename the file to Update.zip and place on OTG drive or into phone storage using file manager.
* Go to check for update and click hamburger icon in top corner and select you Update.zip file to upgrade
* If it doesn’t work retry steps,, If you have an issue from here let me know, also let me know if it works.
Worst Case after restoration attempt to resolve size issue.
* if you still have a problem install Twrp and Flash via TWRP install.,
* Wipe EVERYTHING... and flash the ROM using a usb Flash Drive and after mounting USB OTG Storage.*
* To Flash TWRP simply shut down the phone and By Keeping the Volume Down Button Pressed Hit the Power Button to Enter the Fastboot Mode.*
* flash TWRP Recovery...
* Boot into TWRP Recovery...
* Restart TWRP Recovery... I
* insert the USB Flash Drive
* Using USB OTG Adapter... and flash the ROM using the Install Tab in TWRP Recovery.
Addendum:
As far as I know the X725, has the exact hardware requirements as the X720 and X727 and many parts suppliers list hardware components being compatible with all three devices.*
Have you tried removing and reinstalling Qualcomm drivers, turning off firewall and antivirus, reinstalling and rebooting? Sometimes the most basic steps are the solution.
Here is a link that might provide additional things to try:*http://www.androidbrick.com/unbrick-...usb_dload_edl/
Stock Rom and drivers can be found here:*https://devsjournal.com/download-let..._Pro_Stock_ROM
I will look around and see if I can help you find anything else that may be useful.
BTW, the X720 and X727 are pretty much the same phone so it doesn't matter, it can be easily fixed. At this most my X727 thinks its a X720 because I just flashed a newly released X720 test Rom.*
Here is a link to a Stock Rom that will not ask for a key and the drivers can be found here as well.*https://devsjournal.com/download-let..._Pro_Stock_ROM*( This should definitely work I know that several people have used this file recently with success)
I will look around and see if I can help you find anything else that may be useful.
_____________________________________________________________________________________
Addendum:
Re: Instructions for unbricking your phone
Okay so you were able to download the files but Windows is not recognizing the file. Okay, I read the message in the middle of being focused on something else and misunderstood,thinking that you couldn't download it.*
So It seems that Windows has damaged the file or Qfil installation.
1. Do you have more then one copy of the file? Here is an alternative copy:*https://androidfilehost.com/?w=files&flid=244213
2. You will need to uninstall and reinstall Qfil
If you are on Windows 10, you will need to turn off antivirus, and all the block-ware that Microsoft has installed within Defender which may delete files or neuter files that it doesn't like. Perhaps this is what happened to your Qfil installation? ( I have a new laptop and dealt with this issue recently attempting to install Viper Audio mods for PC) So unfortunately, you may also need to uninstall and reinstall Qfil, ensure that you install as admin.
Go through your settings and make sure under apps >>apps and features>> the dropdown box installing apps and turn off installing apps from store only.
Go to Apps & features in Settings.
Under “Installing apps,” there is a drop-down menu with three options: make sure “Allow apps from anywhere” is on.
Although the Qfil tool is used universally to repair all Qualcomm boards. Windows 10 may cause issue and disable functions that allow root level changes to your attached device. Yes, this will flag Windows Defender
Defender
* Open Windows Defender Security Center from your Start menu, desktop, or task-bar.
* Click on the App and browser control button on the left side of the window.
* Check Off in the Check apps and files section.
* Make sure that Defender and any other antivirus or malware blocker is turned off.
* Unfortunately, from now on you will always need to turn these things off if you are installing drivers or programs that did not come from Windows store.
* Make sure all defender settings are toggled off.
* Turn off the controlled folder access .
Worst case: Other potential ways to resolve
This sucks ( If you will never use it otherwise) but you may even need to enable developer mode
https://docs.microsoft.com/en-us/win...or-development
You can return everything back to normal after you unbrick your phone.
The link below explains how to resolve additional potential issues caused by the Microsoft OS,
https://flashfiletool.com/qualcomm-usb-driver-download*The full setup option, on this page will download all drivers ( download only if needed) for all supported phones.
Hopefully, this finally resolve it for you. I am keeping notes. So once this is resolved. We can provide some updated cohesive steps to help other people that have the same

HardBricked OP5, plz help! :(

Hi, guys.
Today, my OP5 decided to troll me. I was using normally him, when suddenly it started to lags pretty bad. I restarted and he continued to lags and freeze. I made a wipe cache via stock recovery (i didnt made any change at all in it, no unlocked bootloader, no root). That's when my nightmare begins. It begins to bootloop. Sometimes i was able to start the boot animation, but then it just restarts to the beginning. I tried a lot of tips, wiping cache, system, etc. Then, i left it charging. When i tried to turn on again, it worked like nothing ever happened to him. I made a backup of my personal data fast, scared to him suddenly restart again. After that, i decided to made a Factory Reset, clean up everything. When i did it, he started the lag and freezes again. I was at lost. That's was when i decided to use the official unbrick tool, to make the cleanest OP5 ever possible. I grabbed the archives from this link and followed this tutorial. When i was executing the programa, in the userdate.img, he showed a error. When i saw it, i just stopped and closed the program. Now, my OP5 is hardbricked. The only sign of life that i get from him is when i connect him at the PC. I can identify it as qualcoom 9008, but when i try to run the program, he just fail and show me error 258.
Plz, i need some orientations. I have been read things for about 10 hours and didnt found a solution. I live abroad for any oneplus tech center, and i believe, for the other posts that i read, that online tech support wouldn't help me a lot. I really don't like to make this kind of post but i am kind of desesperate. I dont have money to afford another phone
Again, sry to disturb you all. Sry if i broke some rule of the forum too. And sry for my bad english, i hope that i was able to communicate right.
EDIT: I just tried in another computer. Same error appears. :'(

Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine

I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine
Click to expand...
Click to collapse

Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Click to expand...
Click to collapse
I used the tools for 5. Just the procedure that i get from this topic. :T I am gonna try the method that you gave me now brb.
EDIT: Just tried this. My cellphone cant be recognized in fastboot devices. As a said, i am not getting any response for him, just when i plug it in the PC. So i wasn't able to unlock bootload or anything like that. I tried just to plug it and see if fastboot was able to identifying it, but it wasn't.

bartito said:
I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Click to expand...
Click to collapse
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.

cidsantiago said:
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.
Click to expand...
Click to collapse
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.

bartito said:
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.
Click to expand...
Click to collapse
I can't access recovery anymore, as i said. The only sign of life that i get is when i connect it in the PC.

I guess i have to do something to restore the basics partitions of my cellphone. Like recovery, boot, etc. But i just have the official tool to do that. There is another way? Like transfering directly by the COM port?

Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol

Mash1ro said:
Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol
Click to expand...
Click to collapse
In one of the links, it had the OOS and the HOS. I tried to use the msm tool in one of them, but it didnt worked I'm gonna try the archives in this link that you gave me. It may work brb with updates.

Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.

I am getting the same error 258 in this post. :T I posted there to see if the OP can help me. But thx for your help @Mash1ro

Mash1ro said:
Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.
Click to expand...
Click to collapse
Thx for your support! I will continue to try stuff

Try reading the comments from this post as well https://forum.xda-developers.com/oneplus-3t/help/hard-bricked-op3t-t3574720/page2
2 of the people had the same error as you, and one of them solved the issue by changing the USB port.
---------- Post added at 02:26 PM ---------- Previous post was at 02:23 PM ----------
But don't use the same files and all that stuff, since that's for the 3T. Try to pick out the things that might help but use the files for the OnePlus 5 only

After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?

cidsantiago said:
After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?
Click to expand...
Click to collapse
it seems like a hardware problem, i was facing this on different phone ( 5X )

Apayah said:
it seems like a hardware problem, i was facing this on different phone ( 5X )
Click to expand...
Click to collapse
yeah... But it is kind of weird. He was running smoothly, until suddenly started lag and freeze. He didn't fall or any of that... I think is just a defective phone. Doesn't find another explanation to that.

I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.

david19au said:
I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.
Click to expand...
Click to collapse
I already contact the store that i bought to get my warranty. Unfortunately, i didn't bought it in oneplus.net, bcs they don't deliver in my country. I am hoping that everything work out

Guys, in the end, i RMA my device back to the seller and gonna have a refund Thank you for your help. So sad that this phone came faulty :T
Best regards to you all!

Custom ROM for Redmi Note 3 SD

Hi folks, long time reader, first few times posting however.
The short story:
Redmi Note 3 SD 625 password system corrupted, unable to access it.
Used Miko Tools to remove the lock function. Got access to phone.
The unlock process left me with MIUI 8 6.9.9 on the phone, and the Wifi and BT are both stone cold dead.
I cannot seem to unlock the phone, it's being stubborn about that, however I can get the phone into EDL mode. I have put the phone into Dev mode, and enabled USB debugging.
My only choice to fix this dead Wifi issue, seems to be to flash a new ROM on it, but all these ROMS confuse the heck out of me, I dont know what to use. All this stuff, I have had to learn by reading, and it is on the absolute edge of my computer/tech limits of understanding.
Could someone please do an old guy a favour, and just suggest a stable, dependable, non flashy ROM, that has working Wifi on it, and let me know if I can flash the ROM using MiFlash in EDL mode.
Thanks a lot people. You saved my personal phone last year, lets see if you can rescue my sons one this time.

thatguy. said:
Hi folks, long time reader, first few times posting however.
The short story:
Redmi Note 3 SD 625 password system corrupted, unable to access it.
Used Miko Tools to remove the lock function. Got access to phone.
The unlock process left me with MIUI 8 6.9.9 on the phone, and the Wifi and BT are both stone cold dead.
I cannot seem to unlock the phone, it's being stubborn about that, however I can get the phone into EDL mode. I have put the phone into Dev mode, and enabled USB debugging.
My only choice to fix this dead Wifi issue, seems to be to flash a new ROM on it, but all these ROMS confuse the heck out of me, I dont know what to use. All this stuff, I have had to learn by reading, and it is on the absolute edge of my computer/tech limits of understanding.
Could someone please do an old guy a favour, and just suggest a stable, dependable, non flashy ROM, that has working Wifi on it, and let me know if I can flash the ROM using MiFlash in EDL mode.
Thanks a lot people. You saved my personal phone last year, lets see if you can rescue my sons one this time.
Click to expand...
Click to collapse
Just Flash MIUI 9 stable via edl it solves everything

Thank you Sampath, I appreciate your help.

Still having no success. I download the MIUI 9, but is that a file I can flash via EDL mode, or just update using the phone only?. I keep getting a message saying unable to find flash script. The phone is in EDL, and shows as the right Qualcomm 9008 thing in the Devive manager, but if I am not getting the "less than zero" error, I get the flash script one instead.

http://en.miui.com/a-234.html
Search your phone in the list of this web.
★ Redmi Note 3 SD Latest Global Stable Version Fastboot File Download
★ Redmi Note 3 SD Lastest Global Developer Version Fastboot File Download
★ Redmi Note 3 Special Edition Latest Global Stable Version Fastboot File Download
★ Redmi Note 3 Special Edition Lastest Global Developer Version Fastboot File Download
you need to extract the files.

Got the rom, extracted the files, but now Im getting
length cannot be less ythan zero parameter length
I wish these things could be simpler.
Everything Ive read for the last 4 days of trying to fix this phone says I am at the point where I simply open MiFlash, it will then see my phone, which is showing as the correct Qualcomm 9008 device in the coms section of device manager.
Surely this is just a crappy driver or something that I have missed, I have the right rom (fastboot), and the absolute latest MiFlash, the red light is blinking on the phone showing it's in EDL mode, but im stuck with Miflash not being able to see the damn phone, and giving me this less than zero message over and over.

Well, this story ended up with me giving up. Going to stick with the big brands from now on. Thought I was getting something good with these redmi phones.

thatguy. said:
Hi folks, long time reader, first few times posting however.
The short story:
Redmi Note 3 SD 625 password system corrupted, unable to access it.
Used Miko Tools to remove the lock function. Got access to phone.
The unlock process left me with MIUI 8 6.9.9 on the phone, and the Wifi and BT are both stone cold dead.
I cannot seem to unlock the phone, it's being stubborn about that, however I can get the phone into EDL mode. I have put the phone into Dev mode, and enabled USB debugging.
My only choice to fix this dead Wifi issue, seems to be to flash a new ROM on it, but all these ROMS confuse the heck out of me, I dont know what to use. All this stuff, I have had to learn by reading, and it is on the absolute edge of my computer/tech limits of understanding.
Could someone please do an old guy a favour, and just suggest a stable, dependable, non flashy ROM, that has working Wifi on it, and let me know if I can flash the ROM using MiFlash in EDL mode.
Thanks a lot people. You saved my personal phone last year, lets see if you can rescue my sons one this time.
Click to expand...
Click to collapse
What is miko tools ? Is it given by xiaomi ?

naik2902 said:
What is miko tools ? Is it given by xiaomi ?
Click to expand...
Click to collapse
I found Miko as a link on a youtube video. All other screen unlock methods I tried failed. Miko worked first time, and had other features on it too. It covers a lot of mainstream brands of phone by the looks of it.
As an update, after my rage quit earlier this morning, I found a program that lists all your USB ports? drivers? installed (not really that computer literate sorry), and it showed me a heap of residual drivers left over from my Redmi note 3 MTK flash that I did on my phone earlier last year. I uninstalled dozens of dead or unused and unrecognised usb devices and drivers using this program, and then unintalled anything Xiaomi or Redmi on the list, and started again.
I plugged the phone in, it went to install the drivers, but I specified which ones I wanted to use, I opened MiFlash, and it recognised the phone instantly. I flashed the phone first time, no issues.
If anyone else is stumbling blindly through this process, I all I can say is DRIVERS, DRIVERS, DRIVERS !!!!!. They are the key to your flash working, in my opinion.
The 2 programs I used are linked below. I needed Miko because the the reason for the flash in the first place, was because of a corrupted password system in the phone, that locked us out of it completely. Miko solved that in seconds. The second program is USB-deview, and that showed me all the USB issues and old and incorrect drivers I needed to get rid of. I hope these help someone else out of a jam one day.
These two files are hosted on my personal FTP, they will be clean and virus free.
Miko - http://www.s8.nz/flash/MIKO_TOOL_V1.0.rar
USB Deview - http://www.s8.nz/flash/usbdeview-x64.zip

thatguy. said:
I found Miko as a link on a youtube video. All other screen unlock methods I tried failed. Miko worked first time, and had other features on it too. It covers a lot of mainstream brands of phone by the looks of it.
As an update, after my rage quit earlier this morning, I found a program that lists all your USB ports? drivers? installed (not really that computer literate sorry), and it showed me a heap of residual drivers left over from my Redmi note 3 MTK flash that I did on my phone earlier last year. I uninstalled dozens of dead or unused and unrecognised usb devices and drivers using this program, and then unintalled anything Xiaomi or Redmi on the list, and started again.
I plugged the phone in, it went to install the drivers, but I specified which ones I wanted to use, I opened MiFlash, and it recognised the phone instantly. I flashed the phone first time, no issues.
If anyone else is stumbling blindly through this process, I all I can say is DRIVERS, DRIVERS, DRIVERS !!!!!. They are the key to your flash working, in my opinion.
The 2 programs I used are linked below. I needed Miko because the the reason for the flash in the first place, was because of a corrupted password system in the phone, that locked us out of it completely. Miko solved that in seconds. The second program is USB-deview, and that showed me all the USB issues and old and incorrect drivers I needed to get rid of. I hope these help someone else out of a jam one day.
These two files are hosted on my personal FTP, they will be clean and virus free.
Miko - http://www.s8.nz/flash/MIKO_TOOL_V1.0.rar
USB Deview - http://www.s8.nz/flash/usbdeview-x64.zip
Click to expand...
Click to collapse
U confusing me.
What is ur device? Redmi note 3 sd pro or MTK ?
IN THE FIRST POST YOU SAID Sd and now saying mtk.

naik2902 said:
U confusing me.
What is ur device? Redmi note 3 sd pro or MTK ?
IN THE FIRST POST YOU SAID Sd and now saying mtk.
Click to expand...
Click to collapse
I mentioed in my earlier posts that I flashed my MTK last year, but that I was working on my sons Snapdragon this time.
I have 3 Redmi phones now.
Mine is the MTK, which I flashed last year.
My son has the SD version, which is the one I was trying to fix.
My wife has a Note 4, which is fine.

thatguy. said:
I mentioed in my earlier posts that I flashed my MTK last year, but that I was working on my sons Snapdragon this time.
I have 3 Redmi phones now.
Mine is the MTK, which I flashed last year.
My son has the SD version, which is the one I was trying to fix.
My wife has a Note 4, which is fine.
Click to expand...
Click to collapse
Ok.... Ur phone is rn3mtk and ur son phone is rn3pro
So did u unlock the bootloader on Rn3 sd?
Officially or unofficially? Did u install twrp ?

I unlocked THE RN3SD officially with Xiaomi software. I didnt use TWRP.

thatguy. said:
I unlocked THE RN3SD officially with Xiaomi software. I didnt use TWRP.
Click to expand...
Click to collapse
Do you have fastboot drivers on pc.
Connect phone in fastboot mode to pc. In cmd can u see ur device serial no ? Using below command
fastboot devices
If its showing ur device then Whats the output for below command. Does it show ur device is unlocked.
fastboot oem device-info

What name have your driver in windows?. (To use MiFlash)
What version of MiFlash?
What version of Windows?

Chrisis25 said:
What name have your driver in windows?. (To use MiFlash)
What version of MiFlash?
What version of Windows?
Click to expand...
Click to collapse
Why all the questions still?. I mentioned in my earlier post that i had fixed the phone now. It's running perfectly on MIUI9, and the wifi and BT are working.
If it helps........
The device showed as the correct Qualcomm 9008, but it was showing correctly the whole way through, but the heap of old MTK drivers must have been confusing the issue.
I'm on Win 7 64b
MiFlash was the latest one off the official website

Sorry my bad

Somebody Could Save My Nokia-6(TA-1021) Please?!

I flashed in an incorrect firmware on my Nokia 6 and it now goes into a mode where it boots properly (MIUI) but the screen doesn't work properly (the drivers don't correspond at all), I was able to go into 900E mode properly before but now I can only go into the system.
I have tried brushing in the bottom by shorting the data cable (how the engineering cable works) but it does nothing, it still boots into the system normally.
Is there anything else I can do to save it now?
I used a translator, some words may be a bit strange sorry ....
But thank you for taking the time to help me out!
MydeviceInfo:
Nokia 6 (TA-1021)
NowUI: a MIUI for a xiaomi device that used the same CPU

Hey, so you tried to flash a rom that only has the same CPU? If i remember correctly there are somewhere on the internet tools to recover your Nokia device, although i can't remember how they are called, if i have the time i can look it up and provide them here. Once needed them for myself to recover my device.

Wapitiii said:
Hey, so you tried to flash a rom that only has the same CPU? If i remember correctly there are somewhere on the internet tools to recover your Nokia device, although i can't remember how they are called, if i have the time i can look it up and provide them here. Once needed them for myself to recover my device.
Click to expand...
Click to collapse
Thank you, bro! (hug

Wapitiii said:
Hey, so you tried to flash a rom that only has the same CPU? If i remember correctly there are somewhere on the internet tools to recover your Nokia device, although i can't remember how they are called, if i have the time i can look it up and provide them here. Once needed them for myself to recover my device.
Click to expand...
Click to collapse
Yeah, I flash a MIUI official rom that only has the same CPU...