Recently, I tried flashing a new ROM (I forget which one now, not fully important to the story), but when the phone came back on after installing, it did the Samsung and Galaxy boot screens, but the screen went black and never came on. After a couple minutes, the phone would vibrate once, then a few seconds later vibrate 3 quick times, like something force-closed. Only since the screen is black, I can't see what it is.
The only thing I could do was restore the backup, which contains the ROM with all the circle-icons in the notification bar (I forget the name, but it's a 4-section circle battery, a 4-section circle signal, a circle with 3, 1X, or W in the middle, etc).
I've tried 3 different ROMs, and all result in a black screen, force-closing, and having to restore to this ROM. Any ideas why, and any help to fix?
minmongoblin said:
Recently, I tried flashing a new ROM (I forget which one now, not fully important to the story), but when the phone came back on after installing, it did the Samsung and Galaxy boot screens, but the screen went black and never came on. After a couple minutes, the phone would vibrate once, then a few seconds later vibrate 3 quick times, like something force-closed. Only since the screen is black, I can't see what it is.
The only thing I could do was restore the backup, which contains the ROM with all the circle-icons in the notification bar (I forget the name, but it's a 4-section circle battery, a 4-section circle signal, a circle with 3, 1X, or W in the middle, etc).
I've tried 3 different ROMs, and all result in a black screen, force-closing, and having to restore to this ROM. Any ideas why, and any help to fix?
Click to expand...
Click to collapse
Use Adrynalyne's All-in-one DJ01 .tar, flash it through Odin, re-root, flash RED CWM, flash up to EB01 to whatever ROM you want.
I would also recommend wiping data, cache, and Dalvik cache before you flash anything Froyo-based (when coming from DI01).
Related
OK, so I successfully installed the ROM. It works fine and all until I actually use openscript on the terminal. For example, I wanted to change CPU frequency. I changed it, quit the terminal, and checked the frequency in system information. It was successful. But After about a minute my screen suddenly locked and here is the current situation. The locking screen works fine (I had the pattern lock), I can even open emergency calls. But when I unlock it, the only thing I see is the notification bar (which works btw, clock, wifi , all the icons are there, I can slide it down and up and so on). Everything else is just black. The buttons work - I can quit the notification tab buy clicking back or home or something like that. But I dont see my home screen, menu, buttons - nothing. I can lock it again, and it works fine again in the lock screen but afterwards same black screen again. Reboot does not work.
So I reinstalled the rom. Immediately after installing changed the frequency and waited for a bit. Everything was fine. I installed all the crap I usually have and kept using the phone. But the next day, I got annoyed by the music player and decided to change it again via the openscript. Same thing happened. And this is where I am stuck right now (actually this is already the third time I have this problem in 3 days and it's my third reinstall of the rom, but the first one also happened after using openscript to change frequency.)
So is there a way to fix this without reinstalling the rom again, cause I've customized the **** out of it and I don't wanna do it again. If no, how can I prevent this in the future?
P.S. If this helps, when rebooting, I hear the sound before the android splash screen which is sometimes skipped and sometimes shown for an unusually short time.
P.P.S. Also, I have the apps2sd flashed.
Any help would be appreciated.
Thanks.
Got same problem
Hi,
Even I got same problem when I tried to change boot animation. Just blank screen.
But i realised it is due to, launcher app is not initiated. So tried a trick which worked indeed
Trick is when u are in a blank screen, click "HOME" button which will pop u up the list of launchers u have. Click One of them though they r not visible
Voilaa!!! Your screen is back
Regards,
Murali
Ok So my TFP starts out of the blue rebooting on me from time to time. and then i had to reboot it like 3 times or more to get it to where when i slide to unlock that it would actually unlock instead of have the lock circle on the unlock but never go any place then it would reboot by itself. i got stuck in a loop where no matter how many times i rebooted it got stuck on lock screen and rebooted. so i hit the reset button and jumped in 5.8.2.0 and restored from a back up. it booted up but i noticed that i my home key and setting from the right side did not work. and the lock screen does not come up any more when i turn on and off the device. Anyone have this problem? seems no matter what rom ive tried same results. lock screen no longer comes up right side quick setting no longer work. i did wipe everything before flashing. also for a side not tried to restore to stock image from my backup and got error while it was trying to put the data folder back. ive always used the 5.8.2.0 so not sure what the hell is going on. Any help would be appreciated. Almost feels like there is a problem with my primes memory.
Hi, so sorry for the vague thread title, but really, there's no other way to describe it. So here's what happened.
For the past few weeks (or month), my Xperia Ray has had a problem of switching on after it was put into standby mode, i.e. after i pressed the lock button. The screen would light up, however would remain blank. So all I would get is a bright black screen.
I could have lived with this for a few more months (until Xperia Z gets released in my country D: ) however this problem started getting worse. At first, after pressing the home button, the volume rockers and/or the lock button for about 20 times, the screen would turn on (finally). Despite it giving me that bright black screen, i could still operate the screen. I could still try to unlock it because of the haptic feedback on my lockscreen. I could still change music tracks on my music widget on my lockscreen. In short, the screen worked perfectly, only that it kinda wouldn't show. However, for the past week, the only way to turn it back on would be to do a battery pull and switch on the phone again. And it recently developed a problem of giving me that bright black screen again when I switch it on, causing me to do about 5 battery pulls before being able to actually use my phone again.
I did get fed up with this problem, being a heavy user of my phone. Therefore, today I decided to try to do a factory reset of my phone, intending to wipe the dalvik cache + clear all user data, thinking it might help my bright black screen problem. However, I found that I couldn't boot into recovery because all my phone would do was to give me that bright black screen again! So after many battery pulls, I managed to boot up my phone normally and do a factory reset under the backup & restore tab in settings. Of course, the phone tried to reboot itself, but of course, just gave me the bright black screen.
I kinda gave up at this point, and did many battery pulls and boots, however, all I got was either
1. the terrible bright black screen
or less frequently
2. the free xperia project logo then the terrible bright black screen.
I did get very fed up, so I plugged it into a wall socket to charge it. However, since about an hour or two ago, I realised it may be on bootloop. When I plug it into a wall socket, the free xperia project logo shows up and then an even brighter black screen shows up for about 3-5 minutes, then those two repeat endlessly. The notification light doesn't show that it's charging at all.
Okay here's background info on my phone.
- Is rooted
- Bootloader is unlocked
- CM 9.1 is installed
- Was running GO Launcher (if that helps)
- had a custom boot animation
- I think i deleted an apk for the google start up configuration thing...the one that asks if you have any google accounts you want to connect when you switch on your phone for the first time. I'll search up the correct apk name if you need it.
- Is about a year old (got it last early April)
- is a Sony Ericsson Xperia Ray (in case you didn't notice haha)
- battery level was about 20%+ when I did a factory reset (terrible of me I know)
- I have tried to caliberate the battery a few months ago
That's all the background info I can think you need. Please do let me know if you need any other info. If you need the logcat text of what happens when I hit the lock button at the top of my phone and the phone gives me the bright black screen (the early stages of this problem), let me know and I'll dig it up. I think I've bricked it, but I can't boot it into recovery so I can't do anything. And I did all I could google for the bright black screen problem which I won't tire you by specifying here. Please do help me. It seems as if the worst of evils has befallen my phone. Now I'm stuck here with my phone crazily on bootloop beside me. Please please do help.
Flash stock rom
Just try flashing a stock rom with Flashtool. If the problem persists, then it could be a hardware problem. Flashing a stock ftf takes care of all software issues. Get the stock ics FTF file and place it in firmwares folder of flashtool. Start flashtool and select flash mode. Then choose your ftf and press ok. Then wait until it prompts you to connect your phone. Then, just turn off your phone, while holding the power button down attach the USB cable. The LED notification should turn green and wait until it finishes flashing.
flash extended stock kernel and then the stock ftf firmware file...
hit thanks if i helped u
I have the same problem on my Xperia Mini (ST15i) I use Pureness rom and Mesa Kernel... ((
Benlux1 said:
I have the same problem on my Xperia Mini (ST15i) I use Pureness rom and Mesa Kernel... ((
Click to expand...
Click to collapse
Hi, if your phone can still be switched on and hasn't progressed so far in being destroyed, you could try downloading the Disable Auto Brightness app for Xperia phones from the Play Store. I've read somewhere that the screen might not turn on because of the auto brightness. I'm not sure if it actually helps, but perhaps my phone would have died faster without it. I've read of people changing their battery, doing battery calibrations or changing their screen to fix the problem. But before you change the hardware, I suggest that you check the hardware first. If the Disable Auto Brightness doesn't work, do a Nandroid backup and store the backup somewhere safe. Then flash the stock firmware to your phone and try to get it to switch on. Do flash the firmware before your phone runs out of battery because you never know, your phone may decide to refuse to charge your battery anytime. Then try to switch it on. If your phone goes into a bootloop (like mine now) really consider getting a new phone or sending it for repair or try all day to fix it if you use your phone alot. I'm still trying to fix mine.
I flashed the original firmware for my phone, tried to turn it on, was very happy when I saw the original Xperia logo, but then I realised it was on bootloop. When I tried to charge it, it immediately turns on and goes into bootloop again. Logcat doesn't detect my phone, so I can't obtain the logcat of what's happening. I haven't tried to replace the battery of my phone because I couldn't find a supplier. But I'll go on trying to fix my phone until the day that it really breaks down. Good luck with yours and keep us posted.
Sent from my MT25i using xda app-developers app
First off, using Velocity 1.2b18 on an old LG Ally. As the thread title says, it's based on (ancient by this point I guess) Android 2.2.2/Froyo.
Velocity comes with a modified lock screen font that has a square/robotic/futuristic/etc font chopped in for the numbers. Since it was about as far from matching my launcher clock font as it could possibly be, I figured I would simply switch Velocity's stock font for that of the launcher font. Others have apparently done this in the past, it seemed simple enough, so I figured...why not?
I used 7zip to grab the font from the apk it was in, dropped it into my SD card, and started the process. I did the following in Total Commander, while the phone was running; in hindsight I realize this was a terrible idea. Anyway, I copied the replacement font into the fonts folder, renamed it to Clocktopia.ttf, and renamed the old one Clocktopia.old. Then I exited and tried to lock the phone.
It tried to shut off and lock, came back up, then the screen shut off again. After that, whenever woken up, the key lights and backlight would come on, but it simply freezes on a black screen. Opening the physical keyboard (which would normally auto-unlock) does nothing, and it won't go back to sleep via the power button. Rebooting the phone, since it normally boots to the lock screen, has the same result.
"Ok," I thought, "so I'll simply remove the replacement font and re-rename the original and all will be well". And so, booting into recovery and accessing the phone from adb, I did just that. Rebooted the phone after this: same result as before. A bit of googling suggested clearing the cache when messing with fonts, so I cleared both caches and rebooted: same thing.
I've since made a nandroid of this apparently now borked android installation and restored a backup from the middle of the month (note to self: backup BEFORE screwing with things I don't fully understand next time), but my questions are...where did I go wrong? Was it that I performed the replacement while the phone was running? Why didn't restoring the original font reverse the effects, and is there any way to save the backup from its currently screwed-up state?
I used my phone this morning and it was fine. A few hours later I went to use it and it would not turn on. It is fully charged. I am running go launcher. I usually don't get asked which launcher I want to open it with when I wake my phone. But that screen flashed very quickly but I could not choose as the screen went blank very quickly. The screen was blank but the back button and the home button were lit up. I hit the power button so many times but nothing happens except the the 2 buttons lighting up. I went into recovery try to boot from there but nothing hapeens. It just goes to the HTC screen and hangs there. Its been on that screen for 10-15 and then I go back into recovery and still nothing. I tried to do a factory reset. It went to a screen with a picture of the phone and 2 green arrows going in a circle and a green down arrow inside the circle.
I have no idea what is going on. I have not done anything new to the phone. It is stock and I got Kit kat on it a few weeks back. Everything has been fine up until this morning. I understand the go launcher could cause a problem opening up the phone. But I don't understand why I cant do a factory reset from recovery. Any and all help is appreciated. Thanks
I also noticed that in the bootloader the very first line says 'LOCKED" is it supposed to say that?