What do you mean by "forced installed the driver"? If it was me, the next step I would try if you haven't already is to remove the drivers, go back into the "USB-Burning-tool-v220.127.116.118" package and install the drivers from the "AmlogicusbBurningdriver" folder again. If that doesn't work, the next I would do would be to check and make sure all of my computers drivers were up to date. You could, for example, have a generic or old USB port driver installed instead of the one recommended by your manufacturer, which is causing the device to disconnect repeatedly like that.
Hmm I will try messing around with the USB drivers. So your guess would be that there is a driver miss-communication between the port and the device right? I am trying to narrow down the possible causes for this problem, that's why I am asking.
Maybe SPL cannot load because when I open my device in recovery mode (PWR+Home) instead of the typical android icon, I get a modified icon (from the TWRP recovery probably). Maybe the recovery messed somehow with my bootloader causing an error in the communication between the AML flashtool and the device?
Is this a possible scenario or just bollocks?
I would try installing other USB drivers for my ports and reach back to you! Thanks again so much for the insight
EDIT: With forced installed the driver, I meant that it was recognized as a generic "Android" device from device manager, then updated the software for the "Android" device pointing to the folder that you said as well, installing the WorldCup Driver for the device. By forcing, I mean this procedure instead of being instantly identified by the system as "WordlCup Device"
Edited by kaloboli, 25 March 2014 - 10:46 AM.