Hi, has anyone managed to get ADB working with Jelly Bean? I'm running CM10 and I can't seem to get ADB working. I've downloaded the drivers from the SDK but windows still says it can't find the driver, even when I manually specify where the driver is.
Try 1wayjonny's Universal Naked Drivers over in his thread in the dev section. It's the best. Be sure to remove all traces of the old drivers first.
Do you have a adb debugging enabled on the phone? CM10 has this disabled by default.
Sent from my Galaxy Nexus using Tapatalk 2
And I'll add adb works when you are on booted and when you are on recovery.
Adb does not work on bootloader, fastboot works on bootloader.
atifsh said:
And I'll add adb works when you are on booted and when you are on recovery.
Adb does not work on bootloader, fastboot works on bootloader.
Click to expand...
Click to collapse
I'm aware of that
strumcat said:
Try 1wayjonny's Universal Naked Drivers over in his thread in the dev section. It's the best. Be sure to remove all traces of the old drivers first.
Click to expand...
Click to collapse
Alright, will do. Not at home now. I've never had any ADB drivers installed as this is a clean windows 7 install.
geoffcorey said:
Do you have a adb debugging enabled on the phone? CM10 has this disabled by default.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yep, pretty sure I do.
adbWireless
atifsh said:
And I'll add adb works when you are on booted and when you are on recovery.
Adb does not work on bootloader, fastboot works on bootloader.
Click to expand...
Click to collapse
Can you get a log through fastboot? I need to get a log of boot loop
RichyRicho said:
Can you get a log through fastboot? I need to get a log of boot loop
Click to expand...
Click to collapse
If it's already booting then it's no longer in fastboot
Sent from my Galaxy Nexus
Even today, a friend of mine installed the naked drivers, started adb, device found
I watched him as he did it, guiding him through the commands to push, reboot recovery, the works, and Windows 7 pulled it quite well.
I don't use windows at home, but he did it without troubles at all.
So yeah. ADB has been around for ages, and it will be coming back.
And it's the second proof I see: most of these so called issues with drivers, should be handled on <insert host OS here> forums and not on xda. Most of times, users just don't get it.
Sent from my i9250
Pirateghost said:
If it's already booting then it's no longer in fastboot
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
True
Well after some research last night, and some wasted hours, i now know that ADB does not work in boot Not at all.
So how would I get a log from boot? How does everyone else do it?
RichyRicho said:
True
Well after some research last night, and some wasted hours, i now know that ADB does not work in boot Not at all.
So how would I get a log from boot? How does everyone else do it?
Click to expand...
Click to collapse
do you have android debugging turned on? and which drivers are you using? try using the universal naked drivers that re posted in the dev section
k786 said:
do you have android debugging turned on? and which drivers are you using? try using the universal naked drivers that re posted in the dev section
Click to expand...
Click to collapse
Sorry I have an Xperia S...didnt realise which forum i was in...i dont think the S has naked drivers and the 64 bit ones here dont even work
Related
ok have a gnex had it rooted rommed etc etc Ihave tried every single thing to revert this sum bich to stock for resale and nothing works any help??
PS used both pc and mac, odin, wugfresh, gnex toolkit etc etc
what exactly does not work? any error?
did u tried fasboot to restore the original google stock images?
for an example i just tried the toolkit again and wugfresh it sees my phone says all drivers are installed then i start everything it gets to bootloader mode and then just hangs there saying waiting for device?
AndreaCristiano said:
for an example i just tried the toolkit again and wugfresh it sees my phone says all drivers are installed then i start everything it gets to bootloader mode and then just hangs there saying waiting for device?
Click to expand...
Click to collapse
Try uninstalling the drivers and re install them. Are u in debug bode also?
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
Try uninstalling the drivers and re install them. Are u in debug bode also?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yea in debug did the uninstall reinstall of drivers
Did you restart the pc after installing the drivers?
Which drivers did you install and what OS is your pc running?
If you open the device manager on your pc and connect the phone in fastboot mode what exactly does it say in the Android tab (name of driver installed)?
Mark.
AndreaCristiano said:
Yea in debug did the uninstall reinstall of drivers
Click to expand...
Click to collapse
You have a driver issue.
Uninstall all GN device drivers.
Get the drivers from here.
Follow these steps to install the drivers.
Follow this to get back to stock.
efrant said:
You have a driver issue.
Uninstall all GN device drivers.
Get the drivers from here.
Follow these steps to install the drivers.
Follow this to get back to stock.
Click to expand...
Click to collapse
I will def give this a shot thanks
Ok. I have installed the Wugfresh toolkit. And I have installed the drivers correct I think. So I click on unlock in the tool kit. It tells me to plug my phone in. So I do it. I see my device listed on top of the first screen. Then click YES I see mg device. But when it boot my phone into bootloader and then ask me do i see my device. I don't see it. Everytime it boots into bootloader it doesn't read mg device. So what am I doin wrong. Thanks abunch. I'm really ready to get Thomas phone unclocked and rooted.
Sent from my Galaxy Nexus using XDA
snapper915 said:
Ok. I have installed the Wugfresh toolkit. And I have installed the drivers correct I think. So I click on unlock in the tool kit. It tells me to plug my phone in. So I do it. I see my device listed on top of the first screen. Then click YES I see mg device. But when it boot my phone into bootloader and then ask me do i see my device. I don't see it. Everytime it boots into bootloader it doesn't read mg device. So what am I doin wrong. Thanks abunch. I'm really ready to get Thomas phone unclocked and rooted.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Did you read the directions?
but sounds like you don't have sdk set up right.....but I don't use tool kits....easy to do yourself without tool kit
Setup sdk
Fastboot oem unlock
Fastboot flash recovery
Flash super user from recovery
Sent from my Galaxy Nexus using Tapatalk 2
Epix4G said:
Did you read the directions?
but sounds like you don't have sdk set up right.....but I don't use tool kits....easy to do yourself without tool kit
Setup sdk
Fastboot oem unlock
Fastboot flash recovery
Flash super user from recovery
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
How do i set up sdk. Lol. I thought I had it.
Sent from my Galaxy Nexus using XDA
snapper915 said:
Ok. I have installed the Wugfresh toolkit. And I have installed the drivers correct I think. So I click on unlock in the tool kit. It tells me to plug my phone in. So I do it. I see my device listed on top of the first screen. Then click YES I see mg device. But when it boot my phone into bootloader and then ask me do i see my device. I don't see it. Everytime it boots into bootloader it doesn't read mg device. So what am I doin wrong. Thanks abunch. I'm really ready to get Thomas phone unclocked and rooted.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
You did not setup the drivers correctly. Once the phone boots into the bootloader there is an additional driver that needs to be installed. I forget the exact one but it is included in the toolkit. You probably have some unknown device in your device manager that you need to install the included drivers for in the WugFresh toolkit.
I had the same issue when I first started.
HeCareth said:
You did not setup the drivers correctly. Once the phone boots into the bootloader there is an additional driver that needs to be installed. I forget the exact one but it is included in the toolkit. You probably have some unknown device in your device manager that you need to install the included drivers for in the WugFresh toolkit.
I had the same issue when I first started.
Click to expand...
Click to collapse
Oh ok. Let me look there. Hopefully I can figure this mess out. Lol
Sent from my Galaxy Nexus using XDA
Download PDAnet and install it. This will solve the driver issue. Your issue is that your computer is not recognizing the phone as an ADB interface.
I was having the same problem and corrected it by plugging my phone into the USB port on the back of my PC rather than the one on the front. You can also contact WugFresh for assistance if you still can't figure it out. I had to follow the instructions on manually installing the drivers to my PC.
I am getting a replacement nexus and I am on 4.1 ROM (Verizon gnex) and need to go back to unrooted and all. How do I do it. Plz someone shoot me the link I have 2 more days too send it in thank u
Sent from my Galaxy Nexus using xda premium
frankiedizzle87 said:
I am getting a replacement nexus and I am on 4.1 ROM (Verizon gnex) and need to go back to unrooted and all. How do I do it. Plz someone shoot me the link I have 2 more days too send it in thank u
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Code:
fastboot oem lock
AshtonTS said:
Code:
fastboot oem lock
Click to expand...
Click to collapse
i have a new computer i have to start from scratch as far as adb and all. And i am so lost right now. when i finished re downloading ADB and did cmd and check ADB devices my nexus didnt show up
frankiedizzle87 said:
i have a new computer i have to start from scratch as far as adb and all. And i am so lost right now. when i finished re downloading ADB and did cmd and check ADB devices my nexus didnt show up
Click to expand...
Click to collapse
You gotta install adb driver for Nexus. For my computer, when I enabled usb debugging, it downloaded the driver for me (odd enough) but if your computer doesn't do that, you can Google around to get the exe file for you to install. Just make sure the Nexus has usb debugging on, or it doesn't let you install the driver (from my experience)
Sent from my Galaxy Nexus using xda app-developers app
frankiedizzle87 said:
i have a new computer i have to start from scratch as far as adb and all. And i am so lost right now. when i finished re downloading ADB and did cmd and check ADB devices my nexus didnt show up
Click to expand...
Click to collapse
Go to the development section and get the toolkit. Install all the required drivers. Lock her back up
Sent from my SGH-T999 using xda premium
uoY_redruM said:
Go to the development section and get the toolkit. Install all the required drivers. Lock her back up
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
ok i just went back to cm9 in a panic thinking no jelly bean drivers or something i dunno why i thought that. I will go into dev section and look for some drivers. The site that it gave says KIES is having issues so i cant even download kies. Can i still get drivers with out it? and when i did uSB debugging i still could not load drivers it said failed.
frankiedizzle87 said:
ok i just went back to cm9 in a panic thinking no jelly bean drivers or something i dunno why i thought that. I will go into dev section and look for some drivers. The site that it gave says KIES is having issues so i cant even download kies. Can i still get drivers with out it? and when i did uSB debugging i still could not load drivers it said failed.
Click to expand...
Click to collapse
It doesn't matter what you're currently on. You will completely nuke your phone when you fastboot the images onto your device anyway.
ok my computer currently recognizes my phone now and i know how to re lock my bootloader what rom should i put it on so they dont know i was rooted before relocking the bootloader. I thought locking it would set it back to default but i was wrong i just had cm9 with a locked bootloader lol i think they would know from that but seriously. What rom should i put to just make my phone 100000% stock
frankiedizzle87 said:
ok my computer currently recognizes my phone now and i know how to re lock my bootloader what rom should i put it on so they dont know i was rooted before relocking the bootloader. I thought locking it would set it back to default but i was wrong i just had cm9 with a locked bootloader lol i think they would know from that but seriously. What rom should i put to just make my phone 100000% stock
Click to expand...
Click to collapse
The stock ROM, there's a full factory restore through Odin. Its in one of the stickies.
You can do everything using gnex toolkit v7.0.
Sent from my Galaxy Nexus using xda premium
Download the factory image from Google and flash to stock
https://developers.google.com/android/nexus/images
Sent from my Galaxy Nexus using xda app-developers app
frankiedizzle87 said:
ok my computer currently recognizes my phone now and i know how to re lock my bootloader what rom should i put it on so they dont know i was rooted before relocking the bootloader. I thought locking it would set it back to default but i was wrong i just had cm9 with a locked bootloader lol i think they would know from that but seriously. What rom should i put to just make my phone 100000% stock
Click to expand...
Click to collapse
So you got everything stock except the ROM? So you got stock recovery and everything? If you do, first of all, download the stock rom from google site (there should be few versions, that, you gotta find it out) then you need to download clockwork mod recovery (assuming that you got fastboot and adb) now just boot into cwm on your phone and flash the stock rom. By doing this, you're not over writing the recovery but you can still use the cwm
Also you gotta unlock first lol
Sent from my Galaxy Nexus using xda app-developers app
I used a video to unroot my phone and now it will not come out of boot mode, I turn it on it acts like it is booting up but never does just stays in the same position. and when I try to go into fastboot mode I get an error, it shows an android laying down and a red triangle over him how do I fix this? PLEASE HELP
follow this exactly as its written: http://forum.xda-developers.com/showthread.php?t=1626895
I will try this, but I am not sure that the computer is reading the phone, I can get odin to work but it is not helping I tried putting stock files using odin but same thing. when i tried cmd and fastboot devices it brings up nothing
when I plug my phone in my computer does not recognize it, now what do I do?
Zepius said:
follow this exactly as its written: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
did everthing step by step, I am able to see the device in my device manager, but when I get to the part where I put it in bootloader and and type fastboot devices it does not recognize it. any suggestions?
pamelak38 said:
did everthing step by step, I am able to see the device in my device manager, but when I get to the part where I put it in bootloader and and type fastboot devices it does not recognize it. any suggestions?
Click to expand...
Click to collapse
You need to install the fastboot driver.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
You need to install the fastboot driver.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I cannot turn my phone on to put it on usb debugging, could this be my problem? and how do I install fastboot driver I thought I had it with sdk tools
pamelak38 said:
I cannot turn my phone on to put it on usb debugging, could this be my problem? and how do I install fastboot driver I thought I had it with sdk tools
Click to expand...
Click to collapse
When you are booted into bootloader but a "fastboot devices" does not list your device, it's almost always caused by having installed either no driver at all or the wrong one. Use the naked driver, follow the link in my signature to find it.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
When you are booted into bootloader but a "fastboot devices" does not list your device, it's almost always caused by having installed either no driver at all or the wrong one. Use the naked driver, follow the link in my signature to find it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Ok I got it up and running! My only concern is I did every step but the radio step failed every time, is this a problem?????
THANK YOU SO MUCH, I HAVE LEARNED A LOT FROM THIS!!
pamelak38 said:
Ok I got it up and running! My only concern is I did every step but the radio step failed every time, is this a problem?????
THANK YOU SO MUCH, I HAVE LEARNED A LOT FROM THIS!!
Click to expand...
Click to collapse
Lte radio? Anyway if your connection is ok I'd say it's not an issue.
Good you figured it out.
Sent from my Galaxy Nexus using Tapatalk 2
still cant get into recovery mode
can anyone help, I got the phone back to where I can get into it, but if I try to go into recovery mode I still get the dead android with the red triangle and can anyone tell me where to find a lte radio
pamelak38 said:
can anyone help, I got the phone back to where I can get into it, but if I try to go into recovery mode I still get the dead android with the red triangle and can anyone tell me where to find a lte radio
Click to expand...
Click to collapse
What you see is the stock recovery. Android will flash it back automatically even after you've flashed a custom recovery. To prevent this, you must either rename/delete /etc/install-recovery.sh OR rename/delete /system/recovery-from-boot.p.
LTE radios are in the factory images. Read this: http://forum.xda-developers.com/showthread.php?t=1626895
Petrovski80 said:
What you see is the stock recovery. Android will flash it back automatically even after you've flashed a custom recovery. To prevent this, you must either rename/delete /etc/install-recovery.sh OR rename/delete /system/recovery-from-boot.p.
LTE radios are in the factory images. Read this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Ok, I have never had to rename/delete,ect before, can you help walk me thru that, I know I am asking a lot but I would sure appreciate it
pamelak38 said:
Ok, I have never had to rename/delete,ect before, can you help walk me thru that, I know I am asking a lot but I would sure appreciate it
Click to expand...
Click to collapse
Do you have root? In that case it's a matter of launching your file manager.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
Do you have root? In that case it's a matter of launching your file manager.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes I have root, now what do I need to do?
pamelak38 said:
Yes I have root, now what do I need to do?
Click to expand...
Click to collapse
Navigate to the folder /etc with a file manager. Remount with RW rights (root explorer has a convenient button for this) and rename the file install-recovery.sh to install-recovery.sh.bak.
Then reflash a custom recovery. This time it will stick.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
Navigate to the folder /etc with a file manager. Remount with RW rights (root explorer has a convenient button for this) and rename the file install-recovery.sh to install-recovery.sh.bak.
Then reflash a custom recovery. This time it will stick.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I got it back to stock and locked, THANK YOU so much you are awesome!!!!
I have installed and reinstalled the usb drivers like 4 times with reboots in between. I was about to root, but after root i cant do anything. The main thing i want to do is flash a custom rom. I have the gnex tool kit, it says waiting for device (option 6), and the most recent drivers are from that toolkit. I tried command pront, Fastboot reboot-bootloader, it says waiting for device. I tried adb flash recovery recovery.img it says waiting for device. I tried 2 different cables and all my usb ports on my computer.
Im at a loss. I can still transfer files from my computer to my device. My computer detects it just none of these commands... god i wish i had an sd card slot... lol
Edit:
I also tried putting it inot fastboot mode by pressing the power and wolume up / down keys. It goes to the screen and says start. All commands still say waiting for device.
I feel like this is a driver issue but idk why.... i have tried all drivers...........
i have a samsung galaxy nexus l515 verizon cdma.
Thanks!
Do u have USB debugging on?
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
Do u have USB debugging on?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yeah usb debugging is enabled. :crying:
Unplug your phone from computer install the drivers from Samsung's website. (Google USB drivers for galaxy nexus i515) reboot computer and try again. Maybe u should install android SDK with adb and do it manually instead of using a toolkit. Those cause problems.
Sent from my Galaxy Nexus using xda premium
Its a driver problem, for sure. OP, stop being lazy please, learn from this here, and after that, like Zepius says, put your big boys pants on and do it like this
Sent from my Nexus 10 using xda app-developers app
Ohhh the universal naked drivers. I never even thought of that. Actually i did. I have installed them same issue. I have fallowed the instructions in your first link prior to starting this thread. I appreciate the help but your attempt to call me lazy is wrong. Still unable to flash cwm or anything from the computer however i was able to flash cwrm touch today after buying the rom manager premium. Still doesnt explain why i cannot do it from my computer. Mind you i attempted this on my laptop (slackerware) and i did still have issues.
I think it is somthing with the port on my phone ror maybe somthing else. Regardless, im not lazy for i do know where google is and how to abuse all of her abilities. I know where the forum search button is also.
Drivers i have tried.
Naked nexus drivers
Windows native drivers
Slackerware mobile drivers
Samsung drivers
And what ever the gnex tool kit installs. No matter what i get waiting for device...
Sent from my GT-N8013 using xda app-developers app
5imp7y said:
I have installed and reinstalled the usb drivers like 4 times with reboots in between. I was about to root, but after root i cant do anything. The main thing i want to do is flash a custom rom. I have the gnex tool kit, it says waiting for device (option 6), and the most recent drivers are from that toolkit. I tried command pront, Fastboot reboot-bootloader, it says waiting for device. I tried adb flash recovery recovery.img it says waiting for device. I tried 2 different cables and all my usb ports on my computer.
Im at a loss. I can still transfer files from my computer to my device. My computer detects it just none of these commands... god i wish i had an sd card slot... lol
Edit:
I also tried putting it inot fastboot mode by pressing the power and wolume up / down keys. It goes to the screen and says start. All commands still say waiting for device.
I feel like this is a driver issue but idk why.... i have tried all drivers...........
i have a samsung galaxy nexus l515 verizon cdma.
Thanks!
Click to expand...
Click to collapse
Are you confusing adb with fastboot, or was "adb flash recovery recovery.img" a typo? Anyway, forget the toolkit. Get adb/fastboot binaries from the 101 & FAQ, and try:
1) booted into Android: adb devices
This should list your device with a number. If the list is empty, adb cannot interface with your gnex.
2) booted into the bootloader: fastboot devices
This should also list your device with a number. If the list is empty, fastboot cannot interface with your gnex.
Note that the adb and the fastboot interface are different. If you installed drivers and got adb running, this does not automatically make fastboot working. Boot into fastboot, connect and use device manager to scout for unknown devices. Update using naked driver if necessary.
5imp7y said:
im not lazy
And what ever the gnex tool kit installs. No matter what i get waiting for device...
Click to expand...
Click to collapse
you are lazy. you're relying on a toolkit.
please root your phone the manual way, or at least try fastboot alone so we actually know what the problem is.
Thanks yeah that was a typo. I have the adroid bianarys. Adb and fastboot. I was typing. Fastboot reboot bootloader to try and get gnex tools to see the device. No luck.
Sent from my GT-N8013 using XDA Premium HD app
I did root without the tool kit...? I was trying all possabilities to flash cwrm touch before i created a thread. I realize there was a typo in the op. I AM rooted but i had no recovery. Sorry for the confusion.
I rooted manually no problems. Problems arose post root. This can be marked as solved for buying the app fixed my issue. With recovery i can flash roms on the device. No need for a computer anymore. Thanks to those who didnt attack me and make me cry. To those who did well... thanks anyways....
Sent from my GT-N8013 using XDA Premium HD app
5imp7y said:
I did root without the tool kit...? I was trying all possabilities to flash cwrm touch before i created a thread. I realize there was a typo in the op. I AM rooted but i had no recovery. Sorry for the confusion.
I rooted manually no problems. Problems arose post root. This can be marked as solved for buying the app fixed my issue. With recovery i can flash roms on the device. No need for a computer anymore. Thanks to those who didnt attack me and make me cry. To those who did well... thanks anyways....
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
If you know how to root manually, then surely you must know how to boot or flash a custom recovery like twrp or cwm with fastboot.
Sent from my Nexus
Fastboot flash recovery "your recovery img here". Still said waiting for device....
Edit:
so many typos my bad it is hard to type on my phone or tablet with fat fingers.
Seriously though, to the 2 people taking time out of their day to be jerks, grow up im done with this thread.
Sent from my GT-N8013 using XDA Premium HD app
5imp7y said:
Fastboot flash recover your recovery img here. Still said waiting for device....
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
Again, driver issue. 'fastboot devices' should return your devices serial number. that command is the tell-tell sign that communication between fastboot host (PC/Mac) and client (device) see and recognise each other.
And please try to be flawless on the transcription of the exact commands used, to exclude the possibility of typos.
Sent from my Nexus
bk201doesntexist said:
Again, driver issue. 'fastboot devices' should return your devices serial number. that command is the tell-tell sign that communication between fastboot host and client see each other.
And please try to be flawless on the transcription of the exact commands used, to exclude the possibility of typos.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
BUT! in the gnex tool kit my serial number is displayed...?
5imp7y said:
BUT! in the gnex tool kit my serial number is displayed...?
Click to expand...
Click to collapse
Then it maybe not be a driver problem: you need to update platform-tools through android-sdk, which has fastboot/adb binaries. 4.2.2 requires it.
Sent from my Nexus
Let's try and be as friendly as possible when trying to help someone.
Thanks bk201doesntexist for trying to help.
bk201doesntexist said:
Then it maybe not be a driver problem: you need to update platform-tools through android-sdk, which has fastboot/adb binaries. 4.2.2 requires it.
Sent from my Nexus
Click to expand...
Click to collapse
if not a driver issue, it must be this.
install PDAnet on your device .. follow procedure of installation carefully ( should be installed on both pc and phone ) and when it was installed .when u enter your bootloader your phone will be recognize by your pc and wait for device will gone .
the method tested by me and took me one month two years ago to find .. on my g nexus first try to unlock .
PDAnet isntall drivers and everything you need to use adB commands ... if it helped give me thanks and let me know by pm .
PDA links
http://junefabrics.com/android/downloadold.php
1. Open device manager on your PC.
2. Right click on Android 1.0 with the yellow ! mark on it.
3. Choose update driver.
4. Choose browse my computer.
5. Choose Let me pick from a list.
6. Scroll down and find the Samsung driver with newest date. Should be the driver you downloaded above. (Possibly dated 11/25/2011 ).
7. It will give you a warning about installing the driver, just click yes.
driver: http://www.samsung.com/us/support/owners/product/GT-I9250TSGGEN#