yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] Fstop:
I root & installed TWRP and Magjsk instead of SuperSu because TWRP would only boot in Russian, now the phone reboots logo & into TWRP in English but won't boot into system. [MENTION=6466472]Miss Montage[/MENTION] can you tell me why I can't use fastboot & ADB tools to restore Doogee Mix 6+64GB? I turn off the Device then connect it to PC and it boots to Logo then TWRP. Gong to try Download Logo test before device reboots into TWRP.

I have no problem communicating with the Device via Fastboot or ADB - I've use fastboot & ADB to restore my OnePlus X ??? I couldn't find any fastboot & ADB tutorials for restoring Doogee Mix 6+64GB - its been 2 -3 weeks.
[Upgrading, Modifying and Unlocking] Miss Montage:
The only MediaTek Device I owned was a UMi Hammer. When I tried to flash recovery or system image I got the response "(remote) command not allowed". You can try your luck. I heard of (custom) ROMs which are configured to boot when a USB connection is established. That might be reason why your Doogee Mix 6+64 cannot stay in "download mode". I assume that you cannot remove the battery?
[Upgrading, Modifying and Unlocking] Fstop:
I found no custom roms for Doogie Mix which makes me regret installing an unofficial TWRP and rooting, thank you for your help.

fastboot answer: System.img is too big 3.1GB to flash using:

$fastboot flash system system.img
[Upgrading, Modifying and Unlocking] Fstop:
Trying Recovery with Fastboot & ADB

Remote- command allowed but system.img is too large for fastboot. Trying to go back to twrp to copy recovery image files on to internal SDcard , then flash back to stock recovery & see if update or recovery options will accept them :crying:
[Upgrading, Modifying and Unlocking] Fstop:
Does anyone know if QT5webkit will work with SP Flash Tool?
[Upgrading, Modifying and Unlocking] Fstop:
1June2018

Created the Black List file & added the 2 lines suggested.

Changed from Download Only to Uprgrade Firmware

Option: With the Battery in -

Phone Power Off Connect USB After Hitting Download Button

But then the Battery comes on within a minute and I get the "Status Change Error" battery icon comes on changing this Devices Status.
[Upgrading, Modifying and Unlocking] ady:
Soooo no one has run into "Not implemented" MSP Erroe 0x0 thing on Ubuntu 18.04?
[Upgrading, Modifying and Unlocking] Fstop:
[MENTION=265315]ady[/MENTION], Didn't get that far on Ubuntu, do you have this configuration file /80-persistent-usb.rules?

Ran Live Ubuntu 16.04.1 & when I got to gedit /etc/udev/rules.d/ there is no /80-persistent-usb.rules. yes I did sudo apt installed libusb-dev? Error: "The file or directory doesn't exist".

June24: update, used vi instead of gedit which opens a blank: /etc/udev/rules.d/80-persistent-usb.rules because 80-persistent-usb.rules doesn't exist. Copy and pasted line:

SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0e8d", ATTR{idProduct}=="*"

- into body of this empty file not yet created.

:wq command

- will save the line & create this file: /etc/udev/rules.d/80-persistent-usb.rules

Same thing with this file: /etc/udev/rules.d/20-mm-blacklist-mtk.rules - this did not solve the changing status problem - that keeps SP_Flash Tool from working.

Created a persistent USB Ubuntu14.04.5-64 followed the excellent tutorial again. Tried different options: 1) with 2)without & 3) Auto detect battery. I tried the button + & - while connecting the usb cable to PC.

Finally today I was able to engage Doogee Mix with

SP_Flash Tool used: + volume button while connecting USB cable and holding it till the Red Line Started-

in combination with No. 3. Auto detect battery - option, and the Upgrade Option.

Made sure device power was Off

Started Download

Then connected the USB Cable to PC while holding the + Volume carefully.

Took me a month+ to restore Doogee Mix 6+64GB that has no LTE for USA users.

Thanks @ Miss Montage for telling me what wasn't wrong in my output and all the tutorials she mentioned plus all the ones I got bits and pieces of info to get the device unbricked.
[Upgrading, Modifying and Unlocking] kenshinta:
Are there extra steps for ubuntu 18.04? Done everything right except for non-root running.
[Upgrading, Modifying and Unlocking] lorikeet:
Yes. I am running SP flash as non-root on Ubuntu 14. I had to add the user to dialout group.
[Upgrading, Modifying and Unlocking] militiaOfDeath:
Has anyone made this work from terminal in Ubuntu 18.04? If I try ./flash_tool or ./flash_tool.sh I only get the message "flash_tool: cannot connect to X server", no matter if running as root or not. If I double click icon in file explorer it starts as expected, but then I always get an error about not being able to open the port when trying e.g. a read back.

Update; A reboot fixed the issue, so far works like expected.
[Upgrading, Modifying and Unlocking] zvolsky:
Java and kernel versions

I have had serious problems with Download and especially with Format in ./flash_tool on my Debian Testing machine.

I received many errors and googling them leads to no results or to the misleading results.

The solution was:

- use Java 8 instead of the newer one (download/extract from Oracle, export PATH=...../java8/bin:$PATH, check the version: java -version)

If errors will not disapear with J8, then try older kernel.

My problems were on current 4.17 version, so do something like:

apt install linux-image-4.9.0-7-amd64 linux-headers-4.9.0-7-amd64 ; update-grub

and maybe boot with Shift. I don't know how to do it exactly, I have used the 2-nd machine with 4.9.0-5.

PS: MT6589 is supported in Flash Tool 5.1724 and older.
[Upgrading, Modifying and Unlocking] MK404:
how to fix ?

mskopi@mskopi-Aspire-E5-475G:~$ sudo gedit /etc/udev/rules.d/20-mm-blacklist-mtk.rules

[sudo] password for mskopi:

** (gedit:6189): WARNING **: 13:43:32.358: Set document metadata failed: Setting attribute metadata::gedit-spell-language not supported

** (gedit:6189): WARNING **: 13:43:32.359: Set document metadata failed: Setting attribute metadata::gedit-encoding not supported

** (gedit:6189): WARNING **: 13:55:43.540: Set document metadata failed: Setting attribute metadata::gedit-position not supported
[Upgrading, Modifying and Unlocking] Miss Montage:
Does gedit normally work on your PC? Which Linux version are you using?
[Upgrading, Modifying and Unlocking] mayur badam:
How to install this on Ubuntu 32 bit. This tutorial doesn't work for 32bit. Are there any sites for tutorial on installing on 32-bit Ubuntu 18.04
[Upgrading, Modifying and Unlocking] Miss Montage:
There is no tool for 32-bit. Why don't you upgrade your system to 64 bit?
[Upgrading, Modifying and Unlocking] Bomassy:
Hello,

I get always the Error 2004.

./flash_toolQObject::moveToThread: Cannot move objects with a parent

support_dl_cert_to_storage: 0

Connecting to BROM...

Scanning USB port...

Search usb, timeout set as 3600000 ms

add@/devices/pci0000:00/0000:00:14.0/usb3/3-1

add@/devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0

add@/devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/tty/ttyACM0

vid is 0e8d

device vid = 0e8d

pid is 0003

device pid = 0003

com portName is: /dev/ttyACM0

Total wait time = -1542300868.000000

USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)

USB port detected: /dev/ttyACM0

BROM connected

Downloading & Connecting to DA...

connect DA end stage: 2, enable DRAM in 1st DA: 0

COM port is open. Trying to sync with the target...

Failed to Connect DA: S_BROM_DOWNLOAD_DA_FAIL(2004)

Disconnect!

BROM Exception! ( ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004)

[H/W] Fail to download DA to baseband chip's internal SRAM!

[HINT]:

1. There's an cable communication problem between FlashTool and BootROM.

2. Target might be shutdown unexpectedly or target lost power supply.

[ACTION]

1. Try again.

2. Proceed H/W checking in download cable and target side com port.

3. Monitor if power-drop occured in target side.)((ConnectDA,../../../flashtool/Conn/Connection.cpp,146))

Can anyone help me please?
[Upgrading, Modifying and Unlocking] gerstavros:
This is normally a problem of nand flash. But, did you run as root?
[Upgrading, Modifying and Unlocking] Bomassy:
Yes It was running as root.

First I used Windows for SP Flashtool, but there was this Error 2004. Because of this i used Linux. But now there is the same error. I dont know how to fix ist. :(
[Upgrading, Modifying and Unlocking] Goksu:
libpng

I have been trying to port a solution to the libpng12 error here but have not been able to due to having less than 10 posts. basically do a search for the deb to add to the source file as libpng12 support has been dropped since 16.10 in ubuntu in favor of libpng16.
[Upgrading, Modifying and Unlocking] dFrem:
UPD: Latest *buntu Linux

You might need to do the following:

Happy flashing!
[Upgrading, Modifying and Unlocking] Micchael3345:
Hi, thanks for you help to install this, i have only one problem and it's that the red bar appears and get stuck there, at the right down corner i can read this "/dev/ttyACM0". i don't know what's happening :S.
[Upgrading, Modifying and Unlocking] Ateo1961:
This one works on my Ubuntu 18.10.
[Upgrading, Modifying and Unlocking] Ekki12:
When i try to run ./flash_tool i get "Floating point exception" message (kde neon)

Any suggestion??
[Upgrading, Modifying and Unlocking] DrSliperyFists:
this is what happens after running ./flash_tool

libpng warning: iCCP: known incorrect sRGB profile

X Error: BadAccess (attempt to access private resource denied) 10

Extension: 130 (MIT-SHM)

Minor opcode: 1 (X_ShmAttach)

Resource id: 0x3400002

X Error: BadShmSeg (invalid shared segment parameter) 128

Extension: 130 (MIT-SHM)

Minor opcode: 5 (X_ShmCreatePixmap)

Resource id: 0x340000b

X Error: BadDrawable (invalid Pixmap or Window parameter) 9

Major opcode: 62 (X_CopyArea)

Resource id: 0x340000c

libpng warning: iCCP: known incorrect sRGB profile

QObject::moveToThread: Cannot move objects with a parent

X Error: BadDrawable (invalid Pixmap or Window parameter) 9

Major opcode: 62 (X_CopyArea)

Resource id: 0x340000c

X Error: BadAccess (attempt to access private resource denied) 10

Extension: 130 (MIT-SHM)

Minor opcode: 1 (X_ShmAttach)

Resource id: 0x13f

X Error: BadShmSeg (invalid shared segment parameter) 128

Extension: 130 (MIT-SHM)

Minor opcode: 5 (X_ShmCreatePixmap)

Resource id: 0x3400027

X Error: BadDrawable (invalid Pixmap or Window parameter) 9

Major opcode: 62 (X_CopyArea)

Resource id: 0x3400028

X Error: BadDrawable (invalid Pixmap or Window parameter) 9

Major opcode: 62 (X_CopyArea)

Resource id: 0x3400028

X Error: BadDrawable (invalid Pixmap or Window parameter) 9

Major opcode: 62 (X_CopyArea)

Resource id: 0x3400028

X Error: BadDrawable (invalid Pixmap or Window parameter) 9

Major opcode: 62 (X_CopyArea)

Resource id: 0x3400028

X Error: BadDrawable (invalid Pixmap or Window parameter) 9

Major opcode: 62 (X_CopyArea)

Resource id: 0x3400028

X Error: BadDrawable (invalid Pixmap or Window parameter) 9

Major opcode: 62 (X_CopyArea)

Resource id: 0x3400028

X Error: BadDrawable (invalid Pixmap or Window parameter) 9

Major opcode: 62 (X_CopyArea)

Resource id: 0x3400028

comboTimeout index(3) saved.

X Error: BadPixmap (invalid Pixmap parameter) 4

Major opcode: 54 (X_FreePixmap)

Resource id: 0x3400028

X Error: BadShmSeg (invalid shared segment parameter) 128

Extension: 130 (MIT-SHM)

Minor opcode: 2 (X_ShmDetach)

Resource id: 0x3400027

X Error: BadPixmap (invalid Pixmap parameter) 4

Major opcode: 54 (X_FreePixmap)

Resource id: 0x340000c

X Error: BadShmSeg (invalid shared segment parameter) 128

Extension: 130 (MIT-SHM)

Minor opcode: 2 (X_ShmDetach)

Resource id: 0x340000b
[Upgrading, Modifying and Unlocking] Miss Montage:
The error messages hint to conflicts with x-server (graphics). Please try a double click on flash_tool.

And please do not full quote the op, it clutters the thread.
[Upgrading, Modifying and Unlocking] scheichxda:
executing DADownloadAll... and nothing more

Hello

I am trying to recover a "Head Unit with AC8227l YT9217 YT9218 1GB/16GB"

But the story ends with

"USB port detected: /dev/ttyACM0

BROM connected

Downloading & Connecting to DA...

connect DA end stage: 2, enable DRAM in 1st DA: 0

COM port is open. Trying to sync with the target...

DA Connected

executing DADownloadAll...

and nothing more.

I have tried:

- Volume up/down

- Battery in out

but no success.

Thank you in advance
[Upgrading, Modifying and Unlocking] Ndanou jean-claude:
I need help please. I encounter the error: "BROM ERROR: S_BROM_DOWNLOAD_DA_FAIL (2004)" when I try to put the ROM in my Infinix HOT 6. I use Sp_flash_tool 5.17 on linux. I am waiting for your many answers
[Upgrading, Modifying and Unlocking] opticyclic:
You shouldn't really be installing a package from an old repo on your system.

The script contains this:

LD_LIBRARY_PATH=$dirname:$dirname/lib
export LD_LIBRARY_PATH

This means that it looks in the lib dir for any extra dependencies.

Therefore, you should be able to extract the libpng12.so.0.54.0 out of the deb and copy it to the lib dir without affecting the rest of the system.

dpkg -x libpng12-0_1.2.54-1ubuntu1.1_amd64.deb /tmp/libpng2
cp /tmp/libpng2/lib/x86_64-linux-gnu/libpng12.so.0.54.0 lib
cd lib
ln -s libpng12.so.0.54.0 libpng12.so.0
[Upgrading, Modifying and Unlocking] soorajsp:
After loading the scatter file, the fash tool is closed automatically.

This is the error message shown in terminal:
[Upgrading, Modifying and Unlocking] Miss Montage:
[MENTION=7695975]soorajsp[/MENTION]: it appears to me that the scatter file might be invalid (due to the "out of range" message). Which phone do you try to flash? Which ROM and scatter file did you choose?
[Upgrading, Modifying and Unlocking] Miss Montage:
[MENTION=4954015]opticyclic[/MENTION]: thanks for the information, I updated the OP accordingly. Please bear in mind that I haven't used the SP Flash Tool for years now, but I try to keep the tutorial up to date nonetheless.
[Upgrading, Modifying and Unlocking] soorajsp:
Phone is Micromax Evok Note (aka E453), I don't have this problem while using sp flash tool in windows.

In Linux, to test the installation, I've tried without connecting the phone. Can't load the scatter file properly.
[Upgrading, Modifying and Unlocking] soorajsp:
stuck on downloading DA 100%

That was the issue of scatter file. Now its stuck on downloading DA. 100% completed, but its kind of stuck.

nothing else happens
[Upgrading, Modifying and Unlocking] Miss Montage:
Did you blacklist modemmanager?
[Upgrading, Modifying and Unlocking] roguedbear:
Stuck at DA 100%

I'm having the stuck at DA/red bar problem too.

I followed each step including blacklisting and persistent-usb rules thing

the error that the terminal dialog gives is: S_FT_DA_NO_RESPONSE

(I am running Ubuntu 18.04 )

Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
add@/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2

add@/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0

add@/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1

bind@/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0

add@/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1/tty/ttyACM0

vid is 0e8d

device vid = 0e8d

pid is 2000

device pid = 2000

com portName is: /dev/ttyACM0

Total wait time = -1583507951.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
COM port is open. Trying to sync with the target...
Failed to Connect DA: S_FT_DA_NO_RESPONSE(4001)
Disconnect!
BROM Exception! ( ERROR : S_FT_DA_NO_RESPONSE (4001)

DA didn't send response data to FlashTool!
[HINT]:
Please retry the following steps:
1. retry a new cable;
2. retry a new com port;
3. retry a new device;
4. restart the computer then retry again.)((ConnectDA,../../../flashtool/Conn/Connection.cpp,146))

(I eventually plugged out the cable from phone after alot of waiting and then i got the error message from sp tool)

This thread: https://forum.hovatek.com/thread-439.html lists all the problem/solution, and for stuck at DA, it suggests to uninstall and reinstall MediaTek drivers.

so the solution would be to reinstall MediaTek driver? but how?

(PS: I'm trying this on my Moto E3 Power which is stuck on bootloop, so Im flashing the stock rom. And to make things worse.... this is my only working phone)
[Upgrading, Modifying and Unlocking] Miss Montage:
Sorry for your trouble...

First: which version of SP flash tool do you use?

For SP Flash tool error 4001 I find several approaches on the web.

Most of them advice to reconnect the battery once the red progress bar has reached 100 percent. It might do to hold the volume + or - button at that moment.
[Upgrading, Modifying and Unlocking] soorajsp:
Yes iv

Yes ive blacklisted modemmanager
[Upgrading, Modifying and Unlocking] Miss Montage:
[MENTION=7695975]soorajsp[/MENTION] : can you provide a log file, please?
[Upgrading, Modifying and Unlocking] CMCEYE:
try with dpkg --purge modemmanager
[Upgrading, Modifying and Unlocking] vikasgupta2982:
Solution

Press (+) Volume Post clicking on download button. It will surely fix this problem, I just tried in my device.
[Upgrading, Modifying and Unlocking] VD171:
Than you. It works for me
[Upgrading, Modifying and Unlocking] kanedagr:
I am trying to run sp flash tool to send a scatter file for the frp problem. But it fails to open the port.

upport_dl_cert_to_storage: 0
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
add@/devices/pci0000:00/0000:00:13.2/usb2/2-4

add@/devices/pci0000:00/0000:00:13.2/usb2/2-4/2-4:1.0

add@/devices/pci0000:00/0000:00:13.2/usb2/2-4/2-4:1.1

bind@/devices/pci0000:00/0000:00:13.2/usb2/2-4/2-4:1.0

add@/devices/pci0000:00/0000:00:13.2/usb2/2-4/2-4:1.1/tty/ttyACM0

vid is 0e8d

device vid = 0e8d

pid is 2000

device pid = 2000

com portName is: /dev/ttyACM0

Total wait time = -1615150741.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
Connect BROM failed: S_COM_PORT_OPEN_FAIL(1013)
Disconnect!
BROM Exception! ( ERROR : S_COM_PORT_OPEN_FAIL (1013)

[COM] Failed to open COM port.
[HINT]:
Please retry the following steps:
1. retry a new cable;
2. retry a new com port;
3. retry a new device;
4. restart the computer then retry again.)((ConnectBROM,../../../flashtool/Conn/Connection.cpp,100))

And that happens only when the phone is already open and I'm deactivating. If it is already off nothing happens and the screen is opening to show the battery charging. It's scanning for the usb port but nothing happens.

I run "sudo dpkg --purge modemmanager" and it found the port instantly but it displays the above mesage again.
[Upgrading, Modifying and Unlocking] gerstavros:
Are you running the tool as root?
[Upgrading, Modifying and Unlocking] kanedagr:
./flash-tool is what i type; should I use sudo in front of it?
[Upgrading, Modifying and Unlocking] kanedagr:
The solution was to let the battery drain. Then started sp flash tools loaded the scatter file for the phone, pressed start and plugged the phone. One second it took. Everything fine and frp removed. I did with Manjaro Linux.
[Upgrading, Modifying and Unlocking] dragon788:
For a

Miss Montage this is pretty late to the game, but the newest versions of the SP Flash Tool for Linux have fixed the QT4-libpng12 dependency issues. I'd suggest iinking their download pages and recommending higher than v5.2020, I"m not sure where exactly it got fixed but the latest versions (v5 and v6) both work without error in a Debian Buster environment (and probably on Ubuntu 20.x) where libpng12 is LONG gone.

SP Flash Tool for Linux (all versions)

Download SP Flash Tool for Linux that allows you to flash or install Stock Firmware (ROM) on the devices powered by MediaTek chipset.

spflashtools.com

SP Flash Tool for Windows (all versions)

SP Flash Tool for Windows enables users to flash Stock Firmware (ROMs), unbrick bricked devices, upgrade or downgrade their operating system, and perform advanced tasks like memory testing and parameter editing.

spflashtools.com

Download SP Flash Tool for Windows and Linux (MediaTek Flash Tool)

Download SP Flash Tool (Smartphone Flash Tool) that allows you to flash or install Stock Firmware ROM (Flash File) on Mediatek Devices.

androidmtk.com
[Upgrading, Modifying and Unlocking] vonpupp:
Hello everybody.

I followed up the instructions:

- I added my user to the uucp group (I am using Arch Linux)

- I added the device to the udev rules

- I blacklisted the device from modemmanager

Yet SPFT doesn't work for me, neither on linux nor on virtualbox. I don't have a physical machine with windows. I just use linux.

The software sits there waiting for the device, herewith the screenshot:

If I type mmcli -L no modems are found which leads me to believe that the blacklisting of the device from mm has been successful. I don't know how to proceed. I am using SP_Flash_Tool_v5.2136_Linux.zip with the MT6771_Android_scatter.txt file from the stock rom (Ulefone Armor 8 Pro). I also tried it as root, with the same results.

What I would like to achieve is to perform a dump of the preloader and then a backup of the phone to later test a port of TWRP in colaboration with @lopestom for this phone model. I am friendly with the terminal, isn't there any way to perform this directly on the command line via dd or similar now that I can read the scatter file and have access to the memory mappings? I don't know how to proceed, any help is welcome.

Thank you very much.
[Upgrading, Modifying and Unlocking] qwertyuiop1289:
I have the same problem on Arch Linux - SP_Flash_Tool-5.1916_Linux.
[Upgrading, Modifying and Unlocking] Abdallah00:
I am testing some error when I run the flash tool can you help me I don't mind donating tour chancel for the help thank you
[Upgrading, Modifying and Unlocking] kngharv:
Ok, I had a such trouble getting SP Flash Tool to detect my phone.

In case people don't know, you need to put your phone to fastboot mode for SP Flash Tool to flash the ROM.

I wish people tell me that in a more straight forward way (instead of instructing people to push volume up / volume down / volume up&down etc).

What I did was simply using command line

adb reboot fastboot

and the SP Flash Tool start to download almost immediately.

One advantage of using adb / fastboot command line is that it is a good indicator rather your driver worked or not.

if adb devices and fastboot devices

don't list your connected device, then, you know you either have a device driver issue or you've purchased a usb cable too cheap to flash ROM.
[Upgrading, Modifying and Unlocking] ildar_prophet:
Actually since MTK uses fastboot there's no need in SP Flash tool and such. Just use the standard Google's tool "fastboot" and be happy.
[Upgrading, Modifying and Unlocking] drvnprgrmr:
Hi peeps! I hard bricked my infinix x551 and am trying to unbrick it.

Can someone please guide me?

I believe it was bricked by spflash tool because the issue started after I tried to use the tool to flash the stock rom

but I think I did it wrongly and now my phone is bricked.

SOMEONE HELP!!! :cry:

😭😭😭
[Upgrading, Modifying and Unlocking] drvnprgrmr:
Btw I'm a newbie in android modding so please take it easy. 😅
[Upgrading, Modifying and Unlocking] thekosmix:
Amazing step by step guidelines, but my device is not getting detected in Linux :-(

It gets stuck at

Any help related to this?

This is my system on which I'm trying to run it:
[Upgrading, Modifying and Unlocking] Neal27:
Thanks a lot. It saved a bricked device
[Upgrading, Modifying and Unlocking] Miss Montage:
In my case it looks like this:

You still might have a connection issue... But in your log the tool shuts down after trying to read the partition count. And it looks at three different block starts for that info. My log only mentions one block start at that stage.

I'm out of my wits...

Which device do you want to flash?
[Upgrading, Modifying and Unlocking] Al3XKOoL:
Maybe i need find first from wath versions start this problem on windows.

Thanks ;)
[Upgrading, Modifying and Unlocking] Miss Montage:
You're welcome - please keep me updated! ;)