or at least not documented in a good place.
heres my long story/adventure for the past 2 days.(the short story is after the break\/ \/ \/)
picked up a "broken" htc dream from craigslist... phone is stuck on rainbow bootloader, so everything online is saying flash the dreaimg.nbh file on the root of a fat32 formatted microsd card. then other info about if it fails. but no info if it completes, and verifies every line and say ok, then do the command to reboot, and it still goes into bootloader... as if the camera button is stuck!! great idea, ill remove my camera button from the main board to test that theory that some ppl can force on you like a religion... phone still started in boot loader mode... with camera button desoldered from the phones main logic board(or whatever the official term for it is) so to the guy who said he didnt care if it felt like the camera button is clicking fine or not, somethings wrong with it, no ifs, ands, and buts about it. you might be wrong....
anyways, i picked up another broken g1, this one with a cracked lcd. the screen was half visible, so i tested to ensure it booted before paying for it. it booted fine and fast, i was in good luck, and the radio was already at 2.xx.xx.xx, so dangerspl wasnt a problem. so i took apart phone two and replaced only the main board in each phone. mainboard 1 in phone 2 boots fine(with camera button desoldered from mainboard), and mainboard 2 in phone 1 goes to the bootloader screen, but will still go into recovery mode with no problem. i then just swapped out the front button board from phone 2, over to phone 1, with phone 1's original mainboard. and it boots perfectly fine. so i have come to the conclusion that the front board is what make it not function properly. i have since upgraded mainboard 1's radio to 2.xx.xx.xx, dangerSPL, cyanogenmod 6, psgroove.....
______________Short Story___________________
so i guess what i am saying is if your phone seems like the "camera" button is stuck, cuz the phone isnt bricked due to its other responsiveness(recovery manager), you might need to replace one of these following two items.
This is what i believe to be the main culprit, but i havent tested each peice individually yet, so i could be wrong. and this is the other part that you might consider replacing.
and to prevent a few questions, both of these phones were tmobile US phones, not european or rogers or any other provider one.
That's some good ol' fashioned trouble shooting!
yes, much trouble, but no shooting.... but it was well worth it..
What I said is it MIGHT be the camera button, or it MIGHT be the BACK button. BOTH of those buttons can cause it to jump into fastboot!
And so rather than TRYING BOTH, you decided to try ONE and then give up and replace the entire board containing the button.
Well guess what you've proven: It was the BACK button.
Just like I said it was.
Related
So, i'm usually quiet on these forums. Just reading, trying roms, etc. But here is something that has me stumped. Last thursday my phone crapped out. When i woke up and looked at it (it was connected to my laptop/charging) Applications were opening left and right, i couldn't close any of them because stuff kept opening. I tried to soft reboot it and it didn't help. Once it rebooted stuff started opening itself at random again. I ended up pulling the SIM and battery out and leaving it for 5 minutes. When i put it back and powered it up the touch screen no longer worked, but apps weren't opening on their own.
What gives?
I have hard reset (which means it's waiting for me to touch the screen to setup my rom), i have also taken off the screen protector (in case it had something stuck under it. Neither of these things helped. Per the forums I got a new screen, just put it in, and the touch screen doesn't work still... I'm drawing a blank here can anyone give me some advice. Going back to my Prophet for the time being but I HATE not having a keyboard (and it's slower than molasses)
have you tried flashing a new rom via sd?
Check that the screen protector has not moved under the front bezel and keeps pressing your touchscreen.
Robert
I have totally removed the screen protector and even replaced the screen for that matter so I dont think that's it. I haven't tried flashing a new rom. I just found it odd that this has worked for so long and now I get what appears to be hardware problems. As for flashing Via SD memory, is that better than doing it via cable for some reason? I'd be willing to give it a go...
Any other suggestions?
fiddelm3742 said:
I have totally removed the screen protector and even replaced the screen for that matter so I dont think that's it. I haven't tried flashing a new rom. I just found it odd that this has worked for so long and now I get what appears to be hardware problems. As for flashing Via SD memory, is that better than doing it via cable for some reason? I'd be willing to give it a go...
Click to expand...
Click to collapse
Similar problem happened to my Kaiser phone, although no multiple files opened, the phone just won't react to any touching, not stylus pen either. So I first soft reset, then hard reset, none of them works, now the phone can Sync alright, but the screen just stands on the Window Mobile screen, saying "Tap the screen to set up your window mobile device"
I only have this new phone for <3 weeks.
I went to HTC site, want to download a latest ROM file from them, after typing in the S/N, it won't let me, saying that ROM is not suitable for my phone.
So now I am download ROM file from this site, will choose one to flash the phone, see whether it works.
I will call HTC tech support tomorrow after Thanksgiving, see what they suggest
Hope some gurus here can also make some suggestion, Thanks!
Well I replaced the LCD and the new LCD works great, but the screen still doesn't respond to touches. What gives?! I hard reset and I got past the windows screen alignment thing by creating a welcome.not file but it's still pretty much worthless w/o a touch screen. Anyone have any suggestions?
Whoa, i thought something odd was going on. Never mind i got entirely the wrong idea.
Ha, not the case.
Anyone know if a flex cable would fix my issue? I dont really know what the felx cable is for but i've seen posts about people replacing them w/ LCD problems. I don't know if it is touch screen related or not, and i'm kind of tired of buying parts that don't fix my problem
please just flash a new rom whch ever you want (for some reason i thought you said that it keeps restarting your device because if that was the case the only option you would have was to flash via sd as activesync would load long enough for you to get a connection to flash from the computer)..trust me just try it..what have you got to lose
I reflashed one yesterday actually. The newest HyperDragon (which is looks like a new one is available today) It wasn't rebooting but initially windows were popping open left and right so i restarted it a couple of times(which i first had the problem, not yesterday) Yesterday it worked like any normal rom w/o the ability to touch. Anywho, after the flash of a different rom. No luck. I'm thinking it's a hardware problem of some sort but as i've already replaced the LCD i have no idea what?
yah thats sounds funky..you can bring it in for a warranty exchange either at a local DSC or over the phone (that is if your with att) and if not call HTC..all devcies come with a 16 or 18 month warranty
Well I called ATT yesterday, apparently I purchased the phone On Oct 17th 2007 which means It's out of warranty (apparently it has a 12 month warranty?) So it sounds like I'm SOL. So, i guess I'm off to ebay to try and fine a phone that I can canibalize to try and get mine going again.
touch screen
this may sound dum but when you replaced the screen did you replace the touch part as this is different from the screen
Well I picked up this
http://www.blackberry8100parts.com/...B3-NEW-HTC-TyTN-II-KAISER-P4550-_p_35-70.html
which includes the digitizer (from what I know it's all one part when they send it to you) The screen has the digitizer built in. So i replaced the part they sent me.
I just stated having this issue. My touchscreen stopped responding to touches over the weekend while the keyboard was extended. I just took the phone apart to make sure everything was connected right & put it back together, & now the touchscreen doesn't work at all. This sucks!
Any news? i'm having the same problem: no response at all, stuck at "Tap the screen to set up Windows Mobile-based device"
An interesting problem with screen
well my tilt fell out of the car holster while using gps and i suspect the screen hit my gear shift. I didn't notice anything odd after i put the battery back in it (yeah it fell that hard lol). Later that night I went to check mail and noticed something not right. Turns out my screen seems to have been pushed in a bit. Well here's the issues I've noticed so far: All the touch responses seem fine except for 1) the screen alignment doesn't register taps, but otherwise the touchscreen works and 2) on the htc home screen, I can't tap the house icon unless I tap any other icon first.
Initially I thought there was some pressure or deformation right at that particular spot, but it reacts the exact same way in landscape mode. I can't tap the house icon first; I have to tap something else first, then the icon works fine until I open a program or something and go back to the home screen. Then I simply have to tap weather or something and then home.
I'd reflash the rom or do a hard reset, but the screen alignment didn't work when I tried it so I didn't want to get stuck at the "tap your screen to begin" part.
Any ideas or do I just need to buy another screen or maybe just the digitizer. the amount the screen seems recessed is maybe a millimeter at most. Just enough so that I noticed a difference when touching contacts just above the housing. I tried cleaning by using a business card and running between screen and housing. Ohh... and one more thing... when I open the cube and then close it, I get what I refer to a static frazzle for split second and it goes back to normal. That only happened a couple of times after the business card thing. Do you think I just loosened a connection? damn... I still haven't taken it apart yet. Think I need to. Any help appreciated.
If your screen does not work, you can still use your phone. There is an app that you use on your computer that acts as the touch screen. This also works when the screen craps out.
http://www.sparus-software.com/spip.php?page=download&lang=en&ref=at&t=tilt
(EveryWAN Remote Support Personal Edition - Free download)
yeah -- my touchscreen didn't crap out totally, it just got muffed up when I dropped it a bit. Well, i went ahead and installed codefreaks remote screen alignment thing and did a hard reset. Well, the hardreset did the trick w/out the need for anything else. The alignment worked and everything. So, i'm back in business. Everything seems to work properly, except that my screen is still recessed a tad; but, that's not a big deal really.
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.
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
ok heres my problem. happened about 7+ days ago... well i took it off my computer charger and the screen was messed up when it was closed but when i opened it "Flipping keyboard out" the screen worked fine... so posted on here i had this issue... I at first thought it was a battary problem so i purchased 3700 MaH Tripple life battary... once i got it 2 days ago same problem yet worse.... so heres how it looks
~Turn On Phone
-No T-Mobile Screen Showing
-once Rom Loads it shows yet its Fuzzy like its missing pixels but cant be the problem because i never dropped it.
~Rom Loads
-Screen Still Fuzzy or Scribbly if that helps... can do some basic functions can mount it when I hibernate it and turn screen back on... but doesnt do much
From there tried going into BootLoader "Camera+Power"
Took out battery a few Times Placed it back in
bootloader will come up with backlight but thats it so its a black screen... cant make any Functions.
I can however get into Recovery Mode... yet it looks Fuzzy aswell...soo
what Im asking all of you guru's is... "is my phone bricked..."
Running SuperBad CM5 1.2.5 Test 4 currently not sure if i installed Danger SPL and I cant Check... i had the radio 2.23.02 etc... please reply dont wanna spend 150$ for a new g1... when there could possibly be hope
*Bumping* i had to bump my last like this aswell... Moving out of state in 7 days so Kinda wanna Fix this issue a little Faster Can anyone take a Look Into This
You're phone is not bricked. Sounds hardware, though, not software. You can either warranty if you still have one, or open it up and make sure all cables are securely connected. If both of these fail, you're in the market for a new G1.
ok so what kinda screw driver do i need lol.. i know sounds n00by i used a eyeglass one that seems to be no help... looks like a allen wrench..?
You're going to void the warranty by opening it. Recovering your phone back to stock and sending it in will most likely get you a replacement if you're still under warranty. If you want to disassemble it, you can try this video hxxp://youtube.com/watch?v=3PdhXx3g9nU just replace hxxp with http.
I've replaced my phone twice, and each time I get another they extended my warranty. I've had it since Nov 08 and my warranty is still good for that reason. You might wanna check if your warranty is still good before opening it.
It does sound hardware related but since you can get to recovery can you try a wipe and see if that will do any good.
As we all know, the phone is pretty darn well put together and surprisingly durable. But, unfortunately, it is not invincible. About a month and a half ago I cracked my screen. The phone had a case, but it wasn't anything hefty (the HTC Double Dip case). The phone was still completely usable, but I like the phone and wanted to keep it nice so I decided to replace the screen. I ordered the screen + framework assembly and it was about $55. In the past when I have replaced screens on a few iPhones and an ASUS tablet the parts were quite a bit cheaper, but whatever. My phone is the black model, but I decided to try something different and ordered the new part with red speaker grills. Most guides and such said that the M7 is a pretty hard phone to repair, but I have worked on a couple other phones before, so I gave it a go. After many, many hours of carefully prying apart the phone and transplanting the logic boards to the new screen framework I put it all back together and powered it up. To my surprise the phone powered up and the screen worked fine. (And let me tell you the red and black looks damn good). The first thing I noticed was that vibration didn't work. A bit annoying, but the phone looked good enough that I could get past that. Next I tested the speakers and noticed that at full volume the speakers sound a little bit messed up. Again, a little annoying, but I'm not a professional so I wasn't overly disappointed. Then came the real problem...
THE REAL PROBLEM:
When I put the SIM card in the phone didn't detect it. After a reboot it still didn't detect it. After a factory restore it still didn't detect it. Perhaps the ribbon cable connecting the SIM reader to the board was not all the way secured? After how hard it was to take the phone apart the first time I was not a fan of the idea of doing it again. But alas, the next day I opened the phone back up super carefully so not to damage the new parts. It was thankfully a little bit easier the second time. I made sure the SIM reader was all the way connected, but the phone still wouldn't read the SIM. I pulled the old SIM reader out from the old screen framework assembly and plugged it into the board, but the SIM was still not detected, indicating that the new screen did not come with a bad SIM reader. Has this problem happened to anyone else? What steps should I take? I now have really nice looking M7 that is essentially useless.
So does anyone have input on this?
Pr.TOSHIBA said:
So does anyone have input on this?
Click to expand...
Click to collapse
Same thing happened to me. Also swapped out the old reader without any luck.... Any update on this?
Does it detect it at all? Like ask for the pin code if you use that?
Do you have to disconnect the battery when replacing the screen on this phone? I know on some phones I repaired I had to manually set the current time and date (resets to year 1970 or something like that if you disconnect the battery) to get a signal.
Otherwise I have no idea