Messed up Qualcomm bootloader, anyway to fix ? - Nokia Lumia 800

Hey guys,
I have a Lumia 800 with a "messed up" Qualcomm bootloader. Here's what's different about it:
- Power+Vol.UP button combination doesn't work. Every other combination works great (FTM, Hard Reset, etc.).
- Since that combination doesn't work, I can't get to OSBL mode without NSSPro.
- When in OSBL mode, it shows up as Qualcomm CDMA Technologies MSM on Windows, OS X and Ubuntu but doesn't show its NAND partitions.
- In the Device Manager on Windows, the device has a tiny yellow warning sign like it's not working properly or it doesn't have the correct drivers. I tried installing/uninstalling the Qualcomm drivers from the other thread but nothing changed.
Is there any way to "repair"/reset the bootloader or force it to show its partitions ? Obviously I'm very careful with it so it doesn't get replaced with a DLOAD one.
I can put the USB debug logs from any/all of the OS if it might help.
Please help if you have any idea. Thanks.

---

I have tried all kinds of things on Windows.
I tried forcing the generic USB Mass Storage Device driver but it said it couldn't "start" the device.
I also installed all kinds of Qualcomm drivers I could find. I found the correct one, Qualcomm HS-Diagnostics 9006 (COMx), though unsigned (and still showing the yellow warning sign). Lumia still doesn't show the partitions.
Installed QPST (had weird errors about not being able to register a lot of DLLs while installing) and the Lumia didn't even appear in the devices list. (might be because of the broken install, I don't know)
Any ideas ?

---

inket said:
I have tried all kinds of things on Windows.
I tried forcing the generic USB Mass Storage Device driver but it said it couldn't "start" the device.
I also installed all kinds of Qualcomm drivers I could find. I found the correct one, Qualcomm HS-Diagnostics 9006 (COMx), though unsigned (and still showing the yellow warning sign). Lumia still doesn't show the partitions.
Installed QPST (had weird errors about not being able to register a lot of DLLs while installing) and the Lumia didn't even appear in the devices list. (might be because of the broken install, I don't know)
Any ideas ?
Click to expand...
Click to collapse
Mine does the same thing... My guess is that it is a intermediate version between full dev qualcomm bootloader and nokia dload that they rushed out.
What's your phone info?
My Lumia's information (weird bootloader):
Firmware: 12070
Hardware revison: 112.1402.2.3
Radio SW version: 1.6.00.24
Radio HW version: 8255
Bootloader version: 7.35.0.0
Chip SOC version: 0.74.2.1
ROM Language: 0C0A (Spanish (Spain))
ROM version: 7.0.8107.0
OEM Device Name: RM-801 EU 238
Mobile Operator: 000-ES
IMEI: 35928904 67xxxxx
Friend's (Nokia DLOAD):
Firmware: 12070
Hardware revison: 112.1402.2.3
Radio SW version: 1.6.00.24
Radio HW version: 8255
Bootloader version: 7.35.0.0
Chip SOC version: 0.74.2.1
ROM Language: 0809 (English (United Kingdom))
ROM version: 7.0.8107.0
OEM Device Name: RM-801 EU NDT EURO1
Mobile Operator: 000-33
IMEI: 35928904 79xxxxx
I have thought to open the phone and remove the battery to see if it helps, but I haven't tried it yet.

---

At least, I'm not the only one.
Here's mine:
OS: 7.10.8107.79
Firmware: 1600.2489.8107.12072
Hardware revision: 112.1402.2.3
Radio SW version: 1.6.00.24
Radio HW version: 8255
Bootloader version: 7.35.0.0
Chip SOC version: 0.74.2.1
IMEI: 3592890464xxxxx
Product Code: 059L702
Basic Product Code: 059J2N6
Type Designator: RM-801
Production SN (PSN): 004370FAB (< copied this because it seemed interesting)
That's all I found on WP, NCS and NSSPro. Where did you find the other info ?
I know that mine came from Vodafone Spain and 11414 firmware. Interesting, right ? Both from Spain.

---

My phone is the Unlocked Spanish country version, came with 11412.
I got the information from the diagnostics app (dial ##634#). I don't know if the diagnostics from 12072 has all this data (it should), I haven't updated mine from 11500.
Where did you get the PSN?
The question is: it is related to the country variant or to the production run?

---

I found the PSN on both NSSPro and NCS. Look in the Extended Info in NCS, I think.
My Lumia's info from Diagnostics:
ROM Language: 0C0A (doesn't say "(Spanish(Spain))" or anything, just 0C0A)
ROM version: 7.0.8107.0
OEM Device Name: RM-801 EU 214
Mobile Operator: VOD-ES
So far the only similarity is that they're both from Spain.

---

Nothing new, I guess ?
I'm thinking of trying NCS' "Refurbish" or "Recovery".
Anyone care to explain how do they work or what do they do exactly ?
I still don't want to replace the bootloader with Nokia's; I'm looking if there's a way to "refresh" the bootloader or something like that.

---

just take the battery out and insert after 10 or more second..then press and hold the vol up and insert the usb cable while holding vol up ....usb should be connected to pc from other end...after u inserted usb in phone u feel a short vibration, then leave the vol button and u'll be in qpst mode..

---

@debbuger
Are you sure that would work ?
I mean, did you have the same problem and you fixed it by removing the battery ?

---

sorry bro i thought that u've lumia 710.. don't remove battery do as follows --
as u r on l800
force it off by pressing the power switch for about 10 to 15 sec ,
then press and hold vol up and insert the usb ..a short vibratin means u r in osbl mode...

---

Already tried that. Doesn't work. Thanks anyway.

---

can u tell me if ur lumia is shipped with qualcom boot or you have flashed it after ...

---

It shipped that way.

---

Can you post the USB ID of the phone in bootloader mode? (lsusb -n in Linux, or Details tab in the Windows device manager)

---

Oh my brothers lumia 710 was given for a repair ang was returned with dload
Sent from my MB865 using xda premium

---

lsusb:
Bus 001 Device 002: ID 05c6:9006 Qualcomm, Inc.
Ubuntu's lsusb doesn't have the option '-n' so I'll paste the verbose output:
Code:
Bus 001 Device 002: ID 05c6:9006 Qualcomm, Inc.
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x05c6 Qualcomm, Inc.
idProduct 0x9006
bcdDevice 0.00
iManufacturer 3
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 1
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 32
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 32

---

Seems like your phone is going into QHSUSB_DLOAD mode, whenever you try to use bootloader mode. Also, you get "Couldn't open device", which sounds like a hardware issue. Take it to the repair shop.
One thing to try is plug in the phone normally into your computer (while in Linux), and turning it on. Post the device IDs that show up in "dmesg" after doing that.

---

Thanks NetRoller.
.NetRolller 3D said:
Seems like your phone is going into QHSUSB_DLOAD mode, whenever you try to use bootloader mode.
Click to expand...
Click to collapse
What's QHSUSB_DLOAD mode ? I looked all over the internet and found nothing answering that...
Please note that this mode isn't triggered with the Power+VolUp combination, but by selecting OSBL Mode in NSSPro. I don't know much about this but maybe selecting other modes in NSSPro could be more "useful" ?
.NetRolller 3D said:
Also, you get "Couldn't open device", which sounds like a hardware issue. Take it to the repair shop.
Click to expand...
Click to collapse
I just realized, the "Couldn't open device" is because I ran lsusb as a user (without sudo)... I'll try it again and paste the output.
.NetRolller 3D said:
One thing to try is plug in the phone normally into your computer (while in Linux), and turning it on. Post the device IDs that show up in "dmesg" after doing that.
Click to expand...
Click to collapse
Doesn't seem to have anything important (I added comments):
Code:
[345141.576034] usb 1-6: new high-speed USB device number 3 using ehci_hcd
[345142.410405] generic-usb 0003:045E:041E.0001: hiddev0,hidraw0: USB HID v1.10 Device [Microsoft Windows Phone] on usb-0000:00:1d.7-6/input0
[345142.410441] usbcore: registered new interface driver usbhid
[345142.410445] usbhid: USB HID core driver
# vibration
# screen ON but black, stays like that for 15s
[345157.617055] usb 1-6: USB disconnect, device number 3
# shuts down
# vibration
# boots
[345178.864037] usb 1-6: new high-speed USB device number 4 using ehci_hcd

---

Does Power+VolUP put it into "mass storage" mode?

---

Power+VolUp does nothing. Long vibration and it just boots normally. Here's the `sudo lsusb -v` after switching to "OSBL Mode" through NSSPro:
Code:
Bus 001 Device 005: ID 05c6:9006 Qualcomm, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x05c6 Qualcomm, Inc.
idProduct 0x9006
bcdDevice 0.00
iManufacturer 3 Qualcomm, Incorporated
iProduct 2 Qualcomm CDMA Technologies MSM
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 1 Qualcomm Configuration
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 32
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 32
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)