How do I fit a custom recovery into a ramdisk for sailfish?
Related
Does anyone know if there is a flashable twrp or cmr zip for JB (cyanogen mod 10 v2)
Also is there clockwork mod touch for our device yet?
I've tried to use my twrp installer with the latest ics kernels and it doesn't seem to work anymore. It complains about the ramdisk not being gzipped with boot.img.
I'm sure that if you ask Erik nicely he'll compile a twrp kernel since twrp 2.4 has a patch that allows for the creating of bml_over_mtd for roms that need them like roms for our phone. Luckily this doesn't require anything more than including the latest twrp2.4 tree from teamwin's github and placing it under bootable/recovery, then you can just run mka bootimage and get a twrp boot.img that way.
The idea is to have only one partition that contains the boot and the recovery at the same times!
Why ?
I a previous thread, I have an issue with the touch panel when I boot into recovery : the kernel detect the recovery mode and disable the touch, not good at all for TWRP
If we merge the boot and recovery images in the same image (say bootReco.img) and flash the result merged image in the boot partition (fastboot flash boot bootReco.img), the kernel detect that we are in the boot partition and will not disable the touch.
The boot.img and recovery.img uses the same kernel (duplicated in each partition), only the ramdisk is different for each partition.
So the only things to merge are the 2 ramdisks.
In the boot, we have only to add a menu that ask for normal boot (default behavior) or the recovery (inside the same boot partition)
Any idea please ?
dreambo said:
The idea is to have only one partition that contains the boot and the recovery at the same times!
Why ?
I a previous thread, I have an issue with the touch panel when I boot into recovery : the kernel detect the recovery mode and disable the touch, not good at all for TWRP
If we merge the boot and recovery images in the same image (say bootReco.img) and flash the result merged image in the boot partition (fastboot flash boot bootReco.img), the kernel detect that we are in the boot partition and will not disable the touch.
The boot.img and recovery.img uses the same kernel (duplicated in each partition), only the ramdisk is different for each partition.
So the only things to merge are the 2 ramdisks.
In the boot, we have only to add a menu that ask for normal boot (default behavior) or the recovery (inside the same boot partition)
Any idea please ?
Click to expand...
Click to collapse
Why not just build a kernel that does not do the unwanted behavior and flash that? Seems like it would be much easier to me.
wildermjs8 said:
Why not just build a kernel that does not do the unwanted behavior and flash that? Seems like it would be much easier to me.
Click to expand...
Click to collapse
You are right, but I do not have the kernel sources, the vendor of the phone MAZE Alpha does not provide that.
Can any one help me to have the kernel sources ?
The SOC is MT6757D by Mediatek, who must provide this sources, Mediatek or MAZE ?
HI everyone i need your help to develop a kernel with adhoc support for gt s7270(logan)
I followed the instruction:
1) I downloaded the kernel from the repo in git hub
2) I do the modifications in broadcom wifi driver to support adhoc mode
3) I compiled the kernel for my device and now i have the zimage.
Now because i do not how to create a ramdisk image I take the zip of rom(cm11) and decompresed the boot.img and split into ramdisk and zimage.
Now i ovewrite the zimage, and i repack the boot img, all this I did with the application that I found in xda(https://forum.xda-developers.com/showthread.php?t=2319018)
Now when i flashed the zip that constains the new zimage i get a boot loop. Can you help me and tell what i did wrong?
Hey folks,
I have rooted (magisk) OnePlus 8 phone with Android 11, w/o TWRP recovery. I'm trying to replace kernel with one of blue_spark, here's what I'm doing
1. Download zip file from https://github.com/engstk/op8/releases/tag/r112
2. Extract and unpack Image.gz
3. Unpack Magisk patched boot.img to /tmp (magiskboot unpack boot.img)
4. Replace kernel with unpacked Image (cp Image /tmp/kernel)
5. Repack boot.img (magiskboot repack boot.img boot-new.img)
6. Boot with boot-new.img (fastboot boot boot-new.img)
And here is when I'm getting into "QUALCOMM CrashDump Mode"
The same result if I build kernel from sources. Repacking boot.img with original kernel works, so problem is unlikely in magiskboot.
I'm trying to figure out the problem, but without kernel logs it's troublesome. Any ideas?
Thanks.
Hm... It looks like, I also have to update DTB. After that device boots successfully. Seems a bit strange to me. What's the difference in supported devices between blu_spark and stock kernel?
Ok, turned out AVB was enabled in the original device tree:
fsmgr_flags = "wait,slotselect,avb";
Switching it off fixes boot process.
It was modified from latest stock kernel of WearOS 2.
Features:
[OC] Overclocked to 1.8Ghz
[Magisk] Magisk v23.0 pre-installed
How To Use :
Reboot to fastboot
You are supposed to try it first in order to make sure it is suitable to your system by using
Code:
fastboot boot boot.img
If your test is passed, you could input the command below to flash it
Code:
fastboot flash boot boot.img
Enjoy
Download Link: MEGA
Cannot get it to work on my W200, stuck on LG logo and heating up considerably
Xspeed said:
Cannot get it to work on my W200, stuck on LG logo and heating up considerably
Click to expand...
Click to collapse
Sorry for having forgotten that the fstab in the ramdisk was modified in order to support the system partition which had been formatted to ext4 by myself.
You could use magiskboot to edit the boot.img by yourself. Just replace the kernel and kernel_dtb by the one unpacked from the stock boot.img and then repack the image file.
Prebuilt magiskboot can be checked here: https://github.com/TeamWin/external_magisk-prebuilt/tree/android-11/prebuilt
If available, I will reupload the correct version in several month.