Related
Hi all,
Hope someone can help, I have a desire HD that has some issues.
Long story short the phone was acting up and was flashed with a non official ROM. It was working originally but after about a week it started acting up, with apps force closing, phone crashing altogether etc.
I am trying to get the phone back to a state that Vodafone in Australia will be able to warranty the phone in.
The current situation is that when the phone turns on, it'll load straight to the bootloader/hboot. Recovery mode does not work - it dumps you in to fastboot menu and fails to load.
System restore from boot menu does not work either, and there is no rom at all so USB debugging is a no go, and there appears to be no way to flash the ROM.
Any ideas? Any help would be greatly appreciated.
Thanks
Sent from my GT-P7100 using XDA App
Use adb / fastboot to push a new recovery to the phone (I hope you left USB debugging enabled).
Sent from my Ericsson T39m
Sadly no USB debugging doesn't seem to work. Makes the sound that it connects to the computer and that bootloader states its connected by usb however it doesn't seem to phone is connected. Any other ideas?
Sent from my GT-P7100 using XDA App
CrystalCastle said:
Sadly no USB debugging doesn't seem to work. Makes the sound that it connects to the computer and that bootloader states its connected by usb however it doesn't seem to phone is connected. Any other ideas?
Sent from my GT-P7100 using XDA App
Click to expand...
Click to collapse
ooh i tested it in my DHD and don´t works...how can be possible that don´t works adb parameters, but fastboot commander works perfectly??
maybe we have anything that works badly in our PC´s.. i´m in it...
ei crystal!! has you tested with FASTBOOT COMMANDER? if you download it you can flash a new recovery from this tool... its intuitive...
you only must to download the tool
download the recovery (lastest CWM in the DHD android development forum)
put the file in the paragraph that says "RECOVERY:not file set" and then push FLASH IT"".maybe you enjoy...
remember to put your device into boot loader
CrystalCastle said:
Sadly no USB debugging doesn't seem to work. Makes the sound that it connects to the computer and that bootloader states its connected by usb however it doesn't seem to phone is connected. Any other ideas?
Click to expand...
Click to collapse
How did you check to see if adb shell can see the device?
Run an pb98.img from the bootlaoder
Sent from my Motorola Startac running Atari 2600 software!
Mr_JMM said:
How did you check to see if adb shell can see the device?
Click to expand...
Click to collapse
adb get-state
result:
unknown
Code:
adb devices
But this does depend on you having previously ticked USB Debugging option before you had all these problems (no way to check now without being able to boot the phone).
If this fails you may have to try the previous suggestion of putting a PD98IMG on your sdcard then going into fastboot on the phone.
Mr_JMM said:
But this does depend on you having previously ticked USB Debugging option before you had all these problems (no way to check now without being able to boot the phone).
If this fails you may have to try the previous suggestion of putting a PD98IMG on your sdcard then going into fastboot on the phone.
Click to expand...
Click to collapse
Currently there is no Rom on the Phone. Just put PD98IMG.zip on the SD card which seems to be updating. Does it normally take a while to Update all the Sections?
Can take anything from 5 to 20+ minutes.
Seems to be taking ages to even get past [1]. Is that normal? Hasn't done anything. It says "Updating" yet I'm still yet to see it get past "[1] BOOTLOADER"
Just to confirm...
1. Turn phone off
2. Put PD98IMG file onto ROOT of sd card
3. Use vol- and power button to get to Fastboot
4. Scroll and select Bootloader (HBOOT)
(might automatically do last step when you boot phone)
Phone will show a message to say it is looking for the file then unpack it and install.
Mr_JMM said:
Just to confirm...
1. Turn phone off
2. Put PD98IMG file onto ROOT of sd card
3. Use vol- and power button to get to Fastboot
4. Scroll and select Bootloader (HBOOT)
(might automatically do last step when you boot phone)
Phone will show a message to say it is looking for the file then unpack it and install.
Click to expand...
Click to collapse
Confirmed dude. Doesn't seem to be doing much though. It has been stuck on "updating BOOTLOADER". It has trying to update it for more then 30mins now
It has a big list of 12 things it wants to update however it hasn't moved past the first file "BOOTLOADER" in over 30mins.
Did you confirm the MD5HASH of the file before putting it on the card?
Could you put a link to where you got the file from please?
http://forum.xda-developers.com/showthread.php?t=905003
Thank you.
Are you still connected to the PC? If so disconnect and try again.
Did you confirm the MD5HASH?
Have you got another SD card you can try? If not, reformat the current one and put the PD98IMG file on it again and try again.
The Device fails to even turn on now dude. Thanks anyway man
!!!???!!!
Damn. Do you just get the orange flashing light when you try to turn the phone on?
Take out SD Card and try.
If nothing works the bright side is you can send it to HTC and say "I woke up, turned it on and it's dead". Chances are they'll never be able to tell how it happened.
Many people did this when the Clockwork recovery bug bricked loads of phones.
Sorry but stay positive. Always a sliver lining.
Thank you
thanks for your great guidance to get back to recovery. I followed your tips and made it.
thanks a lot once again.
SERGI.3210 said:
ooh i tested it in my DHD and don´t works...how can be possible that don´t works adb parameters, but fastboot commander works perfectly??
maybe we have anything that works badly in our PC´s.. i´m in it...
ei crystal!! has you tested with FASTBOOT COMMANDER? if you download it you can flash a new recovery from this tool... its intuitive...
you only must to download the tool
download the recovery (lastest CWM in the DHD android development forum)
put the file in the paragraph that says "RECOVERY:not file set" and then push FLASH IT"".maybe you enjoy...
remember to put your device into boot loader
Click to expand...
Click to collapse
Hi to all
I have a big problem. My HTC Desire HD is now "dead". So, everything is working normally, just fine, on JellyTime, but this afternoon everything get broken. Suddenly, after the boot animation is finished, nothing happens, the screen is "black". The phone works, because when I connect USB to the computer sound. I can not get into Recovery (Home + Volume Down), can not do anything. I tried to remove the battery, but it does not help. I tried with adb, but there is "error: device not found". So I installed the drivers, asking me activate USB Debugging on the phone, and I can not access the phone.
Do you have any idea how to access recovery mode and install the new ROM?
Please help!
Thanks in advance.
just turn on your device with press volume down + power to get into the bootloader..then from there you can select recovery
JJeamy said:
just turn on your device with press volume down + power to get into the bootloader..then from there you can select recovery
Click to expand...
Click to collapse
I try, but I can't. :crying:
SkipperRi said:
I try, but I can't. :crying:
Click to expand...
Click to collapse
can you explain more cleared about this..?, did you mean your volume rocker is already broken or what else..?
what is the last you know the state or your phone bootloader..?, unlocked with s-on or already s-off..?
and what about the stock RUU..did you had already tried to flashing it through the pc..?
JJeamy said:
can you explain more cleared about this..?, did you mean your volume rocker is already broken or what else..?
what is the last you know the state or your phone bootloader..?, unlocked with s-on or already s-off..?
and what about the stock RUU..did you had already tried to flashing it through the pc..?
Click to expand...
Click to collapse
I finally managed this problem. I pulled off the battery over the night, and this morning I can booted into the recovery. So, I installed new ROM, all my apps, and now I performed backup to the my PC.
Thanks for help!
Regards.
Again same problem. For few hours everything seems fine, but just now my HTC has "blank" screen... Nothing to do. Again, I can't go to Recovery, nothing... What's going on with this phone?!?!
JJeamy said:
can you explain more cleared about this..?, did you mean your volume rocker is already broken or what else..?
what is the last you know the state or your phone bootloader..?, unlocked with s-on or already s-off..?
and what about the stock RUU..did you had already tried to flashing it through the pc..?
Click to expand...
Click to collapse
How to do this? And, if I do that, will be my phone still rooted after that?
SkipperRi said:
How to do this? And, if I do that, will be my phone still rooted after that?
Click to expand...
Click to collapse
no..you will lost it
what the state of your phone bootloader..?
unlocked or locked or nothing ?
s-on or s-off ?
hboot - ???
n your phone still can't go to bootloader with press volume down + power..?, is that the new rom you've already installed earlier..already by default it had enabled usb debugging under system settings..?
JJeamy said:
no..you will lost it
what the state of your phone bootloader..?
unlocked or locked or nothing ?
s-on or s-off ?
hboot - ???
n your phone still can't go to bootloader with press volume down + power..?, is that the new rom you've already installed earlier..already by default it had enabled usb debugging under system settings..?
Click to expand...
Click to collapse
No, I can't go to bootloader with volume down+power. About state of phone... S-off, that's I know. The ROM is installed earlier, but today I perform full wipe, and then installed ROM again, not backup/recovery, but fresh install. USB debugging is, as far I know, disabled... What should I do?
SkipperRi said:
No, I can't go to bootloader with volume down+power. About state of phone... S-off, that's I know. The ROM is installed earlier, but today I perform full wipe, and then installed ROM again, not backup/recovery, but fresh install. USB debugging is, as far I know, disabled... What should I do?
Click to expand...
Click to collapse
did you already try it adb is connected or not..?, just try first with "adb devices" (while the phone is on booting and had a black screen)
anyway why your phone can't go into bootloader by pressing volume down + power..?, is that already broken with your volume rocker..?
what happen if your pull out the battery first just a few minutes..then put in back again..and try it again pressing volume down+power..
JJeamy said:
did you already try it adb is connected or not..?, just try first with "adb devices" (while the phone is on booting and had a black screen)
anyway why your phone can't go into bootloader by pressing volume down + power..?, is that already broken with your volume rocker..?
what happen if your pull out the battery first just a few minutes..then put in back again..and try it again pressing volume down+power..
Click to expand...
Click to collapse
I don't know why can't go into bootloader with volumeD+power... I pulled battery, but everything is same. Can you please explain to me how can I try with adb?
Thank you so much for help!
SkipperRi said:
I don't know why can't go into bootloader with volumeD+power... I pulled battery, but everything is same. Can you please explain to me how can I try with adb?
Thank you so much for help!
Click to expand...
Click to collapse
i assume that you already had SDK/ADT or adb.exe and fastboot.exe on your PC.. if not just downloading from here..
and already had installing the latest HTC driver on your PC..
firstly your let the phone is boot like normal..then after you see the black screen..try connecting it to your pc..
then open your SDK folder (place of adb and fastboot.exe) then run cmd and source to your adb folder.. example : if your adb folder is in "C:/android tools/" then you must change source to that folder with typing "cd C:\android tools", now you ready to used it..don't closed it..just let it open
while your phone already booting n had black screen..then already connecting it to usb on your pc..then firstly try typing "adb devices" to check that's the phone is already connected with adb..
if your phone is detected..then you had prompt after that is your phone serial number that on list of attached devices
if success connected..then you can typing "adb reboot-bootloader" or "adb reboot recovery" (all command w/o quote)
JJeamy said:
i assume that you already had SDK/ADT or adb.exe and fastboot.exe on your PC..
firstly your let the phone is boot like normal..then after you see the black screen..try connecting it to your pc..
then open your SDK folder (place of adb and fastboot.exe) then run cmd and source to your adb folder.. example : if your adb folder is in "C:/android tools/" then you must change source to that folder with typing "cd C:\android tools", now you ready to used it..don't closed it..just let it open
while your phone already booting n had black screen..then already connecting it to usb on your pc..then firstly try typing "adb devices" to check that's the phone is already connected with adb..
if your phone is detected..then you had prompt after that is your phone serial number that on list of attached devices
if success connected..then you can typing "adb reboot-bootloader" or "adb reboot recovery" (all command w/o quote)
Click to expand...
Click to collapse
Thank you so much! I'll go and try right now and let you know what's going on.
JJeamy said:
while your phone already booting n had black screen..then already connecting it to usb on your pc..then firstly try typing "adb devices" to check that's the phone is already connected with adb..
(all command w/o quote)
Click to expand...
Click to collapse
Nothing. Here is what I get in CMD:
Code:
C:\adbfastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
What now?!
SkipperRi said:
Nothing. Here is what I get in CMD:
Code:
C:\adbfastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
What now?!
Click to expand...
Click to collapse
wel on my windows 8 i also get that blank line whre the serial number from the device should be but in my case its connected 'cause i can push files and to adb commands with it.
try to do adb reboot-bootloader and see if if does that
lexuz said:
wel on my windows 8 i also get that blank line whre the serial number from the device should be but in my case its connected 'cause i can push files and to adb commands with it.
try to do adb reboot-bootloader and see if if does that
Click to expand...
Click to collapse
Hm, I'm also on Windows 8, when I try command: adb reboot recovery then I get error: device not found.
But, when I connect/disconnect phone via USB there is a sound that detect connection...
SkipperRi said:
Hm, I'm also on Windows 8, when I try command: adb reboot recovery then I get error: device not found.
But, when I connect/disconnect phone via USB there is a sound that detect connection...
Click to expand...
Click to collapse
sorry can't help you more its up to the gurus here, try the thread ace think tank here on the forum
SkipperRi said:
Nothing. Here is what I get in CMD:
Code:
C:\adbfastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
What now?!
Click to expand...
Click to collapse
you sure that your pc already had latest HTC driver right and support with your OS..?
if so..maybe that's the usb debugging is not already active on your phone indeed..
because what i know is that just had two option to access your phone again:
1. with your volume down+power to access bootloader of your phone..and you can do it everything from there..
2. with adb command on android home of your phone..
while both option that is doesn't work..i'm sorry..i don't know more how the way to access your bootloader again beside the two way above..
anyway maybe you can try it again like the first way you success go into bootloader with pull out the battery over few hours like before..
and when you've already success flashing new rom again..don't forget firstly to enable it usb debugging from system settings..and connect as charge mode only..
and don't forget to disable fast boot mode too from system settings if you using sense rom
lexuz said:
sorry can't help you more its up to the gurus here, try the thread ace think tank here on the forum
Click to expand...
Click to collapse
Thank you anyway...
JJeamy said:
you sure that your pc already had latest HTC driver right and support with your OS..?
if so..maybe that's the usb debugging is not already active on your phone indeed..
because what i know is that just had two option to access your phone again:
1. with your volume down+power to access bootloader of your phone..and you can do it everything from there..
2. with adb command on android home of your phone..
while both option that is doesn't work..i'm sorry..i don't know more how the way to access your bootloader again beside the two way above..
anyway maybe you can try it again like the first way you success go into bootloader with pull out the battery over few hours like before..
and when you've already success flashing new rom again..don't forget firstly to enable it usb debugging from system settings..and connect as charge mode only..
and don't forget to disable fast boot mode too from system settings if you using sense rom
Click to expand...
Click to collapse
Yes, I have valid drivers, because before this disaster it was possible to connect phone with PC without any problems.
Have you any idea why the phone go "dead" after few hours working just perfect? Hardware or ROM related issue, what do you think?
I pulled battery out just now, for tommorow morning I giving up, maybe I'll be lucky and again I can with volume down + power booting into Recovery Mode.
Thank you, my friend!
P.S. Do you have any suggestion for some stable and good ROM?
SkipperRi said:
Thank you anyway...
Yes, I have valid drivers, because before this disaster it was possible to connect phone with PC without any problems.
Have you any idea why the phone go "dead" after few hours working just perfect? Hardware or ROM related issue, what do you think?
I pulled battery out just now, for tommorow morning I giving up, maybe I'll be lucky and again I can with volume down + power booting into Recovery Mode.
Thank you, my friend!
P.S. Do you have any suggestion for some stable and good ROM?
Click to expand...
Click to collapse
i'm not sure about that..until now..what i see is still software related..but i don't know what software exactly had the problem is..
can be from the recovery that you had installed the rom..or else..
to make sure what exactly is.. you must return the phone to the stock..stock bootloader, stock rom and stock recovery too..all back to the stock..with flashing stock RUU while your phone back in normal condition..
you know the forum rule is doesn't give any permission to all member for compare the rom..
Now my phone thinks it's a D800. I was able to get into download mode and tried using LG Flashtool. I used the 850 dll and .tot but got an error.
Download Fail!
Device model is different.
Check phone or dll.
I read something about using a modified .dll but cant find more info on it. Feeling pretty stupid for possibly ruining a $400 device with such an idiotic mistake. Any advice you guys can give me is truly appreciated.
Thanks Guys
Muuust said:
Now my phone thinks it's a D800. I was able to get into download mode and tried using LG Flashtool. I used the 850 dll and .tot but got an error.
Download Fail!
Device model is different.
Check phone or dll.
I read something about using a modified .dll but cant find more info on it. Feeling pretty stupid for possibly ruining a $400 device with such an idiotic mistake. Any advice you guys can give me is truly appreciated.
Thanks Guys
Click to expand...
Click to collapse
I had a similar issue but it was my d800 lg g2, i flashed a diferent rom by accident that wasn't made for the phone. I'm assuming you tried twrp and it didn't let you enter it?
theinspector said:
I had a similar issue but it was my d800 lg g2, i flashed a diferent rom by accident that wasn't made for the phone. I'm assuming you tried twrp and it didn't let you enter it?
Click to expand...
Click to collapse
Sorry if this is an absolutely stupid question, but you can get into twrp from download mode? I had an app that rebooted into twrp, that's the way I did it. Sorry for the noob answers, I'm completely new to rooting.
Muuust said:
Sorry if this is an absolutely stupid question, but you can get into twrp from download mode? I had an app that rebooted into twrp, that's the way I did it. Sorry for the noob answers, I'm completely new to rooting.
Click to expand...
Click to collapse
If you pull the battery so the phone is full powered off, press and hold the volume down button, and the power button down at the same time until you see the LG logo, then release just the power button, keep holding the volume down button, and then quickly press power and hold it again, you will be brought to a factory reset page, that tells you it will wipe all your data, don't worry about it, nothing will wipe, scroll down with the volume key to the yes button, hit power to accept it, it will ask you to confirm it, hit power twice and it should boot into twrp. If it boots into twrp, like it should, then you can either sideload a rom, flash an existing one you have on the phone, or hopefully you have made a twrp backup of your previous rom to restore. If instead of going into twrp, it puts you back into fastboot or download mode after agreeing to the factory reset, then there is a few more things to try.
theinspector said:
If you pull the battery so the phone is full powered off, press and hold the volume down button, and the power button down at the same time until you see the LG logo, then release just the power button, keep holding the volume down button, and then quickly press power and hold it again, you will be brought to a factory reset page, that tells you it will wipe all your data, don't worry about it, nothing will wipe, scroll down with the volume key to the yes button, hit power to accept it, it will ask you to confirm it, hit power twice and it should boot into twrp.
Click to expand...
Click to collapse
ok ya, I tried that earlier. It takes me back into download mode after I confirm yes with the volume buttons.
Muuust said:
ok ya, I tried that earlier. It takes me back into download mode after I confirm yes with the volume buttons.
Click to expand...
Click to collapse
Have you tried using the fastboot boot command from your computer, to boot into twrp?
theinspector said:
Have you tried using the fastboot boot command from your computer, to boot into twrp?
Click to expand...
Click to collapse
My G3 shows up in Device Manager under Portable Devices for about 40 seconds, then it gets a yellow triangle and says "This device cannot start. (code 10)"
It doesn't show up in "Computer" where all the HDD and other devices show up. So I can't access it.
theinspector said:
Have you tried using the fastboot boot command from your computer, to boot into twrp?
Click to expand...
Click to collapse
Did a little searching and I'm trying to install ADB right now. That's what I need right?
theinspector said:
Have you tried using the fastboot boot command from your computer, to boot into twrp?
Click to expand...
Click to collapse
In cmd I entered adb devices and got back "List of devices attached" but my phone doesn't show up here either.
Muuust said:
In cmd I entered adb devices and got back "List of devices attached" but my phone doesn't show up here either.
Click to expand...
Click to collapse
You'll want to get the fastboot drivers, not just the adb drivers. Under device manager after you get the fastboot drivers installed, makes sure the Windows device manager shows your device, and replace the default installed driver for it with the new fastboot one you installed, open a command window with cmd, and search for "fastboot devices" and it should show a long number come back under that list now.
Also, if your computer shows the device for a short period before it disappears, you may have to go into your computers settings to disable auto-driver install, then you can just manually choose the fastboot drivers.
theinspector said:
You'll want to get the fastboot drivers, not just the adb drivers. Under device manager after you get the fastboot drivers installed, makes sure the Windows device manager shows your device, and replace the default installed driver for it with the new fastboot one you installed, open a command window with cmd, and search for "fastboot devices" and it should show a long number come back under that list now.
Also, if your computer shows the device for a short period before it disappears, you may have to go into your computers settings to disable auto-driver install, then you can just manually choose the fastboot drivers.
Click to expand...
Click to collapse
I gotta head to work soon so it'll probably be a bit before I get back to you. But I sincerely want thank you for taking time to help me out. Truly appreciate it.
Muuust said:
I gotta head to work soon so it'll probably be a bit before I get back to you. But I sincerely want thank you for taking time to help me out. Truly appreciate it.
Click to expand...
Click to collapse
Yeah it is no problem, i remember having this same issue and couldn't find a whole lot of information on the issue, so I'm glad to help.
fastboot
I was stuck on fastboot yesterday, used fastboot boot laf.img to go back to download mode and then used lgflashtool to flash a new rom.
unspokenname said:
I was stuck on fastboot yesterday, used fastboot boot laf.img to go back to download mode and then used lgflashtool to flash a new rom.
Click to expand...
Click to collapse
I'm stuck in download mode now. And I cant use the LGFlashtool because my g3 comes up as a G2 in Flashtool. So when I choose the D850 dll and tot, I get an error saying it's the wrong model.
Muuust said:
I'm stuck in download mode now. And I cant use the LGFlashtool because my g3 comes up as a G2 in Flashtool. So when I choose the D850 dll and tot, I get an error saying it's the wrong model.
Click to expand...
Click to collapse
For me, flashtool is incredibly finicky and it takes me many different tries to make it work properly, i would try downloading the latest twrp for your G3, and extract from the .zip file the recovery.img and then try to fastboot boot that recovery to your device like i have previously explained. If that does not work for you, and flashtool does not then you can use fastboot flash commands and flash each of the partitions of your phones stock rom.
theinspector said:
You'll want to get the fastboot drivers, not just the adb drivers. Under device manager after you get the fastboot drivers installed, makes sure the Windows device manager shows your device, and replace the default installed driver for it with the new fastboot one you installed, open a command window with cmd, and search for "fastboot devices" and it should show a long number come back under that list now.
Also, if your computer shows the device for a short period before it disappears, you may have to go into your computers settings to disable auto-driver install, then you can just manually choose the fastboot drivers.
Click to expand...
Click to collapse
After some searching it looks like you can't disable auto driver install in windows 7 Premium. When I uninstalled the driver and plugged the phone back in, I get "Device driver was not successfully installed" In that window, I choose "change settings" and choose "Never install driver software from windows update", but it does anyway. When I go to update driver--> Browse my computer for driver software-->I choose my folder with the fastboot drivers, I get "The best diver software for your device is already installed". Now my phone comes up as LGE Android Net MTP Device, it doesn't show as G3 anymore. Also when I enter fastboot devices in cmd I get 'fastboot' is not recognized as an internal or external command, operable program or batch file. No matter what i do, my phone goes to the Firmware Update screen with the USB symbol on it. IN the small box below the progress bar, it reads: User 50.0 AS0.0 B40 UHS
S U LG-800 04.4.2 Hrev_10
CloudyG2 2.2
I don't know if this is helpful at all.
Pm me, also it would be helpful if to have team viewer so that I can help you.
Sent from my LG-D800 using XDA Free mobile app
Watch was working great for a month, until this evening. Went to charge it, kept getting the white "Sorry, Android Wear has stopped" message. Pressed and held side button (while on charging dock) to reboot. Now it won't get past spinning color screen (After the Huawei brand screen). Is there a way to factory reset it while booting?
jsbalrog said:
Watch was working great for a month, until this evening. Went to charge it, kept getting the white "Sorry, Android Wear has stopped" message. Pressed and held side button (while on charging dock) to reboot. Now it won't get past spinning color screen (After the Huawei brand screen). Is there a way to factory reset it while booting?
Click to expand...
Click to collapse
If you have an adb/fastboot set up, boot into fastboot:
Press and hold the side button until it reboots. After the reboot, keep holding the side button until you feel the first vibration. Then quickly release and press it again. You will go immediately into fastboot mode.
You can try:
fastboot format userdata
fastboot format cache
fastboot reboot
This should be the same thing as doing a factory reset. This is based on the assumption that the watch acts like a Nexus device with fastboot commands.
brizey said:
If you have an adb/fastboot set up, boot into fastboot:
Press and hold the side button until it reboots. After the reboot, keep holding the side button until you feel the first vibration. Then quickly release and press it again. You will go immediately into fastboot mode.
You can try:
fastboot format userdata
fastboot format cache
fastboot reboot
This should be the same thing as doing a factory reset. This is based on the assumption that the watch acts like a Nexus device with fastboot commands.
Click to expand...
Click to collapse
Thanks brizey. Tried this, seemed to successfully reset. However, on reboot, still same problem. I wonder if I could re-sideload an OTA? Don't know if one exists for the Huawei watch though...
***** UPDATE *****:
This HowTo worked for me (the revised instructions): http://forum.xda-developers.com/huawei-watch/development/guide-return-to-stock-huawei-watch-t3219596
Thanks All!
jsbalrog said:
Thanks brizey. Tried this, seemed to successfully reset. However, on reboot, still same problem. I wonder if I could re-sideload an OTA? Don't know if one exists for the Huawei watch though...
***** UPDATE *****:
This HowTo worked for me (the revised instructions): http://forum.xda-developers.com/huawei-watch/development/guide-return-to-stock-huawei-watch-t3219596
Thanks All!
Click to expand...
Click to collapse
Great. Lol, I actually assumed you had already tried that and was just having reset issues. Glad to hear it worked out!
brizey said:
Great. Lol, I actually assumed you had already tried that and was just having reset issues. Glad to hear it worked out!
Click to expand...
Click to collapse
Hi i have the same problem this guy had which is my huawei watch stuck with the 4 color dots spinning but nothing else i noticed the link he said worked for him but this is my first android experience and have no clue how to recover the watch back to factory settings. is there anyway you can show me what to do step by step. I apologize if im bugging but seeing my watch just sitting there stuck upsets me. i downloaded the stock system.img recovery.img and boot.img provided here at these forums but have no clue how to flash them. i am on windows 10 and when i connect the watch to my pc i can hear that its recognized by my pc. i am able to get into the fastboot menu.
Thanks in advance
MadizM1 said:
Hi i have the same problem this guy had which is my huawei watch stuck with the 4 color dots spinning but nothing else i noticed the link he said worked for him but this is my first android experience and have no clue how to recover the watch back to factory settings. is there anyway you can show me what to do step by step. I apologize if im bugging but seeing my watch just sitting there stuck upsets me. i downloaded the stock system.img recovery.img and boot.img provided here at these forums but have no clue how to flash them. i am on windows 10 and when i connect the watch to my pc i can hear that its recognized by my pc. i am able to get into the fastboot menu.
Thanks in advance
Click to expand...
Click to collapse
Open up file explorer and go to the directory with the image files.
In the Windows start menu, go to Windows System, then right click on Command Prompt and choose run as administrator. Click though the UAC prompt.
Attach your phone via usb to the PC. Most folks recommend using a motherboard USB port rather than a front port or daughter board port.
It sound like your drivers are OK since it can recognize the phone.
Reboot to fastboot. (Turn the watch off, then turn it on, but continue to hold the button. After the first vibration, quickly release then press the button again.)
Use the cd command in the command window to change to the directory where your images are.
ASSUMING YOU HAVE FASTBOOT EXECUTABLE INSTALLED AND IN YOUR PATH VARIABLE:
Type fastboot devices. If you get a device listed you are good to go.
Execute the revised steps in skin1980's thread to flash the images. If you are in the directory where the images are stored, you can just cut and paste skin1980's commands into the command window.
If you need to install fastboot, search XDA. There are threads with minimal fastboot/adb installs. I have not used it, but THIS thread looks pretty good.
I forget my password of watch , how can open it ?
Charge watch, Turn it off and wait
I have the exact same issue. Tried previous things that appear in this post and no luck. But try this. Works for me! :
- Wait until the watch is discharge
- Connect the watch to charge it (the watch will boot up and will appear the spinning color issue) if you touch the watch several minutes later it will be hot.
- Wait several minutes until the watch have 50% or more of charge.
- Now boot up into Fastboot
Press and hold the side button until it reboots. After the reboot, keep holding the side button until you feel the first vibration. Then quickly release and press it again.
You will go immediately into fastboot mode.
-format userdata,
format cache
reboot
-Boot up in fastboot mode again and use the turn off shut down option.
- Wait several minutes until the watch have its normal temperature
-Turn on the watch and just wait until boot up normally.
In my reasoning is to try to make a fresh turn on, boot up with enough power to do it in a good temperature.
I have a Huawei watch running Android Wear Marshmallow
I hope these steps can resolve your issue.
Jsbalrog ; how did you manage?
It has been quite a while not so many is experiencing the sama issue I guess.
Jsbalrog you are the only one who has solved the boot stuck problem of Huawei Watch. I can not get almost any help from the Official Huawei Service. Could you please let us know a little more detail how you have managed?
Thanks...
Update: After so many days I managed to flash... My watch is working again; still no news from Huawei!!!
For newbies like I am, you have to know is you don't need to enable anything before you are stuck to google logos.
I just downloaded "adb-setup-1.4.3" and "Minimal ADB and Fastboot". Whenever the windows didn't recognize the watch I ran adb-setup which at the end asks for installing drivers and when I disconnect and connect the device, it worked.
After getting connected check if the watch is getting fastboot command by c:\fastboot devices. If you can see any letters and fastboot at the right you're ok to go.
You need to c:\Fastboot Oem Unlock which unlocks the watch and you're out of warranty. Just accept it.
Then follow the steps of skin1980 (thanks it was really great)) http://forum.xda-developers.com/huawei-watch/general/guide-return-to-stock-huawei-watch-t3219596
If you need "twrp" not written; just "swipe right" and follow the instructions of skin1980.
Boot Stuck Problem is over.
The watch is getting the updates right now but I guess I'll learn more and get to stock by the experts' help...
Thanks to you all...
hi
i managed to get mine working as well ! (Thanks to abhanli, pkt_lnt and skin180)
connect watch to pc via usb charger
make sure you are in fastboot menu on your watch (holding the power button till switches off and the pressing again after vibrates)
most important thing next is to press shift and right click anywhere in the adb folder on your computer, and then run command prompt from there, otherwise adb will not load up and you will think that you have just run a dodgy script !
unlock your bootloader (typing "Fastboot Oem Unlock" in the command prompt in adb folder)
then you can use steps of skin180 (link above)
OR
https://developer.android.com/wear/preview/downloads.html
scroll down to huawei watch and choose second download option (non preview image for after testing) (thanks pkt_lnt)
extract into your adb folder (located in c:\)
then using the command prompt in adb folder, navigate to that extracted folder (using dos commands)
then if you are on windows, type "flash-all.bat"
hey presto - will work !
when it reboots, you may think "darn it still has spinning dots !" but if you wait about 5-10 mins it progresses past that stage and comes up with welcome screen !
My watch is working again !
HUAWEI customer services are a pile of POO. Their repair centre in UK is waste of time. They never answer the phone and never reply to messages.
If the Huawei watch wasnt so beautiful, i'd never bother with them !
Good luck and thanks all.
I have this issue. Can someone write a noob version of the above solution?
I can get to the "fast boot" menu on watch but how do I right click an adb folder on my computer, my watch is in no way connected to my computer. Any easier way?
Sent from my Nexus 6P using XDA-Developers mobile app
AdamUK said:
I have this issue. Can someone write a noob version of the above solution?
I can get to the "fast boot" menu on watch but how do I right click an adb folder on my computer, my watch is in no way connected to my computer. Any easier way?
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm in the same position as AdamUK, my Huawei kept crashing and then simply stopped booting past the spinning colors and I'm not following the instructions in this thread.
your watch needs to be connected via usb charger to computer
right click using your mouse
follow the instructions ive wrote - im a noob as well
Hello Everyone,
I Have A Strange Problem When I Press Power+Down Button Then Device Goes To Bootloader/Fastboot And Mi Bunny Appears, But After 3-5 Seconds Mobile Device Automatically Switch Off Without Connecting The Cable Or Doing Anything.
Note That, I Have A Latest Build V11.0.9.0.QDLMIXM Installed Without Rooting And Device Working Properly. Since I Just Want To Root The Device And Bootloader Is Unlocked. The Problem Is That Device Doesn't Stay On Bootloader/Fastboot Mode.
Thanks In Advance !!!
Thanks,
MUHAMMAD Asif Qasim
Can you get fastboot to see it in this brief window? I'm wondering if it will stay if it sees fastboot but maybe reboots because it doesn't? (Or because some other app on your PC is confusing it?)
a1291762 said:
Can you get fastboot to see it in this brief window? I'm wondering if it will stay if it sees fastboot but maybe reboots because it doesn't? (Or because some other app on your PC is confusing it?)
Click to expand...
Click to collapse
Thankyou For Prompt Response.
I Couldn't Get Your Point. The Problem Is That Device Doesn't Stay On Bootloader/Fastboot Mode Even I Connect The Cable Or Not. Its Automatically Switch Off With In 3-5 Seconds.
In Addition To That, I Can Use ADB Commands & Shows My Mobile Connectivity When I Use.
Thanks,
MUHAMMAD Asif Qasim
aasiaasi said:
I Couldn't Get Your Point. The Problem Is That Device Doesn't Stay On Bootloader/Fastboot Mode Even I Connect The Cable Or Not. Its Automatically Switch Off With In 3-5 Seconds.
Click to expand...
Click to collapse
I run this on my PC and it waits for a device.
$ fastboot getvar current-slot
< waiting for any device >
3-5 seconds should be enough time to connect your device and see if fastboot can talk to it (and if that stops it from rebooting).
If it happens when there is no cable plugged in... that's a bit more concerning. Does it also happen if you get to fastboot by typing adb reboot bootloader (from a normally-booted system)?
a1291762 said:
I run this on my PC and it waits for a device.
$ fastboot getvar current-slot
< waiting for any device >
3-5 seconds should be enough time to connect your device and see if fastboot can talk to it (and if that stops it from rebooting).
If it happens when there is no cable plugged in... that's a bit more concerning. Does it also happen if you get to fastboot by typing adb reboot bootloader (from a normally-booted system)?
Click to expand...
Click to collapse
Thank You Dear. Yes I Can Use The Command On ADB When Mobile Is Switched On Here Is The Example Snapshot.
The Problem Is That When I Boot To Bootloader It Doesn't Stay On Bootloader And Shutdowns Automatically With In 3-5 Seconds. As You Suggested Me To Check The Command When Mobile Is On Bootloader Mode The Shell Shows "waiting for any device". Ahd Restarts Automatically.
aasiaasi said:
As You Suggested Me To Check The Command When Mobile Is On Bootloader Mode The Shell Shows "waiting for any device". Ahd Restarts Automatically.
Click to expand...
Click to collapse
I don't know exactly what the bootloader does while in fastboot mode, but I'm going to guess it draws the rabbit and then gets ready to talk to the PC. And something fails and it dies.
If it's working normally, that's something... But it's going to stop you from unlocking the bootloader.
I have no idea how to fix. Maybe EDL with the test points? There are 2 aboot partitions (apparently hold fastboot).
# ls -l aboot*
lrwxrwxrwx 1 root root 21 1971-09-16 02:23 aboot_a -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1971-09-16 02:23 aboot_b -> /dev/block/mmcblk0p32
I think the fastboot mode will exit automatically if it doesn't receive any command from PC. It happened to me before and about the <waiting for any device> when you did a command probably related to it. Check if the driver are properly installed because it happened to me on Windows 10 but not on Windows 8.1.
Mewwo2 said:
I think the fastboot mode will exit automatically if it doesn't receive any command from PC. It happened to me before and about the <waiting for any device> when you did a command probably related to it. Check if the driver are properly installed because it happened to me on Windows 10 but not on Windows 8.1.
Click to expand...
Click to collapse
Thankyou Mewwo2,
Could You Please Check Your Device ? Without Connecting The Cable , That Your Device Automatically Switched Off In Few Seconds Or Not. Please Let Me Know So I Can Figure Out Or Take A Clue For Fixation.
Secondly I Have Windows 8 And Drivers Are Properly Installed. If The Drivers Have Issue The Adb Command Doesn't Work And Doesn't Shows My Mobile (Note That I am Taking About When Mobile Isn't on Bootloader Mode)
Thanks In Advance...
Can you type another adb command like 'fastboot oem device-info' and see the output.
it's not a problem.
Mi a2 lite turns off automatically from fastboot when it doesnt detect any fastboot signal.
You can go to device manager and then see if mi a2 lite gets recognized as a device, now go to cmd and type fastboot devices and boot to fastboot again, now it shouldn't power off again.
minicm94123 said:
it's not a problem.
Mi a2 lite turns off automatically from fastboot when it doesnt detect any fastboot signal.
You can go to device manager and then see if mi a2 lite gets recognized as a device, now go to cmd and type fastboot devices and boot to fastboot again, now it shouldn't power off again.
Click to expand...
Click to collapse
Thankyou For Your Support. I Will Check & Respond Accordingly.