Hi!
Soon after a touchscreen repair my E6653 stopped displaying anything on the screen. A return to the workshop revealed that probably the graphics chip is broken - the screen lights up, but it's all black and never shows anything.
Now I'm trying to boot up the phone - as far as I can tell it seems to be working, but without seeing anything it's hard to enter the SIM PIN or the lockscreen code correctly - I didn't succeed so far.
But it's getting worse - I'm neither able to enter recovery (TWRP 3.x) nor is the phone going into fastboot mode when pressing VOL DOWN while connecting the USB cable.
To me this looks like the mainboard is broken - any other ideas? How could I find out?
And more important: Any ideas how to save data???
Yeah Motherboard Died, It Happened To Me Too.
Related
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.
Hi all. I've been given a Tesco hudl 2 that has turned into a paper weight and basically tesco have washed their hands from it.
It has a common error 'No boot device. Hit ok' - but there is no response from screen or power/volume buttons to enter 'ok'
I plugged in a usb keyboard via OTG adapter and pressed enter which takes it to Boot Manager - with sub menu - Boot Options Menu
but there are no options to select and pressing enter just flashes the screen.
I have tried the factory hard reset option and doesnt work. Just turns on and turns off.
There is no charge light when plugged in, but does turn on to, again 'No boot device. Hit ok'
There is no adb access
I absolutely hate wasting tech and like to use them for other uses. Anything that can be done here?
Is the motherboard blitzed someway.
Anyway to flash a rom via SDcard or force some sort of bootloader access or recovery?
Can the rom be flashed with hardware directly on the chip (tho I don't have the equipment, just a query).
Its suppose to be a good enough IPS display with 1,920×1,200.
Ok now for the out of box ridiculous thinking. Can the mainboard be replaced with another brand of tablet with perhaps better specs.
Can these LCD panels interface with other systems at all, to perhaps a laptop via some sort of display board for a possible car project?
A lot of questions, but hope someone can shed some light. I love finding things out and fixing things, if possible.
Thanks
bump
I have replaced a dead hudl2 charging port and battery all i am getting is a faint green light but not always. however still not booting any ideas please
Hi,
My customer brought me a phone after a water damage. He claimed that the phone has been working fine for a few days after being dropped into the water untill it has discharged. Now when connected to the charger it just normally shows battery percentage level and is charging fine, but if try to turn it on it just shows Samsung Logo, vibrate twice, again vibrate twice and turns off.
What I have done:
- i've fully dissasembled the phone and clean everything with isopropyl alcohol (99%) (most of the water damage was on the bottom panel with usb charging and LCD connector, mainboard and batterry looked untouched)
- i've put both boards for an hour onto the 100 Celsius board
- after another 24 hours i've reassembled the phone and the problem remained
- I've replaced usb charging board and cabel between it and main board with working ones (still the same)
- I've reflashed stock ROM for SM-A515F Poland (without CSC)
- wiped cache
Nothing worked. Moreover, when I tried to enter Safe Mode the screen went "static"? It just looked like analog TV when you have no signal. Every restart ended up with this "static screen". However when i enter the recovery or download mode it looked sometimes fine. After another Stock ROM flash "static screen" has no longer showed up, but the device still "turns off" after Samsung logo and 2x2 vibrates.
Right now I'm not really sure if it is software or a hardware issue. Had anyone dealt with something like this? Any advice is welcome
I haven't tried factory reset yet, because the customer has many important photos on the device (with no backup :/)
Have a good day!
P.S. Tomorrow i will replace LCD to check if it's faulty. If don't I'll be looking a way to retrieve photos from this bricked phone. It's locked with Google Account and PIN, has not enabled debugging or anything else. Is it possible to somehow restore photos from this phone? Some way to install CWM without unlocking BL (to prevent data wiping)? Then from CWM i should be able to fire up ADB and pull personal data? Has someone any idea if it is possible?
Hi again,
I was so happy that i've fixed this smartphone for my customer that i've forgot i've wrote here
Finally I was able to fix the phone. Even the screen looked fine in the download/recovery modes it turned out that it's faulty. With new screen phone is starting fine and everything works correctly. Here's the link where i show the old screen and new one and how the phone responds:
So, first I thought my brother's A51 was water damaged because it was wet a little bit and charging was being interrupted. I left the phone turned off for the night and wanted to look at it again the next morning. The problem is that the screen or something else stopped working.
The screen works fine in Download mode, Recovery mode, or at splash screen with phone's model name, the problem begins when it's booting to Android. It's still stuck at the splash screen. no boot animation, no lock screen visible, just a model name. It's not bricked, because I can still unlock the phone (didn't have a password) and I can hear the unlock sound or charging sound (it started working again).
I tried factory reset through recovery - didn't help, flashing fresh firmware from Frija - didn't help. The only thing that changed is now the splash screen brightness goes down a bit and I noticed that until I am touching the screen so the phone can't lock itself it doesn't turn off the splash screen, but when I press the lock button it turns off the screen and I can't turn it back on, but the phone still works because I can hear charging sounds and it shows up in Device manager.
I also opened it because I wanted to see if there's any water damage, but I didn't see any water marks or burnt components. I cleaned the charging board with alcohol and let it dry but that didn't help.
I'm worried that there's something wrong with the motherboard or the charging board because it has a screen connector.
I can also see that some people here have similar issues:
Unbrick A51 - Stuck on samsung logo
Hi, My phone is stuck on A51 logo for days now it charges - I can enter download mode easily - I can sometimes enter recovery mode some other times it doesn't let me I tried flashing different stock ROMs of android 10, 11 for the phone with...
forum.xda-developers.com
black screen after splash and unable to factory reset, possibly frp?
Apologies for formatting, typing up on my phone during my break at work. To be more specific, I have a samsung a51 that recently had a black screen of death with no known cause. The samsung splash screen as well as the recovery menus alll work...
forum.xda-developers.com
I should also add that I don't have access to settings so I can't unlock OEM and flash custom recovery / ROM. I also cannot downgrade to Android 10 (duh)
I have exactly the same behaviour here.
I ordered a "defect" A51 on Ebay which was not working. I opened it an saw a water damage at the USB-C charging board. Since there was a lot of oxydated parts I ordered a replacement for this board.
After cleaning an replacing the charging board I have the same issue as szerbi. I see the charging screen (while powered off), I can enter download mode and transfering stock firmware using Odin, I can enter recovery mode. While all these states the display works well and I cannot see any damages like a broken display.
I even got it working correctly after several Odin firmware update and recovery mode / factory reset attempts and I could install some apps and set up my google account. I was very happy. But after some hours again: no screen while Android is running.
Now, when Android is running I hear the charging and the screen shot (pressing volume-down + power buttons) sounds and the phone will be visible as a storage device while connecting to a PC.
Conclusion: The display is black while Android is running. Since it was shortly active I assume either a loose contact on one of the flex cable connetions or a water damage at the displays flex board. Unfortunately latter cannot be checked without dividing the display from the display frame. I assume this is an irreversible process.
Some time ago I wiped all my partitions on Xiaomi Redmi Note 5A, one by one, using adb. It was pretty dumb because I haven't had any experience with ARM or android. I thought it will act as x86 pc. I can remember that last thing I have done with it was flashing Arrow OS rom, the booting process was going that long that I gone sleep. When I woke up, the device was boiling hot. The android booting animation was still playing. I ran fastboot reboot and since that I haven't seen my phone working again.
I have tried already to enter recovery or do anything, but all my phone reacts to is the charging, the led goes bright (since it's a hardware condition, i guess). Except that, my device doesn't give any signs of working. I have also tried to enter the download mode by tooking the battery off (when I displace the back case using maintenance tools for mobiles) and connecting two gold-color pins and holding the power button. It doesn't seem to work. It has no chance, there is no recovery.
What I got now:
- ADB doesn't see my phone since it can't power on
- Fastboot doesn't see my phone since it's unable to enter fastboot mode
- The device doesn't react to anything
If someone could help, I would really appreciate it.
Take phone to authorized service center and let them try to fix it.
xXx yYy said:
Take phone to authorized service center and let them try to fix it.
Click to expand...
Click to collapse
I won't pay any more for this goofy ah phon. Is it impossible to fix it at home?