Database Users

Phone Not Booting up

Hello devs,
recently i flash my ZUK Z1 with ZUI Rom with QFIL and my phone just does not boots up in neither fastboot nor twrp recovery, as good as dead.
Only thing i can see is com port is connected and while flashing the new stock rom the following error occured :
log details :
Programmer Path:C:\cm_12.1 qpst\prog_emmc_firehose_8974.mbn
Image Search Path: C:\cm_12.1 qpst
RAWPROGRAM file path: C:\cm_12.1 qpst\rawprogram0.xml
PATCH file path:C:\cm_12.1 qpst\patch0.xml
Image Search Path: C:\cm_12.1 qpst
RAWPROGRAM file path: C:\cm_12.1 qpst\rawprogram0.xml
PATCH file path:C:\cm_12.1 qpst\patch0.xml
Start Download
Program Path:C:\cm_12.1 qpst\prog_emmc_firehose_8974.mbn
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.exe -p \\.\COM3 -s 13:C:\cm_12.1 qpst\prog_emmc_firehose_8974.mbn 'Current working dir: C:\Users\Mathrudev\AppData\Roaming\Qualcomm\QFIL
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\cm_12.1
16:45:34: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
16:45:34: ERROR: function: sahara_main:854 Sahara protocol error
16:45:34: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Need assistance urgently.
Thanks in advance.

Unbrick ZenFone 3 Zoom ("Qualcomm hs-usb qdloader 9008" mode)

Hi, everybody!
I dealt with one glitch, I used the utility of management of block devices. I have unsuccessfully chosen the device, I have formatted all sections, respectively, I have received a brick.
Who has an experience of restoration of the loader of specifically our device? It is impossible still independently... The device was in the "Qualcomm hs-usb qdloader 9008" mode, now in the "Qualcomm hs-usb diagnostics 900e" mode

Return device in Qualcomm hs-usb qdloader 9008 mode.
QFIL utilite from packet QPST says "ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes."
How to win this error and return the device to life? I will be grateful for any help!
Log:
Start Download
Program Path:C:\IMAGE\prog_emmc_firehose_8953_ddr.mbn
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'D:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.exe -p \\.\COM21 -s 13:C:\IMAGE\prog_emmc_firehose_8953_ddr.mbn 'Current working dir: C:\Users\MyUser\AppData\Roaming\Qualcomm\QFIL
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\IMAGE\prog_emmc_firehose_8953_ddr.mbn
23:04:08: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
23:04:08: ERROR: function: sahara_main:854 Sahara protocol error
23:04:08: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download

The dump from the unblocked phone is necessary for restoration of my phone. I ask to help with search of a dump Asus ZenFone 3 Zoom ZE553KL (my phone is 128Gb version of built memory).
Thanks to all responded!

My Phone wont turn on too. Have you fix yours?

My Nexus 6p hard bricked itself after charging all night / new battery still nothing

Hello,
I bought my Nexus 6p (stock) three mounths ago. Phone had problems with battery (turned off ~20% etc) but all works fine.
Few days ago I spend all day outside the home when the outside temperature was about -15C degrees (Poland) when I took the phone in my hand, he suddenly turned off having 70% battery. In home I put it in the charger and worked normally.
Phone was on charger all night, I woke up at morning, put off charger and open Snapchat, then phone turned off itself.
Since then phone does not respond, nothing happens with any combination of button, chargers and ports, I havent any red led...
Only live signal from this device is that I see Qualcomm HS-USB QDLoader 9008 in devices menager when pluged to PC.
I trying this [howtos] debrick nexus 6p tutorial, but I get error, log:
Validating Application Configuration
Load APP Configuration
COM:10
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:\Program Files (x86)\Qualcomm\QPST\bin\nexus6p_fix_bricked\prog_emmc_firehose.mbn
SEARCHPATH:C:\Program Files (x86)\Qualcomm\QPST\bin\nexus6p_fix_bricked
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\Program Files (x86)\Qualcomm\QPST\bin\nexus6p_fix_bricked
RAWPROGRAM file path: C:\Program Files (x86)\Qualcomm\QPST\bin\nexus6p_fix_bricked\rawprogram0.xml
PATCH file path:C:\Program Files (x86)\Qualcomm\QPST\bin\nexus6p_fix_bricked\patch0.xml
Programmer Path:C:\Program Files (x86)\Qualcomm\QPST\bin\nexus6p_fix_bricked\prog_emmc_firehose.mbn
Process Index:0
Start Download
Program Path:C:\Program Files (x86)\Qualcomm\QPST\bin\nexus6p_fix_bricked\prog_emmc_firehose.mbn
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Users\Ja\Desktop\nexus\Qualcomm_Flash_Image_Loader_v2.0.0.5\Qualcomm_Flash_Image_Loader_v2.0.0.5\QSaharaServer.exe -p \\.\COM10 -s 13:C:\Program Files (x86)\Qualcomm\QPST\bin\nexus6p_fix_bricked\prog_emmc_firehose.mbn 'Current working dir: C:\Users\Ja\AppData\Roaming\Qualcomm\QFIL
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\Program Files (x86)\Qualcomm\QPST\bin\nexus6p_fix_bricked\prog_emmc_firehose.mbn
02:00:48: Requested ID 13, file: "C:\Program Files (x86)\Qualcomm\QPST\bin\nexus6p_fix_bricked\prog_emmc_firehose.mbn"
02:00:49: 305488 bytes transferred in 0.437000 seconds (0.6667MBps)
02:00:49: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
02:00:49: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
Download Fail:FireHose Fail FHLoader Fail:Nie można odnaleźć określonego pliku
Finish Download
Click to expand...
Click to collapse
*I dont see phone in adb devices or fastboot devices list
Soo I decided to bought new battery and replacement it myself. I did it yesterday and still, not working....
Is that motherboard problem?
I bought used nexus, I havent warranty and in my country that phone is RARE :crying:
I'm desperate, week without a phone....
Heeeeelp me, what can I do? and sorry for bad English :angel:

Have someone tried this the other way around? If the phone is stuck in EDL Mode (9008) then replacing the battery and not flashing with some tools before.
Is there some other way to get out of the EDL mode without the requirement of flashing something?
My phone went into EDL mode under heavy load and now i need my data. I dont want to loose my data, thats why i dont try flashing anything recently.

Would be great if someone could help. I cant get the phone out of EDL mode now for 1,5 months. I need my data.

Had the exact same problem, tried NAND Write via EDL and flashed fine as well, got red LED sometimes and nothing, also new battery didnt help, I guess you can consider yourself "lucky" and it probably is a CPU failure, you probably how to consider how important the data is to you as you wont get it out without any complex hardware soldering or repairs. Things could get costy if you dont know a good workshop.

Gmobilize said:
Had the exact same problem, tried NAND Write via EDL and flashed fine as well, got red LED sometimes and nothing, also new battery didnt help
Click to expand...
Click to collapse
You did not get this red LED before? Just after the NAND Write?
Is it possible to use the EDL mode to get the data out of the phone to put it on an other phone?

Redmi 7A bricked - Help need for programmer file

Hi! I have accidentally flashed the 5A Rom on my 7A rom. I was going to change my rom from a China Rom to a Global Rom. I have successfully unlocked the bootloader. However, I forgot that I purchased a 7A (oopsie xD) and instead downloaded the latest global fastboot rom for the 5A.
I was trying to reflash using MiFlashTool, but it asks for an EDL Authorization.. I also tried to flash using QFIL but to no avail as it keeps on throwing error that the header cannot be read.
I tried to bypass the EDL by downloading the oldest available fastboot rom for the 7A and used its firehose programmer file with the latest 7A rom and flashing it using QFIL. It has not shown the previous error I have mentioned, but another error has popped that it cannot find a file specified.
Any replies would be really appreciated.
Thanks!
EDIT: Here's the log file of the QFIL when trying to flash my phone using the programmer file of the Redmi 7A MIUI 10.2.4.0 Global Fastboot Rom.
If someone knows how to patch or force the programmer file to bypass the EDL Authorization, please help Thanks!
Code:
Validating Application Configuration
Load APP Configuration
COM:20
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:\Users\Vaio\Downloads\xiaomi\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn_50db06715d\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn\images\prog_emmc_firehose_8937_ddr.mbn
RESETSAHARASTATEEMACHINE:False
SEARCHPATH:C:\Users\Vaio\Downloads\xiaomi\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn_50db06715d\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn\images
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:True
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
AUTOPRESERVEPARTITIONS:False
PARTITIONPRESERVEMODE:0
PRESERVEDPARTITIONS:0
PRESERVEDPARTITIONS:
ERASEALL:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\Users\Vaio\Downloads\xiaomi\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn_50db06715d\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn\images
RAWPROGRAM file path: C:\Users\Vaio\Downloads\xiaomi\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn_50db06715d\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn\images\rawprogram0.xml
PATCH file path:C:\Users\Vaio\Downloads\xiaomi\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn_50db06715d\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn\images\patch0.xml
Programmer Path:C:\Users\Vaio\Downloads\xiaomi\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn_50db06715d\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn\images\prog_emmc_firehose_8937_ddr.mbn
Process Index:0
Start Download
Program Path:C:\Users\Vaio\Downloads\xiaomi\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn_50db06715d\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn\images\prog_emmc_firehose_8937_ddr.mbn
***** Working Folder:C:\Users\Vaio\AppData\Roaming\Qualcomm\QFIL\COMPORT_20
Binary build date: Oct 31 2016 @ 22:51:05
QSAHARASERVER CALLED LIKE THIS: 'C:\Users\Vaio\Downloads\xiaomi\QFIL-QualcommFlashImageLoader-v2.0.1.1\QSaharaServer.ex'Current working dir: C:\Users\Vaio\AppData\Roaming\Qualcomm\QFIL\COMPORT_20
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\Users\Vaio\Downloads\xiaomi\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn_50db06715d\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn\images\prog_emmc_firehose_8937_ddr.mbn
22:52:46: Requested ID 13, file: "C:\Users\Vaio\Downloads\xiaomi\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn_50db06715d\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn\images\prog_emmc_firehose_8937_ddr.mbn"
22:52:47: 455388 bytes transferred in 0.281000 seconds (1.5455MBps)
22:52:47: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
22:52:47: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
***** Working Folder:C:\Users\Vaio\AppData\Roaming\Qualcomm\QFIL\COMPORT_20
Download Fail:FireHose Fail:FHLoader Fail:The system cannot find the file specified
Finish Download
Image Search Path: C:\Users\Vaio\Downloads\xiaomi\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn_50db06715d\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn\images
RAWPROGRAM file path: C:\Users\Vaio\Downloads\xiaomi\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn_50db06715d\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn\images\rawprogram0.xml
PATCH file path:C:\Users\Vaio\Downloads\xiaomi\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn_50db06715d\pine_images_V11.0.5.0.PCMCNXM_20200304.0000.00_9.0_cn\images\patch0.xml

bad

H-Bricked Nokia 6.1 plus TA-1083, Bootloader Locked. Trying options QPST/QFIL

Hello team XDA,
I have Hard bricked Nokia 6.1 plus, It is connecting in Qualcomm 9008 Mode to my PC. I used the two test point Short method to make it. I think its also knwon as EDL mode.
Incidence: I was using "Scrcpy" tool for using my mobile on PC. It got freezed,turned off and not starting now.
What I have tried : I have tried OST LA 6.2.8 (the cracked one)in Emergency download Mode which did not work since bootloader is locked.
Error was: Sahara download failed.
Unfortunately Nokia service centers are closed. I heard they can download using their Secure credentials.
I tried Power+VOL Up button --- Did not work.
I tried Power + vol up+ vol dn --- Did not work.
What help i need: I saw tutorials on using QFIL/QPST to unbrick devices but they need certain XML and HEX files. I am unable to find them for my mobile, my knowledge is limited in this. Can anyone suggest where I can get those files.
Imp Questions :
1. Can QFIL / QPST unbrick my device since it is has locked bootloader?
2. If not is there any other tool/way to unbrick the device?
3. I am suspecting eMMC failure, Any ways to check it?
I know I wrote a lot, but want to make things very clear (as per my ability) for anyone willing to help. Kindly suggest I will try it immediately. Phone not in warranty, I dont mind about warranty and all.
Thanks in advance
Have a great day

just enter edl mode , update driver. Ost 6.0.4 software use... flash oreo firmware which before july security patch... flash with emergency mode
Sent from my TA-1054 using Tapatalk
---------- Post added at 04:23 PM ---------- Previous post was at 04:18 PM ----------
download this firmware https://drive.google.com/file/d/1iO1-54ZW986AZkmLva8DelPz_YS2pNTP/view?usp=drivesdk if still failed, send me logdata
Sent from my TA-1054 using Tapatalk

Thank you, I am trying this right away, and will update you.
Have a great day ahead.!
Regards.
EDIT:
1. as Mentioned my boot loader is locked.
2. OST 6.0.4 does not support OREO.
Not tried yet but just re-clarifying.

when u flash through edl mode its doesnt care about ur device lock or unlock ... and one things, i flashed several device like that...and 6.0.4 support oreo very well... so try it
Sent from my TA-1054 using Tapatalk

Sure, I am doing it now, will take some time to download firmware, once finished , I will update you.
Regards.

https://drive.google.com/file/d/1n91aYT9Di6_v4F3Wjlv8TjfeLc64AcYA/view?usp=drivesdk
ost 6.0.4
Sent from my TA-1054 using Tapatalk

Hi,
I downloaded the OST 6.0.4 from the drive link, installed and selected the
file " DRG-237B-0-00WW-B05.mlf" fromthe 7zip file downloaded from your link
It immediately gave the error:
"The update process failed"
Error: The Software version of the updater is out of date. please upgrade the updater and then try again.
I saw one forum to change some hex. Should i go for it? or go for OST 6.1.2? Please help.

TeamViewer id pass?
Sent from my TA-1054 using Tapatalk
---------- Post added at 10:33 AM ---------- Previous post was at 10:29 AM ----------
https://drive.google.com/file/d/1-P_L6f92HznkyKIF819a_m__dkKsNa6V/view?usp=drivesdk
download this
Sent from my TA-1054 using Tapatalk

No good network coverage here, If possible i will arrange in next few days.
Also this is what I did.
OST 6.1.2 : ERROR: FUNCTION :MAIN: 303 Uploading Image using Sahara protocol failed.
OST 6.2.8 (Given by you) : ERROR: FUNCTION :MAIN: 303 Uploading Image using Sahara protocol failed.
Code: 0xc3be
QPST:
2020-06-21 21:36:17.532 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Home\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2020-06-21 21:36:17.532 Sahara mappings:
2020-06-21 21:36:17.532 2: amss.mbn
2020-06-21 21:36:17.532 6: apps.mbn
2020-06-21 21:36:17.532 8: dsp1.mbn
2020-06-21 21:36:17.532 10: dbl.mbn
2020-06-21 21:36:17.532 11: osbl.mbn
2020-06-21 21:36:17.532 12: dsp2.mbn
2020-06-21 21:36:17.532 16: efs1.mbn
2020-06-21 21:36:17.532 17: efs2.mbn
2020-06-21 21:36:17.532 20: efs3.mbn
2020-06-21 21:36:17.532 21: sbl1.mbn
2020-06-21 21:36:17.532 22: sbl2.mbn
2020-06-21 21:36:17.532 23: rpm.mbn
2020-06-21 21:36:17.532 25: tz.mbn
2020-06-21 21:36:17.532 28: dsp3.mbn
2020-06-21 21:36:17.532 29: acdb.mbn
2020-06-21 21:36:17.532 30: wdt.mbn
2020-06-21 21:36:17.547 31: mba.mbn
2020-06-21 21:36:17.547 13: C:\Program Files (x86)\Qualcomm\QPST\bin\DRG-237B-0-00WW-B05.full\B2N-0-237B-prog_emmc_ufs_firehose_Sdm660_ddr.elf
2020-06-21 21:36:17.547
2020-06-21 21:36:17.547 21:36:17: ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
2020-06-21 21:36:17.547
2020-06-21 21:36:17.547 21:36:17: ERROR: function: sahara_main:983 Sahara protocol error
2020-06-21 21:36:17.547
2020-06-21 21:36:17.547 21:36:17: ERROR: function: main:320 Uploading Image using Sahara protocol failed
2020-06-21 21:36:17.547
2020-06-21 21:36:17.547
2020-06-21 21:36:17.547 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2020-06-21 21:36:17.547 Finish Download
Re-confirming: My (NOKIA 6.1 plus) TA-1083 is connected as " Qualcomm HS-USB QDLoader 9008
"

UPDATE:
I did the process multiple times now have new results:
OST 6.1.2 and 6.2.8
Error : TARGET SAID: 'WARN: Get Info failed to open 1 slot 0,
QFIL:
2020-06-21 22:43:08.954 22:42:49: INFO: TARGET SAID: 'Calling usb_al_bulk_set_zlp_mode(TRUE) since ZlpAwareHost='1''
2020-06-21 22:43:08.954 22:42:49: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
2020-06-21 22:43:08.954 22:42:49: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
2020-06-21 22:43:08.954 22:42:49: INFO: In handleProgram('B2N-0-237B-xbl.elf')
2020-06-21 22:43:08.954 22:42:49: INFO: Looking for file 'B2N-0-237B-xbl.elf'
2020-06-21 22:43:08.954 22:42:49: INFO: =======================================================
2020-06-21 22:43:08.954 22:42:49: INFO: {<program> FILE: 'C:\Program Files (x86)\Qualcomm\QPST\bin\DRG-237B-0-00WW-B05.full\B2N-0-237B-xbl.elf'}
2020-06-21 22:43:08.954 22:42:49: INFO: {<program> (2.44 MB) 5007 sectors needed at location 585728 on LUN 0}
2020-06-21 22:43:08.954 22:42:49: INFO: =======================================================
2020-06-21 22:43:08.954
2020-06-21 22:43:08.954
2020-06-21 22:43:08.970 22:43:08: INFO: TARGET SAID: 'ERROR: Failed to open the SDCC Device slot 0 partition 0'
2020-06-21 22:43:08.970
2020-06-21 22:43:08.970 22:43:08: INFO: TARGET SAID: 'ERROR: Failed to open the device 1 slot 0 partition 0'
2020-06-21 22:43:08.970
2020-06-21 22:43:08.970 22:43:08: INFO: TARGET SAID: 'INFO: Device type 1, slot 0, partition 0, error 0'
2020-06-21 22:43:08.970
2020-06-21 22:43:08.970 22:43:08: INFO: TARGET SAID: 'WARN: Get Info failed to open 1 slot 0, partition 0, error 0'
2020-06-21 22:43:08.970
2020-06-21 22:43:08.970 22:43:08: INFO: TARGET SAID: 'storage_device_get_num_partition_sectors FAILED!'
2020-06-21 22:43:08.970
2020-06-21 22:43:08.970 22:43:08: INFO: TARGET SAID: 'parseSectorValue could not handle start_sector value'

i also got sahara protocol error... ur device can be fix... dont panic ... if i can try, it will be nice
Sent from my TA-1054 using Tapatalk

sure, Check the mail through, which u shared OST 6.2.8.
Regards,

try now
Sent from my TA-1054 using Tapatalk

I did what was possible for me, I will share team viewer id and pass on your mail morning - IST

Yanky_NOOB said:
I did what was possible for me, I will share team viewer id and pass on your mail morning - IST
Click to expand...
Click to collapse
@Yanky_NOOB : I tried same steps as whatever you did and face exact same issues.
Guys I have the same problem too, Please share the details with me too so that I can try the same with my device too.
my post:
https://forum.xda-developers.com/no...s-edl-mode-emmc-failure-t4114507#post82899739

@mananarang
Have you confirmed that it is eMMC failure for you? if so how? i will also want to verify.
If so then then there is no point in trying to flash the rom's ? Am i correct as per my knowledge the ROM (android OS) goes to the eMMC portion.
If eMMC ha not failed then:
1. I know that flashing in EDL mode requires a signed ROM from Nokia, A non signed ROM will be rejected by edl since it checks for a Signing key, This can be done by NOKIA CARE as they have OST (USER & PASS)with Authorization to their servers who provide them signed ROM for flashing. Please correct me if any part of this is incorrect or you have some another idea to share.
Are the ROM's available in open domain Signed?
External boot seems to be an option as i saw on your thread but how? i am researching on it.
till then you can read this: https://alephsecurity.com/2018/01/22/qualcomm-edl-1/
Regards,

I'm wondering how did Scrcpy caused the hard-bricked.

heat the emmc little bit than try again
Sent from my TA-1054 using Tapatalk

Yeah @Volski_ i was using scrcpy for a month or so. And suddenly one morning as i was using my phone via scrcpy it freezed. Even hardware buttons, i disconnected the Mobile by the time it was off on its own, after that i tried turning it on..it was not so after connecting to pc i got the 9008 mode.
Surprising but sadly true...

Yeah @Volski_ i was using scrcpy for a month or so. And suddenly one morning as i was using my phone via scrcpy it freezed. Even hardware buttons, i disconnected the Mobile by the time it was off on its own, after that i tried turning it on..it was not so after connecting to pc i got the 9008 mode.
Surprising but sadly true...