Quote:
Originally Posted by RichTJ99
Great guide, I am about to get started. I was curious, if I do this method, can I install various roms once I am done?
|
Yup, flash yer brains out!
I posted this in OMJ's thread but figures it was worth a repost here. What is full root.
Originally Posted by frankenstein @ xda:
Quote:
|
Originally Posted by frankenstein
There are a couple of key things that it does. First it unlocks the bits of your system that remain locked via nand. basically the system is being told to mount certain directories like /system as read only and not let you remount it as RW. This means your rooted but not completely because you can't re-mount these directories as RW under the android os. Doing this will allow you to remount /system as RW or read/write under the andriod os which will allow you modify things in the /system/app directory letting you clean up bloatware you don't want without having to boot into recovery to do so. (Among other things... that's just a good example of what this gives you.)
The second key thing it does is flash a custom recovery image, basically the same one you load now via toast's recovery-windows.bat process, that you can boot into directly from the HBOOT menu. This means that when you want to flash a new ROM or do a nandroid backup, you don't have to go find a computer with the android sdk and toast's evo-recovery.zip extracted on it to run recovery-windows.bat in order to do so. you can dl a new rom directly to your devices sd card and go to town or boot directly into recovery and run your nandroid backup without needing a computer and the previously mentioned tool set to do so. This was also prevented by the nand locking that this process overcomes.
in short, part 1 gave you root but only about 1/2 of it. You could run apps that require su/root but you can't modify key parts of the system that you should have access to as root. Part 2 completes the root process giving you 100% control of your system without having to jump through hoops to achieve it.
|