Develop Bugs

BRICKED Galaxy Nexus - please help me restore/advice

Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
This ISN'T Resolved. I get errors when attempting to fastboot the stock image
~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'
If anybody has any ideas please let me know, I really don't know what to do at this point.

grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Okay your bootloader is unlocked which is good, but your MAC doesn't see your phone in bootloader mode?

grnmons said:
Plan B is to use a PC which I can only access later in the week.
Click to expand...
Click to collapse
Can you bootcamp or use a virtual machine?

grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Wrong section..but
I would def use a PC and use Odin ! Make your life easier...it takes like 3-5 Mins..takes it to stock!
Sent from my Galaxy Nexus using xda premium

All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Sent from my Galaxy Nexus using Tapatalk

Please uninstall and reinstall your phones drivers. Your just soft bricked is all. Once your computer sees the device you should be good.
sent from the Almighty One himself....

borgey said:
All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Click to expand...
Click to collapse
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?

grnmons said:
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?
Click to expand...
Click to collapse
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html

zephiK said:
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html
Click to expand...
Click to collapse
Thanks. Can you confirm that these are the steps?
1) Download the latest stock image( i will leave finding that image to you since this post can become outdated)
2) Unzip the files, and place the images into the adb-fastboot folder you created on your desktop above.
3) Open a terminal and use the following commands:
Code:
~/Desktop/adb-fastboot/adb reboot bootloader
4) Wait for bootloader to reboot on phone.
5) Then, in terminal use the following commands:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
~/Desktop/adb-fastboot/fastboot flash system ~/Desktop/adb-fastboot/system.img
~/Desktop/adb-fastboot/fastboot flash recovery ~/Desktop/adb-fastboot/recovery.img
~/Desktop/adb-fastboot/fastboot flash userdata ~/Desktop/adb-fastboot/userdata.img
~/Desktop/adb-fastboot/fastboot erase cache
~/Desktop/adb-fastboot/fastboot oem lock
6) Reboot to System, and you should be returned to Stock and Unrooted

~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'

anybody have any other suggestions to this? or a follow up?

It should be easy to fix. You do not seem to have the correct driver installed.
Sent from my Galaxy Nexus using xda premium

Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.

grnmons said:
Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.
Click to expand...
Click to collapse
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)

ogdobber said:
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)
Click to expand...
Click to collapse
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?

grnmons said:
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?
Click to expand...
Click to collapse
download the gnex-su.zip and put in in the root of your sd card. then in recovery select "-install zip from sdcard" then "-choose zip from sdcard" then select the gnex-su.zip. this will give you root and install the superuser app

not to get ahead (previous post), but after your computer recognizes the phone you need to flash clockwork recovery
you need to open a terminal in the platform-tools folder of the sdk (also put the recovery.img there) and then
Code:
fastboot flash recovery name-of-recovery.img

Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Just got your last post, I'm unfamiliar with SDK but I've since put the recovery file in there, not sure how to flash recovery. I have tried flashing recovery through terminal and surprisingly it says "-bash: fastboot: command not found"

grnmons said:
Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Click to expand...
Click to collapse
that is for the nexus s
check your pm

ogdobber said:
that is for the nexus s
check your pm
Click to expand...
Click to collapse
If you are still having problems ...like I said before ...use Odin......since the simple process of fastboot is not working properly for you.Odin makes things so Much easier
Sent from my Galaxy Nexus using xda premium

[Q] Phone only starting in Clockwork and Fastboot

After attempting to install franco kernel, my nexus was stuck at the Google logo upon startup. After attempting to recover via clockwork recovery, I found it to be missing (temporary install perhaps?). Currently I have installed clockwork recovery via nexus toolkit. The problem I am now trying to address is that I have no way of putting .zip files on my phone. Some Google searches did not come up with anything quite like this. I am new to this, so any information is good information. Thanks in advance

luminuss3 said:
After attempting to install franco kernel, my nexus was stuck at the Google logo upon startup. After attempting to recover via clockwork recovery, I found it to be missing (temporary install perhaps?). Currently I have installed clockwork recovery via nexus toolkit. The problem I am now trying to address is that I have no way of putting .zip files on my phone. Some Google searches did not come up with anything quite like this. I am new to this, so any information is good information. Thanks in advance
Click to expand...
Click to collapse
Your boot image is missing...
When your phone boots in bootloadermode, it should (now, anyway) say: boot.img missing. Or something of that nature. Check this, flash it via fastboot, then everything should be back to normal...
EDIT:
It works with both: CDMA & GSM

luminuss3 said:
After attempting to install franco kernel, my nexus was stuck at the Google logo upon startup. After attempting to recover via clockwork recovery, I found it to be missing (temporary install perhaps?). Currently I have installed clockwork recovery via nexus toolkit. The problem I am now trying to address is that I have no way of putting .zip files on my phone. Some Google searches did not come up with anything quite like this. I am new to this, so any information is good information. Thanks in advance
Click to expand...
Click to collapse
do you know how to use fastboot and adb?

Excuse my lack of knowledge, but how exactly do I flash something over fastboot? Thanks in advance again.
Edit: And I do know how to use adb, however it does not connect. I do not know how to use fastboot

After some playing around with fastboot, I now have a basic understanding. However, I am not sure where I should be flashing that file you have linked.

Today, a friend suggested I try mounting via, and copying roms over that way. However, even with all the drivers installed on my computer, I get nothing.
If anyone has ANY insight on this problem, it would be be greatly appreciated. My new toy is a brick at the moment
Thanks in advance!

luminuss3 said:
Today, a friend suggested I try mounting via, and copying roms over that way. However, even with all the drivers installed on my computer, I get nothing.
If anyone has ANY insight on this problem, it would be be greatly appreciated. My new toy is a brick at the moment
Thanks in advance!
Click to expand...
Click to collapse
I'd seriously try to go back to stock first. I'm not a Windows user but if you have adb, fastboot, and your drivers setup, it should be easy. Mark is a great help in this thread and you can use his script I guess:
http://forum.xda-developers.com/showthread.php?t=1400871
You need to also realize that if you have wiped everything to install a new rom, you have nothing to boot to. Also there is install-recovery.sh file that keeps re-writing your recovery to stock erasing custom recovery (CWR) until you rename or erase that file. So going back to stock would be the safest and then you can try again.
You can use adb in recovery and fastboot in bootloader. If you have everything setup correctly (sdk, adb, fastboot, drivers for windows) either of these commands should recognize your phone:
In Bootloader (the first screen you see with big arrow on top):
Code:
fastboot devices
In recovery:
Code:
adb devices
If you don't have a recovery, then use the first one. If you see your phone's serial number like this
Code:
List of devices attached
HT12HS005115 device
you can now use it to flash things onto your phone. As I said I am not a windows user so I can't be specific, sorry. But adb and fastboot, once you are at their prompt, should work the same.
In general, when fastboot is recognizing your phone in the bootloader, you can use:
Code:
fastboot flash zip YOURFILENAME.zip
changing yourfilename of course. This zip file could be a stock imaqe or a custom recovery. Again, you need someone with windows to give you exact steps, this is just general stuff.

if your phone is yakju build then you can get the stock images from google.
download and unzip the files to your fastboot folder and use these commands, the file names in these commands are for the Android 4.0.1 (ITL41F) build so you will have to change the filenames if you use a different build.
Code:
fastboot devices (to make sure your phone is connect to fastboot)
fastboot flash bootloader bootloader-maguro-primekj10.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk1.img
fastboot reboot-bootloader
fastboot -w update image-yakju-itl41f.zip

[Q] Noob trying to update to OTA 4.0.4 with GN Stock CDMA

First things first. Im a NOOB, got it. I really want to update to 4.0.4 but haven't been able to acomplish via the posts in the developer forums. I so far have downloaded and installed the GN toolkit, and been able to unlock the bootloader. I have tried to boot to CWM Recovery w/o perm flashing it, to install the update, but I can't get it to work, it just hangs. I don't want to root but I tried that as well via the GN toolkit, it fails out as well. I just want to install the Stock 4.0.4. and relock my bootloader, being back to totally stock, w/the most upto date firmware. PLEASE HELP

1. Go to settings -> about phone -> update (I think, my rom has this feature removed) to get the official OTA from Verizon.
2. If you want to use CWM, you will have to permanently flash it over.
3. If an OTA image is available, you could use fastboot to write it to the system, just make sure you backup everything to a second location as it will often wipe your SD.

flashing CWM is very easy.
download the image for the TORO (galaxy nexus CDMA) version of the nexus from http://www.clockworkmod.com/rommanager
once its downloaded, make sure you are able to use fastboot (should be in the folder for the tool kit)
open a command promt, navigate to the toolkit folder which should have fastboot.exe then type:
fastboot flash recovery cwm-recovery-image-name
let it finish then boot into recovery. this will allow you to flash the 4.0.4 rom.
there is no reason to relock the bootloader and as soon as you boot up, stock recovery will place it self back on the phone since you're not going to root.

Tubes6al4v said:
1. Go to settings -> about phone -> update (I think, my rom has this feature removed) to get the official OTA from Verizon.
2. If you want to use CWM, you will have to permanently flash it over.
3. If an OTA image is available, you could use fastboot to write it to the system, just make sure you backup everything to a second location as it will often wipe your SD.
Click to expand...
Click to collapse
Sadly it isn't truely available OTA. These fourms seem to be the only way it is availble. GN toolkit says it can "boot to CWM Revoery withou Permanently flashing it" but like I said it hangs up on me everytime no matter if I try the standard or the touch version.

Zepius said:
flashing CWM is very easy.
download the image for the TORO (galaxy nexus CDMA) version of the nexus from .....(EDIT)
once its downloaded, make sure you are able to use fastboot (should be in the folder for the tool kit)
open a command promt, navigate to the toolkit folder which should have fastboot.exe then type:
fastboot flash recovery cwm-recovery-image-name
let it finish then boot into recovery. this will allow you to flash the 4.0.4 rom.
there is no reason to relock the bootloader and as soon as you boot up, stock recovery will place it self back on the phone since you're not going to root.
Click to expand...
Click to collapse
the GN toolkit has the disc image file "recovery-cwm-5.5.0.4-toro-lte"
what do you mean when you say make sure I can use fast boot. in the folder I found a application that is named "fastboot-toolkit", but when I click it it opens then closes before I can do anything with it.
also typing in the run box, I'm also not having anyluck, can you be more specific as to what you mean, I tried typing in "fastboot flash recovery cwm-recovery-image-name", and "fastboot flash recovery-cwm-5.5.0.4-toro-lte" because I thought that is the name of the file Im tring to flash, correct?
Is there no way to apply this via the stock recovery?

langman21 said:
the GN toolkit has the disc image file "recovery-cwm-5.5.0.4-toro-lte"
what do you mean when you say make sure I can use fast boot. in the folder I found a application that is named "fastboot-toolkit", but when I click it it opens then closes before I can do anything with it.
also typing in the run box, I'm also not having anyluck, can you be more specific as to what you mean, I tried typing in "fastboot flash recovery cwm-recovery-image-name", and "fastboot flash recovery-cwm-5.5.0.4-toro-lte" because I thought that is the name of the file Im tring to flash, correct?
Is there no way to apply this via the stock recovery?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=20632492&postcount=3'
read this post. it should help you get fastboot setup correctly.
and no, there is no way to apply 4.0.4 via stock recovery that i know of.

Status Update....Phone is unlocked, and connected to Computer via USB Debugging is activatied. It is in Fastboot mode, and I have rebooted and went through the initial setup.
I just installed Java Development Kit because it was "required" for the Android SDK tools install which i am setting up now. This is taking a while....
I have copied the fastboot-windows file into the Android platform-tools folder...

in command prompt I get 'fastboot-windows.exe' is not a recognized as an internal or external command, operable program or batch file

looks like I dont need the .exe, it brought up the a bunch of command options...now what?

okay looks like I got fastboot working, and went back into GN Toolkit and flashed CMW recovery. I was able to boot CWM recovery....now where do I save the update so I can find it? I now have the option to choose zip from SDcard.

langman21 said:
okay looks like I got fastboot working, and went back into GN Toolkit and flashed CMW recovery. I was able to boot CWM recovery....now where do I save the update so I can find it? I now have the option to choose zip from SDcard.
Click to expand...
Click to collapse
you'll want to move the .zip file of the 4.0.4 update to anywhere on the SDcard. basically anywhere you'd download something to from your browser on the phone.
once its there, you'll want to make a backup just in case.
once the backup is complete, you should be able to then install from that zip file and be ok.

[Q] Semi-bricked Nexus and not sure what to do

So I made a mistake and I tried to flash the newest aokp build 3 without a backup. I got my new phone a while back and never made a backup.
I flashed build 3 and (accidentally) some old gapps and I kept getting stuck on the Google screen.
Next I tried pushing files through the Gnex tool kit and manually through fastboot. I keep getting errors that there is no insecure boot or that the device is not connected. attempts at a temporary insecure boot on the tool kit fail.
Next I tried a wipe and then just installing build 3 without google apps so I could add the correct one after boot, but it is again stuck.
So now I'm really not sure what to do. Any suggestions?

Rule number 1 : STOP using toolkits!!
now, can you get into cwm recovery?

Yes, I can gt into twrp everything I did except for trying to push the last files was through twrp
by the way, I have a Verizon Nexus
And as a side comment: The tool kit was used as a last ditch effort. The toolkit had nothing to do with bricking the device. The toolkit has been extremely useful for unlocking and rooting multiple devices quickly.

You could eithther try to flash back to stock or you could boot into TWRP & adb push a different ROM. (You did try Wipe Data / Factory Reset right?)

MK17 said:
Yes, I can gt into twrp everything I did except for trying to push the last files was through twrp
by the way, I have a Verizon Nexus
And as a side comment: The tool kit was used as a last ditch effort. The toolkit had nothing to do with bricking the device. The toolkit has been extremely useful for unlocking and rooting multiple devices quickly.
Click to expand...
Click to collapse
I think what thegtfusion was trying to say was: if you wouldn't have used a toolkit in the past, you would have known how to fix your bootloop.
Buy anyway:
1) Boot into recovery and plug into your PC
2) Open a command prompt (in the folder where you have adb.exe and fastboot.exe)
3) Push the ROM (and kernel if it doesn't come with it) you want to flash to your device: adb push /path/to/ROM.zip /sdcard/
4) Reboot into fastboot mode
5) Erase your old ROM: fastboot erase system
6) Erase your old kernel: fastboot erase boot
7) Reboot into recovery
8) Wipe /data and /cache
9) Flash your ROM & kernel in recovery
10) Reboot. Done.
EDIT: Ninja'd by 3rdstring!

Screwing up is part of the learning process. It's actually a great way to learn how your phone really works.

Thanks for the reply. For some reason I can't get my device to be recognized on my new computer. I downloaded drivers, adb and fastboot and rebooted everything but it didn't work. I'll have to retry again on my other computer tomorrow.

MK17 said:
Thanks for the reply. For some reason I can't get my device to be recognized on my new computer. I downloaded drivers, adb and fastboot and rebooted everything but it didn't work. I'll have to retry again on my other computer tomorrow.
Click to expand...
Click to collapse
Try uninstalling all drivers and reinstalling them.
Sent from my Galaxy Nexus using xda premium

Drivers

Thanks for the drivers. I uninstalled all of the drivers and used the universal one. Everything seems to work until I run 'adb devices' and my Galaxy Nexus is not listed.
I feel that my device is not getting seen because of something I have wrong, but after adb, fastboot, and the correct drivers I'm not sure.
PS - Even with the universal driver I still have to run adb and fastboot from the original directory that I installed them correct? I don't run them from the driver in anyway correct?

MK17 said:
Thanks for the drivers. I uninstalled all of the drivers and used the universal one. Everything seems to work until I run 'adb devices' and my Galaxy Nexus is not listed.
I feel that my device is not getting seen because of something I have wrong, but after adb, fastboot, and the correct drivers I'm not sure.
PS - Even with the universal driver I still have to run adb and fastboot from the original directory that I installed them correct? I don't run them from the driver in anyway correct?
Click to expand...
Click to collapse
did you install android-sdk (and added adb/fastboot to your $PATH) or are you using binary versions of adb and fastboot downloaded elsewhere?
if it's the latter, commands should be run from the directory where you extracted them.
about the drivers, i think you need to go to device manager and update drivers manually to the ones you installed (refered here in the post before mine), assuming you're on windows.
sent from my i9250

You're booted into TWRP when trying adb?

Fixed! I ended up booting into recovery and the device was recognized in adb there. I was able to push fresh copies of aokp build 3 and gapps (my original build 3 download started failing) and now I just got done initiating swagger!

MK17 said:
Fixed! I ended up booting into recovery and the device was recognized in adb there. I was able to push fresh copies of aokp build 3 and gapps (my original build 3 download started failing) and now I just got done initiating swagger!
Click to expand...
Click to collapse
he didnt have usb debugging on.
sent from my i9250

Just for understanding, USB debugging is only activated through recovery?

It's also under settings >> developer options so you can use adb while the android is running.

3rdstring said:
It's also under settings >> developer options so you can use adb while the android is running.
Click to expand...
Click to collapse
Of course,but that is hard to get to when your phone doesn't boot

MK17 said:
Of course,but that is hard to get to when your phone doesn't boot
Click to expand...
Click to collapse
USB Debugging needs to be enabled in Android for ADB to work in Android.
CWM and TWRP have USB Debugging enabled by default, so ADB will work fine in recovery with no other action from the user.

[Q] Do I have this right?

Getting GN tomorrow, I've read all the [REF] posts and I've been working with Samsung devices since Samsung has been making devices.
I know little about Nexus devices, and I am surprised at how easy this process seems to be.
Naturally I'm suspicious, so I come to you to make sure I have this all straight:
1 adb fastboot oem unlock
2 rom manager > install clockworkmod
3 flash rom/gapps in recovery
Ya? No ODIN? No messing with partitions? Is it really as easy as these 3 steps?
kthanks

Step 1.5 is to root while using fastboot. Use efrant's guide in the "stickies" for the commands and sequence. It's very easy.
If you follow your steps as you wrote them (without the rooting commands in fastboot) then ROM Manager will install but you won't be able to flash the CWM recovery because there is no root.
Good luck!

Doc_rockulus said:
Getting GN tomorrow, I've read all the [REF] posts and I've been working with Samsung devices since Samsung has been making devices.
I know little about Nexus devices, and I am surprised at how easy this process seems to be.
Naturally I'm suspicious, so I come to you to make sure I have this all straight:
1 adb fastboot oem unlock
2 rom manager > install clockworkmod
3 flash rom/gapps in recovery
Ya? No ODIN? No messing with partitions? Is it really as easy as these 3 steps?
kthanks
Click to expand...
Click to collapse
Learn to do it all yourself, makes life a LOT easier!
1. fastboot oem unlock. Phone will reboot once you've done this so once booted go back to the bootloader
2. fastboot flash recovery recovery.img (download the latest CWM here and rename it recovery.img)
3. fastboot reboot
4. Once back in Android copy the ROM to your phone (and GAPPs if you need them). I'd also use a wipe script to format the phone before flashing the new ROM. You can get mike1986's one here
5. Turn on USB Debugging
6. adb reboot-bootloader
7. Go into recovery
8. Flash Super Wipe script (if you're going to use one)
9. Flash ROM
10. Flash GAPPs (if required)
11. Reboot phone
12. Enjoy!

EddyOS said:
Learn to do it all yourself, makes life a LOT easier!
1. fastboot oem unlock. Phone will reboot once you've done this so once booted go back to the bootloader
2. fastboot flash recovery recovery.img (download the latest CWM here and rename it recovery.img)
3. fastboot reboot
4. Once back in Android copy the ROM to your phone (and GAPPs if you need them). I'd also use a wipe script to format the phone before flashing the new ROM. You can get mike1986's one here
5. Turn on USB Debugging
6. adb reboot-bootloader
7. Go into recovery
8. Flash Super Wipe script (if you're going to use one)
9. Flash ROM
10. Flash GAPPs (if required)
11. Reboot phone
12. Enjoy!
Click to expand...
Click to collapse
To clarify, the fastboot oem unlock command only unlocks the bootloader, correct?
At what part of the process is root obtained? I've never seen/tried a CWM flash prior to root/SU.
Am I obtaining root simply by flashing the root enabled rom?
I wouldn't call that "Doing it myself"

That's right. Once the bootloader is unlocked you can then flash new files to the different partitions on the device (system, data, recovery, boot, etc...). Root is obtained when you flash the SuperSU package in CWM or when you flash a custom ROM (as they tend to be pre-rooted)
When I say 'do it yourself' I mean all the steps of unlocking the bootloader, flashing CWM manually, etc. as opposed to using apps that do it all for you

Doc_rockulus said:
Getting GN tomorrow, I've read all the [REF] posts and I've been working with Samsung devices since Samsung has been making devices.
I know little about Nexus devices, and I am surprised at how easy this process seems to be.
Naturally I'm suspicious, so I come to you to make sure I have this all straight:
1 adb fastboot oem unlock
2 rom manager > install clockworkmod
3 flash rom/gapps in recovery
Ya? No ODIN? No messing with partitions? Is it really as easy as these 3 steps?
kthanks
Click to expand...
Click to collapse
yup, that's pretty much it.
1. fastboot OEM unlock
2. fastboot flash a custom recovery(differs from ROM manager)
3. flash the su binaries or a custom ROM in your new recovery
4. reboot and profit

Put the rom you want on your sd card before you do any of this actually. Then get yourself into fastboot mode. Then do the
fastboot oem unlock.
Fastboot flash recovery "name of recovery.img"
fastboot boot recovery
Install ROM
Actually come to think of it, maybe the oem unlock erases sd card, putting ROM on before unlocking might not be good. Most roms have root permission anyhow so you don't gotta worry about getting root if your flashing a custom rom.

M3drvr said:
Put the rom you want on your sd card before you do any of this actually. Then get yourself into fastboot mode. Then do the
fastboot oem unlock.
Fastboot flash recovery "name of recovery.img"
fastboot boot recovery
Install ROM
Click to expand...
Click to collapse
if you put the rom you want in your storage before you fastboot oem unlock, then it wont be there when you need to flash it, considering the contents of your storage gets erased when you fastboot oem unlock.

simms22 said:
if you put the rom you want in your storage before you fastboot oem unlock, then it wont be there when you need to flash it, considering the contents of your storage gets erased when you fastboot oem unlock.
Click to expand...
Click to collapse
Ya i thought of that after i posted. That was my bad. Although you could boot into recovery, mount the sd card so computer sees it, copy the rom into phone then flash it. Rather than rebooting to system and using rom manager.

M3drvr said:
Ya i thought of that after i posted. That was my bad. Although you could boot into recovery, mount the sd card so computer sees it, copy the rom into phone then flash it. Rather than rebooting to system and using rom manager.
Click to expand...
Click to collapse
No you can't mount the sdcard as the nexus does not have mass storage
Sent from my Galaxy Nexus using Tapatalk 2

Zepius said:
No you can't mount the sdcard as the nexus does not have mass storage
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Then i have a messed up phone, cause when i'm in recovery i can drop files into my phone from my computer.

M3drvr said:
Then i have a messed up phone, cause when i'm in recovery i can drop files into my phone from my computer.
Click to expand...
Click to collapse
+1
Thanks guys, I've got it. Rooted, CM10.1 in record time.
First device I've had that hasn't put up a fuss during this process.

Now that I'm in CM10.1 can I use AOSP kernel or do I need one based off of CM?