Database Info

Link to Stock HTC Hero ROM

In case you've experiencing the frustration of your inquiries being met with "search for blah blah blah" here is the direct link to avoid frustration.
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe

If anyone can help me get this installed I'd appreciate it. It times out at the waiting for booatloader screen. I have the recovery ROM installed.

Try this:
Pull your battery
Put it back in
Hold down the Volume down arrow and press power
Press Volume Up, screen should say FASTBOOT USB in red
Start your RUU

If I'm in Fastboot USB Mode when I run the RUU, it fails at Verifying. If I boot into Fastboot while it's waiting to boot into recovery, it still times out.

Hmm, do you have the correct driver installed? Check your device manager under Android devices and see if the ADB driver is installed. If it is, install the driver from HTC Sync. Its called My HTC when it is installed

Yup, I definitely have the driver installed. I can use ADB just fine foe shell and push and so forth.
It connects initially to verify the info on the phone, but the RUU process reboots the phone and seems to expect it to boot into a certain bootloader. But it doesn't. I imagine the recovery ROM I flashed doesn't work with the RUU.
Does anyone have the original recovery ROM?

Had the same situation. I was able to get it to work by messing with the volume keys right after the reboot (pressed up and down a couple times.)

Gah, Windows. =/
Gonna see if I can do it in Parallels.

Having the same problem. It restarts the phone waiting for bootloader and then errors out.
Not sure what's going on. 100% positive I've got the adb driver. I've got HTC Sync working.
Using Win 7 64bit.
So it errors out and says a connection could not be made error 170.
I then disconnect the usb cable and the screen shows RUU but of course it's already disconnected.
No idea what to do.

Not sure why it is not working for you guys. My RUU would not update using the adb driver. I put it into fastboot usb mode. My pc then detected the phone. I went into device manager and checked under android devices. Make sure it says something like 'My HTC' and not 'HTC Dream' or something like that.

Hmm, worked fine for me under Vista. Installed HTC Sync update from the HTC site and all was good afterwards. Updating now.

I installed HTC Sync and now it works (that's with the custom recovery ROM).
Cool.

Yeah, the damned thing wouldn't work unless I installed HTC Sync. Back in business.

what OS are you guys using? I'm using w7 and i'm having absolutely no luck, i think i've tried everything possible...

I'm on Win7. You installed HTC Sync?
There's really no reason to flash the stock ROM anyway,,,

yes i have sync installed.
basically what happened was I lost my recovery backup image, i dunno how where i can get another one and how to apply it to my phone...this RUU thing is not working either, i tried fastboot and reinstalled all the phone drivers

Where is it getting hung up?

By the way, Byggun posted his recovery backup image:
http://rapidshare.com/files/308999685/recovery-backup.img.html

the RUU just says that my phone is not connected, i've checked the drivers and all are up to date.
i dont know exactly what to do to use the recovery image, i've never had to use one before, only had to create one.

it connects to my phone then waits for boot loader, then it says that its not connected anymore

Method for 100% factory restore, unrooted.

This is for those of you that may need warranty work, exchanges whatever. It may or may not be an issue but im sure many of you have noticed that clockwork will pop up whenever the phone is powered off with a usb connection present. Which in most cases would be an immediate red flag for those of you needing work done. This will completely restore your phone and remove the clockwork recovery flash.
Update: I no long have an Aria to try this with but if you guys are running into issues try this as well.
winsettr said:
I'd like to suggest that you update the first post to include a link with the last 2.1 RUU, seeing as the 2.2 RUU breaks the ability of future rooting (for now). I have uploaded what I believe is the updated RUU 09142010 to MegaUpload, linked below. Just thought this might help
http://www.megaupload.com/?d=XXYBORR6
Click to expand...
Click to collapse
1.) Download ATT Original Shipped ROM file from here:
http://www.htc.com/us/support/aria-att/downloads/
2.) Disconnect USB connection to phone.
3.) Power down phone
4.) Boot into Fastboot Menu (hold trackpad on start)
5.) Insert USB
6.) confirm that the phone shows "FASTBOOT USB"
7.) Run downloaded exe file
8.) Process will take a few min at the end you should have a 100% restored and unrooted phone.
It may seem self explanatory now but I was running into issues getting the HTC tool to communicate with the phone and it would fail whenever trying to send the phone into the bootloader. Thought I would just save you guys the headache.

thanks for your solution. was thinking about unrooting my phone and exchanging my aria for a samsung captative...

thanks man. doubt i'll do this, but i might need this just incase ATT and HTC actually come through with a stable update to froyo 2.2 within the next couple months.

I think it will be safe to assume that said 2.2 ROM will begin floating around in a rooted form not before too long, and will be flashable via recovery.

this is great info to have. great work.

???
has anyone actually tried this? because my pc dosent recognize phone when i try

bred904= said:
has anyone actually tried this? because my pc dosent recognize phone when i try
Click to expand...
Click to collapse
install Android SDK USB drivers first

??
i think i did... i installed something from google called android-sdk. and when i connect my phone in bootloader i can see fastboot change to fastboot usb and my pc says driver successfully installed. but when i run the .exe file it never sees my phone. also htc sync wont connect and neither will droid explorer. thanks

i agree with bred, can't seem to restore the original rom. it doesn't recognize it during the process

I have tried this method on 2 computers and the exe can NEVER find my phone.
I have installed the SDK USB drivers, my computer sees the Android 1.0 device and sees it as the HTC booloader. And I see FASTBOOT and FASTBOOT USB when unplugged/plugged.
----UPDATE 2010-07-23----
After further research I was able to determine that even with the device NOT in FASTBOOT mode, that adb couldn't see it, so I thought it might be a driver issue.
I've gotten my computer to recognize the device when it's booted normally. But when put the device in FASTBOOT or the BOOTLOADER, adb can't recognize it and I can't get the recover exe to recognize the device, regardless of mode.
I have the latest clockwork recovery installed and I would like to get everything back to factory to exchange for a captivate.

theres no way to do a nandroid backup or anything like that? curious because i was going to take mine back tomorrow to exchange for the captivate as well. i bought mine from radioshack so i might try my luck and just return it rooted . i did the trade in program with them with my iphone and it was jailbroken and they still accepted it. i dont think i would try that with at&t though... worse comes to worse just return it and say it was like that when you got it! maybe an at&t employee messed around with it before you bought it. they cant prove it was you.

Can anyone confirm this works? Just in case. This might be something I will need to do quick fast and in a hurry in the morning. And I'm hoping that if it comes down to this I won't have any issues.
Sent from my HTC Liberty using XDA App

I have been thoroughly unsuccessful in getting this method to work.
I have tried it on 3 different computers and I can never get the HTC OriginalShipRom.exe to find my phone.
I have tried following the instructions to the letter, I have also tried plugging in while booting the phone into various menus (HBOOT, FASTBOOT, and regular booting), which was advice given to me in the IRC room.
I'm plugging the phone in right after I click "Next" on the "Plug your phone into the usb port" right as it shows the "Verifying data on your PDA" window. I have tried with the phone in HBOOT, FASTBOOT, and while booting the phone, none of these seem to work.
I've also tried it with just plugging the phone in and running the exe. Nothing seems to work. People in the IRC channel are claiming successful factory restores, but I can't seem to get it to work.
So can someone please update the first post with more thorough instructions? Because those instructions don't seem to work.

The following instructions came directly from the HTC webiste for restoring the original state of the phone.
1. Download and save the HTC Aria™ Original Software to your PC.
2. Power your device off.
3. Connect your device to your PC via the data USB cable.
4. On the device, press and hold the Volume Down and Power Button until you get the bootloader screen (a white screen with 3 Androids on the bottom).
5. Press the Power Button once to enter FastBoot mode.
6. Locate the HTC Aria™ Original Software that you downloaded and double-click on the file to launch the RUU Wizard.
7. Follow all of the RUU Wizard instructions shown on your PC.
8. Once the update is complete, click Finish in the RUU Wizard and the device will reboot.
9. Once the device reboots it will run through the Customization Process; this must be allowed to complete.
10. Once the Customization process is complete, the device is then ready for use.
I hope this helps. I haven't tried it yet, but would like to know if this works in case I need to do this as well.

OutsiderWV said:
The following instructions came directly from the HTC webiste for restoring the original state of the phone.
1. Download and save the HTC Aria™ Original Software to your PC.
2. Power your device off.
3. Connect your device to your PC via the data USB cable.
4. On the device, press and hold the Volume Down and Power Button until you get the bootloader screen (a white screen with 3 Androids on the bottom).
5. Press the Power Button once to enter FastBoot mode.
6. Locate the HTC Aria™ Original Software that you downloaded and double-click on the file to launch the RUU Wizard.
7. Follow all of the RUU Wizard instructions shown on your PC.
8. Once the update is complete, click Finish in the RUU Wizard and the device will reboot.
9. Once the device reboots it will run through the Customization Process; this must be allowed to complete.
10. Once the Customization process is complete, the device is then ready for use.
I hope this helps. I haven't tried it yet, but would like to know if this works in case I need to do this as well.
Click to expand...
Click to collapse
My problem is with step 3. The second I plug my powered down Aria into the computer via USB, it powers on and goes directly into Clockwork.
If I boot the device into FASTBOOT, then plug it in, and then run the exe, it says it can't locate the device.

If you had flashed the unrevoked clock work you will not be able to plug your phone into the computer while its turned off. Your best bet is to boot into fastboot then plug in your phone. And try to do this under linux since there is no need for drivers.
Sent from my HTC Liberty using XDA App

farquep said:
If you had flashed the unrevoked clock work you will not be able to plug your phone into the computer while its turned off. Your best bet is to boot into fastboot then plug in your phone. And try to do this under linux since there is no need for drivers.
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
Hi farquep, can you give me instruction on how to use linux what's the command line?? thanx

If you do it under linux, just download the file and run it like any other program in any other operating system. Although you will have to let the file run as an executable under permissions. I don't know if you need to install WINE which will emulate windows programs. There should be no need for terminal scripts.
Sent from my HTC Liberty using XDA App

Doesnt recognize my device at all. If I'm returning to insurance company, should I even bother taking off clockwork? I already have the replacement.
EDIT:
Update:
Just worked for me. I had to install aria_shipped_rooted_signed.zip first then HTCAriaOriginalShipROM.exe recognized the phone.

SysAdmNj wrote:
> I had to install aria_shipped_rooted_signed.zip first
perhaps that can be added to the original instructions.
the archive can be downloaded from here

Finally unstuck but now autoresets

My phone did not want to boot this morning after swapping SIM-cards twice. Tried many things, including a hard reset, but nothing worked; the phone kept getting stuck in the second boot menu (with the fancy coloured X). When I tried to leave it it took a few minutes but the phone finally booted.
But I lost all settings (not files luckily) and came into an unknown screen. Had to setup a Google account but could not do that before accessing for internet. All these things work again, but when I reboot the phone it seems to reset again and I have to start from this unknown screen again.
Does this sound familiar and what can I do about it?
By the way, the phone currently runs Android 2.3.6 so there are no official updates (right?).

I've been messing around a bit and the "unknown screen" seems to be the new initial Android screen, in which you can setup the phone (Google account etc.). Strangely enough the phone keeps resetting and I cannot change anything. Even formatting, either through Windows or the boot/root menu doesn't help: all files that are on the phone right now are kept. I cannot add new files either.

Liquid_Metal said:
I've been messing around a bit and the "unknown screen" seems to be the new initial Android screen, in which you can setup the phone (Google account etc.). Strangely enough the phone keeps resetting and I cannot change anything. Even formatting, either through Windows or the boot/root menu doesn't help: all files that are on the phone right now are kept. I cannot add new files either.
Click to expand...
Click to collapse
First of all, do you have a Nexus S, or Nexus S 4G? Is your bootloader unlocked? If not then I suggest you follow the guides in the development section. I can't put links due to still being 'new' on here. Find a recovery, flash via fastboot, boot into recovery and flash a rom to your liking. Or you can find some system images and flash via fastboot. I hope this helps. If not, then you can pm me and then I will show you how.

mabry said:
First of all, do you have a Nexus S, or Nexus S 4G? Is your bootloader unlocked? If not then I suggest you follow the guides in the development section. I can't put links due to still being 'new' on here. Find a recovery, flash via fastboot, boot into recovery and flash a rom to your liking. Or you can find some system images and flash via fastboot. I hope this helps. If not, then you can pm me and then I will show you how.
Click to expand...
Click to collapse
Thanks for your reply. I did not unlock the bootloader. I've seen many difficult topics and don't really know where to start.
I just found out that the phone not necessarily resets to a previous state (this morning) but seems unable to write anymore. I just hooked it on to my PC, removed a file, disconnected, and upon reconnection the file was there again (whereas Windows really removed it).

Liquid_Metal said:
Thanks for your reply. I did not unlock the bootloader. I've seen many difficult topics and don't really know where to start.
I just found out that the phone not necessarily resets to a previous state (this morning) but seems unable to write anymore. I just hooked it on to my PC, removed a file, disconnected, and upon reconnection the file was there again (whereas Windows really removed it).
Click to expand...
Click to collapse
I am uploading some files to Dropbox now. Its gonna take a bit. Then I will guide you through, step by step. Sorry for the wait. I know you want to get your phone back up and running. In the meantime, I recommend doing some reasearch here on xda. Don't be afraid of Google, either. Google can be your best friend.
---------- Post added at 02:42 PM ---------- Previous post was at 02:18 PM ----------
Read this. This should help you out.
http://forum.xda-developers.com/showthread.php?t=935819
Read it first. It might come across tricky or hard, but its not... Once you do that to unlock bootloader and root, I would advise you to download either a stock rom, or any others you may feel comfortable with. Look around. There are plenty here on xda.

mabry said:
I am uploading some files to Dropbox now. Its gonna take a bit. Then I will guide you through, step by step. Sorry for the wait. I know you want to get your phone back up and running. In the meantime, I recommend doing some reasearch here on xda. Don't be afraid of Google, either. Google can be your best friend.
---------- Post added at 02:42 PM ---------- Previous post was at 02:18 PM ----------
Read this. This should help you out.
http://forum.xda-developers.com/showthread.php?t=935819
Read it first. It might come across tricky or hard, but its not... Once you do that to unlock bootloader and root, I would advise you to download either a stock rom, or any others you may feel comfortable with. Look around. There are plenty here on xda.
Click to expand...
Click to collapse
Thanks again . A friend of mine was trying to help with bootloading and stuff, but it's somewhat obscure. He said that chances that it's software or hardware are just 50:50.
Got me kinda frustrated yesterday evening but I still have warranty on the phone (have it for half a year now). Problem is that it might be a hassle, because of a conflict between the shop and the provider. But that should work out.
In the meantime it would be nice to try and get it running again.
Strangely enough, the phone drained itself this night. I made a basic install yesterday and left it in standby. This morning, when I checked the phone, it didn't do anything so I thought it finally passed away. Now that it's hooked to my computer it's charging, and it seems to start from 0 (starting with 0 bars of the battery).

Via your link I came to the following guide, which worked partially (cannot link it here).
age tee tee pee ://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
I got up to step 13, where it seems that I cannot find the .zip-file because the phone doesn't store new files...

You can wait for warranty, or you can follow this guide:
http://forum.xda-developers.com/showthread.php?t=947950&highlight=odin
Odin will flash it back to stock without the need to put files on your sd card. Just download the odin files, open up odin, put phone in download mode, and happy flashing. You have to be careful with odin, though. Follow the guide. If you need help, then let me know. I can probably do it remotely for you.

Thanks, I'll try that tomorrow (topic doesn't seem so clear at first glance).

According to this guide, I have to start in Download Mode. I can access this by holding Volume Up + Volume Down and then plugging in the USB cable. It works, but the phone will not be updated and I'm stuck with the "Downloading..." message. Also, Windows Device Manager sees a Gadget Serial, which I cannot update. Google didn't allow for a clear answer (Samsung PC Studio 7 didn't work).
I also think I have an i9023, because it's the European version (which SHOULD be with an LCD screen).
By the way, I just tried formatting through Windows (FAT32) and if still connected the phone indeed seems to be empty. But as soon as I disconnect USB storage all files (on the phone) are back. Nothing special because the problem is very consistent.

Update
Alright, I finally got the drivers properly installed (also to work in Download Mode) and found proper Bootloader/PDA/CSC files (i9023EUR) for Odin and managed to do the flash update (however Odin I used is called I9003_Odin3 v1.82, don't know if that is a problem).
Then I should do a factory wipe, which works (Bootloader -> Recovery -> Wipe), but if I explore the phone I can see that all data is still present (all images, music, etc). So the hard drive still seems fixed.

Please help me out, guys...

Suggestions? Or unfixable and should I send it to be repaired?

I found out that I did not post my last update. I managed to flash with Odin, and I can get into the Bootloader menu to wipe the phone's data. I can, in Recovery Mode, also see the hard drive and it seems to be empty. That is, the phone fails to see it.
When I reboot out of Recovery Mode the phone gets stuck at the Google logo and that's it..

Ok, I will send the phone to be repaired. The phone is now unrooted and does not go further than the Google load screen.

Do you have fastboot? If not then download below.
http://dl.dropbox.com/u/64632729/platform-tools.zip
Extract contents to desktop. Open up a command prompt:
cd Desktop/platform-tools
Put phone in bootloader mode. In command prompt type:
fastboot oem unlock (only if your bootloader is still locked). If its unlocked then download this
http://dl.dropbox.com/u/64632729/recovery-clockwork-5.0.2.0-crespo.img
Put in the platform-tools folder you extracted earlier. Then type in command prompt:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Sometimes the flash might say 'fail' if that is the case then just boot the recovery image by typing:
fastboot boot recovery-clockwork-5.0.2.0-crespo.img
Now boot into recovery and flash either a stock rom, stock rooted rom, or whatever your desire is.
This should work. If not, then there has to be a hardware issue with phone and go ahead and send it in for warranty. Let me know if this helps.

Flashing Clockwork did work, but if I understand correctly I have to copy the stock rom to the phone and load it in Recovery Mode? When I connect the phone to my PC it is recognized as an Android Phone (and even as a Nexus S) but the drive it shows up as seems to be recognized as empty ("Please insert a disk into Removable Disk (E.").
So what do I do?
What is sort of promising is that it indeed was capable to flash Clockwork. So the memory is not completely stuck. However, when I do a format, still nothing happens (phone isn't formatted).

Update: I am able to mount the phone to USB and I can access the phone via Windows. However, I can still not format the SD Card (which is of course internal) or put files (stock rom) on it. Are there other tricks to flash a stock rom? If not, it does indeed seem to be that I cannot flash a custom/stock rom because the drive of the Nexus is frozen/broken/whatever.

[Q]Softbricked with no ADB or sdcard function ARGH!

NS4G
Will boot to fastboot and recovery
CWMR Touch 6.0.1.0
Situation:
My device started bootlooping after about a week of random restarts and freezes. I had just flashed BlackBean and now this, so I decided I was just going to flash a new ROM/Kernel combo. I remembered someone saying I should format /system to install the specific ROM, but I'm fairly sure I formatted /boot along with it, like an idiot. FYI - Fast Charge and a build.prop tweak to set permissions on boot was enabled when this happened. So then I try and flash a new ROM/Kernel combo to fix my bootloop and it wouldn't read the sdcard afterwards. Now it boots straight to fastboot everytime. Toolkit seems to be able to do some things via USB control like reboot the bootloader, but it does not detect an ADB device when I run the driver check or try to restore my CWM backup. I ran the stock+unroot option in Toolkit (was going to send it in thinking the sdcard thing was hardware at first) and it seemed to have went through the whole process correctly... Until the end when it did not reboot automatically like it should have. After doing this, I now get "STANDARD_SET_CONFIGURATION" on the phone when I insert the USB cord while in fastboot. It did not do this before, whether it is the new cord or the flash I do not know. My old cord WAS having problems with data though.
Problem:
I now have no USB debug or SDcard functionality. I assume because of missing files on /boot. I can mount nothing (except cache, but the PC doesn't recognize) without getting a "can't mount" error. This puts a serious dent in my novice ability to fix it. Anything in Toolkit that runs via ADB commands doesn't seem to work properly because it says the device is not in debug mode. PDAnet USB Drivers seemed to install without a hitch and device is recognized on my PC.
Errors:
When trying to mount ANYTHING except the cache while in CWM, I only get: "E:/ Can't mount /sdcard/".
If I try to mount USB storage I get: "E:/ Unable to write to ums lunfile (No such file or directory)Error mounting /sdcard!"
If I try to run any one click methods that use ADB I get: "Daemon not running* No ADB device detected. Make sure you have debugging enabled on your phone"
The log in CWM recovery always shows: "I: Set boot command "" failed to open /sys/class/android_usb/android0/state: No such file or directory" over and over (as many times as I tried to mount something while in recovery for that session)
Questions:
Do you think USB Fast Charge or having the build.prop tweaks enabled could have done something to USB debug? Is there a way to at least just fix the USB Debug problem? Am I correct in assuming that wiping the /system along with the /boot folder is what caused me to not be able to mount the /sdcard to flash another ROM? Is there a way to push the files I need onto the device to restore sdcard function and flash another zip?

Also, what fastboot do I need to be in to do the StockROM+Unroot method in the Toolkit? I have two. Only hold Vol Up/Power takes me to "FASTBOOT". Holding both Volumes+Power puts me into "FASTBOOT - NO BOOT OR RECOVERY IMG"
What is the difference?
I only ask because the Toolkit wants me to hold both volumes and up to get into bootloader mode, but they describe a big green "Start" with an android lying on it's back, mine does not look like that. It simply looks like regular fastboot, but says "FASTBOOT - NO BOOT OR RECOVERY IMG" instead.

It seems you messed with the ROM zip with some tool. Sorry could read your lengthy post completely.
I just want to know one thing clearly, what is the problem basically? where are you stuck?

Edit - Made it as concise as I could, hope it helps. Sorry for length.
Basically, the phone has a formatted /boot, /data, /sdcard, /system, dalvik cache, and I can't seem to use any of the flashing tools via Toolkit in Fastboot mode because the Toolkit says it "cannot find ADB device" please enable "debug" mode. Even when I run the driver check, it says ADB Device Not Found. Though I do have some control of the device via USB (I can use Toolkit to soft reboot from the bootloader) telling me my drivers are probably OK? I couldn't flash any ROM zips (or anything, even backups on the device) because I lost /sdcard functionality.
After a bunch of reading last night, it seems I want to Push a backup of /system and /boot onto the device, which should then restore USB functionality and allow me to flash a ROM... Right?

DizturbedOne said:
Edit - Made it as concise as I could, hope it helps. Sorry for length.
Basically, the phone has a formatted /boot, /data, /sdcard, /system, dalvik cache, and I can't seem to use any of the flashing tools via Toolkit in Fastboot mode because the Toolkit says it "cannot find ADB device" please enable "debug" mode. Even when I run the driver check, it says ADB Device Not Found. Though I do have some control of the device via USB (I can use Toolkit to soft reboot from the bootloader) telling me my drivers are probably OK? I couldn't flash any ROM zips (or anything, even backups on the device) because I lost /sdcard functionality.
After a bunch of reading last night, it seems I want to Push a backup of /system and /boot onto the device, which should then restore USB functionality and allow me to flash a ROM... Right?
Click to expand...
Click to collapse
Your storage memory is completely inaccessible?

Yes, no way to access it via CWM. ADB stuff does not work either. It seems Fastboot stuff DOES. I would like to find a boot.img and system.img to flash via Toolkit (I believe toolkit uses fastboot or odin for these) to see if that would work for me. Any ideas?
It seems like the easy nature of unlocking, rooting, and customizing this phone leads to less of these kind of discussions, I can usually find many files and discussions pertaining to this for HTC phones, but never for this phone.

My bootloader version is KE1, but my baseband version is LF2, makes no sense to me.
The KE1 bootloader was when I was on ICS, but the LF2 baseband was from Jellybean... wth?
Do you think the time I flashed "stock+unroot" on the toolkit that it only partially took? (I did try to back it up to ICS because the Jellybean download didn't work). It seemed as if it flashed everything via fastboot, but never restarted at the end and still won't boot when done.

same problem kinda
i am having the same problem as this with my nexus. mine started after i downloaded Jellybean.it worked fine for about 1 month. i had changed nothing but when i would change my battery or restart my phone it would get stuck at the google screen every now and then, then it started more often. i could normally pull the battery and restart it and it would work after a couple of times doing that. but now this last time i tried that the phone wouldnt go past google screen at all. i can access my clockwork mods recovery but when i try to install zip from sd i get the error cant load sd i have tried everything i know and cant get nothing to work. please help. i miss my nexus this prevail is too slow and small...

Your drivers don't seem to be installed properly.
Get that right, then you can reflash your recovery via fastboot, then you can mount your usb and transfer anything (rom kernel gapps etc etc)
Edit: oh and Bamamac82, that's not the same problem at all. Create a topic of your own.

polobunny said:
Your drivers don't seem to be installed properly.
Get that right, then you can reflash your recovery via fastboot, then you can mount your usb and transfer anything (rom kernel gapps etc etc)
Edit: oh and Bamamac82, that's not the same problem at all. Create a topic of your own.
Click to expand...
Click to collapse
@ polobunny - There is no way for me to install them more properly if I can't go into debug mode to install them though... I wiped out ALL drivers and manually reinstalled the drivers from PDAnet that had previously worked perfectly on my device. But now it never installs as Nexus S, only as Samsung ADB Interface or some such. I've tried it with PDAnet drivers and the Samsung drivers and have followed every driver install guide on the web... Any other suggestions on how to do this properly? I was even thinking of installing a Google SDK just to see if the drivers would work better...
@ Bamamac82 - Yes, that is pretty much the exact same problem, with the exception of the fact that you didn't wipe the /boot partition as I did. But yeah, I installed a JB ROM, it got a few random restarts, froze up twice, then one morning got stuck in a bootloop after I pulled the battery on a freeze up. Not having a working USB cord at the time botched me, because I couldn't get my drivers reliably installed before anything happened, I was using AirDroid because my OEM cable wasn't working with data reliably.
I totally thought the sdcard problem was because I formatted /boot in a hasty ROM flash though. Could I be wrong here?

DizturbedOne said:
There is no way for me to install them more properly if I can't go into debug mode to install them though... I wiped out ALL drivers and reinstalled the drivers from PDAnet that had previously worked perfectly on my device. But now it never installs as Nexus S, only as Samsung ADB Interface or some such.
And Bamamac82 has the exact same problem, with the exception of the fact that he didn't wipe the /boot partition as I did. But yeah, I installed a JB ROM, it got a few random restarts, froze up twice, then one morning got stuck in a bootloop after I pulled the battery on a freeze up.
I totally thought the sdcard problem was because I formatted /boot in a hasty ROM flash though. Could I be wrong here?
Click to expand...
Click to collapse
When you're in fastboot mode on your phone, on your windows PC point the unknown device or the device with an exclamation/question mark to the path where the .inf for the drivers are located. If it still doesn't detect it, you can always try and force it to install a certain device (adb debug bridge or something of the sort).
Once that is done as I said you won't have any problem fastboot'ing to your phone and doing the other steps. Windows drivers and especially the adb drivers can be finnicky.
Your SDcard problem has nothing to do with the fact your formatted boot partition though, those are not linked.
Edit: Oh and I know there is some people, namely with NS4Gs, that had issues with the drivers. I believe for some reason there's some missing IDs in the inf making it impossible to install automatically. Forcing it should work though.

Polobunny thank you so much for your help so far. My device has been softbricked for a week and I'm using a HTC Hero for now! It's atrocious. I'm going to try as you said when I get home tonight and will update if fastboot allows me to flash after that.
Any idea where I can get all the .img's I need? I can only find the complete .tgz for IMM76D (which is fine for now just want it back to working state) and don't know how to extract .img's from it. Can't even find the complete .tgz for JRO03R though, the link is always down. At this point, all I want is a factory img to start from so I can upgrade to JRO03R, root it, and then make a fresh NAND backup from there.

If I were you, I would download Odin, a factory image from Google (just search nexus s factory image), the SDK tools (Google it) and would "reset" the phone.
You will easily find a guide for Odin. Then you'll just have to follow it and your nexus should be fine (but it will be factory reseted and you will have lost all your data )
Sent from my Nexus S using xda premium

Sorry guys, have been putting late hours in at work and haven't had much time until this weekend.
@BenHeng, that's what I am about to look into tonight. I didn't want to learn an entirely new aspect to restore this, I have been limited on free time and am starting to think it will be less hassle than dealing with this.
Only caveat to that, is that I definitely would like to know what happened to cause the SDCARD problem, because that was the main problem that got to me here, would like to prevent that from happening again.

ADB
Make sure ADB debuging is checked under Developer options

localpagefirst said:
Make sure ADB debuging is checked under Developer options
Click to expand...
Click to collapse
Please read the thread before replying.
@polobunny - I did a complete manual install of the RAW drivers, and got it to recognize properly as a Nexus S, as it did when USB Debug and everything worked correctly... But it still does not recognize it as an ADB device when running a driver check.
Is it safe to continue forward with a flash via ODIN in this state?

Hi, I don't understand why you want to use ODIN, fastboot commands still don't work after you installed correctly your driver?
Anyway you can find all (new and old) originals google image here:
http://www.randomphantasmagoria.com/firmware/nexus-s/

Listen mate, the best way would be to flash the factory image via fastboot in bootloader mode. Follow this simple step to step guide.
If you have any issues. post them there on the blog post itself :good:

DizturbedOne said:
Please read the thread before replying.
@polobunny - I did a complete manual install of the RAW drivers, and got it to recognize properly as a Nexus S, as it did when USB Debug and everything worked correctly... But it still does not recognize it as an ADB device when running a driver check.
Is it safe to continue forward with a flash via ODIN in this state?
Click to expand...
Click to collapse
Please, please don't use a shi**y 1-click package thing. There's no driver check to be done other than using adb and typing "adb devices". Do it manually and report the results. It should show your adb device ID, a long string of number and letters.

polobunny said:
Please, please don't use a shi**y 1-click package thing. There's no driver check to be done other than using adb and typing "adb devices". Do it manually and report the results. It should show your adb device ID, a long string of number and letters.
Click to expand...
Click to collapse
I get nothing when I do that. It says "List of devices attached" and a blank line underneath. When I plug the USB in during fastboot I get "STANDARD_SET_CONFIGURATION" at the bottom, which I never get until I install the drivers.
It seems as if the computer must recognize the device in debug mode in some way to properly install the drivers.
Why is my sdcard partition unable to be written to? This never would have been a problem as I always keep a couple backup ROM's on the phone. Either way, it seems as if all of this is for nothing if the phone will not allow me to read/write to the memory in the device.

How do I Unbrick? Small twist

Ok so here is the issue. My Nexus S i9020a has a power button that is no longer working. Whenever I put the battery in, it automatically boots up, to reboot I take the battery out and slide back in. I want to bring it back for warranty since my bro got the warranty until 2014 or so. I had previously had a couple of custom ROMs on it. I wanted to flash stock ROM and lock the bootloader.
When I boot into recovery (hold up while I put the battery in), I can't do anything. Even the volume up/down doesn't do anything, and of course pressing the power button doesn't select anything. So I got ROM Manager and found a copy of the stock rom. ROM Manager was supposed to install the rom from the .zip file, which it sort of did. It wiped everything and installed. I left it on while I went to do something. When I came back, the phone is stuck in the bootup animation.
If I was able to do anything in recovery I would just reflash a different ROM and go again.
I have watched some videos, and tried the Oneclick Unbrick, but doesn't work. I've read some other threads here that talked about getting Linux on a USB, or other mod. But I am trying not to go that route, as it seems pretty complicated.
When the phone is in the bootup animation and I connect it to the computer, I hear the sound that Win7 detects new hardware. If I am in the bootloader Win7 does not play any of that sounds.
I remember using adb and I still have the files on my computer from when I unlocked and rooted.
Not sure what should I do now?

also, all of my soft button lights are on during the boot animation. read in one of the threads that different lights on mean different modes. so not sure if this means anything.

hi, I am afraid the bad functioning of power button is responsible of all of these problems,
probably you can send it for warranty as is now
---------- Post added at 12:15 PM ---------- Previous post was at 12:10 PM ----------
have you tried already the linux app UnBrickable Resurrector ?
maybe you would be able to install the stock rom via fastboot

Possible fix: Remove all drivers and reinstall via Nexus root toolkit. Go to adb and flash TWRP, or CWM Touch Recovery (make sure it's touch-enabled), then flash a new rom.
Permanent fix: As far as I can remember (I also had this issue about 6 months ago) samsung will still recognize the warranty even when your bootloader is unlocked, at least in my place. The issue you're returning with is a hardware issue, not a software issue. So tell them to just replace the power button and you'll do the rest. As long as the samsung warranty sticker on top of the screw is in-tact, you're good to go. Again, this is my experience in a samsung service center near my place. I don't know how they deal with things elsewhere.

if this can help, I read in forums that also in Italy samsung support fixes nexus s in warranty even with unlocked bootloader, this is not a direct experience though

So I have tried the wugfresh Nexus Root Toolkit and tried installing different drivers. None of them can detect the phone when it is in the bootloader, windows only makes a sound when the phone is trying to boot up.
I've tried the "Flash Stock + Unroot" button but as soon as it tries checking the fastboot it cannot detect anything. The mini description says all it needs it to have the phone in the bootloader, but I can't get it to do anything else.
I have tried the guide at DroidViews (can't post links yet), but in the command prompt, fastboot just keeps waiting for the device again, windows does not detect the phone unless it starts to boot and enters the bootloop.
what do I do now?

eugene188 said:
So I have tried the wugfresh Nexus Root Toolkit and tried installing different drivers. None of them can detect the phone when it is in the bootloader, windows only makes a sound when the phone is trying to boot up.
I've tried the "Flash Stock + Unroot" button but as soon as it tries checking the fastboot it cannot detect anything. The mini description says all it needs it to have the phone in the bootloader, but I can't get it to do anything else.
I have tried the guide at DroidViews (can't post links yet), but in the command prompt, fastboot just keeps waiting for the device again, windows does not detect the phone unless it starts to boot and enters the bootloop.
what do I do now?
Click to expand...
Click to collapse
Remove all android/samsung drivers and install PDAnet drivers. PDAnet detects the phone even on bootloader.

ej8989 said:
Remove all android/samsung drivers and install PDAnet drivers. PDAnet detects the phone even on bootloader.
Click to expand...
Click to collapse
I just tried the PDAnet, I choose the Samsung drivers, then once it pops up with the screen to ask me to connect the phone then I'm stuck. Whether I put the battery in and let it bootloop or hold vol+ and put the battery in, it doesn't get past the screen. Only thing I could do was "skip USB" which still installed PDAnet but possibly without USB support and just bluetooth support.
I even tried it on my brother's laptop which is still in a relatively clean OEM state but the got stuck at the same place.