Hello
I have just bought a Cat S42 H+ with the following specs:
Android 10, planned upgrade to Android 11
Mediatek MT6761D Helio A20 (12 nm)
Quad-core 1.8 GHz Cortex-A53
PowerVR GE8320
I also run a Surface Go with PopOs (ubuntu linux derivative). I’m comfortable with using the terminal.
I have unlocked the Cat S42 using this tutorial: https://highonandroid.com/android-r…bootloader-on-any-android-android-root-101-1/
I have also installed the Treble Check app; the S42 supports Treble and also has VNDK 30.0. It also supports seamless system updates and has an A/B system partition.
What do I do next? There is no TWRP for my specific device. I was intending to install LineageOS for microG as the stock rom doesn’t support signature spoofing, which is requirement for microG. I just want this phone degoogled as much as possible.
Thanks
Related
So I'm having this discussion with a friend that states that you need 4GB of RAM or even more to run smoothly a 64-bit ARMv8 version of Android. So basically my question is:
Will 2GB of RAM be enough for, let's say, Android 6.0.1 ARMv8 64-bit version?
Consider ARMv8 64-bit version of Android consumes more RAM casue 64-bit apps and ROM's are larger, so more RAM is needed. The Nexus 5X has a Snapdragon 808, which is ARMv8 64-bit CPU.
Does the Nexus 5X have a 64-bit ARMv8 Marshmallow version or a 32-bit ARMv7 Marshmallow version?
what
sumantakhan said:
what
Click to expand...
Click to collapse
Well, if you don't know what a 64-bit android version is, or what ARMv7 is or ARMv8, then don't reply, lol.
pretty sure both the 5x and 6p are running 64bit android..
k.s.deviate said:
pretty sure both the 5x and 6p are running 64bit android..
Click to expand...
Click to collapse
Do you actually have the Nexus 5X?
Can you check this?
It's to check if it has Android ARMv8 64bit.
1. See if you have the folder "lib64" in "/system/lib64". I think you need root to access "system" folder.
2. Install an app called AIDA64 from Google Play and see if it reports you have 64-bit ARMv8 CPU in the tab CPU, Instruction Set.
3. Install and app called CPU-Z from Google Play and see if it reports you have AMRv8l in the tab System, Kernel Architecture.
If all these 3 points are checked and true, then you're running Android 64-bit using ARMv8 architecture. The apps are trusted and you can delete them once you've checked what I told you.
Thank you!
1. Yes
2. Yes
3. Yes
Edit. Added screenshots.
k.s.deviate said:
1. Yes
2. Yes
3. Yes
Edit. Added screenshots.
Click to expand...
Click to collapse
Thank you, thank you and thank you. You're awesome, did you know it?
rambomhtri said:
Thank you, thank you and thank you. You're awesome, did you know it?
Click to expand...
Click to collapse
Your welcome
It doesnt really work the way you are thinking...
freestylesno said:
It doesnt really work the way you are thinking...
Click to expand...
Click to collapse
Uh?
Well, I have an Android device with 2GB of RAM and a Snapdragon 615 ARMv8 64-bit and it basically has Vanilla Android 5.1.1.
One friend said 2GB of RAM was not enough for a 64-bit ARMv8 Android, so now that I know that the 5X can totally handle it, my smartphone should handle it as well.
My carrier is retard cause it installed a AMRv7 32-bit Android in it, and we're "pressing" it so it updates our phone to MM 6.0.1 ARMv8 64-bit. As I said, it's not a highly modified ROM, so it's practically pure vanilla MM.
Am I wrong in something?
Why?
freestylesno said:
It doesnt really work the way you are thinking...
Click to expand...
Click to collapse
Uh?
Well, I have an Android device with 2GB of RAM and a Snapdragon 615 ARMv8 64-bit and it basically has Vanilla Android 5.1.1.
One friend said 2GB of RAM was not enough for a 64-bit ARMv8 Android, so now that I know that the 5X can totally handle it, my smartphone should handle it as well.
My carrier is retard cause it installed a ARMv7 32-bit Android in it, and we're "pressing" it so it updates our phones to MM 6.0.1 ARMv8 64-bit instead of MM 6.0.1 ARMv8 64-bit.
As I said, it's not a highly modified ROM at all, so it's practically pure vanilla MM.
Am I wrong in something?
Why?
rambomhtri said:
Uh?
Well, I have an Android device with 2GB of RAM and a Snapdragon 615 ARMv8 64-bit and it basically has Vanilla Android 5.1.1.
One friend said 2GB of RAM was not enough for a 64-bit ARMv8 Android, so now that I know that the 5X can totally handle it, my smartphone should handle it as well.
My carrier is retard cause it installed a ARMv7 32-bit Android in it, and we're "pressing" it so it updates our phones to MM 6.0.1 ARMv8 64-bit instead of MM 6.0.1 ARMv8 64-bit.
As I said, it's not a highly modified ROM at all, so it's practically pure vanilla MM.
Am I wrong in something?
Why?
Click to expand...
Click to collapse
Why do you think that a 64bit version is bigger the a 32 bit version? Do you know what the difference even is?
ARMv7 and ARMv8 these are versions of the ARM processor architecture. Physically how it is made. You can only run software designed for your specific phone, in terms of roms and versions of Android. They need to be designed to work with the physical parts of the phones. Apps interact with android not directly with the processor.
"My carrier is retard cause it installed a ARMv7 32-bit Android in it, and we're "pressing" it so it updates our phones to MM 6.0.1 ARMv8 64-bit instead of MM 6.0.1 ARMv8 64-bit."
So this makes no sense you can't upgrade the processor with a software update. Your carrier does not build the phones it is done by the manufacturer.
freestylesno said:
Why do you think that a 64bit version is bigger the a 32 bit version? Do you know what the difference even is?
ARMv7 and ARMv8 these are versions of the ARM processor architecture. Physically how it is made. You can only run software designed for your specific phone, in terms of roms and versions of Android. They need to be designed to work with the physical parts of the phones. Apps interact with android not directly with the processor.
"My carrier is retard cause it installed a ARMv7 32-bit Android in it, and we're "pressing" it so it updates our phones to MM 6.0.1 ARMv8 64-bit instead of MM 6.0.1 ARMv8 64-bit."
So this makes no sense you can't upgrade the processor with a software update. Your carrier does not build the phones it is done by the manufacturer.
Click to expand...
Click to collapse
It's not about update my processor, it's about installing Android 64-bit so it can handle the ARMv8 64-bit CPU. Right now, with Android 32-bit, my Snapdragon is working obviously with ARMv7 32-bit.
Vulkan api flashable zip available for redmi note 3,is there anyway to get vulkan api for g4 plus such as flashable zip etc...?
I'm fairly sure vulkan libraries are a requirement for all official OEM 7.0 ROMs.
The ROM I'm currently on (Slim 7) has vulkan support.
negusp said:
I'm fairly sure vulkan libraries are a requirement for all official OEM 7.0 ROMs.
The ROM I'm currently on (Slim 7) has vulkan support.
Click to expand...
Click to collapse
There is no vulkan support for g4 plus as of yet rather there's no vulkan support for sd617 devices, however it won't make a huge difference.?
No other rom can support vulkan if it's not on official firmware
sriganesh.s said:
Vulkan api flashable zip available for redmi note 3,is there anyway to get vulkan api for g4 plus such as flashable zip etc...?
Click to expand...
Click to collapse
Unfortunately a ZIP with the Vulkan's API does not exists, because any Adreno 400 series GPU isn't (so far) officially supported, and we have Adreno 405.
The only CPUs officially supported are (Snapdragon 430, 625, 650, 652, 820, 821, 835), and they have Adreno 500 series GPUs (Adreno 510, Adreno 530, Adreno 540).
Theoricly, this CPUs: Qualcomm Snapdragon 415, 615, 616, 617, 805, 808, 810 are planned to be supported, all with Adreno 400 series, but i really doubt that this will happen someday... taking in count that they are "old" SoCs.
Hey Guys,
i have one question:
The Qualcomm Snapdragon 430 is a 64Bit CPU, but tools (specifically Xposed) says the system is ARM not ARM64 and the app AIDA64 says the command set is "64-bit ARMv8-A (32-bit Mode)".
So is the G5 running a 32Bit Android?
And could this be the reason why Xposed don't work?
(Only tested the arm zip file, not the arm64, rooted wit Magisk)
The g5 runs 32bit android
Xposed works fine - I used the Unofficial build from
https://forum.xda-developers.com/xposed/xposed-android-nougat-sdk-25-arm64-t3639221
However since I tested this a while ago the official nougat xposed has been released - according to one post Iv seen AICP rom thread that also works fine
Make sure you choose the correct sdk
Android 7.0 is sdk 24
Android 7.1 is sdk 25
TheFixItMan said:
The g5 runs 32bit android
Xposed works fine - I used the Unofficial build from
https://forum.xda-developers.com/xposed/xposed-android-nougat-sdk-25-arm64-t3639221
However since I tested this a while ago the official nougat xposed has been released - according to one post Iv seen AICP rom thread that also works fine
Make sure you choose the correct sdk
Android 7.0 is sdk 24
Android 7.1 is sdk 25
Click to expand...
Click to collapse
First of all: thank you for your answer.
I only tested the official Xposed and I took the correct sdk, but I got a bootloop on my Stock rom, so I don't know why it fails, probably because of Magisk?
Cubico said:
First of all: thank you for your answer.
I only tested the official Xposed and I took the correct sdk, but I got a bootloop on my Stock rom, so I don't know why it fails, probably because of Magisk?
Click to expand...
Click to collapse
Xposed doesn't always work with stock roms - you may need a custom rom - I only tested on lineageos
How to solve this problem: using arm32_binder64 treble gsi
I have A605K device, and on treble checker, it showed that i can install treble rom, but i can't get seemless update(it means i have to install a partitioned rom) so i tried many roms
uname -m -> aarch64
arch -> armv8l
i have installed arm64_a versions, but there wasn't anything working one, when i flashed system image and reboot, A6+ logo appears 6~8 second, and it reboots
i can't boot properly.. how can i fix this problem?
The only thing "unusual" with the A6+ is that it's a 64bits CPU running 32bits OS, with 64bits binder.
But that's standard in Android Pie.
So if you build pure AOSP GSI, you just use aosp_arm target.
For my GSI, that would be treble_a64_xxx (like treble_a64_avS-userdebug) target
DaanDH12 said:
The only thing "unusual" with the A6+ is that it's a 64bits CPU running 32bits OS, with 64bits binder.
But that's standard in Android Pie.
So if you build pure AOSP GSI, you just use aosp_arm target.
For my GSI, that would be treble_a64_xxx (like treble_a64_avS-userdebug) target
Click to expand...
Click to collapse
I want to know is, how can i fix boot errer? i want to use customized treble rom. Not building it. But i can't boot when i install treble. so i want to fix it.
same her
i have htc u12+
1- unlooked bootloder
2- flash TWRP
i know htc is AB 64bits but nothing working one
when i flash gsi.img i got message (flash complete ) but its just keep reboot device
pleas any help
The title pretty much, the pixel 6 and 7 support pKVM, which allows us to boot Windows 11 ARM or ARM64 Linux images in a virtual machine.
I saw somewhere that it either requires root to enable, or it must be enabled when the kernel is compiled, is it possible for this to work on the F3?
Interesting question.
I think we won't get pKVM-support, unless someone gets GKIs (Generic Kernel Images) working on Alioth (or perhaps more accurately, on the Snapdragon 870 sm8250).
Our device's 4.19 Kernel is too old, and doesn't have Rust-support, which I think is needed to run the crosvm VM Manager. It's part of Android 13's Virtualisation-Module, under the package-name "com.android.virt"
The Pixel 6 and 7 are running a much newer kernel, and it's GKI.
I don't know about pKVM-Support of other GKI devices. There could be more requirements for pKVM-support (besides arm64, GKI-based Kernel and Android 13).
Here are some articles I checked out:
How the Android 13 Virtualization module uses pKVM to boot virtual machines
Android virtual machines are changing in Android 13, here is everything you need to know about VMs in the newest version.
blog.esper.io
How to run a Linux VM on Android 13
Android 13 adds a virtualization feature. Here's how to use it to run Linux in a VM.
blog.esper.io
Android 13 DP1 allows Google Pixel 6 to run full-fledged Windows 11 as a VM
The Android 13 DP1 unlocks the full KVM functionality on the Google Pixel 6 and 6 Pro. You can now boot Windows 11 and Linux VMs on these phones.
www.xda-developers.com
Getting started with Protected Virtual Machines
https://twitter.com/i/web/status/1492754683445669893