Hi,
I have compiled a kernel for my Samsung GT-S5690M from the samsung opensource website. I used the toolchain which was named in the Makefile. After I compiled the Kernel I booted into windows and put the kernel into a .tar and flashed it using ODIN and the flash went well.
My issue is that my phone boot loops on the initial splash screen. I can still get into download mode and flash the stock zImage and put everything back to normal. I am looking for a way to determine what is causing this. I really do not know where to look as adb is not an option because my phone does not get to the second splash screen. I enabled the debugging_config option in the config file but nothing came out after I compiled the kernel.
How do I determine what is wrong with my Kernel? is there a way to troubleshoot this?
Thanks in advance
:highfive:
Related
I've been running imnuts' debloated EE4 since last weekend. Rolled back to ED1/Flashed EE4/Edited build.prop ... After I flashed to the EE4 I had EE4 baseband but ED1 build still, hence editing build.prop
When I flased the EE4 the voice spoke occaisionally during first boot, which I assumed was the file structure being re-written. Phone has been working fine all week, no issues there.
This morning, out of curiosity, I tried to enter recovery mode, to see if it were voodoo or stock. vol.up/home/pwr and the samsung logo appears. But it doesn't enter into ANY recovery screen. It just stays at the Sammy logo until I pull the battery. What's up with that?
Also.... with file structure re-written, can this still be flashed back to say the stock rooted ed1 tar file still? Would there be any steps that need to be taken before attempting such?
Looking at voodoo log file lag fix is being enabled and such.
Have you flashed the clockworkmod recovery odin file?
And before flashing anything not using voodoo just disable it.
How would I disable voodoo ?
Just create a filed called disable-lagfix on your sdcard
Or disable it in clockworkmod
Just create a folder in the root directory named disable-lagfix and that does it? So far as cwm goes, that was one of the initial things I posted about. I've always been able to enter recovery mode by holding down up volume/home and power until the samsung logo appears. Then releasing them would bring the recovery screen up. Stock Samsung was blue lettering and then with cwm installed it was yellow with added options on the menu. Now if I try to get to that point, the recovery screen never comes up. It just stays at the Samsung logo and basically is frozen there until I pop out the battery. Phone boots fine into normal use.
Recovery may just need to be reflashed.
But yea you can disable lagfix just to try it so you know how. If disable-lagfix doesn't work try using an underscore instead. Just be sure to reboot so the conversion actually happens
This is kind of a long read but thanks in advance for bearing with me.
Phone Details
Go Launcher Pro
16GB
I had a couple ram boosters and some apps that tweaked my cpu's
ROM
Cyanogen Mod 10.1.1
Kernel
Stock Kernel (before attempted upgrade)
Model
SCH-I535
Battery
2100 mAh
3.8 V Li-ion
Recently as of 8pm this evening I attempted to install a Faux Custom Kernel from a zip in my root storage using the CWM Recovery interface. From what I could tell, while I was watching the screen, the files unpacked and installed correctly. Before doing all this I researched the proper kernel and method of installation. Simply put, after the installation the phone rebooted and flashed the SAMSUNG logo (no cyanogenmod avatar) and then the screen went solid black. It will load into Odin mode as well as CWM Recovery successfully. I have cleared my data/caches and tried to plug it into my computer to try to flash a different kernel with another zip but it hasn't worked due to my computer not properly installing the MTP drivers. When I turn the phone on the logo pops up with no boot animation what-so-ever and the bottom buttons work but the screen is always black.
Quigly said:
This is kind of a long read but thanks in advance for bearing with me.
tried to plug it into my computer to try to flash a different kernel with another zip but it hasn't worked due to my computer not properly installing the MTP drivers. When I turn the phone on the logo pops up with no boot animation what-so-ever and the bottom buttons work but the screen is always black.
Click to expand...
Click to collapse
Try to flash back the original kernel, if not working, wipe cache/dalvik cache/data/system then reflash the rom.
Solved
I have solved the problem. Basically what I have done now is unrooted the phone. I, using Odin3 v1.85, flashed the Jelly Bean 4.1.2 Stock Rom image file and then the CWM Recovery. Next I flashed the insecure bootloader and from there got back CM11 with a custom kernel.
Hi,
I installed cyanogen, latest one. Flashed an old kernel from dorimanx by mistake, i didnt see that cyanogen was on lollipop for gt9100i. Everything worked fine untill i needed to restart the phone, now im stuck on a screen with modelname and a yellow triangle. I can go to download mode and flash kernel but it wont get me anywhere. Sometimes unit gets past the screen and show the kernels splashscreen, thats it. I need a tar file for odin for the newest dorimanx unofficoal 5.x rom but i can only find zips.. I tried flashing cwm in but i cant get into recovery mode... Any tips?
**Update**
I somehow got into CWM and could reinstall cyanogen, now i get the blue robot (cyanogens) that flashes, hope isnt lost. Can i inside cwm install the zip with kernel?
Hi Everyone,
Im using XT1550 and installed CM-12.1 from the official snapshot type ( download.cyanogenmod.org/?device=osprey) and its been working okay.
I wanted to build my own and so followed steps at Build_for_osprey wiki page to build a ROM (No changes, just copied steps from there) and tried to install it. Once I get into TWRP and flash the zip file, it comes back to the "Warning Bootloader unlocked" motorola white screen, vibrates for sometime and then is stuck at that screen. It then switches off and loops again to the same screen after about 30 secs. The same thing continues. I can meanwhile boot into recovery and install the official ROM and get back to a working phone, but not sure why the loop is happening.
Here are the differences from the official one and the one I built.
1. The system.new.dat from official CM website is of size 492412928 whereas the one I built is of size 427536384. But funnily, when I use sdat2img.py to extract the dat file as an image, the file sizes of the image file are the same (2432696320). I'm not sure why the sizes of the 2 ROM are so different.
2. Everything else is the same.
The one thing I changed during building was to use Oracle JDK instead of OpenJDK by changing the build/core/main.mk from requires_openjdk := true to false so that I can get past that stage.
Are there any pointers on how to debug this? Is there any way of looking at logs to find out why the one I built may result in a loop?
Thanks in advance
Raja
I am working with Pixel 2 and compiled the kernel code for the same using gcc compiler. When I am flashing the boot image obtained from the compilation, the phone boots up properly but it stucks on the lock screen. The power and volume button works normally but the touchscreen doesn't. What could be the possible reason for this? In case I am flashing the original boot image, it works fine again.
dubeyss said:
I am working with Pixel 2 and compiled the kernel code for the same using gcc compiler. When I am flashing the boot image obtained from the compilation, the phone boots up properly but it stucks on the lock screen. The power and volume button works normally but the touchscreen doesn't. What could be the possible reason for this? In case I am flashing the original boot image, it works fine again.
Click to expand...
Click to collapse
I could solve the problem, so mentioning the solution here, in case it comes handy to anyone. So I was using the original factory image for Pixel 2 (walleye-opm2.171026.006.c1). Apparently, this image has some issue with the touchscreen, so when I was modifying the boot.img over it, the touchscreen was not responding. It was a guess work but when I flashed the new Android Pie image (walleye-ppr2.181005.003) and flashed the modified image using boot.img from this factory image, everything worked just fine.