Database Info

[Q] NS4G Not recognised

Hi all,
I've got a Nexus S 4G CDMA Sprint phone running Stock ICS 4.0.4 IMM76D.
My bootloader is unlocked from previous roots and whatnot.
My problem is that my phone is not being recognized by my computer at all. We're talking complete nonrecognition. No yellow triangle in device manager, no pop-ups, nothing. This phone will just not be read by my computer! I've tried different cords, different computers, re-installation of drivers after resetting my computer, installed PDA net, did a factory reset on the phone, I've literally been on Google for hours upon hours upon hours trying to figure this out and can't figure out why the computer is not recognizing the phone and why the phone is not allowing me to put it into usb mounting. It is however, charging via the computer and wall plug. I can get into stock 3e android recovery, fastboot using V-Up and Power and I can get it into download mode. It is NOT recognized in any modes by the computer nor other computers including my Linux box. The phone states that the usb control initializes but then ends a moment later. I am thinking this is a hardware issue but that leaves me with two issues:
If I was to go to Sprint to have it fixed they would realize my bootloader was unlocked thus voiding the warranty and I'd feel like quite an idiot at the store
If it is hardware related why is the charge working on the device.
I have also tried to bend up the usb plate to make it touch the pins better but that did not help at all. I am at my wits end and really need some help here, I've done everything I could find on Google and here plus more. I want to just return it but with the bootloader unlocked this is really not a possibility. I am looking for help to either become able to lock the bootloader without it having to be connected via the computer so I can then get it fixed if it is hardware related or if I can get the darn thing to be read by the computer once more. so yea, this is where I am at and I would appreciate it so much if someone could help me out, thanks guys!!!

Wireless adb in playstore should help.
Sent from my Nexus S 4G using XDA

That would be perfect! Only problem is that it requires root access on the phone which I am unable to obtain because I cannot access the phone. Is there a way to root the phone without having to connect it via the computer? Something like an update.zip with files able to be flashed through android recovery 3e? If I can get root access than wireless adb would be perfect.
*ultimately if I could remove signature checking in Android Recovery 3e that would work so I could in turn try to root the phone and install a different recovery to then try a different rom to see if that in turn fixes the issue.

Ebicoustic said:
That would be perfect! Only problem is that it requires root access on the phone which I am unable to obtain because I cannot access the phone. Is there a way to root the phone without having to connect it via the computer? Something like an update.zip with files able to be flashed through android recovery 3e? If I can get root access than wireless adb would be perfect.
*ultimately if I could remove signature checking in Android Recovery 3e that would work so I could in turn try to root the phone and install a different recovery to then try a different rom to see if that in turn fixes the issue.
Click to expand...
Click to collapse
You might be able to download your rom of choice and rename it update.zip. I'm not sure if it will flash though....someone else chime in if I'm wrong. You can use wireless file transfer if needed.
Sent from my Nexus S 4G using XDA

Yea I've tried that, everything gets shot down by the recovery with a E:Signature Verification Failed. Thank you for your help so far but I don't think this is something that is going to be helped. I've put in a ticket to Samsung for a repair under it's warranty. In the past I've sent in a rooted phone and they've fixed it so I think I'm going to give that a shot. Just don't want to be without a phone for 2+ weeks.

Well good luck...you are running stock unrooted so it shouldn't matter. It is a dev phone for damn sake. Sorry couldn't help.
Sent from my Nexus S 4G using XDA

Well if you want to download a custom rom... Since you are on this forum. Download any rom (preferably CM9 since its quite good from my experience). Flash the stable version and wait till everything is completed. Now when you flash make sure you download a recovery...eg ClockWorkMod Recovery from google market. You should now have a custom rom installed and download wireless adb as chappy said. See if that works

[Q] Mount USB storage under ClockWorkmod Recovery 6.0.1.0

Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max

Use this guide to recover your device.

Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.

How did you erase everything? Was it through fastboot or CWM?

I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.

maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...

maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2

*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2

The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?

Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2

Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307

I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2

[Q] I've tried everything to get out of boot loop

Hello everybody,
I am new to the forum and also new to Androids. After years of using iPhones and finally becoming fed up Apple, I've decided to try something new (please don't judge my prior smartphone selection and start posting opinions about the 2 operating systems, I do not want this thread to turn into one of the "battle of the phones" thread that I've experienced many times on iPhone forums). My friend recently got an S3 and had no use for his Galaxy S 4g, so he gave it to me so that I could try out an Android. There was one issue though, he said that the phone would not get past the Galaxy S screen and would keep re-booting itself (stuck in a boot loop). He said if I could figure out a way to fix it then it's mine.
That being said, here's my dilemma. I've tried many different methods to get the phone out of a boot loop. The first method I tried was putting the phone into restore mode and selecting the "reinstall packages" option. After this executes I get the message:
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
After some further research I discovered a nice little program called Odin I read a lot about Odin and how to properly use it. After trying at least 5 different methods to get the phone into download mode with no success, I purchased a jig. The jig did the trick and instantly put me into download mode, I was ecstatic and hopeful that I could now fix the phone with Odin. I connected the phone to my PC in download mode, but Odin still didn't recognize the phone (I tried many versions of Odin, 1.85, 1.87, and the most recent 3.07). I do have the latest drivers for this phone, which I downloaded from Samsung's website. The phone will charge through the computer but the computer does not recognize it otherwise and will not allow me access its mass storage (I am running Windows 7 64 bit). I have tried using a different USB cable, and I have tried to use a different PC, the other PC I used popped up with a message saying that Windows could not successfully download the drivers (that was after I downloaded the drivers from Samsung's webpage and plugged the phone into the computer). I've even tried transferring stock firmware onto an external SD card and loading it onto the phone from restore mode (is that even possible to do?). I have also tried running Odin in compatibility mode, still didn't detect the phone. I should probably also mention that Kies Mini also does not recognize the phone. I asked my friend if he ever tried rooting this phone and he said no, so I'm assuming this issue has nothing to do with a failed attempt to root.
I really want to get this phone working, but I have run out of options to try. I am hoping that someone on here has a solution for me from a similar experience. After reading through the forum, I have noticed that people on here are very helpful and also very friendly; something that I can say is very different from some of iPhone forums I've used. I apologize if there is already a similar thread to mine, I've read through many threads and none of the solutions have worked for me. I also apologize for my first post being so lengthy, I just wanted to state all of the methods that I've tried to fix this phone. Thanks for your replies.

Hi hubbs134
You have come to the right place.
First,
I suggest you read a little bit about this phone and how to put it in Recovery (by holding Volume Up + Volume Down + Power until you see the SGS4G splash screen) and Download modes, it will help you in the future.
You can find it all in the Wiki.
Second, use this guide to One-Click Heimdall your way to Stock KJ6 2.3.6 Gingerbread ROM (latest official ROM for this phone).
If you use this file (instead) with that guide, you will also get phone rooted, or else you will need to make another flash of a rooted kernel (as the guide suggests).
Now, if you have the official latest stock, but still want some ICS/JB lovin', if you have CWM recovery v5 (you will see the recovery info once you're in that mode), you can flash CM9/AOKP/HebMIUI/UltraGen/RemICS/CM10/Slimbin/etc. etc. etc. ROMs.
Enjoy and welcome aboard!
P.S what the @#%#$ were you doing with an iphone ?

itzik2sh said:
Hi hubbs134
You have come to the right place.
First,
I suggest you read a little bit about this phone and how to put it in Recovery (by holding Volume Up + Volume Down + Power until you see the SGS4G splash screen) and Download modes, it will help you in the future.
You can find it all in the Wiki.
Second, use this guide to One-Click Heimdall your way to Stock KJ6 2.3.6 Gingerbread ROM (latest official ROM for this phone).
If you use this file (instead) with that guide, you will also get phone rooted, or else you will need to make another flash of a rooted kernel (as the guide suggests).
Now, if you have the official latest stock, but still want some ICS/JB lovin', if you have CWM recovery v5 (you will see the recovery info once you're in that mode), you can flash CM9/AOKP/HebMIUI/UltraGen/RemICS/CM10/Slimbin/etc. etc. etc. ROMs.
Enjoy and welcome aboard!
P.S what the @#%#$ were you doing with an iphone ?
Click to expand...
Click to collapse
Thanks for your reply, I have read a lot about this phone and know how to get into download and recovery mode. I tried the method you mention, however, when running the command window I get errors for both roms you suggested (i attatched a screen shot of the errors I'm getting). Do you know how I can fix these errors so that I can proceed with the rest of the tutorial? Thanks.
PS I only had an iPhone because I had yet to discover how bad a** Androids are

It sounds like you can't use Odin because of a windows issue. Try installing linux. I use ubuntu
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 07:48 AM ---------- Previous post was at 07:47 AM ----------
You can also run as live CD or in a virtual machine
Sent from my HTC One X+ using xda app-developers app

hubbs134 said:
Thanks for your reply, I have read a lot about this phone and know how to get into download and recovery mode. I tried the method you mention, however, when running the command window I get errors for both roms you suggested (i attatched a screen shot of the errors I'm getting). Do you know how I can fix these errors so that I can proceed with the rest of the tutorial? Thanks.
PS I only had an iPhone because I had yet to discover how bad a** Androids are
Click to expand...
Click to collapse
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !

itzik2sh said:
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !
Click to expand...
Click to collapse
I second this... This should fix your driver issues.

Thanks for both of your replies. Odin detected my friends GS3 so I know it's not a Windows issue.
itzik2sh I did what you suggested and now got the command to function properly. I am going to try and finish the tutorial, I will be back soon with results. Thanks.

The phone is in download mode with Heimdall One-click 1.3.1 running and nothing is popping up in the command window. Neither is showing that the device is connected. Any suggestions? Thanks

Irish Enigma said:
I second this... This should fix your driver issues.
Click to expand...
Click to collapse
I forgot to mention that I can here the sound that a device was just connected to the computer via USB, and a message pops up saying USB device not recognized. When I click on the message it says "One of the USB devices connected to this computer has malfunctioned, and Windows does not recognize it."

Tried a different port? Tried second different port with a different USB cable?

itzik2sh said:
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !
Click to expand...
Click to collapse
Theraze said:
Tried a different port? Tried second different port with a different USB cable?
Click to expand...
Click to collapse
Ok I got the device connected and I got Zadig running, however, there is no option for "Samsung USB Composite Driver" on the drop down list, on "gadget Serial", "Gadget Serial Control (interface 0), and "1.3 HD Webcam (Interface 0)'. What should I do?

On the one-clicks, you don't actually want to use zadig. Apparently it conflicts, which is awesome for something that gets released WITH the tool.
If you're doing manual Heimdall, make sure you've told zadig to list all devices in the menus. Your phone should show up after that.
If you're using a one-click, make sure you're using a USB port on your computer where you have NOT installed zadig, Kies, or Samsung official drivers. Follow the steps in the one-click religiously, and it should cooperate.

Follow the guide %100 then Odin should work
Sent from my HTC One X+ using xda app-developers app

Ok I ended up getting the phone to register in Odin. I flashed it with the stock rom in Odin and it said success. The phone booted and it seemed like it was going to work but then the recovery menu came up. I posted a screen shot of what it says, what action should I take from here? Thanks

I am also in a different boot loop now, before it would load to the first screen (black screen saying samsung galaxy 4g) then restart, now it boots to past the splash screen to where it says "Samsung" and then reboots back to the screen where the pink letters roll across the whole screen. I don't need to flash bootloaders do I?

Looks like recovery is broken or the updater script on the ROM you're trying to flash is messed up. Flash a new and the proper recovery via Odin then download a new Rom and either sideload it or mount usb from recovery and push it... Or you could just use Odin XD
EDIT: Samsung's are easy to brick and hard to debrick it may take a couple of trys
Sent from my HTC One X+ using xda app-developers app

Irish Enigma said:
Looks like recovery is broken or the updater script on the ROM you're trying to flash is messed up. Flash a new and the proper recovery via Odin then download a new Rom and either sideload it or mount usb from recovery and push it... Or you could just use Odin XD
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
OK GREAT NEWS! After flashing with Odin and that screen popping up, I clicked update from SD card, which failed. I then click system reboot, which brought me into the new boot loop. I put back into download mode and re-flashed with One-Click. Same recovery menu came up as before but when I clicked reboot system it hung at the "Samsung" black screen (after the splash screen) for about 20-30 seconds and then booted up I'm afraid to turn the phone off and see if it reloads lol. Is it safe to say that it is fixed? Or should I still follow your advice and run the proper recovery in Odin and then sideload a new rom? Or take different action? Thanks for all your help guys! Everyone gets a thanks click for being so helpful and friendly on an unhappy/confused/pissed off/ now happy new Android user!

Ok I just put my Tmobile simcard in and the phone is not detecting the sim. Any suggestion?

The IMEI number and baseband both say "unknown", I'm assuming this has to do with the simcard not registering?

hubbs134 said:
The phone is in download mode with Heimdall One-click 1.3.1 running and nothing is popping up in the command window. Neither is showing that the device is connected. Any suggestions? Thanks
Click to expand...
Click to collapse
What Heimdall package are you applying ?
After JAR package runs you are ready to go.
As I wrote, according to guide you can reinstall "Gadget" driver.
EDIT :
Enigma, if you're not an owner of an SGS 4G please stop advising.
Odin is not the common way since we have MTD ROMs and it had its problems.
hubbs134,
blank IMEI is a serious problem. without a proper IMEI your device is everything but a phone.
Try this : take battery off, press the POWER button for 10 seconds, leave device untouched for 15 minutes and then put battery back and power up.
This could bring your IMEI back to life. If not... maybe another flash will help.
P.S
The 3e recovery image you put on post #14 is a snapshot of the the stock unrooted ROM recovery.

[Q] LG optimus pro G bricked after using exitrecovery.zip

hello,
I hope someone can help me with my AT&T LG Optimus Pro G phone, which I have royally screwed up.
I was experimenting with the cyogen mod and after installation I installed the freegee app and once the cwm recovery was installed, I decided to go into the recovery by holding down up volume and power button.
Once I was in recovery for CWM i couldn't exit out, and the phone constantly booted into recovery after every reboot, even if i took out the battery, and powered it on.
I tried reflashing the cynogen mod through the sd card, and even though I would get success message the phone would still reboot into the cwm recovery.
I started doing research on the internet and i found file exitrecovery.zip that could be used to possibly get the phone out of the cwm recovery.
After installing exitrecovery.zip, I rebooted the phone, and now I have complete black screen. There are no light, no hints the phone is even turning on, and I can't get into recovery( or at least I can't tell). The only thing now is that when i connect the phone to the computer the window tries to install drivers for the device, and eventually prompts to insert a CD for LG drivers. I already have LGUnitedMobileDriver v.3.10.1 connection drivers installed from their website.
Please help, I am really stuck here..... and have no clue what to do. I am fairly new with rooting and modding, and I am extremely miserable.
The phone is still under warranty from LG. Anyone if all else fails, and since the phone has no screen or lights, whether they would replace it?
Attaching the exitrecovery.zip that I used.
sobbing....

babaghanush said:
hello,
I hope someone can help me with my AT&T LG Optimus Pro G phone, which I have royally screwed up.
I was experimenting with the cyogen mod and after installation I installed the freegee app and once the cwm recovery was installed, I decided to go into the recovery by holding down up volume and power button.
Once I was in recovery for CWM i couldn't exit out, and the phone constantly booted into recovery after every reboot, even if i took out the battery, and powered it on.
I tried reflashing the cynogen mod through the sd card, and even though I would get success message the phone would still reboot into the cwm recovery.
I started doing research on the internet and i found file exitrecovery.zip that could be used to possibly get the phone out of the cwm recovery.
After installing exitrecovery.zip, I rebooted the phone, and now I have complete black screen. There are no light, no hints the phone is even turning on, and I can't get into recovery( or at least I can't tell). The only thing now is that when i connect the phone to the computer the window tries to install drivers for the device, and eventually prompts to insert a CD for LG drivers. I already have LGUnitedMobileDriver v.3.10.1 connection drivers installed from their website.
Please help, I am really stuck here..... and have no clue what to do. I am fairly new with rooting and modding, and I am extremely miserable.
The phone is still under warranty from LG. Anyone if all else fails, and since the phone has no screen or lights, whether they would replace it?
Attaching the exitrecovery.zip that I used.
sobbing....
Click to expand...
Click to collapse
Find flow ROM with expansion .exe and try it to sew from a computer.

could you further elaborate please
lykosha said:
Find flow ROM with expansion .exe and try it to sew from a computer.
Click to expand...
Click to collapse
hi, thanks for your reply. Again I very much new to the rooting and android OS tinkering, and nowhere close to an experienced user.
I tried to use google with your information in regards to how to use flow ROM with expansion.exe, but did not get any leads.
I would appreciate if you could elaborate more on this process.
When my phone is connect to the computer via usb is is constantly trying to install drivers. I had already installed LG usb connection drivers in the past and it was successful. It almost seems it tries to install driver yet fails after receiving no input from the phone, and then request LG CD with drivers.

babaghanush said:
hi, thanks for your reply. Again I very much new to the rooting and android OS tinkering, and nowhere close to an experienced user.
I tried to use google with your information in regards to how to use flow ROM with expansion.exe, but did not get any leads.
I would appreciate if you could elaborate more on this process.
When my phone is connect to the computer via usb is is constantly trying to install drivers. I had already installed LG usb connection drivers in the past and it was successful. It almost seems it tries to install driver yet fails after receiving no input from the phone, and then request LG CD with drivers.
Click to expand...
Click to collapse
Try to find driver on the web-site of producer. Set them. Overload a vehicle in Bootloader. In the controller of devices on компе must be determined your device. Then on a computer start sewing - .EXE.

Did you get this problem resolved? I have the exact problem with the exact phone!!!

thank you very much

[Q] Urgent! Stuck at bootloader but cant do anything

Hi u all!
First of all thank you for your time and sorry for my english, I speak spanish.
I have a nexus s i9023. I was using CyanogenMod 11 experimental 24042014.
I was having many problems and decided to downgrade to the stable version 10.1.2
It downloaded ok, installed all the updates, rebooted and then got stuck in the logo screen when booting.
The problem is that my nexus s has a broken the power button, it doesn't work.
As for right now the olny thing I can do is to enter the bootloader screen, but cant move throgh the options with the volume keys, it's like its stuck.
If I plug in the device when in the bootloader (fastboot mode) screen my PC doesn't recognice it, I search in the device manager but it doesn't appear.
If it helps when I plug in the battery the phone starts on in it's on.
Please, any help is appreciated.
Im really sad because I love my nexus.
Thank you!!!

Same here. Any help for us would be great. Thanks.

shd128 said:
Hi u all!
First of all thank you for your time and sorry for my english, I speak spanish.
I have a nexus s i9023. I was using CyanogenMod 11 experimental 24042014.
I was having many problems and decided to downgrade to the stable version 10.1.2
It downloaded ok, installed all the updates, rebooted and then got stuck in the logo screen when booting.
The problem is that my nexus s has a broken the power button, it doesn't work.
As for right now the olny thing I can do is to enter the bootloader screen, but cant move throgh the options with the volume keys, it's like its stuck.
If I plug in the device when in the bootloader (fastboot mode) screen my PC doesn't recognice it, I search in the device manager but it doesn't appear.
If it helps when I plug in the battery the phone starts on in it's on.
Please, any help is appreciated.
Im really sad because I love my nexus.
Thank you!!!
Click to expand...
Click to collapse
kijp15 said:
Same here. Any help for us would be great. Thanks.
Click to expand...
Click to collapse
Seems like a driver issue. Can you try installing the drivers in a different system?
If it goes well, then use install cwm touch recovery from fastboot. You can take backup and flash new ROMs after that.
Try Nexus Root Toolkit to install drivers if you don't have access to a different system.

smit.sanghavi said:
Seems like a driver issue. Can you try installing the drivers in a different system?
If it goes well, then use install cwm touch recovery from fastboot. You can take backup and flash new ROMs after that.
Try Nexus Root Toolkit to install drivers if you don't have access to a different system.
Click to expand...
Click to collapse
Don't I need to have android debugging enabled? If so, I don't think Nexus Root Toolkit will work. I flashed a ROM to my NS4g & I get boot loops. I flashed the wrong Gapps a few months ago.
I was hoping there would be a way to automatically turn android debugging on. I know it may sound dumb & also probably impossible.
Any other tips.
Tell me I'm screwed. Haha.

kijp15 said:
Don't I need to have android debugging enabled? If so, I don't think Nexus Root Toolkit will work. I flashed a ROM to my NS4g & I get boot loops. I flashed the wrong Gapps a few months ago.
I was hoping there would be a way to automatically turn android debugging on. I know it may sound dumb & also probably impossible.
Any other tips.
Tell me I'm screwed. Haha.
Click to expand...
Click to collapse
I disabled USB debugging. Rebooted to bootloader. Fired up 'fastboot devices' on cmd and could see my phone. This tells me that I do not need USB debugging on fastboot.
If you see an unknown device in Device Manager while in fastboot then use Universal Naked Driver to install the drivers. But since you don't, you'll need another PC to do this stuff. Once drivers are installed, you can do a 'fastboot reboot recovery' to get into recovery and fix the the problems. The first thing I advice is to flash a touch recovery. The rest is up to you.

Flash back the original soju firmware back onto your device by first using "nexus s root toolkit v.1.8.2 by wugfresh". It may take a little of your time downloading the roms and installing the drivers but trust me it should be working and your phone will boot into stock android 4.1.2. You can then root your device and install custom recovery as normal. Anything do pm me :laugh: ps, click the bricked option one the software is loaded up and remember to connect your device only and remove other phones from your computer