yashsingh1/xdaforums huggingface dataset:
[ASUS ROG Phone II Questions & Answers] king_scourge1987:
How can I do this when the phone will not even turn on?

On a side note I doubt it will work even if I connect my phone charger to this side port, assuming that my phone is actually out of juice..
[ASUS ROG Phone II Questions & Answers] FluffyPants:
Asus Qualcomm
[Off-topic] AkoreJepade:
I have been searching endlessly online for an application that will let me modify a photo that I have of a house to make changes to it to see what it would like when the construction is completed. Most apps I have found and downloaded only let you do interior design or make changes like new doors or windows or paint color of the outside. I need something that lets me remove outside stairs from the house, build a section of flooring to the second floor, add a new roof etc. Does such an app even exist?
[Off-topic] user0u:
It would have to be some next level ultra smart app to do that. I mean how would it know where your stairs, floor, furniture, etc are and tell them apart accurately? You would at least need to define them and in the process end up doing what those other apps you mention already do.

To achieve what you want you will need to create a model of your house from scratch in something like SketchUp.
[Off-topic] AkoreJepade:
It would know where the stairs are by looking at the photo I import into the app. I am not talking about anything on the interior like furniture or floors or stairs on the inside of the house. These are steps installed on the outside of the house that I want to remove from the photo and make other design changes. There are tons of apps for interior designs but I am looking for an app that does exterior design changes to the actual structure of the house.
[Off-topic] user0u:
It does not matter whether we are talking about the interior or exterior. An app isn't a human that can simply look at an image and make complex changes as you describe in the OP.

The only things that even come close to doing what you describe are cutting-edge A.I. image generators like DALL-E and Midjourney.

And the very recent photoshop generative fill feature. Which good as it is, will still not be 100% accurate.
[Off-topic] AkoreJepade:
Yeah that is exactly what I was thinking.. something with A.I. (y)

Guess I will have to mess around a bit with photoshop and see what I can do. Thank you for the feedback!
[Android Q&A, Help & Troubleshooting] quangnguyen7616:
I added the following code to init.rc however it doesn't work

service myservice /system/bin/myservice -c /sdcard/myservice.conf
user root
group root
oneshot
disabled

If I replace the code below it works however I cannot adjust the configuration file in /etc if not the root user

service myservice /system/bin/myservice -c /etc/myservice.conf
user root
group root
oneshot
disabled

Is there a way to be able to access it directly from the sdcard? Or copy the config file from sdcard to etc when boot complete?
[Android Q&A, Help & Troubleshooting] rodken:
The service is not executable. Make sure that the file you are trying to run as the service is executable. You can do this by running the following command:

chmod +x /system/bin/myservice

The service is not in the correct directory. Make sure that the file you are trying to run as the service is in the correct directory. The init.rc file expects services to be located in the /system/bin directory.

The service is not configured correctly. Make sure that your service is configured correctly in the init.rc file. Make sure that you have specified the correct user, group, and oneshot options.

The service is disabled. Make sure that the service is not disabled in the init.rc file. To enable the service, remove the disabled option.
[Android Q&A, Help & Troubleshooting] quangnguyen7616:
I checked the logcat and found an error. Do you have any way to handle this problem?
[Android Q&A, Help & Troubleshooting] rodken:
The audit log line you provided indicates that the process with PID 6037, which is running the "myservice" service, was denied permission to read the file at /dev/sda14/ino=5921. The system context for the process is "u:r:system_app:s0", and the target context is "ubject_r:unlabeled:s0". This means that the process is trying to read a file that it does not have permission to read.

-- The file may be owned by a different user or group.
-- The file may have permissions that prevent the process from reading it.
-- The process may not have the necessary privileges to read the file.

The file may be owned by a different user or group.

The file may have permissions that prevent the process from reading it.

The process may not have the necessary privileges to read the file.

To solve this problem, you need to determine why the process is being denied permission to read the file. Once you know the reason, you can take steps to fix it.

Here are a few things you can try:

Check the ownership and permissions of the file. Make sure that the process has the necessary permissions to read the file.

If the file is owned by a different user or group, you can try to change the ownership of the file to the process.

If the file has permissions that prevent the process from reading it, you can try to change the permissions of the file.

If the process does not have the necessary privileges to read the file, you can try to grant the process the necessary privileges
[P3300, MDA Compact III ROM Development] muthapratikg:
;)i have a htcp3300

but im facing a problem

when start my htc

it shows me htc logo

and then suddenly it shows white screen:)
[P3300, MDA Compact III ROM Development] Thol:
If you had plug a SD card Over 2Gb, it's normal, the P3300 don't support le SDHC card, you must patch your WM5--6 with a SD HC patch, after you can ust it...
[General Questions and Answers] zesta14:
how to remove honor id on honor 80 pro flat (ANB-AN00) device

If you can help, please leave a comment

or does anyone know how to enter edl mode / test point

thx
[General Questions and Answers] CityRepairHub:
looks like no tool those support this one
[General Questions and Answers] zesta14:
up
[General Questions and Answers] zesta14:
how to remove honor id on honor 80 pro flat (ANB-AN00) device

If you can help, please leave a comment

or does anyone know how to enter edl mode / test point
[General Questions and Answers] zesta14:
hii up again

how to remove honor id on honor 80 pro flat (ANB-AN00) device

If you can help, please leave a comment

or does anyone know how to enter edl mode / test point
[Android Q&A, Help & Troubleshooting] HippoMan:
I'm running crDroid 9.8 (Android 13) on a Pixel 7 Pro, and I'm trying to determine whether or not my OS's kernel is GKI. I want to know this because I'm thinking of trying Kernel SU, and it can only run on a device with a GKI kernel.

No one in the crDroid forum or on the KernelSU site can tell me whether or not my kernel is GKI, so I've started this thread here to see if anyone knows how any given Android kernel (not just my own) can be tested for whether or not it's actually GKI.

The KernelSU people say that the official naming convention for a GKI kernel is this:

Version.PatchLevel.SubLevel-AndroidRelease-KmiGeneration-suffix

But my device's kernel is named as follows:

5.10.157-ga88edbe37d3a

This doesn't match the above-mentioned GKI naming convention. However, the official "KernelSU Manager" app that's supplied by the KernelSU people says that my device's kernel is eligible for accepting KernelSU. But the KernelSU people say that the KernelSU Manager is only using a regex test on the kernel's name to determine kernel eligibility, and my kernel's name doesn't even match the "official" naming convention for such kernels that the KernelSU people themselves have said is necessary (in other words, the info from the Kernel SU's docs and the Kernel SU's manager software is inconsistent).

Again, I asked about this at the KernelSU site, but they don't know whether or not the crDroid 9.8 kernel is actually an eligible GKI kernel, and I have also asked in the forums for my crDroid 9.8 OS, but no one there has given any answer to this question, either.

Therefore, I'm wondering: is there any software utility that I can run on my device or elsewhere which will tell me whether or not the device's kernel actually is or is not GKI?

Thank you in advance for any ideas and suggestions.
[Android Q&A, Help & Troubleshooting] rodken:
Check the kernel version. GKI kernels are typically based on the latest LTS kernel release, which I think is currently 5.10.

Check the kernel config. GKI kernels typically have a number of specific kernel config options enabled, such as CONFIG_GENERIC_KERNEL_IMAGE and CONFIG_LOAD_MODULES.

Check the kernel boot header. GKI kernels typically have a specific boot header format.

Also,

Look for the GKI branding in the kernel source code.

Look for the GKI boot header format in the kernel boot image.

Unfortunately, there is no current software utility that can definitively tell you whether or not a given Android kernel is GKI.
[Android Q&A, Help & Troubleshooting] HippoMan:
Thank you very much!

Where can I find the kernel config information and the kernel boot header information? Do I need access to the kernel source code in order to find this information?

And where can I find the kernel boot image for the kernel that is currently in use with my OS?
[Android Q&A, Help & Troubleshooting] rodken:
You can usually find the kernel config information in the config.txt file in the /boot directory.
[Android Q&A, Help & Troubleshooting] rodken:
You can try to use the following command to find the kernel boot image for that kernel:

ls -l /boot/vmlinuz-*

I should list all of the kernel boot images in the /boot directory.

To find the kernel boot image for the kernel that is currently in use with your OS, you can use the following command:

uname -r

This command will print or display the name of the kernel that is currently in use.
[Android Q&A, Help & Troubleshooting] HippoMan:
Thank you very much.

My device (rooted with Magisk Delta 26.3) doesn't have a /boot directory.

The only subdirectory named "boot" is /data/local/boot, and it doesn't contain any config.txt file
[Android Q&A, Help & Troubleshooting] HippoMan:
That lists the same kernel name that I listed in my OP: 5.10.157-ga88edbe37d3a

As I mentioned, the KernelSU people do not know whether that is or isn't a valid GKI kernel.
[Android Q&A, Help & Troubleshooting] rodken:
Back to your original question, there really isn't a software that I know of that will make the process easier.
[Android Q&A, Help & Troubleshooting] HippoMan:
Not only is there no /boot directory on my device, but there isn't even any config.txt file anywhere on my device.
[Android Q&A, Help & Troubleshooting] rodken:
Have you reached out to any of the groups on TG?
[Android Q&A, Help & Troubleshooting] HippoMan:
I understand. I don't care that the process can be complicated and difficult.

I am willing to do whatever work is necessary to find out the GKI status of that kernel.
[Android Q&A, Help & Troubleshooting] HippoMan:
Yes, I reached out specifically to the TG group for the crDroid 9.8 OS for my device. No one has given me any answer.
[Android Q&A, Help & Troubleshooting] rodken:
I feel your pain when it comes to looking for assistance on TG.
[Android Q&A, Help & Troubleshooting] HippoMan:
Thank you!

I'll just be patient about possibily eventually hearing something in that TG group, or maybe in this current thread.
[Android Q&A, Help & Troubleshooting] rodken:
You can try to rephrase your question on TG to see if it can shake some trees.
[Android Q&A, Help & Troubleshooting] HippoMan:
I'll do that tomorrow if I don't get any answer by then. I don't want to come off as a pest.
[Android Q&A, Help & Troubleshooting] HippoMan:
I have two questions that are tangentially related to my original question ...

First question:

On a different device of mine running A13, I see that its kernel name indeed matches the GKI naming conventions. However, I've been told by the KernelSU developer that some kernels are misnamed, so the kernel name itself is not a 100-percent reliable way to determine whether it's actually GKI. And no one in the discussion forums for that device has answered my question about whether or not it's GKI.

That A13 device actually has a working OrangeFox recovery which I've installed, and I can do reliable nandroid backups and restores.

So, if I take a nandroid backup of the entire system (including the boot partition), and if I flash the seemingly appropriate KernelSU module and that hoses my system, would a nandroid restore work to successfully get me back to the original kernel?

Or is an OS's kernel somehow separate from what nandroid can back up and restore?

Second question:

I'm currently running Magisk Delta 26.3 on this A13 device. Would I need to completely uninstall Magisk before attempting to install KernelSU?
[Android Q&A, Help & Troubleshooting] Kplamb:
It is explained here.!

GKI 1.0 applies to all devices shipped with 5.4 kernels, even those launched with Android 12 or Android 13. GKI 2.0 was introduced in Android 12 for devices with 5.10 kernels and is the new standard for all devices that ship with 5.10 or later kernels.

GKI Versioning | Android Open Source Project

source.android.com
[Realme C3 ROMs, Kernels, Recoveries, & Other Devel] kartikeyv299:
Device Information:

Device Model: Realme C3 (RMX2027_11_c.11)

Android Version: 11

Problem Description: I am currently facing a significant issue with my Realme C3. It started when I attempted to root my device and mistakenly flashed the wrong boot image. As a result, my phone is now stuck in a boot loop. The device continuously restarts and never gets past the boot screen. Unfortunately, I am unable to access Recovery Mode.

Actions Taken So Far: I have tried the following steps to resolve the issue:

Attempted to boot into Recovery Mode (unsuccessful).

Checked for solutions online, but none have worked so far.

Modifications and Customizations:

My device has been rooted, and I have previously installed a custom recovery (if applicable).

Troubleshooting Steps: I need guidance on how to recover my Realme C3 from this boot loop and flash the correct boot image. Any assistance or step-by-step instructions would be greatly appreciated.

Attached Files: I am unable to provide any error messages or logs as I cannot access the device's interface due to the boot loop issue.

Additional Information: I understand that this issue may have been caused by my own actions while attempting to root my device. I appreciate any help and advice the community can provide to resolve this problem.

Forum Rules: I have read and will comply with the forum's rules and guidelines.

Thank you in advance for your assistance!
[Realme C3 ROMs, Kernels, Recoveries, & Other Devel] user0u:
What ROM are you on? Flash the boot.img for your ROM in fastboot mode.
[Realme C3 ROMs, Kernels, Recoveries, & Other Devel] kartikeyv299:
i am unable to get specific rom version an u please help me to find that btw it is realme ui 2.0
[Realme C3 ROMs, Kernels, Recoveries, & Other Devel] mvikrant97:
Extract the boot.img partition from your phone's firmware that is currently installed on the device.

Flash the boot.bin partition using MTK client tool to fix your device.

If your phone has dual partitions like A/B just flash the partition with MTK client tool

python mtk w boot boot_a.bin

python mtk w boot boot_b.bin

Then flash back the device using SP Flash Tool to restore it back to stock

View attachment 6015795
[Realme C3 ROMs, Kernels, Recoveries, & Other Devel] kartikeyv299:
bro please give me another solution i am not able to do that right now
[Realme C3 ROMs, Kernels, Recoveries, & Other Devel] mvikrant97:
Why? Let me know what do you need assistance with.
[Realme C3 ROMs, Kernels, Recoveries, & Other Devel] kartikeyv299:
i just try too that but i got stuck into mid bcz it showing no central directory found
[Android Q&A, Help & Troubleshooting] xdagoblin:
I'm looking for an open-source Keystore replacement. I'd prefer to have keys stored on a regular partition and handled by an open-source app, rather than in some inaccessible area of my proprietary hardware.

If I was to implement this on a rooted device, how would I go about it? Specifically, what can I hack to cause apps calling the Keystore API to go to my app rather than whatever the vendor provided? Could a Magisk module achieve this? Maybe someone has done it before me?

I'm looking to get this done on a brand new Sony Xperia 1 V running stock firmware (but rooted). I'm not planning to give Internet access to the proprietary OS, and it appears this is causing some errors in the proprietary Keystore implementation, which I suspect is causing a bug which is preventing me from unlocking the phone with PIN/pattern. I've posted a detailed explanation of this bug in the Xperia 1 V forum.

Also, reading https://www.xda-developers.com/google-remote-key-provisioning/, I see a slight inconsistency:

followed by:

Well, here I am, being a power end-user noticing a change ;-) It's in the form of a bug, but some other meticulous user might notice a change in that a new device issues an extra request to Google. I really don't like this new mechanism, it's shouting DRM all over the place.
[Android Q&A, Help & Troubleshooting] rodken:
There are a few ways to implement an open-source Keystore replacement on a rooted device. One way is to use a Magisk module. There are a few Magisk modules available that can do this, such as:

-- Keystore Wrapper

-- OpenKeystore

These modules work by intercepting calls to the Keystore API and redirecting them to your own open-source Keystore implementation.

Another way to implement an open-source Keystore replacement is to modify the system partition. This is a more complex process, but it gives you more control over how your Keystore implementation works.

Of course, you will need a working version of TWRP.
[Android Q&A, Help & Troubleshooting] xdagoblin:
Nice, many thanks! Could you provide links to those Magisk modules? I'm having a very hard time finding this with my keywords. Is this related? https://github.com/cyberphone/openkeystore
[Android Q&A, Help & Troubleshooting] rodken:
Keystore Wrapper https://github.com/j-hc/revanced-magisk-module/blob/main/ks.keystore

OpenKeystore https://github.com/effortlessdevsec

You might have to do some digging to locate it?
[Android Q&A, Help & Troubleshooting] xdagoblin:
I'm sorry, but I don't understand.

The first link is to a binary file in some other Magisk module called ReVanced.

The second link is to a developer that has 65 repositories on Github, none of them named "OpenKeystore".

Am I talking to ChatGPT?
[Android Q&A, Help & Troubleshooting] rodken:
How far did you dig into the repos of each link?

Keywhizand Keymint are projects that aims to create a secure and easy-to-use Keystore management system for Android. Keywhiz is also still under development, but it has the potential to be a valuable tool for users who need to manage cryptographic keys.
[Android Q&A, Help & Troubleshooting] xdagoblin:
You only provided one link with a repo.

I didn't dig very far, at a first glance it seems irrelevant to the original question. ReVanced *may* be using a similar technique to what I was asking about, but it's definitely not a Magisk module called "Keystore Wrapper".
[Android Q&A, Help & Troubleshooting] rodken:
Read previous post #6.
[Android Q&A, Help & Troubleshooting] rodken:
Was that a rhetorical question?
[Android Q&A, Help & Troubleshooting] xdagoblin:
No.

Your answers seem slightly related to my question, but without any actual substance or meaning. You said there are not 1 but 2 Magisk modules that do what I asked for, then pretended to provide links to them . These turned out to be links to things that theoretically could be related, but aren't at all the actual modules you originally mentioned. Then you started talking about even more projects (KeyWhiz and Keymint) that again are vaguely related to what I asked for, but don't answer my question at all.

Also, not sure why I'd "need a working version of TWRP": I successfully installed Magisk and one of its modules without TWRP. Again, TWRP is slightly related to Magisk, but not at all in this case.

That's exactly the kind of behaviour I observed when talking to ChatGPT.
[Android Q&A, Help & Troubleshooting] rodken:
Since you are fan of ChatGPT were you ever able to achieve success in resolving your issue using A.I. if not, you can always visit some great minds over at StackOverflow with a follow up question.

In case you didn't know, StackOverflow is a website where programmers can ask and answer questions about programming. There are many experienced programmers on StackOverflow who are willing to help others.

The theory was to lead you into the right direction assuming that you knew your way around the web utilizing Google Search and the like especially when links might be related or not.

I was trying to explain how KeyWhiz and Keymint are both open-source Keystore implementations that are still under development. They are not yet available for public use.

Maybe instead of wasting more time trying to explain, I'd rather end with:

I apologize if I can't be of anymore assistance.
[Android Q&A, Help & Troubleshooting] xdagoblin:
OK, in that case I also apologize. I was too quick to judge your answer.

Keymint actually could be quite useful, as it looks like it implements the right HAL. I'd need to somehow plug it in to an existing firmware. Which is kind of what I was curious about originally: how do I go about it? Do I have to recompile the whole Framework? Or are there some hooks, libs or processes that I could hack into, allowing me to replace just a small portion of it?

But I'm still curious: do those Magisk modules you mentioned in the first post actually exist somewhere?

Agreed that Stack Overflow is another good site for asking questions. I just thought I'd try here first, as there are a lot of awesome Android devs around here as well.
[Android Q&A, Help & Troubleshooting] rodken:
The best way to approach your question is to direct you to the GitHub repository for Keywhiz where you are free to roam and submit an issue. As far as Keymint is concerned, you can try to reach out to the owners and hopefully get a response to your inquiries.

The Keystore Wrapper module might not provide as an alternative Keystore implementation. Instead, it only allows you to wrap your own Keystore implementation into the Android Keystore system.

The theory was that once the module was installed, you will needed to configure it to use your own keystore implementation. To do this, you would've needed to edit the module's configuration file.

/data/data/com.topjohnwu.magisk/files/modules/keystore_wrapper/config.txt

The general idea with the Keystore wrapper was to call the wrap_keystore() function which it turns takes two arguments

-- keystore_name: The name of the keystore to wrap.

-- keystore_options: A map of options to pass to the keystore implementation.

To wrap, you would use the following code:

import android.security.keystore.KeyStore

val keystore = KeyStore.getInstance(KeyStore.ANDROID_KEYSTORE)
keystore.load(null)

val keystore_wrapper = KeystoreWrapper.wrap_keystore(
keystore_name = KeyStore.ANDROID_KEYSTORE,
keystore_options = emptyMap()
)

// Use the wrapped keystore

Therefore, disregard. As of this writing, it turns out that the links for the OpenKeystore and Keystore Wrapper modules are no longer available.

Not to beat a dead horse, I apologize if I can't be of anymore assistance.