Watch was working great for few weeks and then suddenly I started getting lots of error message stating "Android Wear has Stopped". So i tried to reset my watch, after the restart the watch was not getting past spinning color screen. I even tried couple of hours but nothing happened.
I went through some of the forum topics and tried to flash Boot, Recovery and System with the stock images. Now the issue seems to be different, whenever the system boots I get a image of Android System chest open with a red alert symbol on it.
I am able to login to Fastboot and Recovery mode, tried the same process multiple times. But still not able to get pass the latest error. I tried to TRWP recovery, Stock Recovery and tried to reset my watch. But nothing seems to fix the issue. Any guidance on how to fix this will be really helpful.
Do let me know if I am doomed also...Hope it is not the case...
Related
Hi,
I am going to describe my experience in hopes that it might help anybody. Also, the result at the end is not consistent with the Lollipop build info I have seen on multiple sites, so I am looking for any comments that experts might have. I am not an expert.
I accepted the Lollipop update (foolishly without looking at others' experiences) and I ended up experiencing the boot loop with the 3 circles flying around endlessly (or at least for multiple hours).
I looked at the various forums of people experiencing problems and learned how to enter the bootloader mode and the screen with the android on his back with red triangle & exclamation point coming out of his chest (can't recall the name of that screen). {apologies that I am in Montreal and I don't have my device so I can't reproduce this to be 100% precise with all statements}
Via these screens I tried:
1-resetting the cache with seemingly no impact ... still had endless boot load screen
2-wipe data/ factory reset with seemingly no impact
Interestingly, both options appeared to complete successfully based on the messages displayed
The forums at this point stated that the only way to get the device working was to flash the factory image, so I spent a while to get ADB and fastboot and the factory image and watched a bunch of youtube videos and got my ducks in a row. I got to the bootloader screen and realized that I didn't have the driver loaded, so took care of that.
For various reasons I re-started the device in order to get back to the boot loader screen. But, I had a brain fart and couldn't remember the sequence to press on the buttons to get there. I got to the first screen with the android on his back (red triangle w/ exclamation point) and the prompt "no command" (or something like that), and I started searching online for the button sequence. Then I got distracted with a phone call for like 15 or 20 minutes, but I am still sitting there with the device in front of me showing the same screen.
THEN, for some unknown reason, the device re-booted itself as it was lying untouched on my table, booted into the started screen and then the setup screen for Lollipop showed up. I was in shock. I set the tablet up without any issues. All the data and all apps were gone (but it seems to not have reverted to factory condition b/c it wasn't setting up KitKat). At any rate, I haven't found any bizarre/bad behavior, though I also had to leave it at home for my wife whilst I went on a business trip.
The one strange thing I noticed was that the versions didn't seem accurate as I compared them to some of the sites I was researching in my prep for flashing to Lollipop.
These 2 looked correct:
build number
LRX22G
Android version
5.0.2
but not in conjunction with this:
Baseband version
DEB-G00_2.42.0_1204
-because this should be for 4.4.3 or 4.4.4 as indicated on these websites
I restarted the device in the event something just wasn't refreshed properly, but all of those still showed the same after the restart. So, this is where things stand. Hopefully there isn't a problem with this combination, but please advise if you think there is. Also, please provide any insight as to how the machine can reboot itself in that mode and suddenly start working. I'm thankful, but befuddled.
Thanks, Peter
I have a LG G3 with rooted stock rom running xposed.
So I pulled my phone out of my pocket today only to see the Verizon boot logo in effect. I was thinking "that's weird, guess my phone needed to reboot? Strange." But the only problem is it never stopped. It will only boot up to the lock screen and occasionally it will display an error message telling me the systemui has stopped. Then about 10 seconds later, it reboots itself. It continues this process until I pull the battery.
I've tried booting into safe mode, no luck. It doesn't even actually boot into safe mode (it doesn't say safe mode in the bottom left corner.)
I tried wiping the cache, no luck.
I don't want to just do a factory reset because that hasn't seemed to help anyone else with this issue as far as I've seen. I have not found any helpful information on how to fix this problem.
My question is, what do I do? I feel lost on this subject. Normally I've always been able to diagnose problems on my own, but not in this situation.
I have all my apps and data backed up to Titanium Backup on my SD card.
Any suggestions?
Xposed is more than likely the cause. Boot into TWRP and open a terminal, then type the commands as shown in the OP of this thread to bypass it...
How to Disable Xposed on Lollipop when stuck in Bootloop
http://forum.xda-developers.com/xposed/xposed-lollipop-stuck-bootloop-t3055816
Watch was working great for few weeks and then suddenly I started getting lots of error message stating "Android Wear has Stopped". So i tried to reset my watch, after the restart the watch was not getting past spinning color screen. I even tried couple of hours but nothing happened.
I went through some of the forum topics and tried to flash Boot, Recovery and System with the stock images. Now the issue seems to be different, whenever the system boots I get a image of Android System chest open with a red alert symbol on it.
I am able to login to Fastboot and Recovery mode, tried the same process multiple times. But still not able to get pass the latest error. I tried to TRWP recovery, Stock Recovery and tried to reset my watch. But nothing seems to fix the issue. Any guidance on how to fix this will be really helpful.
Do let me know if I am doomed also...Hope it is not the case...
Did Anyone managed to solve this issue, currently having my watch without doing anything. Any help on this is really very much appreciated. Thanks.
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
Hey guys,
So I've been running on stock EPD1 and everything had been running smoothly. Last night my phone randomly shut down, even though it was at full battery. After trying to restart it, I got stuck in almost a boot loop. It would boot, and during the Samsung animation, it would freeze and restart. This would happen twice until the phone gave up I guess and the phone stays at a black screen with either a constant blue LED, or a blinking whitish-purple LED. I have tried using ODIN to flash back to stock EPD1 and EPF1. Both were successful in ODIN, but didn't solve anything. I can flash TWRP, but flashing any ROMs doesn't help. Wiping Data, System, Cache, and formatting hasn't done anything as well. I also used the Smart Switch and Kies emergency software recovery and initialization features. Again, both said they were successful, but didn't change anything. Sometimes the boot gets to the point where it says "Android is optimizing apps," but once that finishes, it crashes again. Am I 100% screwed? Thanks to anyone that can offer some advice.
Small update: After using the emergency recovery feature in Kies once more, the phone booted to the green "Android is starting..." screen and it counted through 35 apps and said it was starting. It crashed at that point. Not sure if that's progress.