Flashed compiled kernel, but stuck on Sony logo - Xperia Z5 Compact Q&A, Help & Troubleshooting

My phone is Sony Xperia Z5 Compact, running in LineageOS 14.1
I need to compile NetHunter kernel.
The problem is; i cant find kernel sources.
Which one am i must use? LineageOS source or Sony source ?
Edit: have Xperia Z5 Compact, running LineageOS 14.1
I Downloaded the source from: https://github.com/LineageOS/android...l_sony_msm8994
and used toolchain 64
I compiled for NetHunter (kali)
I got image.gz-dtb bla bla
I used android image kitchen and applied for replace original image to compiled image and repacked bootimg.
After flash new compiled boot , device open but keep in Sony logo.
Need help..

@NetRoot , hey. kinda same thing. finally got twrp flashed , yay!! , but now whenever 'reboot > system' am stuck on sony logo.

Related

Problem building Xperia Mini Kernel

Hello, I want to build Xperia Mini Kernel.
I followed all the steps on the SE official site, and used the ramdisk from the DooMLoRD sources on github.
However, after flashing my kernel the phone does not boot up(doesn't even show first SE logo). What shall I do ?
Please help me understand kernel building.

Building recovery for simba Sx1

I am following this guide XDA university porting cwm to a new device and I just wonder if I need the same android version of sources as it is on the android phone.
I mean, the phone is running android 4.2 so it is neccecary to download cm 10.1 sources or can I build it using cm 11 sources?
tulen_kobi said:
I am following this guide XDA university porting cwm to a new device and I just wonder if I need the same android version of sources as it is on the android phone.
I mean, the phone is running android 4.2 so it is neccecary to download cm 10.1 sources or can I build it using cm 11 sources?
Click to expand...
Click to collapse
It is not necessary to have the same android source as your device's android version to make cwm. CWM is part of the kernel and not the android system. Your device's kernel will be extracted and the ramdisk will be replaced with cwm ramdisk and after that the kernel will be built with cwm ramdisk then you can use it as recovery.
If you want I can help you out with twrp recovery. I have done it for LG L65 and L70. If you want my help with twrp then please download omni rom sources (manifest: https://github.com/omnirom/android ) or just replace bootable/recovery folder with the omni's one in your cm source tree, get kernel source code for your device or have a boot.img, make sure your device has a recovery partition so recovery is not part of the kernel image as a secondary ramdisk like on samsung devices otherwise I could not help.

[Q] Cyanogenmod 13 for Cherry Flare S Play

Hello Everyone,
I made Cyanogenmod 13 build for moto e condor(which is supported by cyanogenmod), then I installed it using twrp recovery and it's working fine.. But now from this cyanogenmod source code I made cyanogenmod 13 build for cherry mobile flare S Play (which is not supported by cyanogenmod) by follwing "How To Port CyanogenMod Android To Your Own Device" wiki page.. I did all the steps as mentioned in this page and one more extra thing I did that I changed kernel folder of surce code(which is kernel version 3.4) with another kernel source code (kernel version 3.10.72), because cheery mobile flare s play has 3.10.72 kernel version..
I build Zip file successfully for Cherry mobile flare s play and I installed it using twrp recovery but after installing while doing reboot system it's only showing flare s play icon and then black screen is coming.. now I am not able to install cyanogenmod 13 build in cherry mobile flare s play
Please do help if anyone knows..
Thanks
Fall-through from normal boot mode
hieuvan said:
Although I don't own the device, but here's some common solutions that you can try:
Restoring the old kernel to your build?
Carefully check the new kernel to make sure it's compatible with the firmware?
Re-flash stock ROM then re-flash your build again?
Cheers!
Click to expand...
Click to collapse
Thanks for reply..
old build i have deleted and today I made fresh cyanogenmod 13 build but when I installed it..
It's showing boot up failed..
Fastboot Reason: Fall-through from normal boot mode
boot up failed
why it's showing this error??
When this error comes, do you have any idea?

Stuck at Company logo after flashing my newly built ROM based on Android 6

I have built Resurrection Remix ROM ( Android 6.0.1 ) for my Meizu m2 note.
The problem is that after flashing it got stuck at the company logo and I dont know why.
Can somebody please help me out ?
Device related repos:
kernel : https://github.com/Moyster/android_kernel_m2note/tree/mm-6.0
device tree : https://github.com/Moyster/mm_device_meizu_m2note
vendor props: https://github.com/Moyster/android_vendor_meizu_m2note/tree/los-13.0
Suvam Mondal said:
I have built Resurrection Remix ROM ( Android 6.0.1 ) for my Meizu m2 note.
The problem is that after flashing it got stuck at the company logo and I dont know why.
Can somebody please help me out ?
Device related repos:
kernel : https://github.com/Moyster/android_kernel_m2note/tree/mm-6.0
device tree : https://github.com/Moyster/mm_device_meizu_m2note
vendor props: https://github.com/Moyster/android_vendor_meizu_m2note/tree/los-13.0
Click to expand...
Click to collapse
Can you adb while booting and grab a log ? If you don't get to the boot animation then you probably can't so I'd guess it's likely to be something kernel related
sawdoctor said:
Can you adb while booting and grab a log ? If you don't get to the boot animation then you probably can't so I'd guess it's likely to be something kernel related
Click to expand...
Click to collapse
I cant get to the boot animation ..stuck at the company logo, so i cant take log.
However, i have tested the kernel with other ROM and its working fine. So no problem with the kernel.

Rom building help

Hi, I'm porting my first rom ever which is Project Sakura. I have problem with booting it, when I made boot by porting zImage from los for platina but the rom stucked at Mi logo, when I used the boot.img from Aurora kernel then it stuck at bootloop. I'm new noob and I don't have idea how to fix it, any help will be great.

Categories

Resources