I have installed merruk kernel through odin on my galaxy y which has Chobits digitalis v2 and it started behaving oddly
1) FC's
2) Sudden reboots
3) Bootanimation is changing colurs from cyan to red
4) Overheating
5) Very poor performance
I went back to stock rom and kernel for time being but I want to know why it happened that way?
Please help
Thanks in advance
1) What superuser app you had? SuperSU gives FCs with merruk
2) Wierd. Merruk is pretty much stable. Much be some problem in your end.
3) Thats chobits random boot animation script lol. Its intended to change
4) Same as 2nd answer
5) Its the best performance kernel out there. You mustve done something wrong.
To debug your problem, can you describe more about the issues?
Thanks I understood the problem now I flashed ext4.zip when it wasn't required and I had SuperSU
Related
I am on stock ICS LPA Rom with GL_NOTECORE Kernel (Safe Kernel). Everything was fine for a week with this combo. Today morning i noticed that the phone was not going in to deep sleep and so tried the old trick (Airplane mode, battery remove restart) and BHOMM my phone is stuck in the Boot. It is not passing the samsung logo.
Tried Delvik and Cache cleaning. Did not do a factory reset even thou its a safe kernel as i dont want to risk anything.
Flashed Stock ICS LPA flash via PC Odin. But noting is happeing. Can anyone help?
Solution Flashed GB and All is Well!
Most of, the best way is to flash a new kernel on this case..... Doing jbroid cleaning script before and then flash another safe kernel, maybe speedmod. This will help in most cases..... For the next time..... I got the same issues one time, after flashing cf Kernel, it was okay.......
That's not a brick or else, just some startup data is crashed, so system can't boot forward on any point.......
Greetz
Sts
Sent from my GT-N7000 using Tapatalk 2
atonal said:
Most of, the best way is to flash a new kernel on this case..... Doing jbroid cleaning script before and then flash another safe kernel, maybe speedmod. This will help in most cases..... For the next time..... I got the same issues one time, after flashing cf Kernel, it was okay.......
That's not a brick or else, just some startup data is crashed, so system can't boot forward on any point.......
Greetz
Sts
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
+1
I had the same issue, I flashed Fronco Kernel (the latest), reboot and my Note started, then I reflashed GL_NOTECORE Krenel.
Good luck.
Djoudi
Guys, what are the step by step instructions for installing MT Kernel 2.5?
I really cannot install it, I already tried flashing it via odin but my phone just crashes. Please help me guys.
Thank you in Advance guys!
Try mai77's method (flashing via CWM). It's in the second post of the kernel's thread (by ronnieryan). Make sure you've flashed to stock firmware first.
Sent from my GT-I9100 using xda app-developers app
I already did that. My phone just freezes in Samsung Galaxy Young Logo and after that, I cannot open the recovery mode.
Uhm, Is it recommended that I also include PIT and Bootloader in odin while flashing?
franzjonard said:
I already did that. My phone just freezes in Samsung Galaxy Young Logo and after that, I cannot open the recovery mode.
Uhm, Is it recommended that I also include PIT and Bootloader in odin while flashing?
Click to expand...
Click to collapse
Nope. NOT Recommended to use PIT/Bootloader/re-partition in odin.
Installing with ext4 system and cache could be tricky, Id recommend to flash to stock ROM before flashing the kernel.
1) Flash back to stock ROM
2) Go to recovery, flash CWM to get CWM recovery
3) Backup using backup and restore
4) Flash ext4converter.zip and reboot
5) Go to download mode
6) Flash the latest merruk kernel using odin
7) Now go to CWM, backup and restore -> Advanced restore -> Restore System
8) Wait till it completes
9) Reboot and your stock ROM will now boot
10) You can flash ANY custom ROM you wish and do any modifications.
Thats it, this worked for me
Oh thanks for the response. I already installed the kernel but I have a question. My galaxy y is having a random shutdown, do you know the reason why? And another question, what applications are you using to undervolt and to manage the cpu of your galaxy y?
franzjonard said:
Oh thanks for the response. I already installed the kernel but I have a question. My galaxy y is having a random shutdown, do you know the reason why? And another question, what applications are you using to undervolt and to manage the cpu of your galaxy y?
Click to expand...
Click to collapse
Same here, my phone does random reboot, too. I'm still in patience because the kernel hasn't been finished yet.
I'm using No-frills CPU Control to manage CPU and CPU spy to monitor it.
LilSasa said:
Same here, my phone does random reboot, too. I'm still in patience because the kernel hasn't been finished yet.
I'm using No-frills CPU Control to manage CPU and CPU spy to monitor it.
Click to expand...
Click to collapse
Oh, I thought it was just me that experiencing that problem. Anyway, thanks for the response.
franzjonard said:
Oh, I thought it was just me that experiencing that problem. Anyway, thanks for the response.
Click to expand...
Click to collapse
Hey, try setting your governor to ondemand (I was using ondemandx previously) and min. frequency to 312 MHz. My phone has lasted for nearly a day without rebooting, I just did it manually to update the kernel to developer edition version 8.
Guys just tick the option prevent other apps from changing the frequency in settings in No Frills CPU....
Because smtimes after deepsleep the phn frequency automaticalky changes to 156 mhz....
So it will not reboot automatically..
And keep its frequency greater than 312 to avoid frequent rebooting because armv6 processor supports frq greater than 300mhz....
Sent from my GT-S5360 using xda app-developers app
Guys, I already solved the auto shutdown problem. I reflashed the kernel because the first time I flashed it, I am on Merruk Kernel 2.0 Pre-final. Now I flashed it on stock. I got it solved and I set 312 Mhz minimum on no frills using smartassv2 and vr.
By the way, I will flash the version 8 now.
I'm running savie's kernel
help me
My phone suddenly shuts down and enters a bootloop
I have to pull the battery out and turn on my phone. It's quite annoying because it overheats and drains my battery, if left in a state of boot loop.
And worse is, it can happen ANYTIME, ANYWHERE!!!
inside my bag
in my pocket
while listening to music
while at home
while in school
while sleeping at night
tried changing cpu states, but no effect at all.
Things which could cause bootloops
1- using a buggy rom
2- using a kernel that doesn't support rom or file system
3- wrong/buggy/incompatible scripts used
You haven't mentioned what rom you a using
The only thing I can suggest is to delete all scripts in system/etc/init.d and then test to see if you are still bootlooping and you can try another kernel
if you are it could be anything so unless you get a logcat and find someone who understands it it's very hard to say what is causing it
All you can do is flash fresh stock rom via odin if the problem persists
rom=hyperion 8 build 2
init.d scripts:
00undervolt
01darky_zipalign
02loopy_smoothness_tweak
03net_buffer
05ram_optimize
06remount_fullext4
07sqlite_optimize
08system_tweak
99complete
Try deleting 99complete
Then change your kernel to hells fusion #50
If it is a kernel/script problem that will solve it
marcussmith2626 said:
Try deleting 99complete
Then change your kernel to hells fusion #50
If it is a kernel/script problem that will solve it
Click to expand...
Click to collapse
is it stable? no imei bug or anything
do i need a data wipe?
TrojanHorses said:
is it stable? no imei bug or anything
do i need a data wipe?
Click to expand...
Click to collapse
No need to data wipe when changing kernel
imei bug was only on latest version of hyperion (reloaded) which required savie #2 as it was based on a new baseband firmware not many people use
I wanted to get imperial kernel v3.3 since they added a google services battery fix
Ran script wiped etc... Phone just stays on model number inital boot screen. :0 This also happened on a stock root rom i tried.
Hybridmax works great but ive got passive battery drain and its a bit outdated. With hulk i cant get wifi working Maybe if tw v2 comes out itll work!? . Kushan seems unstable.
I was hoping imperial would patch the problem yet still no changes :/
any advice?
Try this.
*Update your recovery.
*download the zip again
*flash the file
*clear cache and dalvinks.
*remove the battery and keep it away for 1 min or so.
*place the battery again and turn the phone on
Revert.
DeepankarS said:
Try this.
*Update your recovery.
*download the zip again
*flash the file
*clear cache and dalvinks.
*remove the battery and keep it away for 1 min or so.
*place the battery again and turn the phone on
Revert.
Click to expand...
Click to collapse
I tried your advice before with no results.
Im guessing if trying on a clean install of a different rom had the same problem then the issue lies in a strange place
The other rom was a stock with root :0 so im guessing king of similar to what im running now. Maybe the stock roms have some problems ?
LyQi said:
I tried your advice before with no results.
Im guessing if trying on a clean install of a different rom had the same problem then the issue lies in a strange place
The other rom was a stock with root :0 so im guessing king of similar to what im running now. Maybe the stock roms have some problems ?
Click to expand...
Click to collapse
versions 3.4 resolved the issue i hope my battery life will be as good as everyone says
I've flashed voltaq kernel v15 on i9500 on touchwiz LL ROM, but whenever I open Synapse app it says: No UCI support detected.
Tried wiping cache, restoring stock kernel, etc. When I type uci in terminal it says command not recognized, but I could find the synapse files in res folder.
However I tried Nevermore X and Synapse worked with it. Since it had reboot and wake lock issues I reverted back to voltaq.
How can I fix the UCI problem in Voltaq?
Bro. That is known issue in Volt kernel. Anyway, install volt kernel again. If u get no uci message, manually reboot (mean turn off ur phone then turn on it). Do it 1-3 times then it will work back again.
kongacute said:
Bro. That is known issue in Volt kernel. Anyway, install volt kernel again. If u get no uci message, manually reboot (mean turn off ur phone then turn on it). Do it 1-3 times then it will work back again.
Click to expand...
Click to collapse
Hi @kongacute ,
I am facing the same issue and tried rebooting it several times but no luck.
I loved the kernel but the volume in very low and cant fixed it without synapse. Pls help.
Atrix2dBeast said:
Hi @kongacute ,
I am facing the same issue and tried rebooting it several times but no luck.
I loved the kernel but the volume in very low and cant fixed it without synapse. Pls help.
Click to expand...
Click to collapse
Weird. I used to use volt kernel with ale95 and ale95 based rom, also with other stock and that method help me so much. About volume control without synapse, see in NevermoreX kernel thread, he posted guide to customize it.
kongacute said:
Weird. I used to use volt kernel with ale95 and ale95 based rom, also with other stock and that method help me so much. About volume control without synapse, see in NevermoreX kernel thread, he posted guide to customize it.
Click to expand...
Click to collapse
Hi,
I flashed v 14.0 which is working perfectly with synapse support for me. Thanks for replying.
kongacute said:
Weird. I used to use volt kernel with ale95 and ale95 based rom, also with other stock and that method help me so much. About volume control without synapse, see in NevermoreX kernel thread, he posted guide to customize it.
Click to expand...
Click to collapse
the fix for me was
unroot my s4
flash supersu 2.46 thru recovery
then flash voltaqe
im not sure but whenever i update supersu
synapse fails.. but the old 2.46 works fine
so i never ever ever tried to update supersu..
thats the way i got synapse with voltaqe properly running
tried and tested on first flight, ale95 port, morphose v1 and v2
try it if you want.. but make backup first just in case..