Hello All,
I have been experiencing a very odd bug with a friend's gt540. The first occurred when I flashed the fastboot 2.1 rom. After flashing the rom it would boot and the screen would be all messed up. It's hard to explain, but basically there are static lines all over the screen with things misaligned and constant crazy flickering. You can still make your way through the menus though ever so slightly by pressing on the screen where the buttons are meant to be. Anyways, I freaked out but flashed a 2.2.2 aosp rom through fastboot and the issue went away and I naturally thought nothing of it.
More recently I decided to flash recovery through fastboot in order to flash newer roms and make nandroid backups, but after flashing swiftdroid and recovery, I found that the problem had returned. Not only is the screen all effed up on regular boot, but it is also messed up in recovery. It is by far the most bizarre things I've ever seen.
Swift droid, and oxygen, and pretty much all other gingerbread roms have given me this bug. I've flashed pretty much all of them through the buggy recovery. The only one's I've come across that have the screen working properly are Gingerbread Optimum 6.0 and his Froyo Optimum rom also.
My question is what the hell is going on? lol
At first I thought it was hardware, but if it was hardware why would some roms be fine and not others. Is there something that oxygen and swift have in common that might be the root of the problem? Has anyone experienced this on their phones before?
Maybe it's the kernel that certain roms are using?
I apologize for such a long question
Thanks a bunch for any help!
kweng_ca said:
Hello All,
I have been experiencing a very odd bug with a friend's gt540. The first occurred when I flashed the fastboot 2.1 rom. After flashing the rom it would boot and the screen would be all messed up. It's hard to explain, but basically there are static lines all over the screen with things misaligned and constant crazy flickering. You can still make your way through the menus though ever so slightly by pressing on the screen where the buttons are meant to be. Anyways, I freaked out but flashed a 2.2.2 aosp rom through fastboot and the issue went away and I naturally thought nothing of it.
More recently I decided to flash recovery through fastboot in order to flash newer roms and make nandroid backups, but after flashing swiftdroid and recovery, I found that the problem had returned. Not only is the screen all effed up on regular boot, but it is also messed up in recovery. It is by far the most bizarre things I've ever seen.
Swift droid, and oxygen, and pretty much all other gingerbread roms have given me this bug. I've flashed pretty much all of them through the buggy recovery. The only one's I've come across that have the screen working properly are Gingerbread Optimum 6.0 and his Froyo Optimum rom also.
My question is what the hell is going on? lol
At first I thought it was hardware, but if it was hardware why would some roms be fine and not others. Is there something that oxygen and swift have in common that might be the root of the problem? Has anyone experienced this on their phones before?
Maybe it's the kernel that certain roms are using?
I apologize for such a long question
Thanks a bunch for any help!
Click to expand...
Click to collapse
You can maybe download another fastboot ROM and try. It could've been corrupted. Can you please provide an image?
Related
Hey guys,
I just wanted to let all the devs know that my Evo has been rejecting any and all kernals that have been produced til now. I have full root access and nand fully unlocked. I have followed all neccessary steps to unlock EVERYTHING but still can't overclock the phone AT ALL. I just wanted to see if anyone else has been experiencing this weird phenomenon and if devs have recognized this as more than just an unusual problem with a handful of Evos. I would like to get feedback from any devs out there as far as what you've noticed and if/when this bug will get stompped!
Vipermuscle83 said:
Hey guys,
I just wanted to let all the devs know that my Evo has been rejecting any and all kernals that have been produced til now. I have full root access and nand fully unlocked. I have followed all neccessary steps to unlock EVERYTHING but still can't overclock the phone AT ALL. I just wanted to see if anyone else has been experiencing this weird phenomenon and if devs have recognized this as more than just an unusual problem with a handful of Evos. I would like to get feedback from any devs out there as far as what you've noticed and if/when this bug will get stompped!
Click to expand...
Click to collapse
well, at least say WHAT happens. boot loops? unresponsive? random reboots?
justinisyoung said:
well, at least say WHAT happens. boot loops? unresponsive? random reboots?
Click to expand...
Click to collapse
It freezes up on a force close screen once the bootanimation has finished. At least for me.
neckface said:
It freezes up on a force close screen once the bootanimation has finished. At least for me.
Click to expand...
Click to collapse
Are you doing wipes?
most of the time it will freeze once android has finally booted up. Then the phone tries to restart itself over and over again freezing at different points of the booting process. YES, I wipe, wipe, wipe. I'm not new to this stuff so I know it's nothing I'm doing wrong. Also, I have tried flashing the kernal only through recovery. I have tried immediately following flashing it's corresponding rom and I have tried flashing the kernal after the rom was installed already and rebooted successfully...same results.
Which kernel is being used and what its the hardware revision of you phone?
Hardware version 0003 and I've tried the 1.114 kernal and the 1.2...which seem to be the only ones out there at the moment. Both don't work.
Vipermuscle83 said:
Hardware version 0003 and I've tried the 1.114 kernal and the 1.2...which seem to be the only ones out there at the moment. Both don't work.
Click to expand...
Click to collapse
HW 0003 doesn't work with custom kernels yet. Check the overclock kernel thread, it's posted there.
Hello,
I recently had my HD2 setup with MAGLDR 1.11 and a stock DHD ROM, however this froze constantly and seemed to get worse over time, as well as all together failing to boot sometimes.
So I updated MAGLDR to 1.13 found a nice rom "Typhoon CM7" I believe, downloaded the radio it sugested and flashed it, downloaded CWM and flashed it, and then flashed the ROM from SD using CWM.
Sadly however this has not fixed my freezes/failures to boot, im starting to think it might be hardware related.
So what I am asking is does somebody have a ROM that is working really well for them that they could sugest to me?
Thanks,
Alex.
everyone has different opinions, do you want a version with or without sense?
personally i like sense so am using imilkas ram hd version ,its fast and very stable
Well i usually tend to go for ROMs without sense, but i am pretty impartial to it.
alexhope21 said:
Well i usually tend to go for ROMs without sense, but i am pretty impartial to it.
Click to expand...
Click to collapse
Which ROMs have you tried already, and what was wrong with them?
I have tried one of the many DHD stock ROMs and Typhoon CM7, as well as Raphroid and Ultradroid.
I frequently get a freeze at "GO GO GO" in MAGLDR 1.13, and then once the ROM does eventually succeed to boot, it often locks up.
Some ROMs seemed to do better then others overall however, Typhoon CM7, successfully booted most frequently.
In all cases I have used recommended radio's.
However the greatest hassle has been flashing them as I can only get CWM to boot 1 out of 20 times after multiple reflashings, it often gives me an error stating "FATALHIT 1".
Does everyone get behaviour like this?
Hmm.
That's Weird I Have Tried Lots of these roms and they all seem stable and fast on my hd2
crabtreebrandon29 said:
That's Weird I Have Tried Lots of these roms and they all seem stable and fast on my hd2
Click to expand...
Click to collapse
Could you please give me some specific information of what version of MAGLDR, CWM you were using, as well as a link to the Radio and ROM?
Im starting to think my hardware might be bunged.
Thanks,
Alex.
i am too having a lot of problems when booting up from maglrd. It freezes or gets hit fatal error. Do anyone know a good stable rom that doesn't freeze when booting up,and has great battery life?
thi713 said:
i am too having a lot of problems when booting up from maglrd. It freezes or gets hit fatal error. Do anyone know a good stable rom that doesn't freeze when booting up,and has great battery life?
Click to expand...
Click to collapse
All of them. End of story. This is due to user error. Not build related
alexhope21 said:
I have tried one of the many DHD stock ROMs and Typhoon CM7, as well as Raphroid and Ultradroid.
I frequently get a freeze at "GO GO GO" in MAGLDR 1.13, and then once the ROM does eventually succeed to boot, it often locks up.
Some ROMs seemed to do better then others overall however, Typhoon CM7, successfully booted most frequently.
In all cases I have used recommended radio's.
However the greatest hassle has been flashing them as I can only get CWM to boot 1 out of 20 times after multiple reflashings, it often gives me an error stating "FATALHIT 1".
Does everyone get behaviour like this?
Click to expand...
Click to collapse
i assume you are changing the CWR partition each time you change from a dhd rom to a non sense/GB rom ?
Richy99 said:
i assume you are changing the CWR partition each time you change from a dhd rom to a non sense/GB rom ?
Click to expand...
Click to collapse
Yeah, Im starting to think my hardware is damaged, I used to use the SD RAM rom that Dark Forces released, and I guess it did not benifit my device, as it would frequently get quite hot after 20min of straight use.
How does this ROM run with the 2.15.50.14 radio?
If it is also laggy and has bugs, then I think your phone might be broken.
For me all roms using SD-EXT are laggy as hell and i personally stopped testing those roms as I'm already used to the smoothness of Gingerbread... I'm searching almost everyday though these topics to find somebody who says "This is a really smooth Sense rom!". But never seen a comment like that.
Well I have had my Xoom now for about a month. I use it pretty heavily and as soon as I got it I rooted it and installed Tiamats v1.4.4 kernel with OC'd GPU. I was running pretty flawless OC'd to 1.5Ghz until last night. I was in the middle of reading some posts on here on tapatalk and out of the blue the screen went black and rebooted. It was stuck on the spash screen for 20 minutes. I tried a hard boot and got bootloops.
I then downloaded the stock images and reflashed it back to stock and even relocked the bootloader. Still bootloops. I ended up flashing the stock images like 3 times in all with the same results. Sometimes I can get into the OS and go through setup and sometimes not. Most of the time if I can get into android apps start force closing and it reboots, or the touchscreen becomes unresponsive. I noticed most of the time when rebooting I get bright white flashes of light on the splash screen. Here is a video of the boot sequence:
http://www.youtube.com/watch?v=1ctODeIPANU&feature=player_profilepage
Around 1 minute into the video you can see the white flashes of light. Anyone know if there is any chance of recovering this? BTW, its a verizon 3g xoom. I'm pretty sure its a brick. I just wanted to see if anyone else had seen this same thing happen.
EDIT: I also noticed that sometimes the front camera is flashing red also when rebooting. Weird.
Had you updated any apps like superuser or busybox installer? Were you able to do a nandroid recovery through CMR? What stock files did you flash (what version?) I'll bet you are not completely bricked...there seems to be a fix for almost every crash. It's just that without knowing anything about why it may have crashed or exactly what you did afterwards it hard to know how to help.
okantomi said:
Had you updated any apps like superuser or busybox installer? Were you able to do a nandroid recovery through CMR? What stock files did you flash (what version?) I'll bet you are not completely bricked...there seems to be a fix for almost every crash. It's just that without knowing anything about why it may have crashed or exactly what you did afterwards it hard to know how to help.
Click to expand...
Click to collapse
I didn't update anything at all. I tried my stock nandroid and it locked up too. I tried flashing both factory images for the VZW xoom from motorolas website and they both do the same thing. I've never seen it lock up so much and the screen become unresponsive like it is. Restoring it to factory should fix it and after 3 times of flashing the stock images it should be fine, but its not. The stock files I tried were MZ600_HRI39 and MZ600_HRI66. I'm not sure what else to even try. The flashing white screen and the camera flashing red are definitely not a good sign.
sabbotage said:
I didn't update anything at all. I tried my stock nandroid and it locked up too. I tried flashing both factory images for the VZW xoom from motorolas website and they both do the same thing. I've never seen it lock up so much and the screen become unresponsive like it is. Restoring it to factory should fix it and after 3 times of flashing the stock images it should be fine, but its not. The stock files I tried were MZ600_HRI39 and MZ600_HRI66. I'm not sure what else to even try. The flashing white screen and the camera flashing red are definitely not a good sign.
Click to expand...
Click to collapse
Wow, maybe you have a hardware failure. Did it act funky before at all? I saw that it just bootloops by itself...can you still get it into any kind of recovery? I think that if you can get into fastboot and use adb, you can do a wipe and maybe start over. Of course it you have a hardware fail that's another issue.
okantomi said:
Wow, maybe you have a hardware failure. Did it act funky before at all? I saw that it just bootloops by itself...can you still get it into any kind of recovery? I think that if you can get into fastboot and use adb, you can do a wipe and maybe start over. Of course it you have a hardware fail that's another issue.
Click to expand...
Click to collapse
Yeah i can get into fastboot and I tried erasing everything before reflashing the stock images with no luck.
Sent from my HTC Thunderbolt using Tapatalk
sabbotage said:
Yeah i can get into fastboot and I tried erasing everything before reflashing the stock images with no luck.
Sent from my HTC Thunderbolt using Tapatalk
Click to expand...
Click to collapse
If you can go to the IRC Xoom Channel you could chat with people who know much more than I do. I think with your weird light flashes and continuous boot cycle, that might be your best bet. The address is in brd's signature line.
I sincerely wish you good luck!
okantomi said:
If you can go to the IRC Xoom Channel you could chat with people who know much more than I do. I think with your weird light flashes and continuous boot cycle, that might be your best bet. The address is in brd's signature line.
I sincerely wish you good luck!
Click to expand...
Click to collapse
Thanks I jumped on there and i'll see what everyone says. I've tried it all and nothing is working.
I seem to have encountered a rather unusual issue with my nandroid back up. I was planning on flashing CM7 to test it out, and then after my test return to my backup. CM7 worked like a charm, but I was going to wait until I had more time on my hands to fully explore the rom, so I decided to do a nandroid restore using Clockwork Mod 3.0.2.4. It worked... sort of. After the restore, I rebooted. It brought me to my normal unlock screen, but when I unlocked it, I was presented with the MT4G initial setup, as if I had done a restore with the stock img. I knew my data is still in there, because it remembered little things, like my initial lock screen, my wifi settings and a couple of other things. I went hunting through a couple of forums, and found that the MT4G has issues when using clockwork 3.0.2.4 to flash non-Gingerbread, and that you ought to use clockwork 2.5.1.2. Thinking that may have been my problem, I tried, and it then told me there was a MD5 mismatch. I followed the recommendations found in this post http://forum.xda-developers.com/showthread.php?t=976453 for finding and correcting mismatched MD5s (the data.img file was the one with the mismatch if that helps). Now it flashed properly, but resulted in the same problem I had earlier... after reboot, I am presented with my lock screen, but then taken through the MT4G setup. I have a TI backup, so I'm not really worried, but, I am curious if anyone can shed some light on what happened to my restore so that it doesn't happen in the future, and so that if someone else has this problem, they can have it a little easier than I have.
Thanks in advance for your help,
WestBC
Any thoughts!
Basically, stick with froyo or GB. Don't jump back and fourth.
So i have the I337m, canadian model S4 on Bell Mobility network, and I"m running SlimRoms with 2.5.0.2 twrp recovery.
Every other reboot, the phone gets stuck on the splash screen, I have no problem to go into recovery mode or anything, this is simply a problem when rebooting and gets stuck on the "Galaxy S4" screen. Here's what I've tried, tried both with TWRP and CWM and TWRP seems better, I don't get stuck on the splash screen as often as CWM. I've reverted back to the "stock ROM" and rerooted and loaded the TWRP recovery, and while it seems better at first, it slowly gets stuck more and more at the splash screen.
I'm running out of ideas, no knowing what do to to improve this problem...
Anyone else having this problem? I'm positive this is not a "ROM" related problem but a recovery problem, yet maybe it's just my phone that's being the problem.
JP
I'll also add that I've never formated data on TWRP... since I've read it gives that problem.
jproy12 said:
I'll also add that I've never formated data on TWRP... since I've read it gives that problem.
Click to expand...
Click to collapse
You have to do a factory reset, wipe data, or you will get a boot loop. Do that and I'm sure you'll get past the boot loop. If you're concerned about the version of twrp you're on, update it.
http://forum.xda-developers.com/showthread.php?p=41010145
jd1639 said:
You have to do a factory reset, wipe data, or you will get a boot loop. Do that and I'm sure you'll get past the boot loop. If you're concerned about the version of twrp you're on, update it.
http://forum.xda-developers.com/showthread.php?p=41010145
Click to expand...
Click to collapse
I'm not getting boot loops actually, I get stuck on the "splash screen" and when I hold the "power" button for +/-10sec it reboots and most of the time it's fine.
When I install any roms, I always do a factory reset... So I doubt it's that
i had the same issue. im running the same s4 on koodo/telus. how i got it to work took a while but it fixed the problem. full back up through recovery but i wasnt gona use it..i only had it for safety. used titanium to back up all the apks. then grabbed a stock rom from the Canadian stock roms page and used odin to flash it. rooted and added recovery (twrp). downloaded my rom to the sd, wiped everything and installed the rom. once done then used titanium to restore the apks. im still learning the basics to all this so in no way am i an expert and theres probably a better way around all this but this is what worked for me. maybe it helps who who knows
h_khan said:
i had the same issue. im running the same s4 on koodo/telus. how i got it to work took a while but it fixed the problem. full back up through recovery but i wasnt gona use it..i only had it for safety. used titanium to back up all the apks. then grabbed a stock rom from the Canadian stock roms page and used odin to flash it. rooted and added recovery (twrp). downloaded my rom to the sd, wiped everything and installed the rom. once done then used titanium to restore the apks. im still learning the basics to all this so in no way am i an expert and theres probably a better way around all this but this is what worked for me. maybe it helps who who knows
Click to expand...
Click to collapse
Yea, I had done this before, but I'm giving it another shot tonight to see if it'll fix my problem for good...
Still having the same problem... Running out of ideas
jproy12 said:
Still having the same problem... Running out of ideas
Click to expand...
Click to collapse
I was having a similar problem to your's. I found the cause of my issue. It was TWRP 2.6.0.0. More specifically, it was using TWRP 2.6 to format my /data partition. After doing some trouble shooting, I found that my /data partition was the cause of my S4 hanging at the S4 splash screen. Like you, I was able to get into Android on the first boot, but if I tried to reboot, I was get stuck at the splash screen. So, long story short (solution), I restored one of my nandroid backups, got into Google Play, downloaded ROM Manager and installed CWM. I used CWM to format my /data partition and ONLY my /data partition. Once I did this, I rebooted my phone. Android loaded, I had to go through the initial setup process since I formatted the /data partition, but after this, I was able to reboot my phone 5 times in a row without issue and shut down twice with no problems booting back up.
Here is my thread: http://forum.xda-developers.com/showthread.php?p=45448596#post45448596
There's a bit of reading. Hope this helps.
So my issue was caused by TWRP 2.6.0.0 and using it to format my /data partition.
jproy12 said:
Still having the same problem... Running out of ideas
Click to expand...
Click to collapse
i think the rom is the cause of this issue. i myself am running goldeneye rom which is the best rom ive used so far...perfectly balanced performance and battery life. id definitely recommend it.
Talabis said:
I was having a similar problem to your's. I found the cause of my issue. It was TWRP 2.6.0.0. More specifically, it was using TWRP 2.6 to format my /data partition. After doing some trouble shooting, I found that my /data partition was the cause of my S4 hanging at the S4 splash screen. Like you, I was able to get into Android on the first boot, but if I tried to reboot, I was get stuck at the splash screen. So, long story short (solution), I restored one of my nandroid backups, got into Google Play, downloaded ROM Manager and installed CWM. I used CWM to format my /data partition and ONLY my /data partition. Once I did this, I rebooted my phone. Android loaded, I had to go through the initial setup process since I formatted the /data partition, but after this, I was able to reboot my phone 5 times in a row without issue and shut down twice with no problems booting back up.
Here is my thread: http://forum.xda-developers.com/showthread.php?p=45448596#post45448596
There's a bit of reading. Hope this helps.
So my issue was caused by TWRP 2.6.0.0 and using it to format my /data partition.
Click to expand...
Click to collapse
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "boot screen"?
h_khan said:
i think the rom is the cause of this issue. i myself am running goldeneye rom which is the best rom ive used so far...perfectly balanced performance and battery life. id definitely recommend it.
Click to expand...
Click to collapse
I've been running Slim for a year now, and won't go back to anything else, it's stable and fast, I doubt it's a ROM problem, but a recovery problem.
i think you're right. a problem with the recovery makes more sense.
jproy12 said:
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "boot screen"?
Click to expand...
Click to collapse
So it seems like this wasn't exactly my problem... I've reverted back to stock and I'm doing a couple shutdowns and reboot and see if I still get stuck at the splash screen.
I've been doing reboots and shutdowns on the "stock" rom and "stock" recovery, and all is good, so I can rule out the fact that it's the phone and it's hardware issues...
Now, just need to figure out the actual problem
jproy12 said:
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "booscreen"?
Click to expand...
Click to collapse
So far so good. I rebooted many times since I made the post in this thread. Haven't got stuck on the splash screen yet.
I'm still having the problem, being on either the TWRP, CWM or Philz recovery, so I'm really not sure what it could be. I'm on the latest modem and still have the problem, is none else having these issues?
I'm getting annoyed and really want to get this fixed.
I think any ROM built on AOSP or CyanogenMod have this issue. It's already a known issue to CM.
Use CWM and you'll have to deal with it less.
emckai said:
I think any ROM built on AOSP or CyanogenMod have this issue. It's already a known issue to CM.
Use CWM and you'll have to deal with it less.
Click to expand...
Click to collapse
I've never seen anyone really mentionning this for the Galaxy S4 from my numerous searches...
jproy12 said:
I've never seen anyone really mentionning this for the Galaxy S4...
Click to expand...
Click to collapse
If you look in the cyanogenmod thread, it's located in the known bug (post #2)
Any custom roms built on top of CM10 will probably have this issue.
emckai said:
If you look in the cyanogenmod thread, it's located in the known bug (post #2)
Any custom roms built on top of CM10 will probably have this issue.
Click to expand...
Click to collapse
You are right! I guess it's one of those bugs, just never noticed anyone really mentioning anything about it
jproy12 said:
You are right! I guess it's one of those bugs, just never noticed anyone really mentioning anything about it
Click to expand...
Click to collapse
Yeah, but I don't think its a big deal anyway. How many times do you turn off your phone and turn it back on in a day?