[AOSP ROM] [OFFICIAL] | Android 14 | GSI Install Instructions for Galaxy Tab S6 (SM-T860, SM-T865)

[tablet_seeker]

i found a bug. if the audio player is on and the screen turns off, when you turn it on again the audio returns to 2 speakers only

What image are you using?

 

[peppet]

I've tried almost all of them. now fw stock

 

[tablet_seeker]

I've tried almost all of them. now fw stock

Did you install the recommended kernel? Everybody knows by now that the stable kernel fixes audio for AOSP 13 and 14.

 

[peppet]

yes I tried but despite downloading the indicated kernel I had a bootloop, I must have the wrong version. Could you link to exactly the right one? Thank you

 

[spiramedia]

Is there any "dex" desktop mode?

 

[Sage]

Is there any "dex" desktop mode?

No. Though check my post on GSI for the closest thing

 

[spiramedia]

No. Though check my post on GSI for the closest thing

can you give me a link? just i want a13 or a14 for installing windows 11 arm on virtual machine.​

 

[Sage]

can you give me a link? just i want a13 or a14 for installing windows 11 arm on virtual machine.​

[LineageOS 20] (Android 13) GSI Install Instructions

Hi all, i was kinda bored and sick of no Custom ROM development for our beloved S6 so i thought i'd try using a GSI and i've got it booting so i thought i would share the instructions! As usual all care no responsibility! Nothing here is...

forum.xda-developers.com

 

[Reonz]

can you give me a link? just i want a13 or a14 for installing windows 11 arm on virtual machine.​

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.

 

[fonix232]

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.

Please stop talking BS. APKMirror is ran by Illogical Robot LLC., a company created by Artem Russakovskii (aka ArtemR), a well respected Android expert and journalist. He's also the founder (albeit he does not work there anymore, as the site was sold) of Android Police.

As for your question... Yes, I've verified multiple APKs from there, and they're all intact, unchanged, and signed with the official keys. You can test this theory yourself, download an app from the Play Store, then try to install an APK update from APKMirror via ADB - if there was ANY kind of ****ery, the installation would fail due to different signing keys.


As for the work you've done on this tutorial, thank you. Albeit there are a few mistakes here and there:

• The S-Pen does not detect screen rotation properly, and gets stuck in portrait mode, making it quite useless (claiming that it "works" is a bit of an overstatement)
• Same goes for the touchpad on the official keyboard, exact same issue
• After installing the system, TWRP is removed
• It isn't just removed, but any subsequent flashing of TWRP will not be able to mount or access

  /data

  or Internal Storage, even through MTP. Ideally, one should not need to go through the whole process of reflashing the latest OEM firmware, then TWRP, then the system image, just to update/change the OS.
• Fingerprint reader is stated to be working ,however no AOSP image seems to recognise it.
• Hall effect sensor also seems to be bugged - the official keyboard does not wake the screen upon opening.
• Haptics/vibration seems to be VERY hit and miss. Even though it's enabled for e.g. keyboard and navigation and touches, I can only get it to vibrate when turning off.

On another note, just how possible/impossible would it be to get a "pure" Linux distro (e.g. Ubuntu, Arch, etc.) running on this tablet, in a GSI form?

 

[dodgebizkit]

This looks interesting, I very rarely if ever use any Samsung specific software so image try this after its had a bit more work on development - does the S pen still work as it does with the Samsung fw or does it work differently?

 

[arvin2212]

Failed to flash TWRP but this helped:

How to bypass KG State and/or RMM state prenormal

Hello Guys :) I want to tell how to bypass RMM state: prenormal to install TWRP Also this will resolve "Only official binaries are allowed" Disclaimer: I am NOT responsible for any damage done if you use my guide. It worked for me 100% and...

forum.xda-developers.com

 

[arvin2212]

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:

Artifacts

ci.android.com

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.

 

[arvin2212]

Sorry for the excess post. was supposed to edit the post.

 

[tablet_seeker]

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:

Artifacts

ci.android.com

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

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.

 

[arvin2212]

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.

Thank you for your reply.

I did..

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:

This is the boot.img that i used:

boot.img on branch aosp_kernel-common-android14-6.1 on target kernel_aarch64 at 10298368​

https://storage.googleapis.com/android-build/builds/aosp_kernel-common-android14-6.1-linux-kernel_aarch64/10298368/68a2e1a7b6bbb44c798c92dbf5fc6d67c883a54d3af6e8edd5bc99bf52d6426f/boot.img?GoogleAccessId=gcs-sign@android-builds-project.google.com.iam.gserviceaccount.com&Expires=1686397236&Signature=ikmm687R70V4S0y8/FKVNVCzomAuyaj2KwxZWpj18/5OZ3WA1O/WhEXXMNKg+7LXJz95gt45wlFVBjQ4lOrP6PVDjRawYw8qQQF4u8qTmLKxQEwAU/YUOpyCWBCJ8uJzZ74GoBzrZ30DRLJ2+GEFWR2YjVeGloCV01MIghEgoWmpYujnstFxFDyZ6Fp2oXEfJjkckMKgk1g1lZym4+mHEuYtsVelFnqI5VqMJI5NUgYepYY1ue3XBLfcqDRSlNeRyZNl1r2QusQIgMkSumnCuePBAzGXb0MZfFEI6ubwV7rDH3sMKnfOt7vbtb9xVhCGSeaXY3PLDAqYQqGLMDhP5g==

 

[tablet_seeker]

Thank you for your reply.

I did..

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 10298368​

https://storage.googleapis.com/android-build/builds/aosp_kernel-common-android14-6.1-linux-kernel_aarch64/10298368/68a2e1a7b6bbb44c798c92dbf5fc6d67c883a54d3af6e8edd5bc99bf52d6426f/boot.img?GoogleAccessId=gcs-sign@android-builds-project.google.com.iam.gserviceaccount.com&Expires=1686397236&Signature=ikmm687R70V4S0y8/FKVNVCzomAuyaj2KwxZWpj18/5OZ3WA1O/WhEXXMNKg+7LXJz95gt45wlFVBjQ4lOrP6PVDjRawYw8qQQF4u8qTmLKxQEwAU/YUOpyCWBCJ8uJzZ74GoBzrZ30DRLJ2+GEFWR2YjVeGloCV01MIghEgoWmpYujnstFxFDyZ6Fp2oXEfJjkckMKgk1g1lZym4+mHEuYtsVelFnqI5VqMJI5NUgYepYY1ue3XBLfcqDRSlNeRyZNl1r2QusQIgMkSumnCuePBAzGXb0MZfFEI6ubwV7rDH3sMKnfOt7vbtb9xVhCGSeaXY3PLDAqYQqGLMDhP5g==

Did you patch the legacy boot.img prior to flashing?
You need to extract that boot.img, copy only the kernel files and add them to your original boot.img. That's what you flash via TWRP.

 

[stuie1952]

Did you patch the legacy boot.img prior to flashing?
You need to extract that boot.img, copy only the kernel files and add them to your original boot.img. That's what you flash via TWRP.

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?

Many thanks

 

[Lehner82]

Are there any non source bugs ? Used GSI roms in the past and they had unstable Bluetooth with crackling here and there

 

[fonix232]

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?

Many thanks

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.