HI guys i hope write on right thread, however if not , please move it.
I downloaded this tool http://www.mediafire.com/download/msjbh3cut9bc5im/SP_MDT_src_v3[1].1344.00.00-TestVersion-2.rar
i have a phone with MTK6592
i try to use it but the software give me error like picture
The problem is seems not recognized the COM, but i try also to remove and reinstall driver
The problem also is the old version of SP_MDT work fine with other MTK and recognized fine the com port.
What can i do??
Related
can someone help me urgently !!!!
i need the usb drivers for my milestone to windows7 64 bit version, the ones in the sticky link dont work
im stuck at bootloader and i need to flash it again through rsd lite can someone please help before i ran out of battery !
tks
mousiope said:
can someone help me urgently !!!!
i need the usb drivers for my milestone to windows7 64 bit version, the ones in the sticky link dont work
im stuck at bootloader and i need to flash it again through rsd lite can someone please help before i ran out of battery !
tks
Click to expand...
Click to collapse
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Just had to google it..
i already tried those still gives me an error on the usb driver ....
i think my windows is messed up
What's the error?
usb device not recognized properly
What does your bootloader screen show? Does it show OK to Program?
yes its all good
are you using usb cable that worked on your milestone before?
yep already switched usb cable too still doesnt recognize it , i came home for the weekend and already tried in my usual laptop where i already had drivers rsd lite and all the rest where i´ve done the procedure a gazillion times and still no luck my phone doesnt get recognized, is there something i can do? another software to reload the bootloader i don´t know whats the problem but now i know its in the phone and not in the computer
i have no idea where i pick this up, or it just come to me after reading multiple posts.
inspiration came from this thread:
http://forum.xda-developers.com/showthread.php?t=1225998
if there is a problem with your phone not get recognized in bootloader you cold try this:
get a second working in rdslite milestone go to the point when you should start flashing a sbf, plug the first milestone out, put yours in and hit start.
don't know if this works is just an idea.
good luck.
edit: this is as a last solution if you managed to brick the milestone of course you could try another pc or a virtualization solution and try in linux
The RSD Lite does not have the drivers included? you can try that
thats a good idea but i dont know anyone who also has a milestone ...
rsd lite drivers?
isn´t there another software where i can load another bootloader ? something that doesnt need the usb drivers?
mousiope said:
thats a good idea but i dont know anyone who also has a milestone ...
rsd lite drivers?
isn´t there another software where i can load another bootloader ? something that doesnt need the usb drivers?
Click to expand...
Click to collapse
RSD Lite is the only you are able to make any modifications to the bootloader.
Do you have experience on windows? you can install a side windows and try the drivers if not you can try uninstalling all the motorola programs and related with the phone and look for one of those programs that clean the registry like ccleaner or tuneup utilities and them install the rds lite again. I use RSD Lite 4.9 and it works perfect...
Did you install the program that came in the CD inside the phone box? it could be the reason...
You can try the first post on this thread: http://forum.xda-developers.com/showthread.php?t=932196&page=6 Sorry to hear that it isnt working
the problem is in the phone not windows ...
not sorry because i already sold my milestone like 4 months ago and the idiot who bought it made more damage to the phone in 4 months than i did in a year and a half using the phone
its his problem not mine because i gave him the phone as new, and i am just trying to help him
Hello,
I have phone H600 H640_77v01.01b01 replica for SGS3 (MT6577),but it is briked,when I connect it at my computer,only what can I see it is MTK USB Port (COM 28) in "Manage" ,no light,nothing else!
When I try to flash it with SP Flash tool I got some error after red line,only what can I do it is format.
What can I do to recognize it like MT65xx preloader? I need to press some buttons when I connect it to my computer?
Sorry for my little english!
are you sure this is an MT6577 based smartphone? how do you managed to brick it? flashed wrong firmware? we need some more inforamtions here. "some error" is something i cannot build onto. make a photo of the back of your device (without the battery) to identify your device. you`ll need to get a proper firmware for your device or it will be dead forever.
edit: found this software, this one MAYBE will work: http://4shared.com/file/IAkoq9Z5/
i didn`t looked into it, but is suggest you have to flash it using SP flash tool.
Hello!
So I am newbie in here, and I have huge problem.
I have bought Samsung Galaxy S4 I9500 Clone with MT6572 CPU, as for many people, MT6589 is fake, 2GB RAM is fake, you got only 256MB.
Ok, lets get started, sudenly it stopped working, but PC still recognize it trought VCOM drivers, so I tried to flash it trought SP Flash tool, at start it showed BROM EROOR, bla, bla, bla (4032) its comon error, so I fixed it, and was able to format system, before formating, I needed to put in battery, and only then PC recognized phone, after flashing, it recognizes without baterry. So I started to flash new ROM, and appeared error, that there is not enought space, I reconected phone, one more time same error, and in next time old BROM error was back, and I can't fix it this time.
As my phone switched off sudenly, I was not able to see HW info in MTK Droid Tools, cause I can't install ADB Drivers without USB debugging and switching phone on, and tis makes everything complicated.
So my question is, am I trying to flash wrong ROM or is it fault in drivers or what?
I will be happy for every helpful information. And thanks.
And sorry for my english
First of all, when I'm in the wrong thread, sorry!
So here I go. I guess i bricked my 1+1. Doesn't turn on, only black screen and if i push a button, it vibrates. Looked up for solutions, and found one here somewhere. It's with the recoverytool or with ColorOS.
So I tried to follow the steps. Everything works fine, in Device Manger, the phone is now recognised as Qualcom HS_USB QDloader 9008 (COM3). Til here no problems at all. Then I installed the set-up file, compatibilitymode, run as admin.
I open the recoverytool, and i scan for the device. It should appear as COM. But nothing shows up. It's weird because Windows recognises the device.
What am I doing wrong? What can help?
Thanks
gl411 said:
First of all, when I'm in the wrong thread, sorry!
So here I go. I guess i bricked my 1+1. Doesn't turn on, only black screen and if i push a button, it vibrates. Looked up for solutions, and found one here somewhere. It's with the recoverytool or with ColorOS.
So I tried to follow the steps. Everything works fine, in Device Manger, the phone is now recognised as Qualcom HS_USB QDloader 9008 (COM3). Til here no problems at all. Then I installed the set-up file, compatibilitymode, run as admin.
I open the recoverytool, and i scan for the device. It should appear as COM. But nothing shows up. It's weird because Windows recognises the device.
What am I doing wrong? What can help?
Thanks
Click to expand...
Click to collapse
Have you installed the Qualcomm driver?Its very tricky,Windows wont allow to install it easily.
Yes I did, I was able to switch to non signed in Win8 via F7 in a menu. Thats why it changed from BULK to qualcomm qd9008 on a COM port. Or cant I be sure its done propermy when the name changed?
gl411 said:
Yes I did, I was able to switch to non signed in Win8 via F7 in a menu. Thats why it changed from BULK to qualcomm qd9008 on a COM port. Or cant I be sure its done propermy when the name changed?
Click to expand...
Click to collapse
It should be the driver problem,no other choice.
maskelisuvari said:
It should be the driver problem,no other choice.
Click to expand...
Click to collapse
The easiest way for unbricking oneplus (yes, I tried it): http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136
ColourOS firmware has all needed files for proper flashnig, including right tool for doing that.
Only thing that didnt work on my Win 8.1 x64 was drivers mentioned in post above.
I had to use this QHSUSB_DLOAD drivers from member DallasCZ (that I used for unbricking ZTE v9180). Only with that drivers my Windows recognized bricked phone and Flash tool could find and flash it.
Flash tool in only on chinese, that is a bit problem, but instructions given in post I linked are more/less usefull.
This is a link to DallasCZ shared folder with qhsusb drivers:
https://drive.google.com/folderview...&usp=sharing&tid=0B1T7tp6tJ_3kQkZSWjNsazJZbGc
If you are sure the driver is okay,plug in the usb cable and out and in,until you see the green line on the tool.Also you can follow the guide as in below link:
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
The same thing but this time you can flash CM11s instead of ColorOs.Also there is a video.Pls check it.
Ok so I did the process over and over again, the sixth computer did it right! I was back on ColorOS and now back to CM11S.
This thread can be closed, thanks for the help!
No problem,glad to hear you solved the problem
Hi i have a Homtom 7 with version 2 mother board i contacted Homtom as i was having problems with it dumping contacts etc. they checked the motherboard etc and said i need to update the Firmware to 2.1.2 which they supplied me with and the program SP Flashtool to do it with and a video to try to explain it to me unfortunately it isn't happening all i get when i plug it in to flash is a few fast bleeps and then a single one later but nothing happens anyone any idea what is or isn't happening please?? i have the feeling the PC isn't recognizing it but that's just a wild guess ..
I tried again and got a warning saying "MT65xx Preloader was not successfully installed " no driver found
I followed a thread on here for installing the missing driver but still doesn't work.