Hi everyone
I have a xperia tablet s (SGPT1211) and for a mistake i change one line in the built.prop and now my tablet still in bootloop, what can i do to resolve this????
thanks for the help.
What line exactly?
Sent from my Nexus 4 using XDA Premium 4 mobile app
jvc931 said:
Hi everyone
I have a xperia tablet s (SGPT1211) and for a mistake i change one line in the built.prop and now my tablet still in bootloop, what can i do to resolve this????
thanks for the help.
Click to expand...
Click to collapse
Well that was silly..
DO NOT FACTORY RESET....
At boot Can you you get adb shell with root?
Do you have rescue back-door??
If not then you are probably stuck until sony releases a new update
the line in the dalvik cache this dalvik.vm.heapsize=384m
what happen whit the factory reset???
i don't have the rescue back-door
i try to flash with the recovery but always aborted =S =S =S =S =S
jvc931 said:
the line in the dalvik cache this dalvik.vm.heapsize=384m
what happen whit the factory reset???
i don't have the rescue back-door
i try to flash with the recovery but always aborted =S =S =S =S =S
Click to expand...
Click to collapse
if you factory reset then you will loose adb shell on boot!!!
So do not factory reset....
first of all try to use AiO Tools to install rescue back-door
then try: See FAQ if not sure how to set up adb etc
adb shell
su
chmod 644 /system/build.prop
exit
exit
adb reboot
(See if that helps. This will work if you had not set the permissions correctly)
If no then
adb shell
su
cp /system/build.prop /sdcard/build.prop
exit
exit
adb reboot
(Then insert sd card into pc and edit the build.prop as needed)
Then put back into the tablet and:
adb shell
su
mv /system/build.prop /system/bulid.prop.bak
cp /sdcard/build.prop /system/build.prop
chmod 644 /system/build.prop
exit
exit
adb reboot
Let me know if you get stuck
i loss the shell because i do the factory reset =S =S =S =S
C:\Users\Jvc\Desktop\adb>adb shell
error: closed
C:\Users\Jvc\Desktop\adb>adb shell
error: closed
C:\Users\Jvc\Desktop\adb>
sorry for the double post
jvc931 said:
i loss the shell because i do the factory reset =S =S =S =S
C:\Users\Jvc\Desktop\adb>adb shell
error: closed
C:\Users\Jvc\Desktop\adb>adb shell
error: closed
C:\Users\Jvc\Desktop\adb>
Click to expand...
Click to collapse
Oh. You will have to wait until there is a new release. May take a while as JB R2 was just release
:crying::crying::crying::crying: **** and is possible in the sony technical resolve this??? i still have warranty
jvc931 said:
:crying::crying::crying::crying: **** and is possible in the sony technical resolve this??? i still have warranty
Click to expand...
Click to collapse
Yes providing you act stupid and tell them that it failed when you tried the latest update.
Hopefully they don't notice and you will be okay
I have done that and was all good.
stifilz said:
if you factory reset then you will loose adb shell on boot!!!
So do not factory reset....
first of all try to use AiO Tools to install rescue back-door
then try: See FAQ if not sure how to set up adb etc
adb shell
su
chmod 644 /system/build.prop
exit
exit
adb reboot
(See if that helps. This will work if you had not set the permissions correctly)
If no then
adb shell
su
cp /system/build.prop /sdcard/build.prop
exit
exit
adb reboot
(Then insert sd card into pc and edit the build.prop as needed)
Then put back into the tablet and:
adb shell
su
mv /system/build.prop /system/bulid.prop.bak
cp /sdcard/build.prop /system/build.prop
chmod 644 /system/build.prop
exit
exit
adb reboot
Let me know if you get stuck
Click to expand...
Click to collapse
The build.prop has to get pulled to sdcard1.
If that tweak was not applied then ADB pull has to be done and the build.prop file has to be in the internal storage.
Sent from my Nexus 4 using XDA Premium 4 mobile app
---------- Post added at 08:21 AM ---------- Previous post was at 08:20 AM ----------
jvc931 said:
i loss the shell because i do the factory reset =S =S =S =S
C:\Users\Jvc\Desktop\adb>adb shell
error: closed
C:\Users\Jvc\Desktop\adb>adb shell
error: closed
C:\Users\Jvc\Desktop\adb>
Click to expand...
Click to collapse
Wait, where you on the bootloop when doing this out did you go to the recovery?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Wait said:
yes i try to put the build.prop whit adb commands but before i do the factory reset and the tablet stay in the bootanimation.
Click to expand...
Click to collapse
jvc931 said:
yes i try to put the build.prop whit adb commands but before i do the factory reset and the tablet stay in the bootanimation.
Click to expand...
Click to collapse
So you did do it in the boot animation?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Yes
jvc931 said:
Yes
Click to expand...
Click to collapse
How long in the boot animation?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Thanks all for the help, i send the tablet to Sony and they repair under warranty.
Related
Okay, so I've noticed that this rooting method is a little unconventional. It works through a compromised Fota.pkg which has setuid on /system/bin/sh as root. This is not a very safe, as any application that runs sh will gain root access to your system. Scary... :S Anyway, in order to fix this we need to take a few steps.
It is important that you do these in order, otherwise you may lose root access
Install a proper SU with whitelist
1. Download http://bit.ly/aWgALL
2. Unzip the system folder.
3.
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb push system/bin/su /sdcard/su
adb push system/app/Superuser.apk /sdcard/Superuser.apk
adb shell dd if=/sdcard/su of=/system/bin/su
adb shell dd if=/sdcard/Superuser.apk of=/system/app/Superuser.apk
adb shell chmod 6777 /system/bin/su
adb shell chmod 644 /system/app/Superuser.apk
4. Reboot your phone.
Fix sh to not setuid to root
1.
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell chmod 0755 /system/bin/sh
Properly install busybox
1. Here, it's easier to look for the busybox installer app from the market and then install from there. If you did everything correctly, then after you hit install in the busybox app a prompt will come up asking you to allow the app to have root. Hit allow.
You're done!
this might be stupid questions, i know. But where should I unzip the system folder that mentioned to? And where to type those command?
chai_archer said:
this might be stupid questions, i know. But where should I unzip the system folder that mentioned to? And where to type those command?
Click to expand...
Click to collapse
If you followed the root guide you can put it in the step 4 folder.
Then hit windows key + r and in the box type CMD
A console window comes up.
in the console window type cd <path.to.your.step.4.folder>
then go from there.
zephyrix said:
Properly install busybox
1. Here, it's easier to look for the busybox app from the market and then install from there. If you did everything correctly, then after you hit install in the busybox app a prompt will come up asking you to allow the app to have root. Hit allow.
You're done!
Click to expand...
Click to collapse
i did everything as mentioned but it dint ask me for permission wen installin busybox is it because i had it installed sometime before runnin this guide?
yea i knw im a noob after all
bcool15 said:
i did everything as mentioned but it dint ask me for permission wen installin busybox is it because i had it installed sometime before runnin this guide?
yea i knw im a noob after all
Click to expand...
Click to collapse
yep.
if you check the superuser app it should already be there.
zephyrix said:
yep.
if you check the superuser app it should already be there.
Click to expand...
Click to collapse
all i see in superuser app is titanium backup pro
that's strange. does busybox report that it's installed?
zephyrix said:
that's strange. does busybox report that it's installed?
Click to expand...
Click to collapse
nope it doesnt
well i tried all this and now i lost my root. Did EXACTLY what's written. Anyway to reverse this and get my root back?
unknown13x said:
well i tried all this and now i lost my root. Did EXACTLY what's written. Anyway to reverse this and get my root back?
Click to expand...
Click to collapse
i think i lost mine too but to reactivate there is command or prolly i just messed up summmwhere n redid my whole root with v3 update
bcool15 said:
i think i lost mine too but to reactivate there is command or prolly i just messed up summmwhere n redid my whole root with v3 update
Click to expand...
Click to collapse
use "su" to get root access... allow when the Superuser Whitelist notification pops up.
it worked for me....followed the steps, after i downloaded the busybox app i opened it and a box popped up "Superuser Request", it had discription of the busybox app and then asked whether to allow or deny the request....i then checked the superuser app and was able to see the busybox app in thr....
can anyone confirm if these steps were added in the new root method? please
bcool15 said:
can anyone confirm if these steps were added in the new root method? please
Click to expand...
Click to collapse
I'd like to know that too, I mean, in 2v2 do we still need to do the whitelist thing?
root in adb
I tried this on the last root (ROOT_F2v2) and I lost root in adb..
I still had regular root
I had to revert it back with "chmod 6777 /system/bin/sh" to get adb do admin task again.. (I use adb regularly)
Does anyone know how to secure sh and still have root in adb?
Regards.
th4r said:
I tried this on the last root (ROOT_F2v2) and I lost root in adb..
I still had regular root
I had to revert it back with "chmod 6777 /system/bin/sh" to get adb do admin task again.. (I use adb regularly)
Does anyone know how to secure sh and still have root in adb?
Regards.
Click to expand...
Click to collapse
adb shell su
And after superuser popup add "unknown application" to the whitelist.
Chillest said:
adb shell su
And after superuser popup add "unknown application" to the whitelist.
Click to expand...
Click to collapse
Yes that give me root in adb shell but adb is still running unprivileged.
I believe it's because we can't patch the bootloader yet, so we still have getprop ro.secure 1. :'(
I did a little script to toggle setuid on /system/bin/sh when I'm doing root stuff from adb
Sent from my rooted X10i
I have installed this to protect the system.
The only concern I have is i cannot run for example my cleaning script.
If i type into cmd ;
"adb shell su" it comes up with a # and freezes. If i type in
"adb shell<enter>
su" it works fine. and i can paste all the commands in line by line.
If i do either in a bat or cmd file it crashes. How do i run scripts as su
Here are the answers....
bcool15 said:
can anyone confirm if these steps were added in the new root method? please
Click to expand...
Click to collapse
No they were not. The reason is that many of the rooting steps rely on a setuid "sh"
gfgodoy said:
I'd like to know that too, I mean, in 2v2 do we still need to do the whitelist thing?
Click to expand...
Click to collapse
Yes
Chillest said:
adb shell su
And after superuser popup add "unknown application" to the whitelist.
Click to expand...
Click to collapse
So what? The uid for the shell application launched after invoking "adb shell" is not going to match any of the installed applications anyways. The thing is that Superuser.apk installs a mechanism by which the user (human) can detect when an application is requesting root access. Based upon the nature of the application you may or may not want to grant root access. That is the whole point.
th4r said:
Yes that give me root in adb shell but adb is still running unprivileged.
I believe it's because we can't patch the bootloader yet, so we still have getprop ro.secure 1. :'(
I did a little script to toggle setuid on /system/bin/sh when I'm doing root stuff from adb
Sent from my rooted X10i
Click to expand...
Click to collapse
Oh yeah? I just use "su" whenever I want root access... and I didnt have to write any scripts to enable/disable it.
k1ckn1ck said:
I have installed this to protect the system.
The only concern I have is i cannot run for example my cleaning script.
If i type into cmd ;
"adb shell su" it comes up with a # and freezes. If i type in
"adb shell<enter>
su" it works fine. and i can paste all the commands in line by line.
If i do either in a bat or cmd file it crashes. How do i run scripts as su
Click to expand...
Click to collapse
Then you shouldn't be rooting in the first place. Take my advice, lay off the rooting. It definitely doesn't have anything that will be of advantage to you.
j4mm3r said:
Then you shouldn't be rooting in the first place. Take my advice, lay off the rooting. It definitely doesn't have anything that will be of advantage to you.
Click to expand...
Click to collapse
easy now, it's a fair question, would be nice to be able to run cleaning scripts on a protected system. no need to be a prick
in answer to the question though, once the batch starts adb shell, it won't continue till that process ends
I did some googling for some comandline tools that might allow sending keystrokes to a process, but nothing easy appeared, looks like your only option is to use a linux friendly notepad to create some shell scripts you can execute from the sdcard. i.e. on device
su
chmod 755 /sdcard/myscript.sh
./sdcard/myscript.sh
easiest way to do scripts on a secured root IMO
Hi, I have deleted my build.prop on my phone and im stuck in a boot loop.
I have a backup of a working build.prop on my PC but im having trouble sending it over with ADB, done loads of google'in and searching on here but with no luck.
Samsung galaxy S Rooted
Booted in to ClockworkMod Recovery v3.0.0.5
Mounted /system
CMD> adb push C:\build.prop /system/build.prop failed to copy 'C:\build.prop' to '/system/build.prop' : Permission denied
Please help time is running out got work tomorrow and need my phone work, i could do a restore but i cant remember the last time a backup.
Cheers, James
jamesbebby said:
Hi, I have deleted my build.prop on my phone and im stuck in a boot loop.
I have a backup of a working build.prop on my PC but im having trouble sending it over with ADB, done loads of google'in and searching on here but with no luck.
Samsung galaxy S Rooted
Booted in to ClockworkMod Recovery v3.0.0.5
Mounted /system
CMD> adb push C:\build.prop /system/build.prop failed to copy 'C:\build.prop' to '/system/build.prop' : Permission denied
Please help time is running out got work tomorrow and need my phone work, i could do a restore but i cant remember the last time a backup.
Cheers, James
Click to expand...
Click to collapse
CMD> adb push C:\build.prop /system
CMD> adb push C:\build.prop /system failed to copy 'C:\build.prop' to '/system/build.prop' : Permission denied
Still getting that permission denied.
Cheers, James
have you mounted /system in r/w?
sweetnsour said:
have you mounted /system in r/w?
Click to expand...
Click to collapse
What with adb???
Cheers, James
Try using Android Commander after mounting /system in the recovery menu.
http://androidcommander.com/
jamesbebby said:
What with adb???
Cheers, James
Click to expand...
Click to collapse
not sure if thisll work but try this
Try:
adb remount
adb push C:\build.prop /system
GchildT said:
Try using Android Commander after mounting /system in the recovery menu.
Click to expand...
Click to collapse
Wow, finally download all that is need to install 'Android Commander' but still no luck.
Files count: 1
Files source: C:\Users\James\Desktop
Files destination: /system/
Starting operation...
Remounting...
[1/1] Pushing file: build.prop
failed to copy 'C:\Users\James\Desktop\build.prop' to '/system//build.prop': Permission denied
*** Operation complete! *
Click to expand...
Click to collapse
sweetnsour said:
not sure if thisll work but try this
Click to expand...
Click to collapse
Ill look into that post but i get fault on the #su bit.
fifarunnerr said:
Try:
adb remount
adb push C:\build.prop /system
Click to expand...
Click to collapse
CMD> adb remount
remount failed: Operation not permitted
Thanks for the reply's, Pulling my hair out here!!! Ah
Cheers, James
Right then im gunna have to flash my phone to get it working, But i dont want lose everything.
Whats the best way to go about this?
Cheers, James
jamesbebby said:
Right then im gunna have to flash my phone to get it working, But i dont want lose everything.
Whats the best way to go about this?
Cheers, James
Click to expand...
Click to collapse
depends. are you on the stock rom or a custom rom?
custom = just reflash the rom
stock = lets hope you have a backup. if you don't, you might as well flash a custom rom
Sent from my LG-P500 using XDA Premium App
sweetnsour said:
depends. are you on the stock rom or a custom rom?
custom = just reflash the rom
stock = lets hope you have a backup. if you don't, you might as well flash a custom rom
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Hi, Im on I9000XWJVB stock as the battery life is the best ive come across.
I have a backup but its weeks old, the only thing i dont want to lose is SMS messages, apps and files i have save on my computer.
Cheers, James
I really am well and truly stuck on trying to get this build.prop over to system/
Cheers, James
jamesbebby said:
I really am well and truly stuck on trying to get this build.prop over to system/
Cheers, James
Click to expand...
Click to collapse
Can't you take a backup of your ROM with Clockwork, reflash your stock ROM and restore just the data?
jamesbebby said:
CMD> adb push C:\build.prop /system failed to copy 'C:\build.prop' to '/system/build.prop' : Permission denied
Still getting that permission denied.
Cheers, James
Click to expand...
Click to collapse
I also reckon that booting into recovery and simply restoring a NANDRROID backup is your best bet.
But, if this isn't possible then I think you need to be root when in ADB which is done with the su command
adb shell
su
(this should change the prompt, I think from # to $ or the otherway)
Make an update.zip of build.prop and flash
Or try qtadb
DanWilson said:
Can't you take a backup of your ROM with Clockwork, reflash your stock ROM and restore just the data?
Click to expand...
Click to collapse
Yea i was think that but ive never done it before.........so will all my messages & contacts still be there once i restore???
ben_pyett said:
I also reckon that booting into recovery and simply restoring a NANDRROID backup is your best bet.
But, if this isn't possible then I think you need to be root when in ADB which is done with the su command
adb shell
su
(this should change the prompt, I think from # to $ or the otherway)
Click to expand...
Click to collapse
CMD> adb shell
*daemon not running. starting it now on port 5037 *
*daemon started successfully*
~ $ su
su
/sbin/sh: su: not found
So 'su' stands for superuser??? I have superuser installed and working on my phone before this problem came.
cdesai said:
Make an update.zip of build.prop and flash
Or try qtadb
Click to expand...
Click to collapse
qtadb looks like a good app but when it starts;
"adbd cannot run as root in productions so you cant do anything /system partition. Run anyway?"
I was thinking of a update.zip with my working build.prop but didnt really know what i was doing, If you know what your doing with update.zip's and its not to much trouble do you think you could knock it up for me if i send it to you?
Once again thanks for your reply's!!!
Cheers, James
i've got a similar problem, on build.prop replacing via update.zip
i'll keep you informed...
i need to pull and push some system files in my phone for that i need to enter recovery mode in my xperia sola.please help to enter recovery mode.my phone is rooted.thanks in advance :good:
dviraj00 said:
i need to pull and push some system files in my phone for that i need to enter recovery mode in my xperia sola.please help to enter recovery mode.my phone is rooted.thanks in advance :good:
Click to expand...
Click to collapse
I think you dont need to put your device to recovery mode. Just use adb shell
to pull: (no need superuser privileges)
ex: format: adb pull [location of the file in the device] [to where the file is save locally]
adb pull /system/xbin/su c:
Click to expand...
Click to collapse
to push: (need su) since you rooted then:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
chmod 777 /system/app
then exit from devices, go to your command prompt and type:
adb push <local> <remote>
Click to expand...
Click to collapse
Hope it helps
capsule46 said:
I think you dont need to put your device to recovery mode. Just use adb shell
to pull: (no need superuser privileges)
to push: (need su) since you rooted then:
Hope it helps
Click to expand...
Click to collapse
thank you mate bt i am just a noob and dont know how to use adb shell.can u tell me plzz.this will save my relationship,plz mate
Hi, sorry for late reply
I assume you have installed your device driver properly
Then install android sdk: go to developer.android.com/sdk
Follow the step to install it. If you done it properly,you will find adb command in folder installation name platform-tools
Use it in command prompt. You can type adb /? to learn its capability.
Or you just go frok my post earlier
Hope it helps
Sent from my GT-N7100 using Tapatalk 2
my touch screen(including touch buttons for back and menu/option) is dead and i need to back it up.
is there a way to dump the phone memory to my pc or memorycard? i dont have debugging turned on :/
please help
EDIT: i am on official latest update not locked not rooted
A)is your phone rooted
Or
B)is your phone bootloader unlocked .
If neither then can you move the pointer(select) with navigation keys of keyboard and select using enter ?
Sent from my SK17i using Tapatalk 4
karandpr said:
A)is your phone rooted
Or
B)is your phone bootloader unlocked .
If neither then can you move the pointer(select) with navigation keys of keyboard and select using enter ?
Sent from my SK17i using Tapatalk 4
Click to expand...
Click to collapse
bootloader is unlockable but not unlocked
i cant get through the initial lockscreen (no code or pass just the swipe kind): i managed the first time i rebooted :/
i have managed to activate usb debug but the one click root er fails to run the superuser app :/
is there a manual way of doing it?
http://forum.xda-developers.com/showthread.php?t=2399464
Use cydia impactor
Then there is shell menu in the program
Use this command to backup everything
Code:
tar -c /sdcard/backup.tar /data/*
And wait for a while ...
Alternatively you can
Code:
dd if=/dev/block/mtdblock3 of=/sdcard/data.img bs=4096
Then
Code:
md5sum data.img > nandroid.md5
It will give you nandroid backup...copy the contents to backup the /sdcard/clockworkmod directory and then use it to restore in future when you have cwm...
Sent from my SK17i using Tapatalk 4
Code:
[email protected]:/ $ dd if=/dev/block/mtdblock3 of=/sdcard/data.img bs=4096
/dev/block/mtdblock3: cannot open for read: Permission denied
1|[email protected]:/ $ tar -c /sdcard/backup.tar /data/*
/system/bin/sh: tar: not found
is what i get :/
i tried copying the data folder with a file manager but to paste it needed the menu/options button :/
You need to be root user before executing .Use "su" ...and then execute commands...
i have a lenovoA319
i wanna get involved into the root thing , so i wanna make a backup of my stock phone in case i wanted to get it back to its conditions-i dont care about warranty but i lilke to keep a copy of every thing-
as adb backup doesnt work , it seems that many users have faced that , so what are the alternatives ?
is there a way to back up the stock bootloader?
dimmu.borgir said:
i have a lenovoA319
i wanna get involved into the root thing , so i wanna make a backup of my stock phone in case i wanted to get it back to its conditions-i dont care about warranty but i lilke to keep a copy of every thing-
as adb backup doesnt work , it seems that many users have faced that , so what are the alternatives ?
is there a way to back up the stock bootloader?
Click to expand...
Click to collapse
backing up through a recovery is best
BatDroid said:
backing up through a recovery is best
Click to expand...
Click to collapse
stock recovery???
dimmu.borgir said:
stock recovery???
Click to expand...
Click to collapse
You Can't Do Anything With Stock Recovery Other Than Factory Reset In Emergency Conditions.. Install A Custom Recovery like TWRP,Philz for Your Device & Backup As You Wish..
LoverBoy2415 said:
You Can't Do Anything With Stock Recovery Other Than Factory Reset In Emergency Conditions.. Install A Custom Recovery like TWRP,Philz for Your Device & Backup As You Wish..
Click to expand...
Click to collapse
is there a custom recovery backup phone into the pc
i did the backup using flashtool, i backed up all the partitions
LoverBoy2415 said:
You Can't Do Anything With Stock Recovery Other Than Factory Reset In Emergency Conditions.. Install A Custom Recovery like TWRP,Philz for Your Device & Backup As You Wish..
Click to expand...
Click to collapse
Instead ob adb backup/restore, you can use adb pull/push. But it requires fixing file permissions and ownerships. I do it like this from a Bash shell on my Linux computer:
Bash:
APP_ID="org.secuso.privacyfriendlynotes"
# Backup (RUN WITH OLD PHONE CONNECTED)
adb pull "/data/data/${APP_ID}"
# Restore (RUN WITH NEW PHONE CONNECTED)
APP_OWNERSHIP=$(adb shell stat --format "%U:%G" "/data/data/${APP_ID}")
adb shell mv "/data/data/${APP_ID}" "/data/data/${APP_ID}_backup"
adb push "./${APP_ID}" "/data/data/${APP_ID}"
adb shell restorecon "/data/data/${APP_ID}"
adb shell chown -R "${APP_OWNERSHIP}" "/data/data/${APP_ID}"
#adb shell rm -rf "/data/data/${APP_ID}_backup"
ferivon said:
Instead ob adb backup/restore, you can use adb pull/push. But it requires fixing file permissions and ownerships. I do it like this from a Bash shell on my Linux computer:
Bash:
APP_ID="org.secuso.privacyfriendlynotes"
# Backup (RUN WITH OLD PHONE CONNECTED)
adb pull "/data/data/${APP_ID}"
# Restore (RUN WITH NEW PHONE CONNECTED)
APP_OWNERSHIP=$(adb shell stat --format "%U:%G" "/data/data/${APP_ID}")
adb shell mv "/data/data/${APP_ID}" "/data/data/${APP_ID}_backup"
adb push "./${APP_ID}" "/data/data/${APP_ID}"
adb shell restorecon "/data/data/${APP_ID}"
adb shell chown -R "${APP_OWNERSHIP}" "/data/data/${APP_ID}"
#adb shell rm -rf "/data/data/${APP_ID}_backup"
Click to expand...
Click to collapse
This script requires `adb root`, right? Is it still available in modern versions of Android? I didn't manage to use it even after setting `ro.debuggable=1` in `/system/build.prop`, on my Android 12.
Unless you have any insights about this, I guess I can change permission to or copy an app's data directory with `su` before pulling it.
I also noticed that some files (at least the `cache` and `code_cache` directories) in an app's data dir belong to a different group. I'm wondering whether setting the ownership of everything to the same user and group could cause problems in the future.