Related
Since Monday morning, I have not been able to sync my phone (was dcd v3.0.4 when it stopped working). I have done much research and have tried many different things in an unsuccessful attempt to solve the issue.
When I plug it in, it begins charging but nothing else happens. No windows new device sound or system tray notification, no driver prompt, no windows activesync activity, nor any activesync activity on the phone (that little arrow icon on the top bar).
I have gotten this problem extremely intermittently previously but have always been able to resolve it with either a soft reset and/or a computer reboot. When that solution attempt failed, I tried moving the usb cable to a different port. I tried four or so different ports with no different results. I tried a different cable. I tried disabling advanced networking, deleting my partnerships (lost my contacts and have not yet been able to re-sync them :/), uninstalling activesync, and cleaning all the activesync files and drivers. I even launched device manager with hidden/non-present devices shown to remove the windows mobile devices (which were oddly not present, although this was after my first activesync uninstall/clean).
After not being able to get anything to respond, I thought it may be something not working properly on my workstation, so I tried similar processes of troubleshooting on my laptop with the same results.
At this point, I figured I had isolated the problem to the device, hopefully being just a software issue and not a hardware issue. At the time, I was still running rom dcd v3.0.4 with radio 3.35. I decided to flash to the newest versions in a hopeful attempt to restore my device's functionality. After flashing radio 3.39 and cooking and flashing a dcd v3.1.2 rom, I tried again with no different results.
Finally, I decided to connect it in bootloader mode, just to see what would happen (what is normal behavior for this anyway? does it get detected and drivers installed correctly?). It was detected as a usb device by my workstation but could not install drivers for it.
Needless to say, I have become rather frustrated with my device this week. I am not sure what the problem is exactly, nor what I could possibly do to fix it. I am on the verge of flashing a stock rom and *gasp* going to the Sprint store for support. Perhaps I finally dropped or shocked it one too many times this past weekend, and it does indeed have a physical issue...
Does anyone have any suggestions/ideas/thoughts? I would be very greatful for any input.
Thank you!
See this thread and see if anything in there fixes your problem.
http://forum.xda-developers.com/showthread.php?t=393918
I have been following that thread in hopes that something may prove helpful and have tried everything suggested, including attempting to clean the port (what would be best for this? anything more than just blowing into it?), trying the two Y adapters I have (emu -> emu / mini-usb & emu -> mini-usb / 2.5" stereo), running that batch script and working with the device manager (those devices were not present), and disabling advanced network functionality, all with no results.
VerusMaya said:
running that batch script and working with the device manager (those devices were not present),
Click to expand...
Click to collapse
If you've sync'd in the past then when you display hidden devices those devices should be present (at least faded). It'll be very strange if you don't see them. If not then uninstall the Mobile Device 6.1 upgrade, restart the PC and reinstall it. Then open up the device manager and watch what changes when you plug in your WinMo device.
Keystone said:
If you've sync'd in the past then when you display hidden devices those devices should be present (at least faded). It'll be very strange if you don't see them. If not then uninstall the Mobile Device 6.1 upgrade, restart the PC and reinstall it. Then open up the device manager and watch what changes when you plug in your WinMo device.
Click to expand...
Click to collapse
I also thought it quite strange that I did not see those devices at all at when I displayed hidden/non-present devices in the device manager. I definitely have sync'd on this machine many times, I typically leave it plugged in throughout the day here at work. My machine is part of a corporate domain but I do not see how anything pertaining to that would affect my devices. On my laptop (used to sync here), the devices were present in the device manager, but even after uninstalling them the phone would not be detected when I plugged it in.
When you say uninstall the mobile device 6.1 upgrade, are you talking about the vista mobile device manager? I am on XP with activesync 4.5.
Also, nothing happens when I plug the device in, not even the standard device connected notification sound. Nothing changes in the device manager, nothing is found when I rescan hardware, I even uninstalled all the usb root hub devices and rescanned for them, hoping a complete usb subsystem driver reinstall may help detect something.
I even downloaded and ran two usb tools, one free usbdeview (http://www.nirsoft.net/utils/usb_devices_view.html) which displayed and monitored all usb devices (present and non-) and drivers and a trial of a usbtrace (http://www.sysnucleus.com/) which was a usb protocol traffic capture and analysis program. I experimented with (un)plugging the phone multiple times in multiple ports with two different cables while running these programs, attempting to find something useful. Absolutely nothing at all happened in either program, which makes me believe it is something either on the phone software or hardware.
I have a feeling I may require a device swap :/
VerusMaya said:
When you say uninstall the mobile device 6.1 upgrade, are you talking about the vista mobile device manager? I am on XP with activesync 4.5.
Click to expand...
Click to collapse
Yeah, activesync then... I dunno, I'm at a loss.
Yeah me too, looks like I am going to have to flash the latest stock Sprint rom and take it in hopefully they can do something for me.
Went to sprint, it was a bad port after all, they gave me a brand new device.
VerusMaya said:
Went to sprint, it was a bad port after all, they gave me a brand new device.
Click to expand...
Click to collapse
Are you sure they gave you the brand new device? coz same thing happened to me a week ago and i went to sprint. They gave me the refurbished phone back. Physical condition of the phone is very good tho.
SptMogul said:
Are you sure they gave you the brand new device? coz same thing happened to me a week ago and i went to sprint. They gave me the refurbished phone back. Physical condition of the phone is very good tho.
Click to expand...
Click to collapse
Well I suppose I am not sure it was brand new, but it had the screen protector and the plastic stickers still on it (next to keyboard when you slide it out). I also received an additional 512MB SD card that comes with it.
Did you flash back to a sprint rom via sd card?
arcanecho said:
Did you flash back to a sprint rom via sd card?
Click to expand...
Click to collapse
Yes, I extracted the two NBH files from the latest (3.35 I believe) stock Sprint rom installer and first flashed the smaller image (bootloader/radio I think it was), and then the larger image (os) before I took it in.
The rep I dealt with at first was somewhat of a technical idiot and only served to confuse/delay matters but after I returned, I spoke to someone else and gave them permission to hard-reset, as well as mentioned I had done this multiple times as well as tried multiple computers and multiple cables, just to help them narrow down the possible source of the problem (as well as to block possible common excuses). After waiting around for half an hour or so in-store, a technician brought me a new phone and told me the port was physically bad.
All-in-all, I was quite pleased with Sprint's service and my free swap for an issueless and scratchless new device. I was afraid it was not going to be quite so easy, requiring more time and/or an insurance replacement fee. Not to mention the free 512mb sd card.
I had a similar problem, I was un able to connect to active sync but was able to charge. Everytime I would try to connect to active sync I got the "device is not recognized" error. Then someone on here suggested perhaps my USB port was messed up, sure enough I looked in the port and noticed one of the gold pins was flipped up slightly higher then the rest. My friend took a needle and adjusted the pin and it was good as new. Somehow I had lifted one of the pins.
Anyways IMHO it's good to look in there and just check if your having problems connecting, it saved me a trip to a technician and having to wait or go through reprogramming everything.
Love my phone, but I can't get it to mount to my pc. Before the latest update I was able to use easy tether and access my sd card to transfer files. After the update neither the PC nor the phone do anything when plugged in, other than charge the phone. I've only found one computer that I can mount my phone to. Has anyone else had this problem and found a solution? I've tried multiple USB cords and even HTC's support line. They seem to think Verizon's media manager is to blame, but I think it would happen with all of us if that were true.
BTW phone is completely stock.
I have the same issue.
http://forum.xda-developers.com/showthread.php?t=1546598
Not Quite The Same
My computer doesn't recognize my phone at all. My DINC worked fine on every computer I tried it on, too bad I can't get used to the smaller screen and the 3G speeds again.
What does your computer say under device manager? Might have to update drivers, or delete them and reinstall them.
Sent from my ADR6425LVW using Tapatalk
Just one entry has a problem, but my coworkers Samsung Captivate works in this PC. The other computer doesn't have any issues in Device Manager. When I try to update it the Hardware Update Wizard says that it could not find a better match for my hardware. I can't post the image yet, 8 more posts to go.
http:
//i43.tinypic.com
/2ymdeaa.jpg
I would try uninstalling and reinstalling the HTC drivers. You may also try a different USB port, if you haven't already.
CaliDerb said:
Love my phone, but I can't get it to mount to my pc. Before the latest update I was able to use easy tether and access my sd card to transfer files. After the update neither the PC nor the phone do anything when plugged in, other than charge the phone. I've only found one computer that I can mount my phone to. Has anyone else had this problem and found a solution? I've tried multiple USB cords and even HTC's support line. They seem to think Verizon's media manager is to blame, but I think it would happen with all of us if that were true.
BTW phone is completely stock.
Click to expand...
Click to collapse
Yeah I think it has to do with the Verizon bloat. My Dad's work computer won't see his phone but it sees mine just fine. We both have Rezounds, but mine obviously isn't stock like his.
Tempted to hard reset
I'm so fed up with this that I am tempted to let Verizon do a factory reset. Either it works or they'll send a refurbished phone and hopefully that will one will work. Either way one way or another its going to cost them man hours or phones. I'm fed up with the bloat and the problems it causes.
I'm posting from my Windows 7 i7 gaming rig. My Rezy is usb connected to my rig. I can navigate both my internal memory file system as well as my SD card file system from Win7.
My Rezy is locked and stock, btw. I love this phone.
First, sorry for my bad English. Hope I make myself clear enough for you to understand me.
Second, to the moderators: feel free to move this topic if I posted it on the wrong session. But as you will see reading the following, I believe that the issue I will describe is directly related with the Neatrom - correct me if I'm wrong, but I have reasons to believe that.
So, here it goes:
I have a Samsung Galaxy S2 (i9100), running XXLSJ Neatrom Lite v4.0, and this kernell: 3.0.31-Siyah-s2-v6.0b4+
In december 2012, I bought a MicroSD card (model Sandisk Ultra 32Gb class 10) to install in my i9100, and it rocks.
But 4 weeks ago, when I was playing some games on the phone, I ignored the first battery low warning messages, and kept playing to a point that the phone simply turned off. Completely. I recharged the battery and, after powering the phone on again, it showed a message saying something like "blank sdcard" or something. I had many pictures and important movies on that card, so I decided to not format it; instead, I searched for a way to fix it.
I tried to access the files from my computer - on Windows, no success; on Ubuntu, no success; on Mint, no success. Windows and Linux showed the icon representing the sdcard, but when I tried to open it under Windows, it showed a message saying "this disk is not formated. Do you want to format it?". Linux didn't show any message, and didn't opne a single window to show its content. Nothing. Nada.
Then, my cousin (a geek genius) took my card to test it on his own notebook. He made some long research on the net, and installed a software called TestDisk (http://www.cgsecurity.org/wiki/TestDisk - linux version) to try to recover the partition (or the MBR, I don't know exactly the tech name of this stuff...). He even entered on the software the number of cylinders, sectors and all that stuff to try to achieve sometuing... But after almost two hours reading tutorials, and trying hard to bring that card back to life with no success, he finally gave up, telling me to RMA the sdcard.
Then, I took the card from his hands, and put it aside, giving up too. Half an hour later, accepting the fact that my files was gone forever, I decided to try to format the card on my phone, to see if it would work after being formated. So, I put the card on the phone again, and powered the phone on... And, for my surprise, the card was back to life! For no reason, it decided to work again! With all the movies, all the pictures, all the games, everything was there, untouched!!!!
So, it worked great in the last 4 weeks, fast and nice - recording long HD movies, taking hundreds of pictures, installing huge data games, etc. It worked fine - until two days ago.
Because, two days ago, I was playing again, and again I ignored the low battery warnings, and it happened again! In the middle of the game, the battery ran out, and the phone turned off. Guess what? Yeah, after recharging it and turning it on again, there came that same message, telling me that my sdcard was blank! Again, no success trying to access it from Windows or Linux. And no geek cousin nearby...
(Of course, I had a backup of my files, created just after that first "death").
so, I sent an e-mail to my cousin, asking him about the software he used, and how it used it. He told me about that testdisk software. I downloaded the Windows version of the software, and give a try - no success. The program didn't recognize the drive letter of my "blank" sdcard, because the filesystem was simply not listed by the program. So, I went to the site, and I read that, under Linux, it was possible to force Testdisk to try to repair filesystems that was not shown in the list, by using a command line telling the software to look for the device through this mounting point (a folder inside /dev/). Linux stuff, I wont go any deep on this here.
So, I decided to restart my notebook, to boot on Linux to try that method. Guess what again? Suddenly, Windows recognized the sdcard again! I just ran the TestDisk utility, with no success - no command was used, I just ran the program, and since it didn't recognize the card, I closed the program. Nothing was done.
But, given the fact that the card was dead twice in the exact circumstantes (battery wearing completely off), and given the fact that the card came back to life after a simple run of the software TestDisk, I refuse to believe that it was a simple coincidence; I am not a geek, not a linux or android expert, nor a hardware wizzard, but my little experience tells me that it is possible that the android system locked the SDcard filesystem in a way that, after a sudden energy cut, it needed some sort of "logical shock" (made by TestDisk, even without any changes or command being called by the user, thats me).
I believe that this issue is part NeatRom's (or maybe kernell's) fault, because in stock roms, the system would close the app and close all sdcard access before turning the phone off to prevent issues like this one.
Again, I must repeat: I am not a technician, not an expert, so chances are I am wrong - very wrong. But I believe that my suspicions makes some sense, and woths to be investigated - or cleared out. And, of course, chances are that the card is deffective - and I already called RMA service from Sandisk. And I made another backup right now. But, I insist: everything is working: no movie corrupted, not a single file is corrupted... So, I still have a doubt here: was this issue cause by a deffective card, or was it cause by the sudden turn-offs?
Before you ask: no, I didn't test playing to the end of battery using another sdcard. By the way, I will never play to this point anymore. And yes, the card is still working!
Sorry for the VERY LONG POST. But I think that this testimonial may be of some value to the rom and kernell developpers.
I can honestly say i have never heard of a Rom or Kernel damaging a memory card, could be yours just developed a fault??
Galaxy s2 said:
I can honestly say i have never heard of a Rom or Kernel damaging a memory card, could be yours just developed a fault??
Click to expand...
Click to collapse
Not the rom itself, but possibly some "features" of this or any other rom related to how it handles battery. I will try to make myself as clear as possible...
I know that in stock roms it is not possible to shoot photographs using flash when battery level is under 15% - this is to prevent sudden turn-off of the phone. And I know that some roms uses some tweaks that allows the user to take pictures using flash under this 15%. This is a thing that most users can think is an improvement - but we know that it is dangerous to use battery in a not-so-controled way. The history I told on the first post is a prove of it!
So, my suspictions is that, in some way, some rom configurations (or kernell configurations) may be allowing the user to play a high-power-demanding game or app to the end of battery charge - when, instead, it should close all the apps after the first warning, and before shutting down the phone. In other words, some roms let the decision up to the user - and if the user is (like me) distracted with some game, and forgot or bypass the first warning, he becomes a victim of this own distraction, wearing all the juice without thinking about closing the apk and shuting down the phone in the correct manner.
So, the question is: are there some rom tweaks that could POSSIBLY be the reason for this kind of issue?
Hope I made myself clear now, despite my horrible "engrich"...
...it really is a quirky device. At least mine is.
The other day, I was trying to use Winamp to sync my (up-to-date, stock, rooted) phone's music playlist using a Windows 7 computer, which I had done numerous times before. Just to eliminate the obvious, yes, the computer has a recent, working version of the HTC usb drivers installed, and yes I had the phone in Settings->Connect to PC->Disk Drive mode. No matter what I did, the computer would not recognize that the phone was plugged connected to it, and likewise the phone would not show that it was connected to a computer.
I was almost out of of options, but, as a last resort, I hooked it up to my linux (ubuntu 11.04) computer, which a couple of months ago had given me symptoms that were identical. Et voila! It recognized the phone with no problems whatsoever. You savvy readers here might remember that I posted about some of my pain with the linux box back then, because I was trying to update one of the botched OTA's that had left me unable to re-root my phone. So I booted it to the version of Amon Ra that I'd had problems with back then. Again, no problem. Go figure.
I then disconnected the phone, and hooked it back up to the Windows machine: No problem. Very, very puzzling.
I did a search here some time ago, and I don't remember seeing anything like this happening to anyone else. Regardless, just to be thorough, I'm going to ask once more: Have any of you characters heard of this kind of phenomenon with a Rezound?
many thanks!
john
I dealt with almost this exact problem of the PC connection with another user. In fact I've supported the user on three devices. His issue we eventually mostly figured out was with the sdcard mounting. In that process which seems so simple of plugging in the phone when it unmounts and remounts then afterwards unmounts and remounts, it would get part of the process and not finish the other part. He ended up thinking it was a faulty device and buying a new phone then eventually saw it on the new phone (different brand different OS). He called the sdcard company because it was a high end sdcard, the tech immediately said "I'm really sorry but almost every call we have had has been for this one problem with this one card. After testing we found a faulty internal chip, so we will gladly send you a brand new card that's bigger and better."
That was his experience, the problem is there's a lot of places in the food chain that could be a hardware failure, software failure or driver issue and would mimic the symptoms fairly closely.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Thanks so much for sharing your experiences on that issue!
I have to say I thought of that some time ago, but since this mounting thing affected the internal one too, I didn't put too much energy into following up on that. I will now.
Cheers!
John
Going to take this a completely different way since I have never had the issues you describe, but had another thought...
I used to WinAmp for a long time, remember that with WinAmp if you have a WiFi network you can sync music wirelessly, it is how I did it all the time and to be honest if you have a solid WiFi network, it is faster than USB. All you really need is WinAmp on your PC and phone and a WiFi network.
acejavelin said:
All you really need is WinAmp on your PC and phone and a WiFi network.
Click to expand...
Click to collapse
And you need the winamp app installed on your phone; I'm a minimizer.
I appreciate the suggestion, but the winamp thing was only the vehicle that led to my discovery that the problems I had a few months ago connecting my phone to a computer weren't an anomaly. That experience left me with the feeling that my Linux system was somehow screwy.
Now I know that that wasn't the problem, and since I'm going to need to be able to connect reliably to a computer for adb/fastboot access as well, it motivated me to get some help figuring out why that was happening.
Cheers,
John
Hello ladies and gents,
I am trying to help my fiancee revive her completely dead Amaze. This phone, unlike my own, is completely stock. No recovery or ROM flashing or S-off etc. It's straight from Wind Mobile (though around 22 months old at this point).
What happened: Phone was low on battery, so it was left plugged in to charge. Seemed fine. Going back to it a couple hours later, and it was died, which was odd since it was plugged in. Now it does not turn on at all (no HTC or carrier splash, recovery boot [vol down + pwr] does nothing), and the LED behind the speaker does not illuminate to indicate charging (no flashing, either).
Plugged into my computer, I get the "QHSUSB_DLOAD" device identifier, but using the brickdetect.sh script from the Unbricker thread doesn't detect anything. Likely because this has nothing to do with S-off bricking, but since I found that thread via the QHS string, I figured trying to detect it was worth a shot.
I would really love to be able to revive this device. The fiancee is back in school right now, so my income is the only one. Spending several hundred dollars on a new phone is just a kick in the pants while trying to manage already frightening wedding-related expenses. :/
What I have tried:
- Tried cleaning the battery terminals (battery and phone side) on my device
- Tried charging both on USB and wall charger for several hours (no change, no LED, no boot, no recovery boot)
- At my carriers store, I tested a known-good battery in our device, same behaviour
- Tested our battery in a known-good Amaze, after after a longer initial charge (battery was completely flat), that device booted with our battery.
- Tried booting into recovery, no luck
- Tried following steps in several other XDA Amaze and Sensation threads, and didn't get anywhere.
- I've ordered a new battery and external charger, but I'm not hopeful due to the above testing
What I haven't tried:
- Because I am still trying to get my Credit Card Extended Warranty to cover repair replacement, I have not opened the insides of the device. This thread proposes removing and replacing a battery on the mobo to get it to reset itself. I have not tried this yet.
- Anything to do with JTAG. While I've flashed ROMs and such myself many times on my own devices, I've never ventured into JTAG territory before.
What I want to know:
- Primary: What else can I try to diagnose what is wrong with this Amaze, and if it is recoverable?
- Secondary: Unfortunately we have photos on the internal memory (not SD-card) that are not backed up. If the phone cannot be revived, is there any way for me to get into the internal storage to try to recover those photos? This would be more of a challenge project. We can live without the photos, though she'll be disappointed. I'll be the hero if I can get them back, even if it means destroying the device permanently.
Thanks in advance for anyone who may have suggestions. I'm heading to bed for the night, but I'll check this tomorrow and test out any theories.
Does anybody have any theories I can test out aside from some sort of hardware failure on the mainboard?
What OS are you running on your computer. Try looking for the device in Ubuntu, maybe it'll find it there.
Windows 8 and 8.1 have issues with the drivers and software.
Darin_Ram said:
What OS are you running on your computer. Try looking for the device in Ubuntu, maybe it'll find it there.
Windows 8 and 8.1 have issues with the drivers and software.
Click to expand...
Click to collapse
I'm using Windows 7 (64-bit), but I also tried using the Ubuntu 10.04 based Live CD (PHToolz?) from the Unbricking thread, and it didn't detect anything at all (tried with and without automount enabled).
Reading what you said again, I'd say that it's a manufacture defect. It could be a wide list of things actually, hard to pinpoint.
In regards to recovering your photos and other files on the phone's storage itself, I don't think you can recover it at all.
The best bet right now is to get it exchanged if it's still under warranty (I'm assuming you didn't void the warranty by unlocking bootloader, attaining S-Off or flashing any custom roms/kernels/incompatible zip files e.g. A rom meant for another phone)
If it has warranty, don't give up hope.