Trying to restore my phone back to 100% stock but computer doesnt see my phone in fastboot/bootloader but it does recognize it in normal mode, tried different cables, please help.
*edit*
windows installs the wrong driver, had to edit a driver's .inf file to get it to recognize....used the info on another page, listed below.
Source
Related
I finally got my unlock code from tmobile today. The code worked fine but now im still unable to register the phone, stuck at the sign up or create screen. For the life of me i cannot get the drivers to install, windows keeps telling me it has the latest installed. The first time i plugged the phone in, i did not even know about USB debugging so i cant even use that at this point. How do i get windows to quit saying it has the latest drivers installed and use my own? ive tried just about everything. I even tried using a XP laptop and it automatically used its own drivers. I need to activate the wifi to continue registering this phone but without these drivers im stuck. Please advise!
anyone? ive tried this <enter>setprop persist.service.adb.enable 1<enter> and it does nothing on the phone or pc. The pc refuses to accept the drivers. It keeps on installing its own drivers.
me too...where did u get that from....wat is that supposed to do?
Just manually delete the drivers then install the drivers you want. This happened to me 2.
i went to device manager, choose the device. Uninstall the drivers, restarted the pc and plug the G1 in and still no go. Vista did the same thing, installed its own drivers. Did it on my dad's XP laptop as well and did the same thing. I can't turn on USB debugging if i can't get pass the Registration screen!
Choose UPDATE DRIVER, then specifically point it to the driver. Not just to the folder expanded folder, point it directly to the appropriate driver itself. Pick the right architecture folder (such as AMD64). I cannot emphasize enough not to let Windows search for an appropriate driver. You need to point it to the folder that contains the right .inf file.
i downloaded the usb drivers from off this site and i did what u said and it still gives me the same junk! damnit!!
you say you are stuck at the registration screen - do you not have a skip registration button, allowing you to get into the main OS. or, if you press menu can you not enter APN settings? that will allow you to register successfully
Ok then,
What rom are you using?
What version?
What radio?
What SPL?
What SDK?
You know, the basics.
I am trying to put my captivate back to at&t stock 2.1 but odin does not recognize my phone, when i put it in download mode with debugging on, nothing happens. What should I do?
Does one of the boxes turn yellow? If not, it doesn't see it. If it turns yellow and says com: (some number), hit start.
Also make sure you have the right drivers installed.
Sent from a place my wife doesn't know about (yet)
no it does not go yellow!
Try a diff usb port maybe a motherboard type. Try restarting both pc and phone.uninstall drivers reinstall. Let windows install for you?...also the way I do it...have odin open and ready...have usb connected to pc...phone off… vol up vol down ... then plug into usb cord.
You should see little android guy digging, inside a bright yellow triangle.
I usually put my battery back in phone as soon as this pops up. You won't have a chance later, as phone should rboot automatically as part of odin process.
Sent from a place my wife doesn't know about (yet)
I tried all that. I tried having odin open already as administrator, then put phone into download mode while plugged in and still nothing happens
When was the last restore point you made on your computer? If it was recent uninstall drivers, restore from an earlier point, rienstall drivers, and reboot. I had this same issue and this is the only thing that got it working.
unfortunately my computer recently crashed so i no longer have my restore. Is there any way I can apply yours or someone elses?
I'm pretty sure restore points are system specific. Do you have access to another pc? Try the whole process fresh. Sorry man that's about all I got.
What happens when yoyour not in ODIN and hook your phone to your computer? Does it recoginze it, can you transfer files? What does Device manager show it as?
So I tried to root my phone, it worked, and I wanted to oc it. I used ROM Manager, and bricked my phone, since I installed a program (dont remember what its called) that turned my phone into EXT4, when it needs to run on EXT3 or something. So now its stuck at the LG/ LG with loading bar screen and cannot turn on. I'm trying the flash it with nvflash, but it wont work. I got my phone into APX Device mode once, but I failed and had to try again. But now, my computer won;t recognize my phone and I think I'm doing something wrong, because it wont show my phone as a APX Device. I'm obviously new to this so help would be appreciated.
GhostRai said:
So I tried to root my phone, it worked, and I wanted to oc it. I used ROM Manager, and bricked my phone, since I installed a program (dont remember what its called) that turned my phone into EXT4, when it needs to run on EXT3 or something. So now its stuck at the LG/ LG with loading bar screen and cannot turn on. I'm trying the flash it with nvflash, but it wont work. I got my phone into APX Device mode once, but I failed and had to try again. But now, my computer won;t recognize my phone and I think I'm doing something wrong, because it wont show my phone as a APX Device. I'm obviously new to this so help would be appreciated.
Click to expand...
Click to collapse
Some people have reported that they have to try repeatedly before it will start in APX-mode. So try again and again before giving up, make sure battery is out and that you firmly press both volume-buttons while plugging it in.
If it absolutely, positively cannot enter APX-mode, then your last hope is Smartflash-mode. Does it start in Smartflash mode if you hold volume-down while plugging it in?
Oh, and make sure you're connected directly to a port on the motherboard.
EDIT: You can try deleting the APX-device from the PC too, to get it rediscovered and reinstalled. Unzip the attached archive and run the batch file in it. (It sets a parameter which allows the device-manager to display hidden and "ghost"-devices before starting it.) Select "Show Hidden Devices" from the View Menu, find the APX-device(s) ("NVIDIA USB Boot-recovery driver for Mobile devices") and delete it/them. Then try to reconnect in APX-mode again. (Have the driver ready.)
Just got my phone into download mode after using the jig, and i have been able to connect to my pc before i seriously F'd my phone by messing with a setting in cwm. I have downloaded and redownloaded drivers from samsungs website, along with installing Kies and that does not recognize my phone. (also i would like to add i am unable to access the phone since it wont turn on without the jig, without jig it just goes into a boot loop.)
THis is what happens when i plug my phone into the computer:
plug in usb (to computer and phone)
let it do its thing to recognize device...
pop-up stating "unknown device" so i click it.
then right-click the unknown device which opens up another window
from this menu it shows Install driver, Update driver and 3 other options.
when i press install driver and update driver, it tells me that the driver is already installed in "device unknown."
At this point i throw computer at wall after 2 days of trying to figure this out.
so messed around and the problem only happens when it is in download mode. but when it is not in download mode it shows up but no use to me because i am trying to flash it to stock. soo i dont know why the error 43 only shows up when in download mode. any help would be great.
sean.hunt said:
so messed around and the problem only happens when it is in download mode. but when it is not in download mode it shows up but no use to me because i am trying to flash it to stock. soo i dont know why the error 43 only shows up when in download mode. any help would be great.
Click to expand...
Click to collapse
Just follow this to update the drivers http://forum.xda-developers.com/showpost.php?p=27205737&postcount=4571 , same thing as what you have done earlier but this time , when it searches for new drivers, you can do the selection for it.
But first reboot your PC after pulling out power cord ...and try the quick solutions first
Ok sen, so i tried to install the driver manually but i am stuck at the part where i have to install something on my phone to allow it to sync with the computer, since my phone will not even boot up. I am starting to think my dear Capi is going to be a paper weight =(
some assistance please.
I've been at it for about 40 minutes now, trying to sideload 5.1 onto the N6. Go me! Unfortunately I have come to a halt due to my computer not being able to recognize my device in recovery mode. I have the nexus root tool kit installed on my Win7 PC and i have done all the steps as far as driver installation and the toolkit says it is a success. I even open up command prompt when the device is turned on and type "adb devices" and it gives me the device info, I can even use my explorer to see the files I have in storage on the device too. Now if I type the same command while the device in in recovery mode, my computer tells me the device is not found. I have since downloaded the google drivers and tried updating the driver manually through Device Manager and that tells me that the drivers are up to date/best driver is already installed etc. So after goofing with that for a few tries, I uninstalled ALL nexus/google drivers and reinstalled them, twice now, with the same result.
Am I doing something wrong? Why does my computer not want me to update? why does it hate me?
melficeapollo said:
some assistance please.
I've been at it for about 40 minutes now, trying to sideload 5.1 onto the N6. Go me! Unfortunately I have come to a halt due to my computer not being able to recognize my device in recovery mode. I have the nexus root tool kit installed on my Win7 PC and i have done all the steps as far as driver installation and the toolkit says it is a success. I even open up command prompt when the device is turned on and type "adb devices" and it gives me the device info, I can even use my explorer to see the files I have in storage on the device too. Now if I type the same command while the device in in recovery mode, my computer tells me the device is not found. I have since downloaded the google drivers and tried updating the driver manually through Device Manager and that tells me that the drivers are up to date/best driver is already installed etc. So after goofing with that for a few tries, I uninstalled ALL nexus/google drivers and reinstalled them, twice now, with the same result.
Am I doing something wrong? Why does my computer not want me to update? why does it hate me?
Click to expand...
Click to collapse
Here is a channel i subscribe and the guy goes in detail about wugfresh root tool kid, some of the videos are from december. hope it helps.
https://www.youtube.com/channel/UCWhQwvCaC2ZMkCnrC15NfAw
i went the the link and viewed a video about sideloading through the toolkit, never knew i could do that, but i still came across the same problem. my computer wont recognize it.. smh..
melficeapollo said:
i went the the link and viewed a video about sideloading through the toolkit, never knew i could do that, but i still came across the same problem. my computer wont recognize it.. smh..
Click to expand...
Click to collapse
When you get the device not found error, unplug USB and reconnect. May have to repeat once or twice.
Evolution_Freak said:
When you get the device not found error, unplug USB and reconnect. May have to repeat once or twice.
Click to expand...
Click to collapse
Tried that like it was going out of style lol. No luck.
i finally got it figured out!!
i used the toolkit and install;ed Universal Google Drivers (option #3) and my pc was finally able to detect my device in recovery mode.
so if anyone comes across the same problem of not having the "right" drivers or not having your device detected,
1.) Install Universal Google Drivers and reboot your computer
2.) proceed to sideload your update.