Database Develop

urgent please help -screen issue

Hello,
I've had my tilt for less than a year now. Today, my screen, when I turned it on, shook and while it was shacking, it was showing multiple lines on the screen. At the end, the screen was complete white. I can still make/receive calls, however, I wouldn't know what's going on since the screen was white. It seems to me it was a loose connection???? It got me extremely worried. I took off the battery, made a hard-reset, tried to physically move the screen, non worked. all of a sudden, the screen was fine. Later today, it happened again.
Can anyone please explain this problem to me and how to fix it. I would really appreciate that...
Thank you

Not sure what "shacked" means.
But given you are under 1 year, you probably have a warranty. Would be best to try and get a warranty exchange.
To have you dig around inside checking connection and voiding your warranty, would not be wise with an active warranty.

JimmyMcGee said:
Not sure what "shacked" means.
But given you are under 1 year, you probably have a warranty. Would be best to try and get a warranty exchange.
To have you dig around inside checking connection and voiding your warranty, would not be wise with an active warranty.
Click to expand...
Click to collapse
I'm sorry, I meant to say "shake". Anyways, My phone is unlocked and I bought it from ebay... currently using it in Canada

iamcanadian said:
I'm sorry, I meant to say "shake". Anyways, My phone is unlocked and I bought it from ebay... currently using it in Canada
Click to expand...
Click to collapse
Ahh Booo.
Ok, Find mikechannon's disassembly guides and wiggle all your connections. Sounds like a loose connection to me.

Hello,
Thanks for the reply, I dismantaled my device and made sure all the connections are fine. The problem still appears....

Ok Next Thing it, The LCD panel is "dieing" you will probably need to replace it.

JimmyMcGee said:
Ok Next Thing it, The LCD panel is "dieing" you will probably need to replace it.
Click to expand...
Click to collapse
oh damn
I noticed that when it happens, if I touched the OK and the end call button together, it would sometimes solve the issue. I would have to do it several times though. Is that any hint? are there screen related connections underneath those buttons?
Thank you for your continuing support, much appreciated!

OK, I've noticed that once I click on the call button, the white screen shows up. As I said, I dismantled my device and checked all the connections. However, I didn't go further than the 15th page, i didn't go further because I though that it wasn't necessary.. That's the websites of the tutorial I followed:
http://www.mikechannon.net/PDF Manuals/Replacing the LCD on a Kaiser.pdf
So the two connections I made sure they are properly in was the small and big one only like in the picture below....
Connection #1:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Connection #2:
Another view of Connection #2:
I appreciate any help possible.... Thank you all...
Thank you again for the continuing support

bump...
Please help as this issue is really bothering me. Anyhelp is much appreciated!

Those connections you have pointed out in those pictures are the keyboard ribbon connections....I think you might have to dismantle a bit further to get to the screen.

mic_888 said:
Those connections you have pointed out in those pictures are the keyboard ribbon connections....I think you might have to dismantle a bit further to get to the screen.
Click to expand...
Click to collapse
OK, I went further and was able to see the screen ribbon. I made sure the connections are in tight. However, after putting everything back, the problem still persist. Now, I'll be more than happy to buy a new screen IF it solves the problem... Please correct me if i'm wrong, doesn't seem more like a connection problem; maybe the chip that holds the ribbon cable is loose? In this case, it would need soldering???
Moreover, I noticed that the screen ribbon is underneath the talk button. Like I said before, touching the talk button solves the white screen*. Isn't that more proof that its not a screen issue?
I am very grateful for any advice...
Thank you
* Before completely dismantling the phone, it used to be touching the talk button brings the white screen problem, now its the opposite

Screen dies when closed - help requested

I have an HTC Dream/G1 that's having a rather odd issue. When the screen is flipped open, it appears to behave exactly as it should. When the screen is closed however, the display becomes a mess of vertical lines (or sometimes just fades to black) and does not respond.
One need only "sleep" the phone and "wake" it after flipping the screen up to bring it back to normal operation. This only lasts until the phone is again closed. I've included a couple of screen captures to help illustrate the issue. I've searched and searched and found absolutely nothing about this problem anywhere.
I'm currently running Firmware 1.6, CyanogenMod-4.2.7.1 with Cyanogen recovery. Everything was working fine and the phone suffered no trauma prior to this issue presenting itself. It literally happened while the phone was sitting idle on a coffee table. I've tried reflashing the phone (including reverting to Dreaimg.nbh and starting "from scratch") to no avail.
It does not appear to be an issue with the ribbon cable (no amount of flexing the cable or moving the screen has any effect). The display behaves properly throughout its movement up until the exact point at which it switches to "closed" functionality (approximately 80% closed). It appears to be something related to the hardware after it switches to "closed mode". My shot-in-the-dark guess is some form of chip-failure related to the phone's orientation detection as the vertical lines do not change regardless of orientation or touch-input. Again, that is just a guess.
If no one here has any recommendations, I will likely perform exploratory surgery and barring any obvious hardware failures, will likely be forced to replace the phone. If I do manage to resolve the issue (with or without outside help) I will surely assemble a how-to so others may resolve the issue in the future.
Thank you everyone for your help and suggestions, and for existing in the first place. You are the reason technology is fun.
EDIT - As pjcforpres kindly pointed out, I neglected to include the fact that the display failure is present regardless of boot state. It behaves this way upon initial "G1 screen" boot and even in the recovery console. This is appears to be further support for the idea that it is indeed a hardware failure.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Does it do this while in recovery/boot loader as well? Is there anyway when closed to get it to work correctly?(I think your answer will be 'no' but just double checking)...

Oh wow, I can't believe I forgot to include that important bit of information. Yes, the phone behaves this way regardless of boot-state. Even with the initial "G1" screen displayed or in recovery mode, closing the screen brings about the display failure. No amount or configuration of screen or button operation seems to bring about the appropriate closed screen behavior. I will edit my original post with this information if I can. Thanks for looking and responding!

I didn't read your post
But my dads g1 did this.
It's a hardware ribbon, not software.
Go get a return or exchange for a new g1 because yours is defective.

That makes me think hardware then... not sure what though? Like you were saying, if there is an open/close switch of sorts that would be my bet. It could be the flex cable as well, and when it close that much it gets pinched, and happens to coincide with the orientation flip. But then it wouldn't take sleep and unsleep to go back right when opened, I would think... so we are back to it probably being the orientation sensor switch being funky like a monkey.

Well, I just tore it completely apart and put it back together to no avail. I made the assumption that the LCD flex cable was not the cause because of the behavior (only happening at a precise position, having to sleep then wake the phone to recover, etc...). It appears, however, that this assumption was incorrect. On Icebergxx's suggestion I decided to give it another look. I wedged a tool in against the cable and with various forceful flexing I can recreate the issue even with the screen fully extended. Luckily it appears the LCD flex cable is available on ebay for $24. Thank you so much for your responses. I'll dig around for a flex cable replacement guide, if a sufficient one does not yet exist, I will take the opportunity to share. Thanks again!

You're so handy its admirable haha good luck buddy glad to have helped.

Happy to hear it is just the flex cable! I was worried with the way it was acting it was something worse, just the whole not coming back to life when opened without sleeping then un-sleeping.

[Q] wonky flash + non working ambient sensor after power button service

Hello,
Recently I sent my nexus one for a button replacement. I got the phone back with some strange symptoms:
- Flash light blink at random event (first boot, after I hang up a call, etc..) but cannot be controlled by software (torch and camera app in CM7, MIUI or the stock firmware). The camera however works fine.
- The ambient sensor is dead. It either reports a very high value (2600 or 5800) or a very low one (10) (these values were taken from the CM7 auto brightness adjustment settings)
- Mic from the headphone when I plug in does not work anymore (the mic works before and tested to be in working condition)
From some online research, it seems like a loose connector can cause the wonky flash light problem (report by fblodroid, he fixed it by plug the connector back)
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=46ef1e3a49030ed9&hl=en
My question is: can the other two problems be related to this connectors as well? Or did I get a defective board?
I plan to fix it once the tools arrives (dealextreme takes forever!). Another option is to bring it back to the service center to get fixed (this will take a week, and who knows what kind of fees on top of that). I'd prefer to fix it if I can.
Anyone has some knowledge about this kind of issue? Any idea what do those connectors do?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

popophobia said:
Hello,
Recently I sent my nexus one for a button replacement. I got the phone back with some strange symptoms:
[...]
Anyone has some knowledge about this kind of issue? Any idea what do those connectors do?
Click to expand...
Click to collapse
Dude, if your N1 is on warranty I wouldn't even bother to think what is causing this problems Send it back. You'd have o wait some time but you will still have your warranty for the future, and if you disassemble it you will probably loose it (not mentioning that your problem could be unfixable!).
They screwed up and they should fix it for free. I hate when electronics come back in worse condition after repair than before...

Well, it's out of warranty. But I think I have 3 months part warranty from the last repair.
They didn't put any seal on the screws this time. Maybe you're right, it's smarter to just send it back to get everything resolved.
I'm just curious whether all the problem described above can be attributed to the board they replaced (or one or two loose connectors).

popophobia said:
Well, it's out of warranty. But I think I have 3 months part warranty from the last repair.
They didn't put any seal on the screws this time. Maybe you're right, it's smarter to just send it back to get everything resolved.
I'm just curious whether all the problem described above can be attributed to the board they replaced (or one or two loose connectors).
Click to expand...
Click to collapse
I didn't know about the warranty, BUT: They spoiled your phone while fixing button so as a consumer you have right to demand that they fix it free of charge! Maybe it's something like silicon defect or "cold solder" (don't now if it's correct name. Google-Translated it) on the main board. They should have tried it before sending it to you.
Wish your N1 will get better soon

I need the data from a dead/bricked Huawei P9 for work (Black Screen) Help pls!

Hello,
I was asked by my boss to retrieve the data from a not working Huawei P9 if possible.
Following scenario:
A coworker attached his phone via USB to his laptop. The phone restarted two times but he didnt think its a problem.
Next day he thinks its a good idea to restart his phone because it seemed a bit laggy but after turning it of (restarting) the phone doesnt
turn on anymore. No lights, no nothing. If you plug it into the pc you can still hear the "new device attached" sound and can also hear this sound
when pressing the power button and volume down button for about 10 seconds. There is also no charging light when connecting it to the pc.
I repaired some phones before but most of the times it was just hardware stuff which wasnt a problem. I talked to a repair shop that told me
the battery is probably ok and the memory/data has to be read out of the phone and that would cost at least 200€.
Is there anything else I can do?
The phone is a stock Huawei P9. Nothing changed or flashed ever. The data would be crucial for me and my work colleagues.
Thank you!
Here is a screenshot of what my device manager on windows looks like. I installed a driver for the phone I downloaded online with driver signature turned off.. Thats everything I got so far.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Keratonko said:
Hello,
I was asked by my boss to retrieve the data from a not working Huawei P9 if possible.
Following scenario:
A coworker attached his phone via USB to his laptop. The phone restarted two times but he didnt think its a problem.
Next day he thinks its a good idea to restart his phone because it seemed a bit laggy but after turning it of (restarting) the phone doesnt
turn on anymore. No lights, no nothing. If you plug it into the pc you can still hear the "new device attached" sound and can also hear this sound
when pressing the power button and volume down button for about 10 seconds. There is also no charging light when connecting it to the pc.
I repaired some phones before but most of the times it was just hardware stuff which wasnt a problem. I talked to a repair shop that told me
the battery is probably ok and the memory/data has to be read out of the phone and that would cost at least 200€.
Is there anything else I can do?
The phone is a stock Huawei P9. Nothing changed or flashed ever. The data would be crucial for me and my work colleagues.
Thank you!
Here is a screenshot of what my device manager on windows looks like. I installed a driver for the phone I downloaded online with driver signature turned off.. Thats everything I got so far.
Click to expand...
Click to collapse
You could check with DC Phoenix, Ministry of Solutions and Chimera - describe them a problem and ask if they can help to retrieve data.
It's probably a hardware issue, and you will not be asking to unbrick (if really a hardware problem, even if you succeed to get it booting again, it could happen again) but just to retrieve data.
With DC and Chimera, you will have to work on your own, just to play for their tools (but it will be cheaper then Huawei service shop).
Ministry of solutions might be even cheaper but they will probably want to work with remote access to your PC - maybe asking you first to open back cover and to short-wire for Test points pins.
Might be best bet for you, but you must consider the security concerns for such a remote access work (at the end of the day, if you bring phone to the service shop, you can also only trust them regarding the data they find on the phone)
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
https://ministryofsolutions.com/paid-services/amp
https://chimeratool.com/

zgfg said:
You could check with DC Phoenix, Ministry of Solutions and Chimera - describe them a problem and ask if they can help to retrieve data.
It's probably a hardware issue, and you will not be asking to unbrick (if really a hardware problem, even if you succeed to get it booting again, it could happen again) but just to retrieve data.
With DC and Chimera, you will have to work on your own, just to play for their tools (but it will be cheaper then Huawei service shop).
Ministry of solutions might be even cheaper but they will probably want to work with remote access to your PC - maybe asking you first to open back cover and to short-wire for Test points pins.
Might be best bet for you, but you must consider the security concerns for such a remote access work (at the end of the day, if you bring phone to the service shop, you can also only trust them regarding the data they find on the phone)
Click to expand...
Click to collapse
Thanks for the answer! I will check out the websites you linked and go from there.
Thanks for helping out!

Can't register new face with face unlock

Factory resetting
Upgrading to 12
down grading to 11
factory resetting
using accessibility mode
using "simple" setup mode
outdoors
by windows
by lights
It just wont register a new face no matter what I do. Almost as the module that handles it is completely hosed. Not sure if it matters, but it never does the "blue" squares on the circle when registering, it only ever says "fit face in inner frame".
Anyone have a fix for this?

Did you replace any component on the phone?

#mcl said:
Did you replace any component on the phone?
Click to expand...
Click to collapse
no, all oem

Does front camera work and sensors as well?
What I saw was people which got face unlock broken after changing front sensors, and as it seems, front camera is locked to the motherboard so if you change it you loose Face unlock.
However I also saw people who had a similar problem to you and after uninstall updates from some apps it started working again. I will search those threads and link them here for you

#mcl said:
Does front camera work and sensors as well?
What I saw was people which got face unlock broken after changing front sensors, and as it seems, front camera is locked to the motherboard so if you change it you loose Face unlock.
However I also saw people who had a similar problem to you and after uninstall updates from some apps it started working again. I will search those threads and link them here for you
Click to expand...
Click to collapse
Would be very appreciated.
is there some sensor setting I should mess with?

kallell said:
Would be very appreciated.
is there some sensor setting I should mess with?
Click to expand...
Click to collapse
I am not aware of any settings apart from motion sense settings sorry

Try clearing the system cache.
Hard reboot. Try in safe mode.
I recommended not using any kind of lock.
The user is usually the one that ends up getting locked out. Many times due to a hardware failure... and the lock only makes the situation worse.

kallell said:
... Anyone have a fix for this?
Click to expand...
Click to collapse
@kallell
Sounds like you have a dead sensor or two. You should download and run some sensor testing apps like sensor lab or sensor test . Run those and if you get corroboration across more than one app you have your answer. How is your warranty status? Did you buy the phone directly from Google? If so you may have a pretty good shot at an RMA.

kallell said:
Would be very appreciated.
is there some sensor setting I should mes
Click to expand...
Click to collapse
kallell said:
Would be very appreciated.
is there some sensor setting I should mess with?
Click to expand...
Click to collapse
Hey here are some links:
1.
https://www.reddit.com/r/GooglePixel/comments/eknssj
2. https://forum.xda-developers.com/t/module-fix-broken-face-unlock.4095233/
3. https://forum.xda-developers.com/t/face-unlock-not-recognizing-my-face.4010275/
Hope this helps you. I will be watching this topic, if I found anything new I will let you know

I mean if the phone didn't suffer from any drop and was never water damage, the front sensors are fine almost certainly.
If it is under warranty though I would suggest getting in touch with Google so you don't need to use your time to fix the problem, it's faster and safer.
If not I would suggest you to open the phone. It may be stupid but maybe the conector got disconnected from the motherboard and therefore doesn't work.
This happen with my rear camera. The phone was never damage and never open but somehow the conector manage to disconnect it self from the motherboard.
Here you have a link to Ifixit's guide on how to change the front sensors. I also link a photo to what happen to my rear camera conector.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}