I have a Pixel 4a that I dropped from coffee-table height onto a wooden floor. The phone landed on an edge and broke the internal screen. The outer glass is undamaged.
Initially there were rainbow lines all over the screen, but after abandoning it for a few days, now nothing shows up on the screen at all. Charged it overnight. Nothing. It does make the device a little warm, though. Powering it on produces no signs of life.
When I took it to uBreakiFix they checked for a minute and said since it doesn't respond to charging (no vibration) and doesn't seem to "power on", it probably has a dead motherboard as well.
However, when connecting it to a Windows laptop, it is reported as "Pixel 4a(5g)" in Settings>Devices, and an "MTP device" shows up in Device Manager.
Since I did not have File-Transfer as the default option for USB, and because ADB was not enabled prior to it breaking, I am left with no real way to test this device.
I also put another SIM into the phone and tried calling it, but it goes to voicemail.
Is this phone dead and ready for recycle-grave? Or is there any hope? Help is much appreciated!
Pull it apart. May have loose connectors.
See what visible damage is there.
No visible damage doesn't mean your in the clear but it's a start. Inspect the battery for swelling, a failed Li.
If it starts responding when you use a pencil eraser to gently push and flex the mobo different ways, push on the BGA chipsets, that's clear sign of a mobo solder fracture or broken trace. You can also try this with the phone together by putting pressure on the case at various points... don't go too nuts with it though.
urover said:
However, when connecting it to a Windows laptop, it is reported as "Pixel 4a(5g)" in Settings>Devices, and an "MTP device" shows up in Device Manager.
Since I did not have File-Transfer as the default option for USB, and because ADB was not enabled prior to it breaking, I am left with no real way to test this device.
Click to expand...
Click to collapse
you can do some things booting twrp (fastboot boot twrp.img) for your pixle 4a provided your phone bootloader is unlocked (fastboot flashing unlock vol down once then power to unlock without screen is the command). i can't remember if it wipes the phone or not. adb devices should see the phone once you boot up twrp. you should also be able to access the phone like a usb drive as well. if you are trying to pull data off it. make sure you have the latest google usb drivers installed from their website https://developer.android.com/studio/run/win-usb
this should give you some sort of start. to see if it even is responsive.
Related
I accidentally dropped my s730 today. After doing so the screen froze and the phone didn't respond in any way so I turned it off by removing the battery. After trying to turn it on all i get is a split second fail message that says "No Image Found" and then i get a red, green, blue and white screen which says "WING220 SPL-1.31.0000 CPLD-7.
In the white portion it says "Serial" and when I connect with a USB cable it switches to "USB" other than that it doesn't respond in any way shape or form I've been able to figure out yet. A hard-reset using the soft buttons and on button hasn't worked either.
Any advice on how to fix this or am I screwed?
Just flash a rom
Have you put HardSPL or something on? Wouldnt have expected the phone to allow you into that screen without changes. I also wouldnt see it wiping your OS from the phone since its an SSD not a standard disc drive. In the drop you could have damaged the intnernal memory and now its showing the default screen from the chipset?
Give what Sh1n1 said a try and see if flashing a rom will take. Otherwise you might have something broken internally that needs to be repaired.
I haven't installed hardspl or anything like that. Guess I'll try flashing a rom.
What you are seeing is the Tri-Color-Boot screen. Accessed by pressing the camera button and powering on at the same time.
Sounds like the drop made the camera-button defect. Try prying it out carefully (don't pull it out of the shell) and powercycle the phone, or try pushing it some times with the power off. The power on the device.
Hi everyone ...
I recently disassembled my G1 to fix the touch screen. I acknowledge that I took the phone's fate into my hands when I decided to open it up, but I had done this twice before with no problems whatsoever. If these symptoms sound familiar to you, please let me know if you were able to fix your phone.
I put it back together, and now when I power it on, I get the short vibration that confirms the power-on ... but I get no screen image, no keyboard lights. So when this first happened I pulled the whole thing apart again to be absolutely sure I hooked up all the flex cables and ribbon cables. Yes, everything is connected. Everything. I've triple-checked it now.
What I did next was a couple of tests to see how "awake" or functional the phone actually is behind that blank screen. When I power it on and let it sit a couple minutes, so that I know it has finished booting ....
I CAN:
- boot the phone in normal or recovery mode. both modes produce the blank screen and no key lights.
- view the phone in ADB. (ADB tells me "device" or "recovery" mode)
- execute commands and view files on the phone with ADB shell.
- pull files off the phone with ADB.
- make the LED light up by plugging in the wall charger or USB cable when the phone is off.
I CANNOT:
- make any of the backlit keys turn on by pressing them.
- make the phone receive a call or a text.
- make the LED light up by a missed call, text, or plugging in the charger/USB when the phone is on.
My first impression is that I've done something terrible to the mainboard so the phone is somehow in this "semi-booted" state, where it won't run the screen. Is it possible that a bad cable to the screen could cause this? Thanks so much for your help.
Come on, no one can help me with this? I know I'm not the only one who has taken a G1 apart and met with disappointment.
Hey all,
I just installed a new digitzer on my Vivid. Everything went fine, and nothing broke as I was taking apart the phone, or putting it back together.
Now that the phone is back together, however, it is having some problems.
First off, When I try to power the phone on, it vibrates like usual, but then doesn't display anything. The phone then proceeds to enter in to a bootloop and keeps vibrating every couple moments. When plugged in to the computer, the orange light comes on for a few seconds, then turns off. Windows will not recognize the phone. All the while, the screen is completely black, and none of the lights come on for the buttons either.
The phone was working fine before replacing broken digitizer.
The phone is NOT rooted, nor has it ever been. I am running stock ICS.
have tried entering Hboot with no avail.
Any advice?
Thank you!
Can you get into any other modes? Try to get to hboot(hold down power button and volume down) while plugged into computer. Should take it to fastboot.
how long for? I tried holding down for a good 30 seconds...nothing happened other than my orange light turning off
I noticed with mine I had to go with:
Remove battery.
Replace battery
hold vol down + power
few seconds later release power
few seconds later in hboot
YMMV due to repair.
You can also try a knoppix boot disc and some tutorial to see if you can find any sign of life off the phone in dmesg.
hope this helps some.
Sounds like a loose connection. Make sure that you've correctly reconnected all internal connections. Especially the connection under the little door with the void sticker on the screw in the battery compartment. If after verifying all connections are made and proper, the problem persists, I'm sorry to say you may have physically damaged the connectors during disassembly. Please visually inspect all connections for damage. A powerful magnifying glass is recommended.
(I have successfully replaced my digitizer twice, and my LCD panel once on this phone...)
Sent from my HTC Dark Raider using XDA.
I have taken it apart twice, checked all connections, and everything is good. Phone cannot enter any boot mode, and computer still doesn't recognize it. The orange light still only stays on for a few seconds when plugged in, then turns off. The phone then proceeds to keep trying to restart itself, but the screen remains pitch black blank
idk.. get a replacement.?
My phone went to an endless bootloop after a botched attempt to install TWRP. I tried hard pressing the power button to no avail, and I can't access fastboot either. That's why I removed the back cover and disconnected the flex cable from the battery on the phone's motherboard.
Later on, I reconnected my phone's battery after my shift ended, then I tried to flash my stock rom through SP Flash Tool + bypass tool python script and it went through with a success. However, this time, my screen seems to be completely dead but my phone is still showing some signs of life (short vibration when pressing the power button, but since then it seems that it takes a few seconds more from pressing the power button to turn it on. ) I reconnected and disconnected everything to see whether or not I missed out something but the issue still persists.
The computer reads the device as "Android ADB interface" and the adb console reads it as *device id* unauthorized when I ran adb devices command. There's no notification light whenever I plug it into the charger.
Is my screen dead, or is my motherboard toast? I need to know as I don't want to spend money to buy a replacement LCD only to know that the motherboard's dead. I don't really care about the IMEI as I'm just going to use it as an authorization device for work. I can just always connect to Wi-Fi. Please advise.
One problem after another, so it seems.
Turns out I already unbricked the phone, but the thing is that my display's backlight got busted for some reason. Unless I shine a flashlight through it, I won't know what's in the screen. I'm currently on the way to get a replacement screen, and a new battery cover.
I guess this will be the last Xiaomi device that I'll ever get. This is the only time that I experienced such flimsy build quality since the LG G4.
Maybe you have destroyed a lil cable or something.
Aleatory YouTube videos explaining the problem and possible fixes, I don't recommend this channel, I don't know the YouTuber.
ROG2 here turns off and not power on again after gaming and charging same time (it's dead). Someone here tried one of this with success?
Change IC PM8150B
Reballing the CPU
Hello there!
I have no experience with your problem. Just going to say that from the top. I've never torn a phone down, and when hardware components need replacing that's when I usually decide I need to pick up a new phone.
I just recommend you make sure the phone you're trying to fix like this actually needs it. I've messed with my tencent rog ii quite a bit lately and I have had the phone go completely black - thinking I had thoroughly destroyed my phone, but I was able to get it running again.
It's possible that the complete "power off" that you are reporting is the phone being in EDL mode as the phone gives no indication whatsoever that it is on when in EDL mode. As a hail mary maybe you should quickly try this before tearing your phone down.
go to this guide, and download the zip file in the main post.
Repair your ROG2 phone with EDL mode，Official firmware！
Success is disgusted by some people, and will not share any files for free in the future.
forum.xda-developers.com
extract the zip, then go the the folder "qpst.win.2.7_installer_00453.2" and run "QPST.2.7.453.msi" - this installs the drivers necessary to communicate with your phone when in EDL mode (this may not be necessary, as your pc may identify a usb connection without this, but just to check 100% I'd install the drivers anyway.)
charge your phone for at least 30 minutes. just to make sure it's got juice.
use a DIFFERENT USB-C <-> USB-A cable than came with your phone (pick one up at the shop if you're not sure. ALSO plug your [charged] phone into your PC using the side USB port on the phone (Not the bottom usb port). This is because ASUS's cables don't seem to support flashing, so I'm suspicious if they'd work appropriately in this case, and because the side port is the only one that works for flashing and the like.
now open device manager (press windows key, type "device manager"). with that screen open, plug your phone in. On device manager you're hoping that a device appears under the menu "Ports (COM & LPT)" probably named something to do with Qualcomm.
if nothing shows up, unplug the usb port from the side and hold all three side buttons down for 20 seconds (vol +, vol -, and pwr) and keep an eye on the upper left side of the device where you MAY see a red light flash indicating signs of life. then plug it in again. if nothing happens unplug the phone, and hold the power button for 5 seconds, and plug it in again. if nothing happens, unplug it and try holding down just power and volume up for 20 seconds, then plug in again. If nothing happens, try power and volume down for 20 seconds, then plug in again. (you see where I'm going?) just make absolutely sure your phone has a hardware problem and can't connect to your PC in any way before performing surgery. If the device does show up under this "Ports (COM & LPT)" device it means your phone OS is thoroughly trashed. check out that same guide I linked, as well as this youtube for some ideas how to get it going again.
If your phone doesn't connect no matter what, and you're certain you've gotta get into the hardware, then I wish you the best of luck. I really wish I could be of any further assistance with regards to hardware. maybe if you do take that road let us know how it goes.
good luck!