I have a standard SM-N700 Galaxy Gear and had it running null. All seemed fine until one night after a notification tried to come to the watch, the screen flashed white and the watch appeared to shut down. Since then, it hasn't been able to turn on for anything. Below is the steps I've taken to try to recover my smartwatch...
Tried using multiple power supplies, no response (one power supply even caused the charging dock to become a little warm)
Tried holding power for 10 seconds, no response.
Tried repeatedly holding/pressing power (I heard sometimes this can help clear a softlocked device), no response.
Opened the watch and disconnected the battery. When the watch was reconnected, it vibrated once as if it was going to turn on, but didn't do anything further. Repeated attempts at removing the battery had no response, not even a vibrate.
Tried connecting the watch to my PC, the computer beeped that a device was connected and reported that there was no driver for "sec s5pc210 test b/d". I checked and the standard Samsung USB Drivers are installed. Tried other USB cables and USB ports, either the computer gives the beep of a malfunctioning USB device, or beeps as if something connected, but then the device seems to disappear.
I've read some resources that suggest that either the watch is completely fried, or somehow during an update to Gear Manager, it corrupted or damaged the bootloader of the watch, and after the watch attempted to reboot, it failed and got stuck in the condition it is in now. Based on these resources, there's supposed to be a way using Odin to flash a proper bootloader to the device, but since it does not appear to stay connected for more than an instant, and when it does connect it appears as this "sec s5pc210 test b/d" device, the tools I've tried to flash the bootloader have failed.
I really don't want to have to replace this device. Having a Samsung watch that still runs plain Android is not something I want to give up.
Related
Ok so this will be my second post, no one replied to my first.
Will try to explain what the problem is. in as much detail as I can.
Please help me out guys !
So, tab was in debug mode, messed up using odin, trying to root, not sure what went wrong there and gave up.
Rest of the day tab worked fine.
During the night it was not turned off but left on charger, icon showing.
I listen to audio book while falling asleep
When I woke up, pressed on and nothing, black screen
Panic and frustration followed.
New charge cable, black screen
Searched internet, did the button combo's , took back off, disconnected battery, drained battery, still black screen.
Disconnected all cables inside, reconnected, black screen
Conncted to win7 pc, by holding down power and vol down, pc sees unknown device in APX mode.
Installed various drivers, all I could find that might work, installed and seen in device manager.
Followed nvflash guides, get an error usb write failed.
List devices command, nothing appears.
Installed Samsung Kies. cant connect , using different drivers also.
Odin cant see the device either. Pdanet installed, same outcome.
Also the sdk route, always no device found
I havent got new battery yet, cant afford one at the moment.
With everything I tried it always comes down to device not being seen even though it does appear in device manager.
Installed usbdevieuw software , check the properties, it does say 0mA , which is different to when I check my usb keyboard or mouse, they do have power 90mA etc. which is weird.
I have read and tried just about everything concerning my specific device. I am stuck.
No idea what to try next.
I understood that apx = download mode., which would be fine if I could see something on the tab screen. I know that normally when into download mode you have to use vol up to cross over to the right icon.
So, power + vol down... wait till its in device manager on pc, then vol up. Tried this, seeing as the screen is black I just waited a bit and then vol up, guess work actually.
Anyway, if someone has any ideas etc please let me know.
Thank You All
Try This
TabBabe said:
Ok so this will be my second post, no one replied to my first.
Will try to explain what the problem is. in as much detail as I can.
Please help me out guys !
So, tab was in debug mode, messed up using odin, trying to root, not sure what went wrong there and gave up.
Rest of the day tab worked fine.
During the night it was not turned off but left on charger, icon showing.
I listen to audio book while falling asleep
When I woke up, pressed on and nothing, black screen
Panic and frustration followed.
New charge cable, black screen
Searched internet, did the button combo's , took back off, disconnected battery, drained battery, still black screen.
Disconnected all cables inside, reconnected, black screen
Conncted to win7 pc, by holding down power and vol down, pc sees unknown device in APX mode.
Installed various drivers, all I could find that might work, installed and seen in device manager.
Followed nvflash guides, get an error usb write failed.
List devices command, nothing appears.
Installed Samsung Kies. cant connect , using different drivers also.
Odin cant see the device either. Pdanet installed, same outcome.
Also the sdk route, always no device found
I havent got new battery yet, cant afford one at the moment.
With everything I tried it always comes down to device not being seen even though it does appear in device manager.
Installed usbdevieuw software , check the properties, it does say 0mA , which is different to when I check my usb keyboard or mouse, they do have power 90mA etc. which is weird.
I have read and tried just about everything concerning my specific device. I am stuck.
No idea what to try next.
I understood that apx = download mode., which would be fine if I could see something on the tab screen. I know that normally when into download mode you have to use vol up to cross over to the right icon.
So, power + vol down... wait till its in device manager on pc, then vol up. Tried this, seeing as the screen is black I just waited a bit and then vol up, guess work actually.
Anyway, if someone has any ideas etc please let me know.
Thank You All
Click to expand...
Click to collapse
This same thing happened to me a while back...I used a program called Root With Restore by Bin4ry v18. Look it up, I think it might help you.
galaxy tab 10.1
lordhavmercy said:
This same thing happened to me a while back...I used a program called Root With Restore by Bin4ry v18. Look it up, I think it might help you.
Click to expand...
Click to collapse
Thank you !! for responding. I did as you suggested, Its cool software.
that being said, no matter what option I choose I get The system cannot find the path specified. To me that means that the tablet cannot be entered even though it does show up in device manager samsung android phone> android adb interface.
I mailed samsung help desk and got a reply saying, take it to your nearest samsung repair store. .. THEY can fix it......as I expected they would say.
Im still wondering if the battery is causing the problems. As screen is black, when on charger stays black.
However if the tab is seen on my pc, does this mean tab has power?????
I have no idea how to test the battery without replacing it.
Im guessing tab is fully bricked and if so would that explain the no battery charging icon??? and lack of any other screens lol :laugh:
Anyway, I have learnt so much from reading this forum. I admire the great work and assistence provided.
Guess my tab problem is either too easy to provide a fix for or hardly no one has a clue how to fix my tab :silly:
Please respond and help me out!!!
I am posting this update in aid of future Xperia owners:
Problem: I seemed to have experienced the infamous Xperia "Red Light of Death". Phone vibrated 3 times continuously when charged. Screen never came on. Led was only ever RED, and only came on sometimes, sometimes solid, sometimes blinking twice. Computers were not recognizing the Xperia. Neither volume UP or DOWN button presses were ever recognized by any software on either the Win 7 or Win XP installations. However, on a couple of occasions, both computers recognized there was a device on the USB when doing a reset (reset + power). This caused them to try to install drivers. But the drivers, if installed, did not successfully allow any of the software tools to recognize the phone. Nor was the phone recognized in Device Manager, when connected, even when the UP or other buttons were pressed at connection time.
I asked for assistance on 4 or 5 of the net's biggest android forums on this... none came. So I was quickly giving up hope on the Xperia, since it seemed like there was nothing else to do. It might have taken water for all I know, when it was not in my hands, and the mobo might be quiched.
Solution: The phone is charging right now, the screen and color LEDs work fine, the original system is fully intact, and I did not need to reflash a new ROM or anything. However, I'm not exactly sure how I resolved the problem. I'll go through *some* of the steps that preceded this breakthrough. The breakthrough may (or may not) be due Sony's "PC Companion". This is an older version of what Sony now calls "Xperia Companion" (which did nothing good for me, so I went with the older software). "PC Companion" was also useless to me, since it kept insisting on not working unless you allow a connection for it to update itself. But the update always failed, with no clue as to why, despite a/v & firewall disabled. I found a comment where one user said he was able to do a bit more with PCC, once internet was disabled. So I tried that, and yeah, I could at least convince PC Companion to see if it could recognize the phone once the internet was disabled. But just like Flashtools, adb, the Sony Xperia SP drivers and all the other tools, it didn't recognize the phone was plugged in. At least, not the first few times I tried it, using various button combinations. (Up, Down & Reset/Power). Finally, I got a blue light and the PC (Win XP install) started loading drivers for the device.
I'm just not sure what triggered the change. Was it a reset/power combo operation? Was it a slight shift in the motherboard or USB connector that did it? Was it due to (the THIRD install of) PC Companion, or it would have happened with other software eventually? Its hard to say. I think these things contributed to the solution: PC Companion, the reset/power combo press, and just a lot of perseverance, most importantly. (3 days working at it in my case!). If you get this same problem with your Xperia, good luck to you.
(Trust me. You'll need it).
Lent my Sony Xperia SP (C5306) to someone, and it came back in a state where it vibrates 3 times when powering on or charging (it stops vibrating after a while, then starts again). And it won't boot or show anything on the screen, and only a RED led light comes on occasionally. So now I'm stuck on trying to flash a stock ROM on a Win7 system, using Flashtool 0.9.18.6, after installing the Flashtool drivers for "Flashmode" and the SP model, and PC Companion (PC Companion didn't fully install, because it demands updating, and fails on the update -- despite no antivirus installed, and the Windows firewall set to "enable all'). So now my problem is Flashtool won't recognize the phone on the "Please connect your device into flashmode" step, when I press Volume Down before reconnecting the USB cable. I've even tried taking the battery out for a few minutes, no dice.
At a certain point, after hitting the reset button and other buttons, Windows finally recognized there was a phone connected, and automatically installed USB drivers. Yet despite this, Flashtool still wouldn't flash the ROM. I do get 1 error in red saying "ROOT: THIS BUNDLE IS NOT VALID". Presuming this refers to the ROM, I made sure it specified it was for my model (C5306) and its even from the original carrier (Bell). In any case, it still goes beyond that error and proceeds to prepare the files for flashing.
So I'm not entirely sure what's preventing Flashtool from recognizing the phone, since it could be many things. My best guess is the soft or hard brick condition its in: since you can't power down the phone properly, and removing the battery is apparently not the same thing, its not getting to the trigger point that activates Flashtool's flashing. I'm right now trying the "rubberband trick". The idea is to keep the Volume down button depressed with a rubber band, and eventually, the battery wears down and maybe Flashtool recognizes it when it bootloops. I don't get that though, since Flashtool requires you plug the phone in via USB. And if its plugged in via USB, the battery should not ever run down, since its being charged by the USB port.
The phone was rooted, and IIRC, I think my bootloader is locked, so let's assume that. Can anyone help me along on this?
A few days ago, my Sony Xperia SP also could not start up and would keep on vibrating when connected to mains powered charger or USB port of PC. I just wish to record here my experience, hoping it will help some Xperia SP owners facing similar problems.
I tried various suggestions found in various forums but without success, gave up and bought a new phone. The very next day I did a final try. I charged it for around an hour just before I sleep and disconnected it when it was still vibrating. Next morning (yesterday), I pressed the Reset button (marked "OFF" on the back of the set with back cover removed), each lasting about 8-10 seconds. I did not felt any vibration. Anyway, I proceeded to press the power button on the side. And the set turned on! The battery status was shown as 100%. I connected it to my PC just in case drained down battery would cause it to shutdown. I saw a message indicating update was available and proceeded with update which was completed successfully. I downloaded an app and transferred my contacts to my SIM card. (Doing a backup with Xperia Companion will take many hours and I am not sure my contacts could be moved to a non-Sony phone if the Xperia SP fails again later). It has been 24 hours after my SP had revived and it has behaved normally so far.
My thought on this incident is that the problem was not due to battery or some hardware inside the phone. The problem was very likely due to incomplete software updating.
Hi, yesterday my phone hangs on using apps and won't react to anything. So i have done a hard power off with power+vol up. Next i tried to start the device again and nothing The device won't start into any mode (system/bootloader/flash) and no lights etc. So i checked some threads in net and tried to plug in charger over night. Today behaviour has changed a little bit. When connecting to pc device is detected as usb device with error in getting description. This is the only reaction of the device. Again doing a hard power off etc. won't work (also no vibration).
Has anybody had same behaviour and could fix it ?
System is unlocked and was running with cm12.1.
Before you ask: pcc etc. also won't wark cause usb-connect won't work corectly.
Hey guys. I'm new here. I've been reading this forum for sometime and it has been really helpfull.
But now I really need help.
I tried to root my ZC500TG, did'nt succeed. But a lot of videos on youtube was saying that zenfone go zc500tg couldnt be rooted. So I uninstalled the root program that I was using. The problem started when a window pop-up saying "interf.sys stop working" or something like that. Then I pressed "ok" and it showed up again, sometimes the message was about another problem, like "google play services has stopped working" or "Settings has stopped working" and it goes on until I turn the phone off, restart it and a few minutes later starts all over again. The messages showed up repeatedly every time i've clicked ok, was hard even to turn the phone off.
Then I learned about fastboot and unlock OEM to see if I could solve the problem with settings or removing some malware.
I did the hard reset, install the original firmware, when the phone update to the latest version, start aaaaall over again.
now my phone stop booting, the fastboot doesnt work, I can't access any kind of command, when I plug the usb cable, the Computer try to connect with the device, but stop, and try again by itself. I plug the battery, but the screen or the led doesnt respond to charging.
What do you guys think, did I burn it or needs computer assistance to make it boot?
Please, forgive my english...
BrunoHenrique said:
now my phone stop booting, the fastboot doesnt work, I can't access any kind of command, when I plug the usb cable, the Computer try to connect with the device, but stop, and try again by itself. I plug the battery, but the screen or the led doesnt respond to charging
Click to expand...
Click to collapse
Just reconfirming your statement, your phone does not switch on at all? When you plug it into a power socket, no LED is present? The phone does not function with anything?
Aleatory YouTube videos explaining the problem and possible fixes, I don't recommend this channel, I don't know the YouTuber.
ROG2 here turns off and not power on again after gaming and charging same time (it's dead). Someone here tried one of this with success?
Change IC PM8150B
Reballing the CPU
Hello there!
I have no experience with your problem. Just going to say that from the top. I've never torn a phone down, and when hardware components need replacing that's when I usually decide I need to pick up a new phone.
I just recommend you make sure the phone you're trying to fix like this actually needs it. I've messed with my tencent rog ii quite a bit lately and I have had the phone go completely black - thinking I had thoroughly destroyed my phone, but I was able to get it running again.
It's possible that the complete "power off" that you are reporting is the phone being in EDL mode as the phone gives no indication whatsoever that it is on when in EDL mode. As a hail mary maybe you should quickly try this before tearing your phone down.
go to this guide, and download the zip file in the main post.
Repair your ROG2 phone with EDL mode，Official firmware！
Success is disgusted by some people, and will not share any files for free in the future.
forum.xda-developers.com
extract the zip, then go the the folder "qpst.win.2.7_installer_00453.2" and run "QPST.2.7.453.msi" - this installs the drivers necessary to communicate with your phone when in EDL mode (this may not be necessary, as your pc may identify a usb connection without this, but just to check 100% I'd install the drivers anyway.)
charge your phone for at least 30 minutes. just to make sure it's got juice.
use a DIFFERENT USB-C <-> USB-A cable than came with your phone (pick one up at the shop if you're not sure. ALSO plug your [charged] phone into your PC using the side USB port on the phone (Not the bottom usb port). This is because ASUS's cables don't seem to support flashing, so I'm suspicious if they'd work appropriately in this case, and because the side port is the only one that works for flashing and the like.
now open device manager (press windows key, type "device manager"). with that screen open, plug your phone in. On device manager you're hoping that a device appears under the menu "Ports (COM & LPT)" probably named something to do with Qualcomm.
if nothing shows up, unplug the usb port from the side and hold all three side buttons down for 20 seconds (vol +, vol -, and pwr) and keep an eye on the upper left side of the device where you MAY see a red light flash indicating signs of life. then plug it in again. if nothing happens unplug the phone, and hold the power button for 5 seconds, and plug it in again. if nothing happens, unplug it and try holding down just power and volume up for 20 seconds, then plug in again. If nothing happens, try power and volume down for 20 seconds, then plug in again. (you see where I'm going?) just make absolutely sure your phone has a hardware problem and can't connect to your PC in any way before performing surgery. If the device does show up under this "Ports (COM & LPT)" device it means your phone OS is thoroughly trashed. check out that same guide I linked, as well as this youtube for some ideas how to get it going again.
If your phone doesn't connect no matter what, and you're certain you've gotta get into the hardware, then I wish you the best of luck. I really wish I could be of any further assistance with regards to hardware. maybe if you do take that road let us know how it goes.
good luck!