Develop Bugs

USB Device Not Recognised on Bootloader

I have a problem. My Exec is stuck on the bootloader screen. All I see is Serial at the top, and v1.00 at the bottom.
When I connect my exec via USB, the screen continues to say Serial (rather than switching to USB) and the PC I connect to 'installs' the device as 'unknown device' in device manager.
I've seen mention of the problem elsewhere on the site, but the only solution I can find seems to be to keep trying, and eventually it's recognised. So far, after three days of trying, it has not been recognised.
I am aware of Buzz tool to get the device out of bootloader mode, but that required a connection to be established, which at the moment, I can't do.
Has anyone got any experience of this, or any ideas as to what's causing this, or how this can be fixed? I have tried uninstalling the 'unknown device' from device manger, restarting the PC (and hard reset of the Exec) then reconnecting, but the same thing happens every time.
Any ideas would be appreciated, as I'm currently staring at a rather expensive paper weight.

Try this it shld work
hdubli said:
This is based on my experience with two UNis..one Exec and other JASJAR..both had same problem...this is how I solved :
-Put yr device in bootloader Mode
-Disable USB in Active Sync
-Now connect woth USB cable and open mtty utility
-Select the "WESUSB... " port
-You shall see a blank white screen..press Enter to get "USB>"
-Then type ( as BUzz has informed) set 14 0
(here I wud like to inform that after doing the above I did not get success so I typed set 14 10,then set 14 9 for two three times)
-Then I ran the ROM Upgrade directly(After enbabling the USB)
-I then followed the procedure as informed on the COngratulations Screen that is hold the two "-" buttons and soft reset and then pressed 0
-I got them back to normal..
I hope this helps to all my friends...Pls feel free..pls do not trouble our Buzz..he might be busy in inventing something more to our devices
Click to expand...
Click to collapse

Guru Meditation said:
I have a problem. My Exec is stuck on the bootloader screen. All I see is Serial at the top, and v1.00 at the bottom.
When I connect my exec via USB, the screen continues to say Serial (rather than switching to USB) and the PC I connect to 'installs' the device as 'unknown device' in device manager.
I've seen mention of the problem elsewhere on the site, but the only solution I can find seems to be to keep trying, and eventually it's recognised. So far, after three days of trying, it has not been recognised.
I am aware of Buzz tool to get the device out of bootloader mode, but that required a connection to be established, which at the moment, I can't do.
Has anyone got any experience of this, or any ideas as to what's causing this, or how this can be fixed? I have tried uninstalling the 'unknown device' from device manger, restarting the PC (and hard reset of the Exec) then reconnecting, but the same thing happens every time.
Just noticed your user name, I was a big Amiga fan a few years back, still fire up Amiga forever occasionally on my PC when I feel the need.
Any ideas would be appreciated, as I'm currently staring at a rather expensive paper weight.
Click to expand...
Click to collapse
Try it with a different USB cable or in a different USB port (don't go through a hub and if you've been using a laptop then try it on a desktop PC since some laptops have hubs built into them). If that doesn't work then you're out of luck as your Universal isn't detecting that you've connected to your PC and its time to send it in for repair.

Thanks Niketkumar - unfortunately it's the step before your suggestion kicks in thats the problem - the device won't connect to the PC, so when using mtty WESUSB..... isn't an option, only COM1 and COM2.
Shuflie, I've tried with three separate USB cables on a laptop and desktop (neither through a hub, and the same device has worked fine on both laptop and desktop before).
I fear a trip to the doctors is in order ...
Very frustrating because the PC sees a device, but installs it as unknown device. Anyone know if theres a Windows CE device driver that I could try and install as an overide (i.e. in device manager on the PC go to update driver and browse to a WinCE.inf or equivalent?)
Failing this, has anyone got any clue what needs to be fixed? Or how much it might cost?

i am stuck on the same problem and wondering the forum for almost 3 days now with no luck.... please help my device is in boot loader mood but not turning the serial to USB ......... please HELP.......

solution
Guru Meditation said:
Thanks Niketkumar - unfortunately it's the step before your suggestion kicks in thats the problem - the device won't connect to the PC, so when using mtty WESUSB..... isn't an option, only COM1 and COM2.
Shuflie, I've tried with three separate USB cables on a laptop and desktop (neither through a hub, and the same device has worked fine on both laptop and desktop before).
I fear a trip to the doctors is in order ...
Very frustrating because the PC sees a device, but installs it as unknown device. Anyone know if theres a Windows CE device driver that I could try and install as an overide (i.e. in device manager on the PC go to update driver and browse to a WinCE.inf or equivalent?)
Failing this, has anyone got any clue what needs to be fixed? Or how much it might cost?
Click to expand...
Click to collapse
Please follow the steps:
1. Plug in ur usb cable in bootloader mode while it is showing 'serial' and version 'x.xx'.
2. Soft reset by pressing Backlight+power+reset pin WHILE KEEPING THE USB CABLE CONNECTED
3. your phone will now reboot into 'usb' mode. Don't remove the usb cable yet.
4. Remove the Memory card while keeping the usb cable still connected and VOILA,your pc starts recognising your phone as Microsoft usb sync.
5. Do whatever you want to do now (upgrade)
Hope it solves the problem now.
Press thanks if it does.

Something else to try
Having had a few issues with my G3 Uni, I've been through my fare share of Uni bootloader issues. When I find that I can't get the 'serial' to go to 'USB', I normally find it's because I haven't taken the memory card or the SIM card out (usually the memory card).
Make sure your memory card is out, then try to enter the bootloader and see if this cures it. If it does, then use mtty and the command 'set 14 0'
This tells it to reboot on reset. if you were to use 'set 14 1' it would go back to the bootloader on reset.

my Htc hd2 t-mobile won't recognize usb on boot-loader mode
hey guys i have a big problem!!!! my Htc hd2 t-mobile won't recognize usb on boot-loader mode. Here is the story my phone was running android 2.3.7 cyanogen 7 but i wanted to update it to ics android 4.0.4, So to do that i restarted my phone while holding down the down volume button and the boot-loader with the three colors came-on saying serial but when i connect my usb cable it won't show usb. even when i tried to run the dft.exe it shows an error saying usb connection failed. BY the way it lets me access the sd card using the usb cable on my pc, so i don't know what the problem is. PLEAS HEALP i am begging u guys pleas!!!!!!!!!!!!!!

kaleb2954 said:
hey guys i have a big problem!!!! my Htc hd2 t-mobile won't recognize usb on boot-loader mode. Here is the story my phone was running android 2.3.7 cyanogen 7 but i wanted to update it to ics android 4.0.4, So to do that i restarted my phone while holding down the down volume button and the boot-loader with the three colors came-on saying serial but when i connect my usb cable it won't show usb. even when i tried to run the dft.exe it shows an error saying usb connection failed. BY the way it lets me access the sd card using the usb cable on my pc, so i don't know what the problem is. PLEAS HEALP i am begging u guys pleas!!!!!!!!!!!!!!
Click to expand...
Click to collapse
you have the wrong forum friends! This Htc Universal section
to update Android on HTC HD2, you can use the Clock Work Mod Recovery !! for more details should refer to this thread http://forum.xda-developers.com/showthread.php?t=1021837

I-MATE JASJAR hung
Guru Meditation said:
Thanks Niketkumar - unfortunately it's the step before your suggestion kicks in thats the problem - the device won't connect to the PC, so when using mtty WESUSB..... isn't an option, only COM1 and COM2.
Shuflie, I've tried with three separate USB cables on a laptop and desktop (neither through a hub, and the same device has worked fine on both laptop and desktop before).
I fear a trip to the doctors is in order ...
Very frustrating because the PC sees a device, but installs it as unknown device. Anyone know if theres a Windows CE device driver that I could try and install as an overide (i.e. in device manager on the PC go to update driver and browse to a WinCE.inf or equivalent?)
Failing this, has anyone got any clue what needs to be fixed? Or how much it might cost?
Click to expand...
Click to collapse
Hi every one,
i have a serious problem with my HTC I-MATE JASJAR what's blocked in white screen (Serial / USB) and i cannot do anything on it, no boot, no reset soft, no reset Hard, no upgrade.
The issue is related to:
I tried to upgrade Radio ROM from 1.09.00 to 1.12 and i'm using Windows 7 Pro and when starting Flash, my PC shutdown because an electrical issue and since that, i cannot boot my device, i cannot flash or reset, my device is hung on white screen with Serial when no USB cable bluged in the PC and USB when Cable is pluged.
I Tried many times to boot it but no response, it's still hung and nothing can move on it.
I Just have one detail: when i plug the USB cable in my PC, the device is reconised but when starting upgrade or flash, i have error 101, no connexion.
Plz someone help me

bechir2013 said:
Hi every one,
i have a serious problem with my HTC I-MATE JASJAR what's blocked in white screen (Serial / USB) and i cannot do anything on it, no boot, no reset soft, no reset Hard, no upgrade.
The issue is related to:
I tried to upgrade Radio ROM from 1.09.00 to 1.12 and i'm using Windows 7 Pro and when starting Flash, my PC shutdown because an electrical issue and since that, i cannot boot my device, i cannot flash or reset, my device is hung on white screen with Serial when no USB cable bluged in the PC and USB when Cable is pluged.
I Tried many times to boot it but no response, it's still hung and nothing can move on it.
I Just have one detail: when i plug the USB cable in my PC, the device is reconised but when starting upgrade or flash, i have error 101, no connexion.
Plz someone help me
Click to expand...
Click to collapse
look here
http://forum.xda-developers.com/showpost.php?p=5456317&postcount=6
the first point...

A lot easier than to root this device

[q] • • • DONATING TO WHOEVER SOLVES MY PROBLEM • • •

[q] • • • DONATING TO WHOEVER SOLVES MY PROBLEM • • •
My device is stuck at Serial - v1.01 screen
• Bootloader mode (backlight+power+reset) doesn't work
• SOFT KEYS + RESET give 2 options (press 0 or X)
• My Windows 7 recognizes the device, although as an Unknown Device.
• I can enter MTTY through COM1 port but I can't type anything (ENTER key doesn't work, normal letters don't work, CTRL + V works, DELETE works - idk whats the problem).
• Can't flash - different errors occur (some ROMs give 101 connection error, some 112 error)
• I have browsed this forum for 4 days and found many tips - none of them worked
• Device starts blinking Serial/USB when entering USB cord (sometimes blinks and stays at USB)
PS: I found an interesting thread about win7 and its drivers - it was said to update my Mobile Device driver to XP one but the problem is, I don't see Mobile Device in my Device manager. I only see Unknown Device at Serial Bus Controllers.
WILLING TO DONATE TO THE ONE WHO SOLVES MY PROBLEM AND GETS MY DEVICE UP & RUNNING

Welcome to forums
I would suggest using a Windows XP machine to perform flashing and perhaps a Doc format
Good luck,

paulsrik said:
My device is stuck at Serial - v1.01 screen
• Bootloader mode (backlight+power+reset) doesn't work
• SOFT KEYS + RESET give 2 options (press 0 or X)
• My Windows 7 recognizes the device, although as an Unknown Device.
• I can enter MTTY through COM1 port but I can't type anything (ENTER key doesn't work, normal letters don't work, CTRL + V works, DELETE works - idk whats the problem).
• Can't flash - different errors occur (some ROMs give 101 connection error, some 112 error)
• I have browsed this forum for 4 days and found many tips - none of them worked
• Device starts blinking Serial/USB when entering USB cord (sometimes blinks and stays at USB)
PS: I found an interesting thread about win7 and its drivers - it was said to update my Mobile Device driver to XP one but the problem is, I don't see Mobile Device in my Device manager. I only see Unknown Device at Serial Bus Controllers.
WILLING TO DONATE TO THE ONE WHO SOLVES MY PROBLEM AND GETS MY DEVICE UP & RUNNING
Click to expand...
Click to collapse
When i am home i can help you!

d-two said:
When i am home i can help you!
Click to expand...
Click to collapse
My MSN - MOD EDIT: REMOVED EMAIL

orb3000 said:
Welcome to forums
I would suggest using a Windows XP machine to perform flashing and perhaps a Doc format
Good luck,
Click to expand...
Click to collapse
I have tried on 2 XP machines - laptop and PC both
Maybe the problem is that its COM1 port that works and mtty doesn't let me type anything.
How could I get USB port to work ?

paulsrik said:
I have tried on 2 XP machines - laptop and PC both
Maybe the problem is that its COM1 port that works and mtty doesn't let me type anything.
How could I get USB port to work ?
Click to expand...
Click to collapse
I am now Home but it is too late... Sorry, tomorrow i am back home earlier...

i wrote instruction here about flashing with windows 7. update your "unknown device" driver like it was described. do you have x86 or x64 edition? and have you removed sd and sim card?

Forgetting to remove the SD card is usually the problem. You really need to do that, it's not optional. If it's not the SD card, select the unknown device in device manager, right click, delete the device and reboot. Then try the usual instructions on flashing under Win7. Disable USB connections in WMDC. Put device in bootloader mode and connect it. When Mobile Device appears in device manager, update to the correct drivers. Try rebooting between steps if you get stuck. My drivers seem to get corrupted from time to time for whatever reason and this works for me. You need to see and select the USB option in mtty, it won't work otherwise.

l2tp said:
i wrote instruction here about flashing with windows 7. update your "unknown device" driver like it was described. do you have x86 or x64 edition? and have you removed sd and sim card?
Click to expand...
Click to collapse
I only see Unknown device, not Mobile Device or something else.
Unknown device driver can not be updated.
I have removed both cards, SIM and SD.
onurdndar said:
Forgetting to remove the SD card is usually the problem. You really need to do that, it's not optional. If it's not the SD card, select the unknown device in device manager, right click, delete the device and reboot. Then try the usual instructions on flashing under Win7. Disable USB connections in WMDC. Put device in bootloader mode and connect it. When Mobile Device appears in device manager, update to the correct drivers. Try rebooting between steps if you get stuck. My drivers seem to get corrupted from time to time for whatever reason and this works for me. You need to see and select the USB option in mtty, it won't work otherwise.
Click to expand...
Click to collapse
Removed both cards, I've seen that tip around.
As I said my device stays at Serial/v1.01 screen when pressing BACKLIGHT+POWER+RESET. Only Soft buttons + reset work, brings 2-option screen with white background (0 and X).
As I also said, I have tried same thing over and over in 3 different computers: laptop with XP, PC with XP and another PC with WIN7(current).
Installed ActiveSync from original SPV M5000 CD to both XPs, still doesn't flash and mtty still opens only COM1 port (COM4 for laptop).
I think if I could get MTTY to work, I'd be okay. But how can I get USB port working ?

If you've done everything offered here, the remaining options are faulty USB cable and faulty USB socket.
By the way, this is not the kind of thing people donate for around here. I'm personally not trying to help for any theoretical reward.

onurdndar said:
If you've done everything offered here, the remaining options are faulty USB cable and faulty USB socket.
By the way, this is not the kind of thing people donate for around here. I'm personally not trying to help for any theoretical reward.
Click to expand...
Click to collapse
I am very frustrated and willing to do whatever it takes to save my device.
Now are you saying its both, USB cable and socket that are incorrect or just one of them. Please give me an example which cable do you use.
Thanks

If at the beginning you were able to see your device from W7,than your cable and every thing is ok.
your stock with a device with no rom,so i think this is why your W7 don't see your wince phone.(it could be to a rom error or fault of manipulation done by you!!!battery for example,etc...).
solution:
1)go to a close htc support technician close to you and he will load a Rom to your phone Board.
2) PM me to sell and chip you my HTC Universal,,

[GUIDE][SOLUTION]MediaTek SPFlashTool failure - Disconnect after 2 sec is by design!

Hey everyone
This mostly applies to those of us that have a bricked MediaTek device. Yes the ones amongst us that are the most desperate I am sorry to say. Some of you laugh at that cause your Flashing experience has worked perfectly from the get go and you have flashed successfully with functioning device. Well that's great. Good for you! You're awesome. Sooner or later you are going to make a mistake and panic is going to set in and you will be where I have been. I am sorry to say that is not a very nice place.
For me it was not my device which makes matters worse. I was translating a device for an older gentleman who purchased it from Alibaba; it's an MTK6589 device to be precise.
Anyway I am sure a lot of you out there are frustrated with why your device is doesn't work with SPFlashTool even though you have been following the most of the tutorials to a T? Why your device disconnects from device manager 2 seconds after you plug the thing in and it disappears out of the device list? Like WTF right? Well would you look at me strangely if I said that this is actually by design? That yup your MediaTek device is actually meant to do that?!
If you have experienced this, then I have answers for you and I have an explanation as to why your MediaTek device is doing this, and why your device has not been able to be flashed by SPFlashTool.
Really we are our own worst enemy when it comes to this MediaTek woes; Why? Cause we are impatient and we go off looking for answers in the wrong direction when in fact they are right in front of us all along. Here I will hopefully expand your understanding about these devices and why/how things work so that you can apply it in the future.
I will explain my situation and what I discovered in the process. Hopefully it sheds some light on disconnect device driver situations and lays some thing to rest....hey maybe even some of you who had given up and tossed your cheapo China phone in the bedside draw cause nothing worked and it wasn't worth the price to send back, maybe you guys might want to give this a go and revive your MediaTek device?
Follow this guide step by step BUT READ EVERY STEP EVER SO CAREFULLY.... also take note of the points below that I am going to emphasise that AREN'T emphasised anywhere in this tutorial nor any other tutorials I have followed, so pay attention.
http://forum.xda-developers.com/showthread.php?t=1982587
The part that is not emphasised is this
Turn off your phone, remove the battery and replace it after some seconds (and don't turn on the phone).
Press F9 (or hit Download button) and connect your phone into the computer via USB data cable.
The process will start and a red progress bar will appear.
Click to expand...
Click to collapse
In both cases the word 'and' should be replaced with the word 'THEN' so that people will understand.
What isn't really mentioned on any tutorials is that the MTK6589 is different to how you flash other mediatek devices with SPFlashTool; why? Because you MUST put the battery back in before you flash unlike other MTK devices where they explicitly say DO NOT put it in and/or that you should flash without the battery in place. THIS IS INCORRECT!
Next thing to emphasise is this: You must have the phone disconnected when you click on the download button inside SPFlashTool. You press download then you put the battery back in your phone with the USB connected to the phone., wait and when the download part finishes (only a few seconds) THEN you plug the phone in to the computer (yes with the battery still in place) but do not switch the phone on.
When the phone is detected by Windows and starts to load the drivers like it usually does and then disconnects...well what happens now is that when it loads drivers for a second SPFLashTool engages the phone and holds open the connection. It will pause for a couple of seconds (but you will notice it doesn't disconnect) and then SPFlashTool will show a red/orange progress bar that goes quickly....then it will write the firmware when you see the yellow progress bar.
Something to note here (I downloaded literally hundreds of drivers by the way) that you only need 1 driver and that is the one mentioned in the tutorial.
You don't need to do all the bullsh!t with device manager and removing drivers etc with USBDview....this should only be if the phone doesn't read initially as MTK65xx preloader OR doesn't end up registering as MediaTek DA USB VCOM.
So I will explain...when you plug it in on a clean WIndows 7 PC for he first time it will appear as MTK65xx preloader under device manager under unknown device and Windows will attempt to download the correct drivers and then fail. This is normal.
DO NOT GO AND INSTALL PDANET DRIVERS!!! This doesn't work.
Yes the drivers ARE more stable and don't disconnect nearly as much as the other MediTek drivers, however what this does is register the devices as an Android ADB device, and allows you to use ADB. We want to use SPFlashTool, not ADB at the moment.
Installing other MediaTek drivers after PDANet for some reason causes a conflict and interferes with communication with the device?? I suspect that this is what was causing much of the issues I was experiencing? You may use the PDANet drivers after you have flashed via SPFlashTool if you cannot get an ADB connection, however in my case once the new firmware was written to the device and it was restored and fully functional; when I plugged it in the ADB drivers loaded automatically anyway
Ok next points to make. Unplug your device. Install the drivers (I have attached the ones that worked for me). NOTE: You may need to log in allowing unsigned drivers as mentioned in other tutorials. To do this you can use EasyBCD, go into advanced settings for the Windows 7 bootmenu entry and allow the use of unsigned drivers and put a wait of say 10seconds on the menu count down (in stock form Windows has assigned 30 seconds but standard it bypasses the boot menu - this makes it harder to press the F8 key during boot up). After finishing in EasyBCD reboot and when you come to the Windows boot menu press F8 anyway and choose allow use of unsigned drivers. This is a just in case thing.
Get EasyBCD from HERE
Once in Windows, plug in your device WITH THE BATTERY IN and device switched off. Open Windows device manager (a quick way is type devmgmt.msc in Start menu or Run menu from the start menu - if you search for the management console by full file name you can right click the devmgmt.msc and pin it to the Start menu this is what I have done).
In device manager you NEED to see the device registered as MediaTek DA USB VCOM. If it is not appearing push the volume up button + but keep the phone OFF. When it appears for just a second make sure it is MediaTek DA USB VCOM. *This is important* It must NOT be registered as Preloader or any other MediaTek driver ie. Preloader USB VCOM port OR MediaTek USB VCOM (Android) etc. IT MUST BE MediaTek DA USB VCOM Just look for the one that has DA in the name and is a VCOM driver. This is the driver we want:good:
Ok here is where I will mention that USBDview removal of drivers is not necessary and does absolutely nothing anyway because Windows 7 remembers every single driver you have installed regardless of the fact that you have removed/uninstalled and even checked the box delete drivers or what ever. It doesn't matter...every driver you have ever tried will be in the device driver list. USBDview is only good for unregistering the device association with a registered driver. It doesn't remove drivers.
So now where was I? Ahh right, yep. When you plug in your device (switched off and the battery in place) and it appears momentarily in device manager it must be MediaTek DA USB VCOM, If not Or if it disappeared too fast; just push the volume up button again and this time as it appears quickly, click to expand the (PORTS COM &LPT) listing, then quickly right click the MediaTek listing and go to Update Driver Software. You may need to do this several times to get it. Unplugging the USB from the PC and plugging it back in again may help.
Resist the urge to search for new drivers as the device IS actually detected but not as a PORTS COM &LPT, and doing so will be fruitless as you will only assign the incorrect drivers to the incorrect function. So unplug and replug it in again pressing volume up.
Note: It does not matter if the device disconnects and disappears out of Device Manager when you are in the Upgrade Device Driver software menu....this is normal. The most important point here is that the correct driver is being registered to the correct device protocol (pressing the volume up button to get COM&LPT).
The device needs to appear as MediaTek DA USB VCOM and this must be registered specifically to the (PORTS COM &LPT) in device manager. If it lists elsewhere as a USB device and has the MediaTek DA USB VCOM driver assigned to it, then you need to uninstall the driver from the device listing and start again. Don't go looking for more drivers PLEASE!
Click for explanation
Ok I will digress again for a moment to explain why all this is so important and what many of us are not realising especially with all the tutorials around; the important point here is that MediaTek devices may be listed many numerous devices in device manager and this is normal. They could be an ADB android device, a MediaTek USB Port version etc and these are not the functions we want to use for flashing with SPFlashTool are they? I know when I plug in my Galaxy S3 it loads at least 5 different drivers! Same with these devices.
We need to have the (PORTS COM &LPT) registered as MediaTek DA USB VCOM and this ONLY achieved when we press the volume up button!! If the device disappears from the list after plugging it in and appears as something else and then we register the MediaTek DA USB VCOM driver to this function we are likely trying to use the MediaTek DA USB VCOM driver to load the MediaTek USB Port function and this is obviously NOT the protocol that SPFlashTool is using to communicate with the device to write new firmware.
Ok I will continue now, once you have got into the Upgrade Driver Software menu,
Go to 'Browse my computer for device software',
Then select the second option 'Let me pick from a list of device drivers on my computer', just choose the 'show all' at the top of the list
Next you *should* see MediaTek DA USB VCOM listed in amongst various MediaTek drivers., select this one.
* However if you do not see MediaTek DA USB VCOM listed in the list there then uncheck the box next to 'Show compatible drivers' and it should now show a few more drivers.
You may need to scroll in the right menu bar down to MediaTek.
You will be hit with an overwhelming list of MediaTek drivers! See Pic for reference
Select the required MediaTek DA USB VCOM driver from the list. If its not there (then and only then) you should try install another set of drivers and restart the process again. Try the drivers I have attached below first though.
At this point please resist the urge to click 'Have disk' then 'Browse' to and go scouting for a specific driver in the hopes that this will be the one; THIS IS WRONG! and should not be recommended like it is in just about every tutorial I have seen so far.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's funny how even the drivers you previously removed are included in that list eh? You know...the ones that everyone told you, you need to delete bla bla bla...THEY ARE STILL THERE DAMN IT!
Once you have selected the driver as MediaTek DA USB VCOM and closed out of the menu you will notice that it has actually gone from the list in device manager? This is normal. The driver is only meant to appear when we do a specific thing and that is pressing the volume up button to write firmware using SPFlashTool and nothing else.
As I mentioned earlier, this is by design. You will note that MediaTek devices, have these protocols USB Mass Storage, MTP, PTP, ADB and COM &LPT.
Now unplug your device. I would at this point do a reboot of Windows (again ensuring unsigned drivers by pressing F8 - just incase)
Once you're back inside Windows, open device manager again.
Keep the device off and have the battery in.
Plug the MicroUSB end into the device first (it's easier - trust me you will understand when I explain).
Now keeping it switched off but press and hold the the volume up button and then plug the cable into the PC USB port; watch as it registers inside device manager as MediaTek DA USB VCOM.
When it does, disconnect the cable from the USB port. - You are now good to go
Now Open SPFlashTool.
Select the scatter file.
Uncheck the following from the list (Preloader, MBR1, EBR1, Uboot, Sec_Ro, Logo, EBR2 and FAT - note fat is for the internal sdcard). We want to write to system, recovery and boot pretty much. If you have ruined your device with the incorrect preloader,
Keep the device UNplugged. Click the download button. You will see the purple progress bar but for only a very brief moment. This is ok and is normal.
IF you have completely obliterated your device by flashing an incorrect preloader click below
I have been advised that you may need to first flash the Preloader, MB1, EBR1,Uboot and EBR2) to setup the partitioning again. The preloader I assume is similar to a PIT file for Samsung devices?
Now we do as we did before. Plug the MicroUSB end in first to your device. Have it switched off but with the battery in place. Press and hold the volume up + button and then plug the cable in to the PC USB port again.
At this point you will hear the device register with Windows as you normally would however you should notice that it doesn't disconnect straight away like it normally does?
This is because the MediaTek DA USB VCOM is registered to the PORTS COM &LPT and SPFlashTool is listening on this port.
Then shortly after progress with a Red/Orange bar.
It will pause for a what seems like a long time..... but please leave the device plugged in! [shouldn't be longer than 10min - if it is you've done something wrong, disconnect and do the process again and read making sure you understand every one of the points I have made in this post]
Once you see the yellow progress bar you can breath with relief.
Congratulations you have just revived your bricked device! :good:
Additional Info: After a reboot when you plug the device into the PC USB port again you should start to see Windows identify the extra protocols associated with your MediaTek device. I noted than this one I was working on appeared back as an MTP Portable device, also as an ADB Android device further up the list and as an MTK USB Port when the volume up button is pressed (I guess now Windows knows what it is it is assigning it a different driver?)

But what if it doesn't disappear? I have the problem with ZTE V967s that i cannot flash it (probably dead), because I have "ENABLE DRAM FAILED (4032)" issue.
This is probably because the phone cannot exit the VCOM status, it is visible under this state for many minutes in device manager. Do you have any ideas how to solve this problem?

How i unbricked my Lenovo K3 Note (MTK6752)
Hi,
First of all I am thanking God Jesus Christ for helping me find a solution.
My Lenovo K3 Note was hard bricked when i accidently unplugged it while sp flash tool was flashing the firmware. The screen was not at all lighting up(Not even boot logo). When battery is inside and press power button i could see a feable red colour light near the proximity sensor. When i connect my phone to PC without battery (As many sp flash tool procedures says us to remove battery and connect) , it was not at all being detected by pc. This was my condition..!!!
I searched tried a lot for 5 hrs.. Continously.. Yes literally..
At last I started my own experiments. I downloaded complete stock firmware. and loaded it to sp flashtools by selecting scatter file. I selected the format+download option in sp flash tools. I clicked download button in sp flashtool. Now sp flash tool is waiting for my phone to get connected.
I removed the battery of phone, then i pressed the volume buttons, power buttons etc.. to remove static charges if present (for 10 seconds). "Then i put the battery back to the phone. "
I connected the usb cable to phone ,keep pressed the volume up key, then the other end was connected to the computer. SP flashtool detected my phone and flashing started(Now i released volume up key press). Wait for sometime till flashing completed and we get OK pop up in sp flash tool. Wait for some 10 seconds . Dont remove phone from computer. Press and hold the power button for switching on the phone without removing from computer.
If screen doesnot light up, release the buttons, remove the phone from computer . Press the power button two three times(Dont hold). Now press and hold power button to switch ON your phone. Thank God and Be happy seeing your phone booting up. :laugh::laugh:

if cant non-removeable battery(0% battery) for mtk phone. what shoud i do? power + volup ??? or something

problem install driver MOOREFIELD

Hi everyone,
My zenfone 2 ZE551ML is bricked, so i followed this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
The problem comes when i arrived to the step of IntelSoc:
I install it, no problem until here, i got IntelSoc driver in my device manager .
But when i want to have the MOOREFIELD driver, I cant get it. Following this perfectly
Ash back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables( I don't have hanging cables though, I just have the Logo Asus and write on the top in blue Fastboot mod !!!).
-Connect to your computer via USB cable, to standard Intel SOC driver position, wait a few seconds if the current add an item immediately below another MOOREFIELD new devices is successful.
-If You have not been, the test performed as follows: turn off the machine, plug the cable into the computer, press the power button until the device vibrates slightly, then release.
If you have an idea can you help me please. I think this is the only thing who blocks me in repairing my phone...
Thank you

Yea that problem also persists with my zenfone 2,cant install moorefield 'cause pc cant recognize my phone. Somebody please help us out.

Anagh21 said:
Yea that problem also persists with my zenfone 2,cant install moorefield 'cause pc cant recognize my phone. Somebody please help us out.
Click to expand...
Click to collapse
it is clearly instructed in that thread you mentioned. just keep few things in mind.. uninstall every mobile related driver before installing isoc. uninstall xFSTK tool if you already installed it before installing isoc. third as you are concerned about the line you mentioned morefield under intel soc. well during soc install you will see windows like attached below. at this stage you need to power cycle your device . ( turn off your device holding power button for 10 sec. then connect to pc and turn on. leave connected to pc and turn off again and turn on second time to make sure so driver are installed) don't worry if you don't see morefield under soc now. just go ahead and install xFSTK. now your concern that your device don't stays in morefield download stage ( i mean it appears in device manager and disapear) . after installing xFSTK. run it as administrator and load files. and change gp flag value. also change device detection timeout to 120. now click begin download it will start waiting for device. now turn off your device completely and connect to pc and turn on. xFSTK will force it to stay in required mode. if download do not starts. just power cycle the device while being connected to the tool.
( note: it is strongly recomended that you install isoc and connect mobile before installing. if you have already installed xFSTK then plz uninstall it and install it after performing above said steps. remove all other mobile related drivers also and if you are using windows 8 or 10 disable driver signature enforcement again even if you did it earlier)

The problem with asus flash tool solved
Solution : Open device manager i.r. Windows + X .... if your phone is not being detected... switch it on and off ... there will be ( other devices menu ) that will show your phone there..
right click on the phone , click update drivers, ofcoarse no drivers online, locate the drivers manually , wherever your bootloader file is i.e. the 1 gb file you download or the raw file as we can speak ... i didn't pin pointed it ... my file was on the desktop so I just chose desktop and it searched it and installed it.
After that the phone was successfully in the computer and being detected by the flash tool.

MTK MT6753 Tablet bricked... badly...

It's a Voyo's i8 pro 4G, i downloaded the officialy android 7 rom and used sp flash tool to flash the rom.
I choose the official scatter file and it'd loaded successfully.
I clicked download and connected my "power-off" tablet to win 10 via USB, it quickly recognized my tab and showed hardware info on the bottom right...
i went on for a sec and then a windowed message popped up that said something about "download...", it disappeared quickly and then everything stopped, nothing change on progress bar ....
i waited for a while and decided to quit... disconnected my tab and close the program, hoping to start everything again...
no USB detection of my tab, the tablet doesn't even turn on now, screen is all BLACK...NOTHING.....
tried to installed MTK USB driver in win 10 ( followed online guides) but got code 10....
May I ask what else I can do now? any advise will be greatly appreciated! THX!

Just reflash with SP-Flash Tool. If SP-Flash Tool doesn't detect your device you need to unplug the Battery and connect it after that to your PC