[samsuck]

birdman, on 15 December 2011 - 04:21 PM, said:

Let us begin

• open terminal (command prompt for windows) and change to directory of the fastboot binary (or add to path...but if you can do that then why are you reading this)
  
• Hold your volume up and down and power button, wait for a vibrate and let go of buttons. (if in windows, wait for drivers to install)
  
• run:

  fastboot oem unlock

• choose yes on the unlock option on your phone screen.
  
• press volume down till you get the "recovery mode" option, press power.
  
• wait till you get to a blank screen with an open android in the middle. Press volume up + volume down and power all at once - you *SHOULD* get a menu.
  
• *NOTE* Volume up and down to select in recovery - power to choose the selected option.
  
• select factory reset, this will take about 5 minutes. IT WILL TAKE A LONG TIME
  
• select reboot.
  
• Make sure phone has booted.

*YOUR PHONE IS NOW UNLOCKED*

I have a rooted Nexus, and I used a different method within hours of the release of our device but my brother is getting a Nexus tomorrow and I'd like to use this method. However, I am a bit confused on these steps.

I thought after you selected unlock after the warning screen comes off, that your phone automatically reboots and wipes all data? Sorry, I just don't remember if after unlocking, you go back to bootloader mode.

[yurdle]

samsuck, on 12 February 2012 - 10:14 PM, said:

I have a rooted Nexus, and I used a different method within hours of the release of our device but my brother is getting a Nexus tomorrow and I'd like to use this method. However, I am a bit confused on these steps.

I thought after you selected unlock after the warning screen comes off, that your phone automatically reboots and wipes all data? Sorry, I just don't remember if after unlocking, you go back to bootloader mode.

I just used this method and yes it does go back to bootloader mode

[loveubuntu]

edit: nevermind, I got it: I was stuck right after the unlock and could not get menu after going into the stock recovery. It appears that you have to push the power button just a fraction of a second before the Vol up/down. Or at least in my case that is what worked.


I'm stuck here, new to this so please take it easy on me. Here is what I did: (using ubuntu with adb and fastboot setup, adb devices recognized the device)

1- downloaded fastboot and cd to it in terminal
2- volume up and down and power to get toinital menu with locked state
3- fastboot oem unlock, chose yes and got the unlocked state

now I can't get to the menu in stock recovery to wipe data and factory reset. I pressed the volume down to get the recovery mode option and then power button, it flashed an android standing up (after the google and the lock screen) but quickly goes into the laying down android with a red triangle in it's tummy. Did I miss something?

phone won't boot up (bootloop).

Edited by loveubuntu, 19 February 2012 - 07:19 PM.

[nailbomb3]

r2doesinc, on 15 December 2011 - 04:32 PM, said:

you should mention setting up your udev rules in linux. i got caught up there for a while.

EDIT - The guide you linked ot in the post in incomplete. You need fastboot rules setup as well. I had my ADB rules setup, but not fastboot. Caused fastboot to hang at < Waiting for device >. My info was taken from here. http://source.androi...itializing.html

sudo nano /etc/udev/rules.d/51-android.rules

and add these lines with your username substituted in

# adb protocol on maguro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="<username>"
# fastboot protocol on maguro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0600", OWNER="<username>"

Just for clarity, since I'm going to be doing this Monday: is this step absolutely necessary or is the 99 .rules file enough?

[Samiam303]

Mustang302LX, on 15 December 2011 - 05:35 PM, said:

I have root. I instead downloaded Root Explorer and renamed the file that way and then reflashed CWM. All is good now. This was my first time doing all this with a Mac since my PC is broken. Lessons learned!

That error means that even though you have root, it wasn't using the superuser privileges in your adb shell. If you ran the command "su" then the mount command, it would have worked.

[pjd17011]

I can't seem to get the drivers working properly on my PC. I've followed the steps listed above and I've installed all the alternate drivers but they don't work. I keep getting "waiting for device" and it doesn't do anything. I'm running Windows 7 64bit. Anyone have any ideas?

Thanks!

[razorloves]

pjd17011, on 03 March 2012 - 08:40 PM, said:

I can't seem to get the drivers working properly on my PC. I've followed the steps listed above and I've installed all the alternate drivers but they don't work. I keep getting "waiting for device" and it doesn't do anything. I'm running Windows 7 64bit. Anyone have any ideas?

Thanks!

try this http://rootzwiki.com...post__p__327640

[GrdLock]

You might want to mention in this guide that doing the default factory/data reset wipes out EVERYTHING, including your internal storage "sdcard". I had a ton of shit saved on my internal storage, and lost it all because I've never seen another Android phone that wipes your personal storage like that.

Would be a good idea to mention this in the guide.

[Notorious478]

Aftet going into recovery mode i got a small droid with red exclamation point over his chest. I assume thats normal? But no combo of power and volume buttons could get any menu to do a factory reset. So i started googling and then suddenly the phone restarted. Went to the boot animation. Then appeared to boot loop and went back to the google screen, and then booted up fine. I cant tell if it reset or not bc i had done so little to the phone before starting the process. The rest of the recovery/root worked so am i ok? Should i do a factory reset from cwm? Is the reset from cwm the same as the one from the regular recovery? If i dont do anything will i have issues done the road?

[Jubakuba]

Notorious478, on 28 March 2012 - 03:18 AM, said:

Aftet going into recovery mode i got a small droid with red exclamation point over his chest. I assume thats normal? But no combo of power and volume buttons could get any menu to do a factory reset. So i started googling and then suddenly the phone restarted. Went to the boot animation. Then appeared to boot loop and went back to the google screen, and then booted up fine. I cant tell if it reset or not bc i had done so little to the phone before starting the process. The rest of the recovery/root worked so am i ok? Should i do a factory reset from cwm? Is the reset from cwm the same as the one from the regular recovery? If i dont do anything will i have issues done the road?

Should be fine.
If you really wanted to...a CWM wipe would work.
But the Unlock command acceptance actually calls a wipe on it's own. If you simply select reboot it would wipe without intervention...which is what I assume happened in your case.