Stuck in Boot - Asus ZenWatch

Watch gets past the ASUS Boot Screens but gets stuck in the Android Boot animation.
I've tried booting into recovery (swipe top right to bottom left) but it doesn't work.
I can get into Fastboot and from there I've tried wiping the cache, unlocking, and relocking the bootloader. None of those options seem to do anything.
Background:
I've got two Android watches of my own (360 and LG G) and was actually just helping a friend upgrade the firmware on his ASUS ZenWatch since he's got an iphone.
1) I tethered to my phone and began the firmware download from stock, but it kept throwing an error about running out of memory, even after a factory reset.
2) I booted into Fastboot unlocked and wiped the cache. After this it successfully downloaded and upgraded to Android 5.0.
3) Went to download the next version (5.1 is needed for iPhone) and kept getting an error (this time different, couldn't get any matches doing Google searches). Tried a factory reset and it went into this mode where it makes it to the Android Wear boot animation and stays there until the battery dies.
I'm thinking the watch has some sort of hardware defect since he says he bought the watch new and it's failing on all firmware upgrades and won't boot into recovery.
Any suggestions? I'm not aware of any stock recovery images.

Related

[Q] Galaxy Nexus won't boot up! Restarting after google logo!

Hello to all
I have Samsung Galaxy Nexus 4.2.1 stock and unlocked.
It worked perfectly to two years! From yesterday i have problem with it! My GN won't boot anymore, I can see just google and X (nexus) logo after that GN restart itself! This is repeated without stopping until I put out battery.
I have tried to clear cache, wipe data/factory reset in Recovery Mode but problem has continued!
I have unlocked bootloader and update to android 4.3 stock (non rooted) through ADB (google SDK), updated successfully but when phone has reboot problem has continued, GN restart non-stop!
In Fastboot mode/Recovery Mode phone it never restarted! I have left in this mode with hours to try if restarted but no It works without any problems in this mode! It restart only when phone boot up!
Can this problem to be hardware failure or not?!
Can anyone help me? What can i do to boot my GN again?
I hope in your your support
visar.r said:
Hello to all
I have Samsung Galaxy Nexus 4.2.1 stock and unlocked.
It worked perfectly to two years! From yesterday i have problem with it! My GN won't boot anymore, I can see just google and X (nexus) logo after that GN restart itself! This is repeated without stopping until I put out battery.
I have tried to clear cache, wipe data/factory reset in Recovery Mode but problem has continued!
I have unlocked bootloader and update to android 4.3 stock (non rooted) through ADB (google SDK), updated successfully but when phone has reboot problem has continued, GN restart non-stop!
In Fastboot mode/Recovery Mode phone it never restarted! I have left in this mode with hours to try if restarted but no It works without any problems in this mode! It restart only when phone boot up!
Can this problem to be hardware failure or not?!
Can anyone help me? What can i do to boot my GN again?
I hope in your your support
Click to expand...
Click to collapse
Don't panic, this problem is called bootloop and it's normal. Just download factory images from here and flash them by using this awesome guide by efrant!!
Also bookmark this link for future reference.
http://forum.xda-developers.com/showthread.php?t=1812959
started having the same problem yesterday after 6 months of stability on a custom 4.3 rom.
oem lock then unlock to format, nothing, tried various methods of flashing back to stock via ADB with mixed results, normally more boot looping with it occasionally booting into a rom for ~5 seconds. so SOMETHING is working.
I tried Efrant's method about an hour ago, but its been sitting at the google logo since, I'm at a lost, I'm no stranger to boot loops when installing borked roms but this is the strangest problem I have ever had with an android device.
should I just chock it up to hardware failure?
Mostly yours USERDATA partition is corrupted.
Use FASTBOOT to reflash the USERDATA IMG and it should do the trick.
Sent from my Galaxy Nexus using xda app-developers app
did a total stock reflash again, got to the setup screen before it rebooted after ~15 seconds, bootlooping again. flashed the userdata img with a few different ones.
I'm trying to read my logcat but when I run the ADB command in clockwork It finds nothing.
I've done all steps by this awesome guide by efrant! But same problem here
I've tried to install 4.2.2 stock, 4.3 stock, all comands works but in the end when i press fastboot reboot my nexus it's in bootloop again restart restart and restart
Any other solutions :crying::crying::crying:
I've waited about 30 minutes after restarting non-stop, my GN boot to system i saw home screen of android but after 5 sec restarted again :crying:
I'm getting into my system once every 10 or so reboots. managed to turn off wifi in case that was the problem but still boot looping. I'm inclined to think it might be hardware related as I started having trouble in the middle of a text after several months of rom stability.

[Q] Stuck on Google logo after manual flash of Lollipop

A few weeks ago, before the OTA release of Lollilpop for my Nexus 7, I booted into fastboot mode and manually flashed the razor factory images for Android 5.0. Everything worked fine until the N7 crashed (from a fully working state) and rebooted. When it rebooted, it would not progress past the Google logo. All I can access is the fastboot screen.
I've now come back to try and fix it. I've tried erasing the system and flashing the old (and new) stock Android images using fastboot. This process completes without errors but the N7 will still not boot past the Google logo. I've also tried flashing a custom recovery but the N7 will not enter recovery mode.
My bootloader is unlocked and is currently version FLO-04.02. Does anyone have ideas for what to try next?

Stuck during Factory Reset ("Google")

Amazon Warehouse sent the wrong Nexus 7 2013, Wi-Fi only instead of LTE, so am returning it. I'm following Jimmy McGee's video on restoring factory settings,* using NRT 2.0.5. This wasn't rooted, just upgraded from 4.3.0 to 5.1.0 (didn't note the original build number, so chose the last 4.3.0 listed in NRT). Everything seemed to go fine through the Bootloader running (8:35 into the video). After that it reboots, but in doing so it stuck on "Google." I turned the N7 off and restarted into the Bootloader screen again (fastboot mode) and tried to restart from there, but it's never getting to the moving balls. Recovery Mode shows the Android icon with the triangle and exclamation point, and then switches back to "Google."
* video: http://www.xda-developers.com/factory-reset-unroot-nexus-xdatv/
UPDATE: I got into Recovery Mode and chose Wipe data/factory reset. Showed data wipe complete (but nothing about factory reset), but it still stuck at Google on reboot. Same with Wipe cache partition. I should add that the Nexus is not currently being seen by my computer (Win 8.1), except when in Bootloader mode it's seen by NRM. I ran the whole NRM factory reset process again, but was informed this time that the system is 5.1.1, 5.1.0. Not sure why NRM didn't say anything the first time through (Google had downloaded 5.1.1, but I never ran the install). In any case, it ran the same way again, everything looking fine, but then hanging on Google during the reboot.
Any ideas how to fix this?

LG G3 download mode issue

Hi everyone,
Being the more adventurous kind of person I am, and also rather sick of LG's android overlay, I decided to finally try rooting and installing a custom ROM, as my previous device was the Nexus 5, and I longed to return to the stock android world. It is a first for me to try this, so I read a few forum posts about it, and finally I rooted my G3 (D855 model), which went flawlessly. I then installed cyanogenmod 12 (I cannot remember which version, it was the most recent at the time) and I was finally satisfied by the software, which was as smooth as butter, unlike LGs skin. After a few months, I made the terrible mistake of installing one of the updates that where suggested, and then the problems began. While the phone was performing the update, it froze on the "optimizing apps" screen, and stayed so for several hours, until I decided to pull the plug on it, and it slowly died of a flat battery. I then tried to reboot the device, which stayed on the LG logo screen for a long time, until I again had to leave it to die. I then rebooted into TWRP recovery, which was the recovery I had installed and used to install CM12, and I tried to recover from the last backup I had performed a week prior about, and it failed with "error executing binary in script". After some googling, I found a forum where someone recommended to wipe the cache, data, system, and dalvik partitions. Having done this , the backup was successful and the phone was up again. A few days later I saw that CM13 with android M was released for the G3, and I decided to try it. I downloaded the rom, backed up my old version again and flashed it with TWRP. It worked, and the device booted into CM13, but I was greeted with a "process has crashed" message. I dismissed it, and the OS seemed to work, but then I realised it failed to recognize my SD card, and the phone internal memory (I own the 32GB model) was listed at a mighty 2gb. I decided to return to CM12 for the moment, so I rebooted into recovery, flashed the backup and got the same "error executing binary in script". I then wiped the cache, data, system, and dalvik partitions, and flashed my backup with no error. The phone reeboted, showed the LG screen, and then went black, then the LG screen, then black, etc... I quickly discovered this to be a boot loop. After some attempts to fix this, the phone booted to the LG screen, then the Cm logo pulsing, and then the "optimising apps". At the end of the process, the lock screen appeared, and after unlocking the device, I discovered it was back in CM13. This was suprising, and the errors I previously had were still here, so I returned to TWRP and tried to flash the original CM12 file I had, and this showed no error. After booting the device, CM13 greeted me again. I decided the device was seemingly possessed, and made the decision to unroot and reinstall into factory settings. But the first step of this process was out of reach, as the phone goes no further then the "download mode" screen with the small blue dots in the middle when I hold the volume down and plug it into the PC. After an hour on said screen, I pulled the plug and tried to reboot again. CM13 appeared once again, as if it was haunting my dreams, and I also found out that TWRP is no longer accessible, as the device stays on the blue loading screen of TWRP.
I have searched and not found anything saying how to get any further then this. I know that as I am not very experienced with this, it was rather foolish to act as I did, so spare me the lectures about that. But I didn't learn to ride a bike without falling off it, so it's kind of the same isn't it? Anyhow, is there someone out there who may assist me?
Many thanks to anyone who has any advice, I'm sick of my backup samsung S3 D:
Ed

Stuck on “Google” screen, no boot

Was driving home last night, phone in cup holder and all of the sudden it just has a white screen with the google logo. I went into the boot loader and tried everything i could, including factory reset wipe. Same results.
Then I downloaded adb and fast boot and side loaded the latest firmware zip. The process completed successfully but nothing changed. Still stuck on “Google”
I’ve never customized any bootloaders or firmware, phone is bone stock.
edit: so from what I read online is that pretty much out of luck since my bootloader is locked and i have no way of unlocking it since it wont boot

Categories

Resources