Database Info

[Q] stuck trying to root nexus s, please help

I was trying to root my Nexus S
I got to bootloader, flashed rootboot.img and clockwork. Now I'm stuck on the unlocked google reboot.
When I try mounting the sdcard via usb in clockwork I can't get it to show on my comp, so I can't drop the zip files in there to update the phone. I believe that's the last step I need to get my baby working again.
If this is the case do you have any suggestions on how I can get files in there? I thought there might be a fastboot command to move the files there but I can't seem to figure it out.
If not can you please point me in the right direction
I tried searching the forums for a solution but everything I come across does not seem to help my particular needs, I apologize if I missed the solution elsewhere but I'm at wit's end right now
All suggestions are greatly appreciated
Thanks!

I am almost having the same issue. I unlocked the bootloader and flashed recoverymod but was unable to locate the superuser zip file so I rebooted my nexus. When I tried to start over again and fastboot I'm getting an error with CMD saying its waiting for device. On the nexus when in fastboot mode at the very bottom it says fastboot failsomething or another.
Any suggestions as to how I can get fast boot working again?!
Sent from my Nexus S 4G using XDA Premium App

I'm obviously no pro! but from what I gather it sounds like your phone's not being recognized. I had that problem and this guide seemed to solve it so you might find it of some help
nexusshacks.com/nexus-s-hacks/how-to-install-nexus-s-windows-usb-drivers

Thanks, it can't be a driver issue though since I was able to use fastboot to unlock the bootloader. Although it sure does seem like its not connecting properly.
Sent from my Nexus S 4G using XDA Premium App

blahhhh you jinxed me. I just realized how to use ADP, figured it was the way to push the files I needed to SD card and now I'm getting your error. I'll reply with a solution if I find one, hope you do the same! two noobs are better than one after all!!

Yikes! Please do, it's driving me insane!
Sent from my Nexus S 4G using XDA Premium App

Fixed it, a simple battery pull fixed my problem. Rooted it this morning!
Sent from my Nexus S 4G using XDA Premium App

Think you can tell me what driver you're using? When I plug my phone in I see the following in the device manager
ADB Interface
SAMSUNG Android Composite ADB Interface
I tried your battery trick to no avail, I even had ADB running and tried the battery trick and it won't work
Also, fastboot is recognizing my device.
Any help would really be appreicated. it's day 3 with no phone now

I'm at work now till 9 and I'm in CA. Ill look it up when I get home. U have to DL the Google something or another driver in sdk. I remember 4 was at the end of it. Ill post when I get home.
Your phones not working at all?!
Sent from my Nexus S 4G using XDA Premium App

vintagetonez said:
I am almost having the same issue. I unlocked the bootloader and flashed recoverymod but was unable to locate the superuser zip file so I rebooted my nexus. When I tried to start over again and fastboot I'm getting an error with CMD saying its waiting for device. On the nexus when in fastboot mode at the very bottom it says fastboot failsomething or another.
Any suggestions as to how I can get fast boot working again?!
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
hi there
i'm trying to root my xperia x8 using superoneclick, ADB start OK.... waiting.... and i'm waiting more than 5 min i think.... but nothing happen...
-i've extracted/copied xrecovery into sd, phone browser but nothing happen.
- boot the phone and press "back <--" key multiple time.... but phone start as usual ...
can somebody teach me how or give link to show how to root step by step please...
i'm new here..... TT
-- sorry for english.... not my language..

yeah I just switched to the google android service 4 "something or other" not in the mindset to find it. My phone's working it's just in super retardo mode right now. All that's working is the bootloader screen and the clockwork orange screen. I've kind of abandoned all hopes of getting adb to work on it because I've tried EVERTHING (except for what will work). I'm trying to figure out how to get clockwork to work with my pc that way I can get files into the sdcard which is what I was trying to use adb for in the first place.
ps... can you send a pic of your homescreen? I miss mine

U don't need adb to transfer files to your nexus s. Make sure debugging is turned on and mount your SD. You should get a promt to transfer files to and from your device via comp. You can use cmd to transfer with fastboot. I just got home and haven't even downloaded anything for root other than free tethering so I'm not sure which app will allow screen shot capture.
Sent from my Nexus S 4G using XDA Premium App

I'm relatively sure debug is still on otherwise I would not have been able to do what I already did. what's the command to transfer files to sd via fastboot? I tried "push" but that did not seem to work.

Once you plug the phone in.and mount SD.windows will automatically recognize it and prompt what woulf you like to do. Just choose transfer files. Go to the file you want yo transfer and right click. Choose send to E. At least on my comp the nexus shows up as e drive so choose which one it shows up as.
Sent from my Nexus S 4G using XDA Premium App

Thanks for all your help, I really appreciate it. It seems the phone's not being recognized by the computer when I mount it. The drivers show up in device manager when I boot to bootloader but then disappear when I go into clockwork. So I never get a chance to see it in "computer" when I try mounting the sdcard. Any thoughts?

[Q] Am i bricked ?

Hi All,
i rooted my phone using what i thought was the right img file, but i can only assume it was the wrong file as i can now do nothing, i can boot into the Moto symbol, i can get to the droid with the warning triangle and into the fastboot section but i can no longer detect it when connected to the usb...
can anyone suggest a fix or am i screwed ??
thanks for any help

Try reflashing it with my tool, using unbrick feature, maybe you need fastboot drivers, just download it from sdk
Sent from my awesome ICS Xoom with xda Premium HD

cheers xxlordxx
ill give that a go, which drivers do i need to install for the fastboot ?
i downloaded the google usb driver package via the SDK last time, but it seems they are not firing up when i connect the tab.

TheWhiteDragon said:
cheers xxlordxx
ill give that a go, which drivers do i need to install for the fastboot ?
i downloaded the google usb driver package via the SDK last time, but it seems they are not firing up when i connect the tab.
Click to expand...
Click to collapse
If you can boot, you are not bricked - just start over with the root process using the correct image.

hey guys,
i have downloaded LAIOT but im not sure its detecting the pad, currently im getting
Searching For Device
List Of Devices
(Nothing listed)
on the pad
Starting Fastboot Protocol Support

tried doing the same using the different modes.
on Pad
Starting RSD Protocol Support
Same result on LAIOT

Recovery -
Same result.
this has all been done on a windows 7 laptop,
i have a linux laptop, will i get any more success using that with the google driver ?

just had a brain wave, checked device manager - i have an unknown device detected.. thats where the sodding thing has been hiding...
any ideas what drivers i need to get the dam thing detected correectly ?
just going to try using the default google ones from the SDK.

TheWhiteDragon said:
just had a brain wave, checked device manager - i have an unknown device detected.. thats where the sodding thing has been hiding...
any ideas what drivers i need to get the dam thing detected correectly ?
just going to try using the default google ones from the SDK.
Click to expand...
Click to collapse
Try a diff USB cable - download drivers from MOTOROLA website get this file - MotoHelper_2.1.32_Driver_5.4.0.exe
Okay here we go....
first thing let your xoom stuck on M logo.
Then hold power+volume up.
while power up press volume down to get firstboot.(make sure your PC and xoom know each other.)
You will see some text firstboot bla bla bla on left, top of screen.
Second thing open window cmd.exe
then type ...
cd /AndroidSDK/tools (where ever your adb.exe is located)
fastboot flash boot boot.img (the right boot image)
fastboot flash system system.img
fastboot erase cache
fastboot reboot
wait for reboot. You should see splash screen and you smile on your face.

TheWhiteDragon said:
hey guys,
i have downloaded LAIOT but im not sure its detecting the pad, currently im getting
Searching For Device
List Of Devices
(Nothing listed)
on the pad
Starting Fastboot Protocol Support
Click to expand...
Click to collapse
I need to fix it then...
Sent from my awesome ICS Xoom with xda Premium HD

thanks Mjamocha
ill give it ago tomorrow, sorry been flat out at work.
ill also try xxlords again on another machine just incase its the drivers on the laptop which are the problem.

XxLordxX said:
I need to fix it then...
Sent from my awesome ICS Xoom with xda Premium HD
Click to expand...
Click to collapse
sorry guys i have been flat out at work, SCCM deployment is taking a while to learn & play with.
but im back now and hopefully unbuggering my phone
i am going to redo all the bits you guys suggested on my PC rather than Craptop.
hopefully ill have more joy, ill let ya know how i get on 8)

What about using RDS?

woot im back
Thanks guys, just needed a fresh machine to do it on, think the craptop was a bit confused with the drivers.

TheWhiteDragon said:
woot im back
Thanks guys, just needed a fresh machine to do it on, think the craptop was a bit confused with the drivers.
Click to expand...
Click to collapse
Glad you got it going!

Had a similar problem where I had a boot loop and adb didn't recognise my device, but I could still put it into fastboot or recovery with power + vol down.
What I did was boot the Xoom so that it was stuck at the Moto logo, connected to the PC and queued up the fastboot command (fastboot flash boot boot.img) so the command window said "Waiting for device...", then reset the Xoom and manually put it into fastboot again at which point it picked up the queued command and started flashing.

[Q] Recovery of files

Hi,
I have a Nexus S model GT-I9023 which is broken and now Im trying to recover some photos. I searched for a whole lot of guides and I think Im doing it right but can't get it to work.
I acidentally dropped it into a bucket of water, I let it dry and the next day it worked and on for about a week. Then it suddenly stopped working and I couldn't boot my phone, it wouldn't go pass the startup text "Google" and the lock icon.
I have the android SDK installed including the Google USB drivers. I added the PATH to tools and platform-tools. In the terminal i type "cd C:\Program Files\Android\android-sdk\tools" and hit enter and afterwards type "adb devices". It starts the daemon up etc. but does not list any device.
Note: since I cannot boot up the phone and enable usb debuggin I boot the phone up in recovery mode which I think should work and is the same as enabling USB debuggin, if Im not wrong.
I suspect that maybe it's because of the recovery mode or because some drivers. I don't think my computer recognize the devices regularly but Im not sure what it really is.
Any help would be appreciated

bahagiga said:
Hi,
I have a Nexus S model GT-I9023 which is broken and now Im trying to recover some photos. I searched for a whole lot of guides and I think Im doing it right but can't get it to work.
I acidentally dropped it into a bucket of water, I let it dry and the next day it worked and on for about a week. Then it suddenly stopped working and I couldn't boot my phone, it wouldn't go pass the startup text "Google" and the lock icon.
I have the android SDK installed including the Google USB drivers. I added the PATH to tools and platform-tools. In the terminal i type "cd C:\Program Files\Android\android-sdk\tools" and hit enter and afterwards type "adb devices". It starts the daemon up etc. but does not list any device.
Note: since I cannot boot up the phone and enable usb debuggin I boot the phone up in recovery mode which I think should work and is the same as enabling USB debuggin, if Im not wrong.
I suspect that maybe it's because of the recovery mode or because some drivers. I don't think my computer recognize the devices regularly but Im not sure what it really is.
Any help would be appreciated
Click to expand...
Click to collapse
You don't need to boot in recovery, boot in bootloader only.

polobunny said:
You don't need to boot in recovery, boot in bootloader only.
Click to expand...
Click to collapse
I think I might have confused the terms bootloader and recovery mode, what I meant was I press the vol up button and the power button at the same time which then opens the bootloader I guess? anyways, still the same issue for me.

bahagiga said:
I think I might have confused the terms bootloader and recovery mode, what I meant was I press the vol up button and the power button at the same time which then opens the bootloader I guess? anyways, still the same issue for me.
Click to expand...
Click to collapse
Yes that's the bootloader.
Have you installed the ADB drivers? You don't need only the adb and fastboot executable, but also the drivers.
Under Windows, you can install the PDANet software which makes driver installation a breeze on most cases.
http://junefabrics.com/android/

polobunny said:
Yes that's the bootloader.
Have you installed the ADB drivers? You don't need only the adb and fastboot executable, but also the drivers.
Under Windows, you can install the PDANet software which makes driver installation a breeze on most cases.
link
Click to expand...
Click to collapse
Hmm, on the third step where it says "installing pdanet to your phone" it just like freeze and on my phone in the bottom it says "FASTBOOT STATUS - FAILInvalid Command"
what should I do??

bahagiga said:
Hi,
I have a Nexus S model GT-I9023 which is broken and now Im trying to recover some photos. I searched for a whole lot of guides and I think Im doing it right but can't get it to work.
I acidentally dropped it into a bucket of water, I let it dry and the next day it worked and on for about a week. Then it suddenly stopped working and I couldn't boot my phone, it wouldn't go pass the startup text "Google" and the lock icon.
I have the android SDK installed including the Google USB drivers. I added the PATH to tools and platform-tools. In the terminal i type "cd C:\Program Files\Android\android-sdk\tools" and hit enter and afterwards type "adb devices". It starts the daemon up etc. but does not list any device.
Note: since I cannot boot up the phone and enable usb debuggin I boot the phone up in recovery mode which I think should work and is the same as enabling USB debuggin, if Im not wrong.
I suspect that maybe it's because of the recovery mode or because some drivers. I don't think my computer recognize the devices regularly but Im not sure what it really is.
Any help would be appreciated
Click to expand...
Click to collapse
Can you boot into "recovery" and mount the sd from there?
Sent from my Nexus S 4G using xda premium
---------- Post added at 04:54 PM ---------- Previous post was at 04:50 PM ----------
If you can get to bootloader you should be able to get into recovery. And from there you should be able to mount your sd.
Sent from my Nexus S 4G using xda premium

Bkadleck said:
Can you boot into "recovery" and mount the sd from there?
Sent from my Nexus S 4G using xda premium
---------- Post added at 04:54 PM ---------- Previous post was at 04:50 PM ----------
If you can get to bootloader you should be able to get into recovery. And from there you should be able to mount your sd.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I tried but I dont think I can, when I try it just goes into that 'bootup screen, with the Google text and lock icon'. :/ Not sure what to do

Im still stuck and havent been able to get around this, any helpful information is appreciated. Thanks in advance

Hey guys, Im still stuck with this issue. Anyone who has some tips on what to do or has an idea of what it could be? I just formatted my PC yesterday Windows 7 32bit and everything should be up to date.
Kind regards,
baha

If there's anyone out there I would greatly appreciate your help! I have some pictures that are very valuable to me (pictures of my dog) and would really love to see if I could recover them.
I cannot start up my phone the "normal" way, I can only start up the Fastboot mode. I have the Samsung phone drivers installed along with the Google USB drivers. I have attached a picture that shows that there should be no problems with the drivers. I have tried to use the google usb drivers specifically but still the same. I have also attached a picture of the command prompt and as you can see nothing really happens. I have tried different tutorials and all kinds of ways trying to make it work but I have no clue what the problem is since I am not getting any other error message.
Any help is appreciated, please!
I typed fastboot devices in the cmd prompt and it actually listed a device serial number which matches then one stated on my phone in the fastbootmode. Any idea what to do or what this means?

[Q] Bricked my Nexus 5 using cwm. Help!!!!

Long story short, installed clockwork mod recovery in attempt to install a cyanogen nightly. I stupidly formatted everything including data and SYSTEM! Now I can only boot to recovery. When I plug the nexus into any PC it's not picked up as an unidentified piece of hardware on windows so I can't push another rom or adb sideline commands result in "waiting for device". Any suggestions? Should I attempt to RMA?

Reinstall drivers. Boot into the bootloader and flash the factory image.

El Daddy said:
Reinstall drivers. Boot into the bootloader and flash the factory image.
Click to expand...
Click to collapse
Thank you!! I never used the USB cable that actually came with the NEXUS until just now, the PC finally detected the phone as i was in the Bootloader and start automatically Download and Writing, rebooting itself and looks like it's booting up. Thanks again. Very quick response.

I accidentally formatted system as well, slip of the finger. I am unable to get my computer to recognize my device, "fastboot devices" lists nothing. Have tried flashing factory software, but it just says "waiting for device". Any suggestions???

Check USB drivers. Might not be working
Sent from my Nexus 5 using Tapatalk

wltnkyl said:
I accidentally formatted system as well, slip of the finger. I am unable to get my computer to recognize my device, "fastboot devices" lists nothing. Have tried flashing factory software, but it just says "waiting for device". Any suggestions???
Click to expand...
Click to collapse
If you are on windows 8 or 8.1 you have turn of driver signiture enforecment. http://sixcolumns.com/how-to-disable-and-bypass-driver-signature-enforcement-in-windows-8/
To make adb works when you are in recovery you need the naked usb drivers. Turn on sideload in the recovery and on a cmd type this: adb sideload path_to_your_rom_file.zip end hit enter.

bitdomo said:
If you are on windows 8 or 8.1 you have turn of driver signiture enforecment. http://sixcolumns.com/how-to-disable-and-bypass-driver-signature-enforcement-in-windows-8/
To make adb works when you are in recovery you need the naked usb drivers. Turn on sideload in the recovery and on a cmd type this: adb sideload path_to_your_rom_file.zip end hit enter.
Click to expand...
Click to collapse
Thank you so much!! Unfortunately I am only able to hit the THANKS button once. I thought for sure that it was done for!
I have bricked my phone before, but have always been able to find a workaround. This time, not so much.
Again, Thank You!!

wltnkyl said:
Thank you so much!! Unfortunately I am only able to hit the THANKS button once. I thought for sure that it was done for!
I have bricked my phone before, but have always been able to find a workaround. This time, not so much.
Again, Thank You!!
Click to expand...
Click to collapse
you can also try unlock bootloader, flash factory images. and bumm your phone works again.
install fastboot and etc... http://forum.xda-developers.com/showthread.php?t=2588979
guide to return stock http://forum.xda-developers.com/showthread.php?t=2513701
Oh and send me an e-mail: [email protected] then I will instruct you to downlaod teamviewer, so I could resolve your driver problems

You should give wag tool a try it completely brings you back to stock
Sent from my Nexus 5 using XDA Premium 4 mobile app

Please help me fix this... (Boot problem)

I bought a nexus 5 as a gift for someone and wanted to do some personalizing. I made a custom boot animation, converted it through the "Boot animations" app on google play, but now it hangs on the animation. I tried connecting the device through adb but I can't get my drivers to work, says that nothing is connected. I tested the connection with MY N5 as well and I receive the same result. The reason I tried to connect it though adb was that I read you could change the boot animation through there. Any help would be appreciated... thanks guys :crying:

Are u using Linux? And have u tried using fastboot?

Aurey24 said:
Are u using Linux? And have u tried using fastboot?
Click to expand...
Click to collapse
I'm on windows, and when in fastboot the console on my PC says that it can't detect the phone.

Go to device manager on your pc with the device connected. Do you see anything with a yellow !? If so right click on it and update the driver. Go to let me choose a driver from the pc. Find the adb composite interface driver.
Sent from my Nexus 9 using XDA-Developers mobile app

Jiharu Ikumiya said:
I'm on windows, and when in fastboot the console on my PC says that it can't detect the phone.
Click to expand...
Click to collapse
Yep as u can see it's the drivers that isn't making it happen, typically why I use Linux, just dual boot some light Ubuntu distro like lxde using a USB and use the terminal, the nexus will definitely get recognized and u can save it, I'm almost 100% positive this is the easiest way unless u know how to troubleshoot the drivers in windows, or u don't want to in which case I can get Windows installed onto my PC and figure out how to get it working to help you if u really want to stick with it.

Aurey24 said:
Yep as u can see it's the drivers that isn't making it happen, typically why I use Linux, just dual boot some light Ubuntu distro like lxde using a USB and use the terminal, the nexus will definitely get recognized and u can save it, I'm almost 100% positive this is the easiest way unless u know how to troubleshoot the drivers in windows, or u don't want to in which case I can get Windows installed onto my PC and figure out how to get it working to help you if u really want to stick with it.
Click to expand...
Click to collapse
A friend of mine found the Nexus 5 toolkit on here, I didn't know it existed. We're up and running now, sorry guys... just a bit of a scare. I appreciate the offer of your help though, means a lot to me!

Jiharu Ikumiya said:
A friend of mine found the Nexus 5 toolkit on here, I didn't know it existed. We're up and running now, sorry guys... just a bit of a scare. I appreciate the offer of your help though, means a lot to me!
Click to expand...
Click to collapse
NP, glad u good it working, I thought u knew about the toolkit and that's what u used to flash the phone. I'm glad u figured it out.