Hi all,
Today I've replaced the screen of my Poco F1. Everything was goig fine until I started puting everything back together. When I had the new screen connected, I tested it by switching on the phone and entered the testcode *#*#64663#*#*. For some reason the code didn't open the function test menu (I'm running Pixel Experience, could this have something to do with it?). I didn't think much of it and since the screen seemed to be working properly, I switched off the phone and went ahead and started putting everything back together.
Before shoving the back cover back on, I wanted to test everything so I switched on the phone. After the initial "Pocophone - Unlocked" message, the phone shuts off. I am able to boot to TWRP and access internal memory and the SD Card. From that point I tried:
Taking it apart again to the point where I switched on the phone and it was working
Plugging the old screen in
Recovering from a month old image I had on the SD Card (now it goes straight into fastboot when i try to boot to system)
Wipe system, data, dalvik and cache and flashing clean Pixel OS
Sadly, none of this solved thie issue. At this point I've ran out of ideas so I'm hoping someone here can help me out.
I'm open to all sugestions and please let me know if I can test anything or if you require further information.
Thanks in advance!
How about trying to revert back to stock rom using fastboot mode
Turns out, it wasn't a software issue. I damaged the dock connector on the motherboard (where the main board flex cable connects to the MB). I removed the pins that were damaged (2,3,4,5 counting from the top right to the left) and somehow the phone now boots and seems to be working fine. It only doesn't indicate that it's charging, even though it is. Is there someone who can advise me on whether I can continue using the phone or if it's doomed to fail and worst case, explode (overcharging?) I'd also like to know if there's a better place to ask this question.
PietDeBiet said:
Turns out, it wasn't a software issue. I damaged the dock connector on the motherboard (where the main board flex cable connects to the MB). I removed the pins that were damaged (2,3,4,5 counting from the top right to the left) and somehow the phone now boots and seems to be working fine. It only doesn't indicate that it's charging, even though it is. Is there someone who can advise me on whether I can continue using the phone or if it's doomed to fail and worst case, explode (overcharging?) I'd also like to know if there's a better place to ask this question.
Click to expand...
Click to collapse
Your local Xiaomi Support Centre. I mean you have snapped some pins of a connector. The connector needs replacing.
Sent from my Galaxy Tab S5e using XDA Labs
Hello,
me too , after chaning the screen I can't get past MIUI logo.
About 15 minutes after a messed the the flex tape and no is working,
i'm going to change my earpiece also let's hope that nothing goes wrong.
The weird thing is that changed my screen cause the upper right corner is not working(next to notch) and my screen has some faint lines and also sometimes flickers, I changed the screen and the problem remains...
Related
Well I did it... Broke the screen a couple of weekends ago. Ordered and received a new one. (No problem and not too bad price-wise) Then I ordered the correct screwdriver. That came in yesterday and I followed a couple of tutorials online to take the thing apart. Not too bad despite the teeny-tiny parts. I got it back together and lo-it worked! Actually it took a couple of tries and I reflashed it but then it booted right up. All the apps seemed responsive and life was good once again...
Until I tried to make a call. Then the screen went dark and it appeared that the phone froze up. Called myself from the house phone and discovered that the Aria was dialing, connecting, and sending voice but that I couldn't hear anything on the Aria.
Disassembled, re-set the earpiece, reassembled, called myself again, and I could hear. The screen came on and stayed on, but the touchscreen would not function.
Disassembled, checked all the connections, and reassembled again. The phone appears to work correctly in all aspects until I try to make or receive calls. At that point the screen shuts down and the only way to disconnect a call (or get the screen back) is to pull the battery and reboot.
I tried reflashing the ROM and that didn't work. I'm afraid the transceiver is shorting the screen out somehow but have reached the limits of my expertise.
Any suggestions?
Thanks,
Jerry
I have never had to replace my digitizer so only speaking from what i have read but it sounds like the very small rubber piece that covers the proximity sensor. I have read that if missing or not placed correctly people have had the same problem as you. Just my thoughts
I've replaced my digitizer and I have had the exact same problem. E.Cardo is correct, it is the small rubber piece on the proximity sensor not positioned correctly or not present at all.
Thanks to both of you. The proximity sensor is supposed to be right behind the ATT logo, correct?
I can't wait to get home and try this. I really don't like the backup Cliq Xt... I'll post once I've messed with it.
gdgeorge said:
The proximity sensor is supposed to be right behind the ATT logo, correct?
Click to expand...
Click to collapse
It's hard to see them exactly so I took a picture to show exactly where they are:
http://imgur.com/a/36h8t#ayQhv
It's actually just above the & in the at&t logo, although if you have a replacement digitizer, it might not have the at&t logo on it. If you have trouble seeing it, try looking at it in the sunlight.
To add to what drumist said there as small black rubber piece that goes around the proximity sensor that prevents light seepage and allot of people discard it by mistake when disassembling the phone.
Sent From Deep Within The Rabbit-Hole
Why did you have to reflash? The new screen didn't worked?.
My aria's screen is broken too. I boutgh a new one but It doesn't work. Do you resolve this reflashing? (that's mean applying the new rom version from ATT)
Thanks for your response.
javierarenas said:
Why did you have to reflash? The new screen didn't worked?.
My aria's screen is broken too. I boutgh a new one but It doesn't work. Do you resolve this reflashing? (that's mean applying the new rom version from ATT)
Thanks for your response.
Click to expand...
Click to collapse
The screen or digitizer are hardware they should have nothing to do with the rom. The op only tried flashing the phone to illuminate it is a possible source of the problem. It sounds like you did not install the new screen or digitizer correctly you may need to disassemble and make sure everything is connected correctly and securely. Flashing your phone will most likely not correct your problem.
Sent From Deep Within The Rabbit-Hole
Maybe, just maybe, there are new drivers for the touchscreen included in the rom. I am using cyanogen 7.0.3 without problems, and it works nice with the old screen.
Or the new screen is defective.
I am pretty sure I installed correctly the new screen. Of course the old one is working fine right now.
I requested a new screen so I will wait...
Thanks again.
Hi guys,
I bought a second hand mini pro, and flashed (rooted, unlocked bootloader)it with the help of one of the several guides. with Simplexity and MiniCM7
It seemed to work fine at first, but now something odd happens.
I can only turn the device on (working) when I keep the keyboard slided out. When I start up with it slided in, The screen is turned on but no image appears: It stays black.
When it is turned on (slided out) I can use the phone normally. But when I slide it back in, the screen is frozen and won't react to touches.
Putting the phone in and out of standby (slided out) will have two possible outcomes: Either its usable as normal. Or it simply won't come out of standby at all. The phone seems to react (sounds) to pressing the buttons on the keyboard though.
I used Seus and manual methods to reflash to stock, try other kernels, but the problems remain.
I think it's the hardware that's failing but maybe this can be caused by the flashing as well?
Are there any methods to rule out one or the other?
Cherek said:
Hi guys,
I bought a second hand mini pro, and flashed (rooted, unlocked bootloader)it with the help of one of the several guides. with Simplexity and MiniCM7
It seemed to work fine at first, but now something odd happens.
I can only turn the device on (working) when I keep the keyboard slided out. When I start up with it slided in, The screen is turned on but no image appears: It stays black.
When it is turned on (slided out) I can use the phone normally. But when I slide it back in, the screen is frozen and won't react to touches.
Putting the phone in and out of standby (slided out) will have two possible outcomes: Either its usable as normal. Or it simply won't come out of standby at all. The phone seems to react (sounds) to pressing the buttons on the keyboard though.
I used Seus and manual methods to reflash to stock, try other kernels, but the problems remain.
I think it's the hardware that's failing but maybe this can be caused by the flashing as well?
Are there any methods to rule out one or the other?
Click to expand...
Click to collapse
I'm responding to the thread's title : It's a hardware failure.Brick means you can't even power it on/flash mode.If I helped click the "Thanks" button.Also,try using nAa-11 my and x10man's ROM called XMP Rom and tell us if you still have this problem.I understand that you posted this here (If you post it in questions section almost no one will respond )so I won't tell about that.
(Oh, my bad. Mods feel free to move my thread)
I was afraid of that. I'll try your ROM as well, but I'm afraid its the hardware too.
Thankfully I only paid 30 euros for it
I think the flex cable is gone bad, i have the same problem here. My mobile doesnt respond to any touches. First it happened only when i would slide the keyboard. But now its dead as a whole
speedsys said:
I think the flex cable is gone bad, i have the same problem here. My mobile doesnt respond to any touches. First it happened only when i would slide the keyboard. But now its dead as a whole
Click to expand...
Click to collapse
The XMP rom didn't fix it, so I guess you're right. Would a flex cable (those are the flat orange ones right?) be expensive?
Cherek said:
The XMP rom didn't fix it, so I guess you're right. Would a flex cable (those are the flat orange ones right?) be expensive?
Click to expand...
Click to collapse
I hope you fix it
This is the cable we are having a problem with, i have given my mobile for replacing this stuff as i couldnt get this locally. This board houses the LCD and the digitizer and the buttons connect to this. The black cable goes to the motherboard. Its pretty simple to take apart the phone, but take care while doing so. Another thing its that, when you are opening the display panel, its better to use a guitar pick instead of a screwdriver and open it at the latches, that would avoid damage to the outer plastics.
http://www.ebay.co.uk/itm/BRAND-NEW...K_Replacement_Parts_Tools&hash=item3f0ddd12f3
I have a Galaxy S3 that I have been running CM 10.2 on for quite some time. Today I dropped the phone and cracked the screen. The phone still worked perfectly in every way despite the cracked screen. I used it for a few hours after without any issues. I took it to someone today to replace the screen assembly. When I got the phone back it turns on and the screen looks fine but it hangs on the samsung screen for 3-5 minutes before booting in to anything (booting the rom, recovery mode, download mode etc. all take 3-5 minutes to start) when the phone finally boots the touch screen does not work at all. All buttons work fine, including the bottom buttons (back and settings) for touch but no where else does the screen respond to touch.
So far I've tried:
- wiping cache
- factory reset
- re-installed CM 10.2 rom
- Took the back off the phone and checked all the connections, unclipped and clipped back in to be sure they were connected ok.
- Completely removed battery and all sim/sd cards for an hour
At this point I'm not sure if I'm dealing with a hardware issue (maybe they guy screwed something up when replacing the screen) or the digitizer/screen he used is faulty? I know this doesn't neccessarily mean anything but when I got it back the new screen still had the protective film etc. on it so I'm almost positive the screen assembly the guy used was at least new.
And I don't really understand where the 3-5 minute boot issue could come from? I wouldn't think it would be related to the screen/digitizer but I suppose anything is possible. What could explain this?
Is there any way this could be a software issue or any other troubleshooting I can attempt?
jfall said:
I have a Galaxy S3 that I have been running CM 10.2 on for quite some time. Today I dropped the phone and cracked the screen. The phone still worked perfectly in every way despite the cracked screen. I used it for a few hours after without any issues. I took it to someone today to replace the screen assembly. When I got the phone back it turns on and the screen looks fine but it hangs on the samsung screen for 3-5 minutes before booting in to anything (booting the rom, recovery mode, download mode etc. all take 3-5 minutes to start) when the phone finally boots the touch screen does not work at all. All buttons work fine, including the bottom buttons (back and settings) for touch but no where else does the screen respond to touch.
So far I've tried:
- wiping cache
- factory reset
- re-installed CM 10.2 rom
- Took the back off the phone and checked all the connections, unclipped and clipped back in to be sure they were connected ok.
- Completely removed battery and all sim/sd cards for an hour
At this point I'm not sure if I'm dealing with a hardware issue (maybe they guy screwed something up when replacing the screen) or the digitizer/screen he used is faulty? I know this doesn't neccessarily mean anything but when I got it back the new screen still had the protective film etc. on it so I'm almost positive the screen assembly the guy used was at least new.
And I don't really understand where the 3-5 minute boot issue could come from? I wouldn't think it would be related to the screen/digitizer but I suppose anything is possible. What could explain this?
Is there any way this could be a software issue or any other troubleshooting I can attempt?
Click to expand...
Click to collapse
Go and talk to the person who replaced your screen.. maybe has used faulty screen and also may be he has changed with some of the faulty parts..
suyash1629 said:
Go and talk to the person who replaced your screen.. maybe has used faulty screen and also may be he has changed with some of the faulty parts..
Click to expand...
Click to collapse
Very strange, but it looks like it was indeed a software issue after all. For some reason changing the screen out while having CM 10.2 installed did not play well together. I did a full wipe and went back to stock rom and touch is working now. I may try a new install of CM again to see what happens. Odd
jfall said:
Very strange, but it looks like it was indeed a software issue after all. For some reason changing the screen out while having CM 10.2 installed did not play well together. I did a full wipe and went back to stock rom and touch is working now. I may try a new install of CM again to see what happens. Odd
Click to expand...
Click to collapse
Strange issue.. never had it ever, m flashing CM from more than a year.. Try to do a new flash downloading new files..
One morning I woke up and the bottom half of my Samsung galaxy avant (SM-G386T) had a grid of white lines going across it. First time I restarted my phone it went away.
But they keep coming back and now it's more permanent, Sometimes it goes away briefly but they come back. I tried factory resetting. That worked the first time for a few hours but then it came back. and I tried it again and 2nd time there white lines where there during the factory reset.
The lines even show when I turn the phone off and charge the phone. So I believe this means it is w hardware issue
I tried taking the back planel of the phone off. I disconnected and reconnected the lcd connector latch on the left side. But the problem still persists. I haven't pulled up the screen with a suction cup. So Idk if there is a cable that could be loose on the front end or not. But Idk want to go buy suctions cup if I dont need to you.
Should note that I do have a good sturdy rubber case on my phone. but it has hit the floor a few good times.
One other thing that seems to aggravate or sometimes even make the lines go away is putting my phone to sleep and waking it up repeatedly or adjusting my brightness to max.
What do you guys think? is this fixable or do I need to replace the lcd screen.
man its simple
just press the wires of display which are providing it power & ur problem will be gone.
Its due to lack of sufficient current to display!!
Rustamveer said:
man its simple
just press the wires of display which are providing it power & ur problem will be gone.
Its due to lack of sufficient current to display!!
Click to expand...
Click to collapse
What wires are you speaking of exactly. cause like I said I have taken the back off and disconnected and reconnected the LCD flex cable but nothing changed. Are there wires behind the LCD I need to get to? which means I need to removed the screen with a suction cup?
So I bought a battery for my Mido and followed videos on youtube on replacing it. It all seemed to go well until I started to use my phone. The middle part of my screen doesn't register touches. I was able to install a touch screen test app and you can see that nothing is registering in the middle. Any Ideas? I've attached the screen shot.
prisoner1969 said:
So I bought a battery for my Mido and followed videos on youtube on replacing it. It all seemed to go well until I started to use my phone. The middle part of my screen doesn't register touches. I was able to install a touch screen test app and you can see that nothing is registering in the middle. Any Ideas? I've attached the screen shot.
Click to expand...
Click to collapse
Maybe it's software problem.If you have twrp installed check if the problem appear there too.If not then maybe it's indeed a software glitch.Then maybe you can try a factory reset or clean installation of the rom.
If that doesn't work maybe you can try reconnect the cables you had to disconnect during the battery change process and putting back the previous battery.Not an expert just some logical thoughts.
T3sla said:
Maybe it's software problem.If you have twrp installed check if the problem appear there too.If not then maybe it's indeed a software glitch.Then maybe you can try a factory reset or clean installation of the rom.
If that doesn't work maybe you can try reconnect the cables you had to disconnect during the battery change process and putting back the previous battery.Not an expert just some logical thoughts.
Click to expand...
Click to collapse
I'll test twrp in the morning. Doubt it'll be that. The only connectors I detached were the finger print sensor and battery. I hate prying my phone open. Was such a pain the first time. I'll have to open it up to see if maybe I knocked some other connection loose at all.
I am facing this exact same problem. Pretty much a vertical strip of screen on the right hand side of the screen is unresponsive for me. Screenshot: https://i.imgur.com/8Uqn2lp_d.jpg
I took the phone to the service center, while I had warranty. They pretty much said to my face that this kind of problem can pop up when you've dropped the screen too much and that I need to get the screen replaced to fix it.