I have a OP7t with ColorOS 12.1 installed, it's the hd1900 (china) version.
i wanted to change to havocOS, but I have to unlock the bootloader before.
Oem unlock and USB debug are enable in dev options, in fastboot, the command "fastboot flashing unlock" give me the "'Flashing Unlock is not allowed" error.
To check if oem is really enable, I try "fastboot flashing get_unlock_ability" and it give me 0 (so it's not enable but the option is on and the command "adb shell getprop sys.oem_unlock_allowed" give me 1).
Then I assume that the chinese system doesn't allow the unlocking of the bootloader, I tried to switch to OOS (eu version), I tried :
- with the OOSupdater --> it tell me that it doesn't support my device.
- in the setting of colorsOS, use the local installation with a OOS firmware, don't work either.
- with MSMDownloader --> when I boot on EDL, the device is detected by Device Manager in "PORTS" as "Quectel QDLOADER 9008", but MSM doesn't detect the phone.
I don't know what I can do now :/
Thank you in advance for your replies.
Ok I found out the problem.
It was because, for one raison, my phone on edl mode was detected as "Quectel QDLOADER 9008" and it's bad, it has to be "Qualcomm QDLOADER 9008".
I succeed to desactivate and uninstall the Quectel driver, it automatically turn to Qualcomm and from now MSM can detect the phone.
Then I switch the ****ty colorsOS to OxygenOS and unlock the bootloader.
Related
Hello sirs, I hope you can help me.
I have a mi6 that turned into a brick. Hold the buttons to it to give restart / download mode or put it to load. He does not respond to anything.
However,
By putting it on your computer it recognizes you as Qualcomm QDLoader 9008.
I wonder if I can recover it yet. or unfortunately it turned a paper weight.
DL Xiaomi flash tool and flash fastboot rom. It will be fine.
icrunchbanger said:
DL Xiaomi flash tool and flash fastboot rom. It will be fine.
Click to expand...
Click to collapse
I tried to do this form, downloaded all the miui site drivers, adb fastboot and cualcomm driver.
How to run my flash with a last method with the xiaomi global mi6 I got the following error:
"Cannot receive hello packet Xiaomi Device"
The program tried a few more times and nothing more.
What can I be doing wrong? Do you have another option? because he is in what they call DeadBrick (I discovered this term only now, after searching the forums)
XeeXa said:
I tried to do this form, downloaded all the miui site drivers, adb fastboot and cualcomm driver.
How to run my flash with a last method with the xiaomi global mi6 I got the following error:
"Cannot receive hello packet Xiaomi Device"
The program tried a few more times and nothing more.
What can I be doing wrong? Do you have another option? because he is in what they call DeadBrick (I discovered this term only now, after searching the forums)
Click to expand...
Click to collapse
I know, i was there. Reboot your computer and start again.
I restarted and tried again.
I formatted and installed only the drivers and the error continues.
I tried with miflash 2015 until version miflash2017
I think, you device isn't in EDL mode. You open back cover of device. Make test point for QDL 9008. Then, you flash fastboot rom by Mi flash tool. It's very simply. I made it for unbrick my Mi6 several times.
See video here.
https://youtu.be/vSNRQdUuNYw
bahuy2003 said:
I think, you device isn't in EDL mode. You open back cover of device. Make test point for QDL 9008. Then, you flash fastboot rom by Mi flash tool. It's very simply. I made it for unbrick my Mi6 several times.
See video here.
Click to expand...
Click to collapse
Is this the only way to put the phone in edl mode?
Yes, it's only way for Mi6, which is locked bootloader.
Last time i flashed ThE stock ROM via mi flash tool i lost energy on my pc so prosess ended un error. My phone was in fastboot but i rebooted and never turns on again. I cant get fastboot mide anymore. Adb not recognice it but i can see it on PC in device mánager as "gualcomm HS-USB diagnostics 900E (COM3)
Any help?
MaxxTwo said:
Last time i flashed ThE stock ROM via mi flash tool i lost energy on my pc so prosess ended un error. My phone was in fastboot but i rebooted and never turns on again. I cant get fastboot mide anymore. Adb not recognice it but i can see it on PC in device mánager as "gualcomm HS-USB diagnostics 900E (COM3)
Any help?[/QUOTE
Just go to fastboot mode and type: "fastboot oem edl"
If you can´t enter fastboot, you have to open your phone and connect both testpoints
it's all on xda questions and anwsers mi A2 lite
Click to expand...
Click to collapse
Nxkealen said:
MaxxTwo said:
Last time i flashed ThE stock ROM via mi flash tool i lost energy on my pc so prosess ended un error. My phone was in fastboot but i rebooted and never turns on again. I cant get fastboot mide anymore. Adb not recognice it but i can see it on PC in device mánager as "gualcomm HS-USB diagnostics 900E (COM3)
Any help?[/QUOTE
Just go to fastboot mode and type: "fastboot oem edl"
If you can´t enter fastboot, you have to open your phone and connect both testpoints
it's all on xda questions and anwsers mi A2 lite
Click to expand...
Click to collapse
Thanks! But its in indi, can not undetstand nothing XD
Click to expand...
Click to collapse
https://redirect.viglink.com/?key=e...ter-t3862648/amp/&ref=https://www.google.com/
1- install mi flash tool and Qualcomm driver on your Pc
2- open the phone (just remove the battery connector )
3-plug a USB cable in the device
4- short the jtag pins(you can find their location in this page www mobilerdx com/2018/09/xiaomi-redmi-6-pro-test-point-boot-into-edl-9008-mode.html
7-plug the USB cable in the Pc while shortening the pins
If you do these steps mi flash tool should reconize your device and you will be able to flash it
Thanks man! My phone is working properly again. Let me tell my story in this.
Never opened a device before this. So I decided to take it to the official service. Unfortunately they told me that the mother board was damaged and the cost to REPLACE it is the same as buy a new phone!
So I been forced to try fix it by my self.
A couple of latex gloves XD and don't ask how I did to short the points but it works...
Now I'm using my Daisy again and waiting for official Android Q !!!
I broke my device, I cannot flash rom in fastboot , and I found a solution by removing the battery, connecting two points and then connecting the device to PC to show me " Qualcomm HS-USB QDLoader 9008 " appeared to me but it does not appear in miflash or any another flash tool
cescer4 said:
I broke my device, I cannot flash rom in fastboot , and I found a solution by removing the battery, connecting two points and then connecting the device to PC to show me " Qualcomm HS-USB QDLoader 9008 " appeared to me but it does not appear in miflash or any another flash tool
Click to expand...
Click to collapse
Please Help Me
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, Verizon OP8, Visible OP8, OP8Pro, OP Nord, regular OP8T, T-Mobile OP8T, regular OPN10 5G and regular OPN100 here is the EDL package (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N10 bought from T-Mobile.
As this is a carrier specific MSM, it will only work with BE2028 model with build tag BE88CB
You should also be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
You can download the following versions:
ANDROID 10:
OOS 10.5.8
Mirror for first and last MSMs: https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Maintain volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
OnePlus for the device and OS
Reserved
I need this for the T-Mobile Variant.
- Works great! Thanks.
I learned a ton of hard lessons with this device. My maiden voyage of custom ROM and hackery. Now, unfortunately, I have to resort to a power greater than my own mind to restore my little N10 5G to sanity. Thank you for this post, and wish me luck,
Click to expand...
Click to collapse
Will the above work on the TMobile varent?
mbl1979 said:
Will the above work on the TMobile varent?
Click to expand...
Click to collapse
Duh
una ar oem aluna solucion
Can i use this to downgrade from 11 to 10..?
Fr4n©\<y said:
Can i use this to downgrade from 11 to 10..?
Click to expand...
Click to collapse
Yes. Moreover when boot to Android 10 and connect to WiFi it can be updated back to Android 11 ( through native update interface, did not check but got a prompt )
@Some_Random_Username
What if I have Unlocked Bootloader + TWRP + patched boot - will unbrick flashing restore these partitions to factory defaults ?
Will I lose bootloader unlock after flashing ?
Thank you
.
Testing
Would this also work on the Metro version?
UPDATE: The issue stands solved [see post 5].
........................................................................................................................................................................
I am facing a rather intriguing issue wherein the device tends to automatically exit EDL Mode after around 5 seconds. During that short-time frame, the Device Manager recognizes it in EDL Mode as Qualcomm HS-USB QDLoader 9008. Even the MSM Tool is able to identify the connected device. However, right after a few seconds the device gets booted to the OS.
So could anyone let me know why is this happening and more importantly how it could get rectified. [Windows Driver Signature Verification is disabled and Qualcomm USB Drivers are successfully installed].
Moreover, currently I'm on Pixel Experience ROM. So are custom ROM's known to cause any conflict with EDL Mode?
EDIT My device is not bricked and I could easily access the OS [Pixel Experience]. However, I still want to use MSM Tool as opposed to say, Fastboot Enhance Tool, for testing purpose. So any insights in this regard will be highly appreciable.
My way was :
Launch MSM Tool
Launch Phone into Recovery
Connect USB Cable
Advanced -> allow ADB
On PC : adb reboot edl
As soon as the Device Screen turns black, Phone gets detected in MSM Tool and then Start Process. That worked for me
ohwarumbloss said:
My way was :
Launch MSM Tool
Launch Phone into Recovery
Connect USB Cable
Advanced -> allow ADB
On PC : adb reboot edl
As soon as the Device Screen turns black, Phone gets detected in MSM Tool and then Start Process. That worked for me
Click to expand...
Click to collapse
I face the same issue on my OnePlus 9 and this help me. Thank you so much.
binary**# said:
I am facing a rather intriguing issue wherein the device tends to automatically exit EDL Mode after around 5 seconds. During that short-time frame, the Device Manager recognizes it in EDL Mode asQualcomm HS-USB QDLoader 9008. Even the MSM Tool is able to identify the connected device. However, right after a few seconds the device gets booted to the OS.
So could anyone let me know why is this happening and more importantly how it could get rectified. [Windows Driver Signature Verification is disabled and Qualcomm USB Drivers are successfully installed].
Moreover, currently I'm on Pixel Experience ROM. So are custom ROM's known to cause any conflict with EDL Mode?
EDIT My device is not bricked and I could easily access the OS [Pixel Experience]. However, I still want to use MSM Tool as opposed to say, Fastboot Enhance Tool, for testing purpose. So any insights in this regard will be highly appreciable.
Click to expand...
Click to collapse
were you able to find any work around. I am currently on OOS 12 F.22. I am having another issue of widevine L1 certification as my device has L3 certificate. To rectify this i am trying to use MSM tool.
raoakashyadav said:
were you able to find any work around. I am currently on OOS 12 F.22. I am having another issue of widevine L1 certification as my device has L3 certificate. To rectify this i am trying to use MSM tool.
Click to expand...
Click to collapse
Sorry for the delay in reply. Yup, I fixed this issue via the Disable Driver Signature Verification tweak as shown in this video. In short -->
Install Qualcomm USB Driver and download MSM Tool.
Boot your device to EDL Mode and connect it to your PC.
Then DO NOT disable Driver Signature Verification on your PC.
So as of now, your device will be listed as Qualcomm HS USB QDLoader under Device Manager but will have a yellow exclamation mark [because Drive Signature is enabled]. But at the same time, Windows will hold your device in this ELD Mode and wouldn't let it boot to the OS [which is what we wanted].
So while having your device connected to your PC in EDL Mode, now disable Driver Signature Verification. With this, your device should now stay in EDL Mode and will be listed without any yellow warning sign under Device Manager. You could now proceed ahead with the flashing via MSM Tool without any issues.