I too faced this issue and issuing the fastboot commands manually (instead of relying on flash-all) and it worked well.
These are the commands to use (just forget everything and make sure these commands are executed in this order with the appropriate .img file available):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash ...
Rooting MTK based 'China' phones using SP Flash Tool.
I've tested this on my Ubuntu 14.04 laptop by rooting a Lenovo P780.
@Paul Mahieu tested on Huawei Ascend Y221 using Ubuntu 16.04 and reports that it works.
First of all, install libusb-dev pacakage:
apt-get install libusb-dev
Now you need to download SP Flash Tool v5 from here.
Assuming it is ...
There is no fastboot mode on Samsung. You must use the ODIN mode, which is an alternative to fastboot. On Linux there is a client application called Heimdall which talks to phones via Odin mode. So the answer to your question is ODIN or Heimdall. ODIN is the proprietary Samsung PC application, Heimdall is multiplatform open source alternative.
What does Flashtool do?
Your CPU is made by a chinese company called MediaTek and they have released a tool to flash stuff on devices that use their chip called SP Flashtool. So this tool does what it says. It flashes data onto your phone, and where and what data is flashed is determined by the scatter file your provide(where) and the files you open in the ...
.ftf are more suited for the older line of Xperia devices and is proprietary format, the trend with newer Sony devices is .elf instead.
Their layout of kernel image is non-standard, this requires a special script to run against the freshly built kernel image to convert it and add extra special markers to make it compatible for the Xperia to enable booting. ...
Samsung devices with Download Mode do not support fastboot.
adb is not supported in fastboot mode anyways (nor Download mode).
If you want to flash something via fastboot, you must use Odin or Heimdall (or another tool that works with Download Mode).
I'll be answering my question.
I downloaded USBDeview and I deleted all COM ports that are open. I also did removing my USB controllers on my Device Manager. I restarted my computer to reload all the drivers; then opening the flasher generates a new COM port, clicking the upgrade and it worked.
1. What is a generic firmware?
A generic firmware is the firmware for an android device published by the devices manufacturer.
2. What is a branded firmware?
A branded firmware is a firmware customized by cell phone providers to advertise themself by showing their logo, installing apps or adding bookmarks to the browser. Updates for branded phones getting ...
From my notes when I first used it (which was the only time I did):¹
Download and unzip the package , Open SPFLASHTOOL EXE and Load the Scatter file (Click Scatter Loading)
Uncheck all the boxes
Go to / click RECOVERY box from list and load recovery image according to your device/choice (load image from the separate window -->open)
Now you can see RECOVERY ...
Its a file used in flashing roms (or parts of the rom) for example for the SP Flash Tools. This file has info in it that tells the tool how to flash to the device.
You don't flash the DA file so it wouldn't be checked by the boot ROM. But what you are flashing would be checked.
Check out SP Flash Tool
I couldn't get the XperiFirm integrated into Flashtool to work. Even with the stand alone, it didn't have the firmware I was looking for. I ended up just Google searching the the firmware with "ftf". Flashing it with Flashtools worked fine.
TL;DR download the desired firmware as an FTF found through a Google Search. Flash it with Flashtool.
There's no such thing as "CM bootloader" - a CM installation only writes a new /boot (kernel) and /system.
Since you are explicitly looking to return to stock, FlashTool is still your best bet. Find the latest stock ROM for your variant and region using XperiFirm, generate a .ftf format file with what you downloaded using Flashtool with the guide here, then ...
Preloader is present in eMMC.
/dev/block/mmcblk0 is located in eMMC as linear address.mmcblk0 starts with mbr, not including preloader. You can easily check by putting this mmcblk0 in eMMC raw tool and by clicking Load partition structure button.
But preloader is located as logical address.
Preloader is most certainly a partition visible in a smart device's partition index/filesystem. This partition is present on virtually every Lenovo device manufactured today. It is not embedded in the processor chip, but rather is located within the eMMC SD internal storage. So to answer your original question, yes, the MTK preloader is in
the same eMMC ...
It's present in the Boot ROM, not a directly visible partition in the eMMC.
Source: MediaTek details: SoC startup
The Boot ROM will be embedded inside the processor chip in generic chipsets. (read more) (no idea about MTK)
Further Technical details on working of Preloader: MediaTek details: Partitions and Preloader
Moving one device's rig to another? No problem! All you need is:
one large SD card/USB-OTG
TWRP (You have root, so this will be easy) on both devices
Part one- getting TWRP If you have TWRP already, skip this.
Download TWRP manager from this google play link.
Install TWRP from the install section. Make sure you select the right make and model
Since I have a MTK-6577 based phone and had to delve into repairing a broken partition table recently I thought I'd take a stab at answering this.
I want to know that when we flash specific partition images (say
system.img, data.img, cache.img, etc.), then how does the software
know where exactly to put those partition bytes?
If you flash to known ...
I finally discovered that the problem was in the path to download agent, where was the Chinese characters for example :
**x-302 NEW firmware \ 线 刷 工具 和 驱动 \ mt65xx preloader 驱动 **
I just retype to :
**x-302 NEW firmware\Flash\mt65xx preloader**
and then it works correctly and retrieve the download agent. In all the tutorials I could see that the used ...
No. You can not delete the system while it is running. If you have root access, you could "program" the stock recovery to flash your custom ROM on the next reboot by using a specific command line in a terminal.
There is LG Flash Tool for your device, but it is not official.
Answer compiled from comments
The SPFT version you are using is probably incompatible with your device or firmware, and it is failing silently. Try downloading the latest version of SPFT and the correct firmware, and it should probably work.
OK the problem was that I used the wrong version of fastboot. It was already installed on my Mac so when I was running the flash-all script it was actually running the system version.
So I modified the script to make sure the path to fastboot was actually pointing to the good version.
And voilà, it took about 7 minutes after reboot.