I bought the Amazfit Pace Model A1612, 1 week ago. Everything was perfect.
Today when going for a run, the watch got stuck when I pressed the 'Run' activity.
It stayed like this for 5 minutes before I decided to turn it off by holding the power button.
It then turned off and now seems completely dead. It doesn't turn on, even when connected to the charger.
It had 40% battery when this happened.
Firmware version was 1.3.3a
Help?
guy1243 said:
I bought the Amazfit Pace Model A1612, 1 week ago. Everything was perfect.
Today when going for a run, the watch got stuck when I pressed the 'Run' activity.
It stayed like this for 5 minutes before I decided to turn it off by holding the power button.
It then turned off and now seems completely dead. It doesn't turn on, even when connected to the charger.
It had 40% battery when this happened.
Firmware version was 1.3.3a
Help?
Click to expand...
Click to collapse
Did you try connecting it to a PC/Mac to see if it is recognized? somewhere here in XDA there was method to go into fastboot manually.
madtech360 said:
Did you try connecting it to a PC/Mac to see if it is recognized? somewhere here in XDA there was method to go into fastboot manually.
Click to expand...
Click to collapse
Yes I did. The PC doesn't even detect that it is connected.
The fastboot method requires the watch to first turn on, but it doesn't.
I also tried cleaning the contacts, which I believe are not the problem, as this is a completely new watch.
Had the same problem after a month
My amazfit is got stuck on this morning and tried to shutdown but nothing worked then after sometime it seems completely off and no response by charging, connecting to pc...nothing... Please give me a solution... Thanks in advance,.
Amazafit pace dead
My amazfit pace is dead after 05 days. It got stuck during alarm in the morning. Eventually had to shut down. Now its not switching ON at all. Not even being detected as usb on laptop/mac. Please help me.
Some users reported that after cleaning the connector pins in both the watch and the charging cradle fixed it... Specially if you have used it with sweat or get mildly wet, the pins may get dirty or even corroded. There is a page on Amazfit official website with pics about how to clean it: use a toothpick and/or brush. Good luck.
I have same problem. USB Device is not detected by the computer. Amazfit does not boot at all, does not respond in any way. Completely brick.
---------- Post added at 08:28 PM ---------- Previous post was at 08:00 PM ----------
Oh, I've got some connectivity with the usb device:
Code:
➜ ~ sudo lsusb -d a108:4785 -v
Bus 003 Device 009: ID a108:4785
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0xa108
idProduct 0x4785
bcdDevice 1.00
iManufacturer 1 Ingenic
iProduct 2 JZ4785 USB Boot Device
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
solution found: https://forum.xda-developers.com/showpost.php?p=74556165&postcount=83
Related
Hi, I had a very strange problem with my XDA(T-mobile pocket pc). It will shut off all the sudden by the itself and I can't power it up by doing anything.( softreset, hardreset, softreset while hold down the power button etc... ) the Status led and the screen is keep off. But as soon as I put it back to the craddle, It starts up just as I did a hardreset on it. Everything in the memory is losted, but the pda seems working fine and the battery shows at least 80%. I can then use it for hours without any problem. After couple days, this whole thing will happen to me again. :evil: Can anyone please please help me on this if you have any infomation for this problem.
My question is Is there a fuse or something inside the XDA will cause this to happen? It seems the battery is fine. After I put back to the craddle (external power), I used it for hours without any problem.
By the way, It doesn't seems like a software issue. I tried all different ROM. From old WM2002, special edition, to WM2003 and WM2003/SE(cooked ROM). Same problem. I tried unload a lot of problem programs as SBP pocketplus, wisebar, no luck at all. I don't know what to do next. Can some on Please help me? Thank You so much for reading my post.
Thanks,
sam
Status follow up
Hi, I just did a Bootloader test on the battery.
Off the external power ( on battery)
Battery Test
Charge Status
AC OUT
Main Voltage:
0x0261 --> the number is keep going down????
Ext. Voltage:
0x0000
Chg. Voltage:
0x0000
VOS: FFFF
ROB: 0272
When I plug it into the craddle ( on external power)
Battery TEST
Charge Status
ERROR !!
Main Voltage:
0x0261
Ext. Voltage:
0x0000
chg. Voltage:
0x0000
VOS: FFFF
ROB: 0272
Can someone please help me and let me know what this means. I know the craddle is work because I tried on 2 different craddles and same result. when it's on battery, why the main voltage is keep going down?? Is that mean the battery is no good? Please help me.
Thank You so much for everyone read my post.
Thanks
sam
You may have an internal protection fuse blown.
I have this exact same problem.Did you fix it?
Please inform me if any one of You fixed this error. I have the same.
I have the exact same problem, I have 2 batteries and two cradles. The problem still exists with every combination, so therefore I can only thinks it's a hardware problem. I've upgraded the software, still the same. How do you do a bootloader test on the battery?
I have the exact same problem, I have 2 batteries and two cradles. The problem still exists with every combination, so therefore I can only thinks it's a hardware problem. I've upgraded the software, still the same. How do you do a bootloader test on the battery?
so i installed my unit this week and i was so happy that it fullfilled all my needs.
Now it have started to freak out. after a few minutes after startup (between 1 - 10 minutes) it just shuts down,
i need to restart my tv and the system boots up from the beggining.
I have AC adapter 5v / 2A so that should not be the problem.
I tried to factory lashing the device twice, and upgrade to last firware but it does not improve at all.
the device continue to crash minutes from starting .
what can i do ??
As per subject: My son's YP-GS1CB as of lately fails to boot. When I connect it with a cable to a computer, after a while the screen flickers, then the screen goes black. I have seen this Samsung related thread: Screen flickering and phone turning off? READ THIS!. I can't say that the battery bulges, but still, the charging behaviour of the devices has been weird in the past: The first 50% took just a minute or so and the rest took much longer, i.e. the time you would expect for charging. Also, it has been crashing relatively often.
When I connect the device to my computer running Linux, the system log says:
Apr 25 12:49:19 erwin kernel: usb 7-1: new high-speed USB device number 16 using ehci-pci
Apr 25 12:49:19 erwin kernel: usb 7-1: unable to get BOS descriptor
Apr 25 12:49:19 erwin mtp-probe[2164]: checking bus 7, device 16: "/sys/devices/pci0000:00/0000:00:1d.7/usb7/7-1"
Apr 25 12:49:19 erwin mtp-probe[2164]: bus: 7, device: 16 was not an MTP device
So, could replacing the battery be a solution? Just thought I'd ask here before actually ordering one.
Thanks a lot in advance for any comments!
yahya69 said:
As per subject: My son's YP-GS1CB as of lately fails to boot. When I connect it with a cable to a computer, after a while the screen flickers, then the screen goes black. I have seen this Samsung related thread: Screen flickering and phone turning off? READ THIS!. I can't say that the battery bulges, but still, the charging behaviour of the devices has been weird in the past: The first 50% took just a minute or so and the rest took much longer, i.e. the time you would expect for charging. Also, it has been crashing relatively often.
When I connect the device to my computer running Linux, the system log says:
Apr 25 12:49:19 erwin kernel: usb 7-1: new high-speed USB device number 16 using ehci-pci
Apr 25 12:49:19 erwin kernel: usb 7-1: unable to get BOS descriptor
Apr 25 12:49:19 erwin mtp-probe[2164]: checking bus 7, device 16: "/sys/devices/pci0000:00/0000:00:1d.7/usb7/7-1"
Apr 25 12:49:19 erwin mtp-probe[2164]: bus: 7, device: 16 was not an MTP device
So, could replacing the battery be a solution? Just thought I'd ask here before actually ordering one.
Thanks a lot in advance for any comments!
Click to expand...
Click to collapse
I have bad news to tell you, however before i tell it to you i will give a disclaimer. I AM NOT AN EXPERT, I JUST KNOW A BIT ABOUT HOW BATTERIES SHOULD WORK AND HOW THESE DEVICES SHOULD WORK. (In caps just to grab your attention and prove as an effective disclaimer, not meant as yelling.) now that that is out of the way, the bad news i have to give you is that in my opinion, it is not the battery that is your problem. however to fully test this theory try fully charging the battery and test it with a voltmeter. if the meter reads just above spec when the battery is at 100%, then it is the device, if it isnt, try replacing the battery.
also, are you sure that the device is in mtp mode when syncing it with the computer. and if you mean crashing by restarting often, then yeah they do that and it is annoying but i haven't found a solution to fixing that problem.
I hope this info gives you some help and new things to try.
also, that fourm you sited is for a phone, this device is very different. dont expect what you read for one device is true for another.
henk5066 said:
I have bad news to tell you, however before i tell it to you i will give a disclaimer. I AM NOT AN EXPERT, I JUST KNOW A BIT ABOUT HOW BATTERIES SHOULD WORK AND HOW THESE DEVICES SHOULD WORK. (In caps just to grab your attention and prove as an effective disclaimer, not meant as yelling.) now that that is out of the way, the bad news i have to give you is that in my opinion, it is not the battery that is your problem. however to fully test this theory try fully charging the battery and test it with a voltmeter. if the meter reads just above spec when the battery is at 100%, then it is the device, if it isnt, try replacing the battery.
also, are you sure that the device is in mtp mode when syncing it with the computer. and if you mean crashing by restarting often, then yeah they do that and it is annoying but i haven't found a solution to fixing that problem.
I hope this info gives you some help and new things to try.
also, that fourm you sited is for a phone, this device is very different. dont expect what you read for one device is true for another.
Click to expand...
Click to collapse
Thank you for your message. Seems you were right: A replacement battery didn't help, and I had to send the device in for repair, where the mainboard was replaced. I was still within warranty, though, so except from very minor data loss, no harm resulted....
I have an 2 years old phone Samsung Galaxy Young Duos GT-S6312.
It was running Jelly Bean. It sometimes used to notify me on its titlebar that the internal memory is nearly full. Everything else was fine.
Suddenly one day, I saw the phone was switched off. I thought battery dead. So plugged into power, but no charging symbol came. Although I felt that there was some other problem, I deliberately kept it plugged for nearly one day. But nothing happened. I can't access even the recovery mode or the download mode. When I pressed the power button or shake the phone holding the power button, only sometimes (not always) it would vibrate 3-6 times. But nothing on screen. This happened for nearly 1 week.
I tried to connect the phone with Kies, Odin. None of these detected it. Only sometime, when the phone vibrated as mentioned above, the enumeration sound came twice (one for connection and another disconnection) with a gap of < 1 sec.
I visited local repairing shops. Someone told I have to go to Samsung Service Center for ROM flashing. Someone suggested the power IC is damaged, it need to be replaced. Then they said something else also could be the problem. No one could tell anything with confidence. One person cleaned the whole circuits using some oily material. Finally, I went to Samsung Service Center. One lady checked the phone for nearly 1 minute and told the motherboard has to be changed, some power fluctuation caused this damage. It will take around $40 to replace the motherboard. I decided not to do it.
Now, after coming to home, when I pressed the power+VolUP+Home, shook the phone, all of a sudden, some display came on screen, i.e.
RAMDUMP
Mode (ARM9 mode).
When I press the volDown button, it shows the following:
fsa reset!!
fsa init!!
FSA INFO
cont = 0x1e
int1 = 0x01 int2 = 0x00
dtype1 = 0x04 dtype2 = 0x00
manual1 = 0x00 manual2 = 0x00
the same thing shows again when I again press the VolDown button. Pressing and holding the power button switches off the phone. Pressing Power+VolUP+Home button and shaking does not always bring up the RAMDUMP screen. Only sometimes, it shows the RAMDUMP screen. When the screen comes, if I connect it to laptop, the device manager detects it. If I open Kies, it shows "connecting" forever. If I open Odin, it detects the device. If I try to flash the ROM, it get stucked forever at "setupConnection".
I am not able to access download mode or any other thing except the RAMDUMP screen.
My question is, is it possible that the motherboard is really damaged as the Samsung Service Center lady told? Or at that time, the lady could not access even the RAMDUMP mode on screen, that's why she told that motherboard is damaged?
Hi,
My friend gave me his Honor 9 which was damaged by water (snow).
Phone was dead but after cleaning it and drying and connecting to USB I can see blue LED lit where the earpiece is. The battery is dead. Now: is there any hope for the phone, maybe connecting new battery could bring it to life? I'm not sure if I should spend more time playing with it.
Some additional info: when connected to USB it draws 180 mA, trying to power it through battery connector doesn't do anything. When power button is pressed for ~8 seconds current slightly increases (0,5 s) then goes back to 180 mA - I suspect the reset circuitry or even CPU is alive. LCD is not showing anything. Telephone is not detected on USB port.
Thanks for any tips.
L.
No hope!
Unfortunately no
oifjasofhoiadfkjhkdfhhhhd said:
Hi,
My friend gave me his Honor 9 which was damaged by water (snow).
Phone was dead but after cleaning it and drying and connecting to USB I can see blue LED lit where the earpiece is. The battery is dead. Now: is there any hope for the phone, maybe connecting new battery could bring it to life? I'm not sure if I should spend more time playing with it.
Some additional info: when connected to USB it draws 180 mA, trying to power it through battery connector doesn't do anything. When power button is pressed for ~8 seconds current slightly increases (0,5 s) then goes back to 180 mA - I suspect the reset circuitry or even CPU is alive. LCD is not showing anything. Telephone is not detected on USB port.
Thanks for any tips.
L.
Click to expand...
Click to collapse
There is none unfortunately..