Hello,
during updating my apps from google play, my phone turned down and now I can't turn on it. It lools like hardbricked. When I conntect it into laptop, in devices shows me as "Quectel QDLoader 9008 (COM4)".
Maybe is relevant to say, that the phone sometimes several times randomly reboot during last year.
Anyone any ideas please? :crying:
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732/amp/
So it doesn't matter, that I have Quectel QDLoader 9008 (COM4) instead QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008 and it works same on win10 as win7-8?
Could be just a dead battery??
Bordiax said:
Could be just a dead battery??
Click to expand...
Click to collapse
Could be.But the very first thing to try is restoring the device from dead.
---------- Post added at 11:05 AM ---------- Previous post was at 11:03 AM ----------
Bordiax said:
So it doesn't matter, that I have Quectel QDLoader 9008 (COM4) instead QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008 and it works same on win10 as win7-8?
Click to expand...
Click to collapse
Yeah,it worked for me on 10,too.However,if you run into detecting issues,try using 7.It'll show correct name after you install qhs drivers (given with the tool in the thread mentioned above).
When I start writing file 8974_msimage.mbn from Msm8974DownloadTool.exe to phone, there is sound of disconnect of USB and it do again and again. What is wrong?
Bordiax said:
When I start writing file 8974_msimage.mbn from Msm8974DownloadTool.exe to phone, there is sound of disconnect of USB and it do again and again. What is wrong?
Click to expand...
Click to collapse
Make sure you follow the given process very carefully.Did you install correct drivers?
Maybe not, I'm not sure
I tried again uninstall bricked device and install qualcomm 2012, but than it writes, that I have already the newest drivers. It is OK? :/
Edit: And now it writes ...Sahara... :'(
Edit2: Now 8974_msimage.mbn loop again.... I'm lost...
Edit3: Maybe the problem is that it doesn't work VolUP+Power button...
Bordiax said:
Maybe not, I'm not sure
I tried again uninstall bricked device and install qualcomm 2012, but than it writes, that I have already the newest drivers. It is OK? :/
Edit: And now it writes ...Sahara... :'(
Edit2: Now 8974_msimage.mbn loop again.... I'm lost...
Edit3: Maybe the problem is that it doesn't work VolUP+Power button...
Click to expand...
Click to collapse
https://www.google.co.in/amp/s/foru...eplusrecovery-tool-v1-0-restore-t2991851/amp/
Mr.Ak said:
https://www.google.co.in/amp/s/foru...eplusrecovery-tool-v1-0-restore-t2991851/amp/
Click to expand...
Click to collapse
Still the same loop
Edit: When I connect the phone to computer the usb shows like Unknow device. So I have to before connecting, hold VolUP+power for 15s, and 10s power to the usb shows like Qualcomm HS-USB QDLoader 9008. But when I switch on Color, there is just 8974_msimage.mbn loop.
I don't know, what I do wrong :/
Bordiax said:
Still the same loop
Edit: When I connect the phone to computer the usb shows like Unknow device. So I have to before connecting, hold VolUP+power for 15s, and 10s power to the usb shows like Qualcomm HS-USB QDLoader 9008. But when I switch on Color, there is just 8974_msimage.mbn loop.
I don't know, what I do wrong :/
Click to expand...
Click to collapse
What do ya' mean by "8974_msimage.mbn" loop? The process of flashing keeps going on and doesn't complete?
Mr.Ak said:
What do ya' mean by "8974_msimage.mbn" loop? The process of flashing keeps going on and doesn't complete?
Click to expand...
Click to collapse
Yes. I think is the same problem, as have this user: https://forum.xda-developers.com/oneplus-one/help/hard-bricked-oneplus-one-rebooting-help-t3423725
Bordiax said:
Yes. I think is the same problem, as have this user: https://forum.xda-developers.com/oneplus-one/help/hard-bricked-oneplus-one-rebooting-help-t3423725
Click to expand...
Click to collapse
Are you using an original/branded USB cable? It might happen due to slow transfer speed of local/unbranded cable.
Mr.Ak said:
Are you using an original/branded USB cable? It might happen due to slow transfer speed of local/unbranded cable.
Click to expand...
Click to collapse
Yes, I'm using the branded USB cable, the red one.
Bordiax said:
Yes, I'm using the branded USB cable, the red one.
Click to expand...
Click to collapse
Did you try using a different PC/lappy with windows7/xp?
Mr.Ak said:
Did you try using a different PC/lappy with windows7/xp?
Click to expand...
Click to collapse
I haven't got any opportunity. Only win10 or Linux.
Bordiax said:
I haven't got any opportunity. Only win10 or Linux.
Click to expand...
Click to collapse
Did you try waiting for like half an hour when loop occurs,maybe it's just the transfer speed that's slow?
Mr.Ak said:
Did you try waiting for like half an hour when loop occurs,maybe it's just the transfer speed that's slow?
Click to expand...
Click to collapse
Nope, even more than an hour the situation seems the same.
Bordiax said:
Nope, even more than an hour the situation seems the same.
Click to expand...
Click to collapse
Situation is same with cm11s restore tool as well?
Mr.Ak said:
Situation is same with cm11s restore tool as well?
Click to expand...
Click to collapse
If you mean the tool from this link: https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851, than yes. Absolutely same result
Now I'm thinking about service, but they want more than 60 dollars :/
Related
Hi guys,
I have had my Nexus 5 rooted with franco kernel on it now for about 5 months. Yesterday I tried to autoflash to the new r57 of franco kernel and accidentally aborted it. My phone will now not boot or go into fastboot or recovery. The only way to get my computer to recognize it is by holding the volume up button and plugging in the usb cable. My computer recongnises it as "Qualcomm HS-USB QDLoader 9008 (COM8)". Did I kill my Nexus 5? Please help!.
P.S. please dont tell me how stupid I am, I know. :crying:
kevindj360 said:
Hi guys,
I have had my Nexus 5 rooted with franco kernel on it now for about 5 months. Yesterday I tried to autoflash to the new r57 of franco kernel and accidentally aborted it. My phone will now not boot or go into fastboot or recovery. The only way to get my computer to recognize it is by holding the volume up button and plugging in the usb cable. My computer recongnises it as "Qualcomm HS-USB QDLoader 9008 (COM8)". Did I kill my Nexus 5? Please help!.
P.S. please dont tell me how stupid I am, I know. :crying:
Click to expand...
Click to collapse
Have you tried for example these steps? http://trendblog.net/fix-soft-bricked-android-device-first-aid-guide/
Here are some good files it seems http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
Most often its possible to recover an android as long as you can access the Download mode.
linuxares said:
Have you tried for example these steps? http://trendblog.net/fix-soft-bricked-android-device-first-aid-guide/
Here are some good files it seems http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
Most often its possible to recover an android as long as you can access the Download mode.
Click to expand...
Click to collapse
I'm not able to access Download mode.
What about backuo bootloader? Vol up, down and power?
Sent from my Nexus 5 using Tapatalk
rootSU said:
What about backuo bootloader? Vol up, down and power?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
No, the only thing that does anything is just holding volume up while plugging it in to the computer. Screen stays black, but computer recognizes it as "Qualcomm HS-USB QDLoader 9008 (COM8)"
So to clarify, you cannot get into either the primary or secondary bootloader? You've tried both and literally nothing happens?
Sent from my Nexus 5 using Tapatalk
rootSU said:
So to clarify, you cannot get into either the primary or secondary bootloader? You've tried both and literally nothing happens?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
exactly
Well if you can't get lg flashtool to work, you're pretty screwed.
Sent from my Nexus 5 using Tapatalk
kevindj360 said:
exactly
Click to expand...
Click to collapse
Try the LG Flashtool. That's your only hope. If it doesn't fix your issue, RMA/repairing is the only option.
vin4yak said:
Try the LG Flashtool. That's your only hope. If it doesn't fix your issue, RMA/repairing is the only option.
Click to expand...
Click to collapse
Will google still accept my RMA. My phone is over 5 months old.
kevindj360 said:
Will google still accept my RMA. My phone is over 5 months old.
Click to expand...
Click to collapse
Try lg flashtool first. Click link in my signature and look in section 3 for the guide. It uses vol up + USB which may work for you
RMA is 1 or 2 years depending which country it is in however it is warranty for manufacturing defects not user destruction. If you RMA it and they identify (rightfully) that you caused this issue, they will charge you for a new phone.
You would be better sending it to LG who may offer to repair for cost. You won't have fried the memory, just corrupt the partition so I wouldn't expect it to be expensive.
But try flashtool first.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Try lg flashtool first. Click link in my signature and look in section 3 for the guide. It uses vol up + USB which may work for you
RMA is 1 or 2 years depending which country it is in however it is warranty for manufacturing defects not user destruction. If you RMA it and they identify (rightfully) that you caused this issue, they will charge you for a new phone.
You would be better sending it to LG who may offer to repair for cost. You won't have fried the memory, just corrupt the partition so I wouldn't expect it to be expensive.
But try flashtool first.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I get to this screen here.
EDIT: Attached the photo
kevindj360 said:
I get to this screen here.
EDIT: Attached the photo
Click to expand...
Click to collapse
If you have qualcomm 9008 you cant do much just rma your device.
kevindj360 said:
I get to this screen here.
EDIT: Attached the photo
Click to expand...
Click to collapse
Tried the qpst tool?
https://drive.google.com/file/d/0B3E5yjXCeMBbUmVRdl9VSHhHVkE/preview
Newer version link
http://code.google.com/p/mydownloadsection/downloads/detail?name=QPST.2.7.374.rar&can=2&q=
doctor_droid said:
Tried the qpst tool?
https://drive.google.com/file/d/0B3E5yjXCeMBbUmVRdl9VSHhHVkE/preview
Newer version link
http://code.google.com/p/mydownloadsection/downloads/detail?name=QPST.2.7.374.rar&can=2&q=
Click to expand...
Click to collapse
He cant do anything with qpst tool without a nexus 5 specific flash programmer and a special nexus 5 bootloader.
It seems when you get "Qualcomm HS-USB QDLoader 9008" you have really bricked your phone (hardbrick). Someone with knowledge must program sometool to unbrick it. (example. for a HTC device http://forum.xda-developers.com/showthread.php?t=1627882)
I think it's best to send it to Google.
I am looking for somebody whose phone in Qualcomm HS-USB QDLoader 9008 mode. I want to try out something to unbrick nexus 5's stucked in Qualcomm HS-USB QDLoader 9008 mode.
Contact me on facebook or hangouts: [email protected]
I want you to allow me to connect to your pc through teamviewer.
bitdomo said:
I am looking for somebody whose phone in Qualcomm HS-USB QDLoader 9008 mode. I want to try out something to unbrick nexus 5's stucked in Qualcomm HS-USB QDLoader 9008 mode.
Contact me on facebook or hangouts: [email protected]
I want you to allow me to connect to your pc through teamviewer.
Click to expand...
Click to collapse
Can I just say that anything this guy does ^^^ is for the good of the community, so if you have one in this state, definitely contact @bitdomo
bitdomo said:
I am looking for somebody whose phone in Qualcomm HS-USB QDLoader 9008 mode. I want to try out something to unbrick nexus 5's stucked in Qualcomm HS-USB QDLoader 9008 mode.
Contact me on facebook or hangouts: [email protected]
I want you to allow me to connect to your pc through teamviewer.
Click to expand...
Click to collapse
So basically u r trying to unbrick a hardbricked phone...?thats seems interesting..
I will try my best to get u what u need...
doctor_droid said:
So basically u r trying to unbrick a hardbricked phone...?thats seems interesting..
I will try my best to get u what u need...
Click to expand...
Click to collapse
Come on..... Brick it! ?
Darth said:
Come on..... Brick it! ?de00
Click to expand...
Click to collapse
Lol.....when did i said i was rich ?
bitdomo said:
I am looking for somebody whose phone in Qualcomm HS-USB QDLoader 9008 mode. I want to try out something to unbrick nexus 5's stucked in Qualcomm HS-USB QDLoader 9008 mode.
Contact me on facebook or hangouts: [email protected]
I want you to allow me to connect to your pc through teamviewer.
Click to expand...
Click to collapse
well now i have if you want, i (dont ask me why) wrongly flashed lg g2´s rpm into my nexus 5 rpm partition, and now it only starts at that mode or some kind of download mode
(see http://forum.xda-developers.com/google-nexus-5/help/dead-nexus-5-t2954709)
Hey, I have a totally Hard-bricked nexus 5.
Still wondering how it got bricked although i was not flashing anything it was just sitting there.
Check my post: http://forum.xda-developers.com/google-nexus-5/help/android-lollipop-nexus-5-discovered-t2960372
he never contact me , the guys ho's saying that he can fix ours phone
sahouli31 said:
he never contact me , the guys ho's saying that he can fix ours phone
Click to expand...
Click to collapse
What guy?
Darth said:
What guy?
Click to expand...
Click to collapse
I'm guessing @bitdomo He hasn't posted on XDA since December 1st. Hoping he's just busy because I'd really like to see if he can fix the qhusb brick without a riff box.
theesotericone said:
I'm guessing @bitdomo He hasn't posted on XDA since December 1st. Hoping he's just busy because I'd really like to see if he can fix the qhusb brick without a riff box.
Click to expand...
Click to collapse
i flash it with a riff box , and the flash was succesful , but the phone won't boot up
He didn't say he could fix it.... He wanted a bricked device to test on. ?
And tis the season to be busy with real life.... He'll be back. ?
Just messaged him. Just thought i should post here to let others know.
"Hi i have a water damaged nexus 5 which can boot (but dead lcd and digitizer) and is fully functioning when normally turned on. (Can hear notifications, and is detected normally). However, when its at the bootloader its detected as Qualcomm HS-USB QDLoader 9008. (twrp was installed, but cant get into it).
I want to sell it for parts but I have no way of doing a factory reset to remove my data from it. How do i know my data is still on there? Because i was able to get into the storage and get my photos, music, etc from it when it booted normally (before digitizer died, after lcd died).
If i am of any help, just reply. If not, then im sorry."
Hopefully my "bricked?" nexus can help the community and myself cause currently its a brick.
alb3rtt said:
Just messaged him. Just thought i should post here to let others know.
"Hi i have a water damaged nexus 5 which can boot (but dead lcd and digitizer) and is fully functioning when normally turned on. (Can hear notifications, and is detected normally). However, when its at the bootloader its detected as Qualcomm HS-USB QDLoader 9008. (twrp was installed, but cant get into it).
I want to sell it for parts but I have no way of doing a factory reset to remove my data from it. How do i know my data is still on there? Because i was able to get into the storage and get my photos, music, etc from it when it booted normally (before digitizer died, after lcd died).
If i am of any help, just reply. If not, then im sorry."
Hopefully my "bricked?" nexus can help the community and myself cause currently its a brick.
Click to expand...
Click to collapse
Water damaged is different.. That's physical damage. Can't reverse that with software
rootSU said:
Water damaged is different.. That's physical damage. Can't reverse that with software
Click to expand...
Click to collapse
So.. my data is trapped on that nexus... and its of no use...
Just was wondering cause it had the Qualcomm HS-USB QDLoader 9008 issue.
Would you say it safe to sell that phone for parts even though it has personal contacts and my debit card on it? I think i had a pattern lock on it (but lets just say i didnt), would you think they would be able to access that data?
It depends how determined they are. Plus i doubt its worth anything due to the damage. I'd scrap it info were you.
rootSU said:
It depends how determined they are. Plus i doubt its worth anything due to the damage. I'd scrap it info were you.
Click to expand...
Click to collapse
Ill find a creative way of destroying it.. lmao
alb3rtt said:
Ill find a creative way of destroying it.. lmao
Click to expand...
Click to collapse
Haha
Got to be blender or acid, surely?
alb3rtt said:
Ill find a creative way of destroying it.. lmao
Click to expand...
Click to collapse
Microwave. ?
Um.... In the middle of an open field of course. Not in the kitchen. ?
BUMP!BUMP!BUMP!
I have something working. I can read and write partitions when phone is in qdloader 9008 mode, but before publishing I want to test it on some real hard bricked nexus to make it sure it works.
Edit: Tested. I bricked and unbricked my device a few times. I am making a thread about it in the General forum.
afther install OTA my phone
- No Download mode
- No recovery mode
- Secure booting error
- but no recognized on device manager
any solution without disassemble the phone?
yulianov25 said:
afther install OTA my phone
- No Download mode
- No recovery mode
- Secure booting error
- but no recognized on device manager
any solution without disassemble the phone?
Click to expand...
Click to collapse
Was the device with root?
Did you used OTA from custom ROM
enkhtwshn said:
Was the device with root?
Did you used OTA from custom ROM
Click to expand...
Click to collapse
yes my device was rooted and has OTA from custom ROM
yulianov25 said:
yes my device was rooted and has ota from custom rom
Click to expand...
Click to collapse
that is a total gg
enkhtwshn said:
that is a total gg
Click to expand...
Click to collapse
any solution?
yulianov25 said:
any solution?
Click to expand...
Click to collapse
Have you tried the LG pc suite? I got out of many messes using it with my LG G3 similar to your problem, even when the pc didn't appear to recognise it. Look for the option in the menu : Repair upgrade errors.
Before you try this, plug your device into the pc and look in device manager and see if it shows up as:
QUALCOMM HS-USB QDLOADER 9008 (COM4) device
If it does, it's well and truly bricked I'm afraid and can only be repaired under warranty. This is not as bad news as it may seem, as if this has happened, they will not be able to tell that you have rooted your device or anything else for that matter.
bobsie41 said:
Have you tried the LG pc suite? I got out of many messes using it with my LG G3 similar to your problem, even when the pc didn't appear to recognise it. Look for the option in the menu : Repair upgrade errors.
Before you try this, plug your device into the pc and look in device manager and see if it shows up as:
QUALCOMM HS-USB QDLOADER 9008 (COM4) device
If it does, it's well and truly bricked I'm afraid and can only be repaired under warranty. This is not as bad news as it may seem, as if this has happened, they will not be able to tell that you have rooted your device or anything else for that matter.
Click to expand...
Click to collapse
I get same problem, my phone can not go to download mode and can not connect with PC after I flashed 5.0.1 by KDZ file (in Connectivity option of phone, I can not see and any option for USB connect).
Please kindly help me. Thank you very much!
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.
Hi, I wasn't sure where to post this.
I was using Odin to reinstall the stock firmware for the Verizon S7, and then it won't turn on... In device manager, I see it is called qualcomm HS-usb qdloader 9008 (COM6)
Thank you for your help!
HuhhooXDA said:
Hi, I wasn't sure where to post this.
I was using Odin to reinstall the stock firmware for the Verizon S7, and then it won't turn on... In device manager, I see it is called qualcomm HS-usb qdloader 9008 (COM6)
Thank you for your help!
Click to expand...
Click to collapse
You cant even go in bootloader?
Us3rNam3d said:
You cant even go in bootloader?
Click to expand...
Click to collapse
No
Download samsung smartswitch and try to recover your phone from there.
Us3rNam3d said:
Download samsung smartswitch and try to recover your phone from there.
Click to expand...
Click to collapse
My phone doesn't turn on....
HuhhooXDA said:
My phone doesn't turn on....
Click to expand...
Click to collapse
Is it charged?
HuhhooXDA said:
Hi, I wasn't sure where to post this.
I was using Odin to reinstall the stock firmware for the Verizon S7, and then it won't turn on... In device manager, I see it is called qualcomm HS-usb qdloader 9008 (COM6)
Thank you for your help!
Click to expand...
Click to collapse
That sounds like you entered Qualcomm's download mode. Had encountered issues like that with HTC devices which ended with the device being sent back to HTC. Search around the HTC forums here on XDA. As before, the methods are device specific. But, maybe you'll get an idea. According to what I've read a long time ago, this happens when the device loses drivers for the chip or something. What happened exactly?