[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Ok I just looked at the lsusb and dmesg in the other thread, your device is as [MENTION=229050]VBlack[/MENTION] said some other strange mode :confused: The Unbrick project appeared to at least attempt to work originally I see also until you fixed the issue of the drive partitions.

I'm assuming your working from a USB stick? Which version of Ubuntu are you using?

Normally we see 2 different modes of QHSUSB_DLOAD

A - QHSUSB_DLOAD (Qualcomm USB Storage Device)

B - QHSUSB_DLOAD (Qualcomm Wireless Gobi Modem)

When the device is seen by Linux in mode A the device can be rescued with the Unbrick project emmc recover as we can still see the storage device to write files to it.

When the device is seen by Linux in mode B this is a different matter. If Linux see's the wireless gobi modem, this generally means that the main processor or (AP Processor) is no longer functional or something vital to it (e.g the mainboard) is no longer functional.

To expand on that, a little explanation. Not many people know that Smart phones in general (Including IPhones) are made up of 2 separate computers running largely independent of each other.

Firstly we have the Main Processor, (the AP Processor) or the Quad Core Snapdragon in the case of the M7 is the AP processor. This runs the android OS and all the other main peripherals of the android side of the device. e.g The camera, Bluetooth, WiFi and so on.

Secondly and perhaps more importantly we have the Baseband Processor (or the Qualcomm wireless gobi modem) This run's in a completely separate operating environment to the rest of the device. With its own Processor, Operating system and even power supply. And it controls the Cell side of the phone. Mobile Network, 4g, 3g, LTE and so on.

Obviously if only one or the other is functioning normally it can cause some big issues. Problems from the Android side of the device cause QHSUSB_DLOAD. If this is caused by a hardware failure generally the device is all but dead from the Android side, but the Baseband processor is still functional. Hence the reason we can see the wireless gobi modem listed as an attached device in Linux.

If it's caused by a software problem, generally it's some type of firmware incompatibility that prevents the AP processor communicating with the Baseband Processor. But as both devices are still in fact functional we can still see the device as a Storage Device as apposed to just the modem. Then we can write the necessary files to the device to revive it.

Putting the shoe on the other foot, What if the Baseband Processor stops functioning while the AP processor is still working perfectly fine. Then we get a completely different problem also well discussed here on XDA. "Unknown IMEI and Baseband" and this has an even lower repair success rate than QHSUSB_DLOAD.

Unknown IMEI and Baseband is caused when the AP processor is working normally but cannot communicate with the Baseband processor. This can be caused by a number of issues mostly hardware related. It could be the Baseband Processor itself is dead or damaged, a faulty Antenna connector wire or failure of the Baseband processors power supply all hardware related problems. From the software side a corrupt Radio.img could also cause Unknown IMEI and Baseband in which case flashing an RUU or returning to stock some other way can fix Unknown IMEI and Baseband.

Any who i'm getting off track here a little. Your device doesn't appear to be in either of the known QHSUSB_DLOAD modes. I'm not sure what that means. Unfortunately it could be that neither the AP processor or Baseband Processor are functioning. Which is not good news :( or it could be some connectivity issue or incompatibility with your chosen Linux Distro that is showing only the basic info about the device. Although the dmesg shows it as Qualcom usb modem converter which does suggest at least the AP processor is not working. There is a good chance your working towards a dead end but if you can get the correct files I'd be interested to know if you can get this back up and running.

Sorry for the wall of text possibly containing many typo's lol. But I thought an explination may help towards your final goal. Good luck I will stay subscribed to this thread if there's anything else I can provide let me know :good: