I downloaded a stock Pixel 4a 5G ROM instead of the Pixel 4a stock ROM and flashed it. Now I'm stuck with a black screen with no ability to get into recovery. My device manager shows "Qualcomm HS-USB QDLoader 9008 (COM6) when connected to my computer. I've been following this thread https://forum.xda-developers.com/t/flashed-pixel-4a-with-pixel-5-image-by-mistake.4267097/page-2 and downloaded the Pixel 4a mbn someone linked but I'm still stuck. Any help would be very much appreciated
I am still amazed in this day of tech that the flasher doesn't compare the signature of the device to the intended device signature of the image file and at least warn if the two don't match!
SmegmaDong said:
I downloaded a stock Pixel 4a 5G ROM instead of the Pixel 4a stock ROM and flashed it. Now I'm stuck with a black screen with no ability to get into recovery. My device manager shows "Qualcomm HS-USB QDLoader 9008 (COM6) when connected to my computer. I've been following this thread https://forum.xda-developers.com/t/flashed-pixel-4a-with-pixel-5-image-by-mistake.4267097/page-2 and downloaded the Pixel 4a mbn someone linked but I'm still stuck. Any help would be very much appreciated
Click to expand...
Click to collapse
were you able to fix it?
Related
I'm one of the lucky people with a mostly dead 128gb pixel in HS-USB qdloader 9008 mode. There have been hints at a way of possibly reloading the chipset firmware to revive the phone enough to get to the bootloader.
There is a list of needed files needed for this: a device firehose file + some .xml files, plus some qualcomm software. Apparently someone has been able to pull these off a Pixel XL, but I'm curious if anyone has succeeded for the Pixel.
I have the same problem. Hundreds of people from Russia are watching this. We have the same trouble!
someone has been able to pull these off a Pixel XL ? i read the thread but i can't found who has get these files (MBN or XML)
MBN and XML files are not stored on device after flashing. This is exactly why they need to be sent by QFIL in order to start any flash (emmc, ufs) programming at all. Before Google or whoever produced a particular Pixel phone for them releases these or they're leaked we're out of luck.
Are there any news on this?
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
i bricked my realme 5 rmx1971 pro by flashing stock twrp rom to my devices. It is not booting at all. No fastboot no recovery. devices shows as qualcomm h in s-usb Qloader 9008 in ports. help would be really appreciated. I have tried differnt tools like msms tool crack , which gives sahara communication error. for qfil tool where to find firehose patch0 files.
bgaonkar96 said:
i bricked my realme 5 rmx1971 pro by flashing stock twrp rom to my devices. It is not booting at all. No fastboot no recovery. devices shows as qualcomm h in s-usb Qloader 9008 in ports. help would be really appreciated. I have tried differnt tools like msms tool crack , which gives sahara communication error. for qfil tool where to find firehose patch0 files.
Click to expand...
Click to collapse
If your phone is in warranty, you can get it fixed from authorised service centre for free.
If not in warranty, you will be charged for unbricking , like 1K INR.
You can also unbrick it online, search youtube, get numbers and contact. You will be charged around 1K.
Or
Wait till someone makes the device specific files to flash it through QFIL or MSM.
ATB.
SAME
I have a hard bricked OP9 and have tried alot of different guides from here or other ressources.
The problem is somewhere in the process something is not supported and the how to dies there.
MSM download tool prompts that says "Packed image not exists!"
OP9 LE2113 version (EU Version i guess)
Phone is black screen and can not be detected through ADB or fastboot. Either through the Qualcomm HS-USB QDloader 9008 Drivers.
Before it bricked it was unlocked (bootloader) Not sure it is anymore
Can someone send me a link or guide that can guide me the right direction?
Try the Oneplus 9 Pro India recovery tool. I know it doesnt make sense, but its the only thing that has worked for many, including myself and I have a OP9 5G North America.
Once recovered, the OS will boot but buggy. You can then restore to correct image via twrp full zip
Ill try that this evening, ill let u know ill turn out.
I typically run into sahara connection because i dont have connection through ADB of fastboot
#gorilla p
Try the Oneplus 9 Pro India recovery tool. I know it doesnt make sense, but its the only thing that has worked for many, including myself and I have a OP9 5G North America.
Once recovered, the OS will boot but buggy. You can then restore to correct image via twrp full zip
Click to expand...
Click to collapse
i have used this link
https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_9_Pro/ India version
And at the moment it is booting.
Unticked reboot and SHA check, This is indeed a good day !
Ive got a working phone again,
I will mark this thread as solved
OnePlus 8T+ 5G T-Mobile KB2007
My phone has become a brick. 3 days have been trying to restore it. Can't find the solution...
What issues I have:
- no "QHUSB_BULK" in Device Manager
- no "Qualcomm HS-USB QDLoader 9008" in Device Manager
- MSM tool doesn't see my phone
- EDL mode doesn't load
- fastbootd doesn't load
- all fastboot roms show a lot of errors during installation
Works only usual fastboot.
What can you recommend me to try? Thank you!
UP. Any thoughts? Any suggestions? Please!
Svobodniy_ said:
UP. Any thoughts? Any suggestions? Please!
Click to expand...
Click to collapse
It might help if you shared what you've actually done (what you did that resulted in bricking and what you've done to try fixing things) in detail. Include versions of software and source.
BillGoss said:
It might help if you shared what you've actually done (what you did that resulted in bricking and what you've done to try fixing things) in detail. Include versions of software and source.
Click to expand...
Click to collapse
It's complicated, because I tried a lot of ROMs from this forum and from other sources... The main problems, that MSM doesn't see my phone if I want to install ROM through MSM, and Fastboot give a lot of errors, if I want to install ROM through Fastboot...
How I brick my phone? I used file from OnePlus to unlock the bootloader (before it I unlock my phone from T-Mobile). After that all my data was wiped and I decided to change ROM from T-Mobile's to Global. I tried one of the ROM's (I don't remember which, but one from this forum). And my phone became a brick. (previously in my life I reinstalled a lot of ROMs on my Samsung Galaxy S2, Samsung Galaxy S4 - and have no issues, but this time...)
Use EDL to recover. You can get to fastboot, so you are not hard bricked. Make sure drivers are installed properly, try a different computer/cable
Svobodniy_ said:
OnePlus 8T+ 5G T-Mobile KB2007
My phone has become a brick. 3 days have been trying to restore it. Can't find the solution...
What issues I have:
- no "QHUSB_BULK" in Device Manager
- no "Qualcomm HS-USB QDLoader 9008" in Device Manager
- MSM tool doesn't see my phone
- EDL mode doesn't load
- fastbootd doesn't load
- all fastboot roms show a lot of errors during installation
Works only usual fastboot.
What can you recommend me to try? Thank you!
Click to expand...
Click to collapse
It seems, on PC side of things you don't have drivers properly installed, otherwise you wouldn't have
- no "QHUSB_BULK" in Device Manager
- no "Qualcomm HS-USB QDLoader 9008" in Device Manager.
For the same reason, i presume MSM doesn't see your phone.