Related
I don't want to run custom ROMs, I like the Gingerbread from Google and want to easily continue to receive updates.
That being said, I want to be able to run DroidWall and AdFree, and have to have root to do so.
Is there a way to get root, without installing a custom recovery or Clockwork or anything? And still easily receive updates to Gingerbread?
IDtheTarget said:
I don't want to run custom ROMs, I like the Gingerbread from Google and want to easily continue to receive updates.
That being said, I want to be able to run DroidWall and AdFree, and have to have root to do so.
Is there a way to get root, without installing a custom recovery or Clockwork or anything? And still easily receive updates to Gingerbread?
Click to expand...
Click to collapse
I don't think you can apply the su zip file from the stock recovery, but you can try. If it were that easy, there'd be news of it all over the net!
I think you're going to have to unlock the bootloader and then do the fastboot install of CWM.
I'm on stock Gingerbread, but rooted. I prefer CWM to stock recovery...more options, and especially nandroid backup. I got my 2.3.2 update faster than most, because I was still able to push it manually rather than wait for OTA to someday show up, so no issue there, you just have to wait for someone to post its url.
The 2.3.1 and 2.3.2 updates have a script that rewrites stock recovery on top of CWM if you're on either of those, so you get back to stock with each reboot.
If you're running Android 2.3.1 then use http://forum.xda-developers.com/showthread.php?t=882333 to root.
Android 2.3.0 will be GRH55. Paul hasn't updated SuperBoot for Android 2.3.2.
This method definitely works. I performed it while I was testing the device for any hardware defects. I was able to be rooted without changing the recovery. Make sure you have ADB drivers and 2.3 SDK for the Nexus S installed.
IDtheTarget said:
I don't want to run custom ROMs, I like the Gingerbread from Google and want to easily continue to receive updates.
That being said, I want to be able to run DroidWall and AdFree, and have to have root to do so.
Is there a way to get root, without installing a custom recovery or Clockwork or anything? And still easily receive updates to Gingerbread?
Click to expand...
Click to collapse
First and foremost, you should understand that installing a custom recovery will do nothing to block your ability to receive updates from Google nor will it affect your system in anyway. However, if you follow one of the root methods like this one you will install the custom recovery needed to fix permissions to gain root access but if you ignore the step that has you change the name of a file through root explorer, the next time you reboot your custom recovery will be overwritten by the stock one and you will retain root.
Again, its important to know that having a custom recovery allows you to do a lot more than just flash roms. You can do back ups of your NAND memory that allow you to save all of your data, files, settings, et cetera in the case of catastrophic failures or the need to get a replacement handset. If you do a backup maybe once a month and keep them on your computer, you will always be able to restore your phone exactly back to how it was before issues arose.
There is really no downside to having a custom recovery like Clockwork Recovery Mod, but if you are really against it for moral reasons (that is literally the only reason you would not want to install it) then use the method I described and you will be rooted without CWM.
Agreed with what Kenvan said, the Nexus S is a 'unlocked' bootloader phone and considered a "developer phone." The phone is meant to be altered with a bunch of modifications and hacks.
Not sure why you want to cripple your phone by not flashing custom ROMs. They're created to fascinate the Android experience with improvements made to it. But everybody has their reasons, and are entitled to them right?
Just pointing out my 2 cents. Especially when you're on a forum where a large % of the community are here to modify their phones to the highest extent.
zephiK said:
Not sure why you want to cripple your phone by not flashing custom ROMs. They're created to fascinate the Android experience with improvements made to it. But everybody has their reasons, and are entitled to them right?.
Click to expand...
Click to collapse
LOL. Not flashing custom ROMs is hardly "crippling your phone".
That's like saying not installing a turbo-charger is crippling your porsche...
But I agree, once the custom stuff out there is into actual full public-release, I'll be testing it, but meanwhile a Nexus S on Gingerbread stock is a fine experience...BEST experience on any Android I've had, even supercharged Nexus One and Galaxy S i9000 ROMs.
distortedloop said:
LOL. Not flashing custom ROMs is hardly "crippling your phone".
That's like saying not installing a turbo-charger is crippling your porsche...
But I agree, once the custom stuff out there is into actual full public-release, I'll be testing it, but meanwhile a Nexus S on Gingerbread stock is a fine experience...BEST experience on any Android I've had, even supercharged Nexus One and Galaxy S i9000 ROMs.
Click to expand...
Click to collapse
you both make good points. My point was that there its no reason not install a custom recovery, even if one is staying stock
Sent from my Nexus S
I agree. No reason to not use CWM recovery. Google should buy rights to it from him.
IDtheTarget said:
I don't want to run custom ROMs, I like the Gingerbread from Google and want to easily continue to receive updates.
That being said, I want to be able to run DroidWall and AdFree, and have to have root to do so.
Is there a way to get root, without installing a custom recovery or Clockwork or anything? And still easily receive updates to Gingerbread?
Click to expand...
Click to collapse
I'm wondering the same thing myself.
I just found out that it's possible to boot into the Clockwork recovery without flashing it first. I managed to do this by booting into fastboot mode (power + volume up) and then do
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
This was on a stock but rooted 2.3.2, and the bootloader was locked. I didn't try to apply any update.zip, but nandroid backup seemed to work perfectly.
If you don't remove/delete the "/etc/install-recovery.sh" file once you've flashed a new recovery then you *should* find that the default/stock bootloader is re-applied on the first reboot.
As others have mentioned though, there are plenty of benefits to applying a custom recovery although I do understand the reasons you may not want to.
Thanks, all! Okay, maybe I *will* do the Clockwork Recovery then.
The reason I don't want custom ROMs: I had a Vibrant, and was using Team Whiskey's ROMs, and got "Compulsive ROM disorder". Every TW ROM was better than the last, and I found myself flashing every time they came out with a new one.
I'm going to Afghanistan in a couple of months (leaving for some training on Tuesday), and if I can get Internet at all, I won't have the bandwidth to be constantly downloading the newest, coolest ROM. The stock Gingerbread is good enough for me, and I want to keep it. Plus, that way if my wife has problems with her Nexus S while I'm gone, I have another just like it with me to figure out what's wrong with hers.
I just need root to run DroidWall and AdFree so that if I *do* manage to get a data plan out there, I won't run up huge fees because somebody wants me to buy Viagra or something.
Thanks again!
shrivelfig said:
This was on a stock but rooted 2.3.2, and the bootloader was locked. I didn't try to apply any update.zip, but nandroid backup seemed to work perfectly.
Click to expand...
Click to collapse
Wow, that's a great find.
IDtheTarget said:
Thanks, all! Okay, maybe I *will* do the Clockwork Recovery then.
The reason I don't want custom ROMs: I had a Vibrant, and was using Team Whiskey's ROMs, and got "Compulsive ROM disorder".
Click to expand...
Click to collapse
I fully understand that about the Compulsive ROM flashing disorder. I developed a bit of a case of it with the DocRambone ROMs on my Galaxy S i9000. It became a full time job just keeping up with the forum posts in the thread there. Hundreds of posts per day...ugh! But a sweet ROM.
As I'm sure you've ascertained by our other replies to you, having custom recovery is a benefit whether you flash roms constantly or not.
The ability to do a Nandroid and have a nice working backup of your entire system to fall back on is a major plus, as is the ability to wipe dalvik-cache if you're having issues.
Good luck in Afghanistan!
Thanks!
Yes, I've decided to do the recovery for the Titanium backup as well.
Now if I can only get it to work!
I manually updated to 2.3.2 yesterday, then just now started to try rooting using the directions here: http://forum.xda-developers.com/showthread.php?t=895545
But I keep getting a signature error on the SuperUser flash. I'm guessing it has something to do with the new update.
IDtheTarget said:
Thanks!
Yes, I've decided to do the recovery for the Titanium backup as well.
Now if I can only get it to work!
I manually updated to 2.3.2 yesterday, then just now started to try rooting using the directions here: http://forum.xda-developers.com/showthread.php?t=895545
But I keep getting a signature error on the SuperUser flash. I'm guessing it has something to do with the new update.
Click to expand...
Click to collapse
No, the su file should flash just fine, many of us no problems with it rooting on 2.3.2.
Which version of clockwork recovery did you flash? That post was linking to 3.0.0.0, but that one is buggy, and you want to get 3.0.0.5.
Try this one: http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img
Push via fastboot.
distortedloop said:
No, the su file should flash just fine, many of us no problems with it rooting on 2.3.2.
Which version of clockwork recovery did you flash? That post was linking to 3.0.0.0, but that one is buggy, and you want to get 3.0.0.5.
Try this one: http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img
Push via fastboot.
Click to expand...
Click to collapse
No, the problem was that I'm an idiot who hasn't had enough sleep.
I'd flashed that image but wasn't getting into Clockwork recovery. I downloaded ROM Manager and flashed that recovery and was able to update Super User.
Now my problems are (1) I can't rename /etc/install-recovery.sh because it's a read-only file system, and (2) I can't re-install my Astro Pro file manager until Google fixes the market to recognize the new update...
Thanks for the help!
IDtheTarget said:
No, the problem was that I'm an idiot who hasn't had enough sleep.
I'd flashed that image but wasn't getting into Clockwork recovery. I downloaded ROM Manager and flashed that recovery and was able to update Super User.
Now my problems are (1) I can't rename /etc/install-recovery.sh because it's a read-only file system, and (2) I can't re-install my Astro Pro file manager until Google fixes the market to recognize the new update...
Thanks for the help!
Click to expand...
Click to collapse
Try root explorer.
You don't have Titanium Backup to restore Astro...? Every root user should grab that.
You could rename it via adb shell.
Hook up to adb, connect.
run su
remount /system as writable.
use linux mv command to rename it.
I believe you can connect as su to the phone with adb while booted into CWM recovery. Then use CWM menu to mount /system, then do the commands from your computer's terminal or dos shell. Only advantage to this way is you don't have to figure out the proper syntax for remount of /system.
distortedloop said:
You don't have Titanium Backup to restore Astro...? Every root user should grab that.
You could rename it via adb shell.
Hook up to adb, connect.
run su
remount /system as writable.
use linux mv command to rename it.
I believe you can connect as su to the phone with adb while booted into CWM recovery. Then use CWM menu to mount /system, then do the commands from your computer's terminal or dos shell. Only advantage to this way is you don't have to figure out the proper syntax for remount of /system.
Click to expand...
Click to collapse
Couldn't use Titanium backup until I rooted...
Thanks! I used the following command to change permissions:
mount -o remount,rw /dev/block/mtdblock3 /system
Then I:
cd \etc
mv install-recovery.sh install-recovery.sh.000
Looks like I'm set! Although there are still those few apps that aren't showing up yet after the update. Updating the market should be part of Google's checklist when pushing updates...
I've used the SuperBoot method twice and it's exactly what you're looking for. Stock ROM, Stock Recovery, and a rooted device with superuser permission.
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
I'm running stock EE4 but I'm getting ready to root and install one of the debloated ROMs. Currently I have a lot of apps, home screens and ADW Launcher set to my satisfaction and settings tweaked how I like them.
What are "best practices" for pre-rooting backup so all of these are retrievable? I've used Titanium Pro on my tablet so I'm conversant with that process but don't I have to be rooted first? Should I root the phone, install TP, back-up and THEN flash the ROM? Are there alternatives?
Thanks, I await advice.
adw settings you can backup by going to adw settings and doing a backup. Not sure if there is an unrooted version of titanium. Bad part is. You cannot just root if you are EE4 already. 1click and Gingerbreak do not work on EE4. You have to Odin flash a rooted rom. Sorry. Know thats not what you wanted to hear.
dragonstalker said:
adw settings you can backup by going to adw settings and doing a backup. Not sure if there is an unrooted version of titanium. Bad part is. You cannot just root if you are EE4 already. 1click and Gingerbreak do not work on EE4. You have to Odin flash a rooted rom. Sorry. Know thats not what you wanted to hear.
Click to expand...
Click to collapse
Not true. You simply need to use Odin to flash a new kernel which is rooted (pbj by immuts for example). Once you've done this you'll also get CWM. You need to find an Odin package that only contains the kernel.
Once you've done that, with root you can use TiBackup like you've done before and then flash your ROM.
Thanks, fellas. If you're monitoring this thread, would you mind having a look over here?
keithce said:
Not true. You simply need to use Odin to flash a new kernel which is rooted (pbj by immuts for example). Once you've done this you'll also get CWM. You need to find an Odin package that only contains the kernel.
Once you've done that, with root you can use TiBackup like you've done before and then flash your ROM.
Click to expand...
Click to collapse
OK SO, ROOTED means that the ROM has SU capability which is given to it by superuser app. Which allows you to have admin capabilities to change permissions to your filesystem.
The kernel allows you to overclock and undervolt your system while giving access to other HARDWARE specific functions.
Now please explain to me how a KERNEL can give you SuperUser permission to the filesystem if the KERNEL is a bridge between the Hardware and Software. Not saying your wrong, I just don't see how a Kernel can give you root access.
dragonstalker said:
OK SO, ROOTED means that the ROM has SU capability which is given to it by superuser app. Which allows you to have admin capabilities to change permissions to your filesystem.
The kernel allows you to overclock and undervolt your system while giving access to other HARDWARE specific functions.
Now please explain to me how a KERNEL can give you SuperUser permission to the filesystem if the KERNEL is a bridge between the Hardware and Software. Not saying your wrong, I just don't see how a Kernel can give you root access.
Click to expand...
Click to collapse
Indeed, strictly technically speaking you are correct. However after the radio on the charge got updated to EE4 the usual 'back doors' or exploits to get root no longer worked.
Therefore the developers of the kernels for the charge built in the capability to auto root when it boots and hands off the hardware to the software.
If you read the posts for the kernels (e.g. http://forum.xda-developers.com/showthread.php?t=1104634) you would see that.
Cheers!
I stand corrected. It's right there in black and white. Auto-Root on Boot.
We learn something new everyday. Thanks for getting me brought up to speed.
keithce said:
Not true. You simply need to use Odin to flash a new kernel which is rooted (pbj by immuts for example). Once you've done this you'll also get CWM. You need to find an Odin package that only contains the kernel.
Once you've done that, with root you can use TiBackup like you've done before and then flash your ROM.
Click to expand...
Click to collapse
Is flashing a custom kernel, like PBJ, easily done using Odin? Do I use the same procedure when flashing CWM?
The latest version of CWM is not working--the button mapping is all screwed up. So I can't install any .zip files from my SD card -- I just keep seeing this f***ing blue banana.
So do I already need to have CWM installed to install a custom kernel? I'm waiting for someone to post CWM 4.0.0.8 until danalo is able to fix the faulty CWM currently linked for downloading
---Thank you for any help you may provide---
MrMakeIt said:
Is flashing a custom kernel, like PBJ, easily done using Odin? Do I use the same procedure when flashing CWM?
The latest version of CWM is not working--the button mapping is all screwed up. So I can't install any .zip files from my SD card -- I just keep seeing this f***ing blue banana.
So do I already need to have CWM installed to install a custom kernel? I'm waiting for someone to post CWM 4.0.0.8 until danalo is able to fix the faulty CWM currently linked for downloading
---Thank you for any help you may provide---
Click to expand...
Click to collapse
Flashing anything in Odin uses an almost identical procedure unless you're trying to also upgrade the baseband/radio/modem.
Yes, you can flash a kernel using Odin. You just have to make sure that you download the right file to be flashed because it must be in specific format (*.md5).
Here is a link to jt's kernel from this post. Its a root kernel with CWM and also includes the lagfix (reformat to EXT4) that you should be able to flash using Odin.
That should give you a working (although limited functionality) version of CWM so that you can then install everything else and upgrade when a newer working version of CWM comes out.
Basically you just need to get CWM on there once as a starting point and then you can upgrade, update, and do whatever you want from there.
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
Background:
I got myself a second-hand I9020T a couple of days back which had CWM recovery and a 4.0.4 Userdebug testkeys build on it. As circumstances turned out, I flashed the phone to the factory 4.1.2 (from https://developers.google.com/android/nexus/images), but didn't note down the details of the old 4.0.4 ROM.
I rather like stock roms. However, I like stock roms with root even more.
Questions:
I wanted to know if there was any method to root my Nexus S without resorting to using ClockworkMod recovery? I'm hoping for a z4root kind of method which doesn't mess around with the boot loader.
Does such a method even exist.
I'm hoping that I don't have to mess around with the boot loader, yet get root access and all the power to do direct querying of my SMS DB.
Note: I can install CWM recovery, but I'd rather not. It's just the superficial choice I'm making, not a well informed decision.
samveen said:
Background:
I got myself a second-hand I9020T a couple of days back which had CWM recovery and a 4.0.4 Userdebug testkeys build on it. As circumstances turned out, I flashed the phone to the factory 4.1.2 (from https://developers.google.com/android/nexus/images), but didn't note down the details of the old 4.0.4 ROM.
I rather like stock roms. However, I like stock roms with root even more.
Questions:
I wanted to know if there was any method to root my Nexus S without resorting to using ClockworkMod recovery? I'm hoping for a z4root kind of method which doesn't mess around with the boot loader.
Does such a method even exist.
I'm hoping that I don't have to mess around with the boot loader, yet get root access and all the power to do direct querying of my SMS DB.
Note: I can install CWM recovery, but I'd rather not. It's just the superficial choice I'm making, not a well informed decision.
Click to expand...
Click to collapse
You don't have to mess with the bootloader itself, just the recovery.
And no, you will need a custom recovery to flash chainsDD superuser or chainfire SuperSU. There's TWRP also available and popular, if you simply do not like CWM.
polobunny said:
You don't have to mess with the bootloader itself, just the recovery.
And no, you will need a custom recovery to flash chainsDD superuser or chainfire SuperSU. There's TWRP also available and popular, if you simply do not like CWM.
Click to expand...
Click to collapse
Is is possible to install the SU update (whichever of the 2) and go back to the stock recovery?
samveen said:
Is is possible to install the SU update (whichever of the 2) and go back to the stock recovery?
Click to expand...
Click to collapse
Yes. I don't see why would one want to do that, but that's possible.
Once you're done with your flashing, you can flash stock Jellybean recovery from here:
http://forum.xda-developers.com/showthread.php?t=2032337