[Q] Quick summarize [yakju+bootloader+root]

---

Hey everybody,
I'm planning on getting my GN in the next two weeks and wanted to ask a simple question:

first of all - I will want my GN to be a yakju, I will want to root it and I will want to unlock the bootloader.
Now, I believe I have everything understood just wanted to be sure if you could help me..

these are the steps I will take:

1. Check if GN is yakju
1.1 If GN is yakju simply use the gnex toolkit to unlock bootloader and root.
FINISH.

2. If GN is not yakju -
2.1 Use step-by-step (http://forum.xda-developers.com/show....php?t=1391881) to change rom to yakju 4.0.4.
2.3 Then use gnex toolkit to root (already unlocked bootloader in 2.1).
FINISH.

Am I good to go?
TNX!

Pretty much thats the way it should be,,, advance congrats for the next awesome purchase u r going to make,,,

Originally Posted by deepayanneogi

Pretty much thats the way it should be,,, advance congrats for the next awesome purchase u r going to make,,,

Thanks mate! can't wait already

More replies are welcome.. I just want to feel certain I'm on the right track here..

Be a big boy and don't use a tool kit =]
My guide makes it super simple...
Stickied above and linked in my sig.

Originally Posted by Jubakuba

Be a big boy and don't use a tool kit =]
My guide makes it super simple...
Stickied above and linked in my sig.

Hey tnx

I do consider myself an open minded guy and also I usually like to know the bits and insides stuff of things I do, I will usually prefer going the longer way (I.E - rooting\unlocking bootloader) then to just use the toolkit and pressing "next, next, next" because I prefer to know what every "next" does, BUT in this case, I think I managed to (obsessively) learn what everything does, so I decided to take the shorter trip to rooting+unlocking BL, do you think the toolkit has any disadvantages over the longer way?

Originally Posted by omricn

Hey tnx

I do consider myself an open minded guy and also I usually like to know the bits and insides stuff of things I do, I will usually prefer going the longer way (I.E - rooting\unlocking bootloader) then to just use the toolkit and pressing "next, next, next" because I prefer to know what every "next" does, BUT in this case, I think I managed to (obsessively) learn what everything does, so I decided to take the shorter trip to rooting+unlocking BL, do you think the toolkit has any disadvantages over the longer way?

If it works it works.
The thing I hate about 'em is...
If a user has a soft-bricked phone.
Comes on here...asks for help.
And I tell him to do some adb/fastboot procedure: he asks "lul wut?"
And we have to help him set that up...and assume he set it up correctly.

He then might complain "oh, ya. It won't recognize my device."
Which is possible in some soft-brick situations...but it also might be user error.
Thus making trouble-shooting/fixing 10x harder.

Just...do yourself a favor and make sure ADB/Fastboot work.

run "adb devices"
and "fastboot devices"
If both of those recognize your phone...I guess the toolkit is fine.
As you said, you know whats going on...so what's the harm?

That seems about right. Just be a little cautious when flashing a radio or bootloader, as any of those two when flashed wrong can **** your device up beyond self-repair.

An incorrectly flashed system or boot is "easily" fixable, though.

Originally Posted by Theshawty

That seems about right. Just be a little cautious when flashing a radio or bootloader, as any of those two when flashed wrong can **** your device up beyond self-repair.

An incorrectly flashed system or boot is "easily" fixable, though.

Tnx Actually I'm not going to flash custom roms\radios\BL's just yet (if ever), just going to flash the official 4.0.4 yakju from Google, including the radio that comes with that bundle

Originally Posted by Jubakuba

If it works it works.
The thing I hate about 'em is...
If a user has a soft-bricked phone.
Comes on here...asks for help.
And I tell him to do some adb/fastboot procedure: he asks "lul wut?"
And we have to help him set that up...and assume he set it up correctly.

He then might complain "oh, ya. It won't recognize my device."
Which is possible in some soft-brick situations...but it also might be user error.
Thus making trouble-shooting/fixing 10x harder.

Just...do yourself a favor and make sure ADB/Fastboot work.

run "adb devices"
and "fastboot devices"
If both of those recognize your phone...I guess the toolkit is fine.
As you said, you know whats going on...so what's the harm?

I catch your drift, and I know exactly what you mean.. I'm an IT guy, and apart from my job, I always learn everything there is to know about anything before I buy\change it in any way, to always be super safe and know what to do in every situation I can encounter.
Before I do something I will triple check what could and can happen so that I'm always 3 steps ahead. Thats the reason I already know almost everything there is to know about this phone, about rooting it, about unlocking it, ADB, fastboot etc. even before I bought it call me crazy..

Not crazy by my standards.

I actually did the same thing...
Even posted a thread "OMG LULZ SO I DO THIS, RIGHT?" as you have...
Because I was excited as hell and wanted to reassure myself.

You'll love 'er.
Best phone I've owned...by far.

While the OS (and a Nexus on Verizon...which we thought we'd NEVER see) is a HUGE part of it...
I was/am actually impressed with the hardware as well.
I could go on and on and on about my Droid X (Got it on release day...didn't fully understand the implications of a locked bootloader...and how it would hinder the experience over that of my Original Droid) and how much I hated having a locked bootloader.
That was MY main push. I was like...Oh. My. God. A Nexus?! That **** is MINE.

</rambling>

This phone STILL gives me the shivers.
Love it.