Nokia 7.1 Bricked - Advice?

Search This thread

weslowsk

Member
May 15, 2013
13
0
Regina
I had my Nokia 7.1 for about 2 years and now it won't charge or boot up. Plugging it in does nothing, nor does any button combinations for forced modes (i.e. holding vol up/down + power). It seems to be completely dead.
I read that the USB charging port on these devices can be faulty so I bought a new one and replaced it. Sadly, no change.
I plugged it into my Linux computer and lsusb detected it:
Code:
Bus 003 Device 009: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
But it doesn't charge it and it still won't turn on while plugged in.
Is there a chance that I can use ADB tools to connect/communicate with it and cause a reboot/flash? Or, is that just wishful thinking?
 
Jan 16, 2021
32
14
Great! What do you suggest?

Download the firmware for your phone here. Make sure to get the QFIL, not OST, format for firmware. Extract it and cd to the folder.

Then follow the tutorial here to build QDL.

In the folder there should be many files, including:
  • A .mbn file (possibly B2N-0-351F-devcfg.mbn?)
  • An XML file on how the image is to be assembled (B2N-1-351F-rawprogram0.xml)
  • An XML file on how the image is patched (B2N-1-351F-patch0.xml)
Make sure your device is in QDL/EDL mode (run lsusb). If it is, now run:

Code:
qdl/qdl --debug --include '<path to the firmware files>' '<path to the firmware files>/B2N-0-351F-devcfg.mbn' '<path to the firmware files>/B2N-1-351F-rawprogram0.xml' '<path to the firmware files>/B2N-1-351F-patch0.xml'

This may take a while to restore. Once finished, your device should exit and reboot. I am not responsible for any damage done, as I have only tested this with my Lenovo Tablet, but it should work on the majority of Qualcomm devices. Good luck!
 

weslowsk

Member
May 15, 2013
13
0
Regina
Download the firmware for your phone here. Make sure to get the QFIL, not OST, format for firmware. Extract it and cd to the folder.

Then follow the tutorial here to build QDL.

In the folder there should be many files, including:
  • A .mbn file (possibly B2N-0-351F-devcfg.mbn?)
  • An XML file on how the image is to be assembled (B2N-1-351F-rawprogram0.xml)
  • An XML file on how the image is patched (B2N-1-351F-patch0.xml)
Make sure your device is in QDL/EDL mode (run lsusb). If it is, now run:

Code:
qdl/qdl --debug --include '<path to the firmware files>' '<path to the firmware files>/B2N-0-351F-devcfg.mbn' '<path to the firmware files>/B2N-1-351F-rawprogram0.xml' '<path to the firmware files>/B2N-1-351F-patch0.xml'

This may take a while to restore. Once finished, your device should exit and reboot. I am not responsible for any damage done, as I have only tested this with my Lenovo Tablet, but it should work on the majority of Qualcomm devices. Good luck!

I followed the instructions, disabled the ModemManager service (because I read that might conflict), and ran qdl but I just got:
Code:
Waiting for EDL device
I waited several minutes but it didn't return. So, I killed that. I tried a bunch more times with the same result.
Then, I ran the command using sudo. That just returned immediately; no output.
I unplugged and plugged it back in to the computer while trying holding different physical buttons on the phone.
I tried the qdl command with sudo and got a slightly different response:
Code:
HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0
READ64 image: 13 offset: 0x0 length: 0x40
READ64 image: 13 offset: 0x40 length: 0xe0
END OF IMAGE image: 13 status: 40
received non-successful result
It exited very quickly. Anytime I try to run qdl as normal user or sudo I get the original behaviour again. I don't know what I did to get that slightly longer response.
Any other suggestions?
 

weslowsk

Member
May 15, 2013
13
0
Regina
After a bit more experimentation, it seems that if I hold the power button on the phone, I get more output.
Depending on when I hold the power button, I might get output like this:
Code:
Waiting for EDL device
/dev/bus/usb/003/024
HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0
READ64 image: 13 offset: 0x0 length: 0x40
READ64 image: 13 offset: 0x40 length: 0xe0
END OF IMAGE image: 13 status: 40
received non-successful result

Without sudo, I was able to get a whole string of the /dev/bus output lines as long as I held the power button. Every few seconds, it would spit out a couple more lines:

Code:
Waiting for EDL device
/dev/bus/usb/003/016
/dev/bus/usb/003/016
/dev/bus/usb/003/017
/dev/bus/usb/003/017
/dev/bus/usb/003/017
/dev/bus/usb/003/017
/dev/bus/usb/003/018
/dev/bus/usb/003/018
/dev/bus/usb/003/018
/dev/bus/usb/003/018
/dev/bus/usb/003/019
/dev/bus/usb/003/019
/dev/bus/usb/003/019
/dev/bus/usb/003/019
/dev/bus/usb/003/020
/dev/bus/usb/003/020
/dev/bus/usb/003/020
/dev/bus/usb/003/020
/dev/bus/usb/003/021
/dev/bus/usb/003/021
/dev/bus/usb/003/021
/dev/bus/usb/003/021
/dev/bus/usb/003/022
/dev/bus/usb/003/022
/dev/bus/usb/003/022
/dev/bus/usb/003/022
/dev/bus/usb/003/023
/dev/bus/usb/003/023
 

weslowsk

Member
May 15, 2013
13
0
Regina
Ah ha. When I hold the power button for about 5-10 seconds, I get a new device # for the phone, according to
Code:
lsusb
which would explain why I got those /dev/bus lines spitting out more the longer I held the power button. The device number would keep incrementing as I held the power button.
 
Jan 16, 2021
32
14
I followed the instructions, disabled the ModemManager service (because I read that might conflict), and ran qdl but I just got:
Code:
Waiting for EDL device
I waited several minutes but it didn't return. So, I killed that. I tried a bunch more times with the same result.
Then, I ran the command using sudo. That just returned immediately; no output.
I unplugged and plugged it back in to the computer while trying holding different physical buttons on the phone.
I tried the qdl command with sudo and got a slightly different response:
Code:
HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0
READ64 image: 13 offset: 0x0 length: 0x40
READ64 image: 13 offset: 0x40 length: 0xe0
END OF IMAGE image: 13 status: 40
received non-successful result
It exited very quickly. Anytime I try to run qdl as normal user or sudo I get the original behaviour again. I don't know what I did to get that slightly longer response.
Any other suggestions?

If that happens, then you'll need to take out the battery for a couple of minutes and put it back in again. I've heard of a bug where if a device is in EDL/QDL mode for too long, it will "time out". There's a guide for that here.
 

weslowsk

Member
May 15, 2013
13
0
Regina
If that happens, then you'll need to take out the battery for a couple of minutes and put it back in again. I've heard of a bug where if a device is in EDL/QDL mode for too long, it will "time out". There's a guide for that here.
Thanks. While I've got the battery out, is there a good guide for testing it? i.e. if I find it's dead or soon-to-be-dead, I'd want to replace it at that time.
 

weslowsk

Member
May 15, 2013
13
0
Regina
If that happens, then you'll need to take out the battery for a couple of minutes and put it back in again. I've heard of a bug where if a device is in EDL/QDL mode for too long, it will "time out". There's a guide for that here.



I haven't taken out the battery yet. I wanted to try a few more things and gather more diagnostic data.

This happens after the device hasn't been plugged into the computer for several minutes, then plugging the device into the computer, not holding any physical buttons, and waiting about 60 seconds:

Code:
Waiting for EDL device
/dev/bus/usb/003/012
HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0
READ64 image: 13 offset: 0x0 length: 0x40
READ64 image: 13 offset: 0x40 length: 0xe0
END OF IMAGE image: 13 status: 40
received non-successful result


If I unplug the device, don't wait several minutes, and then plug it in again, I instantly get this response:

Code:
Waiting for EDL device
/dev/bus/usb/003/014


Through trial and error, I discovered that I don't have to wait "several minutes" to plug it in again to get the "HELLO" response. Instead, while the device is unplugged, I can hold the power button for about 10 seconds and then wait a few more seconds. This seems to put it back into that original state (powered off?). Plugging it in again and then waiting the obligatory 60 seconds will yield the same result:


Code:
Waiting for EDL device
/dev/bus/usb/003/012
HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0
READ64 image: 13 offset: 0x0 length: 0x40
READ64 image: 13 offset: 0x40 length: 0xe0
END OF IMAGE image: 13 status: 40
received non-successful result


After reading some articles, I thought I would try some different qdl parameters. I changed B2N-0-415C-devcfg.mbn to B2N-0-415C-prog_emmc_ufs_firehose_Sdm660_ddr.elf.
I saw some examples out there where an .elf file was passed instead of the .mbn and I also saw some .mbn files passed that had filenames looked more like the .elf file I had (i.e. "prog", "firehose", etc.).
So, that's why I changed that.

Just to be clear, here's what my qdl command looks like now:

Code:
sudo /home/kevin/HDD1/git/android/Qualcomm/qdl/qdl --debug --include '/mnt/HDD1/temp/FIHSW_CTL-415C-0-00WW-B03_600WW_10_20200501.full.lzma2.786e65af1f0e0b8bb0077f8de8e2b3ed8190435e0f8c1b0031b7ec90abd5785c' '/mnt/HDD1/temp/FIHSW_CTL-415C-0-00WW-B03_600WW_10_20200501.full.lzma2.786e65af1f0e0b8bb0077f8de8e2b3ed8190435e0f8c1b0031b7ec90abd5785c/B2N-0-415C-prog_emmc_ufs_firehose_Sdm660_ddr.elf' '/mnt/HDD1/temp/FIHSW_CTL-415C-0-00WW-B03_600WW_10_20200501.full.lzma2.786e65af1f0e0b8bb0077f8de8e2b3ed8190435e0f8c1b0031b7ec90abd5785c/B2N-1-415C-rawprogram0.xml' '/mnt/HDD1/temp/FIHSW_CTL-415C-0-00WW-B03_600WW_10_20200501.full.lzma2.786e65af1f0e0b8bb0077f8de8e2b3ed8190435e0f8c1b0031b7ec90abd5785c/B2N-1-415C-patch0.xml'


I was surprised by the response I got when plugged in the device again and waited the obligatory 60 seconds:

Code:
Waiting for EDL device
/dev/bus/usb/003/019
HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0
READ64 image: 13 offset: 0x0 length: 0x40
READ64 image: 13 offset: 0x40 length: 0x2d8
READ64 image: 13 offset: 0x1000 length: 0x1000
READ64 image: 13 offset: 0x2000 length: 0xac8
READ64 image: 13 offset: 0x3000 length: 0x1000
READ64 image: 13 offset: 0x4000 length: 0x1000
READ64 image: 13 offset: 0x5000 length: 0x1000
READ64 image: 13 offset: 0x6000 length: 0x1000
READ64 image: 13 offset: 0x7000 length: 0x1000
READ64 image: 13 offset: 0x8000 length: 0x1000
READ64 image: 13 offset: 0x9000 length: 0x1000
READ64 image: 13 offset: 0xa000 length: 0x1000
READ64 image: 13 offset: 0xb000 length: 0x1000
READ64 image: 13 offset: 0xc000 length: 0x1000
READ64 image: 13 offset: 0xd000 length: 0x1000
READ64 image: 13 offset: 0xe000 length: 0x1000
READ64 image: 13 offset: 0xf000 length: 0x1000
READ64 image: 13 offset: 0x10000 length: 0x1000
READ64 image: 13 offset: 0x11000 length: 0x1000
READ64 image: 13 offset: 0x12000 length: 0x1000
READ64 image: 13 offset: 0x13000 length: 0x1000
READ64 image: 13 offset: 0x14000 length: 0x1000
READ64 image: 13 offset: 0x15000 length: 0x1000
READ64 image: 13 offset: 0x16000 length: 0x1000
READ64 image: 13 offset: 0x17000 length: 0x1000
READ64 image: 13 offset: 0x18000 length: 0x1000
READ64 image: 13 offset: 0x19000 length: 0x1000
READ64 image: 13 offset: 0x1a000 length: 0x1000
READ64 image: 13 offset: 0x1b000 length: 0x1000
READ64 image: 13 offset: 0x1c000 length: 0x1000
READ64 image: 13 offset: 0x1d000 length: 0x1000
READ64 image: 13 offset: 0x1e000 length: 0x1000
READ64 image: 13 offset: 0x1f000 length: 0x1000
READ64 image: 13 offset: 0x20000 length: 0x1000
READ64 image: 13 offset: 0x21000 length: 0x1000
READ64 image: 13 offset: 0x22000 length: 0x1000
READ64 image: 13 offset: 0x23000 length: 0x1000
READ64 image: 13 offset: 0x24000 length: 0x1000
READ64 image: 13 offset: 0x25000 length: 0x1000
READ64 image: 13 offset: 0x26000 length: 0x1000
READ64 image: 13 offset: 0x27000 length: 0x1000
READ64 image: 13 offset: 0x28000 length: 0x1000
READ64 image: 13 offset: 0x29000 length: 0x1000
READ64 image: 13 offset: 0x2a000 length: 0x1000
READ64 image: 13 offset: 0x2b000 length: 0x1000
READ64 image: 13 offset: 0x2c000 length: 0x1000
READ64 image: 13 offset: 0x2d000 length: 0x1000
READ64 image: 13 offset: 0x2e000 length: 0x1000
READ64 image: 13 offset: 0x2f000 length: 0x1000
READ64 image: 13 offset: 0x30000 length: 0x1000
READ64 image: 13 offset: 0x31000 length: 0x1000
READ64 image: 13 offset: 0x32000 length: 0x1000
READ64 image: 13 offset: 0x33000 length: 0x1000
READ64 image: 13 offset: 0x34000 length: 0x1000
READ64 image: 13 offset: 0x35000 length: 0x1000
READ64 image: 13 offset: 0x36000 length: 0x1000
READ64 image: 13 offset: 0x37000 length: 0x1000
READ64 image: 13 offset: 0x38000 length: 0x1000
READ64 image: 13 offset: 0x39000 length: 0x1000
READ64 image: 13 offset: 0x3a000 length: 0x1000
READ64 image: 13 offset: 0x3b000 length: 0x1000
READ64 image: 13 offset: 0x3c000 length: 0x1000
READ64 image: 13 offset: 0x3d000 length: 0x1000
READ64 image: 13 offset: 0x3e000 length: 0x1000
READ64 image: 13 offset: 0x3f000 length: 0x1000
READ64 image: 13 offset: 0x40000 length: 0x1000
READ64 image: 13 offset: 0x41000 length: 0x1000
READ64 image: 13 offset: 0x42000 length: 0x1000
READ64 image: 13 offset: 0x43000 length: 0x1000
READ64 image: 13 offset: 0x44000 length: 0x1000
READ64 image: 13 offset: 0x45000 length: 0x1000
READ64 image: 13 offset: 0x46000 length: 0x1000
READ64 image: 13 offset: 0x47000 length: 0x1000
READ64 image: 13 offset: 0x48000 length: 0x1000
READ64 image: 13 offset: 0x49000 length: 0x1000
READ64 image: 13 offset: 0x4a000 length: 0x1000
READ64 image: 13 offset: 0x4b000 length: 0x1000
READ64 image: 13 offset: 0x4c000 length: 0x1000
READ64 image: 13 offset: 0x4d000 length: 0x1000
READ64 image: 13 offset: 0x4e000 length: 0x1000
READ64 image: 13 offset: 0x4f000 length: 0x1000
READ64 image: 13 offset: 0x50000 length: 0x1000
READ64 image: 13 offset: 0x51000 length: 0x1000
READ64 image: 13 offset: 0x52000 length: 0x1000
READ64 image: 13 offset: 0x53000 length: 0x1000
READ64 image: 13 offset: 0x54000 length: 0x1000
READ64 image: 13 offset: 0x55000 length: 0x1000
READ64 image: 13 offset: 0x56000 length: 0x1000
READ64 image: 13 offset: 0x57000 length: 0x1000
READ64 image: 13 offset: 0x58000 length: 0x1000
READ64 image: 13 offset: 0x59000 length: 0xa90
READ64 image: 13 offset: 0x59a90 length: 0x1000
READ64 image: 13 offset: 0x5aa90 length: 0x1000
READ64 image: 13 offset: 0x5ba90 length: 0x1000
READ64 image: 13 offset: 0x5ca90 length: 0x1000
READ64 image: 13 offset: 0x5da90 length: 0x1000
READ64 image: 13 offset: 0x5ea90 length: 0x1000
READ64 image: 13 offset: 0x5fa90 length: 0x1000
READ64 image: 13 offset: 0x60a90 length: 0x1000
READ64 image: 13 offset: 0x61a90 length: 0xfe8
READ64 image: 13 offset: 0x62a80 length: 0x1000
READ64 image: 13 offset: 0x63a80 length: 0x1000
READ64 image: 13 offset: 0x64a80 length: 0x1000
READ64 image: 13 offset: 0x65a80 length: 0x1000
READ64 image: 13 offset: 0x66a80 length: 0x1000
READ64 image: 13 offset: 0x67a80 length: 0x1000
READ64 image: 13 offset: 0x68a80 length: 0x1000
READ64 image: 13 offset: 0x69a80 length: 0x1000
READ64 image: 13 offset: 0x6aa80 length: 0x1000
READ64 image: 13 offset: 0x6ba80 length: 0x908
READ64 image: 13 offset: 0x6c390 length: 0x1000
READ64 image: 13 offset: 0x6d390 length: 0xe7c
READ64 image: 13 offset: 0x6e210 length: 0x1000
READ64 image: 13 offset: 0x6f210 length: 0x1000
READ64 image: 13 offset: 0x70210 length: 0x1000
READ64 image: 13 offset: 0x71210 length: 0x1000
READ64 image: 13 offset: 0x72210 length: 0x1000
READ64 image: 13 offset: 0x73210 length: 0x1000
READ64 image: 13 offset: 0x74210 length: 0x1000
READ64 image: 13 offset: 0x75210 length: 0x1000
READ64 image: 13 offset: 0x76210 length: 0x1000
READ64 image: 13 offset: 0x77210 length: 0x1000
READ64 image: 13 offset: 0x78210 length: 0x1000
READ64 image: 13 offset: 0x79210 length: 0x1000
READ64 image: 13 offset: 0x7a210 length: 0x1000
READ64 image: 13 offset: 0x7b210 length: 0x1000
READ64 image: 13 offset: 0x7c210 length: 0x1000
READ64 image: 13 offset: 0x7d210 length: 0x1000
READ64 image: 13 offset: 0x7e210 length: 0x1000
READ64 image: 13 offset: 0x7f210 length: 0x1000
READ64 image: 13 offset: 0x80210 length: 0x1000
READ64 image: 13 offset: 0x81210 length: 0x1000
READ64 image: 13 offset: 0x82210 length: 0x1000
READ64 image: 13 offset: 0x83210 length: 0x1000
READ64 image: 13 offset: 0x84210 length: 0x1000
READ64 image: 13 offset: 0x85210 length: 0x1000
READ64 image: 13 offset: 0x86210 length: 0x8e8
READ64 image: 13 offset: 0x86b00 length: 0x1000
READ64 image: 13 offset: 0x87b00 length: 0x1000
READ64 image: 13 offset: 0x88b00 length: 0x1000
READ64 image: 13 offset: 0x89b00 length: 0x1000
READ64 image: 13 offset: 0x8ab00 length: 0x1000
READ64 image: 13 offset: 0x8bb00 length: 0x1000
READ64 image: 13 offset: 0x8cb00 length: 0x1000
READ64 image: 13 offset: 0x8db00 length: 0x1000
READ64 image: 13 offset: 0x8eb00 length: 0x1000
READ64 image: 13 offset: 0x8fb00 length: 0x1000
READ64 image: 13 offset: 0x90b00 length: 0x1000
READ64 image: 13 offset: 0x91b00 length: 0x1000
READ64 image: 13 offset: 0x92b00 length: 0x1000
READ64 image: 13 offset: 0x93b00 length: 0x1000
READ64 image: 13 offset: 0x94b00 length: 0x1000
READ64 image: 13 offset: 0x95b00 length: 0x1000
READ64 image: 13 offset: 0x96b00 length: 0x1000
READ64 image: 13 offset: 0x97b00 length: 0x1000
READ64 image: 13 offset: 0x98b00 length: 0x1000
READ64 image: 13 offset: 0x99b00 length: 0x180
END OF IMAGE image: 13 status: 0
DONE status: 1
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Binary build date: Apr 23 2020 @ 21:40:34"/>
</data>
LOG: Binary build date: Apr 23 2020 @ 21:40:34
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Chip serial num: 0 (0x0)"/>
</data>
LOG: Chip serial num: 0 (0x0)
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase "/>
</data>
LOG: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase
qdl: failed to read: Connection timed out
FIREHOSE WRITE: <?xml version="1.0"?>
<data><configure MemoryName="ufs" MaxPayloadSizeToTargetInBytes="1048576" verbose="0" ZLPAwareHost="1" SkipStorageInit="0"/></data>

FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Calling usb_al_bulk_set_zlp_mode(TRUE) since ZlpAwareHost='1'"/>
</data>
LOG: Calling usb_al_bulk_set_zlp_mode(TRUE) since ZlpAwareHost='1'
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="ACK" MinVersionSupported="1" MemoryName="UFS" MaxPayloadSizeFromTargetInBytes="4096" MaxPayloadSizeToTargetInBytes="1048576" MaxPayloadSizeToTargetInBytesSupported="1048576" MaxXMLSizeInBytes="4096" Version="1" TargetName="MSM8996" DateTime="Apr 23 2020 - 21:40:34" />
</data>
[CONFIGURE] max payload size: 1048576
FIREHOSE WRITE: <?xml version="1.0"?>
<data><program SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="5010" physical_partition_number="0" start_sector="585728" filename="B2N-0-415C-xbl.elf"/></data>

FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to initialize (open whole lun) UFS Device slot 0 partition 0"/>
</data>
LOG: ERROR: Failed to initialize (open whole lun) UFS Device slot 0 partition 0
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to open the device 3 slot 0 partition 0"/>
</data>
LOG: ERROR: Failed to open the device 3 slot 0 partition 0
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Device type 3, slot 0, partition 0, error 0"/>
</data>
LOG: INFO: Device type 3, slot 0, partition 0, error 0
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="WARN: Get Info failed to open 3 slot 0, partition 0, error 0"/>
</data>
LOG: WARN: Get Info failed to open 3 slot 0, partition 0, error 0
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="storage_device_get_num_partition_sectors FAILED!"/>
</data>
LOG: storage_device_get_num_partition_sectors FAILED!
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="parseSectorValue could not handle start_sector value"/>
</data>
LOG: parseSectorValue could not handle start_sector value
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" />
</data>
[PROGRAM] failed to setup programming

So, way more output, but still ends in failure.


Using sudo seems to be necessary because when I don't use it, I get responses like:

Code:
Waiting for EDL device
/dev/bus/usb/003/020


As opposed to the much longer responses when I use sudo.

Based on all this, I don't think it's necessary for me to disconnect the battery, as earlier suggested because I just changed a qdl parameter and that seemed to make a noticeable difference. Or, do I still need to disconnect the battery?
Any other thoughts? What else should I try? Different .mbn/.elf files? Is this looking like a hardware failure? How would I know?
 
Jan 16, 2021
32
14
Based on all this, I don't think it's necessary for me to disconnect the battery, as earlier suggested because I just changed a qdl parameter and that seemed to make a noticeable difference. Or, do I still need to disconnect the battery?
Any other thoughts? What else should I try? Different .mbn/.elf files? Is this looking like a hardware failure? How would I know?

You need to disconnect the battery, yes. I had a similar thing on my Lenovo Tab 4 and had to disconnect the battery.
 

weslowsk

Member
May 15, 2013
13
0
Regina
You need to disconnect the battery, yes. I had a similar thing on my Lenovo Tab 4 and had to disconnect the battery.
I disconnected/re-connected the battery and tried again. I got exactly the same behaviour as before. How long is this EDL timeout? It was only a few minutes between reconnecting the battery and when I connected it to my computer and ran the qdl commands. I assume that's fine?
I put the battery leads on my multimeter and it showed 2.76 V. Assuming that the battery isn't charged up fully, I think this is okay; I don't think the battery is the problem.

Any other ideas?
 
Jan 16, 2021
32
14
I disconnected/re-connected the battery and tried again. I got exactly the same behaviour as before. How long is this EDL timeout? It was only a few minutes between reconnecting the battery and when I connected it to my computer and ran the qdl commands. I assume that's fine?
I put the battery leads on my multimeter and it showed 2.76 V. Assuming that the battery isn't charged up fully, I think this is okay; I don't think the battery is the problem.

Any other ideas?

Did you take out the battery and keep it out for at least ten minutes? If you didn't, try that. Also make sure your device is disconnected from any power supply while the battery is unplugged.
 

weslowsk

Member
May 15, 2013
13
0
Regina
Did you take out the battery and keep it out for at least ten minutes? If you didn't, try that. Also make sure your device is disconnected from any power supply while the battery is unplugged.

I didn't physically take out the battery. I disconnected it from the main board and left it disconnected for about 10 minutes while I used my multimeter to test the voltage, etc. I didn't time it exactly. There are 2 other connections to the main board that I didn't disconnect (because I don't think they're related to the battery) and the 3 gummy strips that I didn't remove (the glue holding the battery down). They're all shown in the video but I didn't think they were necessary to disconnect/remove because I wasn't actually replacing the battery.

The device was not connected to any power supply when the battery was disconnected.
 

weslowsk

Member
May 15, 2013
13
0
Regina
attached image of how I disconnected the battery
IMG_20210123_121758.jpg
 

weslowsk

Member
May 15, 2013
13
0
Regina
Did you take out the battery and keep it out for at least ten minutes? If you didn't, try that. Also make sure your device is disconnected from any power supply while the battery is unplugged.
I disconnected the battery again and timed it. It was disconnected for 45 minutes. I re-tested and I got the same output from qdl as before.
 

mortemonline

Member
May 5, 2019
5
0
kerman
After a bit more experimentation, it seems that if I hold the power button on the phone, I get more output.
Depending on when I hold the power button, I might get output like this:
Code:
Waiting for EDL device
/dev/bus/usb/003/024
HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0
READ64 image: 13 offset: 0x0 length: 0x40
READ64 image: 13 offset: 0x40 length: 0xe0
END OF IMAGE image: 13 status: 40
received non-successful result

Without sudo, I was able to get a whole string of the /dev/bus output lines as long as I held the power button. Every few seconds, it would spit out a couple more lines:

Code:
Waiting for EDL device
/dev/bus/usb/003/016
/dev/bus/usb/003/016
/dev/bus/usb/003/017
/dev/bus/usb/003/017
/dev/bus/usb/003/017
/dev/bus/usb/003/017
/dev/bus/usb/003/018
/dev/bus/usb/003/018
/dev/bus/usb/003/018
/dev/bus/usb/003/018
/dev/bus/usb/003/019
/dev/bus/usb/003/019
/dev/bus/usb/003/019
/dev/bus/usb/003/019
/dev/bus/usb/003/020
/dev/bus/usb/003/020
/dev/bus/usb/003/020
/dev/bus/usb/003/020
/dev/bus/usb/003/021
/dev/bus/usb/003/021
/dev/bus/usb/003/021
/dev/bus/usb/003/021
/dev/bus/usb/003/022
/dev/bus/usb/003/022
/dev/bus/usb/003/022
/dev/bus/usb/003/022
/dev/bus/usb/003/023
/dev/bus/usb/003/023
hi man @weslowsk
i had the exact same problem with my Nokia 3.2
I explored every inch of internet and no luck
so I solved it like this
1- install qdl from https://github.com/96boards/documentation/blob/master/consumer/guides/qdl.md
2- cd to your firmware folder
3- change names of this command and path to qdl folder and run this command (this ss what i typed) : sudo /home/mortem/qdl/qdl prog_emmc_firehose_8937_ddr.mbn rawprogram0.xml patch0.xml
4- unplug the battery
5- short circuit the help point - connect usb cable - release the help point OR use an edl cable
and that should work for you too



(what God prepers for us, is always far better than what we wish for)
 

mortemonline

Member
May 5, 2019
5
0
kerman
and if you can see something like this, tampering with power button so you're on:
HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0
i just unpluged damn battery
 

Attachments

  • Screenshot-1.png
    Screenshot-1.png
    143.8 KB · Views: 8
  • Screenshot.png
    Screenshot.png
    133.5 KB · Views: 8

weslowsk

Member
May 15, 2013
13
0
Regina
interesting ... thanks @mortemonline

I'm going to walk through the steps you did and compare them to what I did or what I will do and see if I've got things straight...

1) Install QDL
- I've already done this.
2) CD to firmware folder
- No problem.
3) Run QDL
- From my earlier post
I think I have the syntax right and it's similar to what you have:


sudo /home/kevin/HDD1/git/android/Qualcomm/qdl/qdl --debug --include '/mnt/HDD1/temp/FIHSW_CTL-415C-0-00WW-B03_600WW_10_20200501.full.lzma2.786e65af1f0e0b8bb0077f8de8e2b3ed8190435e0f8c1b0031b7ec90abd5785c' '/mnt/HDD1/temp/FIHSW_CTL-415C-0-00WW-B03_600WW_10_20200501.full.lzma2.786e65af1f0e0b8bb0077f8de8e2b3ed8190435e0f8c1b0031b7ec90abd5785c/B2N-0-415C-prog_emmc_ufs_firehose_Sdm660_ddr.elf' '/mnt/HDD1/temp/FIHSW_CTL-415C-0-00WW-B03_600WW_10_20200501.full.lzma2.786e65af1f0e0b8bb0077f8de8e2b3ed8190435e0f8c1b0031b7ec90abd5785c/B2N-1-415C-rawprogram0.xml' '/mnt/HDD1/temp/FIHSW_CTL-415C-0-00WW-B03_600WW_10_20200501.full.lzma2.786e65af1f0e0b8bb0077f8de8e2b3ed8190435e0f8c1b0031b7ec90abd5785c/B2N-1-415C-patch0.xml'


The first parameter is the prog/emmc/firehose/ddr file. As I noted in my post, I don't have a .mbn file that looks like that in my firmware folder and the closest one is a .elf file. So, that's why I have that. Or, should I be reverting to the original .mbn file I tried that didn't give me much response earlier?
I also have the rawprogram and patch xml files as the second and third parameters.

So, I assume I run it at this point? You didn't say so but I assume I need to have the phone plugged into the computer via the USB cable, right? And the battery is connected at this point?

4) Unplug battery
- Ok, I can do this again. It's a hassle but if it's necessary, no problem.
- So, I have to unplug the battery while it's connected to the computer? That doesn't seem right, easy, or safe. Please advise.


5) Short circuit / USB cable
- I don't have an edl cable.
- So, at this point the battery is unplugged, as indicated in the previous step.
- I also assume it's not connected to the computer at this point. Please confirm.
- Short circuit. I need some guidance here ... I've never done this before. The red circle on your post/image https://forum.xda-developers.com/t/nokia-7-1-bricked-advice.4221393/post-84888087
is a square metal contact point. What do I do to it?
I found a conflicting article about the test point for a Nokia 7.1, though:
The arrows in that diagram show it's the third and fourth circle metal contact points way to the left of the square metal contact point you're referring to in your diagram. Which is it?
Do I just touch both points simultaneously with a pair of tweezers or 2 ends of a paper clip or something like that?
Then, I connect the phone to the computer via a USB cable? Do I do that while I'm doing the short circuiting and then stop short circuiting after the USB connection is made?

Sorry, but I'm not quite following all the advice/steps so far...I'll need some more handholding.
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone