Hello all,
My unlocked (for a long time) Nexus 7 stopped responding so I turned it off and on and now it won't go beyond the google screen.I have tried connect it to my computer but windows doesn't see it as a device (usually does) so I can't run any adb commands.
I pressed power + volume down until the menu appears but nothing I select helps. I have left it for hours after selecting 'recovery mode' from that menu and still no joy. I have left the battery completely empty then changed it up again and it still won't get beyond that Google screen.
Does anyone please know anything else I can try?
standardman said:
Hello all,
My unlocked (for a long time) Nexus 7 stopped responding so I turned it off and on and now it won't go beyond the google screen.I have tried connect it to my computer but windows doesn't see it as a device (usually does) so I can't run any adb commands.
I pressed power + volume down until the menu appears but nothing I select helps. I have left it for hours after selecting 'recovery mode' from that menu and still no joy. I have left the battery completely empty then changed it up again and it still won't get beyond that Google screen.
Does anyone please know anything else I can try?
Click to expand...
Click to collapse
Does your computer recognize your N7 when it's booted into the bootloader (aka fastboot mode)?
charesa39 said:
Does your computer recognize your N7 when it's booted into the bootloader (aka fastboot mode)?
Click to expand...
Click to collapse
That's the menu with the start/recovery/power off options isn't it? It doesn't detect it at that point either, I'm afraid.
standardman said:
That's the menu with the start/recovery/power off options isn't it? It doesn't detect it at that point either, I'm afraid.
Click to expand...
Click to collapse
Well, if you've already unlocked it in the past, you should still have the drivers on your computer. You need to select the correct drivers, and it should detect it. Once you've done that, you can confirm this by using the "fastboot devices" cmd to make sure your device shows up in fastboot mode.
charesa39 said:
Well, if you've already unlocked it in the past, you should still have the drivers on your computer. You need to select the correct drivers, and it should detect it. Once you've done that, you can confirm this by using the "fastboot devices" cmd to make sure your device shows up in fastboot mode.
Click to expand...
Click to collapse
Thanks for the reply.
Sorry I'm not exactly sure how to do that. Will they just be files on my PC, what should they be called?
If it helps, I used the nexus root toolkit to root mine.
standardman said:
Thanks for the reply.
Sorry I'm not exactly sure how to do that. Will they just be files on my PC, what should they be called?
If it helps, I used the nexus root toolkit to root mine.
Click to expand...
Click to collapse
Give this a try: http://forum.xda-developers.com/showthread.php?t=2588979. Once you have the correct drivers installed, it should detect it in fastboot mode.
charesa39 said:
Give this a try: http://forum.xda-developers.com/showthread.php?t=2588979. Once you have the correct drivers installed, it should detect it in fastboot mode.
Click to expand...
Click to collapse
Thanks again!
Ok, so it didn't detect so I rebooted the device a few times while connected to USB and it appeared, did some windows instally drivers stuff then the DEVICE booted. Unfortunately the touchscreen wasn't working (happens fairly often) so I rebooted and now it won't get beyond the google screen again and windows isn't detecting it again.
So close!
standardman said:
Thanks again!
Ok, so it didn't detect so I rebooted the device a few times while connected to USB and it appeared, did some windows instally drivers stuff then the DEVICE booted. Unfortunately the touchscreen wasn't working (happens fairly often) so I rebooted and now it won't get beyond the google screen again and windows isn't detecting it again.
So close!
Click to expand...
Click to collapse
Well, if it detected it, then you should have the correct drivers. Boot into the bootloader by holding Power + Volume Down. Plug in your device. Open a command window in the folder where your adb/fastboot was installed. The easiest way to do that is to navigate to that folder (default location should be something like C:/android-sdk/platform-tools) and hold SHIFT on your keyboard and right click. The drop down menu should have an option to open a command window in that location. Type "fastboot devices" (obviously, without the quotation marks), and you should see the serial number for you device pop up. That's when you know you can then use fastboot commands successfully.
charesa39 said:
Well, if it detected it, then you should have the correct drivers. Boot into the bootloader by holding Power + Volume Down. Plug in your device. Open a command window in the folder where your adb/fastboot was installed. The easiest way to do that is to navigate to that folder (default location should be something like C:/android-sdk/platform-tools) and hold SHIFT on your keyboard and right click. The drop down menu should have an option to open a command window in that location. Type "fastboot devices" (obviously, without the quotation marks), and you should see the serial number for you device pop up. That's when you know you can then use fastboot commands successfully.
Click to expand...
Click to collapse
Great, that worked, it output my serial number. Now we know we can use those commands, what's next please?
standardman said:
Great, that worked, it output my serial number. Now we know we can use those commands, what's next please?
Click to expand...
Click to collapse
Good. The easiest thing to do to try to recover without wiping your data would be to format the cache. Sometimes, your issue can be caused by a corrupted cache partition. So type "fastboot erase cache" and hit enter. Let it do it's thing. Then, type "fastboot format cache" and hit enter. Let it do it's thing again. Then, on your Nexus 7, select "reboot" and see if it boots into the Android OS.
charesa39 said:
Good. The easiest thing to do to try to recover without wiping your data would be to format the cache. Sometimes, your issue can be caused by a corrupted cache partition. So type "fastboot erase cache" and hit enter. Let it do it's thing. Then, type "fastboot format cache" and hit enter. Let it do it's thing again. Then, on your Nexus 7, select "reboot" and see if it boots into the Android OS.
Click to expand...
Click to collapse
Hooray! This is looking waay more positive! I can nowe boot my device but still have that touchscreen issue (I tend to do this stuff until it sort itself out).
Thank you so much for all your help. Just in case I can't get the damn touchscreen working. How would I use command line to factory reset this thing please?
standardman said:
Hooray! This is looking waay more positive! I can nowe boot my device but still have that touchscreen issue (I tend to do this stuff until it sort itself out).
Thank you so much for all your help. Just in case I can't get the damn touchscreen working. How would I use command line to factory reset this thing please?
Click to expand...
Click to collapse
Great! Well, except for those touch issues... To flash the factory image, check out the OP in this thread over in the Nexus 5 forums: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701. Although it's for the N5, the procedure is pretty much exactly the same for the N7 (2013) (and Nexus 10 for that matter). Just make sure you have the correct factory image for your device. Basically, after you download the factory image, you have to extract the folder inside the zip. Then, open the command window there, and type "flash-all.bat" (assuming you're using a Windows PC). IMPORTANT: After everything is done running, boot back into the bootloader and boot into recovery. Select "wipe data/factory data reset." After that's done, just reboot and you're good to go.
charesa39 said:
Great! Well, except for those touch issues... To flash the factory image, check out the OP in this thread over in the Nexus 5 forums: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701. Although it's for the N5, the procedure is pretty much exactly the same for the N7 (2013) (and Nexus 10 for that matter). Just make sure you have the correct factory image for your device. Basically, after you download the factory image, you have to extract the folder inside the zip. Then, open the command window there, and type "flash-all.bat" (assuming you're using a Windows PC). IMPORTANT: After everything is done running, boot back into the bootloader and boot into recovery. Select "wipe data/factory data reset." After that's done, just reboot and you're good to go.
Click to expand...
Click to collapse
Thank you once. Honestly, I feel like I found a saint on the internet :highfive:
standardman said:
Thank you once. Honestly, I feel like I found a saint on the internet :highfive:
Click to expand...
Click to collapse
Haha! I don't know about all that. Just glad I could help. :highfive: Hope it all works our for you. :good:
Related
I've been working on this since 10am and now my phone is stuck on the Google boot up screen, there is a small 'unlocked' lock icon below it.
My nandroid backup has disappeared and I have nothing to recover. I did a Titanium Backup before I started all this but now that is gone too. I've tried going back to stock, but its gone too. Not sure what role no USB debugging mode is playing in all this. I have scoured these forums and I just keep going in circles, doing the same steps and getting the same result. Hoping this is a soft brick and there's a solution.
I still have Viscious-TORO-JelleyBean-V3.signed.zip , tuna-jb-kernel-019b6.zip , and CWM-SuperSU-v0.89.zip still available on my device but nothing happens when I 'install zip from sd card
Any help is appreciated.
I would suggest flashing the stock images in fastboot to get your phone back to a working state.
Follow efrant's guide. It will walk you through the process if you aren't familiar.
El Daddy said:
I would suggest flashing the stock images in fastboot to get your phone back to a working state.
Follow efrant's guide. It will walk you through the process if you aren't familiar.
Click to expand...
Click to collapse
I appreciate it, I will get to work on that now and report back.
TJDonnell said:
I've been working on this since 10am and now my phone is stuck on the Google boot up screen, there is a small 'unlocked' lock icon below it.
My nandroid backup has disappeared and I have nothing to recover. I did a Titanium Backup before I started all this but now that is gone too. I've tried going back to stock, but its gone too. Not sure what role no USB debugging mode is playing in all this. I have scoured these forums and I just keep going in circles, doing the same steps and getting the same result. Hoping this is a soft brick and there's a solution.
I still have Viscious-TORO-JelleyBean-V3.signed.zip , tuna-jb-kernel-019b6.zip , and CWM-SuperSU-v0.89.zip still available on my device but nothing happens when I 'install zip from sd card
Any help is appreciated.
Click to expand...
Click to collapse
What did you do prior to having this issue occur?
EDIT: Well, those replies moved in quick I agree with the above suggestion.
OK, I still cannot do much b/c USB debugging is NOT enabled. I cannot get to my settings to enable it. Any advice?
TJDonnell said:
OK, I still cannot do much b/c USB debugging is NOT enabled. I cannot get to my settings to enable it. Any advice?
Click to expand...
Click to collapse
The linked guide does not require USB debugging. You are flashing stock images from the bootloader. USB debugging is for using ADB once you've loaded into Android proper.
Having issues with the cmd prompt. My device is plugged in but these instructions are beyond my understanding. the cmd prompt fastboot does not make sense to me and I keep getting an error.
I really, really need help. My phone is vital to my business and not having it tomorrow is not an option. I'm now 12 hours into this attempted flash of a ROM and I've got nothing but a paperweight.
Can anyone give me a hand understanding this process?
First, have you booted into the bootloader? (hold down volume up and down + power)What error does it give? If your drivers are set up correctly and you type the command <fastboot devices> it should list your serial number.
El Daddy said:
First, have you booted into the bootloader? (hold down volume up and down + power)What error does it give? If your drivers are set up correctly and you type the command <fastboot devices> it should list your serial number.
Click to expand...
Click to collapse
I am in fastboot mode, lock state is unlocked.
the cmd prompt error message I get 'is not recognized as a command.
The first line reads C:\Users
You have to open the command window in the folder you have fastboot.exe installed on your computer.
To do so navigate to that folder and hold down shift + right click. Then "open command window here"
Hello smart people. Hoping someone there has an idea for me...
This morning I dropped my GN and killed the screen. The display kinda-sorta works, but the touch sensor is non-op. OK, no problem, I've got in contact with Samsung and they'll fix it for the same price I can buy a replacement lcd/digitizer assembly anywhere I've found. Only problem: They'll be wiping the phone.
90% of what I need on the phone is synced to the cloud in one way or another, so I'm not too worried, but I WOULD very much like to recover some recent video and pictures that haven't been archived yet (daughter's dance recital). Phone is still working, except that it's pin-locked now (company policy) and I can't see the file tree to pull the stuff out.
Then I thought I'd play with the GN Toolkit. Only problem there is I guess I need USB debugging turned on, or something else I need enabled is disabled and I can't twiddle the menus to enable it.
Let's start with the obvious easy question: Any way to sync to the file system without unlocking via the touchscreen?
Failing that, is there any way to unlock/enable whatever I need to use the toolkit to pull the images out of the media directory?
I have a little time before I need to send the phone to Samsung for repair, so I'm willing to mess with this a bit and learn whatever I need to learn, but I'm not sure if what I need to do is even possible.
Thanks.
Can't just plug the phone in to a computer and it appear as a media device? Should be able to just pull the internal data.
Sent from my sprint galaxy nexus
ÜBER™ said:
Can't just plug the phone in to a computer and it appear as a media device? Should be able to just pull the internal data.
Sent from my sprint galaxy nexus
Click to expand...
Click to collapse
If the phone is pin-locked, the file system shows as empty when you connect as a media device (until you unlock it).
Herbie555 said:
If the phone is pin-locked, the file system shows as empty when you connect as a media device (until you unlock it).
Click to expand...
Click to collapse
Sorry wasnt aware of that. If you cant get it unlocked.. and USB debugging isnt enabled... then your outta luck.
You could get an MHL adapter and plug in a mouse, then use that to enter your pin at the lock screen. You could also go into recovery and factory reset, as that shouldn't touch your /sdcard contents.
Is there another way for enable debugging on Nexus?
I guess we can't enable debugging via adb, right?
If you just find a way around to do that, maybe you can use the line "adb pull"
(If you search for "adb commands" on Google you will find a list commands to use on developer.android.com)
Stadsport said:
You could get an MHL adapter and plug in a mouse, then use that to enter your pin at the lock screen. You could also go into recovery and factory reset, as that shouldn't touch your /sdcard contents.
Click to expand...
Click to collapse
If he's on stock then yeah that will delete his internal. If he's on a custom recovery no.
Sent from my sprint galaxy nexus
There's a plug in for the SDK called screencast which let's you use your computer screen a duplicate screen to your Android device. You can select things with your mouse. We used to use it in the early gingerbread days of my old vibrant when recovery was hidden behind the double rainbow
Sent from my Sprint Galaxy Nexus CDMA using xda premium
mnoguti said:
I guess we can't enable debugging via adb, right?
If you just find a way around to do that, maybe you can use the line "adb pull"
(If you search for "adb commands" on Google you will find a list commands to use on developer.android.com)
Click to expand...
Click to collapse
Debugging has to be enabled for ADB to be able to interact with the phone.
Glad I ran across this thread. I have a colleague in the same situation.
Stadsport said:
You could also go into recovery and factory reset, as that shouldn't touch your /sdcard contents.
Click to expand...
Click to collapse
Ahh, this might be a path to victory. Didn't realize I'd be able to do a factory reset and have stuff stay intact. Might be my best approach...
ÜBER™ said:
If he's on stock then yeah that will delete his internal. If he's on a custom recovery no.
Sent from my sprint galaxy nexus
Click to expand...
Click to collapse
Oops, got excited. Yeah, stock ROM. So a factory reset will wipe everything?
Herbie555 said:
Oops, got excited. Yeah, stock ROM. So a factory reset will wipe everything?
Click to expand...
Click to collapse
Yes. And the only way to get anything to work is to have USB debugging enabled. Screen cast only works with adb enabled.
Looks like I might be boned on this one. Thanks much for everyone who had suggestions. Sounds like leaving USB debugging enabled might be a best practice from now on, eh? (Or at least making sure EVERYTHING syncs to the cloud automatically...)
Looking at the google policy manager, I can remotely: Lock the device (duh), Reset the Pin, make it ring, or "Wipe", which I'm guessing is a factory reset. Might try that as a last resort, but I'll remain hopefull.
I'm sure you've tried this - but if you''re on stock you may be able to boot into recovery using voldown + power (or is it volup+voldown + power? Not sure, can't remember). THEN plug it into your machine and see if it shows up in the toolbox as a connected device...
adb should be enabled in recovery. reboot to recovery [power + vol up and down] mount sdcard and then adb pull whatever files.
ipfreelytech said:
adb should be enabled in recovery. reboot to recovery [power + vol up and down] mount sdcard and then adb pull whatever files.
Click to expand...
Click to collapse
Feel like I'm getting closer. I can see enough screen to scroll through to "Recovery Mode" and hit enter. It seems to reboot at that point, but then I can't see enough of the screen to navigate any additional menus. Should I be able to connect at that point?
Herbie555 said:
Feel like I'm getting closer. I can see enough screen to scroll through to "Recovery Mode" and hit enter. It seems to reboot at that point, but then I can't see enough of the screen to navigate any additional menus. Should I be able to connect at that point?
Click to expand...
Click to collapse
Plug it in via USB and see if the Toolkit picks it up...
thepatman said:
Plug it in via USB and see if the Toolkit picks it up...
Click to expand...
Click to collapse
I've apparently managed to get it mounted in the Bootloader interface and in fastboot mode, but can't figure out how to get it into adb mode, which is apparently what I need to do the pull.
The LCD has gotten worse, I have almost no visibility now. If I knew now many down or up strokes to make at each menu stage, I could probably do it blind...
Herbie555 said:
I've apparently managed to get it mounted in the Bootloader interface and in fastboot mode, but can't figure out how to get it into adb mode, which is apparently what I need to do the pull.
The LCD has gotten worse, I have almost no visibility now. If I knew now many down or up strokes to make at each menu stage, I could probably do it blind...
Click to expand...
Click to collapse
Can't do adb in Fastboot mode. While in flastboot mode. Hit the volume up twice and hit the power button. This will boot into recovery. Then try using the
Code:
adb devices
command. If you get a gibberish code next do device ID. Then your good. Go ahead and
Code:
adb pull /sdcard/
Sent from my sprint galaxy nexus
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
I flashed a rom from with twrp. followed the steps up to this point. Upon rebooting phone I have lost all images on the screen. Just a black screen. If I hold power and vol down I can hear it connecting and disconnecting from my computer but nothing ever shows up on screen any help please.
"1. make sure you are on the latest bootloader, radio, vendor image
2. install twrp via the instructions in twrp forum
3. wipe data factory reset
4. flash rom
5. flash twrp zip again as the rom overwrites twrp (stupid pixel lol)"
It sounds like you might have accidentally borked your bootloader. Since I'm guessing you can't get to recovery mode, you'll probably need to try flashing a full factory image through fastboot to fully reset everything to stock and see if that helps.
problem is i have no visual. can even get to bootloader
Does the screen even illuminate? As in does power go to it at least?
Sent from my Pixel XL using Tapatalk
muttley06 said:
problem is i have no visual. can even get to bootloader
Click to expand...
Click to collapse
If you can hear it connecting to your computer, then this is good.
Try 'adb devices' or 'fastboot devices' commands from a command prompt on the computer. If either report a device serial number, you can run flash-all.bat
Just a heads up, I had the same exact issue yesterday and I am completely stock. The phone rebooted and after the Google logo came up the screen went black and hasn't turned on since. After looking around a bit it seems like it's a pretty common issue. Verizon seemed to not even question it and they are sending a replacement.
Power off phone
Hold Vol down and power.
Feel phone vibrate and it is on and in bootloader
you should be able to perform Fastboot Devices at this point to see it.
If you can get here you should be home free.
"Try 'adb devices' or 'fastboot devices' commands....." nothing reports to these commands. Phone does not illuminate at all. no sound is made, and no vibrations upon reboot.(power and volume down).
muttley06 said:
"Try 'adb devices' or 'fastboot devices' commands....." nothing reports to these commands. Phone does not illuminate at all. no sound is made, and no vibrations upon reboot.(power and volume down).
Click to expand...
Click to collapse
Time to get a replacement.
TonikJDK said:
Time to get a replacement.
Click to expand...
Click to collapse
Just put the request in will be here tomorrow.