search

zmsoft / google-glass-api

Automatically exported from code.google.com/p/google-glass-api
0 stars 0 forks source link

fastboot oem unlock hangs #243

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. adb reboot bootloader
2. fastboot oem unlock
3. follow the introduction by typing fastboot oem unlock again

What is the expected output? What do you see instead?
Expected to see it being unlocked. Instead it hangs with "...", and stop 
responsing to any commands. I could only exit the fastboot by pressing the 
camera buttom.

What version of the product are you using? On what operating system?
1st generation hardware with XE11. I've tried on two devices, one of it hadn't 
rooted before, and got the same result

Please provide any additional information below.

$ adb reboot bootloader
$ fastboot oem unlock
< waiting for device >
...
(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
$ fastboot oem unlock
...

Original issue reported on code.google.com by chenxingyu92@gmail.com on 15 Nov 2013 at 1:09

GoogleCodeExporter commented 9 years ago 
PS: even Control-C them fastboot reboot could not get any response.

Mac OS X 10.9, newest Android Studio.

Original comment by chenxingyu92@gmail.com on 15 Nov 2013 at 1:12

GoogleCodeExporter commented 9 years ago 
I have the same problem on Mac. Hope someone will help with this.

Original comment by loh.zh...@gmail.com on 6 Dec 2013 at 9:19

GoogleCodeExporter commented 9 years ago 
According to Hyunyoung Song (https://plus.google.com/104909144433751521217) on 
Google I/O 2013, they tested this and it only works with Linux. She does point 
at someone that knows how to make this work on Mac, which us remote watchers 
never really got who she was talking about.

See https://developers.google.com/events/io/sessions/332704837
@ 17:43

Maybe there's a way, would someone internally care to check and post?

Original comment by o...@cloud.com on 7 Dec 2013 at 3:33

GoogleCodeExporter commented 9 years ago 
Sorry I posted the last question with a different Google Account :(

Original comment by roberto.andrade on 7 Dec 2013 at 3:38

GoogleCodeExporter commented 9 years ago 
I used to success unlocked it in XE8, and locked it back to OTA upgrade XE9. 
But the unlocking fails since XE11. I've tried on my friend's another Glass 
that never unlocked, it fails too.

Original comment by chenxingyu92@gmail.com on 7 Dec 2013 at 3:42

GoogleCodeExporter commented 9 years ago 
Has always locked up on my retina macbook pro as well. Had to use Saurik's root 
method instead, which still worked a few months ago at least last time I tried 
it:
http://www.saurik.com/id/16

Original comment by lna...@gmail.com on 11 Dec 2013 at 7:16

GoogleCodeExporter commented 9 years ago 
The unlock is hanging for me as well.  The unlock hangs at "Unlocking..."  

Host machine is on Ubuntu 12.04, Glass is on XE16.11.  Console output below.

nick@funkotron:/data/glass/glass_images/XE16.11$ 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.028s
nick@funkotron:/data/glass/glass_images/XE16.11$ sudo fastboot oem unlock
...
(bootloader) Erasing personal data. This could take a while...
(bootloader) Erasing cache...
(bootloader) Erasing userdata...
(bootloader) Unlocking...

Original comment by nick.mu...@gmail.com on 1 May 2014 at 7:02

GoogleCodeExporter commented 9 years ago 
It's ridiculous that no one @ google cares about this. I have a Mac and 
essentially this means I can't update my $1500 google glass because OTA isn't 
working on it.

Original comment by yalbaz...@gmail.com on 7 Jun 2014 at 6:09

GoogleCodeExporter commented 9 years ago 
Yeah, pretty ridiculous.  I'm 9 months into this, have an active app in MyGlass 
and have to bust out a laptop I installed Ubuntu on for the soul purpose of 
dealing with updates every time an update comes out.

Original comment by tim.fl...@gmail.com on 8 Jun 2014 at 2:28

GoogleCodeExporter commented 9 years ago 
This issue seems only appears on Mac. I've successfully unlocked my Glass on a 
Windows XP vitural machine (Parallel Desktops for Mac).

Original comment by chenxingyu92@gmail.com on 8 Jun 2014 at 2:43

GoogleCodeExporter commented 9 years ago 
So what if it only appears on Mac products. You say that like Mac users don't 
represent a significant enough install base to warrant fixing something as 
basic as fastboot compatibility.

News flash: Mac users prob have more money to spend, so you might want to 
listen to their pleas. Especially when you're talking about a $1500 development 
item with a questionable go to market strategy.

It works on Android phones. Why wouldn't glass? And why leave this issue open 
for the better part of A YEAR.

By the way. I tried this on a Win7 PC and I can't even get glass to stay in 
fastboot state. The compute never recognizes it when calling fastboot devices 
after doing an adb reboot bootloader, which is a whole other issue. Adb drivers 
for windows suck, too. 

Comment #10 on issue 243 by chenxingyu92@gmail.com: fastboot oem unlock hangs
http://code.google.com/p/google-glass-api/issues/detail?id=243

This issue seems only appears on Mac. I've successfully unlocked my Glass on a 
Windows XP vitural machine (Parallel Desktops for Mac).

Original comment by yalbaz...@gmail.com on 8 Jun 2014 at 4:06

GoogleCodeExporter commented 9 years ago 
Hey folks, let's be cool here.  

First of all, I think we are in the wrong component.  I should've noticed that 
earlier.  Fastboot has nothing to do with the Mirror API.  We really need this 
filed under the Android Platform Tools bug tracker.  I can create a new issue 
there and link it here, and then link this thread back to the Android Platform 
Tools issue.

Second, I think this goes beyond OSX; I reproduced the issue in Ubuntu 12.04.  
Can someone who can reproduce this issue on OSX please sample the fastboot 
process when it hangs and copy/paste the call stack and note what build of OSX 
they are on (copy/paste the output of "sw_vers")?  We should be able to then 
get an idea of where fastboot is hanging.  Only do this is you're pretty 
confident you won't brick your Glass.

I can maybe try and reproduce this in Ubuntu 12.04, but I only ended up here 
because it looked like the unlock procedure had nearly bricked my Glass.

-Nick

Original comment by nick.mu...@gmail.com on 8 Jun 2014 at 4:37

GoogleCodeExporter commented 9 years ago 
Agree with Nick, it may be actually an issue of ADT.

$ sw_vers
ProductName:    Mac OS X
ProductVersion: 10.9.3
BuildVersion:   13D65

Original comment by chenxingyu92@gmail.com on 8 Jun 2014 at 4:43

GoogleCodeExporter commented 9 years ago 
I have refiled this issue in a more appropriate place:

https://code.google.com/p/android/issues/detail?id=70980

We should continue to track it there.

Original comment by nick.mu...@gmail.com on 8 Jun 2014 at 4:47

GoogleCodeExporter commented 9 years ago 
No, the other place is not correct. That's the Android Open Source Project's 
bug tracker, but the bug is Glass specific, Glass is not part of that project, 
and Glass is not open source.

(Also, no, the bug is not Mac-specific. I reproduced it on a Windows 7 machine.)

Original comment by jimrandomh@gmail.com on 8 Jun 2014 at 2:55

GoogleCodeExporter commented 9 years ago 
No, the bug has been refiled correctly. This issue and fastboot have NOTHING to 
do with the mirror API. The issue is an AOSP platform tool not acting as 
intended. We are talking about the tool, not the software running on Glass. I 
never said it was a Mac specific bug, in fact I clearly said it wasn't, since I 
reproduced it on Ubuntu 12.04.It doesn't matter that the issue seems Glass 
specific, the developer tools are not device specific. In fact, Google has even 
documened the use of fastboot, and it is not working as documented. That is why 
this has been refiled in the AOSP Tools component.

Original comment by nick.mu...@gmail.com on 8 Jun 2014 at 4:04

GoogleCodeExporter commented 9 years ago 
It'll take some investigation to find out whether this bug is in fastboot on 
the PC side, or the firmware on Glass. Really, this should be in a "general 
issues with Glass" bug tracker, but there isn't one. But it's probably moot, 
because Google's Glass developers don't seem to be reading *either* bug tracker.

Original comment by jimrandomh@gmail.com on 8 Jun 2014 at 5:35

GoogleCodeExporter commented 9 years ago 
Agreed. I'd love to know how they get the list of bugs they are going to work 
on because this seems like it would be pretty high on the list.

Comment #17 on issue 243 by jimrandomh@gmail.com: fastboot oem unlock hangs
http://code.google.com/p/google-glass-api/issues/detail?id=243

It'll take some investigation to find out whether this bug is in fastboot on 
the PC side, or the firmware on Glass. Really, this should be in a "general 
issues with Glass" bug tracker, but there isn't one. But it's probably moot, 
because Google's Glass developers don't seem to be reading *either* bug tracker.

Original comment by yalbaz...@gmail.com on 8 Jun 2014 at 5:59

GoogleCodeExporter commented 9 years ago 
Hey all, can somebody test this on a cellphone to see if this is a bug of 
Android Develop Tools or Glass?

It may be a bug of fastboot executable from ADT, and it may be a bug of Glass 
that didn't response to fastboot commands too. We need to firstly find out 
where the problem is, so we can decide which tracker to post the bug.

Original comment by chenxingyu92@gmail.com on 9 Jun 2014 at 2:59

GoogleCodeExporter commented 9 years ago 
I don't understand why ADT, the Eclipse plugin, is being brought up at all. 
I've tried from a Mac in the terminal and it hangs. I've tried from a Linux VM 
with the USB connected to the VM and it hangs. I don't actually know any 
official method that works and just use Saurik's root method to manage any 
control and customization of a device I paid $1500 for that is stuck on XE 12 
and I can't flash. I wish Google would put more support into the developer 
experience because unlocking just doesn't work for very many people.

Original comment by lna...@gmail.com on 9 Jun 2014 at 3:06

GoogleCodeExporter commented 9 years ago 
We should not be having this discussion here. This is the mirror API component. 
Wherever the issue lies, it's not in the Mirror API. 

We know we can't unlock Glass, but since Glass is a Google supported Android 
developer product, the Android platform tools should all work with it. It 
doesn't matter where the actual problem is, the workaround needs to be at 
minimum triaged  in platform tools because some people have no way of updating 
the software on their Glass. A workaround in fastboot is likely the first step 
to a fix.

Please, we need to have constructive discussion in the other Issue filed under 
platform tools. It has a screener/assignee who can triage this issue and route 
it appropriately. Nobody who can do anything is looking at this issue. If you 
can reproduce the issue on OSX, sample the fastboot process When it hangs and 
paste the call stack into the other issue.

Original comment by nick.mu...@gmail.com on 9 Jun 2014 at 5:36

GoogleCodeExporter commented 9 years ago 
I can reproduce the issue on OSX. How to sample the process?
2014年6月9日 下午1:36于 <google-glass-api@googlecode.com>写道：

Original comment by chenxingyu92@gmail.com on 9 Jun 2014 at 6:09

GoogleCodeExporter commented 9 years ago 
Run the fastboot oem unlock, then get the pid of the fastboot process, in 
another shell , run "sample <pid of fastBoot>" While fastboot is hung. Output 
will go to stdout and a tmp file.

Original comment by nick.mu...@gmail.com on 9 Jun 2014 at 6:13

GoogleCodeExporter commented 9 years ago 
I have exactly the same problem trying to unlock the bootloader on my BLU DASH 
3.5 phone with Android 4.2.2.  After "fastboot oem unlock" command, it freezes 
with:

C:/adb> fastboot oem unlock
...
_

Control-C takes only takes me back to the C:/adb directory with no further 
action.

Original comment by dean.flo...@gmail.com on 27 Jun 2014 at 6:38

GoogleCodeExporter commented 9 years ago 

I avoid this hang using windows8.1 (If I had Windows 7, I could be easier).
My glass trusted my Mac(10.9.5) but don't trusted my windows.
So I copied adbkey and adbkey.pub which are used in connecting to android to my 
windows.

I setted up android sdk on Windows.
I used "SDK Tools Only" in http://developer.android.com/sdk/index.html .

1. Copy adbkey and adbkey.pub in mac to windows.

Mac (I install adk using homebrew)
~/.android/adbkey
~/.android/adbkey.pub

Windows
~/.android/adbkey
~/.android/adbkey.pub

If default adbkey and adbkey.pub are created, You override these.

2. Edit android_winusb.inf.

I tried 'adb devices' but no device. So add lines to android_winusb.inf.
My google glass's hardware id is different from writing in android_winusb.inf .

default glass config-----

;Google Glass
%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_9001
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_9001&MI_01

C:\Users\jp\AppData\Local\Android\android-sdk\extras\google\usb_driver\android_w
inusb.inf

[Google.NTx86]

;My Google Glass %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&REV_0216&MI_01 %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&MI_01

[Google.NTamd64]


;My Google Glass
%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_9001&REV_0216&MI_01
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_9001&MI_01

When I did these, I can adb devices.

3. Install driver using fastboot.

I tried "fastboot devices" but no device. Because Fastboot mode use a different 
driver.

If you use windows 8, you have more things to do.( 
http://revryl.com/2013/08/06/install-unsigned-drivers/ )

Install fastboot driver. ( 
http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sd
k/3/ )

-----------------------

When I do these things, I can get root.

$ adb reboot bootloader
$ fastboot devices
$ fastboot oem unlock
$ fastboot oem unlock

Original comment by prinum...@gmail.com on 23 Oct 2014 at 9:41