so i flashed a custom kernel it was the nana's kernel but as i flashed it i rebooted my phone and it was showing the gingerdx splash screen i said "okay maybe a just little bug" but i checken what kernel is installed in phone information and it said linux dx v004 then i was like:"WTF? i just flashed nana's kernel and its linux dx on)
so what can happenned?
A classic case of "PEBCAK" (Problem Exists Between Computer And Keyboard)
You simply flashed the wrong kernel, that's all there is.
Related
When I change my stock rom 2.1 to gingerdx v19 I use CWM to do this. To start out with I have version 4.0.1.5 of CWM but after installing gdx it gives me version 3.2. So GDX override my original CWM version. Is this normal? Can I prevent this kind of downgrade? SO where is my newer version - does it get wiped over?
It usually happens. Since Ginger dx has a preinstalled cwm. Gdx must have lower version
.IV got cwm that is your CURRENT version (3.). Hope you understand more bout it now. (We were all noobs at one stage )
Sent from my X8 using XDA App
hey i have the same problem....i used naA kemel which quotes it has cwm 5.x.x but when i installeed gdx v20 it opens up with cwm 3.2.x
i am all ears as to how we can correct this situation
I hate to have my CWM downgraded for no good reason
First install gingerDX then flash the alfs kernel v05 it over rides the stock kernel with a new one and it is including CWM 5.x.x
Hope i helped
Sent from my X8
so what you are saying is install the one with latest CWM last so it will override the previous, which brings to yet another question - is it OK to flash the rom first before the kernel? So you are suggestion this sequence:
flash stock rom-> unlock bootloader -> flash gingerdx -> flash custom kernel
Precisely like that
Sent from my X8
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.
dears
i was using ICS RC2.1, and i used the glitch kernel, then i updated to rc4.1, but i nstalled Devil kernel, after installing it each time i go to recovery, all i can find clock work recovery mod not the new kernel, from settings, the installed kernel is:
3.1.10-galaxys+telus-257255-g0b9d335-dirty.
so how can i change it :S, even i tried to install many kernels, each time return to the original..
thank you
U have the devils kernel only. What's the issue??
nooo, i mean each time i install new kernel and reboot the recovery i cant find the new kernel , i only find the old sticky one...
Hi All,
I'm newly registered as I have problem in using HydraCoreNirvana Kernel.
I was using ZSLPN ICS Stock ROM with PhilZ-cwm6-ZSLPN-OZS-v2.7 Kernel.
A few days ago, I booted into CWM (Power + Up + Home) to flash MaxFu_HydraCoreNirana_n3_std.zip kernel.
HydraCore Kernel is working fine except that this kernel uses a lot of battery according to the
battery monitor. I keep using it for 3 days to make sure the whole system is stable after flashing a new kernel
but it is still consuming a lot of power.
Today, I boot into CWM (Power + Up + Home) to flash back the PhilZ-cwm6-ZSLPN-OZS-v2.7.zip kernel.
After flashing, I select reboot system, the "Galaxy Note N-7000" shows up and then black screen, i.e. without
the boot animation screen. I wait for a long time but still black screen. I tried to power up serveral times but same
thing happen. I then boot into CWM (Power + Up + Home), I can see PhilZ CWM so the PhilZ kernel should be flashed.
I then use this PhilZ CWM to flash Hydra kernel again and then reboot system. It can boot up.
I then try to boot into CWM to flash PhilZ kernel again, same problem. Now I flash back to MaxFU_HydraCoreNirana Kernel.
What's wrong with my procedures? Any idea? Now, I'm afraid to flash any other kernel as I am afraid I cannot flash
back to MaxFu Kernel and that will brick my phone.
Please help. Thank you so much.
I cannot post in Max_FU kernel thread as I am new here and not allowed to post there.
http://forum.xda-developers.com/showthread.php?t=2053084
Thanks.
It is happening because the latest Hydracore kernels have the new Mali drivers, which are incompatible with previous kernels. So, when you first flashed Hydracore, it also installed these new drivers; when you flash PhilZ kernel back, the new drivers are still there, so the kernel can't boot up. The solution is to install a "revert" package which will install and older Hydracore kernel (without the new Mali drivers), and also delete the installed drivers. Search the Hydracore thread for "Returning back to Hydra v5.3 std.zip". This is the file you should get and flash through CWM. After that, you can flash PhilZ kernel again.
To make it easy, download and flash returning back to hydra.zip 1st. After that you can flah philz kernel.. You can go to philz tread you kernel has been updated to v3.99
dbolivar said:
It is happening because the latest Hydracore kernels have the new Mali drivers, which are incompatible with previous kernels. So, when you first flashed Hydracore, it also installed these new drivers; when you flash PhilZ kernel back, the new drivers are still there, so the kernel can't boot up. The solution is to install a "revert" package which will install and older Hydracore kernel (without the new Mali drivers), and also delete the installed drivers. Search the Hydracore thread for "Returning back to Hydra v5.3 std.zip". This is the file you should get and flash through CWM. After that, you can flash PhilZ kernel again.
Click to expand...
Click to collapse
Thank you so much for the detailed description. I've not noticed that Mail drivers are being installed.
zai89 said:
To make it easy, download and flash returning back to hydra.zip 1st. After that you can flah philz kernel.. You can go to philz tread you kernel has been updated to v3.99
Click to expand...
Click to collapse
Hi zai89, thank you so much for your file. I flashed it and then I can flash back to PhilZ newest version.
By the way, I have used your file (v5.3 std kernel) for a while and it consumes the power normally. I still don't
understand why the HydraCoreNirvana drains huge power in my ROM (of course I am not complaining about
HydraCoreNirvana kernel, maybe my ROM problem). Since now I can flash back to PhilZ kernel, I may try
the v5.3 standard you suggested and see how good it is.
Once again, thank you very much for your time and kindly help.
I tried to flash all StrongAccord variants kernel and everytime i got SOD after i lock screen.I tried and Adagio-stable and Adagio-HV and same problem.But other kernel works fine.Is a kernel problem or why?I like this kernel and i really want to use on my OB.