Hey guys,
just replaced my screen by myself and it isn't working. It boots and the screen lights up for a few seconds but thats it. So it seems like I ****ed up somewhere. :/
Now I've got some questions for you guys.
1. What could cause this error? Since it's already not working I don't mind taking it apart some more and trying to fix it.
2. Do you think if I send it to the support from OnePlus they will take a look at it?
3. The whole reason I did this was to get my data back. Is there any way to access the data on the phone without the touchscreen? I encrypted it using CynogenMod. USB-Debugging is enabled.
Thank you so much guys, I'd really appreciate some help. This **** is really tearing me down since it was a lot of work.
I did this on my own phone but Idk about OPO. If you use the power+voldown method to boot into recovery (yes ik nothing on screen) then connect a usb and see what happens
If you power it on, wait 5 mins then call it and if the phone rings you should be able to rule out the display and speakers and storage, obvs if the display is still not on at this point it is probably the display.
you can also adb from recovery and or fastboot so you should be able to see it in there if it is still working (make sure you change the phone for a decent amount of hours before you do any of these) If the display is dead its likely its been on for the last day and dead
Sorry for the late answer, really appreciate your help!
So if I connect the phone to the PC (tried it in recovery and in normal mode) windows detects the phone under "Devices" but sadly if I type in "adb devices" in cmd it doesn't detect the device.
But still, windows is detecting the phone so it seems to still function. I booted into recovery and I could use the touscreen and the lower buttons. I couldn't see anything but it was vibrating whenever I was using the touscreen. So it seems like only the display part is broken.
Can't call the phone since it's fully encrypted so I need to type in a password before booting anything (recovery, normal mode, ...)
I'll try to contact the vendor of the display and see what he has to say.
If anyone got any more tips I'd appreciate them. I'm a pretty big noob so I even appreciate "common sense" tips.
I know this may be a "common sense" thing to say, but double check your connections. Sometimes the connectors aren't made properly and a pin could be covered so you can try connecting and disconnecting several times to see if it clears up.
Since the touch screen was registering and vibrating, then it could be the backlight that's broken. Try holding a flashlight at an angle and see if you can make out anything on screen. If it's the backlight, then you can probably back up your data in case your phone does end up breaking.
reconnected everything multiple times and also tried the flashlight trick. sadly with both no luck
but something good:
adb recognizes my phone in "recovery"
bad news: no commands work, most likely because the phone is encrypted. if I enter a command nothing happens, it looks like its loading forever.
any ideas?
Hey!
I also had the same problem after I replaced OPO's screen about one year ago. The replacement screen was from ebay.
I could see the Cyanogen logo but after a few seconds the screen became black. Booting into recovery mode worked well.
On the video also ROM boots well but the screen stays black.
https://www.youtube.com/watch?v=VcWDCJIkPKQ
Eventually, the screen was defective and I returned it and bought new one.
Related
Hi all... and sorry for my bad English ;-)
I've got an HTC G1. When I try to start it, nothing happens. Only the backlight turns on ... What can I do?
do you have a rooted g1 with recovery and engineering SPL?
No, it isn't rooted...
Is it brand new? I think you should be able to exchange it, if you got it from a store that is; unless you got it from online then you will have to contact the website and see where that goes.
No, it isn't brand new. Someone gave it to me... So i can't exchange it.
Try to boot it thru camera+power holding. Wont help you if success but at least will tell you where the problem.
if he can go to recover mode screen wont remain completely black as far as i know. Because splashscreen appear before recover (or other) mode starts. I might be wrong of course.
If I try to go into the recovery mode thru camera + power button, nothing happens. Only the backlight turns on (black screen with backlight & keyboard backlight...)
Follow first 6 steps in this form...
http://forum.xda-developers.com/showthread.php?t=442480
tihs should boot your G1.... then if you want go on ahead with other rooting steps to root your g1..
I tried the first 6 steps, but it won't work. I think I can't entry bootloader mode. On step #4 (...)You should see a gray/white screen with instructions(...)
nothing happens on my Phone. :S
Isn't it possible, to flash the bootloader/firmware over USB or something like that?
*push* no solution?
are you sure the phone does not boot? Does it rumble when you first turn it on?
I have a similar problemb, but my phone will completely boot and work, but the lcd does not work it stays black. i can move apps around (they rumble when you pick one up), and i can recieve calls.
I was able to get it to occasionally boot with the lcd working by rebooting the phone with call+menu+power. It worked long enough to reflash the rom to rc29, and boot into it. Then it died shortly after.
mine is going to htc.
Yes, it does rumble when I turn it on, but I think it doesn't boot. So I can't "move apps around" or "recieve calls"
And I can't use the warranty, because I'm swiss.
another way to tell if it actually boots is plug it into a pc after giviing it enough time to boot, and listen for the usb connection notification sound your phone should make.
just trying to help you narrow it down. When i am contacted by HTC i will be sure to try and get as much info from then as possible. hopefully ill get something that might help you.
Since you wont have to worry about voiding your warranty, I also suggest snagging the factory service manual and make sure all the flex cables/connectors pertaining to the lcd are properly connected. This, of course, is under the idea that you have the same problem as me.
good luck
When I plug the phone over usb into a PC, the pc find it as "HTC Android Phone USB Device".
Hmm I don't think, that the LCD is broken, because the backlight turns on... If the lcd is broken, the backlight won't turn on, right?
the backlight on mine would also stay on. then again my lcd worked intermittenly at first and proceded to work less and less, but the backlight would remain on. However, I think your problem differs from what I encountered.
The fact that your pc recognizes the phone means the usb controller is working, but thats about it... I am just trying to find out for sure if you phone boots or not. That will help narrow down the problem for sure.
Have you tried calling it from another number?
It also never hurts to take a peek at the factory service manual... if you havent already
thank you. hmm... I think I can't recieve phonecalls.. but I'm not sure. (I tried it, but yeah i don't know. xD it doesn't rumble or something like that...) Is it possible to have "remote" on the phone? So I can use it over the PC?
They have shipped my phone back. Apparently the screen dying was a side effect of the keyboard going bad...The keypad did not give me any problems though. I was told they replaced the keypad FPC (part no: 73H20137-41M, pg#102 in the service manual). They replaced nothing else.
Unforutnately they did not have any more info to give me. In your case, i would suggest opening it up and checking all the flex cable connections to ensure they are properly and fully attached. of course this check is not really for the faint of heart technically speaking, but it shouldnt be too bad with the service manual as a disassembly/assembly guide.
are there any tutorials how to open the g1? =)
http://www.youtube.com/watch?v=27inpgouXII (part I)
http://www.youtube.com/watch?v=HIg_3EgrgGY (part II)
Hi all !!! Sorry for my English but I need your help
I commented what is happening with my phone N5 (which for good and evil is always stock without root or anything, with corresponding OTA updates.)
1- Yesterday afternoon at lunchtime while reading a book in playbooks, I notice that suddenly disappears one line and then appeared intermittently. I close the app and noticed the same thing happening on the screen menu. I shut down the cell and turn on again and I thought it must be an application be kidding. But still does.
2 Also yesterday I happened to change the security on the phone screen. After a while of normal operation, try to turn it on the screen with the button, nothing, the screen goes "black", with light and retrolight turned on but no picture no nothing .
Called the cell to see if it works or is turned off and the phone rings but the screen nothing. Try turning it off and on again by holding the on / off / lock button and the phone restarts, but the screen nothing. In one such attempt to do the above it is seen that managed to turn it off. And I get it on and do a normal boot, except that the picture of my screen is changed to the original. Change the lock screen which was previously using (slip). And it seemed that out or some conflict with the lock. In one of those again pressed the ON / OFF / lock as would normally and it starts all over again.
After I magically back to life, I want to make a full wipe as I think it should be an app that is doing some conflict or something. BUT ....
3I turn off the phone and then press the keys VOLUME UP / DOWN and ON / OFF is normally off, squeezed the first screen with the options but options RECOVERY / BOOTLOADER appears in red I choose RECOVERY give the ok with the key and .... andriod robot appears with the legend below that says something (I do not remember well) without or without controls options appears. So its seems thatI dont have recovery.
After that keep pressing the key ON / OFF and the phone turns off and / or reboot normally. All this I did it again to see if the error reappears and looks that I do not have recovery.
The failure of the screen is increasing. I dont know if they are separate problems or is it all the same problem.
Sorry if I was too long but I need the help of you.
UPDATE Now it seems that the screen died, since I do not achieve to turn it on as before, the light and the retrolight its ok. The phone receives calls and notifications but the screen stills black.
Thanks all.
Matias M 73
the android laying on its back IS the atock recovery.
simms22 said:
the android laying on its back IS the atock recovery.
Click to expand...
Click to collapse
thank you simms22 but I need to fix or understand what happend with the screen first.
:good::good:
Matias M 73 said:
thank you simms22 but I need to fix or understand what happend with the screen first.
:good::good:
Click to expand...
Click to collapse
sometimes things just "derp". itll happen more often if you dont reboot your phone often. also, your phone will be a little bit more responsive if it gets reboot once a day or two.
RMA or fastboot it back to stock, if the screen doesnt turn on afterwards then it looks like a hardware issue, open device and reconnect the display.
republicano said:
RMA or fastboot it back to stock, if the screen doesnt turn on afterwards then it looks like a hardware issue, open device and reconnect the display.
Click to expand...
Click to collapse
Thank you Republicano!!
I think too that its a hardware issue. I already see on you tube problems like mine.
Thanks again!!
Hello All,
Basically what happened is this:
I got phone D6603 with "Vodafone protect" lock on and owner gave me a possible code for phone. I replaced screen and then found that lock requires only numeric pin, not what I was given. So, he then reset pin and deactivated lock, but I still had it on no matter what. So, I tried to flash new firmware into it for same phone and got it done, but now phone screen stays black all the time with only backlight on. Phone seemingly loads something (probably the new phone welcome screen after flash), which I cannot see, but when connected to computer from fastboot or something then all system files are visible.
When I boot phone from off position, it boots to a point where I can use side button to switch on and off the screen but touch does not respond because nowhere it reacts to touch or maybe I do not know where and what to click on screen.
What could be the likely solution? I do not think that phone is bricked, but something is wrong with system as it does not light up the screen properly. I tired flashing 2 times successfully with same result.
Any advice would e appreciated.
Hi, can this thread be deleted because I am getting phone swapped and thread no longer relevant? Thanks.
Heu guys,
So I received a P30 as a gift yesterday, it said it had an update so it downloaded. Then it said it needed to be at 20% to install the update so I just left it until later when I could get to a charger. The thing is, I also didn't have a sim card in it.
I pulled the sim slot with the phone turned on (install pending) , and as soon as I did that I got a new black screen of death, nothing like in any of the videos online.
This one allows me to interact with the screen, however the entire screen stays black except for about 50% of the top (like I can see 50% of the battery icon) notification area. The tiny section of the screen that turns on also looks sorta wonky, like screens often do when they get water damage.
I've been able to turn it off, by guessing where the power buttons were. I *think* I even got it to the hard reset menu, but not being able to see, I can't type on the screen. It does react to the soft reset (power + volume down) but when it turns back on, it won't even show the logos on boot, everything still stays black minus a section of the notification bar.
Is there a way to do a hard reset without being able to interact with the screen at all? Can I do it using my computer somehow?
I know the screen is not broken because I can interact with it. Also on 1 of the 30 soft resets I did, the screen flickered some sort of error message for a quarter of a second, so fast all I could do was see it was text.
I'd just return the phone but it was a friend's old work phone and there is no way to get a replacement.
I recommend you to use Hisuite on a computer, try to connect the phone (I said try because you must select the type of connection on the phone). If the phone connects to Hisuite, use the recovery option to reinstall the default firmware. Good luck!
marselcj said:
I recommend you to use Hisuite on a computer, try to connect the phone (I said try because you must select the type of connection on the phone). If the phone connects to Hisuite, use the recovery option to reinstall the default firmware. Good luck!
Click to expand...
Click to collapse
this might be my only option. I was trying to find something just like that. Couldn't figure out if there was a software for it or not. Thanks will try when I get back to a computer tomorrow!
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
bigblkyj said:
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
Click to expand...
Click to collapse
If what you've described is correct, all of the solutions involve flashing the stock firmware which will of course wipe the device.
Were your photos not stored in a folder on the SD card?
There is a chance you can recover the device using Samsung Kies with the emergency recover option but if you've encountered the "no command" screen it's not looking good.
Unfortunately I did have an SD card installed, but I normally kept my camera pics on the phone's memory, since I have had an SD card fail as well and lost everything on there.
So this took an unexpected turn yesterday pretty much right after posting this... I've been messing with the phone, unplugging the battery each time, and have managed to get into different menus which kept making me think that something still had to be working if I could do that. Well, after leaving the No Command message on the screen it magically booted into the Recovery menu with (finally) the option to wipe the cache partition, which I did and rebooted normally. Believe it or not, it booted normally and into the OS like nothing ever happened?!
I instantly plugged it into my PC and ran Smart Switch which started taking a backup! About 25% though the device restarted again and was really warm to the touch on the RF covers inside. Bummer...
So I figured heat was now the issue for some reason... I waited for it to cool and then reinstalled the SD card and figured, if I could get it to boot long enough, the SD card is a quicker transfer and I'd just use ES File Explorer to try and do a photo dump to the SD card and see how far it would get. It actually made it all the way through and gave me enough time to grab some other stuff before getting hot and restarting again.
I believe the overheating is being caused by my opening of the device though... Currently I have the antennas removed and the speaker so that I'm able to quickly access the battery connector (which BTW seems to be the trick here to this working) But inadvertently, without the larger wireless charging coil in place, it relieved the pressure on the motherboard and broke the thermal paste connection between the chipset and the copper heatsink (I didn't tear it down further to check, but I can hear the 'sticking and peeling' when you press down on it).
I think what I'm going to do is apply pressure with a chip clip or something similar (non conductive) and see if I can grab a backup again before it restarts. After the cache wipe the phone seems to understand that it's plugged in and charging now which is a new thing as well...
Sorry for the long winded posts, but if this at all helps even one person with the same situation as I have, maybe that'll be worth getting lost in here