Develop Bugs

[HELP] Sony Smartwatch 2 stuck in bootloop after a normal reboot

This morning I removed my SW2 device from the charger, and after noticing that my OnePlus smartphone didn't recognize it anymore I tried to reboot the smartwatch.
Since then it seems to be no longer working. The Sony logo appears, there is a loading bar for a few seconds, then the screen flashes for a moment, and it goes back to the Sony logo, and so on.
I have also tried to switch off my OnePlus completely in order to exclude any pairing bug.
I read from the web that it might be possible to force a factory reset by pressing the power button for 15 seconds, but this doesn't work for me - it simply switches the SW2 off.
By putting it again under charge I notice that it turns automatically on, but even then it remains stuck in the bootloop.
Please help, I feel like I bought just an expensive little wrist brick.

Something like this has started to happen to me to... when the watch boots the Sony logo can be either yellow.. .or blue.. or white...
Edit: Try the procedure described in this post. Only 5 mins since I did it.. but so far, so good. :highfive:

I've fixed the problem - by buying a Moto 360.
I would advise everyone to stay away from SW2. It runs a proprietary OS + proprietary software that is just not compatible with everything that is happening in the rest of the world with Android Wear, it's not compatible with all the apps released for Android Wear (and hence it's compatible with only few apps exclusively released for SW2), and in case something goes wrong for any reason (like my bootloop), it's not even possible to perform a factory reset.

Sony Smartwatch 2 stuck in bootloop after a normal reboot
anybody help????

Frustrated - 360 turns off randomly

Hi,
I've had this watch over a year now. Everything was working fine until probably last update or two. Now the watch just turns off randomly even when battery level is high. And sometimes it won't turn on unless its connected to the charging dock. I've tried deleted android wear, clearing cache, unpairing, factory resets, restarts. Nothing has worked, i've tried it close to 10 times now and just another factory reset this morning. Haven't been able to use the watch for like 2 months now. Its just a desk clock now. Please help.
Android Wear version - 1.3.0.2166028
Play Services = 7.8.99
Android OS = 5.1.1

is the watch actually shutting down like when you go into the screen and tell it to shut off or does it just go blank right away?
If the later then I hate to say it but it sounds like something inside the watch is broken. Perhaps a contact or solder point near or on the battery. Hard to say without sending it for service.

SirDigitalKnight said:
is the watch actually shutting down like when you go into the screen and tell it to shut off or does it just go blank right away?
If the later then I hate to say it but it sounds like something inside the watch is broken. Perhaps a contact or solder point near or on the battery. Hard to say without sending it for service.
Click to expand...
Click to collapse
It just goes blank. No notification at all. It's been on for 20 percent now. But I am sure it will turn off again. Maybe it's because it gets hot. I dunno.

bustanut666 said:
Hi,
I've had this watch over a year now. Everything was working fine until probably last update or two. Now the watch just turns off randomly even when battery level is high. And sometimes it won't turn on unless its connected to the charging dock. I've tried deleted android wear, clearing cache, unpairing, factory resets, restarts. Nothing has worked, i've tried it close to 10 times now and just another factory reset this morning. Haven't been able to use the watch for like 2 months now. Its just a desk clock now. Please help.
Android Wear version - 1.3.0.2166028
Play Services = 7.8.99
Android OS = 5.1.1
Click to expand...
Click to collapse
Did the watch suffer any kind of mechanical shock ?

Cst79 said:
Did the watch suffer any kind of mechanical shock ?
Click to expand...
Click to collapse
Not that I know of or anything very severe. I have pumped it on a wall before but that's it. Never dropped or anything. Just seemed like after the updates it when crazy. And I've tried almost every solution I've read on these forums.

So only turned off once yesterday which was good. This morning took it off dock and it didn't pair. Tried turning on/off bluetooth on phone no luck so I restarted watch. Then it says "android is starting". "App 1 of 12". Why does it do this sometimes? Does it alot. And it will not finish the process and boot up the watch unless it is docked. If wearing watch. It just shuts off.

bustanut666 said:
So only turned off once yesterday which was good. This morning took it off dock and it didn't pair. Tried turning on/off bluetooth on phone no luck so I restarted watch. Then it says "android is starting". "App 1 of 12". Why does it do this sometimes? Does it alot. And it will not finish the process and boot up the watch unless it is docked. If wearing watch. It just shuts off.
Click to expand...
Click to collapse
That sounds like it is trying to update or download the apps to the watch... which it sounds like you have 12 installed on your phone.
Have you tried deleting ALL the apps from you phone (only the 12 apps for the moto 360) and then uninstall Android wear and factory reset the moto 360 and then download Android wear to your phone and pair the 360 as a new watch and test it for a while and see how it works?

I have the same issue, watch shuts down while I am jogging and listening to Android Wear music from the watch throught Bluetooth. Watch shuts down around 75-80%. When I start it says: Loading Apps 1 out of 12... then shuts down (I assume its a safeguard mechanism for watch not to start without full battery to ensure all apps load completely).
When I wear the watch normally, it never goes off during the day, issue presents itself only when using Bluetooth headphones (perhaps the heating of BT transmitter forces the watch to malfunction and shut down)

ykazimir said:
I have the same issue, watch shuts down while I am jogging and listening to Android Wear music from the watch throught Bluetooth. Watch shuts down around 75-80%. When I start it says: Loading Apps 1 out of 12... then shuts down (I assume its a safeguard mechanism for watch not to start without full battery to ensure all apps load completely).
When I wear the watch normally, it never goes off during the day, issue presents itself only when using Bluetooth headphones (perhaps the heating of BT transmitter forces the watch to malfunction and shut down)
Click to expand...
Click to collapse
I never connect the bluetooth to listen to music. It just shuts down.

Maybe you are doing something that causes it to overheat. Do you leave it on for prolonged periods of time?

Been having this same issue. The Moto 360 powers off and when I press the power button to turn it back on I see the splash "M" image then it turns off. The only way to get it to stay on is to put it back on the dock and when it turns on it says shows the updating apps screen. Any fixes?

I haven't figured out fix. Because of this I barely use my watch anymore. Sucks.
Sent from my SM-G900V using Tapatalk

yep, haven't used my 360 in 6 months because of this problem. it's a shame really. my warranty went out like a week ago too :/

Same thing has been happening to me as well. Not doing anything on the watch, it just goes into sleep of death and I have to put it back on the charger. Battery level is usually above 60 or 70 %.

Same issue!!!
Guys even I had same issue, my watch will heat up suddenly and turns off. I've to put it in dock to turn it on again. This issue never occurred after stopped using some of the new watch faces which allows dim option. I'm currently using some of the old watch faces which are working fine. May be these new watch faces are not working fine with latest update. Now I don't face any problem and battery life is also great.
Try this solution and let me know.

Watch faces has nothing to do with it. My watch will not fully boot into android wear unless it's on the dock no matter which watch face I am using. Even the minimal face.
Sent from my SM-G900V using Tapatalk

Anybody able to find a fix? This is so annoying

I'm having the same problem. I purchased a used Moto 360 off eBay for $120 and it turns off randomly even when the battery is pretty high for example it just turned off randomly at 80%. Then when I try to turn it on it boots up till the M logo or sometimes to the colorful part but then turns off again. It also only turns back on by putting it on the charging dock. Also it shows the Installing App 1 of 1 at startup and then suddenly shuts down again. I am extremely annoyed and frustrated because of this as I spend $120 on this watch and now I get this which makes it unusable and a waste of money. Please tell me guys if any of you find a solution!

Unfortuanately, mine is doing the exact same thing. I thought I had it working again, but as soon as I tried to give GPS permission to Google Fit (wouldn't run without it), it spun there and just went black. I literally just took the watch off the charger, so it isn't that. Now, if I hold the power button or press it multiple times, it tries to boot up, and will stop before it even gets past the normal Android boot animation. Sometimes, it won't even get past the Motorola boot animation. Now, when I put it on the charger, it seems to load perfectly fine, and even gets past the 'Starting apps' phase. Again, once it loads back up, my watch shows +90% battery. I've tried a factory reset, unpair/repair, and still no go.

Found a pattern
My app does the same but i have at least a pattern when it happens. It seems like it is as soon as there has been an update either in Android ware app or in soem app that has an wear application.

P605 in need of some help.

Hi, hoping someone can help.
Having a major problem with my P605 (Hong Kong version), It just will not start up anymore.
Current State:
At the moment, with just the power button, it shows the samsung galaxy note 2014 logo. Then a few seconds later the startup sound will play. Then a few seconds later the samsung boot animation plays. Then once the animation stops and just displays the samsung logo, nothing else. It stays on that, and can stay on it for hours.
Note: The Samsung boot animation has a very pink hue to it, like the cyan and yellow are no longer there. More on that later.
With the Power + Home + Vol Up it says recovery mode is starting, then resets and boots as above.
With the Power + Home + Vol Down it goes into download mode no problem.
Background (Some of it may or may not be relevant, just putting it on here in case it is):
Up until a couple of weeks ago it was stock, but rooted JB (IIRC), then it was accidentally dropped (not by me). It is in a Trident Krakhen case, but that did not stop damage being done, the damage being the backlight stopped working. I followed a Youtube guide and removed/reinserted the ribbon. Put it back together and switched it on, and worked, sorted!
Now I thought as the seal of freshness has been popped, I may as well upgrade it to Lollipop so I can play Pokemon Go. As Lollipop has not been released for HK p605's I used the Irish (I think) firmware. Upgraded using Odin, no problem. So then I wanted root access, so I used the method described on XDA to root Lollipop using "CF-Auto-Root-lt03lte-lt03ltexx-smp605.zip". Again, flashed with Odin, no problem. But the root didn't take, a few programs randomly lost root access, others would not ask for access and just say the tablet was not rooted, etc. I reflashed the file at least 6 times to try and get it to take. Eventually it did.
Forward to the next day, I go to unlock my tablet and the screen has gone all pink, same as above, like Cyan and Yelow have gone. And a black shadow is over the left half of the screen. I restarted the tablet, colours came back, yay. All fine up until yesterday, the pink and shadow were back again. This was late at night while I was in bed, so not near the computer. I restarted the tablet. This time the pink stayed. OK, so I thought I will wipe the tablet back to factory and see if that helps (not done a wipe or anything else up until this point) so I try to go into recovery mode. It showed the logo and the little blue recovery text, then black screen, then normal boot logo and back into the OS. Tried a few times to get into recovery mode, but just kept resetting back to OS. So I told ROM toolbox to force a recovery restart, big mistake! It went into recovery boot loop. Just Galaxy Note 2014 entering recovery" then blank, repeat. No sound, nothing. I think that perhaps if I can turn it off, it may reset the whole thing, I put the tablet into download mode, then go to sleep. In the morning, the battery is dead. Great! Plug it in, instantly recovery boot loop. Fudge! From this point I don't know the battery level of the tablet, so that MAY be causing issues. I plug it into the PC to flash with Odin. Flashed stock lollipop, restarted, flashed stock bootloader, flashed CF auto root. Multiple times in each. Nothing seems to bring it out. The closest I got to something was the tablet telling me recovery was screwed and I needed to use Kies recovery. I left it plugged in for a few hours to try and build up some battery power, the PC does not provide enough power to charge, it makes the screen flicker rapidly when the battery is empty, but all the time while charging it is boot looping and the screen is on full brightness so I don't know how much I gained.
Finally flashed stock KK, and now it just hangs on the Samsung animation logo as above.
Is there anything I can do?
Does the pink hue and black shadow mean hardware is affected? The colours seem fine in download mode.
If anyone could help that would be great as I am scratching my head here.
EDIT 1: OK, I took the casing off, found that the little push on connector next to the usb connector had pried itself loose, I reattached it, and removed/reinserted the screen ribbon cable. All while the tablet was powered on (my old electronics teacher would have had a fit!). Restarted, the pink tinge has gone and the boot animation came up at the same time as the audio. Good signs. But still froze on the 'glow' effect. Tried recovery and YES it went into recovery, although the little android fell over with an exclamation mark over him. But still, progress. So now I am reflashing stock, will see how it goes.

G4 bricked, possibility of resurrection?

This is embarrassing, but I was trying to install Pokemon Go on my G4 and the phone got really hot and rebooted. It never came back. Just went into a boot loop. I found instructions online on how to do a master reset with the power button and volume down letting it up briefly when seeing the logo and then pressing it again and letting it boot. I answered the question about deleting all user data and then answered it again. It said it was erasing data, then froze for a few hours at "optimizing apps" on one of the steps while I left it plugged in. I eventually pulled the battery to get it to respond again and now it just shows the LG logo and then goes dark. While dark it doesn't respond to button presses or let me try again to power it on, etc.
Any chance of me getting this phone working again? Is there anything else I can try aside from the master reset that I've already tried?

Hello if you look under the battery and your serial number starts with 505 or close its dead.
Sent from my LG-H815 using XDA-Developers mobile app

Eudmin said:
This is embarrassing, but I was trying to install Pokemon Go on my G4 and the phone got really hot and rebooted. It never came back. Just went into a boot loop. I found instructions online on how to do a master reset with the power button and volume down letting it up briefly when seeing the logo and then pressing it again and letting it boot. I answered the question about deleting all user data and then answered it again. It said it was erasing data, then froze for a few hours at "optimizing apps" on one of the steps while I left it plugged in. I eventually pulled the battery to get it to respond again and now it just shows the LG logo and then goes dark. While dark it doesn't respond to button presses or let me try again to power it on, etc.
Any chance of me getting this phone working again? Is there anything else I can try aside from the master reset that I've already tried?
Click to expand...
Click to collapse
send it back for reapir.

hi, mine was 509. It died 2 weeks ago, showing only "LG life is good" if trying to boot it. No way into recovery. (did boot one time very slowly to lockscreen before the definitive death)
This seems to be the same for you.... dead CPU I suppose. I'm still waiting for the repair.
(curious about the 505 asserted here, since mine was higher)

Hello the first 3 digits of serial number indicate date of manufacture, and the early ones have a manufacturing defect.
Sent from my LG-H815 using XDA-Developers mobile app

Hello,
mine was 510 and died on me 4 weeks ago, (boot loop with only LG logo) as it died from overheating (or at least was very hot when die occured), I tried to cool it and it was "succesful"
It put it in the freezer for some time and then could boot it on TWRP and make a full backup (I left it in the freezer the whole time)!
boot at normal temp lead to black screen in 10-15secs. I sent it back for repair (motherboard replacement was made in less than 1 week by Lg France), I am now waiting the answer from Lg developer to unlock the bootloader again.
I guess you can at least try and see if you can have the same result as me.
Marc

G4 bricked, possibility of resurrection?
Click to expand...
Click to collapse
No.

watch nearly dead :( please help . Black Screen!

Hi all
I restarted my watch using settings menu. Then left the watch on charge and went away. Next day found watch to be dead with black screen. I hard reset it by holding button for 10 seconds. It seemed to start but then gets stuck on start up ( at different places and different booting time, every time) Have not able to complete boot it once.
Then I thinking I am very clever, went into the boot menu and deleted cache and data. It seemed to load a bit longer than last times and actually went on to connect with phine and started update but got stuck on 20 out of 27 apps.
So every time it gets stuck, it black screens and the only way to bring it out of this state is to hold down the button for 10 seconds. It does not black screen in FASTBOOT menu. I am not sure if there is any warranty left on this watch as it was bough second hand and till now had been working really well for about 3 weeks.
I have installed adb drivers but it doesn't show up on the PC. May be because i didn't do the developer options step before I am guessing. Anyway I have no idea what is happening to the watch and if it is even recoverable or not.
Any one seen this before? any ideas what I should do?
Thanks so much
One thing that gives me confidence that battery is not dead is that if I leave it in the fastboot menu screen then disconnt the carger it stays there.

I tried sideloading Android Wear 1.4 image. It fails at 57 or 58% , always

Just a note to anyone with similar problem. My watch sorted itself out after a few days. I think , if you leave your watch on charge and don't touch it for two days then it somehow help. I am not sure how it started working. My suspicion is that the watch either had water in it that dried out over two days or the charge had somehow gone so low that it needed a very long charge to stabalize. Anyway, it works now.