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
Related
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
Hello. So, I was using the default ROM for my Galaxy Y, everything in factory settings, and then it started rebooting a few weeks ago. So I tried and installed a custom ROM (BeautySense), but it didn't solve the problem.
The strangest thing is: when I put on the battery, the cell phone turns on all by itself, I don't need to press the power button for it to turn on, and when the cell phone is on, when I press the power button to lock the screen, nothing happens.
Anyone has any idea what might the problem be?
Thanks.
don't worry
vitorassuena said:
Hello. So, I was using the default ROM for my Galaxy Y, everything in factory settings, and then it started rebooting a few weeks ago. So I tried and installed a custom ROM (BeautySense), but it didn't solve the problem.
The strangest thing is: when I put on the battery, the cell phone turns on all by itself, I don't need to press the power button for it to turn on, and when the cell phone is on, when I press the power button to lock the screen, nothing happens.
Anyone has any idea what might the problem be?
Thanks.
Click to expand...
Click to collapse
it has nothing to do with the software its a hardware problem it can be one of thees two:
1.the power button is stack and that will explain why you can't lock the screen and the reboot because you are making him power off and then power on
2.the battery keeps moving form inside the case causing it to shutdown and then start by it self which happens with a lot of phone like my note 2 and y duos
report to me after you chick step 1 and step 2
press thx if i helped :fingers-crossed:
Hello. It did help, but I don't think the problem is the battery moving. As for the power button being stuck, I'd already thought of it, but I don't know how to fix it. Apparently it is not stuck, but maybe it is stuck on the inside. In that case, how can I be sure?
Thanks.
It's a 90% hardware problem scenario.... But why don't you try changing to another kernel? (any stable kernels like hells fusion, jarvis, savie etc)
If it still reboots then u will be damn sure it's the power button problem.
vitorassuena said:
Hello. It did help, but I don't think the problem is the battery moving. As for the power button being stuck, I'd already thought of it, but I don't know how to fix it. Apparently it is not stuck, but maybe it is stuck on the inside. In that case, how can I be sure?
Thanks.
Click to expand...
Click to collapse
you can try flashing a kernel because when my phone fell in the bathroom i opened it my self and i lost my volume Button so i prefer that you keep the opening of phone as the last Solution :fingers-crossed:
Try to flashing with new kernel if it didn't work i think it's hardware problem
Solution
Many replies stated just to flash kernel.
Actually, you have to flash a kernel and then flash ROM.
If you do the reverse, you will stuck in bootloop.
The instability of the kernel is the cause.
Also do not install too many tweaks, which also causes some stability issues.
Over Clocking in some kernels also cause this restarting problem.
Solution: Flash Kernel and then flash the ROM
If it doesn't work, it is surely the hardware problem.
Press thanks button if I have helped you!
the_pirate_predator said:
Many replies stated just to flash kernel.
Actually, you have to flash a kernel and then flash ROM.
If you do the reverse, you will stuck in bootloop.
The instability of the kernel is the cause.
Also do not install too many tweaks, which also causes some stability issues.
Over Clocking in some kernels also cause this restarting problem.
Solution: Flash Kernel and then flash the ROM
If it doesn't work, it is surely the hardware problem.
Press thanks button if I have helped you!
Click to expand...
Click to collapse
this is not true
for stock based roms flash rom then flash kernel - this is because kernel has things like wifi driver that needs to be flashed after the rom however it doesnt matter if you do it the other way round - you can always flash the wifi driver seperately
for cm based roms you need to flash kernel first in order to format your system to ext4 in order to install the rom if not already on ex4 system partition
Thanks
marcussmith2626 said:
this is not true
for stock based roms flash rom then flash kernel - this is because kernel has things like wifi driver that needs to be flashed after the rom however it doesnt matter if you do it the other way round - you can always flash the wifi driver seperately
for cm based roms you need to flash kernel first in order to format your system to ext4 in order to install the rom if not already on ex4 system partition
Click to expand...
Click to collapse
Thanks for correcting my mistakes and guiding me!!
Anyone solved this problem? I am experiencing it right now, what to do .?
Sent from my GT-S5360 using Tapatalk 2
Hello, guys and girls.
So, I'm not an expert like most of you. I need help.
I will explain you what happend with my Nexus 4: I installed CyanogenMod 11 with the installer some weeks ago. Yesterday, I installed an app called "Touch Control", which would allow my phone to have Knock On feature. But it installed a kernel that would make this work. That kernel have MANY bugs, such as Wi-Fi do not work and changed colors. My phone does not have internet, because I don't have mobile data.
I do not have TWRP or CWM, just the simple CyanogenMod Recovery. And I can't install anything because of internet (I can copy .apk to my phone and insall it).
Here is what I would by happy to do: change that kernel to the default one (I didn't make its backup) or to any other kernel that works.
Ask, please, for any detail that can help.
Thank for you to reading my post.
Just something else: I don't want Knock On feature anymore. I just wan't my phone working properly.
What you did was install a AOSP kernel on a CM rom, that does not work well as you might have noticed, you need to dirty flash CM11 to get the default kernel back.
nibla101 said:
What you did was install a AOSP kernel on a CM rom, that does not work well as you might have noticed, you need to dirty flash CM11 to get the default kernel back.
Click to expand...
Click to collapse
I have a question: when I flash CM11, will the kernel be replaced? I heard that the kernel in Android phones is separate from the operating system.
caiodanielnunessantos said:
I have a question: when I flash CM11, will the kernel be replaced? I heard that the kernel in Android phones is separate from the operating system.
Click to expand...
Click to collapse
Yes it will, all roms come paired with a kernel otherwise they would not boot.
When you dirty flash CM11 it will replace ur /system and /boot(this is where the kernel is) but it will leave ur /data and /sdcard so your apps and settings remain.
nibla101 said:
Yes it will, all roms come paired with a kernel otherwise they would not boot.
When you dirty flash CM11 it will replace ur /system and /boot(this is where the kernel is) but it will leave ur /data and /sdcard so your apps and settings remain.
Click to expand...
Click to collapse
Thanks, I will try this.
The most easy way to get back to stock kernel (no matter which android u currently have) is to use a toolkit like Wugfresh and select the stock kernel option.
Only think u need is a pc with internet and the phone to be connected with the cable.
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..