Results 1 to 10 of 10
- 04-10-2011, 03:03 AM
Thread Author #1
- 04-10-2011, 10:10 AM #2
- 04-11-2011, 05:28 AM
Thread Author #3
- 04-11-2011, 10:38 AM #4
If you haven't rooted or installed custom firmware, a data wipe should bring it back to a clean state (any updates to Android will still remain). I believe the only thing Google issues are updates, not recovery images.
Could you share what exactly is going wrong with your Nexus S? - 04-12-2011, 03:38 AM
Thread Author #5
When the battery gets to 15%, the warning box appears, I click Ok, it appears again, Ok, again, Ok again... I have to turn it off to stop the low-battery sound and the messages appearing.
At random intervals during the day, the call signal appears as white instead of green even though the signal has three to four bars. When it is like this the G3 and calls don't work very well.
My contacts slowly start to duplicate over time. ie. I end up with about 3 to 5 versions of each contact.
These are a few of the issues p me off.
I was hoping to reformat and reinstall Android. I do so with my computer (windows) every year to clear out the buildup of typical performance loss and buggyness due to changes to the system by the software installed.
I currently have version 2.3.2.
It is really disappointing to find that Android can't be reinstalled. Actually, it is pathetic. Not sure what I'm going to do now.
Thanks for your reply. - 04-13-2011, 01:45 AM #6
Wow, that's pretty weird
Before you give up on the Nexus S though, you should give it a shot at redeeming itself with Android 2.3.3.
Go ahead and follow AC's instructions on updating your Nexus S manually.
If you want to do a sure fire wipe, I suggest you use the "fastboot oem unlock" command. This will wipe everything except the system itself (including USB storage and caches).
You can follow AC's instructions on unlocking the bootloader, then type "fastboot oem lock" at the end to bring it back to the original locked state.
If you don't have the Android SDK installed, you can use the . It contains adb, fastboot and the drivers for both. - 04-15-2011, 02:57 AM
Thread Author #7
Thanks TDR.
I'm thinking of doing the unlock thing you suggested before installing 2.3.3. The instructions to the site you gave are
1. Shutdown the phone
2. Hold down volume up + power
3. Now you are in the standard recovery mode
4. Assuming you have 2.3 SDK installed with fastboot (Google around for that info..), now on terminal/windows or Windows cmd depending on OS type "fastboot devices" to check your device can be seem via USB
5. Assuming you device is seen via fastboot devices, now type "fastboot oem unlock"
6. Accept ... and new bootloader is unlocked...
Points 4 and 5 assume things. I do have the 2.3 SDK installed and it has fastboot.exe but it doesn't look like it is 'seem via USB'. I run the 'fastboot devices' but an exception about a missing dll appears.
Assuming I don't know how to use fastboot, what do I need to know?
I am going on leave for a week fishing in the NT so won't have access to a comptuer to check your response, but will when I get back.
incedentally, another intermitant bug is that randomally, the screen turns on after turning it off. It just wont stay off. My battery goes dead well before the end of the day.
Must go.. Thanks for your help. - 04-18-2011, 01:12 PM #8
I'm guessing fastboot.exe and AdbWinApi.dll aren't in the same directory. I think for some reason they tend to get split up between "tools" and "platform-tools" directories, just move one of them so they're together.
Perhaps if you're going to unlock the bootloader, you could go one step further and flash a custom recovery. With that, you can restore a backed up image of Android 2.3.3 or custom firmware. This does rewrite the system partition, which is I think what you wanted
While HTC showed some love by releasing an official image for Android 2.3.3 on the Nexus One, AFAIK Samsung/Google haven't blessed us with that. You can download backed up images (with or without root) from . Before going on, I suggest you do the official update first, so you receive the all important new radio and bootloader.
(details in ). Once you unlock the bootloader, you can flash ClockworkMod with the command "fastboot flash recovery 3025-i9020.img". Select the recovery option on the screen, and you'll reboot into the new recovery. If you go down the backup image route, you want to select "backup and restore" from the main menu, then select "restore". To be on the safe side, you might want to go to "wipe", "wipe data/factory restore", then reboot. Clockwork recovery will also be removed when you reboot. (Also, don't be shocked by the new color balance in 2.3.3, that's normal)
If you want to go down the exciting route of custom ROMs, you can select "install zip from sdcard" after you download the appropriate files. I'm personally rocking CyanogenMod 7 on my Nexus S
- 11-24-2012, 06:34 AM #9
- 02-16-2013, 04:38 AM #10



Reply
































