Moto360 Sport 2nd gen -- boot loop - Moto 360

Hello all,
Got a bricked Moto360 Sport after a failed OTA update. It's in a boot loop. No logos shown, can just see the backlight turning on, one vibration, a few seconds later it reboots and repeats ad infinitum.
Are there hidden USB contacts like in 1st gen? Any way I can put it in fastboot and revive it with a proper cable?
If I try to enter the bootloader, it vibrates twice as expected, but only shows me a black screen and the backlight stays on.
Any ideas?

I have the same problem you describe in your post. I am just wondering if you were were able to get pass the boot loop

I have the same problem you describe in your post. I am just wondering if you were were able to get pass the boot loop
Click to expand...
Click to collapse
Not really. I gave up on it.
I did dismantle it completely to try and find USB contacts on the mainboard like the 1st gen. There are none.
I later found out that a lot of people had the same problem and Motorola was replacing their units under warranty (mine wasn't under warranty anymore). They silently withdrew the Moto360 from the stores just a little later.

Related

[Q] Stock KF stuck in boot loop - Win7 PC doesn't recognize KF

After searching and reading many threads and trying several "fixes", I think my last resort is this post (at least before I try Firekit or similar). I hope I didn't miss the one thread that has my answer.
Background:
Using Win7 64 bit
KF 1st gen (I believe)
Completely stock
Using Amazon KF HD charger and USB cable Amazon supplied when similar issue happened with our other KF (that new charger fixed that one)
Symptoms:
While plugged into the charger the green light will appear and a few seconds later we'll get the "KINDLE FIRE" logo on screen, sometimes it's animated and sometimes not. Sometimes the logo appears for about 5 seconds and other times about 30 seconds. When the logo appears the screen back-light first starts out low and then after a second or so it will brighten until the logo disappears and the KF appears to turn off, at least until some seconds later the green power light will come on and the process starts all over and keeps repeating. On occasion during the cyclic boot process I have seen the slide lock screen which was unresponsive and once I saw the screen with the KF device name, time, WiFi status, batt level (and no I didn't notice), etc. Lately I haven't seen either of those screens again, just the logo or nothing.
I've downloaded the Android SDK and installed the drivers but when I plug the KF into any of my USB ports the KF is not recognized. So if I can't get the PC to recognize the KF I can't go any further with trying to restore to factory default using TWRP or similar.
So my question is does anyone have something else I/we can try before moving on to Firekit? Thanks to all for your time and attention. BTW Amazon offered to sell me a new KFHD for $129 but I just don't have that in my budget right now so your help is much appreciated.
hiltoncp said:
After searching and reading many threads and trying several "fixes", I think my last resort is this post (at least before I try Firekit or similar). I hope I didn't miss the one thread that has my answer.
Background:
Using Win7 64 bit
KF 1st gen (I believe)
Completely stock
Using Amazon KF HD charger and USB cable Amazon supplied when similar issue happened with our other KF (that new charger fixed that one)
Symptoms:
While plugged into the charger the green light will appear and a few seconds later we'll get the "KINDLE FIRE" logo on screen, sometimes it's animated and sometimes not. Sometimes the logo appears for about 5 seconds and other times about 30 seconds. When the logo appears the screen back-light first starts out low and then after a second or so it will brighten until the logo disappears and the KF appears to turn off, at least until some seconds later the green power light will come on and the process starts all over and keeps repeating. On occasion during the cyclic boot process I have seen the slide lock screen which was unresponsive and once I saw the screen with the KF device name, time, WiFi status, batt level (and no I didn't notice), etc. Lately I haven't seen either of those screens again, just the logo or nothing.
I've downloaded the Android SDK and installed the drivers but when I plug the KF into any of my USB ports the KF is not recognized. So if I can't get the PC to recognize the KF I can't go any further with trying to restore to factory default using TWRP or similar.
So my question is does anyone have something else I/we can try before moving on to Firekit? Thanks to all for your time and attention. BTW Amazon offered to sell me a new KFHD for $129 but I just don't have that in my budget right now so your help is much appreciated.
Click to expand...
Click to collapse
You need a factory cable
KF Factory Cable
soupmagnet said:
You need a factory cable
Click to expand...
Click to collapse
I appreciate the quick reply. So my follow-up is to say I'm using the USB cable that came with the Amazon charger they sent when having problems with our other KF. Is that not a "factory" cable? If not, do you have any idea if this one would work: ebay.com/itm/like/271275399661?lpid=82 ??? Or do I need to spend $17 on this one: amazon.com/Factory-Amazon-Kindle-Motorola-Tablets/dp/B00BPDH4G4 ???
Thanks again.
hiltoncp said:
I appreciate the quick reply. So my follow-up is to say I'm using the USB cable that came with the Amazon charger they sent when having problems with our other KF. Is that not a "factory" cable? If not, do you have any idea if this one would work: ebay.com/itm/like/271275399661?lpid=82 ??? Or do I need to spend $17 on this one: amazon.com/Factory-Amazon-Kindle-Motorola-Tablets/dp/B00BPDH4G4 ???
Thanks again.
Click to expand...
Click to collapse
Yes 'factory' as in the one they use at OEM to install software.
Build Your own factory Cable is also an option if you can solder tiny things.

Stuck on initial boot screen

My wife and I bought my father-in-law a Fire TV which worked fine for some time. Then he brought it to my house because it wasn't working any more. I don't know what he did, but all it does is hang at the initial boot screen (black screen, white Amazon logo). Amazon has sent us a replacement Fire TV, but they let me keep the brick. Is there any way to recover this Fire TV? I've read through some of the threads. Tried using a keyboard to enter recovery (didn't work). Haven't tried adb (I don't have a USB-A to USB-A cable).
Thanks!
same issue
i hadn't used my fire tv for a couple months but was working flawlessly the last time I did use it and now no matter what tv I try to connect it to or how many hdmi cables I tried I can't get my fire tv to boot past the initial boot screen of the white Amazon logo it don't make it to the fire tv logo or any other screen it's just a black screen and screens all say no signal. I had rooted it back before I stopped using it with towel root and had adb enabled but after I boot it and it goes past the Amazon logo to the black screen the logo the led on the box is white then starts blinking then turns an amber color and sorta pulses or blinks differently than the while led blinked. Any help would b much appreciated I have been searching all over several forums and websites for days and nobody seems like they r having this issue so I'm totally lost
Stuck on Amazon Logo right out of the box/new
ryanrickard85 said:
i hadn't used my fire tv for a couple months but was working flawlessly the last time I did use it and now no matter what tv I try to connect it to or how many hdmi cables I tried I can't get my fire tv to boot past the initial boot screen of the white Amazon logo it don't make it to the fire tv logo or any other screen it's just a black screen and screens all say no signal. I had rooted it back before I stopped using it with towel root and had adb enabled but after I boot it and it goes past the Amazon logo to the black screen the logo the led on the box is white then starts blinking then turns an amber color and sorta pulses or blinks differently than the while led blinked. Any help would b much appreciated I have been searching all over several forums and websites for days and nobody seems like they r having this issue so I'm totally lost
Click to expand...
Click to collapse
Hi, were you able to fix it, I have same issue, except mine did it right out of the box, brand new, first time plugging it in. any help will be appreciate it.
Mike Power

[Q] New AFTV stuck on amazon logo but still adb access.

Hello,
Got an AFTV at staple the other day. I tried to follow the aftvnews guide "How to setup a new AFTV...".
Apparently my AFTV was pretty old since the initial unplug/plug trick did not work and the box was always stuk on waiting to download the update. I finally let the update run through and ended up with Firmware 51.1.0.2_user_510058520.
After that I tried to root the AFTV. For this I used adbFire. I was able to connect to the box (no internet connection at that time) and click on the Towelroot option. I did click on "Make it ra1n" and wait for a very long time. I never saw any message indicating that it succeded or failed. With the remote I ended up going back to the previous menu. I tried to install SuperSu but that did not work. Su was not installed. After rebooting the box, I get the back and white Amazon logo and then the screen goes black. The TV shows the selected input as if the AFTV is not sending any signal. I tried to plug the internet cable (with the 2 domains blocked) and the AFTV finally goes from the Orange blicking led to the Blue one but it's still stuck after the amazon back and white logo. I did try the ALT-I-PrntScr (which had worked previously when I was trying to prevent the update to install, I managed to get into recovery and do a factory reset ,so I know the keyboard itself is OK). But this time ALT-I-PrntScr only get the box to restart and brings me back to the Amazon black and white logo that disappear after a minute.
Nevertheless, I can still access the box from an adb shell, adbFire can connect to the AFTV. But since I no longer see any menu on the screen I can't attempt to reroot from adb fire.
A reboot recovery does not work as it's not authorized.
su command is not found , so it would confirm supersu did not install (properly). What's weird though is that if I do a ps, I see a process "u0_a1 6199 328 476352 18640 ffffffff 00000000 S eu.chainfire.supersu"
Any idea how I can unstuck the box ?
Thank you.
Some info for people in the same situation, the issue was that Towelroot needs internet access to complete.
i have exactly the same situation here. system doing an update and the power got cut off and viola. Welcome white amazon logo and pulsing white and orange indicator light. Tried all the possible ways found on the forum and net but no joy. Now its sitting on my drawer and hoping i can still find a way to make it alive.
DhiJay23 said:
i have exactly the same situation here. system doing an update and the power got cut off and viola. Welcome white amazon logo and pulsing white and orange indicator light. Tried all the possible ways found on the forum and net but no joy. Now its sitting on my drawer and hoping i can still find a way to make it alive.
Click to expand...
Click to collapse
I have the same exact issue right now, probably that same update yours downloaded from 2 weeks ago:
https://forum.xda-developers.com/fire-tv/general/fire-tv-stuck-amazon-logo-adb-t3809305
This guy had the same problem too, and he has a big list of things to try, none of which worked for me:
https://forum.xda-developers.com/fire-tv/help/fire-tv-remains-stuck-amazon-firetv-t3561797
Mine's unrooted on the latest version, so I guess I can't root and reinstall rom. I'd hate to have to throw this away it's only 2 years old. I have a 5 year old Roku that still runs great.
"Perfect" timing I guess with Prime Day coming up?
Edit: couple more guys having the same issue recently, sounds like a mass bricking going on
https://forum.xda-developers.com/fire-tv/help/firetv-box-white-amazon-logo-blank-t3472867
https://forum.xda-developers.com/fire-tv/help/fire-tv-stucks-white-amazon-logo-t2889867
https://forum.xda-developers.com/showthread.php?t=2799779&page=7
DhiJay23 said:
i have exactly the same situation here. system doing an update and the power got cut off and viola. Welcome white amazon logo and pulsing white and orange indicator light. Tried all the possible ways found on the forum and net but no joy. Now its sitting on my drawer and hoping i can still find a way to make it alive.
Click to expand...
Click to collapse
I played with mine a bit more today and I was able to fix
I read somewhere that someone else was having the same issue and said it was a HDCP handshake issue and they were able to fix by plugging to a different HDMI port on the TV. I tried that and it booted up to the colorful Amazon logo, showed the home page for a sec, then went to a black screen. From here, it would flash the home screen really quick randomly every 30 secs or so, so I know it booted up and I'm on the home page, it's just not displaying correctly. I was then able to pair my remote (I unpaired before because I was using flirc), then us the remote shortcut to factory reset. Good to go after the reset.
TBH, I did not try turning it on before I swapped HDMI ports so I'm not 100% sure if switching ports really did help it boot past the white logo, or if it just happen to get fixed after some time.
Interestingly while on the colorful logo, the alt+i+printscreen trick did not work for me. So it took me longer before I could get to the factory reset.
johnusesandroid said:
I played with mine a bit more today and I was able to fix
I read somewhere that someone else was having the same issue and said it was a HDCP handshake issue and they were able to fix by plugging to a different HDMI port on the TV. I tried that and it booted up to the colorful Amazon logo, showed the home page for a sec, then went to a black screen. From here, it would flash the home screen really quick randomly every 30 secs or so, so I know it booted up and I'm on the home page, it's just not displaying correctly. I was then able to pair my remote (I unpaired before because I was using flirc), then us the remote shortcut to factory reset. Good to go after the reset.
TBH, I did not try turning it on before I swapped HDMI ports so I'm not 100% sure if switching ports really did help it boot past the white logo, or if it just happen to get fixed after some time.
Interestingly while on the colorful logo, the alt+i+printscreen trick did not work for me. So it took me longer before I could get to the factory reset.
Click to expand...
Click to collapse
I wish I had the same luck like you but i tried different tv's, all the ports availble and different HDMI cables but still no luck.
Anyone able to find a solution to fix it? or should I just throw it out?
DhiJay23 said:
Anyone able to find a solution to fix it? or should I just throw it out?
Click to expand...
Click to collapse
Sorry you weren't able to fix. Before you throw away, try contacting support. Not because they can fix it, they most probably can't. When I had problems with mine, I contacted them and they gave me a $15 credit off of a new one because I was out of warranty. This was a couple days before Prime Day so I was able to snag a new one for really cheap. Plus my old one started working again, so I now have 2 Fire TVs

Unplugged HDMI and Bricked FTV2

Hi All,
I recently unplugged my AFTV2's HMDI cable and then when replugging it, i cannot get video signal back.
I try to restart, and it doesn't get past the Amazon logo. No colour logo at all. It seems bricked form unplugging the HDMI cable?
To make things worse, this is the 3rd box I have had with this problem.
Any ideas what could be causing it? It has Firestarter and KODI installed.
Thanks
Same Here
That is interesting.
About an hour ago exchanged a 3 day old Fire TV at Best Buy for a new one because of this exact behavior. I thought it was defective. It worked for a couple of days, my kid unplugged it and re-plugged it a few times because the screen had gone black, and afterwards nothing. Booted to white logo, then went straight to black screen. I could connect to it with ADB, but it would no longer output video except for the initial white amazon logo at startup.
Also was running Firestarter and Kodi, nothing else (latest firmware, no root)
b1nuzz said:
Hi All,
I recently unplugged my AFTV2's HMDI cable and then when replugging it, i cannot get video signal back.
I try to restart, and it doesn't get past the Amazon logo. No colour logo at all. It seems bricked form unplugging the HDMI cable?
To make things worse, this is the 3rd box I have had with this problem.
Any ideas what could be causing it? It has Firestarter and KODI installed.
Thanks
Click to expand...
Click to collapse
galvanash said:
That is interesting.
About an hour ago exchanged a 3 day old Fire TV at Best Buy for a new one because of this exact behavior. I thought it was defective. It worked for a couple of days, my kid unplugged it and re-plugged it a few times because the screen had gone black, and afterwards nothing. Booted to white logo, then went straight to black screen. I could connect to it with ADB, but it would no longer output video except for the initial white amazon logo at startup.
Also was running Firestarter and Kodi, nothing else (latest firmware, no root)
Click to expand...
Click to collapse
Have you tried entering recovery and doing a factory reset?
See this thread here
I got this type of behavior and in fact it was my TV just unplug it and plug it back
My set up was originally through an amp, but I now have it plugged directly in to the TV. It makes no difference.
I only unplugged it because I was trying to solve the issue where all the blacks are crushed.
Amazon help just keep saying they are faulty and will replace them, but when I push them to try and offer a better solution as to why it keeps happening, they just tell me it won't happen again.
Dull.
gazdaman. said:
Have you tried entering recovery and doing a factory reset?
See this thread here
Click to expand...
Click to collapse
No matter how many times I try, and believe me, it's a lot of times, I cannot get it to activate recovery.
I also can't get it be seen with ADB. It's recognised on the network, but ADB can't connect.
Just to close this.
It was my AVR putting voltage down the HDMI and causing the unit to brick.
Nothing to do with the AFTV.
Sent from my iPhone using Tapatalk

Is my vanilla 2nd gen FireTV dead ?

My FireTV is stuck in boot. I get a black screen with white amazon logo (no orange colours). The white light slowly flashes on the front box, and eventually my TV eventually gets a no signal response.
The device registers the remote, (every click gives the white light comes on) but I am unable to go into recovery (Right button + Back Button). Opening up ADBLink, I am able to connect to the device by IP address, and I can reboot the device remotely and I can enter reboot recovery. When I enter reboot recovery, the FireTV reboots and in red writing I get
"Your Amazon Firetv will restart in a few minutes, and show resume normal operation, If it does not restart please unplug the power cable and plug it back in to force a restart. If you need assistance please contact support at Amazon" .
However nothing happens, and when I restart I get stuck at the white amazon logo.
I have tried 3 separate keyboards and tried ALT + Print screen, or ALT + i + Print Screen, or ALT+ Home, or ALT + i + home. None of them worked.
It has the stock OS installed (Dont know which version but assume the latest update), and the only action beyond normal operation has been the sideloading of a couple of common APKs. (No rooting, bootloader it locked). As it is out of warrrenty Amazon are little help (15% discount on next FireTV purchase).
Is there anything I can do, or is my box now a paper weight ?
If you swear that it is an unmodified device, then there seems to be a hardware defect where you can't do anything anymore, e. g. the internal eMMC memory is broken!
However, your phenomenon still sounds like a brick through a failed root attempt or rom update or something similar.
rainman74 said:
If you swear that it is an unmodified device, then there seems to be a hardware defect where you can't do anything anymore, e. g. the internal eMMC memory is broken!
However, your phenomenon still sounds like a brick through a failed root attempt or rom update or something similar.
Click to expand...
Click to collapse
Thanks for reply, it is completely unmodified . So you are probably right about it being a hardware fault.
I have a toddler who likes to play with everything (at times even pulled out the fire TV) so guessing she did something. As a last resort I am going to take it apart. Perhaps I will be lucky and see something obvious
abfmdf said:
Thanks for reply, it is completely unmodified . So you are probably right about it being a hardware fault.
I have a toddler who likes to play with everything (at times even pulled out the fire TV) so guessing she did something. As a last resort I am going to take it apart. Perhaps I will be lucky and see something obvious
Click to expand...
Click to collapse
Good luck to you! :fingers-crossed:

Categories

Resources