So,
I've bought an Samsung Galaxy S3 replica (read: fake, and i want only to root it no flash it):
Model number: S930
Android version: 4.0.3
Baseband version: DM_BASE_12A_W12.28_P1|sc8810_modem|07-13-2012 16:42:35
Kernel version: 2.6.35.7 [email protected] #3
Software version: T300_JYYS930_C3BOM_MLB_V6.6.5_20121105
Hardware version: 1.1.0
CPU: Spreadtrum
When I first plugged it my notebook (Win7 32bit) I've got in the device manager:
Other Devices
- Spreadtrum Phone
- Spreadtrum Phone
- Spreadtrum Phone
I'm trying to root it so I started my research, afts thousands of tests, I discoverd that
Other Devices
- Spreadtrum Phone >> Android Composite ADB Interface (driver instaled with Android SDK)
- Spreadtrum Phone >> SCI General U2S(AT) (COM3) (Google Search: Spreadtrum Drivers)
- Spreadtrum Phone >> SCI Vendor U2S(DIAG) (COM4) (Google Search: Spreadtrum Drivers)
So after all the yellow marks disappeard i've tried almost everything to root it:
- QQPhoneManeger for Android (which recognise the device like: Sprd S930 - allow me to access my "device root" but I can't change anything there, not even copy from it)
- UnlockRoot (which worked in my previous phone MTP65XX also an android replica)
- Odin
- PDA Net
- SparkyRoot
- Z4Root
- Poot-debug + Ministro II
- Instant-root
- Gingerbreak
- OneClickRoot
- SuperOneClick
And recently i've tried the DooMLoRD ROOT v18 - And I've only got:
adb is out of date. killing...
*daemon estarted succefully*
and nothing more, so i've went to search some more, and I've learned how to verify if adb recognise the device.
I added the C:\android-sdk\plataform-tools to my system path and tried the commands
adb devices
my answer was:
*daemon not runing. startin it now on port 5037*
*daemon started successfully*
List of devices attached:
....
Nothing, so i've tried
adb shell
my answer was:
error: device not found
So I re-checked all the drivers, unistalled and re-installed.
tried again same thing...
So now i'm stuck, all the solutions that i've fonund for the problem is now coverd
Is there any way to solve it? Or any way to root my device that isn't listed? Or any driver that's better for my device than the one in Android SDK?
Thanks in advance and sorry for the english.
UPDATE!!
Solved, yay!, view solutions below
Did you tried this method http://forum.xda-developers.com/showthread.php?t=1886460 ?
Press the THANKS button if i helped
HOPE IT WILL WORK !! GOOD LUCK !!!
Thanks, but already tryied this one.
karimkahale said:
Did you tried this method http://forum.xda-developers.com/showthread.php?t=1886460 ?
Press the THANKS button if i helped
HOPE IT WILL WORK !! GOOD LUCK !!!
Click to expand...
Click to collapse
Thanks, but this one also don't work, I forgot to list it. 'cause it's similar to the DooMLoRD .bat
All i got is the *daemon started successfully* answer
{
"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"
}
And than when I kill the adb process in the task maneger, it resume the running, but aways returning the answer
error: device not found
What I don't get is, if the windows system recognise my Android Composite ADB Interface, why the adb don't?
SOLVED!!!
I've made it. *so ****ing happy right now*
Solutions:
To - Device adb recognition.
Place Hardware ID VID_xxxx in {user home}/.android/adb_usb.ini.
Source
Subscribing the adb.exe files Download Here
Source
To - Rooting
I've used one of the previos methods i've tried
DooMLoRD ROOT v4
Thanks for the tipo karimkahale
And now i'm going to enjoy my 3 sleepless days victory.
Great!! Glad it worked!!
But just please press the THANKS button, it's much better
H_Bler said:
I've made it. *so ****ing happy right now*
Solutions:
To - Device adb recognition.
Place Hardware ID VID_xxxx in {user home}/.android/adb_usb.ini.
Font
Subscribing the adb.exe files Download Here
Font
To - Rooting
I've used one of the previos methods i've tried
DooMLoRD ROOT v4
Thanks for the tipo karimkahale
And now i'm going to enjoy my 3 sleepless days victory.
Click to expand...
Click to collapse
Hi everyone, I'm having the same problem with a similar phone, a S3 replica:
Model number: Z15A
Android version: 4.0
Baseband version: DM_BASE_12A_W12.28_P1|sc8810_modem|07-13-2012 16:42:35
Kernel version: 2.6.35.7 [email protected] #3
Software version: T300_JYYS930_C3BOM_MLB_V6.6.5_20121105
Hardware version: 1.1.0
CPU: Spreadtrum
It appears in the Device Manager (Win7 64bit) as:
Other Devices
- Spreadtrum Phone
- Spreadtrum Phone
- Spreadtrum Phone
I tried installing the USB driver that comes with the Android SDK ( sdk\extras\google\usb_driver ) using "Update driver..." but it only says that Windows could not find a driver there ( maybe because of the 64bit OS? ).
I think i will try and install a Win7 32 bit somewhere just in case, but nevertheless, could you elaborate a bit the solution you found please? (mostly the driver part, as I cannot find how to get the device recognized by Windows)
Thanks in advance.
sergimas said:
Hi everyone, I'm having the same problem with a similar phone, a S3 replica:
Model number: Z15A
Android version: 4.0
Baseband version: DM_BASE_12A_W12.28_P1|sc8810_modem|07-13-2012 16:42:35
Kernel version: 2.6.35.7 [email protected] #3
Software version: T300_JYYS930_C3BOM_MLB_V6.6.5_20121105
Hardware version: 1.1.0
CPU: Spreadtrum
It appears in the Device Manager (Win7 64bit) as:
Other Devices
- Spreadtrum Phone
- Spreadtrum Phone
- Spreadtrum Phone
I tried installing the USB driver that comes with the Android SDK ( sdk\extras\google\usb_driver ) using "Update driver..." but it only says that Windows could not find a driver there ( maybe because of the 64bit OS? ).
I think i will try and install a Win7 32 bit somewhere just in case, but nevertheless, could you elaborate a bit the solution you found please? (mostly the driver part, as I cannot find how to get the device recognized by Windows)
Thanks in advance.
Click to expand...
Click to collapse
Hello,
I, don't know if the trouble is because you have win 7 64bit, but I will say how i've made it.
Windows has already intalled the device as Spreadtrum with generic drives, so any other driver that you try to install tha isn't compatible with the ones windows associated with your device will be avaliated by the system as "no compatible with your device", so what you got to do is, uninstall this generics drivers so the "spreadtrum"s will be displayed with the yellow mark, and under the "other devices" section in the device manager, then, you install manually the spreadtrum drivers that you can find in searches in two of the "spreadtrum" devices (in the drivers i've found in google searches I've got 3 different drivers General, Vendor and Modem, but i've only used General and Vendor as the other "spreadtrum" device was an ADB interface and not a modem) and the other you also install manually but with the driver in the folder "usb_driver" in "android-sdk/extras/google".
Also, when you use "update driver" follow: Search in my computer> pick in a list> have a disc , then you search in the folders of android-sdk and of the spreadtrum drivers that you downloaded.
Hope it helps.
Just one more thing, i've made it with the root access but now my Play Store don't open... it opens loads a little and then close with (the com.android.vending stopped unexpectedly...
I've tried re-instal the native apk, factory reset, everything, bout nothing works :/
I had to re install all my aps via computer with the "adb install xxxx.apk. And every other aps work normally.
Happy holidays everyone.
If anyone have a clue of what to do, i'd like to try it
H_Bler said:
Hello,
I, don't know if the trouble is because you have win 7 64bit, but I will say how i've made it.
Windows has already intalled the device as Spreadtrum with generic drives, so any other driver that you try to install tha isn't compatible with the ones windows associated with your device will be avaliated by the system as "no compatible with your device", so what you got to do is, uninstall this generics drivers so the "spreadtrum"s will be displayed with the yellow mark, and under the "other devices" section in the device manager, then, you install manually the spreadtrum drivers that you can find in searches in two of the "spreadtrum" devices (in the drivers i've found in google searches I've got 3 different drivers General, Vendor and Modem, but i've only used General and Vendor as the other "spreadtrum" device was an ADB interface and not a modem) and the other you also install manually but with the driver in the folder "usb_driver" in "android-sdk/extras/google".
Also, when you use "update driver" follow: Search in my computer> pick in a list> have a disc , then you search in the folders of android-sdk and of the spreadtrum drivers that you downloaded.
Hope it helps.
Just one more thing, i've made it with the root access but now my Play Store don't open... it opens loads a little and then close with (the com.android.vending stopped unexpectedly...
I've tried re-instal the native apk, factory reset, everything, bout nothing works :/
I had to re install all my aps via computer with the "adb install xxxx.apk. And every other aps work normally.
Happy holidays everyone.
If anyone have a clue of what to do, i'd like to try it
Click to expand...
Click to collapse
I got to get the drivers installed. I've got:
- Android Composite ADB Interface
- SCI General U2S(AT) (COM4)
- SCI Vendor U2S(DIAG) (COM3)
I tried some of the rooting methods you list (z4root, OneClickRoot, SuperOneClick,...) and finally DooMLoRD ROOT v18, but the problem is that my /system directory is Read-Only, so no way is anything working.
I don't kno how to proceed now (noob here ), but I'll keep you posted if I find any solution.
Happy holidays, and good luck!
s550
I have a similar replica, the s560. Should this metod work on my phone? i want to install cyanogenmod on it
this one focalprice.com/MH0369B/35_Android_40_6820_10GHz_Smartphone_with_WiFi_TV_Bluetooth.html
sergimas said:
I got to get the drivers installed. I've got:
- Android Composite ADB Interface
- SCI General U2S(AT) (COM4)
- SCI Vendor U2S(DIAG) (COM3)
Click to expand...
Click to collapse
Hi!
I'm trying to do this myself, but I can't seem to install the drivers properly. Did you use 64-bit windows 7? And which drivers did you use?
Cause I used "SPREADTRUM SCI-USB2Serial-version-1.5.6.1" which I found via Google search, and none of the drivers I found are not digitally signed. That means they won't install properly in win 64-bit.
I only get: SCI USB2Serial (COM3) and SciCmpst Diaog (COM4), and they are both still with the yellow exclamation mark.
Anyone got a good tip for me?
Thanks in advance
teewee3 said:
Hi!
I'm trying to do this myself, but I can't seem to install the drivers properly. Did you use 64-bit windows 7? And which drivers did you use?
Cause I used "SPREADTRUM SCI-USB2Serial-version-1.5.6.1" which I found via Google search, and none of the drivers I found are not digitally signed. That means they won't install properly in win 64-bit.
I only get: SCI USB2Serial (COM3) and SciCmpst Diaog (COM4), and they are both still with the yellow exclamation mark.
Anyone got a good tip for me?
Thanks in advance
Click to expand...
Click to collapse
I've managed to install them on a 32-bit windows 7. Everything I tried on 64-bit just showed the yellow mark, although they where the x64 version drivers.
Regarding the rooting process, I followed this method (As I cannot post outside links yet, just Google: "Root Android 4.0 (Novo método) Atualizado x3") and it worked at last. It's written in portuguese but it's not too difficult to follow looking at the video.
I hope it helps a bit.
Now I was trying to install a custom CWM recovery, prior to install a custom ROM, but I really don't know which one should I use (nor CWM recovery nor ROM)
If someone can point me in any directions on how to continue, it would be great.
---------- Post added at 11:53 PM ---------- Previous post was at 11:46 PM ----------
H_Bler said:
Hello,
I, don't know if the trouble is because you have win 7 64bit, but I will say how i've made it.
Windows has already intalled the device as Spreadtrum with generic drives, so any other driver that you try to install tha isn't compatible with the ones windows associated with your device will be avaliated by the system as "no compatible with your device", so what you got to do is, uninstall this generics drivers so the "spreadtrum"s will be displayed with the yellow mark, and under the "other devices" section in the device manager, then, you install manually the spreadtrum drivers that you can find in searches in two of the "spreadtrum" devices (in the drivers i've found in google searches I've got 3 different drivers General, Vendor and Modem, but i've only used General and Vendor as the other "spreadtrum" device was an ADB interface and not a modem) and the other you also install manually but with the driver in the folder "usb_driver" in "android-sdk/extras/google".
Also, when you use "update driver" follow: Search in my computer> pick in a list> have a disc , then you search in the folders of android-sdk and of the spreadtrum drivers that you downloaded.
Hope it helps.
Just one more thing, i've made it with the root access but now my Play Store don't open... it opens loads a little and then close with (the com.android.vending stopped unexpectedly...
I've tried re-instal the native apk, factory reset, everything, bout nothing works :/
I had to re install all my aps via computer with the "adb install xxxx.apk. And every other aps work normally.
Happy holidays everyone.
If anyone have a clue of what to do, i'd like to try it
Click to expand...
Click to collapse
I guess it won't be the same, but I was having problems with my Play Store also. It did not loaded anything, just giving "Unable to connect" problems, and it was solved (momentarily) uninstalling all updates. That's going back to Android Market, though it updates itself afterwards to Play Store again. You can do it in Applicatins > Manage Applications > Google Play Store, and push the button "Uninstall updates".
As I said, i think it's not the same issue, but I just wanted to share it, just in case.
Where to find the drivers?
H_Bler said:
Hello,
I, don't know if the trouble is because you have win 7 64bit, but I will say how i've made it.
Windows has already intalled the device as Spreadtrum with generic drives, so any other driver that you try to install tha isn't compatible with the ones windows associated with your device will be avaliated by the system as "no compatible with your device", so what you got to do is, uninstall this generics drivers so the "spreadtrum"s will be displayed with the yellow mark, and under the "other devices" section in the device manager, then, you install manually the spreadtrum drivers that you can find in searches in two of the "spreadtrum" devices (in the drivers i've found in google searches I've got 3 different drivers General, Vendor and Modem, but i've only used General and Vendor as the other "spreadtrum" device was an ADB interface and not a modem) and the other you also install manually but with the driver in the folder "usb_driver" in "android-sdk/extras/google".
Also, when you use "update driver" follow: Search in my computer> pick in a list> have a disc , then you search in the folders of android-sdk and of the spreadtrum drivers that you downloaded.
Hope it helps.
Just one more thing, i've made it with the root access but now my Play Store don't open... it opens loads a little and then close with (the com.android.vending stopped unexpectedly...
I've tried re-instal the native apk, factory reset, everything, bout nothing works :/
I had to re install all my aps via computer with the "adb install xxxx.apk. And every other aps work normally.
Happy holidays everyone.
If anyone have a clue of what to do, i'd like to try it
Click to expand...
Click to collapse
Hi, Everyone!
I also have a Spreadtrum S930 phone. My problem is I can't even locate the SCI general and the SCI vendor drivers... Can somebody post a link or tell me where to find these drivers? Sorry... absolute noob here. Thanks.
Will
will_power00 said:
Hi, Everyone!
I also have a Spreadtrum S930 phone. My problem is I can't even locate the SCI general and the SCI vendor drivers... Can somebody post a link or tell me where to find these drivers? Sorry... absolute noob here. Thanks.
Will
Click to expand...
Click to collapse
You can find a them here for example ge.tt/8hWh71S/v/0 (it's a 7zip file).
Cheers.
sergimas said:
You can find a them here for example ge.tt/8hWh71S/v/0 (it's a 7zip file).
Cheers.
Click to expand...
Click to collapse
I got the drivers. They work. Thanks, Sergimas.
Playvinci
Is this how you added your drivers in the .ini file? Also did you have problems loading the drivers because when I installed it (win 7 64bit) it says its unsigned and said something about having a problem installing it. so that when i installed it, it looks like the picture below. would be great if you could post a pic tutorial. btw i can run my adb anywhere since i configured it for fastboot but i still cant find my device. bummer.
playvinci said:
Is this how you added your drivers in the .ini file? Also did you have problems loading the drivers because when I installed it (win 7 64bit) it says its unsigned and said something about having a problem installing it. so that when i installed it, it looks like the picture below. would be great if you could post a pic tutorial. btw i can run my adb anywhere since i configured it for fastboot but i still cant find my device. bummer.
Click to expand...
Click to collapse
In my case, at last I got a win 7 32bit, because I wasn't able to make it work on my 64bit.
I followed this tutorial (Google: "Root Android 4.0 (Novo método) Atualizado x3") to root it, which points to the drivers ( ge.tt/8hWh71S/v/0 ). Though this zip file has 64bit drivers, in my case they didn't work properly, I saw the same screen you post.
Regarding the .ini file, you should put only (I have that myself):
0x1782
In brief, I got the drivers, installed them on a win 7 32bit, and followed the tutorial above. Don't know which could be the problem with my 64bit system
I hope it helps.
Anyway, now I'm stuck with my system rooted. I don't know how to flash a CWM recovery image, nor how to flash a new ROM, because every app I tried to do it ( Mobile Odin, ROM Customizer, ROM Manager,... ) does not detect the phone, so it is unsupported and does not let me flash it .
If someone could help it would be greatly apreciated.
sergimas said:
In my case, at last I got a win 7 32bit, because I wasn't able to make it work on my 64bit.
I followed this tutorial (Google: "Root Android 4.0 (Novo método) Atualizado x3") to root it, which points to the drivers ( ge.tt/8hWh71S/v/0 ). Though this zip file has 64bit drivers, in my case they didn't work properly, I saw the same screen you post.
Regarding the .ini file, you should put only (I have that myself):
0x1782
In brief, I got the drivers, installed them on a win 7 32bit, and followed the tutorial above. Don't know which could be the problem with my 64bit system
I hope it helps.
Anyway, now I'm stuck with my system rooted. I don't know how to flash a CWM recovery image, nor how to flash a new ROM, because every app I tried to do it ( Mobile Odin, ROM Customizer, ROM Manager,... ) does not detect the phone, so it is unsupported and does not let me flash it .
If someone could help it would be greatly apreciated.
Click to expand...
Click to collapse
Thanks Sergimas. I havent tried with a 32 bit yet. I guess I'll borrow my friend's laptop for this and see if it works. BTW... with the .ini file, when you said i should only put "0x1782", that does mean that's the only hex code i need to place on the file and delete the rest? Appreciate much for your reply.
EDIT: So i finally got my adb recognize the device and was able to list the device id however when i used the doomlord and/or he portugese root, it said it wasnt able to root it.
EDIT: Lol so yeah. I dont know what I did but i was able to root my phone using the x64 files that sergimas gave and get this, I still have the yellow icons on both spreadtrum coms (general and vendor)! I mean its freakin yellow!
(If you right click on prorperties it still would show this error) " The drivers for this device are not installed. (Code 28)
Driver is not intended for this platform.
To find a driver for this device, click Update Driver."
I think what I did was, rather than update the first spreadtrum line with google's own file via sdk, I used the composite device that came from "jungo". Then I loaded Doomlord and viola it granted me superuser access! And just when I was about to give up. Lmao.
playvinci said:
Thanks Sergimas. I havent tried with a 32 bit yet. I guess I'll borrow my friend's laptop for this and see if it works. BTW... with the .ini file, when you said i should only put "0x1782", that does mean that's the only hex code i need to place on the file and delete the rest? Appreciate much for your reply.
EDIT: So i finally got my adb recognize the device and was able to list the device id however when i used the doomlord and/or he portugese root, it said it wasnt able to root it.
EDIT: Lol so yeah. I dont know what I did but i was able to root my phone using the x64 files that sergimas gave and get this, I still have the yellow icons on both spreadtrum coms (general and vendor)! I mean its freakin yellow!
(If you right click on prorperties it still would show this error) " The drivers for this device are not installed. (Code 28)
Driver is not intended for this platform.
To find a driver for this device, click Update Driver."
I think what I did was, rather than update the first spreadtrum line with google's own file via sdk, I used the composite device that came from "jungo". Then I loaded Doomlord and viola it granted me superuser access! And just when I was about to give up. Lmao.
Click to expand...
Click to collapse
Happy to read it, I didn't even try it with the yellow marks :laugh:
sergimas said:
I've managed to install them on a 32-bit windows 7. Everything I tried on 64-bit just showed the yellow mark, although they where the x64 version drivers.
Regarding the rooting process, I followed this method (As I cannot post outside links yet, just Google: "Root Android 4.0 (Novo método) Atualizado x3") and it worked at last. It's written in portuguese but it's not too difficult to follow looking at the video.
I hope it helps a bit.
Now I was trying to install a custom CWM recovery, prior to install a custom ROM, but I really don't know which one should I use (nor CWM recovery nor ROM)
If someone can point me in any directions on how to continue, it would be great.
---------- Post added at 11:53 PM ---------- Previous post was at 11:46 PM ----------
I guess it won't be the same, but I was having problems with my Play Store also. It did not loaded anything, just giving "Unable to connect" problems, and it was solved (momentarily) uninstalling all updates. That's going back to Android Market, though it updates itself afterwards to Play Store again. You can do it in Applicatins > Manage Applications > Google Play Store, and push the button "Uninstall updates".
As I said, i think it's not the same issue, but I just wanted to share it, just in case.
Click to expand...
Click to collapse
Thanks but as you said yourself, it's not the same issue :/
I've made some discoveries regarding the problem.
After i've got the root access i removed some system apps that i wouldn't use or that i wanted update the system app.
These are the removed apps:
- Download Provider UI
- Email
- ES File Explorer
- My Favorites
- Playtalk
- Water Locker
- Sprd Note
After that the phone bricked, i've made a forced reboot via adb, and when it came back the screen didn't stop blinking, so i've put everything back and started removing one by one, it turned out that the "Playtalk" was the one that couldn't be removed.
With the issue solved, i discoverd that my market/play store didn't work, and that i could'nt realize any download from the browser, so I re-installed everything again and did a factory reset, but it didn't work to solve the problem, after searching a lot, I noted that in my system apps there is no "dowload provider.apk" only the "download provider ui.apk" that i removed in the beginning, and i'm thinking thats the problem with browser, but I don't know if it is the same problem of the market/play store because it don't even open, when i tap the icon, the screen shows: Loading, then it closes, with the "the application stopped unexpectedly" but it don't even "wait" for me to force stop, I just get back to the app laucher screen.
So, If anyone has anything for me to try to solve the issue, it will be awesome 'cause i'm trying to solve it more than 2 weeks.
PS. I already tried to install the "download provider.apk" but every version I try i get the same two problems:
- Incompatible Shared User
or
- Older SDK.
Ps 2. Regarding the market/play store issue, i already tried to clear the data/cache and neither of them work.
H_Bler said:
I've made it. *so ****ing happy right now*
Solutions:
To - Device adb recognition.
Place Hardware ID VID_xxxx in {user home}/.android/adb_usb.ini.
Font
Subscribing the adb.exe files Download Here
Font
To - Rooting
I've used one of the previos methods i've tried
DooMLoRD ROOT v4
Thanks for the tipo karimkahale
And now i'm going to enjoy my 3 sleepless days victory.
Click to expand...
Click to collapse
thank you for sharing the info. i have the same phone and have been trying to research on how to root it as well. i've tried my best to understand your instructions but i just can't seem to get it. would you mind doing a walk through of the whole procedure? what files/tools do i need and how do i use them? i also can't seem to download the doomlord tool, i always get an error saying that the source file is damaged. i will appreciate any help. thanks in advance.
Hi master of android..
Can U help me?
I have a trouble in my PC to connect my phone to PC..
My phone Axioo x one / gionee D1
My PC win7 ultimate..
1. I have download and install MTK driver
2. Install ADB driver
Both of them succes..
3. Open MTK droid tools 2.5.3.
4. And my phone doesnt detect on my pc on mtk droid tools. But for storage it can detect properly..
So I try on my friend PC win7 ultmate with thats Step..
And it works..
So for the question
1. why my PC can't detect my phone on MDT?
2.How to solve it?
Please help me
My BBM pin 74D0FAD7
Deny Charol - Indonesia
Oh I have try uninstall and Install again driver / adb driver on my PC.. but same result.. thats can't work
Hi, Did you manage to get this working?
denycharol said:
I have a trouble in my PC to connect my phone to PC..
My phone Axioo x one / gionee D1
My PC win7 ultimate..
1. I have download and install MTK driver
2. Install ADB driver
Both of them succes..
3. Open MTK droid tools 2.5.3.
4. And my phone doesnt detect on my pc on mtk droid tools. But for storage it can detect properly..
So I try on my friend PC win7 ultmate with thats Step..
And it works..
Oh I have try uninstall and Install again driver / adb driver on my PC.. but same result.. thats can't work
So for the questio:
1. why my PC can't detect my phone on MTK?
2.How to solve it?
Click to expand...
Click to collapse
Breezer28 said:
Hi, Did you manage to get this working?
Click to expand...
Click to collapse
Did you install VCOM drivers and Android CDC drivers??
Install that and try. (Google it)
I am having lava iris x1 grand with Android 5.0 root and mtk 6582 .mtk droid tool dosent detect my Android it's all blank I downloaded pdanet and installed adb driver and downloaded adb driver of my phone model from lava website but still dosent detect pleaz help me out for this
[email protected] said:
I am having lava iris x1 grand with Android 5.0 root and mtk 6582 .mtk droid tool dosent detect my Android it's all blank I downloaded pdanet and installed adb driver and downloaded adb driver of my phone model from lava website but still dosent detect pleaz help me out for this
Click to expand...
Click to collapse
I am also having this issue, I have installed MTK drivers from the offical Microsoft website as well as adb drivers. Device manager picks up my device as unknown.Has anyone found a fix for this?
[email protected] said:
I am having lava iris x1 grand with Android 5.0 root and mtk 6582 .mtk droid tool dosent detect my Android it's all blank I downloaded pdanet and installed adb driver and downloaded adb driver of my phone model from lava website but still dosent detect pleaz help me out for this
Click to expand...
Click to collapse
Use Vcom drivers
Hey guys so I solved the problem with my droid tool if u are using a lollipop version so please downgrade ur ROM it's must because u can't get the adb after the lollipop and the next thing is sometimes the PC dosnt support adb if u want to check weather ur is supporting or not ,just go to CMD and type adb if it search's for ur devices the ur safe and when it says "adb is not a command "then just search for how to solve the problem on the Google cuz when ur device doesn't support adb side load it can't be detected by mtk or easy magic Phil installer,twrp installer
Hit the like button if works for u?
To fix it, go to options, development options, and find revoke usb debuggin permissions click in it, then accept to revoke all autorizatet pc. And now connect the phone to the pc. In the Phone emerge a Windows saying To accept the permissions to use his phone in his pc, accept it and now mtk droid tool recognize ur phone.
---------- Post added at 06:48 AM ---------- Previous post was at 06:43 AM ----------
[email protected] said:
Hey guys so I solved the problem with my droid tool if u are using a lollipop version so please downgrade ur ROM it's must because u can't get the adb after the lollipop and the next thing is sometimes the PC dosnt support adb if u want to check weather ur is supporting or not ,just go to CMD and type adb if it search's for ur devices the ur safe and when it says "adb is not a command "then just search for how to solve the problem on the Google cuz when ur device doesn't support adb side load it can't be detected by mtk or easy magic Phil installer,twrp installer
Hit the like button if works for u��
Click to expand...
Click to collapse
Not need downgrade the software, lollipop work fine whith adb. But Mtk Droid tools not is compatible whith lollipop, for example if u need make backup, droid tools not is the way. U can use sp flash tool to read back and get backup running lollipop.
MTK Droid tools doesn't work anymore due to old ADB files and drivers
MTK Droid tools doesn't work well on Lollipop and doesn't work at all on Marshmallow and Nougat due to old version of ADB which it uses. Trying to replace the ADB folder with latest ADB files within MTK Droid will pop up error "Impossible to start adb"
Hello,
I have a problem with mtk droid tool.
The button "process file rom_ from flash tool" is off and is unclickable.
The read back with sp flash tool was ok. But now I can not convert the files in .bin.
Someone can help me, please?
Thank you in advance.
i had the problems too .
denycharol said:
Hi master of android..
Can U help me?
I have a trouble in my PC to connect my phone to PC..
My phone Axioo x one / gionee D1
My PC win7 ultimate..
1. I have download and install MTK driver
2. Install ADB driver
Both of them succes..
3. Open MTK droid tools 2.5.3.
4. And my phone doesnt detect on my pc on mtk droid tools. But for storage it can detect properly..
So I try on my friend PC win7 ultmate with thats Step..
And it works..
So for the question
1. why my PC can't detect my phone on MDT?
2.How to solve it?
Please help me
My BBM pin 74D0FAD7
Deny Charol - Indonesia
Oh I have try uninstall and Install again driver / adb driver on my PC.. but same result.. thats can't work
Click to expand...
Click to collapse
why mtk droid tools cant detected my device? i'd try many driver but it still cant detect. i hope smebody help me out . im still a newbie in this site . im sorry if my english not so well . please show me the way of the success . please help me to solve this problem. thank you
ChumaUmenze said:
MTK Droid tools doesn't work well on Lollipop and doesn't work at all on Marshmallow and Nougat due to old version of ADB which it uses. Trying to replace the ADB folder with latest ADB files within MTK Droid will pop up error "Impossible to start adb"
Click to expand...
Click to collapse
I found a work around for that -> https://forum.xda-developers.com/android/general/fix-impossible-to-start-adb-error-t3582571
Re: MTK Droid tools doesn't work anymore due to old ADB files and drivers
ChumaUmenze said:
MTK Droid tools doesn't work well on Lollipop and doesn't work at all on Marshmallow and Nougat due to old version of ADB which it uses. Trying to replace the ADB folder with latest ADB files within MTK Droid will pop up error "Impossible to start adb"
Click to expand...
Click to collapse
Yes, but an XDA Developer has a work-around for this. See this post:
https://forum.xda-developers.com/android/general/fix-impossible-to-start-adb-error-t3582571
Dennis
The latest version of MTK Droid tools is still using an old version of ADB.
To resolve this issue, downloaded the latest adb.exe and its two DLL files, then place them inside the adb folder that is in the file location of MTK Droid Tools.
You can download just adb.exe and its DLL files from http://adbshell.com/downloads
IMPORTANT: When I first tried to copy adb.exe from my PC's SDK folder, it didn't work. I don't know why but there was some difference between my latest adb version and the one posted on adbshell.com
After that, restart MTK Droid tools and it now detects newer devices.
Works
leroy30 said:
The latest version of MTK Droid tools is still using an old version of ADB.
To resolve this issue, downloaded the latest adb.exe and its two DLL files, then place them inside the adb folder that is in the file location of MTK Droid Tools.
You can download just adb.exe and its DLL files from ...
IMPORTANT: When I first tried to copy adb.exe from my PC's SDK folder, it didn't work. I don't know why but there was some difference between my latest adb version and the one posted on adbshell.com
After that, restart MTK Droid tools and it now detects newer devices.
Click to expand...
Click to collapse
^This worked perfectly - LEM 6 Device. Whether the next steps of TWRP work or not is TBC
i have posted earlier about my problem @ http://forum.xda-developers.com/showpost.php?p=53643114&postcount=747 and @ http://forum.xda-developers.com/showthread.php?t=2795429 and the XDA assist thread was closed so i am having to post here with more info.
i did search for "MT6572" on xda forums for any possible recoveries that might work, but now the only way i can use this tablet is via fastboot.
it doesnt have any recovery or a stock ROM.
further info about the brand and tablet:
their website www.kulala.hk ,
i have submitted query on their also and tried to contact the office in Dubai, UAE where i am located but non are operational no more. so this forum is only place i can get any help with this tablet.
i just want to get this tablet working again any rom will do
thanks.
I've found these threads for your model:
Android Development and Hacking > Android General > [TUT] MTK Root and CWM Guide (Really Easy)
Android Development and Hacking > Miscellaneous Android Development > [PORT] [TOOL] Carliv Touch Recovery for MediaTek devices
Hope it's a solution for you
philos64 said:
I've found these threads for your model:
Android Development and Hacking > Android General > [TUT] MTK Root and CWM Guide (Really Easy)
Android Development and Hacking > Miscellaneous Android Development > [PORT] [TOOL] Carliv Touch Recovery for MediaTek devices
Hope it's a solution for you
Click to expand...
Click to collapse
i dont have adb access no more only way is fastboot i downloaded the CTR but it needed adb access i am not able to use that.
We are not a support forum, but I can tell you that if you can use fastboot, you can use ADB
Go here and follow my guide which is for Nexus 7, but you can use it for all devices
FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND and FILES
and this => [GUIDE][30/10/2013]New To Adb And Fastboot Guide
philos64 said:
We are not a support forum, but I can tell you that if you can use fastboot, you can use ADB
Go here and follow my guide which is for Nexus 7, but you can use it for all devices
FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND and FILES
and this => [GUIDE][30/10/2013]New To Adb And Fastboot Guide
Click to expand...
Click to collapse
i do have those tools/folders (platform tools), but it wont work with adb, here i have taken screenshot to show.
when i was able to boot into stock rom i could turn debugging on and get adb working but now without a rom and just fastboot access only i am stuck.
I can suggest you this links => [Guide] Use your tablet/phone as PC for Fastboot and ADB
Update:
I located the distributor for KULALA brand here and visited their office and they reflashed with stock rom and its working normal now.
I will try to up the system dump or if anyone can guide how i should make a copy of that stock rom so it could help anyone else to use as well. Last time did copy of a stock rom was via adb using MTKDroid Tools and chose the backup option and it made a folder in mtkdroid tools folder of it. If thats how its done ill make a copy and post here.
Thanks for the help.
Ok and good luck
Thread closed