FORUMS
Remove All Ads from XDA

Messed up Qualcomm bootloader, anyway to fix ?

69 posts
Thanks Meter: 9
 
By inket, Member on 19th June 2012, 07:37 PM
Post Reply Email Thread
6th February 2013, 05:25 PM |#11  
OP Member
Thanks Meter: 9
 
More
Already tried that. Doesn't work. Thanks anyway.
 
 
6th February 2013, 05:32 PM |#12  
debbuger's Avatar
Senior Member
Flag Dubai
Thanks Meter: 180
 
More
can u tell me if ur lumia is shipped with qualcom boot or you have flashed it after ...
6th February 2013, 05:43 PM |#13  
OP Member
Thanks Meter: 9
 
More
It shipped that way.
7th February 2013, 12:53 PM |#14  
Senior Member
Flag Budapest
Thanks Meter: 166
 
More
Can you post the USB ID of the phone in bootloader mode? (lsusb -n in Linux, or Details tab in the Windows device manager)
The Following User Says Thank You to .NetRolller 3D For This Useful Post: [ View ] Gift .NetRolller 3D Ad-Free
7th February 2013, 02:38 PM |#15  
shubham412302's Avatar
Senior Member
Thanks Meter: 145
 
More
Re: Messed up Qualcomm bootloader, anyway to fix ?
Oh my brothers lumia 710 was given for a repair ang was returned with dload

Sent from my MB865 using xda premium
7th February 2013, 10:47 PM |#16  
OP Member
Thanks Meter: 9
 
More
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
8th February 2013, 04:27 AM |#17  
Senior Member
Flag Budapest
Thanks Meter: 166
 
More
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.
The Following User Says Thank You to .NetRolller 3D For This Useful Post: [ View ] Gift .NetRolller 3D Ad-Free
8th February 2013, 04:55 AM |#18  
OP Member
Thanks Meter: 9
 
More
Thanks NetRoller.
Quote:
Originally Posted by .NetRolller 3D

Seems like your phone is going into QHSUSB_DLOAD mode, whenever you try to use bootloader mode.

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" ?

Quote:
Originally Posted by .NetRolller 3D

Also, you get "Couldn't open device", which sounds like a hardware issue. Take it to the repair shop.

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.

Quote:
Originally Posted by .NetRolller 3D

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.

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
8th February 2013, 07:55 AM |#19  
Senior Member
Flag Budapest
Thanks Meter: 166
 
More
Does Power+VolUP put it into "mass storage" mode?
8th February 2013, 09:24 PM |#20  
OP Member
Thanks Meter: 9
 
More
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)
9th February 2013, 01:00 AM |#21  
Senior Member
Flag Budapest
Thanks Meter: 166
 
More
That's basically the same, and it's not quite "QHSUSB_DLOAD".

How about Power+VolDn?
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes