Hello,
I have compiled custom kernel based on samsung update1 drop. I am able to compile and build the kernel along with initramfs based on the stock kernel. However, I get stuck at the booloader screen.
My searches so far did not turn up a way for being able to get some sort of early console communication to see where the problem is. Can someone give me a guidance on how I can figure out where the problem lies.
Thank you in advance
Ordered parts to get access to UART for console messages. As explained in
http://forum.xda-developers.com/showthread.php?t=1143190&highlight=serial+cable
and
http://forum.xda-developers.com/showthread.php?t=1010314
hopefully that will help
Related
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+
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
Yesterday I have created my first Android ROM. Flashed it and flashed the boot.img file.
This ROM includes a custom kernel.
When starting up, I see the bootloader splash screen and then somekind of graphical glitch where the logo is displayed twice in green and the screen goes all black.
I think it has something to do with the kernel. I am using version 2.6.32 with Android 4.2.2 for my Huawei Ideos S7. If you'd like, I can link the repos here, but I have build the ROM with a private clone of those repos.
How can I 'debug' the system and tell what is causing the device not to boot?
You can send me a guide if you want, and hopefully I will figure it out.
Thank you in advance,
Tim
Hi all,
I have been trying to port TWRP for my device (a somewhat dated tablet, the Toshiba AT100 Thrive) but am running into problems with the kernel. It seems that no matter what I try, I am unable to get a kernel that actually boots.
I have the full OmniROM 4.4 source (with the end intention of building OmniROM for the tablet) as well as the kernel source from Toshiba (it is their patched version of 2.6.39.4). I also have a known working recovery (built around CWM with a 2.6.39 kernel) and stock boot.img and ICS ROM for the tablet.
I have extracted the kernel config from the ICS ROM as well as the kernel command line parameters.
Additionally, I also have access to two other ports (CyanogenMod) with kernel sources for this tablet and have found the AOSP source for the 2.6.39 and 3.10 kernels.
I am using CentOS 6.7 64-bit as my build OS, as that is what I have running on my Linux machine. I have OpenJDK 1.6 installed as opposed to the Oracle version (this might affect building OmniROM, but certainly shouldn't affect the kernel build).
I can successfully compile the kernel from the Toshiba sources using the tablet's config, as well as the CM-based port kernel sources and the 3.10 kernel (2.6.39 has some bugs straight out of the Google repository, which I can only get around if I disable yaffs2 in that kernel config or replace the yaffs2 source for it with the equivalent from the Toshiba sources).
I have the Android emulator set up on my Windows machine with both a ICS and KitKat AVD. After being unable to get the Toshiba-based kernel to start on my tablet, I thought I'd try building a kernel from the sources to run in the emulator.
At this stage, not a single one of my kernels has successfully booted either the tablet or the emulator. I have tried using the kernel config from the ICS AVD to build both the Toshiba 2.6.39 and AOSP 3.10 sources. The compile completes with no errors and a zImage is produced. However, it fails to boot the emulator.
Out of desperation, I have tried downloading the toolchains for Gingerbread and ICS and using those to build the kernels instead of the toolchain provided with OmniROM 4.4. That hasn't made a difference, either.
On the tablet, I have tried extracting the known working recovery kernel from the CWM recovery and using it as a prebuilt kernel. TWRP fails to load and the tablet always reboots after a few seconds, regardless of whether I set the kernel commandline parameters or not.
I am puzzled by this. Clearly there is something wrong but I am at a loss as to how to debug it, especially as do not appear to be able to produce a working kernel either for the tablet or emulator, despite having the sources and the kernel configs.
If anyone has any suggestions, they would be much appreciated.
Still have the same problem.
I've now tried building an Ubuntu 12.04 VM and compiling the kernels within that, but still get the same results.
Does anyone have any ideas or has anyone else ever run into this problem?
Did it ever work? I am experiencing this with SM-G950F. Very keen.
Unfortunately I was not able to resolve the issue. After spending a fair bit of time on it, I gave up and moved onto other projects. I've still got everything I need to try again, so at some point I may do so (especially as a use case for my tablet is possible again in the near future).
Has anyone been able to build a kernel for this phone.. I can't seem to get mine to work.. I'm going to try again and work on fixing the twrp issue we all have no promises I didn't wasn't able to get anything to boot after I repacked my boot.img.
Kernel Source for Borneo
Have you been able to build the kernel source at all? I keep running into issues.
What steps did you use to attempt the build and what errors are you receiving?