Related
hi! my apologies but i searched and read alot of post already on how to solve this.
i flashed Roach latest CMW how ever being so stupid i forgot to put a ROM on internal memory. did full wipe already and i have no ROM to flash as it reads internal memory only.
ive read alot of post regarding the concern, i want to try to push a ROM on internal drive using ADB but when i run "adb devices" nothing is found.
any suggestions or any links to posts that i might get help or tutorial. im not an expert on using ADB so keep instructions simple, im a noob i admit it but i just need help. thanks!
read through posts "[Troubleshooting/Solved] ClockworkMod recovery 5.5.0.4 from Koush" "Used roach's new CWM recovery, now can't intall rom" "
im on recovery and when i run adb devices it just blank. any walk through is much appreciated!
Do yo have USB debugging on?
I dont know because i was about to flash a new rom so i did a full wipe already
Did you ever get ADB working before all this? USB debugging usually have to be turn on by the user. In Settings>Developer options.
i havent with my tablet but with my htc desire hd i used adb. and when ever i flash a ROM on my tf i usually turn on usb debugging always. right now in on recovery roach r2. my ROM is on my external memory. also tried to do a nvflash how ever whenever i run the download.bat cmd opens then closes 3 secs maybe
i also got a new sdk from this forum " [GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting!" as ave said above when i type "adb devices" its just blank and does not list any device.
I had exactly the same problem - I'm not sure about tablet version that I own, but I've flashed Wipe Lite and new Recovery. I also have HTC phone that I've been using on the same PC .
I've spent an hour trying to get my TF back on feet and I managed it.
I would recommend uninstalling all HTC and ASUS software and drivers, rebooting PC and installing just ASUS PC Suite. It worked in my case - suddenly Device ID showed up for a few seconds before ADB reported "no device" again.
So I've pushed Rogue XM Recovery to data/media:
adb push roguexm data/media
Of course use name of zip file instead "roguexm" in command above.
After that zip file showed up on sdcard and I could flash it - it doesn't support AROMA but it works quite fine otherwise.
Hope it'll work in your case. Good luck!
Hope it will help
I once were in your case, did full wipe and forgot to put a Rom in internal memory. But in my case I just rebooted the transformer and all of a supprise, my tablet reverted to the stock Rom! I dont know how this happend but may be Asus did something to keep stock Rom persistent whatever you have flashed roms or CWMs.
So i hope this also happened in your case, just give it a try. Good luck!
If he did "Full Wipe - factory reset" then he should be able to boot HC/ICS and from that copy files onto internal /sdcard.
But if he used Android Revolution Super Wipe script either Lite or Full then he has nothing to boot into, no system at all - I've done that Only thing that left was recovery without external sdcard support, so I had nothing to install...
ASUS and HTC drivers have some issues and make everything harder than it should be, that's why I recommend to uninstall all HTC and ASUS software, rebooting PC and installing ASUS PC Suite only, to have "clean" drivers on PC.
I've tried different drivers and none of them worked, until I've done that.
Ok, I'll try to write it simple, I'm not sure if I can post links so just in case I'll give thread names. If it will be too simple don't get mad - ok?
1. Uninstall ASUS and HTC software, reinstall ASUS software like mentioned above.
2. Create folder on your C: drive called CWM
3. Go to post "Eee Pad Transformer Android Development\[Recovery] Rogue XM Recovery v1.3.0 (CWM-based Recovery v5.0.2.7" thread - http://forum.xda-developers.com/showthread.php?t=1446019
and "save as..." cwm_recovery-5027_rogue_rburrow-tf101-r1.zip to C:\CWM
4. Highlight/select command below:
adb push cwm_recovery-5027_rogue_rburrow-tf101-r1.zip data/media
then right click on it and select "copy" - it will save you typing it later.
5. Boot Recovery on your Transformer and connect it to PC, let system install device drivers
6. Click START, "Run...", type: cmd
7. It should show you path to your profile folder - C:\Users\yourname>
8. Type: cd /CWM
it will change folder to C:\CWM>
9. type: adb devices
(it should give you your device ID, if it still will give "no device id" then there I can't help you - I'm sorry)
10. right click on black background and select "paste" (you'll see command that you've copied from number 4), then press enter
11. It should copy recovery onto your internal sdcard - you will be able to select it from tablet
12. type adb kill-server and disconnect tablet, install new recovery and from that one you will be able to select external or internal sdcard
Notes:
I don't know why but I was able to send only small file from CWM-adb connection, it kept disconnecting quite quickly that is why I recommend sending Rogue XM Recovery instead of whole new ROM.
Other thing - it may depend on what windows system you have - I'm on Win 7 x64 (don't remember how it worked on other versions) and I can paste onto cmd (black) window without problems from right click menu. If you won't be able to paste there or you'll get some rubbish, try to right click on top bar and select "Edit" and then "Paste".
Ok, that's all. Hope it will work.
thanks for all inputs. i did a full wipe but not as scripts. i wiped manually. i did try to reboot but stuck as eepad screen. will try to re-install asus drivers and uninstall htc ones. hopefully i get it done today. i will update later...
still no luck. device not found. im going to try to install new sdk... i hope it works. ive already removed htc sync and drivers. also re-installed asus sync and updated drivers. on device manager detects on other devices transformer but drivers are not installed.
yahoo! got it working now. i had to enable adb usb Drivers for Nvidia Tegra based Android Tablets and re-install SDK download android usb and learn What Is ADB And How To Install It With Android SDK.
finally got my tablet working again and my first thing to do is have a copy of a ROM and CWM in both storages!
thanks alot for the input and for helping!
thanks Kraliz
monespeso said:
yahoo! got it working now. i had to enable adb usb Drivers for Nvidia Tegra based Android Tablets and re-install SDK download android usb and learn What Is ADB And How To Install It With Android SDK.
finally got my tablet working again and my first thing to do is have a copy of a ROM and CWM in both storages!
thanks alot for the input and for helping!
thanks Kraliz
Click to expand...
Click to collapse
Could you tell me how to do that? Because I have the exact same problem.
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.
**UPDATE**
NEW VERSION
THIS RELIES ON ADB COMMANDS, SO IF YOU DO NOT HAVE USB DEBUGGING TURNED ON, OR A CUSTOM RECOVERY TO BOOT TO, THEN IT WILL NOT BE AS SIMPLE AS JUST RUNING THE PROGRAM.
Another user was having issues because he had an emulator installed, so I updated the file to give you the choice between an emulator, or device. I intend to update further to allow you to check for and select an individual device, that will come soon..
----------------------------------------------------------------------------------------------------------------
Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.
For anyone having issues...
If you had not previously activated USB Debugging, there are several steps you need to follow in order to enable ADB
SCREEN WORKING TOUCH BROKEN NO CUSTOM RECOVERYfirst, if you can see your screen, and have access to an otg cable, plug a mouse in to the otg cable, and the otg cable into the phone. Use the mouse to enable USB debugging, or to transfer files.
HOW TO ENABLE USB DEBUGGING
SCREEN WORKING TOUCH BROKEN WITH CUSTOM RECOVERYboot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
SCREEN BROKEN TOUCH BROKEN WITH CUSTOM RECOVERYboot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
SCREEN BROKEN TOUCH BROKEN NO CUSTOM RECOVERYnow things get complicated...
*The following is paraphrased from this site
1. download the custom recovery image for your device. Copy the recovery image to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
I recommend clockwork mod non touch from this page
2. Power your device off and reboot your device to FASTBOOT or DOWNLOAD MODE depending on which type of device you have.
(most devices are fastboot, SAMSUNG typically uses DOWNLOAD MODE)
how to boot to fastboot or download mode
[FASTBOOT]3. Connect your device to your computer via USB and wait till you see the PC recognize the device
to check if your device is in fastboot and connected use CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
fastboot devices
you will see a list of connected devices. if not, something went wrong.
4. Launch Command Prompt and type the following commands;
cd c:\android (this is your ADB path, c:\android is default)
fastboot flash recovery c:\recovery.img
5. Wait for the process to finish.
6. Turn device off then boot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
[RECOVERY MODE (SAMSUNG)]USE THE INSTRUCTIONS ON THIS PAGE
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
HOPEFULLY THIS HELPS. REMEMBER TO CHECK THE FORUM PAGE FOR YOUR DEVICE IF YOU RUN INTO ISSUES. THIS ISN'T ANYTHING THE MEMBERS OF XDA HAVEN'T DONE THOUSANDS OF TIMES OVER.
Don't forget to hit "Thanks"
i'll bump this thread for those who didn't see this amazing tool, this tool is really useful, thank you very much
Hi,
Sturggling to find the .adb file as my phone shows up as a "Portable Device" any ideas?
Cheers
Thank you!
I joined just to say thank you to FuzzyMeep Two. Thanks for an awesome tool! It worked better than advertised!
:good:
Thanks again!
-th3r3isnospoon
Question
Hi! Can I use that to restore data not from sdcard but from internal memory of the device? I was storing photos on device memory on my Asus TF300T and now its bricked. I need to restore these photos, my girlfriend has something like 1000 of them from her trip to Caracas. Its very important for her. I already managed to connect the device through fastboot and I launched anb in cmd. What should I do next? Please help me guys
koperkowy said:
Hi! Can I use that to restore data not from sdcard but from internal memory of the device? I was storing photos on device memory on my Asus TF300T and now its bricked. I need to restore these photos, my girlfriend has something like 1000 of them from her trip to Caracas. Its very important for her. I already managed to connect the device through fastboot and I launched anb in cmd. What should I do next? Please help me guys
Click to expand...
Click to collapse
Yes, when it references SD Card it means the internal "SD" storage built in to the phone, not the removable one. It should work as long as ADB can connect.
Sorry for taking so long to reply, i really hope you got your pictures back.
FuzzyMeep Two said:
Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.
P.S. I apologize if i have posted this in the wrong place, if so please let me know.
Click to expand...
Click to collapse
Really great stuff - so simple but so effective. Cheers and thanks.
Error msg
zobes said:
Really great stuff - so simple but so effective. Cheers and thanks.
Click to expand...
Click to collapse
When i run that tool, i get the error mesg: more than one device and emulator,
I dont want to uninstall the emulator coz it was a headache getting it running
How i procede to select the device to be used
alisdairjk said:
When i run that tool, i get the error mesg: more than one device and emulator,
I dont want to uninstall the emulator coz it was a headache getting it running
How i procede to select the device to be used
Click to expand...
Click to collapse
NEW VERSION
Try this, i haven't gotten to test it, so please let me know if it worked for you, I added the option of selecting an emulator or USB device, because of your post. Hopefully it helps.
When I try to run this I also get an error message saying that the adb.exe file cannot be found.
Please can anyone help?
Joeb29 said:
When I try to run this I also get an error message saying that the adb.exe file cannot be found.
Please can anyone help?
Click to expand...
Click to collapse
Have you also installed ADB, as well as this software?
I'm also having an issue - I have installed java, java SDK and ADB, so I can now run the data recovery tool. But when I do I'm getting "error:device not found" - am I missing drivers or something? I couldn't get all the way on the ADB configuration, because part of it required me to do something on the device... anyway, looks like the computer isn't recognising the the phone at the moment.
Any help very gratefully received (phone is Samsung Galaxy S2).
joffmeister said:
Have you also installed ADB, as well as this software?
I'm also having an issue - I have installed java, java SDK and ADB, so I can now run the data recovery tool. But when I do I'm getting "error:device not found" - am I missing drivers or something? I couldn't get all the way on the ADB configuration, because part of it required me to do something on the device... anyway, looks like the computer isn't recognising the the phone at the moment.
Any help very gratefully received (phone is Samsung Galaxy S2).
Click to expand...
Click to collapse
I have the same situation right now. Managed to make your program work then I get the "error:device not found". My phone does show up in the computer folder(albeit not in mass storage mode), but isn't that what this program was made to work around?
My phone is a LG Optimus G with a smashed glass... The LCD still displays fine, but I'm stuck at my swipe lock because the digitizer is dead.
Thank you for your help and your wonderful program.
Thanks for this app. My girlfriend broke her screen and digitizer on her Galaxy S4. She never turned USB Debugging mode and has a lock on her screen. When using your app I get the same error when I use adb by itself which is "error: closed". ADB detects my phone but any command I use in ADB or with your app I get that same error.
Do you know how to fix this? Thanks in advance.
Thanks a lot man.
dude this tool is just amazing and does exactly what it promised. I was spending sleepless nights thinking about how to recover my data from my broken galaxy nexus and now that I have it I can rest easy. Seriously can't thank you enough for this. Just joined xda to thank you buddy.:laugh::fingers-crossed:
Getting an error "The system cannot find the path specified."
I start the recovery tool, set eh adb path successfully, and then I get this error. If I try running the recovery to pull the DCIM library I get this:
"error: device not found"
What can I do?
Thanks!
Either way this is an amazing tool, seeing how it helped some people already. :good:
Hi, Seem to have the same problem as many others, Device not found. I cant change to MTP mode on my LG G2.
I hope someone can find a solution to this problem.
Program seems amazing doh.
Hello,
This is really a great tool ! I was wondering if you could add the possibility to recover the external sd card aswell.
Device not found
Tried to recover a Samsung Galaxy S3 mini with a broken screen
I installed adb and RecoverData, run it and then get a "device not found error"
What can I do?
Amazing app. thank you so much :good:
FuzzyMeep Two said:
**UPDATE**
NEW VERSION
Another user was having issues because he had an emulator installed, so I updated the file to give you the choice between an emulator, or device. I intend to update further to allow you to check for and select an individual device, that will come soon..
----------------------------------------------------------------------------------------------------------------
Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.
Don't forget to hit "Thanks"
Click to expand...
Click to collapse
Hi, Thank you very musch, It's so usefull for me.. :angel:
Hi everybody !
I got my new OPO phone Tuesday, and I decided to root & unlock it. I downloaded Bacon Root Toolkit v1.0.2, and runned it. I first opened it and wrote that i had an old version of android, because my OPO was not updated yet, so the rooting didn't work. So i updated Cyanogen Version on my OPO today, it's now 64GB SandStone, XNHP44S-KTU84Q. I clicked on Full Driver Installion - Automatic + Manual, and then went to Step 3 as recommended. I downloaded Google Drivers, then clicked on Configure ADB. So appears the Device Manager, i clicked on A0001 ( OnePlus One ) and then tried to Update Drivers Software, but i can't have the " Android Devices " in the selection, i only have " USB MTP Device ". And if i try to Fastboot the OPO, it doesn't appears anymore in the Device Manager.
My friends didn't have that problem so they couldn't help, maybe could you ?
Sorry for bad english, i'm a French student ...
Waiting for an answer soon ! Cya !
Chyquito said:
Hi everybody !
I got my new OPO phone Tuesday, and I decided to root & unlock it. I downloaded Bacon Root Toolkit v1.0.2, and runned it. I first opened it and wrote that i had an old version of android, because my OPO was not updated yet, so the rooting didn't work. So i updated Cyanogen Version on my OPO today, it's now 64GB SandStone, XNHP44S-KTU84Q. I clicked on Full Driver Installion - Automatic + Manual, and then went to Step 3 as recommended. I downloaded Google Drivers, then clicked on Configure ADB. So appears the Device Manager, i clicked on A0001 ( OnePlus One ) and then tried to Update Drivers Software, but i can't have the " Android Devices " in the selection, i only have " USB MTP Device ". And if i try to Fastboot the OPO, it doesn't appears anymore in the Device Manager.
My friends didn't have that problem so they couldn't help, maybe could you ?
Sorry for bad english, i'm a French student ...
Waiting for an answer soon ! Cya !
Click to expand...
Click to collapse
first off root kit is not needed to root your phone. Secondly you did not have to update it prior to rooting as well. Now I came across this issue with my friends phone the other day and used this method here.
It works just dont skip a step and please use the stickied method in General to root your phone. You learn nothing with root kits. Its also keeps you from searching properly and finding answers.....
...
playya said:
first off root kit is not needed to root your phone. Secondly you did not have to update it prior to rooting as well. Now I came across this issue with my friends phone the other day and used this method here.
It works just dont skip a step and please use the stickied method in General to root your phone. You learn nothing with root kits. Its also keeps you from searching properly and finding answers.....
Click to expand...
Click to collapse
I did Step 1 and Step 2 successfully, now i reached the Step 3, and did a) and b). When i do c) step, i cannot find my OPO in the list, it is int the " Hided Devices " and when i try to update drivers softwares, i just have : " Android Devices -> USB MTP Device ", and not, Google Inc. - Android Bootloader Interface., how can i find it ?
Chyquito said:
I did Step 1 and Step 2 successfully, now i reached the Step 3, and did a) and b). When i do c) step, i cannot find my OPO in the list, it is int the " Hided Devices " and when i try to update drivers softwares, i just have : " Android Devices -> USB MTP Device ", and not, Google Inc. - Android Bootloader Interface., how can i find it ?
Click to expand...
Click to collapse
you are confusing me if you followed the directions then put your phone in Fastboot mode you should see your phone popup in your device manager list.
Install the latest Samsung drivers: SAMSUNG USB Driver v1.5.33.0
Restart the computer (very important)
Go to Device Manager, find the Android device, and select Update Driver Software.
Select Browse my computer for driver software
Select Let me pick from a list of device drivers on my computer
Select ADB Interface from the list
Select SAMSUNG Android ADB Interface (this is a signed driver). If you get a warning, select Yesto continue.
Done!
Please dont take this wrong but is this your first android phone and rooting? If so there is soooo much you should be reading before doing this. Also make sure this is what you want to do. With rooting what goal are you trying to achieve
playya said:
first off root kit is not needed to root your phone. Secondly you did not have to update it prior to rooting as well. Now I came across this issue with my friends phone the other day and used this method here.
It works just dont skip a step and please use the stickied method in General to root your phone. You learn nothing with root kits. Its also keeps you from searching properly and finding answers.....
Click to expand...
Click to collapse
playya said:
you are confusing me if you followed the directions then put your phone in Fastboot mode you should see your phone popup in your device manager list.
Install the latest Samsung drivers: SAMSUNG USB Driver v1.5.33.0
Restart the computer (very important)
Go to Device Manager, find the Android device, and select Update Driver Software.
Select Browse my computer for driver software
Select Let me pick from a list of device drivers on my computer
Select ADB Interface from the list
Select SAMSUNG Android ADB Interface (this is a signed driver). If you get a warning, select Yesto continue.
Done!
Please dont take this wrong but is this your first android phone and rooting? If so there is soooo much you should be reading before doing this. Also make sure this is what you want to do. With rooting what goal are you trying to achieve
Click to expand...
Click to collapse
This is my second Android phone, and i never rooted my phone. A friend told me to do this and i have to do this if i want to get WiFi access at my school.
When i'm the Device Manager, the OPO doesn't appears in Fastboot mode... Neither Android Device...
I downloaded the Samsung Driver, but after rebooting the PC, i can't see any Android Device in the Device Manager. I only have MTP, that contain A0001, Android ADB Device, and something else useless. And i can't update Android ADB Device's Drivers Software...
Chyquito said:
This is my second Android phone, and i never rooted my phone. A friend told me to do this and i have to do this if i want to get WiFi access at my school.
When i'm the Device Manager, the OPO doesn't appears in Fastboot mode... Neither Android Device...
I downloaded the Samsung Driver, but after rebooting the PC, i can't see any Android Device in the Device Manager. I only have MTP, that contain A0001, Android ADB Device, and something else useless. And i can't update Android ADB Device's Drivers Software...
Click to expand...
Click to collapse
OK with android and rooting following instructions is key. By your response you did not follow all the steps. Please follow each one to the letter
There are more steps for you to do after a reboot
Hi.
I have done something stupid
Some website claimed that rom manager from clockworkmod would not work unless twrp was installed. (I guess they meant "for getting the CWM Recovery Boot Menu to work").
I had already rooted my device (Denver Tablet TAQ-80053 ARMv7 with Android 4.1.1) but I thought why not flash to TWRP with the file: "CWM-based-Recovery-v6.0.3.3-signed.zip" ?? BAD idea
Now "Recovery Mode" is only the "TeamWin Logo" then BLACK SCREEN and nothingness ??
Everything else is somewhat normal:
1) I can boot normally into the start screen of Android 4.1.1 and run applets etc.
2) I can connect to Windows 7 (x64) and get file access to everything.
But: Any flashing tool for windows cannot "see" my device, and I very much doubt that it could be a driver problem since I get full access to drives and files on the tablet (USB-connected to Windows 7 x64).
Do you have any thoughts about that ? Because to me it seems logical that a working windows-driver would also work with ADB or ... ?
I also tried the ADB installation with SDK etc. Everything installs fluently with no errors but when I do the "adb devices" command no devices are listed at all ?? The command "ADB Shell" returns an error.
Since I know about the settings needed on the tablet I have: set USB Debug Mode to ON and everytime I plug it in I select "Mass Storage Mode" to get file access from Windows; and it works fine.
As stated above, everything works except "boot into recovery mode" and ADB being able to "see" my device. Not even CWM Rom Manager can boot into recovery mode ??
I want to be able to flash a new OS but recovery mode seems to be the only way apart from the USB to Windows. I cannott accept the notion that the device is "almost bricked" just from installing the wrong
recovery image and now I cannot go back .....
I have spent too much time already and I have discovered that I am not the only one with this problem but I cannot find any solution (that actually works) anywhere. So writing to you guys must be my last
hope. The alternative is getting an axe and chop it to pieces just to be shure that it's completely dead and my $150 lost forever; gone out the window :\
Can anyone please advise me what to do ??
/Pete
PS: OMG captcha is unreadable 30 times or more . . . and then the session ran out. Great
Hi there,
I'm sorry but I can't find anything related to your question/device.
Please post that in the forum bellow for more answers from the experts but first you must register an account on XDA forum:
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck