Hi Guys
When I turn my phone on, after the Galaxy S first screen, the screen is multi-colored for about 1 second before going to the boot animation. Once the boot animation appears the screen is fine.
That's not a problem. What is a problem is booting into recovery, the top of the screen has a few blue lines. It still operates as if it is in recovery, as if I press the power button it reboots - but if I press down once, then power, it's not rebooting. So it looks like it's just the screen can't display what's being sent to it. So I can't do anything in Recovery like installing the auto-phone record, screen capture service or extended power menu. It will also be a problem if I come to install another ROM.
Does anyone know why? It started happening after I flashed a new ROM - I flashed the new ROM because the phone was constantly freezing when running certain apps (and needed the battery removed to restart the phone) - it's no longer freezing.
thanks
I'm not sure but,i think it because you don't have the good bootloader.For example,if you flash a rom from Froyo to gingerbread,you need to choose a rom with the gingerbread sbl(bootloader) include.
So to avoid this problem,just re-flash the entire rom with boot loader included.
Just go there http://forum.xda-developers.com/showthread.php?t=1102881
thanks I'll try that
Related
Need help/advice.
I flashed from stock rotos rom jme. I had problem with flashing. Things like windows not recognising tab in download mode. Several times failed flashing in midle of flash process. At the end I flashed succesfully. And things are working normaly. But when I switch off and then on. I get at&t logo and then black screen, i get sound from samsung logo but still black screen. Buttons on/off the backlight few times and still black screen. Then I press sleep then wake and i get straight the locking screen and all fine till next boot.
It looks like the boot part does not initialize the screen propely as its has a white line across when its black.
And in recovery i cant see what I am selecting.
Any ideas?
update:
sys73r pointed me to http://forum.xda-developers.com/showthread.php?t=899196. I will test that after I solve my unstable USB connection. As flasshing boot with usb problem smells like brick factory.
Sorry for bringing this again to top.
The fix was already posted.
used gingerbreak on g2. Got superuser and everything was great. Now (don't know why) no splash screen, no recovery even holding down volume and power on boot, random screen blackout. tried to re-gingerbreak with no effect. tried hard reset with no effect. stuck in hell please help. phone is stock rom and has no modifications even has all bloat-ware.
p.s. initial problem upon booting screen black but have lights at bottom after stock boot sound hit power twice and phone is active like normal. now stuck like this after each boot and couldn't find anything about the problem after searching. I hope this hasn't been covered before. Any thoughts? I am at my wits end about to get out the light saber and take out my frustrations on the mutt
If your phone is this: http://www.htc.com/us/products/t-mobile-g2/ then you're in the wrong place.
I have installed Cyanogenmod on my MT4G, it was working fine for few months, but now it is developing a strange problem with the display. The symptoms include:
The screen is pixelated when displaying text, and colors are distored (at first a reboot took care of the problem, but now the problem no longer goes away)
No display of the myTouch 4G splash screen
When boot into recovery, I can see the recovery menu VERY briefly, then the screen goes dark, completely black
When boot into bootloader, the screen is completely blank. Can not see anything.
I was thinking the problem may caused by Cyanogenmod, however, because now the screen is completely blank, I can not even restore to stock using the Power+Volume down method. I do know that it still entered bootloader mood since I can see the device using adb/fastboot command.
Any pointer as to what may have caused this or help getting me restored back to stock would be greatly appreciated.
Note, I have wipe the phone, I have tried Cyanogenmod 7.1, nightly build 252 and 7.2RC1, and the problem is still there. I was not able to flash a stock rom using rom manager.
Hello everybody.
I am a Defy Red Lense user with a recently flashed PA 2.14 build (coming from 2.00 version of same ROM). At first 3-4 boots everything was ok, till I made some changes on phone config (namely enabling 16 bit transparency as recommended by it's maker, and then some small changes in Paranoid Android Settings) and asked me to reboot. Ok so I went to reboot and as usual, it booted me into bootmenu, and I chose "boot" and "2ndinit" as usual. After a odd bootloop (where the phone wouldn't go through the blue, then green LED sequence and would then reboot, show Moto logo boot animation, rinse and repeat, etc) that I ended by pressing vol - and entering, again, into bootmenu, I chose again boot and 2ndinit and then something really weird happened:
After almost half an hour i'm still stuck at the very ROM booting animation (the Paranoid Android one, no the Moto logo), just like the guys that tried that new kernel that were reporting 15+ min first boot times. As a clarification, my first boot with just flashed 2.14 took, at most, 5 minutes. And there is another odd vehaviour, concerning the PA boot animation: it gets randomly stuck for a few secs and continues as usual, with no looping from 0 just like the normal loopboot.
So here comes the questions:
- What is really happening? is it really booting or the phone is just stuck in ROM bootanimation? How long should I wait to consider shutting it down?
- Is there some way to get out of it/shutting it down without damaging the device? Can I just pull the battery off without bricking the device?
Looking fowardd for some theories behind this issue :good:
Well, seems like it was OK to unmount the battery while on ROM booting animation, since I haven't had mayor problems after doing so and rebooting. Now the phone works just fine.
Tho im still curious the reason behind this pseudo-bootloop. Thanks for reading anyways :good:
Hi, I changed my screen resolution and all of a sudden the whole screen went black. I can still access recovery and I can still see the power menu when I leave power pressed and the screen responds to me clicking the button to restart etc. I can also flash through recovery. I dirty flashed a newer version of the ROM and I could see the system dialogue box telling me the system apps were updating, but from then it all went black. What should I do?
Fixed it by flashing an updated version of the same rom then flashing back to previous rom and then flashing back to the updated version.