I bought a used Zenwatch 2 and after a week it stopped working. When I turn it on it sticks on the Asus splash screen. After talking to customer support and looking online it appears that the "firmware has been corrupted.
I made the mistake of not turning on ADB Debugging while it worked, and unfortunately the screen appears to be unresponsive so I can't even put it into Fastboot mode to turn ADB Debugging on. Of course to make it even better the watch is not recognized when I plug it in because it doesn't appear to boot enough. Since I can't get into anything it makes it impossible to reinstall the firmware.
You all are my last hope, does anyone have any insights into a way to get the phone recognized, or anything that may help? Please help me keep this from becoming a fancy bracelet.
When you first turn it on, swipe diagonally down from either direction to get into recovery or fastboot. I know you said the screen is unresponsive, but if you haven't done it before it can be tricky. Even on a perfectly working watch, I still have trouble getting it to work. Try continuously swiping as you hold the power button, even before the splash screen shows up. If you can get it into fastboot, unlock the bootloader and try flashing my ROM.
CVertigo1 said:
When you first turn it on, swipe diagonally down from either direction to get into recovery or fastboot. I know you said the screen is unresponsive, but if you haven't done it before it can be tricky. Even on a perfectly working watch, I still have trouble getting it to work. Try continuously swiping as you hold the power button, even before the splash screen shows up. If you can get it into fastboot, unlock the bootloader and try flashing my ROM.
Click to expand...
Click to collapse
That seems to be what I am reading, but so far I have had no luck getting it to trigger into fastboot mode. I will keep trying.
Related
Hi, I was wondering if anyone can help me with my last problem. I recently started a different topic ( which seems dead
Link), and I have one problem after I have finally
gotten my phone in a usable state. It is unable to mount my /efs directory, or whatever. And while I don't know if they are directly connected,
things like my lock screen, holding my power button to get options like Flight Mode, Data Network, Restart, Etc., is gone, among the most
noticeable things. And I have tried screen lock to work, it doesn't. Holding my power button shuts my phone down (in the same amount of
time that holding it would normally bring up the options screen, as well). I would just like to get my phone in complete working order,
assuming that isn't to much to ask. Any help in getting past this final hurdle would be greatly appreciated. To see what I've done/my
progress, go here: Link. Currently, I
successfully have CF-Root on my phone, and my firmware is XXLPH. I've only had luck with 2 firmwares I believe. This one and one
other... Others make my screen black, except for my notifications tray.
Hello everyone,
I've been a reader for a while, purely out of interest. I've never really dabbled with customizing android. In that regard I am a noob... I recently acquired a Medion X6001 that I was planning to build into my car as informant/navigation. Phone root successful, developer options active, debugging and oem options active. Automate programmed to all the standards I was happy with., worked great. All that was left to do to was get the thing to boot on charge. The "fastboot oem off-mode-charge 0" command was unsuccessful so I resorted to trying to find the system file responsible for battery icon on charge with power off.
That's where I went wrong. This phone has two icons; first a battery with a bolt, then switches to another with blue fluid and battery percentage. I found the blue fluid battery icon - 'system/bin/kpoc_charger', unfortunately I needed the killswitch battery icon. So I made another guess and renamed - 'system/bin/lmkd'. This was the file directly before ...kpoc and my daft logic lead me to believe that that might have been the right file. Obviously, it wasn't.
So the problem? The phone won't boot. Not really... At first, it was entirely stuck in bootloop. So, the good sheep I am, I factory reset the phone through recovery. The phone still went into bootloop for a few minutes, but came out of it to an applet saying 'optimizing apps'. Took 10 minutes to optimize and then went through to another applet saying something along the lines of "system process not found, do you want to wait?". Behind this applet I could tantalizingly see the startup screen of a freshly reset android.... It gave the option to wait or push ok, neither of which were actually active to touch. If I held the power button it would give me the option to shutdown, reboot or screenshot, also none of which where actually active to touch.
So after more googling, I wiped the cache through recovery. Everything stayed the same; bootloops for a few minutes then applets. Only now everything is in Chinese kanji... which is why I can't reiterate verbatim what the applets originally said...
After around 12 hours of tirelessly searching the web I've tried everything I've found but every time I get through a door there's another one closed. I can't install twrp or clockwork, I can't flash the rom, the phone won't let me unlock the bootloader in fastboot. Went I type the command it asks if I want to unlock it: volume up yes, volume down no. But fails: "remote access denied"
Since the factory reset, I don't have access through adb anymore. If I let the phone boot I can see it connect to the computer, but only as mtp. The file is entirely empty. I have no access to usb debugging. And to remotely access that, I need to be able to unlock the bootloader.
I can't get around the blocks and everything that is advised to get around bootloops and flash through fastboot are seemingly impossible because I no longer have proper access. But I can't get into the phone to get access...
And to make matters worse, just now as I type this.... I can't get into fastboot anymore. I think the phone battery is dead, but apparently doesn't accept a charge. When I plug it in the battery symbol appears, the dark red led lights up indicating very low battery. Very shortly after that the led turns off, which is not how it was before I buggered everything. Battery icon stays on, but when I push the necessary buttons to get into recovery, everything goes blank and the phone does nothing. When released, battery icon comes back and red led for a few seconds. Repeat. Phone has been plugged in all night....
I'm nearly bald from pulling my hair out. I hope there's someone out there that can give me a hand. I have a hard time believing I bricked the phone just by changing a bin file name.
Thanks in advance!
fastboot
I have access to fastboot again. Plugged the phone into a different cable, is now charging. I can see the battery % through recovery.
Back in business....sort of.
Any idea's welcome.
bump
Anyone?
Well I found the ultimate cure: buy a new one.
I will however keep fumbling around with the other one and hopefully as my knowledge increases I'll have a break through.
After allowing to download a security update a couple of days ago, my watch went into a boot loop. It would get up to the screen with the time and the colorful spinning circles, run for a bit, then turn off.
I can enter fastboot, which has a message that the battery is low, and to connect a USB data cable (don't believe that's possible), status: 0.
I can also enter recovery. However, the instructions say that I should swipe up on the image of the dead Android. This doesn't work at this point, but a long press of the physical button does. So I enter recovery, and see my list of options. Again, I'm supposed to be able to swipe up and down to scroll through the list, and swipe left and right to select an item. No swiping works. Both a short and a long press just select the item in recovery, and the only item I can select at that point is to reboot.
After draining the battery as much as possible, to the point that I can't even enter fastboot without charging, I powered it on, and instead of displaying the time and spinning circles, it's just the spinning circles, but I think I have the same problem. It was running that for at least 20min and never got past, which is longer than even a first boot after factory reset.
Any thoughts on how to navigate in recovery or factory reset another way?
Same situation in here, but I solved it by pressing power button for 10 seconds, then the watch reloaded and everything went fine.
I have the same problem, but I get to the factory default option and back to the initial loop
Did anyone fix this?
Motorola have said they'll take my watch in for repair, but as I'm outside the 1yr warranty, they'll charge me. Also, they don't know the cost of the repair, so I'm basically giving my watch away allowing myself to be held to ransom for whatever price they seem fit.
Same here but its booting showing we got key update and I can't navigate to any side, even though on recovery mode same touchscreen not working. all was ok before this update...
ITMASTER said:
Same here but its booting showing we got key update and I can't navigate to any side, even though on recovery mode same touchscreen not working. all was ok before this update...
Click to expand...
Click to collapse
There might be a possibility that your recovery mode is working, but you have to navigate with two fingers or swipe multiple times to get from one to the next entry. I thought that my touch is broken, but its just a bad engineered handling.
I hope this helps
Cheers
Rezoran said:
There might be a possibility that your recovery mode is working, but you have to navigate with two fingers or swipe multiple times to get from one to the next entry. I thought that my touch is broken, but its just a bad engineered handling.
I hope this helps
Cheers
Click to expand...
Click to collapse
Yes Same here I also managed to do that !!
But anyway its not working normal and its not an system update..as after full reset you get back... this is just wear os update which is not coming back to my watch after I have reset it, I got old interface and security patch stays on 2017 April so our watch is lost support for updates
Is there a way to report Motorola support team that with this update they make watch useless?
You can get the touch to work in recovery. It's just very buggy...
Swipe down (might be up, not quite sure anymore) like a maniac as soon as you select recovery mode and don't stop for about a minute. You might have to press the button to get rid of the android symbol. But the touchscreen will suddenly start working normally allowing you to navigate the recovery. Might take you a few tries, but it does work.
Good luck.
I purchased a note 4 as a fun project, it has a cracked top glass only around the upper camera, I figured once I reset it, was going to proceed with glass replacement.
I put it aside, now its been a few weeks, so I hope I get the this in order of events.
While I am not expert, I am not a newberry either, but have exhausted my knowledge and searched this forum over, but maybe not using the correct search keyword.
I believe it is complete stock, but has a passcode and/or finger print lockout, so unsure. Still has all the previous user's settings & files.
It boots fine to lock screen. I can navigate to make an emergency call, all screen, volume buttons work, etc.
I simply want to wipe it through the normal stock recovery, but the normal key power+up+home combo is not working, the phone simply boots straight to lock screen every time.
Download mode is also not accessible either. power+down+home, same thing - boots and straight to lock screen.
Every combo of pressing power, volume or home get me to the same spot. Its as though the buttons do not work until it is booted up to lock screen.
I figured I would craft up a 300K usb jig to force download- still no go, same issue - boots straight to lock screen. Even tried variable resistor values, still no go.
I finally was able to get to download mode using Samsung 300K tool program - but even then, the phone will only initiate download mode if I click "connect" at just the right time during bootup.
So I downloaded the appropriate 6.0 android from SamMobile, loaded it via Odin successfully, the download finished, phone rebooted, and continued with android setup ( the screen where android initializes apps i.e 1/3xx, 2/3xx, etc and runs through 200, 300 or how many apps are installed, it takes awhile), so I walked away to let it finish.
I come back - its on the same dang lock screen.
Now I have read that one workaround is to pull the battery after some point to stop the phone from booting, then enter recovery and clear cache/ dalvik.
So I tried that, Odin, download, once phone reboots and vibrates, pull battery - but as stated, still not able to enter recovery.
USB debugging does not appear to be enabled, so unable to try that route either.
At a dead end. Anybody have a suggestion to get this device reset to factory.
I will even take a verbal beating :laugh:
Would love to even get TWRP, but thats a pipe dream at this point.
jammer
Ive got a note 8 that just died on me today. The screen remains blank no matter what I do. When I plug into any charger, it sends out random short vibrations usually every few seconds. Ive tried rebooting, force rebooting, recovery booting, nothing lights up the screen. No combination of volume and power keys accomplish anything. The battery had around 40% when it went out. Please help me recover this thing! Ive replaced the battery and LCD on it once. I really don't want to just throw random parts at it hoping for a fix. Yes Ive checked every connection to be secure. I am thoroughly stumped.
Skytex said:
Ive got a note 8 that just died on me today. The screen remains blank no matter what I do. When I plug into any charger, it sends out random short vibrations usually every few seconds. Ive tried rebooting, force rebooting, recovery booting, nothing lights up the screen. No combination of volume and power keys accomplish anything. The battery had around 40% when it went out. Please help me recover this thing! Ive replaced the battery and LCD on it once. I really don't want to just throw random parts at it hoping for a fix. Yes Ive checked every connection to be secure. I am thoroughly stumped.
Click to expand...
Click to collapse
Connect the phone to the PC and then open a command prompt window where you installed ADB and run adb in the command prompt window and when it opens then type adb shell reboot recovery and see if it reboots to recovery mode but it requires that you have USB debugging enabled in developer options and if it's not enabled then there's nothing else you can do.
Its totally stock. Never installed adb on this phone
Skytex said:
Its totally stock. Never installed adb on this phone
Click to expand...
Click to collapse
Adb is "installed" on your computer, not phone. Adb/fastboot commands are delivered to the device.
https://developer.android.com/studio/releases/platform-tools