that is unlikely to happen because normal snapdragon soc don't allow pKVM etc.etc virtualization from factory, some machines come with Windows on ARM and still without virtualization support, e.g. Huawei Matebook e (snapdragon 850), while in fact 850 support VM, but it can't be turn on after being manufactured.
The crucial difference being that all the code you mentioned is 100% Open Source. It is developed, inspected and verified by large communities of FOSS contributors.
With the exception of Odin, but I'd personally recommend Heimdall anyway.
APKMirror offers no such transparency. You have to manually extract and decompile their files in order to check the source code, which is undoubtedly changed.
Obviously, you'll appreciate the massive disparity in security and transparency when comparing some website to established open source projects.
This happens when you don't flash the vbmeta tar in the correct slot with TWRP. Please make sure to follow the OP exactly. It's extremely detailed on purpose, so that everyone with the same device will have the exact same outcome.Hi,
I tried installing the latest version of Android 14, and also the beta version of Android 13 in this guide. Tried a few different GIs but the top speakers did not work for all.
I then tried flashing the latest version of Android 14 and also flashed the latest kernel here:
But when i do flash the kernel (flashed as boot) after flashing the system image (flashed as system) it results in a error that takes me to the donwload screen.
Need help on how to download and flash the kernel..
* I tried crDroid as well , and enabled the alternate audio for both samsung and qualcom, and enabled wide hall as someone mentioned here, but it made no difference. The top speakers did not work * which makes me assume that the issue is not fixed with the roms but the kernel.. tried all the builds that are on android 14 and everything that was said to have solved the speaker issue but none worked. My kernel is still the old kernel that came with the stock rom.
View attachment 5929301
Did you patch the legacy boot.img prior to flashing?Thank you for your reply.
TWRP in the AP , and vbmeta in the CP right?
Flashing any android build works fine with that. I can boot in AOSP and different roms without any error.
The error only occurs (as shown in the pic above) when I flash the kernel (boot.img).
This is how it looks like before flashing:
View attachment 5929923
This is the boot.img that i used:
boot.img on branch aosp_kernel-common-android14-6.1 on target kernel_aarch64 at 10298368https://storage.googleapis.com/android-build/builds/aosp_kernel-common-android14-6.1-linux-kernel_aarch64/10298368/68a2e1a7b6bbb44c798c92dbf5fc6d67c883a54d3af6e8edd5bc99bf52d6426f/boot.img?GoogleAccessIdfirstname.lastname@example.org&Expires=1686397236&Signature=ikmm687R70V4S0y8/FKVNVCzomAuyaj2KwxZWpj18/5OZ3WA1O/WhEXXMNKg+7LXJz95gt45wlFVBjQ4lOrP6PVDjRawYw8qQQF4u8qTmLKxQEwAU/YUOpyCWBCJ8uJzZ74GoBzrZ30DRLJ2+GEFWR2YjVeGloCV01MIghEgoWmpYujnstFxFDyZ6Fp2oXEfJjkckMKgk1g1lZym4+mHEuYtsVelFnqI5VqMJI5NUgYepYY1ue3XBLfcqDRSlNeRyZNl1r2QusQIgMkSumnCuePBAzGXb0MZfFEI6ubwV7rDH3sMKnfOt7vbtb9xVhCGSeaXY3PLDAqYQqGLMDhP5g==
Thanks to the OP for all his efforts on this project. It is quite a job to respond to the myriad queries and questions and remain calm, cool and collected at the same time.
Standard Android boot.img's are actually a combination binary of an ELF standard kernel image, and an initrd file. Presumably, there are some device-specific init sequences in that initrd, hence why you can replace the kernel image itself, but still need to repack the boot.img.Thanks to the OP for all his efforts on this project. It is quite a job to respond to the myriad queries and questions and remain calm, cool and collected at the same time.
My question relates to the above statement.
Please correct me if i am wrong but as i understand it the boot image is an executable and does not contain kernel files that can be accessed. I would therefore be grateful if you could clarify the above statement for me. My understanding is that i need to use the patched boot image, not the original. Is there more to it than that?
Of course it refuses to do so, a boot.img, as I've already explained a number of times in this thread, is NOT a file system, therefore can't just be mounted. What you're looking for is mkbootimg, a tool made by Google to create (and in some ways, unpack) the boot.img files according to the format.
Hi there! Yes, top speakers are an issue without the latest kernel. You need to reflash your boot.img with the latest mainline kernel. You can find the instructions in the OP.Hey there, I gave the guide a try and have the latest ponces PE+ image (https://github.com/ponces/treble_build_pe/releases/tag/v2023.08.21-plus) working mostly fine on my SM-T860, but even with the specific phh settings enabled, I can't get the top speakers working; only the bottom ones.
I have enabled:
Qualcomm - alternate audio
Samsung - alternate audio, enable stereo audio
Misc - enable system wide BT HAL
I've tried every combination of those settings enabled and disabled, and it doesn't do anything for me. Any ideas?
Yes, I get the vbmeta error too after flashing a new kernel. You just have to reflash vbmeta. I also flashed a new GSI and wiped system, dalvik/cache before that, not sure if that's related.I managed to get it to boot once using that kernel, but as soon as I reboot after first boot, I end up on the download screen overlaid with an error message about being unable to verify vbmeta.
Either way, the kernel you linked didn't seem to fix the speaker issue, even with those specific phh settings enabled. Any advice?
The error at the beginning is expected, but nobody else has reported any major stability issues so far.