i've rooted my own Samsung Fascinate, via instructions posted in the forums, and am trying to do the same for my girlfriends, but my computer keeps dropping sight of the phone upon the first reboot. Initially it will see it, and after the reboot, i've gone through the motions of disabling the media sync, waiting for the computer to see it, and sometimes it does, but it either won't or it comes back as USB storage. either way, the root is unable to finish because the computer doesn't see it as the phone anymore. i have reinstalled the samsung drivers as well. Help!, i'm sure it's something simple.
is 'odin' the process of manually rooting via the command window and inputting the commands to root by hand?
some insight and maybe i can get some other opinions as well. It seems there is a file native to the phone 'tool_bootlauncher.exe' which wants to run whenever the device is connected to the computer. I believe it is tied to the media sync. Whenever the phone is reconnected after the driver install, it goes through a series of 'hardware found' flags...android usb, android device, a couple others i cant recall, and lastely, usb mass storage. for rooting, this is all fine (at least the fascinate_v02 one click), but when the device is connected the second time to the computer, the verizon file takes over and regardless of disabling the media sync, will either connect as as storage device, or more commonly, not at all. Thanks sheepdog, the usb driver trick worked....for a moment. I did reinstalll the drivers and went through it again, and left the 'install software' from verizon to help interact with the phone pop up up to see if i could get further. i actually got excited, because though it didn't show my phone, it also didn't error out and actually got to exploiting my phone, then when it tried to replace files, i got the 'error, device not found'. So damn close. it's gotta be the dang startup files native to the phone and what it's supposed to do when it gets connected, but i'm at a loss. i will try it again in the morning, and if nogo, i guess post #5, though it looks scary. I'm no pro, nor even a novice, just know enough to get myself into trouble. Thanks to all who responded so quickly! i am amazed and in awe! i am grateful. Pointers and direction are welcome, cause i'm still scratching my head! Happy Hunting (thanks again sheepdog)
ok, maybe i'm a DA or was just too tired. i ran the one-click process again, only this time after reboot, i let the media scanning occur, never got the media sync icon, unplugged the phone, plugged it back in, got the usb icon(which wasn't always coming up in previous attempts), pulled it down and selected it to copy files from computer and then selected the 'mount' option for the sd card. waited a few, then hit 'enter' to continue in my dos window and waalaa! happy rooter! thanks!
Still trying to figure out why this isn't working. I've tried re downloading the drivers at least 5 times. I've tried going through all the steps multiple times but the same problem is occurring every single time.
"Testing if your device is connected. 'adb' is not recognized as an internal or external command, operable program or batch file."
My guess is its something to do with the new update over the air? Or maybe something to do with the drivers but if I've downloaded them over and over again successfully it shouldn't be a problem. Is there another one click program that I could use?
Alright, so I followed your directions. I turned off the phone while it was connected to the pc using the usb cable that came with the phone and made sure debugging was still on. It shut off, so I then turned the phone back on. When it is rebooting, as it gets to the SAMSUNG title I hear the connection to my computer being made. Also it gives me the option to open the files on the pc. So far so good. Now when it passes the Verizon Wireless title and it proceeds to run my background and starts scanning the media, it immediately closes the option to view files and I hear the disconnection being made on the computer. The debugging mode is still on and I did not touch anything during this process. Maybe there is something on my phone preventing it from connecting. Could it have anything to do with LauncherPro as my default? Or maybe just a simple setting such as mass storage/media player. (It is set to mass storage) Thank you for your patience.