[Android Q&A, Help & Troubleshooting] Old faithful:
Thank you for the encouragement, but it simply doesn't work, I have NEVER seen such a frustrating driver to install, I mean, I've been on it for the past 8 hours with no progress whatsoever. Some of the things I've tried:

- Loading the driver this way. The damn device , when it actually shows up, does so for only a fraction of a second. Literally. If you've tried on that USB port already, too late, won't show again, you'll have to try on another USB port. At the 4th attempt (my LAST USB port!) I was able to select load a driver for it... And Windows tells me I already had the best driver installed. AAAAARGH!

- So I uninstalled all instances of Mediatek and Lenovo in USBDeview and in Device Manager using Shown Hidden Devices, and tried three different driver versions. None of them work with SP Flash, and none load the same devices anyway. In other words, the picture I posted, I wasn't able to get it to show that device anymore and frankly, can't remember which driver I used to even get to that state.

It doesn't show there, actually, it doesn't show at all anymore: if you've tried once and weren't able to catch it, it doesn't appear anymore.

I have reloaded registry backups and even uninstalled things in safe mode, same thing.

Oh, I can get the recovery loaded using its scatter file alright - No problem with that - But nothing happens at all when I click download and connect the phone. Device Manager briefly refreshes, but at this point it doesn't even show any new device anymore.

I sure wish it would - I have exhausted every possible solution I could think of now, and thank you for sticking around ;).

Maybe my next step is to try on another computer. Like I said, I have NEVER seen such a difficult driver to install!!!

Been there, done that.

Yes, and it is exactly the build version my tablet is running out of the box. In other words, with the ROM and the update I would be able to completely restore the tablet to exact factory condition should I require it. If I could get SP Flash to work, that is!!!

No, that would be A10-70F_S000118_150710_ROW

When I flashed my Note 2 three years ago I was very careful to make sure I wouldn't have any problems, and learned to use Odin, but never had any driver issues with it like I am having with SP Flash tool. This really has me stumped...

I agree. Nerds and engineer types aren't the most forthcoming folks when it comes to explaining how they do things. I am often criticized for it ;) But let me tell you this: when I get this thing going, I WILL make an extensive write up on it, because it is dead wrong and criminal for corporations such as Google to make products defective like this.

I have made many searches online and simply cannot understand why no one has sued Google yet for deliberately damaging products through software. 40 years ago, any company making products like that would have seen its principals prosecuted in criminal court. I am truly, fuming mad. And glad to have an understanding wife who's had to suffer loneliness in bed for the past week or so while I go to war against slavery ;)

I have read many tutorials, some very detailed on how to clean the computer from failed driver installs, and nothing has worked. I am starting to think that perhaps my 5 year old install of Windows Vista is the problem, although it has been tweaked and works exceedingly well otherwise (one example of a problem I have not been able to fix is the NET framework - simply haven't been able to uninstall and reinstall it, and I tried everything even the command line tools straight from Microsoft - as a result I cannot use any software that relies on it)

Tomorrow (it is already tomorrow, but I meant after I get some sleep) I'll see if I can't get it to work on my Windows XP machine - I wouldn't be at all surprised if it worked on it... Maybe I should simply kick myself in the butt, get all my stuff backed up and FINALLY UPGRADE my main computer to this machine to XP and at the same time figure out how to UPGRADE the tablet to Ice Cream Sandwich and be done with all the hassles ;)

Definitely - doing it low level is be the only real way to go. If I could find a way to sideload the recovery and the whole ROM through the command line interface and avoid all the SP Flash Driver hassle, I would!

It works fine with me... The device is read at an MT8165, which it is, the build date is read correctly, the blocks info is read alright, and if you edit the ini file so that the 8165 is made equivalent to the 6752, you can even write a scatter file for it, unfortunately it is not recommended to use it because the tool is NOT compatible with the latest chipset and android version and I'm certainly not interested testing whether I can brick it or not, there are enough opportunities for that to happen as it is!

Have a look...