Hi, around 4 years ago i flashed Android on my Lumia 520 by watching YouTube tutorials. It was working great but all of a sudden after few days it went to black screen, And its dead forever since.
I do have all the ROM backup(which the guide said were very important) and files that i used for flashing like TWRP , Android ROM etc , But unfortunately my device is not recognised by adb so i cannot follow any recover guide that are available here. And Windows Phone recovery tool doesn't even list Lumia 520 in its available devices.
Its currently recognised as "Qualcomm HS USB QD LOADER 9008 COM4" on my PC, Please see attached pictures.
Please give me some hope of getting my phone back to life.
Its been in coma for years sitting in my desk.
Any help if possible. Thanks
Related
Hi everyone
I tried to updade my huawei nova CAN-L11C530B130 to CAN-L11C432B340
I think the copy/paste of the UPDATE.APP ****ed up beacause the transfer time was very short...Anyway the phone accepted the update but turned off after that.
Now I can't boot, no recovery, no download mode, not even a charging led light.
Please tell me there is a way besides RMA
Thank you very much :good:
Well, either there is no charge (try keeping it on charger for a few hours) or it is totally bricked based on what you said. If it is completely unresponsive there is really nothing you can do.
Boot loader doesnt start as well?
Thanks for your help
I tried an all night charching but It did not help, no boot loader either.
What about the version I had : CAN-L11C530, I don't find any results about it on the internet, strange right ?
When I plug the phone to my computer I get "Qualcomm HS-USB QDLoader 9008 (COM3)"
You could try contacting Huawei support, their is a qualcomm flash tool. You need the tool and the rom to use it. I know it worked on the Nexus 5, but have seen nothing like it for us. I would try going to a shop and asking, but I do not know how viable that is for you.
Thank you wangdaning, it's very kind of you
I'm gonna leave the phone to the carrier who will send it to huawei.
I'm just surprised how easy it was to brick, I have a honor 8 and a mate 8 and it never happened.
I wonder if it comes down to it being a defective device. I have run circles of flashing on mine and it does not brick. I am running Lineage and even the build is not for my device. I have manually flashed partitions, wiped and reflashed partitions (in fastboot). I have made it unusable at times, but never bricked. It works fine now. Seems it might just be an unlucky bad unit you got. Hopefully you had all your stuff backed up and hopefully you get a unit that works well next time.
Hey sir
I just found an old lumia 525 in my house and I just got curiusd to install android on that. I had followed all the steps correctly. I unlocked the bootloader but when it come to run uefi2lk.cmd . I made a mistake that I did not ( plugged out usb and battery and insert it again ) and I directly click enter by mistakely.
And for that reason my windows phone got bricked. It only vibrating and the screen is not turning on . When I connect it with pc and went to control panel it showing android. By the way my phone have samsung emmc based storage. So if you have any short of trick in 2020 then please help me to resolve this problem.
Thanks you for giving your precious time.
Adi. 19 said:
Hey sir
I just found an old lumia 525 in my house and I just got curiusd to install android on that. I had followed all the steps correctly. I unlocked the bootloader but when it come to run uefi2lk.cmd . I made a mistake that I did not ( plugged out usb and battery and insert it again ) and I directly click enter by mistakely.
And for that reason my windows phone got bricked. It only vibrating and the screen is not turning on . When I connect it with pc and went to control panel it showing android. By the way my phone have samsung emmc based storage. So if you have any short of trick in 2020 then please help me to resolve this problem.
Thanks you for giving your precious time.
Click to expand...
Click to collapse
Hello, I am having same issue. Please let me know if you have got the solution.
I was on A11.1.1.1 , when I decided to root my device. Tried to install Twrp but failed, then unlocked boot loader and flashed magisk using Adb from my windows 7 desktop. Phone restarted, went into bootloop, then restarted naturally - however I couldn’t turn on Wi-Fi. Downloaded SuperSU, which showed device was rooted. In an attempt to revert back to stock os, I flashed another boot image, and phone went into continuous boot loop. So I searched the web and downloaded Qualcomm hs-usb QDloader 9008, and MsmDownload tool v 4.0 in an attemp to unbrick my device and installed them. However, my desktop doesn’t recognise my phone as Qhusb_bulk or as Qualcomm qhusb qdloader9008 in devicemanager. So I m unable to use the MSM tool to un brick my phone. Tried reinstalling the drivers on desktop , but the phone doesnt show up on device manager still. Only shows up as “pci simple communications controller” under other devices.
When i turn on my phone, it shows the OP logo going round and round for 5mins, then the screen goes blank. If I keep the power off button pressed for quite sometime, phone restarts into boot loop again. Can’t get into boot loader, nor does adb on my desktop recognise the device.
i m at my wits end as to how I m gonna unbrick my phone, as this is my primary phone. Kindly guide me step by step as to how to unbrick my OP6t. Any help is appreciated.
Jeet77 said:
I was on A11.1.1.1 , when I decided to root my device. Tried to install Twrp but failed, then unlocked boot loader and flashed magisk using Adb from my windows 7 desktop. Phone restarted, went into bootloop, then restarted naturally - however I couldn’t turn on Wi-Fi. Downloaded SuperSU, which showed device was rooted. In an attempt to revert back to stock os, I flashed another boot image, and phone went into continuous boot loop. So I searched the web and downloaded Qualcomm hs-usb QDloader 9008, and MsmDownload tool v 4.0 in an attemp to unbrick my device and installed them. However, my desktop doesn’t recognise my phone as Qhusb_bulk or as Qualcomm qhusb qdloader9008 in devicemanager. So I m unable to use the MSM tool to un brick my phone. Tried reinstalling the drivers on desktop , but the phone doesnt show up on device manager still. Only shows up as “pci simple communications controller” under other devices.
When i turn on my phone, it shows the OP logo going round and round for 5mins, then the screen goes blank. If I keep the power off button pressed for quite sometime, phone restarts into boot loop again. Can’t get into boot loader, nor does adb on my desktop recognise the device.
i m at my wits end as to how I m gonna unbrick my phone, as this is my primary phone. Kindly guide me step by step as to how to unbrick my OP6t. Any help is appreciated.
Click to expand...
Click to collapse
When you get it to reboot did you try holding volume down as it starts? Should get you into recovery then bootloader.
Also get magisk to root rather than SuperSU. You can install twrp from magisk in oos with the correct installer but first you have to root correctly with modded boot.img. Can make your own or get from the one post in here. I'd suggest getting the newest oos also.
Brettroth said:
When you get it to reboot did you try holding volume down as it starts? Should get you into recovery then bootloader.
Click to expand...
Click to collapse
Probably need to flash a stock boot of 11.1.1.1 to unbrick. You can try booting to the newest twrp from fastboot I'm not sure if it works anymore.
Brettroth said:
Probably need to flash a stock boot of 11.1.1.1 to unbrick. You can try booting to the newest twrp from fastboot I'm not sure if it works anymore.
Click to expand...
Click to collapse
Couldn’t fastboot into twrp, since device got corrupted while trying to flash multiple things. Thankfully while tinkering, my desktop recognised my device as qhusb qloader 9008, and all I had to do was boot my device into edl mode (which was also a pain tbh!). After trying numerous key combinations and timing it perfectly, device booted into edl and I could use the msm download tool to unbrick my device. Now device has rebooted into iOS 10.3.5 (same version as msm tool version) and I have somehow breathed a huge sigh of relief that my device could be resuscitated. Will be updating to 11.1.1.1 now (I see the latest is 11.1.2.2) and setting up my device now.
Thank you a lot for looking into my issue and suggesting solutions. In my younger years, I was a technology enthusiast and often rooted/flashed, but have pursued medicine since then. Now am out of touch completely to the tech scene and it was a grave blunder on my part to have used my primary driver to try and root/flash again.
Have a great day, my friend and please know that it means a lot to me to have received help from the community.
Jeet77 said:
I was on A11.1.1.1 , when I decided to root my device. Tried to install Twrp but failed, then unlocked boot loader and flashed magisk using Adb from my windows 7 desktop. Phone restarted, went into bootloop, then restarted naturally - however I couldn’t turn on Wi-Fi. Downloaded SuperSU, which showed device was rooted. In an attempt to revert back to stock os, I flashed another boot image, and phone went into continuous boot loop. So I searched the web and downloaded Qualcomm hs-usb QDloader 9008, and MsmDownload tool v 4.0 in an attemp to unbrick my device and installed them. However, my desktop doesn’t recognise my phone as Qhusb_bulk or as Qualcomm qhusb qdloader9008 in devicemanager. So I m unable to use the MSM tool to un brick my phone. Tried reinstalling the drivers on desktop , but the phone doesnt show up on device manager still. Only shows up as “pci simple communications controller” under other devices.
When i turn on my phone, it shows the OP logo going round and round for 5mins, then the screen goes blank. If I keep the power off button pressed for quite sometime, phone restarts into boot loop again. Can’t get into boot loader, nor does adb on my desktop recognise the device.
i m at my wits end as to how I m gonna unbrick my phone, as this is my primary phone. Kindly guide me step by step as to how to unbrick my OP6t. Any help is appreciated.
Click to expand...
Click to collapse
This happen to me several times and the first time it happened I thought my phone would not be unbricked after numerous attempts with the msm tool!
My issue was that my phone was a renewed amazon phone and amazon listed it as a unlocked international but it actually was a t-mobile variant and when i downloaded the correct msm tool with firmware it worked!
You need to get the phone into edl mode. For edl, when phone off press both volume buttons and plug in the usb while connected to your pc and the qualcom driver should pop up in device manager. After that finding the right msm firmware will be your next issue but with enough searching you should find it!
Let me know your progress with the driver and I can try and post some links to different msm firmware for the oneplus 6t!
Hello everyone !
I'm new on this forum but I really need your help. I tried to fix my mistake all day long yesterday (9am to 2am non stop).
So, basically, I have a OnePlus 8 Pro, Model IN2023.
I had OOS 11 updated. I tried to install OOS 12 Bêta and I did but I had a indian version so a lot of bugs.
I wanted to go back to OOS 11 but it was impossible because I was now in an indian version.
I tried with MyApplication2 to local upgrade and downgrade as recommand in Internet.
I tried to unlock bootloader and the following steps but here my problem:
I unlocked my bootloader then I misclick and I locked again my bootloader.
Then my phone just crashed and put this message:
"The current image (boot/recovery) have been destroyed and can not boot."
So, I forced to turn off the phone and try to go in EDL mode but:
1. ADB doesn't work anymore
2. Fastboot work fine
3. EDL mode is impossible
So, my bootloader is unlocked again. My phone is stuck on Fastboot mode:
Fastboot mode
Product_name - kona
Variant - SM8 UFS
Bootloader version -
Baseband version -
Serial number - eed52b71
Secure boot - yes
Device state - unlocked
I used the official firmware on OnePlus website, I used Python and Payload_dumper.py to have the .img from the .bin of the official firmware.
I tried to flash all the images, I tried to install TWRP, I tried almost everything I found but still stuck in Fastboot. Recovery mode doesn't work.
I tried to boot, to flash, to do everything I could.
I also tried MSM Download Tool but nothing appears inside.
Now, when I connect my phone, it's with a cable in USB-C but 3.0, not 2.0. Maybe that's the problem ?
When I plug my phone, in Device Manager, I have a "!" but the phone is recognized under
"Qualcomm HS-USB QDLoader 9008 (COM6). When I click on it, it says (sorry, I'm about to translate from french):
"Windows can not verify the numeric signature for the drives required for this peripheric. It is possible that a material ou software modification has been installed a corrupted file or with an incorrect signature, or it is a malware from an unknown source (Code 52)"
Please help me, contact me on Whatsapp, or here. Let's do this in direct.
Btw, I have a Macbook Pro to do all this. I used also Windows with Bootcamp.
So... I finally did it. 2 days to do it.
I asked a friend to lend his computer (Windows).
So my phone turned into EDL Mode immediatly without trying to do so.
I plugged into my MacBook under Windows (Bootcamp) and launch MSM Download Tool under an old version and it worked.
I tried first with the latest but I had "param preload failed" so I found a good article MAGIC and tada.
SUCCESS. My OnePlus 8 Pro works better than never.
Don't install OxygenOS 12, it's really bad.
andshura said:
So... I finally did it. 2 days to do it.
I asked a friend to lend his computer (Windows).
So my phone turned into EDL Mode immediatly without trying to do so.
I plugged into my MacBook under Windows (Bootcamp) and launch MSM Download Tool under an old version and it worked.
I tried first with the latest but I had "param preload failed" so I found a good article MAGIC and tada.
SUCCESS. My OnePlus 8 Pro works better than never.
Don't install OxygenOS 12, it's really bad.
Click to expand...
Click to collapse
Im happy you fixed your phone.
Read this before you even think to go to A12 again on this device.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Hi guys. As the title says I have a T-mobile Oneplus 6T running Android 11 and I think it is bricked. It is SIM unlocked and bootloader-unlocked as well. The problem started when I tried to flash TWRP and the phone continuously went to a Qualcomm CrashingDump state. Now I've tried several tutorials online but all of them point to the 10.3.8 instead of the 11 that the phone has and using the MSM Tool comes back as The image does not match the device. To make things worst following one of the videos I updated the Qualcomm drivers via WIndows Update and now my PC will not recognize the phone (USB not recognized by Windows error). Please I need the community's help on this one. Thank you soo much in advance.