[HBOOT][3.19.0.0000][S-OFF] StopYellingAtMe - HTC Desire 510

You must have S-OFF in order to be able to install this custom HBOOT.
What is it?
This is a hex-edited HBOOT (3.19.0.0000) that makes all the text (well, as much as possible) lowercase (as opposed to all uppercase, which is the default) and it removes the red warning text on boot. This is designed to be run on A11_CHL (I'm kinda new to this device. I literally just got it yesterday. I bought the Sprint variant, so I'm not sure what other variants this is compatible with).
Gimme teh download link plx
Okay, here you go.
I, personally, don't check the MD5 on things, but if I were you, I would double-check it, just to be safe.
How to install:
1) Download from the link above
2) Place your device in fastboot mode.
3) Plug your device into your PC, ensuring that you already have fastboot drivers installed (if needed).
4) Issue the command "fastboot oem rebootRUU" via Command Prompt or Terminal
5) In that same window, issue the command "fastboot flash zip " (notice the space on the end there) then drag-and-drop the file you downloaded into the Command Prompt (or Terminal) window then hit enter. If nothing happened after you hit enter, click inside the Command Prompt (or Terminal) window and hit it again.
6) After the command completes successfully, issue the command "fastboot reboot".
7) Now, whenever you boot to hboot, your phone will no longer be yelling at you.

r3pwn said:
You must have S-OFF in order to be able to install this custom HBOOT.
What is it?
This is a hex-edited HBOOT (3.19.0.0000) that makes all the text (well, as much as possible) lowercase (as opposed to all uppercase, which is the default) and it removes the red warning text on boot. This is designed to be run on A11_CHL (I'm kinda new to this device. I literally just got it yesterday. I bought the Sprint variant, so I'm not sure what other variants this is compatible with).
Gimme teh download link plx
Okay, here you go.
I, personally, don't check the MD5 on things, but if I were you, I would double-check it, just to be safe.
How to install:
1) Download from the link above
2) Place your device in fastboot mode.
3) Plug your device into your PC, ensuring that you already have fastboot drivers installed (if needed).
4) Issue the command "fastboot oem rebootRUU" via Command Prompt or Terminal
5) In that same window, issue the command "fastboot flash zip " (notice the space on the end there) then drag-and-drop the file you downloaded into the Command Prompt (or Terminal) window then hit enter. If nothing happened after you hit enter, click inside the Command Prompt (or Terminal) window and hit it again.
6) After the command completes successfully, issue the command "fastboot reboot".
7) Now, whenever you boot to hboot, your phone will no longer be yelling at you.
Click to expand...
Click to collapse
Is there some way to get s off yet? Because most of us don't have s off so we can't use this..

MrMike2182 said:
Is there some way to get s off yet? Because most of us don't have s off so we can't use this..
Click to expand...
Click to collapse
Sunshine works for S-OFF.

welcome to the community
btw,working and looking great on A11_UL with the red splash,awesome work

pattyboi:) said:
welcome to the community
btw,working and looking great on A11_UL with the red splash,awesome work
Click to expand...
Click to collapse
Thanks. I'm rocking the Nyan Cat splash screen myself. It makes the phone's weird blue color a little less weird.

writing 'zip'...
(bootloader) zip header checki
(bootloader) zip info parsing.
FAILED (remote: 99 unknown fai
finished. total time: 1.528s
cricket version

Related

Cant get into fastboot

Well, Im trying to unroot, however I am having a problem getting into fastboot to remove a second splash screen. When on the "skate boarding" screen, the command prompt on my PC pops up for a second then closes. I'm pretty sure there is something I'm doing wrong, but I just can't figure out what.
Any assistance would be appreciated.
Thanks
CM- 3.9.7
Palm Pre v1.9
So your saying that when you open up command prompt it only stays up for a second and closes.
When I manually open command prompt, it stays open. However, when the PC tries to load fastboot.exe, it opens and closes quickly.
fastboot.exe is a command line utility, running it by itself (without arguments) will produce the behavior you are seeing.
To use it you drop to a command prompt and enter a command such as:
fastboot devices
to see if your phone is being recognized in fastboot mode...
or
fastboot flash system system.img
to flash the system with a backup image.
You get the picture?
uva463 said:
When I manually open command prompt, it stays open. However, when the PC tries to load fastboot.exe, it opens and closes quickly.
Click to expand...
Click to collapse
Your not suppose to open up fastboot.exe
daveid said:
fastboot.exe is a command line utility, running it by itself (without arguments) will produce the behavior you are seeing.
To use it you drop to a command prompt and enter a command such as:
fastboot devices
to see if your phone is being recognized in fastboot mode...
or
fastboot flash system system.img
to flash the system with a backup image.
You get the picture?
Click to expand...
Click to collapse
Thanks for info. After trying to get the phone recognized, I went back and redid everything and found out I had the wrong USB drivers
Thanks again

[Q] Unlock Bootloader Problem

Hi guys, I have a problem.
I want to flash my N1 with the Cyanogenmod, but I have a problem with Bootloader unlocking. I do exactly what here is written (in the N1 guide from wiki.cyanogenmod), but when I open CMD (win XP) and write "fastboot oem unlock", it just doesn't works, but "adb devices" works and shows my phone. What can I do ? Any ideas ?
You need to boot into bootloader to work with fastboot. And if "adb devices" shows your phone - you obviously didn't boot.
adb reboot bootloader
Click to expand...
Click to collapse
Also, for a more comprehensive guide, please read the Wiki.
Code:
C:\fastboot>fastboot oem unlock
'fastboot' is not recognized as a
operable program or batch file.
This is what it shows in bootloader mode.
P.S. I have already re-installed my drivers. I have to notice that when I try to reinstall the drivers (in fastboot mode), they always auto-install themselves and when I try to update them, they say that there isn't newer version.
Fastboot executable isn't in the same directory as ADB executable, and isn't in the path you're executing it from (which is C:\fastboot).
Check, what is the actual executable you're trying to run, and if you have one. It might be called fastboot-windows.exe, if you didn't get it from downloading the Android SDK.
There is a executable file named "fastboot-windows.exe", but when I try to run it, it just open and close for 1 second. Any ideas ?
I thought the message would be clear by now... Oh well.
Open command prompt.
Run:
fastboot-windows oem unlock
Click to expand...
Click to collapse
I think It's done but my computer shows this message (see attached) 5 mins and I don't know it's ready or not ? Could I turn on the phone ? (Sry for the easy questions but I'm a real noob, because that's my 1st Android phone.)
The "too many links" message doesn't look good.
Reboot your computer.
Reboot the phone.
Use different USB port in your computer.
Ok well if you want my input try "fastboot devices" this should return your S/N (starting with "HT") if it gives you the same error then I would reinstall the SDK.

Unlock bootloader Developers edition verizon

Can someone help me figure out how to unlock my bootloader on my dev edition. It seems very simple but I'm not very command prompt savvy. All step by steps and links are appreciated! Thanks!
Sent from my XT1060 using Tapatalk
Swimboy46163 said:
Can someone help me figure out how to unlock my bootloader on my dev edition. It seems very simple but I'm not very command prompt savvy. All step by steps and links are appreciated! Thanks!
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Step by step instructions are on moto's site.
https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth
It's pretty straight forward.
Coop9 said:
Step by step instructions are on moto's site.
https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth
It's pretty straight forward.
Click to expand...
Click to collapse
This is the part I'm unclear on:
2. On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android SDK tools (or make sure fastboot is in your $PATH)
Sent from my XT1060 using Tapatalk
Swimboy46163 said:
This is the part I'm unclear on:
2. On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android SDK tools (or make sure fastboot is in your $PATH)
Click to expand...
Click to collapse
Start > type "cmd" and launch. You get a black box with white letters in a mono-spaced font.
Run the following (assuming this is the right path for you): SET PATH=%PATH%;C:\Program Files (x86)\Android\android-sdk\platform-tools
Then you should be able to run fastboot.exe and continue on.
Alternatively, you can browse in a file explorer window to that directory, then right click on it (maybe while holding shift) and choose "Open command window here"
icrf said:
Start > type "cmd" and launch. You get a black box with white letters in a mono-spaced font.
Run the following (assuming this is the right path for you): SET PATH=%PATH%;C:\Program Files (x86)\Android\android-sdk\platform-tools
Then you should be able to run fastboot.exe and continue on.
Alternatively, you can browse in a file explorer window to that directory, then right click on it (maybe while holding shift) and choose "Open command window here"
Click to expand...
Click to collapse
i am working on a guide right now to try and make it as easy as possible but moto requiers you to sign in inorder to get everything done. but the correct command for Windows is CD then the location ware your adb and fastboot files are
Click on the link below and pick your Moto X by what carrier you are with
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/87215/action/auth
im going to try and do this the best i can but no matter what i do your going to have to go to the moto website to get the unlock key
download the SDK and install it.
locate ware it was installed normally (C:\Program Files\Android\android-sdk)
open Command Prompt and type
Code:
CD C:\Program Files\Android\android-sdk\platform-tools
put phone into bootloader
type below commands in CMD
type
Code:
fastboot oem get_unlock_data
it should come back with something like this
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Now we need to remove all the (bootloader) and make the key into one line
we then need to paste this into the box on the bottom of the Moto unlock page and hit the button "Can my Device be Unlocked"
if your device can be unlocked you need to accept the license agreement and then click the button to request your key. It will then email you your unlock key.
Copy your unlock key then click the link Step 3
now if you left your device connected and everything ware it was then great if not we need to put are phone back into bootloader and open a CMD and CD it to the same directory as before.
then type
Code:
fastboot oem unlock UNIQUE_KEY
ware Unique_key being the code you copied from your email.
now your bootloader is unlocked.
Sorry this guide is not great but it is the best i can do for the fact that you have to be on the moto website to get your unlock key. i hope this helps somewhat.
IMO, if you can't figure out Motorola's instructions, you should leave your phone as it is. There is nothing difficult about it, and learning how to do it will help you in the road should something happen to your phone and you need to recover.
Sent from my Moto X
dray_jr said:
i am working on a guide right now to try and make it as easy as possible but moto requiers you to sign in inorder to get everything done. but the correct command for Windows is CD then the location ware your adb and fastboot files are
Click on the link below and pick your Moto X by what carrier you are with
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/87215/action/auth
im going to try and do this the best i can but no matter what i do your going to have to go to the moto website to get the unlock key
download the SDK and install it.
locate ware it was installed normally (C:\Program Files\Android\android-sdk)
open Command Prompt and type
Code:
CD C:\Program Files\Android\android-sdk\platform-tools
put phone into bootloader
type below commands in CMD
type
Code:
fastboot oem get_unlock_data
it should come back with something like this
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Now we need to remove all the (bootloader) and make the key into one line
we then need to paste this into the box on the bottom of the Moto unlock page and hit the button "Can my Device be Unlocked"
if your device can be unlocked you need to accept the license agreement and then click the button to request your key. It will then email you your unlock key.
Copy your unlock key then click the link Step 3
now if you left your device connected and everything ware it was then great if not we need to put are phone back into bootloader and open a CMD and CD it to the same directory as before.
then type
Code:
fastboot oem unlock UNIQUE_KEY
ware Unique_key being the code you copied from your email.
now your bootloader is unlocked.
Sorry this guide is not great but it is the best i can do for the fact that you have to be on the moto website to get your unlock key. i hope this helps somewhat.
Click to expand...
Click to collapse
When you get to the fastboot menu what option do you click Normal Powerup, Recovery, Factory, Barcodes, BP Tools?
Swimboy46163 said:
When you get to the fastboot menu what option do you click Normal Powerup, Recovery, Factory, Barcodes, BP Tools?
Click to expand...
Click to collapse
nothing you just plug your usb cable in and start the guide

[Q] W7 wont recognise phone when in fasboot mode

I've been struggling for a week with this.
Trying to unlock the bootloader but whenever I get to the stage of using command prompt I get this message;
'fastboot' is not recognized as an internal or external command,
operable program or batch file
The PC just will not recognise the phone when in fastboot mode although it does when not.
Windows 7
Android 4.3
HTC Sense Version 5.5
Software number 3.62.401.1
HTC SDK API Level 5.65
USB Debugging ticked
Fast boot deticked
HTC cable used
Latest drivers installed
Any help would be appreciated, the only previous experince I have is rooting a Galaxy note and tablet with no trouble whatsoever.
tj
tjpearson said:
I've been struggling for a week with this.
Trying to unlock the bootloader but whenever I get to the stage of using command prompt I get this message;
'fastboot' is not recognized as an internal or external command,
operable program or batch file
The PC just will not recognise the phone when in fastboot mode although it does when not.
Windows 7
Android 4.3
HTC Sense Version 5.5
Software number 3.62.401.1
HTC SDK API Level 5.65
USB Debugging ticked
Fast boot deticked
HTC cable used
Latest drivers installed
Any help would be appreciated, the only previous experince I have is rooting a Galaxy note and tablet with no trouble whatsoever.
tj
Click to expand...
Click to collapse
Do you have fastboot.exe on your computer? It looks like CMD isn't finding fastboot.exe 1-because you don't have it 2- because you have not started your cmd prompt from your fastboot.exe folder
can you post a screenshot of your cmd prompt when you get this error?
ADB Installer
Installed ADB Installer and now been able to copy and been able to submit my token.
Recieved email reply with unlock code and it came as a VLC icon, still put this onto my phone but now get message 'unable to open bin file'
Got one step further but now unable to open file.
Below is the message I get:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\tjpearson>fastboot flash unlocktoken Unlock_code.bin
error: cannot open 'Unlock_code.bin'
C:\Users\tjpearson>
Your help is very much appreciated but my wife fails to understand my pannick and she thinks out tea is more important so may not get back to you straight away.
tj
tjpearson said:
Installed ADB Installer and now been able to copy and been able to submit my token.
Recieved email reply with unlock code and it came as a VLC icon, still put this onto my phone but now get message 'unable to open bin file'
Got one step further but now unable to open file.
Below is the message I get:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\tjpearson>fastboot flash unlocktoken Unlock_code.bin
error: cannot open 'Unlock_code.bin'
C:\Users\tjpearson>
Your help is very much appreciated but my wife fails to understand my pannick and she thinks out tea is more important so may not get back to you straight away.
tj
Click to expand...
Click to collapse
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
mb_guy said:
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
Click to expand...
Click to collapse
OK, I'll try this tomorrow, thanks for the help.
Originally Posted by mb_guy
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
Click to expand...
Click to collapse
OK, I'll try this tomorrow, thanks for the help.
Click to expand...
Click to collapse
Like mb_guy said, you MUST place the bin file in the same folder where adb and fastboot are. Every time you want to flash a file to your phone it must be in that folder, otherwise fastboot won't find it and it will output you that error (can't open file). That rule apply to recovery, unlock code, rom, kernel, ruu, firmware etc etc.
Sent from my HTC One using xda app-developers app
alray said:
Like mb_guy said, you MUST place the bin file in the same folder where adb and fastboot are. Every time you want to flash a file to your phone it must be in that folder, otherwise fastboot won't find it and it will output you that error (can't open file). That rule apply to recovery, unlock code, rom, kernel, ruu, firmware etc etc.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help because at least I've now been able to unlock bootloader.
My problem now is 'fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img' command line and yet again I'm getting error unable to open as below;
C:\Users\tjpearson>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.0-m7.img'
Even placing zip on root of phone and in adb folder still no joy.
tj
tjpearson said:
Thanks for the help because at least I've now been able to unlock bootloader.
My problem now is 'fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img' command line and yet again I'm getting error unable to open as below;
C:\Users\tjpearson>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.0-m7.img'
Even placing zip on root of phone and in adb folder still no joy.
tj
Click to expand...
Click to collapse
''error: cannot open'' is caused because fastboot don't find the file. Is the recovery file you are trying to flash is named exactly <openrecovery-twrp-2.6.3.0-m7.img> ?
Btw I'll recommend you to flash twrp 2.6.3.3 not 2.6.3.0 as you could have issur flashing newer 4.4 rom
Code:
fastboot flash recovery <name_of_file.img>
fastboot erase cache
fastboot reboot-bootloader
alray said:
''error: cannot open'' is caused because fastboot don't find the file. Is the recovery file you are trying to flash is named exactly <openrecovery-twrp-2.6.3.0-m7.img> ?
Btw I'll recommend you to flash twrp 2.6.3.3 not 2.6.3.0 as you could have issur flashing newer 4.4 rom
Code:
fastboot flash recovery <name_of_file.img>
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Yes, named exactly the same.
It's driving me mad, if the bootloader is now unlocked is there an easier way to flash twrp and then root.
Whats the best way to check adb is actually communicating with the phone
tj
tjpearson said:
Yes, named exactly the same.
It's driving me mad, if the bootloader is now unlocked is there an easier way to flash twrp and then root.
Whats the best way to check adb is actually communicating with the phone
tj
Click to expand...
Click to collapse
Do you have a Sprint phone ? and can you post a screen shot of your adb / fastboot folder containing the files or at least post your results for dir
open command prompt from your adb / fastboot folder (shift+right click - command prompt here)
type
adb devices
your device SN will be here
type
adb reboot bootloader
you should be in fastboot usb
type
fastboot devices
again your serial no should be here
type dir
you should see the contains of the folder your in
now
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
if error change the twrp name to match the one in the dir command above
clsA said:
Do you have a Sprint phone ? and can you post a screen shot of your adb / fastboot folder containing the files or at least post your results for dir
open command prompt from your adb / fastboot folder (shift+right click - command prompt here)
type
adb devices
your device SN will be here
type
adb reboot bootloader
you should be in fastboot usb
type
fastboot devices
again your serial no should be here
type dir
you should see the contains of the folder your in
now
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
if error change the twrp name to match the one in the dir command above
Click to expand...
Click to collapse
I seem to have a problem adb detecting the connected phone, I'll unistall and start again and if I can then get back to you later I'd appreciate it very much.
The phone is UK on 02 Android 4.4 HTC Sense version 5.5
tj
tjpearson said:
I seem to have a problem adb detecting the connected phone, I'll unistall and start again and if I can then get back to you later I'd appreciate it very much.
The phone is UK on 02 Android 4.4 HTC Sense version 5.5
tj
Click to expand...
Click to collapse
can you check my guide under faq #2, if that solves it
Well, think I'll give up with rooting my HTC One, I have never had so much trouble routing a divice as this. My bootloader is now unlocked and that's about as far as I get.
My phone seems to have been detected once through adb that then allowed me to run unlock token but everything else just fails.
In one last attempt I've attached image of ADB folder and below is result from command line.
It must be my age because evertybing seems so complex nowadays
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
error: cannot load 'openrecovery-twrp-2.6.3.3-m7.img': No error
C:\Android>
tjpearson said:
Well, think I'll give up with rooting my HTC One, I have never had so much trouble routing a divice as this. My bootloader is now unlocked and that's about as far as I get.
My phone seems to have been detected once through adb that then allowed me to run unlock token but everything else just fails.
In one last attempt I've attached image of ADB folder and below is result from command line.
It must be my age because evertybing seems so complex nowadays
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
error: cannot load 'openrecovery-twrp-2.6.3.3-m7.img': No error
C:\Android>
Click to expand...
Click to collapse
cannot load = MyFileNameIsWrong
and from the screenshot you posted the filename is: openrecovery-twrp-2.6.3.3-m7.img.img <- yes, double extension, next time do a "dir" in command prompt to see your filenames, not in Windows Explorer.
d -darrrrr
nkk71 said:
cannot load = MyFileNameIsWrong
and from the screenshot you posted the filename is: openrecovery-twrp-2.6.3.3-m7.img.img <- yes, double extension, next time do a "dir" in command prompt to see your filenames, not in Windows Explorer.
Click to expand...
Click to collapse
I love you nkk71, I really can't tell you how much I love you but I do !!!!! :victory:
Did what you said and fumbled through flashing twrp and then adding superuser after to the phones root, did recovery again and installed superuser via twrp and bingo, rooted and confirmed.
Been struggling 2 weeks with this and non stop all weekend, my wife wants a divorce but I don't care cos I'M ROOTED !!
Thanks so much for all the help, nice one :good:
tj
tjpearson said:
I love you nkk71, I really can't tell you how much I love you but I do !!!!! :victory:
Did what you said and fumbled through flashing twrp and then adding superuser after to the phones root, did recovery again and installed superuser via twrp and bingo, rooted and confirmed.
Been struggling 2 weeks with this and non stop all weekend, my wife wants a divorce but I don't care cos I'M ROOTED !!
Thanks so much for all the help, nice one :good:
tj
Click to expand...
Click to collapse
Lol
Now that the phone is good, go spend some time with your better half!!!
No guides on xda, on "how to return my marriage to stock"
Put the phone on the charger or something, and spend time with your significant other.
Sent from my HTC One using Tapatalk
One last question
nkk71,
Can I uninstall Superuser now and install SuperSU instead cos I've already purchased that when had the Note rooted or will it cause me more time away from the mrs with issues.
tj
tjpearson said:
nkk71,
Can I uninstall Superuser now and install SuperSU instead cos I've already purchased that when had the Note rooted or will it cause me more time away from the mrs with issues.
tj
Click to expand...
Click to collapse
Shouldn't be a problem, use the flashable zip from the thread: http://forum.xda-developers.com/showthread.php?t=1538053
Yeah , sorted.
Thanks again for all your help.
tj

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)

Categories

Resources