Ok guys, I tried searching but couldn't find an answer.
I'm running Windows 7 x64. I previously have a non-rooted, 1.5 Droid Eris. I also had HTC Sync installed and working properly, and was able to sync my contacts and calender back and fourth.
I followed the guide HERE, with two exceptions;
1.) I already had a working USB driver for my phone, so even when I downloaded the Android SDK and the USB v3 drivers, there was no need to install them to gain root and upgrade to 2.1 - as proven by my currently upgraded Eris.
2.) In order to install the Recovery, I had to do the following from Command (while the phone was connected via USB w/ USB Debugging enabled:
With phone powered on
Code:
adb shell reboot bootloader
Once the phone gets into hboot and says "recovery usb" type
Code:
fastboot flash recovery recovery.img
with recovery.img in the current folder you are in, and fastboot in your path.
Click to expand...
Click to collapse
That said, I've got my Eris rooted and upgraded to 2.1 (I know, I already said this.. just refreshing you..), but I can't connect to HTC Sync anymore.
In device manager, my phone is recognized as "My HTC" under "Android Devices", as it always has. It's the same with or without USB Debugging enabled.
Am I missing something, or is this simply not possible at this time?
EDIT: I figured it out. Since nobody replied, I'll assume you guys don't need the fix.. if anyone does, feel free to PM me
Ok...I've searched all over and can't seem to find the answer.
Question - "How can I get my phone back to factory (out of the box) settings on a Mac Computer or Parallels?"
Current Settings - I am rooted, I have ROM Manager, Super User Permissions, Root Explorer and a Custom Rom (Fusion).
Attempts - I have downloaded ODIN, install all the necessary drivers, have booted up Parallels and have have been able to mount my phone and view files on Parallels. I have opened up ODIN and it has recognized my phone when it is ON.
Dilemma - I have gone through the steps given to us by the nice ODIN video tutorial. However, once I access download mode on my phone my Parallels gives me a pop up that says it is unable to connect the device to the USB. I have tried this over and over about 30x, still I cannot get it to recognize the phone while in download mode.
*So, can someone provide me with a solution? Either via MAC or Parallels? I'd like to get my phone back original settings soon, thanks.
I hope this is the right place to post this. I'm new to rooting and flashing but did tons of research and got my vibrant rooted and running great with Nero v.3. Did the same to my roommate's phone with equal success. I tried the Gingerbread experimental rom from Team Whiskey and now I can't get rid of it. I've tried using Odin like the post says but my phone won't go into download mode no matter what I try and Odin won't recognize it, so I can't flash the voodoo kernel back. I've tried every combo of buttons and battery, sim, sd card removals, etc. I got sdk android set up and followed all the posts but when I try adb reboot recovery my computer says adb is not a known command, process, or batch file. I have the environment variables set up in advanced settings for my computer but still nothing. To make it worse my phone had no service detected now and keeps powering itself on and off consistently. Any advice on why adb won't work or another way to get to download mode? Something other than odin?
For one, ADB is not set up correctly if you are getting that error. I had to manually adjust the environment settings on my Win7 pc to get it to run right. It does not write it correctly to Win7's environment settings for some reason.
Second, if you cannot get into DL mode, you could always try this:
http://forum.xda-developers.com/showthread.php?t=889128&highlight=jig
It says for Captivate but should work just fine on the Vibrant. There are other threads on this in the i9000 forums as well.
adb
So can anyone help with the setting required for Win 7 in the environment settings to get ABD to work?
criswell01 said:
So can anyone help with the setting required for Win 7 in the environment settings to get ABD to work?
Click to expand...
Click to collapse
Did you place a copy of the adb.exe and the adbwinapi.dll into your system32 folder? Thats necessary to allow adb to be run from any command line location.
Ginger Clone's of the World Unite! Via the XDA App
Sorry for all the questions but where would I find the system 32 folder?
You need to insatll the nexus s drivers for adb and odin to.see.the phone.
For download mode, turn phone off, unplug the usb. Hold vol up and down and.plug.in.usb. will put you right into dl mode. If it doesnt...then you.need a jig
Sent from my SGH-T959 using XDA App
criswell01 said:
Sorry for all the questions but where would I find the system 32 folder?
Click to expand...
Click to collapse
Your system32 folder is on your windows machine. C:\windows\system32
Ginger Clone's of the World Unite! Via the XDA App
I know nothing about ADB, nothing at all, however I was able to install it with no problem, and it detects my phone.
I followed the step by steps directions posted directly by Google.
edit:
Seems like I installed SDK. Wait are the two the same?
Anyway, I followed the directions at the link below, and seems like I'm running ADB via command prompt.
http://developer.android.com/sdk/index.html
click on "installing the sdk"
edit:
yup, sure enough I have ADB. LOL now i'm confused. SDK and ADB are the same? Anyways, I followed the link above, installed sdk, and I have ADB too. I'm using drivers via samsung kies.
The android sdk installs adb I do believe. I've gotten into the habit of just copying my sdk folder to (random pc's) c drive, if I'll need the functions in there, and/or copying the two files over and going in commando style. Just copying the files over to system32 on most pc's will give you basic adb commands, for more advanced functions sdk is necessary. Probably not the surest way but its been working for me.
Ginger Clone's of the World Unite! Via the XDA App
SamsungVibrant said:
I know nothing about ADB, nothing at all, however I was able to install it with no problem, and it detects my phone.
I followed the step by steps directions posted directly by Google.
edit:
Seems like I installed SDK. Wait are the two the same?
Anyway, I followed the directions at the link below, and seems like I'm running ADB via command prompt.
http://developer.android.com/sdk/index.html
click on "installing the sdk"
edit:
yup, sure enough I have ADB. LOL now i'm confused. SDK and ADB are the same? Anyways, I followed the link above, installed sdk, and I have ADB too. I'm using drivers via samsung kies.
Click to expand...
Click to collapse
Again, you need to install the Nexus S drivers.
http://www.fileserve.com/file/5bgRBX5
Download and extract.
When you plug your phone in, go to Device Manager, you'll see that Nexus S was unable to install. Right click and choose update driver.
navigate to where you extracted the files to, and install.
It will now install the ADB driver, which also allows ODIN to see the phone in Download mode.
First thanks to everyone for the help and suggestions. I've got adb working now, it recognizes my phone and the adb commands work. I updated the nexus drivers in the device manager. Now when I connect the phone and use the adb reboot recovery command it shuts down, goes to a charging screen for a second, then boots back up to gingerbread. I tried using the adbrebootdownload in the adb bat file and once again the phone shut down and booted back up to gingerbread. The phone is unusable but doesn't seemed to be "bricked" (based on my understanding of bricked). Very frustrating. I had Nero v.3 with voodoo working amazing, Im so pissed at myself. Any other thoughts?
to get to download you need to do the 3 button combo.
power down, unplug, hold vol up and down, and plug in usb.
Thanks but the three button method wont work. Am I wrong in assuming that using ADB you can get into download mode without using the button method? The op said that all I need to do is use odin to flash the previous kernel to get the phone back to nero. I'm stuck! Has anyone had problems using adb recovery?
krylon360 said:
Again, you need to install the Nexus S drivers.
http://www.fileserve.com/file/5bgRBX5
Download and extract.
When you plug your phone in, go to Device Manager, you'll see that Nexus S was unable to install. Right click and choose update driver.
navigate to where you extracted the files to, and install.
It will now install the ADB driver, which also allows ODIN to see the phone in Download mode.
Click to expand...
Click to collapse
No, I got ADB working by installing SDK, using the link I provided, and using the normal drivers from kies. However, I did this a couple months ago, maybe the driver requirments have changed now, I'm not sure, but it works for me.
criswell01 said:
Thanks but the three button method wont work. Am I wrong in assuming that using ADB you can get into download mode without using the button method? The op said that all I need to do is use odin to flash the previous kernel to get the phone back to nero. I'm stuck! Has anyone had problems using adb recovery?
Click to expand...
Click to collapse
The adb command for download mode is adb reboot download, be sure usb debugging is switched on on your phone. If that doesn't trigger download mode, I think the jig is your only hope.
Ginger Clone's of the World Unite! Via the XDA App
criswell01 said:
Thanks but the three button method wont work. Am I wrong in assuming that using ADB you can get into download mode without using the button method? The op said that all I need to do is use odin to flash the previous kernel to get the phone back to nero. I'm stuck! Has anyone had problems using adb recovery?
Click to expand...
Click to collapse
Try this method:
1) remove batt, sim, and sd
2) plug in usb cable (and attached to computer with odin open)
3) hold down both vol keys
4) pop in battery
This always works for me.
This is a request for help with a Bell Samsung Vibrant, model GT-I9000M.
I bought it unlocked, rooted it with the update.zip file from the Noob Guide on XDA-Developers by s15274n, and all was well. The phone was running Eclair 2.1-update 1, with UGJH2 and a 2.6.29 kernel. SIM card from AT&T.
Then I made the mistake of trying to see if Kies worked, and let it update the phone to kernel 2.6.32.9, Froyo 2.2, UGJK4.
In short, can't root via 'update.zip' because Android recovery 3rd Edition prevents all the files I have tried from installing. And the 2.2 'update' killed off any USB connectivity (and GPS) so I cannot use Odin or adb.
I have tried many different update.zip files; none will run because they do not have the right signature ('signature verification failed'). The phone is invisible via usb on Ubuntu, on WinVista, or on WinXP; Odin cannot find it; adb from the Android SDK cannot find it. The Galaxy usb drivers will install on my WinVista laptop, but the device fails to start with Error 10.
I have been careful always to get the usb set to mass storage and the usb debugging turned on.
The recovery is the Android third edition recovery, and unless I find an update.zip that will pass inspection, I doubt I can root the phone. I can turn it on (three-button) and get into recovery mode, or into download mode, but neither will solve the problem as it stands. Recovery mode rejects the available update.zip files, and neither of my computers will connect via usb.
Any advice greatly welcomed!
drddx66
My understanding is with the 3E recovery you are not going to be able to find any signed packages that will work as those keys are only known to Samsung.
Have you tried switching usb ports? I don't have any other ideas if you can't get your computer to recognize the phone in usb debugging mode.
drddx66 said:
This is a request for help with a Bell Samsung Vibrant, model GT-I9000M.
I bought it unlocked, rooted it with the update.zip file from the Noob Guide on XDA-Developers by s15274n, and all was well. The phone was running Eclair 2.1-update 1, with UGJH2 and a 2.6.29 kernel. SIM card from AT&T.
Then I made the mistake of trying to see if Kies worked, and let it update the phone to kernel 2.6.32.9, Froyo 2.2, UGJK4.
In short, can't root via 'update.zip' because Android recovery 3rd Edition prevents all the files I have tried from installing. And the 2.2 'update' killed off any USB connectivity (and GPS) so I cannot use Odin or adb.
I have tried many different update.zip files; none will run because they do not have the right signature ('signature verification failed'). The phone is invisible via usb on Ubuntu, on WinVista, or on WinXP; Odin cannot find it; adb from the Android SDK cannot find it. The Galaxy usb drivers will install on my WinVista laptop, but the device fails to start with Error 10.
I have been careful always to get the usb set to mass storage and the usb debugging turned on.
The recovery is the Android third edition recovery, and unless I find an update.zip that will pass inspection, I doubt I can root the phone. I can turn it on (three-button) and get into recovery mode, or into download mode, but neither will solve the problem as it stands. Recovery mode rejects the available update.zip files, and neither of my computers will connect via usb.
Any advice greatly welcomed!
drddx66
Click to expand...
Click to collapse
First you can root the phone using SuperOneClickRoot from here http://forum.xda-developers.com/showthread.php?t=803682
Then you have to find a modded 3e recovery file similar to the one here http://forum.xda-developers.com/showthread.php?t=833423 You might even be able to use that one but don't blame me if you screw up your phone trying it.
At this point all you have to do is copy the "recovery" file to the /system/bin folder (I use root explorer) and you're good to go. Update.zip will work then. Make sure you backup your original recovery file.
MoWeb said:
First you can root the phone using SuperOneClickRoot from here http://forum.xda-developers.com/showthread.php?t=803682
Then you have to find a modded 3e recovery file similar to the one here http://forum.xda-developers.com/showthread.php?t=833423 You might even be able to use that one but don't blame me if you screw up your phone trying it.
At this point all you have to do is copy the "recovery" file to the /system/bin folder (I use root explorer) and you're good to go. Update.zip will work then. Make sure you backup your original recovery file.
Click to expand...
Click to collapse
Thanks for the reply.
I found the modified 3e recovery.
Problem is I cannot get any computer to reconize the phone via USB, so SuperOneClickRoot has no way to root the phone.
It looks like it will be a backup phone until Samsung lets us make our own 'update.zip' files.
Hello,
I'm trying to connect my Samsung GS3 to my computer to use with the Android SDK Manager and the ADB console, but when I connect it to my computer it recognizes it as a Camera and ADB doesn't recognize it either, how do I fix this?
I'm locked out of my phone and trying to unlock it using methods from here: http://forum.xda-developers.com/showthread.php?t=2620456. So I have no interaction with my phone beyond the locksreen to change from PTP to MTP as I've seen people with similair problems suggest. Is their a workaround?
1337Dev said:
Hello,
I'm trying to connect my Samsung GS3 to my computer to use with the Android SDK Manager and the ADB console, but when I connect it to my computer it recognizes it as a Camera and ADB doesn't recognize it either, how do I fix this?
I'm locked out of my phone and trying to unlock it using methods from here: http://forum.xda-developers.com/showthread.php?t=2620456. So I have no interaction with my phone beyond the locksreen to change from PTP to MTP as I've seen people with similair problems suggest. Is their a workaround?
Click to expand...
Click to collapse
install kies if you have it installed already then uninstall it then install again
1337Dev said:
Hello,
I'm trying to connect my Samsung GS3 to my computer to use with the Android SDK Manager and the ADB console, but when I connect it to my computer it recognizes it as a Camera and ADB doesn't recognize it either, how do I fix this?
I'm locked out of my phone and trying to unlock it using methods from here: http://forum.xda-developers.com/showthread.php?t=2620456. So I have no interaction with my phone beyond the locksreen to change from PTP to MTP as I've seen people with similair problems suggest. Is their a workaround?
Click to expand...
Click to collapse
Since you're already looking in the right place, consider installing a custom recovery (such as philz) with odin and then flash the zip.
Thanks for the help. I was finally able to get my computer to recognize the GS3 (Installed Samsung USB Drivers from their website instead of Kies). But now after it recognizes that I have new hardware installed, when I try to use the Wizard to automatically install the drivers I get the error: "The required section was not found in the inf", did some searching and realized that this is due to not having the wpdmtp.inf file on your computer. I've checked and it is indeed missing, does anyone now of a way to install this file?
I'm still locked out of my phone. And I don't have an SD Card to install recovery and flash the zip as dxppxd suggested.
1337Dev said:
Thanks for the help. I was finally able to get my computer to recognize the GS3 (Installed Samsung USB Drivers from their website instead of Kies). But now after it recognizes that I have new hardware installed, when I try to use the Wizard to automatically install the drivers I get the error: "The required section was not found in the inf", did some searching and realized that this is due to not having the wpdmtp.inf file on your computer. I've checked and it is indeed missing, does anyone now of a way to install this file?
I'm still locked out of my phone. And I don't have an SD Card to install recovery and flash the zip as dxppxd suggested.
Click to expand...
Click to collapse
Take another shot by booting into a custom recovery, most give you adb access while in recovery.
If the phone is locked with usb debugging disabled you won't be able to get adb access.