Good day, XDA.
Recently, I became the proud owner of a Nexus S 4G, primarily because whomever had the phone prior to me had decided that flashing a GSM rom onto their Nexus S 4G would be a good idea. Needless to say, and as you can all probably guess, this did not benefit the functionality of this phone.
So lets start from the top, the phone is able to power on and boot up, it is running 2.3.6 stock. About phone reads the following:
Model Number: Nexus S
Android Version: 2.3.6
Baseband Version: Unknown
Kernel Version: 2.6.35.7-gf5f63ef [email protected] #1
Build Number: GRK39F
It has no SU binary. While powered up in this mode, it can charge VIA usb, but is unable to be seen by the computer with debugging mode on, or with debugging mode off. Neither option would seem to result in the phone being picked up by either Windows or Linux (Odd that it charges fine though. I did confirm this was not a "Charge Only" cable.)
Moving on, I can boot into fastboot, where I am presented with the following:
Product Name - Herring
HW Version - Rev 03 (JTAG)
Bootloader Version - I9020XXKA3
Baseband Version - I9020XXKF1
Carrier Info - SPR
Lock state - Unlocked.
At the bottom when booting into fastboot, it shows me "USB Control Init", followed immediately by "USB Control Init End". The computer does not see the device when plugged in here either. So no pushing fastboot or adb commands.
Booting into recovery, I am presented with Andy, standing next to a White triangle with a yellow exclaimation mark in it. After fiddling around with the power and volume buttons, I am eventually presented with a screen that states
"Android system recovery <3e>". Oh boy! Stock recovery. How lucky I am. It has the option to apply update from /sdcard, but these need to be signed; and it seems every update.zip file for the Nexus S 4G that I can find makes the assumption that you are on the previous android version, and will not flash if you are not.
So here is where I currently am. I can download zip files over wifi and attempt to push them out to the phone, but there is no PC connectivity, which seems to hinder my attempts at making it work a bit better. I will admit, I am new to the Nexus S (Having never used one before), and to the Samsung devices rooting community (Having been exclusively HTC prior to this). So I might be missing something; does anyone have any thoughts on where to go from here? Sorry for the long post.
SoberSquid said:
Good day, XDA.
Recently, I became the proud owner of a Nexus S 4G, primarily because whomever had the phone prior to me had decided that flashing a GSM rom onto their Nexus S 4G would be a good idea. Needless to say, and as you can all probably guess, this did not benefit the functionality of this phone.
So lets start from the top, the phone is able to power on and boot up, it is running 2.3.6 stock. About phone reads the following:
Model Number: Nexus S
Android Version: 2.3.6
Baseband Version: Unknown
Kernel Version: 2.6.35.7-gf5f63ef [email protected] #1
Build Number: GRK39F
It has no SU binary. While powered up in this mode, it can charge VIA usb, but is unable to be seen by the computer with debugging mode on, or with debugging mode off. Neither option would seem to result in the phone being picked up by either Windows or Linux (Odd that it charges fine though. I did confirm this was not a "Charge Only" cable.)
Moving on, I can boot into fastboot, where I am presented with the following:
Product Name - Herring
HW Version - Rev 03 (JTAG)
Bootloader Version - I9020XXKA3
Baseband Version - I9020XXKF1
Carrier Info - SPR
Lock state - Unlocked.
At the bottom when booting into fastboot, it shows me "USB Control Init", followed immediately by "USB Control Init End". The computer does not see the device when plugged in here either. So no pushing fastboot or adb commands.
Booting into recovery, I am presented with Andy, standing next to a White triangle with a yellow exclaimation mark in it. After fiddling around with the power and volume buttons, I am eventually presented with a screen that states
"Android system recovery <3e>". Oh boy! Stock recovery. How lucky I am. It has the option to apply update from /sdcard, but these need to be signed; and it seems every update.zip file for the Nexus S 4G that I can find makes the assumption that you are on the previous android version, and will not flash if you are not.
So here is where I currently am. I can download zip files over wifi and attempt to push them out to the phone, but there is no PC connectivity, which seems to hinder my attempts at making it work a bit better. I will admit, I am new to the Nexus S (Having never used one before), and to the Samsung devices rooting community (Having been exclusively HTC prior to this). So I might be missing something; does anyone have any thoughts on where to go from here? Sorry for the long post.
Click to expand...
Click to collapse
what model is your nexus s? i9020A i9023 ect..? the link below has a ton of stock roms for various nexus s versions and most are flashable via Stock Recovery
http://forum.xda-developers.com/showthread.php?t=1063664
It is the SPH-D720, my appologies for leaving that out. Unfortunately, it seems the D720 has the misfourtune of not having a fully flashable ROM listed on that page.
SoberSquid said:
It is the SPH-D720, my appologies for leaving that out. Unfortunately, it seems the D720 has the misfourtune of not having a fully flashable ROM listed on that page.
Click to expand...
Click to collapse
Its a shame it wont connect to adb because that's one of the few nexus s that has signed images flashable via fastboot.
Sent from my Nexus S using xda premium
Indeed. It is quite odd - It can boot into fastboot, download mode, etc just fine, but it isn't picking it up at all on the PC. I'm thinking it has to do something with the kernel-mode USB drivers, prehaps there are different drivers used for the CDMA and GSM varients? It is a bit frustrating because it would be a fairly simple fix if fastboot could pick it up.
SoberSquid said:
Indeed. It is quite odd - It can boot into fastboot, download mode, etc just fine, but it isn't picking it up at all on the PC. I'm thinking it has to do something with the kernel-mode USB drivers, prehaps there are different drivers used for the CDMA and GSM varients? It is a bit frustrating because it would be a fairly simple fix if fastboot could pick it up.
Click to expand...
Click to collapse
You might want to try reinstalling the drivers, I use an apple computer & they dont require those drivers so i cant be much help there. Here's another link to check out. Pete Alfonso makes roms from the Nexus S and has the original signed software images for the Nexus S 4g and some other stuff that might help you... http://download.peteralfonso.com/crespo4g
Hmm, looking at his site, he has quite a lot of good stuff, most of it requires a non-stock recovery though. The Nexus S 4G (When it came out), was running 2.3.4, in contrast to the normal Nexus S. I wonder, Since my phone is currently reading on a GSM rom/radio, could I flash the phone to 2.3.3 (Android 2.3.3/GRI40/XXKB1 Radio/KA3 Bootloader), use gingerbreak to gain SU, install CWM, and possibly flash back to a proper baseband and rom from there? Or is that really looking at mucking things up?
SoberSquid said:
Hmm, looking at his site, he has quite a lot of good stuff, most of it requires a non-stock recovery though. The Nexus S 4G (When it came out), was running 2.3.4, in contrast to the normal Nexus S. I wonder, Since my phone is currently reading on a GSM rom/radio, could I flash the phone to 2.3.3 (Android 2.3.3/GRI40/XXKB1 Radio/KA3 Bootloader), use gingerbreak to gain SU, install CWM, and possibly flash back to a proper baseband and rom from there? Or is that really looking at mucking things up?
Click to expand...
Click to collapse
I wouldnt flash any rom with a bootloader not made for your phone.
---------- Post added at 01:22 PM ---------- Previous post was at 01:18 PM ----------
scott8281 said:
I wouldnt flash any rom with a bootloader not made for your phone.
Click to expand...
Click to collapse
you might try this flashable update... Look down towards the bottom of the page... they are flashable via stock recovery.... http://forum.xda-developers.com/showthread.php?t=1063664 D720:
Android 2.3.4 (Build GRJ06D/PRKC9 Radio/KC5 Bootloader)
2.3.4 (GRJ06D) -> 2.3.4 (GRJ22)
2.3.4 (GRJ06D) -> 2.3.5
2.3.4 (GRJ06D) -> 2.3.7
Android 2.3.4 (Build GRJ22/PRKD8 Radio/KC5 Bootloader)
2.3.4 (GRJ22) -> 2.3.5
2.3.4 (GRJ22) -> 2.3.7
Android 2.3.5 (Build GRJ90/PRKE5 Radio/KC5 Bootloader)
2.3.5 -> 2.3.7
Tried all 3 of those, they state the following:
-- Install /sdcard/Download ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
I believe all 3 of those are expecting you to be on the prior android version, and when it sees that you are not, it fails.
SoberSquid said:
Tried all 3 of those, they state the following:
-- Install /sdcard/Download ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
I believe all 3 of those are expecting you to be on the prior android version, and when it sees that you are not, it fails.
Click to expand...
Click to collapse
Well crap! im officially out of ideas... Best of luck to you, Im certain that with your phone able to boot into bootloader that its fixable
Ahh, well thanks anyway for trying to assist! Anyone else have ideas on how to fix this, or anyone else experience this before?
Assuming I cannot recover this, as it is slowly looking fairly unrecoverable, does anyone have a recommended JTAG service (Preferably in the US)? I'm not aware of any around my area. I did see a few online, but I'm unsure as to how trustworthy any of them are...
Did you try the roms listed here?
http://forum.xda-developers.com/showthread.php?t=1078213
Hmm. Without fastboot its tough to flash a rom, Did you try the factory data reset option in your settings, IS it showing error?
you're lucky i just did this last week.
seems that jerk flashed a gsm radio to that phone.
what you'll need to do is ODIN the phone to flash the CDMA radios back. you can find that HERE just follow the steps in that program and then you should be booting 2.3.4.
from there take the updates from sprint to get back to 2.3.7.
something about flashing a gsm radio hosed the MEID of my new phone, so keep that in mind. you may need to repair it afterwards before you can use it on sprint.
if you need help get back with me but that program should do the trick for you.
saranyan said:
Did you try the roms listed here?
http://forum.xda-developers.com/showthread.php?t=1078213
Hmm. Without fastboot its tough to flash a rom, Did you try the factory data reset option in your settings, IS it showing error?
Click to expand...
Click to collapse
Tried those; those were the ones listed on Peter Alfonso's Site (Who I assume is BuglessPete? Like I said, I'm new in this section ). Unfortunately the Odex/Deodex require signature verification to be off, and the other updates are only partial updates, so they make the presumption you are on the prior Android revision, and promptly fail signature verification if you are not, so yeah unfortunately none of those had worked :/
thedudejdog said:
you're lucky i just did this last week.
seems that jerk flashed a gsm radio to that phone.
what you'll need to do is ODIN the phone to flash the CDMA radios back. you can find that HERE just follow the steps in that program and then you should be booting 2.3.4.
from there take the updates from sprint to get back to 2.3.7.
something about flashing a gsm radio hosed the MEID of my new phone, so keep that in mind. you may need to repair it afterwards before you can use it on sprint.
if you need help get back with me but that program should do the trick for you.
Click to expand...
Click to collapse
Thanks much - I downloaded the program, ran setup.exe, installed all of it (Wow, this looks familiar from way back when I had a Samsung Moment, lol.). Threw the phone into download mode and waited. Unfortunately, it went downhill from here - It just sits there stating "Detect Port...", and shows disconnected. In Windows, under device manager, I went to view>devices by connection, then expanded out to my USB Port Hub. I don't show any devices there. So it seems that my phone is simply not being picked up by my computer - I did verify the USB cable I had was a data cable, and not a charge-only cable. And while hard to see them, the pin connectors in the charging port on the phone look good.
When I go into download mode (Or fastboot, for that matter), it shows the following on the screen, which I think is part of the cause of this issue:
"USB Control Init"
"USB Control Init End"
These happen right after one another. I'm not really sure why the USB controller wouldn't be working in this case, but I think whomever had the phone before me (in an attempt to fix an issue), decided to restore this phone back to stock using the I9020T files. I believe the Nexus S GSM variant may have a different USB controller in it, which is causing the drivers to malfunction on the CDMA variant, but I could be wrong. I haven't seem something like this occur before, lol.
Here are some fancy photos:
Download mode (Plus the error message given):
http://i.imgur.com/T4wOE.jpg
USB Port:
http://i.imgur.com/COAhb.jpg
Its an odd error, and looking online, some others who had it just had a bent usb port, but mine appears to be good, and all 5 pins look A-OK.
(Also, as a side note: Man, look a the viewing angles on that thing in the second shot, you can still see the error from the first pretty clearly. That is awesome.)
SoberSquid said:
Here are some fancy photos:
Download mode (Plus the error message given):
http://i.imgur.com/T4wOE.jpg
USB Port:
http://i.imgur.com/COAhb.jpg
Its an odd error, and looking online, some others who had it just had a bent usb port, but mine appears to be good, and all 5 pins look A-OK.
(Also, as a side note: Man, look a the viewing angles on that thing in the second shot, you can still see the error from the first pretty clearly. That is awesome.)
Click to expand...
Click to collapse
In download mode it should show up as a Samsung diag modem or something like that.
I'll bet it's your cord or usb port on your PC. Can you try a different port or cable?
Sent from my Nexus S 4G using xda premium
Tried different ports (And different computers, My linux box is the same) - I have also been through 3 different cords trying this. - That message comes up immediately, even if there is no USB cable connected.
SoberSquid said:
Tried different ports (And different computers, My linux box is the same) - I have also been through 3 different cords trying this. - That message comes up immediately, even if there is no USB cable connected.
Click to expand...
Click to collapse
are you seeing any com port at the bottom of the window? mine is com4
SoberSquid said:
When I go into download mode (Or fastboot, for that matter), it shows the following on the screen, which I think is part of the cause of this issue:
"USB Control Init"
"USB Control Init End"
These happen right after one another. I'm not really sure why the USB controller wouldn't be working in this case, but I think whomever had the phone before me (in an attempt to fix an issue), decided to restore this phone back to stock using the I9020T files. I believe the Nexus S GSM variant may have a different USB controller in it, which is causing the drivers to malfunction on the CDMA variant, but I could be wrong. I haven't seem something like this occur before, lol.
Click to expand...
Click to collapse
and don't worry about that error, mine says that too
No matter what I do, I cannot get the LG Support Tool to recognize my phone being plugged into the PC. I'm trying to do the new baseband install.
Running Win7 x86, already have the necessary files installed, getting to the last portion of the update, where LG support has to boot up, and it keeps telling me to install the driver.
I've downloaded the driver from the LG site, I already have the Nvidia driver installed on this PC. I plug in my phone and i see the P999 in the Device section of Manage Computer, has an exclamation point next to it so I search for driver automatically, no luck.
I don't know what the issue is.
dont do it automatically do it manually... and next time just post this in a thread already pertaining to this kind of stuff, less clutter the better.
mt3g said:
dont do it automatically do it manually... and next time just post this in a thread already pertaining to this kind of stuff, less clutter the better.
Click to expand...
Click to collapse
I've tried it manually, but no LG USB driver i've installed gives me a folder, it always is an EXE file.
Screw it, was reading that the phone needs a valid T-Mobile sim card. But my IMEI is blocked....sooooo this wont work for me.
Sent from my LG-P999 using XDA
watch a video on how to install it, I believe it is as easy as putting the folders in a dedicated folder (i have mine in a folder named "android") and just directing the files to the apx folder... not any .exe extensions
Are you currently running an ICS rom? I had the same issue but I flashed a rooted stock rom then I was able to get the LG tool to work. Might try that. Good luck.
The problem is that the USB driver is not recognized on my PC.
stevew84 said:
The problem is that the USB driver is not recognized on my PC.
Click to expand...
Click to collapse
I understood exactly what you meant. I had the same problem. The LG driver did not recognize my phone when I was running the Hellfire sandwich rom. The software did not detect that my phone was connected. I was beating my head on the desk trying to figure it out. Then I decided I would try restoring to a stock rom and try to pull the update. Restored to stock and no OTA update avail. So I went back to the LG software and it recognized it on stock. Still had CWM installed. All I had done was use the stock nand restore from here http://forum.xda-developers.com/showthread.php?t=1048274 If you need the file let me know and I will host it for you for a faster download.
Yatyas said:
I understood exactly what you meant. I had the same problem. The LG driver did not recognize my phone when I was running the Hellfire sandwich rom. The software did not detect that my phone was connected. I was beating my head on the desk trying to figure it out. Then I decided I would try restoring to a stock rom and try to pull the update. Restored to stock and no OTA update avail. So I went back to the LG software and it recognized it on stock. Still had CWM installed. All I had done was use the stock nand restore from here http://forum.xda-developers.com/showthread.php?t=1048274 If you need the file let me know and I will host it for you for a faster download.
Click to expand...
Click to collapse
Alright well thanks.
Good morning everyone.
First of all I want to apologize for my english, that I'm afraid it's very poor.
My question goes next: I bought an used Samsung Galaxy tab 2 7'' p3100 3G and it has a very big problem. It can't be connected to any pc, windows or mac. It's not a drivers' problem, so when the device is connected, the pc does nothing. Not even a display in the device manager, or a noise. However, it usually charges. I say usually because sometimes the icon battery shows a red ray, but it charges spending more time. That's all. It has been proved with three different original cables in several computers running different SO.
I don't know if it's a connector problem or it's a Rom one. It has an operator locked SO with Android 4.0.4 that not even shows the OTA update option in the menu. And I cannot select the way I want to be connected by usb in the "Storage" options.
The fact is I cannot update the device and I cannot root it in order to install a better rom or an original stock one.
I've googled all I can do to find a way for rooting the device, but all the roads drive me to the same point: Odin. The software I cannot use because my device can't be connected to any Pc.
I know this forum is my last chance. There are some ways like z4root or framaroot that work in another devices (Galaxy S for example, I think), but they have not been ported to my device. I think my chances are to make it by an apk o perhaps flashing a signed file from the original recovery.
I just need to install a simple clockword mod or having the device temporary rooted to install and run the Odin's apk that allows me to install a pre-rooted rom, an open recovery... Just a simple step for one man, But the Colorado's Canyon for me in my situation.
If someone of you know any solution or want to help me, I'll be truly grateful. And I didn't even mind to pay him for his help.
Thank you very much in advance.
Even_Flow said:
Good morning everyone.
First of all I want to apologize for my english, that I'm afraid it's very poor.
My question goes next: I bought an used Samsung Galaxy tab 2 7'' p3100 3G and it has a very big problem. It can't be connected to any pc, windows or mac. It's not a drivers' problem, so when the device is connected, the pc does nothing. Not even a display in the device manager, or a noise. However, it usually charges. I say usually because sometimes the icon battery shows a red ray, but it charges spending more time. That's all. It has been proved with three different original cables in several computers running different SO.
I don't know if it's a connector problem or it's a Rom one. It has an operator locked SO with Android 4.0.4 that not even shows the OTA update option in the menu. And I cannot select the way I want to be connected by usb in the "Storage" options.
The fact is I cannot update the device and I cannot root it in order to install a better rom or an original stock one.
I've googled all I can do to find a way for rooting the device, but all the roads drive me to the same point: Odin. The software I cannot use because my device can't be connected to any Pc.
I know this forum is my last chance. There are some ways like z4root or framaroot that work in another devices (Galaxy S for example, I think), but they have not been ported to my device. I think my chances are to make it by an apk o perhaps flashing a signed file from the original recovery.
I just need to install a simple clockword mod or having the device temporary rooted to install and run the Odin's apk that allows me to install a pre-rooted rom, an open recovery... Just a simple step for one man, But the Colorado's Canyon for me in my situation.
If someone of you know any solution or want to help me, I'll be truly grateful. And I didn't even mind to pay him for his help.
Thank you very much in advance.
Click to expand...
Click to collapse
Have you manually installed the drivers? If not, download the samsung drivers, install and try again. Read through the link below to find the drivers.
http://forum.xda-developers.com/showthread.php?t=2510669
cwyman said:
Have you manually installed the drivers? If not, download the samsung drivers, install and try again. Read through the link below to find the drivers.
http://forum.xda-developers.com/showthread.php?t=2510669
Click to expand...
Click to collapse
Unfortunately yes. I've tried with several versions of Kies, by installing manually the drivers and it doesn't work. The fact is I connect the device and the pc does nothing. Not even the device manager shows a new device or is alterated in some way. It's like one data pin in the connector was damaged or the rom was corrupted and it doesn't let the device be recognized.
I think my only chance is to make everything inside the device. By sd in the boot manager or with an apk. If not, I'm condemned to an obsolete device that could not even be updated.
Thanks for trying to help me.
Even_Flow said:
Unfortunately yes. I've tried with several versions of Kies, by installing manually the drivers and it doesn't work. The fact is I connect the device and the pc does nothing. Not even the device manager shows a new device or is alterated in some way. It's like one data pin in the connector was damaged or the rom was corrupted and it doesn't let the device be recognized.
I think my only chance is to make everything inside the device. By sd in the boot manager or with an apk. If not, I'm condemned to an obsolete device that could not even be updated.
Thanks for trying to help me.
Click to expand...
Click to collapse
This may sound absurd, but try a different version of the drivers. I had to install like a dozen drivers before it worked
mirzafran said:
This may sound absurd, but try a different version of the drivers. I had to install like a dozen drivers before it worked
Click to expand...
Click to collapse
I agree. The drivers can be so touchy. I'd uninstall and reinstall drivers numerous times before giving up. Good luck!
Sent from my GT-p511x
your cable is faulty. Get another one on ebay cheap.
I'm afraid I've tried with three different cables, as I said (one of them original from Samsung and new), two Windows Pc's, one mac and about fifteen different drivers.
Believe me: I've rooted with no problem more than twenty different devices (and jailbreaked another ones ) and this is the first time I cannot make it.
Think it's a hardware problem or a corrupted rom one. In both cases I have to root it by an apk or a flash from the sd.
Anyway, I appreciate very much your help, boys.
Even_Flow said:
I'm afraid I've tried with three different cables, as I said (one of them original from Samsung and new), two Windows Pc's, one mac and about fifteen different drivers.
Believe me: I've rooted with no problem more than twenty different devices (and jailbreaked another ones ) and this is the first time I cannot make it.
Think it's a hardware problem or a corrupted rom one. In both cases I have to root it by an apk or a flash from the sd.
Anyway, I appreciate very much your help, boys.
Click to expand...
Click to collapse
I'm in a similar situation with a Galaxy Tab 2 p3113tsyxar
It is not recognized by any computer, and my next step is to try another cord manana. Until then (hopefully) I've got a nice paperweight.
You have not rooted ur tab till now......so u have not played with your firmwares! So its better to visit a samsung store. If you have warranty then they will do it in free.(And your android will also get updated!)
If I helped you, just press thanks!
I've been browsing these forums all night and I for the life of me cannot just find a simple answer. This update came out a while ago and I had no idea about it, so hopefully someone can help me.
Literally, all I'm trying to do is upgrade to 4.2. I've never done anything at all to my phone, it's always been stock. I'm looking for help because the OTA won't work at all, it said I was on 4.1, so it checked for updates and downloaded like a 400mb file, and it turns back on and I'm still at 4.1??
I went to HTC's site and saw that I could just manually install it, but of course it's never that easy. I did all the steps exactly, but when it starts to download and gets to the black HTC screen, my computer always says it doesn't recognize it and can't install drivers (error 170), and then it fails to update. I've tried this on both machines that run windows 8.1. I feel like I've tried everything..I tried running it in different compatibility modes, run as admin, and then I read somewhere that you update it when you're on the fastboot screen. So I tried that but when I'm in the bootloader my computer doesn't recognize my phone at all.
I'm stuck on what to do at this point. I can borrow a computer that has windows 7 on it, if that would help at all. Any help is appreciated!
Not enough info. What carrier version is the device? What region/country are you in? What is your current software number (not Android version).
When you say "manually" update, I think you are talking about RUU. What is the RUU version (file name)?
WIndows 8.1 is probably your main issue with the RUU. Win 8.1 is not compatible with HTC drivers. Anything before 8.1 should work. But again, you need to provide more info.
Hey man thanks a bunch! I should've provided more info, although I just tried it using a windows 7 laptop and it worked with no issues thanks!