Hi everyone,
I'm having this "locked bootloader" issue as probably hundreds other people do, since January update appeared. In my case the phone became unusable, stuck on MI logo, and also there is no recovery available.
I can only use fastboot.
I understand that some people managed to completely erase the eMMC and reflash the bootloader while the phone is connected to the computer in "Qualcomm HS-USB QDLoader 9008" or "QHS_USB Bulk" mode.
I can't figure out how to boot the phone in either of these modes! When connected through fastboot the MI4C is being recognized as "Marshall London Bootloader Interface". When I just turn it on and it's stuck on MI logo, it isn't recognized by device manager at all.
I'm on Windows 10 64 bit. Anyone has any idea what needs to be done to access these modes on Mi4C?
Many Thanks!
dsafro said:
Hi everyone,
I'm having this "locked bootloader" issue as probably hundreds other people do, since January update appeared. In my case the phone became unusable, stuck on MI logo, and also there is no recovery available.
I can only use fastboot.
I understand that some people managed to completely erase the eMMC and reflash the bootloader while the phone is connected to the computer in "Qualcomm HS-USB QDLoader 9008" or "QHS_USB Bulk" mode.
I can't figure out how to boot the phone in either of these modes! When connected through fastboot the MI4C is being recognized as "Marshall London Bootloader Interface". When I just turn it on and it's stuck on MI logo, it isn't recognized by device manager at all.
I'm on Windows 10 64 bit. Anyone has any idea what needs to be done to access these modes on Mi4C?
Many Thanks!
Click to expand...
Click to collapse
You need a working phone with USB debug enabled, then " adb reboot edl" from cmd... Sorry but if you are in a boot loop there is no knows way to access the Qualcomm mode...
There is no way for you to go into EDL mode. You need to apply for unlock permission from Xiaomi if you want to fix your mi4c yourself.
I applied for permission on Feb 1, and I got it today (Feb 18) despite the Chinese New Year holidays. I haven't even received my mi4c from China yet, and am not even a diamond member at miui.com, either. Good luck!!
dsafro said:
Hi everyone,
I'm having this "locked bootloader" issue as probably hundreds other people do, since January update appeared. In my case the phone became unusable, stuck on MI logo, and also there is no recovery available.
I can only use fastboot.
I understand that some people managed to completely erase the eMMC and reflash the bootloader while the phone is connected to the computer in "Qualcomm HS-USB QDLoader 9008" or "QHS_USB Bulk" mode.
I can't figure out how to boot the phone in either of these modes! When connected through fastboot the MI4C is being recognized as "Marshall London Bootloader Interface". When I just turn it on and it's stuck on MI logo, it isn't recognized by device manager at all.
I'm on Windows 10 64 bit. Anyone has any idea what needs to be done to access these modes on Mi4C?
Many Thanks!
Click to expand...
Click to collapse
Did you try flashing it with Miflash? I got bricked yesterday, so I reflashed system this way, but via Qualcomm HS-USB QDLoader. Also, my phone did not react to anything except bootloader mode (holding buttons for a long long time), no charging, no lights - nothing.
Me too
Me too. :crying:
Hi,
I have the same problem of the bootloader locked. Not let me do anything. It is blocked. I've tried to give instructions by ADB, but will not let me load any file since it claims to be the phone locked.
I have applied the code unlock via SMS to Xiaomi, but they are very slow. Yesterday I wrote and asked you to unlock it. They asked me 2 days more waiting, at least.
This is still horrible, a shame.
I read the post of a colleague who manages to unlock it but has to be the phone working. For those who stayed with my at startup, there is no solution.
Regards.
Hi Guys,
Im new to the forums so i hope this is the right place for this post
I have a hardbricked oneplus one 64GB.
I have read and followed mutiple guides here and on youtube on how ot unbrick it.
But in every guide i followed mine "failed" at the same step.
When i start the "oneplus one recovery tool" or Msm8974DownloadTool this happens; (cant seem to use a link so ill try to explain it).
It starts with one green bar, when that is finished it stops an i hear the disconnected device sound.
I am currently on Win 10 but i also tried it on WinXP since mutiple posts suggested hat it would work better, but that also didnt help.
I also tried diffrent drivers (oneplus driver from the color zip), google multi driver, qualcomm driver etc.
Hope someone can help
Tiic said:
Hi Guys,
Im new to the forums so i hope this is the right place for this post
I have a hardbricked oneplus one 64GB.
I have read and followed mutiple guides here and on youtube on how ot unbrick it.
But in every guide i followed mine "failed" at the same step.
When i start the "oneplus one recovery tool" or Msm8974DownloadTool this happens; (cant seem to use a link so ill try to explain it).
It starts with one green bar, when that is finished it stops an i hear the disconnected device sound.
I am currently on Win 10 but i also tried it on WinXP since mutiple posts suggested hat it would work better, but that also didnt help.
I also tried diffrent drivers (oneplus driver from the color zip), google multi driver, qualcomm driver etc.
Hope someone can help
Click to expand...
Click to collapse
How your device got bricked?
Which recovery tool you tried?
Mr.Ak said:
How your device got bricked?
Which recovery tool you tried?
Click to expand...
Click to collapse
I don't have all the info since i got the phone from a "friend" who was about to throw it out, but ill do my best to provide accurate info
According to the privious owner the flashing of a custom rom or recovery went wrong and it ended up in it's current state.
The recovery tools i tried are;
- Oneplus one recovery tool by; Zyxxeil
- Oneplus one toolkit 1.5 by Manudroid19
- Msm8974DownloadTool
Tiic said:
I don't have all the info since i got the phone from a "friend" who was about to throw it out, but ill do my best to provide accurate info
According to the privious owner the flashing of a custom rom or recovery went wrong and it ended up in it's current state.
The recovery tools i tried are;
- Oneplus one recovery tool by; Zyxxeil
- Oneplus one toolkit 1.5 by Manudroid19
- Msm8974DownloadTool
Click to expand...
Click to collapse
Use the one with cm11s by Zyxxeil.Use Xp and use Qualcomm drivers,as this tool doesn't use fast boot/adb drivers and instead uses USB debugging port.
It need a few tries before device getting detected.
Make sure the device is getting recognized as "Qhs_bulk" or "Qualcomm diagnostics 9006" or some thing like that then install drivers manually.Also try different ports and refresh the toolkit. Open the toolkit with administrator rights.
Hope this helps
Mr.Ak said:
Use the one with cm11s by Zyxxeil.Use Xp and use Qualcomm drivers,as this tool doesn't use fast boot/adb drivers and instead uses USB debugging port.
It need a few tries before device getting detected.
Make sure the device is getting recognized as "Qhs_bulk" or "Qualcomm diagnostics 9006" or some thing like that then install drivers manually.Also try different ports and refresh the toolkit. Open the toolkit with administrator rights.
Hope this helps
Click to expand...
Click to collapse
I'm on windows xp now.
Made a clean install to be sure.
Phone is connected as Qualcomm HS-USB QDLoader 9008
The Zyxxeil tool recognizes it as a com port.
When i press start, it starts flashing 8974_msimage.mbn
When it finishes it just does the same. It looks like it's stuck on a loop at flashing 8974_msimage.mbn
I would post some pictures but i can't since im a new user
Edit; It is the same as this guy; youtube (dot) com/watch?v=TOw3-yX57jM
Flashing 8974_msimage.mbn nin a loop.... you're not the only one with this problem. I couldn't find a solution to this problem so far. Have tried fresh installs of Windows XP and Windows 7 and drivers installed in Test Mode without success. Please report back once you could figure out what's wrong.
Tiic said:
I'm on windows xp now.
Made a clean install to be sure.
Phone is connected as Qualcomm HS-USB QDLoader 9008
The Zyxxeil tool recognizes it as a com port.
When i press start, it starts flashing 8974_msimage.mbn
When it finishes it just does the same. It looks like it's stuck on a loop at flashing 8974_msimage.mbn
I would post some pictures but i can't since im a new user
Edit; It is the same as this guy; youtube (dot) com/watch?v=TOw3-yX57jM
Click to expand...
Click to collapse
Got it,it's because of a bad download or corrupt zip perhaps.Redownload the toolkit and also try with Color Os toolkit too.
If your device is recognized then there's no way you can't bring it back to life.
Mr.Ak said:
Got it,it's because of a bad download or corrupt zip perhaps.Redownload the toolkit and also try with Color Os toolkit too.
If your device is recognized then there's no way you can't bring it back to life.
Click to expand...
Click to collapse
Just redownloaded the tools and tried again.
Still the same issue, i also tried the color os toolkit like you suggested.
I have the same issue too, keep installing 8974_msimage.mbn again and again.
I'm still open for sugestions since the issue is still there
Right click msm tool, and RUN AS ADMINISTRATOR.
Problem solved.
kthejoker20 said:
Right click msm tool, and RUN AS ADMINISTRATOR.
Problem solved.
Click to expand...
Click to collapse
Although it is correct that you must run it as admin, this isn't the issue at all. There are phones that appear to be broken beyond the point where you can fix it with software.
MrBrainstorm said:
Although it is correct that you must run it as admin, this isn't the issue at all..
Click to expand...
Click to collapse
Yep, i always run tools like this as admin, the issue is something else in this case, but i wouldn't know what exactly
I may have found a solution/work-around to the problem described (in case anyone's still trying to unbrick a OPO after all this time). I must warn, however, that I really have no idea what I'm doing as I'm new to all of this, and have blundered through with no real understanding of what's going on, so pay heed at your own risk. It uses Qualcomm's QFIL program and Zyxxeil's OPO unbricking tool. I want give detail in describing the steps involved, so this will be fairly long.
***background***
My 64GB OPO has for the past couple of months almost always failed to get past the first 6-7 seconds of booting, and powered off before reaching the Cyanogen animation. It did the same when booting into fastboot and recovery, and at some point it stopped being able to access recovery at all. Very rarely it would boot, but pressing the power button while it was on would cause it to crash a few seconds later. I discovered that it would consistently boot properly if volume up were tapped while holding down the power button before it vibrates and the OnePlus logo appears, but this fix simply stopped working recently, and so it became impossible to turn the OPO on. Before giving up on it, I decided it would be worth trying the hard unbricking tool based on the ColorOS installer by Zyxxeil. However, I had the problem where the tool continually repeats the step of flashing 8974_msimage.mbn without progressing any further, to which nobody ever seemed to find a solution. I may have found a way to get around the problem, however.
Even though the procedure seems to have worked, the phone still shuts down after a few seconds as it did before (so I suspect my device has a hardware problem, possibly with the power button, and there's nothing that can be done for it). This means that I can't confirm that the fix actually works, but only that it appears to have worked. What it did was:
1) unbricked the phone - it probably wasn't even bricked before, but it definitely was after the installer hung on 8974_msimage.mbn ; it wouldn't respond to the power button at all afterwards. Applying the workaround allowed it to show signs of life again.
2) installed the COS11 fastboot. I'm not sure and can't tell whether the rest of the OS is there or intact, but the fastboot logo has changed from the newer small one to the bigger one from older versions.
***the problem***
The standard method for dealing with a hard-bricked OPO is to use the ColorOS tool as described in the "[GUIDE] [UNBRICK] Unbrick Oneplus One" thread and then flash Cyanogen, or to use Zyxxeil's tool which goes straight there. A common issue in both is that after pressing start, the tools repeat the step of flashing 8974_msimage.mbn , seemingly disconnecting the phone each time, and never progressing beyond that. This happened to me as well. This will happen if the tool is not run as an administrator, but for some people the same problem is seen even if it's run as an administrator. To the best of my knowledge, nobody has posted a solution to this problem, but some have suggested using alternative methods such as using QFIL (which I have gotten to work) or MiFlash.
***potential solution***
From what I understand, QFIL does the same thing as the unbricking tool, only not automatically. I directed it to use the files provided by Zyxxeil's tool, and it was then able to do something that unbricked the device as described above. This is what I did: (all on Windows 10, *not* using the original cable)
Required files:
1) Obtain the Qualcomm QDLoader driver. I used the the Qualcomm HS-USB QDLoader 9008 2.1.0.5 x64 driver from Zyxxeil's tool's thread (page 5, #48).
2) Download Zyxxeil's tool. I used the 64GB version. Extract DRIVER.iso and run setup.exe as described. I'm not sure whether this actually did anything and presume manually installing the driver in 1) overrides this, but I'm including this for completeness.
3) Download QFIL version 1.0.0.2 . I originally used 2.0.0.5 , but this did not work (it produced the error "unable to read packet header. only read 0 bytes", to which the recommended solution was to use an older version). This can be run from the extracted folder. Open it once, and then close it again - it seems not to behave properly the first time it is run.
Preparation:
4) Create a new folder, for instance on the desktop, and give it a short name. Copy and paste (or just move) the contents of the "OnePlusRestoreTool" folder from Zyxxeil's tool into here. This step is because QFIL supposedly doesn't like long folder names or locations (I'm not sure whether this is true or not but there's no harm in making sure).
5) Install the QDloader driver: (the PC may need to be disconnected from the internet for this stage, I think Windows may try to automatically download and install incorrect drivers)
>Open device manager, then plug the OPO into the computer. It should come up after a few seconds under "Ports (COM & LPT)" as something like QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Mine originally showed up as "Quectel QDLoader 9008". If it comes up as a malfunctioned device ("Unknown USB Device") under "Universal Serial Bus controllers", try holding the power button on the OPO down for a few seconds, or holding it down for a few seconds at the same time as volume up. If it's still not recognised, try rebooting the PC and repeating this step.
>Right click on the device as it appears in device manager, select "Uninstall device", tick the box saying "Delete the driver software for this device", and click on "Uninstall".
>The OPO will disappear from device manager. Unplug and then replug it into the PC, and after a few seconds it should be recognised again, perhaps as "Unknown USB Device" again, requiring the same procedure as above. It should now show up as QHSUSB_BULK under "Ports (COM & LPT)"
>Right click on the device and select "Update driver", then "Browse my computer for driver software". Paste in the file path for the folder containing the driver as downloaded above, which will be called "20561190_ed08f7139a2028da454a6668162f44ac311facc0" if using the driver specified above. Ensure "Include subfolders" is ticked, and click on Next. This should install the driver, and because it's signed, it shouldn't present problems often encountered in this stage. Your device should now be called "Qualcomm HS-USB QDLoader 9008", with (COM#) after it.
Fix:
6) Restart the PC, leaving the phone plugged in. Open device manager again. At this point, if it is detected as a malfunctioned "Unknown USB Device", do not try to remedy it as described above - leave it as it is. This is exactly what happened in my case.
7) Run QFIL.exe as an administrator. I don't know whether this is actually necessary to run as an administrator, but seeing as problems arise in the normal methods from not doing so, it seems sensible. If the device is listed as "Unknown USB Device", then QFIL should say "No Port Available".
8) In QFIL, click on "Browse" in the "select programmer" section. Navigate to the folder where the contents of Zyxxeil's tool were copied/moved to, and open "prog_emmc_firehose_8979.mbn". Lower down, click on "Load XML", which should give you three files to choose from. As I couldn't fully boot my OPO afterwards I don't know which one is most appropriate, but I have tried the procedure with each and it worked for all of them. Perhaps start with rawprogram_unsparse.xml and if that doesn't work try the other two. Click Open, then select patch0.xml , then click Open again.
9) Paying attention to the QFIL window, hold down power+volume up until the text changes from "No Port Available" to "Qualcomm HS-USB QDLoader 9008 (COM#). Incidentally, this will also cause the device to change from "Unrecognised USB Device" to "Qualcomm HS-USB QDLoader 9008 (COM#)" in device manager. I believe that this step starts "Qualcomm's debugging mode" as explained in Zyxxeil's thread, and this is necessary for the process to work.
10) Click on "Download" (below "Load XML"). QFIL should do its thing, and if nothing has gone wrong the phone might be unbricked at the end of the process. Disconnect from the PC and see if it works.
In my experience, where this step did not work it gave one of two errors:
"unable to read packet header. only read 0 bytes" - this happens on the newer version of QFIL, which is why I used the older one.
"unable to download flash programmer using sahara protocol" - this was the troublesome one. I believe it means that the phone is not in Qualcomm's debugging mode. This would probably be the case if, for whatever reason, the PC recognised the phone immediately as Qualcomm HS-USB QDLoader 9008, and so it wasn't necessary to hold power+volume up for the PC to recognise it properly. In my case the program ran properly the first time but was interrupted because I hadn't transferred all of the right files to the target folder. After I had done this and tried again, it gave this error. I fixed this by holding down power+volume up, while the device was recognised, until the PC made a sound indicating something had been plugged in. The next attempt to download was successful.
If the procedure doesn't work properly, it might also be worth using one of the other two XML files mentioned in step 9.
*** ***
Anyway, after hours of searching and trial and error, this unbricked the phone, with it becoming responsive once more to button presses, despite still having the original problem of powering down during boot. It seems to have the CM11 fastboot as expected, and I was able to have my PC recognise it in the short time it stays on using fastboot devices. Other than that, I'm afraid I don't know how successful this was, or how successful it would be for other people. I hope this is useful nonetheless!
hi follow this guide https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
hi!
I bought a new huawei watch from china, as he arrived with my sister home, i flashed it the global version and it all worked great!
a couple days after, i updated the watch by hes wish, and it woke up stack on the huawei logo, i tried to flash the same Rom as i flashed before but it didnt worked, so i daownload another rom and tried to flash it.
i guess it was'nt the right rom and the watch is not responding ever since.
i tried to read every sulotion in this forum and to use several QFIL programs but it always give me an ERROR. "sahara server" or some thing else.
the current situation:
black scree, no response, no vibrates, no logo. "brick"i guesse
the computer detect it by "Qualcomm HS-USB QDloader 9008 (com3)
and i realy realy tried to figure it out by reading every thread i found!
be very greatful for evety one that can help me some how..
thanks ahead!
Check this thread:
https://forum.xda-developers.com/smartwatch/watch-2/rom-bootloader-recover-huawei-watch-2-t3855864
If the computer detect it only as "Qualcomm HS-USB QDloader 9008" and you cannot enter fastboot by pressing and holding power button until watch vibrates and then pressing one more time power button (one single short click) - probably QPST is your only friend ...
PS: I cannot confirm method as I never bricked my watch to try it - but this thread is the only one for un-bricking HW2
Thank you!
I already tried this for sevral times, always get the "sahara server error" you know some thing abuat it?
anyone? help with the sharafail error? searce for hours and cant find the sulotion
Please Help...
I have a Huawei watch 2 model 4G sawshark.
I Install another rom, and have BRICK
Now, my watch can connect with computer: QUALCOMM HS-USB 9008
It no vibrator, no logo,... when I charging, It hot...
I used QPST but don't ok
I need help!!!!
Sorry, my English not good, I hope everyone understand me...
I was on Masik X 4.1. Phone was working just fine.
I downloaded Masik X 5, installed it over 4.1. Flashing goes very well but at the end phone become dead.
No response on USB, No Driver on PC at all. Phone is complete dead.
Just noticed that I mistakenly downloaded "Masik P Tulip.zip" and flashed it blindly. There was no warning regarding File Mismatch in TWRP.
Very very bad luck.
I manged to bring phone into EDL Mode by testpoint method. Phone flashed successfully with both Qfil and Miflash.
Flashed many many times, tried all files available on different threads but phone is now permanently stuck in EDL mode and dont reboot after successful flashing.
Phone flashed successfully every time but I cant get rid of EDL Mode aka Qdloader 9008.
Plz help me to get my phone out of Qdloader 9008 mode.
Anybody please help me.................................
press power button for more than 30 seconds to get out of edl mode.
yawarniazi said:
I was on Masik X 4.1. Phone was working just fine.
I downloaded Masik X 5, installed it over 4.1. Flashing goes very well but at the end phone become dead.
No response on USB, No Driver on PC at all. Phone is complete dead.
Just noticed that I mistakenly downloaded "Masik P Tulip.zip" and flashed it blindly. There was no warning regarding File Mismatch in TWRP.
Very very bad luck.
I manged to bring phone into EDL Mode by testpoint method. Phone flashed successfully with both Qfil and Miflash.
Flashed many many times, tried all files available on different threads but phone is now permanently stuck in EDL mode and dont reboot after successful flashing.
Phone flashed successfully every time but I cant get rid of EDL Mode aka Qdloader 9008.
Plz help me to get my phone out of Qdloader 9008 mode.
Anybody please help me.................................
Click to expand...
Click to collapse
AFAIK , there's no such things as "automatically reboot after successfully flashed the device"
I was also in this condition but with different phone (it was Redmi 4 Prime (markw)), and all I did is just disconnect the battery form the circuit and then replug it, then I can boot to the system successfully
Hope it helps, but if it isn't then maybe something wrong