I can't seem to work ADB or anything like that, I've read most of the threads on here and tried to follow numerous tutorials and this is my first android phone.
I've enabled USB Debugging, however when I run install.bat with superuser.apk in the same folder it just tells me that there is no device found, not sure what to do
-thanks
I had a similar issue. Easiest thing to do is install omega .
Make a back up of your stock Rom first then flash omega without wiping your data.
It has full root built in
Sent from my GT-I9300 using Tapatalk 2
Your problem is you need to run adb start-server in a terminal in the sdk/platform folder.
It needs to start so the install bat can talk to the phone.
Had the same issue yesterday in my case there was a strange problem with the drivers. All was installed fine i could see ADB device in device manager however adb did not se the device.
Finally installed kies on a computer that never had anything installed like mobile phones etc than run install.bat and all was ok.it took around 15 sec to find the phone and drivers and finish all the rooting operations.
Still dont know what kind of a driver conflict is it...Some report that reinstalling kies helps but not in my case.
If u can try on another computer.
Related
I previously rooted my phone without difficulty. Using titanium backup and an number of other apps that required superuser/root acess. I am now trying to flash a Froyo rom. I had upgraded the home PC to a win 7 Pro (64 bit) machine and for some reason I can not get USB drivers to work. I have download drivers from several different threads. SOme fail to load while others seem to install. The Fascinate is recognized but not the modem and I can not get odin to see the device in software download mode.
Any thoughts?
Your best test of whether drivers are installed properly is to install adb and do 'adb devices'. If one shows up in the list you are installed correctly.
You may have an incorrect driver installed. The best place to download these is Samsung directly. If all else fails you can try a different computer and/or heimdall instead of odin.
Swyped w/ XDA App. A clean tie attracts the soup of the day.
get the drivers from samsung, or one of the noob threads, and be sure u mount then first go to setting/applications, make sure unknown sources is checks, and then go to development and make sure usb debugging is checked, then plug it in, and on ur phone u should get an option in notification bar that says transfer files.. click on it.. and then click mount.. n try again.. u should have to do this at least once on every phone to get the drivers properly installed.
There are alot of things that are different compared to htc devices so far.
Now I rooted using this method:
http://forum.xda-developers.com/showthread.php?t=1285894
Downloaded and installed kies drivers, Downloaded odin, downloaded and loaded codeworkx, used superoneclick..it all went smooth. I tried different roms through cwm. Currently I'm running cm7 as I am so used to it. But here is my question, on two different pc's when I tried to run "adb devices" it cannot find my device. I wanted to push something and couldnt find my devices. I have the Superuser icon in my apps. Also when I tried to su in terminal app it said permission denied. I'm a bit baffled lol. All my drivers seemed to have installed fine.
SysAdmNj said:
There are alot of things that are different compared to htc devices so far.
Now I rooted using this method:
http://forum.xda-developers.com/showthread.php?t=1285894
Downloaded and installed kies drivers, Downloaded odin, downloaded and loaded codeworkx, used superoneclick..it all went smooth. I tried different roms through cwm. Currently I'm running cm7 as I am so used to it. But here is my question, on two different pc's when I tried to run "adb devices" it cannot find my device. I wanted to push something and couldnt find my devices. I have the Superuser icon in my apps. Also when I tried to su in terminal app it said permission denied. I'm a bit baffled lol. All my drivers seemed to have installed fine.
Click to expand...
Click to collapse
If "adb devices" failed you either have a driver problem or USB debugging is turned off
I do recall that with recent CM7 builds on my Infuse, root didn't work on first boot. I had to open the Superuser app or reboot, not sure which one fixed the problem.
Entropy512 said:
If "adb devices" failed you either have a driver problem or USB debugging is turned off
I do recall that with recent CM7 builds on my Infuse, root didn't work on first boot. I had to open the Superuser app or reboot, not sure which one fixed the problem.
Click to expand...
Click to collapse
usb debugging has been on. This issue I mention happened when I was stock, after I tried cognition, and now using cm7. Might be a driver issue, is there any other samsung drivers I can try for my windows machines?
SysAdmNj said:
usb debugging has been on. This issue I mention happened when I was stock, after I tried cognition, and now using cm7. Might be a driver issue, is there any other samsung drivers I can try for my windows machines?
Click to expand...
Click to collapse
if you are on CM7, i think you need to install the nexus S drivers, which are included in the Android SDK. you will need to run the emulator and run the update in SDK
Since you mentioned this has happened on two different computers, I doubt my advice will help. With that said, whenever I've had issues like this, I've found that USB ports tend to be the culprit. Have you been using ports on the front of a tower? Have you tried the ones on the back as well? Again, just taking a shot at a possible fix...
i need help, i have tried everywhere and can't find anything and any help would be greatly appreciated
i'm on the road to root my samsung galaxy fascinate and have ran into a laundry list of problems. i have rooted many android phones coming from eclair, froyo, and gingerbread, but seem to be stuck at the slightest of problems when it comes to the fascinate.
i can not install the drivers to the fascinate. i have searched through the web for all the drivers and have tried every possible galaxy driver. the driver simply won't install on my windows 7 prof 64bit machine. i have never ran into this problem before with any other phone. every time i try to install the driver it gets to the very end of the install then pops up with the message "windows was unable to install the driver"
It also gave me the option to view the failed windows installation log, which after many successful steps, at the end the log shows this error:
Action ended 1:26:53: ShowMsiLog. Return value 0.
=== Logging stopped: 12/16/2011 1:26:53 ===
MSI (c) (0C:08) [01:26:53:750]: Product: SAMSUNG USB Driver for Mobile Phones -- Installation operation failed.
MSI (c) (0C:08) [01:26:53:750]: Windows Installer installed the product. Product Name: SAMSUNG USB Driver for Mobile Phones. Product Version: 1.3.550.0. Product Language: 1033. Manufacturer: SAMSUNG Electronics CO., LTD.. Installation success or error status: 1603.
i have also attached the entire log
the first thing i did was plug in the phone, which windows sensed this and automatically installed a driver, not sure which. after this i unplugged the phone and then checked "usb debugging" for rooting purposes and plugged the phone back into the computer which windows then installed another driver automatically, then following the steps from xda to root the phone, i downloaded the given drivers which is where the problem first occurred and the drivers were unable to download.
I'm simply trying to get root access to the phone and can't do anything with the phone with crappy drivers...i can't even mount usb sd card now to transfer data anymore. the drivers have completely been shot. i desperately need help. please
also what is the absolute easiest way to root the fascinate? is it with one click root or with Odin? Because the fascinate just updated itself from 2.2.2 EH05 to 2.3.5 EH03 and i'm not sure which program supports rooting which version of android. also all other android devices simply give root access to the stock rom, which is great cause i get to keep all my apps, messages, contacts...etc, then simply titanium backup everything and transfer it over to the new rom. is it different with the fascinate? will rooting the device simply flash a completely new rooted rom? therefore loosing everything? if anybody has any answers to any of these questions, please be my hero. thanks
Uninstall everything you previously installed in the way of Samsung drivers (in fact, you could use Windows 7 backup and restore to restore your PC to the state it was in the day before you installed the drivers as they are sometimes hard to uninstall completely). Reboot and simply plug your phone (with USB debugging of course), and let Windows automatically install the drivers for you like it did before you installed the ones linked to on XDA. This time, if your PC recognizes your phone, just keep the drivers you have and don't install the ones linked to. Those drivers from the guide are for those whose PC doesn't automatically install working drivers. From that point, just follow the rest of the guide and skip the install drivers part. You will not have to install any further drivers unless you flash an AOSP ROM, in which case you'll have to follow the instructions in the OP of the ROM thread. I hope this works for you.
Has anyone seen John Connor?
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
bigwhat said:
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
Click to expand...
Click to collapse
root is not flashed via odin, rather cwm is...then the root file su_2.6.3.1 is flashed via cwm. If you need directions section 5 of my guide in general section has it covered...everything needed is there including the correct recovery and root file.
I will tell you what...the Fascinate is probably the biggest pain in the ass phone...I tried forever to root my friends and couldn't get it done...need to try again I guess, but it was a driver issue as well..ODIN just wouldn't recognize the dam phone
Use Droidstyles guide. Very easy to follow. Also, the USB cable for some reason seams to be a bit finicky at times with this device. Unplug from phone and replug. Sounds odd but trust me, I have done this many times.
Sent from my SCH-I500 using XDA App
I am having a problem too and it's not covered anywhere i've seen to date. I've got an XP and a Win7 box at home. On both, I've tried with no drivers and i've tried with every other driver set I can find and every time I hook the phone up to the machine it pops up saying USB device couldn't be recognized or something. I'm going nuts! I've never had so much difficulty in my life, not even the first time changing ROMs on anything.
Droidstyle- I've seen your guide and unless I missed it doesn't cover this. Have you seen or heard of this and have any ideas at all?
Thanks!
Posted this on the general discussion section but have had no replies, hopefully someone here can help?
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
have you try on a different pc?
maybe on your PC there is some problem with the drivers.
Moreover to connect via
adb u must enable Debug mode on your device in the application menu.
To flash kernel or other directly from your sd you can use the clockwordmode, but to install it you must before
install it and i fear you must use your cable connection
Sent from my GT-I9100 using XDA App
I have tried multiple PCs and a mac, even windows on bootcamp. I have installed drivers on every one, even uninstalled and reinstalled on one. One PC, my laptop was a fresh windows install (it was a linux box but I needed windows to use Odin). I was in debug mode and not in debug mode when attempting adb. Thanks for the suggestions though. As I said, I have tried numerous things and am completely stuck! so frustrating!
"I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device"
Exactly there... you can try to force device to install a different driver.
Double click the unknown device then driver then update driver then find software in your computer then choose manually from a list of device drivers in your computer then show all devices you should see "android adb interface" or something related to google or android.
Try it... i hope this can help you.
ive tried every method to unlocking the bootloader and i cant get the command prompt to do anything it wont reconize my device is their an easier way into unlocking and rooting
If you can't get adb working then you shpuldnt have a rooted phone in the first place.
Sent from my HTC6435LVW using xda app-developers app
Sounds like you don't have all the drivers installed and/or don't have sdk tools installed.
And no, there is no other way to unlock it.
orangechoochoo said:
Sounds like you don't have all the drivers installed and/or don't have sdk tools installed.
And no, there is no other way to unlock it.
Click to expand...
Click to collapse
Download the latest SDK (search for 'adt- bundle -windowsx86') and extract that file into your C drive.
There will now be an 'adt-bundle-windowsx86' folder on your C drive, inside that is the SDK manager.exe
Run SDK manager-it will create the adb tools you will need AND put them in the "sdk/platform-tools folder"
after the SDK tool opens, you only need to add the 'google usb drivers' (1 item) No need to select that box
as is checked off by default anyway. All other required adb files will have installed already. Install those google drivers
and you should be ready to unlock the bootloader. I would put all the OTHER required files to unlock it in the 'platform-tools folder also.
Then go to that platform-tools folder, hold down shift key and right click in an open area, choose 'open command prompt here' then just follow the tutorial pasting in the commands.it will work...
Jduncan312 said:
ive tried every method to unlocking the bootloader and i cant get the command prompt to do anything it wont reconize my device is their an easier way into unlocking and rooting
Click to expand...
Click to collapse
This work perfectly for me http://forum.xda-developers.com/showthread.php?p=34582289
https://www.youtube.com/watch?v=glGdw2HAumg&feature=youtube_gdata_player
I followed this video to get sdk installed
Thats the same vid that i used too and it work just fine for me, did you also changed your local variable like the vid, also on your phone make sure you have usb debugging enabled
Gungrave223 said:
Thats the same vid that i used too and it work just fine for me, did you also changed your local variable like the vid, also on your phone make sure you have usb debugging enabled
Click to expand...
Click to collapse
I'm not the one with the problem, I'm already unlocked, rooted, and rommed
ive already gotten the sdk installed ive watched droidmodderx video on how to do it and still cant get no where im new to rooting htc phones ive done rooted motorola and samsung phones and their not as hard
I had a issue with the drivers installing from my phone to my pc. I installed pdanet 3.5 (Google it for pc, play store for phone) on my pc and phone. Let pdanet install the drivers, once installed you can uninstall pdanet.
Once the drivers installed I was able to see my device in adb. Sorry if one of the links above were for this fix I didn't click them.
HTC DROID DNA
orangechoochoo said:
I'm not the one with the problem, I'm already unlocked, rooted, and rommed
Click to expand...
Click to collapse
Lol yea i know i was just saying that that method work for me too.
Jduncan312 said:
ive already gotten the sdk installed ive watched droidmodderx video on how to do it and still cant get no where im new to rooting htc phones ive done rooted motorola and samsung phones and their not as hard
Click to expand...
Click to collapse
Well if you type the command adb device and nothing and your device doesnt show, there is 2 possible reason for the issue the first is that your phone is not in adb mode, go to the setting/developer options and make sure usb debugging is enabled
the second is that your phone adb driver weren't installed correctly i had the issue when i watch this video because when i was in sdk manger i unchecked the option to install the android 4.2 (API17) package, disconnect/reconnect phone and the adb driver install just fine after that
Sadly there is no other way to remove the verizon cid block as of right now
Jduncan312 said:
ive already gotten the sdk installed ive watched droidmodderx video on how to do it and still cant get no where im new to rooting htc phones ive done rooted motorola and samsung phones and their not as hard
Click to expand...
Click to collapse
If you have sdk installed right then adb will be working...then if you follow the tutorial in the dev section (jcase) it will work. I have heard that some older versions of adb didn't support restore and that WAS an issue for me so I re installed the latest version of SDK and it then worked flawlessly. That's why I suggested getting the latest version and reinstalling. Maybe not the problem but you have had no luck with your old version so why not. You need to go slowly and read carefully. The process is really 3 sections, bootloader fix, official HTC website unlock code process and then rooting itself. It takes a while but it's how everyone got there, some easier than others.