After installing GalaxyROM_v14 I have weird display during boot after custom FW install
See picture.
Any idea?
I think it's sometimes caused by the custom kernel. I've seen similar behavior during boot on some custom kernels. If everything works otherwise, it's nothing to worry about.
I get something similar when booting into recovery with DamianGTO's kernal.
Sent from my GT - I9000M running Tornado JVR Gold with Tornado kernel.
I also get this when i try and open some apps/games but then it runs normally afterwards
That would normally be associated with a voodoo kernal.
Related
Hi guys,
my problem is that whatever i flash it ends up with reboots.
I have flashed a gingerbread bootloader and then deoxed rom JVQ and finally semaphore Kernel to get CWM(with odin).
Then I have tried Darkys rom but anytime i reboot it reboots again-twice or it reboots when im in the app drawer.
Juwes rom-sometime it reboots itself. SYMPLY rom-after closing voodo control app it hangs and reboot and the same thing happens with control freak or it just reboots when your sliding through the menu.
I dont get it what iam doing wrong why i have this ****ing reboots.
I hope someone can help
selami023
Some ROMs have bugs that cause reboots. Sometimes it might be cause by modem or kernel incompatibilities.
The safest option would probably be to find a ROM you like the look of (with detailed installation instructions) and do a completely clean install of it (factory reset/format SD->Odin flash stock Firmware -> Follow ROM instructions). Or just stick with the stock firmware. Avoid using TitaniumBackup to restore apps to be really safe.
thx dude for your answer now i have miui galnet and everything works fine except that it restarts when i press shut down(but only while charging).
But i really dont get it why there are so much bugs. I have also a htc desire hd and i can overclock it to 1,6 ghz and its still stable almost with all custom roms that are available for the desire hd.
selami023
I tried to install the illuminance Rom last night, and it kept getting stuck at the ATT logo. I reflashed back to stock did a master clear, flashed a stock 2.3.5 uckj3 gingerbread Rom with corn kernel v307 also ATT gingerbread boot loaders. I used CWM to install the ROM, it'll restart then get stuck and get stuck at the ATT logo....is there something I'm missing? I've installed other ROM and have had no issues until now?!?!
If you used Corn kernel, are you sure you where on RFS format and not ex4?
it was rfs format before I tried to install
Did you make the file (don't remember exactly wich) that disable Voodoo. There is no reason for it to bootloop. After you flashed stock did you let it boot up? Maybe try with Boog kernel to flash then flash wich ever kernel you want to use?
I'll try the boog kernel.....I also ensured that the lagfix for system and data was disabled through CWM recovery ....in the install instructions it stated that it would take awhile to boot, I let it set for two hours. One thing I noticed is that 150 jpegs were installed
Sent from my SAMSUNG-SGH-I897 using xda premium
Doubt this might be it but, If you set it on CWM to disable lag fix reboot in cwm then flash. Random thought.
LOL....did that also.
Sent from my SAMSUNG-SGH-I897 using xda premium
Guess I'll start over clean again....
SGH-I897 Cappy
I897UCKJ3 2.3.5 Gingerbread
Corn kernel UCKJ3 V307
FASTY III V1 KJ3
Tegrak OC Ultimate
lilbigdude1 said:
Guess I'll start over clean again....
SGH-I897 Cappy
I897UCKJ3 2.3.5 Gingerbread
Corn kernel UCKJ3 V307
FASTY III V1 KJ3
Tegrak OC Ultimate
Click to expand...
Click to collapse
My boot getting stuck got fixed after Wipe data/factory reset in CWm, wipe cache, wipe Dalvik cache, - all three -then install illuminance. Tried that ? Starting from stock KJ3 no bootloaders.
Importantly: Can you boot with just Illuminance boog kernel (the one that comes wiht the ROM, no other kernel flashed)? I presume you cannot boot a fresh Illuminance install............if this is the case wiping as above should help.
I finally got illuminance to install, and is working great.
this may seem like over kill but everytime I flash a new ROM I start from scratch and flash to stock and master clear and then build from therethis is the first time that I ever had any issues by doing it this way. usually I have it setup up in 10 to 15 minutes it seems to save any issues later down the road as far as being buggy.
Glad to hear it
Hi, I tried to install Illuminance 1.1, but I think the file is corrupted. I downloaded it twice, from different locations, and its the same zip file.
I tried to decompress it before installing it, just to check file consistency, but lots of files can´t be decompressed.
Anyone had this problem? If not, any way /any where to safely download it?
Thanks!
In the Illuminance Rom Thread, in the OP, there is a link to IlluminatedOne's website, where u can find a good non-corrupted download and u will also find the installation instructions.
Not sure why u think u had a corrupted download ?? But u should b good to go once u get to the website.
As of this version 1.1 release, u should only be downloading the Illuminance Rom from said website.
Sent from i897uckj3
I downloaded my version from Mega-upload. I tried it again last night just for...you know....and received the same results of being stuck on the att logo for hours. as usual i flashed to stock and master cleared, GB boot loaders, reinstalled stock 2.3.5 and reinstalled luminance and before i rebooted i installed the samurai kernel, then rebooted and everything worked as normal....so being fairly new to the whole Dev scene i don't know why that would make a difference, but it works fine and it didn't get stuck on the att logo.
oh and thanks twin I'll try and go to the website and check it out
have been running my captivate on CM7 with Glitch v13 for a while, and having a lot of force close, and sometimes lockups, so decided to try the new Fasty III KK4 rom, the rom is supposed to have Corn kernel built in.
Well everytime I try to flash the zip in CWM, it says successfully installed please reboot, I reboot and it still show the Glitch boot images, and just sits at that screen for 10+ minutes.
I tried flashing just Corn kernel v7.06, says it finished, still reboots with Glitch logo.
I formatted data and cache, tried factory resets, cleared kernel, cleared dalvik, but it still seems the same everytime.
I was able to successfully flash the Glitch v13.1 update, and re-flash CM7, but I still cant seem to flash any other rom or kernel - any ideas?
CM Roms use a different file system than Samsung based roms (Fasty, Legend, Saurom, etc).
You will need to flash back to a stock image so that it will repartition your device back to the Samsung format. After that you can Odin/Heimdall/CWM flash to your new ROM.
thanks -I had a feeling it was something like that.
Hi all,
I'm running CM7 on my i9001 and tried to experiment with different kernels. Everytime I try to flash a new kernel, however, the phone won't boot up anymore and I have to recover. I tried vitality, skyhigh and cranium using both CM recovery and quick flasher.
Is CM7 possibly incompatible with other kernels? I'd very much like to try overclocking and undervolting but set cpu doesn't allow me to do that.
Thanks,
Marsi
No idea anyone?
Hello!
I've been having a lot of trouble flashing recovery, rooting and installing custom rom for my Mini 2. After a lot of researching and trying I have successfully rooted and after installed Cyanogenmod 10.1 and now I got the JellyBean 4.2.2. And now I would like to find out whether or not I should upgrade/change the kernel. Can anyone tell me please if there is another kernel for CM10.1 and for my device specifically, and will it make my phone more faster or not. I have tried to install Semaphor (I don't think this is compatible with my device), Devil (Same here) and Franco (Which is same) for all three of them I have got the status 7 error. I have also tried to install some kind of kernel update for my device which completely messed up everything (different colored display, some glitchy stuff and random reboot every 0.5 seconds ), so I had to install the stock rom (because the cm didn't work) and then the cm.10.1 again (now I'm good). Also to let you know my current kernel version is 2.6.38.6-1214151 (that's what says settings -> about phone -> kernel version). If there is nothing better then don't worry, my phone at the moment runs smoothly anyways!!!
Thanks in advance.....
Please...
Anyone???
I had that error on cwm 6.xxx
Then i flashed cwm 5.0.2.8 and there was no error, it worked
Just wipe everything and go to mounts and storage->format /system and after that mount /system
Make sure you have backup of your working rom. If your device wont boot after flashing (if its just booting in recovery, flash stock rom
(get into downlad mode voldown+home+power, hold power button until samsung logo.)
If thats what you have problem with...
No, don't install something that won't work for your phone. Kernel are main controllers in your phone. You change the kernel, you change how your phone works. If you lucky, you get your phone booting, but with glitch everywhere. If you aren't lucky your phone will dead, no matter if you install a custom ROM, or a fresh stock ROM.
THX
F4uzan said:
No, don't install something that won't work for your phone. Kernel are main controllers in your phone. You change the kernel, you change how your phone works. If you lucky, you get your phone booting, but with glitch everywhere. If you aren't lucky your phone will dead, no matter if you install a custom ROM, or a fresh stock ROM.
Click to expand...
Click to collapse
I appreciate the reply, so as far as I understand, Kernel is completely separated from the ROM. So if I get any error or problem with the Kernel, it's going to be hard to fix, because re-flashing the ROM will not change anything. If what you said is right then I will not risk it, because my phone has got already CM10.1 installed and is working nice and smoothly, however I got another question. I'm not sure what Kernel version I had previously but when I installed CM I think it changed the Kernel, because the name of it is not the same as I've seen when I had stock ROM (It says 2.6.38.6-1214151 [email protected]#1 Sat Mar 23 11:49:35 EET 2013). I am really happy with what I've got at the moment so I will not change it, because if my phone ends up bricking, or anything else, I can't afford to buy another one for now (sometime later yeah )
Anyways thanks for your help!!