Database Info

G900P Dead boot Shows Qualcomm HS-USB

I have a Galaxy G900P that had bad unlock and now has dead boot and won't power on. It only shows Qualcomm HS-USB QDLoader in device manager. I've searched the net but couldn't find the files to repair. If anyone has please share the procedure and files. Thanks

i assume that youve tried getting into download mode without any success. Is it completely nonresponsive to any button presses? If so, you might have corrupted the boot image.
if the image isnt bad, might wanna try this
http://www.amazon.com/gp/product/B0053H73JQ?psc=1&redirect=true&ref_=oh_aui_detailpage_o08_s00
if it is bad, might wanna look here
http://forum.gsmhosting.com/vbb/f77...-boot-repair-complete-files-included-1886367/

Thanks..For sure the boot image is bad. I've found and read the second thread but it's for different model, G900F. I've requested for G900P but no one seems to have it. That's why I'm trying to get help here.

oh, sorry, i was super tired when i posted that and didnt notice that part. RWILCO12 seems to be a g900p guru, id maybe hit him up

citifone said:
I have a Galaxy G900P that had bad unlock and now has dead boot and won't power on. It only shows Qualcomm HS-USB QDLoader in device manager. I've searched the net but couldn't find the files to repair. If anyone has please share the procedure and files. Thanks
Click to expand...
Click to collapse
In order to troubleshoot we would need to know how it got there. What happened that caused the "bad unlock"?

It was unlocked with a software that has no EFS or security backup. After unlocked, it has unknown baseband then reflashed it with wrong firmware.

citifone said:
It was unlocked with a software that has no EFS or security backup. After unlocked, it has unknown baseband then reflashed it with wrong firmware.
Click to expand...
Click to collapse
If you flashed the wrong firmware you're probably hosed. If you can tell us what firmware we can maybe see if there is something that can be done... If you can get it into download mode there's a chance Odin can fix it but again, it is slim if you flashed firmware for another device.

Thanks for your reply...No download mode now, only Qualcomm HS-USB QDLoader shows in device manager when plugged into PC. I think there's chance to revise this phone with this guide only if I have the G900G boot image and other files but I couldn't find them. Files available are for G900F.
http://forum.gsmhosting.com/vbb/f77...-boot-repair-complete-files-included-1886367/

rwilco12 said:
If you flashed the wrong firmware you're probably hosed. If you can tell us what firmware we can maybe see if there is something that can be done... If you can get it into download mode there's a chance Odin can fix it but again, it is slim if you flashed firmware for another device.
Click to expand...
Click to collapse
thanks for jumping in and helping man!! I knew you were probably the dude to go to!

Oppo R7sf with no fastboot mode, no recovery mode. Please Help :(

Please help me.
So I think I accidentally removed some bloatware when my phone still great.
When I restart the phone hope for a more speedy and light everyday use, it goes bootloop instead.
Here is My Oppo R7sf back then:
1. Already rooted via Oppo Tools, I downgraded the firmware to 151210 version.
2. Booloader not unlocked yet.
3. Cant boot into fastboot mode via buttons, and if I keep holding it = always bootloop, but if I stop pressing it = the logo stucks.
4. Cant boot to Recovery mode nor Hard Reset, and if I keep holding it = same bootloop logo, even I can tell its blinking every 2 seconds. and if I stop pressing it, the logo stucks.
So I was trying how to do fastboot mode via adb and command prompt, but when I type adb devices, it always says "device unauthorized", 12 hours and I have no idea how to get rid of these as far as I know we have to enable usb debugging first, but my phone cannot boot... so... is there any solutions?
Any feedbacks will be much appreciated. Thankyou for your kindness.

My guess is your phone is entering Qualcomms Emergency Download Mode. Try connecting your phone to an PC USB port and look for driver install attempts.

celoxocis said:
My guess is your phone is entering Qualcomms Emergency Download Mode. Try connecting your phone to an PC USB port and look for driver install attempts.
Click to expand...
Click to collapse
Ive done it, trying to flash with QFIL, loading .mbn files, rawprogram0, patch0, and the software cant run..
Ive tried with Msm8974 download tool, finished and sahara failed or something like that.
I really lose my hope.. Please everyone... :

ojankun said:
Ive done it, trying to flash with QFIL, loading .mbn files, rawprogram0, patch0, and the software cant run..
Ive tried with Msm8974 download tool, finished and sahara failed or something like that.
I really lose my hope.. Please everyone... :
Click to expand...
Click to collapse
You just need the proper factory flasher.
I will send you a pm when I get to my terminal.

celoxocis said:
You just need the proper factory flasher.
I will send you a pm when I get to my terminal.
Click to expand...
Click to collapse
I'm now trying to download miui rom for Oppo Find7 so then I can proceed it with MiFlash. I dont know this will work or not, because I think my only solution is playing around with this Qualcomm things. I've already download MsmDownloader for Find7 too. And I have R7sfEX_11_OTA_005_all_201511191402 stock firmware ready, but have no idea how to flash it because I cant get through fastbood mode via Phone nor ADB devices.
Thankyou, I'll be waiting for your PM. Thanks for your kindness.
Best regards.

ojankun said:
I'm now trying to download miui rom for Oppo Find7 so then I can proceed it with MiFlash. I dont know this will work or not, because I think my only solution is playing around with this Qualcomm things. I've already download MsmDownloader for Find7 too. And I have R7sfEX_11_OTA_005_all_201511191402 stock firmware ready, but have no idea how to flash it because I cant get through fastbood mode via Phone nor ADB devices.
Thankyou, I'll be waiting for your PM. Thanks for your kindness.
Best regards.
Click to expand...
Click to collapse
ok check your PM

celoxocis said:
ok check your PM
Click to expand...
Click to collapse
Okay, thank you so much I will try this and will report you back.
Thankyou.

celoxocis said:
ok check your PM
Click to expand...
Click to collapse
Finally it works, thanks mate very very big thanks i owe you my life
YESSSSSSSSSSSSSSSSS!!!! :victory:

Hello,
Could I also please have the link to this file. I'm basically in the exact same situation.
Thank you!

InspireM3world said:
Hello,
Could I also please have the link to this file. I'm basically in the exact same situation.
Thank you!
Click to expand...
Click to collapse
You can PM celoxocis there, mate.

celoxocis said:
ok check your PM
Click to expand...
Click to collapse
Please PM me, same my problem

chua83 said:
Please PM me, same my problem
Click to expand...
Click to collapse
Check your PM

Hi, if you can help me too ... Oppo R7 PlusM
I'm stucked in the "download mode". No Recovery, No Fastboot. I wasn't unable to find the right MSMDownloadtool.
Can you help me? Thank you a lot

mast3rf0x said:
Hi, if you can help me too ... Oppo R7 PlusM
I'm stucked in the "download mode". No Recovery, No Fastboot. I wasn't unable to find the right MSMDownloadtool.
Can you help me? Thank you a lot
Click to expand...
Click to collapse
I can't help for R7PlusM only R7S.

celoxocis said:
I can't help for R7PlusM only R7S.
Click to expand...
Click to collapse
I only need the MSM8939 program utility. The R7s should have the same qualcomm chip. For all others files there are no problem, I should have all necessary.
If are the same, can you send me the link?
Thank you a lot

mast3rf0x said:
I only need the MSM8939 program utility. The R7s should have the same qualcomm chip. For all others files there are no problem, I should have all necessary.
If are the same, can you send me the link?
Thank you a lot
Click to expand...
Click to collapse
No it's not that simple.
The program utility uses headers to compare which phone is plugged it. It compares those headers with the headers of the phone plugged in.
There is no way to force the program utility to flash a different phone than the ones containing the headers it was shipped with.

celoxocis said:
No it's not that simple.
The program utility uses headers to compare which phone is plugged it. It compares those headers with the headers of the phone plugged in.
There is no way to force the program utility to flash a different phone than the ones containing the headers it was shipped with.
Click to expand...
Click to collapse
Ok. For what I understand the process is quite similar to those I've see for MTK. A correct list of the memory and the right flasher.
I've analyzed the content of the directory and seems that the "key" is inside the flasher and a correct settings.xml and rawprogram0.xml.
The various MSMDownloadTool I've found until now can be grouped in : ver.1, ver.2.0 and ver.3.0 (the last one). Everyone of this version have a "range" work using various types of flasher (number.mbn). I belive that the 3.0 should be able to program qualcomm Smartphone of last generation.
However the last MiuiFlasher should be able program everything.
So the main problem is to find the Mbn flasher with Sahara support and right settings files.
I can't find the right flasher.
Maybe I can get a wrong way ... ... correct me for everything I've missed out :angel:

mast3rf0x said:
Ok. For what I understand the process is quite similar to those I've see for MTK. A correct list of the memory and the right flasher.
I've analyzed the content of the directory and seems that the "key" is inside the flasher and a correct settings.xml and rawprogram0.xml.
The various MSMDownloadTool I've found until now can be grouped in : ver.1, ver.2.0 and ver.3.0 (the last one). Everyone of this version have a "range" work using various types of flasher (number.mbn). I belive that the 3.0 should be able to program qualcomm Smartphone of last generation.
However the last MiuiFlasher should be able program everything.
So the main problem is to find the Mbn flasher with Sahara support and right settings files.
I can't find the right flasher.
Maybe I can get a wrong way ... ... correct me for everything I've missed out :angel:
Click to expand...
Click to collapse
Yes that's correct. However there is a thread here somewhere in the R7Plus forum which is specifically for the R7PlusM and in there somewhere is a download link to the factory flasher you are looking for.
I know it because months ago I came across it and downloaded its, saw that it contains only Chinese based Oppo files and deleted it later on.
So I suggest you search that thread for what you need.

celoxocis said:
Yes that's correct. However there is a thread here somewhere in the R7Plus forum which is specifically for the R7PlusM and in there somewhere is a download link to the factory flasher you are looking for.
I know it because months ago I came across it and downloaded its, saw that it contains only Chinese based Oppo files and deleted it later on.
So I suggest you search that thread for what you need.
Click to expand...
Click to collapse
Ok ... I will search. Thank you for your useful information.:good:

celoxocis said:
I can't help for R7PlusM only R7S.
Click to expand...
Click to collapse
I have an R7S which has been bricked; details originally posted here but no reply yet.
Additionally to the quoted post above, if I attempt to go into recovery mode and plug the phone into my PC at the same time, the logo stays on but nothing else. I'm not sure if this is sitting in fastboot mode, however I still can't communicate via adb.
Could you please help me resurrect my phone.

[LG-H918 TMO] [TOTs]

As promised,
here above you have some TOTs just created and only for Development use
This image files are been created in Stock bootloader locked mode, but should be the same as unlocked mode for sure.
V 10d TOTs
Stock FULL TOT -----> LINK
Stock System and boot partitions TOT -----> LINK
Stock only Recovery TOT -----> LINK
Stock only Boot Partitions TOT -----> LINK

Sick! Do these flash correctly though? Have you tested on your device?

Honestly Annoying said:
Sick! Do these flash correctly though? Have you tested on your device?
Click to expand...
Click to collapse
Still not Bro.
Waiting @tungkick to have a way to always go back, but i'm pretty sure if you flash only recovery TOT for example, you don't have any risk of brick nothing

wolfgart said:
Still not Bro.
Waiting @tungkick to have a way to always go back, but i'm pretty sure if you flash only recovery TOT for example, you don't have any risk of brick nothing
Click to expand...
Click to collapse
Alright, I am going to attempt to make a TOT with TWRP. Just need the TWRP file from @jcadduono

Honestly Annoying said:
Alright, I am going to attempt to make a TOT with TWRP. Just need the TWRP file from @jcadduono
Click to expand...
Click to collapse
He already posted it on his website a few pages back. Check it out

arjuna_ said:
He already posted it on his website a few pages back. Check it out
Click to expand...
Click to collapse
Oh damn, I'll check that out! Totally missed that, my bad

Wait. Is there a TWRP for the T-Mobile V20??...

stanleyopar2000 said:
Wait. Is there a TWRP for the T-Mobile V20??...
Click to expand...
Click to collapse
There is a twrp recovery.img, but it's not yet flashable.

What is @tungkick website where I can find all of this stuff? Looking forward to flashing everything in the near future.

stanleyopar2000 said:
Wait. Is there a TWRP for the T-Mobile V20??...
Click to expand...
Click to collapse
Yes, there seems to be one already, but as far as i know it is not flashable yet.
Look on this thread:
http://forum.xda-developers.com/v20...-stock-tot-t3484982/post69308906#post69308906

I have a bricked v20 and I have tried flashing this .tot and the other posted in this forum and I keep getting error messages at 9% on all attempts on two windows machines. Any ideas on what this issue could be? I am using LGUP version 1_14_3. Is this the latest build or the build compatible with the V20? Drivers were latest I could find also using the LG common.dll which I needed for LGUP to recognize the V20. This is my only way out of brick I think. Any suggestions would be greatly appreciated. Thanks

bud951 said:
I have a bricked v20 and I have tried flashing this .tot and the other posted in this forum and I keep getting error messages at 9% on all attempts on two windows machines. Any ideas on what this issue could be? I am using LGUP version 1_14_3. Is this the latest build or the build compatible with the V20? Drivers were latest I could find also using the LG common.dll which I needed for LGUP to recognize the V20. This is my only way out of brick I think. Any suggestions would be greatly appreciated. Thanks
Click to expand...
Click to collapse
mate, as of today, i have read that there is no dll file for the v20. i.e there is no updated dll file to recognise the v20 in lgup.
u might want to wait a bit longer before u can unbrick your phone.

frostmore said:
mate, as of today, i have read that there is no dll file for the v20. i.e there is no updated dll file to recognise the v20 in lgup.
u might want to wait a bit longer before u can unbrick your phone.
Click to expand...
Click to collapse
Not good news.. it is just the dll? I mean i knew it had to be a missing piece because it was ready to flash. Every file failed at the same time. If anyone hears anything please post here or PM me just for a heads up. Im sure a few other desperate souls out there are anxiously waiting. Any reason the flash tools are incomplete? It doesnt seem like a big deal. Can someone here in the forum make one? Just couious.. i would gladly donate. Thanks for the info.

bud951 said:
Not good news.. it is just the dll? I mean i knew it had to be a missing piece because it was ready to flash. Every file failed at the same time. If anyone hears anything please post here or PM me just for a heads up. Im sure a few other desperate souls out there are anxiously waiting. Any reason the flash tools are incomplete? It doesnt seem like a big deal. Can someone here in the forum make one? Just couious.. i would gladly donate. Thanks for the info.
Click to expand...
Click to collapse
I don't think the flash tool is meant to be public, so they are probably leaked files.
I have a soft bricked LG V20 and have tried the LGUP DLL for every LG phone model I could find. The most progress I got was with the LG G5 dll and it only went to 10%.

bud951 said:
Not good news.. it is just the dll? I mean i knew it had to be a missing piece because it was ready to flash. Every file failed at the same time. If anyone hears anything please post here or PM me just for a heads up. Im sure a few other desperate souls out there are anxiously waiting. Any reason the flash tools are incomplete? It doesnt seem like a big deal. Can someone here in the forum make one? Just couious.. i would gladly donate. Thanks for the info.
Click to expand...
Click to collapse
not really sure as i am new to LG.
been reading up on xda relating to flashing and rooting (i came from samdung phones) this baby. i think being patient here is what you can do at the moment.also, not only the dll file is missing, i read twrp is not saving backup properly due to the new security protocols in place android 7.0.
take heart mate,i know it sucks to have a bricked phone.

all im getting is "Unknown Model"

Managed to soft brick my H918 as well, so if anyone working on this needs a tester, I'd love to get my phone back.

Perion said:
Managed to soft brick my H918 as well, so if anyone working on this needs a tester, I'd love to get my phone back.
Click to expand...
Click to collapse
Check here
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423/page13
Sent from my Pixel XL using Tapatalk

alane708 said:
Check here
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423/page13
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I appreciate it, wish I'd seen that the day before. I tried to go back to stock recovery to see if that would fix my boot loop issue, so, without access to TWRP, I'm hosed until we have a method to reflash recovery from Fastboot or Update modem connection..

I am screwed as well, I messed my phone up too, and when I turn my phone on it automatically goes the to the upgrade mode screen, I want to through away this damn phone, hehehe.

Pixel Bricked & replaced - old phone returned - can i revive it somehow?

Hi all,
My Pixel bricked a few months back & was still under warranty. It was replaced & I've just today received the original bricked phone back to my surprise.
When plugged in via USB it shows as Qualcomm HS-USB QDLoader 9008
QFIL detects it but I can't find any .xml, .mbn, .hex files to flash it with.
Can i copy anything of the working phone (exact same model), to my laptop to then revive the bricked phone?
Thanks in advance for your advice...

Any luck with this? My girlfriend's Pixel is stuck in this mode as well. I can't find these files anywhere on the net. She's starting to get a little cranky.....please help!

Unfortunately the files you are looking for are not available. The have not been released

shagbag913 said:
Unfortunately the files you are looking for are not available. The have not been released
Click to expand...
Click to collapse
Thanks for the reply. How and when do these files usually get released? Do you advise I keep the device in hopes that I will be able to revive it in the near future?
Thanks!

Melnutz said:
Thanks for the reply. How and when do these files usually get released? Do you advise I keep the device in hopes that I will be able to revive it in the near future?
Thanks!
Click to expand...
Click to collapse
I wouldn't advise keeping it. They honestly will probably never be released, sadly.

Adventur0us said:
Hi all,
My Pixel bricked a few months back & was still under warranty. It was replaced & I've just today received the original bricked phone back to my surprise.
When plugged in via USB it shows as Qualcomm HS-USB QDLoader 9008
QFIL detects it but I can't find any .xml, .mbn, .hex files to flash it with.
Can i copy anything of the working phone (exact same model), to my laptop to then revive the bricked phone?
Thanks in advance for your advice...
Click to expand...
Click to collapse
Melnutz said:
Any luck with this? My girlfriend's Pixel is stuck in this mode as well. I can't find these files anywhere on the net. She's starting to get a little cranky.....please help!
Click to expand...
Click to collapse
shagbag913 said:
Unfortunately the files you are looking for are not available. The have not been released
Click to expand...
Click to collapse
Melnutz said:
Thanks for the reply. How and when do these files usually get released? Do you advise I keep the device in hopes that I will be able to revive it in the near future?
Thanks!
Click to expand...
Click to collapse
shagbag913 said:
I wouldn't advise keeping it. They honestly will probably never be released, sadly.
Click to expand...
Click to collapse
Wrong! I just did it!
https://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
Follow that guide but with the files provided here https://forum.xda-developers.com/pixel/help/fix-google-pixel-help-noob-t3790470
(https://dl.google.com/dl/android/aosp/sailfish-opm4.171019.016.b1-factory-68c3a77d.zip)
All you need is a working bootloader, thank God. This just saved my ass.

Creed14 said:
Wrong! I just did it!
https://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
Follow that guide but with the files provided here https://forum.xda-developers.com/pixel/help/fix-google-pixel-help-noob-t3790470
(https://dl.google.com/dl/android/aosp/sailfish-opm4.171019.016.b1-factory-68c3a77d.zip)
All you need is a working bootloader, thank God. This just saved my ass.
Click to expand...
Click to collapse
Your right, IF you have a working bootloader. The op does not.

I was having this same issue. Currently running crDroid and selected the Reboot Recovery option from the advanced Power Menu. It turned off but didn't come back on. Tried booting into the bootloader but got nothing. Plugged it into my PC and saw the same device description then realized I probably had a hard brick. I was about to give up when I decided to just hold the power button alone and after about 20 seconds it booted normally. Looks like I dodged a bullet.

shagbag913 said:
I wouldn't advise keeping it. They honestly will probably never be released, sadly.
Click to expand...
Click to collapse
Is there a way to pull it off a working Pixel? I have two 128GBs Pixels with the exact that were running the exact same setup (Unlocked BL with LOS15.1)

oppo find x2 softbrick at qdloader 9008. how to

hello guys. When installing the rollback of android 10, the phone has been stuck in the installation. I cannot enter recovery, I can only turn off the phone and the pc detects it as qdloader 9008, I know that with qfil I can install the rom, but I cannot find the necessary files, the .mdn file of the cph2023 global version. somebody could help me? thank you

ferchu91 said:
hello guys. When installing the rollback of android 10, the phone has been stuck in the installation. I cannot enter recovery, I can only turn off the phone and the pc detects it as qdloader 9008, I know that with qfil I can install the rom, but I cannot find the necessary files, the .mdn file of the cph2023 global version. somebody could help me? thank you
Click to expand...
Click to collapse
I have exactly the same issue did you find a fix? or the .mdn at all?

DanTh0mas said:
I have exactly the same issue did you find a fix? or the .mdn at all?
Click to expand...
Click to collapse
Sorry for take a long time. I did not find the solution. luckily I work in an electronics store and gave it to one of our clients who repaired it.

DanTh0mas said:
I have exactly the same issue did you find a fix? or the .mdn at all?
Click to expand...
Click to collapse
I had a similar issue, got hold of some files and tried flashing with MSNDownloadTool and QFIL but kept getting errors (think the files may have been dodgy).
Sent back to Oppo and they repaired under warranty (even though mine was the Chinese version and I am in the UK and its a 2nd hand phone) - really good service from them.

klanbo78 said:
I had a similar issue, got hold of some files and tried flashing with MSNDownloadTool and QFIL but kept getting errors (think the files may have been dodgy).
Sent back to Oppo and they repaired under warranty (even though mine was the Chinese version and I am in the UK and its a 2nd hand phone) - really good service from them.
Click to expand...
Click to collapse
They didn't ask you for the purchase invoice?

Nope, I didn't have one and they didn't ask. I contacted through the Oppo Facebook page and they were really helpful.