Related
I have been reading on how to compile android 4.0.3 and have my linux system all set up. I have a few questions before continuing.
From my understanding, there are a few components to a full working phone (please let me known where I am mistaken):
Bootloader
Radio(s)
Recovery
Kernel
Android OS
Gapps
What exactly is being compiled when I retrieve the source from google? My guess would be the recovery, kernel and android os. And the bootloader and radio are proprietary?
Where does one get the Gapps? Pulled from a stock phone maybe?
When flashing with
Code:
fastboot flashall -w
that erases cache and userdata, and it flashes the recovery, the kernel and the os?
What exactly is CWM doing when "installing from zip"? Is that pretty much a "fastboot boot ???"?
Once a developer compiles the source, how does he package it ready for CWM?
I don't intend to be a rom developer, but I love to tinker and I like to know what exactly is going on. It makes me a bit more comfortable flashing different roms if I know exactly what is going on in the system.
I'm no dev, although I'm compiling ICS as we speak just to tinker, as you put it. I believe its only the kernel and Android OS that is compiled from the Google source. Bootloader and radio are proprietary, like you said, and I'm not sure where the recovery comes from, but I know when I compiled from source on my OG Droid recovery wasn't included.
Sent from my Galaxy Nexus using Tapatalk
Install from zip runs a Recovery API that allows scripts to be ran to perform various tasks on the phone. You can extract and look at these update-scripts on packaged ROMs in the development section to get an idea.
I have experimented with different ROMs and two versions of TWRP, and have installed the fff bootloader. (I have two working cracked-glass KF's that I picked up cheap in addition to a like-new one, so I can try different ROMs, etc., at the same time.)
I had presumed until recently that the kernel was a part of the ROM that was locked in by the ROM developer. It appears, though, judging by the two lengthy threads about a kernel 3.0, that users can install different combinations of kernel and ROM.
Can somebody explain, or point to an explanation of, the relationship between a kernel and a ROM and how one installs a desired combination of the two? Can one install a new kernel over an existing ROM, install the kernel and then a ROM, or is it necessary to do something else, such as editing a .zip file before installing it?
I realize that if I were to read a few hundred messages in a few threads, I might come up with the answers myself, but I might also transition from being a still-coherent old guy to one with senile dementia before I got to that point. Aside from my personal needs, though, it seems that an explanation of this matter deserves to be someplace where it can be easily found.
The kernel is the main component of the operating system (ROM). The kernel is essentially the middle man between the applications and the processing being executed at a hardware level. Basically the kernel is the communicator between software and hardware.
With that said, ROM developers will use a specific kernel with their ROM. You are not locked in to use the kernel which came with "x" ROM. A new kernel can be installed. You want to make certain if you are using an ICS ROM you parallel it with an ICS kernel. If you flash an incompatible kernel that could be a problem. Some kernels work better with some ROMS. Different combinations produce different bugs. It's just a matter of tinkering until you find the combination which suits you best. Hash's latest 3.0 kernel (http://forum.xda-developers.com/showthread.php?t=1591850) is popular and seems to be mostly stable with the ICS ROMS for the KF.
Installing a kernel is just like flashing a ROM although you don't need to wipe anything. Just boot in to recovery and select the kernel you've downloaded.
Should the custom kernel be installed after the ROM? It would seem that that would be necessary if the ROM itself comes with a kernel, as it apparently does.
Also:
? Are both the kernel and the rest of the ROM installed into the system partition, /dev/block/mmcblk0p9? If not there, then where?
? Does the kernel include the compiled code for all the standard linux commands, or only the system-level ones? Does it include the Dalvik interpreter?
aarons510 said:
Should the custom kernel be installed after the ROM? It would seem that that would be necessary if the ROM itself comes with a kernel, as it apparently does.
Also:
? Are both the kernel and the rest of the ROM installed into the system partition, /dev/block/mmcblk0p9? If not there, then where?
? Does the kernel include the compiled code for all the standard linux commands, or only the system-level ones? Does it include the Dalvik interpreter?
Click to expand...
Click to collapse
1. boot.img
2. Kernel come with system calls, or API, the commands you mentioned is binutils (most popular is GNU's). In Android you can install busybox to get these commands.
Gửi từ Kindle Lửa của tôi qua Tapatalk 2
linktohack said:
1. boot.img
Click to expand...
Click to collapse
What part of my question is this an answer to? I'm guessing that it's meant to answer the questions in the third paragraph of my original post, but it's a bit cryptic, to say the least. I do want to confirm that the new kernel gets installed after the ROM is installed, if that is indeed the case.
2. Kernel come with system calls, or API, the commands you mentioned is binutils (most popular is GNU's). In Android you can install busybox to get these commands.
Click to expand...
Click to collapse
I just checked the version of ICS I have installed on one KF and the CM7 installation I have on another. On both of them, the system calls seem to be in /system/bin while the file manipulation and document processing commands are in /system/xbin. Most of the latter are, indeed, symlinks to busybox while many of the former are symlinks to toolbox.
So, when one installs a new kernel, is one just over-writing /system/bin and maybe other directories with a new set of system calls, or is something else going on? And where does the dalvik interpreter fit in? Is it part of the kernel, part of the ROM, or neither?
aarons510 said:
What part of my question is this an answer to?
Click to expand...
Click to collapse
I think he meant to tell you that the kernel is usually distributed as boot.img in the ROM zips.
aarons510 said:
I do want to confirm that the new kernel gets installed after the ROM is installed, if that is indeed the case.
Click to expand...
Click to collapse
The kernel is installed along with whatever ROM you install. Let's say you pick MadeUpRom and it features kernel #8 with it. You'd have to flash kernel #11 after installing said ROM.
aarons510 said:
So, when one installs a new kernel, is one just over-writing /system/bin and maybe other directories with a new set of system calls, or is something else going on? And where does the dalvik interpreter fit in? Is it part of the kernel, part of the ROM, or neither?
Click to expand...
Click to collapse
Kernels are installed to the boot partition, which is separate from the ROM's /system partition. Installing a new kernel will overwrite the existing one. For the dalvik, read this to understand it better: http://stackoverflow.com/questions/7541281/what-is-dalvik-and-dalvik-cache
aarons510 said:
What part of my question is this an answer to? I'm guessing that it's meant to answer the questions in the third paragraph of my original post, but it's a bit cryptic, to say the least. I do want to confirm that the new kernel gets installed after the ROM is installed, if that is indeed the case.
I just checked the version of ICS I have installed on one KF and the CM7 installation I have on another. On both of them, the system calls seem to be in /system/bin while the file manipulation and document processing commands are in /system/xbin. Most of the latter are, indeed, symlinks to busybox while many of the former are symlinks to toolbox.
So, when one installs a new kernel, is one just over-writing /system/bin and maybe other directories with a new set of system calls, or is something else going on? And where does the dalvik interpreter fit in? Is it part of the kernel, part of the ROM, or neither?
Click to expand...
Click to collapse
In Android world, a kernel is an image contains a Linux kernel and a ramdisk which is named *boot.img* and will be *write* (byte copy) to the boot partition.
A complete ROM is a singed zip file contains at least /system files and a kernel. When you flash a ROM, it will unpack and *copy* file of /system to the system partition (that's why we wipe the system partiton aka. factory reset before we flash a new ROM) then *write* boot.img to boot partition.
Usually, a kernel needs external modules, offen reside at /system/lib/modules, so developer create an *uncomplete* ROM, which contains only kernel and these external files. This flashable kernel looks like a ROM, but it's really small size compare to complete ROM.
Like I said above, files in /system/bin/ and /system/xbin/ is not related to kernel (boot.img). They are just binaries, compiled to use system calls that kernel (and modules) offer.
--- Dev only ---
System calls is not binaries, they are CPU interupt instructions. Your programs need to be compiled to call them.
In linux, system calls are called through interupt *0x80*
Q&A for [ROM][V500][5.0.x][CM12] Official CyanogenMod 12
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][V500][5.0.x][CM12] Official CyanogenMod 12. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
is there any way of getting MULTICAST enabled in the CM12 stock kernel?
axelander1 said:
is there any way of getting MULTICAST enabled in the CM12 stock kernel?
Click to expand...
Click to collapse
Yes, the first step is to submit a patch to gerrit. Is there a patch available?
Deltadroid said:
Yes, the first step is to submit a patch to gerrit. Is there a patch available?
Click to expand...
Click to collapse
I could probably create one.
Do you know which kernel config is used? is it one in https://github.com/CyanogenMod/android_kernel_lge_v500/tree/cm-12.0/arch/arm/configs ?
Is this even the kernel repo which is used for the cm12 nightlies?
axelander1 said:
I could probably create one.
Do you know which kernel config is used? is it one in https://github.com/CyanogenMod/android_kernel_lge_v500/tree/cm-12.0/arch/arm/configs ?
Is this even the kernel repo which is used for the cm12 nightlies?
Click to expand...
Click to collapse
This is the script that generates the config and moves it to arch/arm/configs/
https://github.com/CyanogenMod/android_kernel_lge_v500/blob/cm-12.0/make_defconfig.sh
Deltadroid said:
This is the script that generates the config and moves it to arch/arm/configs/
https://github.com/CyanogenMod/android_kernel_lge_v500/blob/cm-12.0/make_defconfig.sh
Click to expand...
Click to collapse
this file takes a parameter, I suppose awifi070u-perf_defconfig is used (see the other make script make_awifi070u_defconfig.sh).
However this has CONFIG_IP_MULTICAST=y.
I somehow doubt that this is the config which is actually used for the official builds. If I understand http://wiki.cyanogenmod.org/w/Build_for_v500 correctly, the command "breakfast v500" would pull the kernel repo and triggers make for the kernel's .config file?
Yes. You can also create a local manifest to pull a specific repo without having to pull everything.
Example:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="cmhub" fetch="git://github.com/CyanogenMod/" review="review.cyanogenmod.com" />
<project path="device/lge/v500" name="android_device_lge_v500" remote="cmhub" />
</manifest>
Example Procedure:
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.0
repo sync device/lge/v500
repo start my_fixed_branch device/lge/v500
cd device/lge/v500
<edit files>
git commit -a
repo upload device/lge/v500
---------- Post added at 12:23 AM ---------- Previous post was at 12:11 AM ----------
Just substitute "device" for "kernel" in the project path and name.
How do I know if I'm using hardware or software decoding for Netflix? No idea if I need your patch.
Also, I installed cm-12-20150226-NIGHTLY-v500.zip yesterday. Updated to cm-12-20150227-NIGHTLY-v500.zip with CyanDelta today, works like a charm. Thank you!
If you make a backup of /system/etc/media_codecs_google_video.xml then you can revert the patch. It only removes one line in that xml file so that adaptive playback is not an option for h264 decoding. The only difference is that hardware decoding should save on the battery. This patch was taken from slimRom and I need it for other devices, so I thought it would be worth testing for this device also.
Hi everyone, I am on 28\02 nightly and Google Now doesn t work, showing "Network error. Check your network connections".
Does anyone knows how to solve it?
It's working here. Either the Google services is temporarily down in your area or you need to install the correct version of gapps. The "Delta" gapps that I have posted in the development section are up to date and working.
cm12 crashes after flashing
Everytime I flash cm12 it fails. I get into the setup process, login to wifi' cyanogenmod, and google. I never get passed this. During setup I get messages that say "unfortunately there is a problem with music", then the same for camera. Then the screen stars flashing and eventually goes dark. The back key shows at the bottom, but the other two do not show. The back key is nonresponsive. I have to power down and get back to recovery and restore my cm11 backup.
When I got the gpad, it came with 20D, andI had to use the lgflashtool to get back to 4.2.2. (20A0. Then I rooted with stump and installed twrp using flashify. Then I was able to flash cm11 (m10, 11 and 12). Cm11 ran like a champ.
A couple of weeks ago I decided to flash a cm12 nightly and had the problem described above.
I have tried multiple combinations of steps to solve this problem: going back to 4.2.2, rooting and flashing cm12 from 4.2.2, I have tried 4.4.2. I have tried multiple versions of twrp and philz. I have wiped with and without wiping system. I have tried different versions of gapps-lp. I have tried different versions of the nightlies.
Every time I get the same result (which I think is the definition of insanity).
What is most frustrating is that I have another gpad that went from cm11 to cm12 with no problems. Worked the first time using the 0217 nightly,
So what am I doing wrong? Why am I having problems with cm12 after I flash it?
Thanks in advance. Xda has been a life saver since I got my first tablet, a viewsonic, a few years ago.
John
It sounds like you know the procedure of installing CM because one of your devices works fine. There seems to be a difference between your two devices. Have you looked at the thread for "back cam fix" in the development section to find out how to check which camera module your device has? Maybe one of your devices has a different camera module than the other (which requires other camera drivers). Although, the device should still function with cm12 even if your camera module is unsupported.
Also, make sure you format the cache, Dalvik cache, and system partitions in addition to a factory reset before flashing from your internal sdcard.
Still can't set up CM12
Deltadroid said:
It sounds like you know the procedure of installing CM because one of your devices works fine. There seems to be a difference between your two devices. Have you looked at the thread for "back cam fix" in the development section to find out how to check which camera module your device has? Maybe one of your devices has a different camera module than the other (which requires other camera drivers). Although, the device should still function with cm12 even if your camera module is unsupported.
Also, make sure you format the cache, Dalvik cache, and system partitions in addition to a factory reset before flashing from your internal sdcard.
Click to expand...
Click to collapse
Thanks for the suggestions. I first checked the camera.
While in CM11 I turned on the camera and took a picture. I also opened a terminal window and grepped both the OV and the S5K cameras. Nothing came back for OV. I did get stuff from S5k. So I assume the camera is the right one.
Then I did went into recovery, carefully wiped and formatted, and flashed CM12 and Gapps.
I am still getting the camera and music errors. Then the screen flashes to black and the it locks.
The bad news is that I cannot get back to recovery. It looks like I'm back to the lgflashtool.
I will try again from stock. But right now I think it is miller time.
Yeah, if it was working on cm11 then your camera is supported.
Maybe going back to latest stock Rom with lg tool would help fix any unknowns. Instead of flashing the 10a firmware, stay on 20d stock and just replace aboot so you can install a custom recovery. Next, install cm12 with red kernel or mani kernel to support your stock 20d 4.4.2 firmware.
Are you sure you did wipe SYSTEM before flashing?
Still can't set up CM12
Deltadroid said:
Yeah, if it was working on cm11 then your camera is supported.
Maybe going back to latest stock Rom with lg tool would help fix any unknowns. Instead of flashing the 10a firmware, stay on 20d stock and just replace aboot so you can install a custom recovery. Next, install cm12 with red kernel or mani kernel to support your stock 20d 4.4.2 firmware.
Click to expand...
Click to collapse
No cigars yet! Same error with camera and music then screen locking.
I found an XDA tool called Original LG Firmware.exe. It allowed me to download V50020d_00.kdz.
I used LGFlashTool2014 to install.
I used Stump to get Root.
I downloaded SuperSU and Flashify to set up recovery.
Recovery failed. It didn't think I was rooted.
I used another tool, LGGPabRecoveryTWRP 2.8(BypassBootloader).apk to resolve this problem
I installed CM11-M12.
Then I went to recovery to install CM12, gapps, and red kernal.
The first attempt used the 0305 nightly. It hung on the flash.
I forced a power down and manual reboot into recovery.
Did all the wiping and tried the 0217 nightly. The flash was successful but as it initialized, CM12 crashed and burned again.
I'm beginning to believe I have a poltergeist in this gpad.
johnseidel said:
No cigars yet! Same error with camera and music then screen locking.
I found an XDA tool called Original LG Firmware.exe. It allowed me to download V50020d_00.kdz.
I used LGFlashTool2014 to install.
I used Stump to get Root.
I downloaded SuperSU and Flashify to set up recovery.
Recovery failed. It didn't think I was rooted.
I used another tool, LGGPabRecoveryTWRP 2.8(BypassBootloader).apk to resolve this problem
I installed CM11-M12.
Then I went to recovery to install CM12, gapps, and red kernal.
The first attempt used the 0305 nightly. It hung on the flash.
I forced a power down and manual reboot into recovery.
Did all the wiping and tried the 0217 nightly. The flash was successful but as it initialized, CM12 crashed and burned again.
I'm beginning to believe I have a poltergeist in this gpad.
Click to expand...
Click to collapse
The reason your recovery failed is because your 20D firmware has an aboot.img that is not loki exploitable. After rooting, you will need to replace your aboot.img with the aboot.img from 10A firmware. This means you are keeping the 20D bootloader but only downgrading the 10A aboot.img so that you can use the loki tool to install a custom recovery. Flashify also needs a loki exploitable aboot.img (10A) to be installed before it can work and install a lokified recovery. The trick is to keep your new bootloader from 20D but only downgrade the aboot.img. There is a batch file in the development section that does this with a script using the dd command.
Okay.
20D is flashed and rooted.
V50020_aboot_twrp_v2 has been executed.
Flashify flashed TWRP 8.0.0.0 and rebooted.
I am assuming the next step is to flash CM12, but wanted to make sure. I've shot myself in the foot so many times I'm running out of toes.
Next, factory reset, and format /system. You could also format your internal sdcard, but it's not often necessary.
Finally, install latest nightly build of cm12. You can install gapps later.
---------- Post added at 02:45 AM ---------- Previous post was at 02:36 AM ----------
Note, make sure you copy the files to your sdcard first if you plan on formatting the internal sdcard.
I was wondering if their is an additional step to flashing files from github
Other then download and flash? Every file I get from github fails with a wrong zip file format error.
Are those files just a repository for builds and not for flashing in twrp?
Or do they need to be rezipped or some other additional step?
For instance-
I. Tried to download
https://github.com/exynos5420/android_kernel_samsung_exynos5420
And flash, in an effort to get full functionality from deathly auditor.
Same result.
So if anyone at all can clear this up for me I would greatly appreciate it.
Than you in advance.
Tchk856 said:
I was wondering if their is an additional step to flashing files from github
Other then download and flash? Every file I get from github fails with a wrong zip file format error.
Are those files just a repository for builds and not for flashing in twrp?
Or do they need to be rezipped or some other additional step?
For instance-
I. Tried to download
https://github.com/exynos5420/android_kernel_samsung_exynos5420
And flash, in an effort to get full functionality from deathly auditor.
Same result.
So if anyone at all can clear this up for me I would greatly appreciate it.
Than you in advance.
Click to expand...
Click to collapse
You cannot flash anything from Github.its a repository mainly for source code. Any zip you download is simply an archive containing source code.
You can either compile the source yourself of just find the relevant thread on XDA where the precompiled kernel will be.
Ty for the info.
So I got this kernel file
https://www.androidfilehost.com/?fid=4996500813288309548
And tried to flash it in twrp, it says it succeeded, enjoy your kernel, but it doesn't take.
This is what I'm running now, iron rom with iron kernel.
Tchk856 said:
So I got this kernel file
https://www.androidfilehost.com/?fid=4996500813288309548
And tried to flash it in twrp, it says it succeeded, enjoy your kernel, but it doesn't take.
This is what I'm running now, iron rom with iron kernel.
Click to expand...
Click to collapse
You can't just flash any kernel to any device. That's not even intended for your device so will not work.
ok thx again
Idk if I should start a new post for this or not.
How can I figure out which kernels are appropriate for which roms?
What this basically boils down to is I really like deathly auditor, so to get full functionality
I need that kernel installed, plus that kernel seems to run very very well on my device.
So I would like to run an OS that's MM or newer, and that's touchwiz based,
(I think that's what it's called when they leave most of the Samsung apps on it),
So that my samsung gametuner, gametools, and other Samsung apps work.
If I could get the game service app to work on any of the roms that have the deathly kernel I would
Just use one of those roms.
Here's a screens shot of the app.
I believe it's called "game optimizing service"
If anyone could help I would greatly appreciate it, ty in advance.
Hi guys,
I know custom ROMs are made of AOSP. However, it's not very clear to me why do they also have lower quality signal compared to stock ROMs. In the same area where I usually got 4G (not great signal, but still 4G), now I only get 3G.
Is there a reason for this? Aside from "it's not made by the manufacturer". Yeah, I know that, but why exactly isn't the same quality...? What makes it slightly worse?
Also, is there anything can do to improve reception?
arsradu said:
Hi guys,
I know custom ROMs are made of AOSP. However, it's not very clear to me why do they also have lower quality signal compared to stock ROMs. In the same area where I usually got 4G (not great signal, but still 4G), now I only get 3G.
Is there a reason for this? Aside from "it's not made by the manufacturer". Yeah, I know that, but why exactly isn't the same quality...? What makes it slightly worse?
Also, is there anything can do to improve reception?
Click to expand...
Click to collapse
Exactly what you said: "It's not made by the manufacturer". Proprietary blobs are extracted from the device, creating vendor image while building AOSP and modifying vendor partition it when installing a zip.
I don't think there's anything to improve, until someone makes a kernel or a vendor image.
(flashing original vendor lead to bootloop on my phone, probably because encryption?)
However, you can try downloading stock ROM and flash stock vendor, but make sure to not have your device encrypted (I did not try on a non-encrypted device).
georg3_ said:
Exactly what you said: "It's not made by the manufacturer". Proprietary blobs are extracted from the device, creating vendor image while building AOSP and modifying vendor partition it when installing a zip.
I don't think there's anything to improve, until someone makes a kernel or a vendor image.
(flashing original vendor lead to bootloop on my phone, probably because encryption?)
However, you can try downloading stock ROM and flash stock vendor, but make sure to not have your device encrypted (I did not try on a non-encrypted device).
Click to expand...
Click to collapse
I've noticed this with stock ROMs as well, when they weren't dedicated for that specific region... So...I'm guessing it's probably the same here. AOSP includes some files to make the ROM work...but not dedicated files for each region.
By the way, can you please, guide me how should I do this? It's been a really long time since I've done stuff like this. Android has changed a lot.
I already have the ROM at hand, downloaded via RSA. But it's Android 11, since that's the last ROM that Motorola released for this phone.
So that part is done. What next? )
Also, any idea if this method should also bring back VoLTE and VoWIFI? Or it's not that simple?
arsradu said:
I've noticed this with stock ROMs as well, when they weren't dedicated for that specific region... So...I'm guessing it's probably the same here. AOSP includes some files to make the ROM work...but not dedicated files for each region.
By the way, can you please, guide me how should I do this? It's been a really long time since I've done stuff like this. Android has changed a lot.
I already have the ROM at hand, downloaded via RSA. But it's Android 11, since that's the last ROM that Motorola released for this phone.
So that part is done. What next? )
Also, any idea if this method should also bring back VoLTE and VoWIFI? Or it's not that simple?
Click to expand...
Click to collapse
EDIT: Newer OS than vendor shouldn't make a problem.
Newer vendor than OS does.
Extract the ROM, there should be vendor.img in there, and there are 2 methods for this:
1. TWRP method
Install, Install Image, select your vendor image set it to flash as vendor image, and swipe to flash.
2.Fastboot method
Open a terminal/command prompt in the extracted ROM folder, and type
Code:
fastboot flash vendor vendor.img
That should do it.
georg3_ said:
Older OS than vendor shouldn't make a problem.
Older vendor than OS does.
Extract the ROM, there should be vendor.img in there, and there are 2 methods for this:
1. TWRP method
Install, Install Image, select your vendor image set it to flash as vendor image, and swipe to flash.
2.Fastboot method
Open a terminal/command prompt in the extracted ROM folder, and type
Code:
fastboot flash vendor vendor.img
That should do it.
Click to expand...
Click to collapse
Alright. So....I can't use Android 11 vendor, extracted from stock ROM, if I'm currently on PixelExperience based on Android 12, right?
arsradu said:
Alright. So....I can't use Android 11 vendor, extracted from stock ROM, if I'm currently on PixelExperience based on Android 12, right?
Click to expand...
Click to collapse
Stau bine pe engleza daca e )
I translated it wrong, i meant it would be fine to flash it
Buun. Thank you, kind sir. Will try it then and let you know.
georg3_ said:
Stau bine pe engleza daca e )
I translated it wrong, i meant it would be fine to flash it
Click to expand...
Click to collapse
I'm getting bootloop, too...
I tried to flash the rom, flash Disable_Dm-Verity_ForceEncrypt.zip (should disable encryption...unless I'm missing something). But after flashing vendor.img from stock Android 11, I can't boot anymore. I also tried wiping data after that, but no luck.
arsradu said:
I'm getting bootloop, too...
I tried to flash the rom, flash Disable_Dm-Verity_ForceEncrypt.zip (should disable encryption...unless I'm missing something). But after flashing vendor.img from stock Android 11, I can't boot anymore. I also tried wiping data after that, but no luck.
Click to expand...
Click to collapse
Probably not an encryption related issue, guess we can't fix anything.