Develop Bugs

[Q] Help: Heimdall flashing CWM Recovery on Linux error.

has any of you guys successfully used Heimdall to flash CWM Recovery? im trying to flash CWM Recovery-6.0.4.5 on a a very old samsung w gt-I8150 model and keep getting the same error(in download mode);
$ Initialising connection...
$ Detecting device...
$ Claiming interface...
$ Attempt failed. Detaching driver...
$ Claiming interface again...
$ Setting up interface...
$ libusb: error [op_set_interface] setintf failed error -1 errno 71
$ ERROR: Setting up interface failed!
i've sucesfuly conected my phone using:
$ adb devices
and no issues with "adb push" command but when i reboot the phone to "download mode" the adb seems to lost connection to the phone, or am i doing it all wrong here?
this is how i tried to flash using Heimdall:
$ sudo heimdall flash --recovery recovery.img --no-reboot
here's Heimdall debug output:
[timestamp] [threadID] facility level [function call] <message>
--------------------------------------------------------------------------------
[ 0.006502] [00002215] libusb: debug [libusb_get_device_list]
[ 0.006548] [00002215] libusb: debug [discovered_devs_append] need to increase capacity
[ 0.006571] [00002215] libusb: debug [libusb_get_device_descriptor]
[ 0.006587] [00002215] libusb: debug [libusb_open] open 2.29
[ 0.006620] [00002215] libusb: debug [usbi_add_pollfd] add fd 11 events 4
[ 0.006643] [00002215] libusb: debug [libusb_get_device_descriptor]
[ 0.006657] [00002215] libusb: debug [libusb_get_config_descriptor] index 0
Claiming interface...
[ 0.006686] [00002215] libusb: debug [libusb_claim_interface] interface 1
Setting up interface...
[ 0.006730] [00002215] libusb: debug [libusb_set_interface_alt_setting] interface 1 altsetting 0
[ 0.010729] [00002215] libusb: error [op_set_interface] setintf failed error -1 errno 71
ERROR: Setting up interface failed!
Releasing device interface...
[ 0.010756] [00002215] libusb: debug [libusb_release_interface] interface 1
[ 0.010779] [00002215] libusb: debug [libusb_close]
[ 0.010790] [00002215] libusb: debug [usbi_remove_pollfd] remove fd 11
[ 0.010804] [00002215] libusb: debug [libusb_exit]
[ 0.010809] [00002215] libusb: debug [libusb_exit] destroying default context

dude127 said:
has any of you guys successfully used Heimdall to flash CWM Recovery? im trying to flash CWM Recovery-6.0.4.5 on a a very old samsung w gt-I8150 model and keep getting the same error(in download mode);
[...]
Click to expand...
Click to collapse
For as far as I know, Heimdall works only with Galaxy S phones. For Ancora (aka Samsung Galaxy W), use ODIN 4.43 or 4.44 on a Windows machine. If your phone is rooted, you can also install CWM Recovery 6.0.4.5 (by flashing the recovery.img file) using a software called Flashify (app downloadable from Google Play Store).

@arsradu is right, this phone is slightly older/different and uses Odin Multi Downloader's .OPS files instead of the Heimdall/Odin3 compatible .PIT files.

Problem SOLVED!

dude127 said:
Problem SOLVED!
Click to expand...
Click to collapse
Good to hear that. Would you mind sharing the solution?

arsradu said:
Good to hear that. Would you mind sharing the solution?
Click to expand...
Click to collapse
the problem was Heimdall doesnt support GT-I850. so what i did was i downloaded one of the root terminal cleints and dd'ed the recovery.img to mmcblk0p13 and that was pretty much it. reboot to recovery and CWM recovery installed now im using CMod 10.2 with PurePerformanceX script oh man my old and aging phone feels like waaaaay snappier than i first bought it lol

How to do I exactly 'dd' the recovery.img ?
dude127 said:
the problem was Heimdall doesnt support GT-I850. so what i did was i downloaded one of the root terminal cleints and dd'ed the recovery.img to mmcblk0p13 and that was pretty much it. reboot to recovery and CWM recovery installed now im using CMod 10.2 with PurePerformanceX script oh man my old and aging phone feels like waaaaay snappier than i first bought it lol
Click to expand...
Click to collapse
I know the thread is rather old, but I am having the exact same problem with an Samsung S plus i9001... Therefore, I 'd like to ask dude127 if you could share the commands you used to run dd to overwrite mmcblk0p13? c.f. http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001#Flashing_in_Linux.2FMac
1. Put phone into bootloader mode.
2. $ sudo dd if=recovery.img of=/dev/block/mmcblk0p13 ?
With "root terminal client" you talk about an app? Why would I need it?
All this looks quiet dangerous to do. So, I would really appreciate your help/expertise here.
Thanks!
digisus

ERROR: HRESULT = 0x8024a110

Can't send update to my Lumia build 10.10.10586.29 i have always
Code:
(IUTool Version: 11:52:10/Feb 7 2014)
Log file: C:\Users\Thierry\AppData\Local\Temp\IUTool-{299338D7-E9AD-4D02-BD74-B341894FDEEF}.etl
[1] Started device 6ea0f2436b51fa6d88d745b2c8dde3d3
[1] Transferring files started
[1] Transferring files complete: 2 files
[1] Update started
[1] Installation failed (HRESULT = 0x8024a110)
[1] Failed (0x8024a110)
ERROR: 0x8024a110
Command failed. (HRESULT = 0x8024a110)

Im trying to deploy old nokia.service_ndtksvc.generic.spkg.cab
0x80188306
E_FILE_COLLISION
More than one package targeted for the same partition contained the same file.

titi66200 said:
Can't send update to my Lumia build 10.10.10586.29 i have always
Code:
(IUTool Version: 11:52:10/Feb 7 2014)
Log file: C:\Users\Thierry\AppData\Local\Temp\IUTool-{299338D7-E9AD-4D02-BD74-B341894FDEEF}.etl
[1] Started device 6ea0f2436b51fa6d88d745b2c8dde3d3
[1] Transferring files started
[1] Transferring files complete: 2 files
[1] Update started
[1] Installation failed (HRESULT = 0x8024a110)
[1] Failed (0x8024a110)
ERROR: 0x8024a110
Command failed. (HRESULT = 0x8024a110)
Click to expand...
Click to collapse
Astoria's dead. Get over it.

Nokia lumia 822 - error : Unable to find boot able device , press any key to shutdown

Hello ,
I have a Nokia Lumia 822 with me here , and since 2 days i am trying to fix it .
ERROR ( Unable to find a bootable device : press any key to shutdown )
I have already tried WDRT , WP Internals , doesn't work ( WDRT -Unkown Error , WP Internals gives security Header error ).
With Thor2 , can't flash FFU file . ( I got the FFU from WDRT downloaded RM-845 package in C:/ProgramData)
It's give me an Error RDC file not found. I tried flashing partitions separately but Nothing works until i have this RDC file.
Now where do i get it ? I have dumped FFU via Thor2 , and i do have PLAT , GPT , MAIN OS , MMOS , UEFI , TZ . I dont see any RDC named file here.
Kindly help me any one here.
P.S , I have Following list of files.
WINSECAPP
UEFI
SBL1
SBL2
SBL3
RPM
PLAT
MAIN OS
MMOS
GPT
GPT0
GPT1
EFIESP
DATA
just missing the RDC file and HEX i guess.

I don't know anything about this, but this seems relevant. https://forum.xda-developers.com/chef-central/windows-phone-7/replace-rdc-t3277506/page1
Sent from my Moto G (5S) Plus using Tapatalk

RoshanX said:
Hello ,
Kindly help me any one here.
Click to expand...
Click to collapse
Try to install EFIESP.bin partition from another phone, using WPinternals.
I unbricked lumia 530 flashing the EFIESP.bin from custom ROM of lumia 830.
Unfortunately, after, the phone cant upgrade to windows mobile 10 or hard reset. Sad face appear. Is stuck on wp 8.1.

augustinionut said:
Try to install EFIESP.bin partition from another phone, using WPinternals.
I unbricked lumia 530 flashing the EFIESP.bin from custom ROM of lumia 830.
Unfortunately, after, the phone cant upgrade to windows mobile 10 or hard reset. Sad face appear. Is stuck on wp 8.1.
Click to expand...
Click to collapse
Thank you for your participation , I tried it it , and also tried flashing UEFI paritition , but it gives me an error(see below)
[21:44:40.362] D_MSG : Initiating flash of partition image operations
[21:44:40.362] D_MSG : WinUSB in use.
[21:44:40.380] D_MSG : Using programming of partition image method
[21:44:40.380] D_MSG : isDeviceInNcsdMode
[21:44:40.381] D_MSG : isDeviceInNcsdMode is false
[21:44:40.381] D_MSG : Detecting UEFI responder
[21:44:40.382] D_MSG : HELLO success
[21:44:40.474] D_MSG : Lumia Flash detected
[21:44:40.474] D_MSG : Protocol version 1.18 Implementation version 2.2
[21:44:40.475] D_MSG : Disable timeouts
[21:44:40.476] D_MSG : Get flashing parameters
[21:44:40.567] D_MSG : Lumia Flash detected
[21:44:40.568] D_MSG : Protocol version 1.18 Implementation version 2.2
[21:44:40.568] D_MSG : Size of one transfer is 2363392
[21:44:40.568] D_MSG : Size of buffer is 2359296
[21:44:40.568] D_MSG : Number of eMMC sectors: 30535680
[21:44:40.568] D_MSG : Platform ID of device: Nokia.MSM8960.P5219.3.2.1
[21:44:40.568] D_MSG : Async protocol version: 01
[21:44:40.569] D_MSG : Security info:
[21:44:40.569] D_MSG : Platform secure boot enabled
[21:44:40.569] D_MSG : Secure FFU enabled
[21:44:40.569] D_MSG : JTAG eFuse blown
[21:44:40.569] D_MSG : RDC not found
[21:44:40.569] D_MSG : Authentication not done
[21:44:40.569] D_MSG : UEFI secure boot enabled
[21:44:40.570] D_MSG : SHK enabled
[21:44:40.570] D_MSG : Device supports FFU protocols: 0031
[21:44:40.571] D_ERR : getGpt failed. Error code 12 h
[21:44:40.572] D_ERR : Cannot flash partition image. Write the RDC into the device or use open/RnD HW & SW
[21:44:40.584] D_MSG : Operation took about 0.00 seconds.
[21:44:40.585] D_ERR : THOR2 1.8.2.18 exited with error code 84214 (0x148F6)

I said WPinternals. Capisci?
Anyway, be carefull to not accidentaly click OK when windows will ask to format partition, if you put your phone in mass storage mode. I bricked lumia 640xl that way.

augustinionut said:
I said WPinternals. Capisci?
Anyway, be carefull to not accidentaly click OK when windows will ask to format partition, if you put your phone in mass storage mode. I bricked lumia 640xl that way.
Click to expand...
Click to collapse
Didn't work either. i double checked.
What i need over here i guess is either the RDC , or either the HEX file.
I have seen people generating msimage.mbn via GPT dump
But how do i get the hex file ?! or the RDC ?

WPinternals. Is this? https://forum.xda-developers.com/windows-10-mobile/windows-phone-internals-2-2-t3713157

h815 no download no fastboot only black screen after vibration

my phone is h815tr usu unlocked not international
i have tried all the roms
today i want to try stock rom
http://leech.binbash.rocks:8008/stock/LG/h815/29a/LG-H815_Official_v29A_keepsTWRP-LAF.zip
i think i chose the right rom because i had been done USU METOD 6 months ago
So i have been using different roms about 6 months so i tihnk i know what to flash or nor to flash
after flashing the rom in the link now my phone is bricked
i know the button combinations for fastboot for download mode
now my phone only vibrates than goes black screen
i tried usb 3 and usb 2 ports in my pc
please help

addition: also if i take out the battery and connect to to the pc via usb
battery icon with a question mark shows on the screen
also i have tried this metod --> https://forum.xda-developers.com/g4/general/guide-proper-h815-unbrick-qfil-files-t3709212
1. Download this archive. --> yes i downlaoded https://androidfilehost.com/?fid=1322778262904000036
2. Install every driver/runtime and QPST from the "software_drivers" folder (do not install virtualhere_client files, those are not needed for unbricking) "qhsusb_dload" driver cant installed from windows device manager. so i used this driver --> http://dl.drp.su/driverpacks/repack/Telephone/Quectel/All10x86x64/Quectel-All10x86x64-drp.zip because no driver suits with the hardware
3. Extract "flashing" folder.
3. If your device is not in 9008 mode already, force boot to it (tutorial in "stuff" folder in archive, or look up LG G4 EMMC shorting)
It should show up something like this when properly in 9008 mode (QHUSB_BULK in device manager means drivers are not properly installed, try again)
4. Once your device is in 9008 mode, Open QFIL, disconnect it from the computer, remove the battery and connect it back to the computer with battery removed.
5. Proceed to select the files from the "flashing" folder you extracted in QFIL, then press the "Download" button.
also i did this
UsU devices have to replace files from the UsU unlock zip:
aboot_UsU.img (UsU unlock zip) --> flashing/emmc_appsboot.mbn
laf_UsU.img (UsU unlock zip) --> flashing/laf.img
rawres_UsU.img (UsU unlock zip) --> flashing/raw_resources.img
than here is the log
Validating Application Configuration
Load APP Configuration
COM:3
SAHARA:True
SAHARA:\indirilenler\G4-h815_fullunbrick_working_7a3ae5809224d\h815_full_working_7a3ae5809224d\flashing\prog_emmc_firehose_8992_lite.mbn
SEARCHPATH:\indirilenler\G4-h815_fullunbrick_working_7a3ae5809224d\h815_full_working_7a3ae5809224d\flashing
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
READBACKMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
Load ARG Configuration
Process Index:0
Validating Download Configuration
Image Search Path: D:\indirilenler\G4-h815_fullunbrick_working_7a3ae5809224d\h815_full_working_7a3ae5809224d\flashing
RAWPROGRAM file path: D:\indirilenler\G4-h815_fullunbrick_working_7a3ae5809224d\h815_full_working_7a3ae5809224d\flashing\rawprogram0.xml
PATCH file path:\indirilenler\G4-h815_fullunbrick_working_7a3ae5809224d\h815_full_working_7a3ae5809224d\flashing\patch0.xml
Programmer Path:\indirilenler\G4-h815_fullunbrick_working_7a3ae5809224d\h815_full_working_7a3ae5809224d\flashing\prog_emmc_firehose_8992_lite.mbn

mkrts said:
my phone is h815tr usu unlocked not international
i have tried all the roms
today i want to try stock rom
http://leech.binbash.rocks:8008/stock/LG/h815/29a/LG-H815_Official_v29A_keepsTWRP-LAF.zip
i think i chose the right rom because i had been done USU METOD 6 months ago
So i have been using different roms about 6 months so i tihnk i know what to flash or nor to flash
after flashing the rom in the link now my phone is bricked
i know the button combinations for fastboot for download mode
now my phone only vibrates than goes black screen
i tried usb 3 and usb 2 ports in my pc
please help
Click to expand...
Click to collapse
as already answered in your duplicated post in the UsU thread: that was the wrong file. The UsU FAQ lists the correct link to the nougat build made for UsU'd devices. Btw the download site where you got it from has at the top in RED colors a warning that this is not for UsU'd devices. ok anyways, next time read first.
so what state is your phone now when you have the battery in? Get it recognized by QFIL? attach a screenshot when it is connected.
When it is recognized: what happens when you press the download button? the log shows nothing or you have not copied the full log. scroll down to the end and copy everything.
.-

i recorded a screen video
https://www.youtube.com/watch?v=tSOZyGRQucU
sorry for posting in usu thread. can i delete my post from usu thread ?

mkrts said:
i recorded a screen video
https://www.youtube.com/watch?v=tSOZyGRQucU
Click to expand...
Click to collapse
pls when I say screenshot I do not wanna watch a 6min video.
anyways I saw that it was detected and so it should work.
you saved the log but didnt uploaded it but according to the error I saw do this:
prepare everything up to the point where you would click on "download" but do not click it yet.
now disconnect the phone and take out battery. put battery back in and connect it to the PC again. Immediately after QFIL detects the phone press download.
if that still fails share the full log
.-

steadfasterX said:
pls when I say screenshot I do not wanna watch a 6min video.
anyways I saw that it was detected and so it should work.
you saved the log but didnt uploaded it but according to the error I saw do this:
prepare everything up to the point where you would click on "download" but do not click it yet.
now disconnect the phone and take out battery. put battery back in and connect it to the PC again. Immediately after QFIL detects the phone press download.
if that still fails share the full log
.-
Click to expand...
Click to collapse
in 1. step the battery is taken out already isnt it ?
i have been trying about 1 hour only two times connection established.
and i press download there is no success
what do you mean about full log i just click "save log"
Validating Application Configuration
Load APP Configuration
COM:-1
SAHARA:True
SAHARA:\indirilenler\G4-h815_fullunbrick_working_7a3ae5809224d\h815_full_working_7a3ae5809224d\flashing\prog_emmc_firehose_8992_lite.mbn
SEARCHPATH:\indirilenler\G4-h815_fullunbrick_working_7a3ae5809224d\h815_full_working_7a3ae5809224d\flashing
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
READBACKMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
Load ARG Configuration
Process Index:0
Validating Download Configuration
Image Search Path: D:\indirilenler\G4-h815_fullunbrick_working_7a3ae5809224d\h815_full_working_7a3ae5809224d\flashing
RAWPROGRAM file path: D:\indirilenler\G4-h815_fullunbrick_working_7a3ae5809224d\h815_full_working_7a3ae5809224d\flashing\rawprogram0.xml
PATCH file path:\indirilenler\G4-h815_fullunbrick_working_7a3ae5809224d\h815_full_working_7a3ae5809224d\flashing\patch0.xml
Programmer Path:\indirilenler\G4-h815_fullunbrick_working_7a3ae5809224d\h815_full_working_7a3ae5809224d\flashing\prog_emmc_firehose_8992_lite.mbn
Image Search Path: D:\indirilenler\G4-h815_fullunbrick_working_7a3ae5809224d\h815_full_working_7a3ae5809224d\flashing
RAWPROGRAM file path: D:\indirilenler\G4-h815_fullunbrick_working_7a3ae5809224d\h815_full_working_7a3ae5809224d\flashing\rawprogram0.xml
PATCH file path:\indirilenler\G4-h815_fullunbrick_working_7a3ae5809224d\h815_full_working_7a3ae5809224d\flashing\patch0.xml
Start Download
COM Port number:3
Switch To EDL
Download Fail:Failed to Switch to Emergency Download mode
Download Fail:Switch To EDL FailFireHose Fail
Finish Download

@steadfasterX first of all thank you for all your help
i think now you are busy
i just want to ask you can we repair my phone at last ? what is the chance ?
i am waiting your support patiencely

@steadfasterX did you forget this post ?

mkrts said:
@steadfasterX did you forget this post ?
Click to expand...
Click to collapse
no but I have a RL and I do not get paid for doing support here. somehow i have to pay my bills right?
so either you are too slow when following my instructions or you do not follow it strictly or if you are sure both is fine it will not work that way.
sometimes the auto 9008 mode can behave weird and does not allow flashing that way. the only option is to either using the sdcard method to boot from it or using the debug pins to enter a forced 9008 mode. the debug pin method is extremely hard in your case though as your device turns already in 9008 mode and if you never did it before you will not know if you do it right.
so imho you should give the sdcard unbrick a try which should work fine as long as your device gets into 9008 mode directly.
see my sig for a link

thank you i will try

i cant see sd card name ?
[[email protected] ~]$ sudo dmesg -c >> /dev/null
[sudo] password for android:
[[email protected] ~]$ dmesg
[ 900.775546] audit: type=1130 audit(1576496069.537:51): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 900.775549] audit: type=1131 audit(1576496069.537:52): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 901.371072] usb 1-1: new full-speed USB device number 4 using ohci-pci
[ 901.849709] usb 1-1: config 1 interface 0 altsetting 0 endpoint 0x81 has invalid maxpacket 512, setting to 64
[ 901.849719] usb 1-1: config 1 interface 0 altsetting 0 endpoint 0x2 has invalid maxpacket 512, setting to 64
[ 901.880804] usb 1-1: New USB device found, idVendor=14cd, idProduct=125d, bcdDevice= 1.00
[ 901.880812] usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=2
[ 901.880818] usb 1-1: Product: Mass Storage Device
[ 901.880823] usb 1-1: Manufacturer: Generic
[ 901.880828] usb 1-1: SerialNumber: 125D20140310
[ 901.895975] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 901.900030] scsi host2: usb-storage 1-1:1.0
[ 902.950269] scsi 2:0:0:0: Direct-Access Mass Storage Device PQ: 0 ANSI: 0 CCS
[ 902.975335] sd 2:0:0:0: [sdb] 62914560 512-byte logical blocks: (32.2 GB/30.0 GiB)
[ 902.989068] sd 2:0:0:0: [sdb] Write Protect is off
[ 902.989071] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 903.004691] sd 2:0:0:0: [sdb] No Caching mode page found
[ 903.004695] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 903.122278] sdb: sdb1
[ 903.218590] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[[email protected] ~]$

https://forum.xda-developers.com/showpost.php?p=75770329&postcount=527
i am using fwul disk images. salt version is under 3.5
are there any image contains salt upper 3.5 ?
also i cant see sd card name

''TID should not be 0'' error while flashing using SMT mode..

I accidently messed up the dynamic partition now the boot menu stuck at "SMT download failed' and whenever I try to use SMT mode in MSM it gets stuck in ''TID should not be 0" screen, Do anyone know the fix of it, any help is appreciated.
tried with MSM hotdogb_14_O.22_210127 and hotdogb_14_O.05_191012_repack (both are of oos10).
OOS10 boots fine but with the SMT error boot screen.
OOS11 seems impossible to boot
The error screen image is attached below (Not my image but it shows exactly like that)
log:
IA V1.0
FCL V1.0
========================================================
MetadataVersion=2,CryptVersion=1,m_bIsPackImage=1
Project Name: 18865
Image Version: hotdogb_14_O.05_191012
Skip SHA256 Check: No
HW CHK: No
RF CHK: No
PRJ CHK: No
MDL CHK: Yes
Tool version verified! (V5.0.15)
project 18865 not support boot mode feature
project 18865 enable fuse
MVL V1.2
[1] dwMajorVersion=6,dwMinorVersion=2,is_win7_system=0te123
Use Lite Firehose
Use DDR Firehose
Dialog selection = 4
Device Arrival: \\?\USB#VID_05C6&PID_9008#5&32cc216f&0&4#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[2] Set device as UFS
[2] [CSerialCommHelper] Buf: 0 (21/10)
[2] [CSerialCommHelper] No data in buffer to be sent 0
[2] [SP][193] Check cmd done status failed. 1
[2] [SP][206] Reset Sahara
[2] UFS Inquiry Command Output: SAMSUNG KLUEG8UHDB-C2D1 0400
[2] UFS info Vendor = samsung, TotalLogicalBlocks = 499892224
[2] EmmcSizeInGB = 238.367188, TotalLogicalBlocks = 499892224
[2] Memory size:256G
[2] provision file: samsung
Device Remove: \\?\USB#VID_05C6&PID_9008#5&32cc216f&0&4#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
Device Arrival: \\?\USB#VID_05C6&PID_9008#5&32cc216f&0&4#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[2] [CSerialCommHelper] Buf: 0 (14/10)
[2] [CSerialCommHelper] No data in buffer to be sent 0
[2] [SP][193] Check cmd done status failed. 1
[2] [SP][206] Reset Sahara
[2] UFS Inquiry Command Output: SAMSUNG KLUEG8UHDB-C2D1 0400
[2] UFS info Vendor = samsung, TotalLogicalBlocks = 499892224
[2] EmmcSizeInGB = 238.367188, TotalLogicalBlocks = 499892224
[2] Memory size:256G
[2] [Firehose] HwVersion = 14
[2] [Firehose] RfVersion = 3
[2] [Firehose] PrjVersion = 4
[2] HANDSET_TYPE_256G:
[2] Target ID should not be default in SMT mode
Device Remove: \\?\USB#VID_05C6&PID_9008#5&32cc216f&0&4#{86e0d1e0-8089-11d0-9ce4-08003e301f73}