I am using flashtool version 0.9.18.6,
Installed z3 drivers from directory flashtool/drivers.
When phone is turned on check driver shows serial no & drivers installed true
After booting in flashmode there are these errors
Use debugging is off(its on)
Check device not in mtp mode
Windows notification shows us device not recognized
I have pc companion installed,& previously used the same laptop for flashing
There is problem with restart need to use yellow reset button every time,is it interfering with flashtool,will flashing fix it????
Related
Hi! I have a problem with the drivers in the flashtool. I installed all the drivers from the drivers folder, but when you connect your phone to install the firmware flashtool indicates that there is no driver.
Ps.In the Device Manager Universal Serial Bus Controller with an exclamation point next to the stamp.
Ps. I can not turn the phone apart recorvery mode
Ps. PC Companion tells the modified software or can it miss?
manually download and install adb drivers and fastboot drivers via android sdk...
if this doesnt help then...i had all the drivers installed separately like adb drivers from screen lag fix pack by dragoboss(look in apps and themes section) and usb drivers with pc companion. fastboot drivers via android sdk....still i installed drivers provided by flashtool never got any problem hope this helps hit thanks
first of all many thanks to all the developers for doing excellent work.
i am on odyssey 4.3 rom.when i connect my phone to pc in normal mode it shows everything is fine and working but when i connect it in download mode, i'm getting android composite device driver failed error even after instlling drivers many times,i have read almost everywhere related to the issue here but of no help.and major issue is in recovery mode bymistake formatted boot and so now my device is stuck in samsung boot logo.no recognision in odin so cant flash it either way.what should i do ?
Download driver from here
http://adbdriver.com/downloads/
(Samsung offical android driver(contains MTP and ADB Driver))
Connect and uninstall current driver with yellow triangle. Disconnect and install the downloaded driver. Now connect and see.
Now follow the post
http://forum.xda-developers.com/showpost.php?p=54459555&postcount=343
if you do not want to start it from zero ie from BG ddlf2.
I rooted Xperia C and installed CWM with Mobile Uncle Tools. Something went terribly wrong and since then the phone is dead. I have tried possibly all the ways on the internet to connect it to my PC (Windows 10) in download mode to use either Sony Companion or wmshua to flash the stock rom but the problem is it isn't detected. All I get under device manager is a Serial Device (COM4) under Ports even though the light is still red on the phone and another thing I have noticed is that it keeps disconnecting and connecting again and again. I have tried installing various drivers, but no luck!
Can you guys please help me out?
Anyone please?? Any suggestions??
Guys my m2 stuck in semc flash device..
When i connect with pc..
In device manager it shows semc flash....
No flashmode and fastboot mode when i press volume down and up keys.
Flashtool doesn't detected..
Sony pc companion doesn't detected
Please help me..
I don't knw what to do!!
Connect your phone, go to device manager and uninstall the driver and disconnect your phone,
Now if you're running Windows 8+ restart your PC with driver signature enforcement disabled through advance boot, now go to C:\Flashtool\drivers and open the driver installer and install Flashmode and fastboot drivers and now connect your phone and go to device manager and install the Sony Xperia M2 driver http://developer.sonymobile.com/downloads/drivers/xperia-m2-driver/
Once that's done open your sim/microsd tray and use a pin and click on the red button inside the hole,
Now connect your phone to your PC and tell me what it says in device manager and later open PC companion and see what it detects
Help
What you said i did..
But my phone is detected as semc flash device..
Device doesn't goes to flashmode or fastboot mode...
If i connect my device in another pc which doesn't have any drivers for adb or Xperia m2.
It shows "qhusb bulk" in device manager..
I don't know what it means?
Only red light blinking
...
Need help. I was using Miracle Box to flash stock ROM, I don't know how but the phone (Micromax E453) is bricked now. I tried to start phone in Meta Mode (swiched off phone connected to PC by holding volume up button), it worked once, then following some tutorials I uninstalled (and checked, Delete the driver software for this device) MTK USB COM driver under port. Since then phone is not turning on and PC is not recognizing the device. Tired changing the USB cable and even tried it on another laptop, but no go. Kindly share what else I can try. PC has Windows 10 64 bit and MTK preloader vcom driver always has yellow exclamation mark (always installs with error code 10). I have disabled driver signature verificiation.
vnandwana said:
Need help. I was using Miracle Box to flash stock ROM, I don't know how but the phone (Micromax E453) is bricked now. I tried to start phone in Meta Mode (swiched off phone connected to PC by holding volume up button), it worked once, then following some tutorials I uninstalled (and checked, Delete the driver software for this device) MTK USB COM driver under port. Since then phone is not turning on and PC is not recognizing the device. Tired changing the USB cable and even tried it on another laptop, but no go. Kindly share what else I can try. PC has Windows 10 64 bit and MTK preloader vcom driver always has yellow exclamation mark (always installs with error code 10). I have disabled driver signature verificiation.
Click to expand...
Click to collapse
Did you have USB debugging enabled in the device's system settings before it got bricked? If not, you might not get it to connect via USB and be recognized.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Did you have USB debugging enabled in the device's system settings before it got bricked? If not, you might not get it to connect via USB and be recognized.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thank you for your response. Yes, USB debugging was enabled before it got bricked. I was able to successfully see my device when I ran adb -devices command. I was also able to run fastboot commands. Now its completely dead.