Ok, so here's the deal. Bought the watch and charged it to 100% before turning it on. Fired it up, synched with android wear fine and it wanted to update. I ran the update but it kept getting to the end and complaining about how there was an error and to try again. I threw it back on the charger and it had dropped all the way down to 64%!
I charged it back up and did the update. I was stuck on the android icon for about 10 min then it rebooted and was stuck at "Just a minute" for a good 15 min or so. I did a hard reboot. Since then I have performed a hard reboot multiple times. For awhile there it was giving me the option to reset, which I tried 3 times. I kept getting stuck on "just a minute" when trying to sync.
Now, after the last reset, I can't get past the big motorola logo when it boots. Usually it shows the logo and then has the gears moving through the logo. But now, it just shuts off and comes back on to that logo.
GaresTaylan said:
Ok, so here's the deal. Bought the watch and charged it to 100% before turning it on. Fired it up, synched with android wear fine and it wanted to update. I ran the update but it kept getting to the end and complaining about how there was an error and to try again. I threw it back on the charger and it had dropped all the way down to 64%!
I charged it back up and did the update. I was stuck on the android icon for about 10 min then it rebooted and was stuck at "Just a minute" for a good 15 min or so. I did a hard reboot. Since then I have performed a hard reboot multiple times. For awhile there it was giving me the option to reset, which I tried 3 times. I kept getting stuck on "just a minute" when trying to sync.
Now, after the last reset, I can't get past the big motorola logo when it boots. Usually it shows the logo and then has the gears moving through the logo. But now, it just shuts off and comes back on to that logo.
Click to expand...
Click to collapse
sounds like a boot loop, which sucks because i don't think there's a known way to get into recovery or if the watch even has one. i'd email motorola if i were you.
Ok, I left it off for about 30 minutes and finally got it to power back on so I could reset it again. Once again, it reset and wants to download an update. It downloads, reboots, installs, reboots and then just sits at "just a minute..."
This thing is a serious pain to get up and running. Any ideas? I don't know what else to try. Ive tried pairing it with a HTC One and a Galaxy Note 3.
*EDIT*
Ok, after 2 more tries I finally got it to the point where I saw a new boot screen. I figured that was good news. Now its been sitting on the Android boot screen. By that I mean the green, blue, red and yellow orbs have been flying around for 10 minutes.
wiredout46 said:
sounds like a boot loop, which sucks because i don't think there's a known way to get into recovery or if the watch even has one. i'd email motorola if i were you.
Click to expand...
Click to collapse
It looks like if I press and hold the power to shut down, then press and hold for a good 10 sec or so when booting back up it will boot me to a screen that shows:
"Bootloader version: 940
Device is LOCKED. Status Code: 2
Battery OK
Connect USB Cable"
Thats about as far as I can get now. It refuses to go past the android screen now.
*EDIT*
OMG... so I decided to fire it up and start trying to power it down immediately. I did that 3 times in a row and it booted up to the Android Wear pairing screen. I paired it and... its trying to download something again. I can't win. I may have to take this thing back and wait for the next LG watch. I can't figure this out.
GaresTaylan said:
It looks like if I press and hold the power to shut down, then press and hold for a good 10 sec or so when booting back up it will boot me to a screen that shows:
"Bootloader version: 940
Device is LOCKED. Status Code: 2
Battery OK
Connect USB Cable"
Thats about as far as I can get now. It refuses to go past the android screen now.
*EDIT*
OMG... so I decided to fire it up and start trying to power it down immediately. I did that 3 times in a row and it booted up to the Android Wear pairing screen. I paired it and... its trying to download something again. I can't win. I may have to take this thing back and wait for the next LG watch. I can't figure this out.
Click to expand...
Click to collapse
Try to get it to reset not restart. Then leave it go until it's fully charged again and retry.
dottat said:
Try to get it to reset not restart. Then leave it go until it's fully charged again and retry.
Click to expand...
Click to collapse
Got it to 100%, reset it. Rebooted a few times and it sat on the motorola logo for about 25 minutes, never moved. Powered down and on, now I'm in this damn android logo boot loop again. What a PoS.
GaresTaylan said:
Got it to 100%, reset it. Rebooted a few times and it sat on the motorola logo for about 25 minutes, never moved. Powered down and on, now I'm in this damn android logo boot loop again. What a PoS.
Click to expand...
Click to collapse
Is possible you got a dud.
So this morning I made s trip back to best buy and luckily they had 2 left in stock. I wasn't that aggravated because my last 360 had a dead pixel anyway.
With the replacement I did everything the same as I did last time and this time around it updated and did its thing flawlessly. So yea, sounds like I just have bad luck and got a dud.
GaresTaylan said:
So this morning I made s trip back to best buy and luckily they had 2 left in stock. I wasn't that aggravated because my last 360 had a dead pixel anyway.
With the replacement I did everything the same as I did last time and this time around it updated and did its thing flawlessly. So yea, sounds like I just have bad luck and got a dud.
Click to expand...
Click to collapse
Lucky to get one first round. Lucky to get a replacement the day you took it in. Glass half full. Enjoy your new watch!
GaresTaylan said:
It looks like if I press and hold the power to shut down, then press and hold for a good 10 sec or so when booting back up it will boot me to a screen that shows:
"Bootloader version: 940
Device is LOCKED. Status Code: 2
Battery OK
Connect USB Cable"
Click to expand...
Click to collapse
Just picked up my moto 360 and this is the screen I see when I first booted it up, so I have no idea what the battery level is or what to do for that matter.
---------- Post added at 10:24 AM ---------- Previous post was at 10:06 AM ----------
Ok maybe I acted too quick but I forced it off then put it on the charger for several minutes and automagically it booted up and seems to be working.
Related
Running new LVSW version of WM6. Working smooth as glass for 3 days now and this morning I turned on the phone, checked my email, adjusted call volume and the thing locked up HARD. I tried everything but nothing worked so I just pressed the reset button on the bottom. It rebooted but hung on the boot splash after displaying the red version numbers on the bottom. After a minute or so the green wireless light began to flash so I thought it was just slow booting, i left it like this for 15 min and it never proceeded to finish booting so I pressed reset again. Same result, stuck in boot splash forever. Since it was just going to sit and run down the power I unseated the battery to turn it off (the power button wouldnt do a thing.) Finally I get to work, I figure I'll put it in bootloader and hopefully just reflash it. As soon as I plug it into the USB cable and boot it up, it came up fine. Anyone have ANY idea what the heck is going on? Thinking now of trying the new WM Black edition v1.2 but with the recent strangeness of the current rom I'm wondering if I'll wind up bricking it. Any advice is greatly appreciated.
[email protected] said:
Running new LVSW version of WM6. Working smooth as glass for 3 days now and this morning I turned on the phone, checked my email, adjusted call volume and the thing locked up HARD. I tried everything but nothing worked so I just pressed the reset button on the bottom. It rebooted but hung on the boot splash after displaying the red version numbers on the bottom. After a minute or so the green wireless light began to flash so I thought it was just slow booting, i left it like this for 15 min and it never proceeded to finish booting so I pressed reset again. Same result, stuck in boot splash forever. Since it was just going to sit and run down the power I unseated the battery to turn it off (the power button wouldnt do a thing.) Finally I get to work, I figure I'll put it in bootloader and hopefully just reflash it. As soon as I plug it into the USB cable and boot it up, it came up fine. Anyone have ANY idea what the heck is going on? Thinking now of trying the new WM Black edition v1.2 but with the recent strangeness of the current rom I'm wondering if I'll wind up bricking it. Any advice is greatly appreciated.
Click to expand...
Click to collapse
Was your battery fully charged?
yep
Yes, 100%, had just taken it off charge about an hour before....
It has happened to me twice
The first time that I couldn't igure out what to do I simply Hard reset the device
The second and last time that happened to me (2 days ago)
after 3 consecutive soft reboots the thing came back to normal operating status..
I suspect that this has to do with ROM
Anyways I sure hope this is fixed with the new release...
Which I may flash later on today...
Today I was surfing the web and the phone locked up and restarted itself. Kept getting to the android screen with the red yellow and blue symbols then restarting. Left the phone alone to get back to work then the phone restarted finally went to use the phone and after about 3 mins froze up again. Now the phone won't get past the Google boot screen and if I want to try and power the phone on the power button has to be pressed in about 30secs to a minute of two.
Also i can't get into recovery mode reliably since if I select recovery the phone again freezes at the Google screen on reboot and never gets to recovery 9 out of 10 times other times I can get to recovery and then phone will then crash while in recovery or will allow me to use recovery long enough to wipe the cache and factory reset which neither has worked.
While Plugged into a charger and just sits there nothing on screen just a black screen.
Phone is on latest android unrooted and locked.
i had this happen to my SO's stock/locked/unrooted Nexus 6P.
Plug it into a PC, wait a couple minutes, then press and hold the power button for like 1-2 minutes.
2x4 said:
i had this happen to my SO's stock/locked/unrooted Nexus 6P.
Plug it into a PC, wait a couple minutes, then press and hold the power button for like 1-2 minutes.
Click to expand...
Click to collapse
What is this supposed to do? Where did you hear about this solution? Just curious.
jgr208 said:
Today I was surfing the web and the phone locked up and restarted itself. Kept getting to the android screen with the red yellow and blue symbols then restarting. Left the phone alone to get back to work then the phone restarted finally went to use the phone and after about 3 mins froze up again. Now the phone won't get past the Google boot screen and if I want to try and power the phone on the power button has to be pressed in about 30secs to a minute of two.
Also i can't get into recovery mode reliably since if I select recovery the phone again freezes at the Google screen on reboot and never gets to recovery 9 out of 10 times other times I can get to recovery and then phone will then crash while in recovery or will allow me to use recovery long enough to wipe the cache and factory reset which neither has worked.
While Plugged into a charger and just sits there nothing on screen just a black screen.
Phone is on latest android unrooted and locked.
Click to expand...
Click to collapse
do RMA
PiousInquisitor said:
What is this supposed to do? Where did you hear about this solution? Just curious.
Click to expand...
Click to collapse
read it on the nexus help forums i think. I was about to RMA the phone, so I'm glad i didn't have to. give it a try
2x4 said:
read it on the nexus help forums i think. I was about to RMA the phone, so I'm glad i didn't have to. give it a try
Click to expand...
Click to collapse
I don't have any issues. I was just curious. I've just never heard of a fix for any phone that requires a button press for more that like 30 seconds.
So what is the expected outcome? Does the phone just reboot and simply function correctly? Do you have a link to the forum post you read this in?
PiousInquisitor said:
I don't have any issues. I was just curious. I've just never heard of a fix for any phone that requires a button press for more that like 30 seconds.
So what is the expected outcome? Does the phone just reboot and simply function correctly? Do you have a link to the forum post you read this in?
Click to expand...
Click to collapse
Sure.
Here is where I read about plugging it into a PC and then pressing the power button:
https://support.google.com/nexus/troubleshooter/3337561?hl=en#ts=3337942,3339328
That didn't work (15 seconds hold). Then I found this random post on XDA where someone said they held it for more than a minute, so i tried that.
deanb1234 said:
Same exact problem. Phone was over 80% charged. Picked it up off of my desk at work to check the time and nothing. Just a brick.
Update*** I hooked the thing to power and nothing. So I just sat here at my desk for several minutes holding down the power button and the damn thing finally came back on. But I had to hold it for a very very long time, not the normal 10-30 seconds like it should take to do a hard power off. I'm talking minutes.
Click to expand...
Click to collapse
not sure why this worked, but it did. probably held it for 45s to 1m and it booted normally after that. honestly not sure what happened or why this worked.
2x4 said:
Sure.
Here is where I read about plugging it into a PC and then pressing the power button:
https://support.google.com/nexus/troubleshooter/3337561?hl=en#ts=3337942,3339328
That didn't work (15 seconds hold). Then I found this random post on XDA where someone said they held it for more than a minute, so i tried that.
not sure why this worked, but it did. probably held it for 45s to 1m and it booted normally after that. honestly not sure what happened or why this worked.
Click to expand...
Click to collapse
I'm glad my old post helped! Just an update though, it did that a few more times and then eventually I had to have it RMA'ed as no amount of time would make it boot.
deanb1234 said:
I'm glad my old post helped! Just an update though, it did that a few more times and then eventually I had to have it RMA'ed as no amount of time would make it boot.
Click to expand...
Click to collapse
haha dang, i hope the Nexus 6P it helped me boot doesn't have this issue any more...
Apayah said:
do RMA
Click to expand...
Click to collapse
Already did. Trying any last ditch efforts to revive the phone oh well it was a good phone.
deanb1234 said:
I'm glad my old post helped! Just an update though, it did that a few more times and then eventually I had to have it RMA'ed as no amount of time would make it boot.
Click to expand...
Click to collapse
Yup same here. It can get to the boot menu but recovery only works 1/10 times and can't ever get through 54% of the boot log until it freezes and crashes.
jgr208 said:
Yup same here. It can get to the boot menu but recovery only works 1/10 times and can't ever get through 54% of the boot log until it freezes and crashes.
Click to expand...
Click to collapse
Sounds like its time to RMA that bugger. Bummer.
PiousInquisitor said:
Sounds like its time to RMA that bugger. Bummer.
Click to expand...
Click to collapse
Yup new one is getting here today. Anyways, before old one is sent off I am curious to see if the battery is even charging when I connect to the charger. Anyone know if I can use a multi-meter to check this?
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.
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.
I have an idol 4s and last night before bed, around 11:30pm, it decided it was a good time to windows update. I looked over and I saw the reboot and the gear icon, so although I knew I had about 50% battery I plugged it in and continued to read my book while waiting for it to finish.... except after the progress bar got to the end my phone never turned back on.
Despite several attempts at holding the power button to get it to come on, or plugging and unpluggin the power , all I get is the White Alcatel Idol4S boot screen, followed by the pink TMobile Logo.
Then, coincidentally as I'm writing this I plug it in again (coincidentally into my pc at work if that makes any difference) and it finally gets passed the windows logo and it shows the message at the top something about finishing up or whatever.
But as I recall, this happened on the last update, whenever that was too. Any idea what the heck is going on? Has this happened to anyone else?
RobbieRobski said:
I have an idol 4s and last night before bed, around 11:30pm, it decided it was a good time to windows update. I looked over and I saw the reboot and the gear icon, so although I knew I had about 50% battery I plugged it in and continued to read my book while waiting for it to finish.... except after the progress bar got to the end my phone never turned back on.
Despite several attempts at holding the power button to get it to come on, or plugging and unpluggin the power , all I get is the White Alcatel Idol4S boot screen, followed by the pink TMobile Logo.
Then, coincidentally as I'm writing this I plug it in again (coincidentally into my pc at work if that makes any difference) and it finally gets passed the windows logo and it shows the message at the top something about finishing up or whatever.
But as I recall, this happened on the last update, whenever that was too. Any idea what the heck is going on? Has this happened to anyone else?
Click to expand...
Click to collapse
I cannot tell much from what you are describing, but my best advice is to let it do what it needs to do and finish.
Just plug it in and leave it alone. Possibly you interrupted the update/upgrade process, but who knows? Unless it hangs there for hours and hours I try to never touch my windows phones to force a soft reset unless I absolutely have to.
Yeah, so it happened again last night. Just as I was going to bed, I saw the black and white screen with the gears rotating, so I just plugged the phone into power and went to bed... but making sure to turn on my other device so I'd atleast have an alarm to wake up to. 8 hours later nothing. If I plug in power or unplug power, I'll see the tmobile splash screen and then nothing else.
[edit] Not sure how relevant this is. But when I plug it in to power. The white led near the camera turns on as usual. But after a while it turns off, which leads me to believe that the device is literally turned off because as I recall, genreally speaking, it is not possible to plug in a windows phone device and not have it charge. What makes it interesting though is that even though the led is turned off, I still see the device in "This PC" when it is connected. I just can't browse the device storage of course. So as soon as I disconnect, it is not visible on my windows 10 pc until I plug it in again. I finally long pressed the power button, and unlike earlier when I would just remove and reconnect usb power, this time, the White Alcatel/windows 10 branding showed up, THEN the pink tmobile logo. And finally it booted up.
Mine's been doing the same since the start of the year... I have to keep rebooting till it finally "works" again... takes about 45-60mins of rebooting.