[Android Software/Hacking General [Developers Only]] Donphillipe:
I don't think this device is supported by Smart Phone Flash Tool v5.13.35.2.

Hardware : MT6582

Model : STUDIO6.0HD

Build number : BLU-D650a-i-V25-GENERICK

Build date UTC : 20140717-035318

Android v : 4.4.2

Baseband v: RF9810_GSM4_W1258_MT6582_MP_V0.0.2_S0609, 2014/06/09 15:34

Kernel v : 3.4.67 (mudingyu@compiler5-desktop) (gcc version 4.7 (GCC) ) #1 SMP Thu Jul 17 11:49:58 CST 2014

Uboot build v : -----

LCD Driver IC : 1-otm1283a_dsi_vdo_hlt_hd

I first downloaded the SDK USB drivers and added the BLU 6.0 hardware IDs to the androidxxx.inf file and that got MTK Tools and adb talking to the phone. I was able to complete a MTK backup but I wanted to test Flashtools in case I ever wanted to restore that. I have spent 30 hours on this. Everything I read says powering off the phone makes flash tools able to somehow communicate with the phone. Not sure how that is possible with this phone. I do get a USB awakening with the battery charging with the phone off and the USB cable attached. Should that be the point Flashtools is able to communicate, because that isn't working on this phone. And that is after deleting the SDK drivers, installing the MediaTek Preloader VCOM (code 10) and all and that didn't seem to help.

After hours and hours I finally discovered that using the command "adb reboot bootloader" puts this phone in fastboot mode. In fastboot mode a command from the MKT tools ADB console "fastboot devices" produces :

C:\MtkDroidTools v2.5.3>fastboot devices

mt6582_phone fastboot

........ so I assume the driver is working. Now this is the same regardless if I am using the SDK USB drivers or the ones from Mediatek

It is also not clear if the flash tool menu is supposed to indicate anything, errors or success.

I ran it overnight last night and all it did was build a 100M console log. No flash tools ROM created.

******** After 40 hours I have it working. There are way too many quirks while going through this process, such as that the Media Tek Preloader USB VCOM driver must be installed first, followed by another ADM driver such as from the SDK, and if a unique device like the Blu, with its xxxxx.inf file modified to contain extra entries with the Hardware IDs of the phone in question. Plus it turns out, SP Flash Tool has to be all set up and running waiting for a USB interrupt from the phone which is created when the phone in off mode (battery charging) has its USB cable removed and re-inserted. (This seems so easy after you do it the first time ;) Only this careful selection of drivers and installing them in the right order, setting up the tool to wait and cycling the USB cable will trigger the SP Flash to tool take off transferring data one way or the other and from an otherwise-considered powered-off phone. It's done through a COM port attached to the USB apparently. (In this world, the word "off" certainly has a new meaning.) And I also found that SP Flash Tool has nothing to do with the "fastboot" utility of the SDK, which incidentally I could only find that it could enabled on the Blu devices via an ADB command of "ADB reboot bootloader". Incidentally if you play with this to do any of the fastboot options, in order to exit "fastboot" hold in the PWR+VOL UP or PWR+VOL DOWN (depending on if you ran anything like iRoot which has switched the Factory/Recovery optionsm as well as changing Factory boot option to Chinese). Note: Fastboot has nothing to do with SP Flash tool.

Otherwise, it can be done after quite a lot of research.

My progress so far is I have created a backup from MTK droid tools, and from that created a scatter file and "prepared files for SP tool" (and with no clue how to restore them still from my research.

Still confused on how much is too little or too much to back up with SP Flash tools - do I back up the whole thing if I am going to restore to the exact same phone and if so, exactly what scatter check boxes are checked and want is my data length on the Readall page? Nice to know also would be how do I share this image with others who have bricked their Blu Studio 6.0HDs (there are no ROMs in the immediate circles) and what considerations would I consider for backups before I put my personal data into it, and what effect will the wrong IMEI have on them and am I exposing myself by sharing my IMEI within this ROM is someone else needs it?

Then with all the helping other people aside, how do I use this various stuff for my own benefit, like making a full system restore of my phone exactly as it is today. I just ran a Read all and I ended up with 750M from a phone with about 1.4G of internal storage occupied, so something fell short somewhere. Perhaps it was using the beginning physical address of the Cache section from the scatter file as my Redall "data length" and all the other is just dead space. But with this as my first Android and first experience with all this, I haven't a clue.

So anyway, I am still trying to capture a single "full backup" I feel comfortable with so I can move forward to re-customize my phone and start using it. Turns out I am just taking advantage now of capturing a "Factory Reset" image, considering all the stuff I lost after first running iRoot2, getting hung up in a Chinese text Factory boot menu and like a fool, exiting on the Chinese version of "Factory Reset". I guess if that is the only mishap to the root I am doing, then great. Still I'm working on how to add CWM on this phone and trying to work around MTK droid tools already saying "already patched" when I attempt to add it.