Bricked by Update ?
This seems to happen a lot I'm afraid. The symptoms are:- You try to start your glasses and you are stuck on the glass logo.
- The device is producing a significant amount of heat.
First rule
First of all don't panic. I panicked and it probably did cost me some extra effort.
Second rule
Your next step would depend on where you are and what you have planned. You should probably contact google but be aware that you probably will be sucked into answering a lot of irrelevant questions, waiting for replies and probably start answering a lot of the same and quite similar questions.
They are quite good at convincing you to believe in their confidence in resolving your problem no matter your deadline, even if they don't have the foggiest idea about what your problem is and in even lesser degree how to fix it. I guess there is some kind of positive emphasis customer support training at work.
If your Geo locations or schedule permits it you should insist on replacements if you are still within warranty.
So secondly don't trust google support, define your own point of no return where you will go off the reservation in persuit of anything that works.
Keep track on other users experiencing the same problem and if they are able to peg it down to a recent upgrade even if you can not be sure yourself. Your glasses will auto update on the strangest points of time and unless you are actively wearing them you will never know.
Being in Europe with an important meeting to demonstrate the glasses this was not an option for me to get replacements and after 3 days of being lead around in the desert by Google support I had to take drastic action.
Going off the reservation
So what to next ?
First of all: This will void your warranty and make your life with Google support difficult. So consider carefully if you are willing to proceed and if you should do so do it 100% at your own risk and peril.
Firs of all check that you are able to connect to the device using adb and retrieve the system logs.
First of all: This will void your warranty and make your life with Google support difficult. So consider carefully if you are willing to proceed and if you should do so do it 100% at your own risk and peril.
Firs of all check that you are able to connect to the device using adb and retrieve the system logs.
adb shell logcat > log.txt
Google may love you for these in determine their problem.
If you don not get the logs I'm not sure if you should proceed or not since this might indicate that you have a different problem.
Preparations
- Charge you device to a sound level.
- Be aware that it does not charge very well for very long in this state due to the heat it develops. I solved this by having a paper towel and ice water. Tear of a pice, put it water and press most of the water out. Be aware of the buttons, microphone and track pad.. Replace when you can feel it getting dry.
- Monitor the charging light, once you observe it to get dull turn the device off and let it rest for half an hour.
- You can expect to use more than 3 hours doing this.
Prepare your computer use a computer you know to work. Do never,ever use a mac using a mac that I knew to work did cost me two days.
Execution
- Get the system images located at Google.
- After booting in fastboot mode execute:
fastboot oem unlock
- Follow the procedure described at that page for "to flash Glass back to factory specifications".
- Do not panic if you are not able to flash the restore image.
Ingen kommentarer:
Legg inn en kommentar