I just woke up to a nightmare. I reached over for my phone and i found it dead unplugged from the charger. I thought to myself... "Alright, let's begin charging it... I probably forgot to put it on the charger last night"
I plugged the phone into the charger and the phone powers on...
After it boots, i it prompts me to connect the phone to my computer... Strange...
I plug in the phone to my computer and Zune pops up with c101002e error code.
Now i did some research and it looked like my phone somehow got bricked... so i found the following link and sure enough, my error code is on the list of known troubles.
The Windows Phone Support Tool is not working on my phone, After following the steps i get the attached screenshot error.
My next step is to reflash... however. Following These instructions, I cant seem to get my phone to boot into the tricolor bootloader screen!
PLEASE HELP! Any input would be greatly appreciated!
You say "After it boots, i it prompts me..." is windows booting before the error pops up?
The phone is off... i plug the charger in, and it boots as in it turns on. Once it turns on, windows does not load. instead it's telling me to connect to computer. I connect to computer and the error appears
already tried an hard reset??
Not able to perform a hard reset... I hold down both volume bottons while the phone is off and press the power/lock button to power it on. while holding on the volume buttons... the phone just goes to the connect to computer screen.
Try taking out the battery. Leave it out for a short while then replace it & check its securely in place. Reboot & see what happens. The phone shouldn't brick when charging or sleeping. Good luck!
Sent from my HD7 using XDA Windows Phone 7 App
Might try this and see if it helps
http://answers.microsoft.com/en-us/winphone/forum/wp7-sync/windows-phone-7-error-code-c101002e/2e7cd10e-4123-46ea-844b-e3aed54eb6bd
may be the camera key is pressed down by the case and stopping it from booting
I do not have a case with the phone but i always did have a problem with that camera buttom... it does seem to be kinda pushed in... I hate this...
what is ur version???
just u can jailbreak the 7004 or 7008 by chevron...
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.
First of all, it's not my tablet, but a collegue gave it to me because I said I might be able to fix it.
But it's showing no life signs, I can't boot in any way, not download nor recovery, and when I charge it nothing happens neither. So I guess it would be hard bricked, but when I connected it via USB to my PC, I heard the windows-device-connected sound. The driver thing showed up, and it said cloverview installing. So I guess it's not hard bricked? By longpressing the power button, the windows sound let me now it disconnected, and when I pressed it again it reconnected. Could it be that the screen is just broken? But to power off the device, I normally would have to confirm it on the screen right? I tried booting blind into download mode and checked it with Odin but nothing.
But are these the normal Samsung drivers? You guys have any ideas? I saw a thread on how to unbrick it, but you have to unsolder capacitors etc. from the mainboard, and apparently the OP didn't test it out neither.
If someone has any idea that would be nice.
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.
Hi all .. I have a phone but nothing appears on the screen and when I connect the phone to the charger shows the sign of the charger until the green sign appears, which means full battery .. What do these things show? Is the screen damaged or motherboard problem ? Please Help
Try holding the power button down for 10 seconds or more, and see if there is any change. Also try power+vol up (which normally boots to bootloader) and hold for 10 seconds or more.
Jnoubileb said:
when I connect the phone to the charger shows the sign of the charger
Click to expand...
Click to collapse
You mean the charging animation on the screen, or just the LED charge light?
If it's showing the charge animation, your screen is okay. And at least have a working bootloader, as well.
redpoint73 said:
Try holding the power button down for 10 seconds or more, and see if there is any change. Also try power+vol up (which normally boots to bootloader) and hold for 10 seconds or more.
You mean the charging animation on the screen, or just the LED charge light?
If it's showing the charge animation, your screen is okay. And at least have a working bootloader, as well.
Click to expand...
Click to collapse
thanks for your replying >>
i mean the led charge light ..also when i connect my phone to laptop , all files on memory appear
Jnoubileb said:
thanks for your replying >>
i mean the led charge light ..also when i connect my phone to laptop , all files on memory appear
Click to expand...
Click to collapse
I gave another suggestion about holding the power/vol buttons. I have no idea if you tried, and if so, whether there was any change.
Reading the files on internal storage to me, means the phone is booted to OS. So I agree that it appears the phone is on, but screen is either not working, or somehow darkened all the way.
What is the history of this device, and did anything happen before the current condition? Did it just happen spontaneously, or did you drop it or try to open it to fix anything? Try to install anything? Is the phone modified at all (TWRP, root, etc.) or basically still stock? Even if it happened spontaneously, did it happen when you were using it (and if so, what were you doing exactly)? Or just picked it up and it was this way?
I try to press power button 10 sec and more and power+ vol+ nothing happened on screen just vibrate ....the problem for my phone appear without any open to phone
Jnoubileb said:
I try to press power button 10 sec and more and power+ vol+ nothing happened on screen just vibrate ....the problem for my phone appear without any open to phone
Click to expand...
Click to collapse
Do you have debugging turned on? Know how to use adb?
i think is on before the problem appear
Jnoubileb said:
i think is on before the problem appear
Click to expand...
Click to collapse
Then connect the phone to a computer, type:
adb devices
And see if your phone's ID is returned, or if there is an error or just hangs "Waiting for device".
If it returns your phone's ID, then the phone is booted to OS (or alternately, booted to custom recovery will also allow adb connection). So to me, this means the phone is on, but the screen is not working (not displaying anything) like you suggested. adb won't connect if the phone is not on (and booted to OS).
redpoint73 said:
Then connect the phone to a computer, type:
adb devices
And see if your phone's ID is returned, or if there is an error or just hangs "Waiting for device".
If it returns your phone's ID, then the phone is booted to OS (or alternately, booted to custom recovery will also allow adb connection). So to me, this means the phone is on, but the screen is not working (not displaying anything) like you suggested. adb won't connect if the phone is not on (and booted to OS).
Click to expand...
Click to collapse
the phone now on mtp mode
C:\WINDOWS\system32>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
3a55e345 unauthorized
So it looks like adb is connecting. I think it is saying "unauthorized" since the phone's screen is trying to prompt you to authorize adb commands (which you obviously can't see or respond to). But it is obtaining the device's ID code. Which by the way, is unique to your device. So I would advise to remove it from your previous post. Don't know if it is dangerous for other folks to have this, but better safe than sorry. Simply telling us that an ID code was returned, would have been sufficient.
Moral of the story, I am thinking the phone is booted to OS, just the screen is not displaying anything. Screen may be broken, as you somewhat were guessing from your top post. I suppose there is a possibility it may be some software fault. You can try to eliminate this as the cause, by possibly booting to bootloader, which should allow fastboot access, then flash a stock recovery image. Although it may be tricky without seeing the display. Since if you need to see the display, or select anything during the process (don't recall if you do or not), you are out of luck.
Although I tend to think this is a hardware issue. Screen may be malfunctioning. Or it may be as simple as a loose connector.