1. bigeazy000's Avatar
    I am new to these forums, I was wondering if someone has seen my problem before...

    I have an Iphone 3g 16gb with a replaced front glass/digitizer, was running jailbroken 2.2. It was working great for a while (months) since the glass was replaced, but then last week, I noticed that the proximity sensor was not working. So, I opened up the phone again to see if something perhaps was blocking the sensor, or if the cable had become dislodged. Anyway, when I put it back together, it didn't boot up! So, I plugged it into my macbook, and itunes could still see it fine and sync with it, so I knew it was still "on". That being said, I tried to toggle the vibrate function just so see if it would vibrate and nothing, just a phone that appeared completely off, except for being able to see it in Itunes.

    Next I tried flashing it with 2.2.1 (regular methos and DFU) back to factory defaults to see if that would fix it. Still nothing. The "geniuses" at the apple store wouldn't help me either, because apparently the water-sensitive tape at the bottom got wet at some point. I am sure it hasn't been wet or in water, at least for several months. So, what could it be? It's possible too that I damaged the LCD ribbon cable and/or proximity assembly. If either of those are bad, could it cause this behavior? I would think that even if one or both of those were bad, I would still feel the phone vibrate when I flip the side switch, since itunes sees it as "on".

    Update: Today I replaced the LCD and proximity sensor, same results. So, I d/l'ed itunes for Windows, tried re-imaging it in DFU-mode windows. I was able to do so, but same results

    Any help would be greatly appreciated....
    2009-04-14 06:58 AM
  2. ALL DAY's Avatar
    Well, since your water sensor was tripped, it could have been water damage from months ago finally taking a toll. A lot of the time after getting it wet it will be fine for quite a while and then just stop working... If you're sure you're putting everything back together correctly, other than that I don't know what your problem could be. Sorry.
    Respect your elders.
    2009-04-14 08:24 PM
  3. bigeazy000's Avatar
    Thanks for your reply. For what its worth, it is u/l'ing crash/panic files to itunes when it syncs. Here is the beggining of the iphone.crash dump:

    Incident Identifier: 5BADB589-CAA5-42B3-853D-E842E79B47A8
    CrashReporter Key: 869cdd1183a9b66eb65cefda7dc94bbfdae8ddaa
    Process: SpringBoard [145]
    Path: /System/Library/CoreServices/SpringBoard.app/SpringBoard
    Identifier: SpringBoard
    Version: ??? (???)
    Code Type: ARM (Native)
    Parent Process: launchd [1]

    Date/Time: 2009-04-14 10:27:38.810 -0700
    OS Version: iPhone OS 2.2.1 (5H11)
    Report Version: 103

    Exception Type: EXC_CRASH (SIGABRT)
    Exception Codes: 0x00000000, 0x00000000
    Crashed Thread: 0

    Thread 0 Crashed:
    0 libSystem.B.dylib 0x3145dc58 0x313fa000 + 408664
    1 libSystem.B.dylib 0x3145dc46 0x313fa000 + 408646
    2 libSystem.B.dylib 0x3145dc3a 0x313fa000 + 408634
    3 libSystem.B.dylib 0x31478424 0x313fa000 + 517156
    4 libSystem.B.dylib 0x31462f44 0x313fa000 + 429892
    5 GraphicsServices 0x3156c464 0x31564000 + 33892
    6 GraphicsServices 0x31569f58 0x31564000 + 24408
    7 UIKit 0x30a4fa14 0x30a45000 + 43540
    8 UIKit 0x30a591d0 0x30a45000 + 82384
    9 SpringBoard 0x000031e8 0x1000 + 8680
    10 SpringBoard 0x000030cc 0x1000 + 8396

    And here is the beggining of the panic.crash file:

    Incident Identifier: 60BD8325-D84F-4726-B3E7-70887C5FC8C1
    CrashReporter Key: 869cdd1183a9b66eb65cefda7dc94bbfdae8ddaa
    Date/Time: 2009-04-14 10:28:54.314 -0700
    OS Version: iPhone OS 2.2.1 (5H11)

    Debugger message: WDT timeout
    9s ago: 1705m10000004 1665u0 1665u0 1665u0 1665u0 1605m10000004 1505m10000004 1465u0 1465u0 1465u0 1465u0 1405m10000004 1305m10000004 1265u0 1265u0 1265u0 1265u0 1205m10000004 1105m10000004 1065u0 1065u0 1065u0 1065u0 1005m10000004 904m10000004 865u0 865u0 865u0 865u0 804m10000004 704m10000004 704c76 703g2 665u0 665u0 665u0 665u0 644d76 603m10000004 603g2 503m10000004 502g2 465u0 465u0 465u0 465u0 402m10000004 402g2 302m10000004 300g2 265u0 265u0 265u0 265u0 200m10000004 200g2 100m10000004 100g2 64u0 64u0 64u0 64u0 0m10000004 0g2
    OS version: 5H11
    Kernel version: Darwin Kernel Version 9.4.1: Mon Dec 8 20:59:30 PST 2008; rootnu-1228.7.37~4/RELEASE_ARM_S5L8900X
    iBoot version: iBoot-385.49
    secure boot?: YES
    Paniclog version: 1
    Task 0xc08b6ce8: 2133 pages, 72 threads: pid 0: kernel_task
    thread 0xe029e410
    kernel backtrace: ec423ae4
    lr: 0xc00670b5 fp: 0xec423b14
    lr: 0xc006731b fp: 0xec423b2c
    lr: 0xc02a4535 fp: 0xec423fa8
    lr: 0xc00659f8 fp: 0x00000000
    2009-04-15 02:42 AM
  4. cpjr's Avatar
    ^That tells us nothing.

    Since its been opened, its basically impossible to tell whats wrong with it without having in hand.
    2009-04-15 02:57 AM
  5. bigeazy000's Avatar
    well, I am an engineer, and can give you more information if you like. I can tell you that I completely disassembled the unit, checked the motherboard pretty closely for water damage, and verified that the battery is holding a charge correctly. What would you look for if you had it in front of you?
    2009-04-15 03:15 AM
  6. cpjr's Avatar
    Well, lets just say since the water sensor did show moisture damage...that it quite possibly has water damage.

    In which case there could be many places internally, or on the mainboard that could be effected.

    To find out it would take probing along the mainboard checking all the micro smd's and trans.

    I would have said (at first) it was the LCD, but you said that you replaced that. And also, that wouldnt effect the vibrate feature.
    2009-04-15 03:22 AM
  7. doctoriphone's Avatar
    Are you still getting sync from itunes? If so, don't give up on it just yet.

    For the record the vibrate does not actually function if the LCD is faulty or not connected at boot. In fact, neither does the ringer.

    I would suggest that you find another LCD to test or check for damage on the logic board LCD connector. When separating the phone be very gentle, and even more so when removing the LCD connector.
    2009-04-23 03:25 AM
  8. cpjr's Avatar
    For the record the vibrate does not actually function if the LCD is faulty or not connected at boot. In fact, neither does the ringer.
    No offense, but thats not actually true. The phone will function just fine with a bad LCD, you can actually navigate the phone (obviously if you can do it without looking at the screen), make/receive calls, vibrate and speakers work. The LCD is a separate component.
    2009-04-23 03:49 AM
  9. doctoriphone's Avatar
    Depending on the meaning 'bad', then possibly. In the case of no LCD being connected, the phone will respond very similarly to the way described in this thread. The same is true of an LCD damaged to a sufficient degree or one not connected properly due to ribbon or connector damage or otherwise. Feel free to try. The phone will respond if the LCD is pulled when the phone is powered up, but not when it is pulled and then powered up.
    2009-04-23 03:57 AM