yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A34] Felix2502:
Good morning,

I have a problem, my friend locked his phone and he can't remember his google password, I told him to leave it with me to try to recover the phone, but when I was doing it I remember just install recovery then flash the rom and problem solved, now I saw that you have to do unlock (FRP) as well.

I tried to follow some videos on YT pero I still haven't found one that works for me, with different software for this process. The problem that they cost or at the most they make you unlock versions lower than android 13. Please I need some help.
[Samsung Galaxy A34] V0latyle:
Samsung Galaxy FRP Unlock Thread!

Please apologise me if your thread or messages remain unanswered but I get a lot of messages and notifications from so many thread and users on a daily basis from all over XDA so there would be a delay in answering you back. Thank you for your...

xdaforums.com

Tell your friend he'll need to provide proof of purchase as FRP is intended to prevent use of stolen devices.
[Samsung Galaxy A34] Felix2502:
Is'nt complete
[Android Head-Units] mily-manson:
hi

i bought Allwinner QUAD-CORE T3 K2001N TL with MCU 3.7

i wanna root this device but cant find any solution's,

i find post about head unit to root but with different MCU version, can i use that way?

in this thread have root file but cant download! any body have this file or succeed to root this unit?

thread : https://4pda.to/forum/index.php?showtopic=840515&st=19660#entry96234891

but link not work error 404

Thanks

my device info :

Software version: v.23.03.10A_3.0[17:02]{H.221020} {C.230320}

Car model: Peugeot - 206 - [2005-2008(1Gen)] - [A]] {9-1-1-1-1}

Can box: simple

EMMCID: 0x04816820

APPVER: K2001N_TL_S212620.20230419.101643

PlatformVer: K20N-2023/0414[9:42:44]-1.00_R

MCUVER: V3.7-FF01-20221119-A02-CAN0000-00-00-DVD00000000-00

BTVER: XR829_V2.0/2022:09:23:(10:20:27)
[Android Q&A, Help & Troubleshooting] teknixstuff:
I'm trying to make a fully automatic LineageOS installer, however I cannot seem to figure out how to enable USB debugging and rooted debugging automatically via TWRP.

Does anyone know adb shell commands to enable it or have a TWRP zip file to enable it?
[Android Q&A, Help & Troubleshooting] khusika:
Hi @teknixstuff

That's called ADB Sideload

Read this for more info

What is ADB Sideload and how can I use it?

What is ADB sideload?ADB sideload is a new feature that was added to AOSP recovery in Jelly Bean. As of version 2.3, TWRP now supports ADB sideload mode. A...

twrp.me
[Android Q&A, Help & Troubleshooting] teknixstuff:
No, I understand ADB sideload, but that is not what I need (in fact I already am using adb sideload in an earlier phase of the script). I need to change whatever lineageos config file to enable adb (rather than needing to manually do it after the reboot). Currently my script pops up a GIF of how to enable USB debugging and Rooted ADB (in developer options), however I would like to be able to automate this part. My script currently supports three devices: Pixel 4a (sunfish), Note II (N7100), and Galaxy A52s 5G (a52sxq), as these are the ones I have. On the Note II, ADB is already enabled from a wipe and ROM flash in both LineageOS 19 and 20. However, on LineageOS 20 for the Pixel 4a and Galaxy A52s, ADB is disabled by default and requires manual intervention to enable. I am using ADB to automatically install and launch the magisk apk, approve the "Magisk needs additional setup" prompt, wait for the reboot, and then install modules. If it helps I can attach the current (albeit buggy) version of my installer. My reasoning for a fully automated installer was that it would vastly simplify the installation process for people who are new to Android modding. Sorry for such a long response (I'm terrible at writing short messages)
[Android Q&A, Help & Troubleshooting] Oswald Boelcke:
Such a glitch occasionally happens... I've removed the duplicate; just use the report button in future and we clean up.

And I've moved your thread to

Android Q&A, Help & Troubleshooting

This forum is for all of your questions about Android Development and Hacking. If you need help troubleshooting a problem, please be as specific as possible by describing your software configuration, including the ROM, kernel, and any modifications you've done.

xdaforums.com

Regards

Oswald Boelcke
[Android Q&A, Help & Troubleshooting] Slim K:
Solutions for your problems can be found here. Keep in mind that solution with modifying only prop values works only in Userdebug and eng ROM bulids. Stock ROMS with the default adbd binary and User builds do not have the necessary SELinux contexts to run in Root mode, so setting the correct ones or setting SELinux to permissive might be a solution.

You may also need to edit the Global Settings db in /data/system/users/0/, usually named settings_global.xml, to add or change:

Key "adb_enabled" defaultvalue "1" value "1"

#if using android 10 or earlier and in some devices

Key "development_settings_enabled" defaultvalue "1" value "1"

Keep in mind that the commands getprop and setprop in TWRP will return/change the values of default.prop from the Recovery and not from the ROM's. So you would need to modify them in their respective files. Off the top of my head I remember persist.sys.usb.config to be in /data/properties/persistent_properties. If you're not sure which props to edit, look at the files: init.usb.rc and init.usb.configfs.rc usually found in /system/etc/init/hw/for more clues.

P.s. I would look for an alternative way of setting up Magisk's env/bind mounts/$PATH instead of rebooting to System and using adb, but thats up to you.
[Android Q&A, Help & Troubleshooting] teknixstuff:
That looks useful! Although I just figured this out myself. Also I've already seen that gist, it doesn't work (out of date?). The values I'm looking for are adb_enabled in settings_global.xml, and echo -n 1 > /data/adbroot/enabled. Also with regards to booting into the system and using ADB, there's a lot that needs doing from the system (installing the magisk APK with adb install, setting up magisk using adb shell input keyevent, and installing modules with adb shell magisk --install-module) and I've already written all the code, so I see no reason to scrap it (nor any other way to do it tbh)

EDIT: settings_global.xml doesn't exist due to /data having been wiped before the install. That won't work.

EDIT 2: I'ma test if you can just push a sparse settings_global.xml and mkdir the folder tree

EDIT 3: Doesn't work. A sparse settings_global.xml just breaks most settings. It doesn't enable ADB.
[Android Q&A, Help & Troubleshooting] alecxs:
run a startup script from init or addon.d

settings put global development_settings_enabled 1
settings put global adb_enabled 1

https://xdaforums.com/t/bootloop-at-lock-screen.4547951/post-88082967
[Android Q&A, Help & Troubleshooting] teknixstuff:
Didn't work. Here's the code I tried:

adb shell mkdir -p /data/adb/service.d
adb shell echo "settings put global development_settings_enabled 1"^>/data/adb/service.d/adb_enabler.sh
adb shell echo "settings put global adb_enabled 1"^>^>/data/adb/service.d/adb_enabler.sh
adb shell chmod 777 /data/adb/service.d/adb_enabler.sh
adb shell mkdir /data/adbroot;echo -n 1 ^>/data/adbroot/enabled

It didn't say anything (ie seemed to work), but after the reboot, adb was NOT enabled.

EDIT: I enabled ADB manually and checked the file, and the 1 had gone missing from both lines! Sounds like a command-line syntax error, probably CMD removing the quotes. Gonna try again with single quotes.

EDIT 2: Still didn't work, but this time the file was created correctly. Are you sure that service.d is processed when magisk is only partially installed?

EDIT 3: I set up magisk manually, rebooted, and still it was not enabled. Running the commands manually works fine.

EDIT 4: After lots of trial and error, I have working code, but magisk has to be manually set up before it works :(

"%adb%" shell mkdir -p /data/adb/service.d
"%adb%" shell echo '#!/bin/sh' ^>/data/adb/service.d/adb_enabler.sh
"%adb%" shell echo 'while [[ -z $^(getprop sys.boot_completed^) ]]; do sleep 1; done;' ^>^>/data/adb/service.d/adb_enabler.sh
"%adb%" shell echo 'settings put global development_settings_enabled 1' ^>^>/data/adb/service.d/adb_enabler.sh
"%adb%" shell echo 'settings put global adb_enabled 1' ^>^>/data/adb/service.d/adb_enabler.sh
"%adb%" shell echo 'rm /data/adb/service.d/adb_enabler.sh' ^>^>/data/adb/service.d/adb_enabler.sh
"%adb%" shell chmod 777 /data/adb/service.d/adb_enabler.sh
"%adb%" shell mkdir /data/adbroot;echo -n 1 ^>/data/adbroot/enabled
[Android Q&A, Help & Troubleshooting] alecxs:
you can achieve the same from /system_root/system/etc/init without magisk, but requires init script.

yes, but maybe too early. check /cache/magisk.log

Magisk can be set up from TWRP (see SQLite commands)

magisk.db injection
[Android Q&A, Help & Troubleshooting] teknixstuff:
Could you give me an example of using /system_root/system/etc/init?

Also by setting up magisk, I mean installing the manager app and approving the "Magisk requires additional setup" prompt. Allowing root is not the problem, as root is already granted via "%adb%" shell mkdir /data/adbroot;echo -n 1 ^>/data/adbroot/enabled. And with regards to the question of it being too early, service.d IS too early, but adding while [[ -z $(getprop sys.boot_completed) ]]; do sleep 1; done; causes it to wait until the system has booted, which works great if magisk is already set up, but the script never gets started if magisk is partially installed AFAIK.
[Android Q&A, Help & Troubleshooting] alecxs:
I remember it didn't work on a Samsung tablet (stock ROM) no matter what I tried (I think I also tried @Slim K's method)

https://xdaforums.com/t/accessing-my-phone-with-a-dead-screen.4542763/post-88166805

what is done with this?

booting magisk_patched.img was always sufficient for service.d scripts, check the logs.

I am not sure about the secontext u:r:su:s0 on LineageOS is permitted for init, maybe I am wrong.

By default, every .rc script placed inside /system/etc/init /vendor/etc/init /odm/etc/init directory is executed. This is the init script language (for examples see my zips)

https://android.googlesource.com/platform/system/core/+/master/init/README.md
[Android Q&A, Help & Troubleshooting] teknixstuff:
Tried the following, no luck. Although /cache/magisk.log says it executed my script, the script did not self-destruct (despite having code to rm itself). And adb_enabler.rc did nothing AFAIK.

"%adb%" shell twrp mount system; twrp remountrw
"%adb%" shell mkdir -p /data/adb/service.d
"%adb%" shell echo '#!/bin/sh' ^>/data/adb/service.d/adb_enabler.sh
"%adb%" shell echo 'while [[ -z $^(getprop sys.boot_completed^) ]]; do sleep 1; done;' ^>^>/data/adb/service.d/adb_enabler.sh
"%adb%" shell echo 'settings put global development_settings_enabled 1' ^>^>/data/adb/service.d/adb_enabler.sh
"%adb%" shell echo 'settings put global adb_enabled 1' ^>^>/data/adb/service.d/adb_enabler.sh
"%adb%" shell echo 'rm /system/etc/init/adb_enabler.rc' ^>^>/data/adb/service.d/adb_enabler.sh
"%adb%" shell echo 'rm /data/adb/service.d/adb_enabler.sh' ^>^>/data/adb/service.d/adb_enabler.sh
"%adb%" shell chmod 777 /data/adb/service.d/adb_enabler.sh
"%adb%" shell echo 'on boot' ^> /system_root/system/etc/init/adb_enabler.rc
"%adb%" shell echo ' exec_background u:r:magisk:s0 0 0 -- /data/adb/service.d/adb_enabler.sh' ^>^> /system_root/system/etc/init/adb_enabler.rc
"%adb%" shell chown 0.0 /system_root/system/etc/init/adb_enabler.rc
"%adb%" shell chmod 777 /system_root/system/etc/init/adb_enabler.rc
"%adb%" shell chcon u:object_r:system_file:s0 /system_root/system/etc/init/adb_enabler.rc
"%adb%" shell mkdir /data/adbroot;echo -n 1 ^>/data/adbroot/enabled

EDIT: Tried this, and icanhasworked was NOT created, so the script must not be running correctly.

"%adb%" shell mkdir -p /data/adb/service.d
"%adb%" shell echo '#!/bin/sh' ^>/data/adb/service.d/adb_enabler.sh
"%adb%" shell echo 'touch /data/adb/service.d/icanhasworked' ^>^>/data/adb/service.d/adb_enabler.sh
"%adb%" shell echo 'while [[ -z $^(getprop sys.boot_completed^) ]]; do sleep 1; done;' ^>^>/data/adb/service.d/adb_enabler.sh
"%adb%" shell echo 'settings put global development_settings_enabled 1' ^>^>/data/adb/service.d/adb_enabler.sh
"%adb%" shell echo 'settings put global adb_enabled 1' ^>^>/data/adb/service.d/adb_enabler.sh
"%adb%" shell echo 'rm /data/adb/service.d/adb_enabler.sh' ^>^>/data/adb/service.d/adb_enabler.sh
"%adb%" shell chmod 777 /data/adb/service.d/adb_enabler.sh
"%adb%" shell mkdir /data/adbroot;echo -n 1 ^>/data/adbroot/enabled
[Android Q&A, Help & Troubleshooting] teknixstuff:
There is no magisk_patched.img involved here. Magisk is being installed via TWRP, and since Magisk 26.0, further setup is required if installed from recovery.
[Android Q&A, Help & Troubleshooting] alecxs:
that explains :p installing Magisk through TWRP is long deprecated.

that's a pretty clear indication your script was interrupted. afair zygisk uses two stage init, all processes are killed and executed twice.

also please note that /data must decrypted during boot. depending on encryption type that may require credentials for CE encrypted directories.

I recommend to play with timing. 30 seconds after boot everything should be ready.
[Android Q&A, Help & Troubleshooting] teknixstuff:
My script already does wait! It uses while [[ -z $(getprop sys.boot_completed) ]]; do sleep 1; done;! Also I know data does NOT need decryption, since DFE-NEO is applied on devices where encryption exists (since TWRP+Encryption=failure, at least on my Pixel 4a). Also I know installing magisk with TWRP is deprecated, but how else can I install magisk fully automatically? If I tried to install Magisk Manager and automate it with input keyevent, that rather complicates things, and anyway then I'd need to enable ADB without magisk at all! And if I didn't install magisk at all, then people would inevitably try to do it themselves and screw up, plus I have some modules to preinstall (Play Integrity bypass and a bootanimation). And yes I could make it another checkbox in the Installer, but that will be confusing for people, add more complexity and code (where failures could occour), and anyway if you don't want magisk, just uninstall it (Uninstalling is way easier than installing)! Also with regards to interruption, I know that 0 lines of code are getting executed, as I tried putting touch /data/adb/service.d/icanhasworked and touch /cache/icanhasworked at the top of the script, both to no avail.
[Android Q&A, Help & Troubleshooting] alecxs:
Nah... sys.boot_completed is way too early ;)
[Android Q&A, Help & Troubleshooting] teknixstuff:
Well either way the script isn't running line 1, let alone getting past sys.boot_completed. I'll gladly try adding sleep 60 after it though! EDIT: Yet again doesn't work.
[Android Q&A, Help & Troubleshooting] alecxs:
maybe you have issue with windows line endings - does the script do something when executed manually?

instead of creating the script on-the-fly adb push prepared file for testing purposes.
[Android Q&A, Help & Troubleshooting] teknixstuff:
Already tested that, the script does exactly what it should when ran via adb shell /data/adb/service.d/adb_enabler.sh, and I was careful to ensure that the echo and redirection all ran on-device, to avoid line ending issues (or more likely text-eating issues, like happened previously when I missed a CMD escape char). Also the bat file is fully self-contained and I would like to avoid adding any required files, so creating on-the-fly is ideal. At this point I suspect something to do with the magisk environment is the problem, although I have no way of testing my claims. Also is there a way to enable push notifications from XDA so I can respond sooner?
[Android Q&A, Help & Troubleshooting] alecxs:
if the script is working and magisk.log says it is executed, I have no clue about the real issue. all I know is that magisk uses mount mirrors, might be the execution happens on another mount namespace or you have some avc denies in kmsg.

I could do a test on my tablet, but if you say it's not an issue with the script itself, I trust you.

maybe ask the ROM developer what's the official way to enable usb-debugging hands-free?

We have a Mobile app push but no desktop push.
[Android Q&A, Help & Troubleshooting] teknixstuff:
What's an avc deny, and what is kmsg? Also the full install script is device-specific, and none of the devices I have built it for are tablets (I don't own any working android tablets). With regards to asking the ROM dev, the ROM being used is LineageOS, and I'm not sure how to contact them. Also thanks for the info about push notifications, however all my mobiles get factory reset on a daily basis currently (script testing), so mobile push isn't terribly useful.
[Android Q&A, Help & Troubleshooting] alecxs:
example: if selinux is enforced, you can format /data, all files are gone, and you think the command was successful (as root) - but in dmesg it creates "avc: denied" entry and next time you open a shell, all files are still there. (example, but happened to me)

maybe magisk has issue with selinux and think the script is executed, but it's not. check your dmesg
[Android Q&A, Help & Troubleshooting] teknixstuff:
How do I check dmesg? Or would it just be better to disable SELinux with setenforce 0 for now? Also doesn't magisk do everything in the fully permissive u:r:magisk:s0 SELinux context?
[Android Q&A, Help & Troubleshooting] alecxs:
Basically, yes. Just guesswork possible issue with Magisk, IDK. I must confess I am still on A10 + Magisk 24.

you should be able to get dmesg by typing dmesg in shell (maybe /system/bin/toybox dmesg)
[Android Q&A, Help & Troubleshooting] teknixstuff:
I got it working! Thanks for your advice with dmesg, it listed all the issues with my script! First off, I'd used chmod 777, and init says skipping insecure file if it's world-writable, so I used chmod 755 to fix that. Next up, SELinux was complaining that the init context is not allowed to run binaries without a transition first, so I put back exec u:r:magisk:s0 0 0 to switch to the magisk context. And finally, init failed to run settings because PATH (or whatever the Linux/Android equivalent is) wasn't set up that early in the boot process. Here's my final, working code:

"%adb%" shell twrp mount system; twrp remountrw
"%adb%" shell echo 'on property:sys.boot_completed=1' ^> /system_root/system/etc/init/adb_enabler.rc
"%adb%" shell echo ' exec u:r:magisk:s0 0 0 -- /system/bin/settings put global development_settings_enabled 1' ^>^> /system_root/system/etc/init/adb_enabler.rc
"%adb%" shell echo ' exec u:r:magisk:s0 0 0 -- /system/bin/settings put global adb_enabled 1' ^>^> /system_root/system/etc/init/adb_enabler.rc
"%adb%" shell chown 0:0 /system_root/system/etc/init/adb_enabler.rc
"%adb%" shell chmod 755 /system_root/system/etc/init/adb_enabler.rc
"%adb%" shell chcon u:object_r:system_file:s0 /system_root/system/etc/init/adb_enabler.rc
"%adb%" shell mkdir /data/adbroot;echo -n 1 ^>/data/adbroot/enabled

Now just to work around the pesky "Allow USB Debugging?" prompt (resetprop ro.adb.secure 0 did not work)

EDIT: resetprop ro.adb.secure 0 DOES work! I just missed a closing ' mark. Here's the new code:

"%adb%" shell twrp mount system; twrp remountrw
"%adb%" shell echo 'on property:sys.boot_completed=1' ^> /system_root/system/etc/init/adb_enabler.rc
"%adb%" shell echo ' exec u:r:magisk:s0 0 0 -- /system/bin/resetprop ro.adb.secure 0' ^>^> /system_root/system/etc/init/adb_enabler.rc
"%adb%" shell echo ' exec u:r:magisk:s0 0 0 -- /system/bin/settings put global development_settings_enabled 1' ^>^> /system_root/system/etc/init/adb_enabler.rc
"%adb%" shell echo ' exec u:r:magisk:s0 0 0 -- /system/bin/settings put global adb_enabled 1' ^>^> /system_root/system/etc/init/adb_enabler.rc
"%adb%" shell chown 0:0 /system_root/system/etc/init/adb_enabler.rc
"%adb%" shell chmod 755 /system_root/system/etc/init/adb_enabler.rc
"%adb%" shell chcon u:object_r:system_file:s0 /system_root/system/etc/init/adb_enabler.rc
"%adb%" shell mkdir /data/adbroot;echo -n 1 ^>/data/adbroot/enabled
[Android Q&A, Help & Troubleshooting] alecxs:
In case resetprop doesn't work another workaround for Android 10 was placing /data/misc/adb/adb_keys from script, can be generated on-the-fly too (not sure for A13).

but I found this thread

How to enable access via adb on a new installed OS

For automatic installation and configuration of a phone running the Android OS the access via adb is required. "Unfortunately" the access via adb is disabled in most Android distributions (in reality it is of course good that the access via adb...

xdaforums.com
[Google Pixel 8 Pro] marmin:
Hi All

Wonder if anyone can shed any light on this little bit of weirdness:

Had a Pixel 6 Pro and 2 wireless charging stands which worked perfectly.

Changed to Pixel 8 Pro and all was fine for a while.

BUT all of a sudden the stands wont charge the 8, I just get "realign phone to charge wirelessly" showing on phone, still works perfectly for the 6!?!?

Charges fine from the USBC in the back of the wireless charger.

Reboot does nothing and seems to have stopped on both wireless stands?!

UPDATE: Just noticed that I cant turn on battery share and when I press it, it flicks on and off and then the wireless charging works for a sec then goes to "connected-not charging"!?

Seeing a few examples now on Reddit

Looks like it might be software/phone related.

Anyone found a fix, before I contact them and they tell me its just me?
[Google Pixel 8 Pro] rlivin:
I have the same problem.
[Google Pixel 8 Pro] Major Tokage:
My wireless charging has been fine on the OG Pixel Stand. I have not tried batt share yet
[Google Pixel 8 Pro] CHH2:
Both my P6P and P8P have been spotty on my wireless chargers. So far, the P6P was spottier than the P8P but that remains to be seen. I chalk part of it up to the chargers themselves though. One is an old original TYLT wireless charger from who knows how many years ago. The other is an Ikea fabric slab with a wood base. Looks nice but questionable on its effectiveness.

As to battery share, just tried it. It stays toggled on and I was just able to top off my PBPs.
[Google Pixel 8 Pro] byproxy:
no issues here using aftermarket wireless charging stands. i have battery sharing turned off though so maybe it's an issue caused by that?
[Google Pixel 8 Pro] marmin:
Nah, mine wont even toggle on.
[Google Pixel 8 Pro] ScoobyWRX:
Wireless charging and toggling battery share both working for me
[Google Pixel 8 Pro] old_fart:
Is it tied to the toggle labeled " adaptive charging" being turned on or off ?
[Google Pixel 8 Pro] ScoobyWRX:
Working with adaptive charging on or off for me
[Google Pixel 8 Pro] xmenmatrix:
Did you try without any case on?

Seen several cases with wrong mage safe ring position, centered on the google logo.

Which is wrong, as you can see on official cases like Mous.
[Google Pixel 8 Pro] marmin:
Mine is misbehaving without any case at all.

Point blank refuses to charge wirelessly now, just comes up with a message saying realine phone to charge.

also when I click the Battery Share toggle, it just flicks on and off immediately, with no message.
[Google Pixel 8 Pro] aabshire:
I noticed if I had an attached item (wallet) on my phone it wouldn't turn on (Peak Design Case with wallet) If I remove the wallet it toggles
[Google Pixel 8 Pro] marmin:
Phone is not in a case
[Google Pixel 8 Pro] A.Priori:
So far, in my car with wireless charging and wireless android auto, my P8P is working great.
[Google Pixel 8 Pro] K1nsey6:
Both working fine for me
[FYT Android Head Units] dario85re:
Good morning, I'm having problems displaying the names of the songs on my device. I have an m700s fty car radio and I can see the name of the station, but it doesn't give me any additional information like the names of the songs. Has this happened to anyone else? How did you solve it? Thank you very much.