Hello. I have a Motorola Xoom MZ604 that operates but the screen is dark. It started this a while ago.
The device has the stock rom that came with it, when plugged in the charger, the led indicator shows it charging as it changes from white to green, also when plugged into the PC i can browse the files in it, plus tapping on the screen seems to indicate it is functional as it makes system sounds.
Could this be a software or hardware issue??
Any assistance on how to restore the Xoom back will be highly appreciated.
AnthonySanya said:
Hello. I have a Motorola Xoom MZ604 that operates but the screen is dark. It started this a while ago.
The device has the stock rom that came with it, when plugged in the charger, the led indicator shows it charging as it changes from white to green, also when plugged into the PC i can browse the files in it, plus tapping on the screen seems to indicate it is functional as it makes system sounds.
Could this be a software or hardware issue??
Any assistance on how to restore the Xoom back will be highly appreciated.
Click to expand...
Click to collapse
Reboot the device into recovery, if the screen is still really dim/ can't see it then it's a hardware issue, if however you can clearly see the text on the screen then it's software, and since your in recovery I'd suggest a factory reset if you find its software related *note a factory reset will wipe all internal data so pull what you need/want before resetting
See this for entering recovery process.
Recovery: http://youtu.be/koxgbdQuzOQ
sent from space
Related
Come across a strange problem on my TF300. The battery completely drained one night and thereafter it's become unresponsive. It charges, boots to the lock screen, but the battery is shown at 0% and I'm unable to interact with anything other than using the hardware keys. It freezes when attempting a cold boot or attempting to go to recovery. Had TWRP 2.8 on Katkiss 4.4, anyone got any ideas?
Just to update this, the dock just doesn't work with the tablet currently.. Despite being on charge for a number of hours there's been no progress. Both charging lights do go green eventually though, but still on 0%. It connects to my PC, and I can even view the files on it, but the tablet itself is unusable. Device manager shows it but I couldn't get it to appear in Adb for fastboot commands
Anyone know how to get it to show in Adb?
Bump on this since I'm out of ideas and would appreciate any help
Fixed this now, thanks to those who had a look. Somewhat simple solution, connected a mouse via USB, which allowed me to navigate the tablet. After that it was just a simple selection of rebooting to recovery from the power menu, which got me into TWRP and let me do a wipe and flash a new ROM.
Sent from my TF300T using XDA Free mobile app
A couple of months back I decided to root my device. I did this using the unlocking the bootloader method. As a result, I lost my DRM keys, and I managed to restore DRM function by following the methods detailed here: http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
I had to download the stock Android 4.4.4 from online, which I flashed my phone with - no problems. Things ran smoothly from then for about a month, and then I realised that my cellular network started to malfunction, and I couldn't access apps like YouTube and Snapchat on the cellular network. This prompted me today to do a "soft reset" of my phone, by holding the power button and volume up button simultaneously for about 3 seconds - under the impression that it would restore my phone settings back to the factory default.
Much to my horror, the worst case scenario happened. When I performed the soft reset, my phone vibrated 3 times and switched off. When I tried to turn it back on, it would show the boot-up screen indicating "SONY", followed by the next screen indicating "powered by android", and then it would show the blue screen with the wavy lines. It stayed on this screen for about 20 minutes. I figured something was wrong, and I tried to soft reset it again, only to be stuck at the blue screen once again. I decided to let it stay that way for 2 more hours, in order to drain the battery. When the battery drained, I turned it back on, and it was still stuck at the blue wavy screen.
I don't know a whole lot about Android phones, and I have no idea why this is happening, but it is causing me an immense amount of frustration - I have invaluable data on that phone, and to lose it would just be devastating. I can't even begin to describe it. I'm using TWRP recovery, and I'm also using TitaniumBackup which is backed up onto my phone's internal storage, and I can't access any of the files on my phone from my computer, because it doesn't recognise my phone.
This has been a long one, thanks for bearing with me. I've got a few questions:
1. What's the problem that's preventing my phone from booting?
2. How do I fix it?
3. If it's unfixable, how can I retrieve my data from my phone?
Really, really hoping someone can help me out on this - I'm completely lost and am desperate here. Thank you in advance!
Can you boot into TWRP's recovery mode using the volume down key?
Just press volume down when you see the green light on your notification led upon powering on your phone
Well something keeps the phone to boot, try to clean cache in recovery, it might help.
But to restore data on internal storage, count it as unpossible.
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:
I was using my phone like any other day and just like that the screen went blank. The phone itself is functioning as it should, notification LED blinks properly, vibration is working and when rebooting, the whole REDMI and MIUI animation shows up (with the screen fully functioning) but once the boot ends, PUFF, gone blank again. Fastboot also shows the bunny messing with the android, so it is not a faulty screen but some glitch with the ROM (stock fully updated) I guess.
Any insights on this particular issue without the need of wiping it clean?
PS: the MI suite says it is not compatible with the phone... so I'm super anxious about losing all my data.
PPS: since the screen isn't working I can't change from CHARGE ONLY to USB FILE TRANSFER, is there a way?
I have dropped the phone once, and the screen wasn't working.
Luckily I changed the battery before, so it was easy to open the back of the phone.
After the drop, the screen connector got disconnected somehow.
So after connecting it, it still working fine.
Check the connection if you can, and the new screen is only $20.
Not a hardware issue I think. He cried his system UI (user interface). Try factory resetting in stock recovery.
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.