yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] Miss Montage:
Did you start the flash tool, select the scatter file, press "download" and then try to connect the switched-off phone? I'm asking because the computer seems to be looking for a MTP device...

If you connect the phone successfully the terminal should give out something like this:

./flash_tool

QThread::setPriority: Cannot set priority, thread is not running
"11-20-2015"
QObject::moveToThread: Cannot move objects with a parent
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
add@/devices/pci0000:00/0000:00:13.2/usb2/2-2

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

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

add@/devices/pci0000:00/0000:00:13.2/usb2/2-2/2-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 = -1448123501.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
COM port is open. Trying to sync with the target...
DA Connected
executing DADownloadAll...
download speed: 4.87Mbps.

Unfortunately I'm not familiar with Debian, but according to [MENTION=6864103]Sn4kes[/MENTION] it should work just fine... I don't know if he or she's using LMDE2. I read numerous times that the flash tool works only with USB type 2 port. Please try a different port ;)
[Upgrading, Modifying and Unlocking] Abraham79:
Well Miss, I'm new to flashing android stuff, though I'm accustomed to terminal use. I did launch Sp flash tool and tried to load scatter file through Download button, but no signs of the phone is detected, either when switched ON or in OFF condition.

I've few doubts:

1. When the phone is switched ON as you can see, the device id is 271d,3c03. adb recognizes fine.

2. When the phone is switched OFF, the device id is 0e8d,2000 . I've added this device id in ~/.android/adb_usb_ini .

Now, ~/.android/adb_usb_ini contents:

0x0e8d
0x271d

3. Which mode (phone: on or off?) the sp flash tool should be invoked? I'm confused here. Also, the device id's - will there be anymore product id's under 0e8d in this phone? anyway to find out.

EDIT: these are the udev rules I've added. Is this fine?

~ $ cat /etc/udev/rules.d/80-persistent-usb.rules
SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0e8d", ATTR{idProduct}=="*"
~ $ cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="271d", ATTR{idProduct}=="3c03", MODE="0660", GROUP="plugdev", SYMLINK+="android%n"

If not sp flash tool, is there a way to flash the update stock ROM using fastboot? Without rooting? Also backing up NVRAM and IEMI in Linux possible?

TIA and Regards,

Abraham
[Upgrading, Modifying and Unlocking] Miss Montage:
You don't get the scatter-file via the "Download"-button, you need to navigate to it (it should be within the folder of the ROM you want to flash). Then you select "Download Only" (or if you have been using Kitkat so far "Firmware Upgrade")

Once ready, hit Download button and then connect the phone. It must be switched off. It might be necessary for your device to remove the battery, please try around.

Your udev rules look fine to me, in case you get error [2035] please look into my OP (step 5).

It is kind of normal that you get different Vendor ID's in Preloader vs. ADB/MTP-Mode.

Here is a nice how-to for the flash tool itself (from step 6 onwards)
[Upgrading, Modifying and Unlocking] Abraham79:
Hi, from the beginning I've selected the scatter file from the ROM folder as it is common sense - 15 years on Linux means you'll be twice sure before asking here ;) . But, no signs of detecting. No option for removing battery as it is a fixed 5000mAh one!
[Upgrading, Modifying and Unlocking] hammer-joe:
thank you man.. sp flash tool worked fine on ubuntu 15.10 (64) following your tutorial
[Upgrading, Modifying and Unlocking] Miss Montage:
[MENTION=6178240]Abraham79[/MENTION] : Have you tried to connect the phone holding Vol+ or Vol- ?

You can also remove "0x0e8d" from ~/.android/adb_usb_ini

Preloader mode is different to adb. And have you tried a USB 2.0-port yet?

And please do not use full quotes of a post directly above yours. It clutters the thread...
[Upgrading, Modifying and Unlocking] Abraham79:
[MENTION=6466472]Miss Montage[/MENTION] : I've tried upgrading to 4.2.x kernel assuming it's a kernel issue. But it is not. So, do you know if it is possible to manually flash the firmware using fastboot? I mean, the files listed in the scatter file manually flashed on to the phone to the specific partitions mentioned in the scatter file?

Meanwhile I've put a report on libmtp BTS, since I guess this phone's vendor,product id's are not added?
[Upgrading, Modifying and Unlocking] Abraham79:
I ended up using a friend's PC(Win 7), rooted using iroot, backed up nvram using dd and later used sp flash tool in Windows which worked fine upgrading to Lollipop firmware.
[Upgrading, Modifying and Unlocking] Abraham79:
This time, I tried sp flash tool on Debian Linux and it is working. [MENTION=6466472]Miss Montage[/MENTION] :good:
[Upgrading, Modifying and Unlocking] abe_long:
thank you for your guide...this method have revive my phone...
[Upgrading, Modifying and Unlocking] Noroot:
X server

Hi, trying to get this to work on my mint 17 installation, when I try to start it I get the error:

flash_tool: cannot connect to X server

Any ideas?

Thanks
[Upgrading, Modifying and Unlocking] Miss Montage:
Have you made flash_tool and flash_tool.sh executable?

chmod +x flash_tool
chmod +x flash_tool.sh

If these commands don't help, try to double-click the flash_tool icon.
[Upgrading, Modifying and Unlocking] Noroot:
I had made them executable, no joy but double clicking the flash_tool icon worked

I don't see a thanks button but thanks!
[Upgrading, Modifying and Unlocking] kingofswords:
why doesnt 32 bit version works from sp flash tools web site?
[Upgrading, Modifying and Unlocking] Miss Montage:
Because it's not a 32-bit version ("file flash_tool" tells you). I would upgrade to 64-bit Linux anyway, as long as your hardware supports it.
[Upgrading, Modifying and Unlocking] kingofswords:
The download link on spflashtools. Com said it was 32 bit
[Upgrading, Modifying and Unlocking] DerTeufel1980:
Then you need to complain there

Gesendet von meinem JY-S3 mit Tapatalk
[Upgrading, Modifying and Unlocking] kingofswords:
what is it i should be complaining about?

site says its a 32 bit version, ive no reason to doubt that, i have no idea how to get it running so ive come on here for help
[Upgrading, Modifying and Unlocking] Miss Montage:
Look at post 70 ff
[Upgrading, Modifying and Unlocking] DerTeufel1980:
This...

You should complain about the file being 64bit, although it says 32.

If the file is 32 bit, then it is already working fine, I guess ;)

Gesendet von meinem JY-S3 mit Tapatalk
[Upgrading, Modifying and Unlocking] kingofswords:
oh yeh sorry you were both right it was 64bit ver.....i download from site i thought was official sptools but didnt read through this thread:s

took your advice and installed 64 bit ubuntu on old laptop and it running following your guide and then double clicking(cannot connect to x server error)

dmesg | grep usb

has phone listed ...then usb disconnect so not sure if its the problem

when phone is on its automatically recognized it on pc

but when i hit download in sp tools and then plug turned off phone nothing happens then battery charging screen comes on phone.

any ideas what' S_BROM_CMD_JUMP_DA_FAIL (1013) 'is? failed to open COM port.

i unlocked bootloader earlier using fastboot oem unlock via terminal would that make a difference?

im just trying to download a recovery so as to flash supersu in order to root phone..

thanks

---------- Post added at 05:11 AM ---------- Previous post was at 05:02 AM ----------

just read elsewhere on xda 1013 error is 'u need to run it as adminstrator'
[Upgrading, Modifying and Unlocking] Miss Montage:
Not necessarily, Linux users don't need to run the flash tool as root if they belong to usergroup "dialout". Sometimes I get the error message too, if the charging screen starts instead of preloader mode. I think I'm just a little too slow in these situations. Just try it again, probably with vol- or vol+ pressed while inserting the plug. If your battery is removable, you can also try to remove it, connect the phone and reinsert the battery. Your unlocked bootloader shouldn't be a problem. What kind of phone is it?
[Upgrading, Modifying and Unlocking] kingofswords:
Thank so much for your help miss montage can't believe finally got it working

Held vol- when plugging USB in and got another error so tried again with vol+held whole time and it worked

Weirdly enough after error I booted into stock recovery which normally just shows picture of Android robot with red error triangle coming out chest but as I was holding phone I had vol+ depressed for 10 secs or so then it entered Android stock recovery different to one another was installing... It wouldn't flash supers though

It's elephone p8000, one of earlier models without home led, seems without pre root also as most others don't have to use so tools
[Upgrading, Modifying and Unlocking] Miss Montage:
It's kind of normal that you see the "dead" android in MTK stock recovery. Pressing the Power button did the trick for me. Also it will not allow to flash unsigned .zip files, that's why you need to flash a custom recovery. It worked now? Congratulations :)
[Upgrading, Modifying and Unlocking] kenny108:
When my phone was working Vol+ at power on would take it to a screen with lots of options like clearing cache, fastboot, and so on,is that the 'peloader' mode?

But I put on the wrong recovery image and now the screen shows manufacturer's logo for about a second and then just goes white.

And SP_Flash_Tool just keeps giving the same error (1013) (see this thread).

So if its gone into charging screen its too late for SP_Flash_Tool is it? With my Pixi 3 4.5 4G and Ubuntu 14.04 I've tried lots of variations with Vol+, Vol-, battery in, battery out, different order of connecting USB at computer or phone but so far nothing works, the flash tool just keeps giving that 1013 error.
[Upgrading, Modifying and Unlocking] Miss Montage:
Vol+ plus Power gets you into the bootloader. Preloader/Download mode is not visible on the phone, you just recognize the connection in the flash tool. Unfortunately I don't know how to help you with your phone. But yes, in my experience it's too late for the flash tool once the charging screen appears.
[Upgrading, Modifying and Unlocking] kenny108:
Thanks for explaining that, I was confused about the difference.

I followed your guide, it is very good, thanks. Today the flash tool is working fine and I've recovered my Pixi3 4.5 4G from it's boot loop. The procedure that works for me with this phone is:

Remove battery from phone, don't connect to computer yet

Start flash tool, load scatter file, select what to download

Click 'Download' - flash tool is waiting

Now plug in phone (without battery) to computer USB

Download starts, progress bar moves across, Done

After flash tool says 'Done' it seems to disconnect the USB, so if I tried another download it would fail...I needed to unplug the phone and start again if I needed to do another download.
[Upgrading, Modifying and Unlocking] firefoxjds:
Thankyou So Much for this Post

I really appreciate this post. It's really nice to get Sp Flash tools working on Ubuntu. I will find this tool very helpful for many purposes.
[Upgrading, Modifying and Unlocking] prz52:
I'm trying to flash Manta 713 tablet(non-removable battery), but SP Flash tool hangs at USB port detected: /dev/ttyACM0 - no BROM connected messages. Followed udev rules, can't see a reason, dmesg seems to be fine. Doing that on Fedora 23. Any ideas please?

All the time I get BRom_AutoBoot::BRom_StartCmd(0): m_ext_clock(EXT_26M), m_baud_rate(xxxx), SEND(0xA0)->RECV(0xA0), fail_retry(yyyy) error in logs.
[Upgrading, Modifying and Unlocking] Miss Montage:
Have you tried Vol+ or Vol- while connecting?
[Upgrading, Modifying and Unlocking] Phoenix_Alx:
Hi people,

Big tools at least on Linux.

I have a problem. Big problem.

I have a Doogee Valencia Y100 pro . I updated a OTA's update and then BRICK!!!!!!

I have downloaded this software with the official rom but when I do download and connect the phone I have the next error:

Failed to Connect DA: S_BROM_CHKSUM16_MEM_RESULT_DIFF
Disconnect!
BROM Exception! ( BROM ERROR : S_BROM_CHKSUM16_MEM_RESULT_DIFF (2020)

[H/W] Fail to download DA to baseband chip's internal SRAM!
The internal SRAM has the problem that leads to 16 bits checksum error!

Then I try again and i do Vol+ and Vol- while connecting...but

BROM Exception! ( BROM 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,../../../qt_flash_tool/Conn/Connection.cpp,127))

Does any body know how fix it ?

Thanks for your time ^_^
[Upgrading, Modifying and Unlocking] Miss Montage:
Which Flash Tool Version do you use? Can you remove the battery ? (just while connecting, you should reinsert it for the download procedure)
[Upgrading, Modifying and Unlocking] Phoenix_Alx:
V5.1520.00.100 Linux 64 bits

Yes, I removed the battery, and reinserted The same problem, again.
[Upgrading, Modifying and Unlocking] Phoenix_Alx:
I have seen the Log the first error. ERROR: BRom_MT6276::BRom_WriteBuf(): checksum error!, checksum(0xBE8E) != brom_checksum(0x0000). (brom_mt6276.cpp:1161)

I don't know if this can help to anyone.

do you know where download the source code of this program?
[Upgrading, Modifying and Unlocking] Miss Montage:
You may try a newer version of the flash tool: http://mtk2000.ucoz.ru/down16/SP_Flash_Tool_Linux_v5.1552.rar is most up to date. According to an older list: http://en.miui.com/thread-78047-1-1.html error [2020] hints to a connection error due to battery settings.
[Upgrading, Modifying and Unlocking] Phoenix_Alx:
Thanks, I have tryed this and...the same results
[Upgrading, Modifying and Unlocking] Miss Montage:
You can try a different USB Port - as far as I know USB 2.0 is still recommended - and/or a different cable.
[Upgrading, Modifying and Unlocking] firefoxjds:
Are you using sp tools on Ubuntu?

If so there is a modem incompatibility issue with ubuntu. I have the link at home as to how to fix it. I can post it in a bit when I get back. In the meantime you can try googling the fix or use sp tools on windows to get around the issue. Ill be home in a couple hours and try to find my instructions.
[Upgrading, Modifying and Unlocking] gerstavros:
Your phone's memory is dead. It's not flash tool problem or else, just your phone needs new motherboard.
[Upgrading, Modifying and Unlocking] Miss Montage:
[MENTION=4666118]gerstavros[/MENTION]: How can you be so sure about this?

Well, I don't know why it says 0xBE8E, if it is looking for the vendor ID it should be 0x0E8D... "0x0000" doesn't look good, though. What is the output of

dmesg | grep usb

if you connect the (switched off) phone?

Another thought: does the ROM contain a "checksum.ini" file? You might move it away from the folder and try again...
[Upgrading, Modifying and Unlocking] gerstavros:
It's shown on the messages. They have nothing to do with the connection with the pc. Phone connects, but don't give access to the flash memory. Also the phone bricked after ota update. That's not normal, and makes me sure that the flash memory of motherboard got bricked.

I flash mtk phones almost every day in my job for 4 years, i 've seen almost anything
[Upgrading, Modifying and Unlocking] Miss Montage:
It happens all the time that a phone gets softbricked by an OTA update - especially if it was rooted before and/or equipped with a custom recovery.
[Upgrading, Modifying and Unlocking] gerstavros:
No. Phone doesn't update at all with custom recovery, and if it's rooted it replaces the system, or don't update. Doogee, doesn't download updates if rooted, it gives message "system modified, cannot update".

Anyway, let him try another cable, or pc, he doesn't lose anything to try.
[Upgrading, Modifying and Unlocking] dormilonX:
Thank You so much for this tutorial. :good::good::good:

After one week of useless tries I was about to bang my head against the wall :eek: until I happened to find your instructions. :D
[Upgrading, Modifying and Unlocking] Preet_:
[MENTION=6466472]Miss Montage[/MENTION]. my device isn't detected and I cannot even see Mediatek 65xx Preloader, what should I do? my device boots up correctly but I cannot use SP flash tools to revert back to stock

---------- Post added at 05:13 AM ---------- Previous post was at 04:43 AM ----------

preet@Preet-HP-620:~$ cd Desktop/SP
preet@Preet-HP-620:~/Desktop/SP$ ./flash_tool
QObject::moveToThread: Cannot move objects with a parent
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
add@/devices/pci0000:00/0000:00:1d.7/usb2/2-1

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

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

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

vid is 0e8d

device vid = 0e8d

pid is 2000

device pid = 2000

com portName is: /dev/ttyACM0

Total wait time = -1459055489.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0

Phone detected but gives me an error

BROM ERROR : S_COM_PORT_OPEN_FAIL (1013)

[COM] Failed to open COM port.
[HINT]:
[Upgrading, Modifying and Unlocking] Miss Montage:
Try to connect without battery (reinsert when detected) or with Vol+ or Vol- Button pressed.
[Upgrading, Modifying and Unlocking] SecUpwN:
Thank you for this wonderful thread, [MENTION=6466472]Miss Montage[/MENTION]! I am currently working on a Wiko Bloom using my openSUSE Tumbleweed x64 Laptop and always get the same error as mentioned above:

Is this error caused by the program not running with root privileges? Note: I have temporarily added my own username to group dialout to avoid creating yet another user on my linux box. Here's the current logfile:

SecUpwN@GLaDOS:~/Home/Hackfleisch/ROOT/SP_Flash_Tool> ./flash_tool
QThread::setPriority: Cannot set priority, thread is not running
"03-09-2016"
QObject::moveToThread: Cannot move objects with a parent
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
add@/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2

add@/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0

add@/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1

add@/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-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 = -1460183023.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! ( BROM ERROR : S_COM_PORT_OPEN_FAIL (1013)

[COM] Failed to open COM port.
[HINT]:
)((ConnectBROM,../../../flashtool/Conn/Connection.cpp,85))
comboTimeout index(3) saved.
[Upgrading, Modifying and Unlocking] Miss Montage:
I don't think the error occurs due to lacking root. You might try these options:

Source: https://forum.hovatek.com/thread-439.html

You might also try to press Vol+ or Vol- when connecting the phone.
[Upgrading, Modifying and Unlocking] Miss Montage:
No, fastboot mode will not help you here - I assume you pressed Power and Vol-? You really need to connect an entirely switched-off phone, sometimes even without battery (it should be reinserted once the flash tool recognizes the device).
[Upgrading, Modifying and Unlocking] SecUpwN:
Yes. And I am currently trying again on a Windows computer without Admin rights (bercause it is not my own). Phone still does not get recognized.

Thanks for your endurance with me, [MENTION=6466472]Miss Montage[/MENTION]. NEWS: IT FINALLY WORKED. THANK YOU SO MUCH! :cowboy:

SecUpwN@GLaDOS:~/Home/Hackfleisch/ROOT/SP_Flash_Tool> ./flash_tool
QThread::setPriority: Cannot set priority, thread is not running
"03-09-2016"
QObject::moveToThread: Cannot move objects with a parent
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.5

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

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

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

vid is 0e8d

device vid = 0e8d

pid is 2000

device pid = 2000

com portName is: /dev/ttyACM0

Total wait time = -1460217550.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
COM port is open. Trying to sync with the target...
DA Connected
Format Succeeded.
Format Succeeded.
executing DADownloadAll...
download speed: 7.08Mbps.
Disconnect!
[Upgrading, Modifying and Unlocking] Amehk:
God bless you and Sergio Riveros as well!!!
[Upgrading, Modifying and Unlocking] xBlackout:
Hello guys, can you help me? I followed the guide and the phone is detected and the download begins but it disconnects. Here is the output:

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

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

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

add@/module/cdc_acm

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

vid is 0e8d

device vid = 0e8d

pid is 2000

device pid = 2000

com portName is: /dev/ttyACM0

Total wait time = -1465566482.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
COM port is open. Trying to sync with the target...
Failed to Connect DA: S_BROM_DOWNLOAD_DA_FAIL
Disconnect!
BROM Exception! ( BROM 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,../../../qt_flash_tool/Conn/Connection.cpp,127))
[Upgrading, Modifying and Unlocking] Miss Montage:
One of my favourite sources for Flash Tool errors is https://forum.hovatek.com/thread-439.html
[Upgrading, Modifying and Unlocking] MilkyPL:
Didn't work. I did all the steps, and when i click download, nothing happens (of course i hold the volume down and plug the phone-that worked for windows) I'm on Ubuntu 14.04.
[Upgrading, Modifying and Unlocking] bigsupersquid:
I found a page with a 32 bit linux version of spflashtool.

didn't try it myself, but here it is

http://spflashtool.com/

//edit: apparently mislabeled 64 bit version...