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.
Basically about 2 months ago I rooted the phone and put in cyangen mod, everything was fine until the touch screen stopped working. Most of the time it was brief but sometimes the touch screen just wouldn't work for a whole day and then start working again. Thinking I had done the root wrong I unrooted the phone back to it's orginal. However the problem still showed up despite that. I recently updated it to the donut update, and that's when the problem got worse. Now the touch screen won't work and when I go to the contacts using the trackball I get an error. And anytime i recieve a phone call I get the same error. Thinking it was a software problem and factory reset the phone and scaled it back to rc29. But still the touch screen doesn't work, and now because of that I am stuck on the setup screen at the beginning which ask you to touch the android to continue (which I can't). I have wiped and factory reset the g1 many times, and usually that has made the touch screen work again, but now it seems to not work at all. I deducted over the last couple of days that it must be the power adapter causing all of this. Since I got the touch screen working yesterday and had no problems the entire day. Then a hour after I put it on the charger the touch screen stopped working again and hasn't worked since. Is there anything that can be done at this point to fix it? I read somewhere about a script that makes the g1 touch screen work again but haven't been able to find it.
Same problem
I'm having a near identical problem. Most all of the symptoms are the same - except my touchscreen has only worked for a few seconds on one occasion after the initial failure. I've tried wiping, and about 3 different mods (JaCx, Cyan, Enomther). None have helped, and currently I'm stuck at the same point where it's asking me to touch the Android to begin, and I can't. The only difference is that I didn't unroot. So I'm going to try a few more roms, but I doubt I'll have any luck. My phone was also put on a charger that wasn't made for the g1. I began to notice the problem thereafter. Not sure why, but that certainly seems like the only reasonable variable which could be causing this.
Anyone out there have any ideas? It'd be much appreciated.
Have you guys dropped your phone recently? I'd like to share my story as well. Two weeks ago, I dropped the phone on hard tile while it was still in its leather/suade case. I picked it up and instantly found the touch capabilities were gone (with screen open or closed). After many soft resets and not knowing how else to fix it, I also decided to revert back to rc29 from cyanogenmod. Still no go, after being stuck at the setup screen. I disassembled the phone, using the G1 service manual, to make sure none of the ribbons were knocked loose and examined the lcd and digitizer for any cracks. No problems that I could see. Disassembled, and reassembled the phone a few more times and still with no avail.
If you were one of the first to receive a g1, such as myself, oct 22nd is the last day of your 1 yr warranty. So give t-mobile a call, and submit a claim before then if you want to take advantage of it. Make sure you reflash to stock image, and that there are no signs of visible damage on the phone or else the warranty will be void. Good luck.
Edit: If your phone's touch screen is working at random times, I'm suspecting its a hardware problem, most likely a damaged or worn out flex cable from opening and closing the screen. Try slowly opening the screen and touching the screen at the same time to see if anything happens.
When I was waiting for my G1 I came on this forum (Had a Diamond before so knew about it anyway) and found a topic discussing problems like this... If you have an Early G1 then I'm guessing this is the problem...
There is some sort of design flaw with the ribbon cable connecting the Touch Screen to the Mainboard catching onto the sliding mechanism. This eventually destroys the cable and causes the touchscreen to stop working. On Later models they've fixed it by taping the ribbon cable down instead of letting it hang loose.
In short... you need to unroot your phone and take it back to T-Mobile.
Interesting thoughts, thanks for the input. My G1 has never been dropped, and is actually relatively new, only a couple months old. But it's not on T-Mobile. I flashed MLIGN 2.5.7 (Hero). I did this b/c I know it bypasses the typical "touch here" activation BS. So I can boot, and get into the OS just fine. Which is where I'm at now.
Here's what I've done. I completely wiped my Fat32, Ext2, and Linux_Swamp partitions using Gparted. I completely wiped the phone using Cyan 1.4 Recovery. Yet no matter which Mod I use my touch screen doesn't cooperate, AND (no matter which mod I'm using) when I try to launch basic apps (dialer/phone, some settings menus, etc) I am notified that, "android.process.acore" has stopped. Without fail. It ALWAYS does this when attempting to access the dialer/phone. I would be more than happy to take some time troubleshooting the touch screen IF my damn dailer/phone would work. But it does not.
I read on some other forums about there being 2 compcache files for someone who had a similar issue. That's slightly above my head, though, and I'm not quite sure how to go about checking that and/or deleting one. Really, I just want to be able to access my dialer/phone app for the time being. Then I can take some time to trouble shoot the touch screen.
Anyone have any ideas about the process failing, or the compcache affect?
Also, I'm using 1.33.2005 SPL.
Thanks
gat0rjay said:
Interesting thoughts, thanks for the input. My G1 has never been dropped, and is actually relatively new, only a couple months old. But it's not on T-Mobile. I flashed MLIGN 2.5.7 (Hero). I did this b/c I know it bypasses the typical "touch here" activation BS. So I can boot, and get into the OS just fine. Which is where I'm at now.
Here's what I've done. I completely wiped my Fat32, Ext2, and Linux_Swamp partitions using Gparted. I completely wiped the phone using Cyan 1.4 Recovery. Yet no matter which Mod I use my touch screen doesn't cooperate, AND (no matter which mod I'm using) when I try to launch basic apps (dialer/phone, some settings menus, etc) I am notified that, "android.process.acore" has stopped. Without fail. It ALWAYS does this when attempting to access the dialer/phone. I would be more than happy to take some time troubleshooting the touch screen IF my damn dailer/phone would work. But it does not.
I read on some other forums about there being 2 compcache files for someone who had a similar issue. That's slightly above my head, though, and I'm not quite sure how to go about checking that and/or deleting one. Really, I just want to be able to access my dialer/phone app for the time being. Then I can take some time to trouble shoot the touch screen.
Anyone have any ideas about the process failing, or the compcache affect?
Also, I'm using 1.33.2005 SPL.
Thanks
Click to expand...
Click to collapse
I realize this is an old thread but did you ever get the issue figured out? My phone did this just last night
Alright as suggested earlier in the thread it was a hardware issue. I found that my touchscreen had become unplugged and was causing the errors.
Sorry to bring this guy back from the dead but I figured I would educate a few people one a common touch-screen problem.
Yeah, 90% of the time it's the adapter you're using. Being a G1 owner with lots of mini-USB chargers i found the same problem. Also being a tech rep at t-mobile, i've had lots of calls revolving around this and fixing it.
The G1 uses a 1000mA charger (1A). For me, the touch-screen going haywire/unresponsive seemed to get more severe as the the chargers specs went lower. An old Motorola charger at 500mA was ridiculous. Talking to customers with the exact symptoms and hardware, eventually lost all functionality of the touch screen.
On a side note, it's not just the G1 that has problems with the wrong charger. A linksys router I have has a standard power port connection type in the back but requires a bigger amp adapter. hooking the wrong one up will cause complete failure. In many situations, not enough energy is just as detrimental as too much energy. One last example: Take a big 10" sub driver, hook it up to a crappy 300W amp, you get an overheated coil and eventually a busted driver.
So, lesson is, just because it fits doesn't mean it's safe to use. I never mix and match adapters with any device ever because of the risk of damage.
Hey all, I bought a Captivate when it first came out, and I loved it. I rooted it and have been playing with roms since forever.
A couple months ago, my computer stopped recognizing the USB device, and after much troubleshooting I figured it was the USB port on my Captivate.
I called AT&T, and they told me I had 7 days left on my warranty, but that they could offer me an Atrix at a very low rate instead of replacing the captivate. I decided to bite, and now I have my Atrix, and I love it, but I still have this Captivate and I'm trying to figure out what to do with it.
I'd like to sell it, since it's not really doing me any good, but were I to do that, i'd at least like to either return it to stock, or install like CM7 on it.
Do you guys think I could still exchange it at the local AT&T branch?
Is there a way to install either the stock rom or CM7/MIUI on it without a working USB port?
Anything I didn't think of?
I can get files onto it via both micro sdcard and through the wireless, and the rest of the phone works fine.
Maybe if I switch my default phone back to the Captivate and ask them to replace?
What rom are you on now? And which boot loaders
Sent from a phone controlling a computer controlling a different phone
Same situation
It appears I got some water from the rain in my USB port, and I never bothered to close my little slide cover thing. Anyways.. Things were very weird last night. First the camera would crash, then the phone stopped booting up. Finally, and I think when things finally dried out.. it booted, but the USB which worked before the boot issue no longer works. It charges.. but I think I fried my port.
Now I would like to take this back, problem is.. my phone is rooted, and I doubt AT&T will grant me a new phone with a non-stock ROM (running CyanogenMoD7 android 2.3.7).
Im lucky to have a service center located right near me, so i don't have to go through the hassle of the phone tech run-around. I just need to go there and I should be able to get a new device since I still am under warranty.
My problem is this.. Should I just "drop" the thing to avoid them freaking out because my new ROM?
John
If it's willing to charge, there's still a chance you might be able to get data to the phone. Have you tried putting the phone in a bag of rice (to make 100% sure it's dried out) or tried swabbing the USB port with something thin enough to fit in the usb port, wrapped in a piece of cloth with rubbing alcohol on it (to clean the USB contacts)?
If neither of those things work, and it still won't connect, then I guess the decision to perform a non-controlled hardware restructuring is up to you, and whether you're willing to risk the cost of your phone.
Hey guys, got a busted i896 from someone, with the lcd AND digitizer both destroyed, phone boots up properly, can hear the audio when it boots, and notifications when i text it. My brother's gf has the EXACT same phone, (i896 from rogers). I have tried several ideas to turn debugging on, to no avail, my final thougt on this is maybe i could access the broken phone's system/data by placing the motherboard (from the broken screened one) into the fully functional phone? (as in swapping ONLY the motherboard).any thoughts on this? Would like to give it a shot, but as the fully working phone is her everyday phone, i am a little worried about crashing the working one.
Just to clarify, the main question is : if i take the motherboard out of the broken phone and put it in an identical phone, will that present any problems that may damage either device?
And also: i would assume the nand memory (system, data, etc.. (obviously not sd)) is located on the motherboard itself somewhere. Would this be a correct assumption to make?
If this were to work, my goal is simply to turn on usb debugging and maybe root, then put the boards back into their original phones and use the broken one for development purposes, so any other ideas to turn on usb debugging please post them (keeping in mind i can't use adb whatsoever because usb debugging is off, which is why i need to turn it on. And lcd is broken and digitizer completely unresponsive). The phone is a completely stock samsung galaxy s captivate (sgh-i896).
Sent from my GT-P7500 using xda app-developers app
khemical7 said:
Hey guys, got a busted i896 from someone, with the lcd AND digitizer both destroyed, phone boots up properly, can hear the audio when it boots, and notifications when i text it. My brother's gf has the EXACT same phone, (i896 from rogers). I have tried several ideas to turn debugging on, to no avail, my final thougt on this is maybe i could access the broken phone's system/data by placing the motherboard (from the broken screened one) into the fully functional phone? (as in swapping ONLY the motherboard).any thoughts on this? Would like to give it a shot, but as the fully working phone is her everyday phone, i am a little worried about crashing the working one.
Just to clarify, the main question is : if i take the motherboard out of the broken phone and put it in an identical phone, will that present any problems that may damage either device?
And also: i would assume the nand memory (system, data, etc.. (obviously not sd)) is located on the motherboard itself somewhere. Would this be a correct assumption to make?
If this were to work, my goal is simply to turn on usb debugging and maybe root, then put the boards back into their original phones and use the broken one for development purposes, so any other ideas to turn on usb debugging please post them (keeping in mind i can't use adb whatsoever because usb debugging is off, which is why i need to turn it on. And lcd is broken and digitizer completely unresponsive). The phone is a completely stock samsung galaxy s captivate (sgh-i896).
Sent from my GT-P7500 using xda app-developers app
Click to expand...
Click to collapse
Yeah, the processor, flash, etc. are on the mb. Swapping it would be a messy job and might damage both devices, so I would advise you from tampering with the internals.
nirajpant7 said:
Yeah, the processor, flash, etc. are on the mb. Swapping it would be a messy job and might damage both devices, so I would advise you from tampering with the internals.
Click to expand...
Click to collapse
I already went ahead and did the swap after a bit of research, everything went smoothly.
Sent from my GT-P7500 using xda app-developers app
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