Database Info

Flashed US blackjack with i600 firmware cant flash back HELP

i flashed my blackjack over with the i600 carousel rom and it all went smoothly, i later noticed everything worked except for usb and bluetooth ive read around and noticed everyone mostly had just the phone not working but mine worked, anyways i tried to reflash back to my cingular rom and noticed it no longer said cingluar usb when i went into flash mode and the phone will appear for a short seccond as an unknown device on my pc and suddenly die. i cant flash back, i tried the flash fix rom and wasnt able to get anywhere with it without my phone communicating via usb. can someone help me my phone is useless now without usb/bluetooth

NOPE. there is nothing you can do at all. So say hello to your new brick. Someone did this in the excalibur thread. THERE IS NOTHING YOU CAN DO AT ALL. SHould have done some reading bro.

deviusdragger said:
NOPE. there is nothing you can do at all. So say hello to your new brick. Someone did this in the excalibur thread. THERE IS NOTHING YOU CAN DO AT ALL. SHould have done some reading bro.
Click to expand...
Click to collapse
i did read plenty but i made this flash around the time the rom first leaked out so there wasnt a "i bricked my blackjack" post to take notes on. the phone isnt a total brick though, everything works minus the usb option doesnt show up on the connection setttings, and bluetooth doesnt work. i guess ill try to sell it on ebay or something

no conclusive evidence of i600/i607 working after this!
though some have suggested using a serial cable (probably a Samsung D820 serial cable) to connect to the pc instead of usb and then reflashing the original rom, there is no conclusive evidence of the phone working.
You can try your luck with the serial cable. I am looking to buy one myself because I did the other way around, flashed a i600 with i607 WM6 rom and I ended up having an expensive paper-weight on my table.

NNagendran said:
though some have suggested using a serial cable (probably a Samsung D820 serial cable) to connect to the pc instead of usb and then reflashing the original rom, there is no conclusive evidence of the phone working.
You can try your luck with the serial cable. I am looking to buy one myself because I did the other way around, flashed a i600 with i607 WM6 rom and I ended up having an expensive paper-weight on my table.
Click to expand...
Click to collapse
its shocking how a phone as popular as the blackjack has little to no scene action, if this was an htc phone someone would have found a way by now

[Q] USB Connection Issues

Some time in the last 2 or 3 ROM flashes, my usb port has quit communicating. It will charge the phone, but never so much as gives me the usb connected tone on the pc. have tried numerous pcs that have worked in the past, 3 different cables that all have worked before, reinstalled drivers, tried adb, kies, odin, and mass storage to no avail. I have checked and unchecked debugging. Currently running MIUI, but was on phidelt82's EC10 combo rom before that with the same result. Anything I may be missing? I have run out of ideas, and none of what I am finding by searching seems to be helping.

snowgod76 said:
Some time in the last 2 or 3 ROM flashes, my usb port has quit communicating. It will charge the phone, but never so much as gives me the usb connected tone on the pc. have tried numerous pcs that have worked in the past, 3 different cables that all have worked before, reinstalled drivers, tried adb, kies, odin, and mass storage to no avail. I have checked and unchecked debugging. Currently running MIUI, but was on phidelt82's EC10 combo rom before that with the same result. Anything I may be missing? I have run out of ideas, and none of what I am finding by searching seems to be helping.
Click to expand...
Click to collapse
I went to settings then USB settings and changed my option to ask everytime. Now when I plug phone to usb cable the phone screen comes up to select media or mass, I select mass and the computer sees it.

No dice. Not sure what else to try, can't go back to stock, acts as if my usb port is charge only.
Sent from my SCH-I500 using XDA Premium App

Anyone have a package to get me back close to stock with clockwork (cant use Odin obviously) so I can take the phone in for a replacement?.

This is why you should back up your phone before flashing.

Thanks so much for your kind and helpful words. As it stands, I did back it up in Clockwork, but the phone will not read the backup now. At what point did these forums change from a place of information sharing and learning to a troll haven full of "Noob bashers"?

I had those same problems and I could never get my phone to recognize but I found one computer and xp machine that odin saw and I got it to work but my USB still doesnt work on any other pc (Weird). So just keep trying diff computers maybe it my show up

Thanks for the tip, will see what I can come up with

snowgod76 said:
Thanks so much for your kind and helpful words. As it stands, I did back it up in Clockwork, but the phone will not read the backup now. At what point did these forums change from a place of information sharing and learning to a troll haven full of "Noob bashers"?
Click to expand...
Click to collapse
No one is bashing anybody. Maybe you need to change the way you interpret things. If you'd reread your original post, you'll see you never said you made a backup and couldn't restore it. I was making a legitimate point to make sure in the future you made backups. I had no way of knowing you had.
Point is, my comment was legitimate; I was not bashing you, so don't be so quick to interpret things people say in the most negative connotation as possible.

Sorry, add, I too fell victim to your "hard" tone in many of your replies around the forums. I apologize for being quick to the trigger, as I can see where you are coming from in the piles of questions daily from folks who have never even thought to back up before flashing. As it turns out, I gave it a quick bricking, and a replacement with working usb is on the way. Pretty sure it was a hardware issue, as it was working one minute and gone the next with no changes to the phone.

Phone completely Dead

So I lent my brother my nexus s that had cm7 on it. He got into the clockworkmod, went to mounts/storage, and proceeded to format everything (bootloader, boot data, etc. everything in there) he said he thought that would fix the force closes, I figured no biggie, but now I can't even get the phone into download mode and I have no idea what to do, the phone will simply not turn on

wow.... dont even know why he would do that.
rule 1: dont lend people your phone.
and i dont know why you would try and get into download mode, Odin isn't the first thing you want to go to.
1. turn the phone off (if it isnt already)
2. hold volume up + power
... what happens? does bootloader mode pop up?
- plug your phone in your computer's USB
- does the sound for USB plugged in occur?
- does computer detect it?

Can't access fastboot.
Phone sometimes recognizes it and says this device is not recognized and it couldn't install the usb driver, sometimes when i plug it in it does nothing.
Didn't want to lend it to him, had no choice. I told him he should have just fixed the permissions on the phone, but then again he's not exactly android literate.

thats just dumb on his part.. i dont know why he would try and mess with your device. if it has problems, just ask you first.
its probably bricked if you cant access download or bootloader... definitely bricked if the computer is unable to detect it
your only way out of it is to get a replacement

In Device/Drivers of windows under Unspecified there's this:
SEC S5PC110 Test/BD
says drivers are not installed

Anybody out there with a solution?

I think there is more than one driver you can try, though I've never flashed anything in Windows (Linux already comes with the driver ), so I don't know for sure. I think I've seen people mentioned a few drivers before, try search for all the "brick" threads here.

Easiest solution might be to download a Linux live distribution (f.e. ubuntu) and run fastboot from there. No need to install any drivers.

Kicking him in the nuts will probably make you feel better... I don't know if it'll fix your phone though.

jruweaver said:
Kicking him in the nuts will probably make you feel better... I don't know if it'll fix your phone though.
Click to expand...
Click to collapse
lmao!!!!!!!!!!

KryPTiCk0d3 said:
lmao!!!!!!!!!!
Click to expand...
Click to collapse
While funny, it doesn't help one bit.

I would try the various methods to get into download mode and use Odin to fix it ...you might be screwed tho
Sent from my Nexus S using XDA App

SphericalPuma said:
While funny, it doesn't help one bit.
Click to expand...
Click to collapse
Unfortunately with the state your phone is in it is probably going to be the best advice you get.
Sent from my Nexus S using XDA App

http://forum.xda-developers.com/showthread.php?t=1000175
any chance that this could help you?

Ddi you ever get your phone sorted ? I'm now in the same situation !

Yes, hit up http://www.mobiletechvideos.com/blog/?page_id=970 For 50 bucks they'll fix your phone and ship it back to you in no time. They got my phone on a Friday, I got it back on either Monday or Tuesday. Of course they're based in Texas and I'm in STL so it could differ for you, but the point is, they're fast, reliable, and professional.

Thanks for that - I'm based in Ireland but I'll give them a shout and see if we can do business......

Thanks a million for the reference PUMA. Please contact me when you are in need of a brick fix. I fix hundreds of Galaxy S / Samsung / HTC variants and several others in a brick of nearly any scenario. I've devoted a lot of time to providing and almost unseen service to people in need versus parting the phone out or trashing it.

[SOLVED] No service, no imei, more info within...

Hello, thank you for reading this, to start with.
First off, here are the specs of the phone I am asking about:
Galaxy S 4G exclusive from T-mobile
Model #: SGH-T959V
Firmware: 2.2.1
Kernel:2.6.32.9
Build #: FROYO.VUVKD1
If that's not enough please ask.
Back Story: Phone was given to my ex by his mother. It was for T-mobile, which don't have good plans for pre-paid/pay as you go in my area. So I was asked to make it work for ATT. I rooted using Superoneclick, and then did the hex voodoo and unlocked the phone. It worked for a few months, no problem. There was no data plan so no phone internet was acessed, wifi was but only rarely. It DID work.
Then, the other day, my ex dropped it. It worked just fine for a minute or two, but now is stuck with no service, and such. No imei number. No phone number. Nothing. Searches for the provider. Sim card has been replaced just in case. I've restored and re-rooted, but i couldn't re-unlock the sim # as the hex editor couldn't find the code. AND the sim doesn't ask for an unlock code when inserted.
I have googled and searched my tushie off to figure this out. All my answers are bad flashing of roms and such, and the last anything that was done to it out of ordinary use was me unlocking it, and it worked for months.
Keep in mind that i haven't a clue what flashing a rom means, or what odin is (i read that several times, haven't a clue what it is), and I know how to follow step by step instructions as long as they use reasonably understandable terms to the android nooblett.
I am currently running on an ubuntu laptop, so downloading and running anything means I download, put it on a flash drive, and install it or run it on a windows computer that doesn't have internet access (long story, i'm rambling as it is).
Some extras:
I did not do any backups, because everything worked for the longest time anyways.
I've tried a few things involving nv_data.bin and the like, but it seems they don't exist or are hidden from my silly self.
I have to re-root and such as I've just performed a factory reset to see if that would fix the issue.
I am extremely tired so I'll likely do nothing tonight, including responding, as I have to work tomorrow and lots of other things.
I am a rambling idiot, feel free to mock me for it, but i do try and give out as much information as I can.
Any questions? If not, please, please, please tell me an answer that doesn't involve sending this phone back, because it's long out of warranty and has passed through many hands (the previous people did not like t-mobile either...).
And thank you for reading the ramblings of this idiot.

Are you sure it's not a hardware issue? I dropped my old iPhone 3G and it stopped recognizing my SIM unless it was placed just right. Have you tried any other SIM cards in there? Take a look at my SGS4G carrier unlocker (link is in my signature) and see if it scans through your nv_data.bin file correctly. I never liked that people encourage direct editing of that file. :/

Have you tried seeing if Samsung Kies mini will recognize your phone? Since you still seem to be on factory stock and did a factory reset.... download Kies mini, plug your phone in and see if it will recognize it. Kies mini - in case you are unaware is Samsung's software to update our phone.
If it recognizes your phone - try to do the upgrade to Gingerbread. If it will upgrade to Gingerbread, it might rewrite your efs folder - which is where the IMEI and phone information is stored. If it doesn't rewrite the efs folder... it shouldn't matter if your phone is out of warranty as Kies mini - you will say and not mention the other stuff you have done - messed it up during the upgrade... which is happening to people more than you would think. Take it back to where you purchased the phone and give it a shot. Or try contacting Samsung. Many have done that as well. You need a computer you can download Kies mini to and do the upgrade... in other words - a computer with internet access you can work on.
o You may start with another Factory Reset
o Download Kies mini if you do not already have it. < - - Click link here for Kies mini - When you follow this link you will see two tabs - 'Manuals' and 'Software' - click software and download.
o Make sure your phone is charged.
o Make sure USB Debugging is off.
o Start Kies mini on the computer.
o Make sure phone is not connected to computer yet.
o In USB Settings on phone select ‘Kies (Firmware update)’ if it is not set to ask every time.
o Plugged in phone, let device drivers install on computer. You will see a notification on your computer when complete.
o Then Kies mini will recognize the phone.
o Hit upgrade and wait.
o Phone will eventually reboot. Check your IMEI.
---------- Post added at 05:32 AM ---------- Previous post was at 05:26 AM ----------
FBis251 said:
I dropped my old iPhone 3G and it stopped recognizing my SIM unless it was placed just right. Have you tried any other SIM cards in there?
Click to expand...
Click to collapse
You owned an iPhone FB? Damn!
FB is one of the best on here... however, if you are on stock you should try an upgrade if Kies mini will recognize your phone. I have read flashing stock - in this instance via Kies mini - has many times rewritten the efs folder for people with IMEI problems. Either way - if he is on stock everything he can take it in to T-Mobile and ask for you?
Thoughts on that FB?

lumin30 said:
You owned an iPhone FB? Damn!
FB is one of the best on here... however, if you are on stock you should try an upgrade if Kies mini will recognize your phone. I have read flashing stock - in this instance via Kies mini - has many times rewritten the efs folder for people with IMEI problems. Either way - if he is on stock everything he can take it in to T-Mobile and ask for you?
Thoughts on that FB?
Click to expand...
Click to collapse
I still have it lying around and it's bricked. I wanna try flashing it again with another USB cable but I can't find my spare.
Hmm, haven't ever tried the kies mini approach but it's worth a shot, especially if it'll restore the /efs directory.
If it IS fully stock, then yes take it in to T-Mob and see if they'll give you a replacement and next time don't go editing anything in /efs directly.

Thank you everyone. I will try these things later today. Like I said the only things I've personally done to it are root and unlock. I dunno what happened and its possible it could be hardware, but ill try updating it through kies first. Again thank you, ill keep you updated on what happens.

RamblingIdiot said:
Thank you everyone. I will try these things later today. Like I said the only things I've personally done to it are root and unlock. I dunno what happened and its possible it could be hardware, but ill try updating it through kies first. Again thank you, ill keep you updated on what happens.
Click to expand...
Click to collapse
Hi,
If the problem is solved for you please edit the title in the OP and add [SOLVED] to it
10x

Ok Guys/Gals, I'm stumped...
Followed the instructions. Mini Kies on computer that works with it (windows vista 32 bit), waited til kies told me to plug in the device. I did. Drivers installed. I waited. And waited. And waited. And waited a bit more. Then it pops up for me to enter a pattern. No pattern had been established with that phone before. So I set one up on the phone, and redid all that, thinking that's all I had to do. Asked me for the pattern again, I put it in.
Here are the steps i'm taking.
Mini kies asks me to plug in my phone.
I do it (this is the phone in the thread, not my actual phone).
And I wait. A while, actually. Somewhere in the line of 1-5 minutes.
And now i get a little popup. "Pattern" the header reads. "The mobile phone is locked. To connect, use the mouse to enter the pattern as specified by the mobile phone." Followed by the pattern unlocker.
I place the pattern i created on the phone in to the one on the computer. It must not be right (as there was none to begin with, and i had to create new and redo this whole step) because now it reads:
Firmware version: device cannot be upgraded
Firmware upgrade: (this is a blank nothingness)
Agh, don't get me wrong, i love this stuff, but after dealing with a defaulty U-scan computer all day (i am a cashier...), computers are not on my good list.
Please help ?

Ok, so after hours of crying, moaning, cursing, yelling at the phone, cursing SD cards for being so small, cursing the better phone for being more retarded than it's cheapo brother the Prevail, I fixed it.
I was so frustrated, i reset everything, again. Still wouldn't work with kies. Checked everything. Made sure I was doing everything right. Googled every last letter i could find about my issue.
I wanted to throw the phone, but instead, i took the battery out, the sim card out, and the SD card out, and cursed each and every one of them out. Before I continue, let me say, that I'd done this before, for approximately the same time, if not longer. Then, i threatened their inanimate lives and put them back, and tried to do the kies update. Turned on the phone, not expecting any miracle of any sort. Suddenly the phone's alive with all sorts of missed calls and texts and who knows what else. So while the phone is no longer rooted, it's still unlocked, and works like a dream again.
TL;DR version? Took the battery, sim, and SD card out for a while. Even though I'd done this as the first thing i did when this issue started happening, perhaps yelling at them made the difference.
Thank you all for putting up with me and my rambling idiocy.

Awesome, glad you got it working again. Maybe we need to put "threatening sdcard/SIM card" methods into the wiki...

stephen_w said:
Awesome, glad you got it working again. Maybe we need to put "threatening sdcard/SIM card" methods into the wiki...
Click to expand...
Click to collapse
Stephen
I threaten my phone with a trip to the recycling yard all the time. It works.
And to the OP glad you got it figured out. A few people with the imie issue have used the pull battery wait ten approach and it seems to work.

Glad you fixed it.
I strongly suggest you make a copy of your efs folder in case you have an IMEI issue again. I keep a copy of my efs folder on my external sdcard and my PC.

[Q] HELP! Need to Root NS4g w/o computer! pwease? 8)

I'm not new to android whatsoever.. I've just returned from an Iphone 4s cause i was missing the openess of android. Now.. i've pulled out my old Nexus S 4g, Updated it to 4.0.4 and i cant get it to connect to my computer for the life of me! tried 4 different cables, 5 different computers, every driver i could find and nothing. I've come to believe this is a software failure... All i need is root and i will be able to sleep at night. Could someone package up .zip to give root and twrp recovery that i could flash through stock recovery? I dont know else i could do to get root... but this problem is becoming quite annoying.

1. There is no way to package a zip to flash through stock recovery since it would have to be signed.
2.For someone who is "not new to android whatsoever" making 2 threads about the same topic 2 minutes apart isn't exactly acting the part.

Try this guide.

Actually you're wrong, On the Epic 4G someone did in fact manage to do so. And yeah since i'm not new to these forums i understand that stuff like this gets overlooked so i made two posts. Cry me a river.
BTW Thanks harb... but that would involve being able to connect to my PC. Which just is not possible right now.

Thats the Android Karma... it happens but a little advice.
If you can't connect to the computer then it might a hardware issue not software.
If getting root was that easy that you just had to flash a zip on stock then everyone would be doing it. And good luck getting root without unlocking your bootloader first. Not to be rude but the problem could possibly be between the computer and the chair.

robogoflow said:
Thats the Android Karma... it happens but a little advice.
If you can't connect to the computer then it might a hardware issue not software.
If getting root was that easy that you just had to flash a zip on stock then everyone would be doing it. And good luck getting root without unlocking your bootloader first. Not to be rude but the problem could possibly be between the computer and the chair.
Click to expand...
Click to collapse
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?

grumpySasquatch said:
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?
Click to expand...
Click to collapse
Bro... Chill... They're just trying to help you out. There is NO way to to root your NS without a computer (currently. We are not Epic 4G owners here). You said you didn't use your NS since GB, SO during the time in between something could have happened to the hardware. Don't rule that out just yet. Your drivers might also be bad. Is this what migrating to iOS does to people? Makes them snobby and demand fixes to problems they can't figure out on their own? Don't hate on the XDA forums. If we're not helping you "hit the thanks button anyways, you ungrateful bastard" (XDA into video ). Anywho. Chill. Keep trying.
Nexus S (GSM i9020a)
Paranoid (14.a Hybrid - 4.0.4)
Matrix Kernel (CFS - 20.0)
Intellidemmand (800/100)
Live OC (105 - 800/1000)
Deep Idle (On - Noop)
BLX - 96 (Inverted Apps)

I am chill, i am just trying to describe what I've already done so maybe someone could suggest something else. And no what i meant is i downloaded the OTA on my computer than transferred it onto my Nexus through USB mount a couple of days ago so i know its not a hardware issue. Im not demanding fixes, just trying to see if anyone has done been able to figure this out yet as i know im not the only one with this issue. And there is a big problem w/ people on the XDA forums as a whole.. i am a little frustrated and just dont like when someone is telling me is a User issue when i have tried everything conceivable and know what i am doing.. Sorry if this offended you. and IOS is a good device.. its just like.. NWO they want to control everything haha. I'd rather be part of the rebel faction. even though i love my ipad XD

There is currently no way to root 4.0.4 without an unlocked bootloader (and no custom recovery), and the only way to get an unlocked bootloader is to either have root or plug it into the PC and unlock via fastboot. As such, you are stuck with sorting out drivers - despite how annoying they are.
The video i linked to above describes in detail (and through video) exactly how to sort out NS drivers on Windows machines as well as the required fastboot commands to get a custom recovery.

Harbb said:
The video i linked to above describes in detail (and through video) exactly how to sort out NS drivers on Windows machines as well as the required fastboot commands to get a custom recovery.
Click to expand...
Click to collapse
Yes that is a good video, and does a job well done in describing on how to install drivers. My main issue is that my Computer(s) are'nt recognized my device at all... It doesn't show up as android device, or nexus s... but Unknown device. If i could figure this out i believe i could handle the rest.

grumpySasquatch said:
Yes that is a good video, and does a job well done in describing on how to install drivers. My main issue is that my Computer(s) are'nt recognized my device at all... It doesn't show up as android device, or nexus s... but Unknown device. If i could figure this out i believe i could handle the rest.
Click to expand...
Click to collapse
Pretty sure that video describes that. You need to open up device manager, double click unknown device (while device is in fastboot), hit update driver and navigate to the provided drivers on the site. Watch it a few times, you'll figure it out.

Have you tried to install PDANet? I've read numerous times about it working wonders for users who have trouble with drivers. It has all of the necessary drivers built in.
Sent from my Nexus S using xda premium

d_phekt said:
Have you tried to install PDANet? I've read numerous times about it working wonders for users who have trouble with drivers. It has all of the necessary drivers built in.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
yes i second that,PDANet Drivers usually work across all devices you should try them.

Like ppl said before, try PdaNet drivers it might help.

thanks everyone, , but like i said i tried pretty much every driver you can find online. they will not install as my device comes up as "Unknown", i've literally tried every piece of literature on the web relating to this issue... at this point i'm just going to wait for the JB update and see what happens.

grumpySasquatch said:
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?
Click to expand...
Click to collapse
So the ICS update makes you unable to boot to fastboot and makes your device unable to be recognized by your computer from there?
That's a new one. As far as I know, "Unknown device" is actually your device being recognized, just the driver doesn't get installed correctly.
Have you tried manually specifying which driver to install and selecting the PDA Net driver? Look at Harbb's last post.
Have you went as far as editing the drivers inf to match your hardware ID? I know I had to do that way back when the PDA net drivers weren't even available.
'til then, user error.

polobunny said:
Have you tried manually specifying which driver to install and selecting the PDA Net driver? Look at Harbb's last post.
Have you went as far as editing the drivers inf to match your hardware ID? I know I had to do that way back when the PDA net drivers weren't even available.
'til then, user error.
Click to expand...
Click to collapse
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?

Epic 4G could do this in FROYO... It was patched by google in 2.3+. Do you want an app to secretly root you and install malware?
Sent from my Samsung Epic 4G using Tapatalk 2

grumpySasquatch said:
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?
Click to expand...
Click to collapse
Well it is going to be basically one of two things.
1. Is user error of some sort. That is what people have been trying to help with.
2. Is hardware issue that no one can help you with of course. Or some software issue causing it to not show up for who knows what reason. Neither of which folks can help with since a computer is not seeing it. So they revert back to what they can. Point 1
When you asked a question like is there a zip that you can flash in stock recovery to give you root or custom recovery that also doesn't help your cause for people assuming user error.
The one other thing you can try is download mode and Odin.

grumpySasquatch said:
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?
Click to expand...
Click to collapse
Cool. Trash your Nexus S, clearly broken.
Edit: That's nice of you albundy, but Mr grumpySasquatch (fitting name eh?) has tried everything, including modding the drivers inf. His Nexus S is broken beyond repair, also the first one we've ever seen that won't adb but works fine for USB mounting. *chuckle*