[HOWTO] get root back after ota update!

[radinjxu]

Is it necessary to go back to stock to get the OTA? Won't it just be incorporated into future custom ROM's. Sorry, I'm somewhat new to the whole rooting community and am unsure of whether or not I need to flash back to stock, unrooted to get the update, or if I can just stick where I am and get it in an update to a custom ROM.

 

[jroid]

I just pushed everything and executed permissions manually. Got 2.3.1 by restoring /system and /cache while keeping my boot.img and it booted perfectly fine

 

[ogh417]

Is it just me or does adb remount no longer work?

If I use the old koush rootboot.img it works, but no wifi, if I use the stock boot.img, I get no wifi but am able to remount.

Same here. What do I need to do to make adb remount work?

Thanks.

 

[jimmypopulous]

I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.

I guess time will tell

The method I used was:

[snip]

These steps worked for me. Thanks!

 

[jaker.the.skater]

where do i get recovery-clockwork-3.0.0.0-crespo.img?

edit: im an idiot. sorry i got it now

 

[jblade1000]

No, it's a safety mechanism so you can't lose recovery... It has nothing to do with clockworkmod. Someone can make a root script or app that disables it easily. Or people can just do it themselves manually.

edit: actually, all that needs to be done is add some code to the update script inside su-2.3.6.1-ef-signed.zip so when it installs the update, it renames install-recovery.sh

so if all the future ota updates require stock recovery, we can just un-do the rename of that file and reboot to get stock recovery, then update, then re-flash CWM recovery from ROM Manager (assuming the ota retains root or you re-root)?

 

[kramer987]

having a bit of trouble here. i followed all the steps but when i go to rename the install-recovery.sh file i am told that it is a read only file and cannot be changed. how do i fix this?

i also tried this method and get the same error:
adb shell
su
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak

EDIT:
nevermind. got it to work using this:

adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak

 

[yungfresh]

how do you go into adb? is it just through the terminal? i'm confused. I'm pretty new to the adb thing?

 

[nyijedi]

Does flashing a new recovery normally result in all data on the Nexus S getting wiped? This happened when I first flashed the clockwork recovery when I rooted and I wasn't expecting it. I'm currently rooted, but my recovery has reverted to stock. If I flash clockwork recovery back on (and then rename install-recovery.sh to install-recovery.sh.old), will my phone be wiped again?

 

[DKYang]

No, only unlocking the fastboot will erase everything. Possibly locking it will also erase everything, but I haven't done that so I'm just assuming. Flashing recovery images should not result in loss of data.

 

[alexeiz]

If I use the old koush rootboot.img it works, but no wifi, if I use the stock boot.img, I get no wifi but am able to remount.

I'm left with a broken wifi as well. Is there any way to fix it?

Or where do I find the stock boot.img?

 

[k0mpresd]

I'm left with a broken wifi as well. Is there any way to fix it?

Or where do I find the stock boot.img?

i posted the stock boot.img in another thread.

 

[alexeiz]

i posted the stock boot.img in another thread.

And it did fix the wifi. Awesome.

 

[nyijedi]

No, only unlocking the fastboot will erase everything. Possibly locking it will also erase everything, but I haven't done that so I'm just assuming. Flashing recovery images should not result in loss of data.

Ah. So it's just the unlocking that erases everything. Thanks a lot for the info.

 

[k0mpresd]

If I use the old koush rootboot.img it works, but no wifi, if I use the stock boot.img, I get no wifi but am able to remount.

i made 2.3.1 kernel with working adb remount: http://xdaforums.com/showthread.php?t=886965

 

[headsh0tshurt]

i received an alert to update about the OTA. I allowed the system to run the update and upon reboot i got the droid logo w/ an exclamation point over its head. I pulled the battery and did a normal boot and everything appears fine...my version is "2.3".

Is this the lastest & greatest? if not, how can i get the OTA on my rooted phone.

 

[GuestD0856]

So if it wont let me rename the install recovery file, do i assume i dont have root?
Followed all the instructions but now it wont let me rename that file.