Related
Hi all,
I'm having some strange difficulties with - what i think are - the drivers for the Magic (32B). I cannot for the life of me connect the darned device to my PC in any way (well, apart from the storage option)! My ADP1 works 100% with adb/fastboot and whatnot and i'd really like it if the Magic would as well.... Both phones run the same version CM and i use the same cables/computer every time, both phones are set up the same (USB debugging and such) and both have an engineering bootloader but the Magic will not be recognized by my computer!
I've tried all and every driver i could find incl. the drivers that came with adb and the latest drivers from HTC Sync but all fail bad (the 'Android Bootloader interface' and 'MyHTC' drivers both give me a 'This device cannot start. (Code 10)' error...).
Now, i got it all working.... once... about a month ago to root the device and all and i cant remember changing anything since then but for some reason it simply doesn't work anymore. Has anyone here had similar experiences or any insights on how to fix this?
Help would be very much appreciated!!
So nobody knows? Hrm, im still having these difficulties...
maarten82 said:
Hi all,
I'm having some strange difficulties with - what i think are - the drivers for the Magic (32B). I cannot for the life of me connect the darned device to my PC in any way (well, apart from the storage option)! My ADP1 works 100% with adb/fastboot and whatnot and i'd really like it if the Magic would as well.... Both phones run the same version CM and i use the same cables/computer every time, both phones are set up the same (USB debugging and such) and both have an engineering bootloader but the Magic will not be recognized by my computer!
I've tried all and every driver i could find incl. the drivers that came with adb and the latest drivers from HTC Sync but all fail bad (the 'Android Bootloader interface' and 'MyHTC' drivers both give me a 'This device cannot start. (Code 10)' error...).
Now, i got it all working.... once... about a month ago to root the device and all and i cant remember changing anything since then but for some reason it simply doesn't work anymore. Has anyone here had similar experiences or any insights on how to fix this?
Help would be very much appreciated!!
Click to expand...
Click to collapse
Is USB debug enabled?
alex___ said:
Is USB debug enabled?
Click to expand...
Click to collapse
Yes, like i said in my first post everything is setup the same (USB debugging and such).
Also, if im not mistaken it wouldn't matter if i enabled this or not when trying to get the phone hooked up in fastboot mode and that doesn't work either.
So i guess its quite a unique problem im having...... sucks
Well, after some heavy duty searching/experimenting i found that it was a driver problem (windows XP's driver handling REALLY sucks)!
If anyone else is having problems, here's how i fixed it:
Disconnect phone from PC
Download USBDeview and run it
From within this program remove ALL non-Mass Storage drivers for Android and/or HTC (unlike XP this DOES actually remove em)
Reconnect phone with debugging enabled and install drivers from SDK (in my case r3 drivers)
This fixed it for me!
maarten82 said:
Well, after some heavy duty searching/experimenting i found that it was a driver problem (windows XP's driver handling REALLY sucks)!
If anyone else is having problems, here's how i fixed it:
Disconnect phone from PC
Download USBDeview and run it
From within this program remove ALL non-Mass Storage drivers for Android and/or HTC (unlike XP this DOES actually remove em)
Reconnect phone with debugging enabled and install drivers from SDK (in my case r3 drivers)
This fixed it for me!
Click to expand...
Click to collapse
I am having the same problem, do you mind sending me the link to download the drivers
deb82swearingen said:
I am having the same problem, do you mind sending me the link to download the drivers
Click to expand...
Click to collapse
The 'new' SDK works different from the old one, you actually need to install a bunch of stuff....
Get the package here, and read up on how to get the drivers with this package here!
Hi, I have a Micromax A52 device that I am trying to use for application development. Unfortunately, I can't seem to find the correct drivers for the phone. I scoured the Micromax website, but the drivers I found there did not seem to work at all. I searched these forums, and there are a few topics about the phone, but they all seem to be unsuccessful rooting attempts. All I need is drivers that will let me interface the phone with eclipse for testing. I didn't see a section for this phone (probably because the handset is not very popular) so I didn't know where a better place to post this was. Sorry if it's in the wrong section or something. Anyway, does anyone have working drivers for this device? I tried installing the drivers for the A50 (the previous model that has working drivers) but it did not work. Please help
Hello so I read trough your complains and this is the driver which should work in any case: http://www.priceandspecification.in/micromax-a52-pc-suite-modem-driver-download.html
A few questions:
What operating system your using: XP, 7 or MAC?
Have you installed ADB drivers?
I have the ADB drivers installed, and I am running Windows 7. These are the same drivers I found on the Micromax website which did not work for me. Maybe I am just installing it wrong or something, but I honestly can not make head or tail of it because there are so many folders with so many installers. I tried running a few of the intaller exe/bats but none of them worked for me. Is there some process I don't know about? Because as far as I can tell, this installer does not work. Thanks for any help!
pachufir said:
I have the ADB drivers installed, and I am running Windows 7. These are the same drivers I found on the Micromax website which did not work for me. Maybe I am just installing it wrong or something, but I honestly can not make head or tail of it because there are so many folders with so many installers. I tried running a few of the intaller exe/bats but none of them worked for me. Is there some process I don't know about? Because as far as I can tell, this installer does not work. Thanks for any help!
Click to expand...
Click to collapse
Hi,
If you are looking for Micormax A52 (unknown device/no suitable in device manager) then you can also install A56 driver.
Code:
http://www.micromaxsuperfone.com/products/PDF/Drivers_A56.zip 13MB
Right click on Micromax A52 and update driver software and choose the android_winusb.inf which will show you three different driver company's and drivers.
Choose Google Inc and on right side choose Android ADB interface.
Then your adb devices would display your device.
not able to install driver
Not working. Driver not installed Error. Any method to get the driver??
A52 ADA- Drivers
helloansuman said:
Not working. Driver not installed Error. Any method to get the driver??
Click to expand...
Click to collapse
Hi,
I have found some software that poses the same USB drivers that this mobile has
first install the server software and navigate to the programs folder and extract the driver for your OS.
Password : micromax
Refer to below link
The complete driver list posted by me.
http://forum.xda-developers.com/showthread.php?p=30906925#post30906925
install driver using software
use moborobo software to install your driver in pc
first to the download moborobo software and install it
after open moborobo and connect your mobile in pc
moborobo will find your mobile driver and install autometicly
click thnks button
So here's how I did it:
Basically, with an Cortex A8 processor, the Maxell C8 tablet seems to be a slightly upgraded Allwinner A10, which is a bit cheaper than the Maxell tablet but then again Maxell really did package theirs nicely in terms of casing. But it's no secret - when you plug in the Maxell C8 with Windows 7 it shows clearly that it's a MID tablet. So essentially, my theory is that this method should work on all similar tablets such as Allwinner A13,A10 etc (although many of those come with preinstalled google play, as China, like me, doesn't give a **** about copyright). For reference, my tablet is running Android 4.0.4
Step 1. Root your tablet.
This took me a few times to figure out but this program called "Android Root Unlock" finally did it for me. You can get it from Source Forge: http://sourceforge.net/projects/androidroot/
Enable USB debugging (settings > developer options > Usb debugging). Then just connect your tablet to your PC via USB, wait until Windows recognizes the device. It should read "MID" in the device manager screen. The unpack the zip file you downloaded above on your Windows machine and run "ICS_Root_Unlocker.bat" it while the tablet is still plugged into USB. A black terminal window will open, just follow the instructions from there. Your tablet will restart - that means it probably worked, don't close the program yet but follow what it says to the end until the terminal window closes. Now you can unplug your device.
Step 2. Install modded Google Play
Now you can go ahead and follow the instructions on xda-developers.com:
http://forum.xda-developers.com/showthread.php?t=1650116
That's it! Google play now works like a charm and I can download stuff directly from Google Play without problems
Here's my full blog post: http://truthtech0.blogspot.com/2013/03/android-maxell-maxtab-c8-tablet-market.html
Thanks for your efforts, I'll give it a try. I was going to try Root_with_Restore_by_Bin4ry, but as you've confirmed it works, I'll use Android Root Unlock.
I think it's running Jelly Bean, it's my dads tablet. I'll see him tomorrow.
profixit said:
Thanks for your efforts, I'll give it a try. I was going to try Root_with_Restore_by_Bin4ry, but as you've confirmed it works, I'll use Android Root Unlock.
I think it's running Jelly Bean, it's my dads tablet. I'll see him tomorrow.
Click to expand...
Click to collapse
Thanks for the tips.
Anyone managed to install either a recovery image or a custom rom on the maxtab?
I've rooted mine but cannot get fastboot to work and unable to load a recovery image. Adb is working OK. Tried clockworkmod but device is unsupported.
gadget19, what happened to yours, why do you need to recover or use custom rom?
profixit said:
gadget19, what happened to yours, why do you need to recover or use custom rom?
Click to expand...
Click to collapse
I tried the google play fix but its not working for me. I wanted to use a custom rom so that I get google play to work correctly and also to try out 4,2 features.
Hi, thank you for your guide.
Unfortunately i'm unable to complete it because when i connect the maxtab c8 to a windows 7 system it doesn't find the MID driver so the root bat doesn't find the device.
Do you have any hint in how to complete the procedure?
Thank you.
Town Annteem
lordtruten said:
Hi, thank you for your guide.
Unfortunately i'm unable to complete it because when i connect the maxtab c8 to a windows 7 system it doesn't find the MID driver so the root bat doesn't find the device.
Do you have any hint in how to complete the procedure?
Thank you.
Click to expand...
Click to collapse
I used the samsung drivers and google naked universal drivers. Adb commands work with them but could never get fastboot cmds to work.
gadgethome said:
I used the samsung drivers and google naked universal drivers. Adb commands work with them but could never get fastboot cmds to work.
Click to expand...
Click to collapse
Thanks for the hint; I was able to execute the bat file but i still have some problems.
The procedure looks like complete but if I open Root Explorer and try to do some changes in \system\app it just tell me that it's in read only mode.
Tried root check pro and it's all red...
superuser installed
sbin/su: permission denied
system/bin/su: no file
system/xbin/su: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
system/xbin/sudo : no exsist
su binary not found or not operating correctly
Tried to run the su file in system/xbin/su as a script on the tablet and via adb without any changes. Checked a bit online but i'm a bit stucked since my other android device (lg p500) was much easier to root.
If you have any idea i't will be very helpful. Thank you.
Ok solved.
To easy root the maxtab c8 (android 4.1) i used the RK29 tab tolkit v1.3: easy and fast.
Now i have problem installing the play store...
I followed the guide but since i don't have any Vending.apk or phonesky.apk in system/app i just copied it without a backup, rebooted but nothing happened.
Need more testing.
Ok play store installed and working.
I didn't use the apk linked in the first post, i had to use this one instead: http://forum.xda-developers.com/showthread.php?t=1934441
The method is the same (copy in system/app, set the permission as rw-r--r-- and then reboot) just use the apk i linked.
Hope this help someone.:victory:
Hi all, what's the best drivers to use for the Maxtab C8
Windows 8. Device manager showing unrecognized MID device
Thanks
profixit
I used PDAnet software for driver instal on XP. Have no idea if it will work for 7 or 8.
Google it, i cant post URL
Finally got everything working.
Used my old Intel x86 XP Pro to root it
Then Google play installer.
Maxtab welcome to the real world.
i'll have a Nandroid backup of the stock rom by tomorrow. if interested PM me
maxell maxtab 8
Hi,
I have a maxtab 8, with recovery loop..
Where can I ask -this machine-, which would not take off the observer?
this forum is the correct place?
Hi there
I have seen some posts where users are having difficulty connecting Xperia L to their PC or ADB. Therefore, I am writing this guide to help you all.
The guide was prepared using Windows 7 Ultimate but should work with Windows XP and Windows 8.
Firstly, Sony uses a different driver for their Xperia devices and therefore, sometimes you are unable to install drivers for your devices especially for ADB commands.
IF YOU ARE LUCKY
There are few ways to get around to install drivers for your device. The most convenient and easy is you plug in your device and wait for automatic detection of your device. Make sure you have USB connected as MTP in MY XPERIA in SETTINGS of your phone. The device drivers would be automatically installed by Windows update.
METHOD
If suppose you can not install your drivers, connect your xperia and then on your PC, go to My computer > Properties>Device Manager.
You should see an undetected hardware with a yellow exclamation mark over it. Open it and click on update my drivers. Then choose GOOGLE DRIVERS by choosing hard-drive. This should install the drivers for you. If this doesnot work. Try the attachment with the post where the drivers are modified to work with Sony Xperia Devices.
Follow the same steps but this time choose the attachment folder to search for drivers. It might say, the drivers are not verified. Just Ignore it and carry on installing them. You will need to unzip these files.
IF suppose you do not see any exclamation mark while you connect your xperia. Just go to control panel and add new hardware. Select, I will choose my device and then install from hard-disk. Select the folder where you have unzipped the files and you are good to go. The name of new hardware is not important as windows will read the drivers files and install drivers for Xperia.
This will install all drivers for your device. If there are two or more drivers while installing them. Redo the steps and install all of them individually.
Suppose your ADB still doesnot work, then
FOR ADB DRIVERS :
Download the ADB Universal Drivers and connect your device. Then hit install. The ADB drivers will be automatically detected and installed.
Further, if these tricks fail, you can delete the unknown driver from your control panel and then try finding it again by using refresh button(scan for new hardware changes) in device manager.
Another trick is to click on unknown drivers and delete them. Connect your phone and restart your phone. Then scan for new hardware in device manager. The drivers should be installed for your device.
If still there are some problems, I will try to help you out.
DOWNLOAD LINKS
DOWNLOAD GOOGLE DRIVERS FOR MTP/ PC ETC
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
DOWNLOAD UNIVERSAL ADB DRIVERS HERE :
http://adbdriver.com/upload/AdbDriverInstaller.exe
UPLOADED FILE : Sony Xperia Drivers for ADB.
UPDATE :
Use flashtool drivers to install adb/fastboot/flashboot drivers. This is the most simplest and easiest method I have come across lately.
Simply download flashtool
http://www.flashtool.net/index.php
Go to folder where you have downloaded it. Usually C:/flashtool/drivers.
Select the drivers for your particular device. I use universal for all three types of drivers. It is helpful to boot into fastboot/Flashtool before installing the drivers but not necessarily.
Good Luck
Reserved
This is great Hnk1 thanks a bunch
joel113- said:
This is great Hnk1 thanks a bunch
Click to expand...
Click to collapse
I am glad I could be of help
Good work
Hnk1 said:
Hi there
I have seen some posts where users are having difficulty connecting Xperia L to their PC or ADB. Therefore, I am writing this guide to help you all.
The guide was prepared using Windows 7 Ultimate but should work with Windows XP and Windows 8.
Firstly, Sony uses a different driver for their Xperia devices and therefore, sometimes you are unable to install drivers for your devices especially for ADB commands.
IF YOU ARE LUCKY
There are few ways to get around to install drivers for your device. The most convenient and easy is you plug in your device and wait for automatic detection of your device. Make sure you have USB connected as MTP in MY XPERIA in SETTINGS of your phone. The device drivers would be automatically installed by Windows update.
METHOD
If suppose you can not install your drivers, connect your xperia and then on your PC, go to My computer > Properties>Device Manager.
You should see an undetected hardware with a yellow exclamation mark over it. Open it and click on update my drivers. Then choose GOOGLE DRIVERS by choosing hard-drive. This should install the drivers for you. If this doesnot work. Try the attachment with the post where the drivers are modified to work with Sony Xperia Devices.
Follow the same steps but this time choose the attachment folder to search for drivers. It might say, the drivers are not verified. Just Ignore it and carry on installing them. You will need to unzip these files.
IF suppose you do not see any exclamation mark while you connect your xperia. Just go to control panel and add new hardware. Select, I will choose my device and then install from hard-disk. Select the folder where you have unzipped the files and you are good to go. The name of new hardware is not important as windows will read the drivers files and install drivers for Xperia.
This will install all drivers for your device. If there are two or more drivers while installing them. Redo the steps and install all of them individually.
Suppose your ADB still doesnot work, then
FOR ADB DRIVERS :
Download the ADB Universal Drivers and connect your device. Then hit install. The ADB drivers will be automatically detected and installed.
Further, if these tricks fail, you can delete the unknown driver from your control panel and then try finding it again by using refresh button(scan for new hardware changes) in device manager.
Another trick is to click on unknown drivers and delete them. Connect your phone and restart your phone. Then scan for new hardware in device manager. The drivers should be installed for your device.
If still there are some problems, I will try to help you out.
DOWNLOAD LINKS
DOWNLOAD GOOGLE DRIVERS FOR MTP/ PC ETC
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
DOWNLOAD UNIVERSAL ADB DRIVERS HERE :
http://adbdriver.com/upload/AdbDriverInstaller.exe
UPLOADED FILE : Sony Xperia Drivers for ADB.
Click to expand...
Click to collapse
:good: Good work
Installing these drivers didn't work, But after a factory reset and installing the Sony companion, the drivers installed and now gets detected in the ADB.
Thanks
ReSkid said:
Installing these drivers didn't work, But after a factory reset and installing the Sony companion, the drivers installed and now gets detected in the ADB.
Thanks
Click to expand...
Click to collapse
Did you try the attached drivers ?
I am just wondering you might hadnot turned USB debugging or disabled MTP mode or something you might have done to your kernel/ROM that might have changed the environment of your phone which factory reset reverted back. These drivers are NOT the drivers for connecting your device to your PC. These are used when you are unlocking your bootloader or working with ADB/fastboot commands.
Thanks for your contribution about how it worked for you and it might help others who might have a problem!
you can use ADB Wireless
https://play.google.com/store/apps/details?id=com.sherdle.adbwireless&hl=en
Hnk1 said:
Did you try the attached drivers ?
I am just wondering you might hadnot turned USB debugging or disabled MTP mode or something you might have done to your kernel/ROM that might have changed the environment of your phone which factory reset reverted back. These drivers are NOT the drivers for connecting your device to your PC. These are used when you are unlocking your bootloader or working with ADB/fastboot commands.
Thanks for your contribution about how it worked for you and it might help others who might have a problem!
Click to expand...
Click to collapse
I had tried every possible driver haha! Also had everything like USB Debugging etc turned ON, I guess it might have been some app I had installed. Anyways now I have rooted it successfully.
Thanks a lot for your help.
I am still having this problem for days now. still no connection to pc/flashtool whenever i try to reboot into flashmode/flashboot. i've been google'ing around. and i've tried this method but it's seems doesnt work. i've already got tons of these unknown devices, and the driver doesnt work(or maybe im too noobish to install them).please help
ReSkid said:
I had tried every possible driver haha! Also had everything like USB Debugging etc turned ON, I guess it might have been some app I had installed. Anyways now I have rooted it successfully.
Thanks a lot for your help.
Click to expand...
Click to collapse
I am here for anything that I can help you with. It's great that your problem is fixed now !
AATrooperz said:
I am still having this problem for days now. still no connection to pc/flashtool whenever i try to reboot into flashmode/flashboot. i've been google'ing around. and i've tried this method but it's seems doesnt work. i've already got tons of these unknown devices, and the driver doesnt work(or maybe im too noobish to install them).please help
Click to expand...
Click to collapse
For a second when I looked at your images, I was just baffled. THOSE MANY UNKNOWN DEVICES! That can't be right you know.
There must be only ONE unknown device that ought to be installed as mentioned above in my post.
Do you see these devices when you connect your phone to your PC or those unknown devices are already there?
Have you tried windows update to fix it?
Tell me more about why you see so many devices.
If suppose, they are already there, just see which device comes up when you connect your phone and try installing drivers for that particular device.
Also, i suggest just go for add a new device and then select hard disk and then install drivers which are attached. I hope that fixes your problem.
REMEMBER your device must be connected when you are trying to install the drivers
right.i'm gonna give it a try,wish me luck. thanks!
I still need your help!!
I could not install or might be dont know how to install the attached xperia drivers which are in .dll files. Can u explain in detail how can I install it. I've lost root access after upgrade to 4.2.2 . I do really need your help to get back root access and install a valid driver for my device. From C2104
Hnk1 said:
I am glad I could be of help
Click to expand...
Click to collapse
Dude someone needs your help ^
I just quoted your post so you'd get notified about it.
@up ur post is a simple spam, if u dont know how to help just dont write anything. n one needs notifications for replying
FPThatea said:
I could not install or might be dont know how to install the attached xperia drivers which are in .dll files. Can u explain in detail how can I install it. I've lost root access after upgrade to 4.2.2 . I do really need your help to get back root access and install a valid driver for my device. From C2104
Click to expand...
Click to collapse
just go to device manager, connect phone and find ur not recognized device; then right click on it and press update/install drivers. From the window that will appear choose socond option (it should be something like manualy find drivers or something like that), then navigate to that downloaded folder. This way it should install them
But XL doesnt need any external drivers. If u install fasboot an flashmode drivers from flashtool folder they should work; they are working for me and for anyone i know. U may also install SEUS and then connect phone. This way u dont need that drivers, but ofc what i have mentioned earlier should work.
FPThatea said:
I could not install or might be dont know how to install the attached xperia drivers which are in .dll files. Can u explain in detail how can I install it. I've lost root access after upgrade to 4.2.2 . I do really need your help to get back root access and install a valid driver for my device. From C2104
Click to expand...
Click to collapse
Hi
well first thing you need to understand is there are three drivers you need to install to make everything work including fastboot , flashboot, and Xperia L storage and SD card.
To install each type of drivers, you must have the phone in that particular state. To install normal drivers (for mass storage and PC companion), if suppose not detected automatically, you need to turn on your phone and then unlock it. Then see if drivers are found or not!
If the windows give you the error like undetectable device attached, go to my computers and then properties and the device manager and look for any device with an exclamation mark (yellow).
click on it and then select update drivers and use drivers that have been attached in the first post. (Remember to extract the attachment in a folder)
Then click on select drivers from hard drive (click manual installation of drivers )
and locate the folder where you have extracted drivers. This will install drivers!
if you want drivers for flashmode/fastboot, turn off phone and boot into flashmode and then install drivers as I mentioned above.
I'm quite certain they wouldn't trouble you at all. If you still need help, do not hesitate to ask !
Good luck
P.S: You will need to enable developers option and select USB debugging to root your device. I hope you are doing that right !
Joel16 said:
Dude someone needs your help ^
I just quoted your post so you'd get notified about it.
Click to expand...
Click to collapse
Thank you so much ! I only check my notifications so I really appreciate it
uremytoy said:
@up ur post is a simple spam, if u dont know how to help just dont write anything. n one needs notifications for replying
just go to device manager, connect phone and find ur not recognized device; then right click on it and press update/install drivers. From the window that will appear choose socond option (it should be something like manualy find drivers or something like that), then navigate to that downloaded folder. This way it should install them
But XL doesnt need any external drivers. If u install fasboot an flashmode drivers from flashtool folder they should work; they are working for me and for anyone i know. U may also install SEUS and then connect phone. This way u dont need that drivers, but ofc what i have mentioned earlier should work.
Click to expand...
Click to collapse
Actually why don't you have a look at what the OP said,
"Thankyou so much, I only check my notifications so I really appreciate it"
I know what I'm doing here, if you don't have anything nice to say about it then DON'T say anything
Thanks..but still need you
Hi..Thank you so much for getting me back very soon.. I've successfully installed the driver with your your help. But, When I tried to root by using metachopper 1.3 my device did not reboot and start. Now, it just dead and really sad for this. I don't know what shall I do to get my phone back. Yes, I have 4.2.2 update in .ftf file with a flashtool. But, it does not work for me now.. Do you any experience to help me to solve my unwanted problem..Please..
FPThatea said:
Hi..Thank you so much for getting me back very soon.. I've successfully installed the driver with your your help. But, When I tried to root by using metachopper 1.3 my device did not reboot and start. Now, it just dead and really sad for this. I don't know what shall I do to get my phone back. Yes, I have 4.2.2 update in .ftf file with a flashtool. But, it does not work for me now.. Do you any experience to help me to solve my unwanted problem..Please..
Click to expand...
Click to collapse
you must boot your phone in fast boot mode. turn off your phone and hold down volume down when you connect it to the PC!
Use flashtool to flash ftf file. you'll need to place ftf file in C:/flashtool/firmwares
then select the right file for xperia L and just flash ftf.
in flash tool , select flash n then fastboot and then I'll ask you to put your phone in fast boot (use method mentioned above)
good luck !
I have tried all your methods
but I keep getting this error message "An error occurred during the installation of the device"
I am using windows xp sp3
please help
Many have faced this problem while using a new phone (Lollipop, Marshmallow and later) with MTKDroid Tools.
Here is the issue - MTKDROID ships with an older version of ADB. (The program hasn't been updated for a few years but it still works.)
This ADB cannot recognize the newer phones. So the obvious solution is to replace the older adb.exe from the 'adb' folder of MTKDroid Tools. But MTKDroid recognizes this and refuses to start, showing us the 'It is impossible to start ADB' error.
I have made a workaround which starts MTKDroid with the older adb and immediately when it finds everything to be OK, replaces it with a newer one. It worked for me. So I hope it will for you too.
Download the zip in attachment.
Instructions.
Goto your MTKDroid/adb folder and delete everything in it.
Open the zip file you have downloaded with winrar or 7zip or anything.
Inside the zip file, there will be 8 files. Copy all these files to the adb folder.
Now you can double click StartMTKDROIDTOOLS.bat and press enter to start MTKDroid Tools. A few black console windows will come and ask you to wait 10 seconds (this is to make sure MTKDroid is loaded completely), wait and don't worry it will close itself when the work is done.
There you go problem fixed and MTKDroid is ready for your command!
NOTE: This fix will help you to start MTKDroidTools and use it to create a scatter file for flashing and backup purposes with SPFlash tool. From what I learned, you can't use this to root your phone unless you enable the temporary root shell from Engineering Mode.
To do that, open your phone dialer, dial *#*#3646633#*#* .
Swipe left to reach Log and Debugging section, there select user2root, in it enable root shell and now connect your phone using the above method.
This method is not guaranteed to work on every phones out there and I still recommend flashing SuperSU the old fashioned way.
Please reply back with any of your troubles or suggestions.
Hi, Thank you for posting this I was disappointed when the tool did not work. But thanks to you it's working now and I can do my surgery xD
pig_slay said:
Hi, Thank you for posting this I was disappointed when the tool did not work. But thanks to you it's working now and I can do my surgery xD
Click to expand...
Click to collapse
I hope it lives.. :fingers-crossed:
Thanks so much, Adithya! This was a life-saver. I had spent over a day trying to get MTKDroidTools to work and only now found your post!
I have a new Nook tablet (BNTV450). This runs Marshmallow and the adb v31 included with MTKDroidTools 2.5.0 could not connect with it, as you reported. (BTW, I'm using 2.5.0 because 2.5.1-2.5.3 have a malware built in. androidmtk.com says not to worry about the malware (!) but my anti-virus reports it as w32.malware.heur which is quite serious. Anyway, these later versions of MTKDroidTools also use adb v31.)
I did need to make one small change due to a race condition: I added a 2 second delay between the call to run startup.bat and the call to run MTKDroidTools. So this section of StartMTKDROIDTOOLS.bat now reads:
start Startup.bat
timeout 2
cd..
start MTKdroidTools.exe
Without this on my Windows 10 PC, MTKDroidTools starts too quickly and picks up the newer version of adb even though startup.bat had just replaced it. The 2 second delay allows MTKDroidTools to find the old version reliably.
So thanks again for this! Really helpful!
Best,
Dennis
DMcRitchie said:
Thanks so much, Adithya! This was a life-saver. I had spent over a day trying to get MTKDroidTools to work and only now found your post!
I have a new Nook tablet (BNTV450). This runs Marshmallow and the adb v31 included with MTKDroidTools 2.5.0 could not connect with it, as you reported. (BTW, I'm using 2.5.0 because 2.5.1-2.5.3 have a malware built in. androidmtk.com says not to worry about the malware (!) but my anti-virus reports it as w32.malware.heur which is quite serious. Anyway, these later versions of MTKDroidTools also use adb v31.)
I did need to make one small change due to a race condition: I added a 2 second delay between the call to run startup.bat and the call to run MTKDroidTools. So this section of StartMTKDROIDTOOLS.bat now reads:
start Startup.bat
timeout 2
cd..
start MTKdroidTools.exe
Without this on my Windows 10 PC, MTKDroidTools starts too quickly and picks up the newer version of adb even though startup.bat had just replaced it. The 2 second delay allows MTKDroidTools to find the old version reliably.
So thanks again for this! Really helpful!
Best,
Dennis
Click to expand...
Click to collapse
You're welcome.
I have included the changes you suggested.
Also I found this on stackoverflow which might help on w32.mal.heur detections.
W32 is the platform: Windows 32
Malware is the Category
Heur (Heuristic) might refer to what usually is the family or might be some specific naming of your AV
The heuristic term usually refers to detections based on generic signatures which look suspicious.
That detection looks very generic and might be a false positive.
Click to expand...
Click to collapse
Since the nature of the tool is indeed a hack itself your AV might be showing a false positive.
Still it's all up to you to decide.
All the very best.
Post updated.
Added a 2 sec delay to call MTKDroidTools. (Thanks @DMcRitchie)
Added a guide on rooting.
This doesn't work for me. I used to Only get the phone not recognized error now, after copying over the 8 new files to my now empty ADB folder, I get the error that says Impossible to start ADB.
I'm using a Figo Atrium upgraded from Lollipop to Mashmallow using the SP Flash Tool. All I'm trying to do now it root the device, I don't need a custom rom. Using MTK Droid Tools version 2.5.3
Edit: Fixed it. I had to turn off then back on UBS Debugging, simply revoking the USB did not work. It's seeing my device now but says it can't root my device and sends me to an html page with lots more instructions. The tool tells me my device can be rooted this way. https://forum.xda-developers.com/showpost.php?p=38337401&postcount=5 Grrr.. time to spend days jumping through more hoops.
Divergent Droid said:
This doesn't work for me. I used to Only get the phone not recognized error now, after copying over the 8 new files to my now empty ADB folder, I get the error that says Impossible to start ADB.
So this didn't fix it, just made it worse. Is there another way to fix? I'm using a Figo Atrium upgraded from Lollipop to Mashmallow using the SP Flash Tool. All I'm trying to do now it root the device, I don't need a custom rom. Using MTK Droid Tools version 2.5.3
Click to expand...
Click to collapse
This was supposed to fix the 'impossible to start error'. You shouldn't have used it if you were not facing that issue.
Don't worry you can just redownload MTK Droid Tools to fix that.
As for rooting, MTK Droid Tools CAN NOT ROOT phones newer than kitkat. Your best bet is to flash a custom recovery and flashing super su.
This guide is for those people who can't use SP Flash Tools because they need a scatter file which MTK Droid Tools can't make for newer androids.
All the best.
Thanks.
You gave me the most detailed answer so far. I got the info to use MTK Droid Tools from a website claiming it will work for Android 6.0 Marshmallow. That's why I tried it. If you are very knowledgeable about rooting in general, perhaps you'll answer my other thread asking someone to help me understand these things better. it seems according to you, i would be able to flash a new rom and SuperSU? See my other post and answer there. https://forum.xda-developers.com/general/help/guru-to-discuss-rooting-t3683594 - I did try the folks at the SuperSU sub forum and they cant help me.
When i connect Infinix Note 4 Pro X571 (bricked) to pc for Mtk to detect, it just boots to recovery mode (twrp)
tried using Maui Meta, it automatically installed vcom drivers then it said "it cannot find Kernal USB comport for AP and Modem handshake. Please check the usb driver version or find the driver owner to check"
thank you so much!! it works
I Get This Only :/ What's wrong? Noob Mistake?
qounik said:
I Get This Only :/ What's wrong? Noob Mistake?
Click to expand...
Click to collapse
I have the same issue. I just want to backup some stuff.
EDIT: this worked for me https://forum.xda-developers.com/showpost.php?p=75722412&postcount=14
Hi
Great fix but I still have a problem, I only have the hardware and baseband detected nothing else, so I can not save.
An idea ?
Thanks