Dear xda-developers members,
I need some help in the right direction:
I have installed Dhollmen's kernel (from forum.xda-developers.com/showthread.php?t=2176563) on my GT-P5110
which is rooted and running CM10.1 at the moment and I used cwm to flash the kernel (from the link above).
Now I am trying to compile the kernel from their source code (see link) and flash the compiled kernel.
This has not been a success yet. I either get stuck at bootscreen or in a boot loop.
What I have tried:
Code:
export ARCH=arm
export CROSS_COMPILE=~/android/toolchains/arm-eabi-4.4.3/bin/arm-eabi-
make dhollmen_P51XX_defconfig
make
This resulted in zImage file and I tried to flash with heimdall:
Code:
heimdall flash --KERNEL arch/arm/boot/zImage
This got me stuck on the bootscreen
Try 2:
With the compiled zImage and the working Dhollmen kernel zip (DhollmenCM-P51xx-Kernel_20130706.zip from the link)
I unpacked the working Dhollmen kernel, split boot.img, replace zImage with mine, repack to boot.img, repack to zip and flash zip from cmw
This got me stuck in a boot loop
The frustrating thing is that I have no errors so I am clueless of what is going wrong.
Can someone explain how he is going from his source code (https://github.com/Dhollmen/DhollmenCM_kernel) to a flashable zip file?
EDITED: Posted in Galaxy Tab 2 10.1, thread can be closed/deleted here
You will have more support in the tab 2 forum...this is the tab 10.1 P7500 forum.
Sent from my GT-P7500 using Tapatalk HD
Hello, I have built a custom kernel for CM12 (Android Lollipop) and I want to release it as a boot.img. After building the kernel, I took the brand new zImage and started searching for a tool that allowed me to unpack and repack the boot.img, which I had extracted from the ROM zip. The problem is, every kernel tool/kitchen failed to unpack the boot.img with errors like "Android Magic not found in boot.img" or other errors related to boot_magic or Android Magic.
What should I do in order to unpack the boot.img?
Thank you in advance
Hi all..
I have complied my source code and brought up zImage and I have ram disk file. Using mkbootimg tool I created my own boot.img. Now how can I flash that boot.img on my Samsung GT-S6012 mobile.
As I found someone saying that Samsung mobiles doesn't have fast-boot mode or boot-loader mode.
Someone please help with a solution to make this happen.
Thanks in advance
Hi folks,
I had opened the bootloader for this device, the TRWP is starting fine. The partitions: product, boot and vendor is not modified, only the vbmeta has been changed, and also the recovery and the system.
I'm used the system file: lineage-17.1-20200402-UNOFFICIAL-treble_a64_bvN.img
The file I'll has flash with the command: heimdall flash --SYSTEM lineage-17.1-20200402-UNOFFICIAL-treble_a64_bvN.img, the flashing was successfully.
The SMA105 is booting, but after 10 minutes, the phone is stucking in the same boot logo. Nothing is happend, no steps for terminating the system installation. It seams, the SMA105 waiting for an command. But, I can not read an log file for the booting or switching of temporally the bootlogo.
Any solutions for me?
Greetings tiptel170
P.S.
Flashing other roms for example Viper etc ... This is the same effect. Wateing and wateing ...
renaming the file "bootaniamation.zip" in the folder /system/media was not successful. Because, it turns the animation on with the word "ANDROID". And the adb logcat, the same it will not working.
I'll has changed the file default.prop
Code:
ro.adb.secure=0
persist.sys.usb.config=mtp,adb
ro.secure=0
Thanks...
Edit:
On the SM-T813 I'll had the same problem, but I could resolved with the "heimdall print-pit". And the tablett reboot normaly. But I use the same command on the A10, nothing has been changed, the same result with the booting.
I did the same haha. It shows android but it booted
tiptel170 said:
Hi folks,
I had opened the bootloader for this device, the TRWP is starting fine. The partitions: product, boot and vendor is not modified, only the vbmeta has been changed, and also the recovery and the system.
I'm used the system file: lineage-17.1-20200402-UNOFFICIAL-treble_a64_bvN.img
The file I'll has flash with the command: heimdall flash --SYSTEM lineage-17.1-20200402-UNOFFICIAL-treble_a64_bvN.img, the flashing was successfully.
The SMA105 is booting, but after 10 minutes, the phone is stucking in the same boot logo. Nothing is happend, no steps for terminating the system installation. It seams, the SMA105 waiting for an command. But, I can not read an log file for the booting or switching of temporally the bootlogo.
Any solutions for me?
Greetings tiptel170
P.S.
Flashing other roms for example Viper etc ... This is the same effect. Wateing and wateing ...
Click to expand...
Click to collapse
Samsung Galaxy A10 has Lineage 17.1 custom rom (arm and arm64 versions)
You can download them here:
arm version
arm64 version
Note:
-> They will boot only with permissive selinux kernels (here)
-> It's a rom, not a gsi. It has it's own vendor.
-> You just need to flash the rom in recovery (twrp) , and then flash the permissive kernel.
Hello Chatur27,
I 'll had installed the system and the kernel. This is the same effect, stucks on booting. Then I 'll changed form arm to arm64 with the same kernel, it's the same result. And I used the twrp. And waiting more then 10min for the finish up the booting.
tiptel170 said:
Hello Chatur27,
I 'll had installed the system and the kernel. This is the same effect, stucks on booting. Then I 'll changed form arm to arm64 with the same kernel, it's the same result. And I used the twrp. And waiting more then 10min for the finish up the booting.
Click to expand...
Click to collapse
I will suggest you to stick to stock rom if you are not able to install a rom
Cheers!
I'm able to install roms on the Samsung phones / tablets. Something is missing, but it will not continua. And on this phone is not an stock rom installed, it's empty. I think I will be back to the stock rom and then reinstall the LOS 17. May be I' ll erased an part for booting. ;-)
Cheers.
Update:
I 'll had downloaded the firmware for this phone, then I extracted the packages in to the /tmp directory:
Code:
BL_A105FNXXU6BUC3_CL20057335_QB39107009_REV00_user_low_ship.tar
cm.bin.lz4
param.lz4
sboot.bin.lz4
And
Code:
CP_A105FNXXU6BUC3_CP18543320_CL20057335_QB39107009_REV00_user_low_ship.tar
modem.bin.lz4
Decompress the lz4 files:
Code:
cd /tmp
for lz4 in `ls *.lz4`; do unlz4 $lz4; done
Boot in to the download-modus and than I had flashed with heimdall
Code:
heimdall flash --CM cm.bin --PARAM param.bin --SBOOT sboot.bin --RADIO modem.bin
The RADIO partition is very important, if is not installed your SIM-Card wil not be detected and the mobil network will not work!
Reboot to the download-modus
And finally I had installed the twrp-3.5.2_9-0-a10.img.tar and vbmeta_disabled.tar:
Code:
heimdall flash --RECOVERY recovery.img --VBMETA vbmeta.img
Reboot again in this case in to the recovery mode:
Wipe
Code:
data
cache
And install this:
Code:
lineage-17.1-20200921-UNOFFICIAL-a10.zip
open-gapps
magisk-amager 20.4
And the phone will be start up normaly.
This system with this version works well, but:
- The battery runs out very fast - in an day is the battery at 9%
- Open files with WhatsApp, K9-Mail or simelar dose not work: The dialog open with an APP will be open very sohrt and cloed quickly, by WhatsApp crashed the window and restart the Whatsapp.
And this version of the lineage OS lineage-17.1-20210221-UNOFFICIAL-a10.zip
- Crashed the grafics, the screen goes withe, and then I need make an hard reset.
Need help for resolver the problem.
Thanks, tiptel170
Hello everyone.
I'm trying to compile from source the kernel of my phone which is an unlocked motorola g6 play codename aljeter with the stock rom (android pie). I found the kernel repository in this post https://forum.xda-developers.com/t/rom-r-v5-unofficial-aljeter-bananadroid-for-moto-g6-play.4362405/. I downloaded the toolchain in my case arm-linux-androideabi-4.9 because my phone architecture is arm.
Then i extracted the defconfig from the stock kernel obtained from the extraction of stock boot.img using AIK. After that i successfully compiled the kernel and i obtained the Image, zImage, and zImage-dtb. I unpacked the boot.img using AIK and i changed the boot.img-kernel with my zImage-dtb (and of course i renamed my zImage-dtb with boot.img-kernel). Then i repacked everything and i obtained a image-new.img. I rebooted my phone in fastboot mode and i run "fastboot boot image-new.img" to boot the new boot.img. After that the phone showed the boot logo but it immediately reboot to the stock boot.img (stock kernel). I think that the problem is related to avb but i am not sure.
Does anyone know how can i fix that?
Thanks
P.S
I also tried to compile the kernel for my tablet which is a Lenovo X606F but i obtained the same error