[Q] 5158N replaced with 5158N.. no joy - Transformer TF300T Q&A, Help & Troubleshooting

I decided to learn tablets..so I took on a TF300T repair for a friend to start learning.Looks like this TF300T was the wrong choice.
Background.
TF300T Original digi was shattered and was barley working. possible ghost touches
Andriod 4.2.1
Original Digi 5158N FPC-1 06WW 2010 on the sticker JA-DA5158N-IBB 18140-10120500
I did check a few post before I bought a digitizer saw the issues with mixing different versions. So I went with an ebay digi from china with the 5158 model. I received the new on visual inspection it looks exactly the same. New Digi revived no white label but printed in small black ink on the new digi says 5158 12.28 D4\ 11205019701012D. At the bottom in white ink it says 5158N FPC-1 06WW 1225. seems like a match
I replaced the cracked screen went pretty smoothly. I put double sided tape on the digitizer plastic frame after cleaning the old junk off. I did not remove the top cover from the new tape,I just put the unit back together without screw so I could make sure it worked the plan was to test, re tear down then glue/tape the new digitizer down after I tested. Well I get no touch after the 5158N to 5158N swap.
unit loaded the first time and updated the camera firmware but not the touch
I did check the fuse on the main PCB around the LCD/touch connectors and found no burning.
the first time I powered the unit up with the new digi the screen jitterd a bit but no touch. after resetting the cables still no touch. the jitters stopped.. So at this point I ordered a USB adapter to connect a mouse.
This morning I received the mouse connector. went into settings it said. Touchpanel version ELAN-3011-4822 Kernal version 3.1.10-g215ac8bf
Also had a message about DMClient has stopped on first boot. went away after a few reboots.
Today I tried a cold boot after reading some post. It booted up showing the three icons RK/ANDRIOD/WIPE.. up at the top I got the following line:
andriod cardhu-user bootloader <1.00 e> released by "U5_epad-10.6.1.27.5-20130902" A03
key driver not found...booting 05
starting Fastboot USB download protocol
at this point in the cold boot booting the mouse and keyboard seem to be unresponsive. If I hit vol up I get booting kernal recovery image then i get an android logo and big error message sits there and then boots up normal.Still no touch.
After 1st cold boot I went back to check the touchpanel version and now it says ELAN-0000-0000 the Kernal version is a tad different now its 3.1.100-G215ae8bf
Is this normal and Ive missed something? Could it not be working because I ave not glued the new 5158 to the plastic frame?
Do i need to root the device then flash the touch firmware? Seems to me that it should have just accepted the new 5158 and worked that's why i spent the extra cash to avoid this kind of issue.
Any words of wisdom from some TF300T gurus would be a big help!

Forgot to mention at the time i replaced the touch digitizer I did not know to turn the service switch off. the battery was drained as it had ran down to nothing because I could not touch the power off. hopefully this didn't screw me?

CompJock said:
Forgot to mention at the time i replaced the touch digitizer I did not know to turn the service switch off. the battery was drained as it had ran down to nothing because I could not touch the power off. hopefully this didn't screw me?
Click to expand...
Click to collapse
Barring any hardware malfunction, the only way to find out is to root the thing and flash the firmware anew through ADB. This issue has been discussed so many times, it hardly warrants a new thread.

graphdarnell said:
Barring any hardware malfunction, the only way to find out is to root the thing and flash the firmware anew through ADB. This issue has been discussed so many times, it hardly warrants a new thread.
Click to expand...
Click to collapse
Thanks for the response. I apologize for the new thread, most of the other threads seem to deal with swapping mis matched digitizers and then flashing the rom. I thought because mine was an exact digitizer match it may be a different situation. i was just hoping that my experience had rung a bell and someone may point out my error.
At this point I'm pretty sure its not hardware the microsd card reader that shares the touch digitizer board works. and the touch ELAN chanaged to 0000-0000 only after I did a cold boot.

CompJock said:
Thanks for the response. I apologize for the new thread, most of the other threads seem to deal with swapping mis matched digitizers and then flashing the rom. I thought because mine was an exact digitizer match it may be a different situation. i was just hoping that my experience had rung a bell and someone may point out my error.
At this point I'm pretty sure its not hardware the microsd card reader that shares the touch digitizer board works. and the touch ELAN chanaged to 0000-0000 only after I did a cold boot.
Click to expand...
Click to collapse
Hi, i have the exact same issue. Also the system/etc/firmware/touch folder does not exist. I made it and put inside fw. The device whenever reboots it doesnt automatically update fw from the touch folder as it should. Through adb shell i always get error. Seems like the mobo not recognising digitizer. I also put the old broken one and still the same ELAN-0000-0000 i also forgot the off switch but i cant find any "weird" coil. Any help would be appreciated. I have read the other thread and learned a lot but nothing specific to this problem. Also my micro sd port was not working and i really thought was the pcb, but then i manually updated to the latest asus fw (from 4.1.1 to 4.2.1) and instantly micro sd works. When it wan on 4.1.1 i could find the touch folder and 04-3021-7038.ekt was inside (no label digitizer was the broken one and the new i bought as well). After the 4.2.1 update the touch folder disappeared and had to remake it. Tried with 04-3021-7038 and 02-3011-4820

Related

Att Fuze black screen need help please! Not a bad flash issue.

Hi all,
I am at my wits end on this problem if anyone can offer any adivice it would be greatly appreciated. So let me give a recap of what has occured thus far. The water damage tag for some reason turn pink thus i am unable to get warranty exchange. I am pretty certain that the phone has never been expose to any water of anything of that sort, but i do live in houston, tx so might be humidity or what not that cause the tag to turn. Anyways.
1. This all started after i flashed RRE 5.2 RC3. Initially after a successful flash everything seem normal and fine. Then next morning i woke up to a frozen screen with many verticial lines running up and down the screen was almost unreadable. Initially i thought it was a bad flash or just random lock up. I did a hard reset and tried to enter the bootloader. Black screen, it does seem like the backlight is coming up but nothing on the screen. I can hear the phone power on and boot successfully into windows. Activesync connects i can browse the contents of the phone.
2. After flashing to stock att rom and stock htc roms same symptoms. So at this point i am thinking crap bad LCD screen. so I ordered both the digitizer and lcd screen for good measure. I replaced them hoping that a bad LCD was all. replaced both screens and i powered on the phone. same problem. black screen. The phone still powers on and boots into windows. Activesync still connects and i cna still reflash the phone.
3. I work extensively and do both desktop pc and notebook repair. I am not new to dealing with small electronic repairs. but at this juncture i am unable to identify the cause of hte malfunction. i am hoping maybe some of the gurus here might be able to shine some light on the subject.
Thanks in advance for any help.
I would have followed the same approach; your description makes it sound like it might be some kind of backlighting issue at first read. I'm inclined to think it might be a cold connection (bad connector) on the main board.
Silly question, what happens if you power up the phone with the keyboard exposed?
*EDIT* Not sure if you have been here yet: http://www.mikechannon.net/
Cheers,
i just tried to power up the phone with keyboard exposed. Powers up the same as with the keyboard hidden. Still boots up fine but black screen. I already have the service manuel dowloaded. i have checked around with several repair places both local and on the web. Seems like no one has any parts for the att fuze/touch pro gsm except for the lcd and digitizer and a speaker.
its quite possible that it is a main board but as the same time it might be something as simple as a ribbon cable. i have contacted htc about doing a possible repair and they want wayyyy too much for just a main board repair almost $400 USD.
Anyone have a bricked/ non working touch pro they would like to sell ? =P
fkoong said:
its quite possible that it is a main board but as the same time it might be something as simple as a ribbon cable.
Click to expand...
Click to collapse
Could be a bad ribbon cable ... and firmly pressing around the front/back of the unit shows no change?
pressing the phone front and back show no changes to display. in a very dark room I can see that there is light emitting from the display but its just the screen is not displaying anything visable. this occured both before and after i changed out the screens. I'll do another visual inspection of all the boards to see if there is any bad resistors burnt out circuits etc.. but i didn't notice anything mentionable during my first 2 inspections. Maybe 3rd time is the charm.
Thanks for all the feedback thus far Hilaireg it is quite appreciated. All this venting has at least made me feel 1000% better than after i replaced my lcd and still same problem at least i don't feel like a complete idiot!
Sorry I couldn't be of much help ... you've done all the steps a seasoned hardware person would do.
Do post back to let other folks know if you get it back up and running.
Cheers,
you have a pm fkoong.
I have possibly the same problem. Phone got wet, dried it out for 2 days (in a container of rice). Phone worked but had "water marks" on screen that disappeared after two days and everything was fine for about 2 weeks. Then one day (happened to be humid misting rain eve in Charleston) the screen is blank (hint of backlight only). A soft reset and it seems OK for about 1hr, then blank again. The hard resest screen displayed OK (readbale text etc), but didnt work. But as I write this, I retry to document it results correctly and the NATF ROM is reloading and the screen works! We will see how long!!
Well.. not that long, the end of the ROM load and it went blank again, seems like a video driver problem. The Press VoluP to boot does show some red artifact.
Trying hard reset again (No SIM no uSD)
The NATF v4.4 loads and gives me the Tap screen, Align Screen, stylus, loads customization, opera, tf3d, then loads a bunch of files under ...... and then the screen goes blank again, seem like what happened last time, so Ill try loading a fresh ROM copy... later

i9023 - Replacement screen touch input not working

Hi,
I recently dropped my i9023 and smashed the glass.
Bought a new screen with digitizer from global direct parts (www globaldirectparts com/Samsung-GT-I9023-LCD-and-Digitizer-Assembly-p/smsng6102150.htm)
Having put the new screen in it boots up fine and displays perfectly but the touch screen is not working at all and I can't do anything. If I put my smashed screen back in touch input works fine.
I've flashed back to stock I9023XXKB3 and I9023XXKB1 firmware, but nothing seems to help.
The ribbon to the screen doesn't appear to be damaged and because global direct parts had a minimum purchase of 2 I have 2 new ones and they are both unresponsive.
Anyone have any ideas?
My first idea would be to have the manufacturer fix it.
Sorry you are having trouble getting the touch screen to respond. I too have cracked my screen and would be very interested in your strip down and replacement steps as I am going to be doing the same. If you get time, could you write down your steps. There is a pretty good teardown at
http://www.ifixit.com/Teardown/Nexus-S-Teardown/4365/1
but I am not confident of the last bit of using a heat gun to separate the screen from the frame. Did yours come off easy ?
Yes I could have sent it to an authorized repairer but I would of been without the phone for a a while and it would cost twice as much. Plus I like pulling things apart.
markread544 - I pretty much followed the ifixit guide. however when pulling out the motherboard make sure the front and rear cameras and speaker are loose as well otherwise it wont come out.
I didn't use a heat gun, I just applied pressure until it started to lift, it would of definitely been easier if it had been warmed up but I didn't want to use a heat gun either. You would want to use an adjustable heat one on low if you did, I think a hair dryer would work as well.
I pulled mine a bit further apart then they did, the grey part in the attached pic comes off as well which makes it easier to get the screen out of the front bezel which it is also glued to.
Phone is back together at the moment with the cracked screen but I'll take some photos if I pull it apart again.
same problem here.
i bought an lcd on ebay for i9023 (slcd)
display OK , but no tactil response.
i had MP the OP but still no answer.
if you have any suggestion
thanks
how much for the screen? seems that 9023 is cheaper than 9020
80 euros for the less expensive , about 120-150 for the others
I ended up returning the screens from global direct parts and after about a month they gave me a refund.
After being quoted AU $250to get the screen replaced by an authorized repairer I decided to try again and bought a replacement screen on eBay from a seller called stream_beautiful for $86.
Got it today, installed and it works perfectly. No idea why the original screens from global direct didn't work.
I'm sorry to bump such an old thread, but I was wondering if there was any more information on this issue... I ordered an i9023 screen to repair a friend's phone about 2 months ago and had the same issue as the OP with it; touch input didn't work. I then contacted the seller (forceviewer on aliexpress) and he told me he'd replace it. After sending it back I then had to contact him again and send him pictures of the back of the old screen (with which touch input still works) because according to him there are 2 versions. Now I received the second screen a week ago and lo and behold, it exhibited the same problems. I noticed a number on the back of the screen is different, and the atmel IC (which I assume handles the digitizer input) has a different number on it too, however the seller has now adopted the position that it is definitely the correct display (quote: "If the pictures is right
The item will be right
I just send you the one same with your picturs
There are only two version.
Thanks")
Can anyone shed some light on what causes this? I know the guy's company tests their displays before sending them out, so that's probably not the problem, and receiving 2 faulty units in a row would be a bit weird, so I guess there's actually multiple versions (with a different digitizer controller IC?) which aren't compatible with each other... How do I make sure I'm getting the right one for my friend's phone? And, optionally, how would I go about convincing the seller to take this one back too and send me one that really works?
I'm having exactly the same issue...two replacement screens and touch input non responsive, re-install original and hey presto no problem...what I have noticed is that the part number on what I assume is the digitizer is different...
original -> KJ00423-101228-P00-7F-1
replacement -> KJ00423-101228-P00-5F-1
Yeah, my replacement says 6F-1 at the end, I can't check the original right now because my friend has his phone, but I'm willing to bet it doesn't say the same. Maybe I can make my case with this with the vendor, I'd really hate to have to buy another one of these displays for nothing
Guys,
It's the third SLCD screen that one of my fried is replacing to my I9023 Nexus S, and none of them is working. Yesterday he told me that when he bough the third one, the seller told him to "reprogram" the phone, because the drivers for new SLCD will be installed only then.
To be honest I didn't quite understood him, so, I though that the seller means to flash with a ROM. I did that, I installed CyanogenMod 9, everything went fine, but the touch still not working .
Does anyone knows how the phone could be completely wiped. Meaning everything what is in it to be reinstalled from the beginning....
I don't know what else to do, besides to buy a new phone
Hi All,
Just want to ask if anyone came to the solution yet ...?
Cheers,
no touch
Hello
i have the same problem:
1. The display works
2. But no touch reaction
i had bought a new screen for my I 9023 .
thanks for solutions
Yep, I have the same problem.
Original: KJ00423-101216-P00-1F-1
Replacement: (Not responding to touch): KJ00423-110207-P00-1F1
eBay Seller: mike410512
Bump - anyone sort this issue out?
I know this is an old thread, but since I have a shattered SLCD screen and i'm willing to replace it, i'd like to know what to do in case there's no touch response...
To get touch input again
Hi all,
I have smashed my phone screen twice on my S3 i9300. The first time I had the issue with the touch screen not detecting input but displaying correctly, I had taken it to an authorised repair centre and initially they did not know what was wrong.
There is only one way to "fix" this situation. You must remove the custom recovery and then reflash your phone with the stock samsung rom. Flashing the stock rom with stock recovery should pose no problem as it will be "official" and thus not blocked by stock recovery.
After reflashing, you must do a factory wipe + data reset. This is where you change your screen, making sure not to boot the phone for "the first time". If it does not work, repeat the reflash + factory wipe and try again.
The samsung rom will register the new hardware profile, and touch input will work. Why it works this way is beyond me, but taking these steps when changing the screen on a custom rom will ensure that the touch input works. Perhaps custom roms "borrow" drivers left over from stock rom? I don't know.
You can back up your current rom and restore after messing around with the samsung stock rom and you have gotten your touch screen working properly.
I have tried a whole heap of different "solutions" with this problem and this is the only one that works, and if you are taking it to a repair centre, make them aware that you have a custom rom installed.
Change screen
sinphild said:
Hi all,
I have smashed my phone screen twice on my S3 i9300. The first time I had the issue with the touch screen not detecting input but displaying correctly, I had taken it to an authorised repair centre and initially they did not know what was wrong.
There is only one way to "fix" this situation. You must remove the custom recovery and then reflash your phone with the stock samsung rom. Flashing the stock rom with stock recovery should pose no problem as it will be "official" and thus not blocked by stock recovery.
After reflashing, you must do a factory wipe + data reset. This is where you change your screen, making sure not to boot the phone for "the first time". If it does not work, repeat the reflash + factory wipe and try again.
The samsung rom will register the new hardware profile, and touch input will work. Why it works this way is beyond me, but taking these steps when changing the screen on a custom rom will ensure that the touch input works. Perhaps custom roms "borrow" drivers left over from stock rom? I don't know.
You can back up your current rom and restore after messing around with the samsung stock rom and you have gotten your touch screen working properly.
I have tried a whole heap of different "solutions" with this problem and this is the only one that works, and if you are taking it to a repair centre, make them aware that you have a custom rom installed.
Click to expand...
Click to collapse
Did anybody else use this way?
spanusorin2005 said:
Did anybody else use this way?
Click to expand...
Click to collapse
UP ..
i'm going to buy a screen + digitizer and i would have some advice about this, what code should i look ??? there are only two kind of screen or more ? what should i ask to the seller ???

[Q] ASUS TF300T stuck on boot. Can anyone help?

Hello,
I have searched the threads but cannot find a situation similar to mine so am posting, but apologise in advance if this has been solved before. It's a bit of a long story. About a year ago I was foolish enough to have stood on my TF300T, cracking the screen. The tablet was still working, but it would not register touch. I put it to one side and left the battery to drain. For various reasons I have just got around to replacing the screen.
I found a screen and digitiser of the correct version for my UK TF300T (version G01) and I'd thought the replacement went without any problems, although I was slightly unsure of one digitiser connection. On pressing the power button (I had pre-charged the battery) the screen came to life just as I'd left it as if coming out of sleep rather than being off for a year. It was short lived though and soon the tablet went to black and would not turn on. I thought maybe it was the digitiser connection so went back in to re-fit it. It was only then that I noticed the power switch on the logic board itself under the plastic shell. I hadn't switched it to off before (duh) so did so then, refitted the digitiser cable much more securely,switched the power back on and tried to boot, but nothing happened at all, apart from the power LED flashing orange. After some experimenting (trying to charge the tablet again etc) I found I could only boot by charging the dock and plugging the tab in the dock, but the tablet would only get as far the ASUS screen (not the 3D one, just the flat lettering), with the 'device is unlocked' message in the top left corner and stops there. I can turn it off, but can't boot into recovery at all. And that's where I am now.
Things I have tried - a different logic board from a TF300T's scrounged from eBay which also had a cracked screen (this, weirdly, seemed to have the same problem as mine), swapping various parts out from some other TF300T's (without logic boards) from eBay and contacting the device through Sandix's ADB GUI (after downloading and extracting the SDK), which registered no device.
My best guess at what's happened is that the battery on the tab itself is totally gone (as are the three other batteries I have accumulated) after a last valiant effort and either that going or me messing with the on off switch has some how corrupted the boot process. Is that possible? What do people think? I could buy a brand new logic board, but the only ones I seem to be able to find have some different brand chips on them and appear to be different versions - versions probably not compatible with my digitiser. :S
I am quite a novice here (and maybe poking around the inside of my tab wasn't a great idea, but then neither is wearing boots in the house) so any help would be greatly appreciated! Sorry for the long post, but I wanted to give a detailed report. Let me know if you have any questions. Although unlocked, it is running the stock ROM.
I would make sure drivers are reinstalled properly, by removing the drivers, reboot the computer, reinstall the drivers and then reboot again.
See if that works.
I had something similar happen on a different tablet. That was one from Box.co.uk, but after trying to get it fixed under warranty (and missing the end date by 1 day), I opened it myself. When the charger was plugged in, it showed the charging LED, but it didn't actually charge it.
I don't suppose you've checked the terminals for the battery to the mainboard? On this other tablet, one had broken off. I re-soldered it on, charged it fully and it worked fine.

[Q] XT925 killed during attempt of downgrade from OTA 4.4.2

Hello,
I've had recently broke my XT925 and have question if it’s possible to bring it back to life...
Well from the beginning... I've had glass smashed and during tearing screen from the glass I damaged it, so I've ordered new screen with glass and digitizer. When it arrived, after putting it all together it appears that screen doesn't respond on any touch. My friend read somewhere that it could be solved by flashing the phone again(now I don't know is it truth, and right now it feels like one of the smallest problem I have).
I flashed my Milestone 2 and Droid 4 before so I didn't suspect it be so troubling now.
Because my Motorola had been updated to 4.4.2 and I couldn't find firmware in that version I've decided to downgrade the version to 4.1.2. I found some video with how to modify XML file to be flashable. Unfortunately the video is in foreign to me language (Spanish I guess) and at the time I don't realize, that phone has to be unlocked to do that.
It, start to flash, but when it gets to "boot" it stop saying that it can't be downgraded. So right now My XT925 starts to AP Flash mod with text Flash Failure. I'm able to get to recovery mode and from there try to update phone but like in AP Flash it just don't want to flash Android 4.1.2.
Is there any way to bring it back to life?
I'm guessing that it should run if I could flash files for 4.4.2 but I don't know from where I can get them...
Please tell me do I have nice looking brick or there is a hope for my phone?
Phone is locked, has no other then stock tools installed, and it had system version 180.46.117.XT925.CCE-Retail.en.EU before I started to mess with it.
I tried flash it with 9.8.2Q-8-XT925_VQU-22_USERSIGNED_S7_UCAVANQU02NA02F.0R_LSAVNQJBRTFR_P007_A004_CFC.xml. When it begin starting in AP Flash mode I have removed every line that cause stopping the process (technically everything except "partition", "tz", "boot" and "system" is loaded from 4.1.2) so now its very messy. Right now I don't know what I was hoping for. What's done is done, so now I can only hope that it can be fixed.
If its even fixable, there is no way to fix it without the stock kk fxz, unless you can get it unlocked using Moto's site.
Sent from my G3 Rockin Cyanogen
Thank you for your reply.
I'll try unlocking by web when I get home. I'm only hoping that it can be done without working properly touch screen, or buy connect keyboard via OTG. Otherwise I'm doomed...
Why the F would reflashing after changing the screen and/or digitizer magically bring back the touchscreen functionality to life ?
No touchscreen only means the digitizer was not installed properly, that's all. Open the phone again and check all flex cables and connection, they are really tricky to put back in connectors properly. (pro tip, use some very small pliers to manipulate flex cables and put them back in their connectors)
Unlocking does not require any touchscreen functionality though, it's just a matter of keyboard input from your computer. Just unlock, downgrade properly to say 4.1.2, and when you're done see if the touchscreen work. And when you find out it doesn't, tear the phone apart again and double-check all flex cables connectors on the motherboard
It works!! Thank you very much!!
At first I have problems to find the fastboot.exe in the downloaded SDK directory (for those who also have problems with finding that file it is in 'sdk\platform-tools' folder). The process of unlocking is very easy so I have no problem with that . After unlocking phone flash correctly.
CoinCoin88 said:
Why the F would reflashing after changing the screen and/or digitizer magically bring back the touchscreen functionality to life ?
No touchscreen only means the digitizer was not installed properly, that's all. Open the phone again and check all flex cables and connection, they are really tricky to put back in connectors properly. (pro tip, use some very small pliers to manipulate flex cables and put them back in their connectors)
Unlocking does not require any touchscreen functionality though, it's just a matter of keyboard input from your computer. Just unlock, downgrade properly to say 4.1.2, and when you're done see if the touchscreen work. And when you find out it doesn't, tear the phone apart again and double-check all flex cables connectors on the motherboard
Click to expand...
Click to collapse
Apparently when you have KitKat update it's necessary to flash phone again after replacing the screen and/or digitizer. After flashing digitizer is working properly. I didn't need to open the phone and correct any flex cables (there is only one common to the screen and digitizer so if that was wrongly connected probably I won't be seeing anything). To be honest I don't think that will work without opening the phone. I instinctively unlocked the phone and started to choose the language. Then I realized that I can do it. I'm really glad that the phone is working correctly.
Once again thank you very much for your help.
M_Kwiatkowski said:
It works!! Thank you very much!!
At first I have problems to find the fastboot.exe in the downloaded SDK directory (for those who also have problems with finding that file it is in 'sdk\platform-tools' folder). The process of unlocking is very easy so I have no problem with that . After unlocking phone flash correctly.
Apparently when you have KitKat update it's necessary to flash phone again after replacing the screen and/or digitizer. After flashing digitizer is working properly. I didn't need to open the phone and correct any flex cables (there is only one common to the screen and digitizer so if that was wrongly connected probably I won't be seeing anything). To be honest I don't think that will work without opening the phone. I instinctively unlocked the phone and started to choose the language. Then I realized that I can do it. I'm really glad that the phone is working correctly.
Once again thank you very much for your help.
Click to expand...
Click to collapse
Well, I'll be damned, it's the first time I hear of such behaviour, and i've ripped apart a long list of devices before my razr... Sometimes to replace the screen, sometimes to replace the battery, sometimes just for fun... and I've never seen that before.
(Although IIRC there are two flex cables going from the front assembly to the motherboard in the xt925 and not just one, but I don't remember which one is for what)
edit: OK just found out lcd and digitizer are glued together in most recent phones, including xt925, so there's probably only one flex cable for the whole assembly. They other one was probably for the led I guess...)
CoinCoin88 said:
Well, I'll be damned, it's the first time I hear of such behaviour, and i've ripped apart a long list of devices before my razr... Sometimes to replace the screen, sometimes to replace the battery, sometimes just for fun... and I've never seen that before.
(Although IIRC there are two flex cables going from the front assembly to the motherboard in the xt925 and not just one, but I don't remember which one is for what)
edit: OK just found out lcd and digitizer are glued together in most recent phones, including xt925, so there's probably only one flex cable for the whole assembly. They other one was probably for the led I guess...)
Click to expand...
Click to collapse
The second one is for front camera, speaker and light sensor. I don't count that one because is actually separate part from the screen witch is screwed to the front frame of the phone. To be clear I had problems with that cable and I had to put it few times before camera and sensor start work correctly. That is why I paid special attention to the good fitting of these cables to the motherboard. That was before I smashed software by trying downgrade locked phone so I was pretty sure that it was fitted correctly.
Now my Motorola still works fine. After replacing the screen it actually lived longer in one piece then when I bought it. I scratched the screen next day from purchase... then it fell of my hands few times(usually with the help of other people)... That is why I decided to change glass and front frame... and then during the peel-off old glass from screen I broke the screen... It all happened in period shorter than two months... I'm guessing this particular XT925 is very unlucky... or... it's just unlucky to have me as the owner...
I'm very careful with carrying it with me now, so I don't have to replace the screen again... it cost alto... :|
Well, at least now I know how to bring it safely back to life. And I must admit that my friends are quite impressed that I managed get it work again.

Bad motherboard or ?

I bought my brother a second-hand M8. It had a cracked screen but it was really cheap. I put the new screen in and a new SIM card reader. Everything worked fine for months and out of the blue the screen stopped responding to touch. Everything else worked fine as far as I could tell. Even in TWRP touch was gone so I figured maybe it was a cheap screen or something like that. I took it apart and the backlight was falling apart. Ordered a new screen that had the frame with it to save time on reassembly and because the old one was a little tweaked. Same problem, ran the RUU from Windows, ran different RUU's from several threads via Fastboot. Ran the latest firmware package on Santods thread and still nothing. It has to be the motherboard at this point right? The display and digitizer cables go right into the motherboard and the only cable that looks replaceable goes up int the daughter board with the cameras and top speaker assembly. Am I missing something or should I just scrap this mess?
lightweaponx said:
I bought my brother a second-hand M8. It had a cracked screen but it was really cheap. I put the new screen in and a new SIM card reader. Everything worked fine for months and out of the blue the screen stopped responding to touch. Everything else worked fine as far as I could tell. Even in TWRP touch was gone so I figured maybe it was a cheap screen or something like that. I took it apart and the backlight was falling apart. Ordered a new screen that had the frame with it to save time on reassembly and because the old one was a little tweaked. Same problem, ran the RUU from Windows, ran different RUU's from several threads via Fastboot. Ran the latest firmware package on Santods thread and still nothing. It has to be the motherboard at this point right? The display and digitizer cables go right into the motherboard and the only cable that looks replaceable goes up int the daughter board with the cameras and top speaker assembly. Am I missing something or should I just scrap this mess?
Click to expand...
Click to collapse
When I swapped out the battery in mine the screen was unresponsive and it was becaus a ribbon cable was misaligned in the connector. I cannot rememer Which one it was but I hope this helps.
bug6810 said:
When I swapped out the battery in mine the screen was unresponsive and it was becaus a ribbon cable was misaligned in the connector. I cannot rememer Which one it was but I hope this helps.
Click to expand...
Click to collapse
I checked all of the ribbon cables multiple times and sadly that had no effect. Thank you for trying though!
lightweaponx said:
I checked all of the ribbon cables multiple times and sadly that had no effect. Thank you for trying though!
Click to expand...
Click to collapse
No problem and good luck!

Categories

Resources