Related
First of all, when I'm in the wrong thread, sorry!
So here I go. I guess i bricked my 1+1. Doesn't turn on, only black screen and if i push a button, it vibrates. Looked up for solutions, and found one here somewhere. It's with the recoverytool or with ColorOS.
So I tried to follow the steps. Everything works fine, in Device Manger, the phone is now recognised as Qualcom HS_USB QDloader 9008 (COM3). Til here no problems at all. Then I installed the set-up file, compatibilitymode, run as admin.
I open the recoverytool, and i scan for the device. It should appear as COM. But nothing shows up. It's weird because Windows recognises the device.
What am I doing wrong? What can help?
Thanks
gl411 said:
First of all, when I'm in the wrong thread, sorry!
So here I go. I guess i bricked my 1+1. Doesn't turn on, only black screen and if i push a button, it vibrates. Looked up for solutions, and found one here somewhere. It's with the recoverytool or with ColorOS.
So I tried to follow the steps. Everything works fine, in Device Manger, the phone is now recognised as Qualcom HS_USB QDloader 9008 (COM3). Til here no problems at all. Then I installed the set-up file, compatibilitymode, run as admin.
I open the recoverytool, and i scan for the device. It should appear as COM. But nothing shows up. It's weird because Windows recognises the device.
What am I doing wrong? What can help?
Thanks
Click to expand...
Click to collapse
Have you installed the Qualcomm driver?Its very tricky,Windows wont allow to install it easily.
Yes I did, I was able to switch to non signed in Win8 via F7 in a menu. Thats why it changed from BULK to qualcomm qd9008 on a COM port. Or cant I be sure its done propermy when the name changed?
gl411 said:
Yes I did, I was able to switch to non signed in Win8 via F7 in a menu. Thats why it changed from BULK to qualcomm qd9008 on a COM port. Or cant I be sure its done propermy when the name changed?
Click to expand...
Click to collapse
It should be the driver problem,no other choice.
maskelisuvari said:
It should be the driver problem,no other choice.
Click to expand...
Click to collapse
The easiest way for unbricking oneplus (yes, I tried it): http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136
ColourOS firmware has all needed files for proper flashnig, including right tool for doing that.
Only thing that didnt work on my Win 8.1 x64 was drivers mentioned in post above.
I had to use this QHSUSB_DLOAD drivers from member DallasCZ (that I used for unbricking ZTE v9180). Only with that drivers my Windows recognized bricked phone and Flash tool could find and flash it.
Flash tool in only on chinese, that is a bit problem, but instructions given in post I linked are more/less usefull.
This is a link to DallasCZ shared folder with qhsusb drivers:
https://drive.google.com/folderview...&usp=sharing&tid=0B1T7tp6tJ_3kQkZSWjNsazJZbGc
If you are sure the driver is okay,plug in the usb cable and out and in,until you see the green line on the tool.Also you can follow the guide as in below link:
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
The same thing but this time you can flash CM11s instead of ColorOs.Also there is a video.Pls check it.
Ok so I did the process over and over again, the sixth computer did it right! I was back on ColorOS and now back to CM11S.
This thread can be closed, thanks for the help!
No problem,glad to hear you solved the problem
LG G2 D800 (AT&T) not turning on at all..... when connected to PC, showing as QHSUSB_
When connected to a PC, it is showing up as "QHSUSB_BULK". I only have official software from att OTA, and phone is not rooted.
From my reading online, it means hard brick..... I cant get into recovery,download modes or anything at all now..... definitely not motherboard since the phone turned on over the weekend, when battery was almost zero.....
Can someone tell me how to fix this phone.
Anyone?? Help plz
akusbharat said:
When connected to a PC, it is showing up as "QHSUSB_BULK". I only have official software from att OTA, and phone is not rooted.
From my reading online, it means hard brick..... I cant get into recovery,download modes or anything at all now..... definitely not motherboard since the phone turned on over the weekend, when battery was almost zero.....
Can someone tell me how to fix this phone.
Click to expand...
Click to collapse
Install QHUSB BULK Drivers - http://www.mediafire.com/download/pba9wajnehr9qwg/Qualcomm+USB+Drivers.rar
Then
https://www.youtube.com/watch?v=ERZvlJIC9dE
Use the link in description of youtube video to download the SRK tool.
Make sure you select D800!
spikyshotgun said:
Install QHUSB BULK Drivers - http://www.mediafire.com/download/pb...SB+Drivers.rar
Then
https://www.youtube.com/watch?v=ERZvlJIC9dE
Make sure you select D800!
Click to expand...
Click to collapse
The above link for QHSUSB BULK Drivers is dead, no file is there
akusbharat said:
The above link for QHSUSB BULK Drivers is dead, no file is there
Click to expand...
Click to collapse
Sorry my bad
Should work now. http://www.mediafire.com/download/pba9wajnehr9qwg/Qualcomm+USB+Drivers.rar
spikyshotgun said:
Install QHUSB BULK Drivers - http://www.mediafire.com/download/pba9wajnehr9qwg/Qualcomm+USB+Drivers.rar
Then
https://www.youtube.com/watch?v=ERZvlJIC9dE
Use the link in description of youtube video to download the SRK tool.
Make sure you select D800!
Click to expand...
Click to collapse
spikyshotgun said:
Sorry my bad
Should work now. http://www.mediafire.com/download/pba9wajnehr9qwg/Qualcomm+USB+Drivers.rar
Click to expand...
Click to collapse
Thanks for that driver. When I downloaded and extracted the file and try to select this as driver for the phone......
Now the phone is being detected as "Unknown USB device (Device descriptor Request failed)"
Now, When I try to update driver manually, I selected both folder under 'Win64/AMD64' which are checked and free, but PC says, driver is upto date
I also tried to install using the setup file under '72' folder.
Please help with how to install this driver to detect the phone by SRK droith tool.... BTW, disk management doesnt show the many partitions as the video shows when device is connected
akusbharat said:
Thanks for that driver. When I downloaded and extracted the file and try to select this as driver for the phone......
Now the phone is being detected as "Unknown USB device (Device descriptor Request failed)"
Now, When I try to update driver manually, I selected both folder under 'Win64/AMD64' which are checked and free, but PC says, driver is upto date
I also tried to install using the setup file under '72' folder.
Please help with how to install this driver to detect the phone by SRK droith tool.... BTW, disk management doesnt show the many partitions as the video shows when device is connected
Click to expand...
Click to collapse
"Unknown USB device (Device descriptor Request failed)"
You could try unplugging the battery connector and using just USB power to bypass that, or maybe short it over to 9008 mode and attempt to repair that way - good luck with that! I have one stuck in 9008 mode and its apparently a lifeless brick forever more. Or maybe if you could charge the battery somehow, that would bring back the ever desirable 9006 mode?
Before all that though it wouldn't hurt to uninstall all LG drivers, then reboot and reinstall, then plug in device. Maybe it's just a driver kerfuffle.
Still not working..... Anybody help please to fix the issue
Hello,
since 5 years i am playing with google android OS and about 15 devices it looks like i have first fully bricked device.
What happened?
I made a custom marsmallow firmware from the update.zip.
The bad thing was (i think) that i deleted the aboot and also sbl1 partition from the update and also the script for flashing recovery. The second bad thing was (maybe) that i included busybox and root to the update.zip right from the begining without testing the firmware without it.
Then i made complete wipe of cache, dalvik cache, data and system (anothe rmistek i think). Flashed the firmware with no problem, no errors. Then i made wipe cache and dalvik cache again (as i used to, when going to higher OS version).
Afte rthat i hit reboot and my device is dead since then.
It cant be powered on normaly, neither recovery, neither bootloader, neither qualcomm loader.
Only thing that happens is when i connect the device to PC, the LED turns on. I have to tweak the ALCATEL USB drivers to be compatible with my WIN10PRO (yes i hate the win 10 because of the drivers,but had no other option than upgrade to win10).
Now i managed to see the device as "Android HS-USB QDLoader 9008 (yes 9008 not 9006 also bad thing).
When i try to connect to the device with panasonic eluga SUGAR_QCT_SP tool or with mobile upgrade Q or with SUGAR_QCT_SP tool i always get error when the tool downloads the MPRG. It cant download it from the device so it gives me error and thats it.
Since I dont have the proper rawprogram0.xml, patch.xml and other mbn files to pus them trough QPST i think i am in the dead end.
So if anybody has any suggestion i wil appreciate it.
If not, i will send it to warranty repair on friday and get finger crossed that they will repair it (while the service in chzech republic who is Alcatel aproved is a bunch of loosers, who do anything to do not have make it as warranty repair).
DallasCZ said:
Hello,
since 5 years i am playing with google android OS and about 15 devices it looks like i have first fully bricked device.
What happened?
I made a custom marsmallow firmware from the update.zip.
The bad thing was (i think) that i deleted the aboot and also sbl1 partition from the update and also the script for flashing recovery. The second bad thing was (maybe) that i included busybox and root to the update.zip right from the begining without testing the firmware without it.
Then i made complete wipe of cache, dalvik cache, data and system (anothe rmistek i think). Flashed the firmware with no problem, no errors. Then i made wipe cache and dalvik cache again (as i used to, when going to higher OS version).
Afte rthat i hit reboot and my device is dead since then.
It cant be powered on normaly, neither recovery, neither bootloader, neither qualcomm loader.
Only thing that happens is when i connect the device to PC, the LED turns on. I have to tweak the ALCATEL USB drivers to be compatible with my WIN10PRO (yes i hate the win 10 because of the drivers,but had no other option than upgrade to win10).
Now i managed to see the device as "Android HS-USB QDLoader 9008 (yes 9008 not 9006 also bad thing).
When i try to connect to the device with panasonic eluga SUGAR_QCT_SP tool or with mobile upgrade Q or with SUGAR_QCT_SP tool i always get error when the tool downloads the MPRG. It cant download it from the device so it gives me error and thats it.
Since I dont have the proper rawprogram0.xml, patch.xml and other mbn files to pus them trough QPST i think i am in the dead end.
So if anybody has any suggestion i wil appreciate it.
If not, i will send it to warranty repair on friday and get finger crossed that they will repair it (while the service in chzech republic who is Alcatel aproved is a bunch of loosers, who do anything to do not have make it as warranty repair).
Click to expand...
Click to collapse
Try with other Pc with WIndows 7 or 10 ..today i get my phone back 3 times with panasonic software and shows me "Android HS-USB QDLoader 9008"..sometimes fails with download mprg but try again ...first press + and - and then connect usb and try with panasonic in my situation power and volume buttons are don't work so i must open the phone
Alek Dev said:
Try with other Pc with WIndows 7 or 10 ..today i get my phone back 3 times with panasonic software and shows me "Android HS-USB QDLoader 9008"..sometimes fails with download mprg but try again ...first press + and - and then connect usb and try with panasonic in my situation power and volume buttons are don't work so i must open the phone
Click to expand...
Click to collapse
have tried with 3 PCs with win7 and with 3 usb cables. Still error when downloading MPRG.
I cannot understand where it went wrong. The aboot and sbl1 parition shouldnt affect the device to boot to recovery or to bootloader, because when the sbl1 chechk for aboot it should be fine whle they are the same version.
DallasCZ said:
have tried with 3 PCs with win7 and with 3 usb cables. Still error when downloading MPRG.
I cannot understand where it went wrong. The aboot and sbl1 parition shouldnt affect the device to boot to recovery or to bootloader, because when the sbl1 chechk for aboot it should be fine whle they are the same version.
Click to expand...
Click to collapse
i hardbricked many times and panasonic helped in every time...one time i made test zip of Miui and i hardbricked only led worked,screen not worked but panasonic helped me........i can't understand what's the problem with downloading MPRG
Alek Dev said:
i hardbricked many times and panasonic helped in every time...one time i made test zip of Miui and i hardbricked only led worked,screen not worked but panasonic helped me........i can't understand what's the problem with downloading MPRG
Click to expand...
Click to collapse
thats the probelm. I also dont know why is there a probelm to download the MPRG to comunicate with the device.
The removable battery was a good thing, because you can power off the device. Now i can just guess if the device is powered off or not when i connect to the PC.
And of course this f**ing windows 10.
maybe when the 6.0.1 will be released i can connect with propper mbn. but i cant wait. I will send it to repair on friday or buy another device (zenfone 3 or moto g4plus).
Now i am still trying to bring it to life.
DallasCZ said:
thats the probelm. I also dont know why is there a probelm to download the MPRG to comunicate with the device.
The removable battery was a good thing, because you can power off the device. Now i can just guess if the device is powered off or not when i connect to the PC.
And of course this f**ing windows 10.
Click to expand...
Click to collapse
Try to disconnect the Battery and reconnect and then try with Pc AND Panasonic
here is the screen.
Alek Dev said:
Try to disconnect the Battery and reconnect and then try with Pc AND Panasonic
Click to expand...
Click to collapse
but it means to open the device, and i am a little bit affraid not to loose the warranty by opening it and reconnect the battery.
DallasCZ said:
but it means to open the device, and i am a little bit affraid not to loose the warranty by opening it and reconnect the battery.
Click to expand...
Click to collapse
Try to go to TAB Infromation and Get information from Device and then press Reboot Device....I think if you dissconect battery and reconnect it will work....also
whether to open or not Тhe service will want money for repair
Alek Dev said:
Try to go to TAB Infromation and Get information from Device and then press Reboot Device....I think if you dissconect battery and reconnect it will work....also
whether to open or not Тhe service will want money for repair
Click to expand...
Click to collapse
if they cant boot the device they will probably replace the mainboard so they will not get known if the device was unlocked or rooted.
If i will open it and replace the battery i will break the stamps on the battery so they will know i was inside the device and they will refuse to make it as warranty repair.
SO if there is no software option i will send it to warranty repair. If they will refuse to repair it as warranty repair. then i will consider to open it and do whatever it takes to get it to life
DallasCZ said:
if they cant boot the device they will probably replace the mainboard so they will not get known if the device was unlocked or rooted.
If i will open it and replace the battery i will break the stamps on the battery so they will know i was inside the device and they will refuse to make it as warranty repair.
SO if there is no software option i will send it to warranty repair. If they will refuse to repair it as warranty repair. then i will consider to open it and do whatever it takes to get it to life
Click to expand...
Click to collapse
Did you have TeamViewer..i think that i can help you to get your device to life ( if you have Teamviewer send me ID AND pass to PM)
@Alek Dev: i congratulate you ! respect .... Sometime, you're like a morpion. But in this case , i salute your dedication
I hope you manage to save DallaCZ :angel:
murigny64 said:
@Alek Dev: i congratulate you ! respect .... Sometime, you're like a morpion. But in this case , i salute your dedication
I hope you manage to save DallaCZ :angel:
Click to expand...
Click to collapse
We are tried but Nothing same error . .i will google it ..)
murigny64 said:
@Alek Dev: i congratulate you ! respect .... Sometime, you're like a morpion. But in this case , i salute your dedication
I hope you manage to save DallaCZ :angel:
Click to expand...
Click to collapse
As i said to him...sometimes he is a pain in the ass, but he meneged to sped his time to try to solve my problem...rispect!
DallasCZ said:
As i said to him...sometimes he is a pain in the ass, but he meneged to sped his time to try to solve my problem...rispect!
Click to expand...
Click to collapse
i think the problem is drivers...because my device in device manager is showed like "Qualcomm HS-USB QDLoader 9008 " yours is showed like "Android HS-USB QDLoader 9008"-i think that you can again try this + and - and connect usb or + and - and pwr button and then usb
DallasCZ said:
As i said to him...sometimes he is a pain in the ass, but he meneged to sped his time to try to solve my problem...rispect!
Click to expand...
Click to collapse
Sent from my SM-N920V using XDA Free mobile app
---------- Post added at 02:30 AM ---------- Previous post was at 02:26 AM ----------
frankie paul said:
Sent from my SM-N920V using XDA Free mobile app
Click to expand...
Click to collapse
Alek Dev said:
i think the problem is drivers...because my device in device manager is showed like "Qualcomm HS-USB QDLoader 9008 " yours is showed like "Android HS-USB QDLoader 9008"-i think that you can again try this + and - and connect usb or + and - and pwr button and then usb
Click to expand...
Click to collapse
Sent from my SM-N920V using XDA Free mobile app
---------- Post added at 02:35 AM ---------- Previous post was at 02:30 AM ----------
DallasCZ said:
if they cant boot the device they will probably replace the mainboard so they will not get known if the device was unlocked or rooted.
If i will open it and replace the battery i will break the stamps on the battery so they will know i was inside the device and they will refuse to make it as warranty repair.
SO if there is no software option i will send it to warranty repair. If they will refuse to repair it as warranty repair. then i will consider to open it and do whatever it takes to get it to life
Click to expand...
Click to collapse
Sent a my SM-N920V using XDA Free mobile app
Alek Dev said:
i think the problem is drivers...because my device in device manager is showed like "Qualcomm HS-USB QDLoader 9008 " yours is showed like "Android HS-USB QDLoader 9008"-i think that you can again try this + and - and connect usb or + and - and pwr button and then usb
Click to expand...
Click to collapse
I tried with "Android HS-USB QDLoader 9008" and also with "Qualcomm HS-USB QDLoader 9008" and even with "Alcatel HS-USB QDLoader 9008" always error when reading MPRG from the device.
http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
This should help you I think
yash_rathore25 said:
http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
This should help you I think
Click to expand...
Click to collapse
maybe,but you have to rewrite all the .xml files with data for your device, which we dont have.
can anyone sent the whole emmc dump of yuphoriya 5010A
bcoz mine is dead...
Hi
Does your device show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008 . on your computer.
Also is ur device hard bricked like no display no vibration but gets detected by pc as com port in device manager.
If this is ur condition give a reply
my ph vibrt bt no display
Is your phone yu5010 or yu5010a
satyabobby09 said:
Hi
Does your device show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008 . on your computer.
Also is ur device hard bricked like no display no vibration but gets detected by pc as com port in device manager.
If this is ur condition give a reply
Click to expand...
Click to collapse
bro my yuphoria is also dead it doesn't even get detected by pc as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008 bro help me!!!
satyabobby09 said:
Hi
Does your device show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008 . on your computer.
Also is ur device hard bricked like no display no vibration but gets detected by pc as com port in device manager.
If this is ur condition give a reply
Click to expand...
Click to collapse
Qfil is giving this error do you have any fix ??
arun531 said:
can anyone sent the whole emmc dump of yuphoriya 5010A
bcoz mine is dead...
Click to expand...
Click to collapse
i'm dumping YU5010A Emmc once it is done.i don't know if flashing it on SdCard will revive my dead Yuphoria incase it works i will upload it
arun531 said:
can anyone sent the whole emmc dump of yuphoriya 5010A
bcoz mine is dead...
Click to expand...
Click to collapse
tried it doesn't boots fastboot with sdcard
smh.saad said:
Qfil is giving this error do you have any fix ??
Click to expand...
Click to collapse
1. install QPST tool. and drivers.extract file also.
2. go to "run" and search for "QFIL", hit enter. it will open QPST tool.
3. in QPST tool.. select flat build
4. for "select programmer" select program_emmc
. 5. for XML, select raw program & then patch0.
then "Download" option wil get highlighted.
press vol+ & connect flashing. do not leave vol+ key untill flashing complete.
Do not forget to holdind vol+ button Best of luck bro
satyabobby09 said:
1. install QPST tool. and drivers.extract file also.
2. go to "run" and search for "QFIL", hit enter. it will open QPST tool.
3. in QPST tool.. select flat build
4. for "select programmer" select program_emmc
. 5. for XML, select raw program & then patch0.
then "Download" option wil get highlighted.
press vol+ & connect flashing. do not leave vol+ key untill flashing complete.
Do not forget to holdind vol+ button Best of luck bro
Click to expand...
Click to collapse
unable to connect to comPort error
smh.saad said:
unable to connect to comPort error
Click to expand...
Click to collapse
which windows OS are u using. i had problems with win 10 . use win7 64bit if possible. its easier to install the drivers.Then COM port error should get solved
satyabobby09 said:
which windows OS are u using. i had problems with win 10 . use win7 64bit if possible. its easier to install the drivers.Then COM port error should get solved
Click to expand...
Click to collapse
did u got COM Port error on windows 10 i got it on windows 8.1 nd 7
satyabobby09 said:
which windows OS are u using. i had problems with win 10 . use win7 64bit if possible. its easier to install the drivers.Then COM port error should get solved
Click to expand...
Click to collapse
can you link me the drivers for yuphoria as my windows 7 64bit even tried 10,8,8.1 ..
was your device yu5010A??
smh.saad said:
can you link me the drivers for yuphoria as my windows 7 64bit even tried 10,8,8.1 ..
was your device yu5010A??
Click to expand...
Click to collapse
I had both yu5010A n you 5010CM. I'll give u the link soon(I'm at office. I'll upload or find u the link when I reach home.). I had problem with win 10. And one more thing you should boot in safe mode for unsigned drivers to install
View attachment 4011689
this is the link n change it to .rar from .zip
https://forum.xda-developers.com/attachment.php?attachmentid=4011689&stc=1&d=1485012543
satyabobby09 said:
View attachment 4011689
this is the link n change it to .rar from .zip
https://forum.xda-developers.com/attachment.php?attachmentid=4011689&stc=1&d=1485012543
Click to expand...
Click to collapse
I had tried many things including QPST AND QFIL to revive my hardbricked yuphoria yu5010 two-three months earlier, but had the same error as shown in earlier attachement image having sahara error in this thread. But didn't try of keep pressing vol + button during qfil download.
hey @satyabobby09, have you really ever revived hard-bricked yuphoria ?
ravi2106 said:
I had tried many things including QPST AND QFIL to revive my hardbricked yuphoria yu5010 two-three months earlier, but had the same error as shown in earlier attachement image having sahara error in this thread. But didn't try of keep pressing vol + button during qfil download.
hey @satyabobby09, have you really ever revived hard-bricked yuphoria ?
Click to expand...
Click to collapse
I have unbricked my device. The process needs to be followed properly
Have u revived u r yuphoria
satyabobby09 said:
which windows OS are u using. i had problems with win 10 . use win7 64bit if possible. its easier to install the drivers.Then COM port error should get solved
Click to expand...
Click to collapse
Satyabobby09;
Can I get u r contact no plz so that I can get details regarding how to revive hard bricked yuphoria
satyabobby09 said:
I have unbricked my device. The process needs to be followed properly
Click to expand...
Click to collapse
means, you revived your yuphoria using only this QPST and QFIL tool ? when no recovery and fastboot were working. confirm me please @satyabobby09 .
ravi2106 said:
means, you revived your yuphoria using only this QPST and QFIL tool ? when no recovery and fastboot were working. confirm me please @satyabobby09 .
Click to expand...
Click to collapse
Yes you need qfil signed ROM n qpst. Also this is msm8916 so use msm8916.mbn
Guys follow this video its in Hindi hope this. Helps you
https://youtu.be/5qnr8bJ2Zso
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