moordown66
Newbie
As some of you may have seen from a previous post, I'm having a few problems unlocking the bootloader on my Nexus S. Things have moved on slightly now, so maybe someone could give me a point in the right direction.
USB debug is on. Phone is in fastboot mode.
I have downloaded SDK, downloaded everything it offered me and have extraced the drivers and they're now fully recognised via device manager as Android ADB Interface. That's good.
Next thing I do is open a command prompt and point everything at where my tools folder is (that's c:/androidsdk/tools in my case). That's good, it can see that.
I also have the unzipped contents of the fastboot.zip into the tools folder which contains the likes of adbwinapi.dll. Is that the right place for it?
On the cmd I then type c:\androidsdk\tools>fastboot oem unlock
That's when things grind to a halt. I get the message <waiting for device> which just hangs forever and ple of occasions when I've tried (and failed) to unlock it, on a the very bottom of the screen I get the message 'fastboot status FAILInvalid command'....but I don't always get that.
The other info on the screen is as follows:
Fastboot mode (it's in red)
Product name - herring
HW version - rev11
Bootloader version - I9020XXJK1
Bootloader build - Nov 4 2010
Baseband version - I9020XXJK8
Serial number - (it's on there - won't put it on here)
Lock state - locked
So....I've obviously done something wrong. Am I missing something that should be in that tools folder?
Does this give anyone any clues what it might be, and and any chance of explaining to me how to put it right so I can get that bootloader unlocked and the thing rooted?
Gettin this done is now close to taking over my life
USB debug is on. Phone is in fastboot mode.
I have downloaded SDK, downloaded everything it offered me and have extraced the drivers and they're now fully recognised via device manager as Android ADB Interface. That's good.
Next thing I do is open a command prompt and point everything at where my tools folder is (that's c:/androidsdk/tools in my case). That's good, it can see that.
I also have the unzipped contents of the fastboot.zip into the tools folder which contains the likes of adbwinapi.dll. Is that the right place for it?
On the cmd I then type c:\androidsdk\tools>fastboot oem unlock
That's when things grind to a halt. I get the message <waiting for device> which just hangs forever and ple of occasions when I've tried (and failed) to unlock it, on a the very bottom of the screen I get the message 'fastboot status FAILInvalid command'....but I don't always get that.
The other info on the screen is as follows:
Fastboot mode (it's in red)
Product name - herring
HW version - rev11
Bootloader version - I9020XXJK1
Bootloader build - Nov 4 2010
Baseband version - I9020XXJK8
Serial number - (it's on there - won't put it on here)
Lock state - locked
So....I've obviously done something wrong. Am I missing something that should be in that tools folder?
Does this give anyone any clues what it might be, and and any chance of explaining to me how to put it right so I can get that bootloader unlocked and the thing rooted?
Gettin this done is now close to taking over my life