Package Details: spflashtool-bin 6.2228-1

Git Clone URL: https://aur.archlinux.org/spflashtool-bin.git (read-only, click to copy)
Package Base: spflashtool-bin
Description: SP Flash Tool is an application to flash your MediaTek (MTK) SmartPhone.
Upstream URL: http://spflashtools.com/category/linux
Licenses: unknown
Conflicts: spflashtool
Provides: spflashtool
Submitter: Omar007
Maintainer: Omar007
Last Packager: Omar007
Votes: 31
Popularity: 0.000186
First Submitted: 2016-05-21 15:48 (UTC)
Last Updated: 2023-04-29 01:05 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

nasrul commented on 2018-03-31 13:16 (UTC)

@ardadem i replaced my usb cable and it solved.

ardadem commented on 2018-03-31 13:07 (UTC)

Bus 001 Device 008: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader

same issue with @nasrul. i get ERROR : S_FT_DA_NO_RESPONSE (4001) message. this is about flashtool can't connect com port. any solution?

Omar007 commented on 2018-02-16 11:37 (UTC) (edited on 2018-02-16 11:38 (UTC) by Omar007)

@nasrul; this is not a support forum for the application. If you have trouble with the package itself, feel free to drop a comment, but don't expect any support on the program itself. You should probably go to the XDA Developers website for that.

I'll only leave you with this last bit of info; afaik that error is shown when the application has trouble communicating with the phone (bad cable? not enough power? bad USB port?).

nasrul commented on 2018-02-16 11:26 (UTC)

Any suggest for ERROR : S_FT_DA_NO_RESPONSE (4001)?

Some articles said that the error because DA on PC has no information dowloaded. it maybe cause of bad memory or bad HDD. My pc has 11,6 GB RAM and 128 GB SSD (3GB space available in /home and 27GB in root).

Any suggest will be very appreciate.

nasrul commented on 2018-02-12 02:13 (UTC)

my wrong. my device seems dead. it boot / restart loop.

The program showed Download DA progress after I click Format All + Download, but it returned S_BROM_DOWNLOAD_DA_FAIL (2004).

As @Omar007 suggest, i think i should learn how to use the program.

thanks for all supports. (y)

Omar007 commented on 2018-02-11 17:42 (UTC) (edited on 2018-02-11 17:46 (UTC) by Omar007)

@nasrul: I'm pretty sure you're not connecting the phone properly. Afaik, those are the IDs of the phone itself, not of the Preloader. The vendor isn't even the same as the MTK Preloader vendor. What phone is this?

At this point you should probably look up how to use this program (does it even support your phone?) and how to connect your phone..

nasrul commented on 2018-02-11 17:34 (UTC) (edited on 2018-02-11 17:37 (UTC) by nasrul)

@Omar007 Thanks for your big support. I've updated the program and i found the addition file 60-spflashtool.rules on /lib/udev/rules.d directory.

Then i ran the app but same error. The error still persist when i adjusted the file using idVendor and idProduct of my device that i got through sudo lsusb -v

...
  idVendor           0x2717 
  idProduct          0xff40  
...

if you mind to see the complete details here: https://pastebin.com/ciUCbZfC

And once again big thanks. (y)

Omar007 commented on 2018-02-11 16:24 (UTC) (edited on 2018-02-11 16:42 (UTC) by Omar007)

@nasrul:

First let me git this out of the way; you really should not be running GUI application under root!

Second, the error is pretty self-explanatory. Your user does not have access/permission to open the required COM device under /dev (/dev/ttyACM*).

A 2min Google search would've given you a solution to this... Anyway, there are several ways to go about this:

1) set up an udev rule to set mode to 0666 for the given device

2) add your user to the uucp group

You can pick whichever solution you prefer but I guess I could whip up a udev rule and include it with the package. If you wait a while I'll just throw that in.

EDIT: Udev rule added to the package. If it doesn't work, please let me know the vendor id and device id for your device.

« First ‹ Previous 1 2 3 4 5 Next › Last »