Database Info

[Q] Tried to Install MIUI, Now Stuck

Welp I am one of the stupid ones and installed MIUI on my Infuse, and like everyone else, I'm stuck on the boot screen. I looked at the post on the same topic and tried to do it but couldn't get it to work probably becuase the computer says that its an Unknown device instead of a Samsung device.
So my question is what do I do now that my computer doesn't recongize the phone as a device anymore?
Thanks to all that can give help.

http://forum.xda-developers.com/showthread.php?t=1116251
And lesson learned - never install a ROM from another phone.

Yeah I know that now. Foolish mistake I know I shouldn't have made.
But, I have tried using that but when I connect the phone to the computer it shows to be an unknown device and Odin doesn't pick it up at all. My problem is, is that the computer doesn't recognize it as an Android Device anymore. Is downloading the drivers from Samsung going to help?

I'll have to leave that to someone else - I use Heimdall on a Linux box, I've never flashed from Windows.

Oh, ok. Well thanks for your help .

I fixed my problem. What I had to do was get another computer that doesn't have the Samsung Drivers or Kies installed and then install them. Once that was done Odin found the device and I was able to restore it.
So there's a tip for anyone who can't get their device to be recognized by the computer or Odin itself.

Or just uninstall/delete those drivers?

Entropy512 said:
I'll have to leave that to someone else - I use Heimdall on a Linux box, I've never flashed from Windows.
Click to expand...
Click to collapse
i have started to do this to since i got the infuse. ill tell you i dont miss driver issues one bit! linux/bsd/mac/whatever rock as long as you have supported hardware and that is becoming less and less of a problem these days.

re: Now Stuck
You need to try and pull the battery out and put it back see if you can get the phone into "download mode". If you cannot get it into download mode by doing that or using the up/down volume and power key combo then I would suggest that you purchase a "jig" on ebay. (they cost under $10 bucks shipped).
Here is the ebay link for the jig:
http://cgi.ebay.com/Samsung-Galaxy-...0563626533?pt=Cell_Phones&hash=item20ba3eba25
With a jig all you would need to do is to remove battery, plug the little jig into the usb port of phone and replace the battery, then wait 5 seconds or so and the phone will be in download mode allowing you to use Odin3 and flash back to "stock rom" to start with..
Best if you did that using the "Ultimate Unbrick" stock froyo rom after that
you can install infuse 1.5 custom rom or Bionix or the defused custom rom or any other rom.
Here is the link for the Ultimate Unbrick:
http://forum.xda-developers.com/showthread.php?t=1116251
Good luck.

nstong said:
Or just uninstall/delete those drivers?
Click to expand...
Click to collapse
I tried that but it didn't work on my computer, but that's just my computer that could work for someone else. If that doesn't work though, you can get another computer and install the drivers on them and that should work.

SamsTechAnswers said:
I tried that but it didn't work on my computer, but that's just my computer that could work for someone else. If that doesn't work though, you can get another computer and install the drivers on them and that should work.
Click to expand...
Click to collapse
Where are you trying to uninstall the drivers from? I have windows 7 and went to device manager or whatever and took it off there. Then reinstalled kies, worked perfect after.
Sent from my SAMSUNG-SGH-I997 using XDA App

Entropy512 said:
http://forum.xda-developers.com/showthread.php?t=1116251
And lesson learned - never install a ROM from another phone.
Click to expand...
Click to collapse
and.... do not touch if it works properly

I guess this is a good sign. Our phone is gaining popularity because new people are buying it and trying dumb things with it

Please help me with download mode!!

Hello, i am currently trying to root my sisters galaxy s 4g... Her Baseband is T949VUVKI1. Firmware is 2.3.5, Build Number is GINGERBREAD.VUVKI1. i remember flashing her phone to 2.3.5 and download mode working perfectly fine, and for some reason it wont go into download mode at all... the computer is not recognizing her phone either. YES, i do have usb drivers installed otherwise my galaxy s 4g wouldnt be recognized on my computer(odin specifically, not turning yellow). Please help, i have searched everywhere in the internet and tried almost everything... Volume up and down and plug charger, batter out volume up and down usb and battery in etc. PLEASE HELP!! Thank You in Advance.

Nvm
10c

1. Try reinstalling to drivers. Also make sure you're using the same USB port as Windows can be funny about it it sometimes.
2. if download mode is being difficult, go download the Android SDK from www.android.com. Install it, run it, and only download the platform tools. When that's done, open a command promt, CD to where the plaform tools installed (either c:\program files\Android\Android-sdk\platform-tools or c:\program files (x86)\Android\Android-sdk\platform-tools ), then issue the command: adb reboot download.
3. I suggest you check the dev section for bhundven's one-click collection. Uses Java and Heimdall vs. ODIN and works easily.
Sent from my SGH-T959V using XDA App

i have this issue 2.3.5 messed me up. Odin sees my phone in debug mode but not in download mode...using odin 1.85 sinse it is the only version that responds to my phone at all. help please!

Tytan0007 said:
i have this issue 2.3.5 messed me up. Odin sees my phone in debug mode but not in download mode...using odin 1.85 sinse it is the only version that responds to my phone at all. help please!
Click to expand...
Click to collapse
Get it back into download mode, go grab a bhundven's one-click. The one-clicks utilize Heimdall vs. ODIN, which means they use open-source USB drivers instead of the proprietary Samsung drivers. See if that enables the computer to see the phone. If so, flash the one-click

Should I uninstall the samsung drivers prior to using Heimdall's One-Click?

Tytan0007 said:
Should I uninstall the samsung drivers prior to using Heimdall's One-Click?
Click to expand...
Click to collapse
That's a good idea. Some people have reported conflicts between the drivers.

Why would only Odin 1.85 see my phone in USB Debugging and not in download mode? And all other Odin verisions never see my phone, no matter what state it is in... I am at work so I will give the one click another try when I get home. I never thought of uninstalling the Samsung drivers prior to install; however, I did use the one click method to no avail. However, Heimdall's one-click was able to see my device it just kept giving me a driver error. This is so crazy it might just work.

Tytan0007 said:
Why would only Odin 1.85 see my phone in USB Debugging and not in download mode? And all other Odin verisions never see my phone, no matter what state it is in... I am at work so I will give the one click another try when I get home. I never thought of uninstalling the Samsung drivers prior to install; however, I did use the one click method to no avail. However, Heimdall's one-click was able to see my device it just kept giving me a driver error. This is so crazy it might just work.
Click to expand...
Click to collapse
I wish I had a good answer. ODIN's a funny animal. I've been fortunate and not had any problems with it. I am hoping you are correct - maybe it was just a driver conflict. Let me know how it goes.

didn't work...

You could try downloading a terminal app from the market. Open the terminal and type:
reboot download
See if that does it.

***Update***
Okay, so Oneclick was not working at all no matter what I did with the drivers. However, in all my tinkering with it I installed the Samsung Driver, the Open Source one, and some gadget driver as well from oneclick.
Doing this put all these drivers in my computer. Then I went into my Device manager (Win 7) and looked at my USB driver and I uninstalled everything and went to the stock win 7 usb driver. Then I plugged my phone in and my computer began searching for drivers for this device when it decided that it would be a good idea to load all three drivers at once and voila my phone was then showing up on ODIN 1.85.
I then proceeded to flash my phone with a rom, probably the wrong one considering I was coming from 2.3.5 and my phone boot looped and then soft bricked(sorry if I used these term incorrectly, noobin it).
After, some nervous moment of scouring XDA I found the god-send of a post on getting in to download mode, using odin, and flashing stock 2.3.6 - thank you Raver(I believe). When I did this, my phone magically started obeying ODIN like a devout viking and is now running 2.3.6 superbly.
Keeping with my phones newly found viking heritage, I intend to figure out how to properly root it, update the kernal and modem(not sure which one is best), get CWM, and subsequesntly put in Valhalla Black.
Seeing as though this last rendevous with flashing caused me a little scare I may hold off and wait to see what the next big update is (maybe a port ICS variant) and then go with that.
Anyway, thank you Stephen for helping me out with this and to everyone in this post.

Here's some reading for you Tytan,
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G#FAQ_.28with_answers.29
PS: Unless you wanna brick your phone, do not flash anything that isn't intended for the SGH-T959V Samsung Galaxy S 4G. You're saying you wanna flash a Vibrant ROM. You can, if you want an expensive paperweight. Happy flashing!

2.3.5 may have been for vibrant...yeah I think I got lucky. I did it prior to knowing about xda.
Sent from my SGH-T959V using XDA App

Tytan0007 said:
didn't work...
Click to expand...
Click to collapse
How are you getting into download mode?
There was a post in another thread where the person apparently was using the power menu to get into download mode or maybe the adb command.
Have you tried both the old fashion volume +/- and plug in usb cable? Or the adb command?
Do you have access to another computer? Believe it or not sometimes just changing computers will make the difference.
Weird when I replied there was no posts other than the ones on the first page...oh well glad its working now.

[Q] Stuck in a weird place

Hi, I tried reflashing zeus on my infuse after getting tired of AEON, but instead I ended up flashing cm7 onto my phone, now i cant get it past the samsung screen. Its not like the infinite boot loops where it flashes on and then resets, it just sits at the samsung screen. I have already tried deleting all caches reflashing to ZEUS, AEON, and CM7, nothing works, i cannot get past the samsung screen. Luckily i can still get to the recovery menu which means something still is working.
My question is, what do I have to do? I dont mind going back to stock but I dont know how to go about doing it. Another problem I have is that my phone cannot ( from my point of view) connect to a computer. Ever since I rooted my phone I cannot connect my phone or sd card to my computer.
Someone Please Help.

There is a whole section on how to return to stock (Factory / Return to Stock at the beginning of the following:
http://forum.xda-developers.com/showthread.php?t=1610374
Do a little reading. I find Heimdall the easiest, others prefer Odin.

Yeah, what he said. Me, I use Odin, with unbrick root 1.1 then flash again with a cwm root extras, getting me out of that stock recovery 3e I think it's called.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

psal217050 said:
There is a whole section on how to return to stock (Factory / Return to Stock at the beginning of the following:
http://forum.xda-developers.com/showthread.php?t=1610374
Do a little reading. I find Heimdall the easiest, others prefer Odin.
Click to expand...
Click to collapse
Heimdall Odin and computer in general doesnt acknoweldge that my phone is plugged into the computer no matter what usb port I plug into, I can give them a shot again but I tried odin yesterday and It didnt do anything...
Edit: Just tried Heimdall and odin again to no avail, the computer does not nor has ever recognized that the phone was plugged in, and just to make sure I used my laptop and my desktop and neither of them could connect to my phone.... looks like im screwed......

Javelin177 said:
looks like im screwed......
Click to expand...
Click to collapse
Not by a longshot.
For Heimdall, a lot of people have reported problems but the suggestion is perserverence.
First make sure you read and follow the instructions very carefully.
Try with different ports on your computer (ok, you did this one).
Try with different computers.
Try with different cords.
Perhaps unload and re-install the drivers.
Post back here what kind of things you are seeing.. which step looks like it isn't responding as expected.
If you really can't connect using Heimdall (and I can understand how hopeless that can seem... been there myself), you still have a lot of options because you said in your first post you can boot into recovery. .
That means there is a lot of stuff you can flash.
Ethereal, Aeon are good stable GB custom roms and easier to flash than the stock one.
For stock, you might try to flash dman's stock UCLB3:
http://forum.xda-developers.com/showthread.php?t=1508619
The complicated part of dman's stock UCLB3 is the stuff in there about video I don't quite understand (*)
To get video back, you have to put the stock kernel back in (disable lagfix first!). The stock kernel will make you lose CWM but not root.
Then you can flash a custom GB kernel (Entropy's DD or Zen's Infusion) to get back CWM.
(*) Here's the part I don't understand: When we go back to custom kernel, do we still have the video or does it get lost because we no longer have the stock kernel ?
If anyone can clarify that one point, I'd be grateful.

electricpete1 said:
Not by a longshot.
For Heimdall, a lot of people have reported problems but the suggestion is perserverence.
First make sure you read and follow the instructions very carefully.
Try with different ports on your computer (ok, you did this one).
Try with different computers.
Try with different cords.
Perhaps unload and re-install the drivers.
Post back here what kind of things you are seeing.. which step looks like it isn't responding as expected.
If you really can't connect using Heimdall (and I can understand how hopeless that can seem... been there myself), you still have a lot of options because you said in your first post you can boot into recovery. .
That means there is a lot of stuff you can flash.
Ethereal, Aeon are good stable GB custom roms and easier to flash than the stock one.
For stock, you might try to flash dman's stock UCLB3:
http://forum.xda-developers.com/showthread.php?t=1508619
The complicated part of dman's stock UCLB3 is the stuff in there about video I don't quite understand (*)
To get video back, you have to put the stock kernel back in (disable lagfix first!). The stock kernel will make you lose CWM but not root.
Then you can flash a custom GB kernel (Entropy's DD or Zen's Infusion) to get back CWM.
(*) Here's the part I don't understand: When we go back to custom kernel, do we still have the video or does it get lost because we no longer have the stock kernel ?
If anyone can clarify that one point, I'd be grateful.
Click to expand...
Click to collapse
Well heres the thing, when i first screwed up I tried flashing back to Zeus or AEon, problem was it would go through all fine and dandy and I would get happy thinking I have a phone again, but then when I rebooted it sat at the samsung screen, which i figured it would do, so I left it over night so it could set itself up like it usually does after flashing to a new rom. It sat over night and didnt move off the samsung screen, both with Aeon and Zeus.
Another thing too is that I thought if I partitioned the sd card and then worked off a fresh partition, I could get past the screen and then upartitiion and reflash the whole thing... Now my phone won't mount the sdcard, it doesnt recognize the sd or the sd-ext, tried mounting, manual mounts and everything. I even tried reformatting the external sd, to see if that would help. It didnt....
So the question is now... am I now screwed???
tl;dr... Phone cannot connect to computer to use heimdall or odin, wouldnt boot into new rom after flashing three or four times, and now the sd card wont mount... screwd :crying:
edit: It might not even be worth fixing because I think im going to get the nexus 4 on wednesday.... but I still would like to fix it if I can. Thanks guys for helping me so far through these tough times hahaha

(*) Here's the part I don't understand: When we go back to custom kernel, do
we still have the video or does it get lost because we no longer have the stock
kernel ?
If anyone can clarify that one point, I'd be grateful.
Click to expand...
Click to collapse
The post from Dman predates the video and MHL-HDMI out fixes that Entropy512 provided. The current Entropy DD and Zen Infusion kernels have the same video and MHL support found in the stock UCLB3 kernel.
Note that if you are coming from a JB ROM, you need to flash an Odin or Heimdall package with a PIT file to get the stock partition config back. They can be found here:
ODIN - http://forum.xda-developers.com/showthread.php?t=1705260
Heimdall - http://forum.xda-developers.com/showthread.php?t=1524081
Either will return your phone to stock after which you can ODIN or Heimdall a custom kernel and flash a custom ROM. If you flash the ODIN package with root you can also use SGS Kernel Flasher to flash a new kernel zImage file.

Zen Arcade said:
Either will return your phone to stock after which you can ODIN or Heimdall a custom kernel and flash a custom ROM. If you flash the ODIN package with root you can also use SGS Kernel Flasher to flash a new kernel zImage file.
Click to expand...
Click to collapse
But like I said just a few minutes ago, I can't even get heimdall or odin to recognize the phone. Even before All of this started happening, my computer would not recognize my phone, or my sd card.

You said you used a different PC or laptop. Did you try a new cable? I had a cable that didn't read correctly, switched to another and was able to flash.
Sent from my SGH-I997 using xda premium

psal217050 said:
You said you used a different PC or laptop. Did you try a new cable? I had a cable that didn't read correctly, switched to another and was able to flash.
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Yup. I have used three different usb cables: Two OEM's, and one After market.

You may have an issue with your Infuse drivers on your PC.. to fix this:
1 - uninstall all existing Samsung Infuse drivers using control panel/programs and features - this would include "kies", "kies mini" and/or "SAMSUNG USB Driver for Mobile Phones"
2 - remove any remaining devices from control panel/device manager
2a - as part of this you may need to look at hidden devices. To do this you will need to add a system environment variable (from control panel/system/advanced) called "DEVMGR_SHOW_NONPRESENT_DEVICES" and set its value to "1". Then from device manager "view" menu select "show hidden devices"
2b - Look for devices under "Universal Serial Bus devices" and "Universal Serial Bus controllers" that are named "SAMSUNG USB Composite Device" or "SAMSUNG Android USB Composite Device" and remove
3 - you might need to reboot after removing drivers and associated devices (recommended)
4 - reinstall Samsung Infuse drivers... (do not use the link in the ODIN thread)
4a - kies mini is available here:
http://org.downloadcenter.samsung.c...ATT_I997_Infuse_4G_Kiesmini_1.0.0.11084_3.exe
or from here (downloads/software):
http://www.samsung.com/us/support/owners/product/SEG-I997ZKAATT
(you may have better results using the "driver only" option at the second link - the smaller of the two files. Kies can sometimes cause problems of its own).
5 - once installed and rebooted, connect your phone (booted into phone OS with USB Mass Storage mode enabled and then USB Debugging enabled) and validate connectivity using ADB or by mounting to PC as a USB storage device. Test by copying a decent sized file to/from the phone.
6 - if this works, boot into download mode and retry Odin or Heimdall packages. If you don't have Java Runtime Environment installed make sure you install that first. For Heimdall (and maybe Odin) make sure to right click the file name and run as administrator.
---------- Post added at 01:38 PM ---------- Previous post was at 01:36 PM ----------
Or... If you are still in the middle of a CM7 install, you may just need to complete the install by booting recovery, wiping system and flashing a second time as shown in the install instructions here:
http://forum.xda-developers.com/showthread.php?t=1311960&highlight=cm7
Either way, good luck!

I thought cm7 required a double flash...just like ICS does if coming from GB...
So flash
Get stuck at Samsung screen
Boot to recovery
Re flash
reboot
Enjoy?
Could be wrong though as I never used cm7...but I remember reading that our idea to double flash for ICS came from cm7
Sent from my SGH-I997 using Tapatalk 2

Zen Arcade said:
You may have an issue with your Infuse drivers on your PC.. to fix this:
1 - uninstall all existing Samsung Infuse drivers using control panel/programs and features - this would include "kies", "kies mini" and/or "SAMSUNG USB Driver for Mobile Phones"
2 - remove any remaining devices from control panel/device manager
2a - as part of this you may need to look at hidden devices. To do this you will need to add a system environment variable (from control panel/system/advanced) called "DEVMGR_SHOW_NONPRESENT_DEVICES" and set its value to "1". Then from device manager "view" menu select "show hidden devices"
2b - Look for devices under "Universal Serial Bus devices" and "Universal Serial Bus controllers" that are named "SAMSUNG USB Composite Device" or "SAMSUNG Android USB Composite Device" and remove
3 - you might need to reboot after removing drivers and associated devices (recommended)
4 - reinstall Samsung Infuse drivers... (do not use the link in the ODIN thread)
4a - kies mini is available here:
http://org.downloadcenter.samsung.c...ATT_I997_Infuse_4G_Kiesmini_1.0.0.11084_3.exe
or from here (downloads/software):
http://www.samsung.com/us/support/owners/product/SEG-I997ZKAATT
5 - once installed and rebooted, connect your phone (booted into phone OS with USB Mass Storage mode enabled and then USB Debugging enabled) and validate connectivity using ADB or by mounting to PC as a USB storage device. Test by copying a decent sized file to/from the phone.
6 - if this works, boot into download mode and retry Odin or Heimdall packages. If you don't have Java Runtime Environment installed make sure you install that first. For Heimdall (and maybe Odin) make sure to right click the file name and run as administrator.
---------- Post added at 01:38 PM ---------- Previous post was at 01:36 PM ----------
Or... If you are still in the middle of a CM7 install, you may just need to complete the install by booting recovery, wiping system and flashing a second time as shown in the install instructions here:
http://forum.xda-developers.com/showthread.php?t=1311960&highlight=cm7
Either way, good luck!
Click to expand...
Click to collapse
You should get a triple thanks for writing this up.
Here is where I noted many users get stuck. Completely uninstalling and reinstalling drivers is the key.
mg2195 said:
I thought cm7 required a double flash...just like ICS does if coming from GB...
So flash
Get stuck at Samsung screen
Boot to recovery
Re flash
reboot
Enjoy?
Could be wrong though as I never used cm7...but I remember reading that our idea to double flash for ICS came from cm7
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Yeah..I think CM7 require a double flash if you are coming from froyo or gb. Something about the double flash for the recovery

same thing for gb to jb double flash works on mine flash once sticks at kernel, pull bat,three finger again to blue recovery the reflash rom again and bingo
Sent from my SAMSUNG-SGH-I997 using xda premium

[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] please help, softbricked galaxy s5 active

i made a extremely poor decision and was trying to change the boot animation loader when i actually changed the boot cmd and now it boots to samsung then to download everytime,. i can get into the onboard recovery yet i cant access safestrap and none of the many many drivers ive tried i cant get the phone to show to connect, its listed as unknown device in my device manager and ive hand picked the ones im supposed to have to other ones. ADB doesnt see it either and i was wondering if there is cmd for adb to find myu device, if you help me guys i promise ill only practice on hand me down smart phones. Ty:cyclops: [email protected] SM-G870A

This may be a dumb question, but have you tried Odin? I have had situations similar to this with my Samsung devices and always thought i bricked. But as long i could get into download mode, i could Odin back to stock and start over.

MrAwesome75 said:
This may be a dumb question, but have you tried Odin? I have had situations similar to this with my Samsung devices and always thought i bricked. But as long i could get into download mode, i could Odin back to stock and start over.
Click to expand...
Click to collapse
ya but i havent even tried loading a file into odin cause it wont see my device
and i have installed the samsung drivers but after this happened my pc wont see the phone

has to be a way to get a connection between the pc and phone

I'm not an expert so I'm not sure. Do you have the correct drivers installed on PC?
---------- Post added at 06:34 AM ---------- Previous post was at 06:30 AM ----------
Try different Odin versions. And make sure you have the proper drivers installed on the PC.

ya ive actually read that it probably doesnt have the function running to talk with the pc cause it cant boot. im all set up to reset the phoone. just need it to appear in my odin
..does kies still work?

[email protected] said:
i made a extremely poor decision and was trying to change the boot animation loader when i actually changed the boot cmd and now it boots to samsung then to download everytime,. i can get into the onboard recovery yet i cant access safestrap and none of the many many drivers ive tried i cant get the phone to show to connect, its listed as unknown device in my device manager and ive hand picked the ones im supposed to have to other ones. ADB doesnt see it either and i was wondering if there is cmd for adb to find myu device, if you help me guys i promise ill only practice on hand me down smart phones. Ty:cyclops: [email protected] SM-G870A
Click to expand...
Click to collapse
When you boot to system
It doesn't show anything right ??
but the touch is still functioning
Sent from my GT-i9300 running cm11 using tapatalk.

when i just boot it goes to download mode and says "could not do do normal boot"

i can access recovery mode and download mode but i cant get drivers to show it, and it used to show it until i did this, can i put a file on my micro SDcard from my pc via card reader then install it in recovery mode ? like firmware or a memory wipe reset?

If you can get into recovery, I believe that would be possible. Couldn't hurt to try. As long as you can get into recovery and all the recovery functions work, I don't see why you couldn't.

fixed it!
well after two nights of reading i got my pc to discover the device by changing ports three different times to find one that seamed to like it. and also installed kies and installed the drivers from them, (figured couldnt go wrong after as many as ive used from samsung and others). so win7 pro / altered boot command and only stock options afterwards sucks big time. ty all for helping me

never let up