1. estebancam's Avatar
    I am following the seemingly easy directions to root the device, and everything seems to go well... however, when I put in the final command on the command prompt "fastboot-windows oem unlock" i just get a message that says "waiting for device."


    I can't figure out the issue and I can't find a solid answer that I understand online. Can anyone help???


    Thanks!
    08-18-2012 12:34 AM
  2. 2defmouze's Avatar
    It's a driver issue.. Check the troubleshooting section of the unlock thread, you just need to update the drivers correctly.

    Sent from my Galaxy Nexus using Tapatalk 2
    oxymoron likes this.
    08-18-2012 12:49 AM
  3. estebancam's Avatar
    Awesome got it.... I am now just waiting for the device to reboot!

    Final question: my main goal was to install Jelly Bean, and there are like 10,000 versions out there. Which one would be the most stock-like? Or which one is recommended as the most stable?
    08-18-2012 02:18 AM
  4. bbudnick5001's Avatar
    Awesome got it.... I am now just waiting for the device to reboot!

    Final question: my main goal was to install Jelly Bean, and there are like 10,000 versions out there. Which one would be the most stock-like? Or which one is recommended as the most stable?
    Currently everybody seems to be running AOKP nightlies or Euroskank Jellybro CM10 nightlies. Both seem to be pretty darn stable. Just make some nandroids, flash some ROMs and have fun. But, be aware crackflashing is very addictive !!!

    Sent from my Galaxy Nexus using Android Central Forums
    oxymoron, CA1NE and 2defmouze like this.
    08-18-2012 04:43 AM
  5. dmmarck's Avatar
    If you want stock, run Bugless Beast .
    08-18-2012 09:23 AM
  6. digitalslacker's Avatar
    If you want stock, run Bugless Beast .
    Or if you want stable and fast without "bloaty" options, run bugless :-)

    Sent from my Galaxy Nexus using Tapatalk 2
    08-18-2012 05:07 PM
LINK TO POST COPIED TO CLIPBOARD