[LG Nitro HD] NFleck:
Wow.. Loaded question. :)

Not sure exactly what you mean.. If you searched you'd have found on the very first page of this very sub-forum:

Root LG Nitro HD on ICS

In post # 4 you can see that the method linked worked.. and this was posted

this

month.. Not sure why you have so much trouble finding this info.. It's right here, and if you notice; if that fellow had bothered to search, he'd have found the same info that the first response provided. It's literally all right here. XDA is usually the one-stop-shop for all required info and resources, so long as you're willing to look.

Nevertheless, I've tried both of these methods, and both worked first try for me. However, you usually only have to do this once, and Ive done it both on GB when I first got it, and then again on ics 4.0.4 when I updated like a moron without reading... This was a great example of a "lesson learned" for me.. and trust me, I am better for it.

I don't understand what you're "scared" of... Basically, as long as you follow the guides properly you'll never have a problem..

However, if you are flashing custom ports, or beta release roms that are known to be unstable (it will always say); then your worst "fear" would be having to follow the Unbrick Guide, which shouldn't take more than 30-45 mins tops after the first run-through in which you obtain all the required files. Unless you do something stupid -- usually caused by not following/reading guides properly.. again, most of the time human-error is the only culprit of bricks -- your phone will never be "broken beyond repair."

Warnings are typically clearly stated -- I can't stress this enough: READ READ READ :) (replies, comments, reports, bugs.. all listed in the same thread as the guide itself).

Again, "bugs" and "issues" usually means random reboots, or force closing of apps... Nothing serious. Flashing CM nightly (trusted dev) is very safe IMO.. Flashing custom ports is probably the most risky. but again, nothing an unbrick cant fix in 45 mins or so.

It was more a general look at the rules. Not specifically saying you're like that, I just think he worded it well so I thought I'd share.

Anyways, from my experience as long as you have the drivers properly installed and don't let your antivirus delete the zergrush or other exploit file (because it will), superoneclick has always worked first try for me. However some people report having to try multiple times so just keep trying.

As I said, all rooting guides use pretty much the same exact tools, just worded differently or a different app that does the same thing.

Yes, the official ICS update locks the bootloader so you have to follow the same guide you would if you had "bricked" your phone.

Flashing any ROMs or doing pretty much any modding requires a full wipe. Simply back up your data (I suggest helium).

After you flash a custom recovery (CWM), you can do what's known as a Nandroid backup, which (basically) backs up every last detail of your current running ROM including settings for all installed apps, games, etc. as well as settings for the OS itself, wifi info, etc. -- Let me put it this way, if you restore a nandroid backup, it's as if you never wiped/flashed anything else. This is the best benefit of flashing a custom recov. (IMO) besides flashing roms of course.

Rooting is very non-intrusive.. Unless you have apps that require root, you wouldn't even notice. There's no risk of errors or bricked via root itself, however.. Root means "admin" or "full" access. You will have access to things that are normally hidden/protected from accidental changes.. Similar to the control panel in windows.

As with any computer, If you go deleting things or editing important options like a moron after obtaining root then yes, you will have problems. That's the whole point of why phones don't come with root access.. People who aren't smart enough to figure it out most likely aren't smart enough to handle it.. (Ie. General public).

I'm not sure what you mean by bugs.. It works 100%. Its user error that is the problem.

Google "how to unlock p930 bootloader".. Its clear as day

That's the point.. Read the mantra more closely. The whole point is to try.. You learn by trying.. If you're afraid to get a little dirty sometimes, then this stuff probably isn't for you.

One last tip: Read guides fully before starting and make sure all files are still available/alive. This ensures you don't get stuck half way through. You'll thank me later.

Edit:

PS: mattman was kind enough to make an updated repo for us.. It's on this same sub-forum:

[May 05, 2013] Repository

This contains an updated list of almost all important resources. Just read the guide you're interested in, and like I already said; go to the last page and read every post from the last 3-5 pages if necessary. Most of the time, this is where the latest bugs, and newest updated info is located in

any

thread.. Its very simple. Did you read my post or just skim through it?

PPS: HO!NO! has been kind enough to offer a mirror of all the required files for unbricking, as well as many other useful resources. If you look around you'll find everything you need right here.

Heres the guide you want for rooting official ICS:

Note: Disregard the word "Bell" in the title.. It'd be the same for any provider, so long as you're running a p930 (even then, it probably works for the 935, 936, and su640, etc.)

[GUIDE] How to ROOT Bell official v20e firmware

Here's the guide you want to use for both rooting, and unlocking bootloader if you're going to want to flash a custom recovery and/or roms:

Note: I highly recommend.. Clockworkmod Recovery is

extremely

useful, and nothing beats CM10.1 RC2 + Wind Kernel 2.01 as far as battery life is concerned, and the features JB offers over ICS are simply amazing.. (as long as bluetooth isn't a deal-breaker for you -- this should be fixed soon though.. we're getting very close.)

[GUIDE] Rooting and Unbricking p930/p935/p936

FYI: I found all of this info in a matter of seconds.. This is why it's so frustrating when people ask this every day.. lmao

Good luck.