First, the watch stopped responding to touch and the buttons out of nowhere, but the bezel worked. Then it entered a boot loop for about 18 hours. Still, since the buttons did not work I could not break the loop. As per youtube.com instructions I tried to reset the device to fix it to no avail. Then it spontaneously would select accessibility screen reader on the Setup screen except it would read only a few words from the paragraph's selection. It did this on and off for about 3 hours. Then it entered Wireless download mode. After a short while, it turned off and is completely bricked.
I cannot de-brick it with net odin because the buttons still do not work, even though; if charging; the top button (not the power button); will show and hide the battery percentage.
I have a crazy suspicion my neighbor has something to do with this. He is an admitted sadistic psycho/sociopath (and he passes the test.. I've read 10 books on identifying psycho/sociopaths.) He is high-functioning and a genius. He has even admitted to hacking my computer. I went back into my house and my computer was, indeed, hacked.
I saw a youtube.com video where a user soldered a USB cable to the watch to connect it to his computer for Odin. Is this my only hope?
Related
Well, I think I have finally managed to kill my PDA2k. It was a late night and long story short, it got wet (but not too wet).
The next day, I plugged it into a usb power supply (car charger) and it would begin to boot (displayed the info at bottom right screen) but would fail when it tried to load the OS. I waited for a bit a re-tried a few times. Then the red light came on (top right led) and it no longer even attempts to boot. I disassembled it and made sure everything was dry and clean and it still just turns on the red light and does not attempt to boot.
So, does anyone have any other thoughts/suggestions?
I'm going to go ahead and be prepared for the worst and assume that it is in fact, done. What should I do with it? I do have an insurance policy on it (via State Farm) but I'm not sure if that is covered.
Anybody know of some cool DIY projects to make use of the parts? Or just fun ways to say "farewell" to a phone?
Well sweet moogly googly, it started working again!!! I just left it on the charger for a while and the red light went off...then I hit reset and it booted just fine!
Its like Christmas came about 15 days early...I hadn't made a backup of my data in a LONG time.
If anyone looks over my posts history, they'll see that there have been several "close calls." But I guess this is just a testament to HTC and their ability to build "resilient" hardware.
Well all is not well in PDA2K land...again.
The last post was a bit premature as it is having some serious issues. First, I cannot communicate (hear/talk) on any phone calls. I can make and receive calls fine, but no audio coming or going (despite sounds and recording working). Second, I am unable to connect via ActiveSync (or even mtty), so I can't reflash to see if that is the issue. Third, although it is becoming less frequent, the device will just power off and the red led will come on. After a few seconds the light will go off and it can be restarted. Last, the power button does not work at all. So even when it is working, there is no way to turn off the screen (without using a program).
One other related note: when you do a reset it loses the date/time.
All in all, it seems as though it is very rapidly becoming a glorified paperweight. Any ideas? If not, I'm back to deciding how to send it to "gadget heaven."
Would anyone has any use for the hardware?
Hey all,
I just installed a new digitzer on my Vivid. Everything went fine, and nothing broke as I was taking apart the phone, or putting it back together.
Now that the phone is back together, however, it is having some problems.
First off, When I try to power the phone on, it vibrates like usual, but then doesn't display anything. The phone then proceeds to enter in to a bootloop and keeps vibrating every couple moments. When plugged in to the computer, the orange light comes on for a few seconds, then turns off. Windows will not recognize the phone. All the while, the screen is completely black, and none of the lights come on for the buttons either.
The phone was working fine before replacing broken digitizer.
The phone is NOT rooted, nor has it ever been. I am running stock ICS.
have tried entering Hboot with no avail.
Any advice?
Thank you!
Can you get into any other modes? Try to get to hboot(hold down power button and volume down) while plugged into computer. Should take it to fastboot.
how long for? I tried holding down for a good 30 seconds...nothing happened other than my orange light turning off
I noticed with mine I had to go with:
Remove battery.
Replace battery
hold vol down + power
few seconds later release power
few seconds later in hboot
YMMV due to repair.
You can also try a knoppix boot disc and some tutorial to see if you can find any sign of life off the phone in dmesg.
hope this helps some.
Sounds like a loose connection. Make sure that you've correctly reconnected all internal connections. Especially the connection under the little door with the void sticker on the screw in the battery compartment. If after verifying all connections are made and proper, the problem persists, I'm sorry to say you may have physically damaged the connectors during disassembly. Please visually inspect all connections for damage. A powerful magnifying glass is recommended.
(I have successfully replaced my digitizer twice, and my LCD panel once on this phone...)
Sent from my HTC Dark Raider using XDA.
I have taken it apart twice, checked all connections, and everything is good. Phone cannot enter any boot mode, and computer still doesn't recognize it. The orange light still only stays on for a few seconds when plugged in, then turns off. The phone then proceeds to keep trying to restart itself, but the screen remains pitch black blank
idk.. get a replacement.?
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.
Apologies if this is the wrong area for this or if up to date information is available, but I can't find any solutions anywhere.
My daughter has a pre-paid Virgin HTC Desire 510 that she has had for some time, but just started acting up today. Starting from off, it boots up and goes to the home screen fine. Then 35 seconds later (I've timed it several times) it shuts down. No matter what you are doing it goes black, just as if you pulled the battery. Then it boots up again automatically and continues the same cycle indefinitely until the battery is pulled.
I've been searching for the last 3 hours and have tried every remedy I've read, from checking the battery connections, wedging a small piece of paper there to force a better connection, and trying a new battery, to booting it without the sim card, without the sd card, and without both. Makes no difference, the phone is usable for 35 seconds, then power cycles. One interesting note on this though, if I try to manually shut down the phone, as soon as I press "shut down" or even "restart phone", it instantly shuts off the same as at the 35 second mark. Instant black screen with no proper shutdown sequence.
I (and she as well) have conceded to just wiping the phone entirely to attempt to fix the problem. Only that doesn't work either. I found that in order to do a factory reset, the "fast boot" option must be turned off in the power settings. Her's is not. In the 35 seconds I have to go into the menu, I can deactivate the setting, but it always hits that 35 second mark and turns off just after I do. After rebooting (either by letting the cycle occur, or pulling the battery and booting fresh) the "fast boot" section is still valid. In fact, I even went so far as to try to move icons around, change other settings, etc. to see if anything sticks after the boot cycle and nothing does. It seems the improper shut down that occurs prevents any previous changes from being saved. In turn, this prevents the phone from doing a factory reset.
Now, I've tried the factory reset several times and it always reboots with the same normal home screen, 35 second function, then power cycle. I've also tried recovery mode as well but it just stays on a black screen with a red triangle and "!" inside until battery pull.
This is about all the information I can dig up or provide without any further insight. I will say that I'm not that comfortable with my skill at attempting anything that requires downloading and transferring any kinds of files to the phone and installing them manually, as I'm not THAT savvy when it come to things like rooting phones, etc.. So if there are ANY solutions short of "rooting", "unlocking", "bootloader", etc that I just don't know much about, please let me know.
Thanks for any and all help, I will attempt any possible solutions I am able!
Hmmm....this sounds strange. The things you described could be from a bad kernel. But you haven't tried to root it yet so that rules out the bad kernel. I think that you should reinstall the whole system using an RUU. That is your best shot at this moment. If that also doesn't resolve your issue, your only option will be to root your phone and install a custom ROM. If you have any questions, don't hesitate to ask
psycho76384 said:
Apologies if this is the wrong area for this or if up to date information is available, but I can't find any solutions anywhere.
My daughter has a pre-paid Virgin HTC Desire 510 that she has had for some time, but just started acting up today. Starting from off, it boots up and goes to the home screen fine. Then 35 seconds later (I've timed it several times) it shuts down. No matter what you are doing it goes black, just as if you pulled the battery. Then it boots up again automatically and continues the same cycle indefinitely until the battery is pulled.
I've been searching for the last 3 hours and have tried every remedy I've read, from checking the battery connections, wedging a small piece of paper there to force a better connection, and trying a new battery, to booting it without the sim card, without the sd card, and without both. Makes no difference, the phone is usable for 35 seconds, then power cycles. One interesting note on this though, if I try to manually shut down the phone, as soon as I press "shut down" or even "restart phone", it instantly shuts off the same as at the 35 second mark. Instant black screen with no proper shutdown sequence.
I (and she as well) have conceded to just wiping the phone entirely to attempt to fix the problem. Only that doesn't work either. I found that in order to do a factory reset, the "fast boot" option must be turned off in the power settings. Her's is not. In the 35 seconds I have to go into the menu, I can deactivate the setting, but it always hits that 35 second mark and turns off just after I do. After rebooting (either by letting the cycle occur, or pulling the battery and booting fresh) the "fast boot" section is still valid. In fact, I even went so far as to try to move icons around, change other settings, etc. to see if anything sticks after the boot cycle and nothing does. It seems the improper shut down that occurs prevents any previous changes from being saved. In turn, this prevents the phone from doing a factory reset.
Now, I've tried the factory reset several times and it always reboots with the same normal home screen, 35 second function, then power cycle. I've also tried recovery mode as well but it just stays on a black screen with a red triangle and "!" inside until battery pull.
This is about all the information I can dig up or provide without any further insight. I will say that I'm not that comfortable with my skill at attempting anything that requires downloading and transferring any kinds of files to the phone and installing them manually, as I'm not THAT savvy when it come to things like rooting phones, etc.. So if there are ANY solutions short of "rooting", "unlocking", "bootloader", etc that I just don't know much about, please let me know.
Thanks for any and all help, I will attempt any possible solutions I am able!
Click to expand...
Click to collapse
Has she done anything to the phones files? (deleting stuff you shouldn't?).. RUU for Virgin Mobile - Run from a Windows computer. http://dl3.htc.com/application/RUU_A11_CHL_K44_DESIRE_SENSE60_Sprint_WWE_VM_1.49.652.3_Radio_1.47.40.0224_NV_SPCS_1.08_003_release_448617_signed_2.exe
Thanks for the responses. It seems like fixing this phone would be more trouble than it's worth for me, as it wasn't an expensive phone and I have no experience rooting phones, lol! I think she has money saved up and wants a new one anyways. Thanks for taking the time help out!
My phone went to an endless bootloop after a botched attempt to install TWRP. I tried hard pressing the power button to no avail, and I can't access fastboot either. That's why I removed the back cover and disconnected the flex cable from the battery on the phone's motherboard.
Later on, I reconnected my phone's battery after my shift ended, then I tried to flash my stock rom through SP Flash Tool + bypass tool python script and it went through with a success. However, this time, my screen seems to be completely dead but my phone is still showing some signs of life (short vibration when pressing the power button, but since then it seems that it takes a few seconds more from pressing the power button to turn it on. ) I reconnected and disconnected everything to see whether or not I missed out something but the issue still persists.
The computer reads the device as "Android ADB interface" and the adb console reads it as *device id* unauthorized when I ran adb devices command. There's no notification light whenever I plug it into the charger.
Is my screen dead, or is my motherboard toast? I need to know as I don't want to spend money to buy a replacement LCD only to know that the motherboard's dead. I don't really care about the IMEI as I'm just going to use it as an authorization device for work. I can just always connect to Wi-Fi. Please advise.
One problem after another, so it seems.
Turns out I already unbricked the phone, but the thing is that my display's backlight got busted for some reason. Unless I shine a flashlight through it, I won't know what's in the screen. I'm currently on the way to get a replacement screen, and a new battery cover.
I guess this will be the last Xiaomi device that I'll ever get. This is the only time that I experienced such flimsy build quality since the LG G4.
Maybe you have destroyed a lil cable or something.