Hello friends. So I am officially stumped. I have an issue with my kernel bootlooping. The interesting thing is, eventually it boots. After about 5-10 minutes of bootloop, it just boots. Weird right?
See, I merged a lot of code with my kernel and I'm not sure what is causing the bootloop. Here is my source: https://github.com/Snepsts/kernel_e980
It started on the add intelli-plug commit (which also includes intelli-thermal) it is probably important to mention disabling intelli-plug and thermal (and only one of each) all have the same outcome. I have also tried wiping the board back to its original state. I'm assuming its one of the core changes or nr_running changes. But I cannot find any way to get a log of the issue as it is not in a stable state during bootloop to give me logs from adb. I also cannot compile intelli-plug without the changes I made. And I really want to have it. I have looked for code I may be missing but cannot find any. I have made many different test kernels and taken the ramdisk and config from the latest official cm build for my device. Does anybody have any ideas? If you need anymore info please let me know. Thanks for any help in advance.
Sent from my LG-E980 running Carbon KitKat & E980 Kernel+
Related
Google just moved out the 2.6.32 kernel from the experimental git repo to the msm repo. This means that google thinks they are stable now.
There are currently two 32 branches:
android-msm-2.6.32-nexusonec
http://android.git.kernel.org/?p=kernel/msm.git;a=shortlog;h=refs/heads/android-msm-2.6.32-nexusonec
android-msm-2.6.32
http://android.git.kernel.org/?p=kernel/msm.git;a=shortlog;h=refs/heads/android-msm-2.6.32
I've compiled both and I'm finding the nexusonec branch more stable than the 32 branch. The 32 branch causes issues with the gallery and camera app not recognizing the sd card. Everything seems to work fine in the nexusonec branch (sdcard, wifi, BT, camera, etc). Speed is definitely faster than 29.
For those who are interesting in flashing the 32 zimage, they can d/l it here:
http://drop.io/xdp6104#
Right now the kernel is just a stock config, meaning no tethering or anything else. Only change I've made from stock is to use the deadline I/O scheduler. I'm sure cyanogen will add those other goodies when he releases a new version.
Very nice: cant wait for a Enomther rom with this new Kernel
nice....
ive compiled a nice cyanogen kernel 2.6.32 already
just need to get the wifi module compiled correctly and we are gtg!
Does this mean that they've fixed some of the power saving regressions people were seeing with 2.6.32 before?
Installed on my Nexus with enomther 1.61: works nicely
Tot mem 395448K, Free 265916K
Does this still have the charging issue that blocks the battery to charge when it goes under 90%...???
eug89 said:
Does this still have the charging issue that blocks the battery to charge when it goes under 90%...???
Click to expand...
Click to collapse
86% now and charging..
eug89 said:
Does this still have the charging issue that blocks the battery to charge when it goes under 90%...???
Click to expand...
Click to collapse
It wasn't an issue per-se it was a 'feature'
The problem was caused by downgrading to older kernels after using 2.6.32. Certain hardware states that were set by the new kernel telling the battery not to charge weren't being un-set by the new kernel, and the older kernel didn't even know about them. They patched the newer kernel pretty quickly after getting feedback so that it removes the hardware state when shutting down, I believe. So, yes, it's 'fixed'
FettsVett said:
It wasn't an issue per-se it was a 'feature'
The problem was caused by downgrading to older kernels after using 2.6.32. Certain hardware states that were set by the new kernel telling the battery not to charge weren't being un-set by the new kernel, and the older kernel didn't even know about them. They patched the newer kernel pretty quickly after getting feedback so that it removes the hardware state when shutting down, I believe. So, yes, it's 'fixed'
Click to expand...
Click to collapse
Thanks, i called it issue because i didn't know how to call it but i knew that it was meant to be a sort of new feature of the 2..6.32 kernel and I wanted to write above 90% and not under 90%... did a bit of a mess
woahhh its way faster
thanks dwang
will do some thorough testing and post back soon.
edit: Hmmm having some trouble with fastboot... unable to push wifi via adb?
anyone else encountering this?
Are you trying to push the ko module on fastboot mode?
This kernel is FAST and SNAPPY! HIGHLY RECOMMENDED!
boqonx said:
Are you trying to push the ko module on fastboot mode?
This kernel is FAST and SNAPPY! HIGHLY RECOMMENDED!
Click to expand...
Click to collapse
yeah. iirc thats where you do it right?
Let the OS run, then push through adb. Can't do it when it's on recovery either because the /system/lib is not mounted. Wifi should work even without a restart.
yep just did that
i think i was just confused on where to use adb
it still works so all good. this kernel is zippy.
Damn right This thing flies now! Scrolling through messages is MUCH smoother. Seen a lot of tearing when scrolling on CM's kernel.
I released my undervolted version of CM's in the other thread. He changed the scheduler from anticipatory to deadline as well.
Will try! Had any reports on instabilities yet?
Dwang: great job on the deadline scheduler suggestion. It really does make the whole experience smoother.
Can someone write the exact adb command to push it?
Code:
adb remount
adb push ./bcm4329.ko /system/lib/modules
himmatwala said:
Can someone write the exact adb command to push it?
Click to expand...
Click to collapse
I had the problem with replacing the broken glass on my TF201 that caused an inverted X-axis. Thanks to the solution provided by flumpster, I was able to get the fix the problem in the stock JB ROM (10.4.2.18) so that the inversion is corrected there, however the problem still exists in TWRP. I understand why. I asked in the TWRP IRC chat support if there were any fixes or patches that could be applied that would correct the issue. I was told that I needed to compile my own TWRP to load with the fix and that there were flags that could be set to flip either axis. I've looked into it but at the moment I am a little overwhelmed with the process of setting up the build environment and making sure I have everything in order to do this as I have never compiled anything from source before. Is there anyone out there that could possibly do a build of a compatible version of TWRP that would fix this issue? Many thanks to anyone who can.
i compiled htcs official kernel and made some mods to it and it worked well, some wifi bug made me retry making it from 0, but now everytime i compile the kernel with the same toolchain but no modifications to it, lcd image disapears when booting, any help?, its a rare bug that shouldnt be happening since i already compiled and nothing like this happened before
So I've rooted my phone less than a month ago, and I get this bug where the phone just freezes for 10-60 seconds, pressing the power button does nothing, I just have to wait until it sorts itself out. It happens quite often, and it's really annoying. One guy mentioned the same bug in the HTCDev unlock/root thread, but he was lucky enough to have the AT&T version, so he was able to get back to stock with the ruu.
I've already performed a factory reset twice, but it didn't help.
Does anyone know what my course of action should be? Should I download one of the back-ups, which one and so on. Also, how to get back to stock recovery, because TWRP doesn't let me do OTA upgrades.
I bought the device in Croatia, if that means anything, because I've seen dozens of different twrp backups so far.
Thanks in advance guys
HTC Desire 610 AT&T and EU is not 100% same phone, firmware also have pretty different version numbers: latest AT&T is 1.53.502.1* EU 1.31.401.3(Croatia).
So you cannot expect that everything will go without any problems.
Sorry I replied before I fully read your question.
You're on the stock Rom and kernel?
Stock rom, JMZ's kernel.
JMZ probably took source code from HTCDEV for US(AT&T) version of phone, some people with EU/International version of phone have similar problems like you (member DulinDuskhawk) with JMZ Kernel.
Please go to thread "Jmz A3UL Kernel v1" and ask someone for stock EU kernel or send message to member DulinDuskhawk, maybe he found a solution.
TomoBero said:
JMZ probably took source code from HTCDEV for US(AT&T) version of phone, some people with EU/International version of phone have similar problems like you (member DulinDuskhawk) with JMZ Kernel.
Please go to thread "Jmz A3UL Kernel v1" and ask someone for stock EU kernel or send message to member DulinDuskhawk, maybe he found a solution.
Click to expand...
Click to collapse
Hi TomoBero, I'm not 100% sure but I think jmz's kernel is made from 1.30..... international htc sorces (I'll check soon for exact version) as there where no at&t sources available at the time he did it. I think most problems with flashing other kernels is the fact that HTC built kernels are configured to only be able to load modules that were compiled specifically for that kernel. This is definately what has caused wifi to stop working for many people who have flashed other peoples backups or at&t rom(withut backing up atleast the own /system/lib/modules from their origianal rom as when gong back to their original kernel the modules no longer match the kernel). I have a build environment set up for compiling the kernel and have local sources for 1.29.... asia ,1.31...... EU_international, and 1.30.....US at&t. I can (and have) compiled these kernels as stock with just the flag changed to allow loading of modules that don't match version. If you let me know the software version number you (or others) are running I can supply a kernel update.zip and seperate /system/lib/modules.zip that matches software version and you to return to stock and experiment with modules if still having promlems. I havn't merged jmz's insecure /system code into these sorces so apart from allowing the kernel to load non-matching modules they are comletely stock.
MiniBlu
Hi MiniBlu, it's 1.31.401.2
Do you by any chance know how I could return my device to stock recovery, so i can install OTAs?
Thank you so much dude
I'm in the same boat. I'm trying to get back to stock, somehow.
I really need to go back to stock as soon as possible, the sim card locking mechanism doesn't work all of the sudden, and I've read it has happened to hundreds of 610s already. Because I'm unsure if my guarantee will work after root (although it's a hardware fail), i really need to get rid of the red disclaimer at boot (although I sadly think it can only be achieved with S-OFF). :c
After rooting my s9+ with the modified Magisk, my phone sometimes becomes unresponsive. I cannot identify any sort of trigger for this to happen, it just does. The AOD displays but does not update. The notification LED still blinks, but when I go to unlock the phone it freezes and I am forced to soft reset it. I am root with Magisk and have TWRP installed. I followed Max Lee's tutorial on how to root the S9+. Any ideas on why this is happening and how to fix it?
Hey, Did you have any luck with this, i am having the exact same issue?
having the same problem i followed Max Lee video and everything work fine until the phone started freezing
same issue on the G960F/DS....
wonder who can help us regarding with this issue.
For everyone having this freezing after rooting...attention to detail is absolute paramount, go back and re-read the twrp thread by jesec. For those (possibly those having freezing issues) who find that challenging, here is a snippet of jesec exact words..." Samsung implemented security measures such as "Real-time Kernel Protection (RKP)" and "RKP Control Flow Protection".
Those security measures are intended to block control flows such as privilege escalation, memory kernel code modification, etc which are not authorized by Samsung.
If those are not disabled, processes (such as daemon of root solutions) that violated those security rules will fall into deadlock.
Deadlocked processes will then consume large amount of resources (leads to performance issues, battery drains) and eventually crash the system.
Technically it is possible to disable those security measures by hex editing stock kernel but just simply flash a custom kernel is better in my opinion.
TL;DR: Flash custom kernel before root or be screwed.
To reiterate...flash a custom kernel before root or be SCREWED
I'm not saying this is 100% u guys issue, but seems kinda likely?
can someone post links or steps on how to fix this freezing lock screen issue, i tried reading the threads but did not find anything, thanks
I was facing the exact same issue after using his tutorial.
I've tested SOD Killer from the Playstore so far it's working fine! No freezes anymore .
Installing a custom kernel like elementalX should also work.
crs_dev said:
I was facing the exact same issue after using his tutorial.
I've tested SOD Killer from the Playstore so far it's working fine! No freezes anymore .
Installing a custom kernel like elementalX should also work.
Click to expand...
Click to collapse
Can we flash this Elementalx over the N965F_Root_for_OEM_issue_devices/Magisk we already installed ?
I already installed the TWRP, No-verity opt encrypt and the N965F_Root_for_OEM_issue_devices package on my friend's 960F.
I would be really greatful if anyone could help me with this.
I had the same issue after having troubles initially getting Lineage flashed and working on my S9.
I removed Magisk, reset and it still was freezing after a lock.
I reflashed Lineage through TWRP and now all seems to be back to normal with no freeze after lock.
Possibly try the steps I did and see if they worked out for you.
hey guys, you solved the issue?
i experience same Problem..
Any one notice , this issue occurs after we apply lock screen password or biometric security. in my device i notice, when i apply lockscreen password or biometric lock my phone freeze. after i remove all lock and set default to swipe...its not freezing. anyone sees that
I solved the same issue (1 hour ago, so I hope it's fixed now) installing first:
ElementalX Kernel
and than installing:
G965_Root_for_OEM_issue_devices_V5 (the lastest available right now)
Following the instruction on the XDA Thread
Hope this can be helpfull to solve it
Its because of dm verity issues...i assume that you rooted the phone over an odin flashable stock rom. To fix this try installing either a patched stock kernel from Soldiers website or other custom kernels if you consider doing over(under)clocking.
KevAngelo14 said:
Its because of dm verity issues...i assume that you rooted the phone over an odin flashable stock rom. To fix this try installing either a patched stock kernel from Soldiers website or other custom kernels if you consider doing over(under)clocking.
Click to expand...
Click to collapse
What is the different in Soldie between Patched Kernel and ELS custom kernel?