Hey guys bout to beat my head against a wall on this one.
A buddy of mine "tired" to replace his front glass on his Moto X and ended up destroying it. Apparently he cooked it pretty well with a hair dryer on high in the process of trying to the glass off and fried the LCD and digitizer and possibly more. Anyway he brought me over a bag of parts and asked if i could retrieve his data. He was running unrooted stock with a locked bootloader and I'm assuming debugging turned off but not sure.
So this is the part i start hitting my head against the wall. After reassembling it without the LCD/digitizer assembly pluged in, I pluged it in via USB and it installs it's self as a MOTOROLA PHONE, and seams to be using the USB INPUT and HID Compliant Vendor Defined Device drivers. I cant for the life of me get it to use the right drivers. I've installed Motorola's driver/device manager and run the Motorola driver installer but nothing is working.
Really don't know that much about the Moto X as I don't own one myself but i'd assume that it should install as a specific device and not a generic MOTOROLA PHONE as well as using MTP drivers instead of USB INPUT
Basically though, short of the driver issues, my main question is. Is there anyway of pulling data from a headless, bootloader locked, ADB disabled device? I personally don't think there is but just in case i thought i'd ask.
Would rather not buy a new LCD/Digitizer assembly for $70 if the main board got fried from the heat of the hairdryer, but might have to if there's no other way, at least then I could see what going on.
Have checked though the forms and didn't see any other similar topics on this, so if I missed it please link it.
Thanks ahead of time.
~Ninjaboy837
Ninjaboy837 said:
Hey guys bout to beat my head against a wall on this one.
A buddy of mine "tired" to replace his front glass on his Moto X and ended up destroying it. Apparently he cooked it pretty well with a hair dryer on high in the process of trying to the glass off and fried the LCD and digitizer and possibly more. Anyway he brought me over a bag of parts and asked if i could retrieve his data. He was running unrooted stock with a locked bootloader and I'm assuming debugging turned off but not sure.
So this is the part i start hitting my head against the wall. After reassembling it without the LCD/digitizer assembly pluged in, I pluged it in via USB and it installs it's self as a MOTOROLA PHONE, and seams to be using the USB INPUT and HID Compliant Vendor Defined Device drivers. I cant for the life of me get it to use the right drivers. I've installed Motorola's driver/device manager and run the Motorola driver installer but nothing is working.
Really don't know that much about the Moto X as I don't own one myself but i'd assume that it should install as a specific device and not a generic MOTOROLA PHONE as well as using MTP drivers instead of USB INPUT
Basically though, short of the driver issues, my main question is. Is there anyway of pulling data from a headless, bootloader locked, ADB disabled device? I personally don't think there is but just in case i thought i'd ask.
Would rather not buy a new LCD/Digitizer assembly for $70 if the main board got fried from the heat of the hairdryer, but might have to if there's no other way, at least then I could see what going on.
Have checked though the forms and didn't see any other similar topics on this, so if I missed it please link it.
Thanks ahead of time.
~Ninjaboy837
Click to expand...
Click to collapse
Now , I'm not a hardware specialist or anything ,but , do you suppose you could somehow "Directly" access data from the NAND chip ?
Ref: " https://www.ifixit.com/Teardown/Motorola+Moto+X+Teardown/16867 "
I did a little research on the NAND chip, unfortunately there is an NDA in place, so you probably won't be able to find out what the pins are to access it. I have been wrong before. Problem with using the hair dryer on high is that heat=energy in motion, which can cause electron flow.
If your friend didn't take appropriate precautions, ie grounding himself, ESD pad, dry hands, it is possible he shorted the entire assembly, and all his data is destroyed, especially if he didn't disconnect the battery.
Finally, the bag of parts=sensitive electrical components in a heavily charged static bag. Chances are that could've killed any chance of getting data.
The reason that your computer is recognizing the device as a Motorola Phone and that is it is as a failsafe, the processor isn't completely dead and is doing what it can to help you, by trolling you.
Good Luck!
I picked up a 4.4.2 Moto X with a bad battery and a bad (broken panel, no display) screen assembly. It did the same as what you're describing when hooked up via USB. After installing a good battery and plugging in a working screen it booted right up without any trouble. Before the parts the phone would light a green LED in the earpiece when plugged into the charger. Unless he really super baked the crap out of it you can probably get it working with a screen and possibly a battery.
If you do need a screen I was looking at the $52 dollar option on ebay myself before I found another option, it's auction number 251892071870 .
I'd suggest trying this http://forum.xda-developers.com/showthread.php?t=2786395
You'd be able to run the recovery by pressing all three buttons when the device is off to get to the bootloader. Then when you guess that its loaded press volume down once, then volume up once. Then wait 10-30 seconds for recovery to load
tormin said:
I picked up a 4.4.2 Moto X with a bad battery and a bad (broken panel, no display) screen assembly. It did the same as what you're describing when hooked up via USB. After installing a good battery and plugging in a working screen it booted right up without any trouble. Before the parts the phone would light a green LED in the earpiece when plugged into the charger. Unless he really super baked the crap out of it you can probably get it working with a screen and possibly a battery.
If you do need a screen I was looking at the $52 dollar option on ebay myself before I found another option, it's auction number 251892071870 .
Click to expand...
Click to collapse
I might just have to try that, i did notice with the battery out and connected via USB the phone shows up as a USB INPUT, but as soon as you plug in the battery and the X8 computing system then it switches to MOTOROLA PHONE.
mrmidnight said:
I did a little research on the NAND chip, unfortunately there is an NDA in place, so you probably won't be able to find out what the pins are to access it. I have been wrong before. Problem with using the hair dryer on high is that heat=energy in motion, which can cause electron flow.
If your friend didn't take appropriate precautions, ie grounding himself, ESD pad, dry hands, it is possible he shorted the entire assembly, and all his data is destroyed, especially if he didn't disconnect the battery.
Finally, the bag of parts=sensitive electrical components in a heavily charged static bag. Chances are that could've killed any chance of getting data.
The reason that your computer is recognizing the device as a Motorola Phone and that is it is as a failsafe, the processor isn't completely dead and is doing what it can to help you, by trolling you.
Good Luck!
Click to expand...
Click to collapse
Yea, some people don't realize the big affects of not following little precautions.
Found a article on hackaday about reading NAND chips in place on the pcb might give that a try if all else fails.
http://hackaday.com/2010/12/24/reading-nand-flash-chips-without-removing-them/
http://www.uchobby.com/index.php/2007/05/05/read-embedded-flash-chips/
raddacle said:
I'd suggest trying this http://forum.xda-developers.com/showthread.php?t=2786395
You'd be able to run the recovery by pressing all three buttons when the device is off to get to the bootloader. Then when you guess that its loaded press volume down once, then volume up once. Then wait 10-30 seconds for recovery to load
Click to expand...
Click to collapse
When booting in to the Moto X's recovery does it start ADB? I'm not sure if ADB is enabled or not, but it's worth a shot. I've gotten spoiled with My TWRP recovery auto enabling ADB on recovery boot.
ooo just saw this, there might be hope after all
Ricky Divjakovski said:
for people who dont have adb enabled, i suggest you contact a kernel developer to automatically enable it in the default.prop and sideload the kernel in recovery!
i broke my S3 on stock so nothing was enabled.
i enabled adb via the default.prop and compiled the kernel and flashed in recovery(sideload).
now i have full control over the device.
Click to expand...
Click to collapse
Ninjaboy837 said:
When booting in to the Moto X's recovery does it start ADB? I'm not sure if ADB is enabled or not, but it's worth a shot. I've gotten spoiled with My TWRP recovery auto enabling ADB on recovery boot.
ooo just saw this, there might be hope after all
Click to expand...
Click to collapse
Hmm you know what, you're right. It seems Nexus devices have adb on stock recovery- Moto's don't. Though what you found might be gold, I hope you can bust out a modified kernel- or know someone who does.
EDIT: Though I don't know how you're going to get the Update.zip on the phone to flash it. Worse comes to worse you could plug a mouse into the phone and play a guessing game of what you're clicking on
Related
I bought this G1 with a cracked screen and I decided to replace the screen, however when I removed a certain part in the phone I managed to rip a ribbon cable. I searched for a replacement part and found out that it will cost about $185 to replace it. Now I am about to buy this other G1 for $50 that had water damage that I will be using for parts. But before I buy it, is there a way I can see whats wrong with it using adb? I'm interested in whether the part that I need is in working condition.
the phones condition is:
-the screen does not show anything but a backlight
-leds work
-rebooting using three buttons work
-lcd is probably screwed up because when i hit the power button i see part of the home background and then it fades away.
-no g1 screen logo while rebooting
-normally vibrates once while rebooting
-android os boots up
-"adb kill-server adb devices" doesn't list me any devices when i hook it up to usb. maybe debugging is turned off.
here is a link to the part i am about to remove
http://www.cellphone-repair-shop.co...icrophone-and-sd-card-slot_50H10000-02M-A.htm
the pcb board has the trackball, usb port, simcard slot, sdcard slot, and various other peripherals.
sensimila said:
I bought this G1 with a cracked screen and I decided to replace the screen, however when I removed a certain part in the phone I managed to rip a ribbon cable. I searched for a replacement part and found out that it will cost about $185 to replace it. Now I am about to buy this other G1 for $50 that had water damage that I will be using for parts. But before I buy it, is there a way I can see whats wrong with it using adb? I'm interested in whether the part that I need is in working condition.
the phones condition is:
-the screen does not show anything but a backlight
-leds work
-rebooting using three buttons work
-lcd is probably screwed up because when i hit the power button i see part of the home background and then it fades away.
-no g1 screen logo while rebooting
-normally vibrates once while rebooting
-android os boots up
-"adb kill-server adb devices" doesn't list me any devices when i hook it up to usb. maybe debugging is turned off.
here is a link to the part i am about to remove
http://www.cellphone-repair-shop.co...icrophone-and-sd-card-slot_50H10000-02M-A.htm
the pcb board has the trackball, usb port, simcard slot, sdcard slot, and various other peripherals.
Click to expand...
Click to collapse
you ARE SO FUNNY!!!
Why? can I laugh too?
I don't see you turning a profit considering u can buy one for $200 on craigslist easy
its funny cuz its like you trying to buy a coumputer without a mother board. this is the main thing in the g1 it would be cheaper to buy the phone brand new
i have two, one of them needs this part and the other one has the part i need. and plus im fixing it for my brother.
G1 #1
-already Bought for $74
-needs pcb board
G1 #2
-$50 as is
-has pcb board
-has water damage
anyhow I managed to get into recovery and did a wipe logged in but once the screen turns off i cant turn it on anymore. would you say it is safe to exchange these parts?
Wrong Forum, goodness
how is it wrong..I'm not asking anybody to take it apart and do it for me. if it was in the wrong place would it be because I'm not developing something for someone to use. is there a section for modding, taking apart the g1 and internals. if i could develop something i would. i guess there's no help in posting useless remarks because that doesn't contribute to nothing. If this so happens to be in the wrong forum well then this is my first mod now isn't it? and since you went of of your way to tell me its the wrong place why don't you be helpful to lead your fellow xda forum member. ok.
accessory forum This seems to strictly be about discussing the SOFTWARE for the Dream. Accessory forum covers mods and replacements (to my knowledge)
$50 for a water damaged G1? WTF? Are you serious?
miketaylor00 said:
$50 for a water damaged G1? WTF? Are you serious?
Click to expand...
Click to collapse
do you mean by that as expensive or cheap???
prince.siraj said:
do you mean by that as expensive or cheap???
Click to expand...
Click to collapse
I'd say expensive, as you have no idea the extent of the water damage. If the phone was on while dropped into the water, the mainboard is likely dead. Buying it would be a waste.
Also, this forum is for software development. Moving this thread. Thanks!
hey thanks for moving my thread. as i reread my post it seems more of a question than a developmental thread.
further testing
i booted up
ran through all of the radios wifi, 2g, 3g, orientation sensor, made a call and they all seem to work fine. the one problem with this phone is that if i turn off the screen it won't turn back on.i think that maybe the pcb board might be salvageable. would that be worth doing?
What cable was it that you ripped? What was it connecting? And is it possible for you to take pictures?
my digi cam isnt working but this will do. its like a 1/8" rip on the side of the ribbon i was thinking about repairing but i cant because the ribbon is soldered to the board. i figure that i should try swapping it out, what could possibly go wrong? im assuming that the lcd has lost the ability to regain power after turning off from the water. and maybe...possibly the main pcb has dried up and not been damaged considering most things work fine. thanks for sticking around.
I'm not liking your chances of getting this working, but fwiw here's the service manual:
http://mikechannon.net/PDF Manuals/HTC Dream SM (A04).pdf
Thanks I already have that manual printed out. Took it all apart like4 or 5 times. its pretty easy to do. I'll be starting operation on it tonight.
PLZ help im freaking out. i accidentally booted into the blue light mode, but when i pulled the battery and rebooted the backlight wouldnt work. i could see everything and even navigate my phone but only under a light. the backlight just wont turn on during boot and changing the setting doesnt help.
i dont get it the thing was working 10 minutes ago and now i cant use it what should i do? i love this phone but i cant afford a new one. is there a way to tell it to turn on during boot in the console?
ok new update the backlight works if i have the keyboard open. i know 100% its software and not the screen. something when wrong with the boot prosses or something.
i think the trackball boot (bluelight boot) must have options but wont display on the screen maybe. like a bios menu. this is very infuriating
Why don't you restore a recent backup?
i have even went as far as downgrading with the .nbh file. and re installing the bootloader (Just the original, didnt want a brick).
Definitely NOT a software problem.
This is a HARDWARE problem -- hence the fact that it works when the keyboard is open.
When you pulled the battery, you might have twisted/pulled something.
*** I would check the ribbon cable connecting the display to the main body!!!
Bluelight mode (where you end up by booting with the trackball pushed in), is just a serial console allowing interfacing with the radio firmware. Unless you actually had a serial cable connected and punched in some commands (which happen to be security locked, therefore wouldn't work for you anyways), bluelight mode wouldn't be able to do this.
lbcoder said:
Definitely NOT a software problem.
This is a HARDWARE problem -- hence the fact that it works when the keyboard is open.
When you pulled the battery, you might have twisted/pulled something.
*** I would check the ribbon cable connecting the display to the main body!!!
Bluelight mode (where you end up by booting with the trackball pushed in), is just a serial console allowing interfacing with the radio firmware. Unless you actually had a serial cable connected and punched in some commands (which happen to be security locked, therefore wouldn't work for you anyways), bluelight mode wouldn't be able to do this.
Click to expand...
Click to collapse
if that were the case than wouldnt it flicker if i flex the screen/hinge ? ill try anything at this point cuz im outa warranty and have no money . im going to the store later trying to update to official 1.6 so i can convince them its software related and they may replace it for me.
oh forgot to mention that if i close it and open it the light stays off untill i hit end and unlock with menu again. im not to sure if that helps.
OK OK OK you are right. i just half closed it and the light stayed on untill it compleatly closed (so the screen flipped, i thought that is what triggered it) and then i got it to stay on completely closed and then the problem flipped to it wouldnt come on while open and now back to the way it was. so im going to go buy a T5 screw driver today and clean the contacts of the ribon cable and reinsert it (i have had experience with that just need to know what ribon. a pic would be nice)
projectzro said:
OK OK OK you are right. i just half closed it and the light stayed on untill it compleatly closed (so the screen flipped, i thought that is what triggered it) and then i got it to stay on completely closed and then the problem flipped to it wouldnt come on while open and now back to the way it was. so im going to go buy a T5 screw driver today and clean the contacts of the ribon cable and reinsert it (i have had experience with that just need to know what ribon. a pic would be nice)
Click to expand...
Click to collapse
There is only one ribbon running to the screen. Try THAT one.
lbcoder said:
There is only one ribbon running to the screen. Try THAT one.
Click to expand...
Click to collapse
LOL lbcoder - always practical.
lbcoder said:
There is only one ribbon running to the screen. Try THAT one.
Click to expand...
Click to collapse
lol ok didn't know that a lot of the devices I have taken apart have had 2 one for the desplay and one for the backlight. Getting a T5 screw driver in half an hour. Will post results later. Hopefully this works, therr area few more ppl with the same problem.
projectzro said:
lol ok didn't know that a lot of the devices I have taken apart have had 2 one for the desplay and one for the backlight. Getting a T5 screw driver in half an hour. Will post results later. Hopefully this works, therr area few more ppl with the same problem.
Click to expand...
Click to collapse
There are two wires going to the screen.. sounds like the "top" one is loose... The jtag photos will give you an idea (it's the two com ports next to the jtag test points)
These are usually taped down very well..
Also you need both a T5 and T6.. the "Security" (has black void sticker) screw is larger than the others.. and a small flat head screwdriver to unclip the cover..
If all else fails: replacement screens seem much cheaper than the phone on ebay.
ezterry said:
There are two wires going to the screen.. sounds like the "top" one is loose... The jtag photos will give you an idea (it's the two com ports next to the jtag test points)
These are usually taped down very well..
Also you need both a T5 and T6.. the "Security" (has black void sticker) screw is larger than the others.. and a small flat head screwdriver to unclip the cover..
If all else fails: replacement screens seem much cheaper than the phone on ebay.
Click to expand...
Click to collapse
ok got it apart 3 times and no luck its prolly the ribbon cable. im going to test that soon. i have a donor phone comming soon from a friend who dropped it in water, the ribbon cable should be fine to use. if that doesnt work im thinking maybe it is software. either way if i cant get it fixed by next month im spending $410 on a new mytouch 3G brand new from the store and getting insurance XP
Alright, I tried first with the stock rom: different usb cables, kies, installing uninstalling samsung drivers, double twist, on a mac and on windows 7, and nothing works, no matter what I tried, none of that could show me the notification bar asking for what to do with the usb connection. Of course I tried setting the phone on debugging mode and on mass storage, also ask everytime, etc.
Finally I decided to leave the stock rom and move to Cognition froyo, in order to discard a hardware issue. Thanks to Rom manager I could make it without needing the usb at all.
Once in Cognition v2.3b8 I crossed my fingers and looked to the sky (even considering that I'm atheist) and plug in the usb to my computer.... and nothing happens besides the phone charging.
Can I say right now that this is definitely a hardware issue?
Some people here are use to say, "if it's charging, definitely it's a drivers issue", but after moving to a new rom, and trying in three computers (two windows and one mac) it is a drivers issue that I can fix without buying a captivates motherboard?
Please help me out here and I'll buy you a beer, a blue moon one if you like ;P
Have you played with your USB settings; debugging, mounting SD card etc?
dionieins said:
Alright, I tried first with the stock rom: different usb cables, kies, installing uninstalling samsung drivers, double twist, on a mac and on windows 7, and nothing works, no matter what I tried, none of that could show me the notification bar asking for what to do with the usb connection. Of course I tried setting the phone on debugging mode and on mass storage, also ask everytime, etc.
Finally I decided to leave the stock rom and move to Cognition froyo, in order to discard a hardware issue. Thanks to Rom manager I could make it without needing the usb at all.
Once in Cognition v2.3b8 I crossed my fingers and looked to the sky (even considering that I'm atheist) and plug in the usb to my computer.... and nothing happens besides the phone charging.
Can I say right now that this is definitely a hardware issue?
Some people here are use to say, "if it's charging, definitely it's a drivers issue", but after moving to a new rom, and trying in three computers (two windows and one mac) it is a drivers issue that I can fix without buying a captivates motherboard?
Please help me out here and I'll buy you a beer, a blue moon one if you like ;P
Click to expand...
Click to collapse
I'm pretty sure there's a problem with your USB cable if it's not the drivers. Try using a different cable and check.. Should work!
I am having the same issue and I took it to AT&T device warranty center and they found that the USB side on the phone had some water corrosion in it and therefore my warranty is voided. I also went down the path of installing drivers, different OS but this seems to be close. now If some can tell me how to clean this port...awesome
Is the water sensitive patch under the battery still white?
rockosifraldi said:
I am having the same issue and I took it to AT&T device warranty center and they found that the USB side on the phone had some water corrosion in it and therefore my warranty is voided. I also went down the path of installing drivers, different OS but this seems to be close. now If some can tell me how to clean this port...awesome
Click to expand...
Click to collapse
First make sure its not the usb cable. Main power leads in cable usually hold up but smaller wire leads are much more fragile and the only symptom you may get is either wont be recognized and/or usb registers as data connection on the dropdown menu. Ive had a captivate with a corrosion problem but Ive also had a Samsung cable that had broken shorted out data lead but still charged fine.
You can clean port with fingernail emery board cut to shape and stripped on one side of board to proper thickness. Its a five minute mod to a 99 cent board.
rockosifraldi said:
I am having the same issue and I took it to AT&T device warranty center and they found that the USB side on the phone had some water corrosion in it and therefore my warranty is voided. I also went down the path of installing drivers, different OS but this seems to be close. now If some can tell me how to clean this port...awesome
Click to expand...
Click to collapse
I've seen long threads of people who reported the same issue: no actual water damage, but a messed up USB port and their warranties being unjustly denied. Try cleaning the contacts in the phone's microUSB port with a coffee filter dabbed in rubbing alcohol, or scratching at them with a thin wire.
I'm currently having USB port issues with my brand new replacement Captivate (phone sometimes randomly thinks it's plugged in when it isn't, thinks it isn't plugged in when it is), haven't had any luck fixing them yet.
If there's no visual residue on the charging port, they cannot rightfully void your warranty. The captivate has 2 LDI's(Liquid Damage Indicators), one on the battery and one on the phone itself, behind the battery. As long as those two are white, and as long as there isn't a bunch of green crap on the charging port, they will replace it.
I work at AT&T, and we deal with this everrrrrrrrry day. 3 big rules with warranty swaps; LDI's need to be white, charging ports need to be intact and not corroded, and there needs to be no physical damage, any scratches or dings that you can feel with a fingernail are considered physical damage. We help people who terlet their phones get warranty exchanges sometimes, nothing an exacto knife and some raw effort can't fix. AT&T is a weak beast, be assertive and they will bend to your will.
In all honesty though, just make the charging port as clean as you can and call in. Ask for a supervisor, tell them it's a documented defect with a recent wave of Captivates, and you won't hang up until they exchange it for you.
well thanks for the help, now I'm gonna check the white indicators and if the phones usb needs to be clean
dionieins said:
well thanks for the help, now I'm gonna check the white indicators and if the phones usb needs to be clean
Click to expand...
Click to collapse
well I cleaned the phone and still is not working, this is a hardware issue definitely
dionieins said:
well I cleaned the phone and still is not working, this is a hardware issue definitely
Click to expand...
Click to collapse
I had that problem with my brand-new second Captivate out of the box. Not going to deal with warranty and bull**** water damage accusations, this is being returned to the retailer first chance I get.
I've had something weird happen as well. I've had my Captivate plugged into my PC using USB Debugging at least 10 - 15 times today. I also clicked "Mount" so I could transfer files that I have backed up.
Now suddenly it stopped working. I have jumped around using every port on my laptop (all 4). I have noticed it's acted weird before.
But now (without anything plugged in at all) the laptop keeps popping up saying USB Device Not Recognized.....even though I'm not trying to plug anything in.
Should I reinstall the Samsung 32 bit drivers? I did uninstall Kies today because I had no use for it. It was annoying to have Kies open every time I plugged in.
I have a captivate lying around which have the same problem, i/e the USB cable works fine for charging but not for PC connectivity.
Since it is a development phone, I just reverted to using adb wireless widget.
Other than that, after reading this thread, it seems to be a common issue.
I got my phone exchanged (again) and no USB or GPS problems this time. I got a grainier-looking screen though...meh can't complain really, since this is the only Captivate I've owned that doesn't have any major/hardware-related problems.
My USB not working ended up being my laptop (not phone). I had to unplug the power supply....shut down for a few minutes.....reboot and it worked. I had tried reinstalling the drivers but it did nothing.
mikegy2002 said:
First make sure its not the usb cable. Main power leads in cable usually hold up but smaller wire leads are much more fragile and the only symptom you may get is either wont be recognized and/or usb registers as data connection on the dropdown menu. Ive had a captivate with a corrosion problem but Ive also had a Samsung cable that had broken shorted out data lead but still charged fine.
You can clean port with fingernail emery board cut to shape and stripped on one side of board to proper thickness. Its a five minute mod to a 99 cent board.
Click to expand...
Click to collapse
I appreciate the advice use some acetone to remove the green stuff but phone is still being difficult when trying to connect to the pc ...be nice if samsung came up with something so there wouldnt be a possibility that water would get in the port
I've had this problem since i got my phone, and i've had it for months now.
Always thought it was drivers.
My last try was with the new AIO captivate tool box app and the drivers their.
For those of you that got replacements how did you go about this.
just go to the store? Or is there a number to call to do it over the phone?
It's just annoying not being able to transfer pictures and such off my phone, hell it worked with my iPhone. I know you can setup wifi file transfers, but if i'm at a friends house it would be nice just to be able to plugin the phone and transfer files too it.
I fixed this problem selling out the phone. Not joke.
BUT, thing is, that the buyer, couple days after the purchase, told me that he fixed this issue by simply restoring the phone to the stock rom through odin 1 click.
Why I didn't try that easy fix? Simply because I thought that the phone was already in the stock rom :S
Lesson learned: always double check if you're in stock rom or not. (obviously you don't need to do this if your purchased the phone brand new!)
It's really weird, a week ago my phone suddenly freezing while I was out, I took the battery off and put it back but it was stucking on AT&T logo scree. I've tried that for few times nothing changed, put it away and the next day tried for few more times and this time came up (also recovery mode and 3 buttons didn't work too).
Everything was look fine but had a problem it was when I plug the USB cable it's just showing the charge status, means couldn't connect the Phone to PC ,I tried with some other cables and PCs, also put hair dryer if possibly water went in but the problem was from the phone.. also when took the USB off the charging status was keep going. first thing I thought it would be the ROM, I had some other ROM in the memory to I flashed to another ROM, but the problem was still there.
tried many times nothing changed, I was almost wanted to grab a new one, till 2 nights ago after a week while it was charging I suddenly noticed that it can connected, I straight away got backups copied to PC and flashed to Stock, now everything looks fine after few days and it works good.
any suggestion on that? is it could be water inside or something?
My ROM was Cognition 2.3 at that time
hope it's not gonna happens again.
I had the same problem and it was a bad USB port any phones made before December '10 have had a lot of problems. Warranty gave me a replacement without question.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
History:
Bought Captivate 08/10. I'm on my 3rd phone, all replaced due to "sleeping death", capacitive buttons not working, some other common bug with this phone.
In May, I (and the captivate) was pushed in a swimming pool so my phone is no longer under warranty and I'm stuck with this thing. I actually tried to get it replaced at the AT&T service center and the guy was going to let me, but I had to get it back to stock firmware - I was running Paragon. The capacitive buttons are sometimes working, sometimes not so getting to stock fw was a challenge. I did that after several hours and returned to the store, but they voided the warranty due to water damage.
Present:
1. Capacitive buttons sometimes work. sometimes don't (days at a time)
2. USB will not work (I hate you for this Samsung). 2 cables, 3 pcs, drivers galore. I can charge off USB, but the PC doesn't see the phone and the phone doesn't see the PC.
3. Can no longer dl any apps from the Market - get unsuccessful message. Tried clearing cache of download manager, etc. as recommended on xda.
What can I do at this point? I'd like to install a decent ROM and recover as much as possible, but this thing blocks every attempt I make with some problem. I would replace it, but $600 is pretty steep for a phone right now.
Thanks
I'll offer what I can (I'm ready to give up on this $&@# device, too)
The buttons are flimsy as ****. They are just rubber inserts whos 'spring mechanism' is the rubber itself (to restore itself to its original shape). This isn't 'mechanical' its like expecting a seat cushion to always retain its shape (and not create ass divots). I suppose these extremely small rubber inserts could be replaced, but there is no mechanism to 'fix'.
**I'm assuming you meant the vol / power buttons (not the touchscreen buttons)
The USB thing.....I would get this sometimes. I found the BEST way around this (and this may not be a solution for you), but the market app "USB Cable" essentially sets your device up as an ftp location on whatever wireless you're on. Freaking golden if you're on your home wireless network, but if not, I doubt its much of an option (it is considerably faster than a 2.0 / 3.0 USB connection). **since you can't access Market (http://www.androidzoom.com/android_applications/productivity/wifi-ftp-box-free_vkuk.html)
One year in, then it's time for an early upgrade.
What do you expect after it being under water?
You can't blame samsung for usb or button problems, blame the water.
That said sell it and put the money towards another phone.
By any chance did you buy the insurance? If you did, just call it in lost and pay the $125 deductible and have a working phone. If not there's really not that much you can do. What did you do to dry the device out? believe it or not, there may still be moisture in there. You might try putting the phone in a container of some sort and covering it with rice (uncooked of course) and letting it sit for a day or two, and then try it out.
I would blame the jerk that pushed you in the pool, not the phone....That person owes you a phone.
If you've been running stock 2.1 or 2.2 the poor performance will happen.
I felt the same way about the phone until I discovered the cognition rom, it's well known for being very stable but with your usb issues...good luck.
thanks for the advice everyone. i will check on the insurance route.
but yes, i can blame samsung for the usb issues. why is it so difficult to access your phone via the built in usb port? special drivers, distinct cables, etc. are absurd.
spanishfry said:
thanks for the advice everyone. i will check on the insurance route.
but yes, i can blame samsung for the usb issues. why is it so difficult to access your phone via the built in usb port? special drivers, distinct cables, etc. are absurd.
Click to expand...
Click to collapse
How many phones don't use some sort of drivers to get this kind of access to it? I know the majority of the phones I have used in the past have needed some sort of drivers. Also, what distinct cables? It's a micro USB, you can't get any more common for a modern device than that. Samsung uses excellent hardware in everything they build and they regained my respect from the Froyo flop when they leaked Gingerbread so quickly to realistically a fairly old device. On top of that, they also leave their hardware to be hacked by our skilled developers (unlike Motorola).
Reamer09 said:
How many phones don't use some sort of drivers to get this kind of access to it? I know the majority of the phones I have used in the past have needed some sort of drivers. Also, what distinct cables? It's a micro USB, you can't get any more common for a modern device than that.
Click to expand...
Click to collapse
He didn't mention this issue specifically, but even when using the correct cable/drivers you can still get the dreaded adb offline error. Sometimes changing usb port fixes the issue. This screams bug, either in the samsung drivers or maybe adb itself?
BenKranged said:
He didn't mention this issue specifically, but even when using the correct cable/drivers you can still get the dreaded adb offline error. Sometimes changing usb port fixes the issue. This screams bug, either in the samsung drivers or maybe adb itself?
Click to expand...
Click to collapse
What "special drivers" would he be talking about then? I'm just one of the lucky ones that got a phone that works, 3 button works, adb always works, never had USB problems, never bricked (yet).
sent from my KF1 Galaxy S Captivate
spanishfry said:
but yes, i can blame samsung for the usb issues. why is it so difficult to access your phone via the built in usb port?
Click to expand...
Click to collapse
Possibly because you submerged the phone in water?
spanishfry said:
thanks for the advice everyone. i will check on the insurance route.
but yes, i can blame samsung for the usb issues. why is it so difficult to access your phone via the built in usb port? special drivers, distinct cables, etc. are absurd.
Click to expand...
Click to collapse
Welcome to the world of smartphones.
thread closed
Hello.
The full story is here:
Just before the new years eve, me and some friends went to the mountain where under light snowfall and temperatures close to -10°C, we enjoyed putting our youngsters sliding downhill with their sleds. Some of us even went for a little bit of easy snowboarding as all the other tracks were closed. I did not do any snow sledding nor any snowboarding but was strolling around there with my phone in my open pocket so there might was some slight snowfall on the phone.
After that, while we were returning to our urban homes, I was sitting in the back seat of my friend's car and had the phone resting on a niche on the passenger's door. When we stopped at a gas station to refuel under HEAVY snowfall I got off the car to buy some some chocolate and coffees for the travelling party. When I got back home, after about 1 hour, I discovered that my phone wasn't there. A quick recall of my previous actions lead me to the conclusion that my phone must have fell there while the door was open.
I made a phone call to the station where I was told that the phone was found, was working but the screen was not working. I went back there to retrieve the phone which meanwhile had died due to the battery outtage. So under all scenarios my phone could have been exposed to some snowfall while always inside its leather flip case.
tl;dr
My phone was exposed to lower temperatures and snowfall in its flip leather case.
So, now I have a phone that it's screen has died. No cracks or dents or bents or anything like that.
How would you suggest I should troubleshoot?
What are your guesses about what's faulty?
If Im guessing correct the screen might slightly cracked in 1 of the corners, if so the crack will be very light and not easily visible, due to drop.
Thats what I can think of now.
TryllZ said:
If Im guessing correct the screen might slightly cracked in 1 of the corners, if so the crack will be very light and not easily visible, due to drop.
Thats what I can think of now.
Click to expand...
Click to collapse
I will closely examine and report back.
But I have the feeling there were absolutely no cracks.
Like I said the screen looks Ok.
I have plugged it into the USB port and the Notification LED blinks orange.
I will at least try to extract what's within my phone via adb to move to my new Motorola Moto G4.
olspookishmagus said:
Like I said the screen looks Ok.
I have plugged it into the USB port and the Notification LED blinks orange.
I will at least try to extract what's within my phone via adb to move to my new Motorola Moto G4.
Click to expand...
Click to collapse
if it blinks then it lives, the bad news is its not charging.
How long did you leave it charging? could take a while until it starts actually charging due being so empty.
Could be battery its gone due temperatures. but dont see reason why.
kativiti said:
if it blinks then it lives, the bad news is its not charging.
How long did you leave it charging? could take a while until it starts actually charging due being so empty.
Could be battery its gone due temperatures. but dont see reason why.
Click to expand...
Click to collapse
It's charging OK.
The phone was rooted and was running CM, however even though I'm white-listed for USB debugging for this PC, when I reboot to recovery to get a full backup I'm getting this:
Code:
$ sudo adb devices
List of devices attached
_HTC_SERIAL_ unauthorized
$sudo adb shell
error: device unauthorized. Please check the confirmation dialog on your device.
If I reboot into normal again I get full adb rights and now I'm struggling to bypass my lock-screen pattern.
Best adb screenshot so far here: http://i.imgur.com/TOMPNROg.png
olspookishmagus said:
It's charging OK.
The phone was rooted and was running CM, however even though I'm white-listed for USB debugging for this PC, when I reboot to recovery to get a full backup I'm getting this:
Code:
$ sudo adb devices
List of devices attached
_HTC_SERIAL_ unauthorized
$sudo adb shell
error: device unauthorized. Please check the confirmation dialog on your device.
If I reboot into normal again I get full adb rights and now I'm struggling to bypass my lock-screen pattern.
Best adb screenshot so far here: http://i.imgur.com/TOMPNROg.png
Click to expand...
Click to collapse
sorry my bad missread.
Ok so its comming to life.
i would leave the phone charging for a few hours. the heat from the battery will warm the components. Maybe its just bad connection.
olspookishmagus said:
Like I said the screen looks Ok.
I have plugged it into the USB port and the Notification LED blinks orange.
I will at least try to extract what's within my phone via adb to move to my new Motorola Moto G4.
Click to expand...
Click to collapse
Perhaps the cable connecting the LCD to the board might have jolted, a bad connection as @kativiti said.
I will try and backup whatever is possible with ADB while the phone allows it.
Then I will try to pry it open and clean and remove whatever residue I'll find.
And then I will try and replace the faulty parts (starting with the cheapest part first).
But if the screen will still not function that would rule out the digitizer and I should go straight for the LCD, right?
olspookishmagus said:
I will try and backup whatever is possible with ADB while the phone allows it.
Then I will try to pry it open and clean and remove whatever residue I'll find.
And then I will try and replace the faulty parts (starting with the cheapest part first).
But if the screen will still not function that would rule out the digitizer and I should go straight for the LCD, right?
Click to expand...
Click to collapse
yes since the image is in the LCD.
Good luck