Nexus S upgrade [2.3.4-2.3.6]

After getting the Nexus S, we found it was version 2.3.4. After Ota, we planned to upgrade it to version 2.3.6.

1. Normal OTA
Directly choose to restart and upgrade. I was praising Nexus S as Google's second son. After the restart, I found that the robot and exclamation point icon appeared halfway through and searched for it, I found that everyone has encountered this problem.
When the swap battery restarts and enters the system again, the system prompts that the upgrade is up to date.
At the same time, we found that we should receive the OTA notification again after a while, but we are sure that the update process is still unsuccessful.

2. Try OTA again
I just clicked restart and threw it aside, so I don't know what is going on in the middle. So I plan to re-Ota and try again.
Although there will be an OTA prompt later, it is not very willing to wait, so use the following method:
First, perform dialing (* #* #2432546 # *) to verify system updates. Then, enable settings-privacy-Restore factory settings. After this step is completed, the system will automatically restart, after the instance is started, dial again (* #2432546 # *) for a few minutes, and then enable settings-about mobile phone-system updates
This time I watched the restart and went halfway through the machine and the exclamation point again.
It seems that the reason for this is that a third-party recovery mode is used, but I don't know why it is like this.
Here, you can press power and volume up again to enter the recovery mode.

3. Try to get the upgrade package from data and manually upgrade
I thought of this method right away. However, because there is no root, I have to leave it alone because I cannot get the data (ddms + shell) under data ..

4. Manual brush 2.3.6
There are actually two options here. One is to directly brush 2.3.6, the other is to brush 2.3.4, and then wait for Ota, I chose one.
Attached to a native 2.3.4 system, I am useless, not responsible is good
Native 2.3.4 System (http://v14.lscache1.c.android.clients.google.com/packages/data/ota/google_crespo/da8206299fe6.signed-soju-ota-121341.da820629.zip)

Upgrade the 2.3.6 package (Http://dl.dbank.com/c0te6aot7c) After the download is completed, put it in the SD card and restart to upgrade
Prompt that the upgrade is successful. After the restart, you will find that you are stuck on the Google interface and will not continue.
This is the legendary fake brick.

5. Solve the problem of false bricks
Sorry, I plan to change the package name and upgrade it again. However, according to the instructions on the internet, modifying the files in SD in recovery mode does not work, mainly because I am suspected of a third-party recovery mode problem.
I think this third-party recovery mode is not very good. Just click it and try again later.

Download refresh (Http ://Dl.dbank.com/c0e7k6vkw4), Perform the following six steps:
The following steps are reproduced, reproduced from: http://bbs.gfan.com/android-1587046-1-1.html

Step 1 shut down and go to the flash screen
Turn off the phone and press "volume up key" + "power key" to keep it for about 5 seconds. Then, the mobile phone screen displays the bootloader interface.

Step 2 install the driver(My file contains the NS driver. If you do not understand how to install the driver, please do not continue to read this tutorial! I beg you !)
Connect your phone to your computer with a USB cable. Right-click my computer and choose manage from the shortcut menu. Then, right-click the Device Manager and choose unrecognized Android 1.0 device, then select "Update driver", select manually install driver, select miui_ns/Drivers/x86 directory (64-bit system select miui_ns/Drivers/x64), and then continue the next step to complete the installation, you may choose whether to continue the installation. After the installation is successful, the system can identify your mobile phone as an Android phone.

Step 3: Check whether your machine has been unlocked, that is, root? (Very important !!!)
Note the text on the bootloader interface. If it is displayed as "Lock State-Unlocked", it indicates that it has been unlocked,Skip the following steps and go to Step 5 to recovery,
If it is displayed as "Lock State-locked", continue step 4.

Step 4 unlock your root machine!
Double-click the unlock. BAT file under the kekeyin_fastroot/fastboot directory on your computer (if your computer does not display the file suffix, double-click the unlock file)

Step 5 refresh to the machine (my version is v3.1.0.1, i9023/i9020)
Double-click the flash_recovery.bat file in the kekeyin_fastroot/fastboot directory on your computer (if your computer does not display the file extension name, double-click the flash_recovery file)
In fact, at this step, we have completed all the steps to unlock the root. However, some junk tutorials may fail to start the boot due to some boot brush steps, such as failing to enter the system or enable the USB flash drive.
Here I provide the original boot for those who are cheated to brush the machine. If you brush the machine for the first time, if you want to brush the sixth step, there will be no problem, but it is redundant.


Step 6 brush boot to the machine (i9023/i9020)
Double-click the flash_boot.bat file under the kekeyin_fastroot/fastboot directory on your computer (if your computer does not display the file extension name, double-click the flash_boot file)

6. Flash
Finally, we can see the yellow recovery mode, which is much simpler.
Go to recovery mode and select "toggle Signature Verification" in the "Install zip from sdcard" option to make it disable;
Download the upgraded Rom package such as 2.3.6and download the update.zip file to the mobile phone sdcard folder (advanced recovery, then select mounts and storage, and then mount USB storage. After more than a dozen seconds, you can see the mobile phone drive letter on your computer and copy the file)
Install zip from sdcard, then choose zip from sdcard, select sdcard, then select update.zip to upgrade, and reboot the mobile phone.