Database Info

[GUIDE]Updating to 4.22.651.2 OTA WITHOUT flashing a new ROM or wiping your Phone

This assumes you:
- Have the latest FROYO OTA installed 3.70.651.1
- Have some experience working with flashing things in recovery
- Have NOT deleted/uninstalled ANYTHING in /system
- Have defrosted any bloat you froze with Bloat Freezer or Ti Backup Pro
- Have S-OFF (Used Unrevoked Forever or a version of Unrevoked3 that includes Forever)
OK now let us get to it.
1. Go ahead and download the OTA like normal on your phone, but DO NOT install it.
2. Using a file manager copy the OTA zip file from /cache to /sdcard
3. Using Rom Manager, flash Amon RA Recovery 2.3 (Down at the bottom)
4. In Rom Manager, click the Reboot into Recovery button.
5. Select apply zip from SD Card and flash the OTA zip file that you put in /sdcard
--10 Minutes later.....you now have the UNROOTED OTA installed just as if you installed it normally--
6. Download the 2.6.0.1 ClockWorkMod Recovery zip from here and place it in the root of your SD card
7. Under settings > applications > disable FastBoot (re-enable this when you are done with the whole process)
8. Power off and reboot holding Volume down. The bootloader will scan and then will and ask you to press Volume up to install. Reboot.
9. Delete the PC36IMG.zip file from your SD card and place the attachment below in the root of the SD card.
10. Power off and reboot holding Volume down and then select recovery to start CWM recovery.
11. Choose apply zip from sd card. Choose select zip on sd card. You will see the SU file on the list, flash it to root your phone. Reboot.
You should now be rooted and can upgrade the recovery now to whatever style and version you want!
Enjoy! Please click the THANKS button if it worked for you!
----------------------------------------
Developer of Bloat Freezer - Freeze Your Pre Installed System Apps in One Click
Bloat Freezer - Android Market Link

Very cool!!

Great info ..hey if I follow these steps and skip the last part will my phone be stock / uprooted and good to go.for a trade in or repair? I've been trying to figure out the best way to unrest when.e3d comes out

I never updated to 3.70. I'm assuming I can do that the same way, root again, download the gingerbread, and root again?
I'm thinking it might just be easier to flash the rooted ROM and radios, but I'm not sure what's best.

if you have amon ra recovery (and a stock rom), you can simply download and click install.
I clicked install, amonra booted up, detected and ran update, click reboot, then the stock recovery will be active and updates the radios, once back in to sense, you can reinstall amonra or clockwork, then SU
worked for me.
http://forum.xda-developers.com/showthread.php?t=1109230

im curious why the title says "WITHOUT flashing a new ROM" yet you are clearly flashing the rom in amon ra. sorry just got to nit pick

what happens if you have deleted some system apps. Such as nova and blockbuster. I saved the APKS on the SD card however but I did delete them?

JMQUINT00 said:
what happens if you have deleted some system apps. Such as nova and blockbuster. I saved the APKS on the SD card however but I did delete them?
Click to expand...
Click to collapse
Well I wouldn't want to try it unless your prepared to do a full ruu reset if it fails.
the OTA is like a patcher, it deletes unneeded files, adds new files, and updates existing files... if its not completely stock it may (or may not) cause an error which the updater can't handle, and then you may be left with a half upgraded system.
if you nandroid *before* downloading the ota, you should always be able to go back, assuming you have perm soff from unrevoked forever.

it should run whether you have removed files or not. if it tries to delete a file that does not exist the script will just skip it. op i think you have bit of confusion going on though. you were only able to reattain root because you are s-off from unrevoked forever. if you are not s-off and do your method, which is no different then just excepting the ota and letting it do its thing btw, you will loose root until this new ota is cracked. just fwi, there was no "magic" from you flashing manually, the same script is ran and the same files are moved and patches are made regardless.

cant I reinstall the apps and put the apks in their original system folder?

DomSim said:
it should run whether you have removed files or not. if it tries to delete a file that does not exist the script will just skip it. op i think you have bit of confusion going on though. you were only able to reattain root because you are s-off from unrevoked forever. if you are not s-off and do your method, which is no different then just excepting the ota and letting it do its thing btw, you will loose root until this new ota is cracked. just fwi, there was no "magic" from you flashing manually, the same script is ran and the same files are moved and patches are made regardless.
Click to expand...
Click to collapse
Lol OK so which one is it? Can n just accept the ota and run? I'm rooted on stock rom, but I deleted nova and blockbuster from the system? I know I will loose root which I got by using unrevoked 3, but I just want to know if I can do it without bricking the phone. Ty

JMQUINT00 said:
Lol OK so which one is it? Can n just accept the ota and run? I'm rooted on stock rom, but I deleted nova and blockbuster from the system? I know I will loose root which I got by using unrevoked 3, but I just want to know if I can do it without bricking the phone. Ty
Click to expand...
Click to collapse
shouldn't be any worry about bricking but make 100% sure you are s-off from unrevoked forever and you should be able to re-root pretty much how the op outlined.

im currently running cm7. if i go back to a rooted stock froyo rom, will this work???

confused. I just don't understand why you wouldn't download the rooted version of the ROM from here on XDA and just flash it like a normal rom. Maybe I'm overtired and missing the point.
To me, its like this. If you're rooted, and want an OTA update, just wait for the devs at XDA to go through it and root it, and make it available for download. Then just download it and flash it. You get the same exact update that way, as if you took the OTA from sprint. Except this way you don't risk losing root, and your good to go.
If you're not rooted and your phone is stock, accept OTA like normal.
I don't understand why all this extra stuff needs to be done, and add more to the confusion. If your rooted, updating to the latest is simple. Download it and flash it in recovery.

DaEXfactoR said:
im currently running cm7. if i go back to a rooted stock froyo rom, will this work???
Click to expand...
Click to collapse
Just download the update from here http://forum.xda-developers.com/showthread.php?t=1038701
Do a full wipe and flash like any other rom you've ever flashed before. You'll then be on the latest and greatest . (you'll probably be going right back to CM)
EDIT: and to the OP, sorry that I don't agree with you. I just find it more confusing that way, and I guess that whatever the point of doing it that way is, is sailing miles above my head.

k2buckley said:
confused. I just don't understand why you wouldn't download the rooted version of the ROM from here on XDA and just flash it like a normal rom. Maybe I'm overtired and missing the point.
To me, its like this. If you're rooted, and want an OTA update, just wait for the devs at XDA to go through it and root it, and make it available for download. Then just download it and flash it. You get the same exact update that way, as if you took the OTA from sprint. Except this way you don't risk losing root, and your good to go.
If you're not rooted and your phone is stock, accept OTA like normal.
I don't understand why all this extra stuff needs to be done, and add more to the confusion. If your rooted, updating to the latest is simple. Download it and flash it in recovery.
Click to expand...
Click to collapse
I see your point. I guess I am anxious. So there will be a stock ROM that is rooted, thats what I was wondering. I wasnt sure if every ROM would be customized somewhat...Thanks

DaEXfactoR said:
I see your point. I guess I am anxious. So there will be a stock ROM that is rooted, thats what I was wondering. I wasnt sure if every ROM would be customized somewhat...Thanks
Click to expand...
Click to collapse
That link I supplied a couple posts up is a completely 100% stock and rooted version of the OTA update.
This is from the first paragraph of the first post of that thread.
"Stock 4.22.651.2 ROM, rooted and ready for your flashing pleasures. This is a completely stock ROM that has had nothing done to it outside of rooting & deodexing, it's not even zip aligned yet (sorry DrMacinyasha)
As always make sure your wipe your dalvik and create a nandroid before flashing."

k2buckley said:
That link I supplied a couple posts up is a completely 100% stock and rooted version of the OTA update.
This is from the first paragraph of the first post of that thread.
"Stock 4.22.651.2 ROM, rooted and ready for your flashing pleasures. This is a completely stock ROM that has had nothing done to it outside of rooting & deodexing, it's not even zip aligned yet (sorry DrMacinyasha)
As always make sure your wipe your dalvik and create a nandroid before flashing."
Click to expand...
Click to collapse
thanks for your insight. only thing I am confused on at this point is why there are kernels listed to flash from May just below it? wouldnt the htc stock kernel from the ota be in this rom already? seems like alot of folks are looking for newer kernels to flash after flashing xhaus rom. Any insight would be great. thanks again!

rileyd5 said:
thanks for your insight. only thing I am confused on at this point is why there are kernels listed to flash from May just below it? wouldnt the htc stock kernel from the ota be in this rom already? seems like alot of folks are looking for newer kernels to flash after flashing xhaus rom. Any insight would be great. thanks again!
Click to expand...
Click to collapse
I was a little curious about why those kernels were linked there too. I honestly haven't really kept up with thread, because I don't have an interest in flashing the update to begin with. I noticed those kernels are from May 4th, so it doesn't seem like they'd be the most current one. Without reading that thread, I first would've presumed that the kernel that comes with the rom would be the one to use. So, you've read through the thread and you're seeing that people are having trouble with the kernel that the rom comes with?? I'll take a gander over in the thread in a few minutes and see what I make out of it.

Well I f'd up and installed the latest update straight from sprint, instead of waiting for the rooted version to come out. I guess I thought I would find something exciting, but now I would realize it was kind of worthless and want to go back to a different rom like miui or vaelpak. I am s-off with unrevoked. Is there some combination of the steps listed I can use to back out of this?
Let me take a guess...did this update my radios and hboot to a version that would be incompatible with these roms?

[ROM] ASUS rooted firmwares repackaged for ClockworkMod recovery

NOTICE
The method described is now obsolete.
Thread closed.
The only suggestion I would have is to make ClockWorkMod compatible directly with ASUS ROMs (previous and new format: patches + BLOB), as the previous idea is both inadequate or extremely inefficient.
Original first post:
Hi fellow Transformer adopters
After writing an Asus firmwares repacking tool for personal/dev usage, I repacked some official Asus ROMs in ClockWorkMod recovery update.zip formats.
Uploaded here on my server:
http://dl.project-voodoo.org/transformer-roms/
Those are unmodified but rooting is automatically applied in the flashing process without requiring manual intervention.
What's flashed:
- Everything (Kernel, system, additional stuff)...
- except of course the recovery, this way you keep your previously installed custom recovery.
What's needed:
- Only requirement: any custom recovery capable of flashing unsigned standard update.zips, like this one
- As long as the custom recovery is here, there is no prior-rooting requirement.
Requests to repack missing ROMS are welcome if accompanied by download links.
Happy flashing ^^

Hi, I'm new to Asus Transformer, but these are 3.0 ROMS? Do you have 3.1?
And am I correct in saying, that if I flash old 3.0, I can then get clockwork mod on there, and then flash one of these to get a stock ROM but rooted? (I'm guessing I would need SuperUser.APK to install).

CrazyPeter said:
Hi, I'm new to Asus Transformer, but these are 3.0 ROMS? Do you have 3.1?
And am I correct in saying, that if I flash old 3.0, I can then get clockwork mod on there, and then flash one of these to get a stock ROM but rooted? (I'm guessing I would need SuperUser.APK to install).
Click to expand...
Click to collapse
repacked-8.4.4.5_US+root-CWR-update.zip is a 3.1 ROM.
May I rename the files for faster recognition?
And yep that's the idea. Once you get the custom recovery, you can flash any ROM this way.
The lack of proper flashing tool is really annoying but those ROMs are here to make the whole rooting+flashing process a bit easier in the end for most people.

i'm slightly confused by what this does.
i see that these are stock roms with root, however does that mean that, if you are on pure stock 3.1 and you flash your rooted 3.1 rom over it. we then get a 3.1 rooted rom without wiping everything?
or is it a case of it will root the rom but wipe everything? or will it just not flash over a stock 3.1 rom?
thanks for all the help!

I would like to understand this more too. I want to root my 3.1 install and add custom recovery. Well the recovery first then root!

As long as the custom recovery is here, there is no prior-rooting requirement.
Click to expand...
Click to collapse
How does one install CWM without prior root?
Putting on CWM and then flashing a prerooted room seems like a very easy way to get root if there is a way to just install the CWM apk.
--dyst

drdystopia said:
How does one install CWM without prior root?
Click to expand...
Click to collapse
That's what I'd like to know. I'm on 3.1 now, and I understand how to downgrade, root, install CWM and re-upgrade, but that's a lot of effort if this really requires no previous root.

I believe these packages make it easier for you to go from rooted 8.x.y.z to rooted 8.x.z.z, without having to worry about CWM getting overwritten. It doesn't help you root.

drdystopia said:
How does one install CWM without prior root?
Putting on CWM and then flashing a prerooted room seems like a very easy way to get root if there is a way to just install the CWM apk.
--dyst
Click to expand...
Click to collapse
You have to be rooted previously.
What you're waiting for is someone to release the SBK, so we can use NVflash.

10ks Supercurio
just wait for your developing skills implement in TF

So I'm running 3.1 and dont want to downgrade to root and I have heaps of stuff on my tf,dies these mean 3.1 Rom is rooted ?
LEEDROID GB3.0.1DESIRE HD using XDA PREMIUM

I have a quick question:
I downgraded from 3.1 to 3.0, rooted, and installed CWM. When I rebooted I was rooted with the superuser app. I then installed the repacked 8.4.4.5 rom linked in the first post and rebooted. After the reboot, I no longer have the superuser app. How can I tell if I'm still rooted?
**EDIT**
I confirmed the ROM linked above for 8.4.4.5 is indeed rooted. I was trying to use titanium backup but it kept failing to gain superuser permissions. You'll need to manually install superuser (and busy box) from the market after flashing this rom.

combat goofwing said:
So I'm running 3.1 and dont want to downgrade to root and I have heaps of stuff on my tf,dies these mean 3.1 Rom is rooted ?
LEEDROID GB3.0.1DESIRE HD using XDA PREMIUM
Click to expand...
Click to collapse
There are rooted 3.1 roms avaiable yes. To use them you need custom recovery which can only be
install if you're rooted. So you have to downgrade first to gain root then upgrade bck to 3.1 rooted rom.
Sent from my Transformer TF101 using Tapatalk

supercurio said:
repacked-8.4.4.5_US+root-CWR-update.zip is a 3.1 ROM.
May I rename the files for faster recognition?
Click to expand...
Click to collapse
That may help, or put them in Android 3.0, Android 3.1 sub directories.
Any chance of a WW 3.1 ? Then i'm gonna give it a go.....

kingwp1 said:
I have a quick question:
I downgraded from 3.1 to 3.0, rooted, and installed CWM. When I rebooted I was rooted with the superuser app. I then installed the repacked 8.4.4.5 rom linked in the first post and rebooted. After the reboot, I no longer have the superuser app. How can I tell if I'm still rooted?
**EDIT**
I confirmed the ROM linked above for 8.4.4.5 is indeed rooted. I was trying to use titanium backup but it kept failing to gain superuser permissions. You'll need to manually install superuser (and busy box) from the market after flashing this rom.
Click to expand...
Click to collapse
Does Titanium backup require su binary be located in /system/bin instead of being in PATH? (I install the su binary in /system/xbin)

CrazyPeter said:
That may help, or put them in Android 3.0, Android 3.1 sub directories.
Any chance of a WW 3.1 ? Then i'm gonna give it a go.....
Click to expand...
Click to collapse
If you tell me where to download WW 3.1, sure I just don't where to find it

supercurio said:
Does Titanium backup require su binary be located in /system/bin instead of being in PATH? (I install the su binary in /system/xbin)
Click to expand...
Click to collapse
I don't honestly know. I just searched for superuser app in the market and downloaded and installed it normally. After you install it, you actually have to open the SU app first in order for Titanium Backup to work. Here's the app I installed:
https://market.android.com/details?id=com.noshufou.android.su
This is the version that came installed in all the roms I've ever used on my Captivate, so I figured I'd give it a try. It worked for me!
Before installing SU, Titanium Backup was unable to gain superuser permissions. Everything I've mentioned is what I've done after installing your repackaged stock rom for 3.1 and nothing else.

Oh that's right, I don't install Superuser apk correctly, I'll fix that.
So far the most important is that su binary is there already, this is the hard part

Does that mean you're going to repackage the repackaged firmware?
If so, would you recommend I reflash your new version over your previous version?

kingwp1 said:
Does that mean you're going to repackage the repackaged firmware?
If so, would you recommend I reflash your new version over your previous version?
Click to expand...
Click to collapse
Lol yeah I will
No need to reinstall anything though, you can have the exact same by installing Superuser from market like you di

[Q] Restore stock kernel and unroot?

All - There is absolutely nothing wrong with my TF101 but I am getting annoyed at the Asus Update notices and wanted to know if there was a way to go back to a stock kernel and then un-root for the update before re-rooting and switching back to a custom kernel. All without loosing my data/config/etc.
I have seen how to un-root but not restore a stock kernel.
I assume it is possible and I am simply trying to walk a thin line that no one else cares to do!
Thanks if you can help and if my search skills failed me I apologize.

use titanium backup, freeze the app DMClient, no more update

Thanks - that is one solution to try.

That stopped the update notice - but as I fall farther and farther behind on versions (8.6.5.6) the OC and CWM are not really worth it, or more specifically I do not want to have to rebuild my install after a full flash/wipe.
Amy idea's?
Thanks

So what configuration do you want to have in the end? Latest firmware, rooted, with a custom kernel? and no more update notifications?

I suppose there are a few ways to go about this:
1) download the stock 8.6.5.13 firmware from the asus website and use that to upgrade. It will also flash the stock kernel. You can wait for the OTA and afterwards, re-root and apply a custom kernel. You might have to flash the stock recovery to get the update to flash or you can use adb and CWM to get it to flash.
2) my favorite- download the 8.6.5.13 firmware and the OTA and repackage them into a rooted rom. It's like a new rom and a puzzle all in one. You can even add a custom kernel to get everything in one shot.
Both of these should keep your data partition intact.
The fine line is more like a limbo - you have to either choose to revert to stock every time you want to upgrade and hope that the update doesn't fail. Or, you can take advantage of root privileges so that you can load custom roms, even if they are just rooted versions of the stock firmware.

gee one said:
2) my favorite- download the 8.6.5.13 firmware and the OTA and repackage them into a rooted rom. It's like a new rom and a puzzle all in one. You can even add a custom kernel to get everything in one shot.
Click to expand...
Click to collapse
Sounds like a plan - tips or source for the too dumb to fail instructions?
Thanks!

Download the 8.6.5.13 firmware from ASUS. Choose android/firmware and download the country specific firmware for 8.6.5.13 (or latest firmware)
Unzip it and it will be an ASUS folder with some goodies inside. Copy the whole folder onto your externel sdcard. Insert the sdcard into your TF and it should recognize the update. Apply it and you'll have stock 8.6.5.13. Check for updates and apply it. Re-root and update you kernel and you should be good to go.
Link for firmware:
http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download
sent from my cyanogen(mod) vision

Im just wondering; will this method work with a custom rom? I currently have a Modaco custom ROM, but this is based on .9 firmware.
Im happy to resort to the method above if it will let me progress to the latest firmware (which i can then re-root afterwards) but keep my data intact.
Thanks for your advice.

I don't know if the custom rom will recognize the firmware. If it does, it should work.
As far as rolling your own, I'm not sure there are any step by step instructions from start to finish. You'll need to know how to:
1) root a rom (adding su and Superuser.apk)
2) package a flashable zip file (including updating the updater-script)
3) manipulate a rom to add/remove things like kernels, system firmware, etc.
4) pack/unpack boot and other android! magic files
5) pack/unpack blob files
6) (optional) deodex a rom

gee one said:
As far as rolling your own, I'm not sure there are any step by step instructions from start to finish. You'll need to know how to:
1) root a rom (adding su and Superuser.apk)
2) package a flashable zip file (including updating the updater-script)
3) manipulate a rom to add/remove things like kernels, system firmware, etc.
4) pack/unpack boot and other android! magic files
5) pack/unpack blob files
6) (optional) deodex a rom
Click to expand...
Click to collapse
OK - sounds like my desire exceeded my ability by many a mile.
Thanks for the other suggestion - I think that plus Titanium Backup and a little bit of time should do it.

Bone STOCK UCLA3 2.3.6 ROM ?

Does anyone have or know where to get this update. Iam looking for the actual OTA, unmodified, untouched rom. I figure they would have it posted in these forums, but all i am finding is modified ucla 2.3.6.

right now, both cdshepherd's and silver03wrx's 2.3.6 UCLA3 roms are 'stock'. I guess it depends on what you mean "bone stock". Both of their roms were directly extracted from the system dump of the recent ATT OTA update. As a matter of fact silver and others were able to extract the stock UCLA3 modem and UCLA3 kernel and package them up as separate zips... their roms now have the kernel baked in as well. cd and silver will most likely be taking their roms and customizing (i.e., theming, new features, debloating etc), but for now (2/25/12), they are both based on same stock system dump.

Think he means a rom that's not rooted, untouched, unthemed, etc. I'm honestly looking for the same thing... A UCLA3, untouched rom that you can flash in CWM would be nice.
Only thing is that I believe they needed root access in order to pull the rom from their phone after they updated, so all the builds they pulled/copied from their phone have root.

Fortune090 said:
Think he means a rom that's not rooted, untouched, unthemed, etc. I'm honestly looking for the same thing... A UCLA3, untouched rom that you can flash in CWM would be nice.
Only thing is that I believe they needed root access in order to pull the rom from their phone after they updated, so all the builds they pulled/copied from their phone have root.
Click to expand...
Click to collapse
Amen, yes that is what I would like too. Although I am not sure it would be possible to get that without root? A "dd" command would need root, and also a new recovery (if going the nandroid route). I would be curious as to how to take a "dump" of all partitions without being rooted.

i believe this rom has the att bloatware removed.
http://forum.xda-developers.com/showthread.php?t=1509978

Rooting Nexus S [Help]

A while back, I always rooted and unrooted my Nexus S with no problems at all. Now whenever I try to root it, it just goes wrong. I've tried TWRP & CWM, CWM used to always work but now it just messes up. Both TWRP and CWM both give me an error that say Installation Aborted when I try to install a custom rom. I've redownloaded the rom from different browsers and even different PCs but nothing working, still that same error. Does anyone have a guide that is 100% to work without any errors during the process?

What guide are you using?

paul96 said:
What guide are you using?
Click to expand...
Click to collapse
I used this one: http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/

1. Make sure you're running one the more recent versions of the custom recovery. You probably are but there are issues with older versions so just make sure.
2. Boot into what ever recovery you pick and do a full wipe. That is everything gets wiped but your SD card. Factory reset. Format /system etc.
3. Flash your ROM and gapps if they are seperate.
You should not get any errors. If your recovery is current and your flashing a new rom onto a fully wiped system and you still get a error either you're screwing something up or you may have a hardware problem.
To rule out a hw problem flash the factory images with fastboot. If those flash normally and everything works it is almost certainly user error.

albundy2010 said:
1. Make sure you're running one the more recent versions of the custom recovery. You probably are but there are issues with older versions so just make sure.
2. Boot into what ever recovery you pick and do a full wipe. That is everything gets wiped but your SD card. Factory reset. Format /system etc.
3. Flash your ROM and gapps if they are seperate.
You should not get any errors. If your recovery is current and your flashing a new rom onto a fully wiped system and you still get a error either you're screwing something up or you may have a hardware problem.
To rule out a hw problem flash the factory images with fastboot. If those flash normally and everything works it is almost certainly user error.
Click to expand...
Click to collapse
Alright, thanks Do you recommend that I root my Nexus S or should I wait for the Jelly Bean update? I've rooted before and I enjoyed it but now I don't see that many reasons to root, do you have any good reasons?

I have many. My reasons for root don't matter. If you don't have a reason for root then don't root. Its that simple really.
Make sure you're on a stock 4.0.4 rom. When the ota is out install it.
If you want just root on either os at any time just flash su.zip from custom recovery. Its that simple. Having root on a stock rom does not affect the ota process.

albundy2010 said:
I have many. My reasons for root don't matter. If you don't have a reason for root then don't root. Its that simple really.
Make sure you're on a stock 4.0.4 rom. When the ota is out install it.
If you want just root on either os at any time just flash su.zip from custom recovery. Its that simple. Having root on a stock rom does not affect the ota process.
Click to expand...
Click to collapse
What are your reasons for root? Please share?

Getting rid of stuff I don't want in a ROM.
Apps that do things that require root.Titanium backup/autoruns adaway ( ad blocker app alone could be its one point) etc
Changing kernel settings. Bid/bin clocks volts etc.
Being able to have a replacement launcher use the ICS style widget drawer.
Lastly , I simply just can't see having a computer that I don't have root/admin rights to. Its my damn device and I do what I want.

albundy2010 said:
Getting rid of stuff I don't want in a ROM.
Apps that do things that require root.Titanium backup/autoruns adaway ( ad blocker app alone could be its one point) etc
Changing kernel settings. Bid/bin clocks volts etc.
Being able to have a replacement launcher use the ICS style widget drawer.
Lastly , I simply just can't see having a computer that I don't have root/admin rights to. Its my damn device and I do what I want.
Click to expand...
Click to collapse
Oh cool. There is this project that some members from XDA are working on called Sense4All and they are porting Sense to many devices. Im probably going to wait until a fully functionable release is available for the Nexus S. I do like AOKP a lot, so that might be a reason for why I'll root.

You seem to be a little confused with some terms. Root is simply being able to grant superuser permission.
You don't need to root to flash a custom rom on a nexus. Just a unblocked bootloader. You could run aokp or any other rom without root if you wanted to.

albundy2010 said:
You seem to be a little confused with some terms. Root is simply being able to grant superuser permission.
You don't need to root to flash a custom rom on a nexus. Just a unblocked bootloader. You could run aokp or any other rom without root if you wanted to.
Click to expand...
Click to collapse
Oh, I never knew that, haha. Is it possible to flash a custom kernel with an unlocked bootloader or does that require root access?

m1l4droid said:
No you just need a custom recovery. But using that kernel's mods, like BLN, OC, UV, touchwake, etc, requires apps that need root, like NSTools, SetCPU, etc.
Click to expand...
Click to collapse
Oh alright. Now I really wanna root + install a custom rom. Do any of you have a full 100% fully working guide for rooting Nexus S and which rom should I flash first? I already know what kernel I want.

http://forums.acsyndicate.net/showthread.php?2024-ACS-Nexus-S-One-Click-Root-V4-0

leap_ahead said:
http://forums.acsyndicate.net/showthread.php?2024-ACS-Nexus-S-One-Click-Root-V4-0
Click to expand...
Click to collapse
Thank you so much! I rooted my phone with CWM recovery installed and Paranoid Android + gapps installed