Saturday my S7 Edge - stock ROM, no root - BSODed:
I picked Up my Phone but it wouldnt turn on the display. no reactions to any button or combo (forced reboot, download mode...).
LED flashed blue like a notification.
I let it run the battery low so it turned off (at least the LED went off).
It doesnt load anymore unfortunately, at least the display wont show anything. Still no reactions to any button when plugged in for hours..
I disassambled it and replaced the battery unit but no change.
Maybe somebody who has gone throughb this too or anyone with a hint?
What could be broken, so I could swap the parts from another one (i.e. a used one with broken display).. the disassably tutorials mention a a"logic board" (=mainboard?), could that be it and is there any hope to recover the internal storage?
Update:
I had to replace the logicboard, so either CPU / RAM / flash storage are broken. I bought another S7 edge with a broken screen for a few bucks got get the "spare parts" and followed common tutorials for disassembly. Phone is back to live now but wirh the "new" IMEI + flash drive.
I was lucky I had Google Backup enabled so I didn't lose any important information.
Related
I using my Xoom earlier today and after a while I noticed that the display looked a bit strange. On closer inspection/further use, there is *massive* ghosting/burn in (I think).
If I turn the screen off/on, I can actually see through the lockscreen to the homescreen underneath. When I unlock it I can see previous apps burned in there.
If I shut it down and reboot, I can see the homescreen through the bootscreen (which should be completely black excepting the red Moto logo and the ripple effect).
I've only had it for about a month and mostly use it for browsing the web/facebook and reading comics. I could understand gradual burn-in if I was using a certain app really heavily but that isn't the case here. It seems to have gone from fine to completely f**ked in the space of about half an hour.
I guess my question is, is there any chance it's software based and a factory reset will help or do I go back to where I got it and try to get it repaired/replaced under warranty? And if I do take it back, is the fact that I rooted going to cause problems?
*************
After a factory reset (which did nothing) I used OTA RootKeeper to try and unroot before sending it to Motorola (turns out it's only a temp unroot), then used Titanium Backup to restore apps + data and the display returned to normal as suddenly as it broke 0_o
I have no idea what caused the problem and no idea what fixed it but it seems fine now 0_o
0. Specs
My Samsung Galaxy S6 G920F 128GB keeps crashing.
N.B.: This is also a bit of rant....
The device is unlocked and was flashed just after it was bought with the BTU firmware for minimal bloatware and crapware, and of course that B(r)itish Humor Since then it was updated several times OTA. It's running 5.1.1 right now.
OffTopic: Seriously Word, Exel, Powerpoint, OneNote, OneDrive. I didn't want any other apps on my phone... ESPECIALLY AFTER AN UPDATE ! ! ! In any case WTF SAMSUNG?
1. Symptoms
- Nature of crashes:
1.1 - Screen freeze
1.1.1 - If music is playing on internal speakers the device will emit a "noise loop", does also happen with headphones.
1.1.2 - After a freeze the device will:
1.1.3 - only restart if a soft reset is performed (DOWN and POWER pressed for 7 seconds)
1.1.4 - reboot
1.2 - Reset immediately without rebooting to lock-screen
1.3 - The device also freezes in Safe Mode (DOWN while booting)
1.4 ! - The device also freezes sometimes while charging and powered of: The LED is red and it does not react to POWER or HOME
1.5 ! - The device also freezes while on recovery menu (HOME and UP at boot)
1.5.1 - It even froze when factory resetting; I then did a soft reset and it rebooted with that blue screen with the Android; after a few seconds it added "Erasing...."; it rebooted successfully into ANDROID with lock-screen....
1.6 - If the device is charging a reboot will not be initiated; it's only powered off
1.7 - The phone also powers off sometimes
1.8 - Crashes at random intervals
1.8.1 - Some just after booting and before any SIM-PIN entry is possible
1.8.2 - Some take place after a few minutes of usage
1.8.3 - Very rarely does the device function longer than half an hour without a crash
2. Already tried (unsuccessful in eliminating crashes:
2.1 - Reset of cache (several times)
2.2 - Factory reset/Data wipe (several times)
2.2.1 - From recovery menu
2.2.2 - From settings
3. Other Symptoms:
3.1 - The device will not display "Starting Android Apps, or whatever it says..." on startup
3.2 - Sometimes it emits a disturbing crackling noise right after the lock screen; actually I kind of like it now, it gives you a nice warm feeling just like the old tube TV had that crackling noise...
3.3 - I think it has a shorter battery life for the last week or so, I might be wrong, or it might be due to normal usage
3.4 - It gets quite hot while fast charging, especially the OEM-MICRO-USB-TYPE-B-CONNECTOR gets very hot, so hot you would burn yourself if holding for a sufficient amount of time (probably more than a minute or two), I'm not sure if this is related to the original issue
As with capitalism one thing is sure: The next crash will come. While writing this( using the auto save feature) the device restarted more than a dozen times. The device goes from not usable at all to annoyingly usable.....
4. What might cause it:
4.1 - Something in CACHE or RAM or TEMP (temporary files on the file system) is not deleted as it should be.
4.1.1 - The other day I read that there is an issue with ENCRYPTION as the device will boot WITHOUT PASS CODE if it has crashed or shutdown due to lack of battery, maybe the issue is the same?
4.2 - Hardware defect:
-Maybe but: I had the issue a few months ago and a factory reset resolved it, but why not now?
4.3 - Maybe I'm using too much internal storage?
- Apple Music had ~30 GB and
- Videos ~40GB most ~100MB
- Music ~ 3GB
4.3.1 - Just some crazy thought: Does ANDROID have TRIM? If not might I have not left any free pages for it to write to?
5. What can be done:
5.1 - Continue using the phone
5.2 - Bring it back to shop (the phone came with a contract for two years) and try to get a new one, but how am I going to reproduce random crashes?
5.3 - Eventually buy an iPhone
- I'm actually not joking on this one; I will. But how will I put music on it, just how, how???
Thanks for reading. Do you have any suggestions?
Hi did you ever find a solution for this? I am experiencing the same thing, I even sent it to Samsung via RMA, but they could not find anything wrong. I got it back and it continues to freeze and restart.
Nah I returned it (to my carrier) while it was freezing and got a new one after two days.
Try to make a video so that no can argue that the unit is not broken or even better: Show it broken/freezing/restarting for no reason to the retailer where you have bought the phone.
Also depending on your jurisdiction you might have the right to a flawless product within a certain time frame i.e. EU: 2 years, AUS: 3 years.... besides the manufracturer warrenty!
Anyways good luck.
Hello, my Xiaomi 4's motherbaord is damaged, the phone still functions and comes on but the screen is completely black. It does not work at all. (I know it comes on because there is a black light so the black screen sort of lights up from the back light) Ive accepted its broken but I need the data thats on it very very much, there are very important notes, pictures, contacts and messages that I need to access....Usually I would jump to misuite and let it back up my phone or get to my internal storage through it but due to some bad luck, misuite seems to have a problem of itself at the moment. When I connect my broken screen phone, misuite displays the message "You need to upgrade your device to use Mi PC Suite. Update your device before connecting" I've come to understand that this means that misuite itself does not support higher versions of MIUI. That misuite has a problem.....I really do need my data.....can you help me at all?
Hello, first of all, sorry if I'm wrong section or if my English sucks but is my first discussion on xda.
I have a big problem with my 5x nexus since yesterday morning when i turn on the screen there are some lines that prevent me from using the phone, i'll explain it better, the screen is locked, but the cellphone seems to work because i feel the vibration of the unlock And even the sound, the phone is normally detected by the PC, both in mass memory and in fastboot and adb. The only way I have to use it is to turn off and turn on the screen several times (about 50 or more), and every now and then the screen returns normal, and until the shutter closes the cellphone works perfectly. I thought it was an old rom problem since i had the nexus in April, then yesterday i completely deleted it (system, recovery, cache etc.) i even put everything back to root without root and then i put the google pixel rom, and it seemed It works, but this is the same again this morning. The strange thing that made me worried is that it happens the same even when I go into recovery, fastboot or even while the cellphone starts. To change the rom or do else i used the nexus root toolkit, and there is also the function that makes the screen on screen and seeing the photo on your computer comes out of the normal unlock screen ... I do not know more than do. (I forgot while this screen is present the touch does not work). I could not upload a photo here, but I found a similar image on the internet (I can not put it because I'm a new user )
:crying::crying::crying:
Hi everyone,
I got on my hands an s6 with a broken screen, glass is fine, but it stays black.
I'd like to kinda recover it somehow, but I'm afraid it's not just a "screen issue", so I'd like to test it mirroring its screen via usb (unfortunately S6 doesn't support HDMI). The point is that s6 needs usb-debug to be turned on in order to do this.
I thought about how to blindly enable it helping myself with my main s6 side-by-side, but I'm not sure what Android version the broken one mounts (probably it's not been updated since it was bought), so it seemed not to work.
Is there a way to turn it on, maybe flashing a tweaked kernel? Would you suggest any other solution?