Found my original little idea sketch for that bonzi buddy comic that took off a while ago. Plus a bonus bonzi Garf
This page's posts are visible only to users who are logged in.
I have a Nokia Lumia 521 with some very odd behaviour that, now that I look into it, seems very common for qualcomm snapdragon-based devices. Essentially, when plugged in to a PC, it will vibrate and show as a HID device VID_05C6&PID_F006. The phone will get a bit warm, but nothing else will happen, not even the screen will turn on.
The first thing I found was this XDA thread: https://forum.xda-developers.com/t/my-lumia-520-is-ded.3534676/
This gives some basic info:
- Showing as device ID 05C6:F006 occurs when the battery is completely depleted.
- Removing the battery should make it not vibrate or detect at all -- can confirm this
From this, I can kind of figure out where the issue lies, given some other info I know about this phone:
- I know the battery I am using to be good as of a few months ago, since I was able to test it in a different phone.
- It also doesn't do anything when not pulgged into a power source.
- It is showing the symptoms of having a depleted battery.
- Also, last I checked, leaving it plugged in for 12 hours does not do anything different.
It seems like this should be some kind of power management issue. (Though, I have heard that this issue is sometimes blamed on firmware corruption, but I'm not sure yet.) I'm not exactly sure what kind, though. It seems that it can differintiate between having a battery and not when connected to a PC, so the connection to the battery is probably at least partially okay. Still, it's not that helpful for actually trying to fix it.
After more searching, specifically the device ID that it shows up as, I found this about a Nexus 4: https://thecomputerperson.wordpress.com/2015/12/29/google-lg-nexus-4-red-flashing-light-unusual-behavior/
It seems the Nexus can have a similar issue, although it will actually start up if you play with it a bit! I sort of suspect that it's the same root cause, especially since it's "bizzare power management related issues" on the same SoC series. There is no fix, but this does confirm that power-related issues is not exclusive to Windows Phone.
However, the more intresting part of this post is that it mentions this is connected to the (3G) Modem directly. Definitely very odd behaviour and I'm unsure where the source for this is...
Anyway, I did a lot of searching, and came to things like HTC's having the same issue and a fiarphone forum thread with confirmaion that dead batteries can cause this, from a qualcomm engineer and then even more confirmation this isn't a rare issue, but maybe the most helpful hint is this:
The instructions are not very understandble to me, but essentially there is a way to get to EDL from "modem mode" by using a cable. (Also, just looking it up, there is a way to do this by shorting some board points out aswell: https://forum.xda-developers.com/t/lumia-x2x-series-service-manuals-unbrick-from-05c6-f006.4361801/) I've not tried it yet, but I think it's really the only thing I can do, there are seemingly better tutorials and I don't think anything will explode, so...
I've not been able to build the cable, but I noticed that if you plug the phone in after a long time away from a power source1, it will connect in QDL for a few seconds:
$ lsusb
Bus 007 Device 005: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Before just going back to modem mode for some reason:
$ lsusb
Bus 007 Device 006: ID 05c6:f006 Qualcomm, Inc.
(Also, wow, file transfer STILL sucks in 2023.2)
-
This was also the first time I connected the device to this PC, so could this also be a factor(?) It seems unlikely, but possible.
-
Somehow Bluetooth was the fastest way to transfer the log file for this post, including having to figure out how to set it up.
The cable did not work. However, I found that if I parially unplug the USB cable after it vibrates and then quickly plug it back in,1 it will start reporting as being in download mode (05C6:9008 QHUSB_DLOAD).
... What the fuck?
And I say "report as" because while it does show up properly in Windows, it does not detect in WP internals or Windows Device Recovery Tool.2
-
Alternately, you can "wiggle" the usb connector until device manager refreshes then quickly connect it. It helps to have a pretty loose usb port for this.
-
I also tried a few different drivers: the lumia ones and the qualcomm serial ones. Nither find the device under windows.