first sry for my bad englich and open a new thread
i did this instruction:
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
step by step to unbrick my OPO but did not work :/
i installed the driver ok Qualcom HS - USB QDLoader 9008
but when i start Msm8974.exe tool One PC cant read the Phone and the other when i press start writes xxxSaharaxxx and don't load any files to my OPO
pls need help thx :/
By now I hope you have solved your problem. I had a similar problem yesterday with my phone. I was on a Window 7 computer and I tried everything. Somehow the system insisted my phone was a serial device instead of a USB device. I tried everything I could think of. I eventually gave up and put it on an XP box and was able to then finish the job of un-bricking it. Make sure your device is properly registered with the computer you are using. Good luck.
Kirlus said:
first sry for my bad englich and open a new thread
i did this instruction:
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
step by step to unbrick my OPO but did not work :/
i installed the driver ok Qualcom HS - USB QDLoader 9008
but when i start Msm8974.exe tool One PC cant read the Phone and the other when i press start writes xxxSaharaxxx and don't load any files to my OPO
pls need help thx :/
Click to expand...
Click to collapse
Hello please help phone campaign became a brick, I flashed through lenovo z90-3 miflash on s240 firmware with the substitution of non-hlos after the launch of the phone did not see the connection and stop defined COM port Qualcomm HS-USB QDLoader 9008 by pressing the volume + button and the inclusion of is determined only by the adb, after a whole bunch of incomprehensible to me manipulation somehow all have seen my phone as it should, then I went qfill decided to fill stitching s208 and at the beginning flew error and then the phone even completely refuse to be included, not taking charge does not go in rekaveri and computer saw him as an unknown device, a week later decided to re-connect it defined as the ADB interface as it is now to revive and if possible ??. I have mat. board ordered him a new
maks.9016 said:
Hello please help phone campaign became a brick, I flashed through lenovo z90-3 miflash on s240 firmware with the substitution of non-hlos after the launch of the phone did not see the connection and stop defined COM port Qualcomm HS-USB QDLoader 9008 by pressing the volume + button and the inclusion of is determined only by the adb, after a whole bunch of incomprehensible to me manipulation somehow all have seen my phone as it should, then I went qfill decided to fill stitching s208 and at the beginning flew error and then the phone even completely refuse to be included, not taking charge does not go in rekaveri and computer saw him as an unknown device, a week later decided to re-connect it defined as the ADB interface as it is now to revive and if possible ??. I have mat. board ordered him a new
Click to expand...
Click to collapse
Hi and welcome to XDA!
I couldn't find much information about your device here except this thread
Vibe shot(z90-3) bricked
Try posting your query there. Hopefully other z90-3 users may be able to help you.
Good luck
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
I was on Masik X 4.1. Phone was working just fine.
I downloaded Masik X 5, installed it over 4.1. Flashing goes very well but at the end phone become dead.
No response on USB, No Driver on PC at all. Phone is complete dead.
Just noticed that I mistakenly downloaded "Masik P Tulip.zip" and flashed it blindly. There was no warning regarding File Mismatch in TWRP.
Very very bad luck.
I manged to bring phone into EDL Mode by testpoint method. Phone flashed successfully with both Qfil and Miflash.
Flashed many many times, tried all files available on different threads but phone is now permanently stuck in EDL mode and dont reboot after successful flashing.
Phone flashed successfully every time but I cant get rid of EDL Mode aka Qdloader 9008.
Plz help me to get my phone out of Qdloader 9008 mode.
Anybody please help me.................................
press power button for more than 30 seconds to get out of edl mode.
yawarniazi said:
I was on Masik X 4.1. Phone was working just fine.
I downloaded Masik X 5, installed it over 4.1. Flashing goes very well but at the end phone become dead.
No response on USB, No Driver on PC at all. Phone is complete dead.
Just noticed that I mistakenly downloaded "Masik P Tulip.zip" and flashed it blindly. There was no warning regarding File Mismatch in TWRP.
Very very bad luck.
I manged to bring phone into EDL Mode by testpoint method. Phone flashed successfully with both Qfil and Miflash.
Flashed many many times, tried all files available on different threads but phone is now permanently stuck in EDL mode and dont reboot after successful flashing.
Phone flashed successfully every time but I cant get rid of EDL Mode aka Qdloader 9008.
Plz help me to get my phone out of Qdloader 9008 mode.
Anybody please help me.................................
Click to expand...
Click to collapse
AFAIK , there's no such things as "automatically reboot after successfully flashed the device"
I was also in this condition but with different phone (it was Redmi 4 Prime (markw)), and all I did is just disconnect the battery form the circuit and then replug it, then I can boot to the system successfully
Hope it helps, but if it isn't then maybe something wrong