After replacing the B screen, the phone goes into a boot loop, and seems to corrupt the data partition. After resetting the device it boots normally with the display closed, but crashes and corrupts when opened. I've seen another similar post on here and am wondering if it's possibly that the original screen was "paired" to the device similar to apple and touch id, or if there's a way to fix the issue.
Related
Greetings all!
I have an AT&T Tab that I got a few weeks ago, and yesterday I let my curiosity get the best of me and decided to flash the Euro firmware to enable the calling function. It flashed flawlessly and, popping my personal SIM in, I could easily make calls and text and was pretty happy with the experience aside from two things. First, the home screen was no longer centered (page 3 of 5) but was on the far left on page 1. Petty concern, perhaps, but I really prefer the symmetry of the stock AT&T layout (as well as HTC Sense). I haven't enjoyed any aftermarket launchers so I didn't want to bother when them, and that would have been acceptable enough if it didn't result in the loss of my Media Hub and the $50 credit I got from registering the device with Samsung. Also perhaps a petty concern, but a concern nonetheless.
After getting it fully rooted and adding apps, the Tab would freeze horribly, becoming completely unresponsive and requiring a hard reset. This was after installing Titanium. But by this time, I decided to have a go at reflashing the stock ROM as provided by rotohammer. He did indeed warn us that there was no boot screen, and he was correct. Aside from that the experience is completely stock and just as it should be.
But the reason for this thread is...WTF can I do to get some sort of flash screen and boot animation so I'm not looking at a black screen for ages until the lock screen comes up? I've tried replacing the boot animation ZIP file with some files provided on these forums using Root Explorer, and it has no effect at all.
For some of you brains out there, I'll present a bit more info that may be of some use if you're willing to try to figure out a resolution to this:
Upon powering it on, the Galaxy Tab Samsung image appears for a second or less, then the screen goes black. After a few moments you hear the chime that accompanies the normal Samsung boot animation, but the screen is still black. Finally, after the typical length of time for booting, you can access the lock screen, but you have to hit the power button to get it to appear; it doesn't just light itself up as it should. I actually have to put it to sleep with one push, wake it up with another, then the lock screen appears and I'm using my Tab like normal. There was one time that I pressed the power key as it was booting and I saw the image of the boot animation briefly, but that's not typical.
Another thing that might help you figure out the root problem here is that I can't boot in Recovery. I power off completely, hold down the Power and Volume Up keys until I see the backlight come on, but the screen remains black. I can't actually see any of the text on the screen, but I know from experience that the device is in Recovery because if I hit Power, it reboots again, just as it would if pressed in Recovery (when the reboot option is highlighted).
When I put it in Download mode, I do see the normal screen with the Android shoveling.
Surely the inability to see splash screens and boot animations is related to not being able to see the Recovery menu, right? Can anybody help me get a splash and animation going on this without affecting anything else? I know that this too may sound petty to some, but I really want to make this the perfect tablet experience, like it was before I started messing with things.
I should also note that the shutdown animation works just fine. So far the entire experience seems pretty normal once you get past the boot.
Several peeps have had a blank boot screen issue after flashing a rom on att tabs; myself included. The blank boot screen usually has a thin white line, too.
Maybe check out this thread for some ideas: http://forum.xda-developers.com/showthread.php?t=928076
Sent from my GT-P1000 using XDA Premium App
fwelland said:
Several peeps have had a blank boot screen issue after flashing a rom on att tabs; myself included. The blank boot screen usually has a thin white line, too.
Maybe check out this thread for some ideas: http://forum.xda-developers.com/showthread.php?t=928076
Sent from my GT-P1000 using XDA Premium App
Click to expand...
Click to collapse
Thanks for the link! I looked around but didn't find any proposed fixes. Obviously overlooked this one.
However, that fix seems to be for people who go from stock to custom. In my case I went from stock to Euro and back to stock, but the resulting symptom is the same as described in the above link - except I have no white line, it's just black.
Given that I went back to stock and have this problem, will the above referenced fix work for me, or am I FUBAR? I don't want to risk bricking it just to fix the boot animation issue.
I cannot say for certain if it will help in your case. But here is my sequence of events that cause blank screen and when I applied the fix in the link:
Stock (non-blank boot)
Jmev4 rom (blank boot screen started)
Jmiv2 (never bothered to fix boot screen)
Overcome 1.3.0 failed install due to blank boot screen and cant 'see' recovery mode
Jmiv2 again fine but with blank boot screen
Follow link to fix blank boot
Jmiv2 now with fixed boot screen
Overcome 1.3.0 success!
So maybe you can apply fix to stock?
Sent from my GT-P1000 using XDA Premium App
Hopefully some of our dev wizards can chime in? I'm wary of trying something out that might turn my Tab into an expensive scrying mirror.
I ran the fix for the blank boot screen. Odin declared the flash a success but I can confirm that it didn't fix a goddamn thing! There is absolutely no change in the device whatsoever after installing the jj4 bootloaders.
Just to confirm, it was downloaded as a .ZIP file which contained a .TAR file. It was the .TAR file that I added into the PDA field; that was correct, right? Or was I to insert the .ZIP in the PDA field?
Does anybody have any idea why there's no visible splash screen, boot animation or recovery mode screen? Rotohammer: are you still alive? I got this stock ROM from your post; surely you've figured something out by now, no?
If Samsung/AT&T finally release 2.3, do you think installing it will resolve this issue? Where is everybody that could help with this??? Have they all forgottten about the Tab and gone on to bigger screens/greener pastures?
Greetings,
I'm not experienced with android devices, so i thought i'd ask here first before trying to do anything.
Since a few months ago some weird things started happening to my X8 - random display glitches and blackouts at completely random intervals (sometimes one or even two a day, sometimes it can last two or more weeks w/o an incident, i haven't figured out any relation yet).
Glitches manifest in distorted view on screen - shifted up/down/sideways - or colored graphics artefacts - up to completely bizarre patterns of random-colored pixels covering the whole screen. Weirdly enough, pushing power button as if to lock the screen usually alleviates the issue, sometimes i need to do it few times to remove completely, but it works. Touchscreen works fine, but i need to tap the "right" spot on the screen, not where it's displayed on the screen ("right" as in where the element is when the screen is not glitching).
The other issue (may be related) i'm having with the phone is random screen "blackouts" - the screen goes completely black and the power button cycling doesn't help - but the phone still reacts to screen input (i.e. i can unlock the screen by dragging the slider, launch app, start/stop music playback and so on). I can see the backlight on, so it's definitely screen/gfx hardware issue, not backlight. If i try to reboot the phone, it hangs on either shutdown or boot up. Removing the battery, placing it back and booting the phone up doesn't help - it vibrates as usual, i see the backlight go up, but screen stays black and i can't interact with the phone even if i leave it there for a few minutes (which is more than enough for it to boot up - it usually takes ~30 seconds till full boot). Also the backlight won't go off. It usually helps to boot normally if i hit the phone with a palm on the back side and/or leave it alone for a while. This issue is much more rare (only had it three times), but it puts the phone out of service for a while, so it's an issue for me.
Now, the device info:
Sony Ericsson Xperia X8 E15i
015 baseband
10W44
Unlocked bootloader
Alfs8 kernel (2.6.29.6-Alfs v08a 24/03/2012)
GingerDX v026 ROM
No cpu tweaks done, cpu governor "ONDEMAND", cpu speeds 122-600.
The glitches started when i was still using the older version, GindgerDX v013 with locked bootloader, i have done factory reset and flashed a new version with new kernel (and unlocked the loader along the way), but apparently it did not help fix the issues.
I can't provide and screenshots/photos of the issue because the only camera i have access to at most times when it happens is my phone one and, obviously, i can't use that in this case
The question is: can i still try to fix it by myself (i can do it if it doesn't involve disassembling the phone completely - i don't have the screwdrivers required) by software tweaks or other techniques or should i reflash stock kernel/rom, apply for warranty and hope they find the defect and fix it? I really do like the phone. Or, maybe, you have encountered anything resembling these issues and may shed some light on what's happening.
Appreciate any input in trying to figure out and fix this.
Thank you if you have read all this even if you can't help me, cheers!
1st problem could be 'Screen Cut' issue which is solved using kernel without FPS Cap...
2nd problem usually happens on my phone with miniCM9 3.0.2 but shows splash and boot animation...
Can you see the splash screen and the bootanimation? Because my friends' Xperia Ray has the issue on official firmware... so it could be hardware damage...
Try unlocking the screen then press the power button then press it again...
and also try flashing the stock firmware... If it doesn't work... I think you should live with it...
Sounds like a hardware problem to me. Reflash stock kernel and ROM and full wipe and then flash a different ROM and see it it still happens. If it does I think it is advisable to send it to Sony for repair.
Sent from my E15i using Tapatalk 2
Thanks for your replies, i'll try reflashing the stock rom and see if it still happens.
@Lily48: no, no splashcreen or boot animation, just black screen and visible backlight.
I have the same problem and I checked it many times and my conclusion is....ITS A HARDWARE PROBLEM NOT SOFTWARE..
KASHYAP9 said:
I have the same problem and I checked it many times and my conclusion is....ITS A HARDWARE PROBLEM NOT SOFTWARE..
Click to expand...
Click to collapse
Well, notify me if you find a solution, thanks
Sorry for double post, but this is important update:
My phone died this morning with the permanent black screen syndrome. Until i rebooted i could use it to receive phone calls or even listen to music (i knew where to touch to activate the features). However it would not boot sompletely after restart, even if i leave it for ~hour. Connecting to flashtool showed that it does boot to a certain stage, but no GUI (for user interaction with haptic feedback) available - the flashtool does show that device connected with usb debugging enabled.
I reflashed the stock ROM, now it's apparently stuck in some sort of bootloop - it keeps on connecting and disconnecting. But the screen is still black, with backlight. If i remove the battery, replace it and just connect to pc w/o trying to boot on, it acts normally as if trying to charge - backlight activates for a few seconds if i touch a key and green led is lit, but still the screen is black.
I will RMA it tomorrow, thanks for help, hopefully i'll get a new one, or they'll repair this one so it does not glitch on me again. Anyway it was/is a good phone, i absolutely love it.
Wish me luck =]
Aessaya said:
Sorry for double post, but this is important update:
My phone died this morning with the permanent black screen syndrome. Until i rebooted i could use it to receive phone calls or even listen to music (i knew where to touch to activate the features). However it would not boot sompletely after restart, even if i leave it for ~hour. Connecting to flashtool showed that it does boot to a certain stage, but no GUI (for user interaction with haptic feedback) available - the flashtool does show that device connected with usb debugging enabled.
I reflashed the stock ROM, now it's apparently stuck in some sort of bootloop - it keeps on connecting and disconnecting. But the screen is still black, with backlight. If i remove the battery, replace it and just connect to pc w/o trying to boot on, it acts normally as if trying to charge - backlight activates for a few seconds if i touch a key and green led is lit, but still the screen is black.
I will RMA it tomorrow, thanks for help, hopefully i'll get a new one, or they'll repair this one so it does not glitch on me again. Anyway it was/is a good phone, i absolutely love it.
Wish me luck =]
Click to expand...
Click to collapse
It is a hardware problem and Sony Service Center is the last option you have.. if your X8 is in warranty period.
I did the same and they replaced its display with new one.
Hello, reporting back in:
Just got my X8 back, it really was a hardware problem. They changed the screen now it works as good as new =]
Thanks everyone for support
This morning during a call my phone shuts off for no reason. It is not rooted no physical or water damage. I tried to power it on it will vibrate than attempt to start get stuck at boot screen than eventually turn black. I tried booting into recovery to hard reset I will get to the menu do all the prompts and get the lg logo and back to black screen. I don't know what is going on. Is this a common issue? Admins if this is in the wrong section feel free to move it.
Kingaries79 said:
This morning during a call my phone shuts off for no reason. It is not rooted no physical or water damage. I tried to power it on it will vibrate than attempt to start get stuck at boot screen than eventually turn black. I tried booting into recovery to hard reset I will get to the menu do all the prompts and get the lg logo and back to black screen. I don't know what is going on. Is this a common issue? Admins if this is in the wrong section feel free to move it.
Click to expand...
Click to collapse
Not sure what caused the issue but if wiping from recovery doesn't work I would look into restoring phone with kdz file. Sucks to do that seeing as all data will be gone but hopefully you have a backup. If restore doesn't work you need to call T-Mobile for replacement
Sent from my Porn Infested G4
The replacement has been processed. Unfortunately trying to factory ? reset doesn't work because the phone ? wouldn't stay on long enough for that to happen. Love to know what actually caused this issue. Kinda kicking myself for not doing a weekly backup.
I actually got the same problem on mine but mine is rooted and was working fine but then randomly my phone is doing bootloop. I don't have terp installed and I'm I only able to boot up to software upgrade mode. Ive tried the step for format everything with holding the volume up n on button but after I did the reset stuff still does boot loops. Also another problem is that whenever I plug in phone to computer it doesn't show up, so I have no option to add roms or anything like tht to internal or sd card. Is there anyways too flash anything of the software mode, if so can you plz let me know thank you.
Today I replaced my cracked Redmi 4X screen. The replacement consisted of a screen+digitizer+frame assembly (no messing with a heat gun to detach screen+digitizer from frame). I think it went fairly well, took my time and didn't force anything.
However, when testing the screen halfway through reassembly, it was stuck on the mi logo. I decided to complete the reassembly, thinking maybe it did a hardware test and refused to boot as i hadn't reconnected all parts. No such luck, even when i use the old screen it doesn't boot .
The charging led also doesn't come on when attached to a charger or laptop usb port, which seems weird. I think the battery is about 50% but right now i can't even turn it off. It just reboots when holding the power button. It doesn't enter recovery when I hold the volume-up button. I do get a fastboot logo when booting with the volume-down button. But no response on the USB cable and the logo just stays on exactly like the mi logo in normal boot. I'm not sure but I think fastboot is supposed to show some kind of menu interface? Or is it normal to see a fastboot logo only?
I've read some other posts about Xiaomi phones using different brands of digitizers, having to clear the cache to reset it and accept a different brand, but when I detach the digitizer it doesn't boot either .
I could try a factory reset with mi flash but it requires Windows which i don't have easy access to (if it even detects the phone). Perhaps there's a way to rescue it that doesn't involve losing all data, i might as well just buy a new phone if i have to reinstall/configure everything. anyway.
Any ideas?
I've got a strange bootup problem that I can't find any help on. My S20 FE 5G fails to boot properly on every other bootup. On the failed bootups, it spends 3-5 minutes on the initial Samsung S20 FE 5G splash screen (the one with the android logo). When it eventually gets past that screen, it boots up to the lock screen and prompts me to swipe, but all touch input is ignored. My only option is to hold power and volume down to force a power down. Powering back up, it will boot normally, spending only a few seconds on the splash screen before booting up and functioning as expected. It's been doing this for a long time, and today I finally got annoyed enough to try a factory reset, which hasn't solved the problem. I also lined up a safe mode boot with a failed boot, and the touch screen still didn't work in safe mode. Anyone know enough about how these phones boot up to explain why this alternating pattern of failures might occur? Is it alternating between two images of the OS and one of them is possibly corrupted? Is there any debugging method I can use to try and figure out what's going on?
I'm new here, so if there's a better place to ask this question, please let me know. Thanks!
I'd try flashing a stock rom to the phone, see that fixes it. if it doesn't you should get Samsung to look at it.