yashsingh1/xdaforums huggingface dataset:
[Nothing Phone 2] HippoMan:
Thank you very much. I already understand that KernelSU installation requires a GKI kernel.

I guess I should have asked part of my question a bit differently, as follows: does anyone know whether the kernel that comes with OS 2.0.3 is a proper GKI kernel?

It seems to fit the GKI naming convention, but that's not conclusive enough proof for me, because it might simply be mis-named.

But the other part of my question still stands: has anyone already successfully installed KernelSU under OS 2.0.3 on the Nothing 2?

I need my phone for work and other aspects of my life, and I don't have a lot of spare time. Therefore, I don't want to run the risk of bootlooping or bricking if the KernelSU installation attempt fails due to my device's kernel not actually being GKI.

That's why I'm asking here if anyone has already successfully installed KernelSU on the Nothing 2 running OS 2.0.3 .
[Nothing Phone 2] khusika:
Just refer to this guides

Installation | KernelSU

A kernel-based root solution for Android GKI devices.

kernelsu.org

Select the KernelSU version according to your current kernel

You don't need to worry if you have a stock boot.img or backup kernel
[Nothing Phone 2] HippoMan:
I understand the guides and I'm following them, and I understand how to choose the correct KernelSU installation module and how to install it. If you read my OP, you'll see that I already chose the appropriate KernelSU installation module based upon the information given in the KernelSU guides.

I'm not asking about that.

Once again, the following is my question: does anyone know whether or not the OS 2.0.3 kernel is a proper GKI kernel?

I'm asking this question within a Nothing 2 forum because my question specifically concerns something about the Nothing 2 device itself: i.e., whether or not its OS 2.0.3 has a GKI kernel.

Even though I have OrangeFox installed and I can do full nandroid system backups and restores, I don't want to attempt the KernelSU installation unless I know for sure that the OS 2.0.3 kernel is actually a true GKI kernel.
[Nothing Phone 2] khusika:
Then what are you be afraid of? I assume you are already read the whole installation instruction and you should have installed the KernelSU application. Those application will tell you whether KernelSU supports it or not.

if not supported > don't do anything

if supported > install kernel version which is matchup with your current kernel version

Again

Read this (KMI)

Installation | KernelSU

A kernel-based root solution for Android GKI devices.

kernelsu.org

Flashing KernelSU doesn't burn your device
[Nothing Phone 2] HippoMan:
I was told by the KernelSU developer in a discussion in the KernelSU github issues forum that the KernelSU Manager only does a regex match on the device's kernel name to determine whether it *might* be a proper GKI kernel, and that this is not a definitive determination as to whether or not the kernel actually is GKI, because some kernels are misnamed.

I was told by that person that I need to find out from the kernel's developer as to whether or not it's actually GKI.

That's why I am asking this question here in this Nothing 2 forum.
[Nothing Phone 2] HippoMan:
That's good to know, but I still don't want to try installing KernelSU unless I know that the OS 2.0.3 kernel is actually GKI.
[Nothing Phone 2] HippoMan:
I have a tangentially related question: my OS 2.0.3 device is currently rooted with Magisk Delta 26.3. Would I need to completely uninstall Magisk before attempting to install KernelSU?
[Nothing Phone 2] HippoMan:
Just checking back here to see if there might be any new information.

Has anyone successfully tried KernelSU with OS 2.0.3? ... or 2.0.4, for that matter?
[Nothing Phone 2] dlads:
People on TG been using it, assume it'll work on any version.
[Nothing Phone 2] HippoMan:
Thank you, and I'm sorry for the following question. I just want to make sure that my understanding is clear:

Are you saying that some people have reported on TG that they have been successfully using KernelSU specifically with either 2.0.3 or 2.0.4? I don't have access to TG at the moment.
[Nothing Phone 2] dlads:
Yes pretty sure.

Install the test app and it'll say "not installed" meaning you can use it.

Grab the boot image or patched image in your case for your firmware.

Then grab the kernelsu image and flash it, if it works you're rooted, if it doesn't then just boot your original patched image or flash your stock boot image.

Risk free
[Nothing Phone 2] HippoMan:
Thank you very much for explaining and for so much detail!
[Nothing Phone 2] HippoMan:
Oh ... a couple related questions:

I'm already running Magisk from having installed the patched 2.0.3 image in the past. Would I have to uninstall Magisk before trying to install KernelSU?

Also, I'm already using OrangeFox. If I take a full nandroid backup and then try to flash the KernelSU image, and if this fails, I assume that I can just restore my nandroid backup in order to get my previously running set-up installed again, without needing to go through any re-flashing exercise ... correct?
[Nothing Phone 2] dlads:
There's no reason to restore a nand because you're only modding the boot image..

You can uninstall the magisk app if you need to think you'd be using the kernel su app instead.

I've not installed kernel su I've just read their page.

You can use your custom recovery to install the KernelSU image..

Again this is on their site.

There's three ways to root
[Nothing Phone 2] HippoMan:
Yes, I have already read everything on their site, and I understand it all.

The reason I'm posting this thread here is to query whether anyone has actually successfully performed these steps specifically on a Nothing 2 running 2.0.3 or 2.0.4.

Sometimes there are unexpected issues that crop up when standard, documented, normally successful software-installation procedures are followed on certain devices or under certain OS's.

I'm going to wait a few days to see whether anyone who will read this thread might reply and report such issues that might have occurred under 2.0.3/2.0.4.

If no such replies appear, then I will go forward and try this on my own.
[Nothing Phone 2] HippoMan:
I assume that people have carefully read this thread, and therefore, I assume that people clearly understand that ...

(1) ... before creating this thread, I already read all the documentation on the official KernelSU site, and I totally understand that documentation;

(2) ... I am therefore *NOT* asking for help in installing KernelSU;

(3) ... and I don't have access to the KernelSU TG channel, and that's why I'm posting here.

All I want to know now is a one-word answer to the following "yes or no" question:

Can anyone who's reading this confirm that they have indeed successfully installed KernelSU on either OS 2.0.3 or OS 2.0.4?

Yes or no?

I asked a similar question in my previous message, and so far, no one has answered. Therefore it's likely that the answer is probably "no". However, I'm posting now simply to double-check that assumption.

Thank you very much.
[Samsung Galaxy Watch 5] HoxtonRob:
Hello dear XDA, I wanted to ask you developers if it was possible to get around the impossibility of activating the draw on top option, given that before it was possible if an application requested itView attachment 6023676
[Samsung Galaxy Watch 5] HoxtonRob:
Guys Before updating to UI 4View attachment 6023681
[Galaxy S6 Q&A, Help & Troubleshooting] NipunRasadara:
In my phone, the volume down button is not working.

I want to enter into download mode now.

How can I do it?

Note: When I turn on the phone, it is tucked in the TEAMWIN logo (TWRP). Any button doesn't respond.
[Galaxy S6 Q&A, Help & Troubleshooting] Renate:
Almost all motherboards have test points for the switches so that a motherboard can be exercised in the factory without the little side PCB connected.

These are usually located where the side PDB plugs in.

Usually it's a contact to ground.

It's safer if you ground it using a resistor (in case you hit some power point instead).

Or you could replace the side PCB.

Or you could repair the side PCB. Remove the adhesive layer. Fix or replace the little "buckle" contact. Cover with electrical tape.
[Galaxy S6 Q&A, Help & Troubleshooting] NipunRasadara:
Thank you so much dr. Is there any software or tool to enter into DOWNLOAD or RECOVERY MODE?
[Galaxy S6 Q&A, Help & Troubleshooting] Renate:
Was the VolDn broken before you ran into this boot problem?

Or are you just guessing that the button is the problem?

Sorry, I don't know much about Samsung stuff.
[Galaxy S6 Q&A, Help & Troubleshooting] NipunRasadara:
Was the VolDn broken before you ran into this boot problem?

YES

Or are you just guessing that the button is the problem?

I cant go to Download mod because VolDn is broken
[Galaxy S6 Q&A, Help & Troubleshooting] Renate:
I guess that removing the back on the S6 is a big pain?

Do you want to continue to use this device or only be able to get files off it?

If you want to really fix it dealing with the back is the biggest problem.

You can replace the switches for $2 https://www.ebay.com/itm/254198712426

If you just want to get files off this you can pry out the VolDn button.

You should be able to see the contacts under the little tin buckle.

You can short them without taking off the back.

Of course, this reduces the resale price.

If you just wanted to hit the VolDn in Android you could use a keyboard into an OTG adapter.

But booting up this device is just looking for contact closure on a GPIO.
[Galaxy S6 Q&A, Help & Troubleshooting] NipunRasadara:
Got it dr. Thank you so much for your valuable support. Have a nice day!!!
[General Questions and Answers] Runner_76:
Hi all,

Is there a tread in the works for owners of a

Motorola g200 5G / Edge S30 (xpeng) ?​

If not, i might be interested to know if it is worth trying to learn maintaining one.

Thanks!
[General Questions and Answers] Deivid Soltoski:
Here is the forum for Moto G100 / Edge S only, go to the forum for Moto G200
[General Questions and Answers] FluffyPants:
I would like to know how to install the engineering rom on xiaomi with an unlocked bootloader. it possible?
[General Questions and Answers] khusika:
What "engineering rom" are you talking about? You can install any ROM as long as it is build only for your device.
[OnePlus 9RT] leemanhlc:
Mod edit - translated by https://translate.google.com/?. Oswald Boelcke.

Please help me how to update oxgenos international rom for 9rt. I would like to thank you

************************

các bác chỉ giúp em cách up rom quốc tế oxgenos cho 9rt với ạ. em xin cảm ơn
[OnePlus 9RT] Oswald Boelcke:
Hello and good morning, @leemanhlc Welcome to XDA! I hope you'll always get the support you require.

However, as a one-time courtesy I've translated your above post. With reference to rule no. 4 of the XDA Forum Rules, please post in English or add at least an English translation to your Vietnamese posts.

Spoiler content hidden.

Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[Google Pixel 7] liwerfg:
Following the problem stated at reddit:

https://www.reddit.com/r/GooglePixel/comments/178jj3i

"So guys, I was using my phone normally when suddenly I got a message that phone is being factory reset. It went to factory reset screen where you have to use volume and power button to select and scroll. There I had two options, “try again” and “factory reset” so I chose try again. Since then it is stuck at “Phone is starting”. Google pixel 7 128gb."

It seems that is a problem involved with multiple user profiles in Android 14.

If my only solution is do a factory reset, I can live with it, but do you know any way to save/backup all the data before the factory reset? Maybe with adb tools? Phone isn't rooted.

Thank you.
[Google Pixel 7] TMW1996:
i think the only way is to reset the device
[Google Pixel 7] simplepinoi177:
particularly because the phone isn't rooted, you are stuck with limited options and will not be able to "save/backup all the data before the factory reset" -- and even if you were rooted, there is no adb tools or command that would accomplish that either (running adb commands outside of the OS) -- one of the major drawbacks of not being able to have a custom recovery.

If you can get into the stock recovery, you could always try (the only option available for Pixel phones with locked bootloaders) sideloading a Full OTA -- this doesn't require the device to have an unlocked bootloader -- and I would say (my own personal opinion of course) 15%-20% of those who try it are able to get back in....
[Google Pixel 7] insestito:
Use Android Flash tool. easy
[Google Pixel 7] simplepinoi177:
you'd need to have at least "OEM unlock" ticked, and since phone isn't rooted, I was going off the strong assumption that the bootloader isn't locked....

And since he can't go into the OS, in the case that it isn't ticked; it can't tick it now....

So, considering all of that, usually sideloading OTA is the only other option (after factory wipe/reset)....

Before even Android Flash tool, I'd suggest Google Pixel Update and Software Repair tool, but in either case the bootloader needs to be unlocked...
[Google Pixel 7] liwerfg:
Yes, the bootloader was locked too. And I also tried to sideload OTA, but the result ended up being the same, so in the end, I had to reset the device. I find it unacceptable that a company as large as Google hasn't caught these kinds of errors in the testing phase because it's not just one user, it's happening to a lot of people.

Anyway, thanks to everyone for the answers. One learns from these experiences, and I've already unlocked the bootloader and even rooted it.
[Google Pixel 7] simplepinoi177:
Sorry you were forced to resort to resetting the device.

FWIW, for any who are following this issue (sorry if it's not really applicable any longer to OP), the below article speaks on Google's acknowledgement of the bug...

Google is investigating Android 14’s multiple profile update bug

The Android 14 update has wreaked havoc on some phones.

www.theverge.com
[Google Pixel 8 Pro] gpvecchi:
The Play Store shows that every app is installed in my Pixel 7 Pro, is there any way to fix it?
[Google Pixel 8 Pro] Ducter:
Mine oddly says the same thing, I was thinking because I transferred from the 7p to 8p but can't be sure.
[Google Pixel 8 Pro] Misterxtc:
Same here, I thought it was because I did a sim card swap instead of registering the new sim. I did a clean install though.
[Google Pixel 8 Pro] HipKat:
Weird, even the ones that just updated still show P7P
[Google Pixel 8 Pro] gpvecchi:
I restored a backup, but I never had that issue before, and I always restore backups.
[Google Pixel 8 Pro] cmh714:
Curious if you went to the play store on your PC and uncheck the P7P as one of your devices....GL!
[Google Pixel 8 Pro] HipKat:
Since I updated Play Services, there's no device listed on my apps in the store any longer
[Google Pixel 8 Pro] gpvecchi:
I removed the access to my account on my old P7P.

Play Store updated to latest beta, and still showing.
[Google Pixel 8 Pro] gpvecchi:
Under further investigation, the phone in use is not shown in Play Store, so the one you see is the other phone in your (previous) possess. If you remove it from your device list, it will not appear again.
[Miscellaneous Android Development] Hadenix:
View attachment 6023693

This is a Lineage OS 20.0 ROM for the Helio P23 based UMIDIGI A 5 Pro.

Lineages is a free, community built, aftermarket firmware distribution, which is designed to increase performance and reliability over stock Android for your device.

Lineages is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Lineages does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for Lineage OS is available in the Lineages Github repo. And if you would like to contribute to Lineages, please visit our Gerrit Code Review. You can also view the changelog for a full list of changes & features.

Downloads

Get the latest LineageOS Build for breeze Download

Magisk (optional) https://github.com/topjohnwu/Magisk/releases

Recovery https://xdaforums.com/t/recovery-tw...-umidigi-a5-pro-mt6763.3954643/#post-80017156

For reporting bugs, be sure to include a log : check how to

Source Code

LineageOS: https://github.com/LineageOS

Device Tree: https://github.com/umidigi-mt6763-dev/android_device_umidigi_breeze

Vendor Tree: https://github.com/umidigi-mt6763-dev/android_vendor_umidigi_breeze

Kernel Tree: https://github.com/umidigi-mt6763-dev/android_device_umidigi_breeze-kernel

Support

Telegram: https://t.me/umidigia5prochat

ROM OS Version: Android 13

ROM Kernel: Linux 4.4.146

Latest Release Date: 20/10/2023
[Miscellaneous Android Development] Hadenix:
Screenshots
[Miscellaneous Android Development] Hadenix:
List of LineageOS Vendor OSS breeze changes:

• Full VNDK 33 build

• Lineage Upstream

• October Security Patch

• Most of the files have been moved for vendor from the systems. according to android 13

• Overlay: Exempt ImsService from location indicators

• Disable BPF

• Build android.hardware.camera.device@3.3 from source

• Set gestures only navigation default

• Update power_profile.xml

• Uprev Clearkey DRM service to 1.4

• Drop prebuilt configstore HIDL

• Enable DM file pre-opting to reduce first boot time

• SurfaceFlinger properties from merlin (Redmi 9)

• Overlay: make transition animation a bit faster

• Overlay: make window animation/transition scale to 50%

• Add fingerprint configuration to overlay

• Build fingerprint service from source

• SettingsProvider: def_bluetooth_on to false

• Overlay: Disable UI touch sounds by default

• Drop thermal_manager service

• Enable USB ConfigFS in recovery mode

• Fixing in call gain control on MediaTek devices

• Don't override APNs config file

• Drop useless factory and meta_tst binary

• Add basic USB HAL that reports no status change

• Build libstdc++ from source

• Drop partition_permission & throttle scripts

• Drop vendor.mediatek.hardware.log

• Drop useless em_hidl

• Drop engineermode completely

• Drop unneeded vendor cacerts

• Overlay: Enable call recording

• rro_overlays: Move rro overlays to vendor

• Kang auto brightness configuration from 'guacamole'

• Switch to modern Bluetooth Audio HAL

• Set correct channel mask for BT SCO Headset Mic

• Nuke AOSP rild

• Disable settings provider model

• Disable VSync for CPU rendered apps

• Fix rank of SW OMX components

• Disable codec2

• Import recommended pm dex props

• Reduce number of CPUs for system-background apps

• overlay: Limit screen recorder's framerate to 60fps

• enable multiuser ui

• Enable Natural and Boosted display color modes

• Allow device to transition colors efficiently

• overlay: Enable WCG mode

• overlay: Allow support of unprocessed audio

• overlay: configure SQLite to operate in MEMORY mode

• Suppress vendor logspew

• Enable config_avoidGfxAccel

• Disable Nearby Discovery and Nearby Messages service

• Disable debug.sf.enable_hwc_vds

• overlay: Update deprecated screen power items

• Added zram parameter

• Add WiFiOverlay

• Switch BtAudio to AIDL

• Disable PQ to avoid video flickers

• Set the VENDOR_SECURITY_PATCH level to match the platform security patch level
[Miscellaneous Android Development] ildoge:
great Rom. Installed easily, it's very fast. Gapps, however, I struggled, in the end I flashed [AUTO]LiteGapps_arm64_13.0_v2.6_official. Bluetooth doesn't work
[Miscellaneous Android Development] Hadenix:
I'll fix the rest later
[Miscellaneous Android Development] ildoge:
I try to turn on Bluetoot but after a while it goes OFF. The fingerprint doesn't appear either
[Miscellaneous Android Development] Hadenix:
When I have time I'll check everything
[Miscellaneous Android Development] Turtles77:
I also have that problem with the Bluetooth and the camera not working while waiting for a solution, otherwise the fingerprint reader can be used again.

Thanks and greetings
[Miscellaneous Android Development] Hadenix:
View attachment 6033387

lineage-20.0-20231115-UNOFFICIAL-breeze.zip​

• Lineage Upstream

• November Security Patch

• Prefer HW codecs for thumbnailer

• Override mediacodec service definition from stock

• Set proper product model

• Relocate the firmware customfilter to the vendor

• Fixed ROM installation errors
[Miscellaneous Android Development] Hadenix:
View attachment 6034739

lineage-20.0-20231119-UNOFFICIAL-breeze.zip​

• Overlay: SIM hot swapping is supported

• Overlay: Enable config_unplugTurnsOnScreen (turn on the screen when you disconnect the usb)

• Overlay: Enable haptic text cursor

• Pack required stock firmware V2.0_20210326 into the lineage

• Add dtbo image to the output zip

• Update the charging logo (https://t.me/hadenix_blog/36)

• Update the boot logo (https://t.me/hadenix_blog/35)
[Miscellaneous Android Development] ildoge:
Very good rom, bluetoot doesn't work for me, I attach logcat
[Miscellaneous Android Development] Hadenix:
I am aware of this problem
[General Questions and Answers] marcoNST:
HI,

I understand that TWRP/Nandroid full backup allows you to restore the files to the same phone. However , I have 2 Samsung Galaxy A5 (same model) and I would like to take a full image backup from one and restore it to the other one. I tried to copy/paste files to the other phone but TWRP -restore would not see them (I guess It only recognises backups of its own device).

So my question is: Is it possible to have a Nandroid-type of image backup and have it restored to *another* identical phone, in order to create litterally a backup phone?

Thanks
[General Questions and Answers] Slim K:
Seeing as your phone (Samsung A5) comes with Android 7.0 or lower, you can possibly backup the whole data partition and restore it. It depends on if your data partition uses full-disk encryption or file based encryption.

In order to determine that, access TWRP on device without decrypting data first (when prompted to enter pass/pin at the start press cancel) and use the file manager to look inside your data partition. If it is empty or cannot be mounted, then your device has FBE, Which would be good news.

Now if both devices are running the same OS version and everything (apart from the data partition), then you can use the command dd in TWRP's terminal (found in advanced menu) like this:

#Go to the partitions
cd /dev/block/by-name/

#List all partitons and see if it's named userdata or just 'data'
ls

#Backup Userdata partition to internal storage
dd if=/dev/block/by-name/userdata of=/sdcard/userdata.img

#This is the reverse operation in your to be restored device
dd if=/path/to/userdata.img of=/dev/block/by-name/userdata

You would find the .img in the root of internal storage. Transfer to your other and use the dd command to write it back.
[General Questions and Answers] marcoNST:
Thank you so much for your help!

I forgot to add that both devices run on LineageOS 18.1 and they are both rooted.

I assume your solution is still valid?
[General Questions and Answers] Slim K:
Sadly no. After android 8, FBE data partitions are mandatory, meaning that a 1 to 1 copy and paste won't work. (For encryption reasons). If you however run both phones with unencrypted data partitions, the above solution will work. (you can disable encryption by flashing a special .zip on a clean install of your Custom ROM + Formatted Data)

If you prefer an encrypted partition Instead, I would look into using Neo Backup. This solution works for all things except maybe Dialer and contacts backups (could work with it or maybe not, very device dependent).

Hope I answered any confusion.
[General Questions and Answers] marcoNST:
Given that I do not use the phones for calling and contacts "database" , I won't need to backup any data in there.

I had looked into NeoBackup but I understand It backs up only apps and data. How about the phone settings? Don't think It can.