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)
HTML:
Hey all,
So after successfully going S-off on my own phone, I was unable to do so on a friends. The problem now it seems is my linux box does not see the phone as /dev/ttyusb0 when plugged in.
lsusb shows as:
Code:
Bus 001 Device 016: ID 05c6:9008 Qualcomm, Inc.
But I am unable to complete the LazyPanda Unbricker because it does not see my phone. ADB devices does not show it either.
I have run modprobe qcserial many many times, as well as plug and unplug, hold power for 30 seconds etc etc to no avail but no /dev/ttyusb0.
So what are my options here? Any advice would be greatly appreciated. Really frustrated.
Upon further investigation the Qualcomm USB modem is registering
Code:
[11087.431154] usbcore: registered new interface driver usbserial_generic
[11087.431160] usbserial: USB Serial Driver core
[11087.434594] USB Serial support registered for Qualcomm USB modem
[11087.434839] usbcore: registered new interface driver qcserial
For the archives:
I was able to get the unbricker to work finally by using a different distro. Apparently older versions of Ubuntu server don't work. You must unplug any usb to serial converters as well because they will be bound to /dev/ttyUSB0.
run
Code:
sudo modprobe -r qcserial
Plug your phone in then run
Code:
modprobe qcserial
type dmesg and look to see if your phone is bound to /dev/ttyUSB0
if it is, you are good to go.
Hope this helps anyone who had the same issue as I did.
I am trying to resurrect my old Samsung Galaxy i5500. A couple of years ago I tried installing some custom rom but failed and bricked the phone. The boot process halts at the Samsung logo (the very first logo to appear.)
Putting the phone into recovery mode (using the volume down button + center button + power button) works, at least i presume that it works - the logo with the android shoveling dirt and the word "Downloading..." beneath it appears - but neither adb nor fastboot can see the device.
My troubleshooting so far:
Code:
[email protected]:~# dmesg
...
[823736.755555] usb 2-1.1: new high-speed USB device number 6 using ehci-pci
[823736.851772] usb 2-1.1: unable to get BOS descriptor
[823736.857819] usb 2-1.1: New USB device found, idVendor=04e8, idProduct=6601
[823736.857829] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[823736.857835] usb 2-1.1: Product: MSM7x27
[823736.857839] usb 2-1.1: Manufacturer: Sasmsung
[823739.903177] cdc_acm 2-1.1:2.0: ttyACM0: USB ACM device
[823739.903553] usbcore: registered new interface driver cdc_acm
[823739.903557] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[823761.102222] cdc_acm 2-1.1:2.0: failed to set dtr/rts
[email protected]:~# lsusb
...
Bus 002 Device 011: ID 04e8:6601 Samsung Electronics Co., Ltd Mobile Phone
...
[email protected]:~# adb devices
List of devices attached
[email protected]:~# fastboot devices
[email protected]:~#
I am running Lubuntu 12.04 on my laptop.
What do I need to do to be able to connect to the phone using adb and fastboot?
Thanks!
The "recovery mode" that you mentioned, is actually download mode and it's used to flash packages with Odin.
Use it to flash a custom recovery and then use that to flash a custom ROM. Format /system and /data as ext4 before flashing the ROM.
Sent from my LG G2 Mini using XDA Labs
First of all, as we all know, ZTE Blade V880 is an ancient phone. I did this just for fun.
My laptop is a 4th gen Intel platform (haswell), which has both EHCI and xHCI.
After plugging my Blade into the laptop, I found that fastboot cannot function. If it's plugged into the USB3.0 port, the device manager complained "code 10" (it was recognised as "Android Bootloader Interface" made by "Marshall London Device"), while it's plugged into the USB2.0 port, the error code was "code 43", with a message of "enumeration of BOS descriptor failed". (in this case it's just cataloged into abnormal USB device, lol)
After some googling (thanks to the code 43 actually!), I found that a registry hack of SkipBOSDescriptorQuery works. However, ironically, this fix only works on USB3.0 ports, which didn't throw "code 43" at all.
Steps:
1. Plug the phone into the USB3.0 port
2. Open the device manager, find out the hardware ID (vendor id and product id, aka VID and PID). For my Blade it was VID_18D1 PID_D00D REV_0100
3. Open regedit, locate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100 (see, it's [VID][PID][REV])
4. Create a DWORD value named "SkipBOSDescriptorQuery" and then change its value to 1
5. Done, just unplug and replug the USB cable once again, then it should work.
I'm having problems with a Chinese tablet that I believe to be a Mediatek TAB910 with a MTK6592 processor.
It started by having problems with the SIM slots which I put down to a faulty SIM card. I obtained another from the telco but that didn't solve the problem. I concluded that the problem was with the SIM slots or with the software so I did a factory reset.
That appears to have gone well EXCEPT that I cannot get past the "Enter Privacy Protection password" screen (PPP). Let me say at this stage that I have never used PINs on my SIM cards; in fact, if I put a SIM card in which has a PIN then the screen asks for and accepts the SIM PIN but still presents the PPP screen.
I have tried to connect to the tablet by USB in order to try SP FLASH, but that tool doesn't see the tablet at all.
I then tried sudo dmesg|grep usb to see if there was any recognition of the USB and got the following results:
[237820.461318] usb 1-2: new high-speed USB device number 22 using xhci_hcd
[237820.611762] usb 1-2: New USB device found, idVendor=0e8d, idProduct=2000, bcdDevice= 1.00
[237820.611773] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[237820.611779] usb 1-2: Product: MT65xx Preloader
[237820.611783] usb 1-2: Manufacturer: MediaTek
[237823.266112] usb 1-2: USB disconnect, device number 22
[237830.885144] usb 1-2: new high-speed USB device number 23 using xhci_hcd
[237831.034440] usb 1-2: New USB device found, idVendor=0e8d, idProduct=2002, bcdDevice=ff.ff
[237831.034451] usb 1-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[237831.034456] usb 1-2: Product: TAB910
[237831.034461] usb 1-2: Manufacturer: MediaTek
[237831.034465] usb 1-2: SerialNumber: 0123456789ABCDEF
[237831.038098] usb-storage 1-2:1.0: USB Mass Storage device detected
[237831.045186] scsi host2: usb-storage 1-2:1.0
[237831.471860] usb 1-2: USB disconnect, device number 23
Click to expand...
Click to collapse
It appears that the tablet is identifying itself, but immediately disconnecting again, hence no response from SP FLASH.
I can get the tablet to drop into two factory setting levels, one with English language instructions, the other with Chinese language instructions. Both of these appear to work as expected when I run through the menu items including, in the Chinese menu, "Eliminate eMMC".
I have also modified the udev files, but seemingly to no avail.
~$ cat /etc/udev/rules.d/80-persistent-usb.rules
SUBSYSTEM==”usb”, ACTION==”add”, ATTR{idVendor}==”0e8d”, ATTR{idProduct}==”2000“
SUBSYSTEM==”usb”, ACTION==”add”, ATTR{idVendor}==”0e8d”, ATTR{idProduct}==”2002“
~$ sudo service udev restart
Click to expand...
Click to collapse
My question is: Where do I go from here before I decide to bin this chablet.
TIA
For your reference.
https://visihow.com/Bypass_Privacy_Protection_Password_on_Android
James_Watson said:
For your reference.
https://visihow.com/Bypass_Privacy_Protection_Password_on_Android
Click to expand...
Click to collapse
Thanks for that but I have already been down that rabbit hole without success. My big problem is that the USB comes up but promptly disconnects again
Usually MTk preloader comport will disconnect if correct bootloader is not detected. So check you've got MTK6592 supported sp flashtool version and original firmware loaded. For privacy protection removal you need to format whole flash except bootloader and flash origin firmware then need to repair imei.
For some models you need to press and hold VOL+ or VOL- or both to get in to flash mode.