yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] Al3XKOoL:
Right now I remembered in windows long ago got the same problem.

This happens if I try to use flash sp tool new versions

In windows:
[Upgrading, Modifying and Unlocking] Miss Montage:
The sp_flash_tool_linux 5.1520..... worked perfect for me though... Have you tried an earlier version?
[Upgrading, Modifying and Unlocking] Al3XKOoL:
SP_Flash_Tool_Linux_v5.1452.00.100 tested, same problem.

SP_Flash_Tool_Linux_v5.1436.00.100 also tested and same.

No older versions found :(
[Upgrading, Modifying and Unlocking] Miss Montage:
The version v5.1504.00.100 works on my 64-bit-system, too... But the error seems to be caused by something else. Have you checked the SP logfile?
[Upgrading, Modifying and Unlocking] Miss Montage:
Have you also tried the newest version? I just involuntarily re-flashed my UMI Hammer with it... Wanted to choose the twrp only, but too much multi-tasking leads to no good:eek:
[Upgrading, Modifying and Unlocking] Al3XKOoL:
Tested and same.

Here logs
[Upgrading, Modifying and Unlocking] Miss Montage:
Hmm, I will compare these lines to a successful log:
[Upgrading, Modifying and Unlocking] Miss Montage:
It hints to a communication problem between Flash tool and your phone. Do you use a USB 3 port? If available, try a USB 2.0 hub. A different cable might also help...
[Upgrading, Modifying and Unlocking] rgnr:
Using usb2, the cable is ok.
[Upgrading, Modifying and Unlocking] Miss Montage:
Have you added the user to the group "dialout"? Otherwise you need to run SP Flash Tool as root....
[Upgrading, Modifying and Unlocking] rgnr:
I'm the only user, so I'm admin, and yes, I exist in both uucp and dialout.
[Upgrading, Modifying and Unlocking] hystrix65:
IS there a 32bit working version? I'm using linux on an old (12 years) laptop
[Upgrading, Modifying and Unlocking] Miss Montage:
Sorry, but no....
[Upgrading, Modifying and Unlocking] gerstavros:
very bad idea to use 32bit Linux nowadays. lots of apps are available only in 64bit builds, so install 64bit distro (if needed, upgrade ram)
[Upgrading, Modifying and Unlocking] Jordi432:
Hi!!

I'm trying to use the tool on Antergos and the "| grep usb" order not showing the phone, and, then, the tool not works. I made all the steps and added the rules but nothing changed, I need some help please. I have a bricked phone and the only option to use it is preloader mode.

Thank you.
[Upgrading, Modifying and Unlocking] henk_j:
hi i tried to run SP flash tool linux and it runs, but whenever i try to open the scatter file it says "Error: Initializing scatter file failed. Please check the name of scatter file which you load is legal." and i dont know what to do now all things are installed as mentioned. its for my elephone p9000

anny help is highly apriciated.

Update when i use wine and use the windows variant of flashtool it opens correctly I've installed the mtk windows drivers through wine. But i am to scared to try to flash it now. To often i get sudden unexpexted closures with wine. But why don't i get that error messages in wine but with Linux mint 18 64 bit i get them.
[Upgrading, Modifying and Unlocking] Tom130:
32-bit machine

My linux MX-14 runs on 32-bit machine,and I'm not sure if I'll be able to use sp_flash_tool on it?Please let me know about it...
[Upgrading, Modifying and Unlocking] Miss Montage:
No, the flash tool is only available for 64-bit systems....
[Upgrading, Modifying and Unlocking] eloydark:
Is there a version of the SP Flash Tools in linux that supports authentication files? Are the download agents operating system specific or can I use the DA_PL_HIGH.bin from windows in linux?
[Upgrading, Modifying and Unlocking] ildar_prophet:
The latest versions seem to have that "Authentication file" thing. Just look at the versions >=16xx. Download link (mtk2000) is in the post#1.

---------- Post added at 04:44 PM ---------- Previous post was at 04:40 PM ----------

Seen that when the scatter file was for recent versions but I had an old version of the flasher.

---------- Post added at 05:00 PM ---------- Previous post was at 04:44 PM ----------

Haven't used the program for a while. And what a surprise! Two advantages in the new version:

It doesn't use libusb anymore

It does use ttyACM now. Which means no need to blocklist cdc_acm module.

Nice!
[Upgrading, Modifying and Unlocking] Charles IV:
when i open flash tool, the progress bar is already there at the bottom (just on 0, of course, however, after progressing onto the other steps, when i click download, nothing happens, i've tried the steps in the tutorial, but it doesn't make a difference.

When i run flash tool with terminal, after clicking download, these three lines appear, and it stays like that. My phone is in recovery mode, and the computer does recognise it (file browser appears and everything)

these are the tree lines that appear:

Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms

edit: these lines have now appeared:

change@/devices/pci0000:00/0000:00:02.0/drm/card0

change@/devices/pci0000:00/0000:00:02.0/drm/card0

Aaaand i accidentally ^C'ed it when copying it, will start again
[Upgrading, Modifying and Unlocking] Miss Montage:
Is your phone switched off when you connect it? This is important! Do you see it when you run

lsusb
[Upgrading, Modifying and Unlocking] Charles IV:
No, whenever I click power of in recovery, it always reboots itself. Will try the command.

edit: ooh, my free alcatel pixi 4 (4) phone is now a nexus 4!!! ... according to lsusb. I will try to power off and run lsusb again

edit: i powered off, and continued running lsusb. when powering off, it didn't appear, when off (or at least the screen), it was 'MediaTek Inc. MT65xx Preloader', when the alcatel logo appeared, it didn't appear on lsusb. Currently, it get's no further than the alcatel logo before rebooting itself into recovery, where file explorer says it's a 4034, but lsusb says its 'Google Inc. Nexus 4 (debug)'

edit: aha! with the battery removed, it comes up as 'MediaTek Inc. MT65xx Preloader', will try again ... no, it's gone again, and bootloader comes up as 'HTC (High Tech Computer Corp.) Dream / ADP1 / G1 / Magic / Tattoo'. will try anyway.

update: it appears to me, that the way to fix this, is to either make recovery show up as the correct device (i have tried serveral, and they all show up as 'Google Inc.'), or find a way to keep the device turned off.
[Upgrading, Modifying and Unlocking] Charles IV:
ok, i now take the battery out, and even though lsusb doesn't detect it, i get some progress, and land upon an error about opening ports:

Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
remove@/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/tty/ttyACM0

vid is

device vid = 0000

pid is

device pid = 0000

com portName is: /dev/ttyACM0

remove@/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0

remove@/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1

remove@/devices/pci0000:00/0000:00:14.0/usb1/1-3

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

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

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

add@/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/tty/ttyACM0

vid is 0e8d

device vid = 0e8d

pid is 2000

device pid = 2000

com portName is: /dev/ttyACM0

Total wait time = -1497088645.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
Disconnect!
BROM Exception! ( ERROR : S_COM_PORT_OPEN_FAIL (1013)

[COM] Failed to open COM port.
[HINT]:
)((ConnectBROM,../../../flashtool/Conn/Connection.cpp,85))
[Upgrading, Modifying and Unlocking] Miss Montage:
You can try to insert the battery after the flash tool recognized the phone as mtk preloader. Or try to switch off the device by long-pressing “on/off“ (at least 30 seconds)...
[Upgrading, Modifying and Unlocking] Charles IV:
holding down the power button didn't work.

when exactly should i insert the battery? if i look at the log in terminal, at what point do i know it's recognised it properly.

edit: dw about me, i restored the boot partition from a twrp backup, and now i can flash roms again, so i dont need to use spft ... for now
[Upgrading, Modifying and Unlocking] gerstavros:
Connect phone without battery, then put it. You press Download before connecting.
[Upgrading, Modifying and Unlocking] praclika:
Hello!

Thank you for your tutorial.

I have some questions about it.

lsusb doesn't show the phone when it is turned off. What could be the problem?

lsusb shows me different vendor ID, than in this tutorial.

Vendor ID:

in tutorial: 0e8d

for me (when phone turned on): 0bb4 (HTC device)

My phone is a Doogee DG310 (mtk6582).

I installed SP FlashTool from this package: https://aur.archlinux.org/packages/spflashtool-bin/

and after it I followed your tutorial.

I have other doubts about adb on my PC.

I have problems with "adb backup" command from version 1.0.32. My problem is the same as here: https://android.stackexchange.com/questions/83080/adb-backup-creates-0-byte-file-prompts-for-current-backup-password-even-though

Can I brick my phone because of this?

How can I use MTKDroidTool, SN Write Tool (, SP FlashTool) from VirtualBox?

Did anybody try to flash a ROM from (Arch) Linux to Doogee DG310 (mtk6582)?

Did it work?

Thank you for your answer ahead.
[Upgrading, Modifying and Unlocking] Miss Montage:
Did you install libusb? I think the correct package for archlinux might be https://www.archlinux.org/packages/core/x86_64/libusb/

I wouldn't worry too much about this...

This is off topic here. But you cannot brick your phone unless you try to restore the (far too small) backup file...

This is also off topic. I'm not sure if MTK Droid Tools work with your phone, they haven't been updated for quite a while. You need to install the VM Extension Pack in oder to run the programs in question. https://www.virtualbox.org/wiki/Downloads
[Upgrading, Modifying and Unlocking] praclika:
I installed libusb before.

The problem is the phone disappears from device list.

When I run lsusb at correct timestamp I could list the phone:

Bus 003 Device 011: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader

And I saw it with the correct vendor ID.

But unfortunately it disappears.

Is it normal? Can SP FlashTool catch it and will be this connection stable?
[Upgrading, Modifying and Unlocking] Miss Montage:
Yes, if you klick the "Download" Button in SP Flash Tool and then connect the switched-off phone, the tool should catch it and the connection should be stable...
[Upgrading, Modifying and Unlocking] brianbrr:
Problem when run command "./flash_tool" and "./flash_tool.sh"

I use Ubuntu 14.04.05 LTS.

When i run :

./flash_tool

and

./flash_tool.sh

output :

flash_tool: cannot connect to X server

Anyone can help me? Thanks.
[Upgrading, Modifying and Unlocking] Miss Montage:
Have you tried to double-click flash_tool?
[Upgrading, Modifying and Unlocking] :
Worked for SPFT v5.1712.00 on Fedora 20 x86_64 for a MT6737T.
[Upgrading, Modifying and Unlocking] hanalinqu:
When I run

./flash_tool

I get:

./flash_tool: error while loading shared libraries: libQtWebKit.so.4: cannot open shared object file: No such file or directory

And clicking on the file asks me whether I want to open it in terminal or not, both options don't do anything.
[Upgrading, Modifying and Unlocking] Miss Montage:
Which version of SP Flash Tool do you use? Do you run the command from within the SP Flash Tool folder? The file that cannot be found should be located under "lib".
[Upgrading, Modifying and Unlocking] hanalinqu:
It's "SP_Flash_Tool_exe_Linux_64Bit_v5.1520.00.100.zip". I run it from the installation folder in terminal. I'm running Lubuntu (Lxde) 17.04. And, yes, that file is in the lib folder.
[Upgrading, Modifying and Unlocking] Miss Montage:
edit: It seems like libqtwebkit is not included in your distribution. You can install it by the terminal command

sudo apt install libqtwebkit4
[Upgrading, Modifying and Unlocking] hanalinqu:
Well, it worked now. Thank you.
[Upgrading, Modifying and Unlocking] Miss Montage:
You're welcome. :)
[Upgrading, Modifying and Unlocking] hanalinqu:
I realized that the version I'm using is quite old. I tried installing the latest version but that gives me this error,

./flash_tool: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory

According to Ask Ubuntu:

I already installed and used the latest version on Windows 10 (the old version on Lubuntu didn't work properly), so I don't need this anymore. But I was just wondering if you're using Ubuntu 16.10+ or Arch and do you get the same error at first?
[Upgrading, Modifying and Unlocking] Miss Montage:
Thanks for the feedback! Indeed the most recent Ubuntu version I use is 16.04 LTS. It might be helpful to report this to the flash tool developer(s)...
[Upgrading, Modifying and Unlocking] z3r0c00l_2k:
When i run this

./flash_tool

i get this error on Kubuntu 17.04

./flash_tool: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory

Is there any workarround for this error?:(:(

---------- Post added at 05:36 PM ---------- Previous post was at 05:27 PM ----------

I found a fix for this....

Install the following library using this command

dpkg -i libpng12-0_1.2.54-1ubuntu1_amd64.deb

libpng12-0_1.2.54-1ubuntu1_amd64.deb
[Upgrading, Modifying and Unlocking] Miss Montage:
I will add this information to the opening post. Thank you very much!
[Upgrading, Modifying and Unlocking] z3r0c00l_2k:
cool;););)
[Upgrading, Modifying and Unlocking] mohamed.yassine:
Hi

i think that I found the solution of this problem

1- download the officiel UNBRICK DOOGEE Y100PRO - VALENCIA2

2- when u extract the zip file u will see two txt file UNBRICK DOOGEE Y100PRO - VALENCIA2 - Eng and French read the favorit one

3- at the 14 th step dont insert battery and still pressing and holding the Vol- until the downloading will done :good::good:
[Upgrading, Modifying and Unlocking] Michaelbukachi:
I'm getting this error when I click download.

https://ibb.co/fFsmLm

What could be the problem?
[Upgrading, Modifying and Unlocking] Miss Montage:
You might try a different download agent. There are a few more in the flash tool directory...
[Upgrading, Modifying and Unlocking] spaten3:
I had also the error message: PMT changed for <BMTPOOL> in the log when using newer versions of the SP Flash Tool

the solution to use v5.1352.01 worked for me too for a MT6582 device (Landvo L800S)

:good: thanks for sharing
[Upgrading, Modifying and Unlocking] Aguthadeus:
Thanks, it worked flawlessly on Kali Linux
[Upgrading, Modifying and Unlocking] Miss Montage:
Does it also happen if you start the flash tool, hit "Download" and then connect the phone?
[Upgrading, Modifying and Unlocking] sramjadhav:
Thanks [MENTION=6466472]Miss Montage[/MENTION], now its working fine on my ubuntu 16.04.

Flash tools shows flash OK, but phone is not booting, I know this question is not related to thread but i think you can help me out,

Phone REDMI Note 3g
[Upgrading, Modifying and Unlocking] Miss Montage:
[MENTION=6523441]sramjadhav[/MENTION]: Please start a topic here: https://xdaforums.com/redmi-note-3/help
[Upgrading, Modifying and Unlocking] Slitherin:
Platform MT6589 not supported on this version.

Do we have updated SPFT for a Linux?
[Upgrading, Modifying and Unlocking] Miss Montage:
According to develpers' platform list MT6589 is supported. Can you be more specific about the problem?
[Upgrading, Modifying and Unlocking] 8dr:
SP Flash Tool does not work with KDE neon. It does work with Elementary OS. Both are Ubuntu 16.04 based.

$ ./flash_tool
QMetaObject::connectSlotsByName: No matching signal for on_pushButton_browser_clicked()
QObject::moveToThread: Cannot move objects with a parent
comboTimeout index(3) saved.
Application asked to unregister timer 0x2600000b which is not registered in this thread. Fix application.
Application asked to unregister timer 0x70000009 which is not registered in this thread. Fix application.
Application asked to unregister timer 0x7b00000a which is not registered in this thread. Fix application.
Uncaught std::exception in main(): locale::facet::_S_create_c_locale name not valid

Tried it with SP_Flash_Tool_v5.1752_Linux.
[Upgrading, Modifying and Unlocking] Maddytechsavvy:
Hi friends can you help me...

Phone not starting with enough battery

no recovery no fastboot no bootloader nothing just preloader

tried flashing from sp flash tools both old and new versions in windows (error- brom cmd da jump fail)

tried flashing from ygdp tools (that cpb not for phone error)

tried flashing from multiporttool ( brom cmd da jump fail)

no success....

What do i need to do do i need to use linux for spflash tool??
[Upgrading, Modifying and Unlocking] Miss Montage:
Have you read step 4 of the start post?
[Upgrading, Modifying and Unlocking] Maddytechsavvy:
Dude i have read it and i am happy that bug is found out but i do not have any pc with linux i have win 8 and 10 how can i unbrick mu phone ising windows
[Upgrading, Modifying and Unlocking] Miss Montage:
You better ask here: https://xdaforums.com/showthread.php?t=2650125

As far as I remember the error message hints to missing or wrong drivers (Windows version)
[Upgrading, Modifying and Unlocking] Miss Montage:
I wonder about the vendor ID. Did you switch off the phone before connecting?
[Upgrading, Modifying and Unlocking] Elsatests:
Xiaomi Redmi Note 4

Thanks for the answer!

Yes, the phone was switched off before connecting. Well, I've tried several: connecting once I had started SPFT and "Readback", before "Readback", before connecting the cable... I've read that the steps are:

1) start SPFT, then Readback

2) connect the cable to the PC

3) connect the cable to the mobile and switch it on with Vol+ (which enter Flashboot mode and that is correct)

The vendor is Xiaomi, model Redmi Note 4
[Upgrading, Modifying and Unlocking] Miss Montage:
AFAIK the Xiaomi Redmi Note 4 is equipped with a Snapdragon chipset? The SP flash tool works only with MediaTek devices...
[Upgrading, Modifying and Unlocking] Elsatests:
I forgot to add that I've tried with two cables (the original one and another Huawei's one) and I've tried with and without battery. All this, make me think that it has something to do with drivers, but I'm using Linux (Ubuntu) and I don't see any errors I can follow.

Thanks again for your help and your thorough tutorial.

---------- Post added at 10:13 AM ---------- Previous post was at 10:06 AM ----------

I thought it was MediaTek: https://www.gsmarena.com/xiaomi_redmi_note_4_(mediatek)-8291.php

4x is Snapdragon: https://www.gsmarena.com/xiaomi_redmi_note_4-8531.php

Am I right?
[Upgrading, Modifying and Unlocking] Miss Montage:
Can you boot the phone and look into settings -> about phone?
[Upgrading, Modifying and Unlocking] Elsatests:
No, I cannot. That's why I want to recover data. Though it boots in fastboot mode or normal mode it doesn't work and I cannot access the phone.
[Upgrading, Modifying and Unlocking] Miss Montage:
It does not make sense to run a readback from a dysfunctional phone. However, you could try to backup solely the userdata partition.

I'm still sceptical about the cpu... Can you boot into recovery mode? Probably you can find info about the chipset producer there.
[Upgrading, Modifying and Unlocking] Elsatests:
Thanks for your patience Miss Montage!

I don't get any other info from the recovery menu. And now I'm skeptical about the CPU too. I've googled around and I've seen that there are two variants:

"For your information, Xiaomi has released two variants of Redmi Note 4: the one powered with MediaTek chipset and the other one powered with Qualcomm Snapdragon chipset. The MediaTek Helio X20 variant is known as Nikel whereas the Snapdragon 625 variant is known as Mido." from https://androidfilebox.com/tips/how-to-fix-bricked-redmi-note-4-snapdragon/

In that case, I'll give up. As you said, I was just trying to backup solely the userdata partition, but from your comment, should I understand there is an easier way?
[Upgrading, Modifying and Unlocking] page64:
there are different steps to set up and use Flashtool on Manjaro ?
[Upgrading, Modifying and Unlocking] Miss Montage:
Since Manjaro is based on Arch Linux there will be differences. You might ask [MENTION=6755930]Yoshi_Guy[/MENTION] or [MENTION=3784300]BlueFlame4[/MENTION], they "ported" the instructions to Arch...
[MENTION=9017627]Elsatests[/MENTION] : no, without TWRP I wouldn't know of a simple way to backup Data/Userdata.
[Upgrading, Modifying and Unlocking] BlueFlame4:
I'm afraid I cannot help here because it's been years since I used an Arch based distro and I don't remember the details for SPFT.
[Upgrading, Modifying and Unlocking] Amigo62:
Hi,

I was trying last FlashTool 5.18 on my Zenbook UX 32VD (Xubuntu 17.10(artful)), according to this manual. But Flashtool not start with this message:

dedy@zen:~/Android/SP_Flash_Tool_v5.1812_Linux$ ./flash_tool

./flash_tool: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory.

Thanks for Yours advices, and sory for my english.
[Upgrading, Modifying and Unlocking] Miss Montage:
obsolete
[Upgrading, Modifying and Unlocking] Miss Montage:
Please try this:
[Upgrading, Modifying and Unlocking] Amigo62:
Operation deny, required root access, sudo not working. :(
[Upgrading, Modifying and Unlocking] Miss Montage:
Which error message do you get with sudo?
[Upgrading, Modifying and Unlocking] Amigo62:
NOw it is work and SPFT starting. I will try it now.

Thaks for all. :good::good::good::good::good:

---------- Post added at 07:12 PM ---------- Previous post was at 06:33 PM ----------

Ooops, starting from terminal give message:

dedy@zen:~/Android/SP_Flash_Tool_v5.1812_Linux$ ./flash_tool

QMetaObject::connectSlotsByName: No matching signal for on_pushButton_browser_clicked()

QObject::moveToThread: Cannot move objects with a parent

comboTimeout index(3) saved.
[Upgrading, Modifying and Unlocking] Amigo62:
My mistake,

after read up scatter file, SPFT is OK for now, cpu 6750 is recognized, tomorrow I will be contiuned.
[Upgrading, Modifying and Unlocking] Fstop:
Using Slackware64-14.1

Scatter File loads fine. But Logo Download Test hangs with the following info.:

Stage: checksum processing:100% percent, checksum:0x67d2
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[HINT]:
)((ConnectBROM,../../../flashtool/Conn/Connection.cpp,100))
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
SearchUSBPortPool failed!
Failed to find USB port
Connect BROM failed: S_TIMEOUT
Disconnect!
User stopped.
comboTimeout index(3) saved.

bash-4.2# dmesg | tail
[ 7138.712561] usb 1-7: can't read configurations, error -22
[ 7138.713121] hub 1-0:1.0: unable to enumerate USB device on port 7
[ 7138.943032] usb 5-1: new full-speed USB device number 4 using uhci_hcd
[ 7139.459036] usb 5-1: device not accepting address 4, error -71
[ 7139.612038] usb 1-7: new high-speed USB device number 13 using ehci-pci
[ 7139.727254] usb 1-7: New USB device found, idVendor=0e8d, idProduct=201d
[ 7139.727260] usb 1-7: New USB device strings: Mfr=3, Product=4, SerialNumber=5
[ 7139.727264] usb 1-7: Product: MIX
[ 7139.727267] usb 1-7: Manufacturer: MediaTek
[ 7139.727270] usb 1-7: SerialNumber: 0123456789ABCDEF

Looking for the udev persistent-80-usb.rules but I'm not sure I need them given usb 1-7 is reading Device ID info.?
[Upgrading, Modifying and Unlocking] Miss Montage:
Although I see no sign of disconnecting, try the udev rule. It should help to establish a connection.