A few days ago, I flashed Sony's new bootloader to see if flashing AOSP 5.1 over it would work (it did, but that's aside the point). At first I thought that the new bootloader didn't work for some reason. But I then realized that it did indeed work, but there was no more Sony logo when I start up my E3. It just hangs there for a few seconds as if nothing happened, then the screen turns on and displays black for another few seconds, and finally the boot animation comes up. Does this happen to others? Or only to me? Not that I really mind anyways, but is there a fix to this? I am trying this on the D2203 model.
Related
Hi,
I recently rooted my htc vivid and i tried to flash a rom. However, the rom didnt work and my phone isnt working. The phone's bottom touch-buttons vibrate when touched, but the screen remains off no matter what i do. What's wrong with it?
EDIT: I got it to boot, however, its stuck on booting, the boot logo just keeps on popping up. What should I do?
any luck?
sounds like you need to try and flash the rom again. this may or may not be a know issue with the rom. check the thread where you got the rom. I had to flash twice with the same rom the last time i did it (unrelated device)
May have to hold the buttons in a specific sequence to get back to the debug mode.
also have a look through this thread:
http://forum.xda-developers.com/showthread.php?t=1433149&page=2
Hi all, I have a weird issue that every time I flash a ROM on my phone I get stuck on the bootloader screen after I restart for about 5-10 minutes until my screen turns off, then after the screen is off im able to wake it and use it regularly. I have this issue with almost every ROM I have tried. I used the RUU to restore my phone about a week ago if that matters. My phone is S-OFF and pre-rooted. Does anyone else have this issue or know what is wrong?
I think i found my issue im updating my firmware to the lastest see if that works..
Yea sounds like you r not on the newest firmware out.
Hello guys,
some days ago my phone was permantly booting up in the recovery mode nothing else was possible. As I was on road and couldn't access internet anywhere I just tried to do some wipes, which then made my phone not show anything. I guess the reason that it didn't boot up anymore was that the battery was fully drained. When I was finally back home I was able to charge my phone but then the following happend:
I can start my OPO, see the android logo and then it turns black, but it fully boots up. I mean I can even click the touchscreen and hear some touch reactions/sounds. Also I'm able to turn up/down the volume and hear my phone. Furthermore I'm also able to do the "V-gesture" to turn on the flashlight. When I boot up into fastboot mode I also see the message "fastboot mode" + the little cyanogen face.
All in all everything seems to work, aside that I dont see anything else than dark after the logo.
I tried flashing new roms, stock reset, like seriously anything, but I can't get my phone to work probably again.
Does that mean that my phone got some hardware problems, maybe the touchscreen?
Help is appreciated, thanks in advance!
btw: English isn't my first language, so please excuse any mistakes.
You'll have to try flashing completely stock CM11 rom or CM12 rom, img by img in fastboot..modem, boot, system etc. I helped a friend who had this kind of problem. Probably not the cleanest way, but at least it works.
Already did that 3times using different methods. Stock CM11, CM12 and colorOS
I have a similar problem, did you manage to fix it? And if so, how?
Thanks,
Capelare.
My xperia p is rooted and bootloader is unlocked. I tried honami moon walker and didnt like it. So restored it to my old back I took using CWM recovery backup.
I dont know if it got restored properly. I mean I was in honami moon walker and just restored the old backup which is jellybean os. Was it the way to do?
And then I tried to unlock the bootloader to try more roms like cyanogen. but the phone doesnt stay in fastboot mode or the violet light goes faster before I point to the customized interface file in my system. When I pointed, it told "windows was able to find the driver but unable to install it". Cannot find the file specified. I used an application quick boot(Reboot) to get into fastboot mode which was easy. But all in vain. In the process of getting into fastboot mode, I never got out. The screen will be blank.
Then I will try restarting by pressing the power and volume up buttons together and restoring to the old back up I took already.
Now whenever I restart my phone, it gets stuck with the sony logo and it keep restarting. Before trying the power plus volume up combination, it may stay in a blank screen with 2 pixel sized blinks on the two sides of the bottom screen.
So now I am afraid to restart my phone itself. Because it never restarts the phone but gets stuck with the sony logo and then I have to restore it to the old back up.
What should I do? I want to keep my phone rooted and unlock the bootloader and try new roms.
I've had some previous experience with custom roms on my old Nexus 6P and thought I would try the same for my mate 9. Unfortunately I've discovered the Mate 9 is not as easy to install custom roms as I thought.
I've tried several things throughout the day and I feel I've accidently overwritten things I shouldn't have but can't remember everything I've done.
It is an Optus branded phone so I believe at the start of the day I had some version of L09C34. I currently have an unlocked boot loader and TWRP installed and would like to flash back to the stock firmware, but seem to be unable to do so. The boot loader is unlocked and when I try flashing extracted parts from fastboot, the phone will reboot, reboot again and sit at erecovery. Unfortunately while I can connect to wifi, no packages are found for recovery.
Additionally I now get this lovely colourful screen in lieu of the logo on initial boot.
Any help would be appreciated.
Okay, so I've managed to unbrick it and install a version of L09C432 and get it working again - thank you to various threads on XDA. I think what I noticed was that someone else had tried the C432 firmware on a C33 model and it worked. Without being able to get hold of the C34 firmware, I tried to flash nougat originally and it worked.
This morning, I've noticed I still have an issue where the touchscreen won't work when the phone is cold (i.e I can't click anything and can't turn alarms off). If I reboot the phone to recovery it's fine, so it leads me to believe its an OS thing. Also, if I give it a few minutes in my pocket, or holding my palm on the screen it then responds. This is the issue I tried to resolve by resetting and trying a different rom but seems I haven't been successful.
Finally, when I first turn the phone on and the screen lights up I see a green background with one blue and one red box. Any ideas what I have messed up there and how to fix it? I'm not too concerned, but it would be a nicety.
Just providing updates in case anyone comes a long with similar issues.
I have now fixed the strange coloured screen on initial power on. I've found the oeminfo for the C432 firmware on another XDA thread and took a backup of what was currently there, restored the C432 version and rebooted. I was presented with the eRecovery and no TWRP. Quick check in fastboot mode showed the phone relocked. I unlocked it again and it booted no issues, however was unsure if the custom rom was still installed as I was presented with the option of an OTA update. Initially my sim card was not recognised, so I had to remove and reinstall it but so far so good.
I've just reflashed my custom rom and will see how I go.
The only potential issue I have outstanding is my touchscreen not working either first thing in the morning, or when the phone is cold - i.e I've gone to the gym and left it sitting in the locker for 2 hours and I can't use the touchscreen when I come back. I can unlock it fine with the finger print reader and the phsyical buttons respond but touches on the screen won't. If the phone is left alone for a few minutes the screen shuts off and turns back on approx every 5 seconds until it becomes responsive. Has anyone seen anything like this before? My googling hasn't lead me to anything helpful.