-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can I use this on rooted Galaxy Tab S9 Ultra #24
Comments
Try slbounce? |
slbounce won't work on SD8G2 because hypervisor does not support secure-launch feature. |
SD8G2 (SC8180XP) boots WoA, though. So... thats what's needed for slbounce. At least worth a try. I have a Volterra running on EL2 this way. |
SD8G2 here is SM8550 Mobile Platform, not SC8180XP or 8cx gen2 Compute Platform... On this topic, you can not replace hypervisor on your phone because it need qcom's signature. You can use Qemu to run it on your rooted Galaxy Table S9 Ultra. |
Thanks for pointing that out, my bad. |
Thanks for clarifying! So the only option currently available for SM8550 is to compile the kernel with KVM support and use QEMU? |
Sorry i'm not sure with crosvm... |
Unfortunately I cannot help but I would like to second this issue. I am trying to enable either KVM or Gunyah on my Galaxy Tab S8 Ultra to be able to run Windows on Arm virtual machines with hardware acceleration. |
Upon looking at the Galaxy Tab S8 kernel source code, it seems KVM and Gunyah are enabled in the GKI (General Kernel Image), however I am receiving many errors when trying to compile the unchanged source code of the kernel using the provided materials. I will let you know if I am able to flash the GKI successfully and be able to use KVM. |
I have a Tab s9 and on the stock kernel I tried this in root shell via termux
Still debugging, but so far looks like its having trouble starting the kernel or crosvm is having issues with gunyah. Will update |
I was still never able to get a kernel image working. Each time a boot loop appeared. Perhaps I need to factory reset the operating system before installing a kernel. I think KVM maybe able to work as it is enabled in the GKI |
I tried the android13-5.15 GKI and it worked, higher versions didn't boot. But still didn't see a /dev/kvm. So I think we only have gunyah for now, which is fine as they seem to have done everything needed for it to be in AVF and work with crosvm too. I think the error is actually related to the kernel image I am using to start crosvm, will dig more and keep you posted. A description of my setup:
Update:
|
I downloaded the open source Android 14 kernels for the Tab S8 Ultra from Samsung's website and tried to compile it but my tablet went into a boot loop, so I had to revert back to the previous kernel. I'm just running stock firmware, rooted by Magisk, alongside the stock kernel, which is Android 12. |
Tried Looks like this is where the below error comes from i.e when crosvm tries to use gunyah
Not sure how to resolve this. Would really appreciate your help @quic-cvanscha . Ty! |
https://issuetracker.google.com/issues/280625917 |
I could never do that! I love my tablet too much haha. I'll figure out some way to enable such soon. |
Have you tried with the 6.1 Update? |
hi need help on samsung s9 ultra to format manual remove lock can someone help |
it doesnt work for me, i tried on SD8G3 with oneplus 12, the kernel version is:
tried run QEMU got these error
looks like doesnt work anymore |
I got really excited and hopeful, as I was just reading about Gunyah, prior to finding this issue thread and thought I may be able to use Gunyah on my unrooted Samsung Galaxy Tab S9 Ultra, to provision a VM and run Docker. Though, this I understand from this thread is a mere pipedream. The only solution I have so far been able to determine, is to provision a VM on a local or remote server and mount the VM locally in a project directory on the Tab. Then, it is possible to use Docker on the Tab, when not using Docker on the Tab, by mounting the remote VM locally on the Tab, through the project directory, which acts as a portal. To seal the deal, I get to enjoy the privilage of my local environment and shell config. Any other solutions? |
Note that gunyah open sourced here does not have support for running on a commercialized phones/tablets. Also we are working on fixing the build related issues since other related software versions have changed.
Thanks
Yug
From: b9Joker108 ***@***.***>
Sent: Friday, October 18, 2024 8:46 AM
To: quic/gunyah-hypervisor ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [quic/gunyah-hypervisor] can I use this on rooted Galaxy Tab S9 Ultra (Issue #24)
WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
I was just reading about Gunyah, prior to finding this issue thread and thought I may be able to use Gunyah on my unrooted Samsung Galaxy Tab S9 Ultra, to provision a VM and run Docker. Though, this I understand from this thread is a mere pipedream. The only solution I have so far been able to determine, is to provision a VM on a local or remote server and mount the VM locally in a project directory on the Tab. Then, I can use Docker on an untooted tablet.
—
Reply to this email directly, view it on GitHub<#24 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A32MLWBDZLJ7VMOCH4HLRS3Z4EUL3AVCNFSM6AAAAABDC5DTX6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRSG43DIMJQHA>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>
|
How root my Motorola g14 on termux cli? |
The CPU is Snapdragon 8 Gen 2 and the Tab S9 Ultra has 16 GB of memory. I am trying to find ways to use this device to run VMs. I would like to use Gunyah but I don't know how to install it.
The text was updated successfully, but these errors were encountered: