Nokia 7.1 Bricked - Advice? - Nokia 7.1 Questions & Answers
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?
Do you have a computer running Linux? If so, I might be able to help. I had the same issue with my Lenovo tablet and fixed it.
ChasTechProjects said:
Do you have a computer running Linux? If so, I might be able to help. I had the same issue with my Lenovo tablet and fixed it.
Click to expand...
Click to collapse
Great! What do you suggest?
weslowsk said:
Great! What do you suggest?
Click to expand...
Click to collapse
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!
ChasTechProjects said:
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!
Click to expand...
Click to collapse
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?
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
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.
weslowsk said:
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?
Click to expand...
Click to collapse
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.
ChasTechProjects said:
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.
Click to expand...
Click to collapse
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.
ChasTechProjects said:
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.
Click to expand...
Click to collapse
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?
weslowsk said:
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?
Click to expand...
Click to collapse
You need to disconnect the battery, yes. I had a similar thing on my Lenovo Tab 4 and had to disconnect the battery.
ChasTechProjects said:
You need to disconnect the battery, yes. I had a similar thing on my Lenovo Tab 4 and had to disconnect the battery.
Click to expand...
Click to collapse
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?
weslowsk said:
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?
Click to expand...
Click to collapse
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.
ChasTechProjects said:
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.
Click to expand...
Click to collapse
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.
attached image of how I disconnected the battery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ChasTechProjects said:
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.
Click to expand...
Click to collapse
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.
weslowsk said:
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
Click to expand...
Click to collapse
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)
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
mortemonline said:
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
Click to expand...
Click to collapse
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
Nokia 7.1 Bricked - Advice?
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...
forum.xda-developers.com
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:
Nokia 7.1 Test Point Reboot to 9008 EDL Mod - ROM-Provider
step by step guide to reboot Nokia 7.1 to 9008 edl mod, to enable edl mod you have to do test point which require additional device disassemble knowledge
romprovider.com
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.
Related
Error ,What is the problem ?
USB>task 32 Level = 0 USB>lnbs spl-1.04.nb 50020000 :F=spl-1.04.nb :A=50020000 :O=00000000 :L=FFFFFFFF start NB image downloadSH Load ADDR: 50020000 Length: 40000 **ERROR: NO header matched Cert Key Error USB> Thanks
jimmy69 said: USB>task 32 Level = 0 USB>lnbs spl-1.04.nb 50020000 :F=spl-1.04.nb :A=50020000 :O=00000000 :L=FFFFFFFF start NB image downloadSH Load ADDR: 50020000 Length: 40000 **ERROR: NO header matched Cert Key Error USB> Thanks Click to expand... Click to collapse Do not use lnbs-command, use lnb instead. USB>lnb spl-1.04.nb 50020000 this will work!
An anohter error! task 32 Level = 0 USB>lnb spl-1.04.nb 50020000 :F=spl-1.04.nb :A=50020000 :O=00000000 :L=FFFFFFFF start NB image downloadSH Load ADDR: 50020000 Length: 40000 **Code entry point at 0x50040000 USB>
No, it's Ok, sorry
jimmy69 said: task 32 Level = 0 USB>lnb spl-1.04.nb 50020000 :F=spl-1.04.nb :A=50020000 :O=00000000 :L=FFFFFFFF start NB image downloadSH Load ADDR: 50020000 Length: 40000 **Code entry point at 0x50040000 USB> Click to expand... Click to collapse Why? All works fine. Check your Bootloader Screen. Press Buttons: Ok + Power + WirelessManager hold it and soft reset with styles. You should see IPL 1.01 SPL 1.01MFG
In this moment: IPL-1.00 HERM200 SPL-1.04 but not its possible to change radio to 1.27.000 Error invalid 114
try it once again! EDIT: You should see IPL 1.01 SPL 1.04 When flashing 1.01 MFG You should see IPL 1.01 SPL 1.01MFG
[Q] heimdall & SHW-M440S ?
I'm trying to flash an SHW-M440S with the KIES_HOME_M440SKSALG2_M440SSKTALEE ROM using heimdall. heimdall seems to detect the phone OK, but when trying to flash, I get the following: Code: $ sudo heimdall flash --normal-boot boot.img --cache cache.img --hidden hidden.img --modem modem.bin --recovery recovery.img --system system.img --verbose --stdout-errors [sudo] password for akos: Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna This software is provided free of charge. Copying and redistribution is encouraged. If you appreciate this software and you would like to support future development please consider donating: Initialising connection... Detecting device... Manufacturer: "SAMSUNG" Product: "Gadget Serial" length: 18 device class: 2 S/N: 0 VID:PID: 04E8:685D bcdDevice: 021B iMan:iProd:iSer: 1:2:0 nb confs: 1 interface[0].altsetting[0]: num endpoints = 1 Class.SubClass.Protocol: 02.02.01 endpoint[0].address: 83 max packet size: 0010 polling interval: 09 interface[1].altsetting[0]: num endpoints = 2 Class.SubClass.Protocol: 0A.00.00 endpoint[0].address: 81 max packet size: 0200 polling interval: 00 endpoint[1].address: 02 max packet size: 0200 polling interval: 00 Claiming interface... Attempt failed. Detaching driver... Claiming interface again... Setting up interface... Checking if protocol is initialised... Protocol is not initialised. Initialising protocol... Handshaking with Loke... Beginning session... Session begun with device of type: 131072 Downloading device's PIT file... PIT file download sucessful ERROR: Partition corresponding to -modem argument could not be located when printing the partitioning, the modem part is stored in a partition named radio: Code: --- Entry #10 --- Unused: No Partition Type: 2 (EXT4) Partition Identifier: 7 Partition Flags: 5 (R) Unknown 1: 1 Partition Block Size: 114688 Partition Block Count: 65536 Unknown 2: 0 Unknown 3: 0 Partition Name: RADIO Filename: modem.bin I wonder what the solution is - is there a way to tell heimdall to use the above partition instead? Akos
Please use the Q&A Forum for questions & Read the Forum Rules Ref Posting Thanks ✟ Moving to Q&A
error while trying to install TWRP
I am trying (for the first time ever) to install LineageOS on my S9+. I am using a Windows 10 laptop. I have tried installing the correct driver using Zadiag, I have found two occurrences of Gadget Serial. Anyway heimdall is erroring out with: C:\Users\codru\Downloads\Heimdall Suite>heimdall print-pit --verbose Heimdall v1.4.0 Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna <link removed> This software is provided free of charge. Copying and redistribution is encouraged. If you appreciate this software and you would like to support future development please consider donating: <link removed> Initialising connection... Detecting device... Manufacturer: "SAMSUNG" Product: "Gadget Serial" length: 18 device class: 2 S/N: 0 VIDID: 04E8:685D bcdDevice: 021B iMan:iProd:iSer: 1:2:0 nb confs: 1 interface[0].altsetting[0]: num endpoints = 1 Class.SubClass.Protocol: 02.02.01 endpoint[0].address: 83 max packet size: 0010 polling interval: 09 interface[1].altsetting[0]: num endpoints = 2 Class.SubClass.Protocol: 0A.00.00 endpoint[0].address: 81 max packet size: 0200 polling interval: 00 endpoint[1].address: 02 max packet size: 0200 polling interval: 00 Claiming interface... Setting up interface... Initialising protocol... WARNING: Control transfer #2 failed. Result: -7 WARNING: Control transfer #5 failed. Result: -7 WARNING: Control transfer #6 failed. Result: -9 ERROR: Failed to send data: "ODIN" Releasing device interface... C:\Users\codru\Downloads\Heimdall Suite>
Likewise using latest Heimdal 1.4.2 Code: Heimdall v1.4.2 Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna http://www.glassechidna.com.au/ This software is provided free of charge. Copying and redistribution is encouraged. If you appreciate this software and you would like to support future development please consider donating: http://www.glassechidna.com.au/donate/ Initialising connection... Detecting device... Manufacturer: "SAMSUNG" Product: "Gadget Serial" length: 18 device class: 2 S/N: 0 VID:PID: 04E8:685D bcdDevice: 021B iMan:iProd:iSer: 1:2:0 nb confs: 1 interface[0].altsetting[0]: num endpoints = 1 Class.SubClass.Protocol: 02.02.01 endpoint[0].address: 83 max packet size: 0010 polling interval: 09 interface[1].altsetting[0]: num endpoints = 2 Class.SubClass.Protocol: 0A.00.00 endpoint[0].address: 81 max packet size: 0200 polling interval: 00 endpoint[1].address: 02 max packet size: 0200 polling interval: 00 Claiming interface... Setting up interface... Initialising protocol... ERROR: libusb error -7 whilst sending bulk transfer. Retrying... ERROR: libusb error -7 whilst sending bulk transfer. Retrying... ERROR: libusb error -7 whilst sending bulk transfer. Retrying... ERROR: libusb error -7 whilst sending bulk transfer. Retrying... ERROR: libusb error -7 whilst sending bulk transfer. Retrying... ERROR: libusb error -7 whilst sending bulk transfer. ERROR: Failed to send handshake!ERROR: Failed to receive handshake response. Result: -7 ERROR: Protocol initialisation failed! Releasing device interface...
eduuk said: Likewise using latest Heimdal 1.4.2 Code: Heimdall v1.4.2 Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna http://www.glassechidna.com.au/ This software is provided free of charge. Copying and redistribution is encouraged. If you appreciate this software and you would like to support future development please consider donating: http://www.glassechidna.com.au/donate/ Initialising connection... Detecting device... Manufacturer: "SAMSUNG" Product: "Gadget Serial" length: 18 device class: 2 S/N: 0 VID:PID: 04E8:685D bcdDevice: 021B iMan:iProd:iSer: 1:2:0 nb confs: 1 interface[0].altsetting[0]: num endpoints = 1 Class.SubClass.Protocol: 02.02.01 endpoint[0].address: 83 max packet size: 0010 polling interval: 09 interface[1].altsetting[0]: num endpoints = 2 Class.SubClass.Protocol: 0A.00.00 endpoint[0].address: 81 max packet size: 0200 polling interval: 00 endpoint[1].address: 02 max packet size: 0200 polling interval: 00 Claiming interface... Setting up interface... Initialising protocol... ERROR: libusb error -7 whilst sending bulk transfer. Retrying... ERROR: libusb error -7 whilst sending bulk transfer. Retrying... ERROR: libusb error -7 whilst sending bulk transfer. Retrying... ERROR: libusb error -7 whilst sending bulk transfer. Retrying... ERROR: libusb error -7 whilst sending bulk transfer. Retrying... ERROR: libusb error -7 whilst sending bulk transfer. ERROR: Failed to send handshake!ERROR: Failed to receive handshake response. Result: -7 ERROR: Protocol initialisation failed! Releasing device interface... Click to expand... Click to collapse Heimdall does not work any more. It has not for a while. You must use odin.
[GUIDE] unbrick and flash Official ROM in EDL on linux
Introduction Hey guys! In my journey to completely go from windows to linux I was trying to see if there was a qfil alternative for linux, seeing that the program barely works on wine nor on a WIndows VM, so after a lot of digging i found an open source alternative to that, so today I'm going to show how you could flash any rom using qdl on linux (in my case I have a lenovo z5 pro gt so the guide will help you specifically with that) You need some things before we start: Your rom file, which you can get from lolinet A few dependencies, which you can install with Code: sudo apt install fastboot libxml2-dev libudev-dev git build-essentials make QDL binaries, downloadable via the command Code: git clone https://git.linaro.org/landing-teams/working/qualcomm/qdl.git Preparing files and Building QDL Once you got all the files you need to first extract the files stored on the *.zip of the rom you downloaded on a folder (for simplicity's sake you should call the folder something easy and sort such as z5pro). You should now look for a few files on the newly unzipped folder, especially for patch0.xml rawprogram_unparse0.xml, prog_firehose_ddr.elf (could have also a .mbn file extension, it's the same) Some Linux distributions come with ModemManager, a tool for configuring Mobile Broadband. You should stop this service because it interferes with the process Code: sudo systemctl stop ModemManager After that open a terminal and cd to the qdl folder that you downloaded with git and run make. If everything went to plan you should now have a qdl file. Test if it works by just typing on the terminal "./qdl" At this point you are nearly done! start building your command without pressing enter. it should have this scruture: Code: ./qdl --debug --storage ufs --include /path/to/z5pro /path/to/prog_firehose_ddr.elf /path/to/rawprogram0_unparse0.xml /path/to/patch0.xml Before pressing enter you should send your device in EDL mode. You can do this in a variety of ways: From fastboot Code: fastboot reboot edl By pressing both vol up and vol down and connecting the phone to the computer Press send on the terminal to start the process. Beware, you should do this as quickly as you can, otherwise it could just error you out Wait at least 10 minutes for the process to complete and congratulations, you should have a working rom installed on your phone! Thanks a lot to 96boards.org for telling me the necessary dependencies to run the program, it really helped me a lot on the process. If my guide helped you leaving a thanks would be greatly appreciated!
hi, i'm with issues here... the device - xiaomi redmi note 5A (ugg) - is dead. i'm managed for put it in edl mode, just blink the led, and this is what i receive in terminal: $ ./qdl --debug --storage ufs --include /home/tuga/ugg_global/images/ /home/tuga/ugg_global/images/prog_emmc_firehose_8937_ddr.mbn /home/tuga/ugg_global/images/rawprogram0.xml /home/tuga/ugg_global/images/patch0.xml HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0 READ image: 13 offset: 0x0 length: 0x34 READ image: 13 offset: 0x34 length: 0x120 READ image: 13 offset: 0x1000 length: 0x1000 READ image: 13 offset: 0x2000 length: 0xa48 and just it, no error messages, nothing. the system is MX-linux 19, debian like. thanks in advance and sorry for my poor english.
I have the exact same output issue as anton above. Except...my command is sudo qdl <prog.mbn> <rawprogram.xml> <patch.xml> from the extracted firmware directory. Alcatel tru metropcs 5065n cannot boot. cannot adb. fastboot is recognized at boot logo but doesnt accept commands. edl mode (vol up+vol down black screen) qdl mode (vol up+vol down white screen) cant flash either one. at least qdl gets recognized in mAid with op's commands i get this error: I/O warning: failed to load entity "ufs" [PATCH] failed to parse ufs qdl: failed to detect file type of ufs. maybe ufs is wrong for this phone. but ill keep a look if anton above gets a solution.
Arch users can install it trough the AUR: https://aur.archlinux.org/packages/qdl/
Please keep in mind when using QDL tool on Linux, be sure to remove ModemManager
U can try the following:
Bash:
sudo apt remove --purge modemmanager
The command I use for flashing is (Run after cd into the folder containing the files)
Bash:
qdl --storage ufs --include . prog_firehose_ddr.elf rawprogram_unsparse0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml
Be sure to know what is your storage type before hand. I think the possible values are: emmc, ufs etc.
Also, try to verify that
Bash:
lsusb
lists a "QDLoader 9008" device
The last thing I can think of is you can use --debug flag to see what's going on. Like:
Bash:
qdl --debug --storage ufs ...
I'm using this project: QDL Github
You need to git clone the project, the cd into it, and run make command. If make fails, then it's usually just a few missing libraries. You can easily find on Google, which packages you need to install to get it to compile.
Once it is compiled, you will get a qdl file.
Usually I have a ~/bin folder in my Home Dir like /home/sam/bin
In my bashrc I have added lines
Code:
PATH="${HOME}/bin:$PATH"
export PATH;
# You can add any number of directories to Path. I also have a /home/sam/scripts folder where I place my scripts
# Next you can do
cd ~/bin
# ln -sf (forced symlink) source dest
ln -sf ${HOME}/qdl/qdl qdl
# To create a symlink from git cloned folder's generated qdl executable into ${HOME}/bin
Then you can run qdl from anywhere
anton vier said: hi, i'm with issues here... the device - xiaomi redmi note 5A (ugg) - is dead. i'm managed for put it in edl mode, just blink the led, and this is what i receive in terminal: $ ./qdl --debug --storage ufs --include /home/tuga/ugg_global/images/ /home/tuga/ugg_global/images/prog_emmc_firehose_8937_ddr.mbn /home/tuga/ugg_global/images/rawprogram0.xml /home/tuga/ugg_global/images/patch0.xml HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0 READ image: 13 offset: 0x0 length: 0x34 READ image: 13 offset: 0x34 length: 0x120 READ image: 13 offset: 0x1000 length: 0x1000 READ image: 13 offset: 0x2000 length: 0xa48 and just it, no error messages, nothing. the system is MX-linux 19, debian like. thanks in advance and sorry for my poor english. Click to expand... Click to collapse Sure you have solved by now but for others that will look at this in future, you have to select correct file system for storage. ufs or emmc makes a difference in command, I had to use emmc as per firehose loader.
Hello, Firstly, thank you for your guide, it is very clear. My issue is that the phone is still not booting up after these steps. I believe I managed to correctly flash my bricked phone, here is the log : Code: sudo ./qdl/qdl --storage emmc --include /dev/ttyUSB0 prog_emmc_firehose_8937_ddr.mbn rawprogram_unsparse_8937_tw_no_fsg.xml patch0_8937.xml Waiting for EDL device HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0 READ image: 13 offset: 0x0 length: 0x34 READ image: 13 offset: 0x34 length: 0x120 READ image: 13 offset: 0x1000 length: 0x1000 READ image: 13 offset: 0x2000 length: 0xa48 READ image: 13 offset: 0x60ef8 length: 0x1000 READ image: 13 offset: 0x61ef8 length: 0x1000 READ image: 13 offset: 0x62ef8 length: 0x87c READ image: 13 offset: 0x63774 length: 0xb28 READ image: 13 offset: 0x3000 length: 0x1000 READ image: 13 offset: 0x4000 length: 0x1000 READ image: 13 offset: 0x5000 length: 0x1000 READ image: 13 offset: 0x6000 length: 0x1000 READ image: 13 offset: 0x7000 length: 0x1000 READ image: 13 offset: 0x8000 length: 0x1000 READ image: 13 offset: 0x9000 length: 0x1000 READ image: 13 offset: 0xa000 length: 0x1000 READ image: 13 offset: 0xb000 length: 0x1000 READ image: 13 offset: 0xc000 length: 0x1000 READ image: 13 offset: 0xd000 length: 0x1000 READ image: 13 offset: 0xe000 length: 0x1000 READ image: 13 offset: 0xf000 length: 0x1000 READ image: 13 offset: 0x10000 length: 0x1000 READ image: 13 offset: 0x11000 length: 0x1000 READ image: 13 offset: 0x12000 length: 0x1000 READ image: 13 offset: 0x13000 length: 0x1000 READ image: 13 offset: 0x14000 length: 0x1000 READ image: 13 offset: 0x15000 length: 0x1000 READ image: 13 offset: 0x16000 length: 0x1000 READ image: 13 offset: 0x17000 length: 0x1000 READ image: 13 offset: 0x18000 length: 0x1000 READ image: 13 offset: 0x19000 length: 0x1000 READ image: 13 offset: 0x1a000 length: 0x1000 READ image: 13 offset: 0x1b000 length: 0x1000 READ image: 13 offset: 0x1c000 length: 0x1000 READ image: 13 offset: 0x1d000 length: 0x1000 READ image: 13 offset: 0x1e000 length: 0x1000 READ image: 13 offset: 0x1f000 length: 0x1000 READ image: 13 offset: 0x20000 length: 0x1000 READ image: 13 offset: 0x21000 length: 0x1000 READ image: 13 offset: 0x22000 length: 0x1000 READ image: 13 offset: 0x23000 length: 0x1000 READ image: 13 offset: 0x24000 length: 0x1000 READ image: 13 offset: 0x25000 length: 0x1000 READ image: 13 offset: 0x26000 length: 0x1000 READ image: 13 offset: 0x27000 length: 0x1000 READ image: 13 offset: 0x28000 length: 0x1000 READ image: 13 offset: 0x29000 length: 0x1000 READ image: 13 offset: 0x2a000 length: 0x1000 READ image: 13 offset: 0x2b000 length: 0x1000 READ image: 13 offset: 0x2c000 length: 0x1000 READ image: 13 offset: 0x2d000 length: 0x1000 READ image: 13 offset: 0x2e000 length: 0x1000 READ image: 13 offset: 0x2f000 length: 0x1000 READ image: 13 offset: 0x30000 length: 0x1000 READ image: 13 offset: 0x31000 length: 0x1000 READ image: 13 offset: 0x32000 length: 0x1000 READ image: 13 offset: 0x33000 length: 0x1000 READ image: 13 offset: 0x34000 length: 0x1000 READ image: 13 offset: 0x35000 length: 0x1000 READ image: 13 offset: 0x36000 length: 0x1000 READ image: 13 offset: 0x37000 length: 0x1000 READ image: 13 offset: 0x38000 length: 0x1000 READ image: 13 offset: 0x39000 length: 0x1000 READ image: 13 offset: 0x3a000 length: 0x1000 READ image: 13 offset: 0x3b000 length: 0x1000 READ image: 13 offset: 0x3c000 length: 0x1000 READ image: 13 offset: 0x3d000 length: 0x1000 READ image: 13 offset: 0x3e000 length: 0x1000 READ image: 13 offset: 0x3f000 length: 0x1000 READ image: 13 offset: 0x40000 length: 0x1000 READ image: 13 offset: 0x41000 length: 0x1000 READ image: 13 offset: 0x42000 length: 0x1000 READ image: 13 offset: 0x43000 length: 0x1000 READ image: 13 offset: 0x44000 length: 0x1000 READ image: 13 offset: 0x45000 length: 0x1000 READ image: 13 offset: 0x46000 length: 0x1000 READ image: 13 offset: 0x47000 length: 0x1000 READ image: 13 offset: 0x48000 length: 0x1000 READ image: 13 offset: 0x49000 length: 0x1000 READ image: 13 offset: 0x4a000 length: 0x1000 READ image: 13 offset: 0x4b000 length: 0x1000 READ image: 13 offset: 0x4c000 length: 0x1000 READ image: 13 offset: 0x4d000 length: 0x1000 READ image: 13 offset: 0x4e000 length: 0x1000 READ image: 13 offset: 0x4f000 length: 0x1000 READ image: 13 offset: 0x50000 length: 0x1000 READ image: 13 offset: 0x51000 length: 0x1000 READ image: 13 offset: 0x52000 length: 0x1000 READ image: 13 offset: 0x53000 length: 0x1000 READ image: 13 offset: 0x54000 length: 0x390 READ image: 13 offset: 0x54390 length: 0x1000 READ image: 13 offset: 0x55390 length: 0x1000 READ image: 13 offset: 0x56390 length: 0x1000 READ image: 13 offset: 0x57390 length: 0x1000 READ image: 13 offset: 0x58390 length: 0x1000 READ image: 13 offset: 0x59390 length: 0x1000 READ image: 13 offset: 0x5a390 length: 0x1000 READ image: 13 offset: 0x5b390 length: 0x1000 READ image: 13 offset: 0x5c390 length: 0x1000 READ image: 13 offset: 0x5d390 length: 0x1000 READ image: 13 offset: 0x5e390 length: 0x1000 READ image: 13 offset: 0x5f390 length: 0x1000 READ image: 13 offset: 0x60390 length: 0xb68 END OF IMAGE image: 13 status: 0 DONE status: 0 qdl: firehose operation timed out LOG: [email protected] [email protected] ERROR: n = -1, errno = 110 (Connection timed out) LOG: [email protected] [email protected] qdl: firehose operation timed out LOG: start 131072, num 172032 LOG: Finished sector address 303104 [PROGRAM] flashed "modem" successfully at 10752kB/s LOG: start 393234, num 723 LOG: Finished sector address 393957 [PROGRAM] flashed "sbl1" successfully LOG: start 394258, num 723 LOG: Finished sector address 394981 [PROGRAM] flashed "sbl1bak" successfully LOG: start 395282, num 365 LOG: Finished sector address 395647 [PROGRAM] flashed "rpm" successfully LOG: start 396306, num 365 LOG: Finished sector address 396671 [PROGRAM] flashed "rpmbak" successfully LOG: start 397330, num 2991 LOG: Finished sector address 400321 [PROGRAM] flashed "tz" successfully LOG: start 401426, num 2991 LOG: Finished sector address 404417 [PROGRAM] flashed "tzbak" successfully LOG: start 405522, num 119 LOG: Finished sector address 405641 [PROGRAM] flashed "devcfg" successfully LOG: start 406034, num 119 LOG: Finished sector address 406153 [PROGRAM] flashed "devcfgbak" successfully LOG: start 406546, num 32768 LOG: Finished sector address 439314 [PROGRAM] flashed "dsp" successfully at 8192kB/s LOG: start 530352, num 1 LOG: Finished sector address 530353 [PROGRAM] flashed "sec" successfully LOG: start 786432, num 1186 LOG: Finished sector address 787618 [PROGRAM] flashed "aboot" successfully LOG: start 788480, num 1186 LOG: Finished sector address 789666 [PROGRAM] flashed "abootbak" successfully LOG: start 790528, num 55695 LOG: Finished sector address 846223 [PROGRAM] flashed "boot" successfully at 13923kB/s LOG: start 921600, num 60563 LOG: Finished sector address 982163 [PROGRAM] flashed "recovery" successfully at 10093kB/s LOG: start 1054720, num 262160 LOG: Finished sector address 1316880 [PROGRAM] flashed "system" successfully at 10923kB/s LOG: start 1318792, num 16 LOG: Finished sector address 1318808 [PROGRAM] flashed "system" successfully LOG: start 1322848, num 256176 LOG: Finished sector address 1579024 [PROGRAM] flashed "system" successfully at 11644kB/s LOG: start 1583064, num 258064 LOG: Finished sector address 1841128 [PROGRAM] flashed "system" successfully at 11730kB/s LOG: start 1841152, num 16 LOG: Finished sector address 1841168 [PROGRAM] flashed "system" successfully LOG: start 1843080, num 16 LOG: Finished sector address 1843096 [PROGRAM] flashed "system" successfully LOG: start 1847136, num 256176 LOG: Finished sector address 2103312 [PROGRAM] flashed "system" successfully at 10674kB/s LOG: start 2107352, num 13360 LOG: Finished sector address 2120712 [PROGRAM] flashed "system" successfully LOG: start 2365440, num 16 LOG: Finished sector address 2365456 [PROGRAM] flashed "system" successfully LOG: start 2367368, num 16 LOG: Finished sector address 2367384 [PROGRAM] flashed "system" successfully LOG: start 2371424, num 256176 LOG: Finished sector address 2627600 [PROGRAM] flashed "system" successfully at 9852kB/s LOG: start 2631640, num 258104 LOG: Finished sector address 2889744 [PROGRAM] flashed "system" successfully at 11732kB/s LOG: start 2891656, num 16 LOG: Finished sector address 2891672 [PROGRAM] flashed "system" successfully LOG: start 2895712, num 256176 LOG: Finished sector address 3151888 [PROGRAM] flashed "system" successfully at 11644kB/s LOG: start 3155928, num 1288 LOG: Finished sector address 3157216 [PROGRAM] flashed "system" successfully LOG: start 3414016, num 16 LOG: Finished sector address 3414032 [PROGRAM] flashed "system" successfully LOG: start 3415944, num 16 LOG: Finished sector address 3415960 [PROGRAM] flashed "system" successfully LOG: start 3420000, num 256176 LOG: Finished sector address 3676176 [PROGRAM] flashed "system" successfully at 11644kB/s LOG: start 3680216, num 240 LOG: Finished sector address 3680456 [PROGRAM] flashed "system" successfully LOG: start 3938304, num 16 LOG: Finished sector address 3938320 [PROGRAM] flashed "system" successfully LOG: start 3942360, num 88 LOG: Finished sector address 3942448 [PROGRAM] flashed "system" successfully LOG: start 4200448, num 16 LOG: Finished sector address 4200464 [PROGRAM] flashed "system" successfully LOG: start 4204504, num 88 LOG: Finished sector address 4204592 [PROGRAM] flashed "system" successfully LOG: start 4462592, num 16 LOG: Finished sector address 4462608 [PROGRAM] flashed "system" successfully LOG: start 4466648, num 258104 LOG: Finished sector address 4724752 [PROGRAM] flashed "system" successfully at 11732kB/s LOG: start 4728792, num 24568 LOG: Finished sector address 4753360 [PROGRAM] flashed "system" successfully at 6142kB/s LOG: start 4986880, num 16 LOG: Finished sector address 4986896 [PROGRAM] flashed "system" successfully LOG: start 5249024, num 16 LOG: Finished sector address 5249040 [PROGRAM] flashed "system" successfully LOG: start 5511168, num 16 LOG: Finished sector address 5511184 [PROGRAM] flashed "system" successfully LOG: start 5773312, num 16 LOG: Finished sector address 5773328 [PROGRAM] flashed "system" successfully LOG: start 6035456, num 16 LOG: Finished sector address 6035472 [PROGRAM] flashed "system" successfully LOG: start 6297600, num 16 LOG: Finished sector address 6297616 [PROGRAM] flashed "system" successfully LOG: start 6559744, num 16 LOG: Finished sector address 6559760 [PROGRAM] flashed "system" successfully LOG: start 6821888, num 16 LOG: Finished sector address 6821904 [PROGRAM] flashed "system" successfully LOG: start 7084032, num 16 LOG: Finished sector address 7084048 [PROGRAM] flashed "system" successfully LOG: start 7346176, num 16 LOG: Finished sector address 7346192 [PROGRAM] flashed "system" successfully LOG: start 7608320, num 16 LOG: Finished sector address 7608336 [PROGRAM] flashed "system" successfully LOG: start 7610248, num 16 LOG: Finished sector address 7610264 [PROGRAM] flashed "system" successfully LOG: start 7614304, num 256176 LOG: Finished sector address 7870480 [PROGRAM] flashed "system" successfully at 11644kB/s LOG: start 8132608, num 16 LOG: Finished sector address 8132624 [PROGRAM] flashed "system" successfully LOG: start 8134536, num 16 LOG: Finished sector address 8134552 [PROGRAM] flashed "system" successfully LOG: start 8138592, num 256136 LOG: Finished sector address 8394728 [PROGRAM] flashed "system" successfully at 11642kB/s LOG: start 8394752, num 16 LOG: Finished sector address 8394768 [PROGRAM] flashed "system" successfully LOG: start 8656896, num 16 LOG: Finished sector address 8656912 [PROGRAM] flashed "system" successfully LOG: start 8660952, num 258088 LOG: Finished sector address 8919040 [PROGRAM] flashed "system" successfully at 10753kB/s LOG: start 9043968, num 3952 LOG: Finished sector address 9047920 [PROGRAM] flashed "cache" successfully LOG: start 9306112, num 16 LOG: Finished sector address 9306128 [PROGRAM] flashed "cache" successfully LOG: start 9306312, num 16 LOG: Finished sector address 9306328 [PROGRAM] flashed "cache" successfully LOG: start 9568256, num 16 LOG: Finished sector address 9568272 [PROGRAM] flashed "cache" successfully LOG: start 9572008, num 11240 LOG: Finished sector address 9583248 [PROGRAM] flashed "cache" successfully at 5620kB/s LOG: start 9826304, num 1 LOG: Finished sector address 9826305 [PROGRAM] flashed "misc" successfully LOG: start 10095616, num 26853 LOG: Finished sector address 10122469 [PROGRAM] flashed "mdtp" successfully at 13426kB/s LOG: start 10223616, num 394 LOG: Finished sector address 10224010 [PROGRAM] flashed "cmnlib" successfully LOG: start 10224128, num 394 LOG: Finished sector address 10224522 [PROGRAM] flashed "cmnlibbak" successfully LOG: start 10224640, num 500 LOG: Finished sector address 10225140 [PROGRAM] flashed "cmnlib64" successfully LOG: start 10225152, num 500 LOG: Finished sector address 10225652 [PROGRAM] flashed "cmnlib64bak" successfully LOG: start 10225664, num 442 LOG: Finished sector address 10226106 [PROGRAM] flashed "keymaster" successfully LOG: start 10226176, num 442 LOG: Finished sector address 10226618 [PROGRAM] flashed "keymasterbak" successfully LOG: start 10354688, num 26 LOG: Finished sector address 10354714 [PROGRAM] flashed "apdp" successfully LOG: start 10355200, num 26 LOG: Finished sector address 10355226 [PROGRAM] flashed "msadp" successfully LOG: start 10486800, num 327680 LOG: Finished sector address 10814480 [PROGRAM] flashed "APD" successfully at 10922kB/s LOG: start 10814480, num 86016 LOG: Finished sector address 10900496 [PROGRAM] flashed "ADF" successfully at 14336kB/s LOG: start 10967056, num 20480 LOG: Finished sector address 10987536 [PROGRAM] flashed "factory" successfully at 10240kB/s LOG: start 11141120, num 8728 LOG: Finished sector address 11149848 [PROGRAM] flashed "userdata" successfully at 4364kB/s LOG: start 11403264, num 16 LOG: Finished sector address 11403280 [PROGRAM] flashed "userdata" successfully LOG: start 11407880, num 16 LOG: Finished sector address 11407896 [PROGRAM] flashed "userdata" successfully LOG: start 11665408, num 16 LOG: Finished sector address 11665424 [PROGRAM] flashed "userdata" successfully LOG: start 11669520, num 258048 LOG: Finished sector address 11927568 [PROGRAM] flashed "userdata" successfully at 11729kB/s LOG: start 11932168, num 16 LOG: Finished sector address 11932184 [PROGRAM] flashed "userdata" successfully LOG: start 12189696, num 16 LOG: Finished sector address 12189712 [PROGRAM] flashed "userdata" successfully LOG: start 12451840, num 16 LOG: Finished sector address 12451856 [PROGRAM] flashed "userdata" successfully LOG: start 12456456, num 16 LOG: Finished sector address 12456472 [PROGRAM] flashed "userdata" successfully LOG: start 12713984, num 16 LOG: Finished sector address 12714000 [PROGRAM] flashed "userdata" successfully LOG: start 12976128, num 16 LOG: Finished sector address 12976144 [PROGRAM] flashed "userdata" successfully LOG: start 12980744, num 16 LOG: Finished sector address 12980760 [PROGRAM] flashed "userdata" successfully LOG: start 13238272, num 16 LOG: Finished sector address 13238288 [PROGRAM] flashed "userdata" successfully LOG: start 13500416, num 16 LOG: Finished sector address 13500432 [PROGRAM] flashed "userdata" successfully LOG: start 13505032, num 16 LOG: Finished sector address 13505048 [PROGRAM] flashed "userdata" successfully LOG: start 13762560, num 16 LOG: Finished sector address 13762576 [PROGRAM] flashed "userdata" successfully LOG: start 14024704, num 16 LOG: Finished sector address 14024720 [PROGRAM] flashed "userdata" successfully LOG: start 14286848, num 16 LOG: Finished sector address 14286864 [PROGRAM] flashed "userdata" successfully LOG: start 14548992, num 16 LOG: Finished sector address 14549008 [PROGRAM] flashed "userdata" successfully LOG: start 14811136, num 16 LOG: Finished sector address 14811152 [PROGRAM] flashed "userdata" successfully LOG: start 15073280, num 16 LOG: Finished sector address 15073296 [PROGRAM] flashed "userdata" successfully LOG: start 15335424, num 16 LOG: Finished sector address 15335440 [PROGRAM] flashed "userdata" successfully LOG: start 15597568, num 16 LOG: Finished sector address 15597584 [PROGRAM] flashed "userdata" successfully LOG: start 15859712, num 16 LOG: Finished sector address 15859728 [PROGRAM] flashed "userdata" successfully LOG: start 16121856, num 16 LOG: Finished sector address 16121872 [PROGRAM] flashed "userdata" successfully LOG: start 16384000, num 16 LOG: Finished sector address 16384016 [PROGRAM] flashed "userdata" successfully LOG: start 16646144, num 16 LOG: Finished sector address 16646160 [PROGRAM] flashed "userdata" successfully LOG: start 16908288, num 16 LOG: Finished sector address 16908304 [PROGRAM] flashed "userdata" successfully LOG: start 17170432, num 16 LOG: Finished sector address 17170448 [PROGRAM] flashed "userdata" successfully LOG: start 17432576, num 16 LOG: Finished sector address 17432592 [PROGRAM] flashed "userdata" successfully LOG: start 17694720, num 16 LOG: Finished sector address 17694736 [PROGRAM] flashed "userdata" successfully LOG: start 17699336, num 16 LOG: Finished sector address 17699352 [PROGRAM] flashed "userdata" successfully LOG: start 17956864, num 16 LOG: Finished sector address 17956880 [PROGRAM] flashed "userdata" successfully LOG: start 18219008, num 16 LOG: Finished sector address 18219024 [PROGRAM] flashed "userdata" successfully LOG: start 18223624, num 16 LOG: Finished sector address 18223640 [PROGRAM] flashed "userdata" successfully LOG: start 18481152, num 16 LOG: Finished sector address 18481168 [PROGRAM] flashed "userdata" successfully LOG: start 18743296, num 16 LOG: Finished sector address 18743312 [PROGRAM] flashed "userdata" successfully LOG: start 19005440, num 16 LOG: Finished sector address 19005456 [PROGRAM] flashed "userdata" successfully LOG: start 19267584, num 16 LOG: Finished sector address 19267600 [PROGRAM] flashed "userdata" successfully LOG: start 19529728, num 16 LOG: Finished sector address 19529744 [PROGRAM] flashed "userdata" successfully LOG: start 19791872, num 16 LOG: Finished sector address 19791888 [PROGRAM] flashed "userdata" successfully LOG: start 20054016, num 16 LOG: Finished sector address 20054032 [PROGRAM] flashed "userdata" successfully LOG: start 20316160, num 16 LOG: Finished sector address 20316176 [PROGRAM] flashed "userdata" successfully LOG: start 20578304, num 16 LOG: Finished sector address 20578320 [PROGRAM] flashed "userdata" successfully LOG: start 20840448, num 16 LOG: Finished sector address 20840464 [PROGRAM] flashed "userdata" successfully LOG: start 21102592, num 16 LOG: Finished sector address 21102608 [PROGRAM] flashed "userdata" successfully LOG: start 21364736, num 16 LOG: Finished sector address 21364752 [PROGRAM] flashed "userdata" successfully LOG: start 21626880, num 16 LOG: Finished sector address 21626896 [PROGRAM] flashed "userdata" successfully LOG: start 21889024, num 16 LOG: Finished sector address 21889040 [PROGRAM] flashed "userdata" successfully LOG: start 22151168, num 16 LOG: Finished sector address 22151184 [PROGRAM] flashed "userdata" successfully LOG: start 22413312, num 16 LOG: Finished sector address 22413328 [PROGRAM] flashed "userdata" successfully LOG: start 22675456, num 16 LOG: Finished sector address 22675472 [PROGRAM] flashed "userdata" successfully LOG: start 22937600, num 16 LOG: Finished sector address 22937616 [PROGRAM] flashed "userdata" successfully LOG: start 23199744, num 16 LOG: Finished sector address 23199760 [PROGRAM] flashed "userdata" successfully LOG: start 23461888, num 16 LOG: Finished sector address 23461904 [PROGRAM] flashed "userdata" successfully LOG: start 23724032, num 16 LOG: Finished sector address 23724048 [PROGRAM] flashed "userdata" successfully LOG: start 23986176, num 16 LOG: Finished sector address 23986192 [PROGRAM] flashed "userdata" successfully LOG: start 23990792, num 16 LOG: Finished sector address 23990808 [PROGRAM] flashed "userdata" successfully LOG: start 24248320, num 16 LOG: Finished sector address 24248336 [PROGRAM] flashed "userdata" successfully LOG: start 24510464, num 16 LOG: Finished sector address 24510480 [PROGRAM] flashed "userdata" successfully LOG: start 24772608, num 16 LOG: Finished sector address 24772624 [PROGRAM] flashed "userdata" successfully LOG: start 25034752, num 16 LOG: Finished sector address 25034768 [PROGRAM] flashed "userdata" successfully LOG: start 25296896, num 16 LOG: Finished sector address 25296912 [PROGRAM] flashed "userdata" successfully LOG: start 25559040, num 16 LOG: Finished sector address 25559056 [PROGRAM] flashed "userdata" successfully LOG: start 25821184, num 16 LOG: Finished sector address 25821200 [PROGRAM] flashed "userdata" successfully LOG: start 26083328, num 16 LOG: Finished sector address 26083344 [PROGRAM] flashed "userdata" successfully LOG: start 26345472, num 16 LOG: Finished sector address 26345488 [PROGRAM] flashed "userdata" successfully LOG: start 26607616, num 16 LOG: Finished sector address 26607632 [PROGRAM] flashed "userdata" successfully LOG: start 26869760, num 16 LOG: Finished sector address 26869776 [PROGRAM] flashed "userdata" successfully LOG: start 27131904, num 16 LOG: Finished sector address 27131920 [PROGRAM] flashed "userdata" successfully LOG: start 27394048, num 16 LOG: Finished sector address 27394064 [PROGRAM] flashed "userdata" successfully LOG: start 27656192, num 16 LOG: Finished sector address 27656208 [PROGRAM] flashed "userdata" successfully LOG: start 27918336, num 16 LOG: Finished sector address 27918352 [PROGRAM] flashed "userdata" successfully LOG: start 28180480, num 16 LOG: Finished sector address 28180496 [PROGRAM] flashed "userdata" successfully LOG: start 28442624, num 16 LOG: Finished sector address 28442640 [PROGRAM] flashed "userdata" successfully LOG: start 28704768, num 16 LOG: Finished sector address 28704784 [PROGRAM] flashed "userdata" successfully LOG: start 28966912, num 16 LOG: Finished sector address 28966928 [PROGRAM] flashed "userdata" successfully LOG: start 29229056, num 16 LOG: Finished sector address 29229072 [PROGRAM] flashed "userdata" successfully LOG: start 29491200, num 16 LOG: Finished sector address 29491216 [PROGRAM] flashed "userdata" successfully LOG: start 29753344, num 16 LOG: Finished sector address 29753360 [PROGRAM] flashed "userdata" successfully LOG: start 29757456, num 36064 LOG: Finished sector address 29793520 [PROGRAM] flashed "userdata" successfully at 18032kB/s LOG: start 11010048, num 1 LOG: Finished sector address 11010049 [PROGRAM] flashed "version" successfully LOG: start 0, num 34 LOG: Finished sector address 34 [PROGRAM] flashed "PrimaryGPT" successfully LOG: start 61071327, num 33 LOG: Finished sector address 61071360 [PROGRAM] flashed "BackupGPT" successfully Update last partition 53 'userdata' with actual size in Primary Header. LOG: Patched sector 15 with 03A3DFDE Update last partition 53 'userdata' with actual size in Backup Header. LOG: Patched sector 61071340 with 03A3DFDE Update Primary Header with LastUseableLBA. LOG: Patched sector 1 with 03A3DFDE Update Backup Header with LastUseableLBA. LOG: Patched sector 61071359 with 03A3DFDE Update Primary Header with BackupGPT Header Location. LOG: Patched sector 1 with 03A3DFFF Update Backup Header with CurrentLBA. LOG: Patched sector 61071359 with 03A3DFFF Update Backup Header with Partition Array Location. LOG: Patched sector 61071359 with 03A3DFDF Update Primary Header with CRC of Partition Array. LOG: crc start sector 2, over bytes 7168 LOG: Patched sector 1 with 17C1FAC8 Update Backup Header with CRC of Partition Array. LOG: crc start sector 61071327, over bytes 7168 LOG: Patched sector 61071359 with 17C1FAC8 Zero Out Header CRC in Primary Header. LOG: Patched sector 1 with 00000000 Update Primary Header with CRC of Primary Header. LOG: crc start sector 1, over bytes 92 LOG: Patched sector 1 with 964C7190 Zero Out Header CRC in Backup Header. LOG: Patched sector 61071359 with 00000000 Update Backup Header with CRC of Backup Header. LOG: crc start sector 61071359, over bytes 92 LOG: Patched sector 61071359 with 2A632198 LOG: Set bootable drive to 0. partition 0 is now bootable Despite having a "bootable partition 0" and somewhere among the log "flashed "boot" successfully at 13923kB/s" it seems that the phone is stuck in QDL mode. When I unplug the phone and try to power it on or start the bootloader nothing happens. Connecting it back to the PC shows that it is still in QDL mode. So I tried to unplug the battery, plug it back, same thing. I went so far as to connect the phone with an unplugged battery and the PC immediately detects it in QDL mode. My only concern is with the "qdl: firehose operation timed out"... I searched info on the internet, the only thing useful I found and tried is to use a different QDL version, but it failed. And I stumbled upon 3 different firmware versions. So I am wondering what it might be, is it a normal behavior and do I need an additional step to boot? I made sure before posting to try all the tips listed above. Thanks in advance for your help.
If you didn't restart anything after firehose timed out I don't think it was flashing anything. It said it was but I don't believe it, if the loader timed out and failed, what was it flashing ?
Do anyone has an idea what can be wrong: ./qdl --debug --storage emmc --include /home/rudi/Downloads/9008/prog_emmc_firehose_8953_ddr.mbn /home/rudi/Downloads/9008/rawprogram0.xml /home/rudi/Downloads/9008/patch0.xml HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0 READ image: 13 offset: 0x0 length: 0x34 END OF IMAGE image: 13 status: 20 received non-successful result Thanks!
rudi.timmer said: Do anyone has an idea what can be wrong: ./qdl --debug --storage emmc --include /home/rudi/Downloads/9008/prog_emmc_firehose_8953_ddr.mbn /home/rudi/Downloads/9008/rawprogram0.xml /home/rudi/Downloads/9008/patch0.xml HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0 READ image: 13 offset: 0x0 length: 0x34 END OF IMAGE image: 13 status: 20 received non-successful result Thanks! Click to expand... Click to collapse include directory /home/rudi/Downloads/9008 then path to firehose, rawprogram and patch. edit: Like below. Path to folder so it knows where to get all files then firehose rawprogram and patch. Code: ./qdl --debug --storage emmc --include /home/rudi/Downloads/9008 /home/rudi/Downloads/9008/prog_emmc_firehose_8953_ddr.mbn /home/rudi/Downloads/9008/rawprogram0.xml /home/rudi/Downloads/9008/patch0.xml
tek3195 said: include directory /home/rudi/Downloads/9008 then path to firehose, rawprogram and patch. Click to expand... Click to collapse Ok thanks!
rudi.timmer said: Ok thanks! Click to expand... Click to collapse I edited post above. It has full command if you want to copy paste.
tek3195 said: I edited post above. It has full command if you want to copy paste. Click to expand... Click to collapse Ok thanks but i have found it out myself when you have posted the first message and it worked out OK so everything is fixed ! Thanks!!
Ricky0178 said: Introduction Hey guys! In my journey to completely go from windows to linux I was trying to see if there was a qfil alternative for linux, seeing that the program barely works on wine nor on a WIndows VM, so after a lot of digging i found an open source alternative to that, so today I'm going to show how you could flash any rom using qdl on linux (in my case I have a lenovo z5 pro gt so the guide will help you specifically with that) You need some things before we start: Your rom file, which you can get from lolinet A few dependencies, which you can install with Code: sudo apt install fastboot libxml2-dev libudev-dev git build-essentials make QDL binaries, downloadable via the command Code: git clone https://git.linaro.org/landing-teams/working/qualcomm/qdl.git Preparing files and Building QDL Once you got all the files you need to first extract the files stored on the *.zip of the rom you downloaded on a folder (for simplicity's sake you should call the folder something easy and sort such as z5pro). You should now look for a few files on the newly unzipped folder, especially for patch0.xml rawprogram_unparse0.xml, prog_firehose_ddr.elf (could have also a .mbn file extension, it's the same) Some Linux distributions come with ModemManager, a tool for configuring Mobile Broadband. You should stop this service because it interferes with the process Code: sudo systemctl stop ModemManager After that open a terminal and cd to the qdl folder that you downloaded with git and run make. If everything went to plan you should now have a qdl file. Test if it works by just typing on the terminal "./qdl" At this point you are nearly done! start building your command without pressing enter. it should have this scruture: Code: ./qdl --debug --storage ufs --include /path/to/z5pro /path/to/prog_firehose_ddr.elf /path/to/rawprogram0_unparse0.xml /path/to/patch0.xml Before pressing enter you should send your device in EDL mode. You can do this in a variety of ways: From fastboot Code: fastboot reboot edl By pressing both vol up and vol down and connecting the phone to the computer Press send on the terminal to start the process. Beware, you should do this as quickly as you can, otherwise it could just error you out Wait at least 10 minutes for the process to complete and congratulations, you should have a working rom installed on your phone! Thanks a lot to 96boards.org for telling me the necessary dependencies to run the program, it really helped me a lot on the process. If my guide helped you leaving a thanks would be greatly appreciated! Click to expand... Click to collapse this what i keep getting...any help is appreciated [email protected]:~$ chmod u=rwx,g=r,o=r qdl [email protected]:~$ sudo qdl --storage ufs --include /Home/downloads/9008 /Home/qdl/rp2-edl/prog_ufs_firehose_sdm845.elf /Home/downloads/9008 /Home/qdl/rp2-edl/rawprogram0xml /Home/downloads/9008 /Home/qdl/patch0.xml I/O error : Permission denied I/O error : Permission denied I/O warning : failed to load external entity "/Home/downloads/9008" [PATCH] failed to parse /Home/downloads/9008 qdl: failed to detect file type of /Home/downloads/9008
ATACELITE said: this what i keep getting...any help is appreciated [email protected]:~$ chmod u=rwx,g=r,o=r qdl [email protected]:~$ sudo qdl --storage ufs --include /Home/downloads/9008 /Home/qdl/rp2-edl/prog_ufs_firehose_sdm845.elf /Home/downloads/9008 /Home/qdl/rp2-edl/rawprogram0xml /Home/downloads/9008 /Home/qdl/patch0.xml I/O error : Permission denied I/O error : Permission denied I/O warning : failed to load external entity "/Home/downloads/9008" [PATCH] failed to parse /Home/downloads/9008 qdl: failed to detect file type of /Home/downloads/9008 Click to expand... Click to collapse try with chmod a+x qdl
tek3195 said: try with chmod a+x qdl Click to expand... Click to collapse what is going on? howmto fix this? Thankyou in advance [email protected]:~/qdl/rp2-edl$ qdl --debug --storage ufs --include /home/android/qdl/rp2-edl/prog_ufs_firehose_sdm845.elf /home/android/qdl/rp2-edl/rawprogram0.xml /home/android/qdl/rp2-edl/patch0.xml Waiting for EDL device *** buffer overflow detected ***: terminated Aborted (core dumped)
ATACELITE said: what is going on? howmto fix this? Thankyou in advance [email protected]:~/qdl/rp2-edl$ qdl --debug --storage ufs --include /home/android/qdl/rp2-edl/prog_ufs_firehose_sdm845.elf /home/android/qdl/rp2-edl/rawprogram0.xml /home/android/qdl/rp2-edl/patch0.xml Waiting for EDL device *** buffer overflow detected ***: terminated Aborted (core dumped) Click to expand... Click to collapse You have to tell it where it is going to get all the files it is supposed to flash. Need the folder where they are located. Looks like you need to add /home/android/qdl/rp2-edl to your --include. Run qdl as root or with sudo.
tek3195 said: You have to tell it where it is going to get all the files it is supposed to flash. Need the folder where they are located. Looks like you need to add /home/android/qdl/rp2-edl to your --include. Run qdl as root or with sudo. Click to expand... Click to collapse So there should be no space after --include so like this...--include/home/android...etc. I will try with root privileges as well. I've been working on unbricking this razor phone 2 since 2020...I have more updated devices but the razer company makes it nearly impossible so it's personal at this point haha!
ATACELITE said: So there should be no space after --include so like this...--include/home/android...etc. I will try with root privileges as well. I've been working on unbricking this razor phone 2 since 2020...I have more updated devices but the razer company makes it nearly impossible so it's personal at this point haha! Click to expand... Click to collapse Also tek, thank you for taking time out of your day to continue to help on an outdated thread and for free. I really appreciate you.
ATACELITE said: So there should be no space after --include so like this...--include/home/android...etc. I will try with root privileges as well. I've been working on unbricking this razor phone 2 since 2020...I have more updated devices but the razer company makes it nearly impossible so it's personal at this point haha! Click to expand... Click to collapse There wil be a space after --include like this example for your system. Copy paste if you want. Code: --include /home/android/qdl/rp2-edl /home/android/qdl/rp2-edl/prog_ufs_firehose_sdm845.elf /home/android/qdl/rp2-edl/rawprogram0.xml /home/android/qdl/rp2-edl/patch0.xml
@ATACELITE you include that folder with all your rom files so when rawprogram and patch tell it what partitions to flash it will know where to get them.
Hisense A5 L1657.6.12.01.00_Root_by_Sillage?
Hi, has anyone been able to download the latest Hisense A5 L1657.6.12.01.00 root as available in this Chinese forum? Would love to give it a go, but cannot find another source. (@joygram?)
this root kit is available here but the full firmware of version L1657.6.12.01.00 is still inaccessible.
Thanks for the download link! I rooted my 6.12.01.00 fine with it. The procedure I followed is the following: - Install 6.09 from sd card - OTA upgrade to 6.10, 6.11 and finally 6.12 - Then after too much trouble fighting windows, simply installed adb and qdl on my linux machine - adb reboot edl - sudo ./qdl --debug FireHose_HiSenseA5.mbn RawProgram_HiSenseA5.xml Patch_HiSenseA5.xml - adb install MagiskManager-v7.5.1.apk - update MagiskManager to v22 - et voila running the latest HiSense A5 firmware with root
artelse said: Thanks for the download link! I rooted my 6.12.01.00 fine with it. The procedure I followed is the following: - Install 6.09 from sd card - OTA upgrade to 6.10, 6.11 and finally 6.12 - Then after too much trouble fighting windows, simply installed adb and qdl on my linux machine - adb reboot edl - sudo ./qdl --debug FireHose_HiSenseA5.mbn RawProgram_HiSenseA5.xml Patch_HiSenseA5.xml - adb install MagiskManager-v7.5.1.apk - update MagiskManager to v22 - et voila running the latest HiSense A5 firmware with root Click to expand... Click to collapse Thanks for sharing! I'm now on a rooted 6.10, do I need to roll back to 6.09 first and then follow your steps? Thanks a lot!
Yes, I think you should start with an unmodified firmware, upgrade three times (..) and then apply the rootkit. 6.11 is a quite substantial update compared to the others in terms of size, about 500MB. Good luck.
artelse said: Yes, I think you should start with an unmodified firmware, upgrade three times (..) and then apply the rootkit. 6.11 is a quite substantial update compared to the others in terms of size, about 500MB. Good luck. Click to expand... Click to collapse Thank you very much!!
Mod edit - translated by https://translate.google.com/?hl=en Thank you for sharing ************ 謝謝分享
Works following the steps above. I installed Joygram's version of Gapps again, but was wondering if anyone has tried installing a more complete version of Gapps in magisk? I was reading that you can potentially install openGapps stock in Magisk? Just curious if it helps with anything or just causes a bootloop or too much of a mess with the Vision system.
artelse said: Thanks for the download link! I rooted my 6.12.01.00 fine with it. The procedure I followed is the following: - Install 6.09 from sd card - OTA upgrade to 6.10, 6.11 and finally 6.12 - Then after too much trouble fighting windows, simply installed adb and qdl on my linux machine - adb reboot edl - sudo ./qdl --debug FireHose_HiSenseA5.mbn RawProgram_HiSenseA5.xml Patch_HiSenseA5.xml - adb install MagiskManager-v7.5.1.apk Click to expand... Click to collapse I did it. I launch magisk, click on "install", upgrade to 22.1, after i launch the updtated app, magisk is not installed (just SAR : Yes), my phone is not rooted. Did I miss a step? What should I do?
Dunno, has been a while since I worked on it. SAR is fine for my purpose as I can grant apps superuser rights.
artelse said: Dunno, has been a while since I worked on it. SAR is fine for my purpose as I can grant apps superuser rights. Click to expand... Click to collapse I can't grant apps superuser rights, the phone is not root :c When I execute sudo ./qdl --debug FireHose_HiSenseA5.mbn RawProgram_HiSenseA5.xml Patch_HiSenseA5.xml : HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0 READ image: 13 offset: 0x0 length: 0x34 READ image: 13 offset: 0x34 length: 0x140 READ image: 13 offset: 0x1000 length: 0x1000 READ image: 13 offset: 0x2000 length: 0xa68 READ image: 13 offset: 0x686a8 length: 0x1000 READ image: 13 offset: 0x696a8 length: 0x1000 READ image: 13 offset: 0x6a6a8 length: 0x878 READ image: 13 offset: 0x6af20 length: 0xb28 READ image: 13 offset: 0x3000 length: 0x1000 READ image: 13 offset: 0x4000 length: 0x1000 READ image: 13 offset: 0x5000 length: 0x1000 READ image: 13 offset: 0x6000 length: 0x1000 READ image: 13 offset: 0x7000 length: 0x1000 READ image: 13 offset: 0x8000 length: 0x1000 READ image: 13 offset: 0x9000 length: 0x1000 READ image: 13 offset: 0xa000 length: 0x1000 READ image: 13 offset: 0xb000 length: 0x1000 READ image: 13 offset: 0xc000 length: 0x1000 READ image: 13 offset: 0xd000 length: 0x1000 READ image: 13 offset: 0xe000 length: 0x1000 READ image: 13 offset: 0xf000 length: 0x1000 READ image: 13 offset: 0x10000 length: 0x1000 READ image: 13 offset: 0x11000 length: 0x1000 READ image: 13 offset: 0x12000 length: 0x1000 READ image: 13 offset: 0x13000 length: 0x1000 READ image: 13 offset: 0x14000 length: 0x1000 READ image: 13 offset: 0x15000 length: 0x1000 READ image: 13 offset: 0x16000 length: 0x1000 READ image: 13 offset: 0x17000 length: 0x1000 READ image: 13 offset: 0x18000 length: 0x1000 READ image: 13 offset: 0x19000 length: 0x1000 READ image: 13 offset: 0x1a000 length: 0x1000 READ image: 13 offset: 0x1b000 length: 0x1000 READ image: 13 offset: 0x1c000 length: 0x1000 READ image: 13 offset: 0x1d000 length: 0x1000 READ image: 13 offset: 0x1e000 length: 0x1000 READ image: 13 offset: 0x1f000 length: 0x1000 READ image: 13 offset: 0x20000 length: 0x1000 READ image: 13 offset: 0x21000 length: 0x1000 READ image: 13 offset: 0x22000 length: 0x1000 READ image: 13 offset: 0x23000 length: 0x1000 READ image: 13 offset: 0x24000 length: 0x1000 READ image: 13 offset: 0x25000 length: 0x1000 READ image: 13 offset: 0x26000 length: 0x1000 READ image: 13 offset: 0x27000 length: 0x1000 READ image: 13 offset: 0x28000 length: 0x1000 READ image: 13 offset: 0x29000 length: 0x1000 READ image: 13 offset: 0x2a000 length: 0x1000 READ image: 13 offset: 0x2b000 length: 0x1000 READ image: 13 offset: 0x2c000 length: 0x1000 READ image: 13 offset: 0x2d000 length: 0x1000 READ image: 13 offset: 0x2e000 length: 0x1000 READ image: 13 offset: 0x2f000 length: 0x1000 READ image: 13 offset: 0x30000 length: 0x1000 READ image: 13 offset: 0x31000 length: 0x1000 READ image: 13 offset: 0x32000 length: 0x1000 READ image: 13 offset: 0x33000 length: 0x1000 READ image: 13 offset: 0x34000 length: 0x1000 READ image: 13 offset: 0x35000 length: 0x1000 READ image: 13 offset: 0x36000 length: 0x1000 READ image: 13 offset: 0x37000 length: 0x1000 READ image: 13 offset: 0x38000 length: 0x1000 READ image: 13 offset: 0x39000 length: 0x1000 READ image: 13 offset: 0x3a000 length: 0x1000 READ image: 13 offset: 0x3b000 length: 0x1000 READ image: 13 offset: 0x3c000 length: 0x1000 READ image: 13 offset: 0x3d000 length: 0x1000 READ image: 13 offset: 0x3e000 length: 0x1000 READ image: 13 offset: 0x3f000 length: 0x1000 READ image: 13 offset: 0x40000 length: 0x1000 READ image: 13 offset: 0x41000 length: 0x1000 READ image: 13 offset: 0x42000 length: 0x1000 READ image: 13 offset: 0x43000 length: 0x1000 READ image: 13 offset: 0x44000 length: 0x1000 READ image: 13 offset: 0x45000 length: 0x1000 READ image: 13 offset: 0x46000 length: 0x1000 READ image: 13 offset: 0x47000 length: 0x1000 READ image: 13 offset: 0x48000 length: 0x1000 READ image: 13 offset: 0x49000 length: 0x1000 READ image: 13 offset: 0x4a000 length: 0x1000 READ image: 13 offset: 0x4b000 length: 0x1000 READ image: 13 offset: 0x4c000 length: 0x1000 READ image: 13 offset: 0x4d000 length: 0x1000 READ image: 13 offset: 0x4e000 length: 0x1000 READ image: 13 offset: 0x4f000 length: 0x1000 READ image: 13 offset: 0x50000 length: 0x1000 READ image: 13 offset: 0x51000 length: 0x1000 READ image: 13 offset: 0x52000 length: 0x1000 READ image: 13 offset: 0x53000 length: 0x1000 READ image: 13 offset: 0x54000 length: 0x1000 READ image: 13 offset: 0x55000 length: 0x1000 READ image: 13 offset: 0x56000 length: 0x1000 READ image: 13 offset: 0x57000 length: 0x1000 READ image: 13 offset: 0x58000 length: 0x728 READ image: 13 offset: 0x58728 length: 0x1000 READ image: 13 offset: 0x59728 length: 0x1000 READ image: 13 offset: 0x5a728 length: 0x1000 READ image: 13 offset: 0x5b728 length: 0x1000 READ image: 13 offset: 0x5c728 length: 0x1000 READ image: 13 offset: 0x5d728 length: 0x1000 READ image: 13 offset: 0x5e728 length: 0x1000 READ image: 13 offset: 0x5f728 length: 0x1000 READ image: 13 offset: 0x60728 length: 0x1000 READ image: 13 offset: 0x61728 length: 0x1000 READ image: 13 offset: 0x62728 length: 0x1000 READ image: 13 offset: 0x63728 length: 0x1000 READ image: 13 offset: 0x64728 length: 0x1000 READ image: 13 offset: 0x65728 length: 0x1000 READ image: 13 offset: 0x66728 length: 0x1000 READ image: 13 offset: 0x67728 length: 0xf80 END OF IMAGE image: 13 status: 0 DONE status: 0 FIREHOSE WRITE: <?xml version="1.0"?> <data><nop value="ping"/></data> FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" /></data><?xml version="1.0" encoding="UTF-8" ?><data><log value="[email protected] [email protected]" /></data> LOG: [email protected] [email protected] FIREHOSE WRITE: <?xml version="1.0"?> <data><configure MemoryName="ufs" MaxPayloadSizeToTargetInBytes="1048576" verbose="0" ZLPAwareHost="0"/></data> FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><log value="[email protected] [email protected]" /></data> LOG: [email protected] [email protected] FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" MinVersionSupported="1" MemoryName="eMMC" MaxPayloadSizeFromTargetInBytes="4096" MaxPayloadSizeToTargetInBytes="1048576" MaxPayloadSizeToTargetInBytesSupported="1048576" MaxXMLSizeInBytes="4096" Version="1" TargetName="8937" /></data> Unable to open vbmeta_sillage_sign.img...ignoring Unable to open boot_sillage_sign.img...ignoring Update last partition 67 'grow' with actual size in Primary Header. FIREHOSE WRITE: <?xml version="1.0"?> <data><patch SECTOR_SIZE_IN_BYTES="512" byte_offset="296" filename="DISK" physical_partition_number="0" size_in_bytes="8" start_sector="18" value="NUM_DISK_SECTORS-34."/></data> FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><log value="Patched sector 18 with 0749FFDE" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" /></data> LOG: Patched sector 18 with 0749FFDE Update last partition 67 'grow' with actual size in Backup Header. FIREHOSE WRITE: <?xml version="1.0"?> <data><patch SECTOR_SIZE_IN_BYTES="512" byte_offset="296" filename="DISK" physical_partition_number="0" size_in_bytes="8" start_sector="NUM_DISK_SECTORS-17." value="NUM_DISK_SECTORS-34."/></data> FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><log value="Patched sector 122290159 with 0749FFDE" /></data> LOG: Patched sector 122290159 with 0749FFDE FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" /></data> Update Primary Header with LastUseableLBA. FIREHOSE WRITE: <?xml version="1.0"?> <data><patch SECTOR_SIZE_IN_BYTES="512" byte_offset="48" filename="DISK" physical_partition_number="0" size_in_bytes="8" start_sector="1" value="NUM_DISK_SECTORS-34."/></data> FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><log value="Patched sector 1 with 0749FFDE" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" /></data> LOG: Patched sector 1 with 0749FFDE Update Backup Header with LastUseableLBA. FIREHOSE WRITE: <?xml version="1.0"?> <data><patch SECTOR_SIZE_IN_BYTES="512" byte_offset="48" filename="DISK" physical_partition_number="0" size_in_bytes="8" start_sector="NUM_DISK_SECTORS-1." value="NUM_DISK_SECTORS-34."/></data> FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><log value="Patched sector 122290175 with 0749FFDE" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" /></data> LOG: Patched sector 122290175 with 0749FFDE Update Primary Header with BackupGPT Header Location. FIREHOSE WRITE: <?xml version="1.0"?> <data><patch SECTOR_SIZE_IN_BYTES="512" byte_offset="32" filename="DISK" physical_partition_number="0" size_in_bytes="8" start_sector="1" value="NUM_DISK_SECTORS-1."/></data> FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><log value="Patched sector 1 with 0749FFFF" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" /></data> LOG: Patched sector 1 with 0749FFFF Update Backup Header with CurrentLBA. FIREHOSE WRITE: <?xml version="1.0"?> <data><patch SECTOR_SIZE_IN_BYTES="512" byte_offset="24" filename="DISK" physical_partition_number="0" size_in_bytes="8" start_sector="NUM_DISK_SECTORS-1." value="NUM_DISK_SECTORS-1."/></data> FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><log value="Patched sector 122290175 with 0749FFFF" /></data> LOG: Patched sector 122290175 with 0749FFFF FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" /></data> Update Backup Header with Partition Array Location. FIREHOSE WRITE: <?xml version="1.0"?> <data><patch SECTOR_SIZE_IN_BYTES="512" byte_offset="72" filename="DISK" physical_partition_number="0" size_in_bytes="8" start_sector="NUM_DISK_SECTORS-1" value="NUM_DISK_SECTORS-33."/></data> FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><log value="Patched sector 122290175 with 0749FFDF" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" /></data> LOG: Patched sector 122290175 with 0749FFDF Update Primary Header with CRC of Partition Array. FIREHOSE WRITE: <?xml version="1.0"?> <data><patch SECTOR_SIZE_IN_BYTES="512" byte_offset="88" filename="DISK" physical_partition_number="0" size_in_bytes="4" start_sector="1" value="CRC32(2,8704)"/></data> FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><log value="crc start sector 2, over bytes 8704" /></data> LOG: crc start sector 2, over bytes 8704 FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><log value="Patched sector 1 with 0572A741" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" /></data> LOG: Patched sector 1 with 0572A741 Update Backup Header with CRC of Partition Array. FIREHOSE WRITE: <?xml version="1.0"?> <data><patch SECTOR_SIZE_IN_BYTES="512" byte_offset="88" filename="DISK" physical_partition_number="0" size_in_bytes="4" start_sector="NUM_DISK_SECTORS-1." value="CRC32(NUM_DISK_SECTORS-33.,8704)"/></data> FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><log value="crc start sector 122290143, over bytes 8704" /></data> LOG: crc start sector 122290143, over bytes 8704 FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><log value="Patched sector 122290175 with DCB571CF" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" /></data> LOG: Patched sector 122290175 with DCB571CF Zero Out Header CRC in Primary Header. FIREHOSE WRITE: <?xml version="1.0"?> <data><patch SECTOR_SIZE_IN_BYTES="512" byte_offset="16" filename="DISK" physical_partition_number="0" size_in_bytes="4" start_sector="1" value="0"/></data> FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><log value="Patched sector 1 with 00000000" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" /></data> LOG: Patched sector 1 with 00000000 Update Primary Header with CRC of Primary Header. FIREHOSE WRITE: <?xml version="1.0"?> <data><patch SECTOR_SIZE_IN_BYTES="512" byte_offset="16" filename="DISK" physical_partition_number="0" size_in_bytes="4" start_sector="1" value="CRC32(1,92)"/></data> FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><log value="crc start sector 1, over bytes 92" /></data> LOG: crc start sector 1, over bytes 92 FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><log value="Patched sector 1 with E9BE6A11" /></data> LOG: Patched sector 1 with E9BE6A11 FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" /></data> Zero Out Header CRC in Backup Header. FIREHOSE WRITE: <?xml version="1.0"?> <data><patch SECTOR_SIZE_IN_BYTES="512" byte_offset="16" filename="DISK" physical_partition_number="0" size_in_bytes="4" start_sector="NUM_DISK_SECTORS-1." value="0"/></data> FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><log value="Patched sector 122290175 with 00000000" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" /></data> LOG: Patched sector 122290175 with 00000000 Update Backup Header with CRC of Backup Header. FIREHOSE WRITE: <?xml version="1.0"?> <data><patch SECTOR_SIZE_IN_BYTES="512" byte_offset="16" filename="DISK" physical_partition_number="0" size_in_bytes="4" start_sector="NUM_DISK_SECTORS-1." value="CRC32(NUM_DISK_SECTORS-1.,92)"/></data> FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><log value="crc start sector 122290175, over bytes 92" /></data> LOG: crc start sector 122290175, over bytes 92 FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><log value="Patched sector 122290175 with 20F9FAC0" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" /></data> LOG: Patched sector 122290175 with 20F9FAC0 no boot partition found FIREHOSE WRITE: <?xml version="1.0"?> <data><power value="reset"/></data> FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" /></data> Normal ?
It looks normal as it reads in the image and runs the patch. You didn't accidentally install Magisk via the install button?
That is to say? After flash, I install the apk, and after i launch the app (the additionnal requirements are not proposed) magisk manger said "Magisk is not installed" how do you proceed after the patch?
It's a hassle to get right and have tried many things, so my memory doesn't serve me well here. My notes have this after the adb install of MM: - update MagiskManager to install some .zip - update Magisk to 22.x, not 24. - DON'T install Magisk!! via de Install button.. leave it alone. What 'some .zip' means I don't recall.
Thanks but if Magisk is not install, the phone is not root
Success root using QSPT/QFIL with Windows ! After flash the root kit, I install magisk manger 7.5.1 apk, update to v22.1, install additional requirements, reboot, install gapps module, all work
artelse said: It's a hassle to get right and have tried many things, so my memory doesn't serve me well here. My notes have this after the adb install of MM: - update MagiskManager to install some .zip - update Magisk to 22.x, not 24. - DON'T install Magisk!! via de Install button.. leave it alone. What 'some .zip' means I don't recall. Click to expand... Click to collapse Woops installed 24... does this cause a boot loop is that why it should be avoided? Now I don't know what to do haha.
Can not remember if it got into a boot loop or something else. I tried so many things to get it working that I've lost the details what didn't work with 24. I had to start over quite a few times to get it right.
artelse said: Can not remember if it got into a boot loop or something else. I tried so many things to get it working that I've lost the details what didn't work with 24. I had to start over quite a few times to get it right. Click to expand... Click to collapse Hi, Which are the steps to root/install gapps/install a native language other than english, for Hisense A5 on 6.12.01.00?
lillo9546 said: Hi, Which are the steps to root/install gapps/install a native language other than english, for Hisense A5 on 6.12.01.00? Click to expand... Click to collapse I don't have Gapps, only installed microG.