Related
*** I've been receiving many requests and PMs from members asking to help them unbrick their device. Please note that I no longer own this device (and even if I did I would not purposely brick it just to reproduce your problem), therefore I am unable to help out beyond this tutorial. ***
Hello,
First some background and credits:
There are a few ways to brick a phone. Sometimes it's lack of experience, sometimes it's an accidental thing, sometimes there just isn't an explanation for what went wrong... (share your experience here, if you wish). For me, I owned my OPO for about 4 hours before things went wrong. First thing I did was I rooted it and installed TWRP. After creating a nandroid backup of the stock image I installed my favorite custom ROM and restored all my apps with TiBu. Everything was great and configured just the way I wanted it. I then wiped my old phone (Nexus 4), installed a new ROM and got it all ready for my wife. She was so excited to get rid of her GNex and move up to the N4. But then, for whatever reason, I opened an app on my OPO that I used to manage, download, and install kernels with. It came up with "there is a new kernel update!" and I instinctively clicked on "Install". 10 seconds later my phone was bricked. Nothing came on the screen, no fastboot, no recovery, nothing to boot to, no way to send data to and from it. The second the screen went black and the phone became lifeless I got that wretched feeling in my gut as I realized I just flashed a N4 kernel on my new OPO. Restoring the kernel management app with TiBu made it act like it's still running on my old phone, and in my excitement I didn't take a second to think things through...
I received a bit of consolation when a quick XDA search revealed that I am not the only dumbass to brick his phone this very way. I joined forces with some pretty smart and desperate people and tried different things, all described in the following thread: http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696. Unfortunately it took us what seemed like many long weeks to figure it all out. Well, in the end a solution was found and I documented it in the the following post: http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136.
This was a few months ago, but I recently noticed many people continue to search for these directions and have problems finding them hidden among many pages and other threads, so I've decided to put this stand alone thread with these, now updated, directions.
Let me get one more thing straight, for the record. I did not find the way to unbrick the OPO. In fact I wasn't even the very first one to do it. It was a collective effort of few people who tried many different approaches and ideas, and I eventually documented these steps for others to follow. Being said, the following people deserve credit as well: @os_man, @rezor92, @Mnt-XDA. If I am forgetting other significant names and efforts, I apologize.
***CAUTION***
The following instructions are for hardware bricked devices ONLY and will not work on soft bricked devices. To determine whether your device is soft or hard bricked, click the button below:
Hardware brick
A hardware bricked OPO has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition. The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OPO should be detected as QHSUSB_BULK USB. You might have a bricked OPO as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition.
Software brick
Please do not attempt to use these directions if your phone is soft bricked. A software bricked OPO is one that might be stuck in a bootloop, but has a working bootloader, recovery partition, fastboot, or adb. If you press the power button and images appear on the screen and you are able to enter fastboot mode (Power + VolUP) or recovery (Power + VolDOWN) then your device is soft bricked. This thread does not encompass soft brick recovery, the instructions below do not apply and will not work on these phones. Consult other threads for help on soft bricked devices.
If based on the above explanation of differences between soft and hard bricks you determined your device is hard bricked, here's what you will need to do...
1:
Download Color.zip from (mirror needed).
After downloading, unzip the archive on your computer.
2:
Next, you need proper Windows drivers. There are architectural differences between Windows XP and Windows 7/8, so follow the directions below that pertain to you. One quick note about the drivers: the installation and process is very simple and straightforward on Windows XP (I also tested successfully on Windows 2003), but proves to be quite a challenge when running on Windows 7 or 8. Over and over people report issues when attempting the unbrick procedure on Windows 7/8, some have more luck than others. Being said, if you have access to a Windows XP computer, I highly recommend that you use that. If you have no choice but to use a Windows 7 or 8 computer and have problems, please share them here and read others' experiences.
So first, by now you probably tried a few different things to fix your phone and you've already installed some drivers, including Qualcomm USB drivers for 9006 and 9008. My best advice is to uninstall the drivers you tried so far and use the ones listed below. Go to Device Manager, right click on the bricked USB device (QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008) and go to Properties, click on Driver, then select Uninstall. Check the box to remove driver files, if prompted. Then:
2a:
Windows XP users:
You are in luck, driver installation is straightforward. Go to the extracted Color.zip folder and find Driver.iso. Extract Driver.iso. Inside the extracted folder find Setup.exe. Run Setup.exe to install the drivers. The installer is Chinese, but all you need to do is click through the prompts.
2b:
Windows 7 and Windows 8:
These operating systems block unsigned driver installations by default. Follow these steps (thanks @nag4pl for testing these):
Download and extract these Qualcomm 2012 drivers: (mirror needed).
Connect your bricked phone and let Windows do its thing.
Now something very essential you need to do here is to execute two commands to allow you to install unsigned drivers for QHUSB_BULK. Click on Start Menu > Type cmd.exe > Right Click and Run as Administrator.
In the CMD window type in the following commands (hit enter after each):
Code:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
Code:
bcdedit.exe -set TESTSIGNING ON
After both the commands should run successfully, restart your computer.
You can now proceed to install unsigned drivers from the file you downloaded. Open Device Manager, you should be seeing ugly yellow warning under other devices for QHUSB_BULK. Right click on the name and select Update Driver Software > Browse my Computer for driver software. For driver software location provide the path where you have extracted Qualcomm 2012 drivers you downloaded and make sure 'Include Subfolders' is checked. Proceed through all the installation prompts ignoring any warnings.
3:
Once you have the drivers straightened out, connect your bricked phone to the computer and start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe as Administrator (right click on Msm8974DownloadTool.exe and select "Run as administrator") from the extracted Color.zip archive. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com ports and devices. If you unplug the phone and move it to another port, it will show your bricked phone on a different line.
Clicking on "Enum" just rescans the busses. Clicking the big square button in upper right corner scans the phone and reports what's good and what's not. It takes a minute for the scan to finish.
If you don't see your phone in the list of com devices, try unplugging/plugging in your phone a couple times, and rebooting it with VolUP + Power (hold 10 seconds). You will see it in Device Manager as well.
Once you see the phone in the list, click Start. You should see the programs start writing different files to the phone. Each time it writes a file you'll see a progress bar. Once you see this process happening, smile, you know you will be good to go... After all files are written, the com line with your device will turn green. You're good, unplug and reboot your phone. It will boot to ColorOS, the Chinese OS that comes on OPO.
4:
Optional Steps:
Your phone is no longer bricked. You now have a few options to get back to stock. The easiest way is to use a toolkit from http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418, or you can flash an image manually by following directions from: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541. Download the proper image zip and after extracting it, run the following commands in fastboot mode:
Code:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
Make sure you have the proper image. I accidentally installed the 16GB version on my 64GB OPO first time and obviously didn't get 64GB of space.
That's about it. I think if people are still having problems then it's likely due to drivers, or Windows 7/8 issue.
Good luck! Share your experience here and let me know if I can improve this thread.
Please click the Thanks button if you found the above guide useful.
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
did this and it finally worked but still i have unknown baseband and no imei.........flashed coloros using the msm tool and rom goes into a bootloop......tried all the ways with no luck....even flashed the persist.img......still no luck.......my last hope is claiming warranty and act like a noob in service center.......will they get to know taht i unlocked the bootloader?
mysterio619 said:
did this and it finally worked but still i have unknown baseband and no imei.........flashed coloros using the msm tool and rom goes into a bootloop......tried all the ways with no luck....even flashed the persist.img......still no luck.......my last hope is claiming warranty and act like a noob in service center.......will they get to know taht i unlocked the bootloader?
Click to expand...
Click to collapse
You should be able to boot to fastboot now. From there flash the cm11s image. I believe that "fastboot flash sbl1 sbl1.mbn" will fix the imei issue.
Also, unlocking bootloader does not void your warranty. Not with OPO.
netbuzz said:
You should be able to boot to fastboot now. From there flash the cm11s image. I believe that "fastboot flash sbl1 sbl1.mbn" will fix the imei issue.
Also, unlocking bootloader does not void your warranty. Not with OPO.
Click to expand...
Click to collapse
Tried it......still no imei
mysterio619 said:
Tried it......still no imei
Click to expand...
Click to collapse
Just to give one last try, flash color os modded zip from relic, i used 2.0.43 purezip and it gave me back my imei. Had the same issue as you last week. Be sure to flash TWRP 2.8.4.1 first and then flash color os.
Legit method.
Worked for me 2 weeks ago!
unbrick oneplus one, oppo 7
Hi there my friend, i had many works about unbricking solutions, a few of you know that, i have much easier and faster ways now, tested many times before i decided to share with you, it will be a long topic ( and my brain is messed up to sum them up clearly), as soon i can think clearly again, i start to write them, till then,
greetings from Istanbul to all geeks around thw world.
Ps: including restoring imei's if they got lost during this process.
Ps2: just a quick info abou imei, if your imei is "invalid" , this means your modem.bin (NON-HLOS.bin, baseband) is not inadaptable with your rom, just try flashing the right modem ( from fastboot), your imei will be back.
Ps3 : This will lead us to unbrick many Snapdragon's out there , not only oneplus one's or oppo's.
I had to use this tutorial some days ago.
There is also a modified .zip where the tool from OPO flashed CM11s instead of ColorOS.
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
I had many driver problems and i had to use this driver from qualcomm so my win7 could recognize the phone.
Tutorial to install the driver:
1. Open your device manager (Start - right click on computer - properties - devices manager)
2. Press on power + vol up for like 10 sec until you see a device showing up (called QHSUSB_BULK)
3. Right click on this devices and click on "Update Driver Software" -> "Browse my computer for driver software" -> locate the Qualcomm 2012\fre\Windows7 8 or vista folder depending on your setup. Update the driver.
michaeldepotter said:
I had to use this tutorial some days ago.
There is also a modified .zip where the tool from OPO flashed CM11s instead of ColorOS.
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
I had many driver problems and i had to use this driver from qualcomm so my win7 could recognize the phone.
Tutorial to install the driver:
1. Open your device manager (Start - right click on computer - properties - devices manager)
2. Press on power + vol up for like 10 sec until you see a device showing up (called QHSUSB_BULK)
3. Right click on this devices and click on "Update Driver Software" -> "Browse my computer for driver software" -> locate the Qualcomm 2012\fre\Windows7 8 or vista folder depending on your setup. Update the driver.
Click to expand...
Click to collapse
Hi, Dropbox link for drivers seems to be wrong.. could you please update correct one.. I am in very much need of it! pls!!
nag4pl said:
Hi, Dropbox link for drivers seems to be wrong.. could you please update correct one.. I am in very much need of it! pls!!
Click to expand...
Click to collapse
Sorry. Here is the link:
https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0
Sent from my A0001 using XDA Free mobile app
michaeldepotter said:
Sorry. Here is the link:
https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you.. Troubleshooting my phone now..
may i ?
http://www.androidbrick.com/?wpdmdl=2599
Back from Brick!!
First of all Thanks a lot to @netbuzz(for such a life saver guide on unbricking 1+1) and @michaeldepotter for providing link to download appropriate drivers.
Here is some good news by my findings and can be a quick help for those who do not have or can't get XP. You can use Windows 7 itself for the process mentioned by @netbuzz
All you need to do is:
1. Download drivers from link provided by @michaeldepotter : https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0
2. Extract to some folder under C: or whichever drive you prefer.
3. Connect your bricked phone after pressing Volume Up and Power key (make sure phone vibrates once)
4. Now that QHUSB_BULK should be detected and Windows will eventually try to download drivers from update, which you can skip and close the window.
Now something very essential you need to do here is to execute some commands so that you will be able to install unsigned drivers for QHUSB_BULK.
4a. Click On Start Menu > Type cmd.exe > Right Click and Run as Administrator (make sure you are running cmd as admin)
4b. Now type below command
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
>hit Enter
bcdedit.exe -set TESTSIGNING ON
> hit Enter again
4c. Both the commands should run successfully, then restart your computer.
These steps are to disable driver sign verification. You must proceed to next steps only after above steps executed successfully.
After machine booted back to desktop
5. Now Open Device Manager by Start > Run > type "devmgmt.msc" and hit enter
6. You should be seeing ugly yellow warning under other devices for QHUSB_BULK.
7. Right click on the same > Update Driver Software > Browse my Computer for driver software
8. Now under driver software location, provide the path where you have extracted drivers which you downloaded from step 1. For me it was:
"C:\Users\Arjun\Downloads\Qualcomm 2012\fre\Windows7" - Remember to provide path only till windows 7 and make sure 'Include Subfolders' is checked.
9. Click next, and it should install driver for QHUSB_BULK. Click on Install Driver if you get any warnings.
Now your driver set-up for QHUSB_BULK in Windows 7 is complete and now you may proceed with the steps to run Msm8974DownloadTool as provided by netbuzz.
I have attached the screenshots for the same just for confirmation.
SuccessfullDriver - showing successful installation of driver
FlashInProgress - showing tool flashing the system image
FlashSuccess - showing green row indicating successful flash.
Once again, thanks a lot for all the guide and help. Hope this quick guide helps some one in need!!
nag4pl said:
First of all Thanks a lot to @netbuzz(for such a life saver guide on unbricking 1+1) and @michaeldepotter for providing link to download appropriate drivers.
Here is some good news by my findings and can be a quick help for those who do not have or can't get XP. You can use Windows 7 itself for the process mentioned by @netbuzz
All you need to do is:
1. Download drivers from link provided by @michaeldepotter : https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0
2. Extract to some folder under C: or whichever drive you prefer.
3. Connect your bricked phone after pressing Volume Up and Power key (make sure phone vibrates once)
4. Now that QHUSB_BULK should be detected and Windows will eventually try to download drivers from update, which you can skip and close the window.
Now something very essential you need to do here is to execute some commands so that you will be able to install unsigned drivers for QHUSB_BULK.
4a. Click On Start Menu > Type cmd.exe > Right Click and Run as Administrator (make sure you are running cmd as admin)
4b. Now type below command
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
>hit Enter
bcdedit.exe -set TESTSIGNING ON
> hit Enter again
4c. Both the commands should run successfully, then restart your computer.
These steps are to disable driver sign verification. You must proceed to next steps only after above steps executed successfully.
After machine booted back to desktop
5. Now Open Device Manager by Start > Run > type "devmgmt.msc" and hit enter
6. You should be seeing ugly yellow warning under other devices for QHUSB_BULK.
7. Right click on the same > Update Driver Software > Browse my Computer for driver software
8. Now under driver software location, provide the path where you have extracted drivers which you downloaded from step 1. For me it was:
"C:\Users\Arjun\Downloads\Qualcomm 2012\fre\Windows7" - Remember to provide path only till windows 7 and make sure 'Include Subfolders' is checked.
9. Click next, and it should install driver for QHUSB_BULK. Click on Install Driver if you get any warnings.
Now your driver set-up for QHUSB_BULK in Windows 7 is complete and now you may proceed with the steps to run Msm8974DownloadTool as provided by netbuzz.
I have attached the screenshots for the same just for confirmation.
SuccessfullDriver - showing successful installation of driver
FlashInProgress - showing tool flashing the system image
FlashSuccess - showing green row indicating successful flash.
Once again, thanks a lot for all the guide and help. Hope this quick guide helps some one in need!!
Click to expand...
Click to collapse
Thanks for this Win7/8 workaround. I'll be adding your info to the OP.
Finally Unbricked mine...Drivers resolved on Win 7
netbuzz said:
Second note about drivers is that I had the worst time trying to get things to work on my Windows 7 computers. Both Windows 7 and 8 block unsigned driver installations by default. I've tried overwriting these settings in Windows and spent half a day messing with it, and I never got things to work properly. At first all looked good to go, but then latter steps were failing. You might have a better luck getting drivers to work on Windows 7 or 8 (I've heard some people did it), but if you have access to a Windows XP or 2003 machine, try it first, it should save you some major headache.
Once you have the drivers straightened out, connect your bricked phone to the computer and start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe from the extracted Color.zip archive. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com ports and devices. If you unplug the phone and move it to another port, it will show your bricked phone on a different line.
Click to expand...
Click to collapse
I have used the override tool for certificates: DSEO - Driver signature enforcement overrider
to allow the unsigned drivers to be used and it worked like charm on windows 7 64 bit.
Also, I used the additional Qualcomm 2012 drivers and not sure which one might got picked in that mess :cyclops::cyclops:
Thanks!!
:good::good::angel::angel:
nevermind!
Well I managed to hardbrick my phone. I am download the ColorOS file from Mega at the moment. It's downloading at 30KB/s and will take around 6.5 hours. Is there any other source to download it from ? Thanks !
Also, about the driver ...
While I wait on the colorOS to download I want to clarify one more thing about the driver.
According to the screenshot of @nag4pl the driver should show as Qualcomm USB diagnostic 9006, while for me it shows as Qualcomm HS-USB QDloader 9008. Is this going to be an issue ?
This is what I did. I uninstalled the default driver that came with windows 7. After that it failed to install the driver provided in this forum because it kept saying that device descriptor failed. I rebooted the phone several times and changed the USB ports and eventually windows detected it but AGAIN with the windows driver even though I had checked the option to delete the original driver while uninstalling it. Through the update driver option I managed to force it to install the unsigned driver.
Now I can see both the drivers under the update drivers option. Interestingly the default driver is a version ahead of the unsigned driver provided in this forum.
My only concern is that I see a different driver name compared to the one posted by @nag4pl
Thanks! Very useful for me!
That shouldn't be a problem. Not sure if that is specific to region, mine is India version phone.. Can some one clarify on this?
Hello everybody !
I 've spend a long time on this forum and i've found a lot of interesting and useful tips.
I'm in a bad situation today and I can not find a solution so i thank you for the time spent reading this.
Yesterday i've seen an icon on my desktop and i couldn't remember what application it is. I clicked and it was the beginning of an endless nightmare... A huge lag began by making the phone unusable and apps was installing one after one...
When it has calmed down a bit, i tried to install cleaning softwares but i couldn't do anything so I tried to do a factory reset. After that... the malware was still here... So i've decided to clean all by installing a new ROM.
This is a Jiayu S3 4G 5.5 Inch MT6752 Octa Core RAM 3GB 1080P Screen Dual SIM 4G LTE Mobile Phone (invoice description) so i wanted to try the CM12.1 for Jiayu S3 (found on needrom).
My phone was Rooted and TWRP was installed so i've copied the ROM files on a SD card, rebooted in recovery mode, wiped cache, data, dalvic and system and tried to install the new ROM. it was abnormally rapid and now the phone bootloops.
The only thing i can do is activate Fastboot (if i choose normal boot or recovery it continues to bootloop).
I've tried to flash recovery with :
fastboot flash recovery recovery.img
but i get an error message : FAILED (remote : partition 'recovery' not support flash).
Does anyone has ever been in this situation and solved it ?
Thanks for your help !
Hello,
I got exactly the same problem. Did you find a solution?
My phone is in a bootloop, I can only access to the fastboot mode. (fastboot devices show my device).
In this mode, I can't flash my recovery.img:
fastboot flash recovery recovery.img --> partition 'recovery' not support flash.
I can't see my device with the command adb devices (adb devices doesn't show my device, I think because USB debugging is off, but i can't switch it on)
Did someone find a solution ?
Any help would be appreciated, thanks !
That's the behavior of a wrong preloader that was flashed / malware that affected preloader.
Grab a full spftools ROM set, and flash the entire ROM using " upgrade mode"
Cheers
PS: on s3 you need to have both volume buttons pressed, then you can press download on the spft.
PPS: this will destroy all of your data, so back it up first ..
Thanks for your answer.
So, I downloaded latest version of Flash_Tools, but i can't find any complete set for flashing... only recovery.img (I'm searching on needrom.com). Do you have a place to find these?
>PS: on s3 you need to have both volume buttons pressed, then you can press download on the spft.
I think i got another problem: with Flash_Tools, I'm unable to flash anything to my device... There is a special mode to launch, as you explained, but it seems I can't access it... By pressing both up and down volume button, the phone should boot on a special mode ? How can I know if the phone is booted in this mode ? The USB cable must be plugged before/after booting the phone in this mode ?
mick605 said:
Thanks for your answer.
So, I downloaded latest version of Flash_Tools, but i can't find any complete set for flashing... only recovery.img (I'm searching on needrom.com). Do you have a place to find these?
>PS: on s3 you need to have both volume buttons pressed, then you can press download on the spft.
I think i got another problem: with Flash_Tools, I'm unable to flash anything to my device... There is a special mode to launch, as you explained, but it seems I can't access it... By pressing both up and down volume button, the phone should boot on a special mode ? How can I know if the phone is booted in this mode ? The USB cable must be plugged before/after booting the phone in this mode ?
Click to expand...
Click to collapse
There is no special mode, please serach the forum on how to use sptools, i am sure you will find plenty of them.
Sorry for late answer !
Thanks for this advice, i will try as soon as possible and post if it's ok or not.
Hello everybody !
Ok, I got it !
My problem came from the drivers... But not the ADB drivers, the preloader drivers.
In the Windows device manager, when I plugged my phone (previously swithced off), I got a "MT65xx Preloader" device with a warning. Be careful, this item stay 2 or 3 seconds before disappearing ! This driver wasn't installed correctly, that's why Flash Tools didn't worked for me (it didn't see my phone) !
So, I got the driver on the web, by typing "MT65xx Preloader driver", I got the drivers that I installed. This guide gave me the files and a method to install them:
http: //laurentiumihet.ro/sp-flash-tool-mediatek-mt65xx-drivers-download-and-installation-guide-including-bricked-devices/ (can't post links, delete space after http: )
To install the driver, you can set up manually by right clicking on the "MT65xx Preloader" > "Update drivers". Then, browse to the drivers you previously downloaded (a folder containing .inf and .sys files). Windows should detect the driver and install it.
To check if the preloader driver is correctly installed, power off your phone and unplug it, them plug it. Instead of the previous "MT65xx Preloader" entry, you should now see a "MediaTek PreLoader USB VCOM Port" under "Ports (COM & LPT)" (same as before, this item is displayed only 2-3 seconds...).
Now that the preloader driver is correctly installed, Flash Tools works for me. I successfully flashed a new rom I got from needrom.com (a full set, as suggested by superdragonpt), and my phone boots now =)
Thanks all for your answers ! Xehon, hope it will works for you !
Thanks mick605 !
I travel for work so i can't try all the advices on this forum atm.
I'll check this when i get back home and i'll tell you if it's ok
Thanks again !
mick605 said:
Hello everybody !
Ok, I got it !
My problem came from the drivers... But not the ADB drivers, the preloader drivers.
In the Windows device manager, when I plugged my phone (previously swithced off), I got a "MT65xx Preloader" device with a warning. Be careful, this item stay 2 or 3 seconds before disappearing ! This driver wasn't installed correctly, that's why Flash Tools didn't worked for me (it didn't see my phone) !
So, I got the driver on the web, by typing "MT65xx Preloader driver", I got the drivers that I installed. This guide gave me the files and a method to install them:
http: //laurentiumihet.ro/sp-flash-tool-mediatek-mt65xx-drivers-download-and-installation-guide-including-bricked-devices/ (can't post links, delete space after http: )
To install the driver, you can set up manually by right clicking on the "MT65xx Preloader" > "Update drivers". Then, browse to the drivers you previously downloaded (a folder containing .inf and .sys files). Windows should detect the driver and install it.
To check if the preloader driver is correctly installed, power off your phone and unplug it, them plug it. Instead of the previous "MT65xx Preloader" entry, you should now see a "MediaTek PreLoader USB VCOM Port" under "Ports (COM & LPT)" (same as before, this item is displayed only 2-3 seconds...).
Now that the preloader driver is correctly installed, Flash Tools works for me. I successfully flashed a new rom I got from needrom.com (a full set, as suggested by superdragonpt), and my phone boots now =)
Thanks all for your answers ! Xehon, hope it will works for you !
Click to expand...
Click to collapse
First of all hi I'm new in this thread,
I have installed everything correctly but I still have only 3 seconds before my phone showes the the charging icon and disconnects.
Can anybody please help me? I actually have been stuck with this problem for months now and all these months I have been using the samsung galaxy s advance (launched in 2011) on marshmallow.
First of all, i have read some similar threads about this, and all advise diffrent solution besides the hardware mod, I have tried for 2 days all methods in Miui forums and none have worked for me except the hardware method.
My Device: Xiaomi Redmi Note 3 Pro / SD version.
State:
-would only show "Mi" logo when powered on.
-Would enter only Fastboot.
- No EDL mode
- No recovery
-bootloader locked
-In this state, you can't flash absolutely nothing with any software. (from fastboot).
Requirements:
- windows 7/ windows 10 x64 edition.
- ONLY LATEST version of miflash, from 2016 onward, so it has the required drivers and methods to work with the phone. (I have tried with older versions and it did not work, i thought there was no hope for my phone).
- one hard bricked Redmi Note 3 Pro
- any fersion of Stable FASTBOOT OFFICIAL rom. (.tgz extension) - I personally used kenzo_global_images_V7.2.3.0.LHOMIDA_20160129.0000.14_5.1_global_c85ba6c524.tgz
- medium disassembly skills,
- a lot of patience,
- minimum set of tools (one small cross screwdriver, 1-2 strong finger nails, good eyesight).
- one microusb cable
HOW TO:
1. uninstall all drivers and software related to the Xiaomi phone. (I ended up reinstalling windows 7 just to be sure all was gone - that is how desperate I became). To be sure this is done correctly, with the phone turned off, connect it to the computer.
Go into device manager, search in com ports, or wherever any drivers are installed for the phone, and uninstall all of them, ticking remove driver files also.
after doing this, hit refresh, and see if any drivers get installed again.
Repeat until there are no drivers installed, and the device will be without a driver.
2. Disconnect the phone and RESTART WINDOWS
3. Disable driver signature verification/enforcement:
a. in windows 7, this is easy: restart windows, hit f8 until a menu pops up where you can choose disable driver signature verification/enforcement.
b. in windows 10, it is a little bit longer, but: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/ - Be careful, when choosing the option in the last menu, use F... keys, not number keys.
4. while in windows, in the bottom right corner, there should be a message saying "test mode"
5. install ONLY the LATEST VERSION of Miflash! you may get some messages about driver installation (2 times), allow installation!
6. RESTART WINDOWS
7. Prepare the phone!: I followed the video here, even I did not understand the language: http://choimobile.vn/threads/video-...o-snapdragon-650-fix-download-mode-edl.65098/
- First, I used my nail to open the phone up, just like in the video. It is great that the screen is not glued to the body, there are only some clips holding it in place!
- after opening the cover please be careful - there is a cable connecting the case to the mainboard - the fingerprint sensor.
- after this, unscrew the 7 or 8 screws as in the video.
- unlock the cables as in the video - please be sure not to disconnect all the cables.
- now, first get the antenna plastic cover outside of the way.
- after disconnecting the camera module, I would personally advise you to get the camera out of the way first, as there is a piece of foil glued between the mainboard and the underneath of the camera module (on the display)
- with great care, rise the Mainboard from the display.
- to have better access to the testpoint pins, I turned the Mainboard over the battery.
- now, connect the microusb cable to the phone.
8. connect the phone to the computer.
9. go into device manager and check if there are any devices installed, there should be under ports.... a device called Qualcomm HS-USB Diagnostics 900E.
10. Now comes the tricky part, switching the phone to EDL mode (emercency download)
look on the back of the motherboard of the phone to connect the 2 testpoint pins as in the video. You can use anything to do this. a metal wire, a small scissors, an untied paperclip... You will have to do this while device manager is opened, as you must check it when the driver changes to "qualcomm hs-usb qdloader 9008".
Please be careful when trying to connect the 2 pins not to touch any metal housing, ans this will restart the device each time.
Now, try and try and try until the driver changes to "qualcomm hs-usb qdloader 9008".
11. unzip the rom using 7 zip to a destination of your choosing. I advise as short destination as possible and no spaces used in the folder naming. I unpacked it in C:\rom\
12. Open Miflash
13. As per other many many instructions:
a. click browse - select the folder where you unpacked the rom (for me, c:\rom\)
b. click the arrow next to brows button and select advanced.
c. in the first field, navigate to the folder where the rom was unpacked and select flashall.bat
d. in the third field select prog_emmc_firehose_8976_ddr.mbn from the "images"folder in the folder whre he rom was extracted
e. field 7: rawprogram0.xml and field8: patch0.xml
f. Hit the Refresh button, the device should appear as a com port in the white field of Miflash.
g. just to be sure, tick also "flash all" in the bottom of miflash.
14. Hit the Flash button on Miflash and this should be the last step before powering up your revived Xiaomi Redmi Note 3.
This is what I learned in the past 2-3 days.
Different errors I got during the learning process and what i did to avoid them:
- different problems with drivers not installing correctly or showing different device names - just use the method i pointed out in the beginning to uninstall any driver previously installed on the computer, with the refresh in device manager and than uninstalling all.
- "end of package" error at second 2 while flashing in Miflash - you are using an older or an unsupported version of miflash, just use the latest one.
- not being able to flash anything while in fastboot - if you have a locked bootloader, on redmi note 3 snapdragon version, you simply won't be able to flash anything. end of story. this is the whole purpose of having a locked bootloader.
- trying to go into EDL mode using fastboot comand "fastboot oem eld" - this will not work for a really bricked device as was mine. the only solution is to go through the tespoint pin connection.
i wonder if there's a way not to make trwp locked in the recovery partition, so if someone flashes a factory rom without precaution, twrp will simply get overwritten by factory recovery. Wouldn't that prevent these hard bricks?
btw, nice guide
Please move the thread into guides/tutorial section.
Well, mine was bricked too 2 days ago... even I already unlock the bootloader using the official way.
It happened because I'm on AOSP and I flash Xiaomi.EU ROM from TWRP.
'MI' Logo flashed twice then the phone turns off itself.
It can't boot, can't enter EDL mode. I just can go into fastboot mode. But nothing can be done there because it always says 'device is locked'.
'fastboot oem device-info' also says the phone is on locked state.
Dunno why this happen, I think its because I play with the unlock bootloader toggle on previous MIUI and AOSP ROM.
After countless of times trying to get into EDL, I give up.
Device manager always show "QCom HS-USB Diagnostic 900E" instead of "QCom HS-USB QLoader 9008"
Finally I try the official Mi Unlock software, re-unlock success and BAM... Phone boots again into system. lol...
This makes me think the bricked problem can prevented/solved to by:
- At least bind a Xiaomi Account to your phone once when using official ROM (recommended China Dev ROM)
- Use that account to apply for the unlock, and when you got the phone bricked/relocked, you can re-unlock it using official way to revive the phone
Now is possible unbrick without disassembly:
http://en.miui.com/thread-267263-1-1.html
http://www.htcmania.com/showthread.php?t=1174700
jujusito said:
Now is possible unbrick without disassembly:
http://en.miui.com/thread-267263-1-1.html
http://www.htcmania.com/showthread.php?t=1174700
Click to expand...
Click to collapse
please read through all the thread, don't just throw in a link. the method mentioned by you will not work on some bricked devices, including mine. this did not work for me, so I ended up disassembling the phone.
aabenroi said:
Well, mine was bricked too 2 days ago... even I already unlock the bootloader using the official way.
It happened because I'm on AOSP and I flash Xiaomi.EU ROM from TWRP.
'MI' Logo flashed twice then the phone turns off itself.
It can't boot, can't enter EDL mode. I just can go into fastboot mode. But nothing can be done there because it always says 'device is locked'.
'fastboot oem device-info' also says the phone is on locked state.
Dunno why this happen, I think its because I play with the unlock bootloader toggle on previous MIUI and AOSP ROM.
After countless of times trying to get into EDL, I give up.
Device manager always show "QCom HS-USB Diagnostic 900E" instead of "QCom HS-USB QLoader 9008"
Finally I try the official Mi Unlock software, re-unlock success and BAM... Phone boots again into system. lol...
This makes me think the bricked problem can prevented/solved to by:
- At least bind a Xiaomi Account to your phone once when using official ROM (recommended China Dev ROM)
- Use that account to apply for the unlock, and when you got the phone bricked/relocked, you can re-unlock it using official way to revive the phone
Click to expand...
Click to collapse
I also applied for an unlock code, but this takes up to 15 days, and I have the phone for only 3 days . I could not wait for the code, I had to do something to revive it.
meangreenie said:
i wonder if there's a way not to make trwp locked in the recovery partition, so if someone flashes a factory rom without precaution, twrp will simply get overwritten by factory recovery. Wouldn't that prevent these hard bricks?
btw, nice guide
Click to expand...
Click to collapse
I made a modified TWRP which will not cause hard bricks
Rajdip said:
I made a modified TWRP which will not cause hard bricks
Click to expand...
Click to collapse
great work! your modded twrp will no doubt save me when i forget i have to delete the emmc file in the future.
Dear, thank you for your contribution, this deserves to be a section more important, really saved my phone from the hard brick. Again very grateful
how do i know what a test point looks like on any phone? like the new redmi 3s? i cant get into edl because im stuck in Qualcomm HS-USB Diagnostics 900E
xdarkmario said:
how do i know what a test point looks like on any phone? like the new redmi 3s? i cant get into edl because im stuck in Qualcomm HS-USB Diagnostics 900E
Click to expand...
Click to collapse
maybe look for something like this?
http://choimobile.vn/Temp/Testpoint_Redmi_Note3_PRO_3.jpg
I doubt they will have much variance from xiaomi phone to phone to make it easy for factory / repair centers to fix many models... (I could be wrong though), other brands are probably different.
Well you can enter edl mode from fastboot via this simple tool
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
And then you can flash any miui .tgz based rom and resurrect.
I hard bricked my Device last night and resurrected
PS : you must have the MiPcSuit installed
ilvmyname said:
Well you can enter edl mode from fastboot via this simple tool
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
And then you can flash any miui .tgz based rom and resurrect.
I hard bricked my Device last night and resurrected
PS : you must have the MiPcSuit installed
Click to expand...
Click to collapse
links dead
Quick addition: if you're using Virtual Box, like me (on a mac), you need to enable USB 2.0 on the virtual machine. On Virtual Box, this means you have to add an extension pack. This might save you 48hrs, like it cost me
please help me unbricking my device currently i am unable to boot into edl, fastboot or recovery. The phone keeps on vibrating and no display.
What i did wrong was that I tried flashing a custom boot logo as said in a thread and flashed splash.img and it resulted in this.
Please help me!!!
Akshatpunj said:
please help me unbricking my device currently i am unable to boot into edl, fastboot or recovery. The phone keeps on vibrating and no display.
What i did wrong was that I tried flashing a custom boot logo as said in a thread and flashed splash.img and it resulted in this.
Please help me!!!
Click to expand...
Click to collapse
ok here what u do:
1. I know the device isn't getting charged, no logo.no recovery,no flash-boot,even won't get detected on windows but,don't panic... first thing is to believe in urself that u can fix that device...
2.. second powering of ur device, so to do that observe the vibrate pattern carefully... very carefully... you'll notice while holding up the power after some vibrations(for me 12) it'll skip one vibration.that's the moment my friend release the power button.
3. so now u have to flash the ROM with QFIL & the cyanogen QFIL file ...
4. now before get into the process make sure u download all the drivers(ZUK drivers & Qualcomm Drivers)
5. installing drivers:
boot ur system into the state that ensures driver signature verification is disabled install zuk drivers if u haven't.
now install Qualcomm Drivers depending upon ur system
6. install Qpst
7. now unzip the ROM.
8. run Qpst as admin
9. select the flat build mode on Qpst and browse the extracted rom folder...u'll get to see the ".mbn " file, select it , load XML
10. now the most important thing press the vol+ button and plug the device (it won't get detected),now after 1sec of pluging it press power button it''ll get detected and press the download button ....
11. wait for the flash....get a cup of coffee..
12. u'll get a messege like download success... u r done mate..
links :
drivers: https://mega.nz/#!FJRH2b6B!QlS9-7ppEiP9Nw_htWSMtYQWOk9KDxDxImtJZ66usaw
QPST: https://mega.nz/#!dcAQgSZT!C5JhNLnsOru6y_cX52yGzMkgfnriBY0am7nW45Bzsm0
rom: https://mega.nz/#!dFpn3BYb!Eq2i2ldpA8UJnlkjijCh4fM7EdLSaleWBRmW5rJNI84
ADDICTED777 said:
ok here what u do:
1. I know the device isn't getting charged, no logo.no recovery,no flash-boot,even won't get detected on windows but,don't panic... first thing is to believe in urself that u can fix that device...
2.. second powering of ur device, so to do that observe the vibrate pattern carefully... very carefully... you'll notice while holding up the power after some vibrations(for me 12) it'll skip one vibration.that's the moment my friend release the power button.
3. so now u have to flash the ROM with QFIL & the cyanogen QFIL file ...
4. now before get into the process make sure u download all the drivers(ZUK drivers & Qualcomm Drivers)
5. installing drivers:
boot ur system into the state that ensures driver signature verification is disabled install zuk drivers if u haven't.
now install Qualcomm Drivers depending upon ur system
6. install Qpst
7. now unzip the ROM.
8. run Qpst as admin
9. select the flat build mode on Qpst and browse the extracted rom folder...u'll get to see the ".mbn " file, select it , load XML
10. now the most important thing press the vol+ button and plug the device (it won't get detected),now after 1sec of pluging it press power button it''ll get detected and press the download button ....
11. wait for the flash....get a cup of coffee..
12. u'll get a messege like download success... u r done mate..
links :
drivers: https://mega.nz/#!FJRH2b6B!QlS9-7ppEiP9Nw_htWSMtYQWOk9KDxDxImtJZ66usaw
QPST: https://mega.nz/#!dcAQgSZT!C5JhNLnsOru6y_cX52yGzMkgfnriBY0am7nW45Bzsm0
rom: https://mega.nz/#!dFpn3BYb!Eq2i2ldpA8UJnlkjijCh4fM7EdLSaleWBRmW5rJNI84
Click to expand...
Click to collapse
Thank you sooooooo muchh!!! I almost tried everything and lost hope! This method worked like a miracle, i wish i could hit the thanks button a 1000 times! Thanks again!
Akshatpunj said:
Thank you sooooooo muchh!!! I almost tried everything and lost hope! This method worked like a miracle, i wish i could hit the thanks button a 1000 times! Thanks again!
Click to expand...
Click to collapse
Always remember mate...
Computers & smartphones are such a thing u can't damage them until and unless u broke them... so do whatever u wanna try ... test them out... so be productive n believe in urself that u can..
ADDICTED777 said:
Always remember mate...
Computers & smartphones are such a thing u can't damage them until and unless u broke them... so do whatever u wanna try ... test them out... so be productive n believe in urself that u can..
Click to expand...
Click to collapse
Sure, thanks for the advice.
Btw were you able to change the splash.img/boot logo?
This state isn't named as it is hard bricked ...if it was it won't even vibrate at all...that's we call it as a hard bricked device... it was soft bricked .... in a BOOOOOOOTLOOOOOOOOOOP...
There r various type of bootloops
---------- Post added at 06:54 PM ---------- Previous post was at 06:49 PM ----------
Akshatpunj said:
Sure, thanks for the advice.
Btw were you able to change the splash.img/boot logo?
Click to expand...
Click to collapse
Oh yeah two times...listen here the main thing for the devices is to choose the r8 image...should be less then 200kb & as much as less color... make sure to do it with 16bit(or less) for PNG
ADDICTED777 said:
This state isn't named as it is hard bricked ...if it was it won't even vibrate at all...that's we call it as a hard bricked device... it was soft bricked .... in a BOOOOOOOTLOOOOOOOOOOP...
There r various type of bootloops
---------- Post added at 06:54 PM ---------- Previous post was at 06:49 PM ----------
Oh yeah two times...listen here the main thing for the devices is to choose the r8 image...should be less then 200kb & as much as less color... make sure to do it with 16bit(or less) for PNG
Click to expand...
Click to collapse
Oh ok! I thought i hard bricked my device but luckily you helped me
Okay i will try to change boot logo tomorrow again. Thanks a lot!
Akshatpunj said:
Oh ok! I thought i hard bricked my device but luckily you helped me
Okay i will try to change boot logo tomorrow again. Thanks a lot!
Click to expand...
Click to collapse
Yo there is a button for that ...u know I'm kind of GREEDY...
ADDICTED777 said:
Yo there is a button for that ...u know I'm kind of GREEDY...
Click to expand...
Click to collapse
Already done...
ADDICTED777 said:
Always remember mate...
Computers & smartphones are such a thing u can't damage them until and unless u broke them... so do whatever u wanna try ... test them out... so be productive n believe in urself that u can..
Click to expand...
Click to collapse
I have the same problem. I went to flash a boot image and I messed up. QFIL does not detect my phone maybe beacuse Qualcomm drivers are not getting installed using the INF file.
I have shut the vibrations using the power button step. But as soon as I plug it in with volume up held down, it starts all over again.
---------- Post added at 12:26 PM ---------- Previous post was at 11:43 AM ----------
I have disabled the driver signature verification while rebooting using F8 key.
However, I still get the same error message while installing the INF file that The INF file you selected does not support this method of installation.
---------- Post added at 12:36 PM ---------- Previous post was at 12:26 PM ----------
Please help!!!!
Sahaj Desai said:
I have the same problem. I went to flash a boot image and I messed up. QFIL does not detect my phone maybe beacuse Qualcomm drivers are not getting installed using the INF file.
I have shut the vibrations using the power button step. But as soon as I plug it in with volume up held down, it starts all over again.
---------- Post added at 12:26 PM ---------- Previous post was at 11:43 AM ----------
I have disabled the driver signature verification while rebooting using F8 key.
However, I still get the same error message while installing the INF file that The INF file you selected does not support this method of installation.
---------- Post added at 12:36 PM ---------- Previous post was at 12:26 PM ----------
Please help!!!!
Click to expand...
Click to collapse
u need a video tutorial that shows how to install .inf file
here is the one:
https://www.youtube.com/watch?v=lJ7WTRW7psA
Now before u proceed make sure u have disabled the driver signature verification.
ADDICTED777 said:
u need a video tutorial that shows how to install .inf file
here is the one:
Now before u proceed make sure u have disabled the driver signature verification.
Click to expand...
Click to collapse
I did it using Qualcomm drivers in .exe format.
Now the phone is working fine.
Sahaj Desai said:
I did it using Qualcomm drivers in .exe format.
Now the phone is working fine.
Click to expand...
Click to collapse
:good::good::good:
Hei!!! You are the best. I followed your instructions and it seems it works 100%. You saved my day. I cant thank you enough.
ADDICTED777 said:
ok here what u do:
1. I know the device isn't getting charged, no logo.no recovery,no flash-boot,even won't get detected on windows but,don't panic... first thing is to believe in urself that u can fix that device...
2.. second powering of ur device, so to do that observe the vibrate pattern carefully... very carefully... you'll notice while holding up the power after some vibrations(for me 12) it'll skip one vibration.that's the moment my friend release the power button.
3. so now u have to flash the ROM with QFIL & the cyanogen QFIL file ...
4. now before get into the process make sure u download all the drivers(ZUK drivers & Qualcomm Drivers)
5. installing drivers:
boot ur system into the state that ensures driver signature verification is disabled install zuk drivers if u haven't.
now install Qualcomm Drivers depending upon ur system
6. install Qpst
7. now unzip the ROM.
8. run Qpst as admin
9. select the flat build mode on Qpst and browse the extracted rom folder...u'll get to see the ".mbn " file, select it , load XML
10. now the most important thing press the vol+ button and plug the device (it won't get detected),now after 1sec of pluging it press power button it''ll get detected and press the download button ....
11. wait for the flash....get a cup of coffee..
12. u'll get a messege like download success... u r done mate..
Click to expand...
Click to collapse
hey bro I just accidentally rebooted my zuk z1 in edl mode via all in one tool, but after rebooting in edl mode, screen went off and it didn't boot up again and now pc is not recognizing my device nor does the qfil detects it, its power button does not work so tried it while holding the volume up button but it's not working. I have got qpst file and zuk drivers are also installed. now please someone help me out bro. ;(
Walter Black said:
hey bro I just accidentally rebooted my zuk z1 in edl mode via all in one tool, but after rebooting in edl mode, screen went off and it didn't boot up again and now pc is not recognizing my device nor does the qfil detects it, its power button does not work so tried it while holding the volume up button but it's not working. I have got qpst file and zuk drivers are also installed. now please someone help me out bro. ;(
Click to expand...
Click to collapse
keep it charged overnight... fix the power button...then try the mentioned method...
ZUK Z1 Hard Bricked
Greetings, everyone. I've got a hard bricked zuk z1 which just went into the state all of a sudden.
I was using lineage o.s pie roms, and had faced some Random Reboots also. Not sure what happened, but here's what i did:
Installed zuk drivers
installed qualcomm drivers
installed adb and fastboot(minimal abd and fastboot)
installed qfil, which comes with QPST v2.7.0.460
--------------------------------------------------------------------------------
Downloaded the zuk stock firmware files
pressed vol+ and plugged the usb
Got detected in 9008 mode
QFIL also detected it and chose the correct files and started downloading in FLAT build
mode
now, QFIL shows this error at the end:-
Code:
10:17:52: INFO: Looking for file 'gpt_main0.bin'
10:17:52: INFO: Looking for file 'gpt_backup0.bin'
10:17:52: INFO:
Total to be tansferd with <program> or <read> is 78.85 MB
10:17:52: INFO: Sending <configure>
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
10:18:17: {ERROR: Could not write to '\\.\COM3', Windows API WriteFile failed! Your device is probably *not* on this port, attempted 100 times}
Writing log to 'C:\Users\HARRY\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt', might take a minute
Log is 'C:\Users\HARRY\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt'
Download Fail:FireHose Fail:FHLoader Fail:Process fail
Finish Download
Hope someone can help me . Oh, by the way, the bricking is like "fully-dead" bricking. No vibrations, display, led, nothing.
I feel i haven't done anything wrong in the steps also. SO, How to decode this situation??
i am face same problem "help please expert" my zuk z1 show logo and blew light after 10se not display on screen when touch with pc via usb many partition opening with error how to solve it
Hard partition damaged
helo expert zuk z1 vibrate and show blue light black screen no display after firmware via qfil completed on PC many partition apeared not writeable only show a partition with "image" folder in witch all firmware file stored who write via qfil
naseera422 said:
helo expert zuk z1 vibrate and show blue light black screen no display after firmware via qfil completed on PC many partition apeared not writeable only show a partition with "image" folder in witch all firmware file stored who write via qfil
Click to expand...
Click to collapse
Hello there!. As far as i know, from what you've said,
The phone still vibrates and shows led, which is a good thing.
About the qfil:
Check whether you are using the latest version of QFIL. Many errors did arise while using the earlier ones.
Make sure you haven't messed up any QFIL configuration settings, and check whether the selected build type is "FLAT".
If you are having trouble with the current firmware files, then download another one for the zuk z1, and check if it works. This is because errors can come from wrong/bad programmer files.
::::: This is all assuming that there are no driver issues & that you know well, how to work with QFIL :::::
Hope this helps....
Hi guys
At first - I tried a method given on this forum: https://forum.xda-developers.com/mi-a1/help/phone-goes-to-qualcomm-hs-usb-qdloader-t3757867
This method doesn't work for me, because after disconnect my PC doesn't recognize my phone.
Phone is in Qualcom HS-USB Diagnostics 900E mode after OTA update (Mi A1 April Update) - strange
So guys... I know there are some magicians who can do almost everything.. Any ideas what to do?
Does MiFlash recognize your phone? If not, try instaling ADB drivers nd disable driver enforcment,
To kick device out of diagnostic mode and into QDLoader you will need either:
1) A "deep flash" cable
2) Take the phone apart and bridge test points
There are guides online for both, you can Google. You can make deep flash cable yourself fairly easily with a spare USB cable. Testpoint location is found easily via Google and can be bridged with tweezers or small flat-head screwdriver.
I did NOT have success with deep flash cable myself, I had to use testpoint method (and sadly broke my LCD in the process). The deep flash issue might of been because I was in Windows 10 x64 or on a USB3 port. If you do go that route and can't get it working, try with a Windows 7 x86 VM and USB2 passthrough mode before last resort of taking device apart.
Hold power button for 20 sec then volume down and fastboot will apear
1. install all necessary drivers (adb, qualcomm's HS-USB Diagnostics 900E, xiaomi flash tool)
2. use test point method as suggested by @CosmicDan - lots of tutorial on web on how to do this. Carefully read this before actually attempting it.
3. When you successfully do the test point method you will hear the device recognized sound on your computer
4. when you hear it, open miflashtool and your device should show up in it.
5. if not, reboot your PC. You should reboot your PC after installing all the drivers. See #1. (reboot required)
6. Once you successfully see your device on miflashtool, you can flash the fastboot rom of your choice.
7. (you might get stuck on "Can't receive hello packet" dialogue which will prevent your device from flashing), in that case change the USB port, possibly to USB 2.0 and try the test point flash method again to get detected and try flashing again.
8. Test point method should be done everytime you disconnect the USB from your phone and computer, hopefully you only need to do it twice.
9. Sadly for me, I am still unable to flash stock roms with this method, my problem is kind of unique, after flashing it shows me "Your phone is destroyed, press power to turn off" dialogue. lmao
10. if you get the same message then you dun goof'd. Hopefully yours will successfully flash.
Oh and only one version of fastboot ROM actually revives the phone, other fastboot roms actually puts it to coma (vibrating every one second, no display, no nothing). Only one fastboot ROM allows me to go to fastboot and flash recoveries. But if I flash any ROM (stock or custom) it kills the phone again and I have to repeat the given method and try again with another rom. I think the phone is effectively dead. What a **** phone! lol
udaan said:
1. install all necessary drivers (adb, qualcomm's HS-USB Diagnostics 900E, xiaomi flash tool)
2. use test point method as suggested by @CosmicDan - lots of tutorial on web on how to do this. Carefully read this before actually attempting it.
3. When you successfully do the test point method you will hear the device recognized sound on your computer
4. when you hear it, open miflashtool and your device should show up in it.
5. if not, reboot your PC. You should reboot your PC after installing all the drivers. See #1. (reboot required)
6. Once you successfully see your device on miflashtool, you can flash the fastboot rom of your choice.
7. (you might get stuck on "Can't receive hello packet" dialogue which will prevent your device from flashing), in that case change the USB port, possibly to USB 2.0 and try the test point flash method again to get detected and try flashing again.
8. Test point method should be done everytime you disconnect the USB from your phone and computer, hopefully you only need to do it twice.
9. Sadly for me, I am still unable to flash stock roms with this method, my problem is kind of unique, after flashing it shows me "Your phone is destroyed, press power to turn off" dialogue. lmao
10. if you get the same message then you dun goof'd. Hopefully yours will successfully flash.
Oh and only one version of fastboot ROM actually revives the phone, other fastboot roms actually puts it to coma (vibrating every one second, no display, no nothing). Only one fastboot ROM allows me to go to fastboot and flash recoveries. But if I flash any ROM (stock or custom) it kills the phone again and I have to repeat the given method and try again with another rom. I think the phone is effectively dead. What a **** phone! lol
Click to expand...
Click to collapse
Did you do factory flash mode? That's the only one that can recovery it, the other scripts won't flash everything.
Note that because you didn't backup partitions you will also wipe the IMEI, or so I've read (I backed up my whole device via emmcdl before brick so I was able to recover fine without miflash)
CosmicDan said:
Did you do factory flash mode? That's the only one that can recovery it, the other scripts won't flash everything.
Note that because you didn't backup partitions you will also wipe the IMEI, or so I've read (I backed up my whole device via emmcdl before brick so I was able to recover fine without miflash)
Click to expand...
Click to collapse
Actually I think I got scammed. It is Mi5x sold as MiA1. ****ing chinks! Anyway, I managed to install (Tiffany) on it and now it is booting to boot logo and bootlooping. I can get to fastboot and default (MIUI's) recovery by pressing button combos. But OEM is locked now so I cannot flash TWRP or other ROMs in it. I will have to EDL flash back to that MIA1 ROM to get it unlocked from fastboot. Otherwise MIUI unlocker asks me to link my miui account to this phone by going to settings, which I can't do because it is not booting up.
funny situation.
Bruce666 said:
Hi guys
At first - I tried a method given on this forum: https://forum.xda-developers.com/mi-a1/help/phone-goes-to-qualcomm-hs-usb-qdloader-t3757867
This method doesn't work for me, because after disconnect my PC doesn't recognize my phone.
Phone is in Qualcom HS-USB Diagnostics 900E mode after OTA update (Mi A1 April Update) - strange
So guys... I know there are some magicians who can do almost everything.. Any ideas what to do?
Click to expand...
Click to collapse
Facing The same Issue
---------- Post added at 10:42 AM ---------- Previous post was at 10:35 AM ----------
Phone Showing Charging Only
Can't Even Transfer Data
Not Detected on Pc
udaan said:
1. install all necessary drivers (adb, qualcomm's HS-USB Diagnostics 900E, xiaomi flash tool)
2. use test point method as suggested by @CosmicDan - lots of tutorial on web on how to do this. Carefully read this before actually attempting it.
3. When you successfully do the test point method you will hear the device recognized sound on your computer
4. when you hear it, open miflashtool and your device should show up in it.
5. if not, reboot your PC. You should reboot your PC after installing all the drivers. See #1. (reboot required)
6. Once you successfully see your device on miflashtool, you can flash the fastboot rom of your choice.
7. (you might get stuck on "Can't receive hello packet" dialogue which will prevent your device from flashing), in that case change the USB port, possibly to USB 2.0 and try the test point flash method again to get detected and try flashing again.
8. Test point method should be done everytime you disconnect the USB from your phone and computer, hopefully you only need to do it twice.
9. Sadly for me, I am still unable to flash stock roms with this method, my problem is kind of unique, after flashing it shows me "Your phone is destroyed, press power to turn off" dialogue. lmao
10. if you get the same message then you dun goof'd. Hopefully yours will successfully flash.
Oh and only one version of fastboot ROM actually revives the phone, other fastboot roms actually puts it to coma (vibrating every one second, no display, no nothing). Only one fastboot ROM allows me to go to fastboot and flash recoveries. But if I flash any ROM (stock or custom) it kills the phone again and I have to repeat the given method and try again with another rom. I think the phone is effectively dead. What a **** phone! lol
Click to expand...
Click to collapse
Im sorry, exactly with which ROM did you get to the fastboot?
Press power button for 15 sec
If you feel vibration then you are so lucky
boshell said:
Im sorry, exactly with which ROM did you get to the fastboot?
Click to expand...
Click to collapse
Fastboot rom for Mi5x because the phone is Mi5x.