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.
my oneplus one is hard bricked. i tried several tools to recover my OPO, sadly nothing worked. The problem i've figured out is, that after flasing the 8974_msimage.mbn image my phone disconnects (sound from windows), reconnects again and the msm8974 download tool starts again. so i'm stuck like in this video:
The Qualcomm Flash image loader doesn't give me an error message (i can flash everything - i did so with Color.zip and with OPO Recovery Tools files), but still i get no vibration, no led light or anything else from the phone.
so what can i do for now? that's actually not my first android phone which is hard bricked (i helped a lot of friends of mine and i'm computer scientist as well....), so can anyone, please, help me!!!!
regards
markus
hi!
I bought a new huawei watch from china, as he arrived with my sister home, i flashed it the global version and it all worked great!
a couple days after, i updated the watch by hes wish, and it woke up stack on the huawei logo, i tried to flash the same Rom as i flashed before but it didnt worked, so i daownload another rom and tried to flash it.
i guess it was'nt the right rom and the watch is not responding ever since.
i tried to read every sulotion in this forum and to use several QFIL programs but it always give me an ERROR. "sahara server" or some thing else.
the current situation:
black scree, no response, no vibrates, no logo. "brick"i guesse
the computer detect it by "Qualcomm HS-USB QDloader 9008 (com3)
and i realy realy tried to figure it out by reading every thread i found!
be very greatful for evety one that can help me some how..
thanks ahead!
Check this thread:
https://forum.xda-developers.com/smartwatch/watch-2/rom-bootloader-recover-huawei-watch-2-t3855864
If the computer detect it only as "Qualcomm HS-USB QDloader 9008" and you cannot enter fastboot by pressing and holding power button until watch vibrates and then pressing one more time power button (one single short click) - probably QPST is your only friend ...
PS: I cannot confirm method as I never bricked my watch to try it - but this thread is the only one for un-bricking HW2
Thank you!
I already tried this for sevral times, always get the "sahara server error" you know some thing abuat it?
anyone? help with the sharafail error? searce for hours and cant find the sulotion
Please Help...
I have a Huawei watch 2 model 4G sawshark.
I Install another rom, and have BRICK
Now, my watch can connect with computer: QUALCOMM HS-USB 9008
It no vibrator, no logo,... when I charging, It hot...
I used QPST but don't ok
I need help!!!!
Sorry, my English not good, I hope everyone understand me...
Hello all,
I'm new here, and I searching since many time a solution for my issue.
I'm technician for a company in France, that import professional PDA's from Korean. These devices are strong, and a little "expensive"... So when a customer send me a device for RMA, I need to found the best way for solve the issue, without change parts.
At this time, I'm facing to the issue below :
Lot of devices come in RMA because they can't boot. When I plug the device to my computer, I see Qualcomm HS-USB QDloader 9008 in port COM list.
For the manufacturer (we work direclty with him, no "intermediary"), the only way is to change the main board. OK but I'm not stupid, and I konw that they want sold main boards
I know that the main board is bricked and the device boot in EDL mode, no command can't be send (ex adb), and no screen boot.
Impossible to acces to the bootlader with touch combination.
I have the OS files on my computer (boot.img, emmc_appsboot.mbm, rpm.mbn, NON-HLOS.bin etc...)
The CPu is MSM8916, so I tested with QFIL and Miflash to send send files but nothing good :/ MiFlash told me that the "device is busy", and QFIL told me that there is a Sahara fail error".
So my question is : Can I save the main boards ? I think that there is some people here with more competent than me
For information, I have try 1 year ago with Miflash, and I saved only ONE board with Miflash and Xiaomi OS (I try the OS of the redmi because this phone work with the same CPU) ............. Only one file of the OS was sent by Miflash (before a crash of Miflash), but the main baord was save ^^ So I think that it is really a little problem, maybe an only one partition corrupt ....
I can take pictures of the board if needed.
Hi,
I have somehow bricked my Xiaomi Redmi Note 6 Pro (Tulip) in a peculiar fashion.
It happened when a firmware flashing went downhill due to a faulty cable.
My device is now totally unresponsive. Pushing the power button does utterly nothing. There is no System, no Recovery, no Fastboot.
I managed to connect it in EDL mode (my PC sees it as "Qualcomm HS-USB QDLoader 9008" device).
With the correct drivers and after deactivating Windows Driver signature enforcing, I've been able to connect it with MiFlash Utility and receive the hello package.
UNFORTUNATELY, I cannot proceed to flash the new system image, since my Xiaomi Account does not have FLASHING PERMISSION.
I can't find any way to avoid this check. I mailed Xiaomi and they answered they can but won't help, since "it's my fault the phone is bricked".
Does anyone know how to flash in EDL mode without a flashing-enabled Xiaomi account?
Please, help. It's a fine phone, I'd hate to lose it when i'm just a mere security measure away from restoring it to perfect functionality!
Thanks for any help.
ILLE_614 said:
Hi,
I have somehow bricked my Xiaomi Redmi Note 6 Pro (Tulip) in a peculiar fashion.
It happened when a firmware flashing went downhill due to a faulty cable.
My device is now totally unresponsive. Pushing the power button does utterly nothing. There is no System, no Recovery, no Fastboot.
I managed to connect it in EDL mode (my PC sees it as "Qualcomm HS-USB QDLoader 9008" device).
With the correct drivers and after deactivating Windows Driver signature enforcing, I've been able to connect it with MiFlash Utility and receive the hello package.
UNFORTUNATELY, I cannot proceed to flash the new system image, since my Xiaomi Account does not have FLASHING PERMISSION.
I can't find any way to avoid this check. I mailed Xiaomi and they answered they can but won't help, since "it's my fault the phone is bricked".
Does anyone know how to flash in EDL mode without a flashing-enabled Xiaomi account?
Please, help. It's a fine phone, I'd hate to lose it when i'm just a mere security measure away from restoring it to perfect functionality!
Thanks for any help.
Click to expand...
Click to collapse
Funny I was just reading an article about this yesterday. There is only one way to fix this and that is with an authorized account. Sadly Xiaomi gave out a few account authorizations but won't do it anymore. Yet you may still be in luck if you open your wallet. The prices I saw were not very high $18-35USD. One of the guys here on XDA will do it remotely but I don't remember who. I found the article on mi-globe.com and will try and find it and link it.
Did you find the solution
cidxtc said:
Funny I was just reading an article about this yesterday. There is only one way to fix this and that is with an authorized account. Sadly Xiaomi gave out a few account authorizations but won't do it anymore. Yet you may still be in luck if you open your wallet. The prices I saw were not very high $18-35USD. One of the guys here on XDA will do it remotely but I don't remember who. I found the article on mi-globe.com and will try and find it and link it.
Click to expand...
Click to collapse
Did you find the solution
ASHRAFGTX said:
Did you find the solution
Click to expand...
Click to collapse
I found a person who had edl permission. Unfortunately due to xda rules we are not allowed to give out contact information because they charge for the service.
Try qfil application
Qfil application might help