title: fastboot problems leads to bootable but non-starting glass
body: <p>I was hoping to have some Glass hacking fun tonight.  Turned out really bad.  :( </p>
  
  <p>Let me try to explain the steps I have taken. </p>
  
  <ol>
  <li>I installed Launcher.apk and Setting.apk</li>
  <li>Paired a keyboard and mouse</li>
  <li>All was good. </li>
  </ol>
  
  <p>Then I tried to unlock the device as described at <a href="https://developers.google.com/glass/downloads/system" rel="nofollow noreferrer">https://developers.google.com/glass/downloads/system</a></p>
  
  <ol>
  <li>adb reboot bootloader</li>
  <li>fastboot oem unlock</li>
  </ol>
  
  <p>The system sat there for over an hour so I hit Ctrl+c assuming that something had gone wrong.  I checked if the system was in adb or fastboot mode and it looked like it was still in fastboot, so I tried again.  30 minutes later nothing had happened so I Ctrl+c'd it again.  </p>
  
  <p>Here is a copy of the output of the terminal for those steps:</p>
  
  <pre><code>local:Downloads mmicire$ adb install -r Launcher2.apk 
  4361 KB/s (9723188 bytes in 2.176s)
      pkg: /data/local/tmp/Launcher2.apk
  Success
  local:Downloads mmicire$ adb install -r Settings.apk 
  3937 KB/s (3269290 bytes in 0.810s)
      pkg: /data/local/tmp/Settings.apk
  Success
  local:Downloads mmicire$ adb devices
  List of devices attached 
  015D98410D020013    device
  
  local:Downloads mmicire$ adb reboot bootloader
  local:Downloads mmicire$ fastboot oem unlock
  ...
  (bootloader) Warning: Unlocking your device will void your warranty
  (bootloader) and erase your personal data from the device.
  (bootloader) Run "fastboot oem unlock" again to confirm.
  (bootloader) Device still locked.
  OKAY [  0.001s]
  finished. total time: 0.001s
  local:Downloads mmicire$ fastboot oem unlock
  ...
  ^C
  local:Downloads mmicire$ adb reboot bootloader
  error: device not found
  local:Downloads mmicire$ fastboot devices
  015D98410D020013    fastboot
  local:Downloads mmicire$ fastboot oem unlock
  ...
  ^C
  local:Downloads mmicire$ fastboot reboot
  rebooting...
  </code></pre>
  
  <p>After the device rebooted it went back into the Glass home screen and everything looked fine.  So I tried adb reboot bootloader again and the system seemed unable to boot into fastboot mode.  When I type "adb reboot bootloader" the system shutdown, rebooted, showed the GLASS logo and started right back up into Android.</p>
  
  <p>I then tried Jenny Murphy's solution for fastboot here -- <a href="https://stackoverflow.com/questions/17519865/having-issues-seeing-glass-in-fastboot">Having issues seeing GLASS in Fastboot</a> -- and it did not change the situation.  The system boots, the LED comes on solid for about 5 seconds, then the system reboots and I see the GLASS logo as the system is coming up. </p>
  
  <p>So I thought that possibly doing a factory reset might fix things.  (It was a stretch at this point.)   I went into the Glass setting and performed a factory reset.</p>
  
  <p>The system rebooted, presented the GLASS logo, and then presents the welcome screen asking me to go to google.com/myglass.  I went to the URL on my laptop and configured a WIFI connection.  The Glass does not seem to be reading QR codes at this point.  I have a very clear picture of the QR code and it just does not seem to be responding at all. </p>
  
  <p>The problem I have now is that I have no way of getting past the second screen for WIFI, I can't turn on debugging since I can't get to the settings menu, and I also can't hardware-enable fastboot to reset the image to factory.  :(</p>
  
  <p>So, after a discouraging evening of hacking, I am needing some help.  At this point, the Glass can only boot, ask me to go to the web, and then pretend to read QR codes to no avail.  Feeling like a d-bag for pseudo-bricking a 48-hour old Glass.  </p>
  
  <p>Thoughts anyone?  </p>
  
  <p>This was on a OSX 10.8.5 machine running adt-bundle-mac-x86_64-20130917.  I do have linux machines available if that helps. </p>
  
  <p>Thank you ahead of time.  </p>
  
  <hr>
  
  <p>EDIT:  I have been able to log back into the device and enable debugging.  "adb reboot bootloader" still gives the previous behavior of shutting down, LED is solid for about 5 seconds, reboot, GLASS screen.   I do see a usb device in linux appear and then disappear during what I assume is the fastboot debug device coming up and down during this cycle. </p>
  
  <hr>
  
  <p>EDIT:  Tried it on my linux box as recommended by Jenny, but no dice.  The Glass is not willing to stay in fastboot mode.  On reboot, while watching dmesg, I can see the Android debug device dissapear, the glass reboots, I see the fastboot device come up and then three seconds later it dissapears.  Then the Glass reboots into normal Android.  </p>
  
  <p>:(</p>
  
  <hr>
  
  <p>SOLUTION:  (And this makes <em>NO</em> sense to me.)  I basically ran the battery completely dead.  I have had other Android phones where I needed to pull the batteries and let them sit for a while, so I tried the closest thing that I could accomplish without disassembling the battery from the unit.  It sat on my desk completely drained for a couple days.  I would turn the Glass on even after dying to drain the battery as far as possible.  Frankly, this was as much out of frustration as anything else.</p>
  
  <p>72 hours later, I charged it for about 30 minutes and plugged it into my Linux machine and did the following:</p>
  
  <pre><code>mmicire@blue:~$ sudo fastboot devices
  015D98410D020013    fastboot
  mmicire@blue:~$ sudo fastboot oem unlock
  ...
  (bootloader) Warning: Unlocking your device will void your warranty
  (bootloader) and erase your personal data from the device.
  (bootloader) Run "fastboot oem unlock" again to confirm.
  (bootloader) Device still locked.
  OKAY [  0.001s]
  finished. total time: 0.001s
  mmicire@blue:~$ sudo fastboot oem unlock
  ...
  (bootloader) Erasing personal data. This could take a while...
  (bootloader) Erasing cache...
  (bootloader) Erasing userdata...
  (bootloader) Unlocking...
  (bootloader) Device unlocked!
  OKAY [256.353s]
  finished. total time: 256.353s
  </code></pre>
  
  <p>Nothing done differently from the last test for Jenny.  Not sure what I did, but it just decided to work.  I suppose there was something resident with the charged battery?  </p>
  
  <p>Thank you to everyone that helped.  I hope that this helps someone else.  Off to hacking....  </p>