Hi all, i really appreciate if someone can getme out of this trouble. I did not have much money to build a pc. So, i managed to scavenge pc parts and build one. My specifications are,
Asus p5q mb, hd radeon 6850, xeon x5460 mod processor, ddr2 8gb ram, 600w power supply, 160 sata hard drive.
I updated bios before install the cpu and it recognize by the system. It had a problem initially, that usb ports not working. I managed to fix it by adjusting some settings.
But now it has an even bigger problem, which i cannot find a solution. Pc starts ok, and works ok. But after some time, it suddenly freezes. No usb is recognized. If i unplug my mouse and plug it back, even the mouse light is not lightning up. Then i have to restart the pc, then, sometimes it restart ok. But sometimes, it doesnt post. No beep sound coming from the motherboard. No matter how much time i restart, it does not post. Then, i have to switch of the pc from the main current supply and wait for 2 minutes and switch on. Then it starts ok. It is a must to turn off the pc from main current supply.
I checked followings,
Rams working ok, changed the cpu fan, reinstall windows, unplugged all the parts and put them in order.
Can someone plz, help me to find the culprit here. Really appreciate it.
Freezing up of Windows OS can happen anytime. Try these steps to fix the ramdomly freezing - one by one
1. Free Disk Space on your System Disk2. Check for any Damaged Hardware3. Disconnect all attached Devices4. Repair Corrupt System Files5. Uninstall Possible Incompatible Programs6. Update Device Drivers7. Perform a System Restore or a Clean Install of Windows 11
Sounds corrupted, clean up disk/files or restore could assist...
galaxys said:
Sounds corrupted, clean up disk/files or restore could assist...
Click to expand...
Click to collapse
Im doing a troubleshooting now. Lets see what is the outcome. Thank you gys.
Something is definitely going on with the hardware. First suspect the PSU,. That's a pretty old board, are the electrolytic capacitors swollen? That would cause the problems you are having. Try one of those software programs that monitor voltages and temps. One of those should give you the answer, good luck!
I have started testing one by one. just now i was doing a furmark test and the pc frozen. So, i installed vga on another motherboard and checking it now. Will see what will happen. Motherboard is pretty old. Hope it could be repaired.. But i suspect bios or the modded processor might be the culprit. I will update the results. Thank for your kind reply. Appreciate it.
Gys, does anyone have any kind of clue what to do.plz do tell me. I tested all the parts using another motherboard. Turned out, my processor was the culprit. My processor is xeon x5450 a modded processor to work in lga 775 socket. It works fine in asus p5qpl-am motherboard. But not in asus p5q. I downloaded the bios updates from the same site and Tried few Other bios updates as well downloaded from the internet. Unfortunately, no luck. What to do? Plz help me if someone know what to do. Thank you.
I think It the OS that is causing this issue. Install the fresh version of OS and see if it gets solved.
shoaibiqbal123 said:
I think It the OS that is causing this issue. Install the fresh version of OS and see if it gets solved.
Click to expand...
Click to collapse
Tried it. But no luck.
Chanixsl said:
Tried it. But no luck.
Click to expand...
Click to collapse
Thank you for kind reply
Absolutely puzzling and nondeterministic nuisances are usually hardware/electric issues (this is also why OS has nothing to do with it, and it is even unaware anything bad happened).
Putting aside that it could kind of be every component in your system, if you have USB going haywire too it's most likely your motherboard going bust (people here and here even having some anecdote).
Check the pcb for odd paths, caps or whatever I guess.
there can be many problems, the best option is to reinstall the system
Run CMD and type the command (( sfc /scannow )) This command repairs damaged files, searches for problems and records them in the log file. When finished, it will give you the path of the log file.
This second command does repairs, but when you type and execute it, restart your computer ((( chkdsk /f )))))
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.
Please don't try anything mentioned below, if you are not familiar with flashing roms and programming ! You've been warned !
The following steps had been done in 4 sets of Galaxy Tab 10.1 (from different sources), all touchscreens become unresponsive within a minute. The system is still running, volumn keys are working, orientation sensor is operational, even the clock and wifi signal is fine. The only problem is the touchscreen. All 4 devices are not rooted, brand new, fully charged, and now returned to Samsung for inspection.
WARNING !!! The following steps may cause you trouble ! I share these steps only because I think some experts here may be able to solve it ! I'm also looking for some proof, if the same problem occurs to Samsung Tab 10.1 devices in different countries.
The steps to trigger an unresponsive touchscreen :
(1). Download and install any file manager from the Market (skip if you already have).
(2). Browse to "/sys/devices/virtual/sec/sec_touch/".
(3). Select all files (excluding folders).
(4). Copy and paste to any other location that have write permission (such as sdcard). Some of the files are not allowed to be copied, so just skip it.
And then, in a short while, the touchscreen will not respond anymore.
The files mentioned in step 2, are some driver files of Atmel mxt1386 (the touchscreen hardware). It seems that users of Acer Iconia also have touchscreen issue, turned out to be using the same hardware.
I know that there are also many users that do not have any touchscreen problem. This may only because those files are not accidentally accessed yet. I'd rather hope that you have a different version of the hardware driver that does not have such problem.
I'd like to ask for help from experts and developers here. But please don't try it if you are not absolutely confident to at least restore the system. Please don't blame me if your Tab becomes un-usable.
For those who are willing to try (at your own risk), I'm much appreciated. And I'd like to say thank you to all of you. Your effort may be helping a lots of users who have this problem.
Hey idsam,
have you got any ideas how to fix touchscreen broken this way?
Im sorry, I dont get this.
To me its like saying "I removed my battery and now my device won't turn on"
So, if I dont mess around with my system files and touch screen drivers, then my touch screen will be fine?
If you mean something else, please explain
Yeah, you got wrong.
Topic starter made too complicated example. The simple description is: if you try to read files from /sys/devices/virtual/sec/sec_touch/ directory - you'll got broken touchscreen. Looks like this operation damages touchscreen firmware, though this won't happen with properly configured/written (by manufacturer) system.
So who wants to read from those files? Any software for any reason. E.g. a lot of users have bricked their devices by doing a full system scan with Dr.Web for Android antivirus.
Sorry for the complicated example. I just tried to provide as much information as I could.
Feedback from Samsung is that it need hardware replacement (which is weird due to a software issue). But when they have a lots to sell, they simply says that they don't have parts for replacement at this moment. And they confirmed that flashing rom does not recover the device.
Yes. In most cases, we won't touch those files, except using any kind of antivirus software. I don't think it is limited to one brand, unless the antivirus software doesn't scan system files at all.
Besides, I also noticed that some Tablet users talked about unresponsive touchscreen : some said it happened suddenly; some said after charging for a while; some said having a useless device when woke up in the morning. It is hard to believe that all caused by the same antivirus software, right ?
What I've mentioned in the first post, is a way to trigger the problem. There may be other causes I'm not aware of. Some experts here may be interested in this issue. But it will be quite difficult for them, if they don't know how to replicate the case. This is why I posted the steps in the first place, and hope someone can help.
idsam said:
Sorry for the complicated example. I just tried to provide as much information as I could.
Feedback from Samsung is that it need hardware replacement (which is weird due to a software issue). But when they have a lots to sell, they simply says that they don't have parts for replacement at this moment. And they confirmed that flashing rom does not recover the device.
Yes. In most cases, we won't touch those files, except using any kind of antivirus software. I don't think it is limited to one brand, unless the antivirus software doesn't scan system files at all.
Besides, I also noticed that some Tablet users talked about unresponsive touchscreen : some said it happened suddenly; some said after charging for a while; some said having a useless device when woke up in the morning. It is hard to believe that all caused by the same antivirus software, right ?
What I've mentioned in the first post, is a way to trigger the problem. There may be other causes I'm not aware of. Some experts here may be interested in this issue. But it will be quite difficult for them, if they don't know how to replicate the case. This is why I posted the steps in the first place, and hope someone can help.
Click to expand...
Click to collapse
When the touchscreen goes unresponsive, do other parts of the device still function? For example, when you hold down the power button, will the shutdown menu appear? When you rotate the device will the orientation change?
I have had an unresponsive touchscreen many many times. I'm not sure it is the same unresponsive touchscreen you talk about here. When mine goes unresponsive I can still use the power button and if I rotate the screen a few times it eventually becomes responsive again.
Yes. The power and volume up/down buttons work, orientation sensor also works as a normal device. I tried to rotate the screen, discharge and recharge the battery, but it aside for hours and tried again, nothing helps.
And it is actually confirmed by Samsung that hardware replacement is needed. They said that they tried to recover the device by flashing rom, but failed.
so I have the same problem. Quite frustrating. Not only that, I've noticed that there is a vertical 1-2 inch area from top to bottom of the screen that doesn't ever respond to touch.
I'm sending it to Samsung
Hi Idsam, I'm from Russia and have a same problem. After full scan by Dr. Web the touchscreen not responding and now I don't know what to do, beacause I've bought my Samsung in USA in Bestbuy, but now I'm at home in Russia, no warranty, no service, nothing. May be somebody can give me advise?
To be honest, it seems that Samsung doesn't have a solution yet. And probably worse, Samsung did not modify the driver at all, which means Atmel is responsible to fix the problem. No matter what, you can wait, but who knows how long it takes.
I think Best Buy has refund policy. You should discuss with them asap, as this kind of policy is normally time limited. You may consider to pay for delivery, in order to minimize your lost. If they refuse to refund for you, then you may need to contact Samsung Russia. I'm sure they know about this issue, and perhaps you may discuss with them. Still, you may need to consider to pay a little more as repair service charge.
BUT, I'm not saying you should pay more for what they've done wrong. It is only a suggestion, in order to speed up the process and at least minimize your lost.
The last option, I think, is to wait until Samsung announce a solution. If the method to fix it doesn't require hardware exchange, perhaps you may get information from Samsung and try to solve it by yourself.
As I know, when the touchscreen issue occurred, the Android system is actually still running WITHOUT problem. It means that you may still control the device by using ADB via USB. So, if Samsung can provide a patch, it may be easily fixed. I'm not sure if it is possible or not, just hope it will be as simple as that.
I think I heard to get it on hold the lock button for 10 seconds then touch the screen the it should turn bk on try it let me know if it works
Thanks for your answer. As I understood we have to wait patch from Samsung and when they provide this patch then problem can be fix without hdd replacement?
---------- Post added at 07:28 AM ---------- Previous post was at 07:23 AM ----------
oawalker said:
I think I heard to get it on hold the lock button for 10 seconds then touch the screen the it should turn bk on try it let me know if it works
Click to expand...
Click to collapse
No, it doesn't help. Only one method left - use the hammer.
oawalker said:
I think I heard to get it on hold the lock button for 10 seconds then touch the screen the it should turn bk on try it let me know if it works
Click to expand...
Click to collapse
Thanks for your suggestion, which I tried before and didn't help. Actually, I wouldn't start this thread if it is that simple. But probably too risky for anyone to try to fix this.
AlexNovoross said:
Thanks for your answer. As I understood we have to wait patch from Samsung and when they provide this patch then problem can be fix without hdd replacement?
Click to expand...
Click to collapse
I can't say if hardware replacement is needed or not. I just *HOPE* that a patch will be able to fix the problem, which should be the best news for all of us.
idsam said:
Thanks for your suggestion, which I tried before and didn't help. Actually, I wouldn't start this thread if it is that simple. But probably too risky for anyone to try to fix this.
I can't say if hardware replacement is needed or not. I just *HOPE* that a patch will be able to fix the problem, which should be the best news for all of us.
Click to expand...
Click to collapse
I hope Samsung can patch this up when they update to 3.2 if that update comes
Does this mean i Lost my Tap if that patch did't come out..
!!!???
Honestly, only Samsung can answer your question. But my steps can help you to show proof to them that it is a design flaw, and force them to admit that it is their responsibility to provide solution.
This is, unfortunately, the known issue with all mxt1386, mxt224 and qt64-blah-something touchscreens. I have wasted a week debugging my iconia and have experienced tons of butthurt. To put it simple, when an error occurs in the touchscreen controller, it does not report proper ID, but an error code instead. Some versions of drivers (like Asus one) just return -ENODEV in that case. Acer's driver was intended to handle it, but was written poorly and died in a deadlock in such an event. My solution was to comment out semaphores and other synchronization techniques and that got past the device detection and cleared error bits.
You can read more in http://forum.xda-developers.com/showthread.php?t=1143892 and try to use the drivers from iconia (the patched drivers are also uploaded and there's a link in that thread)
I have the same problem with my Galaxy Tab P1010. I can get into download and recovery mode i can move the selection using the volume button but i can't press the power to enter my selected option. I have already tried re-installing the latest available firmware for my device using ODIN 1.7. Eventually everything seems to be ok until i reach the point where you select the language. I can't select any option mainly because the touchscreen is unresponsive. All along i thought this problem is only software? Hopefully somebody can find the solution to this.
sp3dev said:
This is, unfortunately, the known issue with all mxt1386, mxt224 and qt64-blah-something touchscreens. I have wasted a week debugging my iconia and have experienced tons of butthurt. To put it simple, when an error occurs in the touchscreen controller, it does not report proper ID, but an error code instead. Some versions of drivers (like Asus one) just return -ENODEV in that case. Acer's driver was intended to handle it, but was written poorly and died in a deadlock in such an event. My solution was to comment out semaphores and other synchronization techniques and that got past the device detection and cleared error bits.
You can read more in http://forum.xda-developers.com/showthread.php?t=1143892 and try to use the drivers from iconia (the patched drivers are also uploaded and there's a link in that thread)
Click to expand...
Click to collapse
It seems that the second link is invalid. Besides, it is necessary to root the device and flash CWM recovery first, right ?
I mean, it may be a bit risky. I read your post before, but not sure if it is the same issue. If it is not, and the device is rooted, the official warranty may be voided too.
I have updated the links but the recovery image is only valid for the Iconia tablet. I mean, one could try using the attached driver sources and add them to the kernel but that will require at least flashing custom kernel. Samsung seems to be releasing a firmware update to fix this issues but people familiar with linux kernel development may try experimenting with the driver from acer.
I am trying to flash my vibrant to stock, but my laptop says usb unrecognized.This causes Odin not to detect my vibrant in download mode. I have downloaded all drivers including nexus drivers, but still same error usb unrecognized. I have then start on switching data cables including the stock data cables but the errors remain the same. I have tried on different computers and different windows, nothing working its the same errors on all computers. I have messed up by formatting everything in the Vibrant, now it boot loops to Vibrant logo. I can get into download mode normal but I cant get into CWM or any recovery mode, its probably because I have formatted the whole phone. When the phone is off, I plugged in the micro USB to the phone from the laptop, all it shows is the white lines that are in circler motions and then freezes. Weird my laptop still detects it as a USB unrecognized. As the phone is plugged in to the laptop I try taking the battery out and my phone is still on with the frozen screen of those white lines in circler Motions. Can anyone help me, or at least explain to me what the problem may be? My thoughts is that it may be a hardware problem. If so can anyone provide me some schematics on the USB portion? I hope we can bring some light on this problem. Giving it to T-Mobile is not an option. I have dealt with many problems and solved it, but this is one problem that keeps me stomp in my own tracks.
You can give a man a fish and he will eat for a day, but if you teach a man to fish, he will be able to eat for a lifetime!
Ok, so I am in a similar situation as yourself. I bought another Vibrant that was stuck on the bootloader screen. I gets into DL mode just fine, however Odin doesn't recognize it. I have uninstalled, reinstalled the drivers, used Nexus S and GNex drivers, 4 cords and 3ports and still no joy. My daily driver Vibe is like a mid-town flasher and is seen all over the place. So this leads me to believe that it is not driver/SW related but rather HW realted for me.
I think that my next step is to clean the USB ports on the phone and see if that works. If not, then I'll have to probably crack her open and clean there. I have another laptop that is using WinXP, so I might give that a try since nothing Samsung has ever been installed on it.
Keep me up to date with your findings and I will do the same with mine. Clearly I am not a noob but now this is just making me mad. Why one phone works/is seen and not the other. Common denomitator has to be HW.
Woodrube said:
Ok, so I am in a similar situation as yourself. I bought another Vibrant that was stuck on the bootloader screen. I gets into DL mode just fine, however Odin doesn't recognize it. I have uninstalled, reinstalled the drivers, used Nexus S and GNex drivers, 4 cords and 3ports and still no joy. My daily driver Vibe is like a mid-town flasher and is seen all over the place. So this leads me to believe that it is not driver/SW related but rather HW realted for me.
I think that my next step is to clean the USB ports on the phone and see if that works. If not, then I'll have to probably crack her open and clean there. I have another laptop that is using WinXP, so I might give that a try since nothing Samsung has ever been installed on it.
Keep me up to date with your findings and I will do the same with mine. Clearly I am not a noob but now this is just making me mad. Why one phone works/is seen and not the other. Common denomitator has to be HW.
Click to expand...
Click to collapse
I agree with you, it may be a HW issue. I have tried connecting other phones to my laptop and it reads it just fine, but for my vibrant no success. Im gonna go ahead and actally open it up and check on some componets, i have a feeling that it may have burnt one of the componets due to over charge. Ill get back with you on my findings. Keep me updated on your progress.
Before you open her up, have you tried cleaning the metal contacts inside the USB on the phone? I am at work not, so I can't try anything, but I would check that before opening. Might just need to be cleaned.
Woodrube said:
Before you open her up, have you tried cleaning the metal contacts inside the USB on the phone? I am at work not, so I can't try anything, but I would check that before opening. Might just need to be cleaned.
Click to expand...
Click to collapse
yes i've tried. I used a Q-tip and some alcohol, still same problems.
Update: Nothing!! How about you?
I have tried un/reinstalling the drivers, Odin v1.8, 1.3 and 1.0, about 4-5 cables and all 3 ports. I have cleaned the USB with alcohol and at this point am at a slight loss. The phone boots into DLmode and charges fine, so I don't think it is a faulty USB port. I cannot get into any recovery or ROM boot. All I have is DLmode and the GB bl screen. No kernel or ROM splash.
Gasp! I'm in a similar boat guys. My phone charges fine, and all my drivers are working and up to date...I can get into DL mode and all that jazz...phone even boots up and works! (fortunately)...but no dice on it being recognized by my or any computer. Glancing into the port, it looks like there may be some corrosion on the left hand side of the port, or some sort of damage...can't really tell without a proper magnifying glass. but it does look damaged or at least irregular. I've been reading around, and cleaning sounds like a potential solution...I've no idea how you guys are cleaning with giant q-tips lol but hopefully I can figure that one out also and give it a whirl xD But in the mean time, I sure hope somebody can come to the rescue
I don't know if this can help you guys, but this is how i hard bricked my vibrant few months ago. I get into download mode trying to get back to stock from ICS and my computer didn't recognize my phone....after a couple of hours my phone was completely dead and after a few days of research i brought it back to life using the unbrickable mod. What i'm thinking now is to use the Unbrickable Resurrector but you will need Linux...it always worked for me but i'm not sure if you need the unbrickable mod already applied. However i think if you have Linux installed you can have a try. Here is the link for the unbrickable resurrector http://forum.xda-developers.com/showthread.php?p=17135277#post17135277
Hi guys/gals,
I've been passed a Nokia 710 by a friend of mine. She managed to drop it in a bowl of water at work and has been refused a fix under warranty (not surprising). This was a few weeks ago, so the phone is fully dried out. It boots up, makes the start-up sounds and the three buttons on the front work, but the screen is totally blank - although touch-screen response seems to work still.
I have installed Zune, but whenever I connect the phone I get "Phone setup incomplete" and a message to disconnect the phone and complete the remaining steps on the phone. Without a screen to see I have no idea what I should be doing.
Is there a simple solution to this, or is there some way of connecting to the internal memory to recover the data from it some other way?
SimonTS said:
Hi guys/gals,
I've been passed a Nokia 710 by a friend of mine. She managed to drop it in a bowl of water at work and has been refused a fix under warranty (not surprising). This was a few weeks ago, so the phone is fully dried out. It boots up, makes the start-up sounds and the three buttons on the front work, but the screen is totally blank - although touch-screen response seems to work still.
I have installed Zune, but whenever I connect the phone I get "Phone setup incomplete" and a message to disconnect the phone and complete the remaining steps on the phone. Without a screen to see I have no idea what I should be doing.
Is there a simple solution to this, or is there some way of connecting to the internal memory to recover the data from it some other way?
Click to expand...
Click to collapse
How did she do that, I don't think you can recover the data from your phone, Zune is giving you an update error which means that the update isn't intalled completly.
What you can do, but you had to do that a lot earlier, is to put the phone in a bowl of rice (not water ) and wait a few days, that's the only thing I can think about at the moment.
Succes,
Rataplan said:
How did she do that, I don't think you can recover the data from your phone, Zune is giving you an update error which means that the update isn't intalled completly.
What you can do, but you had to do that a lot earlier, is to put the phone in a bowl of rice (not water ) and wait a few days, that's the only thing I can think about at the moment.
Succes,
Click to expand...
Click to collapse
She had the phone in her pocket when she bent over. I think the problem may be down to a key-lock on the phone which needs to be entered first, but am waiting for her to get back to me.
Thanks for the help though, I didn't expect much else.
SimonTS said:
She had the phone in her pocket when she bent over. I think the problem may be down to a key-lock on the phone which needs to be entered first, but am waiting for her to get back to me.
Thanks for the help though, I didn't expect much else.
Click to expand...
Click to collapse
Plug it into a Linux machine and copy direct from the phone as any other USB flash drive would work
Or uninstall Zune and use the reg hack to allow that to be done in windows
http://shivamsoftworld.blogspot.co.uk/2012/12/how-to-enable-usb-mass-storage-mode-in_14.html
---
*Detection* said:
Plug it into a Linux machine and copy direct from the phone as any other USB flash drive would work
Or uninstall Zune and use the reg hack to allow that to be done in windows
http://shivamsoftworld.blogspot.co.uk/2012/12/how-to-enable-usb-mass-storage-mode-in_14.html
---
Click to expand...
Click to collapse
Fantastic, thank you. Following the link you posted also took me to another site USB Storage Enabler for Windows Phones 7 which might be useful for anyone else coming up against this in the future, or simply wanting to use their device as a USB drive, not requiring Zune.
SimonTS said:
Fantastic, thank you. Following the link you posted also took me to another site USB Storage Enabler for Windows Phones 7 which might be useful for anyone else coming up against this in the future, or simply wanting to use their device as a USB drive, not requiring Zune.
Click to expand...
Click to collapse
I think the phone has been reset
SimonTS said:
Hi guys/gals,
I've been passed a Nokia 710 by a friend of mine. She managed to drop it in a bowl of water at work and has been refused a fix under warranty (not surprising). This was a few weeks ago, so the phone is fully dried out. It boots up, makes the start-up sounds and the three buttons on the front work, but the screen is totally blank - although touch-screen response seems to work still.
I have installed Zune, but whenever I connect the phone I get "Phone setup incomplete" and a message to disconnect the phone and complete the remaining steps on the phone. Without a screen to see I have no idea what I should be doing.
Is there a simple solution to this, or is there some way of connecting to the internal memory to recover the data from it some other way?
Click to expand...
Click to collapse
I think the phone is reset entirely..
and the reason you couldn't connect to zune is because you haven't completed the initial boot procedures...
There are many ways to get your phone started...
But I don't think its of any use unless, you have your screen working..
My Amaze was connected via USB to my Ubuntu laptop and I was testing a game I was working on. Suddenly, my computer could not recognize my device and, my device and charging light was off (the battery was at ~94%). I have 3 batteries, and none of them work when trying to power on the device. My device was S-OFF, SuperCID, rooted, and running Android Revolution ROM HD. I was using a Samsung cable if that makes a difference. I tried booting with Power+Vol. Down but that did not work. I figure it is a hardware problem, but it seems odd that it would do this all of a sudden. Can anybody confirm what is wrong with it, and maybe a possible fix? Thanks!
Edit: I get the QHUSB_DLOAD driver message.
Anyone? Please help!
Sorry, your phone is almost bricked. Flash chip bug makes large chunks of the entire flash unreadable. It's more likely to happen if you issue a trim command or format a partition in the wrong way. (Well, it's the right way for flash, but our chip can get borked.) Mine just happened when I was copying a bunch of data over.
You corrupted something fairly early in the boot process but not the earliest thing. Search for fixes for the qhusb and you'll find a couple things. They didn't work for me, but might for you. Even if you fix it, it might re-brick itself after a bit of usage.
ezdi said:
Sorry, your phone is almost bricked. Flash chip bug makes large chunks of the entire flash unreadable. It's more likely to happen if you issue a trim command or format a partition in the wrong way. (Well, it's the right way for flash, but our chip can get borked.) Mine just happened when I was copying a bunch of data over.
You corrupted something fairly early in the boot process but not the earliest thing. Search for fixes for the qhusb and you'll find a couple things. They didn't work for me, but might for you. Even if you fix it, it might re-brick itself after a bit of usage.
Click to expand...
Click to collapse
Thank you for your response! You logic seems to be correct as I wasn't messing with any critical files. Please update your post if you find a solution!
Did you find the post(s) I was talking about? They may work for you. It basically involves trying to rewrite the bootloader.
I ended up punting and trying to desolder the MMC chip so I could try to get my data off it. Unfortunately, it's epoxied on so it got very damaged even though I was using a pretty good hot-air reflow station, so I haven't tried soldering it to a SD-card reader.
ezdi said:
Did you find the post(s) I was talking about? They may work for you. It basically involves trying to rewrite the bootloader.
I ended up punting and trying to desolder the MMC chip so I could try to get my data off it. Unfortunately, it's epoxied on so it got very damaged even though I was using a pretty good hot-air reflow station, so I haven't tried soldering it to a SD-card reader.
Click to expand...
Click to collapse
I have tried that numerous times to rewrite the bootloader, but to no avail. Can you post a picture, and do you think a JTAG would work?
cowboy1995 said:
I have tried that numerous times to rewrite the bootloader, but to no avail. Can you post a picture, and do you think a JTAG would work?
Click to expand...
Click to collapse
Picture of the board? I think I have it around somewhere. If I can find it, sure.
In theory it should work, but I don't think anyone has publicly mapped out the pins for it and I didn't feel like trying to figure out the software side of things to connect it to the generic JTAG adapters I have access to. It's possible that one of the phone-centric JTAG makers has an adapter board, but I'm not willing to spend $bank on a phone worth barely anything.