Database Users

need stock system image for Nexus S

My phone doesnot go past google logo.
Need the stock recovery and system image
I am thinking once i get them i should be able to run using FAstboot commands
without even unlocking(as fast boot oem unlock also not working for me) boot loader..somebody please confirm...

I tried fastboot update update.zip with Official 2.3.3 ROM but i get following error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
My phone is not rooted neither the boot loader is unlocked( I have failed to unlock it with Fastboot OEM unlock)

First thing first... connect your phone and type "adb devices". Does your serial nr show up? Turn off your phone and boot into bootloader (hold vol up + power). Type "fastboot devices", does your serial nr show up? If not, adb and/or fastboot isn't recognizing your connection and device. If it does, you SHOULD be able to type "fastboot oem unlock" to unlock your bootloader.
Tip: you can view your bootlooader state on the device display when inside the loader. It says "State: LOCKED" or "State: UNLOCKED" respectively.

[ROM] Samsung stock D720 for Nexus S 4G
All else fails, this should get your phone back to factory.
http://forum.xda-developers.com/showthread.php?t=1072698
http://www.holylivingfuck.com/Crap/SamsungSimpleDL_D720(1.0.002).zip
MIRROR
http://www.fileserve.com/file/JnCgZkm

I have nexus s GSM(tmobile version) , anybody knows similar link like above for it.

jottosson said:
First thing first... connect your phone and type "adb devices". Does your serial nr show up? Turn off your phone and boot into bootloader (hold vol up + power). Type "fastboot devices", does your serial nr show up? If not, adb and/or fastboot isn't recognizing your connection and device. If it does, you SHOULD be able to type "fastboot oem unlock" to unlock your bootloader.
Tip: you can view your bootlooader state on the device display when inside the loader. It says "State: LOCKED" or "State: UNLOCKED" respectively.
Click to expand...
Click to collapse
when i run adb devices it doesnt display any device seems it needs usb debugging enabled which I cant do as mentioned above.
when i run fastboot devices , it does display my phone's serial number but when i run the command fastboot oem unlock my phone displays a confirmation to select "Yes or no" , i chose "yes" and hit the power button but then it doesnt do any thing it just stays there , i tried multiple times waited several mins to hours but no luck yet.
I am running all this on windows 7 64 bit computer .

http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK
justsahid said:
when i run adb devices it doesnt display any device seems it needs usb debugging enabled which I cant do as mentioned above.
when i run fastboot devices , it does display my phone's serial number but when i run the command fastboot oem unlock my phone displays a confirmation to select "Yes or no" , i chose "yes" and hit the power button but then it doesnt do any thing it just stays there , i tried multiple times waited several mins to hours but no luck yet.
I am running all this on windows 7 64 bit computer .
Click to expand...
Click to collapse

cadams14 said:
http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK
Click to expand...
Click to collapse
this doesnt work as it also asks to unlock botloader sing Fastboot oem unlock

i am also stuck in the same situation but i dont have a sprint 4g. is there any other links available?

Another one here. Same situation. Any resolutions yet?

jboxer said:
Another one here. Same situation. Any resolutions yet?
Click to expand...
Click to collapse
Here you go, set your phone to download mode and use ODIN to flash your phone (i9020) back to stock.
http://www.samfirmware.com/WEBPROTECT-i9020.htm

justsahid said:
My phone doesnot go past google logo.
Need the stock recovery and system image
I am thinking once i get them i should be able to run using FAstboot commands
without even unlocking(as fast boot oem unlock also not working for me) boot loader..somebody please confirm...
Click to expand...
Click to collapse
Check out that u hv installed driver properly for fastboot. Bootloader need to b unlocked for getting into Download mode.
Sent from my Nexus S using XDA App

zirra said:
Here you go, set your phone to download mode and use ODIN to flash your phone (i9020) back to stock.
http://www.samfirmware.com/WEBPROTECT-i9020.htm
Click to expand...
Click to collapse
This will work for the t? I was under the impression we didnt have any images for the 9020t version.
Edit: I just signed up for the site and everything, and it says nothing about being for the T version.

Yes that Odin package from Samfirmwares is for the I9020T. However it is not version 2.3.3, but rather 2.3.1 GRH78.

[Q] Permanent problem with Unlocking Bootloader Nexus S

Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!

alpheus said:
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
Click to expand...
Click to collapse
It looks like your device is not recognized in Fastboot mode...
Have you turned on USB Debugging while connecting PC and Allow in Device when Prompt some message ..
Go to fastboot mode and write this command... fastboot devices
If it will give you a message like this
List of devices
1235456785164
Then your devices is successfully recognized...:good:

It is not recognized by adb devices, but:
fastboot devices - gives the following output:
ERROR: could not get pipe properties
3331E6EBCA6000EC fastboot
Click to expand...
Click to collapse
fastboot oem unlock - gives the following:
ERROR: could not get pipe properties
...
FAILED (remote: Erase Fail)
finished. total time: 4.753s
Click to expand...
Click to collapse

alpheus said:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
fastboot oem unlock - gives the following:
Click to expand...
Click to collapse
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data

demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
Thanks, I tried 3 different cables on 3 different operating systems, with the same problem unlocking the fastboot. When I send fastboot oem unlock the device opens a prompt with Yes or No choice, but after choosing Yes, it stays Locked

Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too

demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
demkantor said:
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
Click to expand...
Click to collapse
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!

alpheus said:
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
Click to expand...
Click to collapse
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..

UPDATE (resolved)
Here is an update. Hope this would help others with similar issue, as I've read many threads and folks complaining that they weren't able to unlock fastboot and further root their Nexus S, and who can't boot the phone, which stacked with Google Logo (soft loop). This was the case with my device and finally I got it resolved. I've read some guy tried to hit the phone and after that he was able to boot phone normally. It related to some hardware electrical circle issue. Anyways, I tried to hit my phone by placing it under the direct sun in balcony for some time until the phone got hot and then power it on. And ooops, my phone started booting passed by that Google Logo which was the good sign. Once the phone booted up, I went ahead and activated USB debugging and restarted the phone into the Fastboot mode. while the phone was still hot and in Fastboot mode I run "fastboot oem unlock" and hey, fastboot is Unlocked! Again, this was done while the phone was hot, any previous attempts (read above) weren't successful. From that point, I went ahead and rooted my Nexus S by Nexus Root Toolkit, available on wugfresh.com/nrt, without a slightest problem. Now my phone is fully rooted, bootable and working fine. I thank all who replied to my thread and tried to help and hope this info would help someone with the similar issue.

Rushabh22 said:
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
Click to expand...
Click to collapse
Thank you for your help and suggestions.

Q Mobile X 32
bootloader oem unlock problem
plz help

Q-mobile said:
Q Mobile X 32
bootloader oem unlock problem
plz help
Click to expand...
Click to collapse
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923

Setting.Out said:
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Click to expand...
Click to collapse
can you help me in rooting Qmobile x32

Q-mobile said:
can you help me in rooting Qmobile x32
Click to expand...
Click to collapse
That thread didn't help?

Here's what the guide says...

Phone can't read ADB in Fastboot/Bootloader Mode. Recognizes when its on though.

I need help figuring this out. My phone pops up and recognizes my computer when it's on, but not when in bootloader mode. I'm trying to flash the new bootloader/radios, but I can't. I've already uninstalled and reinstalled google drivers via SDK. Any suggestions? Yes it responds properly when on when i type "adb devices" just not when in bootloader mode.

aval1392 said:
I need help figuring this out. My phone pops up and recognizes my computer when it's on, but not when in bootloader mode. I'm trying to flash the new bootloader/radios, but I can't. I've already uninstalled and reinstalled google drivers via SDK. Any suggestions? Yes it responds properly when on when i type "adb devices" just not when in bootloader mode.
Click to expand...
Click to collapse
Can you be a bit more clear on this? Adb doesn't work in bootloader mode, it isn't meant to, so if you're using adb commands while in the bootloader you're doing the wrong thing. What OS are you using? Exactly what command(s) are you issuing?

How about "fastboot devices"?

Heisenberg said:
Can you be a bit more clear on this? Adb doesn't work in bootloader mode, it isn't meant to, so if you're using adb commands while in the bootloader you're doing the wrong thing. What OS are you using? Exactly what command(s) are you issuing?
Click to expand...
Click to collapse
I figured it out. It took me a bit to realize adb doesn't work in bootloader. But I installed the correct drivers using max Lee's radio, bootloader, vendor flashing video if anyone needs in the future. Thanks for all you help with Heisenberg. https://www.youtube.com/watch?v=jwEJJIQEt3Y if anyone needs help like I did

aval1392 said:
I figured it out. It took me a bit to realize adb doesn't work in bootloader. But I installed the correct drivers using max Lee's radio, bootloader, vendor flashing video if anyone needs in the future. Thanks for all you help with Heisenberg. https://www.youtube.com/watch?v=jwEJJIQEt3Y if anyone needs help like I did
Click to expand...
Click to collapse
We already have a detailed guide right here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Can't find "fastboot" mode in bootloader

Hello, I've bought the HTC U Ultra for my birthday at a very good price (250€) and I'm very satisfied about this phone!
Only, it's been 3 months since I try to root without any success. I can not find the "fastboot" mode in the bootloader and I do not know how.
Yet I followed all the tutorials to the letter (French expression I do not know if you go to understand ... x)) but I have never reached that point. I have the ADBs and all the other files needed.
Also, I made all the updates at the first launch of the phone. Is that why it's blocked?
Thank you in advance.
PS: I also unlocked the bootloader in the development options.
PS n°2: I post here because the French forums are desperate desert for this phone.

Hold both volume down + power together for around 10 seconds. Your phone will vibrate after that. You will then enter download mode, which is actually fastboot.

bc Yume said:
Hold both volume down + power together for around 10 seconds. Your phone will vibrate after that. You will then enter download mode, which is actually fastboot.
Click to expand...
Click to collapse
Ok, but when I want to unlock the bootloader using htcdev, I have < waiting for device > when i enter fastboot oem get_identifier_token.

SofianeLasri said:
Ok, but when I want to unlock the bootloader using htcdev, I have < waiting for device > when i enter fastboot oem get_identifier_token.
Click to expand...
Click to collapse
The computer is unable to recognise your phone. Maybe another port.

bc Yume said:
The computer is unable to recognise your phone. Maybe another port.
Click to expand...
Click to collapse
my device is recognize when it's start, but when it reboot to bootloader, abd / fastboot lost the connection. :/
I've tried with all of my ports.

SofianeLasri said:
my device is recognize when it's start, but when it reboot to bootloader, abd / fastboot lost the connection. :/
I've tried with all of my ports.
Click to expand...
Click to collapse
Are you sure you have USB Debugging on and you are using ADB driver from Google, not the one comes from HTC Sync?

bc Yume said:
Are you sure you have USB Debugging on and you are using ADB driver from Google, not the one comes from HTC Sync?
Click to expand...
Click to collapse
I use minimal adb 1.4.2 and i don't installed htc sync.

I use adb command line directly from Android Developers and have absolutely no problem. Maybe uninstall minimal adb and try that one. I can't help you with something I am not familiar with.

bc Yume said:
I use adb command line directly from Android Developers and have absolutely no problem. Maybe uninstall minimal adb and try that one. I can't help you with something I am not familiar with.
Click to expand...
Click to collapse
Yes but I must to download a lot of GB to user these abd. :/
I've just install htc sync, I tell you more if it work.
UPDATE : Oh it work! x) I never thought it would work! I thought htc sync was a software like those samsull that block the phone.

cool but i've now s-on and a i can"t install twrp with this. x)

SofianeLasri said:
cool but i've now s-on and a i can"t install twrp with this. x)
Click to expand...
Click to collapse
You can install TWRP as long as your bootloader is unlocked, regardless of the status of S-ON or S-OFF

SofianeLasri said:
cool but i've now s-on and a i can"t install twrp with this. x)
Click to expand...
Click to collapse
double check "Allow USB debugging" for the computer. From Developers "Revoke USB debugging Auth" . Unplug & plug back USB cable should come up with dialog box for auth. You may (not sure) this from cmd: adb reboot fastboot which could come up with error msg: "error: device unauthorized. This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong. Otherwise check for a confirmation dialog on your device."

You cant find fastboot mode because it is now called download mode...

Need help unlocking bootloader

I've tried several times to unlock the bootloader and it will not respond to any commands once in fastboot mode. I've tried to follow this guide https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ but whenever I type "fastboot oem unlock" it just says "waiting for any device" and nothing happens. I have usb debugging enabled and oem unlocking on so I don't know what I'm doing wrong. I have the platform tools from Google installed. I can run adb and type "adb reboot bootloader" and it responds, but after that, no fastboot commands work. I mainly just wanted to root so I could restore my apps and data via Titanium Backup. Is there a temp root solution I can use? Or has anyone else experienced this?
Let me know if you need more info. Hopefully this is an easy one.

What do you get if you run "adb devices"?

thedrizzle said:
What do you get if you run "adb devices"?
Click to expand...
Click to collapse
ADB: USAGE: unknown command DEVICES
Or do you mean run it while it's in fastboot?

I feel like it's something simple I'm missing. I've never had trouble figuring this stuff out. I've been rocking an HTC M8 on VenomRom since forever ago so it was time for an upgrade. I've looked at several different guides, but some of them seem to be incomplete. Like the guide at the official TWRP page says to power off the phone. Then it says to hold volume up to go into fastboot mode. I tried following those instructions to a T, but that didn't actually do anything. It doesn't say where to put the twrp.img file, it just says to run the command to boot the .img. Getting into fastboot isn't a problem. It's that no matter what I do once it's in fastboot, I just get "waiting for any device". I've tried the OnePlus6t Manager because I thought maybe I needed a one-click method. But again, it gets to fastboot and goes nowhere from there.

blockhead428 said:
I feel like it's something simple I'm missing. I've never had trouble figuring this stuff out. I've been rocking an HTC M8 on VenomRom since forever ago so it was time for an upgrade. I've looked at several different guides, but some of them seem to be incomplete. Like the guide at the official TWRP page says to power off the phone. Then it says to hold volume up to go into fastboot mode. I tried following those instructions to a T, but that didn't actually do anything. It doesn't say where to put the twrp.img file, it just says to run the command to boot the .img. Getting into fastboot isn't a problem. It's that no matter what I do once it's in fastboot, I just get "waiting for any device". I've tried the OnePlus6t Manager because I thought maybe I needed a one-click method. But again, it gets to fastboot and goes nowhere from there.
Click to expand...
Click to collapse
Do not forget to enable OEM Unlocking in Developer options
Sent from my ONEPLUS A6013 using Tapatalk

Just my 2 cents I'm not an expert but it Might be your drivers or when you installed adb did you do it with administrator rights? The first time tried I couldn't get it to work it wasn't detecting the device in fastboot so I reinstalled adb and then it worked
I just rooted mines today but I went off a YouTube video I looked up and they had everything you needed to download in the description. Took about ten minutes ? I'm not sure if I can put a link on here

DinarQ8 said:
Do not forget to enable OEM Unlocking in Developer options
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I've done that also. Developer options are enabled, USB debugging, and OEM unlocking. Are there newer drivers I need? But if that was an issue, it wouldn't allow me to do "adb reboot bootloader". It'll reboot to fastboot mode, but after typing "fastboot oem unlock" it just says waiting for any device.

blockhead428 said:
ADB: USAGE: unknown command DEVICES
Or do you mean run it while it's in fastboot?
Click to expand...
Click to collapse
In the picture it shows you typed your commands all capitals letters

Dr8ven said:
Just my 2 cents I'm not an expert but it Might be your drivers or when you installed adb did you do it with administrator rights? The first time tried I couldn't get it to work it wasn't detecting the device in fastboot so I reinstalled adb and then it worked
I just rooted mines today but I went off a YouTube video I looked up and they had everything you needed to download in the description. Took about ten minutes I'm not sure if I can put a link on here
Click to expand...
Click to collapse
Try and post it. It let me post the link to the guide in the initial posting. You could be on to something.
This is where I got my version of ADB. https://developer.android.com/studio/releases/platform-tools It's not so much an "install" as it is unpacking a zip archive.

twinnfamous said:
In the picture it shows you typed your commands all capitals letters
Click to expand...
Click to collapse
I did not know it was case-sensitive. I just tried again and it seems to show my devices (I'm transferring files off of my m8 which is why it shows two).
Good call, brother! Where do I go from here?

blockhead428 said:
I did not know it was case-sensitive. I just tried again and it seems to show my devices (I'm transferring files off of my m8 which is why it shows two).
Good call, brother! Where do I go from here?
Click to expand...
Click to collapse
you need to be careful in fastboot. One wrong command can lead to a catastrophe.

I used the adb installer from the same video. Once you unzip it. It's an .exe file which I granted administrator rights to install... it installs adb and drivers and it worked for me
That's the video and did it to a T
Another thing don't use power shell use command

twinnfamous said:
you need to be careful in fastboot. One wrong command can lead to a catastrophe.
Click to expand...
Click to collapse
I'm following a video now. I'm thinking I didn't have the ADB drivers installed so I'm trying that now.

Let us know how it turned out ?

Dr8ven said:
Let us know how it turned out
Click to expand...
Click to collapse
Still getting nowhere. I thought my problem was that I didn't intall the drivers as administrator. So I did it again, following this video https://www.youtube.com/watch?v=B-XZy27wy5o When I reboot into bootloader, I type "fastboot devices" and it just goes right back to the command prompt. Nothing happens. I guess I'm going to try the old fashioned computer restart and see what happens. If all else fails, I can unplug it from the wall and blow on it, lol.
I swear, I've never been this simple before.

blockhead428 said:
Still getting nowhere. I thought my problem was that I didn't intall the drivers as administrator. So I did it again, following this video https://www.youtube.com/watch?v=B-XZy27wy5o When I reboot into bootloader, I type "fastboot devices" and it just goes right back to the command prompt. Nothing happens. I guess I'm going to try the old fashioned computer restart and see what happens. If all else fails, I can unplug it from the wall and blow on it, lol.
I swear, I've never been this simple before.
Click to expand...
Click to collapse
::sigh:: Still no joy. Restarted pc, ran adb devices and it showed my phone. So i reboot into bootloader, typed fastboot devices and it still took me right back to the command prompt.

blockhead428 said:
::sigh:: Still no joy. Restarted pc, ran adb devices and it showed my phone. So i reboot into bootloader, typed fastboot devices and it still took me right back to the command prompt.
Click to expand...
Click to collapse
I was thinking that maybe the latest OTA broke the bootloader unlock process, but someone else in this thread said they just unlocked theirs. I don't understand what the issues is. I've followed this video so closely I could re-enact it in my sleep.

Got it! I had two sets of drivers installed so I uninstalled both and it finally recognized my phone in fastboot. My old drivers from my m8 from 2014 were probably interfering with it. I knew it was something simple. I feel like Carl in Sling Blade when they bring him the lawn mower engine and he says "ain't got no gas in it, mmhmmm".

Nice! For a noob I wasn't too far off lol it just had to be one of those two issues
Enjoy happy rooting ?

blockhead428 said:
Got it! I had two sets of drivers installed so I uninstalled both and it finally recognized my phone in fastboot. My old drivers from my m8 from 2014 were probably interfering with it. I knew it was something simple. I feel like Carl in Sling Blade when they bring him the lawn mower engine and he says "ain't got no gas in it, mmhmmm".
Click to expand...
Click to collapse
Hi I have the same problem, when fastboot it says waiting device. I also had rooted my other phone, so how to find my other driver phone in device manager because I can't find it