Bricked my phone (Stuck WSOD while booting up) - Nokia 7 Plus Questions & Answers

FML.... Here goes some background story (lazy to read? skip to next paragraph). One day found my Nokia 7 plus bent a bit (top right corer) it was working perfectly fine, but my OCD made me "fix it"... After bending phone the other way, to straighten it - Power button stuck (pushed in). Phone got into constant restart loop, and eventually ended up in download mode. Since I couldn't do anything - left it as is until battery died. After gathering all the tools, I've dissembled my phone, fixed stuck power button, charged battery, turned it on - I found out that I cracked the screen.... Bought new screen and replaced it.
Now when I turn on my phone (in fact it turns on automatically, after power off it will turn on again after few seconds), it vibrates and goes to WSOD (white screen of death)
I can't enter recovery mode
I've tried workaround as per this thread: https://forum.xda-developers.com/nokia-7-plus/help/device-stuck-download-mode-t3934323
fastboot devices - returns my phone, however adb devices - does not.
Any ideas how I can get back to life?

Related

[Q] Massive Problems

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.?

No boot / freezez

Hello,
Today my phone suddenly froze. It happened before so i didn't care much about it and left phone for some time. Unfortunately, I'm not able to boot system anymore, because phone turns off right after first white HTC logo screen. When I boot into recovery only up and down buttons work, pressing on/off button causes phone freeze.
Phone is rooted (ROM - insertcoin-7.1.3), since few months and till today it was all working fine. Conecting it to laptop it was recognized as RELINK device (but it doesnt work anylonger) so I think it might be over. Any idea what to or what steps perform to bring it back to live?

HTC One M7 non-rooted, hard reboot loop - need help

I've got an AT&T HTC One M7. It's non-rooted and has stock firmware. Android updates from AT&T are installed when pushed. It's all pretty routine. As of yesterday evening, this phone started rebooting and won't stop.
If I leave it alone, it vibrates (normal startup notification), goes to the green on white "htc" screen for a few seconds, then goes blank and starts over. I can get to the bootloader screen, and I've gotten it to start in safe mode as well, but it always restarts again within a few seconds.
Things I've done/found:
- Holding down the volume down button while it restarts takes me to the bootloader menu, but the buttons don't seem to work correctly when I get there, and it always restarts again within a few seconds.
- I managed to start it in safe mode a few times--I think by holding volume up and volume down at the same time--but it restarted before I could do anything.
- I removed the SIM card. Same thing.
- I let it reboot until it died. As soon as I plugged it in, it started the same thing again.
I'm starting to think it's hardware failure, like the power button is constantly making contact, even though the button feels fine to the touch. Note that I get to the bootloader just by holding the volume down button. I don't have to touch the power button. I'm not certain whether that's normal. Can anyone give me any ideas or even just verify that it seems like a hardware problem?

Looping between charging/Android logos

Hi, so I got an A2 which has been submerged in water for a while. I was not turning on at all (just showing the white led light blinking), so I bought a new USB part and battery for it, replaced it, and now it seems to react.
However, it keeps switching between the charging logo for a second, then vibrates and shows the Android One logo (this switch goes on and on forever). I have tried the button combo to go into recovery, but as soon as the Android recovery boot logo appears, it'll still timeout into the charging logo.
Does anyone know what may be going on? Or what component to replace? (the phone was only days old when it accidentally got soaked, so everything is new and it's a shame to just throw it away)

Screen is dead after disconnecting/reconnecting battery.

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.

Categories

Resources