Timeline for Wileyfox Swift won't boot, identifies as QHSUSB_BULK
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 26, 2017 at 12:15 | vote | accept | Izzy | ||
| Oct 26, 2017 at 11:30 | answer | added | Wileyfox NL | timeline score: 1 | |
| Oct 19, 2017 at 17:35 | comment | added | Grimoire | To be honest, I don't know whether you did it on purpose or not, and it's not my job to know #D. Anyways, I had to install Windows 7 specifically for having Odin communicate to a SM-A520F, so I sort of know what you're implying. | |
| Oct 19, 2017 at 17:30 | comment | added | Izzy | I've got no Windows (except those for light and fresh air), so I cannot follow that procedure. But WTF: Holding VolUp and VolDown while plugging in USB bricks the device? No shit? Who had that brilliant idea? You know how easily that could happen. Though it could come in handy for a device refresh a month before warranty ends… (no speculations: I didn't do that. Didn't even know before I read that XDA post you've linked) | |
| Oct 19, 2017 at 17:21 | comment | added | Grimoire | That's support for you. If your warranty is still up, then relay the responsibility to them. Otherwise, this seems like an interesting starting point. | |
| Oct 19, 2017 at 17:16 | comment | added | Izzy | Thanks again, @DeathMaskSalesman – I'll check that and report back. But if my warranty is still up, I might be better of accepting Wileyfox' offer of sending the device in; at least, if they break it they know how to replace it :) Funny thing with "canned blocks": They suggested I should back up everything before sending it in. Wish they'd explained how to do that with the device not even booting up :) | |
| Oct 19, 2017 at 17:11 | comment | added | Grimoire |
cough time-bomb cough. Aside from the speculation, I'll suggest you to search for xda qfil, as the flashing procedure is the same for every phone in such condition. The catch is, that many malware disguised as Qualcomm tools is around, so tread carefully. I'll see if I can dig up something, but I'm not familiar with the toolkit either.
|
|
| Oct 19, 2017 at 17:08 | comment | added | Izzy | @DeathMaskSalesman thanks for confirmation – and yes, that was my (temporary) conclusion. But as you write (which again confirms my findings) it's "used for flashing firmware", I was hoping to be shown a way to do so and, in that process, fix the bootloader. // What I completely fail to grasp is how the bootloader got damaged tonight. I didn't fiddle with it – the device still has its original firmware and all. Last "flashing stuff" was done more than a year ago (TWRP), and there have been several boots since. | |
| Oct 19, 2017 at 17:03 | comment | added | Grimoire |
As you've already searched for QHSUSB_BULK, I take it for granted that you know your phone is bricked, and its bootloader has been damaged. That identifier stands for the Qualcomm 9008 emergency mode, which is used for flashing firmware.
|
|
| Oct 19, 2017 at 16:09 | comment | added | Izzy | Note: After having posted the question I've reached out to Wileyfox support. Surprisingly I already got an answer about an hour ago, asking me to send in the device for them to check directly. Need to check warranty state etc. first of course. Will update details / answer the question as soon as I've obtained sufficient information. | |
| Oct 19, 2017 at 11:30 | history | asked | Izzy | CC BY-SA 3.0 |