Database Develop

Usb Driver Problems

Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying

magma9495 said:
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
Click to expand...
Click to collapse
I'm having the same issue myself i think.
Look under N1 Q&A and find the topic "N1 Bricked"
Glad to know im not the only one

I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
I have a tutorial called ADB 4 Dummies that will walk you through installing the android sdk 2.2(froyo) and setting up your environments. Step by step for every system.
First thing, unplug your Phone from computer, uninstall ALL drivers and try from scratch.
Also, if you're using windows, when you're done and you plug in your phone, don't choose to "automatically find drivers" instead manually point it to the drivers folder in the SDK.
Don't worry, it's not bricked. lol.

mrandroid said:
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
Click to expand...
Click to collapse
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up

magma9495 said:
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
Click to expand...
Click to collapse
Hmmmm....
There are 2 modes to the bootloader HBOOT and Fastboot.
Make sure you're phone is in fastboot mode... it should say FASTBOOT USB highlighted in red on top. If it doesn't, use the volume down key, select Fastboot and hit the power button once to switch the phone to fastboot.
Remember, "adb devices" works while your phone is turned on regular. If your phone is in Fastboot mode use "fastboot devices"
Ok, are you using windows? If you are;
Turn off your phone and boot it back up in Bootloader mode. (trackball+pwr, or volume down+pwr)
Once it's on bootloader, plug it in to the computer.
See if the computer asks for any drivers, etc. If it does point it to the Drivers folder in the SDK. If it doesn't... go into your Device Manager. (Right click on MY COMPUTER, click on MANAGE and when computer management opens up, go to Device manager from the list on the left). Look to see if there are any icons with an Exclamation mark and yellow background. If there is, right click on it, select update driver and point it to the drivers folder in the sdk.
Basically there should be a menu on top that says "Android Phone" and when you expand that selection you'll see "Android Bootloader Interface".

nope, no luck with that either, I tried it both on windows XP and windows 7. same error each time. Could it be a problem with my device? because Snow Leopard doesn't recognize the nexus as a storage device or anything

Damn. I think i'm out of options. Last thing to try:
- Turn on phone regular.
- Plug in through USB to computer (try a different USB cable, even if that one worked with the CLIQ, try a different USB port also.)
- On Phone: GO to settings, Application Settings, Development, USB Debugging, (if it's checked on, check it off then on again) make sure it's ON.
Go into your Android SDK folder, go into the TOOLS folder. Now click on DDMS. See if it lists your device...
Last thing would be to go back through the Device Manager, and click on SCAN HARDWARE while your phone is plugged in... It has to be on that list somewhere, whether it's a bad driver, etc, it should still appear in your device manager somehow.

alright that didnt work, but, i got it, i just kept unplugging and plugging back in my phone until adb recognized it. then i got fastboot to run and now i have superuser . But now im stuck at another point. I'm trying to do the recovery.img file. I tried in mobile terminal "flash_image recovery /sdcard/recovery.img" but it told me something like "flash_image not found" I saw that i could do this via fast boot but i dont know how to do that. how would i do fastboot on Mac?

http://www.myhangoutonline.com/tutorials/nexus-one/6-upgrade-nexus-one-recovery

when i try to do the fastboot command i get "-bash: fastboot: command not found" i dont think i have fastboot set up right

have you tried typing in "./" before the command? I found that that was one of my mistakes I did when I first rooted my phone

tried that, entered "./fastboot-mac flash recovery recovery.img" and i just get "waiting for device"

I believe you can also try "./fastboot-mac flash recovery ./recovery.img"

Alright I flashed a clockwork recovery through the app manager in the market. Is there any way I can apply the other recovery with an update.zip?
Also, thanks so much for all the help guys!!!!!!!!!!

you can do it through terminal emulator, if you go to amonra's recovery thread he tells you how.
this is the link http://forum.xda-developers.com/showthread.php?t=611829

fastboot somtimes doesn't come in the SDK... download the version for your system from here: http://www.myhangoutonline.com/tutorials/nexus-one/5-unlock-nexus-one-bootloader
place it in your androidsdk/tools folder

[Q] Can't get out of recovery mode

First I want to apologize for the double post (post in General)
I used odin to get froyo on the Captivate. That worked fine. When I try and root 2.2, the phone froze and now it won't get out of recovery mode. I have tried every combination I can think of to reboot the phone short of throwing it down the street, but I cannot get out of recovery mode. I am also unable to use the power button (ok key?) to select anything. I can use the volume keys fine for up and down.
One of the errors says:
"(Unknown error: 0) ensure_root_path_unmounted++
ensure_root_path_unmounted (/mnt/internal_sd)
ensure_root_path_unmounted ret 0
unmount(/mnt/internal_sd) attempt 1 (unknown error: 0)
Install default apk-files. finished.
Mind you, I have already tried to put the rooted 2.2 files on the sd card, but still to no avail. Any suggestions? I am really hoping this phone isn't rooted.

So you have a european firmware? Which one is it?
Sent from my phone so excuse the spelling errors

I just fixed it. Reinstalled the firmware with Odin and it's working fine now. Thank you.

dude how did you do that.. I have the same friggin issue and I can't fix it. I'm stuck in recovery mode all the time, as soon as I plug the phone in to charge, or plug it in the computer via usb, or push the power button, the damn thing goes into recovery mode and stays there. I can use the volume buttons to navigate up and down through the options and if I hold the power botton down long enough the phone will turn off and back on again. But if I press the power button once (as in select an option) it doesn't do anything. I tried every single option out there to get into download mode with the battery out and usb in and volume buttons then put bat in....etc nothing works. I need to get into download mode
anyone?................

anyone that is messing with flashing firmwares on their phone needs to learn basic ADB skills.
use the following command in adb:
adb reboot
it will get you out of recovery mode

Pirateghost said:
anyone that is messing with flashing firmwares on their phone needs to learn basic ADB skills.
use the following command in adb:
adb reboot
it will get you out of recovery mode
Click to expand...
Click to collapse
What he said. Plus, I have had it happen sometimes that no matter what I always reboot into recovery. At that point I just adb reboot download and re-flash.

ok thanks. I know I said I have tried everything before but I wasn't completely truthful. I did try ADB though, but I don't think I was doing it right. I downloaded the SDK thing and started a command prompt from "start menue, accessories, and command prompt" but when I type the command "adb reboot download" nothing happens and the command prompt disappears. I don't have much experience with ADB, is there anyway you can give step by step instructions on how to do this? I would very much appreciate it.
Thanks

I found this thread on here "http://forum.xda-developers.com/showthread.php?t=517874" but still didn't help me much. Everytime I type cd c:\Android or any other command I get The system cannot find the path specified.

Here's what I do. After you download the sdk. There is a folder called tools. I copy that to c:
Then opencommand prompt and type,
C:
CD tools
adb reboot
Or, adb reboot download
Of course make sure your phone is connected via USB.
Sent from my SAMSUNG-SGH-I897 using XDA App

thanks I'll try that when I get home. I think this might take care of the problem, because I did keep the folder on the desktop and did not move it to C: folder. Although when I plug in the phone via USB, I still can't establish connection between phone and computer, but I will let you know how it goes after I get home tonight. and I did find some stuff about ADB through google so I might be able to do something with it tonight.
Thanks for the help though

Download odin one click, remove the battery, open odin, replace battery, hold down both volume buttons, and plug the usb cable in. That should get you to download mode unless your 3-button doesn't work.

bobbylx said:
Here's what I do. After you download the sdk. There is a folder called tools. I copy that to c:
Then opencommand prompt and type,
C:
CD tools
adb reboot
Or, adb reboot download
Of course make sure your phone is connected via USB.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Hi, so I did all that heres a copy and paste of what I did and results I got
"Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Shahed>cd c:\
c:\>cd c:\android-sdk-windows
c:\android-sdk-windows>tools
'tools' is not recognized as an internal or external command,
operable program or batch file.
c:\android-sdk-windows>cd tools
c:\android-sdk-windows\tools>adb reboot download
error: device not found
c:\android-sdk-windows\tools>"
I guess it can't be done because the device is not initiated to begin with

jatkins09 said:
Download odin one click, remove the battery, open odin, replace battery, hold down both volume buttons, and plug the usb cable in. That should get you to download mode unless your 3-button doesn't work.
Click to expand...
Click to collapse
tried that still nothing.. keeps saying waiting for device

drhusamali said:
tried that still nothing.. keeps saying waiting for device
Click to expand...
Click to collapse
Find the tools folder in the SDK you dowloaded and extracted, I found a shortcut to it scroll over the tools folder, hold the shift key and right click on the tools folder then choose open command window here.
When the command window opens type the command ADB shell then hit enter, then type adb reboot download then hit enter with your phone plugged into pc. This always works for me. You can always change the path by moving the folder directly to your c drive but this will work for you for now.

Pirateghost said:
anyone that is messing with flashing firmwares on their phone needs to learn basic ADB skills.
use the following command in adb:
adb reboot
it will get you out of recovery mode
Click to expand...
Click to collapse
This has saved my azz a few times.....Learn to use adb mode from PC inDEEED!!!!
Adb recovery adb download ....on and on.....

fastboot help.

Maybe somebody can give me some pointers how to install fastboot? I hold arrow down then hold power till it goes into fastboot. I then plug it into the computer and install the drivers. which it did. but in fastboot it still says starting fastboot usb protocol. I check device manager and it recognize my dell. But yet i still have no fastboot on my device? what am i missing?

Make sure that you are using fastboot from the latest SDK.

Ok i guess i dont fully understand fastboot then. Does fastboot take commands from pc to device. Or if i install it correctly will fast boot be on the device? Does that make sense.
sent from my re-engineered dInc

There is a fastboot.exe file that is included with the SDK and there is a fastboot mode that you boot your android device into with power + volume down. It is already there by default.
The exe file is used from the command line to pass commands to the android device while it is it 'fastboot' mode.

Ok so im passing commands from the pc to the device. Got it. I just unistalled my old version of sdk and did a fresh install. About to give it another go. Somebody needs to port clockwork over. Lol thanks kable
sent from my re-engineered dInc

I was about to say,
just make sure you properly installed your SDK then should be fine.

Im getting app failed to start because adbwinapi.dll was not found. What is causing this and how do i fix it?
sent from my re-engineered dInc

This is when i try to open the fastboot in tools
sent from my re-engineered dInc

ive done everything by the books and I cant figure out why the.dll file is missing. When I know its installed. I tryed this on 2 different comps. One on vista and one on xp. Installed everything as I should and no dice. Oh well if someone happens to port clockwork is that going to be flashed via fastboot? Or will it be an update.zip? Flashed through the updater? Can someone point me in the right direction maybe? Ive never had this much trouble with getting into bootloader.
Sent from my Dell Streak 7

its in another directory of the SDK.
Sent from my Dell Streak 7 using Tapatalk

happen to know which one? I see the folder on my sd card should I copy off it and move it too another folder in sdk?
Sent from my Dell Streak 7

nm found it. Im going to start on a fresh restore of my pc.
Sent from my Dell Streak 7

im giving up. Ha I cant figure it out for the life of me oh well.
Sent from my Dell Streak 7

some tips
1. Follow the guide "What Is ADB And How To Install It With Android SDK" by searching google for "adb install" (should be third link down)
*Note: That will help you install the latest SDK and drivers etc, don't forget to add the path **
2. Make sure you have a copy of the Drivers from the streak itself, these are what you should be using for the fastboot mode.
3. Open a command prompt and go to c:\android-sdk-windows\tools
4. Make sure your streak is in fastboot mode using the volume down/power button
5. check that fastboot see's the device by doing "fastboot.exe devices"
6. If you see a ? blah blah then it works, if you see nothing, then its not working.

Thanks i installed sdk per that write up. Still no dice. Where should i place the copy of the drivers. But im sure i did this as well. Ill wait. Im pretty happy with the way things are with it stock. Atleast i have root and can do what i want within the device. Thats the thing i cant even get a command prompt to take. Oh well ill do some more investigating later
sent from my re-engineered dInc

What should it say in device manager when the device is plugged in? Mine currently says android phone. Click on it and it says android composite adb interface. Is there where im doing something wrong? It should say adb devices correct?
Sent from my Dell Streak 7

Figured it out.
sent from my re-engineered dInc

Reinstalling stock firmware?!?!

Ok I've been at this for hours trying to get adb to recognize the tablet in recovery mode and to no avail. I've tried every trick and random driver i can find on here and still am unable to get adb to recognize the tablet while waiting for a sideload .bin file. While in normal mode while up and running adb devices command find sit np but once it goes into recovery it's gone.
I type adb devices and it comes back null. I've tried killing and restarting the daemon server and that isn't it. I've tried uninstalling and reinstalling the drivers. There is even an ADB composite driver listed in the device manager and yet once the tablet is in recovery mode it seems to disappear.
I tried doing a factory reset and wiping the cache. i'm drawing a blank on this. I've also tried changing usb ports and cables on the computer. It's just not working.
Any ideas?

You may need to disable driver signature enforcement
then install drivers.
After that you may still need to follow this guide
http://forum.xda-developers.com/showpost.php?p=62561874&postcount=2
This was written for a different FIRE so yours will be KFFOWI instead of KFARWI in the guide.
I did this and in worked for me..

There are two options to restore stock at the bottom of this link, it all depends what version you have. See if it helps...
http://forum.xda-developers.com/showpost.php?p=62986666&postcount=4
or you could also try this to get into Amazon Custom recovery:
adb reboot recovery

Yeah, most likely a driver issue. Try different drivers until you find one that actually works!

Well I just thought of this when I woke up, could it be that I'm using minimal ADB and fastboot or should that not make a difference?

As long as your device is listed when doing a "adb devices" or "fastboot devices" should make no difference. But yes, minimal should be fine.
But it is usually a good idea to have the latest version.
I think your issue is with getting to Amazon recovery. If in recovery, there should be a menu. See that menu here in post #3:
http://forum.xda-developers.com/amazon-fire/general/amazon-fire-2015-tips-tricks-t3214544

Tuvan03 said:
Ok I've been at this for hours trying to get adb to recognize the tablet in recovery mode and to no avail. I've tried every trick and random driver i can find on here and still am unable to get adb to recognize the tablet while waiting for a sideload .bin file. While in normal mode while up and running adb devices command find sit np but once it goes into recovery it's gone.
Click to expand...
Click to collapse
You're talking 2 different modes here: (1) Recovery mode: You see menu options on tablet. Windows can't ever recognize device while in recovery mode; no driver appears in Win Device Manager. (2) Sideload mode: After you select "apply update from ADB" and press power button and you see yellow text on tablet saying to sideload the file. Fire appears in Device Manager. If no driver installed (or messed up), it's under "Other" with the name KFFOWI as @gray-beard said. That's what you need to install drivers for in order for sideload to work. I doubt Minimal adb is the problem. You're probably just not all the way into sideload mode. If problems persist, open the console window from the folder containing adb.exe.

gray-beard said:
You may need to disable driver signature enforcement
then install drivers.
After that you may still need to follow this guide
http://forum.xda-developers.com/showpost.php?p=62561874&postcount=2
This was written for a different FIRE so yours will be KFFOWI instead of KFARWI in the guide.
I did this and in worked for me..
Click to expand...
Click to collapse
Many Thanks Gray Beard, it's reloading the stock firmware now. I was just trying to go through the pick your device drivers thing too quickly and needed to do the see all devices to be able to see the adb drivers to get them loaded.
A pint of the finest dwarven ale to you (with a name like gray beard i couldn't resist)
EDIT: I did all this just to try to restore OTA updates, yet i hit the update button now that it's restored with the factory firmware and it's saying no updates found. hmm

google glass stuck on "glass" text screen

Okay I know I need to wipe the device and/or reinstall the update
But I have no clue how to use android SDK or adb.
I have them both downloaded, not sure if they are installed for google glass access.
I'm using the command prompt and I search for adb or fastboot but no devices come up?
I downloaded the XE22 (latest firmware) but when I open that it asks me to burn a cd?
I'm lost and glass support won't help. Anybody?

phild22 said:
Okay I know I need to wipe the device and/or reinstall the update
But I have no clue how to use android SDK or adb.
I have them both downloaded, not sure if they are installed for google glass access.
I'm using the command prompt and I search for adb or fastboot but no devices come up?
I downloaded the XE22 (latest firmware) but when I open that it asks me to burn a cd?
I'm lost and glass support won't help. Anybody?
Click to expand...
Click to collapse
I just went through this to get to XE23. Did you ever get to the answer? Very similar process to flashing any other android device; identical really. LMK if you're still charging and using or want to.
GH

greddy91 said:
I just went through this to get to XE23. Did you ever get to the answer? Very similar process to flashing any other android device; identical really. LMK if you're still charging and using or want to.
GH
Click to expand...
Click to collapse
Ok... As I am new to the Glass game.... Last night, when I got the unit fully charged (Sitting at SW version XE12), I connected it to the network to update.... This morning, I have a bootloop issue.
I want to flash XE 12 back to the device and try to let it update again.... I have yet to find a clear breakdown on how to falsh this... SDK is installed.... But it appears that I don't have a the proper USB drivetr and have know idea how to install it...
Really could use some help with the entire process...

So, sharing files used on Google drive:
https://drive.google.com/drive/folders/0B3-nca6GSfX1R2h1eDNDUjZwRVk?usp=sharing
Installed Minimal ADB and hit yes all the way through - in the google drive above.
This gives ADB commands functionality anywhere in CMD
I plugged in the glass and it came up as a USB drive - AWESOME.
Enter Command Prompt
Navigate to the directory where I had the Glass EX23 unzipped
Entered "adb devices" to make sure ADB was seeing the Glass (make sure no other android goodies are plugged in)
It was there so...
Enter "adb reboot bootloader"
My glass went blank.
Entered "fastboot devices" ... and nothing.
So opened "Device Manager"
There was a flagged driver standing out for when I flashed an old Note 2. There's the problem...
Right click and chose "Update driver" and pointed it to the "usb driver" directory extracted from the zip file in the google drive above.
Chose Android Composite ADB Interface - Skipped past the unsigned driver warning
Voila - the device is now seen in device manager
I then entered the command in cmd "fastboot devices" - and still blank
Unplugged glass and rebooted.
After it came up, plugged it back in - seen as USB drive again. Still good!
Entered "adb devices" to make sure ADB was seeing the Glass
It was there again so...
Enter "adb reboot bootloader"
My glass went blank again.
Entered "fastboot devices" ... and there it is!!! The Gates of Valhalla are in sight!!!
Assure you're in the directory where the google image has been unzipped...
Now begin by entering:
"fastboot flash boot boot.img"
let it complete
Now "fastboot flash system system.img"
let it complete (this is the longest one... be patient)
Now "fastboot flash recovery recovery.img"
Now "fastboot flash userdata userdata.img"
Now "fastboot erase cache" - takes a bit of time for cleanup
Now "fastboot reboot"
The moment of glory has arrived... watch your glass go through boot - yes the Glass screen turns on and off a few times and flashes some odd colors... again, be patient... took like 5 minutes and ate up 40% of my full battery, but there it was XE23 and full stability.
Note - NONE of these utilities are mine, they were borrowed after researching in hundreds of other threads on how to get this done.
Of note... I came from XE10 straight to XE23 with no issues.

Legobricke said:
Ok... As I am new to the Glass game.... Last night, when I got the unit fully charged (Sitting at SW version XE12), I connected it to the network to update.... This morning, I have a bootloop issue.
I want to flash XE 12 back to the device and try to let it update again.... I have yet to find a clear breakdown on how to falsh this... SDK is installed.... But it appears that I don't have a the proper USB drivetr and have know idea how to install it...
Really could use some help with the entire process...
Click to expand...
Click to collapse
What version of Glass is it? And there is a thread under development about modifying your android_winusb.ini file so you can manually select the driver.

Muskeman16 said:
What version of Glass is it? And there is a thread under development about modifying your android_winusb.ini file so you can manually select the driver.
Click to expand...
Click to collapse
It is model XE-C running version XE-12...

Legobricke said:
It is model XE-C running version XE-12...
Click to expand...
Click to collapse
Have you attempted to re-flash it at all?

Muskeman16 said:
Have you attempted to re-flash it at all?
Click to expand...
Click to collapse
That is was I'm attempting to do.... But I'm not having much luck....
I am sure that USB debugging was not turned on.... When I put the Glass in to fastboot mode (holding down camera button and turning on which gives me short fast bursts from the power light) it doesn't seem to recognize it on the desktop. I get 3 low tones when I plug it in and ADB doesn't see it...
I guess I need a direct breakdown of the process... I have searched the net and forum, but the ones I find seem to drop a process or imply something that I'm not understanding.
I have flashed devices before and I'm familiar with the process, but I'm missing something when it comes to the Glass....
When I power up (normal power up) and the plug it, device manager lists it as Android Device. When I open that, just shows ADB Device Interface... I have tried to update the entry with the USB driver, it is claims the drivers are up to date.
I am using Windows 7.... But it is clear that ADB is not seeing the device... So, I'm stuck until I can findout how to get the device to be recongized.... What is strange is that when I plug the Glass in, it does see it in the tray below... It even allows me the "eject Glass_1... but for the life me, I can't get ADB to see it...
Any help is appreciated!

Ok.... I can finally see the Glass in ADB.... But only if I put the Glass in Fastboot mode prior to plugging in to USB.... I adb "fastboot device" and get a serial number.... Then I adb "fastboot flash boot boot.img and get FAILED (remote failure)...
What am I doing wrong?

I have even tried to unlock the device, but it hangs at erasing userdata.
The very interesting thing is on a few occasions, I have gotten GLASS to work....
I re-set it up.... and then it works fine until I have to charge it again and then it goes back to the freezing on the GLASS screen.
Every time I try to flash Boot/system/ etc image... it fails.... Not sure why....

Ok....
Finally nailed it.... No more GLASS looping....
I took this unit that was experiencing GLASS loop at firmware X12 to X23... What a journey....
To start.... I downloaded the "minimal adb fastboot" and installed....
Then I downloaded the new firmware from google
I dragged the zip folder to my desktop and extracted it....
At this point, I put GLASS in fastboot mode (Hold camera button down then press the power button. Once power light come on, let go of the power button but keep camera pressed. One the light starts to flash (slowly, not fading), you are in fastboot mode).
I then attached the glass via usb cable to computer (I was operating Windows 10).
Open device manager and look for "android devices" and open it. You should see "Android ADB Interface" - Right click on it and select Update Driver Software". Then select Browse my computer for driver software. The select "Let me pick from a list of device drivers on my computer". Look for "Android ADB Interface". Select it and then update it.
Once this is done, got to your icon tray (should be down in the bottom right of your scree) and right click on "Safetly Remove Hardware or Eject Media". It should open a window up. Confirm that glass is there.
Then go to the desktop where you extracted the firmware and open the folder. Once open, Hold shift and right click. This should give you a menu. You are looking for "Open command window here". select it and it should open a command window.
Then follow the instructions listed on the google firmware page.
I didn't follow all the instructions.... The ones I did were enough to fix my boot looping GLASS -
1.) fastboot devices (This should comeback with a serial number. If it doesn't, be sure you have the glass in fastboot mode)
2.) fastboot oem unlock ( I had to do this because the device would fail when I tried flashing to the device. This was the only way I could get it to take the flashing). It will make you type this twice to confirm you wish to unlock.... This will erase all the data (cache and user data) on the device and you have to be patient.... It does take some time... If you think it has hung up (which I did), I just hit a key on my keyboard and then pressed enter.... It then confirmed that the unit had been unlocked.
3.) After I unlocked the unit, I then typed fastboot devices again just to be sure that it was still reading the GLASS.
4.) fastboot flash boot boot.img - This will fail if you don't have the unit unlocked.... The first time I did this, the glass unit went down and I had to start the process again. The second time I did the process, it worked.
5.) fastboot flash system system.img - This did take a few minutes
6.) fastboot flash recovery recovery.img
Once done, I closed the command window and ejected the glass unit from the computer..... I pressed the power button and BOOM! I was back to a working glass...
One key element I must point out.... allot of this process requires allot of patience....
The pages that are linked above will help you through the process.... I took a week of researching.... But it was worth it...
There are risks involved - bricking/etc.... But this is the process that worked for me...
Good luck!

Legobricke said:
Ok.... I can finally see the Glass in ADB.... But only if I put the Glass in Fastboot mode prior to plugging in to USB.... I adb "fastboot device" and get a serial number.... Then I adb "fastboot flash boot boot.img and get FAILED (remote failure)...
What am I doing wrong?
Click to expand...
Click to collapse
Just for clarity - I associate adb and fastboot as two seperate commands.
"adb devices" gives you your android attached devices inventory
"fastboot devices" gives you your attached devices in fastboot
The "adb reboot bootloader" changes the device seen in adb to a device that can be seen in fastboot.
Not sure if that was clear before, but it may help here.

greddy91 said:
Just for clarity - I associate adb and fastboot as two seperate commands.
"adb devices" gives you your android attached devices inventory
"fastboot devices" gives you your attached devices in fastboot
The "adb reboot bootloader" changes the device seen in adb to a device that can be seen in fastboot.
Not sure if that was clear before, but it may help here.
Click to expand...
Click to collapse
Thanks for the clarify....
I attempted to go the adb route, but could never get the system to see the GLASS in adb... and because the GLASS was looping on the GLASS screen, I couldn't activate USB Debugging..
So, I found out in researching that I could manually put the GLASS in fast boot mode....
Once it was unlocked, everything took...

not a tech guy -_-
Hi thanks for clearifying But could you explain step by step and like i know nothing about commad prompt. Im just tring to work my glass but at turkey i cant find any coder who understands this. (sorry for bad english)