my nokia 620 got damaged while working with the wpinternals program. Now it won't start. In the device manager it appears as qualcom 9008 and then freezes the computer. Do you know what happened to this phone and how to fix it? thor2 shows connection problem.
Im think Nokia lumia 620 wasnt in emergency mode.
How to enable this mode? is there any way
when trying to upload via thor2, the message CONNECTION NOT FOUND appears
ATF
I was able to upload a big-boot using atf. Is it possible to upload individual partitions separately: MainOS, Data etc. I have a copy with data and I would like to restore it.
the lumia 620 is now red screen.
user restore bootloader feature of wpinternal
Related
Hello...
i've got a bricked phone from a friend of mine because he's out of options to put it back to fully function.
he told me that he had flashed the phone while it was in 9008 usbbulk whith a recovery thats not suitable for this
phone. now the only thing the phone is doing is turn backlight on when connect to pc ... it will not be recognized. all drivers are installed .... windows runs on test mode with no verfication for drivers or else ... is it possible to rescue the phone or is it good white brick ?
Phone Data:
LG K10 (420N)
16 GB
TheRazcall said:
Hello...
i've got a bricked phone from a friend of mine because he's out of options to put it back to fully function.
he told me that he had flashed the phone while it was in 9008 usbbulk whith a recovery thats not suitable for this
phone. now the only thing the phone is doing is turn backlight on when connect to pc ... it will not be recognized. all drivers are installed .... windows runs on test mode with no verfication for drivers or else ... is it possible to rescue the phone or is it good white brick ?
Phone Data:
LG K10 (420N)
16 GB
Click to expand...
Click to collapse
Do you see anything in device manager?
No... device manager shows nothing and there is no satisfaing "da ding" noise after plug in the USB to my PC...
Hi All,
Is there any way to recover the phone from the Quectel QDloader 9008 COM mode ? Screen not coming up, no adb or fastboot mode, the only think I see in the Windows Device Manger is that the phone is connected as COM Port.
Thx for any advice.
Have the same issue - were you able to figure out how to fix it?
The only way to fix it would be to have a copy of the ROM that can be flashed in EDL mode, which is the mode your device is in. Google doesn't make EDL-flashable copies of its ROMs available - not a surprise - since that mode is mainly for tech support personnel. I'm afraid your only recourse is to contact Google and see what they can do for you.
freshmike said:
Hi All,
Is there any way to recover the phone from the Quectel QDloader 9008 COM mode ? Screen not coming up, no adb or fastboot mode, the only think I see in the Windows Device Manger is that the phone is connected as COM Port.
Thx for any advice.
Click to expand...
Click to collapse
Phone should still be covered under manufacturer's warranty if anything call it in see you at the phone shut off and did that and they'll replace it
@freshmike what did you do to get to this state?
davidcie said:
@freshmike what did you do to get to this state?
Click to expand...
Click to collapse
No idea, not mine got it from a friend to try to fix. I think the memory is grilled. On the other hand there are so many complains regarding the quality of Pixel phones, I would not want one even as a gift
try it !
Hi, I need help, I got Lumia 925 and the only activity it shows is the storage when i connect it to the PC, and also i get a beep sound when connected to the charger but thats it. The screen stays blank. Even after using windows device recovery tool and installing firmware nothing happens.
Any suggestions?
Display or motherboard fault.
uiqjirka said:
Display or motherboard fault.
Click to expand...
Click to collapse
I see, thanks.
I got another 925 that died while attempting to unlock the bootlocker with WPinternals , its not even detecting the USB anymore. I wonder if there is anything I can do with that one. I would do anything at this point
Hello, I need help with my LG, the cell phone ran out of battery while updating firmware, now I cannot enter download mode, nor fastboot, and the recovery does nothing, when I turn on the cell phone it always ends up in a black screen with a text of the type "CMD" putting a number and something of "udc_start" and that's it.
windows 10 makes the normal beep but does not recognize the model, in the device manager "android device" appears with the warning sign that there are no drivers.
LGUP does not recognize the device
The only way I had to "make windows recognize it" was with "QFIL" and touching the two pins on the motherboard, in the program it says:
"qualcomm hs-usb qdloader 9008 (com4)"
I have never flashed a cell phone bios or a bootloader if I misunderstand (I am relatively new to android), I have only flashed "the operating system" in this case a 1gb .kdz
I have no idea how to do this, if I don't misunderstand, I need a .mbn (I think it's the bios), which is compatible with QFIL, which I couldn't find in all of google.
I've come across other .mbn of "similar" g4 models, I wonder if it will work if I at least try them.
They may not work perfectly, but at least turn on.
What do you suggest? I feel lost in an ocean t-t
Wachecheiro said:
Hello, I need help with my LG, the cell phone ran out of battery while updating firmware, now I cannot enter download mode, nor fastboot, and the recovery does nothing, when I turn on the cell phone it always ends up in a black screen with a text of the type "CMD" putting a number and something of "udc_start" and that's it.
windows 10 makes the normal beep but does not recognize the model, in the device manager "android device" appears with the warning sign that there are no drivers.
LGUP does not recognize the device
The only way I had to "make windows recognize it" was with "QFIL" and touching the two pins on the motherboard, in the program it says:
"qualcomm hs-usb qdloader 9008 (com4)"
I have never flashed a cell phone bios or a bootloader if I misunderstand (I am relatively new to android), I have only flashed "the operating system" in this case a 1gb .kdz
I have no idea how to do this, if I don't misunderstand, I need a .mbn (I think it's the bios), which is compatible with QFIL, which I couldn't find in all of google.
I've come across other .mbn of "similar" g4 models, I wonder if it will work if I at least try them.
They may not work perfectly, but at least turn on.
What do you suggest? I feel lost in an ocean t-t
Click to expand...
Click to collapse
Check out this thread:
[GUIDE][9008][EDL|QDL][QUALCOMM ONLY] Unbrick via external sdcard (no QFIL!)The author is the definitive LG G4 hard-brick answer guy with possible solutions. You may be able to get some help there.
sdembiske said:
Check out this thread:
[GUIDE][9008][EDL|QDL][QUALCOMM ONLY] Unbrick via external sdcard (no QFIL!)The author is the definitive LG G4 hard-brick answer guy with possible solutions. You may be able to get some help there.
Click to expand...
Click to collapse
I'll take a look at it, thanks
Seems like a similar problem as I had, that's not gonna work though. The only way to fix it is to use a firehose which you can use a one from a Cyanogen MSM8939 device.
UPDATE: The issue stands solved [see post 5].
........................................................................................................................................................................
I am facing a rather intriguing issue wherein the device tends to automatically exit EDL Mode after around 5 seconds. During that short-time frame, the Device Manager recognizes it in EDL Mode as Qualcomm HS-USB QDLoader 9008. Even the MSM Tool is able to identify the connected device. However, right after a few seconds the device gets booted to the OS.
So could anyone let me know why is this happening and more importantly how it could get rectified. [Windows Driver Signature Verification is disabled and Qualcomm USB Drivers are successfully installed].
Moreover, currently I'm on Pixel Experience ROM. So are custom ROM's known to cause any conflict with EDL Mode?
EDIT My device is not bricked and I could easily access the OS [Pixel Experience]. However, I still want to use MSM Tool as opposed to say, Fastboot Enhance Tool, for testing purpose. So any insights in this regard will be highly appreciable.
My way was :
Launch MSM Tool
Launch Phone into Recovery
Connect USB Cable
Advanced -> allow ADB
On PC : adb reboot edl
As soon as the Device Screen turns black, Phone gets detected in MSM Tool and then Start Process. That worked for me
ohwarumbloss said:
My way was :
Launch MSM Tool
Launch Phone into Recovery
Connect USB Cable
Advanced -> allow ADB
On PC : adb reboot edl
As soon as the Device Screen turns black, Phone gets detected in MSM Tool and then Start Process. That worked for me
Click to expand...
Click to collapse
I face the same issue on my OnePlus 9 and this help me. Thank you so much.
binary**# said:
I am facing a rather intriguing issue wherein the device tends to automatically exit EDL Mode after around 5 seconds. During that short-time frame, the Device Manager recognizes it in EDL Mode asQualcomm HS-USB QDLoader 9008. Even the MSM Tool is able to identify the connected device. However, right after a few seconds the device gets booted to the OS.
So could anyone let me know why is this happening and more importantly how it could get rectified. [Windows Driver Signature Verification is disabled and Qualcomm USB Drivers are successfully installed].
Moreover, currently I'm on Pixel Experience ROM. So are custom ROM's known to cause any conflict with EDL Mode?
EDIT My device is not bricked and I could easily access the OS [Pixel Experience]. However, I still want to use MSM Tool as opposed to say, Fastboot Enhance Tool, for testing purpose. So any insights in this regard will be highly appreciable.
Click to expand...
Click to collapse
were you able to find any work around. I am currently on OOS 12 F.22. I am having another issue of widevine L1 certification as my device has L3 certificate. To rectify this i am trying to use MSM tool.
raoakashyadav said:
were you able to find any work around. I am currently on OOS 12 F.22. I am having another issue of widevine L1 certification as my device has L3 certificate. To rectify this i am trying to use MSM tool.
Click to expand...
Click to collapse
Sorry for the delay in reply. Yup, I fixed this issue via the Disable Driver Signature Verification tweak as shown in this video. In short -->
Install Qualcomm USB Driver and download MSM Tool.
Boot your device to EDL Mode and connect it to your PC.
Then DO NOT disable Driver Signature Verification on your PC.
So as of now, your device will be listed as Qualcomm HS USB QDLoader under Device Manager but will have a yellow exclamation mark [because Drive Signature is enabled]. But at the same time, Windows will hold your device in this ELD Mode and wouldn't let it boot to the OS [which is what we wanted].
So while having your device connected to your PC in EDL Mode, now disable Driver Signature Verification. With this, your device should now stay in EDL Mode and will be listed without any yellow warning sign under Device Manager. You could now proceed ahead with the flashing via MSM Tool without any issues.